Related
Hi all,
I just received an update to my OnePlus 2 - Oxygenos 3.5.5. The update removed the the recovery, root, Magisk and Xposed so I went ahead and flashed the TWRP again and then installed Magisk + phh's SuperUser.
All went fine, the phone booted OK. Then I decided to put back the Xposed and installed it via Magisk Manager and rebooted the phone. The phone got stuck at booting. I suspect that the new OxygenOS update + Xposed are the reason. I am able to uninstall the Magisk using the uninstaller and then can get back to the Magisk + root, but whenever I try to install Xposed the phone gets stuck when booting.
Any idea how to fix this?
6opuc said:
Hi all,
I just received an update to my OnePlus 2 - Oxygenos 3.5.5. The update removed the the recovery, root, Magisk and Xposed so I went ahead and flashed the TWRP again and then installed Magisk + phh's SuperUser.
All went fine, the phone booted OK. Then I decided to put back the Xposed and installed it via Magisk Manager and rebooted the phone. The phone got stuck at booting. I suspect that the new OxygenOS update + Xposed are the reason. I am able to uninstall the Magisk using the uninstaller and then can get back to the Magisk + root, but whenever I try to install Xposed the phone gets stuck when booting.
Any idea how to fix this?
Click to expand...
Click to collapse
https://github.com/rovo89/XposedBridge/wiki/Bugs#how-can-i-get-logs
Get a adb logcat on boot stuck with xposed installed, put it on pastebin and link here to see why isn't booting.
dcastro172 said:
https://github.com/rovo89/XposedBridge/wiki/Bugs#how-can-i-get-logs
Get a adb logcat on boot stuck with xposed installed, put it on pastebin and link here to see why isn't booting.
Click to expand...
Click to collapse
Hi dcastro172,
Unfortunately adb logcat does not give any info. At this boot stage the device is not detected yet by adb, hence no logcat possible. Is there anything I can collect differently?
Here are two logs from /data/data/de.robv.android.xposed.installer/log/
Perhaps this helps?
6opuc said:
Hi dcastro172,
Unfortunately adb logcat does not give any info. At this boot stage the device is not detected yet by adb, hence no logcat possible. Is there anything I can collect differently?
Click to expand...
Click to collapse
You see bootanimation or only splash logo?
Enviado de meu SM-G900M usando Tapatalk
6opuc said:
Hi all,
I just received an update to my OnePlus 2 - Oxygenos 3.5.5. The update removed the the recovery, root, Magisk and Xposed so I went ahead and flashed the TWRP again and then installed Magisk + phh's SuperUser.
All went fine, the phone booted OK. Then I decided to put back the Xposed and installed it via Magisk Manager and rebooted the phone. The phone got stuck at booting. I suspect that the new OxygenOS update + Xposed are the reason. I am able to uninstall the Magisk using the uninstaller and then can get back to the Magisk + root, but whenever I try to install Xposed the phone gets stuck when booting.
Any idea how to fix this?
Click to expand...
Click to collapse
Xposed v87?
I guess it is boot animation. It it like a clock with moving hands....
Yes. 87
6opuc said:
Yes. 87
Click to expand...
Click to collapse
Looks like update break Xposed, bunch of errors in log, open a issue at Xposed github.
Hello,
is it possible to uninstall Magisk completely without using the Magisk Manager. Everytime i try to uninstall with the manager, it comes "error downloading file". Is there another simple way to do this?
Thanks
painkiller_one said:
Hello,
is it possible to uninstall Magisk completely without using the Magisk Manager. Everytime i try to uninstall with the manager, it comes "error downloading file". Is there another simple way to do this?
Thanks
Click to expand...
Click to collapse
In the Magisk thread there is an uninstaller file you can flash from recovery
Sent from my Pixel using Tapatalk
Chocobubba said:
In the Magisk thread there is an uninstaller file you can flash from recovery
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Hello, do you mean this file? https://github.com/topjohnwu/Magisk/releases/download/v17.3/Magisk-uninstaller-20181022.zip
I´m using Magisk v17.1 on Huawei P10
This won´t work for me in TWRP. After flashing i get an error like this:
!Cannot access /data , please uninstall with magisk manager
- Unmounting partitions.
Yeah that's the for, try updating Magisk first, then uninstalling it.
Sent from my Pixel using Tapatalk
On my P10 it looks like the newest Version. Update isn't possible. Or is it a way to install an older version and then remove it?
Try flashing the uninstaller as you would a module not in the Magisk repo (Modules section, "+"-button).
Thanks this worked fine. Problem solved.
Hi, I don't want to create a new thread because my problem is very similar.
I want to uninstall Magisk to be able to update my OP5. But however I am trying, it's not working. I tried flashing the uninstall.zip via TWRP first, tried the deinstall feature of the Magisk Manager and finally tried the method mentioned above. None of them worked. I restart my phone and Magisk is still installed. It needs to update and reinstall the manager but my phone is still rooted. I don't know what to do. Magisk Manager is/was up to date and I even restored a TWRP backup just in case I did some mistakes during the uninstallation.
Can anyone help me with that?
Vanillezucker said:
Hi, I don't want to create a new thread because my problem is very similar.
I want to uninstall Magisk to be able to update my OP5. But however I am trying, it's not working. I tried flashing the uninstall.zip via TWRP first, tried the deinstall feature of the Magisk Manager and finally tried the method mentioned above. None of them worked. I restart my phone and Magisk is still installed. It needs to update and reinstall the manager but my phone is still rooted. I don't know what to do. Magisk Manager is/was up to date and I even restored a TWRP backup just in case I did some mistakes during the uninstallation.
Can anyone help me with that?
Click to expand...
Click to collapse
There's a bug in the Magisk v19.1 uninstaller. It's been fixed upstream, so try using the Canary uninstaller instead: https://github.com/topjohnwu/magisk_files/raw/master/canary_builds/magisk-uninstaller.zip
Didgeridoohan said:
There's a bug in the Magisk v19.1 uninstaller. It's been fixed upstream, so try using the Canary uninstaller instead: https://github.com/topjohnwu/magisk_files/raw/master/canary_builds/magisk-uninstaller.zip
Click to expand...
Click to collapse
Looks like it worked. My phone is not rooted anymore and I could update without a problem. Thanks a lot
Works great on Nougat 7.1.1
Thanks
Well hello,
I'm on the canary build on Huawei P20 pro. I've installed, I guess... A module, which was not for this version of magisk, or whatever...
The phone, when I press the + button during boot -> to boot with magisk running -> the phone stays in bootloop
If I boot without the + button, therefore without magisk running, the phone works.
But now I'm stuck with some problematic module, which I can't disable nor uninstall, because the Huawei P20 pro has encrypted /Data and the magisk uninstaller tells me it can't access the /data so I should uninstall the magisk with the magisk manager.
But I can't, because I'm booting only without the magisk, so the magisk manager doesn't see any Magisk running.
So, I even flashed back the stock boot, which worked and then flashed the magisk once again (the installer told me I got stock boot and it's patching and stuff...) But I'm back where I was. without +button the phone works, but no magisk. With the +button boot I got stuck in bootloop.
I've serached everywhere to find some "patchable magisk module disabler" but without luck.
Thanks for any advice
Have you tried magisk recovery management? That may work.
Hi thanks, didn't know somethiung like that existed... But still doesn't work. I'm stuck at "error 1" in twrp. I've tried multiple versions of TWRP, tried magisk again, tried reflashing stock boot. but still error 1.
It's wierd...
Do you have access to /cache? If so:
https://www.didgeridoohan.com/magisk/Magisk#hn_Disable_all_modules
Didgeridoohan said:
Do you have access to /cache? If so:
https://www.didgeridoohan.com/magisk/Magisk#hn_Disable_all_modules
Click to expand...
Click to collapse
Hi, I've been browsing the magisk webpages today and I found exactly what you sent to me. Thank you kind sir. It worked
Didgeridoohan said:
Do you have access to /cache? If so:
https://www.didgeridoohan.com/magisk/Magisk#hn_Disable_all_modules
Click to expand...
Click to collapse
Hi, I've been browsing the magisk webpages today and I found exactly what you sent to me. Thank you kind sir. It worked
Hi everyone.
So I had a moto x4 for about year and a half before fricking up the charging port. So I recently acquired another one. Everything went smoothly the first month or so, with twrp properly installed and magisk too, but then I tried to install a magisk module and the phone bricked. I tried restoring via twrp backup but it didn't work and I ended up in a bootloop. So I flashed a stock rom. And when I wanted to install twrp it just didn't stick after a reboot and magisk would just get my phone stucked on the splashscreen.
I realized that, for whatever reason, a previous version of magisk would work (magisk 18.1) but I've no idea why. Magisk 18.1 is the only version that works. If I flash any other version from twrp my phone gets stuck on the splashscreen, same if I update magisk via magisk manager. And if I try to install any magisk module my phone won't start. But root permission works fine on other apps i.e. system app uninstaller, root explorer or swift installer.
Does anyone have any idea? It'd be greatly appreciated.
Thanks!!
Organics said:
Hi everyone.
So I had a moto x4 for about year and a half before fricking up the charging port. So I recently acquired another one. Everything went smoothly the first month or so, with twrp properly installed and magisk too, but then I tried to install a magisk module and the phone bricked. I tried restoring via twrp backup but it didn't work and I ended up in a bootloop. So I flashed a stock rom. And when I wanted to install twrp it just didn't stick after a reboot and magisk would just get my phone stucked on the splashscreen.
I realized that, for whatever reason, a previous version of magisk would work (magisk 18.1) but I've no idea why. Magisk 18.1 is the only version that works. If I flash any other version from twrp my phone gets stuck on the splashscreen, same if I update magisk via magisk manager. And if I try to install any magisk module my phone won't start. But root permission works fine on other apps i.e. system app uninstaller, root explorer or swift installer.
Does anyone have any idea? It'd be greatly appreciated.
Thanks!!
Click to expand...
Click to collapse
Please help me to root Moto X4, bootloader unlocked
hrushikesh.inc said:
Please help me to root Moto X4, bootloader unlocked
Click to expand...
Click to collapse
Wrong thread.
https://forum.xda-developers.com/moto-x4/help/moto-x4-f-q-s-thread-t3814393
i run china k20 pro on indian miui 11.01.0
i installed twrp -21 version
installing magisk 20 provides root access however magisk manager asks to something which results in bootloop to recovery
ignoring that request, the module i wanted to install [energized ] asks for updating to magisk 20.1 which also leads to bootloop to recovery.
is there anything to do ? or just wait for magisk 20.2 to be released and then try it
p.s installing magisk was the only way to prevent redmi recovery from overwriting twrp, i don't know if this has any importance
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
eLcTrOn said:
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
Click to expand...
Click to collapse
yeah i used magisk uninstaller to make the phone work normally
Glad it worked . Are u able to install magisk again ?
eLcTrOn said:
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
Click to expand...
Click to collapse
Dont install Viper4android via magisk. Just download the package and install in via TWRP. Use this guide
I have this exact problem right now but even with other versions of magisk, I encounter the same issue. Any suggestions?
Same problem here with magisk I guess it is a compatibly issue with MIUI 11
Yep, it's a MIUI11 issue and the reason I haven't shifted over to it. I suspect whatever release of magisk is in the pipeline will fix it provided it's been reported.
In the meanwhile I've read 19.4 works; you could try the canary builds if that seems to old for your liking... just be careful.
Had the same problem, its because of data encryption.
You guys need to format data before installing magisk.
winesh said:
Had the same problem, its because of data encryption.
You guys need to format data before installing magisk.
Click to expand...
Click to collapse
Even with data formatting 20.1 causes issues: In fact, it seems latest Magisk build seems to be causing issues on all (or, many) builds of MIUI 11.
For k20 pro, 19.3/.4 seems smartest to install and then update via magisk manager
I believe other phones (mi 9?) need even older versions like 17.2, so I wouldn't be surprised if future updates continue to push the installation build back.
AvgZing said:
Even with data formatting 20.1 causes issues: In fact, it seems latest Magisk build seems to be causing issues on all (or, many) builds of MIUI 11.
For k20 pro, 19.3/.4 seems smartest to install and then update via magisk manager
I believe other phones (mi 9?) need even older versions like 17.2, so I wouldn't be surprised if future updates continue to push the installation build back.
Click to expand...
Click to collapse
I'm hoping the Magisk situation gets fixed. I checked the Magisk support thread and only saw one post about a bootloop with a Mi9T Pro (again, likely data encryption) so I'm given the impression MIUI might be off the radar for Magisk bug fixes.
I've had a couple of issues with Magisk 20.1 on MIUI10 - nothing critical but a couple times Magisk Manager has frozen (i.e. kill the process, relaunch and it works) and a couple hangs when root apps have been launched for the first time (again, kill + relaunch, a few times if necessary). Smooth sailing otherwise but gives me the impression that Magisk isn't without flaws on MIUI. One response was to dump MIUI altogether but I'd rather have a stable hardware experience for now. I tested a lot of custom ROMs on my last device and based on that, I'd like to stick to MIUI for a while.
Out of curiousity what are the other bugs with MIUI11 aside from it not working with encryption?
droident said:
I'm hoping the Magisk situation gets fixed. I checked the Magisk support thread and only saw one post about a bootloop with a Mi9T Pro (again, likely data encryption) so I'm given the impression MIUI might be off the radar for Magisk bug fixes.
I've had a couple of issues with Magisk 20.1 on MIUI10 - nothing critical but a couple times Magisk Manager has frozen (i.e. kill the process, relaunch and it works) and a couple hangs when root apps have been launched for the first time (again, kill + relaunch, a few times if necessary). Smooth sailing otherwise but gives me the impression that Magisk isn't without flaws on MIUI. One response was to dump MIUI altogether but I'd rather have a stable hardware experience for now. I tested a lot of custom ROMs on my last device and based on that, I'd like to stick to MIUI for a while.
Out of curiousity what are the other bugs with MIUI11 aside from it not working with encryption?
Click to expand...
Click to collapse
Other than standard app compatibility issues, I haven't heard of any major MIUI11 bugs, which is fantastic to hear.
I have tried all sorts. MI9T MIUI 11.0.1.0 and magisk just causes recovery bootloop . Gonna try magisk 19.4 if thats a thing mentioned in a previous reply
I use Miui 11.0.3 together with Magisk. I used the following procedure:
1. Copy Magisk 20.1 (for twrp) to your internal storage (e.g. downloads)
2. Install Magisk via TWRP
3. Don't reboot (it will cause bootloop).
4. Do factory reset (it will remove your Data). Your bootloader will remain patched.
5. Reboot your phone, do initial config.
6. Install Magisk Manager and run it so you will see that Magisk is installed.
7. DON'T install additional files suggested by Magisk Manager (or you will end up in bootloop again)
8. Enjoy your rooted K20Pro!
I got the same problem on my k20 pro (with MIUI EU).I try driffent ways provided by magisk official but no one works.I have to flash the system. It's not a good idea for intalling V4A on this phone
XedosMD said:
I use Miui 11.0.3 together with Magisk. I used the following procedure:
1. Copy Magisk 20.1 (for twrp) to your internal storage (e.g. downloads)
2. Install Magisk via TWRP
3. Don't reboot (it will cause bootloop).
4. Do factory reset (it will remove your Data). Your bootloader will remain patched.
5. Reboot your phone, do initial config.
6. Install Magisk Manager and run it so you will see that Magisk is installed.
7. DON'T install additional files suggested by Magisk Manager (or you will end up in bootloop again)
8. Enjoy your rooted K20Pro!
Click to expand...
Click to collapse
Does your phone remain encrypted after you do these steps? I doubt...
For some reasons, I wanna keep my phone encrypted.