Bootloop Xposed Framework - Xposed Framework Modules
Hello !
I want to apologize for my English from Google translation because I'm French ... Hope you understand ?
Yesterday I rooted my phone which is a Huawei P8 Lite Android 6.0 with Magisk.
So far so good.
I wanted Xposed installed so I started by installing Xposed Installer and then in Magisk I installed Xposed framework [SDK23] but restarting my phone I was stuck with the huawei logo ... ?
If anyone will have a solution I am a taker!
Thank you !
netyx62 said:
Hello !
I want to apologize for my English from Google translation because I'm French ... Hope you understand [emoji23]
Yesterday I rooted my phone which is a Huawei P8 Lite Android 6.0 with Magisk.
So far so good.
I wanted Xposed installed so I started by installing Xposed Installer and then in Magisk I installed Xposed framework [SDK23] but restarting my phone I was stuck with the huawei logo ... [emoji17]
If anyone will have a solution I am a taker!
Thank you !
Click to expand...
Click to collapse
I don't know your phone, but I can tell you that on mine I had to do the following:
1) Install the Xposed Installer.
2) Reboot.
3) Install correct SDK in Magisk.
4) Reboot.
5) Wait about 20 minutes for it to boot up.
It took that long on Step 4. But only once. After that, it booted up normally.
I recommend that you first install an app called "LiveBoot" (Grant it Root). It will replace your bootup logo with lines of text that are the commands that your phone normally processes when it boots up.
The advantage here, is that unlikr the logo, with LiveBoot you can see that the phone has not frozen (it may pause for 30 seconds now and then), as long as it's still processing commands.
You can uninstall LiveBoot after you're done, or leave it on.
I was being serious. The first time, it took my phone 20 to 30 minutes to boot. After that, it booted up as fast as it always did.
Good Luck!
Posted from my way cool LG V20 (H910) Nougat 7.0
Thank you for your advice I tried and actually I was not patient enough when restarting but i have another problem now, xposed tell me it is installed but not active .... Solution?
netyx62 said:
Thank you for your advice I tried and actually I was not patient enough when restarting but i have another problem now, xposed tell me it is installed but not active .... Solution?
Click to expand...
Click to collapse
netyx62,
It may just need another reboot. But first go into Magisk, look at the SDK Module and make sure the little box is checked.
Then go into the Xposed Installer app and go into the "Framework" section.
Is the switch on?
What color is the rectangle below the switch?
Also, important… Did you use the "Xposed Installer for Magisk"?
There is a different installer for when you have Magisk. It'll say "for Magisk".
*** If you did NOT use the right installer, then you'll need to get the right one and then follow the steps below.
First Google and Download;
"Xposed Installer for Magisk"
I think it's also v3.1.5 for Magisk too.
Then go into Magisk >> Modules and tap the little garbage can for the Framework Module, which will make it uninstall on the next reboot.
But before rebooting, Uninstall the Xposed Installer app.
Now Reboot.
Now start over, using the correct Xposed Installer for Magisk, by doing the steps I outlined in my previous post and remember that once it's all installed, the first boot will take forever!
TTYL
Posted from my way cool LG V20 (H910) Nougat 7.0
Zeuszoos said:
netyx62,
It may just need another reboot. But first go into Magisk, look at the SDK Module and make sure the little box is checked.
Then go into the Xposed Installer app and go into the "Framework" section.
Is the switch on?
What color is the rectangle below the switch?
Also, important… Did you use the "Xposed Installer for Magisk"?
There is a different installer for when you have Magisk. It'll say "for Magisk".
*** If you did NOT use the right installer, then you'll need to get the right one and then follow the steps below.
First Google and Download;
"Xposed Installer for Magisk"
I think it's also v3.1.5 for Magisk too.
Then go into Magisk >> Modules and tap the little garbage can for the Framework Module, which will make it uninstall on the next reboot.
But before rebooting, Uninstall the Xposed Installer app.
Now Reboot.
Now start over, using the correct Xposed Installer for Magisk, by doing the steps I outlined in my previous post and remember that once it's all installed, the first boot will take forever!
TTYL
Posted from my way cool LG V20 (H910) Nougat 7.0
Click to expand...
Click to collapse
I used "XposedInstaller_3.1.5-Magisk.apk"
Yes everything is checked in Magisk or Xposed and then the rectangle is yellow with a danger sign
netyx62 said:
I used "XposedInstaller_3.1.5-Magisk.apk"
Yes everything is checked in Magisk or Xposed and then the rectangle is yellow with a danger sign
Click to expand...
Click to collapse
Okay, assuming the switch is on in Xposed, try another reboot. That's what I'd do first.
P.S. You said that you installed the Framework from inside the Magisk app, right? Are you positive you have the right one installed? Which version of Android are you running!
Android Nougat 7.0
Android Nougat 7.1
Android Oreo 8.0
Android Oreo 8.1
Posted from my way cool LG V20 (H910) Nougat 7.0
Zeuszoos said:
Okay, assuming the switch is on in Xposed, try another reboot. That's what I'd do first.
P.S. You said that you installed the Framework from inside the Magisk app, right? Are you positive you have the right one installed? Which version of Android are you running!
Android Nougat 7.0
Android Nougat 7.1
Android Oreo 8.0
Android Oreo 8.1
Posted from my way cool LG V20 (H910) Nougat 7.0
Click to expand...
Click to collapse
I already restart many times ... And I'm on Android 6.0
netyx62 said:
I already restart many times ... And I'm on Android 6.0
Click to expand...
Click to collapse
I'm trying to think of what your problem might be.
Let me ask you, which SDK version ended up being installed? I think it's supposed to be SDK23 for Marshmallow. I do know that there's a 32 bit and a 64 bit version and you need to have the right one for your phone (the phone is either 32 or 64).
In the Magisk Modules, what version SDK does it say is installed?
In Xposed >> Framework, near the bottom, does it say which (32 or 64) the installed framework is? Or does it not show a framework there?
Posted from my way cool LG V20 (H910) Nougat 7.0
Zeuszoos said:
I'm trying to think of what your problem might be.
Let me ask you, which SDK version ended up being installed? I think it's supposed to be SDK23 for Marshmallow. I do know that there's a 32 bit and a 64 bit version and you need to have the right one for your phone (the phone is either 32 or 64).
In the Magisk Modules, what version SDK does it say is installed?
In Xposed >> Framework, near the bottom, does it say which (32 or 64) the installed framework is? Or does it not show a framework there?
Posted from my way cool LG V20 (H910) Nougat 7.0
Click to expand...
Click to collapse
In Magisk it's SDK23. Then my phone is a 64 bit
netyx62 said:
In Magisk it's SDK23. Then my phone is a 64 bit
Click to expand...
Click to collapse
Okay, the only other thing I can think of off the top of my head is the order in which the components are installed. It can be different. On my last phone I had to install the Magisk Framework Mod first and then the Xposed Installer. On my current phone, it's in the order that we did it on yours.
So here's what I'm going to suggest…..
I suggest that you uninstall both the Magisk SDK and the Xposed Installer and we start from scratch using a different method.
Are you game?
Posted from my way cool LG V20 (H910) Nougat 7.0
Sory i just flashed Xposed SDK27 for Pocophone F1 (Beryllium) but stuck in logo, is that bootloop or i just have to wait?
How can i know Xposed is that work succesfully installed in my Pocophone F1?
Thx b4
NB : Now i use ROM MIUI 9.6.14.0 Global Stable & Magisk v18.0 installed.
Zeuszoos said:
Okay, the only other thing I can think of off the top of my head is the order in which the components are installed. It can be different. On my last phone I had to install the Magisk Framework Mod first and then the Xposed Installer. On my current phone, it's in the order that we did it on yours.
So here's what I'm going to suggest…..
I suggest that you uninstall both the Magisk SDK and the Xposed Installer and we start from scratch using a different method.
Are you game?
Posted from my way cool LG V20 (H910) Nougat 7.0
Click to expand...
Click to collapse
Nothing works... I even try to install it without using Magisk but nothing ...
netyx62 said:
Nothing works... I even try to install it without using Magisk but nothing ...
Click to expand...
Click to collapse
As I said, there is another method to try if you wish.
Posted from my way cool LG V20 (H910) Nougat 7.0
Related
LG K7 insalling Xposed Framework
I'm rooted, 5.1 with lollipop and I am desperate for answers as to why this has to be rocket science just to put Framework on Xposed. Sorry if this is the wrong section, I don't have the patience right now to make a ton of posts just to meet the requirements for whatever reason. But anyways, does anyone have a solution to my problem?
Its no different than any other phone. The only twist is unrelated to xposed in that you need Quick Boot or my favorite NeoPowerMenu to boot to TWRP. You could use FlashFire but if the above is a foreign language id suggest doing it that way. You can save a future post and time on how to boot to recovery and flash the uninstaller if Xposed boot loops you. Im using v85 and has been working on my K7, v86 works good on my moto but ive heard of a few k7s having issues with 86.
what version of xposed are you running? terminal emulator x v2 keeps auto downloading armeabi-v7a and it says its for the wrong phone.. i can flash manually but i dont know what xposed to get
[Xposed 3.1][SM-A320FL] Samsung Galaxy A3 2017 | Confirmed working on stock 6.0.1
(All credit goes to wanam for providing Xposed for TouchWiz roms) I am not sure if this needs a thread but since i was searching for this information i'm making one for the Xposed fans with an A3 2017. Because i don't have enough time to test more configurations i can't say if this will or will not work on any other configuration besides the one i have. Feel free to backup everything (using a recovery like TWRP or CWM) and try flashing Xposed yourself. Read the bottom of the post on how to get into your recovery when having a bootloop. I do not take any responsibility for bricked devices and any other damages. I mostly followed the steps in this thread but i'll write the steps here as well. This will only work with stock or stock-based roms, for AOSP based roms, use normal Xposed flashables A recovery like CWM or TWRP (guide) is required. Backup your /system partition or reckon that you might lose data. Flashing Xposed only affects /system Install the Xposed 3.1 apk (requires "Unknown sources" to be allowed in system settings) Go to your recovery by shutting down your phone and holding Volume Up + Home while powering it on Flash this zip file for Xposed on Samsung devices (ARM). You might find newer versions here (choose ARM for this phone, not ARM64). Reboot and wait for up to 15 minutes. It might bootloop a couple times and you might have to wait for app optimization for some more minutes Enjoy the flexibility of Xposed If your device is bootlooping for more than 10 minutes it's highly likely that Xposed is not working for you. Note that using Volume Down + Power will restart your device but will always attempt to restart Android. In order to get to your recovery charge your device which will make VolDown + Power shut down the phone instead of restarting it. From there you can VolUp + Home and power it on to boot into recovery. You can attempt to flash the uninstaller in order to fix the bootloop or if Xposed is just not working and you wanna get rid of it. If that doesn't help, restore your backup (will always work, flashing the uninstaller is just quicker). Known bugs on the A3 2017: - none (will add from comments or if i find any) Sources: https://github.com/wanam/Xposed https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 https://forum.xda-developers.com/sa.../samsung-sm-a520f-2017-kernel-source-t3557622
Hello, why is arm64 version not working / 64bit ist not recognised by xposed? It's definitely a 64bit CPU with arm64v8a instruction set (Aarch64). So why the installation of arm64 is blocked? SinusStudios said: (All credit goes to wanam for providing Xposed for TouchWiz roms) I am not sure if this needs a thread but since i was searching for this information i'm making one for the Xposed fans with an A3 2017. Because i don't have enough time to test more configurations i can't say if this will or will not work on any other configuration besides the one i have. Feel free to backup everything (using a recovery like TWRP or CWM) and try flashing Xposed yourself. Read the bottom of the post on how to get into your recovery when having a bootloop. I do not take any responsibility for bricked devices and any other damages. I mostly followed the steps in this thread but i'll write the steps here as well. This will only work with stock or stock-based roms, for AOSP based roms, use normal Xposed flashables A recovery like CWM or TWRP (guide) is required. Backup your /system partition or reckon that you might lose data. Flashing Xposed only affects /system Install the Xposed 3.1 apk (requires "Unknown sources" to be allowed in system settings) Go to your recovery by shutting down your phone and holding Volume Up + Home while powering it on Flash this zip file for Xposed on Samsung devices (ARM). You might find newer versions here (choose ARM for this phone, not ARM64). Reboot and wait for up to 15 minutes. It might bootloop a couple times and you might have to wait for app optimization for some more minutes Enjoy the flexibility of Xposed If your device is bootlooping for more than 10 minutes it's highly likely that Xposed is not working for you. Note that using Volume Down + Power will restart your device but will always attempt to restart Android. In order to get to your recovery charge your device which will make VolDown + Power shut down the phone instead of restarting it. From there you can VolUp + Home and power it on to boot into recovery. You can attempt to flash the uninstaller in order to fix the bootloop or if Xposed is just not working and you wanna get rid of it. If that doesn't help, restore your backup (will always work, flashing the uninstaller is just quicker). Known bugs on the A3 2017: - none (will add from comments or if i find any) Sources: https://github.com/wanam/Xposed https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 https://forum.xda-developers.com/sa.../samsung-sm-a520f-2017-kernel-source-t3557622 Click to expand... Click to collapse
knzsys said: Hello, why is arm64 version not working / 64bit ist not recognised by xposed? It's definitely a 64bit CPU with arm64v8a instruction set (Aarch64). So why the installation of arm64 is blocked? Click to expand... Click to collapse To be honest i flashed 32 bit xposed because i searched for the phones architecture and found 32 bit but that must be a misinformation. I'm surprised now that it's working on my phone! Thanks for mentioning this, if you have time feel free to safely try out both versions and report back what's working and what's not.
knzsys said: why is arm64 version not working / 64bit ist not recognised by xposed? It's definitely a 64bit CPU with arm64v8a instruction set (Aarch64). So why the installation of arm64 is blocked? Click to expand... Click to collapse Can't find a reason why our 64-bit phone is not recognized bit the 64-bit Xposed I you want to install the 64-bit Xposed: got through Magisk Don't know if it has a direct link: had lotz of reboot with 32-bit Xposed; nearly no reboot with 64-bit Xposed. PS: Don't get too addict to Xposed has it will stop running when we'll get Nougat
The 64bit version will not work because Samsung shipped the SM-A320F with 32bit Android, even though it has a 64bit-capable SoC.
Im Wondering something here ... 32 bit os on our phone, no custom roms .. etc ... but the J7 2016 has the same CPU, same ram, storage, screen res ... you get the point .. i just wonder if a rom from that would ... and its 64 bit ... i mean, its the same damm SoC
are there any news for android 7 to get xposed without magisk. I have supersu root
y2kadir said: are there any news for android 7 to get xposed without magisk. I have supersu root Click to expand... Click to collapse Yes, you just have to search the Xposed thread and read.
Pat750 said: Yes, you just have to search the Xposed thread and read. Click to expand... Click to collapse ok but I just did it and coulnd`t find anything. can you tell me where to find?
y2kadir said: ok but I just did it and coulnd`t find anything. can you tell me where to find? Click to expand... Click to collapse Well I did, but if you can't even find it, I think it's better for you not to use it. Sorry.
Pat750 said: Well I did, but if you can't even find it, I think it's better for you not to use it. Sorry. Click to expand... Click to collapse why are you talking foolish ****. if you don't wanna help other people go home.
y2kadir said: why are you talking foolish ****. if you don't wanna help other people go home. Click to expand... Click to collapse OK here's something to start with. https://forum.xda-developers.com/showthread.php?t=3034811 but please read the threads there are some good advice's.
Pat750 said: OK here's something to start with. https://forum.xda-developers.com/showthread.php?t=3034811 but please read the threads there are some good advice's. Click to expand... Click to collapse I only found this in the thread "The first fixes have found their way into version 88.1, only available for Nougat. That includes especially some fixes for Samsung ROMs, but might also fix bootloops and slowdowns on other devices. Besides that, I think I fixed a MIUI incompatibility, not sure if it works now (and to be honest, I don't give much priority to MIUI). There are still unfixed issues on the queue, and again, please keep reporting whatever you find." but this information is not confirming me that its working.
LG g5 h830
Hello I am trying to get xposed on h830. I see there are difficulties I could use a full guide. I would like to use magisk. Please let me know what info needed to help. Thanks
Well I did it. Have lineage is installed. I think lineage is better for this screen anyway. The screen seems to ghost all those white menus anyway. Have magisk 14.5 Xposed 88.2. had to follow several posts since not 1 had it all correct. Started with h83020f downgraded to h83020a with uppercut. Then used recowvery 4 g5 thank you. Then found out I couldn't upgrade without loosing TWRP. Redid downgrade and recowvery again. Did install of lineage. Install magisk. Installed Xposed right from magisk. No need to install from TWRP. Done any questions
Don't flash Magisk 17.0+ ***on STOCK ROM***
Updated OP since this thread became useful to track if magisk works with our stock ROM. The most recent version you can use at the moment is magisk 16.7 and magisk manager 5.8.3. I suggest that you change the update channel to custom and set the address to 127.0.0.1 For the most recent Magisk version: mickey36736 said: I tested 19.3 on B01 oreo and it still bootloop. Click to expand... Click to collapse Thanks for checking @mickey36736
rzarectha said: It bootloops Click to expand... Click to collapse I don't have any problems on Magisk 17.0 - safetynetpass on AEX(O), NitrogenOS(P) and PE(P) :cyclops: Open Manager and update. Download latest stable one and flash it. Reboot.
raystef66 said: I don't have any problems on Magisk 17.0 - safetynetpass on AEX(O), NitrogenOS(P) and PE(P) :cyclops: Open Manager and update. Download latest stable one and flash it. Reboot. Click to expand... Click to collapse mine bootlooped on stock. I'm naive enough to wait for the big update also, I got it from the beta channel. I'll try the stable and see what happens. I was assuming it's the same build update: it bootloops on stock no matter what channel (stable/beta) you get it from. I'll try to get a mod to help me change the OP title, I can't seem to be able to do it myself.
rzarectha said: mine bootlooped on stock. I'm naive enough to wait for the big update also, I got it from the beta channel. I'll try the stable and see what happens. I was assuming it's the same build update: it bootloops on stock no matter what channel (stable/beta) you get it from. I'll try to get a mod to help me change the OP title, I can't seem to be able to do it myself. Click to expand... Click to collapse You can change the OP tittle by pressing Go Advanced button next to the Save button when editing the OP post.
Not only on stock... I am on LOS 14.1, saw the update notification, did update, and now also a bootloop... I installed the zip of an earlier version to no avail.
Prophet 5 said: I am on LOS 14.1, saw the update notification, did update, and now also a bootloop... I installed the zip of an earlier version to no avail. Click to expand... Click to collapse use the uninstaller zip first
Try 17.1. supposedly solves the bootloops.
bootloops are easily fixed by using the uninstaller first.
koftheworld said: Try 17.1. supposedly solves the bootloops. Click to expand... Click to collapse Nope, it doesn't. I'm on B35 and it still bootloops. Had to use the uninstaller to remove and revert to v16.7
KwesiJnr said: Nope, it doesn't. I'm on B35 and it still bootloops. Had to use the uninstaller to remove and revert to v16.7 Click to expand... Click to collapse You have to use the uninstaller first and then flash 17.1.
Too late for me. I was on last years' Darkrom (LOS14.1 based, really stable, so no recent backup) and immediately got a bootloop which I'm still working to recover from... :crying:
pnin said: Too late for me. I was on last years' Darkrom (LOS14.1 based, really stable, so no recent backup) and immediately got a bootloop which I'm still working to recover from... :crying: Click to expand... Click to collapse Did you use the magisk uninstaller? If not, just reflash your bootloader
koftheworld said: Did you use the magisk uninstaller? If not, just reflash your bootloader Click to expand... Click to collapse Excuse my ignorance but how would reflashing the bootloader help. Doesn't Magisk modify the boot image? I figure that if flashing the uninstaller and then flashing v17.1 still results in a bootloop I (personally speaking) would go into TWRP and manually remove any Magisk related directories/files, maybe flash the uninstaller again (might catch something I missed), and then dirty flash Dark ROM (fresh boot image). Flash Magisk 17.x afterward. That said, I am a non-Magisk kind of guy (not present on any ROMs or devices) so I might not know what I'm talking about. [emoji16] Dark ROM. FTW. [emoji41] ZTE Axon 7 A2017U, AospExtended v4.6 ROM, LlamaSweet 0.5 Kernel, microG (NoGapps), Multiboot, XDA Legacy
marcdw said: I (personally speaking) would go into TWRP and manually remove any Magisk related directories/files, maybe flash the uninstaller again (might catch something I missed), and then dirty flash Dark ROM (fresh boot image). Click to expand... Click to collapse Care to clue me in on those directories/files? I'm having a hard time here, dirty flashing my previous ROM, getting up to setup and then have something fail catastrophically over and over again... I have even had to restore recovery through fastboot mode now. :silly:
I did not flash Magisk 17.x on Stock B35 (stayed with v16.4), but installing the latest Magisk Manager (v5.9.1) resolved the previous SafetyNet Check errors
Using stock anything above and v17.0 will bootloop using stock, Just my 2cents, if that your issue just do the following: -Download v16.7 first in case you don't have it yet, and move it to the SDCard. * Head back to TWRP * Flash v16.7 or your preferred release. * You're good to go.
pnin said: Care to clue me in on those directories/files? I'm having a hard time here, dirty flashing my previous ROM, getting up to setup and then have something fail catastrophically over and over again... I have even had to restore recovery through fastboot mode now. :silly: Click to expand... Click to collapse Not sure to be honest. Last time I had Magisk was around v15.x. When I initially rooted my Moto Magisk was part of the process. Even though the stock ROM is using SuperSU it seems I didn't fully remove Magisk. I have the following remnants visible in TWRP... /data/magisk /data/magisk.img and files in /data/adb/ Not sure why everything is failing so badly on your end. I can't test things on my Axon 7 since I use DualBoot Patcher where Magisk is a no go. Moto G5S Plus XT1806, MSM-Xtended v2.5 ROM, MultiROM, XDA Legacy
So I have managed to fully restore the phone, including updating Magisk to v17.1 (v16.0 didn't work at all, v14 did). Apart from Goggle Messages that is, which FC whenever I try to start it (both current and past versions). I was careful with Magisk in the past, I will be even more so in the future. No dot zero releases for me from now on. Thanks for your tips, people.
pnin said: So I have managed to fully restore the phone, including updating Magisk to v17.1 (v16.0 didn't work at all, v14 did). Apart from Goggle Messages that is, which FC whenever I try to start it (both current and past versions). I was careful with Magisk in the past, I will be even more so in the future. No dot zero releases for me from now on. Thanks for your tips, people. Click to expand... Click to collapse I'm not currently having Magisk issues, but Google Messages, after the recent update, does the same here. Gave up on it & switched to Textra.
New beta version released. Still bootloop
Help with Naptime 6.4 lost my settings i made after (re)boot android 8+9
Hi ! I need help with Naptime (Francisco Franco). The setting i've made under section "advanced->apps" resets every reboot to default values. Unfortunatly It also resets by time whyle the phone ist running a bit (2-3h) Phone is galaxy s4 9505 i've testet with lineage 15.1 and optimized lineage 16, rooted with magisk. ---please please please help---
can you send a screenshoots with this settings section?also have you installed magisk modules or xposed?
paranoic(d) said: can you send a screenshoots with this settings section?also have you installed magisk modules or xposed? Click to expand... Click to collapse Hmm, I dont know how to insert a image in my Post... It's the last section of the advanced settings, that only appears if you got root. Called "Apps". There are no xposed or magisk modules installed. Best regards
hmm sorry i have never heard of it again.its the first time i have seen something like this.maybe trying to go back to stock and then root again?