Related
Hi guys, please direct me to the correct place if this is not it. I am currently running revolt and I want to flash a new ROM. I had a status 7 error, which I have had before and I fixed that by updating CWM. But here is where I get hung up. I get an error that I thought was related to ROM manager not having the correct permissions. I went to update my supersu and give it the correct permissions, but I decided I wanted to change to Superuser and uninstalled supersu. I have now having an error where I can not download anything from he play store because my memory is full. When I check my memory it does not add up. I have 12gb of space and a I am using roughly 4 gb of that. If anyone knows of a way that I can fix the issue so that I can update my CWM and flash a new ROM it will be greatly appreciated!
Did you have the same error before changing your root managing app? You went from superuser to supersu
Sent from my ST18i
Guynan said:
Did you have the same error before changing your root managing app? You went from superuser to supersu
Sent from my ST18i
Click to expand...
Click to collapse
I tried to change from supersu to superuser and I can't download superuser because it says my memory is full.
eviltweak said:
I tried to change from supersu to superuser and I can't download superuser because it says my memory is full.
Click to expand...
Click to collapse
That is really confusing. When it says wrong permissions, it won't mean the root managing app has the wrong permissions, it means that the system has wrong permissions somewhere. This cannot be fixed through Supersu or Superuser. If you can still go into recovery, go into advanced, and then 'fix permissions' and that should fix issues if that is what it pertains to.
Because Android it is based off a Linux kernel, it is very picky with the permissions you give it. Too little and it doesn't work. Too much, and it doesn't work.
Let me know how you go.
I don't think I explained this very well in my first post. My issue lies when I try to flash the new version of cwm. I get this screen.
I went into recovery and advanced and I don't have an option that is fix permissions?
So you do have a current working recovery? Okay then advanced>Fix Permissions, at the bottom. If it isn't there, it might be the stock recovery included by Samsung. What is wrong with your current recovery? I can't seem to figure it out sorry.
Guynan said:
So you do have a current working recovery? Okay then advanced>Fix Permissions, at the bottom. If it isn't there, it might be the stock recovery included by Samsung. What is wrong with your current recovery? I can't seem to figure it out sorry.
Click to expand...
Click to collapse
I am running CMW 6.0.3.7. When I go to advanced all that I see is Reboot recovery, Reboot to bootloader, Power Off, Wipe Dalvik Cache, Report Error, Key Test, Show Log, *******Go back*******.
My recovery works, its just not up to date so when I go to flash a new ROM I get a status 7 error. I have had this issue before and I fixed it by updating my recovery. BUT this time when I go to flash an updated version of CWM I get the screen that I posted above.
the status seven error is usually to do with the updater-script. So make sure the ROM you want to flash is for your device, if it isn't (which may be why you have run into issues) don't flash it. But if you are sure it is, go into the ROM, META-INF>Android>Google>Updater-script (the android and google may be the other way round, it won't take you long to find it) And then open the updater script in a text editing program and remove the first few lines of stuff. It will have the words "assert" "getprop" and looks different to the rest, so just delete that section, and rezip if you have to, and try reflashing. But if that doesn't work and the issues are becoming intrusive, a full reset might be in order.
Update (May 20): Update to latest version 2.74-2
All versions after SuperSU 2.72 has force encrypt support built in. However it will still disable force encryption by default, you have to set flags manually.
I only modified the default value of the force encrypt flag in the flashing script, so no need to worry that this might break things
If your OCD forces you to use the official version, please look here for instructions to set the flag manually by yourself.
Hi, many people have their hands on the HTC 10, and you may found out that wiping data after rooted with SuperSU, your signal will be broken.
This is caused by the fact that by default, SuperSU's flashing script will change the data encryption flag from "forceencrypt" to "encryptable". If you wiped data after the flag is set to "encryptable", your data partition will be decrypted. In many times, decrypted data is good, but on the HTC 10, for some unknown reason the signal will break with data decrypted.
More info here:
[PSA][MUST SEE] New HTC Policy : Things You Should Know Before Unlocking Bootloader
This issue has caught more attention after an S-OFF method is available. You're required to have root and wipe data after gaining S-OFF. The developer of the S-OFF tool has created a tutorial for this particular problem, you can find it here:
[Guide] Root (Optionally s-off) and Keep your radio working
I slightly modified the SuperSU flashing script, so now it won't change the encryption flag.
This zip will remain useful until we find a way to decrypt our data partition with working signal.
Hi,
this works without problems, big tanks. Device is rooted now.
regards
starbase64
Big thanks. I wish I would have had this yesterday afternoon!
Now I just need to get a stock 1.21.617.3 image to start again with my US unlocked. If anyone has it, please let me know.
Is there a way to manually change the flag back to forceencrypt?
MNoisy said:
Big thanks. I wish I would have had this yesterday afternoon!
Now I just need to get a stock 1.21.617.3 image to start again with my US unlocked. If anyone has it, please let me know.
Is there a way to manually change the flag back to forceencrypt?
Click to expand...
Click to collapse
I have TWRP images for system_image and boot if you need them to fix broken signal as per @jcase. We're both 1.21.617.3
datafoo said:
I have TWRP images for system_image and boot if you need them to fix broken signal as per @jcase. We're both 1.21.617.3
Click to expand...
Click to collapse
Yes yes yes please! THANK YOU!
Where can I find them?
Nice buddy, will update the method used in my build, makes life a lot easier.
I had considered making similar modifications but you appear to have beaten me too it
topjohnwu said:
Hi, many people have their hands on the HTC 10, and you may found out that wiping data after rooted with SuperSU, your signal will be broken.
This is caused by the fact that by default, SuperSU's flashing script will change the data encryption flag from "forceencrypt" to "encryptable". If you wiped data after the flag is set to "encryptable", your data partition will be decrypted. In many times, decrypted data is good, but on the HTC 10, for some unknown reason the signal will break with data decrypted.
More info here:
[PSA][MUST SEE] New HTC Policy : Things You Should Know Before Unlocking Bootloader
This issue has caught more attention after an S-OFF method is available. You're required to have root and wipe data after gaining S-OFF. The developer of the S-OFF tool has created a tutorial for this particular problem, you can find it here:
[Guide] Root (Optionally s-off) and Keep your radio working
Here I come up with a more elegant solution. I slightly modified the SuperSU flashing script, so now it won't change the encryption flag, and also won't remove dm-verify.
NOTE: If your boot image is already modified, it will not reset the flag back to forceencrypt. You have to restore to the stock boot image, then flash this zip. The way I accomplished this is reverting a few modification from the previous ramdisk, so the ramdisk itself has to be stock.
Devs can include this zip into their rom, so users can wipe their whole data with your rom installed.
This zip will be useful until we find a way to decrypt our data partition with working signal.
Click to expand...
Click to collapse
I would NOT use this zip to root the HTC 10, you really need to remove verity, this is going to cause many many many issues, its going to softbrick a huge number of phones, anything from a lot of root apps, to restoring a twrp backup is going to trip dm-verity
SuperSU v2.72 has all of this built in via KEEPVERITY and KEEPFORCEENCRYPT flags. It's not publicly released yet but will be within a few days.
Chainfire said:
SuperSU v2.72 has all of this built in via KEEPVERITY and KEEPFORCEENCRYPT flags. It's not publicly released yet but will be within a few days.
Click to expand...
Click to collapse
Out of curiosity, where will we put those flags? /data/.supersu isn't an option, because /data is encrypted and unmountable, and /system/.supersu isn't an option if /system is read-only and we want to preserve dm-verity.
jcase said:
I would NOT use this zip to root the HTC 10, you really need to remove verity, this is going to cause many many many issues, its going to softbrick a huge number of phones, anything from a lot of root apps, to restoring a twrp backup is going to trip dm-verity
Click to expand...
Click to collapse
My system is modified, but everything is working fine. I'm using this without a problem so I shared it.
Is it because my device is S-OFF? If this is the case, then I'll remove the link. Thanks for the kind remind.
topjohnwu said:
My system is modified, but everything is working fine. I'm using this without a problem so I shared it.
Is it because my device is S-OFF? If this is the case, then I'll remove the link. Thanks for the kind remind.
Click to expand...
Click to collapse
I'd have to look at the zip and test to see why. It could be that your particular firmware isn't actually enforcing dm-verity (I believe google mandates this on 6.0+), that HTC disables enforcing when s-off or the zip isn't properly enforcing verity.
Best advice is not to enforce verity on system if you are rooted.
What should (and did for my phone) happen if you have dm-verity enabled on system and a modified system is the phone shouldn't successfully boot.
Captain_Throwback said:
Out of curiosity, where will we put those flags? /data/.supersu isn't an option, because /data is encrypted and unmountable, and /system/.supersu isn't an option if /system is read-only and we want to preserve dm-verity.
Click to expand...
Click to collapse
I've added /cache/.supersu as location specifically for those devices with a TWRP that can't read encrypted /data.
Still, you can echo to /data/.supersu even if /data isn't mounted and that'll still work. It just will not persist between boots.
Custom ROM devs should put it in /system/.supersu, though, or set the variable in shell and export that variable (important!) before running the SuperSU ZIP.
Chainfire said:
I've added /cache/.supersu as location specifically for those devices with a TWRP that can't read encrypted /data.
Still, you can echo to /data/.supersu even if /data isn't mounted and that'll still work. It just will not persist between boots.
Custom ROM devs should put it in /system/.supersu, though, or set the variable in shell and export that variable (important!) before running the SuperSU ZIP.
Click to expand...
Click to collapse
Will that cause complications for users who wipe cache often?
Sorry everyone, didn't though much about the dm_verity.
Re-uploaded one with dm_verity removed.
Everyone should re-flash this zip if you've used the old one, thanks a lot.
@LeeDroid, could you please test if this works on your rom?
topjohnwu said:
Sorry everyone, didn't though much about the dm_verity.
Re-uploaded one with dm_verity removed.
Everyone should re-flash this zip if you've used the old one, thanks a lot.
@LeeDroid, could you please test if this works on your rom?
Click to expand...
Click to collapse
Will have a bash tonight mate
topjohnwu said:
Sorry everyone, didn't though much about the dm_verity.
Re-uploaded one with dm_verity removed.
Everyone should re-flash this zip if you've used the old one, thanks a lot.
@LeeDroid, could you please test if this works on your rom?
Click to expand...
Click to collapse
still no go on boot
LeeDroid said:
still no go on boot
Click to expand...
Click to collapse
Yeah... Just tested myself and it won't boot.
It's weird though, it can boot on my modified system
I might need more investigation, or just wait for Chainfire to release the new update.
Is it OK to use SYSTEMLESS with your current build?
Thanks
ah, perhaps encountered a blarf
you wanna stick with blarp ... he's much nicer
topjohnwu said:
Yeah... Just tested myself and it won't boot.
It's weird though, it can boot on my modified system
I might need more investigation, or just wait for Chainfire to release the new update.
Click to expand...
Click to collapse
Ahh, I knew why.
I cannot separate the forceencrypt flag patch and verify flag by modifying the script.
Had to wait for Chainfire to release new version, or we have to manually modify the boot image.
As title says, anyone get viper4android installed and working with the OP3 and OOS 3.1.3?
I keep getting crashes and system lock ups after flashing Viper4Android 5.4 stock. I soft bricked it once and had to flash stock once when my prior Nandroid Backup failed. So hopefully someone gotten it to work.
vision33r said:
I keep getting crashes and system lock ups after flashing Viper4Android 5.4 stock. I soft bricked it once and had to flash stock once when my prior Nandroid Backup failed. So hopefully someone gotten it to work.
Click to expand...
Click to collapse
Yeah, same here. I am playing with it now. Not sure if I will figure anything out...
vision33r said:
I keep getting crashes and system lock ups after flashing Viper4Android 5.4 stock. I soft bricked it once and had to flash stock once when my prior Nandroid Backup failed. So hopefully someone gotten it to work.
Click to expand...
Click to collapse
Can you try this (I am not available to test it right now). Install Busy Box (https://play.google.com/store/apps/details?id=ru.meefik.busybox&hl=fi) and ensure that you install Busy Box via the app. Then flash the attached zip. It *should* work...
dustintinsley said:
Can you try this (I am not available to test it right now). Install Busy Box (https://play.google.com/store/apps/details?id=ru.meefik.busybox&hl=fi) and ensure that you install Busy Box via the app. Then flash the attached zip. It *should* work...
Click to expand...
Click to collapse
I just tried, my phone rebooted 30 seconds after the boot.
I could go into Viper and it wasn't working, still "abnormal".
All the applications that use the audio are now lagging and FCing...
Audio doesn't work anymore , I restore my backup ^^
Letin69 said:
I just tried, my phone rebooted 30 seconds after the boot.
I could go into Viper and it wasn't working, still "abnormal".
All the applications that use the audio are now lagging and FCing...
Audio doesn't work anymore , I restore my backup ^^
Click to expand...
Click to collapse
Well that stinks. I will keep playing around with it once I get home...
dustintinsley said:
Well that stinks. I will keep playing around with it once I get home...
Click to expand...
Click to collapse
Okay, tell me if you want that I test it
Letin69 said:
Okay, tell me if you want that I test it
Click to expand...
Click to collapse
Found a missing file, maybe this will work if you can test
I had bootloop by flashing V4A.zip...tried to install V4A.apk along with viper fix.apk and works flawlessly
I'll definitely try it out tomorrow. Done wiping my phone over and over. Did Nandroid backup twice and both restores failed. There's something about the Oxygen OS that is checking and is not backed up. Flashing the stock rom fixes it but loses root.
I did have BusyBox installed when I flashed V4A 5.4 stock and boot looped. I will try the V4A fix. The only thing is that if you flash V4A.zip, it causes the phone to become unstable.
Do I flash the V4A Fix after V4A.zip or boot into rom then apply the apk??
hunhool said:
I had bootloop by flashing V4A.zip...tried to install V4A.apk along with viper fix.apk and works flawlessly
Click to expand...
Click to collapse
Where is this v4a fix? can you post it here?
http://forum.xda-developers.com/showthread.php?t=3403304
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
vision33r said:
I'll definitely try it out tomorrow. Done wiping my phone over and over. Did Nandroid backup twice and both restores failed. There's something about the Oxygen OS that is checking and is not backed up. Flashing the stock rom fixes it but loses root.
I did have BusyBox installed when I flashed V4A 5.4 stock and boot looped. I will try the V4A fix. The only thing is that if you flash V4A.zip, it causes the phone to become unstable.
Do I flash the V4A Fix after V4A.zip or boot into rom then apply the apk??
Click to expand...
Click to collapse
Letin69 said:
Okay, tell me if you want that I test it
Click to expand...
Click to collapse
One more test. Made a small change. Also, once you install, you will get the initial freeze after boot up. I got a prompt asking me to wait or stop process. i stopped the process. once system is somewhat stable, install the viper fix.apk, restart and let me know. it seems to be working on mine....
dustintinsley said:
One more test. Made a small change. Also, once you install, you will get the initial freeze after boot up. I got a prompt asking me to wait or stop process. i stopped the process. once system is somewhat stable, install the viper fix.apk, restart and let me know. it seems to be working on mine....
Click to expand...
Click to collapse
tested on mine. didn't work. Thanks for your effort to fix it for us, though.
OK, I got viper working just fine. At first I thought it was my SuperSU version, so I downgraded to 2.67 (which did fix my es file explorer root issue). However, the driver would never install. What did work, was my selinux mode. After changing to permissive, viper works perfectly. So this is an issue with the app itself. I'm sure there are other work arounds with enforced mode, but I don't care. Lol. Also, I simply installed the apk directly from vipers page, enabled the driver, reboot, and voila! No flashing anything, or messing with anything other than the selinux mode. And I am on stock oxygenOS
Viper apk: http://vipersaudio.com/swupdate/viper4android/download.html
Selinux mode changer: http://forum.xda-developers.com/showthread.php?t=2524485
js042507 said:
OK, I got viper working just fine. At first I thought it was my SuperSU version, so I downgraded to 2.67 (which did fix my es file explorer root issue). However, the driver would never install. What did work, was my selinux mode. After changing to permissive, viper works perfectly. So this is an issue with the app itself. I'm sure there are other work arounds with enforced mode, but I don't care. Lol. Also, I simply installed the apk directly from vipers page, enabled the driver, reboot, and voila! No flashing anything, or messing with anything other than the selinux mode. And I am on stock oxygenOS
Viper apk: http://vipersaudio.com/swupdate/viper4android/download.html
Selinux mode changer: http://forum.xda-developers.com/showthread.php?t=2524485
Click to expand...
Click to collapse
I got it to install using this but it does not work as far as i can tell. is it actually working for you?
vision33r said:
I keep getting crashes and system lock ups after flashing Viper4Android 5.4 stock. I soft bricked it once and had to flash stock once when my prior Nandroid Backup failed. So hopefully someone gotten it to work.
Click to expand...
Click to collapse
Letin69 said:
I just tried, my phone rebooted 30 seconds after the boot.
I could go into Viper and it wasn't working, still "abnormal".
All the applications that use the audio are now lagging and FCing...
Audio doesn't work anymore , I restore my backup ^^
Click to expand...
Click to collapse
Letin69 said:
Okay, tell me if you want that I test it
Click to expand...
Click to collapse
vision33r said:
I'll definitely try it out tomorrow. Done wiping my phone over and over. Did Nandroid backup twice and both restores failed. There's something about the Oxygen OS that is checking and is not backed up. Flashing the stock rom fixes it but loses root.
I did have BusyBox installed when I flashed V4A 5.4 stock and boot looped. I will try the V4A fix. The only thing is that if you flash V4A.zip, it causes the phone to become unstable.
Do I flash the V4A Fix after V4A.zip or boot into rom then apply the apk??
Click to expand...
Click to collapse
Ok, I think this is it! Reworked the entire package, updated the audio effects. This should be working now. Please let me know. This should work after flash and installing the drivers.
dustintinsley said:
Ok, I think this is it! Reworked the entire package, updated the audio effects. This should be working now. Please let me know. This should work after flash and installing the drivers.
Click to expand...
Click to collapse
Those who tested, still getting a boot loop or is it working?
dustintinsley said:
Ok, I think this is it! Reworked the entire package, updated the audio effects. This should be working now. Please let me know. This should work after flash and installing the drivers.
Click to expand...
Click to collapse
I get an error 6 when i try to install via TWRP.
rm5 said:
I get an error 6 when i try to install via TWRP.
Click to expand...
Click to collapse
well, that's no good i will take a look at the updater script. do you get any output before the error? i installed manually so trying to figure out the script error
Hello guys,
I moved yesterday to Android Marshmallow on my Htc one m8 with a customROM and I am just wondering, why I can't delete any system apps. I tried to Google the thing, but I get over and over advertisement and reviews about Android Marshmallow. Nothing that helps.
I tried to delete them with several tools and manually with a data explorer. Nothing worked. It seems like the system is restoring itself. Is there any way to "fix" my problem?
It seems like it's not a device-specific thing, so I've decided to ask in the general Q and A section.. I am sorry, if this wasn't correct.
Thank for any help!
What custom ROM?
This device has write protection on the system partition, even with root. But most custom ROMs have the mod applied to bypass the write protection (and allow such changes). So its surprising to see this issue on a custom ROM.
If using a file explorer, try to change the permissions on the folder to RW (rewrite) and see if that helps.
redpoint73 said:
What custom ROM?
This device has write protection on the system partition, even with root. But most custom ROMs have the mod applied to bypass the write protection (and allow such changes). So its surprising to see this issue on a custom ROM.
If using a file explorer, try to change the permissions on the folder to RW (rewrite) and see if that helps.
Click to expand...
Click to collapse
Thanks for your response!
I am on ViperOneM8 6.1.0...
I have already mount System as R/W in Venom Tweaks.
YEA64 said:
I am on ViperOneM8 6.1.0...
I have already mount System as R/W in Venom Tweaks.
Click to expand...
Click to collapse
Strange, it should work.
Did you dirty flash the ROM? If so, that may have something to do with the bug.
Did you try to mount as RW in the file explorer, as I suggested?
Or you can try to flash wp_mod, which is normally how you would remove the system write protection on the stock Sense ROM: http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
Highly suggest to make a TWRP backup of you current ROM and user data, before flashing the wp_mod; in case the mod causes any problems. Not sure if this mod will play well with a custom ROM that has all the modifications like Viper.
redpoint73 said:
Strange, it should work.
Did you dirty flash the ROM? If so, that may have something to do with the bug.
Did you try to mount as RW in the file explorer, as I suggested?
Or you can try to flash wp_mod, which is normally how you would remove the system write protection on the stock Sense ROM: http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
Highly suggest to make a TWRP backup of you current ROM and user data, before flashing the wp_mod; in case the mod causes any problems. Not sure if this mod will play well with a custom ROM that has all the modifications like Viper.
Click to expand...
Click to collapse
No, I did a full wipe before flashing the ROM on a clean, stock ROM. I mounted system as RW in the file explorer, yes, but it didn't work. I am going to look for some other ways, if them doesn't work, I will try the file you linked. Thank for your help and ideas!
Did you look at the Viper thread, to see if its a known problem, or any fixes?
redpoint73 said:
Did you look at the Viper thread, to see if its a known problem, or any fixes?
Click to expand...
Click to collapse
I've searched for "uninstall" and "uninstall system", but it seems like I am alone.
One guy, who had the similar problem, was suggested to use Titanium to uninstall. After that he didn't respond anymore.
Titanium didnt work for me, too.
I have a device rooted wit Magisk as in the thread [GUIDE] Install Magisk with proper support for OTA updates (https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952). All is working fine and just installed 2nd November update withou any hassle.
Now I need BusyBox, but I 'm afraid it could interfere with /system, because I see it installs in /system/bin, and so should stop OTA updating using Magisk de-activated and then re-activated.
Has somebody an answer for this issue, may it works the same?
... or another way of installing BusyBox over/with Magisk and let all work flawlessly?
Thanks guys
There is a Magisk module for Busybox, just install it, reboot and you should be fine.
BubuXP said:
There is a Magisk module for Busybox, just install it, reboot and you should be fine.
Click to expand...
Click to collapse
Thanks a lot, I didn't think at all at Magisk Modules...already installed, it works and it put Busybox in /system/xbin/busybox, I hope it will be fine even if it's in /system...I have to wait next OTA and check the behaviour.
Surely it deserve to give it a shot
Thanks for the suggestion, always welcome from you
Grazie e ciao
Magisk works just like this, changing the /system partition without really touching it. That's because if you want to do OTA updates you need to do everything that involves /system from Magisk.
BubuXP said:
Magisk works just like this, changing the /system partition without really touching it. That's because if you want to do OTA updates you need to do everything that involves /system from Magisk.
Click to expand...
Click to collapse
Got it! At the end I'm starting to understand something more about this crazy Android partitions , also thanks to your input obviously!
Now I'm missing just one thing in my device: to have TWRP installed and working without problems with Magisk.
I think that if I un-install Magisk, then install TWRP, and then re-install Magisk again, it could work...
Maybe better to install Magisk flashing from TWRP ...
I'm not really sure, what do you think about this issue?
All the best, ciao
Hi,
I've installed Busybox magisk module but it breaks my mobile data. If it's disabled or uninstalled than data is back connected.
Anyone experienced the same issue?
Kind regards,
Germans.
Create your own xbin folder, download busybox by stephen, wait for app to collect sytem configuration then choose xbin folder and install, before ota, you must uninstall busybox then reboot, then delete xbin folder. The other method is to install straight to sbin, stephens busybox will auto install to sbin on every reboot, because sbin folder always goes back to original on rebooting, so basically you will just need to untick the toggle to stop auto install.
boe323 said:
Create your own xbin folder, download busybox by stephen, wait for app to collect sytem configuration then choose xbin folder and install, before ota, you must uninstall busybox then reboot, then delete xbin folder.
Click to expand...
Click to collapse
The only problem with this solution is banking apps root detection.
gkornaks said:
The only problem with this solution is banking apps root detection.
Click to expand...
Click to collapse
My halifax still works through magisk, honestly it doesnt affect magisk hide, i only mentioned doing it this way because the busybox magisk module kills the phone when you disable it, because the symlinks are still there, you cant log back into the phone.
Thank you! Will try later. BTW, my busybox module is disabled and I could login without any problem.
gkornaks said:
Thank you! Will try later. BTW, my busybox module is disabled and I could login without any problem.
Click to expand...
Click to collapse
Oh, ok it could of been a different module then, i just assumed it would be that one, sorry for that.
Is this really a problem I have busybox installed so it will interfere with the next update?
And if it will, just uninstalling it solve the problem?
Medo22 said:
Is this really a problem I have busybox installed so it will interfere with the next update?
And if it will, just uninstalling it solve the problem?
Click to expand...
Click to collapse
As long as it removes all the symlinks along with the busybox file.
boe323 said:
As long as it removes all the symlinks along with the busybox file.
Click to expand...
Click to collapse
How can I make sure of that?
Medo22 said:
How can I make sure of that?
Click to expand...
Click to collapse
I dont know every single file name but you can check against magisks own busybox library in sbin,magisk,busybox.Check through your bin folder after you uninstall busybox. Dont go deleting files though, thats why i make my own xbin. Id imagine if magisks busybox module in downloads is systemless theres nothing to worry about.