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
Magisk show I have root, and it is installed correctly. I wiped system and reinstalled, still no app shoes I have root. The bootloader shows it is unlocked and TWRP works, but ever application says root is not installed, tried to install magisk manually from TWRP, no issues, but still all apps say I do not have root. What can be done, I can not afford to not backup, so a clean re-install is an issue since Ti-Backup does not show root access.
I would assume manually flashing magisk would fix any issue as would wiping and re-installing system, but neither resolved the lack of root issue. This is on RR Remix so it is rooted by default.
Please help,
ERIC
Did you make sure Root is checked in the Developer options?
Found the solution, with magisk there is a settings option to enable root for Apps or just ADB or both, somehow it got switched to ADB only.
ERIC
After updating to the latest software I found that with the exception of the first time I tried it which weirdly enough worked, I can't for the life of me successfully boot after rooting.
I rooted once and had to uninstall magisk because of a conflicting module but now no matter what I try I always get stuck on essential's splash screen.
Does anyone else have this problem? If I flash the stock boot image I can boot just fine.
have you try flashing update, then boot image then magisk consecutively before any reboot? I'm out of the country at the moment w/o access to my PC, and I can't even risk a soft brick while traveling.
Are you getting as far as installing magisk again? cause from what you've written it sounds like it is working but the module that caused the original issue is still there. you can remove magisk by flashing the stock boot image but the magisk image with all installed modules is still there.
If that is the case then there are a few tool out there to mount the magisk image and remove the module.
I tried a few when I had a similar issue and the only one that worked was this one.
https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
what you would need to do is flash twrp. boot into recovery. (decryption never works for me so would recomend either sideload or adb push to /data/media)
flash the stock boot image back.
then reinstall magisk
flash the magisk recovery manager
once loaded go to the advanced section of twrp select terminal and type mm and follow the on screen instruction to remove the afflicted module then reboot and you should be sorted.
Although that being said if that isn't the issue you're having then can you explain how far you get with trying to reinstall and whats going wrong.
Ibanez33 said:
Are you getting as far as installing magisk again? cause from what you've written it sounds like it is working but the module that caused the original issue is still there. you can remove magisk by flashing the stock boot image but the magisk image with all installed modules is still there.
If that is the case then there are a few tool out there to mount the magisk image and remove the module.
I tried a few when I had a similar issue and the only one that worked was this one.
https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
what you would need to do is flash twrp. boot into recovery. (decryption never works for me so would recomend either sideload or adb push to /data/media)
flash the stock boot image back.
then reinstall magisk
flash the magisk recovery manager
once loaded go to the advanced section of twrp select terminal and type mm and follow the on screen instruction to remove the afflicted module then reboot and you should be sorted.
Although that being said if that isn't the issue you're having then can you explain how far you get with trying to reinstall and whats going wrong.
Click to expand...
Click to collapse
I can't believe I hadn't thought of that. The conflicting modules were still there and I just had to remove them. Thanks so much man, I was about to wipe my phone out of frustration!
hey all!
I'm a newb....
I have a rooted 6p with the factory image installed, twrp recovery.
I don't recall doing a backup before rooting.....yeah I know not smart....didn't know what the heck I was doing in this process....never rooted a phone.
I installed Magisk......then in my infinite wisdom installed supersu
the phone for the most part works fine, but I am having a problem running frida, it complains about magisk hide. I have removed all the magisk modules...
I am hoping I can some how clean up this phone and completely remove magisk.....and get frida running.
am I toast without a backup?
what is the best way to completely remove and uninstall magisk.
tried to run magisk install again and also magisk uninstall gives me error 1, which I see there are videos for dealing with on youtube...though haven't gone done that rabbit hole
I am quite comfortable using adb
I see bits of magisk all through the file system, just not sure if I should be deleting as I might be getting myself into more trouble.
TIA
Well if you don't mind starting fresh (backing up all your data) as this would erase everything and set your phone back to "factory stock" on the latest official version from google and its as easy as clicking one batch file to get things sorted. You may have messed up some stuff permanently on your system partition by installing/uninstalling two incompatible root solutions etc.
Link: https://developers.google.com/android/images#angler
Direct link to latest file: https://dl.google.com/dl/android/aosp/angler-opm7.181205.001-factory-b75ce068.zip
Then you just plug your phone in and run the 'flash-all.bat' file.
What I need to do to upgrade and root version 11.1.1.1, I'm currently on a 9.0.16 rooted twrp magisk
Wheres the download link for the full OOS 11.1.1.1.1.1.1? Does OTA mean the full stock rom download or zip file just for update????
The way I did it from 10.3.8 and 10.3.12:
1) Boot into TWRP
2) Flash latest TWRP (twrp-installer-3.5.2_9-0-fajita.zip from official TWRP site) and Reboot to recovery
3) Flash the full OOS11 zip file. It will flash one of the two A/B slots - DO NOT YET REBOOT!!!
4) Directly after flashing the OOS11 zip flash twrp-installer-3.5.2_9-0-fajita.zip again
5) Reboot into recovery
6) Flash OOS11 zip again into the other slot - Again: DO NOT YET REBOOT!!!
7) Flash twrp-installer-3.5.2_9-0-fajita.zip again
8) Flash Magisk-v23.zip
9) Reboot
Looks more complicated than it really is. You just have to do everything twice to flash both slots. At least that's how I did it a couple of times and it worked without any issues.
!!!You could also Flash directly from the updater app without rebooting. Go into Magisk and install twrp A/B retention script and reinstall Magisk. I never did it that way because I always made a Nandroid backup before flashing everything.!!! See edit comment!!
Hope that helps.
Edit: I just read in another thread the Magisk route (A/B retentio...) leads to a Qualcomm Crashdump which needs unbricking via the MsmDownloadTool!!!
@ptuner: I usually go tp Settings -> System -> System Updates. Don't install, just but put the phone aside for some time. It will download the full zip into Internal memory/.Ota.
You download the full zip from any of the places you find via your search engine of choice.
MrBrainstorm said:
The way I did it from 10.3.8 and 10.3.12:
1) Boot into TWRP
2) Flash latest TWRP (twrp-installer-3.5.2_9-0-fajita.zip from official TWRP site)
3) Flash the full OOS11 zip file. It ill flash one of the two A/B slots - DO NOT YET REBOOT!!!
4) Directly after flashing the OOS11 zip flash twrp-installer-3.5.2_9-0-fajita.zip again
5) Reboot into recovery
6) Flash OOS11 zip again into the other slot - Again: DO NOT YET REBOOT!!!
7) Flash twrp-installer-3.5.2_9-0-fajita.zip again
8) Flash Magisk-v23.zip
9) Reboot
Looks more complicated than it really is. You just have to do everything twice to flash both slots. At least that's how I did it a couple of times and it worked without any issues.
!!!You could also Flash directly from the updater app without rebooting. Go into Magisk and install twrp A/B retention script and reinstall Magisk. I never did it that way because I always made a Nandroid backup before flashing everything.!!! See edit comment!!
Hope that helps.
Edit: I just read in another thread the Magisk route (A/B retentio...) leads to a Qualcomm Crashdump which needs unbricking via the MsmDownloadTool!!!
@ptuner: I usually go tp Settings -> System -> System Updates. Don't install, just but put the phone aside for some time. It will download the full zip into Internal memory/.Ota.
You download the full zip from any of the places you find via your search engine of choice.
Click to expand...
Click to collapse
all data is deleted yes?
ELAD098 said:
all data is deleted yes?
Click to expand...
Click to collapse
No, if you upgrade via TWRP as I described your data will NOT be wiped. But I always advice to make a full backup (nandroid and internal storage) before flashing anything!!
Are you satisfied by 11.1.1.1 generally ?
I was on 11 and rollback to 10 cuz battery issues. Can anyone give some info, are you satisfied with 11.1.1.1 ?
I am only using since last Wednesday but so far I am happy with it. The battery usage is identical to 10.3.12 with 0.7%/h (according to AccuBattery). Screen usage is probably the same. Can't really tell as I am not a heavy user.
Unfortunately I tried to install and got a brick
i can unlocked bootloader on 11.1.1.1
now i on 10.3.8 lock bootloader
i want to upgrade
I bricked mine too and used MSM tool to get to android 9, I installed TWRP 3.3.1-31 (pie version) and last version of Magisk, after that, I wiped all but internal storage, download OOS 11.1.1.1.1.1..1 and flashed with TWRP, done after like 5 min, I clean Dalvik cache and flash the same TWRP (3.3.1-31 pie version) + Magisk 23
Booted the system and noticed that Magisk wasn't installed so I got back to recovery, flashed once again Magisk and all Good until I fok up again in the future.
Messing around with rooted oos 11 only for 1 day so far and I already noticed the battery drain on this system is more (agressive)
I used adb to shut off the update notification posted by Sachin09.
Adb devices (for checking device is connected)
Adb shell
pm uninstall -k --user 0 com.oneplus.opbackup
exit
I have issues with phone after though. Phone says not online WiFi but I can watch youtube but I cannot open or view any attachments in gmail. I had Hotpot on when I ran the adb script. I'm wondering if that was a problem.
Question: If I repeat the adb script but swap install for uninstall, will it revert to normal? Any suggestions? I'm still on 10.3.12 and happy with it.
Jim44 said:
I used adb to shut off the update notification posted by Sachin09.
Adb devices (for checking device is connected)
Adb shell
pm uninstall -k --user 0 com.oneplus.opbackup
exit
I have issues with phone after though. Phone says not online WiFi but I can watch youtube but I cannot open or view any attachments in gmail. I had Hotpot on when I ran the adb script. I'm wondering if that was a problem.
Question: If I repeat the adb script but swap install for uninstall, will it revert to normal? Any suggestions? I'm still on 10.3.12 and happy with it.
Click to expand...
Click to collapse
Try to do a local update with full zip file. Maybe it help.
edited: try thiis command and see if it work
Code:
1. adb shell
2. cmd package install-existing com.oneplus.opbackup
3. exit
After that restart the phone.
Thank you! That worked. I'm back with the unwanted OS 11 update again.
I tried the "pm -k uninstall..." again which removed the update but the wifi and gmail issues returned.
I fixed it though. I rooted my 1+6T long ago. I have the TWRP and MAGISK zip files in root.
I booted into recovery, uninstalled Magisk with the uninstaller zip, installed TWRP..zip then installed Magisk..zip. I rebooted and now everything works.
I tested out OS 11.1.1.1.1 on my buddy's phone and I don't want that OS. Thank again for the help I needed. Jim44