Hi, I'm using Magisk on my LG G2 with RessurectionRemix 5.7 and am looking to update to the Nougat version 5.8. I want to start clean, so will wipe system before the update, but will I have to flash Magisk again after that? What are the steps here, flash the ROM + gapps, unroot, flash Magisk?
de.er said:
Hi, I'm using Magisk on my LG G2 with RessurectionRemix 5.7 and am looking to update to the Nougat version 5.8. I want to start clean, so will wipe system before the update, but will I have to flash Magisk again after that? What are the steps here, flash the ROM + gapps, unroot, flash Magisk?
Click to expand...
Click to collapse
Yep that should be about it. To be sure try safetynet after unrooting and after magisk
guessingagain said:
Yep that should be about it. To be sure try safetynet after unrooting and after magisk
Click to expand...
Click to collapse
Flashed the ROM and magisk last night, so far so good, safetynet passes I went for a clean install this time, but if I was to dirty flash an update now would magisk survive that?
de.er said:
Flashed the ROM and magisk last night, so far so good, safetynet passes I went for a clean install this time, but if I was to dirty flash an update now would magisk survive that?
Click to expand...
Click to collapse
No because Magisk modifies the boot image, which gets overwritten with a new one when you flash a ROM, clean or dirty. So you'll need to flash Magisk again.
The Flash said:
No because Magisk modifies the boot image, which gets overwritten with a new one when you flash a ROM, clean or dirty. So you'll need to flash Magisk again.
Click to expand...
Click to collapse
Was suspecting this might be the case, thanks for clarifying this. At least I know all the steps now, should be only getting more familiar with every flash
de.er said:
Flashed the ROM and magisk last night, so far so good, safetynet passes I went for a clean install this time, but if I was to dirty flash an update now would magisk survive that?
Click to expand...
Click to collapse
afaik Resurrection Remix has addon.d (check if /system/addon.d exists)
you can test this https://github.com/osm0sis/GN-Synap...mdisk/res/synapse/scripts/999-customkernel.sh or modify it to flash magisk instead of the backup (in case you got an updated kernel)
crusader727 said:
afaik Resurrection Remix has addon.d (check if /system/addon.d exists)
you can test this https://github.com/osm0sis/GN-Synap...mdisk/res/synapse/scripts/999-customkernel.sh or modify it to flash magisk instead of the backup (in case you got an updated kernel)
Click to expand...
Click to collapse
wow, that'd be great if it worked. I can confirm addon.d exists, I might try this next time. Do I just put the script into addon.d and flash ROM?
de.er said:
Do I just put the script into addon.d and flash ROM?
Click to expand...
Click to collapse
yes :good:
//btw:
yesterday I posted a feature request to add this to Magisk Manager: https://github.com/topjohnwu/MagiskManager/issues/72
crusader727 said:
yes :good:
//btw:
yesterday I posted a feature request to add this to Magisk Manager: https://github.com/topjohnwu/MagiskManager/issues/72
Click to expand...
Click to collapse
Flashed an RR update to 5.8.1 over the weekend and it went smoother than I expected, to be honest. Didn't use the script you mentioned in the end, just flashed the new ROM, gapps, unsu.zip, magisk and phh's su in TWRP and rebooted. Simple.
de.er said:
Flashed an RR update to 5.8.1 over the weekend and it went smoother than I expected, to be honest. Didn't use the script you mentioned in the end, just flashed the new ROM, gapps, unsu.zip, magisk and phh's su in TWRP and rebooted. Simple.
Click to expand...
Click to collapse
Yes, of course the manual method works :good:
phh-SU was removed in Magisk v11 btw - root is now integrated (MagiskSU).
I still need to have phh's Superuser management app installed. And now on boot I get a notification that my SU binary is out of date. The transition here has been a bit rough.
sweenish said:
I still need to have phh's Superuser management app installed. And now on boot I get a notification that my SU binary is out of date. The transition here has been a bit rough.
Click to expand...
Click to collapse
Are you on about updating your ROM or magisk? Phh su app is required for magisk v10.2, you need to remove it if you're using magisk v11 or later
The Flash said:
No because Magisk modifies the boot image, which gets overwritten with a new one when you flash a ROM, clean or dirty. So you'll need to flash Magisk again.
Click to expand...
Click to collapse
In reference to this, does reflashing Magisk alter anything within Magisk? Namely and really the only thing that would come to mind is it downgrading the Manager app to whatever is in the installer and possibly resetting it settings.
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.
Hey,
I've been trying to install Magisk and it asks me to have SuperSU installed before I do, which I don't want. How do I install MagiskSU or even Magisk if it asks me to install SuperSU?...
Thanks
Keagel said:
Hey,
I've been trying to install Magisk and it asks me to have SuperSU installed before I do, which I don't want. How do I install MagiskSU or even Magisk if it asks me to install SuperSU?...
Thanks
Click to expand...
Click to collapse
Try flashing Magisk in recovery.
jhedfors said:
Try flashing Magisk in recovery.
Click to expand...
Click to collapse
It's what I did, that's where it tells me to install SuperSU first :/
Keagel said:
It's what I did, that's where it tells me to install SuperSU first :/
Click to expand...
Click to collapse
Can you give more details? What ROM, Magisk version, logs, etc?
I would suggest flashing osmOsis's UnSU zip, then Magisk v11.2.
Keagel said:
Hey,
I've been trying to install Magisk and it asks me to have SuperSU installed before I do, which I don't want. How do I install MagiskSU or even Magisk if it asks me to install SuperSU?...
Thanks
Click to expand...
Click to collapse
Your boot image is pre-patched for SuperSU. Flash a clean boot image.
Yeah I found the original boot.img of the stock rom my rom is based on and flashed it and it fixed it! Thanks guys
how to find the original boot.img?
ydstark23 said:
how to find the original boot.img?
Click to expand...
Click to collapse
in twirp
restore> select correct folder > check boot > flash
ydstark23 said:
how to find the original boot.img?
Click to expand...
Click to collapse
In the ROM zip.
In case it has built-in superuser, I would suggest flashing osmOsis's unsu zip as well.
Is MagiskSU just another name for Magisk? A module I want to install has the following requirements:
Requirements:
Magisk v13.x/14.0
MagiskSU
I have Magisk v14.5 installed so does that mean I automatically have MagiskSU or is that something additional I have to add?
alryder said:
Is MagiskSU just another name for Magisk? A module I want to install has the following requirements:
Requirements:
Magisk v13.x/14.0
MagiskSU
I have Magisk v14.5 installed so does that mean I automatically have MagiskSU or is that something additional I have to add?
Click to expand...
Click to collapse
That requirement is probably a remnant from when Magisk also was compatible with SuperSU. It's not anymore, so when installing Magisk you get MagiskSU along with it.
Didgeridoohan said:
That requirement is probably a remnant from when Magisk also was compatible with SuperSU. It's not anymore, so when installing Magisk you get MagiskSU along with it.
Click to expand...
Click to collapse
Thanks! I was confused by that and I couldn't find a good answer when searching. Your help is greatly appreciated!
Oddly, I don't have any root after installing Magisk v15 via recovery. Magisk is working, integrity tests are both green, can install all the modules with no problem and integrity tests are still green, but no root.
Interesting, isn't it?
How i know i've got magiskSU?
Leogur said:
How i know i've got magiskSU?
Click to expand...
Click to collapse
Did you install magisk? Or is it included in your rom? Do you see magisk manager app?
Yes i've. But i still can't fix safetynet problem.
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.
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.