yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] xxNiradxx:
I'm getting error executing updater binary in zip message when trying to flash AOSP Lollipop roms. I updated twrp from 2.7.0.0 (AutoRec).

Anyone know how to fix this? I'm running on VS980.
[G2 Android Development] blastagator:
This has been answered numerous times in this thread and others - Loki does not support new bootstack.
[G2 Android Development] blastagator:
Feb 15, 2015 (2.8.5.1)

-Corrected build of 2.8.5.0

-Edited the init.rc (see: https://github.com/omnirom/android_bootable_recovery/commit/df7abac1a645949ded76418759236bc3b14f107e)

-Also made a slight tweak to move tap-to-wake to a separate init (should make it easier to update the init.rc in the future if it is changed)

-FIXED: sd_card init was not being copied correctly. Relocated it to /etc and made appropriate related changes. (I guess this wasn't getting in the way of sd_card working, but it is proper to include this file.)

-NEW FILE HOST: Now using spideroak.com, they advertise no download limits!

Feb 13, 2015 (2.8.5.0)

-Merged upstream vendor blobs (Updates from lg-devs)

-TWRP Changelog:
[G2 Android Development] berryman13:
Dammit, I just rebooted into recovery (latest before 2.8.5.0) to flash the zip I had, that surely wouldnt have worked (most likely I think) -- so thank you for posting this before I did!
[G2 Android Development] samuele94:
Flash 2.8.5.1 without problems but 2.8.5.0 works great for me,why you rebuild twrp?
[G2 Android Development] :
Read the posts two posts before yours. As a good rule of thumb, always read at least the last two pages of a thread before posting a reply.
[G2 Android Development] samuele94:
I read but I do not find the answers, I read all the pages when was published
[G2 Android Development] :
Feb 15, 2015 (2.8.5.1)

-Corrected build of 2.8.5.0

-Edited the init.rc (see: https://github.com/omnirom/android_b...236bc3b14f107e)

-Also made a slight tweak to move tap-to-wake to a separate init (should make it easier to update the init.rc in the future if it is changed)

-FIXED: sd_card init was not being copied correctly. Relocated it to /etc and made appropriate related changes. (I guess this wasn't getting in the way of sd_card working, but it is proper to include this file.)

-NEW FILE HOST: Now using spideroak.com, they advertise no download limits!
[G2 Android Development] samuele94:
I've read the changelog but I was wondering if there were problems with the previous version, that's all.

it was just a curiosity but thanks of the response
[G2 Android Development] blastagator:
There is even a link to the commit that wasn't included in the first build.

All versions of 2.8.5.1 up now!
[G2 Android Development] pattonsj:
2.8.5.0 asks for password but will not decrypt. If I hit cancel at the password it will bypass but is still encrypted. I can go into Mount and at the bottom it gives me the option to decrypt data but when I enter password it says e:unable to mount settings storage during gui startup.
[G2 Android Development] blastagator:
What ROM? Can you post your fstab?
[G2 Android Development] pattonsj:
Xdabbeb 2.3.0

Trying to post the fstab but it says web page not available. How else can I get it to you?
[G2 Android Development] joedajoester:
I'm confused about the Loki and Bump'd situation. If I am still going to flash Loki'd roms, is it OK if I use the latest bump'd twrp, or will I run into issues when flashing Loki roms?
[G2 Android Development] bloof:
Someone correct me if I am wrong.

1. Start with the bootloader which does not change when flashing ROM.

JB=loki => works with bump/loki TWRP and/or bump/loki kernel

KK=bumped => bump everything

2. If you have KK bootloader, bumped TWRP, bumped kernel and flash a ROM with a loki'd kernel then just flash a bumped kernel straight after before reboot (one that works for your new ROM of course); or revert to JB bootloader and loki, i can't remember right now in which order (ROM first or bootloader first)
[G2 Android Development] joedajoester:
Thanks for the quick responce, but I am still confused if I can use the latest twrp to flash Loki Roms? In one of the change logs it says bump works on jb and Kk boot loader. I just wanna make sure because I don't like messing with recovery.
[G2 Android Development] Sunandroid:
If you are on JB bootloader it doesn't matter if recovery, kernel, both or none are bumped. You can use bumped recoveries on JB bootloader in every way.

[MENTION=5929281]bloof[/MENTION] you were wrong. ;) Because the exploits (loki and bump) work pretty different, bump doesn't influence loki in any way. The other way round it's a bit more complicated... ;)
[G2 Android Development] joedajoester:
That makes sense haha thanks for all your help!
[G2 Android Development] mj56gt:
Thanks a lot for the information!

Just got an LG G2 D800 with stock ROM 4.4.2 with kernel version of Kernel version 3.4.0 and D80020y. I just flashed CM12 with Blackbird kernel on TWRP 2.7.0. Sorry for the basic questions. What bootloader do I have? Should I update my TWRP regardless what ROM and kernel I may try in the future? How to update TWRP? Flashing the .zip file in the current (old) TWRP? Thanks in advance!
[G2 Android Development] bloof:
I changed my original post. Can you double check?

I wrote a more spoon feeding guide on dorimanx kernel thread for each situation (when he introduced bump), just can't find it :)
[G2 Android Development] witek_77:
i can flash it normally from recovery 2.8.4.0 or i need to use flashify or something else ?
[G2 Android Development] bloof:
To check bootloader:

1. Switch off phone completely

2. Boot to recovery woth hardkeys

- voldown+power then voldown+power = JB

- voldown+power then voldown+volup = KK

3. For your future ROMs it is up to you, depends on the ROMs. keeping JB bootloader is more forgiving in my opinion.
[G2 Android Development] vPro97:
Bloof is right, but this is not really needed.

A rule of thumb is, that if you haven't actively flashed the KK bootloader, you're on the jelly bean bootloader. Autorec has not yet been updated, so when you use that to get a custom recovery, your bootloader is downgraded in the process.
[G2 Android Development] pattonsj:
Let me know if you can use this. All I did was add .Zip to the end.
[G2 Android Development] blastagator:
On d800 the hard key is the same for JB and KK. More certain way -

If the menu that comes up after using the hard keys has:

- volup/voldown to move up and down; Pwr to select = KK

- Keep pushing Pwr to continue factory reset = JB
[G2 Android Development] blastagator:
Ya. I can see it. It matches up with what I've been using on the recovery - so I'm clueless.
[G2 Android Development] ars0n:
question, was tryting to change the boot screen via android image kitchen and borked the recovery, is there a special signing needed to be done after injecting/modifing the zip?
[G2 Android Development] JRJ442:
You can either Bump it or put the repacked one in the old zips with Loki. That's what I've been doing for my personal device.
[G2 Android Development] pattonsj:
I cannot believe that it doesn't work. It's almost like it doesn't know what to do once you enter your password.

---------- Post added at 11:50 PM ---------- Previous post was at 11:02 PM ----------

2.8.5.1 doesn't decrypt either.
[G2 Android Development] Garfield3333:
f2fs....?

Is F2FS on Data now working.....?

THX...!!
[G2 Android Development] skola28:
2.5.8.1 (and 2.5.8.0 and 2.4.81) cannot decrypt the Lollipop/CM12 data partitions.

You can still flash a new OS though, as the system partition is not encrypted. I use ADB Sideload and just flash the new CM12 nightly zip every day. I should point out that I'm on a OnePlus One not a G2, in case that matters.
[G2 Android Development] ars0n:
Awesome man thanks!! Are you planning on releasing some of your themed updates?
[G2 Android Development] JRJ442:
I'm not really sure yet. Repacking 40 something recoveries and bumping them again is a lot of time. I could just put them in the old Loki zips, but I'm not sure how panel detection would work then
[G2 Android Development] pattonsj:
I thought of that a while back. It says that it can't mount data and it fails.
[G2 Android Development] shinaipt99:
Hi everyone!

I flashed the new twrp and decided to give a go on F2FS. Formated all partitions and changed them to f2fs. The thing is when i try to copy files in MTP it just gets stuck... any way to solve this? Or what am i doing wrong? The PC detects it but i can't upload anything.
[G2 Android Development] skola28:
Mine does throw a few errors relating to the data partition when I dirty sideload the new nightlies, but it doesn't 'fail'. It really 'shouldn't' have to do anything to the data partition when sideloading (which is why it works) but believe it may be trying to write a log or read some data from it that is not critical to the actual flashing procedure.

Or maybe my device is a fluke; either way, mine flashes fine through Sideload.
[G2 Android Development] blastagator:
It was never broken?

After you format, you should reboot recovery before trying to copy any files.
[G2 Android Development] 4r44444:
I just changed File System of Date and Cache to F2FS, worked without problems, very fast and stable. [TWRP 2.8.5.1]
[G2 Android Development] shinaipt99:
yeah, i figured it out :) thanks blastagator!
[G2 Android Development] Cienight:
Which rom are you on?
[G2 Android Development] 4r44444:
Ressurection Remix newest Version why
[G2 Android Development] blastagator:
I don't think anyone has gotten f2fs working on a stock based rom (or at least I'm guessing that's why he's asking). The stock init binary doesn't seem to support f2fs mounting. The closest thing on stock is f2fs /cache. I use that. f2fs /data on stock ROM still is a no go, from what I've found anyway.
[G2 Android Development] SH4YD33:
I was just able to format the cache and system to f2fs. when doing The data it would not boot.
[G2 Android Development] mj56gt:
I have installed TWRP through AutoRec on my D800, but the version is 2.7.0. I want to update TWRP to a recent version. How can I do that? I tried using Goo Manager (TWRP Manager), but it does not have LG G2 D800 on its device list. I When I flashed the TWRP .zip file (2.8.5 for D800) on the current TWRP (2.7.0), it said that flash failed. What am I missing? Thanks!
[G2 Android Development] siggey:
Delete me
[G2 Android Development] culot:
Yah, what is up with XDA not allowing post deletions? Irksome.
[G2 Android Development] tinydynamite00:
Hi. Have you found a solution to flashing the updated TWRP recovery on your D800? First, Goo is largely defunct. Details in your post suggest you recently gained root. That in mind, which Android OS did you root? Did you come from stock LG 4.4 or a variation of stock 4.2.2 Android for your device? Knowing the above, I or someone in the forum will be better able to help you.

**Note: Up until TWRP 2.8± and the release of KK all recovery images made use of the Loki exploit to bypass the bootloader on our G2s. It was easier to flash a recovery image, as found inside the .zip, using a few ADB commands. Then Flashify <-- link to app in PlayStore became an easier way to flash the same recovery images, as it too employs Loki to work.

Long story short: I believe if you've root LG's stock 4.4 ROM and try to flash this custom - bumped - updated recovery on the stock KK kernel, you won't have luck. Let's find out the state of your device first before answering with every possibility. (:

If you're at all uncertain about flashing the recovery, please make sure to return and ask for assistance.

Sent from my LG-D801
[G2 Android Development] mj56gt:
Thanks a lot for the help! I really appreciate it.

Yes I first gained root through stump root on my D80020y with KitKat 4.4.2. And then flashed TWRP 2.7.0 with AutoRec. Now I have CM12 with Blackbird kernel. I'm planning to try out a couple of other ROMs. Do I have JB bootloader now? I'm not so sure what a bumped TWRP is. Which TWRP do you suggest to flash? And how? I'm actually more comfortable with adb commands than other methods. Thanks again!
[G2 Android Development] linjes:
will this recovery flash directly over twrp 2.8.5.0?

I was on stock KK 20C (d802), rooted using IOroot and used autorec. I then updated my recovery to 2.8.5.0 via flashify.

Currently i am running cloudy G2 v2.2 and dorimanx 9.9. Is it worth it and/or safe to update to this bumped TWRP or should I instead be on the 4.2 bootloader? I'm not sure at all what bumping does and it seems to me that it is another form of LOKI.

Thanks!
[G2 Android Development] Sunandroid:
1. Yes, you are on JB Bootloader since AutoRec automatically downgrades it. 2. Doesn't matter if on JB Bootloader. Ony matters for KK. 3. Grab the zip (best this one here) and flash it in your current TWRP. Reboot recovery and your recovery will be updated. No worries about Data-Loss warning. This is only for users who want to change partiton type to F2FS. Don't worry about bump either. Already explained why above (you can't use a non-bumped recovery with KK bootloader, but for JB bootloader it doesn't matter if bumped or not).

Loki and Bump are two differwnt exploits. But since this recovery is bumped, you can just flash it over your old one (im the current recovery) and you should be fine. Imho it's worth it^^
[G2 Android Development] mj56gt:
Thanks a lot! In addition to flashing this bumped TWRP, do I also need to flash the modems and bootloader on that same download website (http://blastagator.ddns.net/)?
[G2 Android Development] Krenol:
Not if your recovery is already bumped. Modem will not be changed by a rom or recovery so that neither
[G2 Android Development] blastagator:
This is incorrect. Bump works on everything loki works on and more. TL;DR Bump covers JB & KK bootloader. Loki covers JB bootloader only.
[G2 Android Development] noidea24:
i have a major problem woth 2.8.5.0 and 2.8.5.1

i was using 2.8.3.1 with no problem, decided to upgrade to 2.8.5.1, installed it, booted to recovery and everything worked, until i tried to do a factory reset. when i swipe at the bottom, instead of begining to do the factory reset, it vibrates for 3 seconds and reboots.

this happens on 2.8.5.0 and 2.8.5.1, wether it be an advance wipe, or factory reset, when i swipe it just vibrates and reboots. do i need to get a log? vs980 on 12b modem.
[G2 Android Development] :
I'm getting the same thing, you won't be able to get a lot with the way it freezes unless you're pulling it through adb when it crashes.
[G2 Android Development] noidea24:
I tried downgrading to the version i was on before, and tried to wipe/factory reset, it still froze and restarted. attempted to restore the backup i made right before all of this, when it starts "restoring data" it freezes and restarts. phones a brick right now, but i have my backup g2. im doing an adb pull, and kdz/tot back to stock.
[G2 Android Development] blastagator:
I would suggest doing Advanced Wipe. Advanced wipe works fine, quite frankly I never use the other types of wipes.

Related: Did you try the "official" 2.8.5.0 and get similar result?
[G2 Android Development] noidea24:
Yes I tried the official in the other thread, and even in advance wipe when I swipe to start the wipe it freezes and restarts.

On a completely unrelated note, my boot partitions on my computer just messed up so I have windows 7 and Ubuntu but can't boot into either of them, since I can't boot into windows, I can't restore my device. And on top of that my backup g2's back cover cracked, and a chunk broke off the plastic so I can see the battery through the back :( tough day
[G2 Android Development] :
Yeah, it does it even when trying through advanced as well. Which is weird because it worked originally then stopped, but I can't remember at what point in the day I had upgraded twrp. So I'm not positive if it ever worked in 2.8.5.0+.

And no I didn't try the official version. I don't ever use that one as I dobt care for the risk to my phone.

Seems the partitions may have gotten a bad block or something. Running repair on cache let me wipe that one again. Unfortunately dalvik-cache is an unsupported partition to repair.
[G2 Android Development] tholmes8291:
Anyone else with VS980 experiencing this?
[G2 Android Development] noidea24:
fix

Fixed it for now. Boot into twrp and backup all the data off the phone. There are plenty of guides on how to do it. Once your data is backed up follow these steps.

Personally I downgraded back to thermal 2.8.3.1, hit restore defaults and did the following.

I was using f2fs so some steps may not apply to you.

Wipe> advance wipe> select "system", and click "repair or change file system" make sure the file system is "ext4" and then select "repair" and swipe to repair

Wipe> advance wipe> select "data", and click " repair or change file system" make sure the file system is "ext4" and then select "repair" and swipe to repair (this will delete everything on phone)

Wipe> advance wipe> select "cache", and click " repair or change file system" make sure the file system is "ext4" and then select "repair" and swipe to repair.

---------- Post added at 06:09 PM ---------- Previous post was at 05:58 PM ----------

After those steps^^ I can now successfully do a factory reset and advance wipe everything. Now I just have to get my computer working so I can sideload a ROM onto it
[G2 Android Development] blastagator:
Man, you can't catch a break. Maybe the post above this one will help you fix ^^^^
[G2 Android Development] :
I'm actually about to do the same thing.

Though, it's only a temporary fix if something that can be caught with logs is causing this.

My phone was working fine... wiped and everything. Flashed the liquidsmooth rom, didn't like, so I went back to bliss... which is when all this started happening. not saying it's something with bliss or liquidsmooth.... but somewhere, something glitched. Perhaps because bliss is block based instead of file based like every other rom and twrp didnt like switching back and forth? I'm not sure.

I wish I could grab a log, but ADB doesn't work for me in this TWRP for some reason (at least not under windows, I may try under linux before giving up though)

*edit*

got in under linux, however logcat isn't included in the bundled busybox, at least not under 2.8.4.0

But, toggling the format to ext4 back to f2fs fixed my wipe dalvik freeze though. Definitely a format corruption somewhere.
[G2 Android Development] lingarajug:
I am on stock d80020y rooted, want to stay stock, so can i just copy paste recovery.img into dev/block/msm_sdcc.1/by-name and set permissions, if so how to do it and what permissions i need to set, thank u.
[G2 Android Development] z3pp3lin:
Are you on a stock or AOSP ROM? It seems to only work on AOSP ROMs on most devices.

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/247

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/333
[G2 Android Development] pattonsj:
I'm on stock. Xdabbeb's 2.3.0 to be exact. I tried it on a cm 12 variant also and it wouldn't work. On the flip side, xdabbeb 982.5 won't encrypt.
[G2 Android Development] z3pp3lin:
Yeah, CM doesn't according to what I read. The most important parts in both links are from Dees-Troy. Without getting a log to xdabbbeb a log, I'm not sure he'd even look into it.
[G2 Android Development] noidea24:
I am the same one who posted that fix ^.^

I fixed my windows partition, so i was able to flash download mode via fastboot. I then used download mode to restore to stock. Then root, recovery, 12b, and back on validus.
[G2 Android Development] blastagator:
Derp de derp.
[G2 Android Development] pattonsj:
It was my understanding that after he updated 982.5 then he would try some things for me to test. Wouldn't make much sense to logcat now. His update may fix it anyway. After that I'll logcat all he needs.
[G2 Android Development] z3pp3lin:
Sent you a pm.
[G2 Android Development] perna_hungarian:
Thank you the beautiful and useful work.

I am KK bootloader, LG G2 D802 16GB.

I rehearse to install KK loki kernel, and the undermentioned error message gets.

I tried:

twrp-2.8.3.1-d802-bump-blastagator-signed

twrp-2.8.4.0-d802-bump-blastagator-signed

twrp-2.8.5.1-d802-bump-blastagator-signed

Kernel: furnace-2.5.1-stock_d802

Kernel-bruce2728-D802-v0.41

d802-simple-v6 (dr.87)

Please, help me!

I'm sorry the bad English language knowledge, but GoogleTranslate a very good servant...
[G2 Android Development] runekock:
As blastagator said, you can't install a Loki kernel on a Kitkat bootloader.

Either change to Jelly Bean bootloader or use a bumped kernel (Dorimanx's kernel is bumped and very good).
[G2 Android Development] perna_hungarian:
Thank you.

I am a Chinese now G3 bumped rom, in him OptimusRs kernel.

I would like to exchange a kernel.

I try to wipe it the loki.sh, and loki.tool, and to modify updater-script, but the update-binary, until all of them mistake.
[G2 Android Development] blastagator:
You can't use loki. Downgrade your bootloader if you want loki.
[G2 Android Development] Syyed Tamim:
I have d802 rooted how can I instal this and how can I go to the recovery mod for this?

Please say completely.
[G2 Android Development] By.TRabZonLu™:
thanks man :)
[G2 Android Development] condudad:
Follw → this link
[G2 Android Development] tarlabasi:
senin imzana kurban olayım.Aslan kardeşim.
[G2 Android Development] adamfirari:
:):good:
[G2 Android Development] gospodinwizard:
Need some help here. In an effort to get my phone working (VS980) again, I attempted to install this via adb sideload I got this error:

assert failed: run_program("/tmp/panelfix.sh") == 0

E: Error in /tmp/update.zip

(Status 7)

Installation aborted.

sideload is my only option that I am aware of. I've tried a factory data reset from Android Recovery <3e> and the only result was a LG Logo ...reset loop. Can't get the phone to start up normally. Also tried a factory data reset from the reset screen you get from Vol Down/Power hoping to get into the TWRP I thought I had but I get the same result. The only thing Verizon will do is send a warranty replacement so I am rather stuck because the Vol Down/Power reset screen very clearly says "ROOTED" at the top and thus I can't very well send my non-working phone back for fear of getting charged for it. Any and all assistance would be very greatly appreciated.
[G2 Android Development] :
Search for how to flash your phone using kdz method.
[G2 Android Development] gospodinwizard:
That was my eventual goal but as I said I can only get to Android Recovery at this point and not download mode as I believe the Flash Tool requires. Absolutely the only connectivity I have to my phone right now is adb sideload.
[G2 Android Development] :
How can you not get to download mode? If you used one of the method that removed it then you should have fast boot instead... Just use that too flash stuff.
[G2 Android Development] gospodinwizard:
Wish I could tell you for sure but it was rooted with Stump Root and in the process a rom (don't recall which now) something went wonky. Now when I use the appropriate keys to get into download mode it ends up in Android System Recovery and trying to get to TWRP the usual way just gives me a LG Logo...reset loop.
[G2 Android Development] axierr:
Hi guys,

I just installed TWRP 2.8.5 and I can't see F2FS filesystem to format my data and cache partitions. Only, ext2-4 and FATs.

¿Why this can be?

Thanks in advance
[G2 Android Development] zach_95:
Whoops did it and it worked yay. Does tap to wake work for you?
[G2 Android Development] RohanM:
Yes it works.
[G2 Android Development] gospodinwizard:
Any suggestions esp since all I have is sideload?
[G2 Android Development] ZeNiXxX:
hey Guys,

i've a Problem with my Recovery. currently I'm on newest twrp d802.

My problem I can't wipe cache and dalvik cache. When I try to wipe cache and/or dalvik cache my recovery stucks and reboots. I have tried to delete dalvik cache with file manager... same thing... device just restarts without doing something.

I've formated cache to f2fs... when I format it to ext4 it seems to work. But after a fresh format to f2fs is starts to stuck<br

edit: i can't flash any zip file that are cleaning the cache and dalvik automatically :/