Hello,
I have the Huawei mate 9 with fRomFuture-B197. Magisk App is v5.5.5 with v14.0.
Recently, when I start Magisk, I get the message App Version 5.7.0, the latest version is v16.0
Now my question:
How best to update this without the encryption of the memory reappears. So that's how it is now. Only the magisk is updated.
I have tried it before, but every time the encryption was back, Google Play account was deleted, contacts, SMS as well.
Very important: ExSDCard Write Access Enabler v2.1 and Huawei Property Fix v1.2 must also be present.
Encryption must be kept away so I can use FlashFire. Because TWRP unfortunately makes no backup from the internal memory.
Thank you for your help !!!!
Related
Hey guys, I ask here for help because i'm unable to find a solution to this problem.
Here some information to my device:
OnePlus One
ROM lineage-14.1-20170807-UNOFFICIAL-Sultan-bacon
Root with Magisk v13.3
Magisk Hide is enabled
SafetyNet passed
Playstore shows Certified
No other modules.
Already tried
clearing PlayStore app data and reboot
DRM info from PlayStore, It's says supported.
Super Mario Run and other Apps that blocked for rootet devices appeared after i enabled Magisk Hide and passed SafetyNet, but i still cannot download Netflix.
I hope some of you have the same Problem or a solution for this.
I also dont see netflix on playstore. I live in VIetnam
I'm also experiencing this, tried with a couple of roms and it's the same on all of them. I think that maybe it's related to our opo that isn't completely eligible for nougat (no stock rom for it also) and google is blocking every opo+nougat regardless of actual safetynet status. It's only my thought though and waiting for a response from someone who knows for sure.
Have you tried PA yet? When I was on that ROM, I can install many apps which not available on Los and other ROM
I was on stock cos13 with magisk and it also didn't show up but it didn't really matter as I just downloaded the apk file
I thinks is on the kernel side that it detect the root , but try to download from apkmirror.com it should work fine
Updated everything to current versions. Still the same problem.
Is there any way to view the exact reasons why my device is not compatible?
This would be very bad.
On my girlfriends phone (Moto G3) everything is working fine. Same gapps and rom setup.
I finally got it working.
My current setup is:
- OnePlus One
- lineage-15.1-20180827-nightly-bacon
- Magisk-v17.0
| - Magisk Hide Enabled
| - Systemless Host Enabled
| - Hide Magisk Manager
- Magisk Module "Google Play Service Fix for Lenovo Vibe K5"
- open_gapps-arm-8.1-micro-20180901
It seems that it is necessary to falsify the device information, as Lisko has already mentioned, the OnePlus One is blocked by the Playstore for Netflix if the Android API is higher than the last official ota.
This is done by the Magisk module mentioned above.
Hi title says all,
If you root your device is it possible to use snapchat?
On my rooted samsung device i was gettting after a few days a temporary ban.
Thanks, ?
Snapchat should work fine. I had one time over this weekend i got banned for 12 hours but at the time my Magisk was crashing from updating without removing substratum theme.
As long as you enable magisk hide and pay attention to updates, you should be fine.
You can use Snapchat if you don't install Xposed, I do know that much. Xposed gives you a temp. ban. There might be a work-around, but if you don't need that, you're good to go anyways
Don't have OP yet , but with other devices I've found that enabling Hide on Magisk for Snapchat actually makes things worse
Do others using Magisk have to enable Hide to use Snapchat?
jcrompton said:
Don't have OP yet , but with other devices I've found that enabling Hide on Magisk for Snapchat actually makes things worse
Do others using Magisk have to enable Hide to use Snapchat?
Click to expand...
Click to collapse
I have always hid Snapchat and Google Pay, along with other Google apps and never had an issue.
I have snapchat and I don't hide it from Magisk.
Sent from my GM1915 using Tapatalk
had issues on my Pixel 3XL
everything works perfectly fine on the OP7Pro
Well after a week rooting my device i was getting issues. But now i dont wanna risk a permanent ban for the sake of rooting ?
How to use Snapchat with magisk (After Ban)
bartjeh1991 said:
Well after a week rooting my device i was getting issues. But now i dont wanna risk a permanent ban for the sake of rooting
Click to expand...
Click to collapse
Follow these steps to use Snapchat with magisk -
1.) Update to latest Magisk stable build v20.0 - https://github.com/topjohnwu/Magisk/releases/download/v20.0/Magisk-v20.0.zip
2.) After updating magisk, Go to Magisk Manager > Magisk Hide and check/enable Snapchat and Google Services (all services have to be marked).
3.) Hide Magisk Manager by it self, go to Magisk Manager > Settings and "Hide Magisk Manager" so it will repack Magisk Manager with random name.
4.) Delete "busybox" binary from /system/xbin directory and install BusyBox module from Magisk Manager > Downloads.
5.) Clear data and cache of Snapchat, try to login this time, it will work for sure, if it doesn't, login to this and click unlock my account - https://accounts.snapchat.com/accounts/login?continue=https://accounts.snapchat.com/accounts/welcome
I have tried this myself and it works, my first main account was permanent banned on magisk canary build, After that I deleted that account and started out with fresh new account.
Tested on -
Samsung Galaxy S9+
Rom - Ultimate Rom v11.3
Magisk - v20.0 (Stable)
Kernel - ElementalX
ricketrash said:
You can use Snapchat if you don't install Xposed, I do know that much. Xposed gives you a temp. ban. There might be a work-around, but if you don't need that, you're good to go anyways
Click to expand...
Click to collapse
You won't get a temp ban with xposed. I'm even using SnapTools (Snapchat modifications) along with xposed and I've been fine for about 3 months now.
Hi all,
Let's tell you my story,
OP6, unlocked, no TWRP, Magisk 20.3 (safetynet is OK) , I used to use my contactless payement app (French Banque populaire app called "Paiement mobile") thanks to Magisk hide, never had to pay more attention to hide root, no need to hide manager, always works with Magisk Hide only.
Updating from OOS 10.3.2 to 10.3.3 and Magisk 20.4.
Everything seems to me fine. I launch once the payement app, no warning.
Thinking about tweaking to make work VoLTE, I tried to find a way to easly save precious data (can't remember the name of the partition name), and finally found that Wanam created an app called "Partition backup and restore" which do that job.
I Installed it and accepted to grant root access.
And at this moment, I got a toast message from my bank app tells me it has detected a security problem.
Since the message, evreytime I open the bank app, it detected the root...
I tried to reinstall it, verify hiding, clear caches, uninstall the partition backup app, contact Wanam, he doesn't understand how his app can reveal the root to my bank app, hide Magisk manager, disable dev mode, oem debug, phone permission to Google Play Services and other, and maybe other things I don't remember... Read so many threads...
My other root-needed apps work.
Rootbear tells me all is OK except BUSYBOX BINARY (can't find something about it).
You're my last chance before getting stock with MSMTool (don't need root anymore).
Thanks in advance guys.
Edit : used Msmtool to go back to stock. No more problem.
Barclays App used to work just fine until about one week ago, when the latest version has been pushed. And they are now switching to an app-only authentication method (no more SMS, no more PINSentry, and definitely not possible through their website). So, if the app can't be used, I will have to either stop using root (which has been really helpful so far), or find a different bank which has an app that works (I believe it's very unlikely).
The Barclays App Version is: 2.73.2 , released in 16/02/2023
Specs:
OnePlus 7
Android 11 (OOS 11.0.2.1GM57BA)
Unlocked Bootloader
TWRP
Rooted with Magisk (25.2):
magisk app hidden
Zygisk enabled
enforce deny list: Enabled (I tried with enabled and disabled)
Deny List:
ALL Google stuff (absolutely anything that had "google" in their name)
Phone (just for safety, I added everything related to phone and dialer)
Barclays App
Magisk Modules:
App Systemizer v17.3.1
Buybox for Android NDK v1.3.4.1
Debloater (Terminal Emulator) v17.3.3
Disable Screenshot Camera Sounds v1.4
Energized Protection v1.3.5
Magisk Hide Props Config v6.12
OnePlus 7 Volume Booster Mod v2
OOS11 Debloater v7
Shamiko v0.6
Systemless Hosts 1.0 (Magisk)
Universal SafetyNet Fix (kdrag0n, modded by Displax) v2.3.1
Play Integrity API Checker:
device integrity: YES
basic integrity: YES
strong integrity: NO
What is happening:
Barclays App is starting
It prompts for registration (asks to set up a PIN)
Throws Error 00006 (which, after some research, seems to be related to Root)
What I did:
Looked for TWRP folder to delete it (I couldn't find it, perhaps I deleted it in the past, however if you can point me to all possible locations where it could be, I'd greatly appreciate it)
Tried both Shamiko and Universal SafetyNet Fix
Deleted storage, cache, from google, barclays, reboot, even uninstalled and reinstalled apps, all the works...
I tried with both Enforce Deny List Enabled and Disabled
Nothing of the above helped with making Barclays App work. Any Suggestions?
Best option atm is use the last version of the Barclays app which still worked (2.72.2) and disable auto update.
Any official way to get the 2.27.2 version? Obviously, because is a banking app, I don't trust mirrors and unofficial repos.
Thanks.
derei said:
Any official way to get the 2.27.2 version? Obviously, because is a banking app, I don't trust mirrors and unofficial repos.
Thanks.
Click to expand...
Click to collapse
https://barclays-bank-plc-banking.en.uptodown.com/android/download/90801956
That is the one I used. I understand your concerns, I was in the same boat before I downloaded it.. But I really need the app working myself. Worked fine though..
As we known when samsung phone is rooted then Knox is tripping so multi user with a work profile isn't possible with the error message... can't create work profile.
This is howto guide to bypass Knox security so Shelter works on it, after many tries and errors methode
My setup
- S20 magisk zygisk root android 13
- Magisk modules: lsposed, knoxpatch apk and enhancer (in lsposed), shamiko as blacklist mode, safetynet fix
- Shelter
Guide
- Root your samsung phone with zygisk magisk (25.2) and install those magisk modules. Reboot several times
- In Lsposed enable KnoxPatch module with suggested Recommended. Reboot
- In Magisk Settings change Multiuser Mode > Device Owner Managed (using in multi user profile)
- In Magisk Settings change Mount Namespace Mode > Inherit namespace. Reboot
- Install Shelter and create work profile following Setup Wizard
- Clone the needed apps to Work profile or install directly from Shelter Work Profile
- In Magisk configure DenyList with those apps in work profile
My rooted S20 works fine in Work Profile with my company apps Microsoft Authenticator, Company Portal, Outlook, Teams etc.
Hope it helps for you guys too.
Further process how to make company apps work on Work Profile created by Shelter/ Island needs follow steps
- Install Applist Detector to check root
- Install InitrcHider (zygisk version) in Magisk
- In Magisk configure DenyList with full denying for those company apps (ticks all processes)
- Uninstall Magisk from Settings/ Apps, not directly from Magisk! because if doing it from Magisk then you loose the root
- Check root again with AppList Detector
- Delete company apps data and cache from Settings/ Apps then setup those apps again as new
gsmdb said:
As we known when samsung phone is rooted then Knox is tripping so multi user with a work profile isn't possible with the error message... can't create work profile.
This is howto guide to bypass Knox security so Shelter works on it, after many tries and errors methode
My setup
- S20 magisk zygisk root android 13
- Magisk modules: lsposed, knoxpatch apk and enhancer (in lsposed), shamiko as blacklist mode, safetynet fix
- Shelter
Guide
- Root your samsung phone with zygisk magisk (25.2) and install those magisk modules. Reboot several times
- In Lsposed enable KnoxPatch module with suggested Recommended. Reboot
- In Magisk Settings change Multiuser Mode > Device Owner Managed (using in multi user profile)
- In Magisk Settings change Mount Namespace Mode > Inherit namespace. Reboot
- Install Shelter and create work profile following Setup Wizard
- Clone the needed apps to Work profile or install directly from Shelter Work Profile
- In Magisk configure DenyList with those apps in work profile
My rooted S20 works fine in Work Profile with my company apps Microsoft Authenticator, Company Portal, Outlook, Teams etc.
Hope it helps for you guys too.
Click to expand...
Click to collapse
Does the above steps really working bro?
Please help me bro
Device Details:
Samsung S10
Custom ROM: One UI 5.1 android 13 by Ivan_meler
Issue: unable to use intune company portal and Island
Please guide me how to do it bro. The above instruction not working for me bro
Did it work for you to install Island?
The scoop is how to make Shelter/ Island/ Insular work with rooted Samsung.
Further process how to make company apps work on Work Profile created by Shelter/ Island needs follow steps
- Install Applist Detector to check root
- Install InitrcHider (zygisk version)
- In Magisk configure DenyList with full denying for those company apps (ticks all processes)
- Uninstall Magisk from Settings/ Apps, not directly from Magisk (important!) because if doing it from Magisk then you loose the root
- Check root again with AppList Detector
- Delete company apps data and cache from Settings/ Apps then setup those apps again as new
Thanks for your reply bro
My first issue is that when i try to install shelter or island it starts, loads and restarts automatically bro
Rooted, installed above modules and followed the instruction bro.
Are you sure your Knox works? Samsung Health, Biometrics, Samsung Pass etc?
It looks like you've trouble with Knox.
You can try enable multi user (per default disabled in Samsung) either using Firefds Kit module in Lsposed or edit the build.prop with
#Multi user
fw.max_users=3
fw.show_multiuserui=1
I have attached the screenshots bro. Please check. Yea even i think knox is not working it is tripped and i m using custom rom bro. If i use intune on main profile it says you need to enable encryption and in island profile it is not even registering profile. Samsung pass doesnt work bro...other samsung apps works properly when i use lsposed knox enhancer bro
My knox is tripped too because unlocking bootloader.
I'm using stock ROM with custom kernel rooted with magisk. The phone is still encrypted.
Your case is using a decrypted ROM. You can search in xda flashing custom ROM without decryption.
The official twrp doesn't decrypt the data partition, the biggest catch will be that you will not have the data partition in a twrp backup. But apart from that, twrp will still work for installs and updates and backups og the system and cache partitions.
Use smart switch doing backup in stead.
gsmdb said:
My knox is tripped too because unlocking bootloader.
I'm using stock ROM with custom kernel rooted with magisk. The phone is still encrypted.
Your case is using a decrypted ROM. You can search in xda flashing custom ROM without decryption
Click to expand...
Click to collapse
Can u suggest any rom bro?
MY device is S10, and dont want to use pixel or different rom , want only one ui ported rom bro android 13
gsmdb said:
My knox is tripped too because unlocking bootloader.
I'm using stock ROM with custom kernel rooted with magisk. The phone is still encrypted.
Your case is using a decrypted ROM. You can search in xda flashing custom ROM without decryption.
The official twrp doesn't decrypt the data partition, the biggest catch will be that you will not have the data partition in a twrp backup. But apart from that, twrp will still work for installs and updates and backups og the system and cache partitions.
Use smart switch doing backup in stead.
Click to expand...
Click to collapse
How to do it bro using smart switch
You can still use One UI5.1 ivan_meler custom ROM. Nothing wrong with it.
You must flash stock ROM first to get back encrypted. Set it up until your phone is working.
Flash twrp and get custom ROM on external SD card.
Follow your own process to flash custom ROM with twrp.
In twrp do wipe dalvik and cache as usual. DON'T format Data. Doing it will get your phone decrypted.
Install your custom ROM.
I did it as remembered back to the days with my old s10 with custom ROM android 10.
gsmdb said:
You can still use One UI5.1 ivan_meler custom ROM. Nothing wrong with it.
You must flash stock ROM first to get back encrypted. Set it up until your phone is working.
Flash twrp and get custom ROM on external SD card.
Follow your own process to flash custom ROM with twrp.
In twrp do wipe dalvik and cache as usual. DON'T format Data. Doing it will get your phone decrypted.
Install your custom ROM.
I did it as remembered back to the days with my old s10 with custom ROM android 10.
Click to expand...
Click to collapse
In the official TWRP My SD card shows only 117MB instead of 128GB bro. So i will try adb sideload bro
Probably your SD card is formatted with ExFat which isn't visible in twrp.
Try FAT32 in stead.
{the file is too large for destination} -b cant able to transfer file more than 4gb bro after formatting SD card to FAT32
Bro in island work profile, intune looks like this only bro, I did click in check device settings multiple time bro nothing happens bro but in the main profile I can install and register my device in intune bro and use my company mails and teams bro
You do know how to use island? You can only use one intune app either in main or work profile. Clone or install directly in work profile and uninstall from the main profile.
Did you check the root from work profile with Applist detector? Install Applist Detector in work profile and run.
In my work profile my device settings is registered as unknown, but ok because it does pass all checks from company apps.