Hi there - bit of a weird variation of the bootloop 'feature' here.
The phone works fine for while powered on, all features are available, and as far as I can tell, the phone seems in perfect working order. However, a second after I insert a USB cable to charge the phone, it locks up and then restarts. If you leave the USB cable in, the phone bootloops (doesn't reach the boot animation, just the LG splash screen).
You can actually charge it if you force the phone to reboot into recovery mode, where you're presented with the two options (factory reset or quit) and just don't choose anything, but this is a full-brightness screen that never turns off so is agonisingly slow to charge. This suggests to me that it might not be a hardware issue, just an issue with the ROM or something.
Unfortunately, this also happens when you plug the USB into a PC so I can't even wipe with LGUP or root/unlock bootloader. It is currently completely stock, international unlocked H850, running V20a-234-10. According to the guy that gave me the phone, this developed very recently at random, not after a software update etc.
I've also tried disabling USB charging using apps (but they require root anyway), and looked into disabling the power on my computer's USB port (and keep data transfer) but that doesn't seem to be possible.
Obviously factory reset it a few times, tried different cables and chargers, and I can't find any other threads/anything on the web about it.
Can anyone think of anything I can try? Any way I can make it flash/downgrade software without using a USB cable? Wireless adb would be perfect but requires a USB during the initial setup
Thanks in advance!
Most likely a battery defect, try to buy an original one, they're not so expensive. it should fix the issue. otherwise, it's an issue in the USb port, but i don't think it is.
Interesting - I can charge the battery using an external battery charger kit (the one I bought for my G4 actually, as the pins are in the same place) so I assumed the battery was ok, but I'll get a second just in case - thanks.
For info, I can have the device stay on with the USB plugged in in download mode too, and I've also updated the software to the latest available with no change.
New battery arrived today, no change unfortunately. I also bought a replacement standard module (charging port and speaker) but the phone won't accept it, shows the 'swap module' screen on boot and won't go any further.
Does anyone have any tips about trying to bypass/prevent that screen?
jackfacespoon said:
I also bought a replacement standard module (charging port and speaker) but the phone won't accept it, shows the 'swap module' screen on boot and won't go any further.
Click to expand...
Click to collapse
Having done some searching I bought a second replacement phone chin, same as the module I referenced above, which has solved the issue!
I can't find anyone else with this issue, but for posterity, it looks as if there are regional variations of the chin unit which the device detects on boot. My original chin had the code 'GLB 32' on it, the one that didn't work had 'GLB 46' (I think). I specifically asked for one from eBay with a similar number to my original, which when it arrived was 'GLB 33'.
This worked, but only on the second reboot, once I'd reattached it.
Hope this helps anyone else in my position.
EDIT: Mods can mark thread as Solved if they want!
jackfacespoon said:
Having done some searching I bought a second replacement phone chin, same as the module I referenced above, which has solved the issue!
I can't find anyone else with this issue, but for posterity, it looks as if there are regional variations of the chin unit which the device detects on boot. My original chin had the code 'GLB 32' on it, the one that didn't work had 'GLB 46' (I think). I specifically asked for one from eBay with a similar number to my original, which when it arrived was 'GLB 33'.
This worked, but only on the second reboot, once I'd reattached it.
Hope this helps anyone else in my position.
EDIT: Mods can mark thread as Solved if they want!
Click to expand...
Click to collapse
Dude, thanks for posting this! It's been happening to me for the last 4-5 weeks and I couldn't find any posts on this. Was it worth buying a new module? Has it lasted up until now? Thanks!
Related
I am having a problem with my Galaxy S3 when plugged into USB. It wont recognize the USB connection via laptop or charge via laptop or Samsung charger. Tried three official Samsung cables and chargers, 2 computers, and still nothing. The only time it recognizes anything is when the phone is in Download Mode. In which I can restore firmware and everything else. However, no matter what firmware I put, it still will not recognized the USB or charge. If anybody has any suggestions I would greatly appreciate it.
There are different drivers that need to be installed. As it recognizes the download mode seems like CDC driver is installed, but if you download kies, it should install all the necessary drivers automatically. Did you try it with a different computer? If this doesn't help then your last option is to factory reset.
Hope this helps
Sent from my GT-I9300
johrikushagra said:
There are different drivers that need to be installed. As it recognizes the download mode seems like CDC driver is installed, but if you download kies, it should install all the necessary drivers automatically. Did you try it with a different computer? If this doesn't help then your last option is to factory reset.
Hope this helps
Sent from my GT-I9300
Click to expand...
Click to collapse
Downloaded Kies. Has all the correct drivers. Tried two different computers. Have two Galaxy S3's, swapped out batteries. Both batteries are good in one phone. The other phone just wont recognize USB or charge in any situation. Factory reset it 3 times. Cleared everything off the phone. Didnt change anything. Factory ROM no kernel hacks or anything. Cables are genuine Samsung that came with the phone. Used mine and my friend's cable for his S3. When you plug the phone in when the power is off, u can see the battery, but then the screen goes black and doesnt charged. Also we charged up both batteries fully using one good S3 proving both batteries are good. Im out of ideas..Thanks for the reply! I appreciate it!! :laugh:
evospot said:
Downloaded Kies. Has all the correct drivers. Tried two different computers. Have two Galaxy S3's, swapped out batteries. Both batteries are good in one phone. The other phone just wont recognize USB or charge in any situation. Factory reset it 3 times. Cleared everything off the phone. Didnt change anything. Factory ROM no kernel hacks or anything. Cables are genuine Samsung that came with the phone. Used mine and my friend's cable for his S3. When you plug the phone in when the power is off, u can see the battery, but then the screen goes black and doesnt charged. Also we charged up both batteries fully using one good S3 proving both batteries are good. Im out of ideas..Thanks for the reply! I appreciate it!! :laugh:
Click to expand...
Click to collapse
Well if you say, that you did a full wipe, just curious that after factory reset did you restored it from a backup or started new. I recommend start new. Even if this doesn't help than it definitely seems a hardware problem. Get it checked.
Just wanted to share. I had a Iphone 4s and suddenly it stopped charging through a wall charger and used to charge through a usb, after numerous restores I got it checked and there seems the problem.
Sent from my GT-I9300
johrikushagra said:
Well if you say, that you did a full wipe, just curious that after factory reset did you restored it from a backup or started new. I recommend start new. Even if this doesn't help than it definitely seems a hardware problem. Get it checked.
Just wanted to share. I had a Iphone 4s and suddenly it stopped charging through a wall charger and used to charge through a usb, after numerous restores I got it checked and there seems the problem.
Sent from my GT-I9300
Click to expand...
Click to collapse
Started brand new. Didnt restore from any backups or anything. Didnt root it at all. It seems as whatever the firmware that it uses for charging just stopped working...Im at a dead end...its funny because there isnt any topics online with a single similar symptom.
I have the same problem..
It doesn't give any notice when i plug it into the computer,
when i charge it the screen gives a grey battery loading picture
and then just turns black.. i can still acces download mode and use odin..
which makes it really strange..
it would be great if someone knows how to solve this
Thx in advance!
Reedee said:
I have the same problem..
It doesn't give any notice when i plug it into the computer,
when i charge it the screen gives a grey battery loading picture
and then just turns black.. i can still acces download mode and use odin..
which makes it really strange..
it would be great if someone knows how to solve this
Thx in advance!
Click to expand...
Click to collapse
I have the exact same problem on my note 2, have been searching everywhere but cant seem to find an answer.
First of all hello xda, long time reader, first time poster.
I know it's been a long time since the last post, but instead of starting a new thread i suppose it's better to post here.
I got the same problem a few weeks ago and tried everything software-wise and still nothing. I noticed that when i turn my phone on i get a notification "USB connector connected" which leads me to believe that something is keeping the connector busy and unable to charge/connect exept when in d/l mode. Has anyone found a fix for this yet? I'd like to try and fix it myself before taking it in for repair.
Reedee said:
I have the same problem..
It doesn't give any notice when i plug it into the computer,
when i charge it the screen gives a grey battery loading picture
and then just turns black.. i can still acces download mode and use odin..
which makes it really strange..
it would be great if someone knows how to solve this
Thx in advance!
Click to expand...
Click to collapse
I have exact same problem. Seemed to occur out of the blue. I took it off the car charger and everything appeared as normal until the next day I go to charge it with wall charger and no response, except for the grey battery image appearing for 2 seconds when and only when powered off and plugging in the charger. Tried many cables/chargers to no avail. There is also no response connecting to a PC, when the phone is on.
For the moment I can charge the battery(s) with an external charger and still use my phone.
I made a simple USB cable current monitor once to measure current consumption of portable devices. Just a 0.1ohm resistor in series with the USB V_BUS (+5V) pin. Since this fault occurred, the V_BUS pin current after plugging in the charger, starts off 250mA for few seconds while the grey battery image appears then the phone shuts down with a 5mA residual current. Clearly the battery is not being charged. Previous to the fault, V_BUS current during full charge is around 950mA. I'm sure its a hardware problem.
Adam
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
I know, I know, another bootloop thread. I've been reading dozens of them and I can't find my problem, please forgive me.
My wife's phone was stolen, and so we bought a used one from a stranger after seeing a listing on a local sales site (gumtree). Bad call - they demo'd it for us, but we didn't power it off and on before buying. After parting with cash, we find the phone won't boot unless it's plugged in to AC power (and not USB). All it does is loop grey/green battery logos over and over. Sometimes vibrating, sometimes not, but it would never break the loop, except to enter download mode, unless I connected it to AC power.
If I did boot it, I couldn't do some stuff, like enable USB debugging - it flat out wouldn't allow me to check that box. So I checked the kernel, and it seemed to have a weird kernel installed, so I thought it was time to just re-flash with the official firmware.
Well, first I wanted to try SlimROM, but I couldn't get to CWM Recovery (which was already installed) reliably, and on the rare instance where I could get it to come up, I couldn't navigate to extSD where the slim files were, nor mount USB storage (the PC wouldn't recognize it).
So I decided to try and re-flash to stock, using ODIN and the official samsung FW that worked well on my own GS2. This worked, after a fashion - I could get it to boot if I applied AC power, but things were badly broken. It'd reboot a minute or two after the setup began, and so I was forced to suspect either hardware failure or something that survived a complete wipe and flash.
So I thought kernel. The only one I had lying around that I knew worked was an old jeboo kernel. I flashed it with ODIN, and presto - it worked! The thing booted and stayed stable.
But I still have that accursed battery loop when the phone's off, the battery needs to be yanked to keep it actually powered down. And there are other bugs, like the screen comes on after you turn it off with the power button. Just once, but now it can't be powered down and ignored - you turn the screen off and wait to see if it comes back on and do it again.
And it's confused about charging - this morning it reported the AC adaptor was a USB charger, and this evening it thinks both USB and the AC adaptor are both AC (in the battery info settings screen).
And the only way to get it to boot reliably now is to remove the battery and plug it back in, at which point it boots as normal.
So, after all that long winded four-hours-of-tears-and-anger story, my question is this: What's the battery boot loop all about? Why does the screen flicker constantly when it's charging via AC? Why does it take -twenty seconds- to recognize it has been plugged in to power?
I can't install CWM, it won't enter recovery or boot successfully (no loop, just hangs on the yellow triangle screen). Before I start randomly applying new ROMs via odin, I'd like to find out more about my problem.
Please, can anyone shed light on this? I thought I knew what I was doing but I'm coming up empty here.
Sounds like the USB board/port (tho it might be worse than that; this is what I'd replace first). Relatively cheap/easy to replace; but you do need to check which board is currently in the phone & ensure you get the exact same as a replacement - there's 4 different boards, get the wrong one & you won't fix the problem/waste time & money.
Search for similar threads, there have been detailed threads in Q&A over the past few mths, those threads should have the info you need.
There's also a chance it might be as simple as the battery on the fritz, if you're able, try another one.
But definitely sounds like the USB board (hopefully for you) to me
Thanks for the suggestion. Certainly the flickering while charging issue and the delay to recognize the charger being plugged in point towards a USB board issue, but what I can't figure is the reluctance of the unit to boot without changing the kernel. Wouldn't the stock ROM via ODIN have included the stock kernel? Why does CWM cause the unit to lock up during boot?
Last night the thing stopped flickering on AC and recognized the charger cable instantly - is this a self-calibrating feature? (My research of a thousand similar threads seems to suggest a lot of battery issues correct themselves). For the record, the phone did come with a second 3rd-party battery, but neither it nor my own original GS2 battery make any difference.
So... Yeah, I'm still not sure if this is a hardware problem, software problem, or both.
Also last night I followed a suggestion from another thread and loaded up touchwiz, changed the screen timeout and switched back to apex launcher, and the screen started shutting off as desired. This morning it doesn't work anymore, and the phone is frequently found with the screen turned on. =/
Ok so by flashing full stock rom that practically eliminates the software side of things. Now do what mistahbungle said. My money is also on the usb board. I had to replace mine recently. Click the link on my signature, from there you can get onto a guide by keithross39 on how to DIY if you choose.
Sent from a galaxy far, far away
'practically eliminates' indeed. I still can't work out why I had to flash a new kernel to get it to boot. =/
NFGman said:
'practically eliminates' indeed. I still can't work out why I had to flash a new kernel to get it to boot. =/
Click to expand...
Click to collapse
Do you want help, or do you want to continue doing what you think will fix the problem? If you're having the same issues on full stock, it indicates hardware issue. The software won't work unless the hardware is functioning correctly. Let me think, what did MistahBungle say was the problem? Oh that's right. The USB board. Hardware.
Oh, sorry, I thought we were having a conversation. Should I not talk until I get the replacement part?
I'm not disagreeing, I'm fully prepared to accept the USB board is part or all of the problem, but I still wonder why etc etc.
OK....so....firstly, flashing a standard single file firmware won't fully wipe the previous software.....all it does is overwrite what it needs to (leaving who knows what untouched). The easiest way to regain a 'clean slate' is to flash a 3 part test firmware which DOES complete a full wipe during the flash..... @Hopper8 s guide provides a link to this test firmware and full instructions as to how to install it.
Secondly.....hardware faults can/do cause unexpected operational issues......some of the issues you describe were appearing on my wife's S2 before I replaced the USB board on her phone (they disappeared afterwards). As @Hopper8 has mentioned, his guide includes a link to my guide concerning the replacement of this part. I personally would hold off doing any more Odin flashes until you have replaced the board......if the USB port fails during a flash (because of a faulty board) you'll end up in a 'whole world of hurt' that will be infinitely worse than it is now.......
Sent from my GT-I9100 using xda app-developers app
Thanks to both of you for the responses. I've taken the phone to a repair shop and they swapped out the USB board to no avail. =/
Given what you've already spent on it (cost of phone + replace USB board), if I were in your situaton, I'd be cutting my losses & put it down to experience rather than replacing the motherboard (with a 2nd hand board from a 'donor' phone), whilst that's nowhere near as expensive as paying a service centre to put a new board in, it's still likely to cost you >AUD$100. If you can get one for a lot cheaper than that, maybe it would be worthwhile.
NFGman said:
Thanks to both of you for the responses. I've taken the phone to a repair shop and they swapped out the USB board to no avail. =/
Click to expand...
Click to collapse
Or...as first measurement, you clean the pins briefly and bend the holder slightly back to the center.
Tapatalked from my Galaxy SII
By 'holder' do you mean the USB port, or the connection inside the phone between the USB board and main board?
It's not a physical problem, at least in the USB port... I mean, we put a new one in it and nothing changed.
NFGman said:
By 'holder' do you mean the USB port, or the connection inside the phone between the USB board and main board?
It's not a physical problem, at least in the USB port... I mean, we put a new one in it and nothing changed.
Click to expand...
Click to collapse
Ah the usb board had already been replaced? Okay then forget about my proposal, sorry.
Tapatalked from my Galaxy SII
So the next step is either a motheboard replacement or the bin.
I realise this isn't what you want to hear, but think logically about it...You bought a 2nd hand phone from someone you don't know/had no idea what they'd put the phone through before you bought it, it crapped itself shortly after, giving no indications whatsoever the problems are firmware/software related, and showing a number of symptoms which indicate something major is wrong hardware-wise.
You tried the cheap/obvious & that didn't work, one way or another you need to bite the bullet (both options involve you spending a not insignificant amount of money in all likelihood, unless you can score a donor phone cheap).
MistahBungle said:
So the next step is either a motheboard replacement or the bin.
Click to expand...
Click to collapse
Way ahead of you. Ordered a new (NEW this time) phone. Will be selling the S2 to the next guy, along with the caveat "Sometimes the screen comes on." Will lose a few bucks, but it'll go into the old logbook of lessons well and truly learned. ^_^
Thanks for your help.
Hello
Yesterday my phone randomly shutdown. After that I werent able to turn it on even after wiping everything and reinstalling the rom. When I came back home i flashed the official firmware with odin and it didn't work as well. Then I managed to turn it on successfully while it was plugged to a charger. I managed to observe that when I normally turn it on it starts only plugged to a charger and turns off after cuople of seconds. This doesn't happen when I enter recovery mode or download mode - I can boot successfully up my device to these modes and it doesn't turn off without need to be plugged. What do you think happened to the device? Can it be fixed on the software level? If not how much do you think it would cost to fix this if it is a hardware issue?
up
Are you sure your battery is healthy?
Remove your battery and see if it has got any exapndings or swelling? Cause I had the same issue except after losing half of it charge it would suddenly turn my phone off like I'm removing my phone when it's still on!
The battery looks 100% normal. I'll check tomorrow with my friend's battery. But in recovery mode phone doesn't have any problems.
Any other ideas? Can it be anyhow software related? If so is there any option to fix this? What should i try?
Replace USB board/port; quick/cheap easy to do yourself. KeithRoss39 has a guide in General (not stickied, search for 'replace USB charger board' or similar) which has all the info you need to get it done.
MistahBungle said:
Replace USB board/port; quick/cheap easy to do yourself. KeithRoss39 has a guide in General (not stickied, search for 'replace USB charger board' or similar) which has all the info you need to get it done.
Click to expand...
Click to collapse
But the phone does charge well. And it works on battery in recovery. It turn on normally only plugged into power source and the shutdown randomly. How could changing usb port could fix that issue?
Because USB board problems almost always (at least that's been the experience on here) manifest themselves by showing a few faults & working OK otherwise, rather than dying completely - you might be able to charge OK, you might not be able to transfer data all the time; you might be able to transfer data OK, you might get constant shutdowns which you can't explain by changing firmware & trying a new battery.
Everything you've said in this thread so far points to the USB board, and as this is an easy & cheap fix, if it was my phone, that's what I'd be replacing to try and fix it. Put it this way, given how cheap it is (around US$10-$15), if this doesn't fix it, then you'll know there's probably something more major hardware-wise going on. I wouldn't be taking it to a mobile repair shop to have this done though, as obviously they'll probably charge you a crapload in labour to replace a $10 part. Save that for if changing the board doesn't work.
Thanks for your effort. The problem is I don't think i can do it myself. I don't want to spend much money on this phone cause it is quite old. That is why I kind of don't what to do now
Before one month ago a strange problem appeared.i flashed different roms and kernels but a few days later after a complete dischargeof the battery when I completely charged my phone with the charger it tried to reboot and it didn't pass the boot screen.This problem was solved only with a full wipe and a reflash of a rom.But if I try to use the charger instead of pc to charge my phone or if I complete discharge it sometimes It will not boot.i tried a lot of different roms and kernels without success .any ideas what causing this problem?
dadmcleader said:
Before one month ago a strange problem appeared.i flashed different roms and kernels but a few days later after a complete dischargeof the battery when I completely charged my phone with the charger it tried to reboot and it didn't pass the boot screen.This problem was solved only with a full wipe and a reflash of a rom.But if I try to use the charger instead of pc to charge my phone or if I complete discharge it sometimes It will not boot.i tried a lot of different roms and kernels without success .any ideas what causing this problem?
Click to expand...
Click to collapse
Probably the USB board/port. KeithRoss39 has a guide in General (not stickied; search for 'replace USB charger board') which will enable you to replace it yourself quickly/easily/cheaply (<US$15).
dadmcleader said:
Before one month ago a strange problem appeared.i flashed different roms and kernels but a few days later after a complete dischargeof the battery when I completely charged my phone with the charger it tried to reboot and it didn't pass the boot screen.This problem was solved only with a full wipe and a reflash of a rom.But if I try to use the charger instead of pc to charge my phone or if I complete discharge it sometimes It will not boot.i tried a lot of different roms and kernels without success .any ideas what causing this problem?
Click to expand...
Click to collapse
my friend what is the rom now you are using?
if it is based on cm try stock roms
if it is not then i think the problem is from your charger .. try someone else .
you can also try wipe battery statue from recovery
Good luck
MistahBungle said:
Probably the USB board/port. KeithRoss39 has a guide in General (not stickied; search for 'replace USB charger board') which will enable you to replace it yourself quickly/easily/cheaply (<US$15).
Click to expand...
Click to collapse
Ok thank you very much for your answer.Do you think that it could be the charger instead of usb board/port because it seems that if i try to charge it via usb cable from pc or if i try another charger it will boot normaly but the problem is that i don't know for sure because i only use my charger when the phone is completely discharged (turned off) ,i usually have my phone connected to pc all the time,so i also suspect that it may be the reboot that causes the phone to boot loop and it may be not connected to the charging proccess at all.What is your opinion ?
Also is there any way to test my usb board/port to see if it working correctly before replacing it ?
Bashar Jarad said:
my friend what is the rom now you are using?
if it is based on cm try stock roms
if it is not then i think the problem is from your charger .. try someone else .
you can also try wipe battery statue from recovery
Good luck
Click to expand...
Click to collapse
I tried both stock and aosp roms but with no luck.
I tried different chargers but the problem doesn't appear every single time so i don't know for sure if the problem is from my charger.Sometimes it boots normaly with mine too.
I didn't try to wipe battery stats from recovery but how it could be useful ?I couldn't find a lot info for that...
thanks
Might be the charger, so try a new one if you like. But don't be surprised if you end up having to replace the USB board after. The issues you described with booting/not booting sound like symptoms of the USB board on the fritz.
When the boards start dying, they rarely stop working completely (at least initially), and often show a couple of faults, but work OK in other ways (might be able to transfer data OK but can't charge as an example, and so on).
As a test, do a completely clean install of stock & test it for a few days, if you see the same thing, it's fairly likely the hardware fault. Up to you which way you want to go in that case, but I'd be replacing the board.
Edit - In light of your post just now which crossed with my reply, it's definitely the USB board. You've tried different chargers, you've tried stock, that seals the deal as far as I'm concerned. Put it this way, if it's not the board, it's something else hardware-wise.
MistahBungle said:
Might be the charger, so try a new one if you like. But don't be surprised if you end up having to replace the USB board after. The issues you described with booting/not booting sound like symptoms of the USB board on the fritz.
When the boards start dying, they rarely stop working completely (at least initially), and often show a couple of faults, but work OK in other ways (might be able to transfer data OK but can't charge as an example, and so on).
As a test, do a completely clean install of stock & test it for a few days, if you see the same thing, it's fairly likely the hardware fault. Up to you which way you want to go in that case, but I'd be replacing the board.
Edit - In light of your post just now which crossed with my reply, it's definitely the USB board. You've tried different chargers, you've tried stock, that seals the deal as far as I'm concerned. Put it this way, if it's not the board, it's something else hardware-wise.
Click to expand...
Click to collapse
Ok i will start testing then and replace the usb board if needed.Another thing that confuse me is why the phone boots with a full wipe and re-install of a rom ?Also in what way the USB board can affect the booting proccess?
EDIT :I am not experienced with smartphone hardware so i need some info...
I don't think that anybody outside of Samsung themselves would be able to tell you why one of their phones acts the way it does.....they know their hardware and the way software interacts with it in a way that nobody else can.
All I know is that I've handled TWO S2's with faulty USB ports, and they have exhibited various symptoms as a result.......
1) phone displayed charging icon even if it wasn't plugged in.
2) phone NOT charging even though it WAS plugged in.
3) PC/Laptop not recognising phone when USB connected.
4) phone randomly shut down.
5) phone would not boot unless boot option in CWM selected.......
I could go on, but you probably get the picture.
These issues stopped occurring on both devices as soon as I'd replaced the USB assembly......
Choice is yours fella, but I know what I'd be doing.
Sent from my GT-I9100 using Tapatalk
keithross39 said:
I don't think that anybody outside of Samsung themselves would be able to tell you why one of their phones acts the way it does.....they know their hardware and the way software interacts with it in a way that nobody else can.
All I know is that I've handled TWO S2's with faulty USB ports, and they have exhibited various symptoms as a result.......
1) phone displayed charging icon even if it wasn't plugged in.
2) phone NOT charging even though it WAS plugged in.
3) PC/Laptop not recognising phone when USB connected.
4) phone randomly shut down.
5) phone would not boot unless boot option in CWM selected.......
I could go on, but you probably get the picture.
These issues stopped occurring on both devices as soon as I'd replaced the USB assembly......
Choice is yours fella, but I know what I'd be doing.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
MistahBungle said:
Might be the charger, so try a new one if you like. But don't be surprised if you end up having to replace the USB board after. The issues you described with booting/not booting sound like symptoms of the USB board on the fritz.
When the boards start dying, they rarely stop working completely (at least initially), and often show a couple of faults, but work OK in other ways (might be able to transfer data OK but can't charge as an example, and so on).
As a test, do a completely clean install of stock & test it for a few days, if you see the same thing, it's fairly likely the hardware fault. Up to you which way you want to go in that case, but I'd be replacing the board.
Edit - In light of your post just now which crossed with my reply, it's definitely the USB board. You've tried different chargers, you've tried stock, that seals the deal as far as I'm concerned. Put it this way, if it's not the board, it's something else hardware-wise.
Click to expand...
Click to collapse
I replaced the usb board about a month ago but i still have bootloop issues that appear randomly.
I also have some other issues now.
First of all when i try to transfer files from/to pc the copy procedure will stop at some point and then windows does not recognize my phone or a pop up window appear asking to fix my drive but when i try to fix it says that the drive has no problems.
Apart from that if i try to remove the battery and then put it again with the charger still connected to the phone the battery percentage fall from 100% to 10%-15%.
I dont know if all these problems are related but it seems that the usb board is not responsible for these issues because i have the same problems with 2 different boards.Any ideas what else hardware-wise might be ?
Thanks in advance !
My money's still on the usb board.....
Check the OP in this thread......
http://forum.xda-developers.com/showthread.php?t=2335961
.....paying PARTICULAR attention to the part covering 'rev' versions.......
Sent from my GT-I9100 using XDA Free mobile app
keithross39 said:
My money's still on the usb board.....
Check the OP in this thread......
http://forum.xda-developers.com/showthread.php?t=2335961
.....paying PARTICULAR attention to the part covering 'rev' versions.......
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
I read carefully the OP and the replacement that i bought is the same 'rev' version with my old one.So is possible that the new usb board is faulty too ?
Is it possible to be something wrong with the internal SD ?
I want to mention that i have used a PIT file posted by @metalgearhathaway to increase data partition but the procedure was successful...
The only reason that i mention it is because then i had the faulty usb board and i used ODIN for the procedure but it passed all stages succesfully.
Mate.....remapping the partitions with a pit file is a pretty major thing to forget to mention.....
It's pretty advanced and/or risky to start messing with pit files.....it's also something i've never done, so i'm unsure of the consequences.......apart from the obvious 'permabrick' risk.
I don't even know how you'd revert to the factory set partitions if you needed to.....though i'd guess it'd involve flashing another pit file. All the issues you've previously mentioned (apart from the battery) *could* have been caused by the pit file and that being the case, you're lucky it wasn't a whole lot worse. As for the battery, that could simply be the fact that batteries do fail, and if yours is the original, this is probably the case given the age of the phone and the fact that Samsung only offers a 6 month warranty on the battery anyway.......
Sorry fella, but as there's a pit file flash involved, you've moved into territory that I can no longer advise on........
Sent from my GT-I9100 using XDA Free mobile app