Develop Bugs

[Q] cant get further than download mode, but odin wont recognize phone, kies no help

alright, I have had my et4g for about a year and a half now, I have successfully flashed probably close to 100 times if not more, back and forth from GB to ICS, NOT because Im actually smart enough to know whats going on, just that Im smart enough to read and follow the steps you smart people lay out for me in your posts.
I am also pretty sure I have gone back from JB to GB before but I dont remember for sure. I was currently running FK23 and wanted to revert to EL29 and just get whatever the latest official build was onto the phone because I was going to sell it since I just upgraded. AND heres where the problem came, I was doing the restore one click el29(same computer/cable/file I have always used) and everything was going fine and out of the corner of my eye I noticed the monitor dimmed a little bit (didnt sleep or anything, just dimmed. on a laptop that was plugged in) and not sure if thats when it happened but I saw the red fail, the bar on the phone was SO CLOSE to completed its not even funny, but it just continued to sit there. I noticed at the end of the script was a series of "removed" "added" and ended at another "removed".
I can get it into download mode but 2 different computers, 2 different odin OC's, 2 different cables, full odin, nothing recognizes it. when I plugged it into the other computer the computer played the sound and brought up a notification that the usb device had malfunctioned.
tried to use kies as well because when trying a normal boot it says "firmware upgrade encountered an issue. please select recovery mode in kies & try again" but it doesnt recognize the phone either, and I have no recovery code to try.
I have searched and found NUMEROUS threads about this problem, most never were resolved, ALL that were resolved were other devices or they could still boot, or something else.
I have no idea where to go from here, can anyone give me some help?
thanks in advance

Is it possible that the USB port on the device has finally kicked the bucket? Check the pins. See of they are lifted, bent, broken, etc. You can also pull the device apart and check the solder joints on the port. They could just have a bad connection on one of the data leads. Another thing to try, get a full stock flashable restore zip file and place it on your external SD card. Rename it to "update.zip" then in CWM or the stock recovery hit apply update from SD card.
Sent from my SPH-D710 using xda app-developers app

volume up + power just takes me to the "firmware upgrade encountered..." message, no way to get to recovery. looking in with a flashlight the port seems to be fine. now it has been acting up lately where it wouldnt charge if the cord was coming out at a little bit of an angle. it really only was happening with this dirt cheap car charger I got off monoprice though and Ive still been able to transfer files and charge for quite some time so I figured that wouldnt be the problem, especially when the problem happened in the middle of it having a steady connection for ~20 minutes prior to the issue.
know of a source to buy a cheap port I can try and repair myself (Im better at that sort of thing than messing with software so I think I might be able to do it)

maddmatt02 said:
volume up + power just takes me to the "firmware upgrade encountered..." message, no way to get to recovery. looking in with a flashlight the port seems to be fine. now it has been acting up lately where it wouldnt charge if the cord was coming out at a little bit of an angle. it really only was happening with this dirt cheap car charger I got off monoprice though and Ive still been able to transfer files and charge for quite some time so I figured that wouldnt be the problem, especially when the problem happened in the middle of it having a steady connection for ~20 minutes prior to the issue.
know of a source to buy a cheap port I can try and repair myself (Im better at that sort of thing than messing with software so I think I might be able to do it)
Click to expand...
Click to collapse
It might auto flash it at that point if it scans and detects "update.zip". I may be wrong though... Ebay will have them. I will think of some other options and report back. Last resort is to J-Tag it if even replacing the port doesn't work and there is nothing you can do with software. Either that or replace it with insurance and tell them you were updating to the newest ICS.
Sent from my SPH-D710 using xda app-developers app

well, didnt know what JTAG was, looked it up and looks like I have to send it off somewhere and pay 40+ bucks plus shipping to possibly get it fixed, to probably not sell the phone for THAT much more, so if it comes to that I just might leave the phone in its current state and forget about it. Ill try the port first though, and anything else you(or others) can think of trying. also I dont have insurance, I dont get it on my phones. I used to but by the time Ive had the phone for a while plus the cost of the deductible I could just buy a nice one off contract on ebay or something anyways. and this is actually the first time in a very long time I would need to make a claim. last time I would have needed to file it lost/stolen/broken was back on cingular when I had that wierd spin open walkman phone because it fell apart. and monthly insurance costs since then could buy me a couple new phones by now.

also, could it be that the usb port finally crapped out if the computer sees it every time I plug it in, it just says the usb device has malfunctioned. Im trying to find an update.zip to give a shot right now also, so far they are very specific on the condition of the phone to flash (must run this version, usb storage off, usb debugging on).

auto update.zip was a no go

try a 3rd cable

well, I can give that a shot but I used both cables to successfully transfer files from the wifes et4g to the computer that I am trying to fix my phone with, so I know the drivers are in there to recognize the phone and the cables work with another phone of the same model.
last night I tore the phone down and just made sure everything was clean and connected. none of the data connections behind the usb port were damaged, or inside the port but who knows about the part you cant see. anyways the phone still turns on and shows on the screen so I didnt make it worse. I ordered up a new port last night also so I guess as a last resort I am going to try that. I did notice that the moisture indicator on the inside of the back panel that pops off when dissasembling the phone shows it has gotten "wet", but I know its never sat in a puddle, never left on a counter with a spill. I have talked on it in the rain (inside the hood I was wearing) and also gotten some rain drops on the screen while I was dialing the number in the rain or checking a text in the rain but I just wipe it off and put it back in my pocket, which might have been a little damp from the rain, so how sensitive are these things, humid air must be enough to trigger the little purple "x"s then, right?

I had a Nexus S that quit working. Like your phone, it would go into download mode but none of my 3 computers would recognize it, but they did recognize my og Epic. Turned out the internal memory went bad without warning. It was still under factory warranty so I sent it to Samsung and they replaced the mainboard. I hope your problem is something simpler.
Sent from my SPH-D710 using Xparent Cyan Tapatalk 2

maddmatt02 said:
well, I can give that a shot but I used both cables to successfully transfer files from the wifes et4g to the computer that I am trying to fix my phone with, so I know the drivers are in there to recognize the phone and the cables work with another phone of the same model.
last night I tore the phone down and just made sure everything was clean and connected. none of the data connections behind the usb port were damaged, or inside the port but who knows about the part you cant see. anyways the phone still turns on and shows on the screen so I didnt make it worse. I ordered up a new port last night also so I guess as a last resort I am going to try that. I did notice that the moisture indicator on the inside of the back panel that pops off when dissasembling the phone shows it has gotten "wet", but I know its never sat in a puddle, never left on a counter with a spill. I have talked on it in the rain (inside the hood I was wearing) and also gotten some rain drops on the screen while I was dialing the number in the rain or checking a text in the rain but I just wipe it off and put it back in my pocket, which might have been a little damp from the rain, so how sensitive are these things, humid air must be enough to trigger the little purple "x"s then, right?
Click to expand...
Click to collapse
ah, another phone is using those cables fine. . Ok, my bad. Does sound like something borked on the phone (USB, flash memory, etc).

The purple X's dissapeared and the paper turns red when it gets wet. You are good.
Sent from my SPH-D710 using xda app-developers app

oh, ok. for some reason I thought that they were white then the purple x's appeared when they got wet, didnt spend any time today messing with the phone at all today, although nothing I can really do anyways til the port comes in the mail.

[Q] Graphics Issues + Crash while charging

Hello all!
I have noticed that recently, my phone has been doing a very odd thing while charging. When it has been plugged in for a little while, and the screen is on and in use, sometimes the phone will crash. When it crashes in this manner, the backlight on the screen is turned on on full brightness, the screen gets a yellowish hue, and horizontal black bars start appearing on the screen. More black bars keep appearing until I reset the phone (hold the power button), and then there is no evidence of any screen problems. I also generally have to unplug it for a while, as if this happens once, it generally happens multiple times until I unplug the phone and wait. These problems seem to be occurring at odd times (a lot at night, before I am going to sleep), and have just started happening (I also recently made the upgrade from the latest version of GB to 4.0.4). I have had this device for about a year now (the second device, the first one had a physical design flaw and was replaced), and I am out of warranty right now, so any help would be appreciated!

a_p3rson said:
Hello all!
I have noticed that recently, my phone has been doing a very odd thing while charging. When it has been plugged in for a little while, and the screen is on and in use, sometimes the phone will crash. When it crashes in this manner, the backlight on the screen is turned on on full brightness, the screen gets a yellowish hue, and horizontal black bars start appearing on the screen. More black bars keep appearing until I reset the phone (hold the power button), and then there is no evidence of any screen problems. I also generally have to unplug it for a while, as if this happens once, it generally happens multiple times until I unplug the phone and wait. These problems seem to be occurring at odd times (a lot at night, before I am going to sleep), and have just started happening (I also recently made the upgrade from the latest version of GB to 4.0.4). I have had this device for about a year now (the second device, the first one had a physical design flaw and was replaced), and I am out of warranty right now, so any help would be appreciated!
Click to expand...
Click to collapse
That was happening to me (for a weird reason, my devicewas new, its seems that problem is more common in the rogers version dont know why) but, if your problem is the same problem that i had, then, just install stock ICS with oneclick (dont remember the name very well)

lorddavid said:
That was happening to me (for a weird reason, my devicewas new, its seems that problem is more common in the rogers version dont know why) but, if your problem is the same problem that i had, then, just install stock ICS with oneclick (dont remember the name very well)
Click to expand...
Click to collapse
Superoneclick? That's the closest I found, and it doesn't say that it supports the Glide. And, I am running a fully stock version of 4.0.4, unrooted and everything. I might need a little more help here, haha.

I mean, oneclick, is the firmware,and is about 700 mb, give me amoment a will search it
EDit: i found it: http://www.androidauthority.com/captivate-glide-sgh-i927-att-android-4-0-4-ics-uclg9-leak-110365/
I use that, when I install it, that problem gone away, try it. And then, you can flash the custom recovery and install custom roms

lorddavid said:
I mean, oneclick, is the firmware,and is about 700 mb, give me amoment a will search it
EDit: i found it: http://www.androidauthority.com/captivate-glide-sgh-i927-att-android-4-0-4-ics-uclg9-leak-110365/
I use that, when I install it, that problem gone away, try it. And then, you can flash the custom recovery and install custom roms
Click to expand...
Click to collapse
Isn't that a different version though? The build number on that is UCLG9, not UCKJ3 (which is what I have right now).

I am not sure, but, if with that your problem persist, maybe is hardware, but I only do that. When I did it, that was the latest version, now there is another version but not sure what is it

I was having the same problem, except it was happening frequently after my phone had warmed up due to normal use. If the phone was already hot it wouldn't even get past the splash screen.
I put it down to hardware fault, and was successful in getting it replaced under warranty. The new one has been totally fine.
Hopefully yours isn't a hardware issue - but from how it sounds it very well could be

davidpartay said:
I was having the same problem, except it was happening frequently after my phone had warmed up due to normal use. If the phone was already hot it wouldn't even get past the splash screen.
I put it down to hardware fault, and was successful in getting it replaced under warranty. The new one has been totally fine.
Hopefully yours isn't a hardware issue - but from how it sounds it very well could be
Click to expand...
Click to collapse
I really was hoping it was a OS issue, as it hadn't ever done this on GB. If I flash a new rom then, it would be fixed?
Also, I too noticed that my phone is abnormally warm when it does this. I do have a cover on my phone, but I noticed that it seems to be centered about on the horizontal center of the phone, about a half-inch below the camera. If this is related, what do you think it is?

My phone did this as well. Luckily it happened just before I rooted. The att guys said it was a hardware fault and that fault also killed my battery. I'm assuming it was a short. It started as something infrequent, but it eventually escalated to the point the second I turned it on my screen turned completely green and got really hot.

Exxon02 said:
My phone did this as well. Luckily it happened just before I rooted. The att guys said it was a hardware fault and that fault also killed my battery. I'm assuming it was a short. It started as something infrequent, but it eventually escalated to the point the second I turned it on my screen turned completely green and got really hot.
Click to expand...
Click to collapse
Just great, a possible hardware problem while out of warranty. Did yours do it only when charging as well?

a_p3rson said:
Just great, a possible hardware problem while out of warranty. Did yours do it only when charging as well?
Click to expand...
Click to collapse
Didn't have to be charging to do it. Could have been on the street holding it. (I was on GB as well)

Exxon02 said:
Didn't have to be charging to do it. Could have been on the street holding it. (I was on GB as well)
Click to expand...
Click to collapse
Your issue sounds similar, but slightly different. Mine only happens while I am charging it, and it has only done it since a while after I made the upgrade to 4.0.4. Although, they sound similar, and my phone also gets concerningly warm, so I have no idea if it is the same thing or not...

If it's out of warranty, then you have nothing to lose by doing a backup and a clean ROM installation, which is what I would do. I guess if you do it when fully charged and while the phone is cold you should be fairly safe, especially if you use a small ROM. I've found the latest M3 10.1 ROM installs fairly quickly, so that might be worth a shot even just to see if it fixes the problem.
The only risk you're taking is that the phone might die and get bricked in the process if it's a hardware fault, so I guess it's really your call.
EDIT: On that thought, perhaps experiment with seeing if you can charge after leaving it in the fridge for about 15 minutes? It's a trick we used to use to recover data from failing hard drives, if you get them cold enough they can work for long enough to get away with things

davidpartay said:
On that thought, perhaps experiment with seeing if you can charge after leaving it in the fridge for about 15 minutes? It's a trick we used to use to recover data from failing hard drives, if you get them cold enough they can work for long enough to get away with things
Click to expand...
Click to collapse
I like that idea, as it should fix the overheating issue. However, the times that it actually has this malady aren't regular - it seems to happen more at night, but not every night. I could try putting it in the freezer when it does it though, and see if it works. If it is overheating, could it be a hardware issue then? I also noticed that my battery that I have in my phone does appear to have a slight dent near the bottom, and it is only happening when it is charging, so I am wondering if it could be a problem with the battery? When I pull the battery out after it has done this, the battery itself isn't that warm, but the phone is, so I'm thinking it isn't the battery, but does anyone else have any ideas?

[Q] Power Issue on Note 3

I was looking and looking for a thread with a similar issue before posting but I had no luck.
My issue is that when I turn off my Note 3 I have a really hard time getting it to boot back up. This happens every time every single time I shut it off. I hold the power button for about a minute with the battery removed to supposedly drain any power as I've read around but that doesn't help. I'm pretty tech savvy and internally the phone looks perfectly fine. The weird thing is that I don't actually have any issues once the phone is up and running to make me think it's a hardware issue. It charges fine, I get data, S pen is fine, no other issues what so ever. I haven't been able to pin point what I'm doing to bring it back but eventually it does end up booting like normal. I try to pull the battery multiple times with no success. I eventually get frustrated and just leave it alone with the battery removed. When I return it boots up just fine.
Anybody else having this issue or heard of it?
Forgot to mention that the phone is stock. I don't have it rooted or a custom rom installed.

Thats weird. Have you tried reseating the SD card. Sometimes it might bethe memory card.

Why turn it off?
Just let it sleep. I can't remember when I ever turned my phone off.
Pp.

steve_togo said:
Thats weird. Have you tried reseating the SD card. Sometimes it might bethe memory card.
Click to expand...
Click to collapse
I have indeed. I was thinking it was that but it occurs either way.

PanchoPlanet said:
Why turn it off?
Just let it sleep. I can't remember when I ever turned my phone off.
Pp.
Click to expand...
Click to collapse
Well my phone's back camera was broken and I was replacing it. Although the issue started occurring well before replacing the camera.

Im having same issue. Replaces camera now phone wont turn on. shows chargering though.

yotaking said:
Im having same issue. Replaces camera now phone wont turn on. shows chargering though.
Click to expand...
Click to collapse
I noticed you also have a thread which states the same thing and I'm not sure if you figured it out yet, but just out of curiosity did you happen to ground yourself while you were working on your Note 3? This goes for any device in general but it's pretty amazing how much damage the static electricity from just your clothes can cause if you're not grounded while working with an exposed main board. If you weren't grounded while working on it though it also doesn't mean that something automatically happened, I'm just saying it's always a possibility at least. One thing I would try if you're having problems powering it up even just in general, is to make sure it's plugged in and charging first and then hold the volume up and power buttons down together at the same time (and keep them held down) until you feel a vibration and then let go. It will take at least 10 - 15 full seconds (and sometimes even longer) to happen, but that should usually get it to power it up whenever it's being stubborn. Another thing I'd definitely check, especially if it was working fine before disassembling the phone, is the alignment of the power button itself (the button you press with your finger) and the actual power button which is located behind it on a data ribbon that connects to the main board. It's actually kind of a flimsy setup so whenever you reinstall the back frame plate you have to make sure the power button data ribbon doesn't shift, or it can cause all kinds of weird problems when trying to power on or off the phone. Anyway good luck and hopefully this helps [emoji106] [emoji106]
Sent from a modified ColecoVision
---------- Post added at 04:07 AM ---------- Previous post was at 03:47 AM ----------
MexicanGeekian said:
I was looking and looking for a thread with a similar issue before posting but I had no luck.
My issue is that when I turn off my Note 3 I have a really hard time getting it to boot back up. This happens every time every single time I shut it off. I hold the power button for about a minute with the battery removed to supposedly drain any power as I've read around but that doesn't help. I'm pretty tech savvy and internally the phone looks perfectly fine. The weird thing is that I don't actually have any issues once the phone is up and running to make me think it's a hardware issue. It charges fine, I get data, S pen is fine, no other issues what so ever. I haven't been able to pin point what I'm doing to bring it back but eventually it does end up booting like normal. I try to pull the battery multiple times with no success. I eventually get frustrated and just leave it alone with the battery removed. When I return it boots up just fine.
Anybody else having this issue or heard of it?
Forgot to mention that the phone is stock. I don't have it rooted or a custom rom installed.
Click to expand...
Click to collapse
I just mentioned this in my response to someone else in this thread, but it actually sounds like yours has the same kind of alignment issue with power button that I was talking about. I'm not sure if you've ever disassembled yours for any reason or not, but even if you haven't it's still totally possible that it could've happened from the factory and especially if you got a refurbished phone for whatever reason. It's a pretty poor design choice in my opinion because it's such a "fragile" setup, and even the slightest misalignment of the power button itself and the button on the data ribbon can cause the exact same problems your having. Anyway if if you haven't messed with it and it's still under warranty I'd say just get a new one, but if you have taken it apart I'd say first thing to check would be the alignment of those buttons (once you take the back off). I've even had to make a tiny little "shim" and wedge it behind the power button on the data ribbon in order to get it to line up right with the button itself a couple of times, so I'd say it's a fairly common problem with these phones. Anyway good luck and hope it helps! [emoji106] [emoji106]
Sent from a modified ColecoVision

Charging port barely charging

Hello all...
Ive had my m8 since the end of april. It's worked and charged fine up until last Thursday. I started to notice that when I have it plugged in, the led will come on and it'll say it's charging, but it doesn't actually charge, most of the time it continued to decrease. After playing with different cables and the gsam app I found that it won't actually charge unless I put pressure or weight on top of the end of the cable that is plugged in to my phone. Even then, I have to mess with it quite a bit and hope when I wake up, it'll be charged.
This has become increasingly frustrating every time I plug it in to charge now. Has anyone else experienced this problem with your device? Also does anyone know of a fix, besides paying the $149 to get it replaced with my ATT insurance plan? I really just want to wait until around April and get a new phone, preferably with a snapdragon 810 processor, however, at this point, I don't think I can make it until then.

mattprice86 said:
Hello all...
Ive had my m8 since the end of april. It's worked and charged fine up until last Thursday. I started to notice that when I have it plugged in, the led will come on and it'll say it's charging, but it doesn't actually charge, most of the time it continued to decrease. After playing with different cables and the gsam app I found that it won't actually charge unless I put pressure or weight on top of the end of the cable that is plugged in to my phone. Even then, I have to mess with it quite a bit and hope when I wake up, it'll be charged.
This has become increasingly frustrating every time I plug it in to charge now. Has anyone else experienced this problem with your device? Also does anyone know of a fix, besides paying the $149 to get it replaced with my ATT insurance plan? I really just want to wait until around April and get a new phone, preferably with a snapdragon 810 processor, however, at this point, I don't think I can make it until then.
Click to expand...
Click to collapse
If you are. Comfy tearing the phone apart the charging port is on its own board/cable.
Are you sure nothing is buried in the port preventing you from pushing the cable the entire way in?

dottat said:
If you are. Comfy tearing the phone apart the charging port is on its own board/cable.
Are you sure nothing is buried in the port preventing you from pushing the cable the entire way in?
Click to expand...
Click to collapse
Nothing is blocking the inside, I checked. It will plug in all the way fine, but I have to put pressure down on top of the cable where it connects to the port to make it work.
Ive taken mobile devices apart before, but from what I've seen on ifixit, it looks like a pretty daunting process for the m8 and I'm not so sure I'll be able to do it without damaging anything else.
I was just seeing if anyone else may if had this same issue and they knew of a way to get it going. I'll probably just have to take it in and get it replaced

mattprice86 said:
Nothing is blocking the inside, I checked. It will plug in all the way fine, but I have to put pressure down on top of the cable where it connects to the port to make it work.
Ive taken mobile devices apart before, but from what I've seen on ifixit, it looks like a pretty daunting process for the m8 and I'm not so sure I'll be able to do it without damaging anything else.
I was just seeing if anyone else may if had this same issue and they knew of a way to get it going. I'll probably just have to take it in and get it replaced
Click to expand...
Click to collapse
To be honest if the phone is otherwise in good shape they will probably warranty it if it doesn't look like abuse. Just make sure you are stock, locked, and s-on.

mattprice86 said:
Nothing is blocking the inside, I checked. It will plug in all the way fine, but I have to put pressure down on top of the cable where it connects to the port to make it work.
Ive taken mobile devices apart before, but from what I've seen on ifixit, it looks like a pretty daunting process for the m8 and I'm not so sure I'll be able to do it without damaging anything else.
I was just seeing if anyone else may if had this same issue and they knew of a way to get it going. I'll probably just have to take it in and get it replaced
Click to expand...
Click to collapse
If the usb port is not moving around out of the ordinary, then dirt is usually the culprit, and sometimes it gets hardened around the metal contacts with each attach / detach of the usb cable. Try using a tiny pin to carefully clean away the dirt from the metals.
I found it to be pretty useful in the past when i had likewise problems.

mattprice86 said:
Hello all...
Ive had my m8 since the end of april. It's worked and charged fine up until last Thursday. I started to notice that when I have it plugged in, the led will come on and it'll say it's charging, but it doesn't actually charge, most of the time it continued to decrease. After playing with different cables and the gsam app I found that it won't actually charge unless I put pressure or weight on top of the end of the cable that is plugged in to my phone. Even then, I have to mess with it quite a bit and hope when I wake up, it'll be charged.
This has become increasingly frustrating every time I plug it in to charge now. Has anyone else experienced this problem with your device? Also does anyone know of a fix, besides paying the $149 to get it replaced with my ATT insurance plan? I really just want to wait until around April and get a new phone, preferably with a snapdragon 810 processor, however, at this point, I don't think I can make it until then.
Click to expand...
Click to collapse
So in your country you don't have warranty? Even if there is a 12 months since April... Let me think?...
Sent from my HTC One_M8 using XDA Free mobile app

dottat said:
To be honest if the phone is otherwise in good shape they will probably warranty it if it doesn't look like abuse. Just make sure you are stock, locked, and s-on.
Click to expand...
Click to collapse
Agree, that unless the phone has obvious signs of physical damage or water damage, AT&T will replace it (with a refurb) under warranty, and it won't cost the OP anything. AT&T also typically won't check for software mods. Although, its a good idea to return to mostly stock, just in case.

redpoint73 said:
Agree, that unless the phone has obvious signs of physical damage or water damage, AT&T will replace it (with a refurb) under warranty, and it won't cost the OP anything. AT&T also typically won't check for software mods. Although, its a good idea to return to mostly stock, just in case.
Click to expand...
Click to collapse
Yea I was able to get a free replacement. They listed it as a defect. It comes in next Thursday, thank god. I just ran the 4.4.3 ruu. I'm going to try and relock my boot loader, but I don't know if I'll be able to BC I can't get it to recognize when I plug into the computer anymore.
Thanks for all the help

mattprice86 said:
Yea I was able to get a free replacement. They listed it as a defect. It comes in next Thursday, thank god. I just ran the 4.4.3 ruu. I'm going to try and relock my boot loader, but I don't know if I'll be able to BC I can't get it to recognize when I plug into the computer anymore.
Click to expand...
Click to collapse
Try to go to Windows Device Manager (with phone connected) find the device, and pick the option to manually select drivers, the select the MTP USB driver (not HTC drivers). For some reason, I lose fastboot/adb connectivity, and have to do this very frequently (even when no changes on the phone).
But this is only if you really want to relock the bootloader. Which is not stock whether its UNLOCKED or RELOCKED. Unless you want to do the mod to change the flag to LOCKED.
In any case, good to hear they will replace the phone (and rightfully so, as it seems to be a hardware failure not caused by physical damage). So good luck.

redpoint73 said:
Try to go to Windows Device Manager (with phone connected) find the device, and pick the option to manually select drivers, the select the MTP USB driver (not HTC drivers). For some reason, I lose fastboot/adb connectivity, and have to do this very frequently (even when no changes on the phone).
But this is only if you really want to relock the bootloader. Which is not stock whether its UNLOCKED or RELOCKED. Unless you want to do the mod to change the flag to LOCKED.
In any case, good to hear they will replace the phone (and rightfully so, as it seems to be a hardware failure not caused by physical damage). So good luck.
Click to expand...
Click to collapse
Thanks. The problem isn't detecting the drivers, BC I've connected it and used adb tons of times, but now, since it takes a lot of time messing around to charge, I have to do the same when I connect it to the comp.
I think I'll probably just leave the bootloader unlocked and s-off. I read some other threads about having issues turning s back on. I have it on 4.4.3 unrooted. Thanks for everyone's help

mattprice86 said:
Thanks. The problem isn't detecting the drivers, BC I've connected it and used adb tons of times, but now, since it takes a lot of time messing around to charge, I have to do the same when I connect it to the comp.
Click to expand...
Click to collapse
Gotcha. I completely spaced on the (obvious) fact that your connectivity issues could be related to the original issue of the damaged MicroUSB port!
Driver issues are so common, its like a knee jerk reaction for me now!

Not sure if it would help but you can get ADB WiFi on play store
Sent from my Nexus 7 using Tapatalk

Thanks. I had heard about adb WiFi but I want exactly sure what that was. I always just connected my phone to the computer before this happened.
I think I'm just going to leave the boot loader unlocked and s off. Seems like it shouldn't be a problem going back to ATT, as red point mentioned

It seems like the charging port is the cause

Update: I received my replacement phone last Thursday and mailed back my old one today. I did leave the boot loader unlocked and kept it s off, so we'll see if ATT tries to charge me for it. I'll let everyone know after they receive it.
My replacement was still running 4.4.2, so instead of going thru htcdev again to unlock the bootloader, I immediately downloaded, paid, and ran sunshine. It worked like a charm, unlocking my boot loader and turning s off. From there, I changed my cid to supercid, ran the ATT 4.4.3 ruu, then the Dev edition 4.4.4 ruu, then finally the Dev edition 5.0 ruu.
It's so great not having to mess with my phone for 20 min just to get it to charge. I also ordered a charger with Qualcomm quick charge 2.0 and it charges my phone amazingly fast.

LG G4(Verizon) stuck in a bootloop, can I recover my data?

Unfortunately my LG G4 is one of the models that got stuck in a bootloop, if you haven't heard, LG has announced this issue and is definately aware of it. My G4 has been rooted for a while, so I am pretty sure that the root isn't the cause of the bootloop. Is there anyway to maybe boot into a recovery mode, or get the phone turned on long enough to recover my pictures, and maybe contacts? The bootloop gets to "optimizing apps" then restarts again.
Thanks.

may be a little late but i've heard some people having success at putting it in the freezer for an hour and then trying to turn it on. will last for up to an hour from what I heard allowing you to get some data from it. there is also a more dangerous method of taking the motherboard out and baking it at a certain temp in the oven for a certain amount of time. you'll have to google it since i don't remember. I'd personally never try to put plastic in an oven though lol.

I had the same issue. Before doing the freezer method try these as i did this my self.
1. Use a fan in a cool room, put the fan on highest setting and make sure you get a good breeze. Make sure the wind is hitting the phone.
2. If you have a ac unit. I dont care what your friends say if its cold out side. Crank that b!tch up. And hold your phone over the air vent.
3. If it is really really cold out side *please note depending on temp your hands will freeze over* stand out side and back your things up to sd card
4. Hold an ice pack over the camera and buttons keep it there till you back your things up
Thats all i can think of and what i discovered. Every time i was in a warm room. Thing keeps cutting off. Please note. Some things required a sd card and when movine files. Please copy files instead of cut. Once finished you can delete your files off the phone
I hope this helps
Edit- before doing anything dont forget to turn the brightness down. This will help keeping the phone to get warm fast