Database Develop

[GUIDE] Redmi 6 Pro Root Guide

Disclaimer
Code:
#include <std/disclaimer.h> /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about rooting your device * before doing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you. */
Downloads
Instructions
Unlock your bootloader if you haven't already. Detailed steps can be found here.
Download the ADB and fastboot tools, TWRP Recovery IMG file and Magisk zip from the link above.
Extract the ADB zip into a folder and copy the recovery file into the same folder as well.
Copy the Magisk zip file into your phone's internal storage.
Rename the recovery file to recovery.
In the ADB folder and click on the MFA32 to open a command prompt window.
Connect your phone to your PC and go to the Developer Options previously enabled. Find the USB Debugging option and enable it.
Now hold the Volume + Power Down buttons that will allow the phone to boot into Fastboot mode.
In the fastboot mode, type: fastboot devices.
If your device is detected, great. If not, check your connections, USB Debugging or see if proper device drivers are installed or not.
Next, type: fastboot flash recovery recovery.img. This will flash the recovery in a few seconds.
Next, type: fastboot reboot recovery. As a result, you are welcomed by the recovery screen.
Here, click on Install. Find the previously downloaded Magisk zip and select it to flash. This will flash the required binaries.
Reboot.
Open Play Store and install the Magisk Manager. This will allow you to take proper advantage of your root by using multiple modules with many features.
Enjoy!
Full Guide can be found here - http://xboard.in/redmi-6-pro-recovery-root/.

twrp recovery not reading internal storage.
Hi,
I have a Redmi 6 Pro Indian version with unlocked Boot-loader, MIUI Global 10.2 stable. Flashed twrp recovery (Sakura) successfully but booting into the recovery mode I find it cann't read internal memory (showing 0 MB) and I can't flash necessary files through it for rooting my device.
On rooting into twrp recovery mode, first asks for password for un-encription and when I provide device unlock password, after sometime, it shows password failed.
On tapping 'cancel' option, goes to home of twrp with no option to flash from internal storage since it is 0MB.
Fastboot getvar anti command shows nothing [ anti: (blank)]. Fastboot getvar all shows Rollback ver 2.
Please help.

@Aloke17 Your data are encrypted. You have to do format data. Notice that your internal memory will be erased. Make a backup before.

mar.ur said:
@Aloke17 Your data are encrypted. You have to do format data. Notice that your internal memory will be erased. Make a backup before.
Click to expand...
Click to collapse
It did not work. Have already done that with same result. Can you tell me if I can flash from external storage like otg pendrive etc.?

Aloke17 said:
It did not work. Have already done that with same result. Can you tell me if I can flash from external storage like otg pendrive etc.?
Click to expand...
Click to collapse
I think you did a wipe data, not format. Look at the picture below

mar.ur said:
I think you did a wipe data, not format. Look at the picture below
Click to expand...
Click to collapse
I know difference. Formatted data, not wiped. got same result.

Aloke17 said:
I know difference. Formatted data, not wiped. got same result.
Click to expand...
Click to collapse
Restart again to twrp after format

This is what I did (make sure the TWRP.img and lazy flasher zip (attached) are in the same directory as the adb folder):
1. Put phone to fastboot mode.
2. Run ADB command fastboot boot twrp.img (the twrp image downloaded). Phone will reboot into TWRP. It will ask for password to decrypt, just hit back and ignore it for now.
3. Go to Wipe, Format Data. Swipe to Factory Reset. Advanced Wipe: Dalvik/ ART Cache, Cache, System, Internal Storage.
4. Go to Mount and mount System.
5. Run ADB command adb push twrp.img /sdcard
6. Go to Install, Install Image, select the TWRP.img file that you just pushed and flash it as recovery but don't reboot yet.
7. Run ADB command adb push lazyflasher-no-verity-opt-encrypt.zip /sdcard
8. Go to Install, Install Zip, select the zip file that you just pushed.
9. Go to Reboot. Power Off.
10. Boot the Device into TWRP Recovery (press volume up + power button).
Hope this helps a noob like me who wasn't able to flash TWRP due to strange errors.
PS: Bootloader was unlocked and device was running MIUI 10.2.2 Stable (Chinese ROM). I switched to Revenge OS (from XDA) based on Android Pie after this.

Can anyone please tell me how to get rid of SAKURA anti rollback. I'm currently on miui rom global beta 9.6.27..????
I waana flash xiaomi.eu rom on my phone.
I bricked my phone while flashing EU rom direct through twrp.

I followed this guide and it worked. The good thing about this guide is you can mess up and then get the mobile back to working state. I copied from a blog but can not post the link as i have fewer than 10 posts.
The contents of the blog in case if its deleted
1. unlock bootloader.
1.1 To unlock bootloader linking your mobile number to the device is mandatory to unlock bootloader. Read my rant[1] at the end of this post during the flashing as it takes some time. For now move to step 2 after unlocking the bootloader
2. check if the bootloader is unlocked by running the command "fastboot oem device-info"
3. flash the system image.
3.1 Download the image from the mi.com site sakura_india_global_images_V10.3.2.0.PDMMIXM_20190527.0000.00_9.0_global_0aaaa35167.tgz # md5sum 0aaaa35167e8edd299f0dd9418f04c62
3.2 untar
3.3 cd sakura_india_global_images_V10.3.2.0.PDMMIXM_20190527.0000.00_9.0_global/
# poweroff mobile, press volume down + poweron to go to fastboot mode
3.4 ./flash_all.sh
4 twrp flashing using boot and not flash because flashing to recovery parition is successfull but the recovery boot does not launch twrp so use the temporary method(flashboot boot)
4.1 fastboot boot twrp-3.2.3-0-sakura.img # md5sum 16759dcc425042d6a63b635f777a7690
4.2 twrp -> advanced settings ->sideload -> check both the cache to wipe -> swipe
4.3 adb sideload Magisk-v19.4.zip # md5sum 2a1def27607601ecaa780ee4b15210c2
4.4 flashing lazyflasher went in to loading forever, so skip that. it works without lazy flashing
5. reboot will boot to system and then download the MagiskManager apk from its website
5.1 enable the developer options for adb to transfer the MagiskManager apk to mobile
5.2 adb push MagiskManager-v7.3.4.apk /sdcard # md5sum 16e9ad8767665234dea7896a4137288e
5.3 on the mobile install the apk
6. to test it
6.1 adb shell
6.2 su
6.3 the above command should pop up requesting for permissions for root.
[1] Rant on Xiaomi's lies on embracing developer culture
TLDR: Xiaomi don't lie about embracing the hacker ethic. Accept you are evil with some lame excuse that is much more respectable.
It is very evil of Xiaomi to make the user provide their mobile number(thats right, you must provide your **working** sim card number) to unlock the bootloader. They will not unlock if your sim is not active, you must enable internet on your sim, link the sim number to mi account and only then they will unlock the bootloader. If you just use wifi it is not supported and yet they lie on their faq that the need sim for data usage.
Here is the faq they do not say about the sim card requirement . I have archived it in case after reading this Xiaomi might change this faq
The Following is the Q&A of faq
> Isn't locking bootloader against Mi's 'geek' spirit?
> Locking bootloader is aimed to provide a better user experience, which we've been trying to do the whole time. In the meantime, we've provided an unlocking tool for senior users who know their ways around flashing and tweaking their devices.
> The unlocking procedure will need Internet access to get the unlocking password. Also, the Mi Account logged in on the Mi phone and the unlocking tool needs to be the same. Otherwise, the unlocking request will be denied. This will ensure that ill-intentioned people will not get access to your personal data.
Atleast the moto company wanted just the device id to unlock bootloader.
I was rooting for Xiaomi a long back when i saw their faq where the question was "Can i root my mi mobile " and the answer was something along the lines of "Of coures you can, what do you think of us . we embrace hacker ethic. Now i can not find a link to this faq. Is someone find this please comment the link, i will add here.
Hope this guide helps some one.

grv29a said:
Can anyone please tell me how to get rid of SAKURA anti rollback. I'm currently on miui rom global beta 9.6.27..????
I waana flash xiaomi.eu rom on my phone.
I bricked my phone while flashing EU rom direct through twrp.
Click to expand...
Click to collapse
Just try to unlock bootloader as i did.
After flashing, is there any 'unlock' under Mi Logo? If no, need to unlock again.

[GUIDE] All about unlocking bootloader, TWRP and rooting Redmi Note 8/8T

Code:
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
A guide to unlock bootloader, flash a custom recovery and root your Redmi Note 8/8T device :
1. UNLOCKING BOOTLOADER :
Backup your data first. Unlocking will erase your data.
- Enable Developer Options in your phone by tapping the "MIUI Version" 7 times in About Phone.
- Go to Settings > Additional Settings > Developer Options.
- Enable OEM Unlocking, USB Debugging and USB Debugging (Security Settings) .
- Also add account in Mi Unlock Status (Can be found in Developer Options).
- Install the required ADB and Fastboot drivers in your PC from here.
- Download Mi Unlock to PC from here, and sign in with your Mi Account.
- Shut down your phone manually, and hold volume down key and power button to enter Fastboot mode.
- Connect your phone to PC using USB cable and click "Unlock" in Mi Unlock Tool.
- You will be given a specific time (168 hours usually).
- Wait for the given time. Make sure to use your phone and don't log out of your mi account from the phone or reset your device.
- Once waiting time is over, redo Unlock process.
- Your phone will be unlocked successfully.
2. FLASHING TWRP :
- Install the required ADB and Fastboot drivers in your PC if not already in step 1. from here.
- Download TWRP from here.
- Put that TWRP in the ADB and Fastboot installed folder (mostly C:\Program Files (x86)\Minimal ADB and Fastboot).
- Rename that recovery(TWRP file) to "recovery" for convenience (optional).
- Click on Start Menu, type cmd
- Right click and select Run as administrator
- Then type:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
- Now Connect your phone to PC With USB Debugging on (keep phone on).
- Type:
Code:
adb devices
and accept the pop up on phone's screen.
- Now reboot your phone to Fastboot mode either manually by shutting down phone and then holding volume down key and power button or by:
Code:
adb reboot bootloader
- Once in Fastboot mode type:
Code:
fastboot devices
- Your device ID will be visible on Screen.
- Then type(hit ENTER after each line):
Code:
fastboot flash recovery recovery.img
fastboot boot recovery.img
- Now your phone will boot into TWRP.
OPTIONAL STEPS (Not Recommended): Encryption is always recommended for better security. However if you don't want encryption in your device, follow these steps. Again, not recommended.
- In TWRP go to Wipe and select Format Data(don't go to advanced). Type yes and format data. [This process will format all your data so make sure your data is backed up]
- Go back to TWRP home and Reboot > Recovery.(Don't reboot system or else you will have to repeat whole process again).
- Done
3. ROOTING :
- Download Magisk zip to PC from here.
- Download Universal DM-Verity and ForceEncrypt disabler from here. (Only required if you followed optional steps.)
- When in TWRP transfer the file(s) to phone and go to Install.
- Here select Magisk zip file and swipe to flash.
- Then select Universal DM-Verity and ForceEncrypt disabler zip and swipe to flash(Make sure to flash this at last or else phone won't boot). (Only required if you followed optional steps.)
- Reboot system.
- Done. Debloat. Enjoy
Links
1. Minimal ADB and Fastboot
2. MI Unlock Tool
3. TWRP
4. Magisk
5. Universal DM-Verity and ForceEncrypt Disabler (OPTIONAL)
If this helped you then hit the Thanks Button. Good Luck.

Thanks for guide. Anyway, latest versions of Windows 10 don't have "Open command prompt here" option. Instead, they have PowerShell. I don't know how PowerShell will react with ADB, so, for these Windows 10 is better to:
Click on Start Menu, type cmd
Right click with mouse and choose "Run as administrator"
Type these commands (hit ENTER after each line):
cd\
cd "program files (x86)
cd "minimal adb and fastboot"
Now the user is on right folder.
--------------------------------
A question: I'm on stock ROM and have a Google Apps account on my phone, and I'm currently using stock Second Space feature to handle it. As encryption is mandatory to use a Google Apps account, I can't use "disable encryption". Or will Second Space be encrypted even if "main account" isn't? There are any problems to use Magisk with encrypted phone?

romulocarlos said:
Thanks for guide. Anyway, latest versions of Windows 10 don't have "Open command prompt here" option. Instead, they have PowerShell. I don't know how PowerShell will react with ADB, so, for these Windows 10 is better to:
Click on Start Menu, type cmd
Right click with mouse and choose "Run as administrator"
Type these commands (hit ENTER after each line):
cd\
cd "program files (x86)
cd "minimal adb and fastboot"
Now the user is on right folder.
--------------------------------
A question: I'm on stock ROM and have a Google Apps account on my phone, and I'm currently using stock Second Space feature to handle it. As encryption is mandatory to use a Google Apps account, I can't use "disable encryption". Or will Second Space be encrypted even if "main account" isn't? There are any problems to use Magisk with encrypted phone?
Click to expand...
Click to collapse
totally forgot about the powershell thing . Thanks to you I updated my post.
What do you mean by Google Apps account. Do you mean google account??. I'm using a decrypted phone right now and google apps work just fine with decryption too.
There aren't any problems to use Magisk with encrypted phone(I used it myself for a good week or so before decrypting).
Unfortunately as of now I don't have the answer to your second space question. Will let you know once I get it myself.

the_weird_aquarian said:
totally forgot about the powershell thing . Thanks to you I updated my post.
What do you mean by Google Apps account. Do you mean google account??. I'm using a decrypted phone right now and google apps work just fine with decryption too.
There aren't any problems to use Magisk with encrypted phone(I used it myself for a good week or so before decrypting).
Unfortunately as of now I don't have the answer to your second space question. Will let you know once I get it myself.
Click to expand...
Click to collapse
You must update the command to change folder on cmd. Put the path in quotes, or else the users will receive an error!
Code:
cd "C:\Program Files (x86)\Minimal ADB and Fastboot"
About Google Apps, is also called Google for Work, or Work Profile. Is MANDATORY to have the phone encrypted, or the account won't sync.
Thank you for feedback!

romulocarlos said:
You must update the command to change folder on cmd. Put the path in quotes, or else the users will receive an error!
Code:
cd "C:\Program Files (x86)\Minimal ADB and Fastboot"
About Google Apps, is also called Google for Work, or Work Profile. Is MANDATORY to have the phone encrypted, or the account won't sync.
Thank you for feedback!
Click to expand...
Click to collapse
the command works fine without quotes too man, checked it myself. both ADB and Fastboot commands work fine.
I'll check about Google for work issue. :good:

the_weird_aquarian said:
the command works fine without quotes too man, checked it myself. both ADB and Fastboot commands work fine.
I'll check about Google for work issue. :good:
Click to expand...
Click to collapse
You're right. Tested right now and worked. Maybe newer Win10 versions are "smarter" than older... who knows...
Well, about the second space, thanks, but you don't need to check with an Google Apps account.
If your phone is decrypted, just open Second Space, configuring it for first time use as you like. Then, on Second Space, go Settings -> Password and security -> privacy. Check if encryption is active.
Thanks again!

Thank you for this awesome tutorial.. now i m in "waiting mode" for unlocking bootloader ?
Just one dummy question for me sir .. can i root my device while i am using stock rom (miui 11 global) ? Or i have to install custom rom ? Thank you ?

Mozar3lla said:
Thank you for this awesome tutorial.. now i m in "waiting mode" for unlocking bootloader
Just one dummy question for me sir .. can i root my device while i am using stock rom (miui 11 global) ? Or i have to install custom rom ? Thank you
Click to expand...
Click to collapse
Yes you can root on stock rom. Rooting is not rom specific. You can root on any rom.
Hope it helps.

@the_weird_aquarian thanks for the tutorial mate, do i have to flash dm verity everytime i flash magisk????
and also I found this tutorial and software for flashing twrp, is it ok to use this software too?
https://github.com/XiaomiWiki/XiaomiWiki.github.io/blob/master/wiki/Flash_TWRP_and_custom_ROMs.md

shayanb2004 said:
@the_weird_aquarian thanks for the tutorial mate, do i have to flash dm verity everytime i flash magisk????
and also I found this tutorial and software for flashing twrp, is it ok to use this software too?
https://github.com/XiaomiWiki/XiaomiWiki.github.io/blob/master/wiki/Flash_TWRP_and_custom_ROMs.md
Click to expand...
Click to collapse
dm-verity is just required to stop the stock mi recovery from coming back. Hence it's just for MIUI based roms. However disable forceencrypt helps you get rid of force encryption of miui or other custom roms(so that you can access internal storage from recovery too if you are flashing something). The zip provided has both features in one file. Just rename the file to whatever you want to disable(see instructions here).
Regarding that tool on github, I have never used it personally as I like doing each step myself so if something goes wrong I know the last working step and from there I can figure out what went wrong. Using the tool might or might not work for you. Use at your own risk.

the_weird_aquarian said:
dm-verity is just required to stop the stock mi recovery from coming back. Hence it's just for MIUI based roms. However disable forceencrypt helps you get rid of force encryption of miui or other custom roms(so that you can access internal storage from recovery too if you are flashing something). The zip provided has both features in one file. Just rename the file to whatever you want to disable(see instructions here).
Regarding that tool on github, I have never used it personally as I like doing each step myself so if something goes wrong I know the last working step and from there I can figure out what went wrong. Using the tool might or might not work for you. Use at your own risk.
Click to expand...
Click to collapse
Thanks for the info mate
damn I have to wait a whole week to unlock my bootlaoder

shayanb2004 said:
Thanks for the info mate
damn I have to wait a whole week to unlock my bootlaoder
Click to expand...
Click to collapse
Yeah you gotta wait for a week. Weird Xiaomi policy. Can't help you with that though.

the_weird_aquarian said:
Yeah you gotta wait for a week. Weird Xiaomi policy. Can't help you with that though.
Click to expand...
Click to collapse
yea too bad... I cant use it for a week cuz all of my data is gonna get wiped again
I need to transfer all my data and apps from my old phone with migrate
so I will wait

shayanb2004 said:
yea too bad... I cant use it for a week cuz all of my data is gonna get wiped again
I need to transfer all my data and apps from my old phone with migrate
so I will wait
Click to expand...
Click to collapse
Make sure to atleast keep your phone turned on.

I will try it to root my device to get rid off the annoying ads. But my ordered cell phone does not come yet and I still patient to wait it.
Question :
1. Can I use the Mi Mover application to migrate data from an old cellphone (Redmi Note 5) to Redmi Note 8?
2. Whether migrating data (via Mi Mover) before root or do data migration after root ? Because my old RN5 already rooted, have it TWRP and Magisk too.

AMJ_Vario said:
I will try it to root my device to get rid off the annoying ads. But my ordered cell phone does not come yet and I still patient to wait it.
Question :
1. Can I use the Mi Mover application to migrate data from an old cellphone (Redmi Note 5) to Redmi Note 8?
2. Whether migrating data (via Mi Mover) before root or do data migration after root ? Because my old RN5 already rooted, have it TWRP and Magisk too.
Click to expand...
Click to collapse
I suggest you to move AFTER you root your new device, because to have root, you must unlock the bootloader. And when you unlock the bootloader, all data is lost.

romulocarlos said:
I suggest you to move AFTER you root your new device, because to have root, you must unlock the bootloader. And when you unlock the bootloader, all data is lost.
Click to expand...
Click to collapse
So its mean, first the device RN8 must do unlock the bootloader, then root it, next is migration data from old cellphone.
Is that the right way?
Is the migration data from old cellphone, will included the third party application from that old cellphone too? Is it will compatible on RN8?
Or just migration important data only (like email account + Mi account + contact + notes, etc) and the application 3rd party should be installed one by one on the RN8 exacly as RN5?
Sorry for asked to much becuse I dont want to make a mistake on the new devices.
Just guide me into the right way, please..
Thanks for the respond..:good:

AMJ_Vario said:
So its mean, first the device RN8 must do unlock the bootloader, then root it, next is migration data from old cellphone.
Is that the right way?
Is the migration data from old cellphone, will included the third party application from that old cellphone too? Is it will compatible on RN8?
Or just migration important data only (like email account + Mi account + contact + notes, etc) and the application 3rd party should be installed one by one on the RN8 exacly as RN5?
Sorry for asked to much becuse I dont want to make a mistake on the new devices.
Just guide me into the right way, please..
Thanks for the respond..:good:
Click to expand...
Click to collapse
In fact, I never used Mi Mover. As each device has its features, I prefer to install apps one by one. My data is on cloud, so for me is easyer.
I suggest you to do the transfer, only for tests, just after you receive your phone. These videos may help you also:
https://www.youtube.com/watch?v=shf-i8z86Ms and https://www.youtube.com/watch?v=ql-f88qllrE

@the_weird_aquarian mate have you tested orangefox recovery?
I'm hearing a lot about it, but donno anything :S
thinking if it is good instead of twrp or not?

shayanb2004 said:
@the_weird_aquarian mate have you tested orangefox recovery?
I'm hearing a lot about it, but donno anything :S
thinking if it is good instead of twrp or not?
Click to expand...
Click to collapse
yes so I have recently flashed orangefox about 2 weeks ago or something. I personally don't use anything other than official twrp, but I flashed orangefox because of it's miui OTA update feature. You can flash if you are planning on staying on stock rom with a decrypted device, as I have dirty flashed stock rom with my decrypted device but it always ends up in bootloop with official twrp. I have to format data everytime. Surprisingly Orangefox solves this issue. Also if you are a fan of theming then it provides a few custom fonts, colors and themes. However if your device is encrypted there's absolutely no reason to switch from official to any other recovery unless you want to customize the looks of your recovery.

[Android 11] Unofficial Lineage OS 18.1 for A21s

WARNING + DISCLAIMER:
By installing this custom ROM, you are VOIDING your warranty. Also, installation of this ROM WILL TRIP KNOX PERMANENTLY, and render apps such as Samsung Health, Private Folder, (+ any apps that depend on KNOX) useless until you get the phone's motherboard replaced at the Samsung C/S center.
Although this software is released in the hope that it will be useful, there is NO GUARANTEE that installing this will not cause any harm to your device. I TAKE NO RESPONSIBILITY FOR ANY BRICKED DEVICES, DAMAGED HARDWARE, OR ANY OTHER PROBLEMS CAUSED BY THIS ROM. You are using this ROM at YOUR OWN RISK. I strongly recommend that you DO NOT continue to the steps below UNLESS YOU FULLY UNDERSTAND WHAT YOU ARE DOING.
While this ROM has been tested with South Korean variant of Galaxy A21s (SM-A217N, CSC changed from LUC->SKC), please keep in mind that it hasn't been tested on any other variant (such as A217F, A217M.)
Click to expand...
Click to collapse
I would like to express special thanks to all the developers who contributed to the LineageOS port for Galaxy Tab S6 Lite + all the other developers who contributed to sepolicy & hardware parts for Samsung SLSI (Exynos) devices. Porting LineageOS to A21s would have been much harder without them.
Click to expand...
Click to collapse
After doing some research on this device, I was able to port LineageOS. The original sources are based on Galaxy Tab S6 Lite Wi-Fi version (gta4xlwifi), with some heavy modifications made for the A21s. In the process, I was able to fix some of the problems that were found on GSI (MTP, Fingerprint removal issues, NFC, Wi-Fi hotspot and direct), and added in some enhancements to the kernel.
Unfortunately, installation of this ROM requires Lineage Recovery, and since FBE (File-based-encryption) is enabled by default, it is incompatible with the TWRP.
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOT WORKING:
- Cell Broadcast (Emergency Messages) is broken in South Korea. The phone shows notifications, but the messages appear broken. Not sure about other countries. FIXED in South Korea as of 2021/9/2. However, its functionality in other countries hasn't been tested.
- Samsung's Proprietary Apps
- In order to use Wi-Fi Direct, you need to install a Wi-Fi direct sharing app from Google Play, as LineageOS doesn't have a sharing app installed by default
- Auto Brightness (The phone doesn't have the sensors for it anyway)
- On very rare occasions(probably once in more than 20 boots), the device's RIL (Phone calls, Data) might start up late when booting. If you see "No service" after booting, please wait for 30-60 seconds.
- VoLTE & VoWifi(not tested) - Unfortunately, this is located deep within Samsung's framework. AOSP-based roms for other Samsung devices don't support it either. Someday, this might be fixed.....
WORKING:
- Everything Else
GITHUB:
Device Source Tree: android_device_samsung_a21s, android_device_samsung_universal3830-common
Kernel: android_kernel_samsung_universal3830-common
Instructions for Installation:
1. BEFORE INSTALLING, make sure that you have UNLOCKED the bootloader of your device. This is a great guide that show how to do it. Also, the phone must be on the Stock ANDROID 11. If you are on binary U6, please use the recovery tar for U6.
2. Download the Lineage Recovery, ROM, Google Apps, ADB, and Odin. Unzip ADB and Odin to somewhere appropriate.
- ROM
- Recovery / Recovery(for U6)
- Google Apps
- ADB
- Odin
3. Enable USB Debugging on the device. Go to settings->About phone->Software information, and tap the build number several times until you see the notification that the devloper settings have been enabled. After enabling developer settings, go to settings->developer settings and check USB debugging.
4. Open Command Prompt, and type "cd <the path where you saved ADB to>".
4-1. As a test, type "adb devices". After typing it, the phone should show a screen that asks you to grant permissions for USB debugging. Select Yes.
5. On the phone, start holding down the Volume Up and Down keys. KEEP THE KEYS PRESSED UNTIL THE PHONE REBOOTS AFTER YOU TYPE THE COMMAND IN THE NEXT STEP.
6. While holding the keys down. type in the command "adb reboot recovery" on the command line.
11. After the phone reboots into download mode, press volume up to continue. Make sure that you see the "OEM LOCK: OFF" before continuing.
12. Open Odin. After opening Odin, click on AP, and select the Lineage Recovery Tar file that you downloaded in the step 2. After that, click on Start.
13. After a few seconds, if everything goes well, Odin should show "PASS" and the device should reboot into Lineage Recovery. After the device enters recovery, tap on Apply update->Apply from ADB. In some cases, touchscreen may be unresponsive or slow. If that happens, use Volume Keys to navigate and Power key to select. KEEP THE DEVICE CONNECTED TO THE COMPUTER.
14. After choosing Apply from ADB, type "adb sideload <the path where you saved the ROM file>" on the command prompt and press enter.
<CONTINUED ON THE NEXT POST>

15. If everything goes right, the device should show "script succeeded: result was [1.000000]" While ADB may show errors such as "Failed to read command" at 47%, this is no problem as long as the device says that the script succeeded.
16. Now it is time to install Google apps. On the phone, tap on Apply from ADB again, and on the computer, type "adb sideload <the path where you saved Google apps to>" and press enter.
17. After about 1-2 minutes, installation should be complete. Again, ADB might show "Failed to read command" errors. As long as the phone says that it was success, this is no problem. After installing, click on the "back" icon shown below.
18. Choose Wipe data/factory reset, and reboot the device.
19. If everything went well, the phone should reboot into LineageOS. Set up the device and Enjoy!

ADDITIONAL TIP: HOW TO ROOT THE PHONE ON LINEAGE 18
On Lineage 18, I patched the kernel so that it would have no problem with the official Magisk app.
Therefore, you DON'T need to use a version that has been modified for A21s.
If you want to have root, you can get the Official Magisk App.
1. Download & Install Magisk from the official source.
2. Select Install. When it asks you to select the boot image, choose the boot image from the Lineage OS ROM file that you downloaded from the step above. After patching the boot image, move & rename it to something you can type easily (ex. /sdcard/rooting.img)
3. Enable developer settings (Settings->About phone->Tap on build number)
4. Go to developer settings and enable USB debugging & root permissions for usb debugging.
5. Connect the phone to the PC.
6. Open the command prompt, and type "cd <the folder where you installed adb>. After that, type "adb root". If the phone asks you for permissions for USB debugging, allow it.
7. After the adb shows "Restarting adbd as root", type "adb shell dd if=/sdcard/<the path to saved boot image>" of=/dev/block/by-name/boot". The output should be something like
" *** records in
*** records out
*** bytes (** M) copied, *** s, **M/s"
8. After seeing the output above, reboot the phone. After rebooting, it should be rooted.

Good news. Thank you very much

Then, my friends, write here how it works and thank you for your observations

Thanks for your work buddy.....
I got Magisk installed an easier way...
Download Magisk Canary .apk
Change .apk to .zip then install the same way as the Rom and Gapps, by ADB sideload.
Factory reset/Format data and reboot.
Done
All we need is a working TWRP.... I've got one working but it shows no files and won't mount anything..... e.g. system, data etc

Pharcanal40 said:
Thanks for your work buddy.....
I got Magisk installed an easier way...
Download Magisk Canary .apk
Change .apk to .zip then install the same way as the Rom and Gapps, by ADB sideload.
Factory reset/Format data and reboot.
Done
All we need is a working TWRP.... I've got one working but it shows no files and won't mount anything..... e.g. system, data etc
Click to expand...
Click to collapse
What is your device model ...is it SM A217F/DS android 11 U6? Pls reply..

Gxzllen said:
What is your device model ...is it SM A217F/DS android 11 U6? Pls reply..
Click to expand...
Click to collapse
A217F on U5

Pharcanal40 said:
A217F on U5
Click to expand...
Click to collapse
Can i download it on u6?i'm afraid my phone brick if i do it

Gxzllen said:
Can i download it on u6?i'm afraid my phone brick if i do it
Click to expand...
Click to collapse
If you're on U6, there's a chance that Odin might fail on vbmeta.
A possible solution is:
1. Download Magisk (version doesn't matter)
2. Download the U6 firmware that you're on
3. Using Magisk, patch the AP tar of U6 firmware
4. In the Lineage recovery tar file that you downloaded from above, replace the vbmeta.img with the one from Magisk-patched AP tar file
5. Proceed with the installation as written above
A more fail-safe method would be:
1. Root the phone using a patched Magisk app
2. unpack the recovery.img in the Lineage recovery tar file and copy it into your device's SD card
3. Enable USB debugging on the phone, and connect the phone to adb
4. Using command prompt, type
"cd <path to adb>"
"adb shell"
"su"
"dd if=/sdcard/<path to lineage recovery image> of=/dev/block/by-name/recovery"
"reboot recovery"
After typing these, your device will reboot into Lineage Recovery. After entering recovery, select apply update->apply from adb, and proceed with the installatiom above from Step 14.

grccorps said:
If you're on U6, there's a chance that Odin might fail on vbmeta.
A possible solution is:
1. Download Magisk (version doesn't matter)
2. Download the U6 firmware that you're on
3. Using Magisk, patch the AP tar of U6 firmware
4. In the Lineage recovery tar file that you downloaded from above, replace the vbmeta.img with the one from Magisk-patched AP tar file
5. Proceed with the installation as written above
A more fail-safe method would be:
1. Root the phone using a patched Magisk app
2. unpack the recovery.img in the Lineage recovery tar file and copy it into your device's SD card
3. Enable USB debugging on the phone, and connect the phone to adb
4. Using command prompt, type
"cd <path to adb>"
"adb shell"
"su"
"dd if=/sdcard/<path to lineage recovery image> of=/dev/block/by-name/recovery"
"reboot recovery"
After typing these, your device will reboot into Lineage Recovery. After entering recovery, select apply update->apply from adb, and proceed with the installatiom above from Step 14.
Click to expand...
Click to collapse
nice thankyou bro

Or you can extract just the boot.img from the AP.tar. Patch it in Magisk then repack in the AP and flash with Odin

Pharcanal40 said:
Or you can extract just the boot.img from the AP.tar. Patch it in Magisk then repack in the AP and flash with Odin
Click to expand...
Click to collapse
Ohh okay its easy this way

Can I use adb fastboot instead of Odin?

Successfully Flashed! Everything work fine.
Model- A217f /DS
U6 binary ,Android 11 latest.

NuzzaimStark said:
Successfully Flashed! Everything work fine.
Model- A217f /DS
U6 binary ,Android 11 latest.
Note: Encountered some problems when I flash (vbmeta) ie, its because of its only for u5.
Odin showed failed at last ,
Phone was unable to boot but
By using hijacking software , bootloader was again running . but when auto reboot lineage recovery was automatically loaded, and tryed your above steps and everything working fine,
Note: pubg is very very better in this ROM.
Close range is also better.
Thankyou grccorps .
Click to expand...
Click to collapse
Thank you for your review. It's such a great news that it's working on U6.
Yes, PUBG is a hell of a game, Krafton has done such a great job with it The kernel has newer mali graphics driver (R26P0 -> R31P0), maybe that could've done the trick (or it may just be due to LineageOS being much, much lighter than One UI)
How is the battery? While I wasn't able to find any abnormal battery drains (both in standby and stress conditions), I'm concered about how it would perform in other devices.

NuzzaimStark said:
Successfully Flashed! Everything work fine.
Model- A217f /DS
U6 binary ,Android 11 latest.
Note: Encountered some problems when I flash (vbmeta) ie, its because of its only for u5.
Odin showed failed at last ,
Phone was unable to boot but
By using hijacking software , bootloader was again running . but when auto reboot lineage recovery was automatically loaded, and tryed your above steps and everything working fine,
Note: pubg is very very better in this ROM.
Close range is also better.
Thankyou grccorps .
Click to expand...
Click to collapse
Can you be a little more specific? my phone U6 but idk how to flash recovery can or you give me email so i can exchange?

Phuc230204 said:
Can you be a little more specific? my phone U6 but idk how to flash recovery can or you give me email so i can exc(hange?
Click to expand...
Click to collapse
First look on A21s LineageOS 18.1

hi,so i get this message "only official released binaries are allowed''in download mode,after the vbmeta failed...
SM-A217F/DSN
and in frp hijacker i get ''check device connection or com ports''

Update:so i succeded to hijack my phone after the error but it wouldn't boot into recovery,and i got everytime a screen with a warning that my phone is not using samsung's official software,and when i press the power button to continue,like it shows,it boots automatically into android.
So what should i do?
And do i need root to do this?

How To Guide [GUIDE] Beginner's guide on how to root Redmi Note 10 Pro (sweet) without TWRP

I decided to make this guide since I didn't see a guide thread which explains how to root the phone.
DISCLAIMER: I am not responsible for ANY damage that occurs to the phone, you getting fired because the alarm app failed or the world getting nuked, etc...
Requirements:
-A unlocked bootloader (if you don't know how to unlock it, search "How to unlock bootloader Xiaomi"
-boot.img extracted from your phone's fastboot rom (MAKE SURE YOU DOWNLOADED THE EXACT SAME ROM THAT YOUR PHONE HAS (Check "About phone" in settings. Make sure that the version AND the code (RK(something)XM) match, if you have MIUI).
xiaomifirmwareupdater site contains unmodified MIUI roms for your device.
-If you have a custom rom, extract the rom's zip and get the boot.img from there.
-ADB and Fastboot drivers installed on phone and PC
-SDK Platform tools downloaded from official android website. Extract the downloaded zip to desktop and rename it to platform_tools
-A Computer
-Basic understanding of CMD, ADB and Fastboot commands.
-The phone
If you see an error, scroll down to the troubleshooting section.
Steps:
(on the pc)
-Copy the boot.img file to the phone's downloads folder
(in the phone)
-Download the magisk app from the official github site
-Install the app, then open it.
-In the app, select install on the magisk card
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-Select patch a file, then find and select boot.img.
-Tap "let's go".
(on the pc)
-Connect your phone to your PC and copy magisk_patched.img from the phone (should be in downloads folder) back to the pc.
-Rename the file to magisk.img, then move it to the platform_tools folder which contains fastboot.exe.
-Now reboot the phone and when the screen goes fully black, hold volume down button until you see "fastboot".
-Your phone should now be in fastboot mode. Connect the phone to the pc.
-Press win+r, then type cmd
-Type cd desktop
-Type cd platform_tools
-Type fastboot devices (if you see nothing, make sure you have adb and fastboot drivers, that the phone is connected and is in fastboot mode.)
-Type this carefully: fastboot flash boot magisk.img
-Done! Now reboot the phone by typing: fastboot reboot
-If you did everything correctly, the magisk app should say that it is installed.
TROUBLESHOOTING:
Q:Fastboot says it couldn't find "magisk.img" or CMD says fastboot doesn't exist
A: Make sure that cmd says that its in C:\Users\(name)\Desktop\platform_tools and that magisk.img is also in there.
Q: Phone is in bootloop
A: Hold volume down button until phone is in fastboot and flash stock boot.img with fastboot flash boot.img. (You will not have root access) If the phone is still somehow in a bootloop, execute the flash_all_except_storage.bat script by double clicking it (found in the sweet_(region)_images folder you extracted from the full fastboot rom .tgz file).

usernamenotrequired said:
I decided to make this guide since I didn't see a guide thread which explains how to root the phone.
DISCLAIMER: I am not responsible for ANY damage that occurs to the phone, you getting fired because the alarm app failed or the world getting nuked, etc...
Requirements:
-A unlocked bootloader
-boot.img extracted from your phone's fastboot rom (MAKE SURE YOU DOWNLOADED THE EXACT SAME ROM THAT YOUR PHONE HAS (Check "About phone" in settings. Make sure that the version AND the code (RK(something)XM) match, if you have MIUI).
xiaomifirmwareupdater site contains unmodified MIUI roms for your device.
-If you have a custom rom, extract the rom's zip and get the boot.img from there.
-ADB and Fastboot drivers installed on phone and PC
-SDK Platform tools downloaded from official android website. Extract the downloaded zip to desktop and rename it to platform_tools
-A Computer
-Basic understanding of CMD, ADB and Fastboot commands.
-The phone
If you see an error, scroll down to the troubleshooting section.
Steps:
(on the pc)
-Copy the boot.img file to the phone's downloads folder
(in the phone)
-Download the magisk app from the official github site
-Install the app, then open it.
-In the app, select install on the magisk card
View attachment 5474787
-Select patch a file, then find and select boot.img.
-Tap "let's go".
View attachment 5474793
(on the pc)
-Connect your phone to your PC and copy magisk_patched.img from the phone (should be in downloads folder) back to the pc.
-Rename the file to magisk.img, then move it to the platform_tools folder which contains fastboot.exe.
-Now reboot the phone and when the screen goes fully black, hold volume down button until you see "fastboot".
View attachment 5474801
-Your phone should now be in fastboot mode. Connect the phone to the pc.
-Press win+r, then type cmd
-Type cd desktop
-Type cd platform_tools
-Type fastboot devices (if you see nothing, make sure you have adb and fastboot drivers, that the phone is connected and is in fastboot mode.)
-Type this carefully: fastboot flash boot magisk.img
-Done! Now reboot the phone by typing: fastboot reboot
-If you did everything correctly, the magisk app should say that it is installed.
TROUBLESHOOTING:
Q:Fastboot says it couldn't find "magisk.img" or CMD says fastboot doesn't exist
A: Make sure that cmd says that its in C:\Users\(name)\Desktop\platform_tools and that magisk.img is also in there.
Qhone is in bootloop
A: Hold volume down button until phone is in fastboot and flash stock boot.img with fastboot flash boot.img. (You will not have root access) If the phone is still somehow in a bootloop, execute the flash_all_except_storage.bat script by double clicking it (found in the sweet_(region)_images folder you extracted from the full fastboot rom .tgz file).
Click to expand...
Click to collapse
Very good but easier with unlocked bootloader and flashing twrp via adb flash recovery "name of twrp file". Afterwards you can flash directly magisk (I prefer 23 canary debug apk) to root.

if i may add to the troubleshooting: if it says magisk.img isn't found, just type this (after confirming connection with fastboot devices command:
fastboot flash boot
then drag and drop the patched magisk file onto the cmd window/line where you typed the command above. worked for me.

Tanks you

For beginners, "assuming bootloader is unlocked if not click here" should be mentioned.

hello, I've been trying to login to my account since this morning. after half a day I was able to get in via facebook. problem is when i want to root my phone it shows error 1004. what did I do wrong?

Bastio001 said:
hello, I've been trying to login to my account since this morning. after half a day I was able to get in via facebook. problem is when i want to root my phone it shows error 1004. what did I do wrong?
Click to expand...
Click to collapse
I've searched around, and it seems to be caused by a VPN. If you use a VPN, turn it off and try again. If not, it could be that the Xiaomi unlocking API is down temporarily.

When I root my Redmi Note 10 Pro (sweet) by using twrp to flash magisk 25.2 and lazyflasher-no-verify-opt-encrypt.zip, I receive following message
.
Nevertheless, I reboot my phone which is effectively rooted.
I can then install Magisk manager.
Has someone an idea about the meaning of this error message ?
Thanks in advance.

cocopipou said:
When I root my Redmi Note 10 Pro (sweet) by using twrp to flash magisk 25.2 and lazyflasher-no-verify-opt-encrypt.zip, I receive following message
View attachment 5704507.
Nevertheless, I reboot my phone which is effectively rooted.
I can then install Magisk manager.
Has someone an idea about the meaning of this error message ?
Thanks in advance.
Click to expand...
Click to collapse
No need to flash lazy flasher since you already flashed Magisk. They both do the same which is to disable dm verity. Also, lazy flasher is an old zip intended for old devices so maybe that's why it failed.

BigChungus321 said:
No need to flash lazy flasher since you already flashed Magisk. They both do the same which is to disable dm verity. Also, lazy flasher is an old zip intended for old devices so maybe that's why it failed.
Click to expand...
Click to collapse
I thank You very much.

BigChungus321 said:
No need to flash lazy flasher since you already flashed Magisk. They both do the same which is to disable dm verity. Also, lazy flasher is an old zip intended for old devices so maybe that's why it failed.
Click to expand...
Click to collapse
then what is the solution bro...still i cant install some custom roms showing error 1...please help me.

cocopipou said:
When I root my Redmi Note 10 Pro (sweet) by using twrp to flash magisk 25.2 and lazyflasher-no-verify-opt-encrypt.zip, I receive following message
View attachment 5704507.
Nevertheless, I reboot my phone which is effectively rooted.
I can then install Magisk manager.
Has someone an idea about the meaning of this error message ?
Thanks in advance.
Click to expand...
Click to collapse
bro am facing this erros 1. will u pls help me.

THis is the stupidest guide for beginners, this article assumes you have unlocked your phone in the first place. All the important steps are just skipped and is stuffed in the requirements. And just shows simple screenshots that even a child would know where to click.
No external links to find the sources.

While unlocking the bootloader I'm having the issue linked below, thanks in advance for all and any responses. https://forum.xda-developers.com/t/mi-unlock-country-code-broken.4572339/

r4nchy said:
THis is the stupidest guide for beginners, this article assumes you have unlocked your phone in the first place. All the important steps are just skipped and is stuffed in the requirements. And just shows simple screenshots that even a child would know where to click.
No external links to find the sources.
Click to expand...
Click to collapse
AGREE 100%!!!

How To Guide (Guide) Install TWRP + Root + Install Magisk + Bypass Safetynet

Please note, the TWRP image used IS NOT the official TWRP image.
I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me.
Warning
As stated by @beatbreakee , do not flash anything on a T-Mobile related device.
Please read beatbreakee's comment regarding this.
Warning
This has only been tested on Android 13. This guide may not work for other Android versions.
Prerequisites
Unlocked Bootloader
Magisk 25.2 Installation ZIP (see attached files)
TWRP Image (download from GDrive)
ADB and Fastboot tools are installed on your machine. Please see this guide
Android 13
Spoiler: Step 1 - Unlocking Bootloader
Step 1 - Unlocking Bootloader:
1.A - Enable OEM Unlocking:
1. Open Settings Application -> About device -> Version -> Tap on Build Number 7 times
2. Open Settings Application -> Additional Settings -> Developer Options
3. Enable OEM Unlocking
4. Enable USB Debugging
1.B - Entering Bootloader
The bootloader must be unlocked in order to flash the recovery.
Ensure the device is connected to the computer via ADB by entering the following command
Code:
adb devices
The output should be something similar to this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(note the device name on the left will not be the same)
Reboot into the bootloader by entering the following command:
Code:
adb reboot bootloader
1.C - Unlock
Once entered, enter the following command:
Code:
fastboot flashing unlock
WARNING: THIS WILL WIPE ALL DATA ON THE DEVICE
Use the volume keys to select unlocking, and then use the power button to confirm.
Once complete, enter the following command:
Code:
fastboot reboot
You will now have to go through the device setup.
Repeat steps 1.A and 1.B to enter back into the bootloader
Spoiler: Step 2 - Flashing TWRP
Step 2 - Flashing TWRP:
2.A - Entering Bootloader
Repeat steps 1.A and 1.B to re-enter the bootloader
2.B - Flashing TWRP:
Again, this IS NOT the official TWRP image. I am not responsible for any harm which this may cause to this device. That being said, it appears to be functional.
The image used is from a leak found on this XDA post
This is not a bootable image. You must flash. fastboot boot img will not work
Enter the following commands to flash the TWRP image:
Code:
fastboot flash recovery_a twrp.img
Code:
fastboot flash recovery_b twrp.img
Code:
fastboot reboot recovery
You should notice you are in TWRP.
You may need to change the language to English.
2.C - Changing TWRP Language:
1. Tap on the button on the Second column, Third Row
2. Tap on the World icon
3. Select your language
4. Tap on the button on the bottom right corner of your display.
2.D - Booting into your phone
1. Select Reboot
2. Select System
You should now have successfully booted in the system with TWRP installed as your recovery
Spoiler: Step 3 - Flashing Magisk
Step 3 - Flashing Magisk:
3.A Preparing the Device:
1. Move the Magisk-v25-2.zip to your device
2. Reboot into your recovery / TWRP
This can be done by entering the following ADB command:
Code:
adb reboot recovery
3.B - Flashing Magisk:
1. Tap Install
2. Select the Magisk-v25-2.zip
3. Swipe to flash (this may take some time)
4. Tap Reboot
5. Tap System
You should now enter the device
3.C - Installing Magisk APK
Install the Magisk APK, click here to download the APK.
Install the APK, and you should have root!
Spoiler: Fixing Data Backup [Optional]
If you encounter a createTarFork() exited with error 255, do the following:
1. Reboot into TWRP
2. Select File Manager
3. Navigate to /data
4. Copy /data/fonts into /sdcard/
5. Copy /data/nandswap into /sdcard/
6. Delete /data/fonts
7. Delete /data/nandswap
The error should now be resolved
The deleted files should not cause any issues. If any issues do occur, then promptly restore them using the backups made to /sdcard/.
Spoiler: Bypassing Safetynet [Optional]
Step - Bypassing Safetynet:
This is optional; however, highly recommend
Note, due to the nature of Safetynet, this can change at anytime and may begin failing in the future.
A - Repackaging Magisk
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Hide The Magisk App"
4. Enter New Application Name
5. Click OK and wait
6. Uninstall original Magisk APK if it has persisted
B - Enable Zygisk & Deny List
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Enable "Zygisk"
4. Enable "Enforce Deny List"
C - Configure Deny List
it is recommended to add any application you would like to hide from Magisk here
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Configure DenyList"
4. Tap the 3 dots in the top right and select "Show System Apps"
5. Select the following applications:
~ Android System
~ Google Play Store
~ Google Play Services
~ Google Services Framework
D - Delete App Data
1. Launch Settings Application
2. Select Apps
3. Select App Management
4. Clear data for the following apps:
~ Google Play Store
~ Google Play Services
~ Google Services Framework
5. Reboot the device
E - Flash Universal Safetynet Fix
1. Download the Universal Safetynet Fix
2. Launch Magisk
3. Select Modules
4. Select "Install From Storage"
5. Select Universal Safetynet Fix
6. Wait for Flashing to complete
7. Reboot
F - Test Safetynet
1. Install YASNAC
2. Grant Super User rights
3. Select "Run Safetynet Attestation"
If both checks pass, you successfully have passed Safetynet!

PlasmaTornado said:
Please note, the TWRP image used IS NOT the official TWRP image.
I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me.
Prerequisites
Unlocked Bootloader
Magisk 25.2 Installation ZIP (see attached files)
TWRP Image (download from GDrive)
ADB and Fastboot tools are installed on your machine. Please see this guide
Step 1 - Unlocking Bootloader:
1.A - Enable OEM Unlocking:
1. Open Settings -> About -> Tap on Build Number 7 times
2. Open Developer Settings
3. Enable OEM Unlocking
4. Enable Android Debugging Bridge (ADB)
1.B - Entering Bootloader
The bootloader must be unlocked in order to flash the recovery.
Ensure the device is connected to the computer via ADB by entering the following command
Code:
adb devices
The output should be something similar to this:
View attachment 5792895
(note the device name on the left will not be the same)
Reboot into the bootloader by entering the following command:
Code:
adb reboot bootloader
1.C - Unlock
Once entered, enter the following command:
Code:
fastboot oem unlock
WARNING: THIS WILL WIPE ALL DATA ON THE DEVICE
Then finally:
Code:
fastboot reboot
You will now have to go through the device setup.
Repeat steps 1.A and 1.B to enter back into the bootloader
Step 2 - Flashing TWRP Image:
2.A - Entering Bootloader
Repeat steps 1.A and 1.B to re-enter the bootloader
2.B - Flashing TWRP:
Again, this IS NOT the official TWRP image. I am not responsible for any harm which this may cause to this device. That being said, it appears to be functional.
The image used is from a leak found on this XDA post
! It is HIGHLY recommended that you boot into the twrp.img before flashing to ensure that TWRPworks . I did not, but I recommend you do. !
To test this, enter the following command:
Code:
fastboot boot twrp.img
Enter the following commands to flash the TWRP image:
Code:
fastboot flash recovery_a twrp.image
Code:
fastboot flash recovery_b twrp.image
Code:
fastboot reboot recovery
You should notice you are in TWRP.
You may need to change the language to English.
2.C - Changing TWRP Language:
1. Tap on the button on the Second column, Third Row
2. Tap on the World icon
3. Select your language
4. Tap on the button on the bottom right corner of your display.
2.D - Booting into your phone
1. Select Reboot
2. Select System
You should now have successfully booted in the system with TWRP installed as your recovery
Step 3 - Flashing Magisk:
3.A Preparing the Device:
1. Move the Magisk-v25-2.zip to your device
2. Reboot into your recovery / TWRP
This can be done by entering the following ADB command:
Code:
adb reboot recovery
3.B - Flashing Magisk:
1. Tap Install
2. Select the Magisk-v25-2.zip
3. Swipe to flash (this may take some time)
4. Tap Reboot
You should now enter the device
3.C - Installing Magisk APK
If for some reason the Magisk Installer did not install the Magisk APK, click here to download the APK.
Install the APK, and you should have root!
Click to expand...
Click to collapse
Good post but one problem...to unlock is " fastboot flashing unlock"

Canuck Knarf said:
Good post but one problem...to unlock is " fastboot flashing unlock"
Click to expand...
Click to collapse
Of course! Thank you, used to the old way of unlocking

I wonder about any major issues with this TWRP as of now. Updating ZIP OOS13 with flashing magisk direclty is working etc.?

kouzelnik3 said:
I wonder about any major issues with this TWRP as of now. Updating ZIP OOS13 with flashing magisk direclty is working etc.?
Click to expand...
Click to collapse
Following the method created by @dladz should still work perfectly fine!
There could still be issues with this TWRP as this is not an official image.
AFAIK Switching ROM is still untested, but decryption, backups and flashing are all confirmed working, which for me makes me feel significantly more comfortable

I won't switch ROMs as there aren't any, so this is ok. I was just asking if installing official OOS updates can be done via twrp now with flashing magisk right after for example.
But I glad decryption, backups and flashing zips working fine now. This is great news!

kouzelnik3 said:
I won't switch ROMs as there aren't any, so this is ok. I was just asking if installing official OOS updates can be done via twrp now with flashing magisk right after for example.
But I glad decryption, backups and flashing zips working fine now. This is great news!
Click to expand...
Click to collapse
This has yet to be tested but I have high hopes! If anyone could confirm in the near future it would be fantastic!

PlasmaTornado said:
This has yet to be tested but I have high hopes! If anyone could confirm in the near future it would be fantastic!
Click to expand...
Click to collapse
I will try factory wipe...flash flash from 2213...to 2215...might work

Canuck Knarf said:
I will try factory wipe...flash flash from 2213...to 2215...might work
Click to expand...
Click to collapse
Fantastic news. Let us know the results!

i wouldnt advise ANYONE with an original TMOBILE device, ANY attempt to flash ANY firmware from the official builds just yet. Tmobile embedded a VERY WELL HIDDEN check into the EFS partition that only appeared in builds after 11_A.14 ... This check forcefully activates a lock triggered by the CarrierDevicePolicy.xml in the efs system... and if the Region and model does not match the original build that it came with, all of your apps will be completely disabled and there is nothing accessible but the settings button. It also disables ADB/USB debugging completely, and deauthorizes your computer from the adb wireless keys too... then it removes the USB DEBUGGING toggle from settings, followed by a persistent message that your phone is "Violating Contract Policy... Please contact after sales for support" ... Tmobile cannot remove this warning... and even them sending an UNLOCK request to your phone for APPROVED will get ignored by your phone. You can hear ringing, but cannot accept calls... hear emails but not open them,.. and you dialer is in emergency calls only!...
At this point you will think panic is the only option, but instead just Pull your sim card, and use your buttons to force reboot and enter recovery .... Then do a Format Data ,,,, followed by a reboot, but do not put your sim back in... Until you go thru the whole setup wizard, enable usb debugging, and then flash a rollback package to a fw earlier than the one i listed above, your phone will INSTANTLY lock again any time you insert ANY sim card.
Im very sure that there is a system process that can be disabled which will at least block the lockout.... but i dont have that knowledge as to which process(es) are calling it! A logcat generated about 15 screens on my computer as soon as i plugged a sim in... so that was too much for me to sift thru. This is present on both the 10 Pro and 10 T so be warned.... If you are already not using your original T-MO firmware, but you also have been loading other regions with no problem, that does not matter.... I have found an exact reference to the ORIGINAL FW build and Model # that was loaded by TMO at the factory level, in several different TXT and XML files inside the EFS part. AND my 10T and 10 Pro BOTH have been fully bricked, then formatted and flashed thru an authorized MSM Account.... Doing an ERASE ENTIRE FILE SYSTEM, thru msm, did not get rid of this file, so i doubt a twrp level wipe will do it either... MAYBE an "unlock Critical" in Fastboot, followed by a "Fastboot wipe", "DM-verity disable", and "VB-Meta erasure" MIGHT take out this crazy security system, but i know this .... if you flash an original FW using TWRP, it has protections in it to keep IT (twrp) from being overwritten, so you might find yourself in bootloop territory if you region hop.... cuz the fw might notice the changes to the partitions... For now, until someone is brave enough to challenge the Android 12 kernel and remove these trapdoors, I would just be happy you have TWRP, and wait for the person who finds and slays the Tmobile Dragon hidden in our phones! But this is truly an android 12 function that was put in place for Carrier and Manufacturer benefit ONLY. Another strike against 1+

beatbreakee said:
i wouldnt advise ANYONE with an original TMOBILE device, ANY attempt to flash ANY firmware from the official builds just yet. Tmobile embedded a VERY WELL HIDDEN check into the EFS partition that only appeared in builds after 11_A.14 ... This check forcefully activates a lock triggered by the CarrierDevicePolicy.xml in the efs system... and if the Region and model does not match the original build that it came with, all of your apps will be completely disabled and there is nothing accessible but the settings button. It also disables ADB/USB debugging completely, and deauthorizes your computer from the adb wireless keys too... then it removes the USB DEBUGGING toggle from settings, followed by a persistent message that your phone is "Violating Contract Policy... Please contact after sales for support" ... Tmobile cannot remove this warning... and even them sending an UNLOCK request to your phone for APPROVED will get ignored by your phone. You can hear ringing, but cannot accept calls... hear emails but not open them,.. and you dialer is in emergency calls only!...
At this point you will think panic is the only option, but instead just Pull your sim card, and use your buttons to force reboot and enter recovery .... Then do a Format Data ,,,, followed by a reboot, but do not put your sim back in... Until you go thru the whole setup wizard, enable usb debugging, and then flash a rollback package to a fw earlier than the one i listed above, your phone will INSTANTLY lock again any time you insert ANY sim card.
Im very sure that there is a system process that can be disabled which will at least block the lockout.... but i dont have that knowledge as to which process(es) are calling it! A logcat generated about 15 screens on my computer as soon as i plugged a sim in... so that was too much for me to sift thru. This is present on both the 10 Pro and 10 T so be warned.... If you are already not using your original T-MO firmware, but you also have been loading other regions with no problem, that does not matter.... I have found an exact reference to the ORIGINAL FW build and Model # that was loaded by TMO at the factory level, in several different TXT and XML files inside the EFS part. So this is truly an android 12 function that was put in place for Carrier benefit ONLY. Another strike against 1+
Click to expand...
Click to collapse
Absolutely despicable and such an anti-consumer technique.
This stands against everything OnePlus was. It's sad to see OnePlus turn into such an anti-developer phone
A Carrier should never have this much power over a device. It is absurd

heres a google drive link to my account if anyone wants to see a video of what you will go thru if triggered!
feel free to share or re-upload the link/video to anywhere... ppl need to know this is happening thanks to Tmobile and Oneplus collaboration. I have not seen any reference to another carrier inside any of the device policy files, and my phone was restored to a NON TMO branded build of android 12 for the 2217 NA model, so it should NOT have even recognized the TMO policies cuz i even used a new sim card after the MSM Unbrick, and it still instantly locked in less than a second of plugging it in... heres the vid
https://drive.google.com/file/d/17H6YpGrUCe1Y7PoFji4gperdpTHNX5AI/view?usp=sharing

also everyone should know, that EVERY fw on the internet no matter whether it is labeled, 2213, or 2215... 2217, as well as 2413-2419 ALL have EVERY other model's manifest built in and all of the restrictions / bloatware that each region comes with, saved into the OFP extracted files.... so there really is nothing that expressly was bricking your phones by simply flashing a different labeled FW..... the brick came from the manifest reading the region identifiers that the manifests are labeled under.... it is a file that is again picked by some random hidden check inside the TMO EFS, and as soon as your phone tries to boot the newly flashed FW, the TMO Lock is what bricks your phone, to either a bootloop state, or if you continue to force a flash by using Fastboot , you will have a non responsive phone, thanks to this stupid security issue. If unresponsive, the only way out is MSM Tool... and i can help you locate your test points if your buttons dont work.
I cannot publicly post a picture nor a description of where the test points lie inside the 10T , because i already got a cease and desist letter from BBK and i dont know if they have said anything to the mods here about posting Undisclosed hardware access points.... but ive been a member here almost 10 years, and i aint risking a ban from a tattle tale company! There are test points on the 10 t though,.. just well hidden!
The 2nd pic is of the 2217 Unpacked OFP , yet the build prop shows a 2210-2211 base in one and a 2413-2415 base in the.... with NO 2217 in either prop,or manifest file, yet when my phone was flashed back from Brick status, THIS is the FW that was used, and my phone identifies as a 2217 NA now..... can oneplus be any more clear that they have completely turned against us, by straight SHOWING US that they are being super cryptic and sneaky in something as common as the BUILD.PROP files?!?

The weird thing happened to me. I was doing "fastboot boot twrp.img" and adb gave me an error "Too many links" and the device only shows a OP logo for a half second, then turned off and then again repetatively.
Even if I turned off the device by holding power button + volume up + volume down, then turned on, same behavior happened.
Well, my fastboot was accessible so I did "fastboot boot boot.img" which worked and system booted up. But what happened, what might been wrong?

kouzelnik3 said:
The weird thing happened to me. I was doing "fastboot boot twrp.img" and adb gave me an error "Too many links" and the device only shows a OP logo for a half second, then turned off and then again repetatively.
Even if I turned off the device by holding power button + volume up + volume down, then turned on, same behavior happened.
Well, my fastboot was accessible so I did "fastboot boot boot.img" which worked and system booted up. But what happened, what might been wrong?
Click to expand...
Click to collapse
It could been...cause you might of had to many things open containing the same file...plus you might want to try the command ( fastboot flash recovery_a )....then ( fastboot flash recovery_b )

Canuck Knarf said:
It could been...cause you might of had to many things open containing the same file...plus you might want to try the command ( fastboot flash recovery_a )....then ( fastboot flash recovery_b )
Click to expand...
Click to collapse
Oh. I had opened like two or three folders containing that file, yes. But this can cause it? Wow. And I wanted to try to boot it first instead of flashing it.

kouzelnik3 said:
Oh. I had opened like two or three folders containing that file, yes. But this can cause it? Wow. And I wanted to try to boot it first instead of flashing it.
Click to expand...
Click to collapse
Yeah i hear you but I'm not sure if this a bootable version or a just install version....I will try it on mine to see if i get the same as you

Don't use command "fastboot boot twrp.img"....your phone will keep rebooting to op logo...but fastboot still works

Canuck Knarf said:
Don't use command "fastboot boot twrp.img"....your phone will keep rebooting to op logo...but fastboot still works
Click to expand...
Click to collapse
Yeah, I realised that, this happened to me. Thanks to fastboot I was able to boot into stock boot image, so nothign really happened, but hey. So if I dont want to flash it but only try it, what willl be the command? Fastboot boot recovery twrp.img?

kouzelnik3 said:
Yeah, I realised that, this happened to me. Thanks to fastboot I was able to boot into stock boot image, so nothign really happened, but hey. So if I dont want to flash it but only try it, what willl be the command? Fastboot boot recovery twrp.img?
Click to expand...
Click to collapse
It appears the image is not bootable. As stated, this is the one thing I didn't try.
I have amended the guide. Thank you