yashsingh1/xdaforums huggingface dataset:
[Verizon LG G3] mikereidis:
I have read this whole thread now, so I'll point out some things.

IMO the Spirit FM apps are the best tools for trouble-shooting because they have absolutely minimal requirements: The Spirit apps do not need any JAR files or libraries/HALs or RC files except for the most common ones that are on all AOSP ROMs.

On devices like LG G3 with both a Qualcomm audio chip and a Qualcom WCN36xx FM/BT/WiFi combo chip, there are only 2 kernel drivers needed: An ALSA driver for audio (which ALL G3 kernels have), and a Qualcomm radio-iris (and radio-iris-transport) FM V4L driver (which some kernels do not have and require a 2 line config file change for.)

All the Broadcom related stuff is useless because there is no Broadcom chip on the G3. Stock and AOSP ROMs these days are often a bit "universal", including files (like Broadcom HCD or other firmware files) that are not needed for that device. Makes it easier for OEMs (and ROM devs) to develop ROMs for multiple devices.

Schematics can not be trusted, especially in an area like FM where some carrier variants have it and some do not. I have seen many (including LG Optimus G and G2) that show an optional FM antenna connection, with no indications which variants have it or not. I have never found anything useful about FM in FCC documents so I don't bother even looking anymore.

Qualcomm audio chip devices have an ALSA kernel driver with many references to "Internal FM". This is a reference to their own WCN36xx FM, and it is in ALL of their audio kernel drivers, whether or not there is a WCN36xx chip. For some devices which use Broadcom chips, these "Internal FM" controls are useless and can be ignored. There is no standard about how to hook Broadcom combo chips to Qualcomm audio chips, which causes me much grief trying to support many different devices with Spirit.

If you try Spirit1, there is an Audio-> Method setting that can be changed. Spirit2 currently has no such setting, but the next release has an analog mode setting. This analog mode might work better. At this time, even International G3's, with known working FM, are having "no audio" problems with Spirit2, at least on AOSP Lollipop ROMs like CM12. This analog mode may work around the digital audio issues.

Except for one lucky case, with a chinese tablet where a jumper could be cut/removed, I have never ever heard of anyone unshorting a shorted FM antenna pin. Virtually always there is an RF shield which makes it very difficult to even start. I've cracked open a few devices to look and never went beyond the shield, except for poking a wire in once. A shield that can easily be removed is interesting. It's possible that a jumper might be found and cut. But regardless, this is almost "crazy level" tinkering.
[Verizon LG G3] ogrekane313:
i remember flashing g flex roms to my vzw g2 and got working fm radio app. so should be possible on g3
[Verizon LG G3] mikereidis:
No, the G2 and G3 have different hardware, so no such inference can be drawn in my opinion.

Can you post a link to anywhere that someone reports getting FM working on a Verizon G2 ?

AFAIK, nobody has ever gotten FM to work on G2 from US VZW, ATT or TMobile variants. My investigations have always indicated this is most likely impossible.

Unless there is audio, or at least RDS data, FM is not WORKING, even if the app starts and gives no error.

Has anyone made any more progress on proving FM might be possible on VZW G3 ?

I am going to submit CM12 patches and build a test ROM for the known FM friendly G3's to get FM working on those.
[Verizon LG G3] maria137137:
LG G3 - is FM working?

Are you still working on the Verizon G3?
[Verizon LG G3] mikereidis:
No.

AFAIK, it is impossible.
[Verizon LG G3] grease×monkey:
this is a matter of public safety.

freeradioonmyphone.org/take-action let's complain.
[Android Software/Hacking General [Developers Only]] Rohit99:
/* Disclaimer
* I am not responsible for bricked device use at your
* Own risk

*/

Introduction

Images

Coming Sooon

Features

Installation instructions

Downloads

XDA:DevDB Information

Boot Animation installer, Tool/Utility for all devices (see above for details)

Contributors

Rohit99

Source Code: https://github.com/stormtheh4ck3r/Boot-Animation-installer

Version Information

Status: Beta

Current Beta Version: v1.0

Beta Release Date: 2014-12-19

Created 2014-12-19

Last Updated 2015-01-26
[Android Software/Hacking General [Developers Only]] Vismis:
Google says it's a virus and only owner can download the file ...
[Android Software/Hacking General [Developers Only]] Rohit99:
LINK to download
[G3 Q&A, Help & Troubleshooting] SourceCoder:
Hi there,

I have a problem that my LG will not boot the device is stuck at the logo, I've also done a hardware reset but the process also depends on the logo proof and 10min not happened.

In the download mode, I'm not coming.

About the fastboot mode I try to start TWRP, but it appears the TWRP logo and nothing else happens.
[G3 Q&A, Help & Troubleshooting] Deleted member 4783640:
How did you manage to get it to this point? What did you do before it didn't boot anymore?

Also, if you manage to get adb access somehow you can just reflash the recovery again
[G3 Q&A, Help & Troubleshooting] SourceCoder:
I ran a SuperSU update and then he appeared dialog that I should restart the system and since I have the problem.

How can I flash the recovery again?

If I want to flash TWRP on the fastboot mode, only the TWRP logo and then nothing happens appears.
[G3 Q&A, Help & Troubleshooting] DelBoy:
So you cant enter download mode or recovery? And you cant turn on phone?
[G3 Q&A, Help & Troubleshooting] SourceCoder:
No download mode is not only possible fastboot mode. If I we want to install Recovery in fastboot mode, shown below

Command: fastboot flash recovery recovery .img

Error on LG G3:

Error: Command never completed

Error: Auto CM012 error

Error: Command completed with errors

Error: Command timeout error

Errror:Command completed with errors

Failed to send stop command

Failed Writing block @1
[G3 Q&A, Help & Troubleshooting] SourceCoder:
The following screen appears:

lgg3root.com/wp-content/uploads/2014/08/howto-unroot-unbrick-lgg3-2-690x492.jpg

And then immediately this screen:

android-hilfe.de/attachments/root-custom-roms-modding-fuer-lg-g3/345262d1415303724-lg-g3-kein-download-modus-mehr-img_20141106_093950.jpg

This screen does not appear:

androidheadlines.com/wp-content/uploads/2014/07/LG-G3-Download-Mode-AH-1.jpg
[G3 Q&A, Help & Troubleshooting] iBolski:
Something does not compute in this at all. SuperSU should not have caused your phone to brick like that.

Is there something else you are not telling us about how your phone was set up? Were you doing anything before you updated SuperSU? This looks like a case of where you flashed the wrong image on your phone, if you ask me.

SuperSU is not phone specific, so I'm having a hard time believing SuperSU did this.

Something else must have happened that you are not telling us. You need to lay out in order, everything you did to your phone up to the point of updating SuperSU.

Also, SuperSU asks how to update: normal or via recovery. Which way did you choose? Either one shouldn't matter, but it's a start.
[G3 Q&A, Help & Troubleshooting] SourceCoder:
I had the ROM KNVIRUS V11, since I got the message that an update to SuperSU are available. The update I installed then I get the message that the device must be restarted for the update to be finished and since I have the problem.

I wanted to start the download mode just in fastboot mode, unfortunately without success.

command to start the download mode: fastboot boot laf.img

Result: fs2.directupload.net/images/141219/p68gn6y5.jpg

What I do not understand whatever I command in fastboot mode I enter I get these error messages:

Error: Command never completed

Error: Car CM012 error

Error: Command completed with errors

Error: Command timeout error

Errror: Command completed with errors

Failed to send stop command

Failed writing block @ 1
[G3 Q&A, Help & Troubleshooting] iBolski:
Did you flash the correct laf.img file for your model of phone? If not, that could be part of it. What model of the G3 are you using and where exactly did you obtain the laf.img file from?
[G3 Q&A, Help & Troubleshooting] SourceCoder:
SuperSU update should I install because the PlayStore has shown that there is an update.

laf.img I downloaded here: http://xdaforums.com/showthread.php?t=2766437

I found a thread has to ängliches problem: http://xdaforums.com/lg-g3/general/guide-how-to-restore-download-mode-t2897257
[G3 Q&A, Help & Troubleshooting] iBolski:
Well, there you go. I have NO idea for what version of the G3 that thread was for. The guy never states which version it is. You do not, repeat, do NOT flash anything to system, boot, etc for this phone unless you know for sure it's for YOUR model of the G3. There are various models of the G3. For example, mine is the Verizon model (VZ985). There is an AT&T model (DS855), and numerous others, especially for those overseas. I would not and should not flash the DS855 boot image to my VS985 boot image. It will brick the phone as you have found out the hard way from what I can tell.

You just flashed something you have NO idea which version it was for. You may have completely bricked your phone. I'm not entirely sure, but you need to find the correct stock images for your phone and flash them back.

You need to go here and figure out which model of G3 you have:

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

After that, you need to go and find the correct stock image files and flash those back onto your phone. Since this are NOT img files, you cannot fastboot flash them. You muse use either KDZ or TOT files depending on which ones are available for your model of phone:

http://lg-firmware-rom.com/

or

http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/

Then, you have to use the correct tool to flash these files depending on if they are KDZ or TOT file:

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

Hopefully, flashing back to the correct stock image will fix you up. However, you better make darned sure which model of phone you have BEFORE you even attempt it. Once you figure out which model of G3 you have, post here and ask. Otherwise, you could bork your phone up even worse to where it may not be recoverable. Hopefully, it's not at that state right now.
[G3 Q&A, Help & Troubleshooting] SourceCoder:
I have LG G3 16GB EU version.

As I have written on the first page, I get nothing into download mode so I can not flash it.

What I can not understand why no command in fastboot mode works no matter what I type, I always get the error message: FAILED (remote: flash write failure)
[G3 Q&A, Help & Troubleshooting] iBolski:
Again, did you verify with the link you posted for the image file that it was indeed for YOUR model of your phone? If not, you probably have bricked it.

You need to go and follow the links I posted which tell you how to flash back to stock.

There was no reason to go into fastboot mode for SuperSU. I don't know why you felt you had to do that.

Also, the second link you posted has the thread pretty much deleted. The OP said he was incorrect in what he posted (whatever it was I don't know since he deleted it), so it was removed due to it not working as stated.

Go back to the links I posted to flash back to stock on your model. If what you say you have is the European model, then this would be the KDZ file you want:

http://storagecow.eu/Xda/LG G3/Stock/Europe Common 16G D85510A_00.kdz

I would verify for sure that is what your phone is before continuing or else, you'll bork your phone up even worse than it is already.

The boot image you flashed is probably for the Korean version of the phone and that's why everything is messed up.

If you are not sure on how to do this, then you might want to find someone near you who does.

Just remember, just because a post says it's for the G3 doesn't mean it's specifically for YOUR model of the G3. You need to verify for sure that it is. Most have the model number in the thread's title.
[G3 Q&A, Help & Troubleshooting] razaaliarain:
LG G3 Fastboot

well i have the same problem for a week every command was giving error, but then used this command "fastboot boot twrp.img" i was able to get into the recovery from there i wiped everything and then rebooted but nothing happened but then somehow (I DO NOT KNOW HOW) i was able to get into the download mode so i flashed the stock firmware of my lg g3 D855 and everything was going good and i was just setting up my phone and then suddenly it turned off and again booted into the fastboot mode, WTF , i was just installing some apps from playstore man, and now when i try to boot into twrp it is just stuck on twrp image on the whole screen
[G3 Q&A, Help & Troubleshooting] _narisha_:
[1700] fastboot mode started

i was facing the same problem and "fastboot boot twrp.img" worked. it took me to twrp where i flashed my ROM. i had freaked out that my G3 was bricked.
[G3 Q&A, Help & Troubleshooting] razaaliarain:
But now i am stuck again on fastboot mode and this time i was not rooted and did not had twrp installed so now when i try to use the "fastboot boot twrp.img " my device will reboot and then will be stuck on twrp logo on the screen
[G3 Q&A, Help & Troubleshooting] TypQxQ:
I have the same problem...

I ran stock OTA update 20f, since a couple of weeks ago. While I had my phone on the table and it was runing voice recorder soft it restarted once and then after a couple of minutes again. This time it never booted but stuck at the LG screen.

Never rooted, never installed anything other than the OTA 20e and 20f updates. I have not flashed anything to the phone other than the official OTA.

Doesn't boot to anything other than fastboot. Recovery starts but after confirming twice it reboots and stuck still.

If I boot to Download Mode it goes to fastboot, if I wait long enough on regular boot that only shows the LG logo it will eventually go to fastboot.

Running "fastboot.exe boot openrecovery-twrp-2.8.4.0-d855.img" gives me the same error messages, stuck at the TWRP logo screen. I found the ADB port is connected but when running "adb devices" it says "LGD855..... offline". I didn't enable ADB before the device crashed and I can't enable it in TWRP because it doesn't start properly.

I have the 32GB D855 European unlocked. I belive this is hardware problem and will send it for repairs.
[G3 Q&A, Help & Troubleshooting] gee2012:
Oeps, `flash write failure` brings back memory`s of the emmc failure with Samsung devices where the sdcard is no longer readable and can not be written on. Send it in for repair, there is no other way and they`ll probably replace the motherboard.
[G3 Q&A, Help & Troubleshooting] TypQxQ:
That's right. I tested to boot Philz recovery and it freezes at the text.

Mine says actually:

Error: Command never completed

Error: Auto CMD12 error

Error: Command never completed

Error: Command timeout error

Failed to send stop command

Failed reading block @ 1

mmc read failure misc 2048

The CMD12 is according to emmc spec a "Stop command".

So this is a hardware fault and not a software one.
[G3 Q&A, Help & Troubleshooting] SourceCoder:
Update:

LG Say:

Defekt: Swap Board (Main, RF): Immpossible to Repair
[G3 Q&A, Help & Troubleshooting] SilverBullet129:
Ok I was in similar situation not to long ago since I flashed the wrong rom for my device and just would boot in download mode, luckily I got it working again through sheer luck I guess.

Here is what I did (assuming you are running Windows of course:P):

You can follow the guide here It should have everything you need to get back to stock so you can at least start using your device again.

Any questions or if you need further help just ask since it took me awhile to get it to work successfully on my G3.
[HTC One S] ptjack:
I can't go to hboot 2.16 if i flash with adb i get the soft brick
[G 2014 Q&A, Help & Troubleshooting] Jcardoso4:
Hi

I had Moto G XT1068 with stock rom, bootloader locked and no root.

Then I decided to follow this tutorial http://xdaforums.com/moto-g-2014/development/tool-moto-g-xt1068-andoid-l-updater-t2964933 to install Lollipop with root and bootloader unlocked and worked fine but I couldn't get acess to 3G, the dialer wasn't working and I faced a few more little bugs so I decide to downgrade to Stock rom again and followed thus tutorial http://xdaforums.com/moto-g-2014/general/restore-to-stock-t2873657

Now I can't pass the bootloader unlocked logo. I have acess to fastboot and I have Philz recovery installed. I searched and found some tutorials to unbrick the phone but I'm a little afraid to follow the wrong one and do worst.

Can you help me please? Is my phone soft bricked or hard bricked? Can I have hope?

Thanks to all.

PS: my english is not perfect, if you don't understand something please say.
[Transformer TF300T Q&A, Help & Troubleshooting] hkp2:
Hi,

I was wondering what steps I would need to take to go from

To be able to flash into a Kitkat Stock-based ROM or KatKiss 5.0.1? I need to stick with stock based so my flashed touch firmware will stay.

If someone could link me to the proper tutorials/guides that would be great.
[Transformer TF300T Q&A, Help & Troubleshooting] cmendonc2:
In order to use the new KitKat ROMs, you actually have to upgrade to the latest stock firmware (JB 4.2). The new TWRP and ROMs require the newer bootloader. I'm not that familiar with the touch firmware and how that works, but I'm not sure if that is upgradable too?
[Transformer TF300T Q&A, Help & Troubleshooting] balu25int:
First OTA to 4.2, then install any recovery (see Question and answer section) and then flash ROM.
[Asus ZenWatch] tonyguy2000:
problem resolved
[Asus ZenWatch] modelyacht:
cover to mute

Very curious what the issue was, and how it was resolved. I went the Asus Support chat route, and was supremely disappointed when they sent me to their website, had me do a reset, a reinstall of the Zenwatch Manager, then decided it must be a hardware issue, and told me it would need to be sent in to be serviced.

If cover to mute doesnt work, and the app wont save the selection when I click apply...but cover works for other features....why blame the watch hardware? Seems more likely to be a phone software issue than watch hardware.

Support had no clue. The watch is saying install android wear, the phone indicates that Zenwatch Manager requires and uses Android Wear configuration, and the guy is telling me I dont need to install Android Wear. Very frustrating half hour!
[Asus ZenWatch] JohannFaust:
Not working for me either

I can't get incoming calls (Nexus 5, stock Lollipop 5.0.1) to mute using the feature either. Could it be related to the fact that I wear the watch on my right wrist?
[Asus ZenWatch] modelyacht:
nah, sounds like a hardware issue... send it in for service.

nah, sounds like a hardware issue... send it in for service.
[Asus ZenWatch] JimSmith94:
Are you putting your palm ON the watch? That's what I have to do with my Moto 360.
[Asus ZenWatch] modelyacht:
cover to mute

What's odd, is cover with palm does work for other things....if you want to return to dismiss whatever is on screen, and return to the watch screen, so the cover function works! And the phone calls can be answered or dismissed from the watch with a right or left swipe. Its just that function in zenwatch manager.
[Asus ZenWatch] nlwclark:
Here was my solution

I had this problem too, and found a solution.

PROBLEM: On my phone, in the Zenwatch Manager app, under the "Cover to Mute" setting, I would tick the box next to "Incoming call", then "apply", but when I would go back into that setting, the box would be unticked.

SOLUTION:: On the WATCH, start FoneHelper (touch the clock to get the main menu--where it says "speak now" up top--scroll down and press the menu item "start", scroll and press "fonehelper). You will then have the option to toggl "Cover to Mute." I was able to enable the setting from that screen.

*Incidentally, when I do it that way, I can immediately see that choice reflected on my phone, in the Zenwatch Manager App. I still cannot use the Zenwatch Manager to enable this setting, but I've succesfully done it via my watch multiple times.

Hopefully this is helpful for someone else as well. :)
[Asus ZenWatch] modelyacht:
Confirmed resolution!

That's it! Even Asus support was stumped, but that setting is the cause/solution!

Thanks for taking the time to provide such a well written response! Thanks again! +++
[Asus ZenWatch] dr_gibberish:
Thank you so much. Having the same problem and this totally fixed it for me!
[Asus ZenWatch] kual:
On Nexus 5 and Android 5.1 installed this does not help. Problem is, that Watch put Phone into "Interrupt priority" state, which allows only important events to ring or vibrate. But this setting does not prevent ring or vibration, which is already in progress during the incoming call. I tried to use Takser app to set Silent mode on, ringer off, vibrate off, interrupt mode to None - but none of them helped. It can mute the ringer, but not the vibration. But then i figured out the solution. First, you need a rooted phone. Then create Tasker profile for variable set event "%INTERRUPT~priority". This will trigger event, when Watch will set the phone to "interrupt priority state". Create a task for this profile to just simulate pressing volume down key: select Button action to do this. This will completly mute the call.

Also, ASUS support told me, that this issue will be fixed in android 5.1.1 in the middle of may.
[Xperia Z3 Compact General] fifadol:
Hi everybody especially Z3C Owners,

I am one of those who cracked their phone.

The Height of the fall is less than half a meter. less than 1.7 feet for NA members.

The touch is working ONLY in the bottom half of the screen >>> recognized but not always accurate.

I assume that any damage on the screen will result on unresponsive or at least a malfunction in touch sensor.

Fortunately the LCD itself is okay but local Sony service said it will at least cost 99GBP = 173.5$ which is waaaaaaaaay too expensive :crying:

Please is you have a damaged screen contribute on the survey :)
[T-Mobile Samsung Galaxy Note II] bumrocky:
I'm running stock 4.3 TMO ROM. SGH-T889

Kernel 3.0.31-2085660

Build T889UVUCMK7

I attempted to flash a KitKat 4.4.4 ROM (Cyanogen 11) but every time I do, I get "Sim Card Not Detected" and all the APN's are blank. When I try to enter a new APN, it just disappears.

All the IMEI and Device Info go to "Unknown".

I was able to restore the original ROM, and everything was fine. Outside of the SIM/Signal issue, the KitKat ran fine, too.

Do I need to flash a new radio/modem when I go from 4.3 to 4.4?
[General Questions and Answers] -MaoR-:
How does it work?

I mean.. I currently own an LG G2.

Everybody is waiting for the android 5 CloudyG3 port but it's not comming because there is no matching Kernel. So from what I understood, only when LG releases the Android 5 version to the G2, there will be a CloudyG3 ROM based on Lillipop.

But then I see my old Samsung Galaxy S running 4.4.2 on a custom rom, when the last official version was like 2.3.6.

So.. How come the G2 can't get the 5.0, but the SGS can run 4.4.2?
[General Questions and Answers] root-expert:
Just because the hardware can support higher version but the vendors want you to buy the new phones..! ;)

But the developers still can develop a 4.4.2 rom for galaxy S...
[General Questions and Answers] -MaoR-:
I know. What I ask is, why do we have to wait for LG's official Lollipop kernel so that LG G2 will get a lollipop rom?

Why doesn't it work the same with SGS?
[General Questions and Answers] root-expert:
Of course we can port android lollipop on LG G2. We can port for example CyanogenMod, or other roms.

I think there is an unofficial CyanogenMod rom for LG G2.