So after having a metric f**k ton of issues trying to get a custom recovery to work on 6.0.1, I gave up trying to install a custom rom and eventually went back to stock unrooted. After updating to 7.0 and waiting a bit, I gave it another go and managed to get TWRP to work and rooted my phone. Now I'm looking to install a custom ROM and have a few questions.
Is there anything I should know before going in? Any prerequisites I need to get before/after flashing a custom ROM so certain features will work?
Can I use any custom ROM that is listed as compatible with 7.0/G925F? Or do I have to be more specific as to what version I get?
What should I keep an eye out for? Any features that are good/bad?
Anything else I should know?
As for my choices, it's currently between Nemesis and Noble. Anyone used either and care to share your experience? Any other recommendations?
ProdigyThirteen said:
So after having a metric f**k ton of issues trying to get a custom recovery to work on 6.0.1, I gave up trying to install a custom rom and eventually went back to stock unrooted. After updating to 7.0 and waiting a bit, I gave it another go and managed to get TWRP to work and rooted my phone. Now I'm looking to install a custom ROM and have a few questions.
Is there anything I should know before going in? Any prerequisites I need to get before/after flashing a custom ROM so certain features will work?
Can I use any custom ROM that is listed as compatible with 7.0/G925F? Or do I have to be more specific as to what version I get?
What should I keep an eye out for? Any features that are good/bad?
Anything else I should know?
As for my choices, it's currently between Nemesis and Noble. Anyone used either and care to share your experience? Any other recommendations?
Click to expand...
Click to collapse
The first and most important thing to do is make a backup. A nandroid backup is fine but make sure you back up your EFS folder. If this gets corrupted you will corrupt your IMEI and have no signal permanently. So backup efs and store somewhere safe like your pc.
I recommend doing full wipe before installing a custom ROM just so it's a clean install.
After that your pretty much good to go.
You can use any ROM that's compatible for your model only. So any G925F ROMs will work fine. Most support a number of models like G925F/I/V etc.
Most s6 edge custom ROMs are stable and have very few issues, and if there are issues then generally there are fixes for them.
Nemesis and Noble are both good stable ROMs. Also Omega ROM is a good choice. But my favourite that I used for over a year is CarHD ROM. It's customisation is endless.
One more is AlexisROM. Good ROM used for a while.
Hope this helps.
callumbr1 said:
snip
Click to expand...
Click to collapse
So after a painfully long download, I installed CarHD and I'm liking everything I see. My only issue is trying to get SafetyNet to pass. I've removed SuperSU, installed Magisk and its kernel and now whenever I check SafetyNet, it fails with "CTS profile mismatch". I've looked around on a few different threads about it and everything I've tried hasn't worked. Mostly because they revolve around MagiskHide, which isn't showing up for me.
My first thought is to completely uninstall magisk, go back to a stock kernel and start off fresh, but I'm not going to do that just yet as I wanted your opinion first. Is that the best thing to do or would it cause more harm than good?
And if it wasn't already obvious, yes I'm still pretty damn new to this, but I'm trying not to **** up as I quite like my phone working.
Edit: solved the MagiskHide not showing.. I'm an idiot and forgot it was under settings and not enabled by default.
ProdigyThirteen said:
So after a painfully long download, I installed CarHD and I'm liking everything I see. My only issue is trying to get SafetyNet to pass. I've removed SuperSU, installed Magisk and its kernel and now whenever I check SafetyNet, it fails with "CTS profile mismatch". I've looked around on a few different threads about it and everything I've tried hasn't worked. Mostly because they revolve around MagiskHide, which isn't showing up for me.
My first thought is to completely uninstall magisk, go back to a stock kernel and start off fresh, but I'm not going to do that just yet as I wanted your opinion first. Is that the best thing to do or would it cause more harm than good?
And if it wasn't already obvious, yes I'm still pretty damn new to this, but I'm trying not to **** up as I quite like my phone working.
Click to expand...
Click to collapse
You don't need any kind of custom kernel to use magisk, or at least you shouldn't. It should work perfectly fine with stock.
Try updating magisk manager app from xda labs and magisk hide should appear.
If it does then just enable magisk hide and hide all apps that require safety net, hide knox also if it's still on the ROM. Then you should pass.
If this fails I recommend to flash the ROM again, no need to wipe data and then choose magisk in aroma installer and flash again.
Let me know if you need help :good:
callumbr1 said:
You don't need any kind of custom kernel to use magisk, or at least you shouldn't. It should work perfectly fine with stock.
Try updating magisk manager app from xda labs and magisk hide should appear.
If it does then just enable magisk hide and hide all apps that require safety net, hide knox also if it's still on the ROM. Then you should pass.
If this fails I recommend to flash the ROM again, no need to wipe data and then choose magisk in aroma installer and flash again.
Let me know if you need help :good:
Click to expand...
Click to collapse
Fixed the MagiskHide issue, but simply enabling hide on the apps that I want to use doesn't work. I tried reinstalling the ROM as you said, but it never gave the option to choose Magisk over SuperSU. Then when I switched from SuperSU to Magisk, SuperSU was removed normally, but Magisk is installed and saying I don't have root access. Flashed Magisk kernel from CarHD as TWRP wasn't allowing install of Magisk with the other that came stock, then flashed Magisk again. Magisk saying I now have root access, but Magisk isn't installed and when I try to install it, the app crashes. Currently checking Magisk threads for a solution for that.
Tried reinstalling Magisk and clearning data/cache to no avail... I still have root access, but can't install Magisk through the manager.
Uninstalled Magisk, flashed stock kernel, re flashed magisk and now SafetyNet is passing, but still can't install Magisk through the Manager
ProdigyThirteen said:
Uninstalled Magisk, flashed stock kernel, re flashed magisk and now SafetyNet is passing, but still can't install Magisk through the Manager
Click to expand...
Click to collapse
If you have root access and safety net pass then I don't understand what you mean by can't install magisk through the app?
So you have magisk manager app installed?
callumbr1 said:
If you have root access and safety net pass then I don't understand what you mean by can't install magisk through the app?
So you have magisk manager app installed?
Click to expand...
Click to collapse
Yeah, the manager is installed, but when I open it, it says there is an update available and under status says Magisk is not installed, v130 is available. There is no option to enable Magisk hide or any other extras available for download.
Screenshot of magisk
ProdigyThirteen said:
Screenshot of magisk
Click to expand...
Click to collapse
It's the magisk manager app. You need to install the new one. Delete the one you currently have installed and download latest one from magisk Thread here or from xda labs.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Should look similar to this.
callumbr1 said:
It's the magisk manager app. You need to install the new one. Delete the one you currently have installed and download latest one from magisk Thread here or from xda labs.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Should look similar to this.
Click to expand...
Click to collapse
Tried to uninstall it, no option to. Downloaded something to uninstall system apps, tried to uninstall it, still there. Tried to install a new app over it, gave an error saying app already installed with same name.
ProdigyThirteen said:
Tried to uninstall it, no option to. Downloaded something to uninstall system apps, tried to uninstall it, still there. Tried to install a new app over it, gave an error saying app already installed with same name.
Click to expand...
Click to collapse
You should be able to uninstall it with titanium backup or any app to remove system app.
Infact you should be able to just remove it as you would remove any other app.
Use what you used before to remove it when it didn't go and then reboot and it should go. If not flash the uninstaller from magisk thread.
Then start again, if you flash the newest magisk from the thread on here then it also should install newest magisk manager app.
callumbr1 said:
You should be able to uninstall it with titanium backup or any app to remove system app.
Infact you should be able to just remove it as you would remove any other app.
Use what you used before to remove it when it didn't go and then reboot and it should go. If not flash the uninstaller from magisk thread.
Then start again, if you flash the newest magisk from the thread on here then it also should install newest magisk manager app.
Click to expand...
Click to collapse
No app that removes system apps can remove Magisk Manager it seems... TB says "Failed to locate the apk file", NoBloat Free says it removed it, but even after rebooting it's still there. Flashing the uninstall doesn't remove it either. I would manually uninstall through root explorer, but there's a risk I delete the wrong file and screw something else up.
Edit: Found Magisk Manger in root/system/app/magisk, backed it up, deleted it, rebooted, seems to be gone. Will try intalling new APK
Fixed it. Had to manually delete the apk, then installed the updated version and now it's showing as magisk is installed perfectly fine. Thanks for all the help.
Third and hopefully final edit: Getting kernel is not seandroid enforcing. Tried uninstalling magisk, flashing stock kernel, reinstalling magisk and still getting it. But it doesn't seem to be messing with anything, can still boot fine, safetynet is still passing so all looks pretty good.
callumbr1 said:
snip
Click to expand...
Click to collapse
No point starting a new thread when I can just ask here as it's a somewhat follow on question. I can't seem to get V4A to work. I've installed the module from Magisk, installed the APK, restarted my phone, loaded up the app and checked the driver just for it to say Status: Abnormal / Audio Format: Unsupported. Can't seem to find anything about a fix for it, been searching for about an hour, so either I'm blind or there's nothing on it (I'm betting it's the former).
When I open the app, I get a message prompting me to update/install the driver, despite it already being installed through Magisk. I've tried both the standard v2.5.0.5 apk and Nougat test fix, standard doesn't do anything and test fix has update/install prompt.
ProdigyThirteen said:
No point starting a new thread when I can just ask here as it's a somewhat follow on question. I can't seem to get V4A to work. I've installed the module from Magisk, installed the APK, restarted my phone, loaded up the app and checked the driver just for it to say Status: Abnormal / Audio Format: Unsupported. Can't seem to find anything about a fix for it, been searching for about an hour, so either I'm blind or there's nothing on it (I'm betting it's the former).
When I open the app, I get a message prompting me to update/install the driver, despite it already being installed through Magisk. I've tried both the standard v2.5.0.5 apk and Nougat test fix, standard doesn't do anything and test fix has update/install prompt.
Click to expand...
Click to collapse
Good stuff. As for the seandroid message on boot you can just ignore it. It's not an error and will stay but doesn't affect anything.
As for viper first thing to try is remove the currently installed app and remove it from magisk manager modules.
Install busybox.
Freeze sound alive with titanium backup (don't delete just freeze)
Then flash this through TWRP
https://mega.nz/#!CV5wQYSa!i-V1UvJ_Lh9YoZDPN9rUUXuJNgXWcXRlhBE83fYH7e8
After this if it doesn't work let me know and I'll tell you next steps.
callumbr1 said:
Good stuff. As for the seandroid message on boot you can just ignore it. It's not an error and will stay but doesn't affect anything.
As for viper first thing to try is remove the currently installed app and remove it from magisk manager modules.
Install busybox.
Freeze sound alive with titanium backup (don't delete just freeze)
Then flash this through TWRP
https://mega.nz/#!CV5wQYSa!i-V1UvJ_Lh9YoZDPN9rUUXuJNgXWcXRlhBE83fYH7e8
After this if it doesn't work let me know and I'll tell you next steps.
Click to expand...
Click to collapse
Tried that, still getting abnormal/unsupported.
ProdigyThirteen said:
Tried that, still getting abnormal/unsupported.
Click to expand...
Click to collapse
Now check that magisk module is enabled and the audio modification module is enabled.
You may also need a permissive kernel to get viper to work.
callumbr1 said:
Now check that magisk module is enabled and the audio modification module is enabled.
You may also need a permissive kernel to get viper to work.
Click to expand...
Click to collapse
Googling permissive kernel is just coming back with a bunch of threads saying get a terminal emulator, type su / setenforce 0. Tried that, trips safetynet and doesn't change Viper.
I feel like it's not changing viper because I need it to stick through reboots, enable it, then reboot, but it's not persistent. How would one go about making it stick?
And honestly, is viper really worth all this hassle?
ProdigyThirteen said:
Googling permissive kernel is just coming back with a bunch of threads saying get a terminal emulator, type su / setenforce 0. Tried that, trips safetynet and doesn't change Viper.
I feel like it's not changing viper because I need it to stick through reboots, enable it, then reboot, but it's not persistent. How would one go about making it stick?
And honestly, is viper really worth all this hassle?
Click to expand...
Click to collapse
You can try Hacker kernel
https://forum.xda-developers.com/ga...l-hacker-kernel-s6-universal-t3254487/page234
Or arter kernel
http://arter97.com/browse/exynos7420/kernel/22.0/g925fi/
As for is it worth it? In my opinion yes 100%.
It depends really if you like the stock effects enough. Personally I love music and love been able to customise it. It sounds 10000x better in my opinion.
Hi, I'm running RR 6.0.1. I clean installed, removed built-in root (leaved the phone unrooted). Play Store showed my device as uncertified. Latest Netflix does not work.
I flashed Magisk 14, then this module, and Device Certification section dissapeared. Uninstalled Magisk, now device showed as certified.
Netflix still NOT working. It does show up on Play Store search. Flashed Magisk again, Mario Run seems to work, and also Android Pay.
EDIT: Forgot to say, SafetyNet passes all the time.
But Netflix insists in Incompatible device. May be the unlocked bootloader? Or the custom ROM?
Is there any workaround for this? (Aside from installing old 4.x version of Netflix)
Thanks!
I've installed Netflix on a few devices succesfully, after facing the same issues as you, by downloading the .apk from Netflix directly here: https://help.netflix.com/en/node/57688
Unfortunately, that's 4.16.x version
I'm talking about newer versions
:bump:
Sent from my ONE A2003 using Tapatalk
Same problem! I used to be able to use the latest Netflix from playstore on my stock and even custom Nougat ROMS, but since the Oreo update I can't. It passes Safetynet but Netflix says incompatible. :/
I'm in the same boat. I have a OnePlus 2 running Lineage 13 and unable to run any Netflix app above version 4.16-200147. My device passes SafetyNet and able to run other apps (Super Mario Run, Pokemon GO) without any issue. If I however update my phone to Lineage 14.1, install the same version of Magisk I'm able to run the latest version of Netflix. Personally I prefer Lineage 13 on my device. I'm guessing that the "system" is signed differently???????
I "fixed" it by upgrading to Nougat, RR ROM Rootless + Magisk 14 + Xposed + No Device Check module, nothing specifically activated in Magisk Hide.
+1 4.16 version, anything newer complained about device not supported
running sony xperia z3 compact on omnirom
On LineageOS 16, every version i tried complained about not supporting my device (SM-G920F), except this one: https://m.apkpure.com/netflix/com.netflix.mediaclient/download?from=details
(v6.26.1 build 15 31696)
It's not the latest, but fairly new compared to v4.16
Hello all, I tried search the Q&A threads for any solution to my problem about Google Pay complaining about altered phone.
I have an unlocked US998 V30 variant (Nougat) that I almost never updated till now.
I followed the WTF guide using Magisk 18.0 and 20b KDZ file.
Then afterwards, I downloaded 20e, f, g, h TWRP files and flashed them via TWRP using zip queue.
In the same TWRP proces, I accidentally flashed Magisk 19.3 and that caused my phone to go into bootloop error.
I managed to fix this by going using hardware buttons to go back into TWRP, resetting everything and flashing Magisk 18.0 and the other two verity/rctd zips.
As I am reinstalling and resetting up everything, I had to update Google Play Services for Ebay (and other) apps to work (Not sure if this information is important).
When I got to trying to setup Google Pay, it complains about the phone being rooted and altered in some way.
I've tried removing phone permission from Google Play Service/Store (no go).
I've seen people suggest updating Magisk to 19.x, but I am wary of that after my bootloop fiasco.
Anyone have any suggestions or am I SOL on Google Pay?
At least on my VS996, you can upgrade Magisk outside of TWRP. In other words, have the Magisk Manager update itself, and Magisk directly (I think it's called "Direct Install").
I'm on 19.3 now without issues. This also solves the GPay issue, because nothing would let it work properly on 18.x in my experience... you have to be on 19.x for Gpay to work.
schwinn8 said:
At least on my VS996, you can upgrade Magisk outside of TWRP. In other words, have the Magisk Manager update itself, and Magisk directly (I think it's called "Direct Install").
I'm on 19.3 now without issues. This also solves the GPay issue, because nothing would let it work properly on 18.x in my experience... you have to be on 19.x for Gpay to work.
Click to expand...
Click to collapse
Can anyone else confirm this works with a US 998 Unlocked variant? I am not sure if I should upgrade my Magisk again and go through all that.
techsam2k8 said:
Can anyone else confirm this works with a US 998 Unlocked variant? I am not sure if I should upgrade my Magisk again and go through all that.
Click to expand...
Click to collapse
Yes, it works. As said, update Magisk through the app, IOW, when u boot the phone and Magisk says there's an update, do it.
Also, be sure to have gpay hidden from Magisk, in the 'Magisk Hide' section. Not sure if it matters but I also have google play services and google play store hidden.
Cheers
AsItLies said:
Yes, it works. As said, update Magisk through the app, IOW, when u boot the phone and Magisk says there's an update, do it.
Also, be sure to have gpay hidden from Magisk, in the 'Magisk Hide' section. Not sure if it matters but I also have google play services and google play store hidden.
Cheers
Click to expand...
Click to collapse
FWIW, I did not have the Magisk Hide anything, and Gpay is still working...
As the above mentioned posters said, installing it directly from Magisk Manager worked (19.3)!
However, after I rebooted, SafetyNet was failing and I found out it was due to Systemless Xposed Module.
Uninstalled that through the Magisk Manager, which worked and was able to successfully use Google Pay after hiding Magisk itself.
It is a shame I cannot use both Google Pay and Xposed at the same time.
techsam2k8 said:
It is a shame I cannot use both Google Pay and Xposed at the same time.
Click to expand...
Click to collapse
You can use Xposed and pass Safety Net. There's a guide I wrote.
You have to install THIS version of Xposed (called edXposed), enable it, then download specific Xposed modules which work with it.
Xposed and Safety Net Pass -- How To!
(with Gravity Box links)
There's link for Gravity Box, and you can look in the edXposed repository and see other Xposed mods in which you might be interested.
techsam2k8 said:
Then afterwards, I downloaded 20e, f, g, h TWRP files and flashed them via TWRP using zip queue.
In the same TWRP proces, I accidentally flashed Magisk 19.3 and that caused my phone to go into bootloop error.
Click to expand...
Click to collapse
That was not the issue.
1) If you made a backup in TWRP, all you had to do was delete boot and then restore boot from the backup.
2) You never flashed the Magisk uninstaller before updating magisk. This is a common issues going from V18-V19
Sent from my LG-H932 using XDA Labs