Database Users

[GUIDE]How to make a ROM - Easiest

How to Make Your Own Custom Rom
Click to expand...
Click to collapse
Part 1 : Setting Up Dsixda's Android Kitchen.
So, Do you want to make a custom rom or, mod one that is made already? If your answer to this question is yes then you are at the right place. In this article I will help you get started with setting up an environment to make your own custom roms or edit the ones that are developed already. We are going to take help of dsixda's Android Kitchen Utility to help us in this task and in this article I am going to help you get started by guiding you through the installation process of Android Kitchen on your Personal Computer. So, you might have the question in your mind what exactly is Android Kitchen and what does it do and whom it is for? Continue reading to know all this as well as to get instructions on setting it up on your PC.
What is Dsixda's Android Kitchen?
Who is this kitchen for?
-Those who are brand new to creating custom ROMs and want an easy place to start learning
-Those who just want to modify shipped ROMs or someone else's custom ROMs to their liking
-Those who are confused by all those scripts and complex commands required for building and extracting
Please note:
-The kitchen will not automatically turn you into a developer. A developer is someone who writes code or builds something from the ground up and understands exactly what goes on behind the scenes. The kitchen hides all that and puts a user-friendly interface above it. However, this may be the push that gets you into development in the future.
My goal is to give you the tools to make your life easier and save you lots of time, and at the same time help you learn about the Android OS.
A little bit of prior UNIX command-line knowledge would be useful to get started with the kitchen, but the help guides should be enough for a newbie. Knowledge of command lines is always important if you ever want to get involved in Android or development.
Code:
===========================================================
Android Kitchen - by dsixda (xda-developers.com)
===========================================================
Main Menu
1. Set up working folder from ROM
2. Add root permissions
3. Add BusyBox
4. Disable boot screen sounds
5. Add wireless tethering
6. Zipalign all *.apk files to optimize RAM usage
7. Change wipe status of ROM
8. Change name of ROM
9. Check update-script for errors
10. Show working folder information
Advanced Options
11 - Deodex files in your ROM
12 - Add task killer tweak for speed (stock ROM only)
13 - Add /data/app functionality
14 - Add Nano text editor + sysro/sysrw
15 - Add Bash (command shell)
16 - Add Apps2SD
17 - Add /etc/init.d scripts support (busybox run-parts)
18 - Add custom boot animation functionality
19 - Porting tools (experimental)
20 - Tools for boot image (unpack/re-pack/etc.)
21 - Unpack data.img
22 - Sign APK or ZIP file(s)
23 - Convert update-script or updater-script
24 - Miscellaneous optins / Plugin scripts
99. Build ROM from working folder
00. About/Update kitchen
x. Exit
How To Install Kitchen?
1. Install latest Java JDK. It's pretty simple just follow the instructions and you are done.
2. Download and Extract Cygwin Packages and Android Kitchen on your desktop or somewhere easy to
access.
3. Once extracted go through kitchen_readme.txt and you will get an overview of how to setup the
kitchen.
4. To begin, install Cygwin first. So, run setup.exe from the extracted files and go through the installation
process.
5. Run Cygwin.exe once and it will create a folder with your username on /home/ directory.
6. Navigate to the folder where you installed Cygwin and go inside .../ home// folder.
7. Copy the extracted kitchen folder to this location.
8. Once copied, rename it to kitchen (type all letters in lower case for Linux is case sensitive).
9. Run Cygwin.exe and navigate to kitchen folder. for that simply type the command cd kitchen and press Enter
10. Once inside kitchen folder, type ./ menu to run android kitchen. Note: if you get a permission denied error then type chmod +x menu or chmod 777 menu in Cygwin command line utility first and then only run the command ./menu .
11. You will be presented with the Android Kitchen menu seen above. Use these options and get started. That's all. You have successfully installed android kitchen on your PC. Though this is originally meant for only HTC based roms some of it's features will come handy for modding Samsung Roms too. Please note that because of the same reason all the functions/features of Android Kitchen may not work for you.

Wow. Why did you copy and create a new thread and paste it? Why? Don't we have enough spam already?

EDIT: I don't see the point of this. Couldn't just share a link to the thread?

Interesting.
Thanks!
Sent from my Xperia™ PLAY using TapatalkHD

Lol. Nah, I think I will just stick with good ol' Linux and good ol' terminal and gedit (the proper way )
Sent from my E15i using XDA

Aha!!!
This is what i need... Great! Thankx

Nice info

Creating Custom ROM For Xperia 2011 Device
SatrioDwiPrabowo said:
Nice info
Click to expand...
Click to collapse
Is there any guide how to make custom rom for 2011 device like : Xperia Ray .. ???

engkozhe said:
Is there any guide how to make custom rom for 2011 device like : Xperia Ray .. ???
Click to expand...
Click to collapse
Use dsixda for basic tools rest you do whatever you want theme it add scripts do whatever you want !
Sent from my HTC Explorer A310e using xda premium

Ok. Tnx
Sent from my ST18i using xda app-developers app

I got stuck on services.odex n i cant get the classes.dex file, how can i deodex. Odex n put it on jar file? Tnx
ST18 with custom kernel

engkozhe said:
I got stuck on services.odex n i cant get the classes.dex file, how can i deodex. Odex n put it on jar file? Tnx
ST18 with custom kernel
Click to expand...
Click to collapse
To deodex ROMs use the option in Kitchen for it!
Sent from my HTC Explorer A310e using xda premium

Oh... One more question, can we put apk directly to system folder on cygwin? And how do you create credit on updater script?? Thank you
Sent from my ST18i using xda app-developers app

engkozhe said:
Oh... One more question, can we put apk directly to system folder on cygwin? And how do you create credit on updater script?? Thank you
Sent from my ST18i using xda app-developers app
Click to expand...
Click to collapse
You can add apps in /system/app or /data/app
But if you add in data you will have to create appropriate lines in updater script!
Sent from my HTC Explorer A310e using xda premium

Interesting.

...

updated

[Guide][HOW TO]Install a GNU/Linux and tools to make Custom ROMs

HOW to install a distribution of GNU/Linux and configure the necessary tools for the development of ROMs
Autores: TugaPower aka danieldmm e porfirio
Firstly, it is important to say that GNU/Linux is open source software / free, robust, reliable, free and easy installation for any user, even if you have few computer skills.
There are dozens of distributions of GNU/Linux, all available free at: http://distrowatch.com/, so choose that of your choice and according to the hardware capabilities of the machine will be installed where the distribution chosen by you.
The choice of authors this "HOWTO" is based on the distribution of GNU/Linux, Ubuntu 11.10, with the XFCE desktop environment and also the GNOME desktop environment. This is abolished by default the manager's main Gnome desktop environment and in its place put XFCE, to perform the daily tasks of work, which is very lightweight and fast. Or if they want to be more direct, Xubuntu and will soon install from scratch, which will get the same results. Personally, I'm a fan of this graphical environment (XFCE), attending to its lightness, speed, customization, etc..
What will be explained in this HOWTO:
1. Install Ubuntu or any other distribution, such as: Xubuntu, manager native XFCE desktop environment, Kubuntu, manager native KDE graphical environment; Lubuntu, manager native LXDE graphical environment, which uses less hardware resources on the machine all present in this work. Basically, we are always talking about Ubuntu, what changes is only the GUI (Graphic User Interface), where the user goes to work.
2. The process of installation and basic configuration for any of these variants, it is always the same.
3. Do not expect to find in this work, the whole process complete installation and configuration. Only the main roads and where possible, with visual aids. However there are situations so redundant, that does not need that same help. Not the purposes of this HOWTO, other possible configurations, eg setup SAMBA, APACHE, a home FTP server, desktop, etc..
4. Let's begin as follows:
4.1 Installing Ubuntu on dual boot with WIndows 7 via USB Universal Installer;
4.2 From the field 16 is a normal installation via live DVD of Ubuntu (Xubuntu, Kubuntu, Edubuntu, Lubuntu).
4.3 Installing and configuring the basic tools for the development of ROMs for the Android operating system (smartphones) on GNU/Linux.
4.4 Some illustrative examples of these tools in place to obtain "cooked," ready to use for users.
GETTING STARTED
1. Installing Ubuntu on dual boot with WIndows 7 via USB Universal Installer.
1.1 To start this process, you must be made to download an image of the Ubuntu operating system for the machine architecture, or x86 (for CPU 36 bit) or x64 (for 64-bit CPUs).
1.1.1 However, this day, there is some controversy on this subject. Some say that if the machine has 4GB of RAM or more, we always use the 64 bit version, even if the CPU is x86 and also say that if the machine has less than 4GB of RAM, we use the 32 bit version regardless of the CPU is x36 or x64.
NOTE: Rarely, modern computers, whether desktops, laptops, at least have at least 4GB of RAM standard. However, do not relinquish that each CPU (x86 or x64), must have the OS corresponding to your architecture. Therefore it is up to each one choose the best option.
2. ISO Images
2.1 Ubuntu 02.01 11.10 (32bit)
2.2 Ubuntu 02.02 11.10 (64bit)
3.Universal USB Installer
3.1 Now we do download the appropriate version of the distribution, we will have to download the USB Installer: www.pendrivelinux.com/downloads/Universal-USB-Installer/
But what is the purpose of this installation process?
3.2 Firstly, we can be a machine, you have not installed a drive read / write CD / DVD.
3.3 Secondly, avoid using a CD or DVD drive for installation.
4. Run the USB Installer, as Administrator of the OS and this not to happen errors during the copy of the OS to the thumb drive. This procedure is performed as follows:
- Click on the icon of the program with the button on the right mouse button and select Run as Administrator option.
5. After installing the USB Installer, run the program and click on I Agree.
{
"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"
}
6. Now we set the distribution of GNU/Linux, we will be using. I choose Ubuntu 11.10.
7. Now calm down! I hope you remember where it was saved the iso image of Ubuntu! Only then will the USB Installer will be able to recognize and perform the installation on the pen drive. Will normally be in downloads.
8. Insert the flash drive and expect it to be recognized by Windows. In this case explanation, their location is in F.
9. At this point, we select the Format F: Drive to FAT32.
NOTE: If you wish, can create a little more memory to the pen, in case it is likely to change. This is an optional. If your interest, as it is put in the picture.
Now we have everything configured properly, we will click Creat.
10. At this point you will get a WARNING message. All contents of pen drive will be erased. Click YES and continue.
11. Now it is time for a coffee, etc., etc. and wait for the installation process to complete. After this step, we will be ready for installation on the computer distribution.
11.1 While the above task does not end, we can and must perform other actions, such as creating a partition for the Ubuntu operating system.
11.2 Let's Start Menu;
11.3 Clicking the right-click Computer and then Manage;
11.4 Now on the left menu, click Disk Manager;
Arrived here, the C partition, let's click and select Shrink Volume.
12. Let us wait quietly, and very soon we will be faced with the option to reduce the partition chosen. For a minimal installation of Ubuntu, will require approximately 10 GB. However, if we want to later install the updates, music, videos, etc. ... recommend 25 GB. To be closer to the 25GB, 26GB put!
13. The next step is to reduce and click new partition will be marked in black. We will then activate this partition:
13.1 Click on the partition, with the right mouse button and select New Simple Volume.
13.2 Click Next> Next> and choose a letter to the new drive (eg U).
13.3 Now let's change the Volume Label. Put Ubuntu.
13.4 Next Run. We have created the partition and active.
NOTE: Wait now that Universal USB Installer program in the following screen appears indicating that the installation was completed and then click Close.
14. Restart the computer.
15. Immediately press F12 and select USB stick and then press ENTER.
15.1 will appear something like this:
Calm ..... very quiet .... Choose the option Install Ubuntu on a Hard Disk.
16. Now it is like to install via DVD, which I dispense to comment on "How to install Ubuntu 11.10 per DVD." See 4.2 The field from the field 16 is a normal installation of Ubuntu live via DVD.
16.1 After appearing Choose Setup Language, Portuguese choose and click Next. (You pick the language that you anderstand)
Preferably, you must have a fast Internet connection, so that the OS be upgraded soon. In the situation of not being currently available internet connection, do not put the "seen". No problem your installation will proceed smoothly. You can do it later.
17. Then will click on: One more thing, in order to choose the partition for installation.
18. CAUTION ... CAUTION!
18.1 In this field, we have all the possible CARE! The Windows partition can die!
18.2 Should be selected before the partition created in Windows (which is named Ubuntu), and then click Modify. After selecting the partition that was created on Windows (Ubuntu). In the new partition size, and put 21,000 Mount Point select /. After running OK.
The aspect should be this:
19. Now let us take the remaining space in the example 1490MB. Click Modify, and followed by the option Use as we choose and swap area and click OK.
It should be something like this:
20. Next, click Install Now and wait ......
21. Choose the location of the user:
22. Now the installation of the default keyboard ....
23. Enter personal information and click Continue.
24. Installation completed. Reboot the PC.
25. And Behold .....
Choose from the boot menu option Ubuntu .... There is also the option Windows ... Choose!
26. I chose .... Ubuntu with the Gnome GUI!
7. There is a method, also very reliable, to expedite this process, but directed to Mint distribution, which can be obtained here: community.linuxmint.com/tutorial/view/744
NOTE: TugaPower friend and colleague, will use the Mint 12 in the process of compiling ROMs. (In this case S2 i9100 ROM 4.0.3 ICS)
Version used: Linux Mint x64 12 vKDE
Download Links: http://blog.linuxmint.com/?p=1927
4.3 Installing and configuring the basic tools for the development of ROMs for the Android operating system (smartphones) on GNU / Linux.
4.3.1 Installing the JAVA
Open the Synaptic package manager and install the openjdk-7-jdk and mark their dependencies:
Approval for the changes made​​:
Download the required files:
Installation of the necessary files and OpenJDK 7:
Now we have to install JAVA on the machine fully realized, we will proceed to their inspection.
To do so open the command line terminal to write the following command: java-version
4.3.2 Check if the package is installed 7zip more specifically p7zip-full, if not select for installation:
Once this is done we can then proceed with the installation of the Kitchen.
4.4 Installing the Kitchen
4.4.1 Initial Procedures
All information to carry out this section were collected on: forum.xda-developers.com/showthread.php?p=5626292#post5626292
Therefore, our choice falls on dsixda Android's Kitchen (Support Several devices)
(The Custom ROM made in this Guide its based to the Galaxy S2 i9100)
Download link of Kitchen: http://github.com/dsixda/Android-Kitchen/archives/master
Informational Page on Kitchen: http://forum.xda-developers.com/showthread.php?p=5626292#post5626292
After these preliminary procedures have been performed, we proceed to next steps.
By default, you will be allocated in the Downloads folder files.
4.4.2 Click on the file up with the right button of mouse and perform the extraction of the file to the Downloads folder:
4.4.3 Change the file name for kitchen (it's easier to work).
4.4.3.1 Move or Copy to folder or Personal Home:
They should stick with a structure like this:
4.5 Perform download the ROM Stock
NOTE: I personally recommend two sites:
http://forum.xda-developers.com/showthread.php?t=1075278
http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=GT-I9100&r=1#regional
Download the ROM to be used in Kitchen, in this case we use the XDA, specifically the XWLP7:
NOTE: The screenshot references XWLP4 because at that time had not XWLP7
4.5.1 Download the kernel corresponding CF-root (This way remains CWM Recovery Busybox and SuperUser GB, if ICS SuperSU depends the kernel used to cook the ROM.
4.5.2 Download the kernels on CF-root: http://forum.xda-developers.com/showthread.php?t=1103399
NOTE: This case will be used the latest available to ICS, the CF-root-SGS2_XX_OXA_LPS-v5.4-CWM5.zip
NOTE: It is already available in the XDA KERNEL CF ROOT XWLP7.
4.5.3 Copy the file from the ROM inside the Kitchen to the folder original_update
4.5.3.1 If the file is in the form *******. Tar.md5 have to remove the. Md5 so that it only ********. Tar
After these steps have been made ​​in all its fullness, then we have all the necessary files to start our cooked
4.5.4 Some illustrative examples of these tools in place to obtain "cooked," ready to use for users.
4.5.4.1 In order to run our furnace we have run the Kitchen in a command line also known as terminal or console, for it will open a command prompt within the folder Kitchen:
In order to execute the Kitchen just run the following command as root sudo. / Menu in the terminal:
6. First thing to do is point 1 or set a folder where we work. In this process the Kitchen will get to select and give the stock ROM original_update previously placed in the folder, simply enter the next screen and then select the ROM list:
Therefore, we select the first option because we only have a ROM in the kitchen, so just to enter a default because it's one
6.1 In the kitchen will then ask if we want to keep the name.
This name stock is organized as follows: WORKING_DATA_HORA, this can be changed to whatever you want, the only thing required is to keep the WORKING_
In this case I press the button to change the name ye WORKING_XWLP7_TugaPower:
To continue then just press Enter.
7. The kitchen will start the process of extracting the file from the ROM to the folder with the name we gave earlier WORKING_ ********
In this process we have to decide if we want to use the CSC (NET configuration and applications) that are included with the Stock ROM or NO.
By default this is set to YES ...
Thus, we can, because the Kitchen gives the following list of apks existing CSC and if we add the folder WORKING_ *****
Remember that in most cases, there is no problem in using the CSC Stock ROM, just advise not to use the apks the CSC because they are essentially propaganda NETWORK, which can be set to follow in the next menu to the Kitchen already well default to not add the apks:
Ready to the next step?
8. After the CSC will appear in the information regarding the boot.img, here we select the letter n because for the effect of Custom ROM do not need!
9. Then will come the question if we want to see information about the ROM.
This option is your choice will; default is Y. I personally put n. Now let's return back to the first screen which means that the necessary files are all ready ....
10. In this field, you may want to check whether there is a need to use option 2 and 3.
10.1 In the case of using the KERNEL Stock are advised to do option 2 and 3.
If the kernel you are going to use is for example the CF ROOT or any other that already have root then there is necessary to make the option 1 and 2.
10.2 In this case I will use the CF KERNEL, we will open the zip file of CF ROOT Kernel, find a file ****.tar, opening the file we find the zImage (KERNEL), selecting the zImage we proceed to the extraction process to the working folder of the Kitchen, in this case to the folder: Working_XWLP7_TugaPower
A new window will appear saying that the file already exists, just select and replace the existing ...
11. We will now switch to the Kitchen 7. Kitchen is a default to NO WIPE ROM, option 7 serves to change this ...
12. In this case I do WIPE version, you just will access option 7 in the next field and put y:
12.1 This procedure will eventually lead back to the main menu of the Kitchen. Now we have to think whether we want a ROM or deodexed ODEXED Stock ...
12.2 If we use a version ODEXED we can switch to the option 99 which will be explained below, because I'll use this version deodexed and before passing the option will be option 0 99: ADVANCED OPTIONS
IMG]http://i.imgur.com/XtfZp.png[/IMG]
13. Here I select option 11 to deodexed ROM:
13.1 Now we need one more aspect to consider: what kind of ROM, if GB or ICS.
In this case as I am using a ROM ICS will change the level of API's Kitchen and they default to GB, so I'll use the v
14. Then I confirm that I change the level of the API key y.
In this case I set the API level to 15 which corresponds ROM will be concerned that I'm using ICS 4.0.3:
14.1. Now set the API, I will proceed to the DEODEX ROM for option b, which is advised, because this way, will deodexed the system / app and system / framework.
15. Will be asked if you want a log deodex, this is your charge, if you put y, a file will be created in the root folder of the Kitchen with Deodex process, this log can be used to screen for possible errors that occur in deodexed; I always use the log file because the design is not great and always give way if there are problems in deodexed.
16. After this step made ​​the Kitchen will carry out the relevant technical Deodexed ROM:
17. Now just wait, if you can go for a coffee or a cigarette because it still takes a bit if they do not get any errors and the process goes well deodexed will be presented the following screen:
18. Pressing the Enter, go to the submenu of Kitchen Advanced Menu.
We will then press 0 to return to the main Kitchen; next step we change the name of the build of the ROM (this information that appears in the menu on the About the Phone.
18.1 For this press the key 8 from the Main Menu of the Kitchen, in which case I will change to XWLP7 Stock by TugaPower:
http://i.imgur.com/I6ZXw.png[IMG]
19. Press Enter, then we will change back to the Main Menu Kitchen, now is the time better, create CWM zip file for flashing the ROM :)
19.1 For this we will then press the Option 99:
[IMG]http://i.imgur.com/eYhj4.png
NOTE: Because you are beginning to learn how to make Custom ROMs recommend the first option which is already the default and that the Kitchen, then just do enter in the respective options that appear to the end:
Until we reach the end of file creation can change the name of it, this is the last question that makes the kitchen:
Done this you can find the ROM inside the OUTPUT folder in the Kitchen ...
You only need to copy to the memory of the phone and make the flash.
Have a good cooked and good flash
ROM that was created in TUTU --->
XWLP7 Stock By TugaPower

a hell lot of screenshots, foolproof guide, really great one for beginner

Thanks.. Must have !!

Thanks fool proof, full of screens and has each and every detail.
:thumbup:

randommmm said:
a hell lot of screenshots, foolproof guide, really great one for beginner
Click to expand...
Click to collapse
aditya_7298 said:
Thanks fool proof, full of screens and has each and every detail.
:thumbup:
Click to expand...
Click to collapse
Thanks guys...
Cheers

wow really Great Guide.....................

[Guide For creating custom Rom's]N00B Proof ]

So you heard alot about creating a custom rom how about creating one with ease with this simple guide you will find it easy
So for whom is this guide?
1.Absolute Beginners.
2.People with little or no programming skills
3.people who really want to learn how to make custom rom's
4.people who want to learn android and don't know where to start
Click to expand...
Click to collapse
Tools Required : (Update them manually and report me dead links please)
Java JDK FROM HERE FOR INSTALLING CYWIGN
WARNING: Do not install Cygwin before the JDK!!
Click to expand...
Click to collapse
Cywign Direct Download- Linux Terminal For Windows
Android Kitchen (ROM Development Tool)- For Cooking custom ROM and many more things, Please update this Kitchen to latest version when available.
notepad++ - for editing files like build.prop, updaterscript
MOST IMPORTANT TOOL YOUR BRAIN... AND ALSO LOTS OF TIME...
Click to expand...
Click to collapse
Step one: Installing the JAVA JDK, Cygwin and Setting up the Kitchen
*Before you do anything install the java jdk* (don't skip)
Try this Dsixda Kitchen Install Picture Tutor(recommended)Or
Watch this video guide by gitagaire for how to setup cygwin and kitchen
http://www.youtube.com/watch?feature=player_embedded&v=sYJMdHPD410
Now for the real developing so lets get ready
Click to expand...
Click to collapse
INSTRUCTIONS
1.Download and extract the cygwin_packages.zip
2.Run the set up(make sure there is no previous cygwin installation)
NOTE: INSTALL CYGWIN IN ROOT DISK LIKE C:\
1. Follow the kitchen read me txt!!!
2.Run the set up(make sure there is no previous cygwin installation)
{
"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"
}
Click to expand...
Click to collapse
1.when it shows all the package names, go to the top and select "all default" until it changes to "all install" (you must click on the arrows)
Click to expand...
Click to collapse
1.Download the kitchen from above. Then, extract the kitchen's .zip file to a folder under your home account. Rename the dsixda-android-kitchen-*** folder to just "kitchen". In Cygwin, this folder would depend on what was set for your Cygwin install directory, e.g. C:\cygwin\home\John\kitchen
NOTE!! If your user folder contains spaces (e.g. C:\cygwin\home\John Smith\kitchen), then the kitchen will not function properly. Instead, copy it under C:\cygwin\home\kitchen
1.It's the time now you run the kitchen so follow carefully
2.Run the kitchen and follow
those who have their kitchen like this C:\cygwin\home\John\kitchen use these commands given below.
cd kitchen(enter)
./menu(enter)
Click to expand...
Click to collapse
those who have their kitchen like this C:\cygwin\home\kitchen use these commands given below.
cd ../kitchen(enter)
./menu(enter)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
If every things are right you should have this
congratulations!! you have sucsessfully setup up The kitchen
Click to expand...
Click to collapse

Step Two: Setting up a working folder
THERE ARE TOW METHODS FOR THIS -but i will mention only one for now.
1. WHEN YOU HAVE BASE ROM AVAILABLE.
FIRST METHOD -
1.First our folder structure should look like this:
Code:
cygwin folder/home/your user name/kitchen
1.Inside the kitchen it should look like this:
1. Now we need a base rom for working on, You can any rom but i don't know if it works with stock roms:silly:
Just Place the original rom zip in the original_update folder inside the kitchen.
2.run the cygwin.exe again type:
Code:
cd kitchen(enter)
./menu(enter)
1.now enter option 1, enter again. You should see your rom listed, choose and enter
you will be asked about changing the working folders name, at this point it makes no difference so just continue.
2.congratulations you have a working folder!!!:victory:
Step Two :change/modify/update rom
YOU CAN MODIFY YOUR ROM IN TWO STEPS:
MODIFY USING ANDROID KITCHEN - for basic modification.
MODIFY MANUALLY. - for advanced modification.
1. MODIFYING USING ANDROID KITCHEN
watch this amazing tutorial by neroyoung on how to editing rom with kitchen
NOTE: DON'T FORGET TO DEODEX YOUR ROM
Click to expand...
Click to collapse
2.Modifying manually will be added later on
3.Modifying .9.png's and oter stuff will be added soon saw stay tuned

BUILDING KERNELs​This post includes every thing that helps you develop and make a good kernel for your device
Requirements
1. linux box 32 bit with working gcc. you can use real linux machine or virtual machineOr just simply UBUNTU 10.04 64-bit
2. Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI from http://www.codesourcery.com/ (Linux version without installer arm-2009q3-68-arm-none-eabi-i686-pc-linux-gnu.tar.bz2)
3. mkbootimg with md5support. got it from http://forum.xda-developers.com/show...&postcount=241 . credit to harish2704
4. split_bootimg.pl (google it)
5. kernel source from http://opensource.samsung.com . i use GT-P3100_ICS_Opensource_Update.zip
6. stock boot.img (or from your custom kernel).
Click to expand...
Click to collapse
Setting up the environment & building the kernel for the first time
Ubuntu 10.04 64-Bit (recommended)
Ubuntu 12.04 64-Bit
Note: If you want to use virtualization software, do not use Virtualbox. You can run into networking issues and so on. I suggest using VMWare Player instead, which is available for free on http://www.vmware.com
Steps :
1. make folder "sgy" in your home. the result is folder "/home/<yourname>/sgy". <yourname> is your linux user name, and from now replace <yourname> with your user name. put all file you already download there
2. extract "GT-P3100_Kernel.tar.gz" from "GT-P3100_GB_Opensource_Update.zip". put also in "sgy" folder
3. open terminal emulator and go to your working path with command
Code:
cd ~/sgy
4. extract your compiler with
Code:
tar -xvf arm-2009q3-68-arm-none-eabi-i686-pc-linux-gnu.tar.bz2
5. create folder "kernel" and extract kernel source there
Code:
mkdir kernel
cd kernel
tar -xvf ../GT-P3100_Kernel.tar.gz
you got 2 folder, "common" and "modules"
6. open folder "common", there is file "Makefile". open with text editor and find line with content "/opt/toolchains/arm-eabi-4.4.3/bin/arm-eabi-". replace with "/home/<yourname>/sgy/arm-2009q3/bin/arm-none-eabi-", don't forget replace <yourname>.
7. in terminal goto folder "common" and load default config for sgy
Code:
cd ~/sgy/kernel/common
make bcm21553_totoro_05_defconfig
8. if you want change you config run
Code:
make menuconfig
9. if you ready to build then run
Code:
make
or if you want to make it faster
Code:
make -j3
10. when complete and no error appear, copy your kernel to "sgy" folder
Code:
cp arch/arm/boot/zImage ~/sgy
11. extract ramdisk from your boot.img
Code:
cd ~/sgy/
perl split_bootimg.pl boot.img
you got "boot.img-kernel" and "boot.img-ramdisk.gz". move "boot.img" and "boot.img-kernel" to other place.
12. repack your new kernel and ramdisk. but first get md5sum of your new kernel
Code:
md5sum zImage
you got something like
Code:
1fd319aa60abc2abae2e5932bcb9fc77 zImage
you need that "1fd319aa60abc2abae2e5932bcb9fc77" write it or copy to text editor. you need run it every time compile new kernel
13.Repack
Code:
chmod +x mkbootimg
./mkbootimg --kernel zImage --ramdisk boot.img-ramdisk.gz --base 0x81600000 --kernelMD5 <your md5sum result> -o boot.img
14.And if you want to make an odin flashble
Code:
tar -cf boot-sgy.tar boot.img
Now you've built you'r kernel

reserved For FAQ

UOT Kitchen customization​Hello everyone, today I'm creating this thread for newbies who want to learn how to use UOT Kitchen so it can be used by the Galaxy Tab 2.
It allows us to mod everything in the phone! You can even choose which to mod.
Prerequisites:
- You current ROM's SystemUI.apk, framework-res.apk and twframework-res.apk
The instructions are as follows:
Step 1: Battery mod
Over here, you can change:
Battery icon
Battery charging animation
Battery style
Battery colour parts
Firstly, just choose a battery bar that you like. (I personally prefer the Honeycomb one)
Secondly, choose the charging animation. (Hybrid looks nice)
Thirdly, you can choose to change the colour parts or leave it as it is.
Fourthly, (optional) you can select Additional options:
Remove % numbers
Remove charging icon
Use gradient colour fill
Well, that's all for battery.
Step 2: Icons
Here you can change:
Smiley icons
Status bar icons
Notification Power icons
This doesn't need much instructions; pick what you like.
Step 3: Status bar
This is probably the most important thing when it comes to theming: the Status Bar!
It allows you to change:
Status bar transparency
Top bar
Add/edit top bar text
Add a header
Add/edit carrier
Add a background on the status bar
Customize notifications' colours
Add/edit footer
Firstly, you need to specify your phone's screen resolution size. (Ours is hdpi.)
Secondly, mix-and-match.
Step 4: Popup (a.k.a Window Animations)
This one is just as important.
It allows you to change:
Add/edit overscroll glow
Edit popup windows
Loading circle
Volume/Download bar
Add/edit list dividers
Same thing, mix-and-match.
Step 5: Lockscreen
This allows you to change:
Lockscreen
Step 6: Window
This allows you to change:
Window animations
It allows us to use the ICS windows animation effect!
Step 7: Fonts
This allows you to change:
System fonts
They have 26 fonts to choose, including the famous Roboto font!
Step 8: Bootanimation
This allows you to change:
System bootanimation
They have loads of bootanimations to choose from. Have fun!
Step 9: File upload
This is where you:
Upload system files for modding
Choosing updater-script type
Apply 9patch autofix
Toggle ThemeChooser preview for ldpi/mdpi/hdpi
Allow to download your settings into a UOT Kitchen-openable format
Just upload your system files.
But remember to choose the updater-script type as Galaxy !!!!!!!!!!!!!!
Step 10: Summary
This is where you can check the status of your mods.
Once it's okay, you can submit the work to the kitchen.
Once you submit it, you'll be given a number. That's the name where your file will be processed under and be shown for download at the "Pickup" section.
(Note: If it gives an error instead of a download post it at the UOT thread)
Thanks for reading this small guide, I'll update it with more info!

Credits ​1. Neroyoung for his video tutorials
2.For lokeshsaini94 for his amazing tutorial
3.For irfanbagus and his nice tutorial that i ported to galaxy tab 2
4.For shakatu fo remembering me to credit people thanks Alot!!!!
And any one that Iforgot to mention lol

[DIY GUIDE] Create a personalized ROM yourself! [UPDATED: 28-07-2014]

Introduction
After releasing my 'Update to .253' thread, I've figured it is something you might want to do your self, maybe because you like to use your own created FTF, or even want to modify your ROM a bit before flashing. This guide will help you through it, as secure and successful as possible!
Anyone can do it!
There is no need to unlock your bootloader to work this guide, however it did help me out of some sticky situations myself, as long as you keep a cool head while working on your ROM, you'll be able to get out of any situation.
The XDA mantra: MAKE BACKUPS!
Before you do anything on your phone, make sure you create a solid backup first. As CWM and TWRP both do not backup your internal storage, create a backup of it's contents too before trying to install your very own ROM.
Prerequisites
Flashtool version 0.9.x.x (the latest) - Windows / Linux / Mac
Needed to flash your phone, also needed to create the FTF bundle. The Linux version is already installed in the VM but you can download any other version too, to do the flashing and FTF building before hand in a desktop enviroment you are accustomed to.
[GUIDE] Download ANY firmware customization from Sony & create an FTF with Flashtool
This thread will help you make an FTF file for your DIY project, as we already have this excelent thread I will save myself the trouble of creating a guide for that
VMWare Player (76Mb) (Free for non-commercial use) and [NUT]'s UbuntuHost VM (Bittorrent: 4.84Gb)
The VM you download is OK to use on any 4.1.2 ROM as base.
If you wish to use a 4.2.2 ROM, you will need the DIYGuide UPDATE PACKAGE 1 (Bittorrent: 169Mb).
If you wish to use a 4.3 or 4.4 ROM, you will be needing DIYGuide UPDATE PACKAGE 2 (Bittorrent: 159Mb). Flashtool however needs to be updated to 0.9.15.0 if you are going to build a 4.4 ROM
See the index below for the link to the guide post that explains how to use it.
This you will need for the tricky bits, as modifying a ROM is safer on a Linux host with less chances of breaking file permissions. As most of the world around us uses Windows, I've created a VM to support you in your tasks. I've installed the Linux tools you need, for me this VM works just fine.
The VM needs about 10Gb space on your pc and you need around 1Gb of free RAM when trying to use it smoothly.
This VM also contains a build script, simple but effective, which will create the (unsigned) flashable zip for you, grabbing all the files it needs along the way and giving you time to edit what ever you want during the building process.
I've made sure you have fastboot and adb commands to be found in the PATH variable, and that the connection to most android phones and tablets will most probably work just fine. You can do adb and fastboot commands to your phone without having them in the directory where you keep the files, easy to use!
The VM has one user, which is called XDA Community. To log in on Ubuntu, use the following credentials:
User: xda
Password: xdauser
This user has SUDO privileges, so expect to type that password again when prompted to do so while installing packages or even when running the rombuilder script.
Download and install WinRAR or 7Zip to be able to unpack my VM.
Included in the ROM you will build using this DIY Guide
Your DIY ROM will be rooted with SuperUser (or SuperSU when you used an update package), including the reboot fix. It will also include XZDualRecovery 2.3 RELEASE (or newer if you used an update package). So you will end up with a cool ROM!
Extra's
You will be able to use my AROMA ROM Mutator package to fix your JB 4.1 ROM if anything might fall to pieces in the future regarding root. You'll also be able to use it to make the switch from SuperUser to SuperSU using the mutator, if you might change your mind in the future.
Guide Index
Chapter 1: Introduction and Prerequisites
Chapter 2: Installing VMWare Player and getting 'UbuntuHost' running
Chapter 3: Preparing the FTF for NOOB use
Chapter 4: Preparing and Extracting the ROM
Chapter 5: Building the (unsigned) flashable ZIP
Chapter 6: Installing your DIY ROM
Addendum: How to replace the recoveries to suit your device
Addendum: How to update your VM
Frequently Asked Questions

Installing VMWare Player and getting 'UbuntuHost' running
I'm assuming you have downloaded the VMWare Player application suitable for your system. Installing it is a basic knowledge to most Windows users, so I'm not going to elaborate on the actual installation.
I'm also assuming you have downloaded the VM. You can now unpack it to your Documents folder.
Now, fire up VMware player and when you see the following...
{
"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"
}
Then click on 'Open a Virtual Machine' and navigate to the folder you just extracted:
Click on the UbuntuHost.vmx and confirm the choice. You'll end up with this view:
Now you can either double click on the name in the list on the left or click play on the right to start it.
Remember, the password is xdauser
NOTE: This Ubuntu has the Unity interface which means, among other things, the menus are moved from the application window to the top bar. Move your mouse over it and the menus will appear.
And you are ready for the next chapter!

Preparing the FTF for NOOB use
Why would you do that? Well... to make sure you won't screw up flashing the wrong bits and make it erase your userdata... better safe then sorry!
This step is actually also needed to unpack the system partition from the FTF you created using the guide I put in the OP.
Copy the FTF you created to the VM by dragging the file in to the VM window. You can see Ubuntu recognizes it as a ZIP, which it essentially is.
Open it by double clicking on it.
Now delete userdata.sin, cache.sin and appslog.sin from it. Then drag system.sin to the DIY Guide folder on the desktop. Once it's unpacked, delete system.sin from the FTF as well.
That was easy, wasn't it? Lets move on to the next chapter.

Preparing and Extracting the ROM
Click on the Terminal icon on the left, type 'cd FlashTool' and then './FlashTool'.
NOTE: Use 'sudo' and your password you used to login to run FlashTool as root if you run in to problems.
In the Tools menu, you can select Sin Editor, select the system.sin in your DIY_Guide folder in your home.
Then click 'Extract data' to start the extraction, now go get a cup of coffee, this might take a while
Once it's done you will end up with a file called 'system.ext4' inside your DIY_Guide directory.
Click Close and close FlashTool using the orange X in the top left corner.
You can rename it to something you like but it should end with '.ext4' to allow the scripts to recognize it. Just open up the DIY Guide folder on the desktop and right click on the system.ext4 file and choose 'Rename'. For purpose of demonstration I renamed mine to 'nuts.ext4'
NOTE: The scripts allow for more then one flashable system to be created, so you can repeat the above multiple times, just remember to rename the system.ext4 to something else, otherwise you'll just end up overwriting the same file over and over again
Because of size considerations, the virtual disk is not really big (10Gb) so you'll run out of space fairly quickly, do not forget to empty the trash after this step!
That's it for this chapter, lets move on!

Building the (unsigned) flashable ZIP
Now we can open the Terminal by clicking on the icon on the left with the '>_' sign in the 'monitor'. Change directory to DIY_Guide and type 'ls -la' to show the following
You can start the build process using the rombuilder script by typing './rombuilder' and it will ask you for your password before it starts.
Once it successfully mounts the system partition it will open it for you. The script will pause for you to complete whatever modifications you want to do to it. Remember the XDA Mantra? Well... a backup would be good to make right now.
If you have more then one system.sin extracted, the above process will repeat itself until it passes all the various .ext4 files it has found.
NOTE: The mounted ext4 image has been mounted as root and as the contents are owned by root, you will need to sudo your actions when modifying the contents!
Tip: To make it easy on yourself you can use the terminal to open a file manager running as root. Type ctrl+shift+t, this will open a new terminal tab. In there type 'sudo nautilus' which starts the file manager again, but with an appropriate warning at the top of the explorer window, that one will be running as root. Be careful, you might wreck your entire VM if you mess things up big!
Once you are finished with the modifications or just enter through to the next bit, it will pack up the system partition and repeat or when done it will continue to create a flashable ZIP for each of the different .ext4 files you created.
You're almost done! Lets move to the next chapter...

Installing your DIY ROM
FOR 4.1.2 ROM's:
Before doing these steps, remember to have any recovery installed on your phone if you are doing this with a locked bootloader, otherwise you won't be able to flash the zip you've built!
Put your '$NAME.flashable.zip' on (the external) SDcard;
Put the 'FTF' inside the FlashTool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash everything in the 'FTF' to your phone and boot the phone straight to recovery after that;
NOTE: If you have an unlocked bootloader, you CAN flash the kernel, but you do not need to, to keep your custom kernel.
Flash '$NAME.flashable.zip' in recovery (Works in both CWM and TWRP!)
Reboot to system without clearing (dalvik-/)cache.
And you're done! :victory:
FOR 4.2.2 AND 4.3 ROM's:
Before doing these steps, remember to have any recovery installed on your phone if you are doing this with a locked bootloader, otherwise you won't be able to flash the zip you've built! You will need XZDualRecovery 2.5 BETA or newer to make this work.
NOTE: This guide assumes you are coming from a 4.1.2 ROM. If you have a 4.2.2 ROM already installed, you can skip this one and use the above guide.
Put your '$NAME.flashable.zip' on (the external) SDcard;
Put the 'FTF' inside the FlashTool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash '$NAME.flashable.zip' in TWRP, then TURN YOUR PHONE OFF AFTERWARDS - DO NOT BOOT IT YET!
Flash everything in the 'FTF' to your phone;
Now boot to system without clearing (dalvik-/)cache.
And you're done! :victory:

Addendum: How to replace the recoveries to suit your device
Download XZDualRecovery specific for your device, the flashable package to be precise.
Drag the file to the VM window and open the zip. You will see 2 folders in there, traverse in to system/bin where you will see the files you need most.
Open the DIY_Guide on the VM's desktop, traverse to updater/system/bin and drag all the files from the zip in to this directory, replacing all the files already in your VM and you are set to go
On the Xperia Z Ultra, Z1 Compact, Z1 and (Tablet) Z2, don't forget to copy the disableric file from the tmp folder inside the recovery zip to the updater/system/xbin folder. Forgetting to do so will cause your system partition to be not fully accessible from the fully booted ROM.
For completeness, you could copy the dr.prop file inside the zip to the updater directory too: this will ensure people downloading your package will know what XZDR version was included.

Addendum: How to update your VM
The update package 1 contains the following:
FlashTool 0.9.11.0
XZDualRecovery 2.5 BETA
The Remount-Reboot fix
Superuser has been replaced by SuperSU
IMPORTANT NOTE: This update makes your flashable ZIP assume you are updating from a 4.1.2 ROM to a 4.2.2 ROM. So the resulting flashable ZIP will move the contents of your internal storage to the new 4.2.2 location. If you are creating a package to go from a 4.2.2 ROM to a 4.2.2 ROM, you will need to edit the updater-script to stop it from doing that
Code:
ui_print(" Moving contents of the internal storage to it's new location...");
ui_print("");
ui_print(" NOTE: This may take a while!");
ui_print("");
run_program("/sbin/busybox", "mv", "/data/media", "/data/temporary");
run_program("/sbin/busybox", "mkdir", "/data/media");
run_program("/sbin/busybox", "mv", "/data/temporary", "/data/media/0");
set_progress(0.850000);
Remove the above portion from updater/META-INF/com/google/android/updater-script using gedit and you're set! :fingers-crossed:
The update package 2 contains the following:
Flashtool 0.9.13.0
SuperSU 1.86
XZDualRecovery 2.7.62.
How to update:
Download the update package from the link in the OP;
Open the Home directory in the VM on the bar on the left;
Drag the file in to the home directory straight from your host PC's location where you stored the downloaded package;
Remove the FlashTool and DYI_Guide folders or rename them (to rename, right click on them to get the menu with the rename option);
Now open the diyvm-update.tar.gz, drag the 2 folders in to the Home directory.
All done! :good:

Frequently Asked Questions
Q: Could I use this for any other Xperia device?
A: Sure you can! The proof is starting to pop up now and then
Just make sure you put in the right recovery pieces to support your specific device
Q: Am I allowed to release my ROM to the public?
A: Of course! I only require a simple mention or a humble thank you in your topic, where ever that may be. I like to know where my work travels to, so post or PM me the links to it
Q: Am I allowed to change the updater script to suit my needs?
A: You are allowed to change whatever you wish, I have NO copyright or license stuck to my work, simply because I consider anything with a license or copyright not to be 100% pure open source.
Q: I would like to make a ROM for my device, but there is no XZDualRecovery for it?
A: Try to integrate a recovery package available for your device. You can of course also request XZDR support, but it can take some time before that happens.
Q: I want to expand the storage capacity of the VM, is there any guide for that?
A: Yes, @gregbradley posted one here.
Q: My VM disk is slowly filling up, while I am keeping the trash empty, how come?
A: @GavTheStoner found out why, read his post on the subject and the solution he found.

Would be very useful! Thank you for the nice and clear guide!
Could you please also provide the script and other files needed such recovery etc. ? The whole VM image is large...

Fishmanzero said:
Would be very useful! Thank you for the nice and clear guide!
Could you please also provide the script and other files needed such recovery etc. ? The whole VM image is large...
Click to expand...
Click to collapse
No
It's not hard to find parts in my releases...
Sent from my C6603 using xda app-developers app

Great guide! Thanks a lot for this!
Gesendet von meinem Xperia Z via Tapatalk

Don't suppose anyone's come up with a way to rebuild to FTF?
Would love to be able to do that and just load with FlashTool.

Johbremat said:
Don't suppose anyone's come up with a way to rebuild to FTF?
Would love to be able to do that and just load with FlashTool.
Click to expand...
Click to collapse
Me too, but unfortunately that's just impossible... Sorry
Sent from my C6603 using xda app-developers app

Great Guide
Thanks for sharing - I was able to create my own deodexed and zipaligned 10.1.1.A.1.307 firmware. I tweaked it a bit so it doesn't reboot when changing system to R/W.
Next I'll try creating one for the Japanese 10.1.D.0.343 build

I was able to create a working 10.1.D.0.343 build for the SO-02E variant using your guide. Is it cool with you if I upload it and share it for our Japanese friends? I'll give you credit of course. :good:

lancebukkake said:
I was able to create a working 10.1.D.0.343 build for the SO-02E variant using your guide. Is it cool with you if I upload it and share it for our Japanese friends? I'll give you credit of course. :good:
Click to expand...
Click to collapse
Of course you can
If I didn't want you to release it to the public I'd have that explicitly stated in the OP ... which I haven't, so go right ahead! :good:
--- ON A DIFFERENT NOTE ---
I'll be updating the VM soon to reflect the changes in the updater script, the remount-reboot fix and the latest XZDualRecovery.
I'll also make a tar archive with a little guide in one of the reserved posts to help you update your VM so you won't have to download it all over again

Thanks!
But its possible to create a ROM out of a CWM Backup on Windows.. I.E. thats more simple
Thanks for the VM though

jader13254 said:
Thanks!
But its possible to create a ROM out of a CWM Backup on Windows.. I.E. thats more simple
Thanks for the VM though
Click to expand...
Click to collapse
I know it is, but that is basically a TAR backup and requires a few extra steps: flashing the FTF to your phone, then booting to recovery to make that backup, dragging that to your PC and stripping the META info from the nandroid backup process adds to the TAR (which makes it a non-standard tar archive!) and you still risk losing all permissions and ownership information on the files inside the archive when extracting that to integrate it in your flashable zip... which is a ZIP and does not know about the extended file permissions and ownership from a Linux system... so you will have to make your updater-script reset permissions or instruct your users to do so using recovery... :silly:
Using this VM and my method of using the SIN file to extract a ROM prevents a huge heap of possible issues and keeps the updater-script nice and small and the installation a breeze

[NUT] said:
I know it is, but that is basically a TAR backup and requires a few extra steps: flashing the FTF to your phone, then booting to recovery to make that backup, dragging that to your PC and stripping the META info from the nandroid backup process adds to the TAR (which makes it a non-standard tar archive!) and you still risk losing all permissions and ownership information on the files inside the archive when extracting that to integrate it in your flashable zip... which is a ZIP and does not know about the extended file permissions and ownership from a Linux system... so you will have to make your updater-script reset permissions or instruct your users to do so using recovery... :silly:
Using this VM and my method of using the SIN file to extract a ROM prevents a huge heap of possible issues and keeps the updater-script nice and small and the installation a breeze
Click to expand...
Click to collapse
I just used a nice tool called "yaffey" which keeps the file structure and I set permissions via updater-script.
Works really fine but may be more difficult
Reall great way though and big thanks for this guide

[Magisk 15.3] [android-x86] [Phoenix-os 2.5.7] [systemless root and much more ]

{
"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"
}
​
Latest Stable Magisk Version: v15.3
Latest Magisk Manager Version: v5.5.5​Installing Magisk will give you ROOT, a super powerful Systemless Interface,
Magisk Modules support, and hide from tons of integrity tests like SafetyNet!​Magisk only modifies the boot image and install files to /data and /cache
Your /system partition will only be modified if root is installed in /system, or using custom rom with addon.d support!
This Guide has been deprecated,Try Post#7
Before Proceeding , Beware that after this modification ,you will loose ALT+F1 TTY shell completely and you will only get back that after restoring original ramdisk.img.Mirroring System Image is still not working .So Limited Function
Requirements:
1.Linux OS or Windows OS (optional)
2.Phoenix_OS or any Android-x86 based Distro
3.Magisk Manager App
Installation Instructions
1.In Linux OS
Download android-tools-mkbootimg ,abootimg packages
For Debian Based Distros:
Code:
sudo apt install android-tools-mkbootimg abootimg
Copy ramdisk.img and kernel from Phoenix os iso and put in Home Directory
Now put these commands in terminal
Code:
mkbootimg --kernel kernel --ramdisk ramdisk.img --output boot.img
Copy generated boot.img somewhere you can access in Phoenix OS
2. Now boot into Phoenix OS and Download Latest Magisk Manager from Official Github Repo
3. Now open Magisk Manager and Tap Install
Choose Patch boot.img
Select boot.img generated earlier
Now ,it will save patched img in /sdcard/MagiskManager/patched_boot.img
Save it somewhere again where you can access it in Linux OS
Go to ALT+F1 (ALT+Fn+F1) TTY and run these codes
Code:
cd /system/xbin && mv su su.bak
4. Go into Linux OS :
Open Nautilus and copy patched_boot.img in Home Directory
Now open terminal and enter these :
Code:
abootimg -x patched_boot.img
It will generate kernel and initrd.img file in Home directory
Rename initrd.img to ramdisk.img and replace with original ramdisk.img in Phoenix OS Installation Directory
5.Cool! Its Done ,Check Magisk Manager to confirm Root Access and Enjoy Magisk Latest features.
6.For Windows OS users ,check Sir [email protected] Android Kitchen thread for extracting and recompiling boot.img .
Further for sole Androidx86 users check CNexus thread .
Downloads:
I have done one for Phoenix OS 2.5.7 .see attachment ,backup original one and replace it.
This method will work for Any Android-x86 Distros like Bliss-x86 , LOS-x86 etc.
Credits:
topjohnwu
osm0sis
Ifom
Android-x86 Developers
PhoenixOS Team

Hello,
WONDERFUL GUIDE ! Thanks !
I've just manage to get PheonixOS onto Tesco connect 7" - which was hard, since no guide in the web for that cheap tablet.
few question for you:
1. have you done that on pheonixOS based on nougat or MM ?
( i've installed nougat - hope it is compatible )
2. have you mange to use magisk Xposed ( as a module ) onto this type of installation of magisk ?
( hope you can... since that's why I want to use magisk ).
did you manage

gps3dx said:
Hello,
WONDERFUL GUIDE ! Thanks !
I've just manage to get PheonixOS onto Tesco connect 7" - which was hard, since no guide in the web for that cheap tablet.
few question for you:
1. have you done that on pheonixOS based on nougat or MM ?
( i've installed nougat - hope it is compatible )
2. have you mange to use magisk Xposed ( as a module ) onto this type of installation of magisk ?
( hope you can... since that's why I want to use magisk ).
did you manage
Click to expand...
Click to collapse
1.There is no mm release of phoenixOS ,btw for Lollipop ,you can try .it should work
2.Nope lomount is still not working ,limited system tweaks @topjohnwu still silent

Camlin3 said:
Download android-tools-mkbootimg ,abootimg packages
Click to expand...
Click to collapse
Where can I find those two files? I'm using Windows 10, but working through cygwin64, I can do it following Linux steps, but couldn't find yet abootimg and I think that I have a wrong mkbootimg file if it needs to be named android-tools-mkbootimg and not just mkbootimg.

DaniDeVega said:
Where can I find those two files? I'm using Windows 10, but working through cygwin64, I can do it following Linux steps, but couldn't find yet abootimg and I think that I have a wrong mkbootimg file if it needs to be named android-tools-mkbootimg and not just mkbootimg.
Click to expand...
Click to collapse
Sorry to say but ,i dont use Windows btw you can try linux subsystem in Windows 10 or just try this guide ,it seems solved system mirroring issue . http://bbs.phoenixstudio.org/cn/index.php?m=3g&c=read&tid=14288&fid=12&page=1

2.5.9
Does this also work for 2.5.9?

Works perfect for Windows users. This would help more people with same issues.
Camlin3 said:
Sorry to say but ,i dont use Windows btw you can try linux subsystem in Windows 10 or just try this guide ,it seems solved system mirroring issue . http://bbs.phoenixstudio.org/cn/index.php?m=3g&c=read&tid=14288&fid=12&page=1
Click to expand...
Click to collapse
IT WORKS PERFECTLY!!! THANKS!!!
At this point, I thought that I could help you in this post, so I'll paste here the a simply traduction of the website you linked me. It should be perfect to add beyond the guide you wrote too. So you can review this and post if you find this usefull like it was to me in Windows.
--------------------------------------------
[Magisk v15.3 installation tutorial] for Phoenix OS based on Android 7.1
Follow steps from the OS given in initial subparts of this guide:
__
DO THIS WORKING FROM INSIDE OF Phoenix OS
1. Download Magisk.zip file and extract to /sdcard (built-in storage)
2. Now, inside the extracted folder, open the folder common and install the file magisk.apk
3. When installed, open terminal by pressing "Alt + F1" (remember that to exit from terminal just need to press "F7" or "Alt + F7")
Respect always the spaces when writting into terminal.
3.1 - Write this cd /sdcard/Magisk and press enter
3.2 - Write the following points depending of your system and press enter
REMEMBER: Follow just the point a or b depending if your Phoenix OS is 32 bits (a) or 64 bits (b) but JUST a or b, NEVER both.
3.2.a - sh script32
3.2.b - sh script64
3.3 - Restart to your other OS (Windows, Linux, ...)
__
__
DO THIS WORKING FROM OUTSIDE OF PHOENIX OS (working on Windows, Linux, ...)
4. Go to the folder where Phoenix OS is installed and replace the following files:
(Personally, I always prefer to first copy the original files into another folder to invert this work if any problem happen, but it should work always without any kind of issue)
4.1 - Replace initrd.img with the file initrd.img found into the common folder
4.1.a - if your Phoenix OS is 32-bits: Replace ramdisk.img with ramdisk.img found into the x86 folder
4.1.b - if your Phoenix OS is 64-bits: Replace ramdisk.img with ramdisk.img found into the x64 folder
Note: "Alt + F1" terminal won't be available after replacing initrd.img
__
At this point, Magisk is full installed and you're now ready to install every module suitable for your Android x86/x86_64 kind of version from Magisk Manager App.
--------------------------------------------

@DaniDeVega ,
I can only link works of others,but you posted the same ,so i don't think ,i have to do any thing else .

Jpalmer82 said:
Does this also work for 2.5.9?
Click to expand...
Click to collapse
Yess

Camlin3 said:
@DaniDeVega ,
I can only link works of others,but you posted the same ,so i don't think ,i have to do any thing else .
Click to expand...
Click to collapse
Yes, so I just did a little traduction of the chinese link you gave me, so I don't know yet if post this here (with or without mentioning the owner of the work) is forbidden or not on XDA.
If so, then, I would like to talk with a high rank member to explain and find any kind of way to let this be on xda too. :fingers-crossed:
This translation could help here so many people who would be with the same kind of issues to install Magisk on Phoenix OS that I found until finally you told me to review the link that gets me the solution, and I translate, just like a very helpful suggestion. :good:

DaniDeVega said:
IT WORKS PERFECTLY!!! THANKS!!!
At this point, I thought that I could help you in this post, so I'll paste here the a simply traduction of the website you linked me. It should be perfect to add beyond the guide you wrote too. So you can review this and post if you find this usefull like it was to me in Windows.
--------------------------------------------
[Magisk v15.3 installation tutorial] for Phoenix OS based on Android 7.1
Follow steps from the OS given in initial subparts of this guide:
__
DO THIS WORKING FROM INSIDE OF Phoenix OS
1. Download Magisk.zip file and extract to /sdcard (built-in storage)
2. Now, inside the extracted folder, open the folder common and install the file magisk.apk
3. When installed, open terminal by pressing "Alt + F1" (remember that to exit from terminal just need to press "F7" or "Alt + F7")
Respect always the spaces when writting into terminal.
3.1 - Write this cd /sdcard/Magisk and press enter
3.2 - Write the following points depending of your system and press enter
REMEMBER: Follow just the point a or b depending if your Phoenix OS is 32 bits (a) or 64 bits (b) but JUST a or b, NEVER both.
3.2.a - sh script32
3.2.b - sh script64
3.3 - Restart to your other OS (Windows, Linux, ...)
__
__
DO THIS WORKING FROM OUTSIDE OF PHOENIX OS (working on Windows, Linux, ...)
4. Go to the folder where Phoenix OS is installed and replace the following files:
(Personally, I always prefer to first copy the original files into another folder to invert this work if any problem happen, but it should work always without any kind of issue)
4.1 - Replace initrd.img with the file initrd.img found into the common folder
4.1.a - if your Phoenix OS is 32-bits: Replace ramdisk.img with ramdisk.img found into the x86 folder
4.1.b - if your Phoenix OS is 64-bits: Replace ramdisk.img with ramdisk.img found into the x64 folder
Note: "Alt + F1" terminal won't be available after replacing initrd.img
__
At this point, Magisk is full installed and you're now ready to install every module suitable for your Android x86/x86_64 kind of version from Magisk Manager App.
--------------------------------------------
Click to expand...
Click to collapse
This method works on 2.6.2 but How can I update Magisk?
And None of the modules that I have tried get enabled after rebooting
Update: Any module that has an app it requires you to install the app separately all other modules work fine

Hello, how to update pls :silly:

after the installation the internet was working, but after reboot, the internet stopped working, even configuring an static ip.
I'm using a desktop with wired cable and I don't have wireless network card
1.5.0 x86 Phoenix OS
Sorry for my bad english and sorry for posting here.

Hi ,the tools you mentioned I didn't find on CentOS, could you please give a repo address or direct RPM address? Thanks.

Does this method work in other android-x86? cm-14 r1, bliss etc?,
DaniDeVega said:
IT WORKS PERFECTLY!!! THANKS!!!
At this point, I thought that I could help you in this post, so I'll paste here the a simply traduction of the website you linked me. It should be perfect to add beyond the guide you wrote too. So you can review this and post if you find this usefull like it was to me in Windows.
--------------------------------------------
[Magisk v15.3 installation tutorial] for Phoenix OS based on Android 7.1
Follow steps from the OS given in initial subparts of this guide:
__
DO THIS WORKING FROM INSIDE OF Phoenix OS
1. Download Magisk.zip file and extract to /sdcard (built-in storage)
2. Now, inside the extracted folder, open the folder common and install the file magisk.apk
3. When installed, open terminal by pressing "Alt + F1" (remember that to exit from terminal just need to press "F7" or "Alt + F7")
Respect always the spaces when writting into terminal.
3.1 - Write this cd /sdcard/Magisk and press enter
3.2 - Write the following points depending of your system and press enter
REMEMBER: Follow just the point a or b depending if your Phoenix OS is 32 bits (a) or 64 bits (b) but JUST a or b, NEVER both.
3.2.a - sh script32
3.2.b - sh script64
3.3 - Restart to your other OS (Windows, Linux, ...)
__
__
DO THIS WORKING FROM OUTSIDE OF PHOENIX OS (working on Windows, Linux, ...)
4. Go to the folder where Phoenix OS is installed and replace the following files:
(Personally, I always prefer to first copy the original files into another folder to invert this work if any problem happen, but it should work always without any kind of issue)
4.1 - Replace initrd.img with the file initrd.img found into the common folder
4.1.a - if your Phoenix OS is 32-bits: Replace ramdisk.img with ramdisk.img found into the x86 folder
4.1.b - if your Phoenix OS is 64-bits: Replace ramdisk.img with ramdisk.img found into the x64 folder
Note: "Alt + F1" terminal won't be available after replacing initrd.img
__
At this point, Magisk is full installed and you're now ready to install every module suitable for your Android x86/x86_64 kind of version from Magisk Manager App.
--------------------------------------------
Click to expand...
Click to collapse

DaniDeVega said:
IT WORKS PERFECTLY!!! THANKS!!!
At this point, I thought that I could help you in this post, so I'll paste here the a simply traduction of the website you linked me. It should be perfect to add beyond the guide you wrote too. So you can review this and post if you find this usefull like it was to me in Windows.
--------------------------------------------
[Magisk v15.3 installation tutorial] for Phoenix OS based on Android 7.1
Follow steps from the OS given in initial subparts of this guide:
__
DO THIS WORKING FROM INSIDE OF Phoenix OS
1. Download Magisk.zip file and extract to /sdcard (built-in storage)
2. Now, inside the extracted folder, open the folder common and install the file magisk.apk
3. When installed, open terminal by pressing "Alt + F1" (remember that to exit from terminal just need to press "F7" or "Alt + F7")
Respect always the spaces when writting into terminal.
3.1 - Write this cd /sdcard/Magisk and press enter
3.2 - Write the following points depending of your system and press enter
REMEMBER: Follow just the point a or b depending if your Phoenix OS is 32 bits (a) or 64 bits (b) but JUST a or b, NEVER both.
3.2.a - sh script32
3.2.b - sh script64
3.3 - Restart to your other OS (Windows, Linux, ...)
__
__
DO THIS WORKING FROM OUTSIDE OF PHOENIX OS (working on Windows, Linux, ...)
4. Go to the folder where Phoenix OS is installed and replace the following files:
(Personally, I always prefer to first copy the original files into another folder to invert this work if any problem happen, but it should work always without any kind of issue)
4.1 - Replace initrd.img with the file initrd.img found into the common folder
4.1.a - if your Phoenix OS is 32-bits: Replace ramdisk.img with ramdisk.img found into the x86 folder
4.1.b - if your Phoenix OS is 64-bits: Replace ramdisk.img with ramdisk.img found into the x64 folder
Note: "Alt + F1" terminal won't be available after replacing initrd.img
__
At this point, Magisk is full installed and you're now ready to install every module suitable for your Android x86/x86_64 kind of version from Magisk Manager App.
--------------------------------------------
Click to expand...
Click to collapse
I couldn't have it work on x86 5.0.1
It boots back to BIOS

There's anyway for use phoenix os 3.0.5 or 3.0.6
I'am using windows,want use magisk

It works but after using it for a few minutes it reboots. Any fix?

Ytim08 said:
It works but after using it for a few minutes it reboots. Any fix?
Click to expand...
Click to collapse
I didn't get that ,if you can upload log ,I may help

Camlin3 said:
I didn't get that ,if you can upload log ,I may help
Click to expand...
Click to collapse
If I could get a logcat I could've maybe fixed it myself already, the problem is it reboots and logs are reset
Edit: out of curiosity, were you able to successfully install magisk 18 on latest Phoenix is version? It works for a couple minutes and then crashes and I have to hard reset