Unlike its competitors, Xiaomi has been slow to add battery health information to its devices. While HyperOS or MIUI won’t tell you how degraded your phone’s battery is, you will start to see the effects as it ages. This guide will outline the procedure for extracting battery health metrics from your phone through device logs directly.

To check the battery health on a Xiaomi phone, you may need to manually generate a bug report and find the maximum charge the battery can hold at that time. This value can then be compared with the rated capacity of a new battery to determine its health.

1. Open Settings > About Phone > Detailed Info and Specs.
2. Tap the CPU icon 2-3 times until a pop-up appears to generate a bug report.
3. Tap Agree to the permissions.
4. In the notification bar, you’ll see the progress of generating the bug report.
5. Once it’s done, tap the notification. It will be a ZIP file.
6. Go to Internal storage/MIUI/debug_log/ and find the bugreport.zip file.
7. Extract the ZIP file. Inside, you’ll find another ZIP file. Extract that one too.
8. In the last extracted folder, you’ll see the bug report as a TXT file.
9. Open the TXT file with the native text reader. Tap the search icon (magnifying glass) in the top right.
10. Search for “Estimated Battery Capacity” to find the battery capacity in mAh.
11. Look for “Max Learned Battery Capacity” below it. This is the maximum charge used to reference battery health.
12. To calculate battery health, divide the estimated battery capacity by the max charge, then multiply by 100.
    • Use the formula: (estimated battery capacity/max learned battery capacity)×100

How to Improve Battery Longevity in Xiaomi

The battery health of your phone will inevitably degrade over time with use. Xiaomi phones do not have a centralized battery replacement program, which means that once your battery health declines, getting an authorized repair may be difficult depending on your region and the level of company support available.

1. Avoid using your device in extreme conditions: If your phone becomes excessively hot, whether due to intensive tasks or high ambient temperatures, turn off your device and allow it to cool down before using it again.
2. Avoid charging to 100%: Try to keep your charging cycles between 20% and 80%, avoiding full charges and deep discharges.
3. Use Adaptive Battery: For more dynamic battery management, consider using Xiaomi’s Adaptive Battery feature built into HyperOS or MIUI.

The post How to Check Battery Health in Xiaomi Devices? appeared first on Appuals.

This feature allows the phone to automatically make software adjustments to improve performance and reduce battery drain. It does this at the backend by managing background services and improving running efficiency for certain apps. As a result, the battery may also see a better, and more efficient output for the same level of relative workload.

How Does It Work?

MIUI Optimization reduces stress on the device’s hardware by limiting background activity. This not only improves battery life but is especially important in devices running on low-end hardware. It also limits third-party apps and services, prioritizing Xiaomi’s own system services like MIUI SystemUI, MIUI Screenshot, and MIUI Notifications.

Should I Disable MIUI Optimizations?

Although it’s generally not recommended to disable this feature unless necessary for a specific purpose, it’s important to understand the potential issues it may cause. For one, disabling it could lead to unusual app behavior, and may also expose your device to security vulnerabilities.

Here’s what happens if MIUI Optimization is turned on:

1. The system forces Xiaomi’s implementation of apps, instead of using native AOSP services.
2. All app preferences and permissions are reset to their default settings.
3. App data isn’t synced in the background. This means options like live location, downloading apps, and background updates may be restricted.
4. Some third-party music players and widget animations may not update in real time.
5. The UI may become laggy after an app has been opened from the background.
6. Some mods or apps may not be authorized to install from third-party sources.

How to Turn off MIUI Optimization?

This section outlines the procedure to disable the MIUI Optimization feature, but keep in mind that certain steps may vary based on your phone’s region, and software version.

1. Open Settings and tap on “About phone.”
2. Tap on “MIUI version” repeatedly until you see a pop-up message saying “You are now a developer!“
3. Head back to Settings and scroll down to “Additional settings.”
4. Look for “Developer options” and tap on it.
5. Scroll down to the end till you see “Turn on MIUI optimization.” Tap on the toggle in front to disable the feature on your device.

NOTE: For phones that are running MIUI 13 or later, the option to “Turn on MIUI optimizations” may not be visible. Furthermore, on HyperOS-supported devices, this setting has been renamed to “Turn on system optimization.” To unhide the toggle, you may have to:

1. Go to Settings > Additional settings > Developer options.
2. Scroll down until you see the option to “Reset to default values.” Tap on this to unhide the optimizations tab.
3. Within the Developer options, scroll down to the very bottom of the page. You’ll now see “Turn on system optimization.”
4. Toggle off the setting to disable MIUI optimizations.

The post How to Enable or Disable MIUI Optimization on Xiaomi Devices? appeared first on Appuals.

NOTE: For users running the original version but still receiving the ‘You Need the Official WhatsApp to Log in‘ message, it’s important to note that WhatsApp performs server-side verification using the Google Play Integrity API. Unfortunately, WhatsApp will not support devices that do not pass these checks.

Why is WhatsApp Not Verifying App Status?

1. WhatsApp cannot validate the phone number associated with your device.
2. Your phone number was likely banned or flagged due to using the app in a vulnerable environment.
3. You may have rooted your device or installed a custom ROM recently.
   • It is possible that the newly installed ROM is not secure and fails to pass basic Play Integrity API checks on the device.
4. You may have linked a modded WhatsApp application to your mobile number.

Pre-Requisite: Check if Your Phone Number is Banned

This authentication error message can mean one of two things: either there is an issue with your account, or your phone is the culprit. In the third off-case scenario, if you’re not using the official version of the app, download the verified version from the Google Play Store.

For users with former complaints, check the following. This will give you a rough idea of isolating the cause of the issue:

1. Get a different phone and try to log in there.
   • If it works, the issue likely lies in your device. If not, your phone number may be banned.
2. On your current device, try a different phone number.
   • If it works, your phone number is likely flagged.

If your phone number works on another device and a different number works on your current device, the most commonly suggested solution is to flash your phone back to its stock ROM.

Companion Device Linking (Non-Root)

To bypass the official WhatsApp error message, you may need to use a WhatsApp Business account and link it to a companion device. With this method, you won’t need to root your device but will require a different phone, preferably one with no account linked to WA Business.

1) Link as Companion Device on Different Phone

In this device linking method, you’ll need a secondary device to log into WhatsApp. Before proceeding, sync your contacts via Gmail, and download WA Business from the Google Play Store on your current device.

1. Open WA Business, and tap “Agree and continue” to accept the Terms of Service.
2. On the verification page, tap the three vertical dots on the top right-hand side and select “Link as companion device.”
3. Scan the QR code with the secondary device.
4. Log out of WA Business on your secondary phone.

2) Log Back in On Your Primary Device

Once you’ve linked your phone as a companion device on your secondary device, you’ll be able to log back into your primary phone. Try to log back in and check if WhatsApp shows the same error message.

Spoof Bootloader via Magisk (Root Required)

WhatsApp is known to flag devices running on unlocked bootloaders, which means that re-locking the bootloader may resolve the issue. However, if your device is rooted, you could spoof the bootloader status and hide root access from the app itself.

1. Flash Magisk Kitsune, a fork of the official Magisk app, which has older features like MagiskHide re-added.
2. Open Magisk, and tap on the Settings gear icon on the top right-hand side.
3. Scroll down to “Zygisk” and toggle it on.
4. Below Zygisk, tap “Configure DenyList.” Tap the three vertical dots on the top right-hand side and select “Show system apps.”
5. Add WhatsApp, Play Store, and Google Play Services to the list.
6. Flash LSPosed’s Magisk module and install BootloaderSpoofer.
7. In BootloaderSpoofer, check all apps to hide the bootloader status from.
8. Open Magisk again, and tap on the Settings (gear icon) on the top right-hand side.
9. Scroll down to “Hide the Magisk app,” and tap on it.
10. Rename the file to a random app name and tap “OK.”
11. Magisk is now spoofed as a different app with a random package ID.

After completing these steps, you may need to disable Play Protect from within the Google Play Store. The steps below outline the procedure to do so:

1. Head on over to the Google Play Store, and tap on your account’s profile picture on the top right-hand side.
2. Tap on “Manage apps & device.”
3. Tap on the Play Protect icon and head over to the service’s settings. To do this, tap on the gear icon in the top right-hand side.
4. Toggle off the “Scan apps with Play Protect” setting.

Once Play Protect is disabled, reboot your device and try to verify your phone number on WhatsApp. If it still doesn’t work, check your Play Integrity status. On most custom ROMs, these checks fail to pass STRONG_INTEGRITY. In case you have issues with SafetyNet (now known as Play Integrity), consult our guide on bypassing Play Integrity checks on Android.

The post How to Fix “You Need the Official WhatsApp to Log in” Error appeared first on Appuals.

It’s important to note that TWRP may not be available for all Android devices. You can check if your device is supported by TWRP on TeamWin’s Devices page.

If your phone doesn’t support TWRP, it can potentially be ported over to your specific phone model. However, it might require a basic understanding of Linux commands and compiling AOSP from scratch. Appuals offers an in-depth guide to port TWRP to any Android device.

How to Flash TWRP on Your Android Phone?

This section provides a general outline for flashing TWRP on your phone. However, please note that some steps may vary depending on the specific device.

NOTE: It is strongly advised to consult the official documentation for your device before proceeding with any flashing process. Each device page includes a detailed section outlining the specific requirements for running TWRP on that particular model.

Pre-Requisites

Before initiating the flash process, there are a few things you will need in advance. Without these, it is not recommended to move any further with flashing TWRP, as an incomplete flash could possibly result in a soft-brick, too.

• Unlocked Bootloader: Your device must have an unlocked bootloader. We have detailed guides on the unlock process for Xiaomi, Huawei, Samsung, and OnePlus devices.
• PC with Internet Connection: You will need a PC, preferably Windows, to download and install the recovery via ADB.
• ADB Drivers: To connect your phone to your PC and communicate via the Android Debug Bridge, you will need ADB drivers installed beforehand. We have an in-depth guide on setting up ADB on Windows.
  • You can download Minimal ADB and Fastboot directly for ADB commands to run on Windows Terminal.
• USB Cable: For connecting your device via USB, you will need a cable that is capable of transferring data to and from your phone.
• Enable USB Debugging: Your phone will need to have USB Debugging enabled in order to communicate with the PC via Android Debug Bridge.

Fastboot Manual Flash (No Root Required)

If your device isn’t rooted, you’ll have to stick to Manual Flash. This procedure may require a bit more user intervention, but it is advised that non-rooted devices avoid Automatic Flash via TWRP’s app, which only works for rooted phones.

1) Find TWRP for Your Device

To check if your device is supported by TWRP, visit TeamWin’s devices section, where you’ll find a list of mobile phone manufacturers, each with a list of supported mobile devices. These links will take you to the download page.

You will need to download the IMG file for the recovery; this file will later be flashed onto the phone via ADB. The device page will also link to TeamWin’s GitHub repository for the specific model, providing information on known bugs and working features within the recovery. You may want to review this list before downloading the latest file version.

2) Boot Into Fastboot Mode

To boot into Fastboot mode, you can either use an ADB command or manually use your phone’s manufacturer-defined button combination after turning off your device. In this state, connect your phone to a PC via an external USB cable.

1. Connect your phone to your PC using an external USB cable.
2. Launch Minimal ADB and Fastboot. This will open a Terminal window in Command Prompt.
3. Type adb devices in the terminal window. This will check to see if your phone is being detected by ADB.
4. If your device is recognized, type adb reboot bootloader to boot directly into Fastboot mode.

NOTE: When connecting your phone to ADB or your PC for the first time, you may need to manually grant permissions on your device. After connecting the phone, when you enter the “adb devices” command, a pop-up may appear on your phone requesting user authorization. Simply tap “Allow” to proceed.

3) Flash the Recovery IMG File

Once in Fastboot mode, you will need to flash the recovery image file. For reference, this is the same file you downloaded in the first step.

1. Copy the IMG file to the Minimal ADB and Fastboot directory.
   • This is commonly found inside C:\Program Files (x86)\Minimal ADB & Fastboot, unless manually changed.
2. Rename the copied file to twrp.img for ease of flashing. If not, you may need to manually drag over the file when needing to provide the image file path.
3. Open the Minimal ADB and Fastboot terminal, and type fastboot devices to ensure your device is detected in Fastboot mode.
4. If it is, type fastboot flash recovery twrp.img. This will initiate the flashing process on your device.

The flashing process may take a few minutes to complete. Once finished, the screen will display a message showing the total time taken: “Finished. total time: X.XXs” (where X is the duration of the process).

To reboot into TWRP, you will need to enter the command “fastboot reboot recovery,” which will reboot your phone into TWRP automatically. If the process is completed without any issues, you may unplug your phone from the PC. TWRP is now installed on your device.

The post How to Flash TWRP Custom Recovery on Android? appeared first on Appuals.

Why Do You Need Camera2 API?

In a nutshell, the Camera2 API provides apps with the tools they need to use or control a phone’s camera hardware. While the specifics of how it works are beyond the scope of this guide, it’s important to know that most third-party camera apps rely on it. This is because, unlike other services, a camera app itself needs direct access to leverage the full capabilities of the available hardware.

For instance, the default WhatsApp camera has options to capture photos or videos, enable flash, and switch between front and rear cameras. In contrast, there are full-fledged camera apps such as GCam, where you need features like capturing RAW images, adjusting white balance, shutter speed, ISO, manual focus, etc. The latter is exactly what the Camera2 API is used for.

Check if Camera2 API is Enabled on Your Device

Start by checking if the Camera2 API is enabled on your phone. You can either choose to scour online forums to check compatibility or use a third-party application that checks for you. If you prefer the latter, download the “Camera2 API Probe” from the Google Play Store.

The app will give you complete details on your phone’s Camera2 compatibility. You may see certain terms under the “Hardware Support Level.” Here’s what they mean:

1. LIMITED: Camera ports may not function as intended, and you will probably encounter potential bugs and glitches down the line.
2. LEGACY: Basic camera functions will continue to work, but advanced controls will be limited.
3. FULL or LEVEL_3: Your phone has the Camera2 API enabled and is fully compatible with third-party camera ports.

Camera2 API Probe will give you complete information on what features are supported and where the boundaries are drawn. It will isolate the rear and front cameras and provide complete details on supported video FPS, focus modes, exposure settings, stabilization modes, and preview sizes.

How to Enable Camera2 API on Your Android Phone?

This section will detail some of the different ways to enable the Camera2 API on your device. However, be cautious that each of the processes requires some kind of change to the system files. If you simply need a third-party camera app, try GCam Go — it has all the basic camera features and doesn’t require a phone to have Camera2 enabled with full support.

1) Camera2API Magisk Module (Root)

With Magisk’s modular approach, simply flashing the fix would be enough to bypass the Camera2 limitations, although it does require your phone to be rooted.

1. Download the Camera2API module from jhangyu’s GitHub repository.
2. Flash the module
   • To do this, open Magisk > Modules (bottom-right corner) > Install from storage > select the downloaded .zip file.
3. Restart your device.

2) Terminal Emulator (Root)

Users using a different root tool, such as KernelSU, can use the Terminal Emulator app to modify the build.prop files and enable the API.

1. Download Terminal Emulator on your device.
   • You can find the .APK file for this app on online forums and websites.
2. Grant the app root access by typing in: su
3. Once done, type in both commands below:
   • setprop persist.camera.HAL3.enabled 1
   • setprop vendor.persist.camera.HAL3.enabled 1
4. Press Enter, and reboot your device.

3) TWRP (Non-Rooted, Unlocked Bootloader)

Users who aren’t on rooted devices can use TWRP to push both commands listed above into the build.prop file. It is advised that you back up all of your data beforehand and proceed with caution since tinkering with the wrong files can certainly hard-brick your device.

1. Set up ADB on your PC.
   • If you’re setting up ADB for the first time, it is highly recommended that you follow along with our detailed guide on the subject.
2. Download the TWRP recovery file for your device, and rename the file to twrp.img.
3. Connect your phone to your PC via a USB cable.
4. Open TWRP by typing the following commands into the Platform Tools’ Command Prompt.
   • adb devices
   • adb reboot bootloader
   • fastboot boot twrp.img
5. Once your phone has booted into TWRP, swipe the bar that reads “Swipe to Allow Modifications.”
6. On Command Prompt, type in the following commands to enable the Camera2 API via ADB Shell.
   • adb devices
   • adb shell
   • setprop persist.camera.HAL3.enabled 1
   • exit
   • adb reboot

Once you’ve followed through with either one of the steps above, check your Camera2 API status again and use Google Camera, or other ports with ease. Keep in mind though that resetting your device may prompt you to follow this procedure again.

The post How to Enable Camera2 API on Android? (ROOT & NO ROOT) appeared first on Appuals.

However, it’s important to note that the ability to record calls may depend on your phone model, the version of Android you’re using, and your geographical location—some regions have strict laws regarding call recording. In this guide, I’ll walk you through several methods to record calls on Android without rooting your device, step by step.

But before diving into the workarounds and discussing third-party apps to record phone calls, let’s first cover why recording calls on Android has become more complicated compared to the past. This will help you choose the best solution and avoid any legal issues.

Lastly, please remember that this guide is strictly for educational purposes, and Appuals does not endorse any non-consensual call recording without the other party’s knowledge, as this is illegal in some regions. Proceed with caution.

Complications with Call Recording, Google’s Policy Changes, and Legal Considerations for Android

1. As of May 11, 2022, Google implemented a significant policy change that prohibits third-party call recording apps from using the Accessibility API for recording calls. This decision was made to close loopholes that allowed developers to exploit this feature for unauthorized purposes. The Accessibility API is intended for apps that assist users with disabilities, not for call recording.
   
2. With Android 10 and later versions, Google tightened restrictions even further. Many third-party apps can no longer effectively record calls because they can only capture one side of the conversation or fail entirely. This has led to a decline in the availability of reliable call recording solutions for users on newer Android versions.
3. While some Android devices come with built-in call recording features, their availability often depends on the region and carrier. Moreover, many devices only allow automatic recording for unknown numbers, further limiting user options.
4. The legality of recording calls varies significantly by location. In the United States, federal law permits one-party consent (meaning only one participant needs to know about the recording). However, some states require all parties to consent. Users must be aware of these laws to avoid legal repercussions.
5. Recording calls raises ethical questions about privacy and consent. Users should always inform the other party that the conversation is being recorded, both as a courtesy and to comply with legal standards.

Now that we understand the complications of recording phone calls on the latest Android versions without root access, let’s discuss some methods to help you achieve this.

Method 1: Using Built-in Call Recording Features

Some Android devices come with a built-in call recording feature.

Check Compatibility

1. Ensure your phone runs Android 9 or higher and has the latest version of the Phone app.
2. Be aware that call recording may not be available in all regions due to local laws.

Recording a Call

1. Launch the Phone app on your device.
2. Start a call as you normally would.
   
3. During the call, tap on the Record button. On some devices, this might be in a menu (like Samsung).
   
4. To stop, tap the Stop Recording button when you’re done.
   
5. Find your recordings in the call history or a designated folder within the app.
   

READ NEXT: How to Turn Off Google’s Call Recording Announcement?

Method 2: Using Google Voice

If your device doesn’t support built-in recording, Google Voice is a great alternative, especially for incoming calls.

Setting Up Google Voice

1. Install the Google Voice app from the Play Store.
   
2. Open the app and log in with your Google account.
   
3. Tap on the gear icon for settings.
4. Under Calls, check the box for Call Options to enable recording.
   

Recording Calls

1. When someone calls your Google Voice number, answer it.
2. During the call, press 4 on your keypad to start recording. An announcement will confirm that recording has started.
3. Press 4 again to stop recording before hanging up.
4. Recordings can be found in your Google Voice account under recorded calls.

Method 3: Using Third-Party Apps

If neither of the above methods works for you, third-party apps are another option. Here are two popular choices:

1. Automatic Call Recorder ACR

Installation and Setup

1. Download Automatic Call Recorder ACR from the Play Store.
   
2. Open the app and allow it access to your contacts and microphone.
   
3. Enable Accessibility Service (for Android 10+):
4. Go to your device’s settings.
5. Navigate to Accessibility and turn on the service for Automatic Call Recorder.

Recording Calls

1. Open Automatic Call Recorder.
2. Go to Settings and enable call recording for incoming and outgoing calls.
   
3. The app will automatically record calls based on your settings.
   
4. Open the app to view and manage your recordings—save them, delete them, or share them as needed.
   

2. Cube ACR

To effectively use Cube ACR for recording calls on your Android device, especially in light of recent restrictions, you need to set up both Cube ACR and its companion app, Cube ACR Helper.

Installation and Setup

1. Start by downloading Cube ACR from the Google Play Store.
   
2. Launch the app and grant it access to your contacts and microphone to enable call recording.
   
3. Tap on Install Helper.
   
4. Since Cube ACR may not function optimally on newer Android versions without additional support, download the Cube ACR Helper APK from their official website.
   
5. Go to your device’s Settings, then navigate to Security or Apps & Notifications. Find Install unknown apps, select your browser or file manager, and enable Allow from this source.
6. Locate the downloaded APK file for Cube ACR Helper and tap on it. Follow the prompts to install the app.
7. Open Cube ACR Helper.
8. Grant the necessary permissions for the app to function correctly by allowing microphone, storage, and phone access.
   
9. Tap Allow for each permission request when prompted; if you accidentally deny any, you can grant them later through your device settings.
10. Tap on the option labeled Enable App Connector.
11. Tap Go to Apps and select Cube ACR Helper.
    
12. Tap the three-dot menu (⋮) at the bottom.
13. Enable the option labeled Allow restricted settings by tapping it and confirm any further prompts by tapping OK.
    
14. Go back to the Cube ACR Helper app and tap Go to Accessibility.
    
15. Select Downloaded apps, and from the list of downloaded apps, select Cube ACR Helper.
    
16. Toggle the option labeled Use Cube ACR app connector to On to enable integration for call recording.
    
17. Go back to Cube ACR Helper. The setup is now complete, and the two apps are connected. Tap Open Cube ACR.
    
18. Go to the Settings menu within Cube ACR. Here, you can adjust the audio source to enhance recording quality and select other preferences as needed.

Recording Calls

1. You can choose to record all calls automatically or manually start recordings during calls based on your preference.
2. If set to automatic, Cube ACR will begin recording without any additional action required from you when you make or receive calls.
   
3. Make sure both Cube ACR and the Helper are running in the background when you start the call you want to record. The app will automatically record the call.
4. Open the Cube ACR app to find all recorded calls stored within the application for easy playback and management.

Method 4: Using External Devices

If you encounter issues with call recording through apps, consider using an external device as a workaround:

1. Place your phone on speaker mode during the call.
2. Utilize another smartphone or digital recorder with a microphone to capture both sides of the conversation clearly.
3. After recording, transfer files from your external device to your Android phone if needed for storage or playback.

Recording calls on Android without rooting is definitely achievable through built-in features, Google Voice, third-party apps like Automatic Call Recorder and Cube ACR, or even external devices if necessary. Always remember to check local laws regarding call recording before proceeding, as legality varies by region.

The post How to Record Phone Calls on Android (No Root)? appeared first on Appuals.

Why Do Banking Apps Block Rooted Devices?

While the discussion of bypassing built-in security measures to run apps with sensitive financial data is still up for debate, here’s why companies restrict rooted phones from running banking apps:

• Your financial data is extremely sensitive; root access is simply a security risk.
• Companies need to protect themselves. It’s their responsibility to secure their clients’ information and funds; any breach could result in extremely dire consequences for the bank.
• A rooted device is an easy target for malicious actors; there is a small but existent chance that they could steal your money without you knowing.

How to Run Banking Apps on a Rooted Phone?

Disclaimer: The information provided in this article is for educational purposes only. Modifying your device to run banking apps on a rooted phone involves security risks and may void warranties or violate terms of service with your hardware provider and banking applications. Proceed at your own risk. We are not responsible for any damages or losses incurred as a result of following this guide.

The main idea for banking apps to run on rooted phones is to bypass device state detection by hiding privileged access from these apps. While there are other root solutions, this section will particularly touch upon the most common tool, Magisk.

1) Shamiko in Zygisk

With anything Magisk, you’ll be looking at a modular approach — using Magisk modules — to circumvent root detection and hide the device state from the app. In the past, the MagiskHide module was the go-to way to bypass SafetyNet Attestation, but in 2021, the feature was axed.

Note: After the retirement of MagiskHide, Zygisk took its place. It is essentially a module that runs Magisk directly in Zygote, a process that Android uses to start apps, and handle the forking of each application process.

Make Sure Your Device Passes Play Integrity

Before proceeding to flash Shamiko, all of your Play Integrity checks must be passed. Most banking apps, if not the majority, would do just fine without STRONG_INTEGRITY, but rooting, or even unlocking the bootloader of your device unchecks the rest.

We have a detailed guide for bypassing Play Integrity API checks for all apps. They won’t be included in this guide since they are a must-install, even if you don’t need to run banking applications on your device. Without passing the checks, app support on your phone would likely be limited.

1. Update Magisk to Canary Release 27005+ since Shamiko won’t be compatible with previous releases.
2. Download the Shamiko module from LSPosed’s GitHub repository.
3. Uninstall any bank apps that you’ve installed.
4. Open Magisk and tap the settings (gear icon) on the top right-hand side.
5. Scroll down to Zygisk and turn on the feature via the toggle in front.
   • Don’t enable “Enforce DenyList” since this method uses Shamiko instead of Zygisk itself to bypass detection for apps in DenyList.
6. Go back to the home page, and tap on Modules (jigsaw puzzle-like icon) on the bottom right-hand side.
7. Tap on “Install from Storage” and select the downloaded Shamiko module.
8. Once the installation is complete, reboot your device.
9. Open Magisk again and check if Zygisk is enabled.
10. Go to settings and tap “Configure DenyList.”
11. This will open a list of all apps installed on your phone. The selected apps in the list will be used as a reference to hide root from them.
    • Tap on the three vertical dots on the top right-hand side and select “Show system apps.”
    • Select all banking apps from which you wish to hide root access.
    • Check all tick boxes under “Google Play Services” or “com.google.android.gms”
12. Reboot your phone once again.
13. Open Magisk and check to see if Zygisk is still enabled. Now, once root is hidden from selected apps, the Magisk app itself needs to be hidden.
14. Go to Magisk’s settings and tap “Hide the Magisk app.”
    • This will duplicate the app under a different name that can be used to bypass Magisk detection, as many apps look for Magisk itself to detect if a phone is rooted.
15. Rename Magisk to whatever you wish, and tap “OK.”
16. A popup will appear, asking you to add the shortcut to your home screen. Select “OK” or “Allow.”
17. Remove the Magisk icon from your home screen.
18. Reboot your device, and your banking apps should be up and running.
    • Keep in mind that some apps may still fail to work. However, in the majority of cases, apps tend to start up without any issues.

Additional Step for Xiaomi Phones

If you’re on a Xiaomi device, you’ll need to check off one last step before opening up your banking apps, and that is to hide certain apps from accessing the list of installed apps. See, when an app has access to the list of all apps on your phone, it’ll likely find root tools and modules and can infer that the device is insecure.

1. Long-press the app you need to hide root from, and select “App info.”
2. Head on over to Permissions > Other Permissions.
3. Scroll down to find “Access list of installed apps,” and uncheck the permissions in front of it.

2) MagiskHide (Deprecated)

Some online threads have mentioned the procedure to bypass root detection via MagiskHide. As discussed above, this module is deprecated and won’t function on the latest versions of banking apps. Back when it was still the go-to method, it wasn’t reliable, really.

With MagiskHide, it was a constant rat race to install new updates when older ones got patched. This is why, even if you have an older version of the said module running, it may be a good time to switch to Shamiko.

What if Apps Still Don’t Run?

On the off chance that your banking apps still fail to start, there may be an issue with spoofing your phone’s hardware integrity, or the root modules may not have been configured correctly. Here’s what you can try.

1) Check if Your Device Passes Play Integrity Checks

The Play Integrity (PI) API allows developers to detect and verify the authenticity of device software and hardware. If PI checks aren’t passed, you won’t be able to use most banking services. Chiteroman’s PlayIntegrityFix (PIF) is commonly the go-to module for bypassing basic verification checks.

You can check your device’s Play Integrity status using the ‘Play Integrity API Checker‘ on the Google Play Store. If it doesn’t pass the basic tests, it is highly recommended that you flash the PIF module in Magisk manually.

2) Disable Chiteroman’s BootloaderSpoofer (If in Use)

The BootloaderSpoofer module is primarily used to hide the bootloader lock status from phone apps, which is sometimes essential when working with services with better root detection techniques. However, a few users have reported that using the spoofer with banking apps sometimes leads to a positive on the root status.

If you have the module installed, remove the app from the spoofer and clear the app cache before trying again. BootloaderSpoofer is based on the Xposed framework, which has a certain reputation for being easy to detect.

3) Try a Clean Install of Magisk

If all else fails, consider a clean install of Magisk, repeating the entire procedure above and manually flashing the Play Integrity Fix module. This will single out any issues with the module or Magisk itself. Trying a different version of Magisk can also help, but this isn’t recommended since you’ll need to install a similar version of Shamiko that is compatible with the version you’re using.

If your banking app, by some chance, requires Play Integrity to meet its “STRONG_INTEGRITY” requirements, you need to know that it is nearly impossible to have that enabled on a device with an unlocked bootloader; you’ll either need to revert back to a locked bootloader or make system-level changes that are beyond the scope of this guide.

4) Check if Your Phone Has Any Root Files in Storage

As mentioned above for Xiaomi phones, most devices and apps use access to internal storage and scour documents and files to see if any files signal that the device is modified. To be on the safe side, delete any recovery files, such as twrp.img, if you have them in your device’s storage.

The post How to Run Any Bank App Safely on a Rooted Phone? appeared first on Appuals.

No need to worry if you’re not a tech expert—this really isn’t rocket science. Once you get the hang of it, it’s a lot like giving your phone a quick spring cleaning. And let’s be honest, who doesn’t love a phone that runs smoother and faster? Plus, it’s oddly satisfying to finally get rid of those apps you never asked for in the first place!

I’ll walk you through everything, from prerequisites to the actual debloating process, step by step. Let’s get started!

Prerequisites

• Always back up important data before making changes like this.
• Removing certain system apps can lead to instability; if unsure, consult forums or communities for advice specific to your model.

Before diving into the debloating process, there are a few things you need to set up.

1. Enable Developer Options and USB Debugging

1. Open the Settings app on your Xiaomi device.
   
2. Tap on About phone.
3. Find the MIUI/HyperOS version and tap it seven times. You should see a message saying “You are now a developer!”
   
   
4. Go back to Settings, then tap on Additional settings.
   
5. Look for Developer options, and enter it.
   
6. Find USB debugging and toggle it on. Confirm any prompts that appear.
   

2. Install ADB and Fastboot Tools

You will need ADB (Android Debug Bridge) installed on your computer. Here’s how:

1. Download the latest version of ADB and Fastboot tools from a reliable source (like the official Android developer site).
2. Extract the downloaded zip file to a folder on your computer.

3. Install Java SDK

ADB requires Java to run, so make sure you have it installed:

1. Download the latest version of OpenJDK or Oracle Java from their official website.
   
2. Follow the installation instructions for your operating system.

4. Install Universal ADB Drivers

To ensure your computer recognizes your Xiaomi device:

1. Download Universal ADB Drivers from a trusted source.
2. Install them by following the on-screen instructions.

5. Connecting Your Device

Now that everything is set up, let’s connect your phone to your computer.

1. Use a USB cable to connect your Xiaomi phone to your computer.
2. When prompted on your phone, select File Transfer (MTP) mode.
   
3. You may see a prompt asking for permission to allow USB debugging; make sure to allow it. Verifying ADB Connection

Before proceeding, let’s check if ADB recognizes your device:

1. Open a command prompt or terminal window in the folder where you extracted ADB tools.
2. Type the command ‘adb devices’ and press Enter.
3. On your phone’s screen, you should see a prompt to allow or deny USB Debugging access. Tap Ok.
   
4. Now enter the ‘adb devices’ command again in the command prompt. If you followed everything correctly, you should see a list of connected devices. If you see your device listed, you’re ready to go!
   

Debloating Your Xiaomi Phone

Now we can start removing those unwanted apps!

Using Xiaomi ADB/Fastboot Tools

1. Get the latest version from Szaki’s GitHub repository or another trusted source.
2. Open the downloaded tool (it may require Java to run). If you’re using Windows, double-click on XiaomiADBFastbootTools.jar.
   
3. Ensure your phone is still connected via USB and recognized by the tool.
4. The tool will display a list of installed apps. Carefully select the apps you want to remove.
   
5. Be cautious not to uninstall essential system apps like Dialer or Settings, as this can cause issues with your device.
6. Click on the uninstall button at the bottom of the application window.
   
7. Wait for confirmation that the apps have been successfully removed.

Using ADB Commands

If you prefer using command-line commands, follow these steps:

1. Open a command prompt or terminal window in your ADB folder.
2. To uninstall an app, use this command format:
   adb shell pm uninstall -k –user 0 package.name
3. Replace package.name with the actual package name of the app you want to remove (for example, com.google.android.youtube).
4. After executing the command, if you see “Success,” that means the app has been uninstalled successfully.

List of Common Bloatware That Is Safe to Remove

Below are some common apps that many users choose to remove, which can be safely removed without affecting the system.

1. Analytics
2. App Vault
3. Backup
4. Browser
5. CatchLog
6. Cleaner
7. Compass
8. Digital Wellbeing
9. Downloads
10. FM Radio
11. Facebook
12. Feedback
13. Games
14. GetApps [Only for Global ROM]
15. Hybrid Accessory
16. MSA
17. Market Feedback Agent
18. Mail
19. Market Feedback Agent
20. Mi Cloud
21. Mi Credit
22. Mi Drop
23. Mi Mover
24. Mi Pay
25. Mi Share
26. Mi Recycle
27. MiConnectService
28. MiPlayClient
29. Mi Wallpaper Carousel
30. MiuiDaemon
31. Music
32. NextPay
33. Notes
34. PAI
35. Partner Bookmarks
36. Quick Apps
37. Quick Ball
38. Search
39. SMS Extra
40. Scanner
41. Services & Feedback
42. Soter Service
43. UniPlay Service
44. Weather
45. Yellow Pages
46. Xiaomi Sim Activate Service
47. Xiaomi Service Framework

Apps You Should Never Uninstall:

1. VsimCore – Removing this app will prevent the Control Centre tile from displaying your data usage.
2. MiVideo – Uninstalling this app will make it impossible to view or edit Slow Motion videos taken with the stock camera.
3. Battery & Performance – Essential for monitoring and optimizing your phone’s battery performance.
4. Power Detector – Important for detecting and managing power usage on your device.
5. Security App – Deleting this app could cause your device to bootloop, potentially rendering it unusable.
6. Mi Wallpaper – Necessary for managing wallpapers and related features on your device.

While the above-provided list of apps safe to remove from your device without breaking it is comprehensive and reported by many users to be accurate, still make sure to do some research on any app before removing it!

After debloating:

1. Restart your device to ensure all changes take effect properly.
2. Check if everything is running smoothly and verify that no essential apps were accidentally removed.

Enjoy a cleaner and faster device! And if you still have any questions about any part of the guide, feel free to drop them in the comments section below.

The post Debloat Your Xiaomi Phone: List of Safe to Remove Apps appeared first on Appuals.

But here’s the good news: installing .xapk files isn’t as tricky as it seems. With a few simple steps, you’ll have them up and running in no time. In this guide, I’ll walk you through everything you need to know so you can get your apps installed without any headaches.

But before diving into the guide, let’s learn a little more about .xapk files so that we have better context while dealing with them.

What Even Are XAPKs?

XAPK files are a different way to install Android apps, especially for larger ones that need extra resources beyond what a regular APK file can handle. Basically, they’re like a compressed package that includes both the main APK file and any additional data the app might need, such as graphics or media. This extra data usually comes in a file called an OBB.

One of the main reasons XAPK files exist is because Google Play limits APK files to 100MB. So for bigger apps, developers often have to split them into multiple downloads, which can be a hassle for users. XAPK solves this by bundling everything together, so you just download and install everything in one go.

The catch is that XAPK files aren’t supported by Google Play. That means you usually have to download them from third-party websites or app stores. Because of that, it’s super important to only grab XAPK files from trustworthy sources to avoid any security risks.

In general, XAPK files are popular with gamers or people who want apps that might not be available in their region or have been removed from the Play Store. They make the whole process of installing larger apps way easier by packaging everything into one neat file.

To install XAPK files on your Android device, follow this detailed guide covering everything from prerequisites to the installation process. XAPK files are essentially APK files bundled with additional data, making them a convenient option for installing apps, especially games that require extra resources.

Prerequisites

Before diving into the installation process, ensure you have the following:

1. Make sure your device is running Android 6.0 or higher.
2. Download the XAPK file you wish to install from a trusted source.
3. You may need a file manager app to navigate and manage files on your device. You can download one from the Google Play Store if you don’t have it already.
4. For easier installation, consider downloading any reliable XAPK Installer from the Google Play Store. For this guide, I’ll be using a well-known and easy-to-use file manager: ZArchiver.

Step 1: Enable Installation from Unknown Sources

1. Go to your device’s settings by tapping on the gear icon.
   
2. Scroll down and select Security, Privacy or Special App Access, depending on your Android version and vendor. I am using stock Android.
3. Look for an option labeled Install unknown apps or Unknown sources and tap on it.
   
4. This will give you a list of apps. You can then individually allow them to install apps from sources other than the Google Play Store. In my case, since I am using ZArchiver to install the XAPK file, I will allow it to install apps on my device.

Step 2: Download and Prepare the XAPK File

1. Use a trusted website to download your desired XAPK file. For this guide, I have downloaded the Roblox XAPK from APKPure.
   
2. Open your file manager app and navigate to the Downloads folder where your XAPK file is saved.

Step 3: Install Using ZArchiver (Recommended Method)

1. If you haven’t already, download the ZArchiver app from the Google Play Store.
   
2. Launch the app and allow any necessary permissions.
3. Navigate to the folder containing your downloaded XAPK file.
   
4. Tap on the XAPK file and select Install.
   
5. Confirm any prompts that appear to start the installation process.
   
6. Once installed, you can open and use the app as usual.

Manual Installation (Alternative Method)

If you prefer not to use ZArchiver, you can manually install an XAPK file:

1. Long-press on the XAPK file in your file manager and select Rename. Change the extension from .xapk to .zip.
   
2. Use a file extraction app like RAR (available on Google Play) to open the ZIP file.
   
3. Extract its contents to a folder of your choice, or you can simply choose the ‘Extract here’ option to extract the ZIP file contents into the same folder where the ZIP file is.
   
4. Inside the extracted folder, look for an OBB folder (If it does not exist, skip to the last step). This folder contains additional data needed for some apps or games. Copy this OBB folder.
   
5. Navigate to Internal Storage > Android > OBB and paste the copied OBB folder here.
   
6. Go back to the extracted folder and locate the APK file. Tap on it to start the installation process and follow any prompts that appear during installation.
   

After completing either method, you should find your newly installed app in your app drawer. Tap on it to launch and enjoy!

Just follow these steps, and you’ll be able to install any XAPK file on your Android device without any hassle. If you run into any issues or need help, don’t hesitate to ask!

The post How to Install XAPK Files on Android? appeared first on Appuals.

As the name suggests, Play Integrity will check if the device hardware is secure (unmodified, non-rooted) and verify app binaries to ensure they come from a legitimate source. Google allows developers to use the Play Integrity API in their apps to identify if there are any security risks; what the app does next is up to the creator.

Most apps wouldn’t care for all integrity checks to pass, but some, with sensitive data, like banking and government apps, block such phones from using their service. Here are some of the reasons why Play Integrity checks may fail on your device:

• The device has an unlocked bootloader.
• The device is rooted.
• The device is running a custom ROM.
• If a fix is implemented, it may be patched or conflicting with other modules.
• The device is using an unsigned ROM.
• The DenyList in Magisk may not be configured to exclude Google services.

How to Bypass Failed Play Integrity Checks?

To bypass Play Integrity checks, the device will either need to spoof or bypass the said requirements to find its way around these checks. There’s a legitimate way, and then there are workaround modules that’ll essentially trick Play Integrity into showing the green checkmark and subsequently allow apps with strict device state detection to run on your phone.

Revert to the Device’s Stock ROM (Lock Bootloader)

Since Play Integrity verifies the device status, the most straightforward and legitimate way to retrieve that status is to revert to a locked bootloader and flash the manufacturer’s stock ROM. This would be the simplest and most effective way to avoid the hassle of periodically updating specific modules inside Magisk.

In addition, if your banking service takes security seriously, you may want to consider opting out of workarounds. If and when a Play Integrity module is patched, chances are that your financial services will detect that and may block certain services, like online banking, from running on your account or, even worse, lock you out of your account.

Play Integrity Fix Module (Keeps Root & Bootloader Status)

Disclaimer: The methods in this guide involve changing your device’s operating system and security settings, which can be risky. Doing this might void your device’s warranty and could lead to data loss, system issues, or security vulnerabilities. It may also break the rules of certain apps or services, possibly resulting in account suspensions or bans. Proceed with caution. This guide is for educational purposes only. We are not responsible for any damage, loss, or legal issues that may arise from following these instructions.

For most people who root their devices via Magisk, the Play Integrity Fix is a must-install. This module bypasses the Play Integrity limitations and spoofs apps to verify the device’s authenticity. However, before proceeding, there are certain elements you need to keep in check.

Pre-Requisites

1. Make sure that the latest version of Google Play Services is installed on your phone.
   • You can use a direct link to the Play Store to check if there is an option to update Google Play services.
   • You can also open Play Store > Tap on your account photo (top right-hand side) > Settings > About > “Update Play Store.”
2. Make sure that you are using a signed custom ROM on your device.
   • You can use the RomSignCheck app (external install) to check if your ROM is signed. If so, it will display a “ROM sign normal” or “ROM sign is testkey” message.
3. Update to the latest version of Magisk, or switch to Kitsune Mask, a fork of the official Magisk Manager with the old MagiskHide features re-added.
   • For KernelSU users, flash the Zygisk Next module to access Zygisk (built-in for Magisk users).
4. Install MT Manager on your device. This will be used to install working keybox files for Play Integrity tokens.

Install Procedure

The general overview of this section is that it’ll hide selected apps from being detected in a rooted environment and will install Magisk as a proxy application. If a Trusted Execution Environment (TEE) is broken, it’ll attempt to fix it, use Shamiko to hide Zygisk, and finally flash the Play Integrity Fix module.

1) Hide the Magisk App

The first plan of action is to hide the Magisk app itself. Some services access the list of installed apps on the phone, and if they find Magisk, they use that information to extrapolate that the device is modified. Magisk allows you to replace itself with a proxy app with a random package ID.

1. Open Magisk and tap on the Settings (gear icon) on the top right-hand side.
2. Scroll down to “Hide the Magisk app,” and tap on it.
3. Rename the file to a random app name and tap “OK.”
4. Magisk is now spoofed as a different app with a random package ID.

2) Configure the DenyList

The selected apps in the DenyList are a set of services that would be referenced to be blacklisted from root detection. This means that modules such as Shamiko and MagiskHide will use this list to block apps from identifying the root status on your device.

1. Open Magisk and tap on the Settings (gear icon) on the top right-hand side.
2. Scroll down to “Configure DenyList,” and tap on it.
3. Tap the three vertical dot menu on the top right-hand side and select “Show system apps.”
4. From the list of apps, find Google Play Services, extend the dialog, and turn on the toggle for “com.google.android.gms” and “com.google.android.gms.unstable.”
5. Now, go back to the list, find Google Play Store, and turn on the toggle for “com.android.vending.”

Note: Go to your phone’s settings, force stop, and clear data for both Google Play Store and Play Services after configuring the DenyList.

3) Spoof the Bootloader Status (If TEE Broken)

Since Play Integrity also relies on the bootloader status to check device integrity, it is important to spoof that too.

1. Check whether your Trusted Execution Environment is broken.
   • To do so, get Momo, and check your TEE status.
2. If TEE is broken for your device, you’ll need to flash the LSPosed module.
3. From Xposed settings, enable the BootloaderSpoofer module.
4. If you need to hide root status from a certain app, select those here.

4) Hide Zygisk & Flash Play Integrity Fix Modules

To hide the remaining root traces from your device, flash the Shamiko module (Magisk), or Zygisk Assistant, if you’re on KernelSU.

1. Download the Play Integrity Fix module from chiteroman’s repository.
2. Get the TrickyStore module from aviraxp’s repository.
3. Flash both of these modules via Magisk.

5) Push a Working Keybox File via MT Manager

It is important to update the keybox files periodically since they’re patched sooner or later. These will be the keys that’ll be used to spoof the integrity tokens. You can find these tokens via online forums on XDA, Reddit, and Telegram.

1. Open MT Manager and copy your keybox file.
2. Go to <em>/data/adb/tricky_store/</em> and paste the file there.
3. Long tap on the keybox file, and go to properties.
   
4. In front of the “Owner,” you’ll see root. Tap on Modify.
5. Tap on Group, and select “root – 0.”
6. Head back to the properties and in front of Permissions, tap on Modify.
7. Select “Other” under Read and deselect “Group” under Write.
8. Tap “OK.” Note: When an app makes a request to the Play Integrity API, it returns an integrity token that is signed using a private key. For the bypass, we will need custom, working keyboxes to create tokens that bypass these checks and spoof the app into believing it is running on an unmodified, non-rooted environment.
9. Once everything is set up, reboot your device, get the Play Integrity API Checker app, and check your device’s integrity status.

The post How to Pass Strong Device & Play Integrity on Any Android? appeared first on Appuals.