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)
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.
So, I am on stock 7.1.1 - N6F27C no-root.
-- have unlocked bootloader & latest TWRP installed.
I am wanting to root, but not have SU.... and not really sure how to accomplish that.
-- do i use the Unified Toolkit in "original development" ?
What I am wanting to accomplish:
- Load PureNexus
- use Magisk (to hide root from PokemonGo, and AndroidPay)
I've seen people talk about un-SU, which i don't anything about, as i haven't rooted or modded a phone since my note3, so I am kind of in the dark here.
UPDATE -- after some reading this seems to be what i need to do.... right?
Reboot to twrp
Make backup
Wipe system, data, cache, and dalvik cache.
Flash PureNexus
Flash BeansGapps
Flash Magisk
Flash FrancoKernel & Reboot
Install Magisk Manager & update
is that all correct? (to have PoGo & Pay working?)
Ph0z3 said:
So, I am on stock 7.1.1 - N6F27C no-root.
-- have unlocked bootloader & latest TWRP installed.
I am wanting to root, but not have SU.... and not really sure how to accomplish that.
-- do i use the Unified Toolkit in "original development" ?
What I am wanting to accomplish:
- Load PureNexus
- use Magisk (to hide root from PokemonGo, and AndroidPay)
I've seen people talk about un-SU, which i don't anything about, as i haven't rooted or modded a phone since my note3, so I am kind of in the dark here.
Click to expand...
Click to collapse
If you want to use Magisk, then flashing Magisk will root your device using phh's root. Just download Magisk and flash. Of course, read through the original post and at least the last several pages of the thread.
If you flash PN, beans-gapps (as specified by PN), then Magisk in the same flash que then boot, you should be good to go. The first 4 posts of the PN thread helps with installation instructions.
The primary reason to use osm0sis' unsu.zip is to remove an existing root prior to replacing it with a different one. Not necessary if you're flashing a new ROM, since you'd lose root anyway. Switching roms should always be a clean flash (system, cache, dalvik - not user data which holds your "sdcard" stuff).
ktmom said:
If you want to use Magisk, then flashing Magisk will root your device using phh's root. Just download Magisk and flash. Of course, read through the original post and at least the last several pages of the thread.
If you flash PN, beans-gapps (as specified by PN), then Magisk in the same flash que then boot, you should be good to go. The first 4 posts of the PN thread helps with installation instructions.
Click to expand...
Click to collapse
awesome!
thank you for the rapid reply. :highfive: :good:
Ph0z3 said:
awesome!
thank you for the rapid reply. :highfive: :good:
Click to expand...
Click to collapse
You're welcome. See the edit I made to add info.
ktmom said:
You're welcome. See the edit I made to add info.
Click to expand...
Click to collapse
ok, so lemme make sure i got this 100%
Reboot to twrp
Make stock backup
Wipe system, data, cache, and dalvik cache.
ALL IN ONE QUE:
Flash PureNexus
Flash BeansGapps
Flash Magisk
Flash FrancoKernel & Reboot
Install Magisk Manager & update
I also want to point out, IMHO, hold off switching kernels until you have stuff set up. Then do a backup, flash your new kernel and Magisk again (after the kernel). That's the safest way to keep things headed the right direction.
Flashing Magisk gives you the manager as well.
ktmom said:
I also want to point out, IMHO, hold off switching kernels until you have stuff set up. Then do a backup, flash your new kernel and Magisk again (after the kernel). That's the safest way to keep things headed the right direction.
Flashing Magisk gives you the manager as well.
Click to expand...
Click to collapse
good point.
alright, well i will hold untill i have it all squared and setup, then flash Franco after im all restored and good to go.
thank you again! you kick ass!
Ph0z3 said:
Flash PureNexus
Flash BeansGapps
Flash Magisk
Flash FrancoKernel & Reboot
Install Magisk Manager & update
Click to expand...
Click to collapse
One thing to add. If you install Franco Kernel after flashing Magisk, you'll lose root since Magisk modifies the kernel. Flash Franco Kernel after flashing Beans GApps, then flash Magisk and boot.
one last question...
what about xPosed?
I used to use Amplify a while ago & would like to use that again... will that work with Magisk?
Ph0z3 said:
one last question...
what about xPosed?
I used to use Amplify a while ago & would like to use that again... will that work with Magisk?
Click to expand...
Click to collapse
Xposed doesn't work on nougat. You'll need to go back to marshmallow.
ktmom said:
Xposed doesn't work on nougat. You'll need to go back to marshmallow.
Click to expand...
Click to collapse
Well poo... Anyhoo thank you for all the help.
Personally, I wouldn't bother with Xposed, but to each his own.
Stock Kernel + SafetyNet Patch + DRM Fix
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- This will not prevent SafetyNet from tripping for other reasons, like rooting.
- Now You can use Android Pay with an unlocked bootloader.
Installation:
- Installation using TWRP
- Installation via the bootloader
Code:
fastboot flash boot boot.img
Downloads: Dropbox (E6633,E6653,E6683)
Current version: 32.3.A.2.33 -perf-g1016077
I compiled the stock kernel and applied the SafetyNet patch by sultanxda.
DISCLAIMER:
No one is responsible for any damage caused to your device except You. You have been warned.
TWRP 3.1.1 for Xperia Z5, Z5C, Z3+
Vulkan API for Adreno 430
please port for E6853
anjelz2012 said:
please port for E6853
Click to expand...
Click to collapse
Try the Zach's Kernel, in it the SafetyNet check is partially disabled.
Great work!
delete
Thank you! SafetyNet check passes without errors
But one question: I want to flash recovery afterwards, so i can use (or at least try to use) the magisk root + magisk hide method along with safetynet passed.
I tried different twrp.img (3.0.2 and 3.1.0) for e6653, but no recovery seems to work.
I tried to flash it via "fastboot flash recovery twrp-x.x.x.img" but it does not boot into recovery ("adb reboot recovery" and hotkeys result in a simple system reboot).
I am not sure though, if i have to flash twrp into a different partition than "recovery"?
Thank you in advance.
rrdna said:
I tried different twrp.img (3.0.2 and 3.1.0) for e6653, but no recovery seems to work.
I tried to flash it via "fastboot flash recovery twrp-x.x.x.img" but it does not boot into recovery ("adb reboot recovery" and hotkeys result in a simple system reboot).
I am not sure though, if i have to flash twrp into a different partition than "recovery"?
Thank you in advance.
Click to expand...
Click to collapse
Try to install TWRP 3.1.1.
grayleshy said:
Try to install TWRP 3.1.1.
Click to expand...
Click to collapse
Thanks, 3.1.1 worked for me
rrdna said:
Thanks, 3.1.1 worked for me
Click to expand...
Click to collapse
It's great that TWRP came up and Magisk hides root.
Thanks for the work!!! Any chance for E6633?
christis said:
Thanks for the work!!! Any chance for E6633?
Click to expand...
Click to collapse
If the kernel don't work for You, give me Kernel.sin, then I will do it for E6633.
Thanks for the work. @grayleshy
SIN Files : https://drive.google.com/drive/folders/0B9v3aNFonkyMWlFMbF9yME5EaTg
Did you use sultanxda safetynet patch?
Added kernel for E6633.
sceryavuz said:
Did you use sultanxda safetynet patch?
Click to expand...
Click to collapse
I will soon lay out the source code. There and see, what patch is applied.
Thanks a lot. Can't wait to see the source code! Do you have an eta?
rrdna said:
Thank you! SafetyNet check passes without errors
But one question: I want to flash recovery afterwards, so i can use (or at least try to use) the magisk root + magisk hide method along with safetynet passed.
I tried different twrp.img (3.0.2 and 3.1.0) for e6653, but no recovery seems to work.
I tried to flash it via "fastboot flash recovery twrp-x.x.x.img" but it does not boot into recovery ("adb reboot recovery" and hotkeys result in a simple system reboot).
I am not sure though, if i have to flash twrp into a different partition than "recovery"?
Thank you in advance.
Click to expand...
Click to collapse
I've the same issue...
MichaMichaMicha said:
Can't wait to see the source code!
Click to expand...
Click to collapse
Patch in kernel from @Sultanxda . Patch of may 23.
Earlier I didn't publish information on a patch as checked this patch.
Looks like you're working on an all in-built kernel ?
If you're making an progress towards in-built MHL please, please let us know
The magic seems to be in the configuration or additional patches (I had it working in the SunKernel Corona source)
but it doesn't seem to work out of the box with Sony's source [or I missed something],
anyway:
Keep up the good fight !
rrdna said:
Thank you! SafetyNet check passes without errors
But one question: I want to flash recovery afterwards, so i can use (or at least try to use) the magisk root + magisk hide method along with safetynet passed.
I tried different twrp.img (3.0.2 and 3.1.0) for e6653, but no recovery seems to work.
I tried to flash it via "fastboot flash recovery twrp-x.x.x.img" but it does not boot into recovery ("adb reboot recovery" and hotkeys result in a simple system reboot).
I am not sure though, if i have to flash twrp into a different partition than "recovery"?
Thank you in advance.
Click to expand...
Click to collapse
When you install magisk is the drmfix still active? The last time I installed magisk I was facing issues where I'd get white noise when taking pictures and no post processing being done
Thank you!
Now I can use OTA updates for my Z5!!
The_Miggs said:
Thank you!
Now I can use OTA updates for my Z5!!
Click to expand...
Click to collapse
This is not about OTA. SafetyNet : https://www.howtogeek.com/241012/sa...y-and-other-apps-dont-work-on-rooted-devices/
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.
Quick disclaimer
-I am not the founder of this @Chainfire made this and @joemossjr is the founder of this method.
-I am also not responsible for a raise in gas prices getting cheated on by your wife and a bricked device
So for you that don't know already: "SuHide" is a application which hides root from other apps that detect it (Snapchat, Hulu, banking apps, etc.) And will allow you to use these apps while rooted.
In other words you pass safetynet
PLEASE READ THIS:
AFTER YOU INSTALL "SUHIDE" DO NOT INSTALL XPOSED IT WILL CAUSE A BOOT LOOP WHICH IS UNRECOVERABLE WITH OUT THE STOCK FIRMWARE FLASH
DO NOT INSTALL SYSTEM TWEAKS (PERFORMANCE TWEAKS FLASHED THROUGH TWRP) THEY WILL ALSO CAUSE I BOOTLOOP
**If you do brick your phones here is the link to the stock firmware flash**
T-Mobile: https://drive.google.com/file/d/0B1tqDJm_qQf4YWxreUJSWXJWeVk/view?usp=sharing
Sprint: https://androidfilehost.com/?fid=889964283620761146
-------------------------------------------------------------------------------------
STEPS TO INSTALL:
But what you want to do for root is.
1. Download the configurer. http://download.chainfire.eu/1121/SuperSU/AROMA-SuperSUConfig-v1.00.zip
2. Download the latest SuperSU. http://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
3.Download the latest suhide. http://download.chainfire.eu/1219/suhide/UPDATE-suhide-v1.09-20171001222116.zip
FLASHING
4a. Boot into TWRP
4b. Flash the configure file and chose these options.
1st page= Last option should say 8.0 sbin mode
2nd page=Choose the second option on all sections.
3rd page= leave everything defaulted
5. now after that's done flash SuperSU the suhide. Then boot and it should reboot a few times but it will boot and you will have suhide
6. Open up the new app in your app drawer named "SuHide" and Grant superuser permission
Have Fun
(Tell me if it worked please)
This worked perfectly for me. I am on the stock T-Mobile August build and no longer have to fire up the hotspot and use my old VZW Z Force for Android Pay. Thanks for putting this guide together!
WeUseLord- said:
...
PLEASE READ THIS:
AFTER YOU INSTALL "SUHIDE" DO NOT INSTALL XPOSED IT WILL CAUSE A BOOT LOOP WHICH IS UNRECOVERABLE WITH OUT THE STOCK FIRMWARE FLASH
...
Click to expand...
Click to collapse
Do you think it is related to Suhide presence or to installing SuperSU on /sbin?
(to be clearer, installing SuperSU on /sbin is safe with Xposed?)
enetec said:
Do you think it is related to Suhide presence or to installing SuperSU on /sbin?
(to be clearer, installing SuperSU on /sbin is safe with Xposed?)
Click to expand...
Click to collapse
I honestly do not know I believe the reason is because XPOSED is detected differently than SuperSU which is why it won't work
DarkFalconX said:
This worked perfectly for me. I am on the stock T-Mobile August build and no longer have to fire up the hotspot and use my old VZW Z Force for Android Pay. Thanks for putting this guide together!
Click to expand...
Click to collapse
No problem thanks for clarifying that it works