Database Develop

[Q] Xperia SP Device Tree/ Proprietary Blobs

Hey guys,
I know the dev scene is pretty bleak here. I already had the android 4.3 jellybean source code synced on my laptop, since I was creating builds for my Nexus.
I tried for the SP, but then I realized that there is no device tree present. I found one by Krabappel but it was incomplete (or atleast I think so). It refers to 2 other extract-files.sh, but for the life of me I can't figure out which ones.
I know there are a few devs here, so can one of them help me out here? How to I get the blobs for the phone?
If I get that going, we can start with an AOSP build and then keep adding stuff to it.
Let me know. \
Cheers! :good:

sarkar1990 said:
Hey guys,
I know the dev scene is pretty bleak here. I already had the android 4.3 jellybean source code synced on my laptop, since I was creating builds for my Nexus.
I tried for the SP, but then I realized that there is no device tree present. I found one by Krabappel but it was incomplete (or atleast I think so). It refers to 2 other extract-files.sh, but for the life of me I can't figure out which ones.
I know there are a few devs here, so can one of them help me out here? How to I get the blobs for the phone?
If I get that going, we can start with an AOSP build and then keep adding stuff to it.
Let me know. \
Cheers! :good:
Click to expand...
Click to collapse
I tried building cm10.1 for the sp, but could not get past the kernel logo. Even the recovery didn't work.
If you want the blobs, I can upload them somewhere. I had extracted them from the current 4.1.2 implementation on the device.

the extract-files.sh are in the below repo
"repository": "android_device_sony_common",
"target_path": "device/sony/common"
I have tried to build the recoveryimage but I am getting problem in builting kernel.elf as normally it is in kernel.img
I have tried to both method building kernel and using zImage.

nil1511 said:
the extract-files.sh are in the below repo
"repository": "android_device_sony_common",
"target_path": "device/sony/common"
I have tried to build the recoveryimage but I am getting problem in builting kernel.elf as normally it is in kernel.img
I have tried to both method building kernel and using zImage.
Click to expand...
Click to collapse
Did you try to convert the zimage to elf using the build tools?
Here's the link that you may try http://forum.xda-developers.com/showpost.php?p=43356450&postcount=2

eeehaw said:
I tried building cm10.1 for the sp, but could not get past the kernel logo. Even the recovery didn't work.
If you want the blobs, I can upload them somewhere. I had extracted them from the current 4.1.2 implementation on the device.
Click to expand...
Click to collapse
Awesome. You can either upload them link me the git if its there

sarkar1990 said:
Did you try to convert the zimage to elf using the build tools?
Here's the link that you may try http://forum.xda-developers.com/showpost.php?p=43356450&postcount=2
Click to expand...
Click to collapse
I mean that i tried to make write device files from scratch
as given here
[link]http://wiki.cyanogenmod.org/w/Doc:_porting_intro[/link]
as on method 3 i tried using zImage as kernel as stated there.
but make recoveryimage fails

nil1511 said:
I mean that i tried to make write device files from scratch
as given here
[link]http://wiki.cyanogenmod.org/w/Doc:_porting_intro[/link]
as on method 3 i tried using zImage as kernel as stated there.
but make recoveryimage fails
Click to expand...
Click to collapse
If you want to learn. It would be best to clone the Doomlord git and then read the files and scripts that are present there. This will give you the knowledge you may need to proceed further.
the git for our processor msm8960t is already present on github. Also download the kernel sources and drivers provided by Sony themselves from their developerworld page

sarkar1990 said:
the git for our processor msm8960t is already present on github.
Click to expand...
Click to collapse
You mean the kernel sources or the cm / aosp sources ? Can you provide a link.

eeehaw said:
You mean the kernel sources or the cm / aosp sources ? Can you provide a link.
Click to expand...
Click to collapse
Here is the link
https://github.com/DooMLoRD/android_kernel_sony_msm8960t.git

eeehaw said:
I tried building cm10.1 for the sp, but could not get past the kernel logo. Even the recovery didn't work.
If you want the blobs, I can upload them somewhere. I had extracted them from the current 4.1.2 implementation on the device.
Click to expand...
Click to collapse
I am using the device tree: https://github.com/Krabappel2548/android_device_sony_huashan
I added CPU_TARGET_VARIANT according to JB 4.3 requirements. And loaded up the required gits.
But the thing is now I get an error:
Code:
Code:
make: *** No rule to make target `device/sony/huashan/zImage', needed by `out/target/product/huashan/kernel'. Stop.
Could you help me out a bit?

I recall CM10.1 needing a kernel build from scratch, along with building the ROM
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."

sarkar1990 said:
I am using the device tree: https://github.com/Krabappel2548/android_device_sony_huashan
I added CPU_TARGET_VARIANT according to JB 4.3 requirements. And loaded up the required gits.
But the thing is now I get an error:
Code:
Code:
make: *** No rule to make target `device/sony/huashan/zImage', needed by `out/target/product/huashan/kernel'. Stop.
Could you help me out a bit?
Click to expand...
Click to collapse
I did not use krabappel's device files. I had based my stuff on the Xperia T. I'll try this probably tonight.

eeehaw said:
I did not use krabappel's device files. I had based my stuff on the Xperia T. I'll try this probably tonight.
Click to expand...
Click to collapse
Can you push your device file on github

nil1511 said:
Can you push your device file on github
Click to expand...
Click to collapse
I'm behind a very nasty proxy which makes it super hard to push/pull files from github. Instead of pulling i just download the zip archives.
I'll check out ways to push files though.

eeehaw said:
I'm behind a very nasty proxy which makes it super hard to push/pull files from github. Instead of pulling i just download the zip archives.
I'll check out ways to push files though.
Click to expand...
Click to collapse
Man, I keep running into the error! Ahh.. I think we need a better device tree.

sarkar1990 said:
Man, I keep running into the error! Ahh.. I think we need a better device tree.
Click to expand...
Click to collapse
Try getting the yuga tree, and change yuga to huashan, and fusion3 to viskan wherever possible.
This should not be straightforward. You will have to make some tweaks also.
That *might* work.
CallMeVentus said:
I recall CM10.1 needing a kernel build from scratch, along with building the ROM
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
Click to expand...
Click to collapse
You mean coping the kernel sources files to kernel/sony/huashan right ? I did the same thing.

eeehaw said:
Try getting the yuga tree, and change yuga to huashan, and fusion3 to viskan wherever possible.
This should not be straightforward. You will have to make some tweaks also.
That *might* work.
You mean coping the kernel sources files to kernel/sony/huashan right ? I did the same thing.
Click to expand...
Click to collapse
Hmm....and did you define the kernel building path in the boardconfig.mk?
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."

CallMeVentus said:
Hmm....and did you define the kernel building path in the boardconfig.mk?
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
Click to expand...
Click to collapse
yes. The kernel was getting built. I was able to see a boot logo on the screen. FreeXperia/Sony logo in this case. And then it would hang. Once I got a bootloop. I was messing around with the ramdisk to see if any hacks get it working.

eeehaw said:
yes. The kernel was getting built. I was able to see a boot logo on the screen. FreeXperia/Sony logo in this case. And then it would hang. Once I got a bootloop. I was messing around with the ramdisk to see if any hacks get it working.
Click to expand...
Click to collapse
Did you implement the changes needed for a CM kernel from its stock sources? I'm not sure of the changes, though. Each kernel differs.
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."

CallMeVentus said:
Did you implement the changes needed for a CM kernel from its stock sources? I'm not sure of the changes, though. Each kernel differs.
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
Click to expand...
Click to collapse
No. I knew there were changes but I never knew what they were ? I asked a few people in a few threads but was not able to decipher.
Do you have any idea what sort of changes are required. ?

[10-06-2014][ROM][DISCONTINUED] UnityROM-2 v.2.5.0 [CM-11][Optimized]

UnityROM-2 v.2.5.0
*****Discontinued.... No way to test actively till I have a functional build.*****
HTC One M7 Sprint Edition ( m7spr )
​

Development Section...
Want to contribute to the project or become team member?
Contact Me by PM here or leave a post detailing what you can and are willing to do for the projects' advancement.
My Github: https://github.com/LiquidSmokeX64
All current project sources can be found there .
ALSO MY FOOL-PROOF BUILD GUIDE & SCRIPTS ARE THERE FOR THOSE TOO IMPATIENT TO WAIT FOR MY NEXT RELEASE .
**Sources current as of version 2.5.0**
**10/06/2014**
Direct link to guide:
https://github.com/LiquidSmokeX64/Guides-Scripts
Note: Noob Friendly. If you're new to building ROMs or have never done it at all. I will help for as long as you maintain civility and focus on the project goals.​

Installation errors out. Here is a pastebin of log saved after error
http://pastebin.com/fz15gwwn
Edit: I was able to install after removing that set perm line from updater. I will let ya know how it goes.

gruesomewolf said:
Installation errors out. Here is a pastebin of log saved after error
http://pastebin.com/fz15gwwn
Edit: I was able to install after removing that set perm line from updater. I will let ya know how it goes.
Click to expand...
Click to collapse
Ok. I just removed it too. My bad adaptation from Evo LTE. Nothing too bad luckily.
Reuploading the fixed version now.

LiquidSmokeX64 said:
Ok. I just removed it too. My bad adaptation from Evo LTE. Nothing too bad luckily.
Reuploading the fixed version now.
Click to expand...
Click to collapse
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...

gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8

gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
Will you be releasing this kernel for the Evo 4G? [emoji14] Evo4gnoob here

LiquidSmokeX64 said:
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
Click to expand...
Click to collapse
I wouldn't say Im a kernel dev....more of a dabler...lol. I sent you a pm with my makefile so you can see adjustments I made for my kernels latest build (not yet publicly released)
Notorious said:
Will you be releasing this kernel for the Evo 4G? [emoji14] Evo4gnoob here
Click to expand...
Click to collapse
Umm....no I dont have any plans for that ATM

gruesomewolf said:
I wouldn't say Im a kernel dev....more of a dabler...lol. I sent you a pm with my makefile so you can see adjustments I made for my kernels latest build (not yet publicly released)
Umm....no I dont have any plans for that ATM
Click to expand...
Click to collapse
Was joking lol

Notorious said:
Was joking lol
Click to expand...
Click to collapse
So you're allowing the integration of it? Just to be clear.

So I'm not sure why but the kernel borked again. Maybe I need to go through one flag at a time? Or maybe forgot something....?

gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
Hey. Im having nothing but issues building it in the ROM so I was curious if you could tell me what I need to do after copying the msm8960 folder to a new place and adding in the makefile changes? Ive never built a kernel independently before but would like it to be a boot.img like normal so I can just replace the one in the ROM zip with the new one. Im sure it's pretty easy, just figured I'd ask you rather than comb through 80 guides saying different stuff lol.

LiquidSmokeX64 said:
Hey. Im having nothing but issues building it in the ROM so I was curious if you could tell me what I need to do after copying the msm8960 folder to a new place and adding in the makefile changes? Ive never built a kernel independently before but would like it to be a boot.img like normal so I can just replace the one in the ROM zip with the new one. Im sure it's pretty easy, just figured I'd ask you rather than comb through 80 guides saying different stuff lol.
Click to expand...
Click to collapse
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.

gruesomewolf said:
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
Click to expand...
Click to collapse
I'm not seeing errors. Hell I removed everything but the -O3 spots and it still refused to boot. I dont know what the deal is....
Anytim I do ANYTHING to the kernel its dead, no matter how stupid it is.

gruesomewolf said:
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
Click to expand...
Click to collapse
BTW. The makefile is borked. And was curious if you knew how to build AOSP for this device? CM was pretty easy, I'd figure AOSP isn't too different. Then I can try to get Android L running once I have a working Android K to cross-reference to and make the version specific changes in device, kernel, vendor, qcom-common, and s4-common

LiquidSmokeX64 said:
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
Click to expand...
Click to collapse
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk

thicklizard said:
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Absolutely correct. And to elaborate on this just a bit more. Since your source building here, you can actually adjust the ramdiskadd with the scripts, considering it uses mkbootimg commands to build the boot.img.
An additional line in your devices board config, to give it a new ramdiskaddr size. Then an additional line in the build folder factory_ramdisk.mk , to handle the command for a new ramdiskaddr size should do the trick.
As for your other question about building aosp. I'm afraid that would be beyond my area of expertise. You would have significantly modify aosp code to allow for caf. It would be much harder then building cm, cause cm already has all the adjustments needed for caf devices

thicklizard said:
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
gruesomewolf said:
Absolutely correct. And to elaborate on this just a bit more. Since your source building here, you can actually adjust the ramdiskadd with the scripts, considering it uses mkbootimg commands to build the boot.img.
An additional line in your devices board config, to give it a new ramdiskaddr size. Then an additional line in the build folder factory_ramdisk.mk , to handle the command for a new ramdiskaddr size should do the trick.
As for your other question about building aosp. I'm afraid that would be beyond my area of expertise. You would have significantly modify aosp code to allow for caf. It would be much harder then building cm, cause cm already has all the adjustments needed for caf devices
Click to expand...
Click to collapse
I read this and my eyes glaze over. But you are in good hands with these two helping you. :highfive:

Yeah I'm working on it guys. Read the integrated kernel building guide and trying that. But if I could just get it to build me the boot.IMG and get my ramdisk sizes and whatever I'm looking at where to edit it in the device/BoardConfig changed the defconfig to a custom one I made based off the original one from the working boot.IMG but changed the I/O scheduler & CPU governed defaults. Gave it a local name (UnityKernel-x.x.x) and am fighting its last issues. So if nothing else help building it independently might be the most useful now. So if nothing else I can push a new boot.img

My bad. It just says the boot partition size so I think I might be almost there

[REQUEST] Desire 510 Rom Development Guide

Hey, as alot of us know many people have left this phone and moved on to the cooler more exciting phones. and are busy with life.....id like to request a guide for the ones that would like to make some creation and learn how to build...for the love of this phone ^-^and that have some knowledge atleast

Xendrix said:
Hey, as alot of us know many people have left this phone and moved on to the cooler more exciting phones. and are busy with life.....id like to request a guide for the ones that would like to make some creation and learn how to build...for the love of this phone ^-^and that have some knowledge atleast
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/software/guide-build-port-miui-rom-to-device-t3250984 I tried with this but I was getting to much rejects and I couldn't fix them all by my self. Most likely because I was trying to patch the stock 64 bit. But you have the CM, RaptorROM that are more vanilla like. If you are lucky you should be getting less rejects then me. :highfive:

denny.hell said:
http://forum.xda-developers.com/android/software/guide-build-port-miui-rom-to-device-t3250984 I tried with this but I was getting to much rejects and I couldn't fix them all by my self. Most likely because I was trying to patch the stock 64 bit. But you have the CM, RaptorROM that are more vanilla like. If you are lucky you should be getting less rejects then me. :highfive:
Click to expand...
Click to collapse
Ok cool i just pulled that same guide up, ill try it out and see where i get!
Sent from my iPhone using Tapatalk

Xendrix said:
Ok cool i just pulled that same guide up, ill try it out and see where i get!
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
If you need help with the rejects just ask. I'm sure I could spare some time to help out

denny.hell said:
http://forum.xda-developers.com/android/software/guide-build-port-miui-rom-to-device-t3250984 I tried with this but I was getting to much rejects and I couldn't fix them all by my self. Most likely because I was trying to patch the stock 64 bit. But you have the CM, RaptorROM that are more vanilla like. If you are lucky you should be getting less rejects then me. :highfive:
Click to expand...
Click to collapse
That was really not all that great of an instruction on how to get started with rom building because for 1 unless you have a really super fast computer trying to do that in a VMWARE is going to take forever because the first compile and build takes hours upon hours I'm not kidding when I said you needed to download the entire CyanogenMod or AOSP source code and apparently from all the changes people have made its up over 13GB which is huge mind you the first build is going to give quite a few errors which you'll need to fix by going into your github and making changes to the specific file that needs changing and then repo sync or just change it on your local computer first then push it to github.. You did fork the device tree to your own github right? Then you have to download the device tree source to your local pc in order to even begin building anything. They also need to be in the correct spot by the way or the build is gonna throw an error that it can't find / or so and so doesn't exist.. By the way the 3 device tree files you're gonna need are "Device, Vendor and Kernel.."..
https://wiki.cyanogenmod.org/w/Development
https://wiki.cyanogenmod.org/w/Doc:_porting_intro

MrMike2182 said:
That was really not all that great of an instruction on how to get started with rom building because for 1 unless you have a really super fast computer trying to do that in a VMWARE is going to take forever because the first compile and build takes hours upon hours I'm not kidding when I said you needed to download the entire CyanogenMod or AOSP source code and apparently from all the changes people have made its up over 13GB which is huge mind you the first build is going to give quite a few errors which you'll need to fix by going into your github and making changes to the specific file that needs changing and then repo sync or just change it on your local computer first then push it to github.. You did fork the device tree to your own github right? Then you have to download the device tree source to your local pc in order to even begin building anything. They also need to be in the correct spot by the way or the build is gonna throw an error that it can't find / or so and so doesn't exist.. By the way the 3 device tree files you're gonna need are "Device, Vendor and Kernel.."..
https://wiki.cyanogenmod.org/w/Development
https://wiki.cyanogenmod.org/w/Doc:_porting_intro
Click to expand...
Click to collapse
Yes, everything you said is correct. I was only giving him a starting point. I know that porting, in this case patching, is a lot more easier than building, if done properly. If he wants to build and to learn a lot of stuff I personally advice him to follow your advice.
But in the end it's up to him. At least now he has two starting points. :highfive:

denny.hell said:
Yes, everything you said is correct. I was only giving him a starting point. I know that porting, in this case patching, is a lot more easier than building, if done properly. If he wants to build and to learn a lot of stuff I personally advice him to follow your advice.
But in the end it's up to him. At least now he has two starting points. :highfive:
Click to expand...
Click to collapse
That's true, 2 starting points is better than none.. I don't necessarily like "patching" others work because you never really know how they made it or if it has problems which is why I just start from scratch.

Yes starting from scratch was initially what i wanted but i looked around on XDA university for a week and that helped get me to learn about setting up Vm, installing android sdk through terminal ETC and repo init repo sync, downloading repositories and other source codes.....BUT my thing is wanting to learn how patch errors and need more on hands experience for setting up build environment
Sent from my iPhone using Tapatalk

Huawei P9 Lite devs

Good day lads,
Disclaimer:
Code:
I don't know if you noticed a thread in the Q&A section that was closed by Matt. While I respect Matt's decision to close it, I find it a very relevant topic... The future of LineageOS for the P9 Lite. Please note that I do respect meticulous' wishes to charge for his work because I know how time consuming it is I wish to firmly express that I do not condone this mentality when it comes to Linux based operating systems.
I decided to make this thread with my little Dev knowledge in order to attract more devs who's willing to put in work on a stable device tree for free in spirit of community and for all to enjoy.
I do not have the Lineage source code at the moment but I will start downloading soon, I do know that I will need help and I encourage more devs/beginners to lend a hand for the benefit of us all.
Please, to begin, post links to relevant tarballs/links/downloads for development purposes, device tree and kernels, anything you've worked on so perhaps we can all work together.
Cheers
Sent from my HUAWEI VNS-L31 using Tapatalk

Hmmm... The fact that building android ROMs is time consuming is not a good enough reason to request money for OPEN SOURCE SOFTWARE. Yes, LineageOS and android in general are open source, so that's an infraction.
About the collective effort, that's a good idea, but there are no sources from Huawei right now. You need to wait for the Nougat sources if Huawei really gives a dime about releasing them. From that point, it is easier to develop and get stuff working. Until then, good luck working without sources and experimenting stuff. Not to mention that there's no official TWRP as well, and TWRPs posted here on XDA for our devices have specific requirements to get them flashed on your device.

Asphyxiate666 said:
Hmmm... The fact that building android ROMs is time consuming is not a good enough reason to request money for OPEN SOURCE SOFTWARE. Yes, LineageOS and android in general are open source, so that's an infraction.
About the collective effort, that's a good idea, but there are no sources from Huawei right now. You need to wait for the Nougat sources if Huawei really gives a dime about releasing them. From that point, it is easier to develop and get stuff working. Until then, good luck working without sources and experimenting stuff. Not to mention that there's no official TWRP as well, and TWRPs posted here on XDA for our devices have specific requirements to get them flashed on your device.
Click to expand...
Click to collapse
Why do you need to come here with negativity? I don't support meticulous but he can do what he wants with the device sources he took the time to build, heck, he doesn't need to release those sources so I don't know what you're talking about, firstly. Secondly, a device tree can be built, Q.E.D we as a community can work on it together, if they release it we'll just have it much easier.
Note also; I've asked for relevant input and help from the community.
Thanks for your time though.
EDIT: P.S Professional Flasher, have you ever built a ROM before? Because that's my target here, finding people who knows how to fix error and put the tree together
Sent from my HUAWEI VNS-L31 using Tapatalk

Carlyle_f said:
Why do you need to come here with negativity? I don't support meticulous but he can do what he wants with the device sources he took the time to build, heck, he doesn't need to release those sources so I don't know what you're talking about, firstly. Secondly, a device tree can be built, Q.E.D we as a community can work on it together, if they release it we'll just have it much easier.
Note also; I've asked for relevant input and help from the community.
Thanks for your time though.
EDIT: P.S Professional Flasher, have you ever built a ROM before? Because that's my target here, finding people who knows how to fix error and put the tree together
Sent from my HUAWEI VNS-L31 using Tapatalk
Click to expand...
Click to collapse
Ignore it's just a critic custom rom user....[emoji12]

Hipom said:
Ignore it's just a critic custom rom user....[emoji12]
Click to expand...
Click to collapse
My words are razor sharp but honest and realistic.
Sent from my VNS-L21 using Tapatalk

Asphyxiate666 said:
Hmmm... The fact that building android ROMs is time consuming is not a good enough reason to request money for OPEN SOURCE SOFTWARE. Yes, LineageOS and android in general are open source, so that's an infraction.
About the collective effort, that's a good idea, but there are no sources from Huawei right now. You need to wait for the Nougat sources if Huawei really gives a dime about releasing them. From that point, it is easier to develop and get stuff working. Until then, good luck working without sources and experimenting stuff. Not to mention that there's no official TWRP as well, and TWRPs posted here on XDA for our devices have specific requirements to get them flashed on your device.
Click to expand...
Click to collapse
Open source does not mean free, period.

pilgrim011 said:
On xda, it does mean free, period. People that think that they should be paid for contributing here are not welcome on XDA.
Click to expand...
Click to collapse
you are totally right

Just finish already. If you want to discuss all that situation just create some g+ group or telegram for this.
XDA dev thread is not for that king of discussion.
Also it should be in QA SECTION.
You start xda dev thread when you have something made already. Not just with idea.

lsander said:
If you want to discuss all that situation just create some g+ group or telegram for this.
XDA dev thread is not for that king of discussion.
Click to expand...
Click to collapse
This disussions are undesired here. I know a board where you can discuss that. If you want, feel free to have a look at it. This little Board is very pleased about every enlivenment. Opened a thread over there.

Well, developers do not grow on trees. I guess there are not enough devs here who have the P9 Lite device.
However I like the intention of the thread author. For that reason please try to discuss in a human way.
In the end: I am vers interested in learning how to build custom roms but I can't find a way how to learn it. Does anyone have some good advice?

Updated kernel
Hello everyone, I've recently been working on updating the Honor 5c kernel to 3.10.105 and so far it seems to be working fine on my P9lite, LineageOS 14.1. It's based purely on stock, with one or two commits borrowed from Meticulus' kernel repo, so it compiles without errors.
Since this is a new account, I can't link my repo directly, you can find it on my github profile, Avsky.
I'll be making my own additions to master branch, while stocklike branch will contain only fixes and kernel updates.
If somebody would like to test them, you can get the boot image from releases tab on github. Stock kernel hasn't been tested, mind you, always keep a backup!
Also depending on how much time I have, I might get started on bringing OmniROM to our device (I'm really missing it). I'm just a college student though, so it might never see the light of day, any help is much appreciated.

Avsky0 said:
Hello everyone, I've recently been working on updating the Honor 5c kernel to 3.10.105 and so far it seems to be working fine on my P9lite, LineageOS 14.1. It's based purely on stock, with one or two commits borrowed from Meticulus' kernel repo, so it compiles without errors.
Since this is a new account, I can't link my repo directly, you can find it on my github profile, Avsky.
I'll be making my own additions to master branch, while stocklike branch will contain only fixes and kernel updates.
If somebody would like to test them, you can get the boot image from releases tab on github. Stock kernel hasn't been tested, mind you, always keep a backup!
Also depending on how much time I have, I might get started on bringing OmniROM to our device (I'm really missing it). I'm just a college student though, so it might never see the light of day, any help is much appreciated.
Click to expand...
Click to collapse
Hello, I tried your kernel on AOSPA MM but I couldn't get the proper unpacked zImage. I got only 9.7 MB gzip which contains the 22 MB Image but I couldn't extract it.
Could you provide the zImage?

dady000 said:
Hello, I tried your kernel on AOSPA MM but I couldn't get the proper unpacked zImage. I got only 9.7 MB gzip which contains the 22 MB Image but I couldn't extract it.
Could you provide the zImage?
Click to expand...
Click to collapse
Strange, I can extract it without problem using abootimg. Anyway, zImage now included on releases page.

Avsky0 said:
Strange, I can extract it without problem using abootimg. Anyway, zImage now included on releases page.
Click to expand...
Click to collapse
That zImage looks like the same I got from unpack. For some reason it won't boot when I repack it with my ramdisk.

dady000 said:
That zImage looks like the same I got from unpack. For some reason it won't boot when I repack it with my ramdisk.
Click to expand...
Click to collapse
I repacked and uploaded my image with ramdisk from your latest AOSPA, could you try it? Sizes varied a bit, I've used my abootimg config with SELinux changed to permissive, as that is the case in your image.
EDIT: I'm uploading extracted zImage as well.

Avsky0 said:
I repacked and uploaded my image with ramdisk from your latest AOSPA, could you try it? Sizes varied a bit, I've used my abootimg config with SELinux changed to permissive, as that is the case in your image.
EDIT: I'm uploading extracted zImage as well.
Click to expand...
Click to collapse
Yeah of course it works :silly:. Looks like my boot-packing skills are pretty low. Good job :fingers-crossed:

dady000 said:
Yeah of course it works :silly:. Looks like my boot-packing skills are pretty low. Good job :fingers-crossed:
Click to expand...
Click to collapse
Glad to hear it! Your images seem to be using uncompressed zImages, while in stock ROMs they're gzipped, seems like unintentional change somewhere in your build process.

Avsky0 said:
Glad to hear it! Your images seem to be using uncompressed zImages, while in stock ROMs they're gzipped, seems like unintentional change somewhere in your build process.
Click to expand...
Click to collapse
Yeah you're right. I just checked it and I am copying Image instead of Image.gz. Seems like it's only a 'cosmetic' issue because it runs anyways.

Great news guys, my sources now compile with latest Linaro toolchain. The kernel actually barely needed any fixes, but I'm not releasing anything prebuilt yet, since I have no idea what impact on stability my hacks might have.
Screenshot

ndroid1562 said:
Well, developers do not grow on trees. I guess there are not enough devs here who have the P9 Lite device.
However I like the intention of the thread author. For that reason please try to discuss in a human way.
In the end: I am vers interested in learning how to build custom roms but I can't find a way how to learn it. Does anyone have some good advice?
Click to expand...
Click to collapse
Perhaps reading through GitHub commits, checking the code and see whether or not you're really interested. If you're using a Linux distribution which I strongly advise, learn bash scripts first - it's easy and self explanatory and from there you will get basics of directories and calling up files.
Goodluck
Sent from my HUAWEI VNS-L31 using Tapatalk

[CLOSED][Discontinued][UPDATED][ROM][UNOFFICIAL][MIUI][4.4.4] MIUI 7 for espresso3g devices

Discontinued.
Awaiting for thread deletion.

Thanks...Nice work after your miui 5 ROM

Help please..
Need someone who can risk his device by testing this ROM......

Happy holi.....
Happy holi my friends...
May this holi bring lots of Colors in your life!! and in mine too.

Kunal Gautam said:
Need someone who can risk his device by testing this ROM......
Click to expand...
Click to collapse
I tried to install but it gives error 7 i think update.script should be rechecked.

Deep_dhimaan said:
I tried to install but it gives error 7 i think update.script should be rechecked.
Click to expand...
Click to collapse
Thank you very much, i've understood whats the problem( as a pm by ashkineeeeee).
New update coming soon. Stay tuned.

Hey bros...
so there were some problem with permissions, it seems that it is fixed now..
Flash the ROM and review here....
----------------------edit 1---------------------
dont flash the rom now!!!
Some files are missing in boot.img
how stupid i am!!
------------------------edit 2-----------------------
Flash it now!

Last build not installed,error 7.

mels01 said:
Last build not installed,error 7.
Click to expand...
Click to collapse
Logs,screenshots?
Try installing from internal storage... Or update your recovery to the latest one by android andi...
Thanks!

Hey, I would like to help out, can I have the link to the ROM?

theportal2 said:
Hey, I would like to help out, can I have the link to the ROM?
Click to expand...
Click to collapse
I agree this message is a bit long but it is worth reading.
- Thanks, but sorry. Even if I give you the links and even if spend your precious time you would only be able to fix the error 7.
- Actually I've already fixed that(or know what's the issue atleast). There are files that are missing from the directories that are listed in the updater script. They cannot be deleted as the original base ROM I compiled was from UA(unlegacy android) that are based on the newer sources.
- Some files that are required for MIUI are also missing.
- Boot.img is incomplete. Which will result in bootloop even if I upload the error 7 fixed ROM.
- I am giving my board exams that are one of the biggest exams in India. And I cannot afford to score less in these.
- All I need is a older base ROM ,CyanogenMod 11 made around may of 2016. And also it must support init.d because the port ROM requires that.
- I've taken permissions from the maker of the port ROM. He has allowed me to proceed.
- All I need is permission from Android-Andi, as only he has older CM ROMs.
- I cannot compile because older sources are not available or maybe I am not known to them
Hope you understand. Thank you.
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam

Links

Kunal Gautam said:
I agree this message is a bit long but it is worth reading.
- Thanks, but sorry. Even if I give you the links and even if spend your precious time you would only be able to fix the error 7.
- Actually I've already fixed that(or know what's the issue atleast). There are files that are missing from the directories that are listed in the updater script. They cannot be deleted as the original base ROM I compiled was from UA(unlegacy android) that are based on the newer sources.
- Some files that are required for MIUI are also missing.
- Boot.img is incomplete. Which will result in bootloop even if I upload the error 7 fixed ROM.
- I am giving my board exams that are one of the biggest exams in India. And I cannot afford to score less in these.
- All I need is a older base ROM ,CyanogenMod 11 made around may of 2016. And also it must support init.d because the port ROM requires that.
- I've taken permissions from the maker of the port ROM. He has allowed me to proceed.
- All I need is permission from Android-Andi, as only he has older CM ROMs.
- I cannot compile because older sources are not available or maybe I am not known to them
Hope you understand. Thank you.
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Click to expand...
Click to collapse
Have you seen this CM 11? https://forum.xda-developers.com/galaxy-tab-2/7-inch-development/rom-cm-11-0-galaxy-tab-2-t3737392
Just made last month by @Deltadroid

Links are removed because *the ROM is not complete yet*.
Thanks, but I need to confirm a few things before I could use a ROM(includes init.d support and a bunch of other things). Also, it is very important that deltadroid provide me permission to use his ROM.
Thank you!
Regards,
KG
-----_edit_--------
I just saw deltadroid's thread, the title clearly says that the ROM is for p3110. I want to make a unified one. I need a ROM made with unified device tree.
If I do port, it will only work on p3110 and maybe on every 7" device. I don't want do this.
Sorry, but yeah thanks!
Just wait till 3 april 2018. Most probably I will upload.
Edit 2
Or I must say it an update. 75 percent of the work is done. Somehow I managed to get a base ROM(only I know how). Only build.prop editing and Updater script editing work left(these are the most difficult BTW).
Update coming soon. Stay tuned.

I've updated the links. I've uploaded the new ROM. I've done with porting(i guess). I've used a lot of time.
Flash and review!

Kunal Gautam said:
I've updated the links. I've uploaded the new ROM. I've done with porting(i guess). I've used a lot of time.
Flash and review!
Click to expand...
Click to collapse
No wonder the ROM doesn't work.... Security patch is in a wrong format.
"ro.build.version.security_patch=2080-17-March"
It should be, "ro.build.version.security_patch=2018-03-01"
or,
"ro.build.version.security_patch=2018-03-05"
And this, hardly doubt this will work, but idk.
"ro.build.date.utc=999999999999"
Mistakes....................
EDIT**** Build id should be the app id: example lets say the id is 678, on build.prop, it would say 678.
you have, "ro.build.id=KUNAL"

secretwolf98 said:
No wonder the ROM doesn't work.... Security patch is in a wrong format.
"ro.build.version.security_patch=2080-17-March"
It should be, "ro.build.version.security_patch=2018-03-01"
or,
"ro.build.version.security_patch=2018-03-05"
And this, hardly doubt this will work, but idk.
"ro.build.date.utc=999999999999"
Mistakes....................
EDIT**** Build id should be the app id: example lets say the id is 678, on build.prop, it would say 678.
you have, "ro.build.id=KUNAL"
Click to expand...
Click to collapse
You, sir, definitely have a lot to offer. I am afraid that this is not the actual problem. By now, I surely understand the importance of logs. Would be very helpful if someone could arrange me them.
And about your post it seemed really rude, raw, insulting and manipulating to me. But however, helpful. It makes it really hard to continue developing for a 6 years old Tab, with hardware that has nothing to offer in 2018. At least, I am trying.
Since, this was an Alpha build(because I moved sources) these problems are sure to arise. I did the same(build.prop things) with my kinda successful ROM MIUI 5(see it in the 7" forums).
I guess you haven't tasted port ROMs yet. They are hard to build. Alike your compiling ones, you have source, type some commands, turn your computer on for about 5 hours, when done upload it.
I am sure you must have did trail and error (in chemistry and math) porting ROMs is just the same. I am sure, that as a developer, you must know what logs actually mean.
But whatever, thank you for you review(insult I guess).

Kunal Gautam said:
You, sir, definitely have a lot to offer. I am afraid that this is not the actual problem. By now, I surely understand the importance of logs. Would be very helpful if someone could arrange me them.
And about your post it seemed really rude, raw, insulting and manipulating to me. But however, helpful. It makes it really hard to continue developing for a 6 years old Tab, with hardware that has nothing to offer in 2018. At least, I am trying.
Since, this was an Alpha build(because I moved sources) these problems are sure to arise. I did the same(build.prop things) with my kinda successful ROM MIUI 5(see it in the 7" forums).
I guess you haven't tasted port ROMs yet. They are hard to build. Alike your compiling ones, you have source, type some commands, turn your computer on for about 5 hours, when done upload it.
I am sure you must have did trail and error (in chemistry and math) porting ROMs is just the same. I am sure, that as a developer, you must know what logs actually mean.
But whatever, thank you for you review(insult I guess).
Click to expand...
Click to collapse
FYI, I port ROMs. It was pointers what to fix, if you wanted to get this ROM better, than it is already.

Kunal Gautam said:
(...)
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Click to expand...
Click to collapse
Sorry, I won't give permissions after different people used my ROMs as base in the past without permissions. Hope there is a learning affect....
Since i love OpenSource: Sources are available on every official GitHub (slim, Omni, Lineage, UA) and up to date (note: I wouldn't have to do this, I could keep all device trees private but I am updating them for everyone - always). You'll have to compile your own base ROM to use for such port ROMs (I am not a fan of).

Android-Andi said:
Sorry, I won't give permissions after different people used my ROMs as base in the past without permissions. Hope there is a learning affect....
Since i love OpenSource: Sources are available on every official GitHub (slim, Omni, Lineage, UA) and up to date (note: I wouldn't have to do this, I could keep all device trees private but I am updating them for everyone - always). You'll have to compile your own base ROM to use for such port ROMs (I am not a fan of).
Click to expand...
Click to collapse
Thank you. For at least replying. You works will always be appreciated. Now, I am gonna close this thread. Thanks again!