Develop Bugs

Unofficial TWRP 2.8.7.1

What is better than the standard CM Recovery:
You can flash another firmware (not the CM)
Normal backup data
You can easily flash the Root
{
"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"
}
Unlock the bootloader as on CM Wiki instructions
Puth the phone in bootloader mode
In the folder with fastboot put crackling-t0x1.img
Enter the following command:
Code:
fastboot -i 0x2970 erase recovery
then Enter
Code:
fastboot -i 0x2970 flash recovery crackling-t0x1.img
Disconnect the device from the USB and remove the battery. Then replace the battery and restart the device in recovery mode to verify the installation. To do this, hold down the "Volume Down" and "Power".
You can download crackling-t0x1.img from here
http://www91.zippyshare.com/v/60lfsDiR/file.html
Credits to 4PDA Members and especially to FindYanot for developing and allowing posting here
IT is NOT my Work

I've been using this for a while, working very good!
Great to make backups and test ROMs.

There is a problem - this recovery can not mount f2fs partitions

RaidonChrome said:
There is a problem - this recovery can not mount f2fs partitions
Click to expand...
Click to collapse
for my information : which system firmware can mount f2fs partitions?

Dior DNA said:
for my information : which system firmware can mount f2fs partitions?
Click to expand...
Click to collapse
Latest Cyanogen Mod 13 has Linux 3.10, so it should be able to mount f2fs just fine

RaidonChrome said:
Latest Cyanogen Mod 13 has Linux 3.10, so it should be able to mount f2fs just fine
Click to expand...
Click to collapse
thanks, then perhaps latest CM recovery will mount f2fs just fine as well.

Dior DNA said:
thanks, then perhaps latest CM recovery will mount f2fs just fine as well.
Click to expand...
Click to collapse
It does not, in fact it is broken even with ext4 currently

PLEASE HELP, something when wrong
RaidonChrome said:
It does not, in fact it is broken even with ext4 currently
Click to expand...
Click to collapse
Is this the reason why i can't install gapp on my wileyfoxswift and an error appear("e: unable to find partition size for '/recovery") every time i use the wipe.
i upgraded from 12.1 to
13.0-20160127-NIGHTLY-crackling and use the same for recovery but did not work so i installed TWRP and this error occurs -see pics
PLEASE HELP

AromaGapp not working in TWRP
TWRP not working in Aroma Gapp need fix (Aroma is best for me since i can customize install & will not replace CM stock files/app)
In the previous post, i was able to install twrp but i found out on many trial and error that open gapp aroma/full doesn't work both on cm12.1 and cm13.0 using TWRP. Also cm13.0 recovery will not work with open gapp aroma/full.
What works: (haven't tried all version)
On TWRP - i was able to use arm64-pico-6.0 on cm13.0 20160130
On CM Recovery - arm64-aroma-5.1 on cm12.1 20160107
This is based on my experience with the HELP of the awesome people in the forum. I just want to let you know and maybe it will be useful to other noobs like me

noob2016 said:
TWRP not working in Aroma Gapp need fix (Aroma is best for me since i can customize install & will not replace CM stock files/app)
In the previous post, i was able to install twrp but i found out on many trial and error that open gapp aroma/full doesn't work both on cm12.1 and cm13.0 using TWRP. Also cm13.0 recovery will not work with open gapp aroma/full.
What works: (haven't tried all version)
On TWRP - i was able to use arm64-pico-6.0 on cm13.0 20160130
On CM Recovery - arm64-aroma-5.1 on cm12.1 20160107
This is based on my experience with the HELP of the awesome people in the forum. I just want to let you know and maybe it will be useful to other noobs like me
Click to expand...
Click to collapse
Aroma compatibility with TWRP is listed on the Open G-Apps website.
Unfortunately this is the only TWRP we have available to us.

Tamarinde said:
Aroma compatibility with TWRP is listed on the Open G-Apps website.
Unfortunately this is the only TWRP we have available to us.
Click to expand...
Click to collapse
No it is not there is this one https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRPand yes it works with aroma

Thanks
robin0800 said:
No it is not there is this one https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRPand yes it works with aroma
Click to expand...
Click to collapse
That is great! i hope i can try i try it but sadly i send it back since the phone was just here for the upgrade. Anyway thanks for the reply here and on my other post.
Much appreciated

robin0800 said:
No it is not there is this one https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRPand yes it works with aroma
Click to expand...
Click to collapse
Confirmed!!! It works... i used TWRP 3.0. Works on both aroma and pico. Thanks so much!!!!

There is a zip file and recovery. IMG file, any reason why?

image45 said:
There is a zip file and recovery. IMG file, any reason why?
Click to expand...
Click to collapse
The .img file can be flashed by fastboot.
The zip file by any non stock recovery
and yes I do know the image file is contained in the zip but some people may not

robin0800 said:
The .img file can be flashed by fastboot.
The zip file by any non stock recovery
and yes I do know the image file is contained in the zip but some people may not
Click to expand...
Click to collapse
Yes i downloaded the zip file, extracted the recovery.img then flashed by fastboot. I am used to using fastboot commands
So the zip file would function as an update file via a non stock recovery, however once installed would replace the non stock recovery with twrp version!

[Un-Official][RECOVERY][NITROGEN] TWRP 3.2.2-0 for Mi Max 3

Team Win Recovery Project
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.
Read more about TWRP here: https://twrp.me/about/
Bugs
1:-encryption don't work
DOWNLOAD:
TWRP
*note always download the latest twrp in the folder
Flashing Guide
1:- Unlocked Boot-loader is required.
2:- Download TWRP recovery .img file compatible with your device and save to a separate folder on your PC.
3:- Setup ADB and Fastboot on your PC.
4:- Enable USB debugging on your device.
5:- Open the folder where you saved TWRP Recovery .img file in Step 2 above.
6:- Now open a command window inside that folder. To do that, “Shift + Right click” on any empty white space inside the folder and then select “Open command window here” from the context menu.
7:-Connect your device to the PC. And type the following into the command adb reboot bootloader
8:-Once your device boots into bootloader mode, issue the following command into command window to flash the TWRP recovery .img file fastboot flash recovery recovery.img
9:-Once TWRP is successfully flashed on your device, issue the following command to reboot fastboot reboot
Note:- THIS IS ONLY A TESTING RELEASE SO MANY THING CAN BE BROKEN.​THIS IS MADE DIRECTLY FROM SOURCE NOT PORTED​
XDA:DevDB Information
TWRP-NITROGEN, Tool/Utility for the Xiaomi Mi Max 3
Contributors
ROMFACTORY, yshalsager
Source Code: https://github.com/minimal-manifest-twrp
Version Information
Status: Testing
Created 2018-07-29
Last Updated 2018-08-05

Update 31-07-2017
Added Crypts
So Encryption Should Works
Updated 02-08-2018

another reserved

Wow..u already buy mi max 3? How about ur max1?

raymondsanusi said:
Wow..u already buy mi max 3? How about ur max1?
Click to expand...
Click to collapse
i have all 3

Thanks, will test it now and revert
-works fine with magisk 16.7
-seems to be finicky with encryption

@ROMFACTORY i'm really happy that you come for the development of mi max 3, very satisfied with your work on hydrogen ? cordially

Thank for share .Waiting 360h

wow nice so fast ,still waiting for mi max to be available at my country.

Thanks for the work. Gonna try this now.

< DELETED >

ugene1980 said:
Thanks, will test it now and revert
-works fine with magisk 16.7
-seems to be finicky with encryption
Click to expand...
Click to collapse
really ? encryption is not yet enabled i have disabled it
can u plz post some ss

ROMFACTORY said:
really ? encryption is not yet enabled i have disabled it
can u plz post some ss
Click to expand...
Click to collapse
Sure, what SS do you need?
Managed to root both miui 9.6.7 stable and 8.7.26 dev (miui10) by flashing Magisk 16.7 via TWRP
For encryption, i just clicked cancel when it asks for password/key
Also, flashing xiaomi.eu rom leads to bootloop, not sure if due to xiaomi.eu or TWRP

ugene1980,
Did you try Magisk 16 Stable with it?
Does it works ?

kelvintisw said:
ugene1980,
Did you try Magisk 16 Stable with it?
Does it works ?
Click to expand...
Click to collapse
Didnt try, doubt it would, 16 doesnt support treble enabled xiaomi roms

I see. Okay. Will use the Beta later when my unlocked is approved.
Thank.

Now I waiting for 15 days to unlock bootloader first. After that i will test your TWRP.
Just 10 days left.

ugene1980 said:
Sure, what SS do you need?
Managed to root both miui 9.6.7 stable and 8.7.26 dev (miui10) by flashing Magisk 16.7 via TWRP
For encryption, i just clicked cancel when it asks for password/key
Also, flashing xiaomi.eu rom leads to bootloop, not sure if due to xiaomi.eu or TWRP
Click to expand...
Click to collapse
u can try the latest recovery and send some screenshots of the recovery
i have updated it recently u can try it should work fine

ROMFACTORY said:
u can try the latest recovery and send some screenshots of the recovery
i have updated it recently u can try it should work fine
Click to expand...
Click to collapse
I still see the same Jul 29th version on your AFH
{
"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"
}
For some strange reason... i never had to wait to unlock on my last three xiaomis (redmi note 4x, mix2, max3)

ugene1980 said:
I still see the same Jul 29th version on your AFH
For some strange reason... i never had to wait to unlock on my last three xiaomis (redmi note 4x, mix2, max3)
Click to expand...
Click to collapse
are u porting team group or higher moderator etc in MIUI forum??
no need to wait to unlock bootloader

[RECOVERY][UNOFFICIAL][dipper] TWRP 3.2.3.0 For Mi 8 3/9/18

{
"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://www.androidfilehost.com/?fid=1322778262903997138
Alternative link
https://drive.google.com/open?id=10-Mham_-4CFllgVWPS-QGTG5jcf9lwgH
Note this is just a hobby, but feel free to report bugs.
Kernel source: Prebuilt stock kernel
Code:
Fastboot Flashing Code
Code:
Fastboot boot Twrp.img
Flash the recovery img again inside twrp and reboot to recovery again and it will stay.
If u are new to twrp, format data in twrp and reboot to recovery again and flash this file https://androidfilehost.com/?fid=3700668719832238534 after that u can flash the rom.
If u have already twrp installed, just flash the img in twrp
BUGS:
Nothing, if u find anything contact me
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Contributors
@bassbounce
Source Code: https://github.com/omnirom/android_bootable_recovery/
Thanks to geoleonsh for the device tree.
Version Information:
Status: Stable
Created 3-9-2018
Last Updated 3-9-2018

Update 3-9-2018
Fixed vibration
Set standard language to English

bassbounce said:
Reserved
Click to expand...
Click to collapse
custom rom is coming. . .

Wait for unlock bootloader and test

Installed, it works ok, but atm i've not flashed anything....
Starts in chinese language.... not in english.
Maybe is better to enable english as default language, chinese is very difficult to parse and to find a way to set another language.
This build is different from [LR.Team] (wzsx150) TWRP-3.2.3-0806 Version, because this build use official MI 8 Kernel?

I give thanks as a future Mi 8 user

gulp79 said:
Installed, it works ok, but atm i've not flashed anything....
Starts in chinese language.... not in english.
Maybe is better to enable english as default language, chinese is very difficult to parse and to find a way to set another language.
This build is different from [LR.Team] (wzsx150) TWRP-3.2.3-0806 Version, because this build use official MI 8 Kernel?
Click to expand...
Click to collapse
Thanks, I will look in that!
It was English by default when testing but I used also some files from a Chinese tree.
Edit:
Problem found i will re-upload a new img with English language set on default.

Thanks,
Is it different in any way compared to the latest L.R Team version?

drms12 said:
Thanks,
Is it different in any way compared to the latest L.R Team version?
Click to expand...
Click to collapse
No, this is just the stock twrp with the normal additional language's.

Thank you very much.

Thanks for your efforts.
Awaiting the developers to enjoy new custom roms

Thanks man

ultrarain said:
custom rom is coming. . .
Click to expand...
Click to collapse
what you mean?

you do not say anything in which you have improved it, it works with the global beta miu10 and it is not overwritten returned original recovery? Does magisk work without bootlops?

destroymen said:
you do not say anything in which you have improved it, it works with the global beta miu10 and it is not overwritten returned original recovery? Does magisk work without bootlops?
Click to expand...
Click to collapse
It works great with magisk 17.0 and with miui 10, always flash the img of Twrp after u flash global rom or Chinese rom just to be sure.
There is nothing to improve when it already works great.
If u like some mods in the recovery u can try to compile Redwolf recovery.

Keep bootlooping for me after installing Magisk 17.1

Its working great with the latest xiaomi.eu rom and magisk 17

No bootloop for me either.
I use the latest magisk 17.1.
Treble gsi is also working with magisk 17.1 without a. Bootloop.
If u bootloop follow the guides and informations on this forum.
It isn't related to this recovery.

bassbounce said:
No bootloop for me either.
I use the latest magisk 17.1.
Treble gsi is also working with magisk 17.1 without a. Bootloop.
If u bootloop follow the guides and informations on this forum.
It isn't related to this recovery.
Click to expand...
Click to collapse
Can you give me any tutorial to flasg magisk on global stable or global beta rom?

I flashed the twrp, booted into it, rebooted into twrp again, then system, and the stock recovery still as default and can't boot into twrp, what should I do?

[RECOVERY][EXYNOS] TWRP 3.5.2_9 for S10e|S10|S10+ (UPDATE: 2021-06-07)

[RECOVERY][EXYNOS] TWRP 3.5.2_9 for S10e|S10|S10+ (UPDATE: 2021-06-07)
This project provides the TWRP recovery for the Samsung Galaxy S10e (SM-G970F, beyond0lte), S10 (SM-G973F, beyond1lte) and S10+ (SM-G975F, beyond2lte).
{
"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 recovery supports FBE decryption of AOSP based ROMs like LineageOS, OmniROM etc. There is no support for Samsung ODE in TWRP yet. If you're interested, help to provide it is welcome.
FEATURES
File-Based Encryption (FBE) support
MTP and ADB support
EXT4 support
F2FS support
EXFAT support
Provides unzip
Additional languages
KNOWN ISSUES
If you decrypt /data with TWRP, the trustzone thinks this is a failed unlock attempt and will lock the storage for 1d
'adb sideload' doesn't work
DOWNLOAD
Make sure you download the .img.xz and corresponding .asc.txt file (see INTEGRITY)! You can decompress the the recovery image using p7zip or xz.
You can always find the latest version of the recovery under the follwing links:
S10e
S10
S10+
INTEGRETY
The recovery images also come with an GPG armor file (.asc). With that file you verify that the image I created hasn't been altered.
How do you do that?
Download my gpg keyring here: https://cryptomilk.org/gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg.
Download the recovery.img.xz and recovery.img.xz.asc.txt file
Rename the recovery.img.xz.asc.txt file to recovery.img.xz.asc
Verfiy the signature using the following command:
Code:
gpg --keyring ./gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg --verify recovery.img.xz.asc
A good tutorial is: How to verify signatures for packages from the Tor Project.
SECURITY ADVICE
Don't flash ROMs or Magisk modules which set SELinux to permissive or you open your device for malware!​
What a Wurst!
Contributors
modpunk, derf elot
Source Code: https://github.com/whatawurst/android_device_samsung_beyond0lte/tree/twrp-9.0
Version Information
Status: Stable
Current Stable Version: 3.4.0-0
Stable Release Date: 2020-06-12
Created 2020-03-16
Last Updated 2020-06-12

FAQ
How do boot into the bootloader/download mode?
Here are the steps:
Turn off your phone
Press and hold the volume down and bixby keys
Connect a USB cable attached to your computer
The 'Bixby' button is the button below the volume keys.
How do boot into recovery mode?
Turn off you phone
Press and hold the volume up and bixby and power key
You can also do the above when you reboot the phone, once the screen turn black press the buttons.
How do I reboot my phone?
Press and hold the volume down and power key for at least 7 seconds.
How do I unlock my device?
Not that if you unlock your device, your phone will be factory reset! Make sure to make backups.
To unlock your device:
Go to Settings -> About Phone and find the "Build Number"
Tab the build number several times till it tells you that you unlocked the Deverloper Settings
Go to Settings -> System -> Advanded -> Developer Settings
Enable "OEM Unlock"
Reboot to bootloader mode (see above)
Follow the instruction displayed on screen and unlock your device
How do I flash the recovery?
After you unlocked the bootloader:
Boot into download mode (see above)
Flash recovery.img and vbmeta-disabled.img using Odin or Heimdall.
What is VBMETA?
Your phone has a partition for storing cryptographic hashes to verify the validity of the flashed software to all the partitions on your system. This is called Android Verified Boot.
In order to flash a recovery.img you need to replace the VBMETA image with a custom image to disable the checks. You can find a vbmeta-disabled.img here.

CHANGELOG
2020-07-24
Update to Linux Kernel 4.14.189
Updated to CTF3 blobs
Removed TWRP app
2020-06-09
Update to TWRP 3.4 (Fixes for SAR and multi user decryption)
Update to Linux Kernel 4.14.183
Fixed ADB only mode

Good Job!

ExtremeGrief said:
Good Job!
Click to expand...
Click to collapse
Thank you
I'm working on S10 and S10+.
If someone is interested to get it working with stock we could look into Samsung ODE. I don't need it for LineageOS.

modpunk said:
Thank you
I'm working on S10 and S10+.
If someone is interested to get it working with stock we could look into Samsung ODE. I don't need it for LineageOS.
Click to expand...
Click to collapse
I don't think TWRP supports Samsung FDE.
By the way for S10(+) just change kernel.

Alright so what are the differences between this and the already available twrp by ian?

stefan243546 said:
Alright so what are the differences between this and the already available twrp by ian?
Click to expand...
Click to collapse
See the features list, this recovery has support for FBE decryption on AOSP based ROMs. Also USB is working correctly and not making your phone so hot that you can fry an egg on it.

It should be possible to format /data and use FDE encryption now.

@modpunk
Thanks a lot. I was waiting for this for some time now.
Two questions:
1) FBE: Do i need to come from stock to have FBE working? Or is it ok to format /data from within TWRP to activate FBE with the right settings in fstab? I am using Lineage. Did you try that combination? I tried to keep FBE in the past but upon rebooting LineageOS TWRP kept stuck in the splash screen because it was not able to handle FBE.
2) Would it be possible to provide the build steps or would you consider pushing your work on FBE into the official repo? As i can see Ianmac's TWRP version isnt capable of dealing with FBE yet so it would be great to have it official.
Thanks for all your hard work. Much appreciated.

angela5246 said:
@modpunk
Thanks a lot. I was waiting for this for some time now.
Two questions:
1) FBE: Do i need to come from stock to have FBE working? Or is it ok to format /data from within TWRP to activate FBE with the right settings in fstab? I am using Lineage. Did you try that combination? I tried to keep FBE in the past but upon rebooting LineageOS TWRP kept stuck in the splash screen because it was not able to handle FBE.
Click to expand...
Click to collapse
Normally, LineageOS sets up FBE by default if the fstab is configured to use FBE. I'm currently working on a LineageOS ROM for the S10e and FBE is working just fine. Normally all you have to to is to format /data. I dunno which ROM you're using and if it has FBE turned on by default.
angela5246 said:
2) Would it be possible to provide the build steps or would you consider pushing your work on FBE into the official repo? As i can see Ianmac's TWRP version isnt capable of dealing with FBE yet so it would be great to have it official.
Thanks for all your hard work. Much appreciated.
Click to expand...
Click to collapse
Take a look at https://github.com/whatawurst and check the corresponding twrp-9.0 branches (Kernel, platform, device).

I see.
So just for clarification: Do you say FBE should work in theory with LOS or did you try it actually? Let me tell you about my experience.
I came from stock to LOS 17 provided by Ivan. Kept the original fstab which has FBE enabled. Didnt format /data so FBE was kept. After flashing LOS from within TWRP i booted into LOS. All fine. But on the first reboot or shutdown the phone automatically goes to TWRP. And there it stucks at the splash screen. At that point only flashing to stock is helping. So Ianmac's TWRP is not able to handle FBE. Are you sure this is different with yours?

I've added TWRP for more devices.

With the current release MTP isn't working. However I think I have a fix.

Will this twrp work with one ui 2.1?

I dont think so. But the ctc9 sources are up now.

mcgomfer said:
Will this twrp work with one ui 2.1?
Click to expand...
Click to collapse
Why shouldn't it work?

hanspampel said:
I dont think so. But the ctc9 sources are up now.
Click to expand...
Click to collapse
I don't see what the recovery has to do with CTC9 kernel sources at all.

I've uploaded new versions which fixes MTP.

modpunk said:
I've added TWRP for more devices.
Click to expand...
Click to collapse
Can you support Note10+ devices?
Sent from my SM-N975F using Tapatalk

Question Custom recover for Xperia 10 III

I want to know any compatible custom recovery for Xperia 10 III. I tried installing TWRP but that ended up bricking my phone.
I don't know if it helps but it is an XQ-BT52.

TrulyPain said:
I want to know any compatible custom recovery for Xperia 10 III. I tried installing TWRP but that ended up bricking my phone.
I don't know if it helps but it is an XQ-BT52.
Click to expand...
Click to collapse
no any custom recovery available for your devices

ada12 said:
no any custom recovery available for your devices
Click to expand...
Click to collapse
Okay, would you expect any custom recovery being released soon or is my best hope to create an myself?

TrulyPain said:
Okay, would you expect any custom recovery being released soon or is my best hope to create an myself?
Click to expand...
Click to collapse
Best solution is compile yourself ...
3day ago I have used twrp trees generator from stock recovery.img
Here sources https://github.com/Aarqw12/twrp_lena
But I no compile succefully for now I'm really no experimented for twrp stuff...
or I will try compile stock recovery witch signature verificstion disabled for allow all zip flash

TrulyPain said:
Okay, would you expect any custom recovery being released soon or is my best hope to create an myself?
Click to expand...
Click to collapse
good news I booted just now twrp compiled
I need fix some issue before open thread

bug no fixed : internal storage decryption ( mtp too so )
work : booting , touchscreen , fastbootd, external storage / usb otg , backup , access to partition system,vendor ...
I hope in 1-2 day its stable

ada12 said:
bug no fixed : internal storage decryption ( mtp too so )
work : booting , touchscreen , fastbootd, external storage / usb otg , backup , access to partition system,vendor ...
I hope in 1-2 day its stable
Click to expand...
Click to collapse
It is sufficient for custom roms
I have a small request. Can you send me system and vendor partitions? Or at least tell me how to get it.
In LG, I could use qfil for this. In Sony I can't do that anymore
In adb I don't see vendor and system
{
"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"
}

Kyrimeas said:
It is sufficient for custom roms
I have a small request. Can you send me system and vendor partitions? Or at least tell me how to get it.
In LG, I could use qfil for this. In Sony I can't do that anymore
In adb I don't see vendor and system
View attachment 5469595
Click to expand...
Click to collapse
Its fstab I extracted from /vendor/etc , its give you response how is mounted

For encryption, you can just decrypt it after installing twrp. Then you'll be able to see your sdcard no problem.
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com

ada12 said:
bug no fixed : internal storage decryption ( mtp too so )
work : booting , touchscreen , fastbootd, external storage / usb otg , backup , access to partition system,vendor ...
I hope in 1-2 day its stable
Click to expand...
Click to collapse
Got any updates on how it's going?

TrulyPain said:
Got any updates on how it's going?
Click to expand...
Click to collapse
No, when I add qcom encryption & blobs recovery no boot...
Without encryption stuff its boot but I get 0mb internal storage

Has there been any progress on the matter yet?
It would be really great if we have the ability to flash unsigned zip files.
@ada12 can you provide me your TWRP build?
I would love to test it.
Even without working decryption it would be a huge added value

@psychofaktory what are you trying to accomplish with the recovery? There's a Magisk module (Backup, by Draco) which gives you a command line tool that dumps partition images, and you can flash them with fastboot. I've dumped the boot partition and compared the checksum with the one I flashed (the one patched by Magisk) and they're identical.
There's also a stock recovery that's very limited but allows you to do factory reset.

It would give the ability to flash unsigned zip files.

This guy has a twrp tree for 10 III. Maybe it can be built and used. Optionally, we can modify the tree from 10 II.
https://github.com/pintaf/android_device_sony_lena_twrp

psychofaktory said:
Has there been any progress on the matter yet?
It would be really great if we have the ability to flash unsigned zip files.
@ada12 can you provide me your TWRP build?
I would love to test it.
Even without working decryption it would be a huge added value
Click to expand...
Click to collapse
I have no shared in public any build because its unusable for user , twrp boot but impossible to mount internal storage , we simply cant flash gapps zip and more ... I need help from pro twrp dev for encryption but seem nobody care for this devices.
they are no sources twrp usable for lena

Would it work to disable the encryption temporarily so that the internal memory of TWRP does not have to be decrypted at all?
It would be really awesome if more developers would show interest in the device.
It's a really great device with a lot of potential.

Can anyone provide TWRP for Xperia 10 III?

ada12 said:
I have no shared in public any build because its unusable for user , twrp boot but impossible to mount internal storage , we simply cant flash gapps zip and more ... I need help from pro twrp dev for encryption but seem nobody care for this devices.
they are no sources twrp usable for lena
Click to expand...
Click to collapse
What kernel are you using?
Maybe some dev from another Xperia could help you.
@modpunk @Sjll

Kyrimeas said:
What kernel are you using?
Maybe some dev from another Xperia could help you.
@modpunk @Sjll
Click to expand...
Click to collapse
I found the solution, flash litegapps systemless as magisk module https://sourceforge.net/projects/li...MAGISK]LiteGapps++_v2.3_official.zip/download