yashsingh1/xdaforums huggingface dataset:
[G3 Q&A, Help & Troubleshooting] mviktors:
an update

For the last two days I tried everything I can, so I'll try to explain every move I made. First of all, I tried every version from kitkat to lollipop, even I flashed the marshmallow update, but no success. ATM I am on lollipop stock rom, with root and TWRP recovery. I am using my mouse through usb adapter to navigate with the phone. I rooted my phone with kingroot app.

- The touch screen firmware version on my phone is -1, that was the case even before my screen got unresponsive, I can't figure it out how is this possible. I tried doing the same thing, updating the touch screen firmware but nothing happens when I click update through the service menu.

- I opened the back of the phone, reconnected the screen with the motherboard and turned on the phone - but no success. The situation remains the same. unresponsive screen.

So I am kindly asking for any advice or idea you have about my problem, how can I get my phone to work properly?

Does someone know where can I find a working touchscreen firmware for LG G3 D855? Is it possible to push the firmware to my phone using adb sideload or twrp?

At last, can a screen replacement solve this issue? I am 100% sure that this is not a hardware problem, all I need is to push a touch screen firmware on my phone.

Please help xda members!
[G3 Q&A, Help & Troubleshooting] Zmaja:
Hi mate, i have a same isue on my lg g3 d855 like you, did you find any solution for touch screen start to work again?
[G3 Q&A, Help & Troubleshooting] mviktors:
No luck, I tried all above mentioned and I am nearly given up from finding any solution by myself. If you somehow find some touch screen firmware on the internet or any possible solution about this problem, please send me a message or write a reply here. On Monday I am taking my phone to a mobile service, I hope that they can find what's the problem without changing my screen or motherboard...
[G3 Q&A, Help & Troubleshooting] myclarity:
Hmm, can you go to the service menu again and Hw test or something like that and see if it works? Something on the hidden menu must work..

My g3 is in a rough state too, best of luck for you mate.
[G3 Q&A, Help & Troubleshooting] mviktors:
I can access the service menu with my mouse, but my screen stays unresponsive after clicking on the update touch screen firmware option. :crying: The touch screen firmware version is: -1, clearly something is wrong with it. Don't know what else can I do in the secret service menu, my brother g3 went just fine updating the touch screen firmware... Running test does not solve the problem.

I think that some professional service can repair it with connecting on a special equipment and resetting the chipset and screen firmware ( similar to pc bios with programator).

Maybe it is possible to do it on a pc with adb , pushing through sideload the firmware of the touch screen, but I can't find any touch screen firmware for lg g3 d855 :(
[G3 Q&A, Help & Troubleshooting] myclarity:
Tell me the files you need and I'll try to help you :highfive:
[G3 Q&A, Help & Troubleshooting] mviktors:
hm, I don't know the specific name for the file needed, I can't find any touch firmware for lg g3 d855. Do you have any suggestion how can I do it? Is it possible to somehow pull the touch screen firmware version file from other g3?

I read on some websites about galaxy devices that were fixed with updating the Linux kernel to call the driver function that updates the firmware. I tried changing two kernels for stock rom on my g3, the situation remains the same.
[G3 Q&A, Help & Troubleshooting] myclarity:
If i was you, I'd get in touch with some kernel developer from the G3 or from those galaxy phones and try to explain your situation and kindly ask them if they could mod a stock kernel in order to force update firmware and test if it'd work.
[G3 Q&A, Help & Troubleshooting] mviktors:
Thanks for the advice, I'll try to contact some of the kernel developers for g3 d855. I would glad make a donation to someone who can help me out with this.
[G3 Q&A, Help & Troubleshooting] Zmaja:
im going to buy a mouse cable an try to look in hidden menu what`s went wrong. if i got any luck and somehow touch start to work again i will send you a post. thanks for posting me;)
[G3 Q&A, Help & Troubleshooting] mviktors:
I got my g3 back from the mobile service, with zero results. The touch screen cannot be fixed with flashing the software, they recommended changing the whole screen. The price is around 100 euros, a big sum compared to the phone price. I asked them to give me more time to think about, so I can make the right decision. I plan to take the phone to another mobile service for a second opinion.

The thing that bothers me the most is how can a touch screen firmware update destroy the functionality of the whole touch screen with one click.

Any advice is appreciated.
[G3 Q&A, Help & Troubleshooting] suljo94:
did you cse flash the kdzs they should overwrite everything you could also try the tot and dll way if that doesn't work screen replacement
[G3 Q&A, Help & Troubleshooting] mviktors:
Yup, I tried all above mentioned, cse flash, .tot method, .kdz method, kitkat, lollipop and marshmallow rom flash, nothing helps. I am running out of options, screen replacement seems like the only one left :(
[G3 Q&A, Help & Troubleshooting] Ninja243:
Hello, I've been having a similar issue to yours, only my entire screen stopped responding to input. I have noticed that the screen responds if I press harder (almost to the point that the screen starts discoloring), but even then it is unreliable. My phone is the LG G3 D855, and I am currently using Euphoria ROM and TWRP. The screen doesn't respond in TWRP either. I would also like to point out that I have not accessed the Hidden Menu since I bought my G3.

Do you have any advice for me? Any help at all would be appreciated.
[G3 Q&A, Help & Troubleshooting] mviktors:
I think that your problem is not the same as mine. I've got a firmware issue, my screen doesn't respond no matter how hard I try. You should check your connectors on the touch screen.
[G3 Q&A, Help & Troubleshooting] Zmaja:
Damn i gues we got bad lack, i try also all flashing metod(tot,kdz dll and nothing helped) :crying: second opinion is not bad idea. I cant wait to hear it. Stay well;)
[G3 Q&A, Help & Troubleshooting] Eliminater74:
I got your Messages, But what you explain about firmware is very strange.. My kernel it self uses the G4 touchscreen firmware.. The firmware is located in kernel/firmware/synaptics/g3 ..

also the phone it self has the blobs aks libs that also communicate with touchscreen.. when you said you tried everything.. I dont see how reverting to stock though kdz destroyed your phones touch screen.

pressing one simple button, I just dont see it... your root method was something I would never use.. but do you have access though twrp ? does it work then or still nothing?

Are you sure you went into download mode and flashed a fresh kdz? Download that app from the playstore that test touchscreen. and see if any reading are happening..

I used that app when I used the g4's touchscreen firmware.......... But everything works great for me....

msg me on hangouts if you need anymore input.. but as what I read.. it doesnt seem like a firmware issue. whatever you did effected the hardware totally............
[G3 Q&A, Help & Troubleshooting] mviktors:
Thanks for the reply, I'll try to explain the situation again as best as I can.

The phone worked without any problem on stock lollipop rom 5.0.2 and everything was fine after rooting, flashing TWRP recovery and installing Cloudy 2.5 with Xceed rom. The screen was responsive, just I noticed that after a phone call I can't hang up. I read on xda and other sites that Updating touch firmware might solve the issue, so I went to the secret service menu/ HW Test and I tried to update the touch firmware. After one simple click on the update button, everything went downhill. I tried several things, I am not an expert in this but surely not a noob at android mobile phones and flashing. This is my second LG phone, till September I had G2. Now I use my mouse through micro usb/ usb adapter to navigate.

A list of all the things I've tried:

- Going back to stock with flashing .tot and .dll file

- going back to stock with flashing stock .kdz file with lg flash tool 2014

- flashing different stock roms kitkat/lollipop/marshmallow

- Again rooting my phone and flashing TWRP recovery

- Flashed Blisspop custom rom

-Opened the back of the phone, reconnecting the whole touch screen with Phone on and off

No result!

The touch screen firmware version doesn't change at all. It says:

Touch Firmware Version:

-1

Read fail touch IC info

I don't know what the hell "Read fail touch IC info" means and is is possible somehow to be fixed?

I am nearly given up on the issue, but this can be helpful for other g3 users with the same issue.

Thanks to everyone
[G3 Q&A, Help & Troubleshooting] KronicSkillz:
The assertion that you are 100% sure it isn't a hardware issue is ridiculous. Now that that is out of the way why did you upgrade touch screen firmware? You also aren't very specific saying you tried to install touch screen firmware and then my phone got isn't very specific. I also don't understand the question about default settings doesn't the kdz include all firmware? if you already flashed the stock kdz and its not fixed you might be out of luck, maybe ask someone who knows alot about jtaging or something but i don't even know if that is possible for a touch screen. if you already hard reset the phone or flashed stock kdz's then maybe try upgrading the firmware again, if it is a bad firmware flash and for some reason the kdz didn't reinstall it why not try to upgrade it again hoping it is successful this time?. tip don't multitask or let your phone fall asleep during any kind of firmware upgrading from the android system (meaning if you aren't flashing from a custom recovery like twrp or clockworkmod.)

( you might have to use a usb adapter and a mouse to perform these tasks if your digitizer isn't working (ie touchscreen))
[G3 Q&A, Help & Troubleshooting] Zmaja:
Hi again mate, i have bad news for both of us, i got same information like you from authorized lg service in zagreb croatia, we need to change whole display but i didnt ask the price because this is mine second one from ebay and there will i buy the third one too :D i hope that information helped you to see your option what to do with your phone maybe ebay is not that bad solution because there you can find a display with frame and brand new one for 40$
[G3 Q&A, Help & Troubleshooting] mviktors:
Thanks for the info, can you share with me the link from ebay so I can see the screen you are talking about? Please send me a private message so we can continue this conversation.
[G3 Q&A, Help & Troubleshooting] Rocky-91:
I have the same problem with my g3. Will find the location of the file i need l8r and let you know if ya can send it? Will just have to find a way of replacing the 1 on my phone with it then lol.
[G3 Q&A, Help & Troubleshooting] SuRMaJ:
the same problem, update touch firmware killed touchscreen, Please Help
[G3 Q&A, Help & Troubleshooting] sinanco:
Same problem +1...

Sometimes touch screen can work with firmware details are OK and then suddenly touch response is gone and firmware details is read to fail like software conflict failure

Any solution? Any help will be grateful
[General Questions and Answers] Gutter3052:
So I wasn't very smart when it came to modifing and replacing the build.prop on my tablet...had it rooted with Kingroot and replaced the file with a modified one I opened on Notepad++ (Yeah, I know, I read that was extremely stupid of me.). Sure enough, I rebooted the machine and it's stuck at the Viking Pro screen... I thankfully have the original build.prop file, but my question is, how can I replace the file when there's no such option in the system recovery? Only have had it two days, and can't believe I already screwed it up.

**Edit**

Incase anybody else has had this problem:

http://xdaforums.com/showpost.php?p=64659280&postcount=139

Solution!
[Droid Turbo 2 Q&A, Help & Troubleshooting] rbird2:
When I did a web search for the XT1585 specifications and multiple sites state "FM Radio with RDS".

As far as I can see my Verizon XT1585 does not have FM radio. Is this a feature Verizon removed?

Is the hardware still there or did Motorola remove it.

Google Play states the "Motorola FM Radio" app is not compatible and will not let me download it to see if the FM Radio hardware is there.

Any one have comments or suggestions?

Thank you
[Droid Turbo 2 Q&A, Help & Troubleshooting] LenPer97:
I have the same issue. As I understand it, Verizon has the FM receiver turned off.
[Droid Turbo 2 Q&A, Help & Troubleshooting] romma1:
This would be great to turn on to save on data in certain situations. Plus radio apps block Pro sports unless you pay a subscription

fee.
[Droid Turbo 2 Q&A, Help & Troubleshooting] Zeljko1234:
I would say that xt158x doesn't have fm radio but there's is BTFM.bin file in the stock firmware...
[Droid Turbo 2 Q&A, Help & Troubleshooting] ArgentSouL:
Is it possible to change its ROM for the X Force .... ? Would that give it the radio back....?
[Droid Turbo 2 Q&A, Help & Troubleshooting] damkol:
Moto X Force don't have fm radio.

BTFM.bin is probably BlueTooth FirmWare.
[Droid Turbo 2 Q&A, Help & Troubleshooting] motophreak:
FM radio?

I contacted Motorola support through their warranty replacement number themselves and asked​ them directly and they said xt1585 does not contain FM radio chip. it wasn't Verizon removing it.
[Droid Turbo 2 Q&A, Help & Troubleshooting] mjones73:
No.
[Fire TV Q&A, Help & Troubleshooting] fecaleagle:
So I managed to root my 2nd generation Fire TV, and rather than doing the proper research, I downloaded and installed the stericson BusyBox Installer .apk from the Play Store (play.google.com/store/apps/details?id=stericson.busybox&hl=en). Seemed to work fine, but when I was looking into installing DropBear/BusyDrop and found it would be easier to use adbfire to install system tools and I no longer needed sericson's BusyBox. Well, not having spent much time with Android in general, I failed to realize how badly that uninstall was capable of going, and I have managed to mess things up reasonably badly.

So, naturally, I would like to revert to stock and start the process over. Seemed simple enough. I followed this guide (not written for the 2nd gen aftv):

aftvnews.com/how-to-unroot-a-fire-tv-and-switch-back-to-stock-updates-from-amazon/

(Appears I am unable to post links, as this is my first post here.)

Unfortunately, I've run into at least one problem, and very possibly two. The major problem is that the cache partition on the 2nd gen Fire TV is only 242.1M, while the stock image is ~470M. So I can't push the update image to the cache partition. I tried pushing it to /sdcard/, but didn't have any luck with recovering from there either. This leads me to the second problem, the guide is obviously written for the 1st gen Fire TV, and the contents of my system differ from those indicated in the guide. Where the guide indicates to push the image to "/dev/block/platform/msm_sdcc.1/by-name/recovery", I am finding "/dev/block/platform/mtk-msdc.0/by-name/recovery". I did push the recovery image to the path present on my system, but I am not sure whether to believe that recovery is failing to work because of the differences between the 1st and 2nd gen Fire TVs or because I am forced to push the update.zip to /sdcard/ rather than /cache/. I did modify the /cache/recovery/command file to reflect the new location of update.zip ("echo –update_package=/sdcard/update.zip > /cache/recovery/command").

Anyway, at this point, there's not a ton of documentation available on reverting the 2nd generation Fire TV back to stock, so I am hoping somebody with more familiarity with Android and the Fire TV can toss me a line (or a link).

Thanks,

William
[Fire TV Q&A, Help & Troubleshooting] fecaleagle:
Edit: Okay, so I found the correct images for my device on zeroepoch's site. I'm assuming at this point that system.orig.img is the update.zip (it's currently downloading), and I now know that I was definitely using the wrong recovery image for my system. Still, I will not be able to put the update.zip in /cache/ because of the space limitation on my system. Once I load the correct recovery image, will I be able to follow the steps here (http://xdaforums.com/showthread.php?t=2799779) and just perform a factory wipe/reset?

Thanks!
[Fire TV Q&A, Help & Troubleshooting] ImCoKeMaN:
You can't use recovery at this point to revert an AFTV2 to stock so that thread will not work. It's also not an update zip it's a full /system partition image. You need to dd the image as root to revert. Actually if you are just trying to get to a clean rooted state you should dd the rooted image instead of the stock one.

There are some guides that cover the dd steps with the images, for example the first post of the root thread, along with other comments about it depending on what version you are on etc.
[Fire TV Q&A, Help & Troubleshooting] fecaleagle:
Thanks for this! I'm really glad to know that recovery is off the table for my model (in the sense that I can move on to an approach that works) and also relieved that I can simply flash the entire rooted image with dd. I am reasonably comfortable with dd, so I will seek out the guide and go that route. Very much appreciated.

I've rooted Androids in the past but never owned one, so it's been a bit of an adjustment for me. Looking forward to getting another chance to take my time and get somewhat closer to doing it right this time around.

-William

Edit: Just read through the relevant section of the original guide and will be pushing and dd'ing the rooted image from [MENTION=3411776]zeroepoch[/MENTION]. Thank you so much for your help.

Assuming adbfire is not yet fully compatible with the aftv2, is the better approach to simply use the busybox build on [MENTION=3411776]zeroepoch[/MENTION]'s page? My goal is to get DropBear or any sshd running at boot time so that I'm not limited to accessing it with adb and have the option of using an ssh client app as a terminal on my television. I will relocate these questions to other threads if I am unable to find reasonable answers to them by searching and RTFM. Thanks again for everything.
[Fire TV Q&A, Help & Troubleshooting] thepacketslinger:
Thanks for this, I was running into the same issues you were seeing with the cache partition being too small. I'm trying to get a custom recovery installed so I was trying to downgrade to an earlier version.

Is there any way to get custom recovery working on the ftv2?
[Fire TV Q&A, Help & Troubleshooting] fecaleagle:
I wasn't overly concerned with loading custom recovery, and [MENTION=394912]ImCoKeMaN[/MENTION] seems to suggest that there aren't any options yet for aftv2, but dd'ing the rooted image gave me a rooted stock image, and that was all I was looking for. It is a bit of a concern though, because it basically means you're hosed if the system won't boot. I was unable to get it to boot into recovery mode at all, but that may be because I tried to install ClockWorkMod with adbfire. I have not checked on it since the restore, but I was just pleased to be able to flash a rooted or stock image back onto the device.

I'm assuming we'll just have to be careful until custom recovery for aftv2 becomes a reality. I'm using [MENTION=3411776]zeroepoch[/MENTION]'s busybox binary as well, and everything is going smoothly this time around.
[Fire TV Q&A, Help & Troubleshooting] rbox:
I am working on recovery. Should have something out soon. Although I don't know what you are going to downgrade to.
[Fire TV Q&A, Help & Troubleshooting] thepacketslinger:
Gotcha. I was only looking to downgrade as a path to getting recovery installed, but it looks like that's not an option. Thanks for clearing that up!
[Fire TV Q&A, Help & Troubleshooting] thekwijibo:
Wondering if there is any updates on this. Currently have TWRP and a rooted ROM on my AFT2, and I'm throwing in the towel with its impossible interface and user/dev hostile environment. Looking to return it to factory for refund.
[Nexus 6P Q&A, Help & Troubleshooting] Nath5:
I just went to backup my stock ROM and noticed that twrp now lists system and system image. What is the difference between the two / do both need to be backed up and restored. Also what is contained in the vendor partitions.

Thanks
[Nexus 6P Q&A, Help & Troubleshooting] nhizzat:
http://www.androidpolice.com/2015/0...creating-ota-friendly-system-images-and-more/
[Tilt, TyTN II, MDA Vario III General] ID64:
Does anyone else thinks that BT headset sound is a bit tiny? There is no low frequencies present that makes sound a bit harsh. I am comparing it with HTC Excalibur and Trinity. Is there a way to adjust this parameter via registry?
[Tilt, TyTN II, MDA Vario III General] J273:
Yeah i thought this....Ive been using my bluetooth stereo headset and ive also tried the wired headset.

Im sure this was the same on the tinity though wasnt it when it was first released.
[Tilt, TyTN II, MDA Vario III General] ID64:
Stereo headset works fine for me with plenty of Bass. It's a regular BT headset that I am talking about. Both Jabra JX 10 and Nokia BH 900.
[Tilt, TyTN II, MDA Vario III General] kilowong:
i have jx10 and everything was great with regular phone conversations, even the voice button works.

i have not try the stereo bt headsets so no comment on the music side.
[Tilt, TyTN II, MDA Vario III General] J273:
when you say stereo headset...do you mean the bundled mini USB headset included with the Kaiser?

Thanks
[Tilt, TyTN II, MDA Vario III General] kilowong:
no i mean stereo Bluetooth headsets. my jabra jx10 is only mono (one side), some BT has 2 sides (L&R) stereo for musics.
[Tilt, TyTN II, MDA Vario III General] J273:
Sorry yeah i misread the first post .

I actually thought though with the standard bundled USB headset the sound was a little tinny.

with my stereo DS970 (se) headset the sound is fine.....I was talking about the standard USB headset.

sorry guys misread the first post.
[Tilt, TyTN II, MDA Vario III General] ID64:
anyone have registry keys that can be tweaked to make BT mono sounds better?
[Tilt, TyTN II, MDA Vario III General] ID64:
Guys, this is the first HTC device with this kind of problem! It really drives me crazy. Am I only one who annoyed by this?
[Tilt, TyTN II, MDA Vario III General] maikenhead:
I'm having the same problem with tiny BT sound over A2DP. I'm using an i.Tech S.38 which works perfectly apart from the VERY low volume (volume sliders in actual programs and volume control on S.38 are set to full.). When I pair the S.38 with my laptop the volume is much higher.
[Tilt, TyTN II, MDA Vario III General] rmanulkin:
Welcome to the club

We've already been discussing the poop out of this at

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

Really unpleasant feature.
[General Questions and Answers] dhaddow:
Anyone know if this tablet can be rooted. It's running android 5.1

Thanks

Duncan
[General Questions and Answers] dhaddow:
Anyone manage to root this device yet?
[General Questions and Answers] dhaddow:
Finally got it rooted. Used Kingroot on computer, it took 2 attempts. After rooting ran super sume pro to get rid of kinguser and install super su.
[One (M8) Q&A, Help & Troubleshooting] rsm23:
Hi, this could be asked before or for the first time but I was searching without finding a good solution.

Is there any chance to convert my HTC One M8 from Android to Windows Phone?

If it is possible did someone tried it before.

And thank to everyone.

Best Regards
[One (M8) Q&A, Help & Troubleshooting] Mr Hofs:
http://xdaforums.com/showthread.php?t=2694141
[One (M8) Q&A, Help & Troubleshooting] rsm23:
This is not what I'm looking bro