How to Run iMobile on Rooted Android Device
Here's what we will be doing in this guide:
-Pass Strong Integrity.
-Randomised Magisk app name.
-Add to Denylist: Google Play Store, Google Services Framework, Google Play Services, iMobile.
-Created Blacklist via HMA and added root related apps to it. Then applied that blacklist to iMobile.
-Add iMobile to target.txt via TrickyStore Add-on
-Use the IAmNotADev module to hide the Developer Mode prompt.
-Use the ProtectAI-Bypass module in LSPosed.
-[Optional] Fake your Device ID via Android Faker.
-[Optional] Spoof/Fake Bootloader status as Locked
-Device Restart > Delete Data iMobile > Check out the result.
In this guide, we will show you the steps to run iMobile on your rooted Android device. Running banking and payment apps on a rooted device is no easy task in itself but still a few tweaks here and there and you’ll be able to easily run those apps. However, iMobile doesn’t seem to fall in that category!
Irrespective of the tweaks I carried out on my device, the app was able to identify the root by one way or the other [Rooting Detected or SUBinary Detected were the two most common prompts shown by iMobile]. Well, not anymore! Finally, I managed to find an interesting approach using which you can run iMobile on your rooted Android device.
This is a lengthy approach and involves a combination of multiple fixes, plus the introduction of a new module as well! So without any further ado, let’s get started.
- How to Run iMobile on a Rooted Android Device Via Magisk Via APatch
How to Run iMobile on a Rooted Android Device
Before starting off with the below steps, take a complete device backup. Moreover, using banking apps on an unlocked bootloader/rooted device might pose some serious security risks. So proceed ahead at your own risk. 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.
Via Magisk
It is highly recommended that you use Magisk Alpha. If your device is rooted via any other version of Magisk [Stable/Beta/Canary], then this tweak might not work. As for the downloading source, I was able to obtain it from the Telegram Channel named Magisk Alpha. You are free to use any source of your choice.
- First off, launch Magisk Alpha > go to Settings > Hide the Magisk spp.
- Now go to Configure Denylist and enable the toggle next to these apps Google Play Services Google Play Store Google Services Framework iMobile
- Now create a blacklist using Hide My Applist and apply it to iMobile.
- Then pass at least the Device Integrity , though the Strong will be the best.
- Also, create a custom.pif.json file .
- Now, delete the data of Google Play Service, Google Play Store, Google Service Framework, and iMobile.
- Finally, restart your device and check the result. If it’s still not working, then proceed with the steps below.
- Now go to the below location and open the target.txt file: data/adb/tricky_store/target.txt
- Then add its app package name [given below] and save it com.csam.icici.bank.imobile!
- Again, delete the data of Google Play Service, Google Play Store, Google Service Framework, and iMobile.
- Finally, restart your device and check out the result.
Via APatch
UPDATE: It is recommended that you use APatch instead of Magisk for carrying out this tweak. In that case, you will have to skip STEP 2, 3, 4, and 5.
- To begin with, pass the Strong Integrity Test [recommended].
- Then launch Magisk > go to Settings > tap on Hide the Magisk app.
- Give it any random name of your choice and hit OK.
- Now launch Magisk > go to Settings > Configure Denylist.
- Select the following apps: Google Play Store, Google Services Framework, Google Play Services, iMobile.
- Next, download, install, and set up Hide My Applist . Then restart your device.
- Now launch the HMA > go to Template Manage > Create a blacklist template.
- Name it root. Then tap on Edit List next to 0 Apps Invisible.
- Choose all the apps belonging to the root domain from the list.
- Then go to App Manage > iMobile > Enable Hide > Using 0 templates > select the root template > OK.
- Now launch KSUWebUI > Tricky Store > check the iMobile app.
- Long-press on the iMobile app name and select the green circle. Now hit Save.
- Then download and install the IAmNotADeveloper Module in LSPosed and restart your device.
- Now launch LSPosed, go to Modules, select IAmNotADeveloper, and checkmark iMobile.
- Now, download and install the ProtectAI-Bypass module from GitHub.
- Then launch LSPosed > go to Modules > select ProtectAI-Bypass.
- Now, enable the module and then select iMobile from the list and restart your device.
- Next up, download and install Android Faker from LSPosed.
- Then open LSPosed, go to Modules, select Android Faker, check System Framework, and restart your device.
- Now launch Android Faker, randomize the Device ID, and restart your device.
- Finally, delete the data of Google Play Store, Google Services Framework, Google Play Services, and iMobile.
- Now restart your device and check out the result.
- NOTE: Some apps also check for the bootloader unlock status. So it is recommended to spoof/fake it to Locked .
- How to Run Banking Apps on Rooted Android Device [10 Methods]
- How to Run National Bank of Egypt App [NBE] on a Rooted Device
- Yes, You Can Now Run Rooted Apps Without Rooting Your Device!
- How to Set up and Run Shizuku [Wireless Debugging, Root & ADB]
(Cancel Reply)
Δ
How to Get Fingerprint PIF.JSON File using Play Integrity Fork
In this guide, we will show you the steps to get the fingerprint PIF.JSON file using Play Integrity Fork. A week back or so, we got the unfortunate news that the Play Integrity Fix module has been discontinued by the developer chiteroman. We can’t thank him enough for the invaluable work he has done for this community. But going forward, what can be our next course of action?
Well, while this module was up and running, another developer [osm0sis] was also running a fork of this module, which goes by the name Play Integrity Fork. While we wouldn’t say that it was under the shadow of Fix, but it wasn’t being used that much when compared to its counterpart.
However, all that is about to change now, and so there are a few queries that might pop up in your minds. In this regard, one of the most common questions that I have been asked for the past week is how to get the fingerprint PIF.JSON file in the Play Integrity Fork module.
As you might already be aware, the Fix module already has this embedded in its module; you just need to launch it via KSUWebUI, hit the Fetch PIF.JSON option, and you’ll get the file. But that’s not possible via the Fork module via the direct route. Why? Let’s find out, and after that, we will list the plausible steps through which you can get this file using this module. Follow along.
- Why is the PIF JSON Fingerprint File Missing in Play Integrity Fork
- How to Get the Fingerprint PIF.JSON File using Play Integrity Fork
- Direct Download PIF JSON Files
Why is the PIF JSON Fingerprint File Missing in Play Integrity Fork
By default, the module comes with a template of a PIF JSON file that you need to fill in manually. You can get this file from /data/adb/modules/playintegrityfix. Once you fill in the values, simply rename it to custom.pif.json, and your task stands complete. But why hasn’t the dev simply added this file, as was the case with the Fix module? Here’s what he has to say regarding this:
There’s intentionally no pif.json in the module because the goal remains to be futureproof, and including something that may be banned and obsolete within days would be contrary to that goal.
However, finding these files might not be everyone’s cup of tea. Not only are a few of these remains, but finding them is also quite an effort taking task. The developer acknowledges this, and hence, he has added a script to extract the latest Pixel Beta fingerprint along with the module. The script is named autopif2, which generates a random device fingerprint from the latest Pixel Beta. So let’s have a look at the steps to make full use of this file.
How to Get the Fingerprint PIF.JSON File using Play Integrity Fork
Before starting, please take a backup of all the data on your device, just to be on the safe 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.
NOTE: There are quite a few ways of getting this job done, however, I personally found Termux to be the easiest among all of them. But if you want to try out any other method, then run the generation script from a root manager app that supports the module Action button or from a file explorer app that supports script execution.
- To begin with, flash the wget2 module via Magisk / KernelSU / APatch .
- Then, flash the Play Integrity Fork CI module from GitHub Actions .
- Now, download and install the Termux app from F-Droid.
- Then launch it and execute the following three commands: su //you’ll get a SU request, hit Grant cd /data/adb/modules/playintegrityfix //to change the directory to the module’s sh autopif2.sh –preview // this will give you the fingerprint file
- You can also add a few other parameters to the above command, namely: su -c sh /data/adb/modules/playintegrityfix/autopif2.sh -a -m -p -s -a Advanced -m Match -p Preview -s Strong
- Once done, head over to the below location to access the custom.pif.json /data/adb/modules/playintegrityfix
Direct Download PIF JSON Files
If you don’t want to manually carry out the aforementioned steps, then you may directly get the PIF JSON file from our below guide:
Download PIF JSON File from Here
- How to Pass Strong Integrity Using Revoked/Banned Keybox File!
- How to Pass Play Integrity in New Android 13+ Checks
- Guide to Pass Strong Integrity on Unlocked Bootloader & Root!
- How to Spoof/Fake/Hide Bootloader Unlock Status
- How to Pass Play Integrity Test on any Custom ROM [Video]
- Drw 6 months ago Reply Problem solved. Termux wasn’t prompting me to grant su user access. Found where to enable it in the KSU Next GUI under Superuser.
- Drw 6 months ago Reply I’m getting “su program not found.” Rooted with ksu and susfs. Modules installed are BKI, Play integrity fork, shamiko, susfs for ksu, tricky store, wget2, zygisk lsposed, and zygisk next. Nothing tweaked.
- mario 7 months ago Reply sorry, what do you mean with “Then, flash the Play Integrity Fork CI module from GitHub Actions.” ? i have pif v13 flashed in magisk
- Mohamed 7 months ago Reply Hi, can you please help me with a vaild keybox pleaaase 🙏
- Antonis 7 months ago Reply 1) “Then, flash the Play Integrity Fork CI module from GitHub Actions” https://github.com/osm0sis/PlayIntegrityFork/actions what do i download? 2) and then what do i do with custom.pif.json ?
- Antonis 7 months ago Reply “Then, flash the Play Integrity Fork CI module from GitHub Actions” https://github.com/osm0sis/PlayIntegrityFork/actions what do i download?
(Cancel Reply)
Δ
