Bootloop - New fi Moto x4 - Xposed General

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.

Related

SuperSU & CM13

Is it actually possible to make SuperSU work on CM13 without bricking your device etc?
I have spent the last 2 days googling this and reading various (mostly old, outdated) posts about how it's a bad idea or maybe not, but they are typically from 2.5x or 2.6x or earlier SuperSU versions.
My tablet, the only actively developed non-stock rom available for it is CM13. That is literally it.
However, I would like to have SuperSU features, especially compatibility with SUhide etc.
So, I am wondering if it's possible?
Do the current (2.78+) SuperSU versions play nice with CM13?
Can I just flash it in from the SuperSU app (I have bought pro version if that matters)? or Flashfire? or from TWRP recovery, whichever way is best? And, do I need to do anything else first?
Wellll, I went ahead and did it. Happy to report everything's working fine. So that's that.
DryEagle said:
Wellll, I went ahead and did it. Happy to report everything's working fine. So that's that.
Click to expand...
Click to collapse
Wanna share how you did it ?
. . . I'm running the latest CyanogenMod 13 om my GT-N5100 ( Samsung galaxy note 8 ) and can't get i to work without bricking the device.
Warlock_SVG said:
Wanna share how you did it ?
. . . I'm running the latest CyanogenMod 13 om my GT-N5100 ( Samsung galaxy note 8 ) and can't get i to work without bricking the device.
Click to expand...
Click to collapse
Well, I downloaded the latest supersu zip (2.78), installed the supersu app from market, installed supersu pro from market (i already bought this long ago), then used flashfire to flash the zip. and it just worked. i'm using latest cm13 nightly on nvidia shield.
Got it working I downloaded "BETA-SuperSU-v2.77-20160827190633.zip" and Installed it in TWRP, systemless mode.
Warlock_SVG said:
Got it working I downloaded "BETA-SuperSU-v2.77-20160827190633.zip" and Installed it in TWRP, systemless mode.
Click to expand...
Click to collapse
you can download 2.78 zip here: https://download.chainfire.eu/1001/SuperSU/UPDATE-SuperSU-v2.78-20160905010000.zip the 2.76 or 2.77 had some problem, dont remember which one, but 2.78 is completely solid
How do I install SuperSU in "systemless mode"? I have a google nexus 10 running the latest CM13 Release + gapps.
[Lemmy] said:
How do I install SuperSU in "systemless mode"? I have a google nexus 10 running the latest CM13 Release + gapps.
Click to expand...
Click to collapse
I used supersu-v2.78-201609011115 for my CM13 devices http://forum.supersu.com/topic/152/supersu-v2-78-release/2 the installer decide if it needs to be installed in "systemless mode" so no need to worry about that
You might need to install the SupperSU app from the store yourself.
Warlock_SVG said:
I used supersu-v2.78-201609011115 for my CM13 devices http://forum.supersu.com/topic/152/supersu-v2-78-release/2 the installer decide if it needs to be installed in "systemless mode" so no need to worry about that
You might need to install the SupperSU app from the store yourself.
Click to expand...
Click to collapse
does that work with the "official cyanogen recovery" as well, or should I install TWRP first?
...ok with the cyanogen recovery it did _not_ work, the installer said something about "patching sepolicy failed".
Any other suggestions?
[Lemmy said:
;68885779]does that work with the "official cyanogen recovery" as well, or should I install TWRP first?
...ok with the cyanogen recovery it did _not_ work, the installer said something about "patching sepolicy failed".
Any other suggestions?
Click to expand...
Click to collapse
Install twrp.
Spent my 6 hours in trying this crap.....after installation, my phone doesn't reboot rather says "secure boot error" installed cm13 6 times and faced the same problem.....now I won't install it unless I get a tested and confirmed procedure
Will follow-up with you on the next post...
ALI EHTISHAM BUKHARI said:
Spent my 6 hours in trying this crap.....after installation, my phone doesn't reboot rather says "secure boot error" installed cm13 6 times and faced the same problem.....now I won't install it unless I get a tested and confirmed procedure
Click to expand...
Click to collapse
Here's what I do to get my S3 going...
With the latest TWRP as always since running into issues with flashing when i had CWM quite some time ago.
There are 3 files i place in my external MicroSD...
CM13, Open Gaaps for Android 6 (i use the pico) and the SuperSU 2.78 SR1 zip file directly from the official website (though 2.76 should work).
First, when in TWRP, select wipe then advanced then the top 5 selections leaving the bottom 2 alone. When completed, hit the bottom center home selection to go into the main menu. Again, select wipe then select the data option to the right of the advanced tab you were in before. It requires you to type yes then proceed. Once that is done, go back to the main menu and be sure you do this exactly! Select the reboot and then recovery. Once your back into the TWRP recovery then select install and go to the MicroSD card with the 3 files... Now select the order of files to flash beginning with CM13 then add zip then the GApps then add zip then the SuperSU then begin the flash process. Be sure to wipe the dalvik cache then reboot the system.
SuperSU reboots it again shortly afterwards as part of its installation process.
Once your all done setting up the initial system setup you should go directly to the SuperSU app to set up what you need to.
Though my personal procedure is a bit more involved, this is as basic as it gets.
For your specific system, i can't say that i have ever even used it so please pardon me deeply if I left anything out and if someone can chime in with anything else, I'm sure it would be much appreciated.
Good luck.

Galaxy S7 stuck at booting after 14->15 upgrade

I've let the MagiskManager upgrade Magisk from 14.x to 1.50. Then I rebooted the phone, and then it was stuck at the pulsating SAMSUNG logo.
So, next step would be obvious: get into TWRP and install Magisk 14.0.
And so I did, and so it failed. This time I got a bootloop. The "Galaxy S7 powered by Android" thing appears for a few seconds, and then vibrates and starts over. And over, and over, and over.
So then, I "installed" the Magisk Uninstaller. Thinking to get rid of all traces of Magisk that introduced this problem in the first place.
So I did, and now I'm back at the first problem: stuck at booting.
Then installing Magisk 14 AND wiping cache&dalvik: boot loop
Then I installed the uninstaller again, then Magisk 15, and wipe the cache&dalvik. And it's back at being stuck while booting again.
Brilliant. What do I do to fix this?
Are you using a custom ROM, or a port ROM, or a custom kernel?
It's all stock, except for it being rooted.
I'm having the same issue. Canadian S7 W8, Stock ROM with root, Magisk 14, upgraded to 15 using direct install through magisk manager.
Yes, exactly that. No offense, but that's helping neither yourself nor me nor anyone else. Have you been able to figure anything out?
Maybe how to produce some kind of log output?...
Same thing happened to me just now. Never would have thought that upgrading through the Magisk app would cause this. I've tried all of the above and have also tried installing v 12.0 but still no dice.
I even tried a factory reset and still no dice. This is seriously infuriating.
Guess I will have to reflash everything and start fresh. If anyone else has any other ideas I'm all ears.
I'd like to know what the phone is actually *doing* when it's stuck. How can we get to know this?
`fastboot logcat` and `adb logcat` both keep waiting for a device that will not connect. Something does connect, christ knows what, but certainly no adb or fastboot device.
@fattyspecial
"reflash everything and start fresh" can you explain what exactly this comprises? What should I do?
thany2 said:
I've let the MagiskManager upgrade Magisk from 14.x to 1.50. Then I rebooted the phone
...
What do I do to fix this?
Click to expand...
Click to collapse
Mate 8 running 7.0 stock except rooted, running Magisk 14, did the same thing and I'm in the same boat. Have also tried removing magisk, reinstalling 14 no dice. Have not factory reset yet (trying everything else before that step) but it looks like it won't help.
thany2 said:
I'd like to know what the phone is actually *doing* when it's stuck. How can we get to know this?
`fastboot logcat` and `adb logcat` both keep waiting for a device that will not connect. Something does connect, christ knows what, but certainly no adb or fastboot device.
@fattyspecial
"reflash everything and start fresh" can you explain what exactly this comprises? What should I do?
Click to expand...
Click to collapse
Completely reflash the entire stock rom with ODIN and then re-root and reconfigure my entire phone. About the biggest bother imaginable.
I'm trying to re-flash only a new boot.img (or new kernel) through twrp right now. If I can get that to work I'll let you know right away.
---------- Post added at 03:10 AM ---------- Previous post was at 02:29 AM ----------
FIXED IT!
Ok here's what I did. Maybe not a perfect solution but I am out of bootloop and phone is working and root is working too.
I had to install a custom kernel. I'm guessing this replaces the corrupted boot.img file. So you will need to be rooted and have a custom recovery like TWRP.
Go to https://forum.xda-developers.com/galaxy-s7/development/kernel-tgpkernel-t3462897 and scroll down to the part that says: DOWNLOAD VIA ANDROIDFILEHOST for N version and download the zip file.
Transfer the TGPKernel zip to your external SD card (either with android file transfer if on mac like me or with an SD card reader).
Flash the zip in TWRP.
It will take a LONG time to reboot. Don't worry.
I chose to install root with Magisk and it ended up updating it to v15.0 and so far everything seems to be working well.
Hope this helps. That took a long time to figure out. Time for bed.
Ok, I'm still not in that loop... yet.
Ok, I'm still not in that loop... yet.
I selected installing the 15.0 Magisk zip file (from 14.0) using direct install, then did the reboot and I'm stuck at the pulsating SAMSUNG logo.
Can I do the same fix of fattyspecial without loosing anything on the S7?
I did the exact Magisk 15.0 zip update on my LG Nexus 5, with no problem, in less than a minute.
I'm still not in that loop... yet.
ct1aic said:
Ok, I'm still not in that loop... yet.
I selected installing the 15.0 Magisk zip file (from 14.0) using direct install, then did the reboot and I'm stuck at the pulsating SAMSUNG logo.
Can I do the same fix of fattyspecial without loosing anything on the S7?
I did the exact Magisk 15.0 zip update on my LG Nexus 5, with no problem, in less than a minute.
Click to expand...
Click to collapse
Ok, I tried that soluction and it worked. I didn't loose anything and I have now Magisk 15.0 installed and still rooted/SafetyNet OK
Thanks, fattyspecial .
Happy New Year.
Rui
If you can' t solve download Magisk Uninstaller https://forum.xda-developers.com/attachment.php?attachmentid=4370032&d=1514240372
and Magisk 14.0 https://forum.xda-developers.com/attachment.php?attachmentid=4264532&d=1504713887
Then reboot in Twrp (hope you have it) and flash
1 uninstaller
2 14.0
I had the magisk 14.5 and I installed the 15 via twrp on top, and it updated normal. Is there a problem updating this way?
@fattyspecial
I don't see why installing a custom kernel is a viable fix. Or a good idea. It seems random.
Maybe you can explain why this is a fix, and how the stock kernel makes the phone bootloop?
@Tribal123
I think you will find I've already tried it. I appreciate your contribution, but please do read my topic start.
Same here, updated from v14 to v15 and got a nice bootloop.
Huawei Mate 8 with Nougat (stock) and TWRP.
EDIT:
Solved!
Flashed my stock boot.img backup through TWRP, then booted my phone and downloaded v14, flashed v14 through TWRP, booted my phone again and downloaded v15 with Magisk Manager app and checked "Preserve AVB 2.0/dm-verity" and then tapped "Install" using "Direct Install (recommended)"
thany2 said:
@fattyspecial
I don't see why installing a custom kernel is a viable fix. Or a good idea. It seems random.
Maybe you can explain why this is a fix, and how the stock kernel makes the phone bootloop?
@Tribal123
I think you will find I've already tried it. I appreciate your contribution, but please do read my topic start.
Click to expand...
Click to collapse
Because a custom kernel disables dm-verity. There's an issue, mainly on Samsung devices, with the dm-verity detection in Magisk v15.0. It's under investigation...
Meanwhile, flash a dm-verity disabler together with Magisk v15.0 and you should be good to go.
I'm fairly certain you need a custom kernel. I'm also on the S7 and without one I've always boot looped, I think it has to do with dm-verity.
EDIT: I didn't notice there was a second page so I guess I didn't really say anything new, oh well, sorry!
ct1aic said:
Ok, I tried that soluction and it worked. I didn't loose anything and I have now Magisk 15.0 installed and still rooted/SafetyNet OK
Thanks, fattyspecial .
Happy New Year.
Rui
Click to expand...
Click to collapse
Awesome! Glad it worked. Happy new year.
---------- Post added at 04:22 AM ---------- Previous post was at 04:15 AM ----------
thany2 said:
@fattyspecial
I don't see why installing a custom kernel is a viable fix. Or a good idea. It seems random.
Maybe you can explain why this is a fix, and how the stock kernel makes the phone bootloop?
@Tribal123
I think you will find I've already tried it. I appreciate your contribution, but please do read my topic start.
Click to expand...
Click to collapse
Hey man. I'm just telling you what worked for me. If you don't want to try it then don't.
fattyspecial said:
Completely reflash the entire stock rom with ODIN and then re-root and reconfigure my entire phone. About the biggest bother imaginable.
I'm trying to re-flash only a new boot.img (or new kernel) through twrp right now. If I can get that to work I'll let you know right away.
---------- Post added at 03:10 AM ---------- Previous post was at 02:29 AM ----------
FIXED IT!
Ok here's what I did. Maybe not a perfect solution but I am out of bootloop and phone is working and root is working too.
I had to install a custom kernel. I'm guessing this replaces the corrupted boot.img file. So you will need to be rooted and have a custom recovery like TWRP.
Go to https://forum.xda-developers.com/galaxy-s7/development/kernel-tgpkernel-t3462897 and scroll down to the part that says: DOWNLOAD VIA ANDROIDFILEHOST for N version and download the zip file.
Transfer the TGPKernel zip to your external SD card (either with android file transfer if on mac like me or with an SD card reader).
Flash the zip in TWRP.
It will take a LONG time to reboot. Don't worry.
I chose to install root with Magisk and it ended up updating it to v15.0 and so far everything seems to be working well.
Hope this helps. That took a long time to figure out. Time for bed.
Click to expand...
Click to collapse
Hello,
Here is the problem I personnaly had (solved now !) :
Initially, my wife had a G930F (samsung galaxy S7) and a Custom 7.0 rom (i think it was the "AlexNDR.G930FXXU2DRAG" rom...but I'm not sure at all because it was installed several months ago or even years) with TWRP as recovery and Magisk as root.
I saw that Magisk not working (since when ? I don't know because it was not my phone). So, I tried to update it via the Magisk application (the initial goal was to use then Titanium Backup).
Logically, the phone then rebooted to install the Magisk update... except that a Boot Loop appeared.
I then tried many things :
1° Downgrade or Upgrade the TWRP recovery to 3.0.0.0; to 3.2.2.0 and to 3.5.2.9.0 (thes recovery .img files are here: https://eu.dl.twrp.me/herolte/)
=> It didn't work, and the bootloop continued (but, at the end, i keep the TWRP v.3.5.2.9.0)
2° I tried to uninstall and reinstall Magisk
(cf. the "Custom Recovery" tuto here : https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root)
=> Failure. Still the BootLoop... (either with the .zip v19.1 or the .zip v23)
nb: I even tried to donwload other magisk files but still the same bootloop (cf.https://forum.xda-developers.com/t/collection-of-magisk-modules-v2.3575758/page-13#post-72542167)
4° I tried to change the kernel by using TGPKernel (https://forum.xda-developers.com/t/...2-30-tgpkernel-v6-15-5-3-18-140-esd2.3462897/)
=> Failure, the bootloop remained...
5° Finally, I found a solution :
a° I downloaded the rom "G930FXXU2DRAG_DevBase_v4.6.zip" (via the following tutorial here : https://forum.xda-developers.com/t/...vbase-v7-4-encryption-support-jul-10.3592914/)
, more exactly at the following location : https://androidfilehost.com/?fid=818070582850489124
b° Then, as indicated in the tuto (https://forum.xda-developers.com/t/...vbase-v7-4-encryption-support-jul-10.3592914/), I renamed the .zip downloaded on my PC to "G930FXXU2DRAG_DevBase_v4.6_rescue.zip" (ps: so, i add "..._rescue.zip)
c° After that, I copied the file "G930FXXU2DRAG_DevBase_v4.6_rescue.zip" on my micro SD.
d° In the recovery I finally installed the file "G930FXXU2DRAG_DevBase_v4.6_rescue.zip" and the phone restarted after a long time (or maybe 5 minutes, I didn't watch).
=> End of the bootloop and all data was preserved!!!

Magisk bricks my phone

I'm doing a clean install of this rom on my Samsung S4 using the Aroma installer (Note: problem not related to aroma - see edits below).
The installer has an option to use Privacy Guard (for phones with a locked bootloader), SuperSU, or Magisk.
If I install Magisk, the phone is stuck at the Samsung logo indefinitely. If I choose either of the other options, it boots fine.
I've tried a number of different ways around this:
1. Choosing the Magisk option in the Aroma installer.
2. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.0 afterwards.
3. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.0 with the updater-script modified (commenting out the two lines) afterwards.
4. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.6 afterwards.
5. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.6 with the updater-script modified (commenting out the two lines) afterwards.
All of the above options - every way I can think of - results in bricking the device.
Is there a way to make this work?
Edit:
1. I'm using TWRP 3.1.1.0, if it matters. And yes, my S4 has an unlocked bootloader (MDL).
2. The phone will boot fine if I choose the Aroma SuperSU option, but I discovered that SuperSU is not installing correctly either. It just doesn't brick my phone.
3. I tried running the NON-aroma rom installer. Then I used UnSU to remove the non-functioning SuperSU, and ran the Magisk 16.0 installer (normal one). Bricked.
Rebooted into recovery, ran the Magisk Uninstaller - it failed, saying "Magisk is not installed".
So I tried installing Magisk again - which installed with no errors. And then I immediately ran the uninstaller, and again it failed, saying that Magisk was not installed. Maybe that's a clue as to what's going on. Because it's clearly not related to the aroma installer anymore.
4. I added the recovery log. This shows me doing a wipe, installing the rom linked to above, flashing Magisk, then flashing the Magisk uninstaller so you can see it say that Magisk was never installed in the first place.
I've been having zero luck getting this to work. Does anyone have any ideas?
Maybe you should read this, https://forum.xda-developers.com/ap...7-universal-systemless-t3473445/post77014053, sounds like the issue you're having and apparently Armoa breaks Magisk install. Also go to general support thread and post logs, etc. You will get more help there.
yung40oz84 said:
Maybe you should read this, https://forum.xda-developers.com/ap...7-universal-systemless-t3473445/post77014053, sounds like the issue you're having and apparently Armoa breaks Magisk install. Also go to general support thread and post logs, etc. You will get more help there.
Click to expand...
Click to collapse
Thank you. However, as I stated above, although I started with the aroma installer, I eventually tried the non-aroma installer and had the exact same problem.
In addition, I also tried the normal versions as well as ones that had been patched as per the instructions on the link you posted.
So whatever is causing this does not appear to be aroma related.
Haphim said:
So I tried installing Magisk again - which installed with no errors. And then I immediately ran the uninstaller, and again it failed, saying that Magisk was not installed. Maybe that's a clue as to what's going on. Because it's clearly not related to the aroma installer anymore.
Click to expand...
Click to collapse
It would be interesting to see the recovery log from that...
It kind of sounds like there's some issue with your recovery. Have you tried letting the Manager patch your ROM's boot image and then flash that to your device manually?
Didgeridoohan said:
It would be interesting to see the recovery log from that...
It kind of sounds like there's some issue with your recovery. Have you tried letting the Manager patch your ROM's boot image and then flash that to your device manually?
Click to expand...
Click to collapse
I tried letting the Manager patch the boot image. I got the boot image by extracting it from the LineageOS rom. However, it would appear that the rom installer Loki's it on the fly, so the extracted rom by itself didn't pass the kernel signature check. This wouldn't be a problem if Magisk Lokied it during the patching process, but apparently it doesn't.
If there's an easy way to get the already lokied boot image off of my phone, I would appreciate being pointed in the right direction and I'll try it again. When installing Magisk, it allegedly backs up the boot image - if so, is there a way for me to recover it?
In any case, I went through the full routine all over again so that I could get the recovery log. I added it to the top post. It shows me doing a wipe, installing the LineageOS rom linked to in the top post, flashing Magisk, then flashing the Magisk Uninstaller immediately afterwards so that you can see it say that Magisk was never installed in the first place.
I just tried using TWRP 3.1.0.0 instead of 3.1.1.0 - no change.
Is there an easy way to extract the current boot.img (not the one from the rom installer, since that hasn't been Loki patched)? If so, I can try the patching through the app again.
Otherwise, if there are any other ideas, I would love to hear them.
Otherwise, I may have no choice but to buy a new phone if this one can no longer be rooted.

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.

Xposed for Android 8- help needed

Hello guys I recently rooted my xz premium dual sim and I currently have Magisk 22.1, I'm not an expert so
I need help please, what are a proper direct way to get xposed working properly on Android 8.0 ROM?
I mainly need to install XPrivacy, I tried to install EDXposed but it failed though and I'm not sure what to do
Thanks in advance
Since you need to install this with Magisk, do this:
Donwload the attached files
be sure to install the Xposed Magisk apk file first and open it it will show, thats it's not installed
then go to magisk and flash the xposed framework zip
and reboot
then (after your device is completely started with magisk and xposed) go to magisk, and check if the module's enabled. If it's NOT enabled, flash the zip again. If it's enabled, open xposed installer and check. (it's still not fully installed) and then there comes a message, that it's installed, but not really.
For the last step you need a custom recovery (like twrp or something)
Boot into your custom recovery and flash the xposed zip there (again)
Reboot and enjoy.
Another (way simpler) method would be to download it from magisk manager (if you have a older version) online repo.
I attached the Magisk version (with working repo)
In case xposed is installed but remains not active (yellow triangle instead of a green checkmark in the xposed installer app) follow the instructions of post #2 and don't worry you don't have to be an expert for this fix its fairly easy
Magisk + Xposed Framework is installed, but not active (XposedBridge.jar lacking)
Hi, new member here, who happened to lurk into XDA a few times in the past, and finally decided to register, hoping finding someone that would be able to help with my problem. I have Nexus 7 (2012), which became unusable with Android Lollipop...
forum.xda-developers.com

Categories

Resources