[ROM][Pie][OFFICIAL] Resurrection Remix v7.0.2 [evert] - 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"
}
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.

Related

M7+M7vzw+M7spr AICP-13.1-O 8.1 UNOFFICIAL BUILDS

{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Lollipop, the Rom has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LAOS) we are now LAOS based with some tweaks from AOSP.
If there are any bugs, either we will sort them out or the LAOS team will if it concerns their code base. This rom isn't LAOS supported, so no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough Overview)
In the beginning we would like to thank:
LineageOS & CM (R.I.P.) team
 @maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@Drgravy
@Hashbang173
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 13.1
Download link m7: https://www.androidfilehost.com/?w=files&flid=239910
Download link m7vzw: https://www.androidfilehost.com/?w=files&flid=238220
Download link m7spr: https://www.androidfilehost.com/?w=files&flid=239908
Full Changelog link: http://dwnld.aicp-rom.com/
Google Apps:
(link the best one for your device, there are several variants out there right now, pico/nano gapps from opengapps.org is almost always a good choice though)
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look in the OP to see if your device is built on a nightly or weekly schedule.
Q. Does this ROM support custom kernels?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP, custom ROM's modify the framework a lot, so Xposed can cause a ton of issues on custom ROM's. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. You will need to use the version arm64/arm/whatever for SDK 27.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the install instructions in the first post...
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid backup first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
Q. How do I dirty flash builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), reboot. Or just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot", then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash, and then reboot.
Using the ROM:
Q. How do I enable software buttons?
A. Go to Aicp Extras/Navigation bar, and enable it.
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I keep losing root with Magisk, how do I fix it?
A. Check this out. If that doesn't work for you, ask for help in this thread, read or ask in the Magisk thread on XDA or just re-flash Magisk!
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Oreo. You don't need to install any Add-on's, simply download the latest ROM, GApps, flash it and go!
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash:
(Again: Don't do it if you don't know it!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, Data and ART/Dalvik cache.
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work).
6. Reboot your device.
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every OTA update (= ROM Update)
Currently Supported Root Solutions:
Magisk stable
Magisk versions higher than 14.0 doesn't require flash on every dirty flash depending on the deivce, some devices need you to flash it every time, unless your maintainer says otherwise it should be fine
KERNEL:
The kernel in this ROM follows LAOS source with custom additions.
PREREQUISITE FOR OTA:
To be able to flash using the built-in OTA app, TWRP recovery is needed.
You can still use the LAOS recovery and OTA app, but you will need to download the zip file and flash it manually from within your recovery. The Zipfile gets saved in the "aicp_ota" folder on your internal storage.
Please be sure that you are on the latest TWRP recovery. Keep in mind that this could also be an unofficial version!​
If you want to contribute to the AICP or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
https://github.com/icxj1/android_kernel_htc_msm8960/tree/o8.1
ROM & Additional links:
AICP Gerrit Code Review
AICP on Github
AICP G+ community
Contributors:
 @icxj1
 @alial04
 @tathanhlam66
ROM OS Version: 8.1.x Oreo
Kernel: Linux 3.4.113
Version Information: Development
Status: UNOFFICIAL
Release Date: 02-28-2018
You want to see a "normal" night at the "DEV office", click here!!
XDA:DevDB Information
HTC ONE M7ul,wlv,wls, ROM for the HTC One (m7)
Contributors
icxj1, alial04
Source Code: https://github.com/AICP/platform_manifest
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Based On: All of the above
Version Information
Status: Testing
Created 2018-02-28
Last Updated 2018-02-27
[/ATTACH][/ATTACH]
This ROM is testing & development. I know it must be hard for some to comprehend, the source is not complete yet. And the more they advance the less compatible m7 becomes.
Please report bugs with logs! No need to report what works on N ROM that does not work on O. M7 is not compatible for Oreo & i have many modifications to make it work. If you cannot live with a few bugs for awhile then GTFO! I do not get paid to maintain or develop so I don't want to here your pissing & moaning about an piece of **** obsolete device.
Bugs= "system process isn't responding" anr warning on boot. Select wait & carry on. This is caused by system partition not being mounted early enough in the boot process. 8.0+ expects an early mounted system partition. This is handled in the kernel by use of a separated dts, our kernel does not support dts for m7.
Lock screen with pin or password causing problems for some user's. not sure the entire issue, but reports of waiting up to 5 minutes to unlock. ??? send logs on this please.
Rooted devices must enable d2tw & pocket mode in kernel aduitor to fix proximity wake not working on outgoing phone call, (when screen is black dt2w it). Not an issue on non-rooted devices.
It is pointless to post here, most don't read it & will report the same bugs over & over in thread.
Should have ffcamera in this one & mobile settings partialy fixed, no data usage info & quick settings tile will crash. please do not report these bugs, i already have logs for them. enjoy!
m7 += https://www.androidfilehost.com/?fid=673956719939822539
m7vzw += https://www.androidfilehost.com/?fid=890129502657586018
m7spr += https://www.androidfilehost.com/?fid=746010030569956907
Can you guys make a kernel with wake gestures included?
lucyr03 said:
Can you guys make a kernel with wake gestures included?
Click to expand...
Click to collapse
They are already working on it but it makes some problems with oreo. If it is working they will release it.
Hi @icxj1
Thanks for the developement work!
May I ask,...? What's about Google certification? PlayStore says: "not certified".
And Magisk says: "basicIntegrety: true" but "ctsProfile: false"
Will you even work on that? That would be great. Thank you very much.
samhhmobil
samhhmobil said:
Hi @icxj1
Thanks for the developement work!
May I ask,...? What's about Google certification? PlayStore says: "not certified".
And Magisk says: "basicIntegrety: true" but "ctsProfile: false"
Will you even work on that? That would be great. Thank you very much.
samhhmobil
Click to expand...
Click to collapse
Gapps are beta, search their unofficial thread & see if you can find anything. And m7 will probably have to start using the magisk universal cts module. Search magisk modules for zip.
https://forum.xda-developers.com/an...cial-opengapps-builds-android-t3743495/page28
samhhmobil said:
Hi @icxj1
Thanks for the developement work!
May I ask,...? What's about Google certification? PlayStore says: "not certified".
And Magisk says: "basicIntegrety: true" but "ctsProfile: false"
Will you even work on that? That would be great. Thank you very much.
samhhmobil
Click to expand...
Click to collapse
Flash this zip in twrp to fix safetynet, I tested it and working fine on this rom.
https://www.androidfilehost.com/?fid=962187416754455235
first of all, thx for sharing all the work, the rom (20180228) works very smooth and definitely usable this time. besides the known bugs, i've also noticed (so far) problem with the proximity sensor (not working incalls and cpuz), wifi doesn't reconnect when registered network becomes visible (i have to turn it on and off to get it going), some wifi drops (occasionally) and wifi disconnecting while sleep (also occasionally).
sorry no logs, will do them when can, just wanted to say thank you!
edit: also, i have to reinsert the sim card upon restart.
olivrd said:
first of all, thx for sharing all the work, the rom (20180228) works very smooth and definitely usable this time. besides the known bugs, i've also noticed (so far) problem with the proximity sensor (not working incalls and cpuz), wifi doesn't reconnect when registered network becomes visible (i have to turn it on and off to get it going), some wifi drops (occasionally) and wifi disconnecting while sleep (also occasionally).
sorry no logs, will do them when can, just wanted to say thank you!
edit: also, i have to reinsert the sim card when os booted.
Click to expand...
Click to collapse
This device, the m7 allways had wifi problems even with stock rom it drops sometimes and doesnt connect when a known network is around sometimes. That must be related to the hardware because it was in all android versions from 4.1.2 up to 8.1 in stock and all custom roms the same no matter which firmware is used stock sense or gpe.
olivrd said:
first of all, thx for sharing all the work, the rom (20180228) works very smooth and definitely usable this time. besides the known bugs, i've also noticed (so far) problem with the proximity sensor (not working incalls and cpuz), wifi doesn't reconnect when registered network becomes visible (i have to turn it on and off to get it going), some wifi drops (occasionally) and wifi disconnecting while sleep (also occasionally).
sorry no logs, will do them when can, just wanted to say thank you!
edit: also, i have to reinsert the sim card upon restart.
Click to expand...
Click to collapse
For the sim card problem you just need to enable then disable airplane mode instead of reinserting it.
---------- Post added at 21:21 ---------- Previous post was at 21:20 ----------
Did anyone managed to install V4A on this rom? I installed it but the driver isn't functional.
lucyr03 said:
For the sim card problem you just need to enable then disable airplane mode instead of reinserting it.
Click to expand...
Click to collapse
Aha, good idea. It seems this sim card issue is only happening on m7 if build m7vzw first. Next builds I will make clean & run m7 first then will see if problem still exist.
lucyr03 said:
For the sim card problem you just need to enable then disable airplane mode instead of reinserting it.
---------- Post added at 21:21 ---------- Previous post was at 21:20 ----------
Did anyone managed to install V4A on this rom? I installed it but the driver isn't functional.
Click to expand...
Click to collapse
Is that video related?
icxj1 said:
Is that video related?
Click to expand...
Click to collapse
I don't know about video, it just shows driver: abnormal, neon: no, audio processing: unsupported and of course any settings have no effect.
lucyr03 said:
I don't know about video, it just shows driver: abnormal, neon: no, audio processing: unsupported and of course any settings have no effect.
Click to expand...
Click to collapse
Aha, oK. I will look into it. Thanks
lucyr03 said:
Flash this zip in twrp to fix safetynet, I tested it and working fine on this rom.
https://www.androidfilehost.com/?fid=962187416754455235
Click to expand...
Click to collapse
Thanks, THAT'S IT. Great.
---------- Post added at 08:13 PM ---------- Previous post was at 08:00 PM ----------
I see, it's working very well.
- Video recording in Camera app is not working (as told before by some other member).
- GPS is marked as "Supported" but Enabled "No", and not possible to enable (but working GPS is important to me, so we have to wait for the devs and their great work).
- IR is marked as "Not supported" - even it is in the device -, sigh (it's not really very important to me, but it's "nice to have").
- Mobile data work correctly, but it's impossible yet to switch it off.
- WiFi works to me, even reconnects.
Thanks again,
samhhmobil
lucyr03 said:
For the sim card problem you just need to enable then disable airplane mode instead of reinserting it.
Click to expand...
Click to collapse
tried this, but not working, still had to reinsert it, at least on my device (international version)
olivrd said:
tried this, but not working, still had to reinsert it, at least on my device (international version)
Click to expand...
Click to collapse
I have international version too but with GPE firmware.
Sent from my OnePlus 2 using XDA Labs
lucyr03 said:
I have international version too but with GPE firmware.
Click to expand...
Click to collapse
same here

[ROM][UNOFFICIAL]LineageOS-15.1[Evert][Moto G6 Plus]

{
"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 Build
- TWRP : Get here
Bugs
bluetooth calling
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
A big thanks to @erfanoabdi to kick start the development.
XDA:DevDB Information
LineageOS, ROM for the Moto G6
Contributors
rahulsnair, erfanoabdi
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP
Based On: LineageOS
Version Information
Status: Beta
Created 2018-08-11
Last Updated 2018-08-11
Copy Partition- Initial Setup
Flash the attachement via TWRP
Hi.....after revert from this ROM tô stock....ill lose some thing? Ex....volte.....câmera...etc... Efs backup ok
Already noticed this rom and the new TWRP on his androidfilehost and saw it posted on another site too, might try it soon
However, what exactly does the AB zipfile do exactly? And another question, on his AndrFilehHost he has an outdated TWRP installer Zip, is there any reason the new TWRP's are only bootable images? I'd gladly know why to stick with just booting rather then flashing TWRP?
Also thanks for the effort, i'll give the ROM a try and will report back my experiences..
edit: also, i had no problems with opengapps on treble roms, what makes it problematic for this rom?
Coldstream said:
Already noticed this rom and the new TWRP on his androidfilehost and saw it posted on another site too, might try it soon
However, what exactly does the AB zipfile do exactly? And another question, on his AndrFilehHost he has an outdated TWRP installer Zip, is there any reason the new TWRP's are only bootable images? I'd gladly know why to stick with just booting rather then flashing TWRP?
Also thanks for the effort, i'll give the ROM a try and will report back my experiences..
edit: also, i had no problems with opengapps on treble roms, what makes it problematic for this rom?
Click to expand...
Click to collapse
This device is an A/B device which means it does have two slots.One will be active (running slot) and other will be used for updating system (if any OTA is available) Opengapps doesn't support A/B devices yet.
AB zipfile makes a backup of your active slot so that your device won't get bricked after flashing lineage.
I know that the G6 Plus is A/B, but i don't get what the problem is with opengapps. I flashed them just fine for the treble roms i tried. The only thing i did was flash opengapps straight after the treble rom, without rebooting. It might not be fully working with A/B devices, but they surely worked for the treble roms i tried, that's why i asked. And yes, i think i didn't read it properly the first time. Now it makes sense, though i just got a script to go back to full stock ready anyways. Anyways, again big thanks to both of you.
Maybe @erfanoabdi can say something about the TWRP files? I will probably finally have some time to flash the rom with an hour or so, and gladly report back later.
edit: oops, i totally forgot something here, you are probably talking about OTA lineage updates, while i was not even thinking on that. If that's the case, then it makes sense
david.gs.gm said:
Hi.....after revert from this ROM tô stock....ill lose some thing? Ex....volte.....câmera...etc... Efs backup ok
Click to expand...
Click to collapse
You will loose volte I believe. You will loose the Los camera app but gain the moto camera app.
Coldstream said:
I know that the G6 Plus is A/B, but i don't get what the problem is with opengapps. I flashed them just fine for the treble roms i tried. The only thing i did was flash opengapps straight after the treble rom, without rebooting. It might not be fully working with A/B devices, but they surely worked for the treble roms i tried, that's why i asked. And yes, i think i didn't read it properly the first time. Now it makes sense, though i just got a script to go back to full stock ready anyways. Anyways, again big thanks to both of you.
Maybe @erfanoabdi can say something about the TWRP files? I will probably finally have some time to flash the rom with an hour or so, and gladly report back later.
edit: oops, i totally forgot something here, you are probably talking about OTA lineage updates, while i was not even thinking on that. If that's the case, then it makes sense
Click to expand...
Click to collapse
Opengapps will work it just won't survive an update.
As for twrp, they were buggy more or less. For example the first 3 builds weren't able to decrypt data on the internal SD card. That applies to the twrp zip as well. The 4th build supported decryption but had some lag. Go with the latest twrp build but it does lack mtp for example.
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
You will loose volte I believe. You will loose the Los camera app but gain the moto camera app.
Opengapps will work it just won't survive an update.
As for twrp, they were buggy more or less. For example the first 3 builds weren't able to decrypt data on the internal SD card. That applies to the twrp zip as well. The 4th build supported decryption but had some lag. Go with the latest twrp build but it does lack mtp for example.
Click to expand...
Click to collapse
Yeah i noticed that, but is there any specific reason to stick with fastbooting it rather then flashing? The flashable zip is a very old version, but the newer ones of the last few days might be better? Since there is no documentation with them on the androidfilehost, it's a bit of a gamble what is changed in each of his versions. I'd happily flash the latest version if possible, but it would be usefull to know if there would be any reason not to. Considering there is no new flashable zip i suspect there is at least one reason to stick to fastbooting it over flashing, but again without knowing its still a gamble.
Anyways, every progress done on the G6 Plus is more then welcome, so i'm more then happy so far
Moto app (with gestures and Moto screen) will works with custom roms? I never had Motorola phone before. Good to see that development of g6 plus starts.
Do you mind upload the ROM to an alternative file hosting website?
AFH is really slow even with an gigabit internet connection and it always ends up as Failed - Network error.
If you become a developer, join our group at Telegram:
https://t.me/joinchat/GdyK5BB44joobth3umlAJA
The SU addon can't be flashed, some error in path symbolic something with a sh script, will dump log later i don't have a PC around for now.
Also the LineageOS recovery can't handle the encryption.
WYPIERDAALAAC said:
Moto app (with gestures and Moto screen) will works with custom roms? I never had Motorola phone before. Good to see that development of g6 plus starts.
Click to expand...
Click to collapse
The Moto app itself won't work but the actions are intergrated.
Editie: noticed the SU addon is removed from the OP, i'd suggest keeping us updated here aswell because i'm sure others reported it, but if others report it on another place then it would be much more usefull to at least keep us updated here to prevent people running in the same issues, and dumping the same logs but just on different locations? Also as it is now, obviously only ADB root can be chosen in dev settings.
Coldstream said:
The SU addon can't be flashed, some error in path symbolic something with a sh script, will dump log later i don't have a PC around for now.
Also the LineageOS recovery can't handle the encryption.
The Moto app itself won't work but the actions are intergrated.
Editie: noticed the SU addon is removed from the OP, i'd suggest keeping us updated here aswell because i'm sure others reported it, but if others report it on another place then it would be much more usefull to at least keep us updated here to prevent people running in the same issues, and dumping the same logs but just on different locations? Also as it is now, obviously only ADB root can be chosen in dev settings.
Click to expand...
Click to collapse
If I do understand right moto gestures are intergrated in system settings of lineageOS? What about face recognition ?
Lineage alternative links:
Google Drive:
https://drive.google.com/file/d/1hKeKp5WmWhGkkHAVfSgDu10GObQv_QiK/view?usp=drivesdk
Mega:
https://mega.nz/#!SNt3hLxR!AJ5k0krEiCvHG9MiE3MsirYxhHO9z_j9vYsr-pbRjBo
Finally! Some development going on for Evert! I'll still wait a while before unlocking the bootloader, because I'm afraid that the A/B system bricks my device. Furthermore bluetooth calling is important to me, so I hope this will be solved soon. Is everything else working so far?
smitharro said:
Finally! Some development going on for Evert! I'll still wait a while before unlocking the bootloader, because I'm afraid that the A/B system bricks my device. Is everything working so far?
Click to expand...
Click to collapse
If there's anything i've learned so far from the A/B system, it's a good improvement. Nothing i'd be affraid of. What makes u scared? I've ran a lot of the treble roms with different outcomes but going back to full stock is fairly easy so far and right now i'm running this rom.
Obviously i'm not going to say that you can't brick it or should take things too easy, but with just simply understanding the actions your taking it's nothing to be affraid of. Besides, when you flash stock running on A straight to B, and run into troubles with something flashed on A u can switch rather easy is my experience.
Coldstream said:
Yeah i noticed that, but is there any specific reason to stick with fastbooting it rather then flashing? The flashable zip is a very old version, but the newer ones of the last few days might be better? Since there is no documentation with them on the androidfilehost, it's a bit of a gamble what is changed in each of his versions. I'd happily flash the latest version if possible, but it would be usefull to know if there would be any reason not to. Considering there is no new flashable zip i suspect there is at least one reason to stick to fastbooting it over flashing, but again without knowing its still a gamble.
Anyways, every progress done on the G6 Plus is more then welcome, so i'm more then happy so far
Click to expand...
Click to collapse
At this time the dev has had issues building an updated zip installation for twrp but it will probably be resolved soon.
Coldstream said:
The SU addon can't be flashed, some error in path symbolic something with a sh script, will dump log later i don't have a PC around for now.
Also the LineageOS recovery can't handle the encryption.
The Moto app itself won't work but the actions are intergrated.
Editie: noticed the SU addon is removed from the OP, i'd suggest keeping us updated here aswell because i'm sure others reported it, but if others report it on another place then it would be much more usefull to at least keep us updated here to prevent people running in the same issues, and dumping the same logs but just on different locations? Also as it is now, obviously only ADB root can be chosen in dev settings.
Click to expand...
Click to collapse
You can flash magisk 16.7 beta and root will work fine.
smitharro said:
Finally! Some development going on for Evert! I'll still wait a while before unlocking the bootloader, because I'm afraid that the A/B system bricks my device. Furthermore bluetooth calling is important to me, so I hope this will be solved soon. Is everything else working so far?
Click to expand...
Click to collapse
Nothing to worry about with AB. It's a good thing.
Bluetooth calling is being worked on.
Sent from my moto g(6) plus using Tapatalk
Guys, Is it possible do a similar port to ALJETER (Moto G6 Play) variant too?
Anyone running xposed? Any issues?
Updated process ended with ERROR: 1
When I try to flash this rom to my moto g6 plus, I get this error: error applying update: 7 (errorcode:: kInstallDeviceOpenError) Updated process ended with ERROR: 1
What's wrong here?

[ROM][UNOFFICIAL]LineageOS-16.0[Evert][Moto G6 Plus]

{
"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?

[ROM][H830|H850|RS988] UNOFFICIAL LineageOS-17.1 for G5

{
"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"
}
Disclaimer
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.
Introduction
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device. More info.
These are my UNOFFICIAL builds of LineageOS-17.1 for LG G5 variants. I did NOT create this ROM. I am helping to contribute to this ROM. Thanks to all other coders who contributed to LineageOS.
IMPORTANT
BACKUP! These are UNTESTED builds. Please be ready to recover your previous ROM. If it kernel panic, boots into bootloader, etc... grab as much info as you can.
Builds are done periodically (see download below)
Do NOT be rude.
Respect all users.
Any and all users, please help each other. I have a rs988 variant, so other variants might have some issues.
This now runs System-As-Root. Ie.. / and /system are merged, so /system is really /, and /system is /system/system.
For broken issues see 2nd post
Issues:
WiFi or Bluetooth MAC is "00:00:00:00:00:00" - You wiped the misc partition, you'll need to fix: https://forum.xda-developers.com/showpost.php?p=70474540&postcount=12 (Should be fixed by static hax thanks for @Blaises)
5Ghz tether not working due to "error"
Install
You can upgrade from 15.1 (UNOFFICIAL) to 16.0 to 17.1. If you are not on my UNOFFICIAL yet, flash the to-x86cpu.zip first (and reboot recovery before upgrade, not reboot into system).
Flash to-x86cpu.zip if needed. (See Downloads below)
Flash UNOFFICIAL ROM
Wipe cache, and dalvik cache
Magisk if you choose
Flash GAPPS (I use nano)
Reboot and wait....
Bugs
If you encounter issues/bugs that are not known, please report. This is not the OFFICIAL ROM, but I can help to get any issues fixed. I use the rs988 variant. If I can replicate your issue then I can track it down. If I cannot, please provide as much detail as possible. Logcats are great. (See post #3)
Please indicate what G5 variant you have (h830, h850, rs988) and the dated version. Any mods (no judgment) as well.
I am aware people run mods or change things. I am not against it (as I do myself). However, if needed I may ask you to data wipe (you can say no), or remove a mod that might be interfering. I will do the best I can.
Thanks
Any and all users in this thread who contributed or will contribute to making this ROM as stable as possible
LineageOS Team
@Rashed97 for continuing
@Blaises[/MENTION] for Bluetooth and WiFi static hax if all 00s.
@npjohnson for help along the way.
Downloads
ROM: UNOFFICIAL downloads (Note date)
Gapps: arm64 nano 10.0
Sources
https://github.com/LineageOS
https://github.com/LineageOS/android_kernel_lge_msm8996
https://github.com/LineageOS/android_device_lge_msm8996-common
https://github.com/LineageOS/android_device_lge_g5-common
h830
h850
rs988
What is working:
WiFi
Camera
GPS
NFC
2.4 Ghz Hotspot
USB OTG
What is NOT working:
VoLTE and WiFi calling do not (and most likely never will).
5.0 Ghz Hotspot
Encrpytion is untested, so it may fail.
Anything else NOT listed above might or might not work. I will adjust as necessary and reports. If anyone has any knowledge and can troubleshoot and fix the NOT working items, let me know.
Here is how I capture logs. You need to ensure you can do this right at boot and will need to setup ahead of time.
You need to have root, either su, or "adb root". Verify you can get root quickly.
Here are the steps I do to accomplish this. This is a Linux system, so windows will vary slightly.
Reboot the phone while plugged into the computer.
At a shell, keep attempting to get root/shell:
Code:
adb root ; adb shell
Once connected, immediately paste the following (to capture logs).
Code:
cd /cache
nohup dmesg -w > dm &
nohup logcat -b all > lc &
If you have root installed via Magisk as "su":
Reboot the phone while plugged into the computer.
At a shell, keep attempting to get root/shell:
Code:
adb shell
Once connected, immediately paste the following (to capture logs).
Code:
su
cd /cache
nohup dmesg -w > dm &
nohup logcat -b all > lc &
Once Phone reboots, or boots up. The needed files are in /cache "lc" and "dm", and are available in TWRP even.
Thank you for your efforts and support. I will try as soon as possible
Sent from my LGE LG-H850 using XDA Labs
Thanks, @x86cpu I'll start working on my new threads for Havoc OS and Pixel Experience. I was also curious about this commit does this have anything to do with going Official.
ROMSG said:
Thanks, @x86cpu I'll start working on my new threads for Havoc OS and Pixel Experience. I was also curious about this commit does this have anything to do with going Official.
Click to expand...
Click to collapse
That's just the wiki getting added.
https://review.lineageos.org/c/LineageOS/hudson/+/267517
That above is more what you might be looking for.
x86cpu said:
That's just the wiki getting added.
https://review.lineageos.org/c/LineageOS/hudson/+/267517
That above is more what you might be looking for.
Click to expand...
Click to collapse
Ok kind of a noob question, but what is the wiki sorry for asking.
ROMSG said:
Ok kind of a noob question, but what is the wiki sorry for asking.
Click to expand...
Click to collapse
The wiki page is just information about the device, how to install Lineage, etc..
Preview: https://harryyoud.co.uk/lineage-previews/217514/11/devices/rs988/
hudson is the build server repo, and what order and how often to build for, like "N"ightly, or "W"eekly. Once 17.1 is official, most 16.0 goes to Weekly builds, and 17.1 goes to Nightly.
x86cpu said:
The wiki page is just information about the device, how to install Lineage, etc..
Preview: https://harryyoud.co.uk/lineage-previews/217514/11/devices/rs988/
hudson is the build server repo, and what order and how often to build for, like "N"ightly, or "W"eekly. Once 17.1 is official, most 16.0 goes to Weekly builds, and 17.1 goes to Nightly.
Click to expand...
Click to collapse
Ok Thanks so much, sorry for the Noob question I'm still learning.
i tries gapps and nikgapps and bit gapps no one is letting me go after final touch screen. even i skip setup wizard still setup wizard crashing errer popups continusly. i now removed setup wizard from twrp and started the rom...
---------- Post added at 04:56 PM ---------- Previous post was at 04:19 PM ----------
it has same bugs as romsg 17.1.
google camera processing hdr stucks at 100%
after reboot lockscreen takes 1 minute to accept password.
battery life is a bit bad
till now i saw these issues.
rest is perfect
thank u sir for this rom..
just perfect
just did a dirty flash, coming from 16.0. -->
wiped davlik and cache before, and then... everyhting went perfectly fine
all settings and apps still alive and functional.
quick check... wifi, bluethooth working fine, camera as well.
I'm very happy, thank you! :victory: :highfive:
Also i started the new oc kernel for Android 9 and 10. Hope i will release soon.
Sent from my LGE LG-H850 using XDA Labs
Tried doing a clean flash and I can't seem to get past the setup screen. When I get to the last screen where it asks to set up a few more things, when I tap finished for now, I get a FC and I can't finish the setup.
Using RS988 with opengapps 10 nano 1.24.2020 and magisk 20.3.
Steps used:
Wipe data, cache/dalvik and system
Flash LOS17
Flash Gapps
Flash Magisk
Reboot
I'll try gapps 1.23.2020 and report back.
This is a buggy setup wizard. Try to delete the setup wizard via twrp and it should boot up normally.
---------- Post added at 09:30 PM ---------- Previous post was at 09:26 PM ----------
I have no NFC. Can only turn it on via Quick settings. No menu in network settings. Turning it on in quick settings has no effect. Prior to this ROM I had Romsg's version installed. But with the same behavior. Does anybody know a solution?
djskribbles said:
Tried doing a clean flash and I can't seem to get past the setup screen. When I get to the last screen where it asks to set up a few more things, when I tap finished for now, I get a FC and I can't finish the setup.
Using RS988 with opengapps 10 nano 1.24.2020 and magisk 20.3.
Steps used:
Wipe data, cache/dalvik and system
Flash LOS17
Flash Gapps
Flash Magisk
Reboot
I'll try gapps 1.23.2020 and report back.
Click to expand...
Click to collapse
fscout42 said:
This is a buggy setup wizard. Try to delete the setup wizard via twrp and it should boot up normally.
---------- Post added at 09:30 PM ---------- Previous post was at 09:26 PM ----------
I have no NFC. Can only turn it on via Quick settings. No menu in network settings. Turning it on in quick settings has no effect. Prior to this ROM I had Romsg's version installed. But with the same behavior. Does anybody know a solution?
Click to expand...
Click to collapse
I ended up just flashing LOS16 and dirty flashing to 17.1.
Everything seems to be working except NFC and the camera seems really buggy, even after reboot. Can't save to external sd card, and recorded video can't be played. Also as mentioned above, gcam doesn't work either. Using arnovas advanced 1.7 that worked great on los16.
Roboxl said:
just did a dirty flash, coming from 16.0. -->
wiped davlik and cache before, and then... everyhting went perfectly fine
all settings and apps still alive and functional.
quick check... wifi, bluethooth working fine, camera as well.
I'm very happy, thank you! :victory: :highfive:
Click to expand...
Click to collapse
BT calls works? Or only music?
Wysłane z mojego LG-H850 przy użyciu Tapatalka
Trying out the new build on my H830 and it's good so far. I've dirty flashed from 16.0 using NikGapps core and Magisk 20.3.
I want to note some bugs along with some workarounds:
1. Camera is buggy on first boot (restarting seems to fix this)
2. Recorded videos fail to play (keep pressing play and will play eventually though audio isn't working, videos from previous versions play fine, it's possible that other camera apps don't have this)
3. Gcam not working (use urnyx05's gcam v2.1, works fine on both 9 & 10)
4. Interactive governor is maxing the CPU (gave a decent boost in battery in 16.0)
5. Powersave governor can freeze the camera when in video mode/recording (use default governor)
6. Lockscreen pin is slow on boot (just wait a little it will unlock)
7. Brightness slider still needs adjusting (Turn off autobrightness and use values between 70-90% for decent indoor screen brightness)
8. Google Play downloads can be slow regardless of GApps package and when on wifi/mobile data (Been happening to me since 15.1 and only happens to some, just pause and resume a few seconds later is the workaround I do)
9. Audio files can take a while to load when switching between audio sources like wired & wireless headphones (no workaround will began playing in a bit)
thanks a lot:victory::victory:
Sent from my LG-H830 using XDA Labs
inhave a solution delete lineagesetupprebuilt from twrp and setup will succed lineage setup is causing problem....
delete system/priv-apps/lineagesetupprebuilt...
Ismrocks1234 said:
inhave a solution delete lineagesetupprebuilt from twrp and setup will succed lineage setup is causing problem....
delete system/priv-apps/lineagesetupprebuilt...
Click to expand...
Click to collapse
You can delete every system and user app in OrangeFox recovery.
Sent from my LGE LG-H850 using XDA Labs

[ROM][OFFICIAL][hotdogb][10] RESURRECTION REMIX [Sept 9 2020]

[10.0][OFFICIAL]Resurrection Remix v8.x [device_code]
{
"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 Q
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. For 7T: Be sure to be on latest oos, beta or stable is fine (flash both slots prior to installing the rom)
Download the latest Resurrection Remix Rom (currently on V8.6)
(7T builds gave gapps included) so disregard flashing gapps.)
You can use either twrp (mauronfrios latest or Chinese) to flash the rom.
Additionally - you can unpack the bin that is in the zip and fastboot flash as many other roms. SEE POST#4!! Importantly, after flashing, no matter the method, once you see the RR boot logo, force reboot to bootloader mode, and use the buttons to cycle to recovery. Select this as it will now reboot to the roms recovery. Go to wipe data. Wipe data and now reboot. This is mandatory if you flash via twrp or want to run f2fs vs ext4; bc the rom will run very well on f2fs as it is much faster file system than ext4.( Once you format after the first flash.) If using twrp, the first boot sets it as this but unless a format is done, it will not boot. So, do not skip this step. After the data wipe and rebooting, the rom boots up in a few Mins. If it doesn't boot in 5mins. You may have made a mistake and in that case reflash stock to both slots and try again.
Yes, Ota updates work fine, be sure to go to updater and prioritize update process. I usually send a build every couple days.
You can retain root by after the download and install occurs but before reboot, launching magisk manager and installing to opposite slot and then rebooting.
**Ota will not work unless RR is on both slots before taking ota. To fix that, after you get it booted, boot to bootloader and fastboot set_active other, and reflash via fastboot. OR if you used twrp, flash the ota again and it puts it on the opposite slot.
Neutrino Kernel is built in-line, latest Hoth 1.95
​
Make sure you have a custom recovery installed(TWRP is the preferred recovery)
Download the latest Resurrection Remix Rom & the latest GApps package
Boot into recovery
Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution
Flash ResurrectionRemix Rom
Flash Google Apps package(Optional)
Flash Magisk Root(Optional)
First boot may take up to 10 minutes.
ROM Download
GApps
Resurrection Remix Source
Device Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
AICP
Crdroid
AOSIP
DU
Xtended
Evolution X
Bliss
Omni Team
And Of Course To All The Supporters, Donators And Users
Join our Telegram channel : https://t.me/resurrectionremixchat
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.​
​
Current download and details:https://forum.xda-developers.com/showpost.php?p=83469869&postcount=465
7T TG Chat https://t.me/rr_op7t
Payload Dumper
https://drive.google.com/open?id=1Q5Cq9nAXWvjw9z6wgCDfQi40qk4mw3ut
Thanks for this! Glad to see you here as well
Here are some more detailed instructions by my long time constituent @aer0zer0 thank youuuu!!!
how to extract a payload and flash a rom for noobs, windows only
pre-requisites:
1. In general, you want to have the SAME version of OOS on both sides. Im not going to go into detail on how to MSM, and flash a full OTA locally, reboot, then flash the same OTA locally again and reboot.
2. payload dumper for windows: https://drive.google.com/file/d/1Q5Cq9nAXWvjw9z6wgCDfQi40qk4mw3ut/view?usp=sharing its windows 64 bit only
3. Latest ADB/Fastboot binaries: when flashing using using a script, and you see errors such as system partition cannot be found, etc... your binaries are old, most likely cause by some ghetto version minimal adb/fastboot thats jank. To verify where your adb/fastboot is running from, in a shell, type fastboot --version this will tell you where you resident adb/fastboot binaries are running from. The link to updates binaries is here https://developer.android.com/studio/releases/platform-tools select the windows SDK version. Once downloaded, copy and paste them over top of the ones being used from the fastboot --version output.
4. a bat file to flash all the images you are dumping. https://drive.google.com/file/d/1HW1Q82wpsnBPUcPkAnXO-tQjVIWSZ_oQ/view?usp=sharing this wipes, goes to fastbootd, will flash all the images from the payload.bin dump to both sides, wipes, and sets it to boot from slot A.
5. lots of common sense
Instuctions
1. extract the payload dumper somewhere on your PC, you will see an "IN" folder, "OUT" folder, and an executable.
2. extract the payload.bin file from the rom.zip you wish to install, and place it in the "IN" folder.
3. run the payload dumper exectuable, a shell will pop up, showing the images being extracted.
4. once the shell closes, the images are all succesfully unpacked. Copy those images in the "OUT" folder to whereevr you would like to store your rom.
5. copy/paste the bat file wherever you placed your images.
6. reboot your phone to fastboot, plug it into the PC, and run the bat.
7. process takes 4-5 minutes, sit back, it will then reboot back to fastboot.
8. start the phone from fastboot, and wait for your new rom to boot.
9. finish and enjoy!
Also, there is no real bugs. On occasion one may think there is a bug, and if there is in fact one, we work promptly to resolve it as a team. Typically, one thinks a bug is a bug, but the rom has so many features, it is just a conflicting setting most likely, I implore you all to exercise trial and error. If something was fine and you fiddled with settings, go unfiddle and see what could make something not work. We could not foolproof all features to not conflict on the occasion if we get kinda crazy with what we expect our device and it's software to be able to do. All works flawlessly. Enjoy the rom and thanks to my colleagues and my friends who have always been there in this wonderful android world, never quick to judge, always quicker to help and teach. Never from the class of elitist android dev who is "too cool" to just be nice. Thanks guys.
The names below have helped me in numerous ways over the years, thanks for the help, support, and overall non-douchebaggery activities:
KangaroosterMeadows-Where the magic happens
@wrongway213
@aer0zer0
@xstefen
@NoSpamDan
@varund7726
@Freak07
@return.of.octobot
@abalam
@hondajohn
@Neo
@unixandria
@fKm
@lil_kujo
@kdp162
@omariscal1019
@DeathStroke
@risasuke
JackEagle-his guides and advice in chat, Anthony P, DPryor, Cody S, and everyone else I haven't named. Thanks also go to AOSiP- for solid trees that most of us all use.
Congrats @FullOfHell what a great rom
Just installed it and I'm liking every bit of it thank you @FullOfHell!
I am touched! I was losing hope for this device. thank you!
Thanks! Will try it soon.
Enviado de meu HD1903 usando o Tapatalk
Face unlock included? How about Fp? Works great, even with low brightness?
Kollachi said:
Face unlock included? How about Fp? Works great, even with low brightness?
Click to expand...
Click to collapse
yes faceunlock is included and fingerprint works flawlessly, low light, no light, any situation
Kollachi said:
Face unlock included? How about Fp? Works great, even with low brightness?
Click to expand...
Click to collapse
Yes fp works great even with nightlight on , face unlock is also included . It's a super solid rom
lil_kujo said:
Yes fp works great even with nightlight on , face unlock is also included . It's a super solid rom
Click to expand...
Click to collapse
Thanks man appreciate it. Hope you enjoy it
The news of a stable ROM coming to 7T just made my day. I want to heartily thanks the developer who invested their told in building this goodness.
Also would payment apps work on this ROM? Maybe someone could confirm the same? I am preety new to the ROM scene these days but have some past experience ages ago, I have heard Magisk safety net would work?
Also I wouldllike to know do stable ROMs like these have om par camera performance as the stock builds of OOS does? Or can we make it work just as better with installing a supported Gcam build here from forums?
AnkeshReborn said:
The news of a stable ROM coming to 7T just made my day. I want to heartily thanks the developer who invested their told in building this goodness.
Also would payment apps work on this ROM? Maybe someone could confirm the same? I am preety new to the ROM scene these days but have some past experience ages ago, I have heard Magisk safety net would work?
Also I wouldllike to know do stable ROMs like these have om par camera performance as the stock builds of OOS does? Or can we make it work just as better with installing a supported Gcam build here from forums?
Click to expand...
Click to collapse
I recommend latest arnovo gcam for optimum photography.
I don't know if gpay works as I only use PayPal, but safety net passes. Happy it made your day. Enjoy
FullOfHell said:
I recommend latest arnovo gcam for optimum photography.
I don't know if gpay works as I only use PayPal, but safety net passes. Happy it made your day. Enjoy
Click to expand...
Click to collapse
Great to know the safety net passes.
Would just leave a message here asking if any forum member based from India installing RR can confirm if the payment apps like PayTM, PhonePe and the likes of it work? It's the just last thing that's stopping me from getting this beauty on 7T.
Along with info of banking apps, i would also like to know if this has auto call recording feature ? 90hz display support ?
Also I would like to know the proper install instructions for this ROM, I tried searching for this but feels like I'm a bit lost. Thank you for helping out :victory
shetty_chadda said:
Along with info of banking apps, i would also like to know if this has auto call recording feature ?
Click to expand...
Click to collapse
No call recording feature as the lineage dialer is overridden for gapps, ie google dialer. Find a 3rd party app/mod. Sorry, I tried adding the option to allow the user to pick los dialer or google dialer, it but broke other things the majority of users need over call recording. Yes, 90hz support. 60/90 or auto
AnkeshReborn said:
Also I would like to know the proper install instructions for this ROM, I tried searching for this but feels like I'm a bit lost. Thank you for helping out :victory
Click to expand...
Click to collapse
It's easy. Use twrp, or unpack the bin file in the rom and flash with fastboot. same as other roms, just must format after install and reboot.

Categories

Resources