yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] tecknight:
When you flashed the ROM image, did it say anything about the /data partition being encrypted ?

Did it appear to flash successfully ?

Could you do the following, please ?

I'd like to see the kernel log from when it is booting up badly.

Try to boot normally to that weird blank screen.

Then pull the battery. Boot into TWRP and pull this file for me:

/sys/fs/pstore/console-ramoops

Upload or post it somewhere and I will see if I can diagnose the problem

y
[Miscellaneous Android Development] zamiel2112:
https://drive.google.com/open?id=12cw8BwzQriSVIeR4munovjG0GDrc9ymlLw

Sorry but I dont know how to pull a file. I am not a tech person by any stretch of the imagination. I got my first android last year and I became fascinated whereby I find it as my hobby today.I have successfully rooted 11 phones and every bit of the knowledge employed there was gleaned from here. Dogged determination. I just won't quit and I always seem to find a way if indeed there is a way.http://https://www.google.com/url?q=https://drive.google.com/folderview?id%3D1x8GMJHu0OBM0grjCwmRYqaGjc7chNYOg&sa=D&source=hangouts&ust=1543826623801000&usg=AFQjCNHidpvVb-E-aXw1fHXtkJQEw4XhFw So if you could keep it slanted on the noobish side I will be okay. The five pics were the best i could come up with at this time. I hope the they help. Oh yeah I attempted to flash a noverity zip I used to root my K20 Plus. It flashed fine but still won:t mount. This is proving as frustrating as rooting a 2017 J3 Prime I found ftp locked on a bench.
[Miscellaneous Android Development] tecknight:
OK, I'm going to make you a custom .zip file that will pull everything I need.

Do you have a MicroSD ?
[Miscellaneous Android Development] zamiel2112:
yes
[Miscellaneous Android Development] zamiel2112:
View attachment dmesg.log

Is this it? I had tried to go through TWRP/sys/fs/pstore .. and it would not go further than that
[Miscellaneous Android Development] zamiel2112:
View attachment dmesg.log

Is anyone available to help me with this tonight? I have this evening off work and have hit a wall since Friday.
[Miscellaneous Android Development] tecknight:
FYI: This file that you posted is from a TWRP boot.

I need you to try booting normally until you get to the blank screen.

then remove the battery.

Then boot to TWRP and run the .zip here:

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

When done, connect phone to PC, browse to SD Card, then folder called tec.

In this folder will be several files.

I only need the 1 file, upload.tar.gz. Upload it to google drive, then send me the link.
[Miscellaneous Android Development] zamiel2112:
I PM'd it you (fingers crossed).
[Miscellaneous Android Development] Pain Free IT:
I tried this on two different phones. Both X212TAL. One of them it fixed. Thanks very much! The other one was already updated to the latest OTA as of a few days ago, and apparently included the 10L kernel, because TWRP wouldn't respond to touch inputs, and the screen was shifted up.

On that second phone that needed the newer version of TWRP everything was running fine. I wanted both phones to be completely the same version though, so I flashed the 10j firmware for the Aristo 2 plus (TecsAristo2pv2.zip) to it the same as I had for the first phone, now the screen is shifted up by a centimeter on it for both the OS, and TWRP, and nothing is responding to touch input.

I can access the second phone via adb, and twrp from the command line.

What can I try to get it fixed?
[Miscellaneous Android Development] NonStickAtom785:
Try flashing my Rom. I built it from the X212TAL firmware. It is a custom ROM with a lot of stuff removed and added. Flash it from your recovery and let me know if it works.:fingers-crossed:

https://www.androidfilehost.com/?fid=11410963190603862968
[Miscellaneous Android Development] Pain Free IT:
Thank you for that, unfortunately it didn't fix it.
[Miscellaneous Android Development] Pain Free IT:
So after I flashed your ROM, I took a dump of both using LGUP, of all partitions except for userdata. I then flashed TecKnight's zip again on the bad phone, and took a dump using LGUP of the same partitions. I used Bitser to take an MD5 hash of all of the images, and compared them. Between the Good & Bad phones (both X212TAL) running TecKnight's zip these partitions are showing different sums:

BackupGPT_COM7

boot_COM7

cache_COM7

carrier_COM7

DDR_COM7

drm_COM7

ftm_COM7

modemst1_COM7

modemst2_COM7

mpt_COM7

OP_COM7

persist_COM7

persistent_COM7

PrimaryGPT_COM7

recovery_COM7

sns_COM7

srtc_COM7

ssd_COM7

system_COM7

I'm mostly a windows guy, but I bought UFS Explorer a while back for a project so I can read / write *nix partitions; I can check any of the files between the two devices as I had enabled adb / USB debugging before these problems on both handsets.

What files are worth comparing, or which partitions should I start with do you guys think?

As I understand it I should be able to flash the dump of any partition from the good phone to the bad one using:

fastboot flash boot boot_COM7

for instance?

---------- Post added at 05:59 AM ---------- Previous post was at 05:53 AM ----------

It looks like these four partitions should be the same on both phones, since your zip flashes them.

boot_COM7

persist_COM7

recovery_COM7

system_COM7

The 'COM7' phone is the good one. Do you think if I take these four partition images from the good phone, and flash them to the bad phone it will fix things, or break them worse? I don't mind playing around here to learn.
[Miscellaneous Android Development] Pain Free IT:
I extracted the partition dumps from LGUP using UFS Explorer Standard Access, and then compared them using Winmerge, and either Bitser (better for multiple files), or 7-zip's hash functions (right click 'CRC SHA' context menu in explorer is nice because it can ignore filenames, and provide one hash for multiple files, even in subfolders).

It turns out System was only different because the TWRP management app was installed on the working phone, and not the broken one.

The persist partition was different because the working phone a .twrps file in it, and these five files are different:

ats_1

ats_12

ats_13

ats_15

ats_2

Apparently they are related to the clock.

The Boot & Recovery partitions I am not able to read as they are apparently in the boot file system, and I don't know how to read them yet.

I flashed Boot, Recovery, and Persist dumps acquired with LGUP from the working phone to the broken phone using fastboot. Persist failed with "Fastboot not able to flash partitions with bootloader unlocked", the others succeeded, but there is no change in the phone; touch input still doesn't work, and the screen is shifted up for TWRP, fastboot, android, and download mode, also whatever the LGUP connection mode is called (it looks different than download mode).

Now the recovery shows the same md5 sum between the working, and broken phone, but still a different sum for boot.

Maybe that is my problem since the boot partition contains the kernel?

This is the output from "adb shell > cat /proc/version" though (on both phones)

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell

~ # [6nuname

Linux

~ # [6ncat /proc/version

Linux version 3.18.31-perf+ (lgmobile@LGEACI9R1) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Wed Oct 3 21:50:43 KST 2018

~ # [6n

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell

~ # [6ncat /proc/version

Linux version 3.18.31-perf+ (lgmobile@LGEACI9R1) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Wed Oct 3 21:50:43 KST 2018

~ # [6n
[Miscellaneous Android Development] NonStickAtom785:
Wow this is some interesting information. The kernels are exactly the same. But if your download mode is also shifted that's even crazier. It makes me wonder if there was an issue with the raw_resources.img in some of the phones. Have you tried downgrading it to Aristo 2 firmware or are you troubleshooting the 10L Firmware?

Also if the screen if shifting on everything and the md5 sums are different only for the boot.... That's crazy. I wonder if the there's a hidden partition that is blocking the unencypted boot.img and the device mapping is screwing the screen density.
[Miscellaneous Android Development] Pain Free IT:
The very first splash screen says:

"LG Life's Good

POWERED BY android"

it's in the right place

Then this message is shifted up:

"Your device software cannot be checked for corruption. Lock the bootloader."

When the "LG Life's Good..." splash screen comes back again, then it is shifted up too. Everything after this is shifted up as well.

The pink T-Mobile screen shows the bottom blank area as a grey scale gradiation, darkest in the center band, and lightest on the outside edges. I just noticed the blank area at the bottom of the screen seems to be the same dimensions as the box where the soft keys are...
[Miscellaneous Android Development] zamiel2112:
https://drive.google.com/open?id=13_-tQjVjIujTTt3gQbEGLyhyilUBmabn
[Miscellaneous Android Development] tecknight:
On the phone that doesn't work download and flash this to recovery:

TWRP with 10L kernel:

https://www.androidfilehost.com/?fid...63190603862817

You should then have a working TWRP. Try flashing a ROM from there
[Miscellaneous Android Development] Pain Free IT:
Thanks, I already did. That is what got it working initially after the OTA update.

Do you know of any way that I can extract the contents of the boot partition so I can compare them between the phones? I wasn't able to get both boot partitions to be exactly the same either through flashing your zip, or with fastboot.
[Miscellaneous Android Development] tecknight:
Yes, there are plenty of ways:

1. Use LGUP developer mode:

https://xdaforums.com/showpost.php?p=76995781&postcount=26

Select Dump then check boot partition.

2. If you can get to a root shell, type this command:

dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img

this will write the contents of the boot partition to a file named boot.img in the root of internal storage

or run this (chksys.zip) thru TWRP with a MicroSD installed:

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

It will leave a boot.img and recovery.img in the /external_sd/tec folder.

It also pulls a bunch of other useful info.
[Miscellaneous Android Development] zamiel2112:
Can someone help? I used dual lgup developer mode to flash the k20 plus to the aristo 2 by accident. Now the phone is totally unresponsive. What can be done?
[Miscellaneous Android Development] NonStickAtom785:
Ah jeez dude. Someone else did that and they got QDL9008... An undocumented Mode. You might need to take it in to the vendor to get it fixed because to reflash the original partitions you need the QDL9008 private key and the only people who have it are the device manufacturer and Qualcomm and Qualcomm dosen't like to give there stuff out.

Let me know if you get your stuff fixed.
[Miscellaneous Android Development] Pain Free IT:
Thank you, I have the boot.img saved with LGUP from both phones. I meant how do I compare the contents of that backup between the two phones; I can't find a way to actually look at the contents.
[Miscellaneous Android Development] Pain Free IT:
So I figured I'd try doing the OTA update from TWRP. On the good phone I downloaded it, and then pulled it from /data/ota_package.

On the busted phone I can:

adb shell

twrp install /external_sd/update.zip

It gave me this screen:

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell

~ # [6ntwrp install /external_sd/update.zip

Installing zip file '/external_sd/update.zip'

Checking for Digest file...

Skipping Digest check: no Digest file found

Source: lge/cv1_lao_com/cv1:7.1.2/N2G47H/1818420197aaf:user/release-keys

Target: lge/cv1_lao_com/cv1:7.1.2/N2G47H/182281407567a:user/release-keys

Verifying current system...

E3001: Package expects build fingerprint of lge/cv1_lao_com/cv1:7.1.2/N2G47H/1818420197aaf:user/release-keys or lge/cv1_lao_com/cv1:7.1.2/N2G47H/182281407567a:user/release-keys; this device has lge/omni_cv1/cv1:7.1.2/NJH47F/armand08021516:userdebug/test-keys.

Updater process ended with ERROR: 7

Error installing zip file '/external_sd/update.zip'

Done processing script file

~ # [6n
[Miscellaneous Android Development] NonStickAtom785:
Yah you can't update it with TWRP. I think I have a fix for it. I just need to change the user key in the build.prop folder. Or I can change the update script. Can you send me or upload the update.zip so I can take a look at it. I deleted the Update Center and stuff from my rom so it wouldn't install things as it wished. And so there wouldn't be any issues from TWRP.

---------- Post added at 02:04 PM ---------- Previous post was at 02:02 PM ----------

What are you using to compare files? Also what backups are you looking at? Are they TWRP backups or are they adb backups?
[Miscellaneous Android Development] Pain Free IT:
Here it is:

https://drive.google.com/open?id=17_XNnxw1zbnMomWBX8-3DfdsvIHe5zHM

I'm using the built in hash calculator from 7-zip.org:

https://www.7-zip.org/

It integrates a 'CRC SHA' option in the right click / context menu of Windows Explorer, also a program called Bitser:

https://www.bitser.org/

7-zip is nice because you can calculate a checksum for a folder, with all files in it, or a group of files just by right clicking them. It gives checksums for just the data, or also including the filenames.

Bitser is nice because it will give you a checksum for every file if you highlight a group of them.

The backups are dumps using LGUP.

I compare the directory structure by first extracting the LGUP dump using UFS Explorer Standard Access:

https://www.ufsexplorer.com/ufs-explorer-standard-access.php

(It doesn't understand the bootfs partitions for boot.img, or recovery.img though.)

Then I compare the extracted dumps using Winmerge:

http://winmerge.org/
[Miscellaneous Android Development] tecknight:
OK, the OTA update won't install because I used a trick to disable OTA updates, since an OTA update on a rooted image is not advisable. However, if you want to install an OTA update, browse to the /system/etc/security folder and rename the file otacerts-old.zip to otacerts.zip

---------- Post added at 10:35 PM ---------- Previous post was at 10:27 PM ----------

Not sure if you already knew this, but 7zip has another even more awesome ability.

It can open an ext4 filesystem image directly as an ARCHIVE.

Just right click on the raw image (like a userdata or system or cache image) and select open archive. You don't need UFS explorer.

How's that for a FREE utility !!
[Miscellaneous Android Development] Pain Free IT:
Nice.

---------- Post added at 09:26 PM ---------- Previous post was at 08:53 PM ----------

The only folder I can see under /system is 'bin'. I think the shell is running as root (# symbol in the prompt):

~ # [6ncd system

/system # [6nls

bin

/system # [6n

This is using 'adb shell', the prompt is always '# [6n'

These are the only zip files I can see using find:

~ # [6nfind . -name[J "*.zip[J"

./external_sd/Magisk-v17.1.zip

./external_sd/no-verity-opt-encrypt-6.0.zip

./external_sd/download/TecsAristo2pv2.zip

./external_sd/AR.Update.v2.zip

./external_sd/update.zip

find: ./sys/kernel/slab/L2TP/IPv6: No such file or directory

find: ./sys/kernel/slab/L2TP/IP: No such file or directory

./data/local/bootanimation.zip

./data/local/shutdownanimation.zip

./data/data/com.google.android.gms/cache/downloadservice/ocr_armeabi_v7a.zip

~ # [6nfind . -name "ota"

find: ./sys/kernel/slab/L2TP/IPv6: No such file or directory

find: ./sys/kernel/slab/L2TP/IP: No such file or directory

/edit I had to run 'twrp mount system' from 'adb shell' to mount the system partition.

I have otacerts.zip already in there:

/system/etc/security # [6nls

cacerts mac_permissions.xml otacerts.zip
[Miscellaneous Android Development] Pain Free IT:
How do I check the device mapping, and screen density?
[Miscellaneous Android Development] NonStickAtom785:
Idk. I left all of that stuff to Tec. We're using a 10K based version of the ROM because the 10L is becoming a well known problem.
[Miscellaneous Android Development] tecknight:
Oreo Rooted ROM

OK, here's the Oreo rooted ROM V2.

It actually installs v20c firmware with a Magisk patched boot image, leaving the recovery partition alone (for TWRP)

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

Flash with TWRP.

Prerequisite: Target must be a cv1 device (Aristo 2, Aristo 2 plus, K8) and have TWRP installed.

I would appreciate any feedback on this image.

FYI: There is one issue with the Oreo boot image that I am still trying to figure out a solution for.

They changed the way they enforce force encryption.

The solution that ensured a non-encrypted /data partition with Nougat does not work with Oreo.

As a result, installing Oreo (at present) forces /data to be encrypted.

This is true if you install using LGUP or TWRP.

It's not a huge deal, the biggest downside is that you can't backup your /data partition with TWRP.

One other thing.

Despite having OEM and flashing unlocked, I am not able to flash an image to recovery using fastboot. This may be true for boot as well.

If so, then the only way to root Oreo would be to install a rooted ROM such as this.

For this reason, I would avoid using LGUP or OTA to upgrade to Oreo if you want to root your phone.

If someone has upgraded to Oreo and is not rooted, please let us know if you are able to flash partitions via fastboot.

---------- Post added at 06:26 AM ---------- Previous post was at 06:18 AM ----------

This is my latest disrec.zip

It now breaks apart the following bootable images in order to determine the kernel and ramdisk used:

boot

recovery

laf

Hopefully this will help us to determine what the actual cause of this issue is

https://www.androidfilehost.com/?fid=11410963190603881996
[Miscellaneous Android Development] Pain Free IT:
Thank you for that. I went ahead, and flashed the zip for "Aristo 2 plus (Oreo firmware 20c, T-Mobile)" from here:

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

I already had the recommended version of TWRP installed, and ran the 'fastboot flashing unlock' command (it was already unlocked).

It installed fine, but is stuck on the LG boot screen on startup now.

It fixed the screen being shifted issue, so I can use TWRP manually from the phone now.

I don't mind troubleshooting it, what do you recommend at this point?
[Miscellaneous Android Development] tecknight:
So it just displays the LG Boot screen, then freezes ?

or does it continually reboot ?

Does it display the Yellow triangle screen before the LG boot screen ?

Does it display the custom animation at all ?

You say

How did you use TWRP before this or to flash the .zip itself ?
[Miscellaneous Android Development] Pain Free IT:
It shows

LG boot screen very briefly, then

"Your device software cannot be checked for corruption.

Lock the bootloader.

Press the Power key to pause boot

Your device will boot up automatically after a while."

Then back to the LG boot screen, no custom animation, unfortunately.

I used twrp from the command line via 'adb shell', before:

https://twrp.me/faq/openrecoveryscript.html
[Miscellaneous Android Development] tecknight:
Sounds like we could be close.

So you sideloaded the ROM image and now TWRP loads normally and the touchscreen is working ?

Try this image:

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

It flashes OP as well.

This is the phone that has been down for several weeks ?
[Miscellaneous Android Development] Pain Free IT:
I used 'twrp install ***.zip' from adb shell. Sideload was working too though from the command line.

It fixed the screen completely; TWRP wasn't displaying at all on the phone before that, and the boot animation, and recovery selection screen were shifted up about ~1 cm.

After loading the ROM from that link it does have different boot animation. It says 'LG K8', and then has a rolling 'LG' icon that stops in place. It stays stuck on that screen, however.

---------- Post added at 04:07 AM ---------- Previous post was at 03:41 AM ----------

So I tried flashing this again, after flashing 'TecsA2rootedOreoROMV5.zip' (above). It loaded into android setup. The boot animation was colored dots shivering around what looks like a clock.

When it gets into android setup the touch screen doesn't work, and when I lock / unlock it with the power button (no pin, or anything) the screen shifts up by ~1 cm, again.

I did get this error when flashing it:

mount: failed to mount /dev/block/mmcblk0p60 at /

OP: Invalid argument

mmcblk0p60 is the OP partition (not sure what it is for, I only saw 'boot', and 'system' partitions in the image).

I flashed it back to 'TecsA2rootedOreoROMV5.zip', and it is stuck on the boot screen again.

TWRP (10L kernel) is still working fine.
[Miscellaneous Android Development] tecknight:
OK, stay tuned. I am posting a special .zip for you to run

OK, here it is.

Run this:

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

then upload the .tar.gz file that is in

/external_sd/dr

Also post what it displays
[Miscellaneous Android Development] tecknight:
I have one more file that has a decent chance of fixing your phone:

TWRP for cv1 devices with corrected fstab and OREO Kernel:

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

I am running it now.

Flash it from TWRP (Install->Image) or from adb shell in TWRP

dd if=/path/to/twrp.img of=/dev/block/bootdevice/by-name/recovery
[Miscellaneous Android Development] Pain Free IT:
Here is what came over adb shell:

~ # [6ntwrp install /external_sd/disrec.zip

Installing zip file '/external_sd/disrec.zip'

Checking for Digest file...

Skipping Digest check: no Digest file found

Details about currently loaded BOOT image:

Build date: Thu Nov 22 18:55:26 KST 2018

Build fingerprint: lge/cv1_lao_com/cv1:8.1.0/OPM1.171019.026/1832618554af2:user/release-keys

Kernel size: 11480828

Details about currently loaded RECOVERY image:

Build date: Thu Aug 2 15:16:57 EDT 2018

Build fingerprint: lge/omni_cv1/cv1:7.1.2/NJH47F/armand08021516:userdebug/test-keys

Kernel size: 11239528

Details about currently loaded LAF image:

Build date: Thu Aug 2 15:16:57 EDT 2018

Build fingerprint: lge/omni_cv1/cv1:7.1.2/NJH47F/armand08021516:userdebug/test-keys

Kernel size: 11239528

/////////////////////////////////////

// Script complete //

// //

/////////////////////////////////////

script succeeded: result was [ ]Done processing script file
[Miscellaneous Android Development] Pain Free IT:
At this point TWRP is working on both phones, and is the 10L kernel. It hasn't given me any issues.
[Miscellaneous Android Development] tecknight:
But your phone is not booting into Android.

If you have the same OREO kernel for recovery and boot, maybe it will.

I am pretty certain the screen offset, TWRP locking issue is related to having multiple (different) kernel images on the same device, because every device I have seen having the problem has conflicting kernel images.

As does yours:

Details about currently loaded BOOT image:

Build date: Thu Nov 22 18:55:26 KST 2018

Build fingerprint: lge/cv1_lao_com/cv1:8.1.0/OPM1.171019.026/1832618554af2:user/release-keys

Kernel size: 11480828 <--Oreo kernel

Details about currently loaded RECOVERY image:

Build date: Thu Aug 2 15:16:57 EDT 2018

Build fingerprint: lge/omni_cv1/cv1:7.1.2/NJH47F/armand08021516:userdebug/test-keys

Kernel size: 11239528<--10L Kernel

Details about currently loaded LAF image:

Build date: Thu Aug 2 15:16:57 EDT 2018

Build fingerprint: lge/omni_cv1/cv1:7.1.2/NJH47F/armand08021516:userdebug/test-keys

Kernel size: 11239528 <--10L Kernel
[Miscellaneous Android Development] NonStickAtom785:
This is the TWRP with updated Kernel? I'm gonna flash it and get back to you if there is any issues.
[Miscellaneous Android Development] tecknight:
Yes, I am already using it.

It works great.

I also fixed some issues with the fstab that could cause issues with encrypted partitions

I think it will make for a more stable system.

With this TWRP and Oreo firmware you are only running 1 kernel on your device