I have asked Dumtara Senior Developer from XDA to help us with Development of CM11 / 12 . I would need some help in uploading the following on GITHUB and also some volunteers to test the builds which are being completed
device tree, kernel source & vendorblob for HTC 820
ypkonline said:
I have asked Dumtara Senior Developer from XDA to help us with Development of CM11 / 12 . I would need some help in uploading the following on GITHUB and also some volunteers to test the builds which are being completed
device tree, kernel source & vendorblob for HTC 820
Click to expand...
Click to collapse
Count me in....
as tester
even count me in for testing ... would have helped u in devlopment also but .. m messed up with some stuff ...
count me for test
Desire 820s with MediaTek chip
Count me 2
Desire 820 dual sim asian version
Sent from my HTC Desire 820 dual sim using XDA Free mobile app
count me desire 820 dual sim asia
Count me for test with htc desire 820 single sim
I'm in for testing, desire 820 dual sim. Also, shouldn't we work to attain S-OFF first? Or will installing a custom rom do that automatically? I'm new to HTC phones.
Any news?
He is not reply
I believe he is fake
Sent from my HTC Desire 820 dual sim using XDA Free mobile app
I lost my HTC 820 Device Hence i was not able to continue on this . Here is the message trial i had with Dumtara ... Any one of you can reach out to him or create GITHUB with device tree, kernel source & vendorblob for HTC 820
He will be able to help you compile the ROM . Please don't state Fake etc... without understanding what went in back ground.
_________________________________________________________________________________________________________
Quote:
Originally Posted by dumtara
Quote:
Originally Posted by ypkonline
Hi Dumtara-
I have a HTC 820 Device and we do not have any major Developers working on this ROM. I would like to know if you can port CM 11 or 12 for this device as the chip set is the same. I am ready to volunteer and test the builds and provide inputs etc... i know it would be difficult without the device but if you can help us get started i am sure we will have others help us.
Regards,
Prashanth
link me device tree, kernel source & vendorblob for HTC 820
I got my New desire 820 delivered.
i wanna join for testing roms.
we need lollipop...kitkat looks horrible
link us the device tree and kernel tree!!!
I know you guys are desperately waiting for development for the device, can someone who has the device build the device tree??? Or link us the device tree and kernel tree??? It will be bit difficult to build a device tree from scratch that too without device with us it difficult...
So help us with device tree, kernel tree and HTC vendor blobs and we'll try compiling cm11 or cm12!!!
What say @dumtara
aashking said:
I know you guys are desperately waiting for development for the device, can someone who has the device build the device tree??? Or link us the device tree and kernel tree??? It will be bit difficult to build a device tree from scratch that too without device with us it difficult...
So help us with device tree, kernel tree and HTC vendor blobs and we'll try compiling cm11 or cm12!!!
What say @dumtara
Click to expand...
Click to collapse
how can I get the device tree ,kernel tree and htc vendor blobs,I'm not a developer ,but I will try to do that.
weijianhui said:
how can I get the device tree ,kernel tree and htc vendor blobs,I'm not a developer ,but I will try to do that.
Click to expand...
Click to collapse
It would be useful if you could provide us the system dump so we get a base to start up!
Note: please do a factory reset before providing the dump!
aashking said:
It would be useful if you could provide us the system dump so we get a base to start up!
Note: please do a factory reset before providing the dump!
Click to expand...
Click to collapse
the dump file is too large, I can put it on baidu skydrive
weijianhui said:
the dump file is too large, I can put it on baidu skydrive
Click to expand...
Click to collapse
Yeah sure but it would be great if you compress to .zip
aashking said:
Yeah sure but it would be great if you compress to .zip
Click to expand...
Click to collapse
I use dd to get the image,and choose the first partion,it is 13gb,is it right?
weijianhui said:
I use dd to get the image,and choose the first partion,it is 13gb,is it right?
Click to expand...
Click to collapse
I don't this the dump will be so huge!!!
aashking said:
I don't this the dump will be so huge!!!
Click to expand...
Click to collapse
what about do a full backup to you,the dump is so huge,and just failed when the dd running last night
Now I'm trying again with dd,it has been 1.5gb,hope this time can be success.
Related
Greetings.
Development for the Moto E has been progressing slowly. The few wonderful developers helping us have released builds with some issues that I'm sure with time will be resolved. They have lives and many other things to do, so I'm only grateful with them for taking the time to code for our "lower end" device.
That being said, and taking in consideration that our devices are low cost, could it be possible for us users to donate a few dollars each to send a device to a dedicated maintainer who is part of a development group?.
I personally love Carbon ROM. I have been using that ROM on different devices and always with the best of results. Simply put, I cannot use any other. It is as stable as CM, has all the right configuration options as AOKP, and coupled with Xposed, you can get your own perfect configuration.
I sent a private message to Carbon Dev, and they told me that as long as they have a physical device on hand, they can add it to the official list of supported devices.
I will donate $20. And I'm sure if every one of you can donate $1, we can easily get a Moto E to Carbon Dev in no time.
Is anyone else willing to help me to reach the proposed goal above detailed?.
Let me know, this could be a great alternative for our device.
I'm in!
I'm in with five bucks. Maybe more, if required.
Thank you for the couple of answers. But I think it's not going to be enough.
A shame since we non-developer users could help ourselves this way.
Anyway, it was worth a try.
I THINK...
Is more importan get oficial support from cyanogenmod... And with this files we can port other roms
xperiafan13 said:
Is more importan get oficial support from cyanogenmod... And with this files we can port other roms
Click to expand...
Click to collapse
I don't think there will be official support for dual Sim variant, as cm does not allow any device specific hacks in their builds. The single Sim variant got a chance.
Hetalk said:
I don't think there will be official support for dual Sim variant, as cm does not allow any device specific hacks in their builds. The single Sim variant got a chance.
Click to expand...
Click to collapse
If we atleast get a stable cm for single sim variant even then there are many who can add dual Sim support to it like there is for moto g...
How can we request cyanogen team to add device to official list...
Any online request page or email?
luvk1412 said:
If we atleast get a stable cm for single sim variant even then there are many who can add dual Sim support to it like there is for moto g...
How can we request cyanogen team to add device to official list...
Any online request page or email?
Click to expand...
Click to collapse
the procedure for making CM support official :
1- All the hardware working on stock rom should work in CM build
2- no FC should be there
3- After making it stable we have to give Full source code ( github repo. ) to CM official devs.
4- they try it for atleast 3 weeks then if they found almost stable CM then they add it to their official support
Sent from my XT1022 using XDA
naveenultimategamer said:
the procedure for making CM support official :
1- All the hardware working on stock rom should work in CM build
2- no FC should be there
3- After making it stable we have to give Full source code ( github repo. ) to CM official devs.
4- they try it for atleast 3 weeks then if they found almost stable CM then they add it to their official support
Sent from my XT1022 using XDA
Click to expand...
Click to collapse
No.. I think you took my question wrong
I was asking that is there any way we can ask cm devs to help us in obtaining stable cm .. (Now I am finding this question as silly )
luvk1412 said:
No.. I think you took my question wrong
I was asking that is there any way we can ask cm devs to help us in obtaining stable cm .. (Now I am finding this question as silly )
Click to expand...
Click to collapse
hahahaha
Thinking same If they help to get CM stable
Sent from my XT1022 using XDA Free mobile app
There is no term as a cm Dev. There are a lot of devs that post to cm builds.
If a new devices comes to the market, a new developer, who owns the device, can build cm for the device and fix issues, if any.
If cm makes it official, that particular Dev will be official maintainer for the device.
luvk1412 said:
No.. I think you took my question wrong
I was asking that is there any way we can ask cm devs to help us in obtaining stable cm .. (Now I am finding this question as silly )
Click to expand...
Click to collapse
I think it would be the same procedure as Carbon Team. Give them a device.
I would not mind giving $20, but we all need to contribute. Giving thanks does not help in this very specific case.
SirRhor said:
I think it would be the same procedure as Carbon Team. Give them a device.
I would not mind giving $20, but we all need to contribute. Giving thanks does not help in this very specific case.
Click to expand...
Click to collapse
Ya I know giving only thanks does not help in this very specific case but I should do that much what I can I do as I am still a 16 year old student who gets rs70 as pocket money per week. So I don't have that much amount of money to contribute but still I can contribute an amount less than or equal to Rs 200 if it helps. It was less amount so I didn't mentioned . I really want development for moto e.
But how come there are loads of Roms for moto g dual Sim variant ???????
Sent from my GT-I9300 using XDA Free mobile app
gtsfreak said:
But how come there are loads of Roms for moto g dual Sim variant ???????
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
Because it has official cm for single Sim and devs in large number
That is exactly why we need to give a device to one maintainer.
SirRhor said:
That is exactly why we need to give a device to one maintainer.
Click to expand...
Click to collapse
Till now we have 28$ but we need 105$ nearly (for me 1$=Rs.65 )
Anyone else willing to collaborate?. To this point, it does not matter if we give the device to CM or Carbon.
SirRhor said:
Anyone else willing to collaborate?. To this point, it does not matter if we give the device to CM or Carbon.
Click to expand...
Click to collapse
I guess people aren't ready to contribute to get a working c-rom.
Let's just wait and watch now.
Hetalk said:
I guess people aren't ready to contribute to get a working c-rom.
Let's just wait and watch now.
Click to expand...
Click to collapse
Faith in humanity switch = OFF.
Hello,
Nokia X2 Open Source Release CD that I just received from Microsoft Mobile can be downloaded from:
-----
URL NOT HERE DUE TO XDA ANTI-SPAM RIGIDITY! See the link in my profile's Github section, go to Releases and download rm-1013_2.0.0.11.tar (only file there)
-----
Sorry about the tar-blob format, kernel source for X2 is there but I'm terribly busy today so no neat kernel source repo merged top of correct CAF tag at the moment.
Use msm8610_defconfig or msm8610-sales_defconfig for building debug (eng) or final (user) SW.
On behalf of Microsoft's Nokia-X Linux kernel devs, have fun modding this!
can you request nokia xl kernel source from them?
Nokia x2 kernel file
How do I load the kernel file to my nokia x2 device?????????
Hello,
Anyone found which CAF version this kernel sources is based, to make proper diff?
jniz2013 said:
Hello,
Nokia X2 Open Source Release CD that I just received from Microsoft Mobile can be downloaded from:
-----
URL NOT HERE DUE TO XDA ANTI-SPAM RIGIDITY! See the link in my profile's Github section, go to Releases and download rm-1013_2.0.0.11.tar (only file there)
-----
Sorry about the tar-blob format, kernel source for X2 is there but I'm terribly busy today so no neat kernel source repo merged top of correct CAF tag at the moment.
Use msm8610_defconfig or msm8610-sales_defconfig for building debug (eng) or final (user) SW.
On behalf of Microsoft's Nokia-X Linux kernel devs, have fun modding this!
Click to expand...
Click to collapse
Hmmm… It sounds interesting. can we now merge this to Lolipop source tree and make our custom rom?
i am with you
i am a Android developer
we can make our custom rom for nokia X2
ghorbelmahmoud said:
i am a Android developer
we can make our custom rom for nokia X2
Click to expand...
Click to collapse
Can you simply Port roms from Moto E its the same hardware i think
Sounds intersting
I am now working in a rom for nokia x2
I'll open a post in the forum Development
any one who wants to help me , contact me
ghorbelmahmoud said:
I am now working in a rom for nokia x2
I'll open a post in the forum Development
any one who wants to help me , contact me
Click to expand...
Click to collapse
Nice, which base are you working on? I may be able to help you a bit if my assignments let me
danialbehzadi said:
Nice, which base are you working on? I may be able to help you a bit if my assignments let me
Click to expand...
Click to collapse
base is ROM 2.0.0.11 Nokia X2
ghorbelmahmoud said:
I am now working in a rom for nokia x2
I'll open a post in the forum Development
any one who wants to help me , contact me
Click to expand...
Click to collapse
What kind of help do you need? I guess most of us should be able to "test" the ROM if you cook one. Some good set of instructions would be nice like which Recovery is required, what you expect not to work in initial release etc.
ghorbelmahmoud said:
I am now working in a rom for nokia x2
I'll open a post in the forum Development
any one who wants to help me , contact me
Click to expand...
Click to collapse
Thnx bro. We can test it...
Can u use latest rom cuz its very stable and fast:thumbup:
Sent from my NokiaX2DS using XDA Free mobile app
ghorbelmahmoud said:
base is ROM 2.0.0.11 Nokia X2
Click to expand...
Click to collapse
Ain't it better to base it on Latest Lolipop AOSP from google or the latest CM11?
ghorbelmahmoud said:
I am now working in a rom for nokia x2
I'll open a post in the forum Development
any one who wants to help me , contact me
Click to expand...
Click to collapse
interesting waiting for you man
ghorbelmahmoud said:
base is ROM 2.0.0.11 Nokia X2
Click to expand...
Click to collapse
legend man ... waiting
Hi out there!
Today i've looked another time for kernel sources of our loved (and hated) phone.
The only full source i've found was this one on the Sony Website:
http://developer.sonymobile.com/downloads/xperia-open-source-archives/open-source-archive-for-33-2-a-2-37-and-33-2-b-2-37/
I don't have the time nor the knowledge of kerneldevelopment to check this out.
My question is:
Is it possible to port this Sony kernel, to have a working p9000 kernel, with the goal to have let's say DirtyUnicorn running?
greetings
vsrookie
vsrookie said:
Hi out there!
Today i've looked another time for kernel sources of our loved (and hated) phone.
The only full source i've found was this one on the Sony Website:
http://developer.sonymobile.com/downloads/xperia-open-source-archives/open-source-archive-for-33-2-a-2-37-and-33-2-b-2-37/
I don't have the time nor the knowledge of kerneldevelopment to check this out.
My question is:
Is it possible to port this Sony kernel, to have a working p9000 kernel, with the goal to have let's say DirtyUnicorn running?
greetings
vsrookie
Click to expand...
Click to collapse
Kernel and ROM are 2 different things. We could get DU working on stock kernel, but we need valid device and vendor trees. Sometimes you can make them yourself, other times the manufacturers provide them.
Jonny said:
Kernel and ROM are 2 different things. We could get DU working on stock kernel, but we need valid device and vendor trees. Sometimes you can make them yourself, other times the manufacturers provide them.
Click to expand...
Click to collapse
Ok. But an android system need functions from the kernel, don't they?
What do you exactly mean with device tree and vendor tree? The drivers for the components? If it is so, then can't we "just take them" and integrate in the kernel source?
greetings
vsrookie
Ps: Basically i need to read sonething about Android development. [emoji12]
Sent from my P9000 using XDA-Developers mobile app
vsrookie said:
Ok. But an android system need functions from the kernel, don't they?
What do you exactly mean with device tree and vendor tree? The drivers for the components? If it is so, then can't we "just take them" and integrate in the kernel source?
greetings
vsrookie
Ps: Basically i need to read sonething about Android development. [emoji12]
Sent from my P9000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Vendor tree example >>> https://github.com/omnirom/android_vendor_omni
Device tree example >>> https://github.com/omnirom/android_device_sony_kitakami-common
The Android system does use functions from the kernel but its not really "aware" of doing so, you can run custom ROM's like DU, Omni etc from stock kernels most of the time without any issues.
So basically: When/If Elephone decides to release CM13, it's still possible they won't give us the vendor/device tree? So that's basically a byebye to porting roms?
Sorry, I'm a nub too.
Boristruyens said:
So basically: When/If Elephone decides to release CM13, it's still possible they won't give us the vendor/device tree? So that's basically a byebye to porting roms?
Sorry, I'm a nub too.
Click to expand...
Click to collapse
Tbh that is a massive probability, making device and vendor trees is not non-trivial and is a lot of work. For instance the HTC 10 still doesn't have a stable CM build, and there are some hard hitters in the AOSP dev world that own that device. I'll have a look and see what I can do but I'm an app developer and an apk editor (i.e. Java and Smali are more my languages than C/C++) more than a source builder so I might not be able to do much.
Can i use it for making recovery for moto m
The P9000 has a kernel on github anyway ...
Hi there,
Having seen that this device is gaining popularity in the Southeast Asian region, I have taken the time to start an unofficial development of CM for this device. Right now, having gotten the kernel to build but without the device I won't be able to extract the required blobs and such to start a device tree. So I'm asking here if you guys wanted to help and extract the blobs using the method here: https://wiki.cyanogenmod.org/w/Doc:_porting_intro
Build a device tree based on @hondajohn88 repo and right now doing changes to it to support CM.
https://github.com/webhaikal/android_device_leeco_zl1
You can use this for Method 1 in the porting intro: https://www.androidfilehost.com/?fid=529152257862684212. You either need a Linux distro or Ubuntu Bash on Windows..
Here's the kernel I build: https://www.androidfilehost.com/?fid=529152257862684239
As I don't have the financials to actually buy the device, that's why I'm asking here...
Thank you..
I really don't know anything about building ROMs, but reading method 1 all you need is boot.img?
Hi, me, @hondajohn88 and someone else are working on a source build. Please dig in github for device tree and so on.
Let's keep in touch!
edit: checked updater script and it is referred to Xiaomi device (ferrari). Is that ok?
haikalizz said:
Hi there,
Having seen that this device is gaining popularity in the Southeast Asian region, I have taken the time to start an unofficial development of CM for this device. Right now, having gotten the kernel to build but without the device I won't be able to extract the required blobs and such to start a device tree. So I'm asking here if you guys wanted to help and extract the blobs using the method here: https://wiki.cyanogenmod.org/w/Doc:_porting_intro
You can use this for Method 1 in the porting intro: https://www.androidfilehost.com/?fid=529152257862684212. You either need a Linux distro or Ubuntu Bash on Windows..
Here's the kernel I build: https://www.androidfilehost.com/?fid=529152257862684239
As I don't have the financials to actually buy the device, that's why I'm asking here...
Thank you..
Click to expand...
Click to collapse
Check out my vendor repo on git hub. It has most of the blobs but I haven't added the rest. I might be able to do that later today.
https://github.com/hondajohn88
hondajohn88 said:
Check out my vendor repo on git hub. It has most of the blobs but I haven't added the rest. I might be able to do that later today.
https://github.com/hondajohn88
Click to expand...
Click to collapse
Question, your device tree is based on Kenzo? Or is the specsheet not updated?
haikalizz said:
Question, your device tree is based on Kenzo? Or is the specsheet not updated?
Click to expand...
Click to collapse
Sorry about that, yes, the spec sheet not updated.
Later this evening I'll try to get everything I have updated to git, but what's there now is a decent start (my first commit, so there are a few changes)
hondajohn88 said:
Sorry about that, yes, the spec sheet not updated.
Later this evening I'll try to get everything I have updated to git, but what's there now is a decent start (my first commit, so there are a few changes)
Click to expand...
Click to collapse
One thing when building the kernel, there are a few includes that needs to be fixed. The commit that fixes it can be found on marlin (Google Pixel) kernel on Cyanogenmod github...
http://opensource.le.com
haikalizz said:
One thing when building the kernel, there are a few includes that needs to be fixed. The commit that fixes it can be found on marlin (Google Pixel) kernel on Cyanogenmod github...
Click to expand...
Click to collapse
Ah, thanks...I've been having issues with that Damn thing. I'll look into it, thank you
Flounderist said:
Hi, me, @hondajohn88 and someone else are working on a source build. Please dig in github for device tree and so on.
Let's keep in touch!
edit: checked updater script and it is referred to Xiaomi device (ferrari). Is that ok?
Click to expand...
Click to collapse
Yikes, updater script in my repo? Sigh, so much to look into...
Time for beer.
I think using a device that has a SD821 would be a better starting point than kenzo.
Flounderist said:
Hi, me, @hondajohn88 and someone else are working on a source build. Please dig in github for device tree and so on.
Let's keep in touch!
edit: checked updater script and it is referred to Xiaomi device (ferrari). Is that ok?
Click to expand...
Click to collapse
Oops forgot about the updater script.. Whats the device codename? ZL1?
haikalizz said:
Whats the device codename? ZL1?
Click to expand...
Click to collapse
I'm not sure about the codename. I think it's "le_zl1" at least this is what "ro.build.product" contains. Here some relevant properties from my LEX720 (the chinese version which has dual-sim):
Code:
[ro.build.product]: [le_zl1]
[ro.config.product]: [le_zl1]
[ro.product.device]: [le_zl1]
[ro.product.model]: [LEX720]
[ro.product.name]: [ZL1_CN]
[ro.bootimage.build.fingerprint]: [LeEco/ZL1_CN/le_zl1:6.0.1/WAXCNFN5801811012S/letv11011204:user/release-keys]
[ro.build.description]: [le_zl1-user 6.0.1 WAXCNFN5801811012S eng.letv.20161101.120034 release-keys]
[ro.build.fingerprint]: [LeEco/ZL1_CN/le_zl1:6.0.1/WAXCNFN5801811012S/letv11011204:user/release-keys]
[ro.build.display.id]: [WAXCNFN5801811012S release-keys]
androcheck said:
I'm not sure about the codename. I think it's "le_zl1" at least this is what "ro.build.product" contains. Here some relevant properties from my LEX720 (the chinese version which has dual-sim):
Code:
[ro.build.product]: [le_zl1]
[ro.config.product]: [le_zl1]
[ro.product.device]: [le_zl1]
[ro.product.model]: [LEX720]
[ro.product.name]: [ZL1_CN]
[ro.bootimage.build.fingerprint]: [LeEco/ZL1_CN/le_zl1:6.0.1/WAXCNFN5801811012S/letv11011204:user/release-keys]
[ro.build.description]: [le_zl1-user 6.0.1 WAXCNFN5801811012S eng.letv.20161101.120034 release-keys]
[ro.build.fingerprint]: [LeEco/ZL1_CN/le_zl1:6.0.1/WAXCNFN5801811012S/letv11011204:user/release-keys]
[ro.build.display.id]: [WAXCNFN5801811012S release-keys]
Click to expand...
Click to collapse
Could you extract a boot.img too? Alot of info could be extracted from it too...
goroflack said:
I think using a device that has a SD821 would be a better starting point than kenzo.
Click to expand...
Click to collapse
I agree, and I have since changed to using some of oneplus3. I hadn't changed the device spec on my repo, but merged the change given to me by @haikalizz.
Mostly I was using the Kenzo files as a template, but changed it up a short while after.
Thanks
haikalizz said:
Could you extract a boot.img too?
Click to expand...
Click to collapse
Yes, of course. This is the original unmodified boot.img of the chinese LEX720 model running the latest EUI version for the chinese model (5.8.018S). Note that for the US version there is already a newer release (5.8.019S).
I uploaded it here to my server: WAXCNFN5801811012S_boot.img
the lastest cho x720 is eui 5.9 20s which available from
http://bbs.ydss.cn/thread-714235-1-1.html
moneyrain said:
the lastest cho x720 is eui 4.9 20s which available from
http://bbs.ydss.cn/thread-714235-1-1.html
Click to expand...
Click to collapse
This is a custom release. Is there also somewhere an unmodified official download to look into? The OTA server still responds with version 018S for my device:
Click here for OTA Check
You have to replace the XXXXXX.. with your actual IMEI (and maybe also model and product) to get a response from this server.
im downloading the package. I will flash this build for test ( x720 is my 2nd phone )
moneyrain said:
im downloading the package. I will flash this build for test ( x720 is my 2nd phone )
Click to expand...
Click to collapse
Please, can you upload this ROM with download link?
Sent from my LEX720 using Tapatalk
Hey guys!
NEWS 1: Guys, with help of another developer we are working on the device tree. The builds currently are booting up and there are bugs to be fixed. We have currently released LineageOS 15.0 first test build only to the insiders (.i.e. testers of K10 - K420DS/N).
NEWS 2: We will also be working on K10 MS428. We will be compiling LOS 14.1 for the phone.
Source: https://github.com/LG-K10/android_device_lge_m216
does k430dsY also counts in this project, sir?
EDIT: im a pure noob both in android and english grammar
black_is_colour said:
does k430dsY also counts in this project, sir?
EDIT: im a pure noob both in android and english grammar
Click to expand...
Click to collapse
Yes.
I'd also love to see the LG K10 K410 Dual or Single SIM variant ROM. Is that possible?
abittercoffee73 said:
I'd also love to see the LG K10 K410 Dual or Single SIM variant ROM. Is that possible?
Click to expand...
Click to collapse
yes.
pvineeth97 said:
yes.
Click to expand...
Click to collapse
Good to hear that. But is the 1 or 1,5 GB of RAM enough to maintain a smooth run of the Android 7? And, well, when we can expect the earliest results? Sorry for that, but I'm really interested in this project.
Woohoo!
GuyInDogSuit said:
Woohoo!
Click to expand...
Click to collapse
I already updated my guide.
https://forum.xda-developers.com/lg-k10/development/unofficial-metropcs-428-t3578814
GuyInDogSuit said:
I think so. He ported TWRP to the MS428, so it's possible.
@pvineeth97, any word on this?
Click to expand...
Click to collapse
I will start compiling 7.1 soon
I am busy with my course projects and exams. I will start compiling it in May.
Once AOSP is available I'll gladly build and maintain LineageOS. I don't have the time to work from scratch, porting is a ton of work I'm not ready to commit to! Good luck with this, looking forward to it.
Can you post link from device tree if it's online? (Not for TWRP but for AOSP/LineageOS)
Professor Woland said:
Can you post link from device tree if it's online? (Not for TWRP but for AOSP/LineageOS)
Click to expand...
Click to collapse
I am not ready with those yet. I am working on the device tree. Once I finish compiling LineageOS I will upload the device tree.
LineageOS/AOSP for k430 too?
Please keep on topic within this thread! Thanks all
Forum moderator,
Matt
a_lewicki said:
LineageOS/AOSP for k430 too?
Click to expand...
Click to collapse
Yeah. Later for K430/MTK.
Take my kiss, thnx; Waiting for your work.
+ I have a k430dsy device.
I'm working on the k428/ms428 variants and pvineeth97 is working on the 420 variants. Others may come down the road.
I'm building the device tree now based on a few unofficial builds for devices with the msm8909 SoC, so with some luck it may not take too much work to get it going for us. All depends on how much time I can dedicate to it.
JoeMoDo said:
I'm working on the k428/ms428 variants and pvineeth97 is working on the 420 variants. Others may come down the road.
I'm building the device tree now based on the BQ Aquarius X5 tree I forked from the LineageOS github. It has the same SoC as the K428, so with some luck it may not take too much work to get it going for us. All depends on how much time I can dedicate to it.
Click to expand...
Click to collapse
Right on! Good job and good luck!
Once I'm done, and have it compiled and bootable, I'll need a couple beta testers to help me iron out kinks before releasing publicly (unless of course it just works flawlessly ). This is only open to k428/ms428 owners who can competently recover from brick on their own, and are willing to produce adequate logcats regarding any issues. Hoping to have a bootable rom in the coming weeks, we'll go from there. Keep in mind bootable may mean far from stable. Many things may be broken at first. If you're not willing to dedicate the time and work to help me fix such issues (ie, camera not working, audio not working, data not working, everything not working), please don't volunteer. If you aren't competent with adb, don't know how to produce a logcat, and don't know what to do with a bricked device, please don't volunteer. I won't have the time nor patience to walk anyone through fixing their device, and work on the port. If you feel competent, you can message me with your interest.