yashsingh1/xdaforums huggingface dataset:
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] gazzacbr:
Hi, with the version to include int sd folders, is it possible to specify which actual folders are excluded? Maybe an ini/dat option file?

Hmm, androidfilehost, mega and google everything blocked here in China, I guess the Chinese have their own forums/sources
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
unfortunately not :( it's hardcoded in sources.

you need another host to be able to download? just name one, i'll upload it there for you :)
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] QuitChiefin:
I apologize if this has already been answered or there is a noob fix, but for some of the top current ROMs you must flash the kernel separate but the .img files for the kernel are not showing in twrp to flash. I've tried from internal and sdcard but the .IMG won't show up in either. Is there something I'm missing?
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] mukeshp7867:
In TWRP, you have to select Install image option while flashing Kernels. Normally by default it looks for zip. Here i am assuming you have not done that.

Look at bottom of the TWRP screen -- there are two options ... Select Storage and Install Image.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] minhntp:
Cannot mount /vendor

Hi. I flashed this TWRP and successfully flashed Magisk. But I can't mount /vendor partition as I can't tick on it.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
then you don't have one, which is default for v30 :) or did you run the script which is necessary for creating a vendor partition?
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] minhntp:
I flashed the GPU driver update for snapdragon 835 but it didn't change anything. I think it's because TWRP cannot mount vendor partition. It worked before but now I don't know why it doesn't. I'm on US998 20e.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
nah, that's not because of vendor. how did you check if it was flashed correctly? driver version checked before and after flashing?
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] minhntp:
Yes. The driver doesn't change after flashing. When I flashed the driver zip file, it only showed: "Skipping Digest check: no Digest file found"
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] QuitChiefin:
That was it. Idk how I overlooked that. I've even installed newer versions of twrp before and STILL overlooked this. Thanks so much!!
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] rikita:
Time/Date is now incorrect. I have reflashed .img several times. Any ideas as to a fix? Causing problems with my nandroid backup scheme.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
in twrp, mount /persist and delete following folders:

/persist/time

/data/vendor/time

reboot to android, then reboot to recovery, time should be correct again :good:
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] rikita:
Mounted /persist.

/persist/data folder empty.

deleted /persist/time.

Fixed the problem!!!!

Many thanks!
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] rikita:
Issues with Nandroid file modification time

Still having an issue with date time.

Time and time zone (CST) are correct in TWRP. When I do a nandroid backup, TWRP appends the correct date and time to the name of the directory. However, the modification time appended to the actual backup files is GMT (6 hours fast for us on CST). It uses GMT as the modification time no matter what I set the time zone to.

Any ideas?
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
realized that too already, but it's no real problem: it's the folders title what counts. since it wasn't a real problem i didn't look further into this anymore: for me it's cosmetic, as long as folders are titled correctly. :good:
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] rikita:
Not a super issue for sure.

I use Tasker to run an automated nandroid backup. Upon reboot, Resilio app automatically syncs the /TWRP/BACKUPS folder to a LAN server. After the sync, the Resilio install on the server gives an error toast until the modification date/time on each file is no longer "in the future." (I use Resilio because it is so damn fast. The sync (appx 13gb) usually takes about 5 minutes.) In any event, the error toasts seem to be no more than cosmetic annoyances. The functionality of the idea is sound, I was just trying to get rid of the error toasts.

Thanks again for the reply and more importantly, all of your development efforts.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] shamsul007:
im going to assume that restoring a backup that was made with an earlier version of twrp will cause problems?

im switching to a non-stock rom, so first i updated twrp with the default image, and created a backup of my current ROM. that way if i have any issues I can downgrade to my stock rom, correct?
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
yes, that's a good way, correct. but nope, there are no issues, backups are compatible. it's only every file with "firmware" in its name inside the older backup folder which you want to restore should be either deleted or not restored. i wrote something about that in one of the first posts, anyway: this basically is the main info :)
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
hmm, looks like there's a bug in twrp with restoring boot.img, sometimes. can't figure out what's causing it, but sometimes restoring a backup results in booting into fastboot mode for me. then separate boot.img flashing, either via fastboot or via twrp image flash, is needed to get the phone up and running again. solution for now: better do an additional diskdump backup of your working boot partition, which you can flash in case. i'll add this info to one of the openers soon.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] TheDannemand:
Good catch! For rooted H932 owners this could be extra tricky as they don't have fastboot flash commands on which to fall back. If TWRP cannot flash a boot partition (or any partition) they are dead in the water.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
flashing is no problem, from within twrp. the fastboot situation is sh¡tty for some models, jep, but if a dump of boot is done right after a backup was created, every models owner should be on the sure side.

command for that, just in case, executed in twrp's terminal or via a adb shell:

(adb shell) dd if=/dev/block/bootdevice/by-name/boot of=/external_sd/boot.img

(replace external_sd with sdcard if no additional sdcard is inserted).

this img is flashable with twrp and can save your seat meat :)

just thinking about releasing a new version which has a script for that included; and the vendorizing script from [MENTION=3475147]SGCMarkus[/MENTION] too. omg, we would be on version .8 then, i need to reset the versioning somehow xD
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] TheDannemand:
I see. I understood from your post that the bug was in flashing (restoring) a backed up boot.img, which would mean a H932 would have no way to restore it as they don't have fastboot flash. Good idea to include a script for those tasks.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] byran7:
Hello. I bought a phone LG V35 on ebay and the bootloader is unlocked in it. I want to put TWRP on the phone. I have a desire to put TWRP on this phone. Where can I download this TWRP and does it exist at all? Perhaps someone also wants to install custom firmware.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] ChazzMatt:
TWRP doesn't exist for V35 (JudyP) because bootloader has never been unlocked, to anyone's knowledge.

2018 LG V35 (JudyP) is drastically different from LG V30 (Joan) internally. 2018 LG V35 (JudyP) is basically a 2018 LG G7 (JudyN) that looks like a V30 (Joan). ;) V35 has P-OLED display with no notch; G7 has a notch -- thus the P and the N. The LG code names tell the story.

_____

You are sure the bootloader is unlocked on your LG V35?

If the bootloader is unlocked, you are sure you have a LG V35?

I'm very skeptical. You have any proof? Screenshots of firmware you are running, the About Phone screen, the bootloader unlock warning?

I hate to ask this but I don't know how much you know about phones. I do not mean any disrespect. Are you confusing "unlocked" (SIM card unlock/carrier unlocked) with BOOTLOADER unlock?

This

previous report of a V35 bootloader unlock

was deemed a fake, as no one on XDA was able to replicate it.

And yeah, there's tons of click bait websites offering you idiotic instructions on how to bootloader unlock any phone model in the world -- even V35 -- but they are simply copy and paste crap from older LG/Nexus/Pixel phones. For instance,

here's one click bait website instructions for bootloader unlocking our LG V30.

:rolleyes: I wish it was that simple! Here's the

REAL thing

(on XDA). Unless you have T-mobile H932 V30, then instead

you have to do this.

There's also a Japanese

LG V30+ which the Japanese carrier calls "LGV35"

-- just as this carrier's LG V20 was called "LGV34". Sort of an internal model name. :rolleyes: It has Wi-Max and LTE bands. But then it gets confusing when LG decides to release an actual LG V35. Is it possible you actually have this Japanese V30+ phone, which the Japanese carrier marketed as "V 35"?
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] Redline:
I couldn't see any other reports of this in the thread, but it seems there's somewhat of an issue with TWRP (both this version and the version attached to CazzMatt's root guide) regarding (at the least) OpenGAPPS's AROMA installer.

Starting the installer and everything is fine, but once you try to actually start installation of it, the screen goes black (almost as if TWRP is re-loading) and then you're back on the main TWRP menu screen.

From there, you can't reboot (it just does the same thing no matter what option you choose) or do almost anything else.

Doing a reboot via ADB on a PC allows you to reboot the device back into recovery or system or whatever just fine, but something about AROMA breaks TWRP completely until you restart into it remotely.

I tested using the latest version from the OP of this thread, as well as the version attached to the above mentioned guide, and got the same behaviour. I tried wiping every partition, going through the "installing TWRP" part of the guide multiple times to make sure I wasn't crazy, and everything else I could think of.

I looked through the TWRP log and couldn't see anything noteworthy, although I'm happy to do it again, reproduce the oddity and post a log if you think that'd help.

I should note that I ended up going with a regular GAPPS package instead of AROMA, and that installed perfectly fine.

I'm fresh onto the V30 scene, but I've got experience with ROMs, Kernels and Recoveries (the latter would be the least I have experience with, kernels being the most) from my V20 days not too long ago, so I'm familiar with most things in a sense.

Like I said, I couldn't see anyone else reporting it, so just thought I'd share it. Hopefully it's easily re-producable so we can lock down a fix, not being tied to specific offerings of certain GAPPS packages would be nice.

Otherwise the recovery works well for most everything I've tested so far, so much thanks for bringing that to us!
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
the aroma problem is known, or at least i was told about this misbehaviour already. i always thought that it's aroma itself, which is outdated and not being worked on anymore, but: does the same procedure work flawlessly on other devices? i wouldn't really know where to start debugging this, and beside that i never liked aroma xD but if some more reports arise, then it may be that i invest some time into this :)
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] Redline:
About all I know is that is worked flawlessly on my V20 I had previously, sorry.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] Krekos/CZ/:
This problem is commonly known. It happend to me when I was using Nexus 5 and also i encoutered same problem with my V30. It's bug in Aroma installer. When it happends to me I try it couple more times and usually at 3th or 4th try, it run successfuly. Also sometimes worked for me that I mount/unmount system partition few times.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] rotanid:
Thank you for your work on this!

How's the progress regarding Pie decryption support? The Oreo-based ROMs seem to be outdated, so i currently have the choice between encryption/decryption or security-updates, which is a hard choice :(
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
for hw based encryption, on first place there's pie fw from lg needed :( sw / file based encryption should work, i can try adding it :good:
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
here's a test image for pie filebased encryption (roms need to support this):

https://www.androidfilehost.com/?fid=1395089523397911762

you can try booting this via "fastboot boot <recovery-filename>.img" after a successful encryption of a pie aosp based rom. maybe this recovery is able to decrypt pie fb encrypted devices :good: (need to test this myself, but phone isn't fully charged xD need to charge first and leaving this image here for public testing).

steps to test pie aosp encryption:

encrypt your device via your roms security settings

boot to fastboot mode / bootloader

load the test recovery with "fastboot boot TWRP-3.2.3-8-fbe_test.img", (it will temporarely boot only, it's not installed on your phone)

then try if your userdata partition is decryptable and if internal sdcard is accessible via mtp

good luck :) i will test this too, need only some time to charge my device first.

edit:

not able to switch on encryption in pie versions of

dirty unicorns

lineageOS
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] rotanid:
ah, thanks for this information.

thanks! the currently available ROMs do only support FBE because they would also need LG's firmware for FDE/HWE, so it doesn't matter which ROM to take?

it looks like i was a bit petted with my previous G3/d855 where official TWRP and official LineageOS are available and support everything (except VoLTE) :D
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] Blezi:
Currently using the lastest version with official rom but every time i trying to update the room . it's restart into twrp and when i restart using twrp the update is still there and nothing change.Can some one help me with this.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
are you trying to update via rom's ota update function? this won't work, you need stock unmodified system and recovery for that.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] ChazzMatt:
If you have TWRP, flash the latest TWRP flashable zip version of the KDZ.

Otherwise you have to flash KDZ with LGUP in DL PARTITION mode and UNcheck recovery partitions to keep TWRP.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] Black Manta:
Tested it with encrypted Pixel Experience. Doesn't work.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
so pex has working encryption. :) thx :good:
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] rorsche:
Only the non-EAS version.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] christopherrrg:
Excited for 3.3.0 ?
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
a quick test compiles with fresh synced omni full pie sources = 3.3.0 result: no adb and mtp (mounting usb manually works) and no decryption support. time is off too, and maybe some other stuff to fix. i'll be on this every now and then, and cannot say when it will be available :) but latest some short time after when pie for v30 is officially released by lge :good::cyclops:
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] ChazzMatt:
So, end of June, eh? ;)

Just requesting version for WTF instructions, like before. Thank you for your work!

Sent via open market LG US998 V30/V30+
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] TotallyAnxious:
There appears to be a bicycle stuck in your tree. Perhaps that's related?
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
you won't believe it, but it really is (indirectly) related and connected, but not in a way i like it hehe: i'm a bicycle mechanics, it's terrible atm, there was never such a high volume as it is this year. so much, i even don't have time to ride my own bike because i need to repair so much bikes from other ppls, beside the sellings -.- but, i need to switch profile pic, there were two or three new bikes in the meantime LoL

anyhow, i'm on twrp, will fix the small stuff like adb and mtp in the meantime until pie arrives and then let's see :) some stuff from 3.3 recovery is dependant on pie firmware, which we don't have and therefore some stuff like hw based decryption isn't working. one or two public test builds promised ;)
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
3.3.0-0 test release

found some time to do a first 3.3.0-0 test recovery, features as follows:

- TWRP app excluded

- full pie sources used, 9.0 branches everywhere, works for oreo and pie roms

- not working: decryption fully broken, adb (works partially only, shows device as offline)

- working: mtp, time, all the default functions like backup / restore / wipe etc pp

- worth a try: pie and maybe even oreo aosp roms with file based encryption enabled: maybe userdata is already decryptable with this twrp version, i've added some fbe stuff but didn't test it ;) stock rom isn't decryptable => tested, therefore decryption generally stated as broken

find it here:

https://androidfilehost.com/?fid=1395089523397947141

it's the full default twrp recovery without added backing up of /data/media or dataimage functions, leaving out lockscreen settings etc, all this isn't in here. you can use it for everything beside adb sideloading and reading encrypted userdata partitions or sdcards. have fun flashing and testing; pls report all the bugs ;) :good:
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
vendor enabled recovery updated in first post! :good:
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] Alibaba0101:
put a copy of the img on your device or sdcard and note where you put it

use boot to recovery / magisk / su terminal / special buttons during boot to get into twrp recovery

select flash IMG to RECOVERY partition (find the file wherever you put it)

Click back a few times

reboot to recovery and make sure everything looks good

change timezone in settings

make new backup to sdcard using newer version of twrp

reboot to system

---------- Post added at 09:22 PM ---------- Previous post was at 09:18 PM ----------

At the risk of a duplicate post...

Getting an error that twrp can't mount /ENCRYPT and /OP during full backup. Is this normal?
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] BADA 187:
thanks for the update!

im just having a weird error at everything i do. (backup,restore, wipe, etc etc)

it seems its not affecting anything. (i switched roms, created&restored backups without any issues)

i attached a screenshot so you can see. (error 150)

EDIT: im using the one without the kdz stuff.

im using the first one you posted on SGCMarkus's thread

so not sure if i should flash the one with the kdz stuff added to it since i have no idea what it does and probably not going to use it..
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] BROKEN1981:
Not normal. I'm getting that error as well. I guess there needs to be a few kinks worked out.

Never saw that on my v20.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] Emu:
Flashed in TWRP. Super easy.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] Emu:
Btw yes I am getting the same error. But those are the new partitions that OP has made visible to TWRP. I tried to mount /OP and /encrypt and they cannot be mounted. /OP is overprovisioning is my guess. Both are supposed to be hidden and not possible to be mounted. But what filesystem do /OP and /encrypt even use? If /OP is really overprovisioning it's not gonna be a filesystem that anyone knows other than LG and Toshiba who supply the flash storage same for /encrypt. Even if we knew how to mount and backup, would it even be possible to restore those partitions? I say, OP should exclude them from the backup and restore process in TWRP.

The reason you don't see those error messages in other TWRP versions is because they don't even include those partitions in their backup. All of your other partitions will be backed up. If OP can and knows how to, he can just exclude those partitions from the backup process for now or find a way to mount them and include them which would be incredible and the FBI might be interested in your work as well. :D
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
always install latest version for double check an error :) you can wait a little bit, i'll update the version in some hours :good:
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] truc113:
Hi [MENTION=3138121]seadersn[/MENTION], thanks for your work! vielen danke!

I'm trying to build it on my own so that I can tweak some things (kernel stuff) but I'm pretty new to android dev (not to dev in general though as it's my job),

so far I've followed instructions from https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni

did repo init with twrp-8.1 branch, added the repos you listed in OP in .repo/local_manifest/roomservice.xml (except minimal manifest),

this is the file I'm using

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="seader/android_device_lge_joan-twrp" path="device/lge/joan-twrp" remote="github" revision="android-8.1" />
<project name="Phoenix591/lg-v20-tools" path="lg-v20-tools" remote="github" revision="kdzwriter" />
<project name="SGCMarkus/android_kernel_lge_msm8998" path="kernel/lge/msm8998" remote="github" revision="lineage-15.1" />
</manifest>

repo sync went ok, . build/envsetup.sh also.

lunch omni_joan-eng (instructions from minimal manifest) gives this

build/core/envsetup.mk:223: *** No config file found for TARGET_DEVICE joan. Stop.
Your device can't be found in device sources..
Traceback (most recent call last):
File "vendor/omni/build/tools/roomservice.py", line 355, in <module>
fetch_device(device)
File "vendor/omni/build/tools/roomservice.py", line 323, in fetch_device
git_data = search_gerrit_for_device(device)
File "vendor/omni/build/tools/roomservice.py", line 81, in search_gerrit_for_device
device_data = check_repo_exists(git_data, device)
File "vendor/omni/build/tools/roomservice.py", line 58, in check_repo_exists
"exiting roomservice".format(device=device))
Exception: joan not found,exiting roomservice
build/core/envsetup.mk:223: *** No config file found for TARGET_DEVICE joan. Stop.

** Don't have a product spec for: 'omni_joan'
** Do you have the right repo manifest?

what am I missing?

cheers everyone!
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
:D always these sync and repo problems -.-

first: directory for kdzwriter is 'external/kdzwriter'

second: rename device directory to 'joan' instead of 'joan-twrp' :)

i'll update the github readme, and maybe upload a local_manifest too :good:
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
done, have a look here.

btw, op partition is mountable and backupable now. it is the equivalent to cust partition on other phones and contains preinstallable stuff, app overlays and carrier configs.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] gazzacbr:
Hi, great work, date/time all good now :D