Develop Bugs

[Q] I need serious help here my phone is broken

I have tried to flash my phone to EB13 new 2.2 Froyo. I have rooted my Epic 4g using the one click method a long time ago and never had a problem. I tried all steps on previous posts (http://forum.xda-developers.com/showthread.php?t=963652) and nothing seems to help. I have done the following to update to 2.2 Froyo:
1) I tried to do the update.zip file method. I went to recovery mode and did as you all stated and would return with errors.
2) I have tried to use the odin method (this is where my phone got broken.)
a) I have done all the steps that you guys posted; and odin would return as failed.
b) In odin i have done the following: (Odin recognizes my phone and i have the yellow box and it uses "com6")
I) made sure that the only box that should be checked is Auto Reboot (i didn't know this until the second time i ran odin so the F. Reset Time was checked by default the first time around)
II) the first time around i only placed this file (SPH-D700-EB13-8Gb-REL.tar.md5) in the PDA box. And it returned with errors. (this is where my phone got broken; i realized it when i tired to turn on my phone to call someone)
III) At this point and time i said screw 2.2 i just want my phone back up and running and tried to do your methods to return to stock using these steps (http://forum.xda-developers.com/showthread.php?t=773032)
IV) it doesn't work at all. I can still go to the Downloading section of the phone doing the #1 and then power button. and at times i can go to recovery mode (when it wants to) but nothing happens. i get these icons while trying to turn on my phone "a phone with a computer next to it"
c) in Odin i have noticed that it takes an extreme amount of time while in the Param.?? (this takes about 8 hours and than returns with a "red fail" in other occasions it gets stuck on "initializing"
d) Odin is not working for me!!!!!!
3) i have also tried the samsung update method (since odin doesn't work for me)
a) i have done all the steps that samsung says and it all passes until i get to the "start download" section.
b) after i press "start download" it stays in idle for a long time than goes to that param.?? and it wouldn't go anywhere and it stayed there for a whole day and nothing ever happened.
Please guys i have had no phone for 2 days now and i need my phone for work and i need my phone by Friday. If there is any help you guys can give me it would be appreciative or else i would have no choice but to go to sprint store and get me a new phone or have them fix this issue and i don't want to be penalized for messing with my phones OS. Please return with suggestions and help me fix this asap.
*Note: My phones Drivers are all installed using you driver download link and i am using Windows 7 64bit.
Thank you in advance!

Try again with a different USB cable. If you are sure you got the drivers installed properly
Sent from my SPH-D700 using XDA App

win 7 64 bit drivers
Here are the drivers I used to Odin my Epic with Win 7 ultimate 64-bit. I put the zip in my google documents.
https://docs.google.com/leaf?id=0B8DFupwiCOXyMGViMDJmY2MtMGU4YS00MGY5LWFkOGItNjkyMDY3MjkyNjgx&hl=en
I used the eb13 from here :
http://forum.xda-developers.com/showthread.php?t=853209
using this tar : Stock EB13 Deodexed EXT4 + CW 3.0.0.6
Also, check your usb connector. there are pins in it that can bend and prevent a good connection. I have read a few posts here on XDA where people had to straighten things out.
Good luck!!

Uh, ouch.
SPH-D700-EB13-8Gb-REL.tar.md5 is not the same file as SPH-D700-EB13-8Gb-REL.tar
Flashing the wrong file is a very good reason why your odin attempt did not work.

I will try this out im having my fingers crossed. Hopefully it works out.
Just to be clear....
I have re-downloaded the 64bit drivers for Win7.
Now in Odin what do i have to put in "PIT"?
Do i use "s1_odin_20100512.pit" for the PIT tab?

Results:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
why is this happening? I did all what u guys requested to do.
I used a new cable

Thank God! Its working!!!!!
All is working well for me Thank you so much guys and special thanks to you jdelano for your help.
My last question...
Is this rooted already?
let me know.
Thank you guys!!!!

So I just tried this because I couldn't get CW3 on my phone without it being all funky. When I would do it before I would have android flashing over the sprint bootup. This only has the android showing. Did I do it right?

[Q] Galaxy Nexus (Maguro) showing signs of life, though still at yellow triangle

HI, n00b alert for starters
So went on a longer trip the other day, needed to use GPS on my rooted GNEX running AOKP 4.2.2 (its been a month plus now, but as far as I can remember, last kernel was Faux), when the device started to reboot randomly, sometimes straight from the GOOGLE logo, sometimes from within the OS, the longest it kept running being 10-20 mins. The display had sometimes a purplish hue when the system crashed, rebooted to GOOGLE logo w/ unlock icon, and booted normally. Since I thought it could be a hardware issue (remember reading GNEXs had problem with processors comming off the mainboard?), I wanted to have things back to normal/original before claiming warranty (haha, try to claim one with a broken glass), and for other reason to rule out possible FW/SW errors. Now this is where it gets tricky, since some time allredy passed: I updated via adb/GNEX TOOLKIT to the stock image of 4.3. Phone got stuck at GOOGLE logo, I was able to to get to fastboot, which I on one occasion somehow mistook for the fastboot mode, then I came across the idea of using ODIN without previous experience, and thats where things have gotten really bummed. I suppose I might have flashed wrong version, since the only thing that came up since then, is the "phone" /!\ "PC" screen. Since there was no way of getting into adb, fastboot, I decided to take a try and bring it to the dealership where a nice lady took the piece to the back room and came back with a suggestion of (equivalent of) USD 15 for repair. What a price for geting rid of such pain... When I came to pick it up, a sorry face greeting me said it all... No cigar... Never been told what they actually did, never really asked, since the symptoms were still the same. Then I let it sit for couple more weeks, then decided to have a second chance with it, since the screen comming up and at least some sort of acknowledgement by PC still gave some hope. I tried couple of ODIN methods found here as well as elsewhere, like CF-Root-GGN_YAKJU_ICL53F-v5.1, with no luck, the progress bar on display got either stuck after first 1/8", or went all the way through, but after time for settling, still just the triangle screen. Then I went to a H/W store, built a jig with MicroUSB A+301k (1% tol), which still brought me only to the yellow triangle. Then last night I started fondling around with OMAPflash: Downloaded the tuna zip file, pulled battery, started the batch, and voila all smoth, no errors, then I let the phone sit for some time only to boot to the triangle again! Tried this a couple of times more, same result. All the time, ODIN and OMAPflash, I used only 2 of my laptops USB ports. Then, for some reason, I used a port I hadnt used before, and voila, ODIN shows PASS! in 2:02 - 2:03 mins, but the thing still boots only to trisngle again! Between these tries, I randomly used the jig again to try if anything has changed, but still cant get to Download/fastboot. All this time, when I connect to pc, I keep getting various devices, mostly Samsung USB modem, with battery out and plugged in cable, the OMAP4440 device pops up intermittently to vanish after 2 secs (normal behavior as I read, OMAPflash still says its capable of downloading, gets its chore done, but then lets me sit there with the triangle again. Im slowly running out of Ideas (OK, Im tottaly out of ideas on what to do next, I came across a posting where a guy is suggested to have the JTAG done by, but it seems to me that the symptoms arent that bad to have it JTAGed. Yet. What would you suggest to do-try?
ODIN result after flashing CF-Root-GGN_YAKJU_ICL53F-v5.1.tar:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!
Thanks for your energy spent on reading/answering this LONG post, any help greatly appreciated. PS: As a thank you, I am willing to spend couple bucks on charity of your choice (fund your beer yourself, there are bigger issues in this world / excuse possible typos, my keyboard sucks big time / and greetings from the Czech Republic!

[Q] Should I give up on my SGH-T999?

To start out, some basic information. I got my SGH-T999 about 2 years ago and used it for about a year on the Stock ROM before proceeding to root the phone. The firmware version before things when went wrong was android 4.1.2. Everything was working fine until about a few days ago when the phone would stop being responsive after putting it into sleep mode, or the screen will turn black and the whole unit is unresponsive (the latter only occurring while I was in the home screen, not while running any apps. Rather, the phone would be fine while an app is running).
Troubleshoot Stage 1
Initialy, I thought there was some sort of app update that was causing this problem, and so I tried uninstalling a few apps that might have been culprits. Didn't work. On occasion, the phone would freeze up while i was trying to uninstall the app. So reading around, someone mentioned that it was possibly the TouchWiz Home that was acting up and I should, clear cache. So I rebooted into recovery (I had the clockworkmod recovery from the initial root). Cleared user data/factory reset as well as clear cache. Didn't work. At this point, the phone was restarting itself almost instantly after booting into the lock screen. I searched a bit more about why this would happen, and came across a post saying that I could be a faulty power button. I actually didn't want to physically alter my phone in any way, so I decided to try to do something with the software first before resorting to altering the physical phone.
Troubleshoot Stage 2
Next thought process was that maybe somehow an OTA was pushed onto my phone and now the firmware is screwed up because of it. So reading through many posts on XDA, I came upon this thread (http://forum.xda-developers.com/showthread.php?t=1771687) for a pre-rooted version of 4.3. I figured, if I was going to re-flash the firmware, I might as well go to the latest one. I proceed to go through the process of flashing the firmware with Odin 1.85, leaving Auto Reboot and F. Reset Time checked. Odin flashes PASS message and I unplug the phone and wait for the reset. Phone starts up all the way past all the logos and to where the home screen was supposed to be. But there was no home screen, just a black screen with only the pull down menu at the top and a message saying "Unfortunately, Settings has stopped working". This message would keep repeating even after pushing the ok button. Next thought process is, maybe TouchWiz is acting up still. So I boot to recovery, reset/format to factory, clear cache, and reboot. Now the phone wont boot past the Samsung logo. Tried to boot to recover again, phone won't boot to recovery anymore. Tried to re-flash the same exact firmware again and this time, odin had some trouble. It would sometimes stop working where it is loading the main code at which point I check the task manager to see if it is still running processes or utilizing any of the computer resources to communicate with the device. I would then have to unplug the phone and reset by removing the battery. This kept occurring about 2 more times before it successfully finished and on doing so, the original problem when I first flashed it was still there.
Troubleshoot Stage 3
Ok, maybe my phone doesn't like the pre-rooted firmware. Looked around XDA again and found this thread (http://forum.xda-developers.com/showthread.php?t=1949687) and downloaded the stock firmware. I stayed with android 4.3 because i read that I can no longer downgrade to a previous android version. Proceeded to flash the Stock firmware 4.3 using Odin 1.85. The process completed on the first try. SUCCESS!! Boot up phone, got past logo, home screen appeared. SUCCESS!! Here, I thought that I was done and my phone was finally working again. So I begin to tweak the settings for my own preferences. I didn't flash anything else or try to root the phone again. I was just plain using the Stock 4.3 firmware that I got from the thread above. After about 10 or so minutes of using the settings, the phone freezes and becomes unresponsive. Won't restart by holding the power button or return to the home screen with the home button. Only other option was to remove the batter and restart the phone. This time, the phone doesnt make it past the Samsung logo screen, and I can no longer boot into recovery. It was stuck on a boot loop and could only be turned off by removing the battery. It didn't occur to me that I should flash Clockworkmod Recovery to reset/format to factory and clear cache as I have read previously and thought that I could just re-flash the stock again. Nope, the same issue came up in Odin as it did with the pre-rooted firmware. Again, I went through the process of checking that Odin was no longer communicating with the phone before unplugging and restarting the procedures to flash the firmware. After about 3 times, the 4th time after unplugging, the screen that tells you "Firmware upgrade encountered an issue, Please select recovery mode in Kies & try again". And when I try to flash again using odin, I get the following message
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Troubleshoot Stage 4
New problem! I now no longer have a PIT partition........and reading around, I found this thread (http://www.sammobile.com/forum/showthread.php?t=15719) of someone who has the same error message coming up in Odin. Thus, I found the PIT file via this thread (http://forum.xda-developers.com/showthread.php?t=1848267&page=4) using the link given by DocHoliday77. Downloaded the T999_16GB.pit as the back panel of my phone indicated that the phone was 16GB. I begin trying to flash with Odin 1.85, checking Auto Reboot, re-partition, and F. Reset Time, including the PIT file and using the Stock 4.3 firmware. This didn't work and only came up with the following error message
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Set PIT file..
<ID:0/012> DO NOT TURN OFF TARGET!!
<ID:0/012> Complete(Write) operation failed.
<ID:0/012> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Tried, the same procedure with the pre-rooted 4.3 firmware, still the same message. And haven't gotten past this point since.
Looking back at what I choose to do to try an fix this shutting down problem, I realize there were a few things I could have tried before moving on. But now what I really want to figure out is whether or not my phone can be saved. What have I not tired and what is the end of end to rescue this phone or if its even worth rescuing. I read that JTAG would be the final resort, and I will take that into consideration. Any feedback on what procedures I could've missed would be great as well (for future reference). Thanks for reading this long post and I really do hope I can get this resolved.

I'll try to answer some of this but tbh, tl:dr.
I can very much appreciate a very thorough and detailed post when someone is asking for help. Don't take this the wrong way, but this was a bit much. I could've answered hours ago, but didn't have the time to read it. More importantly though, the majority of people will see how long it is and just close the thread and move on. Like I said, details are good to include, but it gets to a point where it's too overwhelming. Right now I don't even remember a good chunk of what you wrote, and I wasn't able to read it all to begin with.
Not trying to lecture you or anything, but wanted to address it in case it can help you in the future.
I'll try to answer what i can real quick... first, don't use Odin 1.85. That is a very old version. You should only use 3.07 or above. Best to stick with 3.09 or 3.10.
Try the pit file with one of those.
Put the pit file in the pit section and make sure re-partition is checked. Put the firmware in AP. F-Reset time and auto reboot should also be checked, but nothing else.
It does sound a lot like a faulty power switch probably caused all of this. The constant rebooting, crashing and boot looping can and will cause corruption. This is probably what happened to its internal pit. if so, it is very highly likely there is more corrupted data on some of the individual partitions. Depending on which ones, you may or may not be able to fix it without a jtag service.
It is also possible the memory itself could be damaged. If this is the case, the only option is a motherboard replacement. You probably won't know this for sure though unless you try a jtag repair and it fails.
I will say that if the power button is faulty, you should absolutely get that fixed before doing much else. Otherwise it could just bring you right back to where you are now.
If it were me, I would look for a device on ebay with a broken lcd, but a good motherboard with clean imei. Then swap the board. Otherwise it seems to me you'd be spending money on repairs that may or may not work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Thanks you so very much for the reply! Sorry that it was long and looking at it again, It really is TL: DR. I will keep that in mind for any future posts.
I have tried different versions of Odin 3.04, 3.06, 3.07, 3.09. The first two version also give the same message as version 1.85 while the latter two stall at initializing for more than and hour and there doesn't seem to be any progress. I will try Odin 3.10 and see what happens there.
I guess buying a broken LCD phone would be the best course of action cost-wise afterwards if Odin 3.10 doesn't work. Again I really can't thank you enough for all the help and taking the time to read my post.

Quick tip on buying used devices like that...Be Careful! Pay extra close attention to how every listing is worded. Only buy ones that say things like:
Fully functional except display
Powers on but no picture
Some will try to trip you up by using "clever" phrases, or trying to lead you to assumptions. Also, try to only but from sellers with excellent ratings and a large number of them. They will be more likely to help you if you have a problem.
Good luck!
Sent from my SGH-T999 using Tapatalk

Death S4 mini / hard brick

Hi, suddenly my S4 Mini crashed and it doesn't boot up anymore.
It doesn't enter into recovery mode, but enters into download mode.
So I flashed i flashed the stock firmware via Odin and the procedure freezes in the beginning, so i tried 2-3 times and now my phone is a paperweight, completely dead.
How can I fix it? the JIG USB will resolve the problem?
Thanks
Bye

I got same issue 1 year ago. My phone getting Samsung logo and restarting all the time. I flashed many roms in 1 day. Phone getting hot while flashing rom. Also weather is too hot. Unfortunately i burned my phone's hardware partition (I think I burned baseband).
I thought I gave my phone to phone repair shop which has jtag. I don't want to gave it Samsung service because I lost my guarantee with rooting it. But my father said "you already have guarantee. 2 years didn't exist after you bought your phone. You should gave your phone Samsung service"
I gave it to Samsung authorized service. I said that I was upgrading my phone via Kies. (I was too excited while I was saying this) After that my phone couldn't turn on. (I know I told lie but I need to get fixed my phone without money ? )
After 3-4 day i went there again to take my phone. They gave my phone and told me "your phone's mainboard and sub (charging input socket) were changed.
I was shocked ?. They didn't controlled my phone if it was attained knox counter.
Sorry for my bad English.
Maybe I can't help you but I wanted to share this event that I lived it.
GT-I9190 cihazımdan Tapatalk kullanılarak gönderildi

Odin blocks in this point:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9195XXUAMF5_I9195ITVAMF2_I9195XXUAMF5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> tz.mbn
<ID:0/008> NAND Write Start!!

Same thing happened to my S4 mini Duos on 11th February. My phone was on Stock Samsung Firmware, Custom Recovery, Custom Kernel, and of course rooted.
I changed to stock in December. It was working fine for a month. I texted my friends and after 15 minutes I took out my phone to make a call and I found it was powered off. Then I tried to power on. No response. Then I charged the battery using external battery charger as my phone was not showing charging logo.
After some time, it showed logo and entered Download mode. But didn't enter Recovery mode.
I did a complete flash (nandroid erase all) through ODIN. Not entering custom recovery as well as stock recovery. It shows "recovery booting" but restarts right after that. Stuck on Samsung logo. Just vibrates and reboots again and again.
I gave the phone to a Samsung Authorized Service Center, they declared my phone as hopeless. They say the motherboard is faulty and it needs replacement.
I never even dropped my phone or overclocked the cores. I had been using it gently. I really don't know what to do now. Here I am, looking for a solution.

So, I see that there are more and more people with a same problem and there is no clue what is the cause of the problem. I started a topic with a same question about month ago, but without any reaction.

Hi... I got something similar going on.
Samsung s4 mini running CM13 NIGHTLY (cm-13.0-20160214-NIGHTLY-serranoltexx.zip) Yesterday, I Downloaded Feb 18th nightly and decided to update other apps as well.
Today, as I updated some apps on the play store and got "insufficient message". Decided to make SD Card part of internal memory. Went thru the process and it transferred about 3GB into the SD Card. Afterwards, I proceeded with the CM update. A small screen came up saying it was preparing for upgrade and then it rebooted in recovery, as usual, but this time it blacked out. It just wont go into recovery mode.
Should I try to boot with a different SD Card with the CM update? Is there a way to do it on download mode?
Any suggestions would be great! thanks

Data recovery after Water Damage

My Galaxy S6 recently took a dip in a lake and would not turn on. After trying to displace the water with 91% isopropyl alcohol and I tried to power on again, but no LEDs and would not bootup still. I disassembled the phone and tried cleaning the board with a toothbrush and alcohol to clean any corrosion and hope that my attempts to turn it on did not permanently damage any components. After the cleaning the LEDs turn on, but the screen seems to be damaged.
At this point salvaging the phone is not a priority, some very important and irreplaceable pictures that were not yet backed-up are my only concern. When I connect the phone to my PC the MTP connection is established, but trying to connect with Samsung Smart Switch gives me a connection error and fails every time. I have installed the drivers and reinstalled the drivers, but the phone simply won't connect. Are there any alternatives to try on the software side for trying to recover the files? I imagine it is likely the faulty hardware that is causing the error, but I would like to exhaust all options.

You seem to be in luck. The reason it's failing to connect is because of that "allow/deny" prompt. I would suggest getting a custom recovery flashed then using the recovery mtp to get your files. But good job using IPA instead if rice, which does nothing. Lol. So once you get past the mtp block, you should be okay. In recovery you can even run terminal commands.
Sent from my SM-G920P using Tapatalk

elesbb said:
You seem to be in luck. The reason it's failing to connect is because of that "allow/deny" prompt. I would suggest getting a custom recovery flashed then using the recovery mtp to get your files. But good job using IPA instead if rice, which does nothing. Lol. So once you get past the mtp block, you should be okay. In recovery you can even run terminal commands.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
OK, I have been trying to flash twrp with odin, but it keeps failing. Here is the log
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Is there anything left for me to try?

ajvogt42 said:
OK, I have been trying to flash twrp with odin, but it keeps failing. Here is the log
Is there anything left for me to try?
Click to expand...
Click to collapse
Welp. You seem to have OEM unlock turned off. So its not letting you install the recovery.. The only other thing I can think of at this point is to get an MHL adapter. This will allow you to see your screen on a tv and then you could figure out where to touch to click things, if the digitizer still works..

I dontn know if it helps i just aquired a s6 water damaged. I was able to clean the contacts and reassamble and phones like new now runnin on a month

TheMadScientist420 said:
I dontn know if it helps i just aquired a s6 water damaged. I was able to clean the contacts and reassamble and phones like new now runnin on a month
Click to expand...
Click to collapse
I think he tried that already. He got it to power up and that's about where he's at.
Sent from my SM-G920P using Tapatalk

Yea i was readin after i posted. I guess i got lucky. I got this one for 20 bucks. Wd40ed the contacts with a qtip. And it worked.
---------- Post added at 10:52 AM ---------- Previous post was at 10:49 AM ----------
I got a lifeproof coming for it and some of the moisture eliminators. Im puttin one in the lifeproof with the phone to try to eliminate any moisture in the air in the case. Im a long time lg user. And i cant believe that my wife s5 is highly water resistant and then the a6 has absolutly no resistancy at all. Ive been readind that even air moisture has caused failures in this device. Sounds like samsung is going down with lg.