Related
Hi,
I'm rooted with the stock ROM but having some trouble installing busybox using the installer from the play store.
Using the 'normal' installation method it tells me if failed for an unknown reason or reboots the phone.
Any ideas?
Download root checker and verify that you have root
If you do, try another app, if not, you can always download the busybox binary yourself and install it :good:
Root verified, other root apps work fine also. Will try another busy box method
None of the installers seem to work, should I be pushing to /system/bin correct?
are you on the 1.27 stock rom? zhis rom is odexed and i got the same problem. after installing a deodexed rom with 1.28 i was able to install it
Stock 1.28 - Odexed
i think the odexed is the problem
Yeah, push to /system/bin
Then run (in a terminal / shell)
Code:
busybox install ./
CNexus said:
Yeah, push to /system/bin
Then run (in a terminal / shell)
Code:
busybox install ./
Click to expand...
Click to collapse
or install in recovery... that works for me!
snoozor said:
or install in recovery... that works for me!
Click to expand...
Click to collapse
Might be a dumb ass question here but I can't find flashable zip file to install Busybox through recovery, anyone got a link or tell me where I can find one?
Thanks.
I don't seem to have mount system as RW as well. I'm rooted with dual recoveries installed.
Thanks.
timvonlee said:
I don't seem to have mount system as RW as well. I'm rooted with dual recoveries installed.
Thanks.
Click to expand...
Click to collapse
hi, xposed working fine on my z1 with latest 14.6.A.1.236 firmware , current i use xposed-v78-sdk22-arm version and XposedInstaller_3.0_alpha4.apk from here
Problem your phone cant mount as RW, try reinstall pre-root , follow this step.
1. Flash Pre-root.zip
2. flash Dual recovery, (i use Z1-lockeddualrecovery2.8,23-released.combine.zip)
3. Flash Update-SuperSU-V2.46.zip
4. Reboot - Done
after boot you can check whether your phone can mount system as RW , if everything okey, you can flash xposed and install xposed module without problem.
Hope its help..
iedafarha said:
hi, xposed working fine on my z1 with latest 14.6.A.1.236 firmware , current i use xposed-v78-sdk22-arm version and XposedInstaller_3.0_alpha4.apk from here
Problem your phone cant mount as RW, try reinstall pre-root , follow this step.
1. Flash Pre-root.zip
2. flash Dual recovery, (i use Z1-lockeddualrecovery2.8,23-released.combine.zip)
3. Flash Update-SuperSU-V2.46.zip
4. Reboot - Done
after boot you can check whether your phone can mount system as RW , if everything okey, you can flash xposed and install xposed module without problem.
Hope its help..
Click to expand...
Click to collapse
Did you deodex?
timvonlee said:
Did you deodex?
Click to expand...
Click to collapse
no , i run odex rom, just certain apk and framwwork use deodex file, like service.jar (superusermod) , Settings.apk and systemUI.apk
to prevent bootloop , try debloat your rom , u can manually remove blaotware using file manager rootxplorer or using flashable script here
iedafarha said:
no , i run odex rom, just certain apk and framwwork use deodex file, like service.jar (superusermod) , Settings.apk and systemUI.apk
to prevent bootloop , try debloat your rom , u can manually remove blaotware using file manager rootxplorer or using flashable script here
Click to expand...
Click to collapse
Worked but this is how...
Clean install and used xposed from this post. http://forum.xda-developers.com/showpost.php?p=64231801&postcount=2
Its version 75.
iedafarha said:
hi, xposed working fine on my z1 with latest 14.6.A.1.236 firmware , current i use xposed-v78-sdk22-arm version and XposedInstaller_3.0_alpha4.apk from here
Problem your phone cant mount as RW, try reinstall pre-root , follow this step.
1. Flash Pre-root.zip
2. flash Dual recovery, (i use Z1-lockeddualrecovery2.8,23-released.combine.zip)
3. Flash Update-SuperSU-V2.46.zip
4. Reboot - Done
after boot you can check whether your phone can mount system as RW , if everything okey, you can flash xposed and install xposed module without problem.
Hope its help..
Click to expand...
Click to collapse
guys to you with mount problems you have either to put this on prf creator either unzip the zip and run the script!
http://nut.xperia-files.com/?ql=8eaa3680cad126279a904a0c4bc68109ba7c3b28
Στάλθηκε από το SM-T310 μου χρησιμοποιώντας Tapatalk
kos25k said:
guys to you with mount problems you have either to put this on prf creator either unzip the zip and run the script!
http://nut.xperia-files.com/?ql=8eaa3680cad126279a904a0c4bc68109ba7c3b28
Στάλθηκε από το SM-T310 μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
I tried to flash this via recovery and still can't mount system as rw. I suppose the only wat to apply this would be running the script thru PC? I'm really desperate to mount the system as rw on my Z1....
Thanks in advance!
CoolJandee said:
I tried to flash this via recovery and still can't mount system as rw. I suppose the only wat to apply this would be running the script thru PC? I'm really desperate to mount the system as rw on my Z1....
Thanks in advance!
Click to expand...
Click to collapse
It's a flashable zip. Just use dual recovery to flash it on your phone.
motorazrv3 said:
It's a flashable zip. Just use dual recovery to flash it on your phone.
Click to expand...
Click to collapse
Yea I flashed it first. Also tried to run the script via PC. No luck on mounting /system as RW. Any ways you could suggest? I'm running on the latest firmware for Z1 with root and NUT's dualrecovery.
Thanks again
Quick summary, I can not:
mount -o remount,rw /system in normal mode even with root permission. Error is "Device busy"
modify files in /system in twrp and keep it persistent. It somehow roll back to the stock state after reboot into normal mode.
I'm a long-time linux user, and fairly familiar with rooting in pre-nougat versions. My previous phone is Oneplus-X in LineageOS-14, and I could do whatever I like with the system partition. Recently I received a P9 as present. I updated the rom to B377 and flashed OldDroid's TWRP-3.1.0+phh su. But I can not find a way to modify the /system partition. I need to change a lot of things, like /system/etc/hosts, adding apk into /system/priv-app, etc.
Could someone help?
ccaappton said:
Quick summary, I can not:
mount -o remount,rw /system in normal mode even with root permission. Error is "Device busy"
modify files in /system in twrp and keep it persistent. It somehow roll back to the stock state after reboot into normal mode.
I'm a long-time linux user, and fairly familiar with rooting in pre-nougat versions. My previous phone is Oneplus-X in LineageOS-14, and I could do whatever I like with the system partition. Recently I received a P9 as present. I updated the rom to B377 and flashed OldDroid's TWRP-3.1.0+phh su. But I can not find a way to modify the /system partition. I need to change a lot of things, like /system/etc/hosts, adding apk into /system/priv-app, etc.
Could someone help?
Click to expand...
Click to collapse
Hopefully this might help:
1. revert back to unmodified boot image (in TWRP flash from here[/URL or restore your backup from the unmodified boot image] , leave anything else untouched (especially TWRP 3.1.0-0 for EMUI 5)
2. flash this [URL="https://forum.xda-developers.com/showpost.php?p=71588837&postcount=102"]SuperSU image in TWRP (read the comments in the post please ... single bootloop ... then everything is ok and rooted)
3. install JRummy's BusyBox from Google Play (Stephen's won't work)
You are done and good to modify /system.
Note: resulting earthquakes, thunderstorms and spring floods from this work are solely under your own responsibility :laugh:
hakaz said:
Hopefully this might help:
1. revert back to unmodified boot image (in TWRP flash from here[/URL or restore your backup from the unmodified boot image] , leave anything else untouched (especially TWRP 3.1.0-0 for EMUI 5)
2. flash this [URL="https://forum.xda-developers.com/showpost.php?p=71588837&postcount=102"]SuperSU image in TWRP (read the comments in the post please ... single bootloop ... then everything is ok and rooted)
3. install JRummy's BusyBox from Google Play (Stephen's won't work)
You are done and good to modify /system.
Note: resulting earthquakes, thunderstorms and spring floods from this work are solely under your own responsibility :laugh:
Click to expand...
Click to collapse
1. I did a backup of boot partition before phh root, so should be able to restore the backup, instead of download the boot partition from others?
2. Is systemless supersu binaries need be individualized for every phone? Can I download systemless supersu from somewhere more semi-official? I'm not exactly comfortable installing zips from random links. ()
Ad 1. Till now rooting on our P9 works through injection of the su mounting routine into the kernel in boot section (if using a modified kernel + su installation or modifying the kernel during su installation itself doesn't make a difference). So any su installation modifies the boot section and you mess things up if you try to install another su on top of the other. Therefore reverting to the original boot image is mandatory before installation of another su.
Ad 2. The su is compiled against different platforms not phones (in our case arm64). So @Chainfire has the different platform variations in his package. The "shady" package in our case is basically the v2.79 stable version of 12/20 2016 (you can unpack both packages and compare them against each other, they are bit for bit equal) but has an P9 specific injection routine to modify the kernel. After installation you have pure su v2.79 stable on board - not more, not less.
Sorry, "normal" SuperSU packages won't work due to lacking the kernel modification (phh uses a modified kernel instead you have to flash separately on P9).
Cheers!
hakaz said:
Ad 1. Till now rooting on our P9 works through injection of the su mounting routine into the kernel in boot section (if using a modified kernel + su installation or modifying the kernel during su installation itself doesn't make a difference). So any su installation modifies the boot section and you mess things up if you try to install another su on top of the other. Therefore reverting to the original boot image is mandatory before installation of another su.
Ad 2. The su is compiled against different platforms not phones (in our case arm64). So @Chainfire has the different platform variations in his package. The "shady" package in our case is basically the v2.79 stable version of 12/20 2016 (you can unpack both packages and compare them against each other, they are bit for bit equal) but has an P9 specific injection routine to modify the kernel. After installation you have pure su v2.79 stable on board - not more, not less.
Sorry, "normal" SuperSU packages won't work due to lacking the kernel modification (phh uses a modified kernel instead you have to flash separately on P9).
Cheers!
Click to expand...
Click to collapse
Thanks buddy! I flashed systemless supersu, and stucked in infinite bootloop(it is only once in your post), probably because my model is EVA-AL00. I have to restore the previous boot.img.
ccaappton said:
Quick summary, I can not:
mount -o remount,rw /system in normal mode even with root permission. Error is "Device busy"
modify files in /system in twrp and keep it persistent. It somehow roll back to the stock state after reboot into normal mode.
I'm a long-time linux user, and fairly familiar with rooting in pre-nougat versions. My previous phone is Oneplus-X in LineageOS-14, and I could do whatever I like with the system partition. Recently I received a P9 as present. I updated the rom to B377 and flashed OldDroid's TWRP-3.1.0+phh su. But I can not find a way to modify the /system partition. I need to change a lot of things, like /system/etc/hosts, adding apk into /system/priv-app, etc.
Could someone help?
Click to expand...
Click to collapse
Same here with Oneplus 3T.
I just posted in another post (Google Pixel).
There I just guess it was a new encription way, now Im sure, all three devices with Android 7.1.1.....
Hi guys
if anyone is interested in testing out this boot image i created for my c636b172
removes all encrypt, perfect mounting options for all partitions (this took a while to figure since some caused bootloops)
also reduced voltages for wifi module (may be unstable, if anyone has problems let me know i can try and adjust, otherwise if im not getting problems ill just keep decreasing it)
how to install
1. make sure twp is installed
2. in data/dalvik-cache delete arm and arm64 folders.
3. boot into twrp > wipe cache and dalvik
4. flash the boot image in twrp (flash image select image flash to boot)
5. if you had su installed, flash the zip again
6. go to wipe cache and dalvik again (just in case)
7. reboot and enjoy, theoretically should be slightly faster, and less overhead.
Download
https://www.dropbox.com/s/msda9a3smy9lqb4/modBootv2.img?dl=0
if anyone has a request for their specific boot image let me know and ill add the same values.
Thank you for your work. Is this only for C636 devices or would this work on any device.
Could your reassemble it to add features like DT2W (doubletap to wake)?
audioralf said:
Thank you for your work. Is this only for C636 devices or would this work on any device.
Could your reassemble it to add features like DT2W (doubletap to wake)?
Click to expand...
Click to collapse
i think DT2W is disabled, no flags of it in the boot image, you can try this guide.
https://forum.xda-developers.com/mate-9/how-to/enable-double-tap-to-wake-mate-9-t3580764
the boot image is for the c636, im not sure if you can flash it on another base you can try just have a stock boot.img handy
or to be safe you can send me your boot.img and ill edit it the same.
Thank you for your friendly offer!
I am back on C432B156 with supersu modified boot. The original boot img linked here
https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
Mine is https://mega.nz/#!EABCVJwb!wopFOGqJzbpIX6edxM5Y9IVeZAIJ_CAJYUn3q4cc074
I recognized that I have no adb access in TWRP 3.02.2
I can not mount my pc connection. Would this be fixed?
Gesendet von meinem MHA-L29 mit Tapatalk
audioralf said:
Thank you for your friendly offer!
I am back on C432B156 with supersu modified boot. The original boot img linked here
https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
Mine is https://mega.nz/#!EABCVJwb!wopFOGqJzbpIX6edxM5Y9IVeZAIJ_CAJYUn3q4cc074
I recognized that I have no adb access in TWRP 3.02.2
I can not mount my pc connection. Would this be fixed?
Gesendet von meinem MHA-L29 mit Tapatalk
Click to expand...
Click to collapse
no, twrp 3022 doesnt have MTP access right now.
Thank you for the info.
Which advantage is on daily usage. I guess I would have to install supersu again, for it modifies the boot.
My device: Mate 9 supersu b156 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
Mount does work in 3.1.0. Though you have to tap on "Mount USB Storage", then unmount before it actually mounts..
ante0 said:
Mount does work in 3.1.0. Though you have to tap on "Mount USB Storage", then unmount before it actually mounts..
Click to expand...
Click to collapse
ill try this
always thought it didnt work since it worked fine in 303
Hi Virtyx,
I very appreciate your work, good hope to use,
but i have some not understand the installation in STEP 2 (in data/dalvik-cache delete arm and arm64 folders) what to do?
Hope you can help explain more STEP 2 detail.
I have L29-C636b172 and unlocked Bootloader.
A lot of Thanks.
xjeepnsk said:
Hi Virtyx,
I very appreciate your work, good hope to use,
but i have some not understand the installation in STEP 2 (in data/dalvik-cache delete arm and arm64 folders) what to do?
Hope you can help explain more STEP 2 detail.
I have L29-C636b172 and unlocked Bootloader.
A lot of Thanks.
Click to expand...
Click to collapse
Using a file Explorer with root support, navigate to /data/dalvik-cache and remove those 2 folders. Alternatively use a terminal app and 'rm -rf /data/dalvik-cache/arm*'.
I guess you could use the file manager or terminal in twrp.
ante0 said:
Using a file Explorer with root support, navigate to /data/dalvik-cache and remove those 2 folders. Alternatively use a terminal app and 'rm -rf /data/dalvik-cache/arm*'.
I guess you could use the file manager or terminal in twrp.
Click to expand...
Click to collapse
Hi ante0,
I succeeded, Thank you so much
Hello sir,
My mate 9 stuck in boot loop....
And I can't access to recovery too
Can u make scatter file for mate 9 to fix boot loop
(other thread here)
It seems that a Magisk module that I have recent installed (no idea which one) is preventing my phone to boot correctly. I know that because reflashing the latest OTA update removes Magisk and then it works perfectly. As soon as I flash Magisk, it doesn't boot anymore.
Even after flashing SuperSU, Magisk Manager doesn't let me see/remove installed modules.
Is there a way to do that?
zdimension said:
(other thread here)
It seems that a Magisk module that I have recent installed (no idea which one) is preventing my phone to boot correctly. I know that because reflashing the latest OTA update removes Magisk and then it works perfectly. As soon as I flash Magisk, it doesn't boot anymore.
Even after flashing SuperSU, Magisk Manager doesn't let me see/remove installed modules.
Is there a way to do that?
Click to expand...
Click to collapse
Use mount-magisk.zip found in collection of modules thread and delete the folder via twrp in /magisk
@duxishere Thanks so much!
I searched for "Magisk module offline uninstall" but did find anything. This was exactly what I needed! The culprit was App Systemizer. I've had it installed for some time and it didn't cause any problems. I uninstalled it, and it worked! Flashing it again restored the boot problem.
zdimension said:
@duxishere Thanks so much!
I searched for "Magisk module offline uninstall" but did find anything. This was exactly what I needed! The culprit was App Systemizer. I've had it installed for some time and it didn't cause any problems. I uninstalled it, and it worked! Flashing it again restored the boot problem.
Click to expand...
Click to collapse
How did you uninstalled the troubled module?
I'm having the same problem with a module but I don't even have a /magisk folder.
gonsa said:
How did you uninstalled the troubled module?
I'm having the same problem with a module but I don't even have a /magisk folder.
Click to expand...
Click to collapse
Start reading the thread from the beginning and you'll find it.
gonsa said:
How did you uninstalled the troubled module?
I'm having the same problem with a module but I don't even have a /magisk folder.
Click to expand...
Click to collapse
Install "Uninstaller Mod Magisk" from TWRP. Then go in the TWRP terminal and type uninmod_magisk and follow the instructions.
please post the link to thread unistaller magisk module, to other users follow the solution!
edit:
there is https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
nodio said:
please post the link to thread unistaller magisk module, to other users follow the solution!
edit:
there is https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
Click to expand...
Click to collapse
Not working for me!
I will uninstall "Audio Compatibility Patch" V1.0 from zackptg5 & ahrion
In Magisk Manger Status is always " Module will be updated at the next start"
If i use the "TWRP-Uninstaller" the Modul is not in List!
dewois said:
Not working for me!
I will uninstall "Audio Compatibility Pach" V1.0 from zackptg5 & ahrion
In Magisk Manger Status is always " Module will be updated at the next start"
If i use the "TWRP-Uninstaller" the Modul is not in List!
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/Magisk#hn_Module_will_be_updated_at_next_reboot
Didgeridoohan said:
https://www.didgeridoohan.com/magisk/Magisk#hn_Module_will_be_updated_at_next_reboot
Click to expand...
Click to collapse
".... Go the module folder under /sbin/.core/img ..."
I dont have this folder in /sbin!
tobi14 said:
".... Go the module folder under /sbin/.core/img ..."
I dont have this folder in /sbin!
Click to expand...
Click to collapse
If you have a current version of Magisk installed, yes you do. Enable viewing hidden files and folders in your file explorer. The dot at the beginning of the folder name means it's hidden...
zdimension said:
(other thread here)
It seems that a Magisk module that I have recent installed (no idea which one) is preventing my phone to boot correctly. I know that because reflashing the latest OTA update removes Magisk and then it works perfectly. As soon as I flash Magisk, it doesn't boot anymore.
Even after flashing SuperSU, Magisk Manager doesn't let me see/remove installed modules.
Is there a way to do that?
Click to expand...
Click to collapse
If you can launch TWRP then :
Check magisk.img exist
1. Go to "advanced" and then click on "File Explorer".
2. Check there is "magisk.img" file under "/data"
Backup magisk.img
1. Go to "advanced" and then click on "terminal command".
2. type following command
Code:
cp /data/magisk.img /data/magisk.img.bk
Mount magisk.img
1. Make a temp folder
Code:
mkdir /mktmp
2. Mount magisk.img to /mktmp
Code:
mount -o loop /data/magisk.img /mktmp
3. Navigate to mktmp and remove your module
Code:
cd /mktmp
rm -rf /mktmp/xxxx
Unmount magisk.img and reboot to check if it's work
1. Unmount magisk.img
Code:
umont /mktmp
2. Leave terminal and reboot the phone
3. Enjoy!
mklee11224 said:
If you can launch TWRP then :
Check magisk.img exist
1. Go to "advanced" and then click on "File Explorer".
2. Check there is "magisk.img" file under "/data"
Backup magisk.img
1. Go to "advanced" and then click on "terminal command".
2. type following command
Code:
cp /data/magisk.img /data/magisk.img.bk
Mount magisk.img
1. Make a temp folder
Code:
mkdir /mktmp
2. Mount magisk.img to /mktmp
Code:
mount -o loop /data/magisk.img /mktmp
3. Navigate to mktmp and remove your module
Code:
cd /mktmp
rm -rf /mktmp/xxxx
Unmount magisk.img and reboot to check if it's work
1. Unmount magisk.img
Code:
umont /mktmp
2. Leave terminal and reboot the phone
3. Enjoy!
Click to expand...
Click to collapse
Thanks mate ! it worked like a charm !
just use "ls" command on step 3 after changing directory to mktmp , to show installed modules.:silly:
My Phone Specification : Moto X Play ------ 7.1.1 Stock Firmware -------- Squid kernel --------- rooted using Magisk ------ systemless xposed module "xposed_25" installed using magisk module(Uninstalled by this method !) .:victory:
Tanks a lot!
Crossbreeder lite made my phone unusable. Working fine again!
magisk.img not found in /data
This works like charm, if you can't find the magisk.img in `/data` check `/data/adb` ... I hope this work .
Didgeridoohan said:
https://www.didgeridoohan.com/magisk/Magisk#hn_Module_will_be_updated_at_next_reboot
Click to expand...
Click to collapse
Own domain huh? Business growing? Hehehe I only came for the uninstall zip, hey quick question, I'm on a micro sd-less phone (big news), still a flashaholic, kinda, but my phone so happens to require a data format every time for gsi's, where would you recommend keeping the "things to keep on your device" (Magisk related) so i don't have to carry an otg and drive everywhere i go? Thank you sir, you almost get more thanks than posts! Talk about reputation!
culiacanazo said:
Own domain huh?
Click to expand...
Click to collapse
I keep a few of them around. It was nice to finally find a good use for that one...
but my phone so happens to require a data format every time for gsi's, where would you recommend keeping the "things to keep on your device" (Magisk related) so i don't have to carry an otg and drive everywhere i go?
Click to expand...
Click to collapse
Do you have to completely wipe the device? Or can you keep internal storage intact? If not, it sounds like you're out of luck.
Nice thread hijack, by the way... :laugh:
Didgeridoohan said:
Do you have to completely wipe the device?
Click to expand...
Click to collapse
Well i do a factory reset, flash system img and reboot, let it loop because it will, and then do a data format before it will boot, so system, caches, and data go... (Huawei, see)
Didgeridoohan said:
Nice thread hijack, by the way... :laugh:
Click to expand...
Click to collapse
I kinda stayed on topic didn't i? :crying:
You linked to your help guide which i read the beginning of that by the way has nothing to do with the help you offered to the op and reminded me of my struggles with a totally different device and problem!!
It's like how I'm related to my grandma's cousin's wife's sister's doctor's neighbor's son's friend, ain't it?
Sent from my Huawei Mate 10 Pro using XDA Labs
Would be cool if someone could share the adb solution. In the FAQ is just written "email me for this" wtf?!? It is ****ing anoying to reflash the whole system everytime a module isnt working (yeah thats what you need to do if your device doesnt have twrp, and a lot of a/b devices dont have twrp). Also you need to delete all user datas because you flashed the system new and the new system doesnt know the encryption key for the user datas. There need to be a better solution than using twrp or email the dev for adb solution.
The easiest way would be to make it possible that magisk manager can manage (remove/deactivate) the modules while there is no patched boot.img installed. This would solve all problems related to a/b devices without twrp and magisk modules (not booting or anything else) just flash stock boot.img remove the problematic module flash patched boot.img and done. This is not possible because the module section in magisk manager is hidden when there is no patched boot.img installed.
Second thing i noticed, magisk manager doesnt reset the active modules when you wipe the app data. This should be a MUST. Would also solve the problem of not booting modules without wiping the whole system on a/b devices without twrp.
Apply .disable_magisk
saturday_night said:
Would be cool if someone could share the adb solution. In the FAQ is just written "email me for this" wtf?!? It is ****ing anoying to reflash the whole system everytime a module isnt working (yeah thats what you need to do if your device doesnt have twrp, and a lot of a/b devices dont have twrp). Also you need to delete all user datas because you flashed the system new and the new system doesnt know the encryption key for the user datas. There need to be a better solution than using twrp or email the dev for adb solution.
The easiest way would be to make it possible that magisk manager can manage (remove/deactivate) the modules while there is no patched boot.img installed. This would solve all problems related to a/b devices without twrp and magisk modules (not booting or anything else) just flash stock boot.img remove the problematic module flash patched boot.img and done. This is not possible because the module section in magisk manager is hidden when there is no patched boot.img installed.
Second thing i noticed, magisk manager doesnt reset the active modules when you wipe the app data. This should be a MUST. Would also solve the problem of not booting modules without wiping the whole system on a/b devices without twrp.
Click to expand...
Click to collapse
Hi!. I have this user of XDA Dev. hanging out for a time... well the fact is I'm new. My problem (not the only one) maybe merge a kind of solution to this. And this could be putting the ".disable_magisk" blank file inside the cache partition as an ADB Sideload update.
Next to this. I've found that to do that it's not as simply as it seems to be cause I'm on a Samsung Galaxy S7 Nougat 7.0 Version. And all the examples with update-binary file I have, are from downgrade versions...
I'm stuck in a bootloop due to the Magisk Xposed SDK 24 module. I think this module & encription is not good (as I've read on the Xpose module thread).
So, here I'm asking how to make an script to run directly on the Stock recovery using ADB Sideload, which will put the blank ".disable_magisk" file inside the /cache partition. I need just this, and I think this could help some people who are stuck on this issue.
Now, I have this Thread. But really I need the advice of an expert telling me what to do in order to achieve this. As I think this is an easy labor, but you have to know how to do it... If someone is able to clarify please, I will appreciate so much.
Thanks!
---------- Post added at 05:51 PM ---------- Previous post was at 05:41 PM ----------
neromanello said:
Hi!. I have this user of XDA Dev. hanging out for a time... well the fact is I'm new. My problem (not the only one) maybe merge a kind of solution to this. And this could be putting the ".disable_magisk" blank file inside the cache partition as an ADB Sideload update.
Next to this. I've found that to do that it's not as simply as it seems to be cause I'm on a Samsung Galaxy S7 Nougat 7.0 Version. And all the examples with update-binary file I have, are from downgrade versions...
I'm stuck in a bootloop due to the Magisk Xposed SDK 24 module. I think this module & encription is not good (as I've read on the Xpose module thread).
So, here I'm asking how to make an script to run directly on the Stock recovery using ADB Sideload, which will put the blank ".disable_magisk" file inside the /cache partition. I need just this, and I think this could help some people who are stuck on this issue.
Now, I have this Thread. But really I need the advice of an expert telling me what to do in order to achieve this. As I think this is an easy labor, but you have to know how to do it... If someone is able to clarify please, I will appreciate so much.
Thanks!
Click to expand...
Click to collapse
I need to know how to locate the mount point of my /cache partition at the stock recovery ADB Sideload. Then, to mount it, transfer the blank file to it, and then unmount /cache. I think it's an easy labor. So here my incomplete updater-script:
ui_print("Trying to make an script with ADB Sideload..."); CRLF
ui_print("Creating file to disable Magisk Modules..."); CRLF
I NEED THE MOUNT POINT HERE CRLF
ifelse package_extract_file(".disable_magisk", "/cache/.disable_magisk") == "t", ui_print("OK!"), ui_print("Failed!"); CRLF
UNMOUNT COMMAND HERE. CRLF
--last blank line--
So, I need to complete that, BUT things gets difficult when I need the update-binary for my Nougat 7.0 version, and to sign the whole .zip file in order my stock recovery recognizes it. I think this last thing could be made by this Thread. But really I don't know. Please help.
Thanks!.