Develop Bugs

[Recovery] Official TWRP for Galaxy S6 edge+ (3.0.2-1)

Team Win Recovery Project 3.0.2-1
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy S6 edge+ stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Flash a root such as SuperSU or phh-superuser. You can also flash .
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
[url]http://teamw.in/devices/samsunggalaxys6edgeplus.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin to flash when possible.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://idlekernel.com/flash-tools/
FULL STEPS FOR ROOTING YOUR DEVICE
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"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"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for your device variant.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot without touching any other options, then press [Start].
Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 12 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
Only if you want your internal storage or data partition to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
If you only want a bootable system partition or readable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
** If your internal storage is encrypted, you will need to use adb sideload instead.
Go to [Reboot] -> [System].
Wait up to 5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2-1 - New device tree and kernel, support added for Marshmallow, f2fs, and MTP.
v3.0.2-0 - See here for the changes.
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree: https://github.com/TeamWin/android_device_samsung_zenlte (android-6.0)
Kernel: https://github.com/jcadduono/nethunter_kernel_noblelte (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy S6 edge+, Tool/Utility for the Samsung Galaxy S6 Edge+
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/jcadduono/android_device_samsung_zenlte
Version Information
Status: Stable
Current Stable Version: 3.0.2-1
Stable Release Date: 2016-04-08
Created 2016-04-08
Last Updated 2016-12-18

Builds are coming soon guys, I just made the thread so that we have a reference when updating the site.

Bricked after flash, any suggestion? SM-G928F variant with audax plus 3.0 + audax kernel. Recovery not booting, tried reflash with odin old 3.0.0 recovery but the brick persist...

pmisun said:
Bricked after flash, any suggestion? SM-G928F variant with audax plus 3.0 + audax kernel. Recovery not booting, tried reflash with odin old 3.0.0 recovery but the brick persist...
Click to expand...
Click to collapse
Flash the twrp via Odin provided by the Audax rom, that note 5 recovery
Sent from my Darkside of Edge plus

Solved. Btw there is in repo of twrp dev which is linked by audax also 3.0.1 twrp working version. working as charm.

pmisun said:
Solved. Btw there is in repo of twrp dev which is linked by audax also 3.0.1 twrp working version. working as charm.
Click to expand...
Click to collapse
https://idlekernel.com/twrp/zenlte see 3.0.2-1, should be built soon on official, whenever someone confirms that everything is working ok
this includes:
adb shell
brightness slider
installing zips
formatting partitions (as ext4 and f2fs)
not crashing
backup & restore works for each partition
mtp
vibration
otg storage
whatever else you can think of checking
check on both L and M bootloaders, preferably quote my list with Y(working)/N(not working) in front of issues, and give recovery.log

jcadduono said:
https://idlekernel.com/twrp/zenlte see 3.0.2-1, should be built soon on official, whenever someone confirms that everything is working ok
this includes:
adb shell
brightness slider
installing zips
formatting partitions (as ext4 and f2fs)
not crashing
backup & restore works for each partition
mtp
vibration
otg storage
whatever else you can think of checking
check on both L and M bootloaders, preferably quote my list with Y(working)/N(not working) in front of issues, and give recovery.log
Click to expand...
Click to collapse
will try this evening.

pmisun said:
will try this evening.
Click to expand...
Click to collapse
welcome to xda, don't say you'll do things, just do things, it makes people think that they don't have to do it because someone else will do it eventually, slowing things down for everyone.

jcadduono said:
welcome to xda, don't say you'll do things, just do things, it makes people think that they don't have to do it because someone else will do it eventually, slowing things down for everyone.
Click to expand...
Click to collapse
will try and will do..make sense? ok i wont try this.

Why nothing for s6 edge + USC? Everything else except usc version :'(

Tokumei no said:
Why nothing for s6 edge + USC? Everything else except usc version :'(
Click to expand...
Click to collapse
read after first post, builds not up on the site yet, links available

jcadduono said:
read after first post, builds not up on the site yet, links available
Click to expand...
Click to collapse
But there has never been a custom recovery for the s6 edge + USC model. (SM-G928R4 US Cellular) Unless I have missed something then please point me in the right direction for a custom recovery for this specific model.

perfect update TWRP for G928F
https://idlekernel.com/twrp/zenlte/3.0.2-1/twrp-3.0.2-1-zenlte.zip
flash from CWM

It works perfectly fine! The only bug I've found is that vibration doesn't work but that's really not important
Sent from my SM-G928F using XDA-Developers mobile app

Can someone please work on a custom recovery for SM-G928R4? I mean come on now :'(

Works really great on my 928g only vibrations don't work but I don't care thanks a lot.

Guys help
I am using note 5 twrp-3.0.0-0-nobleltezt recovery for my G928C so how to flash this

I have the international SM-G9287 Duo variant on the latest firmware 6.0.1/MMB29K/G9287ZHU2BPC6 (marshmallow) and it's rooted. When I get to the step to press Home+Vol up towards the end of the flash it just reboots normal. Then when I turn of to boot into recovery Home+Vol up+Power I get "RECOVERY IS NOT SEANDROID ENFORCING" in red along the top with the Samsung GS6 logo. I have a tar file with the stock recovery and that boots fine. Any suggestions? Thanks in advance.

I can't find the download link to v.3.0.2-1 on the device page. Am I searching in the wrong place? (https://dl.twrp.me/zenlte)

fisk4rn said:
I can't find the download link to v.3.0.2-1 on the device page. Am I searching in the wrong place? (https://dl.twrp.me/zenlte)
Click to expand...
Click to collapse
Its link is in Post #6.
Powered by Elektrik

Development [Recovery] [A325x] [Stable-ish, Unofficial] TWRP 3.7.0_12.1 - Galaxy A32 4G

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <not_my_phone.h>
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
TWRP 3.7.0_12.1 - Samsung Galaxy A32 4G​
Current Status: Stable-ish
Supported Models:
SM-A325F: tested by @Long266 .
SM-A325M: tested by @Melky777 .
SM-A325N: not tested.
Bugs known so far:
TWRP cannot decrypt userdata if you set lockscreen. (one said it works, other it doesn't, so idk I'll just leave it here, YMMV)
Flashing anything shows many "unlock" red lines. (They are currently harmless by our knowledge).
USB-OTG
<!> There can be many more bugs unknown to me and testers. Report as soon as you face problem.
<!> PSA: I don't have the device to verify some of these bugs.
Download:
TWRP (3.7.0): https://github.com/almondnguyen/twr...a32-20230208/TWRP-3.7.0_12.1-a32-20230208.tar
Samsung USB Driver: https://developer.samsung.com/mobile/android-usb-driver.html
Odin (3.14.4): https://samfw.com/Odin/Samfw.com_Odin3_v3.14.4.zip
Disable VBMeta: https://forum.xda-developers.com/at...236537/?hash=f7249adaefe16f3aeac3256a63063f0a
(Optional) Root using Magisk: https://github.com/topjohnwu/Magisk/releases/
Install:
If you have TWRP or any custom recovery installed and bootable, you can upgrade instead; Look below.
<!> the installation will require WIPING DATA. You will also lose access to all Knox-based solutions like Secure Folder.
Backup every precious data you have on your phone.
<!> PC is required. Windows is preferred. (You probably know what you are doing when using Linux/Heimdall. We don't talk about Macs)
Unlock Bootloader:
Go to Settings > About Phone > About Software. Tap build number (10 times) until "you are now a developer" toast shows up.
Go back, go to Developer Settings.
Turn on OEM unlock toggle.
Turn off your phone, hold vol-up + vol-down, then plug in charging cable (please don't use 3rd-party charging-only cable, it must have data transfer capability).
Your device will boot into download mode with a warning. Accept it.
Hold volume-up until the phone shows the bootloader unlock panel "Unlock Bootloader?".
Press volume-up again. Now your phone bootloader is unlocked.
<!> It will now begin the process of wiping data. Let it do its job.
‎
When it reboots to OS, finish setting up your device.
Double check to make sure OEM Unlock is still ON.
‎ ‎
 
Preparing for the installation:
Download everything above onto your PC.
Install Samsung USB Driver.
Open Odin.
Connect your phone to your PC. There should be a COM entry on the top.
Make sure your phone is in Download Mode. (see step 4 of section Unlock Bootloader)
Make sure that OEM LOCK and REACTIVATION LOCK on your screen show "OFF". If it's not off, DO NOT PROCEED ANY FURTHER.
<!> For those with lock ON, use your device for 7 days without rebooting once. Then check the locks above again.
‎  
 
Installing:
Ensure phone is in Download mode.
In Odin:
Load in Userdata: VBMeta_disabler.tar file.
Load in AP: TWRP TAR file.
Prepare yourself. keep your hand on Volume-up and Power button (don't press yet).
In Odin, press Start. It will flash, then reboot. When the screen turned off, quickly press Vol-up and Power button to boot to recovery (this should take about 20~30 seconds).
<!> You should have TWRP up and running now.
‎  
 
Post-Installation:
MUST: Trigger Multi-disabler.
In TWRP, go to Advanced > Terminal.
Type multidisabler, then enter. If it fails with something about vendor free space, run it again.
Run multidisabler again.
Go to main screen. go to Wipe > Format Data, type yes then swipe.
Reboot to Recovery. Now you can do other stuff.
 
Should: Backup all vital partitions:
In TWRP, go to Backup
Backup: EFS, Modem, NVRAM.
Enjoy: Reboot your phone to have a rooted stock, install custom stuff or do whatever you want.
Upgrade:
<!> Use when you already have any custom recovery installed (TWRP, SHRP, Ofox and the likes)
Download the tar recovery image, then extract it to get recovery.img
Copy it to phone, then reboot to TWRP (Combo is Power + Volume-up)
Go: Install > Install image > select recovery.img file > select Recovery
Swipe to confirm flashing.
If success, reboot to recovery.
<!> You can also use Odin to upgrade, the steps similar to the Install section. All Post-installation, if already done, is unnecessary to do again.
GSI and related stuff:
GSI should be directly flashable now. Big credit to @Long266
Install TWRP, do all the instructions.
Download a GSI. Phh's is a good start.
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
If downloaded a compressed file (the extension is not .IMG; e.g: `gsi.img.gz` ), extract it to get an IMG file. Copy the IMG file to your phone.
Reboot into TWRP.
Tap Install > Install Image > Select your GSI .img file.
Select System Image, then flash.
If previously you were on stock, Wipe > Format data.
Reboot System.
Profit.
Source codes:
Kernel: https://github.com/long266/android_kernel_samsung_a32/tree/s
TWRP device: https://github.com/almondnguyen/twrp_device_samsung_a32/tree/twrp-12.1
Credits:
Devs involved in the making and maintaining of TWRP, twrpdtgen, Magisk and base software.
All the Testers.
@Long266 as tester, collab-dev.
@ianmacd for multidisabler.
@afaneh92 for a32x base tree and MTK-Samsung multidisabler.
@dronkit and @Mighty_Rearranger for Magisk-IMEI fix on MTK devices.
@klfld for GSI installation guide.
Older Release(s):
TWRP 3.6.2_12.1-20220703: https://github.com/almondnguyen/twrp_device_samsung_a32/releases/tag/TWRP-3.6.2_12.1-a32-20220703
TWRP 3.6.2_12.1-20220528: https://github.com/almondnguyen/twrp_device_samsung_a32/releases/twrp-3.6.2_12.1/
TWRP 3.6.1_11: https://github.com/almondnguyen/android_OTA/releases/TWRP-3.6.1_11-a32-B20220324
Footer Infos:
Status: Beta
Current Stable Version: 3.7.0_12.1
Created: 2022-03-24
Last Updated: 2022-07-03

chmod 550 /mnt/vendor/nvdata/md/NVRAM/NVD_IMEI must run on OS, not TWRP, since TWRP cannot mount /mnt

I can't install large IMG files to internal memory? For example a gsi?

Melky777 said:
I can't install large IMG files to internal memory? For example a gsi?
Click to expand...
Click to collapse
I should clarify that I don't own the device and all the testing was/is done by @Long266 .
These specific questions should be inquired to him instead (on his thread here: https://forum.xda-developers.com/t/...hawk-recovery-project-3-1-2021-03-24.4420469/ ).
Anyways, the bug that you are mentioning means that you can't flash images FROM internal SD card. GSI and image stuff should be flashable from other places like external SD or cache. Zip files are so far working as intended (as is they are flashable from anywhere).
To be fair, there could be flaws in his testing methodology and you should try it yourself.

Thanks Bro
I will owe the test of the A325M. I have no SD card at the moment.

Build 2022-03-25 changes:
Add backup entry for NVRAM, so in case Magisk messes up you still have a working copy intact.
Fix flashing image causing file size exceeded limit.

Updated TWRP Link, previously pointing to dead end.

It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!

Melky777 said:
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!
Click to expand...
Click to collapse
can u send recovery.log ?

Melky777 said:
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!
Click to expand...
Click to collapse
just skip NULL errors

How to update the TWRP version if it is already installed?
Is it enough to just flash the new TWRP version in Odin?
Or do I need to do the same steps as with the first installation (i.e. multidisabler, etc)?

YellowSM said:
How to update the TWRP version if it is already installed?
Is it enough to just flash the new TWRP version in Odin?
Or do I need to do the same steps as with the first installation (i.e. multidisabler, etc)?
Click to expand...
Click to collapse
You can use the "install Image" under TWRP.
From the <!> For more info part, download .img file instead, copy it to your phone. Then go to TWRP > Install > Install Image > select TWRP img > select Recovery to flash.
If you've done, Post-installation steps are unnecessary to do again.
edit: upgrade section added to main post.

How to deactive KC Client and
Knox Enrollment Service?

Hi, I wanted to try a GSI with this, is it safe to try it? Thanks for developing this TWRP, I can help with testing too.

Okay, I tested flashing phh's AOSP GSI, TWRP doesn't have the entry to flash to the dynamic partitions (system, vendor, product, etc). It can flash only to the super partition. Tried to flash the GSI there just in case, but i get a bootloop obviously. Restored successfully through ODIN. I wont test magisk because I don't want to lose IMEI.

klfld said:
Okay, I tested flashing phh's AOSP GSI, TWRP doesn't have the entry to flash to the dynamic partitions (system, vendor, product, etc). It can flash only to the super partition. Tried to flash the GSI there just in case, but i get a bootloop obviously. Restored successfully through ODIN. I wont test magisk because I don't want to lose IMEI.
Click to expand...
Click to collapse
try flashing via fastboot!
I saw a video of a Brazilian doing it on the A22

Long266 said:
can u send recovery.log ?
Click to expand...
Click to collapse
On the same day I removed the twrp and blocked the bootloader.

Melky777 said:
try flashing via fastboot!
I saw a video of a Brazilian doing it on the A22
Click to expand...
Click to collapse
I could install the Lineageos 19.1 GSI! I had to use this zip as a workaround ChonDoe_Flasher.zip, that allows flashing dynamic partitions even if the TWRP doesn't. I also made a treble overlay for this device (vendor.img), that fixes power profiles and all this stuff, ill upload it now if anyone is interested.
To flash the GSI you have to rename the .img file to system.img, put it in the same location than the zip and flash the zip. I have the scripts inside the zip to check if it didnt do anything weird and the source code seems safe, tried two GSIs today.
What doesnt work with the Lineage GSI or phh's AOSP is MTP and the fingerprint reader. Also i can't get encryption to work, the GSI crashes if i don't use multidisabler to remove encryption from the fstab. Everything else works flawlessly from my testing.
For file transfer i'm using ADB with this tool, it's even faster than MTP somehow Python ADB File Explorer
EDIT: Uploaded vendor.img with the overlay for this device, ill push the changes to github later.
Download here: vendor.img

klfld said:
I could install the Lineageos 19.1 GSI! I had to use this zip as a workaround ChonDoe_Flasher.zip, that allows flashing dynamic partitions even if the TWRP doesn't. I also made a treble overlay for this device (vendor.img), that fixes power profiles and all this stuff, ill upload it now if anyone is interested.
What doesnt work with the Lineage GSI or phh's AOSP is MTP and the fingerprint reader. Also i can't get encryption to work, the GSI crashes if i don't use multidisabler to remove encryption from the fstab. Everything else works flawlessly from my testing.
Click to expand...
Click to collapse
Very good job!!!
Makes a topic, I think I'm not the only one who wants to install a GSI.

Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy S21 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 S21 FE 5G G9900 and G990B.
Download & Guide:
1. Unlock your bootloader.
2. Download S21 FE 5G: r9q.
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.
- Haptic feedback is currently not working.
Thanks:
TWRP team
@ianmacd for multidisabler
@Dan_FFM (David Dean) for testing and fix touch
Sources:
Kernel tree
Device tree

Changelog:
01.05.2022 - Initial Release.

Tested on BVB3 and CVC6 roms, both are working perfect.
On CVC6, wiping data worked and multidisabler seems to be working too. My phone is rebooting and after all data recover I can tell if it done well completely.
Edit : backup is working, install zip is working, to me there is no bug. Just one weird thing, after the update I directly installed TWRP, it worked fine. Then decrypted data and reboot. When finished, I wanted to reboot recovery via Vol Up and power, it always boot up to system, I née needed to reflash TWRP to access it again.
Except this little thing, it works great.
Many many thanks !!

Great cant wait to test whenever I got some time to clear it all and start over :/

Any1 who tested yet?

How do I unlock my bootloader?

Mr NI said:
How do I unlock my bootloader?
Click to expand...
Click to collapse
If you bought a US Version, i.e. Carrier brands, you cannot do so, even if you have an unlocked. All US Snapdragon device after like S6 they've kicked us out. If you have a Exnos.
1. Open Settings scroll to about device
2. Tap on Software Information tap build number 5 times to show hidden developer settings.
3. Scroll to you see OEM Unlock.
4. Refer to guides online after step 3

Dr.Lost said:
If you bought a US Version, i.e. Carrier brands, you cannot do so, even if you have an unlocked. All US Snapdragon device after like S6 they've kicked us out. If you have a Exnos.
1. Open Settings scroll to about device
2. Tap on Software Information tap build number 5 times to show hidden developer settings.
3. Scroll to you see OEM Unlock.
4. Refer to guides online after step 3
Click to expand...
Click to collapse
well isnt that ass

Doghan13 said:
Tested on BVB3 and CVC6 roms, both are working perfect.
On CVC6, wiping data worked and multidisabler seems to be working too. My phone is rebooting and after all data recover I can tell if it done well completely.
Edit : backup is working, install zip is working, to me there is no bug. Just one weird thing, after the update I directly installed TWRP, it worked fine. Then decrypted data and reboot. When finished, I wanted to reboot recovery via Vol Up and power, it always boot up to system, I née needed to reflash TWRP to access it again.
Except this little thing, it works great.
Many many thanks !!
Click to expand...
Click to collapse
I am considering buying the smartphone. But the root access ist important for me.
Need you to enter twrp again to have root access after a restart and a connection to pc to enter twrp? I ask because my Galaxy A50 loose after every restart the root access and I need to enter the twrp with a connection to pc to fix it.

icalgoos said:
I am considering buying the smartphone. But the root access ist important for me.
Need you to enter twrp again to have root access after a restart and a connection to pc to enter twrp? I ask because my Galaxy A50 loose after every restart the root access and I need to enter the twrp with a connection to pc to fix it.
Click to expand...
Click to collapse
When you make all right, unlock bootloader, twrp, vb_disabler and then magisk. Then you have a rooted phone with advantages and disadvantages. No loosing after reboot. But no OTA too

Does nandroid backups work with this version and android 12?

how can we update the phone say to OneUI 5.0 in the future and keep root.

stuntora said:
how can we update the phone say to OneUI 5.0 in the future and keep root.
Click to expand...
Click to collapse
Patch the fw with Magisk, use Magisk install instructions and possibly replace recovery.img with TWRP so that you keep it and flash any multi disabler again that you may have already flashed.

Is it mandatory to format data when we already have Magisk installed ?

If you are full stock, then disabling vbmeta will trigger a wipe

afaneh92 said:
If you are full stock, then disabling vbmeta will trigger a wipe
Click to expand...
Click to collapse
Just a thought, I have stock ROM october patch and I have Magisk installed properly with Zygisk activated.
I obviously already done a full wipe for this.
If one day I would like to install TWRP, a full wipe will be mandatory ?
I'm asking since I understand that full stock means no Magik installed, which is not my case.

Benjamin2557 said:
Just a thought, I have stock ROM october patch and I have Magisk installed properly with Zygisk activated.
I obviously already done a full wipe for this.
If one day I would like to install TWRP, a full wipe will be mandatory ?
I'm asking since I understand that full stock means no Magik installed, which is not my case.
Click to expand...
Click to collapse
Yes its mandatory

does smali patcher work on rooted galaxy s21 fe?

Hello Mohammad,
After rooting I keep getting "ERR_INTEGRITY" errors in logcat, so some apps (especially Samsung ones) don't work properly. Is it normal since you wrote "Encryption not fully working", or am I doing something wrong?
Thank you!

MoveToZero said:
Hello Mohammad,
After rooting I keep getting "ERR_INTEGRITY" errors in logcat, so some apps (especially Samsung ones) don't work properly. Is it normal since you wrote "Encryption not fully working", or am I doing something wrong?
Thank you!
Click to expand...
Click to collapse
Usually because bootloader unlocked, use safetynet fix module.

Development [OFFICIAL]TWRP for the Motorola G30 (caprip)

{
"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:
#include <std_disclaimer.h>
/*
* 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.
*/
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch-driven user interface, with 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open-source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
This is for UNOFFICIAL builds of TWRP for the Motorola G30 (caprip)
Device Config:
GitHub - TeamWin/android_device_motorola_caprip
Contribute to TeamWin/android_device_motorola_caprip development by creating an account on GitHub.
github.com
Official Downloads:
https://twrp.me/motorola/motorolamotog30.html
Test Downloads:
https://osdn.net/projects/twrp-for-caprip/releases/
Installation:
Backup everything important off of your device
Make sure your bootloader is unlocked
Download the recovery image (and optionally the TWRP installer zip) from above
Reboot into bootloader
Run this command (Change the .img to whatever the name of the file is you downloaded):
Code:
fastboot boot twrp.img
(Optional instructions from this point on) Install TWRP installer zip
Reboot to recovery
Upgrade / Reinstall TWRP instructions
Download desired TWRP installer zip version
Reboot to recovery
Select Install
Tap on install and select the TWRP installer zip you downloaded from step one
Reboot to recovery and confirm that the updated version of TWRP is installed
Nandroid backup/restore
Have an available microSD Card or USB OTG drive
Backup boot, dtbo, system image, vendor image and data (optionally any other partitions you want a backup of) to your external storage device of choice
Once you wish to restore? Reboot to TWRP and format data (Wipe > "format data" button > type yes > keyboard checkbox)
Reboot to TWRP
Restore boot, dtbo, system image and vendor image
Reboot to system
Once it boots to the system without issues? Do not set any lockscreen security and reboot to TWRP
Restore data
Reboot to system
After it finishes boot? Your data and ROM will be restored but sometimes the UI might be incorrect, so reboot to the system again
For the TEST builds of TWRP? Please let me know if this works. If so? I will submit it to Gerrit for official updates.
Credits:
mistersmee for his TWRP tree for the Motorola Moto G9 Power (cebu) that this caprip tree is based upon
Samw662 for encouraging me to work on this and help out caprip owners since I don't own one plus testing these builds

Heyyo, initial public release is twrp-3.6.2_12-0_UNOFFICIAL-20220929-03-caprip which is based on TWRP 12.1 branch. Please test decryption on either A12 or A13 ROMs as I'm unsure if it is setup correctly or not.
Please report any bugs in this thread

Hey, I cannot see my internal storage on this version of twrp. I am on android12 srtock rom

Heyyo @anuragnahata , can you please test this?
https://build.twrp.me/twrp-3.7.0_12-0-caprip.img
Code:
fastboot boot twrp-3.7.0_12-0-caprip.img
If you have any problems with this build too, then please submit logs either here or in PM. I've had other caprip owners say everything on that TWRP build works fine for them

Touchscreen doesn't work. Maybe because my software channel is reteu?

Heyyo, TWRP 3.7.0_12 official is meow up on the TWRP website! Thanks to @Sammm77 for encouraging me to work on this for a device I don't even own and for helping test it out.
@Leogami9009 can you please provide logcat? Tbh I'm not even sure what are all the touchscreen drivers that caprip even uses but I did try to reference the kernel source code but maybe I missed one? Also, are you on the official build or a test build?

ThE_MarD said:
Heyyo, TWRP 3.7.0_12 official is meow up on the TWRP website! Thanks to @Sammm77 for encouraging me to work on this for a device I don't even own and for helping test it out.
@Leogami9009 can you please provide logcat? Tbh I'm not even sure what are all the touchscreen drivers that caprip even uses but I did try to reference the kernel source code but maybe I missed one? Also, are you on the official build or a test build?
Click to expand...
Click to collapse
For some people ek touch does not work, but for the vast majority it works perfectly. You have to wait 15 seconds when starting TWRP but after that it works fine. Excellent work friend.

Leogami9009 said:
Touchscreen doesn't work. Maybe because my software channel is reteu?
Click to expand...
Click to collapse
No, it's not because of your channel, surely the developer skipped a display driver. Maybe with time we will solve it, if you want to contribute send logcat and dmesg to the developer.

@Sammm77 if touchscreen doesn't work right away? Odds are it's just the touchscreen driver still initializing and maybe checking firmware and such. Focaltech for example is really known for having touchscreen issues as well on TWRP because of a long init period. Some touchscreens have a way to manually reset the kernel driver I think but I'm unsure if caprip has a method to do so.
My Asus Zenfone 5z (Z01R) has focaltech touchscreen and has issues with TWRP where sometimes it's intermittent that touchscreen works but it always works in the ROM since the ROM boot time is a lot longer than TWRP

Ok, i let the phone to load the driver and it works, thank you all!

Is it normal for this recovery to not be able to resize system/ not being able to enter on internal storage?

ThE_MarD said:
@Sammm77 if touchscreen doesn't work right away? Odds are it's just the touchscreen driver still initializing and maybe checking firmware and such. Focaltech for example is really known for having touchscreen issues as well on TWRP because of a long init period. Some touchscreens have a way to manually reset the kernel driver I think but I'm unsure if caprip has a method to do so.
My Asus Zenfone 5z (Z01R) has focaltech touchscreen and has issues with TWRP where sometimes it's intermittent that touchscreen works but it always works in the ROM since the ROM boot time is a lot longer than TWRP
Click to expand...
Click to collapse
No, it doesn't load right away, that would be great but it doesn't. You have to wait a few seconds. Do you think that can be solved?

Leogami9009 said:
Is it normal for this recovery to not be able to resize system/ not being able to enter on internal storage?
Click to expand...
Click to collapse
internal storage must be decrypted. Maybe later I'll make a tutorial on how to do that.

Heyyo, well it seems there's some communication breakdown as I was under the impression that decryption worked but I guess it doesn't lol oof.
Ok, can someone who is decrypted please try to decrypt and when it fails send me the recovery.log and logcat?
(No replies? Maybe decryption does actually work and there's some more miscommunication???)

Sorry for the long waiting, but i forgot to get the logcat and recovery.txt. I tried today to get it, but i wasn't able to. it says that it was saved in data/media/ so i tried to get it with adb pull but it says "failed to stat remote object 'data/media/logcat.txt': Permission denied". But i think i should mention that i've installed twrp by flashing the .zip with termux (my phone was rooted with magisk and it had the magic flasher module). I installed it this way because the booted .img touchscreen didn't worked even if i let it some minutes for the driver to load. And when i've flashed the .zip with termux my device wasn't rooted anymore. So i can't use adb root. But when i flash the patched boot.img back, the recovery just disappears.
Sorry for bad english

@Leogami9009 hmm, maybe it's just because of the prebuilt kernel? Not too sure though tbh but I think there's kernel source code somewhere so I might see if that would help? From what I saw from Motorola's source code release there was only like, 2 drivers they used for touch

ThE_MarD said:
@Leogami9009 hmm, maybe it's just because of the prebuilt kernel? Not too sure though tbh but I think there's kernel source code somewhere so I might see if that would help? From what I saw from Motorola's source code release there was only like, 2 drivers they used for touch
Click to expand...
Click to collapse
That's why twrp doesn't work on ilitek screens, on this device.

@Leogami9009 I think I just realized you're trying to get some logcat.txt on the device, but you should be using a PC or something to get logcat like this:
Via Windows PowerShell:
Code:
adb logcat | Tee-Object logcat.log
Via Linux Terminal:
Code:
adb logcat | tee logcat.log
And whatever folder you are in when you run it will have that logcat.log
Also, which build of TWRP are you on?
Plus twrp-installer.zip is meant to be installed whilst in recovery and not while booted into the system. Installing TWRP does remove root so if you want to maintain that you must reinstall it after rebooting to recovery.

Here is the logcat, i let it for 5 minutes:
I have twrp 3.7.0, i realized yestarday that if i root with twrp i can have both root and the recovery, and i tried to flash the zip with the twrp already installed ( nothing different)
Something intresting is that if i format data with twrp and reboot in recovery, it detects the internal storage (when i try to select the internal storage it says it has 15000mb or something like that), but after i set up the phone, it says 0mb. Maybe is something about the partition format? Idk, i can put a sd card to see if it gets detected or not.
Another thins is that when twrp starts it says "Unable to mount storage" and "Unable to mount /data/media/TWRP/.twrps" two times and when i try to manually select the Internal Storage and data partition and format those it says "Unable to mount 'data' (Invalid argument)" "Unable to wipe /data."

ahoy, the release version does not work on my phone, also EU, build S0RCS32.41-10-9-2
I mean, I fastboot boot twrp-3.whatever.img and it boots to that, but touchscreen doesn't work, and adb doesn't work, only thing I can do is turn screen on-off, lol, even after waiting several minutes
also the kernel sources are iirc like, on github, under various tags and branches

Development [Recovery] [a32] OrangeFox Recovery Project [Stable-ish, 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"
}
Code:
/*
*Disclaimer
*
* 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 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.
*/
Introduction
OrangeFox Recovery is one of the most popular custom recoveries, with amazing additional features, fixes and a host of supported devices
OrangeFox version: R11.1
For device: a32
Maintainer: Ahnet ( @Captain_cookie_200 )
OrangeFox source:
OrangeFox Recovery · GitLab
OrangeFox Recovery | OFR
gitlab.com
Device tree:
GitHub - Epico-Bot/ofox_device_samsung_a32: Device tree for building OrangeFox Recovery for Samsung Galaxy A32 4G (MTK), based on A325FXXU2BVD6.
Device tree for building OrangeFox Recovery for Samsung Galaxy A32 4G (MTK), based on A325FXXU2BVD6. - GitHub - Epico-Bot/ofox_device_samsung_a32: Device tree for building OrangeFox Recovery for Sa...
github.com
Kernel Source: https://github.com/ahnet-69/android_kernel_samsung_a32-recovery
Features:
Code:
Synced with the latest Teamwin changes
Designed with latest Material design 2 guidelines
Implemented support for Flyme and MIUI OTA, and incremental block-based OTA in custom ROMs
Included assorted customizations
Inbuilt patches, like Magisk and password reset patch
Several addons
Password protection
Fully open-source
Frequently updated
Status
Stable-ish
Tested on:
SM-A325F (by me)
SM-A325M (by @filipedonato)
other models unknown. But should work.
Please report back so i can update the op
Downloads
Click here.
Bugs
1. TWRP cannot decrypt userdata if you set lockscreen. (someone said it works, other it doesn't, so I'll just leave it here, YMMV)
2. Flashing anything shows many "unlock" red lines. (They are currently harmless by our knowledge).
3.USB-OTG
4. Saving settings is fixed but for fixing settings such as theming resetting on reboot is by editing the bootable/recovery/twrp.cc and at line 396 (as of now) changing the bool to true. This makes the recovery load the themes twice. This should only be for encrypted devices but since it has fixed our issue we'll use this workaround until a proper solution has been found.​
Installation
Code:
If you have TWRP or any custom recovery installed and bootable, you can upgrade instead; Look below.
<!> the installation will require WIPING DATA. You will also lose access to all Knox-based solutions like Secure Folder.
Backup every precious data you have on your phone.
<!> PC is required. Windows is preferred. (You probably know what you are doing when using Linux/Heimdall. We don't talk about Macs)
Unlock Bootloader:
1. Go to Settings > About Phone > About Software. Tap build number (10 times) until "you are now a developer" toast shows up.
2. Go back, go to Developer Settings.
3. Turn on OEM unlock toggle.
4. Turn off your phone, hold vol-up + vol-down, then plug in charging cable (please don't use 3rd-party charging-only cable, it must have data transfer capability).
5. Your device will boot into download mode with a warning. Accept it.
6. Hold volume-up until the phone shows the bootloader unlock panel "Unlock Bootloader?".
Press volume-up again. Now your phone bootloader is unlocked.
<!> It will now begin the process of wiping data. Let it do its job.
7. When it reboots to OS, finish setting up your device.
8. Double check to make sure OEM Unlock is still ON.
 
Preparing for the installation:
1. Download everything above onto your PC.
2. Rename OrangeFox recovery img file to recovery.img and add it to archive using any archiver and select gnu tar.
3. Install Samsung USB Driver.
4. Open Odin.
5. Connect your phone to your PC. There should be a COM entry on the top.
6. Make sure your phone is in Download Mode. (see step 4 of section Unlock Bootloader)
7. Make sure that OEM LOCK and REACTIVATION LOCK on your screen show "OFF". If it's not off, DO NOT PROCEED ANY FURTHER.
<!> For those with lock ON, use your device for 7 days without rebooting once. Then check the locks above again.
‎  
 
Installing:
1. Ensure phone is in Download mode.
In Odin:
Load in Userdata: VBMeta_disabler.tar file.
Load in AP: OrangeFox TAR file.
2. Prepare yourself. keep your hand on Volume-up and Power button (don't press yet).
3. In Odin, press Start. It will flash, then reboot. When the screen turned off, quickly press Vol-up and Power button to boot to recovery (this should take about 20~30 seconds).
<!> You should have OrangeFox up and running now.  
 
Post-Installation:
MUST: Trigger Multi-disabler.
1. In OrangeFox, go to Terminal.
2. Type multidisabler, then enter. If it fails with something about vendor free space, run it again.
3. Run multidisabler again.
4. Go to main screen. go to Wipe > Format Data, type yes then swipe.
5. Reboot to Recovery. Now you can do other stuff.
 
Should: Backup all vital partitions:
1. In OrangeFox, go to Backup
2. Backup: EFS, Modem, NVRAM.
Enjoy: Reboot your phone to have a rooted stock, install custom stuff or do whatever you want.
Upgrade:
<!> Use when you already have any custom recovery installed (TWRP, SHRP, PBRP and the likes)
1. Download the recovery image.
2. Copy it to phone, then reboot to OrangeFox (Combo is Power + Volume-up)
3. Go: Install > select recovery.img file > select Recovery
4. Swipe to confirm flashing.
5. If success, reboot to recovery.
<!> You can also use Odin to upgrade, the steps similar to the Install section. All Post-installation, if already done, is unnecessary to do again.
Credits:
To the OrangeFox and TWRP team and everyone involved in making this all work.
@Long266 For his kernel and amazing work.
@ianmacd For multidisabler.
@afaneh92 For his a32x base tree and MTK-Samsung multidisabler.
@KrutosVIP For his experimental lineage kernel source from here.

reserved

reserved

I have tried to talk to various developers about the settings not saving issue. They have no idea. I have myself tried playing around with the tree but nope. So unless someone has a fix for this i have no idea

New Build!
Whats new?
Fixed the settings such as theming resetting on reboot by editing the bootable/recovery/twrp.cc and at line 396 (as of now) changing the bool to true. This makes the recovery load the themes twice. This should only be for encrypted devices but since it has fixed our issue we'll use this workaround until a proper solution has been found.
If you see the recovery trying to decrypt storage dont worry about it. its just because of this. It does nothing.

It's stable? I mean, i can install gsi's and zips?

ApiYoshi said:
It's stable? I mean, i can install gsi's and zips?
Click to expand...
Click to collapse
yes i use orangefox. flashing gsi works fine. same goes with zips

Captain_cookie_200 said:
yes i use orangefox. flashing gsi works fine. same goes with zips
Click to expand...
Click to collapse
Ok, i flashed it and is awesome!! Thanks for great work brother!

ApiYoshi said:
Ok, i flashed it and is awesome!! Thanks for great work brother!
Click to expand...
Click to collapse
You should make a telegram group

ApiYoshi said:
You should make a telegram group
Click to expand...
Click to collapse
i dont really know on how to maintain one. me and someone else made it but its sitting dead i'll see later on. and i'll post a thread abt it if there are any updates

Works in A32 A325M Brazil variant.

really nice you are keeping the a32 alive!

applesucksLmao said:
really nice you are keeping the a32 alive!
Click to expand...
Click to collapse
i did nothing tbh. all the credit goes to the people who put effort in making twrp work i just copied and built it. all the credit goes to them

Captain_cookie_200 said:
i dont really know on how to maintain one. me and someone else made it but its sitting dead i'll see later on. and i'll post a thread abt it if there are any updates
Click to expand...
Click to collapse
Ooh, i undertand

One question, you will update the recovery when an update came out?

ApiYoshi said:
One question, you will update the recovery when an update came out?
Click to expand...
Click to collapse
yes i will try

Where do I get the orange fox TAR, I see it in the steps but I don't see it to download it

Seth Ofc said:
Where do I get the orange fox TAR, I see it in the steps but I don't see it to download it
Click to expand...
Click to collapse
sorry i didnt include it. but i think i specified. rename OrangeFox recovery img file to recovery.img
then use 7zip or winrar or any other archiver and then add to archive. There select tar and compress. I'll include tar files in next builds by default

Thanks I already compressed the recovery.img to recovery.tar, do you know of any aosp rom for the a325m I was looking for but I can't find it

Seth Ofc said:
Thanks I already compressed the recovery.img to recovery.tar, do you know of any aosp rom for the a325m I was looking for but I can't find it
Click to expand...
Click to collapse
use a generic system image.
if you want heres a list: here