FORUMS
Remove All Ads from XDA

[TOOL/UTILITY][TWRP][3.0][RECOVERY] TWRP 3.0.2-0 TeamWin Recovery Project 4/5

6,350 posts
Thanks Meter: 5,649
 
By bigbiff, Senior Recognized Developer on 6th September 2015, 09:02 PM
Post Reply Email Thread
[RECOVERY] [4/5/16] TWRP 3.0.2-0 - TeamWin Recovery Project

TeamWin is proud to present TWRP 3.0.2-0 for the Samsung Galaxy Note 5 (GSM)!



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
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.

noblelte Device Config: https://github.com/TeamWin/android_d...msung_noblelte

Kernel: https://github.com/TeamWin/android_k...msung_noblelte

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
The Following 30 Users Say Thank You to bigbiff For This Useful Post: [ View ]
 
 
6th September 2015, 09:04 PM |#2  
OP Senior Recognized Developer
Thanks Meter: 5,649
 
Donate to Me
More
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.
2.8.7.1
- fix OTG

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.
The Following 5 Users Say Thank You to bigbiff For This Useful Post: [ View ]
6th September 2015, 09:06 PM |#3  
OP Senior Recognized Developer
Thanks Meter: 5,649
 
Donate to Me
More
Known working:
SM-N920T - note 5 tmobile
SM-G928G - s6 edge +
The Following 4 Users Say Thank You to bigbiff For This Useful Post: [ View ]
7th September 2015, 03:09 AM |#4  
mocsab's Avatar
Senior Member
Flag West Milwaukee
Thanks Meter: 1,323
 
More
Quote:
Originally Posted by bigbiff

Known working on Tmobile Note 5 so far.

AWESOME - will be flashing soon - thanks - as always for your work - it is greatly appreciated!

Flashed and booted successfully into recovery -but saw somethnig I have never seen before -

System partitian unmodivied twrp can leave your system partitian unmodified to make it easier for you to take official updates. Twrp will be unable to prevent stock rom from replacing twrp and will not offer to root your device.

Swipe to allow modification...

I assume this means if I select allow modification - it will flash as normal but then would not allow official updates - is that correct?

ALso - OTG is not currently working - hoping this will be taken care of sometime in the future?

I have never seen this before and wondered what the ramifications of this are?
7th September 2015, 03:40 AM |#5  
Crushader's Avatar
Senior Member
Flag Melbourne
Thanks Meter: 80
 
More
I had problem installing this through ODIN using img.tar.md5, it would failed to download to device and the device would not boot system/receovery , I had to download the img file and flash it using flashify since CWM doesn't do img flashing. Will there be zip file available in near future? Other than that, so far so good everything is working as usual!
7th September 2015, 04:13 AM |#6  
mocsab's Avatar
Senior Member
Flag West Milwaukee
Thanks Meter: 1,323
 
More
Quote:
Originally Posted by Crushader

I had problem installing this through ODIN using img.tar.md5, it would failed to download to device and the device would not boot system/receovery , I had to download the img file and flash it using flashify since CWM doesn't do img flashing. Will there be zip file available in near future? Other than that, so far so good everything is working as usual!

When I flashed the TWRP Tar in Odin - it flashed and then seemed to hangup at the end when it was clearly finished flashing - it just sat there for a while - maybe 20 seconds - but then it completed the flash and booted immediately into TWRP when I saw the initial warning/tip I mentioned in my previous post - but it did complete the flash from ODIN it just took longer than usual.
7th September 2015, 04:18 AM |#7  
Crushader's Avatar
Senior Member
Flag Melbourne
Thanks Meter: 80
 
More
Quote:
Originally Posted by mocsab

When I flashed the TWRP Tar in Odin - it flashed and then seemed to hangup at the end when it was clearly finished flashing - it just sat there for a while - maybe 20 seconds - but then it completed the flash and booted immediately into TWRP when I saw the initial warning/tip I mentioned in my previous post - but it did complete the flash from ODIN it just took longer than usual.

Mine just flashed and then it failed right away and download mode stays on, tried to reboot to recovery to test but it have me an error something about update system failed, try to restore from smart switch on PC. Sop I had to go back to arter's custom CWM from ODIN and then the phone boots up again. Lucky that Flashify managed to flash TWRP img file and everything is working. My model is N920I.
The Following User Says Thank You to Crushader For This Useful Post: [ View ] Gift Crushader Ad-Free
7th September 2015, 12:33 PM |#8  
AlMaghraby's Avatar
Senior Member
Thanks Meter: 573
 
More
GSM means international lte version ? like n920C ?
7th September 2015, 02:10 PM |#9  
OP Senior Recognized Developer
Thanks Meter: 5,649
 
Donate to Me
More
Quote:
Originally Posted by mocsab

AWESOME - will be flashing soon - thanks - as always for your work - it is greatly appreciated!

Flashed and booted successfully into recovery -but saw somethnig I have never seen before -

System partitian unmodivied twrp can leave your system partitian unmodified to make it easier for you to take official updates. Twrp will be unable to prevent stock rom from replacing twrp and will not offer to root your device.

Swipe to allow modification...

I assume this means if I select allow modification - it will flash as normal but then would not allow official updates - is that correct?

ALso - OTG is not currently working - hoping this will be taken care of sometime in the future?

I have never seen this before and wondered what the ramifications of this are?

I will look at enabling OTG soon. 5.1.1 on all phones introduced dm-verity on the system partition. If it gets modified, OEM updates are disabled, and the OEM kernel will fail to boot. If you want to keep completely stock, you need to keep the system r/o

Flashing custom roms/kernels with this turned off will make it so you can have it r/w. R/O will backup the entire system as an image using dd.
The Following 2 Users Say Thank You to bigbiff For This Useful Post: [ View ]
7th September 2015, 03:08 PM |#10  
mocsab's Avatar
Senior Member
Flag West Milwaukee
Thanks Meter: 1,323
 
More
Quote:
Originally Posted by bigbiff

I will look at enabling OTG soon.

awesome - if you need help testing it (I helped you with that on the S6) just let me know
7th September 2015, 03:11 PM |#11  
OP Senior Recognized Developer
Thanks Meter: 5,649
 
Donate to Me
More
Quote:
Originally Posted by AlMaghraby

GSM means international lte version ? like n920C ?

All GSM versions should potentially work.
The Following User Says Thank You to bigbiff For This Useful Post: [ View ]
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes