Related
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
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 NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
More information:
Most Xperia S kernels are probably including CWM by default in the boot image. About a month ago I submitted some changes to the CyanogenMod repos that were accepted. Newer builds of CM include a special extract_elf_ramdisk utility that I wrote to read and extract a recovery ramdisk from the FOTAKernel partition instead of using the ramdisk that is included in the boot image. If the ramdisk in the FOTAKernel partition is a stock Sony ramdisk or not present, then the existing ramdisk in the boot image is used instead. This setup allows users to choose which recovery they want to keep installed. This same setup is possible in other kernels including stock Sony kernels. On our website's download link you will find a copy of a recent stock ICS kernel for the Xperia S that includes TWRP as well as the extract_elf_ramdisk utility.
If the kernel you have installed doesn't support this extract_elf_ramdisk setup, then you won't be able to use the GooManager installed copy of TWRP. Bug your kernel or ROM developer and ask them to update their images so that you can choose what recovery you want.
What is the FOTAKernel partition?
The FOTAKernel partition is used by Sony to do FOTA updates when updating the boot image. Unlocked devices can't take Sony FOTA updates so using this partition for storing the recovery ramdisk seems like a good idea. Unlocked users aren't able to use this partition anyway and the FOTAKernel partition is effectively the "recovery" partition on Sony devices.
Thanks a lot but from your site can we get only 2.4.0.0. And it's for the oldest rom kernel (.452). Can you please update the ramdisk and modem for the our Xperia S?
anychange for locked BL?
Advance Stock Kernel 17 comes with CWM.
How Can I install this over CMW?
eScapeeXc said:
Thanks a lot but from your site can we get only 2.4.0.0. And it's for the oldest rom kernel (.452). Can you please update the ramdisk and modem for the our Xperia S?
Click to expand...
Click to collapse
You should take a look at the "Download - FOTAKernel Image" header. There's no need to install that stock kernel, you can also just push the recovery. The way described on the website requires you use Terminal Emulator but there's an easier way. (I also don't really understand which is the right version because there is 2.4.3.0 for nozomi and 2.4.3.0 for LT26i and afaik that's the same device).
Just install GooManager on your phone, select "Flash ROMs" and there should be a message asking if you have a custom recovery. Select to install one and the latest version of TWRP will be installed.
I'm using Stock+ kernel, that already had TWRP 2.4.1 recovery, after doing this with GooManager I have TWRP 2.4.3.0. If you're using any of the other .55 kernels it should be work as well.
mrkidvn said:
anychange for locked BL?
Click to expand...
Click to collapse
No idea.
darkerm said:
Advance Stock Kernel 17 comes with CWM.
How Can I install this over CMW?
Click to expand...
Click to collapse
That's basically the same question eScapeeXc asked so the answer is the same .
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]
Is it works on locked bootloader?
Sent from my LT26i using xda app-developers app
Will:
dd if=/dev/zero of=/dev/block/mmcblk0p11
remove the recovery?
Is there a way to choose between the recovery from the kernel and this one on fota while booting?
How many space has the fota partition on our device?
algates said:
Is it works on locked bootloader?
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
It needs a modified ramdisk. So it will not work.
Sv: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]
Dees_Troy said:
More information:
Most Xperia S kernels are probably including CWM by default in the boot image. About a month ago I submitted some changes to the CyanogenMod repos that were accepted. Newer builds of CM include a special extract_elf_ramdisk utility that I wrote to read and extract a recovery ramdisk from the FOTAKernel partition instead of using the ramdisk that is included in the boot image. If the ramdisk in the FOTAKernel partition is a stock Sony ramdisk or not present, then the existing ramdisk in the boot image is used instead. This setup allows users to choose which recovery they want to keep installed. This same setup is possible in other kernels including stock Sony kernels. On our website's download link you will find a copy of a recent stock ICS kernel for the Xperia S that includes TWRP as well as the extract_elf_ramdisk utility.
If the kernel you have installed doesn't support this extract_elf_ramdisk setup, then you won't be able to use the GooManager installed copy of TWRP. Bug your kernel or ROM developer and ask them to update their images so that you can choose what recovery you want.
What is the FOTAKernel partition?
The FOTAKernel partition is used by Sony to do FOTA updates when updating the boot image. Unlocked devices can't take Sony FOTA updates so using this partition for storing the recovery ramdisk seems like a good idea. Unlocked users aren't able to use this partition anyway and the FOTAKernel partition is effectively the "recovery" partition on Sony devices.
Click to expand...
Click to collapse
Does this mean that flashing TWRP on Xperia S, this way, will prevent it from being overwritten every time a new kernel is flashed?
twk99 said:
Does this mean that flashing TWRP on Xperia S, this way, will prevent it from being overwritten every time a new kernel is flashed?
Click to expand...
Click to collapse
Yes.
twk99 said:
Does this mean that flashing TWRP on Xperia S, this way, will prevent it from being overwritten every time a new kernel is flashed?
Click to expand...
Click to collapse
[email protected] said:
Yes.
Click to expand...
Click to collapse
Keep in mind, if kernel you are using doesn't implement elf extract then it will not read FOTA partition so it still use recovery that came with kernel.
And almost all kernel came with CWM.
Sv: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]
tosa.th said:
Keep in mind, if kernel you are using doesn't implement elf extract then it will not read FOTA partition so it still use recovery that came with kernel.
And almost all kernel came with CWM.
Click to expand...
Click to collapse
I understand that. I am using latest FXP CM10 so it should work right?
i rooted my uncle sxs like this http://forum.xda-developers.com/showthread.php?t=2133063 after that i installed cmw with this http://forum.xda-developers.com/showthread.php?t=1756346
yes i have unlocked the bootloader. but now the recovery says cannot mount cache/recover/log etc.
i post this here because after installing opensemc 0.4 the problem is still there. only after a factory reset and installing 2 times it will boot.
is this a problem some one reconizes?
R: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]
raydekok said:
i rooted my uncle sxs like this http://forum.xda-developers.com/showthread.php?t=2133063 after that i installed cmw with this http://forum.xda-developers.com/showthread.php?t=1756346
yes i have unlocked the bootloader. but now the recovery says cannot mount cache/recover/log etc.
i post this here because after installing opensemc 0.4 the problem is still there. only after a factory reset and installing 2 times it will boot.
is this a problem some one reconizes?
Click to expand...
Click to collapse
I read that FXP official kernel support external recovery from 3-4 release
But maybe raymanfx has not implemented this
Btw that recovery is a crap.. Try advanced stock kernel
Sent from my Xperia S using xda app-developers app
just flash this thru the current recovery?
and install rom again?
twk99 said:
I understand that. I am using latest FXP CM10 so it should work right?
Click to expand...
Click to collapse
I don't use FXP, so I don't know is it support elf extract.
Check with FXP team about their kernel if it does support then you are good to go.
reading a bit more and i can instal the recovery thru goomanager and thats it. so i install the recovery again. is it so simpel?
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]
Installing seems ok. But how can I uninstall twrp from fota?
Sent from my LT26i using xda premium
raydekok said:
reading a bit more and i can instal the recovery thru goomanager and thats it. so i install the recovery again. is it so simpel?
Click to expand...
Click to collapse
quote myself. this worked but under mount he can not select mount /system.
under my phone i can. what would that be?
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
WARNING!
Your warranty is now void!
We are not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at us for messing up your device, we will laugh at you.
FEATURES:
All Normal TWRP Functions
Fixed Aroma Installers
Dual Boot Patcher Support!
Replaced Normal Fonts with Google Sans Fonts !
Pre-installed Ubuntu Theme insted of boring one
Added Option To Backup EFS (totally new!)
Fixed Formatting Stuck Problem
Removed Supersu !
And Many More! Explore It Yourself
INSTALLATION:
(*)With PC/Laptop (Recommended) :
Copy the downloaded recovery to adb folder
press and hold shift key and right click anywher on the file explorer screen
open cmd from the context menu
then make sure you rename the downloaded recovery to recovery.img
now put the phone in fastboot mode by holding the power+vol up until you see the green screen
type 'fastboot devices' without quotes
you will see your phone connected
Now to install type 'fastboot flash recovery recovery.img' withou quotes
now to reboot type 'fastboot reboot'
after phone starts to go into recovery type 'adb reboot recovery'
You will see the magic!
(*) Withouth PC/Laptop :
Open your existing recovery
navigate to the downloaded recovery file
selesct 'install image' option
selesct the recovery image and swipe to install for recovery
now reboot the recovery
And you will also see the magic
NOTE:
Check the 'use rm -rf instead of formatting' option in settings.
SCREENSHOTS: Attached!
DOWNLOADS:
Recovery :
Download From Mega! :good:
Download From AndroidFileHost!
SOURCE:
As The oem has not release the kernel source which is againt gpl that android follows.
So I have ported ROMs And Recoveries on top of prebuilt stock kernel.
Kernel
Contact For any help : Telegram Group
Credit : Me-U-I
Contributors : Yashraj22,TipzTeam,and all of you!
Version Info :
Status:Stable
Release Date:2020-05-20
Thank You!
Reserved!
Reserved Again!
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Installation
Download version .tar when you haven't a TWRP installed and you are coming from stock ROM and flash it via Odin in download mode. NOTE: Un-check Auto-reboot option in Odin, install tar file (it has to be placed in AP section) and after reboot manually in recovery mode with vol+, home and power buttons. This because otherwise you'll come back to stock recovery.
Download version .img when you have a TWRP installed. Simply, from home, go in install -> install image -> select your .img file -> press recovery as partition where you want to install it -> swipe to flash -> reboot system.
Download version .zip if you have an old TWRP. (you can install a .img or .zip file, as you want)
Bugs/Issues
Encryption with password isn't supported, so don't set the secure boot or put a password at the boot of the device
Download
kmini3g (SM-G800H): https://www.androidfilehost.com/?w=files&flid=319793 - mirror: https://t.me/tab4los
Source code
kmini3g: https://github.com/matteo0026/android_device_samsung_kmini3g
Kernel: https://github.com/matteo0026/android_kernel_samsung_msm8226
Contributors
matteo0026, isbon
Works great, thanks!
New build (-2) is out.
Changelog:
- Minor TWRP source changes (either recovery and device tree)
- Slightly reduced size of the package
New TWRP 3.5.0_9-0 is out.
Changelog:
- All TWRP 3.5.0_9 changes and improvements
- Some changes done in device tree to make it ordered and with less junk
- Persist and firmware (modem) partitions aren't backupable anymore. Firmware partition backup/restore/wipe with vfat partition makes network issues, and with emmc backups are useless since can't be restored successfully, and this "filesystem" isn't wipeable. Persist partition doesn't need any backups/wipes/restores, and if someone has some particular issues, it's always better to go to latest stock firmware, better with pit file too. I don't want to support anymore something that is half working.
- Try to fix time even in backups
Hi guys, new TWRP 3.5.0_9-1 is out!
Changelog:
- Get back persist partition backup, since it can be important to backed up, sometimes.
- Reintroduce su
New TWRP 3.5.1_9-0 is out!
Changelog:
- Changes coming from 3.5.1 version
New TWRP 3.5.2_9-0 is out!
Changelog:
- Changes coming from 3.5.2 version
Hi guys, new builds of TWRP are up. You can find the changelog of the TWRP 3.6.0 here: https://twrp.me/site/update/2021/11/28/twrp-3.6.0-released.html
TWRP 3.6.2_9-0 for kmini3g is out!
Changelog:
- https://twrp.me/site/update/2022/03/10/twrp-3.6.1-released.html
- https://twrp.me/site/update/2022/06/01/twrp-3.6.2-released.html
matteo0026 said:
TWRP 3.6.2_9-0 for kmini3g is out!
Click to expand...
Click to collapse
Where is it?
i5510 said:
Where is it?
Click to expand...
Click to collapse
Sorry, I forgot to put the mirror site. Now you can find it in the downloads section
matteo0026 said:
Sorry, I forgot to put the mirror site. Now you can find it in the downloads section
Click to expand...
Click to collapse
Thanks!
Some people don't use Telegram. Is there a particular reason why you don't upload it to https://www.androidfilehost.com/?w=files&flid=319793 ?
i5510 said:
Thanks!
Some people don't use Telegram. Is there a particular reason why you don't upload it to https://www.androidfilehost.com/?w=files&flid=319793 ?
Click to expand...
Click to collapse
Yesterday I've added on rush the link in the first post, and then I just forgot to upload them in AFH. Now they are uploaded on AFH too, hoping that it works fine.
Thank you.
Hi,
How do i know if my device has Encryption with password enabled ? I have a 800F here and would like to flash TWP.
Thanks in advance.
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 Poco F3/Mi 11X/Redmi K40
touch and adb work
flashing works
USB OTG works
Decryption is working
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
3. select the new image
4. after that is done, if you were using a custom kernel, reflash it now
5. if you were using magisk, reflash it now
Send me a beer: Crypto(Preferred) | PayPal
Trees:
https://github.com/TeamWin/android_device_xiaomi_alioth
https://github.com/TeamWin/android_device_xiaomi_sm8250-common
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomipocof3.html
Unofficial android 12 builds: https://www.pling.com/p/1836619/
mirror: https://store.kde.org/p/1836619/
Thanks for your hard work
All function has usable especially decryption.
Thank you mate!! That's is very important for all the community .What version of magisk i have to install??But you mean flash the zip of magisk??Thanks.
Awesome, mate!
I've been waiting for this, thank you sir for your contribution!
@Nebrassy Nice work - tested on my crDroid working-build and all ok
I only can say thank you a lot!! I'll buy a beer
"Failed to mount /data (Invalid argument) :/ Im on HentaiOS btw
reas0n said:
"Failed to mount /data (Invalid argument) :/ Im on HentaiOS btw
Click to expand...
Click to collapse
I believe that rom has customized encryption, so it's not supported
Nebrassy said:
I believe that rom has customized encryption, so it's not supported
Click to expand...
Click to collapse
Damn.. I will wait for any officially supported custom ROM then so I could just get OTAs, I dont want to do another wipe and setup lol. thx anyway
raystef66 said:
@Nebrassy Nice work - tested on my crDroid working-build and all ok
Click to expand...
Click to collapse
your what?
raystef66 said:
@Nebrassy Nice work - tested on my crDroid working-build and all ok
Click to expand...
Click to collapse
Not shared as yet?
arifqur said:
Not shared as yet?
Click to expand...
Click to collapse
Not yet. Won't take long though when first release will be posted in development.
this works "out of the box" for poco f3 with miui 12.x?
Thank you
Henkl said:
this works "out of the box" for poco f3 with miui 12.x?
Click to expand...
Click to collapse
answering my own question: you have to unlock the phone first with MIUI unlock tool.
AND unlocking involves wiating on part of xiaomi site afer registering ...can be even 7 days..
Hello I am not sure I didn't mess around with the job !!
Firstly, I have copied the twrp image on my device but the twrp didn't see it, so I have plugged an otg device with the file on it.
Now twrp is installed but it can't decrypt data (ask for password)
What is wrong pls ?
Secondly, when I have solved that, could I backup the boot.img with Twrp to be then patched with the Magisk installer app ?
Is it the best way to have Magisk on my device ?
Thanks !
lejeanlouisF said:
Hello I am not sure I didn't mess around with the job !!
Firstly, I have copied the twrp image on my device but the twrp didn't see it, so I have plugged an otg device with the file on it.
Now twrp is installed but it can't decrypt data (ask for password)
What is wrong pls ?
Secondly, when I have solved that, could I backup the boot.img with Twrp to be then patched with the Magisk installer app ?
Is it the best way to have Magisk on my device ?
Thanks !
Click to expand...
Click to collapse
So it asked for password, did you enter it?
As for magisk, just flash latest magisk apk with twrp
lejeanlouisF said:
Hello I am not sure I didn't mess around with the job !!
Firstly, I have copied the twrp image on my device but the twrp didn't see it, so I have plugged an otg device with the file on it.
Now twrp is installed but it can't decrypt data (ask for password)
What is wrong pls ?
Secondly, when I have solved that, could I backup the boot.img with Twrp to be then patched with the Magisk installer app ?
Is it the best way to have Magisk on my device ?
Thanks !
Click to expand...
Click to collapse
The password is ur security PIN for unlocking ur phone.
No idea about backuping the boot.img in TWRP (I am not using it )
Nebrassy said:
So it asked for password, did you enter it?
As for magisk, just flash latest magisk apk with twrp
Click to expand...
Click to collapse
I have entered a password but it failed. Is it a free password ?
EDIT : It's ok, sorry. the security PIN, of course !!!
EDIT 2 : And Thank you very much for your work and your help
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about doing this to your device
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
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, with 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.
This is for OFFICIAL and BETA builds of TWRP for the Asus Zenfone 5z (Z01RD, zs620kl)
Device Config:
https://github.com/TeamWin/android_device_asus_Z01RD
Stable Downloads:
ASUS ZenFone 5z 2018
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
Test Downloads:
Download File List - twrp-for-z01r - OSDN
Download File List - twrp-for-z01r #osdn
osdn.net
Installation:
Backup everything important off of your device
Make sure your bootloader is unlocked
Download the recovery image (and optionally the TWRP installer zip) from above
Reboot into bootloader
Run this command (Change the .img to whatever the name of the file is you downloaded):
Code:
fastboot flash boot twrp-3.5.2_10-1-Z01RD.img
NOTE, If you're coming from stock ROM to custom ROM? You MUST format data (wiping data won't work) to remove stock ROM encryption. Wipe > "Format Data" Button > Type "yes" > Keyboard checkbox
(Optional instructions from this point on) Wipe cache and system and then Install the ROM of your choice
Install TWRP installer zip
Reboot to recovery
Install GApps
Reboot to system
Upgrade / Reinstall TWRP instructions
Download desired TWRP installer zip version
Reboot to recovery
Select Install
Tap on install and select the TWRP installer zip you downloaded from step one
Reboot to recovery and confirm that the updated version of TWRP is installed
Nandroid backup/restore
Have an available microSD Card or USB OTG drive
Backup boot, dtbo, system image, vendor image and data (optionally any other partitions you want a backup of) to your external storage device of choice
Once you wish to restore? Reboot to TWRP and format data (Wipe > "format data" button > type yes > keyboard checkbox)
Reboot to TWRP
Restore boot, dtbo, system image and vendor image
Reboot to system
Once it boots to the system without issues? Do not set any lockscreen security and reboot to TWRP
Restore data
Reboot to system
After it finishes boot? Your data and ROM will be restored but sometimes the UI might be incorrect, so reboot to the system again
For the TEST builds of TWRP? Please let me know if this works. If so? I will submit it to Gerrit for official updates.
Credits:
bigbiff for helping me get set up on gerrit.twrp.me for official status and updating official TWRP
JackEage for working on TWRP for this device
All the users who tested my builds of TWRP
Anyone who worked on the open-source kernel of this device
So the next build of official TWRP for Z01RD will include vendor wiping since it seems that the modified prebuilt vendor image flashing can sometimes break the vendor partition for future flashing.
Z01RD: Enable vendor wipe · TeamWin/[email protected]
It seems that users flashing a modified prebuilt vendor runs the risk of corrupting their vendor partition, so against my better judgement as normally there is zero reason we should ever need to do...
github.com
ThE_MarD said:
Installation:
Make sure your bootloader is unlocked
Download the recovery image (and optionally the TWRP installer zip) from above
Reboot into bootloader
Run this command (Change the .img to whatever the name of the file is you downloaded):
Code:
fastboot flash boot twrp-3.5.2_10-1-Z01RD.img
(Optional instructions from this point on) Install ROM of choice
Install TWRP installer zip
Reboot to recovery
Install GApps
Reboot to system
Click to expand...
Click to collapse
I did steps 1-4 in an unlocked bootloader zenfone 5z. After flashing TWRP, my phone is stuck in either TWRP or fastboot; and TWRP can't mount any storage so adb loading firmware isn't possible.
Is there a way to recover from this?
Phone can only receive fasboot commands and TWRP non storage commands
Heyyo @fastrespawn , you will need to format data in TWRP as stock ROM uses Full Disk Encryption and on custom ROMs like LineageOS we use the newer File-Based Encryption.
Wipe > "Format Data" Button > Type "yes" > Keyboard checkbox
Then wipe Cache and system and reboot to recovery and you're ready to flash a custom ROM.
I've expanded the instructions to mention this
ThE_MarD said:
Heyyo @fastrespawn , you will need to format data in TWRP as stock ROM uses Full Disk Encryption and on custom ROMs like LineageOS we use the newer File-Based Encryption.
Wipe > "Format Data" Button > Type "yes" > Keyboard checkbox
Then wipe Cache and system and reboot to recovery and you're ready to flash a custom ROM.
I've expanded the instructions to mention this
Click to expand...
Click to collapse
Thank you!
After flashing twrp-installer-3.5.2_10-1-Z01RD.zip, I cannot touch my screen in twrp. What should I do?
Heyyo @JuanTamqd21 , there is a bug in the touchscreen firmware updater in the kernel, so on LineageOS tbh I just disabled it as I've heard zero touchscreen complaints from any Z01R user that came to LOS from ZenUI Q .123 build as that is the last device firmware for Z01R. You can try rebooting to TWRP again or wait a few minutes then tap the power button a few times and sometimes that will get the touchscreen working. Otherwise? Ask the maintainer of that ROM to also do the same thing I did.
https://review.lineageos.org/c/LineageOS/android_kernel_asus_sdm845/+/312874
ThE_MarD said:
Heyyo @JuanTamqd21 , there is a bug in the touchscreen firmware updater in the kernel, so on LineageOS tbh I just disabled it as I've heard zero touchscreen complaints from any Z01R user that came to LOS from ZenUI Q .123 build as that is the last device firmware for Z01R. You can try rebooting to TWRP again or wait a few minutes then tap the power button a few times and sometimes that will get the touchscreen working. Otherwise? Ask the maintainer of that ROM to also do the same thing I did.
https://review.lineageos.org/c/LineageOS/android_kernel_asus_sdm845/+/312874
Click to expand...
Click to collapse
thanks for the guide. I will try it now
Heyyo, a new test build is up! twrp-3.6.0_11.0-Z01RD-test17-UNOFFICIAL contains the upgrade to TWRP 11 branch and also added in system/vendor wiping as I keep getting nagged about this useless feature lol oh well...
Release twrp-10 twrp-3.6.0_11.0-Z01RD-test17-UNOFFICIAL - twrp-for-z01r - OSDN
Release twrp-10 twrp-3.6.0_11.0-Z01RD-test17-UNOFFICIAL - twrp-for-z01r #osdn
osdn.net
twrp-3.6.0_11.0-Z01RD-test18-UNOFFICIAL is up! Contains fixes for the Boot Control HAL so that flashing ROM images will work correctly and properly switch to inactive partition upon reboot plus the decryption and other updates from test17
Release twrp-for-z01r twrp-3.6.0_11.0-Z01RD-test18-UNOFFICIAL - twrp-for-z01r - OSDN
Release twrp-for-z01r twrp-3.6.0_11.0-Z01RD-test18-UNOFFICIAL - twrp-for-z01r #osdn
osdn.net
Hii
Heyyo, a new test build is up! twrp-3.7.0_12-0_UNOFFICIAL-20230222-01-Z01RD contains a bootctrl hal fix
Release twrp-for-z01r twrp-3.7.0_12-0_UNOFFICIAL-20230222-01-Z01RD - twrp-for-z01r - OSDN
Release twrp-for-z01r twrp-3.7.0_12-0_UNOFFICIAL-20230222-01-Z01RD - twrp-for-z01r #osdn
osdn.net
Official TWRP for the Asus Zenfone 5z has been updated with the bootctrl HAL fix!