Team Win Recovery Project 2.4, 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.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
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.
Special thanks to toastcfh, the sexy, neckbearded, nice thighed, elite guy that he is, for helping to get TWRP working properly on the S3 Mini.
Reserved!
yayyyyyyyyyyyyyyyyyyyyy
AW: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]
Aaawwwwweeeeesssoommeeeeee!
Sent from my GT-I8190 using xda app-developers app
Oh yeah! Great work.
So will this work with other versions too? (Specifically the I8190L version )
And my flashable zip again.
Sv: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]
With goomanager I get "no recoveries were found for your device".
Maybe because I already done "dd",or isn't it on server yet?
Sent thru time and space from my s3mini.
tys0n said:
With goomanager I get "no recoveries were found for your device".
Maybe because I already done "dd",or isn't it on server yet?
Sent thru time and space from my s3mini.
Click to expand...
Click to collapse
Same with me. But through Rom manager there is also upgrade to recovery
Sent from my GT-I8190 using xda premium
AW: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]
Benzonat0r said:
And my flashable zip again.
Click to expand...
Click to collapse
I tried this zip.
You are the master!
ExtSd is found here.
All features works pretty cool.
Only the version inside must be upgraded.
Very good work.
Only one thing were so much fun,
Partition sd card..
Good evening
Sent from my GT-I8190 using xda app-developers app
mermigas said:
Same with me. But through Rom manager there is also upgrade to recovery
Sent from my GT-I8190 using xda premium
Click to expand...
Click to collapse
Yes, but with rom manager you won't find a recovery for our device because CWM in this forum isn't official build.
Not saying it's no good. xd.bx did a great job, it's just not official
AW: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]
In rom manager there are official cwm and twrp recoveries on ma phone.
There is listed as samsung g9190 golden.
Quiet interesting..
Sent from my GT-I8190 using xda app-developers app
Trykall8 said:
In rom manager there are official cwm and twrp recoveries on ma phone.
There is listed as samsung g9190 golden.
Quiet interesting..
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Oh, I didn't know it was official CMW! Thats great!
Can you really install TWRP with rom manager?
Isn't it CWM touch?
No no, you got that all wrong.
First of all this is not CWM it's TWRP custom recovery.
You can't install it via ROM Manager but you can install it via GooManager.
Benzonat0r said:
No no, you got that all wrong.
First of all this is not CWM it's TWRP custom recovery.
You can't install it via ROM Manager but you can install it via GooManager.
Click to expand...
Click to collapse
Well the goomanager didn't find anything for my device, I mean didn't find no recoveries.
Sent from my GT-I8190 using Tapatalk 2
It's probably a bug, use my flashable zip.
Also does flashing this recovery increase the binary count?
Sent from my GT-I8190 using Tapatalk 2
If you flash it via CWM or via Terminal with dd if command then no, but if you flash it via Odin yes
And yes there's an official CWM recovery and also CWM touch recovery for our device.
For anyone that isn't able to have GooManager find a recovery for you, open up your /system/build.prop and find ro.product.name and give me that line.
Dees_Troy said:
For anyone that isn't able to have GooManager find a recovery for you, open up your /system/build.prop and find ro.product.name and give me that line.
Click to expand...
Click to collapse
ro.product.name=goldenxx
Related
Another port of my custom recovery.
For the aroma file manager option to work you have to flash the zip at least once as the zip file will put aroma in the correct place on your sdcard.
Download ------> cwm6032touch_v15.0.2_m7.zip
Thanks to :
gweedo767 (for creating the original touch recovery)
koush (for creating CWM)
PhilZ (for his amazing improvements and help with applying universal touch code) BIG THANKS!
htc-msm8960 for their device tree
PREVIOUS VERSIONS:
Code:
v1:
[CODE]initial release
v2:
Code:
- updated to latest version of clockworkmod
- add reboot download option
- add reboot recovery option
- add power off option
- change font size
- add various internal/external sdcard options from cwm 5.5.0.4 touch recovery
- change order of internal/external sdcard so internal comes first on backup/restore/install
v3:
Code:
- add support for phones that sdcard mounts as external_sd
- fix the line below the menu to actually be below the menu
- clean up the "andy the android" picture. (if you make a backup you will see that the picture in the background has been poorly edited. there are bits of black spots around him)
- JellyBean Background
v4:
Code:
- fixed missing slash that was not allowing installs from external sdcard
v5:
Code:
- update to latest version of CWM 6.0.0.8
v6:
Code:
- updated to latest version of CWM 6.0.0.9
- added ability to delete nandroids from recovery (in backup and restore menu)
- changed order of internal/external so external comes first
- fix timestamp creation on backups
v7:
Code:
- updated to latest version of CWM 6.0.1.0
- fixed bug that would not allow backup of /system
v8:
Code:
- update to latest version of CWM 6.0.1.1
- allow customization of backup format (dedupe/tar)
- use minizip tool instead of e2fsck, etc.
- more....
v9:
Code:
- update to latest version CWM 6.0.1.2
- fixed bug where backing up to external wouldnt backup /emmc/.android_secure
- ADDED DUAL LUNFILE SUPPORT! (thanks to topprospect for this!)
-- what this does is when you mount USB storage you
will see both of your sdcards mount at the same time
- various /emmc fixes (recovery now looks for all clockworkmod "." files in /emmc instead of /sdcard)
- this is useful for people who dont use an external sdcard at all
v10:
Code:
- grabbed latest commits to official CWM 6
- added new extras menu (look in 2nd post for info)
- some other stuff i dont remember
v11:
Code:
- fixed hide nandroid progress bug (it now works)
- added sk8's fix permissions option (logging is disabled so it runs faster and it also clears stale data directories)
- fixed bug where normal fix permissions wouldnt create a log to correct location
- cleaned up some syntax
v12:
Code:
- added darkside wipe/super wipe built in
- added aroma file manager built in
- added ability to backup/restore the /efs partition
- cleaned up oneconfirm/hidenandroidprogess features to be one menu item
- more......
v12.5:
Code:
- fixed bug where darkside cache scripts wouldnt work
- added option to create a custom zip (read 2nd post)
v13:
Code:
- report log gets copied to /emmc instead of /sdcard
- add support for roms without busybox (stock roms) to create a custom rom zip
- add support for openrecoveryscript (read [URL="http://forum.xda-developers.com/showpost.php?p=31093552&postcount=344"]THIS[/URL])
- add support to choose a custom created openrecoveryscript
- use goo-manager to flash roms and create openrecoveryscripts
- now detects where android_secure is automatically
- fix ors-mount.sh to work even if 'sdcard' is in the path
- misc code cleanups.....
v13.1
Code:
- bug fixes
- android_secure fixes
v13.2
Code:
- that pesky android_secure - bugfixes for restoring android_secure
v13.3
Code:
- updated to latest 6.0.1.4
- some bugfixes
- added option to select where android_secure lives (hopefully this is the last time. i promise)
v13.4:
Code:
- updated aroma file manager to latest version
v13.5:
Code:
- add initial support for whole-device encryption (thanks topprospect)
v14:
Code:
- updated to latest CWM 6.0.1.5
- fixed some mtdutils issues
- added a bootanimation changer
v14.1:
Code:
- not released
v14.2:
Code:
- added bootanimation change selection from external sdcard
- added newest aroma filemanager w/ console support (you can use terminal in recovery)
- updated to latest changes of official CWM
- added support for Android 4.2
- zip file now installs updater.sh to your internal sdcard
- updated updater.sh to fix typo
v14.2.1:
Code:
- openrecoveryscript automatically runs if script is found in /cache/recovery/
- this is good for using my updater.sh or goomanager
v14.3
Code:
- skipping this number to keep in line with my other devices
v14.3.1
Code:
- lots and lots of under the hood improvements
- re-wrote OpenRecoveryScript and efs backup/restore code
- these work alot better now (thanks so much to PhilZ for his amazing help)
- add option to backup/restore boot.img from sdcard
- now using latest stable kernel
- completely re-wrote the touch code for some improvements
- now to select you tap anywhere on the screen
- fixed some typos
- made my source code universally compatible with all phones using ICS or greater
- compiling in jellybean base recovery code now
Code:
v14.4
- fixed soft keys (virtual keys on bottom) (credit to PhilZ for this)
- reverted back to swipe to select
- tweaked some features in the extras menu
Code:
v14.4.1
- messed up on the mount points so i fixed them now
- added some buffer to fix ability to accidentally select wrong item
Code:
v14.4.5
- skipped some versions because they were made for other phones
- re-wrote the create custom backup feature to be universal now with all phones/roms (thanks to PhilZ for the help)
- added new settings menu
- add ability to change timezone
- added /preload support [B](must go and enable it in misc nandroid settings)[/B]
- add rom name to nandroid names
- more i just cant remember now....
Code:
v14.4.6
- added exFAT support
- some under the hood optimizations
Code:
v14.4.7
- added extras>>misc nandroid settings>>disable assert check
- removed black space in error icons
- some under the hood optimizations
- added updater.sh script
Code:
v15.0.0
- updated to latest cwm source
- added HTC One into the group
Code:
v15.0.1
- fix zip file
[/CODE]
Current Version:
v15.0.2
- update to latest cwm official changes
Click to expand...
Click to collapse
How touch works:
UP - swipe finger up on screen
DOWN - swipe finger down on screen
SELECT - swipe finger from left to right
BACK - swipe from right to left
SOURCE: https://github.com/sk8erwitskil/touch_recovery_cm10.1
This is what the new dedupe format does. This is a direct quote from the original creator of clockworkmod:
Code:
ClockworkMod Recovery now deduplicates files between builds. This results in way smaller backups.
Don't delete /sdcard(or emmc)/clockworkmod/blobs
Overview
I've gotten a few questions about how this works, so I figured I'd make a post on it.
Basically, here's what happens:
The files being backed up are hashed (sha256, not that it matters). Then it checks for a file with the name of the hash in
/sdcard/clockworkmod/blobs
So, if the hash of the file was c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed, it looks for /sdcard/clockworkmod/blobs/c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed
If the hash file is found, it continues on to the next file. Otherwise, it copies the file to the blobs directory with the file name being the hash.
ROMs and user data, for the most part, do not change too much between builds and backups. So, your APKs, system files, etc, are generally only stored once. This saves a ton of space. Especially between incremental backups.
Some of you may be thinking "well, how do I delete a backup?".
First, never delete the blobs directory. This would actually delete all your backups by rendering them unusable.
Simply delete the usual backup directory, and the next time you run a backup, all the unused hash files will be automatically delete (a process known as garbage collection). The recovery will show "Freeing space..." while this is happening.
Sounds great - keeping the backup size low is very useful especially when all of the roms are 900+ MBs. I wish there was an easy way to move / still use my TWRP backups.
Thanks... Testing it out now...
Sent from my HTC One using xda app-developers app
Any Idea if this works for the Canadian HTC One on Bell?? I'm not really sure what the differences between the versions are... I tried to install CMW Touch last night and it all seemed to work but when I select recovery it just reboots (twice) and then boots up normally... Sorry Kinda new to the One and installing a recovery
Any help or advice would be greatly appreciated
johnblundon said:
Any Idea if this works for the Canadian HTC One on Bell?? I'm not really sure what the differences between the versions are... I tried to install CMW Touch last night and it all seemed to work but when I select recovery it just reboots (twice) and then boots up normally... Sorry Kinda new to the One and installing a recovery
Any help or advice would be greatly appreciated
Click to expand...
Click to collapse
hmmm i havent checked out what the differences are between att and bell ones. it might have a different partition layout. how did you install recovery?
sk8erwitskil said:
hmmm i havent checked out what the differences are between att and bell ones. it might have a different partition layout. how did you install recovery?
Click to expand...
Click to collapse
Used fastboot method with windows found here: http://forum.xda-developers.com/showthread.php?t=2173863 and used the touch one... not sure about the partition stuff, it gave me all successful messages in CMD prompt but like I said when I go into the bootloader and select recovery it just shows the HTC screen then reboots HTC screen again reboots and boots normally into the system...
Thanks for any help and info you can provide
Wanted to let you know flashing the zip via recovery didn't work, but flashing via fastboot worked fine for me.
johnblundon said:
Used fastboot method with windows found here: http://forum.xda-developers.com/showthread.php?t=2173863 and used the touch one... not sure about the partition stuff, it gave me all successful messages in CMD prompt but like I said when I go into the bootloader and select recovery it just shows the HTC screen then reboots HTC screen again reboots and boots normally into the system...
Thanks for any help and info you can provide
Click to expand...
Click to collapse
can you do a:
Code:
fastboot boot recovery.img
scotty2hotty1125 said:
Wanted to let you know flashing the zip via recovery didn't work, but flashing via fastboot worked fine for me.
Click to expand...
Click to collapse
yah i think thats due to the s-on or something. just make sure to flash the zip once so you get the aroma fm feature.
sk8erwitskil said:
can you do a:
Code:
fastboot boot recovery.img
yah i think thats due to the s-on or something. just make sure to flash the zip once so you get the aroma fm feature.
Click to expand...
Click to collapse
The script is to flash boot.img aswell. A bit of a typo!
backfromthestorm said:
The script is to flash boot.img aswell. A bit of a typo!
Click to expand...
Click to collapse
so youre saying you were flashing boot and recovery?
sk8erwitskil said:
so youre saying you were flashing boot and recovery?
Click to expand...
Click to collapse
No, just look at the script in the zip. It's all wrong.
backfromthestorm said:
No, just look at the script in the zip. It's all wrong.
Click to expand...
Click to collapse
ah youre right. thanks for catching that! i just typed the wrong name so it wasnt flashing anything haha. fixed it now
thanks a lot
great recovery with no aroma installer issue
Still don't think it will flash anyway, unless s-off, though you could try dd'ing it like how we flash the boot partition now if the straight flash won't do it.
@sk8erwitskil
Hey which kernel you using for this?
johnblundon said:
Used fastboot method with windows found here: http://forum.xda-developers.com/showthread.php?t=2173863 and used the touch one... not sure about the partition stuff, it gave me all successful messages in CMD prompt but like I said when I go into the bootloader and select recovery it just shows the HTC screen then reboots HTC screen again reboots and boots normally into the system...
Thanks for any help and info you can provide
Click to expand...
Click to collapse
Boot into phone and go into settings and disable fast boot and you should boot into recovery fine.
Thanks I'll try right now
WORKED PERFECTLY!!! THANKS SOOOO MUCH!!!
Flyhalf205 said:
@sk8erwitskil
Hey which kernel you using for this?
Click to expand...
Click to collapse
im using a prebuilt one i found on github somewhere. actually, i think it was from htc-msm8960. if you were going to say i need to credit the person i got it from then you are absolutely correct. when i made my thread i just grabbed my other thread as a template and just updated a few things but forgot to update the credits section. ill do that right now. sorry about that.
sk8erwitskil said:
im using a prebuilt one i found on github somewhere. actually, i think it was from htc-msm8960. if you were going to say i need to credit the person i got it from then you are absolutely correct. when i made my thread i just grabbed my other thread as a template and just updated a few things but forgot to update the credits section. ill do that right now. sorry about that.
Click to expand...
Click to collapse
I was just curious. Thought someone said they didn't have Aroma issues which was odd because the htc-msm8960 was originally forked from me and my CWM has Aroma issues and I use the stock kernel which so technically you do too.... lol follow me?
Flyhalf205 said:
I was just curious. Thought someone said they didn't have Aroma issues which was odd because the htc-msm8960 was originally forked from me and my CWM has Aroma issues and I use the stock kernel which so technically you do too.... lol follow me?
Click to expand...
Click to collapse
yah im using the same kernel then. are the aroma issues proven to be kernel related? and i think the person that mentioned aroma was referring to the fact that the installer wasnt build with aroma so they didnt have to deal with that when installing this recovery.
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:
Nexus 7 (2013) - flo
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Will there be a version for deb also?
I want to test it but with the flo version this might be a bad idea while using the LTE version of the Nexus 7,
But thanks anyway for your CWM version here - I used it with N7000 and therefore didn't use TWRP.
Until now it was different here...
Thanks
Flo version is booting which is a good sign. However, you get 2 errors when you try to create a Nandroid Backup:
E:FAILED to find partition size `/recovery`
E:FAILED to find partition size `/boot`
Edit: 1 Nandroid Backup created, going to test this soon and report more Bugs after some testing.
Gorgtech said:
Flo version is booting which is a good sign. However, you get 2 errors when you try to create a Nandroid Backup:
E:FAILED to find partition size `/recovery`
E:FAILED to find partition size `/boot`
Click to expand...
Click to collapse
They are cosmetic bugs
Please provide a log on that error
I added a detection mode that seems not working on flo.
To fix it the hard way, provide me from adb shell
Code:
cat /proc/partitions
ls -l /dev/block/platform/msm_sdcc.1/by-name
In recovery, it normally tries to resolve the links when i do not know the real mmcblk name for partitions. So, in addition to above adb shell commands, if you provide a log, I can see why links are not resolved on this device
For 4.3 roms, you must enable selinux context backup/restore in misc nandroid settings by the way
Here are two screenshots: https://www.dropbox.com/sh/roo85slxi7h9l69/kjBrLNIJmC
Phil3759 said:
They are cosmetic bugs
Please provide a log on that error
I added a detection mode that seems not working on flo.
To fix it the hard way, provide me from adb shell
Code:
cat /proc/partitions
ls -l /dev/block/platform/msm_sdcc.1/by-name
In recovery, it normally tries to resolve the links when i do not know the real mmcblk name for partitions. So, in addition to above adb shell commands, if you provide a log, I can see why links are not resolved on this device
For 4.3 roms, you must enable selinux context backup/restore in misc nandroid settings by the way
Click to expand...
Click to collapse
this looks sweet. Does it have multiboot ability?
Gorgtech said:
Here are two screenshots: https://www.dropbox.com/sh/roo85slxi7h9l69/kjBrLNIJmC
Click to expand...
Click to collapse
Thank you a lot
But I really need a log. Just go into "Custom backup and restore" menu, select boot and recovery only, hit backup
In backup folder, you should have a recovery.log file. Zip and attach here
Else, after the backup, "Advanced Menu" and select report error
I need to know why the readlink function is not doing its job to get what you see with ls -l command
I´ve included the log file to the dropbox folder Just to make sure it doesn´t get lost, also as an attachment.
Phil3759 said:
Thank you a lot
But I really need a log. Just go into "Custom backup and restore" menu, select boot and recovery only, hit backup
In backup folder, you should have a recovery.log file. Zip and attach here
Else, after the backup, "Advanced Menu" and select report error
I need to know why the readlink function is not doing its job to get what you see with ls -l command
Click to expand...
Click to collapse
Gorgtech said:
I´ve included the log file to the dropbox folder Just to make sure it doesn´t get lost, also as an attachment.
Click to expand...
Click to collapse
Thank you a lot
I am fixing the silly bug I did
Will release an update when back to home
v5.18.4
http://d-h.st/users/philz_touch/?fld_id=26583#files
This fixes the boot/recovery partition size check
That bug had no effect on backup/restore. It is just for the progress bar accuracy
Phil3759 said:
v5.18.4
http://d-h.st/users/philz_touch/?fld_id=26583#files
This fixes the boot/recovery partition size check
That bug had no effect on backup/restore. It is just for the progress bar accuracy
Click to expand...
Click to collapse
This version is asking me to fix root when i reboot...every time
joeyddr said:
This version is asking me to fix root when i reboot...every time
Click to expand...
Click to collapse
Nothing to do with CWM
Only change from previous is fix to detect size of boot and recovery on backup
Is that fixed?
Phil3759 said:
Nothing to do with CWM
Only change from previous is fix to detect size of boot and recovery on backup
Is that fixed?
Click to expand...
Click to collapse
that seems to be and the version before din't ask to fix root.
joeyddr said:
that seems to be and the version before din't ask to fix root.
Click to expand...
Click to collapse
say yes and it will be happy probably
Or see if you updated your ROM SU version
Phil3759 said:
say yes and it will be happy probably
Or see if you updated your ROM SU version
Click to expand...
Click to collapse
I reflashed the supersu 1.65 and it went away thanks.
Only 12 people thanked for such a nice recovery?
Maybe because there is no (install)information whatsoever?
Sent from my GT-I9505 using xda app-developers app
Barthlon said:
Maybe because there is no (install)information whatsoever?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Should install info be in a dev thread?
Phil3759 said:
Should install info be in a dev thread?
Click to expand...
Click to collapse
Quoting your own posts there
How to Install
This will depend on your device. Please look first for help in your device specific thread.
Provided instructions here ARE NOT VALID for all phone
Click to expand...
Click to collapse
So the answer must be "yes".
ThaiDai said:
Quoting your own posts there
So the answer must be "yes".
Click to expand...
Click to collapse
No
I meant forums, not thread. Will edit it.
People should look, into their device forum, FAQ and General. Dev threads are not meant to be a how to flash tut
If someone doesn't know how to flash a recovery, he has no reason to lurk here. He should start in other general/faq forums
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed.
This rom is for both the Nook Tablet 512M/8GB and 1GB/16GB versions. The device code name is "acclaim".
Prerequisites:
A CWM recovery. To install CWM when coming from a stock device, you need to prepare a special SD card. Installation instructions can be found here on xda.
Installation:
Grab a new recovery (e.g. here http://goo.im/devs/chrmhoffmann/cm-11.0/acclaim/recovery-20140502.img) and flash it with fastboot. You will need to update the recovery in case you have an older one from CM 10.2 or older.
If you have a recent CM 10.1 installed, flash the new recovery and try the updater, otherwise download the zip from nightlies, boot to CWM and flash it.
Once a version is installed, you can update with CM Updater
Settings->About tablet->CyanogenMod updates->Refresh
Building:
The CM wiki explains that here: http://wiki.cyanogenmod.org/w/Build_for_acclaim
Returning to stock BN firmware:
If you have installed above rom and the CWM recovery and you really hate it and want to go back to stock, you may wish to try to flash the original acclaim_update.zip from BN. You have to unzip that file and edit META-INF/com/google/android/updater-script. Drop the first two lines here:
assert(getprop("ro.product.device") == "blaze" ||
getprop("ro.build.product") == "blaze");
Zip the package again. Then go to CWM, flash the zip, wipe, and reboot.
Support:
For any issues encountered, please post into this forum, but add steps to reproduce and dmesg and logcat information. If you don't know what this is or how to get them, try to find that out first before posting here.
Developers:
hashcode, ntemis, kuzma30, fattire, mik_os, chrmhoffmann, and many others that contribute to cyanogenmod and especially this version
Thanks:
kuzma30 - great kernel job
hashcode - we have reused lots of your work and effort for the various omap devices (esp kindle fire). It is thanks to you mainly that we are now official CM device.
mik_os - great touchscreen firmware flasher and other efforts
fattire - for helping us everywhere he can
ntemis - thanks for giving so much energy to this - esp for 4.4 I have copied lots of things from you
DISCLAIMER:
- update the CWM if you come from older versions - otherwise you'll see funny error messages when installing zip
- It is possible that you need to wipe your device. I did not do that, but...
- Also you must flash 4.4 gapps. It can be found somewhere....
- The SELINUX policies are not yet enforced.
Known issues:
- Wifi "works" but a clean fix has to be thought of...
- from time to time boot hangs/crashes. In that case, you need to reboot - I don't know how to fix that - seems that surfaceflinger randomly crashes on boot, but it was the case in older releases (cm-10.2), too.
Get it from http://download.cyanogenmod.org/?device=acclaim
Get recovery from here
File: http://goo.im/devs/chrmhoffmann/cm-11.0/acclaim/recovery-20140502.img
md5sum: 0613b47d01400088d09284eb22c5ecc8
Older versions:
File: http://goo.im/devs/chrmhoffmann/cm-11.0/acclaim/recovery-0.2.img
md5sum: e2a87c433171b3d97d852d27aea1ff49
Get it here:
http://goo.im/devs/chrmhoffmann/cm-11.0/acclaim/cm-11-20131213-UNOFFICIAL-acclaim.zip
md5sum 5658cdfa0c043ac28e25d2fbc50d746e
CM 11.0 build 1: http://goo.im/devs/chrmhoffmann/cm-11.0/acclaim//cm-11-20131208-UNOFFICIAL-acclaim.zip
md5sum: c4c251501cc8b6c4ff4b66443230820f
CWM Recovery 6.0.4.5: http://goo.im/devs/chrmhoffmann/cm-11.0/acclaim/recovery.img
md5sum: fe92011742acaa0190f4180f4e7c77ce
Thanks! I'll be downloading this later.
Sent from my Nexus 4 using Tapatalk
Is there any way to flash the new cwm as a zip through the cwm recovery I have now?
Sent from my LG Optimus G using xda app-developers app
Mirror?
hello,
Installing to a bone stock unit
from a CWM 6.0.2.8 SD card
Im getting
"set_metadata_recursive: some changes failed"
"error in /sdcard/CM-11-20131208-UNOFFICIAL-acclaim.zip"
Log shows
ApplyParsedPerms: removexattr of /system/addon.d/50-cm.sh to 0 failed : Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
edit: appears to have installed with no errors thru twrp 2.6.3.1 (as altboot on same sdcard)
thanks for the work !
I am getting constant android.process.media force closes. Only way to get around them was to delete MediaProvider.apk in /system/priv-app. Probably not OK to do this?
Sent from my Galaxy Nexus
this is a great ROM !
----------
for those who like me , really want to have a working flash player in their web browser
this appears to work quite nicely
( forum.xda-developers.com/showthread.php?t=2548001 )
Download Dolphin Browser
Download Dolphin Browser Jetpak
get his modified flash player from that thread.
I turned flash "Always ON" in Dolphin settings
Thanks again to the devs for all their work.
---------------- workaround 2
"unfortunately android.process.media" has stopped keeps popping up for me
Its probably been addressed, but I stopped it for now with no noticeable ill effects yet by disabling the app "media storage"
----------------------
rajsris said:
I am getting constant android.process.media force closes. Only way to get around them was to delete MediaProvider.apk in /system/priv-app. Probably not OK to do this?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
So far, this too is my biggest problem. I can't open Play to install any other apps. WiFi does work though, so hallelujah! I'll try deleting MediaProvider.apk when I get home just so I can install some other apps.
mikeataol said:
this is a great ROM !
----------
for those who like me , really want to have a working flash player in their web browser
this appears to work quite nicely
( forum.xda-developers.com/showthread.php?t=2548001 )
Download Dolphin Browser
Download Dolphin Browser Jetpak
get his modified flash player from that thread.
I turned flash "Always ON" in Dolphin settings
Thanks again to the devs for all their work.
---------------- workaround 2
"unfortunately android.process.media" has stopped keeps popping up for me
Its probably been addressed, but I stopped it for now with no noticeable ill effects yet by disabling the app "media storage"
----------------------
Click to expand...
Click to collapse
Yep, it works OK after that. If you want to change the wallpaper however, you can't do it using a longpress in the home screen, it must be done using settings->display->wallpapers. Even with that, I keep getting Google search force closes when I try to use the stock KitKat wallpapers.
Sent from my Galaxy Nexus
billy8362 said:
Is there any way to flash the new cwm as a zip through the cwm recovery I have now?
Sent from my LG Optimus G using xda app-developers app
Click to expand...
Click to collapse
Ok what I meant was, is there a zip to flash the new cwm to internal emmc??
In addition, MX Player says it is an incorrect android version, which might be related to MediaProvider being deleted.
Sent from my Galaxy Nexus
mikeataol said:
hello,
Installing to a bone stock unit
from a CWM 6.0.2.8 SD card
Im getting
"set_metadata_recursive: some changes failed"
"error in /sdcard/CM-11-20131208-UNOFFICIAL-acclaim.zip"
Log shows
ApplyParsedPerms: removexattr of /system/addon.d/50-cm.sh to 0 failed : Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
edit: appears to have installed with no errors thru twrp 2.6.3.1 (as altboot on same sdcard)
thanks for the work !
Click to expand...
Click to collapse
You need to install new CWM - or some working twrp.
Chris
rajsris said:
In addition, MX Player says it is an incorrect android version, which might be related to MediaProvider being deleted.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I think that is just a problem with the app. Same problem on other tablets.
Chris
billy8362 said:
Is there any way to flash the new cwm as a zip through the cwm recovery I have now?
Sent from my LG Optimus G using xda app-developers app
Click to expand...
Click to collapse
Just install with fastboot....
Chris
billy8362 said:
Is there any way to flash the new cwm as a zip through the cwm recovery I have now?
Sent from my LG Optimus G using xda app-developers app
Click to expand...
Click to collapse
You can install it from a terminal emulator, if you want to.
1. Download the cwm-recovery.img file referenced in the first post of the thread.
2. Copy this file to the internal memory of your Nook Tablet. Rename this file to cwm.img.
3. On your Nook Tablet, launch Android Terminal Emulator (ATE).
4. In ATE, type in 'su' [ENTER]. Grant it access when prompted.
5. In ATE, type in 'cd /emmc' [ENTER]. This will change your file system current directory to /emmc, which corresponds to the internal storage drive.
6. In ATE, type in 'ls' [ENTER]. This will list the contents of the /emmc directory. You should see the cwm.img file you copied over and renamed earlier (step 2).
7. In ATE, type in 'dd if=/emmc/cwm.img of=/dev/block/mmcblk0p3' [ENTER]. This will write the contents of the cwm.img file to partition 3 of device mmcblk0 (internal memory).
You should now be able to reboot and use cwm. CAREFUL, as you could brick your device if you get step 7 wrong.
Nevermind my phone finally did the job
I see process.media crashes a lot. I'll see what I can dish out.
Well I have one solution..disable the Media Storage app in the App section of Settings. That should flush it away..
Sent from my XT907 using xda app-developers app
billy8362 said:
Is there any way to flash the new cwm as a zip through the cwm recovery I have now?
...
Click to expand...
Click to collapse
You can find a flashable cwm zip (e.g.,from Succulent's recovery repo http://goo.im/devs/succulent/acclaim/recovery), then use an archive file manager (e.g., 7-zip) to replace the copy of recovery.img inside that zip archive file with the new recovery version you want (remember to rename it to recovery.img first).
Got ART to work, everything seems to run fine, except for the boot crash that is known about. Is there any plans to move us to emulated storage?
murkurie said:
Got ART to work, everything seems to run fine, except for the boot crash that is known about. Is there any plans to move us to emulated storage?
Click to expand...
Click to collapse
alil confusing.........i thought it was a known issue art in these new 4.4 builds bootloops on ART......atleast thats wut i have been reading and have found out for myself.......how do mind asking did u get it up and running......?
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
Credits
Phil3759 for his awesome recovery
Koush for having created and maintaining cwm
Cyanogenmod for making all this possible
Android-Andi for helping with aroma issue
XDA:DevDB Information
[bacon][CWM Advanced Edition] PhilZ Touch, Tool/Utility for the ONEPLUS ONE
Contributors
katinatez
Version Information
Status: Stable
Current Stable Version: 6.59.4
Stable Release Date: 2015-09-22
Last Updated 2015-09-22
This is flashable through custom recovery, if you prefer fastboot commands extract recovery.img
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot
Changelog
Code:
[SIZE="4"]
2015-09-22
Updated 6.59.4
Fixed backup of LOGO partition
2015-09-21
Updated 6.59.3
Added f2fs to system partition
to support 3 partition f2fs backup
2015-05-18
Updated 6.59.2
updated f2fs with Jaegeuk Kim repo
[URL="https://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs.git/log/?h=linux-3.4"]https://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs.git/log/?h=linux-3.4[/URL]
Backup Firmware all 8 partitions, and modem partition named firmware
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware
Compatible backup & restore with unofficial twrp v2.8.6.1 in Philz twrp mode
cm-12.1 kernel
exfat kernel support
f2fs data & cache in fstab
/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs rw,noatime,nosuid,nodev,discard,nodiratime,inline_xattr,inline_data,nobarrier,active_logs=4 wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-name/reserve4
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs rw,noatime,nosuid,nodev,discard,nodiratime,inline_xattr,inline_data,nobarrier,active_logs=4 wait,check
2015-01-31
Updated 6.59.1
switched to cm-12.0 kernel for faster loading
updated recovery.fstab
updated f2fs commits
2014-12-14
6.59.0
add larger font, thanks [user=2661222]@xiaolu[/user]
2014-10-26
6.58.8
Added CM fix for persist partition
Added backup/restore of persist partition
2014-10-13
6.58.7: Source Update and Fixes
merge NTFS sources into recovery
add NTFS check binary (ntfsfix)
compile NTFS binaries as libraries and link them to recovery binary
spares 500Kb space
fix compile error when NTFS is disabled
2014-10-11
Update to developers: v6.58.4
Fixes building errors and issues related to new CyanogenMod changes
2014-10-05
Update 6.58.0
libtouch_gui 1.42
CWM 6.0.5.1
update sources
Fix display turned off on auto dim timer:
Some devices, like Motorola and Nexus, have their screen turned off is brightness is set to 0
add option to define min brightness value at compile time
by default, min brightness value is now 10 instead of 0
2014-09-18
6.57.9
fix install in "Free Browse Mode" from non vold managed volumes
2014-09-14
Update v6.57.8
CWM 6.0.5.1
fix for ROM OTA updates generating two install scripts (openrecovery + extendedcommands)
merge CWM updates to selinux permissions for init services
fix adb for 3.10 kernel
2014-09-13
Faster boot
Fixed usb-otg
Updated F2FS version 3.4.y
2014-09-03
6.57.5
Full F2FS Support
format,mount,read f2fs
Initial Release
2014-08-28
6.57.5
CWM 6.0.5.0
libtouch_gui 1.41
Aroma File Manager fixed
Screenshots fixed
EFS backup
[/SIZE]
DOWNLOADS
Android File Host
I added a couple of more recoveries I built here, but there will be seldom updates if any.
CWM Full Touch recovery now supports aroma file manager loading.
And stock bacon recovery has been updated, it's here for those who want to take it back to stock recovery
Thanks @katinatez
Thanks!
But this recovery can't mount f2fs. The log show
can't mount /data
cant' mount /system
can't mount /cache
And i cannot flash anything.
F2fs support in recovery kernel will be back?
gulp79 said:
Thanks!
But this recovery can't mount f2fs. The log show
can't mount /data
cant' mount /system
can't mount /cache
And i cannot flash anything.
F2fs support in recovery kernel will be back?
Click to expand...
Click to collapse
I was afraid of that, so f2fs is needed in recovery kernel then correct? Need more time at the moment use previous version with ak kernel then.
katinatez said:
I was afraid of that, so f2fs is needed in recovery kernel then correct? Need more time at the moment use previous version with ak kernel then.
Click to expand...
Click to collapse
Yes, is needed in kernel. Btw at the moment you can put 2 versions, until a kernel with aroma and f2fs will be available. Have you tried to ask @ak to add aroma fix to his kernel? Or maybe @Dees_Troy can add f2fs support.
gulp79 said:
Yes, is needed in kernel. Btw at the moment you can put 2 versions, until a kernel with aroma and f2fs will be available. Have you tried to ask @ak to add aroma fix to his kernel? Or maybe @Dees_Troy can add f2fs support.
Click to expand...
Click to collapse
@johnnyslt said he would help patch the f2fs, just give us time.
Del
radzmin said:
Del
Click to expand...
Click to collapse
Don't understand. What is the question?
katinatez said:
Don't understand. What is the question?
Click to expand...
Click to collapse
Me too[emoji12]
By the way, whats the difference? This works on s4 i9505 right?
katinatez said:
This is flashable through custom recovery, if you prefer fastboot commands extract recovery.img
Click to expand...
Click to collapse
Would you detail your fix for Aroma?
Maybe we could patch aroma sources hopefully
Also, please rename your files so that they fit in goo host
Many third party apps rely on the naming to update recovery images
Phil3759 said:
Would you detail your fix for Aroma?
Maybe we could patch aroma sources hopefully
Also, please rename your files so that they fit in goo host
Many third party apps rely on the naming to update recovery images
Click to expand...
Click to collapse
All I did was to follow your instructions to compile with other kernels! But I should have started with twrp kernel instead! I also unpacked Dees_Troy, dr87 , KINGbabasula twrp recoveries because they all loaded aromafm.zip. After comparison I added rpm, tz, aboot into recovery.fstab. Compiled with Dees_Troy twrp kernel & dt.img and success.
Also changing naming convention of zip files. Sorry about that
radzmin said:
Me too[emoji12]
By the way, whats the difference? This works on s4 i9505 right?
Click to expand...
Click to collapse
Will not work on s4, your in one plus one forum.
Bah, time and date still borked. My backups are a mess. Does twrp also have this issue?
Mr Woolf said:
Bah, time and date still borked. My backups are a mess. Does twrp also have this issue?
Click to expand...
Click to collapse
Set up your time in options...
gulp79 said:
Set up your time in options...
Click to expand...
Click to collapse
Tried it mate, won't stick. Time was fine on my s3 using philz - have never managed to get it to work on my OnePlus though.
Mr Woolf said:
Tried it mate, won't stick. Time was fine on my s3 using philz - have never managed to get it to work on my OnePlus though.
Click to expand...
Click to collapse
Try with options, have you enabled battery clock? In the options there are some flag to set. For me works, I've to set up time only after option reset
Mr Woolf said:
Bah, time and date still borked. My backups are a mess. Does twrp also have this issue?
Click to expand...
Click to collapse
Correct settings is time settings/Qualcomm time daemon. That should fix your time.
katinatez said:
All I did was to follow your instructions to compile with other kernels! But I should have started with twrp kernel instead! I also unpacked Dees_Troy, dr87 , KINGbabasula twrp recoveries because they all loaded aromafm.zip. After comparison I added rpm, tz, aboot into recovery.fstab. Compiled with Dees_Troy twrp kernel & dt.img and success.
Also changing naming convention of zip files. Sorry about that
Click to expand...
Click to collapse
:good:
As I thought, the issue is Aroma is no more compatible with many CM kernels
I am not sure about the exact missing part though as I never had an affected device
What is PhilZ?
PhilZ Touch recovery is an advanced edition of cwm recovery, that provides more options and you can use the touch.
The original thread was posted by @karthick mostwanted who created this recovery for this device. He did it flashable with Rashr on a .img file, but the developer @Leonnard made it flashable with Odin. In my case, I tried with Rashr but did not flashed the recovery, so I tried the Odin version, and it worked. I think it was due to the ROM I installed to my cell phone, because the developer posted it on the original development section. So in conclusion, this should work in case you have a ROM installed. See the original thread.
Requisites: To know how to use Odin :silly:
Instructions
After you flash the recovery,do the following:
-Get into the recovery mode and go to <Recovery Settings>GUI preferences>Toggle Virtual Keys and disable them, because they don´t work, only the one to go back
-In that same menu, select "Menu Height" and select it up to get number 20, wich is the smallest, perfect for the little screen of the phone.
-Go to /sdcard/clockworkmod/ and create the folder "aromafm" and "custom_res"
-Go to /storage/extSdCard/clockworkmod and create the "custom_res" folder too (ih this carpets you can save pictures in .png files and then use those pictures as the background of the recovery)
-Download Aroma filemanager and place it in /sdcard/clockworkmod/aromafm/ and you will can use Aroma filemanager getting in Advanced Options>Aroma filemanager
Features
-Based on ClockWorkMod recovery v6.0.5.1 (lastest)
-Root Explorer built
-Binaries SuperSu
-Target sdcard
-Choose from check Root on/off
-Save and load the Recovery Settings
-Enter password in the Recovery
-Change colors and background
-Gestures
-Virtual buttons
-Size and sensitivity of menus
-Option "Clean to Install a New ROM"
-Custom option BackUp
-Shows Progress
-And much more
Some piece of advice, touch works only for scrolling, when selecting an option, you will NEED to press the home button.
Downloads: http://sh.st/bgGAf
I decided to create odin package because sometime Rashr fails and when reboot, the old recovery still there
Big thanks to Img to tar devs
Sent from my GT-S5312 using XDA Free mobile app
Lennoard said:
I decided to create odin package because sometime Rashr fails and when reboot, the old recovery still there
Big thanks to Img to tar devs
Sent from my GT-S5312 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, you're right. That happened to me
I have discovered some errors, for example you can´t put a background image. Developers should maybe improve this recovery
I was incorrect, the method is not the best one but is the only one I've discovered. Take a screenshot in the recovery and modify that image. Good luck!
Mine is fine
David Masa said:
I was incorrect, the method is not the best one but is the only one I've discovered. Take a screenshot in the recovery and modify that image. Good luck!
Click to expand...
Click to collapse
Don't need to do it
Just drop the PNG image in ClockworkMod directory in SdCard1
Which is:
sdcard1/clockworkmod/custom_res
After this
Change the image normaly