This is probably an insanely noob-ish question, but I've scoured the internet (and this site) for days and I haven't found anything yet, so I'm hoping someone with some smarts or experience can help me.
I'm trying to build TWRP recovery for my device, an unsupported phone. (The BLU Life One 2015: GSM Arena Specs) Specifically, the 2GB RAM 16GB ROM version, if that helps. I've been following this guide: [DEV]How to compile TWRP touch recovery by Deez Troy, and I've got my whole build environment set up, I have the source downloaded, and I've found (what I'm pretty sure is) a device tree for my phone HERE. I'm convinced it's for my phone since the model listed is X011Q, which is the name of the firmware for my phone.
The issue I'm having is that when I get to the part of the guide about editing the BoardConfig.mk file, I can't find it anywhere. Not in AOSP source, (which I downloaded for later use), not in the TWRP source, not in any of the partitions I've pulled from my phone, or in the device tree. My main questions then are these:
1.)Does it actually exist some where for me to find?
2.)Is it device specific, or will one for a phone with similar specs (probably) work fine?
3.)If I have to make/build it, how do I go about doing that? What needs to be in it? (Though I'm less sure this would be the case thanks to THIS post.
4.)If none of the above questions are the right one to ask, but if you think you know what I need to know/what I need to ask, please TELL ME!
Also, any other resources anyone can point me towards or advice/pointers you can give me would be greatly appreciated.
The same question.
No answers?
Fourteenth said:
The same question.
No answers?
Click to expand...
Click to collapse
Nope. If it didn't spontaneously create itself out of nothingness, you will never be able to find it. No one ever created the files, they popped out of Zeus' forehead fully-formed.
Here is the answer:
source.android.com - new-device
You can download the BoardConfig.mk for your device or make a new one.
Related
Lemme get some things out of the way.. I am a noob. I have searched. I have read some of the results from the search. I am overwhelmed by the 20+ pages of results (lol). I am not 100% sure this is the correct forum for this (not sure where else would be ).. I believe this is one of those things where I need help based on my situation.. Ok, so here I go.
I wish to start porting ICS to my phone. That's my goal. I have general understanding of how linux works, but I do not know much about the android specifics of how they work, or what needs to be modified for this to work. I do not plan to use the kitchen tool as I wish to learn this the hard way. I believe this will help me become more understanding in what I am doing. However, at this point I don't and that's why I'm here. My phone model is irrelevant almost because its prepaid and usually the communities don't even recognize their existence.. at least that's how I feel about it. But I digress. My phone is the zte warp by boost mobile and I am here to learn hopefully the things that will get me started on porting ICS to this phone. I right now believe that the best thing for me to learn is how the android related files work because as it is, I only looked at guides on how linux works and I understand most of it. I'm not sure that's the best thing that will help me port ics, but I'm certain it is important.
Please help me figure out where I should start in learning how to port ICS to my phone basically.
Thanks XDA
anyone? I am quite serious about wanting to do and go into this but I have yet one thread that anyone's ever replied to.. (or post iirc) which puts a damper on me
Snake X said:
Lemme get some things out of the way.. I am a noob. I have searched. I have read some of the results from the search. I am overwhelmed by the 20+ pages of results (lol). I am not 100% sure this is the correct forum for this (not sure where else would be ).. I believe this is one of those things where I need help based on my situation.. Ok, so here I go.
I wish to start porting ICS to my phone. That's my goal. I have general understanding of how linux works, but I do not know much about the android specifics of how they work, or what needs to be modified for this to work. I do not plan to use the kitchen tool as I wish to learn this the hard way. I believe this will help me become more understanding in what I am doing. However, at this point I don't and that's why I'm here. My phone model is irrelevant almost because its prepaid and usually the communities don't even recognize their existence.. at least that's how I feel about it. But I digress. My phone is the zte warp by boost mobile and I am here to learn hopefully the things that will get me started on porting ICS to this phone. I right now believe that the best thing for me to learn is how the android related files work because as it is, I only looked at guides on how linux works and I understand most of it. I'm not sure that's the best thing that will help me port ics, but I'm certain it is important.
Please help me figure out where I should start in learning how to port ICS to my phone basically.
Thanks XDA
Click to expand...
Click to collapse
From my limited knowledge, I think it is a huge task undertaking, you can download Android source code from Google, the hard part will be the device driver development and porting for Linux kernel (and maybe portion of Android). If you are lucky, you can use the existing phone bootloader (or you have to port one). Understanding the inner of the phone (different chip set may need different device driver) will be another challenging task.
by the device driver development, you mean all the libs that go into the phone? Couldn't I just copy/paste the pre-existing libs that are already made for the phone? Also the phone im working with is a bit strange really.. noone has been able to compile the kernel from its source and get it to boot yet.. when it was compiled the zImage was different than that of the stock one.
And yeah, I have downloaded the aosp source.. I just need to know where to start at and the processes involved really
Snake X said:
by the device driver development, you mean all the libs that go into the phone? Couldn't I just copy/paste the pre-existing libs that are already made for the phone? Also the phone im working with is a bit strange really.. noone has been able to compile the kernel from its source and get it to boot yet.. when it was compiled the zImage was different than that of the stock one.
And yeah, I have downloaded the aosp source.. I just need to know where to start at and the processes involved really
Click to expand...
Click to collapse
To answer you question no the drivers and lib files are different for aosp based rooms then they are for the stock OEM from. The first step will be to get a working kernel. Without anything you do will be pointless
I'm somewhat interested in the same thing, and from what I've gathered, you'll need to do these things to begin ROM development:
1. Read every page on the AOSP site and grab a copy of the AOSP source. It probably wouldn't hurt to read the regular Android developer wiki as well.
2. Learn about Linux driver development:
http://lwn.net/Kernel/LDD3/ (this is apparently considered THE BOOK on Linux driver development)
http://www.freesoftwaremagazine.com/articles/drivers_linux
3. Learn pretty much every detail about your phone and its hardware, especially when it comes to how ROMs are installed on it. For example, my phone (the Droid X2) has a locked bootloader, so 2nd init has to be used to boot new ROMs, and this makes it so that we cannot update the kernel.
You can usually find this sort of information on your phone manufacturer's website. Sometimes they even post the source code to their phone's drivers, which is helpful.
4. Look at other ROMs (preferably for your phone) and see how they work. The source code is freely available for most popular ROMs.
For example: CyanogenMod keeps their source code in a public git repository: https://github.com/cyanogenmod
5. Get to work on porting!
I would highly recommend starting with something smaller, however, just as a start. One good jumping-off point is probably this guide: http://forum.xda-developers.com/showthread.php?t=1272270
If any part of this was wrong, or if I left something out, somebody feel free to correct me, I'm still a noob.
Thank you so much for your direction, however,, android kitchen.. im not sure about that because isnt that only ment for htc devices? My phone is made by zte
what device do you even have?
if it's stuck officialy on 2.1 or 2.2 there's no hope that if you even port it that it'll work
its the zte warp from boost mobile (prepaid). Btw if I compile an aosp ics launcher and put that on my phone whats the chances of that working?
edit: it uses 2.3.5
Well Sebastian responded on android forums, apparently zte is very bad at version control with their kernel sources. So when they complete one project, they use the same source for the next project, and what they release could be for anything. Apparently the blade source had the same issues, it took him a while to get them to correct the source
Sent from my N860 using Tapatalk
Yeah I noticed that there were ppl saying there were things similar but I'm not sure what will work or what won't.. guess its time to start a petition on zte to release the source code lol
edit: seems like zte's bein a bad company and violated the GNU GPL license for not providing a complete source code.. I compiled an email and sent it to someone who can proof read it and send it to the right person for this kinda thing.. danggit zte
Hello,
I have an Ampe A10 Quad core tablet (Freescale I.mx6q chip) which has quite a small dev community so far so I am looking at building my own rom for the device.
i can get by in Linux and learn fast so feel I can do it. I have been reading constantly for the last week before even starting to get a grip of whats what. I am trying to make an ASOP version of 4.0.4 to replace the stock 4.0.4, rather poor rom.
My question is what do I do about vendor overlays as there is nothing out there for this device or anything similar. I have done a lot of searching on this and found the suggestion "You could just use an extract from a working Rom or phone" " You use the extracted proprietory files to complete the source" . I understand I need the proprietary binaries to make the build but i don't really understand what that the suggestion means.
Any help you could offer on obtaining the files I need from the stock ROM and how to setup the vendor overlay would be most appriciated.
Cheers,
I don't have your device man, but if there is another similar device out there with a similar board and chip configuration search github for a repo that contains an "extract-files.sh" file for that other device. Fork it, clone into your dev environment under your Device folder, connect your tablet via USB (make sure adb is running), and run that script. It should pull the proprietary files required straight from the device and you may be better off.
Hope this helps a little! Good luck with your project.
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app
djmatt604 said:
I don't have your device man, but if there is another similar device out there with a similar board and chip configuration search github for a repo that contains an "extract-files.sh" file for that other device. Fork it, clone into your dev environment under your Device folder, connect your tablet via USB (make sure adb is running), and run that script. It should pull the proprietary files required straight from the device and you may be better off.
Hope this helps a little! Good luck with your project.
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the advice. I have spend some time searching but cannot find anything on github. There are only a couple of devices that are similar. The Ampe A10 Sanei N10 and Hiapad F10 are all the same thing just rebranded, the other is the Zenithink C94 but I cant find anything on any of them.
How can I create a new device tree for my device? (which from what I understand is what I want) It would be a good thing to achieve as it would help others in the future. I have been through the "Configuring a New Product" on the AOSP site so now understand a bit more what's going on.
Sp3ktral said:
Thanks for the advice. I have spend some time searching but cannot find anything on github. There are only a couple of devices that are similar. The Ampe A10 Sanei N10 and Hiapad F10 are all the same thing just rebranded, the other is the Zenithink C94 but I cant find anything on any of them.
How can I create a new device tree for my device? (which from what I understand is what I want) It would be a good thing to achieve as it would help others in the future. I have been through the "Configuring a New Product" on the AOSP site so now understand a bit more what's going on.
Click to expand...
Click to collapse
extract-files.sh is a cyanogenmod creation, so you'd be lucky to find anything....... Linaro offer support for the sabre lite development platform which is a i.MX 6q based board, maybe building Linaro's version of the AOSP would be a good start
Here's a couple of links to get you started
https://wiki.linaro.org/Boards/MX6QSabreLite - Overview of the Board, you can check how close it is to your device
https://wiki.linaro.org/Platform/Android/BuildSource
You are correct you need to create a device tree , a couple of good resources I've used in the past when creating device tree from scratch are
Embedded Android ( http://shop.oreilly.com/product/0636920021094.do ) this book is pretty close to the bible on the Android Build System and worth the Investment. Alternatively ( more importantly free! ) a slide deck by the same author ( http://events.linuxfoundation.org/slides/2011/abs/abs2011_yaghmour_porting.pdf )
Android Device Porting - http://www.youtube.com/watch?v=mvxYt3AkbrE
Could the extract script not be used to help pull the right files straight from the device for his vendor folder though? He would just need to edit the list of files to be pulled in the referenced list the script uses in the loop if he knows what configuration files are needed, no?
I'm by no means an expert but on first glance that's all the extract-files script does...or is there something I'm missing? I'm learning too so would be good to know either way lol
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app
djmatt604 said:
Could the extract script not be used to help pull the right files straight from the device for his vendor folder though? He would just need to edit the list of files to be pulled in the referenced list the script uses in the loop if he knows what configuration files are needed, no?
I'm by no means an expert but on first glance that's all the extract-files script does...or is there something I'm missing? I'm learning too so would be good to know either way lol
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app
Click to expand...
Click to collapse
Apologieses if that came across as abrupt, Just sayin' you'd be lucky to find one that come close to his board etc, iMX Freescale chips are not that mainstream But yeah if you can find an extract script than have at it! Saying that why do you even need a script? just pull the files yourself through adb, pointless wasting time searching. The question then becomes, what files? And that is unique the each device and each version and how much of it is open source etc,etc.
I think the OP is probably a way off doing that, when I've played around starting a device tree from scratch, I've find it is easier to start off with the base requirements, i.e processor architecture, maybe start with building a mini package first or even BUILD_TINY_ANDROID on a generic arm board. The whole starting from scratch thing is not a small task, which I suppose was your point in the first place lol
For sure. It really does boil down to what files, whether a script is used to pull them or not lol.
Thanks for the links by the way, SUPER informative
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app
thanks for all the great info Trevd. The Sabre lite board is very similar indeed! There seem to be only a few minor differences which are inconsequential anyway. For example the tablet have less USB and no Ethernet. I think it could be a good starting point.
I guessed when I started this project it wouldn't be a quick fix but that't not a problem, At the end of it I will have my own working ROM and that's the point.
I can see the Freescale chips being taken more in to the main stream in the future. The tablet is VERY fast and reliable it has just been let down by poor, half-arsed software. For example all the aspects of Android relating to telephony have still been left in.
Thanks again,
Sp3ktral said:
thanks for all the great info Trevd. The Sabre lite board is very similar indeed! There seem to be only a few minor differences which are inconsequential anyway. For example the tablet have less USB and no Ethernet. I think it could be a good starting point.
I guessed when I started this project it wouldn't be a quick fix but that't not a problem, At the end of it I will have my own working ROM and that's the point.
I can see the Freescale chips being taken more in to the main stream in the future. The tablet is VERY fast and reliable it has just been let down by poor, half-arsed software. For example all the aspects of Android relating to telephony have still been left in.
Thanks again,
Click to expand...
Click to collapse
Plz keep us in the loop on how the rom is comming along.
Not that many I.MX6Q roms out there yet, and im sure many peeps are waiting for it
Thx for giving it a shot
Ill be watching
Corw1n said:
Plz keep us in the loop on how the rom is comming along.
Not that many I.MX6Q roms out there yet, and im sure many peeps are waiting for it
Thx for giving it a shot
Ill be watching
Click to expand...
Click to collapse
I'm one if those hoping for a decent rom... Apparently freescale have released a beta for jelly bean on the imx6.
MrVanDango said:
I'm one if those hoping for a decent rom... Apparently freescale have released a beta for jelly bean on the imx6.
Click to expand...
Click to collapse
Oh? Where did u find that? Been googeling my ass off trying to find a freescale jb rom....
Hope it comes tho.....already ordered my ampe a10 quad.....
Corw1n said:
Oh? Where did u find that? Been googeling my ass off trying to find a freescale jb rom....
Hope it comes tho.....already ordered my ampe a10 quad.....
Click to expand...
Click to collapse
You can download it from github. I can't post links at the moment. If you can't find it PM me and i'll forward the link i have.
MrVanDango said:
You can download it from github. I can't post links at the moment. If you can't find it PM me and i'll forward the link i have.
Click to expand...
Click to collapse
any updates on this? i cant find it on github either.
goldenpipes said:
any updates on this? i cant find it on github either.
Click to expand...
Click to collapse
The Freescale Github account is here, and it doesn't look like they provide much more useful stuff than their meta-packages there: github.com/Freescale
What I know is that for every SoC they have a page (sorry, not allowed to link yet. just search "i.MX6" on the freescale website) where they offer demo images and at least a set of patches with some documentation on how to build that Android branch.
E.g. at "Operating System Software-Board Support Packages" you can find a demo image for Kitkat and a source package: "IMX6_KK442_100_ANDROID_SOURCE_BSP" (you have to register a free account with your mail to download this). Then usually it works like this:
Get the according AOSP branch from Google
Apply patches provided by Freescale
Clone their kernel repository
Clone their uboot repository
Build
Look for a document named "Sabrelite-Android_User's_Guide.pdf" for more detailed information. Sorry, I can't remember if it was included in the source package or in another download provided in their list.
Hello all,
I'm trying hard to figure out how one goes about compiling Android JB AOSP (4.1.2_r2.1) platform for the samsung galaxy s2 (GT-I9100M), with the source code that samsung gives you?
I've setup ubuntu 14, and I see how I can run . build/envsetup.sh, and then lunch.
I get all the options to build, and I see where the saumsung scripts are located, in device/samsung.
I've downloaded the open source file GT-I9100M_BMC_JB_Opensource.zip, and compiled the Kernel.
Now its time to build the platform. I see the folder structure, but I see no instructions.
When I unzip the Platform, I see build, external, vendor, and device, which has the folder "smdk_common".
If I put all files in the corisponding locations within the AOSP, I get errors, as there's only a folder "alsa-lib". (sound drivers).
And if I were to compare what's in here to whats in the AOSP device/samsung folders, there's lots more info.
Do I need to copy files from the default AOSP device/samsung folders and modify to suite my needs or?
Can anyone point me to how-tos? I've been trying to figure this out for days!
I see a lot of how tos on building with existing ROMS, and using kitchen, etc.
But I just want to build samsung from scratch FIRST...
OK, so doing a lot more research, both here and google, I obviously need to create a device tree OFF of the files that samsung has released to everyone. Surely someone has done this already?
I see there are a few GIT repositories that have device trees, but they are based upon existing files, etc.
I'm looking to find a device tree that has all the basics, OR a "template" one i can try and work with samsungs...
technobuddha said:
OK, so doing a lot more research, both here and google, I obviously need to create a device tree OFF of the files that samsung has released to everyone. Surely someone has done this already?
I see there are a few GIT repositories that have device trees, but they are based upon existing files, etc.
I'm looking to find a device tree that has all the basics, OR a "template" one i can try and work with samsungs...
Click to expand...
Click to collapse
Hi,
did you succeeded in your approach to build a device tree with the Samsung-opensource-files? if yes then I'll be very interested in the way you do it as I'm on the same status for a Samsung device which has absolutely no support in the hole internet (except one thread here in XDA
BR
SP
No I didn't.
and I got no help what so ever from the people here at xda-developers.
I even approached some of the people who compile the roms, and got no response from them.
I suspect the only help you'll ever get from these forums is if you ask for help from EXISTING roms,
or you're an "existing" developer that has years of experience.
this place is not for new developers at all.
a lot of brown nosing going on here..
good luck in your search!
SolarPlexus said:
Hi,
did you succeeded in your approach to build a device tree with the Samsung-opensource-files? if yes then I'll be very interested in the way you do it as I'm on the same status for a Samsung device which has absolutely no support in the hole internet (except one thread here in XDA
BR
SP
Click to expand...
Click to collapse
technobuddha said:
No I didn't.
and I got no help what so ever from the people here at xda-developers.
I even approached some of the people who compile the roms, and got no response from them.
I suspect the only help you'll ever get from these forums is if you ask for help from EXISTING roms,
or you're an "existing" developer that has years of experience.
this place is not for new developers at all.
a lot of brown nosing going on here..
good luck in your search!
Click to expand...
Click to collapse
OK, thanks for your response. Thats also my experiance more ore less I have found (with some exceptions which really try to help).
So I'll try to work on it, and if I succseed, I'll make a guide... maybe it will help then others
BR
SP
what phone is it?
and yea, if you need any help,just ask me.
SolarPlexus said:
OK, thanks for your response. Thats also my experiance more ore less I have found (with some exceptions which really try to help).
So I'll try to work on it, and if I succseed, I'll make a guide... maybe it will help then others
BR
SP
Click to expand...
Click to collapse
Its the Samsung sg-i8200 (s3 mini value edition)
The previous phone was supported very well (i8190) but the i8200 has a complete new hardwarebase and its really garbage...
send with my Oneplus One (bacon) SlimKat Tapatalk
Okay, First of all, I know this is the incorrect place for a "development" thread, But I am currently unable to post in the correct area.. So here is the second best place.
I've had an idea. Since sadly I am gonna be giving back the Samsung Note 2 (Friend let me borrow it) I have to do something with the new Umi eMax I have.. Its a great potential phone but MEDIATEK wont freaking let us have the source code... So, Why not pull it off a rom? You can easily download something like ColorOS, Get the kernel, and extract the Source code, Am I not right?
I am wanting to do this because Umi has been sitting around barely doing jack trying to get the new 5.0 android up and running.. So installing CM 12.1 would be great!
This is probably totally impossible.. as I am a beginner at this kinda stuff, But, would this idea work or not?
I have the build.prop file if anyone wants to take a look at it.. Though we probably all know it runs off the MT6752.
So, Does anyone have any ideas? Or am I just getting completely over confident on this?
Trying to get 10 posts....
Hi all,
With the risk of this being called a duplicate thread I just want to clarify that I'm in no way asking to port something for me, and I've read the 2 similar threads around, and felt like this should have it's own place.
So, straight to the point, I've been looking to get involved with android porting, and since LOS and AOKP for our device haven't quite filled my cup I was thinking of trying to port something else (trying to not get into much detail here )
Moving on, after searching around XDA and everywhere else, I've found a tuto or two where the process of porting was explained, and being an average user, I went to grab a "Base ROM", (thought the LOS/Stock ones would do, downloaded both)
To my surprise, files mentioned in the tutorials (framework-res.apk, framework.jar, ...) are nowhere to be found.
Finally the question, this just to save me from a reflash,
Am I supposed to install the "Base ROM" to dump /system to my PC?
Or am I perhaps misunderstanding something?
----
PSA: I'll probably find it difficult to get time to work on this (school stuffs) so even if I decide to go on with it, it might take a good while till something comes up.
Also, if there's someone with some experience in porting who'd be so kind to give me some pointers or show some availability to help with bug fixing/porting (not asking for labor, just explanations, in case I need 'em), please PM
Thanks, and sorry for the long post
b0taSs said:
Hi all,
With the risk of this being called a duplicate thread I just want to clarify that I'm in no way asking to port something for me, and I've read the 2 similar threads around, and felt like this should have it's own place.
So, straight to the point, I've been looking to get involved with android porting, and since LOS and AOKP for our device haven't quite filled my cup I was thinking of trying to port something else (trying to not get into much detail here )
Moving on, after searching around XDA and everywhere else, I've found a tuto or two where the process of porting was explained, and being an average user, I went to grab a "Base ROM", (thought the LOS/Stock ones would do, downloaded both)
To my surprise, files mentioned in the tutorials (framework-res.apk, framework.jar, ...) are nowhere to be found.
Finally the question, this just to save me from a reflash,
Am I supposed to install the "Base ROM" to dump /system to my PC?
Or am I perhaps misunderstanding something?
----
PSA: I'll probably find it difficult to get time to work on this (school stuffs) so even if I decide to go on with it, it might take a good while till something comes up.
Also, if there's someone with some experience in porting who'd be so kind to give me some pointers or show some availability to help with bug fixing/porting (not asking for labor, just explanations, in case I need 'em), please PM
Thanks, and sorry for the long post
Click to expand...
Click to collapse
i wouldnt even try to port, its just confusing, files missing, preloader updates which makes you think which one to use, its all really just a mess, you will have better chance of getting something if you build from source, just fork our device, kernel and vendor trees and download a custom rom source of your choosing and build it, i wont say step by step, but i recommend that to download the vendor, device and kernel sources you make the local_manifest.xml so that when you do repo sync it downloads those sources aswell
Ruben Craveiro said:
i wouldnt even try to port, its just confusing, files missing, preloader updates which makes you think which one to use, its all really just a mess, you will have better chance of getting something if you build from source, just fork our device, kernel and vendor trees and download a custom rom source of your choosing and build it, i wont say step by step, but i recommend that to download the vendor, device and kernel sources you make the local_manifest.xml so that when you do repo sync it downloads those sources aswell
Click to expand...
Click to collapse
And here I thought porting would be easier, but yeah, now that you mention that.. :silly:
Aw well, thanks mate :good: