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

Search This thread

Gleanfast

Member
Dec 20, 2018
22
7
Same problem for me, tried installing fresh (wiped OS, data, cache) with latest TWRP, entered boot loop, got taken back to my old ROM.

When you flash OS it's going to be installed to the inactive slot so you need to boot into other slot.

Also the lastest ROM is encrypted so TWRP will not stick unless you format data, not just wipe it. The new ROM is going to overwrite it so reboot and format data, Use JLB script before installing Magisk and if you want TWRP flash the dm-verity.
 
Last edited:

kshade2

Member
Jan 19, 2018
20
0
When you flash OS it's going to be installed to the inactive slot so you need to boot into other slot.

I did, I now have an unbootable slot with Resurrection Remix and a bootable one with Havoc OS.

Also the lastest ROM is encrypted so TWRP will not stick unless you format data, not just wipe it. The new ROM is going to overwrite it so reboot and format data, Use JLB script before installing Magisk

I might have formatted data, but I'll try again later to make sure.

In case it doesn't work, how would I get some usable debug output? It appear that the kernel doesn't get very far into booting, it basically reboots right after the bootloader screen.
 

kshade2

Member
Jan 19, 2018
20
0
Also the lastest ROM is encrypted so TWRP will not stick unless you format data, not just wipe it. The new ROM is going to overwrite it so reboot and format data

So I tried installing again, wiped everything, formatted data, flashed only the latest RR ROM for Evert, and it boot loops again.

MD5 checksum is correct. Pretty sure the image file is just broken.
 

Gleanfast

Member
Dec 20, 2018
22
7
So I tried installing again, wiped everything, formatted data, flashed only the latest RR ROM for Evert, and it boot loops again.

MD5 checksum is correct. Pretty sure the image file is just broken.


I had the same problem and ended up restoring the stock Boot image from the factory ROM extract, then flashing the new RR ROM, boot back to TWRP via fastboot, keep track of your slots, do not boot to system, format data, fastboot TWRP again, JLB TWRP Ramdisk, Magisk, and most importantly the dm-verity if you want to keep twrp.

---------- Post added at 01:55 AM ---------- Previous post was at 01:11 AM ----------

I did, I now have an unbootable slot with Resurrection Remix and a bootable one with Havoc OS.



I might have formatted data, but I'll try again later to make sure.

In case it doesn't work, how would I get some usable debug output? It appear that the kernel doesn't get very far into booting, it basically reboots right after the bootloader screen.

Format data is under Advanced wipe in TWRP, it will ask you to type "yes" then you need to fastboot TWRP again.

Are you saying it's boot looping back to the bootloader on just one slot or both? And if you can boot the other slot try restoring the boot image in magisk before flashing vthe new RR. Just don't boot system unitill you have TWRP and magisk installed.
 
Last edited:

Dave-C

Member
May 27, 2014
20
1
Really appreciate this thread, all the help and especially this great ROM.

Howeever I now lost track (even after lots of reading), on how to correctly install this rom.
Had RR installed successfully (April Version), howeever after tryin the August Update (failed), I messed my system up.
Even had all partitions successfully backed up via the installed TWRP (and restored several times with success), but after the failed update, I can no longer Restore my working Backups.

Please, could someone write down a simple step-by-step guide on how to correctly install after coming from stock again?
I'm sure, there are others that would find it useful too.
Especially when to switch the A/B Slot, when to install the "copy-partition-script" or the dm-verity.zip and when to format.

Flashed several devices with success, but with this device i'm going crazy....
 

kshade2

Member
Jan 19, 2018
20
0
I had the same problem and ended up restoring the stock Boot image from the factory ROM extract, then flashing the new RR ROM, boot back to TWRP via fastboot, keep track of your slots, do not boot to system, format data, fastboot TWRP again, JLB TWRP Ramdisk, Magisk, and most importantly the dm-verity if you want to keep twrp.

I tried that now, restored the entire stock image successfully (via fastboot), flashed RR into the same slot, wiped partitions and formatted data, still no dice. I skipped the ramdisk and Magisk, but that can't be it.

Format data is under Advanced wipe in TWRP, it will ask you to type "yes" then you need to fastboot TWRP again.

Yep, that's what I did, second try for sure, first not so sure. But the outcome was the same.

Are you saying it's boot looping back to the bootloader on just one slot or both?

Just the RR one. The other automatically boots up fine after a few failed attempts, but isn't loaded with RR.
 

MR1865

Member
Feb 8, 2016
15
2
Really appreciate this thread, all the help and especially this great ROM.

Howeever I now lost track (even after lots of reading), on how to correctly install this rom.
Had RR installed successfully (April Version), howeever after tryin the August Update (failed), I messed my system up.
Even had all partitions successfully backed up via the installed TWRP (and restored several times with success), but after the failed update, I can no longer Restore my working Backups.

Please, could someone write down a simple step-by-step guide on how to correctly install after coming from stock again?
I'm sure, there are others that would find it useful too.
Especially when to switch the A/B Slot, when to install the "copy-partition-script" or the dm-verity.zip and when to format.

Flashed several devices with success, but with this device i'm going crazy....

I also have not been to successfully flash the new ROM with any instructions provided. However I was in the same place in terms of TWRP backups. I have been able to restore them however multiple times. Each time I restored the stock ROM, flashed the version of RR that was being used at the time, for you I presume the April version. Then format data ( Wipe -> Format Data -> Type yes ), boot into the fresh RR install of what version you are using, fastboot boot back into twrp, and restore the Boot, Data, and System partitions from your backup. That has worked multiple times for me after bootlooping from the latest image. Let me know if that works for you.
 

Gleanfast

Member
Dec 20, 2018
22
7
I also have not been to successfully flash the new ROM with any instructions provided. However I was in the same place in terms of TWRP backups. I have been able to restore them however multiple times. Each time I restored the stock ROM, flashed the version of RR that was being used at the time, for you I presume the April version. Then format data ( Wipe -> Format Data -> Type yes ), boot into the fresh RR install of what version you are using, fastboot boot back into twrp, and restore the Boot, Data, and System partitions from your backup. That has worked multiple times for me after bootlooping from the latest image. Let me know if that works for you.


If you are coming from a stock ROM then here's what I came up with after much toil. This will give you the updated ROM with TWRP and magisk installed.

If you are rooted then first restore the factory boot image via magisk manager. Otherwise you should have a clean boot image.

If you are coming from the previous ROM then, restore the factory boot image first, and you can try the following but if you have already wiped system, etc then you will probably have to flash the factory ROM, or you can extract the factory boot image form the ROM and flash it, then follow below.


Backup boot partitions etc.

Make sure you have JLB TWRP on your external SD, as well as dm-verity and magisk.

Fastboot the JLB TWRP from OP.

Copy A/B Partitions might be a smart thing to do just in case.

Fastboot JLB TWRP, take note of what slot you are in.

Wipe everything then format data.

Fastboot JLB TWRP, Flash the RR ROM from August, which is encrypted.

From here make sure you do not boot system at any point. Only fast boot TWRP till you get the boot image packaged properly.

Fastboot JLB TWRP, format, not wipe data.

Fastboot JLB TWRP, install Recovery Ramdisk from your external sd

You should be able to reboot Recovery from TWRP at this point,

If you can boot TWRP without fastboot then flash dm-verity in TWRP, do not reboot, flash magisk, then to be safe flash dm-verity again, it will not hurt anything.

At this point you should be ready to go. I Was careful and booted Recovery again to make sure it stuck, then booted system.

Phone should say not encrypted, and both boxes in magisk under Advanced Settings should be unchecked.

Back it up.

I would recommend flashing gapps after you have booted system and recovery at least once.
 
  • Like
Reactions: MR1865 and ew

ew

Senior Member
Sep 28, 2010
711
168
If you are coming from a stock ROM then here's what I came up with after much toil. This will give you the updated ROM with TWRP and magisk installed.… .

Thank you for the very detailed instructions. Lots of work for an upgrade. Do you know if bluetooth calling is fixed in this build?
 

MR1865

Member
Feb 8, 2016
15
2
If you are coming from a stock ROM then here's what I came up with after much toil. This will give you the updated ROM with TWRP and magisk installed. ...

Appreciate the detailed instructions. Potentially dumb follow-up question, but where did you get the dm-verity? Haven't generally had to deal with it in custom roms before. I think that is the piece I am missing at this point.
 

Gleanfast

Member
Dec 20, 2018
22
7
Appreciate the detailed instructions. Potentially dumb follow-up question, but where did you get the dm-verity? Haven't generally had to deal with it in custom roms before. I think that is the piece I am missing at this point.

https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389

---------- Post added at 12:56 PM ---------- Previous post was at 12:49 PM ----------

Thank you for the very detailed instructions. Lots of work for an upgrade. Do you know if bluetooth calling is fixed in this build?

Not sure about the Bluetooth. And yah, not your usual OTA.

it took me many attempts to get it right so my instructions are just the best of what I can recall, no promises.
 
  • Like
Reactions: ew

Gleanfast

Member
Dec 20, 2018
22
7
Any idea if this is repeatable? I followed your steps exactly twice and got a boot loop both times. I am wondering if it working was somewhat serendipity.



Will it boot the RR rom if you just wipe, format amd fastboot TWRP / flash rom?

I will go over my instructions to see if i left something out.

If you had magisk installed before did you restore the factory image?
 

MR1865

Member
Feb 8, 2016
15
2
Will it boot the RR rom if you just wipe, format amd fastboot TWRP / flash rom?

Do you mean when trying to restore from a broken update? Or apply the update? When trying to restore from a broken update, the only thing I have gotten to work is to revert to stock. When applying the update if I just wipe, format, and flash, I get the same bootloop as always.

If you had magisk installed before did you restore the factory image?

The only time I have installed magisk was the last two times I attempted to flash with your instructions. I have reverted to stock every time before flashing except for the very first time.
 

Gleanfast

Member
Dec 20, 2018
22
7
Do you mean when trying to restore from a broken update? Or apply the update? When trying to restore from a broken update, the only thing I have gotten to work is to revert to stock. When applying the update if I just wipe, format, and flash, I get the same bootloop as always.



The only time I have installed magisk was the last two times I attempted to flash with your instructions. I have reverted to stock every time before flashing except for the very first time.[/QUOTE

I repeated the process until I got it right, sorry if my instructions wasted your time, but I was able to repeat it in a simple fashion today.

For the record

fastboot jlb
flash RR
flash dm
reboot stock recovery
wipe/format data
reboot

This time should be force decrypt disabled, but you keep AVB 2 selinux

Once force decrypt is disabled you can install jlb TWRP ramdisk, reboot to twrp and magisk etc.

The update was about encryption and security so doing this is somewhat redundant, but you do get selinux etc.

---------- Post added at 06:18 PM ---------- Previous post was at 06:13 PM ----------

Disregard the following suggestions: does not work reliably.

If you are coming from a stock ROM then here's what I came up with after much toil. This will give you the updated ROM with TWRP and magisk installed.

If you are rooted then first restore the factory boot image via magisk manager. Otherwise you should have a clean boot image.

If you are coming from the previous ROM then, restore the factory boot image first, and you can try the following but if you have already wiped system, etc then you will probably have to flash the factory ROM, or you can extract the factory boot image form the ROM and flash it, then follow below.


Backup boot partitions etc.

Make sure you have JLB TWRP on your external SD, as well as dm-verity and magisk.

Fastboot the JLB TWRP from OP.

Copy A/B Partitions might be a smart thing to do just in case.

Fastboot JLB TWRP, take note of what slot you are in.

Wipe everything then format data.

Fastboot JLB TWRP, Flash the RR ROM from August, which is encrypted.

From here make sure you do not boot system at any point. Only fast boot TWRP till you get the boot image packaged properly.

Fastboot JLB TWRP, format, not wipe data.

Fastboot JLB TWRP, install Recovery Ramdisk from your external sd

You should be able to reboot Recovery from TWRP at this point,

If you can boot TWRP without fastboot then flash dm-verity in TWRP, do not reboot, flash magisk, then to be safe flash dm-verity again, it will not hurt anything.

At this point you should be ready to go. I Was careful and booted Recovery again to make sure it stuck, then booted system.

Phone should say not encrypted, and both boxes in magisk under Advanced Settings should be unchecked.

Back it up.

I would recommend flashing gapps after you have booted system and recovery at least once.
 

kvviingu

New member
Dec 25, 2018
1
0
Public keys?

Hi, I installed RR today on my G6+ but I get trust error saying, that this build is signed with public keys.
Why is that, and what should I do to prevent compromising my security?

Thanks in advance.
Running on RR v7.0.2
 

Dave-C

Member
May 27, 2014
20
1
[/QUOTE

I repeated the process until I got it right, sorry if my instructions wasted your time, but I was able to repeat it in a simple fashion today.

For the record

fastboot jlb
flash RR
flash dm
reboot stock recovery
wipe/format data
reboot

This time should be force decrypt disabled, but you keep AVB 2 selinux

Once force decrypt is disabled you can install jlb TWRP ramdisk, reboot to twrp and magisk etc.

The update was about encryption and security so doing this is somewhat redundant, but you do get selinux etc.

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
 

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
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone