yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] steadfasterX:
now that all preparation and web stuff is done I can release more frequently from BETA to STABLE .. soooo...

....the next official version get released :)

note: All new builds are twrp-X.x.x-x-

g4

.img .That change is due to the unification of both devices (h811 & h815) and so is valid for both.

Unfortunately we lost the older h811 TWRP images so if anyone has them pls upload them somewhere and share me the link. I will put them back to the official website then.

Latest Official release

Release date: 2017-06-21

Download: https://twrp.me/devices

Device Tree changelog: twrp-3.1.1-0 <--> twrp-3.1.1-1 (previous official vs. current official)

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

Summary

changelog:

decryption fixed (again) for CM/AOSP

Known Issue:

If you wanna download and flash by the official TWRP app you have to search for g4 and select the entry with both "

h811 , h815

". Otherwise you will not find any files.

I work on removing the device specific dropdowns from the app

.
[G4 Android Development] HorstiG:
[MENTION=5545101]steadfasterX[/MENTION]

Unfortunately, the last update does not work. LG G4 H815, Lineage RR 7.12

Here a Log File

https://www.dropbox.com/s/oyq5euq7pg2dxs0/recovery.log?dl=0
[G4 Android Development] steadfasterX:
Oh it DOES work ;)

But you have selected the system IMAGE option AND your external sd card does not met the requirement for that backup method..

I created a FAQ entry for that its no. 13 in https://xdaforums.com/showpost.php?p=68249027&postcount=3

Edit:

Thx that you provided the logs! Not everyone does and that makes it possible to analyze and debug quickly.

.
[G4 Android Development] HorstiG:
Thank you!

So you likely will NEVER use the Image option or when you're a paranoid one only.

grins
[G4 Android Development] ast00:
I'm getting a bit pissed at LG and I need some help.

After typing fastboot boot (twrp.img), it works fine. Then after navigating to the img file and flashing it as "recovery", I boot into Android. Then I type adb reboot recovery and I get an image with a broken android on it.

After spending an hour and not getting anywhere I used fastboot flash recovery (twrp.img) and the same exact thing happens. I also tried multiple versions, no luck. The phone is H815 running official MM and is unlocked.

Why?
[G4 Android Development] steadfasterX:
Try this:

fastboot boot twrp.img

In TWRP flash TWRP to the recovery partition

Choose Reboot -> Recovery!!!

If that worked and you see TWRP go on and boot to android.

When in android type

adb reboot recovery (when you have a PC connected)

or

reboot recovery (when in an android terminal app)

Let me know if that works for you.

.
[G4 Android Development] BIG_BADASS:
I am still trying to understand everything on the conceptual level...

Now I come from the PC world and things are quite different there.... to get an understanding of exactly what is custom recovery.. I need to know what would be the equivalent of TWRP in the PC world......

---------- Post added at 08:17 AM ---------- Previous post was at 07:58 AM ----------

By 'encrypted phone', do you mean the ext4 partition is encrypted?
[G4 Android Development] kessaras:
heh, recovery is something between the bootloader and boot.

it mainly is for backing up and restoring, or cleaning the data partition.

By using a custom recovery we "unlock" more options. like flashing a rom for example.

partition is not encrypted. but you can encrypt it.

the data partition ofc. ext4 are all partitions. its the main android format.

you can format to f2fs too but kernel and rom must support it too.
[G4 Android Development] BIG_BADASS:
So the PC equivalent would be something like this:

https://www.acronis.com/en-eu/personal/computer-backup/

?

Or a Windows recovery disk?
[G4 Android Development] kessaras:
windows recovery disk fits more, but still it's not that.

At a pc (if we talk about windows) , windows are creating a small partition thats used to restore at an earlier time point. When you use the windows 10 disk and choose to format the hard disk , have you noticed a small partition thats system reserved ? thats the recovery partition.

it is used the same way. to restore. it only has information, not all the files of course. windows use shadow copy.

Anyway , thats that. And on windows 10 you go there by using the Shift+Reboot.
[G4 Android Development] BIG_BADASS:
Thank you, very well explained.

So TWRP is like a replacement for that recovery partition, the way I understand?
[G4 Android Development] kessaras:
yeap and a custom one gives more options. Otherwise recovery can originaly only backup,restore,clean.
[G4 Android Development] BIG_BADASS:
Short, simple, and to the point.

Thanks a lot!
[G4 Android Development] kessaras:
deleted.

Fast typing mistake.
[G4 Android Development] SavageRobot:
Something a little strange, running latest TWRP, thought date and time problem had been fixed a while back but for some reason I've noticed backups are defaulting to 2015?

I've been on CRDroid for a couple months now and just risked it no backups and just dirty flashing updates since then. I used to always run Imperium or something so perhaps it's something between stock and custom ROMs?

I've been trying to backup twice today 7.1.2 and when the screen turns off I can't get it back on. I think it is still running as the phone stays pretty hot but I can't check progress or look at it at all as double tap screen and power button do nothing. Ended up just battery pulling both times.
[G4 Android Development] crysknife4life:
Although it's not a solution look here for a workaround of the incorrect date/time in TWRP: https://xdaforums.com/g4/help/h815-hardware-clock-incorrect-unable-to-t3648535
[G4 Android Development] steadfasterX:
yes it was fixed but LOS has changed something so the issue is back when u are using newer ROM builds.

black screen is "normal' - at least for some users (have no idea why not for all).

just wait and be patient it will get responsive after a while (5-10 min latest).

.
[G4 Android Development] ufocus:
Don't let it get too hot. That was the case with me.
[G4 Android Development] SavageRobot:
Ah well that's inconveinient. I thought I had read that somewhere in the past which is why I was not too bothered about that, just need to remember to date it myself. The problem I was worried most about is the backing up staying black screen. I am assuming that that's more ROM based than device specific too then as I never had a problem with it before. Would sometimes be slow to wake up but never just staying dead screen. I will try and backup again. Thanks.
[G4 Android Development] steadfasterX:
hm ok.. i use MM based and LL based ROMs atm only so maybe it is related to N based ROMs?

.
[G4 Android Development] kessaras:
Hi mate, did you have the time to check/compare the drivers with the nougat ?

Imma test our twrp now on nougat stock to see how it rolls.

i'm not gonna check it now before i flash it cause i don't have time. i only have time to send logs if i find a bug.

EDIT:

our latest twrp works great.

i just flashed magisk and a modded g6 launcher.

Maybe, only problem is that it lags a lot. It's like the fps is very very low.

Not a temperature issue. it was at 32 C
[G4 Android Development] ufocus:
[MENTION=5545101]steadfasterX[/MENTION] here's the output

~ # [6nDDPATH='/dev/block/bootdevice/by-name/*'
~ # for part in $(find $DDPATH | egrep -v "(/cache|/userdata|/system|/recovery|/
boot|/grow)");do name=${part/*\/}; echo "dd if=$part bs=512 status=progress | gz
ip -vc > /external_sd/fulldump/${name}.gz";done
/tmp/dummy.gz
dd if=/tmp/recovery.log bs=512 status=progress | gzip -vc > ~ # dd if=/tmp/recovery.log bs=512 | gzip -vc > /tmp/dummy.gz
my.gz38+1 records in
38+1 records out
19609 bytes (19.1KB) copied, 0.000195 seconds, 95.9MB/s
<stdin> to <stdout>
~ # dd if=/tmp/recovery.log bs=512 status=progress | gzip -vc > /tmp/dummy.gz
<stdin> to <stdout> Segmentation fault
[G4 Android Development] ufocus:
[MENTION=5545101]steadfasterX[/MENTION]

Selected EFS, Unlock state and firmware. Nothing else showing for me
[G4 Android Development] steadfasterX:
Oh yes can be true.. Sorry that I miss that.. Will be fixed tomorrow.

Thanks for the log! really appreciated

It's just a display issue btw.. The bl state seems to get backuped fine as well silently..

.
[G4 Android Development] raptorddd:
so i should wait for twrp stead fix right.?
[G4 Android Development] kessaras:
BL Lock state backup

string res 'generating_digest1' and 'generating_digest2' not found.

generating digest...

digest_created not found. using default value.

digest created.

EDIT:

2nd recovery log. And with this twrp i can't flash magisk
[G4 Android Development] steadfasterX:
Please try the latest BETA in the download section and

provide the recovery log

.

Also do this (before the backup or after doesnt matter):

adb shell sha256sum /dev/block/bootdevice/by-name/pmic
adb shell sha256sum /dev/block/bootdevice/by-name/rpm
adb shell sha256sum /dev/block/bootdevice/by-name/fsg
adb shell sha256sum /dev/block/bootdevice/by-name/persistent
adb shell sha256sum /dev/block/bootdevice/by-name/aboot
adb shell sha256sum /dev/block/bootdevice/by-name/sdi
adb shell sha256sum /dev/block/bootdevice/by-name/sbl1
adb shell sha256sum /dev/block/bootdevice/by-name/misc

Please try also this:

adb shell

type something no matter what and use the arrow keys (left and right) and pos1/home and end multiple times

e.g type:

this is an amazing twrp test

then not enter just use the arrow keys to go back to the word "twrp" then type anything here then go forward with the end key

type something again go back and so on

do you see any strance characters magically added? like "^[51" or DD or similar while doing this?

that was an issue in the previous twrp versions which I hopefully fixed here as well..

thanks

should be fixed in the latest beta (sfx-6)

.
[G4 Android Development] kessaras:
same digest error but this time i found the backup in /sdcard/twrp so it was created.

flashing magisk worked and boot.img too. so although it works it still gives digest error.

Moving arrows worked they didn't give any chars , but backspace did. Screenshots in .zip with the .log
[G4 Android Development] kessaras:
this is how it should look right ?

thats how it looks now on nougat.

Maybe i can help with some other way ? if i decompile the kernel and send it to you ?
[G4 Android Development] steadfasterX:
no thx i know what the issue is

thx will look into the logs asap

UPDATE

could you re-do the sha256sum commands like this please (no backup run required when u didnt deleted the previous one)?

adb shell sha256sum /data/media/0/TWRP/BACKUPS/*/*/rmisc.emmc.win

adb shell sha256sum /data/media/0/TWRP/BACKUPS/*/*/drm.emmc.win

adb shell sha256sum /data/media/0/TWRP/BACKUPS/*/*/persistent.emmc.win

adb shell sha256sum /data/media/0/TWRP/BACKUPS/*/*/bl*.emmc.win

adb shell sha256sum /dev/block/mmcblk0p35

adb shell sha256sum /dev/block/mmcblk0p22

adb shell sha256sum /dev/block/mmcblk0p40

adb shell sha256sum /dev/block/mmcblk0p8

adb shell sha256sum /dev/block/mmcblk0p7

adb shell sha256sum /dev/block/mmcblk0p2

adb shell sha256sum /dev/block/mmcblk0p5

adb shell sha256sum /dev/block/mmcblk0p37

adb shell sha256sum /dev/block/mmcblk0p4

adb shell sha256sum /dev/block/mmcblk0p6

adb shell sha256sum /dev/block/mmcblk0p3

.

.
[G4 Android Development] steadfasterX:
Really? No one?
[G4 Android Development] kessaras:
Will do but in the morning mate.

Am I the only one ? ?

Maybe they don't understand how important TWRP is
[G4 Android Development] steadfasterX:
Exactly what I feel..

.
[G4 Android Development] kessaras:
here it is !
[G4 Android Development] steadfasterX:
Many thx!!

You saw my updated sha256 commands?

.
[G4 Android Development] kessaras:
Yeap

adb shell sha256sum /data/media/0/TWRP/BACKUPS/*/*/rmisc.emmc.win

adb shell sha256sum /data/media/0/TWRP/BACKUPS/*/*/drm.emmc.win

adb shell sha256sum /data/media/0/TWRP/BACKUPS/*/*/persistent.emmc.win

adb shell sha256sum /data/media/0/TWRP/BACKUPS/*/*/bl*.emmc.win

adb shell sha256sum /dev/block/mmcblk0p35

adb shell sha256sum /dev/block/mmcblk0p22

adb shell sha256sum /dev/block/mmcblk0p40

adb shell sha256sum /dev/block/mmcblk0p8

adb shell sha256sum /dev/block/mmcblk0p7

adb shell sha256sum /dev/block/mmcblk0p2

adb shell sha256sum /dev/block/mmcblk0p5

adb shell sha256sum /dev/block/mmcblk0p37

adb shell sha256sum /dev/block/mmcblk0p4

adb shell sha256sum /dev/block/mmcblk0p6

adb shell sha256sum /dev/block/mmcblk0p3

Piece of cake. I'm using the beta 6 permanently since it can flash successfully everything. So I can just do any test in seconds
[G4 Android Development] steadfasterX:
What no results? Wtf?

Could you..

Mount data

adb shell

sha256sum /data/media/0/TWRP/BACKUPS/*/*/rmisc.emmc.win

sha256sum /data/media/0/TWRP/BACKUPS/*/*/drm.emmc.win

sha256sum /data/media/0/TWRP/BACKUPS/*/*/persistent.emmc.win

sha256sum /data/media/0/TWRP/BACKUPS/*/*/bl*.emmc.win

sha256sum /dev/block/mmcblk0p35

sha256sum /dev/block/mmcblk0p22

sha256sum /dev/block/mmcblk0p40

sha256sum /dev/block/mmcblk0p8

sha256sum /dev/block/mmcblk0p7

sha256sum /dev/block/mmcblk0p2

sha256sum /dev/block/mmcblk0p5

sha256sum /dev/block/mmcblk0p37

sha256sum /dev/block/mmcblk0p4

sha256sum /dev/block/mmcblk0p6

sha256sum /dev/block/mmcblk0p3

I expect a result for each command.... ?!

.
[G4 Android Development] crysknife4life:
I'm trying to run the commands tomorrow if it helps.
[G4 Android Development] raptorddd:
i have trouble understanding commands or procedure.. :(

anything adb related i have never done.
[G4 Android Development] kessaras:
Flash beta 6 from folder here in this thread.

boot into TWRP

go to Backup and select:

EFS

"BL unlock state"

"BL stack test"

-> and start the backup

adb pull /tmp/recovery.log

( Take that log send it here )

Also do this (AFTER the backup is finished):

(Copy paste it all as it is)

adb shell

sha256sum /data/media/0/TWRP/BACKUPS/*/*/rmisc.emmc.win

sha256sum /data/media/0/TWRP/BACKUPS/*/*/drm.emmc.win

sha256sum /data/media/0/TWRP/BACKUPS/*/*/persistent.emmc.win

sha256sum /data/media/0/TWRP/BACKUPS/*/*/bl*.emmc.win

sha256sum /dev/block/mmcblk0p35

sha256sum /dev/block/mmcblk0p22

sha256sum /dev/block/mmcblk0p40

sha256sum /dev/block/mmcblk0p8

sha256sum /dev/block/mmcblk0p7

sha256sum /dev/block/mmcblk0p2

sha256sum /dev/block/mmcblk0p5

sha256sum /dev/block/mmcblk0p37

sha256sum /dev/block/mmcblk0p4

sha256sum /dev/block/mmcblk0p6

sha256sum /dev/block/mmcblk0p3

Every command will have an output below. Copy paste from terminal everything here.

Just like I did.

sha256sum is like md5 but it's less vunerable to attacks.

He can check files integrity and authenticity.

Lastly he can compare sums to find possible errors.

Of course I can't do all that I just know some basics
[G4 Android Development] crysknife4life:
Here my checksums
[G4 Android Development] steadfasterX:
Thanks but I also need the recovery log after doing the backup

.
[G4 Android Development] crysknife4life:
Here you go
[G4 Android Development] steadfasterX:
Great results. All looking good on your logs.. You're done for the moment ;)

Your logs showing that my idea perfectly works. :)

And [MENTION=5461026]kessaras[/MENTION] logs looking good as well thx. But here one thing is strange. Could you please do this and gimme the console output?

adb shell

sha256sum /dev/block/mmcblk0p40

Thx

I will release another version soon with some more stuff..

.
[G4 Android Development] kessaras:
sha256sum /dev/block/mmcblk0p40

bd80c0bc5639140947c0d02a0320713eb81d80d6cdfdb6e6e66e7dc9420650b2 /dev/block/mmcblk0p40
[G4 Android Development] crysknife4life:
Happy to help and if you have the chance, please fix the date / time issue again (well in case it isn't already fixed in the beta6... forgot to test this)
[G4 Android Development] steadfasterX:
Yours and kessaras seems to have the correct time set. At least when you haven't change the backup name manually..

The question is still why it sometimes works. The thing is I believe it depends on the ROM installed.

What ROM do you had installed when taking the backup? Nougat stock? Any other stock? or any other ROM? Kessaras had nougat stock installed..

.
[G4 Android Development] crysknife4life:
Well the time was correct because I deleted that file atz_2 file as you were suggesting in the other thread. I'm using the latest LOS14.1
[G4 Android Development] steadfasterX:
Hm could you test it again? No backup needed just boot from Android into TWRP and check the automatic generated backup name.

Try it twice or more to check if it behaves the same. Always boot from android to TWRP when testing.

The deletion of the ats2 file should be needed only once after installed LOS but you're the second one with LOS 14 with this problem.

On stock and LOS 13 there isn't this issue.

If the problem recurring it is due to a change in LOS.

.
[G4 Android Development] crysknife4life:
OK, I did several reboots and it is always the same incorrect time. I get only the correct one when I delete the /data/time/ats_2 in recovery and reboot from there again in recovery. As soon as I come from System the file is back and the time back in 2015
[G4 Android Development] steadfasterX:
Ok it's definitely a LOS 14 change then. Thanks

Edit

Ok I found the reason :)

Will release a fix in the next beta...

.
[G4 Android Development] ufocus:
I'm having the time issue too on crDroid v3.7.

That was fast man!

Thank you for all your efforts and keeping this device alive!
[G4 Android Development] steadfasterX:
could you try another typing test but this time within the TWRP terminal instead?

I first thought it is busybox related but it seems to be something else. I wanna exclude adb as an issue here

.
[G4 Android Development] kessaras:
all of them ?!

sha256sum /data/media/0/TWRP/BACKUPS/*/*/rmisc.emmc.win

sha256sum /data/media/0/TWRP/BACKUPS/*/*/drm.emmc.win

sha256sum /data/media/0/TWRP/BACKUPS/*/*/persistent.emmc.win

sha256sum /data/media/0/TWRP/BACKUPS/*/*/bl*.emmc.win

sha256sum /dev/block/mmcblk0p35

sha256sum /dev/block/mmcblk0p22

sha256sum /dev/block/mmcblk0p40

sha256sum /dev/block/mmcblk0p8

sha256sum /dev/block/mmcblk0p7

sha256sum /dev/block/mmcblk0p2

sha256sum /dev/block/mmcblk0p5

sha256sum /dev/block/mmcblk0p37

sha256sum /dev/block/mmcblk0p4

sha256sum /dev/block/mmcblk0p6

sha256sum /dev/block/mmcblk0p3
[G4 Android Development] steadfasterX:
no no ! not the sha sums.. the typing test ;)

type a text with multiple words then do this multiple times:

use the arrow keys of the keyboard use backspace and such

watch if you still see strange characters when doing this

.
[G4 Android Development] kessaras:
in twrp terminal it works great, no strange chars.
[G4 Android Development] steadfasterX:
ok great. it is then adb related.. have to find out when they changed something related to this .. :p

thx for the moment ;)

.
[G4 Android Development] steadfasterX:
[MENTION=5461026]kessaras[/MENTION] or anyone else on Nougat

and someone using a stock or stock based

MM

ROM:

for the time fix on STOCK (LineageOS is fixed I hope) I need some more tests.

could u test on your stock Nougat what happens when you do this:

Boot into TWRP then execute:

adb shell

getprop

dmesg -c >> /dev/null

/sbin/time_daemon

dmesg

.
[G4 Android Development] kessaras:
i put the result in a file
[G4 Android Development] steadfasterX:
thx :)

it seems date/time is working for you the whole time correct?

Could you please re-do those commands in TWRP?

adb shell

getprop

dmesg -c >> /dev/null

/sbin/time_daemon

dmesg

.
[G4 Android Development] steadfasterX:
could u pls give me your results of:

Boot into TWRP (doesnt matter what TWRP version)

adb shell

getprop | grep -i build

getprop | grep -i version

.
[G4 Android Development] ufocus:
The result is not in TWRP. It's from Termux in Android. Don't have a PC near me.

$ getprop | grep -i build
[ro.bootimage.build.date]: [Sat Aug 12 03:33:04 EDT 2017]
[ro.bootimage.build.date.utc]: [1502523184]
[ro.bootimage.build.fingerprint]: [lge/lineage_h815/h815:7.1.2/NJH47F/540755fc52:userdebug/release-keys]
[ro.build.characteristics]: [default]
[ro.build.date]: [Sat Aug 12 03:33:04 EDT 2017]
[ro.build.date.utc]: [1502523184]
[ro.build.description]: [p1_global_com-user 6.0 MRA58K 152940055675e release-keys]
[ro.build.display.id]: [NJH47F]
[ro.build.fingerprint]: [lge/p1_global_com/p1:6.0/MRA58K/152940055675e:user/release-keys]
[ro.build.flavor]: [lineage_h815-userdebug]
[ro.build.host]: [hokiealumnus-ubuntu]
[ro.build.id]: [NJH47F]
[ro.build.product]: [h815]
[ro.build.selinux]: [0]
[ro.build.tags]: [release-keys]
[ro.build.type]: [user]
[ro.build.user]: [hokiealumnus]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.base_os]: []
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [540755fc52]
[ro.build.version.preview_sdk]: [0]
[ro.build.version.release]: [7.1.2]
[ro.build.version.sdk]: [25]
[ro.build.version.security_patch]: [2017-08-05]
[ro.cm.build.version.plat.rev]: [0]
[ro.cm.build.version.plat.sdk]: [7]
$ getprop | grep -i version
[gsm.version.baseband]: [3-00101-M8992FAAAANAZM-1.31581.1]
[gsm.version.ril-impl]: [Qualcomm RIL 1.0]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.base_os]: []
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [540755fc52]
[ro.build.version.preview_sdk]: [0]
[ro.build.version.release]: [7.1.2]
[ro.build.version.sdk]: [25]
[ro.build.version.security_patch]: [2017-08-05]
[ro.cm.build.version.plat.rev]: [0]
[ro.cm.build.version.plat.sdk]: [7]
[ro.crdroid.display.version]: [crDroidAndroid-7.1.2-20170812-h815-v3.7]
[ro.crdroid.version]: [7.1.2]
[ro.modversion]: [crDroidAndroid-7.1.2-20170812-h815-v3.7]
[ro.opengles.version]: [196610]
[sys.cm_settings_secure_version]: [2]
[sys.cm_settings_system_version]: [4]
[G4 Android Development] kessaras:
yes time always works when we 'ave a stock based rom.

here :)
[G4 Android Development] crysknife4life:
[SIZE="1"]~ # getprop | grep -i build
[ro.bootimage.build.date.utc]: [1503563377]
[ro.bootimage.build.date]: [Thu Aug 24 08:29:37 UTC 2017]
[ro.bootimage.build.fingerprint]: [lge/omni_g4/g4:6.0.1/MOB31K/steadfasterX08240829:eng/test-keys]
[ro.build.characteristics]: [default]
[ro.build.date.utc]: [0]
[ro.build.date]: [Thu Aug 24 08:29:24 UTC 2017]
[ro.build.display.id]: [omni_g4-eng 6.0.1 MOB31K eng.steadfasterX.20170824.082659 test-keys]
[ro.build.flavor]: [omni_g4-eng]
[ro.build.host]: [droiddev]
[ro.build.id]: [MOB31K]
[ro.build.product]: [h815]
[ro.build.tags]: [test-keys]
[ro.build.type]: [eng]
[ro.build.user]: [steadfasterX]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.base_os]: []
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [eng.steadfasterX.20170824.082659]
[ro.build.version.preview_sdk]: []
[ro.build.version.release]: [6.0.1]
[ro.build.version.sdk]: [23]
[ro.build.version.security_patch]: [2016-11-05]
~ # getprop | grep -i version
[ro.build.version.all_codenames]: [REL]
[ro.build.version.base_os]: []
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [eng.steadfasterX.20170824.082659]
[ro.build.version.preview_sdk]: []
[ro.build.version.release]: [6.0.1]
[ro.build.version.sdk]: [23]
[ro.build.version.security_patch]: [2016-11-05]
[ro.modversion]: [OmniROM-6.0.1-20170824-g4-HOMEMADE]
[ro.omni.version]: [6.0.1-20170824-g4-HOMEMADE]
[ro.twrp.version]: [3.1.1-beta_sfx-6][/SIZE]
[G4 Android Development] TecknoFreak:
I wish twrp add the only feature missing for flashing images which is an option to flash the modem.img
[G4 Android Development] steadfasterX:
Iirc I have integrated that a while ago. you should be able to do this but you have to use the latest official or my latest beta.

Use the img button in TWRP choose the modem.img.

It should ask you after choosing the modem image where to install which is then the firmware partition.

If that's not the case let me know. I can't test it until I have my device back from LG..

.
[G4 Android Development] TecknoFreak:
Lol we are in the same boat my friend. I get mine tomorrow from T-Mobile