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.
Related
Hey guys,
Magisk has been going NUTS lately. It sometimes reports that I'm not rooted. Most apps work, but Adaway seems to be having a hard time lately. It's been working for a VERY long time and then maybe 2 weeks ago, it stopped. It can no longer copy the hosts file and it's disabled. This just happened out of the blue. Busybox also seems to hang on update.
Android pay is also on the fritz, but I know that's a different type of issue.
Anybody been through this?
Gootah said:
Hey guys,
Magisk has been going NUTS lately. It sometimes reports that I'm not rooted. Most apps work, but Adaway seems to be having a hard time lately. It's been working for a VERY long time and then maybe 2 weeks ago, it stopped. It can no longer copy the hosts file and it's disabled. This just happened out of the blue. Busybox also seems to hang on update.
Android pay is also on the fritz, but I know that's a different type of issue.
Anybody been through this?
Click to expand...
Click to collapse
Disable busy box and enabled core only mode in magisk manager settings.
Gootah said:
Hey guys,
Magisk has been going NUTS lately. It sometimes reports that I'm not rooted. Most apps work, but Adaway seems to be having a hard time lately. It's been working for a VERY long time and then maybe 2 weeks ago, it stopped. It can no longer copy the hosts file and it's disabled. This just happened out of the blue. Busybox also seems to hang on update.
Android pay is also on the fritz, but I know that's a different type of issue.
Anybody been through this?
Click to expand...
Click to collapse
What version of magisk are you using 12 or 13? And what version magisk manager are you using? And are you running it in core only mode?
pcriz said:
Disable busy box and enabled core only mode in magisk manager settings.
Click to expand...
Click to collapse
I uninstalled BB and ran core only mode, didn't work.
mac796 said:
What version of magisk are you using 12 or 13? And what version magisk manager are you using? And are you running it in core only mode?
Click to expand...
Click to collapse
I'm using manager 4.3.1 and Magisk 11.6. I'm going to do a backup and try updating all items.
Edit: According to the Magisk thread the Pixel devices are not supported, I'm not going to update
Edit2: I've noticed that my systemless hosts options doesn't stay toggled in magisk
Edit3: Did a magisk resinstall (unistall manager>Recovery>Flash Magisk>Flash TWRP>Reboot) still doesn't work
Gootah said:
I'm using manager 4.3.1 and Magisk 11.6. I'm going to do a backup and try updating all items.
Edit: According to the Magisk thread the Pixel devices are not supported, I'm not going to update
Edit2: I've noticed that my systemless hosts options doesn't stay toggled in magisk
Edit3: Did a magisk resinstall (unistall manager>Recovery>Flash Magisk>Flash TWRP>Reboot) still doesn't work
Click to expand...
Click to collapse
Id try switching the magic 12. It's posted in the RR thread in op. And magisk manager 4.3.3. You can get it from the APK mirror. You just got to run it in core only mode in settings. I don't have any problems or ever did with BusyBox. But I noticed the free version doesn't work
---------- Post added at 05:53 AM ---------- Previous post was at 05:40 AM ----------
mac796 said:
Id try switching the magic 12. It's posted in the RR thread in op. And magisk manager 4.3.3. You can get it from the APK mirror. You just got to run it in core only mode in settings. I don't have any problems or ever did with BusyBox. But I noticed the free version doesn't work
Click to expand...
Click to collapse
Here's one I'm using
https://drive.google.com/file/d/0B2n4LSlxHxTQOTlOZjQzZGhwZEU/view?usp=drivesdk
mac796 said:
Id try switching the magic 12. It's posted in the RR thread in op. And magisk manager 4.3.3. You can get it from the APK mirror. You just got to run it in core only mode in settings. I don't have any problems or ever did with BusyBox. But I noticed the free version doesn't work
---------- Post added at 05:53 AM ---------- Previous post was at 05:40 AM ----------
Here's one I'm using
https://drive.google.com/file/d/0B2n4LSlxHxTQOTlOZjQzZGhwZEU/view?usp=drivesdk
Click to expand...
Click to collapse
Thanks but the drive link is locked.
Gootah said:
Thanks but the drive link is locked.
Click to expand...
Click to collapse
Should be working again
mac796 said:
Should be working again
Click to expand...
Click to collapse
Got it, thanks.
Now I just have to hope I didn't super screw this thing over with all my tampering.
mac796 said:
Should be working again
Click to expand...
Click to collapse
Finally tried, 12 doesn't install. It errors out.
Flashed factory image and started from scratch, oh well! Thanks guys!
Gootah said:
Finally tried, 12 doesn't install. It errors out.
Click to expand...
Click to collapse
If you're talking about magisk 12 doesn't work anymore you need to use the new one B4.
https://www.androidfilehost.com/?w=files&flid=200113
mac796 said:
If you're talking about magisk 12 doesn't work anymore you need to use the new one B4.
https://www.androidfilehost.com/?w=files&flid=200113
Click to expand...
Click to collapse
you should've gone for magisk 13 B4
I believe c goodwin has his own thread for pixel magisk now
Captain Hindsight said:
you should've gone for magisk 13 B4
I believe c goodwin has his own thread for pixel magisk now
Click to expand...
Click to collapse
Didn't I just say that is your name Captain Obvious?
mac796 said:
Didn't I just say that is your name Captain Obvious?
Click to expand...
Click to collapse
It's Captain Hindsight - you should've realised that.
you should've also noticed you said nothing about C Goodwin having his own thread specifically for Magisk Pixel
you probably shouldn't have tried to one-up me
Captain Hindsight said:
It's Captain Hindsight - you should've realised that.
you should've also noticed you said nothing about C Goodwin having his own thread specifically for Magisk Pixel
you probably shouldn't have tried to one-up me
Click to expand...
Click to collapse
Here you go Captain
https://forum.xda-developers.com/apps/magisk/unofficial-google-pixel-family-support-t3639262
God Bless you.......
I tried uninstalling some modules to see if they were the cause I updated magisk to the beta channel in an attempt to fix it I also can't install new modules either. As far as I can tell I still have root as I have many things that rely on it. The logs are of the first time it happened I rebooted and it failed again giving me the second log. I reinstalled the 15.3 version of magisk and attempted to install a module it failed giving me the third log and the screenshot is after I upgraded magisk to the beta channel. @topjohnwu any idea what might be causing this I saw a post from a few months back but it didn't have a solution
is no one else having this issue?
razgriz1234 said:
is no one else having this issue?
Click to expand...
Click to collapse
I have the same issue. I have been flashing them from TWRP for now until it gets resolved.
CyberpodS2 said:
I have the same issue. I have been flashing them from TWRP for now until it gets resolved.
Click to expand...
Click to collapse
how do you flash them if they are supposed to be systemless? sorry if its a stupid question i still dont completely understand magisk as its the first phone ive had it on
solved with magisk 16.0 version
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.
^title, I haven't done anything new and all of the sudden today my magisksu will not prompt when apps request root with the log only saying superuser denied. I googled it and found posts dating back to 2017 about issues with this (which seems to happen 100% of the time when I have issues). I've done the fixes people said worked for them (turning off adaptive battery, repackaging magisk manager, rolling back to older magisk, taking magisk manager off the optimizing battery list, installing some adb fastboot ndk module thing, reinstalling magisk, full uninstall and reinstall, reflashing /boot /system and /vendor back to factory image stock.) and no luck. Has anyone else fixed this without a factory reset/reflash? Also at the same time this issue popped up I'm also having a really annoying time getting apps to install from the play store, it'll download say for instance 2.50 MB/2.50 MB 100% and just sit there for literally minutes before the app randomly says it's installed after the screen blacks out.
Oh also I'm getting no errors at all in the magisk log even entry is an informative.
Update: I was able to get solidexplorer to request root successfully but it literally too 3 minutes of waiting for the prompt to appear. I'm also getting errors in the log "write failed with 32: broken pipe" which I also saw in that forum post from 2017.
StykerB said:
^title, I haven't done anything new and all of the sudden today my magisksu will not prompt when apps request root with the log only saying superuser denied. I googled it and found posts dating back to 2017 about issues with this (which seems to happen 100% of the time when I have issues). I've done the fixes people said worked for them (turning off adaptive battery, repackaging magisk manager, rolling back to older magisk, taking magisk manager off the optimizing battery list, installing some adb fastboot ndk module thing, reinstalling magisk, full uninstall and reinstall, reflashing /boot /system and /vendor back to factory image stock.) and no luck. Has anyone else fixed this without a factory reset/reflash? Also at the same time this issue popped up I'm also having a really annoying time getting apps to install from the play store, it'll download say for instance 2.50 MB/2.50 MB 100% and just sit there for literally minutes before the app randomly says it's installed after the screen blacks out.
Oh also I'm getting no errors at all in the magisk log even entry is an informative.
Update: I was able to get solidexplorer to request root successfully but it literally too 3 minutes of waiting for the prompt to appear. I'm also getting errors in the log "write failed with 32: broken pipe" which I also saw in that forum post from 2017.
Click to expand...
Click to collapse
Are you using Adware?
Edit: @StykerB My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Homeboy76 said:
Are you using Adware?
Click to expand...
Click to collapse
Can you be specific?
-----
I don't have "adwares" but I have the same issue too. Surprisingly it persists when I reverted to last known good version. Which makes everything strange.
I could not afford a clean format at the moment. But until I have the time to do it (and hopefully it goes away), any suggestions to solve this would be extremely appreciated.
I am not using Pixel 3, but I use Nokia 6. Someone told me that it's a common Nokia issue, but being brought here at a very different device forum kind of prove a point that this is a bug that has to do with Magisk, and not Nokia-specific (or device-specific as for this case (maybe)) issue.
TechnoSparks said:
Can you be specific?
-----
I don't have "adwares" but I have the same issue too. Surprisingly it persists when I reverted to last known good version. Which makes everything strange.
I could not afford a clean format at the moment. But until I have the time to do it (and hopefully it goes away), any suggestions to solve this would be extremely appreciated.
I am not using Pixel 3, but I use Nokia 6. Someone told me that it's a common Nokia issue, but being brought here at a very different device forum kind of prove a point that this is a bug that has to do with Magisk, and not Nokia-specific (or device-specific as for this case (maybe)) issue.
Click to expand...
Click to collapse
My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Homeboy76 said:
My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Click to expand...
Click to collapse
The page didnt help with my issue unfortunately
-------------------------------
I managed to solve my issue by actually formatting everything (including data). Painful 2 hrs for me lel. Now on 6.1 Manager and 7.3 Magisk and everything works as it should.
Since I formatted data, the issue may have something to do with magisk's leftover files.
Still, the problem with 18.x and 7.0 manager will always happen if i update. Fun fact: if you play around the root settings in Magisk Mgr, you may have a luck and the root prompt will appear. Unfortunately, the root prompt will only appear for the current boot. If you reboot, the problem is there again. Use this window of freedom to grant root to your apps.
TechnoSparks said:
The page didnt help with my issue unfortunately
-------------------------------
I managed to solve my issue by actually formatting everything (including data). Painful 2 hrs for me lel. Now on 6.1 Manager and 7.3 Magisk and everything works as it should.
Since I formatted data, the issue may have something to do with magisk's leftover files.
Still, the problem with 18.x and 7.0 manager will always happen if i update. Fun fact: if you play around the root settings in Magisk Mgr, you may have a luck and the root prompt will appear. Unfortunately, the root prompt will only appear for the current boot. If you reboot, the problem is there again. Use this window of freedom to grant root to your apps.
Click to expand...
Click to collapse
Just a thought and maybe you do it but after each update instead of just directly rerooting, run the magisk uninstaller first.
Flash update
Reboot
Boot back to bootloader
Install TWRP, your phones method
Flash Magisk uninstaller.zip
Flash custom kernel if applicable
Flash magisk.zip
Reboot
Tulsadiver said:
Just a thought and maybe you do it but after each update instead of just directly rerooting, run the magisk uninstaller first.
Flash update
Reboot
Boot back to bootloader
Install TWRP, your phones method
Flash Magisk uninstaller.zip
Flash custom kernel if applicable
Flash magisk.zip
Reboot
Click to expand...
Click to collapse
Already did that too my friend. But never mind. I am done for
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.