[MOD] FlymeUI Statusbar for SM-T311 Kitkat XXUBNHA - Galaxy Tab 3 Themes and Apps

DISCLAIMER
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.
*/
FlymeUI StatusBar for SM-T311 Kitkat XXUBNHA
Screenshot :
How to install :
- Download the .zip
- Move .zip to sdcard
- Reboot to CWM/TWRP
- Install .zip
- Reboot to System
- Enjoy
LINK = DOWNLOAD

Related

[GUIDE][ROOT] Nokia X2

Obtain Root on Nokia X2
Disclaimer:
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Hello new users! This is a guide on how to root your new Nokia X2. It was carried out and tested by @Altivex. We will be using the TowelRoot exploit to get root access on Nokia X2.
Instructions:
1. Connect your Nokia X to your PC.
2. Download the Root X2.zip.
3. Extract the contents of the zip onto your Desktop.
4. Copy the APKs to your SD Card.
5. Now, on your phone, goto Settings-->Security and under Device Administration, Check Unknown Sources.
6. Make sure you are connected to the internet.
7. Using ES or any other File Manager, browse to the place where you copied the apps.
8. Install TowelRoot.apk
9. Run the app and Root your phone.
10. After that, go and install Superuser.apk
11. Open it and update your SU Binaries.
Volla! You now have a rooted Nokia X2.
Screenshot: http://forum.xda-developers.com/attachment.php?attachmentid=2868316&d=1406199049
Credits:
@Altivex for testing this.
@geohot for TowelRoot Exploit.
Awsome
:good:
Dom3616 said:
Obtain Root on Nokia X2
Disclaimer:
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Hello new users! This is a guide on how to root your new Nokia X2. It was carried out and tested by @Altivex. We will be using the TowelRoot exploit to get root access on Nokia X2.
Instructions:
1. Connect your Nokia X to your PC.
2. Download the Root X2.zip.
3. Extract the contents of the zip onto your Desktop.
4. Copy the APKs to your SD Card.
5. Now, on your phone, goto Settings-->Security and under Device Administration, Check Unknown Sources.
6. Make sure you are connected to the internet.
7. Using ES or any other File Manager, browse to the place where you copied the apps.
8. Install TowelRoot.apk
9. Run the app and Root your phone.
10. After that, go and install Superuser.apk
11. Open it and update your SU Binaries.
Volla! You now have a rooted Nokia X2.
Screenshot: http://forum.xda-developers.com/attachment.php?attachmentid=2868316&d=1406199049
Credits:
@Altivex for testing this.
@geohot for TowelRoot Exploit.
Click to expand...
Click to collapse

[recovery]*update*cwm6-philz touch/neatkernel-stable

* * * * * * * * * * * * * * * * * * * * * * * * *
PhilZ Touch 6 Recovery
CWM Advanced Edition 6.x
* * * * * * * * * * * * * * * * * * * * * * * * *​
philz-cwm6 op
http://forum.xda-developers.com/showthread.php?t=2201860
philz is no longer supported.
************************************************************************************************************YER WARRANTY IS NOW VOID. I AM NOT RESPONSIBLE FOR YER ACTIONS. RESEARCH YER DEVICE BEFORE MODIFYING***************************************************************************************************
*********************THESE KERNELS ARE NOT DUAL BOOT RECOVERIES*****************************
CYANOGENMOD STOCK KERNEL/PHILZ​
THIS RECOVERY IS VERIFIED WORKING BY ME PERSONALLY USING A KITKAT ROM (CM11)
HOW TO INSTALL
DOWNLOAD
https://drive.google.com/file/d/0B5FXgIkne2uXaV9mc3lCa19Ua1k/view?usp=sharing
YOU NEED HEIMDALL
Code:
sudo heimdall flash --KERNEL ~/Desktop/boot.img
*************************************************************************************************************
YOU CAN TEST PHILZ CWM6 TOUCH
DOWNLOAD
https://drive.google.com/file/d/0B5FXgIkne2uXRkZHaDF0OHBVZWM/view?usp=sharing
FLASH ^ WITH CURRENT RECOVERY, A REBOOT WILL RESTORE YER CURRENT RECOVERY.
NO BUGS AS OF YET
*****************************************************************************************
*****************************************************************************************
NEATKERNEL/PHILZ​
DOWNLOAD
https://app.box.com/s/f5r4xgl00hnxj9dmb8to0fma4amwcay6
INSTALL
FLASH ZIP CURRENT RECOVERY
IF WIFI IS NOT WORKING
https://app.box.com/s/8uwjvnflfsx4ywxqum760uxkv9e0462c
Code:
adb push /modules /system/lib/modules
or copy paste with root browser
**************************************************************************************
SOURCES
https://github.com/PhilZ-cwm6/philz_touch_cwm6
https://github.com/CyanogenMod/android_kernel_samsung_aries
https://github.com/mohammad92/NeatKernel_captivate/tree/stable
REFERANCED TOOLCHAIN INFO BELOW
https://github.com/brandonabandon/arm-cortex_a8-linux-gnueabi
THANKS
thanks to mohammad.afaneh for his kernel deving and allowing permission to host,philZ,cm, aosp.
will restore backups from cwm 6 (non-philz) but will restore the recovery (non-philz) as well. make a new backup for philz. for aroma, dl the zip make new folder aromafm with aromafm.zip renamed. boot recovery, install from sd tap aromafm.zip. now you can tap aroma from the menu.
BUG
i found a minor bug. after mounting usb storage you cannot access sdcard. ie pulling files from pc via usb cord, then attempting to flash. you will need to reboot recovery after accessing usb storage to regain access to sdcard.
edit.
BUG FIX
unmount usb via pc before unmounting device "safe removal" for access to files via recovery after mount/unmounting.
About the WiFi fix for neatkernel there is no modules folder in /system/lib do I have to make one?
Bronando said:
About the WiFi fix for neatkernel there is no modules folder in /system/lib do I have to make one?
Click to expand...
Click to collapse
push or copy/paste the modules folder. make yer own modules folder if you like.

[ROM][7.1.2] LineageOS-eXtended [26 FEB 2018]

Disclaimer
Code:
[COLOR="gray"]
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired [B]because the alarm app failed[/B].
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
[/COLOR]
Prerequisites for Installation
- Must have an unlocked bootloader
- Update TWRP to Android-7.1 builds located here. Please make sure to use the recovery image which is appropriate for your device (Thor or Apollo).
Fresh Installation
- Backup your existing ROM first
- Wipe the /data partition (but you can keep the media storage)
- Flash the ROM File
- Flash Open Gapps: use an ARM 7.1 version smaller than the "full" size to make sure it fits
- Reboot
- Enjoy!
LineageOS-eXtended Downloads
LineageOS Builds for Thor (ggow)
LineageOS Builds for Apollo (ggow)
Gapps
- Open Gapps (use a size smaller than "Full" to make sure it fits)
NOTE: Here's what I do to solve the "Play Games" side load issue... Anytime I update my GApps zip file:
- I download the "full" and "mini" versions of GApps
- Extract the "GApps/playgames-arm.tar.lz" file from the "full" file and add it to the "GApps" folder of the "mini" file.
- Open the installer.sh script in the "mini" file and move the "playgames" line from the full_gapps_list= section into the mini_gapps_list= section
- I use this modified "mini" .zip when flashing CM-14.1 ROMs so that my Play Games install always works.
Source Code (branch: cm-14.1)
- LineageOS-eXtended
- Kernel Source
- Common Device Tree
- Thor Device Tree
- Apollo Device Tree
Credits
- LineageOS Team
- Cyanogenmod Team
- LineageOS-eXtended Team
- CodeAurora
- ggow
- Cpasjuste
- dpeddi
XDA:DevDB Information
LineageOS-eXtended, ROM for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
ggow
ROM OS Version: 7.x Nougat
Version Information
Status: Stable
Created 2018-02-28
Last Updated 2018-02-28
What is different between LineageOS and LineageOS-eXtended?
Mark2014 said:
What is different between LineageOS and LineageOS-eXtended?
Click to expand...
Click to collapse
Responded here: https://forum.xda-developers.com/ki.../rom-lineageos-extended-t3757025/post75736834
The links to download the rom is not working. The hyperlink shows basically the same as the text
Closed per OP request

[UNOFFICIAL][028-Beta][TWRP 3.2.3-0] REDWOLF RECOVERY PROJECT

{
"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:
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.3
Authors build: ATG Droid & dadi11
Developers:ATG Droid & dadi11
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:
Code:
Translated to EN, PL, zh_cn, & CZ
- 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.
* Changes for security reasons *
- 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:
Code:
- get out of here if you are pirating apps. this recovery is not for you
- always up-to-date with the latest TWRP changes
- compiled on omnirom-7.1 source
- kernel compiled inline with the recovery
- fixed backup/restore of Firmware
- added F2FS support
- added NTFS support
- added exFAT support
- more languages
- other improvements from Features and Changelog lists
CHANGELOG :
Code:
25-08-2018
* Full Backup and Restore Partition
* Delete /cust and change /vendor
* Fix f2fs on data and cache partition
* Fix MTP on Windows
16-08-2018
* File-manager: Add support for rendering of multiple selected files & ability to do a specific action for these files at once
* Force rendering of the different GUI icon element object for zip files under the GUI Scroll list, since file-manager show special action for them
* Revert changes which caused issues with slow reboot in 027
* MIUI-Updater: Fix sometimes possible double declaration of the final install status
* DataManager: Fix the TWRP's missing LOGINFO mount point for Output_Version
* RWDumwolf: Add support for the different fstab path on some devices
* RWDumwolf: Better handle the process of modifications to the default properties and let user know about the number of modified ones
* RWDumwolf: Find and remove start of flash_recovery service from inits, if it exists
* Recovery: Don't rename scripts under the /system/bin /system/etc for stock recovery replace, instead of it set different permissions to cause issues with execution
* RWDumwolf: Cleanup
* Updater: Properly handle info about the OSE package signature
* Recovery: Directly call start of the ADB if at the start of main we aren't able stat password file
* Recovery: Correctly handle ADB with recovery password related changes
* Recovery: Update to Oreo tree
* Partition-List: Add new list types for OSE partitions and storages for backup/restore process
* Installation: Load zip entries directly to buffer instead of extracting them
* ORS: Reboot on the sucessfull installation is now optional based on user's selection from the GUI
* ORS: Call Deactivation Process even if reboot on finished ORS isn't allowed or isn't forced by the ORS result
* OPTM: Call set action with the empty value in case that value should be positive
* OPTM: Fallback to main without variable which would be needed to be parsed is now directly down with call of home
* GUI: Allow user to select any active storage for the OSE backup/restore process
* OPTM: Call clear action instead of set if argument is negative
* GUI: Allow user to select OSE partitions for the backup/restore process, instead of the previous direct definition
* Installation: Add support for the format of A/B packages on the OSE zip detection
* GUI: Remove redefinitions of objects from screen page, since they're already defined on one overlay
* PartitionManager: Add new fstab flag to exlude partition from the GUI mount section, cust isn't really needed to be here if we want to use double mount points for one block device
* GUI: Remove for us the useless theme loading parts from previous builds
* Installation: Set install status info to tmpfs first and then update the status in cache during the log file update, since the previous implementation was just slowing us
* Recovery: Set path for screenshots directly to main folder instead of previous resource one
* TWFunc: Cleanup
* GUI: Improve flashlight compatibility with different devices
* OSE: Improve backup/restore call
* Device-Tree: Add support for unofficial treble support on officialy supported devices
* GUI: Fix missing page on the rebootcheck call which caused complete lag during the reboot with formatted system partition
* Recovery: Call Deactivation Process on reboot if there wasn't at least single call during the main threads
* RWDumwolf: Force persist.sys.recovery_update to false during the cleanup process
* OSE: Fix the variable mismatch caused by global variable definitions without handling the previous possible defined value
* INIT: Add new triggers for the ADB startUP.
* We're sure that there is also a lot of other changes which we just forgot to mention
DOWNLOAD
CHANNEL AND GROUP :
* https://t.me/zhanreport
* https://t.me/zhanproject
DONATION
Jika anda merasa puas dengan hasil kerja saya, dan mendukung project saya agar bisa lebih berkembang, silahkan donasi seikhlasnya ke rekening BRI, dgn nomor rekening 3112-01-019706-53-4 atas nama "Muhammad Rifa'i Aziz"
Join on grup ZHAN Project Tester and Report - https://t.me/zhanreport
Follow My Instagram - https://www.instagram.com/zhantech
Like My Facebook Fan Page - https://m.facebook.com/zhantech/
XDA:DevDB Information
Redwolf Recovery, Tool/Utility for the Xiaomi Redmi 4X
Contributors
faizhifzhan, ATG Droid, Dadi11
Source Code: https://github.com/RedWolfRecovery/rw_recovery
Version Information
Status: Beta
Current Beta Version: 028
Beta Release Date: 2018-08-25
Created 2018-08-28
Last Updated 2018-08-28
CHANGELOG
25-08-2018
* Full Backup and Restore Partition
* Delete /cust and change /vendor
* Fix f2fs on data and cache partition
* Fix MTP on Windows
16-08-2018
* File-manager: Add support for rendering of multiple selected files & ability to do a specific action for these files at once
* Force rendering of the different GUI icon element object for zip files under the GUI Scroll list, since file-manager show special action for them
* Revert changes which caused issues with slow reboot in 027
* MIUI-Updater: Fix sometimes possible double declaration of the final install status
* DataManager: Fix the TWRP's missing LOGINFO mount point for Output_Version
* RWDumwolf: Add support for the different fstab path on some devices
* RWDumwolf: Better handle the process of modifications to the default properties and let user know about the number of modified ones
* RWDumwolf: Find and remove start of flash_recovery service from inits, if it exists
* Recovery: Don't rename scripts under the /system/bin /system/etc for stock recovery replace, instead of it set different permissions to cause issues with execution
* RWDumwolf: Cleanup
* Updater: Properly handle info about the OSE package signature
* Recovery: Directly call start of the ADB if at the start of main we aren't able stat password file
* Recovery: Correctly handle ADB with recovery password related changes
* Recovery: Update to Oreo tree
* Partition-List: Add new list types for OSE partitions and storages for backup/restore process
* Installation: Load zip entries directly to buffer instead of extracting them
* ORS: Reboot on the sucessfull installation is now optional based on user's selection from the GUI
* ORS: Call Deactivation Process even if reboot on finished ORS isn't allowed or isn't forced by the ORS result
* OPTM: Call set action with the empty value in case that value should be positive
* OPTM: Fallback to main without variable which would be needed to be parsed is now directly down with call of home
* GUI: Allow user to select any active storage for the OSE backup/restore process
* OPTM: Call clear action instead of set if argument is negative
* GUI: Allow user to select OSE partitions for the backup/restore process, instead of the previous direct definition
* Installation: Add support for the format of A/B packages on the OSE zip detection
* GUI: Remove redefinitions of objects from screen page, since they're already defined on one overlay
* PartitionManager: Add new fstab flag to exlude partition from the GUI mount section, cust isn't really needed to be here if we want to use double mount points for one block device
* GUI: Remove for us the useless theme loading parts from previous builds
* Installation: Set install status info to tmpfs first and then update the status in cache during the log file update, since the previous implementation was just slowing us
* Recovery: Set path for screenshots directly to main folder instead of previous resource one
* TWFunc: Cleanup
* GUI: Improve flashlight compatibility with different devices
* OSE: Improve backup/restore call
* Device-Tree: Add support for unofficial treble support on officialy supported devices
* GUI: Fix missing page on the rebootcheck call which caused complete lag during the reboot with formatted system partition
* Recovery: Call Deactivation Process on reboot if there wasn't at least single call during the main threads
* RWDumwolf: Force persist.sys.recovery_update to false during the cleanup process
* OSE: Fix the variable mismatch caused by global variable definitions without handling the previous possible defined value
* INIT: Add new triggers for the ADB startUP.
* We're sure that there is also a lot of other changes which we just forgot to mention
DOWNLOAD : https://www.androidfilehost.com/?fid=1322778262903989772

[OFFICIAL][S v1.4.5][TWRP 3.2.3] BATIK RECOVERY 19/02

BATIK RECOVERY
{
"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.
*
*/
Batik Recovery is Project Recovery developed by Batik Recovery Teamwork from Indonesia, this Batik Recovery is a derivative of the Official TWRP that was modified by the developer in accordance with the Indonesian characteristics. In Indonesia, batik is a motif that is considered quite famous for the beauty of its art. Therefore, the developer gave the name Batik Recovery and a touch of batik motifs in the Recovery, including splash, background, and icon. The goal of the developer to release the project is to further popularize batik, and especially to popularize the name of Indonesia.​
Based on TWRP version: 3.2.3
Source : https://github.com/BatikRecovery/
Device Tree : https://github.com/BatikRecovery/br_devices
For devices (OFFICIAL) : Santoni, Markw, Rendang, Sumire, Mido, Kenzo, Land, Riva, Rolex, Vince, Ido, Rosy, Whyred, Leeco Lemax2, Asus Zenfone Max Pro M1, Platina
Thanks : Allah Ta'ala, Rasulullah, My Family, Reza Adi, Mr Yacha, Muhajaya, Vickry, Ahmad-farid007, Rivv, Rizak, #nTu21, Costa Nostra, ali_tea, Helmi Amirudin
Credit : Github for source code, Teamwin Recovery Project, Dark Recovery, Pitchblack Recovery Project, Orangefox Recovery Project, SuperSu by Chainfire, Magisk for topjohnwu, Lazyflasher by jcadduono, Cam2API Enabler(HAL3) by helmiau, Password Remover by Magua, Aroma File Manager by amarullz, App Deleter by THE_pirate_predator
FEATURES :
Support Treble (Vendor) or Non Treble
Support GSI, Android Pie
Support Miui OTA
Support F2fs
Ramdisk Cleaner
Enable / Disable HAL3
App Delete
Enable / Disable Navbar
Del Subs Overlay
Lazy Flasher
Reset Password
Aroma FM
Root / Unroot Magisk
Mount Magisk
CHANGELOG :
Code:
~ Alpha-01 ~
* Initial Build
~ Alpha-02 ~
* Add Fitured
~ B v1.1 ~
* Upstreamed base TWRP 3.2.3-0
* Update Batik Theme v1.1
* Update Magisk 16.71
* Add Indonesia, Sunda Language
~ B 1.2 ~
* Overlay Reboot Menu
* Add some icon style
* Update Magisk 17.1
* Add Jowo Language
* Full Backup / Restore Partition
* Further ensure TWRP is not replaced by stock recovery
~ B 1.3 ~
* Add Square Style, Circle Style Icon
* Add Change Color Theme (Header & Navbar)
* Change Themes without Reboot
* Update Magisk 17.2
* Add Mount Magisk (Tools)
* Merge September Security Patch (android-8.1.0_r46)
~ S 1.4 ~
* Add Wipe Substratum on Page Wipe
* Add Automatic Disable DM-Verity
* Add OTA MIUI Support
* Update Magisk 17.3
* Update October Security Patch
Downloads :
SourceForge
Installations :
Flash Zip file with other TWRP
and then Reboot Recovery
Enjoy
JOIN GRUP AND CHANNEL TELEGRAM :
ZHAN Testing And Report Group
ZHAN Project Channel
Reserved.
CHANGELOG :
* BringUp S-1.4.5
* Add Tools: Adblock and Miui OTA Disabler by helmiau
* Change New Logo
* Change New Splash with New Logo
* Update Magisk 18.1
* Add Simple Button : Enable Miui OTA and Disable MIUI OTA
WOW !!! :highfive:
Thanks man, just flashed
Update ota MIUI 10 android 9 Xiaomi.eu, have bootlop
lucainno said:
Update ota MIUI 10 android 9 Xiaomi.eu, have bootlop
Click to expand...
Click to collapse
Fixed new version
ManoloRey said:
Fixed new version
Click to expand...
Click to collapse
what should i do, it keep like this :crying:
ManoloRey said:
BATIK RECOVERY
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.
*
*/
Batik Recovery is Project Recovery developed by Batik Recovery Teamwork from Indonesia, this Batik Recovery is a derivative of the Official TWRP that was modified by the developer in accordance with the Indonesian characteristics. In Indonesia, batik is a motif that is considered quite famous for the beauty of its art. Therefore, the developer gave the name Batik Recovery and a touch of batik motifs in the Recovery, including splash, background, and icon. The goal of the developer to release the project is to further popularize batik, and especially to popularize the name of Indonesia.​
Based on TWRP version: 3.2.3
Source : https://github.com/BatikRecovery/
Device Tree : https://github.com/BatikRecovery/br_devices
For devices (OFFICIAL) : Santoni, Markw, Rendang, Sumire, Mido, Kenzo, Land, Riva, Rolex, Vince, Ido, Rosy, Whyred, Leeco Lemax2, Asus Zenfone Max Pro M1, Platina
Thanks : Allah Ta'ala, Rasulullah, My Family, Reza Adi, Mr Yacha, Muhajaya, Vickry, Ahmad-farid007, Rivv, Rizak, #nTu21, Costa Nostra, ali_tea, Helmi Amirudin
Credit : Github for source code, Teamwin Recovery Project, Dark Recovery, Pitchblack Recovery Project, Orangefox Recovery Project, SuperSu by Chainfire, Magisk for topjohnwu, Lazyflasher by jcadduono, Cam2API Enabler(HAL3) by helmiau, Password Remover by Magua, Aroma File Manager by amarullz, App Deleter by THE_pirate_predator
FEATURES :
Support Treble (Vendor) or Non Treble
Support GSI, Android Pie
Support Miui OTA
Support F2fs
Ramdisk Cleaner
Enable / Disable HAL3
App Delete
Enable / Disable Navbar
Del Subs Overlay
Lazy Flasher
Reset Password
Aroma FM
Root / Unroot Magisk
Mount Magisk
CHANGELOG :
Code:
~ Alpha-01 ~
* Initial Build
~ Alpha-02 ~
* Add Fitured
~ B v1.1 ~
* Upstreamed base TWRP 3.2.3-0
* Update Batik Theme v1.1
* Update Magisk 16.71
* Add Indonesia, Sunda Language
~ B 1.2 ~
* Overlay Reboot Menu
* Add some icon style
* Update Magisk 17.1
* Add Jowo Language
* Full Backup / Restore Partition
* Further ensure TWRP is not replaced by stock recovery
~ B 1.3 ~
* Add Square Style, Circle Style Icon
* Add Change Color Theme (Header & Navbar)
* Change Themes without Reboot
* Update Magisk 17.2
* Add Mount Magisk (Tools)
* Merge September Security Patch (android-8.1.0_r46)
~ S 1.4 ~
* Add Wipe Substratum on Page Wipe
* Add Automatic Disable DM-Verity
* Add OTA MIUI Support
* Update Magisk 17.3
* Update October Security Patch
Downloads :
SourceForge
Drive
Installations :
Flash Zip file with other TWRP
and then Reboot Recovery
Enjoy
JOIN GRUP AND CHANNEL TELEGRAM :
ZHAN Testing And Report Group
ZHAN Project Channel
Click to expand...
Click to collapse
Bootloop when backup.Any idea about this?
Kaconk said:
what should i do, it keep like this :crying:
Click to expand...
Click to collapse
you can start, more installation worked out
Seems this recovery does not support encrypted data fully. It detects and prompts for the password, my password does not successfully mount the data partition.
papodaca said:
Seems this recovery does not support encrypted data fully. It detects and prompts for the password, my password does not successfully mount the data partition.
Click to expand...
Click to collapse
no recovery will support your encrypted date, this kernel thing used, we still do not have something decent, backup your date and format the first time
Anyone tested it on MI 8 lite. It looks like a batter recovery for stock roms. I want to use it but I have no time to test it
Haroon Shehzad said:
Anyone tested it on MI 8 lite. It looks like a batter recovery for stock roms. I want to use it but I have no time to test it
Click to expand...
Click to collapse
I am using it right now. Not really tested much yet just installed mi-globe after unlocking bootloader last week. I will be flashing a few roms this week and will post if I run across any issues.
up
cidxtc said:
I am using it right now. Not really tested much yet just installed mi-globe after unlocking bootloader last week. I will be flashing a few roms this week and will post if I run across any issues.
Click to expand...
Click to collapse
Did you try ota update on stock miui rom
Haroon Shehzad said:
Did you try ota update on stock miui rom
Click to expand...
Click to collapse
I didn't test stock ota update I wont fun stock miui unless I have to wait on unlock. I have flashed multiple custom miui roms and one aosp rom. Everything flashed fine along with backup and restore of all roms. I tested a few of the scripts/tools and no problems so far.
Edit: aroma gapps 9.0 wont install. After selecting all options and install starts recovery reboots. Then no matter what reboot option I choose it boots back into recovery. Have to long press power to reboot to system. Happens on modified twrp also.
Hello. Is it possible to install the image contained in the ZIP file by ADB?
Sorry for my bad English
garbanzito said:
Hello. Is it possible to install the image contained in the ZIP file by ADB?
Sorry for my bad English
Click to expand...
Click to collapse
If your zip contains an image and a META-INF folder you can use adb sideload.
Cannot encrypt my phone properly when using this recovery.
Hey guys I'm familiar with flashing an .img via adb fastboot but how do you flash this recovery if you want to use the entire .zip? I pulled out the img and did it that way at first.
sting12345 said:
Hey guys I'm familiar with flashing an .img via adb fastboot but how do you flash this recovery if you want to use the entire .zip? I pulled out the img and did it that way at first.
Click to expand...
Click to collapse
The zip contains some recovery tools to be unpacked on TWRP folder that will be used by Batik so better is to flash the zip.
You can do it from two ways:
- If you already flashed the image, boot to Batik recovery and flash the zip placed inside your adb folder on pc using adb sideload.
- Or copy the zip to your main SDcard on your device and flash it through batik recovery.

Categories

Resources