yashsingh1/xdaforums huggingface dataset:
[G2 Original Android Development] speebman:
hello all

i have a strange problem with my d802, i flashed CM13 on top of slimrom, i had an old twrp recovory and i have root, i flashed the rom with gapps rebooted and had a bootlooping.

i flashed a new bootstack-d802-caf-signed.zip, well all works ok and the rom come up and its great, BUT NOW i CAN'T access my recovery.

when i try access it shows:

Secure booting error

Error: Boot Certification Verify!

after power off\on the rom is booting OK, but no recovery.

what should i do?

danny
[G2 Original Android Development] thomas2403:
Thanks for your help. I flashed the file, but it didn't change anything.
[G2 Original Android Development] BlushMaq:
Gallery not working properly

Cleared the catche and now everything is buttery smooth.
[G2 Original Android Development] chewdaniel:
you should read the OP
[G2 Original Android Development] Th4nat0s:
hi, nobody has a bug of the audio of the notifications, the problem is the audio start without reason? . i have a registration but i can not post it because i have not 10 post.

Inviato dal mio LG-D802 utilizzando Tapatalk
[G2 Original Android Development] speebman:
i did, and i still dont understand what to do, flashing is not new to me, did it since sam S2

but i cant understand what to do to be able to access my recovery.

pleas advice

danny
[G2 Original Android Development] chewdaniel:
try Pwr&Vol- then when LG logo appears release and Vol+&Vol-

if not then boot your rom and reboot to recovery from there...

and update your recovery
[G2 Original Android Development] speebman:
that's the problem, when i try do enter recovery mode, the screen is black and error is flashed saying that the recovery isn't verified and some thing with security problem

[IMG="screen"]http://s28.postimg.org/xtglkbhml/IMG_4315_3.jpg[/IMG]

the funny thing that the CM13 rom is coming up just fine, and it work like a KING

but, the problem i dont have access to my recovery

danny
[G2 Original Android Development] migueldbr:
[MENTION=2096805]dr4stic[/MENTION] i solved my sound problem by flashing viper4android...its not a solution to the problem but its a good workaround. Had to set selinux to permissive(even though i think the package i used said it worked on enforcing but it didn't) and install busybox because viper asked for it, flashed the viper sony beats edition with the audiophile 2.0 profile (from the viper4android thread), enabled viper4android expert UI, upped max gain to 6.0db, activated Xtralouder and enabled convolver with one of the effects enabled. The result is considerably better sound(louder without almost 0 distortion). Youtube videos sound better too (and are louder)
[G2 Original Android Development] -_-__--__-_-:
Bootloop

Guys, so I did something really stupid - i flashed the LP bootstack on a KK rom and I'm now stuck in a bootloop. Somehow I cant reach TWRP (tried PWR + VOL(-) and then VOL(+ and -)).

Idk what to do now lol, i did back-up through TWRP before doing anything, so I just need to access it to for recovery.
[G2 Original Android Development] chewdaniel:
how bout Pwr&Vol- then Pwr&Vol-
[G2 Original Android Development] floel:
I hade the same problem (I use TWRP). There are 2 options (as far as I know):

1) Re-install TWRP via download mode (didn't work for me, as my PC with Windows 10/64bit didn't recognize my G2 in download mode, no matter which drivers I used)

2) Re-install TWRP by using ADB (see "Option 2" here: http://xdaforums.com/showthread.php?t=2449670 )

The second option worked just fine for me. After reboot, I was able to access the recovery. If anyone knows a better solution, please correct me :)
[G2 Original Android Development] crazyguns:
I had this. This has also been discussed in the OP (which you should read) but here's what I did.

Grab twrp for your model from http://www.gregtwallace.com/lgg2-projects/twrp/?version=3.0.0-1

and then open the zip, get the recovery.img file from that zip, copy it into your phone sdcard's root folder.

Next, go into developer options in settings (google how to get this if you don't have it), select and enable the option "Local Terminal". Now go into your launcher and open the Terminal app, and type the following two commands to get root, and then to flash the recovery;

su

dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
[G2 Original Android Development] panos_ts:
Hello and thanks for bringing MM to our devices.

Unfortunately search function does seem to working as it should*, so I'll ask something that might has been answered before.

Has anyone found a way to install LG (G3/4) Keyboard to CM13? I've found some threads in G2 Apps and Themes forum, but according to their latest posts they seem to be incompatible with CM13. So, if anyone has found any working .zip/.apk, please inform me .

*
[G2 Original Android Development] -_-__--__-_-:
Okay, so there was a different way to go to twrp here are the steps (my phone is LG D802 running god knows what rom, but its KK for sure) :

First of all, take your phone and press the power button; the select “power off”.

Wait while your phone is shutting down; wait a few seconds and then proceed.

Now, press the volume down and power button at the same time for 2 or 3 seconds until the LG logo appears on the display.

Then release the buttons and then press and hold them again.

Keep pressing the buttons until the recovery mode menu will be displayed on your LG G2.

That’s it.

The problem that rose later on is that it took me to HARD reset, but if you are COMPLETELY sure you have twrp confirm the hard reset (PWR and then PWR again) and it will take you to TWRP

Finished that, currently booting..
[G2 Original Android Development] Smobbo:
Crazyguns has give a good solution, but just to give you another option.

I had the same problem after i tried to apply TWRP 3.0 via the PC connection. My solution was to just flash twrp via AutoRecLP (i was on stock LP), this gives an older version of twrp than 3.0, but it works just fine for me :)!

Generally i just want to express my gratitude towards the developers, CM13 runs great on my LG G2 :D ! I'll probably wait with updating (running the 7-2 or 8-2 version) until there is a snapshot release, or are there major improvements expected in the coming days?
[G2 Original Android Development] Mohangrmc:
U can use flashify to upgrade the recovery .it might solve ur problem.
[G2 Original Android Development] 1stGGMan:
Cheers for the reply.

I had used TOT as my last resort :)

Currently using the RESURRECTION REMIX version of this CM13 and that working perfectly on my D802 32GB (including TV out via slimport, which is a 'imortant/well' used feature for me).
[G2 Original Android Development] SirDavidPaladin:
This happened to me as well. I had to reflash my recovery. The other time I had to go back to stock through the lg flash tool. Try using flashify or twrp manager apps to regain access to your recovery. If not, get Arec. Worked for me.
[G2 Original Android Development] berlen:
I just flashed cm 13 20160207. I have noticed some wifi disconnections while the screen was off. How can I solve this? Is it possible to flash a new radio without doing a clean flash?

I am using droidth bootstack now (I bricked my d802 flashing twrp 3 with bump bootstack...).

Also, I am experiencing an above normal battery consumption by CyanogenMod System. The battery life seems worse than cm 12.1 nightly 20151031 I am coming from.
[G2 Original Android Development] johnb380:
So [MENTION=2096805]dr4stic[/MENTION] I tried a clean flash and dirty flash of 2.08 and 2.10 of the nightlies and they both give bootloop when flashed either way for d801. So I'm asking who is the maintainer for d801 because I would like to tag them or at the least let them know this before it gets to far through to many builds and then they cannot find the problem anymore.

PS this sucks the builds r completely borked no matter what u do. The last working build is 2.07 nightly build for d801. Also like I said before I can't get a log because I don't have a pc to pull boot logs as it doesn't boot up all the way so I can't get logs the normal way on my phone.
[G2 Original Android Development] MattatG:
Secure booting error

Error: Boot Certification Verify!

i have got the same problem. Cm13 works but i can not get into recovery.

I go to settings and make factory reset. after that i put TWRP into memory by using usb cable.

next =>go to developer option and tick advanced reset command. Then i hold power button and choose RESET-> reset to Recovery.

Telephone boot into Cyanogen Recovery . Inside i choose instal from ... and choose TWRP File. After while telefon reset and turn on CM13. again hold power button and choose RESET-> reset to Recovery. and.... TWRP start

PS sorry for my english

Question

I have got original LG g2 Window case - will be support for this ?? In original soft when i close i have watch or other stuff.. maybe some kind of application ??
[G2 Original Android Development] dr4stic:
That sounds like you're running a Loki based recovery and a non Loki compatible bootloader. Probably because you changed the bootloader to fix cm. Just find a way to flash the latest recovery from inside cm and you should be fine. There are flashing apps, or you can find instructions somewhere in the thread.
[G2 Original Android Development] penobscot:
I had the same problem on d801. Flashing PsychoGame kernel fixed it for me.
[G2 Original Android Development] johnb380:
What nightly 2.08 or 2.10 and how'd u flash clean or dirty? And what order ROM, gapps, then kernel? Then it boots fine? But without kernel you had bootloop too?
[G2 Original Android Development] penobscot:
Both 2.08 and 2.10 bootlooped. 2.10 clean flash,gapps reboot TWRP then kernel.
[G2 Original Android Development] tuncay_93:
Just installed last night and i had hope to use Manual Camera app. but compability check says G2 with cm13 it is not compatible with the app. (It says it requires "the new Camera 2 API"

- Of topic here ][ would like to be able to use some of the stock apps if somebody uses any stock app on this rom can you link me ? Thanks in advice]
[G2 Original Android Development] chewdaniel:
if [MENTION=4647521]PsychoGame[/MENTION] kernel works fine for you but stock CM one doesn't maybe he or [MENTION=5031300]blastagator[/MENTION] has some ideas since a lot has happened since that kernel release... they've been very active in our kernel development lately

FWIW, on D802 here with no issues
[G2 Original Android Development] dr4stic:
Hi guys,

Been discussing your issues with the devs. The thinking is that the new crypto code exposed a bug with some devices with specific NAND parts (not all devices, just the batches built with a specific part). Sorta like the display panel issue. The updates re-enabled some hardware stuff that exposed the bug.

Please do me a favor. Make sure you're on the affected ROM, and then install he following kernel:

https://www.androidfilehost.com/?fid=24411628330025509

That's a 2016-02-10 build from like a few minutes ago, not that it matters since the kernel hasn't changed much in the last day or two. This kernel should boot. I'd really appreciate it if you'd back up your stuff and do a clean flash of the latest nightly plus my above kernel. If it works for you two, please report back and we'll try to get the bug fix posted.

Thanks
[G2 Original Android Development] dr4stic:
PS> if that kernel works, please don't stay on it. reboot to recovery and re-flash [MENTION=4647521]PsychoGame[/MENTION]'s kernel
[G2 Original Android Development] dr4stic:
Hi,

First I want to say thank you for such a detailed report with a log. While I haven't been in Germany in some years, I presently live in the US in a state well covered by my carrier. That is to say I can't test this problem.

If you could, please, follow the instructions here: https://wiki.cyanogenmod.org/w/Doc:_The_JIRA_project_management_system

and create a ticket. Make sure you specify nightlies for cm-13.0, include your logs as an attachment and include all the information you mentioned here. Add any more information you can and submit the ticket. Post back here with the link to the ticket.

Thank you :)
[G2 Original Android Development] ozguryuksel:
There is an hissing problem when good quality headphones are plugged in.

In fact this problem arised with KK and from there every rom seems to have it.

It appears while tapping on menus and stuff and clearly noticable while listening music.

editing mixer_paths.xml fixes issue partly but hissing is still there.

I wonder if any rom could be crystal clear like JB.

Maybe CM?

Who knows.... Can u please check the issue?
[G2 Original Android Development] dr4stic:
Honestly, if it happens on every rom since KK, it sounds like a hardware issue. Either the headphones or the headphone jack or something in the amplification stage in hardware is introducing noise. And in that case there's nothing CM can do.

Your best bet is to take a full backup of your phone, then return your phone to stock using the TOT or KDZ method (you'll have to find those on your own). If you still hear the noise, then it's definitely a hardware issue. If it isn't a hardware issue, then I'm not sure what to tell you. I can't reproduce that problem and I've not heard anyone complain about a hissing noise like that.
[G2 Original Android Development] ozguryuksel:
I know for a fact that JellyBean is perfect no hising on any headphones and absolutely not a hardware problem. I was on JB a day ago.

Now i installed CM13 and the hissing was so loud that i cried. Edited mixer_paths.xml on system/etc . (Just deleted <ctl name="COMP1 Switch" value="0" /> entries)

Now i can listen music in medium volume but if i increase a bit on volume the hissing appears again :(.

The reason people does not complain cuz lg quadbeats v2 is a common headphones which does not reflect tiny hissing sounds.

If you have better headphones you are in trouble .........
[G2 Original Android Development] johnb380:
It's probably a gain issue try to install viper4a and turn down gain maybe that will help.

---------- Post added at 03:56 PM ---------- Previous post was at 03:39 PM ----------

So ya both of them kernels worked and allowed the 2.10 nightly to boot. So I guess it is definitely a kernel issue.

Idk what I can do to help but whatever you think of let me know I'd be more than willing to give it a shot whatever it is.

Thanks for narrowing down the issue and finding a solution albeit a workaround. But if u need me to flash test kernels to narrow down the bad commits just shoot me whatever's needed and instructions and I'll be on it asap! Again thanks [MENTION=2096805]dr4stic[/MENTION] and team! You guys are awesome! I'm now on [MENTION=4647521]PsychoGame[/MENTION] s newest beta kernel from 2.05. And it seems to be on par with stock Cms kernel.
[G2 Original Android Development] runekock:
I seem to remember that LG fixed it in their last kitkat release. I haven't seen any reports of this being a problem in LG LP.

Anyway, to add to the confusion, Dorimanx has improved a lot on the sound in his kernel for the stock rom. If some users have grown used to Dorimanx sound, then it is no wonder that they complain about CM, even if it's equal to LG.
[G2 Original Android Development] dr4stic:
Heh... yeah, that's cuz [MENTION=4647521]PsychoGame[/MENTION]'s kernel IS the stock CM kernel with a bunch of patches he's testing out to mainline into CM proper :)

Thanks for testing. I'll be posting the bug report on Jira, but our dev knows the workaround works and will likely end up reverting all the recent crypto patches. The workaround in the kernel I gave you disabled a failsafe. That isn't the sort of thing we want going into the kernel (disabling a failsafe) so we'll just disable the offending updates instead. Thanks for your help :)
[G2 Original Android Development] holoyolo01:
Someone have a problem with the gps? I am on 02102016 nightly and my gps can't work 2 minutes without having any disconnection. I searched for this problem on the thread without any luck
[G2 Original Android Development] KpKi:
try this first

https://play.google.com/store/apps/details?id=by.zatta.agps&hl=en
[G2 Original Android Development] blastagator:
My TWRP 3 will ask you for the password and then it will decrypt. Only /data is encrypted. One thing to be mindful of, if you depend on phone for alarm or something and it crashes, phone won't reboot, it'll start to reboot and stop waiting for the decryption password.

[MENTION=2096805]dr4stic[/MENTION] - Any idea WHY cm13 won't boot on the old bootloader? I am assuming it is the same reason my recovery based in cm13 tree doesn't boot. I'd like to try and solve the issue on the recovery end, if possible, so people don't end up in jams, as they seem to be doing a lot with the new bootloader issue.
[G2 Original Android Development] dr4stic:
The devs switched to requiring the KK bootloader to solve them having to deal with the panel detection issues. The bootloader makes the panel access uniform and so the rom no longer needs to worry about it. It was a soft requirement for cm-12.1 but they hardended it for cm-13.0 with asserts. I'm not sure if there were other reasons (there probably were, but I don't always get all the explanations), but that's what I remember myself... They probably also wanted/needed to standardize around a single set of firmwares. That's usually a good idea for a ROM, not so much for a recovery :)

[MENTION=4662457]Rashed97[/MENTION] would be able to speak to this better.
[G2 Original Android Development] blastagator:
Thanks, I sent him a PM so I don't hijack the thread too much :)

I found the assertion check in the device tree, just need to make sure that is the only potential danger.

edit: I think I found the actual problem: http://xdaforums.com/showpost.php?p=65261914&postcount=2289
[G2 Original Android Development] crabilld:
For anyone with the "Secure booting error" problem on the D800... here's how I got it to work. I use Windows 7 and only tried this method with my D800. I haven't scoured all of the posts on this thread so sorry if some of this is redundant. This probably isn't the best way to fix this, but this is what worked for me.

Once I flashed the lg-devs lollipop bootstack with KitKat (bump) bootloader, I got the "Secure booting error" message on the startup screen, and then my screen went black with no further signs of life. I could not access recovery, but I could access download mode. I also eventually tried Daniel Stuart's hybrid CAF bootloader and got the same problem.

The problem is that my phone had a Jellybean (loki) bootloader, even though it was running KitKat. My phone had never gotten the KitKat or Lollipop OTA update, as it's been running a custom rom and recovery for the past couple years. The challenge was to get a KitKat bootloader on the phone without messing with the latest OTA update. I had a hard time finding a KitKat bootloader, so what I eventually did was place stock KitKat on the phone, then root, the replace the recovery, then install new bootstack and CM 13. I initially returned the phone to stock Jellybean (to bring it back to life), but I was never able to get a KitKat bootloader on it from that state.

Here are the steps I took, from the point at which my phone had the "Secure booting error", no recovery or rom access, and only download mode access:

I followed this guide to the letter (yes, it took awhile) to return the phone to stock KitKat. In the process my phone was completely reset and I lost root as well as my custom recovery.

I transferred all the files I wanted to flash to the phone's internal storage. This included the new bootstack, CM 13 nightly, gapps, and Blastagator's TWRP.

I used ioroot25 to reroot the phone. Actually I already had ioroot on my computer from two years back so I don't have a link for that, but there are a number of tutorials online.

I used Autorec to put the TWRP recovery on my phone, then I rebooted into recovery. I was concerned because it said Autorec would downgrade the bootloader, but it ended up working.

I upgraded the recovery by flashing Blastagator's TWRP (I used version 2.8.7.3), then I rebooted into recovery.

I flashed the 5.0.2 Bootstack with KitKat (Bump) bootloader, then I rebooted into recovery. No more booting error!

I wiped and factory reset the phone from TWRP, then flashed CM 13 and the ARM 6.0 Gapps. Then I rebooted the phone and it worked!
[G2 Original Android Development] stayhc:
I'll test if this work, thanks

P. S. Works but whats the deal if i pay for lte network and only can use 3g, at least now i can make calls hahaha :B

Enviado desde mi LG-VS980 mediante Tapatalk
[G2 Original Android Development] Totalrapture:
Error when flashing :/

Hi! Trying to come over from my old Paranoid Android install but I've gotten the same error on multiple flashing attempts. I get an error when trying to install the CM zip file. In red it says:

E: Error executing updater binary in zip '/sdcard/cm-12.1-20151117-SNAPSHOT-YOG7DAO1KI-d800.zip'

I was able to get in what appears to be a broken CM installation, which fortunately includes file system exploration and messaging. Accessing the phone from the computer is no problem either. Any idea what the issue here may be?
[G2 Original Android Development] dr4stic:
A couple of issues... First, wrong thread, this is the cm-13.0 thread.

That being said, I've installed that snapshot because I too have a d800 and I set it up for a family member a month or two again because... well, I just did. If it didn't work for you, either your DL corrupted or your recovery is incompatible for some weird reason.

Personally, I think you may as well run cm-13.0... Just read the FAQ and follow the instructions in the OP/FAQ and you'll likely be fine.
[G2 Original Android Development] Totalrapture:
Whoops, sorry I guess I should have clarified. I've been trying to get either 12.1 or 13 working. I've tried working on 12.1 since 13 gave me the same issue and nothing I've been giving a go has yielded any results. I updated to the latest TWRP so I feel like the recovery should be fine >_> I'm not sure what you mean by my DL being corrupted but how would I go about fixing it? Trying to install 13 yields the same error :/
[G2 Original Android Development] dr4stic:
What process did you use to install? Did you update your bootstack? Is your bootstack current? (I.e.. have you ever installed one, and if not, what was the last stock LG android you ran before switching to PA).

Try switching down to 2.8.7.3 and see if that works for you.

You should verify the downloads when you do these things. Most downloads will offer an MD5 Sum calculation for verification. This number can't be wrong. There are many md5 calculators for windows (or OS X, Linux, whichever your poison). On Windows I use WinMD5. I think for the CM downloads they calculate SHA1 hashes instead, so you'd have to get a calculator for that... Calculate one for your download and then compare it to what's on the site you downloaded from. If the two sums match up your download succeeded perfectly. If not, then you have an issue.
[G2 Original Android Development] GalaxyGusta:
Am I the only one who experience slower animations on 10th of February build? It's like animations are 30fps instead of 60
[G2 Original Android Development] johnb380:
I'm on d801 2.10 nightly and I've noticed a big slow down in animations and transitions also. I though it was just me but now that you mentioned it I agree with you. I wonder what it could be?
[G2 Original Android Development] dr4stic:
I wonder if that has to do with this change: http://review.cyanogenmod.org/#/c/131702/

It looks like it makes the min and max hardware framerates configurable via cmdline params. A default minimum is set to 30 in the code, but no default max. This probably needed an accompanying change in kernel parameters to specify the max and I don't see where something like that was defined.

I'll talk to the devs responsible...