Related
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.
Reserved
Based on the work and assistance of @jmz so thanks very much to him.
Device specific page on our website.
Download link to current and past versions
Official TWRP, nice!
Flashing now.
I'm confused I am already running 2.7.0.4
Why is this version showing 2.7.0.0?
Yay!!! Thank you Sir!
work for gpe?
jimmydigital00 said:
I'm confused I am already running 2.7.0.4
Why is this version showing 2.7.0.0?
Click to expand...
Click to collapse
Latest is actually 2.7.0.2
NJGSII said:
Latest is actually 2.7.0.2
Click to expand...
Click to collapse
True, but it still doesn't explain why this thread is saying that version 2.7.0.0 came out today when they already officially released 2.7.0.2 two days ago. I followed the links provided in the OP, and they end up leading to what we already have been provided. So at least we know this is an error in the thread title, not something new/different.
Gamesoul Master said:
True, but it still doesn't explain why this thread is saying that version 2.7.0.0 came out today when they already officially released 2.7.0.2 two days ago. I followed the links provided in the OP, and they end up leading to what we already have been provided. So at least we know this is an error in the thread title, not something new/different.
Click to expand...
Click to collapse
This thread says a different version number because this version has been ported by the original developer. One of the ones behind the development of TWRP2. The other was a port by Jmz
I followed the link and it definitely doesn't lead to the same downloads, the other ports were hosted on jmz's server.
Sent from my HTC One_M8 using Tapatalk
superchilpil said:
This thread says a different version number because this version has been ported by the original developer. One of the ones behind the development of TWRP2. The other was a port by Jmz
I followed the link and it definitely doesn't lead to the same downloads, the other ports were hosted on jmz's server.
Click to expand...
Click to collapse
They *were*, yes. But he changed that a couple days ago when 2.7.0.2 was officially released. The thread title says the official version is 2.7.0.0 and was released today. But their own official download page says the latest official version is 2.7.0.2 and was released 2 days ago.
superchilpil said:
I followed the link and it definitely doesn't lead to the same downloads, the other ports were hosted on jmz's server.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Wrong answer Sir. Links to the images are exactly the same.
Gesendet von meinem HTC One_M8 mit Tapatalk
no
shorty1483 said:
Wrong answer Sir. Links to the images are exactly the same.
Gesendet von meinem HTC One_M8 mit Tapatalk
Click to expand...
Click to collapse
Then the MD5 does not match, why?
CC
cc999 said:
Then the MD5 does not match, why?
CC
Click to expand...
Click to collapse
I did not refer to the File itself , I stated that the LINKS are the same. Both redirect to techerrata and the latest version openrecovery-twrp-2.7.0.2-m8.img, even the link from TWRP official. The only TWRP 2.7.0.0 existing is for the Sprint variant of M8.
question
shorty1483 said:
I did not refer to the File itself , I stated that the LINKS are the same. Both redirect to techerrata and the latest version openrecovery-twrp-2.7.0.2-m8.img, even the link from TWRP official. The only TWRP 2.7.0.0 existing is for the Sprint variant of M8.
Click to expand...
Click to collapse
There is the .04 and .02, so I am assuming the .02 is the official release for the M8.
The .04 and .02 MD5 do not match so they are NOT the same file/version. correct?
CC
cc999 said:
There is the .04 and .02, so I am assuming the .02 is the official release for the M8.
The .04 and .02 MD5 do not match so they are NOT the same file/version. correct?
CC
Click to expand...
Click to collapse
jmz 2.7.0.4 = official 2.7.0.2 -> same functions as stated in jmz's thread, but different MD5 due to different build process.
TWRP Team built the official one using the unofficial of jmz as stated in the OP and described in jmz's thread also.
shorty1483 said:
jmz 2.7.0.4 = official 2.7.0.2 -> same functions as stated in jmz's thread, but different MD5 due to different build process.
TWRP Team built the official one using the unofficial of jmz as stated in the OP and described in jmz's thread also.
Click to expand...
Click to collapse
THE MD5 DOES NOT MATCH BECAUSE JMZ EDITED THE VERSION NUMBER TO REFLECT .04, INSTEAD OF .02.
Other than that, they are IDENTICAL. Tell 'em to open it himself in a hex editor if he doesn't believe they are the same.
From the site the TWRP for HTC One m8 2014 GSM [m8] is for the HTC One International / Asia version?
MCube74 said:
From the site the TWRP for HTC One m8 2014 GSM [m8] is for the HTC One International / Asia version?
Click to expand...
Click to collapse
Yes, the other ones are Sprint and Verizon.
anybody tested on gpe ?
Listen guys. I worked on TWRP and did my own version number to keep everything straight. My builds were unofficial. I got with @Dees_Troy and he took it official with official numbering scheme.
My 2.7.0.4 is exactly the same as official 2.7.0.2. The reason the MD5s are different are 1) different version number imbedded and 2) I use a different tree to build in from dees.
This is for all variants of the Desire 601
From their site (comments in green are added by me):
Team Win Recovery Project 2.x, or twrp2 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.
Up-to-date phone look photos:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What's new in 2.8.6.0:
Fix daylight savings time rules for USA and Europe (_that)
Allow multiple 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 scroll 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 consistency (Dees_Troy)
Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
What's new in 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
Other small fixes and improvements
What's new in 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
What's new in 2.8.3.0:
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
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
What's new in 2.8.2.0:
(This build was only officially released on select [mainly nexus] devices)
Pull in all changes from Android 5.0 lollipop into TWRP
Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
Revert some changes to exFAT that were breaking exFAT support on some devices
Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
What's new in 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
What's new in 2.8.0.1:
Fix a bug that caused weird graphics and touch issues
What's new in 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
Including screenshots: "Power"+"Volume Down" will now save a screenshot to /external_sdcard/pictures/screenshots.
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
What's new in 2.7.1.0:
Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
Various bugfixes to backup and restore
Improvements to USB storage handling
Added a class to search for files to make finding the correct brightness file automatic in most cases
Various other bugfixes and tweaks
What's new in 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.
What's new in 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
NOTES:
This is the official version of TWRP for our device only modified with the updated partition mount points as changed by the KitKat OTA.
I have also modified it to display the version to show "(KK)" to visibly distinguish it from the official version.
This is only for Desire 601 users who have updated to KitKat or, at the very least, attempted the update and had their partitions remapped. If you have not updated to KitKat using the OTA you need to use the original version which can be found on their website here.
This is for all variants of the Desire 601 - zara_cl and zara_ul
DOWNLOAD:
Three links are available for you to download from:
1) My Google Drive
2) Dev-Host
3) Click the "Downloads" button at the top of this post (you can also find links to the previous versions there).
Known Issues:
- These issues are present in the official version. -
MTP is currently not supported on this device.
When you select Advanced Wipe from the Wipe screen you will see Data listed twice. Fixed in 2.8.0.2 (KK)
Changelog:
2.8.6.0 (KK) - 3/27/2015
Uses official TWRP version 2.8.6.0 uploaded 3/26/2015
Incorporates all previous changes
2.8.5.0 (KK) - 2/12/2015
Uses official TWRP version 2.8.5.0 uploaded 2/11/2015
Incorporates all previous changes
2.8.4.0 (KK) - 1/13/2015
Uses official TWRP version 2.8.4.0 uploaded 1/12/2015
Incorporates all previous changes
2.8.3.0 (KK) - 12/24/2014
Uses official TWRP version 2.8.3.0 uploaded 12/22/2014
Changed it so devices will show as "zara" in recovery instead of "zaracl"
Incorporates all previous changes
2.8.1.0 (KK) - 11/01/2014
Uses official TWRP version 2.8.1.0 uploaded 10/22/2014
Incorporates all previous changes
2.8.0.2 - 10/05/2014
Uses official TWRP version 2.8.0.1 uploaded 9/12/2014
Fixed bug in official version with "Data" partition showing twice under Advanced Wipe options.
2.8.0.1 - 9/12/2014
Uses official TWRP version 2.8.0.0 uploaded 9/09/2014
XDA:DevDB Information
TWRP Recovery for Desire 601 KitKat Devices, Tool/Utility for the HTC Desire 601
Contributors
-Duir-
Version Information
Status: Stable
Current Stable Version: 2.8.6.0 (KK)
Stable Release Date: 2015-03-27
Created 2014-09-12
Last Updated 2015-03-27
Thank you so much for keeping us updated Duir [emoji2]
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
If I understand this correctly
HTML:
fastboot flash recovery openrecovery-twrp-2.8.0.1-zara.img
on a HTCdev unlocked kitkat zara will give me s-off and twrp recovery
Wohoo!!! thanks Duir!
I know you wont let us down for an update
conductive said:
If I understand this correctly
HTML:
fastboot flash recovery openrecovery-twrp-2.8.0.1-zara.img
on a HTCdev unlocked kitkat zara will give me s-off and twrp recovery
Click to expand...
Click to collapse
No, S-off is a whole different process to get.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
conductive said:
If I understand this correctly
HTML:
fastboot flash recovery openrecovery-twrp-2.8.0.1-zara.img
on a HTCdev unlocked kitkat zara will give me s-off and twrp recovery
Click to expand...
Click to collapse
Sweet!
Thanks for the great work Duir!!
Debian Jessie/Sid 64 and mrplowdan's "Hint" (above) did the trick
While running backup ...... Swipe to unlock >>>>>Swipe to install SuperSU....
After reboot
<tampered>
<unlocked>
s-on
per freshly installed SuperSU ......"SuperSU is not fully installed-your device is not yet fully rooted"
go to Play store or download flashable zip and install through TWRP.
Edit: downloaded SuperSU update zip, installed through twrp and I still can not get s-off even after setting enable SU on boot. Must need full SuperSU from play store or????
Hedied4me said:
No, S-off is a whole different process to get.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Click to expand...
Click to collapse
I thought it should work
http://forum.xda-developers.com/desire-601/help/how-to-root-htc-desire-601-t2831084
Hedied4me said:
No, S-off is a whole different process to get.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Click to expand...
Click to collapse
I am officially stuck
Per Duir s-off rumrunner guide
BEFORE YOU DO ANYTHING MAKE A BACKUP UP YOUR DEVICE (INCLUDING BOOT.IMG)
Click to expand...
Click to collapse
I can perform a backup with TWRP but I can not figure out how to move it to my microSD or mount the data partition.
Edit: I can also mount the SD with TWRP for a back-up all is good.
Thanks again for keeping us updated Duir. Running great so far.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Why do you have 2x data partition? I have data and Internal storage. I build TWRP with my cm11 device tree and everything works fine...
patrik.KT said:
Why do you have 2x data partition? I have data and Internal storage. I build TWRP with my cm11 device tree and everything works fine...
Click to expand...
Click to collapse
It's mentioned in the OP.
-Duir- said:
It's mentioned in the OP.
Click to expand...
Click to collapse
I know, I read it, but I meant why is it like that? In the TWRP I built (for multirom to test roms) I have Data and Internal storage, not 2x Data. http://i.imgur.com/UMLYcrt.png http://i.imgur.com/K8tfgsu.png (Yes, I know it's 2.7, but you had this bug in your 2.7 too)
patrik.KT said:
I know, I read it, but I meant why is it like that? In the TWRP I built (for multirom to test roms) I have Data and Internal storage, not 2x Data. http://i.imgur.com/UMLYcrt.png http://i.imgur.com/K8tfgsu.png (Yes, I know it's 2.7, but you had this bug in your 2.7 too)
Click to expand...
Click to collapse
-Duir- said:
NOTES:
This is the official version of TWRP for our device only modified with the updated partition mount points as changed by the KitKat OTA.
I have also modified it to display the version "v2.8.0.1 (KK)" to visibly distinguish it from the 2.8.0.0 official version.
This is only for Desire 601 users who have updated to KitKat or, at the very least, attempted the update and had their partitions remapped. If you have not updated to KitKat using the OTA you need to use the original version which can be found on their website here.
This is for all variants of the Desire 601 - zara_cl and zara_ul
Known Issues:
- These issues are present in the official version. -
MTP is currently not supported on this device.
When you select Advanced Wipe from the Wipe screen you will see Data listed twice. The second data is actually Internal Storage, so use caution when wiping your device (see the Screenshots section)
Click to expand...
Click to collapse
I being quite literal in what I put there. This is TWRP's official build for the phone, just with updated mount points. Any issues with official will exist here because, for all intents and purposes, it is official TWRP. Fixing the mount points for KK requires no compiling.
New Version 2.8.0.2 available!
So I missed Team Win releasing an update shortly after releasing 2.8.0.0
Sorry about that but I do think the result is worth it.
-Duir- said:
Changelog:
2.8.0.2 - 10/05/2014
Uses official TWRP version 2.8.0.1 uploaded 9/12/2014
Fixed bug in official version with "Data" partition showing twice under Advanced Wipe options.
Click to expand...
Click to collapse
Thanks bud, works great.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
New version available! Links in the first post.
In an effort to keep things less confusing I'm no longer bumping the version number. Starting with this version all updates will keep official version number and just simply have "(KK)" added to it.
-Duir- said:
Changelog:
2.8.1.0 (KK) - 11/01/2014
Uses official TWRP version 2.8.1.0 uploaded 10/22/2014
Click to expand...
Click to collapse
-Duir- said:
New version available! Links in the first post.
In an effort to keep things less confusing I'm no longer bumping the version number. Starting with this version all updates will keep official version number and just simply have "(KK)" added to it.
Click to expand...
Click to collapse
The new recovery works like a charm. Thanks for keeping us updated Duir.
Sent from my cdma 4.4.2 Virgin Mobile HTC Desire 601 zara_cl
New version available, all links in OP updated.
Be advised, for some reason Avast is popping up a security threat message on all Dev-Host links. Not sure if it's a false-positive with their site or something is up, but wanted to let you know and say you may want to download from one of the other two sources for now.
Merry Xmas all
-Duir- said:
Changelog:
2.8.3.0 (KK) - 12/24/2014
Uses official TWRP version 2.8.3.0 uploaded 12/22/2014
Changed it so devices will show as "zara" in recovery instead of "zaracl"
Click to expand...
Click to collapse
As always thanks for keeping us updated Duir.
New version available, all links in OP updated.
No issues with Dev-Host links.
-Duir- said:
Changelog:
2.8.4.0 (KK) - 1/13/2015
Uses official TWRP version 2.8.4.0 uploaded 1/12/2015
Incorporates all previous changes
Click to expand...
Click to collapse
[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 4 (Verizon)!
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.
trltevzw Device Config: TBD
Kernel: https://github.com/bigbiff/android_kernel_samsung_trlte
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.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.
- 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.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.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
Reserved2
Reserved3
Retail version??
Mark.Y said:
Retail version??
Click to expand...
Click to collapse
This is for the Developer Version only.
Thanks for the Verizon twrp. However I installed the Tmobile version when I got my dev Note4, which seems to work ok. What's the difference, and should I odin the newer version?
Sent from my Dev Note 4
You don't need to Odin....you can just flash the flashable zip with your current version of TWRP. The major reason to change is that there could be problems flashing ROMS if the recover does not include the VZW asserts etc (when they start showing up) and also.. @bigbiff thanks for letting me test the pre-release version and giving input !!
Sent from my SCH-I605 / Galaxy Note 2 / JB 4.3 / Unlocked, Rooted, ROMed and AGNi-fied !!... using Tapatalk v 2.4.13
couldn't root
Just wanted to share my experience with rooting my dev edition.
I had the T-Mobile Twrp installed and updated to the Verizon one (this one). Supersu kept failing to install in Twrp and also through the play store. I went back to the T-Mobile Twrp and flashed the supersu zip and it had no issue installing.
droidrev71 said:
Just wanted to share my experience with rooting my dev edition.
I had the T-Mobile Twrp installed and updated to the Verizon one (this one). Supersu kept failing to install in Twrp and also through the play store. I went back to the T-Mobile Twrp and flashed the supersu zip and it had no issue installing.
Click to expand...
Click to collapse
=========
I have only used the VZW version....if you have the Tmo version all you need to do is use flashable zip and flash VZW version from the Tmo version.....should have no issues with SuperSU...everything you flashed originally will still be there...no need to re- root.
Sent from my SCH-I605 / Galaxy Note 2 / JB 4.3 / Unlocked, Rooted, ROMed and AGNi-fied !!... using Tapatalk v 2.4.13
manbat said:
=========
I have only used the VZW version....if you have the Tmo version all you need to do is use flashable zip and flash VZW version from the Tmo version.....should have no issues with SuperSU...everything you flashed originally will still be there...no need to re- root.
Sent from my SCH-I605 / Galaxy Note 2 / JB 4.3 / Unlocked, Rooted, ROMed and AGNi-fied !!... using Tapatalk v 2.4.13
Click to expand...
Click to collapse
I didn't re root. I bought the phone with T-Mobile Twrp installed and not rooted. I updated to vzw Twrp before rooting and couldn't. Like i said i had to go back to tmobile Twrp to be able to root. When i flashed the zip in vzw Twrp it failed.
Thanks for the clarification. ..I have used the test version(Odin), flashed the release version (Zip Flashed) and now I am running a "custom" version that I decompiled and re-skinned....all from the vzw base. Glad that what you have is working for you.
Sent from my SCH-I605 / Galaxy Note 2 / JB 4.3 / Unlocked, Rooted, ROMed and AGNi-fied !!... using Tapatalk v 2.4.13
Here is where I'm at...
On 30th October 2014 I used Odin to flash my Verizon Note 4 D E with the T-Mobil TWRP recovery( "openrecovery-twrp-2.8.1.1-trltetmo.img.tar"). That was before the Verizon TWRP recovery came out. So I have Team Win Recovery but I have not rooted the phone yet.
-------------------------------------------------------------------------------------------------------------
I read post http://forum.xda-developers.com/showpost.php?p=56496836&postcount=8 had some issues .
At this point what do I need to do to get on the right track and root my Verizon Note 4 D E.
Flash this zip of TWRP (trltevzw 2.8.1.1) in your current version of TWRP Link:
http://www.techerrata.com/file/twrp2/trltevzw/openrecovery-twrp-2.8.1.1-trltevzw.zip
Then Reboot Recovery from within TWRP and flash this SuperSU zip. Link:
http://download.chainfire.eu/593/SuperSU/BETA-SuperSU-v2.19.zip
Make sure you have both of the zips saved to your SD Card before you start. After you flash SuperSU ...reboot system and phone will reboot. You will have SuperSU in your app drawer. Tap on SuperSU Icon and follow instructions.
Good luck. !!
Sent from my SM-N910V DE / Note 4 / TWRP 2.8.1.1 trltevzw
OK, Thnaks...
manbat said:
Flash this zip of TWRP (trltevzw 2.8.1.1) in your current version of TWRP Link:
http://www.techerrata.com/file/twrp2/trltevzw/openrecovery-twrp-2.8.1.1-trltevzw.zip
Then Reboot Recovery from within TWRP and flash this SuperSU zip. Link:
http://download.chainfire.eu/593/SuperSU/BETA-SuperSU-v2.19.zip
Make sure you have both of the zips saved to your SD Card before you start. After you flash SuperSU ...reboot system and phone will reboot. You will have SuperSU in your app drawer. Tap on SuperSU Icon and follow instructions.
Good luck. !!
Sent from my SM-N910V DE / Note 4 / TWRP 2.8.1.1 trltevzw
Click to expand...
Click to collapse
It looks like XDA forums abbreviated your link address. What I actually downloaded was [ openrecovery-twrp-2.8.1.1-trltevzw.zip ] and [ BETA-SuperSU-v2.19.zip ] are these the correct files? And NOT THE .md5 file on the same download page. Just want to be sure . I will do it tonight.
Thanks
EDIT: I just realized, This just shows my stupidity. I dont know how to use the md5 file. Any how the zip files should be good right?
If you are flashing from your current TWRP yes trltevzw zip....if you are flashing from odin you need the other. The SuperSU is the current beta...I run It on all my phones....there is a "stable" version....but I have no problems with this beta.
Sent from my SCH-I605 / Galaxy Note 2 / JB 4.3 / Unlocked, Rooted, ROMed and AGNi-fied !!... using Tapatalk v 2.4.13
OK, Thanks,
manbat said:
If you are flashing from your current TWRP yes trltevzw zip....if you are flashing from odin you need the other. The SuperSU is the current beta...I run It on all my phones....there is a "stable" version....but I have no problems with this beta.
Sent from my SCH-I605 / Galaxy Note 2 / JB 4.3 / Unlocked, Rooted, ROMed and AGNi-fied !!... using Tapatalk v 2.4.13
Click to expand...
Click to collapse
I installed twrp-2.8.1.1-trltevzw.zip then did a factory reset and rebooted. All is good.
What all should i include in my first backup with twrp before I flash the SuperSU file?
For first "stock" backup I check box everything but recovery...makes a good sized file. After rooting I do the same thing. Just my preference...makes an easy full restore.
Sent from my SCH-I605 / Galaxy Note 2 / JB 4.3 / Unlocked, Rooted, ROMed and AGNi-fied !!... using Tapatalk v 2.4.13
---------- Post added at 09:42 PM ---------- Previous post was at 09:34 PM ----------
If you prefer stable SuperSU v2.16 it is here Link: http://forum.xda-developers.com/showthread.php?p=23427715
Sent from my SCH-I605 / Galaxy Note 2 / JB 4.3 / Unlocked, Rooted, ROMed and AGNi-fied !!... using Tapatalk v 2.4.13
And speaking of backups.....lol. Just had to do my first restore from my "rooted stock" backup. I played with to much stuff...don't know what I did to break it? But restore went smoothly and I am back up and running. Just have to restore my apps. I am posting from my Note 2. I'll sure do a complete backup to my setup state before I try that again..lol !!!
Sent from my SCH-I605 / Galaxy Note 2 / JB 4.3 / Unlocked, Rooted, ROMed and AGNi-fied !!... using Tapatalk v 2.4.13
doctor-cool said:
I installed twrp-2.8.1.1-trltevzw.zip then did a factory reset and rebooted. All is good.
What all should i include in my first backup with twrp before I flash the SuperSU file?
Click to expand...
Click to collapse
Did the supersu zip flash ok in the updated verizon twrp?
droidrev71 said:
Did the supersu zip flash ok in the updated verizon twrp?
Click to expand...
Click to collapse
I have flashed each of the beta updates....no problem .
Sent from my SM-N910V / VZW Note 4 DE / Rooted / TWRP 2.8.1.1 trltevzw
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Red Wolf Recovery is custom recovery based on TWRP source code however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.
Based on TWRP version: 3.2.1
For devices: Ugglite
Authors build: yshalsager
Developers: @ATG Droid & @dadi11
Thanks: z31s1g (for the base of his theme), Ray Li (For his useful advice in the beginnings), osm0sis (for his image scripts), etc.
Features:
Code:
[B]Translated to EN & CZ [/B]
- Password protection
- Flashlight
- MIUI Incremental OTA Support
- Built-in latest Magisk, SuperSU & AromaFM
- Support two screenshot GUI actions - Power+VolDown to save screenshot in to the internal storage &
Power+VolUp to save screenshot in to the external storage (Will be automatically saved in to the internal in case
that external storage doesn't exist).
- Support automatic reboot after the restore process
- Recovery can automatically modify some props in the ROM directly during the installation
- Some built-in scripts from community
- Tap to wake support
- Advanced deactivation of the stock recovery
- Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- Support "set on boot" settings.
[B]* Changes for security reasons *[/B]
- ADB isn't starting automatically at the start of the recovery. You have to activate it in recovery
- MTP isn't starting until user enter correct password
- Deactivated TWRP theme engine
[/URL]
Some differences to the official version:
Code:
[COLOR="red"]- get out of here if you are pirating apps. this recovery is not for you[/COLOR]
- always up-to-date with the latest TWRP changes
- compiled on omnirom-7.1 source
- kernel compiled inline with the recovery
- There isn't bug with reboot from recovery to recovery
- more languages
- other improvements from Features and Changelog lists
Changelog:
Code:
RedWolf-V3.2_027
- If screen is turned off then automatically detect AROMA Installer package and unblank screen before starting the update binary which is going to call AROMA GUI, so we won't be stuck at the black screen since AROMA engine require screen to be turned on.
- Added ability to change OTA Survival driver properties from the recovery GUI, allowing recovery to support "out of the box" almost all incremental OTA updates from different OEMs/custom ROMs out there (as long as they have correctly formatted metadata).
- Notify user about the current activity of the deactivation process - that's handled under the console
- Improved dumwolf driver
- Removed the vibration feedback from all GUI elements
- Automatically resize bootable partitions during nandroid backups
- Changed theme to black/white/red style based on @TBO material theme
- Data files aren't anymore saved on the storage partitions, which means that we're now able to survive even encrypted device.
- Some bug fixes and improvements...
RedWolf-V3.2_026
- This is just a quick bug fix release for MIUI users. So is highly recommend to update to this build if you are using MIUI.
RedWolf-V3.2_025
- Fixed crash of the recovery while running OTA_RES.. (So MIUI OTA is now working again)
- General bug fixes and improvements
- Fixed bug with MIUI Updater app showing error that installation failed after installation of full ROM
- Deactivation process is now called only when it's really needed
- Updated kernel
RedWolf-V3.2_024
- Fixed GUI color glitch while starting Aroma Installer update-binary
- Optimized pigz runtime process
- Updated recovery base to the AOSP 8.1.0 & TWRP 3.2.1
- Highly improved signature verification for Incremental packages so now we can be really sure if the package is compatible with the ROM.
- Introduced a file based backup/restore engine. Expect it to be improved with the next builds...
- Improved security related to the password protection
- Fixed loading of the AromaFM config file
- System survival process for Incremental packages is now set by default
- Code optimizations
- Removed the dumwolf process
- Added signature check for incremental OTA survival so we won't be unnecessarily creating a new one if it's signed under the same access key
- Magisk updated to the version 15.1
- Added Indonesian language
- Fixed issues with Chinese characters...
- Governor which is changed by the action in the recovery GUI is now automatically set for all cores instead of only four.
RedWolf-V3.2_023
- Updated recovery base to the TWRP version 3.2.0
- Fixed issue with recovery sometimes showing "NO-OS" page even when OS is installed
- Merged: Fstab V2, minui updates, Keymaster 3.0 support, ADB updates, fixes related to the compiling errors...
- Added patch against the pirating applications
RedWolf-V3.1_022
- Small improvements in the installation process
- Recovery will now automatically warn the user in case that user selected to install the zip which contain a bootloader
- You can now wipe installed substratum overlays directly from the "advanced wipe" section
RedWolf-V3.1_021
- Automatically return install error if there is any issue with Incremental OTA Survival
- Added option to also backup system partition for Incremental OTA Survival (It's not always needed, but just in case it's better to backup it.)
- Added support for the compatibility verification of the Incremental Package
- Rebuilded & improved installation process
- Fixed starting process not being disabled correctly in case that we are running ORS
- Translation update
- Added support for devices with 2GB RAM or less... (Check installation process of this build for more info)
- Added checkbox for activation/deactivation of the boot check (Disable only if you really need to).
- Fixed booting problems on some custom ROMs which don't have gzip compressed ramdisk
- Removed bookmark feature
- Added ability to unzip files using the stock filemanager.
- Added search selection for the stock filemanager.
- Fixed 'No OS' on system image restore after wipe
- Merged some latest commits from TWRP gerrit
RedWolf-V3.1_020
- Fixed flashing of the images in the previous 018 build
- Added back support for unpacking of the LZ4 compressed ramdisk
- Fixed bookmark feature
RedWolf-V3.1_019
- Disable TWRP installation directly during the first boot
- Default time zone was set to CEST
- Use military time as default time.
- Support of the custom themes was completely removed from the installation process
- Few fixes & improvements in the strings.
- Default value of the RedWolf specific vibrations was slightly increased
- Improved saving/loading of the AromaFM config file.
- User can now select if recovery should disable stock recovery when system is mounted as read-only.
- Default color of the recovery was set to red.
- Fixed automatic reboot if the installation process was unsuccessful
- Center time in the statusbar as default
- Show CPU temp in statusbar as default
- Added "Red Wolf No-OS search engine". Enable this if you are sometimes getting No-OS installed error even when OS is installed.
- Added back support for extra languages
- Added support for Talian language
- Updated Chinese (simplified) translation of the AromaFM by LiuNian and Pzqqt
- Fixed displaying of the extra languages
- Improved mounting of the partitions during the applying of set on boot values
- Fixes with "stuck at unmounting"
- Highly improved speed of the recovery while setting up a new password, changing accent color or setting a new splash screen
- Magisk updated to the V14.3
- Recovery now won't allow the user to enter special characters while entering the password (Causing issues...)
- Few improvements with the Android Oreo installation
- Updated kernel
- Added ability to select if recovery should automatically disable forced encryption in the ROM
- Recovery will now automatically rename scripts in the system if the "Aggresive stock recovery deactivation" is enabled
- Added ability to select if recovery should automatically enable/disable USB Debugging in the ROM
- Removed some useless files to save the space
- Added support for saving the set on boot values also during the automatic reboot
- Redesigned flashlight icon
- Recovery now won't allow the user to enter the space in to the backup name
- Improved support of the last status checking of the MIUI ROM
- Recovery now won't show any button after the cancelled reboot action untill the sleep action won't be running anymore
- You can now select if recovery should also automaticaly reboot after the successfuly finished restore process
- Recovery will now hide the automatic backup feature if the system partition is mounted as read-only
- Updated recovery base to the AOSP 8.0.0
- Updated image drivers
- Added ability to select if recovery should automatically enable/disable "ro.adb.secure" property in the ROM
- Recovery will now automatically disable starting of the flash_recovery service if the "Aggresive stock recovery deactivation" is enabled (this process is also compatible with the backup of the init.rc by Magisk or SuperSU).
- Added new section called "Special Actions" in to the advanced menu
- Updated & optimized flashlight drivers
- Added ability to select if recovery should automatically enable/disable "ro.secure" property in the ROM
- Added ability to select if recovery should automatically enable/disable "ro.allow.mock.location" property in the ROM
- Highly improved support of the Incremental Package installation, detection etc.
- Updated Chinese (simplified) translation of the recovery by LiuNian and Pzqqt
- Added support for the complete deactivation of the secure boot in the MIUI based ROMs
- ADB is now automatically starting as root
- Added support for the RedWolf update package
- Default theme of the AromaFM was changed to holo black with the sense icons and automount turned on
- SuperSU Updated to the 2.82 SR5
- Updated ramdisk cleaner & added support for more kernels (thanks to @MOVZX's kernel installation scripts...)
- Small fixes with the /WOLF folder in the PartitionManager
- Highly improved speed of the reboot
- 'Deactivation process' is now automatically called during the installation instead of the reboot
- Imroved deactivation of the leds after the installation / backup / restore process.
- Fixed bug with recovery showing on the governor page that the active governor is "Interactive" even when user selected performance/powersave mode.
- Removed some GUI messages while we are installing built-in zips.
- And many other things which i don't remember anymore...
RedWolf-V3.1_018
- Fixed bugs with MIUI OTA Support to make sure that it will work even with newest beta builds of the MIUI
- Updated Polish translation by Daviteusz
- Fixed bugs in the Polish strings & edited the scale of the Russian strings
- Recovery will be now more aggressive if the process of the stock recovery doesn't want to be disconnected (Sometimes happen on some MIUI ROMs).
- Added detection of the installed ROM
RedWolf-V3.1_017
- Magisk updated to the V13.6
- SuperSU updated to the 2.82 SR3
- Added ability to automatically flash SuperSU config before the SuperSU - https://forum.xda-developers.com/apps/supersu/2017-08-13-supersu-config-t3655754
- Deactivated hw keys
- Added some missing back buttons
- Attempted to fix encryption
- Attempted to fix MIUI OTA installation - needs testing
- Removed extra languages (were not displayed properly)
- Small update which fixed deactivation of the dm-verity & forced encryption. Now you really don't have to flash the lazyflasher everytime when you are installing the MIUI ROM.
RedWolf-V3.1_016
- Fixed feature "Backup wifi, bluetooth & hosts" not to work if the user wiped the data partition using the "factory reset".
- TWRP source code was updated to the Aug 15, 2017
- Fixed recovery remembering the wipe list after setting a new gui page.
- Improvements with the mounting of the partitions during the boot
- Fixed led drivers on mido
- Fixed ability to set custom backup folder name & ADB ID
RedWolf-V3.1_015
- Updated with the latest TWRP changes
- Added flashlight switch on mido
RedWolf-V3.1_014
- Fixed recovery not deactivating the dm-verity, forced encryption, & stock recovery if the OS was detected as not installed. This issue was often happening on some MIUI ROMs.
- Improvements with the OTA update system of the MIUI.
- Fixed wrong reboot for some users.
- Added support for automatic deactivation of the dm-verity, forced encryption & stock recovery after finishing the OpenRecoveryScript process.
- Fixed recovery not deactivating the dm-verity & forced encryption during the automatic reboot after the finished installation.
- Better explain the current situation if the OS was detected as not installed.
- osm0sis's scripts "unpackbootimg" & "mkbootimg" can now be easily called from the script or terminal
- Improved the speed of the reboot
- Updated the community script "Fingerprint scanner fix" by Magua. It's now working again!
- Added NTFS & exFAT support
- Added more languages and updated Polish RedWolf translation by @Daviteusz
- Added FGO patch - https://goo.gl/GBkhMN
RedWolf-V3.1_013
- Slightly improved deactivation of the stock recovery during reboot after the zip installation
- Added ability to flash boot logo in the recovery
- Fixed firmware restoring issues
RedWolf-V3.1_012
- added F2FS support for mido
- added Night Mode (kcal) support for mido
RedWolf-V3.1_011
- Updated Polish translation by @Daviteusz
- Added few missing strings from the latest TWRP source
[Red Wolf] Install TWRP and root your device without breaking incremental OTA's!
Known Bugs:
- Flashlight is not working.
Downloads:
Latest build for Xiaomi Redmi Note 5A/Y1 (ugglite)
RedWolf-027-Unofficial-ugglite.img
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery. But your device can be still reinstalled using fastboot or Miflash.
XDA:DevDB Information
[RECOVERY][UNOFFICIAL][UGGLITE][V3.2.1-027] Red Wolf Recovery Project, Tool/Utility for the Xiaomi Redmi Note 5A/Prime/Y1
Contributors
yshalsager, ATG Droid, Dadi11
Source Code: https://github.com/RedWolfRecovery
Version Information
Status: Testing
Created 2018-02-21
Last Updated 2018-05-07
Sources:
Recovery: https://github.com/RedWolfRecovery/rw_recovery
Device trees:
https://github.com/RedWolfRecovery-Xiaomi-Devices/android_device_xiaomi_ugg
https://github.com/RedWolfRecovery-Xiaomi-Devices/android_device_xiaomi_ugglite
Screenshots: Here
In ugglite not working. Phone don't go to recovery, reboot and boot normally.
ugglite no work please see : https://forum.xda-developers.com/android/development/recovery-red-wolf-recovery-project-t3762730
Costum rom
Thanks before,and let me hope another dev make costumrom for RN5A UGG,I try 1 mounth searching costumrom yet beside MIUI Pro,or XIAOMI EU,I dont get it why so quiet support?
Reza740 said:
Thanks before,and let me hope another dev make costumrom for RN5A UGG,I try 1 mounth searching costumrom yet beside MIUI Pro,or XIAOMI EU,I dont get it why so quiet support?
Click to expand...
Click to collapse
ugglite
Try to find ugg there
As stated previously, this recovery doesn't work. Try the one on post number 4.
yshalsager said:
ugglite
Try to find ugg there
Click to expand...
Click to collapse
Sorry one question please,I dont understand how to find there,in there all speaking russian no english,maybe next future and thanks again for suggest to me,cheers
Sent from my ugg using XDA Labs
thanks a lot.:laugh:
Updated!
Red Wolf V3.2.1-027
Finally, It's working
Tested on ugglite only.
I will update ugg soon
If any ugg user interesting in testing, ping me on telegram
would that be also for the 2/16 version?
Gesendet von meinem S3 mit Tapatalk
TommeleTBone said:
would that be also for the 2/16 version?
Gesendet von meinem S3 mit Tapatalk
Click to expand...
Click to collapse
It's already for it.
2/16 is ugglite
ah cool, because there was a recent '2gb'-version besides the ugg and ugglite, that made me wonder...
Gesendet von meinem S3 mit Tapatalk
yshalsager said:
Updated!
Red Wolf V3.2.1-027
Finally, It's working
Tested on ugglite only.
I will update ugg soon
If any ugg user interesting in testing, ping me on telegram
Click to expand...
Click to collapse
Thanks a lot!
yshalsager said:
Updated!
Red Wolf V3.2.1-027
Finally, It's working
Tested on ugglite only.
I will update ugg soon
If any ugg user interesting in testing, ping me on telegram
Click to expand...
Click to collapse
hey. have you finished testing the one for ugg?
gingerboy92 said:
hey. have you finished testing the one for ugg?
Click to expand...
Click to collapse
After exams.
@gingerboy92 ugg build, Can you test?
https://www.androidfilehost.com/?fid=746163614322266065
yshalsager said:
@gingerboy92 ugg build, Can you test?
https://www.androidfilehost.com/?fid=746163614322266065
Click to expand...
Click to collapse
Something is wrong. Partition mount error.
gingerboy92 said:
Something is wrong. Partition mount error.
Click to expand...
Click to collapse
Okay, thanks for testing
yshalsager said:
Okay, thanks for testing
Click to expand...
Click to collapse
alright. for now i just unpacked the ugglite build, replaced the ugglite props and *variant*.rc to ugg. working fine. not sure if it'll go wrong but i only use the recovery to flash new rom so i guess it'll be ok, i hope it'll be ok rofl
Code:
Disclaimer
#include
*
* [B]Your warranty is now void.[/B]
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Welcome to hadesKernel
Some personal thoughts:
- this kernel works only on exynos variants of S8(+) and Note8, only Pie and OneUI based roms (stock and stock based roms) I'm not responsable for what can happen if you flash on other devices/roms/android versions.
- if you take any of my work without my permission i'll report you, and you'll probably get banned.
- you should read at least install instructions stated in this post - i won't offer support for any issues regarding installation;
- for more info about features included and bug reports make sure you read post #3;
- press 'Thanks' button instead of saying it - it will keep the thread clean and keep me motivated to do more;
- feel free to send me some coffee (which btw, runs out pretty quick) via paypal, if you want to support my work.
Supported devices:
- G950F / G950FD / G950N / G955F / G955FD / G955N / N950F / N950FD / N950N
Features
G95*FXXS5DSI1 September and N950FXXS7DSH6 August security patch source
compiled with gcc 9.1
RMM/KG prepatched (more info about RMM here)
fully enforcing with the ability to change to permissive
disabled tima/knox/rkp/defex/dm_verity/fips/knox
enabled mass_storage for DriveDroid (download here latest beta app)
disabled zswap and added zram
Led fade
Moro Sound control
Boeffla Wakelock blocker
Wireguard support
blu_active CPU governor
other compiler optimizations
init.d support
dex with any hdmi adapter
crc/fsync toggle
ramdisk scripts for on boot optimizations
disabled excessive samsung logging/tracing
Bugs:
none encountered (see FAQ on #3 post for workarounds)
Instructions:
make sure you have a compatible rom installed (any OneUI pie rom including stock and stock based roms)
make sure you have TWRP 3.3.x installed (download latest official for Note8 or S8/S8+, install instructions here)
download zip and put it into phone's storage
enter TWRP recovery
flash zip
optional - flash root
reboot and enjoy
optional - download and install hKtweaks or MTweaks to be able to change some settings.
Telegram support
Updates and info channel
Support group
Downloads
on #2 post
Credits:
*Noxxx
*djb77
*MoroGoku
*farovitus
*6h0st
*remilia15
*frap129
*ananjaser1211
*BlackMesa123
*Lord Boeffla
*Faux123
*kernel testers
*if i missed someone PM me and i'll add
XDA:DevDB Information
hadesKernel , Kernel for the Samsung Galaxy Note 8 (2017 Phone)
Contributors
corsicanu
Source Code: https://github.com/corsicanu/android_kernel_samsung_universal8895
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v1.4
Stable Release Date: 2019-10-10
Created 2019-05-27
Last Updated 2019-10-10
Reserved
Changelog/Downloads
hadesKernel v1.4
hadesKernel v1.3
hadesKernel v1.2
hadesKernel v1.1
hadesKernel v1.0
initial release
Download - hadesKernel_v1.0 - AndroidFileHosthttps://www.androidfilehost.com/?fid=6006931924117882979
Reserved
FAQ:
Q: How to report bugs?
A: If you want to report a bug make sure you include:
-device variant / modem version / bootloader version / region
-detailed info about the encountered issue
-steps to reproduce the bug
-logs
Q: How to take logs?
A: Download Logcat Extreme and take a look at this.
Q: Does it work with stock rom?
A: Only if you format data on TWRP before installing, if you had stock kernel before - please do note this will erase all your data and internal storage
Q: How to revert to stock kernel?
A: That's not a choice at this moment, you either reflash your current custom rom (if that had stock kernel included), or install stock firmware via Odin which will probably cause damage to all your data including internal storage.
Q: What semi-systemless kernel means?
A: I changed the way of patching camera drivers and secure storage libs in a way to avoid altering original files, so if you are on stock rom and stock kernel, you can simply backup your boot.img and if you don't like hades you can restore that boot.img without any futher issues.
Q: Saved wifi/bluetooth connections don't work anymore, what to do?
A: Simply forget and reconnect wifi networks and/or re-pair bluetooth devices.
Q: Why is this kernel better than *&% kernel?
A: I never said it is and i also don't like to compare. You are the only that can decide if it is or not for your use.
Q: Why this kernel?
A: I made this kernel to disable samsung security and add few things for myself, since it went pretty well for me i decided to include it in the rom and release as separate too.
Q: Why samsung security disabled?
A: Samsung firmware and kernels are signed and made to get along eachother untampered. The second you change something (even only with rooting stock rom), that very moment security starts to spam in logs/operations which can result in lags/heats/freezes etc. Since we can't sign our roms/kernels as samsung, it`s better to disable security to avoid conflicts and ulterior issues.
Q: What's Moro Sound and how does that work?
A: It's an advanced sound control implemented first in S7 by @morogoku, which can be found in hKtweaks / MTweaks - sound section.
You can change the output gain for speaker(s) and headphones, and also the equalizer to one of the profiles inside, or to your very own profile according to your taste.
*I'm not responsable for any damage made by yourself on your phone/headphones/ears using too high values on this mod. If you are in doubt just leave it disabled or switch to other kernel.
Q: Why a separate tweaks app?
A: I made this app to properly maintain and adapt A5/A7 2017, your choice what app you want to use.
One more
Long waited stock close kernel??
Thx again @corsicanu - God of Hades!
Thanks soooooo much
Great... delicius... thanks...
Sent from my SM-N950F using XDA-Developers Legacy app
Is this the same version as what is in the latest hades ROM or are there any differences?
hshah said:
Is this the same version as what is in the latest hades ROM or are there any differences?
Click to expand...
Click to collapse
As mentioned in Telegram, it's the same version as on Hades Rom v7.
Nice kernel. Running fine so far. Thank you.
Some issues.
Hi Dev.
I have tried to flash this kernel because it sounds nice, but after I have flashed it and installed Magisk v19.2 over it my Substratum is not loading themes and Xposed framework not working at all.
Thanks.
EdXposed framework working now
Working fine with dr.ketan room
Sent from my SM-N950F using XDA-Developers Legacy app
Up...
Up...
Sent from my SM-N950F using XDA-Developers Legacy app
hadesKernel v1.1:
Changelog:
- fixed moro sound issues
- enabled dex with any hdmi adapter
- added crc toggle
- added fsync toggle
- disabled zipalign at boot to avoid substratum issues
- touchscreen ops improvements to avoid some stutters or unneeded wakeups
- made it semi-systemless kernel (more info on FAQ)
- ramdisk improvements from S9 June release
- better zip extracting/patching scripts
Install instructions:
- flash as normal zip in TWRP, no wipe needed
*if coming from stock kernel you probably need to format data in TWRP - this will cause losing all data including internal storage
Personal notes:
If coming from stock kernel you probably need to format data in TWRP - this will cause losing all data including internal storage
Kernel zip doesn't contain any root, flash root of choice after flashing the kernel.
Download:
hadesKernel_v1.1 - AndroidFileHost
Telegram support
Updates and info channel
Support group
Misc links
Official TWRP for Note8
Official TWRP for S8/S8+
O/P Bootloaders and modems
Click to expand...
Click to collapse
Regards
corsicanu said:
hadesKernel v1.1:
Regards
Click to expand...
Click to collapse
Insane!!
Thank you!
Hi...
For battery life this kernel best or stock??
I cannot get xposed to work with this kernel, any1 could help?
hadesKernel v1.2:
Changelog:
- Merged G95*FXXU4DSE4 May source and N950FXXS6DSF2 June source
- Updated ramdisk to N950FXXS6DSF2 June
- Optimized Integer SQRT. for upto 3x faster operation
- Compiled with GCC 9.1
Install instructions:
- flash as normal zip in TWRP, no wipe needed
*if coming from stock kernel you probably need to format data in TWRP - this will cause losing all data including internal storage
Personal notes:
If coming from stock kernel you probably need to format data in TWRP - this will cause losing all data including internal storage
Kernel zip doesn't contain any root, flash root of choice after flashing the kernel.
Download:
hadesKernel_v1.2 - AndroidFileHost
Misc links
Telegram Updates and info channel
Telegram Support group
Official TWRP for Note8
Official TWRP for S8/S8+
O/P Bootloaders and modems
Click to expand...
Click to collapse
Regards
My only one problem is , my phone going to deep sleep wlan is going off after some time. But all other fine here.