How to Unlock Bootloader on any Samsung Device [New VaultKeeper Method]

In this tutorial, we will show you the steps to unlock the bootloader on any Samsung device. The OEM is making some considerable progress when it comes to releasing software upgrades. From OneUI 2.0 to 2.5 and now to 3.0, it has been nothing short of commendable (considering their earlier track records). With each new update, device optimizations and system stability improvements are always there. Apart from that, there are additions of a slew of distinct features. Likewise, the customization opportunities are also quickly expanding with each new bump in the OneUI version.

However, these are just the beginning. There are a plethora of other modifications that you could make full use of. Flashing custom binaries, gaining administrative rights, and replacing the device’s stock recovery with a custom one are just some of the noteworthy ones. There is just one prerequisite that you need to a checkmark, and that is an unlocked bootloader. And in this guide, we will help you with just that. Given below are the steps to unlock the bootloader on any Samsung device, keeping in mind the new VaultKeeper security check.

• Samsung Unlock Bootloader: Benefits and Risks
• How to Unlock Bootloader on any Samsung Device [New VaultKeeper Method] An Important Note regarding US Snapdragon Devices STEP 1: Enable Developer Options on Samsung STEP 2: Enable OEM Unlocking on Samsung STEP 3: Boot Samsung Device to Download Mode STEP 4: Unlock Bootloader on Samsung via Download Mode STEP 5: Verify Samsung Bootloader Status with Vaultkeeper

Samsung Unlock Bootloader: Benefits and Risks

Unlocking your device’s bootloader is like opening the gate to a plethora of opportunities. You could flash various Custom ROMs , install Custom Recovery (like TWRP) , try out tons of mods and hacks, and most importantly- root your device. The latter could be done via TWRP (flashing Magisk ZIP via TWRP) or without TWRP ( by patching and flashing the stock boot. img ). After you get administrative privileges, you could then try out a ton of Magisk Modules , Xposed Framework , Substratum Themes , and Viper4Android , among others.

However, they do bring in a few uninvited risks as well. To begin with, it will trip the Knox counter of your device. This will straightway make your Samsung device’s warranty null and void. Furthermore, all the apps that depend on this Knox will no longer function. These include the likes of Samsung Pay and Secure Folder. Likewise, apps like Google Pay and Pokeom Go might no longer function.

Netlfix Widevine L1 Certification will also be degraded to L3 , as a result, you won’t be able to watch videos in HD. The SafetyNet and Play will be triggered [ FIXED ], and Play Integrity will fail [ FIXED ] thereby preventing you from using banking apps [ FIXED ]. So, if you are ready to proceed ahead, then here are the steps to unlock the bootloader on your Samsung device.Even if you restore the stock OS and re-lock the bootloader, many of the Samsung Knox-related features will still not function. So proceed ahead with caution!

• Use Custom Fingerprint/Build.Prop to Pass Play Integrity Test
• How to Root any Samsung device via Magisk and Odin
• How to Patch Samsung AP Firmware via Magisk
• Flash magisk_patched.tar (patched Samsung AP file) via Odin

How to Unlock Bootloader on any Samsung Device [New VaultKeeper Method]

Well, the OEM had already put in a few stringent measures in the form of Prenormal RMM State and DEFEX. Add to it the New Vaultkeeper mechanism, and things turned out to be quite complicated. Fortunately, its fix is relatively simple and we have shared that below. Before this mechanism was introduced, you only had to enable a toggle, and your job was done. However, now you will have to execute a few extra efforts as well.

Thankfully, they are easy to do and take only a few seconds. So on that note, let’s get started. The below process will wipe off all the data from your device. So take a complete device backup and only then proceed ahead. Droidwin and its members wouldn’t be held responsible in case of a thermonuclear war, your alarm doesn’t wake you up, or if anything happens to your device and data by performing the below steps.

An Important Note regarding US Snapdragon Devices

If you own a Samsung device from the US that has a Snapdragon chipset, then you wouldn’t be able to unlock its bootloader because there will be no OEM Unlock toggle to begin with. Likewise, some carriers in the US have also blocked the ability to unlock the bootloader on Samsung devices. In all these cases, you’re unfortunately out of luck with the official method and you’re only course of action is to opt for third-party paid service.

With that said, if you don’t live in the US and have a Snapdragon device, then also the OEM Unlock toggle might be missing. In such instances, you could fix that issue using the steps listed below [the process will wipe off all the data from your device, so please take a backup beforehand]:

1. To begin with, turn off the WiFi on your device.
2. Then, remove the SIM card from your device as well.
3. Now disable Developer Options on your device [if enabled].
4. After that, perform a factory reset from the Settings menu.
5. Once the reset is complete, you will be taken to the setup screen.
6. Do not set up your device now. Instead, go straight to the OS and enable WiFi.
7. Then re-enable Developer Options and you should now see the OEM Unlock option.
8. Once it appears, enable it right away. You may then re-insert the SIM if required.

STEP 1: Enable Developer Options on Samsung

1. First and foremost, you will have to enable Developer Options on your device.
2. So go to Settings on your device and head over to About phone.
3. Then go to Software information and continuously tap on Build Number 7 times.
4. You will then get a toast message that Developer Options has been enabled.
5. Go back to the Settings page and scroll to the end. You should see the Developer Options.

STEP 2: Enable OEM Unlocking on Samsung

1. It’s now time to enable OEM Unlock on your device which will allow you to carry out the unlocking process.
2. So go to Developer Options, and enable the ‘OEM Unlocking’ toggle.
3. Then tap on Turn on in the confirmation dialog box that appears.
4. NOTE: If you don’t see the OEM Unlock option or if it is greyed out, then refer to this guide: How to Fix Missing OEM Unlock in Samsung Devices .

STEP 3: Boot Samsung Device to Download Mode

Well, there is no universal method to boot your device to Download Mode. different Samsung devices take diverse routes for the same. Therefore please refer to our guide on How to Boot any Samsung Device to Download Mode . This guide covers all the Samsung devices. Furthermore, we have also shared a method to boot to download mode without any hardware keys, you may try it out as well. With that said, the below steps might be enough to get the job done:

1. Start by powering off your device,
2. Then press and hold Vol Up + Vol Down together and connect your device to the PC via a USB cable.
3. As soon as you see the Warning message on your device, release the pressed keys.
4. Finally, press the Volume Up key once and your device will be booted to Download Mode.

• New Method to Boot to Recovery Mode on Samsung OneUI 3.0 Android 11
• How to Stop Samsung Find My Device Offline Finding Notifications
• Steps to Create Samsung Combination Firmware and Flash it via Odin
• How to Boot Rooted Samsung to Recovery Mode and Rooted OS

STEP 4: Unlock Bootloader on Samsung via Download Mode

1. Now that your device is booted to Download Mode, press and hold the Volume Up key for a few seconds.
2. This will take you to the Device unlock mode (make sure you have taken a backup).
3. You will now get a confirmation message, use the Volume Up button to reply to the affirmation.
4. The process will now begin and should be completed within a few seconds. Your device should then automatically boot up.
5. But wait, there’s more! Now the Vaultkeeper mechanism will come into the picture. Let’s deal with it and apply the finishing touch

STEP 5: Verify Samsung Bootloader Status with Vaultkeeper

1. You will now have to notify the Vaultkeeper that you unlocked the device’s bootloader.
2. To do so, head over to Settings and enable Developer Options as mentioned in STEP 1.
3. Then go to Developer options and make sure that the OEM unlocking toggle is turned on and is greyed out as well. That’s it.

• Fix error boot prepare- device stuck in fastboot
• Fix Android stuck in Recovery Mode: No Command screen
• Detailed Steps to Fix adb is not recognized Error
• How to Fix FAILED (remote: unknown command) Error

• Johnny 2 years ago Reply I’ve been trying to unlock the boot loader on a Galaxy Note 5 for over a month. Even though I most certainly have OEM unlock turned on. When I do the 10 second hold on up volume. I get no invitation to unlock the boot loader. Mind you this is a Verizon phone. And I’ve gotten many a Google answer that says you absolutely cannot unlock the boot loader on a Verizon phone. Which of course makes a SIM unlock USELESS!
• PM 3 years ago Reply There is no ‘OEM Unlock’ option under Dev.options on my S4 Lollipop 5.0.1. I tried even HW reset to factory defaults… nope not there.
• Zach 4 years ago Reply Hi, I bought samsung galaxy s21 ultra 5g from china. So, as you can see everything’s in chinese. I’m Malaysian but I can’t seem to get into samsung download mode since it doesn’t have download mode but fastboot mode. Even after I got the phone to unlock via fastboot command ” fastboot unlock oem/fastboot flashing unlock” I tried to odin the downloaded files (via frija tool) but still no joy! Help me out please.
• Gerald Baggett 5 years ago Reply I have tried https://droidwin.com/fix-missing-oem-unlock-samsung/#Method_3_Fix_Missing_OEM_Unlock_on_Samsung_using_Update_Check_tweak and countless youtube videos and nothings seems to fix the missing OEM unlock on my Samsung Galaxy S20 Ultra 5g SM-G988U.. I have not tried the method 4 which required actuall flashing something on a locked bootloader which i did not see anything saying that method will work for my phone as the methods seems to only work for the s9 not my s20 ultra
• sewande 5 years ago Reply I have devices samsung A10s (SM-A107F). I would ask there is any chance for downgrade firmware from android 10 (firmware version A107FXXU7BTL1/binary 7)) to android 9 (A107FXXU3ASH5/binary 3). There is chance to downgrade firmware from binary 7 to binary 3 ?
• Zohaib Arif 5 years ago Reply hi, I have Note 09 and i tried every method to unlock the bootloader, also tried above method but there is no option in Download area to unlock … only coming CONTINUE or CANCLE. i am unable to install Magisk due to locked bootloader. can you help me , what else i can try…
• Jarett 5 years ago Reply Sadique, Android os update to 11, even after since hit fixes is still causing my drive to have issues with certain apps, namely war Dragons by pocket Gems. I got a new phone with android 10 on it,but it updated to 11 overnight. Will the steps above allow me to revert an LG V60 ThinkQ from android, never should have been rolled out, 11 back to 10? Zero issues with 10, 11 its all over redit, twitter and other social media platforms that Android 11 has some serious connection issues with google play accounts, certain apps functionality, and overall performance issues with 5G connection and wi-fi enabled everything… Please help. Samsung, Google, LG, Verizon, Comcast, and even the specific app developer Pocket Gems have been useless in trying to resolve these issues. Want to make sure if i root my phone,what else do i need to revert back to 10 instead of 11? Want to make sure I do it right. Thanks!
• kadir 5 years ago Reply hi hassan . i have a samsung galaxy sm51f mobile phone. there is no secure folder opiton. do you have any ideas ? the systme updated from 2.0 to 2.5 . but still no secure folder opitons.. i need your help Sadique Hassan 5 years ago Reply Hi Kadir, True to my knowledge, it might be due to geo-restrictions. Some regions, such as Nepal and Bangladesh haven’t got the Secure Folder option after the update. Anyways, what’s the status on Play Store and did you tried sideloading the APK?
• Chris 5 years ago Reply I have a little problem with a Samsung SM-A115W. There’s no “OEM Unlock option” in the Developer Options. The usual workaround being circulated on the internet is to leave it connected to internet for 7 days and let it do the system update from Samsung or whatever. But I don’t want to do that because once it gets the update, there’s no way back, a factory reset will not bring it back to the original firmware at the time of purchase. And a security update might actually remove even the slightest chance of unlocking the bootloader by removing that option from the system. This phone has a newer bootloader version (0.5) Fastboot fails on most commands, except for “fastboot devices” or “fastboot getvar all” Sadique Hassan 5 years ago Reply Hi Chris, please refer to this guide: https://droidwin.com/fix-missing-oem-unlock-samsung/

(Cancel Reply)

Δ

Use Custom Fingerprint/Build.Prop to Pass Play Integrity Test

In this guide, we will show you two different methods to create custom fingerprints/build.prop to pass the Play Integrity Test on your rooted device or if you are running a custom ROM. Well, it seems we might finally reach the end of the road, as far as gaining administrative privileges is concerned. For the unaware, if you root your device, then it will trip the SafetyNet Test, thereby making it difficult to use banking and payment apps.

However, we managed to find a workaround that helped us pass this test with ease . Fast forward to this year, Google introduced the Play Integrity Test and has instructed every app to incorporate its API by January 2025. At the time of writing, many banking and payment apps have already shifted over to this test.

As before, if your device is rooted, then you will fail this test, thereby resulting in your inability to use banking apps. Fortunately, we once again managed to get hold of a method to bypass this test . Google then took a step further and patched our tweak only for us to bypass it once more! Until now. The Silicon Valley giant has finally taken the most extreme step to date which might finally spell the end of root for the tech enthusiasts.

• Google ‘Banning’ Fingerprints for Play Integrity: Is Hiding Root Impossible?
• How to Create and Use a Custom Fingerprint/Build.Prop to Pass Play Integrity One Click Method [Easiest] Create a New Fingerprint JSON File Manually Some Additional Tips on Creating Custom JSON Files Pixel Flasher Tool [Recommended]
• What if the Test Fails? Repeat and Repeat!
• Rooting and Custom ROMs: A Difficult Yet Achievable Journey Ahead!
• UPDATE: List of Fingerprints Build Prop Passing Play Integrity

Google ‘Banning’ Fingerprints for Play Integrity: Is Hiding Root Impossible?

Up until now, we were able to use the XDA Senior Member Chiteroman’s module to easily pass the MEETS_DEVICE_INTEGRITY and MEETS_BASIC_INTEGRITY, which are two prerequisites of the Play Integrity test. In hindsight, the module uses a fingerprint from one of the unpatched devices and the developer then uploads his mod over to GitHub. Since this mod is open source, anyone can easily decode it, including Google! And that is exactly what is happening.

While it might sound hard to digest why would Google end up utilizing a part of its resources towards this project which affects only about 3% of Android users, but trust us, that’s exactly what’s currently going on. The developer has tried out numerous combinations of fingerprints in its modules, including different OEMs, different Android versions, and even different custom ROMs [such as Evolution X].

However, every time a new module is released, Google tends to patch it straightaway, thereby leaving the developer with three options- either keep on playing this trial-and-error method, make the module closed source, or list out the instructions on how a user could create a custom fingerprint file and use it to pass this test.

The first approach was neither the most feasible nor the most viable for him [because he wasn’t earning anything from it and more importantly he has a life out of this modding community too!]. Likewise, making it a closed source might have raised a few eyebrows from some of the users [though judging by his reputation, that shouldn’t happen in the first place]. Henceforth, the third option is our best bet.

How to Create and Use a Custom Fingerprint/Build.Prop to Pass Play Integrity

There exist a couple of methods of getting this job done- the automatic and the manual way. In the automatic method, you would still need to carry out the first step from the manual method, but it will then take care of the rest of the steps. Moreover, please take a backup beforehand, just to be on the safer side. Droidwin and its members wouldn’t be held responsible in case of a thermonuclear war, your alarm doesn’t wake you up, or if anything happens to your device and data by performing the below steps.

One Click Method [Easiest]

Well, we can’t thank chiteroman enough for this! He has just released a plug-and-play version of this module which would be the easiest and best method to opt for the generic users. All you need to do is get hold of this module v14.2 from GitHub , enable Zygisk, flash it via Magisk, and delete the data of Google Services Framework, Play Store, Play Service, and Play Protect Service [if present]. Here’s a detailed guide on the same , it’s highly recommended you check it out.

Create a New Fingerprint JSON File Manually

XDA Senior Recognized Developer Osmosis took this responsibility on his shoulders and has done quite an excellent job in listing out the steps on how you could create and use a custom.pif.json. Here are the instructions steps for the same:

[Check out UPDATE section at the end of this guide!] First and foremost, download the stock ROM for a random device [see below], extract it, and get the system build.prop and/or product build.prop and vendor build.prop files from it. [In some cases, you could simply get hold of the firmware DUMP file directly on websites like Gitlab. So it’s better if you can find the dump because then you wouldn’t have the download the ROM and neither would you have to extract these files].

We cannot share these files/details publicly because Google will get hold of them and mass ban all of them at once [it has just happened with an Asus device. We managed to get an unpatched fingerprint from one of the Asus devices and used it to pass the Play Integrity Test. This worked for a few days before being ultimately patched by Google!]. Regarding “a random device” that we mentioned above, make sure to keep the following points in mind before you download its ROM:

• All older Nexus devices (Nexus 6/shamu and older) appear to be banned.
• Final release ROM builds of all no-longer-supported remaining Nexus and Pixel devices are banned.
• The device must have at least been upgraded to Oreo (Android 8) and should have come with at least an Android 6 or higher version out of the box.
• Devices launching with Pie (Android 9) or later might not work.
• In a nutshell, try to pick a combination of a device and its ROM which you don’t think many people will choose. This is because “The less obvious statistical data Google receives indicating a particular fingerprint is being abused, the fewer fingerprints will get banned”.
• Don’t go for the likes of Pixel, Samsung, Xiaomi, and other popular OEMs as most of their fingerprints have already been used or patched by Google. Instead, go for less-known brands such as Asus, Vivo, Oppo, or other Chinese brands that not many know about. Remember, the less popular a device is, the better your chance of passing the Play Integrity test!

Let’s now talk about the location of build.prop, product, and vendor.prop. In case of build.prop, it could be found at /system/system/build.prop or /system/build.prop. The product can be /product/build.prop and/or /product/etc/build.prop. The vendor is located in /vendor/build.prop or/system/vendor/build.prop.

In general, they’ll be ro.build.fingerprint + ro.product.* (older system build.prop), or, ro.system.build.fingerprint + ro.product.system.* (newer system build.prop) [or, ro.product.build.fingerprint + ro.product.product.* (product build.prop, only needed on devices where system build.prop contains “generic” values)].

From there, you’ll have to copy the following six values: PRODUCT (ro..name), DEVICE (ro..device), MANUFACTURER (ro..manufacturer), BRAND (ro..brand), MODEL (ro..model), and FINGERPRINT (ro..fingerprint). Optionally, also copy SECURITY_PATCH (ro.build.version.security_patch from system build.prop)

Any build prior to March 16, 2018 does not require a matching SECURITY_PATCH field, though adding it wouldn’t be of any harm. Moreover, do note that the date should be from the ro.build.date present in the system build.prop, instead of the AOSP base date in the fingerprint.

Now paste the copied values between the quotes of the corresponding fields in the template custom.pif.json sample shown below [it’s just a sample one that has already been banned by Google. So make sure to replace the values accordingly].

{

  "PRODUCT": "taimen",

  "DEVICE": "taimen",

  "MANUFACTURER": "Google",

  "BRAND": "google",

  "MODEL": "Pixel 2 XL",

  "FINGERPRINT": "google/taimen/taimen:8.1.0/OPM4.171019.021.R1/4833808:user/release-keys",

  "SECURITY_PATCH": "2018-07-05",

  "FIRST_API_LEVEL": "26"

}

Here’s another JSON file with slightly more information:

{

  "MANUFACTURER": "Google",

  "MODEL": "Pixel 2 XL",

  "FINGERPRINT": "google/taimen/taimen:8.1.0/OPM4.171019.021.R1/4833808:user/release-keys",

  "BRAND": "google",

  "PRODUCT": "taimen",

  "DEVICE": "taimen",

  "RELEASE": "8.1.0",

  "ID": "OPM4.171019.021.R1",

  "INCREMENTAL": "4833808",

  "TYPE": "user",

  "TAGS": "release-keys",

  "SECURITY_PATCH": "2018-07-05",

  "DEVICE_INITIAL_SDK_INT": "26"

}

Once you have got the required information, save it in a text file and rename it to custom.pif.json if you are using the fork of the original module [by Osmosis, which we are using] or pif.json [if you are using the original module by Chiteroman]. After that, you’ll now have to transfer the file to your device.

For that, you could either do so via the Pixel Flasher Tool as explained in the next section, or by copying your .json file to /data/adb/modules/playintegrityfix/custom.pif.json [for Osmosis, in our case] or /data/adb/pif.json [for Chiteroman]. Once done, restart your device and then check if it passes the Play Integrity Test using this custom fingerprint/build.prop! If it doesn’t, then you’ll have to pick a different fingerprint and retry this process.

Some Additional Tips on Creating Custom JSON Files

• Let’s say that a device was released with Android 8, and then it received subsequent updates to Android 9 and 10. This way you’ll be able to create three different fingerprint JSON files to test. However, most of the details will be the same in all those files, such as MODEL, BRAND, MANUFACTURER, and even the FIRST API LEVEL because the device was initially launched with Android 8, that fact isn’t going to change irrespective of the current OS.
• Moreover, there needs to be a comma after the end of every line in the JSON file, except the last line [as is evident from our above example.
• If you still have any doubts with regard to your JSON file, then you could use this JSON Validator and it will point out all the errors in your file, if any.

Pixel Flasher Tool [Recommended]

The tool supports two methods- it could either generate a random fingerprint JSON file for you or you could create and upload your own custom fingerprint. If you ask the tool to generate a JSON file for you, then it has a high chance of getting patched by Google as opposed to the one that you have created manually. However, as opposed to the manual creation, it will take a lot [and yes, we really mean a lot] of time and effort. So decide on this trade-off accordingly.

1. To begin with, get hold of the build.prop file from the desired firmware version as explained above.
2. Then download and extract Android SDK Platform Tools on your PC.
3. After that, enable Zygisk via the Magisk’s settings menu and restart your device.
4. Now download Pixel Flasher from GitHub and launch it [credits: XDA Recognized Developer badabing2003].
5. Then click on Browse > navigate to the platform-tools folder and select it.
6. Now click on Scan and select your device from the list.
7. Then click Magisk > Install PIF module and select the desired one [we have chosen Osmosis].
8. The latest version of the mod will now be installed. Once done, hit OK and click Reboot System.
9. Once your device boots up, click on PIF Manager [it will be empty as of now].
10. Now, if you want to opt for the Manual Method , then click on Process build.prop(s) , navigate, and select your build.prop files. The order of precedence is as follows: build.prop system-build.prop system.prop product-build.prop product.prop vendor-build.prop vendor.prop Any other prop file
11. The tool will now read these files and bring up the output something as shown in the below screenshot.
12. On the other hand, for Automatic Method , click on the Get TheFreeman193 Random Pif button. It will populate the output window with the data from a random device.
13. Once done, click on the Paste button next to Output and the data will be populated under the Active PIF section.
14. At this stage, you should see the red warning next to Active PIF. This just indicates that the contents of the Active PIF window are not the same as the contents on the device.
15. So click on Create PIF.json and the file will be transferred to your device. Likewise, the red warning should now turn gey, meaning the content of PIF widow is the same as that on your device.
16. Finally, download and install a SafetyNet Checker app out of the four listed there. As of now, we are going ahead with Play Integrity API Checker.
17. So click on Play Integrity check. It will launch the Play Integrity API Checker app, perform the test, and display the result in the output window.
18. If it passes the device integrity and basic integrity tests, then congrats, you have found the needle in the haystack! But what if the test fails? Let’s find out.

What if the Test Fails? Repeat and Repeat!

• If you have chosen the Manual Method and failed the test, then you’ll have to get hold of a new JSON file from different firmware and repeat the above steps. Do so until you get the right JSON file that passes both these tests.
• If you have chosen the Automatic Method , then in that case, click on the Get TheFreeman193 Random Pif button > click on Paste next to Output. Then click on Update PIF.json > Play Integrity Check. It will perform the check and display the result. Keep on carrying out these processes until you achieve success.

Moreover, as soon as you find the right fingerprint JSON file, make sure to hit the heart icon and save that file. And please don’t share it with others as upon doing so, the chances of it getting into the hands of Google and subsequently nullifying it by the Silicon Valley giant increases tremendously. [So sharing is not caring in this case!].

Rooting and Custom ROMs: A Difficult Yet Achievable Journey Ahead!

So this was all from this guide on how to use a custom fingerprint/build.prop and pass the Play Integrity Test. While we always believed in the “sharing is caring” motto, however, for once, let’s not adopt it in this case scenario. If you get hold of a working fingerprint and then end up sharing that with the rest of the users, then it will ultimately be patched by Google. So keep that unique build.prop with yourself and prevent it from getting caught by Google!

NOTE: Some or the other changes are being constantly implemented by Google at an alarming rate. Thankfully, the developers are always one step ahead and are testing out new ways of bypassing the patches enforced by the Silicon Valley giant. But this also means that you will witness changes to the modules at frequent intervals as well, so we will update this guide as and when that happens. Make sure to keep a tab on this post regularly. [Screenshots Credits, unless specified otherwise: XDA Recognized Contributor badabing2003].

UPDATE: List of Fingerprints Build Prop Passing Play Integrity

Well, we decided to do all the dirty work on your behalf by compiling a list of all the custom fingerprints/JSON/build props from the devices that pass the Play Integrity tests. However, make sure you’re the earliest adopter of these builds, or else, it won’t be long before others get their hands on them. With that said, even if these get patched by Google, we will generate a new one at the earliest. So make sure to keep a tab on the below linked guide frequently.

List of custom fingerprints/JSON/build prop that pass Play Integrity

• sonn 2 months ago Reply Send me XML file to pass device integrity
• Shadman 4 months ago Reply Hellloo pleaseee send keybox.xml Email : shadmanahmadixo@gmail.com
• Ameer 11 months ago Reply Send me XML file to pass strong integrity Skye 9 months ago Reply Please give me keybox.xml Thank you
• Milan Čížek 2 years ago Reply Hi, I have extracted all three build.prop (system,product,vendor) from original stock image – extracted all *.img via payload-dumper-go.exe from payload.bin + ext2explore.exe. But I am not able to load the prop to PIF Manager, it always ends with the error. File “pif_manager.py”, line 1051, in process_props AttributeError: ‘PifManager’ object has no attribute ‘first_api’ https://pasteboard.co/UioQok8ehMt9.png What is wrong? ro.product.first_api_level=30 is in vendor-build.prop ro.board.first_api_level=30 too
• Tjw 2 years ago Reply Thanks for this guide. I can finally get a working custom file. I appreciate this simplified explanation and it’s straight forward enough for me to get this working. Well done author!! Thanks
• Jonathan 2 years ago Reply get the system build.prop and/or product build.prop and vendor build.prop files from it. How? Milan Čížek 2 years ago Reply You have to download stock image for your phone and then extract them from system/product/vendor.img files. Swastik Singh 8 months ago Reply Pls XML file or file links to solve the issue of safety internet pass problem . in poco f5 matrixx os
• kryspus 2 years ago Reply hello, I have downloaded 4 differents rom, could you explain how to extract the system to get in to it? Thx
• kryspus 2 years ago Reply Hello i have hiting facing the wall while i wanted to unpack stock rom to see the right files. It’s looks like a quite a challenge, can i expect any advice here? It’s unbelievable how much GB’s i have to download from internet and a bunch of tools to get a few lines of code.
• Jimmy 2 years ago Reply Thank you for this guide. I have just discovered today that many of my apps are refusing to work because of this problem. Cheers

(Cancel Reply)

Δ