Develop Bugs

[Recovery][v3.0.0][Curtana] Unofficial PBRP Recovery

{
"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:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're 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.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
This particular build is based on the amazing work done by the PBRP team and Joyeuse devs with some little changes to get it working on Curtana.
This build is really experimental so flash at your own risk.
However, the main use cases are fully covered as the most important functions of the recovery are working correctly.
Working
Data decryption
Flash
Wipe and format data
Backup and restore
Bugs
ADB sideload
Flashing Magisk results in bootloop: if you want to use Magisk you can patch a "boot.img" file from Magisk Manager and then flash that img to the Boot partition from recovery.
The recovery always asks for encryption password, even if the device is not encrypted: if your device is not encrypted just press cancel and it will work just fine.
Error 7 when flashing a ROM: check that System, Vendor and Product partitions are not mounted in the Mount section of the recovery before flashing a ROM.
Changelog
20200730
Updated to the new 3.0 UI
Language selection now works properly
Timezone selection now works properly
20200722
Initial Build
Downloads
20200730
20200722
Source Code
android_device_xiaomi_curtana-pbrp

Hey,
great work!
thanks!
I saw on github you changed that version from joyeuse to curtana.
Would you be able to compile a joyeuse version too for all the joyeuse owners?
Add it here too and change the title [curtana-joyeuse]?
I've unpacked your version and changed build.prop and repacked.
It's working beautifully on my joyeuse_eea device.
It is the only version that:
- does not lock touch after wake up
- can decrypt
- is not closed source as LR-twrp
- backup works
So great work!
PS: have no clue howto compile myself, otherwise I would have tried that path

kheno said:
Hey,
great work!
thanks!
I saw on github you changed that version from joyeuse to curtana.
Would you be able to compile a joyeuse version too for all the joyeuse owners?
Add it here too and change the title [curtana-joyeuse]?
I've unpacked your version and changed build.prop and repacked.
It's working beautifully on my joyeuse_eea device.
It is the only version that:
- does not lock touch after wake up
- can decrypt
- is not closed source as LR-twrp
- backup works
So great work!
PS: have no clue howto compile myself, otherwise I would have tried that path
Click to expand...
Click to collapse
Hi!
dungphp already did a version of PBRP for joyeuse that you can download here:
https://androidfilehost.com/?fid=8889791610682886707
On the other hand PBRP devs are working on a official device tree for joyeuse, but as far as I know there are still no official builds. You can check their progress here:
https://github.com/PitchBlackRecoveryProject/android_device_xiaomi_joyeuse-pbrp

Hey,
Thanks for the info.
For some reason the version of dungphp did not backup the existing install.
Can't remember the actual error.
Another version was 3.4.0 and did not decrypt.
So i stated looking into altering different curtana versions.
The LR twrp is closed source and locks up touch after waking up from sleep.
This version works flawlessly for me. 
I will track the progress of the official build.
Many thanks!

@end222 after flashing joyeuse version of recovery, recovery booted fine but internal storage folders have random names and no files in them, also backup dont work with error that folders dont exist or something like that, also phone didn't been able to boot system after installing recovery.I needed to reflash stock firmware to fix system.Any ideas?

You shouldn't have installed any recoveries because they are in alpha phase.
You can install some roms by using factory recovery and fastboot.

Thanks for the recovery.
patch a "boot.img" file from Magisk Manager and then flash that img to the Boot partition from recovery.
Click to expand...
Click to collapse
Which boot image should I patch and then flash?

mtolgae said:
Thanks for the recovery.
Which boot image should I patch and then flash?
Click to expand...
Click to collapse
You have to patch the image of the ROM you're using. To get it just extract the ROM's zip and you'll see it

end222 said:
You have to patch the image of the ROM you're using. To get it just extract the ROM's zip and you'll see it
Click to expand...
Click to collapse
Thanks

Updated to 20200730:
- New 3.0 UI
- Language selection works well now
- Timezone selection works fine as well

Flashing Magisk results in bootloop: if you want to use Magisk you can patch a "boot.img" file from Magisk Manager and then flash that img to the Boot partition from recovery.
Click to expand...
Click to collapse
If I flash the patched boot image, will it be fully rooted or will my device get bricked by file mangers like other's in the forum have mentioned?

Yoss Roness said:
If I flash the patched boot image, will it be fully rooted or will my device get bricked by file mangers like other's in the forum have mentioned?
Click to expand...
Click to collapse
It should work just fine. I've been using the recovery as a daily driver ever since I released the build and I've flashed Magisk using that method several times, all of them successfully.

end222 said:
It should work just fine. I've been using the recovery as a daily driver ever since I released the build and I've flashed Magisk using that method several times, all of them successfully.
Click to expand...
Click to collapse
Great, thank you!

Thank you
Sent from my Redmi Note 9 Pro using Tapatalk

is it safe to install this recovery over lr-twrp? i don't want to reinstall my whole phone btw. thanks for this project!!

keiner99 said:
is it safe to install this recovery over lr-twrp? i don't want to reinstall my whole phone btw. thanks for this project!!
Click to expand...
Click to collapse
Yes, at least I did...
Sent from my Redmi Note 9S using Tapatalk

how you guys install ROMs? i did everything described in Bugs Section... unmount system, vendor, product.
press cancel and ignore encryption password.
then i try to install mi-globe rom and get error 256 because system partition is unmounted

trinity_user said:
how you guys install ROMs? i did everything described in Bugs Section... unmount system, vendor, product.
press cancel and ignore encryption password.
then i try to install mi-globe rom and get error 256 because system partition is unmounted
Click to expand...
Click to collapse
I have the same issue with miglobe Rom it endet up in System unmounted and Read Only... After that only flash the original Rom with MiFlash fixed this.
With the EU ROM everythings OK.
I have the Issue with LRTWRP to.
I think the Script from MIGlobe ROM that run after flash the .zip - doest work with the unoficial TWRP Versions for now...

Timmiotool said:
I have the same issue with miglobe Rom it endet up in System unmounted and Read Only... After that only flash the original Rom with MiFlash fixed this.
With the EU ROM everythings OK.
I have the Issue with LRTWRP to.
I think the Script from MIGlobe ROM that run after flash the .zip - doest work with the unoficial TWRP Versions for now...
Click to expand...
Click to collapse
sounds logical to me. hm and its possible to fix this? @end222

Method installation
Thanks for the recovery, in the post initial no have installation explication, is "fastboot flash recovery filename.img" the best method? Or fastbootd? I just unlocked the bootloader. Thanks.

[RECOVERY][3.5.2_9-2][Mi A2 Lite] Unofficial TWRP recovery for Xiaomi Mi A2 Lite

{
"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:
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.
*
*/
Features:
- Open Source
- Payload.bin support (ROM flashing works)
- Proper MTP support (for both 4.9 and 3.18 kernels)
- Working decryption for both FBE and FDE
- Adoptable Storage is working
- Android 11 support (No bootloops to recovery mode)
- NTFS, F2FS, exFAT, FAT32 support for SD Cards and USB drives
- Ability to flash splash images directly to the splash partition
- Adjusted theme to account for the notch (the clock doesn't overlap with the notch)
- No TWRP app installation prompts
- Older 3.4.0 button-style reboot menu instead of the newer listbox-style one
- Addon.d script to make TWRP survive ROM updates
Download:
TWRP image: https://drive.google.com/file/d/19ysSbW31NG4QF5OClbox-mArIb17KbpT/view?usp=sharing
TWRP Installer: https://drive.google.com/file/d/1-wk_0kOe_e-2XDDiv08BxJhn1ixWXjUw/view?usp=sharing
Installation Instructions:
- Make sure your bootloader is unlocked. If not, unlock it first.
- Reboot to Bootloader (aka Fastboot mode)
- Execute:
Code:
fastboot boot twrp-3.5.2_9-2-daisy-unofficial.img
- Flash the TWRP Installer zip to keep TWRP permanently
Notes:
- You can ignore any "Failed to unmount /vendor: Device or resource busy" errors since they do not cause any issues (this
happens when switching the active slot while the vendor partition is mounted).
- This TWRP does not have the newer 3.5.0 theme changes in the reboot menu because it is confusing for a significant amount
of users and does not match the rest of the button-style design.
- The TWRP app checks and prompts have been completely removed due to the app causing a lot of issues including bootloops
since it is not designed for A/B devices.
- The portrait_hdpi theme has been adjusted to have more padding in the status bar and to account for the presence of the
notch (the clock's position has been modified in order for the clock not to get overlapped by the notch)
- TWRP's addon.d will only work in the following scenarios:
a) When updating your ROM through the ROM's Updater application
b) When dirty-flashing a newer build of the same ROM you have installed from recovery
- TWRP's addon.d (TWRP survival) may not work in all ROMs as some ROMs choose not to have permissive update-engine domain. This essentially results in SELinux denials, preventing the addon.d script from executing when SELinux is enforcing. You can read more about the said issue here (https://github.com/topjohnwu/Magisk/commit/cba0d040000d6ff38c6646bb9d7daa12beae2878)
Source code:
Recovery Source: https://github.com/LinkBoi00/android_bootable_recovery
Device tree: https://github.com/LinkBoi00/twrp_device_xiaomi_daisy
Kernel source: https://github.com/LinkBoi00/twrp_kernel_xiaomi_daisy
XDA:DevDB Information
TWRP-3.5.2_9-2-Unofficial, Tool/Utility for the Xiaomi Mi A2 Lite
Contributors
LinkBoi
Source Code: https://github.com/LinkBoi00/twrp_device_xiaomi_daisy
Version Information
Status: Stable
Current Stable Version: 3.5.2_9-2
Stable Release Date: 2021-05-04
Created 2020-10-19
Last Updated 2021-05-04

Reserved

Reserved

i'll give a try. still using twrp-3.3.1-dees_troy-daisy cuz its the only one that doenst ask a decrypt key that i dont have

Antho02 said:
i'll give a try. still using twrp-3.3.1-dees_troy-daisy cuz its the only one that doenst ask a decrypt key that i dont have
Click to expand...
Click to collapse
decryption does not work in this build, im looking into a fix. Custom roms do not support decryption anyways so it's a minor issue for now

The handling of the "Adoptable Storage" still broken.
E:Failed to mount decrypted adoped storage device
Click to expand...
Click to collapse
DATA is not encrypted (I use a custom ROM with Force-Encryption-Disabler)

PC295 said:
The handling of the "Adoptable Storage" still broken.
DATA is not encrypted (I use a custom ROM with Force-Encryption-Disabler)
Click to expand...
Click to collapse
Can you send me logs of that issue (advanced > copy log > tick the "include kernel log" option and swipe in the "bar")? After doing this can you also try official twrp and tell me if that has the same issue?
Thanks for the feedback
PS: Can you join a telegram group (https://t.me/XMiA2Lite)? If /When you join there, mention me (@runrunrun00) and your issue, thanks in advance

The problem is with all TWRPs. (Official, Offain, this)
I have to use OTG to install Custom ROMs etc.
It is probably not a TWRP problem but one of the CustomROMs?
Unfortunately, I also find that there are adoptable storage issues in many custom ROMs.
It got noticeably worse with Android 10 ROMs.
For example the migration via key file (/data/misc/vold/....key) does not work everywhere.
Or the memory only works after setting up the microSD several times.
Log attached...

PC295 said:
The problem is with all TWRPs. (Official, Offain, this)
I have to use OTG to install Custom ROMs etc.
It is probably not a TWRP problem but one of the CustomROMs?
Unfortunately, I also find that there are adoptable storage issues in many custom ROMs.
It got noticeably worse with Android 10 ROMs.
For example the migration via key file (/data/misc/vold/....key) does not work everywhere.
Or the memory only works after setting up the microSD several times.
Log attached...
Click to expand...
Click to collapse
i might have found a way to fix this issue (in the bootable twrp, the installed one depends on your rom)

again, with twrp Bogdan, for my work fine, no problem with storage external

dochdoc said:
again, with twrp Bogdan, for my work fine, no problem with storage external
Click to expand...
Click to collapse
what problem do you have with external storage?

dochdoc said:
again, with twrp Bogdan, for my work fine, no problem with storage external
Click to expand...
Click to collapse
what's your issue exactly?

nothing, no problem with this custom recovery (TWRP 3.3.1 by @ScaryMen1325), work fine with me

dochdoc said:
nothing, no problem with this custom recovery (TWRP 3.3.1 by @ScaryMen1325), work fine with me
Click to expand...
Click to collapse
And what's the issue with this recovery regarding external storage (not scarymen's)?

LinkBoi said:
And what's the issue with this recovery regarding external storage (not scarymen's)?
Click to expand...
Click to collapse
If you only boot from TWRP, you can't access Adptable Storage.
There is an installed TWRP required.

PC295 said:
If you only boot from TWRP, you can't access Adptable Storage.
There is an installed TWRP required.
Click to expand...
Click to collapse
Is it possible to contact me on telegram again? I have one version in test that most likely fixes your issue

When I use Offain TWRP PC output is like this
Code:
downloading 'boot.img'...
OKAY [ 15.830s]
booting...
OKAY [ 0.748s]
finished. total time: 16.578s
and then phone reboot to stock Android
When I use TWRP from this thread PC output is same but phone boot Android Recovery and it says Can't load Android system. Your data be corrupt and there are 2 options Try Again and Factory Reset when I try again it boots to stock.

Yyres55 said:
When I use Offain TWRP PC output is like this
Code:
downloading 'boot.img'...
OKAY [ 15.830s]
booting...
OKAY [ 0.748s]
finished. total time: 16.578s
and then phone reboot to stock Android
When I use TWRP from this thread PC output is same but phone boot Android Recovery and it says Can't load Android system. Your data be corrupt and there are 2 options Try Again and Factory Reset when I try again it boots to stock.
Click to expand...
Click to collapse
If you want, you can contact me on telegram, I might have a fixed version there

LinkBoi said:
If you want, you can contact me on telegram, I might have a fixed version there
Click to expand...
Click to collapse
It worked. I tried another USB port and it's okay

hi, is there any plan to support encryption??

biladina.id said:
hi, is there any plan to support encryption??
Click to expand...
Click to collapse
Yup, of course. In the next release, 3.5.0, every bug I listed will be fixed, including Decryption, Android 11 support and more. If you want to test the release candidate (which is still 3.4.0 because twrp hasn't released 3.5.0 yet), you can join the telegram group below:
www.t.me/DaisyTestflight
New update will be released in XDA when TeamWin releases 3.5.0

[RECOVERY][UNOFFICIAL] TWRP for Galaxy S10 (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 S10 G9730, G973U, G973U1 and G973W.
US/Canada bootloader unlock thread:
here
Download & Guide:
1. Unlock your bootloader.
2. Download S10: beyond1qlte.
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
@Mentalmuso for base device tree
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree

Changelog:
30.11.2021 - Update to TWRP 3.6.0
- Update multidisabler
10.03.2021 - Update to latest TWRP source
- Add terminal multidisabler script
- fstab cleanup.
16.02.2021 - Initial R build for Android 11
31.12.2020 - Update TWRP to 3.5.0
14.11.2020 - Initial Release

Seems to be working properly! Thank you!

wow we can unlock Bootloader and install Custom recovery on the US Galaxy S10 now, great!

robocopvn said:
wow we can unlock Bootloader and install Custom recovery on the US Galaxy S10 now, great!
Click to expand...
Click to collapse
It isn't free, but yes. Mine is and rooted. Verizon variant here.

abranson said:
It isn't free, but yes. Mine is and rooted. Verizon variant here.
Click to expand...
Click to collapse
Can you elaborate on how you unlocked the bootloader on the Snapdragon variant? I waited 7 days, but the oem unlock option is still not showing.

superturtlr19 said:
Can you elaborate on how you unlocked the bootloader on the Snapdragon variant? I waited 7 days, but the oem unlock option is still not showing.
Click to expand...
Click to collapse
I had to pay and had it done remotely. Sampwnd. . Google it

abranson said:
I had to pay and had it done remotely. Sampwnd. . Google it
Click to expand...
Click to collapse
Oh wow, these are pricey. Well thank you for your time.

Deleted

afaneh92 said:
Note: download link is down, will make new build tomorrow then will fix the link. Please do not share older builds.
Edit: new builds are up, US devices are not supported anymore, only devices already unlocked before 9 November are.
Click to expand...
Click to collapse
Any chance US model support coming? Any insight why it's so much harder? I don't know anything about it

illspiritX said:
Any chance US model support coming? Any insight why it's so much harder? I don't know anything about it
Click to expand...
Click to collapse
Read notes on OP

afaneh92 said:
Read notes on OP
Click to expand...
Click to collapse
I'd like to request to use the new twrp builds. I got unlocked after November, though. what do I need to provide if you are to grant the green light to use?

abranson said:
I'd like to request to use the new twrp builds. I got unlocked after November, though. what do I need to provide if you are to grant the green light to use?
Click to expand...
Click to collapse
Will contact you on telegram

Thank you very much @afaneh92, I followed the procedure and was able to install TWRP and magisk, and everything is working fine.
The only thing that I'm not able to do is to re-encrypt the phone at the end. The encription procedure starts, but then it is stuck for hours on the "encrypting..." screen and nothing happens. I tried to temporarily remove magisk and also to restore the recovery partition, but nothing seems to work. Do you know if there is any workaround?

fabiokino said:
Thank you very much @afaneh92, I followed the procedure and was able to install TWRP and magisk, and everything is working fine.
The only thing that I'm not able to do is to re-encrypt the phone at the end. The encription procedure starts, but then it is stuck for hours on the "encrypting..." screen and nothing happens. I tried to temporarily remove magisk and also to restore the recovery partition, but nothing seems to work. Do you know if there is any workaround?
Click to expand...
Click to collapse
To encrypted the the data partition again need to do factory reset from stock recovery.

afaneh92 said:
To encrypted the the data partition again need to do factory reset from stock recovery.
Click to expand...
Click to collapse
Thank you for the answer. My idea was to make a TWRP image once I completely personalized the system and then encrypt the device, but I understand that it's not possible...
So the alternative solution is to find a way yo make an image of the encrypted device after the personalization...
Is there a way to make an image of the encrypted data partition apart from using dd? Since it is encrypted with fbe I was wondering if there's a method which doesn't require to save the whole partition but only the actual (encrypted) files.

Changelog:
16.02.2021 - Initial R build for Android 11

Does anyone with a SM-G9730 wanna try a US rom I made for it?

how to disable AVB in s10 9730?

jrkruse said:
Does anyone with a SM-G9730 wanna try a US rom I made for it?
Click to expand...
Click to collapse
9730 module can flash us version? I wanna try

[RECOVERY][UNOFFICIAL] TWRP for Galaxy Note 10 (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 Note 10 N9700, N970U, N970U1 and N970W.
US/Canada bootloader unlock thread:
here
Download & Guide:
1. Unlock your bootloader.
2. Download Note 10: d1q.
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
Telegram account
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@Mentalmuso for base device tree
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree

Changelog:
30.11.2021 - Update to TWRP 3.6.0
- Update multidisabler
10.03.2021 - Update to latest TWRP source
- Add terminal multidisabler script
- fstab cleanup.
16.02.2021 - Initial R build for Android 11
01.01.2021 - Initial Release

How are we unlocking the Bootloader? Message me when you have time.

I have Windows 10 and drivers are installed. I got nothing going on today so anytime will work. If today works for you

menace211 said:
How are we unlocking the Bootloader? Message me when you have time.
Click to expand...
Click to collapse
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
USA/Canada - Samsung Bootloader Unlock
You can view and join @Afaneh92UnlockChannel right away.
t.me
I will PM you too.
Gregbmil1 said:
I have Windows 10 and drivers are installed. I got nothing going on today so anytime will work. If today works for you
Click to expand...
Click to collapse
Ok thats fine.

Just wanted to let people know, if you're on the fence about this, its 100% legit. Thanks again!

Question. How do we flash multidisabler in TWRP if its encrypted in TWRP? I can't find anything in it

Gregbmil1 said:
Question. How do we flash multidisabler in TWRP if its encrypted in TWRP? I can't find anything in it
Click to expand...
Click to collapse
Push the file through adb or use Micro SD or USB-OTG.

afaneh92 said:
Push the file through adb or use Micro SD or USB-OTG.
Click to expand...
Click to collapse
OTG worked great!! Thank You.

Anyone having an issue creating a backup in TWRP? I tried saving it with OTG and internal memory. It always gets to about 21% then it reboots back into TWRP with no backup created

Gregbmil1 said:
Anyone having an issue creating a backup in TWRP? I tried saving it with OTG and internal memory. It always gets to about 21% then it reboots back into TWRP with no backup created
Click to expand...
Click to collapse
Android 11?

Yes, Android 11

Gregbmil1 said:
Yes, Android 11
Click to expand...
Click to collapse
TWRP kernel based on Android 10, wait for 11 kernel source to be released.

Changelog:
16.02.2021 - Initial R build for Android 11

So there will not be a way to unlock the phone without paid service? Seems shifty. There are developers here in the XDA community ths

Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy S22 (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 S901E/S901N/S9010.
Download & Guide:
1. Unlock your bootloader.
2. Downloads for S22: AFH: r0q twrp and kernel / Drive: r0q 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

Is there a kernel for 901E?
Can only seem to find one for 901b
EDIT: found what I needed in the telegram group snapdragon models use the same kernel

i flashed twrp in fw ave4 , after flash kernel, wipe data, and get bootloop, how fix?

skinza said:
Is there a kernel for 901E?
Can only seem to find one for 901b
EDIT: found what I needed in the telegram group snapdragon models use the same kernel
Click to expand...
Click to collapse
send me kernel bro please...

Tonystarki said:
i flashed twrp in fw ave4 , after flash kernel, wipe data, and get bootloop, how fix?
Click to expand...
Click to collapse
you ran multidisabler?

Tonystarki said:
send me kernel bro please...
Click to expand...
Click to collapse
Dont flash wrong kernel, if you have snap use the link from this thread

afaneh92 said:
Dont flash wrong kernel, if you have snap use the link from this thread
Click to expand...
Click to collapse
calm down, I will not install the wrong kernel

running the multidisabler is essential to install the custom kernel, the device does not start but runs multidisabler, all right now, what customizations does the kernel have? @afaneh92

Tonystarki said:
running the multidisabler is essential to install the custom kernel, the device does not start but runs multidisabler, all right now, what customizations does the kernel have? @afaneh92
Click to expand...
Click to collapse
permissive and disabled security

Please lmk if you get it working
I flashed on s22 veh and lost WiFi
Then when phone screen went to sleep I couldbt wake it up
Followed the instructions

skinza said:
Please lmk if you get it working
I flashed on s22 veh and lost WiFi
Then when phone screen went to sleep I couldbt wake it up
Followed the instructions
Click to expand...
Click to collapse
Will look into it

afaneh92 said:
Flash custom kernel and magisk apk in twrp
Click to expand...
Click to collapse
Is this step to root the Phone？

sinaamos said:
Is this step to root the Phone？
Click to expand...
Click to collapse
You can skip magisk if you don't want root

Just got my S901E on FW U1AVCJ. Is it safe to update to U2AVF1 before installing TWRP? Just making sure I will be able to unlock BL and install TWRP. Thanks in advance!

Daemonite said:
Just got my S901E on FW U1AVCJ. Is it safe to update to U2AVF1 before installing TWRP? Just making sure I will be able to unlock BL and install TWRP. Thanks in advance!
Click to expand...
Click to collapse
Its ok

hi there!
i would love to follow this tutorial, however, i have some noob doubts before doing it that i would like to address:
1) what does it mean r0q? "Downloads for S22: r0q twrp and kernel"
2) how should i decide which files download in twrp? what does it mean afaneh92-r0q? its for S22 non-ultra
3) why can i download the custom kernel in point 7 if there is no custom kernel for s22 non-ultra?
4) the custom kernel of point 7 must be flashed through twrp?

r0q is regular s22
The s22, s22+ and ultra all use the exact same kernel

skinza said:
r0q is regular s22
The s22, s22+ and ultra all use the exact same kernel
Click to expand...
Click to collapse
thank you! i have managed to make it work! i dont think it's related but i cant wipe system partition since its not present in the twrp wipe section... perhaps i am missing something?