Custom Rom with gapps inbuilt - Huawei MediaPad T5 Questions & Answers

Hi! I've unlocked bootloader and install LOS 18.1 and I've flashed opengapps. Safetynet is ok, PlayStore is now certified but some apps as Netflix or Disney+ doesn't work, they stuck on logo and I have to kill them manually. I've followed all tutorials on xda (installing magisk, magiskhide on and other stuff) but I can't get these apps working. There's some custom rom with in-built gapps with no problem with safetynet and streaming apps or there's a way to get them working in my rom? Thanks.

Related

Xposed Framework {Advice Needed}

Hey guys,
I've been searching on the web regarding Xposed Framework. I've installed Magisk, and tried to download Xposed Framework for SDK 25, however whenever I reboot, its stick at the Google logo. I also tried the Xposed Installer which said arm64-v8a is not support at the moment, so I was wondering if anyone installed Xposed on their pixel? Any alternative ways?
Cheers
cwk8412 said:
Hey guys,
I've been searching on the web regarding Xposed Framework. I've installed Magisk, and tried to download Xposed Framework for SDK 25, however whenever I reboot, its stick at the Google logo. I also tried the Xposed Installer which said arm64-v8a is not support at the moment, so I was wondering if anyone installed Xposed on their pixel? Any alternative ways?
Cheers
Click to expand...
Click to collapse
wipe your phone and revert to stock and try again through magisk. it will eventually work and id the only xposed working on this phone right now. use the xposed installer in the description of the magisk module.
KittyRgnarok said:
wipe your phone and revert to stock and try again through magisk. it will eventually work and id the only xposed working on this phone right now. use the xposed installer in the description of the magisk module.
Click to expand...
Click to collapse
So I downgraded to Android 7.1.0 (NDE63H) from the official Google Website and installed Magisk v14.5 (beta) by flashing through TWRP Recovery. However, when I download the Xposed Module from Magisk, it was able to install. However, when I press the reboot button on Magisk, it turns into some sort of BootLoop where it stuck at the Google Logo. Any idea?
Cheers
cwk8412 said:
So I downgraded to Android 7.1.0 (NDE63H) from the official Google Website and installed Magisk v14.5 (beta) by flashing through TWRP Recovery. However, when I download the Xposed Module from Magisk, it was able to install. However, when I press the reboot button on Magisk, it turns into some sort of BootLoop where it stuck at the Google Logo. Any idea?
Cheers
Click to expand...
Click to collapse
Oh yeah i forgot to mention, after u downgrade to nougat you need to be on Magisk 14.2 and refuse to update it for xposed to work. ive not yet figured out why this is but i noticed that after updating to 14.3+ and trying to flash it would always do the google loop and i had to full wipe n just keep redoing the process until it works. being updated will cause the fail to boot and updating after its installed will break all installed magisk modules

Google Pay does not work on unrooted custom ROM anymore!

So, I just installed Google Pay and wanted to connect it with my PayPal account. Everything was going fine until I finished the setup - the app showed me a message saying "Setup for paying in stores could not be finished - This smartphone can not be used to pay with in stores. This can be due to your phone being rooted or changed otherwise."
I have a completely vanilla LineageOS 15.1 (latest build) installed. No Magisk or Xposed. So this might be because I installed a custom ROM.
I will keep this thread updated - I will try to install the latest build of LineageOS 16, then if it does not work, continue to flash the latest stock ROM.
Flashed LineageOS 16, got the same issue. Flashed stock ROM now and hopefully it will work.
DKXC said:
Flashed LineageOS 16, got the same issue. Flashed stock ROM now and hopefully it will work.
Click to expand...
Click to collapse
Lineage builds for Samsung have that issue. They struggle to pass SafetyNet even if its not rooted. I'm running stock + Magisk and have Snapchat, Fortnite, Google Pay, and Pokemon Go all working no problem. Sac23's s9 port also has a good SafetyNet, just make sure to not use the Magisk included in the Aroma installer and use the latest zip
I've tried LineageOS 15 with Magisk. Google Pay works, but does not allow fingerprint use, only PIN/pattern. Same with WellsFargo app. It appears that something is incomplete or incorrect on the Samsung port of Lineage. Stock roms with Magisk do not have this issue.
So what's the best way to get android pay working? Just install Stock ROM and use Magisk to root?

Soft reboot after installing magisk modules. Phone is OOS latest stable & encrypted

Soft reboot after installing magisk modules. Phone is OOS latest stable & encrypted
Guys, I will never post a new thread to xda if I ain't doing research for at least 1 day and found a solution. But here I am, so please read this.
Just bought OP6 yesterday, updating to latest stable Pie OOS 9.0, unlock the bootloader, install blu_spark twrp, magisk 17.1 (but haven't install the modules at this point), then reboot just fine like my other magisk rooted phone. HAVEN'T DECRYPT my OP6 until this post.
Now this where it began. I install BUNCH OF MODULES, KEEP REBOOT TO TWRP and ASK FOR MY PASSWORD TO DECRYPT which I did with the pattern I set, and IT DECRYPT just fine. But when I try to REBOOT TO SYSTEM, IT KEEPS REBOOTING TO TWRP AGAIN . The way I fix this is to uninstall then REINSTALL MAGISK 17.1. BOOT JUST FINE, just minus that modules
I try to INSTALL just ONE MODULE, same things happen. The way I fix it is same as before.
Anyone has this same problem? Should I decrypt my phone with this tutorial https://forum.xda-developers.com/oneplus-6/how-to/test-decryption-t3818775 in order to have Magisk modules work?
bramhc said:
Guys, I will never post a new thread to xda if I ain't doing research for at least 1 day and found a solution. But here I am, so please read this.
Just bought OP6 yesterday, updating to latest stable Pie OOS 9.0, unlock the bootloader, install blu_spark twrp, magisk 17.1 (but haven't install the modules at this point), then reboot just fine like my other magisk rooted phone. HAVEN'T DECRYPT my OP6 until this post.
Now this where it began. I install BUNCH OF MODULES, KEEP REBOOT TO TWRP and ASK FOR MY PASSWORD TO DECRYPT which I did with the pattern I set, and IT DECRYPT just fine. But when I try to REBOOT TO SYSTEM, IT KEEPS REBOOTING TO TWRP AGAIN . The way I fix this is to uninstall then REINSTALL MAGISK 17.1. BOOT JUST FINE, just minus that modules
I try to INSTALL just ONE MODULE, same things happen. The way I fix it is same as before.
Anyone has this same problem? Should I decrypt my phone with this tutorial https://forum.xda-developers.com/oneplus-6/how-to/test-decryption-t3818775 in order to have Magisk modules work?
Click to expand...
Click to collapse
Maybe it's the modules your installing. ALOT of people have modules installed on this phone without this issue. Don't Decrypt data because it's not necessary.
yldlj said:
Maybe it's the modules your installing. ALOT of people have modules installed on this phone without this issue. Don't Decrypt data because it's not necessary.
Click to expand...
Click to collapse
Okay man. I just figured out some modules just don't work. Cause I can install Camera2Api and some kernel modules with Magisk.
Modules that always crash to install are James DSP, Audio Modification Library, and Viper4Android from official Magisk repo
bramhc said:
Okay man. I just figured out some modules just don't work. Cause I can install Camera2Api and some kernel modules with Magisk.
Modules that always crash to install are James DSP, Audio Modification Library, and Viper4Android from official Magisk repo
Click to expand...
Click to collapse
I'm using VIPER4AndroidFX 1.7.5 materialized just fine. I have magisk 17.2
yldlj said:
I'm using VIPER4AndroidFX 1.7.5 materialized just fine. I have magisk 17.2
Click to expand...
Click to collapse
Okay. Will try now. Thanks
EDIT: Confirmed. Viper4android works. Maybe it's James DSP that hasn't been updated to work with Pie. Cheers.

SafetyNet false all the time...

I've installed LineageOS 15.1 with Magisk 19.3 (tried 19.4 also) and my SafetyNet is all the time False. I even tried to install LineageOS 14.1 with Magisk 18 - it didn't work. I also flashed GApps (nano/pico versions). Any idea how to fix it? I already tried hiding Magisk and all typical stuff
kamieniarz said:
I've installed LineageOS 15.1 with Magisk 19.3 (tried 19.4 also) and my SafetyNet is all the time False. I even tried to install LineageOS 14.1 with Magisk 18 - it didn't work. I also flashed GApps (nano/pico versions). Any idea how to fix it? I already tried hiding Magisk and all typical stuff
Click to expand...
Click to collapse
status of selinux?
CriGiu said:
status of selinux?
Click to expand...
Click to collapse
Enforcing
EDIT: I've noticed that SafetyNet is true when I revoke all SU privilages... But I need them so it's not a solutions for me
Hi, I was facing the same problem. I am running an Android 9 ROM (crDroid), though, so I don't know if my solution will work for you. Anyway, what seems to have fixed this for me is flashing ROM and Gapps first, let the device boot fully and then flash Magisk on its own. If you want to avoid clean flashing the ROM etc. again, you could try unistalling Magisk by flashing the official uninstaller, reboot, then flash it anew. That also worked for me.
I used to get this erratic behavior from Magisk when dirty flashing ROM updates, so each time I uninstall it and re-install it. It's a bummer, but it works in the end... I haven't yet figured out if this "SafetyNet fail" is either ROM or Magisk related. I hope I helped!
My condition was android pie/custom rom,magisk 19.3 stable,selinux permissive,device uncertified in playstore,safetynet false cts and basic integrity.
How is your device certified or uncertified?
However,this was my fix.
In magisk hide i ticked all apps,even system's ones.
In settings/apps i deleted all cache/data of playstore and google play services.
I rebooted in twrp and i cleaned cache and dalvik cache.
I rebooted system.
I waited until my device was fully booted,it depends on your settings,apps etc.
Then i checked magisk,safetynet passed and in playstore my device was correctly recognized as certified.

Just Unlocking the Bootloader breakes safety net and make device unverified..

So as the title says safety net breaks just by unlocking the bootloader and doing nothing else, no twrp no magisk and even if i flash magisk it doesnt fix it even with magiskprops module.
I flashed stock rom 10.3.1 with msmtool and booted the phone and everything was fine until i unlocked the bootloader and rebooted. I lost all oneplus wallpapers and even then play store says device not verified and netflix shows as unsupported app.
Even with 10.3.4 the issue is same and cant be fixed with magisk. Previously i was using 10.3.2 with unlocked bootloder and magisk and safety net was fine so how it is now not working with factory rom i flashed with msmtool
https://forum.xda-developers.com/on...etynet-magisk-edxposed-tests-failing-t4077527
Manu11 said:
So as the title says safety net breaks just by unlocking the bootloader and doing nothing else, no twrp no magisk and even if i flash magisk it doesnt fix it even with magiskprops module.
I flashed stock rom 10.3.1 with msmtool and booted the phone and everything was fine until i unlocked the bootloader and rebooted. I lost all oneplus wallpapers and even then play store says device not verified and netflix shows as unsupported app.
Even with 10.3.4 the issue is same and cant be fixed with magisk. Previously i was using 10.3.2 with unlocked bootloder and magisk and safety net was fine so how it is now not working with factory rom i flashed with msmtool
Click to expand...
Click to collapse
Don't think so. I'm on a rooted 10.3.4 and I don't see such issues with playstore or safetynet.
hallo dare said:
https://forum.xda-developers.com/on...etynet-magisk-edxposed-tests-failing-t4077527
Click to expand...
Click to collapse
safetynet fails even without the magisk, so i dont think its a magisk problem
Manu11 said:
safetynet fails even without the magisk, so i dont think its a magisk problem
Click to expand...
Click to collapse
What'd u do ?
jaggillararla said:
What'd u do ?
Click to expand...
Click to collapse
There's nothing you can do about safetynet. The moment you unlock the bootloader, you have tripped the safetynet. Why do you need safetynet btw unless you are using bank apps or secure stuff, safetynet really doesn't help much
amirage said:
There's nothing you can do about safetynet. The moment you unlock the bootloader, you have tripped the safetynet. Why do you need safetynet btw unless you are using bank apps or secure stuff, safetynet really doesn't help much
Click to expand...
Click to collapse
Bro as i told already in my post i was yesterday using unlocked bootloader + magisk+ twrp with passing safety net. The problem started when i clean flashed stock rom with msmtool and unlocked bootloader.
ANYWAYS GUYS AFTER SO MANY USELESS ATTEMPS I SOLVED IT..
Older version of magisk worked and safety net passes, i dont know how new version failed me :/ Device is certified again
That's why I don't update anything if not have to
Config below
Sent from OnePlus 7 Pro, OxygenOS 10.0.3, TWRP 3.3.1-75, Magisk 20.4, TaiChi Xposed 6.1.8, Modded Play Store 16.5.15, android core.java patched and SafetyNet pass OK
Install magisk
Go to magisk settings
Enable magisk hide(if you're getting problems with banking apps or games that detect root just hide magisk manager too)
Enable it for google play services and enjoy!
Playstore uncertified status appeared to me when I flash stock rom through TWRP but it solves flashing new firmware via OTA
Sent from my OnePlus7Pro using XDA Labs
The reason an older version of Magisk worked is because newer versions of Magisk turn MagiskHide off by default, which is needed to pass SafetyNet.
Also, SafetyNet is not an e-fuse like Knox is. You don't "trip" it, you can only fail it when it checks your device.

Categories

Resources