Hey all, I got my phone into a serious problem this time... And myself too
I don't know what happened but I just plugged my phone in, started charging... , no I didn't leave it all day, when it was charged but I found out that it didn't charge further than 75%
I waited 10 minutes, still nothing.
I unplugged, showed that it was charging, I thought it may be lag and rebooted the phone.
Nothing, still same, I plugged my OTG cable in and weirdly it fixed itself but after pulling it out it got back to "charging"...
After a few tries it did the same on the OTG cable, I tried cleaning the USB input thingy on the phone but nothing...
Now I'm forced to stay at the wall plug because the phone lasts seconds thinking it's charging since we know that it runs full-speed.
I tried getting into recovery but... Well, I powered off the phone, managed to get to fast boot and it showed "hboot searching sad card for updates" or something like that! it takes long so I powered it off again and it started itself up without touching, I assume that's because it thinks it's charging.
Can I do something to get that phone back to life or is it time for a new one?
Anyone getting this problem too? Or did anyone have it and fixed it? Please tell me how
Sad to hear this. Have you tried any other chargers?
/\/\ said:
Sad to hear this. Have you tried any other chargers?
Click to expand...
Click to collapse
I tried 3 different chargers each with 3 different cables, an apple charger, some belkin charger and another charger with 700mA
my dad fixed it somehow until it went empty and had to replug the charger, it fixes itself below 10 and above 20 prcent it goes back weird
Well, things going totally insane now, I wanted to format the internal SD and flash a rom with sideload.
Went recovery, wiped everything, started sideload... Computer gave an error, I think it was something with timeout or something idk anymore...
Tried it 20+ times! all same
So I went to install stock recovery, installed it too, everything passed, then locked boot loader with fastboot oem lock, succeeded too, but it showed security warning, but I just went on and installed the European RUU, which failed due to code 158 image error...
Redownloaded that RUU, same thing...
Downloaded others, ran each for 1.5+ hour! but it seemed to take hours instead 20 minutes so i lost hope, I still am able to unlock boot loader,install recovery and stuff but unable to get a rom on it, can anyone at least tell me how to maybe flash ROM through USB OTG? I know that works, right before my phone died I used a PC mouse on it...
I need to fix this phone and sell it quickly, support is dropped also so that's the best idea, I cannot afford to give this phone for maybe 10 euro so I really have to get this fixed.
I got patience until mid-October because the OPO comin out probably, anyway I'm waiting for ANY suggestions to get a rom on it, may be stock, custom idc, I just need it working because I found out that the USB charging problem is hardware, not software, my phone still won't turn off
Thanks in advance -ozi
So guys, today I got a bit upset and disappointed because of the loss I almost made, yeah, almost.
Because I sorted out how to get the phone back to life when this issue happens.
Well, it all started with a full memory, yeah I had 5/64GB free space left.
And my phone got the bug/hardware fail then too, I still don't know what it is, but that isn't fixed yet.
I thought like "what can go wrong if I just try to put my phone to all ZERO".
So without even stopping for a second and thinking what can make a problem, I formatted the whole phone.
I knew I was going to use ADB Sideload but not that it was going to take 3 days.
So I went to Sideload (PhilZ recovery) and while side loading the stuff, it got stuck, approximately 30 percent where it stopped working.
The error was something with protocol if I remember correctly since I'm not having this issue anymore.
This happened maybe 20 times, yes, I was freaking out at the command prompt trying to figure out why it didn't work.
Anyway then after hours of searching my brain reminded me of the ADB Push command I once read somewhere... And immediately researched for it, how to use it and such...
Then I rebooted recovery, did ADB push rom.zip /sdcard ... FAILED
Why did it fail, well, I didn't know...
Got very disappointed this time and went to what I was doing: searching on Google, xda...
Took over a day, to be honest, really, I must say I posted this WAY too early, because I could've searched first.
You know, school, laziness, sleepiness and such.
But back to the point. I've finally found some old files sitting there, taking their space in my HDD, they were These files.
(Download them if you want to fix your phone too.)
I opened it, TOTALLY forgot about it, not even remembering it was there...
I saw flash TWRP recovery and flashed it, since I had no adb connection, the first one failed but then fastboot opened, and my device was at fastboot at that moment, knowing that you need fastboot to flash a recovery.
SUCCEEDED, even if I knew that it was going to succeed, I was happy because it was one of the first things which succeeded .
So I opened recovery, and went to advanced - ADB Sideload
I tried everything again, and this time uninstalled htc sync manager (not the drivers).
It took long, just about 30minutes to transfer a 980MB file, MagioROM...
But at least it WORKED, now I got a working ROM.
Now about the USB issue, I'm going to look further into that, I'll change the title to "ROM and USB Charging issue".
Tho I really think it's just the hardware. And I'll update this when I get some further.
And to the fast-panicing people amongst us (including me), do research and don't give up. This way you will less likely have an expensive brick
So today I went on and opened up my phone, I got nothing better to do anyway, it was still thinking that it's charging, but I made sure it weren't the pogo pins by cleaning them and checking the cables...
It was an USB connector problem, when I touched it a bit with a screwdriver, it went back normal and when I plugged it in it got messed up again.
So the people who got this problem: go warranty before it's too late or do it yourself by buying parts and replacing them, I must say, one x+ was one of the worst jobs to open up a phone tho lol
Related
Hi All,
Today when I unpluged my phone from charger I have noticed that I got USB symbol in notification bar, after checking what it is it turned out to be MTP connection but phone was not connected to anything. Next I took the battery out to reboot it and then I got empty battery sign with thermometer warning next to it!?! After few minutes phone booted in safe mode so I took the battery out again but this time for about 10 minutes. It is working fine since but Im worried that there might be something wrong with it. What do you think guys? Have someone had something like that?
Hey,
I had exactly the same thing happen today, tried everything I could think of, factory resets, formatting, cache wiping, tried reflashing multiple times with root and without root, XXKG2, XXKG1, KE7 and back to branded stock firmware. I also used a counter reset jig just in case that had any effect. Anyway, I ended up calling my provider and they suggested it was a hardware fault rather than software or settings and they are sending me a new one tomorrow.
I could only find one thread about a similar issue relating to the Galaxy S though I can't "refind" it, but basically there were a number of posters there with very similar issues and some of them had success cleaning the connectors in the port of the phone. I didn't really fancy trying this and breaking the connector or voiding my warranty and so I went with the easy option.
Hope that helps and hope you get it sorted easily!
Mark
Hi .. I have experienced more or less the same issue: mine was unplaged from charger and switched in "Driving Mode" showing a steering wheel in notification area. That happened many times so I just rebooted the phone and I got the empty battery sign with thermometer warning next to it me too!
Now usb connection is not working anymore I'm still able to charge the phone even flash is working using Odin, but no data connection is detected by any pc with any usb cable!
I've flashed the stock rom and tryed many cooked rom, but usb data is dead!
I think I have to return it on a service center!
Hope that is not your case!
Bye
Looks like it's not a one off then...one thing I would add, just in case anyone hasn't noticed, is that you can still use the phone as by plugging it in to charge then it does boot up properly. In addition, you can also still get into recovery and download via the Home+Volume key+power button methods so you can revert to stock rom etc. It's a bit fiddly to do this though as the phone seems to think its on charge and so you have to time the holding/pressing just right to beat the green battery and temperature warning sign...but at least we can do backups of all our data/apps.
I really do think it might be fixable with a bit of a pointy cleaning tool and maybe some isopropanol...but as I said I didn't want the risk of breaking something further. Worth a try if your carrier isn't very good at replacing things though!
I have a Motorola Atrix 4G on Bell Mobility. Currently the phone will not boot at all. The phone is out of warranty.
When this started I began by searching through the xda forums and found several similar problems. Most pointed to the sleep-of-death or a charging adapter problem. I have tried charging with the Motorola adapter that came with the phone, a USB cable and the Motorola Lapdock. None of these have provided any happy. Each time I tried, I left the phone overnight, when I checked on it, the phone and battery were cold. I tested a known-working battery from another Atrix and the phone would still not boot.
Some other searches point to a factory cable. I bought one on Ebay however the phone will not boot. I tested the cable on a known-working Atrix and it works fine. I did notice that when I plug the factory cable in to my phone and in to my Windows 7 PC, it detects *something*. Under device manager I see an unknown device called "APX". So far Google and xda searches haven't been able to provide me with a correct answer.
When I plug in the regular USB cable the green LED turns on for a while, if I touch the power button, the green LED goes out. RSD Lite does not detect anything, I assume this is because the phone is not in RSD mode.
I have tried combinations of volume buttons/power button as well, both with the wall charger and with the factory cable. Nothing displays on the screen at all no matter what I've tried. The phone had the stock install from Bell however was rooted with SuperOneClick (obtained from xda forums and installed many months ago) and had no third-party apps on it.
This death seemed to start slowly, at first battery life was at times terrible, then it moved on to not wanting to power on for a while if the battery died or the phone was turned off when the battery was low. Removing/re-inserting the battery several times typically helped. Eventually the phone got so bad, when it booted it would just crash repeatedly with a message about motorola.home.something (sorry I don't remember exactly what). Hitting force close would just bring the message back up again. I left the phone off overnight and the next morning, R.I.P. my Atrix
I have access to Windows XP or 7 as well as Linux.
Any help would be appreciated. Also I apologize for the long-winded post, I'm trying to provide as much information as I can.
I had this problem to, I freaked out, what I needed to do was to get another Atrix (in this case my Uncles) and make sure that the battery in it is FULLY CHARGED, then I took out my battery (in the broken phone) and put in his, then I got a solid green LED, then I had to leave it on the charger overnight, after that the M would show, but that was it, so I then went into fastboot and flashed the ICS Leak, and ta-da.
Xerox98 said:
I had this problem to, I freaked out, what I needed to do was to get another Atrix (in this case my Uncles) and make sure that the battery in it is FULLY CHARGED, then I took out my battery (in the broken phone) and put in his, then I got a solid green LED, then I had to leave it on the charger overnight, after that the M would show, but that was it, so I then went into fastboot and flashed the ICS Leak, and ta-da.
Click to expand...
Click to collapse
I had tried that before, but I can't remember if I had charged the battery full. I'll give it a shot today, thanks!
jonbruce said:
I had tried that before, but I can't remember if I had charged the battery full. I'll give it a shot today, thanks!
Click to expand...
Click to collapse
I've tried that with no luck. I should also note that the factory cable bypasses the battery, potentially eliminating any battery problems.
It's possible that your phone is finished. The 'motorola.home' error is usually caused by something you've updated (google search?) but I would doubt that it would cause your phone to not even start up.
At this point, I might be inclined to open the phone up (http://www.ifixit.com/Teardown/Motorola+Atrix+4G+Teardown/4964/1) and see if you can see anything obvious?
barry_ said:
It's possible that your phone is finished. The 'motorola.home' error is usually caused by something you've updated (google search?) but I would doubt that it would cause your phone to not even start up.
At this point, I might be inclined to open the phone up <url removed so I could reply> and see if you can see anything obvious?
Click to expand...
Click to collapse
I will check that out tonight and report back, thanks!
jonbruce said:
I will check that out tonight and report back, thanks!
Click to expand...
Click to collapse
Nothing obvious when I took it apart, no visible damage or problems. Any other thoughts? I've been told to try ADB from a Linux box and see if it will do anything. I've started installing ADB but looking for more insight.
jonbruce said:
Nothing obvious when I took it apart, no visible damage or problems. Any other thoughts? I've been told to try ADB from a Linux box and see if it will do anything. I've started installing ADB but looking for more insight.
Click to expand...
Click to collapse
Update. I found this ... http://forum.xda-developers.com/showpost.php?p=11901016&postcount=75 and now instead of "APX" in Windows device manager, I have "NVIDIA USB Boot-recovery driver for Mobile devices".
It looks like NVFlash might be something I need next. In other news, the phone when plugged in via the factory cable, is actually very slightly warm. It's the first new sign of life I've seen in this thing for a few days.
jonbruce said:
Update. I found this ... http://forum.xda-developers.com/showpost.php?p=11901016&postcount=75 and now instead of "APX" in Windows device manager, I have "NVIDIA USB Boot-recovery driver for Mobile devices".
It looks like NVFlash might be something I need next. In other news, the phone when plugged in via the factory cable, is actually very slightly warm. It's the first new sign of life I've seen in this thing for a few days.
Click to expand...
Click to collapse
I've had no luck at all since my last reply. http://forum.xda-developers.com/showthread.php?t=1046994 seems to have something to do with my problem, but I'm not able to dig up a solid answer. As best as I can tell, I manged to hard brick the thing and I'm up the creek without a required paddle.
Any other thoughts on this would be great. Even if I'm able to ensure the device is wiped, I could send it in. There are work files on there (I know, I know, I'm an idiot) I can't have out in the wild.
Just bought a replacement Atrix for $100. It included three cases, three batteries, wall charger with cable, car dock and a metric ass-load of screen protectors.
I do want to thank everyone for offering help and ideas, it was a good learning experience!
jonbruce said:
Just bought a replacement Atrix for $100. It included three cases, three batteries, wall charger with cable, car dock and a metric ass-load of screen protectors.
I do want to thank everyone for offering help and ideas, it was a good learning experience!
Click to expand...
Click to collapse
I've just encountered this issue and cannot find a solution anywhere online. I've come to terms with my phones fate by now. Just wanted to ask where I could find this Atrix replacement for 100 w/ all the neat stuff you've listed above? Please advise
thanks
Cheekan
cheekan said:
I've just encountered this issue and cannot find a solution anywhere online. I've come to terms with my phones fate by now. Just wanted to ask where I could find this Atrix replacement for 100 w/ all the neat stuff you've listed above? Please advise
thanks
Cheekan
Click to expand...
Click to collapse
I found mine on Kijiji, luckily right in my city.
Hello, so much time searching for this on the web, spanish is my birth language... so i wanted to know some update from this of any of you if posible, thanks in advance.
i couldn't describe better the problem and situatiob, is exactly the same, same phone of course.
I was about to try to make a factory cable, so i ended here, i think is not going to help me then is that right?
PD: i don't know what more to do with the atrix, sell for parts, even that is difficult over here, and the services don't help either, i've tryied 2 of them already, only ignorance they have
Hello everyone, first of all sorry if this has been posted a million times, but i just cant seem to find any answers, if been looking for hours without results. Heres my situation
Got a used HTC DROID DNA in mid december, it was completely stock, s-on and not rooted or anything.
i managed to root it and install a custom ROM, the device was running TWRP.
now, a few weeks ago i was trying to install a new ROM, at first it failed, it would just reboot me to my old ROM, after doing some searching i managed to install it (cant remember what was wrong right now), that same day i went on a small road trip, a few hours later, i knew my battery was extremely low, i pulled my phone out of my pocket, turned the screen on and just saw a a glimpse of the battery saying 3 or 4% and then it just shut down, it showed the white HTC screen and it died, i thought nothing of it, thing is, that was the last time it ever lived, after that, i got home and tried to charge it, nothing works, no led light, it doesnt vibrate i cant enter recovery or do anything, the phone is dead, ive tried leaving it stuck to the charger for hours and nothing.
doing some research it told me to do a few button combinations but non of them worked, i also removed the battery and installed it again, didnt work.
now the thing that gives me hopes that the phone can be relived is that when connected to any pc, the computer recognizes it and installs the driver, it doesnt say its a htc phone, but it says the device is ready to use, i cant even see it in my devices though..... another thing that happens is that when i connect it, windows plays the USB plugged in sound, and exactly (ive timed it numerous times) 5 seconds later, plays the sound that is played when a USB device is disconnected, then about 1 second later it recognizes it again, and this just keeps looping, i have no idea what to do, tried finding it in ADB and nothing.
anybody have any ideas? or tips i can do?
AnonCantRead said:
Hello everyone, first of all sorry if this has been posted a million times, but i just cant seem to find any answers, if been looking for hours without results. Heres my situation
Got a used HTC DROID DNA in mid december, it was completely stock, s-on and not rooted or anything.
i managed to root it and install a custom ROM, the device was running TWRP.
now, a few weeks ago i was trying to install a new ROM, at first it failed, it would just reboot me to my old ROM, after doing some searching i managed to install it (cant remember what was wrong right now), that same day i went on a small road trip, a few hours later, i knew my battery was extremely low, i pulled my phone out of my pocket, turned the screen on and just saw a a glimpse of the battery saying 3 or 4% and then it just shut down, it showed the white HTC screen and it died, i thought nothing of it, thing is, that was the last time it ever lived, after that, i got home and tried to charge it, nothing works, no led light, it doesnt vibrate i cant enter recovery or do anything, the phone is dead, ive tried leaving it stuck to the charger for hours and nothing.
doing some research it told me to do a few button combinations but non of them worked, i also removed the battery and installed it again, didnt work.
now the thing that gives me hopes that the phone can be relived is that when connected to any pc, the computer recognizes it and installs the driver, it doesnt say its a htc phone, but it says the device is ready to use, i cant even see it in my devices though..... another thing that happens is that when i connect it, windows plays the USB plugged in sound, and exactly (ive timed it numerous times) 5 seconds later, plays the sound that is played when a USB device is disconnected, then about 1 second later it recognizes it again, and this just keeps looping, i have no idea what to do, tried finding it in ADB and nothing.
anybody have any ideas? or tips i can do?
Click to expand...
Click to collapse
Let it sit on the charger for 24+ hours then try turning it on, people have reported this to work in situations like yours.
AnonCantRead said:
doing some research it told me to do a few button combinations but non of them worked, i also removed the battery and installed it again, didnt work.
Click to expand...
Click to collapse
Did you really remove and replace the battery? It's integrated into the phone; isn't that a bit of work in advance of charging it over night and maybe trying other things?
I never would have done that on this phone. I probably would have just CL'd another used one before attempting to R/R the battery. Can you post some instructions?
Yehudah said:
Did you really remove and replace the battery? It's integrated into the phone; isn't that a bit of work in advance of charging it over night and maybe trying other things?
I never would have done that on this phone. I probably would have just CL'd another used one before attempting to R/R the battery. Can you post some instructions?
Click to expand...
Click to collapse
He didn't remove it from the phone he just disconnected it and reconnected it. I'm pretty sure the battery has strong adhesive that is attached to the housing. The battery can bend when pulling on it that's how strong the adhesive is.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
---------- Post added at 04:52 AM ---------- Previous post was at 04:51 AM ----------
Btw if you can't get into the bootloader it's most likely hosed and will need to be jtaged.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
I'm new to this site so if this thread is in the wrong place, please redirect me to the appropriate section.
A couple days ago, my GSR had shut off for no reason that I could find, and would not turn on (even to try to boot in recovery mode) for 2 hours(it would go into the boot screen but would then shut off after 5-7 seconds of "booting up"), when suddenly it started working again. I couldn't figure out why it stopped working or why it suddenly starting working again. I even changed batteries but that didn't influence anything. Then, exactly (I mean exactly) 24 hours later at the same time, it shut off again. This time, it won't even show the boot logo, and instead says, for less than a second "Movinand checksum confirmation fail." It is rooted, but has been rooted for almost a year with no real modifications done to the device and no previous issues that I noticed. I have tried changing batteries, trying different chargers, replacing the SIM and SD, and tried booting into recovery but has no effect because it shuts off before I can even do anything to it. I've seen a lot of places say wipe cache partition by going into recovery mode, but that's just not possible with what is going on. I try every other hour to see if it has somehow started working again, but now won't even show the "movinand checksum..." message. It is charged because it has been plugged in most of the time that this has been going on. It's not water damaged, I have never dropped it, and it hasn't been exposed to any intense heat or coldness ever in its life. I'm at a loss here, not sure what to do, as it seems I've tried nearly everything. I'm welcoming any suggestions you may have, as well as answering any questions about the situation.
In Need of Dire Help! Galaxy S Relay 4G(SGH-T699) Completely Bricked?
XmashMAN said:
I'm new to this site so if this thread is in the wrong place, please redirect me to the appropriate section.
A couple days ago, my GSR had shut off for no reason that I could find, and would not turn on (even to try to boot in recovery mode) for 2 hours(it would go into the boot screen but would then shut off after 5-7 seconds of "booting up"), when suddenly it started working again. I couldn't figure out why it stopped working or why it suddenly starting working again. I even changed batteries but that didn't influence anything. Then, exactly (I mean exactly) 24 hours later at the same time, it shut off again. This time, it won't even show the boot logo, and instead says, for less than a second "Movinand checksum confirmation fail." It is rooted, but has been rooted for almost a year with no real modifications done to the device and no previous issues that I noticed. I have tried changing batteries, trying different chargers, replacing the SIM and SD, and tried booting into recovery but has no effect because it shuts off before I can even do anything to it. I've seen a lot of places say wipe cache partition by going into recovery mode, but that's just not possible with what is going on. I try every other hour to see if it has somehow started working again, but now won't even show the "movinand checksum..." message. It is charged because it has been plugged in most of the time that this has been going on. It's not water damaged, I have never dropped it, and it hasn't been exposed to any intense heat or coldness ever in its life. I'm at a loss here, not sure what to do, as it seems I've tried nearly everything. I'm welcoming any suggestions you may have, as well as answering any questions about the situation.
Click to expand...
Click to collapse
Edit, 11/12/2014: As of today, I managed to get myself into ODIN mode, but will only stay in ODIN mode for about
5 seconds before it shuts off. I can repeatedly do this as much as I want, but does not change anything to how long before it shuts off. I've tried rebooting through adb reboot-bootloader, but since my pc cannot find my device, I get this error "error: device not found". I made sure the drivers are installed, as they needed to be for me to even root my phone, but still no other results.
Also, when I take the battery out and put it back in, it vibrates as if it will boot up, but then red text saying "Movinand checksum..." comes up for a split second, then vibrates again with the same text. Then I can't do anything else until I remove the battery. I'm thinking about getting a JIG that will force it into download mode or recovery mode if one even exists.
XmashMAN said:
Edit, 11/12/2014: As of today, I managed to get myself into ODIN mode, but will only stay in ODIN mode for about
5 seconds before it shuts off. I can repeatedly do this as much as I want, but does not change anything to how long before it shuts off. I've tried rebooting through adb reboot-bootloader, but since my pc cannot find my device, I get this error "error: device not found". I made sure the drivers are installed, as they needed to be for me to even root my phone, but still no other results.
Also, when I take the battery out and put it back in, it vibrates as if it will boot up, but then red text saying "Movinand checksum..." comes up for a split second, then vibrates again with the same text. Then I can't do anything else until I remove the battery. I'm thinking about getting a JIG that will force it into download mode or recovery mode if one even exists.
Click to expand...
Click to collapse
The jig is for getting the phone into Download Mode, but I don't believe it's any help in keeping it there. If the phone won't stay in Download Mode, even with a charged battery, then I fear the phone is a lost cause. The only other thing that might help at this point would be a JTAG service, if it's available for that device like it is for the more popular Samsungs.
es0tericcha0s said:
The jig is for getting the phone into Download Mode, but I don't believe it's any help in keeping it there. If the phone won't stay in Download Mode, even with a charged battery, then I fear the phone is a lost cause. The only other thing that might help at this point would be a JTAG service, if it's available for that device like it is for the more popular Samsungs.
Click to expand...
Click to collapse
I'm not sure what I did, but I'm able to stay into ODIN mode for as long as I want. I'm still unable to boot into recovery. Is it possible to restore my phone through ODIN?
Sorry, I misunderstood. I thought you had said it reboots while in Download Mode. If it stays there, then that's definitely the 1st thing to try.
es0tericcha0s said:
Sorry, I misunderstood. I thought you had said it reboots while in Download Mode. If it stays there, then that's definitely the 1st thing to try.
Click to expand...
Click to collapse
Well, it stopped turning off while in download mode just recently. I'm just not sure what caused it. Also, I noticed that the battery I had in my phone when it first started shutting off is slightly bloated. I'm not sure if it's serious enough, but I know that bad batteries bloat, and they can potentially cause issues with your device. But I put my default battery in, but it didn't change anything in regard to the movinand error.
The Galaxy S Relay 4G can be a very odd challenge.
XmashMAN said:
Well, it stopped turning off while in download mode just recently. I'm just not sure what caused it. Also, I noticed that the battery I had in my phone when it first started shutting off is slightly bloated. I'm not sure if it's serious enough, but I know that bad batteries bloat, and they can potentially cause issues with your device.
Click to expand...
Click to collapse
Wow! I'm just making a note here as a marker I can return to and follow up on. This seems almost the worst that anyone can deal with. If the person that made this post just so happens to still be around, or for anyone who may be unfortunately dealing with such an issue, I have an either or "possible" fix, yet haven't been in this particular situation. There are repair files for this device I would assume could be used for this. I'm dropping them, and the last official Samsung software issued for the SGH T699. If I so much as even get a hint my device is going in this direction, I usually flash in the original firmware if and when I can. Back it up and flash it again just to make sure I have a clean build. I can work with stock. It's hard to work with a brick. This device can be very strange so far with any results I'm getting. Which is odd to me on one level because I've haven't had as much difficulty with any of my other devices such as I'm having with this one. I always try to be prepared for any eventuality before I start working on "any" device. I'd call it a very important suggestion, especially for this Galaxy S Relay 4G, to prepare yourself, it's going to be a fun ride!
Okay so one day i decided to Mess around with My LG G2 LS980, i got this phone from a friend and told me that this phone was working originally until he got it stuck between recovery and download mode, their was no fix for this because, i couldnt get my computer to detect that their is a phone connected to it and or it always kept reading it as "Unkown Device". So this one day i spend a few hours thinking and trying a few things. And this is how i fixed it.
Attempts-
-Cleaning the USB port on the phone with a qtip and some alchohal on it 70% -90% doesnt matter it did however make it to where my computer read something but it didnt fix my problem.
-I tried after a one day cleaning attempt and i did 10 minute to 20 minute wait for it dry and same result.
-I tried using my OTF by samsung and it didnt work maybe it was just because its samsung and not lg
- i also tried ADB sideloading and that didnt work because it kept saying it was trying to start and nothing at all.
- I also tried mounting the my OTG or anything nothing seemed to work.
Fix-
-Now here's the weird thing. My phone was already taken apart i used a guitar pick to remove the back cover and then i had a handy dandy mini philips screwdriver to remove the two back plastic peaces and look around the first barrier of the motherboard so im specifically looking and wondering if its the USB port/ Headphone jack chip and i didnt find anything that looked damaged but if that is the case i would have spent money to replace the whole USB port thing but i thought at least minute maybe it needs to be bent in someway to work.
-I had a preset desktop fresh and practically ready with drivers already installed for this flashing or fix, so nothing really would interfere.
-It was a pain in the ass really it was trying to get a certain position the usb port and be at and still hold the plug into the phone at the same time. Reinserting and checking my PC and Device Manager for a good 10 minutes. AS soon as i got a spot where it was best at.
- My Computer read it as a phone and other stuff from the guide. At first it installed drivers successfully but after i jiggled it a bit it messed up and it went into QHSUSB_BULK and idk what that meant and then windows prompted to me to format all this weird drives, i didnt do anything but leave it alone for a bit and i think it mightve went out of the mode because if it bends in a certain it stops being read i guess and then all of sudden after a few 3-4 trys plugging in after about minute during each removal and reinstering my computer read it as the LGE Android Modem and i check the ports and it was exactly the same thing as picture in the guide, i switched it to port 41, started the flash tool and i just waiting and it eventually started flashing and i got it working again but right now i can only seem to charge it theirs no way i cant MTP or anything at the moment.
So i use MoboDaemon to wirelessly transfer files. Kinda handy actually. you guys should try it out.
{ROOT}
Also downloading TowelRoot will root the phone easy peasy and then installing SuperSU or whatever and then hitting continue and normal and then rebooting of course and then everythings fine. The only part to flash a recovery is to flash an old one via. Free Gee by that app and allowing root rights and then downloading an updated TWRP 2.x for that phone and flash it via Rashr or Flashify, everything should be fine and dandy after that.
Thanks for looking at this, i hope some of you guys can fix your phone if this happened to you, its been 3 months and i didnt think about this at all until now at last minute.