Database Info

[RECOVERY][UNOFFICIAL][Jasmine] TWRP 3.2.3.0 17-9-2018

{
"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 (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
https://drive.google.com/open?id=10i5ddHcV0lt8JJ7nV1bJjqc1XXjLCp8n
Note this is just a hobby, but feel free to report bugs.
Kernel source: Prebuilt stock kernel
Boot to fastboot ( volume down and power )
in fastboot type:
Link comes later when stable
fasboot reboot and hold power up and volume
Click to expand...
Click to collapse
Note: this twrp is working with the orginal system, when ota happens just flash twrp again.
BUGS:
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Contributors
@bassbounce ( Compiled )
@Manish4586 ( Device tree )
Device tree: https://github.com/Manish4586/android_device_xiaomi_jasmine-twrp
Source Code: https://github.com/omnirom/android_bootable_recovery/
Version Information:
Status: testing
Created 17-9-2018
Last Updated 17-9-2018

Nice! So this is supposed to work without A/B conflicts - unlike the other TWRP project?
Edit: Awesome! This works great so far. I now have permanent TWRP on my device. It updates partition details perfectly and I was able to flash Magisk without an issue.
Thanks a lot for your work!

thedisturbedone said:
Nice! So this is supposed to work without A/B conflicts - unlike the other TWRP project?
Click to expand...
Click to collapse
U are right, this twrp just boots the stock android, the other did not do that.

bassbounce said:
U are right, this twrp just boots the stock android, the other did not do that.
Click to expand...
Click to collapse
Thank you. Edited my initial post with results. This would open our device to a lot of possibilities.

I have September update, can i install this?

ki69 said:
I have September update, can i install this?
Click to expand...
Click to collapse
I dont know, i didnt test it on the september .

bassbounce said:
Yes, it should be no problem.
Click to expand...
Click to collapse
Thanks man, can you build it for mi a2 lite (daisy) ?

Touch screen don't work
After flash twrp touch screen don't work
My device rooted and install magisk

s.arthit1993 said:
After flash twrp touch screen don't work
My device rooted and install magisk
Click to expand...
Click to collapse
Try flashing stock boot img

This is work for my Mi A2 Rooted Whit Magisk V17.1 ?

Unfortunately, I'm not a developer.
Can someone compile the code and make an available download for this image, please?
Many Thanks!

MMN said:
Unfortunately, I'm not a developer.
Can someone compile the code and make an available download for this image, please?
Many Thanks!
Click to expand...
Click to collapse
same problem here, I don't know how to download or install it, I would like to try it

Adairo said:
same problem here, I don't know how to download or install it, I would like to try it
Click to expand...
Click to collapse
Fastboot flash boot file.img
Restart phone and boot in to recovery volume up and power key.
If it works please report here,
I don't know if twrp works with the September update which is pulled back.
Also I need a 6gb 128 a2 to test this.

DOWNLOAD:
Some ppl reported touch problems we look in to that
Dont download yet

nvm

wi-fi does not work

bassbounce said:
Fastboot flash boot file.img
Restart phone and boot in to recovery volume up and power key.
If it works please report here,
I don't know if twrp works with the September update which is pulled back.
Also I need a 6gb 128 a2 to test this.
Click to expand...
Click to collapse
You have changed the file. The difference is enormous. Which one is correct?
-> twrp-jasmine-0.1.img (27.276kb) -> Link removed in the cited post
-> boot.img (37.252kb) -> Link in post #1
Mi A2 6/128GB is here.
dimaxxxxx said:
wi-fi does not work
Click to expand...
Click to collapse
And yes: wifi does not work on both images

WiFi not working, help please.

Testing without wifi:
* Magisk v17.1 (via TWRP/zip) -> works
* SuperSU (via Magisk) -> works
* SELinux-Manager (via TWRP/zip) and go to permissive mode -> works
* xposed (xposed-v90.2-sdk27-beta3, via TWRP) -> bootloop - I'll try direct installation through Magisk when wifi works.
What's about error message when deleting the cache in TWRP:
unable to find partition for path '/cache'?

To all restore the stock boot.img. To fix it
We need to find a solution. Don't flash the twrp.

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

Changelog:
30.11.2021 - Update to TWRP 3.6.0
- Update multidisabler
25.01.2021 - Initial Release

Will this work on 860 wifi model?

Techguy777 said:
Will this work on 860 wifi model?
Click to expand...
Click to collapse
You can try but not sure if it will boot.
I will add support to WIFI model soon.

On T865 LTE + TWRP + Android 11 doesn't boot. Tried everything nothing works

Zer0Sense said:
On T865 LTE + TWRP + Android 11 doesn't boot. Tried everything nothing works
Click to expand...
Click to collapse
That's because this twrp is meant for 867 model you need the twrp. Here's what your looking for we already know it works people have used it. You have to stay plugged into pc after Odin flashing to boot into recovery on android 11 one ui. If you need anything let me know
[Recovery][Official] TWRP 3.4.0-15 [T860/5][22.Jul.2020]
Official TWRP 3.4.0 for SM-T860 + SM-T865 Telegram thread Built using OMNI source 9.0 TWRP v3.4.0 See post #2 for install steps Changelog... v1 Initial build MTP, OTG and SDcard all working Encryption not working, but being...
forum.xda-developers.com

No I used proper TWRP for T865 not this. I found no other place to ask how to make it work on android 11 and not get into bootloop

Zer0Sense said:
No I used proper TWRP for T865 not this. I found no other place to ask how to make it work on android 11 and not get into bootloop
Click to expand...
Click to collapse
so you didnt mentioned that and asked! Im glad that I didnt answered you yesterday.

Ok I solved this with modified vbmeta_disabled in case somebody has the same problem.

afaneh92 said:
You can try but not sure if it will boot.
I will add support to WIFI model soon.
Click to expand...
Click to collapse
does your 3.6.0 have the wifi support for S6-T860? Im seeing android 12 coming up soon and I dont think 3.4 will work like on my S10.

Techguy777 said:
does your 3.6.0 have the wifi support for S6-T860? Im seeing android 12 coming up soon and I dont think 3.4 will work like on my S10.
Click to expand...
Click to collapse
Idk, you cant test and see

afaneh92 said:
Idk, you cant test and see
Click to expand...
Click to collapse
Maybe I will, I found the restore on the S10 lite now. The way you said to slide the continue to restore made me unsure. I used to do everything and try it on devices but I quit doing that over the last 2 years because unfortunately almost everything doesn't work anymore. I thought if I swiped to restore it might start trying to flash my system without seeing my back ups and wipe my system out. Why after 5 years has it changed? Naturally I would assume it's not seeing my backups not that it's hidden. Than I read about people hard bricking their phones or tablets doing things that should work and it makes me nervous now. If I could buy a new flagship every year I wouldn't care I would try everything but the tab S6, S10 lite, and now poco F3 are the most expensive devices I've owned. So I'm not rolling in money.
My thoughts about this twrp is you made it for a mobile data unit not wifi. Well on the tab a they used the lte source code and it ruined the EFS partition. Because it's meant for lte and it screws up Bluetooth and EFS. Aside from that it did work as long as you didn't wipe EFS. So now I would have to risk my tab S6 to try. If it just bootloops I don't care

Zer0Sense said:
Ok I solved this with modified vbmeta_disabled in case somebody has the same problem.
Click to expand...
Click to collapse
So what twrp did you use for the LTE 865? There's the official 3.6.0 I'm hoping you were able to use that with vb meta disabled file. Could you explain in detail exactly what twrp from where and how you added the vb meta file or what you did. I would really appreciate it. If I can use the official with a vb meta disabled I would be happy thanks. Tell me how you used the vb meta file to

If you get time you should add wifi 860 support because Android 12 is out I need a twrp to decrypt it and make backups. At least all of that stuff still works on the tab s6 before slot a/b.

I really think your the only one that could make a twrp for the S6 860 wifi model because the other developer has deleted everything his files and his GitHub files with device tree and stuff. It's money is what it is developers rush out to be the first to make twrp and kernels for a top device in hopes of making money and then when it doesn't work out they just stop. That's what your doing to is unlocking bootloader's for money and than you want to make a twrp that way there's a reason to pay you to unlock the bootloader. If someone ask for ETAs or certain features it's always I do this for me and I do it for free and I don't want those features or I don't have the time there's the donations link. It's not for free it's for money that's why you guys make for devices you don't even own.

Techguy777 said:
I really think your the only one that could make a twrp for the S6 860 wifi model because the other developer has deleted everything his files and his GitHub files with device tree and stuff. It's money is what it is developers rush out to be the first to make twrp and kernels for a top device in hopes of making money and then when it doesn't work out they just stop. That's what your doing to is unlocking bootloader's for money and than you want to make a twrp that way there's a reason to pay you to unlock the bootloader. If someone ask for ETAs or certain features it's always I do this for me and I do it for free and I don't want those features or I don't have the time there's the donations link. It's not for free it's for money that's why you guys make for devices you don't even own.
Click to expand...
Click to collapse
Stop this useless off topics, If I worked on something there are two reasons. because its interesting for me.
Or someone paid for my time that I spend on interesting or challenging stuff.
I have a life too, I can say NO to you at some point.
So you cant push me to work on something even if you paid me or donated.

Zer0Sense said:
Ok I solved this with modified vbmeta_disabled in case somebody has the same problem.
Click to expand...
Click to collapse
Hey do you still use your Tab S6 SM-T865?
if so, can you tell me which steps you took to install TWRP and magisk.

Does anyone know how I can use a previous Android version backup ntwrp to flash over my unfortunate mistake of putting Android 12 4.1 on my tablet?

lincolnsxda said:
Does anyone know how I can use a previous Android version backup ntwrp to flash over my unfortunate mistake of putting Android 12 4.1 on my tablet?
Click to expand...
Click to collapse
That depends most likely not. What backup are you referring to? Is it android 11 or 10 or 9? You would basically have to say the firmware you were on and the firmware your on now.

It's Android 10

Alpha ROM (AOSP Android 11)

New Android 11 GSI ROM based on Phhusson's AOSP . Really good, stable enough to be used as your daily driver. No major bugs. Preinstalled SuperUser, Android Auto, smart "Keep Notes" etc...
Bored during quarantine? Try this great ROM!
Note: Tested on 9.1.0.132.
Credits: @berkay-gsi
Requirements: basically full stock EMUI 9.1, with stock recovery.
IMPORTANT! Before booting up the ROM, you will need to perform a factory reset in stock recovery!
1. Download system-alpha ROM
ROM
2. Extract the .img file from the compressed file.
3. Flash extracted system.img from fastboot , use command
fastboot flash system (file_name).img
4. Run command 'fastboot reboot', unplug your phone, when on the screen appears yellow warning, press and hold for 3 sec Volume Up . In eRecovery select 'Wipe data/factory reset'. Reboot .
NFC:
- Download NFC Patch
- Install
TWRP
over eRecovery (it makes things easier) - follow this
guide
- In TWRP unmount all except SD Card , Vendor and System (unmount and mount again)
- Flash nfc_universal_patch.zip
- From TWRP menu reboot into recovery and perform factory reset .
Note: you can flash NFC patch before booting up the ROM
How?
Tip: use "Simple Gallery"
download
Enjoy !
{
"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"
}

Some banking apps refuse to work on rooted devices, is it possible to use those on that rom?

CrystalCase said:
Some banking apps refuse to work on rooted devices, is it possible to use those on that rom?
Click to expand...
Click to collapse
-Alf- said:
Preinstalled SuperUser,
Click to expand...
Click to collapse

Thanks for the information! I do not want to break anything so I would like to follow a more detailed 'tutorial'. I did search for some, but I am not sure which I can use to install this particular rom. Is there one you can recommend? Like somthing for beginners?

CrystalCase said:
Thanks for the information! I do not want to break anything so I would like to follow a more detailed 'tutorial'. I did search for some, but I am not sure which I can use to install this particular rom. Is there one you can recommend? Like somthing for beginners?
Click to expand...
Click to collapse
No flashing instructions for beginners are offered, sorry. If you're here in this section, you should know what you're doing. More detailed guide can be found here and here .
Read the instructions carefully and completely, check unfamiliar terminology by google or xda.
The instructions do not perform, if you do not know what you're doing.
P.S.: keep in mind, that this ROM is rooted with build-in SuperUser , and you cannot turn off SuperUser!

-Alf- said:
No flashing instructions for beginners are offered, sorry. If you're here in this section, you should know what you're doing. More detailed guide can be found here and here .
Read the instructions carefully and completely, check unfamiliar terminology by google or xda.
The instructions do not perform, if you do not know what you're doing.
P.S.: keep in mind, that this ROM is rooted with build-in SuperUser , and you cannot turn off SuperUser!
Click to expand...
Click to collapse
Okay thanks. I kinda know what I am doing, at least I know what I want. My last time is some years ago on samsung devices so I am not into the new phoes but I will read some and go for it.

Hi Alf! Is always me ahaha.
Anyway I wanted to ask you if it makes sense to switch from LineageOS 18.1 to this one here, or they are the same (especially in terms of stability). I also would like to know if there is a way to avoid loosing the unlocked bootloader when I have to switch to stock firmware. Thank you

Anonymousxx said:
Hi Alf! Is always me ahaha.
Anyway I wanted to ask you if it makes sense to switch from LineageOS 18.1 to this one here, or they are the same (especially in terms of stability). I also would like to know if there is a way to avoid loosing the unlocked bootloader when I have to switch to stock firmware. Thank you
Click to expand...
Click to collapse
Hello, what about your exams stage? O.K.?

-Alf- said:
Hello, what about your exams stage? O.K.?
Click to expand...
Click to collapse
What do you mean? ahahah

Anonymousxx said:
Hi Alf! Is always me ahaha.
Anyway I wanted to ask you if it makes sense to switch from LineageOS 18.1 to this one here, or they are the same (especially in terms of stability). I also would like to know if there is a way to avoid loosing the unlocked bootloader when I have to switch to stock firmware. Thank you
Click to expand...
Click to collapse
Can anyone more polite answer me please? Thank you

-Alf- said:
New Android 11 GSI ROM based on Phhusson's AOSP . Really good, stable enough to be used as your daily driver. No major bugs. Preinstalled SuperUser, Android Auto, smart "Keep Notes" etc...
Bored during quarantine? Try this great ROM!
Note: Tested on 9.1.0.132.
Credits: @berkay-gsi
Requirements: basically full stock EMUI 9.1, with stock recovery.
IMPORTANT! Before booting up the ROM, you will need to perform a factory reset in stock recovery!
1. Download system-alpha ROM
ROM
2. Extract the .img file from the compressed file.
3. Flash extracted system.img from fastboot , use command
fastboot flash system (file_name).img
4. Run command 'fastboot reboot', unplug your phone, when on the screen appears yellow warning, press and hold for 3 sec Volume Up . In eRecovery select 'Wipe data/factory reset'. Reboot .
NFC:
- Download NFC Patch
- Install
TWRP
over eRecovery (it makes things easier) - follow this
guide
- In TWRP unmount all except SD Card , Vendor and System (unmount and mount again)
- Flash nfc_universal_patch.zip
- From TWRP menu reboot into recovery and perform factory reset .
Note: you can flash NFC patch before booting up the ROM
How?
Tip: use "Simple Gallery"
download
Enjoy !
View attachment 5214123View attachment 5214125View attachment 5214127View attachment 5214129View attachment 5214131View attachment 5214133View attachment 5214137View attachment 5214139
Click to expand...
Click to collapse
any new updates and changes for this rom out yet?

lucsol said:
any new updates and changes for this rom out yet?
Click to expand...
Click to collapse
I don't know bro, but try looking here:
berkai-gsi

J415GN/DS TWRP HELP

yo, can someone help or answer me. I can't seem to find any official/unofficial version of twrp for sm-j415gn/ds. Does anyone have any link?

lamawkalabaw said:
yo, can someone help or answer me. I can't seem to find any official/unofficial version of twrp for sm-j415gn/ds. Does anyone have any link?
Click to expand...
Click to collapse
https://forum.xda-developers.com/f/samsung-galaxy-j4-roms-kernels-recoveries-ot.8287/
There is one here.

ashyx said:
Unofficial release -TWRP recovery for the Galaxy J4 plus 2018 - SM-J415 MSM8917
{
"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"
}
TWRP 3.3.1-0 Released
May 22, 2019
TWRP 3.3.1-0 is out now for most currently supported devices.
What's new in 3.3.1-0:
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
Update - 17/8/2019
TWRP 3.3.1-1 OO/PP build released
Current status - Beta
Treble supported
Bugs: brightness slider
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
*****INSTALL INSTRUCTIONS:*****
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
(Plug in the USB cable and then hold POWER + VOL DOWN + VOL UP)
2. Load the respective file below into the AP slot, uncheck Auto-reboot(not required for twrp_3.3.1-1) and hit start.
twrp_3.2.3-1_sm-j415f_30319
twrp_3.3.1-1_j415x_17819
3. After flashing and ODIN reports PASS immediately force reboot to recovery. (Not required for twrp_3.3.1-1 as it should auto reboot to recovery). You should now see TWRP recovery.
Do NOT let the device boot to the OS.
4. Flash the V3 RMM bypass zip
https://forum.xda-developers.com/showpost.php?p=79745844&postcount=627
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT AND BECOMING RMM LOCKED FOR 7 DAYS.
I ALSO SUGGEST BACKING UP ANYTHING YOU NEED ON INTERNAL STORAGE. AT SOME POINT YOU MAY EXPERIENCE A 'VERIFICATION FAILED MESSAGE' .
THIS IS NORMAL, BUT WILL REQUIRE THE DATA PARTITION TO BE FORMATTED IN TWRP.
5. Reboot to TWRP (Do not boot to the OS yet)
***** ROOT INSTRUCTIONS:*****
OREO ONLY
1. Flash the Forced encryption disabler patch. This is only required if you wish to have full functionality in TWRP.
Flashing this will disable Samsung's forced encryption. Disabling encryption will allow TWRP to mount the data partition.
After flashing the patch it is necessary to *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
J4+J6+_oreo_forced_encryption_disabler
2. To root I suggest installing the latest Magisk beta as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
(NOTE: The DEFEX patched Oreo kernel below may be needed for full root support if certain apps do not work with root):
https://androidfilehost.com/?fid=1395089523397921797
3. Enjoy your rooted device.
PIE ONLY
1. Due to some new securities in Samsung's latest Pie kernels, root will not work with the stock kernel. The patched kernel below is required to gain root on Pie.
Features:
Dmverity, proca, five and defex disabled.
OTG and NTFS file system support.
Selinux permissive switchable.
This kernel may require the U4 bootloader.
(NOTE: flashing a custom kernel on PIe breaks the lockscreen. Ensure NO lockscreen is enabled before installing the kernel.)
J415FXXU4BSF7_patched_boot_318919
2. To root I suggest installing the latest Magisk beta as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/app...mless-t3473445
3. If you wish to have access to internal storage /DATA in TWRP then encryption will need to be disabled. See step 1 of the Oreo root instructions then instead of installing the J4+J6+_oreo_forced_encryption_disabler install the zip below with TWRP:
Disable_Dm-Verity_ForceEncrypt_Quota_08.02.2019
3. Reboot.
The device will take a good 10 mins to boot first time.
Enjoy your rooted device.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my tester @kapmino269 [MENTION=6037748]Zackptg5 for the DM-VERITY & FORCEENCRYPT DISABLER @teamwin, @corsicanu for RMM V3 bypass zip.
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Here.

Kenora_I said:
Here.
Click to expand...
Click to collapse
yo thanks, but is it compatible for my model? i really am confused because i don't know if j415gn/ds and j415gn are the same.

lamawkalabaw said:
yo thanks, but is it compatible for my model? i really am confused because i don't know if j415gn/ds and j415gn are the same.
Click to expand...
Click to collapse
Lol there isnt a j415gn
Just the j415gn/ds
Anyway they are the same phone nonetheless but ive given the one specific to your phone
The devs dont put /ds for convenience probably.

Kenora_I said:
Lol there isnt a j415gn
Just the j415gn/ds
Anyway they are the same phone nonetheless but ive given the one specific to your phone
The devs dont put /ds for convenience probabl
Click to expand...
Click to collapse
Kenora_I said:
Lol there isnt a j415gn
Just the j415gn/ds
Anyway they are the same phone nonetheless but ive given the one specific to your phone
The devs dont put /ds for convenience probably.
Click to expand...
Click to collapse
gee, i owe you a lot man. I just wanted to get the best out of this phone since I'm just a student and broke. I am very nervous that i might hardbrick this since it's my only phone. Anyways, thanks again dude.

lamawkalabaw said:
gee, i owe you a lot man. I just wanted to get the best out of this phone since I'm just a student and broke. I am very nervous that i might hardbrick this since it's my only phone. Anyways, thanks again dude.
Click to expand...
Click to collapse
LOL IM NOT A DUDE
But yeah no issue lol
i kinda do this for fun anyway
i just like helping around
Yeah i hate dem hard bricks. Ive had phones become paperweights, but i seem to unbrick them in the end

Kenora_I said:
LOL IM NOT A DUDE
But yeah no issue lol
i kinda do this for fun anyway
i just like helping around
Yeah i hate dem hard bricks. Ive had phones become paperweights, but i seem to unbrick them in the end
Click to expand...
Click to collapse
lmao I'm sorry and thank you
i might ask for your help again if i had any problems.

lamawkalabaw said:
lmao I'm sorry and thank you
i might ask for your help again if i had any problems.
Click to expand...
Click to collapse
Sure! Ill be here.

Development [RECOVERY][UNOFFICIAL] TWRP 3.6.2 for Samsung Galaxy Z Flip 3 [31/07/2022]

{
"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"
}
This is an UNOFFICIAL TWRP recovery for Samsung Galaxy Z Flip 3
Builded from scratch​Whats Working :​- Decryption (not fully working)
- MTP
- ADB
- OTG
- Backup and Restore (Thanks beanbean50)
- Flash System Image and Vendor Image also
- Rear Touchscreen is Disabled​Known Bugs :​- Others i don't know (this is a flip phone)​Instructions :​- Unlock your bootloader
- Download the TWRP recovery and vbmeta_disabled
- Reboot to download mode
- Put the TWRP Recovery Tar for your device on Odin in the AP slot and vbmeta_disabled in USERDATA slot and click start
- Reboot to recovery via recovery key combo (Vol up + power + USB connected)
- 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
- Reboot to system
- Enjoy​Downloads :​TWRP Recovery
vbmeta_disabled​Supported Devices :​* SM-F711B
​Changelog :​- 1.0 : initial build
- 1.0.1 : disable rear touchscreen and use auto builtin kernel and firmware modules
Device Tree : https://github.com/shadowofleaf96/android_device_samsung_b2q
Credits :
- @afaneh92
- @ianmacd
- @twistedumbrella
if you like my work , consider Donating
Thanks
Paypal.me Donation Link​

Love to see someone upload TWRP for our Z Flip 3. Thanks...

Clusco said:
Love to see someone upload TWRP for our Z Flip 3. Thanks...
Click to expand...
Click to collapse
you welcome , try it and report back because i did not have the time to test all features

Foldable TWRP, isn't that cool?

Zillion said:
Foldable TWRP, isn't that cool?
Click to expand...
Click to collapse
yeah ,dont you think ??!!

Do you have a working GSI image? Others have infinite booting.

All working good here, even backup & restore tested and working
Well done and congratulations, great job!
I've sent you a couple of cups of coffee to say thank you

Maroshall said:
Do you have a working GSI image? Others have infinite booting.
Click to expand...
Click to collapse
Yes just dont use android 12.1 , they cause bootloop , you can use this pixel experience gsi https://github.com/ponces/treble_build_pe/releases/tag/v402.1
But i think they are far from stable for our flip (refresh rate flicker, outer screen logic is missing , no screen lock when locking the phone,etc)

beanbean50 said:
All working good here, even backup & restore tested and working
Well done and congratulations, great job!
I've sent you a couple of cups of coffee to say thank you
Click to expand...
Click to collapse
Thank you very much for your support
Im glad it did work
Now i just need to fix the kernel to open the door for further developement (custom kernels, custom roms....)

YESSS!! You must have heard my silent prayers
TWRP for the Flip 3 is great - this lets me hope to see a custom ROM for this phone!
Can I donate to you a bit as a thanks for the work?
Edit: forget the question. I found the link in your profile - a donation ist on its way!

FFW said:
YESSS!! You must have heard my silent prayers
TWRP for the Flip 3 is great - this lets me hope to see a custom ROM for this phone!
Can I donate to you a bit as a thanks for the work?
Edit: forget the question. I found the link in your profile - a donation ist on its way!
Click to expand...
Click to collapse
thank you very much
yes for sure there will be custom roms and custom kernels in the future

Shadow Of Leaf said:
thank you very much
yes for sure there will be custom roms and custom kernels in the future
Click to expand...
Click to collapse
If custom ROMs exist for the Z Fold 3, that'll be perfect for Android 12L ROMs lol

BMHater12 said:
If custom ROMs exist for the Z Fold 3, that'll be perfect for Android 12L ROMs lol
Click to expand...
Click to collapse
you mean Z Flip 3 ??
yes i think so

Format data, wooaaw, that makes me sigh everytime

naren12 said:
Format data, wooaaw, that makes me sigh everytime
Click to expand...
Click to collapse
hahaha , but it need to be done to use your data partition again

Shadow Of Leaf said:
hahaha , but it need to be done to use your data partition again
Click to expand...
Click to collapse
Offtopic but for our device. Do you have any idea on how to properly edit vendor/build.prop . I tried editing with es,fx,mixplorer but failed, i tried to remount as rw and tried, still no win. The buildprop gets empty whenever i try to make any changes in it. I even edited in internal and then pasted in vendor still no use. Any help would be appreciated or direct me to any place where i could ask this. TIA

naren12 said:
Offtopic but for our device. Do you have any idea on how to properly edit vendor/build.prop . I tried editing with es,fx,mixplorer but failed, i tried to remount as rw and tried, still no win. The buildprop gets empty whenever i try to make any changes in it. I even edited in internal and then pasted in vendor still no use. Any help would be appreciated or direct me to any place where i could ask this. TIA
Click to expand...
Click to collapse
There's no empty space on /vendor to do that.
Try removing recovery-from-boot.p to gain some space.

naren12 said:
Offtopic but for our device. Do you have any idea on how to properly edit vendor/build.prop . I tried editing with es,fx,mixplorer but failed, i tried to remount as rw and tried, still no win. The buildprop gets empty whenever i try to make any changes in it. I even edited in internal and then pasted in vendor still no use. Any help would be appreciated or direct me to any place where i could ask this. TIA
Click to expand...
Click to collapse
you can use a magisk module to change in vendor or system cause they arent fully decrypted

great thanks for porting this to our devices

yo
Leho said:
great thanks for porting this to our devices
Click to expand...
Click to collapse
you are welcome , that is my device now too