yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] blastagator:
Do you have a link? And why is it an issue for TWRP to know what time it is? TWRP has no access to the cell network - Therefore, it can't resolve what time it is.
[G2 Android Development] murdoch1:
Sorry I don't think I explained clearly.... I wasn't sure if it was a recovery issue whereby the time/date was carried through from the internal clock of the phone. The lg g2 does not have this so I believe. I know philz did a fix with cwm recovery. Didn't know if this would be possible with twrp??
[G2 Android Development] blastagator:
I still don't understand the problem. So TWRP doesn't know what time it is - what problem does that cause?
[G2 Android Development] 60nine:
delete (i didn't read well :) )
[G2 Android Development] murdoch1:
TWRP Date

When going into recovery...doing a backup and where you can type the file name of the backup use "+date" the date defaults to January 1970.

There was a fix for CWM which according to this thread made it into TWRP:-

http://xdaforums.com/showthread.php?t=2580974

That's what I am referring to. The date ideally would remain so all nandroid backups would have the correct date/timestamp.

It's not a BUG exactly. but when you then start up the phone (in my case CM12) the phone reports the date is incorrect until it can get a fix from the network date/time.

Hopefully that makes sense?

Cheers

Andy
[G2 Android Development] blastagator:
I believe Android L uses encryption even when the user doesn't expressly use encryption - that is, it uses encryption but with a default password. My guess would be that since the data is encrypted, twrp can't read the time. This should be addressed in the next release, but the code hasn't yet been pushed to the git by teamwin.

Their commits should be soon I would suspect, and I'll rebuild as soon as the code is pushed.
[G2 Android Development] phoenix_rizzen:
Only phones that ship with 5.0 pre-installed use encryption by default. Systems upgraded to 5.0 or that the user manually flashes to 5.0 do not use encryption. You have to jump through a few hoops to enable encryption in those cases.

Typos courtesy of my Liquified LG G2 (D803).
[G2 Android Development] je2854:
So you're basically saying that with a default password we could use F2FS on /data.

So we just need to know the default password and then we would have a full working F2FS system.
[G2 Android Development] sgravel:
So I did a quick search through this thread and also around the web, and cannot find any solutions - maybe someone here can help me...

I'm using 2.8.1.1 on the Android L build, and in this configuration, I find I can only see my backups in the recovery browser, not in android. I finally read that this is by design, as a security feature, but before that I tried several suggested workarounds with no success. Changing ownership and / or permissions in recovery, browsing from mnt with android booted, using abd to set permissions in android, etc.

After that, I did a full return to stock and then back to android L and this recovery, so anything I messed up has been reverted.

I figured I'd try to get access to the backup files when booted into recovery by accessing them via adb or mtp from my Windows machine. Adb 1.0.31 does not show it as a device, so no joy there. I do see a healthy device in Windows device manager though. Mtp doesn't work either. Windows sees it as a device, but no volumes show up in Windows explorer, despite their being checked to mount in twrp settings

I'm sure I'm doing several bonehead things... and suggestions? I'd be happy with just one way to get backup files off the device

Thanks!
[G2 Android Development] blastagator:
I have no idea how you got anything about f2fs out of that comment. But no. What I was talking about has nothing to do with f2fs.
[G2 Android Development] blastagator:
TeamWin hasn't pushed the changes for Android L yet. Specifically, 2.8.2.0 adds "decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use". I'm guessing it is related to that.

Once they push the changes for Android L I will rebuild asap. Until then, must be patient because I don't think there is anything I can do :)
[G2 Android Development] blastagator:
New TWRP incoming hopefully tonight. I realized TeamWin switched to a new branch.

Update: I have to resync the entire repo to 5.0 - might not have this up until tomorrow. Also, it should be viewed as a beta/wip as everything 5.0 is :) I'll also have to patch/change some other things. So very unlikely to get it up tonight.

Update 2: Keep hitting compile errors in the main omni code: specifically in build/core.binary.mk No idea when I'll have it up and running, especially with the holiday.
[G2 Android Development] sgravel:
Not using encryption, but I understand that Lollipop support in general is a work in progress. Just wanted to make sure there was not something I was missing. Thanks.
[G2 Android Development] blastagator:
Someone who uses lollipop please let me know what model you use if you want to do some testing :) A lot has changed (or will be changing). It is a lot more complicated than just updating the twrp source. The primary omni source won't build right now, so I'm going to have to fiddle with a few things.

Anyway, tl;dr need testers on lollipop.
[G2 Android Development] je2854:
You have a +1 got the VS980 variant.
[G2 Android Development] blastagator:
Still trying to muddle through some build errors. Had a long day at work and probably won't have a ton of time to mess with it tonight. Hopefully sometime this week. Not sure with the holiday.
[G2 Android Development] intheair86:
Flash through TWRP

Is this ok to flash through TWRP? Thanks, I know n00b question.
[G2 Android Development] TheUnladenSwallow:
Yes

Also, are there any plans to create an official bumped version of this? I know it can be done by removing some stuff from the script and then manually bumping it, just wondering.
[G2 Android Development] blastagator:
I'm not planning on it. I've just kept my phone on the old BL and see no reason to upgrade it. Or my initial funny thought: "You can go bump yourself." (In a joking manner :p)
[G2 Android Development] vladmir:
Please consider a bumped version!

Dorimanx will try to create a bumped version of this kernel using this:

http://xdaforums.com/showthread.php?t=2950595

It will be nice have a recovery and kernel combo with the benefits of KK bootloader!

Thanks in advance

Enviado do meu LG-D802 através de Tapatalk
[G2 Android Development] x3m.zone:
Whats the benefits of KK bootloader?
[G2 Android Development] vladmir:
Why mess around one of most important part of the phone if we can bypass him?

http://xdaforums.com/showthread.php?p=57048525

Enviado do meu LG-D802 através de Tapatalk
[G2 Android Development] blastagator:
I have some time to really dig in this afternoon. So far, frustration!
[G2 Android Development] cyberlion17:
Hey guys i just want to ask what is the importance of backing up modem and recovery partitions? Do i have to include it in my nandroid backup? Does it corrupt often?
[G2 Android Development] boyheadkick:
me personally, i back up those partitions as well..full nandroid backup..just to be sure to avoid future problems..you can never know if you mess up your phone when you'll those..specially modem
[G2 Android Development] blastagator:
Got the new TWRP to build. However, it doesn't seem to want to boot. But it is progress none the less!

The screen flickers on and then back off. Then on once more and then black.
[G2 Android Development] 6ril1:
Unfortunately, original Bump project is dead http://xdaforums.com/lg-g3/orig-dev...-lg-phones-t2935275/post56991887#post56991887, because someone made it open source against the will of the team.
[G2 Android Development] vladmir:
I don't now who is right but one thing I now is we the LG users will be loosening with this little war!

Enviado do meu LG-D802 através de Tapatalk
[G2 Android Development] Xeon223:
Sorry NOOB QUESTION

How do you flash this, can you do it through twrp itself or what? And what do you do with the seperate md5 file thats on the page along with the zip?
[G2 Android Development] dorimanx:
To DEV :)

here is the way to sign the recovery with LG keys for original JB/KK bootloader.

LOKI is no longer needed.

https://github.com/dorimanx/Doriman...mmit/71546ca4c587e5e57412234c8e3b51f09146801e

have fun. you can BUMP all of your images, and forget about loki.

Attached my work folder.

this is not for USERS!!! dont ask how to use if you cant understand.

it's for DEV.
[G2 Android Development] blastagator:
Thanks [MENTION=2376110]dorimanx[/MENTION] :)

Update: Been working on trying to get 2.8.2.0 to build properly. Unfortunately I am somewhat stuck without being able to resolve an sepolicy issue.

libsepol.check_assertion_helper: neverallow on line 297 of external/sepolicy/domain.te (or line 9144 of policy.conf) violated by allow vold vfat:filesystem { relabelto };
Error while expanding policy
external/sepolicy/Android.mk:149: recipe for target '/home/greg/android/omni5/out/target/product/d800/obj/ETC/sepolicy.recovery_intermediates/sepolicy.recovery' failed
make: *** [/home/greg/android/omni5/out/target/product/d800/obj/ETC/sepolicy.recovery_intermediates/sepolicy.recovery] Error 1

I even tried using the sepolicy device folder from mako, thinking perhaps the device tree was the problem, and that changed the error I was getting, but still an sepolicy problem. If anyone has any experience dealing with this, I'd love to hear some input. Otherwise, I'll probably be relaxing until Sunday.
[G2 Android Development] krija:
With some little changes work with cygwin in windows. Thanks for my first bumped recovery :D
[G2 Android Development] dorimanx:
@blastagator

There is a problem with BUMP and KK bootloader.

touch screen is goinf crazy in recovery and in ROM. when installing KK bootloader.

kernel/recovery boot, but touch is broken... not sync

something we need to fix in kernel before we can use it.

so stand by for now, do not release bumped recovery, it's will be broken with KK bootloader.

EDIT!

It's seems that we must update other KK binary before we can use KK bootloader.

cust

laf

persist

tz

rpm

dbi

sbl1

modem

i got all of them from STOCK KDZ extraction.

then flashed manually to there partitions..

so if user even once updated full KK STOCK, then all will be OK.

I didnt done it, and move to KK from JB by flashing ROM + kernel and was using it like that till today!
[G2 Android Development] blastagator:
Went to dinner. I'll build that one next.
[G2 Android Development] blastagator:
All models now uploaded.
[G2 Android Development] je2854:
Throw me something else to test.

I'll be glad to help.

I'm very knowledgeable in this stuff.
[G2 Android Development] bender_007:
Try with flashify?

Edit:

d802 works

.

Tried dori kernel on liquidsmooth -> /cache /data -> f2fs mounted.

Sideffect -> reboot or any other power option doesn't work
[G2 Android Development] blastagator:
I don't think that would be caused by the recovery, the boot.img and boot kernel are separate from the recovery.img.
[G2 Android Development] blastagator:
Make sure the file was complete. Even though I don't have your model, I was still able to execute the zip and install the recovery. If that doesn't work, just flashify the .img. (Either from within the file, or I'm uploading them all now also.)
[G2 Android Development] wisefreakz:
[MENTION=5031300]blastagator[/MENTION] maybe [MENTION=4608636]bsmitty83[/MENTION] and [MENTION=4544860]osm0sis[/MENTION] can help you to achieve the 2.8.0.1 and also help [MENTION=2376110]dorimanx[/MENTION] to change the ram kernel.
[G2 Android Development] je2854:
SManager with the mount command (SU and Boot options enabled) it fully mounts the cache partition under F2FS! No user interaction is needed.

#!/system/bin/sh

mount -t f2fs /dev/block/platform/msm_sdcc.1/by-name/cache /cache
[G2 Android Development] blastagator:
Very cool! This raises my thought: Could we move SManager to be a /system app, move the script to /system and then use that to mount /data so data can be f2fs also... I guess that would depend on if the script ran before the decryption screen popped up. I'd be intrigued to give it a whirl, that's for sure.
[G2 Android Development] je2854:
It's worth a try. Although the script would need to be in a location that could have permission changed. And it would have to run before any other command.

Mount and then run everything else.
[G2 Android Development] blastagator:
Figured I could go a step farther and put it in the ramdisk. I'm trying to figure out what command is actually mounting the file systems in init.target.rc. It is using mount but without the -t flag, which doesn't seem to work in console. Trying to figure out what mount command is being called since busybox needs the -t flag.
[G2 Android Development] je2854:
As long as it doesn't mess with the aboot I'm willing to test for you.
[G2 Android Development] blastagator:
Eh, it is just a matter of trial and error, I can flash my phone back and forth easy enough. So far, no luck. /facepalm. Maybe tomorrow night.
[G2 Android Development] je2854:
I'm going to -attempt- my new discovery on /data tomorrow and see what happens.

Don't know what time but it will happen lol

Just have to make the script first THEN convert haha
[G2 Android Development] blastagator:
My inclination is you'll probably hang on the decryption screen before the script runs. Make sure you're backed up just in case :p
[G2 Android Development] je2854:
I'm thinking the same thing. ...

But I could always try the /system route you suggested.

If so we should ultimately get recovery to mount it for us.

fstab like real Linux does?
[G2 Android Development] blastagator:
There is an fstab, its in the ramdisk. If you change the partition to f2fs in the fstab, it doesnt boot. If you change the partition to f2fs in dori's mount script, it boots, but the partition isn't mounted. I think the init.mount() function of dori's kernel is missing f2fs support. Or at least that's my best guess at this point.

Maybe dori edited the code that compiles init. The init in other kernels I've looked at is ~150kb smaller than dori's.
[G2 Android Development] je2854:
I'm working on a "personal" edition of his kernel with full F2FS mounting support. I'm waiting on him to complete the compile and upload (:

I enjoy being the pig for the entire community. With the kernel compiled I'll do some more future testing for you as well.
[G2 Android Development] je2854:
Ta-Da

Temporarily found a solution...
[G2 Android Development] blastagator:
Any luck on /data? I just added my workaround for /cache in the OP.
[G2 Android Development] fdavila17:
How.in the hell do you guys installled twrp? Ive been reading... ive tried different methods as of flashify, rom.manager, twrp app with no luck... i have the at&t D800 running on 4.2.2 still and havent found a way to flash a recovery... any help.please? Thanks
[G2 Android Development] kbuck13:
Search for Autorec that's what I use.
[G2 Android Development] Tinchoska:
Autorec is for KK he has jb. Download this twrp and flash it over flashify and then flash the on on open post.

https://mega.co.nz/#!yUUk0CKC!9FfuIjjsr4_GaKLpOmBdtYbG4ibR5BpXeZaQIXp_W_A

Then if you go to KK, only then you use autorec
[G2 Android Development] fdavila17:
It wont mess up anything since i have de D800 and this copy is for the D802? Im about to flash it
[G2 Android Development] Tinchoska:
I didn't saw the D800 stuff. You'll need to download your mobile version from twrp Web page.
[G2 Android Development] dorimanx:
Never flash things not for your model.

Its will mess something for sure.

Sent from my LG-D802
[G2 Android Development] MrJyrks:
D802, TWRP 2.8.1.1, adb sideload is not working. Most of the time i'm getting error: adb device not found, the other times I get some kind of protocol errors. Philz touch adb sideload works fine.
[G2 Android Development] fdavila17:
Yeah i know but i tried my version already and idk why but i have no recovery and ive flashed different versions... this sucks lol

---------- Post added at 01:14 AM ---------- Previous post was at 12:56 AM ----------

Well i managed to install clockworkmod but i want twrp lol but for now gotta stick with clockworkmod. ..
[G2 Android Development] vibrantliker:
In 4 years I never had a problem with Twrp. Now with 2.8.1.1 I'm having all sorts of problems starting with E: error executing updater binary when trying to flash something.

Earlier today, I tried restoring a backup and it kept rebooting back into recovery and when it did, it had one of the backup options unchecked ( I think data).

Could this be due to using the wrong recovery (not one specifically for my device)?
[G2 Android Development] Tinchoska:
[MENTION=2376110]dorimanx[/MENTION] as you made the bump kernel, is OK if I flash any of the themes made for 2.8.1.1?
[G2 Android Development] 60nine:
my material twrp theme was kept after flashing bumped twrp that dorimanx provided...
[G2 Android Development] Tinchoska:
So there would be no trouble... Thanks dude for answering

---------- Post added at 03:06 PM ---------- Previous post was at 02:46 PM ----------

You took theme from theme's thread right?
[G2 Android Development] 60nine:
this one:

http://xdaforums.com/showthread.php?p=50710747

i've been using it for a while...
[G2 Android Development] legal.xchech:
So I know that I have the ability to back up my modem on most recent twrp but does that mean it will automatically restore a different baseband. For example liquid smooth 5.0 needs 12b baseband for vs980 but the some stock roms require 24a so if I backup the necessary modems with corresponding ROMs I can switch back and forth with out extra steps?
[G2 Android Development] blastagator:
Got 2.8.2.0 booting. The device config still isn't quite right though. Hitting some snags with the sepolicy I think. Won't mount partitions on startup.

Edit: I think we'll still be waiting a bit longer for the next version!
[G2 Android Development] Garfield3333:
Any chance to get data to f2fs ......?

Maybe with TWRP 2.8.2.....?

THX
[G2 Android Development] blastagator:
TWRP supports that already. The lack of support is on the ROM/kernel side.
[G2 Android Development] blastagator:
Thanks to [MENTION=912474]Dees_Troy[/MENTION] 's awesomeness I should be able to get us back in business. I will report back after I get things sync'd up.

UPDATE: 2.8.2.0 up and running on d800 !!!!

I'm going to make some adjustments to my build trees before pushing the public builds. Tonight we should be partying my friends.

Update2: I am building all models now. I am building them labeled as 2.8.1.9. This is the 2.8.2.0 code, however, I am going to redo all of the device trees. This is going to take a little bit of tinkering and work, so I am building 2.8.2.0 on my old device trees and just rolling back the version message so that when I have the device trees all patched up, I can rebuild and have that released as 2.8.2.0 instead of having to release that as 2.8.2.1. I believe reworking the device trees will be worth it for future releases and eventual migration to full LP code.

I wanted to release this as 2.8.1.9 so you can all have the new TWRP as soon as possible.

As usual, I will have them posted asap. They ARE still building, so it will be a little while.
[G2 Android Development] blastagator:
TWRP 2.8.1.9

Dec 2, 2014 (2.8.1.9)

-Built with Omni 4.4

-TWRP 2.8.2.0 Source (LP5.0 for TWRP source only)

-Labeled as 2.8.1.9 just for clarity when I redo the device trees and rebuild.

-Team Win Change Log:
[G2 Android Development] Tinchoska:
Is it bump?
[G2 Android Development] blastagator:
No. I use the old aboot. I see no reason to upgrade.
[G2 Android Development] HueyT:
2.8.1.9 All good on VS98012B :good:
[G2 Android Development] blastagator:
In a not-so-amusing twist of fate, the omni g2-common repo is borked. Building with it causes the screen to flicker off and then nothing. Doh. Might be hanging around with the device tree I have for a little bit longer. *Shrug*

Anyway, enjoy 2.8.1.9 (aka 2.8.2.0)
[G2 Android Development] samuele94:
This does not affect the 2.8.1.9, is right it? affects only to build other TWRP? I flashed your latest version and it works, I have to do a restore default?

thanks for your hard work
[G2 Android Development] dorimanx:
You dont have to update aboot to use bumped recovery.

This is singing the image with official keys. Its not brake any thing.

If you will not bump the images.

I will have to do so for all model.

As my users need it bumped.

Think far, not local. If you wish to get far.

Sent from my LG-D802
[G2 Android Development] StreetkillnHD:
Im guessing u just flash this
[G2 Android Development] oTeMpLo:
o....
[G2 Android Development] Arju:
I'm have time and date issues dating back to 1970.

Phone: d802

rom: cm12 by [MENTION=4662457]Rashed97[/MENTION]

kernel: (haven't changed kernel)

twrp: Latest as i write this post: 2.8.1.9

what I noticed was that I started getting this issue right after I restored a nandroid backup on my phone. Now I'm stuck in 1970. Also when the rom boots up for a couple of seconds till the internet can track down current time.

Is this normal for twrp and lollipop roms combined? would it change if I flash kitkat?

Would It change if I completely wipe all and go back to stock?

Does anyone have any solution?

I've tried the offset_clock apk found in this forum for lg g2 but it doesn't solve my issue. I've tried changing to different versions of recovery and even tried going to philz recovery and back.

(I might throw up a thread in Q&A section unless anyone here knows a solution.)

I'm kinda OCD and that's why it bugs me.
[G2 Android Development] Wimmme:
search the CM12 thread, this is a CM12/lollipop issue, nothing to do with TWRP
[G2 Android Development] Arju:
Thank you for answering. I'm new to this device as of last week. Feels good to know that it's not something wrong that I've done to the device but the combination cm12 and twrp is not playing well. I did not have the problem with cloudy g3 rom.

My last question, does anyone know if my issue will fix itself if I go back to cloudy g3 rom or any other kitkat based rom?
[G2 Android Development] kuduku:
LS980 ZVD stock rooted jdi screen

I had bumped up 2.8.1.1 LS980 recovery. Did not use autorec (didn't want to downgrade to JB baseband for recovery) but flashed img on stock recovery using flashify. It has white lines only in TWRP upon screen unlock but not after Android boots.

I had not Flashed white lines fix but still no white lines in Android but only in TWRP.
[G2 Android Development] samuele94:
I accidentally pressed reload theme now says (red): failed to open theme zip but the rest works, what can I do?
[G2 Android Development] khanhnv3007:
Can I use this Recovery to flash CloudyG3 on my F320 ???
[G2 Android Development] jeebspawnshop:
The answers you seek are IN THE VERY FIRST POST.

Don't be lazy - go read it.
[G2 Android Development] Arju:
To answer my own question: yes! Time gets fixed when flashing kitkat rom. Just tested it right now. But having been on lollipop it's hard to look back. So I'll reflash lollipop again. :P

Hopefully there will be some fix for it in future.

Edit: I'm back on lollipop again. Twrp time is messed up. So there we have it confirmed again that lollipop and twrp is not all there yet.
[G2 Android Development] crimple:
sideload fails

I just updated adb to make sure it wasn't that.

While trying to install zips through sideload, adb throws:

error: protocol fault (no status)

This is on the vs980. Thanks for making a great recovery btw, finally made an account after being a lurker just to thank you and report a potential bug!
[G2 Android Development] blastagator:
Someone else reported that too on the 2.8.1.1 build. I'm not sure if the stock build has it. Maybe try the "original" http://xdaforums.com/showthread.php?t=2449679 ? Let me know if it has it. If no report back, I might give it a shot tomorrow.