Database Users

Bringup OMNI from CM tree.

Hey,
I was building OMNI from CM tree just patched couple of GPS hal related errors but can't seems to pass sepolicy errors they keep coming up.
First this comes up!
http://paste.ubuntu.com/7662158/
and then when i deleted that line other sepolicy errors comes up.
http://paste.ubuntu.com/7664916/
http://paste.ubuntu.com/766767
They didn't seems to stop one by one, and they make me to delete my whole device.te
Any help will be appreciated.

icoolguy1995 said:
Hey,
I was building OMNI from CM tree just patched couple of GPS hal related errors but can't seems to pass sepolicy errors they keep coming up.
First this comes up!
http://paste.ubuntu.com/7662158/
and then when i deleted that line other sepolicy errors comes up.
http://paste.ubuntu.com/7664916/
http://paste.ubuntu.com/766767
They didn't seems to stop one by one, and they make me to delete my whole device.te
Any help will be appreciated.
Click to expand...
Click to collapse
Just disable sepolicy in BoardConfig.mk. I suppose/believe you can boot a rom with selinux disabled?

I would suggest starting with selinux permissive and sepolicy removed, then work on adding it back in once your device is solid.
Honestly a lot of maintainers have stuck with permissive for the 4.4 cycle as we've had way too many other things to work on in terms of core device support and such. The 4.4 cycle has been, in general, a huge learning experience (and teambuilding experience) for Omni. There are a lot of things we wanted to do but haven't gotten around to because we had so many unexpected things to take care of.

Sony copyleft sources missing code...

@jerpelea
While in the course of attempting to develop a unified kernel for both normal boot and TWRP recovery boot for Xperia Z3+ for use with extract_elf_ramdisk so that we don't always need to use fastboot to load the recovery image, it's come to my attention that the 28.0.A.8.251 open source downloads are missing code for a number of drivers that are compiled and loaded as kernel modules in the official firmware releases. Notably, the lack of drivers/video/msm/mdss/mhl_sii8620_8061_drv breaks a lot of things if the kernel module isn't loaded (including usb connectivity and, as a result, adb)
It would be nice if Sony could update the source downloads so that they're complete. Some other modules appear to need source including core_ctl.ko, ecryptfs.ko, kscl.ko and texfat.ko as well
Thanks
/dl

dl12345 said:
@jerpelea
While in the course of attempting to develop a unified kernel for both normal boot and TWRP recovery boot for Xperia Z3+ for use with extract_elf_ramdisk so that we don't always need to use fastboot to load the recovery image, it's come to my attention that the 28.0.A.8.251 open source downloads are missing code for a number of drivers that are compiled and loaded as kernel modules in the official firmware releases. Notably, the lack of drivers/video/msm/mdss/mhl_sii8620_8061_drv breaks a lot of things if the kernel module isn't loaded (including usb connectivity and, as a result, adb)
It would be nice if Sony could update the source downloads so that they're complete. Some other modules appear to need source including core_ctl.ko, ecryptfs.ko, kscl.ko and texfat.ko as well
Thanks
/dl
Click to expand...
Click to collapse
You may want to post to the sony developer forums.
I am unsure how often they check xda.

ChrisJ951 said:
You may want to post to the sony developer forums.
I am unsure how often they check xda.
Click to expand...
Click to collapse
im pretty sure they checking very often but more interested with any exploit found to root their LB devices by xda devs so they can cover the hole immediately

Info
dl12345 said:
@jerpelea
While in the course of attempting to develop a unified kernel for both normal boot and TWRP recovery boot for Xperia Z3+ for use with extract_elf_ramdisk so that we don't always need to use fastboot to load the recovery image, it's come to my attention that the 28.0.A.8.251 open source downloads are missing code for a number of drivers that are compiled and loaded as kernel modules in the official firmware releases. Notably, the lack of drivers/video/msm/mdss/mhl_sii8620_8061_drv breaks a lot of things if the kernel module isn't loaded (including usb connectivity and, as a result, adb)
It would be nice if Sony could update the source downloads so that they're complete. Some other modules appear to need source including core_ctl.ko, ecryptfs.ko, kscl.ko and texfat.ko as well
Thanks
/dl
Click to expand...
Click to collapse
Sony has lots of works to do...
& most important part is Updating Sony SDK & another Sony APIs
there is lots of restriction these days with developing for Sony SDK & Support for Android 5.+
from App GUI customization to New Permission Model
:good:

Geeks Empire said:
Sony has lots of works to do...
& most important part is Updating Sony SDK & another Sony APIs
there is lots of restriction these days with developing for Sony SDK & Support for Android 5.+
from App GUI customization to New Permission Model
:good:
Click to expand...
Click to collapse
So Sony uploads incomplete source because they are busy with other things?
It's not justifiable as kernel source and SDK&API are different thing.

dl12345 said:
@jerpelea
While in the course of attempting to develop a unified kernel for both normal boot and TWRP recovery boot for Xperia Z3+ for use with extract_elf_ramdisk so that we don't always need to use fastboot to load the recovery image, it's come to my attention that the 28.0.A.8.251 open source downloads are missing code for a number of drivers that are compiled and loaded as kernel modules in the official firmware releases. Notably, the lack of drivers/video/msm/mdss/mhl_sii8620_8061_drv breaks a lot of things if the kernel module isn't loaded (including usb connectivity and, as a result, adb)
It would be nice if Sony could update the source downloads so that they're complete. Some other modules appear to need source including core_ctl.ko, ecryptfs.ko, kscl.ko and texfat.ko as well
Thanks
/dl
Click to expand...
Click to collapse
yes, that's pretty annoying,
if you're diverging too much from Sony's provided "stock" kernel, the modules won't work anymore
wasn't aware that mhl_sii8620_8061_drv plays such an important role
edit:
actually if it's the same situation like on the z5 several more modules are missing:
gpio (all or most of the sensors aren't working without it), mcDrvModule, mcKernelApi (mobicore, something like TPM), mpq-adapter, mpq-dmx-hw-plugin
so most of the "higher" functionality of the device won't work ...

[FIX] Bypass PIE Security

I'm not sure if anyone will find this of use, but I did so I figured I'd post it for everyone to use:
I recently ran into issues running a few binaries on my V10. After doing a bit of research I found that non-PIE (position independent executables) will not run on newer devices (5.0+). Given I needed to run non-PIE binary, I looked further into a fix. This lead me to a thread posted here on XDA about bypassing the PIE check on Android L for the Nexus 5. Unfortunately the linker included in this fix is not usable by our device. Thankfully the linked thread goes into some detail about how to patch /system/bin/linker to allow non-PIE binaries. After reading into the provided information, I was able to patch our own linker and get my non-PIE binary to run just fine.
I've thrown together a flashable ZIP that simply replaces /system/bin/linker with a patched version that will allow non-PIE binaries. :good:
As a note:
Code:
[I]
[B][COLOR="Red"]
I HAVE ONLY TESTED THIS ON MY OWN LG V10 H901 ON MARSHMALLOW (6.0).
I CANNOT VOUCH FOR ANY OTHER MODEL, VERISION, OR DEVICE. AS ALWAYS
BE SURE TO PERFORM A BACKUP BEFORE FLASHING![/COLOR][/B]
I am, by no means, a developer. I simply dabble in Android for fun. I am not
responsible for any issue(s) caused by using this patch and you are doing
so at your own risk.
[/I]

So what this does is allow older non 6.0+ compatible apps to work?

Swizzle82 said:
So what this does is allow older non 6.0+ compatible apps to work?
Click to expand...
Click to collapse
It's helpful for any app with binaries that don't support position independent execution. In my case it allowed me to use my debugging server (which wouldn't run otherwise).

this works on the latest cm build for the htc one m8
but im a little confused as to which byte was modified can you please explain how you found which byte to replace i am using hex editor on my phone and cannot find the hex allocation mentioned in the forum
well i thought it worked until i went to restart my phone and it woudnt boot... thankfully tho i didnt delete the old linker file i just renamed it to linker.old so i was able to boot into my recovery and use its file manager to fix the issue
for now i guess i will create a script to automatically switch the file when i shutdown my phone and switch it back when it starts

Hi Guys!
I would be happy if someone could post a tutorial on how to Bypass PIE on Android 6.0.1
I have some experience in disassembling ELF files, but do not know where to look for disabling PIE in linker file. I would like to learn how to do it on my own, so i am not asking someone to patch my linker file.
Using G928F with Android 6.0.1
Thank you in advance!

Please help me to patch my linker

Works on Samsung J710MM (Marshmallow 6.0.1) perfectly. Thanx a lot!!!

Could anyone help me bypass PIE On marshmallow Touchwiz 6.0.1 would greatly appreciate your help?

Deleted

I need a little bit of help porting crDroid 6 to the sm-t350

I need a little bit of help portingh crDroid 6 to the sm-t350. Nubianprince started then got pulled away by work. I have initalized the crdroid repo, but i when i run repo sync i think it only downloaded like, 300 mb. i do have an android pie enviroment, does repo link resources? i dont know what is going on there. I will upload my roomservice.xml. I had to remove a couple lines from the original and manually clone them because it keeped giving me an error. the original is here https://github.com/Nubianprince/local_manifests/blob/master/crdroid-ten.xml .
Currently i am using this device tree: https://github.com/Nubianprince/android_vendor_samsung_gt58wifi most custom roms i see are using this: https://github.com/Valera1978/android_device_samsung_gtaxlwifi . I have not seen any non sm-5xx devices using it though, so i hesitate to switch. i worked out a a couple errors of things being defined twice, and then built. but i think i am missing something as the build fails with this: FAILED: ninja: 'out/target/product/gt58wifi/root/init.usb.configfs.rc', needed by 'out/target/product/gt58wifi/ramdisk-recovery.cpio', missing and no known rule to make it
Is there a "quick fix" to provide this file? I am not actually sure what i am missing, or what creates it.
Any help would be appreciated.

This file "init.usb.configfs.rc" is missing from your device tree, somewhere in one of your files you have the path pointing to "init.usb.configfs.rc" which does not exist. Let me know if that makes sense.

nubianprince said:
This file "init.usb.configfs.rc" is missing from your device tree, somewhere in one of your files you have the path pointing to "init.usb.configfs.rc" which does not exist. Let me know if that makes sense.
Click to expand...
Click to collapse
Yes, it does make sense. I just don't know enough about the android environment to know where the file, or what is pointing to it, would / should be.

Okay. I believe there is a missing, or many many missing makefiles. I found the file and manually copied it to out, and then the build fails with another missing file. Rinse and repeat, there are a ton of files not being put where they should be. Now what to do with that information, i am not sure ??. I tried including a couple of the make files from android 9, but they didn't make any difference.
oh yeah, and if i do lunch instead of brunch it fails with a different file missing: FAILED: ninja: 'out/target/product/gt58wifi/system/addon.d/50-lineage.sh', needed by 'out/target/product/gt58wifi/verified_assembled_framework_manifest.xml', missing and no known rule to make it

it makes no sense adding files to the "out" folder, fix the issues in your "device" folder check your device.mk file

Wow. That was really awful. I don't even know what i was thinking there. What i was trying to say, is that i was manual copying the files to see if it was just one or two not being copied. I have been comparing the Pie and Q makefiles to try to determine what file was supposed to be copying it to out, but i cant find it in Pie, all i know for now is that it is being copied in Pie but not Q. For now I'm gonna' keep looking for the correct file.

lividhen99 said:
Wow. That was really awful. I don't even know what i was thinking there. What i was trying to say, is that i was manual copying the files to see if it was just one or two not being copied. I have been comparing the Pie and Q makefiles to try to determine what file was supposed to be copying it to out, but i cant find it in Pie, all i know for now is that it is being copied in Pie but not Q. For now I'm gonna' keep looking for the correct file.
Click to expand...
Click to collapse
What device tree are you using, do you have it on Github?

nubianprince said:
What device tree are you using, do you have it on Github?
Click to expand...
Click to collapse
I am just using the device trees (ten branch) on your GitHub. I haven't made any changes that have gotten me anywhere so i haven't committed my local changes to my GitHub.

That crdroid ten branch still need a lot of work, the last build I did when I was working on it was not getting past the logo

nubianprince said:
That crdroid ten branch still need a lot of work, the last build I did when I was working on it was not getting past the logo
Click to expand...
Click to collapse
I have been away for a while and haven't followed along, but the last week I spent compiling ROMs. I also tried compiling Android 10 using "stock" lineageos gt58wifi and I got stuck at the logo as well. I also tried another device from the msm8916 repository and got stuck at the logo.
The "stock" gt58wifi build, as we all know, has problems with audio, bluetooth, smart cover, etc, etc in all versions 14.1, 15.0, 16.0 and won't even boot with 17.1.
When I first compiled it, it would fail due an error with a config.xml file. I submitted a patch, like others, but haven't seen anything yet.
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/pulls

nubianprince said:
That crdroid ten branch still need a lot of work, the last build I did when I was working on it was not getting past the logo
Click to expand...
Click to collapse
I'm working on SM-T560NU 17.1. It too was stuck at the boot logo. I built an eng build and found it was the hardware vibrator that was getting stuck in a loop. If you remove the vibrator hal from
/device/samsung/msm8916-common/manifest.xml
that should work on the SM-T350 because both platforms share the same msm8916 code?
I did build SM-T350 with 17.1 and was stuck at boot logo and gave up. However, I have not rebuilt it knowing this new information. I will try again with the above change in a few days?

So, as retiredtab has said, he got android 10 booting. But it has all the issues android 9 did: no camera, sound, Bluetooth, or Hal sensor (sort of, it can turn the device on but not off). The system ui is also a little funny on crdroid, not sure about lineage. I don't know how to fix these issues, or where the roots of the problems may lay. Do you have any suggestions for learning more about the android source code? I feel like the aosp docs are good, but you kind of have to know what you're looking for.

I think part of the problem with the SM-T350 is that there has never been a fully working build since day 1. Lineageos 14 had problems to begin with and they were never fixed and got carried over to 15, 16 and now 17. If stock Lineageos 16 was fully working, then getting it to work on 17 would be less of a challenge.
The most likely problem to no audio, camera, bluetooth etc is the Samsung proprietary blobs are not in the correct directories or the configuration blob files are pointing to the wrong directory.
When I face this problem, I find it helpful to look at a working roomservice.xml file and do comparisons.
If there is no working roomservice.xml like "stock" lineageos 14, 15, and 16 for the SM-T350, then I look at similar models. For example, the T550 is the bigger brother and it helps to look through it's roomservice.xml file for hints.
Remember that a compiler mainly checks for syntax errors, not semantic. If you make a typo, a compiler will flag that as an error, but if you write correct syntax, but put a file or files in directory ABC instead of XYZ, the compiler won't say anything.
Another thing that might help is doing a logcat of a working build and comparing it to a non working build. There might be a very obvious error message like "can't find audio.hw.msm8916 in directory /device/samsung/msm8916" or something like that.
Learning how to use tools like meld and diff help tremendously in finding file and directory differences in case you put the blobs in the wrong place. See
https://www.tecmint.com/compare-find-difference-between-two-directories-in-linux/
I used meld when troubleshooting the stuck at boot logo.
If you are a visual learner, I found the following youtube channel helping in learning the overall process of building ROMs.
https://www.youtube.com/c/AlaskaLinuxUserAKLU/videos

I think we have lineage 16 fully working. I think the part I'm having trouble with here is the difference between where the files are read from in Android Q vs P.
If I understood what you said incorrectly, please say so.

HELP!!! please!! compile bootable systemd msm-3.18 arm kernel

hello
For the past few weeks i have been working on porting sailfish os to the LG Aristo 2. Its been a pain too as i had no idea where to start. Any ports to lineage or otherwise never got past boot and after a some searching i could not find a repo.
Any way i have managed to accomplish building a repo on github where curious folks could look me up by my handle. I originally started the project to boot native ubuntu on an sd like the v10 and v20.
But now i have backed myself into a corner. i have been compiling the systemD kernel using msm-3.18 source thats been upstreamed for two weeks now and i still cant get a boot.img that wont boot straight to fastboot.
can some one please help me accomplish this task.
then maybe we can move on to the build errors

Duhjoker said:
hello
For the past few weeks i have been working on porting sailfish os to the LG Aristo 2. Its been a pain too as i had no idea where to start. Any ports to lineage or otherwise never got past boot and after a some searching i could not find a repo.
Any way i have managed to accomplish building a repo on github where curious folks could look me up by my handle. I originally started the project to boot native ubuntu on an sd like the v10 and v20.
But now i have backed myself into a corner. i have been compiling the systemD kernel using msm-3.18 source thats been upstreamed for two weeks now and i still cant get a boot.img that wont boot straight to fastboot.
can some one please help me accomplish this task.
then maybe we can move on to the build errors
Click to expand...
Click to collapse
You should go to IRC #sailfishos-porters, there you will find help from Jolla developers and from community

well i guess theres no help any where. the folks at telegram completely ignore me and are rude as f and if you say any thing about it they say you ate spamming for and claim you are the rude one. ive been ganged up on several times. irq doesnt seem to have enough people to help and i feel all hope is lost at this point.
on the other hand i have built a the whole rom completely and several times over but i cant get it installed and dont know how to see if the kernel works

ok im gonna keep trying to get help from here. I have gotten more help and made it farther in my abilities because of the help and info from this place than any other. Thank you
So this is where i am at. i have compiled Halium\Ubuntu touch several times over and worked it out with no compilation errors and including all of my sources.
But i cannot get it to ssh or telnet. I have followed all of the installation documents and i can see that its pulling the system.img and rootfs to data. i have entered my password on prompt its generated and pushed the rsa keys and every thing. but no go
i have checked the dmsg and kmsg after the attempts and no errors are reported.
so now im trying to go the route of the V20. I have an arm ubuntu 18.04 rootfs that i have unzipped and built up on the 2nd partition of my external sd. i installed every thing needed to build a kernel and any thing else i might need. i have msm-fb-refresher compiled and installed. I also have dev sys and proc mounted bound and and have made the devices using MAKEDEV. But when i try to build the kernel on my aristo 2 in the chroot i get these weird graphics characters and i have to restart my terminal to get my characters back.
in the mean time i compiled the kernel on my pc and had the modules installed to the chroot outside the android device and used update-initramfs to create an initrd.img exteacted it and made a boot.img that i put in the boot directory and installed to laf.
it will not boot stiil from laugh and goes to bootloader. but if i tell the chroot to reboot i get the error system cannot reboot with systemD as init cannot operate.

ok well still no help at any of the halium/ubuntu touch forums or telegram. But the bot said there was no kernel errors.
i have been looking at the lg v20 native ububtu mate rootfs and also the ectracted boot.img contents and i just dont know what it is thats causing it not to boot