[Q] button map for cwm recovery - @rwaterspf1

[Q] button map for cwm recovery - @rwaterspf1 - Samsung Infuse 4G

Hi friends:
I have an infuse 4g with the infamous power button issue. Somehow I have managed to install kitkat on it (due to power button being too touchy in touching it, it was almost impossible to boot to recovery or download mode using the button combo).
So I flashed AoCP 7.2 which was good. I even liked the fact that the CWM recovery included with it did not need me to press the power button for menu selection but rather the capacitive touch search button worked for menu item selection. The CWM version was 6.0.4.6.
But now I updated to CM11 and it upgraded my recovery to 6.0.4.8 but now capacitive search button does not work for item selection. Option and home capacitive touch buttons are still working for moving up and down but I really want search capacitive touch button to work for item selection.
Can somebody explain how can I enable this?
Edit: the search capacitive button does not work for item selection in the root menu (it works in any of the sub-menus).
Thanks in advance.

anybody please.

@Fullmetal Jun
Hi Fullmetal Jun:
I applied your recently created cm11 image and it seems the latest recovery does not allow search capacitive button on the main screen in cwm.
I checked the recent commits in recovery in the github and there are some changes related to how the search button is handled.
I thought to compile the recovery myself but i need the board specific make file that i want to extract from the boot.img but the unpack tools are not working on the boot.img, can you please provide this or generate a new boot.img with recovery fixes (the fix should be small).
Thanks

[email protected] said:
Hi Fullmetal Jun:
I applied your recently created cm11 image and it seems the latest recovery does not allow search capacitive button on the main screen in cwm.
I checked the recent commits in recovery in the github and there are some changes related to how the search button is handled.
I thought to compile the recovery myself but i need the board specific make file that i want to extract from the boot.img but the unpack tools are not working on the boot.img, can you please provide this or generate a new boot.img with recovery fixes (the fix should be small).
Thanks
Click to expand...
Click to collapse
I'm sorry, but I've never created any files for the Infuse! You sure it's really me?
All I know is that I created a detailed list of procedures to flash ROMs properly for the Infuse 4G!
For selection using touch screen, CWM Recovery supports only the capacitive buttons like you mentioned above!
BUT another recovery called TeamWin Projects(TWRP) allows use of touch screen in recovery while flashing which is what you want! It has a newer interface and is as reliable as CWM!! You'll need to find a stable version though

@rwaterspf1
Ohh I'm sorry. rwaterspf1 did it and I saw one of your reply in that thread. Thanks for your replying.
So yeah search capacitive search button does not work for selection in the root menu (the very first menu that you see when cwm recovery starts).
I want this as my infuse has power button issue and I don't want to use power button for selection.

@rwaterspf1
So i checked the source code in default_recovery_keys.c in https://github.com/CyanogenMod/android_bootable_recovery/blob/cm-11.0/default_recovery_keys.c
earlier it was like this and the search capacitive button was working for item selection:
case KEY_END:
case KEY_BACKSPACE:
case KEY_SEARCH:
- if (ui_get_showing_back_button()) {
- return SELECT_ITEM;
- }
- if (!get_allow_toggle_display() && !ui_root_menu) {
- return GO_BACK;
- }
case KEY_BACK:
if (!ui_root_menu) {
return GO_BACK;
but with a recent commit, it was changed to following and as you can see that search button wont anymore do item selection:
case KEY_END:
case KEY_BACKSPACE:
case KEY_SEARCH:
case KEY_BACK:
if (!ui_root_menu) {
return GO_BACK;
I think it'd be really great to use search button for item selection so that the devices like mine can use it instead of the buggy power button

Related

[RECOVERY] ClockworkMod TOUCH 5.5.0.4 v4.3 - (7/9/12)

This is gweedo767's touch recovery ported to the skyrocket/hercules. Because many people have been asking me what the difference between this one and the version that koush put out here is the difference:
This one is open source.
This one has swipe gestures (up,down,left,right)
This one has different UI settings
This one has soft keys on the bottom of the screen
This one has 2 different options of font
Here is a youtube video I made of how it works: ------> VIDEO
4 ways to use recovery:
volume rockers
soft keys on bottom of screen
capacitive buttons
swipe gestures (up/down = scroll && left = back && right = select)
HOW TO INSTALL:
CWMR5504_INSTALL-4.3.zip (NEW ICS BACKGROUND): ---------> BLUE-FONT
CWMR5504_INSTALL-4.3.zip (NEW ICS BACKGROUND): ---------> ROBOTO-FONT
- Just flash in CWM
Click to expand...
Click to collapse
TERMINAL INSTALL:
recovery.img: (NEW ICS BACKGROUND) ----------------> BLUE-FONT
recovery.img: (NEW ICS BACKGROUND) ----------------> ROBOTO-FONT
- download to sdcard
- open terminal emulator (or adb) type:
Code:
$ su
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22 bs=4096
Click to expand...
Click to collapse
Odin Install
recovery.tar.md5 (NEW ICS BACKGROUND): ---------> BLUE-FONT
recovery.tar.md5 (NEW ICS BACKGROUND): ---------> ROBOTO-FONT
Click to expand...
Click to collapse
Test Drive:
CWMRT5504_TEST-4.3.zip(NEW ICS BACKGROUND): -------------------> BLUE-FONT
CWMRT5504_TEST-4.3.zip(NEW ICS BACKGROUND): -------------------> ROBOTO-FONT
(This will not alter ANY files on your phone. It is just a test drive basically. You flash it through ClockworkMod that you have already installed and it runs over it showing you how it would be if you did install it. Once you reboot you will still have the same recovery that you had.)
Click to expand...
Click to collapse
v1:
Code:
- Initial release
v2:
Code:
- fixed "back button disabled/enabled" when scrolling past top to bottom
- 2 different font versions (roboto and normal)
-- roboto font is a little bigger
- complete fix of adb and usb mounting
v2.5:
Code:
- added a cool new ICS background! (thanks CyanmodICS for the idea)
- added green/red font versions
- cleaned up the code a bit
v3:
Code:
- in process of fixing hanging backup issue (need extensive list of apps people have installed when having issue)
- fixed ALOT of bugs
- added many more options for internal/external sdcard
- more....(i cant remember)
- i will add the other color options back in a few days
v3.5
Code:
- fixed recovery.fstab to mount internal sdcard as /sdcard to recognize .hidenandroidprogress file
- ascii art???
v4.0
Code:
- fixed the fix_permissions not working (thanks minotauri)
- fixed sd-ext and .android_secure errors in backup
v4.1
Code:
- re-arranged order of "install from internal/external sdcard" to put internal first
- added "Reboot Recovery" option to the bottom of the advanced menu
- a few code cleanups
v4.2
Code:
- fixed bug where background would reset to blank black after installing a zip/backing up/restoring
- added option to reboot into download mode in advanced>>reboot download mode
v4.3
Code:
- hopefully fixed the hanging backup bug once and for all
- merged all of CWM's latest code changes
Thanks to:
Code:
gweedo767
plastikman
utkanos
romracer

Thanks! I guess i'll be the first tester, to make sure i don't get bricked or anything

Badass!!! Guess I be tester number 2 haha
Sent from my Desire HD using xda premium

Sweet. Flashing now
Sent from my SAMSUNG-SGH-I727 using xda premium

so i created a recovery.tar.md5 to flash through odin. I flashed it and it automatically booted back into android. Once i rebooted into recovery everything worked in there but when i tried to reboot it would only reboot back into recovery. i did a battery pull and waited a few minutes but it only booted into clockworkmod. I had to flash the original clockworkmod 5.5.0.2 i had before to be able to boot back into android. anyone have any ideas on why it gets stuck in a clockworkmod boot loop?
this is only for the recovery.tar.md5...not for the cwmrt5504.zip. just wanted to clarify that. the .zip file is completely safe and will not alter any files on your device when you flash it.

How's the cwm working
Sent from my SAMSUNG-SGH-I727 using xda premium

the zip file seems to work fine. restored a red sonja backup, then flashed another to try it out more. all went well.

so to everyone who has tried it out:
how do you feel about the sensitivity on the swipe gestures? up/down sensitivity? left/right sensitivity? does the sensitivity need to be lowered or raised or stay the same?
thanks

so will this be an actual new recovery or an overlay of type for our current cwm
Sent from my SAMSUNG-SGH-I727 using xda premium

im going to create a recovery.tar.md5 that is flashable via Odin and will be a whole new recovery. but the one i have now gets stuck in a boot loop that only boots into recovery.

Problem with Scrolling...
For me obviously noticed the colours as well noticed that when I pushed Volume increase menu scrolled down and when I pushed Volume Decrease menu scrolled up. Anyone else get that issue... overall what is the difference between this and the other clockworkmod recovery... basically what is the benefit to flashing this over flashing the one that comes with ROM Manager....
Weird when I restarted my phone and went back into recovery it went back to CWM 5.0.2.7 is that what it's supposed to do?

i hadnt checked the volume rocker mappings yet. ill fix that. i just havent used anything but the swipe gestures.
the difference between this and the original one is that you do not need to touch any buttons. you swipe your finger up and down to scroll and swipe left to go back and swipe right to select. and there are the soft buttons on the bottom of the screen. basically there are 4 ways to move around and select and go back.
1.) volume rockers
2.) swipe gestures
3.) soft keys
4.) capacitive buttons
and i explained in the OP that it was a fakeflash. which means that it does not install it on your phone. thats the reason why you booted back into your original clockworkmod. i have an installable version but it is not ready yet. i do not want to release it yet because it could mess up your device.

My Bad... I missed the fake flash... that's why you should read the entire comment I guess LOL... Anyways awesome thanks for the quick reply.

no problem. ive done that before. usually its when i get really excited about a new rom and i download it without reading the whole post and then something doesnt work with it and i get frustrated and realize they have a patch in the OP or something. haha
anyways, once i get the boot loop problem fixed i will make a recovery.tar.md5 that you can just flash in Odin and itll be an entirely new recovery installed

i updated the file on my box.com account with the correct volume rocker key mappings.

So this is the same CWM just a touch screen version... aren't we using a version of CWM that is made for the regular galaxy s2? Isn't that why there are tons of problems with FC's because this CWM does not delete everything it is suppose to and we end up having to install the stock recovery to do a factory reset?

well this is the latest clockworkmod 5.5.0.4. the only other CWM i can find is 5.0.2.7. so its updated. not sure what the changelog is on that though. And this isnt a version that was made for the gs2. it was originally made for the galaxy nexus. Im pretty sure its the same source code as the code from the cm9 repo. Im not 100% sure on that though. ill have to ask gweedo.

and ive been using this recovery for about a week and have backed up/restored/flashed new roms/reset to factory/erase cache/dalvik all a few times and havent had any issues with it not deleting everything.

I have to ask, have you figured out what's up with the colors? They could hurt your eyes if you looked at it too long. xD

Also note, which is something that's also been an issue with the current CWM, Fix Permissions doesn't do a thing. Press it and it instantly tells you it's done. Should at least take a minute to get everything done. Just wanted to mention that this problem still exists. Definitely not at all any kind of dealbreakef, but I just don't get why any ports have worked for our devices.
Sent from my SAMSUNG-SGH-I727 using xda premium

[RECOVERY] Custom Recoveries for Galaxy R

Hello everybody!
Yesterday, I collected my previous recoveries, updated them and built a new one (TWRP) too. I made CWM-flashable and Odin-flashable packages too.
CWM v4.0.0.2: (Thanks to The-Droidster for the recovery! )
- This is the first ever custom recovery for the Galaxy R.
- It has all the nice CWM features.
- You can restore ICS with this.
- It has no known bugs. Everybody used it as a starting point.
- What I changed:
- Removed the /lib/modules directory. --> 0,1MB size decrease.
- Enabled button backlight.
- Key layout: Scrolling: Volume up+down, Selecting: Home key, Going Back: Power+Back button. (Menu key doesn't do anything.)
CWM: http://www.mediafire.com/download.php?71ynk9btw7euocr
ODIN: http://www.mediafire.com/download.php?iczq8xed26ohakw
CWM v5.5.0.4:
- Built from the latest CM9 sources.
- It has all the nice CWM features.
- It can restore v4 backups (you can restore ICS with this too).
- Very stable!
- It has no known bugs yet (Lot of users have been using it and no bugs have been reported).
- Toggle feature is disabled! (I find it really annoying and it doesn't make real sense for a recovery to lock the screen.)
- Key layout: Scrolling: Volume up+down, Selecting: Home key, Going Back: Power+Back button. (Menu key doesn't do anything.)
CWM: http://www.mediafire.com/download.php?98c1smq7nk4485d
ODIN: http://www.mediafire.com/download.php?c7qbjaqwgpnbr9w
CWM v6.0.3.2:
- Built from the latest CM10.1 sources.
- It has all the nice CWM features.
- It can restore v4 backups (you can restore ICS with this too).
- Key layout: Scrolling: Volume up+down, Selecting: Home key, Going Back: Power+Back button. (Menu key doesn't do anything.)
- Known issues: ADB Sideload
CWM: http://www.mediafire.com/download/7xyevjf32fixf3a/CWMv6.0.3.2_CWM.zip
ODIN: http://www.mediafire.com/download/oksv1o2hu63gohi/CWMv6.0.3.2_ODIN.tar
CWM v6.0.1.5 Touch:
- Built using the online builder at http://builder.clockworkmod.com
- It has all the nice CWM features.
- It can restore v4 backups (you can restore ICS with this too).
- Key layout: Scrolling up: Volume up or home button, Scrolling down: Volume down or menu button, Selecting: Power button, Going back: Back button. (This is the default layout and cannot be changed.)
- The touch responsiveness is a little lazy. You have to wait some seconds before it starts working. (The online builder says it needs an ICS kernel for the touch version. We use the CM10 kernel (based on stock ICS one), but it's still lazy.)
CWM: http://www.mediafire.com/download.php?jz24eugrrr988f2
ODIN: http://www.mediafire.com/download.php?6vju9tlf9byeufe
TWRP v2.5.0.0: (Thanks to 'cooleagle' for the tip! )
- Built from the latest TWRP and CM10.1 sources.
- It has a lot of nice features, more than CWM does.
(For example:
- on-screen keyboard -> custom backup names
- built-in file manager
- built-in terminal)
- It has a fully touch-driven and very intuitive interface.
- The touch responsiveness is a little lazy. You have to wait some seconds before it starts working. (The online builder says it needs an ICS kernel for the touch version. We use the CM10.1 kernel (based on stock ICS one), but it's still lazy.)
Note: Backups of TWRP are said not to be compatible with those of CWM. For everything to work well, I recommend that you create a TWRP backup too before modding.
CWM: http://www.mediafire.com/download/8ibammwrtwrwo3d/TWRPv2.5.0.0_CWM.zip
ODIN: http://www.mediafire.com/download/pjxp5xhi96gtbvb/TWRPv2.5.0.0_ODIN.tar
PhilZ v5.06.6: (Thanks to Tha TechnoCrat for the tip! )
- Built from the latest PhilZ and CM10.1 sources.
- It has a lot of nice features, more than CWM does. Check here: http://forum.xda-developers.com/showthread.php?t=2201860
- Based on CWMv6.0.3.2
- Known issues: ADB Sideload
CWM: http://www.mediafire.com/download/4qz1g86oncn4foq/PhilZv5.06.6_CWM.zip
ODIN: http://www.mediafire.com/download/ixlxkh87s2lxbp9/PhilZv5.06.6_ODIN.tar
Stock GB recovery (XWLA4): (Thanks to xlm13x for this! )
- Use this if you want to return to the stock version.
CWM: http://www.mediafire.com/download.php?di4e3ms3qrxuapy
ODIN: http://www.mediafire.com/download.php?i4a1t7ntavvguu7
Stock ICS recovery (XXLQ7): (Thanks to xlm13x for this! )
- Use this if you want to return to the stock version.
CWM: http://www.mediafire.com/download.php?kg58rxmlnxkpkqv
ODIN: http://www.mediafire.com/download.php?pjn87j4fyjs34vt
If you want to install a custom recovery for the first time, you always have to start with an Odin-flashable package first. Flashing a recovery with Odin doesn't increase the download counter!
Tutorial (Flashing with Odin):
Please refer to the following thread (This is very detailed and good in my opinion): http://forum.xda-developers.com/showthread.php?t=1406664
Choose a downloaded TAR file (ODIN-flashable) for PDA option.
Tutorial (Flashing with CWM):
Note: This only works if you have already flashed CWM with Odin.
1: Reboot into recovery mode. Do this with a custom rom or by powering on your phone and pushing Volume UP+Home button simultaneously while the Samsung boot logo appears (you have to be fast).
2: Select 'Install zip from sdcard' menu.
3: Select 'Choose zip from sdcard' menu (or if you want to flash something from your internal sdcard, select 'Choose zip from internal sdcard' menu.) Note: On CWM v4.0.0.2, there isn't any separate menu for internal sdcard. It shows internal sdcard by default. External sdcard is mounted under the external_sd folder on the internal sdcard.
4: Navigate to the file you want and choose it.
5: Choose 'yes'.
6: Wait for it to finish and you're done.
Changelog:
08 July 2012: Initial release of v5.5.0.4 in old thread
09 July 2012: Added CWMv6.0.0.0 Touch (alpha)
17 July 2012: Added CWMv6.0.0.3
18 August 2012: New thread (this) created. CWMv5.5.0.4, CWMv6.0.1.1, CWMv6.0.1.1 Touch and TWRPv2.2.1.4 added.
30 August 2012: Modified CWMv4.0.0.2 (touchkey backlight, some init tweaks and smaller image) added.
2 September 2012: Stock GB (XWLA4) and ICS (XXLQ7) recoveries added.
10 November 2012: CWMv4.0.0.2 and CWMv5.5.0.4 reuploaded. CWMv6.0.1.5, CWMv6.0.1.5 Touch and TWRPv2.3.1.1 with new CM10 kernel added.
14 June 2013: CWMv6.0.3.2 and TWRPv2.5.0.0 added
16 June 2013: CWMv6.0.3.2 and TWRPv2.5.0.0 with USB Mass Storage fix updated, PhilZv5.06.6 added
Every custom modification to devices have risks. Flash these at your own risk!
Have fun and enjoy!

Dude, you're awesome
Sent from my Galaxy Nexus using xda app-developers app

Man thanks. you are the one who making Galaxy R known to the world. thanks again:angel:

wow you are rocking buddy :good:, thank's a lot just now flashed TWRP and its rocking........

Hey guys, sorry for the links being disabled. I've just received a mail about it. Dropbox thinks the links are generating too much traffic. Thank you for downloading so much! I'll reupload everything to somewhere else asap.
Sent from my GT-I9103

Adam77Root said:
Hey guys, sorry for the links being disabled. I've just received a mail about it. Dropbox thinks the links are generating too much traffic. Thank you for downloading so much! I'll reupload everything to somewhere else asap.
Sent from my GT-I9103
Click to expand...
Click to collapse
Thats means u r world famous buddy.. Bt we are waiting.. If someone need that one then we will ask in PM.
Sent from my GT-I9103 using Tapatalk 2

I think this should be stickied!:good:

The-Droidster said:
I think this should be stickied!:good:
Click to expand...
Click to collapse
Me too :good:

Update the OP!
@Adam...Now that this thread has been stickied it is best that you also add the attached CWM recovery v4.0.0.2 to the OP. This will make it a one stop thread for all recoveries for Galaxy R. Also please include a short tut about flashing these recoveries through recovery and ODIN separately!(With screenies if possible!)
One more thing, the attached v4 CWM recovery is ODIN flashable. See if u can make a CWM flashable version out of it as you did for other recoveries!
Thnx:good:

The-Droidster said:
@Adam...Now that this thread has been stickied it is best that you also add the attached CWM recovery v4.0.0.2 to the OP. This will make it a one stop thread for all recoveries for Galaxy R. Also please include a short tut about flashing these recoveries through recovery and ODIN separately!(With screenies if possible!)
One more thing, the attached v4 CWM recovery is ODIN flashable. See if u can make a CWM flashable version out of it as you did for other recoveries!
Thnx:good:
Click to expand...
Click to collapse
Thanks for the idea! I'll do it on tuesday (I'll arrive home then.) as well as I'll reupload everything to somewhere else as Dropbox has limits with file downloads. I may also add a flashable stock recovery if somebody wants to revert only the recovery.
Sent from my GT-I9103

Adam77Root said:
Thanks for the idea! I'll do it on tuesday (I'll arrive home then.) as well as I'll reupload everything to somewhere else as Dropbox has limits with file downloads. I may also add a flashable stock recovery if somebody wants to revert only the recovery.
Sent from my GT-I9103
Click to expand...
Click to collapse
Along with the stock recoveries of ICS & GB CWM flashable zips kindly try to add a Unroot CWM zip (ICS / GB separate if needed) so that everyone can just flash that zip & get unrooted if in any circumstances they can't flash the stock ROM via a USB if the port is damaged. This will serve as a way for people who have damaged their USB port to get unrooted, flash stock recovery & claim warranty for the damaged USB port.
pankaj88 has already made one but it doesn't remove the busybox so if possible try to make a zip which removes all the traces of the a rooted stock ROM.
You could start a new thread for it if you think it's needed as it is pretty useful & important.
Cheers !

Adam Now we are having ICS, so is it possible to rectify the touch Recovery bug (little lazy for few seconds) please.....
oops sorry i haven't read the OP fully, Ok now i understood because of kernel size you are not able to do it.....

UPDATE:
I updated the links, added CWM v4.0.0.2 and a short tutorial.
I'll get stock GB and ICS recoveries and add them in the following days (It depends on when I get them.)

If u want I can send u stock recovery images.
Sent from my Galaxy Royale using Tapatalk 2.

xlm13x said:
If u want I can send u stock recovery images.
Sent from my Galaxy Royale using Tapatalk 2.
Click to expand...
Click to collapse
It'd be really great! I think a GB and an ICS one is enough. Thanks in advance!

ICS Stock Recovery: http://d-h.st/Zgw
(extracted from XXLQ7)
GB Stock Recovery: http://d-h.st/M1R
(extracted from XWLA4)

This is great since I need to repack the stock firmware with CWM now just to get rid of the emmc bug.

xlm13x said:
ICS Stock Recovery: http://d-h.st/Zgw
(extracted from XXLQ7)
GB Stock Recovery: http://d-h.st/M1R
(extracted from XWLA4)
Click to expand...
Click to collapse
Added them to the OP.

can we flash through stock recovery
Sent from my GT-I9103 using xda app-developers app

kartiknnn said:
can we flash through stock recovery
Sent from my GT-I9103 using xda app-developers app
Click to expand...
Click to collapse
You cannot flash through stock recovery right now. Flash a one with Odin first, it'll not increase the binary counter.
Sent from my GT-I9103

[ROM][MOD] Lenovo A820

Dear Owners,
Discontinued
In this post you can find a multilingual (mainly European) modified rom for the smartphone Lenovo A820.
IMPORTANT NOTE!
The newer phones do not work well with S138 or older kernel (no info about S147).
The sympthom is that the touch screen works on inappropriate way: after the first screenlock it does not work again.
For this reason it is highly recommended that update your kernel if you have got this issue.
The kernel changer to S150 zip can be run from modified recovery (CWM, TWRP, COT, Carliv, etc...).
Note that all the things in this thread you do with your phone can be dangerous. I cannot take responsibility for your phone damage.
So, do it at your own risk.
Before you do anything, I recommend you to save your current ROM (I would say it is mandatory!)
There are many ways to save and I highlight some (links will be added later):
1, for non-rooted phones:
- SP_Flashtool, readback option.
- CWM (or TWRP) backup, if it is available on your phone
2, for rooted phones:
- MTKDroidTools backup
- command line dd-backup
In order to install this ROM, you need to have CWM recovery on your phone.
If you have not got this recovery or you do not know which recovery you have got, you have to read post#3 before you do anything.
If you get error during the installation of the ROM, see post#4.
The restore option of the CWM rcovery is not as good as it could have been expected, so please read post#4 carefuly for CWM restoration issues, tricks.
Update: CWM 6.0.4.0 with S150 stock kernel.
Just to clarify the power-on modes:
Normal phone mode: press the power button
Meta mode: VOLUME DOWN + POWER
Factory mode: VOLUME UP + POWER
Recovery mode: VOLUME DOWN + VOLUME UP + POWER
Consider the warranty issues, you need to backup you rom.
In addition, I always suggest to do a backup before install any new ROM to your phone.
You can do it with CWM recovery in backup menu.
About installation in general.
Pre-requisites: CWM recovery menu installed on your phone. (This ROM can be installed from CWM recovery.)
The ROM file must be saved on your physical SD card.
Enter into CWM recovery.
In CWM recovery you can go up/down with the volume up/down keys. The “enter” is the power button.
Choose the “install zip from SD card” menu item.
Choose the “choose zip from SD card” menu item.
Select the rom you want to install.
Choose “OK” in the menu item.
If you need a detailed explanation of its use, see the tutorial : http://bm-smartphone-reviews.blogspot.com/2012/02/complete-guide-to-clockworkmod-recovery.html
Right after the ROM installation has been finished, you can install gapps as well, before restart.
Windorws driver installation:
Please do not ask me about it. I use mainly Linux, which is more friendly.
What I did in XP under Virtualbox was:
Downloaded the Lenovo drivers from here: <link>
Manually added the com ports in control panel.
MOD CP4.0
V1
The modified rom has got the stock kernel - Lenovo A820_ydss_S135_130403
This completely changes your phone appearance, your Lenovo UI will be disappeared.
Also Lenovo applications are not integrated to this rom.
It will look like the stock Jelly Bean.
Main features:
-The firmware is rooted.
-Boot logo, boot/shutdown animations and sounds are changed to Lenovo.
-Minimalist appearance and content, for this reason you have to install google applications manually, from CWM recovery <link>. After gapps installation everything works well (many people wants to have mainly Google Play. It do work.)
-Slide unlock.
-Multilingual. For supported languages, see the screenshots.
-The default language/region is Hungarian, but you can easily choose your one.
Known bugs:
- I found was that the charging logo with turned off phone is not proper.
-the camera does not work adequately in video-camera mode.
-the default setting in some of the application is V987.
V2
The modified rom has got the stock kernel - Lenovo A820_S135_130403
The camera was changed to a non-multilingual one. It looked that the black screen in camcorder mode solved.
But after googleapps something went wrong... black screen again.
V3
The modified rom has got the stock kernel - Lenovo A820_S135_130403
In V3 there is not any significant changes (camera app was changed back to the multilingual one), but I modified the gapps, which caused the camcorder issue.
So, for this modified rom you need to use this gapps.
V3 download link: CP4.0-by-cappa72-v3 - dropbox
or
CP4.0-by-cappa72-v3 - 4shared
Bug: Still, the camera has got green lines in the case of playback.
CP4.1
V1
The kernel has changed to A820_YDSS_S130_130324.
The camera application does not generate green bands in playback.
The default language was set to English, default time zone was set to London.
CP4.1-by-cappa72-v1
You can use the googleapps mentioned for CP4.0-v3
CP4.2
V1
The kernel has changed to A820_S138_130419
CP4.2-by-cappa72-v1
Bug list
#3 - CP4.2-v1 - Wen try to choose themes, the laucher is Force Closed (FC) - Settings was modified to resolve this issue.
#4 - CP4.2-v1 - Serial number is 0123456789ABCDEF instead of the original S/N - not a real bug
#5 - CP4.2-v1 - Under the battery level of 15% the SystemUI is Force Closed (FC) - was a user error, when people deleted the necessary ui files.
CP4.3
This release will be the continuation of the 4.2, but with the newest available kernel (S150) and will (plan) contain all the things that are included in the 5.3.
This will not be with Aromainstaller and will contain the gapps.
Hopefully comng within two weeks.
MOD CP5.3
Available now (25.11.2013.)
CP5.3
V1
Change log; what’s new compared to CP4.2
Aromainstaller is used for optional installation possibilities.
- still Jelly Bean 4.1
- kernel is the stock S150
- Modified systemUI by [email protected] (1% battery signal; automatic hide function for non-used sim signal)
- Modified Settings by apeelme (sloving bug #3)
- Baseband is from the stock ROM S150.
- gps.conf is set to EU by default
- apns.xml is modified for Telenor-HU from “net” to “online”
- gps-tracker solver added to build.prop (dalvik.vm.execution-mode=int:fast)
- libvcodecdrv.so replaced to solve green bars in case of video playback.
- updated MobileUncleTools (2.9.5) in case of 3rd party SW.
There is no default ringtone set! Right after the installation you have to set the ringtone, message alert and so on... otherwise your phone will not play sound...
Important feature!
If you have already repartitioned with the script, you can simply install this ROM, it will recognise that the repartition had been done; and you do not have to run "disable internal SD card" script from CWM.
But please note that this function is onyl available with the repartition script; with Meteos rom editor repartitioning this function is not available.
Right after the installatio, there is not any sound set. Nor the ringtone, nor the message an alert. So, you have to set it first.
Available on mediafire : Link
md5sum: 86e241fcac6faf4fa6baf0f9cc4a18a0
Additional possibility:Change of FM radio
The FM radio can be changed back to Lenovo’s one with this script. It was requested by some people due to the fact that Lenovo’s FM radio can work without connecting the earphone.
The link is here. http://data.hu/get/6494163/FM-radio-change.zip
You can install it from CWM recovery, with the same method that you used during the installation of the ROM. This script does not affect any other part of the ROM, but the FM radio.
Repartition
Please DO NOT USE IT for Lenovo-based ROMs. Sometimes it can cause bootloop or other inconvenience.
The repartition of internal memory of the Lenovo A820 phone has been solved already.
With this action youd intednal SD card will be disappeared and will be added to the /data partition.
Before you do anything, make a CWM backup, and save all your data from internal SD card!
The easiest way is to use this CWM script, if you want to have the maximum available size (2,7GB) for the /data partition.
You have to install it from CWM recovery.
After the installation you need to do a factory reset.
After the factory reset, you have to disable your internal SD card, with CWM script.
And then, you can reboot your phone to check if yo have got the new size of /data partition:
settings --> storage
"internal data storage; full capacity 2,7GB"
"internal SD card; full capacity <your physical SD card capacity"
If the above data appear, you have successfully repartitioned you phone's internal memory!
If you want to have your data back, go into CWM recovery, and choose
backup and restore --> advanced restore --> <choose your save> --> Restore data
And then, your data are available again, after the reboot.
Please do not use it, if you do not want to have the 2,7GB of /data partition!
For Lenovo-based ROMs you need to use Meteos-apk for repartition of A820.
Internal/external SD card exchanger
If you want to use your physical SD card as the default one, and still want to use your emmc-SD card (aka internal SD card by default), you can change it by this CWM script.
Important link in summary:
The driver what works is here.
The original stock recovery is here
The autoroot package can be found here.
The preferred CWM is here.
The root script is here, you can install is from CMW, and your phone will be rooted.
The usable Flashtool is here.
The scattel file for Flashtool is here.
Credits:
bgcngm for the base of the ROM (BM1.0 for ZTE V987), and his amazing tutorials
iBotPeaches and brut.all for apktool
dsixda for his ROM kitchen which is really helpfull for easy-deodexing
Koush for his wonderfull CWM recovery
amarullz for his amazing AROMA installer
...and finally to all the devs whose apps, tweaks and scripts I have used on my custom ROMs

Very nice Thanks for your hard work and good luck

CWM recovery
Installing CWM on your phone
You need to install proper drivers to your computer.
Available (ported) CWM recoveries:
With newest kernel:
CWM recovery 6.0.1.2 - S150 - ported from [email protected] ZTE V970 recovery.
CWM recovery 6.0.4.0 - S150 - ported from [email protected] ZTE V967S recovery.
CWM recovery 6.0.1.2 - S138 - ported from [email protected] ZTE V970 recovery.
CWM recovery 6.0.1.2 - S135 - ported from [email protected] ZTE V970 recovery.
Option 1, with SP Flashtool
Download the SP_Flashtool software to your computer. Extract it to a directory, where you want to run it from.
Download the scatter file, which you will need if you want to use SP_Flashtool.
Download the CWM
(5.5.0.4, 6.0.1.2, 6.0.2.8; it is your decision)
Run the SP_Flashtool.
Browse your scatter file.
Choose only the recovery.
Tick the “DA DL all with checksum” (you can find it close to the download button). It is a really important point!
If your phone is connected, let’s disconnect it from the computer.
Turn off your phone. Take the battery out from your phone for 5 sec. Insert the battery to you phone. Keep it still turned off.
In the flashtool press the Download button.
Choose OK to the warning message.
Connect your phone to the computer.
The flashtool will flash the recovery into your phone.
When the green circle appears, wait for 5-10 secs, and the unplug your phone.
If everything went well, you can enter into the recovery menu (see 1st post, power-on modes)
Option 2, on rooted phone, with MobileUncleTools.
Install MobileUncletools 2.8.x or higher from the Play Store.
Save one of the CWM I linked to the root directory of your physical SD card.
- select menuitem Recovery Update. The program will list the available recovery images.
- choose the one, what you want to install
- It asks back: "Are you sure flash recovery!" - Use recovery file: <name of the recovery what you choose previously>. Tap to OK.
- After the flashing process it offers you to reboot into recovery. If you tap OK, it will automatically reboot your phone to recovery. If you tap cancel, you can use your phone as a phone.
- Before you tap to "reboot to recovery", I suggest you to wait approx. 5-10sec.
Use of the CWM.
If you enter into the CWM (6.x.x.x) recovery, the following buttons can be used:
- Power button : “enter”
- Volume down : step down in the menu
- Volume up : step up in the menu
- Soft key “option”: step down in the menu
- Soft key “back” : step back in the menu
In 5.x.x.x you cannot use soft keys, but the physical buttons works on the same way as in the case of 6.x.x.x
CWM restoration
I experienced failures in restoration of the CWM backup.
This was a real surprise for me because I have not faced this issue with other MTK phones.
So, the issue is that the CWM restoration does not work immediately.
In details:
-I saved the stock rom by CWM 6.0.1.2 (CWM was complied by Bruno, and I modified it for A820)
-For checking the restore function, I did a factory reset: the phone stopped working.
-I did the CWM restoration, but still the phone stopped at the boot animation. And stayed it for 15min. I removed the battery then.
In order to solve the issue, the following method was done:
-In the advanced restore I choose the restore /system (only!)
-After restoring the /system I turned off the phone took the battery out, waited 5 secs, inserted the battery back.
-Turning on the phone it worked again with the restored data, BUT the internal SD card was injured! I formatted the internal SD card – with this action I lost all my data that were saved on the internal SD card.
So, please be careful using it! Save your internal SD card data before the CWM restoration!
This was experience in case of all the available CWM (5.5.0.4, 6.0.1.2, 6.0.2.8).

Installation issues
Post#4 troubleshooting
If you cannot install the ROM by an error:
Code:
assert failed: getprop("ro.product.model") == "Lenovo A820"
E:Error in /sdcard/Lenovo-a820-update-CP4.0-v1.zip (status 7)
This is a safety feature, not a bug.
This error message is a warning that you have not got the proper CWM. (Most of the available CWMs are based on ZTE, STAR phones and contain improper model description.
My CWMs contain the proper one, I modified them, so you need to install a CWM I mod for Lenovo A820.
In this case you have to update your CWM to a ported one that I did.

Great!
I would love an multi lingual rom, but for now I just want to root it. (ones it gets delivered that is)
Are there tools specific for this device to root is with out flashing?
Checking out your rom in the meantime. :fingers-crossed:

ebsbow said:
Great!
I would love an multi lingual rom, but for now I just want to root it. (ones it gets delivered that is)
Are there tools specific for this device to root is with out flashing?
Checking out your rom in the meantime. :fingers-crossed:
Click to expand...
Click to collapse
If you have got CWM recovery on your phone (or a chinese one that has got "xx SD yyy ZIP" menuitem), then you can use root-zip, installing it from CWM recovery.

Thanks

Thanks
Where are the screenshots?

please add some screenshots.

deathhand said:
please add some screenshots.
Click to expand...
Click to collapse
I tried to upload some, but the server was down that time.
I will try it again tomorrow.

Thanks for this rom, I flashed it succesfull on the Lenovo A820, it also takes away that terrible skin from Lenovo.

Gapps link
Thnak you for your ROM. I tried it for a couple of hours and there some minor problems that I don´t know if there are rom related.
1. There is no link to the gapps, so I downloaded a random one and I have errors with google search.
2. The videocam record with a green band on one side.
3. The gps is slow, doesn´t pick satellites easily.
4. If you choose automatic time the it always consider that you´re in china. If you choose manually your timezone then it is ok.
Overall it is a very well-done rom and I would keep it for daily use.
Thanks

1. Are you sure you downloaded the Gapps for Android 4.1.x? You should have this gapps version: gapps-jb-20121011-signed, this the right version you should flash. I first flashed the rom and after that the gapps.
I have reproduced your issue and you need to update the Google search app in the playstore, after that the errors are gone.
2. I have reproduced what you reported, I want to try if I can grab the original camera app from Lenovo and see if it still has the issue, but I don't think its a big problem, I bought the phone for someone else, but this issue is not to big, I don't suppose people often record with an smartphone and this rom at least got Dutch in, the original phone firmware was bloated with China Unicom bloatware, Lenovo skin and had no Dutch support.
3. Try GPSfix, ussualy this kinda works, but the MT6577 chip was know for having GPS problems, perhaps its the same with MT6589? But there are many apps out there that can help you fix it.
I think this in a great rom, Lenovo is a big brand in China, so many will choose Lenovo and with this rom you get rid off the terrible lephone skin, I mentioned this rom in my review about this phone
Oh here you got some screenshots.
Feel free to use them in the OP.

Don't know about you but I do use my device a lot for video recording.
I think it is imperative that all basic functions work flawlessly.
The custom rom's with android 4.2 also have an video bug at this time, which is a bit unacceptable.
I'm sure it will be sorted out :victory:

Well yes, but having fully Dutch support is better, you can always flash new update off the custom rom when it get fixed. I only recorded a few time video with my own smartphone.

Lebrija said:
Thnak you for your ROM. I tried it for a couple of hours and there some minor problems that I don´t know if there are rom related.
1. There is no link to the gapps, so I downloaded a random one and I have errors with google search.
2. The videocam record with a green band on one side.
3. The gps is slow, doesn´t pick satellites easily.
4. If you choose automatic time the it always consider that you´re in china. If you choose manually your timezone then it is ok.
Overall it is a very well-done rom and I would keep it for daily use.
Thanks
Click to expand...
Click to collapse
1, I have added the link.
2, Thanks for the feedback, it is really useful to know. The playback contains the green band, the file itself does not.
I changed the kernel to the '130'-one, and now it works with the camera application, and the playback is also correct.
3, You shall try the EPO / A-GPS support for getting it better. Or thy DexterMorganNL's suggestion.
4, I have never faced this issue, but in the new version I set the default time zone to London.
The new one is available, you can see it in the first post.

cappa72 said:
1, I have added the link.
2, Thanks for the feedback, it is really useful to know. The playback contains the green band, the file itself does not.
I changed the kernel to the '130'-one, and now it works with the camera application, and the playback is also correct.
3, You shall try the EPO / A-GPS support for getting it better. Or thy DexterMorganNL's suggestion.
4, I have never faced this issue, but in the new version I set the default time zone to London.
The new one is available, you can see it in the first post.
Click to expand...
Click to collapse
Thank you for your time. I will try the new version. But, why have you used an older kernel?
By the way, with version 3 I also had some problems with the gyroscope when playing Real Racing 3.
Great work

Its great you released the update so fast, you brought us really good work. I think new owner off this phone is going be thankful, they requested me to buy a phone for them while I'm in China, and when I got it it was not fully Dutch supported, had the terrible skin.
So its great have this phone, because this way I can deliver it without the Chinese bloatware and with full Dutch language and ofcourse Google apps.
EDIT
The newest release gives me a black screen after I boot it up after having it flashed, so I have reverted back to your previous release.

OK. I'm ready to weep.
I've previously had a ROM from NeedRom on my A820.
I'd like to give Cappa's ROM a try, but when I try to install from CWM Recovery I hit the Error outlined in Post 4.
I then follow the advice of Post 3... But there are no links to A820-compatible CWM Recovery installations. I found one on a hungarian site linked to Cappa, but all I get is a .img file and no idea how to get that on to my phone.
Can anyone post detailed instructions, or send me to a page (in English) where I can find instructions on how to get the ball rolling so I can use Cappa's ROM?
Thanks.
Google is my friend. Yes. But Google Translate isn't.

TheTen said:
OK. I'm ready to weep.
I've previously had a ROM from NeedRom on my A820.
I'd like to give Cappa's ROM a try, but when I try to install from CWM Recovery I hit the Error outlined in Post 4.
I then follow the advice of Post 3... But there are no links to A820-compatible CWM Recovery installations. I found one on a hungarian site linked to Cappa, but all I get is a .img file and no idea how to get that on to my phone.
Can anyone post detailed instructions, or send me to a page (in English) where I can find instructions on how to get the ball rolling so I can use Cappa's ROM?
Thanks.
Google is my friend. Yes. But Google Translate isn't.
Click to expand...
Click to collapse
Update, I think I sorted it...
Bit of imagination (and could have totally done the wrong thing, but it seems to be making progress...)
I decided to take a known ROM install that I've tested and that works, which has a recovery.img included, and I renamed the recovery.img to recovery_bak. I then renamed my 'new' CWMRecovery image to recovery.img and dumped it in the directory with the ROM data that I got off NeedRom. I loaded up SPFlashTool and loaded the scatter file from that ROM, then deselected every component except 'recovery' and flashed it.
End result is that I have a phone which recovery-boots to the version 6 cappa-modded CWMR which I found on the Hungarian site, and in turn that CWMR has just installed both the required ZIP updates outlined in Post 1, and Cappa's ROM is now sat on my second A820 awaiting setting up...
I hope I did the right thing, and this won't come back to bite me in the ass later... The newer recovery.img was slightly larger than the old one, but I'm assuming that the scatter file isn't about storing specific pieces of the ROM in specific places based on exact size of file, and thus perhaps all things will continue to work swimmingly.

[DEV][WIP][RECOVERY][TWRP 2.7] TWRP Touch Recovery for Samsung Galaxy S Duos[ALPHA 1]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
DOWNLOAD:
Latest Release
INSTALLATION
Power off your Galaxy S Duos
Get into Download mode by pressing Volume (-) + Home + Power Keys followed by Volume (+) to Confirm.
Step:1 - Press "PDA" button and choose the filerecovery.tar.md5 !
Step:2 - Press "Start" button under Execution.
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.
Credits-
@coolamit for testing.
XDA:DevDB Information
TWRP - kylexx, Tool/Utility for the Android General
Contributors
v_superuser
Version Information
Status: Stable
Stable Release Date: 2014-04-21
Created 2014-04-21
Last Updated 2014-08-18

Note - There might be some things broken, you need to keep calm.
Also, you need to install with the update package from codename13. (Thanks to @coolamit )

Man this recovery almost screw up my phone. for no reason from a certain point the restored backups doesn't boot anymore, stuck at Samsung logo, tried making other backups, reflash twrp, first cwm then twrp but nothing.
The only one working was AN old backup of a week ago, restored that.
I can't use this if it isn't 100% reliable sorry

holymoz said:
Man this recovery almost screw up my phone. for no reason from a certain point the restored backups doesn't boot anymore, stuck at Samsung logo, tried making other backups, reflash twrp, first cwm then twrp but nothing.
The only one working was AN old backup of a week ago, restored that.
I can't use this if it isn't 100% reliable sorry
Click to expand...
Click to collapse
What else do you expect from an Alpha build? :/

v_superuser said:
What else do you expect from an Alpha build? :/
Click to expand...
Click to collapse
ok, I will wait for a more stable version, I like this recovery specially for the compression of backups that saves a lot of space

Awesomee and good work sir ...
can weget for ldpi devices like galaxy pocket,y etc phones ..?? in zip format

Does anyone know if it also works on ace 2x?
Sent from my GT-S7560M using XDA Premium 4 mobile app

Need help for s duos
do you have still s duos and could you please tell how to fix the animation problem in cm11 4.4.4 for s duos( in your cm11 there is no such problem)

I just installed sucefully, but when boot in recovery mode, just hang up.... therefore, the phone boot normally... well, I also lost the root

Not booting in TWRP. Getting restarted every time I am trying to boot with VolUP+Power+Home. If I hold the keys it keeps rebooting, and if I release it boots to system.
If I execute the command from terminal
Code:
adb reboot recovery
it boots into Samsung stock recovery.
Also showing a yellow symbol (!) while booting.
Should I flash it to stock recovery image?
Or is there any other way out to update the recovery to TWRP?

Solved
Thanks to KlinkOnE and m4jonez.
First I installed (ROOT) Rashr - Flash Tool from Play Store as suggested in the post.
Then downloaded Recovery - TWRP 2.8.0.1 and Recovery - TWRP 3.0.2 as mentioned here .
Placed both of the .zip files in the internal memory.
Now I open Rashr and flashed the recovery selecting the .zip file of TWRP 2.8.0.1 (My phone is rooted, so Rashr was able to flash it). Then rebooted to TWRP. But, failed. Removed the battery and insert it again. Now with Vol + Home + Power key, booted the phone in TWRP. From TWRP installed the TWRP 3.0.2. Rebooted to TWRP. It works fine now.

hcp006sl said:
Thanks to KlinkOnE and m4jonez.
First I installed (ROOT) Rashr - Flash Tool from Play Store as suggested in the post.
Then downloaded Recovery - TWRP 2.8.0.1 and Recovery - TWRP 3.0.2 as mentioned here .
Placed both of the .zip files in the internal memory.
Now I open Rashr and flashed the recovery selecting the .zip file of TWRP 2.8.0.1 (My phone is rooted, so Rashr was able to flash it). Then rebooted to TWRP. But, failed. Removed the battery and insert it again. Now with Vol + Home + Power key, booted the phone in TWRP. From TWRP installed the TWRP 3.0.2. Rebooted to TWRP. It works fine now.
Click to expand...
Click to collapse
pls help i'm new to the whole rom flashing thing. i tried what you wrote but the Rashr dosnt seem to find the TWRP both in my phone and external memory. i tried it on both core prime (SM-G360H) and (GT-I9060). i rooted both with kingroot via pc. thanks in advance for your assistance.

digitzonline said:
pls help i'm new to the whole rom flashing thing. i tried what you wrote but the Rashr dosnt seem to find the TWRP both in my phone and external memory. i tried it on both core prime (SM-G360H) and (GT-I9060). i rooted both with kingroot via pc. thanks in advance for your assistance.
Click to expand...
Click to collapse
I don't think this TWRP is for those two models - Core Prime and Grand Neo. Please download TWRP for your phone.
For GT-I9060 follow the thread [RECOVERY][GT-I9060] TWRP 2.8.0.1 touch recovery [UNOFFICIAL] and you can download the TWRP recovery for I9060 from here -Mod edit link removed ppc
For SM-360H follow the thread [Recovery] Official TWRP SM-G360H.
Please don't use king root for rooting. If you have used, replace it with SuperSU. Super-Sume Pro is the app that replaces KingRoot by SuperSu.

[ROM][MM 6.0.1] [ KatKiss - KatshMallow #034 ] [MultiWindow]

{
"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"
}
KatKiss ROM
MarshMallow 6.0.1 ReleaseAsus TF101
Please note that this version is made for and tested on the TF101 model.
This rom is an aosp based rom with my own additions on top of it.
The main motto of the rom being Kiss. Even though the Meerkat could give you a kiss, it stands for Keeps it Sweet and Simple too
Which means that just like the other K.A.T stuff, the rom's main goal is efficiency, speed/res ponsiveness,
while not adding bloated features that will slow things down 
DOWNLOADS:
Latest Rom Version: KatKiss-6.0_034.zip | Mirror
[*] Gapps: opengapps pico
SuperSU: SuperSU BETA 2.52
Sound improvements & gps quick fix : K.A.T App
SL101 Compatibility Pack: KatKiss-6.0-sl101-compat-V5.zip (To flash after the rom for the Asus Slider SL101 only, DO NOT flash for the TF101 model)
Install Instructions:
These builds are designed to be installed with a recent recovery.
TWRP 2.8.1 is recommended: available here
Older versions of TWRP like 2.3.x won't work.
Backup everything !
Go to recovery
[*]The first time you install: Format /data (full wipe doesn't format)
(you can skip this step if you're already on the same main version of KatKiss, if ever you encounter a problem redo a full clean install and format /data and try again before reporting )
Then *EVERYTIME* flash (all together):
rom zip
SuperSU zip
[*]gapps zip
Wipe cache/dalvik
Reboot
Rom Main Features:
MultiWindow Support with 2, 3 or 4 panes setup
High speed and responsive oriented
High performance and overclocked KatKernel included
Dock keyboard Support with full special/function keys support
Global Keyboard Shortcuts / KeyOverride Macro association (See post #2 for more info)
HDMI Support
Battery Level Indicator & Dock Battery support + Mods (icon/Text/%)
CIFS, ext4, NTFS, ExFat support
RRO Theme Engine - Themes & more info
Native Android FSTRIM + Manual scripts for Database optimization and fstrim (see post #2)
Media Scanner Filters
Navbar with left, balanced (PixelC like) or middle aligned buttons.
All Wifi channels support
Integrated cpu & io performance settings panel
Custom Navbars buttons long press actions
Advanced power menu with reboot options.
User Immersive mode and actions with automode when docked setting
Advanced per application permission management (AppOps)
Ethernet-auto support
Misc utils Busybox, rsync...
Custom Quick Settings tiles
ChangeLog: http://public.timduru.org/Android/KatKiss/6.0/ChangeLog.html
Rom Source: https://github.com/timduru (branch katkiss-6.0)
Credits:
Original banner concept by i9apps, Bootanimation by mgeniusm, original drawing by BBF
Chainfire for SuperSU
WebPage
How to report
What to include in the report
Disclaimer: The usual
Use at your own risk, I won't be responsible for any damages caused to your Transformer or to yourself.
In most cases if something breaks, flashing a rom on top should fix it.

XDA:DevDB Information
KatKiss-MarshMallow, ROM for the Asus Eee Pad Transformer
Contributors
timduru
Source Code: https://github.com/timduru
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 2.6.x
Based On: AOSP
Version Information
Status: Stable
Created 2016-02-19
Last Updated 2018-10-19

Tips
First Install
Make sure you do a format /data the first time you install the rom
(backup your internal storage first if you want to keep something)
The first boot after a rom flash can take a few minutes as ART is slower than dalvik to optimize the applications, but is faster after the 1st time.
(First boot takes ~4-5 minutes without gapps and 10+ minutes with gapps)
Also keep in mind that after a fresh install, it might take a bit of time to get up to full speed as media scanner & google are checking/scanning and restoring stuff.
Bluetooth
Bluetooth might require to be turned on twice before it scans and displays the available devices.
Wallpaper Modes
Different Wallpaper modes have been added in Settings => Display
** Normal (regular android mode)
** Disable System Wallpaper rendering (set as default)
** Disable Wallpaper service
2nd setting will prevent the wallpaper being rendered by the system making things faster and also freeing resources
That's the recommended setting you want to use if you are using a launcher that has internal wallpaper rendering
The Default included Launcher3 has internal rendering
For Nova: Go to its Settings => Desktop => Wallpaper Scrolling => Force, then set a wallpaper.
(You will see a black wallpaper if you're not using a launcher that can do internal rendering, If wallpaper is important and that you want to keep your current launcher, then switch back to the 1st setting)
Youtube
Depending on your network and tablet load, 720p videos might not play or take longer to buffer.
Switch to 480p in that case.
Some videos are also 720p60fps so you might need to switch back to 480p for these too.
You can also try an older youtube version and disable auto updates: youtube-v5.0.21
Google Play Movies
Our current Widevine DRM libs are not compatible in MM.
So you can't play a movie on the tablet with Google Play Movies as it requires that.
Starting a movie to play on chromecast should be fine as the drm will be the chromecast one in that case.
Now On Tap
Now On Tap requires the nano opengapps version, however our default /system partition is too small to accommodate them.
So if you want to install the nano or bigger opengapps version, you'll need to repartition the storage space first using Bigwheelie for extended partitions
Then activate Now on Tap from google now settings
Hardware keyboard layouts
More languages have been added in the default asusec keyboard
Set the keyboard layout through Settings => Language & Input => asusec => setup keyboard layouts
These also allow live switching without reboot with ctrl + space
Global Key Override/Shorcut Mecanism
Available in Settings => Dock => Add Key Override Actions
This will allow you not only to redefine function keys assignment, and other special keys actions,
but you'll also be able to assign global macro actions / app launch to any key + Meta key combination (shift Left or Right , ctrl..)
You can also add multiple actions to one key combination, simply click again on the "+" button for the same key combination.
For example if you want to assign to one key combination a list of action to run before going to bed for example, like: turn wifi off, Bluetooth off, mute sound, and turn screen off, you can do that
Note that starting multiple applications with one key is kinda a miss and hit for the moment due to some mecanism in android that seems to prevent applications to start too close to each others.
Storage (fstrim) and Database optimization:
Fstrim is native since 4.3 and will happen in the background if your tablet is idle / sleeping and that your battery is > 70%
There is also a script to run it manually in the rom: /etc/kat/optimizestorage
To optimize the Database: /etc/kat/optimizedb
To run both, open a terminal and run:
su
/etc/kat/optimize

MultiWindow
Multiwindow allows you to split the screen in 2, 3 or 4 panes
you can switch an app back and forth between multiwindow mode and regular mode while it's running
NavBar:
- To switch between full screen and split View you can use the
NavBar Buttons
The app that currently has the focus (or the latest used app if you're on the Desktop) will be used for the main pane (left and/or top depending on the mode and rotation)
And it will lay the remaining most recently used apps in the rest of the available 1-2-3 panes depending on the icon you click
- If you press a multiwindow icon again when in splitview mode, it'll bring the focused app back to fullscreen mode.
- To swap the 2 latest focused apps location / pane , long press on the
NavBar Button
- To change focus simply Tap on the app or use the
NavBar Button
That button can also be used in non multiwindow mode to switch quickly between the 2 most recent apps.
Global Actions:
Actions to switch the app between fullscreen / splitview 2-3-4 panes, swap, or switch between the 2 most recent apps have been added
so you can bind them to a key / key combination with the Global KeyOverride or long press on navbar button too.
Note: Most apps works ok in splitview mode, but some of them might crash or not refresh correctly sometime.
To manually position an app in one of the pane:
For the moment either reorder your apps before clicking on an auto mode icon,
or you can also activate the default Marshmallow Multiwindow mode to get extra icons to positions an app in a specific pane (activate it in developer options )
Then position the apps with the icons from the Recents screen. (default MM recents icons are for 2 or 4 panes)

Banners

First
Many thanks, Tim, for keeping the Tf101 alive!

I'm a little afraid to try, but I know I will
Officially my Transformer is one of the oldest devices I own and should really show its age.
But it just doesn't, it sets itself apart from the two other Tegra 2 devices (Notion Ink Adam and Acer Iconia) by being a thoroughly enjoyable device, which reacts very promptly to all input and still is mechanically perfect with great battery life.
Some hardware ingredients like DRAM and Flash seem to be made of better stuff (some benchmark show twice the memory bandwidth than Acer Iconia and NI Adam and the eMMC is lots better than Acer (Adam is notoriously terrible)), but mostly it must be the constant tweaking you (and Google?) have put in, because the performance only got better and better, even if the applications typically got fatter and fatter and 1GB of DRAM is no longer as plenty as it used to be with Android 2.2.
I surely can't say the same for my Nexus 7, which started being somewhat snappier than the Transformer and turned out pretty bad with LP even after turning off the journalling on ext4.
Marshmallow has disappointed me so far (only Nexus 10 migrated yet), mostly because my standard launcher SPB shell 3D no longer works on it and I just like it better than stock or any other.
And then I just don't see any significant improvements beyond Lollipop or rather CM 12 with all the privacy stuff already included. And I just love the fast task switching, which is part of the multiwindow support and which I have on a keyboard shortcut (hope it comes soon).
Somehow I also doubt that Nougat will be better in any sense except "better" Google integration.
But since I'm very much afraid of operating anything without the latest security patches, I'll just have to make the switch.
And I'm sure it will be as perfect as the current LP by the time Nougat comes out.
Thanks Timduru for making it possible

Link is ready, downloading :good:

Thank you. what I've failed to understand, do you need to install a separate root tool? Or is it included in the recommended recovery tool? It's still as i bought it in 2011... Thanks!

Thanks so much Tim gonna test this out

cwouter said:
Thank you. what I've failed to understand, do you need to install a separate root tool? Or is it included in the recommended recovery tool? It's still as i bought it in 2011... Thanks!
Click to expand...
Click to collapse
Just follow the procedure from the 1st post:
once you have the recovery installed:
the first time: format /data
then install all 3 zips at once: rom + supersu + gapps
then reboot.

Thank you Tim! Awesome as always. Gonna try ASAP.
One question...
What is the downside of not having omx codecs working?

xbs said:
Thank you Tim! Awesome as always. Gonna try ASAP.
One question...
What is the downside of not having omx codecs working?
Click to expand...
Click to collapse
No omx codecs means no gpu video acceleration, so it'll use cpu to decode instead.
Wait a bit before trying, 019b is coming fixing the reboots with some apps

New Version #019b
New rom version available: KatKiss-6.0_019b.zip
ChangeLog:
TF101:
- Fix reboots caused by some apps(ES file explorer, play music, youtube...)
- Fix ExFat support
TF101 KatKernel 122:
- net: Handle 'sk' being NULL in UID-based routing
- add native ExFat FS support

timduru said:
Just follow the procedure from the 1st post:
once you have the recovery installed:
the first time: format /data
then install all 3 zips at once: rom + supersu + gapps
then reboot.
Click to expand...
Click to collapse
It sounds so easy... First I don't really know how to install the recovery (hence, i have been spending 'only' app 7 hours on topic by now). I would assume from PWR+VOL- then Vol+ goes to recovery mode, but the device gets stuck with a android red expression mark. I then tried to install the Easyflasher 0.8.3 and managed to first delete the drivers and installed new universal ones. Rebooted and continue to follow the procedure and the Easyflasher on my Windows tells me i have successfully unbricked my Asus Stock. However, when i reboot, it looks all exactly the same, no data lost, no new installation. Then I could, or should?, flash a recovery. However, if i try to do it from the Easyflasher there is only the old TWRP 2.2.1. available and i fail to make use of the downloaded TWRP 2.8.1.1. CLick the Root, doesn't work either.
Then, the frustration goes up and the progress goes down... please advise and push me in the right direction! MUch appreciated!

cwouter said:
It sounds so easy... First I don't really know how to install the recovery (hence, i have been spending 'only' app 7 hours on topic by now). I would assume from PWR+VOL- then Vol+ goes to recovery mode, but the device gets stuck with a android red expression mark. I then tried to install the Easyflasher 0.8.3 and managed to first delete the drivers and installed new universal ones. Rebooted and continue to follow the procedure and the Easyflasher on my Windows tells me i have successfully unbricked my Asus Stock. However, when i reboot, it looks all exactly the same, no data lost, no new installation. Then I could, or should?, flash a recovery. However, if i try to do it from the Easyflasher there is only the old TWRP 2.2.1. available and i fail to make use of the downloaded TWRP 2.8.1.1. CLick the Root, doesn't work either.
Then, the frustration goes up and the progress goes down... please advise and push me in the right direction! MUch appreciated!
Click to expand...
Click to collapse
Installing the recovery is not really the focus of this thread, and it has been a really long time since I installed on mine
But what I would do, since you seem to have easyflasher and drivers working:
- Install TWRP 2.2.1 from easyflasher
- reboot to that TWRP 2.2.1
- Install the TWRP 2.8.1.1 flashable zip from TWRP 2.2.1
- reboot to the recovery and it should now be TWRP 2.8.1.1

Flashed all 3 zip ROM+su+pico but can't boot to Android.
After the Asus logo screen turns black and nothing happens.
Any ideas?

xbs said:
Flashed all 3 zip ROM+su+pico but can't boot to Android.
After the Asus logo screen turns black and nothing happens.
Any ideas?
Click to expand...
Click to collapse
sounds as if the new kernel didn't flash or something.
What recovery are you using ?
Even if the screen goes black you should get adb working after a few minutes, it's still doing things in the background normally.
Try to grab me a logcat + dmesg at that point.
EDIT: Found the problem, yeah kernel not flashing:
Flash it separatly for the moment: Tim_KatKernel_122_MM6.0.zip
that will be fixed in the next version.

xbs said:
Flashed all 3 zip ROM+su+pico but can't boot to Android.
After the Asus logo screen turns black and nothing happens.
Any ideas?
Click to expand...
Click to collapse
Unfortunately me too.
The only step from install note was the "Format" because of lack of time and data cable to copy everything from internal sd to my pc (only way for me is over the air with My Phone Explorer right now).
Tried 19 & 19b together with SuperSu 2.52 and gapps-arm-pico in one flash.
Backlight of screen is on, but then nothing happens over an hour.
---------- Post added at 13:46 ---------- Previous post was at 13:45 ----------
timduru said:
sounds as if the new kernel didn't flash or something.
What recovery are you using ?
Even if the screen goes black you should get adb working after a few minutes, it's still doing things in the background normally.
Try to grab me a logcat + dmesg at that point.
EDIT: Found the problem, yeah kernel not flashing:
Flash it separated for the moment: Tim_KatKernel_122_MM6.0.zip
that will be fixed in the next version.
Click to expand...
Click to collapse
Will do immediately!
---------- Post added at 14:00 ---------- Previous post was at 13:46 ----------
Just booted fine, into MM

New Version #019c
New rom version available: KatKiss-6.0_019c.zip
ChangeLog:
TF101:
- Fix Kernel not being installed

timduru said:
Installing the recovery is not really the focus of this thread, and it has been a really long time since I installed on mine
But what I would do, since you seem to have easyflasher and drivers working:
- Install TWRP 2.2.1 from easyflasher
- reboot to that TWRP 2.2.1
- Install the TWRP 2.8.1.1 flashable zip from TWRP 2.2.1
- reboot to the recovery and it should now be TWRP 2.8.1.1
Click to expand...
Click to collapse
Sounds like a plan, i tried and Easyflasher tells me it runs Wheelie,NV Flash then 'finished new reboot into recovery'. I do so, but android gets stuck in the recovery with an red expression mark, then it'll boot normal again.
Might it be that root access is blocking it? The Easyflasher root access tells me to first falsh recovery and put the superuser on sd.
I have installed both TWRP and SuperSu but both run into issues: the first tells me 'root is required' then closes, the second tells me 'no SU binary installed' then closes.
I then decided to go for a very crappy 1-click root access, see http://forum.xda-developers.com/showthread.php?t=1689193, with an even worse http://www.4shared.com/postDownload/ja5cFLAL/1-Click_Transformer_Root_11.html. This seems to have succeeded and i got root access (!) and the above described issues on TWRP and SuperSu were not gone.
Then in TWRP i couldn't select the zipfile TWRP 2.8.1, and after telling TWRP i had a TF101 i could select an older version like 2.3, which he was going to download. I had to confirm a path but decided to abort. I then tried to boot recovery but unfortunately, and not as i expected, it run into the same red expression mark. I then decided to run APX mode again and see if easyflasher could access root now. Also negative. Then run normal ABD mode and checked if i could do something with SuperSu, also negative.
So it seems my problem is that TWRP doesn't allow me to select the right zip file and as a result i can't run any recovery... any idea?
UPDATE: going back to apx flash the default TWRP2.2.1 then reboot to recovery succeeds in Easyflasher but the same red expression mark with Android. so also negative

Database Info

welcome