Release MMI-S3SV32.45-24-3 · MotorolaMobilityLLC/kernel-mtk
vicky push for android 12
github.com
As of this week Motorola pushed kernel sources.
Let's hope for custom ROMs.
Yes
Is there any TWRP for this device as well? I have been trying to find one to at least root on the meantime, but I am unable to find one and don't know any for another device that works for it.
And BTW request admins to create a forum for the device you know it feels great...
Could any help building twrp for this device?
I'm building
Related
Hey guys! After a long time of taking a break from the Android world and focusing more on school I am finally coming back and coming back strong! But before I can start my big plans I need a device or two to develop for. I own a Galaxy Note 3 but I really do not like developing for it since we do not have an Unlocked Bootloader yet.
I am a Samsung Fanboy so I know TouchWiz inside and out! I also have plenty of experience with the stock Android OS. I currently do NOT make source builds but if you have the source code then I will be glad to!
All of my builds will be built on my Dedicated Server and uploaded on a fast 1GBPS port! I will develop for pretty much any device as long as it either has source code or is compatible with the Kitchen.
I can theme, build ROMs, and very little Kernel work. Let me know what devices you want me to dev for and what you would like to see in a ROM. I can start working very soon!
Thanks for your time!
-- Droid Premium
Can you give me your knowledge
I know Android only at moderate level but need help with some porting tips (preferably mtk device,i've seen yuweng's thread)
I want to gain more knowledge about Android and i've never built anything from source
Any help regarding the functioning of android is really appreciated
Sent from my A11 using Tapatalk
Hello!
I have ZTE V985 (Grand Era), and he has only 4.0.4
It is sad, bacause we have kernel source and HTC One X (they are similar) already have CM11
So, I want you to port 4.4 to the ZTE V985
Here is the kernel source https://disk.yandex.ru/public/?hash=BWwRVJxvd/ByYk9Ec3R6qwIuNE8rSJ2sB4LjsUucVi8%3D
Hope you will help me with this device
@Droid Premium what about the Note 10.1 2014, WIFI only model, P600? Don't know if youv'e made any roms for tablets but it would be good to have another rom for it because it's been a bit quiet so far
@Droid Premium
hello
Can you help me develop a alcatel idol cm10.1 s or higher.
I already made the recovery
the bootloader is not locked
Alcatel has sources
http://sourceforge.net/projects/alcatel/files/OT_6035R_20140507.tar.xz/download
my sources for recovery carliv
https://github.com/dams161/ot6034r
if you can help me a little
thank you
dams161 said:
@Droid Premium
hello
Can you help me develop a alcatel idol cm10.1 s or higher.
I already made the recovery
the bootloader is not locked
Alcatel has sources
http://sourceforge.net/projects/alcatel/files/OT_6035R_20140507.tar.xz/download
my sources for recovery carliv
https://github.com/dams161/ot6034r
if you can help me a little
thank you
Click to expand...
Click to collapse
I would appreciate any ROM for this device. It could have so many things...
Regards
Its been more than a month since the kernel source for MIPAD has been released.Have been closely following xda and MIUI forums ,but haven't seen any development work being posted in any of them.
Do we have development work going on for MI PAD??
Last i heard was there was some issue with vendor blob , which was preventing an android upgrade.
Has that problem been solved?also i heard that for many devices emulation or wrapping is used when vendor blobs are not available...
Please let us know for development work so that we can also be able to contribute for the betterment of our device
It's not 2 ez as u think
Artemka2008 said:
It's not 2 ez as u think
Click to expand...
Click to collapse
I understand that,I am trying to develop from my side as well.
Highwaystar_ru has done great work in implementing CM 12.1 for mipad.Its in the beta mode but usable,its has some issues such as micro lags,camera,No sounds in certain apps such as go to meetings,Skype etc.
Just wish someone works on the kernel from source as the current CM 12.1 uses stock smoke kernel
Hello guys.
This question is specially for devs or advanced users with development skills.
My question is related to the kernel source of one of my devices, Huawei Mediapad T1 10 (codename: hwt1a21l). I got the kernel source from the oficial Huawei website and uploaded it to a github repo. My device, which has a msm8916 chiset, doesn't have any development (roms, recoveries, device tree, etc) and his rom, EMUI 3.0, is based on Kit Kat 4.4.2.
I have been trying to bring development for this tablet many months ago because the stock rom is too deprecated for the hardware that has, with the msm8916 there is a huge potential to bring it a lot of development.
Well, i'm going to summarize my problems when trying to bring development for the device:
To get started development, for example a LineageOS build i needed a solid base to start with: device tree, propietary blobs and kernel source, so i got all of them. I ported the device tree from another one very similar to mine (with the same chipset), extracted the propietary blobs with the build tools from the source and got the kernel source from the Huawei website. So everything seemed to be good, but when i start the build process with my Linux machine (repo sync > source build/envsetup.sh > breakfast hwt1a21l > brunch hwt1a21l) i always receive thousands of build error by the kernel source, and i have been fixing (or at least avoid) a lot of them but it never ends, so i don't know if it's worth to keep trying to "fix" them or if i'm wasting my time.
So, what i have been trying to do: i have been trying to build a LineageOS 14.1 and TWRP recovery with my device tree This: Mustang-ssc/android_device_huawei_msm8916-common ported from this one from @dianlujitao : dianlujitao/android_device_huawei_msm8916-common and the specific kernel source for my device downloaded from the Huawei website Mustang-ssc/android_kernel_huawei_hwt1a21l. Here ends the summary.
So after a lot of hours, days and nights over the last months trying to make progress with this and not getting any help from the few devs i asked after seeing my lack of progress i decided to publicly ask for help.
The questions:
1. I have the official kernel source (Mustang-ssc/android_kernel_huawei_hwt1a21l) which i didn't have success to compile it, and then i saw the kernel source from a device almost identical to mine (same chipset, brand, ram, ...) (dianlujitao/android_kernel_huawei_msm8916). Can i use that kernel source as a base for my device after porting the specific configurations of my official kernel source (defconfig, drivers, libraries)? That one is much more updated and probably optimized than mine, but i don't know if it's possible to adapt a kernel source from other device using your kernel source.
2. This may be a dumb question: my device has Kit Kat 4.4.2. Is there any link between the kernel source and the android version the device has? I mean, i don't know if i should do something to adapt my kernel source for newer android versions (Marshmallow, Nougat) of if it's ok to just build with it without any change.
If you read it all, congratulations, you're awesome
Still waiting for a reply
Hello, us over at the Moto E4 Plus forums have been struggling to get anything past Nougat to build, let alone boot on our devices. If anybody is familiar with porting MSM8937 devices from Nougat to Oreo, please, please, please contact one of us at the Moto E4 Plus forum (me, SeanStar, bcrichster) to help us out. Thank you.
You're going to have to find kernel source code as well as vendor binaries to get it to work. You'll need to also extract the device tree. Once you have got those things, it is very likely that at least minor modifications will need to be made in order to get it to build. I struggled with this for a long time with a Sony Xperia ZL, but eventually I found a GitHub repo with some files that helped out. Look around and see if anyone is providing similar things for your device.
Here's a link to a device tree repo I found quite quickly: https://github.com/moto8937/android_device_motorola_owens.
nkomarn said:
You're going to have to find kernel source code as well as vendor binaries to get it to work. You'll need to also extract the device tree. Once you have got those things, it is very likely that at least minor modifications will need to be made in order to get it to build. I struggled with this for a long time with a Sony Xperia ZL, but eventually I found a GitHub repo with some files that helped out. Look around and see if anyone is providing similar things for your device.
Here's a link to a device tree repo I found quite quickly: https://github.com/moto8937/android_device_motorola_owens.
Click to expand...
Click to collapse
Thank you for your assistance, but we already have device trees, vendor binaries, and kernel sources for Nougat 7.1.1. We're trying to get Oreo for our device by using these trees and modifying them for Oreo, or Pie at this point.
Hello all, where would I start in making a working twrp for this phone?
Does anyone know if Motorola has released the device tree/source code for this phone so we can make the roms? LineageOS would be ideal.
Well, I have the same phone. Couldn't find ROMs for it.
thebestofall007 said:
Hello all, where would I start in making a working twrp for this phone?
Click to expand...
Click to collapse
look in this forum here, there are a couple floating around for it, I've made one, that I was able to fully flash to mine and has touch (Android 10. there's another that is 11 on here too by another poster), but as there are multiple display options out there it seems for how they were made, that is the sticking point, as not all will behave properly when booted into a recovery like mode it seems. I have tried installing it over bootloader and it will have touch then, but when flashed to recovery the touch never activates properly. So it all likely comes to that, as we'll need combine them in, properly applying proper checks for each display type and having it use the proper driver files, since can't load them all at once or it breaks things.
Working shrp for Borneo
thebestofall007 said:
Hello all, where would I start in making a working twrp for this phone?
Does anyone know if Motorola has released the device tree/source code for this phone so we can make the roms? LineageOS would be ideal.
Click to expand...
Click to collapse
First place to start: twrpdtgen
Read the "readme"
Also check out:
[DEV]How to compile TWRP touch recovery
Device tree made from A10. Should still be relevant for A11.
Kernel for A10. Unfortunately I don't think Moto released the one for A11 yet. You can ask on their GitHub and devs might consider your request.
TWRP for A11. Touch is working.
Edit : here's a link for the device tree (in text) from A11
maybe this will work
thebestofall007 said:
Hello all, where would I start in making a working twrp for this phone?
Does anyone know if Motorola has released the device tree/source code for this phone so we can make the roms? LineageOS would be ideal.
Click to expand...
Click to collapse
maybe this will help probably https://github.com/MotorolaMobilityLLC/kernel-msm
UPDATE: I have a telegram account where we are discussing how to make a custom lineage OS. I'm at the gathering stage and in the process of porting a device tree. For starters I want to start with lineage OS 18 because its the same android version the stock OS is, to be on the safe side, and that I've never done ROMS before.
Moto G Power 2021
I now have a device tree with the help of AOSPdtgen from the stock ROM from mirrors.lolinet: https://github.com/thebestofall007/android_device_motorola_borneo
I have started the build and got the first error:
https://imgur.com/a/XZoqy8B
I've looked this error up and they say it's because of the ram, but the error recurs at the same point. I have 16gb of swap, too.
thebestofall007 said:
I have started the build and got the first error:
https://imgur.com/a/XZoqy8B
I've looked this error up and they say it's because of the ram, but the error recurs at the same point. I have 16gb of swap, too.
Click to expand...
Click to collapse
you need alot of ram to build a rom for android 36GB of RAM or more will be beater to it wont crash
KILLFIREY1389 said:
you need alot of ram to build a rom for android 36GB of RAM or more will be beater to it wont crash
Click to expand...
Click to collapse
The error turned out to be entries in the proprietary-files.text file that needed to be deleted.
@thebestofall007 If you'll suceed. please take in consideration to build \e\ (aka deGoogled Lineage) too.
Here's a couple of interesting links that may help:
https://doc.e.foundation/support-topics/build-e
https://community.e.foundation/t/howto-building-e-roms-a-beginners-guide/26371
Last but not least, we've also suggested them (check here) to setup a "build (V)Machine" by modding this colab notebook to made it device agnostic:
https://github.com/viam1-dev/colab_lineage_build
Hope can "inspire" you.
Thanks in advance.
Does anyone have a complete list of sources so far? I have some experience in the past building ROMs for Android 5 and I wouldn't mind trying. I have a lot of computer resources to dedicate to building as well.
Device tree: https://github.com/thebestofall007/android_device_motorola_borneo-old
Does anyone know if there is a kernel source? I looked on the Moto github and couldn't find one. Is everyone using prebuilt for the time being? Also, do we need a vendor tree?
Thanks