Related
Hi,
what started as an Idea seems to be working now. For once i wanted a phone that has warranty for more than two weeks (or at least a chance for warranty).
DISCLAIMER:
Do all of this at your own risk. Even though we will not be flashing a custom recovery, technically the warranty is lost the moment you root your phone.
None of the Tools is actually written by me, i just tinkered a bit and came up with this tutorial.
1. You will need
- Galaxy A3 (mine was an A300FU but i guess every one that can be rooted without flashing should do) on Lollipop (5.0.2).
- Minimal ADB or some other software that brings debugging drivers and adb.
- KingRoot 4.60+
- SuperSu-ME (from play Store or an older version is also fine) or any other way to go from the Kinguser Root Management to SuperSU
- Deodexed apks matching you phone model
- Flashfire Beta
- Xposed Installer, I used 3.0alpha4
- Xposed bridge for Samsung lollipop I used xposed-v75-sdk21-arm-arter97-snapdragon_requestConcurrentGC
2. If something goes wrong:
- Odin and a stock LOLLIPOP ROM for your device!
This is Important: Since we dont have a custom recovery, whenever something goes wrong the only rescue is going back to a stock rom and thereby wiping. If everything works in the first go there will be no wipe.
3. Rooting
First we need to root. Thanks to KingRoot thats very easy and just a matter of waiting. Install KingRoot (has to be 4.60+ for Lollipop), Click try to Root, wait for it, done. Know we need to get rid of the KingRoot stuff again and install SuperSU (FlashFire does not support KingUser but SuperSU) thats what we need SuperSU-ME for. There Will be some Left overs since KingRoot converts itself to a system app, you can remove this with Titanium Backup or a ROM Toolbox of you choice.
4. Deodexing
Next step is gonna be Deodexing. This one is a little Tricky without a Custom Recovery. Flashing the Deodex using FlashFire will leave you stuck at the Boot Logo.
Unpack the Flashable Deodex zip. you#ll find a META-INF and a system folder. Copy the system folder (or rename it, doesnt matter) to your SDcard or the phone memory using USB. At this point you can also copy the two Xposed files (zip+apk). Next we need USB Debugging. Install the minimal ADB, browse to the install location and start "adb devices" once (this will start the daemon). Now take your phone, browse to settings / phone info and tap the build number like 10 times (this gives you developers options) now go to settings / developers options and enable USB debugging.
Connect you phone via USB. This hould bring up a dialog granting your PC permission to connect. Click Yes.
Connect to the phone and request root using
Code:
adb shell
su
Now turn on the phones screen there should be a root request, allow it.
Next is the following commands, assuming the location of the extracted system folder is /storage/extSdCard/deodex_system
Code:
mount -o rw,remount /system
rm -Rf /system/app
rm -Rf /system/priv-app
rm -Rf /system/framework
cp -R /storage/extSdCard/deodex_system/* /system
chown -R root:root /system/app
chown -R root:root /system/priv-app
chown -R root:root /system/framework
chmod -R 755 /system/app
chmod -R 755 /system/priv-app
chmod -R 755 /system/framework
rm -Rf /data/dalvik-cache/*
reboot
This will replace all system apks with the deodexed ones, sets the right owner and permissions, clears the dalvik cache and reboots. Booting is gonna take a while and then you're enjoying you're rooted, deodexed stock ROM without flashing anything so far. So now about installing Xposed.
Don't be to slow with thus step. Deleting the three folders will make the phone go crazy and at some point reboot, you should be done by then.
Edit: I did this on a second device now, for some reason the remount did not work. In this case try disabling SElinux (http://forum.xda-developers.com/devdb/project/dl/?id=12178) and then remount.
5. Xposed
Install the XposedInstaller apk file like any other app, no need to start it yet. Next install FlashFire and launch it (granting root access) now select the Option "OTA or ZIP" in Flashfire and select the flashable Xposed zip you downloaded earlier. No further settings needed just hit Flash! The next reboot is again gonna take a while, but after that you can launch the Xposed Installer and start Installing Modules. We're done.
Whenever you do a factory reset (from the recovery), You need to root again using Kingroot, replace it with SuperSU and install Xposed again.
Once more, I did not develop any of the tools mentioned, all credits to their respective authors.
Cheers,
prometh
Edit: I did not try too many modules yet but Wanam for lollipop works just fine and that useless S Whatever bar is a thing of the past
Hi.
I already have a rooted Galaxy A3 (A300FU) and I have TWRP as my recovery so my warranty is already gone and I'm not too worried about that. However I have had no success at trying to deodex my rom to be able to install xposed.
Would it be possible to just flash the deodexed and the xposed zip from TWRP? And with regards to the deodexed zip would it matter if I flash it over the top of my current rom when I'm using a carrier rom rather than the BTU unlocked rom?
Squall88uk said:
Hi.
I already have a rooted Galaxy A3 (A300FU) and I have TWRP as my recovery so my warranty is already gone and I'm not too worried about that. However I have had no success at trying to deodex my rom to be able to install xposed.
Would it be possible to just flash the deodexed and the xposed zip from TWRP? And with regards to the deodexed zip would it matter if I flash it over the top of my current rom when I'm using a carrier rom rather than the BTU unlocked rom?
Click to expand...
Click to collapse
I think this would be a question for the deodex thread I linked but heres my 5 cents: The procedure in your case should be Flashing Deodex (eventually also gapps_replacement from that thread if you get Google Apps FCs) flashing Xposed, booting, installing the xposed installer. The Deodexed zip is meant to be flashed on top of your system. What I described is basically doing manually what the deodex zip file would do (deleting copying...). Since you have twrp already, I guess a system backup wouldn't hurt.
Many thanks for the help. I'll make a nandroid backup of system first just in case and then give it a go.
Thanks again.
Impossible with my SG A3 A300FU
Hello, I already have the root and TWRP installed, but if I try to type the command line with ADB it doesn't work and if I flash the zip, it doesn't work too. Any Idee ? With the first or the second method boot loop with the samsung logo !!
darwin345 said:
Hello, I already have the root and TWRP installed, but if I try to type the command line with ADB it doesn't work and if I flash the zip, it doesn't work too. Any Idee ? With the first or the second method boot loop with the samsung logo !!
Click to expand...
Click to collapse
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Great work prometh696 !!! I managed to get xposed on my A5 with knox 0x0 !!!
Some other steps I followed to get it for my A500FU; first I extracted my own system folders system/app/, system/framework/ & system/priv-app/ with root explorer to my ext SD card and then copied it to my computer.
On the computer I batch deodexed those folders with joeldroid's batch deodexer:
http://forum.xda-developers.com/and.../script-app-joeldroid-lollipop-batch-t2980857
Had some issues there as not every Java version seems to deliver the deodexed folders without errors; more details in that topic.
Then I followed your adb commands and installed xposed, and as you said, knox didn't change and is still 0x0 !!!
Thanks again !!!
---------- Post added at 01:30 PM ---------- Previous post was at 01:06 PM ----------
prometh696 said:
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Click to expand...
Click to collapse
The command lines are for copying the deodexed apks (so not in a zip). The zip is for xposed and is flashed by flashfire.
But as he already got TWRP (and thus knox 0x1) I see no use for him to use your method anyway
prometh696 said:
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Click to expand...
Click to collapse
When I type the first command line after this one "rm -Rf /system/priv-app" or this one "rm -Rf /system/framework" I don't know when exactly my phone reboot and bootloop on samsung logo (dynamic one) ???
My mobile restart before end of commands line
Hi,
your solution seems really good but my mobile (A300FU) is retarting before I typed all commands line.
Do you know a solution ?
Maybe cause I've no ExtSDcard and use the internal card ?
Thank you for your help !!
Regards
Virtua
update : I tried with trwp and made the necessary but the mobile does not boot.
This phone is a mess
It's the first time I can't do what I want with a phone. All posts seems to be a hoax. ;( ;(
Whenever you do a factory reset (from the recovery), You need to root again using Kingroot, replace it with SuperSU and install Xposed again.
Click to expand...
Click to collapse
This is actually incorrect unless root is systemless.
Root remains in system, and so does xposed. A factory reset does not touch the system partition.
You lose root after a reset because you need to reinstall superuser. If you make it a system app you won't lose root even after a reset.
The same with xposed just reinstall the apk.
Custom adb root boot image with chainfires adbd kernel from adbd insecure as the phones adbd.. it has a few other tweaks and a custom permissive kernel and systemless root from chainfires supersu... the rsa fingerprint doesn't pop up when you connect a computer but it can be bypassed with adb in a custom recovery and found out if you use adbd insecure and let it patch chainfires adbd kernel it makes the phone as attached device in for adb devices instead of the plain unauthorized device and vendor keys not set. ... if you use it now you get adb root access and regular root access with the su binary but due to the rsa fingerprint not popping up you have to use adbd insecure until a recovery comes out cause it bypasses rsa fingerprint.. credits to come... to use adb root access you need a custom recovery with adb... adbd insecure app... adb on you're computer.... android sdk/android studio... java... boost mobile j7 running build f3 but you can just run systemless root until a recovery comes through. You can grab systemless root from here http://forum.xda-developers.com/galaxy-j7/how-to/root-samsung-galaxy-j7-sm-j700p-t3430185
And use it with the boot image.. but i just added systemless root patches to the boot image so all you have to do is flash the boot image.
Stock boot image below incase you want to unroot and go back to stock which can be flashed in flashfire link below. You can take this boot image and use flashfire to flash the stock firmware or stock boot image and you can root or not root when you flash with flashfires inject systemless root.
Flashfire below
https://play.google.com/store/apps/details?id=eu.chainfire.flash
Stock boot image below
https://drive.google.com/file/d/0B6d5ZB2mhxuHQWlqT2RDMDJNWlE/view?usp=drivesdk
All i did was add adb root access to the ramdisk.. and a few other ramdisk tweaks and added supersu systemless root patch to the boot image and chainfires adbd insecure kernel as the phones adbd. And added the stock boot image in a odin flashable tar.
Custom adb root access and regular systemless root Boot image below
https://drive.google.com/file/d/0B6d5ZB2mhxuHUUpkandKRUpEdXc/view?usp=drivesdk
Credits....
@messi2050 from xda for original boot image and permissive kernel..
@messi2050 from xda for providing instructions on how to root with cf auto root
@Chainfire from xda for adbd kernel and adbd insecure app
@Chainfire from xda for cf auto root tar
@Chainfire from xda for systemless root and supersu
@Chainfire from xda for flashfire
@ANyOne from xda or anywhere else who tests it.
Updated op with a new test build it has systemless root patches from chainfires supersu systemless root and roots you when you flash it in odin.
Added stock boot image to op... incase you want to remove root and the tweaks. Its simple to remove the roots and tweaks by just flashing the stock boot image in odin or flashfire.
Ive been testing as i go.. i haven't had any problems with root access it works pretty good and runs smoothly.
Added flashfire and some minor boot image flashing instructions to get back to stock rooted.
Test build #4 is up.. did some changes in default prop in ramdisk.. should make adb root access more smoother when it gets used in a custom recovery...
Update after some tweaking my last tweaks allow you to access the apn menu and edit apns and add apns.. in regular stock boot image its locked down and you cant access it but you can with this boot image.
Now works with adbd insecure app just let it patch chainfires adbd kernel and it lets you bypass the rsa fingerprint so you can run adb shell without having to wait for a custom recovery. Be sure to test adb shell and adb root access.
In the process of testing adb shell and adb root access some more....
After extensive testing for the past 3 hours using every adb command and adb shell command i can find.... the results are they all work...
Snapping screen shots and screen recording works pretty good too..
For the moment use titanium backup pro or app quarantine to disable/freeze the security logs and stop the pop up cause the permissive kernel running permissive instead of enforcing.
App quarantine
https://play.google.com/store/apps/details?id=com.ramdroid.appquarantine
[email protected]:/#
/sbin/adbdsh:
Bravo!!
Sent from my SM-J700F using XDA-Developers mobile app
Modified adbd uses /sbin/adbd : as its terminal shell
Original adbd uses /system/bin/sh as its terminal shell
One of the mods i did if youre curious but due to usb debugging being secure in newer android versions aka the rsa fingerprint having to match both on computer and phone and the fact you cant just reset the rsa key on stock cause it removes the revoke usb debugging authorization to reset the rsa fingkey and key so you dont get the full luxury of this old mod which has been around awhile and is not new... to grant root on stock firmware you need a custom recovery with adb or chainfires adbd insecure app... oh how times have changed in android...
Get Android Image Kitchen and extract it to your PC;
2. Open your_favorite_kernel.zip with 7zip and extract boot.img file to Android Image Kitchen folder;
3. Drag and Drop boot.img over unpackimg.bat. Kernel is unpacked and you will see 2 new folders - ramdisk and split_img;
4. Go to ramdisk folder and open default.prop file with text editor. This probably is not necessary but just in case change ro.secure and ro.adb.secure to 0 (zero):
Code:
ro.secure=0
ro.adb.secure=0
5. Get Chainfire's adbd Insecure v1.30, open it with 7zip, in assets folder you will see 3 .png files. Extract adbd.17.png to ramdisk\sbin folder;
6. Delete original kernel adbd file and rename adbd.17.png to adbd;
7. Go back to Android Image Kitchen folder and run repackimg.bat by just click on it. This will repack the modified kernel to image-new.img file ready for flashing;
8. Rename image-new.img to boot.img and replace the original one in your_favorite_kernel.zip by Drag and Drop in 7zip window;
9. Close 7zip, copy modified your_favorite_kernel.zip to /sdcard and flash it in recovery.
10. Enjoy ADB full root access for /system;
Android Sdk/ Android Studio
https://developer.android.com/studio/index.html
Java for devs and java for consumers
https://www.oracle.com/java/index.html
For development and adb purposes ill just leave this here.. its big enough to have its own thread but it goes with this mod so ill just leave it here..
CoffeeNAndroid said:
One of the mods i did if youre curious but due to usb debugging being secure in newer android versions aka the rsa fingerprint having to match both on computer and phone and the fact you cant just reset the rsa key on stock cause it removes the revoke usb debugging authorization to reset the rsa fingkey and key so you dont get the full luxury of this old mod which has been around awhile and is not new... to grant root on stock firmware you need a custom recovery with adb or chainfires adbd insecure app... oh how times have changed in android...
Get Android Image Kitchen and extract it to your PC;
2. Open your_favorite_kernel.zip with 7zip and extract boot.img file to Android Image Kitchen folder;
3. Drag and Drop boot.img over unpackimg.bat. Kernel is unpacked and you will see 2 new folders - ramdisk and split_img;
4. Go to ramdisk folder and open default.prop file with text editor. This probably is not necessary but just in case change ro.secure and ro.adb.secure to 0 (zero):
Code:
ro.secure=0
ro.adb.secure=0
5. Get Chainfire's adbd Insecure v1.30, open it with 7zip, in assets folder you will see 3 .png files. Extract adbd.17.png to ramdisk\sbin folder;
6. Delete original kernel adbd file and rename adbd.17.png to adbd;
7. Go back to Android Image Kitchen folder and run repackimg.bat by just click on it. This will repack the modified kernel to image-new.img file ready for flashing;
8. Rename image-new.img to boot.img and replace the original one in your_favorite_kernel.zip by Drag and Drop in 7zip window;
9. Close 7zip, copy modified your_favorite_kernel.zip to /sdcard and flash it in recovery.
10. Enjoy ADB full root access for /system;
Click to expand...
Click to collapse
Hello
Thanks for this tutorial !
I remain on the Samsung logo written with "recovery is not enforcing blah"
Yet I do exactly what's in the tutorial. I boot with the SM-J710FN
Could you help me please?
thank you in advance
Warning!!! I’m not responsible for anything (death, destruction, or nuclear war) which happens to you & your stuffs after following this guide.
Downloads :-
RR-Magisk-Root-vivo-Y51L.zip
TipsyOS Prerooted ROM
How to Install ?
1. Make sure you have RR rom installed(Get it Here) before flashing RR-Magisk-17.2-vivo-Y51L.zip
2. Reboot to TWRP recovery
3. Install RR-Magisk-17.2-vivo-Y51L.zip or TipsyOs-prerooted.zip, whatever your choice is.
4. Reboot to System.
5. If root worked, Come back and the hit the thanks button below!
:Video Tutorial on the same:
https://www.youtube.com/watch?v=omUggCUJGGk
-:NOTES FOR VIVO Y51L DEVS:-1. Played with Magisk once for around 3 hours
2. You wanna know ? Seriously ? Okay
3. Disable Selinux which isn't needed by root ! (Just for fun)
4. Downlad Magisk-latest.zip
5. Extract magiskinit from arm folder
6. Push magiskinit to /data/local/tmp
7. Run :
adb shell
cd data/local/tmp
chmod 755 magiskinit
./magiskinit -x magisk magisk
exit
adb pull /data/local/magiskinit8. Now you will get an file with name magisk in the current dir
9. Place it in the /system/xbin/ folder of your rom
10. Place Magisk Manager apk in /sytem/app/Magisk
11. Now, boot.img part :
Following things to be done in boot.img :
Created /sbin/permissive.sh
Patched default.prop, fstab.qcom, init.environ.rc, init.rc, init.recovery.service.rc, init.root.rc, init.superuser.rc (create one if..), sepolicy, service_contexts
If you wanna know the stuff i added in these files, just search 'Naveen' in all those files (Yeah, i reckon that, i'm Superlazy to find & write those here even though i can write 55wpm)12. What about how to patch sepolicy ? Uh, I used supolicy by @Chainfire (Thanks man....)
13. How to find selinux denies ? Install audit2allow in your linux system & :
adb shell dmesg | audit2allow -p (your sepolicy here, use 'adb pull /sys/fs/selinux/policy') > selinux.error
Now push supolicy to phone (Download SuperSU.zip)
adb push ./ /data/local/tmp/tony/
adb shell
cd /data/local/tmp/tony/
chmod 755 *
./supolicy --live "error here"
./supolicy --save /data/local/tmp/tony/new_sepolicy
exit
adb pull /data/local/tmp/tony/new_sepolicy
Rename new_sepolicy to sepolicy & replace your original one in boot.img
Repack your boot.img13. This won't work with stock rom since we get operation not permitted errors while trying to exec su, i think it's Linux Capabilities (Read more about that here : http://man7.org/linux/man-pages/man7/capabilities.7.html) Don't ask me why it works in cm roms if kernel is the problem
14. Whatever you wanna ask me, reply here please (I'm don't check private messages anymore)
Official Telegram Group for Vivo Y51L/Y21L : https://t.me/vivodevelopment
Fix for bugs
Please fix the bugs asap....i am facing audio and video playback problems
#ask
are you facing mic and call problem?
use y51l kernal
bro.
can you use y51l kernal to patch file?
so that y51l may get rooted with no bugs
Bugs are there
*Front camera not working
*Flash light not working
*Magisk not installing
y51 kernal source restore
can you make tutorial to restore y51 kernal source .also there a wifi bug wont turn on
device stuck at app starting up....pls hlp
installed the miui root boot.img and twrp.img but after rebooting the device was stuck
Can't root
How to download
Magisk cannot run in third-party ROM
It's a pity that my favorite ROM cannot be ROOT. It's not that the installation fails, but it always stops working.
I have a more useful method for rooting vivo y51L
Requirements:-
OTG
Data cable
A second phone
Bootloader unlock
Bugjaeger application
Root checker application
Your custom ROM or stock ROM zip file
Firstly we have to unzip our stock or custom ROM zip file, after unzipping file we have to move out boot.img file and save it in our internal storage . After that we have to flash the boot.img file in magisk and after flashing we will get a magisk patch in our download folder . We have to send that patch to our second phone and save it in it's internal storage .after that we have to boot our phone in fastboot mode and for that we have to power off our device and press volume down and power button .After booting the device in fastboot mode you have to connect otg in your second device and data cable in fastboot device . After that connect data cable and otg , after connecting the Bugjaeger application will open automatically . after that find an icon which looks like lightning in app and click that , after that you will find a blue dot at the bottom of the screen . Click that button and you will get inside command section after that type the first command :- Fastboot devices and click the play button at the right side. After that you will see a serial number which means you are connected. After that write the second command :- Fastboot flash boot , after writing it we will find a paper clip type button at the top right corner , just click that and attach the magisk patch which we sent to our second device and tap the play button at the right side . After the command has succeeded we have have to reboot our fastboot phone after removing data cable and otg . After rebooting just open root checker application and keep internet on , Click on verify root. Your phone is rooted now.
Now do whatever you want to do
Fun fact :- this method works on every phone
Those who want to say me thanks for this method please reply me
Hello Everyone,
I have an SM-T860 WiFi, with the stock T860XXU3BTJ2 update. I was able to root it with Magisk. When I initially opened Magisk, it needed to reboot to complete the rooting. I then installed a few apps, and got prompted for root. I approved it, and was able to browse root.
Usually I will go for an AOSP rom, but I was considering the idea of just removing the APK's I don't want (Google, Samsung), and replace them with alternatives.
I tried a few different things, but *it appears that* every time I modify the /system/app-priv folder, and I reboot, my Magisk changes to "NA"! For some reason, reflashing the Magisk_modified file I made in Odin doesn't return root to the device.
At one point, I used Material File manager to mount the root directory as read/write, so I could delete the APKs. I assume flashing the CSC file will mean the / mountpoint will mount as read only, moving forward.
I also downloaded and used the debloat Magisk Module. It appeared to complete successfully, but I have the same Magisk problem when I reboot.
Here's how i flash the Odin Image:
1. Downloaded the firmware with Frija (Really amazing app after first trying Sammobile).
2. Modified it on the tablet with Magisk Manager, copied it back off the device.
3. Flashed Device with BL, Modified Magisk AP, and no CSC (without the "HOME" option) (My understanding is this will delete all data on the device).
4. After Odin finishes, I immediately hold Volume + and Bixby. I immediately get to the recovery, and run a factory reset.
5. Go through initial setup
6. Use ADB to install Magisk Manager apk to Device
7. Upon opening Magisk Manager, it doesn't prompt me to reboot and complete installation (like I saw before), it just says "N/A".
I appreciate your help!
edit-- I ran ls -la on / with adb, and got the line below, so I think that confirms we are read only.
drwxr-xr-x 22 root root 4096 2008-12-31 09:00 system
hello,
how did you root it?!
stock T860XXU3BTJ2 for me it dont work?
STANDARD DISCLAIMER: I am not responsible for any damages caused to your phone. Use this mod at your own risk there is no warranty or guarantee.
This is a Magisk Module t to disable find my device account administrator. You should also manually turn off find my device on your phone. The script runs on boot and then exits out of memory. Taking up no cpu power or ram in the background.
I have updated the Magisk Module to work with Magisk 20.4 or higher.
How to install?
Just flash in Magisk.
Requirements:
Root
Magisk v20.4 or higher
Delete manual install before installing the Magisk Module "/data/adb/service.d/disablefindmydevice.sh"
Manual Install, unzip and take the service.sh file and rename it and copy it to "/data/adb/service.d/" and change file permissions to 0755 reboot.
You may not need root, you can just enter the adb command.
adb shell pm disable com.google.android.gms/com.google.android.gms.mdm.receivers.MdmDeviceAdminReceiver
Darnrain1 said:
Hello all I made a shell script to disable find my phone at login. I don't use it and it just takes up memory. I have an Lg v20 but this should work on any android phone.
You have to have root access also must have Magisk. You need a file manager I recommend Root Explorer or Solid Explorer
Place shell Script in
/data/adb/service.d
Change attributes to 755
Enjoy....
Click to expand...
Click to collapse
Your script says
#!/system/bin/sh
sleep 100
pm disable com.google.android.gms/com.google.android.gms.mdm.receivers.MdmDeviceAdminReceiver
Click to expand...
Click to collapse
pm disable works perfectly fine without root if you use adb.
You won't need root, Magisk or any root file manager.
User699 said:
Your script says
pm disable works perfectly fine without root if you use adb.
You won't need root, Magisk or any root file manager.
Click to expand...
Click to collapse
Yes that is true but you would not be able to make it persistent across reboots.
Darnrain1 said:
Yes that is true but you would not be able to make it persistent across reboots.
Click to expand...
Click to collapse
Oh, I see. On my Xiaomi, stock Android 10 it was persistent, but maybe that's different with lg.
I have the lgv20 and when I used pm disable it always comes back when i restarted the phone. I am happy it worked for you. thank you for letting me know some may not need root to make this tweak work.
updated magisk script