The topic of how to port the firmware Android is rather hackneyed, but it does not lose its relevance. On the contrary, more and more people are beginning to be interested in it. In this article, we will only cover porting devices with the same kernel. If you want yourself a super-interesting firmware, then it's time to start dealing with the 'kitchen' of this process.
Step-by-step instruction
What you need:
- computer with any OS;
- WinRAR or a similar archiver;
- Notepad ++;
- two ROMs: portable (hereinafter PROM – from which we will take 'tzatzki') and basic (hereinafter BROM – on which we will collect).
BROM is usually native firmware.
Since we will be looking at an ARM device here, you first need to find out which processor you have.
to the content
Action one
Create a backup from the system / app directory to any folder on the desktop. By copying the files, you will understand what the matter is, because if you started porting, then, probably, you have flashed your MID more than once.
to the content
Second action
Delete the directories shown in the picture from BROM and, accordingly, insert the folders from PROM instead.
to the content
Act three
Now we throw the files from the first action back into BROM.
to the content
Action four
Go to the system / lib BROM folder and copy and replace all the libraries to the corresponding PROM storage (don't be surprised, it's easier). We do the same along the paths /system/etc/init.d and / system / etc / permissions. The three above directories can now be destroyed (in BROM), and in their place you can copy everything from PROM.
Important: open the build.prop files in both ROMs via Notepad ++. This enhanced notepad shows tabs well. The latter must be one opposite the other, and the ro.build.description = entry must absolutely match, otherwise you will not be able to flash the device at all. If the entry is not the same, edit it. Do the same with updater-script located in META-INFcomgoogleandroid path. Naturally, the record must be identical with the PROM record.
Very important: you cannot change symlinks at all. You can change or fix or add ui_prints, run_programs, asserts and of course the kernel.
Most importantly, in Updater-script BROM Format values should be for your device. Sometimes you need to fix BOOTCLASSPATH in init.rc or just copy it from RBOOT. Then, of course, repack the kernel.
Well, that's it! Porting firmware Android based on ARM is done like this. Good luck!