FORUMS
Remove All Ads from XDA

Tecknight's Aristo 2 Tutorials

845 posts
Thanks Meter: 690
 
By tecknight, Recognized Contributor on 17th June 2018, 04:35 AM
Post Reply Email Thread
19th November 2018, 01:16 PM |#121  
NonStickAtom785's Avatar
Senior Member
Flag Warrenton, Mo
Thanks Meter: 35
 
More
Quote:
Originally Posted by cody85

Apologies for the delay...

Disregard the incorrect filename for patched boot image, I just pasted the wrong file name in my post as I had it named "boot.img" on my computer but wanted to avoid any confusion or whatever so I meant to paste the full name in my original post...

so I've been working all weekend just fine on my regular aristo 2 (not the plus) using 10L firmware according to settings -> software info.

I've just had a chance to sit down and retry everything.

100% charge
I factory reset in settings.
I enabled dev options.
oem unlock shows off, but it's not grayed out, so I can turn it on but I'm gonna save that till after I run the getvar all you mentioned.
I enable usb debugging, turn off auto updates, change charging to MTP.
I disable verify apps installed over adb.
I allow install from unknown sources.
I install official LG mobile driver.
I install ADB/Fastboot.
I reboot phone and computer.
I connect phone via usb.
run adb devices, select option on phone to allow it, then it shows authorized.
run adb reboot bootloader. phone reboots to bootloader with red text saying to enable oem unlock in settings.
I run fastboot getvar all which I've attached.
I run fastboot reboot.
I enable oem unlock in android developer options.
I verify MTP is set.
I adb-devices, authorized.
I adb reboot bootloader.
bootloader comes up on phone as expected w/o red text.
I run fastboot devices, shosws s/n and fastboot.
run fastboot flashing unlock, success.
run fastboot erase userdata, success.
run fastboot erase cache, success.
run fastboot flash boot 10L_M173_EVD.img, success.
run fastboot flash recovery recovery.img, success.
run fastboot reboot...
It reboots to the initial boot screen saying cant be checked, hit power to pause boot....
It then shows LG screen, but it never changes the bottom of the screen to show "qualcomm ...", it just reboots, and reboots, and reboots forever.

I then pwr and vol down to reset and it boot into TWRP where it shows a 0KB size for my /data partition and won't allow me to mount it.
I'm stuck with this situation every time I've done it, though it used to work without any issues at all until 10L cam

I got the same error but I fixed it by formatting the data file system to ext4 then back to fs2f.
 
 
19th November 2018, 01:58 PM |#122  
Junior Member
Flag Tulsa
Thanks Meter: 0
 
More
Quote:
Originally Posted by NonStickAtom785

I got the same error but I fixed it by formatting the data file system to ext4 then back to fs2f.

I don't seem to have as you, my friend. At what point did you format /data to ext4 and back?

I'm in TWRP, I see f2fs for /data with 0 size.
I then change file system type to EXT4 which changes the partition size to 9xxx MB.
I then select format data and type yes and its successful and size is still 9xxxx MB.

But once I change it back to f2fs and reboot recovery or reboot system, it shows me a size 0 again after rebooted.

I may try the original method that required formatting data and all that to see if it works.
19th November 2018, 02:42 PM |#123  
NonStickAtom785's Avatar
Senior Member
Flag Warrenton, Mo
Thanks Meter: 35
 
More
Quote:
Originally Posted by cody85

I don't seem to have as you, my friend. At what point did you format /data to ext4 and back?

I'm in TWRP, I see f2fs for /data with 0 size.
I then change file system type to EXT4 which changes the partition size to 9xxx MB.
I then select format data and type yes and its successful and size is still 9xxxx MB.

But once I change it back to f2fs and reboot recovery or reboot system, it shows me a size 0 again after rebooted.

I may try the original method that required formatting data and all that to see if it works.

I'll get back to you. I was just going off memory, sorry about that. I'm pretty sure it's supposed to f2fs. Did you flash no-dm-verity to remove device mapping? And did you flash tecknights root boot img. Because I ended up having to erase the internal storage and format data and then finnaly reflash system image and boot.img.
19th November 2018, 10:35 PM |#124  
tecknight's Avatar
OP Recognized Contributor
Flag Las Vegas
Thanks Meter: 690
 
More
Quote:
Originally Posted by cody85

I don't seem to have as you, my friend. At what point did you format /data to ext4 and back?

I'm in TWRP, I see f2fs for /data with 0 size.
I then change file system type to EXT4 which changes the partition size to 9xxx MB.
I then select format data and type yes and its successful and size is still 9xxxx MB.

But once I change it back to f2fs and reboot recovery or reboot system, it shows me a size 0 again after rebooted.

I may try the original method that required formatting data and all that to see if it works.

FYI: If your userdata partition is f2fs, then it has been encrypted by the forceencrypt property in the stock fstab.
That is why my rooting procedure includes patched boot images with the fstab modified and has specific steps to make sure userdata remains unencrypted.
19th November 2018, 10:37 PM |#125  
tecknight's Avatar
OP Recognized Contributor
Flag Las Vegas
Thanks Meter: 690
 
More
Quote:
Originally Posted by NonStickAtom785

I'll get back to you. I was just going off memory, sorry about that. I'm pretty sure it's supposed to f2fs. Did you flash no-dm-verity to remove device mapping? And did you flash tecknights root boot img. Because I ended up having to erase the internal storage and format data and then finnaly reflash system image and boot.img.

I will PM you on how you can make your zip automatically zero out the encryption key and format the userdata and cache partitions.
19th November 2018, 10:48 PM |#126  
tecknight's Avatar
OP Recognized Contributor
Flag Las Vegas
Thanks Meter: 690
 
More
Quote:
Originally Posted by cody85

Apologies for the delay...

Disregard the incorrect filename for patched boot image, I just pasted the wrong file name in my post as I had it named "boot.img" on my computer but wanted to avoid any confusion or whatever so I meant to paste the full name in my original post...

so I've been working all weekend just fine on my regular aristo 2 (not the plus) using 10L firmware according to settings -> software info.

I've just had a chance to sit down and retry everything.

100% charge
I factory reset in settings.
I enabled dev options.
oem unlock shows off, but it's not grayed out, so I can turn it on but I'm gonna save that till after I run the getvar all you mentioned.
I enable usb debugging, turn off auto updates, change charging to MTP.
I disable verify apps installed over adb.
I allow install from unknown sources.
I install official LG mobile driver.
I install ADB/Fastboot.
I reboot phone and computer.
I connect phone via usb.
run adb devices, select option on phone to allow it, then it shows authorized.
run adb reboot bootloader. phone reboots to bootloader with red text saying to enable oem unlock in settings.
I run fastboot getvar all which I've attached.
I run fastboot reboot.
I enable oem unlock in android developer options.
I verify MTP is set.
I adb-devices, authorized.
I adb reboot bootloader.
bootloader comes up on phone as expected w/o red text.
I run fastboot devices, shosws s/n and fastboot.
run fastboot flashing unlock, success.
run fastboot erase userdata, success.
run fastboot erase cache, success.
run fastboot flash boot 10L_M173_EVD.img, success.
run fastboot flash recovery recovery.img, success.
run fastboot reboot...
It reboots to the initial boot screen saying cant be checked, hit power to pause boot....
It then shows LG screen, but it never changes the bottom of the screen to show "qualcomm ...", it just reboots, and reboots, and reboots forever.

I then pwr and vol down to reset and it boot into TWRP where it shows a 0KB size for my /data partition and won't allow me to mount it.
I'm stuck with this situation every time I've done it, though it used to work without any issues at all until 10L cam

Yes, LG changed the boot significantly for 10L.
My phone won't root with 10L at all, even with the 10L patched boot.
Some people have gotten 10L to work with the 10L patched boot, but I am not one of them.
So, I am staying on 10K. I modified the rooting procedure, adding recommendations should you encounter a boot loop on firmware 10L.
The Following User Says Thank You to tecknight For This Useful Post: [ View ] Gift tecknight Ad-Free
19th November 2018, 11:01 PM |#127  
Junior Member
Flag Tulsa
Thanks Meter: 0
 
More
Quote:
Originally Posted by tecknight

Yes, LG changed the boot significantly for 10L.
My phone won't root with 10L at all, even with the 10L patched boot.
Some people have gotten 10L to work with the 10L patched boot, but I am not one of them.
So, I am staying on 10K. I modified the rooting procedure, adding recommendations should you encounter a boot loop on firmware 10L.

Thank ya sir, I noticed that update this morning and have been 10k all day now, very happy to have v4a back amongst all the others...

I felt like I either screwed up a partition that is unmodified when pushing a kdz via lgup, caused an issue by relocking my bootloader last week, or the twrp version changing from 3.1.0 to 3.2.1 (i might ve off on the exact version numbers) caused the problem.

I have a dump of all my original partitions created before i had an issue so i was gonna try pushing my old userdata in with the 10L fw at some point but i feel like i caused myself enough headache already and it didnt push on the 1st try so i quit.

I may play around with it later if youd like to get any logs or have me try some experimenting, i get bored and cant stand the agony of defeat.

Thanks again for all your info and guides thus far.
20th November 2018, 12:11 AM |#128  
tecknight's Avatar
OP Recognized Contributor
Flag Las Vegas
Thanks Meter: 690
 
More
Quote:
Originally Posted by cody85

Thank ya sir, I noticed that update this morning and have been 10k all day now, very happy to have v4a back amongst all the others...

I felt like I either screwed up a partition that is unmodified when pushing a kdz via lgup, caused an issue by relocking my bootloader last week, or the twrp version changing from 3.1.0 to 3.2.1 (i might ve off on the exact version numbers) caused the problem.

I have a dump of all my original partitions created before i had an issue so i was gonna try pushing my old userdata in with the 10L fw at some point but i feel like i caused myself enough headache already and it didnt push on the 1st try so i quit.

I may play around with it later if youd like to get any logs or have me try some experimenting, i get bored and cant stand the agony of defeat.

Thanks again for all your info and guides thus far.

Well, if you could boot into TWRP after a failed (boot looping 10L), then pull this file for me:
/sys/fs/pstore/console-ramoops
That would be the kernel log during the failed boot.
It could be a big help.
I am going to take a close look at the difference between the 10K and 10L boot images to see if I can make some additional mods to the 10L patched boot.
20th November 2018, 11:16 PM |#129  
tecknight's Avatar
OP Recognized Contributor
Flag Las Vegas
Thanks Meter: 690
 
More
Install a pre-rooted ROM to your LG Aristo 2 / 2 + / Best root method
TAT TecKnight's Aristo 2 Tutorials series
Install a pre-rooted ROM to your LG Aristo 2 / 2 + / Best root method
Requirements:
  • An LG Aristo 2 or Aristo 2 plus
  • A PC running Windows with an internet connection, if you don't have TWRP already installed on your phone
  • A USB cable., if you don't have TWRP already installed on your phone
Note: This procedure is currently my recommended method for rooting a cv1 device and the only method for a device already running Oreo

Note: If you have not already unlocked your phone for flashing, this procedure will wipe your userdata and cache partitions. If you want to retain your apps and settings, back up your data before you perform this procedure and restore your data after completing it.

Note: I would like to give credit for the idea and inspiration of using a TWRP flashable .zip to @NonStickAtom785. He started with an Aristo 1 flashable zip and was able to modify it to work on the Aristo 2, creating the first functional flashable ROM for the Aristo 2. When I was helping him to modify his update_script, I realized that using a TWRP flashable .zip will end up being a faster, easier and much more customizable method of rooting an Aristo 2 or Aristo 2 plus.

[SIZE="3"]0. If you have already unlocked your bootloader and have TWRP installed, you can skip to step 13.

1. If you are currently running Oreo based firmware on your device and you do not already have TWRP installed, you will have to first downgrade your device to Nougat based firmware, before fastboot will let you flash TWRP.
If your phone is an Aristo 2 (Metro by T-Mobile), I recommend firmware version 10K, available here:
https://www.androidfilehost.com/?fid...63190603847051
If your phone is an Aristo 2 plus (T-Mobile), you will need 10K for the Aristo 2 plus, available here:
https://www.androidfilehost.com/?fid...31924117907869
Once you have downloaded your .kdz image, flash it using these instructions:
Install a specific .KDZ image to your LG phone using LGUP
If you are already running a Nougat based firmware or after you have downgraded to Nougat based firmware, continue to step 2

2. Allow your phone to boot into Android normally.

3. On your phone, go to Settings->General->About Phone->Software Info. Click on Build Number 7 times. You have now enabled Developer Options

4. On your phone, go to Settings->Developer Options and Turn ON both OEM Unlock and USB debugging. Turn OFF Automatic System Updates. Click on Select USB Configuration and select MTP (Media Transfer Protocol)

5. Connect your phone to your PC using the USB cable.

6. On your PC, open a command prompt or power shell session in the folder where your adb and fastboot executables reside.

7. In your command prompt or power shell session, type"
adb devices
You should see:
List of devices attached
<SerialNumofPhone> device
8. Now type:
adb reboot bootloader
9. You should see some text in very small letters on your phone. You are now in bootloader or fastboot mode.

10. Type this:
fastboot flashing unlock
fastboot will say this will wipe your data. Tell it to continue.
Note: It's OK if you get a response saying flashing is already unlocked. Just proceed to the next step.

11. Download TWRP to your PC:
TWRP 3.2.3.0 for cv1 devices with fstab mods (encryption related) and Oreo kernel
I upgraded TWRP to 3.2.3.0 and made a couple of mods to make it less likely to glitch. I believe booting the same kernel for boot and recovery should result in a more stable experience.
https://www.androidfilehost.com/?fid...63190603893649
Place the TWRP4cv1WithOreoKernel.img file into the folder containing your adb and fastboot binaries.

12. Now flash TWRP. Type:
fastboot flash recovery TWRP4cv1WithOreoKernel.img
You should see:
target reported max download size of 262144000 bytes
sending 'recovery' (17010 KB)...
OKAY [ 0.585s]
writing 'recovery'...
OKAY [ 0.200s]
finished. total time: 0.790s
13. if you want Aristo 2 (Oreo firmware 20g, Metro by T-Mobile), download this:
(Tec's Lightning ROM for Aristo 2 rel 2)
https://www.androidfilehost.com/?fid...31924117889341
or if you want Aristo 2 plus (Oreo firmware 20e, T-Mobile), download this
(Tec's Lightning ROM for Aristo 2 plus beta 2)
https://www.androidfilehost.com/?fid...31924117887513
or if you want an Aristo 2 (Nougat firmware 10K, Metro PCS), download this (Tec's A2 rooted Nougat V4)
https://www.androidfilehost.com/?fid...63190603863164
or if you want an Aristo 2 plus (Nougat firmware 10J, T-Mobile), download this;
https://www.androidfilehost.com/?fid...63190603855657
Either download it directly to your phone or copy it to your phone once the download completes.

14. Remove the battery from your phone and disconnect the USB cable.

15. Re-insert the battery.

16. Hold the Vol - on your phone and press the power button.
As soon as you see the LG logo, quickly release and repress the power button.
Hold both buttons until you see a Factory Data Reset dialog.
Release both buttons and use the vol keys to highlight Yes.
Press the power button. Now use the vol keys to select Yes again and then press the power button.
Your phone will now boot into TWRP.
Note: If you boot into TWRP and find that the touch screen is not responding, and your screen image has shifted slightly, you may have an incompatible bootloader. Try flashing 0ne of these TWRP images instead:
TWRP with Pre-10L kernel:
recovery.img --> Latest TWRP 3.2.1.0 for cv1 devices by armandop_
TWRP with 10L kernel:
https://www.androidfilehost.com/?fid...63190603862817
17. If this is your first time booting into TWRP, Swipe to allow modifications.

18. Now select INSTALL, then browse to the flashable .zip file you downloaded in step 12.
Swipe to confirm flash. TWRP will install the ROM to your phone.
You should see something resembling this:
Code:
////////////////////////////////////
//  LG Binary ROM installer v5    //
//         By TecKnight           //
//--------------------------------//
// Tecs Aristo 2 rooted Oreo ROM v4 //
// This should flash in about 1.5 min //
// Removed LG RCTD, added parted //
////////////////////////////////////
 
 
Wiping encryption key, if any.
Wiping cache partition...
Creating filesystem with parameters:
    Size: 536870912
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 8192
    Inode size: 256
    Journal blocks: 2048
    Label: 
    Blocks: 131072
    Block groups: 4
    Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
Wiping dalvik-cache folder...
about to run program [/sbin/busybox] with 4 args
rm: can't remove '/data/dalvik-cache/*': No such file or directory
run_program: child exited with status 1
Pre-Formatting System partition.
Creating filesystem with parameters:
    Size: 3707764736
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 8096
    Inode size: 256
    Journal blocks: 14144
    Label: 
    Blocks: 905216
    Block groups: 28
    Reserved block group size: 223
Created filesystem with 11/226688 inodes and 30171/905216 blocks
about to run program [/sbin/busybox] with 4 args
about to run program [/sbin/busybox] with 4 args
Inserting custom bootanimation...
Running: mv /OP/MPCS_US/poweron/bootanimation.zip /OP/MPCS_US/poweron/bta.zip
about to run program [/sbin/busybox] with 4 args
Inserting custom shutdownanimation...
Running: mv /OP/MPCS_US/poweroff/shutdownanimation.zip /OP/MPCS_US/poweroff/sda.zip
about to run program [/sbin/busybox] with 4 args
about to run program [/sbin/busybox] with 4 args
Extracting and flashing aboot image...
Extracting and flashing abootbak image...
Extracting and flashing apdp image...
Extracting and flashing cmnlib image...
Extracting and flashing cmnlibbak image...
Extracting and flashing cmnlib64 image...
Extracting and flashing cmnlib64bak image...
Extracting and flashing devcfg image...
Extracting and flashing devcfgbak image...
Extracting and flashing dsp image...
Extracting and flashing factory image...
Extracting and flashing keymaster image...
Extracting and flashing keymasterbak image...
Extracting and flashing laf image...
Extracting and flashing lafbak image...
Extracting and flashing modem image...
Extracting and flashing msadp image...
Extracting and flashing persist image...
Extracting and flashing raw_resources image...
Extracting and flashing raw_resourcesbak image...
Extracting and flashing rct image...
Extracting and flashing recoverybak image...
Extracting and flashing rpm image...
Extracting and flashing rpmbak image...
Extracting and flashing sbl1 image...
Extracting and flashing sbl1bak image...
Extracting and flashing sec image...
Truncating string cache entries.
Extracting and flashing tz image...
Extracting and flashing tzbak image...
Extracting and flashing patched boot image [A2PatchedOreoBoot.img]...
Extracting and flashing custom system image [a2patchedsystem.img]...
This will take about 1 minute to complete...
 
/////////////////////////////////////
//         Imaging Successful      //
//                                 //
/////////////////////////////////////
The flash should complete in about 1 minute and 20 seconds.

Reboot System when done. You should see the new boot animation as your phone boots into Android. Your phone will be rooted and have Magisk installed.

Please hit the Thanks button at the bottom of this post if you appreciate my work.

FYI: Some useful information about the script that installs the ROM.
1. It automatically detects any encrypted partitions (userdata or cache), then wipes the encryption key and reformats the affected partitions as unencrypted, prior to installing the ROM.
2. Unlike 99% of all update_script's, this script flashes binary images to all] partitions. This makes the script MUCH shorter and more efficient, as no set file property commands are needed. It also makes it very easy to create a flashable .zip from a running system.
3. The script now flashes every partition that LGUP flashes when updating the firmware on a phone, except for the recovery partition. It also flashes 3 partitions that LGUP does not flash. This means that flashing this zip is equivalent to flashing your phone with LGUP, then flashing a patched boot and system partition. The boot and system partitions are the only partitions not flashed with a stock image, Here are some details as to which partitions are flashed by this flashable script vs. LGUP:
https://docs.google.com/spreadsheets...it?usp=sharing
Information about the Lightning ROMs (Aristo 2 & Aristo 2 plus).

New versions of each released 06/06/2019

Features of this ROM:
1. Based on the latest Oreo firmware for each phone..
2. Encryption has been disabled and will be eliminated if it exists on the target phone.
3. LG's resource hogging Root Checking Tool has been removed from the boot image and disabled in the system image.
4. The boot image has been rooted using the latest systemless Magisk release.
5. Numerous unneeded system and privileged apps, which are normally not removable, have been removed, freeing up a great deal of space on the phone and significantly reducing processor overhead. This makes the phone run faster and respond more quickly.
6. LG's system update has been deauthorized by changes in the system image. This means there is no chance a system update will brick your phone or undo the changes made by this ROM.
7. The full screen "Code Red" bootup splash screen has been eliminated. In it's place is a much less noticeable and smaller text message in small yellow letters.



_________
Change Log:
07/02/2019 Changed downgrade firmware link for Aristo 2 plus to an AndroidFileHost URL as lg-firmwares.com links are no longer reliable. Thanks to @Mor Headroom for bringing it to my attention.
06/07/2019 Added updated links for new releases of the Lightning ROMs for Aristo 2 and Aristo 2 plus.
06/02/2019 Clarified downgrade instructions and added firmware link for Aristo 2 plus firmware 10k. Added links for Lightning ROMs for Aristo 2 and Aristo 2 plus.
01/17/2019 Added new TWRP 3.2.3.0 image using Oreo kernel. This appears to fix the unresponsive touchscreen issues that had ocasionally occurred.
12/31/2018 Added new Aristo 2 plus Oreo ROM V2. Updated Aristo 2 Oreo flashable .zip to V4.
12/26/2018 Added detailed instructions for users currently running stock Oreo firmware. Updated Oreo flashable .zip to V3.
12/24/2018 Added Aristo 2 rooted Oreo flashable .zip V2 to flashable ROM list.
11/30/2018 Updated Aristo 2 flashable .zip to version 4. Modified description of image to reflect content.
11/27/2018 Updated Aristo 2 flashable .zip to version 3a. Modified description of image to reflect content.
11/25/2018 Updated Aristo 2 flashable .zip to version 3. Modified description of image to reflect content.
11/23/2018 Added Aristo 2 plus flashable .zip version 2.
11/22/2018 Updated Aristo 2 flashable .zip to version 2b.
11/21/2018 Updated Aristo 2 flashable .zip to version 2a.
11/20/2018 Updated Aristo 2 flashable .zip to version 2.
11/19/2018 Created initial procedure.
The Following 19 Users Say Thank You to tecknight For This Useful Post: [ View ] Gift tecknight Ad-Free
20th November 2018, 11:38 PM |#130  
Junior Member
Flag Tulsa
Thanks Meter: 0
 
More
Awesome. I will run thru the 10L loop and get you the log by morning and then its time for the 10k you made available.

Off to the skating rink with the kiddo for now tho, much appreciated bud
21st November 2018, 04:38 AM |#131  
tecknight's Avatar
OP Recognized Contributor
Flag Las Vegas
Thanks Meter: 690
 
More
Quote:
Originally Posted by cody85

Awesome. I will run thru the 10L loop and get you the log by morning and then its time for the 10k you made available.

Off to the skating rink with the kiddo for now tho, much appreciated bud

Thanks. I appreciate your feedback on the flashable .zip as well.
I think it will prove to be a superior method of rooting an Aristo 2.
Post Reply Subscribe to Thread

Tags
lg-aristo-2, lg-k8-plus, lg-k9, lg-phoenix-4, lg-x2

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes