Hi
Freshly installed 11.0.6.0 Android 10
Magisk 20.4
I try to delete useless system apps (Latest root explorer, authorized with Magisk Manager).
Then i wipe Dalvik, and after reboot, all apps are still here.
When i did the same on 11.0.5.0 Android 9, everything was OK.
Help please.
In my case ,I am using system app remover(app) but after uninstalling system app ,in next reboot phone stuck into fastboot and I have to clean flash
I use the Debloater module, it works without problem
Related
I just installed CynogenMod 9 update 8 for my HTC Explorer a.k.a Pico. It works fine. But whenever I try to install an application from GooglePlay or third-party, phone restarts. Please help me to solve this problem. There is no life without good applications
Make a wipe and reflash the rom+gapps for cm9
as it is asked quite often, here's how you get ota with a modified stock rom.
For example, ota will fail if you have root (as it changes your boot partition slightly) or if you deleted some preinstalled apps (e.g. chrome browser). OTA script always checks the signatures of your running rom and the ota update. If they don't match, it will fail.
An unlocked bootloader does not prevent ota from working!!!
requirements: a backup of a 'clean' stock rom
So if you want to update perform the following steps (edit: you can find a second and easier method at the end of the post)
1. boot twrp
2. backup everything to be safe (boot, recovery, system, data) if something goes wrong
3. restore 'clean' stock boot partition and recovery partition
(4. if you changed something in 'system' restore system as well)
5. boot tablet
6. download and install ota - it should succeed
7. boot twrp and restore data again if needed
(8. root again with magisk)
good to know:
if you restore partitions, make sure they are from the same build! if not, tablet might not boot or ota will fail again.
if you are rooted, you can use the the backup of boot created by the magisk script (-->/data/stock_boot_<sha1>.img.gz)
if you don't have a backup, try to get hands on a stock rom and flash the required partitions manually (e.g. fastboot flash boot.img etc..)
good luck
(if anyone knows a better way, let me know and i will add it here)
edit: @MarkAllen provided this method which is far more simple (but which unfortunately has never worked for me by now).
1) Boot TWRP and install "Magisk Uninstaller"
2) Clear cache and Dalvik cache in TWRP then reboot
3) Uninstall phh's SuperUser and Magisk Manager
4) Start OTA update and follow instructions
This completed no problem for myself and then I just re-rooted again
5) Boot TWRP and installed Magisk 12
6) Clear cache and Dalvik cache then reboot
7) Install phh's SuperUser from the play store
8) Launch SuperUser and Magisk manager each one time (for some reason root checker claimed root was not installed properly until I did this)
9) Check root using root checker
I was rooted from the last February security update. I was under the impression I would be able to allow the April security update to download then copy it on the root of my internal or sdcard storage then boot to normal recovery to install. I've done this with other devices I own (Shield Tablet and TV) and seemed to work fine for them. You would just re-root later when done. Anyway as you noted this didn't work on the Yoga Book though due to changes rooting makes on this device.
How I ended up doing this was a bit different then you describe, but meets the same end as your instructions I guess? All I had done was uninstalled root, ran OTA update (which worked this time), then rooted again and it worked great.
1) Boot TWRP and install "Magisk Uninstaller"
2) Clear cache and Dalvik cache in TWRP then reboot
3) Uninstall phh's SuperUser and Magisk Manager
4) Start OTA update and follow instructions
This completed no problem for myself and then I just re-rooted again
5) Boot TWRP and installed Magisk 12
6) Clear cache and Dalvik cache then reboot
7) Install phh's SuperUser and Magisk manager from the play store
8) Launch SuperUser and Magisk manager each one time (for some reason root checker claimed root was not installed properly until I did this)
9) Check root using root checker
MarkAllen said:
I was rooted from the last February security update. I was under the impression I would be able to allow the April security update to download then copy it on the root of my internal or sdcard storage then boot to normal recovery to install. I've done this with other devices I own (Shield Tablet and TV) and seemed to work fine for them. You would just re-root later when done. Anyway as you noted this didn't work on the Yoga Book though due to changes rooting makes on this device.
How I ended up doing this was a bit different then you describe, but meets the same end as your instructions I guess? All I had done was uninstalled root, ran OTA update (which worked this time), then rooted again and it worked great.
1) Boot TWRP and install "Magisk Uninstaller"
2) Clear cache and Dalvik cache in TWRP then reboot
3) Uninstall phh's SuperUser and Magisk Manager
4) Start OTA update and follow instructions
This completed no problem for myself and then I just re-rooted again
5) Boot TWRP and installed Magisk 12
6) Clear cache and Dalvik cache then reboot
7) Install phh's SuperUser from the play store
8) Launch SuperUser and Magisk manager each one time (for some reason root checker claimed root was not installed properly until I did this)
9) Check root using root checker
Click to expand...
Click to collapse
great to hear...
using the uninstaller alone has never worked for me...it always aborts...sometimes it complains that some files are missing or were changed, the recovery partition doesn't match the expected one, etc...
mostly i can't remember which things i've done to the rom/system.
but again, good to know that magisk uninstaller works, it definitely is less complicated and time consuming.
I'm having a a wierd issue can someone explain , i recently downloaded Xiaomi.eu 8.11.15 rom n flashed it via twrp recovery along with data disable force encryption (magisk included 17.3) , it booted , i checked magisk installed n module installation was working properly , then i wanted to remove google app but it's a system app so i downloaded system app remover it was granted root permission but when I was trying to remove app it was failing again n again so i thought trying if via file explorer so i tried to remove it from root storage/system/priv app but again it was failing to delete a folder though root permission was granted to file explorer , when I'm installing module via magisk it's working fine but in explorer I'm unable to delete any system app like google home or other bloatware apps
I see you have already asked this question somewhere else. Why do you keep asking it everywhere? XDA is already becoming a mess, please don't make it worse.
I have the root with Magisk in Android 8.0. At first, the warning always came out asking if you wanted to grant root rights to the application that you just opened. However, this warning is no longer displayed, even though the configuration of Magisk Manager is configured in this way.
In the Magus Superuser section, I do not see any trace of the applications that I can not 'root'.
I have updated Magisk Manager, but the error continues. I also removed BusyBox, but the error continues.
I can not give root permission to any other application. But the mobile is rooted, since the first applications that I installed that require root continue to function normally. I can even deactivate the root and then activate it again.
Reinstalling the applications is not solved. With Dalvik and Caché wipe either.
That could be happening? How is it solved?
____
Magisk Manager has all the permissions of everything (memory, background, manual battery mode). I have tried to reinstall Magisk Manager and nothing.
Deactivating BusyBox (Magisk module) and Xposed and restarting still does not work.
Returning to install the Magisk image by TWRP or Fastboot is not fixed either.
I have removed all the fret that I had done to the phone (BusyBox, Xposed, root Magisk and boot modified for the root) and the problem has not been solved. I do not know what may be happening. I do not have other rare applications.
I have installed Device Control and the TWRP application. I have not gotten the root request to skip (although it has activated that option in Magisk Manager).
Definitely, it is not the fault of the new applications, which was the first question I wanted to solve.
Magisk version:
19.3 (19300)
And from Manager 7.2.0 (213), although I have also tried 7.3.2 (224).
The root is done with patching (via Magisk) of RAMDISK.IMG.
I understand that some applications are not compatible with systemless. But I'm not going any of the new ones that I'm trying. Interestingly, other applications compatible with Magisk (except those that installed the first days of the mobile) do not work either.
I have installed Magisk Manager 7.0.0 (and also 6.1.0), but the bug is still there. It seems that it does not depend on the APK.
As my Magisk file to root consists of a patch of RAMDISK.IMG created directly from Magisk Manager I do not know how to create one based on a lower version (for example, version 18.1). It only gives me the option to patch with the latest Magisk Manager version (if I have a lower one, it asks me to update the APK).
Whenever I generate the IMG of my patched RAMDISK.img it is based on 19.3.
How could I generate a patched IMG based on a lower version?
I have microG, not the GApps. Could that influence? Does Magisk need them?
Hello friends. Yesterday my redmi note 4x snapdragon (mido) showed a strange problem. I was using phone normally and then a notification popped out from magisk. It was about the updates available for both - magisk manager and magisk. I first updated the manager from the app itself by clicking on 'install'.
But after it finished installing the magisk manager, when it reopened it showed that magisk was not installed!
Then I check my root applications (greenify, mixplorer) and they also were not getting root access. Neither There was a prompt for granting root acess.
I checked my root status from the root checker app from playstore and it showed - 'root access available but not properly installed'
Please suggest me what should I do to update magisk or get magisk working back.
Other details-
Rom - aosp extended official 6.3 pie treble
Kernel - Franco kernel r20
Previous magisk installed- 18.00
New available magisk - 20.3
New magisk manger that I updated - 7.5.1
Everything was working fine on my device previously.
Please help me guys.
Thanks in advance.
Solved the issue!
AviralSri said:
Hello friends. Yesterday my redmi note 4x snapdragon (mido) showed a strange problem. I was using phone normally and then a notification popped out from magisk. It was about the updates available for both - magisk manager and magisk. I first updated the manager from the app itself by clicking on 'install'.
But after it finished installing the magisk manager, when it reopened it showed that magisk was not installed!
Then I check my root applications (greenify, mixplorer) and they also were not getting root access. Neither There was a prompt for granting root acess.
I checked my root status from the root checker app from playstore and it showed - 'root access available but not properly installed'
Please suggest me what should I do to update magisk or get magisk working back.
Other details-
Rom - aosp extended official 6.3 pie treble
Kernel - Franco kernel r20
Previous magisk installed- 18.00
New available magisk - 20.3
New magisk manger that I updated - 7.5.1
Everything was working fine on my device previously.
Please help me guys.
Thanks in advance.
Click to expand...
Click to collapse
So friends, i figured out the solution myself. And I am describing it here in case anyone faces such a problem.
First of all, i forgot to mention one strange thing - while i was updating the magisk manager to new 7.5.1 version from the manager itself, during its installation, i got 2 prompts from google play store which said that i should not install this app as it is not a trusted application. But i clicked on "Install Anyway" both the times and it installed.
After then, when i opened the updated maanger, it showed that magisk is not installed (the new manager app also took some time greator than usual, on its first launch). And then the root access went from everywhere on my device.
Then i thought of uninstalling the magisk from flashing the Magisk-uninstaller-zip-file and then installing the magisk-v-18.zip again, but after searching for some time about uninstalling the magisk, i came to know that there are greater chances of my device going into a bootloop.
For one last time, i tried this - uninstalled magisk manager 7.5.1. Then installed MagiskManger 7.4.0 again. And when i launched it, it showed me Magisk-v18 installed!. Also the app showed me that updates are available for both - manager and magisk. App also showed the superuser menu, Magisk Hide menu. I thought that the problem was solved. But quickly i found that still other root apps were not working. When i reopened the Magisk-Manger-7.4.0, it displayed a message - "A addition setup is needed for root to work". But i did not update from there. Instead i followed a safe path -
Solution - 1. Download official Magisk-20.3 and copy in your phone's internal storage.
2. Then copy the original unaltered boot.img of the rom you're using in your internal storage.
3. Boot into TWRP recovery. Go into "install", and select "install image". Then select your boot.img and swipe to flash.
(Here, i did not wipe anything before flashing. Just flashed the img file over)
4. Reboot to your system. Now your android be cleanly unrooted.
5. Again reboot to TWRP. Select "install", and select and flash the Magisk20.3.zip file and reboot to your system.
Voila!!! Here you go! Your system is now properly rooted with latest magisk!
Thanks!