yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Android Development] ne0zone75:
Flashing recovery AND ROM is two different things... if you do not want TWRP anymore just flash [MENTION=3044346]arco68[/MENTION] CWM for example (i personally do recommend to use Odin when switching from a recovery to another because it is not a simple upgrade...)

Good luck ;)

Sent from my GT-I9195
[Galaxy S 4 Mini Android Development] Phenom2122:
The other two recoveries we have are CWM and Philz Touch (a touch capable mod of CWM). Here are the threads for the S4 Mini.

CWM: http://xdaforums.com/showthread.php?t=2398143

Philz: http://xdaforums.com/showthread.php?t=2463322
[Galaxy S 4 Mini Android Development] ne0zone75:
TWRP DEV branch updated !

Hello, i've just released a TWRP update of the DEV branch for GT-I9195 BUT also a brand new DEV branch for GT-9190 :victory: :good:

The previewed feature in both DEV builds is still the 'take a screenshot' from recovery one and it is working really well on the LTE variant (i'm saying so because i'm currently running it... it should work the same way on the 3G one...)

Files are packaged for each device into a zipped .tar.md5 file and also a flashable .zip file as usual ;)

Downloads links are updated on post number 1 and these DEV builds are only available from Dev-Host (not from the downloads tab of this project...)

Happy flashing to you !
[Galaxy S 4 Mini Android Development] Wildfear:
TWRP i9195 stable compatible with i9192

I tested this i9195 stable version of TWRP on my i9192, it's seems compatible.

They have both the same partitions and, only some hardware and modem not matching, but as radio isn't used in recovery...

I flashed some custom stockrom without any issue, but didn't try all functions yet.
[Galaxy S 4 Mini Android Development] ne0zone75:
Well... good evening and thank you a lot for trying it out on your phone and also for posting this valuable information :good: Until reading your positive feedback, i was unsure about the compatibilty of GT-I9195 or GT-I9190 CyanogenMod kernel and GT-I9192 because it's not as spread as the other Galaxy S4 mini variants AND specs are sometime different for its SoC from a website to another (

so it is definitely a MSM8930

...)

Its partitions layout is strictly the same as GT-I9195/0 because all Galaxy S4 mini variants AFAIK are sharing the same 'serrano-common' device tree in CyanogenMod (partitions table information is in it...) and only a few items are into the device specific tree of each variant (mainly cellular radio related as you might have already guessed...)

That is good news and i really appreciate your contribution :D After some more testing on your part, if you're OK to use and review this TWRP build a little bit more of course and if it's really working as it should, i will add a note on post number 1 about the compatibilty of my GT-I9195 TWRP builds with GT-I9192 :fingers-crossed: :good:

Kind regards
[Galaxy S 4 Mini Android Development] smartxdev:
Hi, does anyone here use encryption with CM11?

I've used it with CM10.2 and TWRP, and all was fine.

Now, I've upgraded my I9195 to CM11 M6 (and TWRP 2.7.0.0 stable, dated 2014-05-04):

And if I enable encryption and modify a pin or encryption password or using Cryptfs Password App, I'm unable to decrypt the system in TWRP anymore :crying: .

Though, I can boot into CM properly.

I've notice this change in CM11 branch.

Maybe there is some relation there. I don't know if this change should be supported by TWRP update, or it is just CM11 bug...

Anyways, in this manner, without being able to use TWRP, there will be no NANDroid backups, hence encryption is unusable for me now.

Any ideas on this??
[Galaxy S 4 Mini Android Development] ne0zone75:
Hi, this commit could be involved indeed, the last update in my TWRP builds has been compiled along with CyanogenMod sources BUT i do not know if they have been built before or after the merging of this particular commit... :confused: I will update both STABLE & DEV branches later today or tomorrow morning... just in case ;)

With that said i do not think that this issue is caused by TWRP build flags...

Best regards

Sent from my GT-I9195

EDIT : Updates are delayed to tomorrow... Thank you all for your understanding ;)
[Galaxy S 4 Mini Android Development] dulemars:
Hi, I'm using encrypted CM11... I've used OliverG96's recovery from this thread

http://xdaforums.com/showthread.php?t=2589011

All worked fine, except I could not restore encrypted backups. Then I stumbled upon this thread and tried latest DEV version, and I was unable to decrypt my filesystem when booting recovery, it always reported wrong PIN. Switched back to OliverG96 build and it works fine again (except the same issue with encrypted backups).

I can't wait for someone to fix those since I'm in a real need of encrypted-everything due to nature of my work :)
[Galaxy S 4 Mini Android Development] ne0zone75:
Hello, both branches of each device will be updated today on my part... i do not guarantee that the decrypting issue you are experiencing will be solved.

If this issue still remains after the update then i will ask for assistance to [MENTION=912474]Dees_Troy[/MENTION] who is the main TWRP DEV AFAIK...

Kind regards

Sent from my GT-I9195
[Galaxy S 4 Mini Android Development] Wildfear:
I will try some more testing asap, and report it here ;)
[Galaxy S 4 Mini Android Development] ne0zone75:
TWRP for GT-I9195/0 special TEST builds (decrypting issue)

[MENTION=5786498]smartxdev[/MENTION] [MENTION=4940125]dulemars[/MENTION] and everyone else experiencing the current 'decrypting issue',

Below you'll find updated TWRP from most recent source code (after a 'repo sync' : today) for both S4 mini variants :good:

Just let me know if it solves this particular issue :fingers-crossed:

In the meaning time, i do think it is maybe about some incompatibilty between most recent CyanogenMod 11.0 encryption handling and OmniROM TWRP tree... but it is just a guess ;)

-> GT-I9195 TWRP special TEST build | MD5

-> GT-I9190 TWRP special TEST build | MD5

Kind regards
[Galaxy S 4 Mini Android Development] dulemars:
No luck... Same issue as before, unable to decrypt filesystem.
[Galaxy S 4 Mini Android Development] ne0zone75:
Okay ! I will ask for support and let you know how this issue could be handled...

Best regards

Sent from my GT-I9195
[Galaxy S 4 Mini Android Development] ne0zone75:
About current TWRP 'decrypting issue'...

Hello,

Is any of you who is experiencing the decrypting issue identified by [MENTION=5786498]smartxdev[/MENTION] and [MENTION=4940125]dulemars[/MENTION], is running any custom ROM else than latest CyanogenMod 11.0 ?

Thank you for reporting back... :good:

Best regards
[Galaxy S 4 Mini Android Development] dulemars:
I'm running CM11-20140505-SNAPSHOT-M6-serranoltexx at the moment...

Note that Oliverg96's TWRP can decrypt my storage on boot, using this same ROM (but can't restore from encrypted backup), so I don't think this issue is related to ROM.
[Galaxy S 4 Mini Android Development] ne0zone75:
Okay, i've read your initial posts too fast... sorry about that :confused:

If i'm following you right now, [MENTION=5786498]smartxdev[/MENTION] you have no issue at all untill you change the encryption PIN... is that correct ? -> sounds like encryption keyring issue to me...; and [MENTION=4940125]dulemars[/MENTION] you are never able to decrypt your filesystem when entering my TWRP build isn't it ?

Have you both ever tried to delete 'TWRP' folder from 'internal storage' ? if your backups are on microSD then only TWRP settings are in that one so it is safe and it will be maybe useful to delete it (or move / rename it) so that TWRP will not find it -> it will reset TWRP to default and might solve this '/system decryption from recovery' issue but that it's just an idea at this point ;) (to be honest i do know how filesystem encryption/decryption is handled on Linux but not at all on Android...with that said it should be close...)

It would be also interesting to know if any of you is experiencing the same bug with some custom ROM else than latest CyanogenMod 11.0 ;)

I will ask for support to [MENTION=912474]Dees_Troy[/MENTION] ASAP

Greetings

Sent from my TF701T
[Galaxy S 4 Mini Android Development] smartxdev:
Hi,

Thanks [MENTION=5280400]ne0zone75[/MENTION], for taking a look at this issue.

I think some more details on the issue may be usefull:

What I can surely confirm is the following (the original issue that led me to dig it up):

I was encrypted on CM 10.2

At a time I didn't know that I can remove encryption by TWRP's format data

So, when I wanted to upgrade to CM11, I booted to TWRP, unlocked it and simply did a full wipe (system/data/cache).

Then, Iv'e installed CM11, booted to system, unlocked during boot with my old CM10.2 password sucessfully.

I did booted to TWRP then, successfully unlocked /data, checked some stuff.

Then booted again to CM11, changed the pin and then, I was never able to decrypt anything with TWRP+CM11 (I can unlock in system, just not in recovery)​

So, as you can see, because with CM10.2 + previous TWRP release, I had no trouble with encryption/key decoupling.

I wasn't all that concerned about basic TWRP decryption, and after noticing the CM11 key decoupling change, it seemed to me that that's the problem.

Then, logically, I wanted to test the key modifications.

I've done many wipe/install/encrypt/change pin procedures.

And I can't confirm with confidence that I ever succeeded to unlock in TWRP with

fresh

CM11 encryption prior to key modifications.

But once I forgot to modify pin and gone straight to the TWRP, and failed to decrypt, though, I thought that I've done something wrong wiping stuff beforehand, so I didn't pay close attention to this.

Anyways, I need to do more testing on it, and all the wipe/install/encrypt thing needs time.

I'll probably will find time for it during the next couple of days, and will have more clarification here.

Regarding other ROMs, I didn't try encryption on anything other that CM10.2/11, so I can't help there....
[Galaxy S 4 Mini Android Development] ne0zone75:
Hi and thank you for your detailed feedback :good:

I am investigating this issue ATM and it seems to me that it is not about a 'crypto' issue BUT an 'input' one : whenever i input my 'crypto' password (CM 11.0 private build), i am always getting a 'wrong password' error message when inputing the correct one -> it seems that the password that i'm typing is not correctly inputed...

INFO : when this issue will be solved i will update both branches for GT-I9195 and GT-I9190... USB-OTG will be featured :good:

Nice W.E. :D
[Galaxy S 4 Mini Android Development] ne0zone75:
TWRP 'decrypting' issue fixed ! [STABLE branch updated only ATM...]

I am happy to say that the above mentionned 'decrypting' issue is now solved (there was a small typo in my TWRP build flags :confused: ) :good:

Every of you who is using (or not) encryption is invited to flash the latest update of the

STABLE branch

which is 100% working now with ROM encrypted filesystems (BUT i've not tested encrypted backups creation yet...).

There is no new merged commits since the previous version, it's just an update with proper crypto build flags ;)

I've deleted all entries from the xda downloads tab of this project : new files will be uploaded ASAP.

Meanwhile, new STABLE branch builds for the LTE/3G variants are available from Dev-Host. Download links updated on post number 1 :D

As usual, don't hesitate to report back if anything goes wrong... or not ;) :fingers-crossed: :good:

Enjoy !

EDIT : xda downloads tab is now updated :good:
[Galaxy S 4 Mini Android Development] arsm74:
Font Size

[MENTION=5280400]ne0zone75[/MENTION] .. is it possible to increase the font size a little bit for the running log when we select an option?

The current font size seems a little small......
[Galaxy S 4 Mini Android Development] ne0zone75:
Post #733 is updated !

I have just updated post #733 (TWRP v3.0.0-0 TRYOUTS) with download links for a new set of flashable .zip archives !

I have replaced the first set by a new one... brightness control should work without any bootloop :fingers-crossed: ! The other set (without brightness control) has not changed.
[Galaxy S 4 Mini Android Development] arco68:
Try with

TW_BRIGHTNESS_PATH := "/sys/class/leds/lcd-backlight/brightness"
[Galaxy S 4 Mini Android Development] tioguda:
Works seamlessly with brightness control

thank you [MENTION=5280400]ne0zone75[/MENTION]
[Galaxy S 4 Mini Android Development] arco68:
Never mind. Brightness working in new build. Thank you! :)
[Galaxy S 4 Mini Android Development] ne0zone75:
There was a flag in my 'BoardConfigCommon.mk' that was preventing from a successful building process when using your updated brightness path...

Thank you for your help on this :good: !

Tapatalked from my SM-G903F
[Galaxy S 4 Mini Android Development] arsm74:
Works very well with brightness control on my i9192

Thanks again...,
[Galaxy S 4 Mini Android Development] niklus101:
brightness version works great on my i9192.
[Galaxy S 4 Mini Android Development] Smeagal192:
I9195 LTE (UK)

TWRP 3.0.0.0 with brightness control works fine :)
[Galaxy S 4 Mini Android Development] artu72:
+1

I9195 LTE Italy TIM

Inviato dal mio GT-I9195 utilizzando Tapatalk
[Galaxy S 4 Mini Android Development] ekl25:
I just flashed the bc version on my i9195 LTE (DE) and it works fine:)

Thanks a lot!
[Galaxy S 4 Mini Android Development] :
[MENTION=5280400]ne0zone75[/MENTION]: Thanks a lot for your hard work bringing twrp 3 to the s4 mini.

I'd like to build twrp 3 on my own. My question does not come with a competitive idea: Would you mind providing a how-to that shows how to build the latest twrp for the s4 mini?

This would be very much appreciated. Thanks for consideration.
[Galaxy S 4 Mini Android Development] ne0zone75:
I do not think that i will make a 'how to' guide at this time. Anyway if i do it someday, i will make it in a generic way and not only for the S4 mini because the principle is the same, whatever is the target device (if sources already exist for it).

Also, there is already the official TWRP building thread by [MENTION=912474]Dees_Troy[/MENTION], which provide a lot of useful informations.

Finally, if you want me to send you a mini TWRP building guide for the S4 mini over PM, then just say so...

Have a nice day

Tapatalked from my SM-G903F
[Galaxy S 4 Mini Android Development] malloy0:
TWRP work on SGH-i257 ATT Variant?

Have an unlocked SGH-i257 from ATT.

Rooted with Kingroot, at least seems this way per Titanium Backup, with Kingroot verison of SuperSU.

Any feedback on TWRP working via ODIN?

Flashed some CWM versions but no luck.
[Galaxy S 4 Mini Android Development] RomanSkyline:
Hi, works very fine, but if possible create a kernel with doubletap2wake feature? I see that when the screen turns off, if I touch it, it turns on

Enviado desde mi GT-I9195 mediante Tapatalk
[Galaxy S 4 Mini Android Development] ne0zone75:
What are you meaning by 'unlocked' ? I've not found something very useful about SGH-i257 bootloader status yet. Anyway, the hardware (SoC) of your device is the same as international versions : Qualcomm Snapdragon 400 (MSM8930) :good:. Is your bootloader unlocked or not ? If not, i do not know if the flashing process through Odin will work...

Regards
[Galaxy S 4 Mini Android Development] dagarcia:
I just Installed bc version on my serrano3gxx and it seems to work flawlessly, I'll let you know later or tomorrow when new cm13 build becomes available, how it behaves.
[Galaxy S 4 Mini Android Development] redjamesg:
Using TWRP 3.0, I just had to recover my phone in one of the most destroyed state.

Every partition was formated, had changed filesystem to F2FS on all partitions, and accidently it destroyed my SD card, as this was previously marked as combined internal CM memory.

What I ended up with was a phone with no files present and only 'adb sideload' to recover with.

The problem I ran into was, approximately 46% of CM 13 transfered sideload would deside entire file had been transfered and it would begin flashing it.

Using MTP on the phone didn't work, only state that did work, was to load the flashable image with 'adb push'

How ever knowing your way around adb commands, it is not the end of the world when the phone is in the state mine was, how ever I was putting my faith into adb sideload to perform as expected, not to terminate the connection in the middle if a file transfer.

Anyway, thanks [MENTION=5280400]ne0zone75[/MENTION] for your hard work.

Sendt fra min GT-I9195 med Tapatalk
[Galaxy S 4 Mini Android Development] malloy0:
Sorry I meant SIM unlocked on my I257 or last that's what I was told when I bought it. .

At this point, I am unsure if the bootloader is unlocked given its an ATT phone. ATT phones have a rep for not being unlocked bootloader. Gotta do a little more research to see how to determine if the bootloader is unlocked. What flag there is or is not.

Realted to being an unlocked BL, I used Odin to try to flash a CWM and TWRP recovery version for GT-i9195 but got the FAILED notice in the upper left corner of Odin.

My Build number = KOT49H.I257UCU2BNK1

Right now I am stuck with getting a custom recovery. Root is nice as I have been able to mod things I like, but a Samsung 4.4.2 ROM is not what Id like to run as my DD.

Thank you! (merci beaucoup)
[Galaxy S 4 Mini Android Development] ne0zone75:
Did you go successfully through this issue now ?

Greetings

Tapatalked from my SM-G903F
[Galaxy S 4 Mini Android Development] ne0zone75:
If Odin flashing process is failing each time, then maybe your BL is locked.

Checking if the loki utility is compatible with your device is maybe a lead. If it is, it would bypass your locked BL.

If loki is working for your smartphone, i do not remember if it can do more than rooting it anyway...

Kind regards

Tapatalked from my SM-G903F
[Galaxy S 4 Mini Android Development] Smeagal192:
[MENTION=5280400]ne0zone75[/MENTION]

I9195 lte uk

Hi just to let you know, I have been using twrp3 brightness version since uploaded, updates, backups and recovery all working without issue.

Sorry have not had time to do a clean install, will try and do that Monday.

Regards

Ray
[Galaxy S 4 Mini Android Development] redjamesg:
It seemed sideload timed out on the size of CM13, so I ended up just pushing it directly to /data/media/0 and install it as regular .zip

Everything went smooth from that point on.

Sendt fra min GT-I9195 med Tapatalk
[Galaxy S 4 Mini Android Development] ne0zone75:
Opening post is updated with v3.0.0-0 STABLE download links !

Hello,

I've just updated download links of STABLE branch with v3.0.0-0 packages (which are the same as latest TRYOUTS but Odin ready files are added). Downloads tab of this project has also been updated with v3.0.0-0 STABLE files and v2.8.7.0 ones have been kept as a fallback.

Anyway, latest v3.0.0-0 TRYOUTS are still available from post #733 for now but will be removed soon...

Cheers
[Galaxy S 4 Mini Android Development] Elite2k:
hey guys i cant get TWRP for the canadian variant the I257m to work i tried all the files for the TWRP for Samsung Galaxy S4 Mini US Cellular even tested version 3.0.0 .. it simply shows the blue writing( entering recovery) on the top and gets stuck.. does not enter recovery at all i have tested with all the twrp versions.. none work any adivce would be i wanna put a custom rom on here thanks
[Galaxy S 4 Mini Android Development] ne0zone75:
Custom recovery availability for i257/m ?

[MENTION=276993]malloy0[/MENTION] and [MENTION=345143]Elite2k[/MENTION]

I've found this article over ANDROID GEEKS website !

In this web page, Odin is used to flash CF Auto Root package for i257m by [MENTION=631273]Chainfire[/MENTION] (.tar.md5 file) and it is stated that once it is done, the user can install custom recoveries and ROMs :good: (Odin flashing process seems to be OK for i257m; so, maybe flashing one of my Odin ready files with Odin will work on i257m or through an Android APP like Mobile Odin, still by [MENTION=631273]Chainfire[/MENTION] ?)

BIG RED WARNING : the target device is i257m AND only this one !

Good luck
[Galaxy S 4 Mini Android Development] malloy0:
ne0zone,

Your help is super appreciated. I did see the same thing for the Canadian i257 version with the m suffix.

For me I have the US ATT i257 and I tried this but no luck.

I also downloaded LOKI but not figured out an how to easily use it via ADB to bypass my locked BL.

Overall I have 3 variants of he S4 Mini:

1. I9195 with only 3G and do not know how to get 4G LTE.

2. ST S890L which is 4G LTE has a locked SIM and I cannot use my ATT SIM only a Straight Talk SIM. It is ROOTED and I can install a custom ROM.

3. SGH-I257 which is the ATT version with 4G LTE. Its rooted using Kingroot but with the locked BL. So cannot install a custom ROM.

Needless to say lots of phone with various options but nothing that gets me where I want.

Regards,

malloy0
[Galaxy S 4 Mini Android Development] ne0zone75:
OK, you will find everything to know about the loki utility from its official Github webpage. It seems that your device is not supported yet; however, on this webpage, it is explained how to get support for new compatible devices (AT&T and Verizon branded SAMSUNG Galaxy S4 is supported, maybe your smartphone can be supported too...)

Best regards
[Galaxy S 4 Mini Android Development] arco68:
The Canadian i257m is identical to the international i9195, so use the recovery for that.
[Galaxy S 4 Mini Android Development] smartxdev:
Hi,

Thanks to [MENTION=5280400]ne0zone75[/MENTION] for the 3.0 updates!!!

Has anyone tested crypto support on it?

Also some mentioned that adapted storage is working. Is it encrypt-able as well? (I mean, with user-password protection on boot)
[Galaxy S 4 Mini Android Development] ne0zone75:
About crypto. feature (stock + custom ROMs) ?

Good evening to all,

Please let me know about how crypto. of latest release is working (/data + adopted storage)...

Thanks

Tapatalked from my SM-G903F
[Galaxy S 4 Mini Android Development] Oniwab4n:
Hi guys, I would like to know does this recovery support f2fs, and if yes how to setup this?

I am on RR 5.6.3. Thank you
[Galaxy S 4 Mini Android Development] milouk:
Yes it does support f2fs

In twrp go to wipe > advance wipe then check "data" then select repair or change file system select change file system then select f2fs.

For cache check cache partition and repeat the above once again
[Galaxy S 4 Mini Android Development] flipeicl:
I don't know if it is a bug, but sometimes I need to wipe internal storage to have a properly restore of a nandroid backup, during the process I receive error during flash modem and boot, so I don't mark to wipe just external SD and OTG, remove the battery, and after that everything goes properly, that never happened with 2.8.7.0.
[Galaxy S 4 Mini Android Development] ne0zone75:
Could you please post a TWRP log file as a reply after you got this issue again in order to check out what is going wrong ?

Thanks

Tapatalked from my SM-G903F
[Galaxy S 4 Mini Android Development] flipeicl:
I will, thank you for the reply.
[Galaxy S 4 Mini Android Development] luisbraz:
Can I flash the zip in CWM recovery? Or do I need to flash the other file in Odin? And in Odin where do I put the file? Thanks in advance.
[Galaxy S 4 Mini Android Development] flapane:
Just because it could be useful and the feedbacks on the web are scarce, I confirm that, coming from stock recovery, v3 can be installed via Heimdall+OSX 10.10

First download your PIT file, then just flash your "RECOVERY" partition. It took 60 seconds.
[Galaxy S 4 Mini Android Development] redjamesg:
You can flash it from CWM

Sendt fra min GT-I9195 med Tapatalk
[Galaxy S 4 Mini Android Development] luisbraz:
Just flashed in CWM, the zip in op and it's working fine,I guess!

But see what happened to the battery percentage! Strange!
[Galaxy S 4 Mini Android Development] tioguda:
What did happen with the battery percentage is normal because draining the battery while you were installing cwm (spent battery, lowering%) and when restarted and the device was connected to power it shows the% rising.

I do not advise you to use cwm (outdated) you will have problems, even if you want to use the conversion from SD card to internal memory.