Database Develop

Unofficial ROM Development LineageOS SM-A510F

Hello,
I would like to embark on the creation of an unofficial ROM based on LineageOS for the SM-A510F (A5 2016).
I have downloaded the LineageOS cm-14.1 branch source code.
I saw in the LineageOS wiki that they showed how to download and compile the source code for the already supported phones / tablets, and the A5 2016 is not yet supported.
I've seen that it is enough for a supported device to do: breakfast (the device name) to download the device configuration from the Github repository of LineageOS.
However, there is no configuration of the A5 2016 in the Github repository of LineageOS since it is not yet supported.
I would like to know how to create this configuration, find out if there are any wiki that explain how to architect the LineageOS project as well or how Android works internally.
I find it unfortunate that there is not enough documentation on creating unofficial ROM from LineageOS or directly from Google's sources, maybe I've been looking bad too.
Thank you in advance.

https://github.com/Exynos7580/android_device_samsung_a5xeltexx check here
---------- Post added at 06:07 PM ---------- Previous post was at 06:07 PM ----------
if u succesfully build the rom, i would like to be a tester

Another developer called zonik is trying to port lineageOS. Maybe you can ask to him for informations.
Inviato dal mio SM-G955U utilizzando Tapatalk

Thank you

Another good news for the A5 2016 community ! Keep it up

I'll stay tuned! Pure Android on A5 would be great, I've been waiting for it for a long time.
Please don't give up with this :>

Eu tenho um SM-A510M
caso precise de um testador eu estou disposto

I was trying to port ressurection remix but while halfway through cloning the repo, my ubuntu crashed... ?
I'm willing to be a tester too!

I would like to be a tester too. Approximately when will the ROM be finished?
I'm mentioning I have a A510F

Did u give up?
Do u have any news? I really wish this ROM will become real.

Severdragomir said:
Did u give up?
Do u have any news? I really wish this ROM will become real.
Click to expand...
Click to collapse
It isn't that easy, it takes time. I managed to get the source of resurrection remix but while building, there were alot of errors with the hardware tree...

XenRon said:
I was trying to port ressurection remix but while halfway through cloning the repo, my ubuntu crashed... ?
I'm willing to be a tester too!
Click to expand...
Click to collapse
Can I try to continue your work ? Just tell me how to do it

sm-a510f said:
Can I try to continue your work ? Just tell me how to do it
Click to expand...
Click to collapse
This time it didn't, was due to insufficient ram.
Look at my lost above. I'll try porting lineage os first since rr is now based on lineage
---------- Post added at 05:31 PM ---------- Previous post was at 05:19 PM ----------
DARLAIVE said:
Hello,
I would like to embark on the creation of an unofficial ROM based on LineageOS for the SM-A510F (A5 2016).
I have downloaded the LineageOS cm-14.1 branch source code.
I saw in the LineageOS wiki that they showed how to download and compile the source code for the already supported phones / tablets, and the A5 2016 is not yet supported.
I've seen that it is enough for a supported device to do: breakfast (the device name) to download the device configuration from the Github repository of LineageOS.
However, there is no configuration of the A5 2016 in the Github repository of LineageOS since it is not yet supported.
I would like to know how to create this configuration, find out if there are any wiki that explain how to architect the LineageOS project as well or how Android works internally.
I find it unfortunate that there is not enough documentation on creating unofficial ROM from LineageOS or directly from Google's sources, maybe I've been looking bad too.
Thank you in advance.
Click to expand...
Click to collapse
Extract kernel to kernel/samsung/a5xeltexx
Extract hardware to hardware/samsung_slsi-cm
Extract vendor to vendor/samsung/a5xeltexx
Extract device tree to device/samsung/a5xeltexx
Extract device common to device/common/samsung/a5xeltexx (if im not wrong, just follow the errors if there are any)
Then, build it again and do lunch, it should show up.

Arghhhh...... I'm getting the same errors all over again... See https://github.com/Exynos7580/android_device_samsung_a5xeltexx/issues/1

Deleted

I can't download it. Are u able to do it?

Its fake already tried it

XenRon said:
Arghhhh...... I'm getting the same errors all over again... See https://github.com/Exynos7580/android_device_samsung_a5xeltexx/issues/1
Click to expand...
Click to collapse
I think it is easier to port A3 2016 Lineage OS to A5 no ?
(A3 have 8 cores)

sm-a510f said:
I think it is easier to port A3 2016 Lineage OS to A5 no ?
(A3 have 8 cores)
Click to expand...
Click to collapse
I'll try... Should work though...

XenRon said:
Arghhhh...... I'm getting the same errors all over again... See https://github.com/Exynos7580/android_device_samsung_a5xeltexx/issues/1
Click to expand...
Click to collapse
Need download and put https://github.com/LineageOS/android_hardware_samsung_slsi-cm_exynos5 into hardware/samsung_slsi-cm

Build rom for redmi 4x

Im newby in build rom. But iminterest to learning. Can anyone help me ho lw to build rom for santoni and what should i know before do that.

randifilan said:
Im newby in build rom. But iminterest to learning. Can anyone help me ho lw to build rom for santoni and what should i know before do that.
Click to expand...
Click to collapse
Visit XDA developers Pc site

I suggest that you check out the LineageOS Wiki for some build instructions about other phones, to get an overview about the required steps, how the build system works and so on.
There's no official LineageOS for the Redmi 4X yet, here's the Redmi 2 build guide (I think most steps will be similar): https://wiki.lineageos.org/devices/wt88047/build
Be aware though that building a ROM takes some time and technical knowledge, even when you follow the guide step by step some things might not work, depending on your operating system and software installed.

Thanks, i will try that.

[DISCONTINUED ROM][8.1][OMS][SigSpoofing] Unofficial LineageOS builds by Admicos

(I'm new to all this ROM development stuff, apologies if there's anything wrong with what I'm doing)
These are my personal LineageOS builds. They aren't much different from regular LOS, other than some added patches.
More details and sources over at: https://git.issizler.club/LineageOS/LineageOS-by-Admicos
Download: https://www.androidfilehost.com/?fid=11410963190603912814
What's working/not working: Should be same as official LineageOS
XDA:DevDB Information
Unofficial LineageOS builds by Admicos, ROM for the ZTE Axon 7
Contributors
admicos
Source Code: https://git.issizler.club/LineageOS
ROM OS Version: 8.x Oreo
Based On: LineageOS
Version Information
Status: Beta
Created 2019-01-04
Last Updated 2019-01-04

CHANGELOG
15.1-20190201 1d456849f4b154381071c9ebae87ccff
15.1-20190121 45f811aecd226524c3c68394f0781e10
15.1-20190115 e9c47b0062b822c118f918318289a7e4
LOS Repo Sync
15.1-20190104-2 37ff7fb6510d0d819e10e932d3e18f9d
Fixed WireGuard
15.1-20190104
Initial Release

Nice. The addition of sigspoofing and substratum service would make plain LOS usable for me. Straight LOS and themes were always iffy.
[emoji106]
ZTE Axon 7 A2017U, /e/ v0.1 ROM, microG (NoGapps), Multiboot, XDA Legacy

As nobody really posted here, I just wanted to say that this is working really well.
I had huge gps problems with the last 15.1 unofficial, but it works perfectly in this one and it has some very nice additions as well and is 100% stable for me even with xposed and magisk.
 @admicos Thank you very much and I really hope that, if you have the time, you continue making these.

New build being uploaded right now, no changes other than a LOS repo sync.
The last couple test builds I made were somewhat iffy, but this one seems pretty well. (The recolored boot animation didn't make it in for some reason, but the rest are fine)

Everytime when i reboot the system to os or recovery,the recovery looks replaced and i cant mount data.
Not sure what caused it,i just flashed this on my non treble axon 7

Predatorhaze said:
Everytime when i reboot the system to os or recovery,the recovery looks replaced and i cant mount data.
Not sure what caused it,i just flashed this on my non treble axon 7
Click to expand...
Click to collapse
boy ter here rediscovering the wonders of encryption and dm-verity check

New build being uploaded, another regular LOS repo sync, should be done in about an hour
--
Predatorhaze said:
Everytime when i reboot the system to os or recovery,the recovery looks replaced and i cant mount data.
Not sure what caused it,i just flashed this on my non treble axon 7
Click to expand...
Click to collapse
I'm not sure why that's happening either. Can you replicate this on official LOS? If you can, I'd suggest you try asking on their thread, they might know more.

Good ROM for a while, why not update it? Is there a new kernel upgrade for the top post?

[armitage] said:
As nobody really posted here, I just wanted to say that this is working really well.
I had huge gps problems with the last 15.1 unofficial, but it works perfectly in this one and it has some very nice additions as well and is 100% stable for me even with xposed and magisk.
@admicos Thank you very much and I really hope that, if you have the time, you continue making these.
Click to expand...
Click to collapse
What version of Xposed are you using? I've always wanted to try this ROM, but thought there wasn't an official Xposed yet. The others I knew at the time were reportedly shady.

Sorry for the long wait (kinda forgot about this existing :/), and sorry for the bad news;
As I am planning to switch to another phone, I cannot continue making this anymore.
I might continue this as a GSI or something, but I really don't know if that will happen, as Android source is a big mess that I don't think I, and my (reasonably fast) CPU are prepared to handle. (Any pointers to dealing with this are greatly appreciated)
It was a fun two years lurking around.
(ps: The source link is completely borked (and all my sources are gone). I probably should stop trying to be fancy and use a public Git server like a normal person the next time)

If your build env is on Docker, I can easily stage a build server for you. It won't be fast, but you can leave it running all night long if you need, and free up your computer.
Also, if you're not using Docker, I can help you set it up, so anyone else can easily build by themselves if they choose to do so.

Can I upgrade the kernel?
[9.0/8.1] Updated LOS Kernel [Version 3.18.136]

@admicos THREAD CLOSED!
In the OP, the mandatory link tp source code provides a HTTP 404 error.
Please advise the moderators' team if you want the thread to be re-opened and to update the link.

[DEVELOPMENT] [TB-X606F/X606X/X606V] Device tree bringup for the TB-X606 family

Hey y'all, I've been recently working on a device tree for the X606F (codenamed "achilles6_row_wifi").
I do not have much experience on this topic, so I am essentially doing this blindly, basing it off other's work. I am currently only targeting the X606F, but X606X/V may also be supported.
I am looking for someone to collaborate with, I have an Android build machine ready to test changes. As I saw that Android 12 GSIs boot, I tried to build LineageOS 19.1, but ended up in the usual "black-screen bootloop", I don't know how to debug this so I am looking for someone to help
Link to the tree: https://github.com/UsrBinLuna/device_lenovo_achilles6
Credits
Yahoo-Mike for their recovery tree
Sushrut1101 for DumprX

did u remove the qcom references yet

areallydumbperson said:
did u remove the qcom references yet
Click to expand...
Click to collapse
yes

Hi,
Were you able to make any progress or was it abandoned?

Abandoned OP hasn't done any commits in ages

General Starting kernel from source

Hello everyone,
I recently got this phone and of course noticed xiaomi didn't release the kernel source.
So I'm planning on trying to build a kernel from source that would work with stock miui (I'm aiming for 13.0.13.0 EU android 11 version at first).
My starting point is the source from CAF: LA.UM.9.15.1.r1-07200-KAMORTA.0. If you think a different source would be better please let me know, but I thought this one came closest).
Now I am looking at the Mi github for devices comparable so I can get some specific xiaomi/component source stuff. Currently looking at Redmi POCO M3 its A10 but should be okay.
I will post a link to github soon.
Just letting you know.
SOURCE: https://github.com/daeiron/spes_kernel

So I now have a compilable source here: https://github.com/daeiron/spes_kernel
I used proton clang to compile.

Okay so here is the first result, this is untested. But if someone wants to test it go ahead. My phone isn't unlocked yet
You could first try flashing test_boot.img to boot partition and see what it does (you should be on 13.0.13.0 stock), if that doesn't work you could try flashing dtbo.img to the dtbo partition.
Please make a backup first! This probably won't work.

This is very interesting.
It's great to see that there is another way to have a kernel source, even if Xiaomi doesn't want to release the official.
I'm in the middle of a move, so I can't test it because I need my phone fully functional, but I should be able to help out in time, especially once the kernel is more stable.

Can someone provide me a full dmesg log and maybe a logcat from just after boot. I could take a look at that while I am waiting for the unlock time of a stupid 7 days.

Does anyone have a schematic diagram for our phone? Im trying to find the UART pins

How the project is doing?

I have some of the drivers, extra functions, device specific stuff ready in the source with some cherry picking and reverse engineering the stock kernel with ghidra, but not (nearly) everything. I was planning to find if there are uart pins on the main board with a logic analyzer as it wouldnt make sense to go forth without testing and getting it booting. Because it isn't booting yet. But Im going on a vacation to mid February so there won't be much progress until then unfortunately. If i remember correctly I still need to do the touchscreen/lcd driver (nt36...& focaltech, bq25.. charge driver, all camera's, all connectivity (this shouldn't be hard) and probably some more stuff. There is some source code out there for some of the things but they are not identical to the reversed source so that will be more tricky.

Something to keep in mind, there is most likely a bug in the wifi or the Bluetooth driver ( perhaps both? ) that causes the device to freeze a bit when both are on and the wifi signal is bad.
My guess is that the wifi driver tries to reconnect way too often and something freezes

this is for redmi note 11?
and what's android version 11,12 or 13? pls

yorux2016t said:
this is for redmi note 11?
and what's android version 11,12 or 13? pls
Click to expand...
Click to collapse
Presumably based on Android 12 kernels. But I believe it works regardless on the version. OP of this post literally is doing God's work

thomas1991_12 said:
Does anyone have a schematic diagram for our phone? Im trying to find the UART pins.
Click to expand...
Click to collapse
I've never seen any schematics for anything and I can't believe they would be helpful.
A PCB layout would be helpful, but I haven't seen that either.
In ye old day a UART might have some level shifters.
Nowadays things are more minimal.
You'll get the raw pins out of the SoC.
You'll probably need a USB UART adapter that can work with 1.8V logic levels.
It would be nice to find the reset line, that's very helpful for hacking.
That way you don't have to wait for 10 second power button pushes.
An oscilloscope on likely test points on the board while booting is the easiest way to find a UART.
My specialty is Android ereaders and I've got a half dozen with permanently installed UART connectors.

I think UART should be your last resort, pretty sure the kernel should be writing to RAM and you can read that.

thomas1991_12 said:
Okay so here is the first result, this is untested. But if someone wants to test it go ahead. My phone isn't unlocked yet
You could first try flashing test_boot.img to boot partition and see what it does (you should be on 13.0.13.0 stock), if that doesn't work you could try flashing dtbo.img to the dtbo partition.
Please make a backup first! This probably won't work.
Click to expand...
Click to collapse
well Im going right now try it on pixelexperience 12.1. after that I give some feedback
well, phone instantly boot in to fastboot so nothing there, I was thinking if the source code is not out yet, then what source is used to create kernel for PE roms?

Samuel Ladziansky said:
bueno, voy ahora mismo, pruébalo en pixelexperience 12.1. después de eso doy algunos comentarios
bueno, el teléfono se inicia instantáneamente en fastboot, así que no hay nada, estaba pensando que si el código fuente aún no está disponible, ¿qué fuente se usa para crear kernel para roms PE?
Click to expand...
Click to collapse
Stock kernel

hmmm, so they edit only ramdisk to get it work with PE, interesting

I do little searching and found this...
GitHub - javashin/android_kernel_xiaomi_bengal at 11.0-gcc
MoonBase™ CAF MSM-4.19 kernel source for POCO M3 / Redmi 9T [Fury-Bengal] [Force-Fast-Foward] /.PUSH./ - GitHub - javashin/android_kernel_xiaomi_bengal at 11.0-gcc
github.com
EDIT: here is original source from is forked https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/lime-q-oss
is for "bengal" board but not SM6225 (sdm665) but SM6222 (sdm662)
but I think when we use kernel configuration from stock kernel (like in /proc/config.gz) we maybe get working kernel?
I am going to try it, I downloaded it and we will see

This seems interesting. Does it work as nicely as the kernel extracted from MIUI that all these custom ROMs are using?

The time is over, guys.
Behold the source!!!
GitHub - MiCode/Xiaomi_Kernel_OpenSource at spes-r-oss
Xiaomi Mobile Phone Kernel OpenSource. Contribute to MiCode/Xiaomi_Kernel_OpenSource development by creating an account on GitHub.
github.com