yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Android Development] ne0zone75:
Hi,

I would recommend upgrading straightly if only i could have tested latest TRYOUTs internally : unfortunately i do not have a suitable device for this for a long time now... :fingers-crossed:

Anyway, it will not hurt anything if you install v3.0.3-3. If your are not satisfied with it, then simply flash v3.0.3-0 back again.

:good:

Greetings
[Galaxy S 4 Mini Android Development] gay-sha:
Thank you very much for the prompt response, I will install the latest version available and any inconvenience will let you know.
[Galaxy S 4 Mini Android Development] :
I've tested encryption with 3.0.3-3 and all seems to work well. I'm using aokp_serranoltexx_nougat_nightly_2017-02-27.zip with open_gapps-arm-7.1-nano-20170220.zip.

After encryption, I've rebooted to recovery three times; in between times using the phone normally(using apps etc) to see if there were any decrypting problems in TWRP: No issues at all with encryption.

[MENTION=5280400]ne0zone75[/MENTION]

If you would like I could test other roms, but it seems the crypto footer issue is finally solved. :fingers-crossed:

Thanks again. :good:
[Galaxy S 4 Mini Android Development] ne0zone75:
Good news :good:,

Yes ! If you are interested in other ROMs then it will be interesting to see how v3. 0.3-3 behaves...

Cheers ?

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] Danyaru:
Every time I boot the system, TWRP disappears and I have to flash it every time I need it. Is there a way to permanently flash it?
[Galaxy S 4 Mini Android Development] IronRoo:
Are you booting up straight after you have flashed recovery? Don't. In order for the custom recovery to "stick" you must boot back into recovery the first time after flashing a recovery, TWRP will then overwrite the stock recovery default and it should then "stick"
[Galaxy S 4 Mini Android Development] :
[MENTION=5280400]ne0zone75[/MENTION]

TWRP 3.0.3-3 works fine using OCT-N-M0-7.1.1-20170304-serranoltexx

Backup/restore and encryption/decryption works well. Seems stable to me :)
[Galaxy S 4 Mini Android Development] ne0zone75:
Good evening,

I think that v3.0.3-3 will be flagged as STABLE very soon. v3.1.0 upstream version is out and i was planning to offer updates BUT it is going not good with compilation ATM. I think that it will be sorted out quickly... :finger-crossed:

Also and FYI, a friend of mine will give me a S4 mini as soon as he will have a new smartphone... :good:; internal testings will then be possible again...

Cheers all ?

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] icero:
This is good news !!

Possibly also start the construction of slim? Or some other project?
[Galaxy S 4 Mini Android Development] ne0zone75:
... i will think about it and i will let you know but my answer will likely be no...

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] icero:
Equally grateful for all his work on this team !!! :bueno: :bueno:
[Galaxy S 4 Mini Android Development] ne0zone75:
You are (all) more than welcome ?.

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] ne0zone75:
v3.1.0-0 is compiled ✌️.

New files will be available shortly...

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] ne0zone75:
? v3.1.0-0 is OUT !

Hello,

New installers are available now over AFH. It should work as great as v3.0.3-3 ? . Foreign languages availability and NTFS support for removable storage are still disabled in order to meet recovery image size requirement. That's it !

-> 'Odin' ready files

3G | DS | LTE

-> flashable ZIPs

3G | DS | LTE

Enjoy ?

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] lars85destroyer:
Great ! I've seen in changelog that it should fix restore issue on 7.x.x roms.

With 3.0.3-3, SMS / Button settings / status bar settings / dev options / system profiles were lost during restore (AICP 7.1)

Will report on this during this week
[Galaxy S 4 Mini Android Development] ne0zone75:
Any feedback about v3.1.0-0 ?

Good night

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] KevinX8:
Everything working well, restore seems to work correctly now for nougat roms. The time for recovery to boot is getting longer after each update for some reason for me.
[Galaxy S 4 Mini Android Development] :
Strange. For me the restore function has worked perfectly since at least 3.0.3-0(i9195)

All good here. Backup/restore works well. I'll test encryption later in the week if I have time. Thanks again for your work. :)
[Galaxy S 4 Mini Android Development] ne0zone75:
Perfect ?.

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] pedro311:
Cross-posting also here:

https://xdaforums.com/showpost.php?p=71428719&postcount=674

Also checked your v3.1.0-0 on lineage-14.1-20170306-UNOFFICIAL-serranodsdd - the same problems.

My way to turn on RIL sometimes works on first try, sometimes it takes me even 5 - 6...

What you need to check it, adb log?
[Galaxy S 4 Mini Android Development] Harvey_Spectar:
Yeah for me also restore is not working perfectly.

Still ril broken in GT-I9192

Other than that no issues

Thanks for your hard work?
[Galaxy S 4 Mini Android Development] Darktitor:
Do we need to wait F4k update his kernel to use F2fs or can I try it on the latest SlimKat?

Envoyé de mon unknown en utilisant Tapatalk
[Galaxy S 4 Mini Android Development] ne0zone75:
Hello,

If you move your partitions to F2FS right now without a suitable kernel to mount them during boot, then... it will not boot !

Greetings
[Galaxy S 4 Mini Android Development] spanish33:
Nice! Just have to wait for [MENTION=3261191]F4k[/MENTION] new kernel with f2fs support to test .

Edit: [MENTION=5280400]ne0zone75[/MENTION] format to f2fs is working as expected.
[Galaxy S 4 Mini Android Development] ne0zone75:
Good morning,

Is F2FS implementation in my TWRP builds fully working for you ?! I mean : converting from some filesystem to F2FS firstly (you already answered to this...) BUT then when rebooting into TWRP after you converted a partition to F2FS, is the F2FS partition mounting properly and are you able to back it up, wipe it and restore it... ?!

Thank you for your precious feedback :good: ;)
[Galaxy S 4 Mini Android Development] mielletseed:
For me on a restore partitions were reformatted with ext4 and I didn't found the option to prevent this.

An other questions: by converting you mean reformatting with different file system and losing the data or is there a option of real converting a partition?

Best regards
[Galaxy S 4 Mini Android Development] dulemars:
F2FS + Encryption not working; It seems that recovery, when doing a filesystem format, doesn't format decrypted devices but formats raw devices instead so encrypted partitions get corrupted.
[Galaxy S 4 Mini Android Development] ne0zone75:
Very interesting...

I mean formatting to F2FS : AFAIK TWRP does not perform a true conversion by keeping data on the 'converted' partition ATM...

Very interesting too... you did try to format your encrypted partition manually after having inputted your crypto password i assume...

Thanks for reporting back :good:, as you might already know, F2FS support in TWRP is brand new so it will take some time to make it reliable, furthermore, TWRP F2FS support (kernel side) is quite experimental for S4 mini...

F2FS formatted partitions are correctly mounting for you BTW ?

Greetings

Sent from my GT-I9195
[Galaxy S 4 Mini Android Development] dulemars:
So my plan was like this: Install recovery, confirm that backup/restore of entire phone (encrypted) is working, then reformat encrypted partitions with F2FS, then do restore, and that's hopefully it.

After formatting all partitions with F2FS I became unable to decrypt phone (reported wrong password every time), so my conclusion is that F2FS format process had messed up encryption. Formatting raw partitions instead of decrypted ones is my best guess, no time to confirm that now unfortunately... I've reverted phone back by wiping everything, restoring backup and encrypting everything again.
[Galaxy S 4 Mini Android Development] ne0zone75:
Well...

all my apologies because i had totally forgotten one of my TWRP build flags

: 'TW_CRYPTO_FS_TYPE := "ext4"' so if you do want to use encryption PLEASE DO NOT format any of your partitions to F2FS ATM, this filesystem is not currently handled when using encryption because of the above flag AND i do not know if F2FS could be specified in addition to EXT4 into it... :confused:

I do think that one workaround would be to switch completely to F2FS instead of having both EXT4/F2FS support from recovery BUT that will imply that you will need 2 versions of TWRP in order to switch from EXT4 to F2FS : one version like the current DEV branch one which will only be used to reformat EXT4 partitions to F2FS AND one version with ONLY F2FS support to flash and test out after having switched your partitions from EXT4 to F2FS... ;)

Please let me know what do you think about it...

Regards

PS : I've reported your various F2FS related issues back to [MENTION=912474]Dees_Troy[/MENTION] over PM...

EDIT : I've got an official answer ->

F2FS filesystem by itself is probably NOT compatible with crypto ! Please DO NOT TRY to use crypto over F2FS

! Thank you...
[Galaxy S 4 Mini Android Development] dulemars:
Hmm weird... Under Linux, block device encryption is completely decoupled from filesystem. It goes like this: You have some block device, let's say /dev/mmc0. Using cryptsetup or similar, you encrypt that device, and create a virtual device, let's say /dev/mapper/encrypted, which you can then format with any filesystem, mount and do whatever you please. Virtual device is decrypted frontend of your encrypted backend physical device.

Not sure if this applies to Android completely, but I'd take "F2FS incompatible with encryption" with some suspicion.
[Galaxy S 4 Mini Android Development] ne0zone75:
crypto over F2FS clarification !

Good afternoon,

Yes ! You are absolutely right ! I completely agree with what you said above BUT AFAIK it is not possible to specify to NOT format some place on a partition when formatting it to F2FS, therefore it is not possible to preserve the very end of a partition where the 'crypto key' is stored while formatting it to F2FS like it is the case with EXT4.

To summarize, i do think that you can use crypto over F2FS BUT DO NOT TRY TO FORMAT IT ! Furthermore, crypto is declared as EXT4 in my TWRP builds currently so if you reformat your '/data' from EXT4 to F2FS, then encrypt it from Android, this part should work BUT you will not be able to decrypt it for sure with my current TWRP builds in order to back it up !

Finally, my 'F2FS incompatible with encryption' statement was standing for its 'daily use' if i may say... what will you do with a '/data' that you cannot backup and where you will loose everything on it if you need to reformat it ? (a TWRP build where crypto is declared as F2FS would solve the first issue, not the second one...)

Regards
[Galaxy S 4 Mini Android Development] ne0zone75:
Device checking code is about to be removed from my flashable .zip files !

Good afternoon,

In order to make it easier for everyone to flash my TWRP builds .zip files from recovery (on GT-I9192 mainly...), i will remove ALL my device checking code from them ASAP ! :good:

There are updated screenshots in corresponding tab of this project BTW ;)

Very nice day :D
[Galaxy S 4 Mini Android Development] ne0zone75:
AIO builds (Full dynamic EXT4/F2FS support) from the DEV branch are close...

Good evening,

I am about to release updates for the DEV branch : AIO builds !

New feature are

:

-> automatic filesystem detection : courtesy of [MENTION=3261191]F4k[/MENTION]... Thank you !

-> full support of both EXT4/F2FS filesystems from within the same recovery image !

->

fixed adb functionality

: it now works as it should and is up once recovery is booted !

With AIO builds you will be able to swtich completely from EXT4 to F2FS easilsy

:

-> boot into recovery while all your partitons are EXT4 : /system, /cache and /data

-> convert any partition you do want from EXT4 to F2FS using the new feature present in recovery since TWRP 2.7.1.0

-> reboot to recovery : ALL your partitions should be available (EXT4 & F2FS ones)

-> flash a F2FS ready ROM : /system will be F2FS formatted ! (BTW, i will post an updated F2FS compatible 'updater-script' for my S4 mini ports ROM installers which are not F2FS compatible ATM...) (+ GAPPS + ODEXING script if you like)

With AIO builds you should be able to move from ALL-EXT4 to ALL-F2FS or any other mix !

Dev-Host download links will be updated on post number 1 in a few moments... :good:

Stay tuned ! :D

EDIT : download links are updated AND AIO builds do not have any device checking code from inside their 'updater-script' anymore ! ;)
[Galaxy S 4 Mini Android Development] mielletseed:
I tried the following:

installed the new DEV TWRP AIO

rebooted recovery

made a full backup

reformatted /system /data /cache to f2fs

restored /system /data /cache

Unfortunately I get following result:

Wiping Data...
Formatting Data using [B]make_ext4fs[/B] function.
Restoring Data...

Same for /cache and /system

So no way to restore data after converting the file system?

best regards
[Galaxy S 4 Mini Android Development] Ezylife:
Hello just flashed could not see external sdcard

GT I9195 - Carbon 4.4.3 - f4k Kernel
[Galaxy S 4 Mini Android Development] ne0zone75:
If you back up any EXT4 partiton, then you can ONLY restore it as EXT4 (that is the way TWRP is currently designed -> source : [MENTION=912474]Dees_Troy[/MENTION])

If you do want to restore any F2FS partition, then this one MUST be F2FS formatted before backing it up !

Regards

Well..., that is strange ! I do not have that issue : is your external microSD card 'vfat' formatted ?

Greetings
[Galaxy S 4 Mini Android Development] mielletseed:
Thank you for your quick reply. Maybe the file system is just a flag in the backup file (it backs up and restores file by file) so I will look later if I can change the backup file manually :)
[Galaxy S 4 Mini Android Development] Ezylife:
Yeah it's vfat.

GT I9195 - Carbon 4.4.3 - f4k Kernel
[Galaxy S 4 Mini Android Development] ne0zone75:
Well that is really strange since microSD is declared as 'vfat' as usual ! (on my 32GB 'vfat' formatted SANDISK class 10 microSD, it is working BUT that is not helping you that much... :confused: )

Is anybody else having issue with microSD ? Thank you for reporting back ! :good:

Greetings
[Galaxy S 4 Mini Android Development] Ezylife:
Sounds like we have the same card :)

GT I9195 - Carbon 4.4.3 - f4k Kernel
[Galaxy S 4 Mini Android Development] ne0zone75:
I did not have enough time yet to think about what is going wrong with DUOS. I will work on it very soon...

Thanks for your understanding

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] ne0zone75:
Hello,

I will try to narrow it down soon...

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] Harvey_Spectar:
waiting fir it.

thanks
[Galaxy S 4 Mini Android Development] IronRoo:
[MENTION=5280400]ne0zone75[/MENTION]

FYI in the OP where you say Tryouts 3.1.0 the link is pointing to the wrong post as it goes to the 3.0.3-3 post ....... I've been running that thinking I was on 3.1.0. as I suppose I didn't bother reading the actual text ..... doh!

Well the good news is that the 3.0.3-3 restores CM13 backups perfectly ;) (i9195 LTE)

Though I'm having trouble flashing LOS13 as "zip signature verification failed!"

see screen shot.

(ignore the md5 check in the first flash as I had copied an extra character before the actual code when I created the zip.md5 file, so it failed)

(edit: fixed MD5 but it's on latest LOS13 but also failing)
[Galaxy S 4 Mini Android Development] ne0zone75:
Okay, thanks for pointing that out : i will update OP post link for latest v3.1.0-0 TRYOUTs soon...

What is exactly your issue if i may and did you try v3.1.0-0 ?

Have a nice day

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] IronRoo:
Yes, just installed 3.1.0 and it flashed the same files fine no verification error.

Also back up of LOS13 worked as has restore of CM13 from backup made with 3.0.3-0
[Galaxy S 4 Mini Android Development] MODAR FN:
can I flash recovery by flashify??
[Galaxy S 4 Mini Android Development] ne0zone75:
Theorically yes. Use the .img file...

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] MODAR FN:
Thx man
[Galaxy S 4 Mini Android Development] ne0zone75:
Done !

?

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] NandoHiller:
twrp-3.0.3-0 restarts

Hello,

TWRP Recovery takes several minutes to start.

Custom-twrp-3.0.3-0-serranoltexx-STABLE.tar.md5.7z does not allow the system to start (prepared for startup -> reboot).

Does anyone have an idea for the reason?

Lineage 13 Nightly

Best regards
[Galaxy S 4 Mini Android Development] ne0zone75:
Hi,

Are you using adopted storage ? If so, it is the reason of your recovery booting time...

... try v3.1.0-0...

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] NandoHiller:
Hi,

SD-Card is formated to use as Internal-Storage.

I have tried v3.1.0-0. The System is booting. :)

The Recovery Boot-Time remains constant, very slow.

Best regards
[Galaxy S 4 Mini Android Development] _khianat_:
tnx

tnx sir all twrp is work tested 1000%:D
[Galaxy S 4 Mini Android Development] kwaxi:
Just flashed it and seems to work as designed, thanks for your effort!
[Galaxy S 4 Mini Android Development] Hugo9191:
I'm using 3.1. I used it to install the rom, everything went great. Now I'm trying to update the ROM and I'm unable to enter TWRP. It's basically frozen on the TeamWin picture for a few minutes, then it goes off.
[Galaxy S 4 Mini Android Development] ne0zone75:
I will answer to you very soon... meanwhile, could you please tell me if you did follow carefully instructions given in opening post and which is your S4 mini variant ?

Thanks

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] Hugo9191:
I did, made sure to uncheck the FTime thingy, flashed it with Odin and done. The result is always the same, just stays frozen on the teamwin logo. I tried flashing it again today, same result.

SerranoLTE btw
[Galaxy S 4 Mini Android Development] Freddynic159:
I have the same problem with version 3.1 in my serranoltexx. Version 3.0.3 works perfectly.
[Galaxy S 4 Mini Android Development] IronRoo:
& [MENTION=5750325]Hugo9191[/MENTION]

Just booted to TWRP 3.1 on my LTE, seems to be working.

I flashed 3.1 with 3.0.3 not via Odin, also I boot straight to TWRP using advanced reboot soft key after pressing power off button. What about you guys did you both use Odin to install, are you booting into TWRP with hard keys? Wouldn't have thought the latter would make a difference ........
[Galaxy S 4 Mini Android Development] IronRoo:
Did a little more testing of TWRP 3.1.0. On I9195 LTE

Backed up CM13 using compression. Reinstalled LOS13 from normal uncompressed backup made with TWRP 3.1.0, booted fine. Up dated LOS13 to latest nightly 0415, then created a backup of new LOS13 install. Then reinstalled CM13 from compressed backup. All good, working as expected, no extended boot times either, as reported by some.
[Galaxy S 4 Mini Android Development] Freddynic159:
Well, I have done everything as you say and now version 3.1 works perfect.

Anyway, I didn't know that this version could only be booted from the advanced reboot menu since with version 3.0.3 this was not necessary.
[Galaxy S 4 Mini Android Development] IronRoo:
Good to hear it's working for you. BTW I didn't mean you have to boot from advanced menu, you shouldn't have to do that, I was just putting up ideas for possible solution as mine was working properly but others weren't. Hopefully it will be something the devs can fix easily if it is indeed a reproducible bug
[Galaxy S 4 Mini Android Development] IronRoo:
When using new version of TWRP I was surprised to see a warning msg when backing up that the media partition would not be backed up! I had been under the impression TWRP did a full nandroid backup but it does NOT! So none of your photos, music, some documents etc are backed up by TWRP. Maybe it's because I only switched to TWRP about a year ago, but I had not realised this, and I'm not the only one judging from this

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/276

Luckily for me I have never had to do an emergency reinstall and I back up photos etc via other means & move photos from Whatsapp etc to external SD so have never had a major lose, a couple of items did go missing once though.

See the faq

https://twrp.me/faq/backupexclusions.html

So hope you are all aware that you MUST back up all your media etc using a different means as TWRP doesn't do it as the entire media partition is excluded.
[Galaxy S 4 Mini Android Development] csendre:
Not just media, the entire /data/media partition is left out from backup because this is what is called your internal SD. Same way, your external SD is not backed up either, to my knowledge it never was. As I recall it was the sane on CWM as well. These contain user data an can be quite large. You don't need recovery to create a backup for this, the content could simply be copied to a PC
[Galaxy S 4 Mini Android Development] IronRoo:
Yes, that's what I meant, sorry I wrote "folder", have now edited & changed to "partition".
[Galaxy S 4 Mini Android Development] mashardpro:
Good. Work with my old i9190. Thank you
[Galaxy S 4 Mini Android Development] kullino:
Just installed on my 9195 LTE.

Latest AICP 7.1.1, recovery was CWM.

Downloaded tryout zip, installed via recovery, reboot.

Only boot into recovery, seems to be Ok.

Big rhanks for your work. :)
[Galaxy S 4 Mini Android Development] ne0zone75:
You are more than welcome ? !

?

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] rogers11:
Hello, I've updated my wife's i9195 from 13.0 to 14.1. Which recovery should be used now: 3.0.3-0 (installed), 3.0.3-3 or 3.1.0? Many thanks.
[Galaxy S 4 Mini Android Development] GReddy4:
Keep up to date! 3.1.0 seems stable enough, with no problems at all!
[Galaxy S 4 Mini Android Development] IronRoo:
Yes, I agree with [MENTION=6611440]GReddy4[/MENTION] ver 3.1 is good, though it is a test build ....

(I got a zip verification error with 3.0.3-3 but the same Linage rom file flashed fine with updated TWRP 3.1.0 {& backup & reinstall worked also}, however your 3.0.3 TWRP seems to have flashed Linage just fine!)
[Galaxy S 4 Mini Android Development] waldfee:
I tried 3.1.0 on an I9195 LTE variant with adoptable storage and it doesn't seem to start (waited more than 10 minutes). TWRP is frozen on the splash screen. 3.0.3 however starts but also takes 2-3 minutes to show the menu.

On falshing the lineage ROM it seems to be stuck at about 30% of "patching system image unconditionally".

Any recommendation on how to proceed?
[Galaxy S 4 Mini Android Development] RedSkull23:
Flashed zip by TWRP 3.0.2.0, and for feeling sure after reading posts above, I've rebooted using the reboot sys command in recovery plus the input of the hardware keys during the startup. It immediately started without a problem, and it works in an excellent manner. Thanks for your work :)
[Galaxy S 4 Mini Android Development] IronRoo:
About TWRP, you don't say what you had before you installed 3.1 or how you installed, possibly reflash with Odin will fix both TWRP issues.

For ROM I'd first check the checksum of download, if bad download again. If good try wipe using TWRP then reboot back into TWRP only THEN flash ROM. If that doesn't work try TWRP factory reset (your pictures, docs etc will not be wiped) and if none of that works reinstall stock (you will lose your pictures etc)