My bad, I had actually used the "Flash Recovery" feature in Rom Toolbox lite's Rom Installer. Sorry for my confusion.
[RECOVERY][manta] TWRP 3.1.1-0 touch recovery [2017-05-19]
- Thread starter Dees_Troy
- Start date
My bad, I had actually used the "Flash Recovery" feature in Rom Toolbox lite's Rom Installer. Sorry for my confusion.
I just tried it and works. You may have some additional info about the mounting error in the log file (file last_log in folder /cache/recovery).
I just reformatted the system and did a full wipe, all is good. Thx.
Sent from my Nexus 10 using Tapatalk
Sent from my Nexus 10 using Tapatalk
Problems i've noticed with 2.8.2.0
First it seems to stick on the loading screen for about 30 seconds (on the Nex 5 it loads almost instantly).
Secondly, advanced wiping of all except storage takes an age (same with 2.8.1.0)
Thirdly, the twrp folder has vanished from storage (lollipop related maybe?). It doesn't show up at all in root explorer or in windows explorer when connected to pc via wifi ftp. Yet within recovery itself there are existing backups listed. This affects the Nex 5 as well.
First it seems to stick on the loading screen for about 30 seconds (on the Nex 5 it loads almost instantly).
Secondly, advanced wiping of all except storage takes an age (same with 2.8.1.0)
Thirdly, the twrp folder has vanished from storage (lollipop related maybe?). It doesn't show up at all in root explorer or in windows explorer when connected to pc via wifi ftp. Yet within recovery itself there are existing backups listed. This affects the Nex 5 as well.
Is this bug still present? It's related to lollipop.
Folders/files created in TWRP are 0 bytes and nothing can be done with the file from booted lollipop/mtp.
From recovery they can be accessed in filemanager or from mtp.
Skickat från min GT-I9505 via Tapatalk
The only difference is that for me, I don't even have a visible twrp folder when viewed within lollipop, yet within recovery the backups are all showing.
I read and did on my own N10 the following commands in a rooted terminal session:
Code:
su
restorecon -FR /data/media/0I did this before I even checked if the TWRP backups were visible so never saw whether I had the issue.
Flashable zip just in case if someone need
P.s. Keep in mind twrp 2.8.2.0 are kind of slow booting up....so don't be afraid if you will see long booting process. And don't ask me why, I have no idea...probably I'm not running lolipop and I'm still on 4.4.4
P.s. Keep in mind twrp 2.8.2.0 are kind of slow booting up....so don't be afraid if you will see long booting process. And don't ask me why, I have no idea...probably I'm not running lolipop and I'm still on 4.4.4
2.8.2.1 is out for nexus 6 and 9. Resolves the excessive time booting to twrp, as well as the 5 minute long cache wipes.unless you're seeing something i'm not, 2.8.2.0 is the latest
I'm not sure if this is a bug or my own stupidity but I've now got a "decryption unsuccessful" message when I try to boot into system:
"The password you entered is correct but unfortunately your data is corrupt" "To resume using your tablet, you need to perform a factory reset"
I believe the steps that caused it were as follows: Firstly I decided to encrypt my nexus 10 after ota upgrading to 5.0 using the standard android method.
When I went into recovery later (2.8.1.0) it asked me for a password. I put in my lock screen pin but it failed. I thought to install the latest recovery (2.8.2.0) using fastboot. But at the same time I thought to remove my screen pin anyway. So I got into 2.8.2.0 (after a long wait) and it didn't ask for a pin. Anway I was trying to browse files in install but noticed I couldn't for some reason. I went into mount and tried to mount data and it seemed to hang. I'm guessing this is where things went wrong.
"The password you entered is correct but unfortunately your data is corrupt" "To resume using your tablet, you need to perform a factory reset"
I believe the steps that caused it were as follows: Firstly I decided to encrypt my nexus 10 after ota upgrading to 5.0 using the standard android method.
When I went into recovery later (2.8.1.0) it asked me for a password. I put in my lock screen pin but it failed. I thought to install the latest recovery (2.8.2.0) using fastboot. But at the same time I thought to remove my screen pin anyway. So I got into 2.8.2.0 (after a long wait) and it didn't ask for a pin. Anway I was trying to browse files in install but noticed I couldn't for some reason. I went into mount and tried to mount data and it seemed to hang. I'm guessing this is where things went wrong.
Tried this today (run in terminal emulator in root mode) on both N5 and N10 and it worked great, can now see the twrp folder from within Lollipop.
There is a new TWRP verision in:
http://techerrata.com/browse/twrp2/manta
Well, it doesn't take a whole minute to load like previous version but the battery percentage indicator is still missing
What's new in 2.8.3.0:
-MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
-MTP will now tell the host PC that storage is removed instead of disabling MTP completely
-MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
-Update and improve fix permissions and make fixing contexts optional
-Update SuperSU in TWRP to 2.40 and update install process
-Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
-Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
-Fix kernel panic during MTP start on some devices
-Support unicode fonts on devices with True Type Font support
-Fix slider value not showing sometimes (vibration settings page)
-Toggle MTP off during adb sideload to set correct USB IDs
-Reduce library requirements for 5.0 L decrypt
-Other minor fixes and improvements
http://techerrata.com/browse/twrp2/manta
Well, it doesn't take a whole minute to load like previous version but the battery percentage indicator is still missing
What's new in 2.8.3.0:
-MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
-MTP will now tell the host PC that storage is removed instead of disabling MTP completely
-MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
-Update and improve fix permissions and make fixing contexts optional
-Update SuperSU in TWRP to 2.40 and update install process
-Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
-Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
-Fix kernel panic during MTP start on some devices
-Support unicode fonts on devices with True Type Font support
-Fix slider value not showing sometimes (vibration settings page)
-Toggle MTP off during adb sideload to set correct USB IDs
-Reduce library requirements for 5.0 L decrypt
-Other minor fixes and improvements
There is a new TWRP verision in:
http://techerrata.com/browse/twrp2/manta
Well, it doesn't take a whole minute to load like previous version but the battery percentage indicator is still missing
I can confirm the load time has gone back to normal. (And I hadn't noticed, but I don't have a battery indicator either).
What's with formatting the cache partition taking minutes instead of a few seconds? I know I can have TWRP "rm -rf" instead of formatting, and that only takes a couple of seconds, but the "many-minutes-to-format-the-cache-partition" problem has existed on my N10 for many revisions of TWRP, and doesn't exist on my N5 or Galaxy Nexus. Any thoughts about this appreciated!
I got my Nexus 10 at the end of October & thought the 2 day long wipes were normal. I'm using philz recovery at the moment but think I'll switch to twrp 2.8.3.0.
Sent from my LG-ls990 using Xparent Red Tapatalk 2
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
82Team 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.19121212
