yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Android Development] arsm74:
I have been using this on the i9192 for a few days and it seems OK so far
[Galaxy S 4 Mini Android Development] GioBasi:
Just did backup/restore RR 5.8.0 DUOS with TWRP 3.03.1 and No sim cards. Else few things like settings opening delay and lose UI config power menu and status bar.
[Galaxy S 4 Mini Android Development] ne0zone75:
Okay, thanks for reporting back :good:

I will work on this backup / restore issue affecting N custom ROMs these days...

Any help on this will be greatly appreciated ;)

Stay tuned

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

Now I turned on airplane mode on RR 5.8.0 and then backup/restore sim cards are works after restore when turn off airplane mode. with out errors.

reset some settings status bar , power menu and messages ( google message) as usually.

9192
[Galaxy S 4 Mini Android Development] ericlnu:
TRYOUT version working well. Still have the slowness with adopted storage, but less so. Thumbs up and thank you.

S4 mini LTE.
[Galaxy S 4 Mini Android Development] JHAM2005:
It works perfect, thank you for sharing it.

GT-I9195
[Galaxy S 4 Mini Android Development] arco68:
Thanks again for providing these images.

Since there's on-screen nav buttons, I got one hint for disabling the hardware keys, if you want to implement it in the recovery. Writing 0 to /sys/class/sec/sec_touchkey/touchkey_enable will disable them. Should be easy to achieve in a script or rc file.
[Galaxy S 4 Mini Android Development] Whitest:
Just for the record, v3.0.3-1 TRYOUT working fine here (except the known backup/restore bug with N) I am running latest LineageOS 14.1 Test build by arco.

flashing ROMs, Kernel, SuperSU, recovery, patches, Wiping, File Manager: all good.
[Galaxy S 4 Mini Android Development] DonQuichotte:
Hello,

also just like to report back, that restoring backup of LOS 14.1 is still broken...at least for me. ROM settings are gone and Baseband unknown.

Phone: serranoltexx

...bye DonQ
[Galaxy S 4 Mini Android Development] ne0zone75:
By images you do mean files ? Your message is intended to me right? I am quite busy right now but i will work on my S4 mini TWRP port project very soon again.

Cheers

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] arco68:
Yeah it was for you, and by images I meant the TWRP images. :)

I'm actually working on adding TWRP support directly in the upstream sources.

https://review.lineageos.org/#/c/159000/
[Galaxy S 4 Mini Android Development] ne0zone75:
Okay. Great. ?

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] pidi123987:
I'm currently using the latest test version, working wonderfully

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

I haven't had much time lately, but I did some testing with v3.0.3-1-TRYOUT.serranoltexx.

I used with aokp_serranoltexx_nougat_unofficial_2017-02-01_2052.zip

Install works normally.

Wipe functions work normally.

Backup works normally(I backed up default partitions(system, data and boot))

I then formatted /system, /cache and wiped /data/data, and dalvik/art cache

Restore worked without error. After rebooting back into system, all settings are restored perfectly: My display settings are as they were before, developer settings were still "unlocked" and all settings there stayed as I set them.

Next I will test encryption and f2fs.....
[Galaxy S 4 Mini Android Development] ne0zone75:
[MENTION=6418283]noppy22[/MENTION] : thx for your feedback ?

[MENTION=3044346]arco68[/MENTION] and [MENTION=535343]all[/MENTION] : at least latest TWRP TRYOUTs for S4 mini seem now to be working with latest AOKP installer.

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] cellardoores:
backup

backup

twrp 3.0.3-1 tryout

lineage-14.1-20170130-unofficial-serranoltexx

no gapps

made a backup of system, data and boot

wiped system, cache and data + dalvik/art cache

restore without errors

booting into system with no errors

all settings restored perfectly

no errors

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

So after a few days of testing I found there is a problem with encryption in the TWRP 3.0.3-1 TRYOUT.

From AOKP 7.1.1 thread:

After this, I performed a clean flash(also formatted /data, which may be part of the issue) without gapps and got a soft reboot and no encryption. [MENTION=5416372]csendre[/MENTION] tested and confirmed this later in that thread(he switched to CWM and it worked).

I then reflashed the TWRP 3.0.3-0 to test, rebooted to recovery and did another clean flash(including formatting /data). After the initial boot, I changed a few settings and encrypted and encryption was complete in a few minutes. Rebooting back to TWRP 3.0.3-0, it asked for the password and was decrypted successfully.
[Galaxy S 4 Mini Android Development] ne0zone75:
Dear noppy22,

IMHO, there is no crypto. bug at all in my latest TWRP TRYOUTs for S4 mini...

Nevertheless, i will wait for them to work properly with AOKP before definitely flagging them as STABLE.

Big thanks to you for feedbacking about this problem.

I just saw that i've got new PMs and you can contact me over it anytime you want, like anybody else.

Huge regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] ne0zone75:
I did not forget you at all ?.

Since my TWRP packages for GT-I9192 are built the same way as for 3G and LTE, they should work properly with latest N custom ROMs that are working with serrano3gxx and serranoltexx.

Anyway, device in my latest TWRP TRYOUTs for S4 mini DS is identified as serranodsdd... maybe it is something else in your RR installer.

Regards

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

Thank you.

Right now my s4 mini 9192 is dead 2 weeks already (emmc probably)

I hope to change logic board and then will try to start testing again.

Thank you for your attention. ;)
[Galaxy S 4 Mini Android Development] ne0zone75:
Hello [MENTION=535343]all[/MENTION],

arco68, noppy22 and csendre identified a typo in my GitHub sources. I will fix it ASAP. Meanwhile, please wait before syncing and starting to build TWRP for S4 mini.

Huge thanks to everybody. My TWRP 3 project for SERRANOs should finally become STABLE soon...

?
[Galaxy S 4 Mini Android Development] :
Thank you for your support for the S4 mini. :good:
[Galaxy S 4 Mini Android Development] ne0zone75:
[MENTION=3044346]arco68[/MENTION],

I would like to thank you for having took the time to check my sources over GitHub ?. I am quite busy ATM. That is why i am really grateful for it. Everybody rock.

My best regards,

Nicolas

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] arco68:
No problems.

Be careful with the 3.0.3 sources. It has some issues, so at the moment I'm building TWRP from this repo: https://github.com/mdmower/twrp

It requires an update to the fstab format though, which I made here: https://review.lineageos.org/#/c/160997/
[Galaxy S 4 Mini Android Development] ne0zone75:
Okay thanks. I will be more careful now ?.

Cheers

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] sillet91:
Hi, how are you, I would like to know if the twrp recovery for the 9192 model is already stable, and if it is, which one?
[Galaxy S 4 Mini Android Development] ne0zone75:
TWRP v3.0.3-2 for S4 mini is built !

Hello,

New installers are available now over AFH. It should work great (thanks [MENTION=3044346]arco68[/MENTION], [MENTION=5416372]csendre[/MENTION], [MENTION=6418283]noppy22[/MENTION], [MENTION=6614989]jason972000[/MENTION]). Everything present in earlier images is still here in new ones (except bugs i hope...). I removed foreign languages availability in order to meet recovery image size requirement. That's it !

-> 'Odin' ready files

3G | DS | LTE

-> flashable ZIPs

3G | DS | LTE

Enjoy, :fingers-crossed:...

PS #1: as always, 'Odin friendly' packages will come later...

PS #2: my GitHub sources are almost up to date but not completely... it will be done very soon...
[Galaxy S 4 Mini Android Development] mfPPC:
Thank you for your work.

This version is very slow to boot into recovery, its just me or anyone else noticed that?
[Galaxy S 4 Mini Android Development] ne0zone75:
It is certainly because recovery kernel is XZ compressed... ramdisk is LZMA...

I will try to enhance this part later...

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] figaro972:
Does not start.

Hello!! I have followed these steps to the letter:

Turn your device OFF.

Press AND hold 'PWR' + 'VOL. DOWN' + 'HOME' buttons.

Connect your USB cable and press 'VOL. UP' button to confirm that you want to enter into DL mode.

Start Odin, uncheck "F. Reset Time", and then click 'AP' button.

Select my 'recovery.tar.md5' file that you previously extracted from my 7zip archive and press 'Start' button. The phone will reboot when finished.

When the phone begins to vibrate just before rebooting : IMMEDIATELY press and hold 'VOL. UP' + 'HOME' buttons to boot straightly into your new recovery. <= THIS LAST STEP IS NEEDED ONLY ON SOME S4 MINI DEVICES TO ACHIEVE THE FLASHING PROCESS SUCCESSFULLY.

Odin shows me "Pass" in green, it shows me an animated android for a second and then "no command".:(

Any Suggestion?:rolleyes:

Thank you.
[Galaxy S 4 Mini Android Development] icero:
The last update is only via recovery, the odin version is not yet available 3.0.3-2
[Galaxy S 4 Mini Android Development] figaro972:
But now, I ran out of recovery, not accessing the menu.:crying:
[Galaxy S 4 Mini Android Development] icero:
Download odin version from the op for your model and install ..... Then from there you can upgrade to the latest version
[Galaxy S 4 Mini Android Development] ne0zone75:
'Odin ready' packages for v3.0.3-2 will be out later this morning .Meanwhile, please try to delete / move your .twrps located in /TWRP from /DATA and once done launch recovery mode. It will be recreated to default. If this is better like this, then your .twrps was corrupted. If this is not better, it is something else...

Tapatalked from my OnePlus 3

PS : 'Odin' files will be online in a few hours... going to work now ?.
[Galaxy S 4 Mini Android Development] ne0zone75:
Post #1315 is updated with 'Odin ready files, you will find it here.

Any feedback about v3.0.3-2 TRYOUTs ?!

Regards
[Galaxy S 4 Mini Android Development] mfPPC:
Installed gapps with it ok, didn't try anything else yet.
[Galaxy S 4 Mini Android Development] pidi123987:
Encryption and f2fs doesn't work unless I resize the mmcblk0p24 partition to include room for the footer manually

Ext4 partition have a resize button to fix this, can this be included for f2fs also?

Thanks
[Galaxy S 4 Mini Android Development] ne0zone75:
Okay. It will be done.

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] :
Haven't had a lot of time, but the basics definately work as intended(I flashed aokp_serranoltexx_nougat_nightly_2017-02-11.zip and open_gapps-arm-7.1-nano-20170211.zip in one go after a full wipe and no issues).....

I will test backup/restore and encryption in the next few hours. Anything else you want tested?
[Galaxy S 4 Mini Android Development] ne0zone75:
If you do have enough time, please test EXFAT + NTFS for removable devices (microSD card + USB OTG).

Thanks

NB : i will create a poll very very soon in order to know which features you need the most in addition to the basics because a XZ compressed kernel is the only way ATM BUT it is slow to boot like it has been reported. I would like to get a LZMA compressed kernel back BUT it is likely mandatory to remove some extra. features in order to do so.

If a kernel guru is ready these lines, maybe he / she can give me some good advice to keep all features BUT with a normal recovery booting time.

Re-thanks

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] :
[MENTION=5280400]ne0zone75[/MENTION]

I tested backup and restore and as with 3.0.3-1, no problems. Encryption works without any issues as well

I also tested the filesystems you mentioned for sd card. ExFAT worked well both in TWRP and android(AOKP). I formatted from vfat in TWRP.

NTFS had no option to format from TWRP, so I formatted from windows(PC). Interestingly, TWRP recognized the sd card and I could flash from it no problems, but in android the sd card was "unsupported" and prompted me to re-format into a recognized filesystem. ES file explorer didn't recognize it either. For OTG, I don't have anything to test this with, my apologies.

Provided someone could confirm OTG working, IMHO this could be considered "stable". Thank you again for your work :)
[Galaxy S 4 Mini Android Development] ne0zone75:
Allright. I thank you for your time with this task ? ?.

1 -> core TWRP features seem to work well.

2 -> ExFAT is working well : this FS should be used with large microSD cards and can store large files (both with TWRP and Android).

3 -> NTFS should be used with USB OTG ONLY : it allows the user to connect a large external HDD to his phone when this HDD id usually plugged to a Windows PC (this is useful to copy large files between the smartphone and the computer : backups, movies, pictures, etc... to store them securely away from the mobile phone). User should not use NTFS with microSD, only with USB OTG...

i will wait a few days to get feedback about USB OTG feature.

Finally i do agree with you that v3.0.3-2 should become STABLE ? ✌️ ?.

Cheers ?

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] pidi123987:
I have an issue with encryption and f2fs.

I first have to resize the data partition to allow for the 16kb crypto footer. After doing this, the encryption process seems to work, until it asks me to enter the password.

Entering the password it just shows the boot animation again indefinitely (I left it for 30 minutes, nothing happened).

I'm not sure if this is a twrp issue or ROM issue.

I should add that I'm using the latest Marshmallow version of AICP from around September 2016. Clean flash, and no gapps.

The only way to recover from this was to format the data partition again, using the format data option.

One thing I also noticed is that twrp also complained about not being able to find the crypto footer.

All other stuff in twrp works fine, I make daily backups and restores between 2 ROMs, no problems, without encryption.

I have not tried ext4 encryption, but there definitely is some issue with f2fs and encryption.

Cheers
[Galaxy S 4 Mini Android Development] xTr3Me123:
Hello together,

I own a Galaxy S4 Mini I9195 and its currently stuck in a bootloop.

The problem is that I cannot boot into the recovery mode. I tried to flash various TWRP versions etc but nothing helps me to get into recovery mode.

Can somebody help me with this problem? It seems that I cannot flash anything at all with ODIN because it says something like write protection enabled after trying to flash something...

I would be really happy if someone could help here...
[Galaxy S 4 Mini Android Development] wartomato:
Try ext4 encryption...First.

Btw, our latest AICP MM build was on 30th October... ;)

Encryption on CM or lineageOS based ROM with f2fs has always been a hassle...
[Galaxy S 4 Mini Android Development] pidi123987:
Yes I was gonna try ext4 tonight, but I have a lot of data on this f2fs partition, is it wise to just flash it onto a ext4 and continue using it?

Btw can you send me a link to the October build?

I always like to have the latest builds :)

Edit: latest I can find is 29 September 2016
[Galaxy S 4 Mini Android Development] wartomato:
I hope I still have... We began working on nougat while the servers crashed...

And I do not think it is wise to just flash it on ext4... But hey, I would at least try...Risky business.
[Galaxy S 4 Mini Android Development] pidi123987:
So I tried it with ext4 still same problem.

I've also tried using command line from twrp to encrypt, but there I got a segmentation error when running the following command:

set enforce 0

cd system/bin

Vdc cryptfs enablecrypto wipe password password

Any help would be greatly appreciated.

PS : hope you can find that version for me.

Thanks
[Galaxy S 4 Mini Android Development] csendre:
Which TWRP version are you using? Earlier versions had a bug and crypto folder was not created but you should not have any issues on last build, nor should you have to resize any partitions. I successfully encrypted on both AOKP and Lineage. There are no issues.
[Galaxy S 4 Mini Android Development] pidi123987:
I'm using the latest tryout version 3.0.2.-2 ?

I did actually get it to encrypt in the end using the command line :

setenforce 0

vdc cryptfs enablecrypto wipe password password

But twrp couldn't mount the data partition complaining it couldn't find the footer.

This was on an ext4 partition and aicp 6.0.1
[Galaxy S 4 Mini Android Development] ne0zone75:
Hi and sorry for answering such lately,

Did you follow 'Odin' flashing instructions from opening post ? There is a QUICK ODIN HOWTO section in OP...

Let me know if you need further assistance...

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] pidi123987:
Ok so something is broken in the latest tryouts when it comes to encryption, twrp is unable to find the crypto footer.

I reverted back to 3.0.3.0 and its working now.
[Galaxy S 4 Mini Android Development] :
Can you be more specific about what you have done? Filesystem, rom + android version, what is not working? etc, etc

I have tested encryption on stock filesystem with aokp 7.1.1 from 11 feb(TWRP 3.0.3-2-tryout) and I don't have any issues......
[Galaxy S 4 Mini Android Development] pidi123987:
Ok so I clean flashed the latest AICP nougat from 12 feb.

All partitions are back to stock ext4 (data + cache).

When i try to encrypt using the settings menu, it just soft reboots and nothing is encrypted.

This is with TWRP 3.0.3-2-tryout. I then resize the data partition to all room for a footer... to 1421303 4k blocks down from 1421307.

This then allows me to encrypt from the settings menu, but TWRP will not find the footer in this version. Downgrading TWRP to 3.0.3-0-stable, It works and TWRP will ask for the encryption password.

I also trying using the resize / fix partition menu buttons in twrp before doing this, didnt help.
[Galaxy S 4 Mini Android Development] ne0zone75:
Yes, you are right i believe... I will check this out ASAP and i will offer updates. I am very busy right now but i think that this will be done before next weekend.

Stay tuned,

Regards

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] ne0zone75:
Seriously ?! I will check my sources history very soon...

ATM i think that i forgot some code related to crypto. footer in latest TRYOUTs. If it is working, it is good luck...

Thanks for reporting back ? !

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] :
Yes. It is as I reported in post #1329. I haven't changed anything since then, still encrypted. Rebooting the device prompts the password screen before booting into android......

TWRP is the latest TRYOUT and asks for the password before decrypting. It all seems to be working from my end.

I was thinking of installing AICP to see if there was an issue rom-side, but you think there is something missing in TWRP?
[Galaxy S 4 Mini Android Development] ne0zone75:
My POV is that if anything is working properly for AOKP with latest TRYOUTs, then it should work the same way with any other custom ROM (meaning that if it is not working for a specific one, then it should be a ROM side issue...).

Anyway and like i just wrote down, it is good luck because as far as i remember, i think i forgot some code in v3.0.3-2, compared to previous releases but i am not completely sure...

Anyway, there is another way to consider this for me... may be that missing code makes the recovery less compatible with custom N ROMs. So adding it again will may be make TWRP working with more than without it. For sure, i am using LineageOS to build my recovery images, so v3.0.3-2 must work at least for this one and AOKP (according to your feedback).

IMHO, one thing to do is to check this out by testing TWRP for major custom N ROMs for S4 mini and for both v3.0.3-2 and any previous version. Yes, i know it is a little bit boring...

All of this is just a guess and any pro. DEV may have a more solid opinion about it.

Cheers ?

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] :
[MENTION=5280400]ne0zone75[/MENTION]

I just booted to recovery from restart menu to test another rom and this time TWRP(still TRYOUT) couldn't find the crypto footer. This is very strange, as it asked me for the password last time I booted recovery and decrypted as I would expect . I have not changed anything......so it seems there is something missing in the latest tryout, but the crypto footer is not always unable to be found??
[Galaxy S 4 Mini Android Development] ne0zone75:
I will add my missing TWRP code again and finger crossing about that it will fix it.

It sounds to me that my guessing was right... maybe...

Upcoming TRYOUTs will tell us about it.

Cheers again ?

Tapatalked from my OnePlus 3
[Galaxy S 4 Mini Android Development] xTr3Me123:
Ye I did that, used ODIN 3.09 and I tried different versions of the TWRP recovery. Odin says the flashing "passed" and the S4mini does not vibrate before rebooting.

After this I still cannot boot into recovery mode.

The S4 mini is stuck in a bootloop and this was not caused by flashing a faulty version or whatever, the S4mini was working for over a year without any bigger problems and while not using it, it somehow crashed and started to reboot, which did not work anymore. Since then it is stuck in that bootloop and I cannot boot into recovery aswell.
[Galaxy S 4 Mini Android Development] pidi123987:
Its surely a twrp issue, because i have tried it with latest AOKP and AICP builds same issues. 3.0.3.0 stable works though...
[Galaxy S 4 Mini Android Development] ne0zone75:
[MENTION=6418283]noppy22[/MENTION] confirmed that it is working at least with AOKP. Anyway, i will add code soon to try to fix this. At last, it is not an upstream TWRP bug but an issue specific to my builds.

Stay tuned

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

Hello,

New installers are available now over AFH. It should work great at last (thanks [MENTION=3044346]arco68[/MENTION], [MENTION=5416372]csendre[/MENTION], [MENTION=6418283]noppy22[/MENTION], [MENTION=6614989]jason972000[/MENTION]). I removed foreign languages availability and NTFS support for removable storage in order to meet recovery image size requirement. That's it !

-> 'Odin' ready files

3G | DS | LTE

-> flashable ZIPs

3G | DS | LTE

Enjoy, :fingers-crossed:...

PS : my GitHub sources are NOT up to date... it will be done very soon...
[Galaxy S 4 Mini Android Development] Whitest:
Odin & ZIP links got twisted around ;)
[Galaxy S 4 Mini Android Development] Sarcastic Warrior:
Hi guys, odin cant find the .md5 file. What can i do?
[Galaxy S 4 Mini Android Development] Harvey_Spectar:
Did you unzipped it first?
[Galaxy S 4 Mini Android Development] Sarcastic Warrior:
Yes i did, i've already fix it. I'm using windows 10 so i opened in compatibility mode. Thanks again.
[Galaxy S 4 Mini Android Development] :
[MENTION=5280400]ne0zone75[/MENTION]

TWRP 3.0.3-3 is working well for basic functions. I've tested : Install, Wipe, Backup, Restore and all these work well as expected. I'll test crypto tomorrow. Thank you :)

EDIT: i9195 with AOKP 7.1.1
[Galaxy S 4 Mini Android Development] ne0zone75:
Happy to learn that :good:

:fingers-crossed:
[Galaxy S 4 Mini Android Development] gay-sha:
[MENTION=5280400]ne0zone75[/MENTION]

I'm still in version 3.0.3-0

Do you recommend upgrading to version 3.0.3-3 for future installations or can I continue in the old one?