[dlx][CWM Advanced Edition] PhilZ Touch - HTC Droid DNA

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch 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
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
HTC Droid DNA (dlx)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse

Currently running this on my galaxy note and it works great, putting it on my dna now

is this CWm any faster than the ld one as far as backup and such

CM11 installing works?
thanks!!

How did you guys get this installed?
Just through command line or through another method?
Your help is appreciated

jcyoun33 said:
How did you guys get this installed?
Just through command line or through another method?
Your help is appreciated
Click to expand...
Click to collapse
Flash GUI app

Pretty colors and nice interface. Thanks for this. If you use Flash GUI it will ask you to rename it first. I changed it to "recovery.img" and it flashed no problem.

matteebee said:
Pretty colors and nice interface. Thanks for this. If you use Flash GUI it will ask you to rename it first. I changed it to "recovery.img" and it flashed no problem.
Click to expand...
Click to collapse
is it any faster than the older one ?

About the same as far as backups. I put .hideandroidprogress in clockworkmod folder and my 2.2 gb backup took about 4 mins. Appears to be packed with features I don't know how to use yet but will be quite handy to have.

Can you restore twrp backups or do you need to create new ones?

xlxcrossing said:
Can you restore twrp backups or do you need to create new ones?
Click to expand...
Click to collapse
I was able to restore a TWRP backup when I switched the settings to TWRP mode.

Glad to see this finally making its way to the DNA. Will flash it later today. :sly:
Tapatalked from my HTC Droid DNA

matteebee said:
About the same as far as backups. I put .hideandroidprogress in clockworkmod folder and my 2.2 gb backup took about 4 mins. Appears to be packed with features I don't know how to use yet but will be quite handy to have.
Click to expand...
Click to collapse
Can you link to how to add this mod? Thank you in advance.

nice looking UI, but I can't seem to do adb push blah.zip /sdcard/
not sure why though, because i tried it earlier before i wipe my phone and it worked to seem a small file, but does not work with a larger file size?
I tried it in the twrp beta and it works perfectly fine

this is by far my favorite recovery in all the years ive been a flashaholic.

-DroidIsDNA- said:
Flash GUI app
Click to expand...
Click to collapse
Thanks! Such a dope app!

CM Updater
For those of you that get hasty and install things without reading the FAQ.
Phil3759 said:
CMUpdater cannot flash downloaded files
If you get a /sdcard/0 error, it means you have /sdcard set as /data/media/0 in recovery
The reason is that CM app doesn't support /data/media/0 and is faking recovery with a /sdcard/0 implementation
You still can alter the setting and force it to /data/media in Advanced menu. This will give full compatibility with cwm, CM roms and CM Updater
Click to expand...
Click to collapse
Learn from my mistakes. Also the rude response I got in the 3 minutes before I edited my post in the Philz Recovery thread was the reason people hate this website.

Does this recovery not show up in adb when connected to the PC via USB?

rayjr13 said:
Does this recovery not show up in adb when connected to the PC via USB?
Click to expand...
Click to collapse
ADB works fine for me, make sure you have set the USB connection to Media Device (MTP) under the Menu in Storage

chooven said:
ADB works fine for me, make sure you have set the USB connection to Media Device (MTP) under the Menu in Storage
Click to expand...
Click to collapse
The phone list in adb devices when booted to the rom but in recovery I don't get any connection to it via adb.
MTP works well I used adb to move my backups when booted to the rom but in recovery I could not use adb or adb shell to tinker.
Gonna try the SDK manager to see if I'm out of date or something.

Related

[RECOVERY][ENCORE] TWRP 2.3.1.0 with on-screen keyboard! [2012-10-15]

Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.3.1.0:
-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
CHANGELOG for 2.3.0.0:
-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)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app
For downloads and instructions please visit our TWRP website and choose your device in the dropdown menu
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
ReverendJKR posted a great video on TWRP and Goo Manager working together.. Much more to come with this relationship
http://youtu.be/OA0S275XO3U
Oh man. Awesome!
Looks nice...looking forward to trying it out.
This looks very slick!
Sent from space
Can this recovery be used on any phone/tablet?
Sent from my Desire HD using xda premium
Super cool, thanks guys, I am now into Nook Color... HD2, AMAZE 4G...
Jainyankee1993 said:
Can this recovery be used on any phone/tablet?
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
We have a list of supported devices on the main twrp2 page: http://teamw.in/project/twrp2
So I see you got that stuck in recovery bug all worked out ehh? nice work.
eyeballer said:
TeamWin is proud to present TWRP 2.0 for Nook Color!!
Click to expand...
Click to collapse
Congrats TeamWin... this is supercool.
eyeballer one of the install steps is to push "kernel" to uRecImg but there is none? Am I missing something obvious?
hm, anyway to install this on an existing install?
Midnitte said:
hm, anyway to install this on an existing install?
Click to expand...
Click to collapse
Right from their page? Though idk what kernel they are talking about.
Download the above file. Connect your Nook Color to the PC via the USB cable. This assumes you have working ADB.
Execute the following:
adb shell busybox remount / -o rw,remount
adb shell busbbox mkdir /boot
adb shell busybox mount /dev/block/mmcblk0p1 /boot
adb push twrp-encore-2.0.0RC0.ub /boot/uRecRam <--- You can change uRecRam to uAltRam for alternate boot.
adb push kernel /boot/uRecImg
adb shell busybox umount /boot
Click to expand...
Click to collapse
RileyGrant said:
eyeballer one of the install steps is to push "kernel" to uRecImg but there is none? Am I missing something obvious?
Click to expand...
Click to collapse
Nburnes said:
Right from their page? Though idk what kernel they are talking about.
Click to expand...
Click to collapse
Sorry guys, the page is updated now with the kernel link. However, we just use a stock AOSP kernel so if you had CWM on emmc already you don't need to push the kernel since it's the same.
eyeballer said:
Sorry guys, the page is updated now with the kernel link. However, we just use a stock AOSP kernel so if you had CWM on emmc already you don't need to push the kernel since it's the same.
Click to expand...
Click to collapse
Actually what I thought, thanks for clarifying man .
Oooh, i look forward to trying this.
I was not having success installing this on emmc with the adb instructions probably because busybox was not set up the same way.
So I tried an different approach which was to use the NookColor UMS app to mount the boot partition so it shows up as a USB drive on PC called boot. I then just renamed uRecRam to uRecRamOld and copied in twrp-encore-2.0.0RC0.ub and renamed that to uRecRam. I didn't bother copying the kernel as per the previous posts.
Rebooting into recovery then brought up the TWRP recovery which looks very nice to use. Also works off the power up N after emmc recovery selected as expected.
Clockwork has given me good service but I think I'll be using this going forward.
bobtidey said:
I was not having success installing this on emmc with the adb instructions probably because busybox was not set up the same way.
So I tried an different approach which was to use the NookColor UMS app to mount the boot partition so it shows up as a USB drive on PC called boot. I then just renamed uRecRam to uRecRamOld and copied in twrp-encore-2.0.0RC0.ub and renamed that to uRecRam. I didn't bother copying the kernel as per the previous posts.
Rebooting into recovery then brought up the TWRP recovery which looks very nice to use. Also works off the power up N after emmc recovery selected as expected.
Clockwork has given me good service but I think I'll be using this going forward.
Click to expand...
Click to collapse
I had to do the same thing. Kept getting an error that "applet not found" for busybox in adb.
Thanks for the alternate method.
This is a much better implementation of our hardware in backup.
Thanks TeamWin.
Nburnes said:
Right from their page? Though idk what kernel they are talking about.
Click to expand...
Click to collapse
It wasn't there before! I swear! /thanks
Hm, is usb storage working for anyone?
The only thing I don't really care for is... and I know I am doing things in a unique way....
I have SASD with CM7 on it... verygreen's recovery as alt-boot and replaced CWM with TWRP as recovery mode on the uSD... when in TWRP and reboot... it boots stock on eMMC instead of a normal boot... it should do a normal boot (uSD first)

[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Dees_Troy said:
[RECOVERY] TeamWin Recovery Project (twrp) 2.0.0RC0 [2011-12-17]
Team Win Recovery Project 2.0, or twrp2 for short, is a custom recovery built with ease of use and customization in mind.
Special thanks to xboarder56 for helping test the port and a couple of other testers that I forget the names of at the moment.
Click to expand...
Click to collapse
NICE, thanks to the both of you! Goin' on tonight fo sho.
Very nice job guys! I just might have to update my signature now.
Is there any future in external sdcard support?
Looks good I guess I'll have to update from the old version, thanks.
Awesome work guys.... this kicks total butt!
Nice! It's come a long way since I used it on my 3D. Alot faster compressed backup, thanks
Sent from my HTC Amaze 4G using xda premium
Has anyone had luck installing this on amaze????
Sent from my HTC Amaze 4G using xda premium
milo356 said:
Has anyone had luck installing this on amaze????
Sent from my HTC Amaze 4G using xda premium
Click to expand...
Click to collapse
I have. I can do it in different ways. flash_image recovery recoveryname.img command from the phone itself if you have the flash_image binary installed or by fastboot flash recovery recoveryname.img with the phone in bootloader mode.
Not complicated at all.
Works great, so much better than using the volume up/down keys and power keys. Two weird things that I want to see if anyone else is having issues with (want to know if it is worth reporting on the github)
1. After accessing recovery I get the "Tell HTC" This phone has just recovered from a abnormal reset message. Didn't get that with clockwork, not sure if it is a bug or not.
2. Cant mount ext SD card. Saw that the EVO 3D had the same issue but they had fixed it. I assume this is a problem with the Amaze since it is the same with clockwork mod?
Sikety said:
Works great, so much better than using the volume up/down keys and power keys. Two weird things that I want to see if anyone else is having issues with (want to know if it is worth reporting on the github)
1. After accessing recovery I get the "Tell HTC" This phone has just recovered from a abnormal reset message. Didn't get that with clockwork, not sure if it is a bug or not.
2. Cant mount ext SD card. Saw that the EVO 3D had the same issue but they had fixed it. I assume this is a problem with the Amaze since it is the same with clockwork mod?
Click to expand...
Click to collapse
Use this one if you want to backup and restore to and from external sdcard.
pardon the question, I've looked all over TeamWin's web site... Is there a way to boot the Amaze into twerp directly?
gregma said:
pardon the question, I've looked all over TeamWin's web site... Is there a way to boot the Amaze into twerp directly?
Click to expand...
Click to collapse
I don't understand your question.
You want to reboot into recovery?
adb reboot recovery
or use the 22 different other ways to reboot into recovery.
Binary100100 said:
I don't understand your question.
You want to reboot into recovery?
adb reboot recovery
or use the 22 different other ways to reboot into recovery.
Click to expand...
Click to collapse
I'm talking about rebooting into recovery when I'm not anywhere near a computer. Such as on my HD2, I would hold the power button down until in MAGLDR, then choose to boot into Recovery. Is there something similar on the Amaze?
Greg
gregma said:
I'm talking about rebooting into recovery when I'm not anywhere near a computer. Such as on my HD2, I would hold the power button down until in MAGLDR, then choose to boot into Recovery. Is there something similar on the Amaze?
Greg
Click to expand...
Click to collapse
Which rom are you using?
There are a couple of roms that have the Advanced Power Menu that has a reboot option. When selected it gives you other options such as recovery and bootloader.
There are also a few apps (do a search for Reboot Recovery) on the Market.
I have always used the option from ROM Manager.
You can also use terminal emulator and use the command "reboot recovery" and that should do it too.
You can also power off the device, hold volume down while pressing power to get to hboot mode then select recovery.
Binary100100 said:
Which rom are you using?
There are a couple of roms that have the Advanced Power Menu that has a reboot option. When selected it gives you other options such as recovery and bootloader.
There are also a few apps (do a search for Reboot Recovery) on the Market.
I have always used the option from ROM Manager.
You can also use terminal emulator and use the command "reboot recovery" and that should do it too.
You can also power off the device, hold volume down while pressing power to get to hboot mode then select recovery.
Click to expand...
Click to collapse
Stock ROM right now, I'm getting things set to start flashing new ROM's. Aha! I did see the "recovery" in hboot. Now once I figure out how I lost the ability to get into hboot by holding the volume down button I'll be good to go!
Greg
---------- Post added at 01:55 PM ---------- Previous post was at 01:22 PM ----------
gregma said:
Stock ROM right now, I'm getting things set to start flashing new ROM's. Aha! I did see the "recovery" in hboot. Now once I figure out how I lost the ability to get into hboot by holding the volume down button I'll be good to go!
Greg
Click to expand...
Click to collapse
I LOVE answering my own darned post.... Didn't realize you had to battery power cycle the device to get it back into hboot. I'm good to go now!
Greg
ok i got it loaded up fine on my phone but i cannot figure out how to flash. i click the install button and it takes me to my directories but i dont see any files in the directories... there is no files listed in the root of either sd card as well. what am i doing wrong?
2sh0rt said:
ok i got it loaded up fine on my phone but i cannot figure out how to flash. i click the install button and it takes me to my directories but i dont see any files in the directories... there is no files listed in the root of either sd card as well. what am i doing wrong?
Click to expand...
Click to collapse
Move the zip file to the other sdcard. Remember that you have two.
Here's a free tip!
Make two empty zip files.
Name one internal.zip
Name the other external.zip
Place the internal.zip in the internal sdcard and the external.zip in the external sdcard.
Reboot into recovery and if you see internal.zip file. Guess what sdcard you're looking at? Same goes for external.
Binary100100 said:
Move the zip file to the other sdcard. Remember that you have two.
Here's a free tip!
Make two empty zip files.
Name one internal.zip
Name the other external.zip
Place the internal.zip in the internal sdcard and the external.zip in the external sdcard.
Reboot into recovery and if you see internal.zip file. Guess what sdcard you're looking at? Same goes for external.
Click to expand...
Click to collapse
Dude, i know this... i came from the vibrant. Im saying that NEITHER card shows ANY files... only directories... no zips on the root of /sdcard or /sdcard/ext-sd... nada, zip, zilch
2sh0rt said:
Dude, i know this... i came from the vibrant. Im saying that NEITHER card shows ANY files... only directories... no zips on the root of /sdcard or /sdcard/ext-sd... nada, zip, zilch
Click to expand...
Click to collapse
I came from the vibrant as well however I wasn't so active there.
I don't understand why you don't see any zip files then. Strange.
Me either... think i'll just try and reload it and see what happens. Thought maybe i was clicking the wrong thing or not clicking something.
---------- Post added at 07:47 PM ---------- Previous post was at 07:43 PM ----------
and its not just that i dont see any zip files. i dont see ANY files at all! every directory i click is empty! even on the system partition! not a single file shows up. only directories and when i click them there is nothing except /.. and /.

[Recovery] TWRP Official Builds

Team Win Recovery Project 2.6, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. TeamWin started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of additional 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.
HTC Droid Incredible 4G LTE product page on TeamW.in
Older versions can be found here if needed.
Download
Download TWRP 2.6.3.0 Official (Change Log)
MD5: 22c58a87402b4049f8bafa1b07b1a765
Download TWRP 2.6.3.0a Unofficial
MD5: fd9f7b520bec55c980d0ea39616aa271
Includes these commits on top of 2.6.3.0: Never generate empty backup name, Remove unneeded images, check for space after = too, Improvements to Update_Log_File, Fix checking for file_contexts in updater
GooManager Installation:
Automated installation through GooManager will only work if you have the su binary (root access) on your ROM. If you have just performed unlock or S-OFF, you must use the manual installation method for the first recovery installation.
Install the GooManager application from Google Play
Open GooManager, pull up the menu, and select Install OpenRecoveryScript
Confirm the first prompt, then verify the filename in the second prompt (openrecovery-twrp-2.6.3.0-fireball.img) and confirm again
After the recovery has been installed, pull up the menu and choose Reboot Recovery
Manual Installation:
Requirements: you must have fastboot set up: Windows Guide, Mac Guide, Ubuntu Guide
1) Reboot your phone to the bootloader:
Method 1: Disable fast boot under Settings > Power > Fast boot. Shut down the phone. Hold Volume-Down and Power simultaneously until the phone vibrates. Continue holding volume down, but release the power button. When you reach the bootloader, choose the FASTBOOT menu option using the volume keys to move up/down and the power key to select.
Method 2: If you have adb installed, then with your phone fully booted up, type: adb reboot-bootloader
2) Flash the recovery image using fastboot. Open a terminal and navigate to the directory with the downloaded image. Type:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-fireball.img
When the image has finished flashing (usually less than 10 seconds), issue the command
Code:
fastboot reboot-bootloader
3) Use the volume keys to navigate to BOOTLOADER and then select it with the power key. After the phone finishes scanning for PJ____.zip images, choose RECOVERY from the menu. This will start TWRP recovery.
Themes:
TWRP supports themes! Create a folder called theme within the TWRP folder on your internal storage and copy ui.zip into it. You can either search for themes compatible with the 540x960 resolution (check out the EVO 3D forum for instance) or build your own. Known themes listed below:
Holo TWRP Theme by prairiedogn
HTC TWRP Theme by prairiedogn
Blue Dalek Theme by agentc13
Sports Recovery Themes by lnando84
Gray Theme by lnando84
Themes written for earlier versions of TWRP may not have themed elements for new features. Be sure to compare the user interface before and after applying a theme to make sure everything shows up. You can check the log for errors as well (the middle button on the bottom of the TWRP interface), it will say something like: "unable to load button image" if resources are missing.
Additional Information:
The boot image comes from RUU 2.17.605.2
This build includes HTC Dumlock in case it is needed. S-OFF users can safely ignore it. HTCDev Unlock users (who are still S-ON) can try it out if experiencing trouble writing to the /boot partition. It can be found under Advanced in the recovery.
Credits:
Dees_Troy for adding the Inc 4G to TeamWin's officially supported devices for TWRP
con247 for putting in the original effort to build TWRP on the Inc 4G
utkanos and KemoNine for building assistance
TeamWin for TWRP and their great building guide
CyanogenMod for way too many reasons
Release History:
Official 2.6 - In addition to TWRP's official changes, this version also introduces support for AOSP data encryption. Additionally, Aroma installers should not fail anymore.
Official 2.4 - Builds are now maintained by TeamWin: Change Log
Official 2.3.3.0 - Identical to Build 1.2
Build 1.2 - Mount internal and external SD to computer via USB
Beta 1.1 - HTC Dumlock included
Beta 1.0 - Initial Release
Known issues / Workarounds / To Do
The charging status LED currently does not turn on when the phone is charging. This is really a non-issue since there is a charge level and charging indicator within the recovery.
If the phone is powered off while plugged into USB, it will temporarily reboot into recovery then shut down 20-30sec later.
Source
The device tree is at github.com/cyanogenmod/android_device_htc_fireball.
great, glad to see this coming
Do you think this could get goo manager support? Thanks for all that you do.
Sent from my DROID RAZR using Tapatalk 2
Awesome! Thanks updating now
jamminjon82 said:
Do you think this could get goo manager support? Thanks for all that you do.
Click to expand...
Click to collapse
I need successful user reports for all the features. Once I get confirmation that everything works as expected, I'll submit my device tree to TWRP and ask for official builds. Goo manager support would follow from there.
I updated the build to version 1.1. For those who are S-OFF, there's no difference from 1.0. For those who are S-ON and using HTCDev Unlock (from team fireballas), there's now HTC Dumlock included. I'm still not sure if it is even needed...
im running a backup now. i'll try wiping and restoring too
---------- Post added at 02:18 PM ---------- Previous post was at 01:37 PM ----------
Backup, wipe, and restore all work as well as backup compression and backup rename. Under wipe I didn't know about internal and android secure are those required for a full wipe?
Linch89 said:
im running a backup now. i'll try wiping and restoring too
---------- Post added at 02:18 PM ---------- Previous post was at 01:37 PM ----------
Backup, wipe, and restore all work as well as backup compression and backup rename. Under wipe I didn't know about internal and android secure are those required for a full wipe?
Click to expand...
Click to collapse
Relevant posts about androidsecure:
http://forum.xda-developers.com/showthread.php?t=1934739
http://forum.xda-developers.com/showpost.php?p=27172605&postcount=218
Internal wipe clears out your internal sdcard's media partition (pictures, music)... probably don't want to do that.
Good look glad I didn't. Well as far as I can tell this is recovery is a win pun intended
im trying to mount my phone to my computer while in recovery and its not working v2.3.3.0 idk if its my computers usb its certainly not my phones micro usb the thing is brand new
The ability to mount the phone's sdcards on the computer while in TWRP was unknown to me. I'm working on the issue. The attached recovery is a first stab at a fix, let me know if it works (my faith is low though since the devices didn't mount in ubuntu for me).
MD5: 6fa24210afa860c38fef3f2a7d4360d1
Edit: the attached recovery did not fix the issue. I'll try to look into this sometime this week (research presentations and job interviews over the next few weeks so time is very scarce right now).
Linch89 said:
im trying to mount my phone to my computer while in recovery and its not working v2.3.3.0 idk if its my computers usb its certainly not my phones micro usb the thing is brand new
Click to expand...
Click to collapse
Mine isn't mounting either, internal nor external card, but I can get it to work through ADB, (work around for the time being)
Interesting side note though, (and this may be expected by some, it was new to me) while in TWRP recovery and running shell though ADB it was listing my actual external SD card as "sdcard" and actual internal SD as "internal_sdcard". I have used CWM on another device and I don't remember it changing the file structure while in recovery. Also I had shell root upon issuing the adb shell command. This is my first device using TWRP, it was just different.
Edit: Never Mind, I am running TWRP v2.2.0, this may not have any validity with the OP's version, sorry.
Edit my Edit: OK I just flashed v2.3.3.0 and same goes, I can get in through ADB and I have shell root once in shell. However, the file system looks like it should with "sdcard" and internal and "external-sd" as external. All else seems normal.
DavDoc said:
Mine isn't mounting either, internal nor external card, but I can get it to work through ADB, (work around for the time being)
Click to expand...
Click to collapse
I worked on the sd card mounting issue last night, but still have not figured it out. I will try to get some assistance from the TWRP folks if I find time tonight. Just to make sure, the feature worked when you used TWRP 2.2 by con247?
In fact, I may be misinterpreting how the feature works. Is the computer supposed to auto-mount your SD card when plugged in via USB, or do you have to activate the feature from within TWRP somewhere?
DavDoc said:
Interesting side note though, (and this may be expected by some, it was new to me) while in TWRP recovery and running shell though ADB it was listing my actual external SD card as "sdcard" and actual internal SD as "internal_sdcard". I have used CWM on another device and I don't remember it changing the file structure while in recovery. Also I had shell root upon issuing the adb shell command. This is my first device using TWRP, it was just different.
Click to expand...
Click to collapse
I just tested and this is what I see:
Code:
drwxrwxrwx 11 root root 16384 Jan 1 1970 external_sd
drwxrwxrwx 11 root root 32768 Jan 1 1970 sdcard
EDIT: Both in TWRP and in 'adb shell' the locations are correct.
It doesn't auto mount upon connecting usb, I didn't try mounting it though, through TWRP settings. From what I can tell, both versions work the same, they just have different names for the file structure, and only for the external and internal sdcards - didn't really investigate any other files.
Edit: To answer your first question, no it didn't work in either version. Don't know who's v2.2.0 it is, but it is the recovery that was added into the supercid.auto script.
mdmower said:
I worked on the sd card mounting issue last night, but still have not figured it out. I will try to get some assistance from the TWRP folks if I find time tonight. Just to make sure, the feature worked when you used TWRP 2.2 by con247?
In fact, I may be misinterpreting how the feature works. Is the computer supposed to auto-mount your SD card when plugged in via USB, or do you have to activate the feature from within TWRP somewhere?
I just tested and this is what I see:
Code:
drwxrwxrwx 11 root root 16384 Jan 1 1970 external_sd
drwxrwxrwx 11 root root 32768 Jan 1 1970 sdcard
EDIT: Both in TWRP and in 'adb shell' the locations are correct.
Click to expand...
Click to collapse
i think they mean usb mounting is gone it is suposed to be under mount option
jose51197 said:
i think they mean usb mounting is gone it is suposed to be under mount option
Click to expand...
Click to collapse
Right, so if I just understood this a couple of days ago I could have had a fix pretty quick. I naively thought the phone was supposed to auto-mount to the computer, which would make no sense because the drives would then be inaccessible to TWRP's routines. Anyways, build 1.2 enables the feature and both internal and external SD cards can be accessed.
mdmower said:
Right, so if I just understood this a couple of days ago I could have had a fix pretty quick. I naively thought the phone was supposed to auto-mount to the computer, which would make no sense because the drives would then be inaccessible to TWRP's routines. Anyways, build 1.2 enables the feature and both internal and external SD cards can be accessed.
Click to expand...
Click to collapse
Its back thanks I wish I can thank you twice and don't want to complain but only thing missing is the backup android.secure option under backup
Sent from my ADR6410LVW using xda app-developers app
jose51197 said:
Its back thanks I wish I can thank you twice and don't want to complain but only thing missing is the backup android.secure option under backup
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
Does your .android_secure folder actually have anything in it? Mine is empty on Viper 2.1.1. I just moved an app to SD and the folder is still empty. The reason I ask is because the and-sec folder is correctly mounted and linked to /sdcard/.android_secure when in TWRP.
I've never seen anything in android secure ever on any phone
Linch89 said:
I've never seen anything in android secure ever on any phone
Click to expand...
Click to collapse
On my OG DInc running AOSP that folder would indeed store sdcard apps... strange its different now....
I moved all apps my apps to sd card and I checked android_secure under sdcard and sdcard2 in root explorer and nothings in there. I can't delete the folder though so it must be of some importance

Ubuntu Touch (Latest)

Hello everyone,
I've managed to make a build that boots with the latest versions of ubuntu touch and I wanted to share it with you because I've also been following this thread eager to install ubuntu touch on my phone, although the method to install still might be complicated for some at the moment.
So first off you need to be using Linux, as I don't think project rootstock works on Windows
To install it you must follow the instructions I found here which are, in a terminal:
sudo apt-get install android-tools-fsutils qemu-user-static bzr
android-tools-adb
bzr branch lproject-rootstock-ng
cd project-rootstock-ng
Click to expand...
Click to collapse
then to get the rootfs with the mir fixes
./rootstock-touch -p pps:rsalveti/ppa
Click to expand...
Click to collapse
which takes a little while or you can download the tar.gz from here
but once the screen turns off it takes a while or a reboot to get it back on
Once that part is finished download all the files at the end of the post and put them in the project-roostock-ng directory to make things easier
then in the same terminal with your device connected to bootloader:
sudo fastboot flash boot ./boot.img
sudo fastboot flash recovery ./recovery.img
Click to expand...
Click to collapse
Reboot your device to recovery and do a full wipe, once that's done, with your device still connected to usb, in the same terminal type:
./rootsotck-touch-installer ./out-XXXXXXXX/ubuntu-touch.rootfs-armhf.tar.gz ./system.img
Click to expand...
Click to collapse
your device should reboot on its own, once you get to the black screen type:
adb shell
mount /dev/loop0 -o remount,rw
exit
adb push 70-m7ul.rules /usr/lib/lxc-android-config
adb push m7ul.conf /etc/ubuntu-touch-session.d
adb reboot
Click to expand...
Click to collapse
and your device should load the ubuntu lockscreen
Here are the files for m7ul:
system.img
boot.img
recovery.img
70-m7ul.rules
m7ul.conf
for m7spr (not tested):
boot.img
recovery.img
system.img
and download the 70-m7ul.rules and m7ul.conf but replace m7ul with m7spr
What works:
UI
camera
auto-rotation
Wifi (tested only on at&t version)
Audio (I've managed to get audio to work if the headphones are plugged in but not all the way, you really gotta find the sweet spot so it's not really useable yet but it's still progress.)
What doesn't work:
GSM
etc
it should run more smooth and the phone should get less hot
Backup file - http://www.mediafire.com/download/2xnfez828442k3l/2014-06-17--17-26-37.zip
I also found a way to have the same kind of dual boot setup canonical made for the nexus 4 by flashing the boot.img (the newer one can be found here http://www.mediafire.com/download/i9kmmwvc3gmb0kb/boot.img) on the recovery partition and keeping the internal rom's boot on the boot partition, so in theory if you flash a rom without wiping after flashing the backup and you flash the boot.img I provided on the recovery partition it should also work and then to get ubuntu you reboot in recovery and to get android you just boot normally, the problem is you lose your recovery temporarily and you have to reflash it if you want to use it until canonical finds a different way or I manage to get it to work with multirom.
delete
Sent from my HTC One_M8 using Tapatalk
ModestMouse1312 said:
He told me to post this here?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
could you please upload the backup of your rom so that we can install. I don't have linux installed on my laptop.
Great JOB! Thank You very much lots of people are waiting for working ubuntu touch rom and this is another big step forward!
https://www.dropbox.com/s/zz6xlm30ffskcol/2014-06-12--03-27-15.zip here is the twrp backup. just unzip it
ModestMouse1312 said:
https://www.dropbox.com/s/zz6xlm30ffskcol/2014-06-12--03-27-15.zip here is the twrp backup. just unzip it
Click to expand...
Click to collapse
may be you should update OP but wifi actually works
saketh91 said:
may be you should update OP but wifi actually works
Click to expand...
Click to collapse
wifi works? not for me? i have at&t
ModestMouse1312 said:
wifi works? not for me? i have at&t
Click to expand...
Click to collapse
i have at&t too and it works pretty well for me. I was playing with some settings and suddenly wifi networks popped up and got connected. I then tested if the internet is working by using both facebook and browser. It is working pretty fine for me. Will post screenshots if needed
saketh91 said:
i have at&t too and it works pretty well for me. I was playing with some settings and suddenly wifi networks popped up and got connected. I then tested if the internet is working by using both facebook and browser. It is working pretty fine for me. Will post screenshots if needed
Click to expand...
Click to collapse
my backup wont show up in twrp? any help? lol (nevermind didnt copy to the right place xD)
ModestMouse1312 said:
my backup wont show up in twrp? any help? lol
Click to expand...
Click to collapse
backup should be something like this.
/TWRP/BACKUPS/HT34CW900897/2014-06-12--03-27-15.
what I mean by this is that the backup folder should be in sub folder of backups not in backups itself. I already had a backup of my android rom and now I pasted your backup folder in HT34CW900897 folder not in BACKUPS
saketh91 said:
backup should be something like this.
/TWRP/BACKUPS/HT34CW900897/2014-06-12--03-27-15.
what I mean by this is that the backup folder should be in sub folder of backups not in backups itself. I already had a backup of my android rom and now I pasted your backup folder in HT34CW900897 folder not in BACKUPS
Click to expand...
Click to collapse
what did you do to get wifi working?
ModestMouse1312 said:
what did you do to get wifi working?
Click to expand...
Click to collapse
Is it still not working for you? Trust me I did not touch anything. I just restored ur backup file and it worked. If you still dont believe i can post screenshots for you. Btw i am using the oldest firmware. Hboot 1.43. Just for your info(if that really matters)
saketh91 said:
Is it still not working for you? Trust me I did not touch anything. I just restored ur backup file and it worked. If you still dont believe i can post screenshots for you. Btw i am using the oldest firmware. Hboot 1.43. Just for your info(if that really matters)
Click to expand...
Click to collapse
ah, it finally started working after about 30 minutes.
ModestMouse1312 said:
ah, it finally started working after about 30 minutes.
Click to expand...
Click to collapse
finally it worked. now getting gsm and audio working would be a great achievement. I am learning things now and if I am of anyway useful to this project I would gladly contribute.
saketh91 said:
finally it worked. now getting gsm and audio working would be a great achievement. I am learning things now and if I am of anyway useful to this project I would gladly contribute.
Click to expand...
Click to collapse
go for it man, if you can develop it first just take over
ModestMouse1312 said:
go for it man, if you can develop it first just take over
Click to expand...
Click to collapse
when I try to execute this command "./rootstock-touch -p pps:rsalveti/ppa" I get this error. please help me with this
saketh91 said:
when I try to execute this command "./rootstock-touch -p pps:rsalveti/ppa" I get this error. please help me with this
Click to expand...
Click to collapse
you need to install the debootstrap utility , I guess a sudo apt-get install debootstrap will do it
cuyo11 said:
you need to install the debootstrap utility , I guess a sudo apt-get install debootstrap will do it
Click to expand...
Click to collapse
thank you that worked like a charm. I should have double checked the dependencies installed
Error 509 on link, can someone please mirror it?

[recovery][port][(un-)official][kinzie] twrp 3.2.1-0

After a long time of trying to get things right, i finally got things right.
So here it is:
TWRP RECOVERY 3.2.1-0 FOR THE MOTO X FORCE (KINZIE)
This is an actual port and not a recompile of a different version for another device.
It is not yet official but i intend to submit my device tree, so it gets official.
It is probably never going to be official, but i'll try and provide frequent updates.
Everything *should* work, as far as i was able to test.
I am not sure about encryption though, as i have not encrypted my device, nor do i intend to do so atm.
Encryption should be ok now. (TWRP team has put a lot of effort in this).
Encrypted partitions cannot be read atm.
This would probably also work for the Droid 2 Turbo, if someone finds a way to unlock the BL.
I will try to maintain TWRP for this device, fixes may take a while though as i am not having a lot of time to work on this.
Installation:
1. Unlock your device
2. Download the image
3. Power off the phone
4. Boot to fastboot (VOL DN + POWER)
5. plug your usb cable install via fastboot:
Code:
fastboot flash recovery TWRP_3.2.1-0_Kinzie.img
If you want to keep OTA Update ability you can also temporary boot to TWRP. You would have to repeat this step everytime you want to go to TWRP then:
Code:
fastboot boot TWRP_3.2.1-0_Kinzie.img
Download here:
Version 3.2.1-0
http://www.mediafire.com/file/o6gcj4hhjahf936/TWRP_3.2.1-0_Kinzie.img
Version 3.1.1-0
http://www.mediafire.com/file/y2k08c6m5tazhbo/TWRP_3.1.1-0_Kinzie.img
Version 3.1.0-0
https://www.mediafire.com/?7h4u37ddiohwy45
Credits go out to the people of Teamwin Recovery project for creating this nice piece of software!
And credits go to @Arasthel, who is a great dev!
Official Changelog 3.2.1-0
Fixes for kinzie:
- USB OTG now working
- TWRP internal folder should be now accessible via /sdcard symlink
- cm updater is reporting device correctly now as kinzie
Amazing, the most beautiful and wanted TWRP version! Tested and working perfectly! Using it as my recovery, not boot only.
Enviado de meu XT1580 usando Tapatalk
Awesome! It's cool to have an actual port and to know that you will try to maintain it so we can have future updates .
I'm curious, though. What is the difference between this and clark recovery? Did you build it with the latest motorola kernel, which includes msm8994 support or make some BoardConfig changes? I mean, they share the same config and base kernel, at least, the basics that make TWRP work - wifi and other modules are a whole different story, but they are not needed for recovery.
Arasthel said:
Awesome! It's cool to have an actual port and to know that you will try to maintain it so we can have future updates .
I'm curious, though. What is the difference between this and clark recovery? Did you build it with the latest motorola kernel, which includes msm8994 support or make some BoardConfig changes? I mean, they share the same config and base kernel, at least, the basics that make TWRP work - wifi and other modules are a whole different story, but they are not needed for recovery.
Click to expand...
Click to collapse
To be honest, differences are marginal at this point, as of now we've got the fstabs by-name assignments there is almost no way of messing things up with partition assignments (which is kinda the no. 1 thing to do right in recovery). At the moment i am still using a prebuilt kernel and ramdisk i extracted from the device, because when i started building the device tree the kernel sources haven't been available. And when they finally were i decided to first fix the issues i already had, before introducing new ones. The whole graphics sub routines of TWRP (minuitwrp) recently had undergone a pretty big overhaul and so we've lost ability to flip screen on the way. I recently made a patch to fix this for overlay devices (which the kinzie is), and since then, TWRP is running fine on the native kinzie build. The overhaul also made the use of a custom graphics.c obsolete. (I suspect you had to use that?) I made the device tree mostly from scratch, only looking at similiarities at trees from hima and clark. (Hima has msm8994 too, clark has a different chipset as you know, but is a moto device).
You can have a look at it here. Please note that this is not absolute latest configuration (haven't uploaded it yet) and it still needs a little cleanup before submission. After that, i am going to throw in kernel sources from motorola and fetch the prebuilts necessary.
If you are interested in learning more you can contact me via PM.
Just flashed and working 100%. Moto X force BR version.
Thx a lot dude :good: just flashed and working.
no more upside/down issue :silly:
and nice theme btw
Thanks a lot mate! working as expected.
Perfect and beauty one! Thanks!
Xadro, just to let you know that the OTG is not working yet. Tried several things but no good yet. If you need some one to test some workarounds just let me know.
marzliak said:
Xadro, just to let you know that the OTG is not working yet. Tried several things but no good yet. If you need some one to test some workarounds just let me know.
Click to expand...
Click to collapse
I'll look into it as soon as I can. Might also be a general issue in twrp.
Thanks for this @Xadro . I just received my Moto X Force yesterday, it's great to see this available.
One thing I noticed is that the /sdcard/TWRP folder doesn't seem to be accessible (tried ES File Ex and Android terminal). Android Terminal displayed 'do not have permission' ls -al showed normal perms for the directory
fubofo said:
Thanks for this @Xadro . I just received my Moto X Force yesterday, it's great to see this available.
One thing I noticed is that the /sdcard/TWRP folder doesn't seem to be accessible (tried ES File Ex and Android terminal). Android Terminal displayed 'do not have permission' ls -al showed normal perms for the directory
Click to expand...
Click to collapse
Are you talking of the external sd card (sdcard1)? Or the internal emulated one?
Moderator Edit: @MuyKurioso - it is not necessary or desirable to quote the entire OP. Some users have limited bandwidth or are Mobile - this can affect page load times. Please consider this in the future. Thanks.
Are you currently trying to port CM to Kinzie? Or just waiting to help out someone? Just curious, and thanks for all your hard work in this recovery!
fubofo said:
Thanks for this @Xadro . I just received my Moto X Force yesterday, it's great to see this available.
One thing I noticed is that the /sdcard/TWRP folder doesn't seem to be accessible (tried ES File Ex and Android terminal). Android Terminal displayed 'do not have permission' ls -al showed normal perms for the directory
Click to expand...
Click to collapse
You need root to look inside that folder, you need to access through data/media/0/TWRP you probably did not give superuser permissions to your file manager.
Does this work for the turbo 2?
Xadro said:
Are you talking of the external sd card (sdcard1)? Or the internal emulated one?
Click to expand...
Click to collapse
I have backed up to the internal emulated sdcard.
I wanted to sync the folder and backup to my NAS
Sent from my XT1580 using Tapatalk
---------- Post added at 10:16 AM ---------- Previous post was at 10:13 AM ----------
AztekSoul said:
You need root to look inside that folder, you need to access through data/media/0/TWRP you probably did not give superuser permissions to your file manager.
Click to expand...
Click to collapse
It is accessible through TWRP file manager.
I did try with root permissions in ES File Explorer. Although i haven't tried that directory - is it a symlink?
Sent from my XT1580 using Tapatalk
fubofo said:
It is accessible through TWRP file manager.
I did try with root permissions in ES File Explorer. Although i haven't tried that directory - is it a symlink?
Click to expand...
Click to collapse
/sdcard is a symlink to /data/media/0/. The explanation why it isnt accessible in /sdcard is simple. The folder is not owned by media_rw.
To fix this, navigate to /data/media/0 in ES File Explorer. Then highlight TWRP folder by long touching it. Go to properties and change owner and group of the folder to media_rw. This should fix access rights when trying to access the folder via /sdcard symlink.
Xadro said:
/sdcard is a symlink to /data/media/0/. The explanation why it isnt accessible in /sdcard is simple. The folder is not owned by media_rw.
To fix this, navigate to /data/media/0 in ES File Explorer. Then highlight TWRP folder by long touching it. Go to properties and change owner and group of the folder to media_rw. This should fix access rights when trying to access the folder via /sdcard symlink.
Click to expand...
Click to collapse
Thanks, managed to chown the directory in terminal emulator. All works great now, thanks
Sent from my XT1580 using Tapatalk
Hello @Xadro!
I tested new Clark TWRP 3.0.0-1 version (twrp-3.0.0-1-clark.img) in my MOTO X FORCE and everything worked perfect (except MTP in my case). I believe this new version could be a good base for a Kinzie recovery. What do you think?
rodrigoger said:
Hello @Xadro!
I tested new Clark TWRP 3.0.0-1 version (twrp-3.0.0-1-clark.img) in my MOTO X FORCE and everything worked perfect (except MTP in my case). I believe this new version could be a good base for a Kinzie recovery. What do you think?
Click to expand...
Click to collapse
There is something for you in the OP

Categories

Resources