yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] kenfalco_14:
I had the same problem. I solved making an FWUL cd boot and flashing recovery with fastboot. It was very easy and fast. Many thanks agsin to steadyfasterX.

Cheers.
[G4 Android Development] F1r3byte:
Whoah... That was a fast reply. Thanks a lot !

I have read the guide for nougat carefully !

I don't understand what you mean by using the normal commands. If you mean to use the commands from [MM], then I've already tried that.

Using fastboot boo twrp.img doesn't work with Nougat. The boot command has been removed, as it says in the OP.

I am I have tried several different versions of twrp, but none would really install. Any help would be greatly appreciated.

---------- Post added at 10:28 PM ---------- Previous post was at 10:22 PM ----------

So you are saying that if I follow the same procedure using Linux, it might actually work ?

I'm gonna give this a try, thanks for mentioning it ! :)

But can you please provide a clearer procedure.

I did not understand what you did when you changed directory to boot.

I appreciate your efforts, thanks a lot ! :)
[G4 Android Development] ThePiGuy:
Ok sorry, I didn't realise fastboot boot had been removed. Flash twrp, and then ensure you go straight back into recovery after fastboot reboot using the key combo (if you boot into your main OS first, it will wipe TWRP).

Then ensure system is mounted and not read only to allow TWRP to patch your system
[G4 Android Development] F1r3byte:
It refuses to boot into recovery after fastboot reboot !

It will perform the corruption check on the first boot then boot again into the system.

But I will try a few times, maybe I get lucky. XD

Thanks a lot ! :)
[G4 Android Development] ThePiGuy:
Just guessing, as I don't have it installed, but maybe you aren't getting the key combo in fast enough.

Is the corruption check the warning screen (similar to the bootloader unlocked message on v20).

If so, ensure that as soon as the screen goes blank from fastboot reboot, you hold down power and vol down, and then when the screen first shows something (it may be that warning), release and then immediately press the power again without ever releasing the volume button

Sorry if you have already done this - I'm just guessing based on my brief experience of v29
[G4 Android Development] F1r3byte:
I have already done something similar and it worked ! So I will post in detail what I did, in case someone else faces the same issue !

Here is what I did:

I went to the directory in which I have adb and fastboot installed.

Copied twrp.img there, after downloading it from the official website.

Opened git bash command line.

entered the following commands:

adb reboot bootloader

fastboot flash recovery twrp.img

( Note: With git bash, you made need to use the whole to adb ( and fastboot, and twrp.img ) between qoutations marks instead of directly using adb, because git bash doesn't know the path to adb.exe )

It flashed it, then It held down both the power and the volume down keys.

While still holding them down, hit enter ( with my pinky finger ).

Once the first LG logo appeared, I stopped holding the power button then held it again.

I pressed yes twice when prompted to erase the device's data, and TWRP showed up.

I made sure to not keep my system read only, by sliding the slider the first appears.

I rebooted into recovery from TWRP, and it was installed on my phone.

Now everything is working !

Thanks a lot for everybody's efforts. Especially you my friend. You gave me a good idea on how to get it to work ! :)
[G4 Android Development] ThePiGuy:
You're welcome - glad I could help :)
[G4 Android Development] steadfasterX:
that is is exactly I wrote in the OP just that I do not use git bash or what you using the important thing is mentioned in red colours in the OP which states in the installation guide:

I really have no idea to make this even more clear that this step is crucial important to do otherwise TWRP gets overwritten when Android is booting

But hey it is working for you now so all good! :)

EDIT:

I modified the OP a bit to make it even more clear:
[G4 Android Development] toub74:
3.2.0 or 3.2.1 are nowhere proposed for G4. On the site and on the app, the moat recent available version is 3.1.1. Is this intended ?
[G4 Android Development] ThePiGuy:
I believe (correct me if I am wrong) that the reason we do not have an up to date TWRP on twrp.me is because Nougat and Marshmallow roms need different decrypting algorithms (file-based vs full disk-based).

Therefore, all the unofficial TWRP's are on [MENTION=5545101]steadfasterX[/MENTION]'s (the developer of both the official TWRP and the unofficial ones) website, which is linked in the first post of this thread.

There you will find TWRP 3.2.1 for your G4
[G4 Android Development] steadfasterX:
actually what ThePiGuy said is true but the main reason is I hadn't had the time to fix some build errors on the official build server..

sorry quite busy with UsU atm.. will fix these asap..

.
[G4 Android Development] ojcu:
I've got problem with entering the recovery. Flashing seems successful, I enter the factory reset and hit yes twice but then the unlocked bootloader warning appears and then it's either stuck on LG logo or system boots normally, like no reset was done. I've tried flashing with both Windows and fwul but no luck. BTW, I also can't enter download mode, it just stucks at "download mode" with those 5 blue dots but the phone can't be discovered by the computer. Any help would be appreciated.

Edit: I've tried another approach. After installing Magisk (brilliant app, big thanks for that) I installed TWRP app, granted root permission, flashed latest preview but still can't get into recovery. After hitting yes twice LG logo appears, then reboot to system. Neither enters TWRP nor does factory reset.

BTW, installing Magisk seems to help with Enable OEM Unlock issue. Before that option was greyed out, now it works. Hope that will help someone. ?
[G4 Android Development] steadfasterX:
The Installation process of TWRP is very sensitive and you have to follow it step-by-step which is very clearly described.

if you do not boot directly to TWRP after flashing it will not work!

Also you should mention what bootloader version do you have. So

what was the latest stock rom installed?

The method to install is different between lollipop/marshmallow and nougat. This is all described on the official website and in here in the OP.
[G4 Android Development] DosenHatti:
I enjoy the patience you show with newbees.

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] ojcu:
I know and instruction couldn't be any clearer. I did it exactly as instructed. The only difference was that "Enable OEM Unlock" was greyed out but bootloader was unlocked. That changed after installing Magisk (via patched boot image). It seems like something stops both download mode and recovery from booting but system and fastboot starts fine. Maybe I messed something up while flashing Nougat?

I've got stock Nougat v29a, forgot to mention that, my bad.

P.S.

Everyone was newbie once so thank you for your patience.
[G4 Android Development] bxlegend:
[MENTION=5545101]steadfasterX[/MENTION] Any plans to build for h811?
[G4 Android Development] Aldideos:
Stock based rom bere ready to test, I sent you a pm
[G4 Android Development] bxmoney181:
+1

Also willing to test for H811 v20o.
[G4 Android Development] steadfasterX:
Atm not but we'll if they are the need I could do that maybe. I have to check first what the differences between those both are. Normally I do not provide something for a device I do not own but it seems that 811 and 815 are not so far from each other....

Thx! Check your PM for instructions :good:

Well good to know that! I cannot promise anything and I want to fix at least the time issues for stock and decryption for stock first before doing anything for the 811... :p

.
[G4 Android Development] bxmoney181:
That's exactly the 2 reasons why I was looking for an H811 build. Lol
[G4 Android Development] steadfasterX:
Good news again: time issues fixed (hopefully) for STOCK based ROMs!

build #153 (not released yet) will have the time issue fixed for STOCK or STOCK based ROMs. :highfive:

Next one: decryption on STOCK

.
[G4 Android Development] Aldideos:
Very good news, I love your work :)

Sent you another pm with the request to test the new version. Version 144 works without problems.
[G4 Android Development] steadfasterX:
Unfortunately there are still errors regarding firmware partition

For some users it works (like me) for some not and some reporting that it hasn't worked first time and after restoring manually it works :silly:

At this point I want to say thanks for all those testers it is really appreciated!! :highfive: :fingers-crossed:

Due to the problems of firmware partition the release will be delayed as you may think of..

I will check all the logs and files the testers already send or will send to me soon. If I cannot find the root cause in a short time I will stop supporting backup and restore of firmware partition. That means if you need to have a backup of this you have to follow the FAQ on post 3 of this thread which is ok for the most users I think.

sorry for the delay but it is the best to have it all fully tested as you can see :rolleyes:

.
[G4 Android Development] DevUt:
Can I have the logs
[G4 Android Development] popy2006:
will send you my logs soon with pm
[G4 Android Development] steadfasterX:
build #162 arrived for

private

beta testing. :highfive:

Changes:

time issues fixed for STOCK as well

firmware removed from backup menu (HINT: it is still possible to RESTORE if you made a backup with a previous build

but DO NOT DO IT

)

some fstab issues solved but this is nothing you can see :p

Decryption on STOCK still not working this will be the next I will fix.

If you are on stock or stock based (not Imperium ROM cause I already have a tester for that) and wanna test let me know by PM!

Cheers

steadfasterX

.
[G4 Android Development] DevUt:
Man what did selinux do?

Get me kmsg

Its fine you removed firmware backup

But you cant remove it all together, you need to find a solution. As i saw TWRP was not just being able to restore the selinux context of the firmware. And as you said that only frw person were having this problem like An RR guy and an stock guy tell them to kmsg of latest build 'we' :p made. What steps i took were the firat steps now we need to figure out more about the selinux as we have total new clean sepolicy so get mw the logs i will take a look at them as it is sunday tomorrow :laugh:
[G4 Android Development] steadfasterX:
Devut i said i WILL fix that ! But not for now.

one step after the other. First i will finish the time issue for stock. This is the current beta build. Then i will fix decryption for stock. Then firmware .

Firmware is absolutely luxus. We do NOT need firmware backup. It can be restored by LG up software so to be honest I don care about that much atm. Ok devut? I come back to you dont have fear ;)

.
[G4 Android Development] Meakii:
Where can I find the downloads? 'Download section' link leads nowhere. Thanks for your work :good:
[G4 Android Development] steadfasterX:
Please read carefully my above post. It is not public yet until the beta testers finished the tests. Read the changelog post 2 of the thread too.

Thx for your patience.

.
[G4 Android Development] popy2006:
Send [MENTION=5545101]steadfasterX[/MENTION] a PM, but be aware, these are beta builds.

DO A MANUAL EFS/FIRMWARE BACKUP FIRST with DD or wait for official release!
[G4 Android Development] DevUt:
Dees_Troy fixed efs just look out for firmware
[G4 Android Development] steadfasterX:
.

Finally Build #162 went public

:victory::victory::victory::victory:

Check the changelog: http://xdaforums.com/showpost.php?p=68249026&postcount=2

Download here: http://xdaforums.com/devdb/project/?id=16696#downloads

Thanks again for all testers worldwide making this available for you all

have fun. :highfive:

Cheers

steadfasterX

.
[G4 Android Development] popy2006:
Thx, works as expected!! ?

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] orhtun01:
Works like a charm! Thanks. Nice to see the date correct on twrp :)
[G4 Android Development] steadfasterX:
What do you have flashed exactly when you flashed nougat? Share the link pls.

And when you have root just do this:

Flash latest preview in the TWRP app

While still in this app choose reboot and select recovery!

Do not use the key combo to get into TWRP. You have to boot into recovery directly from android.
[G4 Android Development] ojcu:
It was H81520p_00_0314.kdz but my phone is affected by ilapo so I followed this thread

https://xdaforums.com/g4/development/ilapo-infinite-loop-auto-power-off-fix-t3404421 to make it work. When flashing Nougat, after the main zip I flashed disable_big_cores.zip from Nougat's thread and in the end latest TWRP preview but to be honest I don't remember if I rebooted to recovery right away or to Android.

Edit: I used Twrp app again as you said, rebooted to recovery but it's still the same. After reboot bootloader warning appears -> LG logo for couple of seconds (no blue led flashing) -> reboots itself -> bootloader warning -> LG logo (this time blue led flashing) -> android starts normally.

I tried fastboot method again using latest preview and now my phone has been stuck at stage 2 (LG logo with no blue led) for last couple of minutes.

EDIT: After several minutes being stuck at logo I pulled the battery and turned the phone on normally and the Android started with no problem. Anyway, my goal is to eventually flash the CypherOS but without recovery my options are limited. I can downgrade or try to flash stock Nougat (or FreedomOS) again but I've only got fastboot available. There's also FlashFire by Chainfire but I don't know if anyone tried that on H815. It's bit of an offtop now and sorry for that.
[G4 Android Development] steadfasterX:
Ok try this :

Flash TWRP in fastboot like this:

fastboot flash boot twrp.img (this will overwrite your boot(!) partition with TWRP)

fastboot flash recovery twrp.img

fastboot reboot

TWRP should show up without any interaction.

Choose reboot -> recovery

TWRP should pop up again.

Now you need to flash a ROM like cypher as the boot partition has been overwritten
[G4 Android Development] ojcu:
Thanks mate. I'll try that on on Tuesday. My wife hates the phone already and says I spend more time with it than with her ?
[G4 Android Development] SeewolfPK:
I try kessaras newest rom and also the twrp 103. The data in 103 is not correct (20150101)

In 96 all is good.

Sorry, I try log via https://hastebin.com/ but it seem not work or I did not know how to do:crying:
[G4 Android Development] steadfasterX:
Just click the save button at the top right. The url changes to a unique link for sharing. Or use bpaste, paste.omnirom.org, pastebin or any of the other thousands of paste services. Everything is better then attachments. This is just a last resort and better then nothing ;)

To get time work it is important that you boot once into android. Ensure time is correct and reboot to TWRP.
[G4 Android Development] SeewolfPK:
I fill in the text and klick the save button, but nothing happend.

I boot into android. Date und time is correct. I reboot to TWRP and if I will make a backup the file has wrong data.
[G4 Android Development] steadfasterX:
Ok. On which aoscp build does that happen ?
[G4 Android Development] SeewolfPK:
atm I use kessaras 20180216
[G4 Android Development] ojcu:
Tried that, didn't work but it made me think. It should work on a fully working order device but my device is one of the ILAPO affected. Then I edited recovery image as you said in this thread and BOOM, it's working. I had to do the same with boot.img after flashing the rom. Thanks a lot mate
[G4 Android Development] steadfasterX:
ooh .. yes good finding. actually the flashing went fine always but due to the ILAPO it reboots and so gets overwritten everytime...

glad u figured it out and thx for sharing!

.
[G4 Android Development] SeewolfPK:
No idea to make it work correct?

I can live with that, because I can make own Backupname :D
[G4 Android Development] steadfasterX:
I have many ideas this is not the problem I fixed the time in the past six or seven times and once in a while some ROM changes something and I need to fix it again and again and again and again and again so I'm I am a bit tired at the moment regarding this
[G4 Android Development] rocky184:
Hi,

Not sure if this is the right thread to post this in, so apologies if I'm wrong.

I was on N AOSCP and upgraded to the O version earlier today but Gapps didnt install and I also seemed to lose TWRP so reinstalled. I tried to go back to N using the TWRP backup I'd made and it keeps asking for the pin code to unlock the phone and although I enter the correct one, it wouldn't open.

I therefore reverted back to stock N from another TWRP backup on which I'd used a tap code for unlocking. Again even though I'm using the correct tap code, it still won't unlock.

Can anyone help or do I have to erase and start from fresh?
[G4 Android Development] steadfasterX:
That's a known issue. You have to remove the screen lock protection and set it again. There is a TWRP flashable zip for this too.
[G4 Android Development] rocky184:
Thanks [MENTION=5545101]steadfasterX[/MENTION] for the help.

I'd given up searching for a solution and just reflashed Oreo from scratch. At least now I know what to do if it happens again.
[G4 Android Development] bigd19888:
trying to flash twrp on my device

when I get reboot into bootloader. I get the message "waiting for device" when I try and flash twrp onto my device

adb recognizes my device but as soon as I reboot and try and flash twrp I get that error message

anyone know what I can do?
[G4 Android Development] steadfasterX:
How should one help you without any idea about your environment?

Windows or Linux?

On Linux you need to use sudo for fastboot (if it is not configured for a unprivileged user)
[G4 Android Development] bigd19888:
Windows

Using lg drivers and minimal fastboot adb

"Waiting for device" once i reboot and try and flash twrp. Bootloader already unlocked
[G4 Android Development] steadfasterX:
Well give FWUL on an USB stick a try..
[G4 Android Development] dat_benjie:
Hi everyone,

I hope this is the right thread, I got redirected here from another one. I installed the official Nougat update and after that the Oreo AOSCP ROM. Everything went (seemingly) fine, Oreo was working. I wanted to reflash Oreo to get rid of some Google Apps, but the problem then was, that I could not reboot into TWRP. The only recovery mode is the Android recovery and I cannot reset the phone, neither use ADB sideload, nor do anything else. Only thing that is working, is to enter the fastboot mode, but my laptop does not recognize the phone while in fastboot mode.

I also tried resetting the phone to factory defaults from within Android and now my phone is stuck in a bootloop which ends in the (useless) Android recovery mode.

At first I thought reflashing the stock kdz would not be a problem. I am able to enter download mode, but it only stays in download mode for about 15 seconds and then reboots itself. LGUP or LG flash tool, don't recognize my phone in that short amount of time.

I tried the above mentioned solutions on OS X, Windows 7, Windows 10 as well as FWUL. No system recognizes my phone.

I really am at my wit's end. Any help would be appreciated.

If any further information are needed, I am happy to provide these.

Thanks in advance
[G4 Android Development] steadfasterX:
Flash TWRP to boot and recovery

fastboot flash boot twrp.img

fastboot flash recovery twrp.img

Reboot

TWRP should popup
[G4 Android Development] dat_benjie:
Thanks for your quick reply, but fastboot does not recognize the phone. When i try to flash TWRP I am stuck on waiting for device. adb and fastboot drivers are installed properly, also reinstalled everything several times. The phone is neither recognized in Windows nor FWUL while in fastboot mode. Do you have other suggestions? Thank you

EDIT: same results with FWUL, fastboot devices is not showing my device, and fastboot flash boot twrp.img is stuck on "waiting for device" so I guess this is no driver issue?
[G4 Android Development] steadfasterX:
How do you installed FWUL? It's highly recommended to flash FWUL on an USB stick especially when you have issues like that.

in FWUL open a terminal and type

lsusb

While the device is connected in fastboot

Paste the output here
[G4 Android Development] dat_benjie:
The output is

[android@fwul ~]$ lsusb

Bus 004 Device 006: ID 05ac:0253 Apple, Inc. Internal Keyboard/Trackpad (ISO)

Bus 004 Device 005: ID 05ac:8242 Apple, Inc. Built-in IR Receiver

Bus 004 Device 009: ID 05ac:821d Apple, Inc.

Bus 004 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)

Bus 004 Device 003: ID 0424:2513 Standard Microsystems Corp. 2.0 Hub

Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub

Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 001 Device 003: ID 05ac:8509 Apple, Inc. FaceTime HD Camera

Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 002 Device 002: ID 058f:6387 Alcor Micro Corp. Flash Drive

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The laptop I am using is a MacBook, hence the Apple Camera etc..

I flashed FWUL on a USB stick, but somehow it can only boot in forgetful mode. But this should not be a problem should it?

I attached the output of the lusb command as a screenshot.
[G4 Android Development] steadfasterX:
I guess it's either your USB port, the USB cable or any adapter between (if any)
[G4 Android Development] dat_benjie:
I thought of this at first as well, but I tried different cables (using the LG charger atm), different USB ports and 3 different computers. I am not using a USB hub.

Do you think that this

https://xdaforums.com/android/general/unbrick-lg-model-download-recovery-t3060184

could help fixing my problems?

or do you have other ideas how to solve this situation?
[G4 Android Development] steadfasterX:
Well if you can get your device recognized in download mode... Flash different firmwares and re-try.

If that doesn't help open an own thread in the help section..
[G4 Android Development] steadfasterX:
New PREVIEW release

read more about the <flavor>'s in the OP!

Now since UsU has been released I will fix the official builds hopefully soon

twrp-3.2.1-PREVIEW-106_g4_<flavor>

Status: stable

Release date: 2018-03-15

Download: Download Page (same download for all G4's)

Device Tree changelog: MM flavor and N flavor

PREVIEW vs. OFFICIAL changelog: MM PREVIEW <--> latest official TWRP and N PREVIEW <--> latest official TWRP
[G4 Android Development] adam_s_459_:
So is the TWRP build you have made for UsU G4's specific to those devices? Or can we flash a build from here?
[G4 Android Development] steadfasterX:
there is no UsU specific TWRP version.

All TWRP versions are unified for ANY g4 out there.

.
[G4 Android Development] steadfasterX:
NEW PREVIEW release

read more about the <flavor>'s in the OP!

twrp-3.2.1-PREVIEW-109_g4_N

Status: stable

Release date: 2018-03-17

Download: Download Page (same download for all G4's)

Device Tree changelog: N flavor

Summary

changelog:

Decrypting STOCK N is working now!
[G4 Android Development] zulfurion:
link is dead :/
[G4 Android Development] DosenHatti:
I downloaded 1 hour ago

Gesendet von meinem LG-H815 mit Tapatalk

But you are right, now it's dead
[G4 Android Development] zulfurion:
could you put it in a cloud please ? :D
[G4 Android Development] steadfasterX:
will be back soon. I have to do some maintenance

[MENTION=2626236]zulfurion[/MENTION] in the meantime download from here: http://leech.binbash.it:8008/TWRP/

-
[G4 Android Development] DosenHatti:
Thought so, because kessaras lg g4 Oreo is also not available. ;)

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] zulfurion:
Nice job