SuperSU 2.79 for OOS? - OnePlus X Q&A, Help & Troubleshooting

I am looking for the SuperSU 2.79 zip that works on OOS. the one I downlaoded from chainfire sent it into a bootloop

Might work if you initiate systemless mode but easier just to flash modded 2.78 for oos3 and just update later from playstore.

Exodusche said:
Might work if you initiate systemless mode but easier just to flash modded 2.78 for oos3 and just update later from playstore.
Click to expand...
Click to collapse
can you link me to modded 2.78?

Here

Related

Root is lost !!!!

hi guys
i have e2333 mrashmallow rooted
when i tried to update supersu binary , i got installion failed
then i flashed un-su zip , after reboot i lost root
i tried to reinstall root in this thread http://forum.xda-developers.com/m4-aqua/general/root-t3421932
but with no hope
so any one have an idea
Did you updated SuperSU via PlayStore to 2.78 ???
MartyX1987 said:
Did you updated SuperSU via PlayStore to 2.78 ???
Click to expand...
Click to collapse
Yes
I had the same problem. When SuperSU asks you about updating binaries, hit cancel. Then go to SuperSU's settings, find "Cleanup" section and hit reinstall. This should reverse SuperSU to 2.76. After that there should be no more binaries error. Don't install 2.78 update. I've done these steps and root and SuperSU works fine.

Which SuperSU for 3.1.4?

I tried flashing 2.79 and it went into a bootloop. Which version do I flash to root stock 3.1.4?
BrokenBee said:
I tried flashing 2.79 and it went into a bootloop. Which version do I flash to root stock 3.1.4?
Click to expand...
Click to collapse
You must use a modified version of SuperSU to force systemless install.
Here you have Chainfire's version of 2.79 modified by me.

Anyone else having issues with MIUI 7.6.15, twrp + supersu or magisk

for some reason whenever I flash supersu or Magisk the phone just hangs at the MI logo with 7.6.15 global beta rom, I do the same flash method every time and this is the first time it has happened..
try 1
zcx twrp, flash 7.6.15, flash supersu, reboot and it doesnt boot
try 2
zcx twrp, flash 7.6.15, flash magisk, reboot and it doesnt boot
try 3
zcx twrp, flash 7.6.15, reboot, -boots fine
edit:
try 4 .
zcx twrp, flash 7.6.15, flash just supersu 2.82, reboot and it boots, so now I can say it has something to do with Magisk or Xposed
so I might now try to flash Magisk, but run the xposed uninstaller incase the magisk.img image still carries xposed module from previous installs this way I can narrow it down from xposed or magisk
I'm having the same issue. I try to flash Super SU after flashing MIUI 7.6.15 and I also try to flash Xposed but it hangs on the Mi logo and won't boot properly. If I hols the power button down for ten seconds to turn the phone off and then get to recovery mode by holding down the volume up button with the power button I can reflash MIUI and it works fine on its own. Wonder is it a Super SU issue? Might try an older version of MIUI....
Same issue, tried everything. :'(
Magisk and zcx super su working but not xppsed niether systemless nor solarwarez editon.
+1
just updated my phone via zcw twrp. su and magisk works fine, only xposed got me stuck at the logo.
No problem with magisk v12, boot normal
Problem with xposed v87, stuck in logo
now back to v7.6.7, and waiting for FIX
Flashed v87.1 xposed
Worked
adiversion said:
Flashed v87.1 xposed
Worked
Click to expand...
Click to collapse
Link?
Sent from my kenzo using XDA Labs
Flash the modified xposed, it's working with the latest global beta. Link:
https://forum.xda-developers.com/xposed/unofficial-xposed-miui-t3367634/page77
Btw: why u guys still use xposed? Any recommendations for modules except YouTube adaway which I should try?
the issue is with SuperSu 2.86, should flash Supersu 2.76, im in build 7.6.8+Supersu 2.76 and all works fine and Xposed not work fine in this builds

Oreo stock root

It seems it is impossible to get root with magisk on latest Oreo stock. Maybe someone found solution?
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
dolar4ik said:
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
Click to expand...
Click to collapse
its not work for me:crying:
Try to follow this guide then: https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
But use latest magisk beta instead of suggested 15.3.
And keep in mind that it is possible to easily restore working state with magisk uninstaller.
Do you have any errors during magisk or workaround installation in twrp console?
dolar4ik said:
Try to follow this guide then: https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
But use latest magisk beta instead of suggested 15.3.
And keep in mind that it is possible to easily restore working state with magisk uninstaller.
Do you have any errors during magisk or workaround installation in twrp console?
Click to expand...
Click to collapse
now its working for me.:highfive::highfive:
dolar4ik said:
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
Click to expand...
Click to collapse
Hi, does not work for me, stuck at bootloader logo, tried Magisk, followed the steps many times but nothing, can you help please ?
evnimaster said:
Hi, does not work for me, stuck at bootloader logo, tried Magisk, followed the steps many times but nothing, can you help please ?
Click to expand...
Click to collapse
follow this: https://forum.xda-developers.com/mot...reo-8-t3743273
Code:
echo keepverity=true>>/data/.magisk
echo keepforceencrypt=true>>/data/.magisk
Is there a way to remove encryption already?
Remove root?
Is it possible to remove root and the TWRP without hard reset? Does anyone already have the original recovery of Oreo?
DavidKalil10 said:
Is it possible to remove root and the TWRP without hard reset? Does anyone already have the original recovery of Oreo?
Click to expand...
Click to collapse
There is magisk uninstaller provided in official thread.
To remove twrp you just need to flush original recovery via fastboot
Hello guys, can I have some advice on whether I should install this latest Oreo update on my moto z, how is the battery doing on this update? And overall experience?
@dolar4ik
i reflash the stock oreo ROM,then flash TWRP,flash magisk,flash f2fs bug workaround, stuck at bootloader logo,how can i do it??
Flash the Magisk uninstaller, reboot to recovery (you have this option in TWRP) and flash again only the Magisk 16.3 (without the f2fs bug workaround). This worked for me two days ago.
Today I updated to the latest Magisk 16.4 without any problems.
lesbianu said:
Flash the Magisk uninstaller, reboot to recovery (you have this option in TWRP) and flash again only the Magisk 16.3 (without the f2fs bug workaround). This worked for me two days ago.
Today I updated to the latest Magisk 16.4 without any problems.
Click to expand...
Click to collapse
still not work for me.:crying::crying:
---------- Post added at 03:12 AM ---------- Previous post was at 02:58 AM ----------
This is strange. It works on Oreo OTA but it does not work in full flash Oreo ROM.
have anyone help me??
rakee said:
It works on Oreo OTA but it does not work in full flash Oreo ROM.
Click to expand...
Click to collapse
This is right.
I re-flashed my phone using the OPL27.76-51 firmware. Now, no way to install Magisk (old, new, any version).
The solution, I restored a TWRP backup made at the first bootloader unlock (when the ROM was updated only using OTAs, not flashed). Immediately I was able to install Magisk 16.4 - without any F2FS workaround.
HERE is my TWRP backup containing the partitions: Boot, Data & System. Hope it helps!
rakee said:
@dolar4ik
i reflash the stock oreo ROM,then flash TWRP,flash magisk,flash f2fs bug workaround, stuck at bootloader logo,how can i do it??
Click to expand...
Click to collapse
Uninstall magisk with it's own uninstaller.
I installed Magisk on the full Oreo release and everything is working.
I did make a "less bloat, less bs" zip version but I doubt it would make a change.
If you guys want, I can upload it when I get home.
The Marionette said:
I installed Magisk on the full Oreo release and everything is working.
I did make a "less bloat, less bs" zip version but I doubt it would make a change.
If you guys want, I can upload it when I get home.
Click to expand...
Click to collapse
Could you provide your twrp ZIP Version? That would be great.
lesbianu said:
This is right.
I re-flashed my phone using the OPL27.76-51 firmware. Now, no way to install Magisk (old, new, any version).
The solution, I restored a TWRP backup made at the first bootloader unlock (when the ROM was updated only using OTAs, not flashed). Immediately I was able to install Magisk 16.4 - without any F2FS workaround.
HERE is my TWRP backup containing the partitions: Boot, Data & System. Hope it helps!
Click to expand...
Click to collapse
Just got myself a hand me down Moto z.
My friend who gave it to me hasn't touch the phone for a year.
So i started with 6.0 and after multiple updates, now i am on Oreo.
Since i have done ota from Marshmallow, would this method work?
Bootloader was never unlocked.
thanks for any input

Question TWRP

Hi guys, will Twrp be available for this device so I can root it with Supersu, instead of Magisk, couldn’t get Viper4Android and Adaway run properly with Magisk.
Yes, TWRP will be available, I tried making it for now with a dump but failed, waiting the real sources.
Also, use magisk lol, supersu is ancient and doesn't work. It's impossible that magisk didn't worked with those apps
I think it didn’t work cause of systemless root
TroyCas99 said:
I think it didn’t work cause of systemless root
Click to expand...
Click to collapse
Well no idea, all that I know is that Adaway and 99% Viper is working fine with Magisk.

Categories

Resources