Database Develop

XPOSED Framework Install - Galaxy S4 SCH-I545 (OF1) Flashfire

I've been reading thousands of forum entries on how to install the xposed framework for my device and I can't seem to get it. They all end the same way -- stuck at the Verizon logo screen.
I am using a Verizon Samsung Galaxy S4 on stock Lollipop (5.0.1). I only have the stock bootloader thanks to it being locked before I laid hands on the device, but I do have Flashfire, Root, SuperSU. Each time I fail, I use ODIN to flash I545VRUGOF1_I545VZWGOF1_I545VRUGOF1_HOME.tar and try again.
I have tried using a deodexed rom by flashing the above with ODIN, then using Flashfire to OTA update: I545_OF1_Stock_Rooted_Deodexed_ROM.zip
Next, install the XposedInstaller_3.0_alpha4.apk
I then tried flashing:
xposed-v71-sdk21-arm-arter97-V6-snapdragon
xposed-v75-sdk21-arm-arter97-snapdragon
xposed-v86-sdk21-arm
They all result in freezing on the Verizon logo during boot.
I can flash xposed-sdk21-arm-20150430-arter97 on to the deodexed rom and it will work, but the Xposed Installer says it's not the most recent and all modules yield the same error:
This module requires a newer XposedBridge version (30) and thus cannot be activated.
Then I try with the stock rom (odexed).
I can flash:
xposed-v71-sdk21-arm-arter97-V6-snapdragon
xposed-v75-sdk21-arm-arter97-snapdragon
xposed-v86-sdk21-arm
Without a crash; So long as the XposedInstaller_3.0_alpha4.apk is not installed. If I install the XposedInstaller then try to flash, it hangs on the Verizon logo during boot.
Finally, if I flash the zips first, then reboot and install the XposedInstaller it will yield me the same result of not the most recent version and I get the requires newer bridge for all modules.
Because it's an S4 there are hundreds of forums and guides, but I can't find one that applies to me. That makes me either the worst internet researcher in the world -- or I'm missing something so obvious that it's embarrassing...well, humiliating.
Can anyone offer a suggestion? ...and yes, I've read every read only forum to the last line and every XDA Lollipop forum. I've reflashed my phone almost two dozen times trying different suggestions with absolutely no luck.

I was having similar issues trying to get xposed on 5.0.1.
Long story short I gave up and flashed 5.1.1 onto my Note 4 and used wanam's custom xposed framework.

Galaxy S4
I don't believe there is a stock 5.1 firmware for the Galaxy S4. More importantly, I have to believe you can install Xposed on the S4. I just hate feeling like I'm missing something so simple!!

DemoMatrix said:
I don't believe there is a stock 5.1 firmware for the Galaxy S4. More importantly, I have to believe you can install Xposed on the S4. I just hate feeling like I'm missing something so simple!!
Click to expand...
Click to collapse
I have a i545 with locked boot loader I used flashfire to flash XposedInstaller_3.0_alpha4 and xposed-v85.0-samsung-5.0.x-sdk21-test-by-dkcldark.zip and it has been working fine for me, I thought my phone was froze on the Verizon splash screen on the first restart so I pulled the battery and tried starting the phone again and it started like normal

krusherkills123 said:
I have a i545 with locked boot loader I used flashfire to flash XposedInstaller_3.0_alpha4 and xposed-v85.0-samsung-5.0.x-sdk21-test-by-dkcldark.zip and it has been working fine for me, I thought my phone was froze on the Verizon splash screen on the first restart so I pulled the battery and tried starting the phone again and it started like normal
Click to expand...
Click to collapse
I think I might love you.
I haven't seen that v85 file anywhere. I'm going to go search for it now. Thank you!

krusherkills123 said:
I have a i545 with locked boot loader I used flashfire to flash XposedInstaller_3.0_alpha4 and xposed-v85.0-samsung-5.0.x-sdk21-test-by-dkcldark.zip and it has been working fine for me, I thought my phone was froze on the Verizon splash screen on the first restart so I pulled the battery and tried starting the phone again and it started like normal
Click to expand...
Click to collapse
That went faster than I expected. Going to give it a flash now.

Well, thank you for the effort.
It flashed very quickly and then rebooted without a problem, but the Xposed Installer still shows, "The Xposed framework is not installed. Please download the latest ZIP file from XDA and flash it manually via recovery." and all the modules say, "..requires a newer XposedBridge version (30) and thus cannot be activated".
I don't suppose you'd be willing to use FlashFire to make a full backup (minus your cache, of course) to share?

Well, thank you for the effort.
It flashed very quickly and then rebooted without a problem, but the Xposed Installer still shows, "The Xposed framework is not installed. Please download the latest ZIP file from XDA and flash it manually via recovery." and all the modules say, "..requires a newer XposedBridge version (30) and thus cannot be activated".
I don't suppose you'd be willing to use FlashFire to make a full backup (minus your cache, of course) to share?

UR 31337
krusherkills123 said:
I have a i545 with locked boot loader I used flashfire to flash XposedInstaller_3.0_alpha4 and xposed-v85.0-samsung-5.0.x-sdk21-test-by-dkcldark.zip and it has been working fine for me, I thought my phone was froze on the Verizon splash screen on the first restart so I pulled the battery and tried starting the phone again and it started like normal
Click to expand...
Click to collapse
Thank you! I uninstalled Xposed Installer and rebooted. Reinstalled Xposed Installer, rebooted, then flashed the file again. Upon that reboot it did the, "Upgraded file xx of xx" and now it's installed!
I can't thank you enough!

View attachment xposed-v65-sdk21-arm-arter97-V5-krait.zip
View attachment de.robv.android.xposed.installer_v33_36570c-1.apk
The Wanam Module is the only thing that I've used.

DemoMatrix said:
Thank you! I uninstalled Xposed Installer and rebooted. Reinstalled Xposed Installer, rebooted, then flashed the file again. Upon that reboot it did the, "Upgraded file xx of xx" and now it's installed!
I can't thank you enough!
Click to expand...
Click to collapse
I am in same boat do you think this very would work if I have the strang5litre rom on the s4. Or would I need another ver. What rom did you have when you got this to work the stick one?
---------- Post added at 11:18 PM ---------- Previous post was at 11:15 PM ----------
trulosdoulos said:
I am in same boat do you think this very would work if I have the strang5litre rom on the s4. Or would I need another ver. What rom did you have when you got this to work the stick one?
Click to expand...
Click to collapse
Stock one* I meant

I'm using the stock rom, jfltvzw, 5.0.1

I'm on stang5litre. I'm surprised you got it to work on stock.

Details
DemoMatrix said:
I'm using the stock rom, jfltvzw, 5.0.1
Click to expand...
Click to collapse
Could you provide the steps you used to achieve this? Thanks!

Please explain how to do this.
Hello.
Can anyone explain the steps to install Xposed framework on the Samsung Galaxy S4 SCH-i545, rooted with stock ROM 5.0.1? I found and downloaded the two files noted in krusherkills123's post, but Flashfire only shows the XposedInstaller_3.0_alpha4 under "Flash firmware package" where it brings up a blank "Partitions" screen and no options.
I used Flashfire to flash the other file, xposed-v85.0-samsung-5.0.x-sdk21-test-by-dkcldark.zip, which I hated to do since I have no idea what it actually does. Since I don't know what it does, I can't confirm that flashing it was successful.
Any help would be appreciated.

Same question here, rooted Verizon S4 I545VRSGPL1, can I install xposed? This is stock rom, rooted with kingroot then cleaned to use SuperSU
People have done with OF1, not sure about PL1, but they are not far apart
Thx!

[Guide] Pass Safetynet on a rooted 7.0 AOSP based ROM - Updated 11-01-2016

Update (11/09) - This method no longer works with the november security updates from Google as it causes suhide to break.
Here are the steps to follow
If you are already rooted, fully unroot. I do this by doing the following.
1) In the SuperUser app, go to settings and choose to do a full unroot. Choose "No" when it prompts you to restore your stock boot.img
2) Let the system reboot normally.
3) Reboot to recovery
4) If you have Magisk installed, flash the Magisk uninstaller Link
5) If you have suhide installed, flash rm-suhide 0.51 Link
6) Flash your ROM's boot.img extracted from your ROM (simply dirty flashing should also work), or install a custom kernel of your choice
At this point you should have a stock boot.img (or custom kernel) with no traces of SuperUser anywhere
Install SuperUser 2.78 Link
Install suhide 0.55 Link
Reboot into system. Verify that you have root. I'm not 100% sure this is necessary, but I like to do it before proceeding.
Reboot back into recovery.
Flash xsetpropSu.zip (attached to this post) Link
Reboot the system
Install RootSwitch 1.3.3.2 Link
Open up RootSwitch, uncheck disable all SU daemons. Disable Root
Pass SafetyNet
Optional
Using tasker to automatically disable root when certain applications are run. @NYZack made a little writeup here
Credits:
@NYZack - Helping me figure out how to put all of this together
@Captain_Throwback - For help with xsetprop
@Chainfire - SuperSU + SuHide
@topjohnwu - Magisk

work around found

no longer relevant post..

I don't know if the kernel can be modified to pull that trick. Even if someone does though, it's not going to last long. Every bypass you can find, Google can find. Then they know what to fix. The only way to win, is not to play.
And no, you can't lock the bootloader without wiping data.

Well I got it to work...I will turn this thread into a Guide. Who knows how long it will last, but...at least it's working for now.

Thread updated with instructions. I hope this can help someone!

So there's no way to do this without rooting and magisk?

3dawg said:
So there's no way to do this without rooting and magisk?
Click to expand...
Click to collapse
I want root, so I did not try to do that. If your bootloader is unlocked, I do not think there's a way to do it.

Thanks
skaforey said:
Thread updated with instructions. I hope this can help someone!
Click to expand...
Click to collapse
Yes I just followed these instructions and I am green panel. I have to check at a terminal to pay with phone but it probably will work. One note that was kinda unclear in case others do same....It should read :
Turn the Root switch ON....not OFF....when wanting to use AP. You can turn it back on when you want to do other things that require root permissions. I believe this is dynamic and working with the magisk mount point in addition to tricking the boot process into thinking the bootloader is locked.
Thanks so much for this. I was so angry with Google. And I was just going to say FK it and not use AP.
WORKS! Do all the steps in the order he says above and you can turn root off and on at will and have Android Pay work just fine! YAY!

skaforey said:
This thread started as a plea for help, but thanks to @NYZack I have gotten it to work.
Here are the steps to follow
If you are already rooted, fully unroot. I do this by doing the following.
1) If you have suhide installed, download rm-suhide 0.51 Link
2) In the SuperUser app, go to settings and choose to do a full unroot. Choose "No" when it prompts you to restore your stock boot.img
3) Let the system reboot normally.
4) Reboot to recovery
5) Flash rm-suhide 0.51
6) Flash your ROM's boot.img extracted from your ROM (simply dirty flashing should also work), or install a custom kernel of your choice
At this point you should have a stock boot.img (or custom kernel) with no traces of SuperUser anywhere
Install SuperUser 2.78 Link
Install Magisk v8.zip Link
Install suhide 0.55 Link
Reboot into system
Install Magisk Manger 2.1 (apk) Link
Open up Magisk Manager app and go to modules. Click on the + button. Add the following zip for xsetprop Link
Install RootSwitch 1.3.1.2 Link
Reboot system
Using Root Explorer (or some other file manager capable of root access), browse to /magisk/xsetprop and modify post-fs-data.sh . Add the following line to the end of the file, save and exit
Code:
xsetprop ro.boot.flash.locked 1
Reboot system
Open up RootSwitch, uncheck disable all SU daemons. Disable Root
Pass SafetyNet
Click to expand...
Click to collapse
FYI - The latest version of the xSetProp zip (0.2.1 as of this post) handles setting that prop automatically, and has additional logging. I'd recommend using that and you can remove that portion of your guide.

Captain_Throwback said:
FYI - The latest version of the xSetProp zip (0.2.1 as of this post) handles setting that prop automatically, and has additional logging. I'd recommend using that and you can remove that portion of your guide.
Click to expand...
Click to collapse
Thank you! Instructions updated (also tried to give proper credit all around).
I think Chainfire might be in the process of doing something similar without the need for Magisk.
I suppose we could also probably use the xsetprop binary along with a su.d script to run the necessary commands on startup? This would avoid having to use Magisk all together.
If I get some time I might try that out.

No longer works after I reboot the device. It's almost like it knows about my hack. It passes the safety net thing with green screen yet I get message saying that can't verify blah blah...your phone might be rooted! I've updated to 0.2.1 of the xprop and double checked the other things like suhide and magisk and so on. Wth ... Less than a day and Google changed something? I'm baffled. Help!

Pkt_Lnt said:
http://www.xda-developers.com/android-safetynet-now-reportedly-tripped-by-unlocked-bootloaders/
Click to expand...
Click to collapse
Thanks so much for taking the time to write this out.
I am 100% successful with M ROMs like ResRemix
However on my Nexus 6 with N ROMs (like Nitrogen or cDroid) I can't get SafetyNet to pass this way. With Root Switch I can get PoGo to work but following these instructions to a T I still don't have green SN
I wonder if it is the kernel ? What kernel have you been successful with?
Lastly are you aware of any way to find success with 7.1 ROMs?
---------- Post added at 12:31 AM ---------- Previous post was at 12:27 AM ----------
photolarry said:
No longer works after I reboot the device. It's almost like it knows about my hack. It passes the safety net thing with green screen yet I get message saying that can't verify blah blah...your phone might be rooted! I've updated to 0.2.1 of the xprop and double checked the other things like suhide and magisk and so on. Wth ... Less than a day and Google changed something? I'm baffled. Help!
Click to expand...
Click to collapse
Is the message you are getting coming up with SafetyNet or with PoGo ... or when ??

jcrompton said:
Thanks so much for taking the time to write this out.
I am 100% successful with M ROMs like ResRemix
However on my Nexus 6 with N ROMs (like Nitrogen or cDroid) I can get SafetyNet to pass this way. With Root Switch I can get PoGo to work but following these instructions to a T I still don't have green SN
I wonder if it is the kernel ? What kernel have you been successful with?
Lastly are you aware of any way to find success with 7.1 ROMs?
---------- Post added at 12:31 AM ---------- Previous post was at 12:27 AM ----------
Is the message you are getting coming up with SafetyNet or with PoGo ... or when ??
Click to expand...
Click to collapse
Yea I know I think it's something to do with either the kernel I've selected or perhaps suhide no longer works...I'm not sure what the deal is. I'm running Franco #55 and even without root, I get failure but inside the testing app ...see attached

Thanks for this write-up! I was able to pass SafetyNet in both apps while running Pure Nexus 7 w/ Stock OpenGapps.
I think one key thing that was skipped in the OP - be sure your ROM is SafetyNet compatible to begin with. I've run numerous ROMs that even before Google started checking bootloaders, wouldn't pass SafetyNet even if unrooted. For example, I just tried the OP method with Despair's new 7.1 ROM and it failed (probably won't work on 7.0 either). But with Pure Nexus 7.0 it works great.

MrBrady said:
Thanks for this write-up! I was able to pass SafetyNet in both apps while running Pure Nexus 7 w/ Stock OpenGapps.
I think one key thing that was skipped in the OP - be sure your ROM is SafetyNet compatible to begin with. I've run numerous ROMs that even before Google started checking bootloaders, wouldn't pass SafetyNet even if unrooted. For example, I just tried the OP method with Despair's new 7.1 ROM and it failed (probably won't work on 7.0 either). But with Pure Nexus 7.0 it works great.
Click to expand...
Click to collapse
I'm using stock Rom and only custom kernel so this should work on Nbd90z....I'd think. Last test was dreaded message but I'm trying to add few things to suhide blacklist. We shall see

I get the green screen. But then when I tap at store nfc terminal...it claims error....I'm going to try hiding nfc service, and what I think is play services based on uid chainfire explained. I'll try a small purchase and remember to screen capture the error if occurs

skaforey said:
Thank you! Instructions updated (also tried to give proper credit all around).
I think Chainfire might be in the process of doing something similar without the need for Magisk.
I suppose we could also probably use the xsetprop binary along with a su.d script to run the necessary commands on startup? This would avoid having to use Magisk all together.
If I get some time I might try that out.
Click to expand...
Click to collapse
I built the mod for people that were already using Magisk. If you're not using Magisk, then of course you can try just putting the binary in /su/xbin and put the post-fs-data.sh in /su/su.d and see if that works for setting the props at boot time.
I don't use Xposed, so using Magisk + phh's Superuser was my target for the module. I also did try the su.d method with SuperSU, but it wasn't working on my device. I also didn't want to have to use RootSwitch. But feel free to unpack the zip and try whatever combinations you want.

photolarry said:
No longer works after I reboot the device. It's almost like it knows about my hack. It passes the safety net thing with green screen yet I get message saying that can't verify blah blah...your phone might be rooted! I've updated to 0.2.1 of the xprop and double checked the other things like suhide and magisk and so on. Wth ... Less than a day and Google changed something? I'm baffled. Help!
Click to expand...
Click to collapse
Still working for me. Are you sure you disabled root in Root Switch? It automatically re-enables upon logon. Also be sure your xsetprop file is correct.
You can check by using the getprop command

skaforey said:
Still working for me. Are you sure you disabled root in Root Switch? It automatically re-enables upon logon. Also be sure your xsetprop file is correct.
You can check by using the getprop command
Click to expand...
Click to collapse
I'm using it for android pay not pogo. And I did. I'm sure the prop is right or wouldn't get green go. It's an error from AP saying something about unable to verify and might be rooted....or words to that effect

[Q] Magisk v16 Problems T715

Hi all, i'm using a stock rom, rooted with magisk and debloated (manually). I always faced this problem, the 90% of the modules i try to install ends with something like that:
See Screen below
However i've never asked help because i tought it was a Magisk problem resolvible with an update...but every update ended always in the same way for me when trying to install some modules. I've also attached some logs here of when i tried to update xposed systemless if someone could help me it will be really apprecciated!
P.s Anyone facing the same problem? I've read somewhere that a similar problem is common with Motorola devices but idk if this is the case

Giuskiller said:
Hi all, i'm using a stock rom, rooted with magisk and debloated (manually). I always faced this problem, the 90% of the modules i try to install ends with something like that:
See Screen below
However i've never asked help because i tought it was a Magisk problem resolvible with an update...but every update ended always in the same way for me when trying to install some modules. I've also attached some logs here of when i tried to update xposed systemless if someone could help me it will be really apprecciated!
P.s Anyone facing the same problem? I've read somewhere that a similar problem is common with Motorola devices but idk if this is the case
Click to expand...
Click to collapse
Is this via Magisk manager?

ashyx said:
Is this via Magisk manager?
Click to expand...
Click to collapse
Yes this is via Magisk Manager, however the same error (could not mount something) appears also when i try to install a module via twrp. The "best" thing is that some module just works both way (Busybox NDK for example) while other fails both ways. No module work in a way and doesn't work in another. So basically if a module work in magisk can be installed also via twrp otherwise it cannot be installed, no matter what i try

I have the same problem. Trying to install viper4a.
I have no clue how to fix it

Giuskiller said:
Yes this is via Magisk Manager, however the same error (could not mount something) appears also when i try to install a module via twrp. The "best" thing is that some module just works both way (Busybox NDK for example) while other fails both ways. No module work in a way and doesn't work in another. So basically if a module work in magisk can be installed also via twrp otherwise it cannot be installed, no matter what i try
Click to expand...
Click to collapse
I think this is a bug in Magisk with the way some modules attempt to install and mount, which is why some work.
I'm surprised though that they don't install in TWRP. Is your device encrypted, can you mount /data in recovery?

ashyx said:
I think this is a bug in Magisk with the way some modules attempt to install and mount, which is why some work.
I'm surprised though that they don't install in TWRP. Is your device encrypted, can you mount /data in recovery?
Click to expand...
Click to collapse
Actually i'm at university, but when i come back home i will try and let you know. What i can say for now is that every zip i've flashed so far worked just flawlessy (well, apart magisk's ones)

Downloaded atmos dolby only module for nougat....rebooted snd stucked on samsung logo. Ohhhh.... How to get rid of this module, is anyway to do it?
Please help
Edit:
installed module uninstaller and followed it - > https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
working now.
Looking for info how to install viper4Android....

netgar said:
Downloaded atmos dolby only module for nougat....rebooted snd stucked on samsung logo. Ohhhh.... How to get rid of this module, is anyway to do it?
Please help
Edit:
installed module uninstaller and followed it - > https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
working now.
Looking for info how to install viper4Android....
Click to expand...
Click to collapse
Well as far as i know, if you're on stock rom you won't be able to install audio mods because they're in conflict with something in the Rom. You should use a custom rom instead. However not sure 100% about this, maybe some audio mods can work, but you should ask someone else, i'm not so informed

Phone stuck on booting screen after install

Hello,
first off, sorry. I was stupid and didn't read into it before installing (or trying to install) Xposed to my Samsung S8. Yes, i've read now that it doesn't work with the official ROM, but now it's a bit to late.
So. After rooting my S8 today (using TWRP) i wanted to install Xposed. I downloaded an installer from this site because.. umm, i had a brain fart. For some reason my brain took that site as the official website, so i downloaded it from a 3rd Party site instead of the actual website.
I installed the apk and granted root access. After that i clicked on install and Xposed installed successfully. After that it obviously asked me to reboot my device, which i did. But now i am stuck on the Samsung screen of the boot progress. I know i could technically just wipe the phone (again) and start anew, but i'd like to avoid that if possible. I can access TWRP, but if i try to access the system files in the file browser, it shows "0MB" and i can't access them.
I tried downloading an uninstaller linked in this thread, but i don't know which one i should download.
Sorry again for me being so stupid and not reading into it and downloading from some weird 3rd Party site.
Thanks in advance for the help!
EDIT: And yea, of course i didn't create a backup before installing Xposed. So if there is no way to properly uninstall it, i gotta wipe everything once again

Emilia-Chan said:
Hello, first off, sorry. I was stupid and didn't read into it before installing (or trying to install) Xposed to my Samsung S8.......
Click to expand...
Click to collapse
I don't have this device but, I believe that you should be able to flash (via TWRP) the Framework Uninstaller located on the following Official XPosed link. Just select the correct ARCH (ARM, ARM64, etc...) for your device.
http://dl-xda.xposed.info/framework/uninstaller/
If necessary, you can always try to obtain some additional member guidance and support from the following Q&A thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=3582142
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

In the link provided by @lbuprophen use the arm64 zip uninstaller (latest version) to uninstall exposed.
Just curious how long did you let it try to boot for,mine took 10-15 minutes for it to do it's thing and boot up.
Sent from my Samsung Galaxy S8 using XDA Labs

Ibuprophen said:
I don't have this device but, I believe that you should be able to flash (via TWRP) the Framework Uninstaller located on the following Official XPosed link. Just select the correct ARCH (ARM, ARM64, etc...) for your device.
Click to expand...
Click to collapse
I tried that before, unfortunately without success. It also may be noteworthy that my brain turned off and downloaded the XPosed installer off some 3rd Party site. I know. Stupid. But it happened.
spawnlives said:
In the link provided by @lbuprophen use the arm64 zip uninstaller (latest version) to uninstall exposed.
Just curious how long did you let it try to boot for,mine took 10-15 minutes for it to do it's thing and boot up.
Click to expand...
Click to collapse
I waited over an hour for my phone to boot, before and after flashing the uninstaller. I also tried wiping it and even completely formatting the data, everything without any success. It kept on not passing the Samsung screen and eventually bootlooping.
I fixed the issue by just flashing the stock rom with odin and then reinstalling TWRP and rooting my device again. Will stay away from XPosed with this phone for now.
Thanks for the advice anyways!

Emilia-Chan said:
.... I fixed the issue by just flashing the stock rom with odin and then reinstalling TWRP and rooting my device again. Will stay away from XPosed with this phone for now. Thanks for the advice anyways!
Click to expand...
Click to collapse
You did what I would have probably done myself in this situation by starting from scratch.
I just wanted to let you know that I believe that I had saw somewhere (within the dedicated area of the forum for your device) that individuals were successful with Magisk XPosed.
Though I do understand if you want to stay away from XPosed until your ready again and I'm happy to see that your at least up and running again.
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

I got the same even just after the installation of the apk for Systemless Xposed on an Xperia (XposedInstaller_3.1.5-Magisk.apk) found here: https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
I made a reboot as I like to isolate the issues while they happen. That was it: bootloop..

Modules not working, can't return to old version, wipe needed on Galaxy S8 / Nougat

Hi,
I was running stock ROM with stock recovery plus Magisk v16 and MagiskManager v5.9.1 on my Galaxy S8 and Nougat. As far as I remember I did install MagiskManager using adb, pushed, patched and pulled the boot.img, flashed it using Heimdall. Both apk and patched_boot.img are available on my hard disk...
I then updated MagiskManager using the in app update. Afterwards I used the "direct install" to update Magisk. That took me to 20.4 / 8.0.2. I don't remember if it asked to install the runtime.
I installed modules busybox, sqlite3 and movecertificates, but with no effect (e.g. there is no /system/bin/sqlite3, no nc in my path, user certs remain user certs). I also can't find any indication in MagiskManager that modules are installed.
I didn't have time to figure out what's wrong and tried to revert back to my old versions.
That's what I did: Full uninstall from MagiskManager 8.0.2. Reboot without Magisk, adb push MagiskManager-v5.9.1.apk. Flash my old patched_boot with Magisk v16 using Heimdall. But unfortunately that gives me Magisk Manager stuck on the splash sceen. No applet can get root access, e.g. su on adb shell blocks (needs ctrl+c). Ok, uninstalled MM.
I installed the stock boot img in the intention to load MM 8.0.2 before I flash M 20.4. That didn't accept my pattern for the "your device is encrypted" screen. Well... I flashed M 20.4 patched boot.img again. After first try it shows an integrity issue and offers to wipe the phone.
* Anyway to go from here besides wipe?
* What residuals might be blocking when returning to the old versions?
* Why are modules not working on current version?
Thank you

urbancubb said:
* Why are modules not working on current version?
Click to expand...
Click to collapse
Are they current module zips, or ones that you had laying around from before updating? The modules might be using outdated installation scripts (that's my prime suspect at least).
* What residuals might be blocking when returning to the old versions?
Click to expand...
Click to collapse
Magisk v16 is soooo old. It's gonna be almost impossible to give any kind of help with that. Better to update to a current Magisk release.
* Anyway to go from here besides wipe?
Click to expand...
Click to collapse
I have no idea, you'd wan't someone who knows Samsung for that. Your device's forum might be a good place to start.

Didgeridoohan said:
Are they current module zips, or ones that you had laying around from before updating? The modules might be using outdated installation scripts (that's my prime suspect at least).
Click to expand...
Click to collapse
I installed them from within Magisk Manager from the online repo.
I noticed that this might be the case, but as there was updates this year I think on at least two of them and none worked, I think its a general problem and not caused by the module itself. Any module I could use to test wich works for sure?
Didgeridoohan said:
Magisk v16 is soooo old. It's gonna be almost impossible to give any kind of help with that. Better to update to a current Magisk release.
Click to expand...
Click to collapse
Which didn't work... We'll see.
Didgeridoohan said:
I have no idea, you'd wan't someone who knows Samsung for that. Your device's forum might be a good place to start.
Click to expand...
Click to collapse
Good hint, I started a new thread.
Thank you!

For the modules issue, the only way to know for sure what happened is to look at the install logs and the Magisk log for the following reboot.
So if you get things up and running again, and the issue still persists, make sure to provide those.

One thing I didn't think of before: I recently tried the SafatyNet check (which failed), maybe the failed reboot was the first one after checking, I don't remember exactly.