Database Develop

Flashable OTA?

When I had my Nexus 5 people would make flashable OTA files to be used in TWRP, is no one doing this any longer? All I can find is how to sideload the OTA.
Thanks

idbl_fanatic said:
When I had my Nexus 5 people would make flashable OTA files to be used in TWRP, is no one doing this any longer? All I can find is how to sideload the OTA.
Thanks
Click to expand...
Click to collapse
just flash the boot.img and system.img in twrp. if you had root, youll need to reroot. yes, twrp flashes system.img and boot.img files now as well.

simms22 said:
just flash the boot.img and system.img in twrp. if you had root, youll need to reroot. yes, twrp flashes system.img and boot.img files now as well.
Click to expand...
Click to collapse
WOW thank you, I didn't know that TWRP did this.

simms22 said:
just flash the boot.img and system.img in twrp. if you had root, youll need to reroot. yes, twrp flashes system.img and boot.img files now as well.
Click to expand...
Click to collapse
Ok, I am a little confused, I am trying to apply the MRA58K from LMY48T OTA found here: http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 in the ZIP file, I am not finding system.img, or boot.img

Download the factory images and extract the system and boot.imgs,put them on your SD card(phone storage) enter twrp,select install,then select images in bottom right, select the partition you want to flash to, select the correct.img file
Sent from my Nexus 6 using XDA-Developers mobile app

holeindalip said:
Download the factory images and extract the system and boot.imgs,put them on your SD card(phone storage) enter twrp,select install,then select images in bottom right, select the partition you want to flash to, select the correct.img file
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Just want to double check, this will be ok to do giong from 5.1.1 to 6.0.1?

idbl_fanatic said:
Just want to double check, this will be ok to do giong from 5.1.1 to 6.0.1?
Click to expand...
Click to collapse
yup

simms22 said:
yup
Click to expand...
Click to collapse
Ok, so, I got my phone updates, however, I had systemless xposed working on it, MM 6.0.1 (MOB30M) however when I went in to try and enable the modules, it gave an error (a long one) so I thought that maybe I didn't have the correct version installed, or wasn't rooted right, so I went back into recovery, re-rooted, and installed 85.3, now it says that xposed isn't installed at all. So for now, I went back to my 5.1.1 restore. Any ideas?

idbl_fanatic said:
Ok, so, I got my phone updates, however, I had systemless xposed working on it, MM 6.0.1 (MOB30M) however when I went in to try and enable the modules, it gave an error (a long one) so I thought that maybe I didn't have the correct version installed, or wasn't rooted right, so I went back into recovery, re-rooted, and installed 85.3, now it says that xposed isn't installed at all. So for now, I went back to my 5.1.1 restore. Any ideas?
Click to expand...
Click to collapse
You have to reflash xposed. It is in the system partition so you will have to redo it after making room as google now fills up the system partition almost completely.

zelendel said:
You have to reflash xposed. It is in the system partition so you will have to redo it after making room as google now fills up the system partition almost completely.
Click to expand...
Click to collapse
I thought that was the whole reason behind the System Less Xposed, so it doesn't install to your system partition.

idbl_fanatic said:
I thought that was the whole reason behind the System Less Xposed, so it doesn't install to your system partition.
Click to expand...
Click to collapse
was the systemless updated to work with the new security measures built into the update? You have to remember that with each update google is making things like xposed harder to get working. It is well known that sooner or later xposed all together will no longer be an option.
So I would check all the changes that the update did to see what it changed. I nor most the people I know have not used xposed in a long time so I really cant say for sure

zelendel said:
was the systemless updated to work with the new security measures built into the update? You have to remember that with each update google is making things like xposed harder to get working. It is well known that sooner or later xposed all together will no longer be an option.
So I would check all the changes that the update did to see what it changed. I nor most the people I know have not used xposed in a long time so I really cant say for sure
Click to expand...
Click to collapse
That makes sense, maybe I'll go to MMB29K instead.

Systemless root or systemless exposed?
Sent from my Nexus 6 using XDA-Developers mobile app

I have systemless xposed working on mob30m. currently have v85.2 installed, all modules working. Only hiccup i ran into was the installer apk. you have to use the one linked in the systemless xposed thread, or it won't recognize the framework is installed.

putridfoetus said:
I have systemless xposed working on mob30m. currently have v85.2 installed, all modules working. Only hiccup i ran into was the installer apk. you have to use the one linked in the systemless xposed thread, or it won't recognize the framework is installed.
Click to expand...
Click to collapse
Thank you, I just reinstalled 6.0.1 MOB30M and it works!

I'm on 6.0 right now with TW recovery, root with SuperSU and Xposed v85, I want to go to 6.0.1 latest version, what would be the best was to do it?
Shall I uninstall xposed, unroot and get stock recovery and then just try to install OTA or is there another way?

cL0uD` said:
I'm on 6.0 right now with TW recovery, root with SuperSU and Xposed v85, I want to go to 6.0.1 latest version, what would be the best was to do it?
Shall I uninstall xposed, unroot and get stock recovery and then just try to install OTA or is there another way?
Click to expand...
Click to collapse
Check out Flashfire in the appstore, it let's you update with OTA, and re-root

idbl_fanatic said:
Check out Flashfire in the appstore, it let's you update with OTA, and re-root
Click to expand...
Click to collapse
Yes, used, Great job, Mr Chainfire

Oxygen OS 3.2.1 Released

Source: https://forums.oneplus.net/threads/...s-starting-on-oneplus-3.454469/#post-15056543
Usual 48h to hit devices thing is probably in effect here swell but i'm sure the VPN trick will work for most if you're impatient or waiting for this fix for your SIM issue.
The changelog seems to have added just the SIM fix but for some reason the changelog on the phone says there's more Notification fixes but have to wait and see on that
Here are some of the highlights:
Fixed some notification issues
Addressed SIM recognition issue
Enabled sRGB mode in developer options
Improved RAM management
Improved GPS performance
Enhanced audio playback quality
Updated custom icon packs
Improved camera quality/functionality
Fixed some issues in Gallery
Implemented latest Google security patches
Fixed bugs in Clock/Music apps
Thanks to @Patschi_ for the links
OTA file
http://otafs1.coloros.com/patch/ama...010-011_patch_1607052050_0e5983ace5314161.zip
Edit: MIrror:
http://www43.zippyshare.com/v/9NUHWPJ3/file.html
Edit2:
Full ROM
http://otafs.coloros.com/patch/amaz...6_OTA_011_all_1607052050_0e5983ace5314161.zip[/QUOTE]
Full ROM Mirror (Soon)

deleted.

The direct link, if anyone is interested in:
OTA file
http://otafs1.coloros.com/patch/ama...010-011_patch_1607052050_0e5983ace5314161.zip
Edit: MIrror:
http://www43.zippyshare.com/v/9NUHWPJ3/file.html
Edit2:
Full ROM
http://otafs.coloros.com/patch/amaz...6_OTA_011_all_1607052050_0e5983ace5314161.zip
Edit3:
Mirrors for all updates and ROMs are available here:
http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870

already installed 3.2.0. and its working very well
should i need to update again for 3.2.1

JumboMan said:
already installed 3.2.0. and its working very well
should i need to update again for 3.2.1
Click to expand...
Click to collapse
no notification issues?

Patschi_ said:
The direct link, if anyone is interested in: (OTA file)
http://otafs1.coloros.com/patch/ama...010-011_patch_1607052050_0e5983ace5314161.zip
Edit: MIrror:
http://www43.zippyshare.com/v/9NUHWPJ3/file.html
Click to expand...
Click to collapse
Thanks for this do you mind if I add them to the OP? not that people shouldn't see your post just might be easier i'll give credits swell.
JumboMan said:
already installed 3.2.0. and its working very well
should i need to update again for 3.2.1
Click to expand...
Click to collapse
Might swell the Changelog states there's Notification issue fixes as well but still waiting to see if that's true.

Roxas598 said:
Thanks for this do you mind if I add them to the OP? not that people shouldn't see your post just might be easier i'll give credits swell.
Click to expand...
Click to collapse
Feel free to add it to the OP
Downloading the Full ROM right now to provide a mirror... could take a while as the download servers are quite slow right now.

mirrors will be provided here aswell I think: http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870

When I'm trying to install the ota update I'm getting an error 7 in TWRP. TWRP, root and xposed are systemless. Do I have to unroot to install the OTA?

daClaus said:
When I'm trying to install the ota update I'm getting an error 7 in TWRP. TWRP, root and xposed are systemless. Do I have to unroot to install the OTA?
Click to expand...
Click to collapse
Are you using the System Update option on the phone to install or the Zip file? either way normally any changes to the system will make OTA fail (like root and xposed)

daClaus said:
When I'm trying to install the ota update I'm getting an error 7 in TWRP. TWRP, root and xposed are systemless. Do I have to unroot to install the OTA?
Click to expand...
Click to collapse
Actually no. You don't have to unroot but you need to flash stock boot.img . Better option always is to flash Full 3.2.0 ROM twice (sometimes first flash doesn't succeed) and then 3.2.0 -> 3.2.1 OTA immediately and then SuperSU and Xposed. Or wait for Full ROM mirror. Will take me some 20 minutes more. I am downloading it at the moment.

Yes, I tried to install the downloaded ota file via TWRP. Guess I have to download the whole 1.2 GB to get the 15MB update.
---------- Post added at 02:37 PM ---------- Previous post was at 02:33 PM ----------
Naman Bhalla said:
Better option always is to flash Full 3.2.0 ROM twice (sometimes first flash doesn't succeed) and then 3.2.0 -> 3.2.1 OTA immediately and then SuperSU and Xposed.
Click to expand...
Click to collapse
Thank's for the hint! Had the 3.2.0 file on my phone and did it this way.

Sledge2013 said:
no notification issues?
Click to expand...
Click to collapse
can you explained it in detail.which notification issues?

Sorry for the question, just to be clear:
I install the full ROM in twrp, install it again without rebooting and after that immediately SuperSU?
Do I have to wipe Cache/Dalvik?
After that I reboot and all the apps are still there?

Spotted this and just VPNd it my self.
Fingers crossed i get less drain over night

Der-Knuffi said:
Sorry for the question, just to be clear:
I install the full ROM in twrp, install it again without rebooting and after that immediately SuperSU?
Do I have to wipe Cache/Dalvik?
After that I reboot and all the apps are still there?
Click to expand...
Click to collapse
If you install the full 3.2.1 rom just install it once, then supersu and THEN wipe cache/dalvik. Your apps will be still there he just needs to optimize them at the start(might take 10 minutes).
If you want to use this "trick" to install 3.2.1 OTA over a 3.2.0 full rom, i have no clue. But i would rather install the full rom. I tried it with the OTA last time and it didn't worked.

eikaramba said:
If you install the full 3.2.1 rom just install it once, then supersu and THEN wipe cache/dalvik. Your apps will be still there he just needs to optimize them at the start(might take 10 minutes).
If you want to use this "trick" to install 3.2.1 OTA over a 3.2.0 full rom, i have no clue. But i would rather install the full rom. I tried it with the OTA last time and it didn't worked.
Click to expand...
Click to collapse
Ok, thanks. That's the way I used to do it since years, but I'm new to OnePlus 3, so ...

Der-Knuffi said:
Ok, thanks. That's the way I used to do it since years, but I'm new to OnePlus 3, so ...
Click to expand...
Click to collapse
me too. coming from nexus 5 some things definitely changed for us flashoholics

flashed over 3.2.0, no issues so far. supersu, xposed, adaway all is working fine.

daClaus said:
When I'm trying to install the ota update I'm getting an error 7 in TWRP. TWRP, root and xposed are systemless. Do I have to unroot to install the OTA?
Click to expand...
Click to collapse
daclaus, you have to install the complete rom via twrp, after that you have to install root and xposed again. ota will not work with twrp.

Gear 3 spay now detecting root.

We used to be able to use spay for gear by hiding spay and busybox but now we can no longer do that
I've tried everything from deleting the app.
with the latest magisk.
Anyone else?
View attachment 4587330
View attachment magisk_log_20180903_090012.log
Thanks for the help
I add logs and screenshot

TheUndertaker21 said:
We used to be able to use spay for gear by hiding spay and busybox but now we can no longer do that
I've tried everything from deleting the app.
with the latest magisk.
Anyone else?
View attachment 4587330
View attachment 4587329
Thanks for the help
I add logs and screenshot
Click to expand...
Click to collapse
Delete SPay app and install this one from APKMirror. Once it installs, make sure to hide it in Magisk. Should work.

coolhandz said:
Delete SPay app and install this one from APKMirror. Once it installs, make sure to hide it in Magisk. Should work.
Click to expand...
Click to collapse
thanks but that didn't work
it detected root

TheUndertaker21 said:
thanks but that didn't work
it detected root
Click to expand...
Click to collapse
And it says version 1.6.7406 in settings?

coolhandz said:
And it says version 1.6.7406 in settings?
Click to expand...
Click to collapse
Yeah.
What else did you do?
I know you have to remove busybox but that doesn't work anymore. Thanks again for your help.
View attachment 4588532

When I previously installed BusyBox I ran into the same trouble. I had to reflash the phone and ROM to start from scratch to erase any sign of BusyBox. After that I haven't had any issues unless I've updated SPay past version 1.6.7406. I've stayed away from BusyBox since as a result, but I've heard there are ways to hide it.

​
coolhandz said:
When I previously installed BusyBox I ran into the same trouble. I had to reflash the phone and ROM to start from scratch to erase any sign of BusyBox. After that I haven't had any issues unless I've updated SPay past version 1.6.7406. I've stayed away from BusyBox since as a result, but I've heard there are ways to hide it.
Click to expand...
Click to collapse
You're the first person who's able to use spay on gear without getting detected

If that's the case, here is my setup on my Pixel XL:
Benzo ROM 09/02
Magisk 17.1
ElementalX 4.02
TWRP 3.2.3-1
Did a clean flash of 9.0 from factory images at the start.
Attached some screenshots. Maybe you can see something different?

I don't think these loaded properly

wow, you added everything samsung
let me try that now
very helpful
i'm on note9
using phh pie rom

coolhandz said:
If that's the case, here is my setup on my Pixel XL:
Benzo ROM 09/02
Magisk 17.1
ElementalX 4.02
TWRP 3.2.3-1
Did a clean flash of 9.0 from factory images at the start.
Attached some screenshots. Maybe you can see something different?
Click to expand...
Click to collapse
i'm not sure what's wrong
this is what i got

coolhandz said:
If that's the case, here is my setup on my Pixel XL:
Benzo ROM 09/02
Magisk 17.1
ElementalX 4.02
TWRP 3.2.3-1
Did a clean flash of 9.0 from factory images at the start.
Attached some screenshots. Maybe you can see something different?
Click to expand...
Click to collapse
what plugin are you using btw?

TheUndertaker21 said:
what plugin are you using btw?
Click to expand...
Click to collapse
Gear Plug-In
Version
2.2.03.18071141N

coolhandz said:
Gear Plug-In
Version
2.2.03.18071141N
Click to expand...
Click to collapse
That's it
i was using the latest version
i forgot plugin is causing issue too
will try later today
since my watch just died
you are so helpful man
thank you

I'm sad I wasn't able to get it work.
Maybe because of project treble
Well try on stock rom
And see

saldy
couldn't get it to work on stock
finally giving up

There's gotta be a way to get spay working on root

Enable Camera 2 api on android 10. Help

Hi everyone, I need your help please .. I updated the device to android 10 and I reset the factory settings, thus losing the enable camera2api. I have the bootloader already unlocked is there a way to enable camera2 api on android 10? :crying:

Yeah. Problems here too

TonyTerry99 said:
Hi everyone, I need your help please .. I updated the device to android 10 and I reset the factory settings, thus losing the enable camera2api. I have the bootloader already unlocked is there a way to enable camera2 api on android 10? :crying:
Click to expand...
Click to collapse
+1

Patched boot Android 10
is there a way to already have the patched boot of android 10?

lol y u guys doing a factory reset after the update?
And no, stop complaining, its not a problem. it was your choice.
Have you guys already tried enabling cam2api like you did on pie? if not try doing so before making a thread

Thats the same as pie just root and install magisk then enable camera 2 api with buildprop or magisk modules

Did anyone tried https://forum.xda-developers.com/apps/magisk/module-camera2api-enabler-t3656651 ?

salmonthefish said:
lol y u guys doing a factory reset after the update?
And no, stop complaining, its not a problem. it was your choice.
Have you guys already tried enabling cam2api like you did on pie? if not try doing so before making a thread
Click to expand...
Click to collapse
Ok

Sohailsamdani said:
Ok
Click to expand...
Click to collapse
I would like to retry the same method used with android pie, but where can I find stock image boot?

TonyTerry99 said:
I would like to retry the same method used with android pie, but where can I find stock image boot?
Click to expand...
Click to collapse
Why you need a patched kernel?
Unlock bootloader
fastboot boot twrp-3.3.1-0-jasmine_sprout.img
adb push Magisk-v20.3.zip /sideload
(go to /sideload in TWRP)
Flash Magisk
Reboot
(do the same steps to enable camera2api as ou did on Pie)
You didn't even touched the system.
If you only want to boot an 'Magisk' patched boot file.
I've created this just now. magisk_patched_androi10_a2_11.0.4.0.img
Unlock bootloader
fastboot boot magisk_patched_androi10_a2_11.0.4.0.img
(do the same steps to enable camera2api as ou did on Pie)

I got it by editing build.prop
No Magisk modules worked here.

Resolved . thank you all
I solved thanks to patched boot, temporary root with magisk and activated unlocked the camera 2 bees with termux, restarted and removed the root.

On android 10 ? Gcam n stock camera no crash.... if yes please guide me, how to install gcam,.

If someone finds a Magisk module which is working, please share

TonyTerry99 said:
I solved thanks to patched boot, temporary root with magisk and activated unlocked the camera 2 bees with termux, restarted and removed the root.
Click to expand...
Click to collapse
Does the stock camera crash now? ?

Zedsdeadbaby said:
If someone finds a Magisk module which is working, please share
Click to expand...
Click to collapse
Just edit build.prop
Look for the lines with the string "HAL3" (2 lines total) and change their value form 0 to 1.
Then look for persist.vendor.camera.stats.test line and change its value to 5.

I know it's easy, but the point of having a Magisk module doing this is to be able to disable it and use the stock camera app with just a reboot.

Zedsdeadbaby said:
I know it's easy, but the point of having a Magisk module doing this is to be able to disable it and use the stock camera app with just a reboot.
Click to expand...
Click to collapse
With Magisk, do we receive Security Patch via OTA?

Zedsdeadbaby said:
If someone finds a Magisk module which is working, please share
Click to expand...
Click to collapse
Try with this:
View attachment 4929815

Thank you !
Just tried it and it's not working

booting to black screen with Mar 2020 update and Magisk stable/beta

any suggestions on how to fix this? updated to the Mar 2020, extracted the boot image, patched in Magisk, flashed, and rebooted like I have done with the previous updates, however once the device is booted up all I get is a black screen! device is still responsive as pressing the power button brings up a menu allowing me to shutdown or reset. flashing a non-modded boot allows me to use the device normally again. help!

dimm0k said:
any suggestions on how to fix this? updated to the Mar 2020, extracted the boot image, patched in Magisk, flashed, and rebooted like I have done with the previous updates, however once the device is booted up all I get is a black screen! device is still responsive as pressing the power button brings up a menu allowing me to shutdown or reset. flashing a non-modded boot allows me to use the device normally again. help!
Click to expand...
Click to collapse
Did you remove all modules prior to rooting March update?

Tulsadiver said:
Did you remove all modules prior to rooting March update?
Click to expand...
Click to collapse
@Tulsadiver no, I neglected to do that since I was able to do so previously without ever having to... any idea how to do so at this point? do I need to wait for an updated image from your thread of https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557 ?

dimm0k said:
@Tulsadiver no, I neglected to do that since I was able to do so previously without ever having to... any idea how to do so at this point? do I need to wait for an updated image from your thread of https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557 ?
Click to expand...
Click to collapse
The old one might work but I'm making a new one for you now...
Edit: here it is
https://www.androidfilehost.com/?fid=4349826312261736126

Tulsadiver said:
The old one might work but I'm making a new one for you now...
Edit: here it is
https://www.androidfilehost.com/?fid=4349826312261736126
Click to expand...
Click to collapse
woohoo! this worked... now I need to figure out which module is fscking me... while you were making this, I followed the steps in your thread to attempt to create a boot image with core only, but mine didn't work. any idea why? regardless, thank you!!

dimm0k said:
woohoo! this worked... now I need to figure out which module is fscking me... while you were making this, I followed the steps in your thread to attempt to create a boot image with core only, but mine didn't work. any idea why? regardless, thank you!!
Click to expand...
Click to collapse
Did you put the whole folder from the zip file?
ramdisk/overlay.d

Tulsadiver said:
Did you put the whole folder from the zip file?
ramdisk/overlay.d
Click to expand...
Click to collapse
hah! I'm in idiot running around with my head cut off. I just checked, I dumped that folder into the root and not into ramdisk! anyway, turns out the culprit of my issue was your mod to increase the notifications to 7! hopefully you can make an updated mod for this update when you get some time

dimm0k said:
any suggestions on how to fix this? updated to the Mar 2020, extracted the boot image, patched in Magisk, flashed, and rebooted like I have done with the previous updates, however once the device is booted up all I get is a black screen! device is still responsive as pressing the power button brings up a menu allowing me to shutdown or reset. flashing a non-modded boot allows me to use the device normally again. help!
Click to expand...
Click to collapse
I was able to update and root, but latest Magisk stable is showing ctsprofile as false. Any ideas on how to fix this?

EVR_PR said:
I was able to update and root, but latest Magisk stable is showing ctsprofile as false. Any ideas on how to fix this?
Click to expand...
Click to collapse
I don't have the link handy, but there's a gpay module fix that should fix that for you. I'm definitely able to use Google Pay now!

dimm0k said:
I don't have the link handy, but there's a gpay module fix that should fix that for you. I'm definitely able to use Google Pay now!
Click to expand...
Click to collapse
Is it the MagiskHide Props Config module the one you're talking about?

So, I can't get Magisk to patch the boot image. It crashes every time I click let's go. I was on canary, went to the stable channel, rebooted, pushed the boot file over a few times, still nothing. Any ideas?

dimm0k said:
woohoo! this worked... now I need to figure out which module is fscking me... while you were making this, I followed the steps in your thread to attempt to create a boot image with core only, but mine didn't work. any idea why? regardless, thank you!!
Click to expand...
Click to collapse
Did you figure out which module? I have the same problem.

EVR_PR said:
I was able to update and root, but latest Magisk stable is showing ctsprofile as false. Any ideas on how to fix this?
Click to expand...
Click to collapse
Same issue, here's what I'm seeing with the ctsprofile. Magisk might need to be updated to support this feature drop.

dimm0k said:
hah! I'm in idiot running around with my head cut off. I just checked, I dumped that folder into the root and not into ramdisk! anyway, turns out the culprit of my issue was your mod to increase the notifications to 7! hopefully you can make an updated mod for this update when you get some time
Click to expand...
Click to collapse
I had some stuff running. Here you go.

Tulsadiver said:
I had some stuff running. Here you go.
Click to expand...
Click to collapse
Hey Tulsadiver, does your MagiskManager pass CTSProfile or are you using a module to fix the issue of it failing?
---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------
arh2o said:
Same issue, here's what I'm seeing with the ctsprofile. Magisk might need to be updated to support this feature drop.
Click to expand...
Click to collapse
I dont have the preserve dm-verity option on nor did I have it on when I patched the boot image. Seems like that doesn't make a difference either?

EVR_PR said:
Hey Tulsadiver, does your MagiskManager pass CTSProfile or are you using a module to fix the issue of it failing?
---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------
I dont have the preserve dm-verity option on nor did I have it on when I patched the boot image. Seems like that doesn't make a difference either?
Click to expand...
Click to collapse
Mine shows it as passing. I'm using beta channel.

Weiii said:
Did you figure out which module? I have the same problem.
Click to expand...
Click to collapse
for me it was the module provided by Tulsadiver to increase the notifications to 7... I'm guessing any modules that makes changes to system files might likely be the culprit. list your modules, but all I can do is take a guess as to which one it would be

dimm0k said:
for me it was the module provided by Tulsadiver to increase the notifications to 7... I'm guessing any modules that makes changes to system files might likely be the culprit. list your modules, but all I can do is take a guess as to which one it would be
Click to expand...
Click to collapse
For me it was smali patcher, i think. Not 100% sure because I booted from Tulsadrivers once I got stuck at the Google logo, this took me into safe mode inside of magisk. Every time I would reboot (after deleting the magisk cache file) with smali patcher enabled it would get stuck. After I disabled magisk safe mode I re-installed smali patcher(re-creating the zip on my desktop). After that everything booted fine and passed all safetynet checks.

EVR_PR said:
Is it the MagiskHide Props Config module the one you're talking about?
Click to expand...
Click to collapse
No, not magisk props config. I linked the module he was referring to. Make sure during installation you hit the volume up key when it prompts you to at the end because you need to let it clear the gpay data.

1dopewrx05 said:
No, not magisk props config. I linked the module he was referring to. Make sure during installation you hit the volume up key when it prompts you to at the end because you need to let it clear the gpay data.
Click to expand...
Click to collapse
I went ahead and installed the Magisk Props config module before I read your message and that fixed the problem. Apparently Google forgot to certify this specific build for ATT (the one ending 004.A1). Thank you for your help though.