[ROM][UNOFFICIAL]LineageOS-16.0[Evert][Moto G6 Plus] - Moto G6 Plus ROMs, Kernels, Recoveries, & Other De

[ROM][UNOFFICIAL]LineageOS-16.0[Evert][Moto G6 Plus] - Moto G6 Plus ROMs, Kernels, Recoveries, & Other De

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LIneageOS is a free, community built, after-market firmware distribution of Android re-branded CyanogeMod, 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.
*/
LineageOS is based on the Android Open Source Project and CyanogenMod with extra contributions from many people within the Android community. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS please visit Gerrit Code Review.
Warning!!!
BackUp EFS partition before installing. .If you lose IMEI , use this backup to retrieve it in future.
Installation
Boot the newest TWRP .img
Flash copy-partitions-AB.zip from second post. (This will prevent device from getting bricked if you are coming from stock rom for the first time. It takes a backup of active slot to inactive slot)
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest build
Reboot to fastboot and do fastboot -w via terminal
Boot into "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps - Only MindTheGApps arm64 are compatible, OpenGApps are not compatible with A/B yet: MindTheGApps.
(Optionally) Flash SU - you'll need to turn it on from in developer settings after first boot Lineage OS SU Addon. - Magisk works fine, though is not supported.
Reboot
Downloads
Warning
If you are coming from stock ROM and it's your first time flashing lineage, flash copy-partition zip (See second post) unless your device will brick and I'm not responsible
- LineageOS : Unoffical Builds
- TWRP : Get here
Bugs
You tell me
Reporting bugs
DO NOT report bugs if you're running a custom kernel
DO NOT report bugs if you've modifies system files
DO NOT report bugs if you've installed xposed and/or other mods
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
Code:
adb logcat > logcat.txt
Code:
adb shell dmesg > dmesg.txt
If it is a random reboot, grab kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Code:
adb shell cat /sys/fs/pstore/console-ramoops
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues or bugs reported in the lastest 5 pages of this thread. Any bug not reported in the bug report format below may be ignored.
Code:
Phone Informations
* LineageOS version
* Gapps version
What you did:
* Wipe data: y/n
* Upgrade from previous official cm build: y/n
* Restore with titanium backup: y/n
You're using (if yes write which one) :
* Task killer
* Phone cleaner / Battery enhancer apps
* Non-stock kernel
* Modified kernel settings
* Other mods
Bug info:
* Last version it worked on
* Repro steps
F.A.Q.
ROOT! ROOT! Give me root or i'll die!!! Where root is???
First of all DO NOT flash any SuperSu/SuperUser/SuperMan zip package to get root. Go to Settings>Developement Settings>Root access and select "Apps Only"
Why no nightly today?
Build failed. Check again tomorrow
When do I have to wipe data?
You must wipe data only when you're switching from another rom or migrating to Snapshot branch from Nightly and vice versa. You don't need to wipe data when you update in the same release channe (this applies to 13.0 -> 14.1 upgrades too)
Will you add <insert awesome feature here>?
I won't. If you write it, submit a commit to gerrit, where it will be reviewed.
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Kernel Source : Here
XDA:DevDB Information
LineageOS, ROM for the Moto G6 Plus
Contributors
rahulsnair, erfanoabdi
Source Code: https://github.com/LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP
Based On: LineageOS
Version Information
Status: Stable
Created 2018-10-22
Last Updated 2018-12-28

Copy Partition- Initial Setup
Flash the attachement via TWRP

Fantastic, can't wait to try this! :good: The copy-partition zip seems to be missing though? :crying:

Awesome! Thank you, can't wait to try it out.
Is the copy partitions zip the same as the one on the Lineage OS 15.1 thread?

Daniel47833 said:
Awesome! Thank you, can't wait to try it out.
Is the copy partitions zip the same as the one on the Lineage OS 15.1 thread?
Click to expand...
Click to collapse
Yes.

"Pixel setup keeps stopping" after flashing Mindthegapps. Which version exactly, am I supposed to use?

Mara-X said:
"Pixel setup keeps stopping" after flashing Mindthegapps. Which version exactly, am I supposed to use?
Click to expand...
Click to collapse
When that app stop working select app info, force stop and clear app data.
And try again it'll work
And when you want to restore your stuff it'll show another error: "data transfer stop working" (I don't remember exact name) do the same force stop and clear data but this time allow all the permissions (storage, calls, etc)
Sent from my g(6) plus using XDA Labs

RokCruz said:
When that app stop working select app info, force stop and clear app data.
And try again it'll work
And when you want to restore your stuff it'll show another error: "data transfer stop working" (I don't remember exact name) do the same force stop and clear data but this time allow all the permissions (storage, calls, etc)
Sent from my g(6) plus using XDA Labs
Click to expand...
Click to collapse
Hmm. Clear data is greyed out, can only clear cache and that doesn't help.

Mara-X said:
Hmm. Clear data is greyed out, can only clear cache and that doesn't help.
Click to expand...
Click to collapse
Try with opengapps nano package
Sent from my g(6) plus using XDA Labs

Mara-X said:
Hmm. Clear data is greyed out, can only clear cache and that doesn't help.
Click to expand...
Click to collapse
? The data transfer tool and Pixel set up both require notification access. Should solve the issue. ??

ksk35695 said:
The data transfer tool and Pixel set up both require notification access. Should solve the issue.
Click to expand...
Click to collapse
Hello, how can I give notification access to the pixel set up? I can't find the option


Daniel47833 said:
Hello, how can I give notification access to the pixel set up? I can't find the option
Click to expand...
Click to collapse
Goto Apps & notifications, scroll down to Special app access, There's the noticfication access around the middle of the list.
Always has worked for me in this senario. Good luck.

Nice work! Congratulations @rahulsnair + everybody on the team. Wow, did You receive the device on Monday this week?
So, I flashed and I'm writing the journey here and keep editing as I go:
- Is Emergency calling working, can you connect? You can test by calling there and saying that you wanted to test.
- Moto actions - Working!
- Is the camera quality the same-ish? I'd say yes.
- Can I install Moto Camera 2 (Stock)? Yes.
- Tethering (yes) / Hotspot (working) / Bluetooth calling (working) / Casting (working) / NFC (working).
- Since "Copy A -> B Partitions zip" makes a copy of the current ROM to another slot (correct?), how to restore from there? I know how to restore from twrp backup.
[STROKE] EDIT: At the moment I'm getting "Pixel Setup keeps stopping" Cleared cache. Did not help. I have no navbar. For some reason Gapps didn't flash correctly I think. Trying again from there.[/STROKE]
EDIT2: You have the wrong link in OP. It points to 8.x MindTheGapps
Here's the 9.x version:
https://androidfilehost.com/?w=file...0cea2c259bd6b42b84ebd97a7d581187be08d20207d94
The same error manifests in 9.0 MindTheGapps. I got a little further though. But it's possible to plough through. Just reboot if you get stuck like I did and you will get there.
* Still no navbar during setup. (This might possibly be remedied by enabling on-screen navbar before flashing gapps, maybe: "settings -> system -> buttons).
* When connecting to wifi at setup, it will connect, but nothing happens, no "next" button"
* Not able to skip restoring backup from Google account.
* Data Migration Tool shows that its pixel version. Give permissions by clicking "App Info", "Permissions", check all.
* I have a strong feeling I have flashed MindTheGapps for Pixel :silly::highfive::laugh:
Wohoo! Made it through the setup, and I have a NavBar! And a working ROM! Super! (Some time later) - It's an awesome smooth driver. Absolutely beautiful.
* TWRP is suddenly showing garbled folders in sdcard. There was a post about that... Lemme see -- Ok so the problem is force_encryption. For that I'd need help, how to change that?
* Computer does not see external sd anymore
* Integrated E-mail app couldn't log to Gmail
* Music player didn't see external SD - fixed by magisk module "ExSdcard Access Enabler".
* Audio Fx didn't change anything - there's a fix to try clearing the data and cache and see if it starts working - I installed Viper4Android FX through Magisk Manager, works.

weazie said:
Nice work! Congratulations @rahulsnair + everybody on the team. Wow, did You receive the device on Monday this week?
So, I flashed and I'm writing the journey here and keep editing as I go:
- Is Emergency calling working, can you connect? You can test by calling there and saying that you wanted to test.
- Moto actions - Working!
- Is the camera quality the same-ish? I'd say yes.
- Can I install Moto Camera 2 (Stock)? Yes.
- Tethering (yes) / Hotspot (working) / Bluetooth calling (working) / Casting (working) / NFC (working).
- Since "Copy A -> B Partitions zip" makes a copy of the current ROM to another slot (correct?), how to restore from there? I know how to restore from twrp backup.
[STROKE] EDIT: At the moment I'm getting "Pixel Setup keeps stopping" Cleared cache. Did not help. I have no navbar. For some reason Gapps didn't flash correctly I think. Trying again from there.[/STROKE]
EDIT2: You have the wrong link in OP. It points to 8.x MindTheGapps
Here's the 9.x version:
https://androidfilehost.com/?w=file...0cea2c259bd6b42b84ebd97a7d581187be08d20207d94
The same error manifests in 9.0 MindTheGapps. I got a little further though. But it's possible to plough through. Just reboot if you get stuck like I did and you will get there.
* Still no navbar during setup. (This might possibly be remedied by enabling on-screen navbar before flashing gapps, maybe: "settings -> system -> buttons).
* When connecting to wifi at setup, it will connect, but nothing happens, no "next" button"
* Not able to skip restoring backup from Google account.
* Data Migration Tool shows that its pixel version. Give permissions by clicking "App Info", "Permissions", check all.
* I have a strong feeling I have flashed MindTheGapps for Pixel :silly::highfive::laugh:
Wohoo! Made it through the setup, and I have a NavBar! And a working ROM! Super! (Some time later) - It's an awesome smooth driver. Absolutely beautiful.
* TWRP is suddenly showing garbled folders in sdcard. There was a post about that... Lemme see -- Ok so the problem is force_encryption. For that I'd need help, how to change that?
* Computer does not see external sd anymore
* Integrated E-mail app couldn't log to Gmail
* Music player didn't see external SD - fixed by magisk module "ExSdcard Access Enabler".
* Audio Fx didn't change anything - there's a fix to try clearing the data and cache and see if it starts working - I installed Viper4Android FX through Magisk Manager, works.
Click to expand...
Click to collapse
I'm not going to test emergency services.
Moto actions do work-and this is why you don't see a navbar on setup. Fingerprint gestures, swipe right to left to go back,tap for home, left to right for recent, long press for assistant.
Copy partions- this should let you dual boot roms. So los15.1 on slot a and slot b can have Los16. The twrp reboot screen can allow you to choose your boot slot.
Gapps-you can use any gapps really just be sure to flash them if you flash a rom update. I like opengapps arm64 nano builds myself. Then install Google apps from play store.
Twrp- we have to wait for devs to deal with this. It will be fixed in time if it's not fixed with the new official twrp(I haven't tested it yet). It only applies to internal storage. SD card won't be scrambled.
SD card-the mount point is wrong. I think it was /run/media/sdcard or something similar. Some apps can find the path and some can't.
Sent from my Moto G6 Plus using XDA Labs

Xplorer4x4 said:
Moto actions do work-and this is why you don't see a navbar on setup.
SD card-the mount point is wrong. I think it was /run/media/sdcard or something similar. Some apps can find the path and some can't.
Click to expand...
Click to collapse
Great, thanks for clarifying
My post above is written as I go through the setup, therefore a mess.
External SD resides at /mnt/media_rw/(sd_card_name).
Easiest way to fix (most apps) to recognize it is to load ExSdCard Access Enabler module in Magisk Manager.

Just to clear up something the reason mavnar isn't shown is you need to use fingerprint gestures. Swipe left to right for recent, tap for home, swipe left to right to go back. Then you can activate navbar in settings after set up.
Sent from my Moto G6 Plus using XDA Labs

weazie said:
Easiest way to fix (most apps) to recognize it is to load ExSdCard Access Enabler module in Magisk Manager.
Click to expand...
Click to collapse
This method unfortunately doesn't work in Lightroom. "Use SD Card" in "Device Info & Storage" is still grayed out.

Alpetrus said:
This method unfortunately doesn't work in Lightroom. "Use SD Card" in "Device Info & Storage" is still grayed out.
Click to expand...
Click to collapse
yes, it seems so. I asked this question in Adobe Support, but didn't get a satisfactory answer.

Is anyone else having a problem enabling the microphone in Gboard? It's not a big issue as I'm able to switch to Google Voice typing on the fly. I was just wondering if it's something I did, or if it is something with this ROM.
For reference I installed Nano Gapps, and Gboard from the store.

DocFallingApart said:
Is anyone else having a problem enabling the microphone in Gboard? It's not a big issue as I'm able to switch to Google Voice typing on the fly. I was just wondering if it's something I did, or if it is something with this ROM.
For reference I installed Nano Gapps, and Gboard from the store.
Click to expand...
Click to collapse
Have you enabled microphone permissions from settings - apps?

Related

[ROM][6.0.1_r10][UNOFFICIAL] CyanogenMod 13.0 [2016-01-23]

Bug reports:
CyanogenMod 13 is in development and has several small bugs and missing translations. Complaints/demands/bug reports without logs will be ignored.
Explain how to reproduce the bug and attach logcat and dmesg (if you had a random reboot, also attach last_kmsg). If you don't know how to get those, you can use this app. Please, do not report bugs if you use any kind of mods (like xposed) or third party kernel.
Frequently Asked Questions:
Q) Will I get facebook/messenger app fc?
A) You shouldn't! Adreno blobs are now updated and now no dirty hacks required to boot up which in turn broke something.
Q) Where are Developer options?
A) Go to Settings > About phone, and press five times on Build number.
Q) How can I enable root access?
A) Go to Settings > Developer options > Root access, and enable it for apps, adb or both.
Q) I don't like superuser icon in statusbar, can I install SuperSU?
A) Ok yes, but read this. First enable root access from Developer options. Then flash SuperSU zip. Now open SuperSU app. It will say, 'SuperSU binary not installed'. So use TWRP/CWM method to install binaries. (This worked for me)
Q) How can I set 3G only network mode?
A)Method 1: Open Settings, Cellular Networks, now you can select LTE/3G/2G modes in 'Preferred network type' menu.
Method 2: Open dialer, dial *#*#4636#*#* , open first option "Phone Information", there you can set your preferred network mode.
Q) How do I update Gapps? (Also useful if you have Gapps related problems).
A) Reboot to recovery. Wipe System, Cache and Dalvik Cache. Install ROM + Gapps. (Yep, at a time) Reboot.

Reserved

Finally!! Great work

Solved : Gapps not able to flash
which gapps works best for this rom?arm,arm64 or x86.Im unable to flash open gapps.Please help.
Solved : Flashed ARM64-6.0-pico.Now it works great.Thanks developer for the wonderful ROM.Keep up your good work

Great Work!

Uc browser not working......

jayent said:
Uc browser not working......
Click to expand...
Click to collapse
Download UC Browser from here

please help
Hey I am facing problem while flashing thus ROM. Please help please

sahil314 said:
Hey I am facing problem while flashing thus ROM. Please help please
Click to expand...
Click to collapse
wipe/factory reset

Yash98 said:
wipe/factory reset
Click to expand...
Click to collapse
"GPS" not working.. phone getting restarted
---------- Post added at 04:59 AM ---------- Previous post was at 04:58 AM ----------
TheStrix said:
Bug reports:
CyanogenMod 13 is in development and has several small bugs and missing translations. Complaints/demands/bug reports without logs will be ignored.
Explain how to reproduce the bug and attach logcat and dmesg (if you had a random reboot, also attach last_kmsg). If you don't know how to get those, you can use this app. Please, do not report bugs if you use any kind of mods (like xposed) or third party kernel.
Frequently Asked Questions:
Q) Will I get facebook/messenger app fc?
A) You shouldn't! Adreno blobs are now updated and now no dirty hacks required to boot up which in turn broke something.
Q) Where are Developer options?
A) Go to Settings > About phone, and press five times on Build number.
Q) How can I enable root access?
A) Go to Settings > Developer options > Root access, and enable it for apps, adb or both.
Q) I don't like superuser icon in statusbar, can I install SuperSU?
A) Ok yes, but read this. First enable root access from Developer options. Then flash SuperSU zip. Now open SuperSU app. It will say, 'SuperSU binary not installed'. So use TWRP/CWM method to install binaries. (This worked for me)
Q) How can I set 3G only network mode?
A)Method 1: Open Settings, Cellular Networks, now you can select LTE/3G/2G modes in 'Preferred network type' menu.
Method 2: Open dialer, dial *#*#4636#*#* , open first option "Phone Information", there you can set your preferred network mode.
Q) How do I update Gapps? (Also useful if you have Gapps related problems).
A) Reboot to recovery. Wipe System, Cache and Dalvik Cache. Install ROM + Gapps. (Yep, at a time) Reboot.
Click to expand...
Click to collapse
"GPS" not working.. phone getting restarted

Update!
CyanogenMod 13.0 R2 Update:
Download: http://goo.gl/h7CkVJ
Changelog:
AOSP 6.0.1_r10 tag.
January 2016 security patches.
Fix offline charging issue (Screen didn't go completely off while offline charging earlier).
Fix Google+ app installation bug present in previous build.
Increased in-call volume speaker gain (reported by some users).
Updated build fingerprint from YU's latest COS release.
Some Wi-Fi updates.
Fix for external SD Card in CM file manager.
Replaced Toybox with Busybox (This may cause some root apps to crash, but CM now uses Toybox!).
Latest CyanogenMod sources with much new patches..

CyanogenMod 13.0 Jan 23rd update:
Download: https://www.androidfilehost.com/?fid=24385658843824514
Just don't hurry up. Read the whole post for once!
Changelog:
Support for F2FS for /data and /cache
Update audio configs to cope up with CyanogenMod's latest changes in audio HAL.
Switch to qcom libhealthd.msm standard library for offline charging (Also it shows battery % now while offline charge)
Switch to Snap camera
Enable USB MIDI support
RIL and connectivity updates
Update new regenerated blobs from crackling
CyanogenMod updates. (CM API v5, new wallpaper, etc. find out own ) [Many changes are made in CyanogenMod repo everyday, so of course can't list all]
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system initially developed by Samsung Electronics for the Linux kernel.
The motive for F2FS was to build a file system that from the start, takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Damn, that was just copy paste from wikipedia and I just didn't get it! So what is F2FS in our language?
It a better file system than ext4 in terms of performance.
Useful Link: http://www.xda-developers.com/f2fs-put-to-the-test-against-ext4/
To get a better idea, XDA forum have a dedicated thread highlighting F2FS features and a very detailed comparison between EXT4 (file system we use by default) and F2FS!
Have a look here: http://forum.xda-developers.com/showthread.php?t=2697069
So, I liked F2FS and wanna try it! But, how do I?
First of all, backup your internal SD Card as it will be wiped if you are switching to F2FS.
So, to start with, first you'll need a new recovery. I compiled modified TWRP recovery with F2FS support and some other cool features like pressing power button will now switch device display off, also wiping the partitions should not take much time now as it did earlier! (EXT4 users can use the same recovery. I just made it for my convenience)
1. Download TWRP: https://www.androidfilehost.com/?fid=24385658843824749
2. In recovery, go to 'wipe' -> 'Advanced Wipe'
3. Check only 'Data' and tap on 'Repair or Change File System' -> 'Change File System'
4. Here select 'F2FS' and Swipe to Change
5. Repeat step 3 and 4 for 'Cache' by checking only 'Cache' in Wipe menu.
6. Reboot! Enjoy!
I want to get back to EXT4 again from F2FS, how should I?
Again, while you are changing your file system, the partition gets wiped. So do backup your data of Internal SD Card and proceed!
1. In recovery, go to 'wipe' -> 'Advanced Wipe'
2. Check only 'Data' and tap on 'Repair or Change File System' -> 'Change File System'
3. Here select 'EXT4' and Swipe to Change
4. Repeat step 2 and 3 for 'Cache' by checking only 'Cache' in Wipe menu.
5. Reboot
PS: Only support for F2FS is added on /data and /cache. It still uses EXT4 by default and is just same as it was in previous builds!

first of all
its an amazing rom
but would absolutely love it if i know how to activate power save mode
and a small request " can you add the theme engine from cyanogen os??????"
i really hate the cm theme engine

hello, why cm13 isn't official because there aren't no bugs?

aminvishwas said:
which gapps works best for this rom?arm,arm64 or x86.Im unable to flash open gapps.Please help.
Solved : Flashed ARM64-6.0-pico.Now it works great.Thanks developer for the wonderful ROM.Keep up your good work
Click to expand...
Click to collapse
Can't we use the gap 6.0 Full

problm in 5.0.2 ?
there is problm of wake up while charging that it may not happen while m charging phone sir can u pls tell me to fix this problm it will be appreciated could you help me pls....??

sahil314 said:
Hey I am facing problem while flashing thus ROM. Please help please
Click to expand...
Click to collapse
bro before flashing the zip file.
do following in TWRP
wipe davlik
wipe data
wipe cache
wipe system
and install the zip file the above error will not appear

reserved

sahil314 said:
Hey I am facing problem while flashing thus ROM. Please help please
Click to expand...
Click to collapse
wipe data and system and install and that will fix the error and one more thing can you make a system backup with twrp and give me i need this rom but my devices is irulu v3 and i try cm12 but its old now.

[ROM] [ 8.1.0 ] Official madOS - Vernee Thor [MT6753]

Reserved
First time Install Instructions
0) Preparation
0.1) Backup your important data to PC
0.2) Download “twrp_vernee_thor_oreo.img“:
http://www.mediafire.com/file/m58f5ifmopyb209/twrp_vernee_thor_oreo.img
0.3) Download “madOS_8.1.0_thor_2018xxyy.zip“ https://www.facebook.com/MediatekAndroidDevelopers/
0.4) Optional, Download “Google Apps (aka Gapps)“: http://opengapps.org/. Choose: “ARM64“, “Android 8.1“, “nano“ or “pico“ package
1) Flash the recovery and boot to it. (choose option a) if you don't have another TWRP already installed, else choose b))
1.1a) Boot in the BOOTLOADER mode (using ADB: "adb reboot-bootloader").
Then execute command “fastboot flash boot twrp_vernee_thor_oreo.img”;
and then “fastboot reboot” (this is a trick to directly bring you to the newly flashed recovery. You can't boot up your current/stock rom at this point anymore).
1.1b) Boot to your current TWRP. Choose install --> image, and select twrp_vernee_thor_oreo.img“. Then choose “recovery“ as the target. After few seconds, and succesful installation, hit “back“ several times, then go to “reboot --> recovery“
2) Install
2.0) Optional, but recommended: Go to "Wipe --> Advanced Wipe", click "Cache" and then "Repair or Change File system". Then select "Change File system" and choose "F2FS". Swipe to confirm.
Hit "back" three times (you can again choose a partition to change now). Choose "Data" and do as above.
Hit "back" several times, to get back to the main menu. Choose "Reboot --> Recovery".
2.1) While already in recovery (TWRP), connect your phone to pc, and copy “madOS_8.1.0_thor_2018xxyy.zip“ and the Google Apps to your phone.
2.2) Go to "Wipe", and directly slide the slider to the right.
2.3) Get back to main menu with the "back" button
2.4) Go to "Install" and hit “madOS_8.1.0_thor_2018xxyy.zip“, then uncheck all boxes and hit "Add more zips", now choose the Google Apps.
Confirm installation by swiping the slider to the right.
2.5) Reboot System
Click to expand...
Click to collapse
Follow up Install Instructions
Download rom and gapps
boot to recovery
flash rom and gapps
optional: flash superSu/Magisk
reboot system
General F.A.Q.
Q: What the hell is madOS ?
A: madOS, (M.A.D. Team OS), is a ROM based on pure A.O.S.P. with extended capabilities and customizations made by or merge/adapted by M.A.D. Team.
Q: Can I install this rom on any other device, than the one mentioned in the title/description?
A:
WTF! Of course not! It is not mentioned in the title/description for some reason...how stupid can one be?!
If you still come to my thread and ask this stupid question, I'll answer some random nonsense. Don't come to me to complain when you break your device!
Q: Which recovery should I use for this ROM?
A: Latest M.A.D. TWRP 3.2.1-0 recovery for OREO 8.1.0
Q: How do i flash new recovery ?
A:
1: You can flash it with a scatter file
2: You can simply flash it from the existing twrp recovery: Install> Install image> Select Oreo TWRP> Select "Recovery" as partition to flash.
Reboot to recovery to use new one
Q: Do i need to make full wipes?
A: YES, dont come crying at me, if you didn't .... ;p
Q: What is "full wipes" ?
A: To Wipe : Cache; System; DATA ...
Q: What should i use f2fs or ext4?
A: Both are supported, choose the one you desire
Q: Does this rom have any Theme support
A: Yup, We have working Theme Engine (madOS extras)
Update: On Oreo 8.1.0:
- We have extended Theme support even further ( madLauncher, messaging, etc)
- As well as many fixes
Q: Some translations are missing for my language, can I help?
A: Sure you can, please check our translations repo available here , you can either do a pull request, or if you don't know how to work with git, sent us the XML. Strings for your language ( Check Readme on repo).
Q: I want to report a bug(s) do you have an issue tracker?
A: Yeah... madOS issue tracker
Q: What's working ?
A: Check first Post for current status
Q: App "x" doesn't work, why?
A: Probably not compatible with OREO yet, feedback is welcome
Q: Is the rom rooted?
A: NO, But you can easily root with :
1: Magisk ( v14 onwards.)
2: Super SU ( v2.82 onwards)
IF there are problems in rooting, you need to report it to the root-threads...There's nothing we can do
Q: Should i root together with rom ?
A: Not advised.. mainly the Magisk that gives some weird issues...
Flash ROM and GAPPS (if you use gapps), after first boot get back to recovery and flash your desire rooting method
Q: Does xposed work?
A: Is there Xposed for O? ... then no ;p
Q: How is battery life with Oreo?
A: Pretty awesome
Q: Does this build support Vulcan?
A: No....duh! v
Q: Does doze work in this build?
A: Yup
Q: when will (feature/issue here) be fixed?
A: NO ETA , please
Porting F.A.Q.
No porting support, no port questions allowed on this thread, and porting PMs will be auto-deleted, porting replies will be reported as well
G.APPS F.A.Q.
Q:What GAPPS package should I use?
A: openGapps arm64 nano/pico
Q: How to properly install GAPPS?
A:Flash Rom + Flash Gapps at once
CREDITS and Thanks
madOS Team
Our translators, credits list here
A.O.S.P.
Pure Nexus
AOSPA
DU (Dirty Unicorns)
Omni
HELP supporting madOS
We do this on our free time, however we do have costs on maintaining this :/
Any donation is highly appreciated
You can donate by using
this link
If the above doesn't work in your country, then you can directly donate by using this e-mail adress: [email protected]
About madOS Proprietary Apps
You are NOT allowed by any means, to use our madOS apps on any other build, your rom
This is exclusively for OFFICIAL madOS ROM releases
@To Moderators: Feel free to clean the thread, whenever users start spamming, severe OT, or questioning about porting...

Reserved

Can I install it on my K4 Note?

Pritam Tumma said:
Can I install it on my K4 Note?
Click to expand...
Click to collapse
Can you read?

Is it possible to roolback to nougat (7.1.2) after install this update?

drifeter said:
Is it possible to roolback to nougat (7.1.2) after install this update?
Click to expand...
Click to collapse
Yes, you would need to flash the N twrp, wipe and flash the N rom

"Size of image is larger than target device" trying to flash new recovery. I just wiped everything, now I'm out of OS for this moment xD
Can you help me?
I used your last OS on this phone. It's before october(received it on may of that year) and MT6753
I have twrp 3.0.... from megthebest
Thank you for your patience
--
EDIT: Can I wipe "internal storage"? I didn't wipe everything :v

ZeDdYRov said:
"Size of image is larger than target device" trying to flash new recovery. I just wiped everything, now I'm out of OS for this moment xD
Can you help me?
I used your last OS on this phone. It's before october(received it on may of that year) and MT6753
I have twrp 3.0.... from megthebest
Thank you for your patience
--
EDIT: Can I wipe "internal storage"? I didn't wipe everything :v
Click to expand...
Click to collapse
I'll check the size error in a bit...
Of course you can wipe internal storage, but keep in mind that this is where your pictures are.
edit: checked/flashed the twrp_vernee_thor_oreo.img.... all fine with it...its size is 13.4mb, the recovery partition is 16mb. i suppose this 'megTheBest recovery' just isn't the best....

DerTeufel1980 said:
I'll check the size error in a bit...
Of course you can wipe internal storage, but keep in mind that this is where your pictures are.
Click to expand...
Click to collapse
Thank you for your quick response!
I wiped internal storage, data, cache, and system. Do I should wipe anything more in order for this to work? I'm still stuck on the error. I go to Install - Install Image, pick the twrp_vernee_thor_oreo.img file on Recovery Partition, and receive the message on the comment above.

ZeDdYRov said:
Thank you for your quick response!
I wiped internal storage, data, cache, and system. Do I should wipe anything more in order for this to work? I'm still stuck on the error. I go to Install - Install Image, pick the twrp_vernee_thor_oreo.img file on Recovery Partition, and receive the message on the comment above.
Click to expand...
Click to collapse
Since you already removed everything, I'd suggest to just install the stock 6.0 rom with flashtool and 'firmware upgrade' option

DerTeufel1980 said:
I'll check the size error in a bit...
Of course you can wipe internal storage, but keep in mind that this is where your pictures are.
edit: checked/flashed the twrp_vernee_thor_oreo.img.... all fine with it...its size is 13.4mb, the recovery partition is 16mb. i suppose this 'megTheBest recovery' just isn't the best....
Click to expand...
Click to collapse
lol, I just gave the name of the dev because could help you figure it out. I'm n00b on this :V
I just did sh** with the files. I was trying to flash with a file called twrp_blablabla.img that was 422MB. For some reason I missclicked on the file while saving :v
EDIT: SORRY and Thank you

Yeahhhhhh finally 8.1 on our Thor.... So great!
Thank you so much Mad-team.
Weeeeeeeeeeeeee!!!

DerTeufel1980
Thank you for your work
Everything works without problems.
:good:

I'm on madOS for 40min and I'm loving it. This is fully customize as you want this machine working. Well played!!! LOVE YOU MAD TEAM

Hello again! Software buttons get bugged when we enter on opened apps menu, and its has a ghost start buttons I'm n00b and I found a bug: D

ZeDdYRov said:
Hello again! Software buttons get bugged when we enter on opened apps menu, and its has a ghost start buttons I'm n00b and I found a bug: D
Click to expand...
Click to collapse
I am using softbuttons for a long time and they always work good. Maybe you can try to go back to default settings... Wipe cache/dalvik and try again

This is for the first revision, is it possible for you to make it for the second? Please...

RalphMalph said:
I am using softbuttons for a long time and they always work good. Maybe you can try to go back to default settings... Wipe cache/dalvik and try again
Click to expand...
Click to collapse
If I could be able to change what buttons do... the back button on soft button is on the right, and I'm used to it on the left. There's any option on madOS to change what I'm telling to you?
EDIT: I read second time and notice what you said. I'll try! Thank you for the tip

ppdua said:
This is for the first revision, is it possible for you to make it for the second? Please...
Click to expand...
Click to collapse
Re-read at least the first ten lines of the first post, before asking things like this

[ROM][Pie][OFFICIAL] Resurrection Remix v7.0.2 [evert]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Resurrection Remix P
Code:
[SIZE="4"]/*
* 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.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.

Make sure you have the latest TWRP.img
Download the latest RR-P zip and GApps zip (opengapps nano or smaller)
fastboot boot twrp.img (NEW!! See post #2 for info on installing TWRP)
If coming from stock for the first time, flash copy-partitions-AB.zip from second post (It takes a backup of active slot to inactive slot)
In TWRP, choose -> Wipe -> Format data and type "yes" at the prompt (Note: this will wipe internal storage)
Flash latest RR-P.zip
Reboot and let the ROM boot once (it is necessary to reboot between ROM flash and GApps/Addon flash due to slot-swap logic)
Reboot back to bootloader and fastboot boot twrp.img again
In TWRP, choose -> Wipe -> Format data and type "yes" at the prompt (You may be able to get away with just doing a factory reset at this point, but that's on you to try)
Flash Google Apps package (optional)
Flash Magisk (also optional) (Note: If Magisk doesn't stick after setting up your device, fastboot boot twrp.img one last time and flash it again, no need to wipe anything)
First boot may take up to 10 minutes.
ROM Download
GApps
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
Omni Team
And Of Course To All The Supporters, Donators And Users
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.

XDA:DevDB Information
Resurrection Remix Pie v7.0.2, ROM for the Moto G6 Plus
Contributors
Jleeblanch, erfanoabdi, rahulsnair, RR Team
Source Code: https://github.com/ResurrectionRemix
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2019-02-25
Created 2019-02-26
Last Updated 2019-04-21

Copy partitions zip & TWRP installation info
[size=+2]Important info, please read...[/size]
Starting from build 20190414, encryption is disabled (temporarily) and you must clean flash
The new TWRP version now supports decryption on Pie when booting twrp. However, I have updated TWRP to include the new magisk repacktools which allows users to download and install one twrp.img without the need of an installer zip. The reason behind releasing the ROM with encryption disabled? If you were to try to install TWRP while using an encrypted ROM, you would end up in a bootloop that would bring you back to TWRP. But, install TWRP on a ROM with encryption disabled, and everything works as expected.
[size=+1]TWRP Installation[/size]
-> TWRP download || twrp-3.3.0-v2-evert-jlb.img
->>> The twrp.img you download above will also be the same twrp.img you will install, so make sure to put a copy on your device as well
-> Boot twrp
Code:
fastboot boot twrp-3.3.0-v2-evert-jlb.img
-> In TWRP, choose Advanced / Install Recovery Ramdisk
-> Select the twrp-3.3.0-v2-evert-jlb.img
->>> At this point twrp will automagically unpack your boot.img and the twrp.img, swap out the recovery-ramdisk, and repack your boot.img. When this process completes, twrp will be permanently installed.
->>> Always flash Magisk AFTER you've installed twrp
-> Reboot and enjoy. You should now be able to reboot to recovery from the Power Menu!!
DO NOT try to install twrp on an encrypted rom. You will most likely end up in a bootloop, you have been warned!
Important
To keep TWRP installed between ROM updates, there is a Magisk Module named "TWRP A/B Retention Script" by @osm0sis. Search for it within Magisk Manager Downloads section. You'll want to flash this script zip after each OTA has installed, but before you install Magisk to the Inactive Slot from Manager.
[size=+1]Coming from stock?[/size]
Make sure to flash the copy-partitions-AB.zip in twrp before you do anything else. You can download it from the attachment below...

Reserved

Cool, i will test it now (im glad its official).
Ps dont do it "Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution"
i meant wiping system.. even if we install custom rom after this it will be no os installed as twrp says.

Woks awesome, thank you dev

Excellent ROM.
Always loved RR ROMs.
Only downside I have is wondering if there will be anyway to get Google Pay working, as unfortunately it doesn't on this ROM.
Also, how can I disable the one button navigation style, as when I have a NAV bar on, I still have functions on my one button.
TIA.

WYPIERDAALAAC said:
Cool, i will test it now (im glad its official).
Ps dont do it "Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution"
i meant wiping system.. even if we install custom rom after this it will be no os installed as twrp says.
Click to expand...
Click to collapse
The install instructions in the OP are generic, and don't necessarily apply for this device. You're better off following the install instructions from Lineage-16.0. I will update the OP with proper install instructions when I have some time asap.
LDMx96 said:
Excellent ROM.
Always loved RR ROMs.
Only downside I have is wondering if there will be anyway to get Google Pay working, as unfortunately it doesn't on this ROM.
Also, how can I disable the one button navigation style, as when I have a NAV bar on, I still have functions on my one button.
TIA.
Click to expand...
Click to collapse
For now, if you've flashed Magisk, you can flash my Magisk module (or any module) that will help pass safetynet and show device as being certified in Play Store. This is why Google Pay doesn't work.
I had updated some blobs and build fingerprint to match the stock Pie update, but it seems to be causing the device to fail safetynet. I will have this fixed in the next update.
As for the fingerprint gestures always being enabled. I'm looking into this too. I'm assuming this has something to do with an overlay I added to insure the navbar was enabled on first boot (as without it, it's not). I hope to have this fixed for the next update as well.

Jleeblanch said:
For now, if you've flashed Magisk, you can flash my Magisk module (or any module) that will help pass safetynet and show device as being certified in Play Store. This is why Google Pay doesn't work.
I had updated some blobs and build fingerprint to match the stock Pie update, but it seems to be causing the device to fail safetynet. I will have this fixed in the next update.
As for the fingerprint gestures always being enabled. I'm looking into this too. I'm assuming this has something to do with an overlay I added to insure the navbar was enabled on first boot (as without it, it's not). I hope to have this fixed for the next update as well.
Click to expand...
Click to collapse
No problem, I won't flash Magisk if you're looking at getting it fixed I will just hang fire, it's not a much needed thing anyway, as Google Pay isn't a much needed thing for me, was just handy.
As for the Fingerpring Gestures that's fine, it's not harmful, I just thought I'd mention it.
I'm loving it so far, not had any problems all good.

Awesome! I'm using magisk with Ainur Sauron and Viper, working flawlessly! Everything works pretty well so far. Thanks for the amazing job!
I flashed it over the stock pie without wiping system, only factory reset. I don't know if this helps because I'm still a newbie P, just sharing!
RR rocks!

LDMx96 said:
No problem, I won't flash Magisk if you're looking at getting it fixed I will just hang fire, it's not a much needed thing anyway, as Google Pay isn't a much needed thing for me, was just handy.
As for the Fingerpring Gestures that's fine, it's not harmful, I just thought I'd mention it.
I'm loving it so far, not had any problems all good.
Click to expand...
Click to collapse
I will fix it, yes. It seems I got it right on Beckham, but not so much on Evert lol. Anyway, I'll have an update ready for the weekend. I don't use Google Pay much myself either, although as you said, it is handy. I'd prefer things worked out of the box rather than needing workarounds to fix things.

Jleeblanch said:
I will fix it, yes. It seems I got it right on Beckham, but not so much on Evert lol. Anyway, I'll have an update ready for the weekend. I don't use Google Pay much myself either, although as you said, it is handy. I'd prefer things worked out of the box rather than needing workarounds to fix things.
Click to expand...
Click to collapse
No worries mate, I'll look forward to the update on the weekend then.
Thanks a bunch.

Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English

asesinodilusion said:
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
Click to expand...
Click to collapse
I've just tested this too, no call volume when earphones are connected, but fine once disconnected.

asesinodilusion said:
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
Click to expand...
Click to collapse
LDMx96 said:
I've just tested this too, no call volume when earphones are connected, but fine once disconnected.
Click to expand...
Click to collapse
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.

Jleeblanch said:
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Click to expand...
Click to collapse
There is a manual or some guide to do that? Please

asesinodilusion said:
There is a manual or some guide to do that? Please
Click to expand...
Click to collapse
There are basic instructions in the OP to take logs on the device using Matlog. There is also a decent tutorial here on xda: [Tutorial] How To Logcat

Jleeblanch said:
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Click to expand...
Click to collapse
https://www.dropbox.com/s/rqz2t7d57epq7i9/data.txt?dl=0
I hope this help

BT Calling not working
Hello together,
i installed th RR Rom on my phone and everything seems to be fine.
BUT the only thing is, "Bluetooth Calling" does not work. I tried it with to different Bluetooth devices, my oneplus wireless bullets, and my car.
No Microphone and no Sound is Working, very rare.
But when i do BT Calling with SIGNAL or VOIP app CSipSimple everthing is fine. It looks like, that the only problem is the telefone app itself from android pie.
Before i used the [ROM][UNOFFICIAL]LineageOS-16.0[Evert][Moto G6 Plus] and BT Calling was working fine!
Does someone have a tip for me, where i can take a look?
Thanks a lot.
Greetings

It works very well, except for the detail that sometimes there is lag and when making or receiving a call there is too much noise
Enviado desde mi Moto G6 Plus mediante Tapatalk

titofariasl said:
It works very well, except for the detail that sometimes there is lag and when making or receiving a call there is too much noise
Enviado desde mi Moto G6 Plus mediante Tapatalk
Click to expand...
Click to collapse
Is there any way of improving in-call audio quality? There is just too much background noise.

[ROM][11] DarkJoker360 AOSP 11 for Huawei P8 Lite 2017

Hi,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DarkJoker360 AOSP 11 for Huawei P8 Lite 2017
*** Stable Version ***
About
Android is an open source software stack for mobile devices and a corresponding open source project led by Google. This site and the Android Open Source Project (AOSP) repository offer the information and source code needed to create custom variants of the Android stack, port devices and accessories to the Android platform, and ensure devices meet the compatibility requirements that keep the Android ecosystem a healthy and stable environment for millions of users.
Click to expand...
Click to collapse
Working
* Touchscreen
* Audio
* Boot
* Bluethoot
* Internal/External storage
* Mtp / Adb
* Sensors
* Wifi
* RIL
* Camera
* NFC
* FP gestures
Click to expand...
Click to collapse
Not Working
* You tell me
Click to expand...
Click to collapse
NOTE: The signal icon is buggy due to Huawei weird ril implementation, I am still looking to fix it over the new Android 10-11 telephony changes.
Installation
* you must have TWRP installed, use this one (make sure to have the unofficial Android 11 one ! )
WARNING: You must be decrypted before installing it otherwise it won't boot. (Read second post.)
* go to TWRP
* format data
* reboot to TWRP again
* do a full wipe (system, data, cache, dalvik/art cache) !
* reboot to bootloader
* extract AOSP 11
* run: fastboot flash system <drag system.img here>
* reboot to TWRP
* resize system
* flash gapps (optional)
* flash NFC.zip
NOTE: this zip is needed for having working NFC. DO NOT IGNORE IT !
* reboot to System
* Enjoy !!!
Click to expand...
Click to collapse
Update
* reboot to TWRP and do a wipe cache, dalvik/art cache
* reboot to bootloader
* extract AOSP 11
* run: fastboot flash system <drag system.img here>
* reboot to TWRP
* resize system
* flash gapps (optional)
* flash NFC.zip
NOTE: this zip is needed for having working NFC. DO NOT IGNORE IT !
* reboot to System
* Enjoy !!!
Click to expand...
Click to collapse
If you are getting Error 70 while flashing gapps just resize system from TWRP !
If gapps are giving network errors or other kind of errors install them after first boot !
Download
AOSP 11 and NFC fix
NikGapps
OpenGapps
Click to expand...
Click to collapse
Please support my work, it's very important! Thanks
DONATIONS
Regards !

NOTES
* For root method read this post, for rooting with magisk read this instead.
* If you face corrupted storage issues you need to go back on emui and re-install the rom.
* I recommend NikGapps core with SetupWizard add-on.
* Use 8.0.0.360 or maximum .400 firmware for booting the rom.
* Gapps can may give "Uncertified device" error and abort the google account login, use this guide to fix it (thanks to @latviandude )
* If you want VoLTE/Wifi Calling working flash this zip
** You must be decrypted for booting this rom **
Before following the installation steps format data and flash this file via TWRP.

Hi, I flashed yesterday AOSP 11via fastboot, storage decrypted with recommanded TWRP using edited fstab.hi6250. Rom seems to work better for me than AOSP 10, screen recorder works, backlight works, already resolved problem with bluetooth(connected/disconnected) by disabling HD Audio in developer options.
Battery drainage while using worries, but it is too early to say, still testing it. There is no way I can get NFC fix working(never could on any custom rom) so obviously I’m doing something wrong. Hope I’ll figure it out.
Thanks @DarkJoker360, great work!
EDIT: Flashing NFC fix worked and it is present in settings(Connected devices), but it's absent in status bar(I can live with that)

Hi . how can i "resize system" ?

piterconlai said:
Hi . how can i "resize system" ?
Click to expand...
Click to collapse
Go to twrp recovery, press "Wipe" Then choose "Advanced Wipe". After that select/check "System" box and then press on "Repair or Change File System" and then you will see down "Resize File System" - press on it and done ur System has been resized.

hardcorehenry said:
Hi, I flashed yesterday AOSP 11via fastboot, storage decrypted with recommanded TWRP using edited fstab.hi6250. Rom seems to work better for me than AOSP 10, screen recorder works, backlight works, already resolved problem with bluetooth(connected/disconnected) by disabling HD Audio in developer options.
Battery drainage while using worries, but it is too early to say, still testing it. There is no way I can get NFC fix working(never could on any custom rom) so obviously I’m doing something wrong. Hope I’ll figure it out.
Thanks @DarkJoker360, great work!
View attachment 5194331 View attachment 5194333
EDIT: Flashing NFC fix worked and it is present in settings(Connected devices), but it's absent in status bar(I can live with that)
Click to expand...
Click to collapse
Hello I would like to ask you some information
- the bluetooth headphones work?
- How's the battery drain going? More or less how many hours of screen does it make?

Added to AOSP 11 accent, font and icon shape picker (like theme picker), now working on an aosp icon pack picker (aka styles) !

piterconlai said:
Hello I would like to ask you some information
- the bluetooth headphones work?
- How's the battery drain going? More or less how many hours of screen does it make?
Click to expand...
Click to collapse
I made more thorough research, hope it’ll be useful for further development.
Battery:
When idle(sleep) it looses 1% overnight, when only screen on battery drain is 1% per 10 min, when only stopwatch on it looses 1% per 5 min. Checked without SIM and brightness level 45%. Now I’m going to let it drain completely and charge again. Maybe this results are normal(right define normal) and needles to worry about.
Bluetooth:
After pair my earbuds automatically trying to switch to aptX audio codec(they have aptX, AAC and SBC support) without success(connected/disconnected again and again), not possible to chose other codec when HD Audio in developer options is enabled. When disabled it automatically chooses SBC(without possibility of change), but this codec works without problems.

hardcorehenry said:
I made more thorough research, hope it’ll be useful for further development.
Battery:
When idle(sleep) it looses 1% overnight, when only screen on battery drain is 1% per 10 min, when only stopwatch on it looses 1% per 5 min. Checked without SIM and brightness level 45%. Now I’m going to let it drain completely and charge again. Maybe this results are normal(right define normal) and needles to worry about.
Bluetooth:
After pair my earbuds automatically trying to switch to aptX audio codec(they have aptX, AAC and SBC support) without success(connected/disconnected), not possible to chose other codec when HD Audio in developer options is enabled. When disabled it automatically chooses SBC(without possibility of change), but this codec works without problems.
Click to expand...
Click to collapse
Thanks for the reply
so can you do 8 h of screen with this rom?
Have you tried if the blutooth smartwatch works by accident?
Last question :
Would it be possible to go back to a previous version if I didn't like it? I am currently using lineage 16 and I am very happy with it

piterconlai said:
so can you do 8 h of screen with this rom?
Click to expand...
Click to collapse
Well you have to calculate yourself from data I provided or flash rom and find out.
piterconlai said:
Have you tried if the blutooth smartwatch works by accident?
Click to expand...
Click to collapse
I don’t have such device.
piterconlai said:
Would it be possible to go back to a previous version if I didn't like it? I am currently using lineage 16 and I am very happy with it
Click to expand...
Click to collapse
If you are more interested in comfort than struggle, testing and help DEV to perfect this rom don’t change anything. Going back means flash and install everything from scratch.

I'm always getting an error when flashing system img via fastboot...
error code : Invalid sparse file format at header magic
The system partition can't be written after the first sparse.
I tried with linux and windows, changed the usb cable but nothing change.
Is there anything to do before this operation except the ones in the insttructions ?

Junkilito said:
I'm always getting an error when flashing system img via fastboot...
error code : Invalid sparse file format at header magic
The system partition can't be written after the first sparse.
I tried with linux and windows, changed the usb cable but nothing change.
Is there anything to do before this operation except the ones in the insttructions ?
Click to expand...
Click to collapse
I’m not sure I also had this warning( Invalid sparse file format at header magic) but after a while flash went from beginning till the end without problems. Two things come to my head: outdated platform-tools or/and you are on wrong firmware(take a look at screenshots DarkJoker 8.0.0.400 and mine 8.0.0.402), but as I said not sure and it’s pure guess from my side. Wait for second opinion.

hardcorehenry said:
I’m not sure I also had this warning( Invalid sparse file format at header magic) but after a while flash went from beginning till the end without problems. Two things come to my head: outdated platform-tools or/and you are on wrong firmware(take a look at screenshots DarkJoker 8.0.0.400 and mine 8.0.0.402), but as I said not sure and it’s pure guess from my side. Wait for second opinion.
Click to expand...
Click to collapse
I have exactly the same problem. Adb also gives me this error, even though it always continues flashing though and also finishes then.
The ROM is however never bootable for me and I can't figure out what I have done wrong. I was on 8.0.0.402 before and used AEX 9 ROM just fine.
What version of TWRP did you use for successful results? I can't find a newer one from pretoriano80 but 3.2.1.0. Maybe that is a problem?
Regards

Friedensfurz said:
I have exactly the same problem. Adb also gives me this error, even though it always continues flashing though and also finishes then.
The ROM is however never bootable for me and I can't figure out what I have done wrong. I was on 8.0.0.402 before and used AEX 9 ROM just fine.
What version of TWRP did you use for successful results? I can't find a newer one from pretoriano80 but 3.2.1.0. Maybe that is a problem?
Regards
Click to expand...
Click to collapse
Hi,
I’ll try exactly step by step how I did it(I’m on macOS so there might be small differences). When on stock after unlocking bootloader and flashing TWRP(took from this post), you need to copy on your external sdcard or USBOTG NFC_fix.zip, gapps(optional) and fstab.hi6250b.zip or edit your own from /vendor/etc like in this post. Boot into TWRP (backup just in case your vendor partition)and either flash fstab.hi6250b.zip(easy way) or replace fstab.hi6250 in /vendor/etc with edited one via TWRP file manager(harder way). After flashing/replacing enter in TWRP into Wipe and Format Data>yes then reboot into TWRP, wipe: cache, dalvik cache and data and reboot into system. You should reboot into ugly looking stock rom. In settings>security>more you should see Encrypt phone that means storage is decrypted. Enable debug and confirm via adb and boot into TWRP. Make backup(ramdisk, kernel, data, system) enter section Wipe>Advanced Wipe and wipe Dalvik/ART Cache, Cache, Data and System. Don’t Format Data again because most probably it'll f*up Internal Storage besides internal storage is already decryptet. Reboot into bootloader. Run in terminal(macOS) or whatever is used in Windows/Linux:
fastboot devices
fastboot flash system drag and drop aosp-11_prague_20210117.img
Reboot into TWRP, resize System if needed, flash NFC_fix.zip and gapps(optional).
Wipe Cache and Dalvik, reboot and that should be all.

Junkilito said:
I'm always getting an error when flashing system img via fastboot...
error code : Invalid sparse file format at header magic
The system partition can't be written after the first sparse.
I tried with linux and windows, changed the usb cable but nothing change.
Is there anything to do before this operation except the ones in the insttructions ?
Click to expand...
Click to collapse
It is a know "issue", just ignore it and boot it.
It is most likely a warning.

DarkJoker360 said:
It is a know "issue", just ignore it and boot it.
It is most likely a warning.
Click to expand...
Click to collapse
Nope it's caused by new version of official firmware for this phone, system partition on newer versions is 2GB on b388 is 3GB.

That would explain why in the past I had troubles reflashing even stock SYSTEM.img via fastboot on latest official firmware. @DarkJoker360 maybe it’s worth mentioning that flashing anything on latest firmware is not advised, and firmware should be downgraded(latest safe confirmed working firmware 8.0.0.402[service rom] or 8.0.0.400 [the same as developer's]).

hardcorehenry said:
That would explain why in the past I had troubles reflashing even stock SYSTEM.img via fastboot on latest official firmware. @DarkJoker360 maybe it’s worth mentioning that flashing anything on latest firmware is not advised, and firmware should be downgraded(latest safe confirmed firmware 8.0.0.402[service rom]).
Click to expand...
Click to collapse
I recommend .360 firmware or .400 (the one I am using)
Newer firmwares with newer security patches may refure to boot due to some Huawei changes for avoiding modding.

Thanks for all of your help. I managed to get AOSP 11 to boot, the reason why it initially just bootlooped for me was that I did not directly come from Stock ROM. Very weird. Following @hardcorehenry 's steps worked fine. Is it somehow possible to get Magisk going on this ROM? I read the AOSP 10 thread and installed the "magisk phh v21.0".zip file, but now I am stuck on the "Your device cannot be trusted, your device is booting" screen. Any ideas for this? Many thanks.

Friedensfurz said:
Thanks for all of your help. I managed to get AOSP 11 to boot, the reason why it initially just bootlooped for me was that I did not directly come from Stock ROM. Very weird. Following @hardcorehenry 's steps worked fine. Is it somehow possible to get Magisk going on this ROM? I read the AOSP 10 thread and installed the "magisk phh v21.0".zip file, but now I am stuck on the "Your device cannot be trusted, your device is booting" screen. Any ideas for this? Many thanks.
Click to expand...
Click to collapse
No magisk at the moment, I'm sticking with A10 untill Magisk 19.3 will work on this rom (need to pass safety net)

[ROM][prague][11] LineageOS 18.1 for Huawei P8 Lite 2017

Hi,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 18.1 for Huawei P8 Lite 2017
*** Stable Version ***
About
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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. You can also view the Changelog for a full list of changes & features.
Click to expand...
Click to collapse
Working
* Touchscreen
* Audio
* Boot
* Bluethoot
* Internal/External storage
* Mtp / Adb
* Sensors
* Wifi
* RIL
* Camera
* NFC
* FP gestures
Click to expand...
Click to collapse
Not Working
* You tell me
Click to expand...
Click to collapse
NOTE: The signal icon is buggy due to Huawei weird ril implementation, I am still looking to fix it over the new Android 10-11 telephony changes.
Installation
* you must have TWRP installed, use this one (make sure to have the unofficial Android 11 one ! )
WARNING: You must be decrypted before installing it otherwise it won't boot. (Read second post.)
* go to TWRP
* format data
* reboot to TWRP again
* do a full wipe (system, data, cache, dalvik/art cache) !
* reboot to bootloader
* extract LineageOS 18.1
* run: fastboot flash system <drag system.img here>
* reboot to TWRP
* resize system
* flash gapps (optional)
* flash NFC.zip
NOTE: this zip is needed for having working NFC. DO NOT IGNORE IT !
* reboot to System
* Enjoy !!!
Click to expand...
Click to collapse
Update
* reboot to TWRP and do a wipe cache, dalvik/art cache
* reboot to bootloader
* extract LineageOS 18.1
* run: fastboot flash system <drag system.img here>
* reboot to TWRP
* resize system
* flash gapps (optional)
* flash NFC.zip
NOTE: this zip is needed for having working NFC. DO NOT IGNORE IT !
* reboot to System
* Enjoy !!!
Click to expand...
Click to collapse
If you are getting Error 70 while flashing gapps just resize system from TWRP !
If gapps are giving network errors or other kind of errors install them after first boot !
Download
LineageOS 18.1 and NFC fix
NikGapps
OpenGapps
Click to expand...
Click to collapse
Please support my work, it's very important! Thanks
DONATIONS
Regards !

NOTES
* For rooting with magisk use this.
* If you face corrupted storage issues you need to go back on emui and re-install the rom or fastboot erase userdata + twrp format data.
* I recommend NikGapps core with SetupWizard add-on.
* Use 8.0.0.360 or maximum .400 firmware for booting the rom.
* Gapps can may give "Uncertified device" error and abort the google account login, use this guide to fix it (thanks to @latviandude )
* If you want VoLTE/Wifi Calling working flash this zip
** You must be decrypted for booting this rom **
Before following the installation steps format data and flash this file via TWRP.
Changelog from initial build
* Fixed offline charger for all devices
* Fixed gapps uncertified error
* Improved performance
* Fixed animations janks and lags
Useful links
My telegram channel
HI6250 support group

Great work
Thank you !

What is the features of this rom?

Everywhere I go said:
What is the features of this rom?
Click to expand...
Click to collapse
its lineage os rom

@DarkJoker360 hi , will there be a descendent rom ?
thanks so much!

amrqqq said:
@DarkJoker360 hi , will there be a descendent rom ?
thanks so much!
Click to expand...
Click to collapse
No, I just work on a rom only !

Looks nice. I will try it later. Thanks.

Hi
Here is a little feedback from the first tests (I am in EMUI version 8.0.0.390):
- No problem for installing the ROM and Google Apps (NikGapps-basic-arm64-11-20201231)
- Playstore: ok
- Wifi: ok
- Touchscreen : ok
- Bluetooth: ok
- Location: ok after clear and update AGPS in GPS Test.
- Cast / Miracast: ko (smartphone reboot)
- NFC: ok (service started but intermittent crash when reading an NFC card with NFC Test)
- Camera lineage OS: ko (unable to take a photo, error message insert SD Card)
- Camera Gcam Go : ok (front and back camera). Unable to store photo on sdcard also
- Alarm and clock lineage : ko . You must install another clock apps
- Fingerprint : ok
I continue the tests ....

Thanks man for Lineage 18 . 1!!! It's awesome!
P.S. Great job like always! Thank you for supporting our device! Please continue working on it! Your the best.
I hope that more people will appreciate your work, it's really great!

AltairFR said:
@DarkJoker360 hi
Here is a little feedback from the first tests (I am in EMUI version 8.0.0.390):
- No problem for installing the ROM and Google Apps (NikGapps-basic-arm64-11-20201231)
- Playstore: ok
- Wifi: ok
- Touchscreen : ok
- Bluetooth: ok
- Location: ko (google maps does not give the correct location)
- Cast / Miracast: ko (smartphone reboot)
- NFC: ok (service started but intermittent crash when reading an NFC card)
- Camera lineage OS: ko (unable to take a photo)
- Gcam Go : ok
I continue the tests ....
Click to expand...
Click to collapse
- Lineage Camera : OK
- Location : Google Maps, fails to detect correct location (some meters accuracy inside house but I'm sure it works, u just need to go outside and do some walking to get more accurate location)
- Gallery : Ok.
- Fingerprint : At first I couldn't add my FP, then I went to "Settings/System/Gestures" and enabled "Swipe fingerprint for notifications" and tested if I can scroll notifications with it, after that I disabled it and then I noticed that I could add FP. So in the end it WORKS.
- Calling : If you are using NikGapps, u need to go to "Settings/Apps and Notifications/Default Apps" and set default Phone app/Dialer. Then you can make calls without problems.
- NFC : I can enable it and disable but I can't use it for mobile contactless payments because my Banking app shows that I'm rooted, even I have no root enabled.
- Performance, animations : Ok.
- RIL/Network : As I have Latvia SIM Card and Dual Sim Variant - PRA-LX1, after first boot I notice - Network restart issue. To fix it you need to set PIN Lock from different device, if it doesn't help, you need to disable Dual sim with "persist.radio.multisim.config=none" and reboot ur device, usually it works, else u need to go to Settings and reset APN settings.
- Battery : Ok.
- Audio : OK.
- Playstore/Gapps : OK
- Bluetooth : Haven't tested yet.
- Cast Screen : Haven't tested yet.
- Touchscreen : OK.
- Messaging : Seems to be OK.
- Notification LED/Light : can't be tested, cuz it's dead for me.
- Sounds for notifications/alarm : Can't be found, you need to download and install "Google/Pixel Sounds app" and set ringtone sound manually.
- Brightness : Seems to be +- good.
- Root : As default it doesn't work. But it can be enabled using one of Hamido's 3 methods. Not gonna add em, you can find them in hi6250 community group or XDA.
- Alarm : OK. So don't worry you will be able to wake up in time LOL
- Instagram : Everything is ok except you can't add Story from Gallery, so to fix this you need to install older Instagram version.
- OneDrive : It's ok, except you can't download your files, documents using app. But there's an workaround, Thanks to Hamido. You can download your files using ADM Browser app.
- Netflix : Latest versions doesn't let you play videos, I believe.. So to be able do that you need to download this version - "6_26_1_build_15_31696_31696". It will still give you sometimes error messages ,for example, when you try to play next episode but at least you will be able to watch something.
I think that this is it for now. Will update things, if I notice something new. Thanks for reading lol.

What version of MUI is your smartphone ?
Does the alarm work?

AltairFR said:
What version of MUI is your smartphone ?
Does the alarm work?
Click to expand...
Click to collapse
AOSP clock is broken here, install Google one !

DarkJoker360 said:
AOSP clock is broken here, install Google one !
Click to expand...
Click to collapse
Actually AOSP clock works fine here.

Hi
I am found my problem (clock, camera etc..)
Before flashing the rom, I wipe data and internal storage in TWRP.
So when system start for the first time, it doesn't set the right permission and owner on /data/media/0 subfolder
If you have the same problem, just open a terminal in TWRP and type
cd /data/media
chown media_rw:media_rw 0
chmod 770 0

AltairFR said:
Hi
I am found my problem (clock, camera etc..)
Before flashing the rom, I wipe data and internal storage in TWRP.
So when system start for the first time, it doesn't set the right permission and owner on /data/media/0 subfolder
If you have the same problem, just open a terminal in TWRP and type
cd /data/media
chown media_rw:media_rw 0
chmod 770 0
Click to expand...
Click to collapse
I don't understand, can you describe the problem at all?

DarkJoker360 said:
I don't understand, can you describe the problem at all?
Click to expand...
Click to collapse
do you want the cause of the problem or the consequence?

AltairFR said:
do you want the cause of the problem or the consequence?
Click to expand...
Click to collapse
The cause

I will try to reproduce the problem, the cause is a problem of access rights on the folder /data/media/0
In my smartphone the owner of 0 subfolder was "root"

AltairFR said:
I will try to reproduce the problem, the cause is a problem of access rights on the folder /data/media/0
In my smartphone the owner of 0 subfolder was "root"
Click to expand...
Click to collapse
Alright, I need to know now what was the problem. What was it giving, I already understood but please tell me exactly.

Database Info

welcome