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.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Mi 11 lite 5G
bugs:
backup/restore is unreliable
adb sideload and fastbootd
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
Send me a beer: Crypto (Preferred) | PayPal
Contributors:
@VladV1V , @TheMalachite
Tree:
GitHub - TeamWin/android_device_xiaomi_renoir
Contribute to TeamWin/android_device_xiaomi_renoir development by creating an account on GitHub.
github.com
Kernel:
https://github.com/VladV1V/kernel_xiaomi_renoir
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomimi11lite5g.html
Sorry, but the installation did not work for me... :-( What i have done:
- i renamend the downloaded file to "twrp.img"
- i copied this file to the internal storage
- i startet the phone in fastboot mode
- then i startet adb
- i used the command "fastboot boot twrp.img"
Then i saw the following:
downloading 'boot.img'...
OKAY [ 2.826s]
booting...
OKAY [ 0.201s]
finished. total time: 3.027s
But the phone only switched off and nothing happend. What's wrong?
EDIT: i solved the problem! I forgot to put the file "twrp.img" into the adb folder. After doing this, the installation worked! Now i tried to make a backup, but it was not possible to select the external sd-card. How can i solve this problem?
Hi, thank's for your work for our device...
I read somewhere, that if we have TWRP installed, that we cannot flash update with fastboot...I want to know if it's true and if yes, how can we flash update..we have to find recovery update, or we can extract from fastboot archive and flash it??
thanks for your answer
Rainman67 said:
Now i tried to make a backup, but it was not possible to select the external sd-card. How can i solve this problem?
Click to expand...
Click to collapse
certainly not available yet...you have to backup in internal storage and then copy to SD...
Another question: how to go back to stock recovery?
Rainman67 said:
Another question: how to go back to stock recovery?
Click to expand...
Click to collapse
I'm on Xiaomi EU ROM. After last update via fastboot Miui Recovery 5.0 comes back.
Great hopefully this leads to development of some easy to flash roms, cant wait to get rid of this buggy MIUI trash.
I tried last version (16th July). Sadly no touchscreen.
Anyway many thanks!
same with #8 boot into twrp and no touchscreen
Peterpaulmarie said:
I tried last version (16th July). Sadly no touchscreen.
Anyway many thanks!
Click to expand...
Click to collapse
FuLuLu said:
same with #8 boot into twrp and no touchscreen
Click to expand...
Click to collapse
Boot TWRP from fastboot and touch will work.
Peterpaulmarie said:
I tried last version (16th July). Sadly no touchscreen.
Anyway many thanks!
Click to expand...
Click to collapse
FuLuLu said:
same with #8 boot into twrp and no touchscreen
Click to expand...
Click to collapse
How did you flash it?
Nebrassy said:
How did you flash it?
Click to expand...
Click to collapse
Fastboot boot twrp.img
Advanced - > flash current recovery
As well tried
Fastboot flash recovery twrp.img
Failed
Also
Advanced - > install recovery ramdisk
But magisk said ramdisk Yes
Peterpaulmarie said:
Fastboot boot twrp.img
Advanced - > flash current recovery
As well tried
Fastboot flash recovery twrp.img
Failed
Also
Advanced - > install recovery ramdisk
But magisk said ramdisk Yes
Click to expand...
Click to collapse
pm me on telegram if you can get logs and have adb access
dannejanne said:
Boot TWRP from fastboot and touch will work.
Click to expand...
Click to collapse
Nebrassy said:
How did you flash it?
Click to expand...
Click to collapse
i just boot to try if it can boot in twrp lol, no need to flash it so far,if needed it i will use the method u guys said(real flash in)
Well then both of you make sure you're actually using the build from afh and only use it for fastboot boot, when you want to flash use flash current twrp don't flash it with fastboot
Touch works when using fastboot boot and when flashed, it Was already tested on multiple devices
@Nebrassy Thanks for your contribution. Looking forward to the stable version with the known bugs fixed and touch works normally, without fastboot.
Thanks again.
doclucas said:
@Nebrassy Thanks for your contribution. Looking forward to the stable version with the known bugs fixed and touch works normally, without fastboot.
Thanks again.
Click to expand...
Click to collapse
Touch already works normally without fastboot
Nebrassy said:
Touch already works normally without fastboot
Click to expand...
Click to collapse
Nebrassy said:
Touch already works normally without fastboot
Click to expand...
Click to collapse
Yes, I can confirm. After start recovery wait 10-15sec touchscreen will work
With the test builds from telegram twrp was not able to recognize my SD card. Is this now fixed?
Is it possible to flash Xiaomi.eu weekly rom only by starting twrp from fastboot without installing it?
Related
http://forum.xda-developers.com/xpe.../recovery-twrp-3-0-0-touch-recovery-t3309938/
This is deprecated.
In this thread I'll share the .img files of the latest TWRP available for our device, so you can flash them with Rashr/PhilZ/Cyanogen recovery.
Disclaimer:
you are responsible for what you do. If your device stops working after you follow this guide, it's not my fault. However, as usual, if you do things in a correct way, you won't face any problems.
Requirements:
any ROM with any kernel
unlocked bootloader
Don't flash it if you have got a locked bootloader!
Features:
up-to-date source
flashable signed zip
f2fs support
Changelog:
TWRP 2.8.7.0_8
- other cleanups
- startup now is not slow! It just takes 3 - 4 seconds!
- Reboot bug is fixed - maybe
TWRP 2.8.7.0_7
- optimizations and cleanups
TWRP 2.8.7.0_6
- f2fs for /system is supported (this is for Temasek users)
TWRP 2.8.7.0_5
- f2fs support improved
- minor optimizations
- less overheating
TWRP 2.8.7.0_4
- attempt to fix issues with reboot option
TWRP 2.8.7.0_3
- signed flashable zip added
TWRP 2.8.7.0_2
- f2fs bugs fixed
- fixed overheating
How to install:
flash the zip through any recovery (even Cyanogen recovery!)
Download from Android File Host:
[url]https://www.androidfilehost.com/?fid=24052804347826443[/URL]
Stock FOTAKernel to remove any recovery (included this one): [url]http://forum.xda-developers.com/xperia-sp/general/stock-components-flashable-zips-t3184111[/URL]
Be sure to select the right variant of your device!
Thanks to:
@[NUT]
@antr34
@TechnoSparks
This work in miui v6
Thanks a lot for this quick update :thumbup:
Working fine on AICP's official nightlies with stock kernel.
The TITAN has landed. Hide your works from this critic! The official maintainer of the XSP Lollipop and M Hub.
Rashr was not working for me. I got it to work with this command on the terminal (with root):
Code:
su
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Notice that you'd have to save the .img file on the proper directory prior to using the command.
You can find more details of my struggle here: http://forum.xda-developers.com/xpe...rnel-tangerine-kernel-v1-t3073297/page28#1379
Hope this helps someone with the same issue.
pilger said:
Rashr was not working for me. I got it to work with this command on the terminal (with root):
Code:
su
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Notice that you'd have to save the .img file on the proper directory prior to using the command.
You can find more details of my struggle here: http://forum.xda-developers.com/xpe...rnel-tangerine-kernel-v1-t3073297/page28#1379
Hope this helps someone with the same issue.
Click to expand...
Click to collapse
I use it and i cant flash nothing
Guizão BR said:
I use it and i cant flash nothing
Click to expand...
Click to collapse
What is the output of the command? Does it throw you an error or anything?
@pilger i'm here, what to do next?
Here's a more detailed description of what I did in order for this to be flashed on my FOTAKernel:
Booted into default Cyanogen Recovery;
Wiped Dalvik and everything else I could in order to flash a new ROM;
Flashed the UNOFFICIAL CM from July 26th;
Flashed Pico Gapps (I guess it doesn't matter which Gapps you install, though);
Booted into system and set up everything (accounts, wi-fi, etc.);
DID NOT install Rashr;
Plugged my device to PC using USB;
Transfered the twrp-2.8.7.0_huashan.img to the root of the internal storage;
Unplugged the device from the computer;
Enabled Developer options on Settings (by tapping like crazy on the build number);
On the Developer options, I turned on Terminal Command, and root access to both ADB and apps;
Opened the terminal and entered "su" command to get root;
Allowed root and set it to remember its choice;
Entered up the command:
Code:
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Rebooted on recovery mode;
TWRP 2.8.7.0 was functioning as expected.
pilger said:
Here's a more detailed description of what I did in order for this to be flashed on my FOTAKernel:
Booted into default Cyanogen Recovery;
Wiped Dalvik and everything else I could in order to flash a new ROM;
Flashed the UNOFFICIAL CM from July 26th;
Flashed Pico Gapps (I guess it doesn't matter which Gapps you install, though);
Booted into system and set up everything (accounts, wi-fi, etc.);
DID NOT install Rashr;
Plugged my device to PC using USB;
Transfered the twrp-2.8.7.0_huashan.img to the root of the internal storage;
Unplugged the device from the computer;
Enabled Developer options on Settings (by tapping like crazy on the build number);
On the Developer options, I turned on Terminal Command, and root access to both ADB and apps;
Opened the terminal and entered "su" command to get root;
Allowed root and set it to remember its choice;
Entered up the command:
Code:
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Rebooted on recovery mode;
TWRP 2.8.7.0 was functioning as expected.
Click to expand...
Click to collapse
I've got TWRP now, one question though, if I flash the next CM nightly, it wouldn't be overwrote by the cyanogen recovery?
J73 said:
I've got TWRP now, one question though, if I flash the next CM nightly, it wouldn't be overwrote by the cyanogen recovery?
Click to expand...
Click to collapse
Glad you got it to work, mate! Flashing CM shouldn't overwrite the recovery. I guess that's the purpose of having the recovery on FOTA.
I'm not an expert though. But I've tested a couple of times myself and TWRP is there after every flash.
pilger said:
Glad you got it to work, mate! Flashing CM shouldn't overwrite the recovery. I guess that's the purpose of having the recovery on FOTA.
I'm not an expert though. But I've tested a couple of times myself and TWRP is there after every flash.
Click to expand...
Click to collapse
Thanks to you! All's well now, I'm so glad to have TWRP again thank you!
pilger said:
What is the output of the command? Does it throw you an error or anything?
Click to expand...
Click to collapse
Sorry i Forgot to edit the play, this have more time to flash
There's a bug with f2fs, it will be fixed tomorrow. Thanks to @Adrian DC for pointing this out.
Tomoms said:
There's a bug with f2fs, it will be fixed tomorrow. Thanks to @Adrian DC for pointing this out.
Click to expand...
Click to collapse
Can you tell me about that bug cause I'm using f2fs for cache,data and media that's formatted through your recovery
Sent from my Xperia SP using Tapatalk
kunal9007 said:
Can you tell me about that bug cause I'm using f2fs for cache,data and media that's formatted through your recovery
Sent from my Xperia SP using Tapatalk
Click to expand...
Click to collapse
Are you using Tangerine? This bug is not present in Tangerine's TWRP.
Tomoms said:
Are you using Tangerine? This bug is not present in Tangerine's TWRP.
Click to expand...
Click to collapse
I'm using tangerine but I've flashed this TWRP first, and this recovery has fotakernel so i geuss it can't be overwritten
Sent from my XT1033 using Tapatalk
kunal9007 said:
I'm using tangerine but I've flashed this TWRP first, and this recovery has fotakernel so i geuss it can't be overwritten
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Well, strange. f2fs volumes couldn't be mounted.
Tangerine probably fixed the issue, same as my CM-12.1 boot image fixed the TWRP image.
The goal of the fix is to have F2FS working without the boot image flashed over TWRP to make clean installs.
Adrian DC said:
Tangerine probably fixed the issue, same as my CM-12.1 boot image fixed the TWRP image.
The goal of the fix is to have F2FS working without the boot image flashed over TWRP to make clean installs.
Click to expand...
Click to collapse
just realized that I didn't had tangerine installed i was on first build of official cm and then before flashing radium i formated to f2fs
Sent from my XT1033 using Tapatalk
---------- Post added at 09:00 PM ---------- Previous post was at 08:58 PM ----------
and i flashed tangerine after atleast 1 day use of stock kernel
Sent from my XT1033 using Tapatalk
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.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Redmi note 10 Global/India (sunny/mojito)
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
Send me a beer: Crypto(Preferred) | PayPal
Tree: https://github.com/TeamWin/android_device_xiaomi_mojito
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomiredminote10.html
Unofficial android 12 builds:
https://www.pling.com/p/1836625/
mirror: https://store.kde.org/p/1836625/
OMG.. thanks sir for helping us about that recovery..
Can someone clarify what "repacking" means in this context? Does this mean the recovery cannot be updated through flashing? When a more stable recovery becomes available, will I have to install it using fastboot?
new build with repacking support is up, installation instructions are in the OP
Nebrassy said:
new build with repacking support is up, installation instructions are in the OP
Click to expand...
Click to collapse
Can we flash Xiaomi.eu ROM using new build?
bravonova said:
Can we flash Xiaomi.eu ROM using new build?
Click to expand...
Click to collapse
If they provide recovery zips, yes
Nebrassy said:
If they provide recovery zips, yes
Click to expand...
Click to collapse
Need to inform Xiaomi.eu developers @ingbrzy Pls have a note of this.
"Advanced" does not have a choice "Install Recovery Ramdisk".
I have recovery PixelExperience.
Twrp - I'm triggering like boot (TWRP-3.5.1-mojito-Nebrassy-2.img).
Recovery Ramdisk but doesn't exist.
StaryMuz said:
"Advanced" does not have a choice "Install Recovery Ramdisk".
I have recovery PixelExperience.
Twrp - I'm triggering like boot (TWRP-3.5.1-mojito-Nebrassy-2.img).
Recovery Ramdisk but doesn't exist.
Click to expand...
Click to collapse
It does, but you can also use
Install > install image > select the image and flash it to recovery ramdisk
Thank you, i expected the button. My mistake.
no mirror available at the time writing this
Does backup and restore work? and what are the select for backup?
.
it will be great, give flashing rom instruction using this TWRP. thanks.
Thanks for your work on this.
If I want to do a standard TWRP backup, would I select data, boot and super? There's no partition called system.
Is installing TWRP to ramdisk due to this model having A and B partitions? Why do some phones have this setup and others don't?
For all those who fail to boot up a rom through TWRP....
Plz re-install TWRP into the ramdisk immediately after rom flash... it'll save your day...
I join the question: Does backup and restore work?
Can I only flash TWRP without flashing any other ROM?
I don't want to root or use a cutom ROM at this moment.
Just want to backup and restore with TWRP.
No one?
nierewa said:
I join the question: Does backup and restore work?
Can I only flash TWRP without flashing any other ROM?
I don't want to root or use a cutom ROM at this moment.
Just want to backup and restore with TWRP
Click to expand...
Click to collapse
It does work. But you need to use either sdcard to store the backup, or other storage like PC or external drive. Because switching roms will cause data format.
Ok. Thanks a lot.
I have a sdcard in the phone so I use it for storing the backup.
So I do this:
Installation:
1. fastboot boot twrp.img
2. copy that same twrp image to the device
3. go to Advanced > Install Recovery Ramdisk
4. select the image you copied
and then I can boot the Redmi without the need to flash a custom ROM?
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.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Oneplus 7/Pro/5G that supports Android 11
can be flashed to boot with working decryption on android 11 roms
bugs:
backup/restore is unreliable
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
Send me a beer: Crypto(Preferred) | PayPal
Trees:
https://github.com/TeamWin/android_device_oneplus_guacamole
https://github.com/TeamWin/android_device_oneplus_sm8150-common
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/oneplus/oneplus7pro.html
Unofficial 12 builds: https://www.pling.com/p/1835156/
Will there be an installer zip or just an .img?
bdwilk said:
Will there be an installer zip or just an .img?
Click to expand...
Click to collapse
Read the Installation instructions, there's a new experimental feature replacing the need for zips.
Nice, at least no more torturing my poor 7Pro with test images, haha.
Thanks.
And yes, the new feature is neat and works here pretty well.
Good job, @Nebrassy !
It says a11 ROMs can be decrypted is oos 11 also included in that ?
jaggillararla said:
It says a11 ROMs can be decrypted is oos 11 also included in that ?
Click to expand...
Click to collapse
Why don't you try it and give us feedback
@Nebrassy thank you . I am sure the entire Oneplus guys here appreciate it.
wartomato said:
Nice, at least no more torturing my poor 7Pro with test images, haha.
Thanks.
And yes, the new feature is neat and works here pretty well.
Good job, @Nebrassy !
Click to expand...
Click to collapse
Been using for awhile now it's awesome this will make things easier great job
jaggillararla said:
It says a11 ROMs can be decrypted is oos 11 also included in that ?
Click to expand...
Click to collapse
I'm using HavocOS 4.5 based on OOS 11 and managed to decrypt data partition just fine.
I can confirm it's working on OP7 with OB4 / Android 11.
Many thanks for the great job!
Uploaded new build with f2fs support
Toutatis_ said:
I'm using HavocOS 4.5 based on OOS 11 and managed to decrypt data partition just fine.
Click to expand...
Click to collapse
Did you need to wipe your phone? Recently installed Android 11 and I can't do nandroid backup and don't want to mess it again.
1 said:
Did you need to wipe your phone? Recently installed Android 11 and I can't do nandroid backup and don't want to mess it again.
Click to expand...
Click to collapse
No, I rebooted to bootloader mode, ran sudo fastboot boot filename.img and TWRP splash screen appeared, asking for password. I entered my password and that's it, data partition was decrypted. I finally rebooted to system.
@Nebrassy
Thanks for the great work btw. Appreciated.
This work with stock oos11 encrypted?
Can somebody elaborate this?
1. fastboot boot twrp.img (Which twrp is this? The one shared here?)
2. go to Advanced > Flash Current TWRP (What does current TWRP mean? Official TWRP? and where is that advanced? Advanced in new TWRP?)
1 said:
Can somebody elaborate this?
1. fastboot boot twrp.img (Which twrp is this? The one shared here?)
2. go to Advanced > Flash Current TWRP (What does current TWRP mean? Official TWRP? and where is that advanced? Advanced in new TWRP?)
Click to expand...
Click to collapse
Yes, run fastboot boot TWRP-3.5.1-guacamole-Nebrassy-2.img (this is the filename for the current latest version)
See my screenshot
Toutatis_ said:
Yes, run fastboot boot TWRP-3.5.1-guacamole-Nebrassy-2.img (this is the filename for the current latest version)
See my screenshot
Click to expand...
Click to collapse
Thanks a lot.
Can this be flashed within twrp if we're on the latest version from https://dl.twrp.me/guacamole/ ?
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.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Mi 11i/Mi 11X Pro/Redmi K40 Pro
USB OTG will not work
Decrypting Android 12 will only work if you remove pin/password
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
thanks to : @erfanoabdi @Cozzmy13
Send me a beer: Crypto (Preferred) | PayPal
Trees:
https://github.com/TeamWin/android_device_xiaomi_haydn
https://github.com/TeamWin/android_device_xiaomi_sm8350-common
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomiredmik40pro.html
Thanks for sharing
Good job,but semms the Touchscreen doesn't work.
don't touch fish said:
Good job,but semms the Touchscreen doesn't work.
Click to expand...
Click to collapse
It does, wait a few seconds after boot
Nebrassy said:
It does, wait a few seconds after boot
Click to expand...
Click to collapse
I waited about five minute,and nothing happend.When I touch the screen,nothing happend or Sometimes twrp responds to the wrong touch position(for example:I touch the Cancel,It opend Language sittings).I can only use adb shell to use this recovery.
thanks，will it support flash miui rom.zip and support android 12 。。
Thank you ………………Testing now
Touch doesnt work for me either
im on xiaomi eu rom
Exodt said:
Touch doesnt work for me either
im on xiaomi eu rom
Click to expand...
Click to collapse
Pull log and send it
adb pull /tmp/recovery.log
Before flashing i removed my fingerprint and device lock Flashed successfully after 2nd step i installed twrp image via twrp recovery installed in phone in Advance - recovery ram disk -Twrp image - flash and after that i created a boot image and dtbo backup also flashed magisk zip btw my device was rooted previously with boot image method, in xiaomi eu 12.5.7.0. Touch takes time then it works … First internal storage was not showing so i go to mount and mount system and then it shows.
Maxx9 said:
Before flashing i removed my fingerprint and device lock Flashed successfully after 2nd step i installed twrp image via twrp recovery installed in phone in Advance - recovery ram disk -Twrp image - flash and after that i created a boot image and dtbo backup also flashed magisk zip btw my device was rooted previously with boot image method, in xiaomi eu 12.5.7.0. Touch takes time then it works … First internal storage was not showing so i go to mount and mount system and then it shows.
Click to expand...
Click to collapse
Can you check if fastboot booting the image has working touch?
Nebrassy said:
Can you check if fastboot booting the image has working touch?
Click to expand...
Click to collapse
Thats how i installed
Installation:
Removed Screen lock And Fingerprint
1.fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3.Go to advance system ram disk select twrp image and flash(if internal storage not showing then go to mount and mount storage)
4.after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Yes…it works for me …… when i run first command it booted but my storage wasn’t showing so i reboot to recovery and device reboted to stock recovery then i again put my device in fastboot and performed first command and it booted to twrp and touch takes 20 seconds for me to work ..
Nebrassy said:
Pull log and send it
adb pull /tmp/recovery.log
Click to expand...
Click to collapse
"adb: error: failed to stat remote object '/tmp/recovery.log': No such file or directory"
Tried it in booted twrp as well but adb doesn't work there.
Maxx9 said:
Thats how i installed
Installation:
Removed Screen lock And Fingerprint
1.fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3.Go to advance system ram disk select twrp image and flash(if internal storage not showing then go to mount and mount storage)
4.after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Yes…it works for me …… when i run first command it booted but my storage wasn’t showing so i reboot to recovery and device reboted to stock recovery then i again put my device in fastboot and performed first command and it booted to twrp and touch takes 20 seconds for me to work ..
Click to expand...
Click to collapse
It worked.
Flash Current TWRP did the trick.
I had to do a reboot.
Hold the volume up and power to go back to TWRP.
After that I could see the internal storage.
And flash Magisk.
*Do not unplug the cable. Unplugging was causing the touch to stop work on my MI11i EU 12.5.7
Thanks Maxx9!
I didn't unplugged the USB and removed the fingerprint + key as well.
But still didn't worked.
on xiaomi eu 12.5.8
Touche said:
It worked.
Flash Current TWRP did the trick.
I had to do a reboot.
Hold the volume up and power to go back to TWRP.
After that I could see the internal storage.
And flash Magisk.
*Do not unplug the cable. Unplugging was causing the touch to stop work on my MI11i EU 12.5.7
Thanks Maxx9!
Click to expand...
Click to collapse
Your welcome
Doesn't work on Indian ROM 12.5.5.0
Official Pixel Experience A12 Custom Rom For Xiaomi Redmi K40 Pro / Pro+ / Mi 11X Pro / Mi 11i is Available On Pixel Experience Official Website.
on my device twrp still freeze touch screen
same problem
Team Win Recovery Project or TWRP for short. Its a fully touch driven user interface, completely theme-able & you can change just about every aspect of the look and feel.
Now ported to the Galaxy Tab A7 Lite.
Download - You'll always find the latest release in here: https://github.com/DevZillion/android_device_samsung_gta7litewifixx/releasesKnown Issues / Report Issues - https://github.com/DevZillion/android_kernel_samsung_gta7litewifixx/issuesTelegram support group - https://t.me/gta7litegroup
How to install
[Boot Into Download mode by inserting an usb cable while holding both volume buttons]
Flash the latest .tar release from releases.
Hold the recovery combination (Volume Up + Power) while the .tar is flashing via the odin tool.
When booted up into TWRP go Flash and flash this zip, then go to Wipe > Format Data, all your data will be lost.
You can now boot into your system and do whatever you want.
Click to expand...
Click to collapse
Flashing Disabled vbmeta (To boot a modified system)
Spoiler: View
Extract the vbmeta.img.lz4 from the AP slot in your firmware.
Remove it's lz4 compression [for Windows use lz4]:
Code:
sudo apt-get install lz4 -y
lz4 vbmeta.img.lz4
Click to expand...
Click to collapse
Reboot into fastboot from TWRP flash vbmeta using this command line:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Sources
TWRP Source - https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-11
Device Tree - https://github.com/DevZillion/android_device_samsung_gta7litewifixx/
Kernel Source - https://github.com/DevZillion/android_kernel_samsung_gta7litewifixx
Click to expand...
Click to collapse
Special thanks to:
TeamWin for the Recovery Project.
Zillion for doing the device tree & kernel.
Click to expand...
Click to collapse
Actual TWRP status: Bugfixing; Try at your own risk and only if you know what you're doing.
Genial!!
Zillion said:
Team Win Recovery Project or TWRP for short. Its a fully touch driven user interface, completely theme-able & you can change just about every aspect of the look and feel.
Now ported to the Galaxy Tab A7 Lite WiFi.
Download - You'll always find the latest release in here: https://github.com/DevZillion/android_device_samsung_gta7litewifixx/releasesKnown Issues / Report Issues - https://github.com/DevZillion/android_kernel_samsung_gta7litewifixx/issuesTelegram support group - https://t.me/gta7litegroup
How to install
Flashing Disabled vbmeta (To boot a modified system)
Sources
Special thanks to:
Actual TWRP status: Bugfixing; Try at your own risk and only if you know what you're doing.
Click to expand...
Click to collapse
it boots, touch does not work but its usable with a mouse and gives an error "unable to mount /data"
dda7lite said:
it boots, touch does not work but its usable with a mouse and gives an error "unable to mount /data"
Click to expand...
Click to collapse
Please, read the How To Install section.
Zillion said:
Please, read the How To Install section.
Click to expand...
Click to collapse
I did but the file that needs to be flashed is unavailable in that link
dda7lite said:
I did but the file that needs to be flashed is unavailable in that link
Click to expand...
Click to collapse
Thanks for reporting the issue, link fixed.
Zillion said:
Thanks for reporting the issue, link fixed.
Click to expand...
Click to collapse
i have other problem error "E:unable to open block device /dev/block/sda: No medium found"
What is vbmeta?
I want to install Elixir Project. Is it necessary to do something from the vbmeta? Or just flashing the rom is enough?
chocovo said:
What is vbmeta?
I want to install Elixir Project. Is it necessary to do something from the vbmeta? Or just flashing the rom is enough?
Click to expand...
Click to collapse
Flash vbmeta is necessary to boot a new system but it's easy to flash too.
dda7lite said:
Flash vbmeta is necessary to boot a new system but it's easy to flash too.
Click to expand...
Click to collapse
I understand that the vbmeta is pulled from original samsung firmware, lz4 format stripped and flashed by AP. Then we implement the command by TWRP and the desired rom is installed.
Is that so?
Does the vbmeta step have to be done every time I put a new rom or only once?
Sorry for my english
chocovo said:
I understand that the vbmeta is pulled from original samsung firmware, lz4 format stripped and flashed by AP. Then we implement the command by TWRP and the desired rom is installed.
Is that so?
Does the vbmeta step have to be done every time I put a new rom or only once?
Sorry for my english
Click to expand...
Click to collapse
I only did once and I didn't use the stock vbmeta I just searched "vbmeta disabled Samsung" it should show up with vbmeta disabled android 11 but works the same on 13 and I didn't use TWRP only fastboot so i don't know how to flash it there.
Btw your English is good don't worry.
After installing TWRP I can't install the fbe. TWRP doesn't recognize my device's internal memory either.
chocovo said:
After installing TWRP I can't install the fbe. TWRP doesn't recognize my device's internal memory either.
Click to expand...
Click to collapse
Yeah
chocovo said:
After installing TWRP I can't install the fbe. TWRP doesn't recognize my device's internal memory either.
Click to expand...
Click to collapse
Because you need to flash the fbe_disabler using some usb otg, external sd card or by pushin the zip to /tmp, flash it and then format /data.
Zillion said:
Because you need to flash the fbe_disabler using some usb otg, external sd card or by pushin the zip to /tmp, flash it and then format /data.
Click to expand...
Click to collapse
Bootloop after
Zillion said:
Because you need to flash the fbe_disabler using some usb otg, external sd card or by pushin the zip to /tmp, flash it and then format /data.
Click to expand...
Click to collapse
My device is a T220.
The touch does not work in TWRP and I use a mouse. I use Micro SD to install the FBE. But when trying to install it gives me an error in the data folder. Although apparently it seems to be installed.
I format data as you indicate and restart in fastboot in TWRP to put the vbmeta by ADB and install a GSI. But it generates bootloop.
I don't know if I'm missing some step.
chocovo said:
My device is a T220.
The touch does not work in TWRP and I use a mouse. I use Micro SD to install the FBE. But when trying to install it gives me an error in the data folder. Although apparently it seems to be installed.
I format data as you indicate and restart in fastboot in TWRP to put the vbmeta by ADB and install a GSI. But it generates bootloop.
I don't know if I'm missing some step.
Click to expand...
Click to collapse
If you really want to flash a gsi and can't get it to work use a fastboot enabled recovery that's what I did
dda7lite said:
Bootloop after
Click to expand...
Click to collapse
Disable vbmeta, it's the only thing I can see you missed.
um i flashed the recovery to my sm-t220 but i do not have a usb otg i am buying it today in the meanwhile i tried to boot back to one ui 5.1 the one i have but it only shows twrpto reboot i used power + volume down but it shows twrp and power + volume up dosnt do anything
Gian-D said:
um i flashed the recovery to my sm-t220 but i do not have a usb otg i am buying it today in the meanwhile i tried to boot back to one ui 5.1 the one i have but it only shows twrpto reboot i used power + volume down but it shows twrp and power + volume up dosnt do anything
Click to expand...
Click to collapse
Force restart and keep the usb cable connected to the PC and tablet then as soon as screen blinks hold volume +and-