Before i download a rom of op3 with my 90kb/s net. I need some instructions.
I'm thinking to port a rom from oneplus 3, since OP2 and OP3 have same screen res and both are arm64 so it shouldn't be that complicated, right?.
1: is it okay to port a rom from OP3 to OP2?
2 How many of you have ported any rom? Does it really works?
3: Do i have to ask permission from the owner to port or i can give credits to him and link to his Original thread?
I've some more questions but not coming in my mind, hope that my above questions get answered so i may think to port a rom from op3 to op2.
Thanks.
chetan_1215 said:
Before i download a rom of op3 with my 90kb/s net. I need some instructions.
I'm thinking to port a rom from oneplus 3, since OP2 and OP3 have same screen res and both are arm64 so it shouldn't be that complicated, right?.
1: is it okay to port a rom from OP3 to OP2?
2 How many of you have ported any rom? Does it really works?
3: Do i have to ask permission from the owner to port or i can give credits to him and link to his Original thread?
I've some more questions but not coming in my mind, hope that my above questions get answered so i may think to port a rom from op3 to op2.
Thanks.
Click to expand...
Click to collapse
As i know if port rom,, device need same cpu,,
Why not building rom from source?
Droidcore said:
As i know if port rom,, device need same cpu,,
Why not building rom from source?
Click to expand...
Click to collapse
Oh! That's why it didn't boot when I tried to mix op2 RR and op3 Pac man. They both have different cpu.
Google nexus 6p won't work maybe, since it have different resolution.
Droidcore said:
As i know if port rom,, device need same cpu,,
Why not building rom from source?
Click to expand...
Click to collapse
And as per building from source, I don't have that much knowledge about these stuffs. So it's pretty impossible for a noob (newbie) to make from source.
Resolution d' not affect porting.. Btw if u want to port some stuff check out yu forum "annabathina " is the dev who port different ui for yu phone..."
Edit: i also know porting but only in mediaktek phones snapdragn never tried cz lake of linux
---------- Post added at 03:55 AM ---------- Previous post was at 03:29 AM ----------
N if u want to port cm base rom u can try this btw..
Take cm oneplus2 as a base rom
Take any cm rom u want to port(port)
Now delet app,framework,priv app,media,font from base rom
Copy all this folder from port to ur base rom folder
2. Copy lib and bin from port to stock but remember dont replace it .(means only copy xtraa files from port or keep base rom libs as it is)
3.replace storagelist.xml from base rom to port rom framework which u copied in base( framework res apk)
4.zipp ur base again and try to flash
neelsolanki said:
Resolution d' not affect porting.. Btw if u want to port some stuff check out yu forum "annabathina " is the dev who port different ui for yu phone..."
Edit: i also know porting but only in mediaktek phones snapdragn never tried cz lake of linux
---------- Post added at 03:55 AM ---------- Previous post was at 03:29 AM ----------
N if u want to port cm base rom u can try this btw..
Take cm oneplus2 as a base rom
Take any cm rom u want to port(port)
Now delet app,framework,priv app,media,font from base rom
Copy all this folder from port to ur base rom folder
2. Copy lib and bin from port to stock but remember dont replace it .(means only copy xtraa files from port or keep base rom libs as it is)
3.replace storagelist.xml from base rom to port rom framework which u copied in base( framework res apk)
4.zipp ur base again and try to flash
Click to expand...
Click to collapse
I tried this method.
I took RR as base for op2 and Pac man of op3 as port.
I tried all the following methods. Everything is well and good till flashing, but when I try to go in system it just stuck in Oneplus boot image and then force me into recovery.
build from source dude.. Dont flash anything you find or make do you want a hard bricked device?
suraj.das said:
build from source dude.. Dont flash anything you find or make do you want a hard bricked device?
Click to expand...
Click to collapse
I'm not quite sure about these stuffs. I don't know how these stuffs work so I thought to start with porting roms. And hard brick is still okay for me, gone through many times, easy to recover.
Watched number of videos on YouTube, I also tried to make Virtual Linux on my pc. But didn't work.
Best way to start is dualbooting linux on your PC and following a guide on how to compile rom.
this here should be just fine https://raw.githubusercontent.com/nathanchance/Android-Tools/master/Guides/Building_AOSP.txt
just download the source of the ROM you want to compile. [The source is around ~20GB so be patient]
PM me if you hit a deadend
suraj.das said:
Best way to start is dualbooting linux on your PC and following a guide on how to compile rom.
this here should be just fine https://raw.githubusercontent.com/nathanchance/Android-Tools/master/Guides/Building_AOSP.txt
just download the source of the ROM you want to compile. [The source is around ~20GB so be patient]
PM me if you hit a deadend
Click to expand...
Click to collapse
Thanks buddy, but i can't do this unless I get a new stable high speed net. 20gb with my current speed will take me around 4 days and if sometime the net went down then again ill have to download the whole file. I will try to make request to my dad about this.
Related
I have ported The Miui ROM from moto g forms and started fixing it .
I'm a new dev here and I'm also 14 years old so plz be kind.
The ROM is still in beta stage.that means so Much Bugs.
IF u want to ask any Thing just ask or pm me.
Taken by me
Some screens:
http://www.mediafire.com/view/tax7vz10cfls2sj/Screenshot_2015-04-29-16-31-57.png
http://www.mediafire.com/view/ap8gikol92k8p4t/Screenshot_2015-04-29-16-32-56.png
http://www.mediafire.com/view/ozbknod19znjyti/Screenshot_2015-04-29-16-50-34.png
http://www.mediafire.com/view/u9npx31os4ns0fa/Screenshot_2015-04-29-16-49-30.png
Another one.
I am ready to test that ROM and even try and help u in fixing the bugs
blackwings66 said:
I have ported The Miui ROM from moto g forms and started fixing it .
I'm a new dev here and I'm also 14 years old so plz be kind.
The ROM is still in beta stage.that means so Much Bugs.
The ROM is booting and working .
Working :
1 : WiFi
2: screen and touch
And a lot not knowin yet.
Bugs:
1: no Sound
2: no ril
3:no screenshots
4: not conformed but sdcard
Still testing
So I can't test the ROM right now because of a bug .
When the device boots for the first time and you go after WiFi
It will search for sim card and the ril is not working soo it won't finish searching .
So as I said it's still beta and testing.
If u won't to ask anything there u go and if u want to help u can pm me.
Q: When it's coming ?
A: soon after fixing some bugs.and it will take a lot of time to upload because of my slow internet.
If there are any devs how want to help plz pm me.
Now I'm building beta 2 and will test it soon .
If it works I will start uploading.:laugh:
Note : if u pm me and I didn't answer plz wait I have exams and I'm busy or testing roms
Click to expand...
Click to collapse
MIUI is open source, and v6 is out. I recommend you try porting from the source directly. It may/may not require more effort. BTW, I had tried porting MIUI also, and RIL was working then. Try copying some related libs. I had used Aapav's CyanogenMod 11 as the base ROM.
heavenly_awker said:
MIUI is open source, and v6 is out. I recommend you try porting from the source directly. It may/may not require more effort. BTW, I had tried porting MIUI also, and RIL was working then. Try copying some related libs. I had used Aapav's CyanogenMod 11 as the base ROM.
Click to expand...
Click to collapse
I tried every ril and from etc and bin but still notworking
Link is up guys and creating fourm soon
But not now phone battery is dying:crying:
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!
Hi, I started to port MIUI 8 based on JDCTeam Optimized CM13.
So I ported rom and here starts the problem.
What the problem is? Bootloop.
And I thought: 'Hey, let's make a logcat'
But then I realized that I don't know how to solve my problems with logcat.
So I came to you, because I think there will be one or more helpful people!
Also, when I will finish rom, then I will ask Base and Port rom makers to allow me publish rom, and I will add them and person that will help me solve my problem to credits
Base rom is JDCTeam Optimized CM13
Port rom is HTC One M7 MIUI8
Oh, I almost forgot logcat: paste . ee/p/1KK1 ( there is no space in this link, I just don't have 10 posts to post links )
Nothing?
Guys i am serious in this Section of development .
I am trying to make more up to date android roms for explay fresh and for the clones but, my guides giving me lots of bugs which i dont like and i am unable to fix them.
Whenever i am trying to contract the devs of a120/wr/ef then either they reply without main question's answer or they just ignoring completely .
Why ??????
Its a development group so u should share/help others to make their project successfull but its actually going fully selfish mind here
If you help then i am also going to add credits of you guys but u guys not even respond me.
Hope u got my words
If u dont/Ignore here also then I dont have words
sahasoumitra007 said:
Guys i am serious in this Section of development .
I am trying to make more up to date android roms for explay fresh and for the clones but, my guides giving me lots of bugs which i dont like and i am unable to fix them.
Whenever i am trying to contract the devs of a120/wr/ef then either they reply without main question's answer or they just ignoring completely .
Why ??????
Its a development group so u should share/help others to make their project successfull but its actually going fully selfish mind here
If you help then i am also going to add credits of you guys but u guys not even respond me.
Hope u got my words
If u dont/Ignore here also then I dont have words
Click to expand...
Click to collapse
The device is old and dead. The processor won't support any more future OS versions. Even Nougat couldn't be stable too. Better get a new device if you want to enjoy development.
If u think so bro then i cant say anything.
Nougat will be stable soon because mt6582 Kernel 3.4.67 Already able to boot Nougat
Stable rom depends on the rom you port so if ur rom is already buggy then u cant do anything
Only way is to build from source but thats need kernel source which is missing for a120
sahasoumitra007 said:
If u think so bro then i cant say anything.
Nougat will be stable soon because mt6582 Kernel 3.4.67 Already able to boot Nougat
Stable rom depends on the rom you port so if ur rom is already buggy then u cant do anything
Only way is to build from source but thats need kernel source which is missing for a120
Click to expand...
Click to collapse
We have custom kernel that can be used to build ROMs.
Dear mxp users there are many other ROMs available for our device except but the Chinese ROMs.Flyme os is there for mxp but it doesn't have volte. I'm not a developer but I would like to try porting miui for our device instead of waiting for someone to port someday. I am a newbie and if anyone is interested in this porting then we can work together and make this port.
The similar phone next to Mi4i that has the same CPU(SD615) of our mxp is micromax yu yureka plus.It also has the same resolution and the ROM has volte.This is the reason why I chose yu yueka plus over Mi4i.
The custom ROM that has volte and Chinese ROM for yu yureka plus is in the link below,
https://forum.xda-developers.com/yu...chrom-miui-8-marshmallow-yureka-t3609071/amp/
I tried porting it today but it failed.
I request you guys to help me with this porting process.
The base ROM I used for porting is
Spectrum MM Volte
https://forum.xda-developers.com/moto-x-play/development/rom-spetrum-mm-volte-t3462690/amp/
Also tell me whether this port is applicable for our device.
Thankyou.
I'm not a developer myself, but I would love to see MIUI ported to our device. Would definitely go out testing it.
ssuurryyaa101 said:
Dear mxp users there are many other ROMs available for our device except but the Chinese ROMs.Flyme os is there for mxp but it doesn't have volte. I'm not a developer but I would like to try porting miui for our device instead of waiting for someone to port someday. I am a newbie and if anyone is interested in this porting then we can work together and make this port.
The similar phone next to Mi4i that has the same CPU(SD615) of our mxp is micromax yu yureka plus.It also has the same resolution and the ROM has volte.This is the reason why I chose yu yueka plus over Mi4i.
The custom ROM that has volte and Chinese ROM for yu yureka plus is in the link below,
https://forum.xda-developers.com/yu...chrom-miui-8-marshmallow-yureka-t3609071/amp/
I tried porting it today but it failed.
I request you guys to help me with this porting process.
The base ROM I used for porting is
Spectrum MM Volte
https://forum.xda-developers.com/moto-x-play/development/rom-spetrum-mm-volte-t3462690/amp/
Also tell me whether this port is applicable for our device.
Thankyou.
Click to expand...
Click to collapse
yu yureka would fail since it has a 64bit architecture where as this device has a 32 bit one. You're better off trying with Mi4i since the architecture is the same. But I suggest you do it the using the patch rom method since porting rom from another device can get really messy.
Here is a guide: http://en.miui.com/thread-9630-1-1.html
Note: It is not an easy and quick process. You're have to learn about resolving rejects. I tried doing it once, there were a ton of rejects. I resolved around half of them until I grew tired of doing so. So I gave up on it completely, so just a heads up. You need to have a lot of patience.
amunarjoh said:
I'm not a developer myself, but I would love to see MIUI ported to our device. Would definitely go out testing it.
Click to expand...
Click to collapse
Me2 amunarjoh and will do my best to port this ROM for our device. :laugh:
rm-rfasterisk said:
yu yureka would fail since it has a 64bit architecture where as this device has a 32 bit one. You're better off trying with Mi4i since the architecture is the same. But I suggest you do it the using the patch rom method since porting rom from another device can get really messy.
Here is a guide: http://en.miui.com/thread-9630-1-1.html
Note: It is not an easy and quick process. You're have to learn about resolving rejects. I tried doing it once, there were a ton of rejects. I resolved around half of them until I grew tired of doing so. So I gave up on it completely, so just a heads up. You need to have a lot of patience.
Click to expand...
Click to collapse
Ohh I didn't know that.Sure rm-rfasterisk but can we preserve volte?
ssuurryyaa101 said:
Ohh I didn't know that.Sure rm-rfasterisk but can we preserve volte?
Click to expand...
Click to collapse
Are you sure that either of the devices is 32-bit?
Coz the site says both the devices have 64-bit architecture.
Moto x play
https://www.devicespecifications.com/en/model/dd8b3569
Yu yureka plus
https://www.devicespecifications.com/en/model/daa4353a
ssuurryyaa101 said:
Ohh I didn't know that.Sure rm-rfasterisk but can we preserve volte?
Click to expand...
Click to collapse
Yes of course. If you know what you're doing. Even if you fail to preserve VoLTE, you could always create a patch.
---------- Post added at 06:59 PM ---------- Previous post was at 06:55 PM ----------
ssuurryyaa101 said:
Are you sure that either of the devices is 32-bit?
Coz the site says both the devices have 64-bit architecture.
Moto x play
https://www.devicespecifications.com/en/model/dd8b3569
Yu yureka plus
https://www.devicespecifications.com/en/model/daa4353a
Click to expand...
Click to collapse
The SoC on this device is 64 bit but the firmware is 32 bit because Motorola is super retarded whereas the YU device has firmware which is also 64 bit. It's really hard to port a natively 32 bit device to 64 bit.
rm-rfasterisk said:
Yes of course. If you know what you're doing. Even if you fail to preserve VoLTE, you could always create a patch.
---------- Post added at 06:59 PM ---------- Previous post was at 06:55 PM ----------
The SoC on this device is 64 bit but the firmware is 32 bit because Motorola is super retarded whereas the YU device has firmware which is also 64 bit. It's really hard to port a natively 32 bit device to 64 bit.
Click to expand...
Click to collapse
Got it
Hey guys I started working on porting process and was able to solve few rejects but not all. I would like to get some suggestions that which ROM would be best suited to get less rejects while porting.
Hi guys today I managed to make the zip file(miui 8 lux) and was able to flash it but can't get past boot. Could someone help me with this? I'll upload the zip later this day and you are most welcome to edit and make this working.
ssuurryyaa101 said:
Hi guys today I managed to make the zip file(miui 8 lux) and was able to flash it but can't get past boot. Could someone help me with this? I'll upload the zip later this day and you are most welcome to edit and make this working.
Click to expand...
Click to collapse
Here is the link to the zip
https://drive.google.com/open?id=1b6h7_JhH8EyxRGt_XCSz4JnPEV5jfBWn