Running stock ROM not rooted, getting this error? .. bootloader is unlocked though
Google has Google pay check for an unlocked bootloader. If you are unlocked it will fail, you do not have to be rooted just bootloader unlocked for Safteynet to fail. You might as well install Magisk and let it hide that you are unlocked and rooted if you wish to use Google Pay. If you do not want to root, then just relock the bootloader, JUST MAKE SURE YOU HAVE THE STOCK RECOVERY AND NO CUSTOM RECOVERY INSTALLED. Otherwise you will brick your device. Also, be aware that relocking your bootloader will wipe all internal data off the phone so backup any photos, files, anything of importance before relocking bootloader.
Eric214 said:
Google has Google pay check for an unlocked bootloader. If you are unlocked it will fail, you do not have to be rooted just bootloader unlocked for Safteynet to fail. You might as well install Magisk and let it hide that you are unlocked and rooted if you wish to use Google Pay. If you do not want to root, then just relock the bootloader, JUST MAKE SURE YOU HAVE THE STOCK RECOVERY AND NO CUSTOM RECOVERY INSTALLED. Otherwise you will brick your device. Also, be aware that relocking your bootloader will wipe all internal data off the phone so backup any photos, files, anything of importance before relocking bootloader.
Click to expand...
Click to collapse
Magisk hide won't hide it. Alot of apps not able to avail of the hide function.
hallo dare said:
Magisk hide won't hide it. Alot of apps not able to avail of the hide function.
Click to expand...
Click to collapse
Strange... on my OP 6 with unlocked bootloader and Magisk root, Google Pay runs fine. And even Magisk Hide was not enabled for Google Pay (now it is).
hallo dare said:
Magisk hide won't hide it. Alot of apps not able to avail of the hide function.
Click to expand...
Click to collapse
What are you talking about? I've been using Magisk with passing safetynet since it came out a couple years ago. I just used Google Pay times today with no issues.
The issue is Google will fail Safetynet if you just have an unlocked bootloader and no magisk installed to pass the safetynet checks.
Eric214 said:
What are you talking about? I've been using Magisk with passing safetynet since it came out a couple years ago. I just used Google Pay times today with no issues.
The issue is Google will fail Safetynet if you just have an unlocked bootloader and no magisk installed to pass the safetynet checks.
Click to expand...
Click to collapse
What I'm talking about is what I'm experiencing. I've magisk installed, Google Pay is ticket to magisk hide, along with other apps, and they all detect root
hallo dare said:
Magisk hide won't hide it. Alot of apps not able to avail of the hide function.
Click to expand...
Click to collapse
please dont give users the wrong impression
Magisk DOES hide it.
i have an unlocked bootloader, TWRP, MAGISK, and a custom kernel installed
and ive been using google pay for the past week without issues.
Why would I give users wrong impression? It's happening to me!!! Just because it doesn't happen to you or others then it cannot be true?
I've also an unlocked bootloader, TWRP and Magisk installed and Magisk is not hiding specific apps. Simple as that.
hallo dare said:
What I'm talking about is what I'm experiencing. I've magisk installed, Google Pay is ticket to magisk hide, along with other apps, and they all detect root
Click to expand...
Click to collapse
Then Magisk must not be installed properly. You must have done something wrong is all I can think of. I use Google pay 2-5 times a day without issue and on the OnePlus 6 since launch, zero issues.
Eric214 said:
Then Magisk must not be installed properly. You must have done something wrong is all I can think of. I use Google pay 2-5 times a day without issue and on the OnePlus 6 since launch, zero issues.
Click to expand...
Click to collapse
I've gone and done a complete format and re-installation of everything and the same issue is present.
hallo dare said:
I've gone and done a complete format and re-installation of everything and the same issue is present.
Click to expand...
Click to collapse
Maybe delete the Magisk APK/zip you have and download a fresh copy then.
Eric214 said:
Maybe delete the Magisk APK/zip you have and download a fresh copy then.
Click to expand...
Click to collapse
Done that, but made no difference. Just reading on another thread that it appears to be an issue for many.
Magisk Hide works fine out of the box (no alterations) with Google Pay for me.
Historically, when it fails it's because Magisk is out of date.
hallo dare, if you want help, post your Magisk Manager's landing page, then another of your test results. Past that, you should head over to the Magisk XDA thread.
Edit:
I guess I forgot to mention I am on the BETA channel - so not exactly without alteration.
Orito said:
Magisk Hide works fine out of the box (no alterations) with Google Pay for me.
Historically, when it fails it's because Magisk is out of date.
hallo dare, if you want help, post your Magisk Manager's landing page, then another of your test results. Past that, you should head over to the Magisk XDA thread.
Edit:
I guess I forgot to mention I am on the BETA channel - so not exactly without alteration.
Click to expand...
Click to collapse
Thanks Orito,
Yeah I'll do just that. Can you please post the magisk you flashed and I'll try it please.
I flashed the 16.4.
I'm running 16.42. In Magisk.
Open Magisk Manager.
Menu.
Settings.
Update Channel -> Beta
Check for Updates -> Enabled
Close Magisk Manager completely.
Reopen.
Orito said:
I'm running 16.42. In Magisk.
Open Magisk Manager.
Menu.
Settings.
Update Channel -> Beta
Check for Updates -> Enabled
Close Magisk Manager completely.
Reopen.
Click to expand...
Click to collapse
Exactly what I've been doing. Thanks
Related
Google pay still does not let me pay in stores, because I have root. I have Blu_spark with Magisk and enabled Magisk Hide on Gpay
What can I do?
Thank you!
Try to use Magisk Canary, It's working for me
Magisk Settings: "Update Channel" to "Custom" and paste
https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/canary.json into the box, restart Magisk and install the update.
https://forum.xda-developers.com/oneplus-6/help/google-pay-magisk-hide-t3912914
The search part of the forum is actually really good! Give is a shoot might be some info in the link
whizeguy said:
https://forum.xda-developers.com/oneplus-6/help/google-pay-magisk-hide-t3912914
The search part of the forum is actually really good! Give is a shoot might be some info in the link
Click to expand...
Click to collapse
If problem not solved, please try this:
https://www.teamandroid.com/2018/07/18/use-google-pay-rooted-android-phones
I suffered same problem with new google play version and my rooted S4 mini , in PIE, OREO and Nougat indeed, and it was fixed.
Magisk Core mode works, but using Magisk beta v19 with Magisk Hide works perfectly too !
I really really miss exposed and I really don't want to root as besides exposed I personally have no need to. I just can't seem to get virtual exposed up and running. Along with not finding and good hot to videos on YT. I get it installed and everything just no luck with actual installing module for some reason. TIA for all help or input
if you root with magisk there is a module for xposed framework but it looks old and it says it won't be updated and I haven't tried it
spart0n said:
if you root with magisk there is a module for xposed framework but it looks old and it says it won't be updated and I haven't tried it
Click to expand...
Click to collapse
If I rooted I wouldn't need to run virtual or magisk I could just run Xposed. I just don't want to root as it's easier for OTA without root. Especially seeing how often updates are coming for this phone since it got released.
lg3FTW said:
If I rooted I wouldn't need to run virtual or magisk I could just run Xposed. I just don't want to root as it's easier for OTA without root. Especially seeing how often updates are coming for this phone since it got released.
Click to expand...
Click to collapse
I don't see how you can get xposed running without being rooted but I am a noob at this still lol
spart0n said:
I don't see how you can get xposed running without being rooted but I am a noob at this still lol
Click to expand...
Click to collapse
It's called virtual Xposed. It's what my post is mostly about getting it running on the phone. No worries we are all rookies one time or another
lg3FTW said:
It's called virtual Xposed. It's what my post is mostly about getting it running on the phone. No worries we are all rookies one time or another
Click to expand...
Click to collapse
I understand your desire not to root, but the only downside to rooting wousl be security, and magisk keeps security intact. Edxposed (unoffical Xposed for Android P) works perfectly fine in magisk.10/10 would recommend. Plus magisk has methods for maintaining root after OTAs
Cm4nXD said:
I understand your desire not to root, but the only downside to rooting wousl be security, and magisk keeps security intact. Edxposed (unoffical Xposed for Android P) works perfectly fine in magisk.10/10 would recommend. Plus magisk has methods for maintaining root after OTAs
Click to expand...
Click to collapse
I bought the unlocked model for root truly but I haven't rooted a phone in 3 years since my LG g3 and g4 and for some reason I can't seem to wrap my head around easiest and safest way to root the OP7 . Don't want to break it. Nicest phone I've ever owned.
There's a tool by the guy who maintains TWRP for the phone. It's called tool all in one and can unlock and root your phone with a simple GUI. OTAs are almost as simple as stock, just 2gig files instead of ~500mb. It's just download from oxygen updater, settings local install, TWRP retention script, Magisk inactive slot install, reboot
Arden144 said:
There's a tool by the guy who maintains TWRP for the phone. It's called tool all in one and can unlock and root your phone with a simple GUI. OTAs are almost as simple as stock, just 2gig files instead of ~500mb. It's just download from oxygen updater, settings local install, TWRP retention script, Magisk inactive slot install, reboot
Click to expand...
Click to collapse
All that seems amazing and I love the tool kits made for other devices heck I remember rooting GB when it was a one click app just to root your device. Miss those days. I'll have to search more as you really lost me with this part.
It's just download from oxygen updater, settings local install, TWRP retention script, Magisk inactive slot install, r
lg3FTW said:
All that seems amazing and I love the tool kits made for other devices heck I remember rooting GB when it was a one click app just to root your device. Miss those days. I'll have to search more as you really lost me with this part.
It's just download from oxygen updater, settings local install, TWRP retention script, Magisk inactive slot install, r
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...fully-upgraded-to-9-5-7-t3937414/post79679795
Have you tried TaiChi? It's an alternative to virtual exposed.
lg3FTW said:
All that seems amazing and I love the tool kits made for other devices heck I remember rooting GB when it was a one click app just to root your device. Miss those days. I'll have to search more as you really lost me with this part.
It's just download from oxygen updater, settings local install, TWRP retention script, Magisk inactive slot install, r
Click to expand...
Click to collapse
I don't think you even need the all in one GUI. It's a very simple process.
Kinda Easy to follow Guide
MORE COMPREHENSIVE GUIDE
spart0n said:
if you root with magisk there is a module for xposed framework but it looks old and it says it won't be updated and I haven't tried it
Click to expand...
Click to collapse
Yes, but there's EdXposed which is compatible and works flawlessly with Safety net. Not all modules work but that's an Android Pie incompatibility issue, not an Xposed problem.
---------- Post added at 17:13 ---------- Previous post was at 17:09 ----------
lg3FTW said:
I bought the unlocked model for root truly but I haven't rooted a phone in 3 years since my LG g3 and g4 and for some reason I can't seem to wrap my head around easiest and safest way to root the OP7 . Don't want to break it. Nicest phone I've ever owned.
Click to expand...
Click to collapse
It was amazingly easy. You just enable developer option, select enable OEM unlocking, back everything up (the phone will get factory reset) and advanced reboot, hook it up to your computer, reboot to bootloader, and then fastboot OEM unlock, reboot your phone to make sure the warning appears and reinitialise the system (since your phone did just get reset), reboot to bootloader, fastboot boot twrp.img, optionally flash the twrp installer, and flash Magisk. Done. Rooted. After installing OTAs, but before rebooting, use the install to slot B option in Magisk manager.
Lirannl said:
Yes, but there's EdXposed which is compatible and works flawlessly with Safety net. Not all modules work but that's an Android Pie incompatibility issue, not an Xposed problem.
---------- Post added at 17:13 ---------- Previous post was at 17:09 ----------
It was amazingly easy. You just enable developer option, select enable OEM unlocking, back everything up (the phone will get factory reset) and advanced reboot, hook it up to your computer, reboot to bootloader, and then fastboot OEM unlock, reboot your phone to make sure the warning appears and reinitialise the system (since your phone did just get reset), reboot to bootloader, fastboot boot twrp.img, optionally flash the twrp installer, and flash Magisk. Done. Rooted. After installing OTAs, but before rebooting, use the install to slot B option in Magisk manager.
Click to expand...
Click to collapse
Do you know if TMobile one plus 7 pro be rooted as well? I've seen people say yes and people say no. Which carrier do you have?
oregonhynita said:
Do you know if TMobile one plus 7 pro be rooted as well? I've seen people say yes and people say no. Which carrier do you have?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/how-to-convert-tmobile-op7-to-t3935947
oregonhynita said:
Do you know if TMobile one plus 7 pro be rooted as well? I've seen people say yes and people say no. Which carrier do you have?
Click to expand...
Click to collapse
I've been told you can, but I don't have one of those. Carriers are mostly irrelevant outside of the US (and I live outside of the US myself). I use the international, carrier agnostic model (1917).
Rooted, bootloader unlocked, latest magisk and edxposed.
Security for a really good game is tripped and force closes randomly during play, not saving what you did.
Core only mode, no go
Magisk hide no go
Edxposed modules and blacklist, no go.
Read that Google checks if bl is unlocked now so impossible to truly hide, I think this app may also use that info.
Can I keep root and relock bl?
Better app at hiding root from other apps?
Anything I'm just not seeing?
Not good at root without twrp, so weird lol.
Any advice would be much appreciated
Idk if you've figured your problem out but I was having the same issue with a couple of games. Do like you were doing by enabling core mode, magisk hide any app on your phone that requires root, and also hide magisk manager. After all that restart your phone and you should be good to go
bobbyp1086 said:
Rooted, bootloader unlocked, latest magisk and edxposed.
Security for a really good game is tripped and force closes randomly during play, not saving what you did.
Core only mode, no go
Magisk hide no go
Edxposed modules and blacklist, no go.
Read that Google checks if bl is unlocked now so impossible to truly hide, I think this app may also use that info.
Can I keep root and relock bl?
Better app at hiding root from other apps?
Anything I'm just not seeing?
Not good at root without twrp, so weird lol.
Any advice would be much appreciated
Click to expand...
Click to collapse
Where did you get exposed module
For some reason I cannot find it for my Moto g stylus
Or how to install it.
Ljw4884 said:
Where did you get exposed module
For some reason I cannot find it for my Moto g stylus
Or how to install it.
Click to expand...
Click to collapse
It's gotten trickier, but it's been tricky ever since Lolipop; the trickiness just changes, and it JUST CHANGED AGAIN as a matter of fact... If you don't see a thread by me on how to get it going in the Guides section in the next few days, please remind me. I've got bigger fish to fry right now, though. I just got this phone and I tried Omni and Havoc so far on it. I came to see if there's a fix for the screen record issue in Havoc. I thought it said a new kernel had fixed it. Remind me and I'll probably make a YouTube video tutorial about Xposed (actually Edxposed) in Android 10 to celebrate getting my screen recording to work.
arkansawdave74 said:
It's gotten trickier, but it's been tricky ever since Lolipop; the trickiness just changes, and it JUST CHANGED AGAIN as a matter of fact... If you don't see a thread by me on how to get it going in the Guides section in the next few days, please remind me. I've got bigger fish to fry right now, though. I just got this phone and I tried Omni and Havoc so far on it. I came to see if there's a fix for the screen record issue in Havoc. I thought it said a new kernel had fixed it. Remind me and I'll probably make a YouTube video tutorial about Xposed (actually Edxposed) in Android 10 to celebrate getting my screen recording to work.
Click to expand...
Click to collapse
Please let me know when you do. I'll definitely check it out and thumbs up the video
Thank you
Ljw4884 said:
Please let me know when you do. I'll definitely check it out and thumbs up the video
Thank you
Click to expand...
Click to collapse
Have you ever used edxposed? The way you install with Magisk?
Anyone have the original build.prop ? I have everything done except CTS profile. But I think that's because I had gcam and in there it has me as pixel 2. Can flash, twrp, no screen issues, RR remix latest, going to go stock tho because CTS and my game, it's too much fun
With the pixel 4a finally arriving for some (like me), figured I'd make a quick guide
Note that unlocking your bootloader breaks safetynet. There's a workaround in this guide but no guarantee that it won't get patched out in the future.
Also note that this only works with the unlocked carrier model. Cell providers typically lock you out from this unlock process.
Unlocking Bootloader (this is for the unlocked mode, can't speak for other models)
Go to system settings -> About phone -> tap on 'Build number' several times until Developer Options is enabled
Back out into settings and go to System -> Advanced -> Developer Options -> Enabled 'OEM Unlocking'
Unplug your phone if it's plugged into anything and power it off
Boot into fastboot by holding Power + Vol Down
Plug into pc -> open terminal/shell/whatever
Type 'fastboot flashing unlock' -> Follow prompt on device to unlock bootloader (Note that this will FACTORY RESET device)
The bootloader is now unlocked!
Rooting
Grab the boot img for your rom. If it's stock, get it from the official zip
Copy the boot.img to your device
Install Magisk manager (grab it from the release zip on github - it's in the common folder)
Open Magisk Manager -> select 'Beta'
Back on the main page of Magisk Manager, Select 'Install' -> 'Select and Patch File' -> select your boot.img file -> it'll output the patched boot img to your Downloads folder
Copy the magisk_patched.img to your pc
Reboot your device back into fastboot (see Unlock section above)
Open a terminal in the directory your patched boot img file is and type 'fastboot flash boot magisk_patched.img'
You're now rooted!
Disable "Automatic System Updates" in Developer Options so you aren't surprised with an OTA on boot and end up unrooted (see the OTA section below on proper way of updating)
Passing SafetyNet
As was discovered some time ago, google is switching to a hardware attestation method for safetynet. Fortunately, at the time of writing, there is a workaround thanks to @Didgeridoohan. As of January 2021, this fix no longer works. A new module by @kdrag0n now fixes the hardware attestation issue:
Enable MagiskHide in magisk manager
Download/Install his Safetynet-fix module from this xda thread
Reboot and verify you should hopefully pass safetynet!
Taking an OTA While Rooted
Note: Installing to Inactive slot has been disabled temporarily meaning that if you take an ota, you'll need to do the patch boot img method like you did initially. See here for more details.
Note that you can download the rom from google's site here and extra the boot img from there for patching.
TopJohnWu has a great guide on how to do this here along with some nice screen shots that complement this quick guide. I'll summarize the applicable stuff here:
When an OTA is available, ignore it at first
Open Magisk Manager and go to Uninstall -> Restore Images
Now go back to Settings -> System -> Advanced -> System Update and install the OTA but DO NOT REBOOT
Once the install is done (but before rebooting), go back into Magisk Manager -> Install -> Install to Inactive Slot
Once the install is done, choose the reboot option IN MAGISK MANAGER. It works some voodoo magic to switch to updated slot and skip post-ota verifications
Having issues?
Try magisk canary instead
Note that this isn't a support thread but just a guide. You're welcome to post your tips/experiences/questions here but don't expect me to answer or reply to them.
I'll try to keep this updated with other useful guides such as TWRP when/if it is released for this device :good:
So this won't work with a Verizon pixel 4a?
Steve One said:
So this won't work with a Verizon pixel 4a?
Click to expand...
Click to collapse
Yes, the 3A's fingerprint will work for the 4A. This will satisfy SafetyNet, thus re-enable Google Pay.... For now!!!
I followed these instructions, and also enabled Magisk Hide. I'm failing both items in SafetyNet. However, I'm also running EdXposed. I'm assuming that is the reason and that there is no workaround for that?
Thank you for this guide. I only needed root to restore old app settings with Swift Backup and this worked great. I just used fastboot to boot the modified image instead of flashing it and then used that session to run Swift Backup with root. When it rebooted, all was back to stock.
neph81 said:
Thank you for this guide. I only needed root to restore old app settings with Swift Backup and this worked great. I just used fastboot to boot the modified image instead of flashing it and then used that session to run Swift Backup with root. When it rebooted, all was back to stock.
Click to expand...
Click to collapse
I would think, in this case, you'll still fail SafetyNet b/c of the unlocked bootloader. Is this the case?
digger16309 said:
I followed these instructions, and also enabled Magisk Hide. I'm failing both items in SafetyNet. However, I'm also running EdXposed. I'm assuming that is the reason and that there is no workaround for that?
Click to expand...
Click to collapse
Xposed can break safety net, I haven't tried it on this device. I have been able to pass safety net with it on some older devices though
cmstlist said:
I would think, in this case, you'll still fail SafetyNet b/c of the unlocked bootloader. Is this the case?
Click to expand...
Click to collapse
Yup but without Xposed, I was able to get safetynet to pass thanks to the module and magiskhide
cmstlist said:
I would think, in this case, you'll still fail SafetyNet b/c of the unlocked bootloader. Is this the case?
Click to expand...
Click to collapse
So, I reinstalled the magisk apk and confirmed that cts does fail. However, it does not appear to be affecting any apps. My games that normally trigger on root being available all work and Google Pay does not appear to be giving me any issues. This will bear some additional testing though anyone else goes that route.
Do I need to keep my Verizon sim card out until this is done? Is there a way to skip the initial setup so I can get to Developer Options?
it looks like there is now a pixel 4a fingerprint available in magiskhide props config
MaxPower742 said:
Is there a way to skip the initial setup so I can get to Developer Options?
Click to expand...
Click to collapse
Yes, but there are several different things you have to skip or back out of. Also, you have to have a Wi-Fi connection before it will enable the OEM unlocking setting in Developer options. You don't need to actually do any setup or enter an account or anything, though, before unlocking.
the_chrononaut said:
it looks like there is now a pixel 4a fingerprint available in magiskhide props config
Click to expand...
Click to collapse
Ya but we don't want that (we have the 4a fingerprint by default). The point of the fingerprint hack is to change the fingerprint to a device that does not use hardware attestation so magiskhide will be enough to pass safety net (like the 3a)
Zackptg5 said:
Ya but we don't want that (we have the 4a fingerprint by default). The point of the fingerprint hack is to change the fingerprint to a device that does not use hardware attestation so magiskhide will be enough to pass safety net (like the 3a)
Click to expand...
Click to collapse
Oh cool. Learn something new everyday
CSX321 said:
Yes, but there are several different things you have to skip or back out of. Also, you have to have a Wi-Fi connection before it will enable the OEM unlocking setting in Developer options. You don't need to actually do any setup or enter an account or anything, though, before unlocking.
Click to expand...
Click to collapse
Awesome thanks for your help. Got it all going including the safetynet thing. Only stumbling block so far has been it didn't seem to recognize my sim card, even waiting till it prompted me to pop it in. I just had to disable wifi and it just became my phone, didn't even ask me to activate with VZ or anything. I just did it though so I guess something could come up later where I have to go through the portal or their support to switch off my old device and turn this one on like I had to do with my last one. Maybe they improved the process though, we'll see.
Should we turn off automatic updates in dev options? I've been on roms so long I don't remember how it works with stock rooted. I imagine it'd be fine as long as it's not an android version upgrade which would not be automatic anyway.
MaxPower742 said:
Should we turn off automatic updates in dev options? I've been on roms so long I don't remember how it works with stock rooted. I imagine it'd be fine as long as it's not an android version upgrade which would not be automatic anyway.
Click to expand...
Click to collapse
I always turn it off, but I'm not sure if it's required.
Zackptg5 said:
Ya but we don't want that (we have the 4a fingerprint by default). The point of the fingerprint hack is to change the fingerprint to a device that does not use hardware attestation so magiskhide will be enough to pass safety net (like the 3a)
Click to expand...
Click to collapse
i don't think that's right there's no problem with using the pixel 4a fingerprint. personally tested. use the module to change the fingerprint and then the next option for basic key attestation. checked cts profile with magisk no problems.
Yeah I switched to the 4a fingerprint then actually did reset to default and still pass safetynet. Ampere thinks my phone is a 3a even after reinstall which is driving me ocd crazy but maybe it's just that app that needs to be updated.
MaxPower742 said:
Ampere thinks my phone is a 3a even after reinstall which is driving me ocd crazy but maybe it's just that app that needs to be updated.
Click to expand...
Click to collapse
Same thing here. I couldn't stand to look at my car showing my phone as a 3a on the screen all the time so I changed it back.
CSX321 said:
I always turn it off, but I'm not sure if it's required.
Click to expand...
Click to collapse
Turning it off is recommended if rooting
Seems like with the magisk module for props config active, it'll continue to self identify as a 3a even if you tell it to reset the fingerprint to default. I assume that's why it keeps working, cause when I disabled it, Ampere did properly see it as a 4a, but safetynet failed.
I haven't been able to disable signature verification
hello! First of all, I don't know if this topic is in this subforum or in another. If it's not here, I'm sorry. I've been trying to lock the bootloader for days before flashing the stock immediately. I try it from fasboot flashing lock and I get this: "failed (remote: 'invalid android images, skip locking') fastboot: error: command failed ". I have the r33 of Adb fasboot. I have restarted in fasboot and from there choose to restart in bootloader as I read in the forums and the same. what happens is that regardless of the ROM, root or mod to pass the safetynet. wallet and among other apps it detects them as root or similar....
juaki said:
hello! First of all, I don't know if this topic is in this subforum or in another. If it's not here, I'm sorry. I've been trying to lock the bootloader for days before flashing the stock immediately. I try it from fasboot flashing lock and I get this: "failed (remote: 'invalid android images, skip locking') fastboot: error: command failed ". I have the r33 of Adb fasboot. I have restarted in fasboot and from there choose to restart in bootloader as I read in the forums and the same. what happens is that regardless of the ROM, root or mod to pass the safetynet. wallet and among other apps it detects them as root or similar....
Click to expand...
Click to collapse
I assume you're trying to relock the bootloader? You cannot do this if any of the images have been modified, including Magisk patching. You have to flash back to stock first.
If you are trying to use payment apps, please see this thread.
yes of course. I have the stock of May. no root or patched init.boot or magisk. Totally stock except for the bootloader, which I intend to close since with no method or module I can get the wallet and other things to work for me. in wallet it says "this device does not meet the requirements". I don't know if a partition has been touched or something, because before I had the crDroid...
juaki said:
yes of course. I have the stock of May. no root or patched init.boot or magisk. Totally stock except for the bootloader, which I intend to close since with no method or module I can get the wallet and other things to work for me. in wallet it says "this device does not meet the requirements". I don't know if a partition has been touched or something, because before I had the crDroid...
Click to expand...
Click to collapse
I wonder why that is. I don't use wallet for payments but I did use it for Megadeth last year and I have my Covid info on it.
I see people having issues so I tried to add a few cards and had no issues, but I know there are people like you where it just doesn't work
HipKat said:
I wonder why that is. I don't use wallet for payments but I did use it for Megadeth last year and I have my Covid info on it.
I see people having issues so I tried to add a few cards and had no issues, but I know there are people like you where it just doesn't work
Click to expand...
Click to collapse
The fact is that it worked perfectly for me with root, stock ROM, safetynet 2.40 mod 1.2 module and Kira kernel. anyway...
juaki said:
The fact is that it worked perfectly for me with root, stock ROM, safetynet 2.40 mod 1.2 module and Kira kernel. anyway...
Click to expand...
Click to collapse
Um you stated no method or module worked for you. Now you are saying you had Wallet and "other things" working with root.
indeed. What I wanted to say is that it used to work for me, and suddenly it has stopped working for me in any ROM. with module or without it, with root or without it. and when flashing the stock in both slots and doing the relevant process, I can't block the bootloader. I honestly don't know what to do anymore. The phone passes the safetynet test.
juaki said:
indeed. What I wanted to say is that it used to work for me, and suddenly it has stopped working for me in any ROM. with module or without it, with root or without it. and when flashing the stock in both slots and doing the relevant process, I can't block the bootloader. I honestly don't know what to do anymore. The phone passes the safetynet test.
Click to expand...
Click to collapse
For locking the bootloader, you many want to try Android Flash Tool. Select "Force Flash all Partitions", "Lock Device" and "Wipe".
What @Lughnasadh has said is your best bet if you are not familiar manually wiping/modifying your phone. If you are not rooted and your phone system image is stock, then you need to lock your bootloader.
As Google has posted on their site a good number of times, you cannot use any of their security based services with an unlocked bootloader.
With root access, you can circumvent these restrictions. But without root access, you need to lock your bootloader. And when you attempt to do so, be sure that you don't utilize the newer versions of platform-tools as they seem to still cause problems.
juaki said:
The fact is that it worked perfectly for me with root, stock ROM, safetynet 2.40 mod 1.2 module and Kira kernel. anyway...
Click to expand...
Click to collapse
The newest working Safetynet Module is 2.4.0-MOD_1.2 by Kdrag0n
I uploaded it to my Mediafire
HipKat said:
The newest working Safetynet Module is 2.4.0-MOD_1.2 by Kdrag0n
I uploaded it to my Mediafire
Click to expand...
Click to collapse
The original USNF module was indeed developed by @kdrag0n but the working module is the fork by @Displax .
It is always best to link to the official source of the module, rather than re-uploading it, due to the potential of someone modifying it for malicious purpose.
Here is the official source
V0latyle said:
The original USNF module was indeed developed by @kdrag0n but the working module is the fork by @Displax .
It is always best to link to the official source of the module, rather than re-uploading it, due to the potential of someone modifying it for malicious purpose.
Here is the official source
Click to expand...
Click to collapse
Yeah if I could have found it but the version I have on my phone is the one I listed, or it's named wrong
HipKat said:
Yeah if I could have found it but the version I have on my phone is the one I listed, or it's named wrong
Click to expand...
Click to collapse
Apologies in advanced if I misunderstood...
the one you listed & the one on your phone is the same one in the Github V0latyle linked (from Displax's very own USNF fork Github) -- it is not named wrong, but if you look at your own screenshot from your own device; it displays "modded by Displax"
Again, sorry if I'm taking it wrong that you didn't get it, but the words "but" and "or it's named wrong" in your post led me under that impression you think you are under kdrag0n's main branch just by name itself....
simplepinoi177 said:
Apologies in advanced if I misunderstood...
the one you listed & the one on your phone is the same one in the Github V0latyle linked (from Displax's very own USNF fork Github) -- it is not named wrong, but if you look at your own screenshot from your own device; it displays "modded by Displax"
Again, sorry if I'm taking it wrong that you didn't get it, but the words "but" and "or it's named wrong" in your post led me under that impression you think you are under kdrag0n's main branch just by name itself....
Click to expand...
Click to collapse
You are correct, I did not notice the Modded by in the name and did think this was Drag0n's but it's all good. It's the one that works and that's the important thing