Related
Team Win Recovery Project , or twrp for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
BUGS:
-OffMode charge not working
-Repartition zips are not working with TWRP
CHANGELOG:
v2.7.0.0 > v2.7.1.0
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button.
-Various bugfixes to backup and restore
-Improvements to USB storage handling
-Various other bugfixes and tweaks
v2.6.3.4 > v2.7.0.0
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
v2.6.3.0 > v2.6.3.4
-Add SELinux support for install kitkat correctly
-Other updates by TeamWin
v2.6.0.0 > v2.6.3.0
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
v2.5.0.0 > v2.6.0.0
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
v2.4.4.0 > v2.5.0.0
Special Note: If you are running a custom theme, the changes in 2.5.0.0 will likely not be compatible with your theme.
-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-Fixed a problem with md5 verification of backups
-Added a search function to libtar (thanks to kokotas)
-Improve handling of XML errors (fix permissions)
-Fixed handling of subpartitions
-Improvements to recovery.fstab flags
-Fixed a problem with decryption not being able to locate the decryption key in some situations
v2.4.3.1 > v2.4.4.0
-Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
-More fixes for the file selector
-Switched from using busybox md5sum to a direct C function call
-Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
-Update exFAT to latest commits
-Added a build flag to disable using the ioctl for screen blanking
-Other fixes
v2.4.3.0 > v2.4.3.1
- Synaptic Touch Screen support added
- In this version,offmode charge not working
v2.3.3.1 > v2.4.3.0
-UI Lag is fixed
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
-Fixed a problem with mkdosfs that formatted sdcards to 2GB
-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
-Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
-Add a brightness setting (requires device specific setup and only some devices have been added)
-Add a root checker and offer to install SuperSU if the device isn't already rooted
-Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
-Check and offer to fix root permissions if broken
-Add an option for a 24 hour clock display instead of AM/PM (aka military time)
-Move stock recovery reflash check to occur during the reboot cycle
-Add support for some MTK6xxx devices
-Change libtar to vfork to help prevent memory problems
-Add a "clicked" effect to most buttons, file selector, and listbox
-Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
-Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
-Added a scroll bar to file selectors and listboxes courtesy of Tassadar
-Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
-Added a screen dim effect 2 seconds before screen off on some devices
-Finally fixed file selector crash (one of the joys of working with multi-threaded software)
-Fixed loading of screen timeout setting during startup
-Improvements and bugfixes to screen timeout code
-Fixed persistence of the 24 hour / military time setting
v2.3.3.0 > v2.3.3.1
- Color bug of UI is fixed. It's blue now
- ADB fixed
- Offmode charge is fully working now (like other recoveries)
v2.3.2.3 > v2.3.3.0
- USB Mass Storage via USB fixed. You can use mass storage with internal and external sdcard
- Random reboot problems are fixed (Thanks to Dazzozo & Blefish)
- Other fixes and updates by TWRP team
Thanks:
Huge Thanks to Blefish for his CM9 device tree
Download:
v2.7.1.0
http://www.mediafire.com/download/j8ydxivg14y5ktb/recovery_TWRPv2.7.1.0_u8800.img
Source:
Here is a simple source for compile TWRP recovery. Tested with CM11 source;
https://github.com/forumber/TWRP_device_huawei_u8800
Hey, nicely done!
About the graphics, if you are using the older kernel from Huawei, simply remove the graphics.c in the recovery/ and it's reference in BoardConfig.mk. In newer kernels the pagesize is aligned into 4K parts so it might cause issues.
Blefish said:
Hey, nicely done!
About the graphics, if you are using the older kernel from Huawei, simply remove the graphics.c in the recovery/ and it's reference in BoardConfig.mk. In newer kernels the pagesize is aligned into 4K parts so it might cause issues.
Click to expand...
Click to collapse
Thanks
It is using lastest 2.6.35.7 ICS kernel by dzo. Should I do this?
Awesome, keep it up. :good:
So with this cwm, i can flash any roms such as aurora, elora, cm7, miui...without any issues??? can you confirm this? i'm going to flash a new rom so i dont want to get problem wait for your reply :thumbup:
★Sent From My U8800★
lemonade747 said:
So with this cwm, i can flash any roms such as aurora, elora, cm7, miui...without any issues??? can you confirm this? i'm going to flash a new rom so i dont want to get problem wait for your reply :thumbup:
★Sent From My U8800★
Click to expand...
Click to collapse
Yes,you can flash anything without any issues
I cant boot to recovery when using this cwm, it freezes at logo boot. Back to cwm 5.5.0.4, this cwm is still stable up to date :thumbup:
★Sent From My U8800★
Looks working well without any freezing!
Updated version.
But i can't find in their website right version for our phone.
dark_vader said:
Updated version.
But i can't find in their website right version for our phone.
Click to expand...
Click to collapse
I will update to 2.3.3.0 with fixed mass stroage. You can't see the recovery for our phone in TWRP website because this recovery compiled by me so It is unoffical
I've tried this recovery for an hour and it's very. I had 5-6 stucks on reboots when trying to use an option or browse the menus. I hope that you can fix it in next update.
Any chance of one for the pro?
Recovery is updated with bug fixes
_________________________________________________________________
Somcom3X said:
Any chance of one for the pro?
Click to expand...
Click to collapse
If you find the source tree for CM7 or CM9,I can compile for pro
Re: [TOUCH RECOVERY] TWRP Recovery v2.3.3.0
It seems that I got it to work perfectly except for the bugs you said but the graphics are orange. Screenshots later.
Sent from my u8800-51 running popura ICS.
Re: [TOUCH RECOVERY] TWRP Recovery v2.3.3.0
Are you updating the laggy UI?
Sent from my u8800-51 running popaura ICS.
Somcom3X said:
Are you updating the laggy UI?
Sent from my u8800-51 running popaura ICS.
Click to expand...
Click to collapse
No,but I fixed the color problem.
I'm working on fix lagly UI :good:
forumber2 said:
No,but I fixed the color problem.
I'm working on fix lagly UI :good:
Click to expand...
Click to collapse
You still working on?
yoyo97 said:
You still working on?
Click to expand...
Click to collapse
Sure,
I fixed color, ADB and offmode charge but I can't fix the lagly UI in 2.3.3.0 . I will try 2.4.0.0 .If TeamWin fixed this problem,I will release it with 2.4.0.0
forumber2 said:
Sure,
I fixed color, ADB and offmode charge but I can't fix the lagly UI in 2.3.3.0 . I will try 2.4.0.0 .If TeamWin fixed this problem,I will release it with 2.4.0.0
Click to expand...
Click to collapse
ok thanks
forumber2 said:
Sure,
I fixed color, ADB and offmode charge but I can't fix the lagly UI in 2.3.3.0 . I will try 2.4.0.0 .If TeamWin fixed this problem,I will release it with 2.4.0.0
Click to expand...
Click to collapse
Thanks :good:
They already release version 2.4.1.0
Just a heads up, a new version of TWRP recovery is out (2.4.0.0), thanx to the team win devs.
CHANGELOG for 2.4.0.0:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!
Grab it here:
TWRP recovery 2.4 for crespo
TWRP recovery 2.4 for crespo4g
DISCLAIMER:
Rooting your phone and using custom Recoveries and ROMS have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledges about phones and phones utilities too.
Make sure that whatever you do, you are doing it at your own responsibility.
Carliv Touch Recovery
- version 5.7.2 is for Lollipop (cm 12.1, aicp lp or resurrection remix lp) and version 6.6 is for Marshmallow (cm 13, aicp-mm or resurrection remix mm).
The version starting number is related to android version.
This is a CWM based recovery and I did put up some work to update it to lollipop (cm 12.1) and marshmallow (cm-13) after official cwm development stopped at kitkat. It works with LOLLIPOP and MARSHMALLOW kernels and it builds with cm 12.1, aicp lp or resurrection remix lp (version 5.7) and with cm 13, aicp-mm or resurrection remix mm (version 6.5).
This is for those who want a lighter and simpler recovery or they just liked CWM before. It's not as good or complex as twrp, but it will do the job just fine.
For gui I ported PhilZ Recovery full touch module.
Because the vold in cm 12.1 and 13 doesn't support cwm anymore I had to use the old fstab1 type for functionality, although for building reason a valid recovery.fstab should be provided in device tree. In the third post there are some building hints to make it clear for those who want to try building it.
Features:
- EXT4 and F2FS support (for f2fs use the BoardConfig flag).
- full touch menu ported by me from PhilZ touch Recovery. The old Napstar-xda touch module was good but it's quite old and to update that was too much work. Actually There is a version 4 with that touch module, all working, but the touch doesn't work with some input drivers and I had to give up on it for the new and improved version from PhilZ.
- all cwm functionalities are up and working (adb, sideload, backup, restore, install, mass storage...). There is no mtp and if your phone doesn't have an external sdcard you can't connect it to PC while is in recovery mode. But there is usb-otg support, of course if your phone was shipped with that.
- added new menu for backup and restore advanced, to use it for backing or restoring only a specific partition and I also ported from PhilZ the multizip flashing function.
- in Carliv menu there is now a new section for flashing boot and recovery images. It is a feature that I needed during many recovery builds testing. I wanted an easier way to flash other image without booting to android and using an app like RashR. You can browse your storage locations for any image and after choose you will have to select on wich partition should that be flashed. I added multiple confirmations check to avoid flashing on wrong partition. This feature works only with boot and recovery images. I won't add other partitions to this because for other things there are multiple backup restore functions.
- for MTK phones (if the flag is used in Boardconfig) there is a new menu to backup and restore some important partitions like uboot, nvram an secro because they are involved in restoring a lost IMEI, and also the logo partition which may often get broken by bad ported ROMs.
- besides these all my old specific menus (aroma, rainbow...) are still in place.
- added support for dencrypting and mounting data partition using the builtin minivold from cyanogenmod with vdc commands (the ideea came from this post of Lekensteyn). Tested and working well with text ar hex passwords, and maybe will work with pin too but I don't think it will work with pattern .
- added support for dencrypting and mounting adopted storage in marshmallow. The solution is based on this article of nelenkov.
- there is no included root solution. I choose to do it this way because there is no universal root solution now and someone may end up messing things with a non-working root option. You can flash a zip installer from Chainfire's SuperSu or other solution that may work for your phone.
All screenshots are made with my old tool from here (still working well).
CREDITS:
The biggest thanks go to AP756 and DerTeufel1980, two friends from Germany, who sent me a new phone each, with lollipop OS and that helped me a lot to do this.
- Phil3759 for the touch code and many other things from his recovery;
- TWRP developers. I learned a lot from their work;
- Clockworkmod Team starting with Koushik Dutta and ending with all developers that made the CWM recovery what it was;
- Cyanogenmod Developers;
- Nikolay Elenkov;
In next post there are some links for built recoveries. I'll add more soon as I get a valid link (on a reliable webhost) from people who build it for other phones.
I worked alone on this, there is no team here, not because I don't want to , but probably because there was no one interested in this, and so there may be some unspotted bugs. If you find any please do tell me to help on fixing it.
XDA:DevDB Information
Carliv Touch Recovery, Tool/Utility for all devices (see above for details)
Contributors
carliv
Version Information
Status: Stable
Current Stable Version: 5.7.3 & 6.6.1
Stable Release Date: 2016-07-19
Created 2016-05-30
Last Updated 2016-07-19
Changelog and working builds
CHANGELOG 19-07-2016:
- fix backup for old mtk phones.
Lollipop
1. Jiayu S3+
2. Zopo Speed 7+
3. Zopo Speed 7
4. Mlais Mx Base
5. Alcatel Pop C2/C3
6. ZTE Blade L3 / Digicel DL910
7. Nous NS5511
Marshmallow
1. Zopo Speed 7+
2. Zopo Speed 7+ with adopted storage
3. Zopo Speed 7
4. Zopo Speed 7 with adopted storage
* NOTE: sadly the kernel source for zopo marshmallow isn't published so these two don't have touch in recovery, but you can use them as in CWM with phone buttons.
[*] QCOMM devices:
1. Huawei Honor 5x (kiwi)
2. Samsung Galaxy A5 (SM-A500FU)
Building Guide
To build you need a local repo of cm-12.1 or cm-13 and a proper device tree. To see how a buildable device tree looks check this one from my github.
It builds out of the box with aicp lp-5.1 and aicp mm-6.0 too, but like in cm you need a proper device tree.
Some things to be considered:
For BoardConfig:
- the most common thing in all BoardConfig I saw (you need this to use power button to select if you use physical buttons in some situations)
Code:
- BOARD_HAS_NO_SELECT_BUTTON
- for the graphical interface
Code:
- TARGET_RECOVERY_PIXEL_FORMAT
- for mass storage if your phone has an external sdcard, to connect it to PC (this one can be specified in fstab too) - and it has to be without any quotes or slashes
Code:
- TARGET_USE_CUSTOM_LUN_FILE_PATH := /sys/devices/platform/mt_usb/musb-hdrc.0.auto/gadget/lun%d/file
- for LCD backlight lights - and it has to be without any quotes or slashes
Code:
- TARGET_RECOVERY_LCD_BACKLIGHT_PATH := /sys/class/leds/lcd-backlight/brightness
- for vibrator feature - and it has to be without any quotes or slashes
Code:
- VIBRATOR_TIMEOUT_FILE := /sys/devices/virtual/timed_output/vibrator/enable
- with link to a valid recovery.fstab version 2 (it may work without it but it is better to be here)
Code:
- TARGET_RECOVERY_FSTAB
- for a better readability adapted to your screen (check the minui folder for more fonts)
Code:
- BOARD_USE_CUSTOM_RECOVERY_FONT
Carliv Touch Recovery specific flags:
- if you have the recovery on recovery-carliv folder under bootable directory in cm-12.1 source use this next flag.
Code:
- RECOVERY_VARIANT := carliv
NOTE: in cm 13, and other android 6 sources too, you can't build with this flag out of the box and so you have some things to do - the easy one is to rename recovery folder in [recovery-stock] and to place my recovery next to that with the name [recovery]. Other option is to open Android.mk from /sytem/core/healthd and find line 58 where you need to replace [LOCAL_C_INCLUDES := bootable/recovery] with [LOCAL_C_INCLUDES := $(call project-path-for,recovery)].
- with your phone resolution like this width x height
Code:
- DEVICE_RESOLUTION := 720x1280
- if you want to use it with encrypted phone (it work with a non encrypted phone too but it will be smaller if you don't need decrypting function)
Code:
- BOARD_INCLUDE_CRYPTO := true
- if your phone is MTK powered you need this for the MTK menu (it is not mandatory though with the mtk phones shipped with lollipop or marshmallow)
Code:
- BOARD_HAS_MTK_CPU := true
- for touch menu, if your phone has an input driver with PROTOCOL_TYPE_B (synaptic is an example, or many samsung devices); if you have access to, check your kernel input driver for something like this [#define PROTOCOL_TYPE_B] - google it if you want to know more about this
Code:
- BOARD_USE_PROTOCOL_TYPE_B := true
- to block an input device use
Code:
- TOUCH_INPUT_BLACKLIST := "devicename"
- if you use Adopted Storage
Code:
- BOARD_USE_ADOPTED_STORAGE := true
For system.prop from device tree:
Code:
#
# system.prop for mx
#
ro.ctr.crypto.passwd="64656661756c745f70617373776f7264"
ro.ctr.forbid_format=/frp,/persistent,/lk,/uboot,/logo,/metadata,/nvdata,/nvram,/secro
ro.ctr.forbid_mount=/frp,/persistent,/lk,/uboot,/logo,/metadata,/nvdata,/nvram,/secro
ro.ctr.touch_accuracy=7
- to use decrypt data specify here your password (ro.ctr.crypto.passwd); I forgot to mention that if the phone uses encryption, the recovery will start with few seconds delay, because of the decrypting and mounting data process. If the message will tell you that couldn't be decrypted it is possible that your password was wrong or it uses an unsuported type of password. To be sure just restart the recovery from Power menu and if you still get the same message then you need to check your provided password from system.prop or to find a different solution (other recovery like twrp). If you want to decrypt your phone for good you need to format data and data media from Mount/Storage menu but you will loose your data (settings, preferences).
- ro.ctr.forbid_format and ro.ctr.forbid_mount are for partitions from fstab that you don't want to be shown in Mount/ Storage menu with mount and format option (coma separated, no spaces and with leading slash), like in my example above.
- ro.ctr.touch_accuracy to improve the touch handling (bigger lcd_density = bigger accuracy); the initial value is 7, just like in PhilZ Recovery, and I reccomend you to try different numbers to see what is right for you, but don't go over 19.
All these system.prop lines are not mandatory.
Carliv Touch Recovery uses a fstab version 1 named [ctr.fstab] and you have to create a folder recovery in your device tree, in that recovery folder create a new folder named root, in root folder another folder named etc and in that one place the ctr.fstab. Like this:
Code:
recovery/root/etc/ctr.fstab
That will be enough since the compiler will add it in recovery ramdisk and the recovery module will find it in etc folder.
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
# mount point fstype device [device2] fs_options [fs_options2] lun
/boot emmc /dev/block/platform/mtk-msdc.0/by-name/boot
/cache ext4 /dev/block/platform/mtk-msdc.0/by-name/cache
/recovery emmc /dev/block/platform/mtk-msdc.0/by-name/recovery
/system ext4 /dev/block/platform/mtk-msdc.0/by-name/system fs_options=rw
/data ext4 /dev/block/platform/mtk-msdc.0/by-name/userdata fs_options=rw
/internal_sd datamedia /dev/null
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 lun=sys/class/android_usb/android0/f_mass_storage/lun/file
Important here is how you define internal storage which is data media
Code:
/internal_sd [COLOR="Red"]datamedia[/COLOR] [COLOR="Magenta"]/dev/null[/COLOR]
You can see It's used the old way with "datamedia" fstype and /dev/null device.
Important thing: if you have only internal storage define it as
Code:
/sdcard datamedia /dev/null
If you have also an external sdcard, use either way:
Code:
/internal_sd datamedia /dev/null
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
or
Code:
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
If you are using the adopted storage feature for external sd card, define this
Code:
/data_sd ext4 /dev/block/mmcblk1p2 fs_options=adopted
and remove or comment out the line for external sd card.
You can see the internal storage can be sdcard or internal_sd and external sdcard can be sdcard or external_sd, but internal storage can't be external_sd or external sdcard internal_sd.
If your phone has OTG support you can use that too defining it like this
Code:
/usb-otg vfat /dev/block/sda1 /dev/block/sda
or this
Code:
/usbdisk vfat /dev/block/sda1 /dev/block/sda
-check with your phone booted up in Android and a OTG USB mounted to see in [/sys/class/block] or [dev/block] how to set device for this (the dev/block/sdx part).
The recovery has fat32, exfat and ntfs support builtin (also f2fs for file system). You can define your usb-otg and/or external sdcard as "auto" instead of "vfat" and it will work with any of these formats. I tested a portable HDD self powered and it works (120 GB) as usb-otg. Anyway that is available only for zip and image flashing. Maybe I'll make it to work for backup and restore too.
@carliv is back!!! Thanks a lot for this.
Should I port or should I build?
kirito9 said:
@carliv is back!!! Thanks a lot for this.
Should I port or should I build?
Click to expand...
Click to collapse
You should build it of course. I won't make porting recoveries anymore.
Actually wait for a day or two because I'm working on some improvements and I'll push them to github soon.
Also I have a working version for cm13 too. That also need some more tests before release.
carliv said:
You should build it of course. I won't make porting recoveries anymore.
Actually wait for a day or two because I'm working on some improvements and I'll push them to github soon.
Also I have a working version for cm13 too. That also need some more tests before release.
Click to expand...
Click to collapse
I will wait for cm13 support
Anyway this recovery support arm64?
Sure. Look at the phones already supported
Gesendet von meinem HERO1 mit Tapatalk
carliv said:
You should build it of course. I won't make porting recoveries anymore.
Actually wait for a day or two because I'm working on some improvements and I'll push them to github soon.
Also I have a working version for cm13 too. That also need some more tests before release.
Click to expand...
Click to collapse
Goood xD. No more complaints from users who "brick" their devices and blame you :laugh:
All things are mostly done.
Just a little heads up: Added usb-otg support for install zip menu - should work with ntfs, fat, exfat and fat32 usb flash drives (I tested only with fat32). Other improvements too for both versions (lollipop and marshmallow).
I'll push the source tomorrow.
Attached a screenshot of the recovery for marshmallow (cm13).
Thanks to Master [emoji322]
Sent from my Lenovo A7010a48 using XDA-Developers mobile app
Thread updated with instruction and links for the new version for cm-13 and the version for lollipop is upgraded to 5.2.
If some of you build a working recovery and want to share here the link, just post a replay and I'll add it in post #2.
If you have a buildable device tree public on github and want a recovery built for it ask here and maybe I or someone else will do it in some free time.
@carliv do you interested to build this recovery for kenzo (redmi note 3 pro) ?
here's kernel source for it: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/kenzo-l-oss
exodius48 said:
@carliv do you interested to build this recovery for kenzo (redmi note 3 pro) ?
here's kernel source for it: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/kenzo-l-oss
Click to expand...
Click to collapse
The kernel alone is useful only if builds out of the box, but you still need a proper device tree to build, even with a prebuilt kernel. For building a recovery or a ROM that is what you need. I can't build a recovery only with that. Maybe someone else have the phone and manage to create the device tree and it will build the recovery.
Cheers
Look forward to Flash system Image In Carliv Menu
Thank You
Finally CTR for LP & MM! Amazing @carliv, I love this recovery.
Update to version 5.3 for lollipop and 6.2 for marshmallow
CHANGELOG 12-06-2016:
- activated working support for ntfs, exfat and f2fs;
- rewritten the flash image menu for better functionality and more protection to avoid mistakes;
- change the local busybox libs and modules names to avoid conflicting with existing external folder;
- some other small fixes and improvements (you can check the github commits).
@carliv
Hi, I have a device tree that I used for TWRP https://github.com/kirito96/device_Alcatel_4032 recovery and I would like to know if this is enough for building CTR or do I need a "complete" device tree? Thanks.
kirito9 said:
@carliv
Hi, I have a device tree that I used for TWRP https://github.com/kirito96/device_Alcatel_4032 recovery and I would like to know if this is enough for building CTR or do I need a "complete" device tree? Thanks.
Click to expand...
Click to collapse
Not really complete like in building ROMs, but you have to do some changes:
- convert it to cm building or, better and easier for you since it's for omni, to aicp.
- then you need to add in boardconfig partitions sizes (twrp doesn't need that because it checks the size from dumchar_info or partinfo).
- add that recovery/root/etc folder with ctr.fstab in it.
- add specific flags in boardconfig, but if your device has a small recovery partition let the crypto flag out (don't use it at all) and you will gain almost 2 Mb.
- add resolution and desired font if you want to not use the default which is for 540x960 dpi.
and that's it ...
Take a look at my mlais device tree (link in OP)-sorry, in post #3 to see these things - I have a branch for aicp too.
And I see your device use mtk header. You can check in my github for the lenovo p780 device tree where I implemented the mkbootimg part from my kitchen.
Cheers!
PS: if you can send me your phone dumchar_info file and a stock boot image I'll try to convert your device folder to use it as an example for other people about how to do it.
@carliv
Thanks for informing me, but for now I think I'll opt for a device tree that you made and I'll use that as a base for other devices that I'll work on in the future.
I've attached the dumchar_info.txt file below along with the stock boot.img. Funny thing is, I have 2 stock boot.img. I have for which my phone came with (4.2.2) and an AOSP upgrade with 3.10.xx kernel (5.1.1). I uploaded both because this recovery is for LP right? Which should be 3.10.xx kernel. In any case, I'll use what you made as a base. Thanks again.
carliv said:
CHANGELOG 12-06-2016:
- activated working support for ntfs, exfat and f2fs;
- rewritten the flash image menu for better functionality and more protection to avoid mistakes;
- change the local busybox libs and modules names to avoid conflicting with existing external folder;
- some other small fixes and improvements (you can check the github commits).
[/B]
Click to expand...
Click to collapse
You did it!!! :victory:
Good thing I was checking up on you or I might of missed it.
Thanks carliv I realize this project must of been a huge effort on your part and I for one am very grateful :highfive:
TeamWin Recovery
What's new in 3.1.0-0:
# vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
# adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
# tweak MTP startup routines (mdmower)
# support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
# support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
# better indicate to users that internal storage is not backed up (Dees_Troy)
# improve automatic determination of TW_THEME (mdmower)
# minimal getcap and setcap support (_that)
# try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
# shut off backlight with power key (mdmower)
# timeout during FDE decrypt (Dees_Troy and nkk71)
# support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
# boot slot support (Dees_Troy)
# TWRP app install prompt during reboot (Dees_Troy) > Only for Official
# support for AB OTA zips (Dees_Troy)
# support new Android 7.x log command (Dees_Troy)
# update recovery sources to AOSP 7.1 (Dees_Troy)
# numerous bugfixes and improvements by too many people to mention
Bug.? You tell me
Link :
https://drive.google.com/file/d/0By49Zozsl43hdnB0aG43NEZJTVE/view?usp=drivesdk
# Just Flash via current your TWRP
Thanks to :
- ShevT
- Mohancm
- Jonnyxda
Source :
Twrp.me
THX
finally... we have latest TWRP .....
thanks.... !
Can I flash it via previous twrp ..??
465swa said:
Can I flash it via previous twrp ..??
Click to expand...
Click to collapse
Yes, you can.
Thanks
yui90 said:
TeamWin Recovery
What's new in 3.1.0-0:
# vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
# adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
# tweak MTP startup routines (mdmower)
# support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
# support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
# better indicate to users that internal storage is not backed up (Dees_Troy)
# improve automatic determination of TW_THEME (mdmower)
# minimal getcap and setcap support (_that)
# try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
# shut off backlight with power key (mdmower)
# timeout during FDE decrypt (Dees_Troy and nkk71)
# support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
# boot slot support (Dees_Troy)
# TWRP app install prompt during reboot (Dees_Troy) > Only for Official
# support for AB OTA zips (Dees_Troy)
# support new Android 7.x log command (Dees_Troy)
# update recovery sources to AOSP 7.1 (Dees_Troy)
# numerous bugfixes and improvements by too many people to mention
Bug.? You tell me
Link :
https://drive.google.com/file/d/0By49Zozsl43hdnB0aG43NEZJTVE/view?usp=drivesdk
# Just Flash via current your TWRP
Thanks to :
- ShevT
- Mohancm
- Jonnyxda
Source :
Twrp.me
Click to expand...
Click to collapse
the temperature of cpu is 0. Is this a bug?
Pcti888 said:
the temperature of cpu is 0. Is this a bug?
Click to expand...
Click to collapse
Yes, if there is time I will fix.
yui90 said:
Yes, if there is time I will fix.
Click to expand...
Click to collapse
thx,,:highfive:
Your recovery is the only that worked for me please dont keep your thread dead ill be using it for sure!
Its outdated recovery use one from LOS 14.1 thread.
n0p3zz said:
Its outdated recovery use one from LOS 14.1 thread.
Click to expand...
Click to collapse
It doesnt work ,it gets stucked on wipe.
Posso instalar o twrp atraves do flashfy ?m2note 571h
{
"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"
}
OrangeFox 11.1(1) UNOFFICIAL
———————————————————————
Based on: TWRP 3.6.2 (Android 11) | Author: iusmac | Kernel: 4.9.309
Summary:
Code:
Decrypt any Android and any encryption method (FDE or FBE) + Original features
*** DISCLAIMER ***
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 recovery
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.
Installation:
Spoiler
Using recovery:
Spoiler
1. Download the OrangeFox .zip file to your device
2. Boot into to an existing recovery
3. Install OrangeFox .zip file
4. The recovery should reboot automatically into OrangeFox
5. Enjoy!
Using Fastboot:
Spoiler
1. Download the OrangeFox .zip archive to your device and .img image to your PC
2. Connect your device to PC and enter into Fastboot Mode
3. Flash .img using the following commands:
Code:
fastboot erase recovery
fastboot flash {put-here-orangefox-recovery-file-name}.img
fastboot boot {put-here-orangefox-recovery-file-name}.img
4. After the last command your device should boot into OrangeFox
5. Install OrangeFox .zip archive
6. The recovery should reboot automatically
7. Enjoy!
Stock Features:
Spoiler
* Supports Treble and non-Treble ROMs
* Updated with latest TWRP commits
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* Password protection
* Torch and LED
* Support for custom ROMs
* Better language support
* Optimized versions of community scripts
* Fox theme engine allows to set: custom scheme/theme (black, dark, etc)
* Gesture navigation
* Backup OrangeFox settings to internal storage or SD card
* And many more!
New Features (added by author):
Spoiler
Spoiler: 1. FBE Encryption Toggler (FBE = File-Based Encryption)
Spoiler: How to Enable/Disable FBE Encryption
* Make sure that the "Enable FBE" button has changed to "Disable FBE" (or vice versa if disabling)
How it works:
Formatting is needed to erase all traces of full disk encryption (FDE) + we need a completely new file system (recovery will take care of this). Immediately after that, the recovery switches encryption type to FBE in the ROM's vendor.
Spoiler: What is this? What is it for?
Some definition:
Android 7.0 and higher supports file-based encryption (FBE). File-based encryption allows different files to be encrypted with different keys that can be unlocked independently.
https://source.android…/encryption/file-based
Click to expand...
Click to collapse
What does FBE encryption look like?
Spoiler
1. The contents and names of files/folders are encrypted using random characters:
2. Upon system startup, the device is absolutely usable and does not require to enter a password. FBE decryption is bound to Lock Screen and occurs at the time of unlocking using PIN/Password/Pattern.
At the time of writing this post, 100% of our devices use Full Disk Encryption (FDE). Traditionally, FDE encryption is enabled inside ROM's settings, and personally, I did not encounter problems with this type of encryption before Android 10. Unfortunately, on new Androids FDE is very unstable. Moreover, in Android 13 (T) it will be possible to encrypt only using FBE method because FDE method is officially deprecated and will be completely removed.
Android T (AOSP experimental) removes support for full-disk encryption entirely.
https://source.android…y/encryption/full-disk
Click to expand...
Click to collapse
Some FDE issues on Android 10+:
1. The device hangs on boot logo (requires formatting of /data to fix).
2. The device may boot up successfully and be detected as encrypted, but most of the installed applications and settings disappear forever.
3. The device boots correctly but is not detected as encrypted.
Having tried a bunch of ROMs, I have never encountered the problems above and have always been able to successfully encrypt the device with FBE method. Therefore, if you are interested in encryption, accustom yourself to encrypt immediately after ROM flashing, since everything is quite handy
Warning: decryption on Android 12+ and workaround | FIXED in OrangeFox R11.1(4)
Spoiler
FIXED in OrangeFox R11.1(4)
Unfortunately, all ROM's on Android 12+ for our device can successfully be encrypted/decrypted using FBE method, but decryption in recovery is problematic. This is an Android bug, which doesn't expose the decryption keys used by the recovery. Indeed, this is a recovery problem; Android 12 stores decryption keys elsewhere, so recovery can't find them. OrangeFox / TWRP devs are already in the process of adapting to the changes of Android 12. As soon as new recovery is ready I'll build a new release and everything will work. Fortunately, I found out that passwordless decryption works.
Temporary workaround:
1. Reboot to ROM
2. Remove the Lock Screen protection (PIN/Password/Pattern)
3. Reboot to recovery, the data will be automatically decrypted
4. When you're done, reboot to system and enable Lock Screen protection again
Note: you'll need to do this until the ROMs fix the decryption keys related issue.
If you don't remove the Lock Screen protection, then instead of the data you will get:
Spoiler: 2. GUI implementation for USB Storage Exporter by 0xCAFEBABE
This is a GUI implementation of usb-stor-export.sh script for geeks.
For the folks, I implemented a way to export entire eMMC memory. How to use this:
1. Disconnect from PC if connected
2. Go to Mount and swipe the slider
3. Connect the device to the PC
4. Your PC should detect a 16/32GB device, as if you connected an external hard drive
Now, all partitions are at your disposal. You can resize them to add to /data , or make an image of the entire eMMC memory (highly recommend) or backup a specific system partition and restore even on another device. Backup using recovery will not do this to you.
(!) DO EVERYTHING AT YOUR OWN RISK! I AM NOT RESPONSIBLE FOR YOUR ACTIONS ON SYSTEM PARTITIONS!
(!) EVEN IF YOU HAVEN'T TOUCHED ANYTHING, ALWAYS UNMOUNT THE DISK FROM THE OS AND ONLY THEN TAP "Unexport".
Spoiler: 3. eMMC Lifetime Used indicator
It displays life time estimation for your eMMC memory. The percentage means how many reserved blocks have been consumed.
The status can be:
- Undefined = The kernel driver cannot detect eMMC memory state
- Normal = Your eMMC memory is fine
- Warning = Your eMMC memory consumed about 80% of reserved blocks
- Urgent = Your eMMC memory consumed almost 100% of reserved blocks
- Reserved = Your eMMC memory consumed all 100% of reserved blocks and will put itself in read-only mode very soon
For geeks: tap on it to print all HEX values to the console.
Spoiler: 4. Enter to Fastboot Mode inside recovery
This is a hidden feature of OrangeFox itself that I've simply exposed. Unfortunately, important commands like fastboot boot exit with an error, because we are still in recovery and things are kind of busy ... But for something not used/static, like flashing partitions, it's working.
Spoiler: 5. fastboot binary
Now, using OrangeFox's embedded Terminal you can do everything you normally did using a PC.
* If you made a male-to-male USB using an USB-OTG cable, then plug the USB-OTG into the device that will send commands.
Illustration: Xiaomi helps Asus
Spoiler: 6. Dark/Light Theme Toggler accessible from anywhere
This is to make sure your eyes feel comfortable
7. Ability to reboot into Fastboot Mode
8. Binaries: nano, tar, sed and xz utils
9. Support mounting of NTFS drives via OTG
10. Handy aliases (l, ll, la, lo) for `ls` command
11. Colorful support for prompt string (PS1) and for `ls/grep/egrep/fgrep` commands when using ADB/AromaFM
12. VIM - Vi IMproved Editor
13. UI rendering at 60 FPS
14. Support Python
15. Semi-transparent Lock Screen background as in stock TWRP
16. Saving screenshots in /tmp/screenshots if /sdcard is not mounted
Miscellaneous:
Spoiler
Spoiler: Error 7. Failed to unmount: /system. No such volume.
Sometimes got this error when flashing old ROM's of Android 9 and lower. To fix it:
1. Open .zip archive and search for file:
Code:
META-INF/com/google/android/updater-script
2. Open it and remove parts where /system is mounted:
Code:
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup", "/system");
unmount("/system");
also this one
Code:
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore", "/system");
unmount("/system");
3. Save it and repack .zip archive
Spoiler: Red/Blue lines after flashing
Can be fixed by installing a more recent Firmware.
For rolex | For riva
* Firmware for riva is also available on Android 8, so experiment. The Firmware V10.1.1.0.NCKMIFI (Android 7.1) works 100%.
Changelog:
Spoiler
-- OrangeFox 11.1(5) --
* Synced with latest OrangeFox R11.1 sources (September 2022)
* Correct FBEToggler button position in some circumstances
* Handle FBE encryption toggling on Android 13+
* Added fastboot support when rebooting to fastboot from OS
* Moved nano editor to ZIP to save space in ramdisk
* Revert back to /sdcard1 path for Micro SDCard mounting
* Disabled APEX
* Removed logcat binaries to free space in ramdisk
* Updated ueventd from Android 11
* Fixed mke2fs issues when wiping
Thanks to @wisanggeni aka Ervan Kurnia for collaborating
* Updated kernel to 4.9.326-2.2-iusmac
* Updated Magisk to v25.2
-- OrangeFox 11.1(4) --
* Synced with latest R11.1 sources based on TWRP 3.6.2 (Android 12.1)
* Fixed ABX format conversion on Android 12 ROMs
* Moved not vital dependencies to /persist partition after flashing recovery using .zip archive
* Added a 'missing dependencies' pop-up at start-up with an invite to flash recovery using .zip archive
* Added full FBE decryption support for Android 12 ROMs
* Removed extra languages (Chinese, Spanish, Hungarian) to free space in ramdisk
* Added to the console an invite to downgrade the recovery for those who use FBE encryption and Android 11 or lower
-- OrangeFox 11.1(3) --
* Upgraded built-in Magisk to v25.1
* Fixed some bugs
* Added to the console an invite to update the recovery for those who use FBE encryption and Android 12 or higher
-- OrangeFox 11.1(2) --
* Replaced 'Percent' with % for eMMC Lifetime Used value
* Added 'Back' button to FBE Encryption Toggler page
* Added synchronization of the fstab encryption flag with the /data encryption type
* Added battery temperature next to CPU temperature
* Enabled OTA by default
-- OrangeFox 11.1(1) --
* Synced with latest R11.1 sources based on TWRP 3.6.2 (Android 11)
* Upgraded Linux kernel to 4.9.309 (from Android 12)
* Upgraded built-in Magisk to v25
* Added nano, tar, sed, xz utils binaries
* Fixed Full Disk Decryption (FDE) on Android 12+
* Added File Based Encryption (FBE) support
* Added NTFS support for OTG devices
* Added handy aliases (l, ll, la, lo) for `ls` command
* Added colorful support for prompt string (PS1) and for `ls/grep/egrep/fgrep` commands when using ADB/AromaFM
* Fixed nano non starting on OrangeFox's embedded Terminal due to missing terminal info
* Added prebuilt VIM - Vi IMproved Editor v8.2.1643
* Added FBE Encryption Toggler to Partition Manager page
* Enabled reboot to 'Fastboot' item unconditionally
* Labeled /dsp partition as 'DSP'
* Moved MicroSD card mount point from /sdcard1 to /external_sd
* Added GUI implementation for USB Storage Exporter by 0xCAFEBABE to Mount page
* Added eMMC Lifetime Used indicator to Partition Manager page
* Add entering to Fastboot mode page to Main menu
* Added fastboot v29.0.6
* Increased UI rendering to 60 FPS
* Added Python v3.10.4
* Added Dark/Light Mode Toggler
* Made the lockscreen background semi-transparent as in stock TWRP
* Added support for saving screenshots in `/tmp/screenshots` if `/sdcard` is not mounted
* Removed Splash changing (it requires ramdisk repacking in recovery.img which exceeds bootloader limit)
Spoiler: (Important) Which OrangeFox version you should choose
CaseR11.1(3) or olderR11.1(4) or newerLatest versionMy ROM is not encryptedXI have an encrypted MIUIXMy ROM was encrypted using ROM's settingsXMy ROM is Android 11 (or lower) and it's encrypted with FBE methodXMy ROM is Android 12 (or higher) and it's encrypted with FBE methodX
Download latest OrangeFox release | Find all OrangeFox releases
OrangeFox 11.1(2) Update
Code:
* Replaced 'Percent' with % for eMMC Lifetime Used value
* Added 'Back' button to FBE Encryption Toggler page
* Added synchronization of the fstab encryption flag with the /data encryption type
* Added battery temperature next to CPU temperature
* Enabled OTA by default
Download latest OrangeFox release | Find all OrangeFox releases
OrangeFox 11.1(3) + OrangeFox 11.1(4) Update
Spoiler: (Important) Which OrangeFox version you should choose
CaseR11.1(3) or olderR11.1(4) or newerLatest versionMy ROM is not encryptedXI have an encrypted MIUIXMy ROM was encrypted using ROM's settingsXMy ROM is Android 11 (or lower) and it's encrypted with FBE methodXMy ROM is Android 12 (or higher) and it's encrypted with FBE methodX
Code:
-- OrangeFox 11.1(4) --
* Synced with latest R11.1 sources based on TWRP 3.6.2 (Android 12.1)
* Fixed ABX format conversion on Android 12 ROMs
* Moved not vital dependencies to /persist partition after flashing recovery using .zip archive
* Added a 'missing dependencies' pop-up at start-up with an invite to flash recovery using .zip archive
* Added full FBE decryption support for Android 12 ROMs
* Removed extra languages (Chinese, Spanish, Hungarian) to free space in ramdisk
* Added to the console an invite to downgrade the recovery for those who use FBE encryption and Android 11 or lower
-- OrangeFox 11.1(3) --
* Upgraded built-in Magisk to v25.1
* Fixed some bugs
* Added to the console an invite to update the recovery for those who use FBE encryption and Android 12 or higher
Download latest OrangeFox release | Find all OrangeFox releases
mtp mode not working in v11.1.4 in rolex
Hello, I have problem with booting recovery. After installing and booting into it that is happens
Max1mus said:
Hello, I have problem with booting recovery. After installing and booting into it that is happens
Click to expand...
Click to collapse
Solved this problem with installing via fastboot miui with android 7 onboard.
Max1mus said:
Solved this problem with installing via fastboot miui with android 7 onboard.
Click to expand...
Click to collapse
read the post better...
https://imgur.com/nuaM3DW
OrangeFox 11.1(5) Update
Code:
* Synced with latest OrangeFox R11.1 sources (September 2022)
* Correct FBEToggler button position in some circumstances
* Handle FBE encryption toggling on Android 13+
* Added fastboot support when rebooting to fastboot from OS
* Moved nano editor to ZIP to save space in ramdisk
* Revert back to /sdcard1 path for Micro SDCard mounting
* Disabled APEX
* Removed logcat binaries to free space in ramdisk
* Updated ueventd from Android 11
* Fixed mke2fs issues when wiping
Thanks to @wisanggeni aka Ervan Kurnia for collaborating
* Updated kernel to 4.9.326-2.2-iusmac
* Updated Magisk to v25.2
Download latest OrangeFox release | Find all OrangeFox releases
THE BEST RECOVERY FOR RIVA
#RECOMMENDED #1
Hello, does OrangeFox Recovery use Android 7.1 or 8.1?
liaotingwei said:
Hello, does OrangeFox Recovery use Android 7.1 or 8.1?
Click to expand...
Click to collapse
You need latest nougat firmware to run it.