SUPPORTS USERDATA DECRYPTION on Nougat ROMs!
Just sharing my TWRP mod... This is the latest code from omnirom v.3.1.x-x, still not officially released by TeamWin. No official changelog yet but from the code and gerrit I can see some new features like option to install the new official TWRP App for keeping recovery up to date and flashing images from within Android, FBE encription support, A/B OTA udate support, abd backup support(WIP), kernel log export to /sdcard etc...
Chages from the official TWRP I have made:
1. Unified build for both hydrogen and helium;
2. Based on source from omnirom "android-8.1" repo - Thank you:good:;
3. All unnecessary input devices disabled including virtual mouse;
4. New features added:
- identifies and sets appropriate device props at boot time;
- enable/disable navbar in General Settings which automatically rearranges theme elements for the screen with/out navbar... The extra space is nice;
- enable/disable device capacitive buttons in General Settings;
- brightness control slider 0-100% for capacitive button's backlight in Screen Settings;
- Reset Lockscreen feature in Advanced > More... No more "can't unlock my phone after backup restore..." thing...
- Temporary disable Xposed framework feature in Advanced > More... for getting out of bootloops caused by bad modules etc.
- statusbar hide/snow keyboard button in Terminal;5. Fixed many bugs... Let me know if you find some more;
Note: Standard external themes on /sdcard are not supported!
You can help translate this thing by copying below code, translate the strings in green and post it here mentioning your language. I will add it in new build. Thank you!
Code:
<!-- Reset Lockscreen function strings -->
<string name="reset_lockscreen_btn">[COLOR="SeaGreen"]Reset Lockscreen[/COLOR]</string>
<string name="reset_lockscreen_hdr">[COLOR="SeaGreen"]Reset Lockscreen[/COLOR]</string>
<string name="reset_lockscreen_note1">[COLOR="SeaGreen"]If you cannot pass Lockscreen security[/COLOR]</string>
<string name="reset_lockscreen_note2">[COLOR="SeaGreen"]after backup restore you should do this.[/COLOR]</string>
<string name="swipe_to_reset_lockscreen">[COLOR="SeaGreen"]Swipe to Reset Lockscreen[/COLOR]</string>
<string name="resetting_lockscreen">[COLOR="SeaGreen"]Resetting Lockscreen...[/COLOR]</string>
<string name="reset_lockscreen_complete">[COLOR="SeaGreen"]Reset Lockscreen Complete[/COLOR]</string>
<!-- v.3.0.3-0 new TWRP App install strings -->
<string name="reboot_install_app_hdr">[COLOR="SeaGreen"]Install TWRP App?[/COLOR]</string>
<string name="reboot_install_app1">[COLOR="SeaGreen"]Would you like to install the Official TWRP App?[/COLOR]</string>
<string name="reboot_install_app2">[COLOR="SeaGreen"]The app can check for new TWRP versions.[/COLOR]</string>
<string name="reboot_install_app_prompt_install">[COLOR="SeaGreen"]Prompt to install TWRP app if not installed[/COLOR]</string>
<string name="reboot_install_app_system">[COLOR="SeaGreen"]Install as a System App[/COLOR]</string>
<string name="reboot_installing_app">[COLOR="SeaGreen"]Installing App...[/COLOR]</string>
<string name="swipe_to_install_app">[COLOR="SeaGreen"]Swipe to Install TWRP App[/COLOR]</string>
v3.1.1-3 new Xposed functions strings:
Code:
!-- v.3.1.1-3 Xposed functions strings -->
<string name="advanced2_btn">[COLOR="SeaGreen"]More...[/COLOR]</string>
<string name="xposed_dis_btn">[COLOR="SeaGreen"]Disable Xposed[/COLOR]</string>
<string name="xposed_en_btn">[COLOR="SeaGreen"]Enable Xposed[/COLOR]</string>
<string name="more_hdr">Advanced >[COLOR="SeaGreen"] More[/COLOR]</string>
<string name="xposed_dis_note1">[COLOR="SeaGreen"]If you experience bootloop after Xposed Framework[/COLOR]</string>
<string name="xposed_dis_note2">[COLOR="SeaGreen"]or Module install you should do this.[/COLOR]</string>
<string name="xposed_en_note1">[COLOR="SeaGreen"]Is your Xposed Framework or Module[/COLOR]</string>
<string name="xposed_en_note2">[COLOR="SeaGreen"]related bootloop issue fixed?[/COLOR]</string>
<string name="swipe_to_dis_xposed">[COLOR="SeaGreen"]Swipe to Disable Xposed[/COLOR]</string>
<string name="swipe_to_en_xposed">[COLOR="SeaGreen"]Swipe to Enable Xposed[/COLOR]</string>
<string name="xposed_dis">[COLOR="SeaGreen"]Disabling Xposed...[/COLOR]</string>
<string name="xposed_dis_complete">[COLOR="SeaGreen"]Xposed Disabled[/COLOR]</string>
<string name="xposed_en">[COLOR="SeaGreen"]Enabling Xposed...[/COLOR]</string>
<string name="xposed_en_complete">[COLOR="SeaGreen"]Xposed Enabled[/COLOR]</string>
TODO:
- translate the new stuff - partially done... Too complicated for Google translate. Need help.
- rescale the UI to use the full screen space with navbar disabled - DONE:good:
- add new option to reset lockscreen security settings after userdata restore - DONE:good:
- maybe add option for quick Xposed enable/disable... Useful for testing when device boot loops after ROM flash; - DONE:good:
- rebuild it including kernel with Android 7.1 branch - DONE:good:
- open to more useful ideas... Just tell me...
Changelog:
08-02-2018
- implement extra step to ensure TWRP is not replaced after stock ROM flash(ensure "Mount > Mount system partition read-only" checkbox is cleared before reboot)
- sync with latest v.3.2.3 Omnirom sources
07-07-2018
- sync with latest Omnirom sources
03-02-2018
- fix no controls(navbar and buttons disabled) in some cases
- optimize Navbar disable/enable routine
- dynamic Oreo /vendor partition support if detected(mount, wipe, backup, restore)
- sync with latest Omnirom sources
01-29-2018
- fix and use busybox again for better compatability
- respect "Mount > Mount system partition read-only" setting when renaming stock recovery to prevent boot stuck @logo if system verify flag is set in fstab
- sync with latest Omnirom sources
01-14-2018
- Fix for lame updater-scripts calling missing busybox
- actually set all device specific properties per code name... no more hydrolium unified device properties
01-03-2018
- Fix tar executable
12-17-2017
- Switch to latest android-8.1 TWRP v.3.2.1 branch
10-28-2017
- New Enable/Disable Xposed function(if installed) - Advanced > More, useful if experiencing bootloops after framework/module install.
- Moved Reset Lockscreen function to Advanced > More
10-14-2017
- Auto detect possible use of legacy props by update-binary - no more 2nd flash retry and confusing error/warning messages, any zip just works no matter what Android version it was build with/for
09-05-2017
- fix flashing zips using old update-binary(like my firmware zips). Recovery will retry 2nd flash so ignore 1st try errors!
09-03-2017_OREO
- v.3.1.1-2: Oreo ROMs flashing compatible!
09-03-2017_fixed-2
- fix missing (Up A Level) everywhere when browsing for file/folder
- remove ability for TWRP GUI to restore ADB Backup for now - braking the above
09-03-2017_fixed
- fix device identify props not set at boot
09-03-2017
- remove TWRP app
- add support for mixed adopted storage + removable storage partitioned SD Card
- add ability for TWRP GUI to restore ADB Backup
- recognize and use /persist as settings storage - try to load settings before decrypt
- add Brazilian Portuguese translation
- synced with latest TWRP 7.1 sources
07-07-2017
- kernel: enable EXFAT and NTFS support(does it fix OTG EXFAT/NTFS drives access!?)
- Backup Options: add option to exclude dalvik-cache for faster and smaller backups
- synced with latest TWRP 7.1 sources
06-12-2017
- use more reliable busybox instead of toolbox(should fix flash/backup restore corrupting /system and /modem in some cases - needs testing)
- synced with latest TWRP 7.1 sources
05-14-2017
- updated to v.3.1.1 code
- built with Android 7.1.2 tree
- synced with latest TWRP 7.1 sources
04-29-2017
- digest: Force lower case md5 compare - https://github.com/TeamWin/Team-Win-Recovery-Project/issues/912
- ADB Backup: fix adb restore issues - https://github.com/nijel8/TWRP/commit/d49427ec4917ab11fdd81d7d06f47bf298e56105
- synced with latest TWRP 7.1 sources
04-07-2017
- fix adb error: device unauthorized
- synced with latest TWRP 7.1 sources
03-24-2017
- switch to in-recovery decryption binaries: fixes decryption for MIUI A-6.0 ROMs
- fix reboot when no OS is present
03-17-2017
- fix ramdisk for 2/16GB hydrogen
- Turkish translation for extra functions added
03-14-2017
- v.3.1.0-1 first release
02-21-2017[/B
- removed logcat - was causing unmount /system failure after backup/restore operations
- fix missing libf2fs.so needed by mkfs.f2fs in some cases
02-21-2017
- added logcat capabilities
02-18-2017
- fixed a major issue with encrypted userdata. Now TWRP supports(should, need testing) userdata decryption with all types of passwords - default(hardware), PIN, pattern etc, regardless what ROM is in use.
- build with Lineage 14.1 sources
02-16-2017
- fixed MIUI userdata decryption this time for sure , kinda pointless b/c MIUI wont boot once TWRP renames /system/boot-from-recovery.p file and /system verify flag present in fstab.qcom... but at least you wont loose your data
- userdata qualcomm hardware decryption works for any ROM now (MIUI/AOSP/Lineage based)
- fixed navbar still visible when disabled in "Select storage" screen
02-12-2017
- added encryption support, now you can backup/restore everything that matters (bootloader, modem, etc) - credit goes to @TheStrix (as usual)
01-19-2017
- synced to latest TWRP code, added f2fs encryption support in kernel(full f2fs support yet to come), improved lockskreen reset routine
01-07-2017
- freshly build kernel, old sdcardfs enabled CM14.1 kernel might cause problems... Update TWRP just in case!!!
12-28-2016
- added Chinese Traditional strings - Thanks @tarkzim
Download:
(08-02-2018)twrp_v323-4_hydrogen-helium_nijel8-MOD.img
Github sources:
Unified device tree
TWRP Mod repo
Kernel source
Thnx. I will try.
Sent from my MI MAX using Tapatalk
How to install the image file in Mi MAX?
yplim2300 said:
How to install the image file in Mi MAX?
Click to expand...
Click to collapse
If you already have TWRP installed save the img file here to ur memory card and reboot to recovery and then select img instead of flash zip in TWRP option.
My phone is new, I do not have TWRP at all.
So, how to install it?
yplim2300 said:
My phone is new, I do not have TWRP at all.
So, how to install it?
Click to expand...
Click to collapse
Best way to install TWRP is to unlock bootloader 1st.
OR you can try the method given here...
http://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594
:good:
yplim2300 said:
How to install the image file in Mi MAX?
Click to expand...
Click to collapse
or just use Flashify (need root). Download it on Playstore
Download link is dead (for me)....is it?
Edited: Woring now. Thanks.
JulianJenner said:
Download link is dead (for me)....is it?
Sent from my MI MAX using Tapatalk
Click to expand...
Click to collapse
Something was wrong with Google Drive... Refreshed the link and now works for me.
nijel8 said:
Something was wrong with Google Drive... Refreshed the link and now works for me.
Click to expand...
Click to collapse
hello nijel8 sorry for off topic but I really need your help, can you please make data fix similar to what you did for CM-RR for miui because any miui rom after 23/06/2016 is not working with my provider, yes I have H,H+ but no stable data traffic, while this one and older miui give me correct data connection , I tried to use your fix but it does not work in miui it flashes ok but no change. please do this for me if you have time ,,
First post updated with new build... Read for details...
You can help translate this thing by copying below code, translate the strings in green and post it here mentioning your language. I will add it in new build. Thank you!
Code:
<!-- Reset Lockscreen function strings -->
<string name="reset_lockscreen_btn">[COLOR="SeaGreen"]Reset Lockscreen[/COLOR]</string>
<string name="reset_lockscreen_hdr">[COLOR="SeaGreen"]Reset Lockscreen[/COLOR]</string>
<string name="reset_lockscreen_note1">[COLOR="SeaGreen"]If you cannot pass Lockscreen security[/COLOR]</string>
<string name="reset_lockscreen_note2">[COLOR="SeaGreen"]after backup restore you should do this.[/COLOR]</string>
<string name="swipe_to_reset_lockscreen">[COLOR="SeaGreen"]Swipe to Reset Lockscreen[/COLOR]</string>
<string name="resetting_lockscreen">[COLOR="SeaGreen"]Resetting Lockscreen...[/COLOR]</string>
<string name="reset_lockscreen_complete">[COLOR="SeaGreen"]Reset Lockscreen Complete[/COLOR]</string>
<!-- v.3.0.3-0 new TWRP App install strings -->
<string name="reboot_install_app_hdr">[COLOR="SeaGreen"]Install TWRP App?[/COLOR]</string>
<string name="reboot_install_app1">[COLOR="SeaGreen"]Would you like to install the Official TWRP App?[/COLOR]</string>
<string name="reboot_install_app2">[COLOR="SeaGreen"]The app can check for new TWRP versions.[/COLOR]</string>
<string name="reboot_install_app_prompt_install">[COLOR="SeaGreen"]Prompt to install TWRP app if not installed[/COLOR]</string>
<string name="reboot_install_app_system">[COLOR="SeaGreen"]Install as a System App[/COLOR]</string>
<string name="reboot_installing_app">[COLOR="SeaGreen"]Installing App...[/COLOR]</string>
<string name="swipe_to_install_app">[COLOR="SeaGreen"]Swipe to Install TWRP App[/COLOR]</string>
...some more screenshots...
nijel8 said:
First post updated with new build... Read for details...
You can help translate this thing by copying below code, translate the strings in green and post it here mentioning your language. I will add it in new build. Thank you!
Code:
<!-- Reset Lockscreen function strings -->
<string name="reset_lockscreen_btn">[COLOR="SeaGreen"]Reset Lockscreen[/COLOR]</string>
<string name="reset_lockscreen_hdr">[COLOR="SeaGreen"]Reset Lockscreen[/COLOR]</string>
<string name="reset_lockscreen_note1">[COLOR="SeaGreen"]If you cannot pass Lockscreen security[/COLOR]</string>
<string name="reset_lockscreen_note2">[COLOR="SeaGreen"]after backup restore you should do this.[/COLOR]</string>
<string name="swipe_to_reset_lockscreen">[COLOR="SeaGreen"]Swipe to Reset Lockscreen[/COLOR]</string>
<string name="resetting_lockscreen">[COLOR="SeaGreen"]Resetting Lockscreen...[/COLOR]</string>
<string name="reset_lockscreen_complete">[COLOR="SeaGreen"]Reset Lockscreen Complete[/COLOR]</string>
<!-- v.3.0.3-0 new TWRP App install strings -->
<string name="reboot_install_app_hdr">[COLOR="SeaGreen"]Install TWRP App?[/COLOR]</string>
<string name="reboot_install_app1">[COLOR="SeaGreen"]Would you like to install the Official TWRP App?[/COLOR]</string>
<string name="reboot_install_app2">[COLOR="SeaGreen"]The app can check for new TWRP versions.[/COLOR]</string>
<string name="reboot_install_app_prompt_install">[COLOR="SeaGreen"]Prompt to install TWRP app if not installed[/COLOR]</string>
<string name="reboot_install_app_system">[COLOR="SeaGreen"]Install as a System App[/COLOR]</string>
<string name="reboot_installing_app">[COLOR="SeaGreen"]Installing App...[/COLOR]</string>
<string name="swipe_to_install_app">[COLOR="SeaGreen"]Swipe to Install TWRP App[/COLOR]</string>
...some more screenshots...
Click to expand...
Click to collapse
here is my translation for Chinese Traditional.
Code:
<!-- Reset Lockscreen function strings -->
<string name="reset_lockscreen_btn">[COLOR="SeaGreen"]螢幕鎖定重置[/COLOR]</string>
<string name="reset_lockscreen_hdr">[COLOR="SeaGreen"]螢幕鎖定重置[/COLOR]</string>
<string name="reset_lockscreen_note1">[COLOR="SeaGreen"]如果你無法通過螢幕解鎖認證[/COLOR]</string>
<string name="reset_lockscreen_note2">[COLOR="SeaGreen"]你應該進行這個程序，在你還原你的備份之後[/COLOR]</string>
<string name="swipe_to_reset_lockscreen">[COLOR="SeaGreen"]滑動以重置螢幕鎖定[/COLOR]</string>
<string name="resetting_lockscreen">[COLOR="SeaGreen"]螢幕鎖定重置中...[/COLOR]</string>
<string name="reset_lockscreen_complete">[COLOR="SeaGreen"]螢幕鎖定重置完成[/COLOR]</string>
<!-- v.3.0.3-0 new TWRP App install strings -->
<string name="reboot_install_app_hdr">[COLOR="SeaGreen"]安裝 TWRP 應用程式?[/COLOR]</string>
<string name="reboot_install_app1">[COLOR="SeaGreen"]你要安裝官方的 TWRP 應用程式嗎?[/COLOR]</string>
<string name="reboot_install_app2">[COLOR="SeaGreen"]此應用程式可以檢查新的 TWRP 版本[/COLOR]</string>
<string name="reboot_install_app_prompt_install">[COLOR="SeaGreen"]如果未安裝TWRP應用程式，彈出詢問[/COLOR]</string>
<string name="reboot_install_app_system">[COLOR="SeaGreen"]安裝為系統程式[/COLOR]</string>
<string name="reboot_installing_app">[COLOR="SeaGreen"]安裝應用程式中...[/COLOR]</string>
<string name="swipe_to_install_app">[COLOR="SeaGreen"]滑動已安裝 TWRP 應用程式[/COLOR]</string>
Refuses to work on my Hydrogen. Mostly just black screen, with the TeamWin logo flashing occasionally.
AttK0 said:
Refuses to work on my Hydrogen. Mostly just black screen, with the TeamWin logo flashing occasionally.
Click to expand...
Click to collapse
working nice on helium, no more errors , thanks dev for this it's even looding faster now:good:
AttK0 said:
Refuses to work on my Hydrogen. Mostly just black screen, with the TeamWin logo flashing occasionally.
Click to expand...
Click to collapse
Can you run these two commands in PC prompt and post the files when it does that:
Code:
adb pull /tmp/recovery.log
Code:
adb pull /proc/kmsg
The two files "recovery.log" and "kmsg" will be in "C:\Users\[your user name]" folder...
Thanks
tombassi said:
working nice on helium, no more errors , thanks dev for this it's even looding faster now:good:
Click to expand...
Click to collapse
Does it say "3.0.3-0 for helium..." on front page?
AttK0 said:
Refuses to work on my Hydrogen. Mostly just black screen, with the TeamWin logo flashing occasionally.
Click to expand...
Click to collapse
Same with me,I get error device '< null>' not found when try to get recovery log
@AttK0 @rizky123
Please provide logs as I asked above... I can't help without knowing what is going on...
Also show me the content of "/proc/hwinfo" file after you boot back to Android.
EDIT:Delete old twrp settings file "/sdcard/TWRP/.twrp" from within Android and see if TWRP boots...
nijel8 said:
Does it say "3.0.3-0 for helium..." on front page?
Click to expand...
Click to collapse
Yes,
Sent from my Mi Max using XDA-Developers mobile app
New builds in OP...
Finished Chinese Traditional translation thanks to @tarkzim
New build with Android 6.0 branch and CM13 kernel for testing if 7.1 fails... @AttK0 @rizky123 try it...
The only reason I can think of without logs 7.1 fails for some is the different display hw... Need logs, please...
tombassi said:
Yes,
Sent from my Mi Max using XDA-Developers mobile app
Click to expand...
Click to collapse
Good... Means it works as intended:good:
Related
{
"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"
}
Unofficial build of CyanogenMod 11 (Android 4.4) for the HTC Desire C (Golfu)
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KITKAT), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* 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.
*/
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. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Working:
Camera
WiFi
Bluetooth
Mobile network
Camcorder
Video playback
VPN
Screenshot
Recent apps switching
Audio (playback/input/routing/headphones/etc)
SD card
NFC
All sensors (accelerometer, proximity sensor, etc. work)
GPS
Everything else, as long as it isn't listed as a bug
Major bugs:
No major bugs
Credits (in no particular order):
The CyanogenMod team
LegaCyMod
Armv6
cute_prince
sachinthomas
Testers for prompt testing
And all those who helped directly or Indirectly
XDA:DevDB Information
CM-11 For Golfu, ROM for the HTC Desire C
Contributors
kirmaniarslan, h1gh1
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Rooted
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 5
Stable Release Date: 2015-05-05
Created 2014-10-16
Last Updated 2015-05-05
Not working
- FM radio.
- Apps that expect newer libOMXVidEnc will not work, Skype is one example. Viber and WhatsApp are working.
- do not use stock browser for serious browsing, although it is working, it has bugs with adreno libs. For 2-step authentication on Google, it will do.
Upstream issues
SDCard not showing unmount option
Trebuchet crashing when you enable CM Home or Google Search as panel
Cyanogenmod stock camera app shows 4.5mp instead of 5 mp - camera works properly with other third party apps and takes 5MP pictures.
Sources: - cm-11.0 branches in each repo:
Device
Kernel
Vendor
Thanks:
CyanogenMod team, legacyMod & KonstaT, HTC Pico development team, TeamHackLg & everyone who's been working on CM11.
Downloads:
CM11 RC5 (194.45 MB)
Android File Host | BasketBuild
MD5: 63ff9995dad6d2f6798f5b6b8b1a8c11
Optional GAPPS:
http://forum.xda-developers.com/showthread.php?t=2779598(thanks @kodirovshchik for suggestion)
How to install:
You must update recovery with this one - TWRP 2.8.6.0 or this one Philz Touch 6.59.0 - ClockWorkMod 6.0.5.1- these two have SELinux support. Philz and CWM do not have support for F2Fs!
Install the recovery trough fastboot
- fastboot flash recovery recovery.img
Reboot to recovery from fastboot
- make a backup of your current ROM to SDCard
- wipe -> do a factory reset
- wipe -> advanced wipe -> select only system and wipe
- install zips (rom and gapps)
- reboot to bootloader
if you are updating from previous CM11, you can dirty flash -> just wipe /system in Wipe -> Advanced Wipe, and install rom and gapps. No guarantees here.
Install boot image
fastboot flash boot boot.img
install boot.img that is inside the ROM that you downloaded
do not do fastboot erase cache
As of RC5, ROM now supports both EXT4 and F2FS in a same installation, and there is an easy way to switch back and forth between full EXT4 and F2FS setup, or any partition layout you would like (why would someone want this, I do not know, but the option is there).
Switching to F2FS from EXT4:
- You must install TWRP 2.8.6.0 with F2FS support.
- install RC5 and gapps (optionally), flash boot.img and restart. Check that the ROM is working properly. Activate advanced reboot in developer options. Reboot to recovery.
- backup - make a nandroid backup of system, data and cache.
- wipe, advanced wipe - select system - change or repair file system - choose F2FS. Repeat this for data and cache.
- settings -> Check use rm -rf instead of format.
- restore -> this will restore your data to existing partitions without format.
- settings -> Uncheck use rm -rf instead of format.
- reboot
You will boot to full F2FS ROM, with all your data and settings intact. Check it out in terminal with
mount | grep f2fs
How to build:
Up to date sources on github. (one patch for legacyMod frameworks_av is missing, will update device tree soon)
1. Follow instructions on initializing a build environment up to a point of downloading the source code.
2. Initialize CyanogenMod 11 repo.
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
3. Add local manifest that downloads HTC Desire C device config, properties and kernel source from my github and few CM replacement projects from legaCyMod github.
Code:
curl --create-dirs -L -o .repo/local_manifests/local_manifest.xml -O -L https://raw.githubusercontent.com/high1/android_local_manifest/cm-11.0/local_manifest.xml
4. Sync source code.
Code:
repo sync
5. Update prebuilts
Code:
cd path-to/cm11/vendor/cm/
./get-prebuilts
6. Apply patches
Code:
path-to/cm11/device/htc/golfu/patches./apply.sh
7. Compile.
Code:
cd path-to/cm11/
. build/envsetup.sh
brunch cm_golfu-userdebug -jx
(x is number of your processor cores -+1)
'repo sync' to pull merged changes from upstream.
'make clobber' to clean the build environment.
Repeat step 7 to make a new build.
FAQ:
Q: I can't find developer options and performance settings, why?
A: Settings -> About phone -> Click 'Build number' several times
Q: I don't have reboot options in power menu, why?
A: Settings -> Developer options -> Advanced reboot
Q: Is ART runtime working?
A: Yes it is. Beware, it is not compatible with xposed framework.
Q: How to make fastboot and adb work with Windows 8.1? (Device enumeration failed error)
A: First, make sure you have this update installed - http://www.microsoft.com/en-pk/download/details.aspx?id=43515 . Unzip http://goo.gl/CAXglZ and merge it to your registry. HTC drivers must be installed, compatible with Windows 8.1 here: http://forum.xda-developers.com/showthread.php?t=2714921
Q: USB tethering does not work?
A: Here is a guide: Android USB Tethering In Windows 8.1
Changelog
3.5.2015 changelog:
- one ROM for both file systems - made multiple file system patch work on CM11, and update fstab and updater-script for that,
- fixed black screen in call - updated touchscreen and proximity driver from cyanogen_htc_msm8960 3.4 kernel, and updated board definitions, so that the proximity sensor is now working properly
- switched back to legacy OMX - camera recording is working, and the latest Viber is working properly. Skype is crashing due to old OMX libraries, but does not render the phone useless.
- using adreno libraries from TeamHackLGE - just for testing
- updated libqc-opt.so from TeamHackLGE repo - seems that this fixes some schedulers get stuck on lowest frequency.
- addes sioplus scheduler to kernel.
10.4.2015 changelog:
- released two separate ROMs, ext4 and full f2fs
- f2fs ROM got hand update for updater-script and fstab
- fixed errors reported when installing the ROM - updater-script has hardcoded filesystem, and this was the cause
- fixed the camera regression
7.4.2015 changelog:
Device tree:
- switched to HtcLegacy display-caf, which fixes high idle battery drain
- updated OMX libraries from TeamHackLG msm7x27a vendor repo - this fixes Viber, Skype etc, but video recording is broken
- switched to QCOM power HAL
- bluetooth vendor library is now in /vendor
- switched to Cyanogenmod frameworks_av
- cleaned up patches (down to only three and one replaced repo - this is almost pure CM11)
- switched to TWRP 5.1 branch, and made it compile with CM11 tree
- switched to QACT for audio lib
- compiling nightly again, as CM11 is EOL, and I think no new milestones will happen
- forcing high-end graphics is not default anymore
- moved adreno libs in vendor tree to vendor folder, removed one unneeded fil
Kernel:
- updated touch and proximity drivers from 3.4 kernel
- headset profile from 3.4 kernel
- added lz4 compression to kernel
- Update zram and zsmalloc up-to 3.17 kernel changes (zsmalloc now used instead of xvmalloc)
- enabled lz4 compression for zram
- restored audit support
- further various updates to kernel
20.2.2015 changelog:
- fixed brightness bug by keeping original framebuffer stack
- fixed memory bug (0.00B shown)
- added f2fs support to kernel
- added intelliactive, adaptive and smartassH3 governors, and updated interactive. Enabled all governors in kernel.
- added zen scheduler. Updated BFQ scheduler to v7r7. Enabled all schedulers in kernel.
- updates to block stack, faster I/O
- ROM built pre deoxed - installation will be longer, first boot will be much shorter
- moved all the proprietaries to vendor tree
- added F2FS support to ROM and recovery
15.12. changelog:
- fixed Bluetooth regression
- added surface texture patch
- updated prebuilts
7.12. changelog:
source synced to CM11 M12
switched to pico kernel, ION build
ported ION changes to golfu board
new graphics libraries, latest that support our board
ported golfu panel driver to pico kernel
switched to kernel XZ compression
switched to display-caf - TeamHackLG with patch
removed a lot of legacy repos - only frameworks_av needs to be replaced now
using CM11 chromium webview - applications that call evaluateJavaScript work now
updated touchscreen drivers
simplified camera build
added Philz touch recovery to ROM build
12.11. changelog:
- new wireless driver, ported from samsung kernel
- kernel changes, needed for new driver - new wireless_ath stack, imported compat folder, Makefile tweaks - do not build ath.ko for golfu
- fixes wifi tether
- fixes soft reboot
9.11. changelog:
Remaining audio routing issues are fixed, libaudio updated so no need for patching.
Call recording works
Solved freezing issues (need confirmation)
decreased wake up delay, enabled slow blur, increased ui responsivness
some other tweaks for sleep mode, limiting number of runnig apps
monitoring net usage on proper interface
removed custom wifi, updated wireless definitions and switched to Cyanogenmod private lib for ath6kl
kernel makefile optimizations - proper flags for our device
-O2 optimizations - kernel fits to boot.image so it should also improve speed
24.10. changelog:
Synced with latest CM11 nightly
Fixed video - camera recording, youtube
Disabled haptic feedback by default
Enabled call recording
23.10. changelog:
Fixed Wifi
Kernel with overclocking - capped to 600 at start, overclockable to 900 - One kernel for All!!!
Fixed stock browser with legacyMod patches
legacyMod prebuilts
18.10. changelog:
Fixed camera rotation (excluded definitions for 3M golfu, sensor mount angle is 0, and fixed sensor driver file in kernel - thx to Sachin Thomas)
Fixed media_profiles.xml partially - you can start the video, but it crashes on recording start
Fixed nfc - firmware was missing
Enabled swap to zRAM KitKat style
Re-enabled HTC performance lock, but only during boot
(Fixes yet to be uploaded with next beta)
16.10. changelog:
Android 4.4.4
First public build
A lot of changes and cleanups to the ramdisk and boardconfig
Added SELinux support to kernel
Made a working, stable recovery, first with repacked zImage and then source built
ROM made bootable
Fixed adb
Fixed SDCard
Fixed Bluetooth
Fixed Audio
Fixed RIL
Partially working camera
Added TWRP to ROM build process instead of CWM
Disabled HTC performance lock and limited frequencies on first boot so that one image is usable for all and devices do not crash
Enabled KSM by default
This all would not be possible without help - I looked up alot to KonstaT that makes CyanogenMod for ZTE Blade III, and a lof of this post is taken from his way of posting. KirmaniArslan helped to solve quite a few quirks, and posted patches actively, and started the development - his device tree was made bootable.
I expect logcats from all who will do testing, and hopefully we can fix the remaining bugs and let this device have fully working Cyanogenmod (Omni, Pacman, AOKP hopefully later). Also, with the release, you have full permission to use the source to build other ROMs, only requirement is that if you find a fix, you do a pull request at Github.
Regards, and enjoy the ROM as much as you can.
kirmaniarslan said:
BETA 1 : https://mega.co.nz/#!mBZhHKaZ!jQ7_vJ...F9zzpyvNla5fgQ
Kernel for BETA 1 : https://mega.co.nz/#!KURjUALa!Rj-nlM...A0I7LIq5Xdj2YQ
Click to expand...
Click to collapse
Ok. Enter decryption key. =)
Reserved for testbuilds
kodirovshchik said:
Ok. Enter decryption key. =)
Click to expand...
Click to collapse
Links updated.
So. As for me.
Adb doesnt work at first boot, so i can't get logcat. All logs what i have - TWRP log.
Cyclic reboot. It works for 2-3 sec and reboots. ANd i cant even look at settings or enable debugging. 2sec and reboot. One thing i'm shure its not from overheating =(
upd:
ok... boot in safe mode gives me 2 extra seconds.. and... there is no developers menu. it is locked. and i cant unlock it.
upd2: nope. i definitely can't attach rom Log and Ksmg.
kodirovshchik said:
So. As for me.
Adb doesnt work at first boot, so i can't get logcat. All logs what i have - TWRP log.
Cyclic reboot. It works for 2-3 sec and reboots. ANd i cant even look at settings or enable debugging. 2sec and reboot. One thing i'm shure its not from overheating =(
upd:
ok... boot in safe mode gives me 2 extra seconds.. and... there is no developers menu. it is locked. and i cant unlock it.
Click to expand...
Click to collapse
Have you wiped everything properly ?
kirmaniarslan said:
Have you wiped everything properly ?
Click to expand...
Click to collapse
idk coz in the HOWTO there is only "do a factory reset". What is the proper way?
Upd: for me it looks like overclock problem =)
kodirovshchik said:
idk coz in the HOWTO there is only "do a factory reset". What is the proper way?
Upd: for me it looks like overclock problem =)
Click to expand...
Click to collapse
Try the boot.img inside the ROM then. But it should not behave like that. Wipe the system along with the factory reset.
I'm having problems with TWRP v 2.8.0.0 recovery. I was using clokwork before and after flashing my log gets spammed with couldn't mount emmc. Adding full log
Adding link to pastebin, because for some strange reason I got error in forum that file was invalid
http://pastebin.com/iRgFm13z
Sorted out this issue, but rom seems to be stuck on bootloop.
Added logcat
doweeez said:
I'm having problems with TWRP v 2.8.0.0 recovery. I was using clokwork before and after flashing my log gets spammed with couldn't mount emmc. Adding full log
Adding link to pastebin, because for some strange reason I got error in forum that file was invalid
http://pastebin.com/iRgFm13z
Sorted out this issue, but rom seems to be stuck on bootloop.
Added logcat
Click to expand...
Click to collapse
Could you try image packaged with the ROM? Seems that I must leave HTC Performance boot lock, as a lot of phones crash.
h1gh1 said:
Could you try image packaged with the ROM? Seems that I must leave HTC Performance boot lock, as a lot of phones crash.
Click to expand...
Click to collapse
Thanks. Got it booted
doweeez said:
Thanks. Got it booted
Click to expand...
Click to collapse
OK. Will post another test kernel image once I fix the boot performance lock.
h1gh1 said:
Try the boot.img inside the ROM then. But it should not behave like that. Wipe the system along with the factory reset.
Click to expand...
Click to collapse
Ok. For me "How to install" must looks like:
1. Install the recovery trough fastboot
2. Reboot to recovery from fastboot
3. install zip
4. reboot to bootloader
5. Install boot image
6. reboot
Mb is is caused by S-OFF, but I rly need to flash kernel only after flashing zip. Work with "normal" kernel.
Upd1: Does ART works? Cause it looks like it works.
Upd2: OMG ART rly works. Can't belive it =)
kodirovshchik said:
Ok. For me "How to install" must looks like:
1. Install the recovery trough fastboot
2. Reboot to recovery from fastboot
3. install zip
4. reboot to bootloader
5. Install boot image
6. reboot
Mb is is caused by S-OFF, but I rly need to flash kernel only after flashing zip. Work with "normal" kernel.
Click to expand...
Click to collapse
Flashing the ROM does not affect boot partition, because of S-OFF. Order of instalation (boot image first) should not affect booting. I enabled zRAM kitkat style in latest build, as you requested - we are compliant with Google recommendations for low RAM devices now. I forgot to say, yes but ART is working without any problems, as long as apps work with it.
h1gh1 said:
Flashing the ROM does not affect boot partition, because of S-OFF. Order of instalation (boot image first) should not affect booting. I enabled zRAM kitkat style in latest build, as you requested - we are compliant with Google recommendations for low RAM devices now. I forgot to say, yes but ART is working without any problems, as long as apps work with it.
Click to expand...
Click to collapse
ART it's rly cool surprise =) Nice =)
As for S-OFF, i rly think u cant make changes with boot if u phone is S-ON. When u swith it to S-OFF u can make changes from recovery. Any way i have no other explanation, why order is important for me. i'll try to test it =)
UPD: is there any trick in win8 for adb? cause for me adb works only from my linux laptop.
kodirovshchik said:
ART it's rly cool surprise =) Nice =)
As for S-OFF, i rly think u cant make changes with boot if u phone is S-ON. When u swith it to S-OFF u can make changes from recovery. Any way i have no other explanation, why order is important for me. i'll try to test it =)
UPD: is there any trick in win8 for adb? cause for me adb works only from my linux laptop.
Click to expand...
Click to collapse
Yes, there is. Import this in your registry - you must have a patch with workaround installed, http://www.microsoft.com/en-pk/download/details.aspx?id=43515
extract reg file from attached zip and merge it to your registry.
I'm having problems with USB mass storage. First time when I click to turn it on, it unmounts sd card, but I'm not able to access sd-card file on PC. Second time I click loading loops forever.
Have anyone encountered similar problems?
doweeez said:
I'm having problems with USB mass storage. First time when I click to turn it on, it unmounts sd card, but I'm not able to access sd-card file on PC. Second time I click loading loops forever.
Have anyone encountered similar problems?
Click to expand...
Click to collapse
It's ums file setting, looks like it. I chose MTP as default, as mass storage requires mounting, unmounting etc... Will be fixed in the next build. Thx.
h1gh1 said:
It's ums file setting, looks like it. I chose MTP as default, as mass storage requires mounting, unmounting etc... Will be fixed in the next build. Thx.
Click to expand...
Click to collapse
MTP seems to work. It detects as HTC EVO 4G LTE .
CyanogenMod 12.1 is a free, community built distribution of Android 5.1 (Lollipop) which greatly extends the capabilities of your phone.
{
"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"
}
ROM Features:
Based on latest CyanogenMod 12.1 sources
Compiled with SaberMod 4.9 and JustArchi's Optimizations V4.1 for maximum performance
Full F2FS support - no mount issues during ROM updates
SELinux set to 'permissive' by default
Android default UID and GID for internal storage
(No more write issues after formatting sdcard!)
Slim and fast user build
Kernel Features:
Based on latest CAF kernel sources (LA.AF.1.1.c1)
Compiled with ArchiToolchain 4.9 and several Cortex-A9 optimizations
Overclocking up to 1.62 GHz
Underclocking up to 162 MHz for maximum battery life
User-customizable CPU Voltage driver (thanks to faux123)
Intelliactive and IntelliMinMax CPU governors (thanks to faux123)
In-kernel Thermal Driver (thanks to franciscofranco)
SIO and FIOPS IO schedulers
F2FS (Flash-Friendly File System) support (Performance comparison vs EXT4)
FauxSound support for maximum audio gain control (thanks to faux123)
Latest TWRP recovery, including a Materialised TWRP theme by z31s1g
Be aware that improper usage of kernel features can cause serious damage to your device!
Only use the stuff above if you know what you're doing!
In agreement with the GPL, you can find the sources and defconfig used to compile this kernel right here.
Known Issues:
Please keep in mind that CM12.1 sources are still work in progress. As a result, some features may be broken or only partially working.
That's why I decided to only list device-specific issues below.
Below ~60% battery, the displayed battery level will reduce significantly on rebooting. This is a known issue with all AOSP based ROMs.
After switching to a new battery, I noticed this behavior is related to automatic battery calibration and directly affected by the health of your phone's battery.
Disclaimer:
By downloading and installing this ROM, you agree that I cannot be held responsible for any damage caused to your device while installing or using it. Please keep in mind that it's YOU who chose to do these modifications to your device!
Installation:
Make sure your bootloader is unlocked - if not, follow this guide: Link
First installation? Flash the boot.img from ROM zip via Flashtool (use Fastboot mode!)
Boot into TWRP recovery
Do a factory reset and wipe system partition
Flash latest ROM zip (check "Downloads" section)
Flash suitable GApps for CM12.1 or CM12
Flash latest SuperSU from here: Link
Reboot
Downloads:
Final CM12.1 version: Link (Last updated: Jan 08, 2016)
Final CM12 version: Link (Last updated: April 05, 2015)
CM default su binary: Link (Don't flash if you're using SuperSU!)
Uninstaller zip: Link (Restores default storage permissions)
Credits:
CyanogenMod Team for their active development on the CM12.1 sources.
updateing for helping me with lots of compilation issues and initial bugfixing.
JustArchi for his awesome optimizations!
Changelog:
- 20160108 (final build):
Latest CM12.1 changes
Fixed the lags in power save mode by slightly increasing the cpu clock
.Thanks to everyone for using and supporting my work! It's been a great time with you all!
- 20151115:
Latest CM12.1 changes
Optimized system for better RAM performance
Enabled CM Performance Profiles support
Reduced minimum screen brightness
Reverted Toast UI to AOSP default
- 20151010:
Latest CM12.1 changes
Reverted SONY lockscreen clock to AOSP default
Reverted softkeys to AOSP default
Removed Xperia fonts
- 20150929:
Latest CM12.1 changes
Added Xperia softkeys
Fixed missing TWRP boot splash screen
- 20150912:
Latest CM12.1 changes
- 20150824:
Latest CM12.1 changes
Recreated NeoKernel with latest CAF sources from here.
Updated ArchiDroid's Optimizations to V4.1
ROM is now built with SaberMod 4.9 toolchain!
Re-colored recoveryboot LEDs. Got sick of this ugly purple!
Replaced stock TWRP ui with latest Materialised Play theme from here. Credits to z31s1g for the great theme and ElArchibald for his help!
Recoveries present on FOTAkernel will be ignored from now on - fixes installation issues caused by broken CWM or outdated TWRP versions
Disabled Dex-Preoptimization to allow greater and easier customizability, as well as more free space on system partition
Fixed Xposed framework causing bootloops
Fixed GPS for some users (Got rid of QUIPC)
- 20150808:
Latest CM12.1 changes
- 20150726:
Latest CM12.1 changes
Added medium L2 clock rates to NeoKernel, should improve battery life
.NOTE: The device tree used to build this ROM is now fully open-source!
- 20150620:
Latest CM12.1 changes
Fixed delayed PIN screen on boot
Added SONY styled lockscreen clock from here. (Credits to idid idamrep!)
Included all stock Xperia fonts in the ROM
- 20150603:
Latest CM12.1 changes
Enabled Multiuser UI with 3 maximum users
Fixed Google Play Services repeatedly force closing
Updated TWRP sources to latest
- 20150516:
Latest CM12.1 changes
Minor fixes and optimizations in device source
- 20150424:
Latest CM12.1 changes
Update to Android 5.1.1
- 20150419:
Latest CM12.1 changes
Added unlimited call log mod from here
Fixed backup issues in TWRP (using updated sources now)
- 20150412:
Latest CM12.1 changes
Reverted updates in F2FS sources (should fix the random bootloops)
Fixed non-working sensors (added prebuilt sensors.msm8960.so)
- 20150405 (CM12.1 build):
Initial release of CM12.1 (Android 5.1)
Merged all kernel features and optimizations from CM12
Updated TWRP to 2.8.6.0
.NOTE: A full wipe is recommended, but not required!
- 20150405 (CM12 build):
Final CM12 build (Android 5.0)
Latest CM12 changes
Added SIO and FIOPS io schedulers
Added in-kernel Thermal Driver (thanks to franciscofranco)
Updated F2FS sources in kernel
Fixed the network disconnects when initiating a call
Reverted to TWRP 2.8.4.0 to fix some ui bugs
- 20150329:
Latest CM12 changes
Compiled with JustArchi's ArchiDroid Optimizations V4
Updated CAF kernel source
Additional kernel optimizations for Cortex-A9
Disabled debug flags in kernel
Switched to ArchiToolchain 4.9 for kernel
Switched to SaberMod 4.8 toolchain for ROM
Removed USB "Mass Storage" and "Charge only" modes
- 20150321:
Latest CM12 changes
- 20150314:
Latest CM12 changes
- 20150309:
Latest CM12 changes
(Introduces a bug: Clock in statusbar disappears on reboot. Hide/unhide statusbar clock in Settings as a workaround)
Removed FM Radio - Have a look at this one!
- 20150303:
Latest CM12 changes
Fixed the segmentation fault when trying to mount/remount
Most likely fixed the volume errors some people encountered
Reverted to AOSP LLVM compiler (QCOM one needs more work)
Minor bugfixes - FM Radio is still WIP for now
- 20150301:
Latest CM12 changes
Added FM Radio
Replaced AOSP LLVM compiler with Qualcomm one, optimized for krait cpus (thanks to MusterMaxMueller)
ROM is now built with Linaro 4.8 instead of SaberMod 4.8
Kernel is now built with Linaro 4.9 instead of SaberMod 4.10
Updated kernel source to latest CAF
Minor changes and improvements in device tree
- 20150222:
Latest CM12 changes
- 20150215:
Latest CM12 changes
FolderMount and "sd issue" fixed - ROM is now using android default uid for sdcard0
Added intellimm and intelliactive cpu governors (thanks to faux123)
Added ultra low CPU clocks to kernel (162 and 270 MHz)
F2FS (Flash-Friendly File System) support
Latest Faux Sound features
Graphite Loop Optimizations in kernel
O3 optimized GPU drivers
Updated TWRP to version 2.8.5.0
Some changes and cleanup in installer zip
.NOTE: From this version on, you will have to flash my neo-uninstall.zip before switching ROMs!
- 20150207:
Latest CM12 changes
- 20150201:
Latest CM12 changes
Removed CMUpdater
- 20150124:
Latest CM12 changes
- 20150118:
Latest CM12 changes
- 20150115:
Latest CM12 changes
Fixed the 3G issue that was present in version 20150112
Updated TWRP to version 2.8.4.0
- 20150112:
Latest CM12 changes
Merged official CM device repos
Added "Charge only" USB mode
Other minor fixes and improvements
- 20150104:
Latest CM12 changes
- 20141228:
Latest CM12 changes
New recovery splash screen, best looking with this Material TWRP theme
Fixed volume key not working when screen off
Optimized boot image size
Minor bugfixes and improvements
- 20141222:
Latest CM12 changes
Update to Android 5.0.2
Compiled the whole rom with O3 flags
Enabled Overclocking up to 1620 MHz in kernel
Added user-configurable undervolting interface
Updated kernel source
Enabled USB Mass Storage
- 20141216:
Latest CM12 changes
Notification LED fixed
Working TWRP recovery included (thanks to colonel_lp)
New lights hal (open source instead of proprietary one)
Switched to SaberMod toolchain
Added some kernel cflags, optimized for Cortex-A9 cpu architecture
- 20141208:
Initial release
If you like my work and want to support me, please hit that thanks button, give some positive feedback or consider a small donation for my efforts.
XDA:DevDB Information
CyanogenMod 12.1, ROM for the Sony Xperia V
Contributors
WhiteNeo
Source Code: https://github.com/WhiteNeo-?tab=repositories
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod 12.1
Version Information
Status: No Longer Updated
Created 2014-12-09
Last Updated 2016-01-08
Screenshots:
Video:
Here's another video by taaviu that gives you an impression of Android L.
FAQ:
How to update to latest build?
1. Reboot to recovery
2. Flash latest rom zip
3. Flash latest gapps linked in OP
4. Flash SuperSU
5. Wipe Cache & Dalvik Cache
6. Reboot
How to safely uninstall this rom?
1. If you were using F2FS, revert to EXT4 before uninstalling!
2. Reboot to recovery
3. Flash neo-uninstall.zip
4. Proceed with the installation steps of your new rom
Should you face storage issues with your new rom, run the following Terminal commands:
Code:
su
chmod 777 /mnt/media_rw/sdcard0
chown 2800:2800 /mnt/media_rw/sdcard0
chown -R 2800:2800 /mnt/media_rw/sdcard0
Troubleshooting:
I can't create folders in internal storage!
Follow the instructions on updating to latest build. While flashing, my rom will apply its required storage permissions automatically.
Alternatively, you may simply run the following Terminal commands:
Code:
su
chmod 777 /mnt/media_rw/sdcard0
chown 1023:1023 /mnt/media_rw/sdcard0
chown -R 1023:1023 /mnt/media_rw/sdcard0
Camera any Gallery won't save my photos!
Follow the instructions on updating to latest build. While flashing, my rom will apply its required storage permissions automatically.
Alternatively, you may simply run the following Terminal commands:
Code:
su
chmod 777 /mnt/media_rw/sdcard0
chown 1023:1023 /mnt/media_rw/sdcard0
chown -R 1023:1023 /mnt/media_rw/sdcard0
I can't move apps to sdcard!
Moving apps to internal storage is quite buggy and discouraged. I recommend repartitioning your device with the instructions below.
Advanced Modifications:
Switching to F2FS:
First of all, make sure you're running homebuild version 20150215 or later!
1. Copy all important files from internal storage to the external sdcard
2. Reboot to recovery
3. Do a full backup (make sure to select external sdcard as target location)
4. Disable MTP in "Mount" menu
5. Go to "Wipe" > "Advanced Wipe" menu
6. Check "System", then tap "FS Options" and "Change FS"
7. Select "F2FS", then swipe to apply the change
8. Repeat steps 5 and 6 for "Data" and "Cache" partitions, as well as internal storage
9. Navigate to TWRP Settings and check "Use rm -rf instead of formatting"
10. Restore your previous backup
12. Reboot to system
13. Restore your copied files from external sdcard
14. Reboot
Reverting to EXT4:
1. Copy all important files from internal storage to the external sdcard
2. Reboot to recovery
3. Do a full backup (make sure to select external sdcard as target location)
4. Disable MTP in "Mount" menu
5. Go to "Wipe" > "Advanced Wipe" menu
6. Check "System", then tap "FS Options" and "Change FS"
7. Select "EXT4", then swipe to apply the change
8. Repeat steps 5 and 6 for "Data" and "Cache" partitions, as well as internal storage
9. Navigate to TWRP Settings and check "Use rm -rf instead of formatting"
10. Restore your previous backup
12. Reboot to system
13. Restore your copied files from external sdcard
14. Reboot
Repartitioning your device:
Note:
Up to 14GB of free space on external sdcard might be required to perform the steps below! (Should be less if your internal storage isn't completely bloated )
The value XXXX used below has to be replaced with a calculated number and varies depending on your desired space. I recommend 5120, as it's a decent balance between general data storage (used for most apps) and space on internal storage for apps with bigger data (games). Refer to step 13 of this link if you want to calculate your own partition sizes.
1. Copy all important files from internal storage to the external sdcard with the following terminal command:
Code:
rsync -P -a /sdcard /ext_card/sdcard0/
2. Reboot to recovery
3. Do a full backup (make sure to select external sdcard as target location)
4. Navigate to "Mount" menu, disable MTP and unmount all partitions listed there
5. Navigate to "Advanced" > "Terminal Command" and type the following code:
Code:
parted /dev/block/mmcblk0 print
This command should display some text like this:
Code:
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 2228kB 2097kB TA
2 2228kB 3801kB 1573kB Boot
3 3801kB 5374kB 1573kB Boot2
4 6291kB 27.3MB 21.0MB Kernel
5 27.3MB 28.3MB 1049kB TZ
6 29.4MB 32.5MB 3146kB modemst1
7 33.6MB 36.7MB 3146kB modemst2
8 37.7MB 40.9MB 3146kB fsg
9 40.9MB 46.1MB 5243kB ramdump
10 46.1MB 54.5MB 8389kB ext4 apps_log
11 54.5MB 71.3MB 16.8MB FOTAKernel
12 71.3MB 1359MB 1288MB System
13 1359MB 1621MB 262MB Cache
14 1621MB 3769MB 2147MB Userdata
15 3769MB 7818MB 4050MB SDCard
We're going to remove Userdata and SDCard partitions, so check if these partitions also have the numbers 14 and 15 on your phone.
6. Type the following terminal commands to proceed with resizing the partitions:
Code:
parted /dev/block/mmcblk0 rm 14
parted /dev/block/mmcblk0 rm 15
parted /dev/block/mmcblk0 mkpartfs logical ext2 1621 [B]XXXX[/B]
parted /dev/block/mmcblk0 name 14 Userdata
parted /dev/block/mmcblk0 mkpartfs logical ext2 [B]XXXX[/B] 7818
parted /dev/block/mmcblk0 name 15 SDCard
7. Leave the terminal screen and go to "Wipe" > "Advanced Wipe" menu
8. Check "Data", then tap "FS Options" and "Change FS"
9. Select "EXT4" or "F2FS", then swipe to apply the change
10. Repeat steps 8 and 9 for internal storage (is named "sdcard" in this menu)
11. Restore your previous backup
12. Restore your backed-up files from external sdcard with the following terminal command:
Code:
cp -a /external_sd/sdcard0/* /sdcard/
13. Reboot
14. Enter the following terminal commands to fix storage permissions:
Code:
su
chmod 777 /mnt/media_rw/sdcard0
chown 1023:1023 /mnt/media_rw/sdcard0
chown -R 1023:1023 /mnt/media_rw/sdcard0
Finally I'll test soon
Aria.A97 said:
Finally I'll test soon
Click to expand...
Click to collapse
Thanks, make sure to give some feedback here.
Upload will be finished in around 15min.. Time to do a Titanium Backup.
WhiteNeo said:
Thanks, make sure to give some feedback here.
Upload will be finished in around 15min.. Time to do a Titanium Backup.
Click to expand...
Click to collapse
Yeah, of course Some minutes ago I saw it was uploaded, but only 72 MBs
Aria.A97 said:
Yeah, of course Some minutes ago I saw it was uploaded, but only 72 MBs
Click to expand...
Click to collapse
I know.. It seems like AFH had some problems with uploading.
By the way, rom is online.
With the whole "no working recovery included", does it mean that we cant flash one to FOTAkernel afterwards?
By the way, you are a freaking champion for releasing this ROM, and thanks for all the work you put into making our phones better
Swidilator said:
With the whole "no working recovery included", does it mean that we cant flash one to FOTAkernel afterwards?
By the way, you are a freaking champion for releasing this ROM, and thanks for all the work you put into making our phones better
Click to expand...
Click to collapse
Just doing what I can.
However, I gotta mention that I would never have come that far without @updateing.
Once more huge thanks for your help!
FOTA recovery should work, as the phone boots properly into recovery. You may give this a shot, I remember having seen a FOTA TWRP version by championswimmer in Cross Device Forum. :good:
The problem is that the recovery is not CWM anymore. CyanogenMod team is developing their own recovery at the moment. And that one doesn't work (yet)
Download complete. Gapps server was really slow. For me it took 13 minutes to download only Gapps. Now I'm doing a full nandroid backup.
Edit 1 : Booted. WiFi, Bluetooth and Cellular works fine. I'll report more soon
Edit 2 : Report after 40 minutes of use : Fully stable. Other stuff including camera and root access work completely fine. I just had 1 setting FC at first. This ROM is smooth enough (not as much as expected Lool)
These are all of bugs I found :
1. Setting - bluetooth menu - when searching, that circle animation has some problems
2. Setting - Wireless & networks - More - Cellular networks - Carrier settings makes "com.android.phone" FC. (Maybe it's carrier related )
3. The most important bug I've found (not for me, but it can be a disaster for some others ) is Notification/Battery LED does not work at all.
By the way, I have functional CM Recovery. I was able to boot into recovery by selecting reboot recovery power menu. CM Recovery appeared. Even touch is working fine but there is no backup/restore related option.There was just apply update from zip and reboot.
After all, really thanks for your work it's awesome, as always
WhiteNeo said:
Just doing what I can.
However, I gotta mention that I would never have come that far without @updateing.
Once more huge thanks for your help!
FOTA recovery should work, as the phone boots properly into recovery. You may give this a shot, I remember having seen a FOTA TWRP version by championswimmer in Cross Device Forum. :good:
The problem is that the recovery is not CWM anymore. CyanogenMod team is developing their own recovery at the moment. And that one doesn't work (yet)
Click to expand...
Click to collapse
Nice work . But can u make dis work on xperia T
Aria.A97 said:
Download complete. Gapps server was really slow. For me it took 13 minutes to download only Gapps. Now I'm doing a full nandroid backup.
Edit 1 : Booted. WiFi, Bluetooth and Cellular works fine. I'll report more soon
Edit 2 : Report after 40 minutes of use : Fully stable. Other stuff including camera and root access work completely fine. I just had 1 setting FC at first. This ROM is smooth enough (not as much as expected Lool)
These are all of bugs I found :
1. Setting - bluetooth menu - when searching, that circle animation has some problems
2. Setting - Wireless & networks - More - Cellular networks - Carrier settings makes "com.android.phone" FC. (Maybe it's carrier related )
3. The most important bug I've found (not for me, but it can be a disaster for some others ) is Notification/Battery LED does not work at all.
By the way, I have functional CM Recovery. I was able to boot into recovery by selecting reboot recovery power menu. CM Recovery appeared. Even touch is working fine but there is no backup/restore related option.There was just apply update from zip and reboot.
After all, really thanks for your work it's awesome, as always
Click to expand...
Click to collapse
Thanks for testing
I think the carrier settings fc and led stuff is device related. Will try to fix it in next build. :good:
Booting in recovery works fine, but flashing does not work.
I'm sure CM team will fix this soon.
Installed in the morning.
Had no crushes yet, no bugs in animation that I`ve seen. However, power consumption is dramatically high compared to stock 4.3 JB. Most time processor runs at 1.5ghz.
WhiteNeo said:
Thanks for testing
I think the carrier settings fc and led stuff is device related. Will try to fix it in next build. :good:
Booting in recovery works fine, but flashing does not work.
I'm sure CM team will fix this soon.
Click to expand...
Click to collapse
So the problem is caused by CM recovery?
Allen Hu said:
So the problem is caused by CM recovery?
Click to expand...
Click to collapse
Exactly. :good:
Hi
It's my first time to post something so I don't know if I'm doing it right
So
First of all thank you for the ROM and the great work keep it up :good:
Second I found some other bugs Dunno if it's apps releated or something in the ROM itself
1. Gestures keyboard doesn't work
2. Google Play services keep asking to update it "and it's up to date"
3. Tap and hold doesnt work "quick toggles" in notification centre. and is it CM feature ?
An other question
When A new release is out can I flash CM11 kernel to flash the new release since I flashed it using CWM I was on CM11
P.S I didnt wipe data or system wipe just backed up the old ROM and flashed this one didn't want to re-install all apps etc..
Very good looking rom. Flashing right now, got first bootloop....because i flashed cm12 kernel. That was my fault. Now im already setting my device up.
Looks like LTE aslo working.
Any good ideas how to make navibar smaller? Xposed wont work with 5.0 as i know.
Shady_BlackSn0w said:
Hi
It's my first time to post something so I don't know if I'm doing it right
So
First of all thank you for the ROM and the great work keep it up :good:
Second I found some other bugs Dunno if it's apps releated or something in the ROM itself
1. Gestures keyboard doesn't work
2. Google Play services keep asking to update it "and it's up to date"
3. Tap and hold doesnt work "quick toggles" in notification centre. and is it CM feature ?
An other question
When A new release is out can I flash CM11 kernel to flash the new release since I flashed it using CWM I was on CM11
P.S I didnt wipe data or system wipe just backed up the old ROM and flashed this one didn't want to re-install all apps etc..
Click to expand...
Click to collapse
Bugs 1 and 3 are related to CM sources. Number two is most likely caused by your dirty installation. (Which I don't recommend, by the way)
Thats the plan.. Until CM recovery works we gotta fastboot NeoKernel and flash the update from its included recovery. :good:
taaviu said:
Very good looking rom. Flashing right now, got first bootloop....because i flashed cm12 kernel. That was my fault. Now im already setting my device up.
Looks like LTE aslo working.
Any good ideas how to make navibar smaller? Xposed wont work with 5.0 as i know.
Click to expand...
Click to collapse
LTE is working? That's great news! :good:
Can anyone confirm this?
No idea how to resize the navbar, but I'm sure CM team will add a customnization option soon.
Temporary Fix for play service
Disable app notifications in settings
Again thank you @WhiteNeo :good:
WhiteNeo said:
LTE is working? That's great news! :good:
Can anyone confirm this?
Click to expand...
Click to collapse
I Confirm. LTE working.
Thank You for the excelient work :good:
{
"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"
}
Here I will share my builds of CyanogenMod 14.1 (Android 7.1) for the Nexus 4.
These will probably become obsolete in future when CM will officially release nightlies, but if as me you can't wait, you can flash it as usual zips!
[About this build]
- Require bootloader/radio from Lollipop minimum
- Contains all CM (kernel, system, ...) + my additional fixes to bring up the device
- This supports LTE. Make sure you have a proper radio for this.
[Note before installation]
- I suggest you to backup your app data with Titanium Backup if you want to restore your apps later
[Downloads]
* Build 11-27
- Build 11-24
- Build 11-17
- Build 11-11
- Build 11-05 (needs a clean install)
- Build 11-02
- Gapps (ARM/7.1/Pico is fine)
[How to install]
- Download latest CM ZIP (see above) + Latest Gapps if you want Google apps.
- Boot in recovery (TWRP - please use latest)
- Wipe System + Dalvik cache + cache. If you come from another ROM, wipe data
- Flash CM zip
- Flash gapps (Flash it along with step3's zip)
- Reboot & Enjoy
[Some recommandations]
- Enable Developer Options: Settings -> About -> tap 7 times on Build number
- Enable USB Debbuging
- Enable Offline APK installations: Security -> Unkown sources
- To enable 3G/4G (if supported by your radio/network): Settings -> More -> Mobile networks -> choose your preferred type !
[About Theme Engine]
- It is coming very soon.
[Working / Known issues]
** Not working **
- Camera is broken actually but I'm working on it
- Video recording is broken but I'm working on it
- Let me know
** Working **
- Everything else
- Installation images has grown, so there is no bigger space available in /system partition. That's why you should use Pico gapps if you need Google Applications.
[Source / Credits]
- Google / CyanogenMod / StephanMc Github / Dmitry Grinberg for his awesome work on N4 / OpenGapps / zaclimon / all developers involved in N for our device
[Changelog]
- Checkout second thread post.
If you are a developer and want to help, feel free to pm/email me
If you find this useful, feel free to hit thanks button, make me a donation to support development, or share it with people you love
.
Changelog build 11-27
Code:
project bootable/recovery/
- bootloader_message: allow devices to override
- fstools: Add libselinux dep
project device/lge/mako/
- mako: Remove enhanced NFC feature
- Update fingerprint
- Revert "mako: fix network values * in the factory images network values are set 10,0,1 but AOSP is set 9,0,1 lets fix it"
- mako: Enable triple framebuffers
- mako: proper rights for kickstart service
- Remove Power Control Widget reference
- Switch to Internal CM File Utils
- msm8960: Delete dhcpcd init entries, since dhcpcd is no more.
- mako: Tune TCP performance Based on CAF values.
- Build libc with GCC
project external/f2fs-tools/
- f2fs-tools: hack headers to unbreak darwin build
- libf2fs_fmt: Add missing src file
project external/libnfc-nci/
- libnfc-nci: set NXP_CHIP_TYPE based on BOARD_NFC_CHIPSET
project external/openssh/
- Merge branch 'master' of https://android.googlesource.com/platform/external/openssh into cm-14.1
project external/toybox/
- losetup: Fix loop mounting
- toybox: Remove -e from @echo
- toybox: kill colors
project external/vim/
- vim: kill colors
project frameworks/av/
- audioflinger: Fix audio for WifiDisplay
project frameworks/base/
- SystemUI: make clock and date clickable in statusbar
- Make Build.TYPE and Build.FINGERPRINT consistent for apps.
- SystemUI: change back button to hide ime button with rotate animation.
- usb: ensure accessory detached sent on re-attach
- Automatic translation import
- sounds: remove last trace of Tejat.ogg
- Remove duplicate audio: Tejat is Argon
- Option to use volume keys to control media volume anytime (2/2)
- Automatic translation import
- Automatic translation import
- base: update settings material colors to match systemUI
project hardware/qcom/audio-caf/msm8960/
- hal: Port the dock support to non-legacy 8960 hal
project hardware/qcom/audio-caf/msm8994/
- hal: Fix warnings in audio HAL and policy
- policy_hal: fix improper voice-playback concurrency handling
- hal: Add performance lock for playback usecase
- hal: update combo device handling
- hal: Add support for LINE out device
project hardware/qcom/display/
- qservice: Allow camera server to call into HWC
project packages/apps/Nfc/
- Automatic translation import
project packages/apps/PackageInstaller/
- Automatic translation import
- Fix PackageInstaller FC when tapping on a downloaded apk notification
project packages/apps/Settings/
- Settings: Remove A/B preference if unsupported
- Automatic translation import
- Automatic translation import
- Automatic translation import
- Settings: skip Misc/Overcounted battery stats in builds
project packages/apps/SoundRecorder/
- SoundRecorder: Add permission for ACCESS_NETWORK_STATE
- Automatic translation import
project packages/apps/UnifiedEmail/
- Revert "UnifiedEmail: not show "help&feedback" in general settiings if url is null"
project packages/providers/MediaProvider/
- MediaProvider: Add read storage permission
project vendor/cm/
- cm: config: Remove enhanced NFC feature
- build: kernel: Remove duplicated targets
- build: Set android jack args to global jack server args if existing
- extract_utils: Use shasum on macOS
- cm: enable hidden storage manager
Downloading
Before I try this ROM, I need to ask.
In the ROM cm14, I installed 24/10 cleanly, used a couple days then updated to 01/11 dirty but came an issue reboot into recovery( I couldn't reboot into system any more). So I restored to original stock image then flashed 01/11 cleanly and now work fine.
When the issue(mentioned upon) happened, I wiped all things but didn't work. And I tried an older version(24/10) but didn't work neither.
So, the question is, what is the correct way to update your ROM? Do I have to wipe dalvik and cache?
dcshallot said:
I couldn't reboot into system any more
Click to expand...
Click to collapse
What do you mean?
I just installed 11-02 and I think I'm in a boot loop. I see the logo and sometimes my n4 shakes. I wiped everything before I flashed 11-02 and de Gapps.
brunoqc said:
What do you mean?
I just installed 11-02 and I think I'm in a boot loop. I see the logo and sometimes my n4 shakes. I wiped everything before I flashed 11-02 and de Gapps.
Click to expand...
Click to collapse
It's a CM14.0 ROM of 01/11, after I installed the zip(without wipe dalvik nor cache), I choose reboot system directly. But It just boot into recovery. And just loop boot into recovery whatever I chose. Recovery version: TWRP 3.0.2.0
And now, he build the cm14.1 ROM, but I'm worry if the issue happen again.
Just to clarify some things:
- It's a new version of Android, please make wipes before upgrading. By the way, a wipe of system + dalvik + caches should work fine if you comes from CM14! (tested on mine). Else, make a clean wipe including /data (don't touch to internal storage).
- Make sure you install 7.1 Pico gapps
- I actually use TWRP 2.8.7.0, but maybe latest twrp should work as well
If you have a boot loop:
- You probably missed a wipe. Get into recovery, wipe system, data, cache, dalvik, flash the rom(+gapps) then reboot.
If you can't go to system and it auto boot to recovery:
- you probably did bad flashing. You'll need to flash stock image occam (it will wipe all), then on,ce it's booted, flash this CM14.1 (twrp + wipes + rom + gapps).
dcshallot said:
Before I try this ROM, I need to ask.
In the ROM cm14, I installed 24/10 cleanly, used a couple days then updated to 01/11 dirty but came an issue reboot into recovery( I couldn't reboot into system any more). So I restored to original stock image then flashed 01/11 cleanly and now work fine.
When the issue(mentioned upon) happened, I wiped all things but didn't work. And I tried an older version(24/10) but didn't work neither.
So, the question is, what is the correct way to update your ROM? Do I have to wipe dalvik and cache?
Click to expand...
Click to collapse
If I remember from what you stated from an older post, you tried updating via cmupdater. Don't do that actually (or in other words, I don't like update using "software" or "auto tools"). Just flash like the older way:
This is how you should update when a new version is available:
- download the ROM zip
- Download gapps (if not yet downladed before) related to the ROM Android's version
- Boot into TWRP recovery
- Wipe only System, Dalvik and cache
- Flash ROM zip, then Gapps
- Reboot
Proceed like this for every update and you'll encounter no issue.
There are exceptions where a "very clean" install may be needed (I mean wipes that includes "Data"), but when it's the case I mention it in the thread's download section
I have TWRP 3.0.2-0.
I went into "advanced wipe" and wiped everything (even internal and data).
I flashed cm-14.1-20161102-StephanMc-mako.zip and open_gapps-arm-7.1-pico-20161102.zip, wiped dalvik/cache again just in case.
My phone was recoverable by flashing cm-14.0-20161101-StephanMc-mako.zip and open_gapps-arm-7.0-nano-20161102.zip.
I can try again.
stephanmc said:
If I remember from what you stated from an older post, you tried updating via cmupdater. Don't do that actually (or in other words, I don't like update using "software" or "auto tools"). Just flash like the older way:
This is how you should update when a new version is available:
- download the ROM zip
- Download gapps (if not yet downladed before) related to the ROM Android's version
- Boot into TWRP recovery
- Wipe only System, Dalvik and cache
- Flash ROM zip, then Gapps
- Reboot
Proceed like this for every update and you'll encounter no issue.
There are exceptions where a "very clean" install may be needed (I mean wipes that includes "Data"), but when it's the case I mention it in the thread's download section
Click to expand...
Click to collapse
Thanks a lot! And now, cm 14.1 work just fine. As you said, camera didn't work.
Some apps have compatible issue with cm14.1, but it's not a big deal.
brunoqc said:
I have TWRP 3.0.2-0.
I went into "advanced wipe" and wiped everything (even internal and data).
I flashed cm-14.1-20161102-StephanMc-mako.zip and open_gapps-arm-7.1-pico-20161102.zip, wiped dalvik/cache again just in case.
My phone was recoverable by flashing cm-14.0-20161101-StephanMc-mako.zip and open_gapps-arm-7.0-nano-20161102.zip.
I can try again.
Click to expand...
Click to collapse
Hmm ok maybe the network upload corrupted the file. I check it out and let you know
dcshallot said:
Thanks a lot! And now, cm 14.1 work just fine. As you said, camera didn't work.
Some apps have compatible issue with cm14.1, but it's not a big deal.
Click to expand...
Click to collapse
Glad to read that!
Post duplicated. But I can say thank you again!
It works now but I'm not sure why.
I re-downloaded everything and the md5 file for the gapps. I created a md5 file for your zip. I wiped System, Dalvik and cache (since I was back on cm-14.0-20161101) and I flashed both file. both md5 matched. I rebooted and it works.
Thanks.
brunoqc said:
I have TWRP 3.0.2-0.
I went into "advanced wipe" and wiped everything (even internal and data).
I flashed cm-14.1-20161102-StephanMc-mako.zip and open_gapps-arm-7.1-pico-20161102.zip, wiped dalvik/cache again just in case.
My phone was recoverable by flashing cm-14.0-20161101-StephanMc-mako.zip and open_gapps-arm-7.0-nano-20161102.zip.
I can try again.
Click to expand...
Click to collapse
What I just did (from cm14.0 1101 build: ) :
- wiped Dalvik cache, System, Cache
- Flashed ROM zip cm14.1 11-02
- flashed pico gapps (the one I've already downloaded yesterday, open_gapps-arm-7.1-pico-20161101.zip)
- reboot
It's boots fine. Can you retry and let me know ?
stephanmc said:
What I just did (from cm14.0 1101 build: ) :
- wiped Dalvik cache, System, Cache
- Flashed ROM zip cm14.1 11-02
- flashed pico gapps (the one I've already downloaded yesterday, open_gapps-arm-7.1-pico-20161101.zip)
- reboot
It's boots fine. Can you retry and let me know ?
Click to expand...
Click to collapse
brunoqc said:
It works now but I'm not sure why.
I re-downloaded everything and the md5 file for the gapps. I created a md5 file for your zip. I wiped System, Dalvik and cache (since I was back on cm-14.0-20161101) and I flashed both file. both md5 matched. I rebooted and it works.
Thanks.
Click to expand...
Click to collapse
Oops, replied a bit later ! Glad to know everything works for you now.
When I use 'file manager' open sdcard/music, it crash.
(I didn't wipe /system, cause by this?) Version: 02/11
I installed the new rom cm-14.1-20161102-StephanMc-mako.zip, reboot the phone stop it boots.
I did so:
- Wiped Dalvik cache system, Cache
- Flashed ROM zip cm14.1 11-02
- Wiped Dalvik cache system, Cache
- Reboot.
Phone stop boots.
I went back to version cm-14.0-20161101-StephanMc-mako.zip and this problem does not exist.
Hm, I'm an idiot. Just deleted everything because some apps (especially the camera) weren't working. Now I see it's even in the release notes.
But yesterday the cam worked, that's why I didn't check...
---------- Post added at 09:36 PM ---------- Previous post was at 09:05 PM ----------
Hm, I need to go back to an older version as well, when trying to reinstall this 7.1, the phone just boots forever.
Hi! Will you merge his branch into yours in the future? His seems to be the official version.
https://github.com/ivanich/android_device_lge_mako?files=1
IMPORTANT ADVISE! I AM NOT THE MAINTAINEER OF THE EPIC ROM OF MI6 YET, NOW IS JOSEMA93, I AM RETIRED BY NOW (BUT WE'LL SEE YOU AGAIN IN AOSP SOON)
Jamflux, Pocarropa, and MrRaines (MrTomatico on en.miui), creators of Épic ROM, we are glad to present Épic ROM for Xiaomi Mi MIX, who was born thanks to the hard work of these guys. Epic ROM is a Custom ROM based on MIUI, but with some mods and improvements that you can see below on features chapter.
The focus of this ROM is improve MIUI official stock on many devices making many mods and improve Xiaomi sellers to get a bigger MIUI-ers family!
**IMPORTANT ADVISE : Install at your own risk on your device. We are not responsible of any damage on your device. Read carefully instructions before install.
Requirements:
-Xiaomi Mi 6
-Unlocked Bootloader (official unlock to prevent issues)
-Custom Recovery (Cofface TWRP Recovery is highly recommended)
-Make previously a full Backup by TWRP Recovery (System, Data, Cache, and EFS).
-Read all thread before proceed
-Love for technology and most important: Love for Xiaomi!
Newest Features
Changelog:
* 9.0.5.0 v1.5 base with all changes (visit en.miui.com/forum to check all)
* Assisted GPS in Settings
* New Camera Interface
* Camera2Api and HAL3 Enabled by default
* New Miui Mail enabled
* Face Unlock
* Blur lock screen effect
* New Epic Themes
* New TWRP 3.2.0.0 base with Epic Theme by MrRaines
* All features from Epic ROM 7.11.30
* Improved Themes Manager and Welcome Message
* New PowerMenu Design
* Notification shade improved (not aosp by now but is better than older)
* Soon I'll add smart assistant and more...
The rest of features are in quote below:
HTML:
* Fixed Notifications and FACE UNLOCK
* BugFixes in the system adn gallery
* Fixed widgets issues
* New boot mechanism
* New settings for Smart Assistant (next week I will add many other features like enable and disable it, etc)
* Fixed many bugs with languages from GitHub like Italian or German
* Fixed a little issue when displaying WiFi in some networks
* Fixed notifications mechanism
* Introduced SMART ASSISTANT Global
* Added few new languages
* Many bug fixes in system
* UI Simplified
* New Epic Music Widgets
* DELETED antispam by default by people asking (now you can flash it by addons in OTA)
* New Audio Modes for Mi 6 and MiMIX
* New GRID for Launcher and Folders (Thanks to Tomhenson and MrRaines)
* New GRID selector in Settings/home and recents (Thanks to Tomhenson and MrRaines)
* New Ringtones and Notifications sounds
* New mods for Icons, Grid, Reflected Icons, and more in OTA and ADDONS
* All changelog from official build in en.miui.com
* Safety net and android pay only works without ROOT (Payments will work as HCE protocol)
* New Network manager and bugfixes in system
-SuperSU in ota and mods, if you want it.
-Improved System Speed
-MultiWindow
-Fixed Wifi from 3.0
-Updated all languages from GitHub
-Deleted Adaway (anti spam now is native in MIUI system by MrRaines)
-Deleted root
-DocumentsUI enabled ALWAYS by default
-Fixed SafetyNet and NFC Payments!
Xiaomi.eu base (thanks to this, I don't have to deodex all rom, that takes me about 1 hour in my old computer... Blur-lockscreen effect is added also in epic rom (services.jar) and all languages from eu base; THANKS to Ingbrzy for his amazing work!)
DOZE enabled!!
New apps added to OTA and MODs (in settings)
Improved icons on status bar mods and improved the rest of the mods
LockScreen Icon in Status Bar MOD now is White
Optimizations on TWRP installation and GAPPS
Better Intelligent CPU management and RAM
DPI Changer in Ota and MODs (settings app)
Multilanguage
Zipalign all ROM
New Nice Icons in settings and launcher
New (a lot of) mods in OTA & MODS on settings
Gapps Pico pre-installed (Google Play Store and Google Services... you can choose what Google app's are you going to install later :P)
Épic OTA Service Added on Settings
Epic Mods on OTA app
Music App Improved
Icons on Settings re-orderer (now you'll have Dolby and SuperSU, and dolby icon from launcher has been removed, you can hide supersu icon from supersu app and only have supersu icon in settings)
Init.d support
Busybox pre-installed
Kernel tweaks (very little changes on boot.img)
Build.prop improved (again)
Miui System improved to get better RAM management
Services and frameworks improvements (more battery and system performance)
MIUI Launcher improvements
Camera MODs (better image quality)
Adway integrated on system (you can see also on Settings)
All Chinese app's and Google app's (bloatware) removed
Advanced Reboot Menú (PowerMenu improved)
DolbyAtmos Updated to latest version
Some Nice Wallpapers added
More Languajes and Spanish Updated (thanks to [user=5863451]@JamFlux[/user])
Assistant Touch Updated Like Epic Team Style :P
Animations on SystemUI (lockscreen), thanks to xiaomi.eu but we now add some optimizations to this
Epic Bootanimation improved
Optimized installation time from TWRP.
Fixed issues in NFC pay (you should unroot your device from SuperSU app)
Added XIAOMI installer multilang (with antivirus :P )
Better Battery and Performance/RAM management thanks also to many patches that we built for JBart
Languages Supported:
All European Languages from Xiaomi.eu (Thanks Ingbrzy, for bring to all MIUI users xiaomi eu roms (availables in www.xiaomi.eu) )
How to install first time
* First of all, make a complete backup of all your photos and internal data in the computer, since the first installation requires to eliminate ALL the sdcard content, given the encryption of Android Nougat and later; the one that warns you is not a traitor, you are going to lose all the data (just as it happens if you install other ROMS). This is due to (in turn) that if we have not formatted the sdcard, it will not boot for security protection data of the cited encryption,
* With TWRP Recovery (read tutorials on how to install it) we will make another backup, but this time System, Data, Cache, Boot, and especially the EFS (important).
* Download the ZIP flasheable and pass it to the internal memory of the phone (no matter if we have already formatted it or not).
* Restart on TWRP recovery
* Make Wipes: System, Data, Dalvik, Cache.
* Install from Recovery the EpicROM ZIP flasheable and wait for it to appear okay (If you get error 7 the TWRP in the step of "formating system / extracting system", restart in recovery immediately, and reinstall it, this is due that in Nougat you must re-generate the system partition for encryption topics, so it will install you, it should work like the rest of us )
* We reboot in fastboot mode once the rom has been installed correctly. To do this, we can do it from TWRP in REBOOT / Fastboot or by holding down the power button and the volume down button until FASTBOOT and Mitu appear by soldering an Android robot. In this step, we connect the mobile to the computer, and in the same folder that can be downloaded from en.miui.com/unlock (to unblock the bootloader) click inside that folder in a blank space in the right mouse click while holding the SHIFT key on the keyboard; a window will appear and the "open command window" option should appear. We tapped on that window. When it opens, if you open powershell (blue screen) from windows 10, type cmd and press enter. If you open the classic cmd of all life (BLACK SCREEN) we are already where we want.
* Type in the cmd (be powershell or cmd) fastboot format userdata and press enter. There will be formatted all our mobile, and restarting it will work everything.
* Restart normally and configure. Remember that the first start takes a little longer, from there, it will always light fast. In the following versions, it will NOT BE MISSING to do all this, just install without wipes and to run. I already adapt it so that I clean what I have to clean with each update EXCEPT that I expressly say something else in that UPDATE.
* Enjoy (and re-pass all data previously backed up to the internal memory).
How to install UPDATE from Epic ROM 7.X.XX
Download Epic OTA with OTA app from Settings (No MIUI Updater, use EPIC OTA!)
You can also download update manually from en.miui forum or htcmania spanish forum
Install update from Epic OTA or from TWRP Recovery manually
You don't need to wipe anything if we don't say it on update! If you have to do some special, we will let you know
Reboot
Enjoy
Download Center
9.0.5.0_1.5 for Xiaomi MI 6 (Sagit) Nougat 7.1.1
Download: https://www.androidfilehost.com/?fid=745849072291693954
Note: Please remember: Installation could take about 5 minutes in the TWRP Recovery, BE PATIENT and don't touch anything!
Current Status: Tested 100%; ROM Stable and TWRP by Cofface works in all MIUI roms!!
Note: If you want to use Google Assistant please set as default assistant Google Aplication in settings/installed aplications/default/assistant and enable Google in home button in settings/aditional settings/buttons.
Obviously, you need to install Google App .
If you like my work please consider to make me a little donation in this paypal link
Thanks to:
Xiaomi (and Xiaomi official developers for bring to us this amazing SO)
Google
Xiaomi Eu Team
MultiROM Team
Epic Team founder Members @JamFlux, @pocaropa, @MrRaines (MrTomatico on en.miui))
All MIUI DEVICE TEAM
All Admins/Mods/SMods from En.MIUI for all support
HTCManía (Spanish Forum)
Official Website: www.epicrom.pro
Enjoy and Remember: Keep loving Xiaomi!
Nice work, I'll definitely look into this once my mi 6 arrives
get for natrium, please
Flashed and seems to work very good.
Thank you!
Can you add features like blurred statusbar option? Like the one on miui7. Since last build miuipro 7.5.25 has implemented this. Thanks for the rom anyway
Got error 7 many times. I cant fix It.
Downloaded 3 times and same
Not booting at all. 30 min and still bootanimation. I have followed the instructions to the letter and nothing changes. Tried it thrice.
A video tutorial would be nice, I might be doing something wrong. Also I'm on official TWRP, IDK if that makes a difference.
riirezende said:
Got error 7 many times. I cant fix It.
Downloaded 3 times and same
Click to expand...
Click to collapse
When you get error 7 try to restart to recovery and flash again. This worked for me with cofface twrp.
---------- Post added at 12:36 AM ---------- Previous post was at 12:36 AM ----------
Asce1062 said:
Not booting at all. 30 min and still bootanimation. I have followed the instructions to the letter and nothing changes. Tried it thrice.
A video tutorial would be nice, I might be doing something wrong. Also I'm on official TWRP, IDK if that makes a difference.
Click to expand...
Click to collapse
No problem with cofface twrp
battery is really awful magisk not working always having FC
IronJacob said:
When you get error 7 try to restart to recovery and flash again. This worked for me with cofface twrp.
---------- Post added at 12:36 AM ---------- Previous post was at 12:36 AM ----------
No problem with cofface twrp
Click to expand...
Click to collapse
Im using cofface also.
Ill try again thx
Someone tried with Official TWRP? I want Install Official TWRP then This
In 2 days I'll release new update by OTA with bug fixes and new amazing features.
Uploading 7.6.10 with many fixes (even battery drain fix).
MrRaines said:
Uploading 7.6.10 with many fixes (even battery drain fix).
Click to expand...
Click to collapse
is it still uploading? Didn't see the links for old file and 7.6.10 either :/
IronJacob said:
No problem with cofface twrp
Click to expand...
Click to collapse
Actually the recovery does not matter. I used official TWRP recovery and got it to work.
It's juts the flashing guide that misguided (lol) me.
Coming from global/official/beta or any other ROMS you HAVE TO WIPE USER DATA.
Also going back to global/official/beta ROMS you HAVE TO WIPE USER DATA.
Otherwise the guide is okay, if this could be pinned or added together with the other *NOTES it would be superb.
Asce1062 said:
Actually the recovery does not matter. I used official TWRP recovery and got it to work.
It's juts the flashing guide that misguided (lol) me.
Coming from global/official/beta or any other ROMS you HAVE TO WIPE USER DATA.
Also going back to global/official/beta ROMS you HAVE TO WIPE USER DATA.
If otherwise the guide is okay, if this could be pinned or added together with the other *NOTES it would be superb.
Click to expand...
Click to collapse
Then everythink is lost from phone ? I need to download with mtp this rom to internal to flash it, or otg works?
fuxmen said:
Then everythink is lost from phone ? I need to download with mtp this rom to internal to flash it, or otg works?
Click to expand...
Click to collapse
Yes, everything is lost from phone.
Copy internal storage, or important data (in internal) to computer.
I have not tested otg since I don't have a type-c otg nor do I have a converter to type-c.
Sideloading works. (I use this a lot)
Also you could just enable mtp and copy .zip to storage.
Not booting stays at EpicROM logo :/
Trying With officeial TWRP, With Cofface, formated all partitions :/ No error 7 while falshing all process went well.
Hmmm What am I doing wronge here :/
edit
FORMAT DATA in TWRP helped
Why the landscape lock icon persist?
yoghibawono said:
Why the landscape lock icon persist?
Click to expand...
Click to collapse
Because you've installed the full mod of status bar from ota and mods by MrRaines . Install the "come back to normal/stock status bar mod" to revert it hahaha.
{
"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"
}
Code:
/*
* Your warranty is now void.
*
* We're 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 us for messing up your device, we will laugh at you.
*
*/
Red Wolf Recovery is custom recovery based on TWRP source code, however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.
Based on TWRP version: 3.2.1
For devices: Sagit, Mido, Land, Kenzo & Kate
Authors build: dadi11
Kernel: https://github.com/RedWolfRecovery/rw_device
Developers: ATG Droid, dadi11 & Devil7DK
Thanks: z31s1g (for the base of his theme), Ray Li (For his useful advice in the beginnings), osm0sis (for his image scripts), dadi11 (for his awesome kernel & mido builds) etc.
Features:
Code:
[B]Translated to EN, PL, zh_cn, & CZ [/B]
- Password protection
- Flashlight
- MIUI Incremental OTA Support
- Built-in latest Magisk, SuperSU & AromaFM
- Support two screenshot GUI actions - Power+VolDown to save screenshot in to the internal storage &
Power+VolUp to save screenshot in to the external storage (Will be automatically saved in to the internal in case
that external storage doesn't exist).
- Support automatic reboot after the restore process
- Recovery can automatically modify some props in the ROM directly during the installation
- Some built-in scripts from community
- Tap to wake support
- Advanced deactivation of the stock recovery
- Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- Support "set on boot" settings.
*[B] Changes for security reasons [/B]*
- ADB isn't starting automatically at the start of the recovery. You have to activate it in recovery
- MTP isn't starting until user enter correct password
- Deactivated support of the custom themes
Some differences to the official version:
Code:
[B][COLOR="red"]- get out of here if you are pirating apps. this recovery is not for you[/COLOR][/B]
- always up-to-date with the latest TWRP changes
- compiled on omnirom-7.1 source
- fixed backup/restore of Firmware
- more languages
- other improvements from Features and Changelog lists
Changelog:
Code:
[B][U]RedWolf-V3.2_027[/U][/B]
- If screen is turned off then automatically detect AROMA Installer package and unblank screen before starting the update binary which is going to call AROMA GUI, so we won't be stuck at the black screen since AROMA engine require screen to be turned on.
- Added ability to change OTA Survival driver properties from the recovery GUI, allowing recovery to support "out of the box" almost all incremental OTA updates from different OEMs/custom ROMs out there (as long as they have correctly formatted metadata).
- Notify user about the current activity of the deactivation process - that's handled under the console
- Improved dumwolf driver
- Removed the vibration feedback from all GUI elements
- Automatically resize bootable partitions during nandroid backups
- Changed theme to black/white/red style based on @TBO material theme
- Data files aren't anymore saved on the storage partitions, which means that we're now able to survive even encrypted device.
- Some bug fixes and improvements...
[B][U]RedWolf-V3.2_026[/U][/B]
- This is just a quick bug fix release for MIUI users. So is highly recommend to update to this build if you are using MIUI.
[B][U]RedWolf-V3.2_025[/U][/B]
- Fixed crash of the recovery while running OTA_RES.. (So MIUI OTA is now working again)
- General bug fixes and improvements
- Fixed bug with MIUI Updater app showing error that installation failed after installation of full ROM
- Deactivation process is now called only when it's really needed
- Updated kernel
[B][U]RedWolf-V3.2_024[/U][/B]
- Fixed GUI color glitch while starting Aroma Installer update-binary
- Optimized pigz runtime process
- Updated recovery base to the AOSP 8.1.0 & TWRP 3.2.1
- Highly improved signature verification for Incremental packages so now we can be really sure if the package is compatible with the ROM.
- Introduced a file based backup/restore engine. Expect it to be improved with the next builds...
- Improved security related to the password protection
- Fixed loading of the AromaFM config file
- System survival process for Incremental packages is now set by default
- Code optimizations
- Removed the dumwolf process
- Added signature check for incremental OTA survival so we won't be unnecessarily creating a new one if it's signed under the same access key
- Magisk updated to the version 15.1
- Added Indonesian language
- Fixed issues with Chinese characters...
- Governor which is changed by the action in the recovery GUI is now automatically set for all cores instead of only four.
[B][U]RedWolf-V3.2_023[/U][/B]
- Updated recovery base to the TWRP version 3.2.0
- Fixed issue with recovery sometimes showing "NO-OS" page even when OS is installed
- Merged: Fstab V2, minui updates, Keymaster 3.0 support, ADB updates, fixes related to the compiling errors...
- Added patch against the pirating applications
[B][U]RedWolf-V3.1_022[/U][/B]
- Small improvements in the installation process
- Recovery will now automatically warn the user in case that user selected to install the zip which contain a bootloader
- You can now wipe installed substratum overlays directly from the "advanced wipe" section
[B][U]RedWolf-V3.1_021[/U][/B]
- Automatically return install error if there is any issue with Incremental OTA Survival
- Added option to also backup system partition for Incremental OTA Survival (It's not always needed, but just in case it's better to backup it.)
- Added support for the compatibility verification of the Incremental Package
- Rebuilded & improved installation process
- Fixed starting process not being disabled correctly in case that we are running ORS
- Translation update
- Added support for devices with 2GB RAM or less... (Check installation process of this build for more info)
- Added checkbox for activation/deactivation of the boot check (Disable only if you really need to).
- Fixed booting problems on some custom ROMs which don't have gzip compressed ramdisk
- Removed bookmark feature
- Added ability to unzip files using the stock filemanager.
- Added search selection for the stock filemanager.
- Fixed 'No OS' on system image restore after wipe
- Merged some latest commits from TWRP gerrit
[B][U]RedWolf-V3.1_020[/U][/B]
- Fixed flashing of the images in the previous 018 build
- Added back support for unpacking of the LZ4 compressed ramdisk
- Fixed bookmark feature
[B][U]RedWolf-V3.1_019[/U][/B]
- Disable TWRP installation directly during the first boot
- Default time zone was set to CEST
- Use military time as default time.
- Support of the custom themes was completely removed from the installation process
- Few fixes & improvements in the strings.
- Default value of the RedWolf specific vibrations was slightly increased
- Improved saving/loading of the AromaFM config file.
- User can now select if recovery should disable stock recovery when system is mounted as read-only.
- Default color of the recovery was set to red.
- Fixed automatic reboot if the installation process was unsuccessful
- Center time in the statusbar as default
- Show CPU temp in statusbar as default
- Added "Red Wolf No-OS search engine". Enable this if you are sometimes getting No-OS installed error even when OS is installed.
- Added back support for extra languages
- Added support for Talian language
- Updated Chinese (simplified) translation of the AromaFM by LiuNian and Pzqqt
- Fixed displaying of the extra languages
- Improved mounting of the partitions during the applying of set on boot values
- Fixes with "stuck at unmounting"
- Highly improved speed of the recovery while setting up a new password, changing accent color or setting a new splash screen
- Magisk updated to the V14.3
- Recovery now won't allow the user to enter special characters while entering the password (Causing issues...)
- Few improvements with the Android Oreo installation
- Updated kernel
- Added ability to select if recovery should automatically disable forced encryption in the ROM
- Recovery will now automatically rename scripts in the system if the "Aggresive stock recovery deactivation" is enabled
- Added ability to select if recovery should automatically enable/disable USB Debugging in the ROM
- Removed some useless files to save the space
- Added support for saving the set on boot values also during the automatic reboot
- Redesigned flashlight icon
- Recovery now won't allow the user to enter the space in to the backup name
- Improved support of the last status checking of the MIUI ROM
- Recovery now won't show any button after the cancelled reboot action untill the sleep action won't be running anymore
- You can now select if recovery should also automaticaly reboot after the successfuly finished restore process
- Recovery will now hide the automatic backup feature if the system partition is mounted as read-only
- Updated recovery base to the AOSP 8.0.0
- Updated image drivers
- Added ability to select if recovery should automatically enable/disable "ro.adb.secure" property in the ROM
- Recovery will now automatically disable starting of the flash_recovery service if the "Aggresive stock recovery deactivation" is enabled (this process is also compatible with the backup of the init.rc by Magisk or SuperSU).
- Added new section called "Special Actions" in to the advanced menu
- Updated & optimized flashlight drivers
- Added ability to select if recovery should automatically enable/disable "ro.secure" property in the ROM
- Added ability to select if recovery should automatically enable/disable "ro.allow.mock.location" property in the ROM
- Highly improved support of the Incremental Package installation, detection etc.
- Updated Chinese (simplified) translation of the recovery by LiuNian and Pzqqt
- Added support for the complete deactivation of the secure boot in the MIUI based ROMs
- ADB is now automatically starting as root
- Added support for the RedWolf update package
- Default theme of the AromaFM was changed to holo black with the sense icons and automount turned on
- SuperSU Updated to the 2.82 SR5
- Updated ramdisk cleaner & added support for more kernels (thanks to @MOVZX's kernel installation scripts...)
- Small fixes with the /WOLF folder in the PartitionManager
- Highly improved speed of the reboot
- 'Deactivation process' is now automatically called during the installation instead of the reboot
- Imroved deactivation of the leds after the installation / backup / restore process.
- Fixed bug with recovery showing on the governor page that the active governor is "Interactive" even when user selected performance/powersave mode.
- Removed some GUI messages while we are installing built-in zips.
- And many other things which i don't remember anymore...
[B][U]RedWolf-V3.1_018[/U][/B]
- Fixed bugs with MIUI OTA Support to make sure that it will work even with newest beta builds of the MIUI
- Updated Polish translation by Daviteusz
- Fixed bugs in the Polish strings & edited the scale of the Russian strings
- Recovery will be now more aggressive if the process of the stock recovery doesn't want to be disconnected (Sometimes happen on some MIUI ROMs).
- Added detection of the installed ROM
[B][U]RedWolf-V3.1_017[/U][/B]
- Magisk updated to the V13.6
- SuperSU updated to the 2.82 SR3
- Added ability to automatically flash SuperSU config before the SuperSU - https://forum.xda-developers.com/apps/supersu/2017-08-13-supersu-config-t3655754
- Deactivated hw keys
- Added some missing back buttons
- Attempted to fix encryption
- Attempted to fix MIUI OTA installation - needs testing
- Removed extra languages (were not displayed properly)
- Small update which fixed deactivation of the dm-verity & forced encryption. Now you really don't have to flash the lazyflasher everytime when you are installing the MIUI ROM.
[B][U]RedWolf-V3.1_016[/U][/B]
- Fixed feature "Backup wifi, bluetooth & hosts" not to work if the user wiped the data partition using the "factory reset".
- TWRP source code was updated to the Aug 15, 2017
- Fixed recovery remembering the wipe list after setting a new gui page.
- Improvements with the mounting of the partitions during the boot
- Fixed led drivers on mido
- Fixed ability to set custom backup folder name & ADB ID
[B][U]RedWolf-V3.1_015[/U][/B]
- Updated with the latest TWRP changes
- Added flashlight switch on mido
[B][U]RedWolf-V3.1_014[/U][/B]
- Fixed recovery not deactivating the dm-verity, forced encryption, & stock recovery if the OS was detected as not installed. This issue was often happening on some MIUI ROMs.
- Improvements with the OTA update system of the MIUI.
- Fixed wrong reboot for some users.
- Added support for automatic deactivation of the dm-verity, forced encryption & stock recovery after finishing the OpenRecoveryScript process.
- Fixed recovery not deactivating the dm-verity & forced encryption during the automatic reboot after the finished installation.
- Better explain the current situation if the OS was detected as not installed.
- osm0sis's scripts "unpackbootimg" & "mkbootimg" can now be easily called from the script or terminal
- Improved the speed of the reboot
- Updated the community script "Fingerprint scanner fix" by Magua. It's now working again!
- Added NTFS & exFAT support
- Added more languages and updated Polish RedWolf translation by @Daviteusz
- Added FGO patch - https://goo.gl/GBkhMN
[B][U]RedWolf-V3.1_013[/U][/B]
- Slightly improved deactivation of the stock recovery during reboot after the zip installation
- Added ability to flash boot logo in the recovery
- Fixed firmware restoring issues
[B][U]RedWolf-V3.1_012[/U][/B]
- added F2FS support for mido
- added Night Mode (kcal) support for mido
[B][U]RedWolf-V3.1_011[/U][/B]
- Updated Polish translation by @Daviteusz
- Added few missing strings from the latest TWRP source
[Red Wolf] Install TWRP and root your device without breaking incremental OTA's!
Downloads:
Latest build for Xiaomi Mi 6 (sagit)
RedWolf-027-sagit.img
Screenshots:
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery. But your device can be still reinstalled using fastboot or Miflash.
XDA:DevDB Information
Red Wolf Recovery Project for Xiaomi Mi 6, Tool/Utility for the Xiaomi Mi 6
Contributors
dadi11, ATG Droid, Devil7DK
Source Code: https://github.com/RedWolfRecovery
Version Information
Status: Testing
Created 2018-04-07
Last Updated 2018-04-07
Reserved
bugs: flashlight doesn't work, yet
https://t.me/joinchat/FZlpFECo9qt3MT5oRn-Bcg
Thanks Great Work
if you face issues with mounting Modem, redownload and flash the v27 image again
i was using your TWRP since kenzo, and mido. nice to see you here on sagit. does it support decryption on oreo? backup and restore works fine?
I flash the newest version, V3.2.1-027. After I enter system, I find the recovery is overwrite by system.
Steps:
1. flash recovery, Red Wolf V3.2.1-027.
2. Enter Recovery
3. Reboot to system
4. Reboot to recovery, the recovery is restored to original.
OS version: MIUI V9.2.3.0.OCAMIEK
P.S. I have renamed the file, /system/bin/install-recovery.sh, to /system/bin/install-recovery.sh.bak.
Does the under function work? or How to let it work? Thx.
"Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM"
@dadi11
sorry, but it seems it doesn't work on MIUI 8.4.5 Global Dev Oreo
same problem as previous, can't read the /sdcard /data.
any further support?
zilan said:
i was using your TWRP since kenzo, and mido. nice to see you here on sagit. does it support decryption on oreo? backup and restore works fine?
Click to expand...
Click to collapse
yes it works fine
planetera said:
Does it support Oreo decryption and vendor support?
Can we flash treble images with it?
Click to expand...
Click to collapse
no you can't
dewa5227 said:
@dadi11
sorry, but it seems it doesn't work on MIUI 8.4.5 Global Dev Oreo
same problem as previous, can't read the /sdcard /data.
any further support?
Click to expand...
Click to collapse
please be more descriptive next time.
sagit doesn't have /sdcard. if /data can't be mounted you have to format (not wipe) /data
finally,it get stable,what a good thing
It does not decrypt the files.
ibrahimyuksel said:
It does not decrypt the files.
Click to expand...
Click to collapse
why would it? that's what the encryption is for. format /data to disable encryption and have a full access..
dadi11 said:
please be more descriptive next time.
sagit doesn't have /sdcard. if /data can't be mounted you have to format (not wipe) /data
Click to expand...
Click to collapse
i'm sorry, it seems that it must be formatted to be able to use it.
but another problem is, the recovery doesn't seems to stick after reboot to system. it goes back to the original stock recovery.
i didn't change the option from the default Aggresively replacing stock recovery, it still being checked. yet it goes back to stock recovery after reboot to system.
slitaz said:
finally,it get stable,what a good thing
Click to expand...
Click to collapse
flashlight is still not running,and i can't change some settings
dewa5227 said:
i'm sorry, it seems that it must be formatted to be able to use it.
but another problem is, the recovery doesn't seems to stick after reboot to system. it goes back to the original stock recovery.
i didn't change the option from the default Aggresively replacing stock recovery, it still being checked. yet it goes back to stock recovery after reboot to system.
Click to expand...
Click to collapse
same problem always goes back to stock recovery and when I try flash it with no-verity-opt-encrypt-5.1 my phone softbrick at miui logo after reboot
dewa5227 said:
i'm sorry, it seems that it must be formatted to be able to use it.
but another problem is, the recovery doesn't seems to stick after reboot to system. it goes back to the original stock recovery.
i didn't change the option from the default Aggresively replacing stock recovery, it still being checked. yet it goes back to stock recovery after reboot to system.
Click to expand...
Click to collapse
I solved it, first u need flash twrp then flash magisk or supersu > reboot system > instal apk like root explorer/mixplorer > open root files > find system/bin/install-recovery.sh then rename > system/bin/install-recovery.sh.bak (i used mixplorer) turn off ur phone > press volume up + power button > say goodbye for mi recovery
I am on latest developer global for Mi6. Do I have to wipe everything (my files, settings and apps?) to install this recovery? Can someone give me link to proper installation procedure? I don't want to lose my stuff on phone.
spiderpl said:
I am on latest developer global for Mi6. Do I have to wipe everything (my files, settings and apps?) to install this recovery? Can someone give me link to proper installation procedure? I don't want to lose my stuff on phone.
Click to expand...
Click to collapse
it's not a rom. search for the guide and you will find it for sure
planetera said:
Can you please update this twrp to 3.2.1.1 base? Because it does not support Oreo encryption :/
Click to expand...
Click to collapse
it does. and if it's not then wait for next build
This is what I did:
1. Booted to fastboot
2. fastboot flash recovery recovery.img
3. fastboot boot recovery.img
The red wolf recovery logo appeared and nothing else happened. I had to turn off the phone and when I went back into recovery it was default xiaomi recovery
spiderpl said:
This is what I did:
1. Booted to fastboot
2. fastboot flash recovery recovery.img
3. fastboot boot recovery.img
The red wolf recovery logo appeared and nothing else happened. I had to turn off the phone and when I went back into recovery it was default xiaomi recovery
Click to expand...
Click to collapse
do not use fastboot boot command