Database Develop

no_verity_op5(t) _v3.zip for OOS OB13 with Project Treble

I made small changes based v2
Suitable with OOS OB13 with Project Treble.
No need to mount any specific partitions (in recovery) manuly such as /vendor
Click to expand...
Click to collapse
How to use
If you see this thread, you should know how to use this file.
Just all the same as v2. More info here https://forum.xda-developers.com/oneplus-5/how-to/guide-how-to-decrypt-data-partition-t3642144
Can be used for HOS/OOS 7.1 8.0 8.1 and 8.1 with Project Treble and mokee rom
Download Link https://drive.google.com/open?id=1dMeYaIC4eFNBc3sfNQpGUqFzcqttlMZ0

daxiaamu said:
How to use
If you see this thread, you should know how to use this file.
Just all the same as v2. More info here https://forum.xda-developers.com/oneplus-5/how-to/guide-how-to-decrypt-data-partition-t3642144
Can be used for HOS/OOS 7.1 8.0 8.1 and 8.1 with Project Treble and mokee rom
Click to expand...
Click to collapse
File is damanged. also, has a zip.zip extension, but still, after renaming it, doesn't open (at least on the PC)

Awesome. Thank you very much @daxiaamu!
fjsferreira said:
File is damanged. also, has a zip.zip extension, but still, after renaming it, doesn't open (at least on the PC)
Click to expand...
Click to collapse
Same thing here. Thanks for the heads up.

fjsferreira said:
File is damanged. also, has a zip.zip extension, but still, after renaming it, doesn't open (at least on the PC)
Click to expand...
Click to collapse
link https://drive.google.com/open?id=1dMeYaIC4eFNBc3sfNQpGUqFzcqttlMZ0

a63548 said:
Awesome. Thank you very much @daxiaamu!
Same thing here. Thanks for the heads up.
Click to expand...
Click to collapse
link https://drive.google.com/open?id=1dMeYaIC4eFNBc3sfNQpGUqFzcqttlMZ0

Need new link please

Aballamis said:
Need new link please
Click to expand...
Click to collapse
You can also use the one from xXx https://forum.xda-developers.com/on...1-1-speed-ram-optimized-t3627121/post72802213

Aballamis said:
Need new link please
Click to expand...
Click to collapse
Here's a mirror: http://www.mediafire.com/file/1psz6...ForceEncrypt_2.0_%28OP5-5T-Treble%29.zip/file

Recommendation
I recommend this-
Its unversaly. I use this on every rom.
Regularly updated.
http://zackptg5.com/android.php#disverfe
XDA Thread for this-
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
P.S. I never format data while updating before flashing this (never needed, it works fine without that). I onlyformat data whenever i want pure clean install of any rom.
Just make sure to flash this after rom and after custom kernel or anything that edits boot. But flash this before Magisk. So. In short-
1. Flash- rom
2. Flash custom kernel or any thing that edits boot
3. Flash this to decrypt and to boot ur device successfully
4. Then flash Magisk
Note1: When you need clean install then follow these steps-
1. Factory reset (as normal when u do but if u r flash pure stock than wipe everything- i recommend this everytime for every stock(based) rom)
2. Reboot to recovery again
3. Click on Format data, type yes and format it.
4. Reboot to recovery again
5. And now go on flashing as mentioned above before these steps.
Note2: When u just need to update and not clean install. Then follow these steps-
1. First make sure to remove all magisk modules (when enabled it makes issues - after Magisk 18 and Pie update - before these updates i never got issues)
2. Now in twrp flash update zip
3. Flash anything that edits boot (ex. - custom kernel) if you want.
4. Now flash Magisk
5. Don'y flash any tweaks etc yet. (xXx NoLimits also)
6. Reboot.
7. Now if you want flash tweaks, modules etc.
8. And now only you are ready to flash xXx NoLimits again if you want.
**
*I guess this may help many of you in many cases.*
**

Mohitash said:
I recommend this-
Its unversaly. I use this on every rom.
Regularly updated.
http://zackptg5.com/android.php#disverfe
XDA Thread for this-
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
P.S. I never format data while updating before flashing this (never needed, it works fine without that). I onlyformat data whenever i want pure clean install of any rom.
Just make sure to flash this after rom and after custom kernel or anything that edits boot. But flash this before Magisk. So. In short-
1. Flash- rom
2. Flash custom kernel or any thing that edits boot
3. Flash this to decrypt and to boot ur device successfully
4. Then flash Magisk
Note1: When you need clean install then follow these steps-
1. Factory reset (as normal when u do but if u r flash pure stock than wipe everything- i recommend this everytime for every stock(based) rom)
2. Reboot to recovery again
3. Click on Format data, type yes and format it.
4. Reboot to recovery again
5. And now go on flashing as mentioned above before these steps.
Note2: When u just need to update and not clean install. Then follow these steps-
1. First make sure to remove all magisk modules (when enabled it makes issues - after Magisk 18 and Pie update - before these updates i never got issues)
2. Now in twrp flash update zip
3. Flash anything that edits boot (ex. - custom kernel) if you want.
4. Now flash Magisk
5. Don'y flash any tweaks etc yet. (xXx NoLimits also)
6. Reboot.
7. Now if you want flash tweaks, modules etc.
8. And now only you are ready to flash xXx NoLimits again if you want.
**
*I guess this may help many of you in many cases.*
**
Click to expand...
Click to collapse
Can the DM Verity n force encrypt disbler installed after magisk and without formatting data
And which one is best for Android pie

amitporedi007 said:
Can the DM Verity n force encrypt disbler installed after magisk and without formatting data
And which one is best for Android pie
Click to expand...
Click to collapse
Magisk must be flashed after dm...zip. But if you have already installed magisk then no worries. Flash DM Verity n force encrypr disabler and then again flash magisk. No need to format data in this case. Format data only needed when you are doing pure clean install of stock (based) rom. Check my signature, i am on OOS 9.0.2 that is android pie 9.0 and magisk v18. Decrypted (using that dm verity and force encrypr disabler).

Why magisk doesn't work with PIE Roms ?

Hi
Since PIE roms for santoni are available, some people, including me, can't root their santoni.
I don't know why.
Flash looks ok in recovery, but after reboot, Magisk Manager says that Magisk isn't installed.
I tried every solution found in forums here, but everytime, same result : "magisk isn't installed"...
So sad !
Could you guys (and girls) centralize here your solutions, step by step, from flash the rom to root it...
It would be so nice for helping desperate people...

I also tried SuperSU and am having the same problem. I've tried Magisk 17.1, 17.2 and the Canary build along with the newest SuperSU and the result is always the same. Flashes fine but Magisk Manager and SuperSU apps can't find root.
The weird thing is that Enpass always tells me that my device is rooted and that it's a security risk even though Magisk Manager can't find root.
Also, I'm positive Magisk is patching the ramdisk. The Uninstaller always finds a Magisk-patched image. I'm assuming something has to be happening during boot that's cancelling root.

Two things I don't understand :
- why some people, with same configuration, don't have root problem ?
- why, with same recovery, same flash method, root works with nougat/oreo rom, and doesn't work with pie...?
Just like that : do you think problem could come from the sd card ?
I'm using à 128 gb samsung sd-card. Maybe I should format it before trying again root ?
I'm not sure it's the problem, since I can flash all roms, but I could try...
Or flash Magisk from internal storage ?
Really desperate...

Hi,
I´m in the same situation like you.
Yesterday I made a new experience of that without solution:
- Backuped all
- Uninstalled magisk at twrp
- Installed santoni_twrp_silent 27_treble (recommended from dev to install havoc)
- Rebooted
- Formated data with factory reset
- Wiped vendor, cache, data... (everything)
- Installed havoc (version 2018-09-08)
- Rebooted
- Installed magisk at twrp
- Rebooted
Same issue like before...
If I try to install magisk on magisk manager I get the following log:
Copying image to cache
Device platform: arm64-v8a
Existing zip found
Extracting files
boot_patch.sh[73]: can't create /proc/self/fd/: Is a directory
MagiskBoot v17.1(17100) (by topjohnwu)
Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
boot_patch.sh[91]: can't create /proc/self/fd/: Is a directory
boot_patch.sh[91]: can't create /proc/self/fd/: Is a directory!
Installation failed
It seems magisk can´t install correct in cause of failing permissions to create new directories. But why?
Edit:
I think there´s an old magisk information written in device system who has to removed manually, cause magisk uninstaller is not able to do

Edit:
I think there´s an old magisk information written in device system who has to removed manually, cause magisk uninstaller is not able to do
Click to expand...
Click to collapse
Ok, but I wiped AND format data of internal storage, same results.
Do you think I should format/wipe micro-sd too ?

newbie_or_not_newbie said:
Ok, but I wiped AND format data of internal storage, same results.
Do you think I should format/wipe micro-sd too ?
Click to expand...
Click to collapse
I don´t think so. Well, if you like you can try, but I think it´s an internal problem, not an external

So,
I tried another wipe of internal storage, made a format data with recovery. Then I flashed another pie rom, then magisk. And after reboot : tada !! still not working...

try with version 16.6 of magisk

Great news, actually my magisk works on Pixys 2.1!
I installed this twrp:
https://drive.google.com/file/d/1RR-8WMNSQgx6QzQv5U4i-sST1Af42nrI/view
What I did:
Uninstalled old magisk, rebooted to twrp, installed magisk 17.2, rebooted, installed magisk manager 6.0 and it works.
The only thing is I didn´t rebooted until now, maybe it still works after next reboot or not...

Lemmy554 said:
Great news, actually my magisk works on Pixys 2.1!
I installed this twrp:
https://drive.google.com/file/d/1RR-8WMNSQgx6QzQv5U4i-sST1Af42nrI/view
What I did:
Uninstalled old magisk, rebooted to twrp, installed magisk 17.2, rebooted, installed magisk manager 6.0 and it works.
The only thing is I didn´t rebooted until now, maybe it still works after next reboot or not...
Click to expand...
Click to collapse
I just tried this and it didn't work for me either. I tried multiple clean flashes, flashed MIUI then back to Pie and flashing things in different orders last night and nothing worked. I'm tired of messing with it. I don't know how to get logs without root. I've come to the conclusion that for now I either have Pie or root. Not both. lol

Me too. I stop trying every day a solution.
For the moment, no root for pie roms, so I keep staying with oreo roms (nice dot OS...) I can root.
Hope next builds of pie roms will accept to be rooted on our santoni...

You can try this:
1 Flash Magisk v 17.2, Reinica in fast boot mode, turn it off and turn the phone on again
2 Install Magiskmanager V6 APK, do not open and restart in recovery
3 Flash Magisk v 16.6 and ready...
It worked for me... important, do not update magisk... The root is lost again
Best regards

Thanks for your reply.
Did you have root trouble before trying your solution ?

yes, when installing Pie only. In oreo no, I tried it in havoc and pixys

Try OrangeFox recovery for flashing magisk.

hyperkin said:
Try OrangeFox recovery for flashing magisk.
Click to expand...
Click to collapse
That's what I've been using. Also tried TWRP. Neither worked for me. The flash always looks good with no errors but when I boot the ROM Magisk says it's not installed.

I just realize to make magisk work on pie roms i realize that i need dev miui firmware not stable miui firmware the file you need is named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1.zip i not sure why stable firmware wont work on magisk.
i used OrangeFox Recovery Project R8.1 for recovery
1. install rom PixysOS 2.1 as normal (clean flash). Note: LineageOS 16.0 also works I have tested it
2. boot up os to make sure it that everything is working
3. then reboot back to recovery
4. flash firmware zip file named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1
5. reboot to system making sure that it still boots in os
6. reboot back to recovery
7. flash magisk 17.2 beta i think magisk 17.1 also works
8. reboot up back to system
9. installl magisk manager apk
10. done
i just uplolad screenshot just to prove it

neijzen said:
I just realize to make magisk work on pie roms i realize that i need dev miui firmware not stable miui firmware the file you need is named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1.zip i not sure why stable firmware wont work on magisk.
i used OrangeFox Recovery Project R8.1 for recovery
1. install rom PixysOS 2.1 as normal (clean flash). Note: LineageOS 16.0 also works I have tested it
2. boot up os to make sure it that everything is working
3. then reboot back to recovery
4. flash firmware zip file named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1
5. reboot to system making sure that it still boots in os
6. reboot back to recovery
7. flash magisk 17.2 beta i think magisk 17.1 also works
8. reboot up back to system
9. installl magisk manager apk
10. done
i just uplolad screenshot just to prove it
Click to expand...
Click to collapse
Sounds like a plan! I'll try it out when I get home from work and let you know how it goes!

Trying asap.
Thanks

neijzen said:
I just realize to make magisk work on pie roms i realize that i need dev miui firmware not stable miui firmware the file you need is named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1.zip i not sure why stable firmware wont work on magisk.
i used OrangeFox Recovery Project R8.1 for recovery
1. install rom PixysOS 2.1 as normal (clean flash). Note: LineageOS 16.0 also works I have tested it
2. boot up os to make sure it that everything is working
3. then reboot back to recovery
4. flash firmware zip file named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1
5. reboot to system making sure that it still boots in os
6. reboot back to recovery
7. flash magisk 17.2 beta i think magisk 17.1 also works
8. reboot up back to system
9. installl magisk manager apk
10. done
i just uplolad screenshot just to prove it
Click to expand...
Click to collapse
This post right here works, thank you so much

Bootloop

Hi, my device reboot after I unlock it, I only have access to my Internal memory of my phone via PC
how to unistall/disable magisk so I can delete the modules?
Is there a folder that I can delete?
I don't have TWRP

albysprx said:
Hi, my device reboot after I unlock it, I only have access to my Internal memory of my phone via PC
how to unistall/disable magisk so I can delete the modules?
Is there a folder that I can delete?
I don't have TWRP
Click to expand...
Click to collapse
How you got magisk to work without flashing it?
PoochyXXX

PoochyX said:
How you got magisk to work without flashing it?
PoochyXXX
Click to expand...
Click to collapse
with patched the boot img of my firmware with magisk manager and then I flashed it with fastboot

albysprx said:
with patched the boot img of my firmware with magisk manager and then I flashed it with fastboot
Click to expand...
Click to collapse
Ohhhhh.... Root is very particular without a custom recovery to get your phone to that exact working state it was in before if you had a custom recovery there could of been a couple modules you could use
PoochyXXX

You can always flash a stock boot image. That will disable Magisk completely, but has the drawback of leaving you without root...
To disable or uninstall modules without removing Magisk you would have to have access to /cache (place a file named .disable_magisk, with the leading dot, in /cache and Core Only Mode will be enabled) or /data/adb (delete the Magisk image file) through recovery. Usually not an option on a stock recovery... If there is no custom recovery for your device you might not have many options, but if there is one available and you don't want to install it, you could at least boot it with "fastboot boot recovery <name_of_recovery_file>".

Didgeridoohan said:
You can always flash a stock boot image. That will disable Magisk completely, but has the drawback of leaving you without root...
To disable or uninstall modules without removing Magisk you would have to have access to /cache (place a file named .disable_magisk, with the leading dot, in /cache and Core Only Mode will be enabled) or /data/adb (delete the Magisk image file) through recovery. Usually not an option on a stock recovery... If there is no custom recovery for your device you might not have many options, but if there is one available and you don't want to install it, you could at least boot it with "fastboot boot recovery <name_of_recovery_file>".
Click to expand...
Click to collapse
Yeah, I got working again with flashing the stock boot.img but after flashed again the pacthed boot.img my phone bootloop again...
I tried to install TWRP and got it working, I typed /cache/.disable_magisk in terminal and rebooted and the device works, went to magisk manager and no modules was there, disabled core magisk and the device bootloop again...
now I'm trying to reinstall the entire firmware and make a factory reset before reinstalling magisk...
Should this remove modules installed?

Didgeridoohan said:
You can always flash a stock boot image. That will disable Magisk completely, but has the drawback of leaving you without root...
To disable or uninstall modules without removing Magisk you would have to have access to /cache (place a file named .disable_magisk, with the leading dot, in /cache and Core Only Mode will be enabled) or /data/adb (delete the Magisk image file) through recovery. Usually not an option on a stock recovery... If there is no custom recovery for your device you might not have many options, but if there is one available and you don't want to install it, you could at least boot it with "fastboot boot recovery <name_of_recovery_file>".
Click to expand...
Click to collapse
Yeah, I got working again with flashing the stock boot.img but after flashed again the pacthed boot.img my phone bootloop again...
I tried to install TWRP and got it working, I typed /cache/.disable_magisk in terminal and rebooted and the device works, went to magisk manager and no modules was there, disabled core magisk and the device bootloop again...
now I'm trying to reinstall the entire firmware and make a factory reset before reinstalling magisk...
Should this remove modules installed?

albysprx said:
Yeah, I got working again with flashing the stock boot.img but after flashed again the pacthed boot.img my phone bootloop again...
I tried to install TWRP and got it working, I typed /cache/.disable_magisk in terminal and rebooted and the device works, went to magisk manager and no modules was there, disabled core magisk and the device bootloop again...
now I'm trying to reinstall the entire firmware and make a factory reset before reinstalling magisk...
Should this remove modules installed?
Click to expand...
Click to collapse
If you got the device booting (in Core Only Mode) and still have root you could just use a file explorer, navigate to /sbin/.magisk/img and delete the offending module directories. Or, you could delete the Magisk image file in recovery (it's in /data/adb). Either of those options would remove the modules.

Didgeridoohan said:
If you got the device booting (in Core Only Mode) and still have root you could just use a file explorer, navigate to /sbin/.magisk/img and delete the offending module directories. Or, you could delete the Magisk image file in recovery (it's in /data/adb). Either of those options would remove the modules.
Click to expand...
Click to collapse
Got my device working again in magisk core only mode but the folder /sbin/.magisk/img is empty .-.

albysprx said:
Got my device working again in magisk core only mode but the folder /sbin/.magisk/img is empty .-.
Click to expand...
Click to collapse
Now that you have your device running, do a complete uninstall from the Magisk Manager and start over. That should remove everything...

Didgeridoohan said:
Now that you have your device running, do a complete uninstall from the Magisk Manager and start over. That should remove everything...
Click to expand...
Click to collapse
ok I deleted the magisk.img from data/adb/magisk, did a complete unistall from magisk manager (after the unistall the phone reboot to the TWRP without doing anything), sideloaded the magisk unistaller and got "ERROR: 1", after that I rebooted, rebooted again in recovery mode and installed magisk, rebooted, removed the core mode and rebooted again..
It works!!
Thanks a lot

No root prompt in Lineage OS 16.0 with Magisk installed

Dear XDA,
Model: Xiaomi Redmi 4X(Santoni)
Used TWRP:
Installed latest Lineage OS 16.0 of November 20, 2019 with formatting internals and wiping system, vendor, dalvik and cache.
Installed lastest Magisk v20.1 from GitHub page
Booted ROM and installed "MagiskManager-v7.4.0.apk" from above link
As the result:
MagiskManager shows everything green
No root prompt in any application and Root Checker shows that root is not installed.
"Settings -> System -> 'Developer options' -> 'Root access'" have only two options: Disabled and "ADB only"
Already have tried:
Disabling power optimization entry for MagiskManager
Reinstall Magisk using MagiskManager
What might be the reason of no prompt issue?
Why not SuperSU: is it worth to tell why? For example, basically Netflix won't work etc.
Thank you very much for any working suggestion.

This happened to me too once. What helped was simply re-flashing the 20.1 Magisk zip. It contains the Manager apk, so no need to install it separately.

I Have Nexus 5x and Lineage OS 15.1.
For me it was Lineage OS issue. Instead 20191118 I flashed 20191105. I had some other weird bugs too.

Ænimal said:
This happened to me too once. What helped was simply re-flashing the 20.1 Magisk zip. It contains the Manager apk, so no need to install it separately.
Click to expand...
Click to collapse
What do you mean by reinstall? Something like that:
Wipe phone
Install Lineage OS image
Install Magisk zip
Boot
Reboot into recovery
Install Magisk zip
Boot
Are above the full steps you suggesting?

vv77vv said:
What do you mean by reinstall? Something like that:
Wipe phone
Install Lineage OS image
Install Magisk zip
Boot
Reboot into recovery
Install Magisk zip
Boot
Are above the full steps you suggesting?
Click to expand...
Click to collapse
I thought I expressed myself pretty clearly. Well, a clean install of your system is always a good idea (given you backed up all your personal data) .You can also just extract the boot.img from your LOS image and flash that in twrp prior to flashing magisk. But what I did when the root prompt didn't pop up was simply flashing the magisk zip again in twrp, (maybe wiping caches as well) and after rebooting magisk su was working as intended.. Good luck

how downgrade sm-a605fn from android 10 to 9

Hello, I have a Samsung Galaxy A6+ with latest fw installed.
(italian version)
A605FNXXU7CUD4
The phone is totally useless after the update to android 10, it takes AGES to perform any action, even open the Camera or open a Message.
Already tried to wipe everything, hard reset, reinstall fw. Still useless.
Since I’d like to downgrade to Android 9 to have back a useful phone, I tried to install the latest Android 9 fw with Odin.
A605FNXXS5BTB1
But it fails, saying SW REV CHECK FAIL : [aboot] Fused 7 > Binary 5
What can I do?
Is there any chance to downgrade this phone?
Thank you

1. Unlock your bootloader.
2. Flash custom recovery for your device.
3. Go to custom recovery (TWRP) and flash any downloaded custom rom (for your device), GSI or save stock firmware as flashable zip with tool like ClassyKitchen.
4. Flash Magisk or RMM-bypass-v3 in TWRP to protect your bootloader from getting locked again.
Backup your personal data at first, of course.

nqnxev said:
1. Unlock your bootloader.
2. Flash custom recovery for your device.
3. Go to custom recovery (TWRP) and flash any downloaded custom rom (for your device), GSI or save stock firmware as flashable zip with tool like ClassyKitchen.
4. Flash Magisk or RMM-bypass-v3 in TWRP to protect your bootloader from getting locked again.
Backup your personal data at first, of course.
Click to expand...
Click to collapse
Almost done, but I can't find any custom rom available for download. Can someone help? Since wwith twrp I cannot install a stock rom. Thanks in advance.

I managed to flash a so called Ari's rom, but I think the phone is now bricked. It is on bootloop on the first screen of Samsung (with phone name and so on) and with SET WARRANTY BIT : KERNEL at top left. I think it is time to trash it or does someone have any hint? Thanks

Ecto1000 said:
I managed to flash a so called Ari's rom, but I think the phone is now bricked. It is on bootloop on the first screen of Samsung (with phone name and so on) and with SET WARRANTY BIT : KERNEL at top left. I think it is time to trash it or does someone have any hint? Thanks
Click to expand...
Click to collapse
I proposed three different options: custom rom, GSI (generic system image) or conversion stock firmware to flashable form. If there's no good custom rom for A6+, then don't worry - you can still try another options. Try playing with Generic System Images:
1. Flash your current stock firmware as usual in Odin.
2. Unlock bootloader and flash TWRP.
3. Go to TWRP.
4. Wipe partitions cache, dalvik, data, system (don't wipe vendor partition - it's needed).
5. Flash GSI image (recommended will be at first phhusson's AOSP (Android 9 or 10)) as "system image". You always need to choose and download "arm32_binder64" variant of img file.
6. Reboot to your new system.
Second option is to convert stock Android 9 firmware into flashable form.
1. Download ClassyKitchen tool.
2. Import downloaded Android 9 stock firmware (for your phone) into it and save it as flashable zip.
3. Go to TWRP.
4. Wipe cache, dalvik, data, system and vendor.
5. Flash your previously done zip with Android 9 as any other flashable zip in TWRP.
6. Flash Magisk or RMM-state-bypass-v3 in TWRP to prevent your bootloader from getting locked again.
7. Reboot.

I went for the second option, in Classykitchen I loaded the stock android 9 rom and selected
BUILD ZIP ROM (for recovery).
Then installed with TWRP following your wipe indications.
Success.
But when I went to install RMM-state-bypass-v3 I got the error impossile to mount /system.
So I rebooted twrp and before anything I manually mounted SYSTEM in twrp in the dedicated MOUNT menu, and I did everything again from wipe to install.
Is this procedure correct?
Success, success also for RMM-state-bypass-v3.
I rebooted but I'm again stuck in the same loop described in my previous reply.
When I selecr REBOOT in twrp, do I have to flag anything? For example System?
Regarding the first option, if I go there:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
exactly which file do I have to download among ASSETS of any release?
Thank you very much

Ecto1000 said:
I went for the second option, in Classykitchen I loaded the stock android 9 rom and selected
BUILD ZIP ROM (for recovery).
Then installed with TWRP following your wipe indications.
Success.
But when I went to install RMM-state-bypass-v3 I got the error impossile to mount /system.
So I rebooted twrp and before anything I manually mounted SYSTEM in twrp in the dedicated MOUNT menu, and I did everything again from wipe to install.
Is this procedure correct?
Click to expand...
Click to collapse
Yes, it's correct. If RMM bypass or Magisk.zip was flashed without any errors in TWRP then everything is okay. Just reboot to system in TWRP after that - there is option to reboot directly to system. First boot always can take a bit longer than next boots.
Ecto1000 said:
exactly which file do I have to download among ASSETS of any release
Click to expand...
Click to collapse
You always need to get any "arm32_binder64" (always AB) image. Gapps or vanilla is just your choice. Just get Android 9 or 10 image and flash it as "system image" (but wipe at first partitions specified in my previous post - don't wipe only Vendor partition, because it contains important things). Android 12 GSI still aren't stable. Android 11 - maybe will work properly. Android 9 and 10 should work fine. There is even short article about GSI on Galaxy A6+ with some fixes for that device attached:
Samsung Galaxy A6 Plus (2018)
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
You can try of course other GSI's as well:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com

Thank you very much, appreciated.
But something weird happens: I install the ROM with success. If then I try to install Magisk (or Rmm) it fails with error 7.
And twrp says No Os installed if I reboot.
But if I try to install Magisk after rebooting into twrp after installing the ROM it goes without errors.
But anyway I have the issues of No Os installed.

Ecto1000 said:
Thank you very much, appreciated.
But something weird happens: I install the ROM with success. If then I try to install Magisk (or Rmm) it fails with error 7.
And twrp says No Os installed if I reboot.
But if I try to install Magisk after rebooting into twrp after installing the ROM it goes without errors.
But anyway I have the issues of No Os installed.
Click to expand...
Click to collapse
You need to reboot to recovery after flashing new system, because just after flashing TWRP doesn't recognize it - that is why you see that "no OS installed". Just reboot your phone to recovery again (you have such option in TWRP). In case of GSI (except maybe CAOS, LineageOS Q/R mod) Magisk or RMM bypass is not needed.
Btw, in case of any problems with hardware support on GSI flash also that patch in TWRP (it may be needed to mount "Vendor" partition in TWRP before flashing that fixes):
Fixes.zip
drive.google.com

Thank you again for your help.
I already rebooted to recovery and twrp keeps saying NO OS.
I'm using twrp 3.5.2_10-0.
I'm starting to suspect that this behaviour is due to the fact that this version of twrp could be too much new and unstable for my phone.
So I'd like to install an older version of twrp with Odin, as explained here:
TWRP for SM-A605FN Samsung Galaxy A6+
How to Install TWRP 3.2.3-1 on Galaxy A6+ SM-A605FN Android 8.0.0 Oreo. Once you installed TWRP recovery on your Samsung Galaxy A6+ SM-A605FN, you can customize it, Rooting or installing custom ROM
www.recovery-mode.com
But I cannot manage to go into download mode again, even from REBOOT menu of twrp it doesn't work, I keep staying in the loop explained before.
Moreover your first option of GSI need me to go into download mode to install the latest stock ROM with Odin.
I just manage to get into the attached screen.
Any idea?
Thank you again

It's not possible to ignore that message and just flash latest stock firmware via Odin? Odin refuses flashing latest stock firmware?
Other builds of TWRP for your devices you'll find here:
Releases · roynatech2544/TWRP_device_samsung_a6plte
Contribute to roynatech2544/TWRP_device_samsung_a6plte development by creating an account on GitHub.
github.com
But don't use TWRP older than 3.4.0, because it doesn't have support for "Vendor" partition.

Yes, I managed to ignore that screen and go in download mode again.
I tried to follow your first option since the second one was not successful.
Installed latest stock and then twrp 3.5.0-1.
Wipe as you explained, I flash the Gsi
system-quack-arm32_binder64-ab-gapps.img
The flash is very fast, but no errors, is it normal?
After that I reboot to recovery in order to flash
Disable_DM-Verity_ForceEncrypt_11.02.2020
it goes but just at the end it gives the error
failed to mount /odm no such file or directory.
And if I reboot to system the phone loops as always.
I'm losing all hope...

Ecto1000 said:
system-quack-arm32_binder64-ab-gapps.img
Click to expand...
Click to collapse
It's okay, but it's possible that you'll always need "vndklite" images for working camera.
Ecto1000 said:
The flash is very fast, but no errors, is it normal?
Click to expand...
Click to collapse
If you flashed it as "System Image" and it was successful then yes - should be fine. DM-Verity isn't needed for GSI - only RMM bypass v3 is sometimes needed (on CAOS, Lineage Q/R mod and maybe in case of some other images). On usual A600FN RMM bypass is not needed on phhusson AOSP. Just format "Data" partition (format, not only wipe) - it will remove encryption for you.
Procedure of flashing should be like that:
1. Wipe: cache, dalvik, data, system ("Vendor" partition leave untouched, because it's important for GSI - that is why you needed to flash stock firmware at first, because it adds vendor files for your phone, but it's needed only once, just don't wipe "Vendor").
2. Flash your GSI as "System Image".
3. Reboot phone (to recovery again).
4. Mount your "data", "vendor" and "system" partition.
5. Flash your zips: RMM bypass v3 (optionally Magisk).
5. Reboot to your new system now.
In case of any hardware support problems, reboot to TWRP again, mount "Vendor" partition and flash that fixes:
Fixes.zip
drive.google.com
Try to boot Android 10 or Android 9 images. If it will succeed, then you can try flashing Android 11 images and check what works, and what not. According to that article

nqnxev said:
It's okay, but it's possible that you'll always need "vndklite" images for working camera.
Click to expand...
Click to collapse
I don't know what are those images. Can you explain better?
When I proceed with RMM bypass V3 I see the errors in the attached image. It seems like there is a problem in writing to /system.
Can this be related to the hardware support problems you mentioned?
I tried with different versions of Twrp already and with Havoc Os too.
Should I try with flashing a different ROM ?
Thanks again

Ecto1000 said:
I don't know what are those images. Can you explain better?
Click to expand...
Click to collapse
Just look at filename of system images. But as I see, it's apparently important on Android 11 and newer. For now, try to boot Android 10 or 9. Let's try with that image:
https://github.com/phhusson/treble_experimentations/releases/download/v222/system-quack-arm32_binder64-ab-vanilla.img.xz
1. Decompress that image.
2. Copy to SD card or to internal storage.
3. Wipe cache, dalvik, data, system.
4. Format data partition (it's needed only once).
5. Flash downloaded and extracted file as "System Image".
6. Reboot phone to recovery (again).
7. Select in TWRP: Mount -> system, data, vendor.
8. Flash RMM bypass v3 (or Magisk).
9. Reboot now to system.
10. In case of some things not working, go back to TWRP and mount vendor partition (Mount -> tick "Vendor" -> go back to flashing zips) and flash that:
Fixes.zip
drive.google.com
11. Reboot to system again and check if now everything works properly.
Ecto1000 said:
When I proceed with RMM bypass V3 I see the errors in the attached image. It seems like there is a problem in writing to /system.
Click to expand...
Click to collapse
Yes, because you need to mount that partitions in TWRP:
Mount -> tick "system", "vendor" and "data" - and now flash whatever you want.

The only "receipt" which isn't giving installation errors is following your last instructions but avoiding to reboot to recovery after ROM flash (used Vanilla), and using Magisk v22 with unticked the line called "skip digest check" . See attached images.
Anyway, still no success to get into android.
Also tried fixes.zip.

Maybe I have to try with sideload ?

Ecto1000 said:
The only "receipt" which isn't giving installation errors is following your last instructions but avoiding to reboot to recovery after ROM flash (used Vanilla), and using Magisk v22 with unticked the line called "skip digest check" . See attached images.
Anyway, still no success to get into android.
Also tried fixes.zip.
Click to expand...
Click to collapse
Everything seems to be okay in your photos. What happens when you press "Reboot System"?

nqnxev said:
Everything seems to be okay in your photos. What happens when you press "Reboot System"?
Click to expand...
Click to collapse
The phone goes into loop with the attached screen and black screen alternatively.
On the top you can see SET WARRANTY BIT: KERNEL, it should be normal right?
Do I have to set something inside MOUNT of twrp before rebooting to system?

Ecto1000 said:
The phone goes into loop with the attached screen and black screen alternatively.
On the top you can see SET WARRANTY BIT: KERNEL, it should be normal right?
Do I have to set something inside MOUNT of twrp before rebooting to system?
Click to expand...
Click to collapse
I've never had such problem, but according to that thread it seems that it's a fault of modified kernel (so don't flash Magisk with GSI, because it patches kernel).
Try to flash stock firmware, unlock bootloader, flash TWRP, format "data" partition, wipe partitions (cache, dalvik, system, data) and flash GSI image as "system image". And reboot to system.
Don't flash RMM and Magisk for now - and check if system will run properly.