Related
How To Play Pokemon Go with Superuser (Root enabled)
Note:
IT MIGHT CAUSE BOOTLOOP OR MIGHT BRICK YOUR DEVICE. MAKE SURE YOU HAVE A BACKUP.
Requirement:
Fresh Installation of Rom or Dirty Flash of your current rom (I tested it on CM and RR- Fresh.It might work on other custom roms.)
TWRP Recovery
Magisk: http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
unSU Script : http://forum.xda-developers.com/attachment.php?attachmentid=3931994&d=1478779893
Steps:
1. Reboot into Recovery
2. Flash unSU Script and Magisk in order.
3. Reboot into System. (Mobile should boot without bootloop, otherwise you have to reinstall the ROM and try again)
4. Install Phh Superuser from here: https://play.google.com/store/apps/details?id=me.phh.superuser&hl=en.
4. Open Magisk Manager ( Update it,if it is asked) and it will ask you for SU permission. Allow it.
6. Go to Settings and Tick " Enable Magisk Hide " and Reboot your phone.
7. Once again Magisk Manager and it will show status of SafetyNet at 3rd row and It should Passed.
Install PokemonGo and Enjoy
Credits:
@topjohnwu
@phhusson
@Hw4ng3r
@Tikerz
Updates:
8/1/17
Updated the steps with New Magsik version 10.2
I did a clan flash. Booted and let everything settle. The rebooted into TWRP recovery. Mounted system, and deleted (or renamed) the Su files from system/bin and system/xbin. This removes root but I can play Pokémon.
Jowhee said:
I did a clan flash. Booted and let everything settle. The rebooted into TWRP recovery. Mounted system, and deleted (or renamed) the Su files from system/bin and system/xbin. This removes root but I can play Pokémon.
Click to expand...
Click to collapse
This guide is for keeping root AND passing SafetyNet.
BTW, this method also works on CM13 and OOS.
It didn't mention keeping root in the title.
Jowhee said:
It didn't mention keeping root in the title.
Click to expand...
Click to collapse
Sorry for the confusion.
Updated the thread.
SafetyNet Helper fails after following the steps:
SafetyNet request: success
Response Validation: success
CTS profile match: failure
Click to expand...
Click to collapse
Do we need to go back into fastboot and disabled the bootloader unlock?
nphillips said:
SafetyNet Helper fails after following the steps:
Do we need to go back into fastboot and disabled the bootloader unlock?
Click to expand...
Click to collapse
Not necessarily. Some kernels such as blu_kernel bypass the bootloader check. Try it out.
svprm said:
How To Play Pokemon Go with Superuser (Root enabled)
Click to expand...
Click to collapse
can Xposed work along with PoGo ?
samnaction said:
can Xposed work along with PoGo ?
Click to expand...
Click to collapse
I'm not sure. I didn't test it.
But you can install the Xposed Framework module through Magisk Manager.
In CM builds you don't need all this you just need this simple app:
http://forum.xda-developers.com/android/apps-games/isu-simple-app-to-deactivate-activate-t3478348
I'm gonna assume this doesn't work with CM12.1 right?
Yepi69 said:
I'm gonna assume this doesn't work with CM12.1 right?
Click to expand...
Click to collapse
I didn't try.
But you can try and post the result here that would help others.
I followed the steps in the first post and everything went OK. I'm using oxygen Os nougat 0.9
Thanks for your tutorial.
Does this mean that CM14.1 passes safetynet now? I don't exactly need root but when I tried it a few weeks ago PKMN Go told me that the OS I had was not supported.
rdar_93 said:
Does this mean that CM14.1 passes safetynet now? I don't exactly need root but when I tried it a few weeks ago PKMN Go told me that the OS I had was not supported.
Click to expand...
Click to collapse
Yes, cm 14.1 could pass safety net with this.
This works for sure. But if you're running a secondary ROM using MultiROM the modified boot.img will cause safetynet to indeed fail. I hope they do bring an update soon to fix this though.
Daft question, but i'm unable to use an online banking app, due to being rooted. I know this relates to PokemonGo, but wondering if this could fool the banking app?
I am using H2OS beta (Nougat) and I followed the below steps, but safety net is failing.
1. Dirty flash current ROM
2. Flash UnSU.zip
3. Flash magisk and phh zips
4. Reboot
5. Install Magisk Manager and Phh superuser
6. check safety net
Is there anything which I'm doing wrong? Can you help me please. Thank you
Edit: A reboot and everything worked fine. Thank you so much
Sorry to disturb this thread, but I am a bit confused because the official Magisk thread nowhere mentions that phh's su would be the only working su solution:
topjohnwu said:
If you're using Magisk v7+ with Magisk version of phh's superuser , or rooted with Official Systemless SuperSU (Android 6.0+ only)
If you choose to use SuperSU (only support Android 6.0+)
Click to expand...
Click to collapse
So I am really wondering about your step 2 ...
svprm said:
2. Flash unSU Script, Magisk and phh's SuperUser Magisk.
Click to expand...
Click to collapse
pathologo said:
Sorry to disturb this thread, but I am a bit confused because the official Magisk thread nowhere mentions that phh's su would be the only working su solution:
So I am really wondering about your step 2 ...
Click to expand...
Click to collapse
Actually i didn't try with SuperSu.So i mentioned phh's SU.
It might work with SuperSu too.
Hello, I am currently rooted on stock oos 4.0.3, with latest TWRP and super su free v2.79, can anyone help me out and tell me how to switch to magisk please, thank you!
Can I just use super su full unroot option then flash magisk?
Either reflash the original boot.img or download the unsu script from https://forum.xda-developers.com/showpost.php?p=63615067, then flash magisk again.
palesaint said:
Either reflash the original boot.img or download the unsu script from https://forum.xda-developers.com/showpost.php?p=63615067, then flash magisk again.
Click to expand...
Click to collapse
so flash unsu, then flash magisk. simple?
Dr Grato said:
so flash unsu, then flash magisk. simple?
Click to expand...
Click to collapse
If you use the unSU script the process is:
unSU
stock boot image
Magisk
This method did not work for me.
I am on KETAN n10 and initially, viper did not work. I installed magisk but that didn't fix it. nor the meefik busy box. So i decided to uninstall magisk and go back to superSU and it magically worked...
I unrooted from SuperSU itself like shown on the app's forum I believe. It rebooted my phone, I went into recovery first and then just flashed the latest magisk and made the switch :laugh:
SourPower said:
I unrooted from SuperSU itself like shown on the app's forum I believe. It rebooted my phone, I went into recovery first and then just flashed the latest magisk and made the switch :laugh:
Click to expand...
Click to collapse
So you just went into the SuperSU app and used the built in Unroot option, and when the phone rebooted, you went back into recovery and flashed the latest Magisk and did NOT flash a boot.img and everything worked fine? you have root with Magisk now instead of SU and you didnt get a bootloop at all??? (i really want to swap out SU for magisk in my sons LG G2, so he can play PoGo again lol) (His G2 is running CRdroid custom rom, I wonder if that effects the steps I'll need to take)
Can anyone offer me some guidance or assistance please and thank you?
JG420 said:
So you just went into the SuperSU app and used the built in Unroot option, and when the phone rebooted, you went back into recovery and flashed the latest Magisk and did NOT flash a boot.img and everything worked fine? you have root with Magisk now instead of SU and you didnt get a bootloop at all??? (i really want to swap out SU for magisk in my sons LG G2, so he can play PoGo again lol) (His G2 is running CRdroid custom rom, I wonder if that effects the steps I'll need to take)
Can anyone offer me some guidance or assistance please and thank you?
Click to expand...
Click to collapse
If there's a proper backup of the boot image for the SuperSU app's full unroot option to restore, then that process should work perfectly (I've done it on a few devices myself). It's when it can't properly restore the boot image you might have issues and you'll have to do it yourself.
Take a look in the Magisk Troubleshooting guide, under "Moving from another systemless root solution to MagiskSU".
The nuclear method might be, to just flash the full stock OOS zip (can flash in TWRP) which will unroot and restore the boot.img (and everything else!). Then immediately flash Magisk before rebooting (so have the Magisk zip on the phone before updating). This should fully remove SuperSU, install Magisk, and keep TWRP on the phone.
Seeing as the original poster is still on OOS 4.0.3, you may want to update, anyway!
JG420 said:
So you just went into the SuperSU app and used the built in Unroot option, and when the phone rebooted, you went back into recovery and flashed the latest Magisk and did NOT flash a boot.img and everything worked fine? you have root with Magisk now instead of SU and you didnt get a bootloop at all??? (i really want to swap out SU for magisk in my sons LG G2, so he can play PoGo again lol) (His G2 is running CRdroid custom rom, I wonder if that effects the steps I'll need to take)
Can anyone offer me some guidance or assistance please and thank you?
Click to expand...
Click to collapse
I've done this on my 3t but I do have a G3 coincidentally lol, but yes I unrooted from su, it restarted my phone, before booting back into the system I went in twrp right away and then flashed magisk.
There are two options given in the SuperSU app, one is clean up to switch to a different SU app and the other is to permanently unroot. Which option is better?
hypothrax said:
There are two options given in the SuperSU app, one is clean up to switch to a different SU app and the other is to permanently unroot. Which option is better?
Click to expand...
Click to collapse
I chose the Full Unroot option. Then flashed magisk. Worked perfectly.
Use the full unroot option. Catch here is that you might get dm-verity warning. It won't affect the phone in anyway but Android Pay might not work and you will see the warning for 5 seconds, everytime you restart the phone.
Thanks so much for ths thread. I am on Resurrection Remix OS and inititally installed SuperSU over Magisk (which came with the ROM). I decided that I wanted to use Magisk instead and followed the instructions in this thread and it worked a treat.
Thought I'd share how I upgraded my T-Mobile Galaxy S6 to Nougat (G920TUVU5FQE1 ) with root, deep sleep and SafetyNet bypass.
*** Read all step before starting as you will need to download and copy several files to your phone first ***
NOTE: This method will trip Knox!
Reboot into Download Mode
Flash G920TUVU5FQE1_G920TTMB5FQE1_G920TUVU5FQE1_HOME.tar.md5 with Odin (I used v3.10.6)
Download from Android File Host | Google Drive.
Reboot into Download Mode
Flash TWRP img.tar with Odin
Flash Magisk zip with TWRP and reboot to system
Install Magisk Manager (and enable Magisk Hide in Magisk Manager settings)
NOTE: The steps below will re-enable Deep Sleep
Install Flashify
Flash stock recovery.img with Flashify
Download from Android File Host | Google Drive.
Wipe cache (twice for good measure) and reboot
(Optional) Flash TWRP img using Flashify and reboot to system
Enjoy Nougat with root and SafetyNet bypass on your G920T! :good:
You do know that Google pulled Magisk from the Play Store....
The Sickness said:
You do know that Google pulled Magisk from the Play Store......
Click to expand...
Click to collapse
You do know that was inevitable and that there are other ways to obtain Magisk Manager?
KaneHusky said:
You do know that was inevitable and that there are other ways to obtain Magisk Manager?
Click to expand...
Click to collapse
Of course there are other ways......But your posting a link to Magisk that doesnt exist.
The Sickness said:
Of course there are other ways......But your posting a link to Magisk that doesnt exist.
Click to expand...
Click to collapse
Uh... I linked to the main Magisk thread on XDA, not Google Play.
KaneHusky said:
Uh... I linked to the main Magisk thread on XDA, not Google Play.
Click to expand...
Click to collapse
Uhh.....thats because you just changed it. I'm not gonna waste my time posting about something that is'nt correct.
So have a very lovely day
The Sickness said:
Uhh.....thats because you just changed it. I'm not gonna waste my time posting about something that is'nt correct.
So have a very lovely day
Click to expand...
Click to collapse
Wow. Ok, dude. Do you see an edit anywhere for my post? No. I specifically linked to the XDA thread because I know it was taken off Google Play. :good:
Gonna give this a shot. Is this an official build or a port? And i wonder if i can use @stangdriver44 V4A Aroma installer hmmmmmm. Is the kernel stock or set to permissive?
BigDaddy38 said:
Gonna give this a shot. Is this an official build or a port? And i wonder if i can use @stangdriver44 V4A Aroma installer hmmmmmm. Is the kernel stock or set to permissive?
Click to expand...
Click to collapse
It's pulled straight from Smart Switch so everything is 100% stock.
KaneHusky said:
It's pulled straight from Smart Switch so everything is 100% stock.
Click to expand...
Click to collapse
Sweet gonna give it a shot, Thankyou!!!!
i have no idea where to find magisk manager any help would be appreciated
BigDaddy38 said:
i have no idea where to find magisk manager any help would be appreciated
Click to expand...
Click to collapse
There's a Downloads section with a direct link to it in the main Magisk thread which I linked to.
KaneHusky said:
There's a Downloads section with a direct link to it in the main Magisk thread which I linked to.
Click to expand...
Click to collapse
Your right i found it, the link didnt work earlier when i tried thankyou
Do we not need to flash SuperSU prior to Magisk? I'm not too familiar with the process so I could be mistaken.
EncryptedCurse said:
Do we not need to flash SuperSU prior to Magisk? I'm not too familiar with the process so I could be mistaken.
Click to expand...
Click to collapse
You don't have to, no. Magisk uses its own superuser called MagiskSU, which gets installed with the Magisk zip file.
It seems kinda... excessive to put TWRP on, then go back to the stock recovery, then back to TWRP again.. Is there a reason for this part?
-> Flash stock recovery.img with Flashify
-> Wipe cache (twice for good measure) and reboot
-> (Optional) Flash TWRP img using Flashify and reboot to system
crashff said:
It seems kinda... excessive to put TWRP on, then go back to the stock recovery, then back to TWRP again.. Is there a reason for this part?
-> Flash stock recovery.img with Flashify
-> Wipe cache (twice for good measure) and reboot
-> (Optional) Flash TWRP img using Flashify and reboot to system
Click to expand...
Click to collapse
Yeah, to fix deep sleep not working after the first TWRP flash.
Heres what I did lastnight.................I followed your setup. And then installed Noble Kernel set to permissive so i can run V4A. Well the kernel trips Safety Net and you get a continuous notification because of the permissive kernel. So I uninstalled magisk(I dont care for it till the dev keeps it updated for us). I then flashed Super SU 2.8+ through TWRP. Used @stangdriver44 V4A Aroma Installer. So you still get the security notification, I found that system app and froze it. No more annoying notification. This is where im at now. Stock Nougat Rooted w-SuperSU/Noble Kernel for Tmobile/Viper 4 Android. All working flawlessly. @The Sickness Are you gonna maybe try and get something going on nougat with that sickness. Maybe an S8 themed option. I bet between you and stangdriver44 it could be awesome. Because you know we probably wont get another Rom upgrade for the S6 after Nougat.
BigDaddy38 said:
Heres what I did lastnight.................I followed your setup. And then installed Noble Kernel set to permissive so i can run V4A. Well the kernel trips Safety Net and you get a continuous notification because of the permissive kernel. So I uninstalled magisk(I dont care for it till the dev keeps it updated for us). I then flashed Super SU 2.8+ through TWRP. Used @stangdriver44 V4A Aroma Installer. So you still get the security notification, I found that system app and froze it. No more annoying notification. This is where im at now. Stock Nougat Rooted w-SuperSU/Noble Kernel for Tmobile/Viper 4 Android. All working flawlessly. @The Sickness Are you gonna maybe try and get something going on nougat with that sickness. Maybe an S8 themed option. I bet between you and stangdriver44 it could be awesome. Because you know we probably wont get another Rom upgrade for the S6 after Nougat.
Click to expand...
Click to collapse
Read my rom thread and kernel thread.
KaneHusky said:
You don't have to, no. Magisk uses its own superuser called MagiskSU, which gets installed with the Magisk zip file.
Click to expand...
Click to collapse
Everything was working fine last night, but I seem to have lost root during some point today. Magisk Manager still says that Magisk is installed, but that I am "not rooted." Any ideas? Should I try to reflash Magisk or will that trip SafetyNet?
I have a blu r1 hd custom build v6.5 I have tried to install magisk manager (i have rooted with super su) but it fails every time I try I get an error message I'm the app and in TWRP I just want to know if anybody else has this problem and if there is any way to solve it
Jô$èph D said:
I have a blu r1 hd custom build v6.5 I have tried to install magisk manager (i have rooted with super su) but it fails every time I try I get an error message I'm the app and in TWRP I just want to know if anybody else has this problem and if there is any way to solve it
Click to expand...
Click to collapse
I believe Magisk dropped SuperSu support at some point before v13. Magisk now includes its own systemless root solution, so SuperSu is not needed. Try uninstalling Magisk and SuperSu and flashing the latest 13.3 zip.
freespeechdev said:
I believe Magisk dropped SuperSu support at some point before v13. Magisk now includes its own systemless root solution, so SuperSu is not needed. Try uninstalling Magisk and SuperSu and flashing the latest 13.3 zip.
Click to expand...
Click to collapse
Ok then ill give it a shot
freespeechdev said:
I believe Magisk dropped SuperSu support at some point before v13. Magisk now includes its own systemless root solution, so SuperSu is not needed. Try uninstalling Magisk and SuperSu and flashing the latest 13.3 zip.
Click to expand...
Click to collapse
I need to get stock boot img I don't have it pls help
Jô$èph D said:
I need to get stock boot img I don't have it pls help
Click to expand...
Click to collapse
Two options:
If you have a pre-supersu/Magisk backup, restore it (at least the boot part).
If you don't have a backup (I encourage you to make them in the future...):
You need to go to the forum post with the fixed prime 6.5 zip downloads. Download the ~1gb zip, unzip it, and grab the boot.img from there. Flash it in twrp by going to install, install image (bottom right). Choose boot. When the flash finishes, reboot to recovery and flash Magisk.
freespeechdev said:
Two options:
If you have a pre-supersu/Magisk backup, restore it (at least the boot part).
If you don't have a backup (I encourage you to make them in the future...):
You need to go to the forum post with the fixed prime 6.5 zip downloads. Download the ~1gb zip, unzip it, and grab the boot.img from there. Flash it in twrp by going to install, install image (bottom right). Choose boot. When the flash finishes, reboot to recovery and flash Magisk.
Click to expand...
Click to collapse
Can you pls link me the post for that file
freespeechdev said:
Two options:
If you have a pre-supersu/Magisk backup, restore it (at least the boot part).
If you don't have a backup (I encourage you to make them in the future...):
You need to go to the forum post with the fixed prime 6.5 zip downloads. Download the ~1gb zip, unzip it, and grab the boot.img from there. Flash it in twrp by going to install, install image (bottom right). Choose boot. When the flash finishes, reboot to recovery and flash Magisk.
Click to expand...
Click to collapse
Never mind man. I can't say thank you enough I found the stock ROM with the info you gave me. Flashing boot.img was successful and so was flashing the Magisk.zip again thanks
Jô$èph D said:
Never mind man. I can't say thank you enough I found the stock ROM with the info you gave me. Flashing boot.img was successful and so was flashing the Magisk.zip again thanks and I will stay active on this and other threads
Click to expand...
Click to collapse
Sure thing. See you around!
Why would someone use Magisk instead of traditional root? Are there some apps that you need to use that won't work on the rooted phone? I guess that there are a few, like snap chat and maybe Netflix but I don't use those on the Blu R1 HD.
I followed Colton's original root thread and while he, at first, included Magisk, he later advised switching to the non-Magisk root and I did. What would I gain by switching back to Magisk?
yaconsult said:
Why would someone use Magisk instead of traditional root? Are there some apps that you need to use that won't work on the rooted phone? I guess that there are a few, like snap chat and maybe Netflix but I don't use those on the Blu R1 HD.
I followed Colton's original root thread and while he, at first, included Magisk, he later advised switching to the non-Magisk root and I did. What would I gain by switching back to Magisk?
Click to expand...
Click to collapse
I wanted to use systemless xposed framework because the official version is not supported on my device. Also I wanted to use the modules that are specifically for magisk
yaconsult said:
Why would someone use Magisk instead of traditional root? Are there some apps that you need to use that won't work on the rooted phone? I guess that there are a few, like snap chat and maybe Netflix but I don't use those on the Blu R1 HD.
I followed Colton's original root thread and while he, at first, included Magisk, he later advised switching to the non-Magisk root and I did. What would I gain by switching back to Magisk?
Click to expand...
Click to collapse
Systemless xposed does not work either found this out earlier today device would not boot after installation of xposed through magisk
Ah, that would be a problem for me. I wouldn't want to use a phone without xposed. I have to have all the tweaking and customizations available in gravitybox and a few other modules.
So what will you do now? Give up xposed or Magisk? Or try to find or wait for a version of xposed that works on Magish?
It was a long time ago, but I think I remember running into problems running xposed on Magisk and Colton provided some helpful advice in his original thread about reflashing the rom, getting root, then installing xposed - he had seperate threads for those.
yaconsult said:
Ah, that would be a problem for me. I wouldn't want to use a phone without xposed. I have to have all the tweaking and customizations available in gravitybox and a few other modules.
So what will you do now? Give up xposed or Magisk? Or try to find or wait for a version of xposed that works on Magish?
It was a long time ago, but I think I remember running into problems running xposed on Magisk and Colton provided some helpful advice in his original thread about reflashing the rom, getting root, then installing xposed - he had seperate threads for those.
Click to expand...
Click to collapse
I will have to see if it works when a new version of magisk is launched.
Got Xposed working on stock .118, thanks, (again), to the work of @lubik1. His original thread for X here- https://www.google.com/url?sa=t&sou...ADAAegQIBRAF&usg=AOvVaw3YZij6LUWGDk3w4JrQ3xmQ Same zip works for XC. All I did was use SuperR's kitchen to make deodex patch.
Instructions, (this is what I did - you may not need it all):
1. Download 3 zips attached, plus Magisk, and these:
118 deodex zip - https://mega.nz/#!dkdGnK7b!VMgKwV4XIooO5erGsIQsKaK-ceEw9ZlIM67XLe74flg
Xposed fix - https://mega.nz/#!R5VWVQBY!ef9EgV4ca5F_az30w86jyUIgox1nhZmV5HX95khyNgM
2. Start from clean stock .118
3. Flash deodex zip and wipe, and boot phone until you get to home screen
4. Boot to recovery, and flash zips. I don't know if the order matters, but I did them all at once using 'add more zips' function in TWRP in this order - Xposed, Magisk, SELinux, safetynet, busybox.
- - note, when selinux is installing, watch for prompt. First press volume up when prompted, then press volume down to set permissive.
5. Reboot, and open Xposed manager, and choose install. It will install framework and reboot.
Done
See next post for init.d tweaks...
Init.d
When rebooting after all that, phone might be laggy. Download attached zips and flash in recovery.
Again, thanks to lubik1. Scripts came from his eXistenZ rom port.
Credit to @Zackptg5 for init.d injector - https://forum.xda-developers.com/android/software-hacking/mod-universal-init-d-injector-wip-t3692105
levone1.
Install is mandatory!
1-clean [118] flash
2-magisk 3 formula
3-118 deodexed flash zip+wipe
4-Wait until the phone opens.
5-twrp xposed flash.
(then others flash zip. Is it true)
thank you.
eymentuna said:
levone1.
Install is mandatory!
1-clean [118] flash
2-magisk 3 formula
3-118 deodexed flash zip+wipe
4-Wait until the phone opens.
5-twrp xposed flash.
(then others flash zip. Is it true)
thank you.
Click to expand...
Click to collapse
I flashed deodex then Xposed then Magisk, and worked also. Glad it's working for you...
Xposed ok
I've been able to use your deodexed rom and files to upgrade from a 34.4.A.2.70 version+magisk already installed. And now, Xposed seems to be working. Thanks for sharing this wonderful update
Fingerprintreader ?
In the 118 deodex zip fingerprintreader is not included - right ?
Johnny Babetto said:
In the 118 deodex zip fingerprintreader is not included - right ?
Click to expand...
Click to collapse
not included brother
*https://forum.xda-developers.com/x-compact/themes/existenz-xc-t3867917
*CE1_118_DEODEX*included
*thank You @levone1
eymentuna said:
not included brother
*https://forum.xda-developers.com/x-compact/themes/existenz-xc-t3867917
*CE1_118_DEODEX*included
*thank You @levone1
Click to expand...
Click to collapse
SO will CE1_118_DEODEX work on XC?
I need these combination at same time:
- 2.118 ROM
-Magisk
-Xposed
-Fingerprint
hnodet said:
SO will CE1_118_DEODEX work on XC?
Click to expand...
Click to collapse
*Yes it works:good:
*load with peace of mind
please confirm these steps:
eymentuna said:
*Yes it works:good:
*load with peace of mind
Click to expand...
Click to collapse
1- clean flash 2.118
2-flash modded boot img for 2.118 (fastboot)
3- flash twrp (fastboot)
4- flash CE1_118_DEODEX and wipe and reboot until see home screen (twrp)
5-flash Xposed (fixed version) , Magisk, SELinux, safetynet, busybox (twrp)
6- flash Drm fix (twrp)
7- flash Init.d_Injector-v1.7.2.zip and initd.zip
Right?
currently I'm in 2.19 with magisk, xposed (systemless), and flashed serajr's DRM fix (I haven't backed up TA )
you can give the right start
hnodet said:
1- clean flash 2.118
2-flash modded boot img for 2.118 (fastboot)
3- flash twrp (fastboot)
4- flash CE1_118_DEODEX and wipe and reboot until see home screen (twrp)
5-flash Xposed (fixed version) , Magisk, SELinux, safetynet, busybox (twrp)
6- flash Drm fix (twrp)
7- flash Init.d_Injector-v1.7.2.zip and initd.zip
Right?
currently I'm in 2.19 with magisk, xposed (systemless), and flashed serajr's DRM fix (I haven't backed up TA )
Click to expand...
Click to collapse
1- flash 2.118
2- flash twrp 3.2.3.2
3- flash CE1_118_DEODEX
4- wipe cache/dalvik
5-reboot>>>>>>>>>>>>bootloop
6- flash modded boot img >>>>>>>>>>>>>>> stuck on logo!
1-deodex flash
2-drm fix flah
3- wait until the phone turns on
eymentuna said:
1-deodex flash
2-drm fix
3- wait until the phone turns on
Click to expand...
Click to collapse
I think I did so
(but without drm fix, because it isn't related to the procedure of booting)
when I faced bootloop, I tried flashing modded boot img
the procedure you mentioned results bootloop
....
@levone1,
What are SELinux, safetynet and busybox zips for?
I got Xposed running without installing them. But SafetyNet checks do not pass in Magisk and GPay does not work. Searching returns mixed answers regarding whether a combination of Xposed + Magisk + GPay is ever functional on Android 8.0. Really confusing.
Will installing them fix SafetyNet? If so, can I do it after I already installed Xposed via Xposed installer?
Thank you for your time.
estrizhok said:
@levone1,
What are SELinux, safetynet and busybox zips for?
I got Xposed running without installing them. But SafetyNet checks do not pass in Magisk and GPay does not work. Searching returns mixed answers regarding whether a combination of Xposed + Magisk + GPay is ever functional on Android 8.0. Really confusing.
Will installing them fix SafetyNet? If so, can I do it after I already installed Xposed via Xposed installer?
Thank you for your time.
Click to expand...
Click to collapse
Don't know too much technically, but in general, any system mods that require bypassing stock security functions will use one or more of things like busybox, disabling SELinux, etc, in order for the mods to work properly. This fix isn't my work ; I just adapted it to work on XC. I would say that your chances of things working how you want are definitely better if you flash those zips. Or you can just flash eXistenZ, which includes all of it and more. You probably need to use Magisk hide to get Gpay to work.
levone1 said:
Don't know too much technically, but in general, any system mods that require bypassing stock security functions will use one or more of things like busybox, disabling SELinux, etc, in order for the mods to work properly. This fix isn't my work ; I just adapted it to work on XC. I would say that your chances of things working how you want are definitely better if you flash those zips. Or you can just flash eXistenZ, which includes all of it and more. You probably need to use Magisk hide to get Gpay to work.
Click to expand...
Click to collapse
I assumed you would know the effect of those zip since your post tell us to install them I guess, I will try to install them. I am just wary of breaking the device again.
But GPay aside, does your phone passes Magisk's SafetyNet checks? That's again assuming you did install all of the Xposed, Magisk, SELinux, safetynet, busybox.
P.S. I don't want eXistenZ, I want less stuff installed, not more.
EDIT: The device still boots. That's a a good news. SafetyNet checks still fail. That's bad.
estrizhok said:
I assumed you would know the effect of those zip since your post tell us to install them I guess, I will try to install them. I am just wary of breaking the device again.
But GPay aside, does your phone passes Magisk's SafetyNet checks? That's again assuming you did install all of the Xposed, Magisk, SELinux, safetynet, busybox.
P.S. I don't want eXistenZ, I want less stuff installed, not more.
EDIT: The device still boots. That's a a good news. SafetyNet checks still fail. That's bad.
Click to expand...
Click to collapse
I haven't checked it with this fix, but with eXistenZ, it's working... This is from someone else -
https://forum.xda-developers.com/showpost.php?p=79068881&postcount=155
And attached is my screen shot...
(btw - the only thing you really add with eXistenZ is improvements - you don't have to use any features you don't want)