Related
[RECOVERY] [4/5/16] TWRP 3.0.2-0 - TeamWin Recovery Project
TeamWin is proud to present TWRP 3.0.2-0 for the Galaxy Note (T-Mobile)!
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project or twrp2 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
Decryption of /data
Easy selection of internal/external storage
See changelog below for new features
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 cache & dalvik, 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/omnirom/android_bootable_recovery
Gerrit for TWRP Official Device Configs - http://gerrit.twrp.me
Gerrit Instance - http://gerrit.omnirom.org
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.
quincytmo Device Config: https://github.com/TeamWin/android_device_samsung_quincytmo
Kernel: https://github.com/bigbiff/i717-GB-Kernel
DOWNLOAD:
All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.
http://twrp.me
Support:
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers
Changelog
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.
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
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 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!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 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!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
- 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)
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.
2.8.6.0
- Allow mulitple overlays for popup boxes (Dees_Troy)
- Add pattern style password entry for decrypt (Tassadar)
- Keyboard improvements (_that)
- Update AOSP base to 5.1 (Dees_Troy)
- Reduce theme count to 5 and rely on scaling (Dees_Troy)
- Various scaling improvements (Dees_Troy)
- Improved handling of resources in the GUI (_that)
- Make scroll bar size proportional to list size (_that)
- Allow scoll lists to render without a header (_that)
- Make console scroll per pixel with kinetic scrolling (_that)
- Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
- Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
2.8.5.0
- Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
- Improve thread handling and move input handling into the main rendering thread to improve stability
- Make MTP work even if unplugged and plugged back in
- Unify scrollable list code and make kinetic scrolling feel more natural
- Fix handling of mapped zip files for OTA updates (CM12 updater)
- USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
- Add Cancel Backup capability
- Other small fixes and improvements
2.8.4.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
- Fix some MTP related crashes and bugs
- Eliminate TWRP toggling USB IDs during boot if MTP is enabled
- Fix various adb sideload issues
- Improve threading of actions
- Eliminate separate thread for screen timeout
- Update libblkid to 2.25.0
- Use power button as back button on watch themes for easier navigation
- Add mutex locking to data manager
- Improve custom theme handling on encrypted devices
- Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
2.8.4.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
- Fix some MTP related crashes and bugs
- Eliminate TWRP toggling USB IDs during boot if MTP is enabled
- Fix various adb sideload issues
- Improve threading of actions
- Eliminate separate thread for screen timeout
- Update libblkid to 2.25.0
- Use power button as back button on watch themes for easier navigation
- Add mutex locking to data manager
- Improve custom theme handling on encrypted devices
- Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
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
2.8.0.0
- Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
- Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
- Add support for color in the console and give error, warning, and highlight lines different colors
- Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
- Improve handling of /misc thanks to mdmower
- Improve setting of time on Qualcomm devices thanks to [NUT]
- Allow using images on slidervalue GUI objects thanks to Tassadar
- Allow using variables and addition and subtraction in variables for easier theming
- Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
- Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
- Other minor fixes and improvements
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. 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
2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
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
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
2.6.0.1
Fix Data being listed twice in advanced wipe
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.
2.5.0.0
Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
Fixed a problem with directory permissions on split archive backups
Fixed a problem with md5 verification of backups
Added a search function to libtar (thanks to kokotas)
Improve handling of XML errors (fix permissions)
Fixed handling of subpartitions
Improvements to recovery.fstab flags
Fixed a problem with decryption not being able to locate the decryption key in some situations
2.4.4.0
Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
More fixes for the file selector
Switched from using busybox md5sum to a direct C function call
Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
Update exFAT to latest commits
Added a build flag to disable using the ioctl for screen blanking
2.4.3.0
Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
Added a scroll bar to file selectors and listboxes courtesy of Tassadar
Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
Added a screen dim effect 2 seconds before screen off on some devices
Finally fixed file selector crash (one of the joys of working with multi-threaded software)
Fixed loading of screen timeout setting during startup
Improvements and bugfixes to screen timeout code
Fix Military Time setting persisting
2.4.2.0
Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
Add a brightness setting (requires device specific setup and only some devices have been added)
Add a root checker and offer to install SuperSU if the device isn't already rooted
Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
Check and offer to fix root permissions if broken
Add an option for a 24 hour clock display instead of AM/PM (aka military time)
Move stock recovery reflash check to occur during the reboot cycle
Add support for some MTK6xxx devices
Change libtar to vfork to help prevent memory problems
Add a "clicked" effect to most buttons, file selector, and listbox
Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
Other minor bugfixes and improvements
2.3.3.0
Added better handling of wiping on /data/media devices with Android 4.2 to help prevent multiple upgrades of the file system for multiple users
NOTE: It is not recommended to jump back and forth between 4.1 and 4.2 ROMs. If you do, this may trigger additional upgrades and you will have to manually move your files back to the "single user" layout when going back to 4.1.
Fixed renaming of backups when a space is present
Added decrypt button to mount page if you cancel decryption during boot
Added ignore blkid flag support
Fixed handling of MTD partitions during mount
Fixed some keyboard mapping issues on 800x1280 layout
2.3.2.3
Added ability to backup modem
Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see http://teamw.in/androidmultiuser)
Fixed a bug with deleting a backup with a space in the name
Added highlights on keyboard key presses
Updates to Fix Permissions
2.3.1.1
Fixed keyboard segfault
Handle single LUN file for USB Storage
Handle mounting of slow sdcards
Update USB Mount Code to be more Efficient
Many, many updates. See https://github.com/TeamWin/Team-Win-Recovery-Project/commits/jb-wip/ for detailed commits.
second
Am I third????:thumbup:
Sent from my SGH-T879 using xda premium
I respect your work.Thanks
Yessssssssssss more development!!! Now if we could just get another ROM =)
Sent from my SAMSUNG-SGH-I717 using xda premium
It's actually good. I fooled with it for a whilw
Sent from my SGH-T879 using xda app-developers app
Its more then good its greattttttttt.
Sent from my SAMSUNG-SGH-I717 using xda premium
I've been using the one for the i717 note and its been fine. Is there any reason I should update to this version?
Sent from my SGH-T879 rom using i717m device using Tapatalk 2
Can't get it working for me. It never seems to mount my external SD card ... any ideas?
Sent from my SGH-T879 using xda premium
You should be able to just select the external sd option right on the bottom of the screen . Then again I install ths one for the i717 so that might be a difference. Did you try the one for the at&t note ?
tomin.fhl said:
Can't get it working for me. It never seems to mount my external SD card ... any ideas?
Sent from my SGH-T879 using xda premium
Click to expand...
Click to collapse
Sent from my SGH-T879 rom using i717m device using Tapatalk 2
No, I installed the T-mobile version. Let me try the i717 version.
Sent from my SGH-T879 using xda premium
tomin.fhl said:
Can't get it working for me. It never seems to mount my external SD card ... any ideas?
Sent from my SGH-T879 using xda premium
Click to expand...
Click to collapse
Alicklee said:
You should be able to just select the external sd option right on the bottom of the screen . Then again I install ths one for the i717 so that might be a difference. Did you try the one for the at&t note ?
Sent from my SGH-T879 rom using i717m device using Tapatalk 2
Click to expand...
Click to collapse
tomin.fhl said:
No, I installed the T-mobile version. Let me try the i717 version.
Sent from my SGH-T879 using xda premium
Click to expand...
Click to collapse
Can you send me the log from /tmp/recovery.log so I can look at it?
How do I flash it though? I installed it via GooManager, but even though it says installed, when I reboot, i'm in CWM Recovery
EDIT: Got it. Went to site and flashed through recovery!
Hi. I just received a report of this port not rebooting to android without Odin. Can someone please verify? Thanks!
I've been trying to use twrp for days now and its just not working. I installed goo manager and down loaded T-Mobile galaxy note recovery, but every time I reboot into recovery all I see is cwm recovery menu with just option to install zip from external SD card. Please help
Sent from my SGH-T879 using xda premium
lrodri30 said:
I've been trying to use twrp for days now and its just not working. I installed goo manager and down loaded T-Mobile galaxy note recovery, but every time I reboot into recovery all I see is cwm recovery menu with just option to install zip from external SD card. Please help
Sent from my SGH-T879 using xda premium
Click to expand...
Click to collapse
Go to rotohammers cm10 thread download the twrp recovery zip in the OP. Flash it in CWM recovery then choose reboot recovery in the advance menu in CWM recovery....
sent from my T-mo Note
Thanks it worked!
Sent from my SAMSUNG-SGH-I717 using xda premium
problem loading roms
If you need help please, please, please, please post recovery.log.
1. adb pull /tmp/recovery.log or Advanced->Copy Log to SDCard
2. Upload /tmp/recovery.log or /sdcard/recovery.log to**CENSORED**
I have TWRP on my T-Mo Note T879, which I installed thru GooManager....and whenever I try to flash a rom I get a fail...I posted the last recovery.log to the link above.....and I have also tried 4 different roms....some I got through goomanager, other were ones I had downloaded....but the result is the same....
jcaplinger said:
If you need help please, please, please, please post recovery.log.
1. adb pull /tmp/recovery.log or Advanced->Copy Log to SDCard
2. Upload /tmp/recovery.log or /sdcard/recovery.log to**CENSORED**
I have TWRP on my T-Mo Note T879, which I installed thru GooManager....and whenever I try to flash a rom I get a fail...I posted the last recovery.log to the link above.....and I have also tried 4 different roms....some I got through goomanager, other were ones I had downloaded....but the result is the same....
Click to expand...
Click to collapse
We don't get automatic emails when you paste it. We need the URL to see what you pasted.
[ THIS POST IS TEAMWIN'S STOCK TWRP POSTING. USE OF THE WORDS "US" AND "OURS" MEANS "DEES_TROY AND TEAMWIN" NOT HASHCODE ]
*** ALL CREDIT FOR TWRP BELONGS TO DEES_TROY AND TEAMWIN. ***
They do a BANG UP job on making a fantastic customizable touch-based recovery.
Donate to TeamWin:
http://www.teamw.in/project/twrp2
BEFORE YOU FLASH THIS, PLEASE MAKE SURE THAT YOU HAVE A 2ND-BOOTLOADER INSTALLED FROM HERE:
http://forum.xda-developers.com/showthread.php?t=2100963
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.
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.
CHANGELOG for 2.5.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!
-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-Fixed a problem with md5 verification of backups
-Added a search function to libtar (thanks to kokotas)
-Improve handling of XML errors (fix permissions)
-Fixed handling of subpartitions
-Improvements to recovery.fstab flags
-Fixed a problem with decryption not being able to locate the decryption key in some situations
CHANGELOG for 2.4.4.0:
-Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
-More fixes for the file selector
-Switched from using busybox md5sum to a direct C function call
-Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
-Update exFAT to latest commits
-Added a build flag to disable using the ioctl for screen blanking
CHANGELOG for 2.4.3.0:
-Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
-Added a scroll bar to file selectors and listboxes courtesy of Tassadar
-Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
-Added a screen dim effect 2 seconds before screen off on some devices
-Finally fixed file selector crash (one of the joys of working with multi-threaded software)
-Fixed loading of screen timeout setting during startup
-Improvements and bugfixes to screen timeout code
-Fixed persistence of the 24 hour / military time setting
CHANGELOG for 2.4.2.0:
-Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
-Add a brightness setting (requires device specific setup and only some devices have been added)
-Add a root checker and offer to install SuperSU if the device isn't already rooted
-Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
-Check and offer to fix root permissions if broken
-Add an option for a 24 hour clock display instead of AM/PM (aka military time)
-Move stock recovery reflash check to occur during the reboot cycle
-Add support for some MTK6xxx devices
-Change libtar to vfork to help prevent memory problems
-Add a "clicked" effect to most buttons, file selector, and listbox
-Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
-Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
-Other minor bugfixes and improvements
CHANGELOG for 2.4.1.0:
-Fixed a problem with mkdosfs that formatted sdcards to 2GB
-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
CHANGELOG for 2.4.0.0:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!
** THIS IS A FLASHABLE .ZIP FILE FOR INSTALLING IN YOUR CURRENT VERSION OF TWRP **
DOWNLOAD:
[ DO NOT DOWNLOAD ANY FILES FROM TEAMWIN'S WEBSITE. IN GENERAL, THEY ARE MEANT TO BE FLASHED TO UNLOCKED DEVICES AND WON'T WORK FOR THE KINDLE FIRE 2 ]
You can download from goo.im here and place on your SDCARD:
http://goo.im/devs/Hashcode/otter2/recovery-zip/zip-otter2-twrp-2.6.3.1-recovery.zip
md5sum: b9eb941b1673396c91f73ccda010daf1
INSTALL INSTRUCTIONS:
During the BLUE logo screen press the power button to cycle through options and select "Recovery" to enter TWRP.
Select "Install"
Navigate to where you placed the file on your device
Select the .zip filename
Swipe to confirm flash
Reboot
KNOWN ISSUES:
None at the moment.
BUGS:
First: I'd read through this thread and see if your issue isn't answered.
Second: Try googling for it
Third: If it seems like a Kindle Fire 2 issue, then post in the thread.
Lastly: If you have found a bug, please consider posting it to TeamWin's 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 #kindlefire-dev or #twrp on Freenode with your IRC client or just click this link.
can i just flash the new image from the old (previously available twrp) recovery?
755 said:
can i just flash the new image from the old (previously available twrp) recovery?
Click to expand...
Click to collapse
You flash it via fastboot
Sent from my Amazon Kindle Fire2 using xda app-developers app
The link is dead
Alin1997 said:
The link is dead
Click to expand...
Click to collapse
No, it isn't.
--
Sent from my mind to your screen.
Any chance this will get usb mounting fixed?
I can adb push, but usb mounting would make like much easier
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
any chance for flashable zip?
mindmajick said:
Any chance this will get usb mounting fixed?
I can adb push, but usb mounting would make like much easier
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I dont think TWRP supports USB sharing for /data/media emulated sdcard space.
Sent from my DROID4 using Tapatalk 2
Hashcode said:
I dont think TWRP supports USB sharing for /data/media emulated sdcard space.
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Is it possible to port a cwm recovery?
Sent from my A2109A using Tapatalk HD
While I'm waiting on my fastboot cable, I've been trying to get to fastboot mode on my own. No luck, of course, no matter what I try. I guess I don't need twrp-2.4 yet since 2.3 does the job, but not having the latest is bothersome.
Sent from my Amazon Kindle Fire2 using xda premium
TWRP 2.5.0.0 for KF2?
Thanks for this. Wondered if TWRP 2.5.0.0 was on the way for the KF2. Any news?
Squuiid said:
Thanks for this. Wondered if TWRP 2.5.0.0 was on the way for the KF2. Any news?
Click to expand...
Click to collapse
Contact @Hashcode. He can make a newer version.
Gesendet von meinem LG-P990 mit Tapatalk 2
TWRP 2.6.0.0 is being tested.
Once approved, I'll add it to the instructions
Sent from my XT926 using Tapatalk 2
OP Updated with TWRP 2.6.0.0 download and instructions.
NOTE: USB Vendor ID / Product ID's have been reset to match Amazon stock OS for better compatibility
Enjoy
and remember if you like this product you can donate to TWRP at the top of this page:
http://www.teamw.in/project/twrp2
(Maybe mention [KFire2] in the donation so that they know what device you have)
WARNING: IF YOU INSTALLED THIS BEFORE TONIGHT(7/8) THEN I WOULD ADVISE RE-INSTALLING. I MADE SOME LAST MINUTE FIXES.
Hashcode said:
OP Updated with TWRP 2.6.0.0 download and instructions.
NOTE: USB Vendor ID / Product ID's have been reset to match Amazon stock OS for better compatibility
Enjoy
and remember if you like this product you can donate to TWRP at the top of this page:
http://www.teamw.in/project/twrp2
(Maybe mention [KFire2] in the donation so that they know what device you have)
WARNING: IF YOU INSTALLED THIS BEFORE TONIGHT(7/8) THEN I WOULD ADVISE RE-INSTALLING. I MADE SOME LAST MINUTE FIXES.
Click to expand...
Click to collapse
Flashed and looking good.
The WIPE screen has changed. Can I get a general consensus that choosing Advanced Wipe, and then choosing "Internal Storage" will still end in a bricked device, before anyone does it?
Thanks for your work on this Hashcode.
EDIT:
I normally create a backup and then copy it to my PC (Ubuntu 13.04), but I can't copy:
system.ext4.win
data.ext4.win
It gives me an error saying it can't copy them. I've tried a couple of times without joy.
Is there anything you want me to try?
chronicfathead said:
Flashed and looking good.
The WIPE screen has changed. Can I get a general consensus that choosing Advanced Wipe, and then choosing "Internal Storage" will still end in a bricked device, before anyone does it?
Thanks for your work on this Hashcode.
EDIT:
I normally create a backup and then copy it to my PC (Ubuntu 13.04), but I can't copy:
system.ext4.win
data.ext4.win
It gives me an error saying it can't copy them. I've tried a couple of times without joy.
Is there anything you want me to try?
Click to expand...
Click to collapse
Could be leaving those files open for some reason. Can you reboot back into recovery and try copying them again?
Also, the "Internal Storage" option under "Advanced Wipe" is for formatting /data + /sdcard. This should *NOT* result in a brick, but I haven't tested it personally.
Instructions have been changed slightly:
Swapped out the .img file for a flashable .zip file for use by those who already have TWRP installed.
Just download, toss on the SD card and flash in TWRP like anything else.
People who do not have TWRP installed should be using the 2nd-bootloader thread anyway.
Hashcode said:
Could be leaving those files open for some reason. Can you reboot back into recovery and try copying them again?
Also, the "Internal Storage" option under "Advanced Wipe" is for formatting /data + /sdcard. This should *NOT* result in a brick, but I haven't tested it personally.
Click to expand...
Click to collapse
I have rebooted into recovery and mounted USB storage, but it doesn't mount on my Ubuntu PC. The message I get is:
Unable to open MTP device '[usb:002,019]'
If I flick into the terminal in TWRP I see the following message:
E: Unable to locate volume information for USB storage mode.
Off to work. If you want me to try anything, just let me know.
chronicfathead said:
I have rebooted into recovery and mounted USB storage, but it doesn't mount on my Ubuntu PC. The message I get is:
Unable to open MTP device '[usb:002,019]'
If I flick into the terminal in TWRP I see the following message:
E: Unable to locate volume information for USB storage mode.
Off to work. If you want me to try anything, just let me know.
Click to expand...
Click to collapse
Sorry, you are correct. USB mounting inside recovery is not supported for any /data/media sharing type device. This includes the Galaxy Nexus and Nexus 4. :/
Best way to push/pull files from the device is via the Windows Command Line using adb.
To push files to the device:
adb push <filename> <destination>
example: adb push cm-10.1-otter2.zip /sdcard/Download
or to pull files from the device while in recovery:
adb pull /sdcard/Download/cm-10.1-otter2.zip
(This would pull the file from the device to whatever directory you are currently in)
or
adb sideload
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.5.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!
-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-Fixed a problem with md5 verification of backups
-Added a search function to libtar (thanks to kokotas)
-Improve handling of XML errors (fix permissions)
-Fixed handling of subpartitions
-Improvements to recovery.fstab flags
-Fixed a problem with decryption not being able to locate the decryption key in some situations
CHANGELOG for 2.4.4.0:
-Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
-More fixes for the file selector
-Switched from using busybox md5sum to a direct C function call
-Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
-Update exFAT to latest commits
-Added a build flag to disable using the ioctl for screen blanking
CHANGELOG for 2.4.3.0:
-Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
-Added a scroll bar to file selectors and listboxes courtesy of Tassadar
-Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
-Added a screen dim effect 2 seconds before screen off on some devices
-Finally fixed file selector crash (one of the joys of working with multi-threaded software)
-Fixed loading of screen timeout setting during startup
-Improvements and bugfixes to screen timeout code
-Fixed persistence of the 24 hour / military time setting
CHANGELOG for 2.4.2.0:
-Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
-Add a brightness setting (requires device specific setup and only some devices have been added)
-Add a root checker and offer to install SuperSU if the device isn't already rooted
-Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
-Check and offer to fix root permissions if broken
-Add an option for a 24 hour clock display instead of AM/PM (aka military time)
-Move stock recovery reflash check to occur during the reboot cycle
-Add support for some MTK6xxx devices
-Change libtar to vfork to help prevent memory problems
-Add a "clicked" effect to most buttons, file selector, and listbox
-Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
-Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
-Other minor bugfixes and improvements
CHANGELOG for 2.4.1.0:
-Fixed a problem with mkdosfs that formatted sdcards to 2GB
-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
CHANGELOG for 2.4.0.0:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!
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.
XDA:DevDB Information
[RECOVERY] TWRP 2.6.0.0 [2013-07-08], a Tool/Utility for the Sony Xperia Tablet Z
Contributors
Dees_Troy, bigbiff
Version Information
Status: Stable
Current Stable Version: 2.6.0.0
Stable Release Date: 2013-07-08
Created 2013-08-20
Last Updated 2013-08-20
Reserved
The images are built using pollux_windy compatible kernels, but if you're using the FOTAKernel setup, it will work with either model. If someone wants to come by #twrp and test builds for regular pollux I'll be happy to try to add support for that model as well.
pls add the information that its for pollux_windy only!
Followed the instruction but " no recoveries were found "
And if you put "for pollux ONLY" on the title that would be great
Sent from my SGP311 using xda app-developers app
I'm at a loss right now. I get up to the point where it's time to connect my tablet to the computer and when I press the volume up button it just flashes this blank screen until I give up. Also my computer doesn't recognize the device being plugged in when I reach this step. Both my mac and Windows computers. I'm at the point where I wanna either return it or pay someone to get twrp on it. I can't stand this Sony skin... I NEED CM 10!
XDA Moderation is contacting OP to clarify the TWRP is for a specific device version.
Thank You.
MD
Moscow Desire said:
XDA Moderation is contacting OP to clarify the TWRP is for a specific device version.
Thank You.
MD
Click to expand...
Click to collapse
AFAIK recovery is bundled within the boot image for Pollux* so we need to know also which kernel is bundled or if they support a multi loader (little kernel or whatever)
Inviato dal mio SGP311 usando Tapatalk 4
I'm just as lost. I'm trying to find a custom recovery for the "POLLUX" and not the "WINDY"
If it's of any use, I'll repeat here what I've already posted in a duplicate TWRP thread in this forum:
If you go to the Team Win website (use the link in the OP), then click on "get TWRP for my device" only the Pollux_windy (wifi only) version is shown.
Again, on the Team Win website, looking at the install instructions for TWRP on the Tablet Z Pollux_Windy, it's not straight forward which makes me think it can't be done using goo. Have a look here : http://www.teamw.in/project/twrp2/185
Very confusing.
is anyone using this recovery? feedback please. thanks
----------------
This was mentioned in the TWRP page
Code:
If you happen to be using lk, then boot your device into lk's fastboot mode and flash using this command:
fastboot flash recovery fotakernel.img
how do I know I'm using "lk"? thanks again
mrjayviper said:
how do I know I'm using "lk"? thanks again
Click to expand...
Click to collapse
If you don't know then you probably aren't using it. LK is a 3rd party bootloader ported to the TabZ
.........
can we fastboot flash this image file ?
golfinggino said:
can we fastboot flash this image file ?
Click to expand...
Click to collapse
No - Sony use a combined kernel/recovery so just flashing the TWRP imgage will not work.
You first have to go through the process of installing the "LK kernel". This effectively splits-out the kernel and recovery.
You can then "fastboot flash boot" the boot.img for whichever custom ROM you have, and then also "fastboot flash recovery" the TWRP recovery image.
See this thread : http://forum.xda-developers.com/showthread.php?t=2333826 , specifically posts #1,2,3,20,39,60,61.
I've done it and I've now got TWRP with my PAC ROM. The process was quite easy - but just watch the timings of when you press the volume buttons. Also, when the tablet goes into LK fastboot mode the LED is red. Bit of a bad choice of colour as it has caused some people to think their tablet has died.
to install TWRP on my stock and unlocked bootloader, I just used the adb commands mentioned in the TWRP site.
mrjayviper said:
to install TWRP on my stock and unlocked bootloader, I just used the adb commands mentioned in the TWRP site.
Click to expand...
Click to collapse
Maybe you have a link to the commands. I cant find it
egosapienz said:
Maybe you have a link to the commands. I cant find it
Click to expand...
Click to collapse
Half way down this page : http://www.teamw.in/project/twrp2/185
Try it out. Maybe I did something wrong but it didn't work for me - maybe it only works on stock ROM.
I had to install LK kernel to get TWRP with PAC ROM - see my post above
GretaLewd said:
Half way down this page : http://www.teamw.in/project/twrp2/185
Try it out. Maybe I did something wrong but it didn't work for me - maybe it only works on stock ROM.
I had to install LK kernel to get TWRP with PAC ROM - see my post above
Click to expand...
Click to collapse
Not shure if I should do it. Its for the WIFI-only Tab. My bootloader is locked too. But anyway thanx for the link
egosapienz said:
Not shure if I should do it. Its for the WIFI-only Tab. My bootloader is locked too. But anyway thanx for the link
Click to expand...
Click to collapse
Download the above file. Copy the file to /sdcard/fotakernel.img and run the following commands using terminal emulator or in adb shell:
su
dd if=/sdcard/fotakernel.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
------
I wouldn't do it if yours is the polux. it clearly says wifi only and there seems to be no TWRP for the LTE version.
mrjayviper said:
Download the above file. Copy the file to /sdcard/fotakernel.img and run the following commands using terminal emulator or in adb shell:
su
dd if=/sdcard/fotakernel.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
------
I wouldn't do it if yours is the polux. it clearly says wifi only and there seems to be no TWRP for the LTE version.
Click to expand...
Click to collapse
You´re right. I´ll wait. Thanx
[RECOVERY] [4/5/16] TWRP 3.2.1-0 - TeamWin Recovery Project
TeamWin is proud to present TWRP 3.2.1-0 for the Samsung Galaxy Note Pro 12.2 (Exynos and Qualcom)!
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project or twrp2 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
Decryption of /data
Easy selection of internal/external storage
See changelog below for new features
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 cache & dalvik, 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/omnirom/android_bootable_recovery
Gerrit for TWRP Official Device Configs - http://gerrit.twrp.me
Gerrit Instance - http://gerrit.omnirom.org
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.
v1awifi Device Config: TBD
Kernel: TBD
DOWNLOAD:
All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.
http://twrp.me
Support:
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers
Changelog
Please see http://twrp.me for release notes.
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.
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.
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
3.0.0.1
-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
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 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!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 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!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 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!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
2.8.7.1
v1awifi only
-Fix brightness slider
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)
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.
2.8.6.0
- Allow mulitple overlays for popup boxes (Dees_Troy)
- Add pattern style password entry for decrypt (Tassadar)
- Keyboard improvements (_that)
- Update AOSP base to 5.1 (Dees_Troy)
- Reduce theme count to 5 and rely on scaling (Dees_Troy)
- Various scaling improvements (Dees_Troy)
- Improved handling of resources in the GUI (_that)
- Make scroll bar size proportional to list size (_that)
- Allow scoll lists to render without a header (_that)
- Make console scroll per pixel with kinetic scrolling (_that)
- Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
- Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
2.8.5.0
- Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
- Improve thread handling and move input handling into the main rendering thread to improve stability
- Make MTP work even if unplugged and plugged back in
- Unify scrollable list code and make kinetic scrolling feel more natural
- Fix handling of mapped zip files for OTA updates (CM12 updater)
- USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
- Add Cancel Backup capability
- Other small fixes and improvements
2.8.4.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
- Fix some MTP related crashes and bugs
- Eliminate TWRP toggling USB IDs during boot if MTP is enabled
- Fix various adb sideload issues
- Improve threading of actions
- Eliminate separate thread for screen timeout
- Update libblkid to 2.25.0
- Use power button as back button on watch themes for easier navigation
- Add mutex locking to data manager
- Improve custom theme handling on encrypted devices
- Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
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
2.8.1.2
v1a3gxx
-add MODEM to backup
2.8.1.1
v1awifi/v1a3gxx
- add efs to backup
viennaltexx
-add MODEM to backup
2.8.1.1
- add efs to backup
2.8.1.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
- Temperature support - thanks to bigbiff
- Various other bugfixes and tweaks
2.8.0.0
- Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
- Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
- Add support for color in the console and give error, warning, and highlight lines different colors
- Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
- Improve handling of /misc thanks to mdmower
- Improve setting of time on Qualcomm devices thanks to [NUT]
- Allow using images on slidervalue GUI objects thanks to Tassadar
- Allow using variables and addition and subtraction in variables for easier theming
- Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
- Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
- Other minor fixes and improvements
2.7.1.1 viennaltexx only
- fix viennaltexx booting
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. 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
2.7.0.2
Fix backup/restore to external SD Card
2.7.0.1
Fix cache formatting by allowing secure discard. This means it will take 5 minutes to wipe cache.
Reserved2
You are awesome. Thank you for the recovery....!
Thank you...
Sent from my SM-P900 using XDA Premium 4 mobile app
Awesome! Thanks so much. Will be sending bounty donation along next pay check.
Worked perfectly here on SM-P900. Installed via Odin 3.09. Tried a backup to ext-sd, and it worked as well. Thanks bigbiff (et al. )
Sent from my SM-P900 using Tapatalk
This is great. Is TWRP being developed also for the SM-P905 ?
Yup, Works perfectly. I'm proud to say I was the first user with a P900 to have a working TWRP thanks to bigbiff.
Mike02z said:
Yup, Works perfectly. I'm proud to say I was the first user with a P900 to have a working TWRP thanks to bigbiff.
Click to expand...
Click to collapse
Yours shows 2.7.0.2, but the downloadable version is 2.7.0.0. Difference?
Also I see twrp has a problem mounting cache partition. At least on mine.
Sent from my VS980 4G using XDA Premium HD app
icem237 said:
Yours shows 2.7.0.2, but the downloadable version is 2.7.0.0. Difference?
Also I see twrp has a problem mounting cache partition. At least on mine.
Sent from my VS980 4G using XDA Premium HD app
Click to expand...
Click to collapse
Yes mine too
Sent from my Nexus 7 using Tapatalk
In case anyone doesnt know.... I tried formating cache and dalvik . dalvik went fine but since twrp cant mount cache partition it errors . Now i experience a boot loop on the samsung logo. Can get back in to twrp no problem. Just need the stock image for SM-P9000ZWFXAR. Sam Mobile or samsung it self doesnt have it available.
icem237 said:
In case anyone doesnt know.... I tried formating cache and dalvik . dalvik went fine but since twrp cant mount cache partition it errors . Now i experience a boot loop on the samsung logo. Can get back in to twrp no problem. Just need the stock image for SM-P9000ZWFXAR. Sam Mobile or samsung it self doesnt have it available.
Click to expand...
Click to collapse
the exact same thing happened to me, I downloaded the firmware from Peru on sammobile (I'm in us) and it worked.
Sent from my SPH-L720 using Tapatalk
hendav said:
the exact same thing happened to me, I downloaded the firmware from Peru on sammobile (I'm in us) and it worked.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Thanks for the info.... Why peru? just curious?
Sweet to see this come to the Note Pro. Once the cache wipe issue gets resolved, this will be an insta install on mine, as well as yet another donation to TWRP.
2.7.0.2 in Mike's screenshot was just me being lazy not resetting the version number when testing.
I already have -DNO_SECURE_DISCARD in BoardConfig so cache should be formatting...
Can someone with this issue post /tmp/recovery.log?
bemanet said:
This is great. Is TWRP being developed also for the SM-P905 ?
Click to expand...
Click to collapse
Adding to my port list. Can you provide stock recovery?
icem237 said:
Thanks for the info.... Why peru? just curious?
Click to expand...
Click to collapse
I was told by a samsung tech that it doesn't matter where you download from, as long as you get a good download speed and it is the most recent firmware. Everything seems to be fine so far.
Sent from my SPH-L720 using Tapatalk
Very odd. During my testing I ran a full backup. I rebooted into the OS then went back into recovery and then restored the backup. It restored fine. It wiped the cache partition and restored it.
When I just tested wiping cache from the advanced wipe menu, It says it is wiping cache but never completes. When I reboot it goes right into TWRP. When I tell it to reboot system it gets passed the initial Samsung splash screen and the Samsung logo and music starts but the music gets cut off and it just sits at that logo.Mine appeared frozen but was not boot looping.
I went back into TWRP and restored my backup and it again wiped cache and formatted it fine. After it completed I booted normally. Not sure why it is wiping and restoring fine but is not wiping from the advanced wipe function.
BTW, there is no /tmp directory in my SM900 or I would have posted the recovery.log. Is is somewhere else?
Mike02z said:
Very odd. During my testing I ran a full backup. I rebooted into the OS then went back into recovery and then restored the backup. It restored fine. It wiped the cache partition and restored it.
When I just tested wiping cache from the advanced wipe menu, It says it is wiping cache but never completes. When I reboot it goes right into TWRP. When I tell it to reboot system it gets passed the initial Samsung splash screen and the Samsung logo and music starts but the music gets cut off and it just sits at that logo.Mine appeared frozen but was not boot looping.
I went back into TWRP and restored my backup and it again wiped cache and formatted it fine. After it completed I booted normally. Not sure why it is wiping and restoring fine but is not wiping from the advanced wipe function.
BTW, there is no /tmp directory in my SM900 or I would have posted the recovery.log. Is is somewhere else?
Click to expand...
Click to collapse
/tmp should be created in twrp ramdisk on boot. It will go away on reboot. I am not sure what is going on unless there is something in cache that is needed on boot. Can you see if logcat is working on the Samsung screen?
bigbiff said:
/tmp should be created in twrp ramdisk on boot. It will go away on reboot. I am not sure what is going on unless there is something in cache that is needed on boot. Can you see if logcat is working on the Samsung screen?
Click to expand...
Click to collapse
OK, let me try again and see if I can get it.
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.
Device page with manual instructions on our website.
Download folders with prior versions:
Mirror 1
Mirror 2
Thanks to Adam77Root for supporting the p880 in OmniROM and helping to make TWRP official for this device!
Hey Dees_Troy happy to see you here.
Thanks for the always awesome work.
Salut
Sent from my LG-V500 using Tapatalk
Great thx seems you are on Androidpolice congrats Dees_Troy and Adam77root
thanks to Dees_Troy and Adam77root for the official support of twrp for P880 ! :highfive:
great recovery.:good:
Why is there no f2fs support?
sprite048 said:
Why is there no f2fs support?
Click to expand...
Click to collapse
you be of good cheer. they just started working.
---edit---
How do you know that no service f2fs?
File openrecovery-twrp-2.7.1.0-p880.img is dated 2014-07-21 so it is current with changes in version 2.7.1.0
You carefully read the changelog for this version in the first post.
What?
srsly. "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."
Installed it and working good. Please add support for f2fs file sytem...:good:
ze7zez said:
you be of good cheer. they just started working.
---edit---
How do you know that no service f2fs?
File openrecovery-twrp-2.7.1.0-p880.img is dated 2014-07-21 so it is current with changes in version 2.7.1.0
You carefully read the changelog for this version in the first post.
Click to expand...
Click to collapse
Since it's based on an fstab and cannot accept some partitions as auto (like system, cache, data) it won't work with an f2fs installation. IOW, if it's not built with a specific fstab it won't work with f2fs.
It should be noted that unless you are running a massive sql server on your phone or writing copious amounts to data f2fs is about half as fast as ext4.
It's not an improvement in any way and just like with most of the additions that grouper devs add, this isn't an addition that you'll want either.
File systems take decades to mature, in 2024 i'm sure it will be considered either the best or the worst file system for a phone but at this point in time it's meh.
You see, sequential reads is a big deal on a hard drive but not as big as random reads so on an actual hard drive this would be a MASSIVE improvement, on a static memory all reads are sequential and f2fs has half the performance on sequential reads compared to ext4.
The only file system i'm aware of that would be faster is xfs.
IcanhasLG said:
(...) You see, sequential reads is a big deal on a hard drive but not as big as random reads so on an actual hard drive this would be a MASSIVE improvement, on a static memory all reads are sequential and f2fs has half the performance on sequential reads compared to ext4.
The only file system i'm aware of that would be faster is xfs.
Click to expand...
Click to collapse
I see you have the same opinion as the @iodak.
To the opinion referred @Demetris.
I personally think that every technology has its advantages and disadvantages.
Do not always use the best, but the most optimal.
.
@IcanhasLG
You're absolutely right.XFS is a high-end data processing.It can be referred to as the file systems in a file system.
Only so much about it.
there are some reports about a version 2.7.1.1
Is it existing ?
Where is the code and changelog to 2.7.1.0 ?
That's what found :
hat'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 restoreImprovements to USB storage handlingAdded a class to search for files to make finding the correct brightness file automatic in most casesVarious other bugfixes and tweaks
Best regards
TWRP 2.8 rocks. Thanks.?
TWRP 2.8
TWRP 2.8 working fine. Thanks a lot!
I just was not able to flash it through TWRP app and had to use the terminal command:
su
cat /mnt/sdcard/openrecovery-twrp-2.8.0.1-p880.img >/dev/block/mmcblk0p1
sync
The image is in: http://techerrata.com/browse/twrp2/p880
2.8.0.1 works fine. Thanks ! :victory:
I will wait for a MultiROM build from @Adam77Root. Or someone else brings this up...
Fladder72 said:
I will wait for a MultiROM build from @Adam77Root. Or someone else brings this up...
Click to expand...
Click to collapse
It's on the way, will release it soon.
openrecovery-twrp-2.8.1.0-p880.img
working very fine! :good: