Hi everyone,
Thank you for reading this thread question.
I have an Android 2.3.3 Mediatek MTK 6573 Phone. I am trying to learn how to make a custom rom. I like to know what tools we need to use in order to develop on this phone and in general. I have a few questions about the process to setup and make a custom ROM.
I rooted my phone using SuperOneClickv2.3.3-ShortFuse. I'm trying to perform backup of the rom before I flash the ROM. I'm atta
1. Backup
http://forum.xda-developers.com/showthread.php?t=1683883
The backup shell script uses mkyaffs2img, but it appears to be missing on my phone. Is there a correct site to get the right binary for mkyaffs2img to execute on the phone?
Currently when I try to backup the last part of the sh file this binary was missing
cat /sdcard/Install/BackUp/yaffs_back_2.3/gen/mkyaffs2image > /system/bin/mkyaffs2image
I tried to get a copy from code.google (http://code.google.com/p/fatplus/downloads/detail?name=yaffs2-source.tar&can=2&q=)
I get the error /system/bin/mkyaffs2image: 1: Syntax "(" unexpected
I tried using Nandroid, but I don't see the system.img or ramdisk.img file that represents the ROM system.
2. Flash ROM
http://bm-smartphone-reviews.blogspot.com/2011/10/mt65x3-flashing-tutorial.html
From the same thread there is mention about SP Flash Tool. What is the scatter.txt file? Do we need to find it some where?
3. Android source
Can we use the android source (http://source.android.com/) to make our own custom ROM? If so how do we include the drivers that are specific to the phone? I can build my own custom system.img and ramdisk.img with the android source and load it on the emulator, but I don't know if I can use those img and flash it onto a real android phone. I'm aware of the idea of android fragmentation, but looking at android source code, it seems we need the specific vendor drivers to be included in the source build. Is this the difficult part in flashing roms for specific phone hardware?
Thanks for you help and explanatins .
I think I'm trying to over complicate things, but this is my first time flashing ROM in android, rather than windows mobile >_<
Best,
SoLi26200
Related
Hiya I am interested in compiling my own version of the android project from the latest sources for Hero but I am having a little bit of trouble, I have been attempting to follow this guide android.modaco.com/index.php?showtopic=301857&view=findpost&p=1179830 but it does not seem to make a lot of sense to me. For instance there is no .repo/local_manifest.xml file only a .repo/manifest.xml file and editing this as outlined gives me an error. Could somebody point me in the direction of a fairly noob friendly guide for this kind of stuff, thanks a lot.
Conb123
P.S Sorry about the dodgy link, newbie restrictions prevented me from formatting it properly
this should be in Q&A Section not development really. But im looking for this too! installed ubuntu using Wubi set up JDK,SDK testsign etc and repo but god knows how to do it all! I only want to port cyanogenROM
follow this: http://source.android.com/download
when you got everything synced you can basically type "make" and watch it compile for a while. i managed to do it with just above zero knowledge about compiling.
if you want the cyanogen sources try it with the according repo. i have zero idea about vendor overlays, as i needed to compile only the recovery (watched two hours of eclair compiling, then was told i need cupcake sources and can compile the recovery only...)
Yes I am aware of how to get sources and how to compile them, I am fairly well versed in linux. But I do not know how I can compile it into a usable rom for hero.
the result of the compiling are image files that can be flashed to the phone: system.img etc. you can extract them using unyaffs.
I ran the make command, but i really have no idea what to do from there. What is the end result of doing the first make command? Im fairly sure that it is not a single .img file you can flash onto your phone. You need to make a kernal if i am correct(anyone know how to do this?)
the result of the compiling is at least a system.img. if you compiled it correctly you can flash that to /system partition. further you need a boot.img, which also contains the kernel. the the rom-cooking howto in dev section how to create one, or just get one from a working rom.
fwiw, the .img files are in out/target/product/generic/ (although there probably is a device specific directory in there if you handled the vendor overlay correctly. <- this is just a guess, i have actually no idea).
Wanna link us to that how to thread? I cant seem to find a complete one with working links.
http://forum.xda-developers.com/showthread.php?t=551711
Hi,
I'm totally new to android custom ROM development scene, and one of the first things I really wanted to do was to be able to create TWRP recovery for any device that I could possibly own.
As such, I started doing my research. I've read a lot of guides and the more I read the guides, the more I seem to get lost on what to do... :crying:
By far, the best guide I've read is this one :
https://forum.xda-developers.com/android/software/guide-how-to-compile-twrp-source-step-t3404024
So far I've 'repo sync'ed twrp-6.0 from 'minimal sources', so what I understand is that I have a build environment to build an android ROM, but now I have to tweak several files to match it to my device.
In the tutorial, it says that I need to have 3 directories set up correctly.
1. kernel
2. device
3. vendor
I have a device SM-J5108.
My first goal was to correctly set up the 'device' directory. So I set off to look for a pre-made 'device' that's similar to my model. I landed on this page.
https://github.com/TeamWin/android_device_samsung_j7ltespr
It's for Galaxy J7, but it had the simplest directory & file structure so I decided to use this one.
However, I think it would be wise to get configs for the BoardConfig.mk from this repository.
https://github.com/TeamWin/android_device_samsung_j5nltexx
Next, I would download the original firmware from somewhere like 'updato.com', and rip off the original kernel from that file. then I would replace the 'kernel' file in the repository with that one.
I would do the same with the ramdisk.
Up to this point, am I on the right track?
And another thing that questions me is since I've ripped off the kernel and ramdisk, is the '/home/username/NameOfTheFolder/kernel/vendor/devicename' folder from the guide not needed at all?
And the third folder in the guide, '/home/username/NameOfTheFolder/vendor/vendor/devicename'.
From my understanding, this folder needs to contain all proprietary libraries & .ko and other stuff specific to the device that is not mounted by the ramdisk.
And from this guide :
https://web.archive.org/web/2016111...ro#Collect_any_available_existing_source_code
It tells me to use 'extract-files.sh' to automate the process of extracting these files. But I'm not entirely sure if I can just use a universal 'extract-files.sh' for this.
Could I use 'extract-files.sh' from any Samsung device repository such as this one?
https://github.com/omnirom/android_device_samsung_i9300
Or do I have to build a new 'extract-files.sh' just for this device...?
After settings up these two folders, I should just
Code:
cd ~/NameOfTheFolder
source build/envsetup.sh
lunch
Type the number of your device and press enter. For example in my case the number 16 is my device
mka recoveryimage ---> This command will start the compilation of the recovery.
And a recovery image should be ready to be flashed on the device right?
Thanks!
I want my ROM to receive OTA-updates, so instead of downloading and flashing a new version manually, users would get it updated for them automatically. All source codes are available for my device (Wileyfox Storm (kipper)), so building a custom kernel, recovery, TWRP, OS itself is trivial - generally you command brunch and everything just works™.
So I wonder - how do I enable OTA-updates for a ROM, while still keeping an option for users to use TWRP recovery? (yes, I got a place to host files & I generally understand how OTA works). I know that official TWRP app can queue zip files for installation in recovery mode, which is almost the same functionality I need for my OTA updates. Generally I'm looking for a way to make TWRP run a script located in /cache/recovery/command right after boot without offering any kind of user interaction. Can it be done with a TWRP, built from official sources or do I need to patch something to support that behavior?
So the question is how do I create OTA-updates that are compatible with official TWRP or how do I create a custom TWRP, that supports OTA-updates (whichever suits more for my task)?
Look up OpenDelta, its exactly what you're asking for I believe.
^^^Link please. im also looking same
I'm running Ubuntu 16.4 in VirtualBox and I'm trying to follow this guide for creating a custom ROM. Problem is, I am completely new to Linux and I'm literally copying and pasting command line. I don't understand what everything does. I'm just kind of doing it for now, learning as I go. So far, everything has worked fine. But now, I'm stuck at this part:
Now before starting with Building guide you have to Download your Device Identity That is has follows
1) Device Tree
2) Vendor
3) Kernel
The Above files are very Vital Parameters of building they specify your device and its Characteristics.
Now you might think from where you have to download those files?
Don't be confused its simple Search in our device forum for CM Tree and Kernel and Vendor. The Dev of CM for your Device forum will specify it in his ROM thread.
Click to expand...
Click to collapse
I found my device's device tree on github: https://github.com/j03lpr86/android_device_samsung_afyonltetmo
What do I do with it? Download the zip and put it somewhere and then extract it somewhere? If so, where? Or do I use the "Clone with HTTPS" link? If so, how do I execute it in the terminal?
Same questions with the vendor I found: https://github.com/j03lpr86/android_vendor_samsung_afyonltetmo
As for the kernel, what do I do for that? XDA doesn't have my device listed (Galaxy Avant). I downloaded the stock ROM from Sammobile. Do I extract kernel.img from that? If so, where do I place it?
There are just too many assumptions that the author of the guide makes and I don't understand what to do at this point.
have you looked on git hub for them?
I have an android device running Android 5.1.1 but on a proprietary build that doesnt include GApps.
What i want to do is root the device, but in order to do so with Magisk, I need the Stock ROM boot.img file which I cant find anywhere because they arent open source like Samsung ect. There is also no TWRP build for it, official or ortherwise.
The device is a Rand McNally OverDryve 8 Pro.
Anyone have any ideas on how to get the boot.img file without having exising root or TWRP? Maybe with adb without root though, unless some way to gain root shell without root device.
Or can anyone point me to a DETAILED, uptodate guide on how to compile TWRP myself, inculding setting up the build envirment and which version of Ubuntu I should use. I have tried previously with some older guides using Ubuntu 12.01 or somthing but lots of sync and repo issues and such and i gave up as im jist learning on the fly and not capable of deep troubleshooting.