Related
{
"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.
{
"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"
}
Orange Fox custom recovery
What is Orange Fox?
This custom recovery is based off TWRP, but has added features and different styling.
For more information visit the official wiki - HERE
Features
* Updated with latest TWRP commits
* Built-in support for installing Magisk
* White Flashlight
* Password pretext your recovery
* Better language support
* Optimized versions of community scripts
* Fox theme engine:
- choice of theme (black, dark, etc)
- choice of color scheme
- choice of splash screen
* Alternative lockscreen
Downloads
MEGA
Kernel - GitHub
OFRP Source - [URL="https://gitlab.com/OrangeFox]GitLab[/URL].
Thanks to the main OrangeFox contributors @MrYacha and @DarthJabba9
Also TeamWin for TWRP
--->
Installation
From existing TWRP or OrangeFox recovery
1. Download the OrangeFox zip to your device
2. Reboot to TWRP-based Recovery
3. Install the OrangeFox zip
4. Reboot recovery
From stock unrooted
1. Unlock bootloader
2. Download OrangeFox Odin installer .tar to PC
3. Boot device into download mode, and connect to PC
4. Uncheck auto reboot in Odin
5. Flash the OrangeFox .tar file to the AP tab
6. When flashed, and you are ready, force reboot into recovery.
7. Download Encryption disabler, and transfer to device.
8. Flash Encryption disabler, FORMAT data, reboot recovery.
9. Download Magisk and transfer to device. Flash.
10. Boot up, first boot may hang. After 3min waiting, hard reboot and you should boot straight into initial setup.
** Don't reboot device before going through initial setup and connecting to the internet. This is needed for KG status to read normal. If you don't do this, you may find yourself in a prenormal state.
** If installing OrangeFox through Odin, you will be missing the Fox add-ons, which aren't essential. But if so desired, flashing the OrangeFox zip from existing custom recovery will install the necessary files for Fox add-ons.
--->
Screenshots
Gallery
Mentalmuso said:
Screenshots
Gallery
Click to expand...
Click to collapse
Thanks for making an N9700 version.
Works great!!
Any chance you can get USB OTG to work?
Android detects my Sandisk Extreme, but TWRP does not.
Duh! Forgot to mount USB drive...now it works!
difference between this and mental?
best to start making custom roms instead
edit: i see this is by mental lol
weird
pretty cool, thanks. Theres a couple bugs: haptics dont work and the keyboard covers the input line in the terminal. Also, I don't know if this is intended for this recovery, but system apps are not shown in the app manager even though I have mounted system as rw. That would be really cool if they were.
Seems like this recovery has the potential to be a great tool for system-on-root modding. I'll keep for a little while, but not being able to use the terminal will end up being a deal breaker if not fixed. Why is it hidden away in menus too? Anyhow, know you didnt design it, thanks for the work in porting this!
AllanRSS said:
pretty cool, thanks. Theres a couple bugs: haptics dont work and the keyboard covers the input line in the terminal. Also, I don't know if this is intended for this recovery, but system apps are not shown in the app manager even though I have mounted system as rw. That would be really cool if they were.
Seems like this recovery has the potential to be a great tool for system-on-root modding. I'll keep for a little while, but not being able to use the terminal will end up being a deal breaker if not fixed. Why is it hidden away in menus too? Anyhow, know you didnt design it, thanks for the work in porting this!
Click to expand...
Click to collapse
Thanks, I'll take a look at those items. I haven't done much else since release, but I'll see if I can move the terminal to the front menus.
Is it really that easy to root a SnapDragon?
Eddie_Brock said:
Is it really that easy to root a SnapDragon?
Click to expand...
Click to collapse
Yes!
Mentalmuso said:
Thanks, I'll take a look at those items. I haven't done much else since release, but I'll see if I can move the terminal to the front menus.
Click to expand...
Click to collapse
That would be awesome if you could figure those things out. No pressure of course, I appreciate what you've done so far.
I do think if fixed up a bit this has the potential to be a great tool for our phones. System on root devices need a robust solution for modifying system files, and this recovery seems like a great start to achieving that. Adding system app management would be the obvious first choice for a feature many people would appreciate
flashed it in twrp and twrp keeps coming up. something is wrong
cylent said:
flashed it in twrp and twrp keeps coming up. something is wrong
Click to expand...
Click to collapse
Flashed what? Link me to the file you flashed
Mentalmuso said:
Flashed what? Link me to the file you flashed
Click to expand...
Click to collapse
https://mega.nz/#F!ng8WiCqD!AGERu9vO97A0YBnnmaXOaA?PxtiDASY
the zip
cylent said:
https://mega.nz/#F!ng8WiCqD!AGERu9vO97A0YBnnmaXOaA?PxtiDASY
the zip
Click to expand...
Click to collapse
Ok, assuming you have the n9750 device, I don't have much else to say. I just tested installing TWRP, then using the orangefox zip to flash OF. and it works fine for me.
I have twrp working and even have nemesis kernel installed.
When I flash orangefox zip in twrp items successful but when I boot into recovery it's twrp once again.
Should I flash it via Odin?
Also, I am on infinity rom...n975fds
cylent said:
I have twrp working and even have nemesis kernel installed.
When I flash orangefox zip in twrp items successful but when I boot into recovery it's twrp once again.
Should I flash it via Odin?
Also, I am on infinity rom...n975fds
Click to expand...
Click to collapse
This is for snapdragon phones only if your model is n975fds then you have exynos model which means this recovery won't work on your phone
minidude2012 said:
This is for snapdragon phones only if your model is n975fds then you have exynos model which means this recovery won't work on your phone
Click to expand...
Click to collapse
Now you tell me
Any chance of exynos version?
Post 14 above he said it works.
https://forum.xda-developers.com/showpost.php?p=81932681&postcount=14
cylent said:
Now you tell me
Any chance of exynos version?
Post 14 above he said it works.
https://forum.xda-developers.com/showpost.php?p=81932681&postcount=14
Click to expand...
Click to collapse
You might consider a different hobby...RTFM
Sent from my SM-N975F using XDA Labs
CAREFUL
I tried to boot into this recovery again yesterday and there was a verified boot problem. I went into a bootloop in download mode with the following error. I had to reflash twrp from odin to get the device back. I'm going to wait till this has been developed a little more to use it on my main device.
"partition vbmeta
Reason vbmeta: Error verifying vbmeta image:
0_0_INDIVLDVMT_EDRHS_IMTHSGAUEMSAC"
AllanRSS said:
CAREFUL
I tried to boot into this recovery again yesterday and there was a verified boot problem. I went into a bootloop in download mode with the following error. I had to reflash twrp from odin to get the device back. I'm going to wait till this has been developed a little more to use it on my main device.
"partition vbmeta
Reason vbmeta: Error verifying vbmeta image:
0_0_INDIVLDVMT_EDRHS_IMTHSGAUEMSAC"
Click to expand...
Click to collapse
This recovery is based off TWRP... vbmeta issues purely stem from root or more specifically magisk.
{
"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
{
"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 G991B/N.
Download & Guide:
1. Unlock your bootloader.
2. Download S21: o1s.
3. Reboot to download mode
4. Put the TWRP TAR for your device with Odin in the AP slot, vbmeta_disabled_R.tar in USERDATA slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.- Type: multidisabler again. will see - Finished. when done.- Go back to Wipe > Format Data > type yes.- Reboot to recovery.7. Flash magisk apk in twrp.
8. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree
Changelog:
29.11.2021 - Update to TWRP 3.6.0
- Updated to latest kernel source
- Update multidisabler
- fstab clean up
- Fix haptic feedback
21.08.2021 - Add Symlinked dynamic partitions to fstab
- Fix dtbs issue from previous build
09.08.2021 - Updated to latest kernel source
- No vbmeta disable require
- fstab clean up
03.03.2021 - Initial Release.
Wait if this is for the S21 Ultra only what is this doing in the normal s21 forum?
Youre very fast gg
DeblaGaming said:
Wait if this is for the S21 Ultra only what is this doing in the normal s21 forum?
Youre very fast gg
Click to expand...
Click to collapse
My bad I missed that but you can know from G991B its regular not Ultra.
@afaneh92 The recovery supports flashing Magisk APK out-of-the-box?
So, no need to rename the .apk to .zip anymore?
I'm kinda casual, with haptic feedback not working do you mean the vibration motor in the phone stops working completely, or? I don't know what encryption not working means either.
I saw the same issues for the S20 FE.
Looking at both forums closely currently as I'm deciding which phone to buy dependent on which phone will have a better root experience.
Will this have to be done everytime there is a firmware update?? Or like other devices we can keep twrp and magisk when updating..
I currently have S20 which I dont have twrp on but can update new firmware and just reboot to odin after flashing new firmware and just flash patched boot.img and all is good. Will the S21 be the same
DJBhardwaj said:
@afaneh92 The recovery supports flashing Magisk APK out-of-the-box?
So, no need to rename the .apk to .zip anymore?
Click to expand...
Click to collapse
You can flash apk
orkavaneger said:
I'm kinda casual, with haptic feedback not working do you mean the vibration motor in the phone stops working completely, or? I don't know what encryption not working means either.
I saw the same issues for the S20 FE.
Looking at both forums closely currently as I'm deciding which phone to buy dependent on which phone will have a better root experience.
Click to expand...
Click to collapse
Vibration not working in twrp only, read more.
bigpotato107 said:
Will this have to be done everytime there is a firmware update?? Or like other devices we can keep twrp and magisk when updating..
I currently have S20 which I dont have twrp on but can update new firmware and just reboot to odin after flashing new firmware and just flash patched boot.img and all is good. Will the S21 be the same
Click to expand...
Click to collapse
Yes need to redo every step.
i got my s21 rooted with ap, and magisk install thing. now i want to get twrp, is it just followed the guide or should i factory ap first?
Emrah132 said:
i got my s21 rooted with ap, and magisk install thing. now i want to get twrp, is it just followed the guide or should i factory ap first?
Click to expand...
Click to collapse
Follow instructions.
i didnt need vibration its great job thank you afaneh92
can i flash twrp without lost magisk root?
What about encryption issue.. is there any clue on next release. I don't think I found a problem except for the two things that were mentioned above bugs
Hi,
I was able to install magisk. In the end, I want to install exposed framework. In the TWRP mode, whenever I try to install, I get an error.
-Mounting /system and /vendor read-write mount: can't find /system in /proc/mounts
!Failed: /system could not be mounted
In the end, it says "Updating partition details" .. done. Can you please help me in resolving this error.
Thanks for your efforts, dev! Everything working as expected.
Hello, is there any way to re-enable encryption after TWRP installation? No matter, FBE or FDE. It says "not fully working" and I see only not working at all, maybe I am doing something wrong?
A note on firmware updates:
It is possible to follow all the instructions from the original post but SKIP the step of wiping your data from within TWRP when updating your firmware. You need to run the multidisabler though. This works if you had already installed this TWRP version with encryption disabled, including a data wipe, but now want to update your firmware. So wiping data is only needed for the first time.
In fact, if you had installed this TWRP version and do a firmware update via odin but do not flash this TWRP version with vbbeta disabled, your phone simply won't start anymore. It will ask you to factory reset.
So once you go TWRP, you have to reinstall it for future updates.
@afaneh92 do you want to add this as a hint in your OP?
Thank you for your great work and the fast twrp publishing! I was able to install and boot a GSI.
Now I would like to flash microg/gapps to system, but the system partition does not have any free space left. In the twrp wipe menu I cannot find the system partition to increase size. Would it be possibe to add this feature or are other steps mandatory to increase system partition in size?
Again, thanks a lot for your efforts!
Hi, I have my S21 Rooted with Magisk Patched Stock Image.
It is possible to flash TWRP but without doing a Data Wipe?
It isn't clear if the Data Wipe is needed for Rooting after unlocking the bootloader (I already did that), or it is actually needed for getting TWRP to fully work.
Thanks.
WiS3 said:
Hi, I have my S21 Rooted with Magisk Patched Stock Image.
It is possible to flash TWRP but without doing a Data Wipe?
It isn't clear if the Data Wipe is needed for Rooting after unlocking the bootloader (I already did that), or it is actually needed for getting TWRP to fully work.
Thanks.
Click to expand...
Click to collapse
In your place I would just try. Take a backup and try the installation, skipping ONLY the data wipe. If this fails, either use your backup or include the wipe.
Though, I HIGHLY assume you need to wipe for the first install of TWRP to remove the encryption initially. In future TWRP updates, you can skip wiping.
Team Win Recovery Project
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.
{
"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:
I am not responsible about any damage of any kind that this custom binary may cause.
Please pay attention to this post & related ones before proceeding and follow the guide correctly. I will not offer support for any issues that have been already stated.
Your Knox Warranty Bit will be blown once you flash this or others custom binaries, preventing you to use Knox features. It can't be resetted in any way, so think twice before flashing this.
Bugs can be reported here in XDA or via the community's Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs.
How do I flash and set it up correctly?
Please notice that the following guide is meant for full stock devices, if you've already rooted your device you can skip it and flash directly the recovery without any extra steps.
Before starting, make sure to backup all your data and important files stored in your phone, since this procedure will format your data partition.
Download Odin3, Samsung's Android USB Drivers, the latest TWRP's tar and a disabled vbmeta image.
Make sure your phone's bootloader is unlocked, follow the guide below in case it isn't:
How to unlock bootloader ?
Open the Settings app, enter Developer Options and enable OEM unlocking (If you don't see Developer Options, enter into About phone>Software info and tap "Build number" 10 times to show it).
Enter Download Mode: to do so power off your device, connect it to a computer via an USB cable and hold both volume up and volume down buttons.
Long press volume up to unlock the bootloader. This will wipe your data and your phone will automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again later. Make sure to connect the device to Internet during the setup.
Enter Developer Options and check that the OEM unlocking option exists and is grayed out. This means our bootloader is unlocked and your phone has no KnoxGuard lock set.
How to install ?
Connect your phone to your PC and boot in Download Mode (power off your device and hold both volume up and volume down buttons).
Open Odin3, select the TWRP tar by clicking the "AP" button and the patched vbmeta tar by clicking "USERDATA", then press the Start button.
Reboot your phone in recovery mode: while it still plugged in your PC, hold both the power and volume up buttons.
Once TWRP has booted you need to format again your data partition in order to be able to boot in system again. To do so touch Wipe>Format Data and follow the instructions in screen.
Bugs:
-
Thanks:
TWRP team
- Samsung opensource kernel
- @BlackMesa123 for device tree and kernel Samsung Galaxy A52s.
Sources:
- Kernel tree : https://github.com/samsung-778/android_kernel_samsung_sm7325/tree/twrp-12.1
Changelog: 11/05/2023
- Support Android 13 decrypt with no password
CHECK LINK LAST ON POST
Hello
nguyenhung9x2018
could you let me know if i can use these files for galaxy m625f as i am not finding anything on the subject for this model, could you help me with this? Thank you very much in advance
rickgermano said:
Hello
nguyenhung9x2018
could you let me know if i can use these files for galaxy m625f as i am not finding anything on the subject for this model, could you help me with this? Thank you very much in advance
Click to expand...
Click to collapse
Samsung Open Source
opensource.samsung.com
Great to see the development got started for the Galaxy A73! Eagerly looking for more under specified forum!
nguyenhung9x2018 said:
Samsung Open Source
opensource.samsung.com
Click to expand...
Click to collapse
Hello! Thanks for the link , but this zip I can do the installation by odin ?
rickgermano said:
Hello! Thanks for the link , but this zip I can do the installation by odin ?
Click to expand...
Click to collapse
it is tar, you can install it with odin
How do I disable vb meta?
Update link download vbmeta disable
nguyenhung9x2018 said:
Update link download vbmeta disable
Click to expand...
Click to collapse
Any updates on decryption?
Are we going to have any Custom ROMs for this phone?
n0tluke192 said:
Are we going to have any Custom ROMs for this phone?
Click to expand...
Click to collapse
i think no, cuz it uses f2fs
xS1lent said:
i think no, cuz it uses f2fs
Click to expand...
Click to collapse
I build rom custom for a73xq , it booted, but RIL broken
nguyenhung9x2018 said:
I build rom custom for a73xq , it booted, but RIL broken
Click to expand...
Click to collapse
Excuse me, but how do YOU create a custom ROM? If the DATE section is not decrypted???Tell me how is this possible???
kissa67zwi said:
Excuse me, but how do YOU create a custom ROM? If the DATE section is not decrypted???Tell me how is this possible???
Click to expand...
Click to collapse
its because of f2fs and encryption im working with a very lovely dev hes helping me decrypt theres an issue with this recovery might have to rebuild and see but for now if you want to use twrp on oneui5 you can use android 12 bootloader (flash via) i dont recommend this as stuff like vaultkeep will be broken
Cockat0o said:
its because of f2fs and encryption im working with a very lovely dev hes helping me decrypt theres an issue with this recovery might have to rebuild and see but for now if you want to use twrp on oneui5 you can use android 12 bootloader (flash via) i dont recommend this as stuff like vaultkeep will be broken
Click to expand...
Click to collapse
thank you for your efforts, and with respect to YOU and YOUR friend- I will look forward to YOUR efforts and updates.....I'm just using LIGICK now and it works..... I have UI5, but I'll wait for DATA decryption
Any custom kernel available?
So can mount r/w
rajnimal nimal said:
Доступно ли какое-либо пользовательское ядро?
Так можно смонтировать r/ w
Click to expand...
Click to collapse
вроде бы ещё пока нет
rajnimal nimal said:
Any custom kernel available?
So can mount r/w
Click to expand...
Click to collapse
There is no custom core yet... And RO2RW hasn't been made for SAMSUNG yet...I am also waiting for the issue to be resolved
Just a heads up, samsung open sourced their initial android 13 build right after they send out 2023 january security update. So they are gonna follow a build late it seems.
https://opensource.samsung.com/uploadSearch?searchValue=SM-A736
I hope to contribute to this phone's development but in it's current state I do not have enough knowledge to be useful. Once it's matured enough and I got enough taste of oneui you can be sure to see me again mate, good luck with the work ahead.