yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] steadfasterX:
well I am the official TWRP maintainer as you can see on http://twrp.me so..

See here on the OP:

so no, official is based and made for MM. It works fine for every version but as you already know you need a ROM specific TWRP version to have all features working.

see also in the OP:
[G4 Android Development] sdembiske:
Get one of two results only, no matter what I try, whether in TWRP or not:

Permission denied or No such file or directory.

Thanks,

S.
[G4 Android Development] steadfasterX:
this has to be done while in TWRP....

Do this instead:

adb shell
find /data/media/0/TWRP/BACKUPS/LGUSUfe62f596
[G4 Android Development] sdembiske:
Same result: No such file or directory.
[G4 Android Development] steadfasterX:
Data partition mounted before?

.-
[G4 Android Development] sdembiske:
Yes
[G4 Android Development] steadfasterX:
hmmm then

adb shell
find /data/media/0/TWRP/BACKUPS
[G4 Android Development] sdembiske:
Sorry, was just doing a complete backup with 3.2.3-PREVIEW-144_g4_0 which completed with no issues (wanted an up-to-date backup before trying Pie release). I was also able to do a needed restore of a prior TWRP backup (something I couldn't do with the latest preview release issues).

Have now re-installed twrp-3.3.0-PREVIEW-182_g4_O and here's a kicker - the re-tried backup didn't fail.

The only thing I can think of is if one has backup data/media checked in settings and then one removes the check after, it doesn't release it fully and carries it over and keeps looking for it

? The setting should not be automatically default checked or manually checked (as I did initially) on first installation and then be later removed, until it is fully tested as ready to go (as per your warning).

Result for:

adb shell

find /data/media/0/TWRP/BACKUPS

the same - No such file or directory.

Next test will be to see if I can restore this latest backup.

[MENTION=5545101]steadfasterX[/MENTION]

Restore failed. Phone turned off when restoring System partition (on previous attempts had also rebooted back to TWRP at the same restore point) - not sure recovery log will reflect anything as had to manually reboot back in to TWRP this time and wasn't able to pull log before phone turned off. If you need a logcat and it can be done in TWRP, let me know. Back to 3.2.3-PREVIEW-144_g4_0 for now.

Thanks,

S.
[G4 Android Development] steadfasterX:
Thanks for the testings and suggestions. I will take a deep look on that hopefully next week.

.-
[G4 Android Development] steadfasterX:
Latest PREVIEW release

read more about PREVIEWS and the <flavor>'s in the OP (what they are and

when to use

)!

twrp-3.3-0-PREVIEW-183_g4_<flavor>

Status: TESTING

Release date: 2019-05-16

TWRP sources changelog: sfx github-changelog

Download: sfX leech server (same download for all G4's)

Kernel: github-changelog (preview builds compile the kernel on build automatically (official not - yet) - so the kernel differ between official and preview)

Device Tree changelogs:

P flavor

O flavor

N flavor

MM flavor

Summary changelog:

HIGH experimental: beginning from #136 build all versions will include my Internal Storage backup patch (state and details: here).

Thats the main reason why the "Status" is "TESTING" for this build.

This update includes the latest TWRP plus my datamedia patch on top. There is one known issue with the current patch state: restoring datamedia crashes atm! I'm working on a fix but the previous implementation was based on the android-8.1 branch and the migration to 9.0 broke things a bit .

Keep in mind that the whole feature is still HIGH EXPERIMENTAL !!

default is now NOT to include datamedia in backup restore until its more stable. This may require to go into the TWRP settings and click "reset default settings" and a reboot to recovery .

The new and

high experimental

feature to backup your internal storage is a WIP (work in progress) but I would love to hear your feedback of the current implementation.

If you encounter any issue just share the recovery.log.

This also means: atm of writing the only safe way of using this new internal storage backup feature is by backing up to an external sdcard. Adb backup works fine too but the restore NOT (yet). Watch the above linked wiki page for any progress regarding the implementation

.
[G4 Android Development] sdembiske:
OK, installed latest twrp-3.3-0-PREVIEW-183_g4_0 on latest H812 UsU LOS 15.1 rom. Tried to backup but it failed again on same error: unable to find data/media backup. Nothing was ticked in Settings.

recovery.log for backup fail: https://paste.omnirom.org/view/2cf89f5e

dmesg.txt for backup fail: https://paste.omnirom.org/view/8860f088

Then, re-installed TWRP-3.2.3 and did a successful backup, booted up and took a picture, making sure it was in Gallery. Next re-installed twrp-3.3-0-PREVIEW-183_g4_0 and did another backup - successfully this time.

recovery.log & dmesg.txt for backup success: https://www.dropbox.com/sh/bbgerhy15gbfip1/AACBmUvLtqlynwmaFg7ENMNFa?dl=0

Recovery.log proved to be too large to paste, so put both files in Dropbox.

OK - one of two possibilities to account for successful backup now? 1). Somehow the file was created in TWRP-3.2.3 backup & was able to be found then in the twrp-3.3-0-PREVIEW-183_g4_0 backup, so backup was successful? 2). Having at least one item (a picture in this case) in internal data allowed the backup to complete successfully, i.e., if nothing in internal data, backup fails?

Will try a restore of the successful backup next.

Addendum

: [MENTION=5545101]steadfasterX[/MENTION] ... Restore failed

Phone shut off again before I could grab any logs etc. What's interesting is that when I rebooted back into TWRP (had to pull out battery first & then manually boot into), in Settings, Include internal storage in backup/restore was ticked as well as Prompt to install TWRP app if not installed and Select Storage was on internal and I could not select Micro SD card.
[G4 Android Development] steadfasterX:
Do you had read and followed this before starting ?

> This may require to go into the TWRP settings and

> click "reset default settings" and a reboot to recovery

?

And yes when data media is empty it will fail ..
[G4 Android Development] Benny100:
Working Perfect Big Thx!:)
[G4 Android Development] HorstiG:
Great, thank you!!
[G4 Android Development] steadfasterX:
Don't say thanks click thanks (button) :svetius: :good: ;)

Anyways glad to see you like it!! :laugh:

.
[G4 Android Development] HorstiG:
Funktionert 1A :good::good:
[G4 Android Development] HorstiG:
Suuuuper
[G4 Android Development] steadfasterX:
HorstiG do you have a twrp theme installed? Your screenshot looks interesting :cyclops:

.
[G4 Android Development] HorstiG:
Yes :D made in germany

http://xdaforums.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
[G4 Android Development] SavageRobot:
Is there something extra I have to do after flashing recovery? I can see the new version is installed as it says "steadfaster" at the top and double tap to wake works, but the time is still incorrect
[G4 Android Development] skdubg:
same problem here, all works fine, only time is incorrect.

i set the correct time zone and summer/winter
[G4 Android Development] steadfasterX:
:eek:

Please follow: FAQ #4

Otherwise i cannot help you.

Thanks

.
[G4 Android Development] skdubg:
here is paste from recovery log:

https://paste.omnirom.org/view/828a42ba
[G4 Android Development] akiute:
recovery installed with cm13. Charging the phone for encrypt it and test if work
[G4 Android Development] akiute:
i can unblock the phone, when cm13 is started and i have put the pattern, say: incorrect pattern :(
[G4 Android Development] popy2006:
start twrp, go to advanced, file manager, locate the file /data/system/locksettings.db and delete it.

After a restart you should be able to enter the system without your pattern.

Just reenable it with a new on :D

pOpY
[G4 Android Development] Aldideos:
It is a known bug of cm13 for lg g4. Using the method you proposed lets you phone unblockable but after you set the pattern or the pin and reboot you will have the same problem. You need to use an alternative lockscreen or remove two libs disabling so the HW Gatekeeper that are in /system/vendor/lib/HW/gatekeeper.....so and /system/vendor/lib64/HW/gatekeeper.....so(the same name).

The mantainers state that it is a bug for configuration without v20d bootloader and modem, but I tested and I can confirm that the problem is also with this configuartion. I think we will not have an official solution to this bug because it is not recognized by the Mantainers...

Sad thing :(
[G4 Android Development] akiute:
thanks, now i haven´t cm13. I have stock rom modified by a guy from htcmania with root, viper4 and personal modifications.

Thanks by the comment, appreciate the explication.
[G4 Android Development] Aldideos:
You're welcome :)
[G4 Android Development] popy2006:
Thats NOT true!

I have gained access to phone sveral times switching cm13 and stock or vise versa (cant remember)!

[MENTION=4557402]akiute[/MENTION]: Just make a nandroid and test...

pOpY
[G4 Android Development] Aldideos:
Without encryption you can do what you say... But if you try it with an encrypted device it don't work... Try it if you don't trust me
[G4 Android Development] popy2006:
Ahh that's the difference!

My device was not encrypted.

Thx for clearing things up.

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] sdembiske:
I checked in Settings first (after install of twrp-3.3-0-PREVIEW-183_g4_0 before successfully backing up) and nothing was checked so didn't feel the need to reset default settings. Is it still necessary in that case ... ?
[G4 Android Development] steadfasterX:
Yes. You HAVE TO..
[G4 Android Development] sdembiske:
Well, that didn't work - restoring default settings failed to clear the two settings that were ticked on the reboot after the backup fail (that continues to happen on the format System portion of the restore, i.e., very early in the restore process). This time the phone didn't shut down completely, just rebooted back into TWRP. Very strange.
[G4 Android Development] steadfasterX:
Just to be clear:

reset settings . Then reboot recovery !

...and you say the data media setting is still enabled? If that's the case share the recovery log
[G4 Android Development] sdembiske:
YES - yes - OK.

Link: https://www.dropbox.com/s/p1ktcpqh6s1zuxx/recovery.log?dl=0
[G4 Android Development] steadfasterX:
New PREVIEW releases

read more about PREVIEWS and the <flavor>'s in the OP (what they are and

when to use

)!

twrp-3.3-0-PREVIEW-184_g4_<flavor>

Status: TESTING

Release date: 2019-05-21

TWRP sources changelog: sfx github-changelog

Download: sfX leech server (same download for all G4's)

Kernel: github-changelog (preview builds compile the kernel on build automatically (official not - yet) - so the kernel differ between official and preview)

Device Tree changelogs:

P flavor

O flavor

N flavor

MM flavor

Summary changelog:

HIGH experimental: beginning from #136 build all versions will include my Internal Storage backup patch (state and details: here).

Thats the main reason why the "Status" is "TESTING" for this build.

This update includes the latest TWRP plus my datamedia patch on top. There is one known issue with the current patch state: restoring datamedia crashes atm! I'm working on a fix but the previous implementation was based on the android-8.1 branch and the migration to 9.0 broke things a bit .

Keep in mind that the whole feature is still HIGH EXPERIMENTAL !!

FIXED (thx [MENTION=6302635]sdembiske[/MENTION] for reporting): default is now NOT to include datamedia in backup restore until its more stable. This may require to go into the TWRP settings and click "reset default settings" and a reboot to recovery .

The new and

high experimental

feature to backup your internal storage is a WIP (work in progress) but I would love to hear your feedback of the current implementation.

If you encounter any issue just share the recovery.log.

This also means: atm of writing the only safe way of using this new internal storage backup feature is by backing up to an external sdcard. Adb backup works fine too but the restore NOT (yet). Watch the above linked wiki page for any progress regarding the implementation

.
[G4 Android Development] sdembiske:
Backup completed successfully with no errors now, both with and without data/media backup checked in settings.

Removing the setting seems to have done the job with the issues I was experiencing before.

One thing I did notice, if one restores the settings, backs out of the screen and immediately goes back in, the Reversed navbar layout, the Prompt to install TWRP app if not installed and Use SHA2 for hashing are checked. BUT, if one does as you suggest, by hitting the restore settings, backing out and immediately rebooting into recovery, only the Use SHA2 for hashing remains (as it should I guess given its function).

So, I reiterate,

as you have indicated

, that users MUST reboot into recovery after restoring the settings when the data/media backup setting has been checked, in order to remove the setting when required

.

One question

before attempting a restore, if the data/media setting is not checked to restore on the backup that did include it, should the restore function work as intended without errors or will it still be problematical?

Thanks for all the work you've put in on this once more.

Best,

S.

Addendum

: [MENTION=5545101]steadfasterX[/MENTION]

The restore failed again

on the backup that was made without data/media checked in settings (following a settings restore and reboot to recovery) and without /data/media checked in the restore settings. The first time, the phone turned competely off and required removing the battery first, reinserting it & manually rebooting into recovery. Thesecond time, the phone rebooted into TWRP. In both instances this occurred while the System partition restore was just getting underway.

Let me know what logs, if any, that I could provide to help solve.
[G4 Android Development] steadfasterX:
New Official release

twrp-3.3.1-0

Release date: 2019-05-22

Download: https://twrp.me

Device Tree changelog: (no changes)

Summary

changelog:

https://twrp.me/site/update/2019/05/22/twrp-3.3.1-0-released.html
[G4 Android Development] steadfasterX:
Thanks again for testing !

Yes you have to reboot as TWRP loads the default settings into RAM once (at least some) and will not update them until you restart TWRP (killing recovery and restarting it) or - much easier - rebooting to Recovery again.

What I had changed in the latest PREVIEW is the way how the first boot behaves regarding that feature. So the known issue for restoring data/media should

still occur

as that should have not effect on that - but who knows :)

.-
[G4 Android Development] steadfasterX:
New PREVIEW releases

read more about PREVIEWS and the <flavor>'s in the OP (what they are and

when to use

)!

twrp-3.3.1-PREVIEW-185_g4_<flavor>

Status: TESTING

Release date: 2019-05-23

TWRP sources changelog: sfx github-changelog

Download: sfX leech server (same download for all G4's)

Kernel: github-changelog (preview builds compile the kernel on build automatically (official not - yet) - so the kernel differ between official and preview)

Device Tree changelogs:

P flavor

O flavor

N flavor

MM flavor

Summary changelog (read the device tree changelogs above for ALL changes):

Now based on TWRP 3.3.1

Notes / Known issues:

HIGH experimental: beginning from #136 build all versions include my Internal storage (data/media) backup patch

(state and details: here).

Thats the main reason why the "Status" is "TESTING" for this build.

This update includes the latest TWRP plus my datamedia patch on top.

There is one known issue with the current patch state: restoring datamedia

crashes

atm!

I'm working on a fix but the previous implementation was based on the android-8.1 branch and the migration to 9.0 broke things a bit .

Keep in mind that the whole feature is still HIGH EXPERIMENTAL !!

atm of writing the only safe way of using this new internal storage backup feature is by backing up to an external sdcard.

Adb backup works fine too but the restore NOT (yet). Watch the linked wiki page for any progress regarding the implementation

The new and

high experimental

feature to backup your internal storage is a WIP (work in progress) but I would love to hear your feedback of the current implementation.

If you encounter any issue just share the recovery.log.

.
[G4 Android Development] aha360:
Hi folks.

I would like to know if NTFS-formatted microSD cards are read-write supported as I tried to make a TWRP backup but it keeps complaining about it being read-only (even when I have 20GB of free space on the microSD card) when I can read and write to it in AOSPExtended 6.5 (Android 9) and on Microsoft Windows and Linux.

Please see the attached logs and screenshot on this post.
[G4 Android Development] sdembiske:
Backup/Restore issue with TWRP-3.2.3-PREVIEW-144_g4_O on H812 UsU running LOS 15.1, May 05 '19 version with video lag fix installed and not encrypted.

In Settings > Sound - no Phone ringtone, Default notification sound or Default alarm sound options available nor can they be added in settings after restore completed and phone rebooted. The sounds are shown either with specific numbers or 'unknown' but funnily enough the sounds are there when individual sound volumes are changed but in the case of the Phone ringtone, it was changed to a single gong sound in one of the restores. Not sure if the problem resides in the backup or restore functions or whether it is related to the video lag fix in some way, so have included logs for both backup and restore.

In order to get the sound options back I have to do a somewhat clean flash, wiping Cache, Dalvik cache and System, re-installing the rom, re-installing Open Gapps and the video lag fix again.

Screenshots 1 & 2: After clean install (including data format) before backup.

Screenshots 3 & 4. After restore of same backup.

recovery.log after backup: https://gist.github.com/sdembis/4b236acd4da5df3a0abf24cf02eb1230

dmesg.txt after backup: https://gist.github.com/sdembis/455baed5634163b83b1310d97aeabc30

recovery.log after restore: https://gist.github.com/sdembis/330e324dab00d33dbdb2515a9d0350f6

dmesg.txt after restore: https://gist.github.com/sdembis/af5cc768182acdbabd741e86725695ba

If you need anything else to help solve, let me know.

Thanks,

S.
[G4 Android Development] steadfasterX:
oh.. damn.. thx for your stubborn tests as usual ;)

found the bug.

should be fixed soon.

You should consider using exFAT instead of NTFS : https://www.quora.com/Why-is-exFAT-better-than-NTFS-for-removable-media and https://superuser.com/a/262304

If you REALLY rely on NTFS I have enabled mounting ntfs drives with WRITE support in one of the

next

builds.

That will work only when you have NTFS on the external SD's

first

partition though (TWRP limitation) but in that special case you can always mount manually then:

adb shell
mkdir /sd_ntfs
mount.[B]ntfs[/B] /dev/block/mmcblk1[B]p2[/B] /sd_ntfs (replace [B]p2[/B] with the partition number which is NTFS formatted)

If you have only 1 partition on the external sdcard no action is required though

.-
[G4 Android Development] steadfasterX:
New PREVIEW releases

read more about PREVIEWS and the <flavor>'s in the OP (what they are and

when to use

)!

twrp-3.3.1-PREVIEW-191_g4_<flavor>

Release date: 2019-05-27

Status:

without

data/media patch*: considered to be STABLE

including

data/media patch*: UNSTABLE (known issues for backup & restore)

TWRP sources changelogs:

without data/media patch

including data/media patch

Kernel: github-changelog (preview builds compile the kernel on build automatically (official not - yet) - so the kernel differ between official and preview)

Device Tree changelogs:

P flavor

O flavor

N flavor

MM flavor

Summary changelog (read the linked changelogs above for ALL changes):

Switched the TWRP base back to pure official (meaning removing the data/media backup/restore support) - read the notes*

added NTFS r/w support as requested by [MENTION=5659251]aha360[/MENTION] (see the notes when you have multiple partitions on the external sdcard)

Download:

without

data/media backup/restore: sfX leech server (compatible with all G4 models and containing all flavors)

including

data/media backup/restore: sfX leech server (read the notes)

*Notes:

From this build on (#191) I split regular TWRP builds:

without

my data/media patch and those

including

my experimental data/media patch - as it turns out it is not as production ready as thought.

The data/media version can be found from now on here only: http://leech.binbash.it:8008/TWRP/datamedia/ and it is always based on Android Pie (almost identical to the P flavor - just with the datamedia patch on top)

The new and

high experimental

feature to backup data/media (so your internal storage) is a WIP (work in progress) but I would love to hear your feedback of the current implementation and the current known issues.

If you encounter any issue check the known issues first and if it is not listed share the recovery.log or even better open a new issue there.

.
[G4 Android Development] aha360:
Point noted. Thank you for your response.
[G4 Android Development] sdembiske:
All good now for both backup and restore for the O version. No issues detected so far at all.

Thanks,

S.
[G4 Android Development] a tiny ant:
Hello, it seems decryption in TWRP no longer functions with the last TWRP preview and Lineage version. Upon entering the decryption pattern TWRP will tell me "decrypt process took too long, killing process" and quit. Booting into the OS works fine.

I have the following installed:

TWRP 3.3.1 preview 191 for Oreo with LineageOS 15.1 from 20190619. I've also installed Magisk 19.3 but I will try replicating the issue without Magisk installed to see if it happens again.

Recovery.log:

https://paste.omnirom.org/view/49d44697

dmesg.log:

https://paste.omnirom.org/view/1889857b
[G4 Android Development] polfrank:
Can you try again with the previous version that used to work? What happens then? Does it work?
[G4 Android Development] steadfasterX:
Thanks for your report and the log files !

Yes it's known as pie is still quite new (and that's why you can't find pie in the OP as supported for decrypt). 2 days ago i had my first encryption test on LOS 16 which worked pretty well but TWRP needs some work too ofc .

Edit:

Sorry just recognized you refer to 15.1.. Will check that as well
[G4 Android Development] kessaras:
Lineage 15.1 is Oreo
[G4 Android Development] steadfasterX:
Really ? Thanks for clarifying .. I didn't know that until now ..
[G4 Android Development] a tiny ant:
I did actually, version 126 of TWRP worked fine with Lineage 15.1 20190409 did work. Later versions of either Lineage or TWRP seem to break decryption.
[G4 Android Development] steadfasterX:
Could you pls try build 193: http://leech.binbash.it:8008/TWRP/O/
[G4 Android Development] Leg0V0geL:
No big cores version for P?

Can you please release a pie version of twrp with only 2 or 4 cores enabled? Or give me a hint how to change the kernel parameters myself inside the twrp.img, just like with the rom zip files and the boot.img?

BTW the latest Lineage 16.1 release works great even on 4 cores.
[G4 Android Development] steadfasterX:
https://xdaforums.com/g4/general/guide-create-custom-x-cores-boot-image-t3718389

Read the very last full sentence of that OP... so replace boot.img wherever you see it in that guide and use the twrp image instead.

.-
[G4 Android Development] a tiny ant:
It works!

Decrypting works although it still gives the "Takes too long, killing process" error message but then works anyway.

Thanks!
[G4 Android Development] steadfasterX:
Yes this is normal as we use the fall back decrypt method ..

Thx for your feedback