hello who got safty net failed in magisk here is solution
first clean flash rr i mean only wipe system partition
use rr bulid 16 march
reboot and check supersu and busybox install if yes then full unroot supersu and uninstall buybox using buybox app
and disable usb debugging
and then reboot to recover and install magisk 11.5
reboot
now install magisk a manger (if you not loss root then reboot then reboot one or 2 time if will get it)
magisk manager setting-check magisk hide and adblock host
and uncheck busybox see pic in attachment for reference
now reboot now you will able to bypass satynet as well as no loss of root and busybox will work even it disbale in magisk manager
remember do not modified any system partition
and don't install any sound mod
use magisk version dobly and viber4android
magisk version of unified adblocked
magisk verson of youtube adblock patched apk
and yes one more thing i forget
plz check two file su and busybox in system/bin and system/xbin if you found these plz delete then using twrp filemanager(remember to mount system) and use stock kernal
i tested this methode on rr
u can try in other rom as well as stock miui rom but before if you used xposed then install it first and use magisk version of xposed for miui or stock
hit thanks button if i help
This is my installation process [last post is OK]
https://forum.xda-developers.com/galaxy-s5/help/wifi-problem-flashed-lineageos-t3576865
Below are screens from CATLOG [not full tho]
If I try to update binaries in TWRP it stops [nothing in TWRP logs about SU], restarts and stops during Lineage loading screen forever.
So I flash ROM again, and SuperSU from TWRP to fix it.
I was reading that after flashing SuperSU - during first restart it should ask me something like "DO you want to keep root" - it doesn't happen.
SuperSU has no apps listed with root access, but root is OK. TitaniumBackup works, but I'm afraid some of the apps doesn't work properly
Now I'm using
lineage-14.1-20170329-nightly-klte-signed.zip
addonsu-ARM-signed_14.1
SM-G900F
Is there a way to have it done?
I remember like trough a fod that once I was setting permissions in Terminal for some files before updating SU? AM I correct?
Thanks for reding
Hi,
With LineageOS, you must only use one root method otherwise problems will occur. The addonSU zip and SuperSU are not the same thing.
The provided root SU zip from Lineage should be enough to give root permissions for apps. If you want to use SuperSU instead of the SU provided by the Lineage team, you must not flash the addonSU zip.
Saber said:
Hi,
With LineageOS, you must only use one root method otherwise problems will occur. The addonSU zip and SuperSU are not the same thing.
The provided root SU zip from Lineage should be enough to give root permissions for apps. If you want to use SuperSU instead of the SU provided by the Lineage team, you must not flash the addonSU zip.
Click to expand...
Click to collapse
I have tried to flash everything and indeed only addonsu-ARM-signed_14.1 is working from TWRP level. Although SuperSU from APK is working OK [latest SR4].
So root seems to be fine for browsing into root or TB! is not complaining about root, but I can not update SU binary - I have also updated Lineage to today's nightly - same thing.
I've used an S4 with lineage and flashing supersu doesn't work. ONE app in particular will not work because the su part of lineage (and old cyanogenmod) doesn't cooperate; it needs supersu for some reason. I was originally on Cyanogenmod from about a year ago, and tried flashing supersu and had this very problem, which is why I tried lineage, but lineage doesn't work and I cannot flash supersu either. I can install from the play store, but it won't update the binary; flashing in recovery fails (in both older cyanogenmod and lineage os) at the boot image patcher step.
supersu 2.79 said:
Finding boot image
Boot image: /dev/block/mmcblk0p20
Extracting ramdisk
Decompressing ramdisk
Failure, aborting
Click to expand...
Click to collapse
The only reason I'm having to resort to this is because Samsung has a problem with their s7 screens failing and won't do a recall...so I'm having to use an older phone and trying to setup my rooted apps, all of which work with the standard Cyanogenmod root or lineage+su addon, except for one app.
EDIT:
Ah-ha, system mode may be the solution, but I'm still trying to get it to boot without getting stuck! I haven't tinkered with supersu in well over a year, and I didn't even know there were two methods for it now.
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
I flashed purenexus rom .previously I was using truepure rom. I did clean install twice . wiped everything except internal storage and then installed purenexus rom and dynamic gapps then wiped cache and dalvik . everything went smooth but now device isn't rooted any more . I installed super su and it said root not detected
Can you please guide me how to root again . which root method is best ? And how to do it ?
Any help would be appreciated.
Thanks
https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
You'd be good to go with Magisk (get the v12 and flash the zip in TWRP)
Now days ROMs don't come pre-rooted as often as concern for system modification and apps that block use on rooted phones.
Magisk has the ability to do root without modifying the system partition (so called systemless root) also has option to quickly hide root
If you don't care about that you can follow the guidelines suggested above by the other answer and you'll find SuperSU systemless root, and you're good to go.
Quick note, if superSU fails (bootloops) read the TWRP log while you installed SuperSU and try to find in which mode did it got installed. This is because older versions of SuperSU failed to detect Moto Clark as systemless and went for system root , which caused bootloop. There are instructions on SuperSU thread on how to force systemless root method
hi, i had successully upgraded my x compact to oreo, installed twrp 3.2.1 (without encrytion support) and rooted with magisk. Everything has been working fine until i messed up magisk with some module (busybox).
My phone hanged at Xperia logo after rebooting, and i had to recover it by flashing the firmware again, but now magisk no longer works. Whenever i install it, boot will hang. Without magisk it can boot, but then i don't have root.
It seems i couldn't uninstall Magisk cleanly, so the problematic module remained there. The magisk uninstaller zip failed at twrp, which i suspect it is because it cannot access some data as twrp does not support decryption.
now i have no idea how to fix this. appreciate any suggestions!
Sent from my F5321 using XDA Free mobile app
dohanin said:
hi, i had successully upgraded my x compact to oreo, installed twrp 3.2.1 (without encrytion support) and rooted with magisk. Everything has been working fine until i messed up magisk with some module (busybox).
My phone hanged at Xperia logo after rebooting, and i had to recover it by flashing the firmware again, but now magisk no longer works. Whenever i install it, boot will hang. Without magisk it can boot, but then i don't have root.
It seems i couldn't uninstall Magisk cleanly, so the problematic module remained there. The magisk uninstaller zip failed at twrp, which i suspect it is because it cannot access some data as twrp does not support decryption.
now i have no idea how to fix this. appreciate any suggestions!
Sent from my F5321 using XDA Free mobile app
Click to expand...
Click to collapse
You can always do a clean install, right?
Time consuming but you'll get your phone back, with Magisk, and have to wait for a fully working TWRP (like many of us X Compact owners, I think).
yes, but wiping everything would cost me a lot of time, and should be the last resort. i didn't even wipe /data when upgrading from nougat to oreo. i was hoping someone can teach me how to remove the problematic magisk module, like using adb or whatever.
just an update... my issue is fixed. Some expert in the Magisk forum suggested me to place a file with name ".disable_magisk" in /cache to disable the modules, and it worked.
dohanin said:
just an update... my issue is fixed. Some expert in the Magisk forum suggested me to place a file with name ".disable_magisk" in /cache to disable the modules, and it worked.
Click to expand...
Click to collapse
I was gonna say that you can disable the module by erasing a cache file, via adb, but here you go.
Pretty straight forward for those of us who like a nice clean flash. Not you dirty dogs.
1 clean flash lastest Android 10 factory image and install
2 setup the device don't set a password or pin
Install latest canary Magisk manager
3 pull the boot.img out of the Factory image zip.
4 move the boot image to phone internal storage
Patch boot.img with Magisk.
5 download latest twrp.img and fastboot boot it
Install the patches boot.img to your boot
Mount opposite partition if A then mount b, if b mount a
Ignore the error.
And repeat flashing patched boot.img like you did the first time
Mount original partition reboot. And boom
So installing the magisk canary build via zip in TWRP does not work?
---------- Post added at 04:07 PM ---------- Previous post was at 04:05 PM ----------
Also, did you use .019 or .020 build from the factory image website?
ne0ns4l4m4nder said:
Pretty straight forward for those of us who like a nice clean flash. Not you dirty dogs.
1 clean flash lastest Android 10 factory image and install
2 setup the device don't set a password or pin
Install latest canary Magisk manager
3 pull the boot.img out of the Factory image zip.
4 move the boot image to phone internal storage
Patch boot.img with Magisk.
5 download latest twrp.img and fastboot boot it
Install the patches boot.img to your boot
Mount opposite partition if A then mount b, if b mount a
Ignore the error.
And repeat flashing patched boot.img like you did the first time
Mount original partition reboot. And boom
Click to expand...
Click to collapse
Is patching the boot.img in magisk mentioned in step 4 an option in magisk? How do I "patch" the boot image?
How do I do this portion of step 5?:
Install the patches boot.img to your boot
Mount opposite partition if A then mount b, if b mount a
Does magisk store the patched boot image somewhere (and it tells you where) that is accessible in TWRP? then we need only go to that file path in TWRP under the "install" tab?
What does this mean?:
And repeat flashing patched boot.img like you did the first time
Do you mean on the partition you were originally on?
So if we're on A, mount B, install the patched boot image on A, remount A, install the patched boot image on B, and then reboot?
How do we "install to th boot?"
I used the .20 from the factory. And Magisk saves the patches boot.img for me in downloads, which I can access in twro
Good instructions but you don't even need TWRP if you want to save time. I just patched the boot.img with the Canary. 20 Magisk build and moved it over to my pc so that I could just flash it using the fastboot flash boot boot.img command. Worked like a champ and did not have to disable my security pin and jack with mounting A or B with TWRP.
I just flashed .20
Booted it once.
Then using fastboot I booted twrp, installed magisk 19.3
and Im rooted.
?* lol w.e works ?
Which magisk modules are workings?
tweaked said:
I just flashed .20
Booted it once.
Then using fastboot I booted twrp, installed magisk 19.3
and Im rooted.
Click to expand...
Click to collapse
Clean or dirty flash of A10?
I just flashed the canary magisk zip (from a booted/not installed TWRP) and it was fine... I didn't go through any extra steps.
hmm so now i have root following these instructions, but i cant seem to do much with it.. i cant seem to make system rw. cant edit build.prop to enable tether, cant edit host files for adaway. those are the two reasons i root, and neither seem to work.
edit: got adaway to work, needed to enable systemless hosts in magisk settings, reboot, then adaway works.
phyl0x said:
hmm so now i have root following these instructions, but i cant seem to do much with it.. i cant seem to make system rw. cant edit build.prop to enable tether, cant edit host files for adaway. those are the two reasons i root, and neither seem to work.
edit: got adaway to work, needed to enable systemless hosts in magisk settings, reboot, then adaway works.
Click to expand...
Click to collapse
I just flashed the factory image without the -W let it boot. Rebooted back to fastboot, booted Twrp, Flashed Twrp, Flashed magisk 19.3. All modules are working including Adaway except for the active edge mod.
dmarden said:
I just flashed the canary magisk zip (from a booted/not installed TWRP) and it was fine... I didn't go through any extra steps.
Click to expand...
Click to collapse
Which Canary please?
humdrum2009 said:
Which Canary please?
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
tweaked said:
I just flashed .20
Booted it once.
Then using fastboot I booted twrp, installed magisk 19.3
and Im rooted.
Click to expand...
Click to collapse
Did the same coming from 9.
What was new for me was the android 'no command' screen; power+volume-up -> menu .
Also had to reinstall Magisk in the manager (19.3), even as it was already installed, to get AdAway (systemless) to be able to alter the hosts.
Adb recognizes my phone and I manage to restart bootloader, but when I try to boot TWRP img it says "waiting for a device.."
What is wrong?
phyl0x said:
hmm so now i have root following these instructions, but i cant seem to do much with it.. i cant seem to make system rw. cant edit build.prop to enable tether, cant edit host files for adaway. those are the two reasons i root, and neither seem to work.
edit: got adaway to work, needed to enable systemless hosts in magisk settings, reboot, then adaway works.
Click to expand...
Click to collapse
I got tethering working (Verizon grandfathered unlimited plan)
1. Magisk -> Downloads -> MagiskHide Props Config
2. Magisk -> Downloads -> BusyBox
3. Reboot
4. Adb shell -> type ‘props'
5. Select ‘5’ -> ’net.tethering.noprovisioning’ -> y -> y
6. Wait for reboot
7. Adb shell -> settings put global tether_dun_required 0
8. Reboot
Adaway and tethering are my only reasons to be rooted as well. Glad both are working now on 10.
barski said:
I got tethering working (Verizon grandfathered unlimited plan)
1. Magisk -> Downloads -> MagiskHide Props Config
2. Magisk -> Downloads -> BusyBox
3. Reboot
4. Adb shell -> type ‘props'
5. Select ‘5’ -> ’net.tethering.noprovisioning’ -> y -> y
6. Wait for reboot
7. Adb shell -> settings put global tether_dun_required 0
8. Reboot
Adaway and tethering are my only reasons to be rooted as well. Glad both are working now on 10.
Click to expand...
Click to collapse
Awesome, yeah I am in the exact same boat as you, thanks for sharing that I will probably take the plunge and root as well. Which magisk version and twrp versions you use?
What kernel if any?
I'm running 10 now with root, I just flashed the latest canary build in twrp, didn't need to modify anything else. I do have a question though, has anybody been able to load up Titanium Backup? It just keeps crashing for me.
murphyjasonc said:
I just flashed the factory image without the -W let it boot. Rebooted back to fastboot, booted Twrp, Flashed Twrp, Flashed magisk 19.3. All modules are working including Adaway except for the active edge mod.
Click to expand...
Click to collapse
This is the way i usually root my device as well.
Flash a fresh rom
fastboot boot twrp.img
flash twrp.zip in twrp, reboot recovery
flash magisk.zip in twrp
reboot.
However after i flashed twrp then rebooted into it, the touch screen wouldn't work. I had to hold power + vol down to reboot into fastboot then i did the boot into twrp.img again and then i flashed magisk from there.
I have no idea why the flashed twrp is not working with the touchscreen. The twrp img and the twrp zip that i used were version 3.3.0-0 and magisk was 19.3.
In Magisk manager it says it is installed properly and that safety net check passes.