yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] blastagator:
BETA 3.0.2-e

BACKUP YOUR PHONE FIRST! You've been warned.

Things seem to be working well now, but you never know.

Version -d and up will only be built for most common variants unless I get a beta tester who will help me. Otherwise, all variants will be back on next non-beta build!

http://www.gregtwallace.com/lgg2-projects/twrp/?version=3.0.2-f

Version -f

-Kernel almost fully caught up to cm-13.

Through commit: https://github.com/blastagator/LGG2_TWRP_Kernel/commit/0acddcfdecdfeb2a49a28924259a4c0411dd20d6

Version -e

-More kernel catch up with CM branch

Through commit: https://github.com/blastagator/LGG2_TWRP_Kernel/commit/015f32ee0744f193b7772a80faa58d15cdfde4c2

Version -d

-More kernel changes

-Trying to catch up to CM source & figure out if something else breaks JB

-If -d doesn't boot, try -c and then please report findings as to -d and -c boot or not!

Through commit: https://github.com/blastagator/LGG2_TWRP_Kernel/commit/c45e6684f9751c417c45ea8f7fcc8bb4a6def23c

Version -c

-Kernel changes

https://github.com/blastagator/LGG2_TWRP_Kernel/commit/19d55306e257c6f5297d911c0ded34354febde69

++Disable module support

++Remove media crap we don't need in recovery, kernel is .9 MB smaller now

Kernel is still huge, 7.9MB compared to 5.3MB from my previous branch. I may try to strip out more junk, but really, don't need to.

Through commit: https://github.com/blastagator/LGG2_TWRP_Kernel/commit/ab1d40dccd401d395c4cf16d28bf87eebc6ebcaf

-Added jpeg support (in case someone wants it for themes)

Version -b

Basically this is the same setup as what we already had, but trying to fix the cm-13 source.

Likely our previous issue was this:

https://github.com/blastagator/andr...mmit/a60c78602d2b6746ad093fc3fd30fcc8980aac55

edit: Confirmed - The source for my original MM kernel was AICP which had modules disabled, which is why the initial releases worked and when I switched to CM all the problems suddenly happened.

Through commit: https://github.com/blastagator/LGG2_TWRP_Kernel/commit/4681cec9abe33c101e27f74f4fb699a6e72fe36c

Should be working on old and new BL. Need confirmation.

Please test and report any problems. The next release will be with cm-13 sources UNLESS I get a bunch of angry complaints about the beta (and in that case I will have time to try and fix them before the next release).

TESTER(S) NEEDED - If you are FOR SURE on the old JB bootloader, know how to use flashify to flash TWRP from inside of your ROM, know how to recovery from uber disaster, and are willing to help me, please reply to this post but don't quote the entire post (please). I am adding back commits to the cm-13.0 kernel to figure out where JB breaks.

Basically, I would send you beta -d -e -f (etc.) and you would tell me if it boots on the JB BL. That's it, I don't need to know any more detail than that. Please reply with your model so I know which model to build. Thanks!

.
[G2 Android Development] jeffsga88:
Every time I run any command in twrpi get the following error: "Error opening: '/data/system/dropbox/system_app_strictmode@1459709385210.txt' (Not a directory)"

I've gotten this error ever since upgrading to twrp 3.0.0, not sure what's going on. It appears everything backs up and restores and flashes correctly but still get the error. I've also included a recovery log. Does anyone have a fix? Thanks.
[G2 Android Development] blastagator:
Probably some corrupt file on /data. Try repairing /data partition or deleting the file manually (if you are comfortable with that).
[G2 Android Development] jeffsga88:
I've deleted the file manually and even wiped everything except internal storage and did a fresh install of another rom and still get that error. I can try to repair the /data partition but if I do that will it delete my data? Anyways it still flashes and backs up without problem.
[G2 Android Development] blastagator:
Did you delete it while in recovery and actually confirm it is gone? Repair

shouldn't

hurt your data. As for the wipe, you would likely have to wipe the entire data partition if those two things didn't fix it (not just the standard wipe which only deletes files and preserves the SD card; full wipe would delete SD and SD isn't automatically backed up).
[G2 Android Development] dipe7987:
Can I install this recovery with kitkat ROM?

Im still on bruce v4.0 rom and his kernel...dont have time to play with rom right now...

My recovery now is philz cmw 6.48...I want factory data reset and reinstall this ROM...

Did I just flash the file??, or I must do some methods to prevent bootloop or brick??
[G2 Android Development] Startrek852:
This has been asked so many times, the answer is yes. Recovery doesn't care about your ROM version, just flash the file. But make sure to flash the KK bootloader if you want to use 3.0. Please use the Search function next time.
[G2 Android Development] dipe7987:
Thx for the answer bro...but which version I need to reinstall bruce ROM with wipe data? I dont need anything else...

May I download the latest version 2 (2.8.7.3)? ?

Does it need to update bootloader too if flash version 2?
[G2 Android Development] Startrek852:
You can flash 2.8.7.3 without needing anything extra.
[G2 Android Development] blastagator:
3 works with either bootloader. The kinks were ironed out. Beta should work on both also. If beta doesn't boot, use stable 3.0.2 and report which beta doesn't work. Thanks!
[G2 Android Development] Startrek852:
OK, thanks for telling me.
[G2 Android Development] dipe7987:
I flash version 2.8.7.3, factory reset and install bruce ROM..

And now it works...thx for helping :D
[G2 Android Development] Floodland:
Basic functions (install packages, backup, wipe tried) with 3.0.2-d works without issues on my D806. Please let me know if you need to test something in particular here.

I am using d802 lollolipop BL with standard partitions (ext4).
[G2 Android Development] Startrek852:
I think you mean Lollipop Bootstack with KitKat bootloader.
[G2 Android Development] merikgvr4:
I was on your latest on d800. Installed sombooms 30h and got bootloop. When I rebooted to recovery touch was screwy and I think a different recovery was installed. Can't install my backup as the touches go to different places. How can I get back to your newest recovery? Thanks in advance for your help.
[G2 Android Development] runekock:
I think that somboons' rom only works on d802. And it includes not only a recovery, but also the full bootstack.

You might be able to use an otg mouse or adb to direct your current recovery to flash the correct recovery, but if your entire bootstack is for d802, you'll need to replace that as well.

But I recommend that you start from scratch by installing a kdz or tot.
[G2 Android Development] merikgvr4:
Thanks, I asked in the dorimanx Q&A thread which they used for d800 and that was the reply. Will search for how to kdz or tot. Can you recommend one that is easy to use. Thanks
[G2 Android Development] fLipz:
[D802]3.0.2-D

[MENTION=5031300]blastagator[/MENTION]

Variant: D802

Recovery: blastagator.TWRP.3.0.2-D

ScreenShot (to follow)

Sir, running good and booted fine here on your latest 3.0.2-D

Thanks!
[G2 Android Development] Astrako:
[MENTION=5031300]blastagator[/MENTION]

Could it be a bug?

1. Being in a aosp rom with:

/sytem (ext4)

/data (f2fs)

/cache (f2fs)

I do wipes and install a stock rom and I get:

/sytem (ext4)

/data (f2fs)

/cache (f2fs)​

2. Being in a stock rom with:

/sytem (ext4)

/data (f2fs)

/cache (f2fs)

I do wipes and install another stock rom and I get:

/sytem (ext4)

/data (ext4) This partition converts automatically to ext4 in this case :confused: Could it be a bug? This thing happens with all the last versions of TWRP (2.8.7.3 to 3.0.2.0)

/cache (f2fs)​
[G2 Android Development] dorimanx:
In rom boot script, there is an order to format data to ext4.

No bugs here, correct the script in rom zip.

If its stock kdz, then install rom.

Boot it, install recovery and kk boot loader.

Convert what you need by instructions!

And be happy.
[G2 Android Development] Astrako:
Hi Dorimanx!

Do you refer to the updater-script file??

It is strange, because if I install my custom stock rom after a aosp rom, it preserve the /data partition in f2fs format, but if I install the same custom stock rom after that custom stock rom, /data get converted to ext4.

Thanks for your reply! BTW your kernel is AWESOME man!
[G2 Android Development] blastagator:
If the kernel of the ROM doesn't support f2fs, ROM will reformat partitions to ext4. Also, as dori said, the ROM install script or the ROM itself (in a script somewhere in /system) could also be doing the reformatting.

In any case, not a TWRP bug.
[G2 Android Development] raptorddd:
dorimanx and blastagator on most of roms. there isnt a setting for data only for system you can see ext4.. i had this many times it always change to ext4..

the only way it works for me its to let it settle overnight till next day.. and back up data.. copy to PC.. then rename to f2fs.. and change file system to f2fs, copy back back up then restore.. but it doesnt restore back most of the times i do it right afte flashing rom.. i have to wait till next day if i do it at night then it works..

in eval 4.0 the script does have data ext4 and system ext4.. i know nothing but would it work if i share with him the line for data? like copy the same like to updater script?
[G2 Android Development] blastagator:
Backup, renaming to f2fs, and then restore should work, so long as kernel support exists. Or flash the ROM and then go to advanced wipe and change data to f2fs after the ROM has been flashed.
[G2 Android Development] raptorddd:
it does work, but only if i flash at night . leae phone as ext4, then next day try it works. i tried twice to get it done all night and didnt worked till next day. :eek:
[G2 Android Development] dorimanx:
Possible, its best to sleep at night :)

And at morning all will work great.
[G2 Android Development] mataflakitas:
Link all device not work...??
[G2 Android Development] blastagator:
What?
[G2 Android Development] duc.tranviet.5832:
What is problem when me chage data to f2fs

Please fix this

MOD EDIT: first this is a development thread...use the q&a section for your support help and questions...second....believe me you have posted a picture which occupies so much space.....like an elephant occupying a swimming pool....please avoid
[G2 Android Development] mataflakitas:
Sorry man ...link work fine ...
[G2 Android Development] jeebspawnshop:
You have failed.

Nothing is wrong, therefor nothing will be fixed.

Do not use TWRP.

Do not use custom ROMs or recoveries.

Do not pass Go.

Do not collect $200.

MOD EDIT: consider people who browse with their mobiles and these huge posters make it so funny and difficult.....
[G2 Android Development] blastagator:
And do not post massive pictures! This is also not the thread for this. Delete whatever files are taking up all the space....
[G2 Android Development] blastagator:
Release Candidate 3.0.2-g

All Variants!

Everything should be working. Still not 100% about JB bootloader. If it actually loads, you shouldn't have any problems.

IMPORTANT: If TWRP boot hangs on black screen, flash older letters until you find one that works, and report it here!

http://www.gregtwallace.com/lgg2-projects/twrp/?version=3.0.2-g

Built on cm-13 sources. Kernel up-to-date with cm-13 kernel + my extra goodies.

Once the complaints have been sifter through, the build version will be updated to -number status.

Kernel through: https://github.com/blastagator/LGG2_TWRP_Kernel/commit/2d1dbeebcf29d44977f9d749fda48757b00af682

Edit: Mockup of the old vs. new splash screen are attached. Will be in next release version! Feedback? I may make changes.

.
[G2 Android Development] petran_7:
Hello guys,

Can I flash 3.0.2-g over version 2.8.7.3 just by flashing it in recovery?

Running android 5.0.2 on D802 using CloydyG2 v3.2

Thanks in advance :)
[G2 Android Development] blastagator:
Installation section added to OP, so hopefully people stop asking this.

But yes, you just flash the new zip! :)
[G2 Android Development] petran_7:
Excuse me. I just asked because for about a year I have stopped flashing roms and every some months I update my recovery. So I didn't knew if there are big changes.

Thank you very much.
[G2 Android Development] blastagator:
New official release will be built this weekend, barring any complaints between now and then about version -g!!
[G2 Android Development] sheikhramnuj:
Hopefully it will solve the aroma installer :)
[G2 Android Development] raptorddd:
same here.. i know blastagator said he did nothing to the arome thingy.. but some roms is confusing to read instrctions... some i know what to select already.. :good:
[G2 Android Development] Startrek852:
​

Guys, blastagator has already said a bunch of times that it's not a TWRP problem, it's an AROMA problem.
[G2 Android Development] blastagator:
I suspect this is possibly the AROMA culprit:

I updated the FAQ a little while ago.

I suppose I can try to make a poll.

edit: GO VOTE! Poll closes 8th May 2016 at 07:06 PM (EST)

http://xdaforums.com/lg-g2/general/twrp-poll-aroma-t3372512

GO VOTE!
[G2 Android Development] blastagator:
Test this:

http://www.gregtwallace.com/lgg2-projects/twrp/?version=3.0.2-h
[G2 Android Development] Startrek852:
D801 please?
[G2 Android Development] raptorddd:
it restarts to system.. it get stucks before the aroma installer appears ..

i hope i got log correctly. i suck at giving logs.

http://www.filedropper.com/recovery_4
[G2 Android Development] sheikhramnuj:
Best solution mate is not to install a custom rom with outdated aroma installer. :)
[G2 Android Development] Startrek852:
That's not easy, because a lot of ROMs and some GApps still use AROMA.
[G2 Android Development] raptorddd:
none of the roms ive installed so far has new aroma...

eval.

chelozteam rom

icex

cloudy

powerg2

as far as i know all of them use the same aroma they all are hard to read. like i said some roms its easy to know what you pic some are confusing, so i use 2.8.7.3
[G2 Android Development] Startrek852:
Dude, there is no new AROMA!
[G2 Android Development] raptorddd:
well i really dont know much of aroma.. so like the guy above posted. using oudated aroma roms..:D if it can be fix great if not. then will use 2.8.7.3 :good:
[G2 Android Development] blastagator:
The intention of the poll was not to create a flame war about if AROMA is good or not. I simply want to know how many people are interested, before I waste time on it.

I'm not to keen on dealing with it, quite frankly. I am curious though.
[G2 Android Development] Startrek852:
If I started a war, I'm sorry. Can you please upload 3.0.2-h for d801?
[G2 Android Development] laranje:
twrp-3.02-g d820 bump blast .. its 100% compatible with cloudy 3.3 and DorimanX 10 kernel ? I have flicker at the botton of screen :(
[G2 Android Development] Startrek852:
No, it's not compatible with D820, it is compatible with D802.
[G2 Android Development] blastagator:
Will do tonight.

What do you mean "flicker" ? It doesn't matter what ROM or kernel.
[G2 Android Development] blastagator:
Posted. Let me know.
[G2 Android Development] gasReal:
[MENTION=5031300]blastagator[/MENTION]

thank you for your work :good:
[G2 Android Development] blastagator:
This is just a log of booting to TWRP before doing any commands.

Someone link me to a ROM with AROMA so I can do some testing, please.

edit: NM, got one

edit2: -h removed, actually made AROMA problem worse.
[G2 Android Development] jeebspawnshop:
The AROMA file manager is tiny, and will easily show the problem... if you don't want a big old ROM sitting there: http://xdaforums.com/showthread.php?t=1646108
[G2 Android Development] blastagator:
Can someone confirm AROMA

functions

fine? I understand it looks ugly, but at least in -g it seems to be working, the background is just bleeding through / it looks ugly.

Need to make sure it is only a visual problem. Thanks.
[G2 Android Development] raptorddd:
works just fine. is that its like letters appear in other areas and some blend with white and are unreadable, or some are on top of other letters. making it hard to read. some rom ask to tick to remove or tick to add and you cant read what action to tak either tick or untick.. :confused:
[G2 Android Development] blastagator:
Great news! I have solved the AROMA problem. I need to polish up the code but the basic idea I came up with and roughly implemented, fixes the graphics all nice and pretty :D

https://github.com/blastagator/andr...mmit/f217a73a603c2ec75029e0de5db38fa82cbdb7ba

I'm up to build letter M now... lot of tinkering!
[G2 Android Development] Startrek852:
Nice job! Can't wait for the new release! FYI, ADB still doesn't work for me, it always says it's unauthorized.

EDIT: I compiled TWRP myself using CM13 and now ADB is working, weird. Also, AROMA freezes TWRP when you try to exit the installer.
[G2 Android Development] raptorddd:
great i knew you could pull it off. :highfive:

thanks
[G2 Android Development] blastagator:
With what device tree, kernel, etc? Define "freezes".
[G2 Android Development] Startrek852:
Using your device trees and kernel source and your TWRP source, no changes, compiled with CM13. Nice job on the AROMA fix by the way, it works really well. And freezes meaning it gets stuck in the AROMA installer on the last page you were, unresponsive to any touch or button presses, and a forced reboot is needed.
[G2 Android Development] blastagator:
What ROM or thing with AROMA are you testing? I have been using cloudy and it exits fine.
[G2 Android Development] Startrek852:
I tested Open GApps and IceX ROM v4.0. Open GApps works perfectly except for the freezing on exit, and IceX doesn't even work, it just gets stuck at a black screen and reboots the instant the power button is pressed.
[G2 Android Development] blastagator:
Ya, I probably can't fix the other broken stuff. AROMA is just ancient and outdated. The overlay fix wasn't too bad, but the other stuff is likely bad AROMA code that is in dire need of an update (or just death, quite frankly). It was a cool idea, but with no one maintaining it... Also, looking at the code, it is kind of a mess in general. :\
[G2 Android Development] Startrek852:
OK, well that sucks. I figured out why ADB works on my build but not yours, it's because I compiled an eng build instead of a userdebug build.
[G2 Android Development] blastagator:
Debug and engineering builds both support ADB. It is strange that (as I recall) you were having that issue but other people with the same phone weren't. Either way, the TWRP guide looks like they suggest engineering builds, so I modified my script for future builds :) Thanks for the info.
[G2 Android Development] 60nine:
yes, i was thinking it was that simple (if i recall, i did it already on my old device) - but it's better to ask before it's too late :) thanks, i apreciate it...

edit:

everything works like a charm and with those latest android L themes from "themes & apps" section looks amazing...
[G2 Android Development] x3m.zone:
Deleted...
[G2 Android Development] x3m.zone:
Hello.

When doing a backup or restore, my CPU temp increases to 80*C. Is this normal?
[G2 Android Development] HueyT:
No, should be around 40-50'C as this TWRP has thermal control kernel
[G2 Android Development] x3m.zone:
Redownloaded zip & reflashed. All working ok, but temp are arround 70*C in a 5*C environment. D802 here...
[G2 Android Development] barturblits:
I have the same temps. Should be pretty normal when zipping and unzipping your backups.
[G2 Android Development] blastagator:
Yes, it should work fine, as the change log says.

No that isn't normal. Mine tops out at 48-50. Either your phone has a serious problem or there is issue in the code for the temperature (which is possible, I am on d800).
[G2 Android Development] x3m.zone:
This are my temp after 5min in TWRP, doing a backup (70-80*C)

Also the temps in normal use, in Android (50-60*C)
[G2 Android Development] blastagator:
I'm not sure what the explanation could be. Does the phone feel warm? Maybe there is something with d802 and the twrp temp code. I build all the recoveries the same way, so the kernel is the same on all.

Puzzling indeed.
[G2 Android Development] x3m.zone:
In heavy load, in Android, i also get the same temps (70-71*C). And when the load is over, the temp drops 10 degrees in 5 seconds. So i don't think it's a problem with recovery. Temps are correct readed.

Now about phone, does not feel very hot. Anyway, I had a Galaxy Nexus before (OC to 1.6GHz), so I have other standards in what means heat feeling.

As long as throttling function works, I do not worry. Do you know at what temp the phone stops due to thermal shutdown?

Thank you blastagator for your awesome work!
[G2 Android Development] sheikhramnuj:
All running smooth here when im doing back up and restore the temp goes around 48-53 degrees. I will report back if there any issues occur. Thank you blastagator! :good:

LG G2 D802

OPTIMUSG3 1.4.1

SUPERSU 2.16

TWRP 2.8.1.1
[G2 Android Development] romasik:
How install this TWRP ? for me install failed on twrp 2.8.0.1 !!!
[G2 Android Development] Mystique:
The Dropbox link..

Get the zip, install in recovery.

Reboot into recovery, settings, reset to defaults.

Reboot into system..

YMMV
[G2 Android Development] romasik:
all ok, i download again zip. this twrp not support this theme http://xdaforums.com/google-nexus-5/themes-apps/theme-twrp-holofied-black-dark-light-t2523629 ? i see in my twrp with theme F2FS but not see temp cpu and not wake to tap!

Sorry for my english :)
[G2 Android Development] romasik:
cool theme for this TWRP with Aroma File Manager http://xdaforums.com/google-nexus-5/themes-apps/theme-twrp-materialised-dark-light-play-t2915611
[G2 Android Development] sheikhramnuj:
just one question about this update is it possible that the internal storage also be wipe during wiping a partition?
[G2 Android Development] blastagator:
Internal storage is on the /data partition.
[G2 Android Development] bender_007:
Mine are the same d802 but it's not that much possible because I always put phone on vacuum hole on job. It has to be around 40-50 top most. Maybe wrong reading.
[G2 Android Development] x3m.zone:
I have 45 in idle, with Tapatalk open.

My room temp is about 25.

Rom: CloudyG3 v1.3

Kernel: Dorimanx 8.7
[G2 Android Development] bender_007:
^ pardon me. Was wrong quoting. This were on backup restore.
[G2 Android Development] Startrek852:
You're welcome. And yes, that is strange.
[G2 Android Development] goblinapoel:
Guys,

I have a weird problem here and I need your help. I was running Cloudy 3.3 for several months now and I decided to give a try to Google 1.5. I had TWRP version 3 (dont remember which version) installed and I flashed 3.0.0.2 (latest version) prior doing anything else. I created a backup after TWRP installation, did a full wipe normally and installed the new ROM. After that though I noticed that for a reason now I am back on TWRP 2.8.x.x (!!!!) and I do not know the reason. Can someone enlighten me here?

Please note that I had the TWRP version 3 installed for a few months now without any issues. Why my phone kept version 2.8.x.x after I changes 2 different versions of TWRP v.3.x.x.x?
[G2 Android Development] Jan Philipp:
Thats caused by the Aroma-Installer. I had this with every Rom with Aroma-Installer. Don't think there is any way to change this.
[G2 Android Development] Startrek852:
It's not because of AROMA, Google Edition probably flashes a recovery.img along with the ROM.
[G2 Android Development] Startrek852:
[MENTION=5031300]blastagator[/MENTION], where's the download for 3.0.2-1?
[G2 Android Development] blastagator:
Nothing to do with AROMA. Some ROMs include a recovery flash, so whatever you flashed also flashed the recovery.

It is coming. I was just working on the change log.