Hi ,
Sorry if this is wrongly posted.
I'm New to building a rom and i've read up on multiple threads on how to port/build etc,
but i'm confused with one thing, its said that the base rom should be the one that is able to run on the specific device.
I'm using the Pantech Vega Iron 2 IM-A910K , there are only 1 vietnamese rom , a Chinese rom which are both translated versions of the original korean rom with basic editing of the SMS limit and such, I was using The PAC man rom on both Sony Xperia Z1 and Z ultra before and i loved the functions it has, i wish to port this over to this device too but seems unsuccessful.
Is anyone able to tell me if i am able to build a rom for this device with the above mentioned avail stock modified roms as base or i have to fully complile a new one?
This Phone has great specs but Its just strange that few devs work in it, even the old Vega Iron A870 only had a multitude of roms including CM after about half a year later or so, as i just got this phone i dun really wanna leave it there unused till then hence i wanna attempt to build the rom myself.
any response is greatly appreciated.
Thanks.
Some of us are not into lollipop firmwares... I hope sir Albe95 will also create a s6 themed rom based on kitkat for s4 gt-i9505. Currently i'm using his albe95 3.0 which is based in note 4.. i hope sir albe95 will grant my wish and i'd be very thankfull for that.. not just myself but also others who still uses kikat firmwares..
I understand there are more than a few people who don't like the changes Android 5.0 brought to the table, but to expect developers to cater to a minority of a minority of the Android userbase is nothing more than wishful thinking. Why should Albe or any developer for that matter develop for an old version of Android? That would be like asking AntaresOne to continue support of CM11 after he released CM12. It's not going to happen.
You might as well upgrade now and get it over with, because your next device will have at least Android 5.x in it anyway. Holding off only delays the inevitable.
Well.. it's upon him.. there is no problem with that.. if he can create then i could be thankful.. if not then ok.. it's just fine... i can still use his other roms.. or specifically the albe 3.0 note4 based rom.. im not forcing him to do that it is just my opinion.
What you posted was a request, not an opinion. Even your statement that "some of us don't like Lollipop," while true, isn't an opinion. An opinion would be "Android 5.0.1 is bad because the white in Material Design hurts my eyes."
Your statement that "it's upon him" smacks of disappointment because he won't cater to you. But continue using Android 4.x while the rest of us go on to Marshmallow. You'll simply be left behind in the dust, like the 2015 Moto E.
Hi there,
I own a Galaxy J500FN and have been unsuccessfully searching the web for a custom rom for my device.
I have used PA on both my S4 and S4 mini and would be very glad (so would many others) if somebody could dedicate some time on working on a build for this device?
It currently ships Lollipop 5.1.1 out of the box.
There is no CWM Recovery build for this device but there is a TWRP Recovery Build that CTxz has kindly developed for us.
I am more than happy to flash experimental builds onto my device to help develop a custom ROM for it.
Thanks a lot!
Kyle
P.S: As many others have found, all root methods currently known for this device will trip the knox security.
No plans as we don't dev for devices we don't own or have access to. It is not on our radar at all, as with most Samsung devices.
@Pirateghost i can provide you all the files of j5 that you needs.
Avigupta.1996 said:
@Pirateghost i can provide you all the files of j5 that you needs.
Click to expand...
Click to collapse
And what exactly does that do for us? That doesn't put a device in a developer's hand and they have ZERO way to test it. We know nothing about the device and we don't care to. It is not on the radar, it is not in the cards....
NO.
Not going to happen.
Please realize that developing for a device isn't easy. Even well documented ones bring along lots of hiccups along the way. There is no way in hell that we will take on a device request for a device that we don't own or plan on ever owning.
Here's a little FYI for you: we prefer Nexus devices or devices where the manufacturer/OEM is willing to allow/support bootloader unlocks, roms, development.
My advice to you: Learn how to bring up the device yourself, and build unofficials for yourself. This site was founded on being a resource BY developers FOR developers. Use the information available to you to build your own.
Is there any way to get Android Lollipop on the Galaxy Core Prime SM-S820L? I have read about custom ROM's but I still don't know much about them and can't find any for this model. If anyone has found or created a way to flash a custom ROM onto this device, please let me know.
Liantik said:
Is there any way to get Android Lollipop on the Galaxy Core Prime SM-S820L? I have read about custom ROM's but I still don't know much about them and can't find any for this model. If anyone has found or created a way to flash a custom ROM onto this device, please let me know.
Click to expand...
Click to collapse
I also own this device, and unfortunately there is very limited support in the custom Rom department. If there was to be a lollipop Rom, someone would either have to port one somehow, or build it from source. Given the development rate for this device, I don't predict it happening anytime soon, sorry to say.
not going to happen
i have been trying since february the answer i got from my carier was samsung is contracted not to support this device thats why that is so hard to find samsung told me to take the device to bestbuy to force update if they could probably irrelavent but maby it helps
SM-S820L Got the Shaft!
Yup! This seems to be the future for the SM-S820L, or lack of future I should say.
I too have the Samsung Galaxy Core Prime SM-S820L. I have spent lots of hours scouring the internet looking through every android related forum in hopes of eventually finding someone that is undertaking much needed programming to build a custom ROM for this CorePrime version.
If you are looking for a custom recovery to use. I can point you to my and others posts over at Needrom. The best I can offer is an unofficial TWRP release, but it DOES work! It does for myself at least and I am no Android Guru whatsoever.
I guess I am not allowed to post Links in any of my posts yet because I am still a NOOB on these forums. I'll PM you with some direction my friend!
I cannot take credit for coming up with any of that software. I simply rooted around long enough to compile a collection of tools and files that worked for me to modify the Recovery of my SM-S820L.
:good: Feel free to shoot me a Private Message on this site or to my personal Email....... [email protected]
I would love to help out as much as I can with modding your phone. Like I said, I'm not a proffesional but I have read up on the procedures used and been successful with my own Galaxy Core Prime:laugh:
Hey folks,
I know most people have already given up on this phone because it didn't sell well and doesn't have much support. But like the rest of us still browsing this forum, I still have my M9 and still believe it can be improved. I am currently working on a project to build a clean AOSP rom (without any kinky modifications, just a nice stock rom built directly from the AOSP sources.)
I've never undergone such a project, and I've been reading a lot about the steps necessary to realize this goal. I've been following Sony's excellent AOSP building guide so far. I have the android sources downloaded, all I'm missing are the proprietary files (from the device itself, most likely) and the ability to set up the proper device trees/manifests. I was planning to use the Cyanogenmod device tree because a lot of work has gone into it and, given that my M9 is currently running one of the CM13 nightlies, is pretty stable and works with new device firmwares. I know there is already a guide on the Cyanogenmod wiki for building CM for the M9, but I am not building CM at all, I want to build a 100% stock AOSP rom.
Can anybody help me proceed from here? I've downloaded the https://github.com/CyanogenMod/android_device_htc_hima-common tree and put it into device/htc/himaul but I'm not sure where to go from here. The extract-files.sh script does not work (because there is no CM helper script). Does anyone have any experience with this sort of thing?
Thank you very much in advance. I hope this will help everyone as I know many people have been looking for a non-CM AOSP rom for this phone (some do not agree with CM design philosophies). I definitely plan to share this rom and write a guide to help other projects when this is figured out.
I look forward to hearing back,
vivremetrique
Hi, I have no idea on doing roms, but you could help be your tester ...
whatever you need, talk me
---------- Post added at 10:22 PM ---------- Previous post was at 10:19 PM ----------
It would be good to make a ROM Nougat if possible
AOSP 100% and cyanogenmod device tree are totally different
I don't know what does it take to have a full aosp working rom, but I'm sure that CM code has nothing to do with it.
anyway, with the right work it shouldn't be so hard since m9 shares hardware with nexus 6p...
Frug01 said:
[/COLOR]It would be good to make a ROM Nougat if possible
Click to expand...
Click to collapse
Yes, the sources I will be building from will be Nougat sources (7.1 experimental sources). Thank you for offering to test once this is done.
throcker said:
AOSP 100% and cyanogenmod device tree are totally different
I don't know what does it take to have a full aosp working rom, but I'm sure that CM code has nothing to do with it.
anyway, with the right work it shouldn't be so hard since m9 shares hardware with nexus 6p...
Click to expand...
Click to collapse
I mean the operating system will be 100% AOSP, but obviously since this is not a Nexus/Pixel device the device tree will not be included in AOSP... The device tree/proprietary files have nothing to do with the actual user experience, they are simply needed for support of the hardware/stock kernel if desired/camera or wireless firmware. I don't see the sense is rewriting these from scratch given the time and effort already put into them by CM devs/those in the Cyanogenmod threads in this forum.
It would be great if some of you could help gather helpers for this project. It seems that properly setting up the device and getting ready to build the rom are all that is missing, so I'm hoping this goes relatively quickly.
So I believe I've made some progress. I downloaded the htc vendor files, the htc msm8994 kernel files, the hima-common tree, and the himaul tree. There is still something missing, because running the "lunch" command warns that it cannot locate the config makefile.
I found references to cm in cm.mk in device/htc/himaul/cm.mk but I don't know what to replace them with and I don't want to download the whole CM source tree as well.
Can anyone shed some light on this issue?
I can't help you, but that is a very good idea! Hope you can solve this issue.
Nice project, I would love to see AOSP Nougat on our M9! I'm not a dev who could help you with the building process, but maybe the dev of the CM14 port for M8 could give you an advice. Good luck!
I think you are underestimating the efford and skills it needs. Even with official Kernel Source released it took some really effort to make for example the camera work. If you don't know hot to setup a device tree for an existing rom, then I feel the skills required exceeding the ones you have. I don't want to offend you, but maybe it's better to take a step back an learn how to add this to an AOSP Marshmallow rom, instead of thinking about porting it to Nougat. If it would be that easy, wouldn't a ready to use Nougat Version of any other popular Rom for the m9 be out already?
Any telegram group of One M9???
Enviado desde mi HTC_M9u mediante Tapatalk
Adromir said:
I think you are underestimating the efford and skills it needs. Even with official Kernel Source released it took some really effort to make for example the camera work. If you don't know hot to setup a device tree for an existing rom, then I feel the skills required exceeding the ones you have. I don't want to offend you, but maybe it's better to take a step back an learn how to add this to an AOSP Marshmallow rom, instead of thinking about porting it to Nougat. If it would be that easy, wouldn't a ready to use Nougat Version of any other popular Rom for the m9 be out already?
Click to expand...
Click to collapse
That effort would.not be wasted. Once the solution to the camera problem is solved, it's solved for all versions, not just Marshmallow. We can reuse the kernel source and firmware blobs in N. I reckon that we don't have a rom because nobody is working on it.
If it would be that easy, why isnt there an official (or even inofficial) cm 14 for m9 out, as it already got an official cm 13? If everything you needed would be to just switch everything else to cm 14 and reuse the mm kernel source and blobs?
Adromir said:
If it would be that easy, why isnt there an official (or even inofficial) cm 14 for m9 out, as it already got an official cm 13? If everything you needed would be to just switch everything else to cm 14 and reuse the mm kernel source and blobs?
Click to expand...
Click to collapse
Because there is almost zero demand for one. People in the CM13 thread are actively discouraged from even mentioning CM14. How can we develop the ROM if we don't have anybody working on it?
Given CM's automated device tree preparation system, I doubt it would take more than a simple source tree update to Nougat to start compiling a 7.x ROM (whether it works perfectly or not, it would be a start).
Well then I would say, a way to start might be to try compile a booting cm 14 for the m9. Last time I looked there has been at least a device tree prepared for cm 14. I guess that would be the easiest way to test, if you might be succesfull with it
Any news @vivremetrique ? Or did you drop the project?
While it is possible to build cm14.1 for the M9, I was unable to make it see the sim card after days of trying. something in libril or possibly the firmware I have makes it not work.
Trainwr3ck said:
While it is possible to build cm14.1 for the M9, I was unable to make it see the sim card after days of trying. something in libril or possibly the firmware I have makes it not work.
Click to expand...
Click to collapse
If it is the same Problem I had with a CM13 based rom, then the build.prop is missing some Values to detect network. I took them from a working one and put them in the BoardConfig by hand
can't help, but my hopes are so high for this one!