[ROM][8.1][ZC554KL] LineageOS 15.1 - Asus ZenFone 4 Max ROMs, Kernels, Recoveries, & Ot

Note:
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
Click to expand...
Click to collapse
LineageOS Description:
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working :
- Boots
- Display
- Wi-Fi
- Audio (except .wma, use VLC Player for that)
- Video
- Sensors
- LED
- Double tap to wake
Bugs:
- Camera (not working)
- Battery drain (because the camera service is restarting endlessly)
- The screen is reversed for about 3 seconds during the boot animation (won't fix)
Untestet:
- RIL
- Bluetooth
- GPS
Firmware:
Oreo firmware (at least for modem) is recommended, but Lineage 15.1 should also boot with Nougat firmware.
Kernel Source:
Github
Download:
Folder with all versions
lineage-15.1-20190218-UNOFFICIAL-X00I
Flashing notes:
You will need TWRP 3.2.2-0 or higher to flash this image. You can download it from here. See this thread for further information.
Warning:
Lineage 15.1 for ZC554KL is still far away from ready for daily use. The images in this thread are primary for developers.
XDA:DevDB Information
LineageOS 15.1, ROM for the Asus ZenFone 4 Max
Contributors
Voldracarno
Source Code: https://github.com/ThaFireDragonOfDeath/android_device_asus_X00I/tree/lineage-15.1
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Based On: LineageOS
Version Information
Status: Testing
Created 2019-02-19
Last Updated 2019-02-20

I tried it, and it's really really smooth, I can't wait for an update, if of course you plan to do one RIL and Wifi didn't work for me sadly, otherwise I would've kept it as a daily driver I really love the stock Oreo UI, thank you for your work, we always appreciate it

SammyInTheCity said:
I tried it, and it's really really smooth, I can't wait for an update, if of course you plan to do one RIL and Wifi didn't work for me sadly, otherwise I would've kept it as a daily driver I really love the stock Oreo UI, thank you for your work, we always appreciate it
Click to expand...
Click to collapse
Thanks .
Wifi doesn't work? Well that's a problem, because I can't fix this. For my device Wifi works without problems and I can't fix bugs which I can't reproduce on my device.
I have the Zenfone 4 Max ZC554KL with MSM8937 (Snapdragon 430), 3GB RAM and 32 GB Memory.
Are there multiple versions of the same device out there?
Edit: Make sure, that your modem firmware is for Android 8.
At the moment I concentrate on the camera bug, but that will take some time (because I'm on vacation in the next week).

Voldracarno said:
Thanks .
Wifi doesn't work? Well that's a problem, because I can't fix this. For my device Wifi works without problems and I can't fix bugs which I can't reproduce on my device.
I have the Zenfone 4 Max ZC554KL with MSM8937 (Snapdragon 430), 3GB RAM and 32 GB Memory.
Are there multiple versions of the same device out there?
Edit: Make sure, that your modem firmware is for Android 8.
At the moment I concentrate on the camera bug, but that will take some time (because I'm on vacation in the next week).
Click to expand...
Click to collapse
Yeah I have the same device as you although on CPU-Z it shows that I have a snapdragon 435 which IDK if there's a difference between the 430 and the 435, but yeah I have the 5.5 inch model with 32/3 GB RAM and rom

Here it is

SammyInTheCity said:
Here it is
Click to expand...
Click to collapse
The Snapdragon 435 (msm8940) is a different SoC. Maybe the WiFi driver, which I integrated in the kernel doesn't work for this SoC (I used the Wifi driver from the Xaomi Kernel for msm8937). Does your phone has already the Oreo Firmware?

Thats amazing.
I'll wait for the camera and battery drain fix before i test it.
How much internal space does the rom takes?

Voldracarno said:
The Snapdragon 435 (msm8940) is a different SoC. Maybe the WiFi driver, which I integrated in the kernel doesn't work for this SoC (I used the Wifi driver from the Xaomi Kernel for msm8937). Does your phone has already the Oreo Firmware?
Click to expand...
Click to collapse
Yes I do have Oreo ? are you sure it's a different SOC? My phone is the same model as yours and the processor speed and graphics processor is the exact same as well, is it just showing Snapdragon 435 to me? I mean I can't have a special phone, I just checked my phone details on another app and it shows 430, online I compared the 430 with 435 and the main differences were the ram speeds and the clock speed, from the 430 was 1.2 ghz while the 435 was 1.4ghz, but on the app that shows that I have a Snapdragon 430 it said 1.4 ghz so I'm hella confused now ?

ashye said:
Thats amazing.
I'll wait for the camera and battery drain fix before i test it.
How much internal space does the rom takes?
Click to expand...
Click to collapse
Thanks .
The system takes not more or less then Lineage 14.1 or Stock ROM. The size of the system partition is fixed by the vendor (ASUS).
SammyInTheCity said:
Yes I do have Oreo ? are you sure it's a different SOC? My phone is the same model as yours and the processor speed and graphics processor is the exact same as well, is it just showing Snapdragon 435 to me? I mean I can't have a special phone, I just checked my phone details on another app and it shows 430, online I compared the 430 with 435 and the main differences were the ram speeds and the clock speed, from the 430 was 1.2 ghz while the 435 was 1.4ghz, but on the app that shows that I have a Snapdragon 430 it said 1.4 ghz so I'm hella confused now
Click to expand...
Click to collapse
Theare are two versions of this phone. the regular Zenfone 4 Max 5.5 und the Zenfone 4 Max 5.5 Pro. The pro version have a Snapdragon 435:
"Powering the ZenFone 4 Max Pro is a Qualcomm Snapdragon 435 octa-core CPU clocked at 1.4Ghz, Adreno 505 GPU, and 3GB RAM. The only difference with the ZenFone 4 Max is the processor and it’s not even a big improvement. The SD435 has all the features of the SD430 with the addition of Snapdragon X9 LTE modem capable of LTE Cat7 downlink and LTE Cat13 uplink."
Read more at https://www.yugatech.com/mobile/asus-zenfone-4-max-pro-review-philippines-price/

Voldracarno said:
Thanks .
The system takes not more or less then Lineage 14.1 or Stock ROM. The size of the system partition is fixed by the vendor (ASUS).
Theare are two versions of this phone. the regular Zenfone 4 Max 5.5 und the Zenfone 4 Max 5.5 Pro. The pro version have a Snapdragon 435:
"Powering the ZenFone 4 Max Pro is a Qualcomm Snapdragon 435 octa-core CPU clocked at 1.4Ghz, Adreno 505 GPU, and 3GB RAM. The only difference with the ZenFone 4 Max is the processor and it’s not even a big improvement. The SD435 has all the features of the SD430 with the addition of Snapdragon X9 LTE modem capable of LTE Cat7 downlink and LTE Cat13 uplink."
Read more at https://www.yugatech.com/mobile/asus-zenfone-4-max-pro-review-philippines-price/
Click to expand...
Click to collapse
But I don't think I have the pro version, my cameras are 13mp+5 ???

SammyInTheCity said:
But I don't think I have the pro version, my cameras are 13mp+5 ???
Click to expand...
Click to collapse
Ok thats strange. But the fact is, it works on my device (so there must be a difference between our phones). And I have no Idea, whats the problem or how to fix it. Do you have a logcat and dmesg log?...

Voldracarno said:
Ok thats strange. But the fact is, it works on my device (so there must be a difference between our phones). And I have no Idea, whats the problem or how to fix it. Do you have a logcat and dmesg log?...
Click to expand...
Click to collapse
Nope ? as soon as I saw the RIL and wifi didn't work I uninstalled it, maybe I did something wrong when installing? I think I flashed Magisk right after flashing the rom or it was that device decrypt zip file I forgot which it was, could that be it?

SammyInTheCity said:
Nope as soon as I saw the RIL and wifi didn't work I uninstalled it, maybe I did something wrong when installing? I think I flashed Magisk right after flashing the rom or it was that device decrypt zip file I forgot which it was, could that be it?
Click to expand...
Click to collapse
You need the device decrypt file only on Stock ROM. And I didn't testet, what happens with magisk (I don't use this). But Root (the su zip from lineage) is already integrated. You can enable root in the developer settings (but System files can't be changed at this time, because the system partition is read only).

Hey guys, I would like to know if dev will also develop something for the ZF4 Selfie (X00LD), because it's a good pen device that ZenUi cuts too much of its potential performance.

LiiRulez said:
Hey guys, I would like to know if dev will also develop something for the ZF4 Selfie (X00LD), because it's a good pen device that ZenUi cuts too much of its potential performance.
Click to expand...
Click to collapse
I'm not talking for the dev, but I think its hard to develop a rom for a device he can't test it with, and are there no forums for your device?

LiiRulez said:
Hey guys, I would like to know if dev will also develop something for the ZF4 Selfie (X00LD), because it's a good pen device that ZenUi cuts too much of its potential performance.
Click to expand...
Click to collapse
SammyInTheCity said:
I'm not talking for the dev, but I think its hard to develop a rom for a device he can't test it with, and are there no forums for your device?
Click to expand...
Click to collapse
Developing for a device, which I don't have is impossible. For the example for the Zenfone 4 I produced about 20 not booting Images before the first fully booting image. After every build, I need a device to flash it and see in dmesg and logcat whats going on on the device (luckily it is possible to connect to the device with adb shell during the boot animation before the system is up to watch out, why the image don't boot).

Voldracarno said:
Developing for a device, which I don't have is impossible. For the example for the Zenfone 4 I produced about 20 not booting Images before the first fully booting image. After every build, I need a device to flash it and see in dmesg and logcat whats going on on the device (luckily it is possible to connect to the device with adb shell during the boot animation before the system is up to watch out, why the image don't boot).
Click to expand...
Click to collapse
I understand, it's a shame my X00LD is new, if I had another device I could start learning how to compile and do it, but ...
Using Android Studio, can I emulate a device like that?
if that's the case, I start my studies today.

LiiRulez said:
I understand, it's a shame my X00LD is new, if I had another device I could start learning how to compile and do it, but ...
Using Android Studio, can I emulate a device like that?
if that's the case, I start my studies today.
Click to expand...
Click to collapse
Android Studio can emulate a generic android device, but not a specific device. You will need Android studio only if you want to develop Android Apps. For porting Lineage you don't need it (I even haven't installed it on my build vm).
Here is a short version how I build the Lineage image (I will complete/correct this tutorial, if I'm on my PC at home) (you will need a Computer with much RAM. 16 GB RAM is recommended)
1. For building you will need to set up a Ubuntu 18.04 LTS VM (so you should know how to use Virtualbox) (the Ubuntu VM have to at least 8GB RAM). Or better: Use a real Ubuntu 18.04 LTS Machine.
2. Then you have to execute the steps from this tutorial from "Build LineageOS and LineageOS Recovery" to "Downloading the source code".
3.After that you have to put the local manifest (I will post that file later) in the .repo directory and sync again.
4. Then you will need to download and extract a Stock image from the ASUS Website for your device.
To extract you must first decompress the system image file with brotli and than convert it with sdat2img. After that you can mount the image and copy all the files out in a seperate directory.
5. After that you cd in the device directory and exec ./extract-files.sh PATH_TO_EXTRACTED_SYSTEM_FILES
6. At last you have to cd to the Lineage build dir and exec the following commands:
source build/envsetup.sh
export LC_ALL=C
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G" (if jack runs still out of memory during building increase the -Xmx value to 6G)
export WITH_SU=true (for integrated root)
lunch lineage_X00I-userdebug
make -j4 bacon (replace the 4 with the count of concurrent build jobs you want to use)
After that you you will find the flashable Zip in the out directory.
To rebuild after changes you can repeat step 6 (to rebuild only the changes files) or delete the content of the out directory and repeat step 6 (for a full rebuild).
And if you didn't close your terminal window you only need to exec the make -j4 bacon commend to start a rebuild.
To update the sources of android you have to run repo sync in the lineage directory.
If you want to learn more about Android:
https://source.android.com/setup

It may have been asked...
Is this rom compatible with the 2gb/16gb version of zenfone 4 max?

The RIL wont work for me but the wifi does.
SammyInTheCity said:
I tried it, and it's really really smooth, I can't wait for an update, if of course you plan to do one RIL and Wifi didn't work for me sadly, otherwise I would've kept it as a daily driver I really love the stock Oreo UI, thank you for your work, we always appreciate it
Click to expand...
Click to collapse
Same as yours bro..the RIL wont work for me except for the wifi. This is a perfect game changer rom if all the things in this rom is working.

Related

[ROM][6.0.1][PRE-ALPHA] Unofficial Cyanogenmod 13.0 for Huawei Honor 4X/4C (Kirin)

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.1 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
All the source code for CyanogenMod is available in the CyanogenMod Github Repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review.
Please see the next posts for downloads, bug list and instructions.
XDA:DevDB Information
[ROM][6.0.1][PRE-ALPHA] Unofficial Cyanogenmod 13.0 for Huawei Honor 4X/4C (Kirin), ROM for the Honor 4C
Contributors
hackslash
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: No Longer Updated
Created 2016-09-12
Last Updated 2016-11-19
Contributions and Bug List
Contributors:
First of all thanks to the P8 Lite Dev Team, @XePeleato @olrak and @haky 86 for helping me out throughout (and especially @XePeleato for offering extra support despite his busy schedule)
To @lloco73 and @xperiafan13 for their work on the kernel sources.
@gabry3795 for fixing the RIL on Mate 7.
And you for testing this ROM, sending me logcats and saying thanks (it's ok if you didn't, still I thank you)
What's not Working:
WiFi
Bluetooth
Audio
Sensors
SD Card
GPS
and many other things I haven't tested yet.
What's Working:
Android as System
Graphics Binaries (except hwcomposer)
Notification Light
MTP
Brightness Slider
RIL
Dual SIM (with 4G LTE) and Mobile Data
Sensors
USB OTG
Downloads and Instructions
Build: Pre-Alpha-2
Build Date: 15th August 2016
System Image download link: https://mega.nz/#!5Ag2TLjB!_dqfki1PWOU2NS-7bf240gyRwhilPikseCH2ZalvOsc
Boot Image download link: https://mega.nz/#!QRQTERgJ!ZZjoDxRDeKqxqQpJ1TGzigi7tjTk5Ec5imFBTkCccBA
Use Fastboot to flash the above images. Please make a complete data, dalvik and cache wipe using TWRP.
It works with the Chinese versions also (however I don't know for how long since the CN variants have less allocated size for /system partition 1.5 GB whereas I am targeting the 2.5 GB variants).
Screenshots:
http://imgur.com/a/P93Hy
Source Code:
I alone might not be able to fix every little bug but with your help that could be possible. If you have any knowledge about building ROMs, please look at the repositories below and help us build the perfect ROM for our device.
Device Tree: https://github.com/HuaweiHonor4C/android_device_huawei_cherryk
Vendor Libraries: https://github.com/HuaweiHonor4C/android_vendor_huawei_cherry
Kernel: https://github.com/HuaweiHonor4C/kernel_hi6210sft_mm
WOW
excellent, and I want to start to work and bring great things to this device ...
That's great!I don't have any knowledges about developing,but maybe i can test your work on Chinese version Honor 4C CHM-TL00H.
Sorry for my bad English.
Android小楼阁-QQ群 439637151
来自搭载Android 2.3 GingerBread的华为Y220-T10
Sorry cor the dead links in first post. They'll be live on 4th May. (My monthly server quota limit is reached and I have to wait for it to reset).
Also a update, I have been able to get CM to boot but still the boot doesn't finished due to issues with CM's surface flinger. I have been trying to patch Mali userspace binaries and gralloc to make them compatible. Let's see if that works.
Does anybody here has experience with Java classes and programs. I have a small task for that person. I have managed to extract RIL class from our stock framework. However, I believe the class has to made compatible with AOSP. Any Java dev up to the challenge?
hackslash said:
Does anybody here has experience with Java classes and programs. I have a small task for that person. I have managed to extract RIL class from our stock framework. However, I believe the class has to made compatible with AOSP. Any Java dev up to the challenge?
Click to expand...
Click to collapse
hi dear.
what did you do?
it's A long time did not reveal the amount of progress.
which point of CM13 way you are?is it possible?
if you go here http://consumer.huawei.com/en/support/search/index.htm?keywords=Honor 4X (Che2-L03)), you can find the kernel open souce from honor 4x/4c, this would work for anything? i never knew this existed before lol
EDIT: i guess you found it anyways, since the gpu drivers are incompatible (i guess?), just a question, this only apllies to cm or to any custom rom?
Any prog?
Sir,HUAWEI P8Lite's CM13 has arrived!https://tapatalk.com/shareLink?url=...share_tid=3419852&share_fid=3793&share_type=t
来自华为荣耀畅玩4C CHM-TL00H -天生急性子 Android 小楼阁
here the cm13 of p8 lite http://forum.xda-developers.com/p8lite/development/rom-cyanogenmod-13-0-arrived-t3419852
if you didnt know, Honor 4X, Honor 4C, P8 Lite, G play and G Play mini phones shares the same specs internal, only some small differences between them, principally that p8 lite has more internal storage, the rest is the same, so when this cm13 is released maybe it will work? i know aosp system.img didnt flashed for some reason, but i guess if xepeleato make a flashable zip it could work
EDIT: and hak86 confirmed that any phone with hi6210sft board, it will work, so it depends if he releases .img or a flashable zip
panchovix said:
here the cm13 of p8 lite http://forum.xda-developers.com/p8lite/development/rom-cyanogenmod-13-0-arrived-t3419852
if you didnt know, Honor 4X, Honor 4C, P8 Lite, G play and G Play mini phones shares the same specs internal, only some small differences between them, principally that p8 lite has more internal storage, the rest is the same, so when this cm13 is released maybe it will work? i know aosp system.img didnt flashed for some reason, but i guess if xepeleato make a flashable zip it could work
EDIT: and hak86 confirmed that any phone with hi6210sft board, it will work, so it depends if he releases .img or a flashable zip
Click to expand...
Click to collapse
It will work flawlessly. The system.img didnt flashed because P8Lite has 16 GB internal with 3-4 GB reserved for system partition whereas Honor 4 has 8 GB internal with 2.5 GB reserved for system partition. Due to this difference in partition sizes the image didnt flashed.
I'll clone his repo and will try a build in one or two days. I was actually busy with my exams and entrance tests for the past three months so I wasn't able to work on this project.
@hackslash Thank you very much! im waiting to test it on My honor 4X, since i only tested that AOSP from russian forums, that had some bugs like signal, BT, etc,(static wifi if i remember right), and well, it flashed well
hackslash said:
It will work flawlessly. The system.img didnt flashed because P8Lite has 16 GB internal with 3-4 GB reserved for system partition whereas Honor 4 has 8 GB internal with 2.5 GB reserved for system partition. Due to this difference in partition sizes the image didnt flashed.
I'll clone his repo and will try a build in one or two days. I was actually busy with my exams and entrance tests for the past three months so I wasn't able to work on this project.
Click to expand...
Click to collapse
Thank you,but in China after September 15,2015,Honor 4C Plus also has 16GB ROM.
来自华为荣耀畅玩4C CHM-TL00H -天生急性子 Android 小楼阁
I already left a thank you but just wanted to leave a coment to praise your effort on doing this, so thank you again =D
I'm not a developer too...
But I'm using honor 4c.
I really appreciate your work no one has tried to build a custom rom for honor 4c.thank you for trying to do it.I hope you succeed
cyanogenmod roms are very fast and stable please make it for our device

[ROM][26May][GNU/Linux] Sailfish OS 2.0.1.11 (community port)

Announcing Sailfish for the Sony Xperia Z3 Compact!
This is not Android!
This should be thought of as a development experiment. It may be useful if you are a developer and want to write/port apps the the Sailfish operating system. It is not an end-user product, however, if you wish to experiment and try something different then feel free!
Please do not contact Jolla Care or Jolla Developer Care, as this is not the Jolla phone.
Special thanks to:
rss351 and locusf for the collaborative effort in porting SailfishOS to the Z3 compact
Everyone from the SailfishOS team/community, sledges and mal- in particular.
All Cyanogenmod devs, since SailfishOS uses drivers from Cyanogenmod to talk with the phone's hardware
Known issues:
Bluetooth isn't turned on, cause i've put no effort in for that so far
Camera doesn't work, cause it's not hooked up to interface.
No recovery inside hybris bootimage (you need to flash manually to return to cm/use recovery)
Sensors dont work (auto-adjust brightness, etcetera)
The Jolla account/store functionality is not enabled. This is being worked on by Jolla. In the meantime: use openrepo's warehouse (see bottom of this post)
What works:
Booting, basic usage of the OS itself (browsing, etc)
Texting, calling, data over mobile network (2g and 3g tested, 4g should work but is untested)
Wifi (both 2,4 and 5 GHz)
Power management seems to work fine (not tested much though)
Looking around and getting a feel for SailfishOS
Using your phone to develop and debug SailfishOS apps.
Installation guide/checklist:
Insert default warranty void message here. Your warranty is now void
Make a backup (just to be sure)
Depending on what you need from your phone, this may not be a rom suitable for daily driving with. But installation is non-destructive to your existing rom, so if you're curious, give SailfishOS a try
I have not tested this on locked bootloaders, but since I needed to modify the kernel, I guess that you need an unlocked bootloader.
Note this is not an official Sailfish OS build, and the Xperia Z3c is not a Jolla phone, so please don't report bugs to Jolla. If you want to report a bug, this thread is perfectly fine for that.
BEWARE: this image is NOT optimized for security. The phone boots in development mode by default. There is a root shell on telnet port 2323. This is not secure and will give anyone who wants it remote access to your phone. When the port matures this will be fixed.
The Sailfish OS image does not provide recovery, and since the Xperia Z3c does not have a recovery partition, you need a bootimage with recovery on it to flash cm/stock/sailfishos upgrade. I highly recommend using Nut's Xperia files for this. Use the boot.img from your Cyanogenmod installation.
The Sailfish OS image is based on a recent version of Cyanogenmod 12.1, so update your Cyanogenmod installation while you are at it. Use cm-12.1-20160523-NIGHTLY-z3c.zip if you encounter issues with other versions. Using another rom is not guaranteed to work, even if this rom is based on Cyanogenmod.
You can find the required zip in this Mega folder: https://mega.nz/#F!ucoRnDjD!WAHNWgxLQX5SK1Vdu8MRWw
Use your favorite recovery (but not CM's recovery since that checks for signatures, which this image does not have) to flash the zip.
If you want to return to Cyanogenmod, extract boot.img from your cm-12 zip and flash that with fastboot. Alternatively you can restore a previous backup. There is no need to re-flash Cyanogenmod because it was not removed by installing SailfishOS. You can remove the /data/.stowaways/sailfishos/ folder afterwards to reclaim disk space.
FAQ
You can find a FAQ which mentions most common user questions for SailfishOS here: http://forum.xda-developers.com/jolla-sailfish/general/qa-sailfish-n4-thread-devices-t2727330 . It's mainly aimed to the Nexus 4 and 5, but it's fairly applicable for all other ports as well.
Contributing
If you think this is awesome, and want to help fix the issues currently open: come by in #sailfishos-porters on irc.freenode.net!
Sources
You can find all used source code (may not be up-to-date to the latest image, but all key components are there) here: https://github.com/xperiasailors/
Installing OpenRepos warehouse
OpenRepos warehouse is like what F-Droid is versus Google's Play store. An unofficial, community-driven repository of open source apps.
Go to settings->developer options and set a password. Then open a terminal or connect over ssh to your phone (ssh [email protected]_of_phone).
Download the latest version of the warehouse app from here: https://openrepos.net/content/basil/warehouse-sailfishos
When you are asked to terminate packagekit anywhere in the steps below, answer yes.
Code:
$ devel-su
# zypper rr adaptation0
# zypper in <location_of_rpm_you_downloaded>
After this Warehouse app will be in your app launcher.
Impressive work! :good:
Sent from my Sony Xperia Z3 Compact using XDA Labs
Just having a go now.
Edit: just stayed on sony screen. Would it be because I came from SLiMM 1.8 ROM and not from a CM based ROM?
mrrflagg said:
Just having a go now.
Edit: just stayed on sony screen. Would it be because I came from SLiMM 1.8 ROM and not from a CM based ROM?
Click to expand...
Click to collapse
Probably, yes.
SailfishOS uses libhybris for hardware communication, which in turn uses the existing Cyanogenmod installation for drivers and proprietary blobs. But hybris is compiled against a certain Cyanogenmod version, so using other roms as a base might fail.
I've updated the TS and put the exact CM version I used in there, that should work fine.
There are any news? The project is in development?
Alexander3273 said:
There are any news? The project is in development?
Click to expand...
Click to collapse
No news, I don't spend much time on this port, every now and then I fiddle around with it an evening.
I'm currently trying to get AOSP based Sailfish port because Cyanogenmod for Z3c seems unmaintained, but progress is very slow.
Thank you for the info. Do you know when a version (sailfish port) comes out?
Hello! Thanks for your work. May i know the progress ?
it would be great to see a real "european" OS coming out of the dust...
i hate the thought that any company from the other side of the atlantic are wheels in the monster of patriot act...
@maikoool Any news about new build or something?
Yes, look here:
https://nokius.net/SFOS/scorpion/PreAlpha/
But still no Cam, no BT, No Sensors and No video playback
AFAIK is the 'scorpion' the Z3 Tablet compact, so not the Z3 compact. The base images will probably be the same.
I've recently rolled a build using AOSP 5.1 from the Sony Xperia developer pages, but my Z3c has developed an issue where the top and bottom of the screen don't function, so I cannot test properly.
Aries is device name, right? What's scorpion ?
kskarthik said:
Aries is device name, right? What's scorpion ?
Click to expand...
Click to collapse
Aries = Z3 compact, Scorpion = Z3 Tablet compact
I'm waiting eagerly to see SFOS on aries Do you know anything about our device support on jolla's list ?

[UPDATED][ANTUTU 30000]ARM64 KERNEL SOURCES FOR REDMI2/2A/PRIME[devs needed]

64bit kernel sources for Redmi2/2A/Prime​
SHARING 64BIT WORKING KERNEL SOURCES FOR OUR DEVICE
WE ALL KNOW THAT OUR DEVICE HAVE A 64BIT CPU, BUT IT COULDN'T USE THAT 64BIT POTENTIAL BECAUSE OUR DEVICE WAS LAUNCHED WITH KK WHICH DO NOT SUPPORTS x64, BUT LATER XIAOMI RELEASED L FOR THE DEVICE BRINGING SUPPORT FOR MANY FEATURES LIKE VOLTE.
BUT ONE OF OUR DEVELOPER WAS ABLE TO CREATE 64BIT KERNEL SOURCES FOR OUR DEVICE. NAME "SEIRYU-2I"
HE ALSO CREATED WORKING MIUI8 64BIT BASED FOR OUR DEVICE. [url]https://goo.gl/2l1oqZ[/URL]
FEATURES: ARM64 BASED (PHEEWW)
SENSORS WORKS FLAWLESSLY
TOTALLY SUITABLE FOR VR AND DAYDREAM
BATTERY LIFE IS NOT COMPROMISED
AVAILABLE FOR BOTH MIUI AND CM (SEPERATE BRANCHES)
HAVEN'T FOUND ANY BUGS TILL NOW
NO PROBLEMS WITH VOLTE
SURPRISINGLY FAST
WE HAVE 64BIT KERNEL NOW!! SO, I WOULD LIKE TO INVITE ALL DEVELOPERS OUT THERE TO START WORKING ON 64 BIT ROMS LIKE, LIKE TESLA, DIRTY UNICORNS, AICP, CM14, ZYPHER AND DEVELOPERS OF OTHER GREAT ROMS OUT THERE AND KERNEL DEVELOPER LIKE JERRICA, LATTE AUTMN AND OTHERS.
[url]https://goo.gl/7AT5fS[/URL]
"THE SCORES HAVE BEEN UPDATED AS PROOF, GO GUYS TEST IT OUT YOURSELF"
AND PLEASE LET ME KNOW IF I AM MISSING SOMETHING.
SORRY FOR MY BAD ENGLISH and thank you :silly:
Let's go to the future. Thanks anyway.
Dyt199412syam said:
Let's go to the future. Thanks anyway.
Click to expand...
Click to collapse
lets see if the developers will work on this....
and if you can do please ping developers about this
fix the link dude
solomonR15 said:
fix the link dude
Click to expand...
Click to collapse
Fixed bro :highfive: :good:
Thanks for sharing :good:
Hope this can get some attention from the rom devs...
https://github.com/seiryu-2i/android_kernel_xiaomi_msm8916
Slight corrections required in the post
These sources are not x64. They are ARM64
x64 refers to 64 bit Intel CISC Chips like Atom whereas ARM64 Refers to 64 bit ARM RISC chips like Qualcomm SnapDragon and MediaTek Helios
Our Redmi 2 comes with Qualcomm ARM64 chipset ( albeit running a 32 bit OS) not x64 chipset
so make the necessary corrections
taalojarvi said:
slight corrections required in the post
these sources are not x64. They are arm64
x64 refers to 64 bit intel cisc chips like atom whereas arm64 refers to 64 bit arm risc chips like qualcomm snapdragon and mediatek helios
our redmi 2 comes with qualcomm arm64 chipset ( albeit running a 32 bit os) not x64 chipset
so make the necessary corrections
Click to expand...
Click to collapse
corrections made brother ... Btw thank you
didhiy said:
Thanks for sharing :good:
Hope this can get some attention from the rom devs...
https://github.com/seiryu-2i/android_kernel_xiaomi_msm8916
Click to expand...
Click to collapse
:fingers-crossed::good::highfive:
Well thank you for posting this thread
If anyone can make this kernel better then it would be good, as I only have limited free time to see the world & don't have any PC or laptop too to work on it :crying:
Jus a lil info, well maybe not useful though, if anyone wish to port 64bit custrom like CM, then you can always pick any existing device tree for our device. Remove "FORCE_32_BIT=true" from BoardConfig.mk and put "$(call inherit-product, $(SRC_TARGET_DIR)/product/core_64_bit.mk)" on top of "$(call inherit-product, $(SRC_TARGET_DIR)/product/full_base_telephony.mk)" line inside cm.mk or device.mk. Edit any other mk files to match your needs and edit some C/C++ sources inside your device tree to match 64bit target (mostly are only type conversions).
And for blobs, you can extract it from my rom port or just use ido (redmi 3) vendor blobs (name/rename it into suitable vendor and target based on your device tree), why? It's because, it came from the same source tree as our device have, so that means it's compatible (just remove the fingerprint we don't need it). And the rest, try to find it by yourself and fix any build error by your hand (in my experience all error only comes from mismatch config & any source code inside the device tree).
cheers
seiryu
seiryu.2i said:
Well thank you for posting this thread
If anyone can make this kernel better then it would be good, as I only have limited free time to see the world & don't have any PC or laptop too to work on it :crying:
Jus a lil info, well maybe not useful though, if anyone wish to port 64bit custrom like CM, then you can always pick any existing device tree for our device. Remove "FORCE_32_BIT=true" from BoardConfig.mk and put "$(call inherit-product, $(SRC_TARGET_DIR)/product/core_64_bit.mk)" on top of "$(call inherit-product, $(SRC_TARGET_DIR)/product/full_base_telephony.mk)" line inside cm.mk or device.mk. Edit any other mk files to match your needs and edit some C/C++ sources inside your device tree to match 64bit target (mostly are only type conversions).
And for blobs, you can extract it from my rom port or just use ido (redmi 3) vendor blobs (name/rename it into suitable vendor and target based on your device tree), why? It's because, it came from the same source tree as our device have, so that means it's compatible (just remove the fingerprint we don't need it). And the rest, try to find it by yourself and fix any build error by your hand (in my experience all error only comes from mismatch config & any source code inside the device tree).
cheers
seiryu
Click to expand...
Click to collapse
Thanks for your great works :good:
seiryu.2i said:
well thank you for posting this thread :d
if anyone can make this kernel better then it would be good, as i only have limited free time to see the world & don't have any pc or laptop too to work on it :crying:
Jus a lil info, well maybe not useful though, if anyone wish to port 64bit custrom like cm, then you can always pick any existing device tree for our device. Remove "force_32_bit=true" from boardconfig.mk and put "$(call inherit-product, $(src_target_dir)/product/core_64_bit.mk)" on top of "$(call inherit-product, $(src_target_dir)/product/full_base_telephony.mk)" line inside cm.mk or device.mk. Edit any other mk files to match your needs and edit some c/c++ sources inside your device tree to match 64bit target (mostly are only type conversions).
And for blobs, you can extract it from my rom port or just use ido (redmi 3) vendor blobs (name/rename it into suitable vendor and target based on your device tree), why? It's because, it came from the same source tree as our device have, so that means it's compatible (just remove the fingerprint we don't need it). And the rest, try to find it by yourself and fix any build error by your hand (in my experience all error only comes from mismatch config & any source code inside the device tree).
Cheers
seiryu
Click to expand...
Click to collapse
lets hope .... If we could see cm 14 based on it
....
Is the cm branch in seiryu's repo good to go?
iamsubhranil said:
Is the cm branch in seiryu's repo good to go?
Click to expand...
Click to collapse
yes... it is working flawlessly . it is ported from its brother device (redmi 3) with the required changes made . and 64 bit based miui gave me 29850 score on antutu. i hope further development will start based on 64 bit architechture.
:fingers-crossed::laugh:
abhishek 9650 said:
yes... it is working flawlessly . it is ported from its brother device (redmi 3) with the required changes made . and 64 bit based miui gave me 29850 score on antutu. i hope further development will start based on 64 bit architechture.
:fingers-crossed::laugh:
Click to expand...
Click to collapse
What? how can you get this performance? I only got 20876
abhishek 9650 said:
yes... it is working flawlessly . it is ported from its brother device (redmi 3) with the required changes made . and 64 bit based miui gave me 29850 score on antutu. i hope further development will start based on 64 bit architechture.
:fingers-crossed::laugh:
Click to expand...
Click to collapse
Ya here's the point. Using just a 64bit kernel won't do anything much. The ROM has to be 64bit too.
iamsubhranil said:
ya here's the point. Using just a 64bit kernel won't do anything much. The rom has to be 64bit too.
Click to expand...
Click to collapse
yeah truly said ... But..... As the kernel got ported ... Rom can also be ported from its brother device(redmi 3) . There are lot of custom roms available on this forum for redmi 3 like our device redmi 2. They can be easily ported if done by the right person.
abhishek 9650 said:
yeah truly said ... But..... As the kernel got ported ... Rom can also be ported from its brother device(redmi 3) . There are lot of custom roms available on this forum for redmi 3 like our device redmi 2. They can be easily ported if done by the right person.
Click to expand...
Click to collapse
Hey hey one thing. SD410 is armv7 and that means it is not a true 64bit processor. SD430 in redmi3 on the other hand is a armv8 processor and that's why they are using all 64bit things. Then, why bother?
iamsubhranil said:
Hey hey one thing. SD410 is armv7 and that means it is not a true 64bit processor. SD430 in redmi3 on the other hand is a armv8 processor and that's why they are using all 64bit things. Then, why bother?
Click to expand...
Click to collapse
I guess the kernel sources has been ported from Redmi 3 (IDO) which has SD 616 and not SD 430.

( Discontinued ) LineageOS-Port{Beta-4} For the R1_HD ( Discontinued )

Discontinued
!!!!PLEASE READ THIS SECTION BEFORE PROCEEDING TO FLASH THIS ROM!!!!
This is based of @vampirefo 's LineageOS , with my tweaks as I now use the port section to test and share with others to help the original LineageOS by @vampirefo to gain fixes
What works : so far , Ril(sim cards) , Bluetooth , Wifi , Audio , Microphone , HotSpot , Rotation .
Bug: Camera (really hard to fix)
P.S- THIS IS NOT A DAILY DRIVER READY ROM , THIS IS PURELY EXPERIMENTAL AND FOR THE JOY OF IT. DONT COME TO ME IF SOMETHING WENT WRONG . FEEL FREE TO REPORT MAJOR BUGS , BY MAJOR WE ( THE R1 HD'S ROUNDTABLE TEAM ) MEAN BUG AND GLITCHES THAT HINDER A NORMAL DAY 2 DAY USAGE OF THE ROM....SMALLER BUGS WILL BE LOOKED AT LATER IF POSSIBLE.
THANKS TO THESE DEVS THIS WOULD HAVE NOT BEEN POSSIBLE:
THANKS TO :
@CyanogenMod
@oleg.svs (REALLY BIG THANKS TO HIM)
@DeckerSU (ANOTHER REALLY BIG-UPS TO HIM)
@OceanLaber over at 4PDA.ru
@niklabs
@vampirefo
@ THE R1 HD'S ROUNDTABLE TEAM
System : Nougat 7.1.1
Kernel : 3.18.19
OS : LineageOS 7.1.1
FULL WIPE/CLEAN WIPE BEFORE FLASHING ROM AND GAPPS
!!!!!! Advance Wipe : Dalvik , system , cache , data , internal
then go back to twrp main menu , go to mount and uncheck system , go back to twrp main menu again
then go to reboot and choose recovery to reboot back to recovery.
Afterwards proceed to flash rom and gapps as usual!!!!!!
**Download Link is automatically updated to recent release**
Download : https://www.androidfilehost.com/?fid=457095661767128973 <<---- Beta 4
Gapps : http://opengapps.org/
Choose Platform: Arm
Android : 7.1
Variant : Its your choice. ( You can choose Micro version to enable Google Assistant )
PLEASE DON'T TELL ME THAT THE CAMERA DOES NOT WORK , WE ALL KNOW THAT IT DOES NOT
Enjoy!!
KazuDante said:
Ive Been looking around to find new roms that i could port to the R1HD. Ive ported about 5-8 roms that work on the R1 HD but only 2 works flawlessly but the others have a camera issue ( camera not connecting ).
Now ive found a x32-bit CM14.1 for the MT6735 , that works on the device that it was built for. Of course I quickly went to attempt to port it but no luck as of now. The issue seems to be that the /system partition is not mounted correctly in regards to our boot image .
Here are the links for those who want to look at it with us ( R1 HD's Round Table )
Where i saw the post : https://vk.com/smart_rom (scroll down a little bit and you guys will see cm14.1 mt6735, they even made a 64bit now)
Where the test builds are posted and also the sources : https://github.com/olegsvs/android_device_archos_persimmon/releases (now they are testing Resuretion Remix 5.8.XX)
It just to prove that MT6735 can also be running Android 7 as well.
As a team we can make this happen and bring new life to the R1 HD.
Update : Now a Resurection Remix 5.8 is also running on the MT6735 x32. ---> https://vk.com/wall-77256552_14248
Click to expand...
Click to collapse
Can you post links for the working Roms? I have been searching for a working Roms for quite some time and I can't manage to find one, don't know how you did it!
I will re-download and fix them to re-upload but only the one that everything works including the camera.
Sent from my BLU R1 HD using Tapatalk
Here one i ported but the camera does not work : https://drive.google.com/file/d/0BzU6b7lzLmttNjVEX0VqdU9OMTg/view?usp=drivesdk
Sent from my BLU R1 HD using Tapatalk
Are there any with a working camera that you could post?
Yes there is one that everything works , i will upload it soon , my only network access is this phone and im low on credits to get more data.
Sent from my BLU R1 HD using Tapatalk
Great!! Let me know if you get 14.1 up and running. I'm a huge cm fan and would love the nougat features! Thanks in advance for your hard work.
Great!!! Uyeee!!
Finally we are getting Nougat
UPDATE
STUCK IN SETUP WIZARD
Keyboard is fc
+++Fixed+++
But is Android marshamallow rom port
Can wait to try any cm 14.1 build
For our Phone
Cheers
Keep THE good job
quick update,found another CM14.1 thats compiled for a MT6737 device with a 3.18.19 kernel , i'm going to test it out because one of the port i made was also from a MT6737 device.
khyr said:
Great!!! Uyeee!!
Finally we are getting Nougat
UPDATE
STUCK IN SETUP WIZARD
Keyboard is fc
+++Fixed+++
Bit is antes Android marshamallow rom port
Can wait to try any cm 14.1 build
For our Phone
Cheers
Keep THE good job
Click to expand...
Click to collapse
aospkeyboard.....during setup avoid anything that requires you to type anything just skip them , then once pass that go to settings->about phone to activate develloper mode , then go to developer mode to enable usb debugging , then on your computer head over to apkmirror to download google keyboard or GBoard(new name for google keyboard), once downloaded open CMD(command prompt) or terminal (for mac n linux users ) type adb install ( then drag the downloaded keyboard in this spot of this message with just 1 space apart from last typed word wich is install in our case then hit enter)........once the install is complete head back to setting then language & input and switch it to GBoard or something else if you decided to get a different keyboard.
with the new cm14.1 that i found today thats built for a 3.18.19 this time actually mount's the system partition and now im able to grab logcats and dmesg ect.... right now what im seeing are egl/mali errors......but i really think we could use that source and use our binary files to build the r1 its own cm14.1 tree
other devs check update 2 in OP.
Modifying an updater-script from a different device and ROM would not necessarily work. IIRC, The Galaxy S2 and Galaxy S Blaze 4G was able to do that, but in this instance, with different phone hardware, this would not work. Luckily, you did not get bricked from doing this. Unless you are completely building from source, with the R1 files, these dirty ports will take a hefty amount of time. I recommend building a device tree and start building with the kernels that either you have found, or have been created on this forum.
xWolf13 said:
Modifying an updater-script from a different device and ROM would not necessarily work. IIRC, The Galaxy S2 and Galaxy S Blaze 4G was able to do that, but in this instance, with different phone hardware, this would not work. Luckily, you did not get bricked from doing this. Unless you are completely building from source, with the R1 files, these dirty ports will take a hefty amount of time. I recommend building a device tree and start building with the kernels that either you have found, or have been created on this forum.
Click to expand...
Click to collapse
from my experience with porting , modding the updaterscript doesnt cause much threat since i remove any other potential threats to the device and of course i dont flash the boot.img that's for the other device....pretty much i modded the updaterscript just to that it flashes the rom to the right partitions for the device im flashing , yesterday was the first time i ported a kernel (boot.img-kernel) from another device's boot.img and it booted the R1, the only thing that did not work was the sim cards since the kernel was compiled with a different driver that was for the other device. it even added in the settings menu a fingerprint option (of course did not work) even tho the R1 does not have a fingerprint sensor. so my conclusion was that the other device is pretty much a clone of the R1 with a slight difference in some hardware , the purpose of the kernel port was to see if it will boot the r1 wich it did but more is the fact that the other device has a defconfig for a 64bit version as well wich the R1 does not and building a 64bit kernel for the r1 would allow me to port over so many more roms. I really wish the devs of this community would take interest in this because this would change the R1 alot.
KazuDante said:
from my experience with porting , modding the updaterscript doesnt cause much threat since i remove any other potential threats to the device and of course i dont flash the boot.img that's for the other device....pretty much i modded the updaterscript just to that it flashes the rom to the right partitions for the device im flashing , yesterday was the first time i ported a kernel (boot.img-kernel) from another device's boot.img and it booted the R1, the only thing that did not work was the sim cards since the kernel was compiled with a different driver that was for the other device. it even added in the settings menu a fingerprint option (of course did not work) even tho the R1 does not have a fingerprint sensor. so my conclusion was that the other device is pretty much a clone of the R1 with a slight difference in some hardware , the purpose of the kernel port was to see if it will boot the r1 wich it did but more is the fact that the other device has a defconfig for a 64bit version as well wich the R1 does not and building a 64bit kernel for the r1 would allow me to port over so many more roms. I really wish the devs of this community would take interest in this because this would change the R1 alot.
Click to expand...
Click to collapse
C,Mon Devs
F2FS?
KazuDante said:
Ive Been looking around to find new roms that i could port to the R1HD. Ive ported about 5-8 roms that work on the R1 HD but only 2 works flawlessly but the others have a camera issue ( camera not connecting ).
Now ive found a x32-bit CM14.1 for the MT6735 , that works on the device that it was built for. Of course I quickly went to attempt to port it but no luck as of now. The issue seems to be that the /system partition is not mounted correctly in regards to our boot image .
Here are the links for those who want to look at it with us ( R1 HD's Round Table )
Where i saw the post : https://vk.com/smart_rom (scroll down a little bit and you guys will see cm14.1 mt6735, they even made a 64bit now)
Where the test builds are posted and also the sources : https://github.com/olegsvs/android_device_archos_persimmon/releases (now they are testing Resuretion Remix 5.8.XX)
It just to prove that MT6735 can also be running Android 7 as well.
As a team we can make this happen and bring new life to the R1 HD.
Update : Now a Resurection Remix 5.8 is also running on the MT6735 x32. ---> https://vk.com/wall-77256552_14248
Update 2 : here is the boot image i used to get the CM14 system partition to be up and allowed me to use a few adb/shell commands ,this by any mean does not mean that CM14.1 booted properly , theres alot of issues , i could not as of now even get the boot animation to load . this is purely experimental. : https://drive.google.com/file/d/0BzU6b7lzLmttSThpX3ctbHNkcFU/view?usp=sharing
And heres the CM14 i downloaded and tested it : https://github.com/DeckerSU/android_device_smart_surf2_4g/releases/tag/0.2alpha
Also of other dev out there are going to take a crack at it the initial updaterscript wasnt correct so replace it with this updaterscript : https://drive.google.com/file/d/0BzU6b7lzLmttVVh0NUQxWjRNODg/view?usp=sharing
this is yet another step foward for R1 HD.
P.S THIS DOES NOT BOOT , DONT FLASH IT IF YOU DONT KNOW WHAT YOU ARE DOING, I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY OCCUR. YOU HAVE BEEN WARNED . (4DEV ONLY NOT USERS)
Click to expand...
Click to collapse
Why not create Support for F2FS IN DATA PARTITION
This Will increase perfomance a Lot AND running cm14.1 64bits
This device Will fly!!!
khyr said:
Why not create Support for F2FS IN DATA PARTITION
This Will increase perfomance a Lot AND running cm14.1 64bits
This device Will fly!!!
Click to expand...
Click to collapse
for that we first need x64 kernel and x64 twrp....thats if R1 bootloader allows x64 kernels
KazuDante said:
for that we first need x64 kernel and x64 twrp....thats if R1 bootloader allows x64 kernels
Click to expand...
Click to collapse
What about F2FS ?
IT IS POSSIBLE TO GET IT?
khyr said:
What about F2FS ?
IT IS POSSIBLE TO GET IT?
Click to expand...
Click to collapse
Unless we can actually compile a fully working rom for the R1 , for f2fs to properly work both rom and kernel has to support it..that also includes the twrp.
As of now we still can't figure out whats missing that's stopping a compiled rom for our device (ex. cm13 from @vampirefo and @bullet25 )to boot.
Damn! What do you think about Lenovo k80m
4GB ram 64G storage
Intel Atom procesador it Is worth it Upgrade from Blu R1 this Phone Is stock in kit kat 4.4.4
http://m.gsmarena.com/lenovo_k80-7216.php
I know this Is a off topic question
But Is just $139 AND you got 64GB of storage AND 4G ram
The zenfone 2 4GB RAM it Is in the same pricetag but Is only 16GB storage

Question Where to start building a working twrp and/or roms for moto g power 2021 (borneo)?

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

Categories

Resources