Hey all,
After my rooting experience with marshmallow, I used that with 7.1.1 and have had no issues. MODS: This was my approach to rooting 7.1.1. I apologize in advance for creating this thread if it's not necessary yet since XDA has given me so much help, I'm returning the favor.
NOTE: for those that want to roast me on this thread and/or flame me, don't do it. We are all noobs at one point or another. I have provided no links but have supplied the filename to the best in my capacity.
XDA gang,
After numerous attempts to root nougat, I tried this approach. This was the same approach I took w/ marshmallow.
I used Odin3_v3.12.3
selected 7.1.1 – look for filename j700tuvu3bqi5 NOTE: uncheck auto reboot. I do\did because in my experience, I encountered a boot loop.
after odin processes the flash, I disconnected the usb cable and did a battery pull.
Boot up your phone and let your phone build the recovery. After your phone reboots after the recovery, do a battery pull when the samsung splash screen starts to display itself.
Enter stock recovery and perform a cache, dalvik, and factory reset. Reboot from recovery.
Do a battery pull when the samsung splash screen starts to display itself. Boot back into download mode while holding volume down, home button, and power button. Let go of the buttons when the download mode screen comes up.
Use odin again and click on the AP button – select twrp_3.0.3-1_sm-j700t_23217. I found and downloaded this from XDA. Click start on odin and let odin do it thing. Disconnect the usb cable and do a battery pull.
Enter twrp recovery while holding volume up, home button and power button. Release buttons when twrp comes up.
Here, you will need to flash the latest supersu. I used v2.82-SR5. Also download no-verity-no-encrypt-ashyx.zip (big ups to ashyx for creating this)
Install these 2 files and reboot. NOTE: your phone will reboot twice – no cause for alarm.
After your phone boots up into nougat, go through the setup and reboot your phone.
After doing all of this, I've had zero issues. It may seem arduous but I found it necessary for my goal.
Did you have any issues with unlock screen lag on pin;/pattern?
There are reports and my own experience with this on a 7.0.0 version of otherwise identical process as yours to root. conclusion seems to be the no-verity-no-encrypt patch causes this, and that this patch (or something functionally identical) is integrated into supersu 2.82 versions.
edit - what model phone did you do this one? 7.1.1 not available for the j730g yet, unfortunately.
im on a320y , i got my phone suddenly custom binary blocked by frp lock,
then i reflash 7.0 stock firmware, i forgot how i rooted my device at the first time.
now im done with all the things, already rooted, but now im facing the unlock lag (especially when u are on secure lockscreen ex.pattern, password, etc)
this is very annoying, because there is no problem with unlocking screen when using fingerprint.
leo31 said:
im on a320y , i got my phone suddenly custom binary blocked by frp lock,
then i reflash 7.0 stock firmware, i forgot how i rooted my device at the first time.
now im done with all the things, already rooted, but now im facing the unlock lag (especially when u are on secure lockscreen ex.pattern, password, etc)
this is very annoying, because there is no problem with unlocking screen when using fingerprint.
Click to expand...
Click to collapse
caveat emptor, your results may differ drastically from mine, brick device, etc. but I did find a way around this
https://forum.xda-developers.com/apps/supersu/supersu-2-82-nougat-pin-pattern-unlock-t3764305
the issue is removing forced encryption, as far as the pattern unlock lag goes.
i have done this repeatedly on the a520f now and on a j730g/ds as well
DullPeon said:
caveat emptor, your results may differ drastically from mine, brick device, etc. but I did find a way around this
https://forum.xda-developers.com/apps/supersu/supersu-2-82-nougat-pin-pattern-unlock-t3764305
the issue is removing forced encryption, as far as the pattern unlock lag goes.
i have done this repeatedly on the a520f now and on a j730g/ds as well
Click to expand...
Click to collapse
can i flash the newest su while im still rooted? i mean, i dont want to reflash the whole rom again and again via odin.
and my superuser is from magisk manager. will it crash my system?
leo31 said:
can i flash the newest su while im still rooted? i mean, i dont want to reflash the whole rom again and again via odin.
and my superuser is from magisk manager. will it crash my system?
Click to expand...
Click to collapse
U should please educate yourself on what u got going on here..just some advice cuz......
SuperSu is SuperSU, either system wide root or systemless root.
Magisk is magisk, systemless root.
Seems like u rooted your device with SuperSu first, then installed magisk just a heads up SuperSu is obsolete now..and u do not need both. Use one or the other.. No matter, though, I would first make a nandroid backup. Next, I would go into SuperSu and select full system unroot. Next, reboot.go back to your magisk manager,it will say your device is not rooted. download and install through magisk, the magisk16.0 zip. Then it will do it's thing and install magisk and you will be rooted with magisk and have your root manager and magisk module manager. Magisk is like having SuperSu and Xposed all in one. So that's why I say to say goodbye to SuperSu and go all in with magisk. U can learn more that way too.
If u do not want magisk as root, I can't ponder why u wouldn't....just uninstall it. Then download whatever the latest SuperSu zip is. Boot to recovery and flash it. If there is any other updates no that magisk is gone, it will automatically update u with a notification and say yes to update SU binary. That's all.you are prob not getting it cuz magisk is in there too. So, u do not need that mess and remember to always make nandroid backups in twrp before anything where u may screw stuff up. I hope this helps and make sure to find out everything about anything with Android, before u do it.. good luck.
fullofhell said:
U should please educate yourself on what u got going on here..just some advice cuz......
SuperSu is SuperSU, either system wide root or systemless root.
Magisk is magisk, systemless root.
Seems like u rooted your device with SuperSu first, then installed magisk just a heads up SuperSu is obsolete now..and u do not need both. Use one or the other.. No matter, though, I would first make a nandroid backup. Next, I would go into SuperSu and select full system unroot. Next, reboot.go back to your magisk manager,it will say your device is not rooted. download and install through magisk, the magisk16.0 zip. Then it will do it's thing and install magisk and you will be rooted with magisk and have your root manager and magisk module manager. Magisk is like having SuperSu and Xposed all in one. So that's why I say to say goodbye to SuperSu and go all in with magisk. U can learn more that way too.
If u do not want magisk as root, I can't ponder why u wouldn't....just uninstall it. Then download whatever the latest SuperSu zip is. Boot to recovery and flash it. If there is any other updates no that magisk is gone, it will automatically update u with a notification and say yes to update SU binary. That's all.you are prob not getting it cuz magisk is in there too. So, u do not need that mess and remember to always make nandroid backups in twrp before anything where u may screw stuff up. I hope this helps and make sure to find out everything about anything with Android, before u do it.. good luck.
Click to expand...
Click to collapse
this is cool. your answer is helping me a lot. since i forgot how i rooted this device, i think i will remove my magisk manager first.
and i will see if my root is still working or not. if my device still rooted, so i will straightly flash newer SU.
but if it wont work, so i have to flash the newer SU too, right?
leo31 said:
this is cool. your answer is helping me a lot. since i forgot how i rooted this device, i think i will remove my magisk manager first.
and i will see if my root is still working or not. if my device still rooted, so i will straightly flash newer SU.
but if it wont work, so i have to flash the newer SU too, right?
Click to expand...
Click to collapse
Couple things buddy,
If u aren't rooted with magisk, which your magisk manager says rooted with magisk or rooted with SuperSu, uninstall magisk, then flash latest SuperSu zip.make sure to make backups in twrp.that is critical or u will be in bad shape if something goes wrong.and until u are better acquainted with Android , something very well may go wrong. If u are J700T, or J700T1 be sure to always flash the encryption break zip( no verity) which is posted on the ashyx twrp page.after flashing anything.always. there are more instructions under the j700t threads just click on any of our roms.make a nandroid in twrp first, that's a backup.then reboot. if u flashed SuperSu first u are rooted with it . So once uninstall magisk reboot, then u can just see if SuperSu app is functioning properly and shows root access granted on specific apps. Then go to recovery/twrp and flash latest SuperSu then encryption break zip(no verity). If u never did this before, chances are u never formatted after root or installing twrp and have to lose everything. After installing root or twrp u were supposed to go to twrp, wipe, format, "type yes" then flash root and encryption break zip, then reboot and set up phone. U can tell easily if in twrp it doesn't allow u to mount "data" and are unable to make a nandroid. If so don't bother with messing with anything root related till u format your phone, not factory reset, u select format, then type yes. Then flash SuperSu, and the encryption break zip. Once u do that re setup your phone. Then boot back to recovery and make a backup. That will flush magisk manger right out.
Sorry I know that's a lot but please read the j700T T1 threads. First pages of roms explain all this. Figure out if u have made nandroids and can even mount data first. Let me know what that status is. Then I can better help.
If u have done backups and flashed the encryption break zip before then follow above instructions and get rid of magisk or supersu.(this one is easy too, select full unroot) then leave magisk manager alone, go into it and select install magisk, it does it for u. Reboot after each system change. Then u will be rooted with magisk which is the current norm. SuperSu isn't what it once was the Creator retired and it's not anything special. Magisk is the future man. Good luck I hope this helps you.
---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------
U don't have to flash only SuperSu to have root.magisk also roots your device, way better too
fullofhell said:
Couple things buddy,
If u aren't rooted with magisk, which your magisk manager says rooted with magisk or rooted with SuperSu, uninstall magisk, then flash latest SuperSu zip.make sure to make backups in twrp.that is critical or u will be in bad shape if something goes wrong.and until u are better acquainted with Android , something very well may go wrong. If u are J700T, or J700T1 be sure to always flash the encryption break zip( no verity) which is posted on the ashyx twrp page.after flashing anything.always. there are more instructions under the j700t threads just click on any of our roms.make a nandroid in twrp first, that's a backup.then reboot. if u flashed SuperSu first u are rooted with it . So once uninstall magisk reboot, then u can just see if SuperSu app is functioning properly and shows root access granted on specific apps. Then go to recovery/twrp and flash latest SuperSu then encryption break zip(no verity). If u never did this before, chances are u never formatted after root or installing twrp and have to lose everything. After installing root or twrp u were supposed to go to twrp, wipe, format, "type yes" then flash root and encryption break zip, then reboot and set up phone. U can tell easily if in twrp it doesn't allow u to mount "data" and are unable to make a nandroid. If so don't bother with messing with anything root related till u format your phone, not factory reset, u select format, then type yes. Then flash SuperSu, and the encryption break zip. Once u do that re setup your phone. Then boot back to recovery and make a backup. That will flush magisk manger right out.
Sorry I know that's a lot but please read the j700T T1 threads. First pages of roms explain all this. Figure out if u have made nandroids and can even mount data first. Let me know what that status is. Then I can better help.
If u have done backups and flashed the encryption break zip before then follow above instructions and get rid of magisk or supersu.(this one is easy too, select full unroot) then leave magisk manager alone, go into it and select install magisk, it does it for u. Reboot after each system change. Then u will be rooted with magisk which is the current norm. SuperSu isn't what it once was the Creator retired and it's not anything special. Magisk is the future man. Good luck I hope this helps you.
---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------
U don't have to flash only SuperSu to have root.magisk also roots your device, way better too
Click to expand...
Click to collapse
i think the lag while unlocking screen is caused by dm-verity.zip file which i flashed straightly after installing twrp.
leo31 said:
i think the lag while unlocking screen is caused by dm-verity.zip file which i flashed straightly after installing twrp.
Click to expand...
Click to collapse
No, that same dm verity zip has been used since marshmallow and the unlock lag is a nougat bug. All that zip does is disable encryption so u can access data. And thus allow mounting of internal.
fullofhell said:
No, that same dm verity zip has been used since marshmallow and the unlock lag is a nougat bug. All that zip does is disable encryption so u can access data. And thus allow mounting of internal.
Click to expand...
Click to collapse
this is the 2nd time i root my device.
the first time i rooted my a3, i didn't face any lag and never laggy while unlocking screen.
but the problem is i forgot how i rooted it. which files did i flashed. which tutorial did i follow.
but no problem so far , because the fingerprint unlock does not give any lag.
Related
Hey I'm looking around and found 2 interesting posts.
http://forum.xda-developers.com/lg-...fficial-cyanogenmod-13-lg-g2-t3264508/page422
http://forum.xda-developers.com/lg-g2/help/starting-root-recovery-custom-rom-t3440752/page1
Click to expand...
Click to collapse
Pretty good instructions? I'm dancing around threads all over. I can't seem to get twrp onto a lollipop build. If I have twrp installed and try to manually go to LP from kk I get a bootloop the last few tries. If I have lp installed I can't seem to get autorec to respond, no matter which cfsu.
@blastagator:
Can you possibly list your steps for cwm and working magisk on your d800? Maybe I need to wipe all but internal, install lp bootstack in twrp-updated to one of your newer versions, install cwm? Is it clean from there to magisk and phhsu, magisk hide, phhapp? Will I need bumpboot ever for this?
andrew2432 said:
Hey I'm looking around and found 2 interesting posts.
Pretty good instructions? I'm dancing around threads all over. I can't seem to get twrp onto a lollipop build. If I have twrp installed and try to manually go to LP from kk I get a bootloop the last few tries. If I have lp installed I can't seem to get autorec to respond, no matter which cfsu.
@blastagator:
Can you possibly list your steps for cwm and working magisk on your d800? Maybe I need to wipe all but internal, install lp bootstack in twrp-updated to one of your newer versions, install cwm? Is it clean from there to magisk and phhsu, magisk hide, phhapp? Will I need bumpboot ever for this?
Click to expand...
Click to collapse
I do not use CWM, so I can't help you with that.
Basic Sequence (assuming starting from completely stock):
Use your favorite rooting tool - OneClick Root still works (I think)
Then install AutoRec (appropriate version for your ROM)
That gets you TWRP - boot TWRP with the key combo
Flash newest TWRP - reboot recovery
Flash bootstack to match new ROM (LP for LP or MM)
Advanced wipe, wipe /data, /system, /cache, /sd, /dalvik
Reboot Recovery
Copy new ROM to phone
Install new ROM
Reboot phone, profit
for magisk, flash magisk zip and then flash boot bump zip
IMPORTANT: If ROM has built-in su (like CM13 DOES) you need to delete that from the device.
I'd recommend deleting these BEFORE installing magisk (but I don't know if it actually matters)
For CM13, enable root in the developer menu
use your favorite console app
Code:
su
mount -o remount,rw /system
rm /system/xbin/su
rm /system/bin/su
Some ROMs might have an su file in /sbin and you might need to remount / as rw to remove that. For CM13 it is just those two files.
blastagator said:
I do not use CWM, so I can't help you with that.
Basic Sequence (assuming starting from completely stock):
Use your favorite rooting tool - OneClick Root still works (I think)
Then install AutoRec (appropriate version for your ROM)
That gets you TWRP - boot TWRP with the key combo
Flash newest TWRP - reboot recovery
Flash bootstack to match new ROM (LP for LP or MM)
Advanced wipe, wipe everything
Reboot Recovery
Copy new ROM to phone
Install new ROM
Reboot phone, profit
for magisk, flash magisk zip and then flash boot bump zip
IMPORTANT: If ROM has built-in su (like CM13 DOES) you need to delete that from the device.
I'd recommend deleting these BEFORE installing magisk (but I don't know if it actually matters)
For CM13, enable root in the developer menu
use your favorite console app
Some ROMs might have an su file in /sbin and you might need to remount / as rw to remove that. For CM13 it is just those two files.
Click to expand...
Click to collapse
Ahh cm is just the recovery not the rom, you use it and not twrp? The newest twrp for g2d800 is yours...twrp-d800-bump-blastagator?? What rom do you use? Will I be able to transfer files to the phone after wiping? I guess it stays in recovery after a wipe...just not used to that I guess.
Get twrp, flash bootstack...from you, wipe all, push my rom, flash rom, boot to phone. Experience my first ever custom os for a bit....Remove su with adb, boot to recovery, magisk, bump, phhsu zip, boot to phone. Install magisk 2.1, enable hide, reboot, phhsu app, ???, profit.
1. How can I thank ALL your posts ever?
2. Cwm nightly is the rom, the other is the recovery?
andrew2432 said:
Ahh cm is just the recovery not the rom, you use it and not twrp? The newest twrp for g2d800 is yours...twrp-d800-bump-blastagator?? What rom do you use? Will I be able to transfer files to the phone after wiping? I guess it stays in recovery after a wipe...just not used to that I guess.
Get twrp, flash bootstack...from you, wipe all, push my rom, flash rom, boot to phone. Experience my first ever custom os for a bit....Remove su with adb, boot to recovery, magisk, bump, phhsu zip, boot to phone. Install magisk 2.1, enable hide, reboot, phhsu app, ???, profit.
1. How can I thank ALL your posts ever?
2. Cwm nightly is the rom, the other is the recovery?
Click to expand...
Click to collapse
Recovery lives in /recovery partition, so I guess I should clarify, don't wipe EVERYTHING, lol. I can't remember if I enabled ability to wipe recovery, DONT DO THAT :silly:
edit: Advanced wipe, wipe /data, /system, /cache, /sd, /dalvik
But, as for everything else, recovery will live through wiping /system /data, etc. You need to backup anything you want to save though. Wipe will destroy everything.
Other than that, you pretty much got the rest.
edit 2: http://download.cyanogenmod.org/?device=d800
See image for ROM vs CM Recovery.
CWM = Clockwork Mod (a different recovery)
CM = CyanogenMod (a ROM)
.
@blastagator:
Haha I may have noticed that during the process. The bumpbootv1.0 is the one to use for even these newer methods?? That was what q2 really was supposed to be. I keep mentioning you because I assume it helps you see my posts, I assume your pretty busy. Some of those posts and files are rom when the g2 was almost new lol thanks seriously for getting back so fast I wish I could help this community more but I'm a skid
EDIT: awesome, I have to run all Internet functions off of the sprint lte network and was downloading one of those behemoths during that posts....that let's me know my efforts aren't in vain
andrew2432 said:
@blastagator:
Haha I may have noticed that during the process. The bumpbootv1.0 is the one to use for even these newer methods?? That was what q2 really was supposed to be. I keep mentioning you because I assume it helps you see my posts, I assume your pretty busy. Some of those posts and files are rom when the g2 was almost new lol thanks seriously for getting back so fast I wish I could help this community more but I'm a skid
Click to expand...
Click to collapse
Please read my edits and don't kill your phone. I am not always so timely in my responses :good:
Other than that, good luck!
There are tons of posts that go into more detail about what I wrote. Just make sure you have a plan before you do it. Think: Measure twice, cut once.
This g2 I found service locked while cleaning out a rental property. I have a galaxy s5 stupid sprint for my primary. I use the g2 for...well everything game and other related. until my Hotspot mod on my galaxy suddenly stopped working on lp. I blame the man
Äptiva is the one I read about a gutted 802 into an 800 or something, got you guys confused!!
@blastagator
Didn't work...steps followed what OS do you use? Do you use you d80030b or something else? No sn or pgo
If I update autorec twrp to your 3.0.2-1 will it hold through a manual FOTA update to 5.0? I use GPS system app for location. Is it possible moving to system then unrooting causes these bootloops and such? My g2 passes sn but I cm and gApps is causing issues? Logged into sc, pass sn, no pgo
andrew2432 said:
@blastagator
Didn't work...steps followed what OS do you use? Do you use you d80030b or something else? No sn or pgo
If I update autorec twrp to your 3.0.2-1 will it hold through a manual FOTA update to 5.0? I use GPS system app for location. Is it possible moving to system then unrooting causes these bootloops and such? My g2 passes sn but I cm and gApps is causing issues? Logged into sc, pass sn, no pgo
Click to expand...
Click to collapse
CM13.
If you're trying to get safety net to work, you have to enable magisk hide (in the magisk app)
Also, if you're using xposed, you can't use safety net.
@blastagator
Yeah done and done. Only things I can figure is installed the application side of phh su last, and gaps after being phh rooted.? I'm gonna check for su files with es here shortly. Safety net passes, snapchat works, just not pgo
Enabled hide after installing application and got root access when ticking hide. Literally the only thing that won't work is pgo, haven't tried android pay yet
No xposed I bought a way around that, not causing the issue because I haven't installed it on the d800
andrew2432 said:
@blastagator
Yeah done and done. Only things I can figure is installed the application side of phh su last, and gaps after being phh rooted.? I'm gonna check for su files with es here shortly. Safety net passes, snapchat works, just not pgo
Enabled hide after installing application and got root access when ticking hide. Literally the only thing that won't work is pgo, haven't tried android pay yet
No xposed I bought a way around that, not causing the issue because I haven't installed it on the d800
Click to expand...
Click to collapse
If the safety net test app passes, it should be working. perhaps downgrade your pogo a version or two, maybe they added something else.
Well, it's on a WiFi only, no SIM device...
I'm thinking this is the issue I'm experiencing now. Which may stem from an update. An older apk is a good idea, I was able to log on with magisk v6 a bit a go and when magisk 7 and 8 first came out I could.
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
Hey everyone,
I`m running LineageOS on my phone and am rooted using SuperSU which seems to work, according to Rootchecker and the feww apps I use, which make use of root privileges.
But I`m not entirely happy with my current situation, since it seems that more and more apps don`t tend to work with my rooted phone. So what are my ways out of this?
Can I easily unroot my phone, while keeping LineageOS?
Is there a working alternative to SuperSU, which would enable me to stay rooted on LineageOS without reflashing the OS and use Banking-Apps?
I`ve heard of Magisk, but I am unsure of how to switch over from my current state and I`am not sure whether or not it would solve my problems
Thanks for any help in advance!!
Magisk
You just have to go to SuperSU, then Full Unroot, then download Magisk 13.3 and flash it from TWRP. After that you should have Magisk Manager, if for some weird reason you don't, install it via apk
Then you just go to the settings, tick MagiskHide, then go back and open the side panel, MagiskHide - select the apps that you want Magisk to hide itself from
So I tried to do what you said.
I did the full unroot in the SuperSu App,
My phone rebooted
I shut it down again and booted into recovery
Tried flashing Magisk
But it failed, apparently due to my Boot image being patched by another program and told me to go with stock image
What do I do now? And will I lose any data by doing so? Thank you so much for any help!
Weird, but you can simply dirty flash LineageOS (the same one that you have now, or an update, doesn't matter) and it should let you install Magisk.
I did what you said and installed a delta update using LineageOS Downloader. Had to manually flash it in TWRP since I had no root permissions anymore. But I was able to install Magisk like a charm! Now I have to questions:
1. How do I update Magisk? Using the app?
2. Do I have to flash it again everytime I'm updating LOS?
Thanks for the great help so far!
And what exactly are those moduls? Should I be messing with them?
If updates come they will appear on the status bar and you can download them, and they'll install with the phone on. after that you have to (not quick) reboot your phone.
and about the modules, seriously? what do you think??
I can't seem to find any rooting method for C432B380 software. Is there any step-by-step guide for this version? I'm currently on fully stock firmware, and I haven't unlocked my bootloader yet.
SteadyDisorder said:
I can't seem to find any rooting method for C432B380 software. Is there any step-by-step guide for this version? I'm currently on fully stock firmware, and I haven't unlocked my bootloader yet.
Click to expand...
Click to collapse
Well, ask for unlock code - that's the first step.
I am interested in this as well, as from what I see some people seem to run into problems. Say one is on Nougat C432B380 (I'm B381) and has now got the unlock code. What then? First of all, unlocking the bootloader will result in a reset, clean C432B380 installation, right? Or will there be any need to flash something else?
EDIT: I passed the unlock part following the Guide, and ended up with a clean Nougat installation as I thought. Now what? In the OldDroid TWRP thread I see many people having trouble...
Makishima said:
I am interested in this as well, as from what I see some people seem to run into problems. Say one is on Nougat C432B380 (I'm B381) and has now got the unlock code. What then? First of all, unlocking the bootloader will result in a reset, clean C432B380 installation, right? Or will there be any need to flash something else?
EDIT: I passed the unlock part following the Guide, and ended up with a clean Nougat installation as I thought. Now what? In the OldDroid TWRP thread I see many people having trouble...
Click to expand...
Click to collapse
I recommend staying away from any custom roms for now as all seem to have problems... you say you have an unlocked bootloader, then next step would be flashing a custom recovery, then from there... flashing supersu... try not to do much more than that and accept a fully functioning rooted phone better than getting a squichy camera or whatever from custom roms.... wait till they get stable
Moemen Shahawy said:
I recommend staying away from any custom roms for now as all seem to have problems... you say you have an unlocked bootloader, then next step would be flashing a custom recovery, then from there... flashing supersu... try not to do much more than that and accept a fully functioning rooted phone better than getting a squichy camera or whatever from custom roms.... wait till they get stable
Click to expand...
Click to collapse
I was not planning to install a custom ROM, I just want root, mainly for Viper4Android and some other things, but after reading the whole OldDroid TWRP thread I saw some people reporting problems with bootloops and whatnot, mainly after flashing SuperSU. Is flashing TWRP and then EliteKernel and rooting with phh or Magisk preferable? I just got my device back from the Huawei services, with a new board and everything and I don't want to ruin the stock installation again, so I am trying to be a bit more certain before I do anything.
Thank you for replying.
EDIT: Okay, so what I did was flash the latest OldDroid TWRP through fastboot and then I booted into recovery and flashed the latest Magisk (v13.3 I think). Now I have root and everything seems to work. So happy.
EDIT2: It seems that although it says I have root, I can't actually do anything with it, e.g. I can't uninstall system apps with Link2SD even though it says it was successful - reboot, still there - and the modules won't appear even after installing.... So, I don't know what's wrong.
Makishima said:
I was not planning to install a custom ROM, I just want root, mainly for Viper4Android and some other things, but after reading the whole OldDroid TWRP thread I saw some people reporting problems with bootloops and whatnot, mainly after flashing SuperSU. Is flashing TWRP and then EliteKernel and rooting with phh or Magisk preferable? I just got my device back from the Huawei services, with a new board and everything and I don't want to ruin the stock installation again, so I am trying to be a bit more certain before I do anything.
Thank you for replying.
EDIT: Okay, so what I did was flash the latest OldDroid TWRP through fastboot and then I booted into recovery and flashed the latest Magisk (v13.3 I think). Now I have root and everything seems to work. So happy.
EDIT2: It seems that although it says I have root, I can't actually do anything with it, e.g. I can't uninstall system apps with Link2SD even though it says it was successful - reboot, still there - and the modules won't appear even after installing.... So, I don't know what's wrong.
Click to expand...
Click to collapse
stay away from magisk if you want something stable... at least my opinion. Magisk is fine, the only add it adds, is magisk hide, which seems to keep failing now for most people. I'm suffering through it now and switching to supersu... try finding the correct way to remove magisk root and go the chainfire's supersu
Moemen Shahawy said:
stay away from magisk if you want something stable... at least my opinion. Magisk is fine, the only add it adds, is magisk hide, which seems to keep failing now for most people. I'm suffering through it now and switching to supersu... try finding the correct way to remove magisk root and go the chainfire's supersu
Click to expand...
Click to collapse
I restored a backup of the boot partition I had made when I first flashed TWRP which seems to have deleted Magisk, the app told me it was not installed (even though I see now a Magisk folder in data...) and then flashed Super SU, but I still can't delete system apps and having trouble with Viper*. But maybe it's not SU's fault. I don't know. I flashed v2.79, I previously had trouble with the newest versions.
Also, I had not activated the Hide function, I think.
*It is driving me crazy! Why does it not work? Supposedly I am root, I even deleted the system apps with the file managers but when I exited and reentered the folder they were there again. What is going on?... Wait... Is this normal, is it because it is system-less root?
To root any nougat fw:
1)unlock bootloader. You have to get unlock code from huawey and then in fastboot mode do: "fastboot oem unlock yourcode"
2)flash twrp recovery, i suggest you the hassan's recovery https://www.androidfilehost.com/?fid=745425885120756473
3)in fastboot mode do "fastboot flash recovery nameoftherecovery.img
4)reboot in recovery and flash this supersu
It is the 2.82 for emui 5 without loop mount,is perfect for p9lite https://www.androidfilehost.com/?fid=817550096634776377
I'm following the topjohnwu's guide on how to update with Magisk but I do not find it clear enough. Are these the steps I need to take in order to not-brick and update my phone with the Feb update.
1. Uninstall Magisk by "restore images" option.
2. Install OTA
3. Reboot to reinstall Magisk on second slot
Magisk is NOT installed on the second partition! And I prefer not to flash back the original image just to do that. My system should be read only and I do not have twrp, I never had, I updated my Google services framework from apkmirror and I got the update, now how do I apply it without soft bricking?
Update
Step 2 failed, "installation problem". Wtf do I do in order not to lose Magisk or data?
Edit
I've uninstalled Magisk but haven't restarted, hoping to get a solution where I keep my sh*t since that's what the guide said...
Edit 2
I'm reading the other thread but I'm having trouble finding a single useful information there, quote one if you find it, it might be my autism that I don't see a solution in that three pages long thread. Tell me I need to MiFlash this sh*t so I calmly jump through my window instead of wasting the whole night on making it work, then wasting another day on backing my sh*t up.
Edit 3
Fully uninstalled Magisk by instructions of an indian guide. BOOTLOOP.
Note to self, stop following southern asian guides.
Downloaded ROM and MiFlash, flashed flash_all_except_storage.bat.
Shook for 4 minutes until "success" mark, successful reboot.
Edit 4:
follow the regular magisk flash guide https://forum.xda-developers.com/mi-a1/help/how-to-root-mi-a1-february-ota-update-t3757934
If you got into bootloop after Magisk uninstallation, you did modify system partition at some point. This is also the reason why you couldn't install OTA. Magisk OTA update guide works perfectly fine for unaltered system partition.
_mysiak_ said:
If you got into bootloop after Magisk uninstallation, you did modify system partition at some point. This is also the reason why you couldn't install OTA. Magisk OTA update guide works perfectly fine for unaltered system partition.
Click to expand...
Click to collapse
That's what I figured, but how? I just did exactly everything I did before the OTA attempt, I just installed few modules and touched nothing else. At which point could've I touched system partition?
So I'm reading now that apps can still alter /system with the Magisk root perm, so, I what about one of these apps.
1. Does anyone know if they can mess with the system?
BusyBox
Greenify
Lucky patcher (this c*nt is my main suspect)
Titanium backup
2. Can we somehow make sure that we haven't touched the system partition before OTA attempt?
3. Once I've redone everything (flash Rom without storage, install OTA, install Magisk), my system shouldn't be touched now, right?
A14DWIN said:
That's what I figured, but how? I just did exactly everything I did before the OTA attempt, I just installed few modules and touched nothing else. At which point could've I touched system partition?
So I'm reading now that apps can still alter /system with the Magisk root perm, so, I what about one of these apps.
1. Does anyone know if they can mess with the system?
BusyBox
Greenify
Lucky patcher (this c*nt is my main suspect)
Titanium backup
2. Can we somehow make sure that we haven't touched the system partition before OTA attempt?
3. Once I've redone everything (flash Rom without storage, install OTA, install Magisk), my system shouldn't be touched now, right?
Click to expand...
Click to collapse
Please keep in mind that Magisk is 2in1 package. First of all it provides root access, any app with root access can modify system directly. Second feature are systemless modifications, but you must follow defined rules to make them work.
From your list of apps, BusyBox would be my first suspect. You must use Magisk BusyBox module, the standard BusyBox is installed directly to the system partition. Lucky app might be the culprit too, though it depends on which features exactly did you use.
Yes, once you reflash stock ROM, apply OTA and install Magisk (the correct way), you're system partition will be ready for the next OTA.
Someone mentioned one command which could verify the last modification date of any partition, but can't find it right now.
_mysiak_ said:
Please keep in mind that Magisk is 2in1 package. First of all it provides root access, any app with root access can modify system directly. Second feature are systemless modifications, but you must follow defined rules to make them work.
From your list of apps, BusyBox would be my first suspect. You must use Magisk BusyBox module, the standard BusyBox is installed directly to the system partition. Lucky app might be the culprit too, though it depends on which features exactly did you use.
Yes, once you reflash stock ROM, apply OTA and install Magisk (the correct way), you're system partition will be ready for the next OTA.
Someone mentioned one command which could verify the last modification date of any partition, but can't find it right now.
Click to expand...
Click to collapse
Dang I really need that command.
_mysiak_ said:
Please keep in mind that Magisk is 2in1 package. First of all it provides root access, any app with root access can modify system directly. Second feature are systemless modifications, but you must follow defined rules to make them work.
From your list of apps, BusyBox would be my first suspect. You must use Magisk BusyBox module, the standard BusyBox is installed directly to the system partition. Lucky app might be the culprit too, though it depends on which features exactly did you use.
Yes, once you reflash stock ROM, apply OTA and install Magisk (the correct way), you're system partition will be ready for the next OTA.
Someone mentioned one command which could verify the last modification date of any partition, but can't find it right now.
Click to expand...
Click to collapse
Don't bother trying to find it, it exists, I'll make a dedicated thread at some point, thanks for the answer, BusyBox seems logical.
The correct way to install Magisk? I just flash Ranjit's patched img from the official thread on Magisk root, that should be the correct way.
I just use lucky to patch cirtain apps, so that shouldn't be a problem
Right now, I'm giving Magisk root perm to Greenify, Lucky Patcher and Unified Hosts. Also both Greenify and the Unified hosts adblock have their own modules in magisk.
Hopefully I still haven't touched my system partition.
I encountered the error as well after trying the Pixel OTA method. To flash the update successfully, I flashed stock January system and boot img via fastboot and it updated properly after. Then I just patched the stock Feb boot img and went back to fastboot. Once there, i did the fastboot boot command with the patched Feb boot.img so I got root back after updating.
Sent from my Xiaomi Mi A1 using XDA Labs
HI,
I have a redmi5+ rooted. I use luckypatcher (i applied some patchs to some apps) and i have installed once BusyBox (didn't do anything in special).
I want to know if it is secure to flash the full update?
PS: how do I confirm if the system files and vendor are ok to proceed?
Thanks
cant you flash the ota in twrp and then reflash magisk if needed?
robgee789 said:
cant you flash the ota in twrp and then reflash magisk if needed?
Click to expand...
Click to collapse
Yes, I can do that.
I Know the procedure to flash full zip file via TWRP. Via this toturial: youtube.com/watch?v=oUUzxYHV_ac&t=1s&index=11&list=WL
But i want to know if it is secure to flash, because i used these two applications.