Related
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
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
DOWNLOAD:
Latest Release
INSTALLATION
Power off your Galaxy S Duos
Get into Download mode by pressing Volume (-) + Home + Power Keys followed by Volume (+) to Confirm.
Step:1 - Press "PDA" button and choose the filerecovery.tar.md5 !
Step:2 - Press "Start" button under Execution.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Credits-
@coolamit for testing.
XDA:DevDB Information
TWRP - kylexx, Tool/Utility for the Android General
Contributors
v_superuser
Version Information
Status: Stable
Stable Release Date: 2014-04-21
Created 2014-04-21
Last Updated 2014-08-18
Note - There might be some things broken, you need to keep calm.
Also, you need to install with the update package from codename13. (Thanks to @coolamit )
Man this recovery almost screw up my phone. for no reason from a certain point the restored backups doesn't boot anymore, stuck at Samsung logo, tried making other backups, reflash twrp, first cwm then twrp but nothing.
The only one working was AN old backup of a week ago, restored that.
I can't use this if it isn't 100% reliable sorry
holymoz said:
Man this recovery almost screw up my phone. for no reason from a certain point the restored backups doesn't boot anymore, stuck at Samsung logo, tried making other backups, reflash twrp, first cwm then twrp but nothing.
The only one working was AN old backup of a week ago, restored that.
I can't use this if it isn't 100% reliable sorry
Click to expand...
Click to collapse
What else do you expect from an Alpha build? :/
v_superuser said:
What else do you expect from an Alpha build? :/
Click to expand...
Click to collapse
ok, I will wait for a more stable version, I like this recovery specially for the compression of backups that saves a lot of space
Awesomee and good work sir ...
can weget for ldpi devices like galaxy pocket,y etc phones ..?? in zip format
Does anyone know if it also works on ace 2x?
Sent from my GT-S7560M using XDA Premium 4 mobile app
Need help for s duos
do you have still s duos and could you please tell how to fix the animation problem in cm11 4.4.4 for s duos( in your cm11 there is no such problem)
I just installed sucefully, but when boot in recovery mode, just hang up.... therefore, the phone boot normally... well, I also lost the root
Not booting in TWRP. Getting restarted every time I am trying to boot with VolUP+Power+Home. If I hold the keys it keeps rebooting, and if I release it boots to system.
If I execute the command from terminal
Code:
adb reboot recovery
it boots into Samsung stock recovery.
Also showing a yellow symbol (!) while booting.
Should I flash it to stock recovery image?
Or is there any other way out to update the recovery to TWRP?
Solved
Thanks to KlinkOnE and m4jonez.
First I installed (ROOT) Rashr - Flash Tool from Play Store as suggested in the post.
Then downloaded Recovery - TWRP 2.8.0.1 and Recovery - TWRP 3.0.2 as mentioned here .
Placed both of the .zip files in the internal memory.
Now I open Rashr and flashed the recovery selecting the .zip file of TWRP 2.8.0.1 (My phone is rooted, so Rashr was able to flash it). Then rebooted to TWRP. But, failed. Removed the battery and insert it again. Now with Vol + Home + Power key, booted the phone in TWRP. From TWRP installed the TWRP 3.0.2. Rebooted to TWRP. It works fine now.
hcp006sl said:
Thanks to KlinkOnE and m4jonez.
First I installed (ROOT) Rashr - Flash Tool from Play Store as suggested in the post.
Then downloaded Recovery - TWRP 2.8.0.1 and Recovery - TWRP 3.0.2 as mentioned here .
Placed both of the .zip files in the internal memory.
Now I open Rashr and flashed the recovery selecting the .zip file of TWRP 2.8.0.1 (My phone is rooted, so Rashr was able to flash it). Then rebooted to TWRP. But, failed. Removed the battery and insert it again. Now with Vol + Home + Power key, booted the phone in TWRP. From TWRP installed the TWRP 3.0.2. Rebooted to TWRP. It works fine now.
Click to expand...
Click to collapse
pls help i'm new to the whole rom flashing thing. i tried what you wrote but the Rashr dosnt seem to find the TWRP both in my phone and external memory. i tried it on both core prime (SM-G360H) and (GT-I9060). i rooted both with kingroot via pc. thanks in advance for your assistance.
digitzonline said:
pls help i'm new to the whole rom flashing thing. i tried what you wrote but the Rashr dosnt seem to find the TWRP both in my phone and external memory. i tried it on both core prime (SM-G360H) and (GT-I9060). i rooted both with kingroot via pc. thanks in advance for your assistance.
Click to expand...
Click to collapse
I don't think this TWRP is for those two models - Core Prime and Grand Neo. Please download TWRP for your phone.
For GT-I9060 follow the thread [RECOVERY][GT-I9060] TWRP 2.8.0.1 touch recovery [UNOFFICIAL] and you can download the TWRP recovery for I9060 from here -Mod edit link removed ppc
For SM-360H follow the thread [Recovery] Official TWRP SM-G360H.
Please don't use king root for rooting. If you have used, replace it with SuperSU. Super-Sume Pro is the app that replaces KingRoot by SuperSu.
[ROM][UNOFFICIAL][6.0.1][E6853/E6803] CyanogenMod 13 for the Sony Xperia Z5 Premium [ALPHA]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod 13 for the Sony Xperia Z5 E6853 and E6803
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase
performance and reliability over stock Android for your device.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be
used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps).
CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Before you start
This ROM is only for the E6853 and the E6803
Code:
*
* Your warranty may be voided !
*
* 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.
*
Special Thanks
@CTXz for getting the ball rolling on CyanogenMod for Z5 series and stemming the lion's share to get this working
@oshmoun for providing fixes ASAP
@AndroPlus for providing a great kernel that works with many recoveries
@moonbutt74 for reminding me that smashing your device can provide a solution
@sub77 for teaching me how to work with QCOM (I was on exynos before)
@Joeisgood99 for providing a solid working TWRP-3.0.0.0 build until we had our own
@bazhip for providing a well working twrp 2.8.7.0 for restoring until we had our own
@alphatact1cs has a great overview on lots of topics for the Z5 device family
@auras76 for his great Custom ROM
@infected_ for his experience
Thanks to @mpro420 for help to get Viper4Android working !
Thanks to @jimRnor for Project DiVA SoundMod !
The Sonyxperiadev team for releasing their sources to the public
SonyAOSP team
SonyCM team
Sony Xperia (community) devs
And ofcourse the entire CyanogenMod team!
(Known) Issues
Video Recording
Bluetooth (keeps restarting) (might be fixed, needs feedback + testing)
Camera Colors (can be circumvented by using specific apps CameraNext Mod )
Camera Focus & Sharpness (driver issue, probably since it uses Xperia Z (original) drivers but different lenses ?)
Camera lowlight pictures (might improve with release of Sony's "Experimental AOSP Camera" for the Z5 series, porting of other Framework + Stock Cam app; partially needs DRM magic)
Camera Focus (even with VCM2 actuator changes focus is still kind of murky)
Fingerprint sensor (might work depending on build date of ROM)
Lag after booting up device (Will resolve: lock screen after boot and waiting a few seconds)
Long bootup times & less smoothness with "stock" (prebuilt) kernel
What can not be fixed, changed - aka WONTFIX - NOTOURPROBLEM
There might be potential speed issues with Class 10+ microSD cards not properly being "tuned", in that case switch to slower cards or RMA it which should hopefully solve it. There is a possibility to force slower speeds on cards but that is not really the optimal solution with ultra speed cards and needs further investigation. Samsung (EVO/EVO+) cards, Transcend cards and a few others UHS-I(+) and faster are affected.
What has been Fixed
Horizontal color lines and color glitches during bootup
Gapps
Sudden Lag after some time
NFC
Odd calling numbers
In-call mic
Sound on calls
Camera button
Microphone
Thermal regulation
Red flashy frames
RIL (SIM detection)
Dex pre-optimization
Camera
Sensors
Crash after locking device
microSD access
Flash light / Torch
Full brightness (should be fully working)
Gapps (permissions issues) [occurs occasionally and should be circumvented by full-wipe approach (incl. internal storage)
Hang/Loop during boot stage (should be circumvented by full-wipe approach (incl. internal storage)) (use Custom Kernel, under investigation)
High battery drain [~ 10%-20% per hour] when dirty-flashing system (fastboot -S 256M flash system system.img), make sure to have data backed up, then format /data ; OTA updates should be fine though [need feedback] ); causes are: dirty flashing, certain apps, ROM issues, etc.
Guides/Instructions
Unlocking Bootloader
Warning! The following procedure may void your warranty and will wipe EVERYTHING
Visit Sonys Official Bootloader Unlock guide (Details to all the risks you are taking are located on their site)
After Unlocking your bootloader you can proceed with the next steps
Steps on how to Fastboot, Flashmode, Recovery, Emergency/Force Poweroff
@alphatact1cs has a great overview on lots of topics for the Z5 device family
over at [GUIDE] Sony Xperia Z5 - UNLOCK / ROOT / TWEAKS - OS 5.1.1 / 6.0
There go to the [GUIDE] StockROM section , open it up and under #GENERAL you'll find everything you need to know.
Setting up fastboot and how to use it
For windows users
Please checkout this guide on how to use fastboot on windows
If you prefer to keep a low footprint instead of installing the whole Android SDK, take a look at its thread
[TOOL]Minimal ADB and Fastboot [8-28-15]
For Linux users
Installation
Debian based distros (Debian, Ubuntu etc.)
Open a terminal and enter the following :
Code:
sudo apt-get update && sudo apt-get install android-tools*
Confirm the installation by either hitting enter or typing y
Gentoo based Distros (Gentoo, Funtoo, Sabayon, Scientific Linux)
Once you're in a terminal, enter the following:
Code:
emerge dev-util/android-sdk-update-manager
Other distros (Arch, Fedora, Open Suse etc.)
Please find the apropriate packages to install android fastboot tools for your distro
How to use
Open a terminal in the location your .img file is located or cd into that directory like this:
Code:
cd <path to your directory that contains the .img files>
Replace <path to your directory that contains the .img files> with your actuall path
To boot temporarely into a .img (ex recovery) use the following command (replace <your.img> with your .img file) :
Code:
fastboot boot <yourfile>.img
To flash a kernel image enter the following (replace <your.img> with your .img file):
Code:
fastboot flash boot <your.img>
To flash a recovery image enter the following (replace <your.img> with your .img file):
Code:
fastboot flash recovery <your.img>
To exit fastboot enter :
Code:
fastboot reboot
How to install CM 13
Above all - do a Backup of ALL your data
When I write ALL I mean ALL (this includes the data on your micro SD card,
don't come whining to me if you lose your wedding photos/videos, kids' photos/videos or other important stuff !
For optimal experience I'd recommend my built custom kernel (quicker boot times, higher reliability, more tweakability)
General, in-depth instructions (for the Xperia Z5 !)
Download one of the newer Z5 AndroPlusKernels v20+ by @AndroPlus from his official website (Scroll down and select Z5, then on AndroidFileHost search for Z5_AndroPlusKernel_Permissive_v2 (v20 - v23) and download it)
Extract the flashable zip-file e.g. Z5_AndroPlusKernel_Permissive_v23.zip
Download our TWRP 3.0.1-0 build for the Z5)
Download the appropriate gapps from below (Can be downloaded on your device)
Download the CM 13 Zip for the Z5 from below (Can be downloaded on your device)
Move the GAPPS zip and the CM 13 to your Z5 if you haven't downloaded them on your device
Power Off your Z5 and wait about 10-15 seconds to make sure it's off
To enter fastboot mode hold VOL UP and while holding VOL UP connect your device to your pc via cable
When the notification LED has turned blue you are in fastboot mode
On your PC flash the boot.img that has been extracted from the Z5_AndroPlusKernel_Permissive_v23.zip using fastboot (
Code:
fastboot flash boot boot.img
)
Now flash twrp-3.0.1-0-E6653-20160403.img by using fastboot (
Code:
fastboot flash recovery twrp-3.0.1-0-E6653-20160403.img
)
Once both of those images have been flashed you can reboot the device like so:
Code:
fastboot reboot
Quickly pull the usb cable from the computer (you can leave the other end in the phone's port)
When booting up wait for the notification light to turn yellow at the Sony logo
Once it has turned yellow, you will enter TWRP by pressing VOL UP (or VOL DOWN - up works more reliably)
If you've missed the step above, reboot your device and try the step above again
Alternatively you can force turn off the device via: Power Button + Volume Up , then turn it on again via Power Button
If TWRP asks you to enable read and write, swipe to continue
Go to settings and lower the max brightness to the minimum or one of the lower levels to preserve energy
In TWRP make a full backup to the microSD in case you want to revert back to stock.
After it has finished, in this case Reboot -> System.
Copy over the TWRP folder from the external microSD to your computer (reason: you might not have access to your external SD or have to reformat it
Thank Microsoft, Sony, etc. for that: "Stock" ROM uses texfat , AOSP, CM, etc. uses exfat, ext4, ntfs
The files on the microSD might get corrupted (filesystem problem) or the microSD going crazy (I already had both cases)
Now Power on your phone and follow the steps again to get into TWRP
Swipe to continue (?)
select Wipe > Advanced Wipe
Now ONLY tick Dalvik/ART cache, System, Cache and Data
WARNING! THE NEXT STEP WILL WIPE YOUR SYSTEM AND DATA, MEANING YOU WILL DELETE YOUR STOCK SONY SYSTEM AND ALL YOUR APPS
(You already DID a Backup of your files so nothing to worry about)
Once you've ticked the correct boxes, swipe to wipe
Once the wipe is complete, return to the main menu and select Install
Locate and select your CM 13 Zip
Select "Add more Zips" and add your GAPPS package and finally swipe to install
Once the installation succeeded you can select "Reboot System"
Wait for CM 13 to boot up (Can take several minutes)
Enjoy CM13
OPTIONAL: You can remove your TWRP backup that is located in the TWRP folder if you feel like you will no longer need it
How to ROOT
In CM 13, enable the developer options
Select Root access
Select Apps Only (Or Apps and ADB if you use ADB)
Done
How to disable the Thermal Manager
Before we start I want to set a few questions and warnings. Disabling the thermal manager will cause you device to run slightly hotter, do this at your own risk.
Let's start out with why you would want to disable the thermal manager. At this point it's not recommended to disable the thermal manager as it has been fixed. However some people still want the max performance out of their device. The average heat without the thermal manager will be roughly the same, if not less compared to the stock ROM with it's thermal manager enabled.
So why is the thermal manager even included if it the device runs mostly fine without it. As most of you already know, the Snapdragon 810 (MSM8994) has overheating problems. The first CM boot after flash is responsible for optimizing apps and android and can become extremely resource hungry at that point. Due to that, the device can heat tremendously! Not only can that cause a panic reboot but it can also damage your device in rare cases. To avoid that issue a thermal manager shrinks down process and slowers the boot animation (That's why the CM logo may lag at first boot).
Enough said, let's get going..
To disable the thermal manager you must do the following :
First enable root access (See "How to ROOT" guide)
Open the CM file manager
Go to settings > General Settings > Access Mode
Select root acess mode
Go back to the file manager
Swipe from left to right or press the menu button in the upper left corner
Select Root folder
Open the folder/directory called etc
Delete thermanger.xml
Reboot
Done
How return back to stock via TWRP backup
Reboot your device
Wait for the notification light to turn purple at the Sony logo
Once it has turned purple, you will enter TWRP by pressing VOL UP or VOL DOWN
If you've missed the step above reboot and try again
If TWRP will ask you to enable read and write, swipe to continue
In TWRP select restore and select your backup, then swipe to restore
Once the restore is done you can select "Reboot System"
If your device hangs at the Sony wave boot animation, force shut down and power your device up again.
Downloads
Latest recommended CyanogenMod release for the Sony Xperia Z5 E6853/E6803 :
6.0.1_13.0-20160627-UNOFFICIAL-satsuki_r46_alternate
Latest recommended Kernel for the CM release for the Sony Xperia Z5 E6853/E6803 :
6.0.1_13.0-20160627-UNOFFICIAL-satsuki_r46_alternate
All my releases can be found here on : Android File Host
TWRP for CM/AOSP-based ROMs:
E68XX_TWRP3_SD_recovery.img
Gapps (Select ARM64 > 6.0) :
Open Gapps
[GAPPS][6.0/5.1/5.0][arm/arm64] Official Slim GApps ( recommended )
XPosed for Android:
[OFFICIAL] Xposed for Lollipop/Marshmallow (Installer in Thread)
XPosed Releases
SuperSU in SystemMode:
SuperSU in System-Mode [v2.65-STABLE] [v2.68-BETA] [v2.70-WIP/BETA-RC]
Sound MODs:
[Sound Mod ][Project DiVA][6.0 MM_Z5 series] KitaKami sound mod Prototype 01 (any effect ?)
A.R.I.S.E. Sound Systems - Auditory Research in Sound Enhancement - Exodus RC8.3 (works (RC8.3))
[SOUNDMOD][JB/KK/LP/MM]Project Yume Final, You are the Legend (needs testing)
[SUPER MOD][4.4+/6.0/N][ v7.5.2 ] XTREMEMusic™ THE SOUND THAT YOU'VE NEVER HEARD! (NOT working (7.4), needs testing of 7.5*
[Audio Mod] eXtremeBeats Aural Maximizer (needs testing)
[APP]Material ViPER4Android 2.4.0.1[Light/Dark][LP/MM]
mpro420 said:
1.)zip file install via twrp.
2.)reboot to system.
3.)enable v4a "write to sdcard" permission in setting/apps/viper4android/permission.
4.)open v4a and gain root permission.
5.)install driver for v4a.
6.)reboot system.
7.)[emoji39]
Click to expand...
Click to collapse
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Requests for other devices
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions or requests usually by the same user
Requests that are out of CM's framework (Ex. Adding Sony Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Source Code
All Source Code can be obtained from:
https://github.com/Sony-Kitakami
https://github.com/SonyAosp
https://github.com/sonyxperiadev
https://github.com/CyanogenMod
https://github.com/zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
Kernel Source code can be obtained from : zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
We gladly accept any developers that are willing to contribute to this project! Please PM @CTXz if you are interested in joining this project!
Build from Source
http://forum.xda-developers.com/xperia-z5/general/guide-build-cm13-source-z5-z5c-z5p-t3357040
Screen Shots (Z5 compact)
XDA:DevDB Information
CyanogenMod 13 for the Sony Xperia Z5 E6853 and E6803, ROM for the Sony Xperia Z5 Premium
Contributors
CTXz, Moonbutt74 , zacharias.maladroit , oshmoun , infected_
Source Code:
https://github.com/Sony-Kitakami
https://github.com/SonyAosp
https://github.com/sonyxperiadev
https://github.com/CyanogenMod
https://github.com/zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
ROM OS Version: 6.0.x Marshmallow
ROM Firmware Required: 6.0 Recommended
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2016-04-11
Last Updated 2016-06-28
one
two
three
Previous ("legacy") threads,
by moonbutt74:
CM13 Z5P E6853 Beta -- Updated NegaSpork
[Rootable Kernel/ TWRP 3 - E6833/E6853/E6883 Marshsmellow ] [32.1.A.1.163] AU]
ok running cm13 on my 6385 and ran it for 5 mins and very happy will see about battery drain later hope there is very little, i have tried the cameras and they both show a blue picture any ideas?
dominicstg2 said:
ok running cm13 on my 6385 and ran it for 5 mins and very happy will see about battery drain later hope there is very little, i have tried the cameras and they both show a blue picture any ideas?
Click to expand...
Click to collapse
there is very little battery drain compared to Sony Stock ROMs,
It's a limitation in the preview of the camera, you tried to take a picture ? That also isn't very great but better
Use Camera Next Mod ( https://www.androidfilehost.com/?w=files&flid=53956 ) for improvement,
until Alin releases calibrated firmware blobs for the cam the picture will be non-focused and/or blurry for objects farer away than 60 cm
@dominicstg2 Weren't you one of those RR (Resurrection Remix) lovers ?
zacharias.maladroit said:
there is very little battery drain compared to Sony Stock ROMs,
It's a limitation in the preview of the camera, you tried to take a picture ? That also isn't very great but better
Use Camera Next Mod ( https://www.androidfilehost.com/?w=files&flid=53956 ) for improvement,
until Alin releases calibrated firmware blobs for the cam the picture will be non-focused and/or blurry for objects farer away than 60 cm
@dominicstg2 Weren't you one of those RR (Resurrection Remix) lovers ?
Click to expand...
Click to collapse
yes i was one who used the rr also i cant flash the rom on 6.0,1 was coming from stock, tried wiped everything and didnt work it said rom is for our device but said my device is . i had to flash android l to flash the rom any idea? not abig deal because im rocking cm13 also i dont see a drain at all on stock over night would see 5% drop on cm13 not a single % dropped and on rr when i used camera next mod the photo would be fine but on cm13 the camera is still blue when i take a picture? also im very happy that mms works and data its basically daily drivable for me
dominicstg2 said:
yes i was one who used the rr also i cant flash the rom on 6.0,1 was coming from stock, tried wiped everything and didnt work it said rom is for our device but said my device is . i had to flash android l to flash the rom any idea? not abig deal because im rocking cm13 also i dont see a drain at all on stock over night would see 5% drop on cm13 not a single % dropped and on rr when i used camera next mod the photo would be fine but on cm13 the camera is still blue when i take a picture? also im very happy that mms works and data its basically daily drivable for me
Click to expand...
Click to collapse
Was that when I uploaded the first build of RR ?
Cause I hope that this time you have more luck with it and it works:
http://forum.xda-developers.com/showpost.php?p=67538514&postcount=45
Is the taken picture now fine with Camera Next Mod and CM13 ?
Both RR and CM13 now should be pretty close, please give RR another try
Thanks
yes i think it was if not the second build , whats more stable rr or cm13? i had some issues with rr ie 4g didnt alway connect nor did 3g and no the photo is still blue on camera next mod on cm13 and sure il will download it now also can you explain why when i was onn 6.0.1 i couldnt flash cm13 nor rr? it would say its for our device but my device is . and i would have to go back to 6.0 to flash?
zacharias.maladroit said:
Was that when I uploaded the first build of RR ?
Cause I hope that this time you have more luck with it and it works:
http://forum.xda-developers.com/showpost.php?p=67538514&postcount=45
Is the taken picture now fine with Camera Next Mod and CM13 ?
Both RR and CM13 now should be pretty close, please give RR another try
Thanks
Click to expand...
Click to collapse
dominicstg2 said:
yes i think it was if not the second build , whats more stable rr or cm13? i had some issues with rr ie 4g didnt alway connect nor did 3g and no the photo is still blue on camera next mod on cm13 and sure il will download it now also can you explain why when i was onn 6.0.1 i couldnt flash cm13 nor rr? it would say its for our device but my device is . and i would have to go back to 6.0 to flash?
Click to expand...
Click to collapse
It's related to the device string that is in the zip-file of the ROM,
if that doesn't match TWRP, it can not be flashed, unless you modify the zip-file to remove that line.
That mismatch can be made in error (something went wrong during creation, typo, etc.)
or on purpose - in that case it's not so wise to flash the wrong ROM
Oh has other people had this problem?
zacharias.maladroit said:
It's related to the device string that is in the zip-file of the ROM,
if that doesn't match TWRP, it can not be flashed, unless you modify the zip-file to remove that line.
That mismatch can be made in error (something went wrong during creation, typo, etc.)
or on purpose - in that case it's not so wise to flash the wrong ROM
Click to expand...
Click to collapse
dominicstg2 said:
Oh has other people had this problem?
Click to expand...
Click to collapse
yeah, not sure if on Z5 compact,
but certainly on Z5 Premium and Z5
waitting for 6883 ^_^
Thanks Dev.
I join the testing!
Changelog
12.07.2016 == stable/testing/UNOFFICIAL update build
upstream ROM changes 6.0.1_r56 (Android security Patchlevel: 2016-07-01 / 2016-07-05)
ADB enabled by default for better error diagnosis, ADB over WiFi disabled
fingerprint scanner might work
NFC should work again
single SIM ONLY
.
other changes: YOU tell me
.
previous custom kernel (if used) should still work + NFC too, if you encounter issues with NFC please let me know
Click to expand...
Click to collapse
Kernel Source:
https://github.com/zachariasmaladro...mi_r2/commits/Sun-Kernel_cm-13.0_III.1_5_3_cm
ROM Source:
mostly
https://github.com/SonyAosp/
https://github.com/Sony-Kitakami/
https://github.com/sonyxperiadev/
Kernel
Z5P_Sunkernel_Permissive_v13_III.1_5_3.zip
ROM
6.0.1_13.0-20160712-UNOFFICIAL-satsuki_r56
Thanks
zacharias.maladroit said:
Changelog
Kernel Source:
https://github.com/zachariasmaladro...mi_r2/commits/Sun-Kernel_cm-13.0_III.1_5_3_cm
ROM Source:
mostly
https://github.com/SonyAosp/
https://github.com/Sony-Kitakami/
https://github.com/sonyxperiadev/
Kernel
Z5P_Sunkernel_Permissive_v13_III.1_5_3.zip
ROM
6.0.1_13.0-20160712-UNOFFICIAL-satsuki_r56
Thanks
Click to expand...
Click to collapse
Hi Dev ^_^
about version cm13 for Z5P E6883, When will be released ?
Tani_bc said:
Hi Dev ^_^
about version cm13 for Z5P E6883, When will be released ?
Click to expand...
Click to collapse
Don't ask for ETAs on XDA. It is rude.
Sent from my SGP311 using XDA Labs
Tani_bc said:
Hi Dev ^_^
about version cm13 for Z5P E6883, When will be released ?
Click to expand...
Click to collapse
Work in progress,
please take a look at the CM13 thread for the Z5, will ya ?
there are several factors that influence access and working for
microSD, sim cards (both), fingerprint scanner and others
Hi. Just curious, is it possible if I use this on E6883 (Z5 Premium Dual) and flash Dual Enabler thereafter?
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.
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Unofficial TWRP 3.0.2-0 for Ulefone Metal
Mirror 1
MD5 - 10286EE1255C8371A2E5F720896D02C2
SHA-1 - E6C0875ADA34EB1CDE5D5A648D3F8B9AC883EFDA
INSTALLATION:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version above
2) Reboot to TWRP
3) Hit Install and tap the "Install Image" button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
To install from SP Flash Tools:
1) Download scatter file attached to this post
2) Load scatter file into SPFT
3) Plug USB cable into device and computer
4) Press download in SPFT
5) Reboot device
BUGS:
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed.
XDA:DevDB Information
RECOVERY] Unofficial TWRP for Ulefone Metal, Tool/Utility for the Android General
Contributors
Jonny
Source Code: https://github.com/JonnyXDA/android_device_ulefone_metal/tree/Omni
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-11-20
Created 2016-10-31
Last Updated 2016-11-20
FAQ:
- None yet!
DEVICE-SPECIFIC CHANGELOGS:
3.0.2-0:
-Fully built from source for Ulefone Metal
Current TWRP "bugs" for Ulefone Metal:
NONE
Thanks for your work.
Recovery not mounting sd card.
Here is log:
Internal build from ulefone forum works.
Mounting sd card works.
Thanks.
here is log:
dropbear2 said:
Internal build from ulefone forum works.
Mounting sd card works.
Thanks.
here is log:
Click to expand...
Click to collapse
Internal? You mean the build I posted there this morning?
Jonny said:
Internal? You mean the build I posted there this morning?
Click to expand...
Click to collapse
Yes, build posted this morning.
dropbear2 said:
Yes, build posted this morning.
Click to expand...
Click to collapse
Cool, I'll update this thread with it in a bit.
This build twrp in downloads (2016-11-02 16:29) does not work.
Is not the same as the build in ulefone forum.
This twrp works: http://ota.cm.mkoas.de:8080/job/TWRP Ulefone Metal/ws/recovery.img
dropbear2 said:
This build twrp in downloads (2016-11-02 16:29) does not work.
Is not the same as the build in ulefone forum.
This twrp works: http://ota.cm.mkoas.de:8080/job/TWRP Ulefone Metal/ws/recovery.img
Click to expand...
Click to collapse
I know, I said I would get round to updating this post as well, I haven't been able to yet as I've been busy
Jonny said:
I know, I said I would get round to updating this post as well, I haven't been able to yet as I've been busy
Click to expand...
Click to collapse
sorry,
I thought that you replaced.
Thread updated with the new links (eventually!).
Apologies for the delay
Hey,
i've flashed TWRP and when i boot it, the phone just shows the ulefone logo and then restarts..
I tried to flash with flashtools and via fastboot flash recovery...
Its possible to flash custom rom, which works quite nice, but TWRP won't come up so i can't root phone or do nandroid backups.
Any help? Any idea how to get logs of what happening?
BTW: reflashed offical stock does the same, displays ulefone logo and reboots..
EDIT:
Flashed recover as boot, and boot as recovery:
Normal boot (should start TWRP now) reboots all the time.
Recovery boot (should boot normal boot.img now) works and boots the System..
So there has to be a problem with the downloaded TWRP/Recovery Image not working on my phone..
It's normal Ulefone Metal don't know why it doesn't work.. wpuld like so see some logs or something
Edit2:
Flashed twrp-3-0-2-4es-by-mdsdev from needrom,
which worked.. don't know why any other one didn't...
I can not find the scatter mentioned in the post. I tried to install it with another scatter or another TWRP, but when I try to run the recovery it simply restarts.
Regards, I inform you that I have been doing a series of tests on my mobile, to try to flash some existing roms. For now the following happens: The official firmware from the 20160912 and lower version do not work (I still have to try the 20161019 version), the 20161024 and 20161117 versions work correctly.
Another error, for now the one that has me more restless is the following: The only functional recovery is the TWRP of the user hanuma50 that has incompatibility with certain roms, the other versions of TWRP available do not work, when trying to install it using SPFT , Flashify or from the same TWRP are installed correctly, but at the time of running it simply restarts the mobile and starts the system normally.
I'm thinking because it is because there is surely a new batch of mobile with changes to the hardware, but I do not know, Do you know anything about it?
Another thing, if the darksense kernel flashed the mobile stops working (it enters an infinite loop with the Ulefone logo), it was tested in stock rom and in the Eragon rom.
sinrequilorios said:
Regards, I inform you that I have been doing a series of tests on my mobile, to try to flash some existing roms. For now the following happens: The official firmware from the 20160912 and lower version do not work (I still have to try the 20161019 version), the 20161024 and 20161117 versions work correctly.
Another error, for now the one that has me more restless is the following: The only functional recovery is the TWRP of the user hanuma50 that has incompatibility with certain roms, the other versions of TWRP available do not work, when trying to install it using SPFT , Flashify or from the same TWRP are installed correctly, but at the time of running it simply restarts the mobile and starts the system normally.
I'm thinking because it is because there is surely a new batch of mobile with changes to the hardware, but I do not know, Do you know anything about it?
Another thing, if the darksense kernel flashed the mobile stops working (it enters an infinite loop with the Ulefone logo), it was tested in stock rom and in the Eragon rom.
Click to expand...
Click to collapse
It is not my fault if existing ROM's don't flash properly, we faced this problem on Elephone P9000, it is because the people who develop the ROM's don't use the proper mount points, if they did, it would flash. Instead, they use the mount points for the ported recoveries which are not correct.
End of story, not my fault and I will not support the people that this happens to.
sinrequilorios said:
Regards, I inform you that I have been doing a series of tests on my mobile, to try to flash some existing roms. For now the following happens: The official firmware from the 20160912 and lower version do not work (I still have to try the 20161019 version), the 20161024 and 20161117 versions work correctly.
Another error, for now the one that has me more restless is the following: The only functional recovery is the TWRP of the user hanuma50 that has incompatibility with certain roms, the other versions of TWRP available do not work, when trying to install it using SPFT , Flashify or from the same TWRP are installed correctly, but at the time of running it simply restarts the mobile and starts the system normally.
I'm thinking because it is because there is surely a new batch of mobile with changes to the hardware, but I do not know, Do you know anything about it?
Another thing, if the darksense kernel flashed the mobile stops working (it enters an infinite loop with the Ulefone logo), it was tested in stock rom and in the Eragon rom.
Click to expand...
Click to collapse
Jonny said:
It is not my fault if existing ROM's don't flash properly, we faced this problem on Elephone P9000, it is because the people who develop the ROM's don't use the proper mount points, if they did, it would flash. Instead, they use the mount points for the ported recoveries which are not correct.
End of story, not my fault and I will not support the people that this happens to.
Click to expand...
Click to collapse
I think here's some confusion. As far as I understand it, it's not a problem of neither the recovery, nor wrong mount points.
There's just a newer revision of the model it seems. This newer models only work with recovery, built against stock pre-built kernel (aka ports).
Our rom is built for being flashed by this recovery, because this recovery is the only compiled one. Unfortunately, there's nothing which can be done without ulefone updating the kernel source code.
DerTeufel1980 said:
I think here's some confusion. As far as I understand it, it's not a problem of neither the recovery, nor wrong mount points.
There's just a newer revision of the model it seems. This newer models only work with recovery, built against stock pre-built kernel (aka ports).
Our rom is built for being flashed by this recovery, because this recovery is the only compiled one. Unfortunately, there's nothing which can be done without ulefone updating the kernel source code.
Click to expand...
Click to collapse
Provide me with the device source to build this recovery from then, instead of hiding your source in a private bit bucket repo. I'm Jonathon Fitch, the guy who's source you probably based yours on. The least you could do is share...
Jonny said:
Provide me with the device source to build this recovery from then, instead of hiding your source in a private bit bucket repo. I'm Jonathon Fitch, the guy who's source you probably based yours on. The least you could do is share...
Click to expand...
Click to collapse
Ug..
GPL source code is provided on our Metal thread...
https://github.com/MediatekAndroidDevelopers/android_kernel_ulefone_metal
Cheers
M.A.D. Team
Jonny said:
Provide me with the device source to build this recovery from then, instead of hiding your source in a private bit bucket repo. I'm Jonathon Fitch, the guy who's source you probably based yours on. The least you could do is share...
Click to expand...
Click to collapse
Of course we didn't build upon your kernel. Why should we have done this?
We are using your recovery, or more detailed, we are suggesting to use your recovery.
What's your problem? We did not disrespect you in any way.
Sent from my Thor using Tapatalk
DerTeufel1980 said:
Of course we didn't build upon your kernel. Why should we have done this?
We are using your recovery, or more detailed, we are suggesting to use your recovery.
What's your problem? We did not disrespect you in any way.
Sent from my Thor using Tapatalk
Click to expand...
Click to collapse
^^ THIS
Team Win Recovery Project
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
WHAT THIS THREAD IS ABOUT?
This thread is about a serious TWRP development for the Xiaomi Redmi Note 6 Pro. By serious I mean a development which isn't using device tree which was just badly kanged from another device or it's a dirty port without any direct compilation from source. That means that issues like a low brightness, which is caused by a maintainer not being able to set the real maximum brightness which is supported by the device, aren't here.
FEATURES:
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support ( ext4 & f2fs )
ext4, f2fs, NTFS, fat file system support (read, write, format, backup & restore)
Covers more partitions for nandroid backup and the backup/restore of them really works!
Covers more partitions for image installation, including System, Vendor, Cust, Cache, Userdata, persist, persistbak, boot logo, modem firmware, and even Bluetooth firmware
ADB root
Always synced with signatures from Android platform, so you don't have to worry about the signature mismatch on MIUI incremental OTA installation
Full SELinux support
Support for Asian languages
Included logd/logcat support
Support for mounting USB storage - Mount -> Mount USB Storage in recovery menu.
ISSUE?
If you face any problem then just let me know and i will fix it asap. I'm not a magician to know everything, so if you won't report it then it's probably not gonna be fixed.
CHANGELOG
3.2.3.0, 18.1.2019
- initial release
3.2.3.1, 19.1.2019
- Fixed USB storage, from now on you can mount it
by clicking on Mount -> Mount USB Storage in the recovery menu.
3.2.3.2, 21.1.2019
- Imported selinux service contexts
- Added ability to backup/restore system/vendor images
- increased platform security values to override anti-rollback features to something rather insane
- Added system vold decryption support, since a process of getting keystore to work
on this device was a pure hell for me, but still this is in testing, just let me know if it works for you, but be careful and better backup your data before trying this...
3.3.0.1, 15.4.2019
- Slightly modified screen offset, so you can now see clock in the statusbar.
- Updated decryption blobs to pie, decryption should now work properly, after that there is also slightly improved vold decryption in case that default decryption fails
- Updated kernel to Android 9.0
DOWNLOAD LINK
3.2.3.0, 18.1.2019
Download
3.2.3.1, 19.1.2019
Download
3.2.3.2, 21.1.2019 - warning: this is test build!
Download
3.3.0.1, 15.4.2019
Download
DECRYPTION Builds (ported builds without source)
3.2.3.0, 27.4.2019
Changelog: Initial release
Download
XDA:DevDB Information
TWRP, Tool/Utility for the Xiaomi Redmi Note 6 Pro
Contributors
ATG Droid
Version Information
Status: Stable
Current Stable Version: 3.2.3.1
Stable Release Date: 2019-01-19
Created 2019-01-18
Last Updated 2019-01-19
Reserved
Device tree sources will be up later, don't worry about that. For kernel, I used prebuilt, so there isn't even what to publish.
Reserved
I'm using AOSP Extended, and data decryption does not work.
vdng9338 said:
I'm using AOSP Extended, and data decryption does not work.
Click to expand...
Click to collapse
Ok, will push a test build for it soon...
Edit: Here it is, someone test it please
https://www.androidfilehost.com/?fid=11410963190603903670
Thank You for this Serious development. Really Appreciate.
Ok, just pushed another update..
3.2.3.1 - 19.1.2019
Changelog: Fixed USB storage, from now on you can mount it by clicking on Mount -> Mount USB Storage in the recovery menu.
https://www.androidfilehost.com/?fid=11410963190603903811
Also tell me if the /data decryption works now
Finally, true TWRP builds there
with 3.2.3.1 it still cannot decrypt the data partition (I have entered the numbers that corresponds to the unlock pattern I have defined in Miui)
clemenza011 said:
with 3.2.3.1 it still cannot decrypt the data partition (I have entered the numbers that corresponds to the unlock pattern I have defined in Miui)
Click to expand...
Click to collapse
Here is another test build for it, in this one I switched to a decryption using vold, which should finally work i hope. Anyway, send me a log once you guys try it.
https://www.androidfilehost.com/?fid=11410963190603904132
ATG Droid said:
Here is another test build for it, in this one I switched to a decryption using vold, which should finally work i hope. Anyway, send me a log once you guys try it.
https://www.androidfilehost.com/?fid=11410963190603904132
Click to expand...
Click to collapse
another failed decrypt with the latest version - recovery log attached. Thanks!
edit: I have removed fingerprints, then switched from pattern to pure Pin unlock, and yet again decrypt failed - recovery2.log attached
ATG Droid said:
Team Win Recovery Project
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
WHAT THIS THREAD IS ABOUT?
This thread is about a serious TWRP development for the Xiaomi Redmi Note 6 Pro. By serious I mean a development which isn't using device tree which was just badly kanged from another device or it's a dirty port without any direct compilation from source. That means that issues like a low brightness, which is caused by the maintainer not being able to set real maximum brightness which is supported by the device, aren't here.
FEATURES:
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support ( ext4 & f2fs )
ext4, f2fs, NTFS, fat file system support (read, write, format, backup & restore)
Covers more partitions for nandroid backup and the backup/restore of them really works!
Covers more partitions for image installation, including System, Vendor, Cust, Cache, Userdata, persist, persistbak, boot logo, modem firmware, and even Bluetooth firmware
ADB root
Always synced with signatures from Android platform, so you don't have to worry about the signature mismatch on MIUI incremental OTA installation
Full SELinux support
Support for Asian languages
Included logd/logcat support
Support for mounting USB storage - Mount -> Mount USB Storage in recovery menu.
ISSUE?
If you face any problem then just let me know and i will fix it asap. I'm not a magician to know everything, so if you won't report it then it's probably not gonna be fixed.
CHANGELOG
3.2.3.0, 18.1.2019
- initial release
3.2.3.1, 19.1.2019
- Fixed USB storage, from now on you can mount it
by clicking on Mount -> Mount USB Storage in the recovery menu.
DOWNLOAD LINK
3.2.3.0, 18.1.2019
Download
3.2.3.1, 19.1.2019
Download
XDA:DevDB Information
TWRP, Tool/Utility for the Xiaomi Redmi Note 6 Pro
Contributors
ATG Droid
Version Information
Status: Stable
Current Stable Version: 3.2.3.1
Stable Release Date: 2019-01-19
Created 2019-01-18
Last Updated 2019-01-19
Click to expand...
Click to collapse
Thank you for your commitment with serious development and hard work.
Hope to see soon a final and official TWRP based on your version.
Keep debugging. Regards,
I'm also having trouble decrypting the date, no password is correct.
gostavovinicius said:
I'm also having trouble decrypting the date, no password is correct.
Click to expand...
Click to collapse
Decryption is always the most complicated thing to fix on every device. Anyway, I already encrypted my device and I'm trying to fix it, it will just take some time...
Ayyy, new update is out.
Changelog:
- Imported selinux service contexts
- Added ability to backup/restore system/vendor images
- increased platform security values to override anti-rollback features to something rather insane
- Added system vold decryption support, since a process of getting keystore to work
on this device was a pure hell for me, but still this is in testing, just let me know if it works for you, but be careful and better backup your data before trying this...
Download link:
https://www.androidfilehost.com/?fid=11410963190603905629
does this one have non anti rollback protecion?
bornlivedie said:
does this one have non anti rollback protecion?
Click to expand...
Click to collapse
Yep, that's what I mentioned in a changelog. And if you're talking about that "anti rollback" protection which is here promoted by the guy who compiled that fork of a TWRP called pitch black, then don't believe it. He didn't changed the required properties for it in his device tree. So it's actually just a clickbait and his recovery build doesn't really support that.
Actually his build doesn't even include the proper max. brightness which is supported by the LCD driver of this device. That's why I mentioned in a OP that compared to other TWRP builds here this thread is meant to be a serious development and not just a joke.
ATG Droid said:
Yep, that's what I mentioned in a changelog. And if you're talking about that "anti rollback" protection which is here promoted by the guy who compiled that fork of a TWRP called pitch black, then don't believe it. He didn't changed the required properties for it in his device tree. So it's actually just a clickbait and his recovery build doesn't really support that.
Actually his build doesn't even include the proper max. brightness which is supported by the LCD driver of this device. That's why I mentioned in a OP that compared to other TWRP builds here this thread is meant to be a serious development and not just a joke.
Click to expand...
Click to collapse
My bad, I read the entire changelog and yet somehow missed that line... I feel like a dumbass.
Thanks for the clarification, that's actually very important.
ouch, I have removed fingerprints, set pin protection, flashed latest twrp. When I rebooted to recovery, got just the twrp background, frozen, no any options. Worseover, I have turned the phone off, then on, and it asks me for password. I tried with the pin I have set before, yet it says - wrong password. so I cannot get my phone started and I do not know what else to do.
clemenza011 said:
ouch, I have removed fingerprints, set pin protection, flashed latest twrp. When I rebooted to recovery, got just the twrp background, frozen, no any options. Worseover, I have turned the phone off, then on, and it asks me for password. I tried with the pin I have set before, yet it says - wrong password. so I cannot get my phone started and I do not know what else to do.
Click to expand...
Click to collapse
It definetely wasn't frozen. Services would time-out. Just reboot back to the recovery, backup data, backup files in internal memory (sdcard). Format data, restore the previous backup of data and copy back the previous files from /sdcard again. After that flash the 3.2.3.1 version of a recovery and everything will be ok.