[Galaxy Tab Q&A, Help & Troubleshooting] biketronic:
RMM state prenormal

OK now that I've jumped through hoops, installed TWRP

I go to reboot and it's locked recovery again - repeat above OEM unlock reappearing act steps fixes RMM=prenormal. Now it's official again.

Apparently you need to install an RMM patch as well which is not mentioned in this thread.

https://xdaforums.com/showpost.php?p=75360965&postcount=22

So, odin -> ap -> TWRP download

quickly press power-up-home when it resets!!!

recovery is not seandroid enforcing appears and TWRP starts.

1. back up all partitions to microsd!

2. install

a TWRP -> magisk

b TWRP -> RMM disabler - this writes to /system defeating the purpose of magisk???

wipe cache/dalvik reboot

on boot:

"Verification failed"

"Unable to restart your device the integrity verification has failed.... erase all your data"

Well recovery boots this time not an RMM error thats nice... oh it runs a few commands and automatically restarts again.

"Verification failed..."

I guess that is a boot loop then, thanks TWRP for not stopping at a menu ffs.

Reflash TWRP with odin, now it halts at TWRP menu.

https://xdaforums.com/galaxy-j7/j700t-development/how-to-recover-verification-failed-t3775722

Apparently I should put in download mode and cancel - Result = fail & TWRP bootloop -> reinstall TWRP

unmountable /data partition - yep thats me - could try format to exfat - ext4 - Result = Verification failed ffs

---------- Post added at 01:52 PM ---------- Previous post was at 01:00 PM ----------

Take 3

"Looks like you didnt flash encryption breaker." no-verity-no-encrypt_ashyx.zip or no-verity-opt-encrypt-6.0 zip well duh of course but which one for t395

https://www.androidinfotech.com/no-verity-opt-encrypt-versions/

seems a few up to 6.0

BTW if you don't press reset and instead try and reboot into recovery you don't have to reflash TWRP

Verification FAIL.

https://xdaforums.com/galaxy-note-8/how-to/guide-how-to-root-device-encryption-t3742493

Take 4 - try reinstating boot.img with no mods.

Try flashing stock AP -> twrp -> DMM fix -> magisk in quick succession & booting tablet

Verification Failed! Reset

Goes to recovery - less errors on TWRP (no mount errors like before) but verification failed again.

Because TWRP is installed I don't get the erasing screen as described by OP....? TWRP does something very quickly I think it says formatting cache, it is doing a standard factory reset. Trying manual factory reset with TWRP does not work.

So I think I need TWRP to prevent DMM tripping and install magisk but I need stock recovery to avoid the verification failing constantly.

Or a new version of TWRP that supports encryption? 3230+ I have 3230...?

Try Stock RO system - twrp - dm verity - magisk

Verification failed. Reset - no dmm error thats nice. TWRP did some extra stuff.

Verification failed again.

#&%^&^#%$#$@#%$@#%#$%

Option 556

Install dmverity patch using stock recovery.

Gives error can't find /misc partition - pretty sure these are TWRP zips only.

Magisk website says install TWRP so I can't see how to avoid TWRP and this annoying verification fail. Maybe try an older version of magisk???

Verification bootloop FIX:?

I tried booting stock, it says something like data corrupt on start, looks the same as the verification failed but with the different message. I let it erase/factory reset with stock recovery.

DMM preload did not trigger on this!

As soon as it succeeded I installed TWRP in case DMM triggers.

Now with fixed data partition (presumably) retry TWRP

1. no verity patch (6.0)

2. magisk

cannot install DMM as it alters system partition...?

No cache wipe.

Lets see what happens...... Black screen but this time

'encryption failed' reset. Press reset.... TWRP does a factory reset

'encryption failed'

LOL now I have an encryption failed bootloop.

Reinstall stock and use stock factory reset again - boot to recovery straight away, wipe data & cache

Now install TWRP (not booted once yet)

Install verity patch 6.0

install magisk 19.1

Boot system for the first time. - got a bootloop? no just taking it's sweet time. Fingers crossed!

Android is starting... WELCOME

HOLY **** IT WORKED

DMM patch not installed and it hasn't tripped DMM yet (the old 7 day wait issue)

SUMMARY:

1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps

2/ flash stock AP - do NOT boot system yet

3/ stock recovery - wipe data and cache

4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar

5/ twrp - install no-verity-opt-encrypt-6.0.zip

6/ twrp - install magisk 19.1

7/ Boot system for the first time

So I have not installed RMM patch (system untouched) but I did install the no encryption/dm verity patch.

It actually boots now.... will update if further problems

Interestingly OEM unlock has disappeared, so RMM must be prenormal so it will probably die on reboot. Argh. But everything is restoring OK for now. See what happens...

Magisk app auto installed and passes safetynet. Preserve force enctyption and AVB 2.0/dm-verity unchecked.

Annoyingly despite backing up all my messages to samsung they are not restoring past 20 april. Not the end of the world.

Skype keeps stopping.

Reboot and YES only officially released binaries are allowed to be flashed boot loop.

So lets do this again!

SUMMARY:

1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps

8skip 2/ flash stock AP - do NOT boot system yet

8skip 3/ stock recovery - wipe data and cache

4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar

5/ twrp - install no-verity-opt-encrypt-6.0.zip

6/ twrp - install magisk 19.1

7/ Boot system for the second time

Pretty sure I already tried this so it won't work. &^%#@&^$#$#%#$%@##%@

Oh great it has managed to install the update and now the date fix doesn't work. &^#%&^#$#@$%@#$

After waiting 7 days

1/ Use stock recovery factory reset, then immediately hold down-home-power download mode

2/ Odin TWRP, then immediately hold up-home-power to enter TWRP

2a/ TWRP swipe to allow modifications (for RMM patch)

3/ TWRP install RMM patch

4/ TWRP install no verity patch

5/ TWRP install latest Magisk

NB Magisk seems to install itself as an app - its just there.

...Safetynet pass despite RMM editing /system phew