Dear All,
I'm complete noob, i'm trying to learn how to build and maintain a rom.
I need your help, I need a device tree as of now, If i get all the required files, i promise to deliver on of the best roms for our device. Our Xperia Z3 is the verge of death, I don't want to let that happen. Please help devs
Device Tree: https://github.com/CarbonROM/android_device_sony_z3
Kernel: https://github.com/CarbonROM/android_kernel_sony_msm8974/tree/cr-6.1
MSM8974 Common: https://github.com/CarbonROM/android_device_sony_msm8974-common
Shinano Common: https://github.com/CarbonROM/android_device_sony_shinano-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
Hello,
So now we have the Z2 sources, Z2 Pro should come soon as-well, it would be great to start building ourselves a nice CM13 or RR. Sadly I am fully booked for the 2 next weeks and as it's my first CM build (despite I builded some ASOP already), it's going to take me a long time. So the goal of this thread is just to regroup and share the files so we can get ASAP to something stable.
Do we have the sources from the chinese CM13 Z2 Pro build ?
Thanks all !
I would love to contribute, but i'm a bit busy, too. It would be nice if someone could create a git for this project following the rules from cyanogenmod, to get this Phone an official release some time soon.
How To Port CyanogenMod Android To Your Own Device
https://wiki.cyanogenmod.org/w/Doc:_porting_intro
Hey, I am fully Intrested in bringing up CyanogenMod for it, but.. Kernel Sources arr bad or something? I am trying to compile with aarch-arm64-androideabi- (gcc4.9) its like failing to build in signal.c
Hi, I'm making this thread to centralize and make easier for devs to work on ZUK Z2(standard).
NOTE: Z2131 & Z2132 are the SAME device, just name and ZUI version different. So ROMs and Kernels are usable by both side, it's the same for ZUK Z2 Rio which is the lower storage z2(3/32)
There are many links and resources, but if you're a Dev who works on this device contact me in private, there is a group for all the devs, indeed Fedor917, Davidenavil, CallMeSuper, Flour_Mo, Frencesco Colella, Leo, scafroglia93 and Franko76 are working in that group.
Source Code by ZUK
LINK ALREADY WITH TRANSLATION
(The source of z2131(CN) & z2132(Indian) ZUIs can be found on the right list)
Dev's profiles for ZUK Z2 repositories:
https://github.com/Silentlys
https://github.com/cryscript
https://github.com/davidevinavil
https://coding.net/u/CallMESuper
https://github.com/mnemonyc
https://github.com/scafroglia93
https://github.com/zuk2plus
Kernel
https://github.com/Silentlys/android_kernel_zuk_msm8996 (original one)
https://github.com/scafroglia93/android_kernel_zuk_msm8996 (the most updated stock)
https://coding.net/u/CallMESuper/p/android_kernel_zuk_z2_plus/git (M-Kernel source)
https://github.com/cryscript/android_kernel_zuk_msm8996
Vendor
https://github.com/cryscript/android_vendor_zuk_z2_plus
https://github.com/davidevinavil/android_vendor_zuk_z2
https://github.com/zuk2plus/android_vendor_zuk_z2plus
Android Device
https://github.com/cryscript/android_device_zuk_z2_plus
https://github.com/davidevinavil/android_device_zuk_z2
https://github.com/Silentlys/android_device_zuk_z2
DualBootPatcher source
https://github.com/cryscript/DualBootPatcher
Hi KronozFX,
Thank you for the link!
I'm trying to compiling a kernel for CM14.1(Lineage OS now), which kernel should I use then?
Thank you!
riaqn said:
Hi KronozFX,
Thank you for the link!
I'm trying to compiling a kernel for CM14.1(Lineage OS now), which kernel should I use then?
Thank you!
Click to expand...
Click to collapse
U can find it on https://github.com/LineageOS
Just search for your chipset
Hi, I created this post for the purpose of collaborate in the creation of a Stock Nougat ROM for our Z3 and possibly for all Shinano devices. I worked some time ago un something related, but my poor experience in ROM made that break down. Recently I could see the work of machao44 who could port XZs firmware to Marshmallow Z3 and some advances of Sony framework on LineageOs 14.1 Z3.
I think we can use as base LineageOs from nailyk that porting Sony framework could have all these features:
* Fully featured camera
* Safetynet pass
* Use themes
* Change lockscreen clock
* Animated wallpapers
* PlayStation controller
* Use your favorites Sony apps and more
I am waiting for your input.
PS: I think a Github and Gerrit could be fine.
Can't wait for that! Keep it up!
But does this ROM required unlock bootloader? Because I am using SOL26(Japan carrier) motherboard for my Z3 and that version cannot unlock the bootloader.
If required unlock the bootloader, it's OK! Just hope that other user can taste it. :fingers-crossed:
Hi
lynxeon said:
Hi, I created this post for the purpose of collaborate in the creation of a Stock Nougat ROM for our Z3 and possibly for all Shinano devices. I worked some time ago un something related, but my poor experience in ROM made that break down. Recently I could see the work of machao44 who could port XZs firmware to Marshmallow Z3 and some advances of Sony framework on LineageOs 14.1 Z3.
I think we can use as base LineageOs from nailyk that porting Sony framework could have all these features:
* Fully featured camera
* Safetynet pass
* Use themes
* Change lockscreen clock
* Animated wallpapers
* PlayStation controller
* Use your favorites Sony apps and more
I am waiting for your input.
PS: I think a Github and Gerrit could be fine.
Click to expand...
Click to collapse
Could be based on AOSP Carbon ROM currently I think it does not present problems in the camera like fisheye and dark tone soon I will try to see that it works but in my personal opinion I think it would be much better based on AOSP.
@lynxeon
Please read this all lynxeon all post of my
I cant download japanes forum
https://forum.xda-developers.com/z3/development/rom-xperia-xzs-rom-z3-t3618918 read all
maple_mak said:
But does this ROM required unlock bootloader?
Click to expand...
Click to collapse
Yup, you need an unlocked bootloader.
For the locked bootloader your can only use: 5.1.1 (firmware .264), 6.0.1 (firmware .291), Nougat DevPreview 4 or Concept 6.0.1 ( .3657).
HEKER510 said:
@lynxeon
Please read this all lynxeon all post of my
I cant download japanes forum
https://forum.xda-developers.com/z3/development/rom-xperia-xzs-rom-z3-t3618918 read all
Click to expand...
Click to collapse
- Brightness is high
- Double Tap to wake no work
- Messaging bootloop
Oooo... yes .. i cant wait to test
hi
hi what we can do for that ?
I decided it might be time to post this kernel as it's starting to take shape. It started life as an Xperiadev unified kernel with some modifications like memutils, it was used by Omnirom that saw a release for the Z1 using kernel 3.10, but had not seen an update since 2016 or so, since that's not something I could live with I decided on Codeaurora-msm-3.10-LA.BR.1.3.7_rb1.9 as a valid subject for purging updates from.
Currently my android-7.1 branch is stuck on the boot logo on Z1 (now led changes color and it reboots, instead of stick on logo before) and finding the issue has taken longer than expected, somewhat due to my relaxed approach this time. The code for supporting all Xperia devices all looks good but I have only Z1 and Z5 to test, for now I've focused on the Z1.
I've forked Xperiadev LA.BR.1.3.3_rb2.14 and testing changes, most surprisingly what i considered a small and important update to the iommu code resulted in a locked kernel, it is certainly not the easily spotted mistake i've been looking for that's at fault with my branch and so this will be my testbed for the code i find functional .
Results thus far:
Xperiadev unified LA.BR.1.3.3_rb2.14 with changes from Codeaurora merge:
https://github.com/threader/kernel , set default to LA.BR.1.3.3_rb2.14
git clone https://github.com/threader/kernel.git
https://github.com/threader/kernel
A speculative merge too far, so far:
git clone https://github.com/threader/android_kernel_sony_msm.git -b android-7.1
https://github.com/threader/android_kernel_sony_msm/tree/android-7.1?files=1
Used for updated qcom device driver code :
git clone git://codeaurora.org/quic/la/kernel/msm-3.10 -b LA.BR.1.3.7_rb1.9 (I also used LA.BR.1.3.7-01310-8976.0 )
threader said:
I decided it might be time to post this kernel as it's starting to take shape. It started life as an omnirom kernel for all Xperia devices, this had not seen an update since 2016 or so, since that's not something I could live with I decided on Codeaurora-msm-3.10-LA.BR.1.3.7_rb1.9 as a valid subject. Currently I'm stuck on the boot logo on Z1 and finding the issue has taken longer than expected, somewhat due to my relaxed approach this time. The code for supporting all Xperia devices all looks good but I have only Z1 and Z5 to test, for now I've focused on the Z1.
I'm working on the android-7.1 branch.
Any ideas?
https://github.com/threader/android_kernel_sony_msm/tree/android-7.1?files=1
Click to expand...
Click to collapse
Don't bother. That is based on Sony's Open Devices Project, which was a good concept but did not provide any sort of usability whatsoever for msm8974 devices. Stick to 3.4.x and forget about unification.
drakonizer said:
Don't bother. That is based on Sony's Open Devices Project, which was a good concept but did not provide any sort of usability whatsoever for msm8974 devices. Stick to 3.4.x and forget about unification.
Click to expand...
Click to collapse
I'm noting difficulties and riddles of #ifndef msm8974 but the omirom 3.10 kernel is not running badly, the camera has issues i noted, and i feel 3.4 has the attention of others.
Regarding the unified project, i started looking at the latest branch for legacy, if i remember correctly the correct branch for legacy is LA.BR.1.3.3_rb2.14, i feel i can compare and move code around with some confidence compared to an older version.
https://github.com/sonyxperiadev/kernel/tree/aosp/LA.BR.1.3.3_rb2.14