[RECOVERY] Cannibal Open Touch Recovery for ZTE V967S - Miscellaneous Android Development

DISCLAIMER:
Rooting your phone and using custom Recoveries and ROMS have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledges about phones and phones utilities too.
Make sure that whatever you do, you are doing it at your own responsibility.
UPDATE:
I updated the recovery to a new version, more stable, with CWM 6.0.4.4 basic structure (updated by me).
After a hard work with many failed builds, I succeded to compile from source a fully working recovery with touch support for ZTE V967S. I used for this the Project Open Cannibal source, named Cannibal Open Touch Recovery. It's a well done recovery, compatible with CWM, with usefull functions: for example advanced backup - you can backup only that partition you want, posibility to use themes, etc.​
Here you can see more images of the recovery, from a device with smaller screen, but you can check the options.
Touch navigation is made by touching bottom buttons menu, just like in Philz recovery or similar. First button is for exit or go back, second is key down, third key up and last is select or enter. Now you can save your phone buttons.
You should read this:
First time you boot in recovery will be a touchscreen calibration set up: you have to touch three times the red square. Also, first time you do a backup, it will take a little longer time, because it will be create directory structure and free up the space. After that it will be a joy, is fast, is powerfull, is full of options and is funny.​
CREDITS:
Project Open Cannibal who release and mantains this wonderful recovery.
Sblood86 for his help.
C3C076 for his help on tweaking recovery source.
bgcngm for his unpacking tool.​​Download from attachment.

Deleted.

Need your Help Master
Great to Have you Master in our MTK Community.
Today as master @yuweng told us try to port this recovery to our MT6577 Device with his auto port tool, but I failed doing so with that tool. So master will you assist me in doing these things for my device. I don't have a linux system and neither my Lappy is accepting it in any form, not even on VM.
My Device Info:-
Micromax A110
Resolution :- 480*854
MT6577 Device with JB 4.1 & 4.2.
Will please help in this. As I failed in philz recovery. So asking for your help here in this recovery also.
Thanks a ton for your time and for this awesome recovery.

BOND1987 said:
Great to Have you Master in our MTK Community.
Today as master @yuweng told us try to port this recovery to our MT6577 Device with his auto port tool, but I failed doing so with that tool. So master will you assist me in doing these things for my device. I don't have a linux system and neither my Lappy is accepting it in any form, not even on VM.
My Device Info:-
Micromax A110
Resolution :- 480*854
MT6577 Device with JB 4.1 & 4.2.
Will please help in this. As I failed in philz recovery. So asking for your help here in this recovery also.
Thanks a ton for your time and for this awesome recovery.
Click to expand...
Click to collapse
Thanks for appreciations,
This recovery is underestimated by users, but is very good. Only one thing, is dependat on display resolution. For your device this is not gonna work. Try this one here. I did it for yuweng to test his device (Ihope he will not be upset). But don't use the port tool. Instead, unpack it with michfood tool, change in ramdisk my files with yours from original or a working recovery (recovery.fstab from dev folder, and from root all files that are not for your phone except init executable), repack it and see if it works.

carliv said:
Thanks for appreciations,
This recovery is underestimated by users, but is very good. Only one thing, is dependat on display resolution. For your device this is not gonna work. Try this one here. I did it for yuweng to test his device (Ihope he will not be upset). But don't use the port tool. Instead, unpack it with michfood tool, change in ramdisk my files with yours from original or a working recovery (recovery.fstab from dev folder, and from root all files that are not for your phone except init executable), repack it and see if it works.
Click to expand...
Click to collapse
Thanks for your help master, I did like you said but other than touch screen, everything is working fine. Now need your suggestion on this. Got this recovery and really saying, users have under estimated it cause it have great potentials for future.
Also will like to know how to create a theme for this recovery, as, I am themer and know for my theming only.
BTW, Hats off to you Master. Recovery is awesome. And Touch will make it great further.

BOND1987 said:
Thanks for your help master, I did like you said but other than touch screen, everything is working fine. Now need your suggestion on this. Got this recovery and really saying, users have under estimated it cause it have great potentials for future.
Also will like to know how to create a theme for this recovery, as, I am themer and know for my theming only.
BTW, Hats off to you Master. Recovery is awesome. And Touch will make it great further.
Click to expand...
Click to collapse
Hm, I'm a little bit confused. Which recovery did you tried to port: mine from here from first post or the one I gave you that link? Because mine is for 540x960 resolution and the one from link is for 480x854. If you port that one it should work touch screen. Attention! is not the same as koush touch recovery, the touch area is only for those four nav buttons from bottom, like in early philz recoveries. I read that ProjectOpenCannibal's next recovery will be full screen touch and much improved.
For theme you need to create a folder in cotrecovery folder on sdcard, name it themes and look here https://github.com/ProjectOpenCannibal/sdcard_themes to see how a theme should look, then create one for your resolution and apply from recovery=>COT settings=>theme=>sdcard theme.

carliv said:
Hm, I'm a little bit confused. Which recovery did you tried to port: mine from here from first post or the one I gave you that link? Because mine is for 540x960 resolution and the one from link is for 480x854. If you port that one it should work touch screen. Attention! is not the same as koush touch recovery, the touch area is only for those four nav buttons from bottom, like in early philz recoveries. I read that ProjectOpenCannibal's next recovery will be full screen touch and much improved.
For theme you need to create a folder in cotrecovery folder on sdcard, name it themes and look here https://github.com/ProjectOpenCannibal/sdcard_themes to see how a theme should look, then create one for your resolution and apply from recovery=>COT settings=>theme=>sdcard theme.
Click to expand...
Click to collapse
No Sir I am not getting any touch in the below navigation buttons and a new problem also arised just now. Now all bitmap of recovery is not able to find any image inside the recovery. Do you know what problem is it actually....???
Its says like "E/ Couldn't able to find bitmap icon_overlay01.
Though I cross checked all are there.
I am using recovery of Master Yuweng that you suggested few post back.
EDIT:-
Got the Images back after installing the default theme. Actually I selected the theme RED but it was not there so it was saying like that. Now will create a theme and share to you also. BTW how can I adjust size and something to do with touch also...
Master You are awesome and your creations also.

BOND1987 said:
No Sir I am not getting any touch in the below navigation buttons and a new problem also arised just now. Now all bitmap of recovery is not able to find any image inside the recovery. Do you know what problem is it actually....???
Its says like "E/ Couldn't able to find bitmap icon_overlay01.
Though I cross checked all are there.
Click to expand...
Click to collapse
That error appear when you select sdcard theme but there is no theme on sdcard. You see first position "Boot Android", navigate with volume buttons volume up two times, power button to enter, volume down once, power to enter, volume down once, power button enter, select hydro press power and now you should see back all images.
I saw in yuweng post that he didn't gave you that link, so if he didn't gave it to you by pm, I don't think you have the right recovery to port.
Look I'll give you again, please try with this COT Recovery 480x854. The reason the touch won't work in your actual ported recovery is because you use mine and the touch area is out of your screen.
If you have that one (named yuweng-recovery.img) and the ported one don't work that must be related to your phone touch module location, and I will have to documents on this when I have time.

carliv said:
That error appear when you select sdcard theme but there is no theme on sdcard. You see first position "Boot Android", navigate with volume buttons volume up two times, power button to enter, volume down once, power to enter, volume down once, power button enter, select hydro press power and now you should see back all images.
I saw in yuweng post that he didn't gave you that link, so if he didn't gave it to you by pm, I don't think you have the right recovery to port.
Look I'll give you again, please try with this COT Recovery 480x854. The reason the touch won't work in your actual ported recovery is because you use mine and the touch area is out of your screen.
If you have that one (named yuweng-recovery.img) and the ported one don't work that must be related to your phone touch module location, and I will have to documents on this when I have time.
Click to expand...
Click to collapse
Just a last question Master,
Sorry for bothering you in everything. Do we have to replace the kernel files also or not...
Cause I am replacing that also So it could be the reason that touch is not working.....????

BOND1987 said:
Just a last question Master,
Sorry for bothering you in everything. Do we have to replace the kernel files also or not...
Cause I am replacing that also So it could be the reason that touch is not working.....????
Click to expand...
Click to collapse
Of course you should pack with your kernel, you only need my ramdisk. I don't think it's about kernel, I think is that resolution thing. In my first builds I didn't setup resolution, for debugging reason, and I didn't have touch either, but after setting correct width and height, everything worked like a charm. I'm using this recovery since I compiled and I'm very happy. The part I like most is the possibility to backup only that partition you want (if I want to backup data I can select to backup only data).
Good luck on porting. I hope this time it will work.

carliv said:
Of course you should pack with your kernel, you only need my ramdisk. I don't think it's about kernel, I think is that resolution thing. In my first builds I didn't setup resolution, for debugging reason, and I didn't have touch either, but after setting correct width and height, everything worked like a charm. I'm using this recovery since I compiled and I'm very happy. The part I like most is the possibility to backup only that partition you want (if I want to backup data I can select to backup only data).
Good luck on porting. I hope this time it will work.
Click to expand...
Click to collapse
Sorry to bother you again master,
But other than touch everything is working fine, may I know is it related to touch drivers or only resolutions.
Cause just checked my device specs and the resolution is saying "480*800" and the file that you gave me is 480*854 so because of this it is not working only for 54 pixels, though I know it's possible as like .9pngs.
If yes so please either do a favor and create another files with resolution "480*800" please.
The last favor please.....

BOND1987 said:
Sorry to bother you again master,
But other than touch everything is working fine, may I know is it related to touch drivers or only resolutions.
Cause just checked my device specs and the resolution is saying "480*800" and the file that you gave me is 480*854 so because of this it is not working only for 54 pixels, though I know it's possible as like .9pngs.
If yes so please either do a favor and create another files with resolution "480*800" please.
The last favor please.....
Click to expand...
Click to collapse
Aahh, there you go! Of course this is the reason. I will try to compile one for that resolution these days and I will post it here.

carliv said:
Aahh, there you go! Of course this is the reason. I will try to compile one for that resolution these days and I will post it here.
Click to expand...
Click to collapse
No Problem Master,
I can wait. I am posting this Recovery in my thread and Credits are yours and Master Yuweng's also for showing me this thread.
Thanks a ton for this awesome recovery.

BOND1987 said:
No Problem Master,
I can wait. I am posting this Recovery in my thread and Credits are yours and Master Yuweng's also for showing me this thread.
Thanks a ton for this awesome recovery.
Click to expand...
Click to collapse
Here it is COT Recovery 480x800 for MTK devices. I hope it works.
Enjoy porting.

carliv said:
Here it is COT Recovery 480x800 for MTK devices. I hope it works.
Enjoy porting.
Click to expand...
Click to collapse
Master,
Its same thing I am getting. Is there any file which is also responsible for making touch to work and one more thing master. There is no Navigation Bars in the new file.
But people have like the new recovery Master. Thanks & Lot for the Masterpiece work.
Here is My Thread :- Cannibal Open Touch Recovery

BOND1987 said:
Master,
Its same thing I am getting. Is there any file which is also responsible for making touch to work and one more thing master. There is no Navigation Bars in the new file.
But people have like the new recovery Master. Thanks & Lot for the Masterpiece work.
Here is My Thread :- Cannibal Open Touch Recovery
Click to expand...
Click to collapse
Well, you gave me wrong info. Your device does have resolution 480x854 not 480x800.
Delete cotrecovery folder from sdcard. Install back 480x854 ported recovery, boot in recovery and see if you get touch screen calibration (first thing after boot in recovery - a red square touch three times). Play a little with menu and boot back in Android. Now open cotrecovery folder from sdcard and give me the content of settings.ini file. Also tell me if your device has a /dev/input folder or tell me which folders do you have in /dev.
Just to test again, boot back in recovery and in COT settings do again touch screen calibration.

carliv said:
Well, you gave me wrong info. Your device does have resolution 480x854 not 480x800.
Delete cotrecovery folder from sdcard. Install back 480x854 ported recovery, boot in recovery and see if you get touch screen calibration (first thing after boot in recovery - a red square touch three times). Play a little with menu and boot back in Android. Now open cotrecovery folder from sdcard and give me the content of settings.ini file. Also tell me if your device has a /dev/input folder or tell me which folders do you have in /dev.
Just to test again, boot back in recovery and in COT settings do again touch screen calibration.
Click to expand...
Click to collapse
But Master, I am not able to touch the red dot, Its not responding. That's what I am saying that touch is not working in any version but in TWRP of ours touch is working fine. Here is the working touch TWRP recovery. May be it can help Master. Regarding I am still confused that its 480*800 or 480*854 but touch is not working in any of them.
Along with that I am uploading the whole dev/input folder and cotrecovery folder.

BOND1987 said:
But Master, I am not able to touch the red dot, Its not responding. That's what I am saying that touch is not working in any version but in TWRP of ours touch is working fine. Here is the working touch TWRP recovery. May be it can help Master. Regarding I am still confused that its 480*800 or 480*854 but touch is not working in any of them.
Along with that I am uploading the whole dev/input folder and cotrecovery folder.
Click to expand...
Click to collapse
Well, for some reason input directory is empty. This recovery has the same way as twrp to trigger touch.
Overwrite your settings.ini with the one attached (rename it to settings.ini).
Also give me your ported recovery.

carliv said:
Well, for some reason input directory is empty. This recovery has the same way as twrp to trigger touch.
Overwrite your settings.ini with the one attached (rename it to settings.ini).
Also give me your ported recovery.
Click to expand...
Click to collapse
Sir, After replacing the settings.ini in COTrecovery folder nothing changed. And I am attaching my ported recovery in the post. So Sir, do check it in your free time.
Thanks for supporting master or else I could never been able to port this recovery for us.

BOND1987 said:
Sir, After replacing the settings.ini in COTrecovery folder nothing changed. And I am attaching my ported recovery in the post. So Sir, do check it in your free time.
Thanks for supporting master or else I could never been able to port this recovery for us.
Click to expand...
Click to collapse
I need your device official boot.img and recovery.img
There is something wrong in your init.rc, but I need to look in those two files to be sure.

Related

[TOOL/UTILITY][TWRP][3.0][RECOVERY] TWRP 3.0.0-1 TeamWin Recovery Project 3/28/2016

[RECOVERY] [3/28/16] TWRP 3.0.0-1 - TeamWin Recovery Project
TeamWin is proud to present TWRP 3.0.x for the Motorola Photon Q!
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for new features
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
Known Issues:
CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit for TWRP Official Device Configs - http://gerrit.twrp.me
Gerrit Instance - http://gerrit.omnirom.org
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Photon Q Device Config: https://github.com/CyanogenMod/android_device_motorola_xt897/tree/cm-13.0
Kernel: https://github.com/arrrghhh/android_kernel_motorola_msm8960-common-twrp
DOWNLOAD:
Official Link
All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.
http://twrp.me
Support:
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers
Many thanks to @Dees_Troy, @helicopter88 & @bigbiff for helping get TWRP running, and of course thanks to @shabbypenguin for getting everything started on the device tree!
I highly advise the buglist and directions be reviewed!!
Thanks!!
Buglist​
**If you had an old version of TWRP installed before, MAKE SURE you 'Restore Defaults' under 'Settings' in TWRP**
Clock is off. Not sure why, seems unfixable.
Cannot use physical keyboard to type in Recovery...Obviously the on-screen kb works fine.
Directions:
** You must be unlocked in order to do this.**
2 choices after rooting. You can download TWRP Manager from the Play Store, menu, TWRP install & wait... (I do not provide support for this app FYI) or:
1. Reboot into fastboot (adb reboot bootloader, or turn off device, hold power + cam when booting and select 'fastboot')
2. Once in fastboot,
Code:
fastboot flash recovery twrp-2.7.1.2-asanti_c.img
3. Hit power - device turns off. Hold vol up + power, then release power when the screen comes on - continue holding vol up. When you see the moto logo dim a bit, release vol up. You should now be in TWRP!
Works great! I used Goomanager
Edit: Works as in installs and boots. Touchscreen works, I have not tested the actual functions as of yet.
Tried to do a backup to external SD, it seems to have done it but after the loading bar finished I got the initial blue and black logo and couldn't get out of it. Had to 3 button reboot. Can't find the backup.
KitsunePaws said:
Works great! I used Goomanager
Edit: Works as in installs and boots. Touchscreen works, I have not tested the actual functions as of yet.
Tried to do a backup to external SD, it seems to have done it but after the loading bar finished I got the initial blue and black logo and couldn't get out of it. Had to 3 button reboot. Can't find the backup.
Click to expand...
Click to collapse
Hrm. I'll look into that... I think I've only done a backup to internal SD as my external is ridiculously full.
Edit - just did a backup of boot to the external, worked just fine. Perhaps wait a bit? How long did you wait, and what were you backing up?
Edit 2 - ok, perhaps I jumped the gun. "Worked" doesn't quite describe it... I have the TWRP folders for the backup, but there's no backup file in there. Strange... Perhaps because I backed up only boot. I'll try again with less junk on the card and do a full backup...
arrrghhh said:
Hrm. I'll look into that... I think I've only done a backup to internal SD as my external is ridiculously full.
Edit - just did a backup of boot to the external, worked just fine. Perhaps wait a bit? How long did you wait, and what were you backing up?
Click to expand...
Click to collapse
Just went with the default settings, I didn't wait that long after the progress bar went away it went back to a team logo, I let it sit for about a minute and then reset it. Trying again.
Ran through it again, it took a while backing up /data. (398 megs). The bar filled all the way up though it still said "... Backing up /data" Sitting at the teamwin logo again, it's been on this image for 4 minutes at this point (Went to the logo at 6:09). ( Now it's blinking. And now it reset. These could have been caused by my touching the screen. I think the logo is getting "stuck" ). Is the progress bar based on a timer or events?
Also, it made the TWRP folder on the internal SD regardless of the fact I told it external. I did notice that the backup path during said "/sdcard" and not "/mnt/external1". The folder does not contain a backup.
KitsunePaws said:
Just went with the default settings, I didn't wait that long after the progress bar went away it went back to a team logo, I let it sit for about a minute and then reset it. Trying again.
Ran through it again, it took a while backing up /data. (398 megs). The bar filled all the way up though it still said "... Backing up /data" Sitting at the teamwin logo again, it's been on this image for 4 minutes at this point (Went to the logo at 6:09). ( Now it's blinking. And now it reset. These could have been caused by my touching the screen. I think the logo is getting "stuck" ). Is the progress bar based on a timer or events?
Also, it made the TWRP folder on the internal SD regardless of the fact I told it external. I did notice that the backup path during said "/sdcard" and not "/mnt/external1". The folder does not contain a backup.
Click to expand...
Click to collapse
Indeed.
I am in the same "stuck" situation as you now. For the meantime, it seems backing up to external SD does NOT work... I tested backup and restore, but only to internal SD. I saw that my external didn't have enough space, and wrote it off as enough... Apologies for not thoroughly testing that.
arrrghhh said:
Indeed.
I am in the same "stuck" situation as you now. For the meantime, it seems backing up to external SD does NOT work... I tested backup and restore, but only to internal SD. I saw that my external didn't have enough space, and wrote it off as enough... Apologies for not thoroughly testing that.
Click to expand...
Click to collapse
No worries, that's what makes XDA the place that it is ^-^. If I expected perfection I would buy an iPh.... couldn't do it with a straight face.
OK, the issue with external SD should be fixed. However, I don't have the ability to push the changes to GooManager, so you'll have to flash manually until it's updated on GooManager (I'll let you know )
Edit - to be clear, you cannot use GooManager or the official link right now. Please use 'mirror 1' and manually update in order to fix the external SD issue (until it's officially updated).
Alrighty, Dees_Troy said it is officially updated. I can see the update on the official link - but I'm not sure how on GooManager you update - if you just click 'check for updates'? That seems to only check on ROM updates, but I could be wrong.
Please let me know how it goes! If you experience any issues, etc.
Edit - seems you just do the same as when it was initially installed... Menu -> Install OpenRecoveryScript & wait... then reboot to recovery.
Also, if you notice - TWRP is now 2.2.2.2 - yes, a whole lotta 2's... but that last .2 is the Q!! Congrats, we're official!
Aweesssommeee....
2.2.2.2 is finally showing up in goo
New SD path seems to be working. Any idea what driver it tried to install?
Looks like the logo issue is fixed too, grats.
KitsunePaws said:
New SD path seems to be working. Any idea what driver it tried to install?
Looks like the logo issue is fixed too, grats.
Click to expand...
Click to collapse
Glad it's workin for ya.
Driver? Not sure what you're talking about... there is ADB in recovery, if that's what you mean...
arrrghhh said:
Glad it's workin for ya.
Driver? Not sure what you're talking about... there is ADB in recovery, if that's what you mean...
Click to expand...
Click to collapse
Hmm, maybe I'm just going crazy, when it booted into recovery I got a dialog box that it was trying to install "asanti" and didn't have the driver, I've got the motorola app installed and adb works normally. Probably just a fluke.
KitsunePaws said:
Hmm, maybe I'm just going crazy, when it booted into recovery I got a dialog box that it was trying to install "asanti" and didn't have the driver, I've got the motorola app installed and adb works normally. Probably just a fluke.
Click to expand...
Click to collapse
Huh... perhaps when the device was 'in limbo'. I forced mine into limbo a few times messing with the kernel yesterday, and it did indeed create a bunch of new devices in Windows - some installed correctly, but adb didn't exactly work...
Hopefully no more of that on TWRP! I have run thru the gambit and the only outstanding fixable bugs are probably going to be the mass storage and the physical keyboard - which will probably take some time. I don't think the clock issue is fix-able...
Let me know if you guys find anything else broken. So far it has all worked for me!
Anyone know how long it's supposed to take to install thru goomanager?
Sent from my XT897 using xda premium
tetrabyt said:
Anyone know how long it's supposed to take to install thru goomanager?
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Mine took no longer than 2-3 minutes from start to finish
KitsunePaws said:
Mine took no longer than 2-3 minutes from start to finish
Click to expand...
Click to collapse
Same. It was REALLY fast over wifi.
I must be missing something. I sat and watched it say installing recovery for about 15minutes. Had to keep touching the screen to keep it awake... Will try again.
Edit: it just took about 40seconds.. Thanks. It works now.
Sent from my XT897 using xda premium
tetrabyt said:
Edit: it just took about 40seconds.. Thanks. It works now.
Click to expand...
Click to collapse
Nice, glad it works for you!
So I've got 3 thanks on the first post, and I think 2 people have responded that they've installed it (with a third 'approving' of it )... but 60+ downloads? Is it just working that well that everyone forgets this thread exists? Hahahaha!
Well, I hope it is working well for everyone. Enjoy!

[CWM] CWM-based Recovery for RK3188/RK3066/RK2928/RK2926/RK2918/RK2906

Mod Edit: Link removed
all credit goes to original CWM author koush and all its contributors. but they have no responsibility for this CWM-based Recovery. use this CWM-based Recovery at your own risk.
this CWM-based Recovery can write raw MTD partition such as kernel, boot, and recovery on RK3188, RK3066, RK2928, RK2926, RK2918, and RK2906 devices without any problem. this can be installed without Windows.
if you want to install zip with edify script which writes something to raw MTD partition, you have to use update-binary and/or flash_image included in this CWM-based Recovery image.
please see my site for detail.
* Known issues (2013/2/11)
- timestamp
backup may be named as 1970-01-01.xx.xx.xx. it's just a directory name on SD card. please rename it.
- dump_image
it says "mtd: read error (No such file or directory)" at the end. please ignore it, it should not be a problem.
* How to controll
- mouse
move up/down: up/down
left click: select
right click: back
- keyboard
cursor up/down: up/down
cursor left/enter: select
cursor right: back
- touch screen
swipe up/down: up/down
swipe left: select
swipe right: back
- button
volume up/down: up/down
power: select
back: back
- remote controller
up/down: up/down
left/ok: select
back: back
* about tools to make device specific image
you can use any tools which can be used to make custom rom for Rockchip devices. I'm using rkunpack, rkcrc, unpackbootimg, and mkbootimg.
if you don't know how to make custom rom for Rockchip devices, please ask google. many developers are already making custom rom for Rockchip devices, many information is already floating around.
where to download rkflash, rkflashtool, or RKAndroidTool.exe
CWM on my mk808b could be great, thanks!
Can any anyone please point me to where to download any of these tools?:
magnemann said:
CWM on my mk808b could be great, thanks!
Can any anyone please point me to where to download any of these tools?:
Click to expand...
Click to collapse
if you want to know how to install CWM, please read "how to install" page on my site, and try "from root shell" method.
if you want to know about these tools, I'll add more information including them on my site. but it will be done little by little.
and I think here is not the best place to talk about other topics. please try search box on XDA, or google.
regards,
fun_ said:
if you want to know how to install CWM, please read "how to install" page on my site, and try "from root shell" method.
if you want to know about these tools, I'll add more information including them on my site. but it will be done little by little.
and I think here is not the best place to talk about other topics. please try search box on XDA, or google.
regards,
Click to expand...
Click to collapse
Thanks alot for info! I'll try 'from root shell' method. Seems like the easiest way. :laugh:
How do i boot into CWM if stuck at boot?
I know I can do it with 'reboot'->recovery with reboot-app in finless 1.5. But I've been troubled with freeze at boot sometimes with no other option than to reflash rom.
magnemann said:
How do i boot into CWM if stuck at boot?
I know I can do it with 'reboot'->recovery with reboot-app in finless 1.5. But I've been troubled with freeze at boot sometimes with no other option than to reflash rom.
Click to expand...
Click to collapse
I only have a MK806. it has a button to boot recovery and bootloader. but sorry I don't know about other device...
if you are sure there is no button, then you need to flash some misc.img with USB flash tool.
sorry, I'm busy a little. please search about RKAndroidTool for RK3066 on google.
I got a report on another forum, this CWM works fine on MK808B.
backup will be named as "1970-01-01.xx.xx.xx" on (at least) MK806 and MK808B.
I'll investigate it. for now please rename it from PC or any explorer app. it's just a directory name on SD card.
Ah, a new cwm for my rk2918 device.
Thanks to fun_ stuff.
JDfense
http://androtab.info/clockworkmod/rockchip/
2013/1/19
update updater-script
add images for MK802III and UG007
latest stock rom for MK802III and UG007 has /system/etc/install-recovery.sh. it restores stock recovery on every boot. then, you need to disable it e.g.
Code:
chmod 644 /system/etc/install-recovery.sh
otherwise, installed CWM is erased and stock recovery is restored after reboot.
I added above code into updater-script in all my CWM.zip. if you install CWM.zip from CWM or adb sideload, it will be done automatically.
if you flash recovery.img from shell or rk tools, you need to do it manually.
if you update your device, install-recovery.sh may be re-enabled. then, you need to disable it again.
----
at this time all images are updated, but only updater-script in zip is changed. if you already installed CWM, no need to install this version.
hi fun!
I was wondering if I provide you with the parameter file and any other files you need if you could modify the build for our Minix Neo X5 device? thanks man!!
onelovekir said:
I was wondering if I provide you with the parameter file and any other files you need if you could modify the build for our Minix Neo X5 device?
Click to expand...
Click to collapse
I added images for NEO G4 and NEO X5. please try.
EDIT:
I noticed NEO G4 and NEO X5 have remote controller. can you try it?
if it doesn't work well, please try "Advanced Menu > key test" and tell me relation between button and key code.
probably VOL+/-, POWER and BACK can be used on this version, but DPAD up/down/left/right/ok will not work.
EDIT2:
little off-topic, X5 looks nice for me. is there any "take apart" pics?
EDIT3:
http://minixforums.com/threads/neo-x5-mod-heatsink-for-cpu.60/ interesting
hmm I want to see another side
http://androtab.info/clockworkmod/rockchip/
2013/01/20
CWM.zip can be installed from stock recovery (it may not work on some device)
if you already installed CWM, no need to install it.
fun_ said:
I added images for NEO G4 and NEO X5. please try.
EDIT:
I noticed NEO G4 and NEO X5 have remote controller. can you try it?
if it doesn't work well, please try "Advanced Menu > key test" and tell me relation between button and key code.
probably VOL+/-, POWER and BACK can be used on this version, but DPAD up/down/left/right/ok will not work.
EDIT2:
little off-topic, X5 looks nice for me. is there any "take apart" pics?
EDIT3:
http://minixforums.com/threads/neo-x5-mod-heatsink-for-cpu.60/ interesting
hmm I want to see another side
Click to expand...
Click to collapse
there is some take apart pics somewhere...let me see if I can find them. thanks for your help and I will test the new build today.
and oh yeah btw...X5 is very nice
for all,
if you can, please try to install from stock recovery. I hope it should be easy and it will work on all RK3066 products/stock roms.
but it doesn't work (invalid message) on Yuandao N50 RK2918 tablet.
I want to know that it works or doesn't work on which product/rom as much as possible.
fun_ said:
I added images for NEO G4 and NEO X5. please try.
EDIT:
I noticed NEO G4 and NEO X5 have remote controller. can you try it?
if it doesn't work well, please try "Advanced Menu > key test" and tell me relation between button and key code.
probably VOL+/-, POWER and BACK can be used on this version, but DPAD up/down/left/right/ok will not work.
EDIT2:
little off-topic, X5 looks nice for me. is there any "take apart" pics?
EDIT3:
http://minixforums.com/threads/neo-x5-mod-heatsink-for-cpu.60/ interesting
hmm I want to see another side
Click to expand...
Click to collapse
ok after further testing, your build so far looks good (although I haven't yet tried to flash a zip file). I just have been trying to get the keys right on the remote that it comes with. I have all the key test functions if you would like to rebuild the X5 version. up/down on the d-pad give you up/down on the screen. left on the d-pad is the select or ok button for CWM.
Re: [CWM] CWM-based Recovery for RK3066/RK2918 devices
fun_ said:
for all,
if you can, please try to install from stock recovery. I hope it should be easy and it will work on all RK3066 products/stock roms.
but it doesn't work (invalid message) on Yuandao N50 RK2918 tablet.
I want to know that it works or doesn't work on which product/rom as much as possible.
Click to expand...
Click to collapse
It works for the Minix Neo X5 perfectly! We just gotta get those keys straightened out.
HTC EVO LTE with Tapatalk
onelovekir said:
ok after further testing, your build so far looks good (although I haven't yet tried to flash a zip file). I just have been trying to get the keys right on the remote that it comes with. I have all the key test functions if you would like to rebuild the X5 version. up/down on the d-pad give you up/down on the screen. left on the d-pad is the select or ok button for CWM.
Click to expand...
Click to collapse
well, my English is not so good. I'm sorry asking again, d-pad up/down/left/right on remote worked on this version?
I want to see key test result.
onelovekir said:
It works for the Minix Neo X5 perfectly! We just gotta get those keys straightened out.
Click to expand...
Click to collapse
my CWM.zip (renamed to update.zip) can be installed from X5 stock recovery, right?
anyway, thank you for your cooperation!
Re: [CWM] CWM-based Recovery for RK3066/RK2918 devices
fun_ said:
well, my English is not so good. I'm sorry asking again, d-pad up/down/left/right on remote worked on this version?
I want to see key test result.
my CWM.zip (renamed to update.zip) can be installed from X5 stock recovery, right?
anyway, thank you for your cooperation!
Click to expand...
Click to collapse
Yes the up/down/left arrows work but not the right (i think cuz we don't need a fourth function), but ONLY (so far) on the stock remote that comes with the X5. Yes changing to update.zip works and I will get you the key test results in a little bit.
Thanks again for your work!
HTC EVO LTE with Tapatalk

[P5100][CWM Advanced Edition] PhilZ Touch

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Since many requests to port it to P5100, here it is released
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
To take a screen shot, just slide left
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
P5100 - P5110 - P5113
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Dualboot edition by @ketut.kumajaya
http://forum.xda-developers.com/showthread.php?p=42012268#post42012268
Click to expand...
Click to collapse
Great work bro.....thank you so much......
Sent from my GT-N7100 using xda premium
Philz you beauty! Welcome to the P5100 land! Finally something to look forward to in this otherwise zzzz P5100 forum. I was really planning to sell off this tablet due to the lack of top notch recoveries and kernels. Now I have eternal hope because Philz our saviour is here!
People, you just have to try his Kernels. He is a legend! Just check out the Note N7000 forums if you want to check out his fabulous work and fan following
About touch:
1- when you touch a menu to select: is the selection precise and working as expected
2- bottom virtual buttons: do they work as expected?
3- If it is slow, try to reduce the Scroll Sensitivity setting and reduce menu height. Play with both to find a sweet point¨
Try to describe what happens with precision. A video would even be better, so that I can get what you mean. I won't be able to help much as I do not have the device, without these
Here are the screenshots. The touch works perfect. There's no lag whatsoever. The bottom navigation buttons work as they should. Hopefully we'll be gifted with a Kernel soon
This works great on my 5113. The Aroma file manager seems really useful. I wasn't totally sure how to set it up so I'll write the steps here in case anyone else is wondering.
I downloaded the zip from here: http://forum.xda-developers.com/showthread.php?t=1646108
You can "install" the zip file from recovery which really just runs the file manager. It doesn't really install anything. When you exit you go back to recovery.
However, if you want to use it from inside PhilZ's recovery do this:
Go to /sdcard/clockworkmod
Create a directory called .aromafm
Copy the zip file you downloaded into that directory
Change the name of the zip file to aromafm.zip
Now you can use the Aroma FM menu item from the recovery to launch the file manager. The first time you run it from a new location you get the "help" overlay screen. I did the above steps in the file manager itself. Pretty cool. And having a terminal from inside recovery is great when you need to fix something and aren't at home.
aashayjardosh said:
Here are the screenshots. The touch works perfect. There's no lag whatsoever. The bottom navigation buttons work as they should. Hopefully we'll be gifted with a Kernel soon
Click to expand...
Click to collapse
Big thanks for the screen shots. At least I can see how the display is looking
I decided on purpose to not enlarge the bottom buttons as I thought it would be harder to use them if spread along all the width. Is it ok?
As for menu toggle options not being completely right aligned, it is a limitation in current stock CWM, and I feel no need to increase the buffer to make it right align
wd5gnr said:
This works great on my 5113. The Aroma file manager seems really useful. I wasn't totally sure how to set it up so I'll write the steps here in case anyone else is wondering.
I downloaded the zip from here: http://forum.xda-developers.com/showthread.php?t=1646108
You can "install" the zip file from recovery which really just runs the file manager. It doesn't really install anything. When you exit you go back to recovery.
However, if you want to use it from inside PhilZ's recovery do this:
Go to /sdcard/clockworkmod
Create a directory called .aromafm
Copy the zip file you downloaded into that directory
Change the name of the zip file to aromafm.zip
Now you can use the Aroma FM menu item from the recovery to launch the file manager. The first time you run it from a new location you get the "help" overlay screen. I did the above steps in the file manager itself. Pretty cool. And having a terminal from inside recovery is great when you need to fix something and aren't at home.
Click to expand...
Click to collapse
Yes, but you can also just double tap outside menu area, and it will launch aroma
Phil3759 said:
Yes, but you can also just double tap outside menu area, and it will launch aroma
Click to expand...
Click to collapse
Forgot about that, but you still have to do the setup to put the zip file with the right name in the hidden directory, no?
wd5gnr said:
Forgot about that, but you still have to do the setup to put the zip file with the right name in the hidden directory, no?
Click to expand...
Click to collapse
yes, sure
So, for p5100, you confirm that touch works as expected? Even the double tap and other shortcuts I guess
Phil3759 said:
yes, sure
So, for p5100, you confirm that touch works as expected? Even the double tap and other shortcuts I guess
Click to expand...
Click to collapse
Yes, the touch works perfect. Flashed 2-3 ROM's just for fun for testing it. The double tap and other shortcuts (the ones i checked) are all cool.
And yes the bottom navigation buttons are also good at this size. Infact they're perfect for the wider screen. Cheers!
Phil3759 said:
yes, sure
So, for p5100, you confirm that touch works as expected? Even the double tap and other shortcuts I guess
Click to expand...
Click to collapse
Yes, all work great.
wd5gnr said:
Yes, all work great.
Click to expand...
Click to collapse
Actually, I may have found a problem related to the 5113. I have installed some kernels through this recovery but when I went to install the latest CM nightly I get an assert failure where it is looking for p5110 or p5113. I've installed many of these in the past. I may revert to old CWM and see if it works, but I feel it must be related to this recovery, perhaps because it doesn't know I have a 5113?
Update: Reverting to normal stock worked.
wd5gnr said:
Actually, I may have found a problem related to the 5113. I have installed some kernels through this recovery but when I went to install the latest CM nightly I get an assert failure where it is looking for p5110 or p5113. I've installed many of these in the past. I may revert to old CWM and see if it works, but I feel it must be related to this recovery, perhaps because it doesn't know I have a 5113?
Update: Reverting to normal stock worked.
Click to expand...
Click to collapse
Just delete the assert line from your updater-script file in zip
For other variants, follow instructions and i will release for your phone
Sent from my GT-I9100 using Tapatalk 2
Phil3759 said:
Just delete the assert line from your updater-script file in zip
For other variants, follow instructions and i will release for your phone
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Yeah I have done that before for other reasons. Just thought I'd mention it.
wd5gnr said:
Yeah I have done that before for other reasons. Just thought I'd mention it.
Click to expand...
Click to collapse
CM ROMs have an extra safety check which cant be avoided by deleting assert prop lines in updater script.
It's under META-INF\com\android\metadata
With N7000 it shows this - "post-build=samsung/GT-N7000/GT-N7000:4.0.3/IML74K/ZCLP6:user/release-keys
post-timestamp=1364279894
pre-device=GT-N7000
Phil3759 said:
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
Since many requests to port it to P5100, here it is the first release, untested by me
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
I would appreciate a screen shot from your device, mainly under GUI options or custom backup menu where you select partitions
To take a screen shot, just slide left
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download: Flash at your own risk, this is a first release, untested
http://www.mediafire.com/file/bj7vnfal8ca8h4q/philz_touch_4.90.8-p5100.tar.md5
http://www.mediafire.com/file/mc71ezq8eg6oqo8/philz_touch_4.90.8-p5100.zip
Click to expand...
Click to collapse
Great my bro but it possible to make for Tab 2 gt-p5110 pleassssseeeeeee.
thanks for your hard work
The one for 5100 doesn't work? There are no big diff, recovery wise
Sent from my GT-I9100 using Tapatalk 2
Phil3759 said:
The one for 5100 doesn't work? There are no big diff, recovery wise
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
ok i test tonight and reply here ok philz ?
thanks
you think i can use my custom res of my note 2 with your recovery ? (with my config of your recovery for have fonts ustom background red etc etc same as your recovery note 2?)
brolee93 said:
ok i test tonight and reply here ok philz ?
thanks
you think i can use my custom res of my note 2 with your recovery ? (with my config of your recovery for have fonts ustom background red etc etc same as your recovery note 2?)
Click to expand...
Click to collapse
Just ensure the resolution, since it is inverted. Let me know and eventually post a screen shot
By the way, since you have a note 2. Can you let me know your opinion about touch difference between note 2 and this one?
Also, if you post a recent recovery.img from sammobile.com, i will repack for p5110 if needed
Sent from my GT-I9100 using Tapatalk 2
ok i see

[RECOVERY] Various recoveries for THL T100S and THL T11

DISCLAIMER:
Rooting your phone and using custom Recoveries and ROMS have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledges about phones and phones utilities too.
Make sure that whatever you do, you are doing it at your own responsibility.
Here are several recoveries compiled from source by me, for THL T100S, octacore mt6592. All are fully functional.
and here are several recoveries compiled from source by me, for THL T11, octacore mt6592. Need to be tested.
I know that there are already compiled TWRP recoveries, same versions, for this phone, but my versions are a little bit different. For example in my versions, both sdcards are mounted at the same time in USB Mass Storage mounting, not one at a time as in existent twrp recoveries. And there are some other small changes.
All can be installed by MobileUncleTools or SPFlashTools.
Could you please help me, how to port your recoveries to T11?
I've tried the manual and automatic modes, on the desktop W8.1x64, no errors but the recovery not showed up.
Indiant said:
Could you please help me, how to port your recoveries to T11?
I've tried the manual and automatic modes, on the desktop W8.1x64, no errors but the recovery not showed up.
Click to expand...
Click to collapse
Hm, I see there are some similarities between THL T100S and T11, but the device resolution is different, and so for recoveries between point 2 to 5 that might be a problem, but number 1 should work... If you can give me a stock recovery I will try to build again for your device, when I will have time. Nevermind. I found it.
carliv said:
Hm, I see there are some similarities between THL T100S and T11, but the device resolution is different, and so for recoveries between point 2 to 5 that might be a problem, but number 1 should work... If you can give me a stock recovery I will try to build again for your device, when I will have time. Nevermind. I found it.
Click to expand...
Click to collapse
It is the same phone except resolution (720x1280), the camera, but it is not matter, and the 16Gb space.
Yes, the 1st works great! The second is working too, but the touch is misaligned.
Thank you for the great recoveries and your work!
Indiant said:
It is the same phone except resolution (720x1280), the camera, but it is not matter, and the 16Gb space.
Yes, the 1st works great! The second is working too, but the touch is misaligned.
Thank you for the great recoveries and your work!
Click to expand...
Click to collapse
Have you tested number 2 from my new list, for T11? Can you make a photo about the problem (touch misaligned) or to provide more details, because version 2 is not full touch, and the actions are taken by swipe (up/down/left/right). If you touch a menu row the highlight will move up or down, depends how it will be interpreted as swipe up or down.
carliv said:
Have you tested number 2 from my new list, for T11? Can you make a photo about the problem (touch misaligned) or to provide more details, because version 2 is not full touch, and the actions are taken by swipe (up/down/left/right). If you touch a menu row the highlight will move up or down, depends how it will be interpreted as swipe up or down.
Click to expand...
Click to collapse
Yes, I did. I mean the four buttons on the screen are not working. The swipe up and down are working ok. (up is up and down is down)
T11
Carliv Touch Recovery v-2.5:
Restore from earlier backup is not working. (Error while flashing uboot image) and stops
TWRP-s are not booting.
Indiant said:
T11
Carliv Touch Recovery v-2.5:
Restore from earlier backup is not working. (Error while flashing uboot image) and stops
TWRP-s are not booting.
Click to expand...
Click to collapse
For Carliv Touch Recovery v-2.5, check to see if the backup format is same as before, if it was tar then set to tar and restore, if it was tar gz set to tar gz.
For twrp I'm affraid I can't help you more without the phone.
carliv said:
For Carliv Touch Recovery v-2.5, check to see if the backup format is same as before, if it was tar then set to tar and restore, if it was tar gz set to tar gz.
For twrp I'm affraid I can't help you more without the phone.
Click to expand...
Click to collapse
Hi!
I tried all mode (tar, tar+ gzip, and the third mode ) without success. "Error while flashing uboot image"
It can restore only own backup. :silly:
I have instaled this one with uncle tools
https://www.dropbox.com/s/u2ixf78a2krl8fd/recovery.img
Sent from my thl T100S using XDA Premium 4 mobile app
Indiant said:
T11
Carliv Touch Recovery v-2.5:
Restore from earlier backup is not working. (Error while flashing uboot image) and stops
Click to expand...
Click to collapse
kamillo said:
Hi!
I tried all mode (tar, tar+ gzip, and the third mode ) without success. "Error while flashing uboot image"
It can restore only own backup. :silly:
Click to expand...
Click to collapse
Of course it does, because probably those old backups don't contain uboot.img. Not every recovery for mtk do backup also uboot. Even I introduced that since version 2.2 I guess, because I saw it will perform better if uboot is refreshed during restore. That's the reason I put lk.bin(uboot) in my custom ROMs too.
The solution is to restore those backups with advanced restore one by one: boot, system, data.
underboy2008 said:
I have instaled this one with uncle tools
https://www.dropbox.com/s/u2ixf78a2krl8fd/recovery.img
Sent from my thl T100S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't understand. Why are you telling me this? If it's one of mine, someone tooked from here and uploaded there, if it's not (there are other versions on the internet) I don't see the point.
I'm glad to have CTR2.5 for T11. :good:
But why smallers the buttons? (I know it is new design, but there are a lot of unused space left...)
Indiant said:
I'm glad to have CTR2.5 for T11. :good:
But why smallers the buttons? (I know it is new design, but there are a lot of unused space left...)
Click to expand...
Click to collapse
Well, you are the first, and thl t100s users too. I didn't release yet that version.
The new UI is focused on better space management. I know in your big screen it is much space left but in a 240 or 480px screen this is better, and I have to think an unified solution for everyone. This new UI will make menus accessible even in devices with only 2 points of touch, in which swipe wont work.
The new Backup is awesome. So detailed. I like it!
Carliv Touch Recovery v-2.5 and old Backups (uboot.img missing solution)
1. create a new backup and from that copy uboot.img file to old backup folder
2. from nandroid.md5 file copy the uboot.img row to old nandroid.md5 file with notepad++
Problem solved.
hello guys i hope you can help me.
i tryed to installed xposed installer and my phone wont boot up anymore.
i get the splash screen but nothing after it.
i can get to recovrey but it doesnt do anything when i press wipe data or catch.
when using SP flash tool i try to load scatter file and i get this error "error initializing scatter file failed"
anyone can help me? =/
EDIT
i meanaged to run sp tool in a diffrent version one. but it wont reconzie phone. i click download and then connect phone but i keep seeing at bottom of sp tools "seraching" and nothing happens (exept of noise of a connecting usb from computer...)
itzikd1 said:
when i press wipe data or catch..
Click to expand...
Click to collapse
..press Factory reset instead (Carliv sry for off) itzikd1,pls do not answer to this
@carliv
Could you update the TWRP to the latest 2.7.1.1/2.7.1.2 (bugfixes)?
Which version (6.0.4.4?) is CWM?
Why on TWRP website (http://teamw.in/project/twrp2) there is no reference about yoour TWP recovery?
HI Carliv.
Could you update TWRP for T100S at 2.8.4.0?
bovirus said:
HI Carliv.
Could you update TWRP for T100S at 2.8.4.0?
Click to expand...
Click to collapse
I don't have the phone. When I built these recoveries I had one from a friend who wanted me to build a recovery for him, but now he doesn't have it either (sold). I can't do it without the phone to test the result first.

Twrp recovery - 2.8.4.0 Rev -2 - xolo q3000

TWRP RECOVERY - 2.8.4.0 Rev 2- XOLO Q3000 with OTG support​
Procedure to follow
download the recovery.
then flash recovery using sptools /flashify /mobileuncle tool using these guides.
OR
if ur using any custom recovery from this thread then
visit this thread to get a flashable recovery which can be flashed from current recovery.
Just reboot to recovery for confirmation.
This is working recovery - tested by me.
flashed JB & KK rom.
Backup and restore without any issues.
OTG is also working properly - FAT/FAT32 formatted USB drives only.
As u all know our device has 6mb recovery partition size.
So while porting i need to trim the actual recovery.
U will not be able to partition ur sd card using this recovery.
Also u wont be able to root using this recovery.
For above issues we have better solutions.
Try and report.
​
For official change logs, see here:
http://teamw.in/project/twrp2
Credits:-
needrom for base recovery.
@z31s1g for TWRP themes.
OTG working normally.
You did it finally...
aaayush_singh said:
You did it finally...
Click to expand...
Click to collapse
Still doing some work on TWRP 2.8.5.0
Almost around 6.12 MB, it has at most tobe 5.99 MB.
Lets see.
avi3230 said:
Still doing some work on TWRP 2.8.5.0.....
Click to expand...
Click to collapse
is twrp v2.8.4.0 rev 2 flashable zip available only in dark theme? how to get the theme shown in the attached pic? will you be releasing other themed zips for twrp v2.8.4.0 rev 2?
m0han said:
is twrp v2.8.4.0 rev 2 flashable zip available only in dark theme? how to get the theme shown in the attached pic? will you be releasing other themed zips for twrp v2.8.4.0 rev 2?
Click to expand...
Click to collapse
Sir all themes working well. i just uploaded dark theme.
u can use rev 1 themes also on rev 2.
working on TWRP 2.8.5.0 so forgot to upload other themes.
u can download from here.
Eventually i increase the action message font and i forgot which ui.xml i used, still searching for it.
TWRP 2.8.5.0 booting but cant flash any ROM but recovery flash, wiping is working normally.
If u can help me with that i can try it.
Thanks.
I would love to see u pressed thanks button sometimes.
just wondering if the rev 2 recovery.img file can be placed inside your TWRP_2.8.2.0_Q3000 play.zip file replacing the twrp v2.8.2.0 recovery.img there.
will flashing that give twrp v2.8.4.0 rev 2 play theme? just a noob-guess! . btw, the ui.zip inside the dark theme zip file of twrp v2.8.4.0 rev 2 is pretty big (8,221,418 bytes).
---------- Post added at 12:57 PM ---------- Previous post was at 12:35 PM ----------
avi3230 said:
....all themes working well......u can download from here.
....i increase the action message font and i forgot which ui.xml i used, still searching for it......
....help me with that i can try it.....would love to see u pressed thanks button sometimes...
Click to expand...
Click to collapse
xolo q3k is not with me. i posted that i've changed my device. so, i don't think i can help you much.
but, when i see some solid work, i hope to get the xolo q3k for testing for a short period.
you know that i've lent you much positive-critical support. and i owe you a lot for helping me in toubled times.
please get that ui.xml and increase the action message font for this rev 2 as well as all your future releases. :good:
p.s.: i see you're doing great. recognised contributor! keep it up! :highfive:
btw, you seem to be in a rush to get to the next level.
waiting for response
m0han said:
....if the rev 2 recovery.img file can be placed inside your TWRP_2.8.2.0_Q3000 play.zip file replacing the twrp v2.8.2.0 recovery.img there.
will flashing that give twrp v2.8.4.0 rev 2 play theme?.... the ui.zip inside the dark theme zip file of twrp v2.8.4.0 rev 2 is ....8,221,418 bytes....
..please get that ui.xml and increase the action message font for this rev 2 as well as all your future releases......
Click to expand...
Click to collapse
@avi3230, expecting you to respond. i checked out your link; but, not sure how to use the template(?). suggest you upload the themed zips.
m0han said:
@avi3230, expecting you to respond. i checked out your link; but, not sure how to use the template(?). suggest you upload the themed zips.
Click to expand...
Click to collapse
Sir first flash the recovery with dark theme (flashble zip is attached so u can flash from any recovery)
Download play theme zip from above given link.
Rename this zip to ui.zip.
Now copy and replace in ur
Internal storage/twrp/theme/ folder.
Or replace in dark themed recovery.zip inside
Emmc/twrp/theme. Folder
In both cases u will find ui.zip already there u need to just replace.
I am in transit so cant upload now.
Wil upload after 9 pm only.
Thank you
Sorry for inconvinence.
m0han said:
@avi3230, expecting you to respond. i checked out your link; but, not sure how to use the template(?). suggest you upload the themed zips.
Click to expand...
Click to collapse
here r the flashble zips - also updated on thread of flashble zip
TWRP 2.8.4.0 Rev 2 -------2.8.4.0 rev 2 dark theme-------2.8.4.0 Rev 2 light theme-------2.8.4.0 Rev 2 Play theme
avi3230 said:
here r the flashble zips - also updated on thread of flashble zip.....2.8.4.0 Rev 2 Play theme
Click to expand...
Click to collapse
tried this, and boy, was i in for some shock! think i'll let the screenshots speak for themselves....
TWRP v2.8.4.0 Rev.1 (2) brought woes.
TWRP v2.8.2.0 brought back relief! :good:
mounting usb otg in TWRP v2.8.4.0 Rev.1 (2) is cumbersome. no way to get back to the previous screen after mounting, except by clicking the back key of the device. the back arrow at the top left does not work.
and i couldn't find the usb otg drive listed anywhere (as opposed to the case of TWRP v2.8.2.0, where you see it listed everywhere). others can try this recovery and correct me if i'm wrong.
more importantly, it'd help the dev do things better/properly. (although i took a screenshot it doesn't seem to have worked.) the device is back on 'twrp v2.8.2.0 play edition by avi3230'.
not sure when i can test further, but i'll be willing to help when possible. in the meantime avi3230 can concentrate on quality rather than quantity, imho. thanks, anyway.
@m0han
Yeah u r correct sir.
First its my mistake - as i used the zip of rev 1 and i replaced the zip and not the recovery in flashble zip so u see its rev 1.
U cant see some buttons cause the theme is meant for rev 2.
In each update of TWRP there is change in backup folder (which i cant define) so it wont detect previous backups.
u need to manually move the backup to respective folder when u upgrade.
Dont worry usb otg works properly in rev 2. u need to use back button to go back. I already made a video of that but not uploaded.
This happens because no one has even tested the recovery. There are more than 70 downloads of the img file but no one even reported.
Sorry for the inconvenience caused.
I am also learning by mistake, hope u understand what i am saying.
avi3230 said:
....u r correct.....no one has even tested the recovery. .....more than 70 downloads of the img file but no one even reported.....
Click to expand...
Click to collapse
that's sad. but, i think i know the reason - and i've stated it before. you're dishing out stuff (even partly cooked) in such quick succession that people can't even decide what to go with. i'm sure you yourself don't get time to test your work - you don't have the device with you full-time. and, frankly, the responses to your releases show that your users are not entirely satisfied. if you're keen to do a better/proper job, you may consider my advice suggestion in the proper spirit - "concentrate on quality rather than quantity". i notice that quite a few others have also opined so.
avi3230 said:
....As the number is more there bound to be the issue of repetitiveness and similarities.....
Click to expand...
Click to collapse
also, the issue of errors/bugs.....
lastly, just want to make a subtle observation: although i was the first among 70+users to give you a detailed feedback, which you found 'correct', you haven't 'thanks'ed me. i usually press thanks for work that has benefitted me as well as the user community for any device or some post that throws light on a matter of general/popular interest. so, continue your good work and the thanks will gush forth. just don't keep looking out for it. don't thank me just 'cos i said this; you know i'm not the kind who solicits thanks.
@m0han
Thanks for trying the recovery and pointing out the mistakes.
Links are corrected with proper recovery version.
I am just trying to learn things here nothing else so mistakes will happen from my side, i apologize for it.
I am just trying my level best.
The sad part is users only replay when they are not satisfied.
Right now i cant thank u cause my today's quota of thanks is already over.
avi3230 said:
.....Links are corrected with proper recovery version.....trying to learn things here....trying my level best.....
Click to expand...
Click to collapse
just go easy on releasing and hard on learning. forget thanking me. :good:.
a couple of suggestions:
1. provide md5 checksums. (i got d9e07dfe97cc26795f1f5f374df89ed0 for the latest one.) would help distinguish the various versions, esp. if there's no change of filename
2. please provide screenshots - at least the ones of the troublesome screens, if not exactly like mine.
"in each update of TWRP there is change in backup folder" - are backup location and usb implementation hard-coded in the recovery? i ask again what i asked here: what could happen if the (rev 2) recovery.img file is placed inside your TWRP_2.8.2.0_Q3000 play.zip file replacing the img file there and flashed? will that give me Q3000 backup folder and the usb otg implementation? . these are noob thoughts, but, i await your answer.
hi @avi3230, i've just sent you a pm. please respond. thanks.. posted in (common) recovery collection thread.
md5 mismatch
avi3230 said:
TWRP RECOVERY - 2.8.4.0 Rev 2- XOLO Q3000 with OTG support....
Click to expand...
Click to collapse
the 'TWRP 2.8.4.0 rev 2.img' from this op has md5 c5d180bc6cdde26541421a220e1a37d9.
the 'recovery.img' inside the '2.8.4.0 Rev 2 Play theme' linked to here has md5 c3b809c3081cd04b4a77446fe69db590.
there is a mismatch. which one is the proper fully-working 'TWRP 2.8.4.0 Rev 2'?
@avi3230 / somebody, please confirm which file (img or zip) to use to avoid troubles. thanks.
None of the two files have any trouble.
Using this recovery, it's working fine, thanks ?

Categories

Resources