I am creating a ROM for a phone that no one else has made ROMs for yet. I went to Samsung's open source site and download the files I for the device. Then I unpakage the file and the where two files in it but I don't know what one it is or anything one how to add it (the files inside Kernel.tar.gz and Platform.tar.gz). So does anyone know how to add a unsupported Samsung device so I can create a ROM for it???? Well what I am trying to ask is how to build a ROM for my device?????
The Device I am working with:
Samsung Legend (Jasper)
SCH-i200pp version MH1
Code Name: jaspervzw
Build.prop of the device download is below!
Open Source File Website:
opensource(dot)samsung(dot)com
Devices Website:
www(dot)samsung(dot)com/us/mobile/cell-phones/SCH-I200ZKPVZW
Related
i'm trying to build an aosp rom for my samsung galaxy s duos(gt-s7562). what modifications do i do so that the rom can work on my phone.
i've downloaded one file from samsung open source website this files contain two things called platform.tar.gz and kernel.tar.gz
how do i go about this.
i'm running the latest firmware update and the phone is rooted and has clockworkrecovery mod on it
Hello,
I'm trying to build a device tree for the Samsung Galaxy Tab A 9.7 (gt510wifi), by following CyanogenMod's porting guide here. I've managed to get a basic device tree going inside CM12.1's source tree, but I'm stuck at the part where I need to create the extract-files.shand the setup-makefiles.sh. The guide says to use other device trees as a reference for creating these scripts, but from what I can tell, each script is vastly different due to device discrepancies, and I'm unsure what to do at this point. I've searched everywhere online, but there doesn't seem to be any documentation whatsoever on how to create these files.
I'm no stranger to porting ROMs, as I've built SlimLP for my other devices, but I always had a pre-built tree created by another developer that I simply renamed files in to get it to work with SlimLP's sources.
Any help is greatly appreciated
Anyone here can u tell me how to create source code of a new device as my device is INFOCUS M680, kernel source.
I have used another device as same board to create source of my device but the kernel source is different. So anyone can tell me how to create kernel source and device tree.
My kernel version is 3.18.19+
Find the open sources for your device and download them. You need to match the build number from that release to the build number for the AOSP sources and download those as well. I have only done Samsung so far but the instructions are fairly clear for merging the sources. Next you need hardware drivers, in my case I have tons of free drive space so I just copied the entire /etc and /vendor from my device firmware.
A lot of time can be saved by downloading a matching sources from a custom rom. You can take configuration files and etc.
No open sources and no custom roms? You should start on something easier my friend. But if you want to continue forward with that I am guessing here. Unpack the boot.img and recovery.img files with the available unpackers. (save the info for the images and follow how to repack carefully) Match your build number to the AOSP sources and get the kernel. Modify, hack, gather and assemble what you need to make a new boot.img and recovery.img. Then with great courage comes lots of bricked devices..
Late reply so I didn't try to hard there. I will always help people send me a PM if your stuck
droidvoider said:
Find the open sources for your device and download them. You need to match the build number from that release to the build number for the AOSP sources and download those as well. I have only done Samsung so far but the instructions are fairly clear for merging the sources. Next you need hardware drivers, in my case I have tons of free drive space so I just copied the entire /etc and /vendor from my device firmware.
A lot of time can be saved by downloading a matching sources from a custom rom. You can take configuration files and etc.
No open sources and no custom roms? You should start on something easier my friend. But if you want to continue forward with that I am guessing here. Unpack the boot.img and recovery.img files with the available unpackers. (save the info for the images and follow how to repack carefully) Match your build number to the AOSP sources and get the kernel. Modify, hack, gather and assemble what you need to make a new boot.img and recovery.img. Then with great courage comes lots of bricked devices..
Late reply so I didn't try to hard there. I will always help people send me a PM if your stuck
Click to expand...
Click to collapse
Thanks for your reply.
I am planning to create a custom rom for my samsung tab A Sm-P555
Where do I start ? Is there AOSP for it ? How do I unpack everything ? Could you help me as I was very new to this ?
Many thanks in advance.
all you need is here
droidvoider said:
Find the open sources for your device and download them. You need to match the build number from that release to the build number for the AOSP sources and download those as well. I have only done Samsung so far but the instructions are fairly clear for merging the sources. Next you need hardware drivers, in my case I have tons of free drive space so I just copied the entire /etc and /vendor from my device firmware.
A lot of time can be saved by downloading a matching sources from a custom rom. You can take configuration files and etc.
No open sources and no custom roms? You should start on something easier my friend. But if you want to continue forward with that I am guessing here. Unpack the boot.img and recovery.img files with the available unpackers. (save the info for the images and follow how to repack carefully) Match your build number to the AOSP sources and get the kernel. Modify, hack, gather and assemble what you need to make a new boot.img and recovery.img. Then with great courage comes lots of bricked devices..
Late reply so I didn't try to hard there. I will always help people send me a PM if your stuck
Click to expand...
Click to collapse
Hola
Perdón pero estoy sufriendo errores con la app XDA labs
Thank you
I would like to build and flash the Android Lollipop Source for a Samsung S5 device. I do not quite understand how to do that. This is what I have done so far
I have downloaded the Android source for 5.0.1 from source.android.com and the Samsung S5 device source code from opensource.samsung.com.
The Samsung device source code zip contains a kernel zip file, platform zip file and two readme files. I have followed the instructions successfully for building the Kernel.
What are the next steps to be taken in order to build and flash the same for my Samsung S5?
Did you manage to figure it out?
Hells.Guardian said:
I would like to build and flash the Android Lollipop Source for a Samsung S5 device. I do not quite understand how to do that. This is what I have done so far
I have downloaded the Android source for 5.0.1 from source.android.com and the Samsung S5 device source code from opensource.samsung.com.
The Samsung device source code zip contains a kernel zip file, platform zip file and two readme files. I have followed the instructions successfully for building the Kernel.
What are the next steps to be taken in order to build and flash the same for my Samsung S5?
Click to expand...
Click to collapse
I'm in a similar situation cant figure out how to go about it.
I am following the Android CustomROM building guide by jackeagle.
But instead of cloning from the CM repositories, I have cloned from the Google repository. Now I'm at that part where we need to download proprietary binaries of the device for which we're developing.
I had read that those proprietary binaries can be extracted from the device, when it is flashed with the stock source it was released with. But unfortunately, I'm unable to understand how I can pull those files using adb.
I'm using Samsung Galaxy S Duos (GT - S7562) (for learning purposes). I don't need a device specific solution. I just want to know in general, how we can pull the device-tree, vendor and kernel for any given device from it.
Thanks in advance.