help with magisk for pie roms - Moto G5 Questions & Answers

So i find imposible to root a pie rom, everytime i install it says it need aditional setup, and then says setup failed, magisk doesn't shows any tab, except for configuration
Anyone knows how to install magisk and don't have this issues?

Related

[Q] [ HELP] No autostarts in clean master with Magicsk and Resurrection ROM ?

Over my fully stock mobile (With Stock OOS 4.1.7) had installed following in sequence: Factory Reset with TWRP, Flash Stock Modem and Firmware Open Beta 22, then Patch for dm-verity, and finally Resurrection ROM 5.8.4 with GAPPS and no wipe cache/data. Now mobile is working fine and rooted, but two problems still persist - any suggestions ?
Key Issue: Clean master autostarts does not show up, i think root is not detected with Magicsk ? Can I safely flash SuperSU with Magicsk to get it working or some other remedy to be done ?
Secondry Issue: Not sure its related or not, but SafteyNet shows ctsProfile=false, basicIntegrity=false. I've no supersu installed so no question of leftover files, also there is no USB debugging option so that I can enable this stuff (may be required for clean master ?). Alongside other apps like Android Pay, not working due to SafetyNet issues.

Can't get Magisk to work on LineageOS 15.1 (Sailfish)

I have pixel (sailfish) running lineage 15.1 w/ microG and I've followed the exact steps from the official Magisk install page using Magisk v18.1 with manager 7.0 only to get the same safetynet api error. Ive even tried other suggested installation methods from: https://android.gadgethacks.com/how-...el-xl-0177522/
And it left me in a bootloop whereby I had to wipe and reinstall everything.
Anybody please help!
**I already tried clearing my Manager data and also testing MagiskHide by adding a root app to the Hide list and still get the same error

[A320] Viperfx with stock rom

Hi
Im back to stock after months of struggling with Lineage bugs.
All i need is viperfx, which improves internal speaker so much, whem properly configured !
I guess the only way to get it is by using magisk (i tried with a supersu root and a viperfx flash but it didnt work).
So I just spent many hours trying to get magisk to run properly but failed.
I flashed 17.1 in twrp, seemed to work, but it didnt find any module to install, so i updated magisk manager to latest version.
Then i was unable to run magisk manager, instant crash at launch, fc.
Any tip please ?
Thanks

Cant seem to update TWRP Official app after installing magisk/twrp, nor pass safetynet in magisk

Hey folks, im having an issue with getting twrp up and running, as well as magisk i guess?
when i go to update twrp through google play it tells me "cant install official TWRP App, Try again, and if it will doesnt work see common ways to fix the problem" When i go to install the app through their website it tries to update that way and the update fails as well just saying "app not installed", i only have the base version at the moment with nothing in it that just tells me to update the app because its a placeholder that fits into a recovery
on the safetynet end of things if i try and pass the safetynet check i just get an api error screen?
this has been a huge headache from start to finish so if anyone can help me out here it would be grealy apprciated
siccoblue said:
Hey folks, im having an issue with getting twrp up and running, as well as magisk i guess?
when i go to update twrp through google play it tells me "cant install official TWRP App, Try again, and if it will doesnt work see common ways to fix the problem" When i go to install the app through their website it tries to update that way and the update fails as well just saying "app not installed", i only have the base version at the moment with nothing in it that just tells me to update the app because its a placeholder that fits into a recovery
on the safetynet end of things if i try and pass the safetynet check i just get an api error screen?
this has been a huge headache from start to finish so if anyone can help me out here it would be grealy apprciated
Click to expand...
Click to collapse
That's because there is no twrp for the pixel 3. There is some development for the 3 XL, but nothing for the 3.
That's because there is no twrp for the pixel 3. There is some development for the XL, but nothing for the 3.

How can I modify what I perceive as a rooted device?

Hi. I was install LineaseOS 17.1 to xz2c. Then, installed the app that I use.
But, Some apps not work because, Rooting detected from my Phone.
Of course, I didn't rooting. (Wipe and only installed LOS and gapps)
I think I recognize it as a Rooted device due to the settings such as build.prop.
To solve this problem, I've tried Magesk or some other method( LOS Recovery -> pull build.prop and Modify), and there's still a problem.
I want to know which part of build.prop or what elements of something else are recognized as a routing device and how to solve this problem.
How should I fix something?
Previously, I tried to solve this problem with Magisk and Module, but it didn't work perfectly.
I have installed magisk and installed magiskHide Props Config 5.4.0 and universal safety net fix 1.1.1.
But Safetynet ctsProfile failed, and some apps works well, but others didn't.
There are only LOS and Gapps now.( Not Uninstall, Full Wipe and reflashing LOS17.1)

Categories

Resources