[RECOVERY][UNOFFICIAL] TWRP 3.2.3-0 for leo [01-09-2018] - Xperia Z3 Android Development

{
"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"
}
Introduction
Hi to all dear Z3 users. This is my first TWRP build, I used omni minimal TWRP source and kernel from Sony git.
I hope you enjoy this.
How to install
Fist of all you MUST flash lastest 23.5.A.1.291 firmware with FlashTool at least one time, for upgrade the bootloader (You need this upgrade for boot on recovery).
Via fastboot
Reboot your phone on fastboot mode.
Flash recovery using this command:
Code:
fastboot flash FOTAKernel <filename>
Via zip (You need a working recovery installed)
Download the zip and put it on your internal or external memory.
Reboot to recovery.
Flash the zip.
Via Official TWRP App (You need root)
Install the app from Google Play Store and download the zip.
Extract recovery.img and copy it to your internal or external memory.
Open the app, give root permissions and tap on TWRP FLASH.
Tap on Select a file to flash...
Select the recovery.img and flash it.
Download
TWRP
Thanks to
@GreyLeshy a lot of thanks for this great dev, he helped me a lot for make this possible, build this recovery and he had a lot of patience with this noob dev.
@Dees_Troy for TWRP.
@omni Team for TWRP Minimal Source.
XDA:DevDB Information
TWRP for leo, Tool/Utility for the Sony Xperia Z3
Contributors
ShadowElite, GreyLeshy
Source Code: https://github.com/ShadowElite117/android_sony_shinano_twrp
Version Information
Status: Stable
Created 2018-09-01
Last Updated 2018-09-01

FAQs
Q. How boot on recovery?
A. With the device turned off, press power and vol- at same time until it vibrates.
Q. Does it works with Z3 dual sim?
A. It should work, since Z3 and Z3 dual sim are like 99% the same device, but is not tested (yet) so you Z3 dual users have to test it and report.
Q. Does it works with stock or custom ROMs?
A. At this momment I know that it is fully compatible with stock ROMs (or stock based ROMs) but at this momment is not tested with custom ROMs, so you users have to test it and report.

Thank you so much for the latest TWRP for our device. I use it with official CarbonROM from
https://forum.xda-developers.com/z3/orig-development/8-1-x-carbonrom-cr-6-1-t3771546
and it works like a charm. The only recovery I could find, which enables full-featured OTA updates and installation of ROM and GApps without up- and downgrade cycle.
Keep up the good work
Jo

Thanks for your work bro
I noticed after using this recovery on Z3 dual that when I flash a custom rom, baseband version and imei codes disappear

ShadowElite said:
FAQs
Q. Does it works with stock or custom ROMs?
A. At this momment I know that it is fully compatible with stock ROMs (or stock based ROMs) but at this momment is not tested with custom ROMs, so you users have to test it and report.
Click to expand...
Click to collapse
Yes, this work on custom rom.
- D6603 with latest CARBON Rom.:good:

Openrecoveryscript issue
@ShadowElite the recovery not execute "openrecoveryscript"
D6603, CARBON CR 6.1

please question friend, and thanks.. i flash recovery.img with flashtools? this is kernel? because is zip, my phone xperia z3 android 6.0.1 and .291 thanks

danilo_scala said:
please question friend, and thanks.. i flash recovery.img with flashtools? this is kernel? because is zip, my phone xperia z3 android 6.0.1 and .291 thanks
Click to expand...
Click to collapse
This is custom recovery please read OP carefully, already clearly. If you still didn't got the point, please stay away because can brick your phone

Hi,
every time i enter recovery i have to setup time (not working), language...
Anyone?

gsausalito said:
Hi,
every time i enter recovery i have to setup time (not working), language...
Anyone?
Click to expand...
Click to collapse
Can you mount data partition? If not, then you coud try to format data.

@ShadowElite so its a recovery for Android 6 Mashmallow compatible with higher Android versions? amazing. EDIT: doesn't boot up.

Hi. Thanks for your work.
I installed this TWRP on my Sony Xperia Z3 (D6603) running Marshmallow 6.0.1 (23.5.A.1.291) and it only booted in recovery mode. Then i installed OMNI ROM (7.1.2) and since then it only boots into system. Is there any way to boot recovery mode and also have the system working? Anything to flash? Thank you in advance.

This recovery is compatible with carbon, but with omni results with sim not being detected for me.

This recovery working on d6633????

At first... my English is not good. SRY.
LOOK..
my TWRP is 3.0.2-0. (on 23.5.A.1.291)
I attempted to install TWRP_3.2.3-0 with TWRP is 3.0.2-0. It was successful
but, after reboot phone and back too TWRP, No change! my TWRP version still 3.0.2-0!!!
What to do???

I can not update from TWRP 2.8.0.1 to 3.x.x.x. ,please help...

Technoolli said:
I can not update from TWRP 2.8.0.1 to 3.x.x.x. ,please help...
Click to expand...
Click to collapse
Turn your phone off. Then, hold its volume up button whilst connecting it to the computer through an USB cable, until you notice its led lighten up in blue color. Let's suppose your TWRP image file is named recovery.img. Then, in a terminal command window, enter:
fastboot flash FOTAKernel recovery.img
Replace recovery.img by the actual name of your TWRP image file. And everything else is case sensitive. If you have a Windows computer and don't have the fastboot command yet, search xda for 'Minimal adb & fastboot'.
To enter TWRP after flashing it, starting with your phone turned off, hold both the power and volume down buttons. When your phone vibrates (as if it was being turned on), release the power button. Some seconds later, release the volume down button.
Sent from my Xperia Z5 Compact using XDA Labs

casouzaj said:
Turn your phone off. Then, hold its volume up button whilst connecting it to the computer through an USB cable, until you notice its led lighten up in blue color. Let's suppose your TWRP image file is named recovery.img. Then, in a terminal command window, enter:
fastboot flash FOTAKernel recovery.img
Replace recovery.img by the actual name of your TWRP image file. And everything else is case sensitive. If you have a Windows computer and don't have the fastboot command yet, search xda for 'Minimal adb & fastboot'.
To enter TWRP after flashing it, starting with your phone turned off, hold both the power and volume down buttons. When your phone vibrates (as if it was being turned on), release the power button. Some seconds later, release the volume down button.
Sent from my Xperia Z5 Compact using XDA Labs
Click to expand...
Click to collapse
I wanted to install the following recovery as follows: fastboot flash FOTAKernel twrp-3.3.1-z3-20200212.img but after restarting I'm still on the old version 2.8.0.1
I can update to version 3.2.3.-2 twrp_z3_2019-03-13.img but not to the latest ...

Technoolli said:
I wanted to install the following recovery as follows: fastboot flash FOTAKernel twrp-3.3.1-z3-20200212.img but after restarting I'm still on the old version 2.8.0.1
I can update to version 3.2.3.-2 twrp_z3_2019-03-13.img but not to the latest ...
Click to expand...
Click to collapse
Install new version
Power off
Hold power+volume up
Release power after vibration

3dguru said:
Install new version
Power off
Hold power+volume up
Release power after vibration
Click to expand...
Click to collapse
Then I'm back to the old version, how do I get the new version ... Need it to switch to Android 10 ... Thank you

Related

UB-14.6.A.1.236-stock ftf-root

Hello!
To give a fresh start to your Z Ultra on a fresh install of 14.6.A.1.236 after flashing ftf and wiping all data, follow the follwing steps
1) Flash ftf using the Flashtool.
2) Complete the initial setup and enable developer mode
3) Open flashtool
4) Connect your phone and accept the ADB request on your phone
5) Copy the lastest Supersu.zip on your phone
6) Download http://download.cyanogenmod.org/get/jenkins/138873/cm-12.1-20151212-NIGHTLY-togari-recovery.img
7) In flashtool click on the fastboot mode and select Reboot into fastboot mode (Via adb)
8) Then Select the kernel to hotboot. and select the .img file you've just downloaded.
9) Once in recovery, select the Supersu.zip file.
10) Reboot
Tada.........................You're rooted
If I've helped you, pls press thanks.
Credits:
cyanogenmod.org for the kernel
Chainfire for SuperSU
I bought XZU 10 days ago and it updated to 14.6.A.1.236
Thanks to your guide, I rooted and got SuperSU now.
But I could not enter CM Recovery after trying Vol U or D + Power button.
pckoloji said:
I bought XZU 10 days ago and it updated to 14.6.A.1.236
Thanks to your guide, I rooted and got SuperSU now.
But I could not enter CM Recovery after trying Vol U or D + Power button.
Click to expand...
Click to collapse
U need to hit Vol+/- when booting up, it should vibrate and LED should light up to Yellow or Pink, once it vibrates and LED turns on, hit Vol+/- that should put u in recovery
Sent from my ONE A2005 using Tapatalk
pckoloji said:
I bought XZU 10 days ago and it updated to 14.6.A.1.236
Thanks to your guide, I rooted and got SuperSU now.
But I could not enter CM Recovery after trying Vol U or D + Power button.
Click to expand...
Click to collapse
İf your bootloader is unlocked you ca use the Sony Open bootloader this way you wont loose the recover when you flash another rom.
Yardım gerekirse pm at.
Vol+ & Power > Nothing, no boot
Vol- & Power > Normal boot procedure, no LED light
fnldstntn said:
İf your bootloader is unlocked you ca use the Sony Open bootloader this way you wont loose the recover when you flash another rom.
Yardım gerekirse pm at.
Click to expand...
Click to collapse
Yes bootloader is unlocked now
Sony Emma detects phone but says no services for your device. So I don't know if it has Sony Open bootloader or not.
{
"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"
}
OK so I installed ZU-lockeddualrecovery on top of those and can enter either TWRP or Philz now.
Also installed NDRUtils from Play Store.
bootloader
Hi guys. I have Z Ultra C6833 with the latest build number which is 14.6.A.1.236 and with locked bootloader. I updated my phone via online update of Sony and without flash tools. I have question:
1) can I use your method in my phone? I mean should I unlock my bootloader or not?
2) does it create problem that I updated my phone via online update and without Flashtools?
Thanks
Perfect, easiest method yet.
muntaha_v3 said:
Hello!
To give a fresh start to your Z Ultra on a fresh install of 14.6.A.1.236 after flashing ftf and wiping all data, follow the follwing steps
1) Flash ftf using the Flashtool.
2) Complete the initial setup and enable developer mode
3) Open flashtool
4) Connect your phone and accept the ADB request on your phone
5) Copy the lastest Supersu.zip on your phone
6) Download http://download.cyanogenmod.org/get/jenkins/138873/cm-12.1-20151212-NIGHTLY-togari-recovery.img
7) In flashtool click on the fastboot mode and select Reboot into fastboot mode (Via adb)
8) Then Select the kernel to hotboot. and select the .img file you've just downloaded.
9) Once in recovery, select the Supersu.zip file.
10) Reboot
Tada.........................You're rooted
If I've helped you, pls press thanks.
Credits:
cyanogenmod.org for the kernel
Chainfire for SuperSU
Click to expand...
Click to collapse
Was there a download link for the ftf?
Kingoroot get te apk from the site... Use Google search.
Sent from my C6833 using XDA-Developers mobile app
pckoloji said:
Vol+ & Power > Nothing, no boot
Vol- & Power > Normal boot procedure, no LED light
Click to expand...
Click to collapse
Me (c6802, same firmware) too having same issue, cant see bootloader (just a blue led is there, nothing else). What should i do? I have access to fastboot and flash mode though (vol + + plug cable | vol - + plug cable). But i cant to go to recovery. Help, thanks in advance.
:laugh:
pckoloji said:
Yes bootloader is unlocked now
Sony Emma detects phone but says no services for your device. So I don't know if it has Sony Open bootloader or not.
Click to expand...
Click to collapse
YOU SHOULD TRY FLASHTOOL NOT EMMA. THIS IS NOT WORKING FOR ME ALSO
muntaha_v3 said:
Hello!
To give a fresh start to your Z Ultra on a fresh install of 14.6.A.1.236 after flashing ftf and wiping all data, follow the follwing steps
1) Flash ftf using the Flashtool.
2) Complete the initial setup and enable developer mode
3) Open flashtool
4) Connect your phone and accept the ADB request on your phone
5) Copy the lastest Supersu.zip on your phone
6) Download http://download.cyanogenmod.org/get/jenkins/138873/cm-12.1-20151212-NIGHTLY-togari-recovery.img
7) In flashtool click on the fastboot mode and select Reboot into fastboot mode (Via adb)
8) Then Select the kernel to hotboot. and select the .img file you've just downloaded.
9) Once in recovery, select the Supersu.zip file.
10) Reboot
Tada.........................You're rooted
If I've helped you, pls press thanks.
Credits:
cyanogenmod.org for the kernel
Chainfire for SuperSU
Click to expand...
Click to collapse
CM12.1-20151212-NIGHTLY togari recovery was deleted
Could you please upload this file? thanks!
ultimize said:
CM12.1-20151212-NIGHTLY togari recovery was deleted
Could you please upload this file? thanks!
Click to expand...
Click to collapse
Hi
Sorry for the delayed reply
You still need it?
works for me.
do you have an idea why can't I remount /system folder though rooting was successful?
muntaha_v3 said:
Hi
Sorry for the delayed reply
You still need it?
Click to expand...
Click to collapse
can u please give me a new link? i cant access the web from the first link.... thank u very much
Pretty please re-upload the recovery.img file.
Please re-upload revocery.img
Update Download Link
muntaha_v3 said:
Hi
Sorry for the delayed reply
You still need it?
Click to expand...
Click to collapse
Please update the file , no body can download
and is working for c6802 ?

[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy Note8 Exynos

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Official TWRP 3.6.1-* For Galaxy Note8 Exynos​Only for exynos variants - N950F (Single SIM: Europe, Australia); N950FD (Global Dual SIM: Europe, LATAM, Brazil; Australia); N950N (South Korea)
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Features:
Code:
- built from Pie kernel source
- built from android-9.0 recovery sources
- built in full 64 mode
- fully compatible with Android 8.*/9.0/10.0
Downloads:
https://twrp.me/samsung/samsunggalaxynote8.html
Instructions:
Odin
Download latest Odin zip from downloads.corsicanu.ro/samsung
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Bixby Key+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Bixby key" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Bixby key" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
Device tree - https://github.com/TeamWin/android_device_samsung_greatlte
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal8895/tree/android-9.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, jesec, geiti94, dyneteve, testers, donors and anyone else involved in making this possible
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
FAQ / Further reading
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware.
Q: I get "Failed to mount /preload message", what to do?
A: From wipe menu select Advanced Wipe, select preload partition to be wiped and reboot recovery.
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
No Download. Img file?
corsicanu said:
TWRP
Click to expand...
Click to collapse
Well done mate
Benny100 said:
No Download. Img file?
Click to expand...
Click to collapse
Its directly in the github link
No IMG file
https://github.com/TwrpBuilder/android_device_samsung_greatlte/releases
https://github.com/TwrpBuilder/android_device_samsung_greatlte/tags
Benny100 said:
No IMG file
https://github.com/TwrpBuilder/android_device_samsung_greatlte/releases
https://github.com/TwrpBuilder/android_device_samsung_greatlte/tags
Click to expand...
Click to collapse
Did you tried taping on Assets?
Found and is working Thx!...
I am using a modified twrp without data fix problem. Should i just flash the image file or i have to format data and setup from zero
tabish84 said:
I am using a modified twrp without data fix problem. Should i just flash the image file or i have to format data and setup from zero
Click to expand...
Click to collapse
datafix is for oreo issues where twrp could not properly access internal storage.
format is if you come from stock rom and still have encrypted storage.
Very nice start of the Note 8 Exy journey Bro ?
It is a big pleasure to see U around N8 development!
I am really excited now for the nearest few months and Your 'crazy' ideas which always bring some goodies ?
Thx for Ur efforts and good luck! ?
Works great thank you.
Dev Base August
Sent from my SM-N950F using XDA Labs
After flashing .img (was on 3.2.1.1) I get "Recovery is not seandroid enforcing", only when booting into recovery.
Seems to work fine otherwise.
N950N
Repulsa's ROM.
Is this normal behavior?
Pinan said:
After flashing .img (was on 3.2.1.1) I get "Recovery is not seandroid enforcing", only when booting into recovery.
Seems to work fine otherwise.
N950N
Repulsa's ROM.
Is this normal behavior?
Click to expand...
Click to collapse
im on the same phone and no such issue with new twrp i was on a newer twrp than yours and had formatted and flash dm verty zip initially from stock oreo. dirty flash your rom again just to see. if still no go then follow OP to the T to reflash it correctly.
did you ever flash oreo bootloader? because from what i understand, looks like you were on nougat before and flashed a oreo rom without upgrading fully to stock oreo before hand.
bober10113 said:
1. im on the same phone and no such issue with new twrp i was on a newer twrp than yours and had formatted and flash dm verty zip initially from stock oreo. dirty flash your rom again just to see. if still no go then follow OP to the T to reflash it correctly.
2. did you ever flash oreo bootloader? because from what i understand, looks like you were on nougat before and flashed a oreo rom without upgrading fully to stock oreo before hand.
Click to expand...
Click to collapse
1. I went from stock rom to Repulsa, using SuperSU. No issues.
2. Nougat to Oreo. Could be the issue. I did not update the BL. Don't know if the ROM did. I will check.
Do you happen to have a link to the correct BL?
Thanks for the tips!
Pinan said:
1. I went from stock rom to Repulsa, using SuperSU. No issues.
2. Nougat to Oreo. Could be the issue. I did not update the BL. Don't know if the ROM did. I will check.
Do you happen to have a link to the correct BL?
Thanks for the tips!
Click to expand...
Click to collapse
i could extract it but u can basically get it from unziping stock.(see link below)
since we are on the n950n, I'm almost sure repulsa rom didnt update it because mostly all roms that might include the BL will have mainly the F/DS bootloader, most dont even update it though.
latest BL would be U3. might be a good idea to update cp(modem) while you are at it too, so grab latest stock firmware and extract both from:
https://samsung-firmware.org/model/SM-N950N/
if download is slow, i can provide these 2 files in a few minutes because package is so big just to get them smaller files.
so only put bl and cp in odin and at least you will be on the latest stuff. dont know what is taking so long for BL U4 to arrive for our korean n950ns....
edit
latest bl and cp for N950N only:
https://1drv.ms/f/s!AhXVLDDj8g3AgdYhY8DslnHgCVMMEw
i also put samfirm downloader for future reference, its a fast way to get latest firmware. those hosting websites are so slow sometimes... updato.com is a fast one but firmwares arent always up to date though
bober10113 said:
latest bl and cp for N950N only:
https://1drv.ms/f/s!AhXVLDDj8g3AgdYhY8DslnHgCVMMEw
i also put samfirm downloader for future reference, its a fast way to get latest firmware. those hosting websites are so slow sometimes... updato.com is a fast one but firmwares arent always up to date though
Click to expand...
Click to collapse
Thank you very much. Most kind of you. :good:
Yes. I've used SamFirm before. Faster indeed.
@ bober10113.
All's well after new CP and BL. no more "Recovery is not seandroid enforcing".
Thanks again.
Good job mate :good:
Really glad we have this dev around. Will flash shortly

[RECOVERY][3.5.A10-TWRP]Unnoficial for (GAUGUIN) Xiaomi Mi10T Lite, Mi10i, Redmi Note 9 Pro 5G (BETA)

{
"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:
We are not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at us for messing up your device, we will laugh at you.
WORKING:​
Decryption userdata with eu roms
Screen brightness settings
Correct screenshot color
MTP
ADB
Vibration
Sideload
To flash the Twrp​Download the recovery and copy to adb folder
Open terminal
Code:
fastboot flash recovery nameofrecovery.img
fastboot boot nameofrecovery.img
or
fastboot reboot with vol + to boot
Source Code​https://github.com/geoanto555/android_device_xiaomi_gauguin
https://github.com/TeamWin/android_bootable_recovery
Prebuilt Stock Kernel
Thanks to ​TeamWin Recovery Project
all testers and developers
Thanks to Μιχάλης (chariPower) for the information(sideload)
Download Link-s​twrp_gauguin_3.5.A10_05-01-2021
twrp_gauguin_3.5.A10_07-02-2021 fixed sideload and mtp
twrp_gauguin_3.5.A10_18-02-2021 fixed backup data error 255 (/data/extm)
twrp_gauguin_3.5.A10_05-03-2021 Fixed Mtp after format data & reboot recovery. (if the MTP does not open, try reboot in twrp again)
twrp_gauguin_3.5.1.A10_30-03-2021 fixed fastbootd
it’s first time i am using xiaomi phone. my device is RMN9P5G and waiting for unlocked. can i flash your recovery and install the latest stable EU rom in mifirm.net: V12.0.8.0.QJSCNXM immediately after unlock success?i’m worry a bit because some members report that internal, user data be encrypted and cannot access..
kien_vip said:
it’s first time i am using xiaomi phone. my device is RMN9P5G and waiting for unlocked. can i flash your recovery and install the latest stable EU rom in mifirm.net: V12.0.8.0.QJSCNXM immediately after unlock success?i’m worry a bit because some members report that internal, user data be encrypted and cannot access..
Click to expand...
Click to collapse
From my experience, the recovery cannot decrypt the stock ROMs, you have to flash a custom ROM (Arrow and Lineage are the only 2 right now), or flash a xiaomi EU ROM.
Copy the rom to sdcard or usb otg.
Format data
Reboot recovery
Flash rom.
With xiaomi eu decryption works...
Decryption on stock rom works if I hotboot TWRP (fastboot boot twrp.img). If I flash it, TWRP doesn't prompt me for a password when started and keeps data encrypted.
Hi there, thank you for the TWRP. Is there any chance to decrypt also user 999 for the Dual apps on the .eu ROMs?
not for now. I will upload new version soon
ilyachelsea said:
Is there any chance to decrypt also user 999 for the Dual apps on the .eu ROMs?
Click to expand...
Click to collapse
twrp_gauguin_MI10TL-RN9P5G_MI10I_3.5.A10_18-02-2021_BL-L
Fixed backup userdata (error 255 for data/extm)
User 999 can be decrypted only with default password ( without pattern-pin-pass) for now.
Thank you, but my password is PIN, anyway the recent twrp can't decrypt user 999. It is the message in red: "Failed decrypt user 999"
Only without pin,pass,pattern can be decrypted user999
It's a pity. I intend to back up also user 999 to keep my dual banking apps with the access data. If I first remove the PIN, and backup user 999 with the TWRP, after restore I will have to set up access again. This kills the benefit of the decryption and makes backup of 999 useless.
Thank you anyway and I hope, NO PIN is the temporary requirement of this version.
Hello everybody! Last week I unlocked the bootloader of my gauguin and initially I tried the official TWRP Recovery released by TWRP official page but it didn't work correctly and I couldn't flash zips, so I tried this beta version released by geoanto555 and it worked smoothly, I flashed zips and I had root permissions... But last night the smartphone had the battery low and it turned off, when I connected it to the charger it automatically reboot in fastboot and I can only enter in recovery mode. Sorry but I'm new in the modding world and I don't know what to do.. First brick.. What I did wrong? Anybody can help me? Is there anything I can do or I have to buy a new phone? Thanks to who will answer . Good evening.
devedel said:
Hello everybody! Last week I unlocked the bootloader of my gauguin and initially I tried the official TWRP Recovery released by TWRP official page but it didn't work correctly and I couldn't flash zips, so I tried this beta version released by geoanto555 and it worked smoothly, I flashed zips and I had root permissions... But last night the smartphone had the battery low and it turned off, when I connected it to the charger it automatically reboot in fastboot and I can only enter in recovery mode. Sorry but I'm new in the modding world and I don't know what to do.. First brick.. What I did wrong? Anybody can help me? Is there anything I can do or I have to buy a new phone? Thanks to who will answer . Good evening.
Click to expand...
Click to collapse
If you have access to the recovery, or fastboot, you can flash the original firmware with fastboot, but watch out, for some reason, when i flash the original rom from Windows using fastboot, it crashes, but with Linux it just works
AnibalSP said:
If you have access to the recovery, or fastboot, you can flash the original firmware with fastboot, but watch out, for some reason, when i flash the original rom from Windows using fastboot, it crashes, but with Linux it just works
Click to expand...
Click to collapse
In my device the rom is still the original. Do I have to do it anyway? What can happen if I try to flash a custom rom? If I only do the factory reset will I lose also TWRP?
AnibalSP said:
If you have access to the recovery, or fastboot, you can flash the original firmware with fastboot, but watch out, for some reason, when i flash the original rom from Windows using fastboot, it crashes, but with Linux it just works
Click to expand...
Click to collapse
I'm trying to do this with XiaoMiTool v2.. Thanks
devedel said:
In my device the rom is still the original. Do I have to do it anyway? What can happen if I try to flash a custom rom? If I only do the factory reset will I lose also TWRP?
Click to expand...
Click to collapse
If you can boot to android, or boot to TWRP / Orangefox, you don't need to flash again miui stock
If you flash a second rom, the worst thing that can happen, is that the rom may not work, but you wipe the internal memory (dalvik cache and data) and it should be running again
If you loose twrp for some reason, you can flash it again with xiaomitoolv2, or with fastboot
I'd recommend to you to try rooting, installing roms and similars things in an old phone if you don't are confident / know what are you doing, you will learn a lot in a few days of tinkering.
Anyone know what I need? I can't finish the installation of a official xiaomi rom to unbrick my device
devedel said:
View attachment 5257349
Anyone know what I need? I can't finish the installation of a official xiaomi rom to unbrick my device
Click to expand...
Click to collapse
Hi,
Download the official stock rom
Dont use XiaoMiToolV2, instead use MiFlash (official tool). Works for me every time. Then connect your phone in fastboot and flash all, I use the clean all and lock option which relocks my bootloader but you could just clean all and leave the bootloader unlocked. Then you can start again
fizzy900 said:
Hi,
Download the official stock rom
Dont use XiaoMiToolV2, instead use MiFlash (official tool). Works for me every time. Then connect your phone in fastboot and flash all, I use the clean all and lock option which relocks my bootloader but you could just clean all and leave the bootloader unlocked. Then you can start again
Click to expand...
Click to collapse
Hi, thanks for your advice.
Do you think it can works if usb debugging is off? I'm afraid I've disabled it the night the phone bricked.
I did wrong too many things but was my first try, tomorrow I'll buy a new Mi 10t lite and I'll try again, using more precautions.
Thank you all anyway, good evening.
devedel said:
Hi, thanks for your advice.
Do you think it can works if usb debugging is off? I'm afraid I've disabled it the night the phone bricked.
I did wrong too many things but was my first try, tomorrow I'll buy a new Mi 10t lite and I'll try again, using more precautions.
Thank you all anyway, good evening.
Click to expand...
Click to collapse
Enabled debugging is needed for adb when the system is running. For fastboot it does not matter.

[RECOVERY] [UNOFFICIAL] TWRP-3.7.0 [togari] [2022/12/13]

{
"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"
}
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
BUGS:
You tell me.
FLASHING INSTRUCTIONS:
fastboot erase recovery
fastboot flash recovery twrp-3.x.x-x-togari.img
Click to expand...
Click to collapse
Changelogs:
2022/12/13
Updated to TWRP 3.7.0.
2021/10/03
Fixed SONY boot logo.
2021/09/24
Fixed touch issues.
Click to expand...
Click to collapse
CREDITS:
@ 115ek on Github for his amami base trees.
SOURCE CODE:
device-tree: LINK
DOWNLOADS:
DOWNLOAD
On C6802 3g model, There is no recovery partition. Only boot and FOTAkernel partitions. So I got boot into this recovery by "fastboot boot twrp-3.5.2_9-0-togari.img". Touchscreen not works. Seems adb working but have no idea what should I do.
Bikkoism said:
On C6802 3g model, There is no recovery partition. Only boot and FOTAkernel partitions. So I got boot into this recovery by "fastboot boot twrp-3.5.2_9-0-togari.img". Touchscreen not works. Seems adb working but have no idea what should I do.
Click to expand...
Click to collapse
Thanks for reporting, but since i don't have this device in hand so i can't really debugging with the touch issues, can you grab dmesg from adb for me?
tarkzim said:
Thanks for reporting, but since i don't have this device in hand so i can't really debugging with the touch issues, can you grab dmesg from adb for me?
Click to expand...
Click to collapse
Something more serious problem is going here. After boot into your twrp once, and then reboot to system by adb reboot, My device stuck at bootloop. At last, after factory reset(Originally installed bootstrap recovery), my device got blackscreen bricked. I need to handle this problem first.
Edit: My device can not boot into system now but I could managed get into your twrp again. So I attached dmesg file. https://www.mediafire.com/file/tassxmx7fac9qwm/dmesg.txt/file
Bikkoism said:
Something more serious problem is going here. After boot into your twrp once, and then reboot to system by adb reboot, My device stuck at bootloop. At last, after factory reset(Originally installed bootstrap recovery), my device got blackscreen bricked. I need to handle this problem first.
Click to expand...
Click to collapse
Damn it... sound not good bro,
I found a scripts in XDA for fixing touch issues, maybe i can integrate it into my TWRP...
Bikkoism said:
Edit: My device can not boot into system now but I could managed get into your twrp again. So I attached dmesg file. https://www.mediafire.com/file/tassxmx7fac9qwm/dmesg.txt/file
Click to expand...
Click to collapse
Thanks for your dmesg logs, it seems like the driver was loading fine, i will see what i can do.
BTW, for your current ROM, maybe you should try to flash the boot.img of it again?
tarkzim said:
Thanks for your dmesg logs, it seems like the driver was loading fine, i will see what i can do.
BTW, for your current ROM, maybe you should try to flash the boot.img of it again?
Click to expand...
Click to collapse
I flashed stock 14.6.A.1.236 customized US to unbrick. Fortunately It revived.
If you mean that I should flash your twrp on boot partition, It also not fix touchscreen issue. Here is the log when your twrp actually flashed on the device.
Bikkoism said:
I flashed stock 14.6.A.1.236 customized US to unbrick. Fortunately It revived.
If you mean that I should flash your twrp on boot partition, It also not fix touchscreen issue. Here is the log when your twrp actually flashed on the device.
Click to expand...
Click to collapse
Oh that's not what i mean, but glad you unbricked it.
I will try to include a fix for touchscreen and upload it again, thanks.
New build released - 2021/09/24
Fixed touch issues.
New build released - 2021/10/03
Fixed SONY boot logo.
on my device C6833 is replaced LCD screen. try flash your recovery and system but touch not works. on stock rom 5.1.1 touch works. Its posible get working touch screen on device with replaced screen?
thanks
kluknawa235 said:
on my device C6833 is replaced LCD screen. try flash your recovery and system but touch not works. on stock rom 5.1.1 touch works. Its posible get working touch screen on device with replaced screen?
thanks
Click to expand...
Click to collapse
Actually all supported touch screen firmwares were already included in both of my recovery and ROM, and those are extracted from STOCK ROMs, so it shouldn't happen...
Do you have your C6833 stock rom backup file that i can take a look?
tarkzim said:
Actually all supported touch screen firmwares were already included in both of my recovery and ROM, and those are extracted from STOCK ROMs, so it shouldn't happen...
Do you have your C6833 stock rom backup file that i can take a look?
Click to expand...
Click to collapse
HERE is twrp backup stock rom. I use hot boot kernel with twrp 2.7.0.0. this recovery works good. on my device.
firmware version is 14.6.A.1.236_R2D android 5.1.1. all is included in mega folder.
Another twrp 3.0.0.0 and android 7.1.2 roms work for first time. but if screen is turn off and then i turn on touch not work. or if device is rebooted. I must completly turn off device and then turn on. thed touch works.
after replace device screen now works only stock rom
kluknawa235 said:
HERE is twrp backup stock rom. I use hot boot kernel with twrp 2.7.0.0. this recovery works good. on my device.
firmware version is 14.6.A.1.236_R2D android 5.1.1. all is included in mega folder.
Another twrp 3.0.0.0 and android 7.1.2 roms work for first time. but if screen is turn off and then i turn on touch not work. or if device is rebooted. I must completly turn off device and then turn on. thed touch works.
after replace device screen now works only stock rom
Click to expand...
Click to collapse
Can you try this TWRP image? (See attachment)
i try but touch not work. only OTG
kluknawa235 said:
i try but touch not work. only OTG
Click to expand...
Click to collapse
Try this one instead.
tarkzim said:
Try this one instead.
Click to expand...
Click to collapse
Same. As older recocery. Not works
kluknawa235 said:
Same. As older recocery. Not works
Click to expand...
Click to collapse
Well, I have no idea then...
Because I've already included the firmware update scripts from stock with stock binaries.
Can't help with your replaced touch panel for now, sorry.
Its ok. Thanks for your time
I just restored my XZU from a soft brick. Does the touch screen work with this version of TWRP?

[RECOVERY][TWRP][UNOFFICIAL] TWRP recovery 3.6.1_11-0

{
"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 recovery 3.6.1 for lancelot​(redmi 9 | lancelot/galahad)​
Code:
I am not responsible for your brick devices.
The recovery is fully working and has been tested.
If you encounter a problem, write here, maybe they will help you.
Before you accuse me of doing something wrong, take a look at how you use your smartphone.
You don't need to blame me for turning your device into a brick with my recovery, it's not my fault.
Attention!​The recovery is fully operational, it can make backups, install backups, it was tested only on custom Roms, but not on MIUI, but it should also work there.
Install:
To install, simply flash img to the recovery section and then reboot.
If you want to flash via fastboot, do the following:
fastboot --disable-verity --disable-verification flash vbmeta your_name_vbmeta.img
fastboot erase recovery
fastboot flash recovery your_name_recovery.img
fastboot reboot recovery
After that, you will find yourself in a new recovery.
Be careful when flashing!
Version Information
Status: Stable
Changelog:
Spoiler
24.03.2022
- inital build
- mtp not worked (For full operation, flash the ROM again through a new recovery!)
downloads:
Mega | GDrive
Information:
TWRP recovery for lancelot/galahad | redmi 9
Contributors
Furry__wolf
Credits:
TheGame455
Randomas3000
zubairk22oct
GADGETNiK
ExpressLuke
Source code
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp
https://github.com/Redmi-MT6768/omni_device_xiaomi_lancelot
Hi,
I'm currently on MIUI V12.5.4.0.RJCEUXM. I follow your instructions, flash vbmeta, erase, etc., but TWRP is still replaced by MIUI recovery after reboot to system. I can reboot to recovery directly from fastboot, but then /sdcard contains folders with weird names. I guess it is encrypted.
My goal is to create IMEI backup, but I'm afraid to run imei-backup.zip, when /sdcard is not proper. I have tried SHRP with the same results.
I have 2 questions:
- Is there alternative of imei-backup, that saves data to external SD or USB-OTG?
- If I use this TWRP to install LineageOS or CrDroid, would I get normal access to /sdcard?
popej said:
Hi,
I'm currently on MIUI V12.5.4.0.RJCEUXM. I follow your instructions, flash vbmeta, erase, etc., but TWRP is still replaced by MIUI recovery after reboot to system. I can reboot to recovery directly from fastboot, but then /sdcard contains folders with weird names. I guess it is encrypted.
My goal is to create IMEI backup, but I'm afraid to run imei-backup.zip, when /sdcard is not proper. I have tried SHRP with the same results.
I have 2 questions:
- Is there alternative of imei-backup, that saves data to external SD or USB-OTG?
- If I use this TWRP to install LineageOS or CrDroid, would I get normal access to /sdcard?
Click to expand...
Click to collapse
Use another recovery. So that it is not replaced by this archive
popej said:
Hi,
I'm currently on MIUI V12.5.4.0.RJCEUXM. I follow your instructions, flash vbmeta, erase, etc., but TWRP is still replaced by MIUI recovery after reboot to system. I can reboot to recovery directly from fastboot, but then /sdcard contains folders with weird names. I guess it is encrypted.
My goal is to create IMEI backup, but I'm afraid to run imei-backup.zip, when /sdcard is not proper. I have tried SHRP with the same results.
I have 2 questions:
- Is there alternative of imei-backup, that saves data to external SD or USB-OTG?
- If I use this TWRP to install LineageOS or CrDroid, would I get normal access to /sdcard?
Click to expand...
Click to collapse
You can backup the whole flash using the instructions provided in this thread.
The problem with restoring recovery is because you haven't rooted (via magisk) the device after flashing recovery. That's why the phone restores the recovery. IMEI (and other numbers like MACs) sits on a dedicated partition, so you can back the partition without having access to the data partition. Currently TWRP is unable to decrypt data when A12+ is used.
Thanks for your advice.
I'm on A11 MIUI. I didn't expect problems with encryption, but maybe it is MIUI problem.
I have made a backup to microSD with SHRP. SHRP can read partitions used for IMEI. For some reasons I couldn't make backup with TWRP.
I forgot about Magisk. With Magisk SHRP stay permanently. Probably tweak in SHRP or zip provided by OP can do the same, but I haven't tested.
My question is if I can format data and install custom A11 system without worrying about encryption?
When you format the data partition, the system will encrypt it again with the fist boot after flashing the ROM.
My Redmi 9 is on Pixel Experience Plus 12.1 with Pixel Experience recovery. Bad battery drain on idle so I want to try crDroid or PixelPlus.
Can I install this version of TWRP over Pixel Experience recovery? I want to install via Fastboot. I am already on Pixel Experience recovery so do I need to issue :
fastboot --disable-verity --disable-verification flash vbmeta your_name_vbmeta.img
or can I just go:
fastboot erase recovery
fastboot flash recovery your_name_recovery.img
fastboot reboot recovery
dataworx said:
My Redmi 9 is on Pixel Experience Plus 12.1 with Pixel Experience recovery. Bad battery drain on idle so I want to try crDroid or PixelPlus.
Can I install this version of TWRP over Pixel Experience recovery? I want to install via Fastboot. I am already on Pixel Experience recovery so do I need to issue :
fastboot --disable-verity --disable-verification flash vbmeta your_name_vbmeta.img
or can I just go:
fastboot erase recovery
fastboot flash recovery your_name_recovery.img
fastboot reboot recovery
Click to expand...
Click to collapse
Use a better full installation using vbmeta
Furry__wolf said:
Use a better full installation using vbmeta
Click to expand...
Click to collapse
Thanks for the reply - so I can just copy the vbmeta.img file from my original MIUI rom, and use that? Or does it need to be modified first?
dataworx said:
Thanks for the reply - so I can just copy the vbmeta.img file from my original MIUI rom, and use that? Or does it need to be modified first?
Click to expand...
Click to collapse
Use this vbmeta. It is patched for use on custom ROMs
Furry__wolf said:
Use this vbmeta. It is patched for use on custom ROMs
Click to expand...
Click to collapse
Thank you for your time and advice. I'll be able to tackle this tomorrow morning.
dataworx said:
Thank you for your time and advice. I'll be able to tackle this tomorrow morning.
Click to expand...
Click to collapse
No problem
I don't know if this is been asked before but after I flashed twrp recovery I noticed that on twrp internal memory doesn't show as it normal, can't access anythin, is there a way to fix that? (Lancelot)
hi iam install lineage os 18.1 twrp version is 3.5.2 this rom is very good and smooth and best battery...but install anu A12 custom rom whit twrp 3.5.2 its very slow and bad ram performance
what is problem? twrp is down virsion for A12?
Hi Everyone, twrp will be gone after some time by the miui Recovery. Though I flashed the vbmeta from Post #10.
What am I doing wrong?
morfikov said:
When you format the data partition, the system will encrypt it again with the fist boot after flashing the ROM.
Click to expand...
Click to collapse
Hello and thanks for your work here friend .
any way to make TWRP or SHRP decrypt internal storage ? I know about formatting data to make internal storage available , but a way to decrypt after booting ? On Android 10 I had no problem but on Android 11 Decryption doesn't work .
hi, when I try flashing this on miui 13 and reboot to recovery, it just reboots and goes into system ui. I'm using redmi 9 prime
Can anyone help me installating twrp for my poco m2, i tried but either i fot stucked into boot loop or my old miui recovery somehow replaced the file , can anyone plz.... Help via deskshare or any other way,
Vedant2 said:
Can anyone help me installating twrp for my poco m2, i tried but either i fot stucked into boot loop or my old miui recovery somehow replaced the file , can anyone plz.... Help via deskshare or any other way,
Click to expand...
Click to collapse
I had the same problem that I would fastboot flash the recovery, but still MIUI recovery would come up instead. You need to enter fastboot mode using Power+VolDown buttons and no cable connected, not via "adb reboot fastboot".
What tricked me is that (at least on MIUI 13) there are two fastboot modes.
When doing "abd reboot fastboot", the screen shows "FASTBOOTD" in BLUE letters. In this fastboot mode, "fastboot flash" finishes with "OKAY", but will actually do nothing.
When phone is off and you start it by pressing POWER + VOL_DOWN buttons, you get "FASTBOOT" (no D) in ORANGE letters. Only this fastboot will actually flash a new recovery!
It also prints "USB downloading..." on screen.

Categories

Resources