[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
Old Info
Download here:
Test1: https://build.twrp.me/test/crosshatch/twrp-3.6.0-0-test1-crosshatch.img
- fix backup and restore
- fix decryption thanks to @Captain_Throwback and his twrp-common tree which fixes the order of proprietary services starting: https://github.com/TeamWin/android_device_qcom_twrp-common
- supports 12 decryption with no pin set
- fully supports 11 decryption with keymaster
Thanks for the build. Tested on Android 11, latest Scorpion rom. Touch does not appear to be working.
ghostcrew said:
Thanks for the build. Tested on Android 11, latest Scorpion rom. Touch does not appear to be working.
Click to expand...
Click to collapse
Scorpion is not using a stock DTBO. You will have to use the fastbooted twrp adb shell session to install this flashable zip:
https://build.twrp.me/test/crosshatch/twrp-installer-3.6.0_11-0-crosshatch.zip
Push it to /sdcard with adb, and do twrp install twrp-installer-3.6.0_11-0-crosshatch.zip inside the adb shell
Then use adb to reboot to TWRP that is now installed as recovery in boot.
Thanks for TWRP for Pixel 3XL!
Thanks bro!. Dont use my pixel for much anymore but great to see someone still developing for it
Thank you for TWRP! Lifesaver. Tried this on my Pixel 3XL running on Evolution X, A11 .... Works great!
bigbiff said:
Scorpion is not using a stock DTBO. You will have to use the fastbooted twrp adb shell session to install this flashable zip:
https://build.twrp.me/test/crosshatch/twrp-installer-3.6.0_11-0-crosshatch.zip
Push it to /sdcard with adb, and do twrp install twrp-installer-3.6.0_11-0-crosshatch.zip inside the adb shell
Then use adb to reboot to TWRP that is now installed as recovery in boot.
Click to expand...
Click to collapse
I followed your instructions and now I have twrp on my phone and touch is working. Thank you for the instructions and thank you for TWRP on Pixel 3xl!
bigbiff said:
[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.
Download here:
Test1: https://build.twrp.me/test/crosshatch/twrp-3.6.0-0-test1-crosshatch.img
- fix backup and restore
- fix decryption thanks to @Captain_Throwback and his twrp-common tree which fixes the order of proprietary services starting: https://github.com/TeamWin/android_device_qcom_twrp-common
- supports 12 decryption with no pin set
- fully supports 11 decryption with keymaster
http://twrp.me
Click to expand...
Click to collapse
Hey, Biff. Thanks, of course. Just wondering if you are releasing it for Pixel 3... I am on P3XL, but my wife is on P3.
sliding_billy said:
Hey, Biff. Thanks, of course. Just wondering if you are releasing it for Pixel 3... I am on P3XL, but my wife is on P3.
Click to expand...
Click to collapse
We are supposed to have someone lined up. Has anyone posted in the blueline forums?
Was able to install TWRP on my Crosshatch however whenever I tried to use the ADB Sideload function to install a rom I would get this error:
serving: 'C:\Users\Zero\Downloads\Pixel 3 XL Project\EvolutionX\evolution_crosshatch-ota-sq1d.211205.016.a1-12251000-unofficial-unsigned.zip' (~0%) adb: failed to read command: No error
Logs attached. *XDA wont let me upload the files see below.
Logs
delete...
Zero_Shadow said:
Was able to install TWRP on my Crosshatch however whenever I tried to use the ADB Sideload function to install a rom I would get this error:
serving: 'C:\Users\Zero\Downloads\Pixel 3 XL Project\EvolutionX\evolution_crosshatch-ota-sq1d.211205.016.a1-12251000-unofficial-unsigned.zip' (~0%) adb: failed to read command: No error
Logs attached. *XDA wont let me upload the files see below.
Logs
Click to expand...
Click to collapse
I was able to sideload lineage-18.1. Does adb devices show sideload?
bigbiff said:
We are supposed to have someone lined up. Has anyone posted in the blueline forums?
Click to expand...
Click to collapse
Unfortunately, no.
bigbiff said:
I was able to sideload lineage-18.1. Does adb devices show sideload?
Click to expand...
Click to collapse
Yes I am able to use adb devices in my command prompt and see the device while adb sideload is active in twrp. Heres what happens.
I open up TWRP > Wipe (Factory Reset) then Advanced > ADB Sideload > Swipe to Start Sideload
I see Starting ADB Sideload feature
I go back to my computer and type adb devices (to confirm it see it) > adb sideload filename.zip (being the file of course).
Soon I hit enter I get a crash within TWRP and it goes back to the Main startup page for twrp.
When I go back to ADB Sideload I see this message:
E: fialed to mount /tmp/com.android.apex.cts.shim.
apex to loop device /dev/block/loop0. Reason: Device
or resource busy
E: Unable to create loop devices to mount apex files
E: Unable to load apex images frin /system_root/
system/apex
I did install TWRP to recovery using Advanced > Flash Current TWRP
If I use one of the recoveries for PE or Lineage I am able to flash using adb sideload.
*Edit 1: Now I did download the version from Telegram so let me try the one link above.
*Edit 2: Just tried with the one linked above same thing.
*Edit 3: Logs for review. https://drive.google.com/drive/folders/1PqKN_QzdGnFJTu4Ov-2iUzyzv85ZaD9D?usp=sharing
I could be doing something wrong so any help would be appreciated.
Zero_Shadow said:
Yes I am able to use adb devices in my command prompt and see the device while adb sideload is active in twrp. Heres what happens.
I open up TWRP > Wipe (Factory Reset) then Advanced > ADB Sideload > Swipe to Start Sideload
I see Starting ADB Sideload feature
I go back to my computer and type adb devices (to confirm it see it) > adb sideload filename.zip (being the file of course).
Soon I hit enter I get a crash within TWRP and it goes back to the Main startup page for twrp.
When I go back to ADB Sideload I see this message:
E: fialed to mount /tmp/com.android.apex.cts.shim.
apex to loop device /dev/block/loop0. Reason: Device
or resource busy
E: Unable to create loop devices to mount apex files
E: Unable to load apex images frin /system_root/
system/apex
I did install TWRP to recovery using Advanced > Flash Current TWRP
If I use one of the recoveries for PE or Lineage I am able to flash using adb sideload.
*Edit 1: Now I did download the version from Telegram so let me try the one link above.
*Edit 2: Just tried with the one linked above same thing.
*Edit 3: Logs for review. https://drive.google.com/drive/folders/1PqKN_QzdGnFJTu4Ov-2iUzyzv85ZaD9D?usp=sharing
I could be doing something wrong so any help would be appreciated.
Click to expand...
Click to collapse
What zip are you installing?
Tried the A12 builds for PE, EvoX and PixelDust same issue across the board.
Thanks a lot for this build!!! My Pixel3 XL keeps getting corrupt due to handing/wifi dropping, now finally I can have a Nandroid backup!
Need help installing pls. Tried many times with stock to no avail. Now trying with evolution Rom to no avail. My cmd is fastboot flash boot TWRP.img, which works with stock, but I'm unable to install or sideload and have to reflash the stock kernel to reboot the Rom. Same with evolution besides with stock I can attempt to reboot (after flashing twrp) which reboots to twrp, but won't reboot at all with evolution (until reflashing the kernel) I've been at this for a few hours now, any advice much appreciated.
brandonabandon said:
Need help installing pls. Tried many times with stock to no avail. Now trying with evolution Rom to no avail. My cmd is fastboot flash boot TWRP.img, which works with stock, but I'm unable to install or sideload and have to reflash the stock kernel to reboot the Rom. Same with evolution besides with stock I can attempt to reboot (after flashing twrp) which reboots to twrp, but won't reboot at all with evolution (until reflashing the kernel) I've been at this for a few hours now, any advice much appreciated.
Click to expand...
Click to collapse
You don't flash boot.img with this device. You temporarily boot it with fastboot boot img, then push it to sdcard and use twrp's install recovery ramdisk function.
nithin suresh said:
Thank you for TWRP! Lifesaver. Tried this on my Pixel 3XL running on Evolution X, A11 .... Works great!
Click to expand...
Click to collapse
Is there any possible way you could put instructions or how to install list for me I would greatly appreciate it. I have the pixel 3xl and have been having the hardest time getting twrp install as well as other items.
Related
This is UNOFFICIAL TWRP for the Pixel C. That said, the TeamWin team greatly helped me in getting this working. But at the same time, neither TeamWin nor me take any responsibility whatsoever for any undesired outcome resulting from any kind of use of this project and project files! If you don't exactly know what you're doing then just walk away and do something good. Don't touch any options of which you don't exactly know what they're for!
What works:
* So far, everything; encryption support should work, but some feedback on this would be welcome
Problems:
* The GUI will be sometimes slow, sometimes super slow. This is probably due to the high screen resolution of the Pixel C.
How to install:
- Unlock bootloader
- In the bootloader, run "fastboot flash recovery <.img file>"
- Reboot into Pixel C bootloader
- Boot into recovery (or later on/from Android through "adb reboot recovery")
If the recovery doesn't stick after booting into Android:
- Do the install procedure as above
- Do NOT reboot into Android
- Press Vol-Down + Power until you see the bootloader menu
- Select "Boot into Android Recovery"
- When in TWRP, mount system
- Using TWRP's File Manager, or using adb, delete the file "/system/bin/install-recovery.sh"
- Reboot
After doing this, OTAs won't work any longer, but they wouldn't work anyway after installing TWRP. Just so you know
DOWNLOAD
twrp-3.0.0-0-dragon-ryu-02-11-2016-1.img
SHA1 hash: 3e97aae6cc18975683eda2bd3732faaecec14166
Changelog
:: 01-19-2016-1
- Removed screen timeout by default, since the GUI is very slow and the screen unlock slider is very hard to use
- Added an option to fix the Fastboot Full Cap flag directly from TWRP; you find the option in "Advanced". If the Pixel C should ever not let you flash in fastboot, boot into TWRP, select Advanced -> Fix Fastboot, swipe to confirm, and you're set.
:: 02-11-2016-1
- Rebased on twrp/android-6.0 branch (i.e. upgraded to TWRP 3.0.0-0)
The recovery is based on the Pixel C stock kernel.
Awesome! I can survive without root for the time being but being able to enable multiwindow would be amazing!
Thanks!
Edit: I am getting a FAILED (remote: unsupported command) error and cant flash this. Anyone know a work around?
Worked fine for me with "fastboot flash recovery [image name]" did you unlock your bootloader? Also root works just fine, you just have to boot from your PC.
Sent from my Pixel C using Tapatalk
brando56894 said:
Worked fine for me with "fastboot flash recovery [image name]" did you unlock your bootloader? Also root works just fine, you just have to boot from your PC.
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
I did unlock my bootloader but can't get anywhere. Tried updating my sdk, drivers everything. I guess I will have to keep playing with it.
Edit: I relocked my bootloader, and then unlocked it again and now it is working. If anyone else runs into this give it a try.
it successfully installed on my pixel c. is reachable as the Android Recovery option. and boots to bootloader to allow boot of boot.img
this is a good thing. thanks to all involved.
it's been 1 month since release and good way to celebrate.
Good work. Thanks you
hooray thanks! just to clarify: I need encryption disabled to use twrp or just to flash SuperSU?
I'm currently using phhusson's noverity boot-img to boot and with a modified vendor img root is working fine while encryption is enabled ... just having to boot via fastboot every time is a bit awkward. And since I don't know what happens if the device got stuck and reboots itselfe without the modfied boot it would be awesome to have at least a nandroid backup
doumer said:
hooray thanks! just to clarify: I need encryption disabled to use twrp or just to flash SuperSU?
I'm currently using phhusson's noverity boot-img to boot and with a modified vendor img root is working fine while encryption is enabled ... just having to boot via fastboot every time is a bit awkward. And since I don't know what happens if the device got stuck and reboots itselfe without the modfied boot it would be awesome to have at least a nandroid backup
Click to expand...
Click to collapse
Hey... You can use TWRP even with encryption enabled, you just can't write anything to /data.
However for the next build I'm going to enable TWRP's decryption option and see if it works with the Pixel C. If it does I'll post a new build this evening (European Time).
I tried the systemless SuperSU on a decrypted /data partition but it wouldn't work (bootloop), clearly there's a lot of ground to cover here, but like I said maybe the decryption functionality will help us here.
EDIT: I'm also working on a boot.img with disabled forced encryption. Looks like we're going to get proper root very soon.
cheep5k8 said:
This is UNOFFICIAL TWRP for the Pixel C. That said, the TeamWin team greatly helped me in getting this working. But at the same time, neither TeamWin nor me take any responsibility whatsoever for any undesired outcome resulting from any kind of use of this project and project files! If you don't exactly know what you're doing then just walk away and do something good. Don't touch any options of which you don't exactly know what they're for!
What works:
* Well, basically everything IN TWRP works, it's just that without a kernel that disables forced encryption this is not of very much use. I tried flashing SuperSU, but it wouldn't work properly.
Problems:
* The GUI will be sometimes slow, sometimes super slow. This is apparently still a problem with how TWRP uses the graphics mode that is used on the Pixel C. Best is if you immediately disable the screen lock once you boot into TWRP because the unlock slider is abysmally sluggish.
How to install:
- Unlock bootloader
- In the bootloader, run "fastboot flash recovery <.img file>"
- Reboot into Pixel C coreboot bootloader
- Boot into recovery (or later on/from Android through "adb reboot recovery")
DOWNLOAD
2.8.7.0-01082016-1
Click to expand...
Click to collapse
Hello thank you for this. Yesterday I tried to build as well twrp but it wasn't fully working.
I just imported this config with TW_INCLUDE_L_CRYPTO := true && TW_INCLUDE_CRYPTO := true
I didnt copy paste the twrp.fstab I added but added its path to BOAR_smthing.
Also I used omnirom's android-6.0 revision with dragon's device tree.
The recovery seems to boot, as
Code:
adb devices
returns XXXXXx recovery.
Also I can reach the device's shell with adb shell. Just the screen stays black.
I was wondering if I missed something. Is your device tree available online ?
Khaon said:
Hello thank you for this. Yesterday I tried to build as well twrp but it wasn't fully working.
I just imported this config with TW_INCLUDE_L_CRYPTO := true && TW_INCLUDE_CRYPTO := true
I didnt copy paste the twrp.fstab I added but added its path to BOAR_smthing.
Also I used omnirom's android-6.0 revision with dragon's device tree.
The recovery seems to boot, as
Code:
adb devices
returns XXXXXx recovery.
Also I can reach the device's shell with adb shell. Just the screen stays black.
I was wondering if I missed something. Is your device tree available online ?
Click to expand...
Click to collapse
Not yet. I'm going to upload it later on to the TWRP devs for official inclusion.
You need to merge the minui patch so TWRP can use DRM for video on the Pixel C; there is no fb0 device.
there were some new boot images out today. i flashed one of them. when i boot to recovery the sdcard is not able to be mounted. do you have any suggestions on what i need to do or look at in order to get it fixed?
dkryder said:
there were some new boot images out today. i flashed one of them. when i boot to recovery the sdcard is not able to be mounted. do you have any suggestions on what i need to do or look at in order to get it fixed?
Click to expand...
Click to collapse
Because /data is (force-)encrypted. I uploaded a new TWRP build with various fixes but decryption doesn't work.
What I also found out is that the boot image for the Pixel C is NOT an Android boot image (!), but a ChromeOS one. This puts a lot of things in doubt, for example I am not sure if systemless SuperSU can handle this.
But, I'm working on all that (working on boot img without forced encryption right now, but so far it doesn't want to boot completely)
OK, so, I'm running the device unencrypted now, but there are many issues still to resolve.
OK guys, if you really want actual SuperSU, and other root stuff, and decrypted /data, here's how it works but it's complicated and will only work tethered as far as I can tell.
First, download this boot image: dragon-boot-encryptable-01092016-1.img
Now here are the steps:
- make sure you have a stock boot.img handy in case something goes wrong (as usual I can not take responsibility but chances of bricking are extremely slim if you know what you're doing)
- boot into fastboot
- flash the above boot image to boot ("fastboot flash boot dragon-boot....")
- flash the TWRP recovery (latest version) ("fastboot flash recovery twrp-dragon-...")
- hold power+vol down pressed.. the device will turn off, keep it pressed even as it turns off, it will turn on again and you are in the coreboot menu
- select "Android Recovery" which will start TWRP
- in TWRP, select system as read only when it asks ("never write onto the system partition").. my boot image does not disable dm-verity which seems to be still in effect, so if you change /system, the Pixel will refuse to boot (even though it's unlocked... no idea)
- once in TWRP, go to "Wipe" and then choose at the bottom "Format Data" (just wiping will not work)
- when that's done stay in the recovery
- get SuperSU 2.66 from somewhere and flash it through TWRP (using sideload for example)
- when it's done, go to "Backup" in TWRP and only backup boot (the kernel) - no password - no compression
- somehow copy the backed up kernel from the device to your computer ("adb pull" for example), but in no case let the Pixel boot into Android
- when that's done, tell TWRP to boot back into the bootloader
Now get ready to be real quick...
- boot (just boot, not flash) the TWRP backed up boot image (it's 32MB large and called boot.emmc.win, but it's all good): "fastboot boot boot.emmc.win" (and now you have to be rather quick)
- It will boot up for a second and then go back to the "The OS will boot in 30 seconds screen"
- Again press power+vol down and hold it, even as the device turns off, until you're in the coreboot bootloader
- There, choose fastboot again
- And once again boot the boot.emmc.win image ("fastboot boot boot.emmc.win")
- Now let it boot up
- If everything went OK you should be in Android, with decrypted /data, and SuperSU should be installed and working
If you want to avoid being encrypted again (although SuperSU should survive that) you will have to boot tethered everytime using that boot.emmc.win image.
Known Issues: Somehow because /data is decrypted, "Security" settings in Android will crash. Hopefully you don't need anything in there. You might also want to skip setting a lock pattern or pin when doing the initial setup, it might crash too.
So far, I tried installing AdAway using root which worked just fine.
If someone figures out how make this untethered: you da real MVP!
Thank you sir!! I will report back if I encounter any undocumented issues.
OK so I've managed to install Xposed, was pretty straightforward except for the tethered boot. Still looking into making it untethered.
since your modified boot and no encryption it seems to be smoother in graphics. in any event, the thing worked in format of data and install of the supersu zip. so, well done.
cheep5k8 said:
How to install:
- Unlock bootloader
- In the bootloader, run "fastboot flash recovery <.img file>"
- Reboot into Pixel C coreboot bootloader
- Boot into recovery (or later on/from Android through "adb reboot recovery")
DOWNLOAD
2.8.7.0-01082016-2 UPDATE: Includes various fixes from first build; decryption of data does NOT yet work
Click to expand...
Click to collapse
So, followed these instructions and whenever I try to reboot into recovery I get the no command screen. Am I missing something? lol
Edit: So figured thats the stock recovery stuff. Got to the stock recovery but can't get into twrp
2nd Edit: I redownloaded the file and didnt rename it shorter this time and now it works...weird
cheep5k8 said:
Not yet. I'm going to upload it later on to the TWRP devs for official inclusion.
You need to merge the minui patch so TWRP can use DRM for video on the Pixel C; there is no fb0 device.
Click to expand...
Click to collapse
Thank you for those informations .
Thank you so much for this! Aside from the laggy UI, which isn't an issue since we got TWRP (f yes!!!), this is amazing. Do you foresee any issues flashing fonts? I am not familiar with ChromeOS and Android structure combination as it seems there is a lot of talk about. Flashing a file that replaces the stock fonts with the ones of my choosing hypothetically should not pose a problem to /system/fonts/, correct? Thank you for your work
CTR Recovery for Galaxy A5
Hi all,
I've ported CTR Recovery from the developer carliv (now bluefirebird) on our Galaxy A5.
This recovery is based on the old CWM, by koush, with some features you can find in the original post HERE, so if you are tired of the TWRP recovery and u are looking for something similar to the old CWM, don't hesitate to download this
NOTE: It should work in any A500 variant, but it's tested only on SM-A500FU variant, so flash on other variants at your own risk!
Desclaimer:
Code:
echo "I'm not responsable for bricked phones, overheat phones, for global warming, for phones that want to suicide without a reason and for imminent explosions"
DOWNLOADS: You can download the recovery here: https://www.androidfilehost.com/?w=files&flid=82499
HOW TO FLASH:
ON WINDOWS (Odin method)
1) Download Odin
2) Download the recovery (with .tar extension)
3) Go in download mode by pressing Power Button + Vol - + Home Button
4) Connect your smartphone to the PC
5) Open odin version 3.9 or 3.10
6) Select AP button and open the recovery file
7) Press start
8) Enjoy
ON LINUX (Heimdall method):
1) Extract tar file with:
$ tar xvf recovery_file.tar
You will find a recovery.img file
2) Open Heimdall Frontend
3) Select pit file (you can find it on sammobile)
4) Select recovery partition
5) Load the recovery.img file and flash
6 Enjoy
ON ANDROID (Need Root)
1) Download flashify or rashr
2) Extract recovery file with apps such as zArchiver and you will find a recovery.img file
3) Open flashify or rashr and select recovery file
4) Flash it
5) Enjoy
ON RECOVERY
IF YOU ARE ON TWRP:
1) Extract recovery file with apps such as zArchiver and you will find a recovery.img file
2) Reboot to recovery
3) Go to install zip menu
4) Select "Install Image" box
5) Select recovery.img file and flash in recovery partition
6) Reboot to recovery
6) Enjoy
ON TERMINAL
If you are on Android (any rom, TWRP, or CTR) (Need Root)
1) Open terminal. If you are on CTR you need Aroma FileManager
2) run:
$ dd if=/path/to/recovery.img of=/dev/block/bootdevice/by-name/recovery
If you are on adb run:
$ adb shell dd=/path/to/recovery.img (inside the phone, not the path of the recovery.img stored in the pc) of=/dev/block/bootdevice/by/name/recovery
3) Enjoy
[NEW] CTR with CWM graphics section
Well, since CWM support ended with cm-11.0, and no one resurrected it, I've decided to give my contributo to the best recovery (in my opinion) which written the begin of android customization, for flashing zip roms, take nandroid backups... So, as I said, since no one resurrected it, I've decided to modify ctr sources, which are based on CWM recovery and which are compilable in cm-12.1 and cm-13.0, for creating a recovery which has, CTR features, but which really like the old CWM.
-So, what does this version offer?
~If you want to know what does it include, please see read this (green highlighted text)
NOTE: If you want to compile with cwm recovery you need my fork which you can find here:
https://github.com/DeadSquirrel01/carliv_touch_recovery_new only cm-12.1 branch for the moment
Then you need to add in BoardConfig.mk (in the device tree) the following flag:
USE_CWM_GRAPHICS := true
otherwise it will compile standard CTR
Flashing instuctions:
Look at "HOW TO FLASH" section
Download Link: Same as CTR recovery link, but you have to download the ones wich have a name which begins with "[CWM]"
OTHER NOTE: Since I've compiled CTR with CWM graphich with an half crapped cm-12.1 source tree, and adb doesn't work (except in sideload), I couldn't take screenshot, so, I've uploaded some photos, instead, which are taken with my ~4 years ago Samsung Galaxy Pocket, so don't flame me for bad quality , and since I tried to upload in attachments, but it doen't show the photo when clicking on the attachment, I've upload a zip with 4 screenshots
HERE (Google Drive Link)
Credits:
@bluefirebird for recovery sources
@TheWhisp for device tree
Me (DeadSquirrel01) for porting the recovery , adding CWM graphics, editing images and adding some cwm features
Sources:
Device Tree: https://github.com/DeadSquirrel01/android_device_samsung_a5-common
CTR: https://github.com/carliv/carliv_touch_recovery_new
CTR with CWM graphics: https://github.com/DeadSquirrel01/carliv_touch_recovery_new branch cm-12.1 only for the moment and you need to add "USE_CWM_GRAPHICS := true" in BoardConfig.mk
Changelog
03/09/2016 (update N2):
_ Add menu color change: you can now change highligh+text color to 3 different colors: blue (default), green or orange.
See my github commit for info, I wrote some awesome comments
06/10/2017 (Update N3):
_Save menu color setting to /sdcard/clockworkmod/cwm_config, so that it's not lost on reboot, resulting a recovery which has always the blue color, even if the user has chosen orange or green.
Thanks for this contribution, try it just have time. For now, I walk with your version of TWRP working well. This CTR Recovery is compatible for install ROMs Marshmallow (Base Stock and CM13 Based)? Cheers.
Thank you DeadSquirrel01 it works perfectly on my A500G running stock marshmallow 6.0.1. Great work
oss_mosis said:
Thanks for this contribution, try it just have time. For now, I walk with your version of TWRP working well. This CTR Recovery is compatible for install ROMs Marshmallow (Base Stock and CM13 Based)? Cheers.
Click to expand...
Click to collapse
Yes you can install roms
meemb said:
Thank you DeadSquirrel01 it works perfectly on my A500G running stock marshmallow 6.0.1. Great work
Click to expand...
Click to collapse
Thanks for the support
you welcome brother
DeadSquirrel01 said:
Yes you can install roms
Thanks bro, unfortunately I have not been able to prove that the screen of my Galaxy A5 is broken and the phone is unusable for now, but I have already shared this Post on Facebook Group so that other users go testing, any news will be reporting here.
A hug. :good:
Click to expand...
Click to collapse
DeadSquirrel01 said:
Yes you can install roms
Thanks bro, unfortunately I have not been able to prove that the screen of my Galaxy A5 is broken and the phone is unusable for now, but I have already shared this Post on Facebook Group so that other users go testing, any news will be reporting here.
A hug. :good:
Click to expand...
Click to collapse
Thanks bro
Nice Recovery.. Succesfully rooted my stock 6.0.1 by flashing supersu (you can flash this file to root on any android which have custom recoveries) on this recovery. It is like stock recovery but with a lot of features.
@DeadSquirrel01 works well on A500F (Duos). Also i tried to get stuck in recovery mode with no succes . So i can say it`s better than twrp. I was waiting for this moment since i got the phone . Many many thanks! Cheers!
LE: Wait a second... So how this recovery has almost 3 months and isn`t that known?
LE2: Some feedback - mount usb storage doesn`t do anything (yes i have sdcard). Also no adb support. So is kinda impossible to push files into phone while it`s in recovery...
corsicanu said:
@DeadSquirrel01 works well on A500F (Duos). Also i tried to get stuck in recovery mode with no succes . So i can say it`s better than twrp. I was waiting for this moment since i got the phone . Many many thanks! Cheers!
LE: Wait a second... So how this recovery has almost 3 months and isn`t that known?
LE2: Some feedback - mount usb storage doesn`t do anything (yes i have sdcard). Also no adb support. So is kinda impossible to push files into phone while it`s in recovery...
Click to expand...
Click to collapse
You can only use sideload regarding adb and i think it isn't known coz everyone use only twrp now
DeadSquirrel01 said:
You can only use sideload regarding adb and i think it isn't known coz everyone use only twrp now
Click to expand...
Click to collapse
Personally i`m more with CWM.. Simple and yet so complex. TWRP is a bit more polished on the UI side, but that bug that keeps me in the recovery drives me crazy [emoji35] . This CTR recovery it`s able to reset the flag and push the device out of recovery... So it`s better IMO.
Anyway i read here and there that Nougat based roms can be flashed in CWM 6.0.5.x so i`ll try to port Philz latest recovery on our device, since i had it for years on my retired devices. Thanks for all your work and for the source!
LE: Sideload doesn`t work since adb isn`t enabled on the recovery..
corsicanu said:
Personally i`m more with CWM.. Simple and yet so complex. TWRP is a bit more polished on the UI side, but that bug that keeps me in the recovery drives me crazy [emoji35] . This CTR recovery it`s able to reset the flag and push the device out of recovery... So it`s better IMO.
Anyway i read here and there that Nougat based roms can be flashed in CWM 6.0.5.x so i`ll try to port Philz latest recovery on our device, since i had it for years on my retired devices. Thanks for all your work and for the source!
LE: Sideload doesn`t work since adb isn`t enabled on the recovery..
Click to expand...
Click to collapse
Windows adb? With linux adb works perfectly but with windows adb not ¯\_(ツ)_/¯
And... good luck with your philz port
DeadSquirrel01 said:
Windows adb? With linux adb works perfectly but with windows adb not ¯\_(ツ)_/¯
And... good luck with your philz port
Click to expand...
Click to collapse
Thanks... It`s on my todo list but i don`t have enough time to do anything now. About the adb - shouldn`t be same thing? What`s the difference between adb in linux and windows? Wait to switch linux to test. Could also be something specific to my device since you made the recovery for FU and i have F.. Cheers!
So i rebooted in linux and here`s the output:
Code:
[email protected] ~ $ adb devices
List of devices attached
???????????? no permissions
[email protected] ~ $ adb shell
error: insufficient permissions for device
And when tryin` to Mount USB Mass storage this is the output:
Code:
Error mounting /dev/sr1 at /media/hades/671D-12F5: Command-line `mount -t "vfat" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,shortname=mixed,utf8=1,showexec,flush" "/dev/sr1" "/media/hades/671D-12F5"' exited with non-zero exit status 32: mount: /dev/sr1 is write-protected, mounting read-only
mount: /dev/sr1: can't read superblock
I have 32gb class 10 sdcard formatted as fat32.. And from what i see it tries to mount as vfat, this for sure is from the fstab..
Any ideas?
corsicanu said:
Thanks... It`s on my todo list but i don`t have enough time to do anything now. About the adb - shouldn`t be same thing? What`s the difference between adb in linux and windows? Wait to switch linux to test. Could also be something specific to my device since you made the recovery for FU and i have F.. Will edit this post in a minute. Cheers!
Click to expand...
Click to collapse
Since it's a recovery it works with any a500xx variant (same chipset ) and also it's the same thing with roms for example on my pac-rom rom noone said it doesn't boot on a500xx. Regarding adb, bad drivers i think
I don't know how much i can thank you, when i use TWRP my phone won't boot into the system but it works perfectly with this recovery
Qcraft said:
I don't know how much i can thank you, when i use TWRP my phone won't boot into the system but it works perfectly with this recovery
Click to expand...
Click to collapse
So use thiz
What I like in it is while I am in this recovery and my phone is charging, and I select reboot, it boot to the system unlike other recovery.
I had installled custom ROMs, Flashed kernel image, and used ADB sideload so far
akil777 said:
What I like in it is while I am in this recovery and my phone is charging, and I select reboot, it boot to the system unlike other recovery.
I had installled custom ROMs, Flashed kernel image, and used ADB sideload so far
Click to expand...
Click to collapse
anyway if in twrp it doesn't reboot you can run $ reboot in advanced->terminal
DeadSquirrel01 said:
anyway if in twrp it doesn't reboot you can run $ reboot in advanced->terminal
Click to expand...
Click to collapse
Yep.. this terminal has commands nearly or exactly like linux ubuntu.
akil777 said:
Yep.. this terminal has commands nearly or exactly like linux ubuntu.
Click to expand...
Click to collapse
Yes, the commands of any linux distro, but they are less... only indispensable commands
Team Win Recovery Project
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
FEATURES:
FBE Decryption support
MTP support
ADB root
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
CONTRIBUTIONS:
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
TWRP for Mi 6, Tool/Utility for the Xiaomi Mi 6
Contributors
TheStrix
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created 2017-06-10
Last Updated 2018-07-07
FAQ
FAQ:
HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?
To get logs while in TWRP, you should connect your device to your PC and use adb.
adb pull /tmp/recovery.log
adb exec-out dmesg > dmesg.log
This will create 2 files in the directory your shell is currently in, recovery.log and dmesg.log. You will need to upload these somewhere such as a pastebin or Google Drive. You can also attach it to your XDA post (recommended!)
If you are having an operating system boot issue, you should gather a ramoops log instead. Do this while in TWRP after the failed boot:
adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar
MY RECOVERY KEEP GETTING REPLACED WITH STOCK RECOVERY... WHAT KIND OF MAGIC IS THIS?
The file: /system/bin/install-recovery.sh present in stock system is responsible for that.
You can simply stop this from happening by deleting it or renaming it to install-recovery.sh.bak using any root explorer or via TWRP (Advanced -> File Manager).
Reserved
Nice
Praying for good developers working on Mi6
Thx for TWRP
thanks
Thanks a lot for your work.
Any comparison to ValoXis / cofface version?
Thanks
Thanks a lot for your work!
Can I disable dm-verify with this revovery when using official MIUI rom?
Can not be backed up
.nice thank you !
Maybe lineage is next ? ?
Any reason why it asks me for a password?
Thanks!
Yeah, Parth its here
Now it's time to xiaomi to release kernel sources
Successfully re-flashed from ValoXis version via official TWRP app.
Thanks Strix!
Tried to restore from backup, This is the thing what I backed up :
1. Backup1 : boot, recovery, EFS
2. Backup2 : system, system image, data, cache
I tried to restore from backup2 first from failing the installation of China dev ROM. Wipe system, data, cache, dalvik, and do the backup.
It's booted okay (it uses the custom boot animation I picked), but at the end / near the end of the boot animation, there's low battery sound played, then the device is switched off.
Tried again to wipe everything, restore backup2, then backup1, I got the same "low battery" sound notification.
In the end I had to reflash Xiaomi.eu ROM and start fresh.
So what actually happened there?
Hello, after installing twrp this one does not stay, do you have a solution? thank you
Thanks a lot for your work!
I hope Sagit can get recovery by ZCX
Sent from my Xiaomi Mi 6 using XDA Labs
TWRP 3.1.1-1 release:
Fixes the nandroid backup/restore issue
(Notice: backups made using old recovery builds still won't restore fine)
Other updates
Also for some of you've have been wondering,
MY RECOVERY KEEP GETTING REPLACED WITH STOCK RECOVERY... WHAT KIND OF MAGIC IS THIS?
The file: /system/bin/install-recovery.sh present in stock system is responsible for that.
You can simply stop this from happening by deleting it or renaming it to install-recovery.sh.bak using any root explorer or via TWRP (Advanced -> File Manager).
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 8T
Installation:
# To temporarily boot it
fastboot boot <twrp_file_name>.img
# Since 8T/9R has a separate recovery partition, you can flash the recovery with
fastboot flash recovery <twrp_file_name>.img
Updating to a newer build:
Simply flash the latest TWRP installer zip from TWRP
OR
Flash the img from TWRP/fastboot
FAQ/Know Bugs are given in post #2
Send me a beer, if you think I deserve it: PayPal
Huge thanks to:
@bigbiff (For everything )
@Lossyx
@osm0sis
@Nebrassy
@Qnorsten
for helping in making this recovery. Without these people, TWRP for this device would not have been possible.
Special mention to a friend @apophis9283
Trees:
Device: https://github.com/theincognito-inc/android_device_oneplus_kebab
Kernel: https://github.com/AOSPA/android_kernel_oneplus_sm8250
Download:
OnePlus 8T (kebab)
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
If you need a black themed TWRP (same TWRP as the above, but themed black), you can go to this thread:
[RECOVERY] TeamWin Recovery Project black Themed [OP8T] [2022-03-11]
TeamWin Recovery Project (TWRP) with full black Theme I build a full black themed TWRP for the Oneplus 8t. This is based on the latest TWRP done by @theincognito This nice black Theme was originally created by @Morphine1 and @acuicultor for...
forum.xda-developers.com
FAQ and Known bugs of TWRP:
If you are planning to switch to a custom ROM, and are currently on OOS/H2OS, format /data, switch slot, reboot to TWRP and then sideload/flash the ROM + installer.
It's better to flash ROM + TWRP installer, if you want to keep your TWRP after flashing a ROM.
Don't format /data, after a flashing a ROM, before the first reboot.
It takes around 50s to actually boot into TWRP.
Ideal way to flash:
For OOS to Custom ROM - Format /data, switch slot, reboot to TWRP, sideload/flash ROM + installer, reboot to TWRP, flash Magisk/Gapps. Reboot to system.
For Custom to Custom ROM - Format /data. Flash ROM + installer, reboot to TWRP, flash Magisk/Gapps. Reboot to system.
For updating a custom ROM - Flash ROM + installer, reboot to TWRP, flash Magisk/Gapps. Reboot to system
For custom ROM to OOS - Format /data. Flash ROM + installer, reboot to TWRP, flash Magisk. Reboot to system.
PS: After formatting /data, until the first time the device is booted to system, the files you send to phone via MTP (USB) will be at /data/media, not at /sdcard
PS2: If, for some reason, you cannot send files to phone after formatting /data and rebooting to TWRP, press vol +, vol - and power button simultaneously.
PS3: Factory reset WILL NOT wipe internal storage.
Steps for backing up and restoring data in TWRP (Huge thanks to @BillGoss )
TL;DR for data backup on custom ROMs:
Backup /data (copy the backup folder to PC if you will format /data).
Flash the ROM and boot it once to system.
Restore /data (copy the backup folder back from PC if you formatted in step 1) and boot into system.
If you find any issues like missing navigation bar or blank screen or something, just do a normal reboot again to system.
System Backup and Restore
The "system" partitions on the OnePlus 8T are:
Boot
DTBO
Super which contains the logical system, system_ext, odm, product, and vendor partitions
Just backup and restore these partitions.
Do NOT backup/restore any of the logical partitions individually.
Data Backup
Make sure USB debugging is enabled
You do NOT need to remove your password
In TWRP
Backup: Select only the Data partition.
Reboot System
Restore
Remove the current password before starting the restore process by Settings>Security & Lock Screen>Screen lock: Select Swipe (if prompted tap on "Yes, remove")
If you don't do this, the system will not reboot properly after restoring.
This will also remove your fingerprint data and your lockscreen (encryption) password (you won't be prompted for a password in TWRP or when you restart the system)
In TWRP
Wipe>Factory Reset
Reboot System (this will rebuild the data partition)
Back in TWRP
Restore: Select the backup you want to restore
Remove the SIM card. If you don't do this the system won't boot properly.
Reboot system, making sure the phone is not connected to a PC
Notes:
At this point the phone will take longer than usual to boot - that's normal
You will be presented with a blank screen
Connect the phone to a PC. You should be able to see the phone using adb devices
Disconnect the phone from the PC
Hold the Power button down and select Restart
In System
Settings>Security & Lock Screen>Screen lock: set your password
Insert the SIM card
Note: Your fingerprints will have been restored because the backup was taken with the password set.
besss
Works flash in fkm?
This is great!
liver20 said:
Works flash in fkm?
Click to expand...
Click to collapse
fastboot only
Thanks for it!
Gonna try it!
Amazing! My OnePlus 8T is arriving tomorrow. Perfect timing for TWRP, thanks a lot for the detailed instructions as I am going to need it.
I was flashing this twrp with the previous test_kebab twrp as flash .img. Choosing recovery partition and was thicking "install to both slots".
So far works good.
Bro, I'm happy for you. Great job.
@theincognito Though I am a fastboot flash guy at this point (honestly forgot how to even use TWRP after all this time), I appreciate all the work and time you (and apop) put in for this project. It's definitely going to make this device appeal to more Android enthusiasts as most are used to and prefer TWRP for flashing I've noticed. And that will lead to more development (hopefully) for the device. That seems to have been the case with previous devices I've owned that had TWRP available, but also had the fastboot method available.
Anyway, I have been up for like 32 hours, so if what I've said doesn't make much sense, sorry.
Thanks @theincognito for all your work and time, and I hope this brings more to the 8t community. Good job!
He has this. Again, great job. Glad folks now have a thread to come to for proper support
liver20 said:
Works flash in fkm?
Click to expand...
Click to collapse
Yep, works fine.
You can also flash the zip in the Magisk app, manually from the modules page.
Booted on 9R but unable to decrypt data, after switching to 9R compatible kernel everything is working fine.
Nice job bro.
YumeMichi said:
Booted on 9R but unable to decrypt data, after switching to 9R compatible kernel everything is working fine.
Nice job bro.
Click to expand...
Click to collapse
Is there a unified kernel tree you know of?
osm0sis said:
Is there a unified kernel tree you know of?
Click to expand...
Click to collapse
I'm using kernel source from aospa.
GitHub - AOSPA/android_kernel_oneplus_sm8250
Contribute to AOSPA/android_kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
Unified prebuilt kernel · YumeMichi/[email protected]
This should be working fine on both OP8 serials and 9R Signed-off-by: YumeMichi <[email protected]>
github.com
@YumeMichi Thanks a lot for this. I shall make a build with the AOSPA kernel and test on 8T. Should I release it here then, or do you wanna release for 9R?
theincognito said:
@YumeMichi Thanks a lot for this. I shall make a build with the AOSPA kernel and test on 8T. Should I release it here then, or do you wanna release for 9R?
Click to expand...
Click to collapse
It would be great if you can do that.
YumeMichi said:
It would be great if you can do that.
Click to expand...
Click to collapse
I will PM you the build once it's done Then let me know whether it works for 9R too
EDIT: Posting it here
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
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_venus
https://github.com/TeamWin/android_device_xiaomi_sm8350-common
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomimi11.html
Android 12 compatible?
pogi.paul0119 said:
Android 12 compatible?
Click to expand...
Click to collapse
Only with no pin/password
Niice thanks for the recovery bro
Nebrassy said:
Only with no pin/password
Click to expand...
Click to collapse
So answer is "no"
great thank you for the recovery, I hope that the rom quotes will finally be able to get us plenty of custom
Nebrassy said:
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
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_venus
https://github.com/TeamWin/android_device_xiaomi_sm8350-common
Telegram group: https://t.me/NSSFB
first test build here, test and report what works/doesn't:
https://build.twrp.me/twrp-3.6.0_11-0-venus.img
Click to expand...
Click to collapse
thank you very much. I installed it for a12. twrp worked. but I couldn't install magisk. How can I install magisk?
Can i update from unofficial 3.5.1 twrp.
But advance not have menu install recovey
Antyhaker said:
So answer is "no"
Click to expand...
Click to collapse
Hummm no it's your selfish answer. It's already good to hear A12 is compatible without security PIN/Password instead of nothing. Congrat dev for his work and for be now the official maintainer
agabey_42 said:
thank you very much. I installed it for a12. twrp worked. but I couldn't install magisk. How can I install magisk?
Click to expand...
Click to collapse
ROM ? MIUI or AOSP ?
You can flash magisk (canary recommanded) directly from TWRP after first setup / boot (so after complete first ROM configuration settings) reboot to TWRP and flash magisk
If from TWRP magisk is not installed, you must using the boot.img patched method.
nunggg said:
Can i update from unofficial 3.5.1 twrp.
But advance not have menu install recovey
Click to expand...
Click to collapse
From TWRP > Install > click button on bottom for change "Install Zip" to ""Install Image" > select new TWRP 3.6 img > Flash
After successfully flashed TWRP, Reboot > Recovery
You can also update from adb (on bootloader/fastboot mode) with this simple line :
Code:
.\fastboot boot twrp-3.6.0_11-0-venus.img
And after flashing, go to recovery mode, it's updated
I'm on Rom 21.12.8, I installed twrp successfully but it can't read the data, I removed all the passwords
Hi
When i try do do this,
"From TWRP > Install > click button on bottom for change "Install Zip" to ""Install Image" > select new TWRP 3.6 img > Flash
After successfully flashed TWRP, Reboot > Recover"
I have one more screen to choose.
I have to select partition.
The options are:
Boot
Dtbo
Persist
Super(system,product,odm, system_ext, vendor)
What should i choose?
Nice job!!! Hope there will be more roms for our phone.
Hello,
I need help, I just intall the new TWRP with the latest Xiaomi.eu stable.
I have a patern and TWRP doesn't let me make my patern to decrypt data.
Can I flash my previous TWRP even if I can't access data ?
Thank you very much !
Edit : I did it, and everything is OK !
After update recovery fastboot loop after reboot every time
please recommend
Nebrassy said:
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
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_venus
https://github.com/TeamWin/android_device_xiaomi_sm8350-common
Telegram group: https://t.me/NSSFB
first test build here, test and report what works/doesn't:
https://build.twrp.me/twrp-3.6.0_11-0-venus.img
Click to expand...
Click to collapse
Could the install command be wrong? I think typing flash was forgotten in the command.
will this be true? fastboot flash boot twrp.img
agabey_42 said:
Could the install command be wrong? I think typing flash was forgotten in the command.
will this be true? fastboot flash boot twrp.img
Click to expand...
Click to collapse
Simply read a little some reply... There litteraly the command
its NOT working (no files/directories on install zip section)
21.12.8 at A12 (no pins/password)
thanks very much for your efforts mate!
I remove pin or password and install twrp but TWRP can't access data (internal data)
Santoshlove20 said:
I remove pin or password and install twrp but TWRP can't access data (internal data)
Click to expand...
Click to collapse
Same with me. I do everything but not access data.
Solve problem
-Back to Global firmware for me is back to "venus_global_images_V12.0.4.0.RKBMIXM_20210306.0000.00"
After finish need to install TWRP
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3.Reboot TWRP
4.Send the ROM to your phone
5.Install Rom ( EU or Custom rom )
6.Do not reboot after installation complete. Go back in main TWRP menu
7.Go in Wipe menu > Format Data button > Type ' yes ' to confirm > OK
8.Rebot system and Enjoy.