yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] kessaras:
yup, i would if it wasnt twrp related.

i flash magisk over RR since a week on my op3T and it doesn't force encryption on me after dirty flashing the rom...

Anyway its all good now.
[G4 Android Development] tqwzUX6fn39GZMEzSnDF:
FYI: Date and time are still correct after flashing newest Lineage OS weekly.
[G4 Android Development] steadfasterX:
thx for givin feedback on this. if it ever occurs again remember the recovery log :)
[G4 Android Development] raptorddd:
official 3.1.00 when you try to reboo from recovery into recovery again it doesnt work.. i have to take battery off and use button combination.
[G4 Android Development] steadfasterX:
To be honest I have to say that the newest version is completely unsupported by me because it is an automatic build and I haven't tested it yet and it does not contain all the changes in my beta version

I have written an email already to remove it from the official website for the moment
[G4 Android Development] gentr:
No problem on H815 to reboot from recovery to recovery.
[G4 Android Development] theviruz:
Where can i find the latest version for h815?
[G4 Android Development] steadfasterX:
Go to tab "Downloads" I uploaded the latest BETA now public

.
[G4 Android Development] XeniX_Force:
Thanks alot for your continuous work
[G4 Android Development] sperelli:
better stay with

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

or update to

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

?

thx a lot
[G4 Android Development] steadfasterX:
twrp-3.0.2-2-h811_h815-steadfasterX-build327_BETA-5.img is tested by many users.

twrp-3.1.0-0_BETA-h811_h815-steadfasterX-build1.img is confirmed to work by 2 users atm.

decide on ur own ;)

.
[G4 Android Development] XeniX_Force:
I can help you Test the new version. What needs to be tested
[G4 Android Development] raptorddd:
ill try latest beta.. i think i had B5 and flashing a rom will end up poping errors as soon as it boots into lg start up wizard.. for h811

thanks
[G4 Android Development] steadfasterX:
Everything you can think of.. ;)

Most important: Backup and restore with a password set would be nice..

This happens when you have incompatible firmware. This new twrp can backup and restore firmware to avoid this.

.
[G4 Android Development] kessaras:
:good:

last time it was a change propably from lineage side that caused me that problem. Dirty flashing forced encryption in my face....

twrp 3.1.x is working until now good. Flashed magisk again earlier on a stock based rom. You need the recovery.log from that ?
[G4 Android Development] steadfasterX:
When it all works no ;)

Thx for givin feedback!
[G4 Android Development] skdubg:
i have tried it with system, data, firmware partiton. backup doesnt work, phone freezes. must remove battery and restart.

the files of the backup are 0 bytes.

where can i find the log for you? (no way to copy to sd from twrp)
[G4 Android Development] kessaras:
don't flash the one in twrp site. ask here for 3.1.0.

its still in beta state but it works flawlessly. he will send you link if you want to test it.

Anyway , always download twrp from here. On all phones, devs do changes and fixes but it takes time to merge with the official , unless the dev is already inside the official twrp group which is rare. For example in op3T we have blu_spark who updates twrp directly on the official server. Very rare.

Always follow xda thread for twrp.
[G4 Android Development] skdubg:
hi kessaras,

i use only the build from steadfasterX, i'm on 3.1.0-0 build1 :p
[G4 Android Development] steadfasterX:
Damn encryption..

adb shell tar czf /tmp/logs.tgz /cache/recovery

adb pull /tmp/logs.tgz

Then upload it to e.g. filedropper.com

.
[G4 Android Development] kessaras:
he used your build ?

i thought he flashed the one from the site sorry.

mention me at least :p i didn't see it. oki.
[G4 Android Development] skdubg:
[MENTION=5545101]steadfasterX[/MENTION]

ok thanks, i do it again and pull it with adb at home later this day
[G4 Android Development] steadfasterX:
He tested a very special setting: set a password for the backup.

This has never worked but I had some hope it may be fixed now.

Skdubg: after your test with the password setting and pulling the logs please also test a normal backup with compression on.

.
[G4 Android Development] skdubg:
partitions:

- boot

- system

- data

- firmware

NO encryption / YES compression

all fine
[G4 Android Development] steadfasterX:
Good now CRASH it again with using enc and pull the logs :D :highfive:
[G4 Android Development] gioxoid:
Any reason why official 3.1 is out for H811 and not for H815?
[G4 Android Development] steadfasterX:
there is no official 3.1 for any of them. I have requested to remove them and they are removed now.

If you want to have 3.1 going official go to the download tab and download the latest beta and test it.

.
[G4 Android Development] gioxoid:
ok, sorry, i didn't notice that h811 was removed.
[G4 Android Development] XeniX_Force:
Edit: Posted on wrong thread. Sorry
[G4 Android Development] mindwarp101:
errors on restoring mm6 backup on beta4

[MENTION=5545101]steadfasterX[/MENTION] issues on beta 4\5 see attached log

https://www.datafilehost.com/d/5f2e2c3d

went from cosmic os 1.4 decided to go back to mm6.0 due to lack of 7.0 app support on gplay market, tried to restore backup.....error!

Hope this helps

Thanks
[G4 Android Development] raptorddd:
beta 31.00 build1 has same bug.. am not sure if its me or the way it suppose to be..

when i do all wipes.. and i want to reboot from recovery into recovery it doenst boot when i do all wipes . it just stays at logo and i can see the blue light on. like its about to boot into o.s but theres none.. happens all the time. it should take me to recovery if i reboot into recovery even if i wipe. inter/cache.dalvik/data. thanks
[G4 Android Development] steadfasterX:
Unfortunately the log is completely damaged/unreadable.. :crying:

So just to be specific:

you created a backup of MM with twrp-3.0.2-2-h811_h815-steadfasterX-build327_BETA-5.img - correct?

then you installed cosmic os 1.4

then you restored your created backup

then you get the error.

Is that all correct?

Can you remember the message you saw?

How do you pulled the logfile? As described in the FAQ in this thread?

thx.

btw: please use the latest BETA from now on because there is an important new feature within (backup & restore of /firmware)

.
[G4 Android Development] mindwarp101:
yeah, created backup of mm6.0 with beta4 recovery

wiped and flashed cosmic os

decided to go back to stock lack of n7 apps, tried to restore backup and failure with that error!

can't remember the exact error fully is was something like extractfolk() didn't have another camera to take a picture, sorry

---------- Post added at 11:31 PM ---------- Previous post was at 11:29 PM ----------

yeah, created backup of mm6.0 with beta4 recovery

wiped and flashed cosmic os

decided to go back to stock lack of n7 apps, tried to restore backup and failure with that error!

can't remember the exact error fully is was something like extractfolk() didn't have another camera to take a picture, sorry

pulled log from within twrp and saved to mSD card
[G4 Android Development] steadfasterX:
I have fixed similar issues a while ago. So this is maybe an issue with that beta. Please upgrade to the latest version and check if this is fixed for you here.

.
[G4 Android Development] xknobi:
twrp-3.0.2-1-h815.img seems to have some problem on the file itself. It is only 16MB big. Others have 31 MB.

Fastboot boot twrp-3.0.2-1-h815.img gives me "remote: dtd not found" error. Others don't have this problem.
[G4 Android Development] steadfasterX:
3.0.0-0 is the latest version supported for devices using LL.

the image has no problem with its size. Read the OP why it is half the size only.

DTB not found means it is not compatible with your bootloader. Use 3.0.0-0 or upgrade the bootloader (means the whole device) to MM (that's why there is [MM] in the thread title).

This is all you can do atm.

Well I could release a LL compatible TWRP 3.1.0-1 as unofficial if you like. That also means: No real support for this then.

.
[G4 Android Development] xknobi:
Sry for not noticing that. :D I will stick with 3.0.0-0 for stock LL. After backup I will flash Nougat and upgrade TWRP as well.
[G4 Android Development] raptorddd:
unofficaol beta.. when you want to turn phone off during twrp. it just reboots phone to LG logo. same for rebot into recovery from recovery. H811 could you please fix.. thank you
[G4 Android Development] kessaras:
hi, any update from your 3.1.0-0_beta1 ?

for me its working fine until now.
[G4 Android Development] steadfasterX:
See above bug report.. . Can you reboot into TWRP from within TWRP?

Im very busy with efidroid and RL which is preventing me from merging to official. I mean it is not that hard but I want to test everything first and this costs so much time...

Before going official I will need testers from the official build server.

...and I wanna test if we can have 1 version for LL and MM as well.

.
[G4 Android Development] gentr:
in h815 this bug not exist, you need to divide in two sections one for h815 and one for h811 for a good test.
[G4 Android Development] steadfasterX:
Thx for reporting but it makes no sense technically. When it works for the h815 it has to work for h811 as well. Is there any other h811 user who can confirm this?

.
[G4 Android Development] kessaras:
i can report the same thing for h815. every important function works.

yea i can reboot to twrp succesfully, i can backup and restore, i can flash anything and i can sideload everything.

The only thing i can't do and i haven't test it in other twrp builds before, is to resize the partitions. I tried to resize /system from 4bg to 3gb but it failed.
[G4 Android Development] raptorddd:
i reported for h811.. maybe i was mistaken.... it does work when theres a rom in it... but question is .. if you do all wipes. and rebot into recovery should it take you to receovery or wiping deletes twrp. it actually doesnt wipe twrp as i can enter using key combination.. so question is is it normal to do all wipes and reboot from recovery into recovery and it would not enter recovery it will take you to LG logo...? like i said if i dont do wipes and using rom it works just fine.:confused:
[G4 Android Development] maxauvy:
Hi there,

just tried the 3.1.0-0 beta, but decryption seems to be broken atm. Using LineageOS 14.1 (25/04/2017 build). TWRP returns a wrong password (event if it's the good one ;) ). Decryption was working before, with the last beta5 build.

Is it a known issue?
[G4 Android Development] steadfasterX:
No you are the first reporting this.. With what ROM do you have encrypted the device? LOS14.1? Do you remember when or which exact build it was? I may have to check if they changed the implementation or something..

..and please provide LOGs! Read the FAQ because I need both dmesg and recovery log

.
[G4 Android Development] maxauvy:
I first encrypted my phone with CyanogenMod 14.1 I think, but I really don't remember which build. I switched to LOS14.1 at the beginning of the official nightlies.

To give you an approximative idea of when I encrypted the phone: it was a few weeks after you added decryption support to TWRP ;)

I'll catch you the logs and dmesg you're asking for :)

EDIT : [MENTION=5545101]steadfasterX[/MENTION] as I can't mount /data/media (encrypted), how am I supposed to get a log? The "copy log" button can't write anything on disk, and adb says my device is offline...
[G4 Android Development] Folloxme:
waiting for 815p bootloader unlock :(
[G4 Android Development] XeniX_Force:
You should instead try fish
[G4 Android Development] steadfasterX:
thanks.

when adb shows offline try to plug off USB cable wait a sec and plug it in again.

if that doesn't work try to disable MTP and enable MTP again (this has nothing to do with MTP but it triggers adb like USB cable connect)

then continue waiting .. or:

http://tinyurl.com/TWRPinFIsHG4

.
[G4 Android Development] steadfasterX:
start in TWRP and try to decrypt for generating the logs

then:

disconnect USB cable

connect again

adb should work now

If that doesn't work use this workaround:

disable MTP

then enable MTP again

adb should work now

EDIT:

oops I wrote the same above ;) sorry for bothering ;)

.
[G4 Android Development] maxauvy:
Sorry for the delay, I was out of home for a few days, without my laptop. Had to setup ADB on my work laptop, that was such a pain in the... butt. Alright then.

recovery.log

dmesg.log

I had to disable/enable MTP, otherwise adb would not start on TWRP.

As adb is installed at work now, please ask if you need something else, I should be able to answer more quickly ;)

EDIT : I had something "similar" with LlamaSweetKernel last update (R7.2-N), pre-boot password wasn't recognised. It was due to SELinux in enforcing mode. This was fixed in LOS, but this may be a clue for you. The commit is here.
[G4 Android Development] XeniX_Force:
before [MENTION=5545101]steadfasterX[/MENTION] says it, I'm gonna say it. adb problems are a p.i.a we all know. so use FWUL.
[G4 Android Development] maxauvy:
Yeah but that's not the point here, I use Linux at home and adb is set properly without any issue. The problem was to set up adb on my professional laptop (Windows 7 :mad: can't change and that drives me crazy), without the use of any VM (disabled in the BIOS by douchy netadmins), so [MENTION=5545101]steadfasterX[/MENTION] won't have to wait for me to come back at home.

BTW I'm not sure posts that says "use Linux instead of Windows" without adding any value to the point discussed here are very useful, as I already provided the logs.
[G4 Android Development] steadfasterX:
thanks I will look into it asap and regarding the llama commit: great finding! :) We will see if that is the cause. At least we have a permission denied so maybe it is really related..

What he meant was using FWUL had maybe saved u some hours.

FWUL does not need to run in a VM necessarily. You can use it from DVD/CD/USB without touching your OS so u can just boot it and have everything in place (when your paranoid admin has not blocked booting from CD/USB in BIOS as well.... :p )

.
[G4 Android Development] XeniX_Force:
yes i meant that. :laugh:
[G4 Android Development] maxauvy:
Yeah, I watched the logs I gave you, that's why I linked this commit. I like to contribute to LOS or LlamaSweet when I can, so I know some of the issues quite well ;)

Hope that's the same thing, this was easy to fix in some way.

Yeah I understand. This Windows thingy didn't took hours, but everything always seems complicated compared to my Linux PC, thus I delayed this, like "I'd rather wait to come home", but I have to stay a few days more elsewhere, so... ADB over Windows. :rolleyes:

Nah, I cant' boot from any USB drive, that would have been too simple ;)

I work for the French data protection authority as IT auditor (investigations dept), so even if we have admin rights on our laptops, the BIOS is protected, the whole HDD is encrypted and the software used asks (like my Android :P ) for pre-boot auth, blah blah... Just in case I forgot my laptop in a train or someone wants to steal it. May seem a bit overkill, but "required by law" so I have to deal with it (and cry a lot each time I want to use Linux cmd utilities).

Off topic apart, if I can help you with anything, just ask :good:
[G4 Android Development] XeniX_Force:
well that's music to my ears

so when you are free, can you please help [MENTION=5545101]steadfasterX[/MENTION] with this:

https://xdaforums.com/g4/development/g4-efidroid-lg-g4-t3589487

he is working real hard to get it working but had to testers currently.

thanks alot
[G4 Android Development] maxauvy:
I'll read this thread but at first glance it seems that Google Play Store is needed, and I don't have Google Apps installed along with my LOS14.1. I may install this from Yalp Store, but I hope that the app does not rely on anything related to Play Services, GCM, Firebase... ;)
[G4 Android Development] HorstiG:
Thanks again, tonight I'll test.
[G4 Android Development] steadfasterX:
cool . take a nandroid backup before actually doing anything else - just to be sure :) !!

but better: come into the IRC before starting and we can it do step by step.

I will be online today at about 21:00 our time latest

.
[G4 Android Development] bergbock:
Hi,

first of all: thanks for your release, steadfasterX!

I just flashed your TWRP version because I hit the trap, that you cannot encrypt the phone when rooted. The method in the article did not work for me, so I had to unroot the phone to encrypt it :( --> done!

Now I hoped that your TWRP can decrypt the storage to flash a superSU again. But unfortunately no luck: after entering the PIN in TWRP it says "Password failed/failed to decrypt data" :(

My h815 is on stock rom with 20d kernel.

Edit: Finally I was able to reinstall superSu with this instruction.
[G4 Android Development] steadfasterX:
So you still cannot decrypt right?

You're on stock but which version? Lollipop??

Please provide the recovery.log and a dmesg

You need adb for this:

Connect your USB cable

Start twrp

Try to decrypt

Then:

adb shell

dmesg > /tmp/dmesg.log

exit

adb pull /tmp/recovery.log

adb pull /tmp/dmesg.log

Then open both files with wordpad and copy and paste each of it to pastebin or similar.

Thx

steadfasterX

.
[G4 Android Development] bergbock:
Hi,

I'm on Marshmallow 6.0.

Logs collected at pastbin. Sent you a PM.

Thanks!
[G4 Android Development] steadfasterX:
Got it thx. I took a short look over it and I saw an error with qseecomd which exits unexpectedly. That service is needed to decrypt so it is the reason why it doesn't work for you. At least one reason (there are maybe others as well).

Please paste the output of the following command while in twrp:

ls -la /dev/block | grep boot

Do you have encrypted in marshmallow or encrypted in lollipop and upgraded to MM?

Then another thing to try is when booted into twrp cancel the decryption dialog and go-to mount menu. Mount system. Then try to decrypt again.

Then paste the recovery.log and dmesg again..

Thx

.
[G4 Android Development] bergbock:
* I did a clean install of this TWRP zip (Marshmallow).

* Uninstalled superSU, because was not able to encrypt rooted phone (even when daemonsu killed)

* encrypted phone

* re-installed superSU from SD card

I collected the new logs and sent you a PM to pastebin page.

Thanks
[G4 Android Development] steadfasterX:
Great thx.

Please pull also the following log:

adb pull /tmp/createsym.sh.log

I believe best support will be possible over irc only. for this check the OP --> Support

what is your timezone? Normally we can find a good time range to meet there so let me know.

Thx

.
[G4 Android Development] bergbock:
My timezone is Germany (CEST), as yours I believe ;)
[G4 Android Development] steadfasterX:
okay check your personal messages :good:
[G4 Android Development] Aldideos:
Hi, I have the imperium rom. my time in TWRP is not correct, is there a way to fix it or not?.

However I want to know if it iss possible to use this twrp versione with encrypted lg g4 with knock code. Thanks
[G4 Android Development] steadfasterX:
Hi

Regarding the time issue: I have added a new FAQ entry for this.

Checkout FAQ #6 :

http://xdaforums.com/showpost.php?p=68249027&postcount=3

I dunno about the knock code.. Sorry. Do you have tested it?

Cheers

.
[G4 Android Development] Aldideos:
No I haven't... However I think that it is not compatible with the knock code because in my opinion the twrp can't ask me the code to decrypt...

Regarding the time issue it is Rom related, as I understood a stock based rom has not the timekeep so no possibility to have real time, right?

Thank you
[G4 Android Development] steadfasterX:
Well check it:

While your android is running connect an USB cable and execute on your pc (check FAQ 3 on the first page):

adb shell ls -la /system/bin/timekeep

adb shell ls -la /system/bin/time_daemon

If one of the above is working you will have good chances that I can fix the time issue. Let me know what the result of the above is

.
[G4 Android Development] Aldideos:
This is my output :
[G4 Android Development] steadfasterX:
Looks good so far. You have the proprietary time_daemon running so it should had worked without any mods in twrp....

Could you also give me the following output:

adb shell

su

ls -la /data/time

ls -la /data/system/time

Then reboot and shortly afterwards (if you waiting too long the buffer will be overwritten so do it just after it completely booted):

adb shell

dmesg | egrep -i "(rtc|restored|time_daemon)"

Then:

boot into twrp and then collect the logs as described in my FAQ #4 on the 3rd post of this thread.

That one should hopefully tell us why the time is not detected for you.

It may be necessary that you install a special twrp version with enabled debugging. I will provide if necessary after you collected the logs as described.

.
[G4 Android Development] Aldideos:
root@p1:/ # ls -la /data/time
-rw------- system net_raw 8 2016-08-30 10:30 ats_1
-rw------- system net_raw 8 2016-08-29 23:58 ats_12
-rw------- system net_raw 8 2016-08-29 23:58 ats_13
-rw------- system net_raw 8 2016-08-30 10:30 ats_2

root@p1:/ # ls -la /data/system/time
/data/system/time: No such file or directory

I made this command via terminal emulator and it has some outgoing. Buut now it hasn't both in adb and in terminal. I don't know why...

shell@p1:/ $ dmesg | egrep -i "(rtc|restored|time_daemon)"
[ 0.000000 / 01-01 00:00:00.000][0] Linux version 3.10.84-Imperium-Kernel-G4-v4.4 (slim80@slim80-System-Product-Name) (gcc version 4.9.4 20160401 (optimized) (UBERTC-4.9.4) ) #1 SMP PREEMPT Fri Aug 12 12:59:25 CEST 2016
[ 0.927189 / 01-01 00:00:00.920][4] qcom,qpnp-rtc qpnp-rtc-ffffffc0c49a0c00: rtc core: registered qpnp_rtc as rtc0
[ 2.060924 / 03-15 17:35:59.500][5] qcom,qpnp-rtc qpnp-rtc-ffffffc0c49a0c00: setting system clock to 2015-03-15 17:35:59 UTC (1426440959)
[ 3.824068 / 03-15 17:36:01.260][5] init: Warning! Service time_daemon needs a SELinux domain defined; please fix!
[ 3.824096 / 03-15 17:36:01.260][5] init: Starting service 'time_daemon'...
[ 40.089770 / 08-30 10:34:22.663][2] FUSE: SHORTCIRCUIT enabled [sdcard : 3217]!
[ 40.089847 / 08-30 10:34:22.663][0] FUSE: SHORTCIRCUIT enabled [sdcard : 3216]!
[ 40.091803 / 08-30 10:34:22.663][0] FUSE: SHORTCIRCUIT enabled [sdcard : 3218]!
[ 43.120782 / 08-30 10:34:25.693][0] FUSE: SHORTCIRCUIT enabled [sdcard : 3975]!
[ 43.120821 / 08-30 10:34:25.693][0] FUSE: SHORTCIRCUIT enabled [sdcard : 3976]!
[ 43.124528 / 08-30 10:34:25.697][2] FUSE: SHORTCIRCUIT enabled [sdcard : 3977]!

createsym.sh

dmesg

recovery
[G4 Android Development] steadfasterX:
Ok so

your time daemon seems to work well in ROM in a manner TWRP should be able to read

TWRP tries to restore the time and had success with that

When I say "success" it means the time gets read and restored but it is obviously not correct

Please tell me Is you device encrypted?

.
[G4 Android Development] Aldideos:
No, I want first to solve this problem and think what to use between pattern and password because now I used knock code as block. Thanks
[G4 Android Development] steadfasterX:
GOOD NEWS

for those running CM or CM based ROMs :)

I was able to fix the time issue (hopefully or let me say: at least for me).

I need some testers! Whoever has a CM based ROM and wanting to test that time fix version send me a PM and I give you the dl link

Regarding the stock roms:

I will check that next...

Cheers

steadfasterX

.
[G4 Android Development] kessaras:
ofc it is. it need core services.

1. it needs to sync to an account.

2. it needs feedback service.

3. to sync you need the other core services. So.....

no play store without gapps :D

EDIT:

but efidroid is not related if you need to know about that.
[G4 Android Development] XeniX_Force:
you can side load the app. i don't think it relies on anything related to play services.