yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] revo420:
Ok following what I posted above - I can move files a few hundred megs but the cloudyg3 i am unable to move which is 1.3gb is there a single file size limit for F2FS? This has occurred both on D800 and D801. Thank you!
[G2 Android Development] blastagator:
Can you move it when formatted as ext4?
[G2 Android Development] voxluna:
I just realized that I flashed the D800 LP bootstack, instead of the right one for my D801. Oops. I did it during a 12 hour marathon trying to restore a G2 (as hard a brick as I've ever had), so I wasn't thinking straight. But the weird thing is, I haven't had any problems yet. I'm using @blastagator's goods, FWIW.

I'd flash the other one, except that it's a KitKat bootloader and not Lollipop, so it has that new car smell -- but I don't really understand the inner workings, and what benefit it would serve over the older one. What should I do now?
[G2 Android Development] purpleurkle:
Hello. I have a ls980 running cm12 I came from stock kk . used autorec, then upgraded to 2.8.6.1 bump. Can someone tell me what bootloader I have, kk or lp? I apologize for the question. In trying to figure out what bootstack I need to go to 12.1 and really don't want to mess up my phone. Than you in advance for your help
[G2 Android Development] Killua96:
Hi [MENTION=5031300]blastagator[/MENTION] sorry for bothering you and for my english.

I'm Killua96, LG Mod from the italian forum tuttoandroid, one of my users has a problem only with the TWRP Recovery, both cyanogen and cwm work fine, the problem is that the touch doesn't work at all but the system boot fine and the touch works normally outside the recovery, he has already tried to restore the stock firmware first with the flashtool2014 and after with the tot's method, any idea?

Thanks in advance for help
[G2 Android Development] sadokhan:
is there any way to edit the bootloader? i am using lg f160k and my home button is not working. i want to change the key combination to enter into recovery which is in bootloader i hope... is there any way to modify it? i am here to get the developer's response not to irritate anyone. if i am commenting at wrong place then sorry but i am helpless because no one cares about my threads that i've created :'(
[G2 Android Development] runekock:
We're all using G2s here, so don't expect us to know anything about your f160k. On the G2 it is absolutely impossible to edit the bootloader in any way, because it must be signed by LG. We have a couple of different versions to choose between, but they are all 100% as LG created them.
[G2 Android Development] sadokhan:
Thanks to you brother for your response... :)
[G2 Android Development] Vineet88:
security error

back to stock---->Root-----> autoRec---->flash twrp 2.8.7.1--->reboot recovery--->lg logo with security error:confused:
[G2 Android Development] runekock:
Which phone model?

Which version of stock?

Did you flash kdz or what?

Did you use autorec for kitkat or autorec for lollipop?

Sure you flashed twrp for your model?
[G2 Android Development] Vineet88:
Lg g2 d802 india.. Back to lollipop rom 30b.. Auto rec kitkat..
[G2 Android Development] voxluna:
I stumbled across something that might explain my problems with encryption, and why TWRP locks up at the password entry. Basically, there needs to be reserved space for the password, in a footer at the end of the /data partition. But if you use fastboot format userdata, I don't think it gets created. The solution seems to involve resize2fs. Is that something available in your TWRP release?

I've never seen this in other TWRPs, so I'm not sure what it's for. I don't suppose it creates .img files?
[G2 Android Development] blastagator:
This doesn't apply to our phone. We have a special partition for encryption:

/dev/block/platform/msm_sdcc.1/by-name/encrypt

Therefore, we don't need to create this 'footer' space on the main partition. That article is how to fix encryption when it isn't working at all. Our phone encrypts. TWRP just won't decrypt.

Good info though, and thanks for sharing.

You are free to try this footer method, who knows, maybe it will be crazy and work, but I'm not optimistic.
[G2 Android Development] voxluna:
Well, in my case, encryption doesn't work now, with CM12.1 or BlissPop. I get stuck at "0% completed" on the screen with the wireframe robot. However, it did encrypt when I was using stock KitKat. I'll have to experiment with this, because I really want my FDE back.

I wonder why someone decided to use a different method to keep track of encryption, when it ostensibly worked just fine in the main branch. Maybe it's because of this very issue, or perhaps it wasn't working on the G2 without it... either of which bring up more questions. The rabbit hole is always deep.
[G2 Android Development] blastagator:
Check your fstab, the encryption partition has to be defined by ROM fstab, or it won't know to check that partition / use it to setup encryption. If it isn't set up in fstab, the resize method in that article should (maybe?) work. Ideally you'd want the partition defined though.
[G2 Android Development] voxluna:
My ./fstab.g2 file has two separate lines for /userdata:

<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>

/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 nosuid,nodev,barrier=1,noauto_da_alloc,errors=continue wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-name/encrypt

/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs rw,discard,nosuid,nodev,noatime,nodiratime,inline_xattr wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-name/encrypt

I have EXT4 for everything, so I don't know if that's normal. In any case, they both have that encryptable= flag, I'm just not sure what they should look like, relative to other Android installations.
[G2 Android Development] purpleurkle:
Does wiping system partition erase internal storage or my sd card? And will I still have the backup of my stock rom I made in twrp? Thanks
[G2 Android Development] dorimanx:
System partition include only the rom

No your sdcard will not be erased.

If you select full wipe then its will.

Always use advanced wipe to select what you want to wipe.

Sent from my LG-D802
[G2 Android Development] AzureusPT:
TWRP + decrypt status?

I've checked the thread and it seems I have an issue as many other users, that upon loading TWRP, it isn't possible to decrypt the data partition. The recovery outputs that the password is incorrect despite using the correct one.

I've read also that this was a know issue in some of the LG G2 models, but I was wondering if it was fixed in any particular version.

In case the issue isn't fixed, I'm thinking a possible workaround would be to wipe all and start from scratch (without encryption) so the recovery would work, right?
[G2 Android Development] goran60:
Perhaps this is a question already asked but I just have not found. asks someone to tell me how I can install TWRP if I philz Touch already installed and if I could zip from TWRP easy to install with philz touch?

P.S. I've been away from the site so that I forgot, and I followed the progress of the community, so we need a little help.
[G2 Android Development] pattonsj:
Yes. Just flash the zip for Twrp just like you would any other zip and reboot.

Sent from my SM-N910V
[G2 Android Development] goran60:
I assumed

a big thank for you
[G2 Android Development] goran60:
whether someone can explain to me how to boot into TWRP 2.8.7.0 LG G2.
[G2 Android Development] 60nine:
boot from rom or from powered off device?
[G2 Android Development] Hiyaslalabs:
Stock Lollipop F320L

I'm currently using f320L stock lollipop 5.0.2. How to install this bump twrp? Can i use twrp manager to install it? Thank you. Sorry Im a newbie!
[G2 Android Development] goran60:
you misunderstand me. combination of butons going to get into the TVRP

sorry for bad English
[G2 Android Development] TMG1961:
Install quick reboot app from playstore

Then you use that to reboot into recovery from within rom
[G2 Android Development] bender_007:
Hold volume down and power. Wait for lg logo. Let the buttons go for 1 millisecond and hold the same buttons again. Select YES x 2

Poslano sa mog LG-D855 koristeći Tapatalk
[G2 Android Development] goran60:
to select yes when the screen is not working

e Touch a certificate to power the phone start
[G2 Android Development] bender_007:
Pm me

Poslano sa mog LG-D855 koristeći Tapatalk
[G2 Android Development] Lordcolus:
Ran into a weird situation. I am on D802; TWRP 2.8.7.1; /Data /Cache formatted to f2fs ; Temasek CM12.1.

Everything works OK before. This week, I tried to boot to recovery to dirty flash new ROM. But I just saw the TWRP splash screen and phone reboot to system directly.

Is there anyway to fix/repair the recovery?
[G2 Android Development] voxluna:
You can flash it two ways:

1) If your system boots up, download Flashify from the Play Store and simply flash the newest TWRP ZIP file over the existing installation.

2) If the phone doesn't boot, you can flash TWRP using fastboot. This method is a little harder, because you need to install drivers and Minimal ADB/Fastboot first. But after that one-time process is done, all you'll ever need is to extract the .IMG file from the TWRP ZIP, put the phone in download mode (power off, hold the UP button, plug in USB to computer) and execute this from a command line.

fastboot flash recovery recovery-name-here.img​

Et voilà.

As always, make backups, read and follow directions to the letter, etc etc.
[G2 Android Development] Lordcolus:
It doesn't work for me. Still stuck in the TWRP splash screen.

The system can boot up without any problem. I just can't boot to recovery. :crying:
[G2 Android Development] dredq:
Try autorec. Make sure you use the right one; KK or L .

KK

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

or

Play store autorec L; use the right one for your variant

https://play.google.com/store/apps/details?id=b007.autorec2&hl=en
[G2 Android Development] voxluna:
That's pretty odd. So it was a working TWRP recovery before, and suddenly just broke?

In either case, someone above me suggested AutoRec, which is definitely worth a try. Download it from the Play Store (select one for your variant and version of Android). It flashes a downgraded bootloader, custom recovery (TWRP), and patched kernel. Be sure to post the results here.
[G2 Android Development] Lordcolus:
I'am on CM12.1. Can I use AutoRec?

I read the intrduction and it said it's for Stock Lollipop rooted ROM.
[G2 Android Development] dredq:
Good question. I am not sure. I know I did this once but I used the KK version back on Paranoid Android rom.... Maybe a question for developer.

ninjacoderxda@gmail.com
[G2 Android Development] voxluna:
Well, it's "for stock" because it downgrades the bootloader so those people can root and what not. This is because downgrading is the only available exploit right now, since Lollipop hasn't been broken yet. At least, that's my understanding.

Granted, you shouldn't need to downgrade, because you've already rooted your phone -- you're only using AutoRec as a different way to get TWRP onto it.

Ideally, you would run AutoRec, then turn around and flash a hybrid bootstack (or Bump/Loki version, or whatever you fancy). Certain ROMs require certain bootstacks, but not all of them do, and some don't care. I'm not sure what CM12.1 wants, to be honest. You should be able to Google around and find out easily, though.
[G2 Android Development] bender_007:
Why don't you just flash twrp?

Poslano sa mog LG-D855 koristeći Tapatalk
[G2 Android Development] Lordcolus:
You mean the official version of TWRP? I tried and stuck in LG Logo.
[G2 Android Development] bender_007:
HM. Tell me the whole story please via pm. 1. What was the original android version 2. How did you proceed for ROM(and which one) inastall and 3. Can you boot up android?

Poslano sa mog LG-D855 koristeći Tapatalk
[G2 Android Development] Lordcolus:
I ended up bootloop after using AutoRec for Lollipop... :eek:

Fortunately, I backed up some important data. So, I reverted to Stock KitKat ROM by TOT files -> Root -> TWRP -> Convert to f2fs -> Hybrid bootstack -> SlimSaber ROM. Now, I can boot up system and recovery normally.

I came cross some previous post in this thread said it might be related to f2fs bug. But not many users reported this problem though...
[G2 Android Development] dredq:
I am sorry you ended up in a bootloop after taking my suggestion. Sorry for all the extra work/time... I am glad you are up an running again.
[G2 Android Development] Lordcolus:
It's totally fine! :o :D

Since there is not any other way to get my recovery back to work, I will need to revert to stock in the end.
[G2 Android Development] Snuzzo:
[MENTION=3075215]Lordcolus[/MENTION]

Next time, if you're having a difficult time booting into twrp. Try moving the TWRP directory from your internal storage.
[G2 Android Development] Lordcolus:
Thanks for the tip! I will try it next time. (Hope not... :p)
[G2 Android Development] frantacech:
Hi there, can you help me please?

I have G2 D802 16GB with android 5.0.2 20H and TWRP 2871

OTG working in android, but not work in TWRP.

I see OTG (0) byte, do not mount.

Why?

Flash FAT32, testing more flash

Thanks
[G2 Android Development] voxluna:
Hmm that is peculiar, sorry. I don't have any problems with F2FS (so far) but I'm running BlissPop, not stock. It has a different kernel than what we were trying to install on yours. It's also 5.1.1, not 5.0.2. So it's apples to oranges.

So you did it, you stumped me. ;)
[G2 Android Development] natenkiki2004:
Dumb question from me... What is System Image as defined in the TWRP Backup/Restore?

I just spent the last 3 hours messing around, trying a new ROM, failing miserably and went to restore a backup just to have it fail as well. Come to find out, the issue was System Image. I checked all the boxes when making a backup and when restoring. When I went to reboot, TWRP said I had no ROM installed. Unchecking System Image when doing the restore makes it boot and work just fine. On my phone it's got 3.3GB of goodies. What's it do?
[G2 Android Development] casual_kikoo:
http://lmgtfy.com/?q=system+image+twrp

http://www.androidpolice.com/2015/0...creating-ota-friendly-system-images-and-more/ .
[G2 Android Development] natenkiki2004:
Oh neat. I didn't know Google had a search thingie too!

Back to the topic, it sounds like backing up System Image isn't necessary for those jumping between ROMs then. The question/issue I have then is why does backing it up and restoring it cause a total loss of the System partition?
[G2 Android Development] mathews95:
i had white line problems with autorec on kitkat - back to stock LP using kdz - if i flash this recovery via flashify , will there be any problem ?

i heard there is problem with display panel - jdi or something ??

and i think my g2 has that panel
[G2 Android Development] Orjakone:
Hello blastagator , I have a problem when installing TWRP on LG G2 (D805).

This friday came lollipop (5.0.2) to the Brazilian model and i install the latest released version of twrp, I'm falling in a gray screen (demigod) upon entering the recovery using the flashify

I extract the .img and i installed with Flashify. If I try to get the command to turn on the device, it is locked in the logo of LG.

I apologize for bad English.

Info:

Firmware 6RA/Brazil (V30A) (LL) (5.0.2)

Root (LG One Click Root)

http://i.imgur.com/xHXU5xS.jpg
http://i.imgur.com/gA219UV.jpg
[G2 Android Development] runekock:
You are in for a hard time, I fear.

The problem is, that a recovery must be accepted by the bootloader, and we only know how to do that for the jellybean and kitkat bootloaders.

The usual way would be: use AutoRec for lollipop. But it doesn't seem to be available for the D805. Maybe you can ask the AutoRec-developer to support your model.

Without AutoRec you have to do things by hand. Go back to the kitkat bootloader, and - as the old bootloader will probably not work with the new kernel - install a bumped kernel (Dorimanx's kernel or just a bumped stock kernel).
[G2 Android Development] Orjakone:
Thanks for the answer

I already texted the creator of AutoRec

This firmware is in trouble even with the root, it seems that there is a conflict because I changed the build.prop to deceive the AutoRec and install the TWRP the D802 and even giving root permission and changing after reboot back as D805.

What method do you use to root on the LG G2 models with Lollipop?

Sorry for bad english :(
[G2 Android Development] vidplace7:
Hey [MENTION=5031300]blastagator[/MENTION], I restructured the folders on my mirroring server, just noticed that the link in the OP results in a 404 now.

https://mirror.vidplace7.com/Android/Devices/LG G2/Common/TWRP/blastagator/

Please update the OP to point to the new link. And please let me know if you need anything changed or updated :)
[G2 Android Development] sdeft:
[MENTION=5031300]blastagator[/MENTION]

branch change on TWRP git :)
[G2 Android Development] blastagator:
Will do.

I will probably start fiddling with this tonight. Thanks for the heads up.
[G2 Android Development] pat99:
Off-mode charging issue.

Anyone with bootlooping on lg logo after turning device on from offmode charging stat?

I own D800 running Dirty-Unicorn latest build, Plugged my device to charge at around 3% and turn off the device, next thing i see LG LOGO followed by tiny white battery logo.

I let it charge for hour or so, then tried to turn it on, LG LOGO did show up but didn't let device to boot properly. Had to remove from charge and turn it back on, but this time it kept repeating the same behavior as before. LG LOGO comes n device screen goes black afterwards. And repeats again n again. later i have forced turn it off, rebooted into recovery wiped cache/dalvic and that's where it booted normally.

Now device has no issue with rebooting or turning it off/on. Its just felt like a bug to me.
[G2 Android Development] da_reeseboy:
That happens to me any time I have to charge it when turned off. I will have to unplug the charger and force the phone off, then turn it on without the charger plugged in to get it back to the OS. It a bug we have with the hacked boot, but its rare that anyone ever sees it since we never have our phones off lol.
[G2 Android Development] dredq:
I have the same issue when the phone runs out of charge. I need to charge it for about 1 hour. Then I have to manually go into TWRP and reboot to system. I do not need to clear cache or dalvik.
[G2 Android Development] blastagator:
Update: I've started laying the ground work for the next TWRP build. The TWRP guys haven't finished implementing some changes with the minui and healthd. At this point, I think I have the build box ready to build the next version with cm-13 source (there were some tricky packages that had to be manually generated and installed). I have only done g2-common and d800 device sources. I don't really want to do the other devices until I can build a fully working TWRP for my d800. Patience until the next TWRP official release version.

The next version appears to have further work for encryption, as well as some other goodies. Stay patient my friends. :)
[G2 Android Development] Orjakone:
Anyone have any idea why I can not get into recovery?

The command "power + volume down" does not work when the TWRP is installed.

When you use the "Flashify or quick boot" the device restarts and gets stuck in the logo of LG

I used the AutoRec (D805) to install the TWRP.
[G2 Android Development] pigmich:
This is save my life coz the official is not quiet good.........
[G2 Android Development] blastagator:
TWRP up and building on the cm-13.0 tree. I'm not going to do another release until the TWRP team puts out the next version. They are still actively making changes related to android-M. It does boot and run on my phone though. I have noticed MTP doesn't work. Like I said, waiting for next official version before running a build for everyone.

Also, there are a few other things I'll probably change before the next release.
[G2 Android Development] dorimanx:
Dear friend.

Please update f2fs driver to 3.4.y build.

See my git for commit that i merged first 3.4.y then next 3.10.y

Use the source that i linked to commit of 3.4.y

Some users report that they cant boot in too recovery after converting data to f2fs.

But can boot to rom with my latest kernel.

So or they made mistake when converted.

Or recovery cant mount f2fs after my kernel made changes in it.

New f2fs has cache release code and contex changes. And many more, including f2fs encryption support.

Let me know if you need help to merge it.

Sent from my LG-D802
[G2 Android Development] Computoncio:
[MENTION=5031300]blastagator[/MENTION] if you want a tester for recovery pm me.

I can't access recovery because i have data in f2fs.

Phone: LG G2 D805

Kernel: Dorimanx kernel v6.6 LP D802

1st ROM : SRK-D80230f_20150926_droidth

2nd ROM : Waiting for custom recovery ;)

MODS: Viper4Android, Xposed
[G2 Android Development] blastagator:
*accidental double post*
[G2 Android Development] blastagator:
Building for my d800 now. Will test to confirm still working and then post for d802, to allow testing before formal release.

Had to cherry pick a lot of commits to get it building again, but I think it is good to go.

edit 1: Working on my d800 - Booted TWRP and formatted /cache - verified cache remounted properly in ROM. Made a couple other minor tweaks. Rebuilding d800 and d802. Will post tonight when they finish - for TESTERS. I did a lot of cherry-picking to get the kernel compiling again after updating the f2fs driver. Will need general testers. Additionally, will need ENCRYPTED f2fs testers!
[G2 Android Development] blastagator:
October 31, 2015 (2.8.7.2)

-Still built off of omni-4.4 source code. (Android-M isn't ready for a full release yet.)

-Vendor: Complete overhaul of vendor blobs, now using cm-12.1-caf branch from lg-devs

-Device: Add ability to backup/restore Bootloader partitions

++(DO NOT RESTORE UNLESS YOU KNOW WHAT YOU'RE DOING!!!)

-Device: Add ability to backup/restore Misc partition

-Device: Removed system_image

++We don't need this for our phone and it was confusing people who didn't READ the change log

-Device: Turned the max brightness back up some, it was a little too dim

-Kernel: Latest f2fs driver

++This should fix issue where ROM running kernel with newest f2fs doesn't boot

-Kernel: Other commits that were needed to make latest f2fs driver work

-Kernel: Config changes that might allow encrypted f2fs to work now!

-Kernel: Enable SELinux

++Before I accidentally completely disabled, now it should boot Enabled, but in Permissive mode.

Someone please let me know if encryption is working now.
[G2 Android Development] dorimanx:
What can i say, you did it man! Its works! We are back to business :)

You can release for all any time you like.

Well done, your contribution is big like sun for our device.

Kernel and rom are nothing! Without recovery.

Sent from my LG-D802
[G2 Android Development] smartpr1v4t3:
Sorry maybe stupid question but where to find the beta?
[G2 Android Development] da_reeseboy:
In the download section of the first post.
[G2 Android Development] casual_kikoo:
http://blastagator.ddns.net/twrp/2-8-7-2.php
[G2 Android Development] smartpr1v4t3:
Dont wanna start a discussion^^ but i searched before i posted 5 minutes and i couldnt find it.

I only find the page to blastagator.ddns.net and there i dont see the new version
[G2 Android Development] dredq:
Just looked. It is there under beta
[G2 Android Development] blastagator:
Sometimes, for some reason, some people have to refresh the page. Try refreshing the twrp page where it lists the versions.
[G2 Android Development] blastagator:
You're welcome. :) Took a lot more kernel commits than I was expecting, but it wasn't too bad. Real fun will be getting the Android-M builds out with the next TWRP release :) :)

AOSP has gotten very good. I think I've had maybe 1 random reboot / month since finding a stable ROM.