[RECOVERY][UNOFFICIAL] TWRP for Galaxy M31s (Exynos) - Samsung Galaxy M31 ROMs, Kernels, Recoveries, & Ot

[RECOVERY][UNOFFICIAL] TWRP for Galaxy M31s (Exynos) - Samsung Galaxy M31 ROMs, Kernels, Recoveries, & Ot

Changelog:
29.11.2021 - Update to TWRP 3.6.0
- Add Symlinked dynamic partitions to fstab
- Update multidisabler
- fstab clean up
04.06.2021 - Initial Release.

vbmeta_disabler_R stuck on ODIN.
UPD: It's flashed, but after TWRP.tar flashing, I'll have an VBMeta error in Download Mode.

withwaves86 said:
vbmeta_disabler_R stuck on ODIN.
UPD: It's flashed, but after TWRP.tar flashing, I'll have an VBMeta error in Download Mode.
Click to expand...
Click to collapse
file updated

afaneh92 said:
file updated
Click to expand...
Click to collapse
It works, thank you. I'll be test this

Is it working on One Ui 3.1 on M31?

Atharkhan101 said:
Is it working on One Ui 3.1 on M31?
Click to expand...
Click to collapse
You can test

afaneh92 said:
You can test
Click to expand...
Click to collapse
In not here to test. I don't want to screw my phone.

Atharkhan101 said:
In not here to test. I don't want to screw my phone.
Click to expand...
Click to collapse
Then dont

TWRP works in ONEUI 3.1. I flashed it but after it boots to the system and I reboot it or shut it down I get only official binary are allowed to be flashed, and I have to go back to stock. Latest U3 Android 11 M31S. Do you have any kernel for this model?

Working on M31s One UI 4.1

afaneh92 said:
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.
Click to expand...
Click to collapse
does this mean I will have to wipe my phone's entire data?

CosmicSavage said:
does this mean I will have to wipe my phone's entire data?
Click to expand...
Click to collapse
yes

The device is not going into recovery mode instead getting stuck at samsung logo after flashing vbmeta using odin

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 M31s M317F.
Download & Guide:
1. Unlock your bootloader.
2. Download M31s : m31s.
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.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram:
https://t.me/a11twrp
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree
Click to expand...
Click to collapse
Hello Bruh..it worked.. i had issue earlier with the
KG State and/or RMM state prenormal then i reflashed using the official m31S ROM then i unlocked the OEM and flashed the above two files at the same time using odin

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 M31s M317F.
Download & Guide:
1. Unlock your bootloader.
2. Download M31s : m31s.
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.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram:
https://t.me/a11twrp
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree
Click to expand...
Click to collapse
Hi ,
Thanks a lot for the TWRP support.
Although I'm able to successfully complete all the above steps , once i boot into system KG state is triggered and i end up getting the error "Only official released binaries are allowed to be flashed".
and the device goes into KG state = prenormal and its locked for 7 days.
i also tried flashing RMM_Bypass_v3_corsicanu , but no luck as it is throwing ERROR : " cant mount /system_root .... aborting"
(currently M31s is running on Android 11)
Kindly Help.
Thanks

Hangrylion said:
Hi ,
Thanks a lot for the TWRP support.
Although I'm able to successfully complete all the above steps , once i boot into system KG state is triggered and i end up getting the error "Only official released binaries are allowed to be flashed".
and the device goes into KG state = prenormal and its locked for 7 days.
i also tried flashing RMM_Bypass_v3_corsicanu , but no luck as it is throwing ERROR : " cant mount /system_root .... aborting"
(currently M31s is running on Android 11)
Kindly Help.
Thanks
Click to expand...
Click to collapse
You don't need all this hassle just connect to internet and open browser then check kg status, must be checking.

are the links updated?

Any update on M31s android 12 OneUI Core 4.1 ???
I didn't seem to be working many guys said here they were forced to go back to the official rom...
Can someone confirm what's going on?

osama_blythe said:
Any update on M31s android 12 OneUI Core 4.1 ???
I didn't seem to be working many guys said here they were forced to go back to the official rom...
Can someone confirm what's going on?
Click to expand...
Click to collapse
M31s, android 12, OneUI core 4.1,
working perfectly with no any issue with TWRP and magisk.

Related

{UPDATED}[RECOVERY][UNOFFICIAL]Red Wolf Recovery Project[09/07/2018][enchilada]

{
"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:
/*
* 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.
*
*/
Red Wolf Recovery is custom recovery based on TWRP source code however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.
Based on TWRP version: 3.2.2
For device: Enchilada
Features
Translated to EN & CZ
- Password protection
- Flashlight(Currently Broken)
- Built-in latest Magisk, SuperSU & AromaFM
- Support two screenshot GUI actions - Power+VolDown to save screenshot in to the internal storage &
Power+VolUp to save screenshot in to the external storage (Will be automatically saved in to the internal in case
that external storage doesn't exist).
- Support automatic reboot after the restore process
- Recovery can automatically modify some props in the ROM directly during the installation
- Some built-in scripts from community
- Tap to wake support
- Advanced deactivation of the stock recovery
- Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- Support "set on boot" settings.
* Changes for security reasons *
- ADB isn't starting automatically at the start of the recovery. You have to activate it in recovery
- MTP isn't starting until user enter correct password
- Deactivated TWRP theme engine
Some differences
- get out of here if you are pirating apps. this recovery is not for you
- compiled on omnirom-8.1 source
- There isn't bug with reboot from recovery to recovery
Changelog
Code:
Initial Build
Bugs:
1)Flashlight doesnt work (only on recovery)
2)Aroma Installer doesn't work
3)If flashing MTP build, on boot if you enter wrong pattern it causes it to crash wherein you'd need to reboot by long pressing power button.
4) password protection doesn't work.
Fixed:
1) Vibration/Haptic Feedback has been fixed
2) encryption/Decryption now work
Glitches
1) Sometimes mtp doesn't work dircetly when booted into recovery. For MTP to work, once booted into recovery go to mount, and tap on disable mtp and then tap enable mtp.
2) When you select any option in reboot, it redirects to recovery. Do the same again and it will work
(For ex: you tap on reboot>system, it redirects to recovery. then again tap reboot>system it will work)
******************Installation Instructions******************
1)Flashing through a Custom Recovery
- Download the RedWolf-installer-enchilada-3.2.2-0.zip
- Copy the zip to your phone's internal storage
- Flash the zip and you're good to go
2)People who don't have any custom recovery(through fastboot)
- Download both RedWolf-installer-enchilada-3.2.2-0.zip & RedWolf-027-Unofficial-enchilada.img into your pc.
- Copy RedWolf-recovery-installer.zip to the internal storage of your phone.
- In PC go to the dir where you downloaded the RedWolf-027-Unofficial-enchilada.img
-Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here (or) open powershell here
- Now switch off your phone, connect your phone to pc using the original cable provided.
- Press power button + vol up button to boot into bootloader.
- In thecmd on your pc type :
Code:
fastboot boot RedWolf-027-Unofficial-enchilada.img
- In a few moments your phone will boot into RedWolfRecovery.
- Once booted into recovery immediately press install and locate the redwolfinstaller zip that you copied into your phone and flash it.
- Wait for it to Flash.
- and you've successfully flashed RedWolf-Recovery
DOWNLOADS
RedWolf-Recovery(MTP) for enchilada(OnePlus6)
RedWolf-Recovery(NO-MTP) for enchilada(OnePlus6)
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery.
Sources:
DeviceTree
RedWolf
Credits: @dees-Troy && @wuxianlin for their sources
OMNI rom for twrp
RedWolf Team for the RedWolf source
A big thanks to @joemossjr for fixing the issues with recovery not booting
@notsyncing on github for the fixes
@Titokhan for helping me with a and b
me for compiling and testing and fixing Haptic Feedback on RedWolf

So guys the builds and testing are finally done.
As told i have uploaded two builds with mtp and without mtp
Based on twrp 3.2.2 source
Bugs:
1)Flashlight doesnt work (only on recovery)
2)Aroma Installer doesn't work
3)If flashing MTP build, on boot if you enter wrong pattern it causes it to crash wherein you'd need to reboot by long pressing power button.
Fixed:
1) Vibration/Haptic Feedback has been fixed
2) encryption/Decryption now work
Glitches
1) Sometimes mtp doesn't work dircetly when booted into recovery. For MTP to work, once booted into recovery go to mount, and tap on disable mtp and then tap enable mtp.
2) When you select any option in reboot, it redirects to recovery. Do the same again and it will work
(For ex: you tap on reboot>system, it redirects to recovery. then again tap reboot>system it will work)
CREDITS
A big thanks to @joemossjr for fixing the issues with recovery not booting
also thanks to wuxianlin and Dees_Troy for the sources @notsyncing on github for the fixes
The Download links and Instructions will be updated in OP
Dated : 09-07-2018

Is Aroma Installer working?
Regards

Lol I built this a few weeks ago
---------- Post added at 03:08 AM ---------- Previous post was at 02:52 AM ----------
encryption doent work

Only for the One Plus 6? Any plans on expanding to other devices?

Eliminater said:
Is Aroma Installer working?
Regards
Click to expand...
Click to collapse
It should, Not tried though

joemossjr said:
Lol I built this a few weeks ago
---------- Post added at 03:08 AM ---------- Previous post was at 02:52 AM ----------
encryption doent work
Click to expand...
Click to collapse
Damn I didn't notice that.... my bad
Updated for now in OP

jdmst77 said:
Only for the One Plus 6? Any plans on expanding to other devices?
Click to expand...
Click to collapse
That's not dependant on me mate

pranavasri said:
Damn I didn't notice that.... my bad
Updated for now in OP
Click to expand...
Click to collapse
Np it's probably due to the 7.1 branch your using btw why are you using the 7.1 branch again?

joemossjr said:
Np it's probably due to the 7.1 branch your using btw why are you using the 7.1 branch again?
Click to expand...
Click to collapse
their 8.1 sources gave issues while compiling(probably due to device sources, so i went with 7.1 source )

pranavasri said:
their 8.1 sources gave issues while compiling(probably due to device sources, so i went with 7.1 source )
Click to expand...
Click to collapse
Ah. Yeah that's where you messed up what was the errors? I've got about every single one lol plus the 8.1 branch has the proper decryption for us lol

joemossjr said:
Ah. Yeah that's where you messed up what was the errors? I've got about every single one lol plus the 8.1 branch has the proper decryption for us lol
Click to expand...
Click to collapse
Shall i PM

pranavasri said:
Shall i PM
Click to expand...
Click to collapse
I'll do you one better hit me up on Hangouts @ [email protected]

Eliminater said:
Is Aroma Installer working?
Regards
Click to expand...
Click to collapse
No, aroma is not working and even core functionality like decryption of the data partition don't work.

xXx said:
No, aroma is not working and even core functionality like decryption of the data partition don't work.
Click to expand...
Click to collapse
Chill man we will get it working

is DM verity and force encrypt disabled? how'd you achieve this? is it only for installing rom after recovery? (format data) or another way?
can you please explain @pranavasri

virtyx said:
is DM verity and force encrypt disabled? how'd you achieve this? is it only for installing rom after recovery? (format data) or another way?
can you please explain @pranavasri
Click to expand...
Click to collapse
I wouldn't say they are disabled but yes they might not work, (looks like it's because i've used nougat source) i didn't get thelast part of your question

pranavasri said:
I wouldn't say they are disabled but yes they might not work, (looks like it's because i've used nougat source) i didn't get thelast part of your question
Click to expand...
Click to collapse
firstly we need a TWRP with decrypt possible for us to disable encryption
and also the ability to edit the fstab in /vendor partition (/vendor/etc/ there are 2 fstab files we need to edit and remove force encrypt to encryptable)
i have tried this with official twrp and didnt work
i cant seem to mount /vendor as R/W in OS or TWRP my changes dont stick for some reason.

@pranavasri
Thank you for sharing.
I'm gonna give it a try!

pranavasri said:
Code:
/*
* 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.
*
*/
Red Wolf Recovery is custom recovery based on TWRP source code however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.
Based on TWRP version: 3.2.1
For device: Enchilada
Features
Translated to EN & CZ
- Password protection
- Flashlight(Currently Broken)
- Built-in latest Magisk, SuperSU & AromaFM
- Support two screenshot GUI actions - Power+VolDown to save screenshot in to the internal storage &
Power+VolUp to save screenshot in to the external storage (Will be automatically saved in to the internal in case
that external storage doesn't exist).
- Support automatic reboot after the restore process
- Recovery can automatically modify some props in the ROM directly during the installation
- Some built-in scripts from community
- Tap to wake support
- Advanced deactivation of the stock recovery
- Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- Support "set on boot" settings.
* Changes for security reasons *
- ADB isn't starting automatically at the start of the recovery. You have to activate it in recovery
- MTP isn't starting until user enter correct password
- Deactivated TWRP theme engine
Some differences
- get out of here if you are pirating apps. this recovery is not for you
- compiled on omnirom-7.1 source
- There isn't bug with reboot from recovery to recovery
Changelog
Code:
Initial Build
Bugs
-Mtp removed (same reason as for the official build)(only in recovery)
-flashlight doesn't work
-encryption doesn't work. thnx to @joemossjr for letting me know
******************Installation Instructions******************
1)Flashing through a Custom Recovery
- Download the RedWolf-recovery-installer.zip
- Copy the zip to your phone's internal storage
- Flash the zip and you're good to go
2)People who don't have any custom recovery(through fastboot)
- Download both RedWolf-recovery-installer.zip & RedWolf-027-Unofficial-enchilada.img into your pc.
- Copy RedWolf-recovery-installer.zip to the internal storage of your phone.
- In PC go to the dir where you downloaded the RedWolf-027-Unofficial-enchilada.img
-Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here (or) open powershell here
- Now switch off your phone, connect your phone to pc using the original cable provided.
- Press power button + vol up button to boot into bootloader.
- In thecmd on your pc type :
Code:
fastboot boot RedWolf-027-Unofficial-enchilada.img
- In a few moments your phone will boot into RedWolfRecovery.
- Once booted into recovery immediately press install and locate the redwolfinstaller zip that you copied into your phone and flash it.
- Wait for it to Flash.
- and you've successfully flashed RedWolf-Recovery
DOWNLOADS
RedWolf-Recovery for enchilada(OnePlus6)
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery.
Sources:
DeviceTree
RedWolf
Credits: @dees-Troy && @wuxianlin for their sources
OMNI rom for twrp
RedWolf Team for the RedWolf source
@Titokhan for helping me with a and b
me for compiling and testing
Click to expand...
Click to collapse
If I don't like or want to revert back to TWRP can I flash TWRP from within red wolf?
---------- Post added at 10:36 PM ---------- Previous post was at 10:31 PM ----------
virtyx said:
firstly we need a TWRP with decrypt possible for us to disable encryption
and also the ability to edit the fstab in /vendor partition (/vendor/etc/ there are 2 fstab files we need to edit and remove force encrypt to encryptable)
i have tried this with official twrp and didnt work
i cant seem to mount /vendor as R/W in OS or TWRP my changes dont stick for some reason.
Click to expand...
Click to collapse
As far as decrypting in TWRP check my post here. https://forum.xda-developers.com/showpost.php?p=76845815&postcount=14
I was able to do it. Here's the whole thread. https://forum.xda-developers.com/oneplus-6/help/soft-brick-restoring-backup-twrp-t3805112

[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy A5/A7 (2017)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Official TWRP 3.6.1-* For Galaxy A5/A7 (2017)Only for exynos variants - A520F (Europe, Global Single-SIM); A520F/DS (Global Dual-SIM); A520K/L/S (South Korea); A520W (Canada), A720F (Global Single-SIM); A720F/DS (Global Dual-SIM); A720S (South Korea)
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.
Features:
Code:
- built from Pie kernel source
- built from android-9.0 recovery sources
- built in full 64 mode
- fully compatible with Android 8.*/9.0/10.0
Downloads:
A5 2017 - https://twrp.me/samsung/samsunggalaxya52017.html
A7 2017 - https://twrp.me/samsung/samsunggalaxya72017.html
Instructions:
Odin
Download latest Odin zip from downloads.corsicanu.ro/samsung
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Home+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Home" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Home" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
A5 2017 Device tree - https://github.com/TeamWin/android_device_samsung_a5y17lte
A7 2017 Device tree - https://github.com/TeamWin/android_device_samsung_a7y17lte
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal7880/tree/android-9.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, jesec, geiti94, dyneteve, testers, donors and anyone else involved in making this possible

Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Latest Magisk stable or canary
FAQ / Further reading
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware.
Q: I get "Failed to mount /preload message", what to do?
A: From wipe menu select Advanced Wipe, select preload partition to be wiped and reboot recovery.
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.

Thanks
like!

bootloop
Immediately after installing my phone went on bootloop and restart continuously.
Please help me:crying::crying:

e.ahangari said:
Immediately after installing my phone went on bootloop and restart continuously.
Please help me:crying::crying:
Click to expand...
Click to collapse
What device and what method of flashing did you used?

a7, when installing Odin, bootlooр

bootloop
corsicanu said:
What device and what method of flashing did you used?
Click to expand...
Click to collapse
A720F oreo stock rom - I wanted to update from twrp_3.1.0-1 to 3.2.2

cant flash in a7 2017 (a720f)using odin

on my a7 bootloop too, flash via twrp. flash through odin previous version helps

A520F, zip downloaded and flashed in TWRP, It's perfect, no problem (bootloop) at this time!
Thank you corsicanu.

Well done.

Works great for me, flashed .img in TWRP,A520F.

Ok, turned out that A7 twrp was broken, fixed that and also tested properly, meanwhile switched from TwrpBuilder repo to my own repo and moved mega downloads to github releases.
New builds will be up soon, beside mentioned, there are no changes.
Enjoy it!
Downloads:
A520x - https://github.com/corsicanu/android_device_samsung_a5y17lte/releases
A720x - https://github.com/corsicanu/android_device_samsung_a7y17lte/releases

Thanks
corsicanu said:
Ok, turned out that A7 twrp was broken, fixed that and also tested properly, meanwhile switched from TwrpBuilder repo to my own repo and moved mega downloads to github releases.
New builds will be up soon, beside mentioned, there are no changes.
Enjoy it!
Downloads:
A520x - https://github.com/corsicanu/android_device_samsung_a5y17lte/releases
A720x - https://github.com/corsicanu/android_device_samsung_a7y17lte/releases
Click to expand...
Click to collapse
Thanks a lot.
Its now fixed and work properly.:highfive::highfive::highfive:

Thanks

A7y17lte
is anyone installed root succesfully?

corsicanu said:
Ok, turned out that A7 twrp was broken, fixed that and also tested properly, meanwhile switched from TwrpBuilder repo to my own repo and moved mega downloads to github releases.
New builds will be up soon, beside mentioned, there are no changes.
Enjoy it!
Downloads:
A520x - https://github.com/corsicanu/android_device_samsung_a5y17lte/releases
A720x - https://github.com/corsicanu/android_device_samsung_a7y17lte/releases
Click to expand...
Click to collapse
I'm about to receive a new A5 2017 and update it to official OREO right out of the box.
After having updated, there's the TWRP step and I just wanted to know of I have to also flash the usual encription thing (opt verity or something like that) I have almost always flashed after a fresh twrp install.

Works fine for me so far... I will test with the official fw to know if the /data is decrypted. We appreciate the work corsicanu. :good:
@edit
For me, everything works fine! including support for all languages.

A7y17lte
corsicanu said:
Unofficial TWRP 3.2.2-0 For A5 / A7 2017Disclaimer
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.
Special features:
Code:
- built from Oreo kernel source
- built in full 64 mode
- updated TWRP source
- fully compatible with all Oreo roms
Downloads:
A520x - https://github.com/corsicanu/android_device_samsung_a5y17lte/releases
A720x - https://github.com/corsicanu/android_device_samsung_a7y17lte/releases
Instructions:
Odin
Download Odin v3.13.1
Download and install Samsung Drivers (if you have them installed you can skip this step)
Download TWRP_*.tar
Switch off the phone
Use Home+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Home" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Home" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.zip, push it into phone storage and flash it as normal zip in your current recovery.
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
A520x - https://github.com/corsicanu/android_device_samsung_a5y17lte
A720x - https://github.com/corsicanu/android_device_samsung_a7y17lte
Kernel - https://github.com/corsicanu/twrp_android_kernel_samsung_universal7880
Credits:
@Dyneteve
@TwrpBuilder
Click to expand...
Click to collapse
is anyone installed root succesfully?

Hey,
I have a problem and I don't know how to fix it, cuz I never had that.
I've installed TWRP successfully and I can start it normally, but TWRP don't have access to any Files in Internal Storage.
I installed TWRP on A520F (with Firmware DBT, Android 8.0)
Kind regards,
DasNuddel // Charles

[RECOVERY][UNOFFICIAL][3.5.2] TWRP for Galaxy M21

{
"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"
}
Disclaimer:
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Kernel Features:
latest kernel source release
disabled security stuff/knox/proca/logging/audit/useless features
Recovery Features:
TWRP 3.5.0, Android 10
Built in 64-bit mode
Super partition support
Added custom super binary to help with managing super partitions ( more on that in post #3 )
Native rw mount dynamic partitions
Native GSI flashing
Native dynamic partitions resize/wipe/backup/restore
Working MTP and ADB only!
How to install?
Spoiler: ODIN(Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Press the volume down + volume up button whilst the phone is connected to a pc to boot 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 + bixby key + 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, factory reset data and redo from step 5!
Download TWRP.tar from download link below;
Open odin and place the TWRP.tar file in AP slot and press start. Once you press start, keep holding power and volume up button and the device will reboot to recovery mode.
* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this Internal storage won't work in TWRP
Flash the encryption_disabler.zip from the link below to disable internal storage encryption and patch stock recovery restoration.
Additionally, flash TWRP_Bootlogo_patcher to patch warning screens when booting the device.
If you want to root, flash Magisk.
Spoiler: TWRP
If you're coming from other TWRP versions, download TWRP.img, reboot to recovery, tap Install > Install Image > Navigate to downloads folder > select TWRP.img > Select Recovery and swipe to confirm flash. Go to reboot and reboot to recovery and the changes will have taken place.
Downloads:
TWRP-3.5.2-m21-v3.1 ( Android 11 ONLY )
TWRP-3.5.1-v3.0_m21nsxx ( Android 11 ONLY )
TWRP-3.5.0-v2.0_m21nsxx ( Android 11 ONLY )
TWRP-3.5.0-v1.1_m21nsxx ( Android 10 ONLY )
Encryption Disabler
TWRP_Bootlogo_patcher
Sources:
Device Tree: https://github.com/soulr344/android_device_samsung_m21
Kernel Source: https://github.com/soulr344/android_kernel_samsung_m21nsxx/tree/prebuilt
TWRP Source: https://github.com/soulr344/android_bootable_recovery/commits/android-10.0
Credits:
TeamWin, corsicanu, ananjaser1211, jesec, epicX67, testers and anyone else who made this possible.

Changelog:
v2.0
Initilal Android 11 support
isn't backwards compatible with android 10
rewrote fstab
added EFS/SecEFS Image Backup
added prism/optics mount
v1.1
fixed adb only
permissive
updated super binary
fixed long boot time
v1.0
Initial Release
MISC LINKS
Telegram Channel
Telegram Group
TeamWin Official Website

FAQ
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you flashed encryption disabler zip / formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.
Q: Why do i need to format data partition?
A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Q: I can't flash anything with TWRP. Internal Storage has some random folders with weird name.
A: Format Data and flash encryption disabler.

Info about custom super partition helper binary. (Irrelevant because of native logical partitions but yeah, its present)
It's meant to help with managing partitions inside the super partition itself. It has some functions built in like mount, unmount, flash and format. Here is a brief rundown on what each of them do.
Partitions that are supported are:
system, system_root, vendor, odm, product
Click to expand...
Click to collapse
Please note that system_root is an alias of system and umount is an alias of unmount.
All of these commands are runnable through TWRP Terminal ONLY!
Code:
super mount partition
This will mount partition in rw mode in mountpoint in fstab.
Code:
super unmount[or umount] partition
This command will unmount given partition and make it read only.
Code:
super format partition
This command will format given partition as ext4 inside super partition.
Code:
super flash partition /path/to/image.img
Flashes image.img to partition.
You can also flash GSI (Generic System Image) using this command. Simply run:
Code:
super flash system /path/to/gsi.img
For Custom ROM Developers:
You can use this as an alternative to mount/format/unmount partitions that are inside super partition normally.
Code:
run_program("/sbin/super", "format", "system"); # formats system
run_program("/sbin/super", "mount", "system"); # mounts system as rw
run_program("/sbin/super", "unmount", "system"); # unmounts system and makes it ro

Don't own an M21 but good job

Good work bro

Well nice, indeed

Don't hab M21 but Excellent Work

Can I flash it on M21s (F415)?

well done soul

Excellent. Will try it out very soon.

bro , Encryption disabler.zip link doesn't work

soulr344 said:
Disclaimer:
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Kernel Features:
latest kernel source release
disabled security stuff/knox/proca/logging/audit/useless features
Recovery Features:
TWRP 3.5.0, Android 10
Built in 64-bit mode
Super partition support
Added custom super binary to help with managing super partitions ( more on that in post #3 )
Working MTP and ADB only!
How to install?
Spoiler: ODIN(Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Press the volume down + volume up button whilst the phone is connected to a pc to boot 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 + bixby key + 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, factory reset data and redo from step 5!
Download TWRP.tar from download link below;
Open odin and place the TWRP.tar file in AP slot and press start. Once you press start, keep holding power and volume up button and the device will reboot to recovery mode.
* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this Internal storage won't work in TWRP
Flash the encryption_disabler.zip from the link below to disable internal storage encryption and patch stock recovery restoration.
Additionally, flash TWRP_Bootlogo_patcher to patch warning screens when booting the device.
If you want to root, flash Magisk.
Spoiler: TWRP
If you're coming from other TWRP versions, download TWRP.img, reboot to recovery, tap Install > Install Image > Navigate to downloads folder > select TWRP.img > Select Recovery and swipe to confirm flash. Go to reboot and reboot to recovery and the changes will have taken place.
Downloads:
TWRP-3.5.0-v2.0_m21nsxx
TWRP-3.5.0-v1.1_m21nsxx
Encryption Disabler
TWRP_Bootlogo_patcher
Sources:
Device Tree: https://github.com/soulr344/android_device_samsung_m21nsxx
Kernel Source: https://github.com/soulr344/android_kernel_samsung_m21nsxx/tree/prebuilt
TWRP Source: https://github.com/TeamWin/android_bootable_recovery/commits/android-10.0
Credits:
TeamWin, corsicanu, ananjaser1211, jesec, testers and anyone else who made this possible.
Click to expand...
Click to collapse
soulr344 said:
Changelog:
v2.0
Initilal Android 11 support
isn't backwards compatible with android 10
rewrote fstab
added EFS/SecEFS Image Backup
added prism/oE]
Hi mate,
tried several times to get the encryption disabler.
No access and no reply when asking for access.
What can I do?
Thanks,
Jürgen
Click to expand...
Click to collapse
kayfee said:
bro , Encryption disabler.zip link doesn't work
Click to expand...
Click to collapse
Hi mate,
Could you please give me access to the encrypt disabler link?
Thanks,
Jürgen

encryption disabler
st

kebson4021 said:
encryption disabler View attachment 5254867st
Click to expand...
Click to collapse
You can flash multi disabler instead. Its available in the telegram group for the device.

encryption disabler...
just put new link please...
I flashed with this Kernel and phone start working...

@soulr344 Does TWRP_Bootlogo_patcher work on Android 11?

mudshark1309 said:
Hi mate,
Could you please give me access to the encrypt disabler link?
Thanks,
Jürgen
Click to expand...
Click to collapse
yep, given access to everyone. check again

userprince said:
@soulr344 Does TWRP_Bootlogo_patcher work on Android 11?
Click to expand...
Click to collapse
yep

Thanks for keeping this updated

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

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
09.08.2021 - Fix haptic feedback
- Updated to latest kernel source
- No vbmeta disable require
- fstab clean up
01.03.2021 - Initial Release.

Boss!

Boss

Thanks boss..

Boss!

Omg.... Boss and Heroes

Any custom rims for this device yet? Maybe a Pixel Experience ROM?

Any news on rom development by chance?, Just curious thanks.

It will take a big while before custom ROMs, don't expect them too soon

Hello everyone, I only have one question, besides the Twrp and the vbmeta_disabled_R.tar do you also need to flash a Multidisabler via Odin? Thank you.

siriow said:
Hello everyone, I only have one question, besides the Twrp and the vbmeta_disabled_R.tar do you also need to flash a Multidisabler via Odin? Thank you.
Click to expand...
Click to collapse
You just need to go to advanced then open terminal in TWRP, and type multidisabler, then wait, then type it again.

FreeRunner2017 said:
You just need to go to advanced then open terminal in TWRP, and type multidisabler, then wait, then type it again.
Click to expand...
Click to collapse
Ok, Thank you

siriow said:
Ok, Thank you
Click to expand...
Click to collapse
Your welcome, any issues feel free to PM me

I wish there was a very easy way to patch AP to keep TWRP after a dirty flash manual upgrade.

Burt Squirtz said:
I wish there was a very easy way to patch AP to keep TWRP after a dirty flash manual upgrade.
Click to expand...
Click to collapse
1.Easiest option - Go with custom ROM (If available)
2.Second easy, modify AP and patch it.
Extract all the contents of AP file - delete recoevry and vbmeta images - Repack as tar (You can use 7zip or similar) - Patch it with magisk
After flashing, straightway go to TWRP - and apply multidisabler before booting device.

dr.ketan said:
1.Easiest option - Go with custom ROM (If available)
2.Second easy, modify AP and patch it.
Extract all the contents of AP file - delete recoevry and vbmeta images - Repack as tar (You can use 7zip or similar) - Patch it with magisk
After flashing, straightway go to TWRP - and apply multidisabler before booting device.
Click to expand...
Click to collapse
This would clear the User data / Accounts also, yeah ?
@afaneh92 _ Bro, I think the existing TWRP doesnt mount Data on the Newest March Security Patch.
I had no issues with the February Firmware.
Could you have a look ?

JazonX said:
This would clear the User data / Accounts also, yeah ?
@afaneh92 _ Bro, I think the existing TWRP doesnt mount Data on the Newest March Security Patch.
I had no issues with the February Firmware.
Could you have a look ?
Click to expand...
Click to collapse
You asked for dirty flash trick right? If erasing data and acc then it's not dirty flash.
I don't have any issue on March secure patch

What could be causing this issue?
Did a full stock flash as well, and repeated the TWRP process.

JazonX said:
What could be causing this issue?
Did a full stock flash as well, and repeated the TWRP process.
Click to expand...
Click to collapse
Run multidisabler script in twrp terminal

[RECOVERY][UNOFFICIAL] TWRP for Galaxy Tab S7/S7+ Series (Snapdragon)

Changelog:
29.11.2021 - Update to TWRP 3.6.0
- Add Symlinked dynamic partitions to fstab
- Update multidisabler
- fstab clean up
- Fix haptic feedback
28.07.2021 - Initial Release.

Amazing!! will try asap!

Any news bout T870/T875 development?

tabs s7 sm-t875 twrp please

I have posted a test build for the T870 here:
TWRP for the Samsung Galaxy Tab S7+ 5G (T976B)
I'm stuck in TWRP loop with the new T970XXU1ATK3 firmware won't boot to system after the update. Is there anyway to fix this issue?
forum.xda-developers.com
Please let me know if it works for you.

Good morning sir is good for tab s7+ sm-t975? tanks in adcance

Marx71 said:
Good morning sir is good for tab s7+ sm-t975? tanks in adcance
Click to expand...
Click to collapse
You can test, but make full backup and know how to recover soft brick by reflashing stock recovery/firmware.

tank you. But recover soft brick possible whit fastboot?

No, samsung disabled fastboot by default.

If I don't care about flashing in TWRP (yet) can I just flash recovery and see it running? (Basically is the wipe data optional)

parkerlreed said:
If I don't care about flashing in TWRP (yet) can I just flash recovery and see it running? (Basically is the wipe data optional)
Click to expand...
Click to collapse
Flashing vbmeta disable will wipe data

I have SM-T870, After point #4, its just in the loop. Cannot get to recovery.

To clarify, US tab s7+ (SM-T970N) snapdragon requires the paid token unlock before this can be flashed?

gpz1100 said:
To clarify, US tab s7+ (SM-T970N) snapdragon requires the paid token unlock before this can be flashed?
Click to expand...
Click to collapse
No, T970N is Korean not US!

tyracz said:
I have SM-T870, After point #4, its just in the loop. Cannot get to recovery.
Click to expand...
Click to collapse
If it doesn't boot on T870 then its not supported.

afaneh92 said:
No, T970N is Korean not US!
Click to expand...
Click to collapse
Hmm.. Costco has it wrong?
https://www.costco.com/samsung-galaxy-12.4%22-tab-s7%2b-128gb---mystic-black---includes-keyboard.product.100684979.html

afaneh92 said:
If it doesn't boot on T870 then its not supported.
Click to expand...
Click to collapse
I have rooted my SM-T870 by inserting Magisk into AP file and flashing it with odin. Only problem is that now i have in magisk A/B - NO. Which means my partitions are not flashed. I run into problems trying to execute some root programs where they crash since they dont have access to both partitions. Is there any way to root partition A/B?

tyracz said:
I have rooted my SM-T870 by inserting Magisk into AP file and flashing it with odin. Only problem is that now i have in magisk A/B - NO. Which means my partitions are not flashed. I run into problems trying to execute some root programs where they crash since they dont have access to both partitions. Is there any way to root partition A/B?
Click to expand...
Click to collapse
our device is not A/B its A only

afaneh92 said:
our device is not A/B its A only
Click to expand...
Click to collapse
Thank you for answer. If I root SM-T870 with Magisk via AP insert, is this considered full root ? or is this root like partial?

Database Develop

welcome