Database Users

[Q] Magisk Root

Has anyone been able to get magisk to work appropriately? I attempted and the magisk apk kept fc'ing. I read about LG devices needing a boot.img "bump". Is this true or has anyone got it working in their own way?

There Is no root method for variants that don't have a unlocked bootloader. You would know this if you read the forums before asking
Sent from my VS995 using Tapatalk

mrtruckincowboy said:
There Is no root method for variants that don't have a unlocked bootloader. You would know this if you read the forums before asking
Click to expand...
Click to collapse
So, quite frankly, if you read, another user has it working. Further more, with the TMO variant, I do have an unlocked bootloader. Root application works with magisk, however the APK itself fc's.

I thought cowboys were polite ; )

I misread your post thought you were the typical person asking for a update on root I apologize.
Sent from my VS995 using Tapatalk

Thats what you get for not reading posts Cowboy... Smh...

I have the H918/tmo and I was able to get magisk running with phh's superuser. I'm kinda iffy on magisk-hide, as i had issues with it initially ( random reboots with it enabled). I turned off magisk hide for about a week, then turned it back on last night with no reboots since.. but haven't tested it with apps.
After running the easy recowvery + root script, i got rid of SuperSU. I believe all i did was a Full Unroot in the options, with no changes to the recovery. (I also may have done a format /data when rebooting to recovery again, but i dont recall fully, so take that into consideration if it didnt work at first (followed by the no-verity-opt-encrypt zip).)
After getting rid of SuperSU/su binary, what i remember doing was:
1 ) Flash magisk v9.zip -> reboot to system to make sure it boots, then adb reboot recovery.
2 ) Flash phh's superuser r266-2.zip -> reboot to system
3 ) install magisk manager via apk, and phh's superuser via playstore.
4 ) test out root.

has anyone been able to get Phh's superuser to work on the Sprint v20 / LS997 ?? If so, how? Thanks in advance.

If you can't get this working there is an app called RootSwitch. It can successfully hide root on the V20 with a toggle.

HiddenKnight said:
Has anyone been able to get magisk to work appropriately? I attempted and the magisk apk kept fc'ing. I read about LG devices needing a boot.img "bump". Is this true or has anyone got it working in their own way?
Click to expand...
Click to collapse
ive got 1 working and 1 in testing that uses magisk and phh.
the phh superuser seems to be casusing the systemui to force close often when in hide mode and the random reboots and loss of service, otherwise it was working fine.
but yeah, just flash version 10.2 on your current rom and see what happens!
btw this was on DEC sec patch, on oct builds i never tried it, but this is latest DEC sofware, didnt even use rootswitch

slayerh4x said:
If you can't get this working there is an app called RootSwitch. It can successfully hide root on the V20 with a toggle.
Click to expand...
Click to collapse
Is this the App you used?
https://forum.xda-developers.com/android/apps-games/play-pokemon-root-switch-method-patched-t3483179

remix435 said:
Is this the App you used?
https://forum.xda-developers.com/android/apps-games/play-pokemon-root-switch-method-patched-t3483179
Click to expand...
Click to collapse
I am using the one from this rom thread;
https://forum.xda-developers.com/v20/development/h819-nrd90m-modded-stock-rom-t3503658
Just follow the directions in the OP and you'll be g2g.

slayerh4x said:
If you can't get this working there is an app called RootSwitch. It can successfully hide root on the V20 with a toggle.
Click to expand...
Click to collapse
Tried RootSwitch w/ SuperSU. Didn't pass SafetyNet if that's what you were referring to.
Tried it again last night. Had the 1st 3 options turned on. Soon as I opened Android Pay my phone hot booted and got stuck on the VZW splash screen. Had to pull the battery. Won't try that again with supersu.

I have a VS995 this is how I got my phone to finally take magisk and pass the safetynet check. I'm running software version VS99513A I performed dirty santa to get unlocked bootloader and root access. Now I tried to uninstall supersu threw the app and I got a failed message. I tried going into recovery and flashing the supersu unistaller and that would fail. I tried flash magisk v12.0 and keep getting error message. I got stock in twrp recovery several times and used LGUP and flash either VS99512A KDZ or the VS99513A KDZ. Am not a developer but it seemed as if the boot.img won't take by the magisk zip. Those where my failed attempts for about a week or two. Now on to the success story
Performed Dirty Santa on software version VS99513A. I decide to flash modstock kernaI update v1.1 because it seem to work well with a stock rooted VS995. I flashed busy box in recovery and downloaded the app and also downloaded quick reboot so I could reboot into recovery easier. After reading @poixninja thread on modstock kernal - stocked with goodies he mention flash a boot.img that was patched with magisk. So I but the phone into fastboot mode and flashed his boot.img onto the phone with cmd (command prompt). I think I might have tried to uninstall supersu threw the app and I think it didn't work after flash the boot.img. So I put the phone into recovery mode the to wipe and then to advance wipe and clear dalvik and cache. After that I went to install and flashed the supersu unistaller and it took. After flashing I wipe the cache that twrp ask after most flashes. I then rebooted into recovery to make sure my twrp was not affected because I had and issue with that in previous supersu unistaller attempts. Rebooted ito twrp recovery then rebooted into system. I think whenever I flashed the verzion logo stayed up longer than normal but the phone fully started up. I clicked on supersu and it said no root access. Turned of the phone and did the steps to get to recovery mode. Once in I first wiped dalvik and cache. Then I flashed magisk unistaller and it went threw with no issue. I wiped dalvik and cache then rebooted into recovery. After getting into recovery I rebooted to system.
Sidenote: I recommend after wiping supersu and flashing magisk unistaller. Once you boot up install magisk apk. I didn't install the apk until after I flashed the magisk v12.0 in recovery. I noticed when I reboot the magisk icon was on the phone but when I clicked it it said go to playstore to download. I had the magisk manager apk on my SD card so I just installed it. The install to longer than normal I think it was because I didn't install it prior to flash the zip in recovery. I didn't get a chance to verify it yet.
Once the phone boot and I installed the magisk app manager I open it up and got green checks for installed magisk v12 and properly rooted. I went to setting and turned on enable busy box, magisk hide, and systemless. But when I clicked safetynet I got cts mismatch. Did some research and read on other XDA magisk thread that it maybe because of custom roms, modified kernals and possible supersu somewhere on the system. The only root accessible apps I had installed during this process was busybox and quick reboot. I did notice the first time I ran quick reboot after getting magisk it did give it root access then it did after I opened it again.
I decide to uninstall quick reboot and busy box. I uninstalled both apps. I rebooted into recovery mode the manual way. First thing I did was wipe dalvik and cache. Then I flashed busy box uninstaller. When the flash was running I say in the command lines that it found supersu. Which I thought was odd so I also flashed supersu unistaller. I rebooted into recovery wipe dalvik and cache and flashed uninstall magisk. Then reboot into recovery. I ran busy box uninstaller one more time to see if it would pick up supersu again and the command lines did not mention it. I flashed back magisk v12.0 rebooted into recovery. Then rebooted into system
Opened magisk went to setting to turn on enable busy box, magisk hide and systemless. Check safetnet and failed I found a magisk XDA thread that talks about common issue. It said I had to check magisk core only mode. Once I did that he requested a reboot which I did. Once back up I first cleared in app manager under show system I cleared all data for google play store, google play service for instant app, google play services. I opened magisk clicked safetynet check and I passed it. I went to search for netflix in play store and it pop up I installed it and it working fine so far. I tried logging into snapchat and I got threw.
Hope this maybe help full to anyone having issues
https://forum.xda-developers.com/v20/development/kernel-modstock-kernel-stock-goodies-t3563887 (boot img and modstock v1.1)
https://forum.xda-developers.com/showpost.php?p=71154562&postcount=4 (Magisk common issues)

Easier than that...?
sentra10550 said:
I have a VS995 this is how I got my phone to finally take magisk and pass the safetynet check. I'm running software version VS99513A I performed dirty santa to get unlocked bootloader and root access...
...
...Hope this maybe help full to anyone having issues
Click to expand...
Click to collapse
If I may be so bold, I played around with the rooting process on mine (I have a VS995 on 13A, too), and found a much easier (and possibly cleaner?) way to do this. Of course, the way I'm about to suggest would require a full KDZ to stock and a factory reset...
Here's mine:
Follow this thread:
https://forum.xda-developers.com/v20/how-to/lgv20-vs995-verizon-aio-post-06-19-2017-t3624326
Note: For noobs: After step 13, it's a bit misleading, because it doesn't boot DIRECTLY into TWRP, but boots to the white-screen "stock" recovery. The trick is to tell it "Yes" to both reset prompts. (It doesn't actually reset your stuff.) After this, it will take you to the TWRP menu.
When you get to step 14E, DO NOT FLASH SuperSU!
Instead, flash the ReStock zip.
After flashing ReStock, follow step 14G, and then flash Magisk 13.3 (latest stable, haven't tested others) from here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I tried this out of order a couple of other times and ended up either having Magisk not following through with install, or developing issues installing certain apps. (Either getting a -504 error from Play Store, or having valid APKs reply that they were "corrupt" when directly installing.)
Of course, all of the stereotypical disclaimers apply-- YMMV, and I'm not responsible if you brick your device, yadda yadda...
No offense, intended, sentra10550. While I'm glad you managed to get things working, the directions were a bit convoluted and I hope my humble findings might help yourself, in the future(?), and any others that may have a VS995.
Good luck, everybody!
)O( NeoHiPPy )O(

Think I'll wait until an easier method comes out for the VS995 to run Magisk lol..

I was UNABLE to do full unroot on my V20 from SuperSu settings menu. It would say "uninstallation failed"
I tried running UPDATE-unSU.zip from TWRP and it did not help. Magisk keeps on complaining about modified boot file.
I am unlocking boot loader, trying to flash Magisk in TWRP instead of SuperSu as per DirtyStanta root method instructions.
I will also flash restock 1.3 right after to stop static and vibration issue.
If it works, ill update my post.
---------- Post added 21st February 2018 at 12:28 AM ---------- Previous post was 20th February 2018 at 11:48 PM ----------
Ok i got it working. It was easier then i thought it would be.
These are the steps i did the very first time i got into TWRP after bootloaded unlock process as per DirtySanta rooting instructions.
Entered TWRP
DID NOT format data>yes
Installed Restock1.3 and Magisk.zip
Wipe cache and dalvik. Says Failed to wipe Dalvik (dont know why but what ever)
Reboot.
Result: Asking for unlock password 9 attempts left. So i have to Format Data>Yes
Re-entered TWRP
Format Data>yes
Reboot.
Root works. No SuperSu needed.
Conclusion:
You have to format DATA not for the root to work, but to be able to get into the phone. If there was a way to bypass that, there would be no need to factory reset to root. Root method would not require you to wipe the phone.
How ever, some apps that i use still do not support systemless root. They fail to do their work such as removing system apps. I cant remove any of my system apps for some reasons. I get "failed" messageevery time.
I was told i need modules for Magisk, but i have yet understood what that even means.
Other apps that use root, work fine. Such as AdAway.org

Help with installing Magisk on Verizon Samsung Galaxy Note 3 SM-N900V

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.

Lost root access and can't get it back via Magisk. Help!

Galaxy S8 Exynos [SM-G950FD] Android Oreo 8.0.0
Hello. it's my first time posting here. So I've had a successful attempt at flashing TWRP and Magisk into my phone. Today I accidentally plugged in my charger while it was in the process of rebooting, so it entered my device into kind of a bootloop. I solved this by going into Download Mode and pressing 'Cancel', which prompted my device to successfully reboot and work again.
The problem is that I've somehow lost my root. None of my apps can get root access, CPU-Z says no root available, and Magisk Manager said "Magisk is not installed". Idk how I got to this because yesterday all was working, I assume it's because I got a bootloop or went into Download Mode.
I tried to install the official Magisk ZIP file from the Manager, go into recovery mode, and flash it via TWRP. Unfortunately this didn't work. This is the only solution I can come up with besides reflashing Stock and having to flash Magisk again and wipe all my current data. If anyone has any suggestions please comment down below as I'm kinda stuck rn. They would be greatly appreaciated!

Stuck on "Downloading..." loop after Magisk Update from the Magisk Manager -RESOLVED

As the title describes, I did the probably not so smart and I tried updating Magisk from within the Magisk Manager and now I cant get out of the loop of it returning to "Downloading...".
I was using Magisk Manager 21.4 and when I tried running the uninstall Magisk zip file within TWRP, it fails cause of something in accordance to the SD card (probably where its running from) or something.
Edit: I figured it out, it does not recognize the contents of the zip files as a bootable image anymore
Now im not sure how im suppose to follow the guide from here: https://magiskmanager.com/uninstall-magisk
Do any of you have a suggestion that does require me to completely re-root my phone?

Im not sure how to remove this thread, but the issue is resolved and I probably posted it in the wrong forum place any way.

How did you resolve the problem. I'm having the same issue right now. Did you simply uninstall Magisk?

Hi @onurdz I faced the same. I solved it by removing the App, rebooting, installing the App v8.0.3 , updating the App to v22.1, and then the option to update Magisk appeared.

Thanks a lot for posting it here! I came here looking for solution for the same, without even realizing it might be caused by Magisk - update and reboot happened a good while apart.
I tried looking but couldn't find - is it a known issue with magisk, and is there a fix (in work) to solve it without removing or rolling back magisk?

Now I'm confused.
My phone wouldn't start. It's either "downloading", or TWRP.
I'm trying to uninstall magisk, by downloading the app, renaming it into uninstall.zip and installing in twrp.
It fails with an error. Not sure it's same, it says to me "unsupported/unknown image format"

AntonGut said:
Now I'm confused.
My phone wouldn't start. It's either "downloading", or TWRP.
I'm trying to uninstall magisk, by downloading the app, renaming it into uninstall.zip and installing in twrp.
It fails with an error. Not sure it's same, it says to me "unsupported/unknown image format"
Click to expand...
Click to collapse
Hi...
first...there is a Magisk Zip file you can use to uninstall with TWRP.
sec...you can flash the Stock Boot.img into boot partion
third...you can recover boot image from a backup
yeah im sure that every option will bring success
solong
speedson
to unbrick a samsung just download the Stock firmware by using Frija tool and start the into download-mode
then use Odin3 to flash the stock rom and restart into System...thats all
solong
speedson

No certification of play protect

Dear comunity,
I really need your help with this. I have a OP6T and finally updated to the android 11. Before the update, I removed magisk (it was giving me some errors from time to time and I wasn't using the root for anything) through TWRP and then I just updated to the latest OOS through OTA. Everything went smoothly until today, when I went to a store and tried to pay using google pay an error appeared and it seems I have no longer the device certified by the play protect.
What did I miss during the update? Is there any workaround?
Thank you in advance!

I would try wiping and installing the latest oos through twrp instead of ota

I just did this to have everything stock again. Since I installed via OTA, didn't I loose the twrp recovery? Wiping are you referring to a complete clean install? I'm not quite prepared for that :|

igoigo said:
I just did this to have everything stock again. Since I installed via OTA, didn't I loose the twrp recovery? Wiping are you referring to a complete clean install? I'm not quite prepared for that :|
Click to expand...
Click to collapse
I don't understand why it would not be certified after ota update. You can try uninstalling updates for play services and play store maybe that will help. Or there might be magisk files that persisted. Could try to root with magisk again and uninstall it using the magisk app. Just ideas for ya cause I really don't know for sure. But I do know for sure even with stock oos you can still boot a twrp and use it even if you dont make it permanent. So you could use twrp to delete magisk or anything that would be throwing off the safety net. Could also try a safety net checking app to narrow down the problem depending if it passes or not. I just suggested clean install because there may be conflicting device names or whatever from going from custom to ota update. Hope it helps

Brettroth said:
I don't understand why it would not be certified after ota update. You can try uninstalling updates for play services and play store maybe that will help. Or there might be magisk files that persisted. Could try to root with magisk again and uninstall it using the magisk app. Just ideas for ya cause I really don't know for sure. But I do know for sure even with stock oos you can still boot a twrp and use it even if you dont make it permanent. So you could use twrp to delete magisk or anything that would be throwing off the safety net. Could also try a safety net checking app to narrow down the problem depending if it passes or not. I just suggested clean install because there may be conflicting device names or whatever from going from custom to ota update. Hope it helps
Click to expand...
Click to collapse
Thank you for the suggestions. I installed root checker and it didn't detect any root. I was thinking on installing again TWRP to then install/uninstall magisk. But I can try to check the safety net, its strange indeed, I have everything working without any problems, even the google or bank apps.
When I uninstalled magisk I had to do it through TWRP because my magisk manager that was in "hide mode" woulnd't open because it was constantly crashing. As you said, probably there is some remnant files from magisk left.
EDIT: I run the safety checker and it found a problem with "CTS profile matched", any idea what is this?

igoigo said:
Thank you for the suggestions. I installed root checker and it didn't detect any root. I was thinking on installing again TWRP to then install/uninstall magisk. But I can try to check the safety net, its strange indeed, I have everything working without any problems, even the google or bank apps.
When I uninstalled magisk I had to do it through TWRP because my magisk manager that was in "hide mode" woulnd't open because it was constantly crashing. As you said, probably there is some remnant files from magisk left.
EDIT: I run the safety checker and it found a problem with "CTS profile matched", any idea what is this?
Click to expand...
Click to collapse
Basically has 2 different ID's probably from going custom to ota update. That's why I suggested clean install. Anytime going from one rom to another clean install is needed.

@Brettroth the thing is, I was/am in the stock rom, the only thing I had "custom" was the magisk (which I uninstalled before update) and TWRP recovery :|

igoigo said:
@Brettroth the thing is, I was/am in the stock rom, the only thing I had "custom" was the magisk (which I uninstalled before update) and TWRP recovery :|
Click to expand...
Click to collapse
Sorry I thought you were on custom

igoigo said:
@Brettroth the thing is, I was/am in the stock rom, the only thing I had "custom" was the magisk (which I uninstalled before update) and TWRP recovery :
Click to expand...
Click to collapse
You should be able to just dirty flash the oos from twrp then. Should fix any mismatched id's

I will try the dirty flash through twrp

Brettroth said:
You should be able to just dirty flash the oos from twrp then. Should fix any mismatched id's
Click to expand...
Click to collapse
Finally got some time during my holidays to try this, but now I'm facing some problems. I tried to fastboot flash the TWRP version that you suggested in another thread but the recovery can't read my storage due to encryption. Do you have any suggestion?

igoigo said:
Finally got some time during my holidays to try this, but now I'm facing some problems. I tried to fastboot flash the TWRP version that you suggested in another thread but the recovery can't read my storage due to encryption. Do you have any suggestion?
Click to expand...
Click to collapse
This will decrypt android 12

Brettroth said:
This will decrypt android 12
Click to expand...
Click to collapse
But I'm with in Android 11 stock ROM (11.1.2.2) will it work?

igoigo said:
But I'm with in Android 11 stock ROM (11.1.2.2) will it work?
Click to expand...
Click to collapse
Yeah it should. The other twrp should have worked also with a11. You might have corrupted your data. Probably need to wipe data by typing yes to fix.

How can I have corrupted my data by just flashing the recovery? Can't I flash the stock boot.img?
EDIT:
I was able to flash the stock boot.img and everything is working now. Starting again, what do you suggest, boot TWRP and then instal zip and flash OOS+TWRP? My problem is, which TWRP version should I boot and flash, since the one I tested gave this problem.

Hi, my case is a bit different as i havent used magisk and i have a difderent phone, but my solution to "device is not play store certified" which was showing in play store, about section was as follows:
Enable Developper mode (setting/about/software info/click 7 times or so on "build number")
A developer menu appears in settings at the bottom, within it i disabled "OEM Unlocking".
Restarted phone checked, was still not certified, cleared data for "google play services" and "google play store", restarted, and voila.
Hope it helps