yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] blastagator:
I will need testers soon. I am working on putting together the device trees and kernel that will compile TWRP using the new marshmallow source. I haven't been rushing because the TWRP guys still haven't put out a release. However, to expedite things when they finally do, I will be doing a test build to make sure the new source at least boots on all of the variants. It will NOT be a "useable" recovery because it is not signed off on by TeamWin yet, but it will enable me to know we are good to go when the next build is released. Particularly, lgl22 is the outcast, so I had to wing kernel support for it again. I will want tests on all though.

Stay tuned and thanks :)
[G2 Android Development] TheUnladenSwallow:
Lemme know if you need a vs980 tester, vs980 is no longer my primary so if it's bricked for awhile it's fine.
[G2 Android Development] blastagator:
I'm going to post a test build soon, which will be ONLY to verify all devices boot - NOT for actual use as a recovery. TeamWin is still pushing lots of commits to the mm6.0 branch, so I'm not comfortable with people using it as their recovery.
[G2 Android Development] _that:
3.0 is still far from done, but if something doesn't work with the current code, bug reports (with logs and/or steps to reproduce) or even patches are always welcome.
[G2 Android Development] blastagator:
https://github.com/omnirom/android_bootable_recovery/commit/36ade45b1bfb69272d6a2f190ef5570d4da9310a

I'm a real boy now! :D

edit: android-6.0 twrp built successfully for my d800, using the updated aicp kernel with added bricked thermal. Alpha build will be coming soon-ish
[G2 Android Development] A Sornchai:
Nevermind Sir, lgl22 has stop update.

Thank you so much.
[G2 Android Development] blastagator:
ALPHA BUILD! (0.8.7.8)

DO NOT depend on this. I would recommend not doing file functions.

Most of the functions seem fine to me, but as [MENTION=4878287]_that[/MENTION] said, TeamWin has not green lit the next version, so I am wary of saying "go for it!"

Please test and confirm booting for me. All variants were built using the cm-13 source tree (instead of the omni-4.4 tree I had been using for everything up until now.)

d800:Booting

d801:Unknown

d802:Booting Thanks [MENTION=5263483]daniel.stuart14[/MENTION]

d803:Unknown

f320:Unknown

l01f:Unknown

lgl22:Unknown

ls980:Unknown

vs980:Unknown

Merry Christmas Eve, everyone.

Please report in thread what model you tested and if it booted.

KNOWN PROBLEMS: MTP does not work (See attached log). No exfat driver in kernel, so usb-otg probably won't work. [MENTION=4878287]_that[/MENTION] also points out that the command line does not work. It will cause TWRP crash.

edit: All variants posted.

edit2: New beta is coming in the next day or two. I fixed MTP, and applied _that's patch for command line. I am going to try and add exfat driver and ntfs driver before pushing out new beta build. (for reference, time of writing this edit is Dec 27, 11:30PM EST)
[G2 Android Development] _that:
Another known problem: The "twrp" command line tool causes the recovery to crash and restart.
[G2 Android Development] daniel.stuart14:
D802: Booting!

I have just a question: Is cm-13 supported devices using cm-13 source?
[G2 Android Development] blastagator:
Thanks!

The alpha build is so I can make sure the cm-13 device trees / source are working on all devices. I am migrating all variants to cm-13 source. (If I can't get it building, I'll build what I can for other devices - f320 and lgl22 are the two I am most concerned about)
[G2 Android Development] daniel.stuart14:
f320 has support to CM-13, not officially but it has.

But, idk about lgl22.

For l01f you'll need to revert some commits that doesn't allow to boot up on JB aboot.
[G2 Android Development] blastagator:
I think I made the necessary changes. Hopefully alpha testers will have good results :) Everyone should be using the newer KK aboot, anyway.
[G2 Android Development] daniel.stuart14:
The problem is that l01f doesn't has KK. :v

But let's see how it goes.
[G2 Android Development] _that:
Since there were no major changes in TWRP's mtp subsystem recently, I blame the kernel.

A fix for that is now on Gerrit: https://gerrit.omnirom.org/#/c/16174/

Feedback welcome.
[G2 Android Development] blastagator:
I fixed MTP - the init was messed up. Honestly, I have no idea how any of the previous versions were working without a usb.init .... lol.

I am going to work on adding exfat and ntfs drivers to kernel tomorrow and then probably post a newer beta build.
[G2 Android Development] RohanM:
I am getting error in TWRP while restoring nandroid backup

E:extractTarFork() process ended with ERROR=255

What could be the issue here ? I have tried backups from my OTG also same issue. Then I restored a very old kitkat nandroid & that worked.

LS980
[G2 Android Development] hahmad78:
me too having same issue on f320. no backup, no restore, any idea,

i am attaching log file too for better understanding. i tried 3 versions, 2.7.0.0, 2.8.4.0 and now using 2.8.7.3, but same issue
[G2 Android Development] RohanM:
I solved the issue. The backup size was around 3.9 Gb and my device was having around 4 gb free. I freed more 1 gb and issue resolved. Try it.
[G2 Android Development] hahmad78:
i have more than 15gb free on internal storage.

have you studied the partition layout for g2?

i have flashed many roms of different models. could it be the reason that partition layout is different?
[G2 Android Development] enetec:
Bump directly a v20D

Hi folks,

I need a confirm about my "install recovery plans"... :p

This is my situation [MENTION=352440]today[/MENTION]:

- d802 int. 32 GB

- KK sw v20D EUR

- rooted with SuperSu Pro

- Xposed installed & working

- no BusyBox

- stock recovery

- stock bootloader, baseband, partitions, etc..

I would like to install this bumped TWRP to go on "safe side" and eventually test some roms (Cloudyfa works, newest AOSP, etc...) but I don't want to use Autorec method since of the old bootloader, patched kernel and so on... I want a working TWRP with MINIMAL system impact.

This is my plan:

- download this bumped TWRP on latest stable version

- extract recovery.img from downloaded. zip

- flash it with Flashify root (after a backup of stock one, already done to be honest...)

Do you think this will work fine with my setup?

My only doubts are related to some articles I read reporting Bump method working with KK v20H and followings.... not a single confirm found for (preferred and still used by me) v20D version of sw.

Every comment/suggestions will be welcome!
[G2 Android Development] blastagator:
BETA BUILD! (0.8.8.2)

BETA BUILD! (0.8.8.5)

OLD - Removed now (as of 2016.01.20)

Wiping f2fs does NOT work!

Everything else(?) is working... I think. This is definitely NOT COMPLETED... TWRP guys are still pushing lots of updates to get version 3 ready.

Things I need to know if they are working:

Exfat - mounting, reading, writing (probably USB-OTG device)

NTFS - mounting, reading, writing (probably USB-OTG device)

I also need to confirm devices booting:

d800:Booting

d801:Unknown

d802:Booting Thanks [MENTION=5263483]daniel.stuart14[/MENTION]

d803:Unknown

f320:Booting & SD Card confirmed working, thanks [MENTION=6761403]ailing[/MENTION]

l01f:Unknown

lgl22:Booting Thanks [MENTION=6077145]A Sornchai[/MENTION]

ls980:Unknown

vs980:Booting Thanks [MENTION=2494120]syrkles[/MENTION]

Known Issues:

-mkfs.f2fs hangs indefinitely... not sure what the problem is.

Manually replacing the binary with the previous binary resolves the problem.

Clearly there is some issue between the new CM binary and twrp.
[G2 Android Development] syrkles:
Boots on vs980
[G2 Android Development] ailing:
TWRP 0.8.8.5

tested with F320S (blisspop 4.0.3 with kitkat bootloader)

boot into recovery is okay

boot into rom is okay

external microSD is okay

I don't have USB-OTG, couldn't test.
[G2 Android Development] bender_007:
Yes, it will work. However you will always have to deal with older bootloader at some time.

Poslano sa mog LG-H815 koristeći Tapatalk
[G2 Android Development] dorimanx:
I have request for twrp correction.

There is a logical problem with BACKUP RESTORE function.

so here what is wrong.

I have EXT4 system partition. so i made backup to storage.

Format system as F2FS! reloaded recovery, checked that system is F2FS. it's was.

Then when i hit restore system, recovery formatted system as EXT4 again! and restored my system files.

Well that is not what i needed to happen.

If i want my system to be F2FS then recovery should restore my backup to F2FS partition!

Restore is files copy paste... so this should be fixed in code.

Thanks.

P.S recovery is 2.8.7.3! not the latest beta.
[G2 Android Development] _that:
That's the intended behavior. Don't ask me why, but I can imagine it makes sense in some situations.

From reading the code, maybe what you want works if you simply rename the backup from system.ext4.foo to system.f2fs.foo.
[G2 Android Development] dorimanx:
nope. no sense at all, it's BUG.

if i have F2FS then just format as F2FS and restore data. if other format, then do the other format.

it's simple small BUG, that can be fixed by simple current partition check and not file name check...

thanks for tip about rename, it's lame way to get my test done :)

Yep, it's works! renamed and now it's formatted as f2fs and restoring...

Proposal! add check + alert to user to select wanted partition type before restore :)
[G2 Android Development] somboons:
Which ROM do you use ?
[G2 Android Development] _that:
No. The code does what it is supposed to do. If you don't like it, that doesn't make it a bug. If you think it should be changed, talk to Dees_Troy.
[G2 Android Development] 60nine:
i think he's on your 30f stock ( [MENTION=2376110]dorimanx[/MENTION] - correct me if i'm wrong)
[G2 Android Development] dorimanx:
Your 30b from old times, still great for my needs.

No time to update to 30f and I don't like that it's bound to provider, I will wait for open build if it's will ever come...
[G2 Android Development] dorimanx:
I guess I will need to correct it my self and build for me...

Ye, I know to do that :)
[G2 Android Development] blastagator:
I had pondered working on a commit to prompt user about confirmation to restore to wrong partition type, however, I figured most users probably don't need it and if they did, they could rename the file. I might look into it, if you don't code it first.

I'm currently pulling my hair out about the stupid mkfs.f2fs binary. I'm running a build with the kernel config change you suggested. However, using the kernel, as currently configured, mkfs.f2fs works fine if I use the older binary, so I suspect it isn't the kernel. I've been looking around in other code, not really sure what's going on, but haven't spent a ton of time on it either.

edit:

http://xdaforums.com/showpost.php?p=64567712&postcount=461

Looks like this is some sort of known CM issue... hopefully they hammer it out before the next TWRP release version.

edit2: Changing the kernel config didn't have any effect.
[G2 Android Development] syrkles:
Also flashed latest aicp with it and also flashed and booted the Rom fine
[G2 Android Development] WereCatf:
Hm, the downloads for TWRP (d802) aren't working. The backup mirror gives 404 and the main ones, ie. the links that say pcloud, don't give any file to download.
[G2 Android Development] xXRapToRiXx:
Do you bump the recovery images yourself? Is there a way to bump not-bumped recovery images, like cwm? I cannot find any bumped version of cwm-recovery for the lg g2(d802). Is there a way to get cwm recovery startet on my lg g2 with lollipop bootstack without getting security error, or is TWRP my only option?
[G2 Android Development] vsdmch:
Hi, im using 2.8.7.1 TWRP. Flashed hybrid bootstack and Resurection Remix 6.0 Marshmallow. Had installed a CM13 theme which gives me a System UI problem and do not let me any access to my phone. I did not let advanced reboot option , so the only thing I can do is Reboot or Power off. How I can access TWRP in this case ??? I have tried Vol down + power, then when LG logo appears, release both buttons and hold vol down + vol up. This brings me to factory reset menu, but when accepted , this does not boot into Recovery , but gives me message "secure boot error" and just black screen. Please any help or idea what should I do to get to TWRP or install it from the situation I am.
[G2 Android Development] raptorddd:
not sure but ill would go back to stock and start from there. unless theres a twrp tha can be installed like in odin.

---------- Post added at 02:29 PM ---------- Previous post was at 02:25 PM ----------

guys i need help. my phone is off so i wwant to have it up in no time. i was talking to somboons changing to f2fs

/data , /cache were f2f2 ? please install icex rom on ext4 + install dorimanx kernel before then backup with twrp after that change /system to f2fs the rename your backup

ex. system.ext4.win to system.f2fs.win (change ext4 to f2fs) all system files after that restore it again.

or

You can edit updater-script replace ext4 to f2fs then format /data , /cache , /system to f2fs after that flash ROM> dorimanx kernel

well i dont know what i did wrong.LOL i reformatted to ext4 in twrp. check and it said ext4, installed rom. then installed dorimanx kernel, then i did a back up. i selected all. or what do i need to select.? then change data/cache/system to f2fs. then copied back up before that i renamed all ext4 to f2fs. including .md5. so theres system.ext4/cache.ex4/and data.ext4. i did restore, but then i got stuck on boot. the led light didnt even turned of just logo ..

then i tried other method.

IceX_ROM_v4\META-INF\com\google\android\updater-script

open it with wordpad then changed

set_progress(0.02);

ui_print(" Mounting system...");

unmount("/system");

mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");

mount{{{{("ext4 changed to f2fs",}}}} "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");

but on aroma it didnt do a thing , in a second it said installation suscesfull.
[G2 Android Development] ST Dog:
Makes sense to me. If I backed up an ext4 partition, restoring that should yield an ext4 partition.

Say I wanted to test a new ROM that uses f2fs. When I restore my prior backup, w/o f2fs support I want it to work.

Changing partition types is not the normal desire. It should not be the default method. For that case you take extra steps (like renaming the backup file) to make the conversion.

A GUI for that would be nice, but I'd suggest make it an advance option to ignore original filesystem type.

Then most won't be asked question when doing the expected thing (restoring partition type) but those that want can change types in the cases where it's wanted.
[G2 Android Development] vsdmch:
Can you point me to a TWRP that can be installed in download mode with some kind of a tool? Im searching too :)
[G2 Android Development] raptorddd:
not that i know of. am still new at g2. i just mentioned when in s2 i could install twrp using odin..
[G2 Android Development] A Sornchai:
Confirm. Lgl22 with kk bootloader cloudyG2 2.2 all work, External microSD card ok. Thank you sir.
[G2 Android Development] blastagator:
What file?

I bump them using an open source tool, this is a smidge off topic, but google "open bump".

That isn't the default behavior, generally. It is only the default behavior for system. Otherwise, TWRP just advises you are restoring to a different type of partition, and it proceeds.

I don't think so. If you can't boot ROM or Recovery, I believe only option is kdz method.

Thanks for report. Please remove quote of my entire post. Too much clutter, plus if I edit the post, the quote may give people wrong info if they read it. Thanks
[G2 Android Development] ST Dog:
Bummer. It's still what I would expect, restore the filesystem unless I specify not to.

Of course I don't go playing with file systems often.
[G2 Android Development] A Sornchai:
I'm sorry,some one removed it completed and I edit post again.
[G2 Android Development] _that:
Actually, formatting to the original filesystem is the default behavior. Only /data is treated specially because it contains /data/media which is not backed up, so TWRP can't format it.
[G2 Android Development] blastagator:
FYI to all: Server will be going down for maintenance soon. (Tonight or sometime this week.) Upgrading :)

For latest TWRP:

http://www.dorimanx.com/LG/recovery/

All other downloads will be unavailable, sorry.

edit: Done.

edit 2: Forgot to enable cUrl. Will fix downloads today after work.

edit 3: Fixed. Everything should be working now.
[G2 Android Development] enetec:
I'll try to avoid this... ;)

Anyway I can confirm that flashing it directly with Flashify on stock v20D works flawlessly! :)
[G2 Android Development] blastagator:
Busybox is being completely abandoned *gasp* !

https://github.com/CyanogenMod/android/commit/50be19e243383a442e90c7f7bed5a3842c66957b

So, we will be moving to toolbox/toybox. Currently, on the CM tree, Toolbox/Toybox do not compile. I may tackle this tonight. [MENTION=4878287]_that[/MENTION] do you know if anyone is working on that issue, or is aware of it? Which tree do you build on and do you use busybox or toybox?

Manually adding busybox back to the cm-13 tree allows proper building with busybox.

Will keep everyone posted.
[G2 Android Development] _that:
I'm aware of busybox being removed from CM since I've read it elsewhere today. I'm also aware that mdmower identified some issues with toybox:

https://github.com/mdmower/twrp/commit/a982e6d7a8234a457602e089c652b4f96ebfe2ad

Since I don't build for devices, I don't care too much about the toolboxes, so I'm still using busybox until the toybox situation gets more stable.
[G2 Android Development] blastagator:
Good to see someone has noticed. It looks like Google is slowly moving everything to toybox, the problem then becomes having to update the TWRP code repeatedly, every time a symlink is changed from toolbox to toybox. As you said, busybox is definitely the easiest current answer.
[G2 Android Development] babe0607:
Hi...

I have d802 int, thunder rom, 2.8.7.3 recovery and last dori kernel. Also i have Kingston DTDUO3/64GB DATATRAVELER MICRODUO 64GB USB3.0 FLASH DRIVE.

I have formatted flash drive to NTFS and it's not regognized when im on recovery. is it possible to have that option in future?

Thanks in advanced :)

Send by my lg g2
[G2 Android Development] 60nine:
afaik, usb-otg drives must be fat32 to be recognizeable in twrp...
[G2 Android Development] blastagator:
Try the beta build. ntfs-3g is included in that. Please report if working or not.
[G2 Android Development] babe0607:
i tried beta and reads ntfs. :)

i haven't checked anything else up to now.

I'll check tomorrow and I'll report

thanks :)

be inspired blastagator:)

Send by my lg g2
[G2 Android Development] blastagator:
Moved to an off-site VM for $5 a month, not too shabby. Will be making some changes to the site soon and adding a 2nd mirror (the VM has 3 TB of bandwidth and by my rough math I currently only use about 100GB a month). I probably won't be putting the large files on that server though.
[G2 Android Development] dorimanx:
F2FS open source update.

Hey :)

I have merged F2FS updates from 4.5.y Kernel!

97 commits. including all that needed.

https://github.com/dorimanx/DORIMANX_LG_STOCK_LP_KERNEL/commits/master

merged from here:

http://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs.git/log/fs/f2fs

after i have cloned it to github! :) here: https://github.com/dorimanx/DORIMANX_LG_STOCK_LP_KERNEL/tree/f2fs-4.x.y

so far all OK. f2fs mount, i can copy and delete files, sync them and add/del dirs.

all seems good.

Some changes about XLS and other massive ALL FS drivers changes, i didnt added.

they are not critical for normal operation. also avoided changes that needs the missing changes from 4.5.y tree.

and replaced with what we have.

so if you wish to update, have fun.

Or you can also use this branch of CM13 for 3.4.y

https://github.com/CyanogenMod/android_kernel_lge_hammerhead/tree/cm-13.0-caf

they have merged FEW of updates that i took from 4.5.y and missing few that i already had from 3.10.y branch.

let me know if you managed to import. note the INCLUDE folder changes too... i have relocated few functions there

as set with 4.5.y branch. + optimizations.
[G2 Android Development] petran_7:
Hello everyone.

I have not updated for a long time, now I am on version 2.8.6.1 to go to the latest do I just flash the new zip from the current recovery?
[G2 Android Development] dorimanx:
Yep.
[G2 Android Development] :
Btw, Jaegeuk has a 3.4.y branch on another repo of his, which may be useful for seeding out the unnecessary commits in the future:

http://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs-stable.git/log/?h=linux-3.4.y

However the only thing is your filesystem sits somewhere in between 3.4 and 3.10 so there may be some inconsistencies there, but you can always pull from 3.10.y if it works for your tree.
[G2 Android Development] Frappoccino:
installed 0.8.8.5 on d802 w/ RESURRECTION-M .. works fine!
[G2 Android Development] blastagator:
New beta coming tonight or tomorrow my beta testers.

Update f2fs-tools to version 1.6.0 (latest) - https://github.com/blastagator/cm_external_f2fs-tools/commits/cm-13.0-twrp

And made f2fs format not take FOREVER - https://github.com/blastagator/andr...mmit/c7f867638c5c1d0cbb50793daad7544014fca5c6

Didn't see dorimanx commit until now, so no kernel changes, yet ;)
[G2 Android Development] fendaris:
Is the newest beta build safe to install on the LS980?
[G2 Android Development] blastagator:
No one ever reported back. Given that the other versions work and 11 people downloaded without complaint, I am going to say it is probably fine, but I can't no for certain. Make sure you know how to recover. Also, wait ~15 more minutes. New beta version is compiled.
[G2 Android Development] blastagator:
BETA BUILD! (0.8.9.5)

I am using this now as my recovery. No guarantees made though, as always.

Speed issue with f2fs wipe is resolved, go me!

Exfat and ntfs have been confirmed working.

Change from last official release Info:

-General:

++Built with latest CM-13 repository

++f2fs tools updated through v1.6.0 (pushed commits to upstream CM gerrit)

-TWRP

++TWRP 6.0 tree (latest changes) - TWRP3 is still a WIP - don't be surprised if you find any issues (in fact, please report them)

++I fixed the flow format issue with f2fs, it works promptly now

-Device Tree:

++Re-enable RO check/warning - MM is potentially sensitive to RO

++NTFS Support

++Fixed USB init problem

++Switched to using TWRP init w/ additional inits added via proper method

++Update external_sd init

++Restructure g2 device repo to further isolate 'TWRP' parts

-AICP-6.0 Kernel

++Updated f2fs

++Add exfat driver

++enable NTFS

++Merged bricked thermal driver and enabled

Probably more I can't think of off hand...

Devices still unconfirmed, but should be fine (please report):

d801:Unknown

d803:Unknown

l01f:Unknown

ls980:Unknown

Known Issues:

-None
[G2 Android Development] TheUnladenSwallow:
All the download links are broken "pCloud Bad Link

This file does not exist on pCloud."
[G2 Android Development] blastagator:
Fixed - typo.

Please unquote post.
[G2 Android Development] TheUnladenSwallow:
Lol sorry about that, been awhile since I've posted on xda, forgot replying did that automatically. Testing vs980 now, flashing it along with latest open gapps and cm13.

EDIT: VS980- 0.8.9.5 Confirmed booting, reformatted system partition to f2fs, full wiped every partition, rebooted, f2fs held (before system reverted to ext4 when formatted) mtp wasn't recognized at first, toggled it and it worked fine after that, copied over latest open gapps and cm13 nightly, flashed and rebooted, all working fine. Only thing is the time is off, any way to fix that? Time zone is correct but it's like 4 and a half hours off.