Database Develop

Going back to stock.

So I have twrp and rooted, running Xposed gravity box. I did not backup ROM when I started. Can I do a factory data wipe and not loose twrp and just reflash supersu? Or will I loose everything? My goal is to get the phone back to when I opened up the box new but keep twrp, bootloader unlocked and rooted.

How did you get Xposed to working, after installing Xposed and the apk my phone booted fine, but if I install any module I get a bootloop

Luminis1987 said:
How did you get Xposed to working, after installing Xposed and the apk my phone booted fine, but if I install any module I get a bootloop
Click to expand...
Click to collapse
You have to use v87 of Xposed Framework as it has a workaround for an issue caused by Android November Security Update.
Any earlier version will bootloop as soon as you enable any module.

Can't update magisk to v17

I try and install directly from magisk but when I go and flash the zip through app it says installation failed. Am I doing something wrong?

Me too
I try unistall magisk in recovery but non success
I'm blocked
Edit: i'm return at v16.6 and work
I don't update for Now Walt for more info

Ty for now I'll wait

same here
Edit:- can't go back to v16.0 either,i'm getting "updater process ended with ERROR: 1
Any suggestions?

1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.

Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
If I don't have TWRP I just install it? Sorry for noob question but i'm new here

Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
Thanks mate,worked for me.

Hi,
I'm running a HTC 10 with Lineage OS 15.1 (8.1.0). I came from Magisk 16 and an update message appeard. I downloaded Magisk 17 and tried to install it via TWRP as usual. The installation stopped with an Error 2. After that I had a boot loop and had to reinstall the Lineage OS. After that it booted again. But I still get this error message when trying to install Magisk 17.
Very odd. Besides of that, GREAT WORK!
Cheers

lmrcarneiro said:
If I don't have TWRP I just install it? Sorry for noob question but i'm new here
Click to expand...
Click to collapse
Magisk uninstaller will not works without custom recovery so i think my instruction is not applicable in this situation.
chaos_since_78 said:
Hi,
I'm running a HTC 10 with Lineage OS 15.1 (8.1.0). I came from Magisk 16 and an update message appeard. I downloaded Magisk 17 and tried to install it via TWRP as usual. The installation stopped with an Error 2. After that I had a boot loop and had to reinstall the Lineage OS. After that it booted again. But I still get this error message when trying to install Magisk 17.
Very odd. Besides of that, GREAT WORK!
Cheers
Click to expand...
Click to collapse
Double check if the package is not corrupted, MD5 should be: 6237bfaf7dcf516b60922b5b26f2dca8.

Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
Thanks for this
but now i can't install universal fix for safetynet check

I'm not sure if Magisk v.17.0 is fully backward compatible. Maybe this is preventing the module from installing?

Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
thank you very much i installed twrp and followed your steps worked great

Karls0 said:
I'm not sure if Magisk v.17.0 is fully backward compatible. Maybe this is preventing the module from installing?
Click to expand...
Click to collapse
ok so wait for new fix thanks

On my pixel 1 it claims to install, but causes a bootloop. AND updating to the most recent manager breaks using v16. So I'm stuck with an old manager and v16

Yes, the new manager seems to not fit to Magisk v16. In my case it also broke something so I updated to v17.

Karls0 said:
Magisk uninstaller will not works without custom recovery so i think my instruction is not applicable in this situation.
Double check if the package is not corrupted, MD5 should be: 6237bfaf7dcf516b60922b5b26f2dca8.
Click to expand...
Click to collapse
I got it solved by uninstallion the former Magisk package with the uninstaller. After reboot I could reinstall version 17 and until now it works fine. Thanks.

uninstaller for me does not flash for me. error 255 v16 same error and 17.1 wont flash either error 2

Thanks.
I'm able to do the steps without error. But then it is in bootloop. Using redmi note 4g (dior) Dot os

adz63 said:
uninstaller for me does not flash for me. error 255 v16 same error and 17.1 wont flash either error 2
Click to expand...
Click to collapse
Have you tried rebooting TWRP when the errors appear, and where are the logs?
barathrr96 said:
Thanks.
I'm able to do the steps without error. But then it is in bootloop. Using redmi note 4g (dior) Dot os
Click to expand...
Click to collapse
Is this on a clean install of Magisk v17.1? Also, logs...

Didgeridoohan said:
Have you tried rebooting TWRP when the errors appear, and where are the logs?
Is this on a clean install of Magisk v17.1? Also, logs...
Click to expand...
Click to collapse
Thanks.. the device does not belong to me..
for the time being I have installed magisk v16.7 and did installed viper and removed it ..
so when I get the device next time in my hand I will try to flash and take logs..

Bootloop - New fi Moto x4

I've just gotten my new fi Motorola x4 running Android 8.1.0 today. I've unlocked the boot loader via Motorola and I've rooted the device via Magisk. Since I had the Xposed framework on my old phone and loved some of the modules I wanted it on my new phone. Downloaded the Xposed Installed from the playstore, gave it root access with Magisk and attempted to install the framework. Phone is now stuck in a bootloop and it's been alternating between the androidone and motorola screens for about 45 minutes.
I tried to flash xposed-uninstaller-20180117-arm64.zip but got an error that it couldn't mount /system. Another page on the net had me holding down the power button and then spamming it ten times to tell Xposed no to load but that didn't seem to do anything at all. I created a disabled file as suggested on some sites but that did nothing to stop the bootloop:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
I actually had to make the /conf directory manually since it wasn't there. Wiped the cache with no better results. Factory reset did nothing to improve the situation and I was unsuccessful with sideloading the Xposed disabler found here:
https://android.gadgethacks.com/how-to/xposed-101-temporarily-disable-xposed-fix-bootloop-0179446/
It's hard for me to grasp how a completely empty barebones android phone which has only been rooted using Magisk with no other actions taken or software installed can be be stuck in a bootloop trying to perform a standard install using the Xposed installer. Not sure you can find a cleaner environment than the one on my phone.
Anyway if anyone has thought I'd love to hear them. I can boot to TWRP without issue and my phone is visible to both fastboot and adb.
Thank you!

Laugh this is just getting worse. I uninstalled Magisk and now the phone boots straight into recovery whenever I restart it. I'd flash a stock rom but I can't find one. I think I'm in trouble...

Reinstalled Magisk and it at least tries to boot up again but it just loops.

Arsenal420 said:
I've just gotten my new fi Motorola x4 running Android 8.1.0 today. I've unlocked the boot loader via Motorola and I've rooted the device via Magisk. Since I had the Xposed framework on my old phone and loved some of the modules I wanted it on my new phone. Downloaded the Xposed Installed from the playstore, gave it root access with Magisk and attempted to install the framework. Phone is now stuck in a bootloop and it's been alternating between the androidone and motorola screens for about 45 minutes.
I tried to flash xposed-uninstaller-20180117-arm64.zip but got an error that it couldn't mount /system. Another page on the net had me holding down the power button and then spamming it ten times to tell Xposed no to load but that didn't seem to do anything at all. I created a disabled file as suggested on some sites but that did nothing to stop the bootloop:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
I actually had to make the /conf directory manually since it wasn't there. Wiped the cache with no better results. Factory reset did nothing to improve the situation and I was unsuccessful with sideloading the Xposed disabler found here:
https://android.gadgethacks.com/how-to/xposed-101-temporarily-disable-xposed-fix-bootloop-0179446/
It's hard for me to grasp how a completely empty barebones android phone which has only been rooted using Magisk with no other actions taken or software installed can be be stuck in a bootloop trying to perform a standard install using the Xposed installer. Not sure you can find a cleaner environment than the one on my phone.
Anyway if anyone has thought I'd love to hear them. I can boot to TWRP without issue and my phone is visible to both fastboot and adb.
Thank you!
Click to expand...
Click to collapse
https://magiskroot.net/uninstall-magisk-module-twrp/
https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
In summary:
Step 1: Download the flasheable zip file from the Magisk module uninstaller from the following link to the PC
Step 2: Send the zip file to the SD card of the phones or to the internal memory using MTP (most of the recovery of TWRP is compatible with this method)
Step 3: Now, touch the Install button and choose the Zip file of the uninstaller of the Magisk module that you want to update.
Step 4: After the completion of the installation. Go back to the TWRP home page.
Step 5: Tap the advanced option from the TWRP homepage. Choose the terminal option now.
Step 6: Type uninmod in the terminal box and touch the input button.
Step 7: Now, you can see the list of Modules and you have to type the Number you want to uninstall (Check the screenshot below)
Step 8: Finally, the magisk module will be completely uninstalled.

Arsenal420 said:
. Downloaded the Xposed Installed from the playstore,
Click to expand...
Click to collapse
What xposed installer in playstore, playstore is not where xposed is gotten from...at all. The closest thing to it that I found is an asian trick your friends app.

Nergal di Cuthah said:
What xposed installer in playstore, playstore is not where xposed is gotten from...at all. The closest thing to it that I found is an asian trick your friends app.
Click to expand...
Click to collapse
You are right I got the apk from here:
https://forum.xda-developers.com/showthread.php?t=3034811
Do you have anything additional to offer?

Arsenal420 said:
You are right I got the apk from here:
https://forum.xda-developers.com/showthread.php?t=3034811
Do you have anything additional to offer?
Click to expand...
Click to collapse
Ok good, I got scared for you a bit there, my post was not meant to be mean spirited but maybe you read it as such. As far as the bootloop i'm afraid i'll be no help.

Help! Need to Uninstall Magisk Modules. Stuck in a Bootloop When Magisk is Activated.

I've flashed the new Lineage 18 on my Samsung Galaxy S10E Exynos and had trouble installing Magisk. I managed to get it installed somehow and tried adding a bunch of Magisk modules, some of which failed.
After rebooting, it booted up and stayed alive for a while before cutting to the bootanim and getting stuck in a loop. Disabling Magisk by flashing the old recovery.img solved it for me, but everytime I try to get Magisk to work again, it gets stuck in a loop after booting up the first time.
Help! Will uninstalling all the modules solve this issue and if it will, how do I go about doing it.
Any/all solutions much appreciated.
Thanks!

To delete a magisk module causing bootloop. Boot to TWRP, then go to advanced/file manager/data/adb/modules. U will see all magisk modules there. Delete the one that you think is causing the bootloop.
This is for my s10, I'm not sure if it's the exactly the same for s10e.

XTrail02 said:
To delete a magisk module causing bootloop. Boot to TWRP, then go to advanced/file manager/data/adb/modules. U will see all magisk modules there. Delete the one that you think is causing the bootloop.
This is for my s10, I'm not sure if it's the exactly the same for s10e.
Click to expand...
Click to collapse
Worked like a charm! Thank you

XTrail02 said:
To delete a magisk module causing bootloop. Boot to TWRP, then go to advanced/file manager/data/adb/modules. U will see all magisk modules there. Delete the one that you think is causing the bootloop.
This is for my s10, I'm not sure if it's the exactly the same for s10e.
Click to expand...
Click to collapse
is it possible somehow to do this with the stock recovery. I can boot with out magisk just fine, but if i enabled it stuck at booting forever. I like to avoid reflashing / Factory resetting.

playfsx said:
is it possible somehow to do this with the stock recovery. I can boot with out magisk just fine, but if i enabled it stuck at booting forever. I like to avoid reflashing / Factory resetting.
Click to expand...
Click to collapse
figure it out.
turn off the phone
open a shell and type: adb wait-for-device shell magisk --remove-modules
boot with magisk enabled.
your phone should reboot and in the next boot you should have a clean magisk with out modules.

playfsx said:
figure it out.
turn off the phone
open a shell and type: adb wait-for-device shell magisk --remove-modules
boot with magisk enabled.
your phone should reboot and in the next boot you should have a clean magisk with out modules.
Click to expand...
Click to collapse
You just saved me an evening reflashing and setting up all **** again.

Stuck in Download mode bootloop after updating from v20.x to v21.x

Phone Model no : Samsung Galaxy S6 / SM-G920F
Security patch date: 01.10.2017
Android version: 7.0
Root status: Yes
Hey guys,
I rooted my phone several weeks ago for the first time via odin and everything went fine. I installed TWRP and Magisk and everything worked out.
Today I was trying to update Magisk from v20.x to v21.x with the inapp option, but now im stuck in a bootloop to download mode, screen says "Downloading... do not turn off target".
Even if I turn the phone off with Power + Home + Vol Down its just restarting right away and getting stuck in the same screen again.
Im still able to enter TWRP Recovery, but I dont know what to do to end the download mode problem when trying to start the phone.
I actually dont know/understand much about that stuff, so I dont know which other info I need to provide.
Is there something I could do without going through the whole flash/root process again?
should i try to delete magisk and install it again? if yes, how do i do it?
Help would be appreciated.

n00btuber said:
Phone Model no : Samsung Galaxy S6 / SM-G920F
Security patch date: 01.10.2017
Android version: 7.0
Root status: Yes
Hey guys,
I rooted my phone several weeks ago for the first time via odin and everything went fine. I installed TWRP and Magisk and everything worked out.
Today I was trying to update Magisk from v20.x to v21.x with the inapp option, but now im stuck in a bootloop to download mode, screen says "Downloading... do not turn off target".
Even if I turn the phone off with Power + Home + Vol Down its just resarting right away and getting stuck in the same screen again.
Im still able to enter TWRP Recovery, but I dont know what to do to end the downloading problem when trying to start the phone.
I actually dont know/understand much about that stuff, so I dont know which other info I need to provide.
Is there something I could do without going through the whole flash/root process again?
should i try to delete magisk and install it again? if yes, how do i do it?
Help would be appreciated.
Click to expand...
Click to collapse
I don't know much about your device but if you can enter TWRP, it's not that bad. First what you can try is to download Magisk uninstaller and flash it in TWRP from USB. However, I don't know what can you do to update Magisk safely. Would be best if you can check your device forum or ask the question there

Lord Sithek said:
I don't know much about your device but if you can enter TWRP, it's not that bad. First what you can try is to download Magisk uninstaller and flash it in TWRP from USB. However, I don't know what can you do to update Magisk safely. Would be best if you can check your device forum or ask the question there
Click to expand...
Click to collapse
Looked like my device forum is pretty dead, which is why I asked the question here again. Thanks for the fast respone
Its probably not possible to just install a Magisk version again and overwrite the current one, probably need to uninstall first and then install it again?
There is a Magisk Module Uninstaller and a Magisk Uninstaller. Are those different things or just the same?
How to Uninstall Magisk Module Using TWRP Recovery | MagiskRoot
Uninstall Magisk Module using TWRP Recovery or Offline whenever you stuck into bootloop. Magisk Module Uninstaller and Magisk Manager for Recovery methods.
magiskroot.net
How to Uninstall Magisk From Android [2 Easiest Method]
Are you facing issues with Magisk? You can uninstall magisk from your phone with these simple and easy steps.
magiskmanager.com
Because the 2nd guide says in the end
Keep in Mind – Whenever you use TWRP as a method to uninstall Magisk, it is imperative to flash the Magisk Module Uninstaller Zip onto your device.
Does this mean I need to do the magisk module one first?

@n00btuber Do not trust those websites. They're in no way official and are just trying to get adc revenue from Magisk's popularity. If you're really unlucky they'll also provide you with malicious zips...
Only download stuff from John's GitHub:
https://github.com/topjohnwu/Magisk

If you need to uninstall Magisk use the uninstall zips from the above linked Github repo, and if you need to uninstall modules (but those will also be removed by the Magisk uninstaller) you can do that directly from TWRP:
https://www.didgeridoohan.com/magisk/Magisk#hn_Uninstalldeletedisable_modules_from_recovery
A lot of times you can just flash another Magisk version over your installed one, but there are times where you do need to uninstall first. Since you have TWRP it can't really hurt to just try flashing whatever Magisk zip you want and it it doesn't work you can just use the uninstaller first.
One other thing to try would be the Canary release, mainly to see if you're affected by any bugs that is present in the current stable release but has been fixed upstream. You'll find the Canary app in the same Github link above.

Didgeridoohan said:
@n00btuber Do not trust those websites. They're in no way official and are just trying to get adc revenue from Magisk's popularity. If you're really unlucky they'll also provide you with malicious zips...
Only download stuff from John's GitHub:
https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
Ok.
Was trying to use the uninstaller from his GitHub.
Trying to flash it leads to
"Updater process ended with ERROR:1
Error installing Zip file .....
Updating partition details"
So what to do now?
Trying to just flash any Magisk version to overwrite the current one leads to the same result.

I think it says Unsupported/Unknown image format

Your TWRP might be bugged/incompatible. I'd reflash your stock boot image and then patch the file manually (you'll find the instructions for that on GitHub as well).

Didgeridoohan said:
Your TWRP might be bugged/incompatible.
Click to expand...
Click to collapse
But TWRP worked fine when installing magisk the first time, I even tried the same zip folder I used to install it back then, but it wont work anymore.
Didgeridoohan said:
I'd reflash your stock boot image and then patch the file manually (you'll find the instructions for that on GitHub as well).
Click to expand...
Click to collapse
However, whats my stock boot image and how to reflash it? Cant find a guide for that on GitHub.
Would a Factory Reset wipe all Magisk stuff and my TWRP Partition as well?

Does anyone know what is going on between Magisk and Google? It seems Google has removed Magisk Manager from the Play Store AGAIN! What's more, I downloaded and installed the apk but when I try to use it to install the latest Magisk the install fails. Tried installing the Magisk zip via TWRP, and while it doesn't show any errors, I still don't have root.

Ok I really need some more help @Didgeridoohan
Meanwhile I tried to reinstall TWRP from within TWRP. There was no error so I think it should have worked, but didnt solve the problem.
As soon as I try to boot the system it directly boots download mode and gets stuck in it. The volume buttons wont work or do anything as they are supposed in download mode.
Im still able to get into TWRP, but I still dont know what to do to stop this crashed download mode that starts over and over again.
When trying to flash the magisk uninstall it states "cannot access /data", when trying to flash a magisk installer it states "unsupported/unknown image format"
I dont care about Magisk right now though, I can root and install magisk again as soon as im able to clear the download mode problem. I was just trying this because trying to update magisk from within magisk manager has caused this download mode problem to appear.
Just tell me please how to fix that or how to factory reset my phone so it is able to boot regular again.
Thank you

n00btuber said:
Ok I really need some more help @Didgeridoohan
Meanwhile I tried to reinstall TWRP from within TWRP. There was no error so I think it should have worked, but didnt solve the problem.
As soon as I try to boot the system it directly boots download mode and gets stuck in it. The volume buttons wont work or do anything as they are supposed in download mode.
Im still able to get into TWRP, but I still dont know what to do to stop this crashed download mode that starts over and over again.
When trying to flash the magisk uninstall it states "cannot access /data", when trying to flash a magisk installer it states "unsupported/unknown image format"
I dont care about Magisk right now though, I can root and install magisk again as soon as im able to clear the download mode problem. I was just trying this because trying to update magisk from within magisk manager has caused this download mode problem to appear.
Just tell me please how to fix that or how to factory reset my phone so it is able to boot regular again.
Thank you
Click to expand...
Click to collapse
Sounds to me like you need to reflash your ROM, not TWRP. According to your OP, you're running Android 7, but it doesn't say if it is stock or a custom ROM.. If it is stock, then use Frija.exe to download the ROM and then flash th AP, BL and HOME_CSC md5 files with Odin. If it is a custom ROM, use TWRP to flash the ROM and gapps. DO NOT try to flash Magisk. Right now there seems to be a problem with Google disabling Magisk. Wait till it is resolved before attempting to get root.

@n00btuber Dirty flashing your ROM is most likely the way to go, just like described above.
But @lewmur, what do you mean by "Google disabling Magisk"? If you're talking about SafetyNet there are ways around that (and it doesn't affect root)...

Didgeridoohan said:
@n00btuber Dirty flashing your ROM is most likely the way to go, just like described above.
But @lewmur, what do you mean by "Google disabling Magisk"? If you're talking about SafetyNet there are ways around that (and it doesn't affect root)...
Click to expand...
Click to collapse
I not talking about safety net. Look in Play Store for Magisk Manager. It is no longer there. And even if you download and install the apk, it won't install Magisk. Flashing Magisk from TWRP doesn't give root privileges. This just happened yesterday.

lewmur said:
I not talking about safety net. Look in Play Store for Magisk Manager. It is no longer there. And even if you download and install the apk, it won't install Magisk. Flashing Magisk from TWRP doesn't give root privileges. This just happened yesterday.
Click to expand...
Click to collapse
The Magisk Manager hasn't been on the Play Store for years... Edit: reference - https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/post-72508849
Nothing of what you describe has anything to do with Google "disabling Magisk".

Didgeridoohan said:
The Magisk Manager hasn't been on the Play Store for years... Edit: reference - https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/post-72508849
Nothing of what you describe has anything to do with Google "disabling Magisk".
Click to expand...
Click to collapse
That 's my mistake. Play Store would put up a lot of "Magisk Manager" stuff, but I never really tried any of it because flashing Magisk would give me the Manager. But even that "stuff" no longer shows up.
Butt Magisk Manager still won't install Magisk. It will download the zip file, but when it attemps to install it, it get an error saying Unsupported/Unknown image format. If I flash it from TWRP, and then open Magisk Manager, it still says N/A under Installed for Magisk.

lewmur said:
Then why won't Magisk Manager install Magisk. It will download the zip file, but when it attemps to install it, it get an error saying Unsupported/Unknown image format. If I flash it from TWRP, and then open Magisk Manager, it still says N/A under Installed for Magisk.
Click to expand...
Click to collapse
That will be an incompatibility between Magisk and your device and has nothing to do with Google (blame your OEM for doing weird stuff instead).

Thanks for the help guys, had to flash the ROM, now its working again.