Hi all,
I see sometimes that there are unofficial ROMs made of official ROMs such as Paranoid Android, that support devices such as our own before the original ROM creator does.
Now I know nothing about making ROMs, I'm guessing there of course is specific firmware and drivers for our phone as one example, unique to us.
Is it a support question, as in the official makers could support another phone (easily?!), but don't, because they don't have the device to confirm it works fine or may carry a brick risk etc?
How hard is it to make an "unofficial" ROM that supports specific devices features/hardware? Is it a case of merging differnt device firmware with another kernel and testing? (I'm sure some will be mad at my naivety)
Sorry for the newb question.
Related
Hey,
I've just recently started Android development and I'm keen to learn as much as I can about the whole system, not just about SDK app development. As such I'm interested in attempting to build my own ROM completely from scratch. I've downloaded the Android Source (and Galaxy S source) and would like to try my luck.
First I've been mucking around creating custom ROMs with the emulator, moving apps from the Galaxy S ROM I dumped from my device onto the stock emulator ROM and testing things out.
Anyway I'm at the point where I'm wondering if it's possible to flash the stock emulator ROM onto a Galaxy S phone? I know the Galaxy S source includes a lot of device specific stuff however I'm not interested in getting the camera, bluetooth or anything hardware specific working just yet.
If I flash a ROM with a stock kernel, drivers etc. onto my phone will it work? Has anyone done this? Will it just brick my phone?
Any help would be appreciated.
Cheers,
Ben
Anyone?
Also, I know people have flashed AOSP ROMs on other phones, does anyone know if they required modifications or whether they are in fact stock ROMs?
nje, can't work. why?
1) different bootloaders
2) different partition layout
3) different (kernel)drivers
4) different vendor setup
etc.
it is possible to flash the emulator image onto a dev device (dream/sapphire) but even then a lot will not work properly!
if you want to learn about the android architecture you should start with building a kernel (there is already a thread about that here) and playing around with stuff like the (file)system and utilities...
Thanks jodue.
Yeah my long term intentions were definitely to build the Galaxy S kernel and any necessary libraries and drivers specifically necessary for the apps I decide to include in a custom ROM.
I was hoping that I'd be able to start out by tweaking a minimalistic/generic ROM (the AOSP default ROM) on my Galaxy S. However, as you've pointed out I'll have to start out with the kernel and all the device specific stuff first.
I've got quite a bit of information on building an Android/linux kernel both from the thread you mentioned and also the official AOSP page. However information on putting together a complete working ROM seems a bit sparse. Does anyone know where I can find some information on the topic?
I'm also curious to learn about the list of things jodue mentioned i.e. Android bootloaders, partition layouts and drivers (generic and Galaxy S specific). I assume detailed information about particular devices and drivers probably isn't available but if anyone even knows where I can learn detailed information about default AOSP ROMs I'd be extremely interested know.
Hi everybody, well, as many of you may know, here in Latin America (Brazil, Argentina, Chile) we have a specific Galaxy S model, the i9000B. Not too many changes from the T model, and Samsung just published the kernel diffs from the standard i9000 kernel source. Our problem is that we have no official ROM other than the old, slow and boring 2.1 Eclair. Well... there`s a leaked 2.2 ROM but what everybody here wants is to take advantage of all the great mods floating around but of course those can not be flashed in our B devices.
The question I would like to make is "WHY???". Of course the Kernel shipped on those ROMS might not be compatible, but as I said before we have access B sources so we could provide our own compiled kernels and mix them with the internation ROM which are of course binary compatible since the underlying harware is almost the same... but I guess that would not probe to be sufficient! What parts of the android platform could be device specific aside from kernel??? I heard something about the modem thing being specific to the geographic area...
Thnx in adv!
HI! I need your help. My samsung s5 clone doesn't open anymore. When i tried to open it, it'll just stay on black screen but when i press the power button it'll vibrate. Please help me. I think restoring will fix this but i don't know how.
MT6572
SM-G9008
Quad-core (but i'm not sure if it's true)
2Gig ram(i'm not sure with this too.)
Manufacturers of clone devices almost never release their factory ROM's, or even their kernel source which breaks the GN GPLv2 license. Therefore you won't be able to find the stock ROM for your phone.
In addition to that we don't usually support cloned devices on XDA in terms of custom ROM's because the developers of custom ROM's buy the real phones, not clones.
Thread closed.
I'm using this phone for a while, but since it is made in China and lack supports
It is still in 2.3.x branch, which contains some known security issues
So, I'd like to know how to build a custom rom for it, my friend told me Slim is one of the most stable custom ROM on the run, and fits my minimaist style, can you give me some advice?
P.S. I've been looking into many Chinese sites, but still I can't get the full list of device tree
EDIT: seems it is a mtk6516 CPU with dual SIM
it has some different model names:
Meizu G11
Chianjing A007 or V7
found some maybe useful specs.
http://forum.xda-developers.com/showthread.php?t=1501849&page=2
I have been waiting quite some time for a custom rom for SM T819 but I haven't see much progress in this. I looked for a device with similar specs for our device and came across this device which already has a Lineage OS build available. Its practically the same device but with a different screen size.
LeEco Le 2 Specs: http://www.gsmarena.com/leeco_le_2-8053.php
LeEco Le 2 Lineage OS Github Repo: https://github.com/LineageOS/android_device_leeco_s2
It will be a good starting point as I think for getting a custom rom for this device with a great potential. I have read that having spec devices is a great start to porting a ROM from one device to another without specifically building it from the source. However it includes a few build prop tweaks and changing few lines on kernel which I have no technical expertise.
Looking forward for your thoughts.
It's true, personally I don't have this tab but I had experience with a Tab I used which was similar in specs with S4 Mini ..
You'll get bugs though and you can base device tree from the Leeco Phone to build ROMs
Anything new here?
Seems like @tuxing built a modified T813 LOS build for himself, but of course no LTE in there. https://forum.xda-developers.com/showpost.php?p=73992901&postcount=552
i really hate the lack of support for LTE Tablets :/
Hi guys, I don't know if i am on topic but 'cause of this lack of ROMs for the T819, can I install the one for the T813? I know there is no LTE, but if I wanna try the ROM can I install it or it is incompatible with the T819?
kinglolloman said:
Hi guys, I don't know if i am on topic but 'cause of this lack of ROMs for the T819, can I install the one for the T813? I know there is no LTE, but if I wanna try the ROM can I install it or it is incompatible with the T819?
Click to expand...
Click to collapse
Not that easy, but I had a nice chat session with @LuK1337 and he explained me how to get things built and boot on T819: https://forum.xda-developers.com/tab-s2/general/guide-build-lineageos-15-1-t819-t3721477
It's not that difficult as I thought. @LuK1337 told me it's simple and even I managed to get it working.