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!!!
Related
The included file is a binary that runs a daemon that fixes the lockscreen freeze that happens with dt2w/sw2w kernels. It requires busybox to be installed on your device. If your screen is still unresponsive the first time you attempt to wake your device; shut your screen off, wait a couple seconds, and try again and it will usually work.
The executable will do nothing on its own, so you must either have it start on boot with an init.d script or manually in terminal. It has to be ran as root.
To install the zip boot into recovery and install it using your recovery's standard install method, like installing a kernel or ROM.
To install the binary simply put the file in /system/bin and give it executable permissions
Recovery installer zip:
https://docs.google.com/file/d/0B_hgNZE_j5sVd0Itb1V4RGhhOGc/edit?usp=docslist_api
Binary:
https://docs.google.com/file/d/0B_hgNZE_j5sVLU9wdDEzamFUV0U/edit?usp=docslist_api
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
What this app does? How did you find it?
and after put in system/bin what to do next? how to run it?
Run it from the terminal command line, and it will continue to run in the background.
Its a quick and dirty fix that resets the touch screen driver when the screen is off.
If you copied the file to system bin you should be able to just type "scrfix" in your terminal and it will run in the background until your next reboot.
Alternatively you can just call it in an init.d script to have it start automatically on every boot.
I use SManager , give to scrfix su and boot privs it will work?
I haven't used that app personally, but it sounds like it should. Its normal for the program to seem like it exits because it spawns a child process that runs in the background that is owned by init (PID 1)
Or if you want to launch it manually, you can launch it in Terminal Emulator, but it will need started again on each reboot.
There is now a link to an installer zip for installation from recovery mode that comes with an init.d script included, for anyone using this method, please let me know if you encounter any issues with it. You may need to enable "trust system user" in your su application for it to work. The recovery installer was made with the ZipMe application.
Will this enable DT2W in cm12
Sent from my Moto G using Tapatalk
imranaryan said:
Will this enable DT2W in cm12
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
If you will read the title, you would realize that this mod is a fix for a very common problem faced by dt2w users. If you want dt2w, flash a custom kernel like optimus.
I just tried this on my Moto E 2015 and I ended up flashing a zip I modified when I tried it on my Moto G some time ago. I've found that it does not work when applying dt2w with an app such as Kernel Adiutor. It does work if you apply dt2w with an init.d script, and make it so the scrfix script is ran before the dt2w script. You just have to change the numbers in the beginning of the script name to something like 01 and 02 with the scrfix script having the smaller number.
Thanks for the info, I may upload an updated zip that has the name change to make sure it runs first. Some times too (on my phone atleast) when the screen isn't responsive I'll turn the screen off for 3-5 seconds and try again and it'll usually respond.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Please donate at:
http://www.PayPal.me/elrod16
Every bit helps, thanks!
elrod16 said:
Run it from the terminal command line, and it will continue to run in the background.
Its a quick and dirty fix that resets the touch screen driver when the screen is off.
If you copied the file to system bin you should be able to just type "scrfix" in your terminal and it will run in the background until your next reboot.
Alternatively you can just call it in an init.d script to have it start automatically on every boot.
Click to expand...
Click to collapse
i know this is an old forum but I just found it. How can I call it in an init.d script?
Just adding the line
scrfix
to a script.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Please donate at:
http://www.PayPal.me/elrod16
Every bit helps, thanks!
elrod16 said:
Just adding the line
scrfix
to a script.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Please donate at:
http://www.PayPal.me/elrod16
Every bit helps, thanks!
Click to expand...
Click to collapse
Would this be correct?
#!/system/bin/sh
/system/bin/scrfix
exit 0
Sent from my Moto E 2015 using XDA Labs
V-Droid said:
Would this be correct?
#!/system/bin/sh
/system/bin/scrfix
exit 0
Sent from my Moto E 2015 using XDA Labs
Click to expand...
Click to collapse
Yes, you'll also need another script with this:
#!/system/bin/sh
echo "2" > /sys/android_touch/doubletap2wake
This one needs to run after the previous script so you'll have to name them 98scrfix and 99dt2w. Also make sure their permissions are 0755.
---------- Post added at 08:46 PM ---------- Previous post was at 08:35 PM ----------
amarc78 said:
Yes, you'll also need another script with this:
#!/system/bin/sh
echo "2" > /sys/android_touch/doubletap2wake
This one needs to run after the previous script so you'll have to name them 98scrfix and 99dt2w. Also make sure their permissions are 0755.
---------- Post added at 08:46 PM ---------- Previous post was at 08:35 PM ----------
Click to expand...
Click to collapse
Im not able to change the script permissions, tried root browser but gave me an error. How can I change the permissions?
By the way sorry for the constant questions
Sent from my Moto E 2015 using XDA Labs
V-Droid said:
Im not able to change the script permissions, tried root browser but gave me an error. How can I change the permissions?
By the way sorry for the constant questions
Sent from my Moto E 2015 using XDA Labs
Click to expand...
Click to collapse
Try Root Explorer or ES File manager. As long as your rooted it should work.
amarc78 said:
Try Root Explorer or ES File manager. As long as your rooted it should work.
Click to expand...
Click to collapse
Still no luck, I tried root browser, root explorer and es file explorer all of them gave me the same error.
I also tried moving the file from the external SD card into the internal memory.
By the way, the way I create the scripts is in a .txt file, is this correct?
Sent from my Moto E 2015 using XDA Labs
V-Droid said:
Still no luck, I tried root browser, root explorer and es file explorer
Sent from my Moto E 2015 using XDA Labs
Click to expand...
Click to collapse
You need to put them in /system/etc/initd not on your sdcard.
amarc78 said:
You need to put them in /system/etc/initd not on your sdcard.
Click to expand...
Click to collapse
Thank you very much for all of your help, finally managed to change the permissions :laugh:
Sent from my Moto E 2015 using XDA Labs
This is a Magisk module to enable the assistant on existing Nexus devices
Github Repo:
https://github.com/kudiaborm/Nexus-Assistant
How soon? I'd like to try the assistant and I was thinking of doing the build.prop modification, but now that I saw this thread maybe I'll rather wait for this module.
Edit: Sweet module. Love it, worked as expected.
Make sure you're on a Google app version higher than 6.5.35.21. http://www.apkmirror.com/apk/google-inc/google-search/google-search-6-6-14-release/
Magisk Manager doesn't like cache mods so you have to flash in recovery. Make sure you wipe data for Google App after flashing.
This only sets the two build. prop variables. I didn't include any Google app apks or wipe data for Google app. You'll have to do that yourself.
flindaman said:
This is a Magisk module to enable the assistant on existing Nexus devices
Github Repo:
https://github.com/kudiaborm/Nexus-Assistant
Click to expand...
Click to collapse
Just so you're aware replacing the entire build.prop causes issues. It's best to replace the two individual lines. You can use my module as a guide.
loserskater said:
Make sure you're on a Google app version higher than 6.5.35.21. http://www.apkmirror.com/apk/google-inc/google-search/google-search-6-6-14-release/
Magisk Manager doesn't like cache mods so you have to flash in recovery. Make sure you wipe data for Google App after flashing.
This only sets the two build. prop variables. I didn't include any Google app apks or wipe data for Google app. You'll have to do that yourself.
Click to expand...
Click to collapse
Will this be a magisk module still? Can it be undone easily?
loserskater said:
Just so you're aware replacing the entire build.prop causes issues. It's best to replace the two individual lines. You can use my module as a guide.
Click to expand...
Click to collapse
Oddly enough no matter what I tried it didn't work/run properly from the post-fs script. I'll check your module. Maybe it has something to do with file encoding
flindaman said:
Oddly enough no matter what I tried it didn't work/run properly from the post-fs script. I'll check your module. Maybe it has something to do with file encoding
Click to expand...
Click to collapse
I couldn't get his to work. I probably am doing it wrong. But now on tap still shows up.
loserskater said:
Make sure you're on a Google app version higher than 6.5.35.21. http://www.apkmirror.com/apk/google-inc/google-search/google-search-6-6-14-release/
Magisk Manager doesn't like cache mods so you have to flash in recovery. Make sure you wipe data for Google App after flashing.
This only sets the two build. prop variables. I didn't include any Google app apks or wipe data for Google app. You'll have to do that yourself.
Click to expand...
Click to collapse
Flashed in TWRP on Nexus 6, no /cache/magisk was created and neither the properties have changed:
Code:
$ adb shell
shamu:/ $ getprop ro.product.model
Nexus 6
shamu:/ $ getprop ro.opa.eligible_device
shamu:/ $
Did it work on Nexus 6p?
loserskater said:
Make sure you're on a Google app version higher than 6.5.35.21. http://www.apkmirror.com/apk/google-inc/google-search/google-search-6-6-14-release/
Magisk Manager doesn't like cache mods so you have to flash in recovery. Make sure you wipe data for Google App after flashing.
This only sets the two build. prop variables. I didn't include any Google app apks or wipe data for Google app. You'll have to do that yourself.
Click to expand...
Click to collapse
This worked for me, thanks so much. Was wating for a way to do this in magisk
Flashed the file in twrp, rebooted, wiped all google app data, long pressed home and there it was. "ok google" command working great
My setup:
Nexus 6P
Stock NBD90X
Magisk v7
Magisk phh
Magisk V4A
Papote3 said:
This worked for me, thanks so much. Was wating for a way to do this in magisk
Flashed the file in twrp, rebooted, wiped all google app data, long pressed home and there it was. "ok google" command working great
My setup:
Nexus 6P
Stock NBD90X
Magisk v7
Magisk phh
Magisk V4A
Click to expand...
Click to collapse
Are you able to Download+Install modules through the Magisk Manager Downloads section? I'm on NBD90x with Magisk v7, Nexus 6P, Magisk phh, Magisk Manager 2, and I get an error for every module I try to install through the manager. If I could get at the zips and just flash them that would be awesome, but I can't.
shinobi26 said:
Are you able to Download+Install modules through the Magisk Manager Downloads section? I'm on NBD90x with Magisk v7, Nexus 6P, Magisk phh, Magisk Manager 2, and I get an error for every module I try to install through the manager. If I could get at the zips and just flash them that would be awesome, but I can't.
Click to expand...
Click to collapse
Yes I can download, install and reboot from the manager. But this mod needs to be flashed in recovery FYI.
Try and flash them from recovery. There's a folder where magisk manager downloads the zip files. It's in the root of the SD and I think its named magiskmanager
Papote3 said:
Yes I can download, install and reboot from the manager. But this mod needs to be flashed in recovery FYI.
Try and flash them from recovery. There's a folder where magisk manager downloads the zip files. It's in the root of the SD and I think its named magiskmanager
Click to expand...
Click to collapse
Yes, there is. Unfortunately immediately after the zips are downloaded, when the install fails, it removes the zip and I can't get at it. I've gone completely back to full stock NBD90X and installed everything, gone into Magisk Manager and am still unable to install any of the modules from there. It's so frustrating, haha.
shinobi26 said:
Yes, there is. Unfortunately immediately after the zips are downloaded, when the install fails, it removes the zip and I can't get at it. I've gone completely back to full stock NBD90X and installed everything, gone into Magisk Manager and am still unable to install any of the modules from there. It's so frustrating, haha.
Click to expand...
Click to collapse
Does magisk manager have storage permission?
loserskater said:
Does magisk manager have storage permission?
Click to expand...
Click to collapse
It does. It's the only permission in fact.
If there's any Nexus 6 (so far the only arm and not arm64 phone to get Nougat, right?) owner who have this module or any other cache-module working, please post here. I suspect something cache-module related is broken on the arm phone(s).
stangri said:
If there's any Nexus 6 (so far the only arm and not arm64 phone to get Nougat, right?) owner who have this module or any other cache-module working, please post here. I suspect something cache-module related is broken on the arm phone(s).
Click to expand...
Click to collapse
You could try my mod. Instead of replacing the whole buld.prop file it just adds the two properties
Code:
ro.product.model=Pixel
ro.opa.eligible_device=true
to it.
Edit:
Forgot to mention it's still a cache mod so let me know how it works out.
And remember you need to flash it via recovery. Magisk Manager won't install it correctly.
Edit2:
As you can see below, loserskater already posted the same thing in post 3.
So yeah ...
TAM1m said:
You could try my mod. Instead of replacing the whole buld.prop file it just adds the two properties
Code:
ro.product.model=Pixel
ro.opa.eligible_device=true
to it.
Edit:
Forgot to mention it's still a cache mod so let me know how it works out.
And remember you need to flash it via recovery. Magisk Manager won't install it correctly.
Click to expand...
Click to collapse
This is exactly like my module in post 3 of this thread.
loserskater said:
This is exactly like my module in post 3 of this thread.
Click to expand...
Click to collapse
Oh man I didn't see that.. Sorry! Didn't want to take anything from you
TAM1m said:
Oh man I didn't see that.. Sorry! Didn't want to take anything from you
Click to expand...
Click to collapse
No worries, just merely pointing it out.
TAM1m said:
Oh man I didn't see that.. Sorry! Didn't want to take anything from you
Click to expand...
Click to collapse
Thanks for trying to help, but you probably missed this: http://forum.xda-developers.com/showpost.php?p=69088754&postcount=8 too.
Again, if anyone with Nexus 6 (or arm platform in general) got any cache modules working, please let me know.
I'm rooted with SuperSU 2.79 systemless on OOS 4.1.0 and I can't get permission to write on /system.
I tried using ES FIle Explorer and the option keeps changing to RO. I also tried via recovery. Root permissions are granted and It's properly root.
Any clues?
belumira said:
I'm rooted with SuperSU 2.79 systemless on OOS 4.1.0 and I can't get permission to write on /system.
I tried using ES FIle Explorer and the option keeps changing to RO. I also tried via recovery. Root permissions are granted and It's properly root.
Any clues?
Click to expand...
Click to collapse
I had the same issue. I don't remember what I did. Try uninstalling super su from the app and then install it again.
Migdilu said:
I had the same issue. I don't remember what I did. Try uninstalling super su from the app and then install it again.
Click to expand...
Click to collapse
Did that, I even clean flashed OOS again nothing seems to be working.
belumira said:
I'm rooted with SuperSU 2.79 systemless on OOS 4.1.0 and I can't get permission to write on /system.
I tried using ES FIle Explorer and the option keeps changing to RO. I also tried via recovery. Root permissions are granted and It's properly root.
Any clues?
Click to expand...
Click to collapse
I also had problem with ES File Explorer while writing to system. Try solid Explorer. It's better
Vaibhunk786 said:
I also had problem with ES File Explorer while writing to system. Try solid Explorer. It's better
Click to expand...
Click to collapse
Still nothing. For some reason permissions won't change.
You have systemless root?
If yes I think you can only modify data Partition. Maybe you need a magisk module?
Remove superSU and just go with Magisk. It works much better than SuperSU ever will. It's easily removable and won't adjust partition permissions, including system. Make sure you mount system in twrp before flashing any root access zip file as well. It helps prevent problems like this.
Fix To Grant ES File Explorer SuperSU Access Using Terminal Emulator
Start Terminal Emulator. Type su.
ENTER EXACTLY LIKE THIS: echo "BINDSYSTEMXBIN=true" >> /data/.supersu
Spaces.......................................................................................... ^....^.........
Make a backup first incase ****e goes south... This has worked for me on a couple of devices.
Standard disclaimer... Yada...
I have the same problem.
jhill110 said:
Fix To Grant ES File Explorer SuperSU Access Using Terminal Emulator
Start Terminal Emulator. Type su.
ENTER EXACTLY LIKE THIS: echo "BINDSYSTEMXBIN=true" >> /data/.supersu
Spaces.......................................................................................... ^....^.........
Make a backup first incase ****e goes south... This has worked for me on a couple of devices.
Standard disclaimer... Yada...
Click to expand...
Click to collapse
Sorry but I dont understand what I have to write, I understand type su
and type echo "BINDSYSTEMXBIN=true" >> /data/.supersu
but whats mean:
Spaces.......................................................................................... ^....^.........
Mean: ^ ^
doesnt mean anything? :crying::crying:
Here I got a very simple fix
Go find a root explorer
Go to /magisk
Check every module.prop in every module
Make sure at the end it have an extra empty line. If not, change it .
Lunch app again . Everything should be fine now.....
It seems to be the mistake maked by some module's dev
I can't install any module ?, already tried to flash module with magisk manager and twrp, still not success..
raymondsanusi said:
I can't install any module , already tried to flash module with magisk manager and twrp, still not success..
Click to expand...
Click to collapse
You dont flash modules... You go to the modules section of magisk manager, and hit the + sign. Then it will open a file manager, you simply just tap and hold on the zip file containing the module, and hit open in the top right. Your module will then be installed and a simple reboot will activate it. Flashing with twrp does nothing lol
That fix worked great.
Thanks!
( If it is not clear: you can find /magsik in your root folder, you need a root filemanager)
Thanks, it worked, adfree youtube module had a missing blank line
https://forum.xda-developers.com/apps/magisk/module-adfree-youtube-template-t3532753
TCUofficial said:
You dont flash modules... You go to the modules section of magisk manager, and hit the + sign. Then it will open a file manager, you simply just tap and hold on the zip file containing the module, and hit open in the top right. Your module will then be installed and a simple reboot will activate it. Flashing with twrp does nothing lol
Click to expand...
Click to collapse
you sure about that? I've been flashing my modules through TWRP and after booting up I can see them in MagiskManager
Unified Hosts Adblock and Universal Deep Buffer Removal doesn't have that blank line. By fixing them, now I'm able to use Magisk Manager 5.1.0 . Thank you.
Sent from my bullhead using XDA Labs
TCUofficial said:
You dont flash modules... You go to the modules section of magisk manager, and hit the + sign. Then it will open a file manager, you simply just tap and hold on the zip file containing the module, and hit open in the top right. Your module will then be installed and a simple reboot will activate it. Flashing with twrp does nothing lol
Click to expand...
Click to collapse
That's just completely wrong... You install modules through the Manager OR by flashing in TWRP. Whatever floats your boat.
Didgeridoohan said:
That's just completely wrong... You install modules through the Manager OR by flashing in TWRP. Whatever floats your boat.
Click to expand...
Click to collapse
sorry, I have been installing Modules in Magisk Manager, I didn't know you could in twrp. Mistakes have been made today, and again, I am sorry.
Ha, amazing fix! Now can someone explain why that happens?
thanks for this! couldn't figure out why it was a perfect install, but after adding modules it would hang... this fixed it for me!
TCUofficial said:
You dont flash modules... You go to the modules section of magisk manager, and hit the + sign. Then it will open a file manager, you simply just tap and hold on the zip file containing the module, and hit open in the top right. Your module will then be installed and a simple reboot will activate it. Flashing with twrp does nothing lol
Click to expand...
Click to collapse
See this...
raymondsanusi said:
See this...
Click to expand...
Click to collapse
As I said earlier, I didnt know you could flash modules in twrp. I have no clue why that error happens.
Silkeyway said:
Ha, amazing fix! Now can someone explain why that happens?
Click to expand...
Click to collapse
Because some dev forgot a basic rule (to leave an empty line in the end) when making their modules
Come on devs ... Even the Github will give you a warning when this happens... Did you guys never check it again?:silly:
yurishouse said:
Because some dev forgot a basic rule (to leave an empty line in the end) when making their modules
Come on devs ... Even the Github will give you a warning when this happens... Did you guys never check it again?:silly:
Click to expand...
Click to collapse
Sure, but why do you need that?
Just asking because I'm learning bash and Python and now I wonder about things like that :angel:
5.1.1 fixed this issue, so.
You guys don't need to do it now.:good:
Silkeyway said:
Sure, but why do you need that?
Just asking because I'm learning bash and Python and now I wonder about things like that :angel:
Click to expand...
Click to collapse
Is a Linux rule, if not blank line, is like the file have not end.
Deic said:
Is a Linux rule, if not blank line, is like the file have not end.
Click to expand...
Click to collapse
Yep you are right.. I just read the update:good:
Hi there,why after updating my magisk manager,every timed force closes my magisk manager,I try clear dalvik and cache still not fix,any idea?Thanks
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