Hi everyone,
I have recently went into a business of messing around custom ROMs for my good old LG Spirit 4g. I am trying to port some newer android version ROMs (e.g LOS 16) to my phone, but not experiencing much success. The question I have is what is the minimum to make ROM from another device to at least make it to bootscreen, where I probably could hook up some adb logcat and debug it futher? I am using builds from Moto G3 which is essentially an identical device in a different body, with a much wider developer support . I have tried to do some things already, using files from roms compatible with my phone:
- Replace kernel in boot.img
- Edit updater_script (usually has very little difference to one from LG)
Might look not sufficient, but that's what I was able to find online. Would really appreciate any help!
Related
Hello XDA,
I have bought a new android device for myself today, the Sharp FX Plus (Model: ADS1) and I've been browsing on the site to find some compatible roms; But no luck. I've used the forums before to successfully root and put a rom on my ASUS tablet with no issues, but this one is a mystery. Is there a thread with what roms are compatible with my phone or has nobody ever really looked into this phone? I've tried to google it with no luck, either. The phone is already rooted, I got that far, I just can't find any roms that are 'confirmed' compatible with it.
Thanks to whoever replies!
P.S. I'm slightly new to the whole custom rom thing - but I do somewhat understand the basics.
metoo!
I too have a sharp fx plus ads1. I have my phone rooted but am having no luck finding a custom rom. I understand it is kind of an entry level android and maybe out of date but it has all the capabilites I need. I also know enough to root my phone and install a rom but not good enough to actually create my own custom rom. Is there anyone that has the time and enjoys doing so that would help out with a custom rom for these phones? I found a page that mentioned updated to 3.2 with a new rom but there was no link for the rom so I'm thinkning it was a fake. Any help or suggestions would be appreciated.
ctucker0416 said:
I too have a sharp fx plus ads1. I have my phone rooted but am having no luck finding a custom rom. I understand it is kind of an entry level android and maybe out of date but it has all the capabilites I need. I also know enough to root my phone and install a rom but not good enough to actually create my own custom rom. Is there anyone that has the time and enjoys doing so that would help out with a custom rom for these phones? I found a page that mentioned updated to 3.2 with a new rom but there was no link for the rom so I'm thinkning it was a fake. Any help or suggestions would be appreciated.
Click to expand...
Click to collapse
EDIT: I posted in Misc Android Development section here, trying to put the information in a centralized area for any potential development on this device.
Recompiled the CM7 Kernel as a test using the device's config.gz, working on getting the CM7 source to go (its being tricky lol). I have a test CyanogenMod 6.1.2 ported from a Z71 that runs, as well as a modded stock 2.2.2 ROM. A "dirty-port" test of a Z71 CM7 rom boots with some mods (no radio, networking, etc..) - so there may be some hope for this lil thing!
Hope that helps
Basically, I'm trying to port this rom to the Samsung Vibrant. I am using the latest Cyanogen Mod nightly as the base rom and following the tutorials for porting roms to other devices. I just want to make sure that I have properly checked everything, since I'd rather not test the rom on my device without community help. I've checked to make sure that the resolutions are similar, etc. My question is, is there anything I'm missing or anything that I should fix?
So, Since the Cyanogenmod source is so big (I heard that it has 19GB), people like us who have gay as slow internet have no chance of even trying to cook a ROM for our unsupported devices.
Since I can't download the whole CM source and I see awesome ROM's out there, I Ported one ROM called Cyanfox (which was made for Samsung S2 i9100) to Samsung Infuse 4G using Beanstalk ROM as a base. I followed a guide which asks me to replace some folders and edit some files. It was walking fine. Then came an update to both the ROMs, Thinking that cince it is a update, it will have the updated apps and source, I tried porting them again but this time Beanstalk updated ROM as a base cause a bootloop while the Beanstalk old ROM works fine as a Base ROM.
Now what I don't get is, why is Beanstalk new ROM not working as a base? (Since the new Beanstalk ROM will have updated Source, I want to use that ROM as my base.)
And the second question is, what files does actually matter when you are Porting or cooking an Android ROM? (I mean like windows works on all kind of PC's all it needs is the drivers right? The drivers actually matter on windows)
And the 3rd question is can I update the source files somehow without downloading the whole 19GB CM source and if possible how?
The 4rth is, I heard from somewhere that boot.img is the file which separates the phones? Then why can't we just port ROM's by replacing boot.img since these two phone's are from the same vendor and it has likely specs. (Which is not possible I think)
I am really really a newbie to this thingies, I just wanted to clear out these things. Sorry for my noobness.
Thanks!
Hello everyone! I am a little new to this, so please take it easy on me. I have actually never created my own Android ROM via the AOSP, but I have opened up Zip files for ROMs other developers have created and have been able to do basics.
I recently bought this device: MPie G7 (gearbest . com/cell-phones/pp_76182.html)
As you can all tell, it is not exactly a very popular phone. So, finding source code for this phone's ROM is basically, impossible. I have also been unable to find the manufactures website address either (anyone have any ideas?).
Anyway, here are my very noob questions. I am obviously planning on hitting base with the AOSP code, but with Lollipop. This poses a new problem to me, because I cannot find the source code, how am I supposed ot create a kernel specific ROM? This thing runs on a MTK, most precisely: MTK6582. It came with Android 4.4.2 (KitKat).
I am also worried about one small other thing, which is the gestures. If my phone is on standby, screen is off, I can do gestures on the off screen to do certain things. Similar to the OnePlus One. But, I am worried I will not be able to do that if I build my own ROM from source.
Anyone have suggestions? Or can possibly help? Thank you very much. All your help is appreciated!
By
omarquazi said:
Hello everyone! I am a little new to this, so please take it easy on me. I have actually never created my own Android ROM via the AOSP, but I have opened up Zip files for ROMs other developers have created and have been able to do basics.
I recently bought this device: MPie G7 (gearbest . com/cell-phones/pp_76182.html)
As you can all tell, it is not exactly a very popular phone. So, finding source code for this phone's ROM is basically, impossible. I have also been unable to find the manufactures website address either (anyone have any ideas?).
Anyway, here are my very noob questions. I am obviously planning on hitting base with the AOSP code, but with Lollipop. This poses a new problem to me, because I cannot find the source code, how am I supposed ot create a kernel specific ROM? This thing runs on a MTK, most precisely: MTK6582. It came with Android 4.4.2 (KitKat).
I am also worried about one small other thing, which is the gestures. If my phone is on standby, screen is off, I can do gestures on the off screen to do certain things. Similar to the OnePlus One. But, I am worried I will not be able to do that if I build my own ROM from source.
Anyone have suggestions? Or can possibly help? Thank you very much. All your help is appreciated!
Click to expand...
Click to collapse
Why don't you list down some of the specifications of your phone and compare them with other mediatek devices!!!
That way if u have the stock ROM of the phone then u can port ROMs from another mediatek device like xolo q700i which has a dedicated thread!!! xolo q700i has many different number of ROMs !!! That way by zip based theming and porting you might be successful in at least creating a ROM for yourself which u can use as a base for different roms!!!
The way I see it if you don't have source or downloadable ROM from your OEM, you have two options:
- like @thecoolster said you could try flashing ROMs from similar devices, and hope you don't end up stuck with a soft brick.
- or, likely your device can be easily rooted (in the settings perhaps?) if it isn't already. Then you can make nandroid to give yourself a stock ROM to cook.
Actually porting your ROM from a developer device tree and AOSP or CM is hard if you are only a hobbyist cook.
Even with a cooked ROM, you'd need a recovery that lets you flash it or you'd have to use SP flashtool and make your own config files for the flash.
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.