Hi, I am quite new to rooting and everything, but I managed to root my phone: (HTC One S C2 stock rom) with WinDroid Toolkit v3.1, which worked great. When I try to install Xposed, I grant it the root access, but after reboot I always get "app_process version "58" has been installed preciously but version "47" was found now. if you didn't expect an old file to be restored, you might want to try installing via recovery (auto or manual)". I tried the auto recovery and the phone entered into a try-to-load loop showing TEAMWIN for second. I accidentally ended it somehow. I tried v 2.7; 2.6.1. and 2.6. Is the problem with phone or with the version?
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!
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.
Hi,
I need some help
Today I successfully installed the newest stable Xiaomi.eu-ROM on my finally unlocked Mi8, using TWRP from here: https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-3-1110-t3869729
TWRP is working flawlessly, but I didn't succeed in making root with Magisk to work.
What I did:
- I booted into TWRP
- formatted data
- rebooted back into TWRP
- flashed DM-verity disabler from here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
- flashed Magisk v18.0 right after from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
- wiped dalvik cache
- rebooted the phone
But everytime I did it, I didn't had root access (checked with Root Checker app) when the phone finally booted up to MIUI 10.1.2.0 (PEACNFI).
I even didn't have Magisk Manager showed up.
Can you tell me what I did wrong? I don't have a clue
Thanks a lot and best regards
Mischa
what does magisk manager tell you about your magisk installation status?
Strange thing...
After I rebooted the phone, there was no Magisk Manager nor the phone was rooted, what I checked with Root Checker app.
Then I used it a couple minutes before it became really laggy. My chosen theme disappeared back to stock theme, scrolling was nearly impossible and the screen went black.
I was not able to wake up the display again, so I held down the power button a couple seconds until the phone rebooted.
Now I saw that the Magisk Manager was installed, without me doing anything else than rebooting after the phone got unusable.
Weird, right? I read that there might be lags after installing Magisk, but that it's going to be like that was surprising.
Anyway, I have root now, TWRP works, Magisk v18 is installed. Now I only have to find some must-have-modules, e.g. like stereo-mod.
BTW, could it be that Netflix isn't working on rooted phones? I always get error 14 saying that the Netflix-service is not reachable even though I have internet connection.
hey dude i know this isnt a guide
but i followed your kind of direction after spending the whole afternoon and few hours in the evening to figure how to root this phone and finally it worked (so far)
thanks a lot my man
and i didnt even format after flashing twrp i hope it didnt **** up my phone
So I finally went ahead unlocking the BL & rooted my Mi9Tpro, using the program by Maunofrio.
So far, so good. Installed twrp from within the program, along with some kind of superSU.
I installed some apps needing root, but they complained over an outdated supersu, so
I then installed the superSU by chainfire. First 2.82 wich wouldn't update the binaries.
Then the 2.79 version, that was said to be more bug free.. It didn't want to update the
binaries either, the normal way. So I then chose the other option (to DL by twrp).
Now my phone won't boot past the boot screen. I can start both fastboot and
recovery mode (twrp). Would anyone be kind and tell me how to solve this?
I just don't know how to proceed (so I guess I shouldn't have fiddled at all).
Just flash Magisk for root.
That will work 4sure.
Televinken said:
So I finally went ahead unlocking the BL & rooted my Mi9Tpro, using the program by Maunofrio.
So far, so good. Installed twrp from within the program, along with some kind of superSU.
I installed some apps needing root, but they complained over an outdated supersu, so
I then installed the superSU by chainfire. First 2.82 wich wouldn't update the binaries.
Then the 2.79 version, that was said to be more bug free.. It didn't want to update the
binaries either, the normal way. So I then chose the other option (to DL by twrp).
Now my phone won't boot past the boot screen. I can start both fastboot and
recovery mode (twrp). Would anyone be kind and tell me how to solve this?
I just don't know how to proceed (so I guess I shouldn't have fiddled at all).
Click to expand...
Click to collapse
Download and flash rom from this thread. (For recovery, not fastboot.)
https://forum.xda-developers.com/k20-pro/how-to/redmi-k20-pro-firmware-10-3-8-0-9-6-13-t3939647
Thanx, fellows!
I tried reflashing Magisk once more, & it did the trick.
:good::silly: