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
Related
Has anyone managed to install adaway on any official rom?
The program fails when trying to apply the hosts file.
Yes i have rooted the phone and yes i have granted permisions with supersu to adaway.
revery0 said:
Has anyone managed to install adaway on any official rom?
The program fails when trying to apply the hosts file.
Yes i have rooted the phone and yes i have granted permisions with supersu to adaway.
Click to expand...
Click to collapse
I had it many times. AdAway is working very wele. Maybe you have not full rooted phone. Use MyRoM it is full rotted and AdAway is preinstalled and many others additions.
Hey...
First step is normal root. If you are ready you have to delete the immutable.list on system. Then you can use adaway.
Booth ways need busybox! Install it before you try to delete immutable.
Make it with my tool - easy update and adjust (http://forum.xda-developers.com/asc...eandadjust-t2941186/post56774286#post56774286) or make it manuelly with your PC and ADB.
adb shell
su
mount -o rw,remount /system
cd system
chattr -R -i *
rm –f /system/set_immutable.list
lsattr (to see if it's still there)
On my device with stock Rom it works well!
Thank you, it works like a charm!!!
revery0 said:
Thank you, it works like a charm!!!
Click to expand...
Click to collapse
No problem...
Wich way you have choosed?
Your script, cause command prompt returned an error when trying to change attributes, the reason was that adb hadnt have su permissions and for some reason supersu didnt prompt me to grant them. But with your script supersu prompt me to give adb su permissions and so i did, after that it worked.
Strange dont you think?
revery0 said:
Your util, cause command prompt returned an error when trying to change attributes, the reason was that wasanted su permiadbwasntions and suidnt proe to give it permissions, but when I tried your script then I got the prompt from supersu and itsusupersudidntsupersu..
Sounds strange dont you think?
Click to expand...
Click to collapse
I dont understand you complete. But my batch is working for you, thats fine
Auto correction on swype keyboard sucks.... I edited the previous post
revery0 said:
Auto correction on swype keyboard sucks.... I edited the previous post
Click to expand...
Click to collapse
yeah it corrects way u dont want it .. just turn off auto and leave options to pick..
Has anyone got Link2SD to work on the R1 HD? It always seems to give the error: mount script cannot be created "mount:No such file or directory" when trying to create mount script. Any ideas what going on.?
darkensx said:
Has anyone got Link2SD to work on the R1 HD? It always seems to give the error: mount script cannot be created "mount:No such file or directory" when trying to create mount script. Any ideas what going on.?
Click to expand...
Click to collapse
yes. the android toybox/ toolbox used by blu has been altered and the mount function is not working properly. Same issue some have had with adaway, and other mods. The solution should be to install busybox and fully symlink it to /sbin.
I have not done it but based on your reported error it should be the correct solution.
old disscussion about "mount" linked here.
https://forum.xda-developers.com/showpost.php?p=71359910&postcount=201
mrmazak said:
yes. the android toybox/ toolbox used by blu has been altered and the mount function is not working properly. Same issue some have had with adaway, and other mods. The solution should be to install busybox and fully symlink it to /sbin.
I have not done it but based on your reported error it should be the correct solution.
old disscussion about "mount" linked here.
https://forum.xda-developers.com/showpost.php?p=71359910&postcount=201
Click to expand...
Click to collapse
Where should BusyBox be installed? ( mines currently in /system/xbin ) which BusyBox is best for this solution? ( mines v1.27.1.YDS )
darkensx said:
Where should BusyBox be installed? ( mines currently in /system/xbin ) which BusyBox is best for this solution? ( mines v1.27.1.YDS )
Click to expand...
Click to collapse
that should be correct. I made typo , didnt mean "sbin" meant "xbin"
mrmazak said:
that should be correct. I made typo , didnt mean "sbin" meant "xbin"
Click to expand...
Click to collapse
Ok so what should be symlink then I thought busybox install took care of the symlinking. What's the command too? Also I'm trying to use Link2SD instead of the lovely Android m adoptive sdcard stuff basically keep sd as portable while using Link2SD so I can have my PC see the fat32 partition if i needed.
darkensx said:
Ok so what should be symlink then I thought busybox install took care of the symlinking. What's the command too? Also I'm trying to use Link2SD instead of the lovely Android m adoptive sdcard stuff basically keep sd as portable while using Link2SD so I can have my PC see the fat32 partition if i needed.
Click to expand...
Click to collapse
the symlinking is done from in the bustbox installer.
so, you still have problem with busybox installed?
not so sure what to try next. Ah, check in the list of installed links for busybox and see if "mount" is shown as installed.
you can try to install the "toybox" from V12. It is untested method and you would need to know how to undo if needed.
link to the twrp install of that file is in my earlier post.
mrmazak said:
the symlinking is done from in the bustbox installer.
so, you still have problem with busybox installed?
not so sure what to try next. Ah, check in the list of installed links for busybox and see if "mount" is shown as installed.
you can try to install the "toybox" from V12. It is untested method and you would need to know how to undo if needed.
link to the twrp install of that file is in my earlier post.
Click to expand...
Click to collapse
Got it to work had to tell BusyBox installer to overwrite and symlink it apparently it's unchecked by default as its "not recommended to replace the systems version" :silly: go figure maybe under normal circumstances with a correctly functioning mount its bad but it fixed it stericson BusyBox installer did others weren't tested but I assume same result. But thanks for your help greatly appreciated it.
Just a note to anyone who comes across this thread if you use Titanium Backup at all don't use "BusyBox X" it seems to break T.B.'s ability to detect root this might be just magisk... or both SuperSU and magisk. but i had this happen with other devices some on SuperSU Some magisk but un-install "BusyBox X" (install any other busybox) and problem goes away not sure what direct cause is in "BusyBox X" might be because X is 1.26.1 and others are 1.27.1 ( ATM ) seems its always one version behind.
darkensx said:
Just a note to anyone who comes across this thread if you use Titanium Backup at all don't use "BusyBox X" it seems to break T.B.'s ability to detect root this might be just magisk... or both SuperSU and magisk. but i had this happen with other devices some on SuperSU Some magisk but un-install "BusyBox X" (install any other busybox) and problem goes away not sure what direct cause is in "BusyBox X" might be because X is 1.26.1 and others are 1.27.1 ( ATM ) seems its always one version behind.
Click to expand...
Click to collapse
magisk is working well in the r1?
dark8899 said:
magisk is working well in the r1?
Click to expand...
Click to collapse
yes but because of the way we have to initially unlock/root the r1 it doesn't pass safety net with magisk unless android is not passing safety net again with magisk. but like i mentioned some things can break root "busy box X" with certain apps. also xposed framework systemless and normal seem to work well.
I have patched august boot image and root with magisk .Can I just use ota to update?
bartoloandre98 said:
I have patched august boot image and root with magisk .Can I just use ota to update?
Click to expand...
Click to collapse
it's in the other thread already. Does not work
Benjamin_L said:
it's in the other thread already. Does not work
Click to expand...
Click to collapse
so what is the way forward? format?
bartoloandre98 said:
so what is the way forward? format?
Click to expand...
Click to collapse
some user is reporting success. So just try. You will loose root if it works and need a patched september boot image afterwards
I will try this when I'm home:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
hugopg said:
I will try this when I'm home:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
Did it work ?
It would be great if this method works, so no more patching of boot.img and flashing after every new OTA.
hugopg said:
I will try this when I'm home
Click to expand...
Click to collapse
Hey, did it work?
I really need to be assured .
*the fact that he disappear may not looks solid good ????
Didn't work for me.
rafihasan710 said:
Hey, did it work?
I really need to be assured .
Click to expand...
Click to collapse
I've tried it, but the update failed again
Lurensu said:
I've tried it, but the update failed again
Click to expand...
Click to collapse
When you enable hal3 API you modify the system partition. If even mounting it rw trips the "modified detector" it is no wonder ota does not work
Benjamin_L said:
When you enable hal3 API you modify the system partition. If even mounting it rw trips the "modified detector" it is no wonder ota does not work
Click to expand...
Click to collapse
This.
From what I understand, and the following confirms it, some people have simply edited the properties file in System (thus no updates) and some have used the 'setProp' command, which doesn't modify System.
The following explains it:
"Android system properties are being managed by special property_service. The /system/build.prop is just one out of 4-6 (depending on the version) read-only files containing the default values that property_service uses to populate its internal in-memory database with during start-up. So changes to the files during run time would not propagate until after reboot.
The setprop and getprop commands are used to access the data in that database. Unless the property name starts with persist. - then the value gets stored in /data/property folder."
So, it seems that if all you do with root is use setprop, you should continue to get the updates.
AsItLies said:
This.
From what I understand, and the following confirms it, some people have simply edited the properties file in System (thus no updates) and some have used the 'setProp' command, which doesn't modify System.
The following explains it:
"Android system properties are being managed by special property_service. The /system/build.prop is just one out of 4-6 (depending on the version) read-only files containing the default values that property_service uses to populate its internal in-memory database with during start-up. So changes to the files during run time would not propagate until after reboot.
The setprop and getprop commands are used to access the data in that database. Unless the property name starts with persist. - then the value gets stored in /data/property folder."
So, it seems that if all you do with root is use setprop, you should continue to get the updates.
Click to expand...
Click to collapse
I've used a Magisk module to enable camera2api.
I've now uninstalled magisk, anyone has an idea about how should I procede?
Lurensu said:
I've used a Magisk module to enable camera2api.
I've now uninstalled magisk, anyone has an idea about how should I procede?
Click to expand...
Click to collapse
This probably also does the setprop stuff. Do you know if uninstalling it restores the original state?
rafihasan710 said:
Hey, did it work?
I really need to be assured .
Click to expand...
Click to collapse
I won't try that because I've changed the build.prop to enable HAL3 and cameraApi2. So i'll need to flash the system.img BEFORE doing that... I'll do it next week only.
I outsourced rooting my device. Now I need access to Magisk to change the settings for the monitoring software I need to install. How do I open the Magisk app after it's been hidden? TIA!!!
It's in your app drawer, named "Manager".
gamoses said:
I outsourced rooting my device. Now I need access to Magisk to change the settings for the monitoring software I need to install. How do I open the Magisk app after it's been hidden? TIA!!!
Click to expand...
Click to collapse
Just run the app "Magisk Manager" or "Manager" (with the Magisk icon) that is on your app drawer.
Don't you have it? Well, then you don't have a proper installation of Magisk, at least the Manager is lacking. Download it (the apk) and install. Then open it and see if everything is fine or not. Check main Magisk release thread for links.
Thank you so much for replying! Magisk Manager is not in my app drawer, but it *is* listed in the device settings as an installed app. I just can't figure out how to open it. I assumed that app had also been hidden somehow. Advice?
Whoever you outsourced it to have done something that's not standard. Ask them...
Bummer. They'll probably charge me again. Thanks for your help, though!!!
gamoses said:
Bummer. They'll probably charge me again. Thanks for your help, though!!!
Click to expand...
Click to collapse
By the sound of it, they've messed up. So if I were you I would demand they fix things free of charge.
Didgeridoohan said:
By the sound of it, they've messed up. So if I were you I would demand they fix things free of charge.
Click to expand...
Click to collapse
Yeah, that didn't work. So I'm again trying to DIY...
Your wonderful guide says:
Unhiding the Magisk Manager
Go to the Manager settings and choose "Restore Magisk Manager".
Click to expand...
Click to collapse
But I can't do that because "Manager" is not in my app drawer.
You also have:
Starting MagiskHide manually
MagiskHide is enabled by default and should start automatically on boot. If it isn’t working, try toggling MagiskHide off and on in the Manager settings. If MagiskHide just won't start when toggling it in the Magisk Manager (check the Magisk log, it might have started but the Manager doesn't reflect it), try starting it manually. This can be done in a terminal emulator (as su) by executing the following command:
su
magiskhide --disable
magiskhide --enable
Click to expand...
Click to collapse
So I downloaded a terminal emulator and ran this command, but got this error message: su: unrecognized option '--disable'
Any more tips before I lose more money? Should I just try and reinstall Magisk completely? Having watched the tech guy do it the first time, I'm not sure I'm completely up for the task. Would it be easier after it's already been successful? Should this be straightforward, or am I better off handing over my wallet?
THANK YOU so much!!!
gamoses said:
Yeah, that didn't work. So I'm again trying to DIY...
Your wonderful guide says:
But I can't do that because "Manager" is not in my app drawer.
Click to expand...
Click to collapse
I'm curious... What happens when you want to grant superuser access to an app? Do you get the prompt to accept or deny?
I'm also curious what Magisk version you actually have installed. What's the result if you run this command in the terminal emulator:
Code:
magisk
You also have:
So I downloaded a terminal emulator and ran this command, but got this error message: su: unrecognized option '--disable'
Click to expand...
Click to collapse
You need to run the three commands separately, not all together.
Any more tips before I lose more money? Should I just try and reinstall Magisk completely? Having watched the tech guy do it the first time, I'm not sure I'm completely up for the task. Would it be easier after it's already been successful? Should this be straightforward, or am I better off handing over my wallet?
THANK YOU so much!!!
Click to expand...
Click to collapse
My first tip is to not trust your "tech" guy... From what you've described here it doesn't at all sound like he knows what he's doing.
Secondly, I would try to install the Manager and see what happens. Download the apk from here (that's the current version of Manager v7.2.0) and install that. If that works you're golden, if it doesn't report back...
I'm curious... What happens when you want to grant superuser access to an app? Do you get the prompt to accept or deny?
Click to expand...
Click to collapse
I don't know what this means or how to do that.
I'm also curious what Magisk version you actually have installed. What's the result if you run this command in the terminal emulator:
Click to expand...
Click to collapse
19.1
Secondly, I would try to install the Manager and see what happens. Download the apk from here (that's the current version of Manager v7.2.0) and install that. If that works you're golden, if it doesn't report back...
Click to expand...
Click to collapse
So I downloaded and installed this apk. I think. All that's necessary to do that is just click on it while on the phone, right? It said it was updating my previously installed Magisk Manager, so I assume it worked. But both immediately and after a reset, there is still nothing new in the app drawer. It still shows in my phone settings->apps, but that's it.
I've attached a log from my results in the terminal emulator regarding magisk and magiskhide. I'm sure I'm doing something wrong.
What launcher do you have? Sounds like the guy just his it from showing up the app drawer?
Sent from my MI 6 using Tapatalk
I was about to kick myself if it was that easy. Just installed Nova to check, and still no Manager app.
So should I just try to reinstall Magisk completely? Do I need to uninstall first? Is it as simple as opening the .apk on the device?
Hi, I have the same problem, did you find a solution?
Hi Everyone,
I am aware these things happen and as of yet I have not found a work around.
=> It only works if I unflash Magisk 19.3 or downgrade to the previous version of the Keytrade app (5.0.9)
=> it appears not be triggered by Magisk manager nor by the presence of certain downloads related to rooting.
=> Magisk hide is not able to fix this.
Tested on a Sony Xperia Z1c with AICP ROM. If I can be to any use to the dev, please drop me a line.
Could be using the stat & uds detection method. @topjohnwu already has a fix for that, just needs some time to implement it.
Didgeridoohan said:
Could be using the stat & uds detection method. @topjohnwu already has a fix for that, just needs some time to implement it.
Click to expand...
Click to collapse
For a workaround see this thread https://forum.xda-developers.com/apps/magisk/app-detecting-root-saftynet-pass-t3940628
https://github.com/Ingan121/UDSBypass
So you were right on the money!:good:
Jeroen1000 said:
For a workaround see this thread https://forum.xda-developers.com/apps/magisk/app-detecting-root-saftynet-pass-t3940628
https://github.com/Ingan121/UDSBypass
So you were right on the money!:good:
Click to expand...
Click to collapse
Hello !
I have the same problem and no method works... And there are a new update for the app (5.1.1).
Pims13 said:
Hello !
I have the same problem and no method works... And there are a new update for the app (5.1.1).
Click to expand...
Click to collapse
Exit all 'su's running on terminal. If it still doesn't work, run 'su -c chmod 600 /sepolicy /sys/fs/selinux/policy' and 'su -c killall su'.
Ingan121 said:
Exit all 'su's running on terminal. If it still doesn't work, run 'su -c chmod 600 /sepolicy /sys/fs/selinux/policy' and 'su -c killall su'.
Click to expand...
Click to collapse
The chmod doesn't work... "Not a directory"... -_-
Pims13 said:
The chmod doesn't work... "Not a directory"... -_-
Click to expand...
Click to collapse
Try the app first. If it's not working, run 'su -c ls /sepolicy /sys/fs/selinux/policy' and show me the result.
Thanks linked solution of su -c chmod 000 /proc/net/unix fixed my o2 Banking App too ?
Ingan121 said:
Try the app first. If it's not working, run 'su -c ls /sepolicy /sys/fs/selinux/policy' and show me the result.
Click to expand...
Click to collapse
I'm not authorized to post external links...
I have the same error message : not a directory
Pims13 said:
I'm not authorized to post external links...
I have the same error message : not a directory
Click to expand...
Click to collapse
Does the app crash immediately? Or it crashes after about 10-15 seconds?
Ingan121 said:
Does the app crashes immediately? Or it crashes after about 10-15 seconds?
Click to expand...
Click to collapse
The app crashes immediately...
Pims13 said:
The app crashes immediately...
Click to expand...
Click to collapse
Run 'su -c killall su' and check if the app works. If it's not working, install RootbeerFresh on Google Play and check if everything passes.
Hello I have same problem with my oneplus 6 for banking app
So what I did? This may help you
1st restore magisk manager if you hide it
Uninstall magisk
Flash the rom again no need to wipe data
Install magisk latest version
Open magisk manager
Hide magisk and in setting enable magisk hide and magisk core mode only
And hide all app in magisk manager
Or
Simply before doing all bla bla stuff above try this first
Hide magisk and in setting enable magisk hide and magisk core mode only
And hide all app in magisk manager
If work use it for 1 or 2 hrs then try disable core mode only then check still app detecting root
Because some module cause root detection even safty net pass
Pims13 said:
The app crashes immediately...
Click to expand...
Click to collapse
immediately and the app opens a website with the warning from keytrade.
After a reboot of the device the keytrade apps always opens a website with the warning.
Rootbearfresh results los 16
Should we download an older version of the keytrade app of accept that we can't use the mobile app anymore?
Same issue for me, I'll try the solutions mentioned above.
Yes! I did it - I passed all the checks on Rootbeefresh except the UDS one.
Then I ran this script that's mentioned before and it worked for me:
https://github.com/Ingan121/UDSBypass
I deleted root apps and I reinstalled the Keytrade app.
flotheking said:
Same issue for me, I'll try the solutions mentioned above.
Yes! I did it - I passed all the checks on Rootbeefresh except the UDS one.
Then I ran this script that's mentioned before and it worked for me:
https://github.com/Ingan121/UDSBypass
I deleted root apps and I reinstalled the Keytrade app.
Click to expand...
Click to collapse
I have follow your solution and finally it's work for me also now / no needed to reinstall keytrade after script run keytrade run immediately
Thanks
It's finally working ! \o/
I did Rootbearfresh, I don't pass all the test, I created the script I copied in /data/adb/service.d, I executed the command and ta dam !
Thanks all !
Just as a FYI: the UDS detection method has been circumvented in the latest Canary release (19307) and will of course be included in the next beta/stable release. Yay.