Database Develop

[RECOVERIES][P31xx] TWRP | PhilZ Touch | CWM

Recovery Downloads​
Supported recoveries:
* TWRP
--------------------------------------------------------
* PhilZ-Touch-Recovery
CWM Base v6.0.5.1; Advanced Edition v6.59.x (discontinued)
--------------------------------------------------------
* CWM 6.0.5.1-Swipe (discontinued)
--------------------------------------------------------
Hey together!
You´ll find different Recoverys for P3100 and P3110/P3113 in this Thread
All latest Recovery´s can flash Android 4.4 (KitKat) Roms!
Enjoy!
1. Screenshots, general information, credits etc. (this post)
2. Information about the Recovery´s
3. Downloads
4. General FAQ & Developer FAQ & Recovery Changelog
​
Encryption - TWRP is a must have!​
Backup all important stuff! We need to format the device!
Make sure using latest TWRP
Wipe -> Advanced Wipe:
Cache
Dalvic
System
Data
Wipe -> Format Data -> Type yes to confirm
This is the most important step! It will keep some space for the footer! Without that encryption is not possible!
Flash Rom
Reboot
Set a Pin for Lockscreen
Encrypt your device
If done boot back in TWRP - TWRP will promt you to enter the PIN
If you haven't done Step 4 you'll get this error in logcat:
Code:
E/Cryptfs ( 105): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
Wipe->Format Data is the only method that fully recreates the file system and obeys the length needed for encryption!
TWRP
Thanks
@Dees_Troy and all the TWRP-Team for this great recovery
@ketut.kumajaya for his "android_kernel_samsung_espresso10" source
@CodyF86 for CM11 tree and his forked "android_kernel_samsung_espresso10" source; but i needed to switch to CM10.2
@gr8nole for helping me make internal SD visibile in TWRP, fix Touch-Orientation etc.
@ CyanogenMod-Team (thanks @codeworkx for supporting our device) for CM10.2 source
@ All testers: @antutu @philidor @zaid.oj @zeetherocker
PhilZ-Touch-Recovery (Advanced CWM)
Thanks @Phil3759 for his Advanced CWM
Main-Thread for PhilZ Touch Recovery: http://forum.xda-developers.com/showthread.php?t=2201860
ClockworkMod Recovery (CWM) Swipe-Edition
Thanks
@ketut.kumajaya for his "android_kernel_samsung_espresso10" source
@CodyF86 for CM11 tree and his forked "android_kernel_samsung_espresso10" source
@ CyanogenMod-Team (thanks @codeworkx for supporting our device) for CM10.2 source
XDA:DevDB Information
[P31xx] Recoveries: TWRP | PhilZ Touch | CWM, Tool/Utility for the Samsung Galaxy Tab 2
Contributors
Android-Andi
Version Information
Status: Stable
Created 2014-05-20
Last Updated 2015-08-03

All latest Recovery´s can flash KitKat-Roms without getting "Error: 7" like using older recoverys
TWRP
I builded this recovery from source, thanks to all who made this possible!
It wasn´t really easy - my flashcounter now > 20 But it´s working
How to flash a zip (it´s not laggy - it´s only because it´s recorded from screenshots ):
PhilZ-NON-Touch-Recovery (Advanced CWM)
CWM Base; Advanced Edition
Missing Features from PhilZ TOUCH:
all gui options, include touch code
name the backup folder with current ROM name
custom zip install menu (Free Browse Mode + custom startup folder)
Create Update.zip from current ROM or from pre-existing backups
misc nandroid settings menu (but /preload is included by default and I added option to toggle compression under backup format menu)
All Information about Features etc. in PhilZ Touch Main-Thread
On-Screen Navigation:
Swipe somewhere on your screen up / down to change selections
Swipe to right to enter
Swipe left to go back
How to flash a zip:
Same like CWM - you only have more features.
CWM
How to flash a zip (it´s not laggy - it´s only because it´s recorded from screenshots )
On-Screen Navigation:
Swipe somewhere on your screen up / down to change selections
Swipe to right to enter
Swipe left to go back

DOWNLOADS​
Please don´t mirror my files without my permissions!​
Recovery & ROM Downloads for all supported devices can be found here
Click to expand...
Click to collapse

FAQ​
GENERAL
1. I found a bug.
You can post all bugs in this Thread! Please tell us your Device and the File / Recovery (including Version number) you are using.
You can use your recovery to safe a recover.log on your device - you can post this log and me or other user will have a look on it.
Please give us detailed information - this meight speed up to fix it
2. I am getting "Error: 7" in recovery, what is wrong?
Be sure you flashed a Recovery for your device!
[For P3100 = P3100 Recovery ; P3110 = P3110 Recovery ; P3113 = Use P3110 Recovery(!)]
Be sure the file was made for your device!
Try the latest Version of Recovery for your device, maybe your recovery is to old!
For KitKat (Android 4.4):
All latest Recovery's posted here now can flash Android 4.4 Roms! You will get "Error: 7" if you use an older reovery!
Minimum: CWM 6.0.4.4 or TWRP 2.6.3.1 or PhilZ NON Touch 6.00.1 (Advanced CWM) - or use any newer Version if available for your device!
3. Why there is no Portrait Recovery?
ketut.kumajaya:
"(...) Samsung used the easiest way to rotate a landscape framebuffer device as a portrait device: rotate the touchscreen driver and then leave the surfaceflinger to rotate Android graphics. A framebuffer application (recovery, AROMA) still detect the framebuffer orientation as landscape. Back rotate the touchscreen orientation is much easier than rotate the framebuffer and LCD driver."
DEVELOPER
1. How to compile this recoverys from source?
You need to compile CWM first! It it works you can try building TWRP or Advanced CWM / PhilZ NON Touch recoverys!
2. How to compile cwm from source?
Follow the Guide on how to compile CyanogenMod from Source for P3110 - you need this setup!
(For p3100 replace "p3110" with "p3100")
Small changes to this Guide at the moment:
Replace
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
with init for CM10.2 source:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-[U][B]10.2[/B][/U]
Follow the Guide until you come to this:mentined
Code:
$ brunch p3110
to build recovery you need to enter this instead "brunch":
Code:
make clean && make -j# recoveryimage
(Replace the # with the core count +1, so if you have a dual core it's -j3 and a quad core becomes -j5, etc.)
If it finished compileing (if nothing goes wrong):
Code:
cd $OUT
You'll have your "recovery.img" inside it
You can flash it and see if it works!
3. I compiled a working CWM, how to compile PhilZ NON Touch from source?
Visit PhilZ Main-Thread and read the Developer Informations. You will find it here.
4 I compiled a working CWM and/or PhilZ NON Touch, how to compile TWRP from source?
You will find all informations here: [DEV]How to compile TWRP touch recovery
(You will maybe need to use https://github.com/TeamWin/Team-Win-Recovery-Project/tree/twrp2.7 as source instead the source from Omnirom)
Usefull links for Devs:
Unpacking and repacking recovery or boot image (LINUX!): http://www.imajeenyus.com/computer/20130301_android_tablet/android/unpack_repack_recovery_image.html
Complete Installation Guide for Android SDK on Ubuntu: http://askubuntu.com/questions/318246/complete-installation-guide-for-android-sdk-on-ubuntu
How to Install Oracle Java JDK on Ubuntu Linux: http://www.wikihow.com/Install-Oracle-Java-JDK-on-Ubuntu-Linux
More will be added later... i am thinking about it (what to add)
Click to expand...
Click to collapse
Recovery-Changelog
Changelog TWRP:
Code:
28.01.2014
2.6.3.4 --> 2.6.3.5
Backup-Fix:
"Clear the relative directory before passing on to twrpTar with the static du object.
Otherwise we will not backup /system/media etc"
23.01.2014
2.6.3.3 --> 2.6.3.4
Compiled on Omni´s Android 4.4.2 Source as base
support using old property system
USB Support
01.12.2013
2.6.3.2 --> 2.6.3.3:
Recovery Kernel updated from 3.0.96-Espresso10++ to 3.0.101-blackhawk
Fixed Bug(s):
Wrong touch orientation in AromaFM (only P311X)
Source changes:
using now https://github.com/kumajaya/android_kernel_samsung_espresso10
-------------------------
30.11.2013
2.6.3.1 --> 2.6.3.2:
Recovery Kernel updated from 3.0.31-CM-g010f848 to 3.0.96-Espresso10++
Source changes:
using now https://github.com/codyf86/android_kernel_samsung_espresso10/tree/cm-10.2
-------------------------
28.11.2013
2.6.3.1: Initial release
Base Source:
https://github.com/CyanogenMod -CM10.2 branch
Recovery: https://github.com/TeamWin/Team-Win-Recovery-Project/tree/twrp2.7
Changelog CWM Based Touch-Recovery from @Napstar
CWM Base v6.0.4.5
Code:
20.12.2013
Fix UI
---------------------
Initial Release 02.12.2013
Base Source:
https://github.com/CyanogenMod -CM10.2 branch
https://github.com/kumajaya/android_kernel_samsung_espresso10
https://github.com/Napstar-xda/android_bootable_recovery
Changelog PhilZ NON Touch Recovery / Advanced CWM:
Code:
24.01.2014
6.09.3 --> 6.10.6
inkl. Swipe Feature:
CWM Base v6.0.4.7;
Advanced Edition v6.10.6
(...)
10.12.2013
6.01.5 --> 6.02.1:
[COLOR="Red"]branch cm-10.2 dies here! (for Advanced CWM and PhilZ Touch)[/COLOR]
-------------------------
09.12.2013
6.00.5 --> 6.01.5:
Recovery Kernel updated to 3.0.101-blackhawk
Added Swipe-Feature
Source changes:
https://github.com/kumajaya/android_kernel_samsung_espresso10
-------------------------
6.00.1: Initial release
Base Source:
https://github.com/CyanogenMod -CM10.2 branch
Recovery: https://github.com/PhilZ-cwm6/philz_touch_cwm6
Changelog CWM / CWM-Swipe-Edition:
24.01.2014
6.0.4.7-Swipe Edition
(...)
Base Source:
https://github.com/Hellybean/android_bootable_recovery
Code:
03.12.2013
6.0.4.5-Swipe Edition
Base Source:
https://github.com/CyanogenMod -CM10.2 branch
-------------------------
6.0.4.5: taken from jenkins server (nightly 28.11.2013)

Added to Index Thread
--------Hit Thanks--------
--------------OR-------------
Visit Some Cool Guides Hmpshah Guides

Android-Andi said:
P3100
GT-P3100_ClockworkMod-Recovery_6.0.4.5_Non-Touch-UNOFFICIAL.zip
Odin flashable:
GT-P3100_ClockworkMod-Recovery_6.0.4.5-UNOFFICIAL.tar.md5
Click to expand...
Click to collapse
Same link for both files...

Fixed

One stop shopping - thank you!

TWRP Updated
Code:
Changelog:
2.6.3.1 --> 2.6.3.2:
Recovery Kernel updated from 3.0.31-CM-g010f848 to 3.0.96-Espresso10++
Source changes:
using now https://github.com/codyf86/android_kernel_samsung_espresso10/tree/cm-10.2

time to update my twrp
didn't find any issue which ever recoveries that you build :good:

Updated again... sorry guys
Changelog TWRP:
Code:
2.6.3.2 --> 2.6.3.3:
Recovery Kernel updated from 3.0.96-Espresso10++ to 3.0.101-blackhawk
Fixed Bug(s):
Wrong touch orientation in AromaFM (only P311X)

Hase someone seen this touch recovery before (i have compiled it for p3110 ):
{
"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"
}
https://github.com/Napstar-xda/android_bootable_recovery/tree/cm-10.2
maybe @Napstar can tell me how to fix the text on left side?

Android-Andi said:
Hase someone seen this touch recovery before (i have compiled it for p3110 ):
https://github.com/Napstar-xda/android_bootable_recovery/tree/cm-10.2
Click to expand...
Click to collapse
Looks interesting.

that´s what i thought

Here come something again...someday you will build your own recovery andi :highfive:
Hope that won't be to long

If someone want to test CWM based Touch recovery from @Napstar . I compiled it in the night from Source.
I hope you like it
GT-P3100_CWM-Based-Recovery.zip
GT-P3110_CWM-Based-Recovery.zip
Source: https://github.com/Napstar-xda/android_bootable_recovery/tree/cm-10.2
Bugs:
Left Buttens wrong placed, need to be fixed.
Any feedback wpuld be great:
How do you like it? Should i fix the bug? Do you like the recovery?

Special-Edition of CWM 6.0.4.5 will be available soon "Half-Touch"
CWM 6.0.4.5 Swipe-Edition
Swipe somewhere on your screen up / down to change selections
Swipe to right to enter
Swipe left to go back
Edit:
OP updated
Added Information, Changelog and Downloadlinks

3. Why there is no Portrait Recovery?
ketut.kumajaya:
"(...) Samsung used the easiest way to rotate a landscape framebuffer device as a portrait device: rotate the touchscreen driver and then leave the surfaceflinger to rotate Android graphics. A framebuffer application (recovery, AROMA) still detect the framebuffer orientation as landscape. Back rotate the touchscreen orientation is much easier than rotate the framebuffer and LCD driver."
If someone has a lot of time:
You can try makeing a portrait TWRP-Theme: http://teamw.in/project/twrp2themers

3. Why there is no Portrait Recovery?
ketut.kumajaya:
"(...) Samsung used the easiest way to rotate a landscape framebuffer device as a portrait device: rotate the touchscreen driver and then leave the surfaceflinger to rotate Android graphics. A framebuffer application (recovery, AROMA) still detect the framebuffer orientation as landscape. Back rotate the touchscreen orientation is much easier than rotate the framebuffer and LCD driver."
If someone has a lot of time:
You can try makeing a portrait TWRP-Theme: http://teamw.in/project/twrp2themers

I just tried TWRP 2.6.3.3... I'm not sure which buttons are moved or missing, but on some screens, the buttons are all spaced out. Specifically like the reboot one, it looks like 2 options are just not there or the screen was rearranged to have a few empty slots.

[ROM][UNOFFICIAL][STABLE] SlimKAT [4.4+][S4 mini] v9.0 FINAL | Updated 2015-01-20

SlimKAT for S4 mini (GT-I9190 + GT-I9195)​
{
"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"
}
SlimROMs is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimROMs team work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimKAT is the project name for SlimROMs based on Android 4.4+ and offers the following unique SlimROMs features :
FEATURES :
-> The real dark Slim : Invert the whole ROM including Gapps with one click.
-> Slim Recents : A complete replacement of the AOSP recents screen to allow better multitasking, along with marking favourite apps.
-> SlimPIE : Based on CM's PIE, inspired by PA's PIE with a light touch of Slim. A true community feature.
-> Slim dialer : A full replacement of the official Google closed source dialer with added features.
-> Privacy guard : Disable unnecessary permissions set by app developers.
-> Shake Events : Shake your device to launch apps or secure it on lockscreen.
-> Notification reminder : An easy way to quickly set short reminders to show on the notification drawer.
-> Notification drawer and and lockscreen shortcuts : Access your most important apps from everywhere.
-> Custom Quick Settings Tiles : Why just settings? Use whatever you want.
-> Camera : Discover SlimROMs team unique Camera feature...
DISCLAIMER : Every team mentioned below and myself or any contributor to this project will never ever be responsible for any damages you do to your device !
ALL CREDIT GOES TO AND ONLY TO :
-> SlimROMs team (ROM tree)
-> CyanogenMod team (device and kernel trees)
-> TheMuppets team (vendor tree)
-> SaberMod team (toolchains)
NOTE : I am not affiliated with any of the teams mentioned above...
THANKS TO :
-> @F4k (for sharing some of his knowledge with me...)
-> @JustArchi (build optimizations)
-> @aconger (screenshots)
INSTALLATION : To install this ROM on your Galaxy S4 mini 3G/LTE you'll need this checklist to be all checked
kitkat enabled custom recovery : regular / Philz CWM or TWRP...
My SlimKAT ROM file...
-> If you are coming from stock ROM please do a full wipe (cache/dalvik/system/data) from recovery before flashing it AFTER having done a FULL NANDROID BACKUP, thank you !
-> If you are coming from another AOSP ROM, you can flash it AFTER having wiped cache/dalvik...
OPTIONAL : You can use any AOSP GAPPs if you want to have Google Play services (I'm using PA-GAPPs nano-modular package by @TKruzze for example )
NOTE : SlimKAT is a KK 4.4+ ROM so if you want to activate ART instead of DALVIK, simply go to 'settings/developer options' and select ART as runtime :good: BUT please do remember that ART is still under heavy development...
DOWNLOADS :
=> This ROM is DEODEXED : if you want to ODEX it (better battery life and better system wide responsiveness), then i do recommend that you use @MatrixDJ96 ODEXER tool available HERE
TWRP Recovery
=> You will find my TWRP for S4 mini page over here...
SlimKAT ROM
=> STABLE version
SlimKAT for GT-I9190 Build 9.0 (2015-01-20)
SlimKAT for GT-I9195 Build 9.0 (2015-01-20)
=> TRYOUT version : none ATM !
Kernel updates : enhanced CM kernel built with latest SaberMod GCC 4.9 is available and is featuring O3 + graphite + Linux 3.4.106 (full details here...)
=> INFO : As i do not own a S4 mini anymore each upcoming update for both devices will be UNTESTED by myself...
-> In SlimKAT root access needs to be activated like this (true if installing for the first time...) : go to 'settings/developer options' and disable it, then go to 'settings/advanced settings/superuser' and set root access to 'apps/adb' (this will re-enable 'developer options' AND you will gain root access)
WARNING : Some information below is maybe obsolete !
NOTE : My SlimKAT ports for GT-I9190/5 ports include 'S4 mini settings' APK !
INFO 1 : CURRENT ROM FILES ARE ALSO AVAILABLE FROM THE DOWNLOADS TAB OF THIS PROJECT (at the top of this post).
INFO 2 : You will find screenshots of this running ROM file from the corresponding tab of this project too...
Happy flashing !​
CHANGELOG :​
2014-04-07 : RC1 -> INITIAL RELEASE​
=> Bluetooth is not working... it's a CyanogenMod device specific issue; if you want you can try to flash a custom kernel onto your phone after flashing my ROM file... it will maybe fix the BT issue... (choose any AOSP custom kernel suitable for the Galaxy S4 mini LTE...)​=> Auto rotation is failing too... i'm working on it ATM !​=> DPI is small ATM... value will be raised in next build ​
2014-04-09 : RC2​
=> DPI is fixed and set to 230 220 in the SlimKAT ROM .zip flashable file :good:​
2014-05-27 : RC3​
=> same ROM features (and failings...out of the box bluetooth is still not working at all !) as RC2, BUT...​=> ROM is compiled with 'Google GCC 4.8' and kernel with 'Official Linaro GCC 4.7' with straight @justarchi v2 optimizations applied ! (you can document yourself about it in his topic over here... special thanks to him for his great work :good:​=> In addition, RC3 is a 'user variant' build (ODEXED), not a 'userdebug variant' one (DEODEXED) like it was previously the case, with all 'slowing down debugging options' turned OFF...​=> RC3 is not compatible AT ALL with all previous releases; please perform a clean install... Thank you !​
2014-06-01 : RC4​
=> same ROM features as RC3, BUT...​=> bluetooth issue of my S4 mini SlimKAT ports is history ! :victory: :good: (BT is now fully working out of the box : therefore my SlimKAT BT fix is obsolete and is discontinued from now on; it is also the case for my 'S4 mini settings' flashable .zip -> post number 2 will soon be empty...​=> RC4 is not compatible AT ALL with all previous releases; please perform a clean install... Thank you !​
2014-06-10 : STABLE​
=> same ROM features as RC4 which was already stable, BUT in addition you will find...​=> Android 4.4.3 4.4.4 !​=> 'build.prop' file is fixed ! (from inside the ROM installers which are not signed anymore...)​=> F2FS support ! (latest CyanogenMod 11.0 kernel is officially F2FS enabled...) : therefore, you should be able to boot your device with embedded kernel, whatever the filesystem used (EXT4/F2FS) by tinkering my ROM installers a little bit...​=> APP2SD functionality ! (available from 'settings/apps' menu)​
NOTE : If you are interested in my work and download my files, please report back AND hit my 'THANKS!' button if you think i deserve it ! Thank you !
Have fun with it !​
XDA:DevDB Information
SlimKAT for S4 mini (3G/LTE) [UNOFFICIAL], ROM for the Samsung Galaxy S4 Mini
Contributors
ne0zone75, silesh.nair, spanish33
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Any kitkat enabled custom recovery
Based On: SlimKAT
Version Information
Status: Stable
Current Stable Version: STABLE
Stable Release Date: 2015-01-20
Current Beta Version: TRYOUT
Created 2014-04-07
Last Updated 2016-12-24

SlimKAT Power Packs for GT-I9195/0 + S4 mini settings for SlimKAT...
SlimKAT Power Packs​
I've re-packaged my original SlimKAT Power Packs for TF300T init.d scripts (Browser2RAM & ZipAlign) into two flashable .zip files to enhance user experience of SlimKAT on GT-I9195 , AdBlock is included and when flashing these packs, filesystem of your device is automatically tuned (see details below )
-> Basic Power Pack for GT-I9195/0 : contains AdBlock and Browser2RAM + ZipAlign scripts while ext4 filesystem tuning sets data journaling ON for /data but tunes /system and /cache too :good:
-> Enhanced Power Pack for GT-I9195/0 : it's contains and does exactly the same as the one above BUT it features GPU Tweaks : GPU 2D is forced AND software rendering is disabled !
The main purpose of the first pack is to safely improve the user experience on your device and to raise improper system shutdown tolerance, while the second one share the same purpose with maybe enhanced graphics performance :good:
PREREQUISITE : Please perform a full NANDROID backup from recovery before flashing it !
DISCLAIMER : I will never ever be responsible for any damages you do to your device !
ALL CREDIT GOES TO AND ONLY TO :
-> @hardslog (this pack is based on his one... thank you !)
-> me
INSTALLATION : Just flash it AFTER a full NANDROID backup, then just wipe cache/dalvik and reboot to system... You can use it with any kernel : embedded CM / f4ktion / etc...
DOWNLOADS :
-> SlimKAT Basic Power Pack for GT-I9195/0 (2014-04-21) | MD5
-> SlimKAT Enhanced Power Pack for GT-I9195/0 (2014-04-21) | MD5
Have fun with it...
NOTE : These packs have been tested by myself, you should safely flash it to your device... if anything goes wrong then restore your full NANDROID backup
INFO : THESE PACKS ARE ALSO AVAILABLE FROM THE DOWNLOADS TAB OF THIS PROJECT (at the top of this post)
PS : Thanks @kioshio for pointing a bug out in the initial release...
THE SECTION BELOW IS DISCONTINUED AND OBSOLETE !​
S4 mini settings for SlimKAT​
You will find below a Dev-Host download link for this SlimKAT re-compiled APK, packaged into a convenient .zip flashable file :victory:
I have tested it and it is working as expected... simply flash it and enjoy
DOWNLOADS :
-> S4 mini settings for SlimKAT (2014-04-30) | MD5
Have fun with SlimKAT

SlimKAT for GT-I9195/0 bluetooth fix released !
Reserved...

Nice ill try it
Sent from my GT-I9195 using XDA Premium 4 mobile app

imputazz said:
Nice ill try it
Sent from my GT-I9195 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hello and thank you for trying it out :good:

ROM works pretty good, but at first boot, the DPI was set on 220, so I've changed it to 230 and the ROM looks like a regular S4 Mini ROM now.
BTW, you as a developer, is there any chance to force kernel to send power to USB port? I mean USB OTG.

lipalok said:
ROM works pretty good,... ...BTW, you as a developer, is there any chance to force kernel to send power to USB port? I mean USB OTG.
Click to expand...
Click to collapse
Thank you ! I honestly do not know how to do this sadly... maybe you could ask for this feature into any GT-I9195 custom kernel thread
Have a nice day
Sent from my GT-I9195

How can anyone change dpi??

mobrol said:
How can anyone change dpi??
Click to expand...
Click to collapse
Hello, you'll find a mini HOWTO HERE...
Kind regards
EDIT : DPI will be adjusted in upcoming SlimKAT RC1 for GT-I9195 build 4.2 Thanks @lipalok for pointing this out :good:

Is halo implemented?

Flatric said:
Is halo implemented?
Click to expand...
Click to collapse
Hello, unfortunately no, it isn't... you'll find below corresponding official SlimKAT FAQ entry from SlimROMs official website
When are you/Are you going to add Halo?
Not before it is stable. It's currently not in a state that we can include it. And even when it becomes stable it's currently not something that we're considering including.
Click to expand...
Click to collapse

ne0zone75 said:
Hello, unfortunately no, it isn't... you'll find below corresponding official SlimKAT FAQ entry from SlimROMs official website
Click to expand...
Click to collapse
Ok, thanks for the fast answer

Sorry I just got the phone today.
This rom will not work with 9192? And will 9190 work? Or only 9192 ROMs for my phone?

Pangadaywalker said:
Sorry I just got the phone today.
This rom will not work with 9192? And will 9190 work? Or only 9192 ROMs for my phone?
Click to expand...
Click to collapse
Hello, my SlimKAT ROM file is dedicated to S4 mini LTE (GT-I9195) ATM, its embedded kernel fits ONLY this device... not S4 mini 3G (GT-I9190) or S4 mini dual (GT-I9192) sadly BUT i may add support to these 2 S4 mini variants someday
With that said, you can still try to flash it... it will certainly boot BUT you will lack device specific features like dual SIM support AND after SlimKAT ROM flashing you can try to flash a custom kernel from recovery that fits exactly your phone variant
Cheers
Sent from my GT-I9195

SlimKAT RC1 for GT-I9195 build 4.2 is out !
Dear SlimKAT users, i've just updated download links for current SlimKAT weekly build 4.2 by SlimROMs TEAM on both xda (downloads tab on this project) and Dev-Host :highfive: Simply checkout post number 1
Below you'll find build 4.2 changelog from SlimROMs official website :
Changelog:
SlimRecents fix 50ms unresponsiveness
Chamber of Secrets string edit
Chamber of Secrets add global database
Fix slow start for settigns/sound
Fix avrcp absolute volume
Do not show Home behind full screen activity
Fix Airplane mode on/off
Parallel shutdown
Great deal of fixes and optimizations for frameworks base
TWRP updated to 7.0+ (for devices with recovery in boot.zip)
Update busybox
Some updates to hardware_qcom_audio-caf
Some updates to frameworks_av
Click to expand...
Click to collapse
You can safely dirty flash it over initial build 4 release :good: (a full NANDROID backup from recovery is recommended though...)
NOTE : I still do not have fixed DPI but you can set it manually after flashing...
From a terminal with root access enabled simply follow these instructions in order to adjust DPI :
Code:
# mount -o rw,remount /system
Then with a text editor simply edit /sytem/build.prop file and search for this line : 'ro.sf.lcd_density=182' (without the quotes...) and please change 182 value to 220 like this 'ro.sf.lcd_density=220' then save the file and input this from the same termnal session started in previous step :
Code:
# mount -o ro,remount /system
...finally you just have to reboot and DPI will be fixed :victory:
Sorry for the inconvenience DPI will be correctly set in .zip flashable file i will release for upcoming SlimKAT RC1 for GT-I9195 weekly next week
Have fun with it

I am still checking what is valid for my phone and what is not. Unfortunately or fortunately I don't know there isn't much so I may stop for now with playing with ROM's. Will wait if 4.3 at least get to the 9192 I will be happy already.
Didn't even find a bloatware free ROM for 9192. I found only the trueclean but I didn't yet root my phone because of Knox stuff which I am not sure I should pay much attention since I never used the warranty of any phone we always replace it first.
I will see and keep reading of what comes out.
Another question I have since 9190 is the same for 9192 besides the dual chip and I do not use dual chip support, can I get 9190 and will it work perfectly withouth the dual sim support (which I don't actually needed it)?

Pangadaywalker said:
...Another question I have since 9190 is the same for 9192 besides the dual chip and I do not use dual chip support, can I get 9190 and will it work perfectly withouth the dual sim support (which I don't actually needed it)?
Click to expand...
Click to collapse
Hello, according to phoneArena.com website and AFAIK, GT-I9192 is the dual SIM slot version of the GT-I9190 aka Galaxy S4 mini 3G (serrano3gxx); i do know that GT-I9192 SOC is a Qualcomm Snapdragon 400 MSM8230 and GT-I9195 features a Qualcomm Snapdragon 400 MSM8930 as well as GT-I9190 (i think so because both GT-I9195 and GT-I9190 have the same 'msm8930-common' CyanogenMod kernel sources tree as a basis... only defconfig file differs !).
So if you own a GT-I9192 and put a GT-9190/GT-9195 custom ROM on it, it will fail because SOCs are not the same on GT-I9192 and GT-I9190/GT-I9195...
With that said if you want to install a custom ROM on your GT-I9192 you'll have to find a dedicated custom recovery and ROM because i'm afraid that CyanogenMod kernels for GT-I9190/GT-I9195 may be incompatible with GT-I9192 but i'm not sure about this sadly...
Best regards

Where did you read that the 9192 uses MSM8230?

Whosat said:
Where did you read that the 9192 uses MSM8230?
Click to expand...
Click to collapse
Just over here at phoneArena.com (GT-I9192 specs are at the bottom of the page...)
Samsung Galaxy S4 mini Dual I9192 (With Dual SIM support)
Differences:
Weight: 3.81 oz (108 g) the average is 4.8 oz (137 g)
System chip: Qualcomm Snapdragon 400 MSM8230
UMTS: 850, 900, 1900, 2100 MHz
Data: HSDPA+ (4G) 21.1 Mbit/s, UMTS, EDGE, GPRS
Multiple SIM cards: 2 slots
Click to expand...
Click to collapse
...of course it may not be accurate...

Nice work on the Rom, but am I missing something or is there no theme support.
Sent from my GT-I9195 using Tapatalk

[ROM]★[TF701 LP 5.1.1][ZOMBi-POP OMNI KANG RC1][AUG 29]★

{
"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"
}
YOU MUST BE ON THE ASUS STOCK KK 4.4.2 BOOTLOADER VERSION 11.4.1.27+ AND TWRP 2.8.6.3+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE
You must do a full wipe in TWRP if coming from another ROM. Do not do a full wipe from the bootloader. Don't forget to do a Nandroid Backup first and give the ROM 15 mins to stabilise! The first boot will take 5 to 10 minutes!
Features and Tweaks
This ROM is based from OMNI AOSP sources
Supports EXT4 Data partitions
Based off omni-5.1.1-20150823_zombi_tf701t-KANG source by lj50036/hardslog/sbdags
Full Aroma Installer for main rom including choice of 4 kernels
Remixed Asus kernel with OMNI ramdisk - repacked by sbdags
Omni Kernel by lj50036/sbdags
Extreme Modded Omni Kernel by sbdags
CM12 kernel with OMNI ramdisk by pershoot/sbdags
DPI Size: 280 (TF701 recommended small fonts), 320 (Stock fonts), 300 (Medium fonts) & 260 (Small fonts), 240 (Tiny fonts)
Launchers: Omni, Google Experience Launcher, Apex , Nova
Boot Animations: ZOMBi-POP, Android-L, Nexus Flow, Unknown Pleasures
Gapps based on Banks' Gapps (updated by me to Google latest apks and libs)
Misc Apps: ESFile Explorer, Adobe Flash, AdAway
Tweaks: File system and performance optimised, Init.d support, Zip Align, Force GPU Rendering, Browser2RAM
Continued Best Support of any ROM!
Warning - experimental tweaks
[*]Option disable data journaling on /data during install - CAN CAN CAUSE DATA LOSS IF SUDDEN SHUTDOWN OR CRASH
[*]Option disable fsync during install - CAN CAN CAUSE DATA LOSS IF SUDDEN SHUTDOWN OR CRASH
[*]Tip 1: Go to Settings - About Tablet, Click build number 7 times
Now you will see Developer Settings & Performance menus
[*]Tip 2: In Developer Settings - Set Animation and Transitions to 0.5 or 0 for extra free speed!
[*]Tip 3: In Performance Settings - Set CPU max and min speed and I/O scheduler to noop
Bug List
[*]No Floating windows yet
[*]Aroma gets stuck sometimes - hit volume up if so to force it to continue
Change Log
Don't forget full wipe to install this please! No excuses!
20150829 ZOMBi-POP 5.1.1 RC1 changes
- Re-based from omni-5.1.1-20150823-zombi_tf701t-KANG maintained by lj50036, hardslog, sbdags
- Fixed missing ZOMBi Tweaks that bring performance back
- New OMNI kernel - thanks lj50036
- Includes the stagefright security fix
- Added dock battery option to installer
- Removed GPU efl.cfg tweaks as no longer in source - thanks lj50036
- Updated to latest Banks Gapps base package (may require google playstore and play framework data wipe)
- Updated Google Maps to version 9.13.0
- Updated Google Search to version 5.1.17.19
- Updated Google Music to version 6.0.1951S
- Updated Google Mail to version 5.5.101116392
- Updated Google Hangouts to version 4.0
- Updated YouTube to version 10.31.55
- Previously saved installer options will be reset on first install due to changes
20150727 ZOMBi-POP 5.1.1 Beta 4 changes
- Re-based from omni-5.1.1-20150726-zombi_tf701t-KANG maintained by lj50036, hardslog, sbdags
- Added dock battery icon as a additional flash zip
- Fixed partitions not getting unmounted correctly for tuning during installation
- OmniSwitch now working - thanks hardslog
- Tidied up some installer messages
- Amended SuperSU installer script to give correct permissions and install locations
- Google play services updated to multi-dpi version
- Updated Google Maps to version 9.12.0
- Updated Google TTS to version 3.5.6
- Updated Google Calendar to version 5.2.2-98195638
- Updated YouTube to version 10.28.59
- Updated Apex Launcher to version 3.1.0
- Updated ESFile Explorer to version 3.2.5.5
- Updated Nova Launcher to version 4.0.2
20150615 ZOMBi-POP 5.1.1 Beta 3 changes
- Re-based from omni-5.1.1-20150613-zombi_tf701t-KANG maintained by lj50036, hardslog, sbdags
- Installer script now cleans up /data if you do not opt to install gapps for compatibility reasons
20150614 ZOMBi-POP 5.1.1 Beta 2 changes
- Re-compiled Omni kernel with changes to init.macaln.rc and fstab.macallan with only 2 usb mounts
- Still shows 9 USB Mounts in settings
- Switched back to BANKS GAPPS package
- Updated Google Search, Calendar, Hangouts to the latest versions
20150606 ZOMBi-POP 5.1.1 Beta 1 changes
- Re-based from omni-5.1.1-20150605-zombi_tf701t-KANG maintained by lj50036, hardslog
- Created the Extreme Omni Kernel with performance tweaks - possibly unstable
- Basic and Extra Tweaks do not get installed for the Extreme Kernal as it has its own version
- Removed script to to remove RES init.d script when at default 2560x1600 resolution
- Added ZOMBi-POP tweaks to init.d that get installed for all kernels
20150605 ZOMBi-POP 5.1.1 Alpha 4 changes
- Based from omni-5.1.1-20150604-zombi_tf701t-KANG maintained by lj50036, hardslog
20150604 ZOMBi-POP 5.1.1 Alpha 3 changes
- Audio fixed - thanks to pershoot for source and _that and lj50036 for helping to diagnose
- Youtube fixed - thanks to lj50036
20150603 ZOMBi-POP 5.1.1 Alpha 2 changes
- Based from omni-5.1.1-20150601-zombi_tf701t-KANG maintained by lj50036, hardslog
- Repacked Asus Stock 4.4.2 kernel with the zombi ramdisk
- Repacked CM12 kernel with the zombi ramdisk
20150601 ZOMBi-POP 5.1.1 Alpha 1 changes
- Based from omni-5.1.1-20150530-zombi_tf701t-KANG maintained by lj50036, hardslog
- Initial release - omni zombified after source build
- Added SuperSU and su binary for root capability
- Added all the ZOMBi/CROMi-X goodness to the base rom
- Aroma tuned for ZOMBi-POP
Click to expand...
Click to collapse
The Team
@sbdags - Creative Mastermind (From CROMi-X/CROMBi-kk/ZOMBi-X ROMS)
@lj50036 - Source Guy (From CROMBi-kk/ZOMBI-X ROMS)
@hardslog - The Canadian (From Grimlock ROMS)
@ikkeT - The Fin
Credits
pershoot for maintaining the CM12 source and his advice and fixes! Thanks man!
Google
Omni Team - Thanks!
@_that For all the great advice, watching over us and fixing everything we break!!!!!
All the beta testers for your patience and feedback : @berndblb, @gav2fc, @dape16, @dragon_rckr, @glor
To Do
Fix loads of stuff!
XDA:DevDB Information
ZOMBi-POP, ROM for the Asus Transformer TF701
Contributors
sbdags, lj50036, hardslog, _that, ikkeT
Source Code: https://github.com/zombi-x
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
ROM Firmware Required: 11.4.1.27 - 30 bootloader
Based On: OMNI AOSP
Version Information
Status: Stable
Current Stable Version: 20150829 RC1
Stable Release Date: 2015-08-29
Current Beta Version: 20150727 5.1.1 Beta
Beta Release Date: 2015-07-27
Created 2015-06-15
Last Updated 2015-08-29

DOWNLOADS
UPGRADE INSTRUCTIONS
Steps
1. Please Unlock using the Asus Unlock Tool first found here.
Note installing and running this app will wipe your device and void your warranty.
2. Install the latest version of Team Win Recovery Project (TWRP) 2.8+ or ClockWorkMod Recovery 6.0.5.0+ Note this ROM will NOT install with older versions of recovery!
TWRP XDA Thread
[email protected]
You can now access the recovery by pushing [volume up] on the RCK icon in the bootloader screen
FLASHING THE ROM FROM RECOVERY
Steps
1. Download the ROM below and save to your internal or external SD Card. Do not unzip the file.
ZOMBi-POP ROM DOWNLOAD
Note: The first boot after install will take 10 mins whilst everything is built. Some people might think it is looping but it is not. The ROM also takes about 10 mins to stabilise after the first boot
ZOMBi-POP 5.1.1 RC1 20150829 Full Mirror 1
ZOMBi-POP 5.1.1 RC1 20150829 Full Mirror 2
MD5 Sum: d291e2ff8ea5d82504ed46378ea1790c
FILES ARE SIGNED. IF YOU ENABLE SIGNATURE VERIFICATION IN RECOVERY IT WILL VALIDATE THE FILE BEFORE FLASHING.
2. Flash the zip files and reboot after - enjoy your new rom.
Do not forget to wipe data first in recovery if you are coming from another rom or installing this for the first time.

MINE
mine

I will do the download post tomorrow but it will be available in the download tab of this thread in about 10 minutes
Enjoy!

Thank you for this ROM!
Before I attempt to install it, I have a question: will the Aroma installer allow me to avoid installing most of the Google apps? Ideally, I'd like the ROM to be installed with no more apps than I would get with a "micro" or even "pico" version of gapps.
.​

HippoMan said:
Forgive me if I'm overlooking something obvious, but I don't see a "download" tab. Is it on a different web page, perhaps?
Click to expand...
Click to collapse
Top of the page in the black bar ....
Says 'Downloads'
Thx Josh

lj50036 said:
Top of the page in the black bar ....
Says 'Downloads'
Thx Josh
Click to expand...
Click to collapse
Yes, I finally found it. Thank you very much.
.​

Flashed, trying it out now

sbdags said:
...
Aroma gets stuck sometimes - hit volume up if so to force it to continue
Click to expand...
Click to collapse
Aroma got stuck for me on the screen for selecting experimental features, but hitting volume up had no effect. It remained stuck.
No other key interactions worked, either, except to reboot.
Any ideas?
.​
---------- Post added at 23:27 ---------- Previous post was at 23:10 ----------
Well, I redid the entire flash procedure, and this time, it worked.
.​

HippoMan said:
Aroma got stuck for me on the screen for selecting experimental features, but hitting volume up had no effect. It remained stuck.
No other key interactions worked, either, except to reboot.
Any ideas?
.​
---------- Post added at 23:27 ---------- Previous post was at 23:10 ----------
Well, I redid the entire flash procedure, and this time, it worked.
.​
Click to expand...
Click to collapse
+1. Ok now.

Took the beta 1 and 2 from androidfilehost (just need to know where to look ). It also happend to me that the installation would sometimes hang or even reboot the recovery (TWRP). With beta 2 i needed three tries. For the rest: very good as always!!

I think that omni roms don't allow immersive mode like cm does. In CM 12.1 I hide the navigation bar to get some extra screen space and I control the tablet via LMT pie menus and gestures. Is there a way to do the same in omni?

HippoMan said:
Aroma got stuck for me on the screen for selecting experimental features, but hitting volume up had no effect. It remained stuck.
No other key interactions worked, either, except to reboot.
Any ideas?
.​
---------- Post added at 23:27 ---------- Previous post was at 23:10 ----------
Well, I redid the entire flash procedure, and this time, it worked.
.​
Click to expand...
Click to collapse
toolmanz said:
+1. Ok now.
Click to expand...
Click to collapse
doom_71 said:
Took the beta 1 and 2 from androidfilehost (just need to know where to look ). It also happend to me that the installation would sometimes hang or even reboot the recovery (TWRP). With beta 2 i needed three tries. For the rest: very good as always!!
Click to expand...
Click to collapse
ariadnejro said:
I think that omni roms don't allow immersive mode like cm does. In CM 12.1 I hide the navigation bar to get some extra screen space and I control the tablet via LMT pie menus and gestures. Is there a way to do the same in omni?
Click to expand...
Click to collapse
Yes Aroma is a bit dodgy on the device - sometimes it hard locks and all you can do is try again - however this was here before we had touch. Not much I can do about it. The latest aroma builds don't even support our device so we are stuck for now.
As for CM12 stuff - nope it's omni but it soes have omni switch which will eventually allow full screen - but you never know what will be developed in the future. It is kept light for a reason - so it is fast and smooth.

The ROM is running very fast and all seems good except for 1 program I like.
I have a very robust infrastructure in the house and I use an app call SmartWIFIAnalyser.
It will automatically switch to the best WIFI signal as I move around the house.
When I start it - the tablet barfs and returns to the bootup screen (wavy lines) - once it returns from losing its mind, it will slowly get back to normal.
This isn't a deal killer - but it works on Zombie-Pop on my TF700 ??
I tried to grab a logcat and I have provided a link to it .... hope I did this right!
http://d.pr/f/1kqpW

toolmanz said:
The ROM is running very fast and all seems good except for 1 program I like.
I have a very robust infrastructure in the house and I use an app call SmartWIFIAnalyser.
It will automatically switch to the best WIFI signal as I move around the house.
When I start it - the tablet barfs and returns to the bootup screen (wavy lines) - once it returns from losing its mind, it will slowly get back to normal.
This isn't a deal killer - but it works on Zombie-Pop on my TF700 ??
I tried to grab a logcat and I have provided a link to it .... hope I did this right!
http://d.pr/f/1kqpW
Click to expand...
Click to collapse
Seems to be a failure with the renderer. Can you reinstall the ROM but don't install the GPU tweaks on the tweaks page and try again for me please.
Thanks!
Code:
E/BufferQueueProducer( 418): [StatusBar] connect(P): BufferQueue has been abandoned
E/libEGL ( 1730): eglCreateWindowSurface: native_window_api_connect (win=0xb498b108) failed (0xffffffed) (already connected to another API?)
E/libEGL ( 1730): eglCreateWindowSurface:423 error 3003 (EGL_BAD_ALLOC)
F/OpenGLRenderer( 1730): Failed to create EGLSurface for window 0xb498b108, eglErr = EGL_BAD_ALLOC
F/libc ( 1730): Fatal signal 6 (SIGABRT), code -6 in tid 2771 (RenderThread)

sbdags said:
Seems to be a failure with the renderer. Can you reinstall the ROM but don't install the GPU tweaks on the tweaks page and try again for me please.
Thanks!
Code:
E/BufferQueueProducer( 418): [StatusBar] connect(P): BufferQueue has been abandoned
E/libEGL ( 1730): eglCreateWindowSurface: native_window_api_connect (win=0xb498b108) failed (0xffffffed) (already connected to another API?)
E/libEGL ( 1730): eglCreateWindowSurface:423 error 3003 (EGL_BAD_ALLOC)
F/OpenGLRenderer( 1730): Failed to create EGLSurface for window 0xb498b108, eglErr = EGL_BAD_ALLOC
F/libc ( 1730): Fatal signal 6 (SIGABRT), code -6 in tid 2771 (RenderThread)
Click to expand...
Click to collapse
Bingo! It now works but once I enable it and come back out to the home screen it is super small on large screen. There has been some other weirdness with the screen like the drawer shows really large icons (2 to a page ??? ). But nothing I can't handle - ESC out of the screen and go right back in and its working.
Cheers and thanks for another great ROM!

toolmanz said:
Bingo! It now works but once I enable it and come back out to the home screen it is super small on large screen. There has been some other weirdness with the screen like the drawer shows really large icons (2 to a page ??? ). But nothing I can't handle - ESC out of the screen and go right back in and its working.
Cheers and thanks for another great ROM!
Click to expand...
Click to collapse
I need a screen-shot of that .....
Thx Josh

lj50036 said:
I need a screen-shot of that .....
Thx Josh
Click to expand...
Click to collapse
Can't seem to get it to do that again ..... Now when I come back to the home page its blank. Hit ESC a couple of times and it comes back normal. ???
Maybe same problem - with different symptoms ... ?
I will gab screen shots if it happens again.
Cheers
---------- Post added at 02:02 PM ---------- Previous post was at 01:39 PM ----------
Ok. Went into the store and found there was an update to the launcher I use - KK Launcher Prime. I did the update and came back to the home screen - normal.
When I went into the drawer it did it again and have attached the screen shots. They are really faint but you can see 3 icons only. Esc back out and go back in and it's working ???
Thinking maybe its the launcher at fault
Link below.
http://d.pr/f/1gdhS
Cheers

toolmanz said:
Can't seem to get it to do that again ..... Now when I come back to the home page its blank. Hit ESC a couple of times and it comes back normal. ???
Maybe same problem - with different symptoms ...
I will gab screen shots if it happens again.
Cheers
---------- Post added at 02:02 PM ---------- Previous post was at 01:39 PM ----------
Ok. Went into the store and found there was an update to the launcher I use - KK Launcher Prime. I did the update and came back to the home screen - normal.
When I went into the drawer it did it again and have attached the screen shots. They are really faint but you can see 3 icons only. Esc back out and go back in and it's working ???
Thinking maybe its the launcher at fault
Link below.
http://d.pr/f/1gdhS
Cheers
Click to expand...
Click to collapse
Well that is odd indeed ...
Can you set a diff wallpaper and see what that does .....
Thx Josh

lj50036 said:
Well that is odd indeed ...
Can you set a diff wallpaper and see what that does .....
Thx Josh
Click to expand...
Click to collapse
Well I am using 500 Firepaper now and it still does it. Go figure. It must be the launcher. ?

[DISCONTINUED][UNOFFICIAL] CM-12.1 [22 Nov 2016]

IMPORTANT NOTICE​:
As many of you know, the CM-12.1 branch will not be supported in the new LineageOS fork. And many of the new Google security patches are difficult and fiddly to back-port as they are now geared towards Marshmallow and Nougat. So as a result there will be no further updates to this rom.
Instead my focus will now be Fire Nexus ROM for this device.
Also looking at possible ways to get later android versions on the device. Will let you know if there is any progress later.
Thanks for all the support :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"
}
Code:
[COLOR="gray"]
/*
* 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 the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
[/COLOR]
Current Progress
updated: 25 Jan 2016
Rules
- Please search the thread before asking questions
- Please try to stay on topic, I know it's not always possible
- Please report bugs here
- Report only one issue per bug report
- When reporting bugs please post a logcat and/or dmesg containing pertinent information regarding the issue...
- Saying something isn't working without proper explanation will not attract any attention.
Prerequisites for Installation
- If you have FireOS 5.0.1 then use Cyanogen Recovery or TWRP Image
- If you have FireOS >= 5.1.1 then use FlashFire 0.50
Fresh Installation from TWRP
- From your recovery perform a Factory Reset
- Flash the ROM File
- Flash Open Gapps - Use either micro, pico or nano
- Do NOT use stock gapps as there is not enough space on the /system partition
- Reboot and enjoy!
- Fresh Installation from FlashFire 0.50
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Cyanogenmod Zip
- Accept defaults
- Click the Red + button again and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Open Gapps Zip.
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
Upgrading from FlashFire 0.50
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Cyanogenmod Zip
- Click the Red + button again and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Open Gapps Zip.
- Accept defaults
- Click the Red + again and choose 'Wipe'
- ONLY tick Dalvik and Cache.
- Press the big FLASH button.
Downloads
*** Please do NOT create any mirrors ***
- CM-12.1 for Amazon Fire 7" 2015 Tablet
- Open Gapps
Source Code
- Device Tree
- Kernel Source: Ford stock kernel, build number update-kindle-global-37.5.6.0_user_560177220
Thanks
- Cyanogenmod
- csolanol
- diegocr
- k4y0z
XDA:DevDB Information
CM-12.1 Amazon Fire 2015, ROM for the Amazon Fire
Contributors
ggow
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Based On: Cyanogenmod
Version Information
Status: Stable
Created 2015-11-15
Last Updated 2017-02-03

Release Notes / Changelog
2016-11-22
- Fix Xposed - Needs testing
2016-11-21
- November 2016 AOSP Security Patch Level
- Switch to using lastest FireOS 5.3.2 - update-kindle-global-37.5.6.0_user_560177220 binaries and boot.img
- Fix Video Recorder bug [Cannot connect to camera]
- Fix bug in OMX causing freeze of video
2016-10-21
- October 2016 AOSP Security Patch Level
- Fix x265 video playback - Thanks @jeromeof
2016-09-22
- September 2016 AOSP Security Patch Level
2016-08-10
- August 2016 AOSP Security Patch Level
- Fix audio lag issue in games - thanks @$ideWinder
2016-07-10
- July 2016 AOSP Security Patch Level
- Re-tested exFAT with 32GB Sandisk microsd card and seems to work fine.
2016-06-14
- June 2016 AOSP Security Patch Level
- Added CIFS Support (Instructions here)
- Switch to using lastest update-kindle-37.5.4.4_user_544271020 binaries and boot.img
2016-05-30
- Fix Swipe for stock keyboard
- Added back fix for screen rotation glitch
2016-05-28
- May 2016 AOSP Security Patch Level
- Fixed bug: No way back from USB Charge Only Mode
2016-04-20
- Updated CM Code
2016-04-11
- Fix sdcard write access
2016-04-06
- Updated CM Code
- 01 April 2016 AOSP Security Patch Level
2016-04-04
- Updated CM Code
- Prevent recovery been overwritten: Modify build system to prevent recovery-resource.dat and recovery-from-boot.p from been generated. This needs testing preferably by people with the ability to boot TWRP.
- Fixed failure to mount /system partition error due to change in build system
2016-03-30
- Enable Bluetooth Low Energy Support
2016-03-29
- Updated CM Code
- Switch to using lastest update-kindle-global-37.5.4.2_user_542168620 binaries and boot.img
2016-03-11
- Updated CM Code
- 01 March 2016 AOSP Security Patch Level
- Updated FlashFire Flashing instructions on OP
2016-02-29
2016-02-19
- Updated CM Code
2016-02-03
- Updated CM Code
- 01 February 2016 AOSP Security Patch Level
2016-01-26
2016-01-20
2016-01-12
- Updated CM Code
2016-01-04
- Enable WiFi Display
2015-12-30-R01
- Fixed bug where FlashFire will fail to go from FireOS -> CM
2015-12-30
- Thanks to @chetta for testing and prompt feedback
- Reverted use of Google's prebuilt WebView for now (Too many issues)
- Clean Flash via TWRP Re-tested
- Google App Tested
- YouTube and NetFlix Re-tested
- Upgrade via TWRP re-tested
- FlashFire FireOS -> CM re-tested
2015-12-29-PM
- Fixed issue with GAPPS and SuperSU been overwritten on upgrade of ROM
2015-12-29-AM
- Fixed bug when using FlashFire where Gapps would not be preserved
- Use Google's Prebuilt WebView
- Update WebView to version 48.0.2564.48
- Updated CM code on 2015-12-29
- Re-tested ROM upgrade via TWRP, CM recovery and FlashFire
- Fixed Flash failure going from FireOS 5.1.1 -> CM
- Re-tested FlashFire functionality going from FireOS 5.1.1 -> CM
2015-12-23
- Fixed ability to use FlashFire to go from FireOS_5.1.1 to CM-12.1
- BLOCK_BASED_OTA is now enabled
- Updated CM code on 2015-12-22
2015-12-16
- Fixed screen-off animation rotation orientation
- Updated CM code
2015-12-11
- Fixed permissions on /system/etc/install-recovery-2.sh
- Implement fix for Play Video - thanks @diegocr
2015-12-10-PM
- Switch to using update-kindle-full_ford-37.5.4.1_user_541112720 binaries and boot.img
- New version of the selinux_permissive.ko module - thanks @k4y0z
- Added /system/etc/install-recovery-2.sh with the same content as /system/bin/install-recovery.sh
- Fixed Built-In Root Access (Privacy Guard)
2015-12-10-AM
- Fix problem with install-recovery.sh been overwritten
- exFAT should now work (was broken in the previous build)
- init.d now initialises correctly
- Enabled built in Root Access
- NuPlayer should now work correctly
- Fixed Camera Support (HDR mode is not working and not supported)
- Fixed Video Recording
- General Video Support should be good now
- I tested Netflix and YouTube
2015-12-09
- Switch to using update-kindle-37.5.2.2_user_522054520 binaries and boot.img
- Add kernel module to switch selinux operational mode to permissive - thanks @k4y0z
- This means SuperSU is now not required and much faster boot times
- Add exfat support
- Enable init.d support - thanks @k4y0z
- Remove GPS configs
- Removed NFC configs
- Removed GPS, telephony and NFC permission files
- Add further properties to disable some SIM/RIL related stuff
2015-12-04
- Fixed USB OTG - thanks @csolanol and @diegocr
- Updated CM Code
2015-12-02
- Fixed Bluetooth Audio
- Updated CM Code
2015-12-01
- Fixed Bluetooth - thanks @diegocr
- Enable Multi-user (5)
- Updated CM Code
2015-11-22
- Enable MTP
- Enable OTG Support
- Add properties to declare device has no radio
- Added configuration item to build for BLOCK_BASED or not.
- BLOCK_BASED build currently not flashing due to symlink error
- Add further config for MTK Bluetooth
- Fixed build errors in lib_driver_cmd_mt66xx private static lib
- Clean up config for WIFI
- Added IPv6 support
- Fixed battery stats - thanks @csolanol for providing the required power_profile.xml
2015/11/16
- This version will boot standalone - no more tethered boot
2015/11/15
- Initial Release

Frequency Asked Questions
Question 1:
How do I adjust the keyboard sound level?
Answer:
- Go to settings -> Languages & input -> Android Keyboard -> Advanced -> Keypress sound volume
- Then adjust the slider to your preferred level
Question 2:
Why does the screen image seem stretched or distorted?
Answer:
- The actual pixels in the Fire's LCD are not perfectly square
- That causes some distortion. It is particularly noticeable with round icons & when the screen rotates.
- This issue also effects the stock amazon OS as well as all custom roms.
- It is not yet known if this will be fixable in software (my current thinking is probably not)
Question 3:
Why is my brightness slider not working?
Answer:
- Try installing Brightness Level and use it to change brightness. After doing this brightness slider should work fine and you can remove Brightness Level.
Question 4:
When installing Google Play Games and Google Calendar I get error -505?
Answer:
- Install older versions from apkmirror then update from Google Play Store.
Question 5:
How do I use CIFS?
Answer:
See the guide here

Actual CM12.1 on the Fire 2015? So, a premium device for $50 with CM12.1? Awesome! Might have to pick one up now... I'd guess I don't have to fastboot each time I power on right? Just the first time to get CM/TWRP, then have CM/TWRP install+boot CM12.1, then I can get CM12.1 without fastboot?

bobbob1016 said:
Actual CM12.1 on the Fire 2015? So, a premium device for $50 with CM12.1? Awesome! Might have to pick one up now... I'd guess I don't have to fastboot each time I power on right? Just the first time to get CM/TWRP, then have CM/TWRP install+boot CM12.1, then I can get CM12.1 without fastboot?
Click to expand...
Click to collapse
- You will have to fastboot each time
- It's all in the OP including the reasons why this is the case at the moment.
- It's not ideal - but thought I would share what I have so far
- I am looking into solutions for this now.

- Links are now up

ggow said:
- You will have to fastboot each time
- It's all in the OP including the reasons why this is the case at the moment.
- It's not ideal - but thought I would share what I have so far
- I am looking into solutions for this now.
Click to expand...
Click to collapse
Thanks for the hard work!

Once booted into CM12.1 we can make general system configuration changes, install apps, etc, correct? And will changes be be retained if we need to reboot (through fastboot)? If so, where will CM12.1 files be stored?

blueberry.sky said:
Once booted into CM12.1 we can make general system configuration changes, install apps, etc, correct? And will changes be be retained if we need to reboot (through fastboot)? If so, where will CM12.1 files be stored?
Click to expand...
Click to collapse
- Yes customise as much as you want - all will be retained.
- Your data and OS is stored on the /data and /system partition respectively
- The only thing you have to reload on a reboot through fastboot is the modified_boot.img which won't affect anything else.

Awesome work @ggow!. @diegocr and me have been working on bring slimrom to this device. We are having some issues with WiFi and bluetooth. Would you mind to share your device and vendor for cyanogen?.
Thanks.

csolanol said:
Awesome work @ggow!. @diegocr and me have been working on bring slimrom to this device. We are having some issues with WiFi and bluetooth. Would you mind to share your device and vendor for cyanogen?.
Thanks.
Click to expand...
Click to collapse
Hi csolanol,
- I am in the process of updating my bibucket with the most recent changes
- Having trouble with bluetooth too.
- Wifi is working fine - I got it working like this:
- put this in your device tree
- then add this to your boardconfig.mk:
Code:
[INDENT]WPA_SUPPLICANT_VERSION := VER_0_8_X
BOARD_WPA_SUPPLICANT_DRIVER := NL80211
BOARD_HOSTAPD_DRIVER := NL80211
BOARD_WLAN_DEVICE := mediatek
BOARD_WPA_SUPPLICANT_PRIVATE_LIB := lib_driver_cmd_mt66xx
BOARD_HOSTAPD_PRIVATE_LIB := lib_driver_cmd_mt66xx
WIFI_DRIVER_FW_PATH_PARAM:="/dev/wmtWifi"
WIFI_DRIVER_FW_PATH_STA:=STA
WIFI_DRIVER_FW_PATH_AP:=AP
WIFI_DRIVER_FW_PATH_STA:=P2P[/INDENT]
- Then add this to your device.mk or equivalent
Code:
[INDENT]# wifi
PRODUCT_PACKAGES += \
lib_driver_cmd_mtk[/INDENT]
- Do not include the propriertary bin/wpa_supplicant when building otherwise you will get a build error
- Instead copy it into your ROM after building.
- Hope this helps for now.

Didnt whats his face say he used the original boot.img file to flash permenatnly asop without using fastboot every time?

ggow said:
Hi csolanol,
- I am in the process of updating my bibucket with the most recent changes
- Having trouble with bluetooth too.
- Wifi is working fine - I got it working like this:
- put this in your device tree
- then add this to your boardconfig.mk:
Code:
[INDENT]WPA_SUPPLICANT_VERSION := VER_0_8_X
BOARD_WPA_SUPPLICANT_DRIVER := NL80211
BOARD_HOSTAPD_DRIVER := NL80211
BOARD_WLAN_DEVICE := mediatek
BOARD_WPA_SUPPLICANT_PRIVATE_LIB := lib_driver_cmd_mt66xx
BOARD_HOSTAPD_PRIVATE_LIB := lib_driver_cmd_mt66xx
WIFI_DRIVER_FW_PATH_PARAM:="/dev/wmtWifi"
WIFI_DRIVER_FW_PATH_STA:=STA
WIFI_DRIVER_FW_PATH_AP:=AP
WIFI_DRIVER_FW_PATH_STA:=P2P[/INDENT]
- Then add this to your device.mk or equivalent
Code:
[INDENT]# wifi
PRODUCT_PACKAGES += \
lib_driver_cmd_mtk[/INDENT]
- Do not include the propriertary bin/wpa_supplicant when building otherwise you will get a build error
- Instead copy it into your ROM after building.
- Hope this helps for now.
Click to expand...
Click to collapse
Thanks, I will wait bitbucket update :good:

Awesomeslayerg said:
Didnt whats his face say he used the original boot.img file to flash permenatnly asop without using fastboot every time?
Click to expand...
Click to collapse
- Yes, that was me who said that but Amazon have changed things since then.
- On the HDX at the time they were not enforcing an selinux policy
- Now that Amazon are enforcing it cannot work in the same way at least for the moment until a workaround is found.

diegocr said:
Thanks, I will wait bitbucket update :good:
Click to expand...
Click to collapse
- Did you guys find a way of been able boot Slim without having to fastboot a boot image each time?

ggow said:
- Did you guys find a way of been able boot Slim without having to fastboot a boot image each time?
Click to expand...
Click to collapse
no, only fastboot

diegocr said:
no, only fastboot
Click to expand...
Click to collapse
@csolanol and @diegocr
I have linked my Device Tree in the OP.

ggow said:
@csolanol and @diegocr
I have linked my Device Tree in the OP.
Click to expand...
Click to collapse
Thanks a ton :good:

diegocr said:
Thanks a ton :good:
Click to expand...
Click to collapse
- I built my ROM without block based image generation
- This means you can extract the ROM and use the proprietary-files.txt with the extract-files.sh to re-generate the vendor tree

[RECOVERY][tassve/CM11] TWRP 3.0.2-1 touch recovery [2016-10-16]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
{
"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"
}
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
CHANGELOG for 2.8.6.0:
-Fix daylight savings time rules for USA and Europe (_that)
-Allow mulitple overlays for popup boxes (Dees_Troy)
-Add pattern style password entry for decrypt (Tassadar)
-Keyboard improvements (_that)
-Update AOSP base to 5.1 (Dees_Troy)
-Reduce theme count to 5 and rely on scaling (Dees_Troy)
-Various scaling improvements (Dees_Troy)
-Improved handling of resources in the GUI (_that)
-Make scroll bar size proportional to list size (_that)
-Allow scoll lists to render without a header (_that)
-Make console scroll per pixel with kinetic scrolling (_that)
-Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
-Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
DOWNLOAD:
1) Download TWRP from here
2) Flash via CWM or TWRP recovery
3) Enjoy
BUGS:
- You tell me
If you have found a bug, please consider posting it here. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, If you see someone that's struggling, feel free to point it out to me.Thanks!
SOURCES:
https://github.com/CyanogenMod-ARMv6/android_kernel_samsung_bcm21553-common
https://github.com/CyanogenMod-ARMv6/android_device_samsung_tassve
https://github.com/CyanogenMod-ARMv6/android_device_samsung_bcm21553-common
TWRP-240x320-ldpi-theme 3.0.2-0
THANKS:
Dees_Troy.
TWRP team.
@psyke83 and BroadcomCM team for device tree and kernel source.

CHANGE LOG:
TWRP 3.0.2-1 [2016-10-16]
-Some UI improvement.
-Updated to latest changes.
totoro changlog
TWRP 3.0.2-0 [2016-04-05]
-Updated to latest changes.
TWRP 3.0.1-0 [2016-04-04]
-Updated to latest changes.
TWRP 3.0.0-0 [2016-02-16]
-Updated to latest changes.
-New theme reworked for ldpi (240×320).
TWRP 2.8.7.0 [2015-06-23]
-Fixed backup.
TWRP 2.8.6.0 BETA04[2015-04-10]
-Fixed all ui overlays.
-MTP enabled.
-Some changes I forgot.
TWRP 2.8.6.0 BETA03[2015-04-08]
-New UI hard coded from scratch.
TWRP 2.8.6.0 BETA02[2015-04-03]
-Fix inverted color
TWRP 2.8.6.0 BETA01[2015-04-01]
-Initial release

I dont have tassve some one test and report

Bricked my ace-i
LOL!

sohamsen said:
Bricked my ace-i
LOL!
Click to expand...
Click to collapse
Wash it with pure water and put in the sun for one year you will have cm15 on it.
Go to sleep soham

hahaha,just kidding bro!
anyways nice work,u brought twrp for our devices thats a great deal,huge thanks to u!
keep it up!
hope someone with tassave will test it for u
gd luck
---------- Post added at 01:38 AM ---------- Previous post was at 01:34 AM ----------
@mohammad.afaneh

work nice!
thx a lot!

Will test it soon :fingers-crossed:
Thanks for your work :good:

Is it compatible with CM 7.2 ROM?
Sent from my GT-S5570I using XDA Free mobile app

DodoGTA said:
Is it compatible with CM 7.2 ROM?
Sent from my GT-S5570I using XDA Free mobile app
Click to expand...
Click to collapse
No, cm11 only!

mohammad.afaneh said:
No, cm11 only!
Click to expand...
Click to collapse
Then can you make it compatible with CM 7.2 ROM?
Sent from my GT-S5570I using XDA Free mobile app

DodoGTA said:
Then can you make it compatible with CM 7.2 ROM?
Sent from my GT-S5570I using XDA Free mobile app
Click to expand...
Click to collapse
Maybe in the near future

tested it today, I flashed CM 11 and CM 9 without any problem but couldn't flash CM 7.2 unfortunately, its really amazing actually to see TWRP working on my dead android phone, feels nostalgic to play with it again ") thanks alot

jackvii7 said:
tested it today, I flashed CM 11 and CM 9 without any problem but couldn't flash CM 7.2 unfortunately, its really amazing actually to see TWRP working on my dead android phone, feels nostalgic to play with it again ") thanks alot
Click to expand...
Click to collapse
IsoRec for the win!
Sent from my GT-S7580 using Tapatalk

as soon as i flashed this my phone now hangs on samsung logo and doesn't move
is there any solution ?

saikyom said:
as soon as i flashed this my phone now hangs on samsung logo and doesn't move
is there any solution ?
Click to expand...
Click to collapse
In case you flashed this over cm7 or stock, flash your old kernel via odin.

Dont know why but my batterry level is always 1% except when charging.Is it a battery issue?

GreatGodvin said:
Dont know why but my batterry level is always 1% except when charging.Is it a battery issue?
Click to expand...
Click to collapse
No, I think this bug can't be fixed, not sure but its kernel related.