Coming from Android P dp3, I wiped and clean flashed dp4. Set up as new, then flashed Magisk.
I have tried different settings, but for the life of me, I cannot get ctsProfile to pass.
Anyone else having a similar issue?
I was on DP3 and both failed for me.. so I just assume wait for an update from the Magisk dev.
Same, will be waiting...
mine was working fine on dp3 but fails cts profile on dp4 (pixel 1 though)
I thought ctsProfile always failed with just Magisk and you need a custom kernel too? I'm waiting for an update to Flash Kernel.
henderjr said:
I thought ctsProfile always failed with just Magisk and you need a custom kernel too? I'm waiting for an update to Flash Kernel.
Click to expand...
Click to collapse
i don't know it was passing on DP3
Did you guys clear data on play services and play store?
The funny thing is that I flashed without wipe and not installing magisk. The cts profile still failed.
Haven't tried fully wipe though.
Sent from my Pixel 2 XL using Tapatalk
henderjr said:
I thought ctsProfile always failed with just Magisk and you need a custom kernel too? I'm waiting for an update to Flash Kernel.
Click to expand...
Click to collapse
Ah -- yes, I probably was on Flash on dp3 -- hard enough to remember what I had for lunch yesterday let alone recall the modding I do to my phone from weeks prior
ram4ufriends said:
Did you guys clear data on play services and play store?
Click to expand...
Click to collapse
Yup. -- think the Flash Colonel will help.
Nope. On my DP3 with magisk, CTS passed.
henderjr said:
I thought ctsProfile always failed with just Magisk and you need a custom kernel too? I'm waiting for an update to Flash Kernel.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
Magisk only worked on boot on DP3 for me. After a couple of minutes it nagged about Magisk v16.4 (which was installed) being available.
So in dp3 I got safety net to pass by clearing Google play services and and the playstore, and after updating to dp4 nothing I did work
KevinThaKid said:
So in dp3 I got safety net to pass by clearing Google play services and and the playstore, and after updating to dp4 nothing I did work
Click to expand...
Click to collapse
I noticed safety net does not pass on DP4 also. have not been able to figure it out either ( may just have to wait for update to magisk ).
wassco said:
I noticed safety net does not pass on DP4 also. have not been able to figure it out either ( may just have to wait for update to magisk ).
Click to expand...
Click to collapse
Not Magisk. Google seems to have done it intentionally.
Guess we've been spoiled the previous builds
https://twitter.com/topjohnwu/status/1014059549643247616?s=09
and
https://developer.android.com/preview/release-notes
"Android P beta devices aren't Compatibility Test Suite (CTS) approved, but they have passed preliminary testing and provide the same set of APIs for developers. Apps that depend on CTS-approved builds might not work normally on supported devices."
I rolled back to DP3, will wait for DP5 to see if it is fixed. I need GPay and that safetynet to pass for stuff daily.
Oh well...working fine on DP3 for me everything I use! Spoiled is right.
techlogik said:
I rolled back to DP3, will wait for DP5 to see if it is fixed. I need GPay and that safetynet to pass for stuff daily.
Oh well...working fine on DP3 for me everything I use! Spoiled is right.
Click to expand...
Click to collapse
Look after flash kernel thread..seems like Google fixed it
The SafetyNet issue has been fixed with a server-side update by Google. I only cleared storage on my Google Play Store app and the device has become 'Certified'. SafetyNet passes and I've just added my card to Google Pay again.
widezu69 said:
The SafetyNet issue has been fixed with a server-side update by Google. I only cleared storage on my Google Play Store app and the device has become 'Certified'. SafetyNet passes and I've just added my card to Google Pay again.
Click to expand...
Click to collapse
Good to know I will update back to dp4 later and do that
widezu69 said:
The SafetyNet issue has been fixed with a server-side update by Google. I only cleared storage on my Google Play Store app and the device has become 'Certified'. SafetyNet passes and I've just added my card to Google Pay again.
Click to expand...
Click to collapse
I tried that but no luck
Can anyone tell me how they rooted?
I tried booting twrp, installing magisk 16, 14.4., 16.4
Installing twrp, flash 16, 14.4, 16.4
Copy the stock boot and patch via the magisk manager, install in twrp,
No luck anyway.
Edit: Twrp can't decrypt a pattern.
Related
Can anyone confirm if Magisk root works with the 8.1 release?
It Works
Its working but when you reboot the device I'm getting the "there's an internal problem with your device " which has to do with a mismatch between the Vendor and System Partitions. Only happens after flashing the 14.5(1456) Build either from TWRP or using the boot.img patcher in Magisk Manager. Not sure how to fix this error but otherwise everything is working.
Edit: Picture for reference
Edit 2: Root, safetynet pass, and modules are all working just an annoying error message on boot.
Edit 3: Known issue with the 1456 build of Magisk. Developers are already aware of it. Information below.
topjohnwu said:
The additional avb-verity removal from DTBO on the Pixel 2 devices results in a scary pop-up. No need to worry here, it's Google warning you that your vendor partition doesn't work as expected. I decided to strip off avb-verity to make modifications to the vendor partition possible, as people tend to modify their partitions a lot, and not sure if this might save a few soft brick devices.... As the old dm-verity and avb-verity works so different, it is very difficult for me to come up with a proper way that doesn't complicate things on the user side.
Click to expand...
Click to collapse
Itachisasuke said:
Its working but when you reboot the device I'm getting the "there's an internal problem with your device " which has to do with a mismatch between the Vendor and System Partitions. Only happens after flashing the 14.5(1456) Build either from TWRP or using the boot.img patcher in Magisk Manager. Not sure how to fix this error but otherwise everything is working.
Click to expand...
Click to collapse
Yep, Magisk works....unfortunately the error upon boot is there. Prior to Magisk, 8.1 didn't show the error. After the Magisk flash, the error always pops up upon start up.
Guess I'll wait with re-rooting then.
Colchiro said:
Guess I'll wait with re-rooting then.
Click to expand...
Click to collapse
Why, it still works fine. Just ignore the message :good:
Badger50 said:
Why, it still works fine. Just ignore the message :good:
Click to expand...
Click to collapse
Does it still pass Safetynet?
MrBrady said:
Does it still pass Safetynet?
Click to expand...
Click to collapse
Yup :good:
The error is just an annoyance, you still have root and pass safety net. I used Magisk on the last Beta build and got the same error It did not impact anything.
Sav_Droid said:
Yep, Magisk works....unfortunately the error upon boot is there. Prior to Magisk, 8.1 didn't show the error. After the Magisk flash, the error always pops up upon start up.
Click to expand...
Click to collapse
14.4 doesn't show the error message, but fails the SafetyNet check. Android Pay still works, though.
Do you need to flash stock 8.0 boot.img before applying 8.1 OTA?
swooperstar said:
Do you need to flash stock 8.0 boot.img before applying 8.1 OTA?
Click to expand...
Click to collapse
Yes I would def uninstall magisk before going on to 8.1 and flash boot.img to both slots
lucky_strike33 said:
Yes I would def uninstall magisk before going on to 8.1 and flash boot.img to both slots
Click to expand...
Click to collapse
I didn't.
Sideloading the new OTA will overwrite the patched image
Just curious, but wondering why people are in such a rush to install 8.1. With all of the contact sync issues oh, this would drive me absolutely crazy. I might just wait until January to update unless there is a quick fix.
Cowbell_Guy said:
Just curious, but wondering why people are in such a rush to install 8.1. With all of the contact sync issues oh, this would drive me absolutely crazy. I might just wait until January to update unless there is a quick fix.
Click to expand...
Click to collapse
Probably just because we can. We flashaholics gotta have our fix! Everything is working fine on my end. Then again, all my contacts are synced through Gmail :good:
Cowbell_Guy said:
Just curious, but wondering why people are in such a rush to install 8.1. With all of the contact sync issues oh, this would drive me absolutely crazy. I might just wait until January to update unless there is a quick fix.
Click to expand...
Click to collapse
Contact sync issues? Never had that before.. what's the issue exactly? Not getting all of them or all the info?
You can get rid of the error message by rooting with Magisk, then uninstalling Magisk Manager, reflashing the stock (or your kernel's) dtbo, then rebooting and reinstalling Magisk Manager. Passes SafetyNet and have full root.
jbarcus81 said:
Contact sync issues? Never had that before.. what's the issue exactly? Not getting all of them or all the info?
Click to expand...
Click to collapse
Some Google contacts aren't syncing since installing the 8.1 official release. I have this issue and so do many others. There's a thread taking about it in this section already. It effected almost all of the contacts I talk to the most.
There is a workaround. Go into the web interface of Google contacts on your computer and edit the contract to reminder their profile URL and it forces the sync to go through for that contact. I did this for my 10 most frequent contacts. However, this would be a nightmare to do for every contact.
Google development is aware of the issue and working on a fix.
---------- Post added at 03:27 AM ---------- Previous post was at 03:27 AM ----------
gettingerr said:
You can get rid of the error message by rooting with Magisk, then uninstalling Magisk Manager, reflashing the stock (or your kernel's) dtbo, then rebooting and reinstalling Magisk Manager. Passes SafetyNet and have full root.
Click to expand...
Click to collapse
What's "dtbo"?
Yeah I did this too and bam,,,error message on boot gone LOL,,,just have to stay with Magisk Manager 5.4.0 and not update through Magisk. But it all works, safety net pass.
gettingerr said:
You can get rid of the error message by rooting with Magisk, then uninstalling Magisk Manager, reflashing the stock (or your kernel's) dtbo, then rebooting and reinstalling Magisk Manager. Passes SafetyNet and have full root.
Click to expand...
Click to collapse
Archangel said:
Yeah I did this too and bam,,,error message on boot gone LOL,,,just have to stay with Magisk Manager 5.4.0 and not update through Magisk. But it all works, safety net pass.
Click to expand...
Click to collapse
I actually was curious what would happen if I used the latest Magisk Manager, and nothing happened. So I am using the latest. No error and no issues that I can note. Except maybe installing modules if you're into that sort of thing.
---------- Post added at 05:07 AM ---------- Previous post was at 05:06 AM ----------
sn0warmy said:
What's "dtbo"?
Click to expand...
Click to collapse
No clue. http://lmgtfy.com/?q=dtbo
I didn't read the links but maybe something there can explain it.
Kind of a long story:
I have the TIM branded Zenfone 3 Deluxe 570KL and everything was ok (safetynet pass on both CTS and Basic integrity with Magisk root).
Then i updated Magisk to the 15.0 version and got my device encrypted randomly at the restart (and yes this is a problem with this version but hangon), after the upgrade to 15.0 and the device encrypted now the CTS verification fails so i tried to downgrade back to version 14 of magisk to no avail.
From there i downloaded the WW version of the firmware, formatted the phone (inc data), convert the zip to a flashable img file and flashed the stock WW with no root.
Device still encrypted despite the complete format and fails again the safetynet.
Tried to flash the TIM version downloadable from ASUS with the same result.
Somehow i flashed the stock WW and safetynet fails only on CTS but as soon as i install the version 15.1 of magisk and enabling Magisk hide on google apps i fail safetynet also on basic integrity.
Do you know any way to remove this dammned encryption since there is no option to disable it in the security settings and flash a fresh stock firmware that passes safetynet?
Maybe with a twrp backup of a stock firware i can do something?
Regards and happy holydays
exico91 said:
Kind of a long story:
I have the TIM branded Zenfone 3 Deluxe 570KL and everything was ok (safetynet pass on both CTS and Basic integrity with Magisk root).
Then i updated Magisk to the 15.0 version and got my device encrypted randomly at the restart (and yes this is a problem with this version but hangon), after the upgrade to 15.0 and the device encrypted now the CTS verification fails so i tried to downgrade back to version 14 of magisk to no avail.
From there i downloaded the WW version of the firmware, formatted the phone (inc data), convert the zip to a flashable img file and flashed the stock WW with no root.
Device still encrypted despite the complete format and fails again the safetynet.
Tried to flash the TIM version downloadable from ASUS with the same result.
Somehow i flashed the stock WW and safetynet fails only on CTS but as soon as i install the version 15.1 of magisk and enabling Magisk hide on google apps i fail safetynet also on basic integrity.
Do you know any way to remove this dammned encryption since there is no option to disable it in the security settings and flash a fresh stock firmware that passes safetynet?
Maybe with a twrp backup of a stock firware i can do something?
Regards and happy holydays
Click to expand...
Click to collapse
I am having the same problem with Magisk v15.1. What I did for a temporary solution is I flashed back to Magisk v14.0 and it now passes safety checks. I am using Android 7.0 and I have the 2.15 ghz version of the phone (Asus_Z016D) Hope this helps.
---------- Post added at 08:48 PM ---------- Previous post was at 08:45 PM ----------
https://forum.xda-developers.com/showpost.php?p=75017953&postcount=5170
Thanks for the suggestion. Flash back the 14 is the first thing I tried but it failed and then I tried to reset and reflash the stock firmware but now, like I said, nothing that I tried works.
I know is asking a lot but can you make a TWRP backup of your phone except the data partition obviously? Maybe that encryption f** up something that I can't fix just by reset and flash the stock
I have the same problem. Safetynet fails... Are you sure that encryption is the cause?
Ryder. said:
I have the same problem. Safetynet fails... Are you sure that encryption is the cause?
Click to expand...
Click to collapse
I believe so, i got encrypted only when i installed the 15.0 but even if i format system and data and i flash a clean stock the options says that my phone is encrypted even if the phone has no password or i didnt activate it
exico91 said:
I believe so, i got encrypted only when i installed the 15.0 but even if i format system and data and i flash a clean stock the options says that my phone is encrypted even if the phone has no password or i didnt activate it
Click to expand...
Click to collapse
I updated to magisk 15.2 and magisk hide works now. Now i can see nintendo games on play store for example. However ctsprofile doesn't pass safetynet check
Ryder. said:
I updated to magisk 15.2 and magisk hide works now. Now i can see nintendo games on play store for example. However ctsprofile doesn't pass safetynet check
Click to expand...
Click to collapse
Would be nice to pass also CTS like before but Im ok with just the integrity check.
And yeah i can confirm that it works now with 15.2.
That was driving me mad; interesting fact: Fire Emblem Heroes go into connection error loop if the integrity check fails or detect that the phone is rooted and that happens at random times. I hate this approach of Nintendo and such, if i want to have control of my phone you shouldnt penalize me for that.
Anyway if someone is brave enough to share a stock/rooted backup that pass the CTS i would gladly try it out.
exico91 said:
Would be nice to pass also CTS like before but Im ok with just the integrity check.
And yeah i can confirm that it works now with 15.2.
That was driving me mad; interesting fact: Fire Emblem Heroes go into connection error loop if the integrity check fails or detect that the phone is rooted and that happens at random times. I hate this approach of Nintendo and such, if i want to have control of my phone you shouldnt penalize me for that.
Anyway if someone is brave enough to share a stock/rooted backup that pass the CTS i would gladly try it out.
Click to expand...
Click to collapse
I agree. Even Gangstar New Orleans isn't downloadable if you have root. It's root the cause! I tought it was the fact that it's available only for some devices for certain reasons. Now even gameloft seems to penalize root users...
Did you go on magisk hide section and selected the apps/games which you are interested in?
Ryder. said:
I agree. Even Gangstar New Orleans isn't downloadable if you have root. It's root the cause! I tought it was the fact that it's available only for some devices for certain reasons. Now even gameloft seems to penalize root users...
Did you go on magisk hide section and selected the apps/games which you are interested in?
Click to expand...
Click to collapse
To download the apps/games, obviously, you have to use hide on google play then, when are installed, on the apps
Since i want to use Android Pay but got this issue, is there any stock rom which passes certification?
Could you please check:
Open the Google Play Store app Google Play.
Tap Menu Menu and then Settings.
Under “Device certification” you’ll see if your device is certified
Edit: After some research i can say it happens because of unlocked bootloader.
Any solution to pass cts verification?
Hey guys. So I have the latest magisk beta v19 and latest magisk manager. My safety net is passing but Google pay doesn't work. Did the new March update make it detect unlocked bootloader? My bootloader is unlocked with TWRP installed. Has anyone tested with and without TWRP installed?
zee24 said:
Hey guys. So I have the latest magisk beta v19 and latest magisk manager. My safety net is passing but Google pay doesn't work. Did the new March update make it detect unlocked bootloader? My bootloader is unlocked with TWRP installed. Has anyone tested with and without TWRP installed?
Click to expand...
Click to collapse
Works for me but I had to make sure to hide the needed apps in MagiskHide (GPay, G Play Services, Framework) and even then, it required me to clear data in Pay, Services > then reboot > then proceed to add a card.
Also check to make sure that auto updates are not on for Google Pay. I think the version matters. My version is currently 2.84.237487748.
SageWilliams said:
Works for me but I had to make sure to hide the needed apps in MagiskHide (GPay, G Play Services, Framework) and even then, it required me to clear data in Pay, Services > then reboot > then proceed to add a card.
Also check to make sure that auto updates are not on for Google Pay. I think the version matters. My version is currently 2.84.237487748.
Click to expand...
Click to collapse
Wow so idk which one of the things you said did it but it worked, I downgraded my app, but I didn't have Google framework hidden from magisk so I did that I cleared the data and then rebooted that worked! Thanks so much and anyone else who's having this issue try this
zee24 said:
Wow so idk which one of the things you said did it but it worked, I downgraded my app, but I didn't have Google framework hidden from magisk so I did that I cleared the data and then rebooted that worked! Thanks so much and anyone else who's having this issue try this
Click to expand...
Click to collapse
Great, I will say its hit or miss sometimes. Mine worked in stores for a few days, then stopped saying I was rooted so I had to redo the method to get it back.
This is the fix
Magisk stable build, all latest official builds of everything else, nothing special. and Magisk hide on google play store, google play services and google pay then - Renaming com.google.android.gms to com.google.android.gms.bak (found in Data/Data) in root browser and then rebooting is the answer .
prot- said:
This is the fix
Magisk stable build, all latest official builds of everything else, nothing special. and Magisk hide on google play store, google play services and google pay then - Renaming com.google.android.gms to com.google.android.gms.bak (found in Data/Data) in root browser and then rebooting is the answer .
Click to expand...
Click to collapse
Great. Finally a fix. All like above but used Magisk 19.0. Thanks. I hope we're able to keep finding fixes like this. Google pay is a convenience.
According to this, it is to be expected on Pixel devices, vs others.
Advantages:
If you will see the list of the advantages and the list is too long of the magisk. This is the best Android application which you can use on your device. Let’s take a dive in the advantages of the Magisk.
You can use Financial/Banking applications.
You can use Snapchat without any issues.
You can also play Pokemon Go on your rooted Android device.
You can install OTA updates on your device.
You can also install System-less Xposed framework on your lollipop and marshmallow devices.
You can use Android Pay.
You can also bypass SafetyNet.
You might Face issues in:
Google Pixel and Google Pixel XL devices. The work is in progress, and we are working on i.
Magisk Manager cannot be placed in adaptable storage, or superuser will not work
MagiskSU does not support multi-user, and we are working on it to make multi-user support.
MagiskSU does not work on Android O preview, and we are working on it.
Click to expand...
Click to collapse
https://******************/
Since when are we not allowed to post links? Go to: magiskmanager dot com
Droid_Nut said:
According to this, it is to be expected on Pixel devices, vs others.
https://******************/
Since when are we not allowed to post links? Go to: magiskmanager dot com
Click to expand...
Click to collapse
Ever since that site was verified to be a fake.
https://www.google.com/amp/s/www.xd...kmanager-com-not-official-website-magisk/amp/
prot- said:
This is the fix
Magisk stable build, all latest official builds of everything else, nothing special. and Magisk hide on google play store, google play services and google pay then - Renaming com.google.android.gms to com.google.android.gms.bak (found in Data/Data) in root browser and then rebooting is the answer .
Click to expand...
Click to collapse
Thanks so much dude....much appreciated
I was running Android 9 Aug?2018 update with a custom kernel and Magisk. A few weeks ago Google Pay stopped working and i read the long thread here about the Google Play store update and Magisk no longer hiding root. I dirty flashed an updated stock rom and removed the format (-w) switch. I stayed with the stock kernel. Re-rooted with update Magisk root and Magisk app. In Magisk i pass SafetyNet Check ctsProfile and basicIntegrity. When i try to use Google Pay I still get the error message that i cannot use GooglePay there. I am very close to just going completely stock with no root as I am not jacking with my phone as much as i did years ago, android is progressing nicely and plus many devs have moved on from the P2XL. I just really dont want to have to re setup my phone. Any thing else i can try to use GooglePay before i go back to stock?
P2XL Bootloader unlocked
Android: 9.0 3/5/19
Magisk V19.0 (19000)
Magisk Manager 7.1.1
Not running any Magisk Modules
Thanks for any help or suggestions
fortillian said:
I was running Android 9 Aug?2018 update with a custom kernel and Magisk. A few weeks ago Google Pay stopped working and i read the long thread here about the Google Play store update and Magisk no longer hiding root. I dirty flashed an updated stock rom and removed the format (-w) switch. I stayed with the stock kernel. Re-rooted with update Magisk root and Magisk app. In Magisk i pass SafetyNet Check ctsProfile and basicIntegrity. When i try to use Google Pay I still get the error message that i cannot use GooglePay there. I am very close to just going completely stock with no root as I am not jacking with my phone as much as i did years ago, android is progressing nicely and plus many devs have moved on from the P2XL. I just really dont want to have to re setup my phone. Any thing else i can try to use GooglePay before i go back to stock?
P2XL Bootloader unlocked
Android: 9.0 3/5/19
Magisk V19.0 (19000)
Magisk Manager 7.1.1
Not running any Magisk Modules
Thanks for any help or suggestions
Click to expand...
Click to collapse
There is a lot of talk in many threads about this. There is a good tutorial or two around that do work but seemingly only temporarily then it breaks again. Seems Google would a way to detect stuff that is not patched yet. I am at work so I don't have much time to go searching but it should not be hard to find. It includes deleting a folder and reinstalling and hiding magisk.
CyberpodS2 said:
There is a lot of talk in many threads about this. There is a good tutorial or two around that do work but seemingly only temporarily then it breaks again. Seems Google would a way to detect stuff that is not patched yet. I am at work so I don't have much time to go searching but it should not be hard to find. It includes deleting a folder and reinstalling and hiding magisk.
Click to expand...
Click to collapse
Yea, I've been through that 106 page thread and a few others. Renamed folders, deleted folders, reinstalled apps, hid services in magisk hide. I was never a fan of NFC payment until I started using it lol.
Try safety patch module in Magisk to pass Safetynet
HueyT said:
Try safety patch module in Magisk to pass Safetynet
Click to expand...
Click to collapse
I appreciate the reply. installed this plugin. cleared cache/data for Google Pay and Deleted the GMS folder again. Reinstalled GPay, no joy
Trying to decide on checking out Android Q or Dirty Unicorn. I dont jack with my phone much anymore, may be worth it to checkout Q and lock it up for GPAY atleast for now.
fortillian said:
I appreciate the reply. installed this plugin. cleared cache/data for Google Pay and Deleted the GMS folder again. Reinstalled GPay, no joy
Trying to decide on checking out Android Q or Dirty Unicorn. I dont jack with my phone much anymore, may be worth it to checkout Q and lock it up for GPAY atleast for now.
Click to expand...
Click to collapse
I'm thinking the same
Hi there,
You can find attached the patched boot image for the first stable OOS 13 firmware (IN2023 = 8 Pro European/Global version)
Steps :
Unlock the phone bootloader
Install ADB and Fastboot on your computer
Download the patched boot.img below
Reboot your phone to fastboot mode and link it to your computer
Open a terminal prompt in the directory where the boot.img is located
type in the cmd
fastboot flash boot IN2023_11_F13-Patched.img
Click to expand...
Click to collapse
and press enter
Reboot the phone
Open the magisk app, hit Install then use the recommended method
Reboot and you're rooted
Google Drive
Thanks for this. Where can you download the oos13 firmware?
MR0808 said:
Thanks for this. Where can you download the oos13 firmware?
Click to expand...
Click to collapse
The update is available through Oxygen Updater app
First thoughts on OOS 13 are really positive, smoothness is the first thing I noticed, it's day and night with OOS 12
The UI revamp is very satisfying to me
Overall, it feels more polished than OOS 12, with the sense of details in every feature/setting, and some new unique features
Thanks. Looks like I'm getting IN2025, so will have to do the patched boot.img myself.
Time to find my old notes somewhere
Is your Fingerprint Sensor working with A13? Mine not.
I assume same issues as we had with A12 and USNF
GhostRider86 said:
Is your Fingerprint Sensor working with A13? Mine not.
I assume same issues as we had with A12 and USNF
Click to expand...
Click to collapse
i kept all my magisk modules after the update which fix SafetyNet and Fingerprint issue, so i don't know
Neil_Armstrong_ said:
i kept all my magisk modules after the update which fix SafetyNet and Fingerprint issue, so i don't know
Click to expand...
Click to collapse
I keepted mine as well, SafetyNet and gPay are working, but Unlock with Fingerprint Sensor is not. No reaction to sensor at all, not able to register new Finger...
Edit: Working now. Needed to disable USNF module, no reboot, Fingerprint Sensor working, register Fingers, screen lock, test, enable USNF module, enjoy
Neil_Armstrong_ said:
The update is available through Oxygen Updater app
First thoughts on OOS 13 are really positive, smoothness is the first thing I noticed, it's day and night with OOS 12
The UI revamp is very satisfying to me
Overall, it feels more polished than OOS 12, with the sense of details in every feature/setting, and some new unique features
Click to expand...
Click to collapse
I already have the fil, but I can't install it from system update apk,
am I missing something ?
EDIT:
re-downloaded the file again from Oxygen updater, but still it fails to install nd also "verification failed" in system local update.
Edit 2:
I re MSM back to OOS11 and upgraded directly to OOS 13 F3.
Tanks you so much it worked for me.
Can we use google pay with this version rooted ?
Edit. Gpay works
Hey guys, what version of Magisk (and branch) are you using to root OOS13?
I am still on 11.0.11.11 with Magisk 23.
What is the procedure to upgrade to OOS13 from OOS11 without losing root, Magisk modules and all my data?
I tried downloading full OOS12 using Oxygen Updater app, ran Local System Upgrade, it finished normally, then installed Magisk to inactive slot (after OTA) and rebooted BUT after reboot - the system stays 11.0.11.11. And the attempt to Local System Upgdate for OOS13 fails right on start.
What am I missing?
Please help
VBBoston said:
Hey guys, what version of Magisk (and branch) are you using to root OOS13?
I am still on 11.0.11.11 with Magisk 23.
What is the procedure to upgrade to OOS13 from OOS11 without losing root, Magisk modules and all my data?
I tried downloading full OOS12 using Oxygen Updater app, ran Local System Upgrade, it finished normally, then installed Magisk to inactive slot (after OTA) and rebooted BUT after reboot - the system stays 11.0.11.11. And the attempt to Local System Upgdate for OOS13 fails right on start.
What am I missing?
Please help
Click to expand...
Click to collapse
I updated from oos 13 unrooted. Lost my root using oos12
I was able to get OOS13 installed but now need to restore root.
Could someone please share
Magisk patched boot.img for Global OOS13 (IN2025_11_F.13) for rooting?
Thank you ~
VBBoston said:
I was able to get OOS13 installed but now need to restore root.
Could someone please share
Magisk patched boot.img for Global OOS13 (IN2025_11_F.13) for rooting?
Thank you ~
Click to expand...
Click to collapse
They have already been shared here.
Thank you very much!
stell52 said:
Tanks you so much it worked for me.
Can we use google pay with this version rooted ?
Edit. Gpay works
Click to expand...
Click to collapse
I have two problems:
1. Netflix and hotstar are not working.
2. Hdfc and Axis apps are not working.
Are they working for u ? I have tried a lot of fixes but couldn't get them to work. If someone can help it would be highly appreciated
Neil_Armstrong_ said:
Hi there,
You can find attached the patched boot image for the first stable OOS 13 firmware (IN2023 = 8 Pro European/Global version)
Steps :
Unlock the phone bootloader
Install ADB and Fastboot on your computer
Download the patched boot.img below
Reboot your phone to fastboot mode and link it to your computer
Open a terminal prompt in the directory where the boot.img is located
type in the cmd
and press enter
Reboot the phone
Open the magisk app, hit Install then use the recommended method
Reboot and you're rooted
Google Drive
Click to expand...
Click to collapse
I have rooted it successfully. Everything is working except Netflix, Disney Hotstar and a few banking apps. I have tried enforcing denylist, shamiko.etc. nothing is getting them to work.
If u have any fix please let me know.
Thanks
MrBloB said:
I have two problems:
1. Netflix and hotstar are not working.
2. Hdfc and Axis apps are not working.
Are they working for u ? I have tried a lot of fixes but couldn't get them to work. If someone can help it would be highly appreciated
Click to expand...
Click to collapse
In magisk go to settings then make sure zygisk is checked and activate denylist. In the denylist check google services is check.
Then install the module universital safetynetfix v 2.3.1 by kdrag0n
To me netflix and other apps work.
In the google play store you have many apps that can check if your safetynet is verified after it. If its verified it should work
To me vanced manager do not work when i try to install youtube vanced. It says that i tried to downgrade paquet but i did not. I uninstalled every youtube upgrade. If somebody know
MrBloB said:
I have rooted it successfully. Everything is working except Netflix, Disney Hotstar and a few banking apps. I have tried enforcing denylist, shamiko.etc. nothing is getting them to work.
If u have any fix please let me know.
Thanks
Click to expand...
Click to collapse
Flash Universal SafetyNet module in magisk (kdrag0n) and Magisk Bootloop Protector (just in case)
Check your status after a reboot with YASNAC from Play Store
Force the Magisk DenyList, and when configuring it, develop the apps and check all the tick boxes manually (to be sure)
Uninstall Netflix and install the latest .apk from APKMirror, can't help as other app (banking too) works fine
Isn't vanced dead ?
YouTube Premium Argentina is very affordable fyi ....
stell52 said:
To me vanced manager do not work when i try to install youtube vanced. It says that i tried to downgrade paquet but i did not. I uninstalled every youtube upgrade. If somebody know
Click to expand...
Click to collapse
stell52 said:
In magisk go to settings then make sure zygisk is checked and activate denylist. In the denylist check google services is check.
Then install the module universital safetynetfix v 2.3.1 by kdrag0n
To me netflix and other apps work.
In the google play store you have many apps that can check if your safetynet is verified after it. If its verified it should work
Click to expand...
Click to collapse
Yes i have done this. Tried shamiko as well. M passing safetynet checks, still it doesnt work.