Database Info

just installed latest cm nightly from rom manager

just installed the latest cm 10 nightly from rom manager now when i boot my phone get a screen says system software not authorized by verizon wireless has been found on your phone please turn off your phone and go to the nearest verizon wireless store for help.

mikeew83 said:
just installed the latest cm 10 nightly from rom manager now when i boot my phone get a screen says system software not authorized by verizon wireless has been found on your phone please turn off your phone and go to the nearest verizon wireless store for help.
Click to expand...
Click to collapse
Did you unlock your bootloader?

yep
I rooted it then i used ezunlock went thru successfully it stated i then backed up my stock rooted and did the rest of of normal wen in to rom manager downloaded did a full wipe dalivk cache data etc and then phone installed and rebooted to that verizon warning screen talk about big brother much.

Had the same issue setting up my bro's galaxy yesterday. I had to flash back to stock via Odin and then I just redid root and unlock boot loader and haven't had issue since. Running the new d2vzw euroskank right now with no issues.

yea
I figured as much i was downloadin the files had to run out so just switched devices real fast while i fix it figure ill just start from scratch once i odin back to stock.

Marcismo55 said:
I wouldn't run the official nightlies for the time being until the data and MMS fixes get approved and merged. CVPS (Austin Dickenson) posted an Alpha 2 on his G+ with those fixes above so you would be better off running those.
Click to expand...
Click to collapse
sent from my unlocked bootloader Verizon Samsung galaxy s III

mikeew83 said:
I rooted it then i used ezunlock went thru successfully it stated i then backed up my stock rooted and did the rest of of normal wen in to rom manager downloaded did a full wipe dalivk cache data etc and then phone installed and rebooted to that verizon warning screen talk about big brother much.
Click to expand...
Click to collapse
You need to UNLOCK your bootloader not just root. the official CM is a non kexec kernel and you are still running with your locked bootloader

and fixed
just funny to me how far verizon will go to feel like big brother so to speak.

Assuming your bootloader is unlocked. I had the same thing happen the first time. Tried to use CWM, missed the suggestion of flashing TWRP from EZ Recovery. Made all the difference. Watch the video from DroidModd3rX:
Verizon Galaxy S3 Cyanogen Mod 10 Unofficial NONKEXEC Install (I can't post links yet, sorry)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SCH-I535 using xda app-developers app

is it suitable for daily use??

jasembiz said:
is it suitable for daily use??
Click to expand...
Click to collapse
Depends on what you use the phone for. NFC still isn't working, which affects me. I hear NFL Mobile and some of the video apps like netflix aren't working.
Other than that, it's stable and fast.

I had more then just those issues, apparently my phone was sending doubles text messages, also WiFi struggled to keep a solid signal, data also dropped in and out and last but not least screen would flicker. Did a clean install of the nightly build and alpha build and had the same issues.
Sent from my SCH-I535 using xda app-developers app

jasembiz said:
is it suitable for daily use??
Click to expand...
Click to collapse
I am happy with it. It has rebooted twice on me, once after an hour and a half phone call with Dell tech support, I was tired of talking to the guy anyway . But jelly bean is nice, if you don't need NFC, MMS, or Flash (can't get my side load to work). Guess it is all in the eye of the beholder, if you don't mind some of those issues is suitable.
Sent from my SCH-I535 using xda app-developers app

Mms is working fine as well as flash. What build are you on?
SGS3 production

zxsix said:
Depends on what you use the phone for. NFC still isn't working, which affects me. I hear NFL Mobile and some of the video apps like netflix aren't working.
Other than that, it's stable and fast.
Click to expand...
Click to collapse
Not quite stable. It suffers from reboots for some during/after calls..... Me for one. The original alpha build never showed that symptom. Also a lot of people are saying that they are having echo problems on calls.
TAPPED in on my (now unlocked bootloader) Verizon S3

Did the same thing
jasembiz said:
is it suitable for daily use??
Click to expand...
Click to collapse
I'm hosed. I have been trying to fix it with Odin but I don't know Odin well enough. I ran the stock root rom and then synergy. Last night I locked it by using the CW app instead of the manual method. Dang. How do I return to stock? Anyone? I used Odin to download the rooted rom, and had no issues with TWRP. I should have known better than to use CW recovery app and the CW recovery.

Nice !

same issue
bluetoast said:
I'm hosed. I have been trying to fix it with Odin but I don't know Odin well enough. I ran the stock root rom and then synergy. Last night I locked it by using the CW app instead of the manual method. Dang. How do I return to stock? Anyone? I used Odin to download the rooted rom, and had no issues with TWRP. I should have known better than to use CW recovery app and the CW recovery.
Click to expand...
Click to collapse
Hi. I downloaded and installed the nightly CyanogenMod 10 build and on reboot I'm getting the same error: System software not authorized by Verizon. How did you get past this?

rmcneely said:
Hi. I downloaded and installed the nightly CyanogenMod 10 build and on reboot I'm getting the same error: System software not authorized by Verizon. How did you get past this?
Click to expand...
Click to collapse
derp....unlock your bootloader!

droidstyle said:
derp....unlock your bootloader!
Click to expand...
Click to collapse
but how?? can't get past this unauthorized software screen

[Q] Screenlock not working?

Hey all,
first of all I would like to say thank you for all for the great job you do in here. It's really awesome I don't have to depend on mobile carrier companies (who always a year late with updates ) and i can take care of my phone myself.
The reason I'm posting here is a problem what I can simply cannot resolve, however i search over the forums.
My problem is lockscreen / screenlock simply not working. Its working on 2.3.6. but not on 4.0.4, I did try I9103XXLQ7 as it is originaly and with flashed over with MAZEL's great rom but no luck. Also i flashed I9103XXLQ9 and tried and after screen lock not worked here either i flashed over BlueBerry ROM 2.1a, but again, no luck. I always do factory reset, wipe cache and dalvik cache still, simply not working.
I did try other locker softwares like holo locker and go locker but I came across a very interesting problem with them, they work fine until my morning alarm would start since somehow the 3rd party locker softwares blocking the alarm clock to start. Simply nothing happening, no wake up sound no light nothing until I touch the phone then suddenly it wakes up. It's not a good way, i get late from work a few times of because of this problem not to mention i miss the snooze option
Can anyone help me please and let me know if this a factory software issue and if it is how to get over it (even with 3rd party software which is not affecting the alarm clock)?
I live in Hungary, got this phone from a friend.
Thanks for everyone and sorry if this was posted elsewhere, i was searching but did not found.

Did you look into Settings->Security->Screen Lock? (I'm not sure if this is that option on stock ICS, but it should be.) Maybe it's set to 'None'. It should not be set to none if you always wipe data.

Adam77Root said:
Did you look into Settings->Security->Screen Lock? (I'm not sure if this is that option on stock ICS, but it should be.) Maybe it's set to 'None'. It should not be set to none if you always wipe data.
Click to expand...
Click to collapse
yeah, i did check there, i can set anything still nothing happens, if i set pin or pattern or even password it will be still nothing asked when closed and opened the phone.
If i set for example PIN and i lock the phone with button and open it again still no pin pass asked (immediatelly goes to home screen) but when i go to settings / security the default setting shown is pin... its like totally ignore anything i set
I did try to set none the reboot then set pin then reboot, same results... also same results with even and pattern security.

应该是软件冲突了。你把锁屏软件的都卸载了。然后在锁屏里从新设置试试。我以前也碰到过，

This guy is saying that "I've come across, this Should be a software conflict. You uninstall software lock screen. Try and set new lock screen."

Maybe..
Go back to Stock GB.
Then reflash your phone to stock ICS??
Tried this??
Sent from my GT-I9103 using xda premium

mj.vikram said:
This guy is saying that "I've come across, this Should be a software conflict. You uninstall software lock screen. Try and set new lock screen."
Click to expand...
Click to collapse
Ty for translate the strange is even a full clean 4.0.4 install has no working screen lock so i dont really know what to uninstall then.

DeepankarS said:
Maybe..
Go back to Stock GB.
Then reflash your phone to stock ICS??
Tried this??
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
yeah, did try, on GB it's working fine...the strange thing is when is reflash GB it starts with the usual welcome screen (flashing GB with odin) set up account etc etc. but when i flash ICS (even after factory reset/cache wipe) it starts the system without the usual start screen... no welcome set you google acc or anything (i flash ICS in Odin too). somehow i got the idea it has something to do with the screen lock.
But is there any cleaner install then flash with ODIN? or should i try other factory FW to flash?

No. Use Odin v1.85
Maybe you should try downloading the STOCK ICS again.
Buddy try XWLP2 POLAND stock rom. As it is one of the latest and most stable stock ics rom with some bugs being corrected.
Our buddy kataria.vikesh has made a thread regarding this too "FROM WHERE TO DOWNLOAD" AND "HOW TO FLASH"
Maybe it will help.
Sent from my GT-I9103 using xda premium

DeepankarS said:
No. Use Odin v1.85
Maybe you should try downloading the STOCK ICS again.
Buddy try XWLP2 POLAND stock rom. As it is one of the latest and most stable stock ics rom with some bugs being corrected.
Our buddy kataria.vikesh has made a thread regarding this too "FROM WHERE TO DOWNLOAD" AND "HOW TO FLASH"
Maybe it will help.
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1983262
[FAQ][GUIDE] "How to Flash" & "From where to Download"
Sent from my GT-I9103 using Tapatalk 2

Thanks for everyone for the tips. I did flash XWLP2 yesterday, the screenlock situation is the same (no mather what i set, not working) however the 3rd party locker apps seems to work now. I did try a few times and it looks the alarm can work together with the locker app so at the moment it looks like the problem is at solved to a level where I can live with it
I do continue to experiment, strange no one came accross this problem. Also interesting and don't know why happening, there is no welcome screen at fresh install at ICS and I think that is part of the problem. It starts and GB and there the lock working fine. On ICS the system just loading like it was loaded before or something.

dodoka313 said:
Thanks for everyone for the tips. I did flash XWLP2 yesterday, the screenlock situation is the same (no mather what i set, not working) however the 3rd party locker apps seems to work now. I did try a few times and it looks the alarm can work together with the locker app so at the moment it looks like the problem is at solved to a level where I can live with it
I do continue to experiment, strange no one came accross this problem. Also interesting and don't know why happening, there is no welcome screen at fresh install at ICS and I think that is part of the problem. It starts and GB and there the lock working fine. On ICS the system just loading like it was loaded before or something.
Click to expand...
Click to collapse
if you can then flash MIUI locker for the same. it has tonnes of themes for locker & has great theme.
Here is mine
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Still not working 100% but i'm getting there one thing came to my mind, is there any ICS firmware with .pit and other files? i just use md5 file in pda at Odin, maybe thats causing the problem (which doesn't make sense since the GB software is md5 too but im desperate to find a solution).
I do found flasher+pit file in sammobile, odin 1.87 and a pit file was in the package but not sure I can use .pit and md5 file without the modem and csc...
Lock screen working (go locker now) but still the alarm clock not always working or if it does start few minutes +- as set and snooze not working at 50% of the time..

Buddy pit files are for advanced users who want to play around with their partition table. It could mess up your partitions if you don't know what you are doing. Be careful.

The-Droidster said:
Buddy pit files are for advanced users who want to play around with their partition table. It could mess up your partitions if you don't know what you are doing. Be careful.
Click to expand...
Click to collapse
Yes buddy, I did that with my Samsung Galaxy 3 aka apollo (indian version with i5801 like i9103 for R). I have changed it with Europe's Galaxy 3 ( i5800). Hence my warranty void for life time.

Buddy go to the SSC then.
They will solve this problem for sure
Only if your phone is still under warranty
Sent from my GT-I9103 using xda premium

what is it happen ?
---------- Post added at 12:47 AM ---------- Previous post was at 12:43 AM ----------
what is the slove choice

[How to] Get rid of the samsung custom boot image

I used Triangle away to reset custom flash counter, both on a stock rooted rom and on goldeneye rom, and both times I was able to get rid of the stupid samsung custom logo with the picture of an unlocked lock.
1. Install triangle away
2. Click reset flash counter (even if it says counter: 0) i think this happens when you have only flashed 1 rom, sometimes under status is shows official but when it boots it says custom.
3. Reboot and enjoy looking at the official S4 logo
4. Profit
It was really bothering me so I found a way to get rid of it, and I thought that I'd share it with you guys.
Edit: Added img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

insaneshan3 said:
I used Triangle away to reset custom flash counter, both on a stock rooted rom and on goldeneye rom, and both times I was able to get rid of the stupid samsung custom logo with the picture of an unlocked lock.
1. Install triangle away
2. Click reset flash counter (even if it says counter: 0) i think this happens when you have only flashed 1 rom, sometimes under status is shows official but when it boots it says custom.
3. Reboot and enjoy looking at the official S4 logo
4. Profit
Not sure if this will help anyone or if the boot logo was there to let you know that you can use a custom boot image, but it was really bothering me so I found a way to get rid of it, and I thought that I'd share it with you guys.
Click to expand...
Click to collapse
While obviously keeping in mind that bad things MAY occur with Triangle Away, of course. Use at own risk.

Could I use ktoonsez kernel with this or?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

insaneshan3 said:
I used Triangle away to reset custom flash counter, both on a stock rooted rom and on goldeneye rom, and both times I was able to get rid of the stupid samsung custom logo with the picture of an unlocked lock.
1. Install triangle away
2. Click reset flash counter (even if it says counter: 0) i think this happens when you have only flashed 1 rom, sometimes under status is shows official but when it boots it says custom.
3. Reboot and enjoy looking at the official S4 logo
4. Profit
Not sure if this will help anyone or if the boot logo was there to let you know that you can use a custom boot image, but it was really bothering me so I found a way to get rid of it, and I thought that I'd share it with you guys.
Click to expand...
Click to collapse
+1 It worked for me after using CASUAL on my S4 (CUAMDL) right out of the box! {removed the "open lock" almost instantly!}
Thanks for the tip!

alternatively, install SuperSU as your su app, let it install binaries, then uninstall whatever other app you were using (it does this automatically), and reboot a few times. Unlocked icon will go away.
No risk of issues from triangle away.

Will this work on non-stock?
Sent from my Galaxy Nexus using Tapatalk 4 Beta

jova33 said:
Will this work on non-stock?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Only if the non-stock you are running identifies the device properly. In other words, if you run triangle and it says a different model, do not continue, it will brick, but if it shows the correct device model, go for it.

No dice. I'm on VZW, SCH-I545, it identifies the device properly, says it's going to reboot into Odin mode, reboots, get the blue text at the top that says booting into recovery, then skips to boot animation.
Sent from my SCH-I545 using Tapatalk 4 Beta

cegna09 said:
alternatively, install SuperSU as your su app, let it install binaries, then uninstall whatever other app you were using (it does this automatically), and reboot a few times. Unlocked icon will go away.
No risk of issues from triangle away.
Click to expand...
Click to collapse
Tried this and no luck.
How well known and acknowledged is this procedure?
Anything I can do differently?

seanpr123 said:
Tried this and no luck.
How well known and acknowledged is this procedure?
Anything I can do differently?
Click to expand...
Click to collapse
I found it through a google search, and it worked perfectly for me. Took about 3-4 reboots, and then the lock icon went away. I'm just running stock rooted software, not sure how it works with other software.
here's the thread
http://forum.xda-developers.com/showthread.php?t=2257058

cegna09 said:
I found it through a google search, and it worked perfectly for me. Took about 3-4 reboots, and then the lock icon went away. I'm just running stock rooted software, not sure how it works with other software.
here's the thread
http://forum.xda-developers.com/showthread.php?t=2257058
Click to expand...
Click to collapse
Ahh ok, do you have a custom recovery?
I'm running TWRP & custom ROM, that must be why.

seanpr123 said:
Tried this and no luck.
How well known and acknowledged is this procedure?
Anything I can do differently?
Click to expand...
Click to collapse
That method seemed to work for some and not for others, with no discernible reason why.
I was stock rooted with stock recovery when I tried it and never did manage to get the custom screen to go away. Thankfully, I realized I could care less about it and went on with my life!

I received an update last night

So I got an update last night on my J7 2016 with MetroPCS. I wanna update it, but I'm rooted and don't wanna screw anything up. Should I take the update, or hold off? Thanks in advance
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

It is nothing important, as samsung says, overall improvement, what is bothering me is how did you get that update since you are rooted

I also received this update yesterday. I spoke with T-Mobile. They told me it was an update from Google. They also told me that I was one of the few customers out of the thousands to receive it. It was not in their system they had to update it themselves. Still kinda sketchy.

Ragazzza said:
It is nothing important, as samsung says, overall improvement, what is bothering me is how did you get that update since you are rooted
Click to expand...
Click to collapse
I have no clue. The same thing happened twice when I had my LG G Stylo with the same company. It's kinda weird. I guess I'll just hold off on the update until further notice. Thanks though

SuperSancho said:
I also received this update yesterday. I spoke with T-Mobile. They told me it was an update from Google. They also told me that I was one of the few customers out of the thousands to receive it. It was not in their system they had to update it themselves. Still kinda sketchy.
Click to expand...
Click to collapse
It was from one of them though, so I guess I can trust it somewhat, but I don't wanna update it with a risk of screwing this phone up. I guess I can hold off for a bit

Yeah, this update bricked my device. SM-J700T.
Accidentally allowed it when clearing the annoying notification while watching youtube. Failed to flash properly. Somehow flashed a new sboot.img still. Tried to reinitialize with smart switch, but its still only listing apk6, and the update managed to only flash the sboot.img from AQC3, so i cant go back to APK6.
I tried as well with the AP from sammobile, and now have unknown baseband and invalid imei. Well, I'm 6 days away from my jump anyways, but I'd rather stick with this phone a while longer.
Any thoughts or advice? It boots, and it shows apk6 for build.
Hell, If any of you have the update.zip, I might be able to fix it still. I pulled the update from cache I thought, but it seems to be corrupt. Hell, maybe that was the problem? Maybe I can pop the update on sd (if anyone has it and would be willing to share?) and use stock recovery to flash it, and see what happens?
Thanks for any input.
EDIT: I have a friend with the same device, who was unrooted and on the new update. He wanted his rooted anyways, so I installed twrp, and used it to pull a backup of the system image, the radio image, the cache image, and used those to restore my phone. All is good. We're both on the last update, rooted and feelin good.

social.catastrophe said:
Yeah, this update bricked my device. SM-J700T.
Accidentally allowed it when clearing the annoying notification while watching youtube. Failed to flash properly. Somehow flashed a new sboot.img still. Tried to reinitialize with smart switch, but its still only listing apk6, and the update managed to only flash the sboot.img from AQC3, so i cant go back to APK6.
I tried as well with the AP from sammobile, and now have unknown baseband and invalid imei. Well, I'm 6 days away from my jump anyways, but I'd rather stick with this phone a while longer.
Any thoughts or advice? It boots, and it shows apk6 for build.
Hell, If any of you have the update.zip, I might be able to fix it still. I pulled the update from cache I thought, but it seems to be corrupt. Hell, maybe that was the problem? Maybe I can pop the update on sd (if anyone has it and would be willing to share?) and use stock recovery to flash it, and see what happens?
Thanks for any input.
EDIT: I have a friend with the same device, who was unrooted and on the new update. He wanted his rooted anyways, so I installed twrp, and used it to pull a backup of the system image, the radio image, the cache image, and used those to restore my phone. All is good. We're both on the last update, rooted and feelin good.
Click to expand...
Click to collapse
Good to know man. one of my friends almost updated it on accident, i was lucky to pull the battery on time. Thanks for that

Juncojam said:
Good to know man. one of my friends almost updated it on accident, i was lucky to pull the battery on time. Thanks for that
Click to expand...
Click to collapse
Glad to help! Or glad to suffer a problem so you don't have to, maybe?

social.catastrophe said:
Glad to help! Or glad to suffer a problem so you don't have to, maybe?
Click to expand...
Click to collapse
Lol that also works:good:

Google Pay alerted me it's not working because of root?

Hi.
Some weeks ago I did unlocked the bootloader and got magisk working and also rooted the phone. I have been using Google Pay since that. Today I went into settings and checked phone for new update. But it was the latest update. I pressed the three dots and selected "Download latest package" and the phone restarted in twrp after that but said it failed to update once the phone was restarted. After this I went to buy some food with Google Pay and it was working. Got home and now I got a pop-up window looking like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I then went into Magisk Manager and it says Magisk is not installed? It has been installed? Super SU says my phone is not rooted? So what strange things has happened?
I tried to install magisk again in magisk manager but it fails doing that.
Any ideas how to solve this? I really need Google Pay to work.

You can try Install Magisk.zip in TWRP again

EDIT:
I installed Magisk using TWRP now (had to flash twrp again using adb). It's strange however that I was not rooted yesterday but Google Pay does not work because it thinks I'm rooted?
So now Magisk Manager says Magisk is installed, and it seems that Google Pay is working again!
Also King Go Root says my phone is rooted now again. (which it was prior to yesterday)
So what really happend then with my phone yesterday? I just want to understand why Magisk was gone, and the phone was unrooted and TWRP gone? Was it because I did try to download and install the package from the phone system update? (which failed anyway, and I did pay with my card after that). This popup just appeared when the phone was picked up before I went to sleep. Any ideas?

Akerhage said:
EDIT:
I installed Magisk using TWRP now (had to flash twrp again using adb). It's strange however that I was not rooted yesterday but Google Pay does not work because it thinks I'm root....
Click to expand...
Click to collapse
I am not sure what happened, but tale a look at this:
https://www.xda-developers.com/magisk-no-longer-hide-bootloader-unlock-status/

MacGuy2006 said:
I am not sure what happened, but tale a look at this:
https://www.xda-developers.com/magisk-no-longer-hide-bootloader-unlock-status/
Click to expand...
Click to collapse
Wow, thats bad news. Is there any way to lock the bootloader again?
For me, there was no point of unlocking and root the device anyway. (I thought that the Mi Note 10 would have more custom roms without Xiaomi bloat)
And I really need Google Pay to work, because I do not take my pay-card with me. So if a rooted and unlocked phone will cause this to spontaneously fail, it would cause a lot of problems for me.
However, strange that a re-install of magisk made the problem go away? If its a hardware-level key attestation my phone would be blocked even after a re-installation right?
If checking the Safety-Net status right now, Im passed.

Akerhage said:
... However, strange that a re-install of magisk made the problem go away? If its a hardware-level key attestation my phone would be blocked even after a re-installation right?
If checking the Safety-Net status right now, Im passed.
Click to expand...
Click to collapse
Yeah, this is why I am waiting for the OTA. It's good that it's working for you, but it's likely that it will end sometime in the not too distant future.

MacGuy2006 said:
Yeah, this is why I am waiting for the OTA. It's good that it's working for you, but it's likely that it will end sometime in the not too distant future.
Click to expand...
Click to collapse
The same error happend again to me today, so is there any way for me to maybe undo the unlock-thing that makes google pay not working?