Database Info

[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

[RECOVERY] [ROM] Wiko DarkMoon (MT6582) [MULTILANG]

DISCLAIMER:
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* DO NOT LEECH MY DOWNLOADS, PLEASE RE-DIRECT YOUR FORUM /PAGE
* TO THIS THREAD, IF YOU LIKE MY WORK, YOU CAN SAY THANKS,
* AND MAYBE BUY ME SOME BEERS
*/
Hello Guys !
In this thread you will find my custom ROM And Recovery for the Wiko DarkMoon
Please be sure to read (and re-read) this carefully in order to avoid unnecessary questions.
Instructions and Frequently asked questions (FAQ):
For Instructions jump into post #2.
FAQ jump into post #3.
Wiko DarkMoon internal memory re-partition, jump into post #4.
How to Revert to the STOCK Rom / Recovery / Partition Layout, jump into post #4.
​
Recovery INFO
The salient features of Carliv Touch Recovery include:
Based on CWM 6.0.4.4
Full Touch Support
With features of Cannibal Open Touch
Aroma File Manager Support
Support for both Edify and Amend scripting allows flashing all ROMs
Touch screen button controls
Advanced Backup
Advanced Restore
Delete old backups
Persistent settings
User-defined backup locations
ADB Sideload
Update CTR v2.5 (30/07/2014)
Changelogs:
New Menu Layout
Tar + Gzip Backup Compression : ( "Backup/Restore" -> "Default Backup Format" )
Your Backups will be smaller now, just like on the old native CWM
Removed "wipe all" option from wipe menu ( if you need to wipe system, use "format system" from "mounts/storage")
Rearanged menu order in root menu to restore CWM order
There's now an "nvram backup/restore" menu in "carliv" section
The nvram partition will be backed up in clockworkmod/backup folder as nvram.img. This will help if you lose IMEI and other communication features. It will work only if you have the nvram partition of size 0x500000 (check your scatter) and if you have the nvram defined as /dev/nvram path in recovery.fstab. If the nvram partition is damaged (as in flashing an oversized recovery) this will not help you, and you need SPFlashTools to reflash with format your phone official firmware, and after that flash this recovery, boot in recovery and restore nvram.
some other small changes.
​
Changelogs
Android 4.2.2 (JB) Based custom ROM:
Changelog Build v1.0 (February 22 2014)
Based on official Android 4.2.2 ROM (WIKO DARKMOON Version 8)
Kernel 3.4.5
Custom Mods:
User customize-able installation based on AROMA installer
Pre-rooted with SuperSU (v1.93)
Debloated
Added BusyBox (v1.22.1 - Stericson)
Added Ad blocker (patched "host" file)
Ziplagned apks (better performance)
init.d support with performance scripts
Network, wifi, power saving, and several other tweeks
Updated APN's from CyanogenMOD repo
Added Performance Control (several CPU/System Mods)
Added in-built Xposed framework and Latest Gravity BOX module v2.9.7 (Several System Mods)
Acess To the Mediatek MTK Eng Mode
Added the following Android 4.4 KitKat Goodies:
Apps (Including Google Launcher - GEL, with Voice Search )
Bootanimation
QuickOffice
And other necessary system files
Kernel:
Insecure
Removed Mediatek debugger (mtk.aee.aed Daemon; etc)
USB Mass Storage as Default (instead of MTP)
​
GPL Compliance:Kernel 3.4.5
Github Kernel Repo​
Downloads:Dev-Host
WIKO_DarkMoon_JB_4.2.2_Stable_v1.0.zip - 386.12 MB
Mod_extended_USRDATA_2.5GB.zip - 7.07 MB
MT65xx_USB_VCOM_drivers.zip - 403.65 KB
Wiko_Recovery_and_FlashTool.zip - 12.54 MB​
Credits:
SuperDragonPT
Wiko
Carliv (Awesome CWM based Recovery)
iBotPeaches, brut.all (for apktool)
amarullz (for AROMA Installer)
Chainfire (for SuperSU)
rovo89 (for the AWESOME Xposed Framework), Learn More Here
C3C076 (For the AWESOME Xposed GravityBox module), Learn More Here
bgcngm(For Maintaining the Gbox JB Branch)
h0rn3t and educk (for Performance Control), Learn More Here
XDA:DevDB Information
[RECOVERY] [ROM] Wiko DarkMoon (MT6582) [MULTILANG] , ROM for the Android General
Contributors
superdragonpt
Source Code: https://github.com/dragonpt/Kernel_Wiko_DarkMoon_Custom
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2014-02-22
Created 2014-02-22
Last Updated 2015-02-14

How to flash custom recovery:
Make Sure your Phone is fully Charged
Make an Full Backup of your files (Photos/Contacts, etc)
Download The MT65xx_USB_VCOM_drivers.zip
Install The Mediatek VCOM Drivers (For Detailed Drivers instalation Instructions, please check this thread)
Download The Wiko Recovery and FlashTool
Extract the .zip and you'll see two folders "Recovery" and "SP_Flash_Tool"
Open "SP_Flash_Tool" > Flash_tool.exe > Scatter-Loading> And select the "MT6582_Android_scatter.txt" from the "Recovery" Folder
Turn OFF your Phone
Press "Download" (don't worry with the pop-up "Download-Warning" Message), press YES
Connect Your Phone to PC (Turned OFF) , The Flash Progress should beginn, when its succesfully Finished A Green Ring will shown.
Congrats The Recovery is installed
​How to enter into recovery mode:
With the Phone completely turned off...
Press and hold VOL. UP + VOL DOWN + POWER keys and turn on the phone.
Keep holding the keys, wait until you see on Phone:
Code:
"Recovery Mode: Volume UP"
"Factory Mode: Volume Down"
Then Press on VOL. UP key, and Recovery will load.
​Navigation under recovery mode:
As soon as the splash logo disappears, Carliv Touch Recovery menu will appear. Navigation is Full Touch.
You can also use VOLUME keys (navigate up with VOL. UP and navigate down with VOL. DOWN) and POWER key to apply the action.
Scroll Pages under Recovery: To Scroll page down you have to swipe right, and for scroll page up to swipe left. Also swipe left for Go Back.
Aroma File Manager:
This Recovery Supports the Aroma File Manager
Whats this? Check here
Download the Aroma File Manager
Then just copy the aroma .*zip into the "Clockworkmod" folder on the root of your SD Card
​Flashing The ROM:
Copy The ROM to The External SDCard
On Recovery:
Wipe Menu> Wipe All Data - PreFlash (Select YES - Wipe All)
Wipe Dalvik Cache (Select YES - Wipe Dalvik Cache)
Install zip > Choose zip SDCard (Select the location of the ROM.zip)
And Follow The On-Screen AROMA Installer Instructions
In the End the Phone will Reboot Itself
The first Boot will take some minutes (it's normal)
​

F.A.Q
Q: How Can i acess The MTK Eng Mode?
A: GravityBox >Engineering Mode
Q: What Mods can i do on the Eng.Mode?
A: There are alot of things you can do, the two most common are:
Increasing volume Level:
MTK Menu> Hardware Testing> Audio> On the "headset mode" and "LoundSpeaker Mode" set max values to 145 (The max is 160, but i dont advise it, stay safe and use the 145 value)
Speed up the GPS reception :
(Before Going to the MTK Menu)
Open the app "FasterGPS", and give it root permissions
Choose your Continent, your region (at this point, your gps is properly configured with your country *.ntp values)
(Now on MTK Menu ...)
MTK Menu> Location> Location Based Service> On the "AGPS" tab, tick the "Enable A-GPS", and on the "EPO" tab, tick "Enable EPO" and "Auto Download" , this last option will download the EPO files it requires an data connection.
Start the app "GPS Status", in the first Satts Lock, you need to wait a little bit (it can take up to 15m, be sure you are in an Open Area).
When you get an good lock, on Satts, your DONE.
A: I dont see the Development Options, how can i acess it?
Q: Unlocking the Development Options:
Go to "Settings" > "About Phone"
Then tap 7 times on the "Build Number"
Q: Where are the Development Options?
A: Settings> Developer Options
Q: What is the Performance Control?
A: Its an Control Panel, where you can Change / managed the CPU Governors/ IO Shedulers / among several other things.
Q: The Launcher sometimes seems an bit laggy
A: Go to Settings> Developer Options> on "Window animation scale" set it to .5x, and on "Transition animation scale" set it to .5x
Q: I really like your work, how can i thank you?
A: You can press the "THANKS" button, and if you want, you can donate some beers to me ​

Wiko DarkMoon internal memory re-partition
Mod Extended Userdata v1 ( 2GB ) --> Removed / Use the v2
This Mod will extend userdata partition to 2GB (stock size is 1GB) and the rest of the space will remain for the internal sdcard
NOTE: Make an FULL backup of your Rom under Recovery, and don't forget to also backup your Internal SDCard since it will be full erased
Instructions:
Download the Mod extended USRDATA.zip
Shutdown your phone
Extract the .zip
Open SP_Flash_Tool dir > Flash_tool.exe
In scatter-loading load the MT6582_Android_scatter.txt from the Internal_2GB_Mod Dir
Press Download
After flashing is complete, boot into recovery mode and format /data (under Mounts and Storage Menu)
Optionally, if you want to restore previously saved userdata, go to backup / restore > and restore data (advanced restore feature)
Profit
​
Mod Extended Userdata v2 (2.5 GB)
This Mod will extend userdata partition to 2.5GB (stock size is 1GB) and the rest of the space will remain for the internal sdcard
NOTE: Make an FULL backup of your Rom under Recovery, and don't forget to also backup your Internal SDCard since it will be full erased
Instructions:
Download the Mod extended USRDATA_2.5GB.zip
Shutdown your phone
Extract the .zip
Open SP_Flash_Tool dir > Flash_tool.exe
In scatter-loading load the MT6582_Android_scatter.txt from the Internal_2.5GB_Mod Dir
Press Download
After flashing is complete, boot into recovery mode and format /data (under Mounts and Storage Menu)
Optionally, if you want to restore previously saved userdata, go to backup / restore > and restore data (advanced restore feature)
Profit
​
Reverting to the Stock ROM
This will revert back your phone to STOCK (including the stock recovery), in case you need to send your phone to the Service Center
Instructions:
Go to Wiko's website and download the latest Rom Version:
http://fr.wikomobile.com/maj.php?telephone=131
Follow the instructions given ...
Older instructions:
Download the DARKMOON_JB4.2.2._Stock Rom-wiko_rev8.zip
Use the SPFlashTool that i provided with the CWM Recovery .zip
Make sure phone is fully charged
Shutdown your phone
Extract the .zip
Open SP_Flash_Tool dir > Flash_tool.exe
In scatter-loading load the MT6582_Android_scatter.txt
Press Download
After flashing is complete,you'll see an green circle
Profit

Thanks. Can you add some screenshots?

h3lder said:
Thanks. Can you add some screenshots?
Click to expand...
Click to collapse
Was Uploading, check under the ScreenShots TAB
Regards

I doubt:
on step "How to flash custom recovery" - before you can do this you need to have already rooted the device?
can you please add how to root the device? it will be nice to complete better all the info.. but is already great!
congrats and thanks you! as soon as i by my wiko darkmoon i will definitely try it!

sapoide said:
I doubt:
on step "How to flash custom recovery" - before you can do this you need to have already rooted the device?
can you please add how to root the device? it will be nice to complete better all the info.. but is already great!
congrats and thanks you! as soon as i by my wiko darkmoon i will definitely try it!
Click to expand...
Click to collapse
Hi
You can root with framaroot, but i dont think thats necessary.
Just flash The recovery, then The ROM.
Regards

superdragonpt said:
Hi
You can root with framaroot, but i dont think thats necessary.
Just flash The recovery, then The ROM.
Regards
Click to expand...
Click to collapse
Ok understood, thanks

Do this rom will work with my Xolo Q700S?
Sent from my Q700S using xda app-developers app

superdragonpt:
Where can you please downloaded the source code for kernel mt6582? Can you give me a link please?
Or: Your sources kernel what you gave to download are original (unchanged)?
Edit:
OK. I found where you can download the source. Sorry for the spam.
http://forum.xda-developers.com/showthread.php?t=2645756
http://forum.xda-developers.com/showthread.php?t=2650513

Hi
You guys are all crazy with the MTK leaked sources, but do you even have an clue what those sources are?
You cant just compile an source that's customize for other phone , thinking it will work on yours.
There's a lot of work to be done, and you need an huge amount of luck to have your phone drivers available in that source.
This said, I will appreciate that people avoid off-topic and other phones talk in this thread.
This ROM and recovery will only work on wiko darkmoon and Micromax a200 (clone).
If your using this ROM as a base for another MT6582 phone, please be an gentlemen and give proper credits.
Regards

Added Internal USRDATA Mod to the OP
Check post #4
Enjoy

superdragonpt said:
Added Internal USRDATA Mod to the OP
Check post #4
Enjoy
Click to expand...
Click to collapse
Great work, thanks.
Do you know by any chance if there is any option to add languages to this rom? Wiko doesn't include many languages. I can use locale2 from google play, but that only translates some of the functions.

skydancer79 said:
Great work, thanks.
Do you know by any chance if there is any option to add languages to this rom? Wiko doesn't include many languages. I can use locale2 from google play, but that only translates some of the functions.
Click to expand...
Click to collapse
The ROM is multi language.
What language where you looking for?
Regards

superdragonpt said:
The ROM is multi language.
What language where you looking for?
Regards
Click to expand...
Click to collapse
Slovenian...most android phones have it. Moto G had the same "problem"

skydancer79 said:
Slovenian...most android phones have it. Moto G had the same "problem"
Click to expand...
Click to collapse
Hi
Yes i know, when i made a MIUI rom for my old ZTE v970, i had an hard time trying to find the proper strings for your language.
Even on stock roms from big brands, its very rare to find support for that language.
Im trying to merge and revise some strings from various sources, maybe in an future version.
Regards

superdragonpt said:
Hi
Yes i know, when i made a MIUI rom for my old ZTE v970, i had an hard time trying to find the proper strings for your language.
Even on stock roms from big brands, its very rare to find support for that language.
Im trying to merge and revise some strings from various sources, maybe in an future version.
Regards
Click to expand...
Click to collapse
Great, that would be awsome.
As for rarity of my language, I find it quite well supported. Google Nexus has it, all Samsungs have it, so does HTC, Sony... I know Prestigio and Gsmart have it. CM also. It's not a big deal, but nevertheless - I wouldn't mind having it
Great ROM btw, very customizable.

skydancer79 said:
Great, that would be awsome.
As for rarity of my language, I find it quite well supported. Google Nexus has it, all Samsungs have it, so does HTC, Sony... I know Prestigio and Gsmart have it. CM also. It's not a big deal, but nevertheless - I wouldn't mind having it
Great ROM btw, very customizable.
Click to expand...
Click to collapse
Hi
Well good news and bad news
The good:
I managed to Build an UNOFFICIAL Lewa Rom for our device, currently fixing the lastest issues and adding multi-language support.
So since im currently working on this language strings, might as well use that work for this rom also.
Preview pics:
http://i.imgur.com/VAGpQI3.png
Http://imgur.com/1IADxZx
Http://imgur.com/1C56EO6
The bad:
From what i gather until now, only about 100 slovenian strings are compatible (this is less than 5% of overall translation files), will keep looking
Regards

superdragonpt said:
Hi
Well good news and bad news
The good:
I managed to Build an UNOFFICIAL Lewa Rom for our device, currently fixing the lastest issues and adding multi-language support.
So since im currently working on this language strings, might as well use that work for this rom also.
Preview pics:
http://i.imgur.com/VAGpQI3.png
Http://imgur.com/1IADxZx
Http://imgur.com/1C56EO6
The bad:
From what i gather until now, only about 100 slovenian strings are compatible (this is less than 5% of overall translation files), will keep looking
Regards
Click to expand...
Click to collapse
So is this ROM fully functional? I mean no bugs? For English language.. I could test it on my Turbo mini

[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.

[TWRP] ported for Blu_Tank-Xtreme-Pro

Old Version
Recovery ported to this device.(Blu Tank Xtreme Pro)
Mtp not working, but adb and backup, restore is fine.
Fstab limited to 3 needed partitions.
1 recovery
2 boot
3 system
Another dev as already hinted to me that he is working on and possibly making progress on fixing the mtp function.
Base recovery was built for blu_max_life by @vampirefo
Some of the ramdisk files files (etc/recovery_fstab) came from other recoveries. So thanks are also needed for @lopestom
See new version at
https://forum.xda-developers.com/android/development/tank-xtreme-pro-recovery-t3716211
.

[ROM][UBIFS]CyanogenMod11_R11_Max_MT6572

#-------------------------Disclaimer----------------------------#
I am in no way responsible for dead NAND/EMMC chips, SD cards Lost basebands, nuclear war or anything else for that matter YOU the users are soley responsible for any and all actions you make the build is 100% tested & confirmed working on UBIFS R11 max chinaphone with board variant Q6_M144_GT-018_MB_1.0
#-----------------------Device info----------------------------#
Android OS : 4.4.2 Kit Kat SDK:19
Kernel Version: 3.4.67
File System: UBIFS
BaseBand CPU: MT6572_S00
BaseBand CPU Secure Version: FF
BaseBand CPU Bootloader Version: 01
Board Variant: HS_Q6_MB_V1.0
Storage Capacity=512Mb (4Gb ext through recovery)
Ram Capacity= 497Mb
Resolution= 480×854
#-----------------CyanogenmodOS--------------------------#
Version = 11
SDK-ver = 4.4.4
SDK-API = 20
B-TYPE = userdebug
Build id = XNG3C
Linux Kernel = 3.4.67
LCD- density = 240
LCD-Dpi = 320
• Deodexed
• IO_scheduler set to CFQ
• Performance adjustments
• Preloaded with Gapps
• Cyanogen account support
• CyanogenMod Logo
• Ram flag optimisations
• Default runtime set to art
• Voice unlock support
• Pre rooted with Cyanogenmod SU 1.34
• addon.d support
• init.d support
• BT NFC support
• addon.d & init.d slinked in cpio in bootimg
• Custom CM bootimg with storage fix.
• Ad and popup blockers
• CM ambient updater
• CM InCallUi
• google voice search
• CM Device management
• CM SetupWiz
• factory test mode [ *#*#0#*#* ]
• CM Live lockscreen
• CM MusicFX
• CM Trebuchet Launcher
• Chrome based browser
• CM Voice +
• Voice command support
• Camera interpolated and tweaked
• camera path changed to added cameraserver in vendor/bin/cameraserver instead of system/bin/mediaserver
• Added Clearmotion props to default & build.prop
• Added Clearmotion config to /etc
• Added Clearmotion support libs
• Added Clearmotion FW to /lib
#---------------------------NOTICE------------------------------#
I do this in my free time DO NOT ask for Eta's,
Includes storage modified CM boot.img which will be flashed with the rom please use the partiton sd card option in advanced options in recovery to make up to a 4096mb /data partition before transferring zip to sd and flashing.
#----------------------------BUGS------------------------------#
• update #003 is having a whinge with storage for downloaded apps from store so they wont install after download will be fixed in build #004,
• NFC is working properly but you must purchase NFC bluetooth module tags to support nfc transfer, i have compiled & added an nfc.ko module to use bluetooth instead of newer modules which use the wifi reciever as the antenna and due to there being no NFC compatibile HW on these extremely poor low end devices i do not wish to see comments about this as a bug.
#-------------------------LINKS------------------------------#
CM CTR recovery.
https://drive.google.com/file/d/1UErBsSe2DLFEtcgwXz-hZR_fQINxpn9H/view?usp=drivesdk
Stock touch recovery to replace original
https://drive.google.com/file/d/14Y-WQHDLfqlEdjmu-PTujNqGkkUpcpLn/view?usp=drivesdk
CyanogenmodOS #001-BETA 20190412
https://drive.google.com/file/d/1Xuf-gSHPHr5CGsZjFu3pgT44FdR5GFx5/view?usp=drivesdk
CyanogenmodOS update #002 20190414
https://drive.google.com/file/d/19Nt1pVo8ruvTCugsgejtMQvJDe2xZIb7/view?usp=drivesdk
CyanogenmodOS update #003 20190504
[ Has play store issue ]
https://drive.google.com/file/d/1D4sCf1oflvSTFJxFzH1WwMJL_1j8H5-G/view?usp=drivesdk

Welcome to CyanogenMod 11

BUILD #002 is up get it from the OP
CHANGELOG
Camera works now with slow motion & fast motion video recording, picture quality is still **** but is tons better than it was on stock rom.
Rebuilt the system layout and merged most /vendor files and folders to /system
Fixed gallery keeps stopping error even though it wasnt
Cleaned up the GUI scaling to produce cleaner icons etc etc changelog is in /etc for anyone that wants to look
Changed the Live lockscreen wallpaper to something much simpler & better looking.
Converted entire system to single sim & removed Gemini where i could & set props to disable what i couldnt find of it, repathed ril to run through mtk-ril.so also added init.volte.rc, volte_imsm.so/volte_stack.files to help ril call clarity as certain parts of the stack are interacting with ril even though its a GSM Radio
Added getenforce & setenforce to /bin and file_contexts to try and get my init.rc props for setenforce to run the kernel permissively for some extra init processes, BUT setenforce for some reason is receiving permission denied cannot symlink so i hope to have this completed & working in build #003
Added /product/build.prop dir to deal with zram for swap & ext4 /data partitiion under logical boot partitions.
Added new android apple crime screen power off logo
Added some misc ringtones, notification tones and ringtones other than the cyanogen tones.

Nice Work Matty1993!!
You have been a busy bee :highfive:

Hello,
I am new to ROMs, Could you give me detailed instructions on how I would install this?
Thanks,
Robby

bigrammy said:
You have been a busy bee :highfive:
Click to expand...
Click to collapse
Haha yeah one of my old projects ive been meaning to get finished for ages, finding out how to attach android to UBIFS on top of UBI was a pain in the ass lol got to experiment with ril on this one as it was dual sim and tried running gemini through it but as it was a source build dual sim compatibility dosent work so had to depract gemini and set single sim still been working on the tuba build tho taking my time with it as sony really like to mix things up, also finishing a lineage OS 14.1 build for Alcatel Pixi 3.5 that was from source also but dualsim works on this one even though this phones a single sim phone haha go figure lol

DJ Robby said:
Hello,
I am new to ROMs, Could you give me detailed instructions on how I would install this?
Thanks,
Robby
Click to expand...
Click to collapse
What model is your R11 max clone phone it must be HS_Q6_MB_V1.0 board revision or it wont boot on your device and i will need to build one for your revision if so as the kernel will be different,
You can find the board variant by taking the backing off the phone and looking at the sim slot see pic attached,
Check this out first or youll brick it 100% i gaurantee it, google how to take a firmware backup using SP flash tool before doing anything SP flash tool can be downloaded from here aswell as the MTK Vcom drivers for flash tool,
https://spflashtool.com
If your board is different i need the BOOTIMG.file from your SP Tool backup so please do this first before anything or i wont be able to build you anything as i need your stock kernel from boot.img to decompile and make changes for my rom aswell as the boot.img is highly modifed with CM source

Hello,
I can't find a number like that, I looked everywhere.
Here is a full backup of the phone: https://drive.google.com/file/d/15P9KutXb0FrxHRTj4qrQ-KW94XA6J2SI/view?usp=sharing
The kernel is the same though because if I go to settings it shows the same kernel number as the one in this post.
Thanks,
Robby

DJ Robby said:
Hello,
I can't find a number like that, I looked everywhere.
I have the boot.img, I will edit this message with the boot.img when I have a chance. The kernel is the same though because if I go to settings it shows the same kernel number as the one in this post.
Thanks,
Robby
Click to expand...
Click to collapse
Hey mate the kernel number may be the same but the config of the kernel will be diff, if it dosent have a number in the sim slot it will deffo not be a HS_Q6_MB you may have the ZMA_12_MB or ZMA_9_MB board
So deffo dont flash any of this stuff if you get me the stock boot.img & recovery img from your R11 max i can build the recoveries and rom for your board revison just upload them here in a .zip file when you get the chance
Thanks

Matty1993 said:
Hey mate the kernel number may be the same but the config of the kernel will be diff, if it dosent have a number in the sim slot it will deffo not be a HS_Q6_MB you may have the ZMA_12_MB or ZMA_9_MB board
So deffo dont flash any of this stuff if you get me the stock boot.img & recovery img from your R11 max i can build the recoveries and rom for your board revison just upload them here in a .zip file when you get the chance
Thanks
Click to expand...
Click to collapse
I added the link to a full backup of the phone through the SP flash tool on my above post which includes the boot.img and recovery.img, Also thanks so much for all the help!

DJ Robby said:
I added the link to a full backup of the phone through the SP flash tool on my above post which includes the boot.img and recovery.img, Also thanks so much for all the help!
Click to expand...
Click to collapse
Hey mate,
Sweet ill get onto it and post link here to a new thread ill make for your variant r11 max.
Ive got a new build just about ready also which is build #003 so ill start your variant from #003 which has vast improvements from build #002
# edit
Glad you didnt flash your R10 is eMMC ext4 fs and not ubifs just finished the boot.img off anyhow

DJ Robby said:
I added the link to a full backup of the phone through the SP flash tool on my above post which includes the boot.img and recovery.img, Also thanks so much for all the help!
Click to expand...
Click to collapse
Try these recoveries tell me if they boot uo and everything is ok with them
Oppo touch recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1ZUZ3jmNhVkWSTB-57ifPh9_Lmm_jjkCB/view?usp=drivesdk
CWM recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1WO44rtoWttfeeAvCdff_97JqbuXboeXB/view?usp=drivesdk
Open sp flash tool & load your scatter file,
Then click on the recovery path and load a recovery into the slot,
MAKE SURE that download only is selected and NOT format all + download this is very very important
Click download with phone switched off plug into pc & recovery will now flash,
Once flash is complete remove then re insert the cord wait for the charging screen to appear,
You can now boot to either recovery by holding the volume up button and power button until the first boot logo appears then release only the power button and keep holding power up to see if they will boot or not,
If they boot all sweet ill upload the rom as its just about finished being built

Matty1993 said:
Try these recoveries tell me if they boot uo and everything is ok with them
Oppo touch recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1ZUZ3jmNhVkWSTB-57ifPh9_Lmm_jjkCB/view?usp=drivesdk
CWM recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1WO44rtoWttfeeAvCdff_97JqbuXboeXB/view?usp=drivesdk
Open sp flash tool & load your scatter file,
Then click on the recovery path and load a recovery into the slot,
MAKE SURE that download only is selected and NOT format all + download this is very very important
Click download with phone switched off plug into pc & recovery will now flash,
Once flash is complete remove then re insert the cord wait for the charging screen to appear,
You can now boot to either recovery by holding the volume up button and power button until the first boot logo appears then release only the power button and keep holding power up to see if they will boot or not,
If they boot all sweet ill upload the rom as its just about finished being built
Click to expand...
Click to collapse
I can try when I get home but I already got TWRP with the Easy Magic Installer except it is an older version: https://forum.xda-developers.com/showthread.php?t=2798257

DJ Robby said:
I can try when I get home but I already got TWRP with the Easy Magic Installer except it is an older version: https://forum.xda-developers.com/showthread.php?t=2798257
Click to expand...
Click to collapse
More or less just to test for device compat is all glad you told me youve got TWRP tho as my rom dosent have mount asserts in the script as they were causing error 7 so ill have to rebuild the meta-inf again as ive got set for perm aswell whereas TWRP uses meta-data to set file permissions

Matty1993 said:
More or less just to test for device compat is all glad you told me youve got TWRP tho as my rom dosent have mount asserts in the script as they were causing error 7 so ill have to rebuild the meta-inf again as ive got set for perm aswell whereas TWRP uses meta-data to set file permissions
Click to expand...
Click to collapse
So when do you think the ROM will be ready?
Edit: Oppo Touch Recovery works, I'd rather not bother with CWM if that's ok? And if you could port a TWRP instead of Oppo Touch Recovery I would appreciate that since it is more advanced.

DJ Robby said:
So when do you think the ROM will be ready?
Edit: Oppo Touch Recovery works, I'd rather not bother with CWM if that's ok? And if you could port a TWRP instead of Oppo Touch Recovery I would appreciate that since it is more advanced.
Click to expand...
Click to collapse
Rom will be ready soon it takes time to convert things to ext4 from ubifs patience is a must for these things unless you want a brick ? Lol plus ive got another 5 projects on the go so lots to do and not enough time to do it all, just finished lineage 14.1 android 7.1.2 for alactel pixi 4027A using a stock kernel on android 4.4.4
as for TWRP probably not due to the size of your recovery and the size of most twrp is about 3mb to short for your partition youll need to use cwm ive added mount points to the script for your data & system partitions so if it dont flash mount in CWM and then flash if it still dosent use the take a log option in my installer and forward it to me so i can see if it was the mounts or what,
Also i havent set meta-data for permissions ive set perm & perm_recursive which is specifically for CWM so please flash with that,
I make no gaurantee it will boot as i dont have one in front of me to work on & debug but everything should work ok though link will be up in roughly half hour max

Links up tell me if it installs and boots ok is based off my cyanogenmod 11 new unreleased build #003 for ubifs
CyanogenMod 11 R10
emmc + ext4
BETA TEST BUILD
https://drive.google.com/file/d/1CvP3TPjo5fxXi6tHKI388WFN5KnWTyZ4/view?usp=drivesdk
If it dosent flash remember to get the log from my modified installer
if it dosent boot past first logo tell me it will be fstab issue which ill need to adjust
If it gets stuck on infinite bootanimation tell me ill need to adjust the vold
If any errors just flash back your backup with SP flash tool using download only mode and youll be back up and running with it until i get it fixed if it does need fixing.

Matty1993 said:
Links up tell me if it installs and boots ok is based off my cyanogenmod 11 new unreleased build #003 for ubifs
CyanogenMod 11 R10
emmc + ext4
BETA TEST BUILD
https://drive.google.com/file/d/1CvP3TPjo5fxXi6tHKI388WFN5KnWTyZ4/view?usp=drivesdk
If it dosent flash remember to get the log from my modified installer
if it dosent boot past first logo tell me it will be fstab issue which ill need to adjust
If it gets stuck on infinite bootanimation tell me ill need to adjust the vold
If any errors just flash back your backup with SP flash tool using download only mode and youll be back up and running with it until i get it fixed if it does need fixing.
Click to expand...
Click to collapse
So does that mean Oppo Touch Recovery is useless? So I should just put CWM in the recovery and then flash the CyanogenMod11 with CWM If I could get more detailed instructions that would be helpful as you know I am a noob...
Edit: So I flashed it with CWM and it failed, Here is the log: https://pastebin.com/i2F55g08
What I think happens is the first image that says welcome comes up, Then the boot animation comes up but it doesn't finish before returning to the welcome image that was at the start and it stays on that forever.
Edit 2: I also don't know how to restore the backup with SP Flash Tool but that is ok since this isn't my everyday phone so i'll just wait until you fix the ROM.

DJ Robby said:
So does that mean Oppo Touch Recovery is useless? So I should just put CWM in the recovery and then flash the CyanogenMod11 with CWM If I could get more detailed instructions that would be helpful as you know I am a noob...
Edit: So I flashed it with CWM and it failed, Here is the log: https://pastebin.com/i2F55g08
What I think happens is the first image that says welcome comes up, Then the boot animation comes up but it doesn't finish before returning to the welcome image that was at the start and it stays on that forever.
Edit 2: I also don't know how to restore the backup with SP Flash Tool but that is ok since this isn't my everyday phone so i'll just wait until you fix the ROM.
Click to expand...
Click to collapse
Hey mate i took a look at the log,
For some reason it didnt symlink any of the system files or set the perms for them
Modified boot.img didnt flash either for some reason so surprised it started playing animation so all my adjustments from ubifs to ext4 must be correct
In the script
Format was ok
Mounting was ok
Extract system files was ok
I think it may have something to do with CWM possibly as thats the only reason its not booting none of the files have correct perms everything else went ok though, so ill see what i can do today about another recovery for you,
The oppo touch recovery is just a stock recovery i added to get rid of the 3e recoveries these phones originally come with, much nicer is all,
To restore your backup using SP flash tool open flash tool, select the scatter box,
Navigate to your backuo folder & double click on the scatter_file.txt,
All of your partitions and files will automatically load up for flash,
Change the download mode to download only
Power off phone click start download
Connect phone & wait for flash

I will just wait for the new Recovery and ROM to work because like I said before this is a device that I didn't use at all but I will probably use it once I get the ROM. Again I just want to thank you for all your help since because of you I don't need to throw out this horrible phone.