Hi people, i am a new member and cannot talk in the posts so I see myself obliged to open this thread!
After reading the countless messages on SuperSU and phh suhide, I have tried to install the phh's superuser R266, but I get an error when installing (philz recovery) and i decided to install it with TWRP but at the start I was without rom (Download mode).
I have a note 3 with a last stock rom 5.0 this superusers suhide works in android 5.0 or need 5.0+???
I was use a Magisk v6 and phh superuser 17, but with the new update with safetynet don't work. I have unroot to play Pokemon go!! T_T
Thanks for all!
Enviado desde mi SM-N9005 mediante Tapatalk
Related
Can anyone tell me how to unroot supersu on Mi Max 2?
I'd like to install magisk root instead.
I've already tried to unroot using the option in the app Supersu but it doesn't work (bootlooped) ,
so i've reinstalled the old supersu with TWRP and the phone is working.
1) Miui version 9.5.5.0
2) Last version of TWRP installed
3) Supersu v2.82 installed
4) I want to keep all the data and configuration on the phone
Is it possible?
https://forum.xda-developers.com/ap...ersu-v2-05-t2868133/post63615067#post63615067
Do you think is going to work despite this post is 3 years old?
sradica said:
Do you think is going to work despite this post is 3 years old?
Click to expand...
Click to collapse
I use it a few days ago
Just Flash Update-unsu-signed.zip
https://forum.xda-developers.com/attachment.php?attachmentid=4410561&d=1517853382
Then Flash magisk.
I've tried the unsu signed yesterday following the instructions on the XDA post.
Result: bootlooped
Do you really think that if i flash the unsu and immediately after flashing magisk is it going to be ok?
Thank you
Title says it all, I can't root my Xiaomi MI8 (dipper) on MIUI 8.11.15 Global with the latest TWRP by wzsx150, I'm not sure what I've done wrong or is it just not compatible? I'm also using the latest Magisk which is v17.3
Things I've tried:
Flash dm-verity first then flash magisk
Flash Magisk without dm-verity
All of them unsuccessful. Please help me on this one, I really need to root my device. Thank you
Why are you flashing beta version of Magisk?
Sent from my MI 8 using Tapatalk
What's the error message? Tried with 17.2?
If the flashing of Magisk has gone without errors, you may need to download the Magisk Manager apk and install and open it and it will show that you are rooted
Getting Xposed working
-make sure Magisk v18.0 or higher is installed.
-download Riru-core v10 or higher and install it in Magisk Manager
https://github.com/RikkaApps/Riru/releases
-download EdXposed 0.2.9.6.beta (any updated zips will cause bootloop) and install it in Magisk Manager
https://github.com/solohsu/EdXposed/releases
-Install official or third-part Xposed Installer.
reboot.
https://forum.xda-developers.com/devdb/project/?id=13191#downloads
have fun
credits to
rovo
topjohnwu
rikka
givein2u
DVDandroid
Thanks. Works on my APL-AL00 9.0.0.167. Tried 'Exi for Swiftkey' module and it works too.
Be careful and make a backup before.
I got stuck in boot, if I rebooted with root. Without root it started, but nothing worked to uninstall this magisk modules again.
So I had to restore a backup...
Same for me. Stuck at boot. Phone can start without root. Now how can we uninstall this modules without magisk?
SuChh said:
Same for me. Stuck at boot. Phone can start without root. Now how can we uninstall this modules without magisk?
Click to expand...
Click to collapse
I found no way to do it because of no properly working TWRP on EMUI 9.
Before next try first install this module: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
Athanatos81 said:
I found no way to do it because of no properly working TWRP on EMUI 9.
Before next try first install this module: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
Click to expand...
Click to collapse
my alp-l09 when you install the riru and reboot to enter by recovery and open the magisk, it stays and does not pass the logo, but then you will have normal system without magisk and delete magisk completely, because even so the logo does not happens, I tried the two versions of riru V16 and V17 and in this update of the alp is that it does not work, if there is any other way tell me please
Enviado desde mi ALP-L09 mediante Tapatalk
Hi there!
Sorry if this post is duplicated, I searched a lot but other people's solutions didn't work for me so I'm writing here.
I am using Samsung s8+ (sm-g955f) Exynos and wanted to install a different rom. Flashed to stock image-everything ok, installed TWRP from here:
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
=everything ok-booted to twrp and phone working perfectly.
I tried to install Magisk using the twrp method-latest installs in the mega thread. All seemed ok until i rebooted and my touchscreen stopped working.
I tried a lot of things to fix that, including but not limited to:
-reflashing magisk
-flashing stock rom again
-installing twrp without magisk
-tried to uninstall magisk but after stock flash it didnt find any modules to uninstall
-flashed stock boot.img.tar via odin
Nothing worked..As of now my phone is working-boots and loads OS and i can use otg mouse to click around but touch still isn't working. At this point I dont care about rooting the phone or the custom ROM, just want my touch screen working again..
Can anyone help?
nundu said:
I tried to install Magisk using the twrp method-latest installs in the mega thread.
Click to expand...
Click to collapse
What does this mean? What is "twrp method-latest installs in the mega thread"?
Didgeridoohan said:
What does this mean? What is "twrp method-latest installs in the mega thread"?
Click to expand...
Click to collapse
Sorry for the unclear explanation, i mean this: https://www.xda-developers.com/how-to-install-magisk/ , i downloaded a zip magisk file and flashed it via twrp.
Edit:after flashing magisk this way and reeboting the touch issue appeared.
I don't understand enough to be able to explain to you why, but with some ROMs you shouldn't flash Magisk right after flashing the ROM, you should reboot after installing the ROM, then go into twrp and flash Magisk. It has solved many issues for me before, I don't know if it applies to your case because I didn't see your method step by step, but is something to try.
Enviado de meu POCO F1 usando o Tapatalk
[email protected] said:
I don't understand enough to be able to explain to you why, but with some ROMs you shouldn't flash Magisk right after flashing the ROM, you should reboot after installing the ROM, then go into twrp and flash Magisk. It has solved many issues for me before, I don't know if it applies to your case because I didn't see your method step by step, but is something to try.
Enviado de meu POCO F1 usando o Tapatalk
Click to expand...
Click to collapse
Thank you for the response! I will try that but I installed Magisk before the custom rom. In the link I uploaded for TWRP instructions after successful TWRP instalation (part 2 completed with no problems) it gives the options for root-magisk or spersu (part 3) before rom installation so I did that.
I installed twrp on a fresh stock image,because I first wanted to do a clean factory reset on the device, before doing anyting else.
UPDATE
-installed stock rom
-installed TWRP
-installed magisk-Version 20.4, Magisk Manager-v 8.0.2-both green ticks, Root check=ROOT DETECTED
-installed Alexis ROM ( https://forum.xda-developers.com/ga...ce-development/alexis-rom-1-1-stable-t3753975 )
-Every function is working, phone is without bloatware, root is active, twrp is working. Everything BUT the stupid touchscreen... Is it possible something fried during the first install? Can I flash some touchscreen driver?
There are kernels with diferent touch drivers like D8G for instance, you'll find it on github.
Enviado de meu POCO F1 usando o Tapatalk
Hello everyone. I recently updated Magisk and it stopped booting, I have a Mi Mix 2, I managed to install its original rom, but I can't install TWRP and I can't Install Magisk. What I can do ?.
​