[RECOVERY][UNOFFICIAL] TWRP for Galaxy A11 (Snapdragon) - Miscellaneous Android Development

{
"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 A11 A115F and A115M.
Download & Guide:
1. Unlock your bootloader.
2. Download Galaxy A11 : a11q.
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:
Link
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree

Changelog:
29.11.2021 - Update to TWRP 3.6.0
- Add Symlinked dynamic partitions to fstab
- Update multidisabler
- fstab clean up
03.03.2021 - Update to latest TWRP source
- Add terminal multidisabler script
- fstab cleanup.
17.12.2020 - Update to latest TWRP source
- Fixed fastbootd
- Fixed external_sd and usb-otg mount points.
02.12.2020 - Initial Release.

reserved for fastboot guide

I have a SM-A115M/DS and I tried to flash the multidisabler and get this error!!!
please help me!

JoKeRBrAzZiL said:
I have a SM-A115M/DS and I tried to flash the multidisabler and get this error!!!
please help me!View attachment 5153865
Click to expand...
Click to collapse
Use latest version multidisabler-samsung-2.6c-afaneh92.zip

MY A115F not booting into recovery after flashing .tar file???solution
please help @afaneh92

musamalyk said:
MY A115F not booting into recovery after flashing .tar file???solution
please help @afaneh92
Click to expand...
Click to collapse
You need to boot into twrp immediately, press both volume buttons and connect usb at logo after first reboot.

afaneh92 said:
You need to boot into twrp immediately, press both volume buttons and connect usb at logo after first reboot.
Click to expand...
Click to collapse
it did not work ..please guide more clearly after installing .tar file using odin i m not able to boot into twrp recovery only my samsung keep restating on galaxy a11 ..may be its model difference because i m using Asian model of A11 from Pakistan @afaneh92

musamalyk said:
it did not work ..please guide more clearly after installing .tar file using odin i m not able to boot into twrp recovery only my samsung keep restating on galaxy a11 ..may be its model difference because i m using Asian model of A11 from Pakistan @afaneh92
Click to expand...
Click to collapse
Oh sorry I gave you the wrong instruction.
I have the A115F which is same as your device.
After flashing the tar file, press power and volume up, then release power at logo and keep vol up pressed until you see twrp logo.

hopefully it will work???
have you tried any GSI project treble Rom in your A11
if yes then please tell which one????

i tried it did not work because to stop downlaoding mode need combination of volume down plus power key instead of volume up ..there is not any twrp ....
" press power and volume up, then release power at logo and keep vol up pressed until you see twrp logo" again wrong
please help

musamalyk said:
hopefully it will work???
have you tried any GSI project treble Rom in your A11
if yes then please tell which one????
Click to expand...
Click to collapse
Yes, lineage-18.0-20201120-UNOFFICIAL-treble_a64_bvS installed

musamalyk said:
i tried it did not work because to stop downlaoding mode need combination of volume down plus power key instead of volume up ..there is not any twrp ....
" press power and volume up, then release power at logo and keep vol up pressed until you see twrp logo" again wrong
please help
Click to expand...
Click to collapse
If you disable auto reboot from odin, then you can reboot using vol down and power, after screen goes black press vol up and power until you got to boot logo. then keep vol up.

afaneh92 said:
Yes, lineage-18.0-20201120-UNOFFICIAL-treble_a64_bvS installed
Click to expand...
Click to collapse
please provide link

musamalyk said:
please provide link
Click to expand...
Click to collapse
Andy Yan's personal builds // GSI
Download Andy Yan's personal builds // GSI for free. None
sourceforge.net

New build up.
- Update to latest TWRP source, Fixed fastbootd, Fixed external_sd and usb-otg mount points.

So where is yours build of LOS 18.0? I see there only the LOS 17.1

griha41 said:
So where is yours build of LOS 18.0? I see there only the LOS 17.1
Click to expand...
Click to collapse
Im not building ROMs, those are GSI. Not my own builds.

afaneh92 said:
Im not building ROMs, those are GSI. Not my own builds.
Click to expand...
Click to collapse
Ok. o you pick it from testing branch? And how do you install LOS? I'm tryin' with ADB Sideload but on my SM-A115F it's failed to start (I'm using TWRP that you had placed in this topic.)

griha41 said:
Ok. o you pick it from testing branch? And how do you install LOS? I'm tryin' with ADB Sideload but on my SM-A115F it's failed to start (I'm using TWRP that you had placed in this topic.)
Click to expand...
Click to collapse
Extract to img and flash using fastboot to system, then flash magisk.
Only a64_bvS can work on A11

Related

[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][UNOFFICIAL] TWRP for Galaxy S21+ (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 S21+ G996B/N.
Download & Guide:
1. Unlock your bootloader.
2. Download S21+: t2s.
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 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
Sources:
Kernel tree
Device tree
Changelog:
29.11.2021 - Update to TWRP 3.6.0
- Updated to latest kernel source
- Update multidisabler
- fstab clean up
21.08.2021 - Add Symlinked dynamic partitions to fstab
- Fix dtbs issue from previous build
09.08.2021 - Fix haptic feedback
- Updated to latest kernel source
- No vbmeta disable require
- fstab clean up
03.03.2021 - Initial Release.
Nice to hear, now I am a bit more tempted to get an S21+
I hope roms will follow
I have error trying do backup. Folder optics make crash and reboot to twrp again. My first backup was fully all folders but now every crash on optics. Still great work
Ziomus said:
I have error trying do backup. Folder optics make crash and reboot to twrp again. My first backup was fully all folders but now every crash on optics. Still great work
Click to expand...
Click to collapse
have you disabled encryption? and logs?
afaneh92 said:
have you disabled encryption? and logs?
Click to expand...
Click to collapse
Yes multi 2x times wipe data Yes reboot. Ive acces to whole data. How to make log for you that will help you? And like i was saying first backup super partition for me was succesful. Then i delete it and trying make new backup, and starts in middle of work. I Discovery that is "optics" folder So now i make backups without it (4Mb data inside optics"
internal memory is corrupted after FactoryReset !!!
any fix
czar22 said:
internal memory is corrupted after FactoryReset !!!
any fix
Click to expand...
Click to collapse
Format data and type yes.
still no FIX
I rewrote the firmware and took it from 0
czar22 said:
still no FIX
I rewrote the firmware and took it from 0
Click to expand...
Click to collapse
Then you are doing something wrong
czar22 said:
still no FIX
I rewrote the firmware and took it from 0
Click to expand...
Click to collapse
We're you on the newest update before unlocking bootloader and installing twrp
is there a TWRP [AUF6] version ????
czar22 said:
is there a TWRP [AUF6] version ????
Click to expand...
Click to collapse
my twrp can work on v3 bootloader, the twrp in the link taken without authorship.
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 S21+ G996B/N.
Download & Guide:
1. Unlock your bootloader.
2. Download S21+: t2s.
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 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
Sources:
Kernel tree
Device tree
Click to expand...
Click to collapse
hello, will this work on my device that has SM-G996B/DS as an model number? thanks!
Redisity said:
hello, will this work on my device that has SM-G996B/DS as an model number? thanks!
Click to expand...
Click to collapse
Yes check supported devices in OP
Hi, i just updated my S21+ Exynos to android 12. It's rooted with magisk and just installed the last TWRP.
But I'm gettin 255 error when trying to backup data. I've been told that TWRP can't backup android 12 data, is that true? There is any workaround? And any hope for this to be fixed?
ffp. said:
Hi, i just updated my S21+ Exynos to android 12. It's rooted with magisk and just installed the last TWRP.
But I'm gettin 255 error when trying to backup data. I've been told that TWRP can't backup android 12 data, is that true? There is any workaround? And any hope for this to be fixed?
Click to expand...
Click to collapse
Try to check recovery log and delete the folders causing the error
afaneh92 said:
Try to check recovery log and delete the folders causing the error
Click to expand...
Click to collapse
I did that, it was a dalvick-cache folder. I moved it. But then the backup failed again because another completely different folder...
ffp. said:
I did that, it was a dalvick-cache folder. I moved it. But then the backup failed again because another completely different folder...
Click to expand...
Click to collapse
Yes need to remove it as well
afaneh92 said:
Yes need to remove it as well
Click to expand...
Click to collapse
How can i know they aren't important? Is this Twrp unable to decrypt android 12 encryption true? And what if I get another error with another folder?

Development [U1][Recovery][Unofficial][A525X]OrangeFox Recovery 11.1

OrangeFox Recovery Project
{
"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"
}
Huge thanks to @geekmaster21 for making this a reality​
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 doing this to your device
* 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.
*/
Disclaimer:
- I do not claim this work as my own, this thread was created to have an XDA thread for A52 OrangeFox Recovery. I will try my best to keep it up to date with @geekmaster21 's work, but can't promise that will remain for ever. If you want the latest OrangeFox Recovery and to be notified as soon as its published, be sure to join the Telegram channel.
- I am not responsible about any damage of any kind that this custom binary may cause.
- Please read the whole main post & related ones before proceed and follow the guide as it is wrote. I will not offer support for any issues that have been already stated.
- Your Knox Warranty Bit will be blown once you flash this or others custom binaries, preventing you to use Knox Features. It can't be reset in any way, so think twice before flashing this.
- Bugs can be reported here in XDA or via our Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs (device variant and logcat).
How to Install:
First, you need to unlock the bootloader. Here's how to do it:
- Backup all media before proceeding, this will erase everything in your internal storage including music and photos
- Go to developer settings and enable [OEM Unlock]
- Reboot to download mode
- When prompted, press and hold VOL + to enter bootloader unlock mode
- Press VOL + to confirm you want to unlock bootloader, this will wipe your data
- If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
- Go through the initial setup. Skip through all the steps since data will be wiped again later when we flash OrangeFox and magisk
- Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader. This step is MANDATORY
- Your bootloader now accepts unofficial images in download mode.
After finally unlocking the bootloader, proceed with installing OrangeFox Recovery(tar) with Odin:
- Boot to download mode and load VBMeta disabler tar file in AP of Odin
- Disable [Auto Reboot] in Odin
- Flash
- Force a reboot by pressing VOL - and POWER buttons at the same time
- After the screen goes black, IMMEDIATELY let go of all buttons and IMMEDIATELY press and hold VOL+ and VOL - button at the same time to boot to download mode again
- Now, add OrangeFox tar in AP of Odin
- Disable [Auto Reboot] in Odin
- Flash
- Force a reboot by pressing VOL - and POWER buttons at the same time
- After the screen goes black, IMMEDIATELY let go of all buttons and IMMEDIATELY press and hold VOL+ and POWER button at the same time to boot to OrangeFox Recovery
- After booting to recovery successfully, go to WIPE in OrangeFox
- You should see an option to FORMAT DATA. After you select it, you will be asked to type "yes" in your keyboard. If you do not see this, you probably selected the wrong option.
- After formatting data, flash the Multidisabler zip with OrangeFox. This is done to avoid future bootloops.
(Optional) Flash magisk.zip to root (google where to find it)
- Reboot to system
- Wait patiently for the device to boot for the first time
How to flash OrangeFox Recovery (img) or (zip):
- Reboot to recovery
- Select Install
- Select Install Image or zip and search for the OrangeFox Recovery img or zip file
- Flash as recovery
- Reboot to recovery
- Done
Downloads:
Android 12 versions
Linked REMOVED (Outdated, use official sources instead)
Android 11 versions
OrangeFox Recovery img by @geekmaster21
OrangeFox Recovery tar by @geekmaster21
OrangeFox Recovery zip by @geekmaster21
Multidisabler zip by Ianmacd
VBMeta disabler for A52
Source Code: https://github.com/geekmaster21/a52q
Source Code: https://gitlab.com/OrangeFox
Credits:
- Samsung for kernel source code
- OrangeFox team for their awesome recovery
- @geekmaster21 for compiling, updating and maintaining OrangeFox for A52
Join our A52 Telegram group​
Code:
Check out the latest projects on our Telegram, where we share our advancement on new things and try to help as best as we can.
For anything already released, please ask here in XDA
Link: Telegram Group
Join our Spanish General Android Telegram group​
Code:
Grupo para los que hablamos español en donde discutimos Android en general /// Group made for Spanish speakers to discuss Android in general
Link: Telegram Group​
Please report any bugs here. As of now, I've only tested with "M" variant (which should really have no difference to "F" variant) and I successfully backed up, wiped, and restored.
-Final Reservation-
Pruh people
Please start custom ROM for this awesome device (Galaxy A52).
ShaDisNX255 said:
Please report any bugs here. As of now, I've only tested with "M" variant (which should really have no difference to "F" variant) and I successfully backed up, wiped, and restored.
Click to expand...
Click to collapse
I have tested first released and it booted to system ( stock rom + GSI ). Kakarot kernel by @neel0210 make it stabled in GSIs. But MTP does not work, It will be better if you can fix MTP for first released. Rooted stock rom + fix safetynet API net error + bypass safetynet.
A custom recovery so fast? WOW! Thanks, great job!
Silly question: Are OTA-updates (in stock rom) still possible after unlocking the bootloader ?
2faraway2 said:
Silly question: Are OTA-updates (in stock rom) still possible after unlocking the bootloader ?
Click to expand...
Click to collapse
After just unlocking it, yes. After tripping Knox, by flashing anything unofficial, no.
VonSparq said:
After just unlocking it, yes. After tripping Knox, by flashing anything unofficial, no.
Click to expand...
Click to collapse
So after flashing OF no more OTA updates, right ? Thanks
I updated the links for newer versions. They load faster and MTP is fixed.
2faraway2 said:
Y.ou still can do OTA updates.
Click to expand...
Click to collapse
not working for A12
Ray putting in some massive efforts! Thanks for porting this over!
not working for A12
tridi001 said:
not working for A12
Click to expand...
Click to collapse
This isn't for the A12 but for the A52?
ashraftheboss said:
This isn't for the A12 but for the A52?
Click to expand...
Click to collapse
i know that is for A52
but i mean A12= Android 12
tridi001 said:
i know that is for A52
but i mean A12= Android 12
Click to expand...
Click to collapse
Oh man my bad, I apologize!
I've tried many of times to install this recovery in my A52 running latest VB3 and every time its stuck in a loop at splash screen.
While TWRP is working fine, but TWRP does not support OTA updates.
Any solution????

[RECOVERY][A40]TeamWinRecoveryProject 3.6.x Unofficial

{
"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"
}
Unofficial TWRP 3.6.x For Samsung Galaxy A40
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.
Recovery Features:
toybox/busybox support
compatible with Android 12.0 and older
Downloads:
Always in the last post!
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 down + power + 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 down + power + 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 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 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
Sources:
Device trees - a40
Recovery - twrp-minimal-manifest-aosp
Credits:
TeamWin, all contributors to the Recovery
odin throw an error: "complete (write) operation failed"
Deyaski said:
odin throw an error: "complete (write) operation failed"
Click to expand...
Click to collapse
i will update the .tar next days. It was my bad, or try remove the file into .tar as recovery.img only that should work then
Changelog:
• Add DTB/DTBO to fstab. (dtb/dtbo flashable as Image via Recovery)
• Set TW Offset back (shows clock now)
• Switch to Eureka Prebuilt Kernel
kevios12 said:
Changelog:
• Add DTB/DTBO to fstab. (dtb/dtbo flashable as Image via Recovery)
• Set TW Offset back (shows clock now)
• Switch to Eureka Prebuilt Kernel
Click to expand...
Click to collapse
Do you expect to merge this changes into the mainline TWRP? Do you know why is that the mainline one does not even boot?
TWRP 3.6.1 Update
Changelog:
• TWRP 3.6.1
• import stock usb config (fixed adb sideload)
• devicetree cleanup
New Update TWRP 3.6.1​
Device Changelog
Code:
▪️ Initial TWRP_11 AOSP Build
▪️ adapt devicetree from android-9 to android-11
▪️ switch from twrp_omni to twrp_aosp
▪️ Adjust TW Offset=85
▪️ fix E3003 Error by set build_date to an older date
(E3003: Can't install this package <date> over newer build)
▪️ no BSOD anymore after flashing ROMs (Recovery got killed)
▪️ Recovery Size: ~46MB
Source Changelog
Code:
▪️ Internal Storage mount (fixed by TeamWin)
Downloads
IMG: TWRP_3.6.1_11 ~46MB
TAR: TWRP_3.6.1_11 ~46MB
Telegram
edit: TAR fixed​
New Update TWRP 3.6.2​
Device Changelog
Code:
• update to TWRP 3.6.2
▪️ Recovery Size: ~46MB
Source Changelog
Code:
• Allow File Transfer >4GB via MTP
• TeamWin changes see here: https://github.com/TeamWin/android_bootable_recovery/commits/android-11
Downloads
IMG: TWRP_3.6.1_11 ~46MB
TAR: TWRP_3.6.1_11 ~46MB
Telegram
Works a treat, thanks. Installed unofficial lineage with this.
However, I'm trying to get Magisk to work. From what I read at Magisk's howtos, I need to patch the recovery img as this device does not have any boot ramdisk.
I tried patching this twrp image, but this leads to a blank screen (and a hung phone I can only reset with 7sec power+vol up + vol down) after the boot logo, no matter whether I boot without holding buttons or with holding power+vol up shortly like stated in the Magisk guide.
I can still get into twrp by holding the vol up longer.
Can anybody help how to get this twrp and Magisk working nicely together?
tbart said:
Works a treat, thanks. Installed unofficial lineage with this.
However, I'm trying to get Magisk to work. From what I read at Magisk's howtos, I need to patch the recovery img as this device does not have any boot ramdisk.
I tried patching this twrp image, but this leads to a blank screen (and a hung phone I can only reset with 7sec power+vol up + vol down) after the boot logo, no matter whether I boot without holding buttons or with holding power+vol up shortly like stated in the Magisk guide.
I can still get into twrp by holding the vol up longer.
Can anybody help how to get this twrp and Magisk working nicely together?
Click to expand...
Click to collapse
Hi, no. Just flash Magisk.apk via TWRP and reboot to system > magisk symbol popup, click on it > install > open > done.
Thanks a lot. Works as expected!
So are the instructions at https://twrp.me/samsung/samsunggalaxya40.html wrong?
I think teamwin should be notified then. I can create an issue, just wanted to know from someone more knowledgeable than me whether I misunderstood something.
Probably add this to the instructions in the first post, this might help others as well.
For everyone where have no Telegram.
### New TWRP Update is Out ###
Download Link in Attachments!
Changelog:
• 3.6.1 > 3.7.0
• Android 11 Manifest!
• Based on R kernel // latest twrp sources
• adb & adb sideload working
• Added fastbootd
Made by @Gabriel260BR NOT BY ME - Shared Only!

[RECOVERY][UNOFFICIAL] TWRP for Galaxy XCover Pro (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 XCover Pro SM-G715U/U1/W xcoverprosq
Galaxy XCover Pro SM-G715F/FN xcoverproxx
US/Canada bootloader unlock thrGalaxy XCover Pro SM-G715U/U1/W:
here
Download & Guide:
1. Unlock your bootloader.
2. Download XCover Pro : xcoverproxx or xcoverprosq
3. Reboot to download mode and flash vbmeta_disabled.tar in USERDATA slot and click start, Device will reboot to 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 (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 magisk apk in twrp.
8. 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.exynos
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.
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree : xcoverproxx or xcoverprosq
Changelog:
02.06.2022 - Fix boot on international variants
- Clean up fstab
- Fix USB-OTG
- Update to TWRP 3.6.2
06.12.2021 - Initial Release.
After flashing the xcover---.tar in the AP slot I can't reboot to recovery mode, as soon as I plug my usb cable in it gets stuck on the "this phone has an unlocked bootloader DANGER DANGER" screen.
What can I do to proceed?
Adam_Jensen_ said:
After flashing the xcover---.tar in the AP slot I can't reboot to recovery mode, as soon as I plug my usb cable in it gets stuck on the "this phone has an unlocked bootloader DANGER DANGER" screen.
What can I do to proceed?
Click to expand...
Click to collapse
what is your bootloader version? and device model?
afaneh92 said:
what is your bootloader version? and device model?
Click to expand...
Click to collapse
The device model is SM-G715FN and I don't know where to find my bootloader version
Adam_Jensen_ said:
The device model is SM-G715FN and I don't know where to find my bootloader version
Click to expand...
Click to collapse
5th character from the right on build number.
Contact me on telegram @ afaneh92 I have a test build for 9 bootloader
phone stuck at bootloader unlocked screen after flash twrp and not start to recovery
my device android 11 full info here:
Starting ADB Interface... OK
Key Value
Model SM-G715FN
Manufacturer samsung
Platform universal9611
CPU Arch arm64-v8a
Android Serial ****
Manufacturing Date 20200603
Security Patch 2021-05-01
Connection mtp,adb
Timezone Africa/Casablanca
Android Version 11
Android SDK 30
Build RP1A.200720.012.G715FNXXU8CUE1
Build Date Tue May 4 15:26:37 +07 2021
Product Code SM-G715FZKDXEO
*****
Baseband G715FNXXU8CUE1,G715FNXXU8CUE1
RIL Samsung RIL v4.0
Device State unlocked
Device Name xcoverpro
Product Name xcoverproeea
Code Name SM-G715FZKDXEO
BL G715FNXXU8CUE1
PDA G715FNXXU8CUE1
CP G715FNXXU8CUE1,G715FNXXU8CUE1
CSC G715FNOXM8CUE1
Sales Code XEO
Click to expand...
Click to collapse
darifgsm said:
phone stuck at bootloader unlocked screen after flash twrp and not start to recovery
my device android 11 full info here:
Click to expand...
Click to collapse
Guys on rev 8 bootloader or later please wait for update. Need to build new kernel and dtbs.
will work with SM-G715A ?
please help
xbenten said:
will work with SM-G715A ?
please help
Click to expand...
Click to collapse
if your bootloader unlocked yes, if not need to unlock it first
afaneh92 said:
if your bootloader unlocked yes, if not need to unlock it first
Click to expand...
Click to collapse
Good morning,
I would like to instal recovery twrp galaxy-xcover-pro-sm-G715fn-XEF-G715FNXXS9CUH1
Unfortunately, I do not succeed.
Can you help me?
Thanks a lot.
Hello!
When can we expect a TWRP build from your side with support for the version 9 bootloader?
*Is it possible to include support for SELinux status Permissive in the kernel?
will post v9 twrp soon
SM-G715U1
Android 11
Can you please please give me a little direction?
Whiteninja73 said:
SM-G715U1
Android 11
Can you please please give me a little direction?
Click to expand...
Click to collapse
you need to be on v7 bootloader or below to unlock bootloader
thank you for twrp-3.6.2_11-4_afaneh92 for G715FNXXU9CVA3
alas the keyboard is congealed.
thank you for your assistant
Can you make for this version of the binary please?
G715U1UESFCVE3​
BakkaYU said:
Can you make for this version of the binary please?
G715U1UESFCVE3​
Click to expand...
Click to collapse
your device cant be bootloader unlocked
But why????

Categories

Resources