Database Develop

[RECOVERY][OFFICIAL][All Bugs Fixed][TOUCH] TWRP v 2.4.2.0 / 2.6.0.0

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.

[APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!

Credits:
birbeck for the usual random java guidance, slushpupie for his previous java guidance, dodgejcr for extreme amounts of testing, and one_love_420 and shift for some great graphics!
testers: JT-, couga6442, happytweak and many others I might have forgot in the furry of three days I built the initial app from scratch.!
Thanks to SDX
Works with HTC Unlock Method:
Tested after using htcdev.com's bootloader unlock method.
Please see the guides at the bottom of this post!
Background:
flash_image (bmlwrite) is an extremely useful utility for flashing custom kernels, boot logos (so far ONLY Samsung devices) and recoveries. This binary has made it possible to easily flash all these items and is used almost everywhere behind the scenes (i.e. in custom recoveries, packaged into a kernel /sbin directoy, included in custom ROMs, etc).
Description:
This android application, FlashImageGUI, is basically a GUI interface for the linux binary, flash_image provided by google in AOSP for loading custom kernels and recovery images onto the phone.
This app allows the flashing of kernels and custom recovery images in normal android mode!
Current Device Support:
Full Kernel, Logo and Recovery flashing: Samsung Moment, Transform, Intercept and Acclaim - the s3c6410 series of devices
Full Kernel (Anykernel and boot.img) Flashing and Recovery (zip file or image) flashing: Sprint HTC One, T-Mobile HTC One, HTC EVO 4G LTE, One S, EVO 3D CDMA and GSM, One XL, Droid DNA, Amaze, Vivid/Holiday, EVO 4G, EVO Shift, Google Nexus 4, Google Nexus 10, Google Nexus 7, Samsung Google Galaxy Nexus, Nexus S/Nexus S 4G & LG Optimus
Full Kernel (zImage) Flashing: Samsung Epic
Check application version for updates
Future Support:
Will continue to test kernels as they are released to ensure compatibility!
YouTube Install Video:
http://www.youtube.com/watch?v=9aqnhFxb__k
Thanks @wwjoshdew !
Install Directions:
Install process is the same as any other .apk. Download to computer and adb push or mount sdcard on computer and copy over or download directly to the phone. Use any file manager, adb, connectbot/terminal emulator to install.
My preferred method, maybe a bit technical: ./adb install c:\downloads\FlashImageGUI.apk
Download Locations
Market (99 cents!): Flash Image GUI
Release version (free): Flash Image GUI
Contact:
Any questions, comments, concerns, or issues, please post in this thread or send me an email! Thanks for all the help and support!
FAQ:
Q: Will this app support a marketplace to pick and chose kernels from?
A: No. Use Kernel Manager!
Q: Can I flash nandroid kernel backups?
A: Yes. Rename the specific image to boot.img and select from inside of Flash Image GUI. **Make sure to also load the associated modules or WiFi might stop working!
Screenshots:
{
"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"
}
Feedback:
Please post any helpful feedback. I'm always looking to improve the application!
HTC Unlock - User Guides for Flash Image GUI!!
HTC Unlock - Users Guide for ROMs with a Kernel (boot.img file):
1) Unlock using the HTC method and gain root access.
2) Load this application, Flash Image GUI, onto the device, either through the Market or the link provided in this OP.
3) Download ROM .zip file to the sdcard on the device.
4) Open up Flash Image GUI, select Browse and select the ROM .zip file, downloaded to /sdcard in the previous step.
5) Flash Image GUI will provide a warning, reminding that the ROM .zip file will *need* to be flashed in the custom recovery afterward.
6) Flash Image GUI will index the full ROM .zip file searching for the kernel and kernel modules. Once located, the Flash Image button should be enabled.
7) Select the Flash Image button and Flash Image GUI will load the kernel modules and kernel from inside the ROM zip file.
8) Select reboot recovery.
9) Inside the custom recovery, wipe data as ROM requires and load/flash the ROM zip file.
10) Reboot to normal Android mode and all should work including WiFi!
HTC Unlock - Users Guide for flashing ONLY a Kernel (zip file):
1) Unlock using the HTC method and gain root access.
2) Make sure the selected Kernel is compatible with the currently loaded ROM. If not, this will result in a lot of frustration!!! See troubleshooting steps below.
3) Download kernel zip file to /sdcard.
4) Open Flash Image GUI, browse and select kernel zip file, downloaded/loaded to sdcard in previous step.
5) Flash Image GUI will validate the kernel zip file is contains the minimum required files
6) Select the Flash Image button and Flash Image GUI will load the kernel and the kernel modules from the source kernel zip file.
7) Reboot
Troubleshooting after Rebooting:
First step, when experiencing issues flashing is to RE FLASH the files again. Many times, re flashing again will clear up any issues. If not, see the issues/solutions below.
Issue #1: If the device hangs or reboots while on the splash screen, the kernel itself or the ramdisk packaged in the kernel is NOT compatible with your device!!!
Solution for #1: Have to boot into fastboot (or directly into the custom recovery) and load the custom recovery to flash a known good kernel or restore a previously known good nandroid backup. Command: fastboot boot c:\downloads\cwm-recovery.img
Issue #2: If the device hangs or reboots while on the boot animation, the ROM is likely NOT compatible with the kernel!!!
Solution for #2: Have to boot into fastboot and load the custom recovery to flash a known good ROM/kernel combination either from a zip file or restore from a nandroid backup.

I actually used this app the other day I used on my evo lte a lot before s-off. Also makes flashing kernels and recoveries a breeze
Sent from my HTCONE using xda premium

This is a great app. Been using it for a while....thanks.
via phONE.

For the guys who never used it,it works great. Forgot how much it was but it was worth every dime.
Just an amazing app.
Sent from my HTCONE using Tapatalk 2

I made a video showing how to update/install custom recovery using your app! Thanks @joeykrim!
http://www.youtube.com/watch?v=9aqnhFxb__k

wwjoshdew said:
I made a video showing how to update/install custom recovery using your app! Thanks @joeykrim!
http://www.youtube.com/watch?v=9aqnhFxb__k
Click to expand...
Click to collapse
Excellent! I've added a link in the OP. Thanks!

App didn't seem to like philz_touch_5.08.5-m7spr.img wouldn't work for me, verified md5 downloaded it twice wouldn't work, then I renamed it to TWRP.img and finally it work and would allow me to hit the Flash Image button.

im0rtalz said:
App didn't seem to like philz_touch_5.08.5-m7spr.img wouldn't work for me, verified md5 downloaded it twice wouldn't work, then I renamed it to TWRP.img and finally it work and would allow me to hit the Flash Image button.
Click to expand...
Click to collapse
The error message that occurs each time you select a file that doesn't fit the naming criteria says, for a boot.img file, it needs to have the phrase "boot" in the name. Just need to add "boot" to the filename, for example: philz_touch_5.08.5-m7spr-boot.img.
Unfortunately, this limitation came about from beginners flashing incorrect files and overwriting their kernels so the device wouldn't boot. No real way around that issue other than silly filename limitations in an effort to education the users.
I test out the function real quick and the error message does come and go fairly quickly. I'll look at adjusting that so it the error message sticks around a bit longer to make it easier to read it.
Thanks for the feedback and hope that helps!

Thanks for the quick reply. This was definately worth the 99 cents. Since I can never get fastboot drivers to work on windows 8.

Myself, I prefer to adb .img's. But for a person who isnt as familiar with adb or someone who just doesnt want to, this is a great app, well worth the .99cnts. Thanks joey.
***Sent from my Super Groovy Hand Held Porno Machine***

Will this let us flash a firmware update instead of using adb? Thanks
Sent from my HTCONE using Xparent Blue Tapatalk 2

treIII said:
Will this let us flash a firmware update instead of using adb? Thanks
Sent from my HTCONE using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Unfortunately, as far as I've seen HTC doesn't allow direct access to the firmware components from the standard booted Android mode. If you see any new information on how to access the firmware components directly, feel free to provide the links here and I'll research.
Thanks for the support!

[DEV] CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.41.6

Main thread + Features + Dev support
http://forum.xda-developers.com/showthread.php?t=2201860
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.41.6​
PhilZ Recovery is a CWM Advanced Edition that adds all the features you could ever miss in CWM.
It is a well proven recovery for many phones.
Please give your feedback, what works, and any bug you could encounter.
Read the features at the Main thread, and check if you are missing something.
To take a screen shot, just slide left!
And don't forget to read about powerful aroma file manager integration and double-tap shortcut (in FAQs).
How to install recovery?
From download link below, you'll get a 'recovery.img' file. Put that recovery.img file at root directory of your
sdcard. (means not in any folder)
Now, go to terminal emulator.
Give command:
Code:
su
You'll be asked to grant superuser permissions, grant it.
Now, give the following command:
Code:
flash_image recoveryonly /sdcard/recovery.img
Wait until it executes the command (4-5 seconds), it is installing the recovery.
Now, normally reboot to recovery and enjoy new recovery!
Download links
Latest version can be found here:
recovery.img (v6.41.6)
https://docs.google.com/uc?id=0B5c3gpyMBJusWi1XN09fZjkzUWM&export=download
aromafm_tass.zip (v1.91)
https://drive.google.com/uc?id=0B5c3gpyMBJusLTk5ZENsNWpudms&export=download
Click to expand...
Click to collapse
Special thanks to:
@Phil3759 : For this awesome open source recovery.
@chraso: For hosting and compatible flags.
AndroidARMv6 Team: For keeping this device alive.
Cyanogenmod Team: For making all these possible.
XDA:DevDB Information
PhilZ-Touch Recovery for Galaxy Mini, Tool/Utility for the Samsung Galaxy Mini
Contributors
Bhargav97, chraso, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.40.1
Stable Release Date: 2014-05-04
Created 2014-05-07
Last Updated 2014-05-26

:FAQs:​
Q: Wanna know about Aroma File manager?
Visit the aroma file manager main thread for more info---> Aroma file manager main thread
Aroma file manager is a touch file manager which can be used while in recovery. It has options for copy, paste, delete,
change permissions and many others. Also, it has a Terminal inside. So, if you forgot to give correct permissions to any
file you can do that directly from recovery. This file manager has got many themes, font, icons, etc. options and it's UI
is fully customizable.
Q: How to start this File manager in Recovery?
Rename the downloaded file to 'aromafm.zip'.
Create a folder 'aromafm' inside 'Clockworkmod' folder on your sdcard.
Now, move that 'aromafm.zip' file to the 'aromafm' folder.
We're ready now, when you want to use it in recovery just double tap anywhere OR go to "philz Settings" and select
"Aroma File Manager" and it will start up.
If you also want to browse /data, /system and /sd-ext then mount them in the "mounts & storage" option in recovery.
Q: Problems with Aroma file manager startup?
After doble-tapping OR selecting 'Aroma file Manager' option under 'philz settings' if recovery gives error: 'aromafm.zip
not found at /clockworkmod/aromafm' then, wait for 4-5 seconds and again select 'Aroma file Manager', because it maybe
busy mounting sdcard.
If still doesn't work, you've made mistakes in steps mentioned in first post, please do again carefully.
Q: Does your phone every time reboots to recovery?
This happens very rare when you flash the recovery using any bad app or via any wrong (not proper) method. What you can do
is:
-If you've made a backup of your current ROM then just restore only it's "boot" and then select 'reboot to system'.
OR
-You don't have a backup? Then just flash the ROM which you are using currently again and wipe 'dalvik-cache'. Then reboot
to system. Booting process will take time.

NEW: Now you can enjoy the full version of the recovery! Thanks to @Phil3759 for uploading necessary commits for armv6. And, everything is expected to be bug-free. Please report the bug here if you find any.
GALAXY MINI GOES OFFICIAL NOW!!!!!!
You'll now find Galaxy Mini in the officially supported devices list at the Main thread.
SCREENSHOTS:
Main menu and PhilZ Settings
{
"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"
}
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
27 color settings + 5 alpha transparency levels for every GUI element
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original
cwm image
User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 30mn offset, super wipe option to install a new ROM
Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target
Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root

Hello and thank you for your work but it reboot to recovery again and it says that cant find aroma.zip in path.

alexanderq said:
Hello and thank you for your work but it reboot to recovery again and it says that cant find aroma.zip in path.
Click to expand...
Click to collapse
u hav to rename it to aromafm.zip
and yeah The Rom doesn't boot after installing this recovery

Faiyaz5yaz said:
u hav to rename it to aromafm.zip
and yeah The Rom doesn't boot after installing this recovery
Click to expand...
Click to collapse
You mean, you are always rebooting to recovery and not to your rom?
If so, it is a problem of your device configuration by your device developer because this happens also in Jenkins recovery. This is not a fault of my recovery.
Now, you can restore boot of a backup (if you made any) or you can install your current rom again and wipe dalvik cache and you'll be back normal.

But i have renamed the zip and it does not work.And i tried another ROM but it all ways reboots to recovery.

Can someone else confirm that it always reboot to recovery even after re-installing a rom?

Good work bro.:thumbup:
Sent from my GT-S5570 using xda premium

no
Bhargav97 said:
Can someone else confirm that it always reboot to recovery even after re-installing a rom?
Click to expand...
Click to collapse
I didn't restore back up..
I reflashed my previous cwm..
it booted normally

Bhargav97 said:
Can someone else confirm that it always reboot to recovery even after re-installing a rom?
Click to expand...
Click to collapse
I confirm it. I even flashed another ROM and it still reboots to recovery instead of system.
Aroma FM works, but there is something I noticed: If you tap internal sd or external sd, they are empty, you have to go to storage/sdcard00 to get to your sd card. Can you somehow link the external sd to the sd card?

Thanks everyone for reporting....
I'll try to fix this when I get time...
ast00,
Internal sd and External sd will be empty because they are kept there for devices having two different memories. There should be an option: sdcard directly on the root directory. Please see carefully.

Good news:
My friend @chraso gave me hint about the problem. There was a very small problem with tags, I'll be fixing and making updated recovery today/tomorrow. Will also update recovery sources.

First post updated with newer version, v6.22.1 (18.03.2014) and also made changes so that you can boot into ROM after installing it. Hope it's fixed.
Also added some FAQs.
Please post back the Results after using it.
Please give feedback on swipe-touch. Is right/left swipe working? And please post your opinion on the poll above, whether you like swipe touch or it just makes things complex or you just don't like it.

Bhargav97 said:
First post updated with newer version, v6.22.1 (18.03.2014) and also made changes so that you can boot into ROM after installing it. Hope it's fixed.
Also added some FAQs.
Please post back the Results after using it.
Please give feedback on swipe-touch. Is right/left swipe working? And please post your opinion on the poll above, whether you like swipe touch or it just makes things complex or you just don't like it.
Click to expand...
Click to collapse
flashed the latest zip
still not booting into the same rom..
didn't test new rom

Faiyaz5yaz said:
flashed the latest zip
still not booting into the same rom..
didn't test new rom
Click to expand...
Click to collapse
Which ROM are you installing?
Is the install successful?
What procedure you follow? This is important, please tell me. Do you use 'wipe to install a new rom'?

Does not work for me either, it reboots to recovery and i noticed that to make aroma work i must first install the zip from recovery and then it works OK .

not that
Bhargav97 said:
Which ROM are you installing?
Is the install successful?
What procedure you follow? This is important, please tell me. Do you use 'wipe to install a new rom'?
Click to expand...
Click to collapse
I mean I just changed the recovery didn't touch any roms.. after changing recovery , it keeps bootin to the recovery

Bro,
please read FAQs, this is a problem of your device sources. For solution, see FAQs.
After that, please give me broader report.

You di not ask the right question:
Does this work for someone , anyone please confirm.

[BOOTLOADER][SAFEBOOT] Ouya Bootmenu (mlq)

{
"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"
}
Ouya Bootmenu development/release thread​
This is based on the awesome work by Hal9k.
Because of the fact that the Ouya doesn't have recovery accessibility via hardware buttons we need to play safe and utilise chainbooting.
This bootmenu resides in the kernel partition and is loaded on every normal bootup.
In-depth info in Hal9k's thread here: http://forum.xda-developers.com/showthread.php?t=2499673.
It presents various choices on every boot:
Normal boot - (default) loads bootimage from system partition (/system/boot.img)
Alternate boot - loads bootimage from sdcard (/sdcard/altboot.img)
Recovery - reboots into recovery (recovery partition)
Failsafe - loads built-in failsafe mode
Bootloader - Reboots into stock bootloader (for fastboot access - USE WITH CARE)
Notes about the failsafe
the failsafe mode (which has the bootmenu built-in) will pop up in the following cases:
the bootmenu could not find a valid bootimage (read: /system/boot.img for "normal boot"; /sdcard/altboot.img for "alternate boot")
the user selects "failsafe" from the menu
the failsafe mode resides in the bootmenu image itself and should ONLY be used (as its name suggests) as failsafe.
for regular flashing you need to use a newer cwm version which resides in the recovery partition and is accessible via the "recovery" entry in the bootmenu (see below).
And remember: After flashing this you DON'T NEED TO EVER touch your boot/LNX partition again
Reminder: Failsafe mode is ONLY to be used in case you can't boot into your recovery partition. For regular rom flashing the respective CWM recovery (see below) is required.
Installation
You need to have a newer CWM recovery installed in order to flash the bootmenu.
READ AND UNDERSTAND what you are doing!
This bootmenu is flashed over your current bootimage - newer cyanogenmod builds will place their bootimage to /system/boot.img automatically. if you are not using a custom rom you will need to relocate your bootimage (read: kernel) to /system/boot.img manually.
You need to have a newer CWM recovery installed in order to flash the bootmenu (otherwise you'll get a build.product mismatch while installing).
1a) If you already have an older custom recovery installed:
Boot into recovery and flash https://download.milaq.net/public/android/ouya/misc/recovery-clockwork-6.0.4.8-ouya.zip. This will update your recovery to a newer version allowing you to flash the bootmenu regularly.
1b) If you don't have a custom recovery installed:
You can either use the one-click installer from http://forum.xda-developers.com/showthread.php?t=2295645 and continue with step 1a).
Or you can flash a newer recovery via fastboot (if you know what you are doing): https://download.milaq.net/public/android/ouya/misc/recovery-clockwork-6.0.4.8-ouya.img
2.) Flash the bootmenu via (the new) recovery by installing the latest updatezip (download below). Make sure that the installation procedure was successful.
If you get a "MD5 mismatch" your download is probably broken. Just redownload and try again. The installscript checks the md5's mutliple times while installing and reflashes your old bootimage in case something goes wrong.
So if you are not doing something REALLY stupid this is safe to go.
Download
Download latest version (v2.0.4)
Changelog
Code:
2.0.4
* reduce menu timeout for faster regular boot
* ui improvements in failsafe mode
2.0.3
* bootmenu: increase maximum number of input devices to 5 - e.g. the gpio
keys (the ouya power button - 1 node), a mutlimedia keyboard (2 nodes), a mouse (1 nodes)
and a controller (1 node).
2.0.2
* add in additional alternate boot image folder handling to fix compatibility with kitkat
* update failsafe recovery to differ more from regular recovery
* minor ui and ux tweaks in both bootmenu and failsafe
2.0.1
* initial reworked version
And as always: we take no responsibility whatsoever for raging, screaming, crying, frustration, failing, confusion, dead kittens, etc.
Source
https://github.com/milaq/ouya_bootmenu

Thanks/Credits
Click to expand...
Click to collapse
Hal9k - for the inital ouya bootmenu and many great ideas
Dan Pasanen (invisiblek) - for great work on the recovery and initial porting efforts
Let me know if i omitted you and i will add you here asap
IRC channel
Click to expand...
Click to collapse
Visit us in #cyanogenmod (general) or #cyanogenmod-dev (only dev related talk) on freenode

alright so i installed it, and normal boot boots back into recovery

YoshiFan501 said:
alright so i installed it, and normal boot boots back into recovery
Click to expand...
Click to collapse
This bootmenu is flashed over your current bootimage (you will need to relocate your kernel (to /system/boot.img) if you not using a custom rom)
Click to expand...
Click to collapse
most probably because /system/boot.img is not found. you need to install cyanogenmod afterwards or relocate your bootimage if still on stock.

Is it possible to easily revert the Ouya to a fully stock state after this? Any unninstall method?

Fyi everyone, if you scroll down through the options in cmw a couple times you'll activate rainbow mode! I'm not sure if this is an ouya specific cmw mod or not cuz all my other devices have twrp but anywho ENJOY!
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

Is it possible to use this bootloader with the EternityProject Kernel 3.4.37 for OUYA and the OUYA-Enhanced Rom. I can flash the ROM from within Recovery, but how do I install their kernel for it to boot in ouya bootmenu? I just don't want to brick, thanks for your help!

Just wanted to be the first to tell you that it's working fine and I'm glad to finally give the ouya what it deserves: a custom ROM! Thanks dude!

Can someone post a step by step to move from ep bootlegger to this one?

So can this be dualbooted? If stock ouya boot image is put on /sdcard and named altboot.bin? Right now if I select Alternate Boot, it boots cwm 6.0.3.2. Same as Failsafe.

new version
new version is available in the first post

firmtech said:
So can this be dualbooted? If stock ouya boot image is put on /sdcard and named altboot.bin? Right now if I select Alternate Boot, it boots cwm 6.0.3.2. Same as Failsafe.
Click to expand...
Click to collapse
update the bootmenu to v2.0.2 and rename your alternate bootimage on /sdcard to "altboot.img" and you should be ready to go

milaq thanks for excellent work....
Can you add reboot recovery options in Ouya Failsafe menu to get the full recovery menu?
The power button(for choices) works only if ouya connected-hdmi to hdmi
If Ouya connected hdmi to dvi(Pc monitor) the power button does not respond!
So to go into recovery mode, you can use alt + printScn (SysRq) + i (if keyboard connected)
But now the Ouya goes into a Failsafe menu.

version bump again
krest said:
the power button does not respond!
Click to expand...
Click to collapse
i suspect that you have too many input devices connected during boot.
in version <=2.0.2 the maximum number of input devices that are recognised in the bootmenu was 3.
in case you have a keyboard (usually takes up 2 input nodes) and a mouse connected, the ouya power button (also an input device) was at the end of the list thus not taken into account.
i raised the number of recognised input devices to 5 in version 2.0.3 (see first post for download). that should allow most setups to work fine.
in case you still can't use the power button to select just briefly disconnect your usb devices at boot and reconnect them after making your choice in the bootmenu.

milaq said:
i suspect that you have too many input devices connected during boot.
in version <=2.0.2 the maximum number of input devices that are recognised in the bootmenu was 3.
in case you have a keyboard (usually takes up 2 input nodes) and a mouse connected, the ouya power button (also an input device) was at the end of the list thus not taken into account.
i raised the number of recognised input devices to 5 in version 2.0.3 (see first post for download). that should allow most setups to work fine.
in case you still can't use the power button to select just briefly disconnect your usb devices at boot and reconnect them after making your choice in the bootmenu.
Click to expand...
Click to collapse
Yes, you're right....
Now it's working perfectly
In any case, it would be great if you added the reboot recovery options in Ouya Failsafe menu.
Thanks

Dual Boot
Now that I have CWM with the newest boot menu and CM11 running super smooth how do I go about flashing the stock Ouya ROM to the SD card without wiping the whole thing again? Must restore balance in the household. The natives are demanding to have Amazing Frog back!

bootmenu v2.0.4
new version up.
see first post for details.
KJRob said:
Now that I have CWM with the newest boot menu and CM11 running super smooth how do I go about flashing the stock Ouya ROM to the SD card without wiping the whole thing again?
Click to expand...
Click to collapse
dual booting the stock rom is not as easy as it may seem.
with the boot menu you _have_ the ability to dual boot another boot image (read: kernel/ramdisk) but you still need to have a partition where all stock roms system files reside. the internal "sdcard" is out of the game here as it is just a fused filesystem. but i could imagine external usb storage or such. one needs to partition it and make the respective changes to the stock ramdisk for it to work.
nevertheless, i will not spend time working on stock rom dualboot compatibility. but anyone willing to invest time into it is very welcomed to do so.

milaq said:
new version up.
see first post for details.
dual booting the stock rom is not as easy as it may seem.
with the boot menu you _have_ the ability to dual boot another boot image (read: kernel/ramdisk) but you still need to have a partition where all stock roms system files reside. the internal "sdcard" is out of the game here as it is just a fused filesystem. but i could imagine external usb storage or such. one needs to partition it and make the respective changes to the stock ramdisk for it to work.
nevertheless, i will not spend time working on stock rom dualboot compatibility. but anyone willing to invest time into it is very welcomed to do so.
Click to expand...
Click to collapse
I appreciate the reply. I would love to have the know how to do the work but that is out of my knowledge base. Maybe one day I will. I can wait for the official Ouya store to hit android. The kids will have to wait as well. I love my KK device just the way it is.

milaq said:
dual booting the stock rom is not as easy as it may seem.
with the boot menu you _have_ the ability to dual boot another boot image (read: kernel/ramdisk) but you still need to have a partition where all stock roms system files reside. the internal "sdcard" is out of the game here as it is just a fused filesystem. but i could imagine external usb storage or such. one needs to partition it and make the respective changes to the stock ramdisk for it to work.
nevertheless, i will not spend time working on stock rom dualboot compatibility. but anyone willing to invest time into it is very welcomed to do so.
Click to expand...
Click to collapse
It's doable but once its done both sides of the roms would have significant storage reduction... on another note the method would be completely ( and easily ) reversible to the actual installed rom.
The other route is like you said with usb storage which would probably be the better of the 2 options.
Although with all this said we know that the ouya storefront is coming in the form of an app and I guess the other option would be to "portablize" the current framework ( I did it with 519... could try with the latest one... but I never tried it on anything higher than 4.3 )

How do you revert back to factory settings? Every time I flash stock, it boots to this. Thanks and sorry in advance

[RECOVERY][HOLIDAY] TWRP 2.8.0.0 Touch Recovery [2014-09-19]

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.
Phone look:
{
"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"
}
Tablet look:
CHANGELOG for 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
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
DOWNLOAD:
You can download the image here
XDA:DevDB Information
Team Win Recovery Project, a Recovery for the HTC Vivid
Contributors
WildfireDEV, josegalre
Version Information
Status: Testing
Created 2014-09-27
Last Updated 2014-09-27

Why is status testing? It is stable, right?

Does it work with the Rogers one too or just the At&t Vivid only? I'm confused.

Zeekayy said:
Does it work with the Rogers one too or just the At&t Vivid only? I'm confused.
Click to expand...
Click to collapse
The name of thread says HOLIDAY...it supports every variant!

projektileSAM said:
The name of thread says HOLIDAY...it supports every variant!
Click to expand...
Click to collapse
Thankyou.

3 cheers for WildfireDEV
NEW STUFF
NEW STUFF
NEW STUFF
Thank you

rignfool said:
3 cheers for WildfireDEV
NEW STUFF
NEW STUFF
NEW STUFF
Thank you
Click to expand...
Click to collapse
Thanks guys couldn't have done it without Jose so make sure to give him some thanks as well. The recovery should be working fine. The only problem I see right now is the inability to charge inside of recovery and the battery percentage being continually stuck on 66% or something like that. Could someone please report back and tell me if the recovery is working as I might have uploaded a non working version.

WildfireDEV said:
Thanks guys couldn't have done it without Jose so make sure to give him some thanks as well. The recovery should be working fine. The only problem I see right now is the inability to charge inside of recovery and the battery percentage being continually stuck on 66% or something like that. Could someone please report back and tell me if the recovery is working as I might have uploaded a non working version.
Click to expand...
Click to collapse
I am downloading it now and will install it and get back to you in a couple minutes.
I have installed it successfully and it works so far, just installed the latest nightly with it. And yes the battery percentage is stuck at 66% and does not change but other than that so far i don't see any issues.

slick97477 said:
I am downloading it now and will install it and get back to you in a couple minutes.
I have installed it successfully and it works so far, just installed the latest nightly with it. And yes the battery percentage is stuck at 66% and does not change but other than that so far i don't see any issues.
Click to expand...
Click to collapse
Thanks for that. For all the PAC users I will be making a few edits to the PAC branch of the device tree to correspond with the new recovery. The next nightly that is released I would like you guys to check if it flashes without a hitch.

WildfireDEV said:
Thanks for that. For all the PAC users I will be making a few edits to the PAC branch of the device tree to correspond with the new recovery. The next nightly that is released I would like you guys to check if it flashes without a hitch.
Click to expand...
Click to collapse
We talking the flash zip button in PAC console?
Or the update recovery option in developer options?

rignfool said:
We talking the flash zip button in PAC console?
Or the update recovery option in developer options?
Click to expand...
Click to collapse
No I meant the way you guys normally flash like download from web and flash. Also try the flash zip button see if it works but I really meant the other one. Good suggestion @rignfool

WildfireDEV said:
No I meant the way you guys normally flash like download from web and flash. Also try the flash zip button see if it works but I really meant the other one. Good suggestion @rignfool
Click to expand...
Click to collapse
Another question...
Does this support the 'flash after update' directory?

Thank you WildFire and Jose for keeping the Vivid alive!
I just read about the charging bug, is this going to be updated with a fix or is this the last version for now?

calikevin said:
Thank you WildFire and Jose for keeping the Vivid alive!
I just read about the charging bug, is this going to be updated with a fix or is this the last version for now?
Click to expand...
Click to collapse
Should release a new version with it working when I have time

WildfireDEV said:
Should release a new version with it working when I have time
Click to expand...
Click to collapse
just flashed the latest nightly, flashed good but google now launcher is dead, tried to change in settings and it force closes.

Ok...
I tried to flash the 9/30 nightly... But its borked... However...
When I tried to flash the 9/30 gapps from tkruzze... It failed... Bad updater it said...
Switched to 2.6.3.0... Flashed no problem... Checked md5sum... It passed...
Also... Could not successfully move a file from external_SD to sdcard with the file manager... And it was not a zip... It was no extension...

I had problems flashing gapps with this v2.8 as well, reverted back to 2.6 and the same file worked without a hitch

Please take down the non working recovery...

rignfool said:
Please take down the non working recovery...
Click to expand...
Click to collapse
I will upload a new version for you to check if it works soon