yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Android Development] lOtz1009:
there are several guides you can find via web search.

e.g. http://blog.sam.liddicott.com/2016/02/android-6-semi-adopted-storage.html?m=1
[Galaxy S 4 Mini Android Development] ne0zone75:
TWRP TRYOUTs for S4 mini updated to v3.0.2-3 (NOUGAT enabled...)

Good evening,

You will find updated packages below. They are only available as flashable ZIPs like any other TRYOUTs. They are TRYOUTs because they are built from new android-7.0 OmniROM sources for TWRP along with CM-13.0 sources tree. Thank you for your feedback...

3G | DS | LTE

Happy flashing and please do not forget to report back about them in order to flag them as STABLE if they are working well !

PS : packages updated on 2016-10-17 ! I made some slight changes over yesterday's release and i switched 'busybox' sources repository from CyanogenMod to OmniROM one... let me know if the 'CM-14.0 backup / restore' bug reported by [MENTION=5416372]csendre[/MENTION] is history or not and if crypto. features are working properly. Thank you !
[Galaxy S 4 Mini Android Development] lOtz1009:
in the meantime you could flag 3.0.2-2 as stable.
[Galaxy S 4 Mini Android Development] ne0zone75:
Yes i could but v3.0.2-3 is a lot of commits ahead v3.0.2-2 and is built from new OmniROM android-7.0 TWRP sources. Also v3.0.2-2 is only a few commits ahead v3.0.2-1 which is reliable but lacks full CM-14.0 support (see [MENTION=5416372]csendre[/MENTION] feedback a few posts ago).

FYI, today TRYOUTs will likely have crypto. features broken. I am working on full crypto. support with them but i do not have any S4 mini to test them out before releasing...

Thanks for your understanding

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] lOtz1009:
LTE 9195

booting, backup, restore and zip flashing is working, file manager as well.
[Galaxy S 4 Mini Android Development] ne0zone75:
Thanks ! Are you running CM-14.0 or another custom ROM ? Backup / restore function was not working properly for CM-14.0 with previous builds...

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] lOtz1009:
aokp cm13
[Galaxy S 4 Mini Android Development] Whitest:
I'm on CM14, just did a fast backup of /data & /system and restored /system - working perfectly fine here. Thanks for supplying us with updates neo
[Galaxy S 4 Mini Android Development] ne0zone75:
You are welcome. Thank you for your feedback !
[Galaxy S 4 Mini Android Development] glkanth77:
I had tested on duos 9192 I had flashed AOKP N test rom did complete backup and restored I have phone fc's with no sim card detected
[Galaxy S 4 Mini Android Development] ne0zone75:
Okay. Of course your custom ROM was working well after a clean flash isn't it (only your restored TWRP backup is affected by this issue...) ?

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] glkanth77:
Yes Bro
[Galaxy S 4 Mini Android Development] csendre:
I can confirm, backup and restore still not working well on 9192 with CM14 or AOKP-N. com.android.phone fc, RIL dies and also, developer options stop working
[Galaxy S 4 Mini Android Development] ne0zone75:
Can anybody report back about the recovery backup / restore function of 3G and LTE S4 mini variants with latest TRYOUTs and CM-14.0... Is GT-I9192 the only variant affected by this issue (telephony and developer options FCing + RIL broken...) ?!

Thanks

PS : i will try to build next TRYOUTs along with CM-14.0 sources tree...

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] Woivod:
On 3gxx recovery and backup works fine(cm13)
[Galaxy S 4 Mini Android Development] ne0zone75:
Or simply because they cannot own every single Android device that is out on the market... ;)

Regards

Sent from my GT-I9195
[Galaxy S 4 Mini Android Development] Wildfear:
So far so good, tested wyping, backup and restore and flashing all new CM11 for our i9192 without any bug.

The only thing is the device name reported by the "assert" command that obviously get i9195 props.

if you could make a specific file/build for i9192 it might help ;)
[Galaxy S 4 Mini Android Development] ne0zone75:
Great news ! When i will release updates of both STABLE and DEV branches (maybe this W.E. i think...) of my TWRP builds, i will turn the GT-I9195 .zip flashable file into a GT-I9195/2 one with adjusted device checking in order to match both devices. The GT-I9195 .tar.md5 zipped archive will also be renamed accordingly.

BTW, AFAIK the GT-I9192 is not featuring LTE... did you gave a try to the GT-I9190 version of TWRP that i am sharing on your GT-I9192 ?! Anyway, because mobile network is far from used in recovery... ;) that is not really important but it would be interesting, just to see which of my current TWRP build behaves the best on GT-I9192...

Thanks a lot for having took some of your time to review it on your GT-I9192 :good:

Greetings

Sent from my GT-I9195
[Galaxy S 4 Mini Android Development] ne0zone75:
ALL my TWRP for GT-I9195/0 builds are now updated to v2.7.1.0 !

Hello all,

Today i am releasing TWRP 2.7.1.0 builds for both STABLE and DEV branches. Both download sources links (Dev-Host on post number 1 and xda downloads tab) are now updated :good:

You will find TWRP 2.7.1.0 changelog below (grabbed from official TeamWin website) :

Best regards
[Galaxy S 4 Mini Android Development] mielletseed:
[MENTION=5280400]ne0zone75[/MENTION]: Is one of them for i9192 too as described above? The file name has not changed.
[Galaxy S 4 Mini Android Development] ne0zone75:
Hello, Yes ! all my updated GT-I9195 TWRP builds should work on GT-I9192 as previous ones have been reported back as working on it... :good:

With that said, i am currently awaiting feedback on my GT-I9190 builds about their compatibility with GT-I9192 BUT i do not see ATM why they would not be compatible with it too because AFAIK GT-I9195 & GT-I9190 kernels only differ with their LTE/3G support...

As soon as it will be clear for me, i will update post number 1 accordingly.

Feel free to report back any issue that you might experience with them on your GT-I9192. ;)

Kind regards

Sent from my GT-I9195
[Galaxy S 4 Mini Android Development] mielletseed:
Thank you very much. I could install the version for i9195 but not for i9190 because of the device check (have no time to edit the zip now and have no ODIN here).

But I have an other question. The ZIP for i9195 is the only one I could install directly. For all other files the device check fails. It says "This file is for 'xxxx' but your device is a '.'"

It really shows only a period, no 'seranods' or 'seranodsxx'. So I always have to edit the ZIP files an remove the device check. That's a little bit annoying. Do you have a glue what I messed up with my device? Where is teh device string read from (getassert), from the build prop?
[Galaxy S 4 Mini Android Development] ne0zone75:
The device checking reads the string which matches 'ro.product.device' from inside your '/system/build.prop' file...

If you have some freetime to test out my new builds on your GT-I9192, i could remove device checking completely on both builds of each branch and make them temporarily available for download...

Just let me know about it... ;)

Greetings

Sent from my GT-I9195
[Galaxy S 4 Mini Android Development] mielletseed:
When I first went to CM11 I installed your recovery vio ODIN first and then wiped system. Could it be, this was wrong?

Since I have CM11 installed, there is a valid /system/build.prop (when system is mounted). Could it be it is read before mounting? Should I copy a build.prop to the unmounted /system folder? I will try that!

I hope, I can check on weekend. I know how to disable the device check so I don't need other builds than yours. I'll just edit the install script inside the zip. But thank you! :)
[Galaxy S 4 Mini Android Development] ne0zone75:
No ! Your '/system' has been reflashed with CM 11.0 since, no problem at all ;)... and i do think that you shoud NOT modify your current build.prop file unless your current CM 11.0 version is not specifically targeted to GT-I9192...

You will be able to read 'build.prop' content from Android once booted into it with any text editor...

Finally, thank you for testing my builds out on your GT-I9192, i really appreciate ! :good: :D

EDIT : I've just gave a look at my device checking code and IT READS 'ro.product.device' AND 'ro.build.product' and compares both to any predefined value i've set; if it does not find any matching predefined value then it stops the script AND displays 'ro.product.device' ONLY, so it it finds only an 'unkown' 'ro.build.product' value THEN it will look like to what you are getting...
[Galaxy S 4 Mini Android Development] spanish33:
Thanks waiting for kernel support to test the f2fs options.
[Galaxy S 4 Mini Android Development] Darktitor:
Hi :D

Anyone has got a good TWRP theme for our device resolution ? I can't find one x)

Envoyé depuis mon Eee PC 1000H avec Tapatalk Pro
[Galaxy S 4 Mini Android Development] F4k:
Nor even here?
[Galaxy S 4 Mini Android Development] Darktitor:
Thanks a lot I'm think I'm blind x)

Envoyé depuis mon Eee PC 1000H avec Tapatalk Pro
[Galaxy S 4 Mini Android Development] spanish33:
[MENTION=5280400]ne0zone75[/MENTION] no f2fs capability in your latest dev build?
[Galaxy S 4 Mini Android Development] ne0zone75:
Good evening,

Currently, there is no F2FS support at all for both branches of each device of my TWRP builds and i am wondering if i will add it someday... [MENTION=3261191]F4k[/MENTION], AFAIK, is already providing F2FS support in his recovery builds and that make sense to me because F2FS needs a compatible kernel and latest f4ktion kernel is F2FS enabled...

I am targetting my TWRP builds for the average user ATM, a user who wants to flash a custom ROM like my SlimKAT ports and maybe to stay with embedded kernel or to flash a custom one over it without pushing his device to its hardware limits...

With that said, i do know that my SlimKAT ports (S4 mini + Transformer Pad series) are running really well since i build them with Linaro GCC (ROM + kernel) with 'JA' optimizations applied :good: :D and even better when using F2FS, so i may add F2FS to my TWRP builds one day finally BUT i've decided of nothing ATM.

Kind regards

Sent from my TF701T
[Galaxy S 4 Mini Android Development] dulemars:
F2F2 would be awesome, I'm hoping that you will add it once :) If you add it, your recovery will be pure perfection :)
[Galaxy S 4 Mini Android Development] MarkAndroid.UK:
Sounds very familiar! Just about to flash 2.7.1

:cool:
[Galaxy S 4 Mini Android Development] ne0zone75:
F2FS functionality added to DEV branch of each device !

Good afternoon,

I've implemented F2FS ONLY in the DEV branch of each device, ... after all this is a testing branch ! :p

To achieve this i've added F2FS support to CyanogenMod's kernel that i am using to build TWRP : THIS PART IS EXPERIMENTAL ! Then i turned ON F2FS support while building the recovery (dedicated TWRP build flag...).

Any feedback on it will be very appreciated ;) BUT please, be very carefull if you decide to test it out ! Thank you !

I've also modified my buggy 'device checking' EDIFY script from inside my flashable .zip files, as a result GT-I9192 users should now be able to flash both versions of the DEV branch :good: Thanks a lot [MENTION=5522383]mielletseed[/MENTION] for pointing that out ! :D

EDIFY script of both STABLE branches will be updated ASAP !

Very kind regards
[Galaxy S 4 Mini Android Development] ne0zone75:
STABLE branch of each device will remain as it is : STABLE ! ;)

Nice W.E. to you !
[Galaxy S 4 Mini Android Development] csendre:
We need feedback on CM-14. All MM builds work well
[Galaxy S 4 Mini Android Development] ne0zone75:
New TRYOUT release !

You will find updated ZIPs from updated post #1167.

Changes over yesterday's release are slight, except for 'busybox' sources which have been switched from CyanogenMod repository to OmniROM one : since 'busybox' is a critical component of a TWRP image, this move may fix the 'CM-14.0 backup / restore' bug reported by [MENTION=5416372]csendre[/MENTION] but it is just a guess...
[Galaxy S 4 Mini Android Development] csendre:
I tried restoring a previous backup, it didn't work with that. Will try a backup/restore cycle as well. Will also send you a PM with further info

Update: Tried a full backup/restore cycle as well on CM-14, unfortunately the same result
[Galaxy S 4 Mini Android Development] glkanth77:
Backup and restore is working well with mm builds
[Galaxy S 4 Mini Android Development] ne0zone75:
Good evening,

I've asked for assistance from [MENTION=912474]Dees_Troy[/MENTION] about the NOUGAT ROMs bug... i am waiting for his answer...

Regards
[Galaxy S 4 Mini Android Development] rayzen6:
We at galaxy s5 aka klte had this problem, and now its solved by our maintainer. No bugs or fix needed in recovery I guess. His quote is here needs fix for symlinking issues in device trees.

Quote

Selinux enforcing

You *should* be able to nandroid restore this and later builds and still have telephony. The problem was Android trying to "upgrade" the symlinks we have to create in order for our blobs to find the critical telephony databases and APNs -- the blobs have them hardcoded and Android 7.0 moved the location.

Hope this help maybe for Serrano too. I'm sure arco68 is aware of this,it'll be fixed soon I hope:)
[Galaxy S 4 Mini Android Development] ne0zone75:
Thanks a lot for this ?! So, if i am following you right, this bug is a ROM side issue ?

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] rayzen6:
Yes for klte it was a solution on ROM side. But let's mention [MENTION=3044346]arco68[/MENTION] here. He I think is knowing about that.
[Galaxy S 4 Mini Android Development] ne0zone75:
Okay

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] glkanth77:
Yep I think [MENTION=700912]arco[/MENTION] is currently working on it
[Galaxy S 4 Mini Android Development] csendre:
Thanks Dude, good to see you are still following S4. Would it be possible for you to ask for a link to the commit that fixed the issue for the klte?
[Galaxy S 4 Mini Android Development] rayzen6:
https://review.cyanogenmod.org/#/c/160957/

I think that's the commit. But lemme ask our dev 1st.
[Galaxy S 4 Mini Android Development] ne0zone75:
Latest TRYOUTs and crypto. ?

Does anyone have feedback about crypto. features of latest TRYOUTs ?

-> decrypting a crypted partition

-> encrypting a backup and restoring it...

I modified my TWRP crypto. build flags so i am wondering if it is working properly and once 'NOUGAT backup / restore' bug will be confirmed as a ROM side issue, i will need crypto. feedback in order to flags them as STABLE...

All the best
[Galaxy S 4 Mini Android Development] csendre:
Yep, this was it. We only had it partially. Thanks a lot!!!
[Galaxy S 4 Mini Android Development] rayzen6:
My pleasure :)
[Galaxy S 4 Mini Android Development] csendre:
I can confirm now the backup/restore issue is ROM side. I will build a new test CM-14 for folks on the DS and maybe someone can confirm then if crypto works.
[Galaxy S 4 Mini Android Development] ne0zone75:
Your help is more than greatly appreciated on this issue. Thanks for clarifying it out ? !

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] erniesan82:
It did what I neded it for on a I9195L from telcel (Mexico) thank you good Sir.
[Galaxy S 4 Mini Android Development] kevinarol93:
Backup and Restore works well with CM13 the process seems more fast than previous version of the recovery but restoring a CM14 backup brake the phone app. I can't tell you anything about crypto because I don't use it.

S4 Mini i9190 3G
[Galaxy S 4 Mini Android Development] ne0zone75:
Allright, thanks for reporting back. The CM-14.0 backup / restore bug has been confirmed a few days ago as a ROM side one which is affecting all NOUGAT based ROMs as long as a specific commit is not applied to the S4 mini device tree of the target ROM.

You will find more info. about it a few posts back.

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] kevinarol93:
Thanks ????
[Galaxy S 4 Mini Android Development] KnightofTheHell:
Green Screen when trying to open recovery

after i installed twrp v3 for my i9190 when i tried to open it with volume up+power+home the screen with logo and s4 text comes after that all the black background turns to green slowly.
[Galaxy S 4 Mini Android Development] ne0zone75:
Good evening,

Please post a picture of it... it is surprising...

Is this issue affecting someone else please ?

Tapatalked from my OnePlus 3

PS : which package did you flash to your device ? STABLE or TRYOUT ?
[Galaxy S 4 Mini Android Development] KnightofTheHell:
Here's a video of problem

https://youtu.be/OXstpxaBWKk

I flashed stable one from odin because of first time.
[Galaxy S 4 Mini Android Development] kevinarol93:
I have the same model (i9190) using the TRYOUT version and don't have that issue, maybe hardware problem?
[Galaxy S 4 Mini Android Development] ne0zone75:
Well... what kind of ROM are you using and are you able to boot properly into it ? Also, is download mode still available (by pressing and holding 'VOL. DOWN' + 'PWR' buttons) and which is your 'Odin' version ?

My advice to you is to :

-> download latest 'Odin' version for S4 mini from here (v3.11.1) and ensure that you have latest SAMSUNG USB drivers installed on your PC...

-> download my latest 'Odin' ready TWRP package again (STABLE or TRYOUT)...

-> flash my file to your device one more time through 'Odin' by following instructions from post #1 AND do not forget to apply step 6 !

Let us know how it goes once it's done...

FYI this kind of issue is likely kernel related...

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] KnightofTheHell:
Download mode is available

Using stock rom

Used v3.11.1 Odin

Downloaded latest Odin ready TWRP package

Applied your instructions from first post letter by letter and the result is same

I dont really dont think so because i can use cwm properly but i cant use phillz touch and twrp.
[Galaxy S 4 Mini Android Development] ne0zone75:
Well, i do not think that this behavior is caused by a hardware fault either. What you can try next is to install CWM through 'Odin' and if it is working properly, then flash my TWRP installer for your S4 mini variant from CWM, even if i do not recommend this method in opening post ?.

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] KnightofTheHell:
Just now i tried the tryout version from flashing in cwm and now it says recovery warranty void.... after that screen goes black phone vibrates and reboots.
[Galaxy S 4 Mini Android Development] ne0zone75:
Are you using the latest stock FW for your device ? If it is not the case, you can download it from SAMMOBILE website (carefully select your country and provider) or through SAMSUNG 'Kies'... but please prefer the 'Odin' way...

Your issue sounds to me like an outdated bootloader problem...

If your stock FW is up to date, then please use CWM instead of TWRP if you want to use custom ROMs anyway BUT please be very careful before trying to flash one because it may not work !

What is the issue with 'Philz CWM' ?

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] mielletseed:
Are you really sure you have the correct device? Not the newer version with different hardware (SoC)? To me it sounds like you are flashing a wrong software to your device ...

What's the exact model number of your device?
[Galaxy S 4 Mini Android Development] ne0zone75:
It seems to truly be a S4 mini 3G, according to the posted video. below and also, when i was owning a GT-I9195 and playing with it, i already experienced this kind of issue but i do not clearly remember in which circumstances...

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] csendre:
[MENTION=5280400]ne0zone75[/MENTION] There are still issues with restore on Nougat based ROMs. I have no clue at this point if this is a CM, TWRP or device issue. On the DS I am loosing settings and all SMS messages upon restore. Would it be possible to ask around in the TWRP community to see if they encountered this on other devices? Thanks!
[Galaxy S 4 Mini Android Development] ne0zone75:
Okay, i will try to have [MENTION=912474]Dees_Troy[/MENTION] point of view about this through IRC ?.

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] Claudio4780:
Got it running on my DS without problems. Thanxxx
[Galaxy S 4 Mini Android Development] ne0zone75:
Good evening all,

I am quickly posting this message to let you know that i will try to gather info. about the 'CM-14.0 backup / restore' TWRP bug of my S4 mini recovery images over IRC ASAP. Does anyone have any news about it ?

Also, i still do not have any crypto. feedback about latest TRYOUTs...

This is why they are not flagged as STABLE...

Happy weekend

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] Lucifer.S:
Some one share me twrp 3.0.2.1 recovery flashable

---------- Post added at 12:01 PM ---------- Previous post was at 12:01 PM ----------

I9192
[Galaxy S 4 Mini Android Development] Smeagal192:
Using I9195, backup/restore and factory reset all worked as expected :good:
[Galaxy S 4 Mini Android Development] ne0zone75:
What do you mean ?! It is available from opening post : AFH download link...

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] ne0zone75:
You are using CM-14.0 right ? If so, it is interesting...

Thanks for your feedback.

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] Smeagal192:
Yes on cm14.0 7.1 nougat 20161107 by Arco68, going to update to yesterday's release the 12th, if anything changes will report back.
[Galaxy S 4 Mini Android Development] ICrusaderI:
ok i have a problem here i have a I9195

i downloaded odin and img recovery file the custom TWRP v3.0.2-1 MM enabled for S4 mini (LTE variant AKA GT-I9195) | STABLE (2016-04-13) :

now i follow odin instruction and it restart well with Twrp interface.

i wiped everything and then i copied the unzipped file with inside the recovery.img file from the Desktop to the phone.

Then i pressed install from the menu and i choose the internal storage directory and i choose the img file, i said OK and i told him to flash BOOT.

It says ok then i do a Reboot system , it ask me if i want to activate the supersu user and i said ok... i wait it restart and then it goes back to TRWP menu.....

What am i doing wrong?!!!
[Galaxy S 4 Mini Android Development] ne0zone75:
I am not sure to follow you right...

-> you installed my 'Odin ready' TWRP package suitable for your device : custom recovery is properly installed on it as a result...

-> i am not understanding what you did next : which flashable ZIP did you "forced" to flash to /boot. I put quotes because it is not possible to do so as is...

If installing SuperSU was your goal, then you should have downloaded latest SuperSU archive from [MENTION=631273]Chainfire[/MENTION] dedicated Web page and finally flash it to your ROM. Of course, there is an option to install SuperSU installer directly from TWRP because it is embedded into it but IMO it is a better way to proceed like i just said above...

Let me know if you need further assistance,

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] koutsman7100:
because it is the first time that i use twrp in cm14.1 by arco68,could you tell me what to wipe after every update except dalvik and cache,not to do any foolness??

i had before the cmw and knew the steps....here there many settings and i am afraid of doing something wrong....thank you