Database Develop

How to Disable Xposed on Lollipop when stuck in Bootloop

I have xposed running on my Nexus 5 lollipop 5.0.1.
After downloading and enabling a couple modules my phone is now stuck in a bootloop.
I tried clearing dalvik and cache it didn't help.
Is it possible to disable xposed from recovery?
EDIT: Solved.
Boot into Recovery (Power + Volume Down)
TWRP > Advanced > Terminal command
Create a file /data/data/de.robv.android.xposed.installer/conf/disabled, which causes Xposed to be bypassed:
Code:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
Click to expand...
Click to collapse

Boot into Recovery (Power + Volume Down)
TWRP > Advanced > Terminal command
Create a file /data/xposed/disabled, which causes Xposed to be bypassed as well:
Code:
touch /data/xposed/disabled
Click to expand...
Click to collapse
Didn't work. Still stuck in bootloop.

bseos said:
Didn't work. Still stuck in bootloop.
Click to expand...
Click to collapse
what modules you have activated?
or
mv /system/lib/*.*.orig /system/lib/*.*
mv /system/bin/*.orig /system/bin/*

opssemnik said:
what modules you have activated?
Click to expand...
Click to collapse
It was between two modules. Can't remember the first one but the last one was XInstaller.
Anyway, got it solved using the below method:
Boot into Recovery (Power + Volume Down)
TWRP > Advanced > Terminal command
Create a file /data/data/de.robv.android.xposed.installer/conf/disabled, which causes Xposed to be bypassed as well:
Code:
touch /data/data/de.robv.android.xposed.installer/conf/disabled

very good

bseos said:
It was between two modules. Can't remember the first one but the last one was XInstaller.
Anyway, got it solved using the below method:
Boot into Recovery (Power + Volume Down)
TWRP > Advanced > Terminal command
Create a file /data/data/de.robv.android.xposed.installer/conf/disabled, which causes Xposed to be bypassed as well:
Code:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
Click to expand...
Click to collapse
XInstaller seems to be causing a few issues, and I don't think its the app itself but the apps it allows you to install instead. I had the same issue after installing xInstaller. But now that you figured this out maybe I can try a few other apps out like xstana which for somereason refuses to install on lollipop devices...

.Ryker said:
XInstaller seems to be causing a few issues, and I don't think its the app itself but the apps it allows you to install instead. I had the same issue after installing xInstaller. But now that you figured this out maybe I can try a few other apps out like xstana which for somereason refuses to install on lollipop devices...
Click to expand...
Click to collapse
After disabling it I flashed the new xposed-arm-20150308.zip and installed XposedInstaller_3.0-alpha2.apk (I was on alpha1 previously)
Re-enabled xposed (deleted "disabled" file) and all is working fine now.

This thread definitely either needs to be made a sticky, or the contents needs to be in one of the already made sticky threads IMHO
Cheers
//edit
I tried this out on my phone to test (my xposed stuff is working just fine) but it doesn't seem to have disabled xposed at all?
Ex, app settings still functions (set my play store to be at 480 DPI and it's still opening in 480 DPI as it should...)
I made the necessary file you said with fx file manager, not through TWRP recovery though... I don't think it should make a difference though how I made the file, just that it's there.
Maybe my permissions on the file are messed up, I just thought of that..
//edit 2
Yup my perms were messed up, xposed is now disabled for me. Cheers for the info, now I know what to do when some shady looking module backfires on me lol

Thank you so much!!! This worked perfectly on Sprint LG G3 using Candy5 ROM!! Saved me!!

Just to report that the method failed on a Samsung Galaxy S6 Edge (SM-G925F).
I created succesfully the disabled file, but I was still having bootloops.
So I thought I forgot to set the file to 755, but then TWRP told me:
Code:
Updating partition details...
...done
E: Resource (font)-(fixes) failed to load
Kernel does not have support for reading SELinux contexts.
MTP Enabled
Now I hope to fix everything by reflashing the firmware again...

After successfully disabling xposed in order to get the device to boot, how do we reenable it? Because after uninstalling the module which caused the problem the framework is "not active". A reboot did not work.

Nokiacrazi said:
After successfully disabling xposed in order to get the device to boot, how do we reenable it? Because after uninstalling the module which caused the problem the framework is "not active". A reboot did not work.
Click to expand...
Click to collapse
Delete the "disabled" file in the folder op showed

jkyoho said:
Delete the "disabled" file in the folder op showed
Click to expand...
Click to collapse
Silly question but how can I delete it? I tried locating it using HTC file manager and es file explorer but cannot locate it.
Is there a command I can use using terminal emulator or something?
Thanks
Sent from my HTC One_M8 using XDA Free mobile app

Nokiacrazi said:
Silly question but how can I delete it? I tried locating it using HTC file manager and es file explorer but cannot locate it.
Is there a command I can use using terminal emulator or something?
Thanks
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
You need you use Root explorer or Es file explorer that supported Root and locate to /data/data/de.robv.android.xposed.installer/conf
Method 2:
You can even delete the "disabled" file in recovery by using file management, if you are using TWRP. Same as previous method, just locate to /data/data/de.robv.android.xposed.installer/conf

jkyoho said:
You need you use Root explorer or Es file explorer that supported Root and locate to /data/data/de.robv.android.xposed.installer/conf
Method 2:
You can even delete the "disabled" file in recovery by using file management, if you are using TWRP. Same as previous method, just locate to /data/data/de.robv.android.xposed.installer/conf
Click to expand...
Click to collapse
Thanks, method 2 worked a treat.
For some reason, even though I have root access, it wasn't showing in either root explorer or es file explorer, however, when looking through TWRP file management was all there.

jkyoho said:
Delete the "disabled" file in the folder op showed
Click to expand...
Click to collapse
can you please explain the process.
i entered the twrp and advanced and terminal command and went through the shown path yet i didnt see the file "disabled"
he has said to create a file; how could i create a file??
please explain the process...

cybercop007 said:
can you please explain the process.
i entered the twrp and advanced and terminal command and went through the shown path yet i didnt see the file "disabled"
he has said to create a file; how could i create a file??
please explain the process...
Click to expand...
Click to collapse
If you can't normally boot to system, boot to recovery(twrp or some other custom recovery which has file management function)
Try copy a small file like host or something, paste it the that /data/data/dev.*****installer/conf folder and rename it "disabled".

flashable zip´s

starbase64 said:
flashable zip´s
Click to expand...
Click to collapse
these will be very good to have! thank you!

starbase64 said:
flashable zip´s
Click to expand...
Click to collapse
Thank you!!!

How to set /system partition into rw?

can someone make me a flashable zip for making my /system partition mounted into RW on boot?
Newbie here Will appreciate every help thanks

ChanSilvers said:
can someone make me a flashable zip for making my /system partition mounted into RW on boot?
Newbie here Will appreciate every help thanks
Click to expand...
Click to collapse
You need to have root and any terminal installed.
Start terminal and type
Code:
su
mount -o rw,remount /system
It will be remounted RW without any zip flashing and rebooting, realtime.

fehhner said:
You need to have root and any terminal installed.
Start terminal and type
Code:
su
mount -o rw,remount /system
It will be remounted RW without any zip flashing and rebooting, realtime.
Click to expand...
Click to collapse
thanks man! ? I tried that but my phone reboots after i entered the command and my phone is rooted ?

Sorry for the dig up but i am also interrested in this.
I am using an app (NFC Card Emularo) which requires access to /vendor/etc/libnfc-nxp.conf but cannot access it -> the partition is reported to be "read only" by the app. I was able to use the mount command but i am not sure it changes anything since the partition doesnt seem to be writable anyway.
My rig : OnePlus 3T / Oreo (Resurrection Remix OS) / Magisk 16 (also tried 16.2)

Error on remount /system
/system permission can't get full permission

Hi I am using the same app and facing the same problem you have. I have a moto Z 2016 and using the app well, on moto Z2 ,the same problem as you are having. I tried to create file in the dest folder where the app need to modifiy file and success. Still digging into that.

Has anyone been able to solve this? I too use NFC Card Emulator and it's been working fine for a while but then I got the same problem. I don't know what caused it, either an update to the app, LineageOS, Magisk or TWRP. I'm using a OnePlus 5T.

Since Magisk is mounting it's systemless mask over /system and /vendor, directly modifying/mounting these as rw can be an issue...
If you're not using any Magisk modules, you should be able to make it work by just enabling Core Only Mode in the Manager settings.
Otherwise, I would try by taking whatever file it is that the app is trying to modify and make a Magisk module out of it. This way the app should have full write access to the file, and you'll have the benefit of keeping your system untouched.

Didgeridoohan said:
Since Magisk is mounting it's systemless mask over /system and /vendor, directly modifying/mounting these as rw can be an issue...
If you're not using any Magisk modules, you should be able to make it work by just enabling Core Only Mode in the Manager settings.
Otherwise, I would try by taking whatever file it is that the app is trying to modify and make a Magisk module out of it. This way the app should have full write access to the file, and you'll have the benefit of keeping your system untouched.
Click to expand...
Click to collapse
There is an option to generate a Magisk module from the app and that's actually what I used until things broke. After some testing, going back to the March 5 build of LineageOS 15.1 and getting version 3.0.9 of NFC emulator from Aptoide made it work again, but any version 3.1.0 or up doesn't and 3.0.9 does not work on latest LineageOS (March 26 because f that April fools crap). I also tried all the latest LineageOS/TWRP/NFC Emulator on my old Nexus 6P and there, everything works as expected.
So what I get from this is that the fault is either in LineageOS or the app and it's device specific.

An update to this. LineageOS version does not matter as I was able to get NFC Card Emulator version 3.0.9 running on the latest LineageOS. If you download version 3.0.9 from Aptoide it will work once and then stop working, later versions won't work at all. So the best current solution is to use version 3.0.9 of the app and on each reboot after the first install, clear data for the app and it will work again.

Limero said:
An update to this. LineageOS version does not matter as I was able to get NFC Card Emulator version 3.0.9 running on the latest LineageOS. If you download version 3.0.9 from Aptoide it will work once and then stop working, later versions won't work at all. So the best current solution is to use version 3.0.9 of the app and on each reboot after the first install, clear data for the app and it will work again.
Click to expand...
Click to collapse
I can confirm this.
I was having problems with the lastest version of NFC Card Emulator, so I downloaded and installed version 3.0.9 and everything works fine.
Thanks for the tip!

same problems.
I have xiaomi with miui10 beta and magisk with a module installed.
The nfc say to me that the vendor partition is read only and I must reboot the boot everytime

Aight! I think I've found a solution!
DAVIZINHO said:
same problems.
I have xiaomi with miui10 beta and magisk with a module installed.
The nfc say to me that the vendor partition is read only and I must reboot the boot everytime
Click to expand...
Click to collapse
I'm using MI6 with all in one magisk module enabling camera2 api and some other stuff.
Today morning I f**up my phone trying to solve this problem and found a solution, by accident.
Here it is:
Don't install magisk module mentioned above

szaman8666 said:
I'm using MI6 with all in one magisk module enabling camera2 api and some other stuff.
Today morning I f**up my phone trying to solve this problem and found a solution, by accident.
Here it is:
Don't install magisk module mentioned above
Click to expand...
Click to collapse
The problem in my case is that i need the module "magiskhide props config" for pass the safety check.
If i uninstall this module, maybe not works?
I dont know if i can uninstall the module and work, i will try

DAVIZINHO said:
The problem in my case is that i need the module "magiskhide props config" for pass the safety check.
If i uninstall this module, maybe not works?
I dont know if i can uninstall the module and work, i will try
Click to expand...
Click to collapse
Checked the module You've mentioned, Nfc Card Emulator works fine but it may depend on Miui ROM, mine is 8.5.8 beta.

szaman8666 said:
Checked the module You've mentioned, Nfc Card Emulator works fine but it may depend on Miui ROM, mine is 8.5.8 beta.
Click to expand...
Click to collapse
I need this module, if I uninstall not works the safetynet check.
And with this module, nfc card emulator give me the error I use miui 10 beta

Didgeridoohan said:
Since Magisk is mounting it's systemless mask over /system and /vendor, directly modifying/mounting these as rw can be an issue...
If you're not using any Magisk modules, you should be able to make it work by just enabling Core Only Mode in the Manager settings.
Otherwise, I would try by taking whatever file it is that the app is trying to modify and make a Magisk module out of it. This way the app should have full write access to the file, and you'll have the benefit of keeping your system untouched.
Click to expand...
Click to collapse
In theory, if I temporarily disable all of my modules and enable Core Only Mode, would I be able to access the system as RW?

rodken said:
In theory, if I temporarily disable all of my modules and enable Core Only Mode, would I be able to access the system as RW?
Click to expand...
Click to collapse
That is a two and a half year old post you're quoting. A lot have happened in that time...
Core only mode is being removed from Magisk and there are plenty of devices that have permanently ro partitions.
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_edit_system_files
So the answer to your question would be a definite maybe.

Didgeridoohan said:
That is a two and a half year old post you're quoting. A lot have happened in that time...
Core only mode is being removed from Magisk and there are plenty of devices that have permanently ro partitions.
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_edit_system_files
So the answer to your question would be a definite maybe.
Click to expand...
Click to collapse
im on android 10 DirtyUnicorns and i want to completely replace the media folder with my own mod. how can i do this? im not able to do it on my pixel 3 yet i just did it on my pixel 2 xl running the same ROM.

Hola yo lo único que quiero es montar sistema como lecturas escritura y ya como puedo hacer android 8

Magisk mounting RO?

I am having an issue where Magisk seems to be mounting itself as read only, this prevents installing modules via Magisk Manager, but also prevents the use of modules such as Terminal Emulator App Debloater/Systemizer. I've attached screenshots of the issue and device/ROM info.
Also, here is my mounts file

ryaniskira said:
I am having an issue where Magisk seems to be mounting itself as read only[/URL]
Click to expand...
Click to collapse
This was reported also by users of Moto Z Play Nougat where the f2fs issue was fixed (since patch March 2017). Seems the fix somehow makes mount points created from /data which is stored on f2fs readonly.
Which format does your data partition use? Can you attach a catlog logfile of the initialization of Magisk?

tag68 said:
This was reported also by users of Moto Z Play Nougat where the f2fs issue was fixed (since patch March 2017). Seems the fix somehow makes mount points created from /data which is stored on f2fs readonly.
Which format does your data partition use? Can you attach a catlog logfile of the initialization of Magisk?
Click to expand...
Click to collapse
Data partition is ext4, Log

ryaniskira said:
I am having an issue where Magisk seems to be mounting itself as read only, this prevents installing modules via Magisk Manager, but also prevents the use of modules such as Terminal Emulator App Debloater/Systemizer. I've attached screenshots of the issue and device/ROM info.
Also, here is my mounts file
Click to expand...
Click to collapse
I've seen this solved other times by switching to a different kernel. Worth a shot...

Didgeridoohan said:
I've seen this solved other times by switching to a different kernel. Worth a shot...
Click to expand...
Click to collapse
Reflashed the ROM without the kernel, same issue.
Sent from my Nexus 6P using XDA Labs

Was this ever resolved?
I have a Samsung Tab A, rooted, with Magisk, and I can't edit a system file because file system is RO. And, I can't figure out how to make it RW; the normal advice doesn't work because of mods that Magisk makes to the file system.
If I uninstall Magisk my device will no longer be rooted, correct? (Yeah, I am new at this.)

fritz.barnes said:
Was this ever resolved?
I have a Samsung Tab A, rooted, with Magisk, and I can't edit a system file because file system is RO. And, I can't figure out how to make it RW; the normal advice doesn't work because of mods that Magisk makes to the file system.
If I uninstall Magisk my device will no longer be rooted, correct? (Yeah, I am new at this.)
Click to expand...
Click to collapse
Go to "/sbin/.magisk/mirror/system_root/" (or maybe "/sbin/.magisk/mirror/system/"), it's RW here.
INFO: If you use a file manager app and you don't see the ".magisk" folder, you need to enable "Show hidden files" option (in "Folder options").

[MOD]: Sqlite3 (v3.8.11.1) binary.

Hello everyone
Well... Not much to say.
I've made that very simple module for my personal use and just sharing it with the community in case anyone needs it.
What it does it really simple.
It installs (or replaces) sqlite3 binary in /system/bin to be used by any app or from terminal.
It's for ARM7 only.
Have fun
Credits: @topjohnwu for the template and @tech128 for the binary used.

Thank you for your effort... Do you have binary of sqlite of 64bit?

lssong99 said:
Thank you for your effort... Do you have binary of sqlite of 64bit?
Click to expand...
Click to collapse
I'm currently on G5 which is 64bit and binary works just fine.

Yes, it will work. However my situation is a bit complex that I call sqlite from Tasker and there is a bug in Tasker's that Tasker will invoke 64 bit libraries and throw error even if sqlite is 32 bit.
There is a work around but a bit complex so I am searching for 64 bit binary...

Sorry but what is SQLite

kwanthenewbie said:
Sorry but what i SQLite
Click to expand...
Click to collapse
You don't need it probably xD
It's the "program" to manipulate sqlite databases.

lssong99 said:
Yes, it will work. However my situation is a bit complex that I call sqlite from Tasker and there is a bug in Tasker's that Tasker will invoke 64 bit libraries and throw error even if sqlite is 32 bit.
There is a work around but a bit complex so I am searching for 64 bit binary...
Click to expand...
Click to collapse
https://github.com/stockrt/sqlite3-android
Build one by yourself. I guess you need arm64-v8a ?

DenyDarko said:
I'm currently on G5 which is 64bit and binary works just fine.
Click to expand...
Click to collapse
DenyDarko said:
https://github.com/stockrt/sqlite3-android
Build one by yourself. I guess you need arm64-v8a ?
Click to expand...
Click to collapse
Haha! Thanks.... Actually I had been trying very hard to resist the urge to build one myself (too lazy....). Maybe I should starting setup the tool train now....
Anyway thanks!

lssong99 said:
Haha! Thanks.... Actually I had been trying very hard to resist the urge to build one myself (too lazy....). Maybe I should starting setup the tool train now....
Anyway thanks!
Click to expand...
Click to collapse
It's not that hard and it's fun. Plus this git contains a customised sqlite for android.
It's not like building a kernel or smth. Give it a try xD

Hi @DenyDarko,
Please, can you update your module? It doesn't install with last version of Magisk. Futhermore, it will be interesting to include all binaries: sqlite3.arm; sqlite3.arm64; sqlite3.x64; etc. and add a symlink for the run architecture to "sqlite3". And last, publish it in the official repository.
Thank you!

manos78 said:
Hi @DenyDarko,
Please, can you update your module? It doesn't install with last version of Magisk. Futhermore, it will be interesting to include all binaries: sqlite3.arm; sqlite3.arm64; sqlite3.x64; etc. and add a symlink for the run architecture to "sqlite3". And last, publish it in the official repository.
Thank you!
Click to expand...
Click to collapse
@ianmacd added an updated version to the official repo already

DenyDarko said:
@ianmacd added an updated version to the official repo already
Click to expand...
Click to collapse
Ha. I didn't know there was already an SQLite module. I checked the official Magisk repo and didn't find one, so I made one for my own use and submitted it so that others could hopefully benefit from the work.

ianmacd said:
Ha. I didn't know there was already an SQLite module. I checked the official Magisk repo and didn't find one, so I made one for my own use and submitted it so that others could hopefully benefit from the work.
Click to expand...
Click to collapse
I even use yours now myself xD

@DenyDarko
Can you somehow check if this sqlite3 works ?

ianmacd said:
Ha. I didn't know there was already an SQLite module. I checked the official Magisk repo and didn't find one, so I made one for my own use and submitted it so that others could hopefully benefit from the work.
Click to expand...
Click to collapse
Hi @ianmacd,
I installed your Magisk module. However, I found a trouble: when enabling your module, the SafetyNet check never completes or indicates "the response is invalid".
So, please verify or review your module. Only disabling it the SafetyNet continues working well.
Or almost, put this info in the description, because your module is now in the official repository.
Regards.

manos78 said:
Hi @ianmacd,
I installed your Magisk module. However, I found a trouble: when enabling your module, the SafetyNet check never completes or indicates "the response is invalid".
So, please verify or review your module. Only disabling it the SafetyNet continues working well.
Or almost, put this info in the description, because your module is now in the official repository.
Regards.
Click to expand...
Click to collapse
The issue might be that the module mounts the binary to /system/xbin, and that your device doesn't have a xbin folder by default. This has been known to cause issues, and seem to be even more prevalent on recent Magisk releases. Try changing the modules xbin folder to bin and reboot, to see if it makes any difference.
@ianmacd It's a good idea to look for the existence of xbin at installation and use bin instead if it doesn't exist.

Didgeridoohan said:
The issue might be that the module mounts the binary to /system/xbin, and that your device doesn't have a xbin folder by default. This has been known to cause issues, and seem to be even more prevalent on recent Magisk releases. Try changing the modules xbin folder to bin and reboot, to see if it makes any difference.
@ianmacd It's a good idea to look for the existence of xbin at installation and use bin instead if it doesn't exist.
Click to expand...
Click to collapse
Thanks for the tip, @Didgeridoohan.
I'll have to read up on the Magisk installation environment to ensure that I write the logic in a sane way. By that, I mean, for example, that I'm unsure whether I can just check for [ -d /system/xbin ], or whether I might get a false positive if some other module has erroneously faked the existence of this directory.

ianmacd said:
Thanks for the tip, @Didgeridoohan.
I'll have to read up on the Magisk installation environment to ensure that I write the logic in a sane way. By that, I mean, for example, that I'm unsure whether I can just check for [ -d /system/xbin ], or whether I might get a false positive if some other module has erroneously faked the existence of this directory.
Click to expand...
Click to collapse
Good point... Check for /sbin/.core/mirror/system/xbin. That's the untouched /system mirror.

ianmacd said:
Thanks for the tip, @Didgeridoohan.
I'll have to read up on the Magisk installation environment to ensure that I write the logic in a sane way. By that, I mean, for example, that I'm unsure whether I can just check for [ -d /system/xbin ], or whether I might get a false positive if some other module has erroneously faked the existence of this directory.
Click to expand...
Click to collapse
Alternately you can just use bin and forget about xbin. There's really no technical reason to use xbin unless you're installing alternate forms of existing commands.

jcmm11 said:
Alternately you can just use bin and forget about xbin. There's really no technical reason to use xbin unless you're installing alternate forms of existing commands.
Click to expand...
Click to collapse
That's actually also been known to cause issues on some systems. While investigating issues like this, a while back, I believe it was found that it was most compatible to use xbin if it exists and bin if it doesn't.

Gigantic X - I detected the Root Magisk

Hello.
This game (GIGANTIC X) Me detects the access root Magisk, the hidden through "Magisk Hide" and when I restart it again detects me again and does not work.
https://play.google.com/store/apps/details?id=com.ActionSquare.GiganticX

D-Mak said:
Hello.
This game (GIGANTIC X) Me detects the access root Magisk, the hidden through "Magisk Hide" and when I restart it again detects me again and does not work.
https://play.google.com/store/apps/details?id=com.ActionSquare.GiganticX
Click to expand...
Click to collapse
Have you tried the v19.0 Beta ?

lahceneamine said:
Have you tried the v19.0 Beta ?
Click to expand...
Click to collapse
I just tried the V19.0 and the same thing happens.

any root-using apps installed or magisk.zip still in storage?

D-Mak said:
I just tried the V19.0 and the same thing happens.
Click to expand...
Click to collapse
Do you pass SAFETYNET with v19.0 ? If not, there's something wrong in your config.

Oh... it's using Lockin Company's Liapp(https://liapp.lockincomp.com/ )...
It's not a problem like misconfig since it detects Magisk itself. Liapp updates frequently to apply new root (especially Magisk) detection methods, so it's hard to bypass it.
(Magisk 17.3+ bypasses 5.0.0, 18.2+ bypasses 5.0.1, but 5.0.2+ cannot be bypassed currently.)

same here.cantplay it on root device,well that sucks.Im not gonna sacrifice my magisk for this game,not worth it

I made a bypass script for it (and all other apps using Liapp and UDS detection method)!
Download it on https://github.com/Ingan121/UDSBypass/blob/master/udsbypass and run 'su -c sh /sdcard/Download/udsbypass com.ActionSquare.GiganticX/com.epicgames.ue4.GameActivity'. Make sure you added this app to MagiskHide.

Ingan121 said:
I made a bypass script for it (and all other apps using Liapp and UDS detection method)!
Download it on https://github.com/Ingan121/UDSBypass/blob/master/udsbypass and run 'su -c sh /sdcard/Download/udsbypass com.ActionSquare.GiganticX/com.epicgames.ue4.GameActivity'. Make sure you added this app to MagiskHide.
Click to expand...
Click to collapse
Thanks! How do i use this script? i tried in terminal but it keep saying no such file or directory

Predatorhaze said:
Thanks! How do i use this script? i tried in terminal but it keep saying no such file or directory
Click to expand...
Click to collapse
Did you download it in Download folder? Then it should be started by 'sh /sdcard/Download/udsbypass' (without quotes).
Also, you can copy it to /sbin, chmod 755, and then just run 'udsbypass'.

Ingan121 said:
Did you download it in Download folder? Then it should be started by 'sh /sdcard/Download/udsbypass' (without quotes).
Also, you can copy it to /sbin, chmod 755, and then just run 'udsbypass'.
Click to expand...
Click to collapse
I copied the text and made a text file saved .sh..or do I something wrong here

Predatorhaze said:
I copied the text and made a text file saved .sh..or do I something wrong here
Click to expand...
Click to collapse
sh /sdcard/path/to/udsbypass.sh

Ingan121 said:
sh /sdcard/path/to/udsbypass.sh
Click to expand...
Click to collapse
I am a noob with this,I don't get it.Cant get it to work.I think will uninstall magisk

Predatorhaze said:
I am a noob with this,I don't get it.Cant get it to work.I think will uninstall magisk
Click to expand...
Click to collapse
Termux can't be used for this.
Use other terminal app.

Ingan121 said:
Termux can't be used for this.
Use other terminal app.
Click to expand...
Click to collapse
It can be used if you adjust the script to check for /sbin in $PATH and then add it if it isn't already there.
Or adjust the script to use the absolute paths to the Magisk binary, but that is a lot less elegant and won't work if the paths change.

Ingan121 said:
Termux can't be used for this.
Use other terminal app.
Click to expand...
Click to collapse
well then i try material terminal.
by the way im running pie gsi.
How is the game btw? is it good? bored fast?

Predatorhaze said:
well then i try material terminal.
by the way im running pie gsi.
How is the game btw? is it good? bored fast?
Click to expand...
Click to collapse
I didn't play it, just deleted immediately after succeeding to bypass.

Alright.i really want to play this game but i cant get this bypass to work.Can someone explain more clear steps?

Ingan121 said:
Did you download it in Download folder? Then it should be started by 'sh /sdcard/Download/udsbypass' (without quotes).
Also, you can copy it to /sbin, chmod 755, and then just run 'udsbypass'.
Click to expand...
Click to collapse
I managed to run the script by putting the file in /sbin but the game is still detecting root

Ingan121 said:
I didn't play it, just deleted immediately after succeeding to bypass.
Click to expand...
Click to collapse
can u explain with a short video the game has official release yesterday