I have a Samsung Galaxy S2 Epic Touch for Virgin Mobile I'm selling to a friend of mine. It's been working great for me for about the last year on VM. It was rooted and running Liquid Smooth and then CM 10.1 (both using CWM). When I called VM to transfer the phone to my friends account we ran into a road block because CM doesn't respond to the keypad phone codes VM uses to update the phone, or have the VM hands free activation apps.
I figured I might as well flash back to stock ROM anyway. I downloaded the ROM from here.
Odin got about 75% of the way through the flash and then failed. The phone won't turn off but instead keeps up a persistent splash screen asking me to connect the phone to Kies to do a system recovery (Which I did try and Kies can't seem to complete the connection. It sees the phone but can't connect to it, even after ensuring all drivers are up to date. But then I've never had much success with Kies).
I can still get into Odin on my phone so I tried downloading the .exe ROM instead of the md5 this time, but by the time the ROM downloaded Odin tells me the battery is too low to flash anything (which I believe). Problem is I can turn the phone off to let it charge properly (it pops up with the Kies message whenever I plug the phone in).
I've left the phone plugged into the wall hoping that maybe it is in fact charging, but the indicator light only flashes for a second when I plug it in. I'm working a double shift today so I left the phone at home hoping it will charge so that I can try flashing again, but does anybody have any experience with this sort of problem, or know if the phone will in fact charge?
jonnierod said:
I have a Samsung Galaxy S2 Epic Touch for Virgin Mobile I'm selling to a friend of mine. It's been working great for me for about the last year on VM. It was rooted and running Liquid Smooth and then CM 10.1 (both using CWM). When I called VM to transfer the phone to my friends account we ran into a road block because CM doesn't respond to the keypad phone codes VM uses to update the phone, or have the VM hands free activation apps.
I figured I might as well flash back to stock ROM anyway. I downloaded the ROM from here.
Odin got about 75% of the way through the flash and then failed. The phone won't turn off but instead keeps up a persistent splash screen asking me to connect the phone to Kies to do a system recovery (Which I did try and Kies can't seem to complete the connection. It sees the phone but can't connect to it, even after ensuring all drivers are up to date. But then I've never had much success with Kies).
I can still get into Odin on my phone so I tried downloading the .exe ROM instead of the md5 this time, but by the time the ROM downloaded Odin tells me the battery is too low to flash anything (which I believe). Problem is I can turn the phone off to let it charge properly (it pops up with the Kies message whenever I plug the phone in).
I've left the phone plugged into the wall hoping that maybe it is in fact charging, but the indicator light only flashes for a second when I plug it in. I'm working a double shift today so I left the phone at home hoping it will charge so that I can try flashing again, but does anybody have any experience with this sort of problem, or know if the phone will in fact charge?
Click to expand...
Click to collapse
The easy options are to borrow a battery from a friend with a s2 phone, or get a charger off ebay, or buy a new battery from the store which will probably come with a partial charge.
Sounds like your usb port may have died. That happens sometimes.
I was thinking of borrowing a battery. I have a friend with the same phone, so that's possible.
If the USB charger failed, however, would the blue charging light still flicker on when first plugged in? Because that's what it does. It doesn't charge, but it does seem to acknowledge that it's been plugged in. Also, when plugged into the computer it will still flash the plug me into Kies screen, but now my computer doesn't seem to even recognize that anything is plugged in.
Sent from my HTC0P4E1 using Tapatalk
jonnierod said:
I was thinking of borrowing a battery. I have a friend with the same phone, so that's possible.
If the USB charger failed, however, would the blue charging light still flicker on when first plugged in? Because that's what it does. It doesn't charge, but it does seem to acknowledge that it's been plugged in. Also, when plugged into the computer it will still flash the plug me into Kies screen, but now my computer doesn't seem to even recognize that anything is plugged in.
Sent from my HTC0P4E1 using Tapatalk
Click to expand...
Click to collapse
It is possible. I had a phone that the data burnt out on, but would still charge. Just one pin needs to be bad to cause some issues, but not break everything.
Could just be the battery is totally empty too. Getting a known good battery with a charge is the first step to troubleshoot this.
I have encountered this problem a time or two before when testing some of my many attempted multiwindow mods, the device will in fact charge, but it is going to take forever. After a double shift I would imagine you'd have enough charge to flash properly, so try it again afterwards. Also have you attempted to return to recovery? If Odin only partially completed, your custom recovery may still be there and you might be able to use the power off option from recovery, while the device is plugged in, and possibly tricking it into not powering on to the error screen.
WARNING! Everything in blue is simply conjecture and has not been proven to work, it is simply a working theory. If it does not work don't say I didn't warn you.
Related
So I have been a long time follower of XDA, did all sorts of things with my Vibrant and just recently got the SGS2 from Sprint. A few days ago I flashed Calkulin's E4GT v2.6 and since then everything has gone down hill:
> The phone started acting like it was "charging" with nothing plugged in, red LED light stayed on and the battery had the charge symbol.
> Car mode began coming on over and over again.
> The phone would freeze and after I took out the battery it would automatically restart with me pushing the power button once the battery was re-inserted.
In hopes to just be down with it I flashed it back to stock with ODIN and everything seemed fine...
Now the phone is constantly freezing, Displaying that I have no service, The touch screen becomes unresponsive while charging, Car mode is still trying to launch.. not as frequently but it has happened. Other minor issues was the pattern lock would display when I woke up the phone even though I never set one...but I could do anything with the pattern to unlock it, even just touching a circle. Worse part in my opinion is either the phone will not recognize the PC or the PC will no longer recognize the phone so I can try ODIN again, same PC, drivers and USB cord being is.
Any suggestions on how I can remedy the situation?
Same thing happened to me, when I tried flashing an AIO over Calkulins you're pretty much done. You'll have to unroot and go to sprint. I ended up getting a new one since I was within the 2 week exchange.
monk3yguy said:
So I have been a long time follower of XDA, did all sorts of things with my Vibrant and just recently got the SGS2 from Sprint. A few days ago I flashed Calkulin's E4GT v2.6 and since then everything has gone down hill:
> The phone started acting like it was "charging" with nothing plugged in, red LED light stayed on and the battery had the charge symbol.
> Car mode began coming on over and over again.
> The phone would freeze and after I took out the battery it would automatically restart with me pushing the power button once the battery was re-inserted.
In hopes to just be down with it I flashed it back to stock with ODIN and everything seemed fine...
Now the phone is constantly freezing, Displaying that I have no service, The touch screen becomes unresponsive while charging, Car mode is still trying to launch.. not as frequently but it has happened. Other minor issues was the pattern lock would display when I woke up the phone even though I never set one...but I could do anything with the pattern to unlock it, even just touching a circle. Worse part in my opinion is either the phone will not recognize the PC or the PC will no longer recognize the phone so I can try ODIN again, same PC, drivers and USB cord being is.
Any suggestions on how I can remedy the situation?
Click to expand...
Click to collapse
What exactly did you use when you did this? I flashed it back to stock with ODIN
Maybe link to the file(s) you used?
Also maybe the exact steps you took. None of this sounds right. And if you flashed the complete EG30 tar you would be back exactly to when you purchased the phone. Everything would be overwritten so there really wouldn't be anything left to linger and cause issues.
Try a ##786# reset
Just_s said:
What exactly did you use when you did this? I flashed it back to stock with ODIN
Maybe link to the file(s) you used?
Also maybe the exact steps you took. None of this sounds right. And if you flashed the complete EG30 tar you would be back exactly to when you purchased the phone. Everything would be overwritten so there really wouldn't be anything left to linger and cause issues.
Click to expand...
Click to collapse
Once the device started acting funny, I basically pulled out the battery until I got home where I could flash it back.
This is the stock files I have saved to my computer:
http://forum.xda-developers.com/showthread.php?t=1351761
The phone is still somewhat usable, 3G, voice calls, everything works as normal until some of the symptoms start up again. Primarily the issues I am having is the phone completely freezing and occasionally displaying no service and of course not recognizing any PC connection.
Try a ##786# reset from dialer.
To get your MSL, in adb shell, type "getprop ril.MSL" without the quotes. If you use Android Terminal make sure you aren't using the Swype keyboard or it'll auto capitalize the "I" despite being told not to.
Initially, sounds like the USB port has some **** in it or damaged ;p
First off thank you everyone who has replied, I have definitely looked into all of your suggestions throughout the day. Here is what I have come up with.
I tried the ##786# for a clear reboot, all the symptoms still continued =(
I started figiding with the micro USB port and finally was able to get my computer and phone to connect to each other, I have also been reading that the port also causes the phone to spontaneous "ghost" charge and activate car mode.
So I am pretty sure it is a hardware issue, in particular the usb port. Tomorrow I am going to get the parts and make a jig to reset the binary counter and just take it in to Sprint and get an exchange.
Here is what happened on my month new Galaxy Nexus.
1. Listening to mp3 via Bluetooth headset
2. Playing a game
3. Standing up
4. On a train
Sound stopped working across everything, in the game and on the mp3. Tried killing the applications and reloading, the mp3 player refused to even start the mp3.
Rebooted the phone, well, I turned it off. It has never turned back on. Tried removing the battery, all that, nothing.
Got home, tried plugging in the USB into a PC. Nothing. Tried booting into recovery mode, nothing, other than the PC claiming to have found a new device.
I haven't plugged it into a PC in recovery mode before. I haven't even seen recovery mode on the Galaxy Nexus.
I was running OTA Vodafone UK 4.0.2 I hadn't even considered rooting it or anything.
Anyone know if this is salvageable or had the same happen to them?
Hi. If popping the battery does no good I'd get it replaced without any further investigation. Sounds like hardware fail, so long as you are sure you have not got it wet or caused any damage to it.
Sent from my Galaxy Nexus using XDA App
If you cant bring it back on after a battery pull then its a dead phone for sure
I had the same problem last month. An usb jig solved the problem.
USB Jig?
Any more details? Something you can point me at?
Cheers
Found this:
http://forum.xda-developers.com/showthread.php?p=20504509
Appropriate?
So does the phone show anything at all? Does the screen come up for any amount of time? Can you get into bootloader?
So for completeness I have exactly this issue:
http://forum.xda-developers.com/showthread.php?t=1384415
Basically this paragraph:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Click to expand...
Click to collapse
Sounds like a USB Jig might do it. But in this case its back to vodafone and jumping through those hoops.
For the record I hadn't done anything at all to the phone than a normal consumer would. i.e. no rooting, hacking, booting, fruiting or cheesing.
It just died.
As much as I hate this phone on any version after 4.1.2, I was enjoying/accepting 4.3 for the last month until I got the OTA yesterday and now my phone won't charge while it's booted into Android. I'm talking a normal wall charger, not USB. Although on that note, I can no longer access my media via USB after this update either. When I plug the phone in Windows says it's an unrecognized device. Turning the phone off and back on while it's plugged in will charge it standalone (with the giant battery icon on the screen) but that's about it. Any ideas on this one? I haven't seen anyone else with this issue. Thanks guys
Sorry I should add that I'm not rooted or anything - when 4.3 came out I did a complete factory wipe with the image from Google.
Hello everyone. My brother has the SM-T320. It doesn't power on at all. But if I plug the tablet directly into an outlet or laptop, it turns on but immediately goes to "recovery booting" and looping and not actually turning on. I can press the Power+Volume Down buttons to go to Download mode. I have three laptops at my disposal. I installed the Samsung USB drivers on two, and just Samsung Kies on the other. I have also tried different Odin versions (3.07 and 3.09) and it still won't connect. I also bought a different battery, and even if I leave it charging (aka bootlooping), if I disconnect it, it turns off. Essentially, I think the firmware is messed up and simply doesn't recognize the battery. So that's why I wanted to flash a stock recovery. Any ideas what I can try? Thanks a lot for the help!
I should also mention that I tested battery connection (tablet plugged into an outlet with the battery removed) with a volt meter and I gut 4.45V, which I think is fine?
mark1995n said:
Hello everyone. My brother has the SM-T320. It doesn't power on at all. But if I plug the tablet directly into an outlet or laptop, it turns on but immediately goes to "recovery booting" and looping and not actually turning on. I can press the Power+Volume Down buttons to go to Download mode. I have three laptops at my disposal. I installed the Samsung USB drivers on two, and just Samsung Kies on the other. I have also tried different Odin versions (3.07 and 3.09) and it still won't connect. I also bought a different battery, and even if I leave it charging (aka bootlooping), if I disconnect it, it turns off. Essentially, I think the firmware is messed up and simply doesn't recognize the battery. So that's why I wanted to flash a stock recovery. Any ideas what I can try? Thanks a lot for the help!
Click to expand...
Click to collapse
OK so it is in download mode when you connect it to Odin?
Hey everyone, I got the problem partly fixed. I was able to reset it to original firmware by using the Samsung kies3 software. It somehow was able to recognize the device even though Odin couldn't. However, turns out, the reason tablet would turn on only when plugged in is because the battery wasn't connected completely. The battery connector on the motherboard itself is separating and so the pins are not touching the board completely. My ghetto temporary fixed was to cut and stick part of a bobby pin over it to clamp it in place. However, this will probably damage the connector/board in the long term. I'm not very good with soldering parts/pins that are this small, and nor do I have special equipment besides solder and soldering iron, so I'm trying to figure another clever way of holding it strongly in place. If anyone has any idea how to go about that, it would be appreciated.
Hi,
I have the SM-T310 Galaxy Tab 3 8.0 variant with stock android 4.4.2 and was rooted with Xposed Framework installed. I need some help and advice on how to fix it, if possible, or whether it's beyond fixing.
A few days ago my tablet was working fine and there was no indication of anything wrong. I put it on charge as the battery was getting low from watching YouTube. I came back to it a couple of hours later to find it stuck on the Samsung boot screen, but was able to get into Odin mode after some time (I tried to get into recovery but it wouldn't work). It had some trouble being recognised in the computer at first. I tried flashing the stock ROM again several times, but it failed each time with no useful error code.
I then tried rebooting which came up with a firmware upgrade error and asked me to recover it with Kies. I tried that to no avail. Firstly tried with Kies 3 which said the device wasn't compatible, even though I have plugged it into Kies before and it has been recognised and worked fine. I then tried the older Kies which wouldn't work either. Then, I opened Odin again and found it was being seen even with this error screen instead of Odin mode. I tried flashing again but still didn't work and had a COM port error instead. I did make sure that Kies was completely shut before attempting to flash. I even attempted to perform a proper Nand erase and repartition but that also didn't work and failed.
I couldn't do anymore after that due to it being so late at night, and had no choice but to let the battery drain. It now won't power on at all, nor does it appear to be charging, although there is something under a metal plate (not entirely sure what it is but possibly the memory or CPU chip), that gets warm when plugged in and slightly warmer when trying to power it on.
I did try a different computer, different cables and different operating systems to ensure none of those were contributing.
I have also tried to use ADB to get the device to be 'seen' but that didn't work either (used 'adb devices' command), but I'm new to ADB so don't understand it too well yet.
I appreciate any help given and hope I've given enough detail. Thank-you for your time,
Jed.
If all else fails try this
https://youtu.be/m2VJ_VRIRSI?t=201
Remove back cover and reattach the battery. Worked for me when my tablet wouldnt charge/turn on.
Maybe after this you can get it to be read by the computer.
wbb1 said:
If all else fails try this
https://youtu.be/m2VJ_VRIRSI?t=201
Remove back cover and reattach the battery. Worked for me when my tablet wouldnt charge/turn on.
Maybe after this you can get it to be read by the computer.
Click to expand...
Click to collapse
I tried this to no avail, with multiple chargers and leads. Thanks for the suggestion though.
I'm in the same boat myself and have not been able to get the tablet to power on at all.
Tried disconnecting the battery
Purchased a new charge/usb port
Any number of key combination tried for extended periods of time.
I think the tablet has officially eaten the dust.
I didn't even use it all that much. Only for ROMing and Readly.
Oh well...
CodeJACK said:
I'm in the same boat myself and have not been able to get the tablet to power on at all.
Tried disconnecting the battery
Purchased a new charge/usb port
Any number of key combination tried for extended periods of time.
I think the tablet has officially eaten the dust.
I didn't even use it all that much. Only for ROMing and Readly.
Oh well...
Click to expand...
Click to collapse
Yeah, I've lobbed everything I had for it, just gotta get a hammer and smash it up. It died with personal data on it and I'd rather not take any chances.