yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Android Development] kamikaze702k:
Is there anything new or changed for the better in this version?
[Galaxy S 4 Mini Android Development] SilviuMik:
What’s new in 3.0.1-0:
[Galaxy S 4 Mini Android Development] ne0zone75:
TWRP v3.0.1-0

Hi,

You will find my updated packages download links to latest official TWRP release below :good:.

Please keep a copy of previous STABLE build for your device before flashing new one because i'm just recovering from a medium data disaster (again !). If latest image is not working properly, then flash previous one back and please give some feedback !

I will update OP download links ASAP if all is going OK :fingers-crossed:...

3G : odin | recovery

DS : odin | recovery

LTE : odin | recovery

Nice week-end to you !
[Galaxy S 4 Mini Android Development] SilviuMik:
[MENTION=5280400]ne0zone75[/MENTION] Windows Defender reports this as Trojan: Win32/Spursint.A!cl

But Virustotal says it`s clean so most likely it is :)
[Galaxy S 4 Mini Android Development] mielletseed:
Since you flash it in recovery to your Android phone it wouldn't infect your Windows PC,I'm sure.
[Galaxy S 4 Mini Android Development] nussbaum:
Try to run it on Windows ;)
[Galaxy S 4 Mini Android Development] ne0zone75:
You are the second one to report this back ! So, i installed latest and up to date 'Bitdefender Security for XP', then fully scanned my XP virtual machine with it; result : not a single threat :) ! I also scanned the network directory where i store my builds (the ones i upload to AFH, so the ones you download...) without finding any problem ! Finally, the tool i use to package my recovery flashable files (D4UpdateZipMaker, available for download over xda) is reported as a generic trojan BUT since output files are clean, i believe that's not very important...

I agree !

How is it going with v3.0.1-0 ?!
[Galaxy S 4 Mini Android Development] KevinX8:
If you want to be part of the XDA community you have to have trust and common sense. If we are being completely paranoid here every developer on XDA could decide to add a virus to their projects but this is where the common sense kicks in. What exactly would they gain from this? A couple cents from the 1% of people without an anti virus? They would also be completely destroying their integrity their identity as a developer. So really there is no reason to be alarmed that a barely competent anti virus is flagging developers files as '' a generic trojan'' it IS a false positive and a more than obvious one
[Galaxy S 4 Mini Android Development] ne0zone75:
Let me clarify something : i never said that i was believing that 'D4UpdateZipMaker' could be bad ! It is reported as 'generic trojan' by the antivirus software i used and it happens sometimes with this kind of tool ! I use it for some time now and will continue to do so !
[Galaxy S 4 Mini Android Development] KevinX8:
I was just talking to the people who actually think that it might be a trojan. I know you know its not one but clearly a few people here believe windows defender in some way
[Galaxy S 4 Mini Android Development] ne0zone75:
Anyway, files are clean for sure now !

That is what matters to me

Tapatalked from my SM-G903F
[Galaxy S 4 Mini Android Development] csendre:
Everything seems to be running great with 3.0.1.0 on the 9192. Flashed from recovery.

Thanks!
[Galaxy S 4 Mini Android Development] SilviuMik:
I actually said in my post that i think the files are clean, i just reported a false positive , but it seems people start to blame and not read the whole post.

Anyway, Thank u ne0zone75 , TWRP 3.0.1.0 Odin package works great on GT-I9192 for wipe/backup/restore/install
[Galaxy S 4 Mini Android Development] RaeesD:
Flashed 3.0.1.0 from recovery, all went fine with a wipe and install of multiple zips on i9190. Thanks!
[Galaxy S 4 Mini Android Development] redjamesg:
Everything is working as it should on I9195, the booting time seems to be less than what it was on 3.0.0.0-1
[Galaxy S 4 Mini Android Development] pedro311:
Did you try on encypted /data partition?

I've encypted my phone when I was on TWRP 3.0.0-1. With this version I was able to reboot in recovery and decrypt /data.

After 3.0.1.0 installation, there is no possibility to decrypt /data in recovery (still: wrong password), so it's useless for me :(

Something's wrong here...

Back on 3.0.0-1, and everything's fine again.
[Galaxy S 4 Mini Android Development] ne0zone75:
Would you be kind enough to post v3.0.1-0 logcat as an attachment to the reply to this post (once tried to decrypt unsuccessfully '/data')... i know that you already installed v3.0.0-1 back, so it will be greatly appreciated :good: !

Thanks
[Galaxy S 4 Mini Android Development] ne0zone75:
Opening post is updated !

v3.0.1-0 is now current release of STABLE branch.

I've just updated opening post download links accordingly and downloads tab of this project has also been updated.

Unfortunately i removed v3.0.0-1 from downloads tab and from AFH because i was not aware that crypto. feature seems to be broken (again !) in v3.0.1-0...

I am currently uploading v3.0.0-1 to AFH again.

If crypto. feature is confirmed as broken in v3.0.1-0, then i will need some logcat to narrow down what is going wrong with it because i built it the same way i built v3.0.0-1 (same own device sources trees).

Anyway, many thanks for your understanding !

EDIT : v3.0.0-1 + v3.0.1-0 are available for download from this web page...
[Galaxy S 4 Mini Android Development] ne0zone75:
v3.0.2-0 is on its way !

OK ! Password entry was upstream broken in v3.0.1-0.

This commit fixes it and v3.0.2-0 is out !

v3.0.2-0 will be ready shortly ;).
[Galaxy S 4 Mini Android Development] KevinX8:
Wow that was fast must have been really broken
[Galaxy S 4 Mini Android Development] ne0zone75:
v3.0.2-0 is out !

Opening post and downloads tab have just been updated (twice today !) to v3.0.2-0 :good: !

v3.0.1-0 has been removed and v3.0.0-1 is still available from AFH.

Please keep me informed about crypto. feature status in v3.0.2-0 :fingers-crossed:, thank you !

Could any of you post some nice screenshots of 3.0.x-x in order to update screenshot section ?! I know that someone already sent me screenshots for 3.0.x-x but if i do remember correctly, displayed language was not EN...

Regards

EDIT : v3.0.2-0 seems to work fine (at least crypto. does :good:), so i removed v3.0.0-1 from AFH again...
[Galaxy S 4 Mini Android Development] KevinX8:
Here a bunch of shots from pretty much every menu
[Galaxy S 4 Mini Android Development] ne0zone75:
Thanks for taking time to do this :good:.

Good night

Tapatalked from my SM-G903F
[Galaxy S 4 Mini Android Development] KevinX8:
No problem wanted to see what's new anyway
[Galaxy S 4 Mini Android Development] pedro311:
Great to hear it.

It is faster than my logcat for 3.0.1-0 :P
[Galaxy S 4 Mini Android Development] ne0zone75:
;)

Screenshots tab updated !

[MENTION=5168296]Xmaster24[/MENTION] : :good:
[Galaxy S 4 Mini Android Development] pedro311:
I can confirm, that crypto is working on 3.0.2-0 ;)
[Galaxy S 4 Mini Android Development] ne0zone75:
OK :) Thanks for your feedback !

Good night

Tapatalked from my SM-G903F
[Galaxy S 4 Mini Android Development] legacymjr:
Please note that the latest download of openrecovery-twrp-3.0.2-0-serrano3gxx-STABLE.tar.md5.7z is throwing a failure on Windows 10 quoting Trojan:Win32/Spursint.A!cl
[Galaxy S 4 Mini Android Development] powwow12:
What happens to the existing CWM recovery when I install TWRP on top of it? I want to make sure there will be no traces of it left afterwards
[Galaxy S 4 Mini Android Development] mielletseed:
Since the recovery is an image it gets replaced completely ...
[Galaxy S 4 Mini Android Development] ne0zone75:
We have already discussed about it here and the conclusion is that my XP virtual machine (used to package my builds) and my files are clean for sure now.

Tapatalked from my SM-G903F
[Galaxy S 4 Mini Android Development] txusmari:
Thanks mate. Good share :good:
[Galaxy S 4 Mini Android Development] afterglow:
Hello, i have question as i never used TWRP,

im currently on CWM 6.0.5.0 and CM11 running on my 9195, can i just change to TWRP and continue to use CM11 or would there be any conflict/incompatibility ?

i have dowloaded the odin file openrecovery-twrp-3.0.2-0-serranoltexx-STABLE.tar.md5 and can flash this through odin (v3.09 is fine - right?)

im planning later on to full format all partitions and install CM13

Thanks.
[Galaxy S 4 Mini Android Development] ne0zone75:
Yes ! Flashing TWRP through Odin will overwrite your current recovery : CWM will be replaced by TWRP. Current TWRP is backward compatible with previous Android releases.

Happy flashing
[Galaxy S 4 Mini Android Development] afterglow:
i suppose the procedure is same as with CWM, uncheck F.Reset Time and only leave Auto Reboot checked, and select as AP file the recovery.tar.md5 file right?

thank you very much in advance ne0zone75
[Galaxy S 4 Mini Android Development] ne0zone75:
Absolutely
[Galaxy S 4 Mini Android Development] kamikaze702k:
TWRP is the best recovery in my opinion, esp this one for our device!
[Galaxy S 4 Mini Android Development] stefanson:
Hi! First, thank you very much for your excellent work. :highfive:

Second, is there any chance that your builds will become official one day? Found the answer.

Last question: You call your build "open". Is there any source code repository available in case I would like to build it myself?

Kind Regards

Stefanson
[Galaxy S 4 Mini Android Development] ne0zone75:
Thanks ! If there is the word 'open' inside the name of the downloadable files of my TWRP project, it is because official TWRP downloads where following this naming some time ago... i just added a 'branch' keyword to fit my project needs.

This 'open' word is not obsolete because all the sources of my TWRP project are freely available on GitHub : TWRP source code belongs to OmniROM GitHub repository (android-6.0 branch) as well as the ROM tree that i use to build my packages (android-5.0 branch). The device and kernel trees are those from CyanogenMod GitHub (cm-12.0 and cm-12.1 branches). Finally, vendor tree can be found from TheMuppets GitHub repository (cm-12.0 branch).

But ATM my working sources tree for this project is not available anywhere, so this 'open' word is maybe inaccurate...

If i have some free time this summer, i will try to upload it to my GitHub account...
[Galaxy S 4 Mini Android Development] smartxdev:
Unfortunately, I'm still unable to enable encryption properly:

Turning it on displays and encrypting android logo for a second, and then screen blanks for an undefined amount of time.

I tried it with CM13 Snapshot + TWRP 3.0.2.0 as posted here...

I also attempted to reformat data partition, restore backup and try to enable encryption - same results, no luck...

Any advice on how to successfully get it working?
[Galaxy S 4 Mini Android Development] stefanson:
Is there a reason why you mix several branches (cm-12.0, -12.1 + android-5.0 and -6.0)?

Quoted from [DEV]How to compile TWRP touch recovery:

Did you run into those issues? May that be the reason why you also use old branches?

I'm looking forward to seeing this!
[Galaxy S 4 Mini Android Development] ne0zone75:
I will not be very helpful on this because as you certainly know i do not own a S4 mini anymore for a long time now... You could ask for assistance from CM-13.0 official support thread : here, in order to have some help from [MENTION=3044346]arco68[/MENTION] for example. He checked crypto. feature of v3.0.0-1 out and it was OK... i could upload v3.0.0-1 again for your S4 mini variant if you want to check out if it is better with it than with v3.0.2-0...

Thanks

Yes ! Of course ! As you already know it is now quite complicated to build TWRP along with a CyanogenMod ROM tree and to answer to your second question : yes i ran into build issues with CM... So i decided to omnify CM S4 mini device sources trees in order to build TWRP along with OmniROM and at that time [MENTION=912474]Dees_Troy[/MENTION] was recommending OmniROM 5.0 for the ROM tree and the latest OmniROM branch available for TWRP as usual... (android-5.0 + 6.0 explained) Also i am building TWRP with a 5.0 OmniROM sources tree : it was quite logical to use CM-12.0 S4 mini device and kernel trees with it (cm-12.0 explained). Nevertheless, in order to avoid some issues i switched from cm-12.0 to cm-12.1 for the kernel only (cm-12.1 explained).

To summarize, my working tree is a LP 5.0 one, except for the kernel which is 5.1 and also for the TWRP sources themselves (currently MM 6.0) which are always the most recent ones...

Anyway, i will switch to OmniROM 6.0 ROM tree and to CyanogenMod 13.0 device, kernel and vendor trees soon or later ;)...

Yes ! See above... and that is why i am using an OmniROM sources tree.

Regards
[Galaxy S 4 Mini Android Development] ne0zone75:
TWRP v3.0.2-1 TRYOUTS (built along with CM-13.0)

Good morning,

You will find build v3.0.2-1 download links below. These packages are TRYOUTS. If you decide to test them out, please keep a copy of my v3.0.2-0 Odin packages ready for flashing, in case new TRYOUTS are not working...

These packages are built along with CyanogenMod 13.0 ROM tree; device and kernel trees are CM-13.0 too for 3G and LTE but they are from [MENTION=943196]k2wl[/MENTION] for DS (thanks to him for his work BTW).

Thank you for reporting back if you install one of these (boot time and adb, mtp, crypto. features...) !

3G | DS | LTE

Happy flashing
[Galaxy S 4 Mini Android Development] mfPPC:
It boots ok and didn't notice any boot speed improvement. Didn't tested any thing else. ;)
[Galaxy S 4 Mini Android Development] ne0zone75:
Okay ! Thanks :good:.Your feedback is letting me know that it is booting and that is great :highfive:.

Have a nice day
[Galaxy S 4 Mini Android Development] Whitest:
Tried nightly update with 3.0.2-1 LTE recovery - works fine here! Thanks for continously updating this recovery!
[Galaxy S 4 Mini Android Development] Falenone:
It works fine but there seems to be issue with backups. When backing up, it shows in TWRP file manager but not on my PC. Free space on SD card remains the same as it was before backup.
[Galaxy S 4 Mini Android Development] ne0zone75:
OK thanks ! I will investigate on this medium issue later.

Does anybody have tested other features out like : ADB, MTP, F2FS, crypto.?!

It is important for me to know that because i am about to definitively switch from my OmniROM LP working tree to my CyanogenMod MM one...

Thanks
[Galaxy S 4 Mini Android Development] Falenone:
I can test some after I backup the device and get to the fun part.

I tried backing up to internal storage. It seems to be able to back up there. But not on my 64GB SD card.
[Galaxy S 4 Mini Android Development] ne0zone75:
Okay i had not understood your issue that way : if your are able to back up your device properly to internal storage (is free space updating correctly in that case BTW ?) and if backing up to your microSD is not working as it should, then try to format your microSD from inside the recovery (keep your data temporarily elsewhere and put it back to your memory card once it is formatted of course...) and try to back up your partitions to it again once done...

Let me know if it helped

PS : what is your current microSD filesystem ?
[Galaxy S 4 Mini Android Development] Falenone:
Yep. I guess it's my SD card issue rather than recovery. I can copy stuff on it but they won't appear after eject/reconnect

Same with deleting, they are gone until I eject/reconnect. Took my SD card out of my main device and slapped it in S4 mini.

Edit: My sd card is dead. Glad I was able to get my stuff before it got corrupted. Can't even format because of bad sectors everywhere. Data can be read from it so I'll use it until I get a new one.

Also, f2fs and other file system changes work.
[Galaxy S 4 Mini Android Development] arsm74:
tested on my i9195......clean install, crypto and all is ok. will test nandroid backup/restore in a few days.
[Galaxy S 4 Mini Android Development] ne0zone75:
I think that i will flag latest TRYOUTs as STABLE soon...

Please feel free to give any positive or negative feedback about them,

Thanks
[Galaxy S 4 Mini Android Development] stefanson:
v3.0.2-1 experience

First time I use TWRP (I only knew CWM before):

The following worked flawlessly:

* Flashing the recovery with heimdall

* Creating a back up --- will test restore later

* Formatting everything

* Flashing CM 13-0

* Flashing OpenGApps

* Changing the language

* Changing the time zone

A few things I noticed:

* Time is absolutely wrong: Saying it's 14:22 while the correct time is 19:40

How do I set it? There was no option.

* Swipe to unlock button is transparent and its text overflows the text of the button lying a layer below. This makes it harder to read the lock screen text.

So far. :highfive:
[Galaxy S 4 Mini Android Development] ne0zone75:
Thanks !

Once booted into your CM-13.0 ROM, if you boot back into TWRP, then time should be accurate. What did you describe usually happens when booting into recovery just after its installation...
[Galaxy S 4 Mini Android Development] stefanson:
v3.0.2-1 backup tested

Hi!

As I recently mentioned I flashed TWRP v3.0.2-1 on my phone and immediately after that I made a full backup of the original Samsung firmware with all apps etc.

Then I wiped the phone completely, flashed CM 13.0, installed various apps etc. and did a another full backup again.

For testing purposes I restored successfully* the full back up of the original Samsung firmware (with MD5 checksum test), which booted quiet fine then.

* However, many apps crashed and the system was no longer usable.

I then restored the full backup of CM 13.0: Here everything worked fine, especially no app has crashed so far. ;)

First time I rebooted into the recovery all settings were lost. After the second reboot into recovery TWRP kept the settings.
[Galaxy S 4 Mini Android Development] ne0zone75:
Well, there is no reason for APPs to FC like this after restoring a full NANDROID backup ... did you perform a full wipe of your device before restoring your SAMSUNG FW backup ? Especially '/cache' partition ? Your issue sounds like this to me...

Regards
[Galaxy S 4 Mini Android Development] stefanson:
Well, the restoring function wipes the partitions itself already, if I interpreted the log correctly. So, there should really be no reason to wipe everything manually again. :confused:

I wiped the cache partition manually afterwards within the recovery btw.

Please consider that I proceeded the same way with the CM 13.0 backup where it worked as expected.
[Galaxy S 4 Mini Android Development] ne0zone75:
I do not remember if '/cache' is or can be wiped before or after restoring a backup archive because i am not using TWRP with my current device but like i already said your issue sounds like this to me...

Anyway, you wiped it manually... this restoring issue is surprising...

Also, i agree that the restoring process is wiping any target partition, nevertheless in some cases it helps to format '/data' partition instead of just wiping it...
[Galaxy S 4 Mini Android Development] stefanson:
For clarification I will format everything tomorrow again before I restore the backup another time.

If it doesn't work then maby the backup failed though it said it completed successfully?
[Galaxy S 4 Mini Android Development] ne0zone75:
OK ;) !

It is very unlikely for the recovery to go successfully through a backup process if it is not the case...

What you can do when you will restore your SAMSUNG FW backup again is to wipe 'cache' + 'dalvik cache' once backup is restored; by doing so, '/cache' will be wiped and 'dalvik cache' will be cleaned (which is stored in '/data' partition).

Anyway, if you need to go back to your stock FW one day and if restoring it still fails, you can download the latest FW for your device as an 'Odin ready' archive from SAMMOBILE website. All you will have to do is to flash this FW through 'Odin', then flash TWRP through 'Odin' too and finally restore ONLY '/data' from recovery by ending with a 'cache' + 'dalvik cache' wipe...
[Galaxy S 4 Mini Android Development] tchavei:
Just a comment. You did backup all 7 partitions, right? By default, if I remember correctly, twrp offers to backup only 4 or so. You have to select all of them when you backup your original rom. Mine has worked flawlessly (restore).

Enviado do meu GT-I9195 através de Tapatalk
[Galaxy S 4 Mini Android Development] smartxdev:
Great!!! Thank you very much!

I've just backed everything up to start en/decryption tests as I intended, to find more clues on the issue.

Came here to check on any news before I start... and luckily we have a fixed version to test instead of digging into old issues :)

I have another question on the encrypted systems topic to the more knowlwgeble and experienced people here (may be a bit off topic for the recovery I guess.. sorry for that):

I have a plenty of windows systems experience, a somewhat limited linux (not on encryption though...) experience, and I'm pretty new to android.

(I've got my first smarter-than-symbian-s60-phone about a month ago (a nice I9195), which I'm now trying to deeper understand....)

So, to the point, I'm trying to establish a fail-safe backup scheme before switching on the encryption for a daily use:

So, let's say I have an encrypted phone, which I back up periodically (with TWRP: boot, cache, data, efs, modem, system partitions)

Then, something gets messed up, so that I have to wipe all, reflash recovery, etc.

So I flash the working recovery with odin, boot to it, format data using TWRP,

removing the encryption from the device

Now, I want to

restore the NANDroid backup I've done before

(when my system was encrypted)...

Will it work????? :confused:​

(Edit) I want to add a question to this:

While I do TWRP's "Format Data" (the function that effectively removes encryption),

Which partitions are affected besides /Data? Will it also wipe internal storage?

Or /storage/sdcard0 and /storage/sdcard1 remain intact???​

The thing is that I'm not sure how's android's encrypted file system works, and what are the exact dependencies.

And whether restoring the full NANDroid (boot, cache, data, efs, modem, system partitions) will be sufficient, or if by removing the encryption beforehand, it wipes some data that is vital to make the restored encrypted partitions work?

At the meantime I'll test the current fix and report back...
[Galaxy S 4 Mini Android Development] ne0zone75:
Good evening, i will give you a detailed answer ASAP ;)

Best regards