So this is my very first attempt in any kind of android development. I have here my phone's official kernel source. I was wondering if I can build this to boot or if it's ready for building.
Also this phone is bootloader locked and there's no official or unofficial way to unlock it.
So what can I do with the source or the boot image ?
I figured a way to get root access using the source code. I am still working on it tho and need help
Related
I just setup my build environment and download source code and custom ROM source code. Unfortunately there was an issue with the custom ROM and I had to wait until they fixed it. I need to update it the code and rebuild. How do I go about it?
Thanks.
So, can anybody port either of these ROMs or both for the InFocus M330? I really want Lollipop in this device.
This device has a MediaTek MT6592 32-bit SoC.
InLife UI (The official ROM) for the device can be found over here: http://drive.google.com/file/d/0B6eY1SgN2PqcVmlFTzJfMl9VQTg/view for copying stuff.
Bump! I still want it, please
Without the kernel source and knowing if the bootloader can be unlocked there is nothing that can be done
How could I extract the kernel? And I can't unlock this device's bootloader because it won't get detected in fastboot.
NutVolt said:
How could I extract the kernel? And I can't unlock this device's bootloader because it won't get detected in fastboot.
Click to expand...
Click to collapse
You need the GPL law required source code for the kernel but if you can't unlock the bootloader that won't do you any good anyway
zelendel said:
You need the GPL law required source code for the kernel but if you can't unlock the bootloader that won't do you any good anyway
Click to expand...
Click to collapse
I really regret buying this device.
How developers get the source code to develop a custom rom?
for example, How CyanogenMod get marshmallow source code for SIII 9300 which hasn't have this Android version?
I wan't to develop my own rom for my device, but I can't find specially Marshmallow pure source code for s3.
There isn't device set source code. Just a base code. Then you have to get/make the device trees for that device.
Then it takes weeks sometimes months of bugs to fix.
For that device to be honest you will be hard pressed to get a fully working set up as there is no kernel for android m for that device. So you will have to merge the code bit by bit and add some of your own
While the bootloader of many g5 devices is not allowed to be unlocked (no official way) LG releases the source code for the kernel of those devices.
Is that even useful?
How can we even compile and use a custom kernel while we are allowed to flash one?
Sent from my sh!tty LG-H860 that is beyond crap
hello again peeps,
ive been gently banging my head around these past few days because i keep walking into knowledge pockets and nothing i can find, in the form of help or internet information, is filling in these holes. i originally planned to take my oneplus device and obtain the source code for oxygenos so i could build and customise it. this seems to have become a dead end so now i just want to build stock android via AOSP, but i dont understand what software i need to get the AOSP working on any device, so far i understand that you need 3 components; 1) Kernel 2) Vendor files (if any) 3) "Proprietary binaries".
The problems are, i have no idea how to obtain these "proprietary binaries", i have no idea where to put any 3 of them in the downloaded android source tree (after repo sync), and i dont know if thats all the information i need to atleast build and flash a stock image onto any phone. i think i have the kernel files i need on OnePlusOSS github and there is a vendor.img in the OTA update files, and a directory in my phone. if anybody could please guide me in the right direction, it'd be very cool. i just want to get started and have some fun.
0
Seppppx said:
You can't customize Oxygen Os as the source code doesn't exist for that. (It's not required for companies to publish that.)
What phone do you have? You already might have the required trees to build AOSP (or at least LineageOS)
You need
1. A Device Tree
2. The kernel (you can use the prebuilt kernel if you really want)
3. The proprietary vendor blobs located in the vendor partition.
You will probably have to download the aosp-caf source code instead of aosp for it to be more easy.
https://www.youtube.com/channel/UCnGqG_jyyXmTzdamBpKfeHA
This is a great channel about Android building and has about everything you need to know.
Click to expand...
Click to collapse
thank you for every inch of text in your reply. I have a oneplus 8. Ah right, so the vendor folder CONTAINS the proprietary binaries/blobs.
it seems safest for me to use the kernel in the manufacturers github for the first flash as i want to be careful with making changes. may i ask what "aosp-caf" is? or can i find out using the resource you provided? thank you again.
my new understanding is, you need; 1) android source (e.g android-10-r5) 2) kernel 3) proprietary blobs. this helps a lot and is a lot clearer. the last issue i have is with knowing where to put the kernel and the blobs. i think if i am not mistaken you put the blobs in a vendor folder after the build? i am unsure with the kernel. i am going to definitely check this guy out. your time means a lot to me.