Cannibal Open Touch v2.1 (latest update: 12/1/2012)

Cannibal Open Touch v2.1 (latest update: 12/1/2012) - Nexus 7 Original Development

Thanks this looks awesome, I will definantly use it when it supports 4.2. I may give it a shot on 4.1.2 though to see what it is all about

mlaws90 said:
Thanks this looks awesome, I will definantly use it when it supports 4.2. I may give it a shot on 4.1.2 though to see what it is all about
Click to expand...
Click to collapse
Yeah Drew (the other dev on the project) wrote in that warning there; it's referring to the Android control application that he did. Allows you to easily change the persistent settings from within android instead of recovery (including but not limited to the user defined backup paths). The recovery does work in 4.2, the app does not.
To set user defined backups you could use the app in 4.1 or older than upgrade the settings will remain in place; or manually create a file in sdcard/cotrecovery/ with the title .userdefinedbackups and the sdcard folder you would like backups saved to: for example if you wanted to add rom manager compatibility you would want your backups to be in '/sdcard/clockworkmod/' so in the .file you would simply write 'clockworkmod' without the quotes.

Sblood86 said:
Yeah Drew (the other dev on the project) wrote in that warning there; it's referring to the Android control application that he did. Allows you to easily change the persistent settings from within android instead of recovery (including but not limited to the user defined backup paths). The recovery does work in 4.2, the app does not.
To set user defined backups you could use the app in 4.1 or older than upgrade the settings will remain in place; or manually create a file in sdcard/cotrecovery/ with the title .userdefinedbackups and the sdcard folder you would like backups saved to: for example if you wanted to add rom manager compatibility you would want your backups to be in '/sdcard/clockworkmod/' so in the .file you would simply write 'clockworkmod' without the quotes.
Click to expand...
Click to collapse
Oh see, that is not a big deal at all. I would be willing to give that a shot, didn't even know there was an app Thanks for the detailed reply, I'm sure it will help others as well.

The recovery looks nice ^_^
Don't know why I prefer unique recoveries and not popular ones

I like the look of this recovery, I have nothing as of yet to flash, but I'll definitely be keeping it

Thanks
Sent from my SGH-I747 using xda premium

OK just to clarify, this does work 100% with 4.2.1 ROMs? And where can i find some themes for it.....looks verrrrrrry promising
Edit...and I'm not concerned about backups as i never use them.... FULL wipe every time for me
Sent from my Nexus 7 using xda premium

lightninbug said:
OK just to clarify, this does work 100% with 4.2.1 ROMs? And where can i find some themes for it.....looks verrrrrrry promising
Edit...and I'm not concerned about backups as i never use them.... FULL wipe every time for me
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yes the recovery works w/ 4.2 roms the only issue is the app that Drew did not being able to communicate with the sdcard properly in 4.2 (this is not related to the recovery itself).
Themes we could use more of; there is an outline of them on our forums and on github (nexus 7 is of course the jb-800x1200 branch)

Looks nice gonna give it a run through

Are there any sources? I kind of want to build this for my spectrum or do you not have plans for open source
Sent from my Nexus 7 using Tapatalk HD

azoller1 said:
Are there any sources? I kind of want to build this for my spectrum or do you not have plans for open source
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I apologize; I ripped the thread layout off from Drew and didn't realize the source was not linked. I'll get it linked in the OP at a later time but for now suffice it to say yes we have open sourced everything; we have full intention of open sourcing all future related code as well (hence the 'Open' part of the name ):
Either sync a CM10 tree or use the jellybean branch in Drew's hacked up manifest (this will only build recovery).
Whichever way you sync your repo you will need to replace the recovery folder (Drew's manifest is pulling the old repo)
you will need the jellybean branch from the recovery itself:
android_bootable_recovery
if you used Drew's manifest you should already have the following if not you will want to pull these as well:
the jellybean branch from here
android_bootable_recovery_gui
and the master from here
android_bootable_recovery_res
Lastly; a slightly modified grouper device repo (pretty sure this one is also for recovery only lol)

I'll definitely give this a run when I can later today!

Pretty Awesome. Installed just fine on my Nexus7 WiFi. Gonna run this for a while and see how she goes, tnx!

Quick question, is there a way to flash this without a computer? As u currently don't have one and could I use my twrp backup if anything are to happen or would I need to make a new one with this recovery?
Sent from my Nexus 7 using Tapatalk HD

xfrancis14 said:
Quick question, is there a way to flash this without a computer? As u currently don't have one and could I use my twrp backup if anything are to happen or would I need to make a new one with this recovery?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
You need to use fastboot, which requires use of a computer (for now). TWRP backups are not compatible so yes you would need to make a new backup.

Okay well I don't currently have a computer so I guess ill stick with twrp for now and okay
Sent from my Nexus 7 using Tapatalk HD

Is it possible for you to make an app which would flash the recovery? If so that would he amazing as I really want to try this recovery
Sent from my Nexus 7 using Tapatalk HD

xfrancis14 said:
Is it possible for you to make an app which would flash the recovery? If so that would he amazing as I really want to try this recovery
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Well... If the nexus 7 supports flash_image or dd (which I have no idea if it does, you'll have to find out or ask Drew) than yes it's possible; than again you could simply do it from a terminal emulator in that case. Fastboot is the safest way in particularly without having the device myself to play with.

finally got a chance to test her out, so far so good!
not the absolute best advance since sliced bread but i do love seeing an alternative!
as of now i give it a 7 out of ten being no problems i can find, everything seems to work but dont feel as if im gaining much over my other recovery options... that said i felt the same way at first with 4ext recovery and now i absolutely love it, so ill let you know if this moves to 10 out of 10 an time soon
thanks again for giving me options!

Related

[ROM][WIP][AOKP] Android Open Kang Project Beta 26 for TF201[2/29/2012]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is this?
This is the AOKP-android open kang project compiled for the TF201. I have tested this and this flashes with no problem. This rom has waaaaaaaay more features then CM9. Like seriously... it has a option in Settings called Rom Control. You can read about it here: http://forum.aokp.co/
Disclaimer
I or PG are not responsible for what happens to your beautiful prime. So, please act with caution. I am 100% sure this works as I have tested it, however.... if if you dont know how to use adb, i suggest you stop reading right now and learn that first.
BEFORE YOU FLASH PLEASE READ
This rom has been shared for educational and entertainment purposes. Please dont flame, dont complain and please dont wine if you find something that doesn't work, this is why this is Work in Progress. Hopefully, it'll work 100% 1 day, and we of course have no ETA. So please do not ask. Maybe another dev can take a crack at it?
Who made this build? Compiled it?
This build was compiled by PlayfulGod. Please donate to him here: http://bit.ly/yeOD3T. Original work by AOKP. This is just a port for the tf201 and nothing more. Credit to AOKP. I have been given permission by PG to release it to the public. This rom comes with no support. However, you can stop by #asus-transformer on freenode and If i am around... I will gladly help. As the TF201 has been unlocked, i figured it would be beneficial to all android enthusiast to have more than 1 option for roms. That is why we are making this build available. Test it out and tell me what you think. Please expect bugs as this is a WIP. I will post screenshots soon.
What is not working?
Screen Rotation is only in portrait mode (Looking into Orientation Switch on market)
Not all options in the Rom Control work
LED Options
Reboots when pressing the Power Button to sleep the TFP
Screen won't turn off while closing the dock/tablet
MicroSD (Looks like there is a solution for CM9, will look into it)
I have noticed on a few occasions as some of these options are not working with the TF201, it will do a fastboot. So, please do not complain.
Instructions
Install like any other rom, however MAKE SURE you unmount SYSTEM and unmount STAGING.
1. Make sure you're on the latest CWM
2. MAKE A NANDROID
3. unmount system & staging
3. wipe data/factory reset in recovery
4. flash ROM
5. flash Gapps (if you want)
6. reboot
Remember, to make a backup of your current rom. Also make a backup of your boot.img, so if you do decide to go back to your rom you can flash the boot.img and you'll be back to normal.
How to backup your Boot.img? You can use ADB or Terminal Emulator
1. su (to make sure you have #)(if your in adb.... adb shell)
2. dd if=/dev/block/mmcblk0 of=/sdcard/boot.img bs=4096 skip=3968 count=2048
Wanna restore to what you had?? Heres how to do it right....
So you saw it, you like it, you can't wait till it completely works, but you wanna go back to what you had for now....
1. Make sure you have your boot.img backed up from the rom your going to restore.
2. Go to CWM and do the Restore
3. Once thats done, go to ADB and flash Boot img
4. adb shell & su (make sure you have #)
5. dd if=/sdcard/boot.img of=/dev/block/mmcblk0 seek=3968 bs=4096 count=2048
6. Exit & Reboot
Now you should be back exactly where you are now be4 you flash AOKP.
Download
AOKP for TF201 - Build 26 - http://goo.gl/2LOiO
Gapps - http://goo-inside.me/gapps/gapps-ics-20120224-signed.zip

Awesome, thanks! Been waiting for this!
One thing: where's the Gapps download?
EDIT: Seems to reboot when you press the power button.

redbullcat said:
Awesome, thanks! Been waiting for this!
One thing: where's the Gapps download?
EDIT: Seems to reboot when you press the power button.
Click to expand...
Click to collapse
gapps-ics-20120224-signed.zip

MasterZen88 said:
gapps-ics-20120224-signed.zip
Click to expand...
Click to collapse
Yeah, I found them literally after I said that. Thanks

Yeah baby more roms! Thank you for this, you beat jermain to the punch with aokp but the more the merrier
-EVO-

Woooo! Can't wait to install this thank you!

Yea, i had noticed that also. I completely forgot to mention it. It was 3 am when i posted this last night.
Updated post.

too many choices, need some help
Is there some high-level comparison of AOKP vs. CM9 vs. Asus stock?
What is Kang and what is its relationship with Cyanogenmod? I've seen CM kernels that have kang in the name, but then also AOKP as a separate rom.
What specific features make Kang compelling for tablets? I've explored the Kang website a bit, but there's nothing that gives an overview of the purpose/goals of the project.

ragesoss said:
Is there some high-level comparison of AOKP vs. CM9 vs. Asus stock?
What is Kang and what is its relationship with Cyanogenmod? I've seen CM kernels that have kang in the name, but then also AOKP as a separate rom.
What specific features make Kang compelling for tablets? I've explored the Kang website a bit, but there's nothing that gives an overview of the purpose/goals of the project.
Click to expand...
Click to collapse
Kang is not the name of the rom, kang means built from someone elses code Eg, if someone takes the cm kernel source builds a kernel from it and releases it you could call that a kang.
The name of this rom is more of a joke I believe as it is "kanged" from source
sent from my Transformer Prime

No NTFS support ?
Hi, Firstly thanks for sharing the ROM. Installed over the Virtuous ROM (.15 v2) to play with and all installed ok, apps restored via TB, etc. but have found that my 32gb microsd card shows up as a Blank SD Card when inserted (I had to create the Removable subfolders first, as per http://forum.xda-developers.com/showpost.php?p=23006383&postcount=2), this read fine before on the stock roms and also on Virtuous. So guessing that the kernel used on this rom doesn't support NTFS ?
Any plans to get NTFS support included as 90% + of the HD films I have are way over 4gb

A feature list for the OP would be nice.
I believe it has the same features as listed on this lsit: https://sites.google.com/site/androidopenkangproject/feature-lsit?

YES!!! AKOP on my prime!! This rocks thank you!

cant wait to flash it!!! thx buddy!

For those that are unaware, AOKP is AWESOME!
I don't think I will flash this until some of those bugs are cleared up, but as soon as those are fixed I am in.
I have not used CM9 yet, but AOKP on my Galaxy Nexus is more stable than any CM7 ROM I ever tried. Its packed with features and the devs are always adding new stuff.

marko! said:
Kang is not the name of the rom, kang means built without permission or stolen work. Eg, if someone takes the cm kernel source builds a kernel from it and releases it you could call that a kang.
The name of this rom is more of a joke I believe
sent from my Transformer Prime
Click to expand...
Click to collapse
I must correct you, Kang is an official denomination of self compiled CM from sources. The Kang ROMs are not stolen !!
CM are built by a buildbot automatically every day or nearly, everyone can build a Kang from sources (remember it's open source) and when you do that the build script automatically add 'Kang' to the name of the ROM as it appear is Settings> About Device menu.
Thus you can easily make the difference between ROM compiled by Cyanogen buildbot and ROM compiled by dev. Usually Kangs are a way to pick only interesting commits for the specific device (called cherry picks) or even removing some commits that are eventually causing bugs.
For example on my optimus 2X phone, CM9 is not officially released, but the CyanogenMod dev in charge of maintaining CM tree for our phone made a Kang to enable us to test it (he named it SelfKang with humour ...)
Don't write such things it could lead to misinterpretations...

Hell yeah. Thought I was in the inc2 forums for a second. This is the best ics rom I've ever used (at least for mobile). Can't wait to give it a run on the tfp
Sent from my Incredible 2 using XDA App

"Orientation Switch" from the Market helps with the orientation issue.
Other issue: the screen won't turn off while closing the dock/tablet.

Nice AOKP on my Desire HD and now my prime. This is great news. For everyone who doesnt know, there are a lot of customizations with rom control. Once the few bugs are worked out, its golden.
Sent from my HTC Desire HD using Tapatalk

Thank you sooooo much! The C9 ROM was KILLING ME! Bug city. After flashing it, I couldn't get wi/fi on any of the other ROM's i was using. So far this looks great. I'm hoping the landscape fix is coming soon.

hobbypunk said:
"Orientation Switch" from the Market helps with the orientation issue.
Other issue: the screen won't turn off while closing the dock/tablet.
Click to expand...
Click to collapse
From what I've learned the kernel is usually the issue with orientation. I have a Skyrocket and of I use a kernel from the Hercules (TMobile version) the orientation is opposite. Sometimes in settings you can torn off specific degrees of orientations.
Thanks for the tip about the app BTW.
Sent from my SAMSUNG-SGH-I727 using xda premium

[ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Grouper

Ohai! Guess I'll jump in here.

Yup... Spoiled by the participating...

Caution - SDcard directory changes with 4.2 installation
For those of you that are new to 4.2 releases, be aware that installing and running this rom creates a directory "/sdcard/0" and moves all content in the sdcard directory to the "0" directory. (Perhaps I missed a posting somewhere on this.)
I reinstalled this rom a few times due to Gapps crashes and later could not find any of my files files in the sdcard directory including my backup files. I first thought I had accidentally formatted the sdcard, but later found that each time I had tried to flash and start this rom another new "0" subdirectory was created and all files were moved to yet another subdirectory. By time I was done all my files were safely stored in /sdcard/0/0/0/.
Also be aware that the Clockworkmod directory is one of those moved and Clockworkmod Recovery may not be able to find your nandroid backup in the new directory if you decide to restore. I haven't tried the latest version of CWM, but it was a problem on the six week old version I had installed.
It took me a few minutes to figure out what was going on and am hoping to save someone else the trouble.
Edit: Installed the latest version (as of 12/17) of CWM and it.too was unable to find my nandroid backup once it was moved to the /sdcard/0 directory by the 4.2 installation process. To restore my old rom I had to do a clean install, then install ES file Explorer, move the clockworkmod directory to /sdcard/ and THEN restore.

freecity said:
For those of you that are new to 4.2 releases, be aware that installing this rom creates a directory "/sdcard/0" and moves all content in the sdcard directory to the "0" directory. (Perhaps I missed a posting somewhere on this.)
I reinstalled this rom a few times due to Gapps crashes and later could not find any of my files files in the sdcard directory including my backup files. I first thought I had accidentally formatted the sdcard, but later found that each time I had tried to flash this rom another new "0" subdirectory was created and all files were moved to yet another subdirectory. By time I was done all my files were safely stored in /sdcard/0/0/0/.
Also be aware that the Clockworkmod directory is one of those moved and Clockworkmod Recovery may not be able to find your nandroid backup in the new directory if you decide to restore. I haven't tried the latest version of CWM, but it was a problem on the six week old version I had installed.
It took me a few minutes to figure out what was going on and am hoping to save someone else the trouble.
Click to expand...
Click to collapse
You need to upgrade your recovery to the latest cwm or twrp. The issue has been fixed since 11/16

freecity said:
For those of you that are new to 4.2 releases, be aware that installing this rom creates a directory "/sdcard/0" and moves all content in the sdcard directory to the "0" directory. (Perhaps I missed a posting somewhere on this.)
I reinstalled this rom a few times due to Gapps crashes and later could not find any of my files files in the sdcard directory including my backup files. I first thought I had accidentally formatted the sdcard, but later found that each time I had tried to flash this rom another new "0" subdirectory was created and all files were moved to yet another subdirectory. By time I was done all my files were safely stored in /sdcard/0/0/0/.
Also be aware that the Clockworkmod directory is one of those moved and Clockworkmod Recovery may not be able to find your nandroid backup in the new directory if you decide to restore. (I haven't tried the latest version of CWM.)
It took me a few minutes to figure out what was going on and am hoping to save someone else the trouble.
Click to expand...
Click to collapse
Its not "this ROM" its all 4.2 ROMs that do it. And the way to prevent the /0/0/0/0 is by updating your recovery to the latest CWM or TWRP.
the new multi user in 4.2.x moves all your internal data to /data/media/0 for the main device owner. And if you create another user you will see /1 for the second user and so on for however many users you add.
So on 4.2.x ROMs you will have one /0 and it needs to be like that, if you move all your data to /data/media you will have issues. The /0 is a must and is the way of the future.
Having said that I will say it again. If you haven't already you really need to update your recovery.
Also on the note of gapps you must use the gapps specifically for 4.2 not 4.1.1 if you don't use 4.2 gapps you will have gapps fc like crazy

The slider in the Quicksettings menu for brightness is very laggy. Volume seems fine though. Also, my battery meter in Quicksettings sometimes says 0%, even though I'm at 97%.

runandhide05 said:
Its not "this ROM" its all 4.2 ROMs that do it. And the way to prevent the /0/0/0/0 is by updating your recovery to the latest CWM or TWRP.
the new multi user in 4.2.x moves all your internal data to /data/media/0 for the main device owner. And if you create another user you will see /1 for the second user and so on for however many users you add.
So on 4.2.x ROMs you will have one /0 and it needs to be like that, if you move all your data to /data/media you will have issues. The /0 is a must and is the way of the future.
Having said that I will say it again. If you haven't already you really need to update your recovery.
Also on the note of gapps you must use the gapps specifically for 4.2 not 4.1.1 if you don't use 4.2 gapps you will have gapps fc like crazy
Click to expand...
Click to collapse
The version of gapps I installed was 4.2 downloaded from the OP. I also tried a 4.2 gapps downloaded from another link so I was probably just missing a step somewhere or had a bad rom download, I'll try again tomorrow.
I do not believe I suggested that there was anything wrong with this or any other 4.2 rom (and certainly did not mean to suggest anything of the sort), only that there are important changes to be aware of when moving from 4.1 to 4.2 and back.

Thanks, will give it a try.

freecity said:
The version of gapps I installed was 4.2 downloaded from the OP. I also tried a 4.2 gapps downloaded from another link so I was probably just missing a step somewhere or had a bad rom download, I'll try again tomorrow.
I do not believe I suggested that there was anything wrong with this or any other 4.2 rom (and certainly did not mean to suggest anything of the sort), only that there are important changes to be aware of when moving from 4.1 to 4.2 and back.
Click to expand...
Click to collapse
Also note a full wipe is a MUST coming from any other ROM or even eos3
And I didn't read it as implying anything.
Just be sure to update recovery
All good Buddy

Does this have tablet ui? Can't use my nexus 7 without it. Lol
Sent from my Nexus 7 using xda premium

TheUndertaker21 said:
Does this have tablet ui? Can't use my nexus 7 without it. Lol
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
In a way.. It has the option to put the soft keys in the left side like tab ui but keeps the top status bar
Sent from my Nexus 7 using Tapatalk 2

Haha that'd do. Thanks for reply.
Sent from my Nexus 7 using xda premium

That's pretty sweet.

New build out. Eos is on a roll

Can we just dirty flash 45 over 44? Will gapps need to be reflashed again also?
44 was running pretty well. Already downloaded 45. Waiting on answer before I flash new build.

demandarin said:
Can we just dirty flash 45 over 44? Will gapps need to be reflashed again also?
44 was running pretty well. Already downloaded 45. Waiting on answer before I flash new build.
Click to expand...
Click to collapse
Dirty flash is fine.. I've had no issues going from 44 to 45
Sent from my Nexus 7 using Tapatalk 2

DJLamontagneIII said:
Dirty flash is fine.. I've had no issues going from 44 to 45
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Yep..dirty flashed rom an reflashed gapps. All running well so far.

Unless instructed otherwise from eos4 nightly to nightly a dirty flash is fine.
Also the latest update fixes ALOT of the third party apps FC'ing.
So put firefox, kindle, and many more on the problem squashed list.

Anybody having issues using the latest nightlys with custom kernels? I tried using Franco's kernel and I am unable to install paid apps with it. I get the USB storage error.

[ROM] 【4.2.2】【UNOFFICIAL】CyanogenMod 10.1.3.1【ON-HOLD】【GPL】

[ROM] 【4.2.2】【UNOFFICIAL】CyanogenMod 10.1.3.1【ON-HOLD】【GPL】
MWF Nightlies
Freshly built every MWF Night
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod 10.1.3.1 is a free, community built distribution of Android 4.2.2 (Jelly Bean) which greatly extends the capabilities of your phone.Features:
CM10.1.3.1
Koush's SuperUser is default
Android JB 4.2.2
Working OTA system - Requires CWM 6.x.x.x/TWRP 2.6.0.0 or later. Amon RA will not work.
Apollo
HDR Camera
CM's new "File Manager"
Lockscreen widgets - kinda
Scroll typed text with vol -/+ (CM settings)
Bluetooth Calling (Has been reported working, your results may vary)
Multi Language Support
Zipaligned
All images optimized
Installation InstructionsI recommend users of this rom to be on the latest firmware and Hboot with an s-off device. If you are not on the latest global firmware, here is how to do it.
NOTE: For recovery I use TWRP 2.5.0.0. Some wipe options below may not be included in other recovery options. Still wipe what is available the best you can.
1. Put the Rom on the root of your SD Card
2. Compare MD5 Sum
Windows: MD5 Calculator
LINUX: Open Terminal and type: md5sum [path to the rom on your sd card]
Mac: Open a terminal and type: md5 [path to the rom on your sd card]
3. Reboot to Recovery
4. Scroll down and select "Wipe"
5. Wipe the following:
Wipe ALL data/factory reset x2
Wipe /data x2
Wipe /cache x2
Wipe Dalvik-cache x3
Wipe /boot x2
Wipe /system x3
Optionally wipe:
Wipe battery stats
Wipe rotate settings6. Scroll to and press return
7. Install Rom from SD Card
8. Reboot and enjoy!Further questions about the ROM
Please check the FAQ in the second post.
Note: Please do not mirror the Rom. Thanks.NOTICE: I do not provide a changelog. However, you may view the official CM changelog by clicking CHANGELOG
Downloads:
ROM: DOWNLOAD
----------------------------------------------------------------------------------------
GApps: gapps-jb-20130812-signed.zip
signatures.mobile-overload.com
I wanted to say thanks to Chad and everyone else involved in getting AOSP based ROMs working on the Rezound. Without our talented group of devs, none of this would be possible.Source:
Google - Android
Cyanogen - Source
Chad0989 - Made it possible to run AOSP based roms on the Rezound
Vigor - Beta builds
Vigor - Kernel
Please see post two for additional notes.

Frequently Asked Questions
HTC Rezound UNOFFICIAL CM10.1.3 (JB-4.2.2)
This is a short list of Q&A that should help you find answers to the questions you might have concerning flashing and using this ROM.
[SIZE=+1]Q1: What version of Android is this?[/SIZE]
This Rom is CM10.1 which is currently built on Android 4.2.2.
[SIZE=+1]Q2: I looked but did not see a changelog in the op. How can I track your changes?[/SIZE]
I do not provide a changelog but you can track CM's official changelog for recent changes.
You can also find device specific changes by looking at Flyhalf205's Github
[SIZE=+1]Q3: Is this ROM S-On compatible?[/SIZE]
By default, no. Follow these instructions to flash on an S-On device:
NOTE:
You must have the Android SDK downloaded and installed onto your computer.
You must be familiar with the SDK's install directory structure.
You must be familiar with using terminal and know how to cd to the platform-tools folder of the Android SDK's install directory.
1. Open the Rom zip with an archive tool such as 7zip and extract the boot.img from it.
2. Place the boot.img into the platform-tools folder of the Android SDK's install directory.
3. Put the Rom and GAPPS on the root of your SD Card
4. Compare MD5 Sum
Windows: MD5 Calculator
LINUX: Open Terminal and type: md5sum [path to the rom on your sd card]
Mac: Open a terminal and type: md5 [path to the rom on your sd card]
5. Reboot to Recovery
6. Scroll down and select "Wipe"
7. Wipe the following:
Wipe ALL data/factory reset x2
Wipe /data x2
Wipe /cache x2
Wipe Dalvik-cache x3
Wipe /boot x2
Wipe /system x3
Optionally wipe:
Wipe battery stats
Wipe rotate settings
Click to expand...
Click to collapse
8. Scroll to and press return
9. Install Rom and gapps (in that order) from SD Card
10. FOR GSM USERS ONLY - After flashing the ROM and GAPPS, re-wipe /data and then flash the GSM patch
11. Return to the main menu of the recovery and select "Developer Menu".
12. Select "Reboot to bootloader
13. Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
14. Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
15. Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
16. Watch the output of the terminal, it should say something like "sent successfully".
17. Finally send this command:
Code:
fastboot reboot
This command reboots your device into Android. Wait for it to boot up and enjoy your new freshly installed CM10.1.
Note: If you are having issues connecting your device to your windows computer in fastboot, please insure the drivers are up to date by installing the latest version of HTC Sync for the Rezound.
[SIZE=+1]Q4: Where did the Developer options in settings go?[/SIZE]
Google/Android has hidden this feature in JB 4.2.1 and up. Follow these steps to re-enable the feature:
Go to settings > about phone. Tap Build Number 7 times. Tapping Build Number 7 times re-enables the Developer Options in settings.
[SIZE=+1]Q5: Where did the reboot menu go?[/SIZE]
In Android 4.2.2 this menu is hidden by default in CM10.1 and must be enabled.
Step 1: Enable Developer options using the method described in Q4.
Step 2: Go to Developer options and check the Advanced reboot box.
Step 3: Go to System settings > System > power menu. Insure the Reboot menu box is checked.
Click to expand...
Click to collapse
[SIZE=+1]Q6: What is the recommended HBOOT and Radio for this ROM?[/SIZE]
RADIO: 2.23.10.0123r, 2.23.10.0124r
HBOOT: 2.28
Click to expand...
Click to collapse
If your device is not using this firmware and HBOOT, its very simple to update. Just follow the guide HERE to get updated.
[SIZE=+1]Q7: Is this ROM GSM compatible?[/SIZE]
Yes. You must enter Mobile Networks and change preferred network list to GSM.
[SIZE=+1]Q8: Can you add in [insert name] mod?[/SIZE]
No. By default this ROM will remain bone stock without any modification. It is intended to be the purest form of CM on this forum for the Rezound. However, user created mod submissions are welcome and will be added to the third post (Mods section) if they fit the standards outlined for this ROM.
[SIZE=+1]Q9: When will such and such bug be fixed?[/SIZE]
Bug fixes are always being worked on. As the fixes are made available, they will be included in the next update version of this ROM.
[SIZE=+1]Q10: This ROM seems a little choppy. Is there anything I can do?[/SIZE]
Go into Developer options and disable hardware overlays.
NOTE: You must disable hardware overlays every time you reboot.
[SIZE=+1]Q11: I notice that Superuser isn't in the app drawer, where did it go?[/SIZE]
Recently CyanogenMod has merged in Koush's new Superuser configuration. Starting in build 20130310 you will now found all Superuser settings in the System settings under the Superuser tab.
[SIZE=+1]Q12: How do I zoom in the camera?[/SIZE]
In the camera app place two fingers on the screen and spread rapidly 
[SIZE=+1]Q13: How can I optimize my battery life on this ROM?[/SIZE]
XDA member md303 has written a very helpful post describing their battery usage and what they have done to optimize it for better life. Check it out HERE
[SIZE=+1]Q14: Why isn't my WiFi working?[/SIZE]
You're most likely s-on then. You must flash the boot.img that comes with the .zip inside of fastboot.
If your question is not answered here or you need further help, go to the official Support Thread for this ROM. DO NOT post questions directly in this thread.

MODS UNOFFICIAL CM10.1
Provided by the community
NOTE: User created mod submissions must follow the standards of this ROM for acceptance.
All mods must:
Blend into the ROM as if they were originally entended to be there stock
Must not break any of the other features of the ROM
Must not be designed to leverage harm unto the devices of the other users of this ROM
Should be intended to improve features of the ROM rather than replace those features
If the mod is entended to be used as a theme, it must present a professional and clean appearance
Must not violate the licenses that cover CM. Open source mods only.
Must be flashable in recovery
If your mods and themes are not to these standards, they will not be accepted!
Onto the Mods
Want to set the dpi for apps individually like you can with Paranoid Settings in Paranoid Android?
Get the Xposed Framework to do so HERE
Click to expand...
Click to collapse
Safety! Control what info of yours your apps can detect.
update-cm-vigor-20130320-openpdroid.zip created by manchucka
Click to expand...
Click to collapse
Prefer SuperSU to Superuser?
SuperSU created by manchucka
Click to expand...
Click to collapse
No-Split MMS
Find it here created by socialruins
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Re: [ROM][JB][CDMA] CM10.1 KANG for HTC Rezound [1-21-13]
Awesome sauce, thanks for being the human build machine and getting this out to us, and of course thanks to the devs responsible for getting this to work on our rezounds!
Edit: won't download on mobile oh well to the computer I go! (what is this? 2008?)
Sent from my ADR6425LVW using xda app-developers app

Squirrel1620 said:
Awesome sauce, thanks for being the human build machine and getting this out to us, and of course thanks to the devs responsible for getting this to work on our rezounds!
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
No problem. Happy to do it with Chads blessings

Wow... so much development lately! Thanks a lot for all your hard work!
:good:

is this 4.2?

ryclegman said:
is this 4.2?
Click to expand...
Click to collapse
Yes, 4.2.1

If your having trouble downloading from mobile, please take note what server on @androidfilehost you are attempting to download from. I will need this info so I can file a report. Thanks

Re: [ROM][JB-4.2.1][CDMA] CM10.1 KANG for HTC Rezound [1-21-13]
Oh my! Welcome back
Sent from my Rezound using Tapatalk 2

Re: [ROM][JB-4.2.1][CDMA] CM10.1 KANG for HTC Rezound [1-21-13]
wildstang83 said:
If your having trouble downloading from mobile, please take note what server on @androidfilehost you are attempting to download from. I will need this info so I can file a report. Thanks
Click to expand...
Click to collapse
(CA) server #5
Sent from my ADR6425LVW using xda app-developers app

Re: [ROM][JB-4.2.1][CDMA] CM10.1 KANG for HTC Rezound [1-21-13]
Restore contacts from sim card shows there are no contacts. Should be 12ish. Playing without gapps for a bit.
Sent from my ADR6425LVW using Tapatalk 2

Re: [ROM][JB-4.2.1][CDMA] CM10.1 KANG for HTC Rezound [1-21-13]
Hey, I don't know if anything has changed but last I recall Chad doesn't want to hear any bug reports at all. That was one of the rules when we were told we could post builds, so you might wanna edit the OP so people don't bug him about it. Unless he has specified otherwise, then by all means, feel free.
Sent from my SCH-I535 using xda premium

Re: [ROM][JB-4.2.1][CDMA] CM10.1 KANG for HTC Rezound [1-21-13]
Yup my bad. Totally forgot about that.

Loving it so far. Only thing I noticed is that the camera doesn't zoom. Thanks for sharing this stang!
Nevermind you zoom with the volume buttons instead of pinch to zoom

No wifi tether on this. I'll skip it til I can look further into it.

Re: [ROM][JB-4.2.1][CDMA] CM10.1 KANG for HTC Rezound [1-21-13]
Pmem or ION?
Sent from my ADR6425LVW using Tapatalk 2

Re: [ROM][JB-4.2.1][CDMA] CM10.1 KANG for HTC Rezound [1-21-13]
GoldenCyn said:
Pmem or ION?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
pmem
Sent from my Rezound using xda premium

Re: [ROM][JB-4.2.1][CDMA] CM10.1 KANG for HTC Rezound [1-21-13]
live2die said:
pmem
Sent from my Rezound using xda premium
Click to expand...
Click to collapse
Yup just tested with my basic kernel and it works. So I assume this is pmem not ion. I'm not near a WiFi device can someone see if tether works using my kernel? It always has worked with mine on cm10
Sent from my ADR6425LVW using xda app-developers app

highdro said:
Loving it so far. Only thing I noticed is that the camera doesn't zoom. Thanks for sharing this stang!
Nevermind you zoom with the volume buttons instead of pinch to zoom
Click to expand...
Click to collapse
I have no idea if this is a kernel thing but I'm running a different persons build and shrikes kernel and it zooms

[TOOL] Nightly Updater | 1.5 | Make Your Nexus Perfect | Backup | AROMA | Flo/Deb

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make Your Nexus Perfect
WHAT'S NEW?
> VER 1.5 | SEPT 10 2013
-> Quick Install quickened to 4 clicks as opposed to 6
-> Backup/Restore Menu Added
-> Backup/Restore User Apps and be able to remove backups
-> Backup/Restore Anything using keep.txt and be able to remove backups
-> How To section updated with info on Backup/Restore Menu
-> junk.txt Updated with Media and Face Unlock files
-> On the horizon: App deletion in AROMA installer
PREREQS
Nexus Device that has a system app you do not want
Grade school diploma (i.e. ability to read)
THE SKINNY
WHAT IS NIGHTLY UPDATER
Nightly Updater is an AROMA installer for those that
yearn to have the cleanest device. Since I first
owned an HTC Droid Eris, I have been wiping bloatware
off of my device. Flash foward to my latest devices -
LG Nexus 4 and the 2013 Asus Nexus 7 and there ain't
much bloatware... But, all AOSP ROMs tend to come with
at least one or two apps that I can do without (and
sometimes a lot more). Nightly Updater is a simple
tool that allows users to remove unwanted system
applications in an easy manner. NU also allows users
to customize which apps are removed.
HOW DOES IT WORK
Nightly Updater works by relying on scripts that
read txt files. When customizing your script, the
installer looks for junk.txt in the "NU" folder of
your virtual (i.e. internal) SD card. Each line that
has not been "commented out" (i.e. does not have a
"#" at the front of it) or any terms (i.e. app
descriptions) that follow a "#" are removed from the
script. This leaves Nightly Updater with a clean text
file that only has the applications you want to remove.
Review:
Custom Script is called: junk.txt
Custom Script goes here: /sdcard/NU/junk.txt
#Chrome.apk -- NOT DELETED FROM DEVICE
Chrome.apk -- DELETED FROM DEVICE
Chrome.apk #Google Browser -- AFTER "#" IGNORED
HOW DO I ADD MY OWN APPS
You can add your own apps in three ways: [1] name (without
apk), [2] name (with apk), or [3] file path.
[1] Name (without ".apk")... Just type:
Code:
Chrome
The installer will automatically know it is looking for an apk and
delete Chrome.apk.
[2] Name (with ".apk")... Just type:
Code:
Chrome.apk
I think you know what it does.
[3] Full File Path... Now, you can get a little funkier and do the entire
file path like:
Code:
/data/app/Chrome.apk
This comes in
handy for files like pre-loaded wallpapers and
ringtones you may want to remove. Be cognizant of
where the files you are removing are located! This
will become very important when telling Nightly
Updater where to scan.
By the way, Nightly Updater also recognizes wildcards.
This is great for those user apps that end up having
unpredictable file names. For example:
Code:
/data/app/com.google.android.youtub*.apk
com.google.android.youtube*
These are both ways of erasing YouTube regardless of
the "-X" at the end of the file name.
WHAT'S UP WITH SCANNING
When using a Custom Script, Nightly Updater asks
where you would like to scan for apps. By default,
Nightly Updater recommends you only scan in the
System/App folder - which is where (shocker) system
apps are located. Remember, most junk apps are located
in System/App. However, Nightly Updater has also given
the option to scan Data/App. Some developers will put
apps in the Data/App folder, so it may be useful to
remove apps from there. But NORMALLY, these are only
the apps you chose to install. The final option is
to scan EVERYWHERE. Be very cautious with this command!
Remember that it is matching what you write in
junk.txt with the scan parameter. If you accidentally
wrote "system" as an app you wanted to remove instead
of SystemTuner.apk (with full scan on)... you would
erase your system folder... that's REALLY BAD!!!
Now, if you only check this option when you are using
full path and double check your junk.txt file so that
you did not make any mistakes... YOU ARE GOOD!!!
When in doubt, post your junk.txt here and I will
check it over for you
WHAT'S THE DEFAULT SCRIPT
If you download junk.txt from the OP at XDA, then
you have seen the Default Script. The Default
Script is meant to remove apps that MOST people
would consider expendable. If you are nervous to
tinker with your own Custom Script, try running
the Default Script first. If the script deleted
an app you need or did not delete at app you want
to destroy - hit me up and I will walk you
through the steps.
MORE DIRECTIONS ARE IN THE INSTALLER
DOWNLOADS
Check the "Downloads" Tab
NU-1.5.zip - Nightly Updater Installer
junk.txt - Customizable Removal Script
keep.txt - Customizable Backup Script
BUGS
Installer will occasionally hang when you press "< Back" - Reboot Device to fix temporarily
You tell me
HOW YOU CAN HELP
Give me feature ideas
Come up with more pre-loaded apps to be added to junk.txt
SPECIAL THANKS
Patrics83 and the whole ROM Cleaner team for the inspiration of this amazing tool!!! :good:
XDA:DevDB Information
Nightly Updater, a Tool/Utility for the Nexus 7 (2013)
Contributors
swagstr
Version Information
Status: Stable
Current Stable Version: 1.5
Stable Release Date: 2013-09-10
Created 2013-09-08
Last Updated 2013-09-10

Thanks, sounds helpful, will try it!

NekroWolfen said:
Thanks, sounds helpful, will try it!
Click to expand...
Click to collapse
Please post your results. I have tested up and down... But who knows if I missed anything
Sent from my Nexus 7 using Tapatalk 4

Sorry, but can't find the link for download
Sent from my Nexus 7 using xda app-developers app

swagstr said:
Please post your results. I have tested up and down... But who knows if I missed anything
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Tested on CM10.2, using the default junk.txt with a couple of mods, seems to work fine. Is there a way to have it just automatically run against the junk.txt without all of the dialogs?

swagstr said:
DOWNLOADS
Check the "Downloads" Tab
NU-1.0.zip - Nightly Updater Installer
junk.txt - Customizable Script
Click to expand...
Click to collapse
Updated OP with mobile-friendly links.
rpr69 said:
Tested on CM10.2, using the default junk.txt with a couple of mods, seems to work fine. Is there a way to have it just automatically run against the junk.txt without all of the dialogs?
Click to expand...
Click to collapse
That "Quick Install" pop-up at the start does exactly what you are looking for
Sent from my Nexus 4 using Tapatalk 4

Nice!!
Sent from my LG-LS970 using xda app-developers app

All working fine on CarbonRom, thanks, I love it.

NekroWolfen said:
All working fine on CarbonRom, thanks, I love it.
Click to expand...
Click to collapse
Any apps missing from the stock junk.txt for Carbon? Or any other ROMs. I based it off of PAC ROMs repertoire to cover the big 3.
Sent from my Nexus 4 using Tapatalk 4

Looking cool.
Sent from my Nexus 7 (2013) using Tapatalk 4

This sounds like a tool that should be updating things. Why is it called what it is called? Neat tool though.
Sent from my Nexus 7 using Tapatalk 4

habylab said:
This sounds like a tool that should be updating things. Why is it called what it is called? Neat tool though.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Because Run This While Updating Your Nightly sounds plain silly
Sent from my Nexus 4 using Tapatalk 4

swagstr said:
Because Run This While Updating Your Nightly sounds plain silly
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Nightly Slimmer?
Sent from my Nexus 7 using Tapatalk 4

habylab said:
Nightly Slimmer?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Sounds like a diet pill...

railed said:
Sounds like a diet pill...
Click to expand...
Click to collapse
And Slimbean doesn't? Okay, I shall leave it there!
Sent from my maybe one day to be CM i9300. That day won't come unless the camera improves!

railed said:
Sounds like a diet pill...
Click to expand...
Click to collapse
Lol
habylab said:
And Slimbean doesn't? Okay, I shall leave it there!
Sent from my maybe one day to be CM i9300. That day won't come unless the camera improves!
Click to expand...
Click to collapse
Both valid points. If somebody could come up with an AMAZING name for NU, then I might consider a change.
P.S.: Starting to look into new features as we speak :highfive:

swagstr said:
That "Quick Install" pop-up at the start does exactly what you are looking for
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Not quite what I meant. What would be useful for me is once I have the junk.txt the way I want, I don't want to have to do anything, just flash nu.zip, and it will just run through the steps automatically, with no prompts. Unless I'm missing something I still need to click through a bunch of stuff for it to actually do anything, 6 clicks to be exact.

rpr69 said:
Not quite what I meant. What would be useful for me is once I have the junk.txt the way I want, I don't want to have to do anything, just flash nu.zip, and it will just run through the steps automatically, with no prompts. Unless I'm missing something I still need to click through a bunch of stuff for it to actually do anything, 6 clicks to be exact.
Click to expand...
Click to collapse
Updated! I have taken out two clicks. Unfortunately if I put the pop-up at the VERY start it doesn't draw correctly. And if I don't put the Scanning Options then it wouldn't be fully custom then...

Dude! Haven't seen you since the 3DVO days and Mean ROM! Glad to see you over here in Razor country (I refuse to call it Flo lol), once again with exactly what I'm after. Hope all is well with you, keep up the awesome work!
Sent from my Nexus 7 using Tapatalk 4

swagstr said:
Updated! I have taken out two clicks. Unfortunately if I put the pop-up at the VERY start it doesn't draw correctly. And if I don't put the Scanning Options then it wouldn't be fully custom then...
Click to expand...
Click to collapse
Thanks for the update, it does streamline it a bit, I as thinking along the lines of a flag (for example in a config file in the NU directory) that it would look for that if it found, it would just automatically load up the junk.txt file, scan the directory that is configured, and exit out, with no user intervention at all. I don't know if this is even possible within the aroma framework, if it was, It would meet my needs 100%!
I also tested it on my Samsung Skyrocket and it worked perfectly there as well. Well, once I added back the one item that broke the Play Store, it worked perfectly!

[2014-09-22] [MT2-L03] TeamWin Recovery Project

Disclaimer: You are responsible for insuring you keep a backup of your stock recovery!
See Post 7 for the Stock Recovery if you failed to keep a copy for yourself: Click here
Steps for Backing up Stock Recovery:
Code:
fastboot boot /path/to/TWRP.img
The above command will only boot the recovery and will not overwrite your stock recovery making it possible to backup your stock from within TWRP. Now backup your recovery partition from within TWRP. It will be saved on your device and named, recovery.emmc.win. You can rename it to recovery.img to flash it back via usage of fastboot or apply restore within TWRP given the original filename, recovery.emmc.win.
Or within a terminal using dd (aka Data Destroyer);
Code:
dd if=/dev/block/mmcblk0p19 of=/sdcard/stockrecovery.img
TWRP for MT2-L03
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CHANGELOG for 2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
Installation (PC):
- You MUST have an unlocked Bootloader! /* See Post 2 */
- Download TWRP Recovery
- Boot to your Bootloader
- Plug your device to your PC
- Open Command Window
- Type, then Enter:
Code:
fastboot flash recovery /path/to/TWRP.img
- Also, a video to demonstrate the process of installing TWRP - Credit goes out to @superbass311:
Installation (Device)(More Experienced Users Only!):
- You MUST have an unlocked Bootloader! /* See Post 2 */
- You MUST be rooted!
- Must have Busybox installed or a properly compiled DD binary
- Download TWRP Recovery
- Install a Terminal Emulator from the Play Store
- Type, then Enter:
Code:
su
Followed By:
Code:
dd if=/path/to/TWRP.img of=/dev/block/mmcblk0p19
Download:
- TWRP 2.8.0.0
CONTRIBUTORS
@Modding.MyMind
@xordos
@Shaky156
SOURCES
- Recovery built in a OmniRom 4.4.4 environment using device trees/kernel/dtb
- Stock Kernel
- Stock DTB
- TWRP source from Omnirom
- MT2-L03 Device Configuration Folder - My Github
VERSION INFORMATION
- Status: Stable
- Created 2014-09-22
- Last Updated 2014-09-22

Unlock Your Bootloader:
As we all know, you are not required to be rooted to install TWRP, however, you must unlock the bootloader on your device.
You must email [email protected] asking:
Hello I purchased the Ascend Mate 2 and I would like my bootloader unlock code.
SN: xxxxxxxxxxxxxxxxxxx
IMEI: xxxxxxxxxxxxxxxxxx
Thank you
Click to expand...
Click to collapse
You should get a response within 24 hours. In a situation where 24 hours has passed by than simply be patient or send another email. This is the 1st step to being able to unlock your bootloader (as of now)!
Here is a video to demonstrate to you viewers how you can go about unlocking your bootloader.
- Video credit goes out to @superbass311

*Reserved Again*

I will flash tomorrow. You just made the HAM2 the hottest phone out.
Sent from my MT2L03 using XDA Free mobile app

Thanks to all involved. Re-installed root using TWRP. Now Titanium Backup is working properly.

Flashed just now!
Backing up at the moment.
THANK YOU ALL!!!
How I did it:
Win 8 pc.
Phone booted and usb debugging allowed.
typed "adb.exe reboot bootloader" in cmd terminal
typed "fastboot flash recovery c:\adb\TWRP.img" in cmd terminal
I downloaded zip to my adb directory, also had to rename it too "TRWP.img" as download was "TWRP_MT2-L03_RECOVERY.img"
back up completed in 480 seconds!
Did have to play with TWRP settings as I hadn't used it in a while .
DID I SAY THANK YOU!!!

For anyone who is lazy to backup your stock recovery, I have uploaded my stock recovery image backup here, it should be same for all our MT2-L03 phone
This is backup of stock recovery, only use this image if you want to revert back from TWRP to Huawei stock crappy recovery.
http://tinyurl.com/qzxkm4x
FileName: recovery_MT2L03_mmcblk0p19.img
md5sum: 35703a1fe81917cb7930ab1e9e93e499
Edit: 2nd thought, they should be same, but let's make sure. Can anyone did (or going to) backup your phone stock recovery post the md5sum of yours? The ES file explorer can calc md5sum for a file.
Thanks iammudd, I think it is confirmed the recovery image is same for all MT2L03 phone.

Absolutely freakin' FANTASTIC!!!
Flashed it via fastboot with no problems.
I couldn't get MTP to work, but that's not a huge surprise to me as I've NEVER seen MTP work properly in TWRP on any device I've had sofar. I'd be interested to see if it works for anyone else.
So awesome that a root method is built right in too!
I think this is the verge of some huge things happening for our MT2-L03s!!!

Thanks for the great work!

TheGeekRedneck said:
Absolutely freakin' FANTASTIC!!!
Flashed it via fastboot with no problems.
I couldn't get MTP to work, but that's not a huge surprise to me as I've NEVER seen MTP work properly in TWRP on any device I've had sofar. I'd be interested to see if it works for anyone else.
So awesome that a root method is built right in too!
I think this is the verge of some huge things happening for our MT2-L03s!!!
Click to expand...
Click to collapse
Thanks for the info, right, mtp not work during my init testing as well. So other device are running twrp 2.8.0 or later?
PS, there are another 2 known issus,
* date is ~1970
* off mode charging

xordos said:
Thanks for the info, right, mtp not work during my init testing as well. So other device are running twrp 2.8.0 or later?
PS, there are another 2 known issus,
* date is ~1970
* off mode charging
Click to expand...
Click to collapse
Check your hangouts

Well done everyone ! Excellent stuff.
I suppose you know what my question will be,lol, but is it feasible to be able to port this to the MT2-L05 or other Chinese models?
If it's likely to be feasible, would it be possible to have your permission to attempt a port, or do you think as the underlying processors are different
it would probably wiser to start from scratch?
Either way, good work again !

xordos said:
* date is ~1970
* off mode charging
Click to expand...
Click to collapse
Interesting that backup filename is 1970-03-23 but the timestamp is 1979-12-31 23:00 on the phone.
After FTP'ing them onto Win7, their last modified times are 2013-12-31 22:00.

The device configuration folder used to build TWRP is available on my github which you can find the link in the OP under "SOURCES". If you have any knowledge on this stuff then feel free to look it over and throw some patches my way. As it stands, mtp isn't working properly however, mtp has only been known to work for a very small select list of devices. A very small list. As for the time stamp, this isn't much of a concern on my part as it is merely cosmetic. However, the problem with it would most definitely be the result of the actual TWRP source and not the configuration folder (device tree). Feel free to look further in to it if it is bothersome.
Right now, my goal is to see if I can resolve the mtp issue if it happens to be at all plausible since the mtp featured in TWRP is still fairly new and has much more work to be done with it over at TeamWin.
Currently looking in to offmode charging as well. This is merely cosmetic. But would be nice to have.

xordos said:
For anyone who is lazy to backup your stock recovery, I have uploaded my stock recovery image backup here, it should be same for all our MT2-L03 phone
This is stock, only use this image if you want to revert back from TWRP to Huawei stock crappy recovery.
http://tinyurl.com/qzxkm4x
FileName: recovery_MT2L03_mmcblk0p19.img
md5sum: 35703a1fe81917cb7930ab1e9e93e499
Edit: 2nd thought, they should be same, but let's make sure. Can anyone did (or going to) backup your phone stock recovery post the md5sum of yours? The ES file explorer can calc md5sum for a file.
Click to expand...
Click to collapse
Yes, md5 are the same and fc on Win7 of your/my versions are the same.

4L0M said:
Well done everyone ! Excellent stuff.
I suppose you know what my question will be,lol, but is it feasible to be able to port this to the MT2-L05 or other Chinese models?
If it's likely to be feasible, would it be possible to have your permission to attempt a port, or do you think as the underlying processors are different
it would probably wiser to start from scratch?
Either way, good work again !
Click to expand...
Click to collapse
Hi, just saw your another post about MT2-L05 RESOURCES. I am not sure if Modding.MyMind have time or not to do this. Maybe we can do some quick test, if worked, then his build (after small update) can support L05 phone as well.
Sending you a PM.

Just flashed TWRP recovery, and it's working great!
Now we just need a CyanogenMod ROM. While I'm thinking about it, when does Android "L" officially get released? It would be nice to just jump from Jelly Bean to L.

xordos said:
Hi, just saw your another post about MT2-L05 RESOURCES. I am not sure if Modding.MyMind have time or not to do this. Maybe we can do some quick test, if worked, then his build (after small update) can support L05 phone as well.
Sending you a PM.
Click to expand...
Click to collapse
I'd be willing to be a guinea pig for the Mt2-l05 if you need more people.

I second that
Sent from my MT2L03 using XDA Free mobile app

Gir357 said:
Just flashed TWRP recovery, and it's working great!
Now we just need a CyanogenMod ROM. While I'm thinking about it, when does Android "L" officially get released? It would be nice to just jump from Jelly Bean to L.
Click to expand...
Click to collapse
L should be released sometime in October I believe, alongside the new Nexus phone and tablet.
Supposedly the HAM2 is getting an EMUI 3.0 update (KK) in November. I don't know if the US version is included though.

Better Mobile App

welcome