yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Android Development] ne0zone75:
Please let me know if you find it out... TWRP settings are stored in 'TWRP' directory from your internal storage... not microSD :confused:

Good luck !

Sent from my GT-I9195
[Galaxy S 4 Mini Android Development] ne0zone75:
Hello all, from now ALL downloads of this project are also available from the downloads tab of post number 1 in addition to Dev-Host links :victory:

Be well
[Galaxy S 4 Mini Android Development] ne0zone75:
I will release a TWRP update soon when all recent important commits will be merged upstream ;)

Stay tuned...

Sent from my GT-I9195
[Galaxy S 4 Mini Android Development] jake3317:
So far your TWRP works great, I really enjoy it's benefits over CWM: no more clicking down, down, down etc

Verstuurd vanaf mijn Transformer TF101 met Tapatalk
[Galaxy S 4 Mini Android Development] ne0zone75:
Thanks... an update will be released this W.E. ;)

Sent from my GT-I9195
[Galaxy S 4 Mini Android Development] ne0zone75:
TWRP update released...

I've just updated Dev-Host download links... new build is currently uploading on xda downloads page of this project... please checkout post 1 ;)

This new build is compiled against SlimKAT build 4 sources tree instead of CyanogenMod 11.0; it should fix timezone issues that some of you encountered and features a lot of improvements => compatibiltiy with JB ROMs should be fine (for KK ROMs support is full) AND many other fixes :good: (still lacks the 'take a screenshot from recovery' feature which will probably be merged soon...)

There is no changelog because it's a TWRP 2.7 intermediate build BUT you can review merged commits included into it HERE...

It's available as a zipped .tar.md5 Odin flashable file AND a .zip custom recovery flashable file as usual :highfive:

Thanks to all of you who downloaded my recovery files so far :good:

All the best ;)

Tapatalked from my TF701T

EDIT : All download links are now updated...
[Galaxy S 4 Mini Android Development] hansare:
Thanks for your quick answer.

I'm on Carbon Rom build 20140704.

Imo you'd better strongly advice use of Odin.

Now it looks whether zip is normally no problem.

Do I understand well that the delay in switching off / rebooting will disappear when I do a clean install of the rom?
[Galaxy S 4 Mini Android Development] ne0zone75:
Yes ! But what i do know is how to manage this thing properly, maybe a true clean install will be sufficient or maybe additional steps to it will be mandatory...

Anyway, you should ask for assistance into 'Carbon ROM' thread because [MENTION=3261191]F4k[/MENTION] is really more experienced than me ;) :good:

Regards
[Galaxy S 4 Mini Android Development] ne0zone75:
TWRP 2.8.0.0 for all S4 mini variants is out !

Good evening,

Post #1 is updated with new AndroidFileHost download links (xda downloads tab will be updated later) : it is TWRP 2.8.0.0 ! :good:

-> no changelog is available officially for it yet... (as soon as it is, i will post it here)

-> you will tell me if decrypting /data over EXT4 / F2FS is working for AOSP based ROMs (not working for sure with stock one)

-> as usual, any comment will be greatly appreciated

Enjoy it ! :D

NB : ALL F2FS version will be updated for each device very soon... ;) (it is still 2.7.1.x)
[Galaxy S 4 Mini Android Development] DeusEx80:
GT-I9195, Cyanogenmod 11

Flashed the 2.8 version both zip from recovery, both the tar.md5 with Odin: the first time the new recovery boot correctly, then always reboot.

I Try also to remove the theme that i have applied to recovery (holo dark).

I reflashed the old recovery (0606)
[Galaxy S 4 Mini Android Development] ne0zone75:
Allright, i borrowed my brother's wife S4 mini LTE and after a few testing v2.8 STABLE was behaving well (besides decrypting /data of stock ROM was not working).

So it should be the same for the three other builds (LTE : DEV & 3G : STABLE + DEV) because differences between each ones are thin...

Finally, i totally agree with you ! It was not booting always at the first attempt... :confused: (i do think that maybe something went wrong with my F2FS CM-11.0 patched kernel : i use it in every build, even STABLE ones... or UU GCC toolchain is involved...)

Anyway, i will take my time to sort this out. Thanks for your feedback.

Regards
[Galaxy S 4 Mini Android Development] F4k:
Hi!

I experimented something similar when I was testing my compiled TWRP sometime ago, sometimes phone won't boot up correctly on recovery mode, unfortunately I didn't did a further investigation yet, maybe we are needing some additional change?

Anyway I'll try to see what is going on if I got a little bit of free time, but let me know if you find a fix for this :)

Regards!
[Galaxy S 4 Mini Android Development] ne0zone75:
Good morning,

Of course, Yes ! We keep in touch... ;) :good: Anyway, thank you a lot for giving feeback about it ! :)

My kindest regards

PS : I am really wondering if 2.8.0.0 is really merged upstream because OmniRom gerrit does not say so...

Tapatalked from my TF701T
[Galaxy S 4 Mini Android Development] ne0zone75:
[MENTION=3261191]F4k[/MENTION] AND all the audience ;)

It really seems that disabling MTP from the 'mount' menu after having flashed v2.8.0.0 AND resetted TWRP settings to default from the 'settings' menu make the recovery booting process more reliable... to be confirmed... (once disabled, MTP will stay like this AND it will be up to you to enable it again)

Now, i will offer updates of all files for both S4 mini variants soon... (EXT4, F2FS and ALL F2FS)

These updates will support every filesystem handled by external storage that matches kernel abilities. (not 'only vfat' anymore)

My best regards
[Galaxy S 4 Mini Android Development] ne0zone75:
Data disaster !

Good afternoon,

Because i've had a hard drive failure AND because i am not using GitHub the way i should, i've lost almost every single piece of my work about all my current and upcoming projects over xda (TWRP AND SlimKat ports for S4 mini & Transformer series) :crying: :mad:

That is not that bad to start again from scratch sometimes... :good:

Anyway, it will take some time for me to have working sources trees again so please be patient...

I cannot give you any ETA about a release date of any update regarding any of my projects and please do not ask for it... :angel:

Furthermore, i am quite overloaded at work and i have less and less free time to take for Android !

Updates will come in that order (if everything goes well...) :

-> SlimKat build 8.x : S4 mini series <= before the end of september 2014 (probably next week...)

-> SlimKat build 8.x : Transformer series <= before the end of september 2014 (after S4 mini series update is released...)

-> TWRP v2.8.x.x : S4 mini series + Transformer series at last !

Finally i am aware that the OPs of my current projects are quite messy and i apologize for that

! ;)

Thank you all for your understanding :good:
[Galaxy S 4 Mini Android Development] laurorual:
Hi! I have a S4 Mini Dual Sim and i'm trying to install this custom recovery. I've flashed the 3G Stable version of this recovery but when i try to enter it, it doesnt boot on recovery. The phone restarts and boot normally in my stock rom. Am i doing something wrong?
[Galaxy S 4 Mini Android Development] smartxdev:
Hi. Very sorry to hear that happened... :crying:

I guess "backup the backup... of backup... of backup..." is the moral of this story for everyone :(

But, anyways, as you said it's an (forceful and not nice) opportunity to do a fresh start. :)

Also, M10 is compiling now, so it's flashing time for me (CM/Kernel/Modem/Recovery).

I want to clarify a bit the current status of the TWRP stable builds in the opening post, since they're going to stay as they are for a while there, giving the circumstances...

So, are all the "fixes to be updated in a few hours" are incorporated there? If not, what has been left out? :confused:

And what are the state of crypto support (as far as you know)? Does CM supported? What about Stock?

Any more cautions you are concerned about?

Should I be able to reflash back safely to a previous version without crippling the encryption in the case the support of the recent build will fail for me?

And again, seems like we (or at least I) are going to settle with some version of TWRP for a bit of a long run now, so I want to make sure to settle on the most stable one, be it the latest, or not.
[Galaxy S 4 Mini Android Development] ne0zone75:
Good afternoon and very sorry to answer to you so lately,

ALL my TWRP v2.8.x.x builds for S4 mini do have the 'recovery not always booting' issue which has been reported by [MENTION=3261191]F4k[/MENTION] too !

I made some kind of mistake by making them available publicly for download and i really apologize for that !

I will wait untill that bug is sorted out before updating my builds again !

What i will do shortly is to rebuild TWRP x2.7.1.x along with CM-11.0 sources : both branches for each device ! These ones will be clean of the above mentioned problem ! ([MENTION=5786498]smartxdev[/MENTION] : encryption will be fully supported too for AOSP...)

-> STABLE one will only have basics : no F2FS version

-> DEV one will have extra features : F2FS for /data only version + ALL F2FS version

I will also make a huge cleanup across all my current xda projects !

To answer to your question, please dowload a TWRP version from [MENTION=3261191]F4k[/MENTION] that is suitable for your device for the moment, thank you

!

Regards
[Galaxy S 4 Mini Android Development] ne0zone75:
Allright,

First of all thank you for your understanding !

Like i've just wrote down in the post just above, post #1 will not stay as is for very long ! I will fallback to TWRP v2.7.1.x soon ! TWRP v2.8.x.x will be back once the 'recovery not always booting' bug is fixed !

I understand that you are quite confused, but :

-> do not download any of my TWRP v2.8.x.x builds for S4 mini (all variants) for the moment, thank you !

-> i will fallback to TWRP v2.7.1.x

-> crypto support : AOSP will be fully supported (at least for STABLE branch because crypto over F2FS is more than experimetal...); stock should be... anyway crypto will be deeply tested before files are released ! (FYI i do own a S4 mini once again...)

Nice week to you !
[Galaxy S 4 Mini Android Development] smartxdev:
Sooo, for now, for the best stability I guess I'll do the following:

(Please, correct me if I'm wrong)

- I'll carry on with my current TWRP 2.7.1 build of yours (dated somewhere in early June, or end of May, before the end-of-august modifications).

- Untill a 2.7.1 version will be re-released. Then, update/switch to it.
[Galaxy S 4 Mini Android Development] laurorual:
No problems dude, we all make mistakes :p

For now i will be using CWM, but for sure i will install this port of TWRP as soon as you fix it!
[Galaxy S 4 Mini Android Development] ne0zone75:
Yes ! Absolutely !

I will release v2.7.1.x again for three reasons :

-> no 'recovery not always booting' issue

-> some of you may have deleted my previous v2.7.1.x series or some of you are new to my builds

-> it will be built from a TWRP commit just behind the one where v2.8.0.0 has been introduced (this one), so it will be far ahead (commit speaking) my previous v2.7.1.x series

Meanwhile, i will try to narrow down this v2.8.x.x bug...

Regards

BTW, here is the 2.8.x.x changelog (grabbed from TeamWin website) :

... i will build it without MTP at all... just to see...
[Galaxy S 4 Mini Android Development] smartxdev:
Thanks a lot for your support and efforts :good: :)
[Galaxy S 4 Mini Android Development] ne0zone75:
Updates are coming...

Yes ! updates will come BUT i really do not know when...

FYI i am currently running 2.7.0.1 with crypto over CM without any issue, i will try to build 2.8.0.1 again and see if it is usable in any manner !

My best regards
[Galaxy S 4 Mini Android Development] ne0zone75:
Unified updates are building !

Good afternoon,

It seems that the 'recovery not always booting' issue has been solved upstream and that is good news ! :) I am currently running a freshly built TWRP v2.8.0.0 and it behaves absolutely as it should ! :victory: :good: So, i will update all files today !

-> All builds will be unified : each new file will be flashable on any S4 mini variant (3G/DS/LTE)

-> There will be two categories (branches) :

* STABLE one for standard usage (fully EXT4)

* DEV one for advanced usage with (F2FS)

-> crypto will be fully supported by STABLE branch only (AOSP, stock)

Stay tuned !
[Galaxy S 4 Mini Android Development] smartxdev:
Sounds awesome :good: !

And cheers on the branch unification :)

Hopefully it'll reduce mess for the users and also simplify builds and updates for you (decreasing chances for mistakes and mess ups), which is even more important :)
[Galaxy S 4 Mini Android Development] ne0zone75:
New builds are online !

Post #1 is updated with new download links (Android File Host) for unified builds; xda downloads tab will be updated later !

Have a nice sunday !
[Galaxy S 4 Mini Android Development] Sushi1022:
Works great! Thanks, man, you da real MVP! :D
[Galaxy S 4 Mini Android Development] wolroc:
First of all thank you for all your brillant work.

Unfortunately the 'recovery not always booting' is still occuring, at least on my dual sim i9192 phone.

I tried a lot of flashing of all your twrp 2.8.0.0 files and reboots to recovery but I had to go back to your twrp stable version 2.7.1.0.

Coming from your twrp 2.7.1.0 all your 3 new versions could be flashed as zip files in twrp but only the dev#2 booted sometimes.

None of your 3 twrp 2.8.0.0 odin files (tar.md5) could be flashed. Odin 3.09 crashed always on my PC and the one of my son as well after selecting 'Start' and the files were being checked before the flashing really started. Philz recovery files were no problem to flash via Odin. Also Odin 1.85 failed with all your files.

Of course I did double check the md5 checksums on the files but they are absolutely correct. As such I wonder whether your odin files are somehow faulty.

On the other hand I also flashed the pure .img recovery files in your twrp zip files with the app 'rashr' without any problem but again only the dev#2 version booted sometimes. The other two typically booted only one time and never again.

Any idea on the 2 problems observed. - the non booting of twrp 2.8.0.0 and the odin flash problem?

I also do not understand why odin flashing should be better/different to the other methods - do you know any backgrounds?

Thanks in advance.
[Galaxy S 4 Mini Android Development] happyta5:
Same here....

Odin 3.09 crash when you press the "start" button. Tried to update via recovery. Installed fine but i can't go back to recovery anymore......
[Galaxy S 4 Mini Android Development] sasank360:
I have the same issues as mentioned by users in above 2 posts. I have I9195 and am running cnh5 deodexed rom. Twrp2.7.0.0 was working fine but the new recovery files fail. Odin crashes and is unable to load the tar.md5

When I use zip version it flashes with no problems but recovery does not show up...

device shows rebooting recovery and after a while it boots back to system(rom).
[Galaxy S 4 Mini Android Development] ne0zone75:
Allright, i do know why my latest Odin files are not working... I will repackage them into zipped recovery.tar.md5 files ASAP and i am sending you all my apologies for this... :confused:

I do think that the 'recovery not always booting' issue is an upstream one so the solution is to wait until it is fixed.

Kind regards

Sent from my GT-I9195
[Galaxy S 4 Mini Android Development] sasank360:
No need for apologies dude.. :highfive:..your work is great..:good: I like the slimkat roms on your thread appreciate your work. Thanks again. Cheers.:D

EDIT :: When I extracted the odin package(tar.md5) i found the img file that is named opersource.twrp..XXXXX.img. Isn't that supposed to be recovery.img???

Just an idea though...i am not sure...
[Galaxy S 4 Mini Android Development] noradtux:
Hi,

I installed the development version of TWRP today. Overall it seems to work fine, but two things seem strange:

1. I cannot connect to the device using adb shell. Adb doesn't seem to be running.

2. I tried to reinstall cm-11 on this serranoltexx. cm-11 denied installation because it thinks the device is a serranolte3g.

Is your source-code available somewhere? I could tray to fix this.

/Malte
[Galaxy S 4 Mini Android Development] ironjon:
Yep, same here.

Installed via zip and doesn´t boot into recovery, goes to system

No problem with 2.7

Thanks
[Galaxy S 4 Mini Android Development] ne0zone75:
1 -> Yes ! I am aware of this.... it will be fixed soon !

2 -> Simply delete the device device checking code in the updater-script of your CM-11.0 ROM installer... it is a downside of my unified builds !

And No ! For the moment my source code is not publicly available !

Regards
[Galaxy S 4 Mini Android Development] ne0zone75:
New files will be released this weekend :

-> repo synced to latest version (omnirom tree) and because of the persistence of the 'recovery not always booting' issue, i will offer a 2.7 + a 2.8 version

-> Odin files will be fixed

-> adb should be fixed

Regards

Sent from my GT-I9195
[Galaxy S 4 Mini Android Development] impactor:
I'm on i9195 LTE.

I installed -> Custom TWRP v2.8.x.x JB/KK enabled for S4 mini | DEV #2 (2014-09-27) | Odin & .zip <= ONLY if you do have an ALL-F2FS setup...

but it turned out there is nothing related to F2FS in it, for example Settings/"Force data and cache wipe functions to use F2FS"

so I tried to downgrade using one of those recoveries for GT-I9195: http://xdaforums.com/showpost.php?p=53243813&postcount=2

but I get an error:

Did the OP confuse links and got me stuck with the wrong recovery?
[Galaxy S 4 Mini Android Development] wolroc:
Very good news - thank you very much for your excellent support.

Concerning the 'recovery not always booting' issue I wonder what you mean with an upstream solution, probably you mean the TWRP team?

Do they know already about such an issue because at least we have here the TWRP 2.8 booting and working flawlessly on a Nexus 7 (2012) and the Samsung S5?
[Galaxy S 4 Mini Android Development] ne0zone75:
Good afternoon and very sorry for this situation, to clarify things a little bit (and i know that my thread is quite messy...) :

-> unified builds are built along with serrano3gxx tree only BUT are working on 3G/DS/LTE, therefore any flashable .zip file with device checking code for anything else than the 3G variant will throw an error just like the one you got.

-> to workaround this you have several ways depending on what you are trying to flash : by using Odin (recovery / kernel) or by deleting the device checking code from inside the updater-script (recovery / kernel / ROM)

So you are not stuck with the wrong recovery... in your case if you want to fallback to any other custom recovery, please use the Odin way, thank you and if the recovery of your choice is not Odin packaged, i will be happy to tell you how to do so...

BTW, all my TWRP builds are working straightly like it has been designed by Team Win team ATM (including F2FS ones) and when you are saying that there is no F2FS support in those, you are simply wrong ! Because there is support for it but like Team Win designed it ATM... there is no MOD !

Precisely differences between each builds are only the fstab files (F2FS enabled kernel is always there...)

Just let me know if you need further assistance,

Regards

Sent from my GT-I9195
[Galaxy S 4 Mini Android Development] ne0zone75:
Hello, my guess is that it has to do with MTP which has been introduced with 2.8 and in one way or another this issue will be fixed... it is a only matter of time (as usual...) but it will not be fixed by me because it is far from my abilities and furthermore i am really short in free time these days...

Anyway there is still the 2.7 fallback as a workaround...

Sent from my GT-I9195

PS : And of course you are right... it is a device specific issue...
[Galaxy S 4 Mini Android Development] ne0zone75:
New builds are out ! (v2.7 fallback)

Good evening,

Opening post is updated with new Android File Host download links, xda downloads tab will be updated later, several things :

-> these builds are compiled from the latest TWRP commit before v2.8 has been introduced

-> all builds feature automatic FS detection by [MENTION=3261191]F4k[/MENTION] which means that EXT4/FSFS FS are supported in every build BUT STABLE is EXT4 oriented (some F2FS limitations) and DEV is F2FS oriented (some EXT4 limitations)

-> separate 3G/LTE builds are back !

Happy flashing !
[Galaxy S 4 Mini Android Development] jukyO:
[MENTION=5280400]ne0zone75[/MENTION]

Downloaded dev2 with chrome. All good, but no extension. Have to add .zip

---------- Post added at 10:10 AM ---------- Previous post was at 09:47 AM ----------

In addition

Where is an option to format to f2fs?
[Galaxy S 4 Mini Android Development] ne0zone75:
Hello,

What do you mean with 'no extension', 'no file extension' ?! Anyway, the option to format 'a partition' to F2FS is there... : go to ''wipe/advanced wipe/select '/system or /cache or /data' and then click on 'repair or change FS', finally choose F2FS and confirm'' -> congratulations your 'partition' is now F2FS formatted...

Have a nice weekend ;)
[Galaxy S 4 Mini Android Development] wolroc:
Dear ne0zone75,

thanks again for your hard work.

I have checked the odin & zip files for the i9190 and i9195 version of the S4 mini stable branch on my S4 min Duos (i9192) with the following result:

The two odin versions can now be flashed without problems. However the i9195 version does not boot into recovery - after a while the phone boots into the system again as also observed with the previous 2.8 TWRP files (but there flashed via existing recovery unsing the zip files) - possibly a hint? I did the odin process twice with the i9195 file and the result was the same.

On the other hand the zip versions, to be correct the recovery image files in the zip files, could be flashed without problems with the rashr app. Also the zip files themselves were flashed without problem. In this case both TWRP versions, the i9195 and the i9190, worked fine without problems. I cannot understand what the difference between the odin flash and the two flashes via an existing recovery (using the zip files) or the rashr (using the img files in the zip files) are but at least the results are different. Maybe you have an idea?

By the way the rashr app is also very helpful for all being stuck with a non working recovery.

Rashr simply needs a recovery.img file (may also have a different name) on any directory and flashes the recovery directly without the need to have another recovery being available and booted. I am not affiliated with this app but I really enjoy using it. Give it a chance if you like it.

Have a nice weekend.
[Galaxy S 4 Mini Android Development] ne0zone75:
Good evening,

It is weird because i am using current STABLE version for GT-I9195 flashed trough Odin and it is booting fine each time; nevertheless it is booting slower than previous versions because of automatic FS detection ! (

FYI i did manage to format /system + /cache + /data to F2FS using it and then flashed a F2FS enabled SlimKat ROM installer after having rebooted into recovery; F2FS partitions were correctly mounted, thanks to [MENTION=3261191]F4k[/MENTION] script inside recovery ramdisk

:good:)

Here are the key features of current recoveries :

-> same F2FS enabled kernel with automatic FS detection for all builds

-> crypto support is present only in STABLE branch (because AFAIK TWRP can handle crypto properly if /data is EXT4 formatted) and is disabled at all in DEV branches

-> a suitable twrp.fstab is present in each branch according to build usage (fully EXT4, F2FS -> /data only or ALL-F2FS)

Your feedback about flashing latest releases is very interesting... Thank you ! I will give a try to the APP you mentionned above ASAP ! ;) There are different ways to flash a partition image file (flashing technique), in my experience Odin was the most reliable (when switching from a recovery to another one) while flashing from a custom recovery was the most convenient (when updating current recovery)...

Regards