Philz touch recovery для explay vega
Dating > Philz touch recovery для explay vega
Download links: → Philz touch recovery для explay vega → Philz touch recovery для explay vega
Скачиваем архив с кастомным рекавери для вашей версии Android во вложениях два архива , распаковываем и скидываем файл recovery. Вы должны понимать, что делаете. Look at next step to regenerate md5 for stock cwm compatibility. Но перед большинством из вас перед вами будет преграда в виде закрытого bootloader. Все ссылки на загрузки находятся на странице —.
Quote: Project Status: No Longer Updated As I mentioned before, I have a lot of new important projects in my real life. I am very happy to abandon this project for real life alternatives. CWM is a dead project for now, until some dev resurrects it. I was about to do, until these new projects came. Current version will probably work a while for many devices. Some devices with new ROM installers could have issues. Just use TWRP and avoid the new CM Simple Recovery If the current version works for you, there is no reason you don't use it though. No need to bitch in all threads because it doesn't work for you. Just move on to other alternatives. This is by design and not a bug. Main menu and PhilZ Settings GUI Preferences: all is applied live no reboot. Up to 14 menu height settings, scroll sensitivity, touch accuracy... Else, skip the vold changes and flags see below details Optional PhilZ Touch extra flags: The below info are optional. That way I can spot needed changes easier. They are open source now Not for now. It is made completely open source code, built from sratch. Look at next step to regenerate md5 for stock cwm compatibility. Put your custom scripts there with file extension. I added extra checks to make it robust to validation by error while scrolling. Double Tap: menus are highlighted on first touch. To validate action, you need to double tap the same menu Semi Touch: the classic semi-touch interface I enhanced. Disable Touch: touch code completely disabled. Lower values are the most sensitive. You can also set recovery to auto-restore them when needed. You can change those time settings. External storage will be always used first. If no external storage is found, internal storage is used. That way, logs are kept in full screen. Obviously, no pause will be performed on boot scripts and multi-zip operations How to Install This will depend on your device. Please look first for help in your device specific thread. Provided instructions here ARE NOT VALID for all phone Recovery. Once flash is done, keep pressing the 3 buttons combo to for a reboot into recovery. It could still be affected by assert error on device name getprop. However, that one is easier to fix by end users by editing updater-script. This is a workaround. G for this port 4. Now, you can read teh screen logs even when having big menus - reorganized menus layout - miscellaneous fixes in initramfs for the kernel 2. See post 2 for details on how to use this new feature - No more true insecure kernel ro. The advantage is for all stock +4. Path changed in v5! This will give full compatibility with cwm, CM roms and CM Updater 6- How to flash a boot. Low compression setting gives around 30% compression with quiet no impact on speed. Rising compression value makes backups extremely slow with very little gain on space. Stock CWM uses exfat fuse but without any buffering of writes. The end of it is a non usable thing for any backup because of an incredibly slow write speed. TWRP uses exfat fuse binary to do the backups + caches tar writes to improve speed. This could cause data corruption on some devices. PhilZ Touch uses patched kernel with native exfat support static mode for Samsung devices and soon other brands. This is supposed to be the faster and safest way. However, it seems to struggle on some devices because of the logging mode used by CWM Solutions: - hide progress bar in Nandroid Settings menu: this will dramatically improve speed for many devices - do not use exfat - change exfat card to another brand. Unlocked bootloader users can still extract the recovery. In all zip installers, you have a file called update-binary. It is the executable that will process and interpret all commands in updater-script, which will do all actions. Older update-binary files cannot access system assert props on kitkat based kernels. Fixes: - edit your updater-script in zip file and remove all assert lines checking for device name. Use notepad++ or a linux editor - manually change your update-binary in the zip with a new one you take from a cm-11. First read FAQ 10 Start of 6. If it detects an outdated version, it will be automatically replaced during flash. This will fix all assert getprop errors discussed in FAQ 10 often used to check if the zip is meant to be flashed on your device However, doing so, can expose you to a bunch of new errors if the update-binary is +2 years old. It will make it work except for the assert for device name error. However, that error is very easy to fix by any one see FAQ 10. The option doesn't stick on reboot, you have to manually set it when you flash such files. It is done on purpose to keep you warned about potential risks using such bad scripts often coming from a copy paste procedure - hammer your ROM maker to keep up to his time, and look closer at his scripting and update-binary engine used 12- Time fix for Qualcom Chips and other devices On many Qualcom devices, setting the time is disabled on different levels, depending on the device New PhilZ Touch versions added a workaround to this limitation. The fixes do not modify in anyway the RTC flags in kernel, as it is not recommended by Qualcom - Qualcom Time Daemon: This is the recommended option. Ask your ROM dev to properly implement Qualcom proprietary binaries and RTC permissions. You have to enable the option. Do it AND Validate your choice to apply the actual time. Enabling the offset mode without manually setting correct time AND validating your option has no effect! Disable previous 2 options and enable this one. Else, it won't have any effect. PhilZ Touch is just a CWM mod in that regard. Installer won't be verifying you did so - you cannot mount vold paths sdcard, usb storage...
Last updated
