[WIP][ROM][LM-G710EM] LineageOS 18.1 for judyln

[J0SH1X]

The most important thing to fix for all of us I think, is the screen flicker that's the only "annoying" issue, other than that your ROM version is awesome and I'm very happy to use it!

The hard thing is I litterally have no idea what this iusse is about i have to ask v40 guys if they have or had this aswell and if they could eventually fix it

 

[MihaiA7X]

The hard thing is I litterally have no idea what this iusse is about i have to ask v40 guys if they have or had this aswell and if they could eventually fix it

I couldn't find anything in the logcat but I suspect the proximity sensor ? because it also appears in calls after the proximity sensor fires...I don't know maybe I'm wrong and it doesn't happen all the time...

 

[FlixH]

I'm stuck when flashing boot_twrp.img, could someone please help me?
After the steps below I'm in a boot loop and only able to access fastboot and factory data reset (volume down + power).

What did I do wrong? Why can't I access TWRP? Thanks for all help.


What I did:

fastboot flash unlock unlock.bin (successful)

platform-tools>fastboot flash recovery boot_twrp.img
Sending 'recovery' (65536 KB) OKAY [ 2.095s]
Writing 'recovery' FAILED (remote: 'Cannot flash
this partition in unlocked state')
fastboot: error: Command failed

fastboot oem lock

platform-tools>fastboot flash recovery boot_twrp.img
Sending 'recovery' (65536 KB) OKAY [ 2.091s]
Writing 'recovery' FAILED (remote: 'Flashing is
not allowed in Lock State')
fastboot: error: Command failed

fastboot flash unlock unlock.bin (successful)

fastboot flash boot_a boot_twrp.img (successful)
fastboot flash boot_b boot_twrp.img (successful)
fastboot flash boot boot_twrp.img (successful)

 

[LameMonster82]

I'm stuck when flashing boot_twrp.img, could someone please help me?
After the steps below I'm in a boot loop and only able to access fastboot and factory data reset (volume down + power).

What did I do wrong? Why can't I access TWRP? Thanks for all help.


What I did:

fastboot flash unlock unlock.bin (successful)

platform-tools>fastboot flash recovery boot_twrp.img
Sending 'recovery' (65536 KB) OKAY [ 2.095s]
Writing 'recovery' FAILED (remote: 'Cannot flash
this partition in unlocked state')
fastboot: error: Command failed

fastboot oem lock

platform-tools>fastboot flash recovery boot_twrp.img
Sending 'recovery' (65536 KB) OKAY [ 2.091s]
Writing 'recovery' FAILED (remote: 'Flashing is
not allowed in Lock State')
fastboot: error: Command failed

fastboot flash unlock unlock.bin (successful)

fastboot flash boot_a boot_twrp.img (successful)
fastboot flash boot_b boot_twrp.img (successful)
fastboot flash boot boot_twrp.img (successful)

We don't use fastboot flash recovery anymore. The recovery is in the boot image

 

[FlixH]

On the second try it worked perfectly.

Then after the last step reflashing boot_twrp, I decided to "fastboot oem lock" the device because I thought that the "unlocked bootloader... ?" on boot message would disappear.

Turns out I messed up pretty bad, as now I'm unable to boot the device because of "Your device has failed a routine safety check and will not boot" and I'm unable to "fastboot flash unlock unlock.bin" because the "OEM .." option in the android developer options is disabled.

I think if I somehow manage to obtain my regions kdz file from LG and then make a firmware update with LGUP it should boot again as the firmware signature is correct and then I can start over again.

Any advice is appreciated.

 

[kadiix]

On the second try it worked perfectly.

Then after the last step reflashing boot_twrp, I decided to "fastboot oem lock" the device because I thought that the "unlocked bootloader... ?" on boot message would disappear.

Turns out I messed up pretty bad, as now I'm unable to boot the device because of "Your device has failed a routine safety check and will not boot" and I'm unable to "fastboot flash unlock unlock.bin" because the "OEM .." option in the android developer options is disabled.

I think if I somehow manage to obtain my regions kdz file from LG and then make a firmware update with LGUP it should boot again as the firmware signature is correct and then I can start over again.

Any advice is appreciated.

You can find all of kdz firmware there:

https://lg-firmwares.com/

Just enter your model and download.

 

[FlixH]

You can find all of kdz firmware there:



Just enter your model and download.

Sadly that list doesn't have my regions firmware. I contacted them, maybe they can help.

 

[kadiix]

Sadly that list doesn't have my regions firmware. I contacted them, maybe they can help.

Don't worry about the region just take the correct model.

I'm from Belgium I take the French one. It works perfect ?

 

[FlixH]

Don't worry about the region just take the correct model.

I'm from Belgium I take the French one. It works perfect

I'm Swiss and tried a French, British and Hungarian version. Still get "Your device has failed a routine safety check and will not boot" with all of them. I really hope that it boots with my regions kdz else I might've successfully managed to brick my device. :fingers-crossed:

 

[kadiix]

I'm Swiss and tried a French, British and Hungarian version. Still get "Your device has failed a routine safety check and will not boot" with all of them. I really hope that it boots with my regions kdz else I might've successfully managed to brick my device. :fingers-crossed:

I don't want to be pessimist but I don't think that will change anything ?

 

[MihaiA7X]

I don't want to be pessimist but I don't think that will change anything

It doesn't change anything, it happened to mine too and I've sent it to service, waiting for them to contact me back

 

[sader1994]

For those who can´t install the ROM

I have tried it multiple times and it doesnt want to boot. I have read about devices that have the a/b partition schematic.

For me the folowing process worked:
I´m working on Ubuntu 18.04 amd64

Downloading

git clone https://github.com/cyxx/extract_android_ota_payload
cd extract_android_ota_payload
chmod +x extract_android_ota_payload.py

download the lineage-16.0-20190508-UNOFFICIAL-judyln.zip file mentioned in Post #1

run :

python extract_android_ota_payload.py lineage-16.0-20190508-UNOFFICIAL-judyln.zip

wait till it was extracted. start your phone in Bootloader mode by turning it off with Vol - and Power Off and holding Vol - and inserting the USB C plug
Please don´t change the directory

The following shell code will wipe your phone.

fastboot  flash boot_a  boot.img 
fastboot  flash boot_b  boot.img 
fastboot  flash system_a  system.img 
fastboot  flash system_b  system.img 
fastboot  flash vendor_a  vendor.img 
fastboot  flash vendor_b  vendor.img 
fastboot  flash vbmeta_a  vbmeta.img 
fastboot  flash vbmeta_b  vbmeta.img 
fastboot  flash dtbo_a  dtbo.img 
fastboot  flash dtbo_b  dtbo.img 
fastboot erase userdata
fastboot reboot

wait till it boots up und have your fun :good:

 

[Baijoosharma]

I guess mine is also lgm710EM m I right?

 

[coolrevi]

I guess mine is also lgm710EM m I right?

4GB/64GB is EMW.
You can check in Settings - System - About Phone - Common - Hardware info
The model number will give the exact variant.:fingers-crossed:

 

[aleksa.dobree]

Led

whats wrong with it , it works fine on my side , also the green if charged full wil turn off as soon as u have 99 percent its not a bug its a feature

I have a problem with led but on AOSIP. It keeps blinking, do you know the solution? Thanks

 

[crnkoj]

Hey guys, do the gcam ports work with this los? HDR, Night sight, 60/240fps video? Thanks

 

[kadiix]

Hi guys.

I don't know how to install boot-twrp.img, I don't know the command.

Please someone can give me this one?

Thank you!!

 

[oliake]

****ing ******s why won't you help anyone?!!

 

[kadiix]

I think this post need a good tutorial with some "noob" details for beginners.. Because there are a lot of questions with no answers.
Maybe someone who successfully install this rom could do it ?

 

[artixerix]

fastboot flash boot_a boot_twrp.img
fastboot flash boot_b boot_twrp.img

That's all there is to it