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.
First of all, I have very limited android experience but I need too root my phone for the functionality of an app that's critical to my business. Anyways, I'm running a Moto x4 with Pie. I already installed magisk 17.3 and magisk manager 6.0.1 using twrp recovery following a tutorial on youtube. When opening the magisk manager, it asked me to update to 7.1.1, which I did. Then it told me that I needed at least v18.0 magisk to be able to run the new magisk manager. Am I able to update magisk by flashing the new zip version in twrp, or is another method required since a prior version is already installed? Is this how I would install all future versions of magisk that comes out? Is there anything that I should know before flashing? I really don't want to get stuck in a boot loop or brick the phone.... Any guidance will be greatly appreciated.
organicloot said:
First of all, I have very limited android experience but I need too root my phone for the functionality of an app that's critical to my business. Anyways, I'm running a Moto x4 with Pie. I already installed magisk 17.3 and magisk manager 6.0.1 using twrp recovery following a tutorial on youtube. When opening the magisk manager, it asked me to update to 7.1.1, which I did. Then it told me that I needed at least v18.0 magisk to be able to run the new magisk manager. Am I able to update magisk by flashing the new zip version in twrp, or is another method required since a prior version is already installed? Is this how I would install all future versions of magisk that comes out? Is there anything that I should know before flashing? I really don't want to get stuck in a boot loop or brick the phone.... Any guidance will be greatly appreciated.
Click to expand...
Click to collapse
You can update it from Magisk and as well as from TWRP...
organicloot said:
First of all, I have very limited android experience but I need too root my phone for the functionality of an app that's critical to my business. Anyways, I'm running a Moto x4 with Pie. I already installed magisk 17.3 and magisk manager 6.0.1 using twrp recovery following a tutorial on youtube. When opening the magisk manager, it asked me to update to 7.1.1, which I did. Then it told me that I needed at least v18.0 magisk to be able to run the new magisk manager. Am I able to update magisk by flashing the new zip version in twrp, or is another method required since a prior version is already installed? Is this how I would install all future versions of magisk that comes out? Is there anything that I should know before flashing? I really don't want to get stuck in a boot loop or brick the phone.... Any guidance will be greatly appreciated.
Click to expand...
Click to collapse
First of all: backup! Then you can bootloop, brick (or not!) with no worries. Do it with twrp.
Download latest (beta) Magisk 19.0, flash it under twrp and be happy.
Just to add to the above....
Since you're already rooted you don't have to flash the zip in TWRP. Just go to the Magisk Manager Modules section, click the "+"-button and select the Magisk zip. When it's done, reboot and you're updated.
Shubham259 said:
You can update it from Magisk and as well as from TWRP...
Click to expand...
Click to collapse
I'm not able to open manager because it says I need at least v18.0. The app wont open.
Didgeridoohan said:
Just to add to the above....
Since you're already rooted you don't have to flash the zip in TWRP. Just go to the Magisk Manager Modules section, click the "+"-button and select the Magisk zip. When it's done, reboot and you're updated.
Click to expand...
Click to collapse
If it's in the manager app, I'm not sure how to do it because it says that I can't open it with anything <v18.0.
wilsonhlacerda said:
First of all: backup! Then you can bootloop, brick (or not!) with no worries. Do it with twrp.
Download latest (beta) Magisk 19.0, flash it under twrp and be happy.
Click to expand...
Click to collapse
Good news! The flash has been successful. And I learned about NANDroid backups. Super helpful! Thanks for the help!!
organicloot said:
If it's in the manager app, I'm not sure how to do it because it says that I can't open it with anything <v18.0.
Click to expand...
Click to collapse
You could of course uninstall the incompatible Manager and reinstall the one that works with your Magisk version.
But, that's now besides the point.
A day when you learn something new is a good day. :good:
If you want to learn more, here's a trivia [emoji14]
Also install "Magisk Manager for Recovery Mode (mm)" module. Not promoting it, but I myself feel it's a good module that you need to have before playing with Magisk Modules
It allows you to manage Magisk Modules from TWRP itself. So next time you run into a bootloop, you know what to do
Sent from my #FlagshipKiller3T using Tapatalk
Hello guys,
I made an update in TWRP and installed Havoc 2.4 to try it. After 1 hour I restored my backup and changed back to MIUI. I couldn't log in, so I cleaned the keyfiles to set a new pin.
I reflashed new Beta (25.4 MIUI - Xiaomi.eu) ROM and Magisk but root does not apply on my device... What is wrong? Seems that it's not possible to root anymore... Its does not give me any fails when installing the magisk 18.1 zip in TWRP...
thanks in advance
Have you tried a simple reboot? Usually it takes a reboot more to apply.
no it's not that. now its always booting into twrp when I try to flash magisk
makmak001 said:
no it's not that. now its always booting into twrp when I try to flash magisk
Click to expand...
Click to collapse
Extract the boot.image from the rom and place it in your downloads folder.
Now with Magisk Manager , download and install Magisk to that boot image
Magisk will write root to the boot.image file and then will automatically flash the the updated boot image, and restart to system >>> Issue resolved.
I fixed it by wiping data... now its working
tsongming said:
Extract the boot.image from the rom and place it in your downloads folder.
Now with Magisk Manager , download and install Magisk to that boot image
Magisk will write root to the boot.image file and then will automatically flash the the updated boot image, and restart to system >>> Issue resolved.
Click to expand...
Click to collapse
I have the same problem with magisk, after weekly update and after magisk installed, boot only TWRP. I tried with18.1 version but will not recognise. Boot image and Magisk 19.1 are in downloads but no success. Anyway, with this weekly update all people have loosen magisk, I have read in Xiaomi forum.
slave2007 said:
I have the same problem with magisk, after weekly update and after magisk installed, boot only TWRP. I tried with18.1 version but will not recognise. Boot image and Magisk 19.1 are in downloads but no success. Anyway, with this weekly update all people have loosen magisk, I have read in Xiaomi forum.
Click to expand...
Click to collapse
Nope, no issues on my Mi 8. Here is the trick. When updating do not flash Magisk until you out have booted into the system and ran updates and deleted cache and trash, then reboot to recovery and flash Magisk.
If the method that I described before in the previous post doesn't work, then unpack the boot image from the update and flash it to boot in recovery then flash Magisk Canary debug.
I have been doing this for every weekly update using the beta ROM.
I had an issue just once that was resolved by flashing SuperSu, booting to system confirming root, then reboot to recovery and removing Su, flashing the boot and Magisk Canary
Sent from my Xiaomi MI 8 using XDA Labs
slave2007 said:
I have the same problem with magisk, after weekly update and after magisk installed, boot only TWRP. I tried with18.1 version but will not recognise. Boot image and Magisk 19.1 are in downloads but no success. Anyway, with this weekly update all people have loosen magisk, I have read in Xiaomi forum.
Click to expand...
Click to collapse
Here you can see that I have root and latest update
Sent from my Xiaomi MI 8 using XDA Labs
tsongming said:
Nope, no issues on my Mi 8. Here is the trick. When updating do not flash Magisk until you out have booted into the system and ran updates and deleted cache and trash, then reboot to recovery and flash Magisk.
If the method that I described before in the previous post doesn't work, then unpack the boot image from the update and flash it to boot in recovery then flash Magisk Canary debug.
I have been doing this for every weekly update using the beta ROM.
I had an issue just once that was resolved by flashing SuperSu, booting to system confirming root, then reboot to recovery and removing Su, flashing the boot and Magisk Canary
Click to expand...
Click to collapse
Man has found the guilty in Xiaomi.eu/community.
It is not Magisk, but Viper 4.2. I have flashed Magisk, after reboot again in recovery and wanted to flash version 4.1. It was uninstalled, have no Viper, but Magisk is installed ?
slave2007 said:
Man has found the guilty in Xiaomi.eu/community.
It is not Magisk, but Viper 4.2. I have flashed Magisk, after reboot again in recovery and wanted to flash version 4.1. It was uninstalled, have no Viper, but Magisk is installed ?
Click to expand...
Click to collapse
I no longer use Viper because my phone has 1 speaker and for me Ainur Sauren works pretty well for all sounds.
For listening to music I have the Pro version of Power amp which has every wanted option such as dynamic compression, dynamic EQ, convolution reverb, limiting , tag editing, visualizations etc, I bought it 5 years ago for $3. Best 3 bucks that I ever spent!
Seriously, I can't recommend Poweramp highly enough, its worth its weight in gold.
Sent from my Xiaomi MI 8 using XDA Labs
I have installed the latest pie stable on my op 3t. However it would never boot when installing with Magisk.
So for now I have installed it without Magisk and got it to work ok. However now I'm having same problem installing Magisk.
I can install and uninstall it from twrp latest, however when it's installed, it is just stuck on the initial screen with oneplus logo. And never makes it to the circle/dots screen.
I tried using 19. 2, 19.0 Magisk and 18.1.
Is there any logs I can pull or did anyone else have this issue?
Are there any other safe root solutions to try instead?
Any help would be appreciated
anykiel91 said:
I have installed the latest pie stable on my op 3t. However it would never boot when installing with Magisk.
So for now I have installed it without Magisk and got it to work ok. However now I'm having same problem installing Magisk.
I can install and uninstall it from twrp latest, however when it's installed, it is just stuck on the initial screen with oneplus logo. And never makes it to the circle/dots screen.
I tried using 19. 2, 19.0 Magisk and 18.1.
Is there any logs I can pull or did anyone else have this issue?
Are there any other safe root solutions to try instead?
Any help would be appreciated
Click to expand...
Click to collapse
I always flash Magisk BEFORE the first boot. Also no custom kernels, especially not AFTER Magisk flash.
Is this what you did as well?
I couldn't get it to boot up before firstboot. So I went with normal nonroot flash so I could use the phone.
I figured it would not matter if I installed Magisk later.
I might try to reflash everything over again
ast00 said:
I always flash Magisk BEFORE the first boot. Also no custom kernels, especially not AFTER Magisk flash.
Is this what you did as well?
Click to expand...
Click to collapse
topjohnwu says that you flash custom kernel after flashing Magisk
Immortalis said:
topjohnwu says that you flash custom kernel after flashing Magisk
Click to expand...
Click to collapse
Never had this problem until today. So I did some testing.
Magisk 19.1 causes it to get stuck at the OP logo.
I flashed uninstaller, reflashed the ROM, flashed Magisk 19.2 and it worked.
Are you using the 19.2 zip?
ast00 said:
Never had this problem until today. So I did some testing.
Magisk 19.1 causes it to get stuck at the OP logo.
I flashed uninstaller, reflashed the ROM, flashed Magisk 19.2 and it worked.
Are you using the 19.2 zip?
Click to expand...
Click to collapse
Yes, I had problems with 19.1 too, that the phone sometimes (if not always) would boot itself into fastboot mode instead of system, so at that time I moved temporarily to canary builds
I used this zip instead and it worked. Not sure what's different but I'm good now
https://forum.xda-developers.com/oneplus-3t/development/rom-theone3tos-v1-0-t3730932
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