I am having issues installing the xposed framework. I have rooted with Magisk successfully and I'm on the ElementalX kernel. When I try to install the xposed framework via TWRP, when I reboot back into the OS, it gets stuck in a hello moto bootloop. I can boot into the OS without issue by clearing the dalvik cache and the normal cache after installation, but when I get into the Xposed installer app, it says it's installed but not running. There is no log, so I assume it is because the Xposed folder doesn't have permissions. I give it permissions and reboot by pressing restart in the power menu, but when I do that, it gets in the bootloop again.
I would appreciate any help on this.
MineMasterHD said:
I am having issues installing the xposed framework. I have rooted with Magisk successfully and I'm on the ElementalX kernel. When I try to install the xposed framework via TWRP, when I reboot back into the OS, it gets stuck in a hello moto bootloop. I can boot into the OS without issue by clearing the dalvik cache and the normal cache after installation, but when I get into the Xposed installer app, it says it's installed but not running. There is no log, so I assume it is because the Xposed folder doesn't have permissions. I give it permissions and reboot by pressing restart in the power menu, but when I do that, it gets in the bootloop again.
I would appreciate any help on this.
Click to expand...
Click to collapse
I had this problem also, I would typically just long press the power button and let it complete a second normal boot, and then xposed would work after the second boot completed. (The second boot after initial bootloop would load up just fine.) However, after a few reboots, my phone became unstable and I had to reflash the stock ROM. I'm not sure how stable OREO xposed is on this device yet. It may have just been my modules. (GravityBox, Flat Color Keyboard, Bars, and Status Icons)
Drkmatr1984 said:
I had this problem also, I would typically just long press the power button and let it complete a second normal boot, and then xposed would work after the second boot completed. (The second boot after initial bootloop would load up just fine.) However, after a few reboots, my phone became unstable and I had to reflash the stock ROM. I'm not sure how stable OREO xposed is on this device yet. It may have just been my modules. (GravityBox, Flat Color Keyboard, Bars, and Status Icons)
Click to expand...
Click to collapse
I also have a Moto G5 plus and when I tried to reboot it a second time it was still stuck in its boot loop so I had to enter TWRP to flash the uninstall and if I try to install Xposed via Magisk I have to factory reset, I don't think it's me ROM because it's the same as a stock ROM (had to install the ROM because the one it came with got corrupted or something when I tried to install Xposed where I still had the boot loop problem). I am running 8.1.0 Oreo.
I think a lot of my problem was i was using a sprint variant also. I think a lot of other users are using the verizon/t-mobile variants. I never really did get xposed to work properly on oreo on the sprint variant of this phone no matter what i tried.
Any news on this issue?
I just updated to 8.1 and would like to get xposed up and running like I had it on Nougat. Has there been any fixes yet to this. Thanks to anyone for a reply.
I get bootloop when I install magisk & xposed.
I am using Xposed since months
Working fine
One thing you is that we've to do soft reboot instead of regular reboot
Related
My model number is the SM-N910P and currently on the 12.1-20151003-NIGHTLY-trltespr Cyanogenmod version.
Every time I attempt to update the nightly (I tried to update the last few times when the 20151010 and 20151009 nightlies were available), I have to do the usual updates like the SuperSU binaries, AdAway host files, and reflash the Xposed framework. Every other update goes fine until I try to reflash the framework. The framework I've been using and reflashing successfully until recently is xposed-v71-sdk22-arm-by-romracer-20150816.zip. I'm pretty certain I have the right Xposed framework for the Note 4 since it has a 32-bit processor. And Romracer's 64-bit zip files would say "arm64" instead of just "arm".
However, now I just get stuck on the CM boot logo. I initially assumed I was just being impatient and not waiting long enough. But I would do the force shut down (Power + vol down + home) and sure enough it would just boot back up by itself which I was certain at that point I was in a bootloop.
So I tried to just manually get the new nightly from the cyanogenmod website and doing the wipe cache + dalvik cache + system + data on TWRP and then update it that way instead of automatically having the CM Updater do it for me. Perhaps my memory must be fuzzy or there's something new in order to install xposed since the last time I did it. I've reflashed that exact Xposed zip file numerous times since the release date of that file after updating the CM nightlies here and there prior to this past week. Do dirty flashes not work for CM software updates anymore? What am I doing wrong that's causing Xposed to get me in a bootloop?
tl;dr
1. Got the zip file for the updated nightly for my SM-N910P (trltespr)
2. Dirty flash it over the old nightly (tried it via CM Updater and manually via TWRP)
3. Go through all the updating steps after a nightly update (eg. Updating SuperSU binaries and AdAway host files)
4. However, when attempting to reflash Xposed, I end up in a bootloop (despite force shutdown with the hardware buttons Power, Vol Down, Home, it boots right back up itself)
Any help would be greatly appreciated!
I made a mistake when installing xposed on my G935F and am now stuck in a bootloop.
I downloaded the xposed uninstaller to undo my install and fix my mistake, but I'm unable to boot into recovery.
Do I have to reflash it via odin?
Note: I downloaded the sdk 23 arm64 version, but I didn't wipe data like the guide said to do (didn't see that guide until after I flashed, I was following another guide).
Thanks.
Why are you unable to boot into recovery? And not wiping data would not prevent the phone booting as long as you installed the correct Xposed framework. Did you install Wanam's arm64 version here or the official one? If you installed the official version in rovo89's thread then that is why you're getting a boot loop. Unless things have changed, that doesn't work on Touchwiz roms and causes bootloops, hence why Wanam made a separate version.
Beefheart said:
Why are you unable to boot into recovery? And not wiping data would not prevent the phone booting as long as you installed the correct Xposed framework. Did you install Wanam's arm64 version here or the official one? If you installed the official version in rovo89's thread then that is why you're getting a boot loop. Unless things have changed, that doesn't work on Touchwiz roms and causes bootloops, hence why Wanam made a separate version.
Click to expand...
Click to collapse
I used the official one version.
I have no idea, but I tried the recovery boot sequence so many times and I can't get it to boot into recovery. What should I do?
Reset your phone (volume down & power for 7-10 seconds) then remove your fingers and press volume up & home & power to boot into recovery. If you have TWRP installed (and I assume you do unless you used Flashfire to flash Xposed) there is no reason it shouldn't work. Installing Xposed, even if you used the incorrect version, would have absolutely no effect on the recovery partition.
Beefheart said:
Reset your phone (volume down & power for 7-10 seconds) then remove your fingers and press volume up & home & power to boot into recovery. If you have TWRP installed (and I assume you do unless you used Flashfire to flash Xposed) there is no reason it shouldn't work. Installing Xposed, even if you used the incorrect version, would have absolutely no effect on the recovery partition.
Click to expand...
Click to collapse
That still doesn't work for me.
I used flashfire the first time and it didn't work (some guide on xda said to use it). It booted fine after that. I then reverted back to flashify and booted into twrp to flash it, and after that it just sat on the S7 edge boot screen endlessly.
I kept trying and managed to boot into recovery. I flashed the xposed uninstaller and its now running again. Thanks for the help!
l33t p1mp said:
I kept trying and managed to boot into recovery. I flashed the xposed uninstaller and its now running again. Thanks for the help!
Click to expand...
Click to collapse
Use this Xposed
https://www.dropbox.com/s/2q69cpwxz...arm64-custom-build-by-wanam-20160504.zip?dl=0
"And on that bombshell!"
Sent from my Echoe powered AEL driven G935F
Hey all!
Those of you monitoring the unofficial LineageOS thread may have seen me talking about this already. I've been having issues with Magisk. I'm running their beta versions for 13.0.
So here's the story...
I have wanted to pass SafetyNet since May, when I got this phone and rooted it. I obviously went to Magisk, and when I realized that 11.6 was not passing SafetyNet, I decided to try the 13 betas. These didn't pass either, but since they were more recent than 11.6, I stuck with them. But when I heard of the Universal SafetyNet Fix Module, I immediately tried it.
Bottom line, these are my issues:
1. Magisk will not install the module. I go to Magisk Manager -> Modules -> + and select the ZIP for the module. Magisk gives me a toast saying "Installation error!" (See screenshot).
2. Okay, so now I want to start fresh and see if it works then. I boot into TWRP, flash the lastest Magisk uninstaller (08 June), and boot. Nope! Stuck on the "device unlocked" screen with ID: bad key.
3. Uhh.. maybe the stock boot image will work? I go to TWRP and flash the stock boot.img taken from the stock firmware. Still ID: bad key and I'm stuck again.
And I can boot successfully if I flash a Magisk 13.0 beta.
So, does anybody have any solutions? I think I may just have to reflash stock firmware.. not my top choice. Thank you for any help and reading through my long post :good: :highfive:
Try to install magisk v12, it always worked for me on every rom with safetynet fix ( try also the previous uninstaller )
eskamhl said:
Try to install magisk v12, it always worked for me on every rom with safetynet fix ( try also the previous uninstaller )
Click to expand...
Click to collapse
Will give it a shot and update when I see results.
Edit: Nope. I've a feeling that I'll have to start from scratch by flashing stock firmware.
Try flashing the safetynet fix in trwp.
triggerlord said:
Try flashing the safetynet fix in trwp.
Click to expand...
Click to collapse
Tried already. Still no.
Well, as far as I can see you messed up your installation. Start from scratch:
1. Go to TWRP and wipe system, data, cache and dalvik cache.
2. Install LineageOS, GAPPS, Magisk 12 and the stable version of the safetynet fix
3. Reboot and setup your nice and clean system again.
Bottom-line: don't keep messing with an already messed up system. Start clean again. And really: don't install stock boot.img on LineageOS: that's asking for trouble! To be honest: I'm astonished it even booted!!
smitharro said:
Well, as far as I can see you messed up your installation. Start from scratch:
1. Go to TWRP and wipe system, data, cache and dalvik cache.
2. Install LineageOS, GAPPS, Magisk 12 and the stable version of the safetynet fix
3. Reboot and setup your nice and clean system again.
Bottom-line: don't keep messing with an already messed up system. Start clean again. And really: don't install stock boot.img on LineageOS: that's asking for trouble! To be honest: I'm astonished it even booted!!
Click to expand...
Click to collapse
Lol, was doing this all on the stock ROM. See my original response to triggerlord's post.
Edit: issues fixed with a clean install of the pure Nexus ROM. I'm assuming this would be the case with a clean install of the stock ROM, but I am definitely not switching anytime soon (this ROM is amazing!)
A little background first, I have had my galaxy (sm-g975F exynos) rooted for some time now with magisk. I wanted to update the firmware, reroot and install TWRP in the process. Took me a few hours and only one mistake but at the end I was successful. This was 2 days ago and Ive been working on customizing ever since.
Now onto the problem, I noticed the camera app didn't work any more when I boot into magisk mode. When I boot in standard mode the camera works fine. I tried force quitting, rebooting, reverting to original settings, etc... and no change. I started reinstalling system apps I removed with debloat thinking I may have removed a system app that had an effect but again no change. I read somewhere that clearing/wiping cache may help so I booted into TWRP, went into advanced wipe and only wiped "cache". Now when I reboot into standard mode the phone works fine, but if I boot into magisk mode I cant get past the lock screen. Basically magisk mode boots fine but when I enter my pin it just goes back to lock screen. So I rebooted into standard mode and made it so there was no lock screen(no pin, no fingerprints, etc...) then I tried rebooting in magisk mode to see if this will get me past the lock screen and now it just bootloops in magisk mode only.
So my first problem is getting my phone back into magisk mode, my second problem is the camera. is there a safe way to reflash with TWRP or am I going to have to redo the whole process with odin?
Thank you in advance for any help, I have searched online but haven't found anyone that has had issues wiping cache with TWRP
update, tried downloading magisk zip from magisk manager, rebooted into TWRP and tried installing the zip, no change. wiped dalvik cache for kicks, no change.
update #2, also tried uninstalling or disabling root privilege apps such as novalauncher, liveboot and buttonmapper but I was only able to do this in non-magisk mode, again no change.
Update #... what # am I on?
So I started fresh, reinstalled stock firmware, reinstalled magisk and reinstalled TWRP. Phone is working fine except for the fact the camera doesnt work in magisk mode. I am now 100% positive this is due to magisk or TWRP. I will try and install another camera app to see if it works, but would still like to figure out how to get samsungs camera app to work in magisk mode.
So I decided to enter into safe mode which ultimately broke my magisk install. Same scenario as before, I can boot into non-magisk mode now but if I try and boot into magisk mode I cant get past lock screen. However while in safe mode and now non-magisk mode, the camera actually does work. So as it stands I can either have my phone rooted and not be able to use the camera or not have it rooted and be able to use the camera. If anyone has any suggested work arounds, please feel free to chime in. In the mean time I will start over again.
another update.
I reflashed stock firmware along with magisk. I now have root as well as a working camera, and yes the camera works in magisk mode and non-magisk mode. I am now looking to blame TWRP or multidisabler in breaking the camera. I know that having TWRP on a galaxy S10+ is fairly new to the market but I am surprised that I cannot find a single other report of someone elses camera not working after installing TWRP. I feel like I should keep trying things but I also have reflashed firmware, magisk, TWRP 3 times in the past 5 days and I just want a working phone with root. The only other ideas I had was to either give the camera root access or make the camera a system app. I dont see why I would/should need to do that though.
Moderator can you please change the title of this thread to "Camera not working after installing TWRP" please and thank you if it is possible.
I'm running Android 10 with EvoX rom and after last update of Magisk to 21.4 the phone is stuck on bootloop. After going to recovery and uninstalling Magisk I have the same problem, it's still in bootloop. What can I do to fix the problem?
Dirty flash ROM or if 1st step doesn't work factory reset and install everything
Same here. I don't want to do a factory reset.
I tried to:
- uninstall Magisk from twrp
- flash the boot.img of the rom
- flash the previous version 21.2 of magisk
but none of this worked!
I have the same Issue. Havoc 3.9., Magisk 21.4.
I tried to dirty flash the rom, uninstall magisk 21.4 via twrp, and flashing 21.2.
Didn't help. Occassionally I got into the system, but the screen is a bit more white than usually, I can type in my lock password, but after this, System UI fails.
Yesterday I flashed the fix for safetynet passing after the latest update, which made it work again, and I remember that at the relevant magisk forum, somebody mentioned that would affect System UI somehow. Now I am trying to repair the System UI to see if it works as a solution.
[email protected] said:
Yesterday I flashed the fix for safetynet passing after the latest update, which made it work again, and I remember that at the relevant magisk forum, somebody mentioned that would affect System UI somehow. Now I am trying to repair the System UI to see if it works as a solution.
Click to expand...
Click to collapse
What fix are you talking about? Where can I acquire it?
EDIT: In my case the bootloop was caused by the Systemless Xposed Framework module v90-beta2 by rovo89 (packaged by topjohnwu). Disabling that module allowed me to boot normally.
en_ha87 said:
I'm running Android 10 with EvoX rom and after last update of Magisk to 21.4 the phone is stuck on bootloop. After going to recovery and uninstalling Magisk I have the same problem, it's still in bootloop. What can I do to fix the problem?
Click to expand...
Click to collapse
Same problem occur with me ,i just unistall 21.4 and indtal 20.4 veraion but nothing happens then i just wait for 5-10 min on bootloop screen and it starts processing it's updating my new boot image ... This thing happens when i update my miui after completing the process i finally see my homescreen
Lars0n89 said:
What fix are you talking about? Where can I acquire it?
EDIT: In my case the bootloop was caused by the Systemless Xposed Framework module v90-beta2 by rovo89 (packaged by topjohnwu). Disabling that module allowed me to boot normally.
Click to expand...
Click to collapse
How can you install that Module from TWRP?
That i remember i never installed it, it's automatically loaded with magisk?
To solve this problem i had to format the phone, installing the OS again and also magisk v21.2. But Today i got the same problem... so maybe is not the versione of magisk. But I don't know of to solve it.
I tried also the sotck boot.img, but it stays some seconds on the boot screen of lineage OS and then reboot again stucking on Mi logo.
i also had to install stock rom, lost all the data on the phone. today i have to install custom rom, and will probably pass on the magisk, i don't need sh**t like this happening again.
I had to reinstall the rom from scratch, and needed to format data partition too. After flashing my ROM back, I installed magisk 21.2 and it works great.
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
flavioggl said:
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
Click to expand...
Click to collapse
Could you help me i got into a bootloop after doing the magisk direct update from the app. My discord is : SneezeOnYou2#8507
I believe that i have a backup in twrp just dont know how to flash or uninstall or what ever to do i dont want to lose my data. I can record my screen if you add me on discord.
flavioggl said:
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
Click to expand...
Click to collapse
Thank you, brother. It was a simple solution but I forget to do that. After wasting 2 hours finally able to solve the problem. Thanks again.