Develop Bugs

[RECOVERY][d2spr] 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.

First!
Thank you!!

Nice!! Thanks guys!

Great work guys!

Thanks looks awesome!
Sent from my SPH-L710 using xda app-developers app

Great work
Sent from my SPH-D710 using Tapatalk 2

In know both do the same but is this better than cwm.
Sent from my SPH-L710 using Tapatalk 2

eduardmc said:
In know both do the same but is this better than cwm.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Yes it is. It has more features and the interface is better for accessibility. It also has themes. You can also rename your backups within the recovery.
Key Features:
Ability to save custom recovery settings
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)
What's new in 2.2.0:
On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
Name new backups and rename existing backups
Rename files and folders in the file manager
Pseudo-terminal emulator
Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
Simplified XML layout support between resolutions
Added dual storage selection radio buttons to zip install, backup, and restore pages
Improved zip install compatibility
Updated update-binary source code
Numerous small bug fixes and improvements

Crazy question and the better part of me says no, but can you restore a backup made with cwm in twrp?

chrisbass said:
Crazy question and the better part of me says no, but can you restore a backup made with cwm in twrp?
Click to expand...
Click to collapse
No.
Sent from my SPH-L710 using xda premium

HELL YEAH....Thank You VERY MUCH for this. I used it always and loved it on my epic 4g and have been really missing it ever since I switch to my SGS3 and had to resort to using the old "caveman" style/method recovery again...LOL
Now I can use TWRP again. AWESOME!
Cheers!

Perfect! This recovery supports OpenRecoveryScript so i'm gonna have to make this an option in the Aroma installer.

Cannot mount scared or ext card while in recovery. Not really an issue since it didn't work on CWM or the older TWRP. miss that feature.
Sent from my SPH-L710 using xda app-developers app

glcK23 said:
Cannot mount scared or ext card while in recovery. Not really an issue since it didn't work on CWM or the older TWRP. miss that feature.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
What does mounting the sd card do? I'm able to backup/restore roms and backups from from the internal and external sd. Is that different?

cbond007 said:
What does mounting the sd card do? I'm able to backup/restore roms and backups from from the internal and external sd. Is that different?
Click to expand...
Click to collapse
It would mount it to be seen on your PC to transfer files.
But yes, long live TWRP. I couldn't get rid of CWM fast enough. Love this recovery.

glcK23 said:
Cannot mount scared or ext card while in recovery. Not really an issue since it didn't work on CWM or the older TWRP. miss that feature.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you have a 64GB card that's formatted as exFAT then recovery won't be able to mount it. You can reformat to FAT32 to fix. If not, then pull a log and paste it to a paste site and give me the link. I might be able to sort it out for you.

it came from my evo 3d so maybe it does need to be formatted. what about the internal sd card ? can that be formatted too ??
Sent from my SPH-L710 using xda app-developers app

Nice, i was waiting for this. TWRP blows away clockwork.

Great work! Made my life easier and this is definitely easier to use

steezc said:
Great work!
Click to expand...
Click to collapse
It absolutely will not install for me. Any way to get it as a tar file so I can use Mobile Odin.
_______________
Just Flash It !!!

[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. 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.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
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.

Reserved!

Dees_Troy is one of the best and nicest developers here, he did it all in like 5 minutes
Kudos brother, this is a great addiction for the Wonder!

sorry , is the image size 7.984MB ?

hadidjapri said:
sorry , is the image size 7.984MB ?
Click to expand...
Click to collapse
4.37MB, MD5 is 4c689ba24c1657540d8094124bf1e155

Dees_Troy said:
Direct Download
Turn the device off. Press and hold volume down, volume up, and power until the device boots, then on your computer:
fastboot flash recovery openrecovery-twrp-2.3.2.3-mako.img
Click to expand...
Click to collapse
this link refers me to the file with 7.984MB

hadidjapri said:
this link refers me to the file with 7.984MB
Click to expand...
Click to collapse
Ahhh, that is what I get for copying and pasting >_<

Dees_Troy said:
Ahhh, that is what I get for copying and pasting >_<
Click to expand...
Click to collapse
you get me bricked my phone :crying:
i hope nobody do the same mistake as i am by flashing "extreme huge" recovery.img
i didn't notice that ancora's recovery partition only capped to 7.5MB :crying:
well, it's not a problem. ssc is near my house
thanks for porting TWRP to ancora :good:

post no weighted ANCORA WAE LAH ....!:good:

hadidjapri said:
you get me bricked my phone :crying:
i hope nobody do the same mistake as i am by flashing "extreme huge" recovery.img
i didn't notice that ancora's recovery partition only capped to 7.5MB :crying:
well, it's not a problem. ssc is near my house
thanks for porting TWRP to ancora :good:
Click to expand...
Click to collapse
Odin should be able to fix it.

Dees_Troy said:
Odin should be able to fix it.
Click to expand...
Click to collapse
well, ancora's download mode sucks. it wastes me almost 1,5hours only stucked in "press up to continue"
gonna try the twrp after ssc fix my phone :good:

Testing it..
Sent from my GT-P5100 using xda premium

Thanks for porting it!

Can I flash this with adb and this command? dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
-sent from my awesome phone-

hotheabilly said:
Can I flash this with adb and this command? dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
-sent from my awesome phone-
Click to expand...
Click to collapse
Tested it, yes it works. But I reverted to CWM for a reason.
Sent from my GT-I8150 using xda app-developers app

Kreaz said:
Tested it, yes it works. But I reverted to CWM for a reason.
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Yes it works for me too, and yes I'm back to cwm for some reason too
-sent from my awesome phone-

comment removed.

hotheabilly said:
Yes it works for me too, and yes I'm back to cwm for some reason too
-sent from my awesome phone-
Click to expand...
Click to collapse
I screwed up ma phone. I flashed TWRP via ADB. When i reboot to recovery it goes to CWM. When i switch on normally it goes to TWRP!!! Now im havin 2 recoveries and i cant boot to SlimBean!!!!!! Any fix?!?!?
Edit: I did a full wipe and Restored my system. Thanks to CWM!!

jassim007 said:
I screwed up ma phone. I flashed TWRP via ADB. When i reboot to recovery it goes to CWM. When i switch on normally it goes to TWRP!!! Now im havin 2 recoveries and i cant boot to SlimBean!!!!!! Any fix?!?!?
Edit: I did a full wipe and Restored my system. Thanks to CWM!!
Click to expand...
Click to collapse
lololol you probably format your ROM partition by your command line and replacing the whole rom to TWRP, but this is the first case I've ever seen!

hotheabilly said:
lololol you probably format your ROM partition by your command line and replacing the whole rom to TWRP, but this is the first case I've ever seen!
Click to expand...
Click to collapse
Is there .tar format for flashing TWRP via Odin?

[Q] twrp 2.6.0.0

I am running twrp 2.5.0 and I want too know what twrp 2.6.0 has to offer in sorts of updates and if I'll need to update to 2.6 for new updates on cyanogenmod 10.1 (I run the official stable version)

What's new in 2.6.0.0:
Special Note: If you are running a custom theme, some of the changes in 2.6.0.0 will likely not be visible with your custom theme.
Can encrypt a backup to prevent theft of private data from your backup files
Updated graphics / icon courtesy of shift
Updated exFAT to latest commits
Fixed a problem with Samsung TouchWiz decryption
Update SuperSU binary
Fixed saving of backup partitions list
Fixed saving of last used zip install folder
Fixed backup of datadata on devices that use a separate partition for datadata
Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
Fixed some problems with partitioning a SD card
Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
Get it here TWRP 2.6

BrooklynNY said:
What's new in 2.6.0.0:
Special Note: If you are running a custom theme, some of the changes in 2.6.0.0 will likely not be visible with your custom theme.
Can encrypt a backup to prevent theft of private data from your backup files
Updated graphics / icon courtesy of shift
Updated exFAT to latest commits
Fixed a problem with Samsung TouchWiz decryption
Update SuperSU binary
Fixed saving of backup partitions list
Fixed saving of last used zip install folder
Fixed backup of datadata on devices that use a separate partition for datadata
Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
Fixed some problems with partitioning a SD card
Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
Get it here TWRP 2.6
Click to expand...
Click to collapse
Is there another way to flash it via zip or a program of some sort or just an img
Sent from my Amazon Kindle Fire using xda app-developers app

You can update it with KF tool 0.99
You can update it with Kindle Fire Utility 0.99 version. Run the KF utility first and select install TWRP. it will download 2.6 version to PC and update it for you when boot the KF

lifegap said:
You can update it with Kindle Fire Utility 0.99 version. Run the KF utility first and select install TWRP. it will download 2.6 version to PC and update it for you when boot the KF
Click to expand...
Click to collapse
First of all here's a flashable zip file. TWRP 2.6 ZIP
Second, you can do this:
Assuming you have the recovery image renamed to "recovery.img" and placed it at the root of the /sdcard partition....
Go to terminal and put in:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p5
Now reboob! Enjoy! -- Sent from my Amazon Kindle Fire using xda premium

BrooklynNY said:
First of all here's a flashable zip file. TWRP 2.6 ZIP
Second, you can do this:
Assuming you have the recovery image renamed to "recovery.img" and placed it at the root of the /sdcard partition....
Go to terminal and put in:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p5
Now reboob! Enjoy! -- Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Makes sense, I'll flash it later. Thanks for sharing! +1

Twrp.3.1.0-0 ??? Just a few questions....

So the newly released twrp 3.1.0-0 has been released and i was wondering if it will be better than my unreleased twrp 3.0.4-1 and in better i mean will it be more compatible and stable with nougat on oneplus 3 , i chose version 3.0.4-1 because everyone seemed to be having problems with the official versions if anybody has any knowledge about this new recovery then please comment , here is a list of updates to the new twrp -
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 (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

OT : You sound like some random private channel Indian reporter..

sarus_b said:
OT : You sound like some random private channel Indian reporter..
Click to expand...
Click to collapse
Hahahaha i don't know how on earth you came up with that assumption but no i am a white male that lives in the UK...

I am gonna go ahead and flash the new version if there are any problems with restoring nandroids or anything i will report back...

Xceeder said:
I am gonna go ahead and flash the new version if there are any problems with restoring nandroids or anything i will report back...
Click to expand...
Click to collapse
Are you using F2FS for data and cache? Also pls report if first boot of new 3.1 TWRP has wiped Internal storage files (/sdcard) like it did for many using f2fs for data..

arvindgr said:
Are you using F2FS for data and cache? Also pls report if first boot of new 3.1 TWRP has wiped Internal storage files (/sdcard) like it did for many using f2fs for data..
Click to expand...
Click to collapse
I had that issue but it only happened when I used open gapps. They seem to be having a lot of issues with this device.
EDIT: Nope, it happened using dynamic gapps too. Has happened on multiple ROMS, must be a TWRP/F2FS issue.
Double Edit: Happened on EXT4 as well.

JohnHorus said:
I had that issue but it only happened when I used open gapps. They seem to be having a lot of issues with this device.
Click to expand...
Click to collapse
Seems unreleased 3.0.4 is really stable on Nougat F2FS devices., Until update for official 3.1 comes fixing those issues, I'll stick with prev. version. Thanks for trying and posting here..

arvindgr said:
Seems unreleased 3.0.4 is really stable on Nougat F2FS devices., Until update for official 3.1 comes fixing those issues, I'll stick with prev. version. Thanks for trying and posting here..
Click to expand...
Click to collapse
Haha... yeah. Nah. It actually just happened for me using dynamic gapps, so forget about that. I had it happen all the time on Lineage, so I assumed it was Lineage at first. I switched to AOSP-Extended, and only had it happen once, when I tried using open gapps. I switched to dynamic gapps for other reasons, and it never happened in 4 or 5 flashes, so I assumed it was open gapps.
BUT it just happened to me, maybe 20 minutes after posting that, using AOSP-Ex and dynamic gapps. So at this point I'm like 100% positive it's this messed up TWRP, not sure if it's F2FS related or not as I've only ever used F2FS, but after this I may just start using EXT4.
Edit: AANNNDD it happened on EXT4 as well... at least it only happens during initial setup.

Xceeder said:
I am gonna go ahead and flash the new version if there are any problems with restoring nandroids or anything i will report back...
Click to expand...
Click to collapse
There shouldn't be any issues since 3.0.4-1 was developed by a member of TWRP team (jcadduono) specifically for the 3 and the 3T and TWRP seem to have merely polished it and posted it as 3.1.0
If you read the description of 3.1.0 on the TWRP site, you will see that it also mentions jcadduono as the developer.

JohnHorus said:
Haha... yeah. Nah. It actually just happened for me using dynamic gapps, so forget about that. I had it happen all the time on Lineage, so I assumed it was Lineage at first. I switched to AOSP-Extended, and only had it happen once, when I tried using open gapps. I switched to dynamic gapps for other reasons, and it never happened in 4 or 5 flashes, so I assumed it was open gapps.
BUT it just happened to me, maybe 20 minutes after posting that, using AOSP-Ex and dynamic gapps. So at this point I'm like 100% positive it's this messed up TWRP, not sure if it's F2FS related or not as I've only ever used F2FS, but after this I may just start using EXT4.
Click to expand...
Click to collapse
I only have the data partition as f2fs if that's any help and my device is not encrypted... As for the recent twrp it works fine with me i can back up and restore nandroids as well as flashing zip files..

tnsmani said:
There shouldn't be any issues since 3.0.4-1 was developed by a member of TWRP team (jcadduono) specifically for the 3 and the 3T and TWRP seem to have merely polished it and posted it as 3.1.0
If you read the description of 3.1.0 on the TWRP site, you will see that it also mentions jcadduono as the developer.
Click to expand...
Click to collapse
Yeah i thought everything would be fine i was just testing it for other people...

[RECOVERY][GUIDE][F2FS] TWRP 3.5.2_9 with F2FS support for Xiaomi Redmi 8 [olive][Unofficial]

This is TWRP-3.5.2_9 unofficially updated with the ability to convert your /data and /cache partitions to F2FS.
Make sure your kernel and rom support f2fs (the dev of your ROM/kernel should have f2fs support noted).Most Aosp/Lineage based roms support it.Miui doesn't
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system initially developed by Samsung Electronics for the Linux kernel.
The motive for F2FS was to build a file system that, from the start, takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers
Click to expand...
Click to collapse
- Wikipedia
This is potentially unstable, F2FS is a file system that is very much in active development. There is a reason that most OEMs go with ext4 out of the box.
How to use F2FS for /data and /cache?
Conversion procedure :
Download and install TWRP from the link below
Reboot into recovery
Replace fstab.qcom in /vendor/etc/
Code:
adb push fstab.qcom /vendor/etc
or use twrp file manager to replace
Reboot into recovery again
Flash a kernel that supports F2FS (I use CherryKernel as I know it works and is frequently updated)
Back up any important data as this will wipe your entire internal storage
Boot into TWRP and go into Wipe > Advanced Wipe
Select Data and then hit "Change or Repair File System"
Hit Change File System
Choose F2FS and slide to confirm
Repeat the previous three steps for cache
Reboot and move all of your files back over (if restoring through TWRP, make sure to check the option to use rm -rf instead of formatting)
Downloads:
fstab.qcom: in attachment
Recovery: twrpf2fs-3.5.2_9-0-olive.img
CherryKernel:CherryKernel-V1-hotfix.zip (Follow t.me/CherryKernel_SDM439 for updates)
Credits:
Twrp team
@oguz298 @altsec for twrp device trees
RALegacy-Kernel dev for fstab file
@TheGame455 for much help and prebuilt kernel
@TheGame455 & Akira for CherryKernel
Source Code:
Device tree: https://github.com/TeamWin/android_device_xiaomi_olive
CherryKernel source: https://github.com/AkiraNoSushi/kernel_cherry_sdm439

Reserved

Reserved #2

Reserved #3