Hi,
I've rooted my Galaxy S7 Edge G935V. I also have SU working. I'm trying to install Xposed based on instructions provided by the rooting thread for Galaxy S7 Edge https://forum.xda-developers.com/verizon-galaxy-s7/how-to/how-to-notes-root-install-xposed-unroot-t3411039
The instructions in the thread provide a link to download an Xposed zip file and to use Flashfire to flash the zip file
However, I'm not able to get Flashfire to work. When I use Flashfire while loading it closes after checking if I have SU Pro. I did purchase SU Pro but still can't get Flashfire to work. Also unable to get TRWP to install as well.
Any suggestion getting Flashfire to work or is there another way to flash the xposed zip file?
Thanks
rosedev said:
Hi,
I've rooted my Galaxy S7 Edge G935V. I also have SU working. I'm trying to install Xposed based on instructions provided by the rooting thread for Galaxy S7 Edge https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
The instructions in the thread provide a link to download an Xposed zip file and to use Flashfire to flash the zip file
However, I'm not able to get Flashfire to work. When I use Flashfire while loading it closes after checking if I have SU Pro. I did purchase SU Pro but still can't get Flashfire to work. Also unable to get TRWP to install as well.
Any suggestion getting Flashfire to work or is there another way to flash the xposed zip file?
Thanks
Click to expand...
Click to collapse
Uninstall flashfire, change date to a date before April 1 and reinstall flashfire should work
Did that trick work? It doesn't sound to me like you are rooted in the first place but I'm no expert. You were able to root the s7 edge Verizon?
Related
Thank you to XBrav for posting this solution!
Since I cannot post or reply in Dev forums, I found this root method that has been confirmed multiple times to work with the NF2 build. It also worked for me; however, I had to flash SuperSU using TWRP rather than installing from Google Play as it would not work properly.
Confirmed working on my Rogers Samsung Galaxy S3, Stock 4.4.2, NF2 build.
Here is the link to the post:
http://forum.xda-developers.com/showpost.php?p=54354429&postcount=142
XBrav said:
1) Install TWRP through ODIN: http://teamw.in/project/twrp2/104
2) Install Team Epic root through TWRP http://www.epiccm.org/2012/06/team-e...-recovery.html
3) Reboot, and install SuperSu through the Market: https://play.google.com/store/apps/d....supersu&hl=en
4) Boot SuperSu, and upgrade the binary (normal seems to work fine). Allow it to remove SuperUser. I also allowed it to remove KNOX.
5) Reboot, and you have the latest SU binary working.
Click to expand...
Click to collapse
Notes:
a) if SuperSU just doesn't seem to be working properly, uninstall the Google Play version of SuperSU, download the ZIP and flash using TWRP: http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip
b) if SuperSU seems to be taking too long to disable KNOX, reboot the phone and try again
Happy Rooting!
Trying to purchase Galaxy S4 Mini (GT-I9195) I received S4 Mini Plus (GT-I9195I) from online retailer. After some consideration I decided to treat this as a challenge and not to return the purchase. Here is what I learned so far about hacking this tiny piece of electronics:
Getting Root
I was not able to get root on the firmware installed on the phone (I9195IXXU1AOB1). The way I fixed that was to download another firmware from SamMobile and flashed it with Kies. The highest version I was able to flash without issues was I9195IXXU1AOD2, and it immediately updated to I9195IXXU1AOG1. For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu. This did not trip Knox device status, BTW.
Flashing Custom Recovery
I downloaded official TWRP recovery from teamw.in and decided to go the hard way and install the recovery doing dd fom command line (ConnectBot) - I was hoping this will help me to keep the warranty. Worked just fine, but tripped Knox bit nevertheless. NB: avoid extra hassles and just use Odin to install recovery.
Installing Xposed
Xposed install sent my device into boot loop. Fixing permissions from recovery allowed me to boot, but gapps was having permanent ANRs. Upon investigation it looks like Xposed for KK is not designed to take selinux enforcing mode into account. Specifically it installed app_process with wrong security context making device unbootable. The fix is very simple:
1. Install Xposed Installer and ES File Explorer.
2. Open Xposed Installer, go to Framework menu, select "Recovery (write zip to SD card, flash manually)" Installation mode, press "Install/Update".
3. Open ES File, navigate to /sdcard/Andriod/data/de.robv.android.xposed.installer/files. There are two files there: Xposed-Installer-Recovery.zip and Xposed-Disabler-Recovery.zip
4. Now comes the fun part: in both archives you need to modify META-INF/com/google/android/update-binary: comment or delete all "chmod", "chown" and "restorecon" commands and replace "cp XXX/app_process[.orig] XXX/app_process" with "cat XXX/app_process[.orig] > XXX/app_process". This will keep both permissions and security context of the file. Unpack, edit, repack.
5. Reboot into recovery, install Xposed-Installer-Recovery.zip, enjoy.
I will send patch to Xposed maintainer later this week. But we have not seen new releases of Xposed fo KK for over a year now, so I am not sure it will get released any time soon.
I will update the post as my adventures continue - my plan is to have CyanogenMod on this device some day. Stay tuned.
Alte.78 said:
I will update the post as my adventures continue - my plan is to have CyanogenMod on this device some day. Stay tuned.
Click to expand...
Click to collapse
If you want you can PM me or join Freenode IRC and PM droidlambda. I've already started making CyanogenMod for the device, although I haven't come that far yet (even though the TWRP recovery you installed was ported by me). I could give you some advice (of my experiences with this phone and porting) and my basic config (which builds recovery successfully) if you want.
Does it have to go through all that trouble for Xposed? Or only if you want to install it via recovery (not classic / APK)?
Because recovery will trigger Knox (bye warranty).
Anyone installed Xposed the classic way on i9195i?
Alte.78 said:
Getting Root
For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu.
Click to expand...
Click to collapse
If we install TWRP, can't we just flash SuperSU zip from recovery to avoid the KingRoot removal hassle?
Alte.78 said:
Installing Xposed
Xposed install sent my device into boot loop. Fixing permissions from recovery allowed me to boot, but gapps was having permanent ANRs. Upon investigation it looks like Xposed for KK is not designed to take selinux enforcing mode into account. Specifically it installed app_process with wrong security context making device unbootable.
Click to expand...
Click to collapse
Was this boot loop after classical (write to /system), or recovery install?
I installed Xposed classical on i9195 (not i) KK (it also has selinux enforcing) without problems. Is there a difference that I'm not aware of?
Thanks.
Alte.78 said:
Trying to purchase Galaxy S4 Mini (GT-I9195) I received S4 Mini Plus (GT-I9195I) from online retailer. After some consideration I decided to treat this as a challenge and not to return the purchase. Here is what I learned so far about hacking this tiny piece of electronics:
Getting Root
I was not able to get root on the firmware installed on the phone (I9195IXXU1AOB1). The way I fixed that was to download another firmware from SamMobile and flashed it with Kies. The highest version I was able to flash without issues was I9195IXXU1AOD2, and it immediately updated to I9195IXXU1AOG1. For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu. This did not trip Knox device status, BTW.
Flashing Custom Recovery
I downloaded official TWRP recovery from teamw.in and decided to go the hard way and install the recovery doing dd fom command line (ConnectBot) - I was hoping this will help me to keep the warranty. Worked just fine, but tripped Knox bit nevertheless. NB: avoid extra hassles and just use Odin to install recovery.
Installing Xposed
Xposed install sent my device into boot loop. Fixing permissions from recovery allowed me to boot, but gapps was having permanent ANRs. Upon investigation it looks like Xposed for KK is not designed to take selinux enforcing mode into account. Specifically it installed app_process with wrong security context making device unbootable. The fix is very simple:
1. Install Xposed Installer and ES File Explorer.
2. Open Xposed Installer, go to Framework menu, select "Recovery (write zip to SD card, flash manually)" Installation mode, press "Install/Update".
3. Open ES File, navigate to /sdcard/Andriod/data/de.robv.android.xposed.installer/files. There are two files there: Xposed-Installer-Recovery.zip and Xposed-Disabler-Recovery.zip
4. Now comes the fun part: in both archives you need to modify META-INF/com/google/android/update-binary: comment or delete all "chmod", "chown" and "restorecon" commands and replace "cp XXX/app_process[.orig] XXX/app_process" with "cat XXX/app_process[.orig] > XXX/app_process". This will keep both permissions and security context of the file. Unpack, edit, repack.
5. Reboot into recovery, install Xposed-Installer-Recovery.zip, enjoy.
I will send patch to Xposed maintainer later this week. But we have not seen new releases of Xposed fo KK for over a year now, so I am not sure it will get released any time soon.
I will update the post as my adventures continue - my plan is to have CyanogenMod on this device some day. Stay tuned.
Click to expand...
Click to collapse
Thanks for the Xposed trick!
I managed to root according to your instructions (King root the supersu me), then install xposed through flashfire.
No need to flash custom recovery!
So knox is still 0x0!!
Great!
nick_white said:
Does it have to go through all that trouble for Xposed? Or only if you want to install it via recovery (not classic / APK)?
Because recovery will trigger Knox (bye warranty).
Anyone installed Xposed the classic way on i9195i?
Click to expand...
Click to collapse
Yes you have. Normal install (Write to /system) will send your phone into bootloop and you will have to re-flash your rom. I've tried that.
Karboush said:
Thanks for the Xposed trick!
I managed to root according to your instructions (King root the supersu me), then install xposed through flashfire.
No need to flash custom recovery!
So knox is still 0x0!!
Click to expand...
Click to collapse
Thats absolutely cool! I want to have custom recovery anyway, but your discovery will surely help a lot of people. :good:
nick_white said:
Was this boot loop after classical (write to /system), or recovery install?
I installed Xposed classical on i9195 (not i) KK (it also has selinux enforcing) without problems. Is there a difference that I'm not aware of?.
Click to expand...
Click to collapse
For me it failed both ways wiping out security context of app_process. Maybe your better luck has something to do with a different rom or Xposed version you are using?
Getting Root
I was not able to get root on the firmware installed on the phone (I9195IXXU1AOB1). The way I fixed that was to download another firmware from SamMobile and flashed it with Kies. The highest version I was able to flash without issues was I9195IXXU1AOD2, and it immediately updated to I9195IXXU1AOG1. For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu. This did not trip Knox device status, BTW.
Could you point me as to where did you find the firmware for the phone. I'm tempted to try rooting it. Is xposed necessary for the root to take full effect or no ? Cause it sounds a bit tricky and risky.
CostasV23 said:
Could you point me as to where did you find the firmware for the phone.
Click to expand...
Click to collapse
Try this link: http://www.sammobile.com/firmwares/database/GT-I9195I/
soo
Alte.78 said:
Trying to purchase Galaxy S4 Mini (GT-I9195) I received S4 Mini Plus (GT-I9195I) from online retailer. After some consideration I decided to treat this as a challenge and not to return the purchase. Here is what I learned so far about hacking this tiny piece of electronics:
Getting Root
I was not able to get root on the firmware installed on the phone (I9195IXXU1AOB1). The way I fixed that was to download another firmware from SamMobile and flashed it with Kies. The highest version I was able to flash without issues was I9195IXXU1AOD2, and it immediately updated to I9195IXXU1AOG1. For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu. This did not trip Knox device status, BTW.
Click to expand...
Click to collapse
So my phone has the AOD1 firmware can i root it like AOD2? Im in greece
Alte.78 said:
For me it failed both ways wiping out security context of app_process. Maybe your better luck has something to do with a different rom or Xposed version you are using?
Click to expand...
Click to collapse
Can you tell me if these will work for sure I have the aob1 firmware
Ok, so I have mine updated to I9195IXXU1AOG1. How do I get SuperSU on it without changing Knox to 0x1?
Which version of Xposed is everyone using? On the S4 Mini Plus?
xposed?
Is xposed necessary for the rooting process? or can i just skip it to avoid all the fuzz?
Alte.78 said:
Yes you have. Normal install (Write to /system) will send your phone into bootloop and you will have to re-flash your rom. I've tried that.
Click to expand...
Click to collapse
I upgraded my firmware to:
PDA: I9195IXXU1APA1
CSC: I9195IPHN1APA1
which is also (one of) the latest version, and has the Stagefright vulnerabilities fixed.
Then rooted with latest KingRoot (4.80) + Super Sume Pro.
Then installed Xposed 2.6.1 (stable) and installed "classical" (write to /system). It worked, no bootloops. Maybe you tried a different Xposed version?
Hi! anyone have a baseband I9195LUBUCNJ2?
Synomenon said:
Which version of Xposed is everyone using? On the S4 Mini Plus?
Click to expand...
Click to collapse
Im using the app_process 58 and
xposedBridge.jar 54 which i think is the latest stable edition as of 13/07/2016
Xposed installer version 2.61 with auto flash in recovery method no problems 5 months that i have it
Full debloat stock ROM on Samsung S4 mini Plus (GT-i9195i)
For more than a year, after I upgraded my firmware to:
PDA: I9195IXXU1APF1
CSC: I9195IYUX1APG1
which was the latest version from https://www.sammobile.com/firmwares/database/GT-I9195I/
I am using a debloat version of Galaxy S4 mini Plus (serranoveltexx). Inspired by @btnetro I made a script and tested a full debloat stock ROM on Samsung S4 mini Plus (GT-i9195i). All this time my device has worked very well and even now I am very pleased with him. For those who want to keep stock OS like me, I decided to share with you this flashable zip.
First flash via Odin, a custom recovery on your device( installation instructions here: https://forum.xda-developers.com/galaxy-s4-mini/development/recovery-cwm-twrp-philz-t3182207 ), restart your device and copy attached files in the root of your ext. SD card. Reboot your device in recovery mode and flash “Full_debloat_i9195i.zip”. For those who want to keep weather widget flash this file “weather2014_A3.zip” too (first debloat). Wipe /cache and reboot your device.
OK, i've a weird issue.
I tried all the available recoveries (Philz touch 6.59.0, twrp 2.8.4.0 & 2.8.7.1 etc, and all flashed with odin method) but none of them recognize my external SD.
I tried other sd cards as well, known to be good as they're used in other phones, but end up with th same.
Funny part is that inside os (stock KK 4.4.4) i can see all the files in SD card...
Any suggestion?
I'm trying to install the new OTA that was just released while keeping Xposed, Root, and TWRP and coming up with a process for the future to apply each OTA going forward without dealing with the mess I'm dealing with now. Any and all help is appreciated . I'm very strong and comfortable with using fastboot commands and flashing and just need someone to help me wrap my head around the process of doing this and step by step instructions of achieving my goal. So currently I have downloaded the new OTA_PERFUME_WL_M60_SENSE80GP_VZW_NA_Gen_Unlock_1.80.617.1_R-1.53.617.5_release_480240aw6u8xea6328m583.zip file. I have the latest TWRP installed on my phone, I have the latest Systemless Root zip (BETA-SuperSU-v2.74-2-forceencrypt.zip), as well as the latest Systemless Xposed zip (Xposed-v85.6-sdk23-systemless.zip). I have also downloaded the TWRP clean system Backup 1.53.617.5_twrp.zip. My phone is a T-Mobile HTC 10 that I've converted into a US Unlocked model by S-Offing it, changing the CID to the super CID (11111111), and installed the 1.53.617.5 RUU. I tried doing different steps on different guides here and now my phone is all sorts of messed up. Root isn't working 100% (es file explorer fails when trying to toggle on root explorer, but fx explorer works fine), and Xposed is broken (modules don't work, Xposed app saying no framework found even though I've flashed it). Can someone help me with what I should do to be able to install the OTA, root, have Xposed, and keep TWRP so that way in the future, I can apply and OTA and keep the rest?
Thanks!
wschamps42 said:
I'm trying to install the new OTA that was just released while keeping Xposed, Root, and TWRP and coming up with a process for the future to apply each OTA going forward without dealing with the mess I'm dealing with now. Any and all help is appreciated . I'm very strong and comfortable with using fastboot commands and flashing and just need someone to help me wrap my head around the process of doing this and step by step instructions of achieving my goal. So currently I have downloaded the new OTA_PERFUME_WL_M60_SENSE80GP_VZW_NA_Gen_Unlock_1.80.617.1_R-1.53.617.5_release_480240aw6u8xea6328m583.zip file. I have the latest TWRP installed on my phone, I have the latest Systemless Root zip (BETA-SuperSU-v2.74-2-forceencrypt.zip), as well as the latest Systemless Xposed zip (Xposed-v85.6-sdk23-systemless.zip). I have also downloaded the TWRP clean system Backup 1.53.617.5_twrp.zip. My phone is a T-Mobile HTC 10 that I've converted into a US Unlocked model by S-Offing it, changing the CID to the super CID (11111111), and installed the 1.53.617.5 RUU. I tried doing different steps on different guides here and now my phone is all sorts of messed up. Root isn't working 100% (es file explorer fails when trying to toggle on root explorer, but fx explorer works fine), and Xposed is broken (modules don't work, Xposed app saying no framework found even though I've flashed it). Can someone help me with what I should do to be able to install the OTA, root, have Xposed, and keep TWRP so that way in the future, I can apply and OTA and keep the rest?
Thanks!
Click to expand...
Click to collapse
I am also just starting this procedure... Just bought my 10 today, and I am starting slowly.. All I know is that if you dont change anything in /system directory and have stock recovery, OTAs perform fine.
So my plan is unlock bootloader, flash TWRP, root, flash ElementalX, install xposed and after that flash stock firmware. Both SuperSU AND Xposed should be systemless. I know that AdAway can also be systemless, but I have to figure out everything beucase I just charged and turn on the phone
Download Xposed for Material Design... I had the same issue with the "framework not found" error.
civicdelslow said:
Download Xposed for Material Design... I had the same issue with the "framework not found" error.
Click to expand...
Click to collapse
Yeah I've downloaded the latest. Now I have an Xposed is installed but not active error :-/
The last version (85.6) doesn't work that well. It's better to install version 85.5 which works fine.
I keep having this problem. I just tried both KINGROOT and CF-AUTO ROOT.
After doing this whole process through ODIN. I then try to flash the latest TWRP from their website : dl.twrp.me/jfltetmo/twrp-3.2.0-0-jfltetmo.img.tar.html
Then after that finishes, I try to boot into recovery and it gives me the message: recovery is not seandroid enforcing and just sits there.
I have a tmobile s4.
and I also checked if I am indeed rooted by using an app from the play store to check root and it shows Im rooted.
Any help would be great.
Root isn't needed to flash a twrp.
Tried flashing the latest stock rom and twrp without rooting the phone?
audit13 said:
Root isn't needed to flash a twrp.
Tried flashing the latest stock rom and twrp without rooting the phone?
Click to expand...
Click to collapse
Yup didn't work after trying it all the only thing that did work was SkipSoft Unified Android Toolkit and it was the easiest thing I ever used.
Krappa420 said:
Yup didn't work after trying it all the only thing that did work was SkipSoft Unified Android Toolkit and it was the easiest thing I ever used.
Click to expand...
Click to collapse
I have the exact problem, can you kindly explain in details how you went about it? I already downloaded SkipSoft.
Same issues here, buddy.
I tried to work on solving it out for approximately 8 hours and still no sign of success. Tried to reflash stock OS back on the phone via ODIN and it went successful. Tried CF-Auto-root file and it went through successful. But when it only came to the TWRP file, it went successful onto flashing on ODIN's side, but now something is interfering with the boot up process onto TWRP now. Hopefully there's a alternative towards this issue, since i've been wanting to reflash a Nougat OS onto the device.
Edit: I give credit to @Krappa420 for the mention of "SkipSoft Unified Android Toolkit" because i just installed the program on my laptop now and it went successful. But since i already had other materials pre-installed, some others with ODIN and ADB installed can just download this TWRP version here: https://dl.twrp.me/jfltexx/twrp-2.7.0.0-jfltexx.img.html
Edit #2: Seems that the TWRP version is too old to flash some of the newer OS's, such as nougat itself. Will find a way to update TWRP without breaking the boot up process, like the past attempts
Edit #3: After fiddling with TWRP versions 2.7.0.0 and up, i managed to get it capped up to 3.1.1 any future versions will most likely not work, so you're capped at 3.1.1 Here's the link for flashing it with ODIN: https://dl.twrp.me/jfltexx/twrp-3.1.1-0-jfltexx.img.tar.html
So you twrp 3.1.1 and it will work right
I having the same issue
Thank you
so do i need to install cf-auto root first or the twrp 3.11
what are the steps to install
Thank you for helping a disabled veteran
timj3371 said:
so do i need to install cf-auto root first or the twrp 3.11
what are the steps to install
Thank you for helping a disabled veteran
Click to expand...
Click to collapse
It wouldn't really matter what order you're using.
You can use CF-Auto-Root to root it for you while you have stock recovery still, and after you can flash to TWRP and use a custom recovery afterwards
Or you can flash TWRP first and flash a SuperSU zip file afterwards and it'll give you root while maintaining to have TWRP installed.
But to sum it up, it wouldn't matter what order you choose. Help yourself
Trwp
What version of twrp I need to use
Thank you
timj3371 said:
What version of twrp I need to use
Thank you
Click to expand...
Click to collapse
TWRP version 3.1.1
Thank you for the help I have lineage installed. Wow so fast. How ever when trying to root it I get a error says binary occupied. If I uninstall I get no root available. How do I install root ? Thank you so much
A disabled veteran
timj3371 said:
Thank you for the help I have lineage installed. Wow so fast. How ever when trying to root it I get a error says binary occupied. If I uninstall I get no root available. How do I install root ? Thank you so much
A disabled veteran
Click to expand...
Click to collapse
Before anything, try to install the SuperSU app over on the play store, if it says you're not rooted, you may have to restart the whole process within TWRP and reflash the SuperSU Zip file.
Thank you
Says the binary is occupied in su
Where do I find su zip
Should I use the chain fire auto zip
Thanks
timj3371 said:
Says the binary is occupied in su
Where do I find su zip
Should I use the chain fire auto zip
Thanks
Click to expand...
Click to collapse
Try this one: https://download.chainfire.eu/696/supersu/
If it keeps on persisting, I'll have to find another way
I tried that file and it just sits in booting. I left it be then reinstated the ROM. Still no root its OK tight not to have root
Thank you
timj3371 said:
I tried that file and it just sits in booting. I left it be then reinstated the ROM. Still no root its OK tight not to have root
Thank you
Click to expand...
Click to collapse
Yeah try to re-flash the ROM again but this time flash magisk through TWRP since SuperSU is being trippy on your S4
Thank you for the help
Dummy me I found out from reading other forums you have to go in to tools and enable root after going in to recovery and flash the root file in the extra section.
Every thing works
Thank you so much
Disabled veteran
How to root first time phone with latest update with magisk method?
I'm find this simple way without TWRP
Is this way good?
No need to install TWRP in this way and no need some other .zip files like "no verify opt encrypt"
or something like that is not necessary. Is that a good idea? What are these additional .zip files for?
I have some experience with root on older samsung phones that have been routed by installing TWRP and flashing .zip magisk pach.
Nothing more was needed.
In short,
This way from joutube goes like this:
First the OEM is unlocked, magiskmanager.apk is downloaded and installed apk. After that the AP file that we downloaded before of firmware is patched with magisk app and inserted into the downloads folder.
After that, we flash the patched AP file over the odin and that's it. Will this work for me on the latest firmware?
I found this way that involves installing TWRP and some zip file.
xxsen said:
How to root first time phone with latest update with magisk method?
I'm find this simple way without TWRP
Is this way good?
No need to install TWRP in this way and no need some other .zip files like "no verify opt encrypt"
or something like that is not necessary. Is that a good idea? What are these additional .zip files for?
I have some experience with root on older samsung phones that have been routed by installing TWRP and flashing .zip magisk pach.
Nothing more was needed.
In short,
This way from joutube goes like this:
First the OEM is unlocked, magiskmanager.apk is downloaded and installed apk. After that the AP file that we downloaded before of firmware is patched with magisk app and inserted into the downloads folder.
After that, we flash the patched AP file over the odin and that's it. Will this work for me on the latest firmware?
I found this way that involves installing TWRP and some zip file.
Click to expand...
Click to collapse
I have used the method on a Samsung Galaxy Xcover 4s with new firmware.
However I don't know if it will work with Samsung Galaxy S9 due to the need for "dm-verity and force encryption disabler".
Have you rooted?