TeamWinRecoveryProject
Changelogs from last Release from Shaaan to mine
Code:
[B]2.4.4.0[/B]
* Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
* More fixes for the file selector
* Switched from using busybox md5sum to a direct C function call
* Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
* Update exFAT to latest commits
* Added a build flag to disable using the ioctl for screen blanking
[B]2.4.3.0[/B]
* Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
* Added a scroll bar to file selectors and listboxes courtesy of Tassadar
* Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
* Added a screen dim effect 2 seconds before screen off on some devices
* Finally fixed file selector crash (one of the joys of working with multi-threaded software)
* Fixed loading of screen timeout setting during startup
* Improvements and bugfixes to screen timeout code
* Fixed persistence of the 24 hour / military time setting
[B]2.4.2.0[/B]
* Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
* Add a brightness setting (requires device specific setup and only some devices have been added)
* Add a root checker and offer to install SuperSU if the device isn't already rooted
* Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
* Check and offer to fix root permissions if broken
* Add an option for a 24 hour clock display instead of AM/PM (aka military time)
* Move stock recovery reflash check to occur during the reboot cycle
* Add support for some MTK6xxx devices
* Change libtar to vfork to help prevent memory problems
* Add a "clicked" effect to most buttons, file selector, and listbox
* Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
* Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
* Other minor bugfixes and improvements
[B]2.4.1.0:[/B]
* Fixed a problem with mkdosfs that formatted sdcards to 2GB
* Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
* Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
* Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
[B]2.4.0.0:[/B]
* Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
* Support for exFAT formatted sdcards (also thanks to bigbiff)
* Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
* Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
* Added wipe cache and dalvik after ADB Sideload
* Replaced many system calls with their native C counterparts
* Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
* Fixed AOSP recovery commands to run after decryption on encrypted devices
* Improvements for building TWRP in CM10.1
* Other minor bugfixes and improvements
[B]2.3.3.0:[/B]
* Fix renaming backups with a space in the name
* Add decrypt button to mount page if you cancel decryption during startup
* Added ignore blkid flag
* Fixed handling of MTD partitions during mount
* Fixed some keyboard mapping issues on 800x1280 layout
[B]2.3.2.0:[/B]
* Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
* Fixed a bug with deleting a backup with a space in the name
* Added highlights on keyboard key presses
[B]2.3.1.0:[/B]
* Unmount system after boot to prevent some status 7 symlink failed errors on zip install
* USB Mass Storage code improvements
* Better handling of mounting storage during boot for some devices
* Fixed a problem with sizes of images (boot & recovery) after resetting defaults
* Fixed size errors during backup for some devices on recovery, etc.
* Fixed a problem with restoring backups when multiple archives were present
[B]2.3.0.0:[/B]
* Rebased onto AOSP Jelly Bean source code
* Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
* ADB sideload functionality from AOSP is included in 2.3, see this link for more info
* Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
* Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
* Faster boot times
* Added charging indicator while in recovery (only updates once every 60 seconds)
Issues
Code:
* Maybe your USB in recovery will be broken (so no mount storage to pc)
!!!It can happen that you brick your Device any other time, but this time NOT, when you flash this!!!
Downloads (My version)
Code:
[URL="http://tinyw.in/clY8"]twrp_2.4.4.0-cooper.zip[/URL]
[B]MD5-Sum:[/B] b812c764b80b2db2d6ae53dc4eb0f9de
Your will look like that if i done all right:
{
"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:
[B]CREDITS:[/B]
* Dees_Troy and other devs for helping me
* original recovery from TWRP team (thx all)
* shaaan for recovery kernel
Wow man You rocks.... Hope we can get stable soon.... BTW any plan to make another version of CMX as it is full of bug
Why version 2.2.0 on screenshots?
Nice, finally Galaxy Ace has 2 custom recovery
Flashed it. Stuck on teamwin splash screen.
AW: [dev][recovery] twrp 2.4.1.0
yash295 said:
Flashed it. Stuck on teamwin splash screen.
Click to expand...
Click to collapse
good to know thanks man, i`ll look later into it, im away from home now
Sent from my GT-P1000 using xda app-developers app
Its fine man.. you are doing so much hard work for ace, least we can do is test things for you. keep it up.
OldDroid said:
good to know thanks man, i`ll look later into it, im away from home now
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
same heree
Re: [dev][recovery] twrp 2.4.1.0
So you fixed the mount errors?
Sent from my GT-I9070 using xda premium
AW: [dev][recovery] twrp 2.4.1.0
no shaaan it goes more deep into the complete recovery as i thought, now im debugging it with bigbiff from twrp team
Sent from my GT-P1000 using xda app-developers app
Re: [dev][recovery] twrp 2.4.1.0
Been looking forward to twrp for a while. Thanks for tackling it.
Sent from my GT-S5830i using xda app-developers app
Re: [dev][recovery] twrp 2.4.1.0
OldDroid said:
no shaaan it goes more deep into the complete recovery as i thought, now im debugging it with bigbiff from twrp team
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Yeah. Also Dees is making some rapid changes to the source to introduce new features.
I worked with him to add basic bml support. Now the recovery atleast recognizes the partitions!
Sent from my GT-I9070 using xda premium
Re: [dev][recovery] twrp 2.4.1.0
OldDroid said:
Code:
* Based on CM10 Code (Next Release or Build will be on CM10.1 Code)
* Maybe you land into a Bluescreen
(you can still boot into Download-Mode so you still can flash another Recovery ;)
Its not a [for me its still easy to fix, but you Wont brick your Device!)
Click to expand...
Click to collapse
Man wtf was the point of posting this. It don't work. I get blue screen. Seriously dude u need to let people know it don't work. Not "maybe you land on blue screen". U should change your wording to "will turn phone into blue flashlight"
I'm still working join fixing this.... Using Odin but it don't seem to be working. I have all the correct files for cwm install via Odin. Soi far its been running for 10 min.
Sent from my Nexus 7 using XDA Premium HD app
ronedogg said:
Man wtf was the point of posting this. It don't work. I get blue screen. Seriously dude u need to let people know it don't work. Not "maybe you land on blue screen". U should change your wording to "will turn phone into blue flashlight"
I'm still working join fixing this.... Using Odin but it don't seem to be working. I have all the correct files for cwm install via Odin. Soi far its been running for 10 min.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
blue screen or twrp screen, no one reported before that you land on a blue screen, twrp screen is still possible because of wrong loaded bml partitions :silly:
ronedogg said:
Man wtf was the point of posting this. It don't work. I get blue screen. Seriously dude u need to let people know it don't work. Not "maybe you land on blue screen". U should change your wording to "will turn phone into blue flashlight"
I'm still working join fixing this.... Using Odin but it don't seem to be working. I have all the correct files for cwm install via Odin. Soi far its been running for 10 min.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Dont came here acting like this !!
U know that tere's risks is this wip projects ... and this dev is working on a top recovery for an almost ancient ace so bare some respects!
i can see that you're ace had problems but keep calm re-download odin files and just put phone in download mode and flashem well
the only hard brick known to ace i rom manager wich screws the partition's of it! If u can enter download mode you're ace is not bricked! keep trying if u need any help just pm me and i'll be glad to help
take care
Re: [dev][recovery] twrp 2.4.1.0
OldDroid said:
blue screen or twrp screen, no one reported before that you land on a blue screen, twrp screen is still possible because of wrong loaded bml partitions :silly:
Click to expand...
Click to collapse
LoL i wasn't being rude if i came across that way. I got cwm back now.
So what was my issue then. How can i use twrp. What else do i have to do. Just flash the zip with cwm, then what?
Sent from my Nexus 7 using XDA Premium HD app
AW: [dev][recovery] twrp 2.4.1.0
Any progress or isnt it possible to run twrp 2.4.x on our Aces?
Sent from my GT-S5830 using xda app-developers app
Re: [dev][recovery] twrp 2.4.1.0
OldDroid said:
TeamWinRecoveryProject
Changelogs from last Release from Shaaan to mine
Code:
[B]2.4.1.0:[/B]
* Fixed a problem with mkdosfs that formatted sdcards to 2GB
* Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
* Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
* Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
[B]2.4.0.0:[/B]
* Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
* Support for exFAT formatted sdcards (also thanks to bigbiff)
* Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
* Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
* Added wipe cache and dalvik after ADB Sideload
* Replaced many system calls with their native C counterparts
* Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
* Fixed AOSP recovery commands to run after decryption on encrypted devices
* Improvements for building TWRP in CM10.1
* Other minor bugfixes and improvements
[B]2.3.3.0:[/B]
* Fix renaming backups with a space in the name
* Add decrypt button to mount page if you cancel decryption during startup
* Added ignore blkid flag
* Fixed handling of MTD partitions during mount
* Fixed some keyboard mapping issues on 800x1280 layout
[B]2.3.2.0:[/B]
* Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
* Fixed a bug with deleting a backup with a space in the name
* Added highlights on keyboard key presses
[B]2.3.1.0:[/B]
* Unmount system after boot to prevent some status 7 symlink failed errors on zip install
* USB Mass Storage code improvements
* Better handling of mounting storage during boot for some devices
* Fixed a problem with sizes of images (boot & recovery) after resetting defaults
* Fixed size errors during backup for some devices on recovery, etc.
* Fixed a problem with restoring backups when multiple archives were present
[B]2.3.0.0:[/B]
* Rebased onto AOSP Jelly Bean source code
* Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
* ADB sideload functionality from AOSP is included in 2.3, see this link for more info
* Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
* Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
* Faster boot times
* Added charging indicator while in recovery (only updates once every 60 seconds)
Current State
Code:
* Based on CM10 Code (Next Release or Build will be on CM10.1 Code)
* Maybe you land into a Bluescreen
(you can still boot into Download-Mode so you still can flash another Recovery ;)
Its not a [for me its still easy to fix, but you Wont brick your Device!)
!!!It can happen that you brick your Device any other time, but this time NOT, when you flash this!!!
TWRP-2.4.1.0-cooper.zip
MD5-Sum: None
Your will look like that if i done all right:
Click to expand...
Click to collapse
Your source?
I do not respond to tech support via PM
AW: [dev][recovery] twrp 2.4.1.0
Shaaan said:
Your source?
I do not respond to tech support via PM
Click to expand...
Click to collapse
locally, added the reboot hack + bml partition layout to preserve a bricl
Sent from my GT-S5660 using xda app-developers app
Re: [dev][recovery] twrp 2.4.1.0
OldDroid said:
locally, added the reboot hack + bml partition layout to preserve a bricl
Sent from my GT-S5660 using xda app-developers app
Click to expand...
Click to collapse
So basically you haven't fixed anything?
I do not respond to tech support via PM
Related
Team Win Recovery v 2.6.0.0
{
"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"
}
Team Win Recovery Project 2.4.3.0, 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.
Code:
#include
/*
* Your warranty is now void.
*
* 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 Recovery
* 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.
*/
Features
Ability to save custom recovery settings
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) and much more
CHANGELOG for 2.5.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!
-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-Fixed a problem with md5 verification of backups
-Added a search function to libtar (thanks to kokotas)
-Improve handling of XML errors (fix permissions)
-Fixed handling of subpartitions
-Improvements to recovery.fstab flags
-Fixed a problem with decryption not being able to locate the decryption key in some situations
What's new in 2.4.4.0:
Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
More fixes for the file selector
Switched from using busybox md5sum to a direct C function call
Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
Update exFAT to latest commits
Added a build flag to disable using the ioctl for screen blanking
CHANGELOG for 2.4.3.0:
-Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
-Added a scroll bar to file selectors and listboxes courtesy of Tassadar
-Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
-Added a screen dim effect 2 seconds before screen off on some devices
-Finally fixed file selector crash (one of the joys of working with multi-threaded software)
-Fixed loading of screen timeout setting during startup
-Improvements and bugfixes to screen timeout code
-Fixed persistence of the 24 hour / military time setting
CHANGELOG for 2.4.2.0:
-Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
-Add a brightness setting (requires device specific setup and only some devices have been added)
-Add a root checker and offer to install SuperSU if the device isn't already rooted
-Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
-Check and offer to fix root permissions if broken
-Add an option for a 24 hour clock display instead of AM/PM (aka military time)
-Move stock recovery reflash check to occur during the reboot cycle
-Add support for some MTK6xxx devices
-Change libtar to vfork to help prevent memory problems
-Add a "clicked" effect to most buttons, file selector, and listbox
-Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
-Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
-Other minor bugfixes and improvements
CHANGELOG for 2.4.1.0:
-Fixed a problem with mkdosfs that formatted sdcards to 2GB
-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
CHANGELOG for 2.4.0.0:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!
CHANGELOG for 2.3.3.0:
-Fix renaming backups with a space in the name
-Add decrypt button to mount page if you cancel decryption during startup
-Added ignore blkid flag
-Fixed handling of MTD partitions during mount
-Fixed some keyboard mapping issues on 800x1280 layout
DOWNLOADS:
=>Please use the recovery found over Here . All bugs have been fixed by me in this build.
INSTRUCTION:
- Installing via goo manager - Read THIS
- Download the recovery.img file and place it in your android-sdk/platform-tools directory
- Reboot phone to boot loader.
- Type fastboot flash recovery recovery.img (If on Windows) or ./fastboot flash recovery recovery.img (if on linux)
- Reboot to recovery- Enjoy
Check this post to get a better understanding on TWRP for new users :Click me!
BUGS
>All bugs fixed
My Device Tree for Twrp :
My Device tree for twrp : https://github.com/nikhil16242/device_htc_golfu
DOWNLOADS:
Stable and Bug Free TWRP 2.4.2.0 : Here
TWRP 2.5.0.0 Is live now. Download via goomanager
Direct Link : TWRP-2.5.0.0
Previous version TWRP 2.4.3.0 : http://d-h.st/eHL
Video:
Heres a short video for TWRP 2.4.1.0 made by russell664 , so guys thank him for the video
(Or use the actual youtube link http://www.youtube.com/watch?feature=player_embedded&v=Na6GgxNytmE )
Credits:
-The Whole of TWRP Team especially Dees_Troy for the compiling guide
-Me For compiling it for Desire C
Hit Thanks If you Appreciate My Hard Work
Wow! Thanks nikhil I was just about to make this recovery myself.
Great job!
Thanks nikhil, i'm glad you did this! I will test it later for you!
Wow, thank you!
I´m going to test later xP
russell664 said:
Wow! Thanks nikhil I was just about to make this recovery myself.
Great job!
Thanks nikhil, i'm glad you did this! I will test it later for you!
Click to expand...
Click to collapse
Jaizu said:
Wow, thank you!
I´m going to test later xP
Click to expand...
Click to collapse
No problem guys. But remember its still in alpha stage. So expect some bugs here and there
Link updated. Forgot to add some options in the earlier one
Re: [Recovery][WIP] TWRP v 2.4.1.0
Is there any bug at backup and restore?
Sent from my HTC Desire C using xda premium
Wooha, it has a handy-dandy file manager as well, no need for aroma file manager!
I made a backup with compression, it says Backup Complete and under it Failed. I checked in file manager, it is indeed not a full backup.
I tried again without compression, it says Successful, looks it has all the files. Restore however fails (but at least it doesn't freak you out with rebooting like CWM lol). I attached the logs, maybe they are the same but just in case.
Mounting-unmounting external/internal USB is fine.
Other:
I liked the android animation in CWM, but oh well
I don't know if you can do something about it, or it's like that by default but the fonts look a bit fragmented, as if scaled badly or something. And some color option other than yellow would be nice, or just green or blue, makes me more relaxed when messing with recovery lol. - If I don't ask too much
Also on the info screen while backing up, the text is out of the screen, doesn't affect usability, just saying.
Question: does it backup kernel as well? because I read CWM even if it's bug-free does not do it, despite that it backups boot.img.
neoyoli said:
Wooha, it has a handy-dandy file manager as well, no need for aroma file manager!
I made a backup with compression, it says Backup Complete and under it Failed. I checked in file manager, it is indeed not a full backup.
I tried again without compression, it says Successful, looks it has all the files. Restore however fails (but at least it doesn't freak you out with rebooting like CWM lol). I attached the logs, maybe they are the same but just in case.
Mounting-unmounting external/internal USB is fine.
Other:
I liked the android animation in CWM, but oh well
I don't know if you can do something about it, or it's like that by default but the fonts look a bit fragmented, as if scaled badly or something. And some color option other than yellow would be nice, or just green or blue, makes me more relaxed when messing with recovery lol. - If I don't ask too much
Also on the info screen while backing up, the text is out of the screen, doesn't affect usability, just saying.
Question: does it backup kernel as well? because I read CWM even if it's bug-free does not do it, despite that it backups boot.img.
Click to expand...
Click to collapse
I will take a look at the issues soon. Try using option of skipping MD5Sum verification while restoring back up.Regular back and restore work flawlessly for me though. You can theme TWRP recovery anyway you want . Just need to do some xml editing. I will try to theme it as well , but only after some of the major issues get resolved .
PS: If you want I could make an option to flash the kernel without fastboot . Check this http://teamw.in/project/htcdumlock . I might implement it in the future
Link Updated Again. Changed Theme to stock blue instead of orange
nikhil16242 said:
I will take a look at the issues soon. Try using option of skipping MD5Sum verification while restoring back up.Regular back and restore work flawlessly for me though. You can theme TWRP recovery anyway you want . Just need to do some xml editing. I will try to theme it as well , but only after some of the major issues get resolved .
PS: If you want I could make an option to flash the kernel without fastboot . Check this http://teamw.in/project/htcdumlock . I might implement it in the future
Link Updated Again. Changed Theme to stock blue instead of orange
Click to expand...
Click to collapse
Stock blue is indeed much more relaxed .
I've been hoping someone would get TWRP up and running for the phone . It is so much nicer enviroment to work in than cwm .
You gotta get it working with aroma though , I'm still using your Aroma for some of the tweaks in there :laugh:
Re: [Recovery][WIP] TWRP v 2.4.1.0
Aroma does work now
Sent from my HTC Desire C using xda app-developers app
Great I will flash the new recovery soon, and try it with the new aroma installer of the revolution rom!
nikhil16242 said:
Aroma does work now
Sent from my HTC Desire C using xda app-developers app
Click to expand...
Click to collapse
Awsome will flash right now
quick guide , will probably seem obvious to most but may help .
1-Boot into recovery (TRWP)
2-Press Backup button
3-Tick every box in the options at the top up to and including sd-ext(if you have an sd-ext)
4-don't enable compression
5-don't tick Skip MD5 generation (for now I will test it now in a mo and update)
6-tick USE EXTERNAL SD (i'm not shouting )
7-before you swipe to backup ..... press set backup name*
8-after writing the name of your backup press the go back button
9-swipe to back up
win:good:
*this is very handy it especially if you have a Nameless backup, a Revolution sense backup and a revolution sensless backup:good:
This is why I tick to save everything , you get the entire picture of your phone at that moment in time .
A nice thing about TWRP is that you don't-have-to-write-the-name-like-this-for-it-to-work you can write normally with spaces and it will work:goodat least that was one of the earlier fixes for the n7)
It also backups much faster than CWM
To restore
1- Boot into recovery
2-press Restore button
3-choose the named file you wish to restore
4- swipe to restore
done
Just checked all of this as I write and it works . The phone has restored my Test backup too , So all is well thankyou
hope this helps a few of you
** Only issue I've seen so far is that the buttons are sometimes unresponsive , usually the go back button and the choose which type of reboot buttons .after restore reboot button is unresponsive too .
Just checked backup with spaces between name (test two) and backup was successful as was restore . so all good there.
Re: [Recovery][WIP] TWRP v 2.4.1.0
Yeah, forgot to mention - the power off option doesn't seem to work in reboot section.All other options work though
The plus point is it restores backups fast
And great guide / review whoamigriffiths :good: . Will add it to the first post soon so people who are new to twrp can understand it better
Sent from my HTC Desire C using xda app-developers app
Great recovery! I have tested it with the revolution aroma installer and it works flawlessly good job!
One little problem, the buttons can turn a little unresponsive but other wise it is perfect.
Keep up the good work!
Russell664
nikhil16242 said:
I will take a look at the issues soon. Try using option of skipping MD5Sum verification while restoring back up.Regular back and restore work flawlessly for me though. You can theme TWRP recovery anyway you want . Just need to do some xml editing. I will try to theme it as well , but only after some of the major issues get resolved .
PS: If you want I could make an option to flash the kernel without fastboot . Check this http://teamw.in/project/htcdumlock . I might implement it in the future
Link Updated Again. Changed Theme to stock blue instead of orange
Click to expand...
Click to collapse
Yep, I confirm too, it restores flawlessly without ticking compression and md5, and it's fast. Thanks man, this was much needed for a carefree tweaking lol! And thanks for the blue theme too
Sure this falshing kernel without fastboot would be good, anything makes things easier.
Does TWRP backup/restore kernel as well? I can see it restores boot.img, but I've read in numerous forums that CWM does that too, but actually leaves kernel alone even if it's bug free. So what's the case with TWRP?
russell664 said:
Great recovery! I have tested it with the revolution aroma installer and it works flawlessly good job!
One little problem, the buttons can turn a little unresponsive but other wise it is perfect.
Keep up the good work!
Russell664
Click to expand...
Click to collapse
I will try my best to fix those bugs
neoyoli said:
Yep, I confirm too, it restores flawlessly without ticking compression and md5, and it's fast. Thanks man, this was much needed for a carefree tweaking lol! And thanks for the blue theme too
Sure this falshing kernel without fastboot would be good, anything makes things easier.
Does TWRP backup/restore kernel as well? I can see it restores boot.img, but I've read in numerous forums that CWM does that too, but actually leaves kernel alone even if it's bug free. So what's the case with TWRP?
Click to expand...
Click to collapse
I dont think TWRP can restore kernel directly without s-off. But with HTC_DUMLOCK addition it might be able to do this (need to check this in more detail)
The Good Recovery ... Thanks :good:
Thankyou
Worked brilliantly last night after flashing russells latest rom and finding no super su binaries. I had already deleted all my cwm backups , so had only TWRP to rely on .
And it past with flying colours . So thankyou very much :highfive:
Hey guys does the TWRP lock screen work(press the power button) in the current version I uploaded?
Also could some one check if enable compression works on /system and /data (select them one at a time while doing a backup) ?
nikhil16242 said:
Hey guys does the TWRP lock screen work(press the power button) in the current version I uploaded?
Also could some one check if enable compression works on /system and /data (select them one at a time while doing a backup) ?
Click to expand...
Click to collapse
I'll do a compress test now . let me check first post to see if I have most up to date version first .
Looks like you updated today ? I'll DL now and flash give me 15 mins to report back cos the kids are playing up lol (we all have man flu)
yup lock works :good: looks awsome
testing compression now . It started a compressed backup and I was thinking man this is slow (the bar was at half way) Now the screen has gone blank and the phone rebooted .
Checking whats going on now
Only file in the backup is system.ext4.win which is the last file in a normal backup (except for the system.ext4.win.MD5 file)
I tried backups and restoring too it works great, unless you compress it then it reboots. Also I superSu binary issues have been fixed on my roms I tested so yeah.
All credits go to Phil3759 as I just ported it to our device. Original thread, I had to change some stuff like the ramdisk and zImage to make it working on our device.
Touch driver fix (also for aroma) thanks to nickdollahz
Click to expand...
Click to collapse
I'm not responsible for your bricked device!
* * * * * * * * * * * * * * * * * * * * * * * * *
PhilZ Touch 5 Recovery
CivZ version 1.1
CWM Advanced Edition 6.x
* * * * * * * * * * * * * * * * * * * * * * * * *
{
"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"
}
Features of this ported recovery:
RECOVERY IS IN TABLET MODE
Touch recovery based on cwm 6.0...
zImage compiled by civato based on Samsung Update2 with Exfat support
Touch driver fixed for aroma thanks to nickdollahz
Backup / restore
Custom backup / restore
EFS backup / restore: It is stored as a hidden file in clockworkmod/backup.
Change theme layout and touch settings
TWRP and CWM restore support
Format data/media = internal_SD will be empty.
Power menu
etc..............................
Full detail from the original thread
touch interface:- toggle between 4 touch modes: FULL TOUCH, DOUBLE TAP to validate and SEMI TOUCH (scroll but no touch validation) and NO TOUCH to only use hardware keys
- written from scratch full touch code
- safe full touch : no wrongly validations while scrolling
- when you set full touch mode, it defaults to optimized settings for menu height, scroll sensitivity and touch accuracy (you still can alter them manually later)
- adjust scroll sensitivity in a huge palette
- adjust menu height in a huge palette
- adjust touch accuracy
- 30 color settings for each of the 8 GUI parts + 5 alpha transparency settings
- user custom background png can be selected in addition to 30 solid colors option
- show / hide background icon
- show / hide bottom virtual buttons
- show/hide + set color and transparency for menu line separators to match solid color themes, like Black...
- set number of bottom log rows to show
- Friendly Log View and pause on logs: no more miss logs during zip installs
- auto dim screen after user configurable delay
- auto turn off screen after user configurable delay
- adjust brightness and turn off screen with a gesture action
- show/hide clock and remaining battery %, even during nandroid operations
- clock and battery stats now effectively refresh every 30 seconds and during nandroid operations
- toggle vibrator on/off on touch
- toggle key repeat for volume up/down scrolling when maintained pressed
- key repeat also enabled for virtual buttons
- set time zone + 30mn offset + DST: correct time can now be set for nandroid backup path and clock
- time setting is now applied to all recovery session, including timestamp of created/modified files (v4.92.3+)
- capture recovery screen shots with a gesture action
- one file to save all settings
- backup and restore settings file
- reset to default settings option
- prompt to restore your settings from a backup when they are wiped by a new ROM install
- option to auto restore your settings from a backup without a prompt
- all toggles are applied live, without restart of recovery (except reset of stock CWM background image)
- toggle menu options are automatically right aligned and menu text left aligned based on device display size
- configurable gesture actions: double tap, slide right/left, long press/lift, long press/move, can be associated with any of: show log, change brightness, blank screen, capture screen shot, launch Aroma File ManagerNote: after scroll, first touch will select only. After one sec of scrolling or on second touch, it will validate immeadiately. This is by design and not a bug. It is there to limit erroneous validation while scrolling
Read more about it here: Validation Lock after scrolling
First to introduce true JB 4.2 migration: toggle between /data/media and /data/media/0
browse phone with root access using full GUI in Aroma File Manager
terminal access from recovery with root access through Aroma File Manager
Multi Zip Install menu: check multiple zip files to install in a row
Custom Install Zip Mode: set a default folder to start with + browse backward up to the root
exFAT, NTFS and Ext4 support in recovery for external sd
TWRP backup and restore support, include full md5 sum support (single and multivolume, compressed and non compressed formats)
Advanced statistics during backup operations shown in color: total backup size, backup size progress, backup time, compression ratio...
support .android_secure backup/restore from external storage
optional reboot after custom backups/restores
sd-ext support (ext4)
nandroid backups support /preload in backup and restore jobs (custom and stock modes)
nandroid backups support /misc in backup and restore jobs (custom mode)
set special nandroid settings: time zone, toggle md5 check for lightning fast backup and restore, toggle /preload backup and restore, enable nandroid compression using pigz (multi-cpu gzip compression) and choose ors backup target volume
recreate md5 sum check for your cwm backups for compatibility with stock CWM if you need to revert
you can cancel any nandroid operation with back button
create custom_rom.zip from current ROM or from a pre-existing nandroid backup (based on boot, /system and optionally /preload)
nandroid backup path now will be named with current ROM id from build.prop (ro.modversion, then ro.romversion, then ro.build.display.id)
custom backup and restore job list: backup and restore freely any partition combo (include modem and efs)
backup/restore EFS in both tar + img formats, now with time incremented copies for both tar and .img
support flash modem.bin image files in addition to custom modem.img files, now support for multiple *.bin versions under dedicated folder
during custom restore, you can see the contents of the folder you want to restore from
delete custom or TWRP backups from recovery menu
full wipe before flashing new ROM: wipe user data + format /system and /preload. SD card content is not affected
full support for openrecovery script specifications include all backup and restore options
run openrecovery scripts in 2 modes: on start goomanager boot scripts + one touch menu to either directly open a default path or freely browse for scripts
define ors backup target volume from within Nandroid Settings menu
ors restore path supports stock clockworkmod path or TWRP path
poweroff, reboot to recovery and reboot to download/bootloader mode options
dual USB mount in recovery support and mount external sd over usb for /data/media devices
adb root in recovery: just wait about a minute to activate
detailed build info in About menu
GT-N5100:
Odin flashable package = if you are on stock recovery you need this: RECOVERY_GT-N5100-CivZ_rev1.1-PhilZ_5-ODIN.tar
cwm flashable package = Only works when you are on a custom recovery: RECOVERY_GT-N5100-CivZ_rev1.1-PhilZ_5.zip = Recovery file manager included
GT-N5110:
Odin flashable package = if you are on stock recovery you need this: RECOVERY_GT-N5110-CivZ_rev1.1-PhilZ_5-ODIN.tar
cwm flashable package = Only works when you are on a custom recovery: RECOVERY_GT-N5110-CivZ_rev1.1-PhilZ_5.zip = Recovery file manager included
GT-N5120:
Odin flashable package = if you are on stock recovery you need this: RECOVERY_GT-N5120-CivZ_rev1.1-PhilZ_5-ODIN.tar
cwm flashable package = Only works when you are on a custom recovery: RECOVERY_GT-N5120-CivZ_rev1.1-PhilZ_5.zip = Recovery file manager included
CHANGELOG:
23/Okt/2013:
First touch release of this recovery ported from the Philz recovery.
24/Okt/2013: CivZ REV1.1 of the Philz touch 5 recovery
EFS backup changed to original : Backup to external or internal = It is stored as a hidden file in clockworkmod/backup.
Touch driver adjusted and rebuild the kernel for it.
Activated ntfs support in recovery kernel.
With the CWM install package the recovery filemanager is installed.
Click to expand...
Click to collapse
Maybe i forgot to tell you, until I push my sources to phil, try compiling with custom touch driver sources to get the touch interface working.
cm 10.1
plz port for us cm 10!N5100 :crying:
Is it possible to get a signed zip? I have a recovery installed, just not the CWM or TWRP (it is the stock one).
Flash this with odin, I doubt the touch will work properly. Even though, N5110 users try it.
emwno said:
Flash this with odin, I doubt the touch will work properly. Even though, N5110 users try it.
Click to expand...
Click to collapse
Touch and efs backup not working.
civato said:
Touch and efs backup not working.
Click to expand...
Click to collapse
Looks like ill wait till mine arrives and then debug alot. A question, does it not work at all? Or does it register them wrong?
EDIT: talking about the touch input
emwno said:
Looks like ill wait till mine arrives and then debug alot. A question, does it not work at all? Or does it register them wrong?
Click to expand...
Click to collapse
It register them wrong, if you look at it like a portrait mode recovery the buttons are situated for that kind of recovery.
example: pressing top right corner (landscape mode) is pressing the return button, so it is way off. But it is this way in all touch recovery's for now on this tablet. Not a real problem not having touch, for me the efs is more important.
It is the same with the aroma installer touch driver, it is way off so you need to use the hardware buttons.
civato said:
It register them wrong, if you look at it like a portrait mode recovery the buttons are situated for that kind of recovery.
example: pressing top right corner (landscape mode) is pressing the return button, so it is way off. But it is this way in all touch recovery's for now on this tablet. Not a real problem not having touch, for me the efs is more important.
It is the same with the aroma installer touch driver, it is way off so you need to use the hardware buttons.
Click to expand...
Click to collapse
This device is more of a hybrid, half of the time its acting like a tablet and other times like a phone. Ill build one for portrait now and upload in a few
---------- Update ----------
Test2. flash with odin.
1. If recovery is portrait, touch issues should be resolved
2. EFS backup should now be fixed
emwno said:
This device is more of a hybrid, half of the time its acting like a tablet and other times like a phone. Ill build one for portrait now and upload in a few
---------- Update ----------
Test2. flash with odin.
1. If recovery is portrait, touch issues should be resolved
2. EFS backup should now be fixed
Click to expand...
Click to collapse
Still in landscape so touch is still off and efs backup still doesn't work.
It looks like it makes a backup but it don't.
civato said:
Still in landscape so touch is still off and efs backup still doesn't work.
It looks like it makes a backup but it don't.
Click to expand...
Click to collapse
think ill just use ameer's script to backup everything via recovery. and about recovery being portrait, i have one more thing i can try, ill do that tomorrow. for now ill just update kernels to .79
bump?
anyone knows if there's a chance for working PhilZ in foreseeable future?
can I use this recovery instead of CWM or TWRP, flashing your ROM - CivZ-FLEXBEAM-4.2.2-Rev1.5?
on OP instruction on your ROM, it says "Install with CWM or TWRP", I am not sure if PhilZ touch works too?
I don't see why not since it is based on CWM advanced edition.
Full touch version released
New release
Download in OP :
* * * * * * * * * * * * * * * * * * * * * * * * *
PhilZ Touch 5 Recovery
CWM Advanced Edition 6.x
* * * * * * * * * * * * * * * * * * * * * * * * *
Features of this ported recovery:
RECOVERY IS IN TABLET MODE
Touch recovery based on cwm 6.0...
zImage compiled by civato based on Samsung Update2 with Exfat support
Touch driver fixed for aroma thanks to nickdollahz
Backup / restore
Custom backup / restore
EFS backup / restore: backup is automatic stored as a efs.img on the internal_SD and external_SD (clockworkmod/efsbackup) This was modded by me as the original didn't work, this is based on the emwo script.
Change theme layout and touch settings
TWRP and CWM restore support
Format data/media = internal_SD will be empty.
Power menu
etc..............................
REV1.1 released
24/Okt/2013: CivZ REV1.1 of the Philz touch 5 recovery
EFS backup changed to original : Backup to external or internal = It is stored as a hidden file in clockworkmod/backup.
Touch driver adjusted and rebuild the kernel for it.
Activated ntfs support in recovery kernel.
With the CWM install package the recovery filemanager is installed.
Download in OP
Thanks civato.. In the other forums they just tell us how worthless CWM is. Here you guys fix it and make it better...Worked like a charm.. k9time
Sent from my GT-N5100 using XDA Premium 4 mobile app
Hi would this work on stock 4.1.2? Just rooted device but has no recovery ..
Sent from my GT-N5110 using xda premium
Valholy said:
Hi would this work on stock 4.1.2? Just rooted device but has no recovery ..
Sent from my GT-N5110 using xda premium
Click to expand...
Click to collapse
Yes it works with stock 4.1.2 but if you're on stock recovery, then you have to flash this with odin because you can't flash a custom recovery with a stock recovery. If you already have a custom recovery, then you can flash this with that, but I assume you're still on stock recovery. So:
1. You need a computer with odin and proper samsung drivers installed
2. Download the right GT-N5110 .tar file from this thread
3. Go to download mode and open odin
4. Make sure you have F.Reset time and Auto-reboot checked
5. Click on PDA and choose the .tar file and then flash it
And you're done
Sent from my GT-N5110 using XDA Premium 4 mobile app
Thanks a lot will try it out
Sent from my GT-N5110 using xda premium
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.
Code:
#include
/*
* Your warranty is now void.
*
* 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 ROM
* 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.
*/
{
"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:
[CENTER]
[B][I][U][COLOR=Red]BUILD 11[/COLOR][/U][/I][/B]
[list]
[*] Bump to v2.8.5
[/list]
[B][I][U][COLOR=Red]BUILD 10[/COLOR][/U][/I][/B]
[list]
[*]Bump to v2.8.5
[*]Updated with latest cm12 tree
[/list]
[B][I][U][COLOR=Red]BUILD 9[/COLOR][/U][/I][/B]
[list]
[*] Bump to 2.8.4
[/list]
[B][I][U][COLOR=Red]BUILD 8[/COLOR][/U][/I][/B]
[list]
[*] bump to 2.8.3.0
[*] updated with cm12 tree
[/list]
[B][I][U][COLOR=Red]BUILD 7
[/COLOR][/U][/I][/B][COLOR=Red][COLOR=Black]BUMP TO 2.8.1.0
REVERTED F2FS FOR NOW .
RECOVERY IS FULLY STABLE
[/COLOR][/COLOR] [B][I][U][COLOR=Red]
BUILD 6[/COLOR][/U][/I][/B]
-FIXED MOUNT OF F2FS PARTITIONS
[B][I][U][COLOR=Red]BUILD 5[/COLOR][/U][/I][/B]
BACKUP AND RESTORE FIXED
MERGED WITH 2.8.0.0
[B][U]
[COLOR=Red]
BUILD 4 SKIPPED
BUILD 3
[/COLOR][/U][/B]ADDED F2FS SUPPORT
[URL="http://forum.xda-developers.com/showthread.php?t=2594669"][B]USED NEBULA KERNEL TREE BY @[/B][/URL][B][URL="http://forum.xda-developers.com/member.php?u=5273865"]xenon92[/URL] (Big Thanx!!!)[/B]
[B][U][COLOR=Red]BUILD 2[/COLOR][/U][/B]
FIXED INTERNAL SD CARD
[B][U][COLOR=Red]BUILD 1[/COLOR][/U][/B]
INITIAL BUILD[/CENTER]
Code:
[COLOR=Red][B]NOTE(build3 onwards)[/B][/COLOR]: instead of flashing k2wl's file to format recovery partitions..
1.u can simply go to wipe/advanced wipe ...
2.choose the partitions (data,system and cache)....
3. select change filesystem format and choose f2fs ..
once its done .. u can flash the desired f2fs rom!!!!
and to revert to ext4 u hv to follow the same procedure STEP 1 &2 and then change filesystem to ext4
CHANGELOG for 2.8.0.0:
Fix a bug that caused weird graphics and touch issues
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
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.
CHANGELOG for 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
CHANGELOG for 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.
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
DOWNLOAD:
DOWNLOADS
THEMES
HOW TO APPLY THE THEME???
STEP 1: DOWNLOAD ANY THEME FROM THE ABOVE LINK
STEP 2: RENAME THE ZIP TO ui.zip
STEP 3: COPY IT TO THE INTERNAL SD CARD / TWRP/themes folder (if the "themes " folder isnt there,... simply create one)
STEP 4:REBOOT TO RECOVERY!!!! YOU HAVE APPLIED YOUR THEME SUCCESSFULLY !!!! ENJOY !!
SOURCES
DEVICE TREE
KERNEL ( a big thanx to @ xenon92 for his nebula kernel source)= Original Thread
BUGS:
U TELL ME !
CREDITS
TWRP
@xenon92 -nebula kernel
@k2wl
@LuK1337
GALAXY GRAND DEVELOPMENT AND TESTERS GROUP
TEAM AOGP :-d
good work bro..............:good::good::good:
zip file is unable to flash getting... status 6....[emoji16]
and tar file can be flashed using odin[emoji3][emoji106]
recovery is superb[emoji5] and the multi zip flashing is great....
but phone internal memory is not supported I think[emoji42]
Redownload it ... Just fixed the link
EDIT : phone memory ..as stated in the op is a bug .. il try to fix it ASAP
its awesome I like It...
@rutvikrvr
Look at my twrp.fstab maybe it will help you.
https://github.com/luk1337/android_device_samsung_s2vep/blob/du44/ramdisk/twrp.fstab
hello any news for "INTERNAL SD CARD NOT SHOWING" bug..
Mohanshbhr said:
hello any news for "INTERNAL SD CARD NOT SHOWING" bug..
Click to expand...
Click to collapse
I'm gonna try today ... 99% it will be fixed
EDIT : BUILD 2 is UP ... internal sd card fixed ... thanx to @LuK1337
download link in OP
rutvikrvr said:
I'm gonna try today ... 99% it will be fixed
EDIT : BUILD 2 is UP ... internal sd card fixed ... thanx to @LuK1337
download link in OP
Click to expand...
Click to collapse
thanks... its my favourite recovery.. thanks a lot..
Mohanshbhr said:
thanks... its my favourite recovery.. thanks a lot..
Click to expand...
Click to collapse
yea mine too .. love it ...especially the install multiple zips
Supppaaa Recovery Mr. Rutvik:laugh::laugh::laugh:
Build 3 is up!!
Build 3
added f2fs support ... THANX TO @k2wl
Download link in op!
NOTE: instead of flashing k2wl's file to format recovery partitions..
1.u can simply go to wipe/advanced wipe ...
2.choose the partitions (data,system and cache)....
3. select change filesystem format and choose f2fs ..
once its done .. u can flash the desired f2fs rom!!!!
and to revert to ext4 u hv to follow the same procedure STEP 1 &2 and then change filesystem to ext4
Thanks for superb recovery! and do i need to flash latest build without f2fs ?
recovery looks awesome with holofied play theme....
Mohanshbhr said:
recovery looks awesome with holofied play theme....
Click to expand...
Click to collapse
u ported it fr hdpi??? if so give me the link .. il add it to OP
Parth2187 said:
Thanks for superb recovery! and do i need to flash latest build without f2fs ?
Click to expand...
Click to collapse
yes u can flash with or without f2fs ...coz only ur data,system and cache partitions are formatted to f2fs
rutvikrvr said:
u ported it fr hdpi??? if so give me the link .. il add it to OP
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2684621
It's not mounting system , data, cache after converting to f2fs, so reverted back.... tried 2 times...
How to fix it????
Sent from my GT-I9082 using XDA Premium 4 mobile app
maxxinn said:
It's not mounting system , data, cache after converting to f2fs, so reverted back.... tried 2 times...
How to fox it????
Sent from my GT-I9082 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm sorry abt that… I forgot to add f2fs to the recovery.fstab… il fix it tom… thanx fr the report
rutvikrvr said:
I'm sorry abt that… I forgot to add f2fs to the recovery.fstab… il fix it tom… thanx fr the report
Click to expand...
Click to collapse
Thanks bro..
Sent from my GT-I9082 using XDA Premium 4 mobile app
{
"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.2
For devices: Kenzo & Kate
Authors build: ATG Droid
Developers: ATG Droid
Thanks: z31s1g (for the base of his theme), osm0sis (for his bootimage binaries), etc.
Features:
Code:
[B]Translated to EN & CZ [/B]
- Password protection
- Flashlight
- MIUI Incremental OTA Support
- Support automatic reboot after the restore process
- Advanced deactivation of the stock recovery
- Support for automatic deactivation of the dm-verity & forced encryption...
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- A lot of other things, just look at it ;)
*[B] Changes for security reasons [/B]*
- MTP isn't starting until user enter correct password
- Deactivated support of the custom themes
Some differences to the official version:
Code:
[B][COLOR="red"]- get out of here if you are pirating apps. this recovery is not for you[/COLOR][/B]
- 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:
[B][U]RedWolf-V3.2.1_028-Kate_Kenzo-Beta.img[/U][/B]
* File-manager: Add support for rendering of multiple selected files & ability to do a specific action for these files at once
* Force rendering of the different GUI icon element object for zip files under the GUI Scroll list, since file-manager show special action for them
* Revert changes which caused issues with slow reboot in 027
* MIUI-Updater: Fix sometimes possible double declaration of the final install status
* DataManager: Fix the TWRP's missing LOGINFO mount point for Output_Version
* RWDumwolf: Add support for the different fstab path on some devices
* RWDumwolf: Better handle the process of modifications to the default properties and let user know about the number of modified ones
* RWDumwolf: Find and remove start of flash_recovery service from inits, if it exists
* Recovery: Don't rename scripts under the /system/bin /system/etc for stock recovery replace, instead of it set different permissions to cause issues with execution
* RWDumwolf: Cleanup
* Updater: Properly handle info about the OSE package signature
* Recovery: Directly call start of the ADB if at the start of main we aren't able stat password file
* Recovery: Correctly handle ADB with recovery password related changes
* Recovery: Update to Oreo tree
* Partition-List: Add new list types for OSE partitions and storages for backup/restore process
* Installation: Load zip entries directly to buffer instead of extracting them
* ORS: Reboot on the sucessfull installation is now optional based on user's selection from the GUI
* ORS: Call Deactivation Process even if reboot on finished ORS isn't allowed or isn't forced by the ORS result
* OPTM: Call set action with the empty value in case that value should be positive
* OPTM: Fallback to main without variable which would be needed to be parsed is now directly down with call of home
* GUI: Allow user to select any active storage for the OSE backup/restore process
* OPTM: Call clear action instead of set if argument is negative
* GUI: Allow user to select OSE partitions for the backup/restore process, instead of the previous direct definition
* Installation: Add support for the format of A/B packages on the OSE zip detection
* GUI: Remove redefinitions of objects from screen page, since they're already defined on one overlay
* PartitionManager: Add new fstab flag to exlude partition from the GUI mount section, cust isn't really needed to be here if we want to use double mount points for one block device
* GUI: Remove for us the useless theme loading parts from previous builds
* Installation: Set install status info to tmpfs first and then update the status in cache during the log file update, since the previous implementation was just slowing us
* Recovery: Set path for screenshots directly to main folder instead of previous resource one
* TWFunc: Cleanup
* GUI: Improve flashlight compatibility with different devices
* OSE: Improve backup/restore call
* Device-Tree: Add support for unofficial treble support on officialy supported devices
* GUI: Fix missing page on the rebootcheck call which caused complete lag during the reboot with formatted system partition
* Recovery: Call Deactivation Process on reboot if there wasn't at least single call during the main threads
* RWDumwolf: Force persist.sys.recovery_update to false during the cleanup process
* OSE: Fix the variable mismatch caused by global variable definitions without handling the previous possible defined value
* INIT: Add new triggers for the ADB startUP.
[B][U]RedWolf-V3.2.1_027-Kate_Kenzo.img[/U][/B]
- 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...
[B][U]RedWolf-V3.2.1_026-Kate_Kenzo.img[/U][/B]
- 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.
[B][U]RedWolf-V3.2.1_025-Kate_Kenzo.img[/U][/B]
- 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
+ Some device specific changes...
Installation instructions:
- Download image and flash it the way you want.. You can use some apps, fastboot or your current custom recovery (if it's supported).
Known Bugs:
- There isn't any!
Downloads:
Latest build for Xiaomi Redmi Note 3 PRO/SE (Kenzo/Kate)
Links to builds:
RedWolf-028-kenzo-Beta.img
Links to MD5 files:
RedWolf-028-kenzo-Beta.img.md5
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
Red Wolf Recovery Project, Tool/Utility for the Xiaomi Redmi Note 3
Contributors
ATG Droid, Dadi11
Source Code: https://github.com/RedWolfRecovery
Version Information
Status: Testing
Created 2017-07-08
Last Updated 2018-07-22
Reserved
Kernel: https://github.com/TeamHorizon/android_kernel_xiaomi_kenzo/tree/o
Reserved
Screenshots!!
Woow new twrp
Thanks DEV. With every new and advanced developments like this, our DEVICE keeps on reviving. Thank you very much.
will test it and let you know if anything is quirky.
:good::good::good::good::good:
ATG Droid said:
Known Bugs:
Search engine for Snap Camera is right now broken. It's still searching for TWRP app so if you want to use it then you have to unfortunately uninstall official TWRP app.
Click to expand...
Click to collapse
So if i don't install twrp app, will snap camera search engine work?
Oh another recovery
Does the bug which causes this recovery non functional on Kenzo but functional on Kate fixed? And is it stable now?
Does it support f2fs?
Sent from my Redmi Note 3 using XDA Labs
AliGulzar-AF said:
Does the bug which causes this recovery non functional on Kenzo but functional on Kate fixed? And is it stable now?
Click to expand...
Click to collapse
+1, same question here. The password protection is the feature I've been waiting for so long.
rád tě zase vidím @ATG Droid
Still not working on kenzo grains/glitches on screen when i open in recovery.
sushank360 said:
Still not working on kenzo grains/glitches on screen when i open in recovery.
Click to expand...
Click to collapse
Thanks for confirming
Sent from my Redmi Note 3 using XDA Labs
I' using Kate so i can't test it.. So if there is someone who have Kenzo then please test if it is working.
sushank360 said:
Still not working on kenzo grains/glitches on screen when i open in recovery.
Click to expand...
Click to collapse
Thanks for reporting...
Using kenzo here..
Everything seems to be working normally
Haven't flashed any zip yet.
Will update later
exodius48 said:
So if i don't install twrp app, will snap camera search engine work?
Click to expand...
Click to collapse
If you have installed TWRP app on your device then recovery will not allow you to install Snap Camera.. Also if you don't have installed TWRP app then recovery will continually offer installation of the Snap Camera even if Snap Camera is installed.. But this bug shouldn't be a huge problem to fix in the next updates.
Password protection is the best
guess the password feature should br adopted to official twrp ...anyway nice work mate except for some wierd blurry screen on kenzo sometimes :fingers-crossed:
I forget that there is also option to get notified about finished installation.. Just try to click on install / find some zip file / and before you swipe to install it check here "Notify about finished installation".. :fingers-crossed:
Edit: Just uploaded new build for Kenzo.. So please test it and report back.
For me the latest version for kenzo is working perfectly i have also clean flashed a rom and it's working. I found only one bug: the shutdown from reboot menu isn't working.
{
"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.2
For device: Enchilada
Features
Translated to EN & CZ
- Password protection
- Flashlight(Currently Broken)
- 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.
* Changes for security reasons *
- 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
Some differences
- get out of here if you are pirating apps. this recovery is not for you
- compiled on omnirom-8.1 source
- There isn't bug with reboot from recovery to recovery
Changelog
Code:
Initial Build
Bugs:
1)Flashlight doesnt work (only on recovery)
2)Aroma Installer doesn't work
3)If flashing MTP build, on boot if you enter wrong pattern it causes it to crash wherein you'd need to reboot by long pressing power button.
4) password protection doesn't work.
Fixed:
1) Vibration/Haptic Feedback has been fixed
2) encryption/Decryption now work
Glitches
1) Sometimes mtp doesn't work dircetly when booted into recovery. For MTP to work, once booted into recovery go to mount, and tap on disable mtp and then tap enable mtp.
2) When you select any option in reboot, it redirects to recovery. Do the same again and it will work
(For ex: you tap on reboot>system, it redirects to recovery. then again tap reboot>system it will work)
******************Installation Instructions******************
1)Flashing through a Custom Recovery
- Download the RedWolf-installer-enchilada-3.2.2-0.zip
- Copy the zip to your phone's internal storage
- Flash the zip and you're good to go
2)People who don't have any custom recovery(through fastboot)
- Download both RedWolf-installer-enchilada-3.2.2-0.zip & RedWolf-027-Unofficial-enchilada.img into your pc.
- Copy RedWolf-recovery-installer.zip to the internal storage of your phone.
- In PC go to the dir where you downloaded the RedWolf-027-Unofficial-enchilada.img
-Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here (or) open powershell here
- Now switch off your phone, connect your phone to pc using the original cable provided.
- Press power button + vol up button to boot into bootloader.
- In thecmd on your pc type :
Code:
fastboot boot RedWolf-027-Unofficial-enchilada.img
- In a few moments your phone will boot into RedWolfRecovery.
- Once booted into recovery immediately press install and locate the redwolfinstaller zip that you copied into your phone and flash it.
- Wait for it to Flash.
- and you've successfully flashed RedWolf-Recovery
DOWNLOADS
RedWolf-Recovery(MTP) for enchilada(OnePlus6)
RedWolf-Recovery(NO-MTP) for enchilada(OnePlus6)
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.
Sources:
DeviceTree
RedWolf
Credits: @dees-Troy && @wuxianlin for their sources
OMNI rom for twrp
RedWolf Team for the RedWolf source
A big thanks to @joemossjr for fixing the issues with recovery not booting
@notsyncing on github for the fixes
@Titokhan for helping me with a and b
me for compiling and testing and fixing Haptic Feedback on RedWolf
So guys the builds and testing are finally done.
As told i have uploaded two builds with mtp and without mtp
Based on twrp 3.2.2 source
Bugs:
1)Flashlight doesnt work (only on recovery)
2)Aroma Installer doesn't work
3)If flashing MTP build, on boot if you enter wrong pattern it causes it to crash wherein you'd need to reboot by long pressing power button.
Fixed:
1) Vibration/Haptic Feedback has been fixed
2) encryption/Decryption now work
Glitches
1) Sometimes mtp doesn't work dircetly when booted into recovery. For MTP to work, once booted into recovery go to mount, and tap on disable mtp and then tap enable mtp.
2) When you select any option in reboot, it redirects to recovery. Do the same again and it will work
(For ex: you tap on reboot>system, it redirects to recovery. then again tap reboot>system it will work)
CREDITS
A big thanks to @joemossjr for fixing the issues with recovery not booting
also thanks to wuxianlin and Dees_Troy for the sources @notsyncing on github for the fixes
The Download links and Instructions will be updated in OP
Dated : 09-07-2018
Is Aroma Installer working?
Regards
Lol I built this a few weeks ago
---------- Post added at 03:08 AM ---------- Previous post was at 02:52 AM ----------
encryption doent work
Only for the One Plus 6? Any plans on expanding to other devices?
Eliminater said:
Is Aroma Installer working?
Regards
Click to expand...
Click to collapse
It should, Not tried though
joemossjr said:
Lol I built this a few weeks ago
---------- Post added at 03:08 AM ---------- Previous post was at 02:52 AM ----------
encryption doent work
Click to expand...
Click to collapse
Damn I didn't notice that.... my bad
Updated for now in OP
jdmst77 said:
Only for the One Plus 6? Any plans on expanding to other devices?
Click to expand...
Click to collapse
That's not dependant on me mate
pranavasri said:
Damn I didn't notice that.... my bad
Updated for now in OP
Click to expand...
Click to collapse
Np it's probably due to the 7.1 branch your using btw why are you using the 7.1 branch again?
joemossjr said:
Np it's probably due to the 7.1 branch your using btw why are you using the 7.1 branch again?
Click to expand...
Click to collapse
their 8.1 sources gave issues while compiling(probably due to device sources, so i went with 7.1 source )
pranavasri said:
their 8.1 sources gave issues while compiling(probably due to device sources, so i went with 7.1 source )
Click to expand...
Click to collapse
Ah. Yeah that's where you messed up what was the errors? I've got about every single one lol plus the 8.1 branch has the proper decryption for us lol
joemossjr said:
Ah. Yeah that's where you messed up what was the errors? I've got about every single one lol plus the 8.1 branch has the proper decryption for us lol
Click to expand...
Click to collapse
Shall i PM
pranavasri said:
Shall i PM
Click to expand...
Click to collapse
I'll do you one better hit me up on Hangouts @ [email protected]
Eliminater said:
Is Aroma Installer working?
Regards
Click to expand...
Click to collapse
No, aroma is not working and even core functionality like decryption of the data partition don't work.
xXx said:
No, aroma is not working and even core functionality like decryption of the data partition don't work.
Click to expand...
Click to collapse
Chill man we will get it working
is DM verity and force encrypt disabled? how'd you achieve this? is it only for installing rom after recovery? (format data) or another way?
can you please explain @pranavasri
virtyx said:
is DM verity and force encrypt disabled? how'd you achieve this? is it only for installing rom after recovery? (format data) or another way?
can you please explain @pranavasri
Click to expand...
Click to collapse
I wouldn't say they are disabled but yes they might not work, (looks like it's because i've used nougat source) i didn't get thelast part of your question
pranavasri said:
I wouldn't say they are disabled but yes they might not work, (looks like it's because i've used nougat source) i didn't get thelast part of your question
Click to expand...
Click to collapse
firstly we need a TWRP with decrypt possible for us to disable encryption
and also the ability to edit the fstab in /vendor partition (/vendor/etc/ there are 2 fstab files we need to edit and remove force encrypt to encryptable)
i have tried this with official twrp and didnt work
i cant seem to mount /vendor as R/W in OS or TWRP my changes dont stick for some reason.
@pranavasri
Thank you for sharing.
I'm gonna give it a try!
pranavasri said:
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 device: Enchilada
Features
Translated to EN & CZ
- Password protection
- Flashlight(Currently Broken)
- 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.
* Changes for security reasons *
- 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
Some differences
- get out of here if you are pirating apps. this recovery is not for you
- compiled on omnirom-7.1 source
- There isn't bug with reboot from recovery to recovery
Changelog
Code:
Initial Build
Bugs
-Mtp removed (same reason as for the official build)(only in recovery)
-flashlight doesn't work
-encryption doesn't work. thnx to @joemossjr for letting me know
******************Installation Instructions******************
1)Flashing through a Custom Recovery
- Download the RedWolf-recovery-installer.zip
- Copy the zip to your phone's internal storage
- Flash the zip and you're good to go
2)People who don't have any custom recovery(through fastboot)
- Download both RedWolf-recovery-installer.zip & RedWolf-027-Unofficial-enchilada.img into your pc.
- Copy RedWolf-recovery-installer.zip to the internal storage of your phone.
- In PC go to the dir where you downloaded the RedWolf-027-Unofficial-enchilada.img
-Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here (or) open powershell here
- Now switch off your phone, connect your phone to pc using the original cable provided.
- Press power button + vol up button to boot into bootloader.
- In thecmd on your pc type :
Code:
fastboot boot RedWolf-027-Unofficial-enchilada.img
- In a few moments your phone will boot into RedWolfRecovery.
- Once booted into recovery immediately press install and locate the redwolfinstaller zip that you copied into your phone and flash it.
- Wait for it to Flash.
- and you've successfully flashed RedWolf-Recovery
DOWNLOADS
RedWolf-Recovery for enchilada(OnePlus6)
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.
Sources:
DeviceTree
RedWolf
Credits: @dees-Troy && @wuxianlin for their sources
OMNI rom for twrp
RedWolf Team for the RedWolf source
@Titokhan for helping me with a and b
me for compiling and testing
Click to expand...
Click to collapse
If I don't like or want to revert back to TWRP can I flash TWRP from within red wolf?
---------- Post added at 10:36 PM ---------- Previous post was at 10:31 PM ----------
virtyx said:
firstly we need a TWRP with decrypt possible for us to disable encryption
and also the ability to edit the fstab in /vendor partition (/vendor/etc/ there are 2 fstab files we need to edit and remove force encrypt to encryptable)
i have tried this with official twrp and didnt work
i cant seem to mount /vendor as R/W in OS or TWRP my changes dont stick for some reason.
Click to expand...
Click to collapse
As far as decrypting in TWRP check my post here. https://forum.xda-developers.com/showpost.php?p=76845815&postcount=14
I was able to do it. Here's the whole thread. https://forum.xda-developers.com/oneplus-6/help/soft-brick-restoring-backup-twrp-t3805112