yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] steadfasterX:
ok dudes pls try the latest BETA (sfx-7) in the download section :)

[MENTION=5461026]kessaras[/MENTION] as well (your test is just to be sure STOCK is STILL working after my changes ;) )

after flashing the new TWRP version just boot into it and

pull the recovery log

and attach it in your answer.

this new version is almost all about time. I have integrated a detection for the ROM type (stock or custom) and depending on that any unneeded files get automatically deleted now!

That means even when switching between STOCK and custom ROMs no further actions are required anymore (means: FAQ #6 - Why is the time wrong in TWRP? will be obsolete then).

The other change made is that I renamed the BL stack test to Bootloader. The tests have shown that at least the backup is working good so far.

oh btw [MENTION=5461026]kessaras[/MENTION] : could you please re-do a backup of the "Bootloader" in TWRP (only this) and then attach the recovery.log ?

You can skip the above time related request as when I have 1 recovery log from you with that new TWRP version is enough :)

also do a sha256sum again:

adb shell

sha256sum /dev/block/bootdevice/by-name/drm

thx for all your time ;) and effort!

.
[G4 Android Development] kessaras:
deleted.

xda propably was updating something and my posts were not posted for some time
[G4 Android Development] kessaras:
adb shell

sha256sum /dev/block/bootdevice/by-name/drm~ # sha256sum /dev/block/bootdevice/by-name/drm

adb67f75fe5d17ff404448ec069a540157c5baf4b2c34d74ccdd156e41afb552 /dev/block/bootdevice/by-name/drm

time is broken now.

flashed twrp in bootloader and boot directly to twrp.

took logs b4 reboot to system and after.
[G4 Android Development] steadfasterX:
oh yes my fault.. this will break the time really for STOCK lol.. gimme a mom to fix..

EDIT

please tell me the output of (while in TWRP)

adb shell

sha256sum /data/media/0/TWRP/BACKUPS/LGH81510a0c098/2015-01-09--17-34-00_NRD90U/drm.emmc.win

ty

.
[G4 Android Development] kessaras:
adb shell

sha256sum /data/media/0/TWRP/BACKUPS/LGH81510a0c098/2015-01-09--17-34-00_NRD90U/drm.emmc.win~ # sha256sum /data/media/0/TWRP/BACKUPS/LGH81510a0c098/2015-01-09--17-34-00_NRD

90U/drm.emmc.win

adb67f75fe5d17ff404448ec069a540157c5baf4b2c34d74ccdd156e41afb552 /data/media/0/TWRP/BACKUPS/LGH81510a0c098/2015-01-09--17-34-00_NRD90U/drm.emmc.win
[G4 Android Development] steadfasterX:
ok perfect! ty
[G4 Android Development] steadfasterX:
ok this one is just for u ;) its an experimental build so I will attach it here only. Its a complete new method so i expect that it may not work yet..

flash and boot into it.

pull the recovery log and attach

thx!

--- attachment removed

.
[G4 Android Development] kessaras:
time is still 6.30 hours ahead
[G4 Android Development] steadfasterX:
hm do u have ensure that you have correct time in Android ? It must be correct first then boot into TWRP..

.
[G4 Android Development] kessaras:
Ofc time is on auto always
[G4 Android Development] steadfasterX:
yea I see..

could you pls do this in running Android?

adb shell

su

ls -la /data/time/

ls -la /data/system/time/

grep ro.build.flavor /system/build.prop

grep "ro.build.flavor" /system/build.prop

pls paste the console output

.
[G4 Android Development] kessaras:
ls -la /data/time/

total 48

drwx------ 2 system system 4096 2015-01-09 20:05 .

drwxrwx--x 56 system system 4096 2015-01-09 13:56 ..

-rw------- 1 system net_raw 8 2017-08-29 13:28 ats_1

-rw------- 1 system net_raw 8 2017-08-29 13:53 ats_12

-rw------- 1 system net_raw 8 2017-08-29 13:53 ats_13

p1:/ #

p1:/ # ls -la /data/system/time/

ls: /data/system/time/: No such file or directory

1|p1:/ #

1|p1:/ # grep ro.build.flavor /system/build.prop

ro.build.flavor=p1_global_com-user

p1:/ #

p1:/ # grep "ro.build.flavor" /system/build.prop

ro.build.flavor=p1_global_com-user

You are looking for /data/time/ ?

But I can't cat the time its decrypted.
[G4 Android Development] steadfasterX:
interesting stuff..

that has changed.. dunno if thats new on (stock) nougat tbh.. but before we only had /data/time/ats_1 and ats_2

no u cant read them easily (afaik) but they contain the offset to the RTC (command: hwclock -r ) in milliseconds.

ok thx i will release a new testing build soon

EDIT:

[MENTION=5461026]kessaras[/MENTION]

here we go (see attached experimental build)

aus usual: flash it, reboot into twrp again, pull recovery log and attach it..

thx

--- attachment removed

.

.
[G4 Android Development] kessaras:
great ! this time the time is correct , here is .log
[G4 Android Development] steadfasterX:
yea that was expected -- nevertheless it still is not how I need it unfortunately..

the rom type detection still failing. I have just a fallback to STOCK thats why it works for you atm..

btw: check the cmdline in TWRP as well:

adb shell

cat /proc/cmdline

I added max cpus 5 ;)

pls do as usual (flash it, reboot into twrp again, pull recovery log and attach it..) with this attached twrp version..

thx

.

--- attachment removed

.
[G4 Android Development] kessaras:
boot_cpus=0,1,2,3,4,5 sched_enable_hmp=1 sched_enable_power_aware=0 maxcpus=5 console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 msm_rtb.filter=0x37 androidboot.hardware=p1 androidboot.selinux=permissive lge.rev=rev_10 model.name=LG-H815 lge.sim_num=1 lge.battid=SW3800_VC1 lge.bootreason=Recovery_mode maxcpus boot_cpus=0-3 kswitch cc_mode=0 androidboot.bl_unlock_complete=true androidboot.dlcomplete=0 gpt bootcable.type=400MA androidboot.ddr_size=3221225472 androidboot.ddr_info=0x3b000206 fakebattery=disable lge.bootreasoncode=0x77665502 lge.hreset=off lge.dsds=none androidboot.revision=11 fips_allow_others=1 fips_panic=0 fips=0 lge.signed_image=false androidboot.bootdevice=f9824900.sdhci androidboot.serialno=LGH81510a0c098 gpt androidboot.authorized_kernel=true lge.signed_image=true lge.dsv_id=DW androidboot.baseband=msm mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_jdi_nt36850_1440p_mipi0_cmd:1:qcom,mdss_dsi_jdi_nt36850_1440p_mipi1_cmd

you forgot to delete the boot_cpus afterwards and maxcpus is without value !

also i see 1440. maybe if we test to lower that and change the dpi to match the screen again , it would lag less ? (its just an idea cause it lags a lot after upgrading to 7)

EDIT:

its ok now i cleaned the cmd line [MENTION=5545101]steadfasterX[/MENTION]. it was mine conficling there
[G4 Android Development] steadfasterX:
no check

boot_cpus=0,1,2,3,4,5 sched_enable_hmp=1 sched_enable_power_aware=0 maxcpus=5

this comes before the other one and so wins ;)

I dont care about boot_cpus for TWRP. its really not needed there..

whats that 1440 value about?

.
[G4 Android Development] kessaras:
1440 is the resolution

see previous post. cmdline is ok. cleaned mine
[G4 Android Development] steadfasterX:
regarding the lagging we need to check this later.

lets fix that time issue first..

sorry for bothering you that much..

usually i do this all alone on my device but.. as I cant atm..

attached a new version.. pls do as usual..

many thx

--- attachment removed

.
[G4 Android Development] kessaras:
its not a problem

time is fine again
[G4 Android Development] steadfasterX:
f**** yes! thats what I expected.. finally. thanks again :)

.
[G4 Android Development] tqwzUX6fn39GZMEzSnDF:
I'd like to support you, but I don't have any free time at the moment. So the only I can do is to say "Thank you very much" to kessaras (and steadfasterX of course!).
[G4 Android Development] DarrenNewsgroup:
I was thinking this as well while reading the dialog between SteadfasterX and Kessaras.

Keep up the good work the pair of you. We appreciate your efforts. I've clicked the thanks buttons on your posts.
[G4 Android Development] steadfasterX:
Giving thx clicks is fully enough and much appreciated ! This is also kind of support for us so just continue this way and one day if you want to do more... you are free to do it and until then just click ;)

[MENTION=6219132]ufocus[/MENTION] and [MENTION=7321996]crysknife4life[/MENTION]

please could you test the latest build sfx-12 for me? flash, boot into that TWRP version, pull the recovery log and attach in your response..

@ anyone else:

I would also like to have more testers from other ROMs, STOCK or not.. doesnt matters. just do this:

flash, boot into that TWRP version, pull the recovery log (FAQ #4 - A) and attach this plus your ROM name / version in your response..

If you do not trust a BETA release just do a: fastboot boot twrp.img (replace twrp.img with the real name) and do the above steps. This will not install TWRP - just boot it once :)

.
[G4 Android Development] kessaras:
fastboot boot <recovery.img>

doesn't work anymore on N bootloader.

Guys, it's ok to trust the beta sfx 12 i'm using it since yesterday without any problem.
[G4 Android Development] ufocus:
I confirm that TWRP time is correct with beta-12. Using crDroid v3.7 and for good measure i tried stock nougat rom (H-ROM G6 Port) too and it's correct also. Thank you!

[MENTION=5545101]steadfasterX[/MENTION]
[G4 Android Development] SavageRobot:
OT (slightly);

I'm want to help and flashed the v8 beta yesterday but noticed that when I went to open cmd in the sdk path it was gone, instead there is powershell and it doesn't seem to recognise adb commands. Can I use adb in powershell do you know? Think it must have replaced the availability of cmd there in a recent update as it used to be there shift and right click.

Can't run cmd as administrator as a work laptop and have shut off admin rights.

PS C:\sdk-tools> adb devices
adb : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ adb devices
+ ~~~
+ CategoryInfo : ObjectNotFound: (adb:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

Suggestion [3,General]: The command adb was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\adb". See "get-help about_Command_Precedence" for more details.
PS C:\sdk-tools>
[G4 Android Development] steadfasterX:
thx for trying to help!

well if you are allowed to use USB sticks or when you have Virtualbox installed.. consider using FWUL ;)

otherwise i cant help you with this. pls open a new thread in the help area ..

.
[G4 Android Development] steadfasterX:
awesome!

and many thanks for trying even both..!!

This way i was able to verify that the process of deleting the unneeded files works well as well :)

.
[G4 Android Development] obvious:
'Stock' nougat recovery log :)
[G4 Android Development] stefan.kurz:
Hi,

I need same advice. I'm now on imperium 14.1, a Stock based (v20p) Rom. Twrp is installed the latest stable build (3.1.1- 1). I would like to test some Nougat Rom (Freedom v6 or H Rom) and have a few questions:

Which twrp must be installed to restore a backup if i wanna go back?

Is the latest beta twrp (v12) reliable?

I'm on vacation till end of next week without pc or laptop. So if i make mistakes i'm not able to use lgup for flashing a kdz. I know i'm a bit of a nerd/freak to do this on Holiday...
[G4 Android Development] steadfasterX:
this requires the latest BETA build (sfx-12 or higher)

the latest BETA is reliable for backup&restore in general but it contains a brand new feature which includes the bootloader stack for backup & restore - which is amazing - but no one has tested it yet.

Read and follow this announcement https://xdaforums.com/g4/developmen...h-recovery-t3442424/post73493567#post73493567

After you finished the DLM Backup push all image files from that backup on your phone's external sdcard. this would be your bulletproof backup as long as u do not shoot urself in the head (e.g. locking the device, erasing TWRP,...)

Then download the latest TWRP BETA and push it to your external SD as well.

Install that beta TWRP image and then create a full TWRP backup as described in the announcement I linked you above.

When it comes to restore to a previous bootloader (so MM in your case) use that BETA TWRP first. ensure u select Bootloader, firmware and EFS besides the other stuff.

.
[G4 Android Development] stefan.kurz:
Is the DLM Backup useable without a pc? The twrp stuff is no Problem. I have a sd card but no usb device. So i have to wait until i'm back at home? Thx for your advice.
[G4 Android Development] kessaras:
stef after you flash latest beta 12 , download the firmware v29a (modem and bootloader) , download the rom, boot into twrp and ONLY wipe /data partition. Since you are on vacation you have to predict a possible download error, connection error, corrupted .zip , possible mistake to clean/wipe everything along with the sdcard (so your downloads will be deleted too).

so then wipe ONLY /data -> advance wipe /data ,

flash firmware, flash rom, reboot. you are good now.

and of course keeping a backup of the rom is useless unless you have also downloaded v20p firmware. You will not be able to restore to MM rom without MM firmware mate.

Thats all.

EDIT:

yeah beta 12 can backup bootloader too, but since it's not tested if it restores successfully (at least not tested by any users yet) its good for pre-caution to also download v20p firmware and keep it in your external sd as instructed to do with the rest of the backup
[G4 Android Development] SavageRobot:
Not sure what you need now, got PS working (would have helped if I read the error properly)

PS C:\sdk-tools> .\adb shell
~ # ^[[2;5Rgetprop | grep -i build
getprop | grep -i build
[ro.bootimage.build.date.utc]: [1504019905]
[ro.bootimage.build.date]: [Tue Aug 29 15:18:25 UTC 2017]
[ro.bootimage.build.fingerprint]: [lge/omni_g4/g4:6.0.1/MOB31K/steadfasterX08291517:eng/test-keys]
[ro.build.characteristics]: [default]
[ro.build.date.utc]: [0]
[ro.build.date]: [Tue Aug 29 15:18:11 UTC 2017]
[ro.build.display.id]: [omni_g4-eng 6.0.1 MOB31K eng.steadfasterX.20170829.151544 test-keys]
[ro.build.flavor]: [omni_g4-eng]
[ro.build.host]: [droiddev]
[ro.build.id]: [MOB31K]
[ro.build.product]: [h815]
[ro.build.tags]: [test-keys]
[ro.build.type]: [eng]
[ro.build.user]: [steadfasterX]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.base_os]: []
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [eng.steadfasterX.20170829.151544]
[ro.build.version.preview_sdk]: []
[ro.build.version.release]: [6.0.1]
[ro.build.version.sdk]: [23]
[ro.build.version.security_patch]: [2016-11-05]
~ # ^[[26;5Rgetprop | grep -i version
getprop | grep -i version
[ro.build.version.all_codenames]: [REL]
[ro.build.version.base_os]: []
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [eng.steadfasterX.20170829.151544]
[ro.build.version.preview_sdk]: []
[ro.build.version.release]: [6.0.1]
[ro.build.version.sdk]: [23]
[ro.build.version.security_patch]: [2016-11-05]
[ro.modversion]: [OmniROM-6.0.1-20170829-g4-HOMEMADE]
[ro.omni.version]: [6.0.1-20170829-g4-HOMEMADE]
[ro.twrp.version]: [3.1.1-beta_sfx-12]
~ # ^[[39;5R
[G4 Android Development] stefan.kurz:
Thx man. If you were me, would you do it or wait till you were at home?
[G4 Android Development] steadfasterX:
no DLM Backup requires a PC. I thought u are not on the vacation yet :p

either wait until someone tests the restore

be brave and be the first one trying the TWRP bootloader restore - with the risk havin an unusable device

or wait until u are at home at least for a possibly restore

hey kessaras :) what do u think about announcement -> "... and I need also brave testers to try the restore...

" ;) the newest BETAs are able to restore the bootloader stack without having any firmware ! just by a TWRP backup.. as long as it is untested we cannot say if it works as I wish though..

pls read the announcement regarding

time

.
[G4 Android Development] gentr:
Clock and in last beta 12 is not correct
[G4 Android Development] steadfasterX:
boot into TWRP and pull the revovery.log (FAQ #4 A). attach it to your response

.
[G4 Android Development] kessaras:
nah, no big deal. having downloaded everything i need

1. v20p firmware

2. v29A firmware

3. Freedom (example)

And having a full backup , i need not to worry.

Even if i accidentaly delete my downloads by having backup i can restore /data and login and re-download.

Even if the install fail i can try again.

Even if i don't like nougat, i can still use full restore with bootloader and if the bootloader doesn't get restored, i can still use hardware combo to log in TWRP and flash 20p firmware ! ;)

looool, yeah no problem. i can flash 20p firmware and try restore to v29A ;)

little later !
[G4 Android Development] gentr:
Ok
[G4 Android Development] steadfasterX:
thx. hm ok. can you tell me: what ROM are u using? I assume its on Lollipop?

.
[G4 Android Development] gentr:
H-rom nougat G6 full port
[G4 Android Development] SavageRobot:
Time & Date correct recovery.log

CRDroid 3.7 (7.1.2) not encrypted.

recovery

dmesg
[G4 Android Development] stefan.kurz:
I have all downloaded. Now i read that it is possible, that i can't activate whatsapp cause i'm abroad... It's like hell
[G4 Android Development] kessaras:
[MENTION=5545101]steadfasterX[/MENTION] , cheers !

Bootloader restore works and i boot fine.

But no signal , we forgot the modem partition backup too, otherwise its useless to only restore bootloader :cyclops:

People will need a wifi hotspot or router to download modem and flash it to have signal. Those coming from MM at least.

Attached recovery.log , with digest verification working too. Just in case you want to see it.

Add pp if= ...modem.img of= ..../modem and it will be perfect !
[G4 Android Development] steadfasterX:
great !

no no i said in the announcement backup ALL (including firmware partition!)

on restore yes you have to select modem partition as well !

Firmware = modem ;)

.
[G4 Android Development] kessaras:
I didn't read it xD

The others are from older twrp so I thought they r tested. Pffff going there now...

EDIT: [MENTION=5545101]steadfasterX[/MENTION], here it is.

flashed whole modem bl h811 20v .

So from 20v restored to h815 29a , everything works
[G4 Android Development] steadfasterX:
hahahaha awesome ! :)

thx dude f**** appreciated really!

.
[G4 Android Development] steadfasterX:
hi gentr,

u need to set the correct time zone once in TWRP.

then reboot back to TWRP and it should be still correct.

This has been verified with [MENTION=6917540]Astrako[/MENTION] on the ROM you're using (many thx again)

.
[G4 Android Development] stefan.kurz:
I installed the latest beta of twrp. If i wanna make a backup the phone crash. I must take the battery out and put it back in. Then i can restart my phone.

Can i flash the latrst stable build again?
[G4 Android Development] crysknife4life:
Well, for me the time/date in the Beta 12 is wrong again. Beta 8 worked.
[G4 Android Development] steadfasterX:
it doesnt crash. its just unresponsive while doing the backup (on my todo list). just be patient.. it will recover!

a nightmare.. :p i will check ur logs asap

EDIT: [MENTION=7321996]crysknife4life[/MENTION]

could u pls try the attached one? Thats a debug build which means it will just give me more log output in the recovery log.

just boot into it and pull the log no need to do anything else

.
[G4 Android Development] stefan.kurz:
Should i install v13 too. It's only 15.6 mb. V12 has 33 mb.
[G4 Android Development] raptorddd:
hope i catch right recovery

time its 1 hour ahead.

port h811 N rom.
[G4 Android Development] kessaras:
no its ok with 12 for now to do what you wanna do. they test time on different roms. to fix the time.

When you are back from vacation yes update with all and help with TWRP too xD
[G4 Android Development] crysknife4life:
Here my log. Btw. Is the time in 13 correct again. Did you change something from 12?
[G4 Android Development] steadfasterX:
Please try to set the correct timezone and reboot into TWRP again.

No. V13 is just a debug build. And the reduced size is because I zipped it ;)

Thx.

Nothing meaningful changed. It's just a debug build..

I believe it depends on how you boot into TWRP. Try it from TWRP to recovery and also try from android to TWRP to see if there is a diff..

When you got the situation again pull the recovery log.

.
[G4 Android Development] kessaras:
[MENTION=5545101]steadfasterX[/MENTION] restore works fine for bootloader but you skipped some partitions that write the pre-boot splash.

i think thats for the better. i hated that crap splash with that huge message to re-lock. its better with simple orange font
[G4 Android Development] steadfasterX:
Hm... Interesting.. Could you describe in more detail what you see / do not see?

Is the device still unlocked?

You restored the bl unlock state in TWRP, too?

.
[G4 Android Development] kessaras:
Yup I restored everything.

The device is still unlocked.

What is see is only the letters just like before.

Did you only backup aboot ?

One of the bootloader partitions has a splash image (which people hate it btw).

Normally the nougat bootloader has (big full screen image) big fancy fonts and icons and some advertisment to visit a site.

Now I only have the letters that say the bootloader is unlocked and to relock it. Only letters. That's better.... No need to flash other crap since only aboot is important

< and OT >

By the way lol. Just lol.

https://www.xda-developers.com/google-android-p-android-9-0-aosp/

Hahaha what's that? Maybe they want to add better api to go against iOS after they saw the wireless charging and the better camera face unlock ?

2nd EDIT:

lucky bas....ds that bought a 2017 brand with nougat they gonna get 3 major updates in 2 years of support (if they have support) haha and here we pray for 1
[G4 Android Development] steadfasterX:
oooh that one!

great .. finding a "fix" by accident.. but serious yes. its due to a partition which is not in the backup but which is not important for the restore itself.

When cou can give me a picture of the "bad"/unwanted screen u see on N i assume can fix that screen for all.

Not sure but I think you know that im working on the unofficial unlock and so I can say that im very experienced now when it comes to the partitions of the g4 ;)

You would be scared what I have tried and done already with my g4 which is far far ahead from what an advanced user would do ;)

so i can say: no just backing up aboot is not enough. the bootloader stack contains other important partitions as well like sbl1, rpm, tz and such. U need them .. believe me. :angel:

.
[G4 Android Development] kessaras:
Didn't you notice a 30mb around difference in size? :)

They added full screen splash with crap.

1st without splash.

2nd with splash
[G4 Android Development] steadfasterX:
thats going too much OT so... lets see where this goes: https://xdaforums.com/g4/development/poc-disable-n-text-one-t3665683

;)

.
[G4 Android Development] stefan.kurz:
The Backup was ok. Thx for helping. If i wanna restore the mm rom backup, should i restore the bl unlocked too? Or only if i get the info that the bl is locked?
[G4 Android Development] MadcapCries:
Hello stead

I'm using the stock european Rom, sorry to inform you that I was not able to decrypt my phone.

But i'm here also for testing, so let me help you.
[G4 Android Development] steadfasterX:
great check your PM ;)
[G4 Android Development] popy2006:
thx [MENTION=5545101]steadfasterX[/MENTION] for your work to fix the time issue at least for cm13.

It works flawlessly with build 127!!

pOpY
[G4 Android Development] Aldideos:
Hi, I want to try this fix, I was in stock but I had a problem with the rom, I tried to return back with a nandroid made by your recovery but it fails, so I am switching right now to cm13 even if i'm scary about the lte problem...
[G4 Android Development] popy2006:
the mobile data issue is just minor.

After reboot just enable and disable airplane mode for a few seconds and your mobile data should connect without an issue.

Flash RR, set zzmove govenor and you never look back :D

pOpY