Database Develop

[P905M LTE and P905][KERNEL] STOCK compiled with SELinux setenfoce command enabled

I am not responsible for any possible bad effects which may result from using included software! You flash it on your own risk!
Probably it will work in the P905 version, because I flashed the a P905 kernel in my P905M without problems. But, as usual, it is your risk.
User esgie confirmed that it works on SM-P905 too!
STOCK compiled with SELinux setenforce enabled
Kernel base: compiled from Samsung sources without modifications (opensource.samsung.com)
Kernel ramdisk: extracted from stock image
Features: setenforce command working
WARNING!
FLASHING THIS WILL TRIP KNOX AVOIDING YOUR WARRANTY!
Known issues
WiFi gets a little screwy. To fix it edit /system/build.prop, change the parameter ro.securestore.support from true to false and reboot.
Installation
flash using ODIN (AP/PDA)
Image sha1sum
b85360a80f6205269b75d9dfabccac211a224d46
CREDITS
- Graeme Hill`s Dev Blog (http://graemehill.ca/compiling-permissive-android-kernel)
- osm0sis user Android Image Kitchen tool (http://forum.xda-developers.com/showthread.php?t=2073775)
- Samsung (opensource.samsung.com)
- esgie Kernel STOCK RELOADED (http://forum.xda-developers.com/showthread.php?t=2771469)

No one interested?
Thanks a lot. Will try it.
Sent from my GT-N7100 using XDA Premium 4 mobile app

rodpp said:
I am not responsible for any possible bad effects which may result from using included software! You flash it on your own risk!
Probably it will work in the P905 version, because I flashed the a P905 kernel in my P905M without problems. But, as usual, it is your risk.
STOCK compiled with SELinux setenforce enabled
Kernel base: compiled from Samsung sources without modifications (opensource.samsung.com)
Kernel ramdisk: extracted from stock image
Features: setenforce command working
WARNING!
FLASHING THIS WILL TRIP KNOX AVOIDING YOUR WARRANTY!
Known issues
WiFi gets a little screwy. To fix it edit /system/build.prop, change the parameter ro.securestore.support from true to false and reboot.
Installation
flash using ODIN (AP/PDA)
CREDITS
- Graeme Hill`s Dev Blog (http://graemehill.ca/compiling-permissive-android-kernel)
- osm0sis user Android Image Kitchen tool (http://forum.xda-developers.com/showthread.php?t=2073775)
- Samsung (opensource.samsung.com)
- esgie Kernel STOCK RELOADED (http://forum.xda-developers.com/showthread.php?t=2771469)
Click to expand...
Click to collapse
Hangs on boot before the Samsung logo.
Sent from my SM-P905M using XDA Premium HD app

gorcutt said:
Hangs on boot before the Samsung logo.
Sent from my SM-P905M using XDA Premium HD app
Click to expand...
Click to collapse
Hi,
I just downloaded the file from this post and checked the sha1sum against the original file that I uploaded and it´s ok. The sha1sum value is b85360a80f6205269b75d9dfabccac211a224d46. So there is no file corruption problem.
Please check if your file has the same sha1sum.
Tonight I´ll flash this file again in my tablet and verify if it works. It´s highly improbable that I uploaded the wrong file, but I´ll check flashing it.
As soon as possible I´ll update here the result of this test.
Regards,
Rodrigo.

Awesome!
Flashed, seems to boot ok on SM-P905
Great job.
Seems to be working fine! Boots as permissive and setenforce 0/1 working fine.
Great job. Now we are waiting for at least some basic overclocking and governors implementation

esgie said:
Awesome!
Flashed, seems to boot ok on SM-P905
Great job.
Seems to be working fine! Boots as permissive and setenforce 0/1 working fine.
Great job. Now we are waiting for at least some basic overclocking and governors implementation
Click to expand...
Click to collapse
Thank you very much for confirm that it works on SM-P905, I'll include this information on the first post.
If you find some WiFi issues don't forget to edit /system/build.prop, change the parameter ro.securestore.support from true to false and reboot.
Regards,
Rodrigo.

Already had the property changed in my build.prop, so i'm not exactly sure if the wifi works out of the box or not. Although I confirm that it DOES work with the build.prop modification
And by "does work" I meant both wifi and mobile radio working flawlessly.

gorcutt said:
Hangs on boot before the Samsung logo.
Sent from my SM-P905M using XDA Premium HD app
Click to expand...
Click to collapse
rodpp said:
Hi,
I just downloaded the file from this post and checked the sha1sum against the original file that I uploaded and it´s ok. The sha1sum value is b85360a80f6205269b75d9dfabccac211a224d46. So there is no file corruption problem.
Please check if your file has the same sha1sum.
Tonight I´ll flash this file again in my tablet and verify if it works. It´s highly improbable that I uploaded the wrong file, but I´ll check flashing it.
As soon as possible I´ll update here the result of this test.
Regards,
Rodrigo.
Click to expand...
Click to collapse
Hi there, I tested here and the image is working fine here. The user esgie just confirmed that too, in a P905. Please check the sha1sum of your downloaded image file.
Regards,
Rodrigo.

rodpp said:
Hi,
I just downloaded the file from this post and checked the sha1sum against the original file that I uploaded and it´s ok. The sha1sum value is b85360a80f6205269b75d9dfabccac211a224d46. So there is no file corruption problem.
Please check if your file has the same sha1sum.
Tonight I´ll flash this file again in my tablet and verify if it works. It´s highly improbable that I uploaded the wrong file, but I´ll check flashing it.
As soon as possible I´ll update here the result of this test.
Regards,
Rodrigo.
Click to expand...
Click to collapse
I probably did something wrong.
I've downloaded again and wiill try once more.
MD5 f39207bd4c45b1854372cd519942a6c2
SHA1 b85360a80f6205269b75d9dfabccac211a224d46
Thanks.
Sent from my GT-N7100 using XDA Premium 4 mobile app

As we all can see, our devices lacks of community support.
I wonder if you are the first person on the planet who managed to prepare an environment and compile P905(x) kernel succesfuly
May I ask you if have any plans to proceed with the kernel developement?

Please integrate fauxsound

esgie said:
As we all can see, our devices lacks of community support.
I wonder if you are the first person on the planet who managed to prepare an environment and compile P905(x) kernel succesfuly
May I ask you if have any plans to proceed with the kernel developement?
Click to expand...
Click to collapse
Unfortunately I don't have enough free time, so I don't have plans to work in kernel development. I did this because I was needing it to install some stuffs in my tablet and decided to share it here o XDA where I always found useful things.
If someone wants simple modifications and points some links explaining that I can try without problems.
And if someone have problems preparing an environment to compile the kernel, let me know, I'll be very happy to help.
Regards,
Rodrigo.

koko115 said:
Please integrate fauxsound
Click to expand...
Click to collapse
Do you have a link?
Honestly, I don't know what fauxsound is!

rodpp said:
Do you have a link?
Honestly, I don't know what fauxsound is!
Click to expand...
Click to collapse
Well, i'm not the one who asked this nor I have ever heard about it, but by curiousity I googled this. Got link for this app at Google Play. There are github links in app description to patches that needs to be added to kernel to make this work.
Just can't see Note Pro in officially supported devices -list and don't know can this device even be supported. There reads "Unofficially Supporting: Any Phones using Qualcomm Audio Chip WCD93xx chipsets." But I don't know which chipset NP12.2 got.

Spere said:
Well, i'm not the one who asked this nor I have ever heard about it, but by curiousity I googled this. Got link for this app at Google Play. There are github links in app description to patches that needs to be added to kernel to make this work.
Just can't see Note Pro in officially supported devices -list and don't know can this device even be supported. There reads "Unofficially Supporting: Any Phones using Qualcomm Audio Chip WCD93xx chipsets." But I don't know which chipset NP12.2 got.
Click to expand...
Click to collapse
Thanks, it seems simple if the audio chip is compatible. I'll try to include this in the kernel.

Thanks, Rodrigo for the great work!
Finally i was able to get Ubuntu running using linux complete installer.
Its a shame there's so little development for this great device.
I wish i had skills to do some.
Thanks, from Piracicaba-SP

js345 said:
Thanks, Rodrigo for the great work!
Finally i was able to get Ubuntu running using linux complete installer.
Its a shame there's so little development for this great device.
I wish i had skills to do some.
Thanks, from Piracicaba-SP
Click to expand...
Click to collapse
Yes, one of my motivations to compile this kernel was to boot Linux images too.
Regards,
Rodrigo.
Enviado de meu SM-P905M usando Tapatalk

rodpp said:
Thanks, it seems simple if the audio chip is compatible. I'll try to include this in the kernel.
Click to expand...
Click to collapse
I tried to compile the kernel with the patches sugested by the Fauxsound developer but, unfortunately, I have no success.
Probably it will be necessary more kernel modifications to compile it with the Fauxsound patches.
Enviado de meu SM-P905M usando Tapatalk

Hi,
I have a question about your kernel.
does it contains a root feature ?
I am running XXUANI1 firmware on P900 (wifi version), and have tried the auto root from Chainfire.
it does not work well (I think it was release for a previous firmware), and give a lot of random reboot.
I was thinking that may be I could flash a kernel accepting to work with su.bin
thanks for any information.
Olivier

orobin said:
Hi,
I have a question about your kernel.
does it contains a root feature ?
I am running XXUANI1 firmware on P900 (wifi version), and have tried the auto root from Chainfire.
it does not work well (I think it was release for a previous firmware), and give a lot of random reboot.
I was thinking that may be I could flash a kernel accepting to work with su.bin
thanks for any information.
Olivier
Click to expand...
Click to collapse
The kernel is for P905M/P905...

Guide for Building Custom Kernel XPERIA E1

This is not my work this a reply i got from a guy when i posted in the sony developers forum ...I hope someone finds this useful:angel: .And since i m a new user i can post links for some stupid reasons...so i will get creative
by fzort
Kernel source for the Xperia E1 is available as a tarball on the "Xperia open source archives" site. I'm running a custom-built kernel on my Xperia E1 (D2114). I documented what I did here:
[https://
github.com
/mpersano
/xperia-e1-kernel-patches
/blob
/master
/README.md]

https://github.com/mpersano/xperia-e1-kernel-patches/blob/master/README.md

This is for KK or JB4.3?
Since im starting development for this device, idk much and i not read actual progress. @Kizoky you can resume progress for me?

Caio99BR said:
This is for KK or JB4.3?
Since im starting development for this device, idk much and i not read actual progress. @Kizoky you can resume progress for me?
Click to expand...
Click to collapse
This is for KK kernel, but I couldn't not build kernel because I'm still a rookie
Camera drivers exists for MSM8610(Xperia E1's chipset) on sonyxperiadev Github
Recovery exists (you can find PhilZ recovery in this forum)
what is still missing is a working Device tree, and vendor libs (and of course a cm compatible kernel)

Kizoky said:
This is for KK kernel, but I couldn't not build kernel because I'm still a rookie
Camera drivers exists for MSM8610(Xperia E1's chipset) on sonyxperiadev Github
Recovery exists (you can find PhilZ recovery in this forum)
what is still missing is a working Device tree, and vendor libs (and of course a cm compatible kernel)
Click to expand...
Click to collapse
Ok, but for now a kernel working in Stock is good, so how i can unpack boot.img?
Enviado de meu E435 (L3 II Dual) usando Tapatalk

Use this:

Zsenyka said:
Use this:
Click to expand...
Click to collapse
Edited: The Bootloader is locked, so the boot.img is "Encripted", and no way to unpack this, i will unlock this.

Ok, i changed boot.img, now i have CWM from boot, and bootsrap.
I tried to boot it, but this get bootloop, the bootanimation is loaded but bootloop, maybe dt.img.
I cant access dmesg command. @Kizoky any tip?
---------- Post added at 10:44 PM ---------- Previous post was at 10:44 PM ----------
https://github.com/Caio99BR/android_kernel_sony_falconss

Caio99BR said:
Ok, i changed boot.img, now i have CWM from boot, and bootsrap.
I tried to boot it, but this get bootloop, the bootanimation is loaded but bootloop, maybe dt.img.
I cant access dmesg command. @Kizoky any tip?
Click to expand...
Click to collapse
Hi! I'm the owner of the github repo mentioned at the top of this thread.
Getting a working ramdisk took me a while. I think that what finally worked was downloading an official firmware image with XperiFirm (you don't even need to wait for it to finish downloading the full image - one of the first files downloaded is the kernel one, containing boot.img), then I extracted boot.img with the unofficial XPERIA flash tool, then extracted the ramdisk. (The kernel command line I used is the same one in the official boot.img, by the way.) As for the device tree image, you can build it from the kernel sources.
Note that boot.img on this phone has a device tree blob appended to the end. I wrote a small script to unpack the official boot.img and compare it to the one that I built and check if I was doing everything right (can't post links as I'm a new user, but it's linked in the README.md file linked above).
I'll try to add more details to those instructions when I have some time (I didn't think anyone else would be interested in building a kernel for this cheap phone ). By the way, I use the E1 with a custom kernel as my main personal phone and it works fine (for a 512M phone), kudos to Sony for not compromising the quality of even their lowest end model.

I think everyone is interested in making this phone better
Since July 2014 we tried porting Cyanogenmod without success, now last year we modified a Moto E ROM and made it work with E1, only the ril is not working
So sad that Sony didn't made this phone even better
So the device tree is located in the ramdisk?

Kizoky said:
I think everyone is interested in making this phone better
Since July 2014 we tried porting Cyanogenmod without success, now last year we modified a Moto E ROM and made it work with E1, only the ril is not working
So sad that Sony didn't made this phone even better
So the device tree is located in the ramdisk?
Click to expand...
Click to collapse
The device tree is located after the ramdisk in boot.img, but you can build it from the kernel sources provided by Sony. The `msm8610-v2-mtp.dtb` make target will build the device tree blob. Then mkqcdtbootimg will build a boot.img containing kernel + ramdisk + device tree blob. The only thing that you need for this which is not provided by Sony (well, other than more detailed build instructions...) is a ramdisk image, I had to extract it from the stock firmware...
If you want to split boot.img into kernel / ramdisk / device tree, you can use this script: github.com/mpersano/bootimg-tools/blob/master/split-bootimage.py
Good luck!

fzort said:
The device tree is located after the ramdisk in boot.img, but you can build it from the kernel sources provided by Sony. The `msm8610-v2-mtp.dtb` make target will build the device tree blob. Then mkqcdtbootimg will build a boot.img containing kernel + ramdisk + device tree blob. The only thing that you need for this which is not provided by Sony (well, other than more detailed build instructions...) is a ramdisk image, I had to extract it from the stock firmware...
If you want to split boot.img into kernel / ramdisk / device tree, you can use this script: github.com/mpersano/bootimg-tools/blob/master/split-bootimage.py
Good luck!
Click to expand...
Click to collapse
I've been trying to get that script work like ages
Does it require Linux, or just Python?
EDIT: nvm, I figured it out

So is CM for E1 finally possible or just custom kernel?

@fzort @Kizoky i make this booting with the stock dt blob (device tree means the Android Device Tree, and this is totally diff, use "dt blob")
See my changes in https://github.com/Caio99BR/android_kernel_sony_falconss
Ah, only with msm8610-v2-mtp.dtb this works too, i tested after.
("I not reply more earlier because the phone is from my father and yesterday ran out of energy.")
The ramdisks works and dt blobs too.
The screenshot

Caio99BR said:
@fzort @Kizoky i make this booting with the stock dt blob (device tree means the Android Device Tree, and this is totally diff, use "dt blob")
See my changes in https://github.com/Caio99BR/android_kernel_sony_falconss
Ah, only with msm8610-v2-mtp.dtb this works too, i tested after.
("I not reply more earlier because the phone is from my father and yesterday ran out of energy.")
The ramdisks works and dt blobs too.
The screenshot
Click to expand...
Click to collapse
I saw you are doing the device part of E1 too
If you need any help just ask me (or tests)

Kizoky said:
I saw you are doing the device part of E1 too
If you need any help just ask me (or tests)
Click to expand...
Click to collapse
Ok man, im trying to do kernel fully working (solved problem of dt blobs. We cant pack qrd dt, so comment build of then), and zip easy flashing, but not working at moment, my father will get crazy when him try to play FM Radio.
After i will merge code to a CAF Linux Kernel, so this is more easy to update.
By last finish the Android Device Tree with a E1 Caf Kernel.
I will try to post the custom kernel.
Im thinking in VeeSSKernel (Since my kernel of L3II is VeeKernel), what do you think?
Enviado de meu E435 (L3 II Dual) usando Tapatalk

Caio99BR said:
Ok man, im trying to do kernel fully working (solved problem of dt blobs. We cant pack qrd dt, so comment build of then), and zip easy flashing, but not working at moment, my father will get crazy when him try to play FM Radio.
After i will merge code to a CAF Linux Kernel, so this is more easy to update.
By last finish the Android Device Tree with a E1 Caf Kernel.
I will try to post the custom kernel.
Im thinking in VeeSSKernel (Since my kernel of L3II is VeeKernel), what do you think?
Enviado de meu E435 (L3 II Dual) usando Tapatalk
Click to expand...
Click to collapse
Would be really great
We still don't have a custom kernel (only Stock kernel with PhilZ)
I can't wait to see it

Kizoky said:
Would be really great
We still don't have a custom kernel (only Stock kernel with PhilZ)
I can't wait to see it
Click to expand...
Click to collapse
We have a problem, the TV is not working anymore, idk why
I will check it, we need TV Support working, or i need it, since my father use it
EDIT: The problem is inside kernel or ramdisk.

it's amazing .. Very good work .. Congratulations friends??

racer.z said:
it's amazing .. Very good work .. Congratulations friends����
Click to expand...
Click to collapse
@Kizoky TV is fixed
Edit: THANKS, i forget ever
---------- Post added at 10:59 PM ---------- Previous post was at 10:19 PM ----------
I will try to release tomorrow, since i want to make a new banner, based on my old VeeKernel banner.
For CM i will need to redownload CAF Kernel MSM (since im stupid and overwrited .git in tests).
I will start building TWRP (V3), merging it to stock ramdisk and update to make cwm and twrp side-by-side.
So i have done this in two weeks for make a custom kernel, thanks @fzort
Enviado de meu E435 (L3 II Dual) usando Tapatalk

Axon 7 GitHub Resources

@jcadduono - http://forum.xda-developers.com/showpost.php?p=68223333&postcount=5
sources: https://github.com/jcadduono/android...e_zte_ailsa_ii
kernel: https://github.com/jcadduono/android...mmits/twrp-6.0
@Unjustified Dev
TWRP: https://github.com/TeamRegular/android_device_zte_ailsa_ii
A user on the Chinese ZTE forums has created a github with the Axon 7 kernel code in it based on the A2017U B18 kernel dump.
http://www.myzte.cn/thread-272111-1-2.html
https://github.com/snowwolf725/ZTE_Axon7

TeutonJon78 said:
A user on the Chinese ZTE forums has created a github with the Axon 7 kernel code in it. Seems based off of the A2017U kernel dump.
http://www.myzte.cn/thread-272111-1-2.html
https://github.com/snowwolf725/ZTE_Axon7
Click to expand...
Click to collapse
ZTE have the kernel uploaded. (been up for quiet a while now)
http://opensource.ztedevice.com/
Under smartphone - ZTE A2017U

DrakenFX said:
ZTE have the kernel uploaded. (been up for quiet a while now)
www.opensource.zte.com
Under smartphone - ZTE A2017U
Click to expand...
Click to collapse
Yes, I've had since then. However, this is all github'ed, compile tested, and ready for forking.

We also have @jcadduono device tree and kernel posted from his TWRP work: http://forum.xda-developers.com/showpost.php?p=68195475&postcount=17

anks329 said:
We also have @jcadduono device tree and kernel posted from his TWRP work: http://forum.xda-developers.com/showpost.php?p=68195475&postcount=17
Click to expand...
Click to collapse
Indeed, I recommend folks clone this:
https://github.com/jcadduono/android_kernel_zte_msm8996/commits/stock-6.0
It's merged into CAF and allows future CAF merges without any issues. I updated it just the other day. Very clean kernel from ZTE, I've been really impressed.
From my stock-6.0 branch you can just run ./build.sh to compile a Image.gz and ./dtbgen.sh is automatically run after build to create a dtb.img.
I dont recommend using Image.gz-dtb as dtb building was not correctly set up by ZTE and I haven't bothered fixing it. Separated dtb.img works great though.
DEFCONFIG=zte_defconfig
DEVICE_DEFCONFIG=device_ailsa_ii
Otherwise you can use opensource-caf branch which is pure ZTE with no build modifications or scripts from me.
As for flashing kernels you build, check out LazyFlasher installer at:
https://github.com/jcadduono/lazyflasher
It will dynamically replace kernel image and dtb, and has a folder to put patch shell scripts. dm verity and forced encryption disabling already included as an example. Supports LZ4, Gzip, Bzip2, and LZO so far. Readme has more info. Avoids the need to constantly update ramdisks, and other branches have examples of things like SuperSU policy mod.

Hey guys, I am a developer thinking of buying this great cell phone. I've never tried to develop kernels or ROMs but I would love to learn and contribute to this community.
How could be the easiest way to learn and to start working in things related with this phone?
Thanks.

Thanks a lot for all the info!
@TeutonJon78 Maybe it would be beneficial to add these infos to the OP?

So...now we have two competing TWRP/device tree setups. @jcadduono and @Unjustified Dev it might make sense to keep them similar as make sure there aren't competing versions running around and making support harder.
Edit: I also updated the title of the thread to reference a more generic change -- just listing all known github resources.

grujildo said:
Hey guys, I am a developer thinking of buying this great cell phone. I've never tried to develop kernels or ROMs but I would love to learn and contribute to this community.
How could be the easiest way to learn and to start working in things related with this phone?
Thanks.
Click to expand...
Click to collapse
Well first of all you need the cellphone but it is heavily back-ordered, you can pre-order it now and you might or might not get it on 09/09/16.
I pre-ordered a month ago so I'll get my Gray Axon 7 on monday 08/22/16 (already have the tracking number), I would be willing to sacrifice it (selling it to you) if you want it, for the full price of course ($400 plus shipping). No means to sell anything, I'm not here to sell phones BUT if it is for a developer I'll do it and sacrifice a couple more weeks of wait time. All for the team.

grujildo said:
Hey guys, I am a developer thinking of buying this great cell phone. I've never tried to develop kernels or ROMs but I would love to learn and contribute to this community.
How could be the easiest way to learn and to start working in things related with this phone?
Thanks.
Click to expand...
Click to collapse
https://wiki.cyanogenmod.org/w/Doc:_porting_intro
This would be the best place to start learning Rom building.

Jose-MXL said:
Well first of all you need the cellphone but it is heavily back-ordered, you can pre-order it now and you might or might not get it on 09/09/16.
I pre-ordered a month ago so I'll get my Gray Axon 7 on monday 08/22/16 (already have the tracking number), I would be willing to sacrifice it (selling it to you) if you want it, for the full price of course ($400 plus shipping). No means to sell anything, I'm not here to sell phones BUT if it is for a developer I'll do it and sacrifice a couple more weeks of wait time. All for the team.
Click to expand...
Click to collapse
Hey thanks bro, don't worry. I just checked in Amazon and they are announcing that they will have stock on the 22 August, so maybe I will buy it there.
---------- Post added at 02:03 AM ---------- Previous post was at 01:58 AM ----------
Recon Freak said:
https://wiki.cyanogenmod.org/w/Doc:_porting_intro
This would be the best place to start learning Rom building.
Click to expand...
Click to collapse
Hey thanks Recon Freak. Are you going to start developing for this phone? Who are the developers that want to be involved porting CM for the Axon 7.
It would be great to have a master dev on porting ROMs and lp him with the process. Otherwise are there any devs interested on porting CM to this phone?
Thanks.

grujildo said:
Hey thanks bro, don't worry. I just checked in Amazon and they are announcing that they will have stock on the 22 August, so maybe I will buy it there.
---------- Post added at 02:03 AM ---------- Previous post was at 01:58 AM ----------
Hey thanks Recon Freak. Are you going to start developing for this phone? Who are the developers that want to be involved porting CM for the Axon 7.
It would be great to have a master dev on porting ROMs and lp him with the process. Otherwise are there any devs interested on porting CM to this phone?
Thanks.
Click to expand...
Click to collapse
I wish I had the time and skilz. I can build roms and tweak stuff, but that's it. I know the processes but time and knowledge are not on a 44 year old father of two's side. Tree development is best left to the young and knowledgable.

grujildo said:
Hey thanks bro, don't worry. I just checked in Amazon and they are announcing that they will have stock on the 22 August, so maybe I will buy it there.
Click to expand...
Click to collapse
I just ordered one yesterday and it will arrive 8/25, but seems that they are already out of stock by now... 1 to 2 months is the status now

Recon Freak said:
I wish I had the time and skilz. I can build roms and tweak stuff, but that's it. I know the processes but time and knowledge are not on a 44 year old father of two's side. Tree development is best left to the young and knowledgable.
Click to expand...
Click to collapse
Nice, If I managed to get the phone early I will tell you and we'll be able to port CM for sure
---------- Post added at 08:05 PM ---------- Previous post was at 08:05 PM ----------
Gachmuret said:
I just ordered one yesterday and it will arrive 8/25, but seems that they are already out of stock by now... 1 to 2 months is the status now
Click to expand...
Click to collapse
Yes ****, I just saw. Anyone know another way to get the phone?

grujildo said:
Nice, If I managed to get the phone early I will tell you and we'll be able to port CM for sure
---------- Post added at 08:05 PM ---------- Previous post was at 08:05 PM ----------
Yes ****, I just saw. Anyone know another way to get the phone?
Click to expand...
Click to collapse
There is some on Ebay right at the $400 mark, that's how I planned to sell you mine in case you wanted it.

Backport Kernel for Xiaomi Mi A1 Based on CAF sources

After the liberation of the kernel by Xiaomi, and seeing what they have done, I have done a Backport of the kernel, over the CAF tag LA.UM.5.6.r1-04600-89xx.0.
You can see the backport code here:
https://github.com/mifl/android_[LIST] [/LIST]kernel_xiaomi_tissot.
You can see the Xiaomi original code here:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/tissot-n-oss.
You can see the cm-14.1 code here:
https://github.com/mifl/android_kernel_xiaomi_tissot/tree/cm-14.1
Please: do not ask questions about Merges, Mods and Tweaks, because they will not be answered.
Greetings.

mifl said:
After the liberation of the kernel by Xiaomi, and seeing what they have done, I have done a Backport of the kernel, over the CAF tag LA.UM.5.6.r1-04600-89xx.0.
You can see the code here:
https://github.com/mifl/android_
kernel_xiaomi_tissot.
Greetings.
Click to expand...
Click to collapse
Does it build? I tried both yours and xiaomis and had a ton of errors

sooti said:
Does it build? I tried both yours and xiaomis and had a ton of errors
Click to expand...
Click to collapse
Please compile the kernel correctly.
You can get a compilation script in the following branch:
https://github.com/mifl/android_kernel_xiaomi_tissot/commits/build.
The original Xiaomi kernel and my Backport compile correctly using this script.
Greetings.

mifl said:
Please compile the kernel correctly.
You can get a compilation script in the following branch:
https://github.com/mifl/android_kernel_xiaomi_tissot/commits/build.
The original Xiaomi kernel and my Backport compile correctly using this script.
Greetings.
Click to expand...
Click to collapse
Script didn't work for me but I was able to build with your latest commits, cheers

Good work, thanks
It can be a very immortal device with the help of XDA
Sent from my Mi A1 using XDA Labs

sooti said:
Script didn't work for me but I was able to build with your latest commits, cheers
Click to expand...
Click to collapse
You can get the compilation script and apply it to your kernel source with this patch:
https://github.com/mifl/android_kernel_xiaomi_tissot/compare/build.patch

mifl said:
After the liberation of the kernel by Xiaomi, and seeing what they have done, I have done a Backport of the kernel, over the CAF tag LA.UM.5.6.r1-04600-89xx.0.
You can see the backport code here:
https://github.com/mifl/android_[LIST] [/LIST]kernel_xiaomi_tissot.
You can see the Xiaomi original code here:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/tissot-n-oss.
Greetings.
Click to expand...
Click to collapse
Thank you very much! I appreciate your help.

@mifl kernel boots fine but can you point me to the needed commits for oreo? I can't seem to find the needed ones

sooti said:
@mifl kernel boots fine but can you point me to the needed commits for oreo? I can't seem to find the needed ones
Click to expand...
Click to collapse
The smartest thing, at the moment is to include all the commits that we can find from the caf or aosp sources, to reduce the initial commit "Kernel: Xiaomi kernel changes for Mi A1.". This will make the developers of LineageOS and others able to use these sources, and also make it easier to make a port to the CAF branch for Android Oreo.
This work I am starting to do now and will be uploaded to the branch of my kernel: "develop". This branch will be updated using force push, to reduce the aforementioned commit.
Greetings.

At the moment these are the changes I've found in caf or aosp sources, to reduce the initial commit "Kernel: Xiaomi kernel changes for My A1.":
https://github.com/mifl/android_kernel_xiaomi_tissot/compare/master...92c73b0
The final result can be seen in the branch:
https://github.com/mifl/android_kernel_xiaomi_tissot/commits/develop
Greetings.

mifl said:
At the moment these are the changes I've found in caf or aosp sources, to reduce the initial commit "Kernel: Xiaomi kernel changes for My A1.":
https://github.com/mifl/android_kernel_xiaomi_tissot/compare/master...92c73b0
The final result can be seen in the branch:
https://github.com/mifl/android_kernel_xiaomi_tissot/commits/develop
Greetings.
Click to expand...
Click to collapse
any kernel made for stock (8.0) with some mods
eg enabled Qcomm fast charge battery tweaks cpu throttling
etc? looking forward to it thanks ?

Nice job there! :highfive:
And thank you Xiaomi, for making devs work more harder than what they should have.
Sent from my Redmi Note 4 using XDA Labs

@mifl Can we use your modified kernel source to build Lineage OS, or does it need some modifications?
---------- Post added at 07:03 AM ---------- Previous post was at 06:59 AM ----------
[/COLOR @mifl Can we use this kernel to build Lineage 14.1 or does it require some more edits?

mifl said:
At the moment these are the changes I've found in caf or aosp sources, to reduce the initial commit "Kernel: Xiaomi kernel changes for My A1.":
https://github.com/mifl/android_kernel_xiaomi_tissot/compare/master...92c73b0
The final result can be seen in the branch:
https://github.com/mifl/android_kernel_xiaomi_tissot/commits/develop
Greetings.
Click to expand...
Click to collapse
Ya those look like the same commits I tried... I have no problem getting the kernel to boot but the data is encrypted... What am I missing?
---------- Post added at 09:51 AM ---------- Previous post was at 09:48 AM ----------
mifl said:
At the moment these are the changes I've found in caf or aosp sources, to reduce the initial commit "Kernel: Xiaomi kernel changes for My A1.":
https://github.com/mifl/android_kernel_xiaomi_tissot/compare/master...92c73b0
The final result can be seen in the branch:
https://github.com/mifl/android_kernel_xiaomi_tissot/commits/develop
Greetings.
Click to expand...
Click to collapse
I'm still at the same place as before... the kernel boots find (did also before) but the data is encrypted... What am I missing?

Isn't the tissot kernel source already based off LA.UM.5.6.r1-04600-89xx.0? It's obviously based on LA.UM.5.6.r1 coz Android 7.1.2 msm8953_64. Don't let the comment on the squashed commit fool you otherwise.

Sorry guys xda wasn't working for me hence it's showing multiple posts. Mod please remove duplicate posts like this one

Duplicate

Sorry guys xda wasn't working for me hence it's showing multiple posts. Mod please remove duplicate posts like this one

bgos10 said:
Isn't the tissot kernel source already based off LA.UM.5.6.r1-04600-89xx.0? It's obviously based on LA.UM.5.6.r1 coz Android 7.1.2 msm8953_64. Don't let the comment on the squashed commit fool you otherwise.
Click to expand...
Click to collapse
Xiaomi destroyed commit history on the released source, by squashing even the tags used as the base over an older, LA.UM.5.3-06310-89xx.0, as a single "Xiaomi kernel changes for Mi A1." commit.
Probably you've to run git diff HEAD~1 at least once and see what it mostly changed.
Sent from my Redmi Note 4 using XDA Labs

@Uvneshkumar. The kernel is open source, you can use this like you want.
Greetings.

LineageOS 15.1 arm64 - testers needed

I'm looking for brave souls with spare Moto g5s. I made build but i cannot test it because its my daily device.
I cannot give a warranty that this build will not hardbrick your device or even boot up.
So if u want to take a risk and try it, send me pm or write comment under this post and i will provide link for zip.
Thanks in advance

I have a G5S but it's my daily phone too...
Please someone be brave

My mother is using my g5s, I will post it on telegram group

Just for curiosity: How did you manage to port this ROM for G5S?

wiktorek140 said:
I'm looking for brave souls with spare Moto g5s. I made build but i cannot test it because its my daily device.
I cannot give a warranty that this build will not hardbrick your device or even boot up.
So if u want to take a risk and try it, send me pm or write comment under this post and i will provide link for zip.
Thanks in advance
Click to expand...
Click to collapse
Hi, can you talk with @rssxda1 on telegram?

Probably i can. What do you mean? I just take cedric device tree, rename what needed. Replace binaries and compile it

Mutcholoko said:
Just for curiosity: How did you manage to port this ROM for G5S?
Click to expand...
Click to collapse
And I didn't port for now. I just build rom for montana, and need someone for test it. I will name it "porting" when at least it boot

wiktorek140 said:
Probably i can. What do you mean? I just take cedric device tree, rename what needed. Replace binaries and compile it
Click to expand...
Click to collapse
Super cool. I always wanted to learn how to do it.
I actually understand the process itself, but I can't understand this binaries and kernel part. Do you recommend any place to learn this?

wiktorek140 said:
Probably i can. What do you mean? I just take cedric device tree, rename what needed. Replace binaries and compile it
Click to expand...
Click to collapse
FIY only camera blobs need to be replaced, and the sensors blobs (cedric uses motosh and montana uses sensors.qcom). i already made an treee for montana, but i had ****ed up the sensors. github.com/motorola-common . i think its best for you to make your tree based on the sanders tree, and use the common vendor i made on github.com/kalil-devices . for doing the bringup based on the sanders tree you will need to get the mixer paths, the media configs, the camera configs, and the sensor configs, and the camera blobs. thats pretty much it. good luck.
---------- Post added at 10:56 AM ---------- Previous post was at 10:54 AM ----------
wiktorek140 said:
And I didn't port for now. I just build rom for montana, and need someone for test it. I will name it "porting" when at least it boot
Click to expand...
Click to collapse
if you install an cedric build and an montana arm64 kernel, it will boot BTW. camera and sensors will be broken, but because motosh is initialized, sensors won't prevent the device from booting

KalilDev said:
FIY only camera blobs need to be replaced, and the sensors blobs (cedric uses motosh and montana uses sensors.qcom). i already made an treee for montana, but i had ****ed up the sensors. github.com/motorola-common . i think its best for you to make your tree based on the sanders tree, and use the common vendor i made on github.com/kalil-devices . for doing the bringup based on the sanders tree you will need to get the mixer paths, the media configs, the camera configs, and the sensor configs, and the camera blobs. thats pretty much it. good luck.
---------- Post added at 10:56 AM ---------- Previous post was at 10:54 AM ----------
if you install an cedric build and an montana arm64 kernel, it will boot BTW. camera and sensors will be broken, but because motosh is initialized, sensors won't prevent the device from booting
Click to expand...
Click to collapse
But i just ask about someone who will test it not how to fix something what i dont know it even work. And device tree from motorola-common don't even compile for me(wifi errors that something missing- i can't find solution)

Solved. My build dont even boot xD
Maybe next time

wiktorek140 said:
Solved. My build dont even boot xD
Maybe next time
Click to expand...
Click to collapse
Bad

I volunteer

wiktorek140 said:
I'm looking for brave souls with spare Moto g5s. I made build but i cannot test it because its my daily device.
I cannot give a warranty that this build will not hardbrick your device or even boot up.
So if u want to take a risk and try it, send me pm or write comment under this post and i will provide link for zip.
Thanks in advance
Click to expand...
Click to collapse
Give the link of the rom I happy ? to try in my phone ? now
Because I looking for 64 bit rom for moto g5s device

Send me the link I volunteer

KalilDev said:
FIY only camera blobs need to be replaced, and the sensors blobs (cedric uses motosh and montana uses sensors.qcom). i already made an treee for montana, but i had ****ed up the sensors. github.com/motorola-common . i think its best for you to make your tree based on the sanders tree, and use the common vendor i made on github.com/kalil-devices . for doing the bringup based on the sanders tree you will need to get the mixer paths, the media configs, the camera configs, and the sensor configs, and the camera blobs. thats pretty much it. good luck.
Click to expand...
Click to collapse
List me the blobs you need and I can pull them for you. My phone runs official Oreo 8.1.
Edit: You already made a list, lol. Just be more specific. Which files, exactly, need to be pulled?

Kamin4ri said:
List me the blobs you need and I can pull them for you. My phone runs official Oreo 8.1.
Edit: You already made a list, lol. Just be more specific. Which files, exactly, need to be pulled?
Click to expand...
Click to collapse
I think it require only files from /vendor to make camera work( i dont see any device specific file in /system), i have stock oreo too so i have all required files, and later i can push to github what i achieved

Kamin4ri said:
List me the blobs you need and I can pull them for you. My phone runs official Oreo 8.1.
Edit: You already made a list, lol. Just be more specific. Which files, exactly, need to be pulled?
Click to expand...
Click to collapse
i have montana stock for ages now. i have a montana vendor set up too.

KalilDev said:
i have montana stock for ages now. i have a montana vendor set up too.
Click to expand...
Click to collapse
Hmm, have u pushed it to github or it is a redo branch on motorola common?

Today will be new build, testers needed again