Hi guy's!
I am BlackFoxy, and i start make sources for ASUS Zenfone 2 Laser
But i need help
If you can, please help me
I in Facebook - https://www.facebook.com/misha.scvorzov
Device sources and more you can see on my GitHub Profile - https://github.com/BlackFoxy757
M here !
Love to help @Shanmugam k @Sujeet Ranipa
What exactly do you need help with?
hardslog said:
What exactly do you need help with?
Click to expand...
Click to collapse
Help with make kernel and correct device and vendor tree
BlackFoxy757 said:
Help with make kernel and correct device and vendor tree
Click to expand...
Click to collapse
Ok I'll give you a little information
1) There is a very highly likely chance that the laser-auto-focus will not work. Of course we don't know until we try but I am not confident because getting things like that which are not in common android source code is very difficult to get working.
2) There are many versions of the ZF2 laser, some come with different kernels therefore will need sources for each kernel (potentially). They also might share the same source (won't know unless I take a good look at it)
3) I am downloading the Kernel source for the ZE551KL and will upload it to github for a starting point. You can easily fork it from there into your github repo. It should be up in a day or less. By the looks of your github repo, you have a different model (one with a 410 snapdragon). Kernel sources are available from the asus.com website under support. You can download it from there for now and I can show you how to upload it to github.
4) If you plan on supporting all the ZF2 laser models, I would suggest for the device repos to make a "common" repo as they will share a lot of the same code, then have separate repos for each model for all the unique characteristics of them.
Edit: kernel uploading to my github. Internet is slow but you can see it soon by going to https://github.com/Hardslog/android_kernel_asus_zf2l
hardslog said:
Ok I'll give you a little information
1) There is a very highly likely chance that the laser-auto-focus will not work. Of course we don't know until we try but I am not confident because getting things like that which are not in common android source code is very difficult to get working.
2) There are many versions of the ZF2 laser, some come with different kernels therefore will need sources for each kernel (potentially). They also might share the same source (won't know unless I take a good look at it)
3) I am downloading the Kernel source for the ZE551KL and will upload it to github for a starting point. You can easily fork it from there into your github repo. It should be up in a day or less. By the looks of your github repo, you have a different model (one with a 410 snapdragon). Kernel sources are available from the asus.com website under support. You can download it from there for now and I can show you how to upload it to github.
4) If you plan on supporting all the ZF2 laser models, I would suggest for the device repos to make a "common" repo as they will share a lot of the same code, then have separate repos for each model for all the unique characteristics of them.
Edit: kernel uploading to my github. Internet is slow but you can see it soon by going to https://github.com/Hardslog/android_kernel_asus_zf2l
Click to expand...
Click to collapse
Yes. I think supported all Z2L
Thank you... we are waiting for you
How is it going?
do you can please creat a custom rom for ze500kl
BlackFoxy757 said:
Yes. I think supported all Z2L
Click to expand...
Click to collapse
There is already a custom ROM for Z00T and Z00L, and I think you should make one for a device that don't have it. Like Z00ED. Also I think you need to have the device so you can test it. No one likes broken ROMs
But.... Why u need make source for zen 2 laser?
Cyanogen have source for this.... And some device already custom.... Only ze500kl don't have.... But i think can use source of msm8916-common !
Related
Okay Guys,
I am working hard to bring up Cyanogenmod to our beloved moto g.
But i am a bit Noobish in this field.
I have been reading guides and following the process.
So far I have setup the build environment and synced the latest repo from CM sources.
Now, further most imp step is Vendor, Kernal and Device tree.
I have found this so far, by searching this forum only,
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/kitkat-4.4.4-release-titan
Now, reading further some guides, they say kernel and device tree will require some modification to work with CM12, but i couldnt find about this modification.
so I request all developers to guide me on this.
We can surely do this together. :fingers-crossed:
N.K.V. said:
Okay Guys,
I am working hard to bring up Cyanogenmod to our beloved moto g.
But i am a bit Noobish in this field.
I have been reading guides and following the process.
So far I have setup the build environment and synced the latest repo from CM sources.
Now, further most imp step is Vendor, Kernal and Device tree.
I have found this so far, by searching this forum only,
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/kitkat-4.4.4-release-titan
Now, reading further some guides, they say kernel and device tree will require some modification to work with CM12, but i couldnt find about this modification.
so I request all developers to guide me on this.
We can surely do this together. :fingers-crossed:
Click to expand...
Click to collapse
I love your initiative! Unfortunately I'm not a developer...
Send from my XT1068 using Tapatalk.
nice work mate.... developers are needed urgently....
Why do you think developers will find you and this thread? It works the other way. You need to find developers and ask for help. I suggest you start here and here
I keep my fingers crossed for the success of the project :highfive:
Yes, I am reading all possible guides given by the developers.
By that only i have reach this far.
But for device tree and kernel, device specific modifications are necessary, and I really need help of some one who has actually done this before.
If this is successful , we can have an alpha build of CM 12 , in 3-4 days.
@ N.K.V.
ok i will help you with this..
first we need to set up device tree and vendor trees....
there is 2 ways to do this
first:- get a official motorola stock lollipop update for your phone.
(unfortunately it not yet released for all variants)
examine the similar device trees like falcon or htc a5 (desire 816) of lg l90 or sony m2 or sony e3
compare the kernel sources of falcon and titan (these are kitkat sources so may be in future motorola will release updated lollipop kernel source)
there are various major differences.
set up a basic device tree from falcon with msm8226 common of cm repos.
take vendor blob list from falcon
adapt it for titan
extract vendor blob from phone.
compile the rom
second:- from existing 4.4.4 rom
repo sync kernel from github
make changes to falcon and msm8226 device tree to adapt titan
extract vendor blobs with falcon list
compile
problem with second approach is that you have to make many changes to kernel and other things
but if we get official moto update of lollipop with kernel source then it will be little easier...
still if you are going to compile and want to make a cm12 from 4.4.4 i am with you ...i will set up device trees and other trees to set up things in motion.....
and then we can change vendor blobs and kernel to lollipop when it get released...
k2wl said:
@ N.K.V.
ok i will help you with this..
first we need to set up device tree and vendor trees....
there is 2 ways to do this
first:- get a official motorola stock lollipop update for your phone.
(unfortunately it not yet released for all variants)
examine the similar device trees like falcon or htc a5 (desire 816) of lg l90 or sony m2 or sony e3
compare the kernel sources of falcon and titan (these are kitkat sources so may be in future motorola will release updated lollipop kernel source)
there are various major differences.
set up a basic device tree from falcon with msm8226 common of cm repos.
take vendor blob list from falcon
adapt it for titan
extract vendor blob from phone.
compile the rom
second:- from existing 4.4.4 rom
repo sync kernel from github
make changes to falcon and msm8226 device tree to adapt titan
extract vendor blobs with falcon list
compile
problem with second approach is that you have to make many changes to kernel and other things
but if we get official moto update of lollipop with kernel source then it will be little easier...
still if you are going to compile and want to make a cm12 from 4.4.4 i am with you ...i will set up device trees and other trees to set up things in motion.....
and then we can change vendor blobs and kernel to lollipop when it get released...
Click to expand...
Click to collapse
This is great news. A team effort can do anything.:good:
Thanks to NKV and Kewl. Great initiative. God Bless You.
Sent from my Nexus 7 using XDA Free mobile app
okay guys,
let's keep this thread clean for developers.
you can always hit like to appreciate
UPDATE: @k2wl is working on kernel and device tree, it will take him some days.
@k2wl and N.K.V.
Thx for your time and work :good:
I wait for the right Software on xt1068!
I have a little bit of knowledge and i can learn really fast, if you guys need help, you can count on me
which model will this be for? (please say xt1064)
Bobboman said:
which model will this be for? (please say xt1064)
Click to expand...
Click to collapse
Doesn't matter. It will be for all variants!
absolutely brilliant, i wish i knew a lick of programming so that i could help get this done faster (i'm tired of seeing a SU update in play store and not being able to use it because it sends my G into a bootloop)
Thanks man, lollipop official update have a bug while playing music via bluetooth when screen is lock, can you fix it on this rom?
Ha ha...Let's make the ROM first..
Bug fixing in Second task.
Now that lollipop soak has started in India....i think Work should go fast. :beer:
Waiting for it. Please keep updated though!
I'm interested in helping with this.
Sent from my A0001 using XDA Free mobile app
Hope to See this soon! Thanks guys!!
Nice intitiative...but i think making device tree and vendor for this device will not be tht easy....still hope for best
I'm here to question the device owner. There are few sources around about this device. They are raw and they are as common always experimental. Does anyone need them?
Furthermore, I can sum up here any sources I or other get to find about this device or its periphery.
If you are eager to Void your Warranty please Mind and Acknowledge that every modification only affects you and your contract and noone else.
custom rom
http://forum.xda-developers.com/xperia-xa/development/f3112-f3116-cyanogemod-13-project-t3488890
Silversniper said:
I'm here to question the device owner. There are few sources around about this device. They are raw and they are as common always experimental. Does anyone need them?
Furthermore, I can sum up here any sources I or other get to find about this device or its periphery.
Click to expand...
Click to collapse
Very good thing, I'm trying to build a CM13 rom from sources and I'm not sure if I have all required sources. For now I have, kernel sources with some "vendor" files from Sony and I found all build parameters like offsets/adresses and correct cmdline (no thanks to Sony because never released or mentioned them), the device tree dumped from my device, and I will dump the vendor tree too.
Now I need the defconfig for CM (very not sure if the stock one will work) , and some files like the boardconfig and some config files. I'm using the Elephone P9000 sources for sample, almost the same device (hardware side) and source files.
If I have some time I will try to upload files to git but I never tried before (sync only)...
rrvuhpg said:
Very good thing, I'm trying to build a CM13 rom from sources and I'm not sure if I have all required sources. For now I have, kernel sources with some "vendor" files from Sony and I found all build parameters like offsets/adresses and correct cmdline (no thanks to Sony because never released or mentioned them), the device tree dumped from my device, and I will dump the vendor tree too.
Now I need the defconfig for CM (very not sure if the stock one will work) , and some files like the boardconfig and some config files. I'm using the Elephone P9000 sources for sample, almost the same device (hardware side) and source files.
If I have some time I will try to upload files to git but I never tried before (sync only)...
Click to expand...
Click to collapse
Don't need to hesitate. I'll try to put the directions I've gathered here up today so it is done.
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
rrvuhpg said:
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
Click to expand...
Click to collapse
cool.. if work I would like to have it on my f3111 !!
rrvuhpg said:
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
Click to expand...
Click to collapse
Can you publish some brief preview?
Need to say the sources I had just seem to be down, so can't share them.
Through which Program are these to flash? If you're that far I can hold a look at it and may join in your development.
Verification of the Vendor Files is something I was not very good at it, not even a yolk I managed.
Silversniper said:
Can you publish some brief preview?
Need to say the sources I had just seem to be down, so can't share them.
Through which Program are these to flash? If you're that far I can hold a look at it and may join in your development.
Verification of the Vendor Files is something I was not very good at it, not even a yolk I managed.
Click to expand...
Click to collapse
For now the only preview I can publish are the CM13 boot and recovery "as is", I'm not sure if it can help but I will release them if someone want to port others MTK Roms on XA. ( Never booted any ported rom with the stock kernel, stuck at Sony logo)
Flashing is easy: the recovery with fastboot and Rom/boot in a single flashable zip on the SD.
The kernel sources are coming from 33.2.B.2.95 open source archive from Sony but built from the lastest CM13 and Google git sources.
The vendor tree from 33.2.B.2.93 dumped from my phone, only common files with the P9000 are on my git for now.
The device tree from P9000 sources (from @Deepflex git) but seem OK.
CM13 have Android 6.0.1, I don't know if the security patch is the last one but August for sure.
I'm not so far from a finished build (not mean fully bootable), for now I successfully build a full CM13 for the Elephone P9000 (the twin of the XA, I'm using it as base). It mean my "kitchen" is working Now I'm trying to identify the last proprietary files from all others stock/cm13 libs, modify make files and cross my fingers it will fully build without errors.
You can join me no problem all people are welcome because I can't do all alone
rrvuhpg said:
For now the only preview I can publish are the CM13 boot and recovery "as is", I'm not sure if it can help but I will release them if someone want to port others MTK Roms on XA. ( Never booted any ported rom with the stock kernel, stuck at Sony logo)
Flashing is easy: the recovery with fastboot and Rom/boot in a single flashable zip on the SD.
The kernel sources are coming from 33.2.B.2.95 open source archive from Sony but built from the lastest CM13 and Google git sources.
The vendor tree from 33.2.B.2.93 dumped from my phone, only common files with the P9000 are on my git for now.
The device tree from P9000 sources (from @Deepflex git) but seem OK.
CM13 have Android 6.0.1, I don't know if the security patch is the last one but August for sure.
I'm not so far from a finished build (not mean fully bootable), for now I successfully build a full CM13 for the Elephone P9000 (the twin of the XA, I'm using it as base). It mean my "kitchen" is working Now I'm trying to identify the last proprietary files from all others stock/cm13 libs, modify make files and cross my fingers it will fully build without errors.
You can join me no problem all people are welcome because I can't do all alone
Click to expand...
Click to collapse
good work , but I am noob to create rom with kitchen .. only zip edit I know
Yesterday I successfully built CM13 for XA from sources
But news are not good, the CM recovery is fully working as expected but the rom is stuck just after the Sony logo (Mediatek screen with "loading...") like on my previous attempts to port other roms. The kernel built from CM kitchen do the same... I will upload my git and my rom to see if someone have an idea on the problem. Now I will focus on the "vendor" files, but I'm not sure if it's the real problem. Can it be a locked preloader/kernel or something like that?
EDIT: I think the boot problem is related to the defconfig file from Sony kernel sources, I will try to change some settings. (the door for adding kernel features :good
rrvuhpg said:
Yesterday I successfully built CM13 for XA from sources
But news are not good, the CM recovery is fully working as expected but the rom is stuck just after the Sony logo (Mediatek screen with "loading...") like on my previous attempts to port other roms. The kernel built from CM kitchen do the same... I will upload my git and my rom to see if someone have an idea on the problem. Now I will focus on the "vendor" files, but I'm not sure if it's the real problem. Can it be a locked preloader/kernel or something like that?
EDIT: I think the boot problem is related to the defconfig file from Sony kernel sources, I will try to change some settings. (the door for adding kernel features :good
Click to expand...
Click to collapse
Love you!
I will buy this phone thanks to you :highfive:
Thank you for your work on our phone, it's very cool.
I would have helped if i could develop myself. If you need help get in touch with me i know some great devs who could maybe help you
any news @rrvuhpg ?
Yes I have some news but I want to create a dedicated thread for the CM13 project with updates, explanations and downloads to avoid off topic here. I am on holiday on next week and I will have time to work on it and give explanations. For now I'm stuck on boot because of Sony extra settings in the boot process, it's the first time I see a bootstrap and TA partition mount on a MTK device. If you know a dev for helping me passing the Sony part in the boot init it can be great :angel:
Other thing, I updated my git with parts of the update made by @Deepflex on the P9000 sources and my recent changes.
rrvuhpg said:
Yes I have some news but I want to create a dedicated thread for the CM13 project with updates, explanations and downloads to avoid off topic here. I am on holiday on next week and I will have time to work on it and give explanations. For now I'm stuck on boot because of Sony extra settings in the boot process, it's the first time I see a bootstrap and TA partition mount on a MTK device. If you know a dev for helping me passing the Sony part in the boot init it can be great :angel:
Other thing, I updated my git with parts of the update made by @Deepflex on the P9000 sources and my recent changes.
Click to expand...
Click to collapse
sorry first time I use sony ... I wish you to have nice holiday !
Hello Folk,
i am Going to build custom roms for le 2 (x526) . But as of core requirement to build any custom rom , first i need 3 source codes which are
1)Kernel Sources (I have that)
2)Device tree sources (Hoping for someone to build this)
3)Vendor Tree sources (Again, we dont have that too)
So if you are serious about custom roms them support me and Ask for any experienced developer to Get these two Tree sources .
umangloria said:
Hello Folk,
i am Going to build custom roms for le 2 (x526) . But as of core requirement to build any custom rom , first i need 3 source codes which are
1)Kernel Sources (I have that)
2)Device tree sources (Hoping for someone to build this)
3)Vendor Tree sources (Again, we dont have that too)
So if you are serious about custom roms them support me and Ask for any experienced developer to Get these two Tree sources .
Click to expand...
Click to collapse
the kernel source you have is it working ???????????/
coz last i heard they removed it officially from their open source site coz they were not correct
Akhil16 said:
the kernel source you have is it working ???????????/
coz last i heard they removed it officially from their open source site coz they were not correct
Click to expand...
Click to collapse
they have removed from their site for all le Mobiles so i hope these are working .
umangloria said:
Hello Folk,
i am Going to build custom roms for le 2 (x526) . But as of core requirement to build any custom rom , first i need 3 source codes which are
1)Kernel Sources (I have that)
2)Device tree sources (Hoping for someone to build this)
3)Vendor Tree sources (Again, we dont have that too)
So if you are serious about custom roms them support me and Ask for any experienced developer to Get these two Tree sources .
Click to expand...
Click to collapse
This mobile contains snapdragon 652, which is rare currently in devices. So i don't think anyone has bring up device tree for this device. I am looking to purchase this device and then do some stuff for it, let's see if i bought it.
This might be helpful https://youtu.be/Uw_caMHZRC4
I want to build a custom ROM (CosmicOS) for my device (ZenFone Selfie, Z00UD, supports all Z00T roms).
I've already found a proper device tree, but I'm unsure about kernel and vendor trees I'm about to use.
Kernel:
https://github.com/LineageOS/android_kernel_asus_msm8916
Vendor:
https://github.com/TheMuppets/proprietary_vendor_asus
Am I using proper kernel and vendor trees?
The reason why am I asking this question is because I couldn't find a kernel tree for my processor (MSM8939) in Lineage OS' github and Asus' vendor's proprietary has no Z00T subfile.
you need proper device trees...send me the link for device trees and is your phone has any current rom supported...if yes paste a link
govind1233 said:
you need proper device trees...send me the link for device trees and is your phone has any current rom supported...if yes paste a link
Click to expand...
Click to collapse
Device tree:
https://github.com/LineageOS/android_device_asus_Z00T
Supported ROMs:
https://forum.xda-developers.com/zenfone-2-laser/orig-development/rom-cyanogenmod-14-0-t3459745
https://forum.xda-developers.com/zenfone-2-laser/development/rom-resurrection-remix-n-t3509698
https://forum.xda-developers.com/zenfone-2-laser/development/rom-viper-os-v2-1-t3640026
There are even more of them, of course
As I said before, my phone (ZenFone Selfie, Z00UD) supports all ROMs that support Z00T variant of device (ZenFone 2 Laser)
Also, a source code of ROM I want to build:
https://github.com/Cosmic-OS
Take the same kernel as the devs use to build for Z00T and vendor of Asus from Muppets...it will be no problem if it won't vendor of Z00T...and also include the common trees of ur device...while building...and for vendor just create a file named vendorsetup.sh in ur device trees...
govind1233 said:
Take the same kernel as the devs use to build for Z00T and vendor of Asus from Muppets...it will be no problem if it won't vendor of Z00T...and also include the common trees of ur device...while building...and for vendor just create a file named vendorsetup.sh in ur device trees...
Click to expand...
Click to collapse
So you say that the kernel tree I've included in this thread is proper one, right? Or should I download the one from ASUS?
Yes...and try including common trees also
govind1233 said:
Yes...and try including common trees also
Click to expand...
Click to collapse
This?
https://github.com/LineageOS/android_device_asus_msm8916-common
darkeyes22 said:
This?
https://github.com/LineageOS/android_device_asus_msm8916-common
Click to expand...
Click to collapse
Yes
govind1233 said:
Yes
Click to expand...
Click to collapse
Thank you
Now this:
https://pastebin.com/Nc4yzCNi
Any suggestions?
Hello,
For those interested in the original kernel source code for the SM-T813 :
As I am learning how to make ports for Android, I am trying to train on the original sources of the Linux kernel for the SM-T813.
After several weeks of research, I couldn't find the origin of the different kernel repositories.
Also on https://opensource.samsung.com, it was impossible to find the sources. So I contact them at the end of January to have an access to this sources...
... And they are now available !
You can download them on https://opensource.samsung.com (search SM-T813 at mobile phone on release center) or on my repository at https://github.com/Akipe/android_kernel_samsung_gts210vewifi_original_samsung
It is based on the T813XXS2BTK3 firmware with Android 7 Nougat.
I will see to ask for sources of similar tablets.
Will this help with porting new Adnoid version to these tablets?
Pawel_ said:
Will this help with porting new Adnoid version to these tablets?
Click to expand...
Click to collapse
I don't think so,
Kernel sources for this tablet already exist, and are ported to newer versions.
It is more useful for those who want start from scratch, and want to inspect the unmodified source code.
But my goal would be to successfully create from scratch for the SM-T813 LineageOS 14.1 (Android 7); and then try to move to the latest versions.
Since I am a beginner, I still have a lot to learn, and I don't have much time, so we will see