[CWM][TWRP] Recovery for ZTE Momodesign MD Smart - Miscellaneous Android Development

I leave below 3 recoveries that you can flash from TWRP or CWM recovery:
- TWRP
- CWM
- STOCK: (for warranty purposes)
CREDITS:
- All xda devs!
- Russian Master Shifu Javum for compiling TWRP V2.5.0.0 & Russian Master Shifu Michfood for the Repack Utils that I used to port these recoveries
Write a request here if you want to share my work after modifying it and keep credits
It took from me a lot of time and hard work to achieve these results :victory:
Press thanks button please if this work was useful to you!!

Related

[RECOVERY] Carliv Touch Recovery for ZTE V967S v2.5 and 1.5

This is my recovery, for ZTE V967S.
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.
The touch module is inspired mostly by scanno touch recovery for Advent Vega and cleaned up and modernized with some stuff from Cannibal Open Touch Recovery. The full touch module is developed by Napstar from UtterChaos Team - Napstar touch recovery, adapted, modified and improved in some parts by me.​A big THANKS to Napstar for his full touch source. ​
FEATURES
To be able to use Aroma File Manager, for which you can find an entry under Carliv menu in recovery, you need to go to amarullz thread and download the version 1.80 of aromafm.zip, because as BOND has discovered this version will be full touch. Rename it to aromafm.zip, make a folder named ".aromafm" (notice the dot before aroma) in clockworkmod folder on sdcard, and copy aromafm.zip in .aromafm folder. Now you can browse your phone without rebooting to Android or connecting the phone to computer.
For porting, unfortunately there are same limitations as in COT recovery - your phone resolution. ​
The most important thing is that you will use from now on the same folder as previous CWM Recoveries, same backups, same settings. Is very good and stable recovery.​
Credits:
Clockworkmod team
Napstar
scanno
ProjectOpenCannibal
C3C076
bgcngm
amarullz​
Carliv Touch recovery v1.5 - only navigation touch menu
The new version 1.5 can be downloade from OP.
Basically is CWM 6+ with touch buttons menu. It has all functionality of CWM Recovery, and I added extra, Aroma File Manager support.
The touch module is inspired mostly by scanno touch recovery for Advent Vega, but also Napstar touch recovery, and cleaned up and modernized with some stuff from Cannibal Open Touch Recovery.
This is not a modified COT recovery. You won't find here settings or theme or some other cool stuff they created for COT recovery. For that go to COT Recovery thread. I made this recovery to keep it simple and slim, because MTK phones have a limited size recovery partition. As I said, is a CWM modded recovery with touch screen menu buttons. Also I kept the Go Back entry in menu, just in case if for some devices is not working the touch menu (brocken or something) - in that case it will be just a good CWM recovery.
Video will be added soon.
carliv said:
Reserved...
Click to expand...
Click to collapse
Good Job, I will try this asap...
Why don't you try to make TWRP recovery to this phone...?
I think TWRP has a better UI than CWM
triwira said:
Good Job, I will try this asap...
Why don't you try to make TWRP recovery to this phone...?
I think TWRP has a better UI than CWM
Click to expand...
Click to collapse
You didn't pay attention at what I said:
I made this recovery to keep it simple and slim, because MTK phones have a limited size recovery partition.
Click to expand...
Click to collapse
The MTK6589 Phones have a recovery with size of 6.2 Mb, and if we took down reserved space from it, it will remain a recovery with 6080-6090 Kb in absolute size. Anything bigger than that won't boot. I know there are some guides on how to increase recovery size modifying scatter file, but that didn't work in my phone (I guess because this phone doesn't have a stock ROM in SPFlashTool format). And also rua1 said that modifying only scatter won't be enough.
So, why make my life complicated when I can simplify it
Nice work!
I'm now running your ported COT on my FAEA F2 and I like it a lot!
I'll be waiting for you to port this one for 1080x1920 resolution so I can try it as well!
can you share your aroma file manager 1.91?.. also i will be waiting for your hd version of this recovery.
carliv said:
You didn't pay attention at what I said:
The MTK6589 Phones have a recovery with size of 6.2 Mb, and if we took down reserved space from it, it will remain a recovery with 6080-6090 Kb in absolute size. Anything bigger than that won't boot. I know there are some guides on how to increase recovery size modifying scatter file, but that didn't work in my phone (I guess because this phone doesn't have a stock ROM in SPFlashTool format). And also rua1 said that modifying only scatter won't be enough.
So, why make my life complicated when I can simplify it
Click to expand...
Click to collapse
Ok, thank you very much for the explanation, I have no experience in it, but I can understand.
So, I think Carliv Touch Recovery is the only choice if I want to use Touch version of recovery...
Will test & create video to show others how this Touch Recovery works on Blu Life Play or other MTK Devices.
SystemErrorOne said:
Will test & create video to show others how this Touch Recovery works on Blu Life Play or other MTK Devices.
Click to expand...
Click to collapse
Sure, but you need to port it first for phone resolution. And the "key test" doesn't work because I remaped keys for touch panel - I should correct that in next release. Or, of course, you can build it from source and repack it after to work in mtk devices.
Thanks!
Thread closed at OP request
Regards
Sawdoctor

12,5,14[Saga] CWM 6.0.4.8 Advanced Edition / PhilZ Touch 6.41.5 (libtouch_gui 1.21)

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
CWM Touch for Ace was a bit old and outdated compared with others recoveries. Now it seems one of the most functional.
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.
USB mount not working
device will go into recovery by itself when charging
one thing need to tell you, you can't use this recovery flash a aroma2.56 package just like this http://forum.xda-developers.com/showthread.php?t=1960734, maybe need update aroma to 2.70B4.
Don't PM me about this recovery,just post at this thread.
If you like my work,please click on the “Thanks” button on the left.
Instruction:
For Unlocked Users:
Download recovery Image and adb tools,
Rename this Image to recovery.img ,Put in
Open the device's USB debugging, run "Run me.bat".
Then will automatically flash recovery.
Click to expand...
Click to collapse
Download links:
http://d-h.st/pkh
Changelog:
http://forum.xda-developers.com/showpost.php?p=39433912&postcount=5
Githubs:
CyanogenMod
SAGAAIO
Phil3759
Thanks and credits:
Phil3759
Andromadus
devil-kin
CodeAuroraForum
BananaGranola
Epic Beard Men
eXistZ
Flemmard
Flinny
Juansheng
paulb_nl
randomblame
synergye
Koush for having created and maintaining cwm
Cyanogenmod for making all this possible
ClockworkMod
Dees_Troy from TWRP team for pigz source and many great ideas in their recovery + source for backups compatibility
kbc-developers for the base semi-touch code and much more
[email protected] for his great job / support
sk8erwitskil for his recovery source, a great place to start learning
shoe63 for his help from the start across many devices
dougiebee for his work on fixing time on many Qualcom devices
Chainfire for his support (stock recovery flash) and all his work for the Android community
All the rest that have helped to construct these builds and develop software for ace directly or indirectly in the past.
A special thank also to the below, and ALL who I do not mention but did contribute a lot with their efforts

[EOL][RECOVERY] Modified CWM (non-touch) for port to all MTK phones[EOL]

This is a Clockworkmod modified (very) recovery.
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 (21-apr-2015):
This is the last batch of builds for porting. I won't do that anymore.
- new GUI theme;
- an extra version with swipe touch support;
- cleaned up the source code;
- reset battery stats option;
- wipe all - preflash option;
- removed nvram backup/restore because it can corrupt the bootloader;
-full track of changes here.
I used it as base for my touch recovery. Basically is a CWM 6.0.3.7 for jellybean and CWM 6.0.5.1 for kitkat modified by me with many extra features.
- aroma file manager menu
- rainbow mode menu
- separate power menu
- separate wipe menu
- nvram backup/restore menu
- advanced backup/restore menu
- toggle signature, toggle md5sum.
To port it follow my new guide from here
All screenshots are made with my new tool from here.
For jellybean version currently there are two lunfile paths in the world of mtk phones. This will make your USB Mass storage to work in recovery or not. Search that path in your device to see what you have.
Lunfile path 1 (old): "/sys/devices/platform/mt_usb/gadget/lun%d/file" - this can be found in many devices mt6572, mt6589, mt6589T, and other old ones.
Lunfile path 2 (new): "/sys/devices/platform/mt_usb/musb-hdrc.0/gadget/lun%d/file" - this is related to new devices mt6582, mt6592...
Find where is your path and download the image to port from correct section.
Depending of your resolution width, choose an image which contains exactly that value or one close to it, and follow the tutorial to port it.
CREDITS:
- Philz-cwm6 - for get partition size method;
- C3C0 - for initial mtk tweack hint - Unused now;
- Koush and all CWM team for the recovery;
- bgcngm for unpack/repack utils;
- sk8erwitskil for aromafm menu
RULES for posting your ports!
If you managed to port this to your device, add proper credits in your thread, post or article.
List of compiled or ported recoveries for various devices.
Lenovo S660 (CN version S026)
THL T100S
THL T11
Elephone P7 mini
Bluboo X1 (mt6582)
Doogee Rainbow DG210
Kuphone 1phone 5s (sanstar72_wet_jb3)
iNew V3 for fw versions up to 1.0.7 (different kernel)
ONN M7 tablet
ZTE V967S
XOLO A500s
XOLO A600
ZOPO ZP999
LAVA Iris 458Q
Wiko Darkfull
Elephone P6000
Ulephone Be Pro
Acer Liquid Jade S (S56)
Acer Liquid Z410
Nvm. Got a black screen same with CTR recovery. Any help?
gatgat23 said:
Nvm. Got a black screen same with CTR recovery. Any help?
Click to expand...
Click to collapse
Usually that means the recovery is bigger than the recovery partition. It happens in some devices with an unusually big kernel (I saw kernels with 4.7 Mb for a recovery at 6 Mb - not much room for ramdisk). Other thing is if you use MobileUncleTools to flash it - this doesn't work in some cases, and you need to flash it with SPFT. Remember, if you have a small partition, any recovery bigger than 5.9 Mb (you need some reserved space) will not work. You can try to shrink some images, or to replace them with blank dummy pngs, but not for stitch and buttons. These have to remain in rgb format, otherwise you have that black screen again, and the phone will reboot to system.
carliv said:
Usually that means the recovery is bigger than the recovery partition. It happens in some devices with an unusually big kernel (I saw kernels with 4.7 Mb for a recovery at 6 Mb - not much room for ramdisk). Other thing is if you use MobileUncleTools to flash it - this doesn't work in some cases, and you need to flash it with SPFT. Remember, if you have a small partition, any recovery bigger than 5.9 Mb (you need some reserved space) will not work. You can try to shrink some images, or to replace them with blank dummy pngs, but not for stitch and buttons. These have to remain in rgb format, otherwise you have that black screen again, and the phone will reboot to system.
Click to expand...
Click to collapse
My device's recovery partition got 6MB. Ported recovery got 5.4MB.
I actually used MobileUncleTool to flash, then I tried to flash using SPFT.
Same issue, black screen. Need to reinsert battery to reboot.
gatgat23 said:
My device's recovery partition got 6MB. Ported recovery got 5.4MB.
I actually used MobileUncleTool to flash, then I tried to flash using SPFT.
Same issue, black screen. Need to reinsert battery to reboot.
Click to expand...
Click to collapse
Try to access the recovery log from temp directory (cache/recovery/last.log), after that happens. If there is nothing there, than the phone didn't even boot in recovery, otherwise you will see where it's stuck.
I think it actually didn't boot recovery.
Log's showing what I did when I was still on Stock Recovery. (Wipe data/cache)
Even the .prop values are using stock ones. (I changed adb secure, debuggable, etc in the one I ported.)
hello carliv,
is it possible to have a version 1.4 with custpack?
@carliv
Thanks for your activity.
Are this recovery compatible with most recent Mediatel ROM based on Android 4.4?
bovirus said:
@carliv
Thanks for your activity.
Are this recovery compatible with most recent Mediatel ROM based on Android 4.4?
Click to expand...
Click to collapse
All my recoveries are compiled on cm-10.1 building environment and in theory they will work better with kernels built for android 4.2 top (in these builds are missing sepolicy files and all selinux related files), but some users report that they used it for flashing and backup lenovo kitkat (vibeUI something) and it was successfull. I can't test that, but my advice is if you have an official Android 4.4 mtk powered phone, I'm sure the recovery partition is bigger than 6Mb, and for that I would recommend you PhilZ recovery if you want to stay on CWM base, or TWRP. I made my recoveries with only one reason in mind: to be small enough to fit a recovery partition of 6Mb.
Thanks for the explanation. What's about Androdi 4.3 compatibility? Like 4.4 ?
Recovery compatibility
Android 4.2.x - OK
Android 4.3.x - ?
Android 4.4.x - ?
Note: personally I like the non touch recovery.
Do you have a link for Philz recovery for Mediatek chipset?
Thanks again.
bovirus said:
Thanks for the explanation. What's about Androdi 4.3 compatibility? Like 4.4 ?
Recovery compatibility
Android 4.2.x - OK
Android 4.3.x - ?
Android 4.4.x - ?
Note: personally I like the non touch recovery.
Do you have a link for Philz recovery for Mediatek chipset?
Thanks again.
Click to expand...
Click to collapse
I think it should work in Android 4.3 but I have no feedback on it. The reason is there are very few mtk devices with Android 4.3 or 4.4 (real not spoofed), and I didn't tested personally any of them.
For PhilZ recovery you can check his official thread http://forum.xda-developers.com/showthread.php?t=2201860 , that support mtk devices nativelly, but you must compile it in cm-11 source,
or the mtk dedicated one started by my friend @yuweng here http://forum.xda-developers.com/showthread.php?t=2748169
The PhilZ recovery require many times a recovery partition bigger than 6MB.
In many acses teh recovery partition is limirted to 6MB.
For this if you can create your recovery from CW11 (compatible with KK) you can sue it.
bovirus said:
The PhilZ recovery require many times a recovery partition bigger than 6MB.
In many acses teh recovery partition is limirted to 6MB.
For this if you can create your recovery from CW11 (compatible with KK) you can sue it.
Click to expand...
Click to collapse
If a mtk phone gets Kitkat then I assure you the recovery and boot partition will be increased by producer in that firmware along with the new kernel. The 6Mb partition is specific to 4.1.x-4.2.2 devices. For these even my recovery, if it's built in CM11, will oversize 6 Mb because of the new modules.
gzip support
Thanks for this non-touch version! Can you update to include the gzip support as in the latest touch version? Thanks.
Hey Sir @carliv.
I ported this recovery to Xolo A500s.Please add it device list.
Here is the link:-Click here
port
Hi Sir ,
I ported it for my device XOLO A600
Please update it in device List .
Thanx Again
Here Is the Link
CWM Recovery MTK 6.0.3.7 carliv non-touch
Hi all!
I just combined some scripts to have a auto make custum recovery.
It is based on BM / michfood / yuweng / carliv work! Version 2014-06-29. See beginning of this thread.
Thank you!
usage: cwmr.bat stock-recovery.img
MTK6575 and MTK6577 tested. May work with MTK6589... (option 3 -> MTK6577)?
It is a question if fstab is matching. It is complete batch source, so you can adapt to alternate partition tabel.
Have fun!
EDIT:
What I did:
I took "old lunfile path" "normal font" file from carliv first thread, I extracted it and added to some old scripts from yuweng (I cannot find anymore to download). I tested it and made it public to all.
The latest CWM is 6.0.4.4 and Carliv release this update. Should be possible to aplly it?
Well, I am not sure about what I understand. You can use my upload and mod it any way you like. I hope to have helped to get latest CWM Recovery.

[recovery][philz-touch][gt-s7270]

PhilZ Touch Recovery
for
Samsung Galaxy ACE 3 (GT-S7270)​
NO SUPPORT FOR F2FS​
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.
Also, do not forget the powerful aroma file manager integration and double tap shortcut.
>> Developers Info + Device Request <<​>> Special Features Guide <<​>> How to Install <<​>> Change Log <<​>> FAQ <<​
​
DOWNLOAD
GT-S7270_PhilZ-Touch-Recovery_6.59.0.zip
Recovery.tar.md5.zip
aromafm_logan.zip
Note:
GT-S7270_PhilZ-Touch-Recovery_6.59.0.zip needed to flash from a current running custom-recovery like e.g. TWRP or CWM.
Recovery.tar.md5.zip inlcudes the flashable *.tar.md5 to flash using Odin. Extract the zip only once!
bug :
Let me know if you find it
Special thanks to : Allah SWT and Nabi Muhammad SAW
CREDITS :
cyanogenmod team
ZIM555
Phil3759
@CTXz
@cleverior.ipul my inspiration
andii_nr
IF YOU WANNA RESHARE THIS RECOVERY, PLEASE FOLLOW THIS RULES :
DON'T USE SHORTENER LINK (i.e. adfly, adfoc, etc)
DONT REUPLOAD MY RECOVERY BEFORE ASKING PERMISSIONS

[DEV][MT6582][3.x]Team Win Recovery Project for Symphony M1[2016-10-01]

[MT6582][Development][RedThemed][BETA][3.x]Team Win Recovery Project for Symphony M1
Hey Everyone!
Assalamu Alaikum guys
This is just a TWRP recovery made for Symphony M1, flash it via Mobile Uncle tool, or Rashr, or flashify or any flashing tools or via adb push, your choice!
About TWRP:
Team Win Recovery Project 3.x, or twrp3 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.
Requirements:
--Rooted
--SuperSU recommended(didnt try with Kingroot, but that should work too! )
Installation:
Method 1:
1) Install Rashr from Playstore
2) Open it, select Team Win Recovery Project for Symphony M1
3) When prompted to go on recovery, select yes and voila you have installed TWRP on your phone
4) Enjoy!
Method 2:
1) Download Mobile Uncle tool
2) Select and flash recovery file from downloads
Downloads:
Download here
Bugs:
--cant mount internal storage, so you have to use external sdcard for backup and flash procedures
SUPPORT for TWRP Dev:
Live support is available via #twrp on Freenode with your IRC client or just click this link. And hit THANKS on threads :3 [/QUOTE]
Credits:
@Allah SWT(For helping me, he is the best programmer)
@Dees_Troy
@raisul2010.5396​
XDA:DevDB Information
[DEV]Team Win Recovery Project for Symphony M1[2016-10-01], Kernel for all devices (see above for details)
Contributors
raisul2010.5396
Source Code: https://github.com/TeamWin/Team-Win-Recovery-Project
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 2016-10-03
Beta Release Date: 2016-10-03
Created 2016-10-03
Last Updated 2016-10-03
Reserved
For changelog

Categories

Resources