Related
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
Heavily based on the WIP LineageOS port for the Moto E4 (Qualcomm) [perry] -- for more information about that, click here.
Known working:
Booting
Connecting to Sprint's 1xRTT network (2G data, voice, SMS)
Fingerprint sensor
WiFi
Broken:
Sound
Sprint 3G data and LTE (need to add in Sprint network blobs)
XDA:DevDB Information
LineageOS 14.1 for Moto E4 Plus (Qualcomm), ROM for the Moto E4 Plus
Contributors
ReimuHakurei, squid2, Alberto97
Source Code: https://github.com/ReimuHakurei/android_device_motorola_owens
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Based On: LineageOS
Version Information
Status: Alpha
Created 2017-10-31
Last Updated 2017-10-31
Uploaded another build that seems to get LTE on Sprint. All of the menus are still broken so you presumably need to be activated on stock before flashing.
Is there any way to make the fingerprint function to wake up / close screen to work with out requiring a pin/pattern/code to be active? That'd be an awesome feature
Installed on my XT1775 briefly and except for the sound this looks pretty good. I'm on AT&T and LTE worked fine, etc. I just can't live without sound as I need my phone for work teleconferences. I will *definitely* use this as soon as I can daily drive it!
I have tried (and failed) to get CDMA data properly working. Once someone gets CDMA/Sprint support working properly on one of the other devices in this family, it should be simple enough to port whatever the fix may be, but until that happens, this will likely remain as-is.
Since gsm seems to get LTE will this ROM still be worked on to get sound working? Even though I know CDMA users are out of luck for now. I have the standard e4 and want to buy a plus but I definitely need aosp ROMs.
Thanks for your work porting this. Actually shocked to not see more development considering how huge the battery is on the device.
fix-this! said:
Since gsm seems to get LTE will this ROM still be worked on to get sound working? Even though I know CDMA users are out of luck for now. I have the standard e4 and want to buy a plus but I definitely need aosp ROMs.
Thanks for your work porting this. Actually shocked to not see more development considering how huge the battery is on the device.
Click to expand...
Click to collapse
I need to repair my shattered Moto X Pure so I have a working phone to use while developing before I can do much more work here (ie: on fixing audio). This was mainly a proof-of-concept to make sure I was, in fact, able to get the thing to boot, before I spent too much work fixing other things.
For CDMA, I think the root of it is the new architecture Sprint is using in preparation for CDMA+VoLTE; I tried porting over files from the Moto X Pure's LineageOS port, but it uses older tech for CDMA internally. The Moto G5S has the same ISIMv2 SIM card on Sprint so should be similar software-side, and the Moto G5S will almost certainly have a pretty active community judging from past Moto G series phones. Moto X4 should be similar as well.
I am likely to be pretty busy for the next month or so, though, so probably won't have time to do any work on this until then.
so does someone plan to pick back up development on this? really surprised there isnt more devs on the plus model. much better build, camera, cpu and that big ?.
What exactly did you have to do to get this to work. I'm considering trying to port a few roms from perry over to owens, but if it's too hard, or just practically impossible I'm not going to bother.
Which version seems to have LTE working? I currently have no LTE just call(no sound) and txt lol
So I am attempting to build my first rom for the Moto e4 plus Qualcomm. I'm just following the build instructions on lineageos's website. I'm stuck now because there is not a device tree in the lineageos git. I see that the OP has a device tree on git and I also see that there is now a Moto kernel on git. I am unsure what the next step is? I'm unsure how to make the device tree part of my local git and also how to mix the new kernel posted from Moto. Any help and I will post what I create. Thanks.
@ReimuHakurei would you please attempt to fix sound for this custom ROM now that the kernel sources have been released. I've been looking forward to replacing the stock room on my phone for a while
FlagersXDA said:
@ReimuHakurei would you please attempt to fix sound for this custom ROM now that the kernel sources have been released. I've been looking forward to replacing the stock room on my phone for a while
Click to expand...
Click to collapse
Yes please! I really want to use this rom but I use my phone for listening to music all the time. Will some please fix the sound?
Bump, can someone please fix this?
Thank you for releasing this!
+1 for no sound or mic on xt1775
I tried Bluetooth and wired audio devices and sound/mic is not functioning for them either.
I am able to connect to the Verizon network with a their Sim through net 10, but only 3g (EvDo-rev.A, by choosing global auto) and not LTE after trying various modes in the 4636 menu. With the same Verizon Sim through net 10 my Nexus 5x h791 does connect to LTE .
Besides the issues above, this appears to be working well!
Also, if anyone can share complete stock partition images files (boot, recovery, and system partitions) for the xt1775, this would be appreciated, but I'm ok using my phone as is for now. I wish I had thought to make a complete backup by booting twrp through fastboot (fastboot boot recoverimagefilenamehere.img) and then making a backup first instead of flashing twrp before doing that. After I flashed twrp, instead of the Motorola bootloader unlocked screen, all I see is the white text "N/A" on a black background in the top left corner during bootup. Also, after I installed twrp I could no longer boot to the os until I installed this unofficial lineageos rom. I'm not sure if that is expected. Since I didn't make a backup of the system partition and boot before flashing twrp, I'm unable to restore the stock os. Lesson learned... immediately after making the mistake. I did make a backup of the boot and system partitions after flashing twrp before installing this unofficial lineageos rom(when I was already having the boot up issue), but when I restore them I have the same issue where the phone will not boot into the os. This is what I expected, at that point anyways.
Thanks again!
For Mediatek Variant
Sir,Any custom rom for Mediatek variant of this handset
fllannell said:
Also, if anyone can share complete stock partition images files (boot, recovery, and system partitions) for the xt1775, this would be appreciated, but I'm ok using my phone as is for now. I wish I had thought to make a complete backup by booting twrp through fastboot (fastboot boot recoverimagefilenamehere.img) and then making a backup first instead of flashing twrp before doing that.
Click to expand...
Click to collapse
I'm not sure if its the exact same variant, but @_maerk released stock images for the retail (snapdragon) e4 plus. Even if yours is carrier specific, as long as your bootloader is unlocked and you have the Qualcomm version you should still be good. I remember on my old Sprint Moto E from 2015 I could still flash the OS/Recovery/Boot images from the retail version, just not the modems or bootloader.
Update: I was able to restore to stock using the following link.
SCROLL TO POST # 10 for directions for Moto E4 Qualcomm (Owens) retail unlocked:
https://forum.xda-developers.com/moto-e4-plus/how-to/moto-e4-qualcomm-owens-completely-to-t3743441
Then I flashed Reiku's version of TWRP for the phone:
https://forum.xda-developers.com/moto-e4-plus/development/twrp-twrp-moto-e4-plus-qualcomm-t3697154
Then I installed this unofficial Lineage version:
[ROM][UNOFFICIAL][owens] LineageOS 14.1 for Moto E4 Plus (Qualcomm)
https://forum.xda-developers.com/mo...lineageos-14-1-moto-e4-plus-qualcomm-t3734197
Then I installed OpenGAPPs and AddonSu. The only hiccup I had through the process was that I got an ERROR Code: 64 when trying to install the ARM 64 version of openGapps in TWRP, so I used a non 64 version without issue.
Thanks to everyone for all of your efforts on these projects.
Hello,
I have redmi note 4 3GB variant, rooted with miui 9.5.11.0
I wanted to try out a stable custom rom, I'm leaning towards resurrection rom and lineage os, can you guys tell me which versions of those are stable enough for me to try?
And, what is the most hassle free and simplest way to back up and restore data.
In other words, how to easily switch from stock rom to custom rom (or vice versa) without loosing user data?
Los is good but if u are fan of customisation Then RR is good also Aosp Extended is good option, u can restore your old backup and its very easy just make backup of your current rom and flash the custom rom.
jime1 said:
Hello,
I have redmi note 4 3GB variant, rooted with miui 9.5.11.0
I wanted to try out a stable custom rom, I'm leaning towards resurrection rom and lineage os, can you guys tell me which versions of those are stable enough for me to try?
And, what is the most hassle free and simplest way to back up and restore data.
In other words, how to easily switch from stock rom to custom rom (or vice versa) without loosing user data?
Click to expand...
Click to collapse
It doesn't get more stable than LineageOS.
But the price you pay is that there aren't any customizations or features. Currently it's basically pure Android
I'm using Miracle droid for 6 months now since i dont need treble at the moment or until magisk has official treble support.
Many customization option and no bug so far.
rs168 said:
I'm using Miracle droid for 6 months now since i dont need treble at the moment or until magisk has official treble support.
Many customization option and no bug so far.
Click to expand...
Click to collapse
How can you use the ROM for 6 months when it was released only 2 months ago?
Noter2017 said:
How can you use the ROM for 6 months when it was released only 2 months ago?
Click to expand...
Click to collapse
OMG ! Did we just spot a time traveler ?
jbanti said:
Los is good but if u are fan of customisation Then RR is good also Aosp Extended is good option, u can restore your old backup and its very easy just make backup of your current rom and flash the custom rom.
Click to expand...
Click to collapse
Alright Man ! Great !! is there any side by side comparison for those three ?
And I'm rooted with Magisk, with stock recovery so that I can receive OTA MIUI stable updates..So are you talking about Titanium Backup or TWRP backup or the in house Local Backups ?
Noter2017 said:
It doesn't get more stable than LineageOS.
But the price you pay is that there aren't any customizations or features. Currently it's basically pure Android
Click to expand...
Click to collapse
So, is the latest Lin OS version the most stable ? and what features does it have, is there any kind of list of features ?
rs168 said:
I'm using Miracle droid for 6 months now since i dont need treble at the moment or until magisk has official treble support.
Many customization option and no bug so far.
Click to expand...
Click to collapse
How is it better than RR and Lin OS ?
Noter2017 said:
How can you use the ROM for 6 months when it was released only 2 months ago?
Click to expand...
Click to collapse
Oh right it sounds weird LOL !!!
The previous release was Elixir OS, developer change the name to Miracle OS.
https://forum.xda-developers.com/re...opment/elixiros-1-0-mw-redmi-note-4x-t3733603
---------- Post added at 08:00 AM ---------- Previous post was at 07:57 AM ----------
jime1 said:
How is it better than RR and Lin OS ?
Click to expand...
Click to collapse
I prefer customization, not pure android.
At least for me, Miracle has better batter life. i love RR since Galaxy S2
oh by the way RR nougat is the best battery life so far.
I use RR Luis ROM, 5..8.5 version, which is for Nougat. Battery life is excellent, lots of customizations, and very stable.
Try the Lineage Extended by Alexey. Its not here in XDA, but search Alexey711 in androidfilehost. Thats the perefect version of Lineage based ROM I've found. Lots of customization plus regular updates.
Alexey build in lineage is the best , he update daily I think:silly: almost all customization in resurrection are available in it
If you want to try resurrection go for endless, his battery life is outstanding, he also update with useful features
rs168 said:
Oh right it sounds weird LOL !!!
The previous release was Elixir OS, developer change the name to Miracle OS.
https://forum.xda-developers.com/re...opment/elixiros-1-0-mw-redmi-note-4x-t3733603
---------- Post added at 08:00 AM ---------- Previous post was at 07:57 AM ----------
I prefer customization, not pure android.
At least for me, Miracle has better batter life. i love RR since Galaxy S2
oh by the way RR nougat is the best battery life so far.
Click to expand...
Click to collapse
rossarnie said:
I use RR Luis ROM, 5..8.5 version, which is for Nougat. Battery life is excellent, lots of customizations, and very stable.
Click to expand...
Click to collapse
So the RROreo is not good at battery life ?
iTalisman said:
Try the Lineage Extended by Alexey. Its not here in XDA, but search Alexey711 in androidfilehost. Thats the perefect version of Lineage based ROM I've found. Lots of customization plus regular updates.
Click to expand...
Click to collapse
naseefnachi said:
Alexey build in lineage is the best , he update daily I think:silly: almost all customization in resurrection are available in it
If you want to try resurrection go for endless, his battery life is outstanding, he also update with useful features
Click to expand...
Click to collapse
You mean this : https://androidfilehost.com/?w=files&flid=256804 ?
if Alexey711 is so awesome, then why is he/she not on xda ? why release ROMs such top secretly ?!
and endless ? is that a custom version of RR ?
and why prefer some secret ROM(Alexey build) over RR ?
Who said he release secretly?? He is in PDA forum ,his thread is there.
p3dboard said:
This is not my Rom - this is just a Forum for discussion on XDA - the main forum is the 4pda.ru site
LineageOS 15.1 eXtended
4pda.ru - Original Rom Thread - https://4pda.ru/forum/index.php?showtopic=809215&view=findpost&p=72074026
Rom download - https://androidfilehost.com/?w=files&flid=256804
Change Log - https://pastebin.com/raw/zEH3kdjK
Youtube Review of differences from LineageOS withe LOS eXtended
LineageOS eXtended is a free, community built, aftermarket firmware distribution of Android 8 (oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS eXtended is based on LineageOS and 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 eXtended does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS eXtended is available in the LineageOS eXtended Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Source Code:
https://github.com/LineageOS-eXtended
https://github.com/Alexey71
What's working :
Boots
RIL (Calls, SMS, Data)
Fingerprint
IR Blaster
Wi-Fi
Bluetooth
Camera
Camcorder (Supports up to 60fps via GCAM in bright light)
Video Playback
Audio
Sensors
Flash
LED (if your notification LED isn't working, use the old LED driver .zip - my Mido needs this)
GPS
Volte
ViLte (Has been fixed since the youtube video was made)
Known issues:
You Tell me
FAQ: (Google Translation of Russian Forum FAQ)
Answers to questions or FAQ:
* What kind of archive is OLD_LED_DRIVER_PATCH?
lineage-15.1-xxxxxxxxx-Extended-mido.zip - the firmware itself with a new ice driver for the diode of notifications. Not everyone works, thanks Xiaomi. (Check the diode flashing when notifications arrive and how it is configured).
lineage-15.1-xxxxxxxxx-Extended-mido (OLD_LED_DRIVER_PATCH) .zip - since not everyone has a new diode driver, they made a patch for the old one.
* The first time the firmware is installed, crashes the setting.
Delete the SetupWizard in GAPPS
* There is no "for program" option on LOS in the superuser settings, there is only "ADB". How do I enable root for programs?
Route of access is not present, it is necessary to flash Magisk treble or LineageOS extension https://download.lineageos.org/extras
Instructions :
Download the latest Rom build - https://androidfilehost.com/?w=files&flid=256804 - and GApps - https://opengapps.org/
Reboot to recovery
Flash the latest build and GApps
Reboot
Downloads :
Recovery & Magisk
Twrp for Treble builds (will work with normal builds too) - RedWolf TWRP 027
Custom Magisk for treble enabled builds v16.4
Rom
Un-Official build [Nightlies]: https://androidfilehost.com/?w=files&flid=256804
Extra Camera's
MIUI Camera (For Slow Motion Video Capture)
GCam (UriKill Version) - For better HDR+ photo capture
Newer Urikill version with FC fix
Credits :
Alexey711 - Rom Compiler / Developer
Alexey711 - Profile on 4pda.ru
Contributors
alexey71
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: Miui 9 8.5.x or later
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: https://androidfilehost.com/?w=files&flid=256804
Beta Release Date: 2018-06-18
Created 2018-05-07
Last Updated 2018-06-19
Click to expand...
Click to collapse
jime1 said:
So the RROreo is not good at battery life ?
Click to expand...
Click to collapse
Nougat battery life is better than Oreo.
rossarnie said:
Nougat battery life is better than Oreo.
Click to expand...
Click to collapse
Alright, but I'm unable to find the older versions on Sourceforge, here are only Oreo versions
I never knew there were other android forums such as XDA in this world, damn
jime1 said:
Alright Man ! Great !! is there any side by side comparison for those three ?
And I'm rooted with Magisk, with stock recovery so that I can receive OTA MIUI stable updates..So are you talking about Titanium Backup or TWRP backup or the in house Local Backups ?
Click to expand...
Click to collapse
check out the official rom forum page for more info...
AOSP 12.0 GSI - G6 ALIHello friends, how are you? I was pretty tired of the traditional roms we have for the Moto G6 there, (I got sick), these roms are excellent, but with time it ended up being more the same, that's when phhusson released an Android 12 GSI, I went to test it and found it amazing the operation on the system, unfortunately there is no way to use the SIM, but some improvements are even nice, I'm starting in this area of customization of the latest ROMs (current android)
You need a recovery that accepts ARM64 ROMs, and the GSI itself
In the link you select system-squeak-arm64-ab-vanilla.img.xz and download, then unzip and install on your system and test
GSI:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Depending on when you are watching this post the performance is already better, however I made this post to motivate the community (us) to try to port ROMs and GSIs for the Moto G6 ALI.
For those who are having doubts a while ago I made a video installing the TWRP with the GSI of Android 11 on the Moto G6 ALI, I recommend you check it out if you have any questions!
(The video is in Brazilian Portuguese my native language)
How were you able to get an a/b partition GSI to boot properly on an A-only partition device like the Moto G6?. I've used A-only GSIs successfully on mine in the past but my understanding is A-only has been discontinued with release of a12.
I don't know man, but I just installed it, in the application that sees which system it is if it's AB or A only says it's AB, if I'm not mistaken I've already tested A only roms for it but it didn't work for some reason, I don't know if it's the current Vendor of the custom Roms I'm using or something else, I think it's the vendor since it's not an ARM32 but an ARM64, it can also be for recovery. In short, I don't know.
but it works
Don't know why an a/b gsi works on an a-only device but it does. Give this a12 gsi a try OctaviOS-v3.2-arm64_bvN-29122021-Unofficial.img.xz. It booted and I got an LTE signal no problem.
doesn't work for me
tried both 64 and 32, i'm using twrp 3.6.0_9-0 though, not sure if that is the problem, rolling back to 11 for now.
You might to flash permissive v4 before first boot after flashing the gsi image. https://androidfilehost.com/?w=search&s=Permissiver
Skippy12359 said:
You might to flash permissive v4 before first boot after flashing the gsi image. https://androidfilehost.com/?w=search&s=Permissiver
Click to expand...
Click to collapse
Nope, still gets a boot loop into the bootloader, i'll give it another try though
adhamnasr said:
Nope, still gets a boot loop into the bootloader, i'll give it another try though
Click to expand...
Click to collapse
Try man, because it's worth testing and seeing the Moto G6 ALI running Android 12, pretty cool
HeroRicky_Games09 said:
Try man, because it's worth testing and seeing the Moto G6 ALI running Android 12, pretty cool
Click to expand...
Click to collapse
i am, but maybe i'm doing something wrong
do you guys push the img and install using twrp or sideload?
edit: i reflashed it to stock, and gonna repeat the process
I didn't use stock boot or vendor when Octavia gsi booted for me. I was on the latest Ali Crdroid11 Dec patch, backed it up in latest twrp, did a normal wipe and flashed the vanilla Octavia arm64 a/b system gsi link above. Don't recall if it booted right away or if I went back to twrp and flashed permissiver v4. Either way it booted fine, got carrier signal right away (t- mobile) , sound also worked fine. Didn't flash gapps or anything else. Just was curious if an a/b gsi would actually boot on a G6 and both Aosp12 and Octavia both did for me. Try this permissive zip if the other doesn't work https://androidfilehost.com/?fid=6006931924117886495
Did a little research on telegram and found out a12 a/b gsi's will also work on an a-only device as long as the device supports SAR (system as root). Treble check app shows the G6 supports SAR and is arm64 so that's likely why they boot OK for some of us. That said the two I've tried Aosp12 and Octavia12 were laggy and would hang occasionally.
For those who are having doubts a while ago I made a video installing the TWRP with the GSI of Android 11 on the Moto G6 ALI, I recommend you check it out if you have any questions!
(The video is in Brazilian Portuguese my native language)
I can't believe it, but I made it work...
adhamnasr said:
I can't believe it, but I made it work...
Click to expand...
Click to collapse
The cool thing about this GSI is that it runs without lags, the only problem is the mobile data. if it worked it would be perfect
HeroRicky_Games09 said:
AOSP 12.0 GSI - G6 ALIHello friends, how are you? I was pretty tired of the traditional roms we have for the Moto G6 there, (I got sick), these roms are excellent, but with time it ended up being more the same, that's when phhusson released an Android 12 GSI, I went to test it and found it amazing the operation on the system, unfortunately there is no way to use the SIM, but some improvements are even nice, I'm starting in this area of customization of the latest ROMs (current android)
You need a recovery that accepts ARM64 ROMs, and the GSI itself
In the link you select system-squeak-arm64-ab-vanilla.img.xz and download, then unzip and install on your system and test
GSI:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Depending on when you are watching this post the performance is already better, however I made this post to motivate the community (us) to try to port ROMs and GSIs for the Moto G6 ALI.
For those who are having doubts a while ago I made a video installing the TWRP with the GSI of Android 11 on the Moto G6 ALI, I recommend you check it out if you have any questions!
(The video is in Brazilian Portuguese my native language)
Click to expand...
Click to collapse
I made a video installing this GSI on it, go there and check it out! It is in Portuguese Brazil.
Will it work on moto g6 play Jeter 3gb ram 64 bit cpu snapdragon 430 currently on Android 11 pixel experience
Nikhil15 said:
Will it work on moto g6 play Jeter 3gb ram 64 bit cpu snapdragon 430 currently on Android 11 pixel experience
Click to expand...
Click to collapse
possibly yes!
Can you tell the steps of installation because I don't understand brazilian
And please tell about bugs of anything
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