[RECOVERY][UNOFFICIAL] TWRP 2.8.1.0 for S4 Mini / I9195

[thomson.aa]

Hello

This is TWRP v 2.8.1.0 for the S4 Mini. It works for the I9195 - I do not know if it works for similar devices.

The problem was that TWRP after version 2.7.1.0 did not boot up - the phone tried to enter recovery mode but eventually booted into android.
This is because of commit https://gerrit.omnirom.org/#/c/8471/ which does not seem to work nice with the S4 Mini.

DISCLAIMER : You apply this recovery at your own risk - if something breaks or bricks I am not responsible


IMPORTANT NOTE :
a) The attached file is NOT a flashable ZIP and I will not provide one. You have to unpack the attached file and use heimdall or dd. If someone wants to provide a flashable zip - I am fine with that.
b) There is no F2FS support.
c) I do not know if there are still problems with the recovery sometimes not booting up - I tried it a couple of times and it worked every time. Tell us if you experience booting problems.
d) I am no coder - so I cannot help with things like encryption, luks or similar wishes.


How to install:
a) Boot your phone to download mode
b) Connect phone to PC
c) Get root on your PC
d) Unzip attached ZIP file
e) Check md5sum
f) heimdall flash --RECOVERY recovery.img --no-reboot (dd should work as well - take care of the right partition)


Thanks goes to:
Teamwin
OliverG96
_that

Additional information:
If you want to build this by yourself from sources open file twrp-functions.cpp and search for line:

int TWFunc::Set_Brightness(std::string brightness_value)

You can change it like that:

int TWFunc::Set_Brightness(std::string brightness_value)
{
	return 0;
	std::string brightness_file = DataManager::GetStrValue("tw_brightness_file");;

This should fix the problem. According to one of the developers there should also be a flag for specifying a brightness file that one can probably set to /nobrightness.

 

[DeusEx80]

It works great on my I9195 !

From your recovery, i created the Odin version and flashed it.

Thank you very much.

I attach the Odin version of your recovery (Instructions: unzip the .zip file, and flash the .tar.md5 file with Odin 3.09 into AP field)

 

[ladislav.heller]

Recovery flashable ZIP version of TWRP 2.8.1.0 attached.

 

[mike_san]

Mounting both (Internal and External) doesnt work

 

[thomson.aa]

Mounting both (Internal and External) doesnt work

What do you mean? Mounting works for me - I can mount System and Micro SDCard and I can access the files there with the TWRP File Manager. So no problem here. Works also with adb - I got access to the full file system. Might be a problem with your phone/setup.

 

[DeusEx80]

What do you mean? Mounting works for me - I can mount System and Micro SDCard and I can access the files there with the TWRP File Manager. So no problem here. Works also with adb - I got access to the full file system. Might be a problem with your phone/setup.

I confirm this.
I tried to mount and unmount System, Data and micro Sdcard... all ok.

 

[lars85destroyer]

Will it work with f4k kernel ?

 

[ericlnu]

lars85destroyer: both CM 12 and f4k work fine with or. As the recovery used isn't kernel dependent anyway, it's not an issue.

 

[dulemars]

Works great so far, noticed only one (minor) issue:

I need to use encryption for my phone and for its backups as well (I'm a sysadmin and my phone is fully equipped to access my datacenter). When using keyboard to type encryption/decryption passwords, somethimes I hit one key and completely another key gets pressed, can't be due to fat fingers because wrong key that gets pressed is usually very far from the original one. This was very iritating sometimes since I needed to type passwords for 3-4 times in a row for them to work. Figured out how to prevent this, I look at whole keyboard carefully on every keystroke and I'm usually able to see when it gets buggy and hits wrong key (keystroke animation is trigerred), but this isn't very fast or comfortable...

I think I had the same problem with early versions of TWRP 2.7 posted here but it has been resolved in newer ones. Otherwise, works as a charm, if someone added full F2FS support it would be totally perfect

PS If my memory serves me well, fix was build.prop related.

 

[lars85destroyer]

lars85destroyer: both CM 12 and f4k work fine with or. As the recovery used isn't kernel dependent anyway, it's not an issue.

works fine on aicp, Thanks

 

[xpamamadeus]

s.basketbuild.com/devs/F4k/twrp/serranoltexx
this one have F2FS