Hi, I'm pretty sure I flashed the correct Xposed, but then it started to bootloop and I had the option to "Download and recovery",
So now I'm downloading.
Any other solution?
Boot to recovery and flash Xposed uninstaller. If you try to install Xposed again make sure you choose correct version. You need "xposed-v85.1-sdk23-arm64-custom-build-by-wanam-20160530".
yiftach said:
Hi, I'm pretty sure I flashed the correct Xposed, but then it started to bootloop and I had the option to "Download and recovery",
So now I'm downloading.
Any other solution?
Click to expand...
Click to collapse
I bought this phone yesterday. I could never start using a device unless I unlock bootloader, root and install xposed. I managed to unlock bootloader, flashed TWRP and also flashed systemless SuperSu (2.74-2). Also, I installed systemless xposed (i have shared link below). Phone took sometime and making me to think it is stuck in bootloader. I switched off and start in TWRP. Wiped art/dalvik and cache. Restarted normally. Everything worked fine.
Someone suggested here how to install official xposed (http://newesc.com/es/instalar-xposed-huawei-p9/).
But I installed systemless xposed (see here: http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268) which works fine without the need of any changes in /system/emui/base/prop/local.pro with this line "ro.config.hwtheme=1" as mentioned in the link I shared above.
Thank you guys!
Hi folks,
i hope i im the right Forum as it seams more a xposed as supersu problem.
I have a Moto X Style rooted with System-less SuperSU 2.78 and Xposed "xposed-v86.1-sdk23" by romracer, Stock ROM 6.0.
Just got a notification that there is a security update available, proceeded but won´t flash. Stops with Error Code 7.
I thought OTA would work with system-less.
Tried also with disable Xposed. Same result. By the way when the phone reboots for flashing it goes into The Recover TWRP 3.0.2 GUI. Anyway i saw the error when switching to the log view.
Any idea whats wrong or i miss?
May i have to restore custom recovery, and if so can i flash the stock recovery with the existing TWRP or do i have to go ADB?
Thanks
Thomas
You have to flash stock recovery image (and probably also boot image) for OTA to work.
Simply use fastboot to flash those. Leave system intact.
Thanks, will do so.
Hello, I am currently rooted on stock oos 4.0.3, with latest TWRP and super su free v2.79, can anyone help me out and tell me how to switch to magisk please, thank you!
Can I just use super su full unroot option then flash magisk?
Either reflash the original boot.img or download the unsu script from https://forum.xda-developers.com/showpost.php?p=63615067, then flash magisk again.
palesaint said:
Either reflash the original boot.img or download the unsu script from https://forum.xda-developers.com/showpost.php?p=63615067, then flash magisk again.
Click to expand...
Click to collapse
so flash unsu, then flash magisk. simple?
Dr Grato said:
so flash unsu, then flash magisk. simple?
Click to expand...
Click to collapse
If you use the unSU script the process is:
unSU
stock boot image
Magisk
This method did not work for me.
I am on KETAN n10 and initially, viper did not work. I installed magisk but that didn't fix it. nor the meefik busy box. So i decided to uninstall magisk and go back to superSU and it magically worked...
I unrooted from SuperSU itself like shown on the app's forum I believe. It rebooted my phone, I went into recovery first and then just flashed the latest magisk and made the switch :laugh:
SourPower said:
I unrooted from SuperSU itself like shown on the app's forum I believe. It rebooted my phone, I went into recovery first and then just flashed the latest magisk and made the switch :laugh:
Click to expand...
Click to collapse
So you just went into the SuperSU app and used the built in Unroot option, and when the phone rebooted, you went back into recovery and flashed the latest Magisk and did NOT flash a boot.img and everything worked fine? you have root with Magisk now instead of SU and you didnt get a bootloop at all??? (i really want to swap out SU for magisk in my sons LG G2, so he can play PoGo again lol) (His G2 is running CRdroid custom rom, I wonder if that effects the steps I'll need to take)
Can anyone offer me some guidance or assistance please and thank you?
JG420 said:
So you just went into the SuperSU app and used the built in Unroot option, and when the phone rebooted, you went back into recovery and flashed the latest Magisk and did NOT flash a boot.img and everything worked fine? you have root with Magisk now instead of SU and you didnt get a bootloop at all??? (i really want to swap out SU for magisk in my sons LG G2, so he can play PoGo again lol) (His G2 is running CRdroid custom rom, I wonder if that effects the steps I'll need to take)
Can anyone offer me some guidance or assistance please and thank you?
Click to expand...
Click to collapse
If there's a proper backup of the boot image for the SuperSU app's full unroot option to restore, then that process should work perfectly (I've done it on a few devices myself). It's when it can't properly restore the boot image you might have issues and you'll have to do it yourself.
Take a look in the Magisk Troubleshooting guide, under "Moving from another systemless root solution to MagiskSU".
The nuclear method might be, to just flash the full stock OOS zip (can flash in TWRP) which will unroot and restore the boot.img (and everything else!). Then immediately flash Magisk before rebooting (so have the Magisk zip on the phone before updating). This should fully remove SuperSU, install Magisk, and keep TWRP on the phone.
Seeing as the original poster is still on OOS 4.0.3, you may want to update, anyway!
JG420 said:
So you just went into the SuperSU app and used the built in Unroot option, and when the phone rebooted, you went back into recovery and flashed the latest Magisk and did NOT flash a boot.img and everything worked fine? you have root with Magisk now instead of SU and you didnt get a bootloop at all??? (i really want to swap out SU for magisk in my sons LG G2, so he can play PoGo again lol) (His G2 is running CRdroid custom rom, I wonder if that effects the steps I'll need to take)
Can anyone offer me some guidance or assistance please and thank you?
Click to expand...
Click to collapse
I've done this on my 3t but I do have a G3 coincidentally lol, but yes I unrooted from su, it restarted my phone, before booting back into the system I went in twrp right away and then flashed magisk.
There are two options given in the SuperSU app, one is clean up to switch to a different SU app and the other is to permanently unroot. Which option is better?
hypothrax said:
There are two options given in the SuperSU app, one is clean up to switch to a different SU app and the other is to permanently unroot. Which option is better?
Click to expand...
Click to collapse
I chose the Full Unroot option. Then flashed magisk. Worked perfectly.
Use the full unroot option. Catch here is that you might get dm-verity warning. It won't affect the phone in anyway but Android Pay might not work and you will see the warning for 5 seconds, everytime you restart the phone.
Thanks so much for ths thread. I am on Resurrection Remix OS and inititally installed SuperSU over Magisk (which came with the ROM). I decided that I wanted to use Magisk instead and followed the instructions in this thread and it worked a treat.
I want to switch from SuperSU 2.79 to Magisk. I tried the unrooting option in SuperSU but the phone doesnt boot, it stays on the google image. Reflashed SuperSU 2.79 and phone boots without a problem.
Then i booted into botloader and flashed the original stock boot.img from n6f27c factory image, but same result, phone stays at the google image and doesnt boot. Reflasing supersu 2.79 fixes the problem.
What would be the best way to move from supersu to magisk without having to completely wipe phone and flash n6f27c factory file.
Would flashing boot.img and system.img be enough? And then install magisk from twrp to get root again or is there another option that works.
TMG1961 said:
I want to switch from SuperSU 2.79 to Magisk. I tried the unrooting option in SuperSU but the phone doesnt boot, it stays on the google image. Reflashed SuperSU 2.79 and phone boots without a problem.
Then i booted into botloader and flashed the original stock boot.img from n6f27c factory image, but same result, phone stays at the google image and doesnt boot. Reflasing supersu 2.79 fixes the problem.
What would be the best way to move from supersu to magisk without having to completely wipe phone and flash n6f27c factory file.
Would flashing boot.img and system.img be enough? And then install magisk from twrp to get root again or is there another option that works.
Click to expand...
Click to collapse
Try using unsu.zip. You can find it in osm0sis' odds and ends thread. Scroll down through the first post.
ktmom said:
Try using unsu.zip. You can find it in osm0sis' odds and ends thread. Scroll down through the first post.
Click to expand...
Click to collapse
Thanks, that did the trick. Rooted with Magisk now.
For the past two days I've tried unsuccessfully to install Magisk for the hide SafetyNet option.
My phone is a D5803 with the firmware 23.5.A.1.291 R12D Nordic Combined
Let me give the background to my dilemma.
I bought the phone already unlocked
I had TWRP installed and rooted with SuperSU
After a few months, I've decided to change the root for magiskSU so I uninstalled SuperSU 2.92 and attempted to flash Magisk 14 with the result of Error 1. After some fiddling I've bricked the phone and did a full reinstallation of my phone with the untouched firmware.
After reinstalling TWRP 3.1.1 I've tried my luck again to no avail, this time backing up my system.
I scoured the forum and on the net for pointers on how I could do this but I can't seem to find anything to make this work.
I tried going back to the kernel 575, flash Magisk, flash 291 just like the superSU thread,
tried reinstalling stock firmware, unSU, uninstall Magisk, flash magisk,
tried using bootbridge and even Magisk Manager app to patch the boot.img but comes up as failed ELF32 format detected and to use bootbridge needs to be used.
Using bootbridge with Magisk in TWRP "appears" to work but really doesn't do anything
I've tried flash tool from and xperifirm to get a boot.img different of the one I have but when I come to create a ftf, the program jams on me.
I don't want to reinstall SuperSU if I can as I tried HideSU with no results. Help would be greatly appreciated
Kesymos said:
For the past two days I've tried unsuccessfully to install Magisk for the hide SafetyNet option.
My phone is a D5803 with the firmware 23.5.A.1.291 R12D Nordic Combined
Let me give the background to my dilemma.
I bought the phone already unlocked
I had TWRP installed and rooted with SuperSU
After a few months, I've decided to change the root for magiskSU so I uninstalled SuperSU 2.92 and attempted to flash Magisk 14 with the result of Error 1. After some fiddling I've bricked the phone and did a full reinstallation of my phone with the untouched firmware.
After reinstalling TWRP 3.1.1 I've tried my luck again to no avail, this time backing up my system.
I scoured the forum and on the net for pointers on how I could do this but I can't seem to find anything to make this work.
I tried going back to the kernel 575, flash Magisk, flash 291 just like the superSU thread,
tried reinstalling stock firmware, unSU, uninstall Magisk, flash magisk,
tried using bootbridge and even Magisk Manager app to patch the boot.img but comes up as failed ELF32 format detected and to use bootbridge needs to be used.
Using bootbridge with Magisk in TWRP "appears" to work but really doesn't do anything
I've tried flash tool from and xperifirm to get a boot.img different of the one I have but when I come to create a ftf, the program jams on me.
I don't want to reinstall SuperSU if I can as I tried HideSU with no results. Help would be greatly appreciated
Click to expand...
Click to collapse
Have you tried with a different stock kernel, (maybe Elite)? Not sure what the problem is. I've never had trouble with Magisk, but now that I think about it, I don't think I ever tried to flash it on straight stock rom, (I prefer phh anyway in general).
Another thought I had is, if Magisk has a problem with elf format, maybe use Rashr to make a kernel backup image, then flash the backup, (I really don't know anything about this stuff, just shooting in the dark...).