Related
I just got my unlocked G5 Plus (XT1687) today and I've unlocked the bootloader and installed TWRP and SuperSU.
However, SuperSU seems to be randomly losing root access. It works for a little while, but then I'll get an error in SuperSU about root undetected and I have to reboot back into TWRP and reflash SuperSU. This has happened 3 times so far today.
Has anyone seen this issue in the stock rom? Is there some security process stealthily running in the background that deletes the su binary on a regular basis? I'm running build number NPN25.137-33.
Edit: SuperSU is running in systemless mode
I rooted mine using the Toolkit here yesterday and that afternoon it acted like i lost root. Root checker would say i didn't have root and just constantly flash that it was trying to get permission. I restarted it and it's been fine ever since.
I tried rebooting and it restores root temporarily, but I'm still losing it constantly (no set time interval, but I've seen it lost within a few minutes of a restart). Getting really annoying.
Would flashing one of the modified stock kernels potentially help this?
Hi,
I've the same problem. XT1685
Already done:
- reflash stock
- reflash updated stock
- reflash SuperSu 2.82 SR3 and SR4
Ever the same, after some (short) time the root is lost.
Unrooted from SuperSu app and installed Magisk 14.0: loses root after some moments!
Edit: after some reboots now its working. The root is maintained from 2 days. So Magisk 14.0 works.
Hi.
Here another confirmation. My XT1687 loses root rights once in a while. I’d say it’s about every 3rd day or so.. Simple reboot brings root rights back.
Config:
Build: NPN25.137-83
Kernel: 3.18.31-ElementalX
Root: Magigk 14.0
EDIT: When checking Magisk App I found out that Magisk crashed each time I started Superuser. So, I deinstalled Magisk and re-installed again. No problem ever since.
Always remember to un-optimize Magisk- (or SuperU-) App in battery options! "Boeffla-Doze-Control" also helps to avoid apps from falling asleep.
On StokROM + SuperSU 2.82SR5, I also experienced the same situation.
Running the following command no longer causes problems.
Code:
ln -s /su/bin/su /system/bin/su
Hello there.
I actually rooted my Moto G5 Plus according to this instructions. I flashed TWRP 3.2.1.0 and the last stabel SuperSU.
I also uninstalled SuperSU over "apps" on Stock Rom and tried to flash Magisk, but this causes in an error while flashing (It says something about "Error 1" and about the path, where the magisk.zip is, for further information I would try to flash again and tell you the whole error).
The latest thing I tried was running the command from highwaystar2699 over the terminal from TWRP, but still I loose root randomly.
Can anybody help? =(
Thanks in advance
FlatD
No root losses anymore
Just_a_fan said:
Hello there.
I actually rooted my Moto G5 Plus according to this instructions. I flashed TWRP 3.2.1.0 and the last stabel SuperSU.
I also uninstalled SuperSU over "apps" on Stock Rom and tried to flash Magisk, but this causes in an error while flashing (It says something about "Error 1" and about the path, where the magisk.zip is, for further information I would try to flash again and tell you the whole error).
The latest thing I tried was running the command from highwaystar2699 over the terminal from TWRP, but still I loose root randomly.
Can anybody help? =(
Thanks in advance
FlatD
Click to expand...
Click to collapse
Well, I can say, that after some updates of Magisk I don't experience the problem anymore. Neither me nor a friend who has the G5 (not Plus) have ever lost our root since being on Magisk Version 16.0
Maybe you should give Magisk a try...
G5 Plus Mate said:
Well, I can say, that after some updates of Magisk I don't experience the problem anymore. Neither me nor a friend who has the G5 (not Plus) have ever lost our root since being on Magisk Version 16.0
Maybe you should give Magisk a try...
Click to expand...
Click to collapse
Like I said, installing Magisk returns an error.
Nevertheless, after I ran the command from @highwaystar2699 and canceled the battery-optimization of SuperSU I've got still root after already 5 days of using the phone.
So, thanks for your help, for now =)
I have no ideas that you can solve your problem ...
What I got interested in your post(#8) is "I also uninstalled SuperSU over apps on Stock Rom".
If there is no mistake in my memory, SuperSU have an "unroot" menu, which should be used to uninstall SuperSU.
Did you uninstall by using "unroot" menu?
In any case, I am not sure how to recover the state of your g5plus.
I will not be able to help you. sorry.
highwaystar2699 said:
On StokROM + SuperSU 2.82SR5, I also experienced the same situation.
Running the following command no longer causes problems.
Code:
ln -s /su/bin/su /system/bin/su
Click to expand...
Click to collapse
How and where to run this code? Fastboot or adb terminal?
sudiptoc19 said:
How and where to run this code? Fastboot or adb terminal?
Click to expand...
Click to collapse
Just boot into TWRP and open the terminal (you can find it under "advanced" or "tools", not completely sure right now) and run that command. Maybe you should check where the mentioned su-folder is located right now on your phone, 'cause in my case it was at a different location.
@highwaystar2699: Yeah, afterwards I also realized that unroot-option
So maybe I have to unroot with that option and retry to install magisk. I will try that maybe, if I should loose root again. Or when the next update comes. (I'm a little afraid about that. Sounds difficult to OTA-update after rooting your G5 Plus...)
Either way: Thanks for your help! If I try something, I will report about it here
Super SU working for G5 plus. I don't think so. It has some problems. Bootloops are frequent.
Sooooo, hello again all! @highwaystar2699: I lost root again after one hour when I had to reboot the phone so I just thought about: "Why don't give it a try now?"
So I flashed the superSU again in TWRP to get root, startet the SuperSU app and choose "Unroot". I was asked if I want to unroot because of an OTA update, which I answered with "no". The app closed and root was gone.
I rebooted into recovery and tried to install the magisk 16.0 zip aaaaaaannnnd...
...got Error 1 again.
At the point "Unmounting partitions", TWRP says
"Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v16.0.zip'"
Now I'm back to superSU again. Damn, I don't know whats wrong here =(
Short edit for @Yeshu_bablu: Yes, after installing superSU, you've got 2 to 3 bootloops. But only the first time. After it's installed, the phone boots normal.
So, according to you... Which is better? SuperSU or Magisk?
SuperSU is obsolete, twrp you need latest version 3.2.1.0 or higher number if updated.
Once twrp installed you can install the rom of your choice with or without gapps package of your choice.
Then you can install magisk 16.3 for root and modules if wanted.
Yeshu_bablu said:
So, according to you... Which is better? SuperSU or TWRP?
Click to expand...
Click to collapse
SuperSu is root, TWRP is recovery, 2 different things.
[email protected] said:
SuperSu is root, TWRP is recovery, 2 different things.
Click to expand...
Click to collapse
I'm sorry, SuperSu or Magisk?
Short update and big thanks to @highwaystar2699 and @Wolfcity.
After I completely lost root with SuperSU, I tried to install Magisk but failed everytime with already known Error 1.
But finally, after I got a stock boot.img and flashed it and instantly (!) installed Magisk after flashing the boot.img, the phone startet normal and now I've got root without problems.
FIY: When I only flash the boot.img and don't root it in TWRP, the phone keeps bootlooping.
So, to give @Yeshu_bablu an answer: Magisk is better. SuperSu only make problems with Moto G5 Plus. Magisk works like a charm.
Hello,
recently I have flashed my ze500kl with XenonOS. I would like to go back to stock rom but I have couple problems.
First of all - my bootloader is now locked. I wanted to unlock it via SuperSU, that is already installed on my phone but when I try to open SuperSU App I see this:
"SU Binary occupied"
So I found tutorial on how to fix this issue, but the problem is i can't uninstall SuperSU, I can only disable it in App options.
Then I tried to install TWRP via App from Google Store, but offcourse my phone isn't rooted so I can only download TWRP installation files but can't initiate installation via App. I downloaded TWRP on my PC, opened ADB in CMD, installed it there and rebooted my phone. TWRP isn't loading and my device stuck on ASUS welcome screen.
I tried also WINDROID but I get lots of errors, so it's not working for me either.
Please help me unlock and root my phone. I really want to go back to stock os.
Thanks!
svyatogor92 said:
Hello,
recently I have flashed my ze500kl with XenonOS. I would like to go back to stock rom but I have couple problems.
First of all - my bootloader is now locked. I wanted to unlock it via SuperSU, that is already installed on my phone but when I try to open SuperSU App I see this:
"SU Binary occupied"
So I found tutorial on how to fix this issue, but the problem is i can't uninstall SuperSU, I can only disable it in App options.
Then I tried to install TWRP via App from Google Store, but offcourse my phone isn't rooted so I can only download TWRP installation files but can't initiate installation via App. I downloaded TWRP on my PC, opened ADB in CMD, installed it there and rebooted my phone. TWRP isn't loading and my device stuck on ASUS welcome screen.
I tried also WINDROID but I get lots of errors, so it's not working for me either.
Please help me unlock and root my phone. I really want to go back to stock os.
Thanks!
Click to expand...
Click to collapse
For anyone who struggle with the same issues.
Use ADB and twrp_2.8.7.7.img. I don't know why, I don't know how but this version of TWRP works.
I have read many threads and lots of videos and cannot seem to get the Magisk installed.
I have flashed back to stock many times with (N900VVRUEOF1_N900VVZWEOF1_N900VVRUEOF1_HOME.tar.md5) in order to try multiple methods.
Rooted with Arabictoolapp - used rootchecker to verify/application also says true for root
followed: https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010
installed SU from playstore to unlock bootloader using the adp method - shows developer mode to verify - using eMMc to verify CID starts with 15
followed: https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
installed twrp using official twrp app & also tried ODIN in another trial (picked verizon americas and got twrp-3.2.3-0-hlte.img.tar and twrp-3.2.3-0-hlte.img )
turned phone off and boot into recovery to verify; at this time i created a recovery
using MagiskManager i downloaded the zip (Magisk-v18.1.ip) and flashed using twrp - no errors but when i restart the phone it says Magisk not installed
next attempt was to extract the boot.img from the stock OF1 and then flash the Magisk - no errors but when i restarted the phone it says the same thing - Magisk not installed
another attempt was to patch the boot.img and got a patch_boot.img then using TWRP i flashed the patch_boot.img - restarted and magisk not installed
after further digging, i tried another method which was to unroot using SU, reboot, go into recovery to then install Magisk - magisk not installed
*note each attempt to install Magisk unrooted my phone
*was able to use Magisk-uninstaller-20190204.zip to uninstall Magisk manager from recovery - icon went away
anyways i am completely stuck now. any suggestions or comments on my approach?
jordanfan23 said:
installed SU from playstore to unlock bootloader using the adp method - shows developer mode to verify - using eMMc to verify CID starts with 15
followed:
Click to expand...
Click to collapse
Did you uninstall SU before trying to install magisk. The two together may cause conflict.
cssr said:
Did you uninstall SU before trying to install magisk. The two together may cause conflict.
Click to expand...
Click to collapse
Yes my last attempt i tried.
please help! there has got to be something i am doing wrong or missing. i can flash the uninstall zip and it does uninstall the magisk manager
@cssr any other input or suggestions?
jordanfan23 said:
@cssr any other input or suggestions?
Click to expand...
Click to collapse
Try twrp 2.8.7 hltevzw. You are using the stock ROM which is android 5. Twrp 3.1 and higher is for android 7 and up. I missed that the first time I read your post.
cssr said:
Try twrp 2.8.7 hltevzw. You are using the stock ROM which is android 5. Twrp 3.1 and higher is for android 7 and up. I missed that the first time I read your post.
Click to expand...
Click to collapse
no go =(
@cssr should i try another version of magisk?
jordanfan23 said:
@cssr should i try another version of magisk?
Click to expand...
Click to collapse
Yes. Are you installing Magisk .zip in twrp and installing Magisk Manager APK after normal reboot?
cssr said:
Yes. Are you installing Magisk .zip in twrp and installing Magisk Manager APK after normal reboot?
Click to expand...
Click to collapse
what do you mean after normal reboot? so flash magisk in twrp. reboot. reboot again then install magisk manager? do you know what version of magisk i should run and where i can find the dl link?
What he means is you install the Magisk ZIP via TWRP in Recovery mode, reboot the phone, then you install Magisk Manager via the APK.
Go to magiskmanager dot com website which has the ZIP installer plus the APK for the Manager.
I only just recently tried to tackle this challenge. I also installed 0F1 with Odin, then rooted with Arabic. I was messing with Pokemon go and it wasn't happy I was rooted. I downloaded magisk manager, installed it that way. At reboot, angry message from Verizon that I have custom software and phone won't boot. I assume this is because I didn't install custom recovery.
If you figure a way to get this done, I will be grateful. One thing I don't quite follow. Magisk is a root method...so should we really be rooting the phone prior? Seems redundant and going against the whole point of magisk. Right?
I wanted to play around with spoofing GPS with PGO which requires making a GPS spoofer a system app (need root for that). Is that still possible using magisk?
I'll post any updates I have as well.
Hi guys!
First of all, please do not send me to somwhere on forum because I have tried dozen of ways do deal with problem. My phone is LG G6 running on android pie. TWRP installed, Magisk installed. Im trying to instal viper4droid. I have tried download module from Magisk itself, I have tried to download .apk file from different sources, I have tried to download .zip file, I have tried to installed as apk itself and grant root accesss, tried by TWRP, tried unify installers and **** knows what else. Trouble is, First few times it was installed but status was "not running", Today after many attempts to deal with that viper4droid installing drivers and.......after each reboot its doing it again. Moreover i have found that sometimes Magisk did not show up the newest version of v4a as a module to download. So......is somebody for the love of god know what the **** is wrong? thank you.
marcin3595p said:
Hi guys!
First of all, please do not send me to somwhere on forum because I have tried dozen of ways do deal with problem. My phone is LG G6 running on android pie. TWRP installed, Magisk installed. Im trying to instal viper4droid. I have tried download module from Magisk itself, I have tried to download .apk file from different sources, I have tried to download .zip file, I have tried to installed as apk itself and grant root accesss, tried by TWRP, tried unify installers and **** knows what else. Trouble is, First few times it was installed but status was "not running", Today after many attempts to deal with that viper4droid installing drivers and.......after each reboot its doing it again. Moreover i have found that sometimes Magisk did not show up the newest version of v4a as a module to download. So......is somebody for the love of god know what the **** is wrong? thank you.
Click to expand...
Click to collapse
Hi man, there are three versions of viper4ndroid on magisk, try the viper4android fx legacy materialized as normal app after disabling play protect on google playstore. hope this helps
I will try that in a minute mate.
didnt work.
I have the same problem. I switched to viper hifi and now after reboot it is working but after some time it stops till i reboot it again. I think it is because of the pie version, on oreo everything works fine. After every reboot every mofule in magisk reinstalls. For example youtube vanced instals like new and i have to set it up after the reboot.
IIRC it required me to install viperfx (the new version, not legacy or xhifi), audio modification library and audio compatibility patch, have you done that?
I have tried all three version of viper. I have isntalled it as a apk and modules in Magisk. All possible audio patches and compatibilies mods from magisk are intalled as well.
marcin3595p said:
I have tried all three version of viper. I have isntalled it as a apk and modules in Magisk. All possible audio patches and compatibilies mods from magisk are intalled as well.
Click to expand...
Click to collapse
if you still have this problem, try installing viper4android 2.7 as apk from xda lab, I was downgrading back to pie sometimes ago and couldn't get viper to work, besides the 2.7
So today I bought a used Nexus 6P for the purpose of installing Kali Nethunter on it, and then after some searching I found out that I should root the device first, so I did following this guide using SuperSU, I installed the SuperSU from this website, the phone then hung on the Google logo for like 30 minutes, then I found out that the SuperSU project is dead, I said maybe because it's an older phone the root should work and then I entered recovery mode through TWRP and went to the terminal and I saw the # sign and to make sure I ran the command whoami and it gave me root, and then I read that if I'm stuck in a bootloop I should reflash the ROM that I already have installed, but I said it wouldn't make a difference if I flashed Nethunter, it's a new ROM anyway, and now it's been stuck on the Google logo for another 30 minutes.
Any help would be appreciated, Thanks in advance.
@Person_0
A side remark:
To install Kali Nethunter ROM TWRP isn't needed, because Kail Nethunter ROM isn't a standalone Custom Android ROM but merely an Android ROM overlay: your existing Android installation gets extended by a bunch of apps and binaries needed by those to run, nothing else.
Wondering why peoples think they have to install TWRP Recovery and then use TWRP Recovery to install Android apps from a given ZIP, when the same is achieved with adb sideload command from the computer ?
Person_0 said:
So today I bought a used Nexus 6P for the purpose of installing Kali Nethunter on it, and then after some searching I found out that I should root the device first, so I did following this guide using SuperSU, I installed the SuperSU from this website, the phone then hung on the Google logo for like 30 minutes, then I found out that the SuperSU project is dead, I said maybe because it's an older phone the root should work and then I entered recovery mode through TWRP and went to the terminal and I saw the # sign and to make sure I ran the command whoami and it gave me root, and then I read that if I'm stuck in a bootloop I should reflash the ROM that I already have installed, but I said it wouldn't make a difference if I flashed Nethunter, it's a new ROM anyway, and now it's been stuck on the Google logo for another 30 minutes.
Any help would be appreciated, Thanks in advance.
Click to expand...
Click to collapse
i also facing same issue . after installting super su my nexus 6p is stuck at boot logo.
i tried to see if adb can see my phoen when data cable is connected now it doesnt even sees it ,
adb devices list no device please help