yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] maxauvy:
:rolleyes:

I was talking about EFIDroid ofc. Obviously, Play Store needs GApps...

I was just saying I'll try to grab the APK from Yalp Store instead of Play Store, as Google apps are not installed on my phone ;)

thx
[G4 Android Development] steadfasterX:
Could u try the following build please: v3.1.1-0_BETA1

it contains the mentioned sepolicy fix for the decryption issue

it should also fix the reboot not possible issue when no ROM installed ( [MENTION=5308112]raptorddd[/MENTION] )

will now boot on LL devices (special things like e.g. encryption/decryption may NOT work though)

hint: to support LL i had to remove kernel compression so don't be surprise of the

doubled

file size as of now

containing many fixes in llama kernel (https://github.com/steadfasterX/kernel_lge_llamasweet/pull/3)
[G4 Android Development] gibbsnich:
Not true: You can have playstore without gapps: https://xdaforums.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616

Sorry for OT ;)
[G4 Android Development] raptorddd:
[*]it should also fix the reboot not possible issue when no ROM installed

works now after deleting or wiping all data/cache/dalvik/system/ and no OS its installed reboot from recovery to recovery works now.. thanks you.:good:
[G4 Android Development] skdubg:
Update works, but System UI has stopped after reboot.

this problem is from llamasweet kernel, its only solved by full wipe, restore of any partitons doesnt work
[G4 Android Development] steadfasterX:
you have restored a previously taken backup and then the error occured? Which ROM?

why do you think the llama kernel has anything to do with that? it runs within TWRP only and is independent from your ROM.

I need the recovery log of backup & restore .

.
[G4 Android Development] kessaras:
TWRP 3.1.0.x xda theme

im sharing my favorite twrp theme.

Tested on [MENTION=5545101]steadfasterX[/MENTION] 3.1.0.x and its working.

Source:

https://plus.google.com/communities/114150127654967230069

Easy installation​

Just download the ui.zip and put it inside /sdcard/TWRP/theme.

Result is:

/sdcard/TWRP/theme/ui.zip

And reboot to recovery to see it !

Screenshots
[G4 Android Development] maxauvy:
Nope, LOS doesn't support Signature Spoofing and other stuff required to make MicroG work properly ;)

---------- Post added at 04:52 PM ---------- Previous post was at 04:46 PM ----------

Yeeaaaaah, I'd like to... but today when taking a picture, my G4 froze itself out. Since then, impossible to boot it, it freezes after a few seconds, with a green screen of death (demigod handler, hardware reset). I have absolutely NO IDEA of what happened nor how to fix it (instead maybe going back to stock). I had something very similar with the G3... Aaah LG >_<

I'll try as soon as my phone is fixed (if that's even possible).
[G4 Android Development] gentr:
beautiful themes, hope for more others like this [emoji108]
[G4 Android Development] gibbsnich:
I know what you mean but LOS is F/OSS and a Nougat patch is available, so it's possible, of course, even if we ignore that there a tools to patch a zipped ROM image.. (And you wrote "my LOS", so I thought you're building it yourself anyway.)

But what "other stuff" do you mean?
[G4 Android Development] maxauvy:
I used to build it but for maybe 4 months I use official builds, as it's much more easy for me (don't have time to build anything these days :D ).

Yeah I discovered the patch last time I clean flashed my ROM, as I wanted at this time try microG. I'm not sure what were the other requirements though, but I'm quite sure there were 2 things that prevented me to install microG. I should give it another try after the summer, as I'll have more free time ;)
[G4 Android Development] steadfasterX:
OT warning #1 :rolleyes:

.
[G4 Android Development] brossovitch:
[MENTION=5545101]steadfasterX[/MENTION] sorry for this newb question, but is the official TWRP 3.1.1-0 download safe for h811?

I noticed you're the listed maintainer on the official TWRP h815 page but on the h811 page the maintainer is listed as NONE.

Just curious, I'm aware there was some issues with a previous Official TWRP build.

Otherwise, I've been using your 3.1.0-0 beta for almost 2 months and it's just exquisite.

Thanks for your hard work.
[G4 Android Development] kessaras:
always go with the op.

twrp server is slow. here the op can share his build without waiting to sync to the official and merge changes.
[G4 Android Development] brossovitch:
That's exactly how I feel about it, but the latest build (3.1.1-0) was just released in both OP and Official TWRP page. So I'd just wondered.

I also feel safer knowing the beta is based on LlamaSweet as I use LlamaSweet Kernel on my device.

Appreciate the response kessaras. I'll probably stick with BETA. However, I did just DL both beta & official 3.1.1-0 and flashed official. Seems to work just fine honestly. I'll have to test it a little bit and make sure.

Also, in BETA there's a few more options for partitions. I don't want to accidentally wipe firmware or something like an idiot. It could happen.
[G4 Android Development] steadfasterX:
I'm very sorry to say that but do not use the official ! either use the latest beta or the previous one

The latest official release doesn't have many many bug fixes included in my beta version! There is at least one which is high critical. I will let remove the latest official ASAP due to this.

Besides this you are right that the current situation of the website is misleading and I have to restructure all g4 sites to show the correct contents! This has to be done right and will take some help from the TWRP developers as well

Sorry about that

.
[G4 Android Development] denied1977:
What is then the best link for download for now? From the first post this link https://twrp.me/devices/lgg4h815.html ?

THANKS :D
[G4 Android Development] steadfasterX:
tbh I can recommend the latest beta only until the code gets merged: https://xdaforums.com/devdb/project/?id=16696#downloads

Which of those depends on you (both are working for any G4 model):

1. very well tested and stable:

twrp-3.0.2-2-h811_h815-steadfasterX-build327_BETA-5.img

2. less tested but when u wanna have the newest:

twrp-3.1.1-0_BETA-h811_h815-steadfasterX-build1.img

Update (2017-06-21):

Please just use the latest official: https://twrp.me/devices for a stable version.

.
[G4 Android Development] brossovitch:
I can say your beta 3.1.0-0 build works well with stock MM and LOS14.1. backups & restoring and flashing. I don't use encryption. I'm about to flash 3.1.1-0 now. Thank you.
[G4 Android Development] owlery_hk:
I was experimenting with the latest 3.1.1 build yesterday and found that it was able to backup and flash without problems on LOS13.

Not sure about restoring, and I do not use encryption.

The only thing is that when the screen times out and turns off, the device becomes non responsive and I have to pull the battery.

The time does not work, but that is an old issue.

As long as you keep the screen on, it works perfectly as far as I know.
[G4 Android Development] steadfasterX:
Time is fixed long time ago... You may have to do an one time action though. Details & howto FAQ #6 (Why is the time wrong in TWRP?)

When you say "The only thing is that when the screen times out and turns off, the device becomes non responsive and I have to pull the battery" does this happen even if you do nothing in TWRP? e.g. just boot in TWRP then wait for the timeout and then it happens? Or while taking a backup?

It would be nice if you can pull the logs when that happened please - see FAQ #4 (What Logfiles have to be provided and how?). (at least 4A better would be also 4B)

.
[G4 Android Development] owlery_hk:
Thanks for the reply.

I applied the procedure in FAQ6.

The time displays correctly after a first reboot into recovery by clicking reboot>recovery.

However it would revert back to its incorrect state after I pull the battery and reboot into recovery, along with other settings I have made in the setting page.

I have pulled the recovery log from the device as per FAQ 4B.

Sent it to you by a PM.

The screen does not refuse to power on if left to time out in the main menu screen, only during a back up does it refuse to come on.

I pulled recovey.log twice to see and confirmed that the actual backup was progressing.

It is just that the screen was unresponsive and the power button does not wake the device up.

When i try to pull dmesg.txt, It says "remote object '/tmp/dmesg.txt' does not exist".

I was patient this time and left the device for a good ten minutes.

It appears that the screen would come back on, upon completion of the back up.

Perhaps I just got to be patient and leave the phone to do its own thing during back up.
[G4 Android Development] steadfasterX:
twrp seems to be inresponsive when the backup is taken: this is known. Just wait until the backup has finished.

regarding the time issue I will check the logs and come back to u

.
[G4 Android Development] brossovitch:
My time in TWRP, literally just started to be correct with 3.1.1-0-BETA. LOL
[G4 Android Development] steadfasterX:
this depends on the ROM mainly. Do you have changed the ROM or installed an upgrade?

.
[G4 Android Development] brossovitch:
Nope LOS14.1 & LlamaSweet Kernel. It happened after I flashed Official TWRP 3.1.1-0 and then your Beta 3.1.1-0!

Oddly.

I used to have to set my timezone 2hrs behind mine..
[G4 Android Development] kessaras:
i've found a bug for the new beta 1.

I had formatted my system partition to f2fs.

I reboot to recovery with the goal to test if RR can support it too, but RR cannot be flashed without a full wipe.(going from official lineage server to official RR)

I only wipe system and reboot to recovery [i can't afford now a full wipe, maybe i'll test that another day (here is the 1st bug)]

After wiping (rm -rf selected in options) the reboot to recovery command was gone. Instead it did a system reboot.

So i was forced to use the hardware keys to reboot to recovery.

After that, i found my system partition formatted back to ext4 (maybe 2nd bug)

So,

1. the reboot to recovery command after system wipe (rm -rf) failed

2. reboot to recovery with hardware keys , formatted system to ext4

ill send the log after i finish flashing

EDIT:

Maybe rm -rf didn't work and caused all these ?

I'll test that using the cache partition

EDIT2:

added recovery.log

but i don't think it will help here.

i think that rebooting to recovery formats the system to ext4 ,

or it was never formatted to f2fs and it only show f2fs without actually being f2fs.
[G4 Android Development] steadfasterX:
1. ok so the recovery log you send writes the correct time. I guess you pulled it within TWRP when time was working.. Please do again when the time does not work.

2. if you pull out the battery the temp stored time settings get LOST. You need to boot into Android once and then back to TWRP to have the time corrected again. That's the way the RTC handling works here.

1. a factory reset will format nothing when TWRP is in place so yes guessing that the format was not taken place would make sense here

2. pull the log when u have done a format with f2fs

.
[G4 Android Development] kessaras:
i think twrp is fine.

The rom installation after detecting f2fs /system, it changes it to ext4.

1. format to f2fs /system (ok)

2. reboot to recovery and check if it is f2fs (ok)

3. flash rom ( changes /system to ext4 )
[G4 Android Development] owlery_hk:
Thanks for the advice!

I think the time issue must have been due to the temp settings getting lost when I pulled the battery.
[G4 Android Development] steadfasterX:
yea. most ROM's do this when they wipe..

.
[G4 Android Development] steadfasterX:
anyone her wants to test the next official?

http://build.twrp.me/twrp-3.1.1-0-h815.img

it contains all my latest code but build on official server

--> please report back!

It would be also very nice to have testers running still on

LL

..

.
[G4 Android Development] skdubg:
no problems so far

flash, backup, restore (without encryption) works fine
[G4 Android Development] steadfasterX:
Thx for reporting!

I assume you're on MM right?

.
[G4 Android Development] kessaras:
no problem here too. Flashed RR and Llama successfully.

there is no need to report that every day. If i find a bug on my normal use, i'll report it
[G4 Android Development] skdubg:
G4 is on Nougat, DirtyUnicorns

G4c is stock MM (for banking apps) :laugh:
[G4 Android Development] HorstiG:
new Update is a little faster and works great, thank you

H815 RR Lineage 7.12
[G4 Android Development] seetru:
flash, backup, and restore w/o enc on h811 mm - working fine
[G4 Android Development] flatratte82:
I can confirm this. :good:
[G4 Android Development] brossovitch:
So the official DOES have your commits? It is only the H815 version? Or does the H815 version work for H811 also because your commits are unified?

They're labeled h815 and only show version 3.0.2-1 on the TWRP website.
[G4 Android Development] steadfasterX:
The next official WILL have and the build I posted here will be the next official.

The naming of the build will be changed to g4 instead of h815 so yes it works for h811 as well.

I'm not happy with the website situation atm but this will be fixed asap (which can take a while...) to stop confusing the ppl..

.
[G4 Android Development] brossovitch:
Thank you for your continued support!
[G4 Android Development] bananajuice666:
[MENTION=5545101]steadfasterX[/MENTION]

hi,

can you tell me how exactly I do point 6 of the installation-list? Especially regarding flashing the twrp.img onto the recovery partition and not somewhere else?

Will TWRP install the twrp.img automatically onto the recovery partition if I do this in the TWRP-menu: Install>Install Image>select twrp.img ?

Is the installation-process after booting into TWRP to install then TWRP permanently exactly the same as installing an Cyanogenmod/LineageOS-Image?

Or do I have to do something different?

Also if you have time, I would appreciate if you could quickly go through my post in here >>> https://xdaforums.com/g4/help/flashed-twrp-official-factory-reset-t3619970...that's my actual problem regarding TWRP.

thx in advance
[G4 Android Development] raptorddd:
after you send command for twrp.. have a copy of it in sd card.. once the commands sends you to twrp menu hit install. lower part right side says IMAGE click on it so you can browse you twrp.IMG select it then it ask to tick. select recovery. swipe and itll install recovery permanently. thats it.
[G4 Android Development] bananajuice666:
Ah the recovery part is in the end....then I can chose the partition.....thx. But still I got that factory reset menu on my phone which always starts first instead of TWRP. Tried it with the official installation way and still got that factory reset s-hit. The thing is....I have TWRP permanently, but I only get to it with clicking through the original factory reset menu or "adb reboot recovery" in a terminal when it is connected to a computer. I think the installation is done wrong, even if I got no errors till now.

So how do I get that factory reset s-hit out of my phone? ( also and maybe better described here >>> https://xdaforums.com/g4/help/flashed-twrp-official-factory-reset-t3619970 )
[G4 Android Development] raptorddd:
thats how it is. all of us have it.. thats when using physical key combination. itll always show that just click yes. its been like this since the G2.
[G4 Android Development] steadfasterX:
It's a restriction by LG. There is no key combo available in some / all / most LG devices to boot directly into recovery and so TWRP. That's it.

TWRP was compiled in a way that it ignores the factory reset command send by the factory reset screen so it doesn't harm anything.

In theory and on unlocked devices we could change the bootloader and implement a key combo to bypass that screen but it would just mean work with high chances to brick devices and the way it is just works very well.

Another possibility without changing the bootloader would be to implement a key combo in the boot image or even in the system image.

I've implemented such way in several devices but only when I made kernels for it and of course for TWRP in FIsH. Btw the way I use in TWRP in FIsH could be the most easiest one to adapt but I haven't the time to do so atm (especially when there is no real need).

TL; DR

Love it or hate you've done everything right and you have to live with it ;)

(btw the FAQ 12 "How to open twrp?" in post 3 would had answered some parts of your question already at least that you've done it right.. )

.
[G4 Android Development] belrik:
Very helpful, I was wondering why H815 behaved this way!
[G4 Android Development] bananajuice666:
Thanks for the quick answer. And of course also thx to [MENTION=5308112]raptorddd[/MENTION]. The problem is not that I can't live with it, but because there was no note or something to that nowhere I think...I thought "S-hit what have I done" . If there still isn't a note somewhere, it would be nice if you could put one right underneath the installation list and also onto the official TWRP site.

Because some people, who maybe don't react as calm as me and search the internet or ask here, will maybe do something to brick their phone in the panic haste.

Till now I had 5 phones on which I installed TWRP and none of them had anything before TWRP booting if I pressed the right key combo.

But again thanks to you all and don't forget that note...I will come back and inspect your work :D

EDIT: Saw FAQ 12, but this is a little bit vague for me. There should be written, and in that words or similiar, that:

After installing TWRP correctly, you will still have the original LG factory reset screen/menu booting before TWRP, every time. So the correct and only way to get into TWRP is to select two times "Yes" in the official LG factory reset menu, and only then you will get into TWRP. (It's a restriction by LG. There is no key combo available in some / all / most LG devices to boot directly into recovery and so TWRP)

Also I think there should be still a note like this directly underneath the installation-list/-path and on the official TWRP site.
[G4 Android Development] steadfasterX:
I added a note in the installation guide and FAQ.

I will add it to the official site as well.

UPDATE-1

: re-worked TWRP page (merge pending: https://gerrit.twrp.me/#/c/2561/)

UPDATE-2

: merge to official site completed ;)

btw @ all:

v3.1.1 official should go online soon (currently waiting for a fix of a build issue on the official build server)

UPDATE-3:

currently a full renaming is happening in the background (only affects twrp.me website).

This is required for a full unify of the devices and so old dl links may not work (like e.g.: dl.twrp.me/h811).

Keep in mind that it is recommended always to use https://twrp.me and then select the device from the menu list.

and just for completeness: direct links to TWRP images are not allowed in general due to the policy of the teamwin project.

UPDATE-4:

website is now clean and the unification has been completed. if u find anything let me know.

Unfortunately we lost the older h811 TWRP images so if anyone has them pls upload them somewhere and share me the link. I will put them back to the official website then.

.
[G4 Android Development] steadfasterX:
finally the next official version get released :)

note: All new builds will become

twrp-X.x.x-x-

g4

.img

from now on.

That change is due to the unification of both devices (h811 & h815) and so is valid for both.

Unfortunately we lost the older h811 TWRP images so if anyone has them pls upload them somewhere and share me the link. I will put them back to the official website then.

Latest Official release

Release date: 2017-06-15

Download: https://twrp.me/devices

Device Tree changelog: twrp-3.0.2-1 <--> twrp-3.1.1-0 (previous official vs. current official)

TWRP sources changelog: twrp-3.0.2-1 <--> twrp-3.1.1-0 (previous official vs. current official)

Summary

changelog:

LL supported again

Unification of h811 and h815

many bugfixes, speed and other improvements (pls check the above changelog links!)
[G4 Android Development] HorstiG:
Thank you for your work. Vielen Dank für die Arbeit.
[G4 Android Development] steadfasterX:
For you and anyone else using encrypted phones:

I think I've found the bug which is preventing from decrypting in TWRP in newer builds and will release a new fixed BETA soon..

UPDATE:

twrp-3.1.1-BETA-g4-sfXbuild3

Status: stable (it's a BETA though)

Release date: 2017-06-20

Download: Download Page (same download for h811/h815)

Device Tree changelog: previous BETA <--> this BETA

BETA vs. STABLE changelog: this BETA <--> twrp-3.1.1-0

Summary

changelog:

decryption fixed (again) for CM/AOSP

:)

.
[G4 Android Development] kessaras:
link in post #2 for latest beta 3.1.1 is partially wrong. its linking not in your download page to find and download the latest, but at the 3.0.2 beta build.

Great work :)

We can safely encrypt ?
[G4 Android Development] steadfasterX:
omg :) fixed! thx!!

sure as long as you're not using STOCK you can encrypt your device and decrypt with TWRP.

If you encrypt using

CM/AOSP/LOS based ROMs

its fine.

I by myself use encryption on my productive device.

STOCK still cannot be decrypted (as from the beginning).

well TWRP has introduced support for system vold decrypt just some days ago which COULD solve that... but as long as no one wants it i will not dive into that one..

.
[G4 Android Development] maxauvy:
That sounds great! :)

I just got my G4 repaired by LG (motherboard changed due to bootloop issue), I'll test this as soon as I reinstall LOS (I have to re-unlock the bootloader, all that stuff you only do once normally :D ).

Thanks for your hard work!
[G4 Android Development] steadfasterX:
nice!

OT:

... but before you do that: could u make a backup of all partitions maybe?

When it is a H815 EU (only then) then it would be nice if you could follow especially steps 1-3 of this guide: https://xdaforums.com/g4/general/h815eur-bootloader-unlock-relock-guide-t3532331

and provide me the drm, misc and persistent partitions from BEFORE and AFTER unlocking ?

.
[G4 Android Development] kessaras:
[MENTION=5545101]steadfasterX[/MENTION], In Greek , the word "εκαθάριση" is wrong on all TWRPs. It should be "εκκαθάριση" with double k. I corrected it up on crowdin, if anyone can approve it.

I don't know who is the big boss there on crowdin so i just pmed a few twrp official devs :p
[G4 Android Development] steadfasterX:
Never used crowdin but your best option to get an answer is the TWRP channel on IRC as described in the OP..

.
[G4 Android Development] kessaras:
oh, since you don't sync with crowdin, thats better. here it is. get it corrected :p

https://drive.google.com/open?id=0B8NCgGRqIB-EZ21GQUM0MzZZSXM
[G4 Android Development] steadfasterX:
lmao

nice try ;)

no I said YOU have to go to the TWRP irc channel as described in the OP (topic Support) and ask there for the reason why it doesnt get synced to the main code.

EDIT:

tbh I have no idea how the regular process is to upgrade language files ;) thats why I suggest to ask the devs in the IRC (just use the easy web link I provided)..

.
[G4 Android Development] maxauvy:
Sure! ;)

Will you need those files? I can upload them on my nextcloud server if needed, as soon as I take the time to unlock.

Do you want to relock your BL? :D
[G4 Android Development] steadfasterX:
yea that would be really great! :victory: pls

PM

me the link then!

but it is crucial important to have them backed up

before

unlocking

and

afterwards :)

No... its more like .. I wanna try to find out how the unlocking works under the hood.. but dont tell anyone :p - bc ppl go crazy on that issue and I have no idea if I can really get something useful :p

.