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

Search This thread

MR1865

Member
Feb 8, 2016
15
2
I'm sorry I just can't figure out, how to install the August Update.
The May Update no problems to install.
Every Time I use your method above I'm stuck in a Boot Loop.

You are not alone friend.

I was able to flash the update once, but it didn't take and just powered off the phone every few minutes at random. Was completely unusable for me.

Note of caution, somehow in all the flashing of different things I managed to wipe/corrupt my EFS/Persist partitions, which has now led to major issues with 4G and Wifi on my device (shutting off and on every 30 seconds or so). Learn from my own idiocy and make sure to take a back up of the efs and persist partitions and save it OFF the device. Will save a lot of headaches in case something bad happens (as it did for me).
 
  • Like
Reactions: Gleanfast

Dave-C

Member
May 27, 2014
21
1
You are not alone friend.

I was able to flash the update once, but it didn't take and just powered off the phone every few minutes at random. Was completely unusable for me.

Note of caution, somehow in all the flashing of different things I managed to wipe/corrupt my EFS/Persist partitions, which has now led to major issues with 4G and Wifi on my device (shutting off and on every 30 seconds or so). Learn from my own idiocy and make sure to take a back up of the efs and persist partitions and save it OFF the device. Will save a lot of headaches in case something bad happens (as it did for me).

Can't believe you say that, same thing happened to me already, about 3 weeks ago.
Same issues with the wifi on/off and no 4G.

Could manage to get wifi back to normal, but 4G still off.
Maybe I got lucky since I made a persist backup couple of months ago, howeever couldn't figure out so far, how to restore it correctly.

After all, have to setup a G6+ for a friend, I'm going with the RR May Version for now.
 

Gleanfast

Member
Dec 20, 2018
22
7
You are not alone friend.

I was able to flash the update once, but it didn't take and just powered off the phone every few minutes at random. Was completely unusable for me.

Note of caution, somehow in all the flashing of different things I managed to wipe/corrupt my EFS/Persist partitions, which has now led to major issues with 4G and Wifi on my device (shutting off and on every 30 seconds or so). Learn from my own idiocy and make sure to take a back up of the efs and persist partitions and save it OFF the device. Will save a lot of headaches in case something bad happens (as it did for me).


I also lost wifi, as on and off and then after reinstall attempt lost all connections mobile no sim no imie.

Wiped everything then flashed latest latest stock ROM fixed everything but hotspot, installed Aug RR, fixed hotspot.

---------- Post added at 02:05 AM ---------- Previous post was at 01:15 AM ----------

I'm sorry I just can't figure out, how to install the August Update.
The May Update no problems to install.
Every Time I use your method above I'm stuck in a Boot Loop.

Again my steps (correct me if something wrong)

TWRP: wipe (data,system,cache) - Format Data
TWRP: Install RR August
TWRP: Install DM
After that anything failes in a bootloop

If it won't boot then try format just data again after boot attempt. The OP also recommended doing it twice in the install instructions first post.

Is it showing the RR boot animation, or just going from the Moto logo to freeze?

My first boot took me to RR recovery with "can not load Android system" so I wiped/format data in RR recovery then it booted after about 3 minutes. OP states give up to ten minutes.

Also, are you just trying to install the update alone or decrypt so you can install TWRP?

And yes in fastboot TWRP:
wipe everything
format data

Aug RR
dm-verity (only if you want to decrypt and install TWRP after decrypt, has to be the jlb ramdisk from OP.)


Boot, if no; try to boot to RR recovery from bootloader and
Format data again, should boot.

Let me know. My XT-1927 coming from latest stock ROM (RELTA DS) reflash is working with Aug RR, and have TWRP and magisk.

I did have a problem with one slot so try alternate.

I will repeat it again if you can't get it.

---------- Post added at 02:16 AM ---------- Previous post was at 02:05 AM ----------

I'm sorry I just can't figure out, how to install the August Update.
The May Update no problems to install.
Every Time I use your method above I'm stuck in a Boot Loop.

Again my steps (correct me if something wrong)

TWRP: wipe (data,system,cache) - Format Data
TWRP: Install RR August
TWRP: Install DM
After that anything failes in a bootloop

See my last post I accidentally posted to Dave c who replied to yours
 

MR1865

Member
Feb 8, 2016
15
2
I also lost wifi, as on and off and then after reinstall attempt lost all connections mobile no sim no imie.

Glad that fixed it in your case. I flashed the newest version multiple times to no avail.

My XT-1927 coming from latest stock ROM (RELTA DS) reflash is working with Aug RR, and have TWRP and magisk.

Do you mean the RETLA version? I flashed the RETLA DS version on my XT-1927 and nothing worked after that (IMEI, Wifi, etc...)

My first boot took me to RR recovery with "can not load Android system" so I wiped/format data in RR recovery then it booted after about 3 minutes. OP states give up to ten minutes.

Mine did the same, however after that I could not boot into recovery. It would restart as soon as it got into recovery if I tried (less than 2 seconds). I tried formatting data from that, but it would restart every time.

Boot, if no; try to boot to RR recovery from bootloader and
Format data again, should boot.

Got the August update to boot using this, but it just continually reboots after the initial boot into the ROM. Making it unusable.
 
Last edited:

Gleanfast

Member
Dec 20, 2018
22
7
Glad that fixed it in your case. I flashed the newest version multiple times to no avail.

You can try blank flash if not already. Sounds like you need a clean start.

https://forum.xda-developers.com/g6-plus/how-to/ultimate-guide-how-to-unbrick-moto-g6-t3862927

Do you mean the RETLA version? I flashed the RETLA DS version on my XT-1927 and nothing worked after that (IMEI, Wifi, etc...)

Yeah RELTA DS for my XT 1926-7 worked.

Mine did the same, however after that I could not boot into recovery. It would restart as soon as it got into recovery if I tried (less than 2 seconds). I tried formatting data from that, but it would restart every time.

Maybe try fastboot TWRP and format data again. Mine did not boot till I did that.

Got the August update to boot using this, but it just continually reboots after the initial boot into the ROM. Making it unusable.

Have you tried the May RR is not encrypted.
 

MR1865

Member
Feb 8, 2016
15
2
You can try blank flash if not already. Sounds like you need a clean start.

https://forum.xda-developers.com/g6-...to-g6-t3862927

I have never had luck with the blankflash. I have tried multiple PC's in both Linux and Windows and basically never get a connection. Just "< waiting for device >" perpetually. Hoping I will be able to get it to work at some point. But so far no joy.

Have you tried the May RR is not encrypted.

The May RR works in terms of the install. But fixes nothing in terms of my 4G or Wifi.
 
  • Like
Reactions: Gleanfast

Gleanfast

Member
Dec 20, 2018
22
7
I have never had luck with the blankflash. I have tried multiple PC's in both Linux and Windows and basically never get a connection. Just "< waiting for device >" perpetually. Hoping I will be able to get it to work at some point. But so far no joy.



The May RR works in terms of the install. But fixes nothing in terms of my 4G or Wifi.

Are you getting errors when wiping with TWRP or flashing stock ROM. I got "invalid partition DDR" and "no space available in persist"?

EFS restore failed.

Blankflash did not work for me either "waiting for device"

There is some issue with having a modified boot image from magisk then going to the Aug update with encryption.

Since the blankflash did not work I did a factory reset, wiped everything (system, cache, data etc) and formatted data.

Then booted to the other slot and did the same.

Maybe Overkill but was able to flash RELTA DS and got wifi, mobile etc back then RR Aug.
 

MR1865

Member
Feb 8, 2016
15
2
Are you getting errors when wiping with TWRP or flashing stock ROM. I got "invalid partition DDR" and "no space available in persist"?

The invalid partition error I think is because the partition name is "ddr" not "DDR" so
Code:
fastboot erase DDR
fails. If you change the partition name it will work fine. Do you know what particular command is giving "no space available in persist"? I have not seen that that I have noticed.

Maybe Overkill but was able to flash RELTA DS and got wifi, mobile etc back then RR Aug.

Did not fix wifi or mobile for me. I think the blank flash is my only hope.
 

Gleanfast

Member
Dec 20, 2018
22
7
The invalid partition error I think is because the partition name is "ddr" not "DDR" so
fails. If you change the partition name it will work fine. Do you know what particular command is giving "no space available in persist"? I have not seen that that I have noticed.



Did not fix wifi or mobile for me. I think the blank flash is my only hope.

The "no space in persist" error came when wiping with TWRP.

Using TWRP File Manager under persist/data/ I deleted all but the native files. Don't know if that will help you though. May be worth a try.

If that and blankflash won't work the only thing I can think of is the Lenovo Assistant.
 
  • Like
Reactions: MR1865

Gleanfast

Member
Dec 20, 2018
22
7
What do you mean by the native files?

Persist/data/

Prov
Prov.bak

Keymaster
Keymaster.bak

Widevine
Widevine.bak

I'm pretty sure these can also be cleaned up to and will be rewritten when flashed.


Unfortunately I already went down that road to no effect.

At one point I had lost wifi and mobile and no sims also, only Bluetooth was working, so I know there is someway to fix it. I tried so many things honestly don't know exactly what it was that allowed the RELTA DS to work.

I even tried repairing the file systems in TWRP.
 

Dave-C

Member
May 27, 2014
21
1
Unbelievable, I was finally able to install the August Update, thanks to Gleanfasts manual in post #131.
Seems like everything is working for me at this point.

Howeever I got one small issue.
Thanks to Dev's with the August Update the FM Radio is finally brought back.
When starting the App (Headphones of course connected) and after completing the chanel search, I hear nothing at all.
The Channels are there and after I start recording a channel, it correctly creates the soundfile stored in the fm recording folder.
The soundfile is indeed playable outside the FM Radio App, howeever inside the FM Radio App I hear no sound at all.

Could someone tell me, if i'm doing something wrong?
 
  • Like
Reactions: Gleanfast

Gleanfast

Member
Dec 20, 2018
22
7
Unbelievable, I was finally able to install the August Update, thanks to Gleanfasts manual in post #131.
Seems like everything is working for me at this point.

Howeever I got one small issue.
Thanks to Dev's with the August Update the FM Radio is finally brought back.
When starting the App (Headphones of course connected) and after completing the chanel search, I hear nothing at all.
The Channels are there and after I start recording a channel, it correctly creates the soundfile stored in the fm recording folder.
The soundfile is indeed playable outside the FM Radio App, howeever inside the FM Radio App I hear no sound at all.

Could someone tell me, if i'm doing something wrong?

Have you tried just resetting the storage for the FM app, just a guess. But I'll see if I can replicate the issue on my XT 1926-7
 

Dave-C

Member
May 27, 2014
21
1
Have you tried just resetting the storage for the FM app, just a guess. But I'll see if I can replicate the issue on my XT 1926-7

Would be nice, if You could try it.

Weird thing is, even with a Lineage ROM, months ago, I couldn't get the Lineage FM Radio App (same as in RR) to work.
Howeever the Stock FM Radio App (on a Stock ROM), works perfectly.
Unfortunely the Stock App can't be installed on RR.

Recently I installed (for testing) the Evolution X 2.0 ROM.
It has both FM Radio Apps included, like Above, the Lineage/RR App doesn't work correctly for me, the Stock one works 100%.
Maybe there were others with Issues, so they included both??
 

Gleanfast

Member
Dec 20, 2018
22
7
Would be nice, if You could try it.

Weird thing is, even with a Lineage ROM, months ago, I couldn't get the Lineage FM Radio App (same as in RR) to work.
Howeever the Stock FM Radio App (on a Stock ROM), works perfectly.
Unfortunely the Stock App can't be installed on RR.

Recently I installed (for testing) the Evolution X 2.0 ROM.
It has both FM Radio Apps included, like Above, the Lineage/RR App doesn't work correctly for me, the Stock one works 100%.
Maybe there were others with Issues, so they included both??

I'm having the same issues you described, no live output but it will record and playback is fine in the record.

Have you had any progress?
 

Dave-C

Member
May 27, 2014
21
1
I'm having the same issues you described, no live output but it will record and playback is fine in the record.

Have you had any progress?

No, I guess, there's nothing we can do at this point.
Should be either a specific Motorola Issue when using Lineage/RR (don't know if the fm radio works on other Phones with Lineage) or simply a ROM issue, that needs to be solved by the devs.

But like I said it's definately not a Hardware issue, since the Stock FM Radio App works on the Phone in a Stock Rom or Evolution X Rom.

Hopefully theres a fix soon, since FM Radio is something I'd like to use on this phone.
 

ksio89

Senior Member
May 1, 2013
215
59
Does this ROM support Hi-Res (24-bit/192 kHz) audio output on 3.5mm jack? Snapdragon 630 does support it, but on stock ROM (Android Pie), it's only available on Bluetooth and USB DAC outputs according to Poweramp. This what the app developer told me:

Hi-Res support on 3.5 output requires config + SOC related patches (e.g. for Qualcomm - CAF patches). Both configs and patches are usually open source and available for custom ROM authors, but not all of such authors merge those patches and configs unfortunately, causing some custom ROM missing hi-res even if stock ROM has it.

Hi-Res support on USB + Bluetooth is in AOSP Android and no patches or specific configs are needed, but some OEMs are known to specifically disable hi-res support (e.g. Meizu) on their low/mid tier devices.

Could someone who has Poweramp or Neutron Music Player please test if 3.5mm can output Hi-Res audio? Thanks in advance.
 
Last edited:

R4Ck

Senior Member
Aug 14, 2011
142
22
The twrp-3.3.0-v2-evert-jlb.img link is broken, could someone reupload it please?
Thx
 

Top Liked Posts

  • There are no posts matching your filters.
  • 13
    rrlogo.png

    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]



    rrabout.png


    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.




    rrinstall.png



    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.



    rrdownload.png


    ROM Download
    GApps



    rrsource.png


    Resurrection Remix Source
    Device Source
    Kernel Source
    Vendor Source



    rrthanks.png


    XDA Developers
    LineageOs Team
    Omni Team
    And Of Course To All The Supporters, Donators And Users



    rrbugs.png


    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
    6
    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...
    4
    Hi, thanks for the ROM. But i also had issues with BT calls and sound quality during phone calls, so i reverted to stock. I tried flashing the newest Pie stock firmware(reteu PPW29.116-20) and relocking the bootloader afterwards. But i had the message "This device has loaded a different operating system", and "Verity mode disabled" during boot. And the worst thing is the message "System integrity compromized" and hens - GooglePay disabled and no software updates.
    I've got a question, how to revert to stock in corect way and eable GooglePay. Wanna to sell the device.
    Is it because of when i came from stock for the first time, I flashed "copy-partitions-AB.zip" from second post?
    Hmm, Bluetooth calls are working for some, so I've been told. Anyway, if you're trying to return to stock, you need to flash the correct firmware for your device variant. The PPW29.116-20 is only for certain variants, not the "latest" update as a lot of users mistake it for. If you wanna stay on Pie, then try the 116-11 or 116-16 firmware.
    Hello, can we dirty install the update?
    Yes, absolutely. The Updater has been fixed in latest build and does support seamless updates (same as stock). I tested it last night as I was running a test build from a couple days ago.

    To successfully dirty flash, follow these steps:
    -> Boot TWRP
    -> Flash RR.zip
    -> Reboot once
    -> Boot TWRP again
    -> Flash GApps + Magisk
    -> Wipe caches and reboot
    2
    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.

    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.
    2
    Woks awesome, thank you dev