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
Related
NEED HELP
Hello guys, I'm working on a generic tree for our beloved device Honor 7, but not getting enough success, so each and every of you are invited to help me create a new device tree for AOSP 5.1 ROM or CM 12.1, so that we can taste the Stock Android too.
The benefits of these ROMs are that the device will get more fast and stable as there will be minimum apps and bloatwares installed.
So, it is a humble request, that whosoever have any knowledge about creating a tree from scratch please help me.
I have created a skeleton of the tree but it is not a success too as there are many things we still have to consider.
@sminki and @kenshiwara, we will setup an organization on GitHub so everyone can contribute there only.
Hi,
It will be wonderfull to have CM on our honor7.
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
sminki said:
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
Click to expand...
Click to collapse
Thanks, this will help enough and I was not aware of your troubles
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Is there any whatsapp group of honor 7.I want to join it.
udayraj99 said:
Is there any whatsapp group of honor 7.I want to join it.
Click to expand...
Click to collapse
Stop spamming
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Mee too
omkarpranavxxx said:
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Click to expand...
Click to collapse
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
asiekierka said:
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Click to expand...
Click to collapse
Hello, did any of the CM compiled fully to be a flashable zip? if yes, then have you flashed it and took logcat?
Nishadan said:
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
Click to expand...
Click to collapse
Yup lesson learnt snapdragon or nothing frm now on
maybe you know
I post link - http://download-c.huawei.com/downlo...oadId=62086&version=204465&siteCode=worldwide
Honor 7 Open Source（PLK-L01_Android5_0_2_EMUI3_1_kernel_EN)
Any progress?
I hope I can do something,it is nice to see cm for honor 7.
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
cycovision said:
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
Click to expand...
Click to collapse
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
DigiGoon said:
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
Click to expand...
Click to collapse
good luck with your exams
Until then you can use this
New ROM for Honor 7 PLK-L01.
DigiGoon said:
Until then you can use this
New ROM for Honor 7 PLK-L01.
Click to expand...
Click to collapse
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
muhammad Shohayeb said:
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
Click to expand...
Click to collapse
I will be developing AOSP 6.0, if others can give it a try then maybe we can get it.
Hi all,
Relatively am a new developer, trying to build aosp got everything figured out (I hope). Blindly following some instructions and got device tree from old nougat branch in google git. Building takes more time or just hangs not sure what is happening..
Before you guys reply like you can't do that or this, I just expect a polite answers.
Refer below!
vasanthmes said:
Hi all,
Relatively am a new developer, trying to build aosp got everything figured out (I hope). Blindly following some instructions and got device tree from old nougat branch in google git. Building takes more time or just hangs not sure what is happening..
Before you guys reply like you can't do that or this, I just expect a polite answers.
Refer below!
Click to expand...
Click to collapse
Takes more thime then what?
Perhaps you should start with a known good configuration.
Elektroschmock said:
Takes more thime then what?
Perhaps you should start with a known good configuration.
Click to expand...
Click to collapse
OK. But am having errors in several areas after doing make otapackage.
Is there any good device tree, vendor, kernel to start with?
Because the one I got is from master branch from google git and of course that is from a nougat version.
BTW I'm having a old laptop with i5 and 4Gigs of Ram. Probably that's why it is taking more time. Also running Ubuntu 18 on VM which is storing on my external hard disk of 2 TB connected through USB 3.0..
Am just curious and exploring things & trying to learn.
Thinking of giving up building 9.0 ...since I'm new to this.. May be proceeding with existing builds like 7.x.x from google or cm15.1 ..
vasanthmes said:
OK. But am having errors in several areas after doing make otapackage.
Is there any good device tree, vendor, kernel to start with?
Because the one I got is from master branch from google git and of course that is from a nougat version.
BTW I'm having a old laptop with i5 and 4Gigs of Ram. Probably that's why it is taking more time. Also running Ubuntu 18 on VM which is storing on my external hard disk of 2 TB connected through USB 3.0..
Am just curious and exploring things & trying to learn.
Click to expand...
Click to collapse
4gb of ram is your culprit, I suggest 8gb or 16gb .
Building is RAM dependent , and it also requires a fast SSD. I don't build roms, but I read a lot ?
Using Google Cloud for building now. Its amazingly fast!!!!! :fingers-crossed:
My first lineage 15.1 build stuck on Google bootscreen..
Build is successful.
anybody knows how to get log or error?
vasanthmes said:
My first lineage 15.1 build stuck on Google bootscreen..
Build is successful.
anybody knows how to get log or error?
Click to expand...
Click to collapse
If you want to build a ROM, you need to search and read a lot! This has been answered literally thousands of time on xda. Just use the search button and you would find that as a first result :fingers-crossed:
All the best for building the ROMs!
Nitin
vasanthmes said:
My first lineage 15.1 build stuck on Google bootscreen..
Build is successful.
anybody knows how to get log or error?
Click to expand...
Click to collapse
Do an -eng build, then you can debug the boot process via ADB.
Did you extract the vendor blobs, or add a repository containing them?
Elektroschmock said:
Do an -eng build, then you can debug the boot process via ADB.
Did you extract the vendor blobs, or add a repository containing them?
Click to expand...
Click to collapse
Vendor blobs I think I did, let me check once I reach home.
Thanks for advice on -eng build and by the way as nitin said I will check how to debug as well.
Been trying to build on Google Compute Engine VM... Crazy fast and best for those who are building for first time..
-Vasanth
Hello,
As the thread where I originally announced this was locked for reasons apparently unrelated to my build, and the links removed, I'm creating a new thread to keep the community aware of these builds.
I've been building LineageOS 14.1 from the official LineageOS source repository for my personal devices for some time now, and it finally occurred to me that others might find them useful.
These builds are created every Saturday night from a 100% unaltered LineageOS repository, which is synchronized with upstream every day. I must stress that there are NO MODIFICATIONS at all; if it worked/didn't work in the last official Cyanogenmod/LineageOS releases, it works/doesn't work in my builds. At Apple we called these "sustaining builds" -- they keep devices in sync with the latest security patches, but receive no new features.
The build for the Asus Zenpad 8.0 Z380K[N]L (aka P024) is at https://lineageos.disavowed.jp/p024/. This appears to work on both the Z380KL (as reported in the locked thread) and my Z380KNL. There are other devices being built as well ... if you would like me to add a 14.1 or 15.1 device to the weekly build roster, please let me know.
I hope this helps out folks who want to extend the service lifetime of their gear. Share and enjoy.
Edit: per moderator request, I need to provide a link to the source repository used to generate these builds to comply with XDA's interpretation of the GPL. It is the stock LineageOS repository, located at git://github.com/LineageOS/android.git. TheMuppets binary repository was used for the vendor blobs; it is at https://github.com/TheMuppets/
Hi, I have been using your build and updated my device weekly! it' s still good and awesome. (I also use your build for my nexus7)
if you find Oreo, Pie version! please let everyone know. Thank you.
Thank's keep update bro.
Hi, I don't see your weekly build for 22 Nov 2019.
Are there any issues ?
Nice update thanks friends l.
Yeap yesterday i reported, and TS promised to update.
Argh, apparently I wasn't subscribed to my own thread. Fixed.
Sorry about the SIM recognization problem. Somehow my private dev builds were being uploaded instead of the sustaining builds. @DEV87WHY pinged me a few days ago to let me know. The newest build is from the correct tree, and hopefully this won't happen again.
Sorry about that ...
Argh, apparently I wasn't subscribed to my own thread. Fixed.
Sorry about the SIM recognization problem. Somehow my private dev builds were being uploaded instead of the sustaining builds. @DEV87WHY pinged me a few days ago to let me know. The newest build is from the correct tree, and hopefully this won't happen again.
Sorry about that ...
Question about Unofficial rom for Asus ZenPad 8.0 z380knl
How do you update device with rom without losing apps and data? Is it possible to update from unofficial lineage os 14.1 from your repository to latest unofficial lineage os 14.1 build from your repository without having to reinstall apps? My understanding is that you follow the process of normal flash of rom but you don't wipe? Is that it?
Another question:
Does MTP(file transfer) work with this ROM?
Also, did you manage to unlock bootloader(oem unlock). I know it is possible to flash the rom without bootloader unlock. Is that how you do it or you have found a way to unlock bootloader?
Thank you so much.
poka_dan said:
How do you update device with rom without losing apps and data? Is it possible to update from unofficial lineage os 14.1 from your repository to latest unofficial lineage os 14.1 build from your repository without having to reinstall apps? My understanding is that you follow the process of normal flash of rom but you don't wipe? Is that it?
Another question:
Does MTP(file transfer) work with this ROM?
Also, did you manage to unlock bootloader(oem unlock). I know it is possible to flash the rom without bootloader unlock. Is that how you do it or you have found a way to unlock bootloader?
Thank you so much.
Click to expand...
Click to collapse
Hi there,
First off -- thanks for the gift! Much appreciated.
If you're just flashing one of my newer builds on top of one of my older builds, then you shouldn't have to do anything special. Just kick the device into recovery and flash on top of the older build. If you're coming from the ancient Cyanogenmod or the stock ROM, then AFAIK you'll have to wipe.
MTP *should* work but I've never tried it. I don't have my device with me right now so I can't do a quick verification.
For unlocking the bootloader, I'm trying to remember (this was several years ago). IIRC I put it into fastboot and did a tethered recovery boot (i.e., "fastboot boot /path/to/recovery_image_on_pc.img"). Then I did a full wipe and a flash ... and bricked the device because I had a Z380KNL and the Cyanogenmod image at the time supported only the Z380KL.
I then put the stock ROM back on, and when the KNL bits hit the Cyanogen repository, I flashed it with success. At no point did I ever successfully unlock the bootloader as far as I can tell -- I downloaded the ASUS unlock but it never reported success. When booted into fastboot, there's a locked symbol at the lower right of the screen. That doesn't interfere with flashing anything from recovery.
Oh, and important safety tip: to enter recovery from fastboot after you've flashed it via the tethered recovery boot, you'll have to choose "factory reset" on the KNL.
I hope that helps.
As soon as I find out MTP is working I will flash the rom
wileyc said:
Hi there,
First off -- thanks for the gift! Much appreciated.
If you're just flashing one of my newer builds on top of one of my older builds, then you shouldn't have to do anything special. Just kick the device into recovery and flash on top of the older build. If you're coming from the ancient Cyanogenmod or the stock ROM, then AFAIK you'll have to wipe.
MTP *should* work but I've never tried it. I don't have my device with me right now so I can't do a quick verification.
For unlocking the bootloader, I'm trying to remember (this was several years ago). IIRC I put it into fastboot and did a tethered recovery boot (i.e., "fastboot boot /path/to/recovery_image_on_pc.img"). Then I did a full wipe and a flash ... and bricked the device because I had a Z380KNL and the Cyanogenmod image at the time supported only the Z380KL.
I then put the stock ROM back on, and when the KNL bits hit the Cyanogen repository, I flashed it with success. At no point did I ever successfully unlock the bootloader as far as I can tell -- I downloaded the ASUS unlock but it never reported success. When booted into fastboot, there's a locked symbol at the lower right of the screen. That doesn't interfere with flashing anything from recovery.
Oh, and important safety tip: to enter recovery from fastboot after you've flashed it via the tethered recovery boot, you'll have to choose "factory reset" on the KNL.
I hope that helps.
Click to expand...
Click to collapse
Gift was my pleasure
The info is most usefull. Thank you for that.
I am currently running my ZenPad 8.0 z380knl on Asus stock rom but ardently looking to upgrade to android 7.1.2 for security reasons as well as other reasons.
I was investigating if everything is working on the new rom. Also upgrade procedure from stock rom to lineage os and from lineage os 14.1 to latest 14.1 lineage os. Thankfully you cleared all that up. Thanks so much !
Only thing that remains for me to find out is if MTP is working on rom, so please check it for me when you have the time.
BTW, I haven't seen your new buld since last week.Will there be no update ?
Is everything working with this ROM?
Can i get confirmation from someone who is actively using it..
MTP and everything else working?
pokadan said:
Gift was my pleasure
Only thing that remains for me to find out is if MTP is working on rom, so please check it for me when you have the time.
Click to expand...
Click to collapse
I just tried MTP (using OpenMTP-2.4.1 on MacOS) and it seems to work fine.
androidlover2019 said:
BTW, I haven't seen your new buld since last week.Will there be no update ?
Click to expand...
Click to collapse
There should be an update (or two!) today. The build rooster hung about midway through last week's build for deb, and was actually still running after seven days. I killed off the deb build process and it's progressing to the other devices, although much slower than it should be. I'll troubleshoot this after the regularly scheduled build completes late tonight.
(I'm using Arch Linux on this build machine, and it seems that something in the filesystem layer in kernel > 5.4.10 doesn't like operating under sustained heavy load)
I saw your new build today and have installed it. Thank you
However, The latest security patch has not been applied yet. Hope it will come in next build.
Thank you so much for maintaining the device.
Thank you wileyc !
wileyc said:
I just tried MTP (using OpenMTP-2.4.1 on MacOS) and it seems to work fine.
Click to expand...
Click to collapse
I have put the latest available rom lineage-14.1-20200202-UNOFFICIAL-P024.zip on my device and works flawlessly!
Million thanks
I have installed the newest one (built on 08 Feb)
the Android security patch was updated to Jan 2020! Thank you very much.
I am worried how long you will keep sharing your build weekly.
Hope next 2 years Thanks again.
I have also installed the latest. Thanks so much!
Thankyou for the update :good:
What about selinux?
I recently got my tab s7 sm-t870 for Christmas. I like it so far. I am trying to build TWRP and Lineage for it because only the 5g version is getting development. So i went and found out the source code for the wifi model is released by Samsung. I'm stuck on building a device tree from it though. I rooted the device so i can get the right blobs from it. If i were to succeed I will try to share it but I haven't used any file sharing sites so i don't know how that would work.
On second thought i should do twrp first before compiling Lineage but i still need a device tree
You might as well asked for the meaning of life...I doubt many will help with this. You maybe better off going to telegram and seeing if there is a dedicated forum, there maybe a dev there with more time or willingness
n0lan said:
I'm stuck on building a device tree from it though. I rooted the device so i can get the right blobs from it.
Click to expand...
Click to collapse
Have not done this before...
If I were to do this I would check out the github repositories of developers who are working on/publishing ROMs or recoveries for recent SAMSUNG devices.
Look what they use and from there find the equivalents for your tablet.
DHGE said:
Have not done this before...
If I were to do this I would check out the github repositories of developers who are working on/publishing ROMs or recoveries for recent SAMSUNG devices.
Look what they use and from there find the equivalents for your tablet.
Click to expand...
Click to collapse
hey i realized Ian has created a device tree for the s7 sm-t875 so i decided to clone it but when i lunch it complains that it doesn't exist in the config makefile. i'm getting so close but just need to figure out how to properly setup the files. I think the hard part is done finding something that would work. Do you have the knowledge of what I might be missing? This is the error
build/make/core/envsetup.mk:257: error: No config file found for TARGET_DEVICE gts7l.
Welp I just solved it it was just giving a different path in the BoardConfig.mk oops
You dont really lol.. samsung opensource is really just kernel source
elliwigy said:
You dont really lol.. samsung opensource is really just kernel source
Click to expand...
Click to collapse
wdym ??
Hi guys,
I am forced to upgrade my moto G5 plus due to a network update
In my moto G5 plus I have installed dotOS with android 11 and I am really happy with it, and I would like "clone" it on a Moto G Power.
Here are some questions:
1) since Moto G Power (2021) is not listed on dotOS but a GSI ARM64 available, has anyone experienced with that? I am also open to other custom ROMS (also Lineage OS doesnt have this devicelisted)
2) I also noticed that TWRP is not available for Moto G Power (2021), is there a good alternative or I have to use adb fastboot?
Thanks!
Edit:
I just found the thread:
[RECOVERY][UNOFFICIAL] TWRP 3.6.0-11 [BORNEO] Android 11 Based (updated 12/11/2021)
I can try that for question 2
Efone said:
Hi guys,
I am forced to upgrade my moto G5 plus due to a network update
In my moto G5 plus I have installed dotOS with android 11 and I am really happy with it, and I would like "clone" it on a Moto G Power.
Here are some questions:
1) since Moto G Power (2021) is not listed on dotOS but a GSI ARM64 available, has anyone experienced with that? I am also open to other custom ROMS (also Lineage OS doesnt have this devicelisted)
Click to expand...
Click to collapse
Presently I don't believe it is possible to have a custom rom as we need the kernel be released for it to have a chance, or a compatible similar device and its kernel.
Hi Onoitsu and thank you for the reply,
so I guess I could go with the stock ROM. I noticed that I can use https://mirrors.lolinet.com/firmware/moto/borneo/ has an official and blankflash (not sure what the difference is). If I understand the process correctly I could:
1) unlock bootloader
2) flash twrp in recovery
3) flash blankflash.zip (or official?) through twrp
4) flash magisk through twrp
5) restore my old phone dotOS android 11 backup through twrp
and I should have all the apps and data as in the old device?
Efone said:
Hi Onoitsu and thank you for the reply,
so I guess I could go with the stock ROM. I noticed that I can use https://mirrors.lolinet.com/firmware/moto/borneo/ has an official and blankflash (not sure what the difference is). If I understand the process correctly I could:
Click to expand...
Click to collapse
The blankflash is only if you can no longer flash anything by usual methods
Blankflash and EDL Mode
Is my device in EDL Mode?
How to boot into EDL Mode
Thanks for the info!
Should the reasoning above work if I use official instead of blankflash?
Efone said:
3) flash blankflash.zip (or official?) through twrp
Click to expand...
Click to collapse
Neither the blank flash nor official firmware are twrp compatible.
Thanks sd_shadow for the info, it is really helping me out.
I saw your post for using LSMA, but I couldnt find a Linux version. Is there one? Or the only other option I have is going through the fastboot process?
Can anyone tell me if there is going to be custom roms made for Borneo?
Hatrackman said:
Can anyone tell me if there is going to be custom roms made for Borneo?
Click to expand...
Click to collapse
Still the reason I cite in post 2 above, indeterminate, sadly.
Onoitsu2 said:
Still the reason I cite in post 2 above, indeterminate, sadly.
Click to expand...
Click to collapse
Mostly concerned because google has said they're going to stop their 'less secure app' thing at the end of this month and it might mean textnow will stop working outright for people that don't use play services.
Hopefully anyone working on making a custom rom for Borneo will see this thread and maybe give an idea if its going to happen.
Does this help?
If I wanted to start from scratch what would I need to know to make my own custom rom? Don't need a phone, will only ever use wifi. Just need microg basically.
The following statement is on the dotOS FAQs:
Q: My device is not supported! What should I do?!A: First reason can be that our development team doesn't have your device to support it or we no maintainer applied for this device. You can always use our GSI builds if your phone supports Treble Project.
Here we have this statement:
... Google requires every Certified Android device launching with Android 8.0 Oreo and above to support Treble.
Here borneo is listed as a supported device.
Does this mean dotOS GSI supports MotoGPower 2021 without the need of vendor blobs?
Onoitsu2 said:
Presently I don't believe it is possible to have a custom rom as we need the kernel be released for it to have a chance, or a compatible similar device and its kernel.
Click to expand...
Click to collapse
@sd_shadow
Two sites that potential rom developers may want to check out:
1) https://github.com/moto-common
check out: https://github.com/moto-common/andr...ernel/blob/12/dtb/bengal-moto-base-borneo.dtb
2) https://github.com/moto-sm6115
Scroll through the list of repositories, particularly in the moto-common site
@sdembiske that looks promising, I am willing to give it a shot and contribute to the community. Is there a good guide on how to build the kernel with vendor tree/blobs etc...?
Reference "Moto G Power 2021 XT2117-4 Firmware Extractions" - You will find the extracted kernel etc. in the boot.img extracted link that you can download - there are many other extractions that you hopefully can use to build a custom or AOSP rom.
Your best bet would be to add a pre-built kernel in the build - you can google that for how-to's.
Onoitsu2 said:
Presently I don't believe it is possible to have a custom rom as we need the kernel be released for it to have a chance, or a compatible similar device and its kernel.
Click to expand...
Click to collapse
The Xiaomi poco m3 has the same SoC and other innards as the Moto G Power 2021 and it also has unofficial Lineage OS 19 support. I am considering hitting them up and using their code as part of the build. I'm also requesting Motorola Mobility LLC to release the kernel source for Android 11. I already have a device tree for Borneo on my github. Me and Fazwalrus have a telegram chat set up for the ROM development here