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

Search This thread

rivvv321

Member
Mar 6, 2016
30
0
Hi guys! I have CWM recovery and i finally need flash TWRP for magisk 13.3. U can tell me how can i flash this via Odin, because i dont have root, and I'm afraid that i can brick my phone ;/ U can also tell me what version is the best, and whether i need special modem and bootloader for this recovery? I have XXUHOF2. Thanks!
 

tmviet

Senior Member
Aug 24, 2017
126
14
Milan
I've same problem of @speter2 & @stylemessiah
for error E:failedtowrite/ dev/block/mcblk0p9 I/O error

Just today I've updated to TWRP v.3.1.1 as image, I've restart TWRP and after reboot system.

It seems that all works fine. :)

Only a little question is a/m error E:......... important or not ?
I ask this because I cannot move downloaded apk from internal storage to external microsd, is there any relationship with error E: .........
:confused::confused:
 
I've same problem of @speter2 & @stylemessiah
for error E:failedtowrite/ dev/block/mcblk0p9 I/O error

Just today I've updated to TWRP v.3.1.1 as image, I've restart TWRP and after reboot system.

It seems that all works fine. :)

Only a little question is a/m error E:......... important or not ?
I ask this because I cannot move downloaded apk from internal storage to external microsd, is there any relationship with error E: ......... :confused::confused:


failed to write/dev/block/mmcblk0p9
Im using Samsung S4 GT-i9505, how to fix this?

That error can be ignored.

It's not important and does not affect your storage.

Are you trying to move the apk in recovery or in the ROM you are using? If it's not in recovery it might have to do with external sd card permissions.

Sent from my OnePlus 3T using XDA Labs
 
  • Like
Reactions: tmviet

Rhoban

Senior Member
Jan 8, 2015
4,734
1,567
Dobra
Hi guys! I have CWM recovery and i finally need flash TWRP for magisk 13.3. U can tell me how can i flash this via Odin, because i dont have root, and I'm afraid that i can brick my phone ;/ U can also tell me what version is the best, and whether i need special modem and bootloader for this recovery? I have XXUHOF2. Thanks!

Odin does not require root.
 

tmviet

Senior Member
Aug 24, 2017
126
14
Milan
That error can be ignored.

It's not important and does not affect your storage.

Are you trying to move the apk in recovery or in the ROM you are using? If it's not in recovery it might have to do with external sd card permissions.

Sent from my OnePlus 3T using XDA Labs
Yes it's not important.

OK I'll try to do ext card write permissions
 

v00d007

Senior Member
Feb 28, 2014
1,387
473
Recently I got the strange error "255" while restoring data. No matter which rom/ android version. Tested v3.1.1.0, 3.1.0.0, 2.8.7.0. never had this before. S4 9505 PK2 modem/bootloader. Any ideas?
 
Recently I got the strange error "255" while restoring data. No matter which rom/ android version. Tested v3.1.1.0, 3.1.0.0, 2.8.7.0. never had this before. S4 9505 PK2 modem/bootloader. Any ideas?

First of all, I know it's off topic but great avatar. I remember those days well. :D :good:

If I'm not mistaken, you should always restore your backups using the version of TWRP you made them with.

According to the following post however, error 255 means insufficient storage space:

https://xdaforums.com/showpost.php?p=71179467&postcount=6

Or it could also mean that your backups got corrupted somehow, I think.

Are you restoring only the /data partition? If so, you could try wiping it (without wiping /data/media because that's your internal storage) before restoring.

This is another possible solution:
https://xdaforums.com/htc-one-m8/help/error-twrp-restore-t2805826

Sent from my OnePlus 3T using XDA Labs
 
Last edited:

v00d007

Senior Member
Feb 28, 2014
1,387
473
...
If I'm not mistaken, you should always restore your backups using the version of TWRP you made them with.

According to the following post however, error 255 means insufficient storage space:

https://xdaforums.com/showpost.php?p=71179467&postcount=6

Or it could also mean that your backups got corrupted somehow, I think.

Are you restoring only the /data partition? If so, you could try wiping it (without wiping /data/media because that's your internal storage) before restoring...
Hmm...
1st I tried to restore two backups of 2 different roms (TW/LP, crDroid/Nougat) that were created with v3.1.0.0. Both failed when reaching the data partition. But I successfully restored an older bkp with 3.1 that was origin. created with v2.8.7.0.
Then I tried to use other builds but all show the same error 255. All was wiped, no obsolete data on the emulated sdcard.
So, its still mysterious...
Your last link - I didn't get wat was meant there, sorry.
 
Hmm...
1st I tried to restore two backups of 2 different roms (TW/LP, crDroid/Nougat) that were created with v3.1.0.0. Both failed when reaching the data partition. But I successfully restored an older bkp with 3.1 that was origin. created with v2.8.7.0.
Then I tried to use other builds but all show the same error 255. All was wiped, no obsolete data on the emulated sdcard.
So, its still mysterious...
Your last link - I didn't get wat was meant there, sorry.

The last link suggested wiping the internal storage (/sdcard or /data/media) partition too to get more free space.

Just make sure you make a backup of your files first because TWRP backups don't include that partition.

Sent from my OnePlus 3T using XDA Labs
 

tmviet

Senior Member
Aug 24, 2017
126
14
Milan
Thanks to my friend I find a solution to move apks from internal storage sd into ext sd, simply rename apk e.g. in ap , move ap and after into destination ext sd rename in apk
 
  • Like
Reactions: iPAQ 6515a User
Thanks to my friend I find a solution to move apks from internal storage sd into ext sd, simply rename apk e.g. in ap , move ap and after into destination ext sd rename in apk

Oh so your problem was transferring apk files?

Do you have any security app installed? Like anti-malware or antivirus. Those apps may block apk files because they may think they're malware because they don't come from the Play Store.

Sent from my OnePlus 3T using XDA Labs
 

v00d007

Senior Member
Feb 28, 2014
1,387
473
Will the display timeout feature ever be fixed?? Still not working in latest 3.1.1.0.
 

3mel

Senior Member
Aug 23, 2012
1,973
647
London
I get the exact same listed error in TWRP when flashing roms. I don't use backups nowadays as titanium works well again and I keep the zip onboard.
so your error ISN'T only related to restoring backups @v00d007
 

Top Liked Posts

  • There are no posts matching your filters.
  • 131
    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.
    51
    3.0.0 with F2FS support

    Any S4 variant with Qualcomm Snapdragon 600 is supported (except I9515)

    Download (flashable zip): https://www.androidfilehost.com/?fid=24407100847292430

    Download (Odin TAR, not for AT&T/Verizon): https://www.androidfilehost.com/?fid=24407100847292433

    :)
    23
    TWRP 3.0.2-0 flashable zip for S4 (GT-I9505)
    21
    TWRP_2.8.7.0_GT-I9505(jfltexx)

    TWRP recovery version 2.8.7.0.
    21
    New TWRP 2.7.1.0 is out.

    What's new in 2.7.1.0:


    • Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
    • Various bugfixes to backup and restore
    • Improvements to USB storage handling
    • Added a class to search for files to make finding the correct brightness file automatic in most cases
    • Various other bugfixes and tweaks


    My flashable zip attached.;)