Database Develop

[RECOVERY][victara] TWRP 3.1.1-0 touch recovery [2017-05-19]

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.2-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
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!
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.
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.

Note, at this point, I haven't tried to mess around with kernel source. The recovery image barely fits with the stock kernel and dtb. The bootloader will refuse to flash the recovery via fastboot flash command so you have to boot the recovery then use dd to flash it. Instructions and download links are on our website:
Mirror
We only tested this on XT1095 but it will likely work on other models. Back up your stock recovery first and use fastboot boot to test the image on other models before flashing.
Touch may be a bit finicky especially when trying to swipe the sliders to confirm actions.

First to post very cool.
@Dees_Troy
But any ways the recovery flashes just fine but you cant do a back up every time I try it fails I get
E:unable to create folder: /data/media/0/twrp(errno=13)
E:Failed to make backup folder
Also swiping left to right to unlock or even start the backup doesn't really work you have to keep trying over and over
also im running the pure edition if that helps any
Thanks look forward to the next test

Victara doesn't yet come up under the device names.

ewalk4866 said:
First to post very cool.
@Dees_Troy
But any ways the recovery flashes just fine but you cant do a back up every time I try it fails I get
E:unable to create folder: /data/media/0/twrp(errno=13)
E:Failed to make backup folder
Also swiping left to right to unlock or even start the backup doesn't really work you have to keep trying over and over
also im running the pure edition if that helps any
Thanks look forward to the next test
Click to expand...
Click to collapse
i'm experiencing the same behavior; don't know if this makes a difference but i'm booting into TWRP via fastboot. @Dees_Troy thanks for your time/efforts creating this recovery image. :good:

Dees_Troy said:
Note, at this point, I haven't tried to mess around with kernel source. The recovery image barely fits with the stock kernel and dtb. The bootloader will refuse to flash the recovery via fastboot flash command so you have to boot the recovery then use dd to flash it. Instructions and download links are on our website:
Mirror
We only tested this on XT1095 but it will likely work on other models. Back up your stock recovery first and use fastboot boot to test the image on other models before flashing.
Click to expand...
Click to collapse
Was able to boot and flash via fastboot as well as dd it. On all occasions I'm also experiencing no functionality. Loads up fine but nothing works

ZeroAlphawolf said:
Victara doesn't yet come up under the device names.
Click to expand...
Click to collapse
I dont see it either. I assume something that will come eventually.

I tested a little bit on XT1095 using "fastboot boot openrecovery-twrp-2.8.0.0-victara.img" command (did not flashed it yet). Did not checked all menu items but looks like menus works fine.
The same error trying to make backup:
E:unable to create folder: /data/media/0/TWRP (errno=13)
E:Failed to make backup folder

Ability to run backups should be fixed now.

Version 2.8.0.1 works perfectly on XT1097 (Brazilian Version)
Thanks so much !!!
{
"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"
}

Thank you Dees_Troy,
Now that you've made it possible to back things up custom ROM's can't be to far away. And by the way the theming is working perfectly as well.

Interesting, so this morning i opened Twrp and found that Victara is now listed, which is great, and downloaded the recovery that way, which gave me 2.8.0.0 which is no problem. It installed it in active Android, and i opened up to it. Even managed to back up, with no problems, on 2.8.0.0, to an OTG drive, which let me tell you is amazing since i had such issues with that on Nexus 5. Thanks for your guys hard work, i always stick with Twrp.

I'm still having issues with slide not working on 2.8.0.1. I was able to back up in twrp app though

bacup directly to computer 2.8.0.1 Victara?
If I boot the openrecovery twrp image via fastboot, can I back up directly to my computer? I have the 16GB pure edition with only 3 GB remaining storage, prior to backup attempt, which is not enough to backup to the device memory. I tried selecting OTG, but couldn't select it. Perhaps I have to install the recovery to the device, plug in a usb otg, then attempt backup to otg?
Im trying to avoid installing the recovery image, because there is no factory system image available from Motorola yet.

I don't think you will be able to properly use any of twrp without installing it as the recovery itself, permission issues. But i believe there is a tool up already that has a copy of the customer recovery with it, if you needed to revert.

Thank you Dees_Troy for this amazing work. There is a bug i noticed and i dont know whats causing it.... After i booted (not flashed) the recovery, i made a full backup.. Then when i hooked the phone thru usb to copy my backup to the computer.. i noticed that the backup folder was empty in the windows explorer window... and then i came up with these findings thru (root explorer app): /storage/emulated/0/twrp (empty) but /data/media/0/twrp has the backup and thats why it isnt showing in windows...
So how do i get the backup show in /storage/emulated/0/twrp???
Thank u again....

The backup should be in data/ media/ 0

yay! thank you for your work and getting twrp to the new moto x!

Great ...waiting for millions roms now...

Just tested on my XT1097 Retail Brazil to flash Cerberus into the system.
I used "fastboot boot" command and it worked like a charm. Thank you for this

[OFFICIAL][TWRP][d5110] TWRP for Infinix Hot 2

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.
{
"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"
}
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
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.
DOWNLOADS
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:
TWRP for Infinix Hot 2
Credits
@MSF Jarvis
@Nonta72
@Dees_troy
@jcadduono
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.
XDA:DevDB Information
[OFFICIAL][TWRP][d5110] TeamWin Touch Recovery, Tool/Utility for the Infinix HOT 2
Contributors
HostZero, MSF Jarvis, Dees_troy
Source Code: https://github.com/TeamWin/android_device_infinix_d5110
Version Information
Status: Stable
Created 2016-06-08
Last Updated 2016-06-08

Reserved

How to back to stock recovery ?

0utc0ntr0l said:
How to back to stock recovery ?
Click to expand...
Click to collapse
Download STOCK recovery and flash it using TWRP.

Thank You So Much For Your Effort And I Have A Problem When I Used The Method That You've Written To Install The Recovery When I Entered To My Recovery And Tap INSTALL And Then Selected INSTALL IMAGE And I Selected The Recovery Image It Appears To Me The Only Partition That I Can Flash It To It Is The BOOT Partition

youssef0789 said:
Thank You So Much For Your Effort And I Have A Problem When I Used The Method That You've Written To Install The Recovery When I Entered To My Recovery And Tap INSTALL And Then Selected INSTALL IMAGE And I Selected The Recovery Image It Appears To Me The Only Partition That I Can Flash It To It Is The BOOT Partition
Click to expand...
Click to collapse
Thankyou I will work on patch soon.

youssef0789 said:
Thank You So Much For Your Effort And I Have A Problem When I Used The Method That You've Written To Install The Recovery When I Entered To My Recovery And Tap INSTALL And Then Selected INSTALL IMAGE And I Selected The Recovery Image It Appears To Me The Only Partition That I Can Flash It To It Is The BOOT Partition
Click to expand...
Click to collapse
It seems like you are using twrp by jemmini.
You can flash it with flashify/rashr or any flashing app.
Or via terminal
Code:
dd if=PATH_TO_DOWNLOADED_FILE of=/dev/block/platform/mtk-msdc.0/by-name/recovery
This might different on android one rom.
Since jemmini's TWRP is only can flash boot images

RendyAK said:
It seems like you are using twrp by jemmini.
You can flash it with flashify/rashr or any flashing app.
Or via terminal
Code:
dd if=PATH_TO_DOWNLOADED_FILE of=/dev/block/platform/mtk-msdc.0/by-name/recovery
This might different on android one rom.
Since jemmini's TWRP is only can flash boot images
Click to expand...
Click to collapse
Thank You So Much I'll Give It A Try But I Tried To Flash It With This Method
1 . Download the latest image file (.img) from the download link above and rename it to twrp.img, then copy it into the same folder as the factory ROM.
2 . Open up the MTK Flash Tool and use the scatter loading button to select the scatter file for this device.
3 . Uncheck all partition boxes except for the RECOVERY partition.
4 . Click on the folder/filename path for RECOVERY, then browse to and select the twrp.img file.
5 . Click on the [Download] button in the MTK Flash Tool.
6 . Power off your device completely.
7 . Plug the device into the computer and wait for it to flash. If it fails to flash the first time, you may have to unplug the phone and click [Download] again. Try this a few times. If it still doesn't work, try a different USB port and USB cable.
And When I Flashed It It Was Successfully Installed But There Was A Problem It Doesn't Show My SD Card

youssef0789 said:
It seems like you are using twrp by jemmini.
You can flash it with flashify/rashr or any flashing app.
Or via terminal
Thank You So Much I'll Give It A Try But I Tried To Flash It With This Method
1 . Download the latest image file (.img) from the download link above and rename it to twrp.img, then copy it into the same folder as the factory ROM.
2 . Open up the MTK Flash Tool and use the scatter loading button to select the scatter file for this device.
3 . Uncheck all partition boxes except for the RECOVERY partition.
4 . Click on the folder/filename path for RECOVERY, then browse to and select the twrp.img file.
5 . Click on the [Download] button in the MTK Flash Tool.
6 . Power off your device completely.
7 . Plug the device into the computer and wait for it to flash. If it fails to flash the first time, you may have to unplug the phone and click [Download] again. Try this a few times. If it still doesn't work, try a different USB port and USB cable.
And When I Flashed It It Was Successfully Installed But There Was A Problem It Doesn't Show My SD Card
Click to expand...
Click to collapse
Yeah, that is the bug of this twrp :3 @HostZero

RendyAK said:
Yeah, that is the bug of this twrp :3 @HostZero
Click to expand...
Click to collapse
Sir,
If your not aware I had been doing testing series for TWRP for d5110 successfully i have compiled and people were like no issues, so i went up publishing and Recovery Partition Flashing! I am trying to work on patch. if possible can you provide me the mmc* partition list. (ex: mmcb500...) I need those for boot and recovery, so i will make stable.
- HostZero

HostZero said:
Sir,
If your not aware I had been doing testing series for TWRP for d5110 successfully i have compiled and people were like no issues, so i went up publishing and Recovery Partition Flashing! I am trying to work on patch. if possible can you provide me the mmc* partition list. (ex: mmcb500...) I need those for boot and recovery, so i will make stable.
- HostZero
Click to expand...
Click to collapse
Here it is.
From /proc/emmc on Infinix 5.1 Rom.
The sdcard partition should be the same with android one rom.

RendyAK said:
Here it is.
From /proc/emmc on Infinix 5.1 Rom.
The sdcard partition should be the same with android one rom.
Click to expand...
Click to collapse
Please do this
adb devices
su (root using TWRP or any other way)
ls -al /dev/block/platform/mtk-msdc.0/by-name
Now copy the partition table and try to give me.
This will provide the mmc/infinix partition table.
- HostZero

HostZero said:
Please do this
adb devices
su (root using TWRP or any other way)
ls -al /dev/block/platform/mtk-msdc.0/by-name
Now copy the partition table and try to give me.
This will provide the mmc/infinix partition table.
- HostZero
Click to expand...
Click to collapse
This can be do with Terminal tho :3

RendyAK said:
This can be do with Terminal tho :3
Click to expand...
Click to collapse
Thankyou I will enter new table and most probably 3.0.2-1 or wait for 3.0.3-0.
- HostZero

I would like to report several issues:
1. NVRAM should've mounted as emmc, not ext4 (there's error in the log), also you should make secro as a sub partition of nvram. In my previous encounter with mediatek, if your secro partition corrupted or missing, your IMEI will still not detected (or detected partially).
2. There's no micro SD card mount point, despite the card is detected. Why?
I decompiled the official image, make necessary edit, and recompiled again. Tested fine on my brother's hot 2.
Download here if you want.

awaaas said:
I would like to report several issues:
1. NVRAM should've mounted as emmc, not ext4 (there's error in the log), also you should make secro as a sub partition of nvram. In my previous encounter with mediatek, if your secro partition corrupted or missing, your IMEI will still not detected (or detected partially).
2. There's no micro SD card mount point, despite the card is detected. Why?
I decompiled the official image, make necessary edit, and recompiled again. Tested fine on my brother's hot 2.
Download here if you want.
Click to expand...
Click to collapse
Fixed All of Them:
https://gerrit.twrp.me/1640
- HostZero

HostZero said:
Fixed All of Them:
https://gerrit.twrp.me/1640
- HostZero
Click to expand...
Click to collapse
Why would you create a fix when it's already fixed? I submitted that like half a month ago dude...
https://gerrit.twrp.me/#/c/1598/
https://gerrit.twrp.me/#/c/1597/
You approved my changes then on gerrit. Why did you do this?

awaaas said:
Why would you create a fix when it's already fixed? I submitted that like half a month ago dude...
https://gerrit.twrp.me/#/c/1598/
https://gerrit.twrp.me/#/c/1597/
You approved my changes then on gerrit. Why did you do this?
Click to expand...
Click to collapse
Bro! I don't remember if I approved. Anyways your changes were not pushed to git. My changes are pushed & I have even got
CPU Temperature for this.
Logo Backup and OEM backup and few other changes which would make twrp more stable.

HostZero said:
Bro! I don't remember if I approved. Anyways your changes were not pushed to git. My changes are pushed & I have even got
CPU Temperature for this.
Logo Backup and OEM backup and few other changes which would make twrp more stable.
Click to expand...
Click to collapse
You +1'd my changes on gerrit. And it IS pushed to github, you can check the commits of mine in TWRP device tree, it is pushed on June 19th.
https://github.com/TeamWin/android_device_infinix_d5110/commits/android-5.1
While it is good you added more partition to backup (note: IIRC, oem partition is not used by infinix) and cpu temp, I only complained about my changes duplicated by you, and that you claimed it.
Anyways, please don't make a duplicate fix in the future

CPU TEMPRATURE, Theres a Fix That i discovered.
and OEM partition is there for d5110 as per me.
I have duplicated on NVRAM etc all are new.

[RECOVERY][ham] TWRP 3.1.0-0 touch recovery [2017-03-12]

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.
{
"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"
}
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
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!
DOWNLOAD:
1) Download the latest version from here: https://forum.xda-developers.com/devdb/project/dl/?id=23595&task=get
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.
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.

Everything should work fine and F2FS support is also included.

Can we use aroma gapps too

Finally recovery update for our device
Thanks for u hard work

Million thanks @ OrdenKrieger for all your hard work to our device up to date and alive.
Thanks OrdenKrieger.

Awesome!!! You're always on top of the wave. Thanks.
Sent from my Nuclear OnePlus3T

Really appreciate your efforts thanks.

Thanks for a New update
Enviado desde mi ZUK Z1

Hmm, the new version is not able to decrypt my data partition anymore. It always sais wrong password :crying:

Thank you so much for your work. TWRP is always an important part of our devices.

Hey there the recovery works fine only aroma support is missing...... I mean it just reboots after flashing aroma arise sound mod or gapps.

OrdenKrieger said:
3.1.0-0
Click to expand...
Click to collapse
Hello.
LineageOS 14.1-20170404
Enabled data encryption.
TWRP asks for the input of the pattern for decryption, but gives an error. The graphics key is entered correctly.

Yagurtov said:
Hello.
LineageOS 14.1-20170404
Enabled data encryption.
TWRP asks for the input of the pattern for decryption, but gives an error. The graphics key is entered correctly.
Click to expand...
Click to collapse
You can try my TWRP 3.0.2 Version from https://forum.xda-developers.com/showpost.php?p=68245349. It's working for me, though I don't know how a pattern might be translated to a password. I couldn't find the time to port these changes over to 3.1.0. Or even get them over into the official TWRP.

btme said:
You can try my TWRP 3.0.2 Version from https://forum.xda-developers.com/showpost.php?p=68245349. It's working for me, though I don't know how a pattern might be translated to a password. I couldn't find the time to port these changes over to 3.1.0. Or even get them over into the official TWRP.
Click to expand...
Click to collapse
Thanks, it works

[RECOVERY][3.4.0-14][monet]TWRP Xiaomi Mi 10 Lite 5G

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.
*
*/
Features:
- Decryption works
- Otg works
- Flash Rom works
- F2FS support
- Fastboot boot command support
Not working:
- Fastbootd
- Adb sideload
- Backup restore and image flash (system-vendor-product)
- Android 11 fully support
Download:
TWRP 3.4.0-14 Unofficial by mauronofrio
TWRP 3.4.0-12 Unofficial by mauronofrio
To Flash the TWRP:
Code:
fastboot flash recovery twrp-3.3.1-xx-xxxxxx-mauronofrio.img
Then reboot in TWRP manually or using a fastboot command.
Code:
fastboot boot twrp-3.3.1-xx-xxxxxx-mauronofrio.img
or
Code:
fastboot oem reboot-recovery
REMEMBER: is important that from fastboot you directly go in TWRP mode or the TWRP will be overwritten.
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/Teamwin/android_bootable_recovery
https://github.com/mauronofrio/android_device_xiaomi_monet
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
- Thanks to @bigbiff and @Captain_Throwback for the hard work on this android 10 TWRP
Thanks to all testers on the Telegram Group
Created 2020-09-23

txt

great job

Good job, Mauro!
We Need it

TWRP 3.4.0-14 for Xiaomi Mi 10 Lite 5G (monet):
- Fixed decryption request also when the device is not encrypted.
TWRP 3.4.0-14 Unofficial by mauronofrio

Very nice, great to see some progress here on this device.
Now we only need some custom roms which we could flash

Nice one

Edited as it contained profanity. Please avoid using profanity. Others have not reported the issue you experienced. If you have any issues with said TWRP kindly post asking for support so someone can help troubleshoot the issue.

Has anyone else had any problems with this twrp? I have to choose between this and pitch black and I would like suggestions.
Sent from my [device_name] using XDA-Developers Legacy app

thanks man

Faced issues while installing Migrate GPE 3.1.1 based backups.
Is/was anyone successful in flashing Migrate GPE based backups?
Tested TWRPs:
PitchBlack Recovery v3.0 - 03102020
TWRP 3.4.0-14 Unofficial by mauronofrio
Used ROMs:
miui_MONETEEAGlobal_V12.0.2.0.QJIEUXM_12bc504f22_10.0
xiaomi.eu_multi_MI10LITE5G_V12.0.1.0.QJIMIXM_v12-10
Here is some log output:
Code:
---------------------------------
Migrate-GPE Flash package
Version 3.1.1 - release
---------------------------------
*** Extras ***
---------------------------------
minzip: Extracted 3 file(s)
Mounting partition...
about to run program [/tmp/mount_script.sh] with 3 args
DEBUG:: --- making config dir (/tmp/manualConfigs) if does not exist ---
Debug:: SAR device!
DEBUG:: --- fstab ---
/dev/block/dm-0 /system_root ext4 ro 0 0
/dev/block/dm-2 /vendor ext4 ro 0 0
/dev/block/dm-1 /product ext4 ro 0 0
/dev/block/dm-3 /odm ext4 ro 0 0
/dev/block/sda18 /metadata ext4 rw 0 0
/dev/block/sda34 /data f2fs rw 0 0
/dev/block/sda30 /cache ext4 rw 0 0
/dev/block/sde48 /firmware vfat rw 0 0
/dev/block/sda23 /persist ext4 rw 0 0
/dev/block/sda32 /cust ext4 rw 0 0
/usb_otg vfat rw 0 0
DEBUG:: --- end of fstab ---
Debug:: mount /system_root
Debug:: Directly internal toybox/busybox
Debug:: mount /data
Debug:: Directly internal toybox/busybox
mount: '/dev/block/sda34'->'/data': Device or resource busy
Debug:: Creating Test file
matches was 2 on <</dev/block/sda34 /data>>
script aborted: Mount failed data! Exiting...
Mount failed data! Exiting...
Updater process ended with ERROR: 7
An assert failed. Please check the output above for more details.
Updating partition details...
I:Data backup size is 3277MB, free: 98337MB.
...done
Error installing zip file '/sdcard/Migrate/Backup_2020.10.21_23.45.24/Extras.zip'
Updating partition details...
I:Data backup size is 3277MB, free: 98337MB.
...done

Can it flash Xiaomi.EU?
because at "Not Working" stands "[...] and image flash [...]"
Does anyone got Xiaomi.EU Rom to work as expected?
Is something else worth to know before doing this?

zShadowStorm said:
Is something else worth to know before doing this?
Click to expand...
Click to collapse
In twrp-3.4.0-14-monet-mauronofrio, I had issues copying the ROM file from PC onto the device using MTP. After several not successful attempts, I used an OTG USB Stick (has USB-A *and* USB-C connector), to flash the ROM file with twrp directly from the stick. Maybe PC W10 driver issues, I did not dig any further into this.
xiaomi.eu_multi_MI10LITE5G_V12.0.2.0.QJIMIXM_v12-10.zip ROM flash with this twrp went fine, MTP after device setup, too. But I go back to stock EUXM because the Play Store is not certified, as followup no Gpay working - open bootloader causes this *and* I don't want root etc. to fix these things.
But good work, thanks to @mauronofrio

After you flash the recovery you have to flash the vbmeta partition too, in order to be able to have working internal storage after format!
That how I do it

sardelisp said:
After you flash the recovery you have to flash the vbmeta partition too, in order to be able to have working internal storage after format!
That how I do it
Click to expand...
Click to collapse
How to do that? After i flash a rom it get stucked on a bootloop.

Thank you!
HI! I just managed to flash xiaomi.eu_multi_MI10LITE5G_V12.0.2.0.QJIMIXM_v12-10 rom to my Mi 10 Lite 5G Monet.
CAMERA is ok! All 4 cameras seem to be working fine.
Messages app is ok
Dial app is functional, the only bug I found so far is that in Dark mode, if I search for a contact, a white background is forced over the black one and makes the text invisible (the font is white due to dark mode) and only the typed letters are visible.
I have used Minimal+adb_fastboot_platform-tools_r29.0.6_2020 to flash twrp-3.4.0-14-monet-mauronofrio, I wiped using the standard slide, then I installed xiaomi.eu_multi_MI10LITE5G_V12.0.2.0.QJIMIXM_v12-10.
A huge thank you to everybody who's contributing!
Good luck!

LuciPanuci said:
HI! I just managed to flash xiaomi.eu_multi_MI10LITE5G_V12.0.2.0.QJIMIXM_v12-10 rom to my Mi 10 Lite 5G Monet.
CAMERA is ok! All 4 cameras seem to be working fine.
Messages app is ok
Dial app is functional, the only bug I found so far is that in Dark mode, if I search for a contact, a white background is forced over the black one and makes the text invisible (the font is white due to dark mode) and only the typed letters are visible.
I have used Minimal+adb_fastboot_platform-tools_r29.0.6_2020 to flash twrp-3.4.0-14-monet-mauronofrio, I wiped using the standard slide, then I installed xiaomi.eu_multi_MI10LITE5G_V12.0.2.0.QJIMIXM_v12-10.
A huge thank you to everybody who's contributing!
Good luck!
Click to expand...
Click to collapse
Thanks for update in this twrp and xiaomi.eu rom.
Can I ask you to confirm this in the eu rom:
# In themes app, can you export 3rd party themes. In the oficial global EU rom, this option is not there.
# In homen screen layout can you choose other than 4x6 5x6
# has it got miui dialer instaid of the google one
# has it got double tap to swich off on home screen. In the global one has double tap only to wake, and swich off in lockscreen.
Many thanks
Sent from my MI PAD 4 using Tapatalk

limonet said:
Thanks for update in this twrp and xiaomi.eu rom.
Can I ask you to confirm this in the eu rom:
# In themes app, can you export 3rd party themes. In the oficial global EU rom, this option is not there.
# In homen screen layout can you choose other than 4x6 5x6
# has it got miui dialer instaid of the google one
# has it got double tap to swich off on home screen. In the global one has double tap only to wake, and swich off in lockscreen.
Many thanks
Sent from my MI PAD 4 using Tapatalk
Click to expand...
Click to collapse
Now that i have the xiaomi.eu installed, I response to my own questions.
#1 yes
#2 yes
#3 yes
#4 yes
Sent from my MI PAD 4 using Tapatalk

İnstalled twrp but couldn't have the root access even flashed successfully anyone could do it ?

setheleh said:
İnstalled twrp but couldn't have the root access even flashed successfully anyone could do it ?
Click to expand...
Click to collapse
Twrp version 14, eu v 12.0.2.0, no problem installing root, works just fine with this versions .
Did nothing special to install rom or magisk.
{
"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"
}

Development [RECOVERY] [11] [star/mars] [OFFICIAL] 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. 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 Pro/Ultra
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_star
https://github.com/TeamWin/android_device_xiaomi_mars
https://github.com/TeamWin/android_device_xiaomi_sm8350-common
Telegram group: https://t.me/NSSFB
Download:
star: https://twrp.me/xiaomi/xiaomimi11ultra.html
mars: https://twrp.me/xiaomi/xiaomimi11pro.html

Wow
Finally, official TWRP for our device, thanks alot to dev

when i flash it ,i can`t mount my /data
my device is mi 11 star

347111268 said:
when i flash it ,i can`t mount my /data
my device is mi 11 star
Click to expand...
Click to collapse
Are you on android 12?

Nebrassy said:
Are you on android 12?
Click to expand...
Click to collapse
yes

347111268 said:
when i flash it ,i can`t mount my /data
my device is mi 11 star
Click to expand...
Click to collapse
on android 11 the same......

Edlar said:
on android 11 the same......
Click to expand...
Click to collapse
Send logs
adb pull /tmp/recovery.log
adb logcat > logcat.txt

Nebrassy said:
Send logs
adb pull /tmp/recovery.log
adb logcat > logcat.txt
Click to expand...
Click to collapse
Hi there !
Can't mount /data neither Mi 11 Star on A12 (latest weekly EU Rom), removed password before fastboot boot twrp.img
Tried to adb pull /tmp/recovery.log, but :
adb: error: failed to get feature set: no devices/emulator found
you do this on fastboot mode, right ?
Thank you

jiyuugataki said:
Hi there !
Can't mount /data neither Mi 11 Star on A12 (latest weekly EU Rom), removed password before fastboot boot twrp.img
Tried to adb pull /tmp/recovery.log, but :
adb: error: failed to get feature set: no devices/emulator found
you do this on fastboot mode, right ?
Thank you
Click to expand...
Click to collapse
did you try if its connected by typing fastboot devices?

jiyuugataki said:
Hi there !
Can't mount /data neither Mi 11 Star on A12 (latest weekly EU Rom), removed password before fastboot boot twrp.img
Tried to adb pull /tmp/recovery.log, but :
adb: error: failed to get feature set: no devices/emulator found
you do this on fastboot mode, right ?
Thank you
Click to expand...
Click to collapse
Try going to mount menu, disable mtp and enable it, then check id adb is recognized

Nebrassy said:
Try going to mount menu, disable mtp and enable it, then check id adb is recognized
Click to expand...
Click to collapse
Worked, here are the logs
Thx !
Edit : That's strange, when i try to attach files, they upload and then disappear when i save
so, recovery :
recovery.log - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
logcat part1 : https://pastebin.com/ZPenY56E
part 2 : https://pastebin.com/6MYkJs5R

marcel112 said:
did you try if its connected by typing fastboot devices?
Click to expand...
Click to collapse
Tried and no problem
But, solved, thank you nonetheless

Hello everyone, I can't access to my data in TWRP completely because I want to flash magisk; any solution?

datadelrey said:
Hello everyone, I can't access to my data in TWRP completely because I want to flash magisk; any solution?
Click to expand...
Click to collapse
did you remove password or pin?

Great news!
I am wondering if there is a roadmap when TWRP will be available for A12?

{
"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"
}
Everything is fine, a log file appeared after I backed up the boot, I hope it's useful

please make a clear tutorial on how to fix the unable to mount/data
i removed the pin and password before fastboot boot twrp.img, go to advanced flash current twrp, and when i restart the device it goes to fastboot again.

Nebrassy said:
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
Click to expand...
Click to collapse
How to update if we are currently use a different TWRP? I mean not "official".

Mi 11 Ultra / star
Using EU 12.5.20 and twrp 3.5.1
Update to 3.6.0 via Install Zip in 3.5.1
Reflash EU rom after update twrp and booted normally now.
Working fine. Thank you.

@hacker738 and now check, which version of TWRP is installed
if 3.6.0 then I'll really congratulate you