yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] Wold:
Does that mean that LOS support will be restored?
[G4 Android Development] kessaras:
he said stock N not los.

and he fixed decryption not encryption.

and just by fixing the encryption it won't restore support because it needs a maintainer too. who will maintain it ? no time for 1 person to be everywhere. me i can't.
[G4 Android Development] ThePiGuy:
Does stock N encrypt differently to LOS N then?
[G4 Android Development] steadfasterX:
When you find a custom ROM for N which can encrypt try it.

By the way what should work is flashing stock then encrypt then flash a custom ROM after decrypting in TWRP
[G4 Android Development] ThePiGuy:
Do they even exist?
[G4 Android Development] steadfasterX:
No.

....and see my post that I have edited it in the meanwhile
[G4 Android Development] ThePiGuy:
Ah ok got it :)
[G4 Android Development] ThePiGuy:
[MENTION=5545101]steadfasterX[/MENTION], sorry if it is off topic, but couldn't we use the N encryption software from stock in custom roms
[G4 Android Development] steadfasterX:
maybe but thats a discussion for a LOS, AOSCP,... thread.

I cant help on that (atm)

-
[G4 Android Development] ziomus684:
deleted
[G4 Android Development] ThePiGuy:
[MENTION=5545101]steadfasterX[/MENTION] I thought you would like to know, your latest update also decrypts non-stock N (I just tried encrypting LOS 14.1, and it worked so I tried decrypting it in TWRP and that also works)
[G4 Android Development] steadfasterX:
many thx for your report!

.
[G4 Android Development] hteles:
First of all, sorry for hijacking the thread.

Just one little direct question! Can you still trim data partition after encryption?

In my d802 it trims, with d855 gives an error about transport endpoint not connected!

Sorry once again to steaderfasterX.

Regards.

Edit: can be done with trimmer app from PlayStore or fstrim -v /data in recovery.
[G4 Android Development] ThePiGuy:
One small question - How do I restore my phone to an unencrypted state. I assumed that wiping the usual partitions (data, system, cache, internal storage and Dalvik/ART cache) would remove it, but I wiped those and freshly installed my OS (LOS 14.1) and my phone is still encrypted
[G4 Android Development] hteles:
Hi,

You have to format data. Full format, will erase internal data.
[G4 Android Development] steadfasterX:
FAQ zzz in the UsU thread ;)

(requires a format data..)
[G4 Android Development] ThePiGuy:
Ah yes I see it now - sorry about that :)
[G4 Android Development] hteles:
Could you please first do :

fstrim -v /data at twrp terminal, please?
[G4 Android Development] ThePiGuy:
I get the error "fstrim: FITRIM: Operation not supported on transport endpoint"
[G4 Android Development] hteles:
Ok, :(

Bummer..... will not encrypt as with my D855 will get laggy after a while.

thanks ( pressed thanks too )

</hijacking over >
[G4 Android Development] ThePiGuy:
[MENTION=5545101]steadfasterX[/MENTION] I am thinking of tweaking something to do with encryption to see if I can make it work, and I was wondering (I have since decrypted my device from last time), does TWRP have a format button if you cannot decrypt the phone? (e.g. the encryption is messed up and so TWRP cannot read the contents of your phone)
[G4 Android Development] steadfasterX:
Huh? Menu wipe -> button format data..?!
[G4 Android Development] ThePiGuy:
Even if I cannot enter a password to decrypt the phone (say it assumes it is wrong due to faulty encryption). Sorry if it is silly - I just don't want to brick my phone
[G4 Android Development] steadfasterX:
When TWRP boots and asking for the password you can press cancel. Then just choose just format data and encryption will be removed (and ofc all data is lost)
[G4 Android Development] ThePiGuy:
Ok thanks :) Now I can get tinkering
[G4 Android Development] steadfasterX:
Good news!

I am able to decrypt OREO in TWRP!

Its in testing phase atm and its not ready yet for the public.

I still need to make it work without manual tricks but the hard part is done :)
[G4 Android Development] zeduck:
That's a very good news :D

Well done steadfasterX!
[G4 Android Development] steadfasterX:
1) When do you need to install a specific flavor (MM, N, O,...) ?

if you want correct time setting in TWRP

if you want to decrypt - so encrypted your device

2) Is there any other reason why I should use a specific flavor (MM, N, O,...) ?

no!

you can use

ANY

flavor if you don't care about the above 2 reasons

3) So I can use ANY TWRP version to install ANY ROM? Or do I need to use a specific flavor (MM, N, O,...) when it comes to install ROMs or other ZIPs?

read 2) again!

ok first public test candidate for TWRP on O:

keep in mind that this has been quickly tested only and it is a

heavy

change:

newest TITAN

switched kernel toolchain (same then TITAN uses)

decrypting O works (aoscp tested)

complete build on O sources (TWRP)

full changelog: https://github.com/steadfasterX/android_device_lge_g4/commit/c801879b86f519035a3c

download: http://leech.binbash.it:8008/TWRP/O/

have fun
[G4 Android Development] Frazercrib:
H811 user

Using the latest 3.2 twrp (o sources)

I get error 7 when flashing aoscp Oreo rom
[G4 Android Development] steadfasterX:
no log - no help
[G4 Android Development] Minto107:
Hey sted, some time ago I flashed Oreo version of TWRP to see clock(incorrect time) bug go away, but unfortunately on my 602 G4 it's still rolling back to 2015, with time offset of 15 mins if I remember correctly. Any log or anything like that could help you? I know it's very minor issue but if in any case you'd like to take a look into it just quote my post or mention me or get me on telegram ;)
[G4 Android Development] vdowner:
Pls help ..

Please help..

i have an LG G4 and its unlocked bootloader, installed twrp, have flashed aoscp rom but calls/texts/data is not working.

Pls help me
[G4 Android Development] steadfasterX:
No log no help.. I fixed time dozens of times in the past but I need the recovery log...
[G4 Android Development] Minto107:
Sure thing, recovery log is enough? I'll try to provide it tomorrow or so ;)
[G4 Android Development] steadfasterX:
yes just boot into TWRP and grab the recovery log :)
[G4 Android Development] steadfasterX:
Just a short heads up

just wanna let you know that I'm working on the merge to android 8.1 for TWRP.

This is needed to enable official builds again and its a heavy change again - even when I had a working 8.0 branch already... (one of the reasons why it takes so long).

The hard stuff has been made already - I fixed all build errors, adapted all stuff like the unified device model detection and so we now have a android-8.1 branch for the TWRP device tree which seems to be fully working. It will replace the previous Oreo one once all tests have been done.

Atm I have issues on my testing device so it would be a great help if someone can test this EXPERIMENTAL build for:

output of this when booted to TWRP:

adb shell
getprop |egrep -i "(usu|model)"

decryption (only for

Oreo

ROMs)!

backup

restore

I would like to have at least one official unlocked device tester and one user who had UsU'd his/her device

recovery logs are needed only

when errors/problems occur.

I will also try to merge the N and O decryption and time issues but thats for later...

.
[G4 Android Development] ThePiGuy:
[MENTION=5545101]steadfasterX[/MENTION] just a question - when I backup via twrp, flash another rom etc, and then restore my backup, my password screen remains (I have set a pattern for my lockscreen) but it will not let me in even with the right pattern. Is this normal? I end up having to go into twrp, and delete the gatekeeper files and a few more to remove the lockscreen so I can gain access.

Do the gatekeeper files get corrupted in a twrp backup?
[G4 Android Development] kessaras:
gatekeeper saves the passes in keymaste which is not backed up and gets resetted.

delete the gatekeeper files in /data/data or /data/system i dont remember where exactly and reboot.

Or remove pass before you backup
[G4 Android Development] steadfasterX:
Yes that's normal.

Just the gatekeeper files need to be deleted.

(other then [MENTION=5461026]kessaras[/MENTION] said they WILL be backuped and restored by TWRP that's not the reason for the problem)

Well I have a guess WHY that happens (and that has nothing(!) to do with TWRP):

Have you tried the same with aoscp Oreo(!)? That would help to know ..

Means in aoscp O: set screen lock, backup with TWRP, FORMAT data, restore backup

...same result?
[G4 Android Development] tqwzUX6fn39GZMEzSnDF:
I've done this in the past with same result.
[G4 Android Development] steadfasterX:
Thx for sharing. How long ago?
[G4 Android Development] tqwzUX6fn39GZMEzSnDF:
Mmhh... I don't remember exact date, but I think it was January.
[G4 Android Development] steadfasterX:
Ok. I need an actual test on a current build...
[G4 Android Development] ThePiGuy:
[MENTION=5545101]steadfasterX[/MENTION] following on from the Lineage thread, it hasn't appeared on boot, so I haven't got a log yet, but I think it appears after flashing a zip, so I'm just backing up now so I can flash a zip and test

EDIT: [MENTION=5545101]steadfasterX[/MENTION] never mind, after I flashed back to the nougat version from oreo it all seems to be fine now
[G4 Android Development] tqwzUX6fn39GZMEzSnDF:
OK, I will test.

What exactly should I backup and restore?

Edit: So I made backup of Boot, System and Data. Afterwards

- Wipe -> Format Data

- Reboot -> Recovery

- Noticed Time and Date is wrong in TWRP

- Restore Boot, System and Data

- Reboot System

I had to enter lockscreen PIN and the correct PIn was correctly detected.

(Moreover it was first time I didn't have no sim detection).
[G4 Android Development] steadfasterX:
Thx! Much appreciated.

Yea that's what I assumed. The screen lock issue when restoring has nothing to do with TWRP. TWRP just restores as it should.

A bit background for those interested:

The issue is the gatekeeper (software in the ROM) which is also the reason why LOS has abandoned the g4 builds. Gatekeeper is responsible to communicate, read, write key master files and it has been fixed in aoscp O but not in N (yet). We never had issues with encryption on N ROMs. And encryption was not the reason for the removal on the LOS site. Encryption and decryption is working fine but the part gatekeeper is responsible for.. That's the reason as users can't screen unlock encrypted devices.

I currently investigating that issue in LOS and found issues with writing(!) the key master file on N. This will be fixed soon (again that's nothing TWRP related!) but until then deleting the files in N ROMs is the only workaround.
[G4 Android Development] ThePiGuy:
[MENTION=5545101]steadfasterX[/MENTION] I was wiping my phone for a test and I got a "Unable to mount storage" error. I thought you might like to know about it - I think this was what I was talking about before. Log is attached

Edit: just noticed Micro SD card was down as storage after I had shut down and removed it so this might be the error
[G4 Android Development] steadfasterX:
The message was about external sdcard..
[G4 Android Development] ThePiGuy:
Ok cool that explains it :). By the way, with my unofficial LOS 15.1 I can encrypt and your O TWRP works perfectly decrypting it
[G4 Android Development] steadfasterX:
Great! I'm still working on the fix for LOS 14.1 though..
[G4 Android Development] ThePiGuy:
Ok so just to clarify what you mentioned earlier, do you think you might have found the reason why N based ROMs can't unlock once encrypted

Edit: fix inaccuracy
[G4 Android Development] steadfasterX:
Maybe. . The tests are ongoing but here is the wrong place for that discussion.. ;)
[G4 Android Development] ThePiGuy:
Yeah sure I understand. Great work though :)
[G4 Android Development] obvious:
I love trying to follow the odd technical discussion.
[G4 Android Development] Netsab:
Hi,

First, thanks a lot for your work.

Sorry for my dumb questions, but I don't understand this part which seems to be important.

What are "the above 2 reasons" ? I see one, not two.

"read 2) again" : I can see 1) and 3) but no 2)...

Or is there a joke I don't understand?

Thanks.
[G4 Android Development] steadfasterX:
consider to view this thread in a browser then - or IF you are using a browser use another one :P

see the attached pic. thats how the post you quoted looks usually
[G4 Android Development] Netsab:
Ok, sorry for disturbing
[G4 Android Development] fil3s:
Thx steadfasterX :) im using ur RR 5.8.5 builds with titan by kessaras with TWRP preview N 109

Perfect :) no issues at all :D

Looking forward to seeing this on twrp.me :D

PS thx again! :angel:
[G4 Android Development] fil3s:
[MENTION=537942]sfx[/MENTION] what are the appropriate partitions to back up? :) sorry if you already mentioned. Im about to flash los15.1 but dont wanna lose my important data !! ;)

Thx
[G4 Android Development] steadfasterX:
See the UsU FAQ #17

Keep in mind: TWRP is not able to backup your internal storage!

-.
[G4 Android Development] hteles:
Hi, [MENTION=8699949]ThePiGuy[/MENTION] , [MENTION=5545101]steadfasterX[/MENTION]

Been trying to find a solution for this problem, it also affects LG G3 with encrypted data.

Have found some info here -> https://github.com/TeamWin/android_device_oneplus_oneplus2/issues/7

For now i did mount -o remount,discard /data

fstrim still not working though.

Regards
[G4 Android Development] dat_benjie:
Hi,

first of all, thanks for the ongoing work on the G4. With the 103 as well as the latest 109 TWRP release, my external SD-card does not get recognized properly. It is a 16 GB card which is correctly shown on lineage-14.1-20180322-UNOFFICIAL-h815. In TWRP however, the card apparently only has a 196 MB capacity. The file format is fat32, so I think this shouldn't be the issue here right? Am I missing sth?

Any help would be appreciated, so thanks in advance :)
[G4 Android Development] steadfasterX:
twrp recovery log pls
[G4 Android Development] dat_benjie:
Hi,

Recovery log:

http://www.filedropper.com/recovery_8

dmesg:

http://www.filedropper.com/dmesg_1

Thank you
[G4 Android Development] dat_benjie:
Hi again,

nevermind, I found the solution by accident. While in Android I reformatted the SD-card, now it gets properly recognized in TWRP.

Sorry for bothering :)
[G4 Android Development] fil3s:
Deleted
[G4 Android Development] lHemaNl:
Hello Guys,

I have problem with properly unlocking H815. I went through guide on the first page and stoped on this point: " TWRP will show your REAL device model when connected to the PC now". Well, mine not showing proper phone name, its shows some, a think korean, letters.

Would like to place here a log file, but I don't have enough posts to place external links. So if someone would like to help me I will send link to log via PM.

Thanks in advance.
[G4 Android Development] steadfasterX:
That goes here:

https://xdaforums.com/g4/general/unlock-unlock-lg-g4-device-usu-t3760451/post76592364
[G4 Android Development] steadfasterX:
Announcement

official TWRP builds are about to come back very soon!

I sorted out all issues on the android-8.1 tree and so nothing should avoid from getting back.

The testing build of TWRP was successful and now we just wait for a productive build which will happen as soon as @bigbiff will have the time to start it.

You may already noticed the changes on http://twrp.me -> I have added all known G4 models to the list of supported devices plus a forwarding page for every model pointing to the unified build.

Notice:

TWRP 3.2 official will support decryption and working time only for

Oreo

based ROMs. If you want to decrypt N or MM ROMs in TWRP or expect working time u are stuck with my unofficial PREVIEW builds.

... thats how it goes. Everyone is moving forward right ;)

Regardless of the above you can use the official TWRP builds for ANY rom and ANY android version and on ANY g4 model.

EDIT:

twrp-3.2.1-0 official is up!

Its identical to twrp-3.2.1-PREVIEW-123_g4_O - just as an official build.

All PREVIEW flavors have received an updated build (#123) today as well:

MM, N

- kernel updated

- sdcard can be partitioned now (advanced menu)

O

- like MM/N plus: changelog

All changelogs

can be found as usual in the changelog post

have fun

sfX
[G4 Android Development] tqwzUX6fn39GZMEzSnDF:
deleted
[G4 Android Development] ThePiGuy:
(wrong thread :))
[G4 Android Development] grantdb:
Ok so I would like to use the official TWRP app to keep updated, however selecting my model H812 has blank page but the unified shows files.

I am running twrp-3.2.1-PREVIEW-109_g4_N, don't encrypt and don't care about the time thing, can I update to the official unified version twrp-3.2.1-0-g4.img? Any benefit or should I just wait for my specific model? I am running stock N UsU H812

Thanks!
[G4 Android Development] steadfasterX:
The app is buggy when it comes to unified models. Sorry but I can't change that as I'm not the TWRP app dev. Just select the unified one.

its what is says: unified and there are no model specific images available as this wouldn't make any sense when we have a unified one.

If you wanna know why the app behaves like that just open twrp.me in a browser and select your model. It's just a landing page forwarding you to the unified page.

So just select the unified one in the app and you're good.
[G4 Android Development] mikemech:
[MENTION=5545101]steadfasterX[/MENTION] One question before I move to the new twrp-3.2.1-0-g4.img:

In your latest announcement you write "- kernel updated". And in the OP it says: "TITAN kernel inside (build with UBER Toolchain)"

I thought the Kernel can be installed by itself or as part of a ROM but does the phone's kernel also get updated doing a TWRP update? If yes, which version of TITAN is used in twrp-3.2.1-0-g4? Is it one that's also downloadble from your leech.binbash page?

Thanks for all your work on the G4!
[G4 Android Development] steadfasterX:
TWRP is a mini Android which also runs a kernel. This is nothing you need to care about and is a complete different thing then when installing the regular android kernel.

-
[G4 Android Development] mikemech:
"This is nothing you need to care about" => glad to hear that :D

Thanks for the clarification :good:
[G4 Android Development] fil3s:
Alright !! :D :svetius:

Hey u might be able to make an update to usu marking it as official unlock for LG devices that were not officially unlocked!! :D
[G4 Android Development] Netsab:
Hi, if I stay on N can I flash the new official build?

Thanks
[G4 Android Development] ThePiGuy:
TWRP is independent of your ROM (with the exceptions being 1) latest official twrp will have the wrong time on N ROMs and 2) latest official twrp cannot decrypt N roms - not an issue as N based aosp ROMs cannot encrypt on g4 anyway)

Edit: basically, yes, you can install the latest official twrp with an N based rom
[G4 Android Development] grantdb:
Just to confirm, using official TWRP app to flash the latest unified is flawless.

Thank you!

Edit: Full backup completed successfully and time is correct.
[G4 Android Development] mikemech:
So you're saying that you flashed the official twrp-3.2.1-0-g4.img and you have the correct time settings when using LG Stock 7.0 Nougat?

Doesn't that contradict what [MENTION=8699949]ThePiGuy[/MENTION] wrote above and what [MENTION=5545101]steadfasterX[/MENTION] wrote here: https://xdaforums.com/showpost.php?p=76617247&postcount=887

"TWRP 3.2 official will support decryption and working time only for Oreo based ROMs. If you want to decrypt N or MM ROMs in TWRP or expect working time u are stuck with my unofficial PREVIEW builds."

Or is this time offset only related to TWRP and not to the time displayed by the phone?

Sorry for all these questions, just want to make sure I understand correctly..... :confused:
[G4 Android Development] ThePiGuy:
You never know - maybe he isn't using stock N any more.

Anyway, yes decryption and the time inside twrp will not work on an N rom but the time in the actual rom will work fine.
[G4 Android Development] mikemech:
[MENTION=8699949]ThePiGuy[/MENTION] That's what I hoped the answer would be :D

Many thanks for the clarification!!
[G4 Android Development] grantdb:
Time is correct in TWRP on stock v29a Nougat using the official TWRP flashed with the official TWRP app. Could just be me and I did need to adjust time zone, no guarantees it works for anyone else. I also use Titan kernel for stock if that might make a difference. Time is only different in TWRP for users and doesn't affect the ROM time settings.

Cheers
[G4 Android Development] toub74:
Hi,

Not sure the question fits here but I try: is there a way to check my modem version ? I'm not sure what I flashed when I decided to install LOS 14.1.

If I'm still on a V20x and want to switch to V29a, do I have to clean install a ROM too or can I just flash the modem ?
[G4 Android Development] ThePiGuy:
You can use SALT (@steadfasterX's tool). He has a thread here about it. If you have a Linux environment then you can set it up in there, if not then you can make a bootable USB using FWUL (@steadfasterX's Linux distribution with SALT already installed). From there it will tell you all the information you need.

Btw, v20x sounds like H811. Only H815 has v29a, so v20x is fine for h811
[G4 Android Development] toub_:
The x was for "something", I have a H815.

What about the modem flashing, if you don't mind me asking again ? Can it be done independantly or does it imply a fresh install ?
[G4 Android Development] ThePiGuy:
Oh right :D

Yes, you can get it from http://leech.binbash.it:8008/stock/LG/h815/29a/

There is a bootloader only one that will flash bootloader, modem and LAF (v29a download mode - this will cause issues with using salt, but other than that it's fine)

Make a full backup in twrp (and also with salt if you want) so you can roll back to v20 if needed (stock MM won't work without v20 firmware)

Edit: Roll back to previous version, not just v20g
[G4 Android Development] steadfasterX:
New Official release

twrp-3.2.2-0

Release date: 2018-07-01

Download: https://twrp.me

Device Tree changelog: (no changes)

TWRP sources changelog: twrp-3.1.1-0 <--> twrp-3.2.2-0 (previous official vs. current official)

Summary

changelog:

https://twrp.me/site/update/2018/07/01/twrp-3.2.2-0-released.html

New PREVIEW release

read more about the <flavor>'s in the OP!

twrp-3.2.2-PREVIEW-127_g4_<flavor>

Status: stable

Release date: 2018-07-05

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

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

Device Tree changelogs:

MM flavor

N flavor

O flavor --> main changes (and difference from the official): sdfat as exfat driver, newest titan, smaller size (background)