Hello everyone. I decided to write a tree for it based on the sources of huawei. Work in the process, it remains to assemble the kernel and deal with Ramdisk and paint the size of its screen.
So let's get to the point. I am laying out now what there is to search for errors and the inclusion of which I could forget.
If we can assemble it, then it will be possible to assemble custom rom for it.
https://drive.google.com/drive/folders/1-Xmq93J4Uybd_jD9Vb78pU-UH2YYOFWd?usp=sharing
**UPDATE***
I posted it on the github. I tried to finish it. Thanks to Team Win Recovery Project and their repository
GitHub - Mirsem13/sourceTreeHuaweiMediapadM28.0: Source tree for huawei mediapad m2 8.0 tablet
Source tree for huawei mediapad m2 8.0 tablet. Contribute to Mirsem13/sourceTreeHuaweiMediapadM28.0 development by creating an account on GitHub.
github.com
I will try to collect lineage os on this tablet within this week
Forgive me for my English I live in Russia
你有个好主意。来,我在注意你
That would be amazing. I still love the hardware of this tablet, but the software is just awful.
**UPDATE***
Related
So apparently you dont have to request for the source code, you can just download it it from the consumer.huawei.com site. With this being available I really hope it will bring about some custom roms or even some custom EMUI 4.0 interface. Open Source Code
Also, something I didnt realize but Huawei has a very deeply supported dev center. From creating application to themes. Many countries have became apart of the their program. The only one I didnt see was the US. Huawei Developer Page
Source code for the Hauwei Mediapad M2 has been updated: Source Code dated 2017
Also an update to a Open Source Code for the M2-802LD Source Code dated 2018
THIS THREAD CLOSED
--------------------------
Hi friends,
Because lineageOS stop supporting xiaomi devices this month, so I decided to build LOS 16 ROM for sagit myself.
I have some experience of using linux, but that is my first time to build an Android rom.
I follow the official guide to build. https://wiki.lineageos.org/devices/sagit/build And I got the freshable zip rom "successfully".
However, after I install it via the lastest TWRP, it stuck on the boot MI logo and can not enter the system.
I ask one oneplus developer, he told me some xiaomi device need specific clang version, but he can not give me a solution. I come here and hope someone can give me some propose.
-----------------------------
UPDATE, I found los group ready the re-support xiaomi device. https://github.com/LineageOS/hudson/commit/9e0206569670a2566562e000b9f1e3492eacca83
But I still hope get some answer just for study.
-----------------------------
UPDATE II
I found the reason that I use a wrong branch of VT repo. I use another VT repo in gitlab when the github repo was closed because of DMCA. And the default branch of the gitlab one is not LOS16. My bad. Sorry to bother everyone.
Thread closed!
-LTT
Hi,
I'm a seasoned Linux user, but I'm relatively new to the world of free operating systems on smartphones. A couple weeks ago I bought an old Samsung Galaxy A5 (SM-A500FU) just for fiddling with LineageOS.
I spent about a week experimenting a lot and taking notes about ADB, Heimdall, TWRP, flashing ZIP files, etc. I found out that unfortunately LineageOS isn't officially supported for this phone. On the other hand, I managed to install a custom (unsupported) version of LineageOS on this phone:
lineage-16_a5_releases/README.md at master · DeadSquirrel01/lineage-16_a5_releases
lineageos 16 releases for Galaxy A5 SM-A500FU. Contribute to DeadSquirrel01/lineage-16_a5_releases development by creating an account on GitHub.
github.com
So much for a successful first experience.
Here's a very general question. Since there is no official LineageOS ROM available for my phone (as far as I understand the platform is a5lte), can I build a recent version of LineageOS from source for my specific device? Is this a more or less trivial task (like building LineageOS from source for an officially supported device) or will I have to jump through a series of burning loops?
Cheers from Austria,
Niki
Why we still don't have LineageOS 19?
What is missing ?
I asked luk and he told me build quality is not enough good in his opinion (that was month ago)
A couple Asus and Pixels got it so far, according to this post.
https://www.xda-developers.com/lineageos-19-android-12/
Kernel source is here but, judging by the performance of the stock rom, it's probably not great as a stable base :
GitHub - OnePlusOSS/android_kernel_oneplus_sm8350 at oneplus/SM8350_S_12.0_9Pro
Contribute to OnePlusOSS/android_kernel_oneplus_sm8350 development by creating an account on GitHub.
github.com
OnePlus themselves seem to have been pushing 12.1 to earlier models and are probably just going to go for a better Android 13 experience for the 9/10 models.
Even Google has made a mess of Android 12 on their own Pixels.
You can always check the OnePlus github at the url above and search for the chipset which you can confirm using the GSMArena page for the phone :
OnePlus 9 Pro - Full phone specifications
www.gsmarena.com
When you do, you'll see the latest revisions pushed by OnePlus along with the Android base, SM8350_S_12.0 in the above case. If you don't see the current version then there's no kernel source pushed by OnePlus which means custom rom modders need to try using previous kernel source. That's why all the Android 12 roms have been using the Android 11 kernel and why the phone had to have OxygenOS 11 before flashing
djsubterrain said:
Kernel source is here but, judging by the performance of the stock rom, it's probably not great as a stable base :
GitHub - OnePlusOSS/android_kernel_oneplus_sm8350 at oneplus/SM8350_S_12.0_9Pro
Contribute to OnePlusOSS/android_kernel_oneplus_sm8350 development by creating an account on GitHub.
github.com
OnePlus themselves seem to have been pushing 12.1 to earlier models and are probably just going to go for a better Android 13 experience for the 9/10 models.
Even Google has made a mess of Android 12 on their own Pixels.
You can always check the OnePlus github at the url above and search for the chipset which you can confirm using the GSMArena page for the phone :
OnePlus 9 Pro - Full phone specifications
www.gsmarena.com
When you do, you'll see the latest revisions pushed by OnePlus along with the Android base, SM8350_S_12.0 in the above case. If you don't see the current version then there's no kernel source pushed by OnePlus which means custom rom modders need to try using previous kernel source. That's why all the Android 12 roms have been using the Android 11 kernel and why the phone had to have OxygenOS 11 before flashing
Click to expand...
Click to collapse
thats why custom A12 roms, still need stock A11 firmware ?
GabrielSousa said:
thats why custom A12 roms, still need stock A11 firmware ?
Click to expand...
Click to collapse
Until now yes but judging by what was said above, even the A12 kernel isn't up to scratch for custom roms.
Hi!
i'm bm0x.
i tried to develop TWRP and OrangeFox for Xiaomi Pad 5 (Nabu), and well... it's not easy to work on that...
i made this thread to try get help, droping my latests repos on my nabu-dev organization on Github...
i don't have so much time to work in nabu, but i can help in a timely manner when i can
i hope to get so many news about that...
best regards...
the link of the org are in the image bellow.
i have the uncomplete lineage tree for the Pad 5 too in the org.
bm0x GitHub
ROM-PacMe said:
Hi!
i'm bm0x.
i tried to develop TWRP and OrangeFox for Xiaomi Pad 5 (Nabu), and well... it's not easy to work on that...
i made this thread to try get help, droping my latests repos on my nabu-dev organization on Github...
i don't have so much time to work in nabu, but i can help in a timely manner when i can
i hope to get so many news about that...
best regards...
the link of the org are in the image bellow.
i have the uncomplete lineage tree for the Pad 5 too in the org.
bm0x GitHub
Click to expand...
Click to collapse
How could someone help out for the development of these projects?
ROM-PacMe said:
Hi!
i'm bm0x.
i tried to develop TWRP and OrangeFox for Xiaomi Pad 5 (Nabu), and well... it's not easy to work on that...
i made this thread to try get help, droping my latests repos on my nabu-dev organization on Github...
i don't have so much time to work in nabu, but i can help in a timely manner when i can
i hope to get so many news about that...
best regards...
the link of the org are in the image bellow.
i have the uncomplete lineage tree for the Pad 5 too in the org.
bm0x GitHub
Click to expand...
Click to collapse
I think at the moment, If you already have an incomplete Lineage tree, then you should just focus on lineage and develop lineage recovery to simplify the process.