yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Android Development (Snapdragon)] MysteryIII:
Ah ok, good to know.

I did following steps:

flashed latest Magisk Uninstaller in Recovery

flashed Boeffla kernel again (I used it before and Magisk Uninstaller restored stock kernel)

flashed Magisk 15.1 in Recovery

flashed devbase 1.11

booted phone and installed latest Magisk Manager

installed/flashed Xposed 87.3 SDK 23 in Magisk Manager (copied zip file to phone, went to Modules section, add module, chose Zip file with file manager).

rebooted phone

Except from SafetyNet I didn't find any issues with 15.1. Only thing App Systemizer would need an update: in the moment I use this module for BetterBatteryStats the App lags like hell. For some (few) Apps passing only "ctsProfile" and hiding in Magisk is enough to let them work, so "No Device Check" might be a big help.

€: Do you use any other Modules? I found out that "Privileged Api Booter" is incompatible with Xposed. Once I activated it Xposed stopped working.
[Galaxy S 5 Android Development (Snapdragon)] DerCasi:
Thanks first of all.

This way I managed to boot up my phone, it took ages. I ended up in a black screen with a pop-up telling "Oberfläche angehalten", which means as much as launcher is stopped. Pressed OK and message reappeared over and over again. At least I could enter the power menue, tapped reboot and now I'm in that bootloop again.

Is the bootloader to be flashed every time I flash the ROM?

Edit: Flashed unmodified zip (for Magisk-SU) and encountered the same issue, but without bootloop after reboot. It simply shows the same issue like after initial boot.
[Galaxy S 5 Android Development (Snapdragon)] It_ler:
Thanks for the installation steps. I'll let you know if it works with stock kernel too ... if I am curious enough to try it out tomorrow ?

I have some Xposed modules, e.g. Firefds. Nothing special ... or critical.

---------- Post added at 11:29 PM ---------- Previous post was at 11:20 PM ----------

No, you just have to flash the bootloader once. As long as you are in a bootloop, it may be caused by not applying the bootloader correctly.

That's why I recommend to flash the bootloader again.

Just to be sure that this is not the culprit.

Maybe you should try to flash the ROM zip file with noroot option. As you have TWRP recovery, you can flash SuperSu (or Magisk) zip file in recovery afterwards.

BTW ... have you already flashed the corresponding modem file with Odin?
[Galaxy S 5 Android Development (Snapdragon)] MysteryIII:
No problem. But I was talking about Magisk Modules not Xposed Modules. Privileged API Booter is a Magisk Module, once activated it kills Xposed completely.

I don't think Xposed has a kernel problem, I just use it boeffla because it is by far the most stable kernel with advantages, especially UMS Mode.
[Galaxy S 5 Android Development (Snapdragon)] DerCasi:
Oh, as I said bootloader worked fine, I should have said, that I rebooted several times after flashing BL and had no issues with former Alexndr 2.2. So I think thats not the problem.

I'll try a different modem and report back.

Edit: Same issue with different CP.
[Galaxy S 5 Android Development (Snapdragon)] It_ler:
If you have a backup of everything important on your S5, or there is nothing to be saved, you may have to do a factory reset (= wipe data).

Then flash the rom with noroot.

You should boot into system if the bootloader was applied successfully.

---------- Post added at 09:54 AM ---------- Previous post was at 09:53 AM ----------

I have no Magisk module installed except Xposed.
[Galaxy S 5 Android Development (Snapdragon)] Many40:
[MENTION=5150393]_alexndr[/MENTION] or anybody who could advice,

Yesterday I decided to move from Magisk to SuperSU just to check different root solution being on DevBase4.3/CQI4.

The steps which I performed (rebooted in between):

1. Removed Magisk with Magisk uninstaller,

2. Flashed latest SuperSU 2.82 SR5 -> gained root with no problems

3. Changed SuperSU to work in SBIN mode and flashed suhide-lite 1.0 -> passed SafetyNet

When everything seemed to work properly I realized that somehow Systemless devbase has been broken -> files placed in /data/devbase/system/framework stopped working.

Then I tried following workaround:

1. Flashed SYSTEMLESS DevBase v1.11 -> no change

2. Reflashed ROM (DevBase4.3/CQI4) without root, flashed SuperSU with suhide and flashed SYSTEMLESS DevBase v1.11 over it -> no change

Only thing which I didn't try was repeating all of these steps but with wipe of data partition (too much effort so far ;)).

So any advice would be appreciated.

But now the most important thing: I wish all of You a Very Happy New Year!!!
[Galaxy S 5 Android Development (Snapdragon)] It_ler:
Hmm ... why do you need systemless DevBase when rooted with SuperSU?

Anyway, I would try to flash the DevBase rom with noroot, then flash SuperSU in recovery.

BTW ... I wish you also a very happy, healthy and successful New Year 2018 !!!
[Galaxy S 5 Android Development (Snapdragon)] Many40:
Thanks for replying.

Why do I need the systemless devbase? Just for the purpose it was designed for -> to be able to customize the rom systemlessly (regardless from root solution).

I have already done this as described in my post :(
[Galaxy S 5 Android Development (Snapdragon)] _alexndr:
In case of changing root solution it is necessary to re-install SYSTEMLESS DevBase (AFTER SuperSU), because we need to place it's "core" to other place (/su/su.d instead of /magisk/.core/post-fs-data.d)

EDIT: [MENTION=2174044]Many40[/MENTION], you can also just re-flash the whole ROM (renamed to "G900FXXS1CQI6_DevBase_v4.3_supersu.zip") and all necessary changes will be performed automatically, then boot the system at least once before you flash suhide

BTW: Then newest version is v1.12 :cool: (although - no changes with SuperSU, minor changes with Magisk)

https://xdaforums.com/showthread.php?p=75025805

That still makes sense because we do not touch the original files in /system

One stumble when modifying and in most cases we just simply need delete the modified file from /data/devbase/system/.. to revert changes to original state :cool:

___________________

[Happy New Year :) ]
[Galaxy S 5 Android Development (Snapdragon)] michi01:
Hi all,

after a long time using Android 5(BOH4), I tried to install Android 6.

I decided to go to CQI6.

I used the well working path (for BOH4 and previous):

Installed Android 4(ANE2)->Towelroot->SuperUser->MobileOdinPro->flashing pre-rooted image.

All worked well, except that I am not able to install the CQI6 Bootloader!?

With the old bootloader, the CQI6 kernel will not start...naturally :(

I tried a CQI4 bootloader...same result...Odin flashing seems to work well, but the bootloader stayed at the initial one (ANE2).

To verify the install path I installed BOH4 again...everything is fine that way.

It seems, that the S5 rejects flashing the Bootloader, when a CQI6 kernel image is installed???!

Even an BOH4 bootloader is not flashable!? I also tried the ODIN "bootloader" hook...no success.

Do I miss something with Marshmallow on S5?

For the moment I am staying with BOH, but I am curious what the reason for this problem is.

Any help is welcome.

...have fun...

Michi
[Galaxy S 5 Android Development (Snapdragon)] Many40:
Hi,

Flashing bootloader is tricky - you might need to try it a few times to take effect.

Did you try this?

- flash devbase in recovery but don't boot into system

- remove the battery for some minutes

- put the battery back and go to download mode

- flash with odin bootloader and modem but don't reboot to system yet -> untick autoreboot option in odin (some don't do that but I do :))

- after flashing pull out the battery again for some minutes

- put in the battery and reboot to system
[Galaxy S 5 Android Development (Snapdragon)] michi01:
Hi,

thx for your quick response.

What makes me wonder, is that flashing the CQI6/BOH4 bootloader flashing felt several tries while the CQI6 main image was loaded, but flashing the BOH4 bootloader while BOH4 main image was loaded worked at the first attempt without any problem!? Even in the past, I had never problems updating the bootloader in several attempts!?

Is it possible to update to [CQI6] directly from rooted [BOH4] with MobileOdinPro? Would save some time to skip the Android 4 - Towel Root - SU - Odin round.

...have fun...

Michi
[Galaxy S 5 Android Development (Snapdragon)] Many40:
Thanks but as I wrote in my previous post - I did it exactly but it didn't help.

I have however one question: in order to flash properly suhide-light it was required to change SuperSU mode into SBIN mode what as far as I know (if not mistaken) changes SuperSU files location to /sbin.

Does it have any influence on your Systemless davbase?

OK but it will rather not help as suhide requires beta version of SuperSU (minimum ver 2.82 SR2) instead of stabale/official release (ver 2.82) what you implemented into the devbase.

Thanks anyway.
[Galaxy S 5 Android Development (Snapdragon)] DerCasi:
Noroot wasn't even starting. I managed to get alexndr 4.2 with Magisk to work. Probably I mixed the wrong BL an CP with 4.3.

I tried BL_G900FXXS1CQI6 with CP_G900FXXS1CQA9 and G900FXXS1CQI6_DevBase_v4.3 and received the described issues. Now I'm running BL_G900FXXS1CQD8 with CP_G900FXXS1CQAV and G900FXXS1CQD8_DevBase_v4.2 and have no problems so far.

Can my problems with 4.3 be related with wrong BL an CP selection?
[Galaxy S 5 Android Development (Snapdragon)] Many40:
1. It shouldn't be any problems with upgrading from LP to MM

2. 30 seconds might be too short - try at least 5 minutes

3. MobileOdinPro is the legacy app. I would recommend switch to FlashFire

4. On android 6.0.1 MM it is not possible to flash a custom rom with root and still keep Knox 0x0. Only possibiity to have this rom without tripping Knox is to flash it without root.
[Galaxy S 5 Android Development (Snapdragon)] It_ler:
Bootloader version must match to the ROM version to successfully boot into system.

Modem just needs to be from the same Android version (in this case Android 6.0.1). So you can keep the modem of v4.2 if you want.
[Galaxy S 5 Android Development (Snapdragon)] DerCasi:
I'll try next year ;)

Thanks for ur help, have a nice party tonight and a shiny happy new year.
[Galaxy S 5 Android Development (Snapdragon)] michi01:
Hmmmh...

I did a lot attempts to update the Bootloader while the Marshmallow kernel [CQ16] is installed, but the S5 refuses to load it.

Odin Status is o.k. [green], but revovery console and phone Info shows the original ANE bootloader.

While trying, I accidently knoxed the phone, so that I have not longer restrictions in directly flash the rooted Kernel :p

Doing that enabled booting even with the old bootloader pretty fast, but I don't understand why the boot loader is not flashable while the Marshmallow Kernel is loaded?!

Before I use the phone in that configuration, I would like to have it stable...and I want definitely understand what's going on!?

If someone has an idea...I would appreciate advice to fix that problem a lot.

Without solving that problem, I will flash back to Lollipop, which is in principle okay for me, but I am really interested in understanding the cause of the problem!

...have fun...

Michi
[Galaxy S 5 Android Development (Snapdragon)] Many40:
By the way, I am not sure if I understood well what you exactly tried - have you tried to upgrade from Lolliopop to MM just by flashing via odin complete stock MM firmware?
[Galaxy S 5 Android Development (Snapdragon)] michi01:
No, i have flashed Alexanders rooted ROM...I like to be a titanium-root-user.

---------- Post added at 06:32 PM ---------- Previous post was at 06:29 PM ----------

Kitkat->Towelroot->SU->MobileOdinPro->Alexander ROM.

That worked fine in the past for upgrading from Kitkat to Lollipop.

For the Kernel it works fine for Lollipop to Marshmallow and if I had'nt missed the disable Knox hook in SU even the Knox bit would be untouched :) :) :)

...but what ever I do, it is not possible to update bootloader and modem!?

I have no idea what the reason is!? Obviously my knowledge is no sufficient...maybe some of the forum's experts can help me!?

...have fun and a happy new year...

Michi

P.S.: I know, that Chainfire is the successor of MobileOdinPro, but I didn't manage to get it working a year ago...so I stayed with MobileOdinPro, which did the job perfectly in the past.
[Galaxy S 5 Android Development (Snapdragon)] Many40:
When your KNOX is already triggered just do what I recommend to you:

Flash pure stock Samsung MM 6.0.1 firmware via PC odin (with battery replacement just in case) and then you can do whatever you want - rooting with SuperSU or Magisk, flashing TWRP recovery and any custom rom including _alexndr's rom of course.

Happy New Year !!! :)
[Galaxy S 5 Android Development (Snapdragon)] michi01:
I tried that , but I always ran into the bootloader/modem flash problem. MM with Alexandr's CQI6 ROM suppresses, however, successful bootloader and modem update on my S5!?.

Maybe something with my S5 is not "normal", it is a used and refurbished device...I will check the origin, when I have reverted it to Lollipop :angel:

Don't ask me why it behaves that strange!?????

My solution is pretty simple: I go back to Lollipop...there is nothing I will miss.

The excursion to Marshmallow was just induced by curiosity, which is now satisfied.

Thx for your support.

Michi

Update: I don't no why, but the bootloader is not updateable longer...neither LP nor MM...that's strange. Fortunately it boots flawless into my LP->BOH4. If someone knows the cause and/or the cure for this problem, I would appreciate that a lot!?

Update-Update: Uh-Oh...something is really wrong with that S5: After rebooting all installed Apps are terminated with "Unfortunately *** has stopped". Something is completely wrong. The recovery menu shows the "Android figure with a exclamation mark above the open service door. I think I have, however, to solve the boot loader problem first!?
[Galaxy S 5 Android Development (Snapdragon)] _alexndr:
DevBase contains the newest SuperSU 2.82 BETA (SR5), just FYI ;)
[Galaxy S 5 Android Development (Snapdragon)] durukanx:
Happy New Years to all, and wishing you a great 2018. Enjoy
[Galaxy S 5 Android Development (Snapdragon)] HJarausch:
Hi,

does anybody know if there are patches for the Meltdown and Spectre ARM-CPU bugs?
[Galaxy S 5 Android Development (Snapdragon)] It_ler:
You should check Magisk v15.2 ;)

Passes SafetyNet checks with uninstalled Xposed framework.
[Galaxy S 5 Android Development (Snapdragon)] ginzo:
I confirm it, thank you for the advice!

Inviato dal mio SM-G900F utilizzando Tapatalk
[Galaxy S 5 Android Development (Snapdragon)] toorzilla_:
Thank you MysteryIII :)

With a few extra steps I got IT To work, starting from CQI6_noroot + Boeffla Kernel + SystemLess DevBase v1.11 + Magisk v14.3 + Xposed 87.3 by topjohnwu :

In Recovery :

Backup :p

flashed latest Xposed Uninstaller (not doing that made my phone able to find Xposed but unable to load it...)

flashed latest Magisk Uninstaller

flashed Boeffla kernel again

flashed Magisk v15.2

flashed devbase v1.13

Booted phone

Installed MagiskManager-v5.5.3.apk

Installed XposedInstaller_3.1.4_Magisk.apk

Installed Xposed 89.0 SDK 23 by topjohnwu from into Magisk Manager (as you did : modules > add module (+) > file...)

Rebooted phone

Enabled Xposed modules

Rebooted phone

Now running CQI6_noroot + Boeffla Kernel + SystemLess DevBase v1.13 + Magisk v15.2 + Xposed 89.0... Sounds stable :)

V/
[Galaxy S 5 Android Development (Snapdragon)] It_ler:
I could also get systemless Xposed v87.3 working with Magisk v15.2 - Private mode still working.

Then I installed Xposed v89.0 in Magisk Manager, rebooted and Xposed is working fine ... but Private mode is broken again.

Strange.

EDIT:

Back on systemless Xposed v87.3 and private mode is working again.

I prefer running on Magisk v15.2 with Xposed v87.3 and working private mode. :cool:
[Galaxy S 5 Android Development (Snapdragon)] MysteryIII:
I will also stick with 87.3. Newer versions are missing something for compatibility and who can say under which circumstances it will happen and if you know Xposed is the cause.

Is it now possible to set Magisk to core function and SN passing even after installing Xposed? Right now I'm very busy and I don't want to test new Magisk as I don't have time for a fixing procedure, so I will check it the next free weekend myself.
[Galaxy S 5 Android Development (Snapdragon)] Many40:
Hi,

I was playing a little bit more with SuperSU + suhide in order to check why/when Systemless devbase gets broken for me and did what you recommended:

1. flashed latest DevBase 4.3 renamed to "G900FXXS1CQI6_DevBase_v4.3_supersu.zip with factory reset - everything OK (systemless modifications in /data/devbase/system/framework still working)

2. changed SuperSU mode to SBIN (according to Chainfire suhide guide) by executing this command in adb shell:

echo "BINDSBIN=true">/data/.supersu

being in Recovery and then just after refleshed SuperSU 2.82 SR5 -> this operation forced replacing SuperSU location from /su directory to /sbin

what caused finally systemless modifications stop working

.

Could you please have a look at this and recommend a workaround if possible?

Currently it is not possible to have at the same time properly working systemless devbase and SuperSU with suhide which passes successfully SafetyNet.

Thanks

Edit: In the meantime going back to Devbase4.3 noroot + Magisk 15.2 + Systemless Devbase 1.13 :)

Edit2: ver. 1.14 of course ;)
[Galaxy S 5 Android Development (Snapdragon)] It_ler:
I just tested it ... for you. ;)

First screenshot is with Xposed active.

Second is with Xposed installed but deactivated.

Both with Magisk v15.2 and systems Xposed v87.3.
[Galaxy S 5 Android Development (Snapdragon)] Schokofreak:
I found a solution,how to use Snapchat with root without Magisk and Xposed.First Install the newest version from Alexndr(4.3).Then download and install Root Switch.After you installed Root switch and Snapchat,open Root switch and turn root off.Open Snapchat and login or register normally.U will see that it will work,like by me.Then you can turn Root on with Root switch.Thats it.
[Galaxy S 5 Android Development (Snapdragon)] MysteryIII:
Thanks that's exactly what I was looking for.

I really appreciate your afford!

---------- Post added at 21:50 ---------- Previous post was at 21:44 ----------

Do you still have this problem? If so check your IMEI:

*#06#
[Galaxy S 5 Android Development (Snapdragon)] Many40:
Hi,

Have you noticed that today Magisk 15.2 stopped passing SafetyNet ? At least for me. Maybe Google changed something :confused:

Not big deal but interesting ....

Edit: strange, after reboot started passing again :eek:

Edit2: after 1 min from the previous check it stopped again. Don't understand that.

Edit3: now I understand more -> being on a custom kernel I disabled Android logger (logcat) support what caused MagiskHide not working properly and as the consequence broke SafetyNet passing.

Now logcat feature is back ON :)
[Galaxy S 5 Android Development (Snapdragon)] _alexndr:
I'm sorry, I just totally missed this BINDSBIN mode (probably I didn't look at the SuperSU's changelog carefully enough)

I just introduced support for BINDSBIN mode to SYSTEMLESS DevBase v1.15 in case of SuperSU as root solution:

https://xdaforums.com/showthread.php?p=75141263
[Galaxy S 5 Android Development (Snapdragon)] Many40:
Thanks a lot. You are the man :)

But now I have a problem being on properly working Devbase+Magisk with the Supersu alternative ;)
[Galaxy S 5 Android Development (Snapdragon)] _alexndr:
MODs section has been updated as previous MOD(s) version(s) may incorrectly install MOD to /system in some modern systemless modes :cool:
[Galaxy S 5 Android Development (Snapdragon)] hardalexport:
Please throw off the link to Magisk v15.2 and systems Xposed v87.3.

My goal,that would Magisk worked with Xposed on the ROM https://xdaforums.com/galaxy-s5/dev...-multi-csc-t2813628/post74646517#post74646517
[Galaxy S 5 Android Development (Snapdragon)] Many40:
Hi,

Come on, just google Magisk (on the Magik beta xda thread you will find ver 15.2. The latest stable version on the main thread is already 15.3 - I don't know if it works well with Xposed 87.3 or not) and google Xposed systemless and chose on xda thread ver 87.3 sdk 23. Easy. If you still can't find it, I will give you the links.
[Galaxy S 5 Android Development (Snapdragon)] curiousde2002:
My S5 is on CQI4 with the default Magisk 14.2, but the latest Magisk Manager 5.5.4, and systemless Xposed 87.3 by topjohnwu.

I'd like to upgrade now to the latest Magisk 15.3.

Can I do this in the Magisk Manager or do I have to uninstall Magisk first and then flash Magisk 15.3 zip via TWRP?

Thanks alot for your help!
[Galaxy S 5 Android Development (Snapdragon)] Many40:
Just flash Magisk 15.3 over 14.2 from recovery but after that you need to flash Systemless Devbase (latest ver is 1.15) from this thread: https://xdaforums.com/s7-edge/development/samsung-systemless-devbase-encryption-t3517178
[Galaxy S 5 Android Development (Snapdragon)] It_ler:
I have done it exactly like this ... worked fine :good:
[Galaxy S 5 Android Development (Snapdragon)] It_ler:
Magisk v15.3 works fine on my phone with Xposed v87.3.

No issues so far - even private mode still works.
[Galaxy S 5 Android Development (Snapdragon)] curiousde2002:
Thank you very much for your really quick replies!

If I want to upgrade to CIQ6, what would be the correct sequence?

Maybe like this?

Flashing via TWRP:

G900FXXS1CQI6_DevBase_v4.3_noroot.zip + Magisk v15.3 + SystemLess DevBase v1.15

Boot into download mode and connect to PC to flash bootloader and modem via PC Odin.

Boot into system and install Xposed 87.3 (maybe 89.1) by topjohnwu via Magisk Manager.

Done hopefully:fingers-crossed:
[Galaxy S 5 Android Development (Snapdragon)] hardalexport:
It_ler

How do I download Magisk v15.3 and Xposed v87.3?I can not find these links in any way ...
[Galaxy S 5 Android Development (Snapdragon)] Many40:
I am disappointed. Belived that you can manage .....

Here you have them:

1. Magisk 15.3 (link in post no 1):

https://xdaforums.com/apps/magisk/o...systemless-t3473445/post68966755#post68966755

2. Xposed 87.3 sdk23 (link in post no 1):

https://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268
[Galaxy S 5 Android Development (Snapdragon)] hardalexport:
Many40

Thank you, I hope I succeed...

P.S.And where I can download the installer xposed .apk?Since just one flash archive is not enough ...To me

need a file with the extension .apk?
[Galaxy S 5 Android Development (Snapdragon)] Many40:
Better look into my 2nd link (XposedInstaller is a key word)

Edit: Sorry I misunderstood you ... post updated :)
[Galaxy S 5 Android Development (Snapdragon)] hardalexport:
Okey!

I installed the Rom "G900FXXS1CQI6_DevBase_v4.3_noroot.zip".

What are my next steps:

1,2,3 etc.

or

I installed the Rom G900FXXS1CQI6_DevBase_v4.3.zip

(default) - install the ROM with Magisk & MagiskSU as root solution

(just flash ZIP file "as it is")

Magisk is already installed and is as root solution.

How do i install Xposed and what version,to make it work module for Magisk?

That is the question.

Help, I will be very grateful to you:)