Hello !
I've tried to install Xposed with Magisk (the v3 beta version, notorious for provoking bootloops instead of the v4 which was the right one) and got stuck in a bootloop. I rebooted into TWRP and tried to restore a backup (system, system image, vendor image and ramdisk), and it still went in bootloop. I figured that, as Magisk was systemless, Magisk and Xposed were still there, so I flashed uninstall-magisk.zip.
Unfortunately, now I don't have access to TWRP (maybe flashing uninstall-magisk flashed the original erecovery over TWRP ?) and whenever I try to boot, I enter the eRecovery with written "Serious problems occured when the device boot" and the options I have are:
-Download latest version and recovery
-Wipe data/factory reset
-Reboot
-Shutdown
Should I use the "download latest version and recovery" ?
Should I try to flash TWRP with fastboot ?
I guess I can't do a factory reset since I updated before to BLA-L29 8.0.0.157(C432) from BLA-L29 8.0.0.120(C432) and downgrading seems to provoke a hard brick.
Thank you.
Edit: Thanks to ante0, I had access to TWRP (couldn't access it since USB was still connected). He suggested I use HuRUpdater TWRP script to update to the same build I have on my device now. I will report once, and if, I succeed in doing this. In the meantime, if anybody as ideas, I wouldn't mind hearing them !
Edit: Ante0 told me that I had to use the HuRUpdater TWRP script to update to the same build I was before bootlooping, so I did and everything went back to normal.
if u you want try xposed or any system less magisk modules be sure to have magisk manager for recovery mode
that's will ensure if u got bootloop to boot to recovery mode and only un tick xposed module or any module got ur devise to bootloop
FYI Xposed v90 beta 3 (which I think is the latest official build) is not compatible with EMUI 8.0 and will cause a bootloop. You need to install v90 beta 4.
https://forum.xda-developers.com/showpost.php?p=77269446&postcount=7439
https://github.com/rovo89/Xposed/issues/310
Antidote03 said:
if u you want try xposed or any system less magisk modules be sure to have magisk manager for recovery mode
that's will ensure if u got bootloop to boot to recovery mode and only un tick xposed module or any module got ur devise to bootloop
Click to expand...
Click to collapse
Didn't know that there was a Magisk Manager available for the recovery, if I succeed in unbricking the device I'll try it out before installing any Magisk Module, thanks !
thref23 said:
FYI Xposed v90 beta 3 (which I think is the latest official build) is not compatible with EMUI 8.0 and will cause a bootloop. You need to install v90 beta 4.
https://forum.xda-developers.com/showpost.php?p=77269446&postcount=7439
https://github.com/rovo89/Xposed/issues/310
Click to expand...
Click to collapse
I went on the official Magisk thread to get the latest build, absolutely forgetting about the v4 that I had seen on another thread a few hours before, unfortunately it was too late when I realized the mistake I had done by flashing the wrong version
Finally systemless Xposed works on Mate 10 Pro
thref23 said:
FYI Xposed v90 beta 3 (which I think is the latest official build) is not compatible with EMUI 8.0 and will cause a bootloop. You need to install v90 beta 4.
https://forum.xda-developers.com/showpost.php?p=77269446&postcount=7439
https://github.com/rovo89/Xposed/issues/310
Click to expand...
Click to collapse
MANY thanks indeed !! After days of searching on XDA and elsewhere...your link brought back Xposed on Ore0 8.0 Mate 10 Pro. Greatly appreciated.
Related
for some reason whenever I flash supersu or Magisk the phone just hangs at the MI logo with 7.6.15 global beta rom, I do the same flash method every time and this is the first time it has happened..
try 1
zcx twrp, flash 7.6.15, flash supersu, reboot and it doesnt boot
try 2
zcx twrp, flash 7.6.15, flash magisk, reboot and it doesnt boot
try 3
zcx twrp, flash 7.6.15, reboot, -boots fine
edit:
try 4 .
zcx twrp, flash 7.6.15, flash just supersu 2.82, reboot and it boots, so now I can say it has something to do with Magisk or Xposed
so I might now try to flash Magisk, but run the xposed uninstaller incase the magisk.img image still carries xposed module from previous installs this way I can narrow it down from xposed or magisk
I'm having the same issue. I try to flash Super SU after flashing MIUI 7.6.15 and I also try to flash Xposed but it hangs on the Mi logo and won't boot properly. If I hols the power button down for ten seconds to turn the phone off and then get to recovery mode by holding down the volume up button with the power button I can reflash MIUI and it works fine on its own. Wonder is it a Super SU issue? Might try an older version of MIUI....
Same issue, tried everything. :'(
Magisk and zcx super su working but not xppsed niether systemless nor solarwarez editon.
+1
just updated my phone via zcw twrp. su and magisk works fine, only xposed got me stuck at the logo.
No problem with magisk v12, boot normal
Problem with xposed v87, stuck in logo
now back to v7.6.7, and waiting for FIX
Flashed v87.1 xposed
Worked
adiversion said:
Flashed v87.1 xposed
Worked
Click to expand...
Click to collapse
Link?
Sent from my kenzo using XDA Labs
Flash the modified xposed, it's working with the latest global beta. Link:
https://forum.xda-developers.com/xposed/unofficial-xposed-miui-t3367634/page77
Btw: why u guys still use xposed? Any recommendations for modules except YouTube adaway which I should try?
the issue is with SuperSu 2.86, should flash Supersu 2.76, im in build 7.6.8+Supersu 2.76 and all works fine and Xposed not work fine in this builds
Systemless Root & SafetyNet working [GUIDE][Magisk][StockROM-6.0.1][SkyMelon][TWRP]
Hi XDA friends,
After quite investigation I finally have found the way to have our devices Systemless Rooted.
The main advantage? SafetyNet working on our rooted device. That means Google does not notice our device is rooted ...yes, you can play Nintendo games or use Android Pay as well!
View attachment 4371569 View attachment 4371476
Here is the step by step guide:
You Must Have: Unlocked bootloader, ADB Fastboot drivers and Flashtool installed.
- Flash Stock Android 6.0.1 ROM with Flashtool (Wipes checked). I recommend 26.3.A.1.33 for the E2303 model. You can find Stock ROMs in this post.
- Flash TWRP from ADB: "fastboot flash recovery recovery.img" (I tried with v3.0.2.0 and also the new v3.2.1-0 recently published here!)
- Flash custom kernel (SkyMelon 8.1 or 9 without-root) from TWRP. Download v8.1 from this post or v9 directly here: View attachment 9-20171210-no-root.zip. Wipe Dalvik/Cache after install it.
- Flash the latest version of Magisk with TWRP. Wipe Dalvik/Cache after install it. GitHub repo: https://github.com/topjohnwu/Magisk/releases
- Install the latest version of Magisk Manager.apk. GitHub repo: https://github.com/topjohnwu/MagiskManager/releases
- [Optional] In order to avoid flashing errors with TWRP it is recommended to update directly through Magisk Manager. If you want to install previous versions of Magisk (between v14.6 and v15.2), could be neccesary to check the box "Preserve AVB 2.0/dm-verity" before "Direct Install" it.
Note: Magisk v16.4 and Magisk Manager v5.7.0 was the last version working tested by me. From this version I will discontinue testing new Magisk releases on this device. Feel free to post your experience with the new ones
- This method is compatible with E2303, E2306 (reported by @zputnyq) and E2333 (reported by @Yester_Ko) models.
- Compatibility with Apps2SD reported by @tim_pear
Please if this works for you, thanks are very welcome to my first post! Also ideas or improvements to the post are welcome.
Credits:
- Special thanks to @osmank3 who built SkyMelon v9 without-root and help me with Magisk updates.
thanks for sharing your experience , I have A question what about DRM fix , did restore you TA backup ?
Hi! Thanks for your guide. Can you share your safety net check screen on magisk? I try that kernel and some other kernels with different magisk versions, but I don't understand safety net checking status.
Hi othmane.os,
I cannot provide information about restoring the TA. My warranty expired some time ago and I don´t have a TA backup.
Thanks for comment.
othmane.os said:
thanks for sharing your experience , I have A question what about DRM fix , did restore you TA backup ?
Click to expand...
Click to collapse
Hi osmank3,
I have modified the post with the screenshot request and also with some links to the material used in the guide.
If you have any problem, I will be glad to help you. Thanks for comment.
osmank3 said:
Hi! Thanks for your guide. Can you share your safety net check screen on magisk? I try that kernel and some other kernels with different magisk versions, but I don't understand safety net checking status.
Click to expand...
Click to collapse
I want to use your guide but I'm busy to do current configuration of my phone. I delete some files on my system partition for gaining storage (I copied some new versions of upgraded apps to system partition) This take my time but I haven't got enough.
I use skymelon 9 kernel, with supersu. I guess because of supersu changed system partition and safetynet fails. I dislike supersu app but skymelon 9 comes with it. So I built skymelon 9 myself without supersu, but I didn't flash stock rom before installing skymelon 9 without-root and magisk. Now on my phone Magisk15 and skymelon9(compiled by me) installed. Magisk's hide function hiding itself from google apps and choosen apps but safetynet check fails.
Can you or anybody try this guide with skymelon 9 without-root which built by me?
View attachment 9-20171210-no-root.zip
Thanks
Hi osmank3,
I have tested the kernel that you built and it is working perfect. Thank you! This version has been added to the post and of course is menctioned your contribution.
I'm afraid you'll have to install a stock ROM...
BTW: I cannot get working Magisk v15. If I install it direclty from Magisk Manager the installation fails. If I install it through TWRP (and do wipes), the process is correct but when I check it, Magisk Manager not shows it as installed. So for the moment, it is only working for v14.5.
osmank3 said:
I want to use your guide but I'm busy to do current configuration of my phone. I delete some files on my system partition for gaining storage (I copied some new versions of upgraded apps to system partition) This take my time but I haven't got enough.
I use skymelon 9 kernel, with supersu. I guess because of supersu changed system partition and safetynet fails. I dislike supersu app but skymelon 9 comes with it. So I built skymelon 9 myself without supersu, but I didn't flash stock rom before installing skymelon 9 without-root and magisk. Now on my phone Magisk15 and skymelon9(compiled by me) installed. Magisk's hide function hiding itself from google apps and choosen apps but safetynet check fails.
Can you or anybody try this guide with skymelon 9 without-root which built by me?
View attachment 4371416
Thanks
Click to expand...
Click to collapse
GameBoy1989 said:
BTW: I cannot get working Magisk v15. If I install it direclty from Magisk Manager the installation fails. If I install it through TWRP (and do wipes), the process is correct but when I check it, Magisk Manager not shows it as installed. So for the moment, it is only working for v14.5.
Click to expand...
Click to collapse
I'm using magisk manager to patch boot.img with v15. I flash patched_boot.img with TWRP. It is working.
When I update it from v14.5 /data/magisk link crashing. I delete /data/magisk and upgrade on magisk manager as recommended type and reboot system, it is starting to work.
Ups! I forget to say. Check AVB 2.0/dm-verity
It works
Thank you very much. Post updated!
osmank3 said:
I'm using magisk manager to patch boot.img with v15. I flash patched_boot.img with TWRP. It is working.
When I update it from v14.5 /data/magisk link crashing. I delete /data/magisk and upgrade on magisk manager as recommended type and reboot system, it is starting to work.
Ups! I forget to say. Check AVB 2.0/dm-verity
Click to expand...
Click to collapse
Hey, i downloaded Magisk v14.5 and tried to flash it with twrp but i got error "invalid zip file format" What should i do now or what did i do wrong?
Yay i got this work but little bit different way.
1. Flashed stock rom with flashtool. I downloaded my stock rom from XperiFirm.
2. Flashed TWRP with this guide.
3. Flashed Skymelon 8.1 with TWRP and wiped Dalvik/Cache after install.
4. Flashed Magisk v14.0 with TWRP from this post and wiped Dalvik/Cache after install.
When that was done i rebooted and Magisk and Magick manager was installed. They aren't latest versions so i updated them.
1. Downloaded latest Magisk manager from here and installed it.
2. From Magisk manager i checked "Preserve AVB 2.0/dm-verity" and installed it with choosing the recommended option "Direct Install"
Everything seems to working fine and i did this to my E2303 with 26.3.A.1.33
Great! Thanks for sharing :good:
Which is the difference between methods? I see that it also works for you by flashing Magisk v14.0.
Artsii said:
Yay i got this work but little bit different way.
1. Flashed stock rom with flashtool. I downloaded my stock rom from XperiFirm.
2. Flashed TWRP with this guide.
3. Flashed Skymelon 8.1 with TWRP and wiped Dalvik/Cache after install.
4. Flashed Magisk v14.0 with TWRP from this post and wiped Dalvik/Cache after install.
When that was done i rebooted and Magisk and Magick manager was installed. They aren't latest versions so i updated them.
1. Downloaded latest Magisk manager from here and installed it.
2. From Magisk manager i checked "Preserve AVB 2.0/dm-verity" and installed it with choosing the recommended option "Direct Install"
Everything seems to working fine and i did this to my E2303 with 26.3.A.1.33
Click to expand...
Click to collapse
GameBoy1989 said:
- Flash Magisk v14.5 from TWRP. Wipe Dalvik/Cache after install it. GitHub repo: https://github.com/topjohnwu/Magisk/releases
Click to expand...
Click to collapse
This was only thing i made differently. I didn't find right magisk there what would work when flashing because i had problem with "invalid zip file format" so i downloaded that magisk zip file from another place.
This worked fine for me but I directly tried flashing/installing latest version (15.1) from TWRP and later after booting via adb the .apk of the Manager.
Didn't show the Magisk as installed.
With making a backup in TWRP of the boot (just renaming it to .img it has a different extension in the name) and then modifying it (as Manager tells you when you want to install) I could make it work (flashing the modified boot image with fastboot).
(Other steps like flashing the stock ROM and the recovery worked as usual. Also no problems with installing the kernel in TWRP.)
If you try to flash directly the last Magisk version (v15.1 in this case) I don´t know why yet but it doesn´t work. For that reason it is neccesary to first flash Magisk v14.5 (last version working with TWRP).
The way that you do it is also a very good one! Thanks for sharing @lordmd.
lordmd said:
This worked fine for me but I directly tried flashing/installing latest version (15.1) from TWRP and later after booting via adb the .apk of the Manager.
Didn't show the Magisk as installed.
With making a backup in TWRP of the boot (just renaming it to .img it has a different extension in the name) and then modifying it (as Manager tells you when you want to install) I could make it work (flashing the modified boot image with fastboot).
(Other steps like flashing the stock ROM and the recovery worked as usual. Also no problems with installing the kernel in TWRP.)
Click to expand...
Click to collapse
After magisk 14.6+ there is a problem about dm-verity. Magisk can't patch it, so we must preserve the original dm-verity. When you are applying magisk 14.6+ from twrp, you can't preserve and magisk can't patch it. The true way is using magisk manager and patch with preserve dm-verity.
Magisk 15.2 version notes says that problem solved but I try it, it is not solved yet.
My first applying procedure is:
First, patch skymelon 9 boot.img file with new magisk version also with preserve dm-verity on Magisk Manager,
Flash recovery and open with twrp
Apply skymelon 9 wipe dalvik and cache
Apply new magisk
Flash patched img
Let´s see if the next v15.3 beta finally works. Thanks @osmank3
BTW: Did you finally install the stock ROM or could you unroot your CFW for installing Magisk?
osmank3 said:
After magisk 14.6+ there is a problem about dm-verity. Magisk can't patch it, so we must preserve the original dm-verity. When you are applying magisk 14.6+ from twrp, you can't preserve and magisk can't patch it. The true way is using magisk manager and patch with preserve dm-verity.
Magisk 15.2 version notes says that problem solved but I try it, it is not solved yet.
My first applying procedure is:
First, patch skymelon 9 boot.img file with new magisk version also with preserve dm-verity on Magisk Manager,
Flash recovery and open with twrp
Apply skymelon 9 wipe dalvik and cache
Apply new magisk
Flash patched img
Click to expand...
Click to collapse
GameBoy1989 said:
Let´s see if the next v15.3 beta finally works. Thanks @osmank3
BTW: Did you finally install the stock ROM or could you unroot your CFW for installing Magisk?
Click to expand...
Click to collapse
I must flash system partition from stock Rom, after that safetynet passed.
Ty
Is pexorom better than stock. Is this going to work on pexorom.
Please reply
I´ve tried with Pexo Rom v3 and systemless root works with Magisk but it does not passed Safety Net check.
Sayan Qadri said:
Is pexorom better than stock. Is this going to work on pexorom.
Please reply
Click to expand...
Click to collapse
It seems it is impossible to get root with magisk on latest Oreo stock. Maybe someone found solution?
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
dolar4ik said:
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
Click to expand...
Click to collapse
its not work for me:crying:
Try to follow this guide then: https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
But use latest magisk beta instead of suggested 15.3.
And keep in mind that it is possible to easily restore working state with magisk uninstaller.
Do you have any errors during magisk or workaround installation in twrp console?
dolar4ik said:
Try to follow this guide then: https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
But use latest magisk beta instead of suggested 15.3.
And keep in mind that it is possible to easily restore working state with magisk uninstaller.
Do you have any errors during magisk or workaround installation in twrp console?
Click to expand...
Click to collapse
now its working for me.:highfive::highfive:
dolar4ik said:
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
Click to expand...
Click to collapse
Hi, does not work for me, stuck at bootloader logo, tried Magisk, followed the steps many times but nothing, can you help please ?
evnimaster said:
Hi, does not work for me, stuck at bootloader logo, tried Magisk, followed the steps many times but nothing, can you help please ?
Click to expand...
Click to collapse
follow this: https://forum.xda-developers.com/mot...reo-8-t3743273
Code:
echo keepverity=true>>/data/.magisk
echo keepforceencrypt=true>>/data/.magisk
Is there a way to remove encryption already?
Remove root?
Is it possible to remove root and the TWRP without hard reset? Does anyone already have the original recovery of Oreo?
DavidKalil10 said:
Is it possible to remove root and the TWRP without hard reset? Does anyone already have the original recovery of Oreo?
Click to expand...
Click to collapse
There is magisk uninstaller provided in official thread.
To remove twrp you just need to flush original recovery via fastboot
Hello guys, can I have some advice on whether I should install this latest Oreo update on my moto z, how is the battery doing on this update? And overall experience?
@dolar4ik
i reflash the stock oreo ROM,then flash TWRP,flash magisk,flash f2fs bug workaround, stuck at bootloader logo,how can i do it??
Flash the Magisk uninstaller, reboot to recovery (you have this option in TWRP) and flash again only the Magisk 16.3 (without the f2fs bug workaround). This worked for me two days ago.
Today I updated to the latest Magisk 16.4 without any problems.
lesbianu said:
Flash the Magisk uninstaller, reboot to recovery (you have this option in TWRP) and flash again only the Magisk 16.3 (without the f2fs bug workaround). This worked for me two days ago.
Today I updated to the latest Magisk 16.4 without any problems.
Click to expand...
Click to collapse
still not work for me.:crying::crying:
---------- Post added at 03:12 AM ---------- Previous post was at 02:58 AM ----------
This is strange. It works on Oreo OTA but it does not work in full flash Oreo ROM.
have anyone help me??
rakee said:
It works on Oreo OTA but it does not work in full flash Oreo ROM.
Click to expand...
Click to collapse
This is right.
I re-flashed my phone using the OPL27.76-51 firmware. Now, no way to install Magisk (old, new, any version).
The solution, I restored a TWRP backup made at the first bootloader unlock (when the ROM was updated only using OTAs, not flashed). Immediately I was able to install Magisk 16.4 - without any F2FS workaround.
HERE is my TWRP backup containing the partitions: Boot, Data & System. Hope it helps!
rakee said:
@dolar4ik
i reflash the stock oreo ROM,then flash TWRP,flash magisk,flash f2fs bug workaround, stuck at bootloader logo,how can i do it??
Click to expand...
Click to collapse
Uninstall magisk with it's own uninstaller.
I installed Magisk on the full Oreo release and everything is working.
I did make a "less bloat, less bs" zip version but I doubt it would make a change.
If you guys want, I can upload it when I get home.
The Marionette said:
I installed Magisk on the full Oreo release and everything is working.
I did make a "less bloat, less bs" zip version but I doubt it would make a change.
If you guys want, I can upload it when I get home.
Click to expand...
Click to collapse
Could you provide your twrp ZIP Version? That would be great.
lesbianu said:
This is right.
I re-flashed my phone using the OPL27.76-51 firmware. Now, no way to install Magisk (old, new, any version).
The solution, I restored a TWRP backup made at the first bootloader unlock (when the ROM was updated only using OTAs, not flashed). Immediately I was able to install Magisk 16.4 - without any F2FS workaround.
HERE is my TWRP backup containing the partitions: Boot, Data & System. Hope it helps!
Click to expand...
Click to collapse
Just got myself a hand me down Moto z.
My friend who gave it to me hasn't touch the phone for a year.
So i started with 6.0 and after multiple updates, now i am on Oreo.
Since i have done ota from Marshmallow, would this method work?
Bootloader was never unlocked.
thanks for any input
—Problem—
Boot loop... is there anyway to solve this problem without a reset?
—generel Infos—
Device: OnePlus 5 (rooted)
OS: oxygenos 9.0.3
Recovery: TWRP
Other: using EDXposed &
Nethunter Kernel
—the reason?—
I think it was the experimental setting in GravityBox Pie. There was a warning but I didn’t read it because ... I don’t know. The setting required a reboot but after that I stuck in the boot loop.
—what I ´ve tried—
I saw a guide on xda how to disable xposed modules via twrp. The problem was that I was using EDXposed. It was a different. But I deleted a similar file via twrp file manager ( /data/data/com.[IdontKnowTheExactPackgeName].xposed.manager/shared_prefs/[SomethingWithModules])
I tried to reboot but without success
I installed mm ( a for twrp to disable/enable magisk modules and more)
In mm I disabled the EDXposed Module und riru Core Module ( Im not sure if I was riru)
I tried to reboot but without success
I flashed magisk uninstaller and after flashing was done( magisk couldn’t restore boot image or something like that but the flash worked so I ignored it) I got the error: error creating fstab ( the same error occurred when wiping cache/dalvic)
I tried to reboot but without success
I wanted to flash EDXposed but it didn’t work because I haven’t magisk installed
So I flashed magisk again ( this solved the fstab error) and after that the EDXposed uninstaller. Both flashes worked
I tried to reboot but without success
Now I gave up and hope that you have an ansewer
Master Luca said:
—Problem—
Boot loop... is there anyway to solve this problem without a reset?
—generel Infos—
Device: OnePlus 5 (rooted)
OS: oxygenos 9.0.3
Recovery: TWRP
Other: using EDXposed &
Nethunter Kernel
—the reason?—
I think it was the experimental setting in GravityBox Pie. There was a warning but I didn’t read it because ... I don’t know. The setting required a reboot but after that I stuck in the boot loop.
—what I ´ve tried—
I saw a guide on xda how to disable xposed modules via twrp. The problem was that I was using EDXposed. It was a different. But I deleted a similar file via twrp file manager ( /data/data/com.[IdontKnowTheExactPackgeName].xposed.manager/shared_prefs/[SomethingWithModules])
I tried to reboot but without success
I installed mm ( a for twrp to disable/enable magisk modules and more)
In mm I disabled the EDXposed Module und riru Core Module ( Im not sure if I was riru)
I tried to reboot but without success
I flashed magisk uninstaller and after flashing was done( magisk couldn’t restore boot image or something like that but the flash worked so I ignored it) I got the error: error creating fstab ( the same error occurred when wiping cache/dalvic)
I tried to reboot but without success
I wanted to flash EDXposed but it didn’t work because I haven’t magisk installed
So I flashed magisk again ( this solved the fstab error) and after that the EDXposed uninstaller. Both flashes worked
I tried to reboot but without success
Now I gave up and hope that you have an ansewer
Click to expand...
Click to collapse
Try reflashing rom you are using again in recovery.so dirty flash over existing one
Sent from my LEX820 using Tapatalk
bilausdaniel said:
Try reflashing rom you are using again in recovery.so dirty flash over existing one
Sent from my LEX820 using Tapatalk
Click to expand...
Click to collapse
Still in boot loop ( I let it boot for 18 min )
Did you tried to disable xposed on booting?
There is key combination when system boots up, to disable xposed, and so all modules.
Go into recovery, and boot up again from there (normal boot), and when logo appears click at least 3 times power button, and xposed will understand it need to disable itself.
That should work.
And if you have some data in phone, you can make app backup from recovery and if you have files you can connect to PC and copy those files on PC.
I am currently having this problem. Some fully updated systems on some devices won't boot into safe mode. Among those devices are many Xiaomi Devices. I can only boot into fastboot mode.
I've got Orange Fox so theoretically I should be able to delete Riru, effectively disabling exposed, however, Orange Fox is asking for a decryption password and I can't access files to delete them.
ADB sideload failed.
Not sure if I can even do a wipe back to default state.
brasscupcakes said:
I am currently having this problem. Some fully updated systems on some devices won't boot into safe mode. Among those devices are many Xiaomi Devices. I can only boot into fastboot mode.
I've got Orange Fox so theoretically I should be able to delete Riru, effectively disabling exposed, however, Orange Fox is asking for a decryption password and I can't access files to delete them.
ADB sideload failed.
Not sure if I can even do a wipe back to default state.
Click to expand...
Click to collapse
go in twrp and to android/adb/modules.. module there reboot phone
bilausdaniel said:
go in twrp and to android/adb/modules.. module there reboot phone
Click to expand...
Click to collapse
delete that module in there
How do I have to install Magisk on the xperia z sgp311 tablet? Once I had managed to install MAgisk just by flashing Magisk.zip but it doesn't work anymore. I tried changing the name of magisk.apk to magisk.zip. It doesn't work either. didn't work either
novatosuper said:
How do I have to install Magisk on the xperia z sgp311 tablet? Once I had managed to install MAgisk just by flashing Magisk.zip but it doesn't work anymore. I tried changing the name of magisk.apk to magisk.zip. It doesn't work either. didn't work either
Click to expand...
Click to collapse
Hi, which TWRP version are you using ? Allowed system partition modification ?
install lineage os microg when I do it it returns twrp with more basic options I have tried flashing the latest twrp with lineage os microg but it doesn't boot the system and makes me flash lineage os microg again when I do it it modifies more basic twrp I don't know why that happens
novatosuper said:
How do I have to install Magisk on the xperia z sgp311 tablet?
Click to expand...
Click to collapse
Edit: what I wrote below is wrong. You're likely running into a Magisk 24.3 bug
-------------------------
This probably doesn't answer your question - but installing Magisk permanently may not be possible. My unscientific opinion (based on my recent experiences) is you may need to install everything in one shot - i.e. no reboot. I recently managed in install Lineage 15.1 from stock using twrp by:
rebooting into fastmode
installing twrp
rebooting into recovery (the one shot I had - if I rebooted at this stage, twrp would be gone! So avoid rebooting from here on out. )
Install lineage zip, then microg & any other packages you want
Reboot into lineage - twrp no longer available
I couldn't get twrp to stay installed even when I tried to install it to system, I figured that's because pollux_windy doesn't have a recovery partition. Also - I'm going off memory, so I may have gotten things wrong. However, it took me about 3 attempts to get things right (at times lineage wouldn't boot, IIRC, I may have forgotten to wipe the cache). I was following the steps in the wiki and used the following versions, accoding to my downloads folder:
twrp v3.6.1_9-0-pollux_windy.img
open_gapps-arm-8.1-nano20220215.zip
lineage-15.1-202000220-nightly-pollux_windy-signed.zip
sangnoir said:
Edit: what I wrote below is wrong. You're likely running into a Magisk 24.3 bug
-------------------------
Click to expand...
Click to collapse
Fixed in recently released v25.0.