Hey Guys,
So I finally decided to learn what all this compiling and building from source is about.. So far I really learned to appreciate the developers on this site.. I started out trying to build AOSP and cherry pick commits, but after the build kept failing now my goal is just straight up AOSP for now..
I followed all different guides to get to the point of building it - it boots up without issue however I have no cell signal - baseband version is unknown.
I am at a lose to what to do. I do have the Google Nexus Binaries, and in the device/lge/mako/full_mako.mk I changed PRODUCT_RESTRICT_VENDOR_FILES := true to false.
I did make clobber to clean out any failed build, and rebuilt. I also can't get a kernel to build but thats a different beast so for now I am just using the stock boot.img.
Any help would be greatly appreciated..
**Edit** Only thing that may be an issue I think I used the preview binaries for nexus 4 - which I guess might be for Android L? Going to try to download the ones for 4.4 and see if that changes anything.
**Edit 2** After changing from the preview binaries to the regular 4.4.4 ones from google, I did make clobber and rebuilt android.. And I have full cell signal
Related
I still use my Nexus 4 happily and recently started modding the kernel a bit.
This led me to the question in the first hand, because it is possible to upgrade minor versions (3.4.0 -> 3.4.105)
The thing is, N4 uses google_msm 3.4 sources
shamu is pretty new, uses google_msm too but 3.10
I've tried by bluntly downloading shamu's kernel source, placing mako_defconfig in arch/arm/configs and updating the defconfig with make menuconfig.
As expected didn't work out, but i'm just a little modder cherry-picking stuff i'd like to have, so in reality i have no clue how to archieve that, or if it is even possible with some modifications.
I've also tried with the standard 3.18 Linux kernel too before, but got the same expected result.
Did someone actually tried this and got a bit further, is this something simply not posiible or too much work to get it going?
I am having trouble finding decent instructions for getting the sources for a standard build for Motorola devices, specifically for athene.
I have built for Freescale products before and it usually involves some combination of repo init and patches, but that doesn't seem to be the case for Motorola.
I know the kernel and other sources are available on Github (https://github.com/MotorolaMobilityLL), but I don't see a manifest repository there. Nor can I find a device repo.
The closest thing to instructions I found was this readme (https://github.com/MotorolaMobilityLLC/readme/blob/master/MMI-MPJ24.139-23.4.txt) (xda wont let me post links, I'm too new a user here).
I am starting to suspect that Motorola is being as lazy as possible and only fulfilling the bare minimum of open source obligations, and thus doesn't provide a device repo, or manifest repo, etc.
Is that the case? I am new to running builds for standard phone manufacturers - are ROM developers around here forced to do legwork filling in what the manufacturers refuse to publish?
Or am I just missing the rest of the instructions from somewhere?
I have the same issue, did you ever manage to successfully complete a build? Thanks.
TheGreatCabbage said:
I have the same issue, did you ever manage to successfully complete a build? Thanks.
Click to expand...
Click to collapse
Nope, my impression of the situation remains the same, though I have not re-investigated. I would like if someone more knowledgeable confirmed though.
It is a shame, as I would really like a "known good" base to work off of and put in root support and remove unnecessary softwares in a legitimate way.
You *can* build LineageOS for athene: (https://wiki.lineageos.org/devices/athene/build)
I ran LineageOS for several months, but eventually switched back to stock. Has some strange issues in regards to texting (seems to only work when making a call).
Thanks for your reply. I've just managed to build Lineage OS for my device, and it seems to work ok.
I was previously using Resurrection Remix OS (which I didn't build, just downloaded a zip) and it worked very well, so if I have any issues with Lineage then I'll try to restore my TWRP backup of RR.
I wish I could use the AOSP codebase directly, though...
This is a question for all the devs here.
Ive been a long time member, mostly lurking. I use to compile windows mobile roms for my own use.
Im interested in trying to build my own custom stock(ish) rom and kernel.
I know it wont be easy and will most likely fail multiple times or even brick my phone completely.
I have the sm-g935w8 version and currently on 8.0 stock root.
My goal would be a custom rom possibly tw with stuff i manully remove and configure i would also make a kernel ..possibly..ive compiled one a long time ago for a linux build. But as for kernel id just like to play around see what is available
Im not looking for the step by step but some information on where to begin and what software ill need.
Also has samsung released latest source code?
Thanks
hello all. you may remember me from building kernels (beast-kernel) for this device well im now trying to build for the device again as i still own the device and would really like to get rid of touchwiz.
i downloaded the cm source but now have a problem . the local-manifest is no longer on the androidfile host. i need the manifest to further proceed in building it
beany23 said:
hello all. you may remember me from building kernels (beast-kernel) for this device well im now trying to build for the device again as i still own the device and would really like to get rid of touchwiz.
i downloaded the cm source but now have a problem . the local-manifest is no longer on the androidfile host. i need the manifest to further proceed in building it
Click to expand...
Click to collapse
You have 2 choices: or you find a source started yet, but with a lot of work to do (like, search in github for degaswifi) or you start from scratch, and to help yourself a little more, look for some other marvell pxa device/kernel sources.
Hello XDA community,
After months of struggling im in desperate need of your help.
What is my goal?
To compile our own kernel so we can mess around with Qualcomm's trustzone.
Where did it all start?
It all started a few months ago back in November 2021 when me and a friend read a blog about a Trustzone exploit in Qualcomm's MSM8974 processor. (link to the blog)
Big noobs as we where, we where getting hyped an bought ourselves a Samsung Galaxy Note 3 with a MSM8974 processor. After messing around with the device we learned more and more about android and the workings of the software. We first started to root the phone and play around with ADB. After that we found that we can use Frida aswell. But all of it didn't lead to the result we wanted. So we started to dig deeper in to the write-up of the blog. We soon came to the conclusion that we where not even close to doing the right thing.
What happend next?
After we came to the conclusion that ADB and Frida is not enough we understood we need to build our own kernel for this exploit to work. So we do what we always do and that was start googling and watch YouTube. By doing that we found 2 different kernels:
Lineage 18.1
SM-N9005_EUR_LL_Opensource
We where over the moon because inside the folders we found the the files that need to be replaced for the exploit to work. So we replaced the files and try to compile the kernel by using this YouTube tutorial. Everything seemed to go well, we made the
Code:
make msm8974_sec_defconfig
and we run
Code:
make menuconfig
so far so good. the last and final step should be to run
Code:
make
to compile the kernel. And that is where it went wrong an ran in to a error.
Then what?
Then we started to compare the original files with the modified files and we found out that it wasn't just a few modifications in the code but the code was different. So we did what we always do, go back to the source. So back at the blog we thought maybe its because they modified a Nexus 5 at android 4.4.4.
Now what?
Now im trying to find the source of a android 4.4.4 kernel of msm8974 so we can compare those files to the modified files. So if anyone has useful info or knows where to find a kernel for android 4.4.4 for a Samsung Galaxy Note 3 (SM-N9005).
TLDR;
Im looking for a source of android 4.4.4. for a Samsung Galaxy Note 3 (SM-N9005) (hlte)
Well, unfortunately today almost no one uses android 4.4.4. even that have the exact same device, I am using Android 11 on my phone.
I recommend not wasting your time on a kernel for Android 4.4.4. And if you really want to make a kernel for this device I need one for Android 10 and above.
Also I think making a kernel for AOSPs like LineageOS or HavocOS or crDroid ETC is much easier.
A.M.2.K.M said:
Well, unfortunately today almost no one uses android 4.4.4. even that have the exact same device, I am using Android 11 on my phone.
I recommend not wasting your time on a kernel for Android 4.4.4. And if you really want to make a kernel for this device I need one for Android 10 and above.
Also I think making a kernel for AOSPs like LineageOS or HavocOS or crDroid ETC is much easier.
Click to expand...
Click to collapse
Thanks for your response I will look in to it. not sure if it will be easier because the files that needed to be changed are:
arch/arm/mach-msm/scm.c
arch/arm/mach-msm/include/mach/scm.h
drivers/misc/qseecom.c
SwAgLaNdeR said:
Thanks for your response I will look in to it. not sure if it will be easier because the files that needed to be changed are:
arch/arm/mach-msm/scm.c
arch/arm/mach-msm/include/mach/scm.h
drivers/misc/qseecom.c
Click to expand...
Click to collapse
Well, I don't know much about kernels.
I said it's easier because I thought it's a pure and raw operating system. But now according to your post it turns out it's not easier.
Plus almost no developers left for this now very old model .