Database Users

[RECOVERY][STABLE]Unoffical TWRP for Xiaomi Mi A3[laurel_sprout]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are 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 features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Whats Working?
Everything is working
Can change Slot A/Slot B on twrp
SDcard and OTG working
Decryption of Data working
Flashing of roms work pie and even Q roms work.
HOW TO UPDATE a ROM and Keep TWRP and ROOT:
Before all Disable all magisk modules for boths methods
- Put rom.zip, twrp installer.zip and magisk.zip on your internal storage or sdcard;
- Flash Rom;
- Flash TWRP Installer;
- Flash magisk(recommend to use Magisk v19.4);
- Reboot.
Download:
TWRP 3.3.1-2 Unofficial Installer by Nikesh Kataria
TWRP 3.3.1-2 Unofficial by Nikesh Kataria
Donations:
Credits:
Thanks to @mauronofrio for a great help to make a stable recovery
Thanks to @Typhus_ for hardcore testing
Thanks to @prakash78 for testing
Contributors
Nik001
Source Code: https://github.com/Nikesh001/android_device_xiaomi_laurel_sprout-twrp
Version Information
Status: Stable
Created 2019-10-21

Reserved

This man -> @Nik001 deserves a beer!!!
Thank you for delivering us a fully working TWRP for laurel_sprout!
Cheers!

Typhus_ said:
This man -> @Nik001 deserves a beer!!!
Thank you for delivering us a fully working TWRP for laurel_sprout!
Cheers!
Click to expand...
Click to collapse
Welcome and thank you for testing twrp.:fingers-crossed:

Thank u peru sir

A3 real modding let's start

Good Job @Nik001

Anyone tell how to flash twrp... proper commands
Please
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Is that tested anyone.

Stock fw 10.3.8 (global) not booting with this twrp - in 10.3.8 audio modules have strange dependence "saved_command_line" symbol from kernel. For loading this modules need patch kernel sources -
diff --git a/init/main.c b/init/main.c
index 6d1880f0b852..2106f54a7008 100644
--- a/init/main.c
+++ b/init/main.c
@@ -128,6 +128,7 @@ void (*__initdata late_time_init)(void);
char __initdata boot_command_line[COMMAND_LINE_SIZE];
/* Untouched saved command line (eg. for /proc) */
char *saved_command_line;
+EXPORT_SYMBOL_GPL(saved_command_line);
/* Command line for parameter parsing */
static char *static_command_line;
/* Command line for per-initcall parameter parsing */
Click to expand...
Click to collapse

Proper install method explained
Hello!
Please, @Nik001, update the OP with the install method that I'm going to describe next, ok?
It's just to avoid future complications (lost of Wi-Fi, sound, etc...) for "not that experienced users".
Your bootloader must be unlocked. If it's not, then follow step 1 of the instructions provided HERE.
Download TWRP zip file and copy it to your device (internal or external storage)
Download TWRP img file and and store it, on the folder where you have adb and fastboot files, on your PC
Open a cmd line and execute these commands (being on that folder, of course):
adb devices (to make sure your device is detected)
adb reboot bootloader (to reboot into fastboot mode)
fastboot getvar current-slot (to check what's your current active slot)
fastboot set_active b (if your active slot was a, if it was b then change it to a)
fastboot erase boot
fastboot flash boot twrp-3.3.1-2-unofficial-laurel_sprout.img
fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)​
When TWRP recovery boots, if you have a stock boot.img that matches the build on this "currently active" slot, flash it into boot partition. If you don't have, then just ignore this step...(it's not mandatory)
Install the TWRP zip (always install the latest build available)
Change slot to the one that was active on the beginning of these steps and reboot to Recovery (just to make sure that the slot, in fact, was changed)
Reboot to System
Why do I suggest this?
By doing this method (which seems more complicated but, trust me, it's how it should be done) we will flash TWRP img into the "inactive" slot, thus, not breaking anything on the "currently active" slot. When TWRP boots, it will patch both slots boot ramdisks. But the thing is, on the "currently active" slot (the one inactive on the beginning) it will patch the TWRP img but, on the "currently inactive" slot (the one that was active on the beginning), it will patch the stock boot.img, thus, no bug will happen that usually appears when a user accidentally flashes the wrong boot.img into boot partition.
On the other hand, if we have a stock boot.img, that matches the build on the "inactive" slot, we could flash it into boot partition before installing the zip that patches ramdisk. By doing this we will patch both stock boot.img present on both slots (instead of patching TWRP img and boot.img).
Cheers!

Sapper Morton said:
The method Typhus shared works 100% of the times; however I must say, I don't use it, just preference; as it follows, instead of flashing into the inactive slot, I flash the pre_patched boot image into the active slot, this of course will mostly like break network and other components on the ROM, if you mismatch image versions; however, if you flash the stock boot image (using install button, inside TWRP, tapping into 'images', select your stock boot.img) and then patch it using the TWRP Installer right after, you will be using the right image, so no problem will occur, and mostly important, no slot change is needed. Both methods works, choose what you prefer, just read it carefully and I repeat, always use the same boot image from your firmware, a lot of confusion comes to the fact, that when you uses TWRP.img or Magisk.img they aren't boot images, but they are; A/B partition scheme doesn't use some individual partitions anymore, as /recovery, thus is extremely important to patch your boot image, where the recovery, kernel and other components now lives.
Click to expand...
Click to collapse
So, in other words, your method is this (correct me if I'm wrong):
Download TWRP zip file and copy it to your device (internal or external storage)
Download TWRP img file and and store it, on the folder where you have adb and fastboot files, on your PC
Open a cmd line and execute these commands (beeing on that folder, of course):
adb devices (to make sure your device is detected)
adb reboot bootloader (to reboot into fastboot mode)
fastboot erase boot
fastboot flash boot twrp-3.3.1-2-unofficial-laurel_sprout.img
fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)​
Flash stock boot.img that matches your current build using TWRP install Image feature, into boot partition
Install the TWRP zip (always install the latest build available)
Reboot to System
Is that it?
If it is, the only downside I see is that, when a new version comes out (through OTA for example), you'll first need to get your hands on a stock boot.img that matches the new build.
Right?
Cheers!

Typhus_ said:
So, in other words, your method is this (correct me if I'm wrong):
Download TWRP zip file and copy it to your device (internal or external storage)
Download TWRP img file and and store it, on the folder where you have adb and fastboot files, on your PC
Open a cmd line and execute these commands (beeing on that folder, of course):
adb devices (to make sure your device is detected)
adb reboot bootloader (to reboot into fastboot mode)
fastboot erase boot
fastboot flash boot twrp-3.3.1-2-unofficial-laurel_sprout.img
fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)
Flash stock boot.img that matches your current build using TWRP install Image feature, into boot partition
Install the TWRP zip (always install the latest build available)
Reboot to System
Is that it?
If it is, the only downside I see is that, when a new version comes out (through OTA for example), you'll first need to get your hands on a stock boot.img that matches the new build.
Right?
Cheers!
Click to expand...
Click to collapse
As someone who just wants to root his phone with TWRP and few magisk modules, and not miss out on OTAs, seeing these many methods is so confusing and overwhelming ?

After flashing recovery from pc..then go for fastboot reboot from minimal adb and " volume+ key" i saw error in my phone "no command"

Sapper Morton said:
Use the method Typhus explained, it's more simple in the long run; there will be no need to manually flash stock boot image afterwards, since Magisk will have done a proper backup, thus, you will only need to use 'restore image' feature inside Magisk Manager; When taking an OTA, make sure to read the complete Magisk documentation before proceeding:
https://topjohnwu.github.io/Magisk/tutorials.html
Click to expand...
Click to collapse
Thank you! I will do that. But one more thing I'd like to ask. Do you know where I could find the boot image for 10.3.8.0.PFQMIXM? I checked git for dumps, but I couldn't find the boot image for this one.

Sapper Morton said:
Sure, read the OP; Typhus has linked a couple of boot images, including 10.3.8.0 PFQMIXM.
https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509
Click to expand...
Click to collapse
Sick! Thank you very much, sir!

What about flashing this on an already rooted phone with Magisk modules and the previously available TWRP by mauronofrio? Any complicated procedures? Is slot changing etc still necessary?

Makishima said:
What about flashing this on an already rooted phone with Magisk modules and the previously available TWRP by mauronofrio? Any complicated procedures? Is slot changing etc still necessary?
Click to expand...
Click to collapse
In that case, obviously, simply flash the new TWRP zip.
The install method I've explained is for everyone who never had TWRP, or Magisk patched boot, installed on the device.

Makishima said:
What about flashing this on an already rooted phone with Magisk modules and the previously available TWRP by mauronofrio? Any complicated procedures? Is slot changing etc still necessary?
Click to expand...
Click to collapse
Just flash the zip in twrp that you have.
That's what I did and it worked no problem on pe ROM

Typhus_ said:
In that case, obviously, simply flash the new TWRP zip.
The install method I've explained is for everyone who never had TWRP, or Magisk patched boot, installed on the device.
Click to expand...
Click to collapse
I did as you said but it says 'NOTE: You are now unrooted!'. Do I need to flash Magisk again?

Makishima said:
I did as you said but it says 'NOTE: You are now unrooted!'. Do I need to flash Magisk again?
Click to expand...
Click to collapse
Yes, that's right.

[ROM][STABLE] LineageOS 18.0 [MI A3] [laurel_sprout]

{
"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"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS 18.0 based on Android 11.0
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
WHATS WORKING :-
- RIL
- WiFi
- Bluetooth.
- Camera
- Audio
- Sensors
- Flash
- GPS
- VoLTE
- FOD (Fingerprint on display)
- Face unlock.
- DT2W.
- Proximity in calls.
- FBE.
WHAT DOESN'T :-
- You tell.
HOW TO FLASH :-
1) Download ROM zip and Gapps (optional).
2) Reboot to Recovery.
3) Wipe Data, System, Cache.
4) Format data. (It might work without this too but its recommended to format data to boot successfully. If stuck on splash or boot animation or reboots back to fastboot or recovery, format data)
5) Flash ROM + Recovery installer (any as per your choice).
6) Reboot to Recovery.
7) Wipe cache.
8) Reboot and enjoy.
IMPORTANT INSTRUCTIONS :-
- The build is based on OSS vendor. Firmware is included in the ROM zip. No need to flash any firmware.
- Fingerprint works fine with no flicker. (Accuracy is improved.)
- Face unlock works.
DOWNLOADS :-
ROM :- LineageOS 18.0
GAPPS :- GAPPS (optional)
DONATION LINKS :-
PLEASE DONATE ME IF YOU LIKE MY WORK
PayTM : [email protected]
Paypal : http://paypal.me/pms2299
GPay : [email protected]
I can't build continuously on my laptop and I need a server to build. Consider donating for continuous support. I will be able to provide bug fixes sooner if I get a server. Please donate if you can. Thanks
SUPPORT GROUP :-
LineageOS Support group :- Telegram
SOURCES :-
KERNEL
XDA:DevDB Information
LineageOS, ROM for the Xiaomi Mi A3
Contributors
PrathameshMS
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: 18.0
Stable Release Date: 2020-10-10
Created 2020-10-10
Last Updated 2020-10-10

Thank you so much

Great, and I mean, GREAT job!!
As usual....
Thank you for your hard work.

You're my [email protected]|<ing idol!
Starting download rigth now

So it is based on Android 11 or 10?

r3pairer said:
So it is based on Android 11 or 10?
Click to expand...
Click to collapse
It's based on 11

Can it be used daily?

i dont know is it only me or not
when im in a call (in discord or any other apps) others say that they can hear my phone sound like instagram or any other thing
i have this problem with any other roms so as lineage
please fix it thanks i realy want to use android 11

Great work. Fod is better than stock to recognize my finger, it has just a small and quickly brightness flickering but is almost unnoticeable.
SElinux is permissive and FM radio is missing but they aren't a big issues for me.
Thanks for this rom.

Hi! Does LOS18 supports signature spoofing? Thanks!

Step by step install procedure for LOS18
1 - Turn your phone into fastboot mode (run adb reboot bootloader or shutdown the phone and turn it on again while pressing Power + Vol- keys)
2 - On fastboot mode set a as the active slot by running the command:
Code:
fastboot set_active a
3 - Now, flash latest STOCK FASTBOOT ROM using flash_all.bat (or flash_all.sh if you're using Linux)
4 - Wait for the installation to finish and, after seeing the welcome screen, go to fastboot mode again
5 - Now run these commands:
Code:
fastboot set_active b
Code:
fastboot erase boot
Code:
fastboot flash boot twrp-3.3.1-17-laurel_sprout_Android_10_mauronofrio.img
Code:
fastboot reboot
(keep pressing Vol+ key to force the phone into recovery mode)​
6 - We're on TWRP Recovery using slot B. Do this:
Install twrp-3.3.1-17-laurel_sprout-Installer-mauronofrio.zip
Reboot to Recovery
Format Data with "yes"
Install lineage ROM zip
Install twrp-3.3.1-17-laurel_sprout-Installer-mauronofrio.zip (yes, again...)
Reboot to Recovery​
7 - Now we're on TWRP Recovery using slot A. Do this:
Install NikGApps Core version. (This is optional! The ROM works fine without any GApps but if you want them, use CORE version!)
Install Magisk (This is also optional! The ROM works fine without it but if you want it, get the MagiskR zip you'll find on the telegram support group!)
Reboot to fastboot and run:
Code:
fastboot flash dtbo dtbo.img
Code:
fastboot reboot
Your device will now reboot to System and you may enjoy LineageOS 18!​
NOTES:
By doing this procedure you will have LineageOS 18 system installed only on slot A!
If your device fails to boot, you should just start all over again! Trust me, it's easier than trying other flashing methods.
You can now install a different Recovery if you like, for example, SHRP Recovery. Simply go to TWRP and flash SHRP installer zip.
You can, also, install a different Kernel. Check the Telegram support group, there are other kernels compatible with this ROM (I'm using No. 192 OSS Batt version, for instance).
All files mentioned on this post can be found on the Telegram support group (including latest ROM build, MagiskR version, twrp and dtbo.img)
Cheers!

wifi does not work

Etzio_Auditore said:
wifi does not work
Click to expand...
Click to collapse
Did you use the correct procedure right before your post? I feel like the developer won't answer you lol

Does anyone got any issues ussing screen share? My device restart once I choose my tv, I've not tried it with a chromecast, Its a LG smart tv

Typhus_ said:
1 -
Turn your phone into fastboot mode (run adb reboot bootloader or shutdown the phone and turn it on again while pressing Power + Vol- keys)
2 - On fastboot mode run the command:
Code:
fastboot set_active a
3 - Now, flash latest STOCK FASTBOOT ROM using flash_all.bat (or flash_all.sh if using Linux)
4 - Wait for the installation to finish and as soon as you see the welcome screen on stock, go to fastboot mode again
5 - Now run these commands:
Code:
fastboot set_active b
Code:
fastboot erase boot
Code:
fastboot flash boot twrp-3.3.1-17-laurel_sprout_Android_10_mauronofrio.img
Code:
fastboot reboot
(keep pressing Vol+ key to force the phone into recovery mode)​
6 - Now we're on TWRP Recovery using slot B. Do this:
Wipe Dalvik, System and Data
Install lineage-18.0-20201010-UNOFFICIAL-laurel_sprout.zip
Install twrp-3.3.1-17-laurel_sprout-Installer-mauronofrio.zip
Reboot to Recovery​
7 - Now we're on TWRP Recovery but on slot A. Do this:
Wipe Dalvik, System and Data (Yes, again. I'm not Stupid, trust me.)
Install lineage-18.0-20201010-UNOFFICIAL-laurel_sprout.zip
Install twrp-3.3.1-17-laurel_sprout-Installer-mauronofrio.zip
Reboot to Recovery​
8 - You will be on slot B again. Change it back to slot A and reboot to Recovery. Now Format Data with "yes" option to remove stock encryption
9 - Reboot to Recovery again
10 - Install GApps (This is optional! The ROM works fine without any GApps. If you really want GApps you may install any version but I recommend just Core version)
11 - Reboot to bootloader and flash the dtbo.img by running the command:
Code:
fastboot flash dtbo dtbo.img
Code:
fastboot reboot
Your phone while boot into LineageOS 18 and it will be awesomely lag free!
NOTES:
By doing this procedure you will have LOS18 system and vendor installed on both slots!
dtbo.img has to be flashed because when you flash a "new vendor" on both slots you need to flash dtbo as well. If you don't do this you will lose your WiFi and Bluetooth!!
Now you can install Magisk if you want root features (for the time being you must use Magisk 20422 Canary Version)
You can now also install a different Recovery if you like, for example, SHRP Recvoery. Simply go to TWRP and flash SHRP installer zip.
I've tested this procedure yesterday like 2 or 3 times. I've been up almost to 3 AM testing stuff. Right now I'm on LOS18 WITHOUT ANY BUG!
All files mentioned on this post can be found on the Telegram support group (including Magisk version)
Of course that you must store the TWRP img file on the same folder you have platform-tools and the TWRP zip file on your SDCard or phone internal memory....duh...
If you feel like this procedure sucks because it's too long, or if you think that this can be completely ignored and just flash the ROM like you've always done then DON'T ASK FOR ANY HELP!!! This will SOLVE any stupid problem your phone might have, so.... yeah, I won't give you credit if you don't want to spare 20 minutes (if so...) flashing things the correct way.
Cheers!
Click to expand...
Click to collapse
Thank you for this great how to do process.
Always most informative and helpful.
I have just one question.
I am now in the latest STOCK EU rom, which I flashed through RECOVERY rom and then used the magisk_patched boot method to root. No TWRP or any other recovery in it.
My question is this:
Can I skip fastboot flash the STOCK rom again AND go to step 2 , OR it is mandatory to start from step 1?
Again, thanks for all your help giving us all that knowledge
:good::good:

If you never had any other custom ROM installed on other slot, or did but have gone back to stock using fastboot, yes you can ignore step 1.
Cheers!

Typhus_ said:
If you never had any other custom ROM installed on other slot, or did but have gone back to stock using fastboot, yes you can ignore step 1.
Cheers!
Click to expand...
Click to collapse
so I have to go from step 1, as I have flashed EVERY custom rom available
Thanks man you are GREAT:good:

after executing commands
fastboot set_active b
Code:
fastboot erase boot
Code:
fastboot flash boot twrp-3.3.1-17-laurel_sprout_Android_10_mauronofrio.img
Code:
fastboot reboot
i am booting back in fastboot even holding Vol+ while booting what should i do? Thank you

If you have the phone locked with a pin, when you go into SHRP recovery, typing the same pin doesn't decrypt the phone.

pol00001 said:
after executing commands
fastboot set_active b
Code:
fastboot erase boot
Code:
fastboot flash boot twrp-3.3.1-17-laurel_sprout_Android_10_mauronofrio.img
Code:
fastboot reboot
i am booting back in fastboot even holding Vol+ while booting what should i do? Thank you
Click to expand...
Click to collapse
Have you flashed stock ROM with flash_all.bat? If not, try that.

[RECOVERY] [OFFICIAL] TWRP 3.6.x for Galaxy A10 Exynos series [SM-A105] [4 January 2022]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
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 about this recovery
* before flashing 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.
Installation
Method 1
1) If you already have twrp on your phone, extract recovery.img from the tar file using Zarchiver (Download here).
2) Reboot your phone and boot into recovery.
3) Flash the recovery.img as "recovery"
4) Finally reboot to recovery to enjoy new twrp 3.6.x
Method 2 (WARNING: YOU WILL LOSE YOUR DATA)
1) If you are installing a custom recovery for the first time, open Odin on your pc. Download both the latest recovery and the vbmeta_disabled file attached below. Boot your phone in download mode.
2) Untick "autoreboot" and flash the vbmeta_disabled.tar file in the AP slot.
3) Follow the instructions on your phone's screen to reboot the phone.
4) Quickly repeat the steps to go back in download mode.
5) Untick "auto reboot" and flash the recovery.tar you downloaded in the AP slot
6) Follow the instructions on your phone's screen to reboot the phone.
7) As soon as the screen turns off, release all keys and press power + volume down keys till you boot into twrp 3.6.x
8) Go to wipe, and format your data.
9) Flash disable_dm_verity.zip (attached in post) in twrp to avoid fbe error.
10) You now have twrp 3.6.x
Download
Twrp 3.6.x for A10
Maintainer
Gabriel260
Support
Contact maintainer on telegram to report any bug → Gabriel
Thanks
TWRP team
Topjohnwu for root
afaneh92
Topser99

Fix etc/fstab "system_root" to "system" please

Thanks for this amazing build. Never ceases to surprise me.

can we have this twrp without root on phone .... ?
sorry for my silly question

Can you install this on the A10e? (A102)

koyo said:
Can you install this on the A10e? (A102)
Click to expand...
Click to collapse
no

howdeedodat said:
can we have this twrp without root on phone .... ?
sorry for my silly question
Click to expand...
Click to collapse
yeah

UPDATE NOTICE:
Twrp 3.5.1 released

Chatur27 said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
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 about this recovery
* before flashing 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.
Installation
Method 1
1) If you already have twrp on your phone, extract recovery.img from the tar file using Zarchiver (Download here).
2) Reboot your phone and boot into recovery.
3) Flash the recovery.img as "recovery"
4) Finally reboot to recovery to enjoy new twrp 3.5.1
Method 2 (WARNING: YOU WILL LOSE YOUR DATA)
1) If you are installing custom recovery for the first time, open Odin on your pc and load the tar file (download below) in the AP slot.
2) On the left of Odin, click on options and untick (remove the tick from) "autoreboot"
3) Boot your phone into download mode and connect it to the pc.
3) Flash the file in Odin. When flashing is complete in Odin, hold power + volume down keys on your phone to reboot
4) As soon as the screen turns off, release all keys and press power + volume down keys till you boot into twrp 3.5.1
5) Go to wipe, and format your data.
6) Flash disable_dm_verity.zip (attached in post) in twrp to avoid fbe error.
7) You now have twrp 3.5.1
Download
Twrp 3.5.1 for A10
Maintainer
Gabriel260
Support
Contact maintainer on telegram to report any bug → Gabriel
Thanks
TWRP team
Topjohnwu for root
afaneh92
Topser99
Click to expand...
Click to collapse
Where is the tar file?

LemonadeSnake said:
Where is the tar file?
Click to expand...
Click to collapse
Download and install 7zip and right click "recovery.img" file > Select 7-Zip from openned menu>Select "Add to Archive" > Replace "Archive Format" to TAR > Click OK > Wait To Compressing... ANDD Ready your TAR file, WALA!
Nice Day!

What has changed compared to the previous version?
Thanks for ALL!

CrazyGenius said:
Download and install 7zip and right click "recovery.img" file > Select 7-Zip from openned menu>Select "Add to Archive" > Replace "Archive Format" to TAR > Click OK > Wait To Compressing... ANDD Ready your TAR file, WALA!
Nice Day!
Click to expand...
Click to collapse
well too late oof i tried another method by somebody else and my phone is now bootlooping

EDIT:
Okay, now everything works, I did it according to this tutorial:​[Guide/Magisk] Root for the Galaxy A10 Series & Flash TWRP (Unlocked Exynos only, A10s not supported)​
Hello,
I have a problem installing TWRP, turned on OEM unlock, then unlocked the bootloader, then when the phone rebooted and went into OEM setup it was turned off so I turned it on. I put my phone into download mode and tried to load twarp via Odin and got the message "Only official released binaries are allowed to be flashed (RECOVERY).
Now, after starting the phone, when I enter programming options, the OEM unlock option is gone
Can I do something about it now? I have SM-A105FN
{
"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"
}

LemonadeSnake said:
well too late oof i tried another method by somebody else and my phone is now bootlooping
Click to expand...
Click to collapse
If you want to get rid of this thing, you can download the Official Firmware, extract it from the compressed file (and extract AP* file), make the necessary changes (replace stock "recovery.img" with TWRP img file, replace stock "vbmeta.img" with custom vbmeta and sarees...) and re-compress all extraxted and changed files to TAR file. Unselect "Auto Reboot" from Odin, select modified AP file from Odin AP menu and flash. If flashing complated, reboot phone directly recovery mode and flash all files.

CrazyGenius said:
If you want to get rid of this thing, you can download the Official Firmware, extract it from the compressed file (and extract AP* file), make the necessary changes (replace stock "recovery.img" with TWRP img file, replace stock "vbmeta.img" with custom vbmeta and sarees...) and re-compress all extraxted and changed files to TAR file. Unselect "Auto Reboot" from Odin, select modified AP file from Odin AP menu and flash. If flashing complated, reboot phone directly recovery mode and flash all files.
Click to expand...
Click to collapse
i can't access download mode without a jig, because it can't even get to the samsung loop animation without restarting.

JUST A NOTICE:
Twrp for A10 is now official !
Cheers

koyo said:
Can you install this on the A10e? (A102)
Click to expand...
Click to collapse
koyo said:
Can you install this on the A10e? (A102)
Click to expand...
Click to collapse
If you need twrp please send me stock recovery.img

Topser99 said:
If you need twrp please send me stock recovery.img
Click to expand...
Click to collapse
I don't have the phone. I was gonna buy it on the basis that it had TWRP but it doesn't so I bought the Moto G7 Play

Staniczek said:
EDIT:
Okay, now everything works, I did it according to this tutorial:​[Guide/Magisk] Root for the Galaxy A10 Series & Flash TWRP (Unlocked Exynos only, A10s not supported)​
Hello,
I have a problem installing TWRP, turned on OEM unlock, then unlocked the bootloader, then when the phone rebooted and went into OEM setup it was turned off so I turned it on. I put my phone into download mode and tried to load twarp via Odin and got the message "Only official released binaries are allowed to be flashed (RECOVERY).
Now, after starting the phone, when I enter programming options, the OEM unlock option is gone
Can I do something about it now? I have SM-A105FN
View attachment 5251963
Click to expand...
Click to collapse
If you are 100% sure of having your bootlaoder unlocked, reflash the stock rom you are on. It worked for me yesterday night.

Chatur27 said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
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 about this recovery
* before flashing 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.
Installation
Method 1
1) If you already have twrp on your phone, extract recovery.img from the tar file using Zarchiver (Download here).
2) Reboot your phone and boot into recovery.
3) Flash the recovery.img as "recovery"
4) Finally reboot to recovery to enjoy new twrp 3.5.1
Method 2 (WARNING: YOU WILL LOSE YOUR DATA)
1) If you are installing custom recovery for the first time, open Odin on your pc and load the tar file (download below) in the AP slot.
2) On the left of Odin, click on options and untick (remove the tick from) "autoreboot"
3) Boot your phone into download mode and connect it to the pc.
3) Flash the file in Odin. When flashing is complete in Odin, hold power + volume down keys on your phone to reboot
4) As soon as the screen turns off, release all keys and press power + volume down keys till you boot into twrp 3.5.1
5) Go to wipe, and format your data.
6) Flash disable_dm_verity.zip (attached in post) in twrp to avoid fbe error.
7) You now have twrp 3.5.1
Download
Twrp 3.5.1 for A10
Maintainer
Gabriel260
Support
Contact maintainer on telegram to report any bug → Gabriel
Thanks
TWRP team
Topjohnwu for root
afaneh92
Topser99
Click to expand...
Click to collapse
Can you install this on the a10 sm-a105m Android 10?

[RECOVERY][A9/A10] [UNOFFICIAL]SHRP 3.0 (20/01/15)

{
"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"
}
Standard Disclaimer:-
* Your warranty is... still valid?
* 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 features included in this Recovery
* before flashing 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.
SHRP is inspired by Material Design 2 to bring the newest design to TWRP. SHRP provides much more features alongside it's rich UI experience. New and improved dashboard makes it very easy to interact with TWRP. SHRP also got some extra cool features like whole new theming section , flash Magisk (root or unroot), Camera2API enabler directly from dashboard, password protection etc. It's all only just started , a lot more to come.
- Themes
- List view mode along with grid dashboard
- Status bar customization
- New rounded icons added on dashboard
- Notch mode with toggle to disable
- Dark mode or pure white, it's on you
- Navigation bar customization
- Settings + Advanced Settings
- Flash Magisk
- Clear fingerprints.
- Flash ViperFX
- Recovery Locking , Pin or Pattern lock
- CPU core lock/unlock
- Language changing
- HAL3 / CameraAPI2 enabling/disabling
- Oreo+ reboot menu style
- Redesigned lock screen interface
- Flashlight
- Magisk manager - Enable, disable or delete magisk modules right from SHRP
- and many more, flash right now to find out
1. Make sure you have a custom recovery installed
2. Download the latest SHRP recovery for your device
3. Boot into recovery
4. Flash SHRP recovery zip
5. Reboot to recovery.
6. Done
or
Fastboot flash boot shrp.img (currently only for stock vendor ROMs)
Recovery asks for decryption password every boot (You can say that this is a feature that increases security or just an inconvenient bug, i prefer the former)
File Manager back button dosent work, have to press home button to exit
Loading time is slightly longer than SHRP2 on boot
Thanks to @Master_L at the Telegram group for pointing out these small bugs
https://drive.google.com/drive/folders/12MDRsmJWtbQDCoAXlp1D3U0gHPYA4PSr?usp=sharing
Github
Website
Telegram Group
SHRP Team:
EpicX
DNI9
Giovix92
TeamWin
osmOsis
VR25
Topjohnwu
Mauronofrio
DarthJabba9
Pritish
Kirill
Burak D.
ZJRDroid
LayeardDevMod
Olek & Oliwier
Special Thanks:
@Nikesh001 (for TWRP trees)
@oddlyspaced (for SHRP trees)
@HarukeyUA (for LineageOS trees from which i took kernel and dtbo for recovery)
@AlaskaLinuxUser (for his amazing tutorials for building recoveries)
The Arch Wiki for helpming me deal wih pesky python building errors
Docker Inc. for Docker which helped me to finally compile this in Manjaro ( I don't like Ubuntu)
Please inform if I forgot to mention your name here , thanks !
Maintainer: NanduPV
Based On: TWRP
Source: SHRP 3_9.0
Screenshots:
​

is this able to flash it over Android 11 so in order to be able installing a Custom Rom? (Pixel Experience, EvolutionX)

Vicro2821 said:
is this able to flash it over Android 11 so in order to be able installing a Custom Rom? (Pixel Experience, EvolutionX)
Click to expand...
Click to collapse
No, only A9/A10 till TWRP supports A11

Is there any difference between this and my official builds?

oddlyspaced said:
Is there any difference between this and my official builds?
Click to expand...
Click to collapse
Just ported to new version 2.3.2 to 3.0, same trees. Many thanks for your contributions to our device

I don't ever see a clear guide how to install this recovery to a stock a10 unrooted device with bootloader unlocked... Step by step with any bricking risc. It's the first Time in ten year that i ever don't undsterstand the correct way to do this

wetito said:
I don't ever see a clear guide how to install this recovery to a stock a10 unrooted device with bootloader unlocked... Step by step with any bricking risc. It's the first Time in ten year that i ever don't undsterstand the correct way to do this
Click to expand...
Click to collapse
It is a bit complicated due to A/B system-as-root and new fastboot security restrictions
But, once you understand and do it, it is pretty simple.
Installing / Flashing TWRP (or any other recovery) on A/B devices:
Since all known A/B devices do not have a separate recovery partition, you will eventually have to flash TWRP to the boot partition. On the Pixel 1 and 2, and some other devices, we use fastboot boot to temporarily boot TWRP without flashing TWRP. We then flash a zip installer to to flash TWRP to both slots.
The Mi A3 unfortunately does not support fastboot boot. Instead, users have to determine their currently active boot slot using
Code:
fastboot getvar all
then use,
Code:
fastboot set_active_a
or
fastboot set_active_b
to switch slots to the inactive slot. From here, the user can
Code:
fastboot flash boot twrp.img && fastboot reboot
to get into TWRP. Once in TWRP they can then go to the reboot page and change back to their originally active slot, make a backup, then install TWRP. Using the inactive slot allows users to get a good, unmodified backup of their device before installing TWRP.
Hopefully this helps!
Taken from @Dees_Troy guide on all things TWRP @https://forum.xda-developers.com/t/dev-how-to-compile-twrp-touch-recovery.1943625/post-32965389
Note: To get TWRP or in this case SHRP image file, just extract SHRP installer zip and find recovery.img, this is the Image file you need.

NanduxXxPV said:
It is a bit complicated due to A/B system-as-root and new fastboot security restrictions
But, once you understand and do it, it is pretty simple.
Installing / Flashing TWRP (or any other recovery) on A/B devices:
Since all known A/B devices do not have a separate recovery partition, you will eventually have to flash TWRP to the boot partition. On the Pixel 1 and 2, and some other devices, we use fastboot boot to temporarily boot TWRP without flashing TWRP. We then flash a zip installer to to flash TWRP to both slots.
The Mi A3 unfortunately does not support fastboot boot. Instead, users have to determine their currently active boot slot using
Code:
fastboot getvar all
then use,
Code:
fastboot set_active_a
or
fastboot set_active_b
to switch slots to the inactive slot. From here, the user can
Code:
fastboot flash boot twrp.img && fastboot reboot
to get into TWRP. Once in TWRP they can then go to the reboot page and change back to their originally active slot, make a backup, then install TWRP. Using the inactive slot allows users to get a good, unmodified backup of their device before installing TWRP.
Hopefully this helps!
Taken from @Dees_Troy guide on all things TWRP @https://forum.xda-developers.com/t/dev-how-to-compile-twrp-touch-recovery.1943625/post-32965389
Note: To get TWRP or in this case SHRP image file, just extract SHRP installer zip and find recovery.img, this is the Image file you need.
Click to expand...
Click to collapse
Tnx a lot!

Great contribution! I'm looking forward to unlock bootloader, install recovery and a custom rom on my friend's mi A3. I have done my research but I still have one question. If I wanna keep the recovery after I install the custom rom, do I have to do anything? Or just flashing the zip before installing the rom will do the job? Thanks!

Batpope said:
Great contribution! I'm looking forward to unlock bootloader, install recovery and a custom rom on my friend's mi A3. I have done my research but I still have one question. If I wanna keep the recovery after I install the custom rom, do I have to do anything? Or just flashing the zip before installing the rom will do the job? Thanks!
Click to expand...
Click to collapse
Just make sure to flash the Recovery installer zip after the ROM you flash.

[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy Note 20 & Note 20 Ultra Exynos

{
"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"
}
Official TWRP 3.6.1-* For Galaxy Note 20 & Note 20 Ultra​Only for exynos variants - N980F / N981B / N985F / N986B (Europe - Global, Single/Dual-SIM)
Disclaimer
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 features included in this recovery before flashing 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.
Kernel Features:
N986BXXU3FVC5 kernel source (OneUI 4.1 / March 2022 sourcecode)
disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
Recovery Features:
Android 11 tree
built in full 64 mode
toybox/busybox support
compatible with Android 12.0 and above
Downloads:
Galaxy Note 20 (c1s / N980F / N981B)
Galaxy Note 20 Ultra (c2s / N985F / N986B)
AVB disabled vbmeta
* official TWRP builds are not up yet, you can find latest test builds in post #2, below
Instructions:
Odin (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .tar file according to your device
Download AVB disabled vbmeta .tar
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Heimdall (Linux)
Install heimdall & additional required packages:
Code:
sudo apt-get update
sudo apt-get install heimdall-flash android-tools-fastboot android-tools-adb libusb-0.1-4 libusb-1.0-0 libusb-1.0-0-dev
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .img file according to your device
Download AVB disabled vbmeta .img
Open your preferred terminal in linux and type (replace red lines with the path of downloaded img files):
Code:
sudo heimdall flash --RECOVERY /path/to/recovery.img --VBMETA /path/to/vbmeta.img
and press enter - once you press enter grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
TWRP
Download .img file for your device and install from your current TWRP with Install image - browse to image location and select - Recovery
dd (Requires root)
Download .img file for your device, place it in the root of your /sdcard folder, rename it to twrp.img then run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13100000.ufs/by-name/recovery
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Sources:
Device trees - c1s / c2s
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9830/tree/android-11.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, geiti94, jesec, dyneteve, ianmacd, testers, donors and anyone else involved in making this possible
As always, if you like what i do, you can always send me some pizza/coffee/drugs/drinks or anything else via paypal.me/corsicanu

Compatibility and changelog:
06.05.2022 - Initial TWRP 3.6.1 release
Compatibility: Android 12 (OneUI 4.0 & 4.1)
Security patch: N/A
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
Further reading:
Full guide of how to unlock/root your device
Background on Android Verified Boot
Rollback protection

FAQ
Q: Can i use this recovery with other firmware then mentioned in compatibility?
A: Only with same Android version or Rollback protection might kick in and you won't be able to pass the lockscreen.
Q: Where do i get vbmeta.img?
A: From here, download the one you need according to install instructions.
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you flashed multidisabler zip / formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.
Q: Why do i need to format data partition?
A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.

Updated first post with official pages from twrp.me, but since the builds are not up yet, i posted latest test builds in post #2.
Regards

well done sir

Hello! I have a rooted sm-n980f exynos European version. I rooted my phone using magisk patched AP file through odin. I am trying to flash twrp 3.6.1 above and vbmeta.tar using odin but it fails. What shall I do? Thank you!

edsoedso said:
Hello! I have a rooted sm-n980f exynos European version. I rooted my phone using magisk patched AP file through odin. I am trying to flash twrp 3.6.1 above and vbmeta.tar using odin but it fails. What shall I do? Thank you!
Click to expand...
Click to collapse
Can you attach a screenshot of Odin and eventually tell me if you see anything in particular changing on phone screen? It should throw an error or something below the usual download mode lines. A pic of phone screen would be nice but i'd assume it's your only phone..
Regards

corsicanu said:
Can you attach a screenshot of Odin and eventually tell me if you see anything in particular changing on phone screen? It should throw an error or something below the usual download mode lines. A pic of phone screen would be nice but i'd assume it's your only phone..
Regards
Click to expand...
Click to collapse
Nothing changes in the screen phone. Attached is odin screen. Thank you!

edsoedso said:
Nothing changes in the screen phone. Attached is odin screen. Thank you!
Click to expand...
Click to collapse
Can you please check Kg state line from download mode? What's written there?

corsicanu said:
Can you please check Kg state line from download mode? What's written there?
Click to expand...
Click to collapse
I installed twrp but it seems that it does not read the internal storage.

corsicanu said:
Can you please check Kg state line from download mode? What's written there?
Click to expand...
Click to collapse
And how to flash the multidisabler? it seems that everything is encrypted and is impossible to locate it in twrp?

I found it!
1. enter into TWRP (after flashing twrp.tar and Vbmeta.tar via odin), format data and reboot again in TWRP
2. Being in TWRP, transfer from PC to your phone multidisabler.zip and magisk zip.
3. flash them both
4. reboot system
That is all!

i have note 20 5G N918B , i make every thing but my mobile keep restarting in to TWRP recovery , not going to system

Hello! What can be done to remove encryption from TWRP? I have flashed disabler but it still continues to encrypt. I tried formatting data from twrp, changing file system to EXT4 and back to EXT2 but with no result so far. any help?

m7mdo_93 said:
i have note 20 5G N918B , i make every thing but my mobile keep restarting in to TWRP recovery , not going to system
Click to expand...
Click to collapse
edsoedso said:
Hello! What can be done to remove encryption from TWRP? I have flashed disabler but it still continues to encrypt. I tried formatting data from twrp, changing file system to EXT4 and back to EXT2 but with no result so far. any help?
Click to expand...
Click to collapse
I'm still trying to find the issue, for whatever reason multidisabler needs a second flash to work as far as i seen on my device. So for now please flash multidisabler 2 times in a row, until i find a better solution to this.
Regards

corsicanu said:
I'm still trying to find the issue, for whatever reason multidisabler needs a second flash to work as far as i seen on my device. So for now please flash multidisabler 2 times in a row, until i find a better solution to this.
Regards
Click to expand...
Click to collapse
yeah , after flashing multidisabler second time my mobile able to working .. thanks for your help

corsicanu said:
I'm still trying to find the issue, for whatever reason multidisabler needs a second flash to work as far as i seen on my device. So for now please flash multidisabler 2 times in a row, until i find a better solution to this.
Regards
Click to expand...
Click to collapse
Thank You very much. It worked!

A big thank you, it works fine.

hey.
i did everything from this guide, and i got root access+twrp installed.
the problem that i am facing, is that i canot install anything from twrp, due to insufficient space.
the system size that twrp is reading is only 8384kb, so every installation of gapps is failed.
i tried to wipe ,format data, and changing the file system, but nothing helped.
please give me an idea how to solve it.
thanks.

Good day
Does this work for Android 13 One UI 5.1?