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/ ?
Related
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Wiki.
Recovery
The LineageOS 17.1 reovery is recommended
If you still want to use TWRP never install the TWRP app as system app. Otherwise your device won't boot
Current lineage 17.1 shamu nightlies are based on the N6F27M October 2017 update from google.
So you should be using the radio and bootloader img from that update.
Before you flash a bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one and don't need to flash it again.
They can be extracted from the factory image on google's site here.
Or you can use the ones linked below that I already extracted:
radio-shamu-d4.01-9625-05.45+fsg-9625-02.117.img
bootloader-shamu-moto-apq8084-72.04.img
IMPORTANT NOTE FOR VERIZON USERS: Google released a separate October 2017 security update (NGI77B) just for verizon users that has a different radio. So you'll want to flash it. I repeat, THIS RADIO IS JUST FOR VERIZON USERS.
radio-shamu-d4.01-9625-05.51+fsg-9625-02.118.img
You can use fastboot to flash the bootloader and radio.
More information and installation instructions can be found on the LineageOS wiki here.
Download Links
LineageOS: https://download.lineageos.org/shamu
Google apps: Opengapps Use an ARM (not ARM64) package for Android 10
HEADS UP: When you initially install LineageOS, be sure you flash the gapps package with your ROM. If you boot your ROM, then go back and try to flash gapps after, you're gonna have a bad time.
Changelog
Builddate: 2020.06.17
Changes:
[new] June security updates
[new] LineageOS clock
Builddate: 2020.05.29
Changes:
[new] May security updates
[fix] ULL audio fixes
[new] Add back serif fonts
[fix] Screen turning itself on when no lockscreen is set
[new] Etar calendar
Builddate: 2020.04.12
Changes:
[new] April security updates ROM & kernel
Builddate: 2020.04.08
Changes:
[new] Initial LineagOS 17.1 release
Known Issues:
[bug] Trusted voice is not working and probably never will
[bug] TWRP is not able do decrypt your data if you encrypted it with lineage-16.0
[bug] IMS is not working - if you need it you have to stay on lineage-15.1
XDA:DevDB Information
LineageOS, ROM for the Nexus 6
Contributors
Elektroschmock, elektroschmock, npjohnson
Source Code: http://github.com/lineagos
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2020-04-08
Last Updated 2020-04-08
Reserved
First build isn't out yet, but I don't want the LineageOS 16.0 thread to be spammed with 17.1 questions
Will waiting for the build you might want to read the Changlog for the first LineageOS 17.1 release:
Changelog 24
Will there be a possibility to root?
Should we wait for 17.1 to flash the radio and bootloader or can we do it now to get it out of the way?
What are the commands for flashing those two images?
Thanks @Elektroschmock and @npjohnson for keeping the Nexus 6 alive in 2020. :good:
Eazy said:
Will there be a possibility to root?
Click to expand...
Click to collapse
Yes you can use your root solution of choice.
Only thing coming with the ROM is adb root.
dlbarron said:
Should we wait for 17.1 to flash the radio and bootloader or can we do it now to get it out of the way?
What are the commands for flashing those two images?
Click to expand...
Click to collapse
Actually you should already have those radio and bootloader images if you had the latest stock image installed at one point.
Commands are:
fastboot flash bootlader [name_of_the_bootloader_image]
and
fastboot flash radio [name_of_the_radio_image]
Elektroschmock said:
Actually you should already have those radio and bootloader images if you had the latest stock image installed at one point.
Commands are:
fastboot flash bootlader [name_of_the_bootloader_image]
and
fastboot flash radio [name_of_the_radio_image]
Click to expand...
Click to collapse
Actually, I've been running Lineage and CM before that since I brought the phone home. So there's no way I had the latest stock image installed ever.
Thanks, I'm all set
Welp I did a stupid.
Flashed the new 17.1 recovery via fastboot. Then I tried to sideload via adb (based on the instructions) but Linux machine kept complaining about needs adb root. Tried with root permission nothing, Then came the stupid. Rebooted into recovery and tried to apply the update. Well that went how I expected, badly. Stuck on LOS loading screen.
Needed a fresh install anyway.
Stick to the instructions, guys.
BootloopedMillennials said:
Welp I did a stupid.
Flashed the new 17.1 recovery via fastboot. Then I tried to sideload via adb (based on the instructions) but Linux machine kept complaining about needs adb root. Tried with root permission nothing, Then came the stupid. Rebooted into recovery and tried to apply the update. Well that went how I expected, badly. Stuck on LOS loading screen.
Needed a fresh install anyway.
Stick to the instructions, guys.
Click to expand...
Click to collapse
Hello you can flash twrp with your pc after boot in twrp flash 17.1 + gapps micro + magisk 20.4 + wipe data + wipe dalvik + wipe cache reboot and it work perfectly ! Ps no intall twrp app in twrp recovery before reboot or you have bootloop Cordialy
BIG THANKS @Elektroschmock very Nice work
xrenoix said:
Hello you can flash twrp with your pc after boot in twrp flash 17.1 + gapps micro + magisk 20.4 + wipe data + wipe dalvik + wipe cache reboot and it work perfectly ! Ps no intall twrp app in twrp recovery before reboot or you have bootloop Cordialy
BIG THANKS @Elektroschmock very Nice work
Click to expand...
Click to collapse
My system got corrupted by the previous process. So I had to do a fresh install.
BootloopedMillennials said:
My system got corrupted by the previous process. So I had to do a fresh install.
Click to expand...
Click to collapse
Hello you have test wipe system with twrp ? Or test repair ? And use pico gapps for trébuchet launcher not work with mirco gapps but pixel launcher work ? !
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
mrk2815 said:
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
Click to expand...
Click to collapse
Best would be to use built in update. Unless you want to do a clean install, there's no reason to do it.
the update inside of lineage is blocking updating to lineage 17.1 , i tried tha earlier and i jsut tried it again. then it gives the link to the wiki page.so thats not going to work.i will have to do the old method of flashing through twrp or hoping that there is a command line approach to flashing lineage through lineage recovery.
mrk2815 said:
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
Click to expand...
Click to collapse
Sorry, I didn't ignore your question, but I first had to check.
It's kind of hard to imagine how a blind person would do it if you can see.
If you have Lineage recovery installed and are able to boot into recovery do the following steps:
Press the Volume Down button 1 time
Press the power button two times
You are now in the adb apply update mode.
There you can install all the zip files you want. I guess you script does the rebooting to system itself.
If you need further help just ask.
@Elektroschmock
Thanks for your hard work!
I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!
s_dino said:
@Elektroschmock
Thanks for your hard work!
I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!
Click to expand...
Click to collapse
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.
I don't know about which bootanimation you are talking about. Do you mean the bootloader?
Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.
Elektroschmock said:
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.
I don't know about which bootanimation you are talking about. Do you mean the bootloader?
Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.
Click to expand...
Click to collapse
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?
I mean I want use the google original boot animation to replace the lineage boot animation, but not success.
I noticed this: "disable audio rotation tracking"
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403
Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).
s_dino said:
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?
I mean I want use the google original boot animation to replace the lineage boot animation, but not success.
Click to expand...
Click to collapse
You still have those options:
Go to "Factory Reset"
There you can choose which partition you want to wipe.
- Wipe data/factory reset
- Wipe cache
- Wipe system
I guess you want the "wipe system" option
Sorry we don't support modifying our builds for obvius reasons. If you want to do that you are on your own. Sorry.
runekock said:
I noticed this: "disable audio rotation tracking"
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403
Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).
Click to expand...
Click to collapse
It's just a test. Non of us was able to trigger the loss of audio. Youl'll still have stereo but it won't switch channels if you turn your device.
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 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?
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
[RECOVERY] TWRP 3.6.0_11-0 - TeamWin Recovery Project
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. 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 official builds.
Device Config: https://github.com/bigbiff/android_device_google_crosshatch
Hello, this is a test build for crosshatch users.
If others thing don't work, please report the issue and let me know.
I am opening this thread to replace @Dees_Troy's thread with his blessing.
http://twrp.me
I tried to boot to this image on my bootloader-unlocked Pixel 3, but the operation failed.
With the device connected and the bootloader active, I ran the following command:
Code:
$ fastboot boot twrp-3.6.0_11-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 1.797s]
Booting FAILED (remote: 'Error verifying the received boot.img: Buffer Too Small')
fastboot: error: Command failed
I had just performed a factory reset (from
blueline-qq3a.200805.001). Flashing a blank vbmeta.img to disable verification did not resolve the error.
Thanks @bigbiff I've now got this installed on my Pixel 3 running Lineage 18 (A11). So nice to have TWRP back!! I've got one question about backing up. I'm seeing the following backup options:
Data (excluding storage)
Boot
Persist
Super (system system_ext vendor product)
I've not seen this "Persist" before. If I want to backup/restore the device, using TWRP, should all four of these options be selected?
Thanks again!
brainchild said:
I tried to boot to this image on my bootloader-unlocked Pixel 3, but the operation failed.
With the device connected and the bootloader active, I ran the following command:
Code:
$ fastboot boot twrp-3.6.0_11-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 1.797s]
Booting FAILED (remote: 'Error verifying the received boot.img: Buffer Too Small')
fastboot: error: Command failed
I had just performed a factory reset (from
blueline-qq3a.200805.001). Flashing a blank vbmeta.img to disable verification did not resolve the error.
Click to expand...
Click to collapse
See this post, and the subsequent posts.
TWRP 3.2.3-2 for Pixel 3
MTP does not work in TWRP on the Pixel 3 and will not work until we have time to update the TWRP MTP implementation. You may still use adb to push and pull files. Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot...
forum.xda-developers.com
OTG not working -_-
Thank you for the earlier reply. I am still learning about the relation between original firmware, Android version, recovery version, and partition layout. Whereas previously each had been largely independent of the others, recent changes have brought them into a very close dependence, which is often not clarified in the distribution of the various components.
I applied Android 11 firmware to the device, and was able to boot from the image.
I am now having problems installing custom Android 11 images, due to limited space on the system partition. In some cases, I can install the image but not Gapps, not even the pico size.
The general recommendation for this problem is to use the Advanced Wipe feature to resize the partition, but I have found no partition labeled System in the list.
The partitions listed under Advanced Wipe are only the following:
Dalvik / ART Cache
metadata
Data
Internal Storage
USB-OTG
I was able to install LineageOS entirely successfully using the project's own recovery, and then, once the main system was ready, install the TWRP 3.6 recovery image. While this procedure has appeared as a viable workaround, I look forward to any clarification about completing the installation entirely through TWRP. I also look forward to clarification about whether these observations indeed represent a current limitation in the TWRP images available for the device, and whether any other limitations are known.
Wow - TWRP for the Pixel 3 - finally!! What a great job, and thank you very, very much! Successfully completed my very first backup of my Blueline tonight; for the first time since buying this great phone over 18 months ago.
Issues I have found:
USB-OTG doesn't seem to work; I was hoping I could perform the backup to a USB flash drive.
Also, could not seem to get ADB from my computer to work.
Thank you so much @bigbiff for your hard work on this. It is very much appreciated! Well done!!
I do have one question, if I may: is it safe to flash this to recovery, or should we only use it via "fastboot boot twrp..."?
shaunoleary said:
Wow - TWRP for the Pixel 3 - finally!! What a great job, and thank you very, very much! Successfully completed my very first backup of my Blueline tonight; for the first time since buying this great phone over 18 months ago.
Issues I have found:
USB-OTG doesn't seem to work; I was hoping I could perform the backup to a USB flash drive.
Also, could not seem to get ADB from my computer to work.
Thank you so much @bigbiff for your hard work on this. It is very much appreciated! Well done!!
Click to expand...
Click to collapse
Thank you so much too, @bigbiff . Although USB-otg cannot be used, I can back up data on ArrowOS 12.0 without issues. Till now, I haven't tested restoration of my backup data yet.
Can this version of TWRP handle encrypted phones? (ones with lock screen passwords) I've been poking around the internet finding conflicting information.
Fnord12 said:
Can this version of TWRP handle encrypted phones? (ones with lock screen passwords) I've been poking around the internet finding conflicting information.
Click to expand...
Click to collapse
It can handle Android 11 encryption. I don't believe Android 12 encryption works yet.
dcarvil said:
It can handle Android 11 encryption. I don't believe Android 12 encryption works yet.
Click to expand...
Click to collapse
Fun, looks like i'll be waiting for a bit then as I was eyeballing one of the Android 12 ROMs to put on my Pixel 3 and i'll need encryption for NFC payment stuff.
Fnord12 said:
Fun, looks like i'll be waiting for a bit then as I was eyeballing one of the Android 12 ROMs to put on my Pixel 3 and i'll need encryption for NFC payment stuff.
Click to expand...
Click to collapse
You can still use it on Android 12 - you just need to remove the PIN first, then restore it afterwards.
dcarvil said:
You can still use it on Android 12 - you just need to remove the PIN first, then restore it afterwards.
Click to expand...
Click to collapse
You need to remove PIN on Android 12 before invoking backup process of your encrypted data on TWRP as @bigbiff said another thread. Probably, you can restore the backup data after removing PIN on Android 12. Then, you can set PIN on Android 12 again after the restoration.
Another observation... After a OTA update, LineageOS replaced the recovery with its own. From booting the TWRP image from a fastboot connection, the resulting session of TWRP shows option in the advanced menu for installing TWRP to the device. I'm not sure that I would be able to reinstall TWRP without this option, since attempts to flash through fastboot had failed previously. I'm confused about why this menu item no longer appears.
brainchild said:
Another observation... After a OTA update, LineageOS replaced the recovery with its own. From booting the TWRP image from a fastboot connection, the resulting session of TWRP shows option in the advanced menu for installing TWRP to the device. I'm not sure that I would be able to reinstall TWRP without this option, since attempts to flash through fastboot had failed previously. I'm confused about why this menu item no longer appears.
Click to expand...
Click to collapse
You can use Flash Current TWRP to have TWRP reinjected in the ramdisk, it's not showing up for you?
bigbiff said:
You can use Flash Current TWRP to have TWRP reinjected in the ramdisk, it's not showing up for you?
Click to expand...
Click to collapse
No. I believe what has happened is that the OTA update switched the active slot from A to B, with TWRP still residing on the now inactive slot A. Perhaps TWRP only looks in slot A, and if it finds itself installed, it hides this menu entry.
I am not sure what the general use pattern is, as I am still learning the newer paradigm of seamless updates, and A/B and dynamic partitions. Is TWRP compatible with OTA updates? What is the general usage pattern? The updated slot seems to have retained Magisk.
brainchild said:
No. I believe what has happened is that the OTA update switched the active slot from A to B, with TWRP still residing on the now inactive slot A. Perhaps TWRP only looks in slot A, and if it finds itself installed, it hides this menu entry.
I am not sure what the general use pattern is, as I am still learning the newer paradigm of seamless updates, and A/B and dynamic partitions. Is TWRP compatible with OTA updates? What is the general usage pattern? The updated slot seems to have retained Magisk.
Click to expand...
Click to collapse
Usually you have to reinstall twrp to the boot partition, which is typically not A/B
bigbiff said:
Usually you have to reinstall twrp to the boot partition, which is typically not A/B
Click to expand...
Click to collapse
The boot partition is shared by both slots, or each has a separate boot partition? It seems two recoveries are resident on the device.
brainchild said:
The boot partition is shared by both slots, or each has a separate boot partition? It seems two recoveries are resident on the device.
Click to expand...
Click to collapse
There are two boot partitions, boot_a and boot_b.
dcarvil said:
There are two boot partitions, boot_a and boot_b.
Click to expand...
Click to collapse
Right. It seems that when I originally loaded the firmware and installed TWRP, it installed to slot A. Later, LineageOS installed its OTA update on slot B, and activated it. Now the active recovery is the LOS recovery, in slot B. I can boot TWRP from fastboot, but the resulting session may be hiding the menu entry for installation on the the device because it detects itself already installed on slot A.
I suppose the questions are whether installation to multiple slots is supported by TWRP, and whether TWRP and LOS support integration for OTA updates.
More generally, the overall question is what is the overall recommended usage pattern for updating LOS when TWRP is also installed.