[RECOVERY][UNOFFICIAL] TWRP for Galaxy S21 (Exynos)

[RECOVERY][UNOFFICIAL] TWRP for Galaxy S21 (Exynos) - Samsung Galaxy S21 ROMs, Kernel

Changelog:
29.11.2021 - Update to TWRP 3.6.0
- Updated to latest kernel source
- Update multidisabler
- fstab clean up
- Fix haptic feedback
21.08.2021 - Add Symlinked dynamic partitions to fstab
- Fix dtbs issue from previous build
09.08.2021 - Updated to latest kernel source
- No vbmeta disable require
- fstab clean up
03.03.2021 - Initial Release.

Wait if this is for the S21 Ultra only what is this doing in the normal s21 forum?
Youre very fast gg

DeblaGaming said:
Wait if this is for the S21 Ultra only what is this doing in the normal s21 forum?
Youre very fast gg
Click to expand...
Click to collapse
My bad I missed that but you can know from G991B its regular not Ultra.

@afaneh92 The recovery supports flashing Magisk APK out-of-the-box?
So, no need to rename the .apk to .zip anymore?

I'm kinda casual, with haptic feedback not working do you mean the vibration motor in the phone stops working completely, or? I don't know what encryption not working means either.
I saw the same issues for the S20 FE.
Looking at both forums closely currently as I'm deciding which phone to buy dependent on which phone will have a better root experience.

Will this have to be done everytime there is a firmware update?? Or like other devices we can keep twrp and magisk when updating..
I currently have S20 which I dont have twrp on but can update new firmware and just reboot to odin after flashing new firmware and just flash patched boot.img and all is good. Will the S21 be the same

DJBhardwaj said:
@afaneh92 The recovery supports flashing Magisk APK out-of-the-box?
So, no need to rename the .apk to .zip anymore?
Click to expand...
Click to collapse
You can flash apk
orkavaneger said:
I'm kinda casual, with haptic feedback not working do you mean the vibration motor in the phone stops working completely, or? I don't know what encryption not working means either.
I saw the same issues for the S20 FE.
Looking at both forums closely currently as I'm deciding which phone to buy dependent on which phone will have a better root experience.
Click to expand...
Click to collapse
Vibration not working in twrp only, read more.
bigpotato107 said:
Will this have to be done everytime there is a firmware update?? Or like other devices we can keep twrp and magisk when updating..
I currently have S20 which I dont have twrp on but can update new firmware and just reboot to odin after flashing new firmware and just flash patched boot.img and all is good. Will the S21 be the same
Click to expand...
Click to collapse
Yes need to redo every step.

i got my s21 rooted with ap, and magisk install thing. now i want to get twrp, is it just followed the guide or should i factory ap first?

Emrah132 said:
i got my s21 rooted with ap, and magisk install thing. now i want to get twrp, is it just followed the guide or should i factory ap first?
Click to expand...
Click to collapse
Follow instructions.

i didnt need vibration its great job thank you afaneh92

can i flash twrp without lost magisk root?

What about encryption issue.. is there any clue on next release. I don't think I found a problem except for the two things that were mentioned above bugs

Hi,
I was able to install magisk. In the end, I want to install exposed framework. In the TWRP mode, whenever I try to install, I get an error.
-Mounting /system and /vendor read-write mount: can't find /system in /proc/mounts
!Failed: /system could not be mounted
In the end, it says "Updating partition details" .. done. Can you please help me in resolving this error.

Thanks for your efforts, dev! Everything working as expected.

Hello, is there any way to re-enable encryption after TWRP installation? No matter, FBE or FDE. It says "not fully working" and I see only not working at all, maybe I am doing something wrong?

A note on firmware updates:
It is possible to follow all the instructions from the original post but SKIP the step of wiping your data from within TWRP when updating your firmware. You need to run the multidisabler though. This works if you had already installed this TWRP version with encryption disabled, including a data wipe, but now want to update your firmware. So wiping data is only needed for the first time.
In fact, if you had installed this TWRP version and do a firmware update via odin but do not flash this TWRP version with vbbeta disabled, your phone simply won't start anymore. It will ask you to factory reset.
So once you go TWRP, you have to reinstall it for future updates.
@afaneh92 do you want to add this as a hint in your OP?

Thank you for your great work and the fast twrp publishing! I was able to install and boot a GSI.
Now I would like to flash microg/gapps to system, but the system partition does not have any free space left. In the twrp wipe menu I cannot find the system partition to increase size. Would it be possibe to add this feature or are other steps mandatory to increase system partition in size?
Again, thanks a lot for your efforts!

Hi, I have my S21 Rooted with Magisk Patched Stock Image.
It is possible to flash TWRP but without doing a Data Wipe?
It isn't clear if the Data Wipe is needed for Rooting after unlocking the bootloader (I already did that), or it is actually needed for getting TWRP to fully work.
Thanks.

WiS3 said:
Hi, I have my S21 Rooted with Magisk Patched Stock Image.
It is possible to flash TWRP but without doing a Data Wipe?
It isn't clear if the Data Wipe is needed for Rooting after unlocking the bootloader (I already did that), or it is actually needed for getting TWRP to fully work.
Thanks.
Click to expand...
Click to collapse
In your place I would just try. Take a backup and try the installation, skipping ONLY the data wipe. If this fails, either use your backup or include the wipe.
Though, I HIGHLY assume you need to wipe for the first install of TWRP to remove the encryption initially. In future TWRP updates, you can skip wiping.

Related

[Recovery][Official] OrangeFox R11.0 Snapdragon [N97x0][26.Jul.20]

{
"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"
}
Orange Fox custom recovery
What is Orange Fox?
This custom recovery is based off TWRP, but has added features and different styling.
For more information visit the official wiki - HERE
Features
* Updated with latest TWRP commits
* Built-in support for installing Magisk
* White Flashlight
* Password pretext your recovery
* Better language support
* Optimized versions of community scripts
* Fox theme engine:
- choice of theme (black, dark, etc)
- choice of color scheme
- choice of splash screen
* Alternative lockscreen
Downloads
MEGA
Kernel - GitHub
OFRP Source - [URL="https://gitlab.com/OrangeFox]GitLab[/URL].
Thanks to the main OrangeFox contributors @MrYacha and @DarthJabba9
Also TeamWin for TWRP
--->

Installation
From existing TWRP or OrangeFox recovery
1. Download the OrangeFox zip to your device
2. Reboot to TWRP-based Recovery
3. Install the OrangeFox zip
4. Reboot recovery
From stock unrooted
1. Unlock bootloader
2. Download OrangeFox Odin installer .tar to PC
3. Boot device into download mode, and connect to PC
4. Uncheck auto reboot in Odin
5. Flash the OrangeFox .tar file to the AP tab
6. When flashed, and you are ready, force reboot into recovery.
7. Download Encryption disabler, and transfer to device.
8. Flash Encryption disabler, FORMAT data, reboot recovery.
9. Download Magisk and transfer to device. Flash.
10. Boot up, first boot may hang. After 3min waiting, hard reboot and you should boot straight into initial setup.
** Don't reboot device before going through initial setup and connecting to the internet. This is needed for KG status to read normal. If you don't do this, you may find yourself in a prenormal state.
** If installing OrangeFox through Odin, you will be missing the Fox add-ons, which aren't essential. But if so desired, flashing the OrangeFox zip from existing custom recovery will install the necessary files for Fox add-ons.
--->

Screenshots
Gallery

Mentalmuso said:
Screenshots
Gallery
Click to expand...
Click to collapse
Thanks for making an N9700 version.
Works great!!
Any chance you can get USB OTG to work?
Android detects my Sandisk Extreme, but TWRP does not.
Duh! Forgot to mount USB drive...now it works!

difference between this and mental?
best to start making custom roms instead
edit: i see this is by mental lol
weird

pretty cool, thanks. Theres a couple bugs: haptics dont work and the keyboard covers the input line in the terminal. Also, I don't know if this is intended for this recovery, but system apps are not shown in the app manager even though I have mounted system as rw. That would be really cool if they were.
Seems like this recovery has the potential to be a great tool for system-on-root modding. I'll keep for a little while, but not being able to use the terminal will end up being a deal breaker if not fixed. Why is it hidden away in menus too? Anyhow, know you didnt design it, thanks for the work in porting this!

AllanRSS said:
pretty cool, thanks. Theres a couple bugs: haptics dont work and the keyboard covers the input line in the terminal. Also, I don't know if this is intended for this recovery, but system apps are not shown in the app manager even though I have mounted system as rw. That would be really cool if they were.
Seems like this recovery has the potential to be a great tool for system-on-root modding. I'll keep for a little while, but not being able to use the terminal will end up being a deal breaker if not fixed. Why is it hidden away in menus too? Anyhow, know you didnt design it, thanks for the work in porting this!
Click to expand...
Click to collapse
Thanks, I'll take a look at those items. I haven't done much else since release, but I'll see if I can move the terminal to the front menus.

Is it really that easy to root a SnapDragon?

Eddie_Brock said:
Is it really that easy to root a SnapDragon?
Click to expand...
Click to collapse
Yes!

Mentalmuso said:
Thanks, I'll take a look at those items. I haven't done much else since release, but I'll see if I can move the terminal to the front menus.
Click to expand...
Click to collapse
That would be awesome if you could figure those things out. No pressure of course, I appreciate what you've done so far.
I do think if fixed up a bit this has the potential to be a great tool for our phones. System on root devices need a robust solution for modifying system files, and this recovery seems like a great start to achieving that. Adding system app management would be the obvious first choice for a feature many people would appreciate

flashed it in twrp and twrp keeps coming up. something is wrong

cylent said:
flashed it in twrp and twrp keeps coming up. something is wrong
Click to expand...
Click to collapse
Flashed what? Link me to the file you flashed

Mentalmuso said:
Flashed what? Link me to the file you flashed
Click to expand...
Click to collapse
https://mega.nz/#F!ng8WiCqD!AGERu9vO97A0YBnnmaXOaA?PxtiDASY
the zip

cylent said:
https://mega.nz/#F!ng8WiCqD!AGERu9vO97A0YBnnmaXOaA?PxtiDASY
the zip
Click to expand...
Click to collapse
Ok, assuming you have the n9750 device, I don't have much else to say. I just tested installing TWRP, then using the orangefox zip to flash OF. and it works fine for me.

I have twrp working and even have nemesis kernel installed.
When I flash orangefox zip in twrp items successful but when I boot into recovery it's twrp once again.
Should I flash it via Odin?
Also, I am on infinity rom...n975fds

cylent said:
I have twrp working and even have nemesis kernel installed.
When I flash orangefox zip in twrp items successful but when I boot into recovery it's twrp once again.
Should I flash it via Odin?
Also, I am on infinity rom...n975fds
Click to expand...
Click to collapse
This is for snapdragon phones only if your model is n975fds then you have exynos model which means this recovery won't work on your phone

minidude2012 said:
This is for snapdragon phones only if your model is n975fds then you have exynos model which means this recovery won't work on your phone
Click to expand...
Click to collapse
Now you tell me
Any chance of exynos version?
Post 14 above he said it works.
https://forum.xda-developers.com/showpost.php?p=81932681&postcount=14

cylent said:
Now you tell me
Any chance of exynos version?
Post 14 above he said it works.
https://forum.xda-developers.com/showpost.php?p=81932681&postcount=14
Click to expand...
Click to collapse
You might consider a different hobby...RTFM
Sent from my SM-N975F using XDA Labs

CAREFUL
I tried to boot into this recovery again yesterday and there was a verified boot problem. I went into a bootloop in download mode with the following error. I had to reflash twrp from odin to get the device back. I'm going to wait till this has been developed a little more to use it on my main device.
"partition vbmeta
Reason vbmeta: Error verifying vbmeta image:
0_0_INDIVLDVMT_EDRHS_IMTHSGAUEMSAC"

AllanRSS said:
CAREFUL
I tried to boot into this recovery again yesterday and there was a verified boot problem. I went into a bootloop in download mode with the following error. I had to reflash twrp from odin to get the device back. I'm going to wait till this has been developed a little more to use it on my main device.
"partition vbmeta
Reason vbmeta: Error verifying vbmeta image:
0_0_INDIVLDVMT_EDRHS_IMTHSGAUEMSAC"
Click to expand...
Click to collapse
This recovery is based off TWRP... vbmeta issues purely stem from root or more specifically magisk.

[RECOVERY][UNOFFICIAL] TWRP for Galaxy S20 FE 5G (Snapdragon)

{
"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"
}
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 your 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 me for messing up your device, I will laugh at you.
Supported Models:
Galaxy S20 FE 5G G7810, G781B, G781N, G781U, G781U1, G981W and G780G (4G).
US/Canada bootloader unlock thread:
here
Download & Guide:
1. Unlock your bootloader.
2. Download S20 FE 5G: r8q.
3. Reboot to download mode and flash vbmeta_disabled.tar in AP slot and reboot. Device will reboot to stock recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
4. Put the TWRP tar for your device with Odin in the AP slot and click start.
5. Reboot to recovery via recovery key combo.
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.- Type: multidisabler again. will see - Finished. when done.7. Go back to Wipe > Format Data > type yes.
8. Reboot to recovery.
9. Flash magisk apk in twrp.
10. Reboot to system, Enjoy.
Note:
To disable encryption manually:
You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.qcom
To avoid stock recovery restoration manually:
Rename system/recovery-from-boot.p to recovery-from-boot.p.bak
Click to expand...
Click to collapse
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ooobs007 for testing on S20 FE 5G G781B
ianmacd for multidisabler
Sources:
Kernel tree
Device tree

Changelog:
02.06.2022 - Update to Android 12 kernel source
- Fix mount issues
- Update to TWRP 3.6.2
29.11.2021 - Update to TWRP 3.6.0
- Add Symlinked dynamic partitions to fstab
- Updated to latest kernel source
- Update multidisabler
- fstab clean up
- Fix haptic feedback
23.05.2021 - Update to latest TWRP source, update kernel to G781BXXU3CUD6.
03.03.2021 - Update to latest TWRP source, Add terminal multidisabler script. fstab cleanup.
22.01.2020 - Fix USB-OTG for Q & R builds.
15.01.2020 - Initial build for Android 11
31.12.2020 - Update TWRP to 3.5.0
15.11.2020 - Add TWRP fastbootd support, Move kernel to gz format.
11.11.2020 - Initial Release.

Hello,
Thank you very much my friend .

my phone Unlock bootloader ok
install Magisk Manager ok
-----------------------------
just ı want twrp
please exynos s20 fe

arlequin2k3 said:
Hello,
Thank you very much my friend .
Click to expand...
Click to collapse
Welcome, Enjoy.
bylumax said:
my phone Unlock bootloader ok
install Magisk Manager ok
-----------------------------
just ı want twrp
please exynos s20 fe
Click to expand...
Click to collapse
Exynos not supported. maybe in future.

afaneh92 said:
Supported Models:
Galaxy S20 G7810, G781N, G781U, G781U1 and G981W.
Click to expand...
Click to collapse
So it doesn't work with the G781B version, right?

ilMerovingio said:
So it doesn't work with the G781B version, right?
Click to expand...
Click to collapse
Should work with any Snapdragon version with an unlockable bootloader, therefore any non US Fe version.

ilMerovingio said:
So it doesn't work with the G781B version, right?
Click to expand...
Click to collapse
Oh, sorry forgot to add it.
It was tested on G781B.

Hello ,
Okay I just tried to install twrp. So the installation went well but the concern is that it does not recognize my sd card and therefore cannot access the multidisabler and magik files to continue ....
I also tested by putting everything on a usb key and the same problem .....

arlequin2k3 said:
Hello ,
Okay I just tried to install twrp. So the installation went well but the concern is that it does not recognize my sd card and therefore cannot access the multidisabler and magik files to continue ....
I also tested by putting everything on a usb key and the same problem .....
Click to expand...
Click to collapse
You can push them through adb to any place like root / or /data
Also you can use external sd!
Try to copy files to sdcard while you booted to system!
USB OTG will be fixed next build.

afaneh92 said:
You can push them through adb to any place like root / or /data
Also you can use external sd!
Try to copy files to sdcard while you booted to system!
USB OTG will be fixed next build.
Click to expand...
Click to collapse
Your idea to connect the pc to the phone to seem to work. Twrp recognized the twrp file on my disk and I introduced the 2 files. And there it worked .... Thank you very much for the idea.

Silly question but can I still install OTA updates if I unlock bootloader/flash custom recovery or root the phone? And will stock recovery flash every time I install OTA update?
Thanks in advance

Is there magisk that we can root? Any guides on it please.

Huberttus said:
Silly question but can I still install OTA updates if I unlock bootloader/flash custom recovery or root the phone? And will stock recovery flash every time I install OTA update?
Thanks in advance
Click to expand...
Click to collapse
Flashing multidsabler make some changes to system and vendor. So no OTA, Flash full firmware instead.
Nchls said:
Is there magisk that we can root? Any guides on it please.
Click to expand...
Click to collapse
Flash magisk zip in TWRP or patch boot.img using magisk manager and flash via odin.

New build up!
15.11.2020 - Add TWRP fastbootd support, Move kernel to gz format.

After installing this will i use knox stuff like secure folder?

tabish84 said:
After installing this will i use knox stuff like secure folder?
Click to expand...
Click to collapse
No, you need to fix them to work again.

Hello ,
This update can be installed directly or must first be installed the 1st version. I ask this question given the size difference between the 2. Thank you for your answer .

arlequin2k3 said:
Hello ,
This update can be installed directly or must first be installed the 1st version. I ask this question given the size difference between the 2. Thank you for your answer .
Click to expand...
Click to collapse
Yes can be flashed directly, You can see in changelog that we moved to gzip format, that explain the size difference.

afaneh92 said:
No, you need to fix them to work again.
Click to expand...
Click to collapse
Where is the fix?

Development [RECOVERY][OFFICIAL] TWRP 3.7 for Galaxy A52 4G and A72 4G

{
"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.7 For Galaxy A52 4G and A72 4G
Disclaimer
Code:
*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.
Features:
Android 11, 12 and 13 support
Encryption support (AOSP and OneUI)
Bugs:
Encryption only works on OneUI if no screen lock is set
Downloads:
A52 4G: TWRP.me
A72 4G: TWRP.me
How to install
Open Settings -> About Phone -> Software and tap "Build Number" 7 times until it says "developer mode enabled".
Go back to Settings -> Developer Options -> Enable "OEM unlocking"
Enter Download Mode by powering off your phone, then hold down both volume keys and connect your phone to a Computer.
Release all keys, then hold down Volume Up to get into "Device unlock mode" and confirm that you want to unlock the bootloader. This will wipe all data from the phone.
The phone will automatically reboot. Now go through the initial setup and connect your phone to the internet (either using Wifi oder Mobile data).
Go back to Developer Options and check that OEM Unlocking is there and grayed out. Your bootloader is now unlocked.
Download and install Samsung Drivers on your Computer.
Download the latest *.tar from the TWRP website for your phone.
Download Odin, from example from https://downloads.corsicanu.ro/samsung/.
Turn off your phone and reboot to download mode by holding down Volume up and Volume down and then connect your phone to a PC. Then press Volume Up once to get into Download mode.
Open Odin and check if your device is detected.
Put the TWRP tar file you downloaded into the AP tab and put disabled VBMeta in the USERDATA slot.
Click start and wait for the installation to finish, Odin will show PASS.
Immediately after the screen goes black hold down Volume up and Power button at the same time until you enter TWRP (You may need to release the keys after about 20-30secs due to the "unlocked bootloader" warning).
If you properly followed all the steps you should now see the TWRP menu.
Once TWRP has booted you need to format your data again to be able to boot into system.
Donations
This is not essential, but if you like TWRP and my work feel free to send me or TWRP a donation.
Sources:
A52 4G: https://github.com/TeamWin/android_device_samsung_a52q
A72 4G: https://github.com/TeamWin/android_device_samsung_a72q
Kernel: https://github.com/Simon1511/android_kernel_samsung_sm7125
Credits:
TeamWin
@Velosh for the original TWRP trees
@corsicanu for updating multidisabler for A12 and providing download links for Odin, USB drivers, etc
@redymedan for the video guide
Testers on Telegram
Everyone else involved

Reserved.

Nice job, congrats! Glad to see another Samsung being alive in terms of custom deving.

Amazing! thanks for the work Devs!

Hello Simon1511,
Please, to not make mistakes, the first time when I enter the TWRP, I must in the right order :
- 1 Format Data
- 2 Flash Multi-Disabler
- 3 Flash Disable DM Verity
- 4 Reboot on recovery or system to access the phone
In addition for Android 12, I have to root the phone first ?
Because I want to have on this phone also ROOT + TWRP.
I come from an s10 Android 10 and the way to install TWRP seems different...
Thank you in advance.

The restoration is not working for vbmeta and super partition

Elvaa said:
The restoration is not working for vbmeta and super partition
Click to expand...
Click to collapse
Restoring the super partition works fine.
However, restoring vbmeta is generally not possible because only Odin can flash stuff to it.

TWRP has been updated to version 3.7!
Changelog
Code:
-Encryption/Decryption support for AOSP 12 and 13 ROMs
-Updated kernel to latest
-Fixed USB OTG and enabled NTFS support
-Switched to using FFS for MTP
-Added busybox bins
-Fixed ADB sideload

Hope this works for Android 13 on "A525FXXS4CVK4".

MobAndro said:
Hello Simon1511,
Please, to not make mistakes, the first time when I enter the TWRP, I must in the right order :
- 1 Format Data
- 2 Flash Multi-Disabler
- 3 Flash Disable DM Verity
- 4 Reboot on recovery or system to access the phone
In addition for Android 12, I have to root the phone first ?
Because I want to have on this phone also ROOT + TWRP.
I come from an s10 Android 10 and the way to install TWRP seems different...
Thank you in advance.
Click to expand...
Click to collapse
I hope the "DM Verity Disabler (Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip)" works for One UI 5.0 also...

SRooks1976 said:
I hope the "DM Verity Disabler (Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip)" works for One UI 5.0 also...
Click to expand...
Click to collapse
You don't need to flash that.
As you can see in the guide you only have to flash Multidisabler.

Why this keeps popping up after I installed this TWRP recovery, whilst earlier I patched the original AP file with Magisk and installed the firmware with that AP file, rooted my A52 (A525F), it was not there.
But when I installed TWRP, format Data, installed multi-disabler zip file, this keeps popping up.

SRooks1976 said:
Why this keeps popping up after I installed this TWRP recovery, whilst earlier I patched the original AP file with Magisk and installed the firmware with that AP file, rooted my A52 (A525F), it was not there.
But when I installed TWRP, format Data, installed multi-disabler zip file, this keeps popping up.
Click to expand...
Click to collapse
Well, this happens because the multidisabler zip disables most of Samsung's security mechanisms which (for somehow) make the phone think that a Service Provider Update is needed.
This should go away once you confirm it and/or reboot.

Can I root & install twrp with A13?

Simon1511 said:
Well, this happens because the multidisabler zip disables most of Samsung's security mechanisms which (for somehow) make the phone think that a Service Provider Update is needed.
This should go away once you confirm it and/or reboot.
Click to expand...
Click to collapse
Nope, even after rebooting many of times, the s**t happens.......
Reverting to Magisk Method without TWRP.

SRooks1976 said:
Why this keeps popping up after I installed this TWRP recovery, whilst earlier I patched the original AP file with Magisk and installed the firmware with that AP file, rooted my A52 (A525F), it was not there.
But when I installed TWRP, format Data, installed multi-disabler zip file, this keeps popping up.
Click to expand...
Click to collapse
This happens because you install a CSC that's not your original and it can't find the configuration for your SIM. Deleting system/priv-app/CIDManager should fix it.

Hello!
ShaDisNX255 said:
This happens because you install a CSC that's not your original and it can't find the configuration for your SIM. Deleting system/priv-app/CIDManager should fix it.
Click to expand...
Click to collapse
Hello! Is the latest one must be selected to backup system/vendor partition and restore it correctly later? If so, why its size is not counted?

can i flash this twrp on my a52f, which is still on stock rom binary 2

Linlova said:
can i flash this twrp on my a52f, which is still on stock rom binary 2
Click to expand...
Click to collapse
#1 says:

Simon1511 said:
#1 says:
View attachment 5794007
Click to expand...
Click to collapse
I already knew that before hehe, but just to make sure

Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy S22 Ultra (Snapdragon)

{
"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"
}
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 your 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 me for messing up your device, I will laugh at you.
Supported Models:
Galaxy S22 Ultra S908E/S908N/S9080.
Download & Guide:
1. Unlock your bootloader.
2. Downloads for S22 Ultra: AFH: b0q twrp and kernel / Drive: b0q twrp and kernel
3. Reboot to download mode
4. Put the TWRP TAR for your device with Odin in the AP slot, vbmeta_disabled_R.tar in USERDATA slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.- Type: multidisabler again. will see - Finished. when done.- Go back to Wipe > Format Data > type yes.- Reboot to recovery.7. Flash custom kernel and magisk apk in twrp.
8. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
@Dan_FFM (David Dean) for helping with convert readonly f2fs vendor to readwrite
Donators
Sources:
Kernel tree
Device tree

Changelog:
GitHub History

Note1: You need a custom permissive kernel to boot with R/W vendor.
Note2: If you got bootloop on Samsung logo, reboot to TWRP and wipe metadata from Advanced Wipe section.

Fantastic!

Once again, Mohammad works his magic

Again the same old question; Sorry !
How to correctly update to the next base without wiping the user data (Keeping Root and TWRP) ?

JazonX said:
Again the same old question; Sorry !
How to correctly update to the next base without wiping the user data (Keeping Root and TWRP) ?
Click to expand...
Click to collapse
If your data encryption already disabled just run multidisabler without wipe.
If not need to start from scratch

JazonX said:
Again the same old question; Sorry !
How to correctly update to the next base without wiping the user data (Keeping Root and TWRP) ?
Click to expand...
Click to collapse
Uninstall all magisk modules if have
Update firmare base with odin
Flash TWRP (including patched vbmeta) & Kernel (You can do this along with flashing stock firmware with USERDATA tab)
Straightway reboot to TWRP and run multidisabler from terminal
Reboot to system
Done!
IMPORTANT :
* You must not reboot device to system before running multidisabler.
* This is true only in case you already have TWRP+ Multidisabler ran on existing ROM. First time using TWRP with multidisabler, you must needs to format data.
* I strongly recommend to make backup of your data though. Sometimes changes in base itself may not allow you to dirty flash (Thanks Samsung).

I am new at this , i have a s22 ultra s908u , i want to do this but i have no idea what to do and what NOT to do hahaha , thanks for any answer even good or bad :3

Jackhernandez said:
I am new at this , i have a s22 ultra s908u , i want to do this but i have no idea what to do and what NOT to do hahaha , thanks for any answer even good
Click to expand...
Click to collapse
You have to unlock bootloader(s908u I doubt) before you want to do this and most important backup your data. If you are new at this, I suggest you read some posts about root & twrp.

Jackhernandez said:
I am new at this , i have a s22 ultra s908u , i want to do this but i have no idea what to do and what NOT to do hahaha , thanks for any answer even good or bad :3
Click to expand...
Click to collapse
Your device cant be unlocked at the moment

afaneh92 said:
Your device cant be unlocked at the moment
Click to expand...
Click to collapse
Awww man , ok , i have a problem , i bought my phone but it has an app that cant be erased , sennco something , and when it starts , i cant do much because everything I download it vanish after minutes , thats why i wanna get this to earse everthing and get my device clean , well i think i have to wait

Thank you for everyone who is working hard on this ~
Really appreciate you guys for making my S22 Ultra experience better ~
Hopefully one day we can find a way to achieve r/w (read and write) permissions for /system partition to be able to do more stuff...
For now are there any alternatives to uninstall stock apps like Youtube as I want to override the Youtube app with Youtube Vanced but my Vanced is of a lower version.

Well, @afaneh92 I finally came back to Sammy. Of course, I have the S908U, which you stated cannot be unlocked. I just hope you can find a work around. I will indeed be following your progress both here and on your Telegram page. Here's wishing you all the luck. Cheers

Hi
Is it possible to mount data partition after multidisabler and format with rooted stock firmware?

sanoayyk said:
Hi
Is it possible to mount data partition after multidisabler and format with rooted stock firmware?
Click to expand...
Click to collapse
Yes you can

afaneh92 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 your 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 me for messing up your device, I will laugh at you.
Supported Models:
Galaxy S22 Ultra S908E/S9080.
Download & Guide:
1. Unlock your bootloader.
2. Downloads for S22 Ultra: b0q twrp and kernel
3. Reboot to download mode
4. Put the TWRP TAR for your device with Odin in the AP slot, vbmeta_disabled_R.tar in USERDATA slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.- Type: multidisabler again. will see - Finished. when done.- Go back to Wipe > Format Data > type yes.- Reboot to recovery.7. Flash custom kernel and magisk apk in twrp.
8. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
@Dan_FFM (David Dean) for helping with convert readonly f2fs vendor to readwrite
Donators
Sources:
Kernel tree
Device tree
Click to expand...
Click to collapse
Hello, I have magisk and TWRP and I ran the multidisabler command, but I have a problem with the mount system and I can't control the system files through Root explorer, is there a solution ?, Thank you for your efforts

7RBY said:
Hello, I have magisk and TWRP and I ran the multidisabler command, but I have a problem with the mount system and I can't control the system files through Root explorer, is there a solution ?, Thank you for your efforts
Click to expand...
Click to collapse
Not yet, system is read only.

Anyone getting this after root?

When I'm trying to backup data keep getting this....any ideas? Error 255. Thanks in advance

Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy A53 5G (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"
}
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 your 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 me for messing up your device, I will laugh at you.
Supported Models:
Galaxy A53 5G A536B, A536E, A536N & A5360
Download & Guide:
1. Unlock your bootloader.
2. Downloads for A53 5G: a53x twrp and kernel
3. Reboot to download mode
4. Put the TWRP TAR for your device with Odin in the AP slot, vbmeta_disabled_R.tar in USERDATA slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.- Type: multidisabler again. will see - Finished. when done.- Go back to Wipe > Format Data > type yes.- Reboot to recovery.7. Flash custom kernel and magisk apk in twrp.
8. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram:
Link
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@MaloyZV on telegram for testing
@ianmacd for multidisabler
@Dan_FFM (David Dean) for helping with convert readonly f2fs vendor to readwrite
Donators
Sources:
Kernel tree
Device tree

Changelog:
12.07.2022 - Initial Release.

Note1: You need a custom permissive kernel to boot with R/W vendor.
Note2: If you got bootloop on Samsung logo, reboot to TWRP and wipe metadata from Advanced Wipe section.

Hi, I am currently testing this. So far, I have only flashed the TWRP via ODIN (already have a custom ROM running).
I want to backup my data first before messing around. When I try to mount internal storage, it says 0MB.
So do I need to flash the custom kernel before I can access the data partition or internal sdcard?
Or is data access/backup not supported?

aximut said:
Hi, I am currently testing this. So far, I have only flashed the TWRP via ODIN (already have a custom ROM running).
I want to backup my data first before messing around. When I try to mount internal storage, it says 0MB.
So do I need to flash the custom kernel before I can access the data partition or internal sdcard?
Or is data access/backup not supported?
Click to expand...
Click to collapse
You cant access the data as mentioned in bug list we dont have encryption support.

afaneh92 said:
You cant access the data as mentioned in bug list we dont have encryption support.
Click to expand...
Click to collapse
I am running LineageOS (based on PHH GSI) which is not encrypted.
This is what the log says.

aximut said:
I am running LineageOS (based on PHH GSI) which is not encrypted.
This is what the log says.
View attachment 5661271
Click to expand...
Click to collapse
And what does GSI that installed to system has to do with data encryption?
If you are worried about your data just move them to pc
And if you are worried about encryption simply dont use twrp.

afaneh92 said:
And what does GSI that installed to system has to do with data encryption?
If you are worried about your data just move them to pc
And if you are worried about encryption simply dont use twrp.
Click to expand...
Click to collapse
The GSI has no support for userdata encryption, which means that the internal data can't be encrypted (and should be unencrypted in /data). Otherwise I would not be able to boot into the ROM. But maybe I am wrong on this.
So if I reformat my data and run the multidisabler, does that mean I can access data in TWRP even having a custom ROM?

aximut said:
The GSI has no support for userdata encryption, which means that the internal data can't be encrypted (and should be unencrypted in /data). Otherwise I would not be able to boot into the ROM. But maybe I am wrong on this.
So if I reformat my data and run the multidisabler, does that mean I can access data in TWRP even having a custom ROM?
Click to expand...
Click to collapse
Yes after running multidisabler and formatting data. You might able to boot GSI without custom kernel but not stock

afaneh92 said:
Yes after running multidisabler and formatting data. You might able to boot GSI without custom kernel but not stock
Click to expand...
Click to collapse
OK thanks. What partition does the multidisabler actually patch to disable encryption? System? Or boot?

aximut said:
OK thanks. What partition does the multidisabler actually patch to disable encryption? System? Or boot?
Click to expand...
Click to collapse
Vendor is ro, it convert it to rw then patch vendor/etc/fstab.exynos****

TWRP and your kernel work in A536N, But root and /system are still ro
I installed stock May 24 firmware with magisk patched before installing TWRP
P.S ) I have to clear dalvik & cache every reboot

gckim250 said:
TWRP and your kernel work in A536N, But root and /system are still ro
I installed stock May 24 firmware with magisk patched before installing TWRP
P.S ) I have to clear dalvik & cache every reboot
Click to expand...
Click to collapse
Yes as I said earlier only vendor is rw to disable encryption. We cant do the same for system as the size doesn't fit.

Ah, Biometrics lockscreen from stock ROM conflicts with SafetyNet Fix module...
That's why I have to clear that every reboot...

Are there any roms available for the A53? Because I was looking for twrp .zip files for this phone, and couldn't find anything for this model.

Lowkeys said:
Are there any roms available for the A53? Because I was looking for twrp .zip files for this phone, and couldn't find anything for this model.
Click to expand...
Click to collapse
phh's AOSP, LineageOS GSI, Pixel Experience GSI are only available for A53 at this time
vndklite version of these can be installed via fastboot mode!
If you want zip-flashing rom, waiting is the only soulution unfortunately
Pixel GSI : https://github.com/ponces/treble_build_pe/releases/download/
phh's AOSP : https://github.com/phhusson/treble_experimentations/releases
Lineage GSI : https://forum.xda-developers.com/t/gsi-12-lineageos-19-x-gsi-a64b-64b.4358041/

gckim250 said:
phh's AOSP, LineageOS GSI, Pixel Experience GSI are only available for A53 at this time
vndklite version of these can be installed via fastboot mode!
If you want zip-flashing rom, waiting is the only soulution unfortunately
Pixel GSI : https://github.com/ponces/treble_build_pe/releases/download/
phh's AOSP : https://github.com/phhusson/treble_experimentations/releases
Lineage GSI : https://forum.xda-developers.com/t/gsi-12-lineageos-19-x-gsi-a64b-64b.4358041/
Click to expand...
Click to collapse
If I were to download phh's AOSP extended for the Samsung galaxy A53 would I have to get the vanilla version? Also when downloading due I have to extract the img.xz file to just get the .img file, and then using an sd card put the file on the phone to flash?
Note my phone model is SM-A536E/DS.

Lowkeys said:
If I were to download phh's AOSP extended for the Samsung galaxy A53 would I have to get the vanilla version? Also when downloading due I have to extract the img.xz file to just get the .img file, and then using an sd card put the file on the phone to flash?
Note my phone model is SM-A536E/DS.
Click to expand...
Click to collapse
gapps = google apps (e.g play store)
vanilla = no google apps
You should install that via TWRP fastboot mode! (or fastbootd)
In fastboot, you may need USB 2.0 port
P.S) my phone is A536N + stock ROM
Treble Info : https://play.google.com/store/apps/details?id=tk.hack5.treblecheck

Will this work on my sm-a536w?

redliner79 said:
Will this work on my sm-a536w?
Click to expand...
Click to collapse
Your bootloader cant be unlocked currently

Database Info

welcome