I have a T-Mobile Galaxy S (aka T959V). I upgraded to 2.3.5 via samfirmware.com and things were working pretty well, well, except that I was having a heckuva time rooting the phone w/2.3.5 so I could install CM 7.x.
I decided to revert to Froyo stock w/EZodin and while EZodin claimed that everything was fine during the installation, my phone has never exhibited signs of life after the RESET portion of EZodin: no blinking lights, no vibrations, just a black screen. No combination of:
- battery out, vol down, power, battery in
- battery out, vol up, power, battery in
- battery out, vol both, power, battery in
- battery out, vol both, battery in
- battery out, vol down, usb in, power, battery in
- etc ...
... causes any activity on the screen at all.
So I'm assuming that my bootloader is cooked in some way such that I can't even get to download mode. Before I resort to the jig method (or just return my phone to T-Mobile which is totally doable but not preferred if I can just kick it in the butt myself), are there further diags I can do to maybe get some activity out of this phone?
Yeah, try the rright forum.. this is for sgh-t959, you have the 4g, we do not... their very different
Sent from a cell tower to the XDA server to you.
Related
So I am now on hboot 1.40 s-off cdma Evo 3d... 2 weeks old, never dropped.
I have cwm touch recovery on my phone. Haven't had a problem with my phone since downgrading the hboot to 1.40.
Was running d3rp's rom and it was pretty amazing... decided to do the usual wipe(s) and flash Newt's RC2 of the Htc One S rom....
My battery wasn't charging and my 3D was bleeding battery life like a vag having it's time of the month, so I decided to wipe everything and flash a different rom. I booted into cwm, like usual, did the wipes and went to flash d3rps rom, kept saying error 1 and now damn thing won't power on and since everything was wiped It is ROM-less.
It's so weird, I can plug it & get a red light for about 2 seconds then it disappears. Never comes back on...nothing gets it to come on.
I have tried adb reboot bootloader, and the whole take the battery out, hold power for 10 seconds put the battery back in mess, but my computer and no computer recognizes the phone, so adb is out of the question.
-- I cannot boot into anything, it won't power on-- EXCEPT I CAN get the HTC screen (the bright one that blinds the sh*t of out of you!) but that's it. And it takes all kinds of work just to get to that screen.
Any suggestions? I'll try em all because there is no way the battery on this is dead if so I'd not get the HTC screen.
You cannot ruu it back to stock either because it has to be in fastboot mode in order to do that, I can't get into recovery so that's a fail as well.
Is there any way to use Odin or Heimdall to fix this; or anything else????
Odin and heimdall are for Samsung. You can try taking the battery out and holding power htton without the battery for a couple minutes. Then replace battery. Hold power both volumes and the camera button.
Sent from my SPH-D710 using Tapatalk 2
that does nothing.
quickfixguru said:
that does nothing.
Click to expand...
Click to collapse
Your problem comes from cwm touch, it does not support off mode charging.
Are the adb drivers installed correctly? Have you ever had adb working before?
If you can, try holding volume down and power while plugged in, choose fastboot USB.
Let it charge, boot into Rom, download 4ext touch recovery which does not have any bugs, phone will charge while off.
Google + pertinent info = results
Yep all my drivers are installed correctly, it won't do anything whatsoever except give me the htc boot screen and that's it. Nothing more and to get it to do that requires all sort's of maneuvers such as the battery being pulled holding down the button, ya know the usual stuff.
I am certainly not new to this whatsoever and I am very familiar with adb nothing seems to recognize my phone and I never had a problem of charging my phone in any time since i've had cwm touch on my phone.
Any other suggestions.......Annnnything at all I'll give it a shot.
Can you get into the bootloader by doing the following?
- Pull out the battery
- Put the battery back in
- Hold the volume down button
- Hold down the power button while still continuing to hold down the volume down button
From there you should go str8 to the bootloader screen rather than the splash screen.
If you get to the bootloader screen, are you able to get into the recovery from the bootloader menu?
If not, if you have access to another battery (like from a buddy's phone or somethin'), I would prolly see if that makes any difference in terms of being able to charge for more than 2 seconds, etc. Perhaps maybe even try a different charging cable as well. That way you can completely rule out faulty battery and/or charging cable.
Sent from my PG86100 using XDA
Well can you charge your battery in a different phone ?? Or via external charger?? Or if what I'm reading is true about cwm then I'd say pick up a spare battery or figure a way to charge your battery without it being in the phone. I mean it seems like your battery is just dead but your phone is ok. The few times you get a little power is from just letting the battey sit but its not enough to boot into anything. I'm just taking a shot here but that's what it seems like.
#Root-Hack_Mod*Always\
So my current phone stopped working so i was going to switch back to my galaxy s2 that has been sitting unused for about 3 months. When i tried to charged it the device will not turn on. The phone heats up when it sits on the charger for sometime. Also if i hook it up to my computer without the battery and hold the power and up/down button i can get to the warning screen about custom os to put it into downloading mode but when I press up to continue the screen just goes black and nothing happen if i press down to restart nothing happens it just goes black and i can hold the power and up/down to get back to the warning screen. The phone was rooted with iscrewd a long time ago before i when to a different phone. I have a usb jig but i cant even get to the warning screen with the battery in. Any thoughts??
You don't say, but I assume the phone was working normally when it was put on the shelf? If you can put your hands on a good I777 battery that is at least partially charged or better yet fully charged, put that in the phone and see if it will boot.
Sitting for three months will completely drain the battery, and this phone is somewhat sensitive to that. At least I have seen quite a number of reports of full discharge of the battery giving the same symptoms of not charging and getting warm.
I don't know what would account for you not being able to go beyond the warning screen with the battery out, especially if the phone was working normally before. The correct button configuration is the volume down button only, when the battery is out. I think the other buttons don't intefere though. Might try with just the vol - being held down and see what happens.
I vaguely remember someone having a problem similar to this, and I think he fixed it by getting the phone into download mode, putting the battery in, and leaving it in download mode to charge the battery. I think after a while he was able to boot the phone and let it finish charging while the phone was on.
This happened to me before. I just bought a new battery on Amazon and it worked just fine.
Sent from my Galaxy Nexus using xda premium
mvi57 said:
I vaguely remember someone having a problem similar to this, and I think he fixed it by getting the phone into download mode, putting the battery in, and leaving it in download mode to charge the battery. I think after a while he was able to boot the phone and let it finish charging while the phone was on.
Click to expand...
Click to collapse
battery does not charge in download mode. nor recovery.
Bought a new battery for it and it booted up like normal
Sent from my SGH-I777 using Tapatalk 2
Hi there,
I have an issue with my Samsung Galaxy S3; had it for a few years on O2 network in the UK. Recently, I left my phone to charge over night after the battery ran out of charge. I woke up to find no charge LED on the phone, and I couldn't turn it on.
I have tried the following things to power it up:
- booting it up in recovery mode (Home button, power button and Volume DOWN simultaneously).
- taking out the battery, pressing the power button a few times, then starting the phone up again with the battery in the phone.
- taking out the battery, pressing the power button and holding it for 10 seconds, and doing both normal power up, and recovery mode.
Now, a week later, after my phone completely died (and having to do with a Nokia Lumia 610 replacement), I came across a YouTube video in which someone recommends to plug it via USB into the computer, taking out SD Card and booting it up through recovery mode. Voila! I was amazed to see that it booted up; I had my menu and everything.
So I charged it to about 10% via the PC, and decharged it back down to zero. Plugged it back into the socket, and again, not a single sign of life from the phone.
To summarize, the phone only turns on via PC with USB connection, and fails to charge through the socket. I'm on Stock, non-rooted phone; with Android 4.3 and Kernel 3.0.31-2168382. When I try to do a software update, it tells me that I have the latest one. eMMC check app also tells me that I have an insane chip.
Where do I begin looking for a fix? I would be forever grateful for your help!
Hey guys,
I believe this is the correct section for this so here we go:
- The phone worked pretty well for quite a long time until it failed.
- It was never rooted and nothing was done on the OS or firmware besides the official updates
- Currently the phone can't start at all. Then you hold the power button it goes into a startup loop where it shows the initial logo, vibrates and then the screen turns black and repeats all of this until either the battery dies or you hold all three buttons.
- The phone charges its battery without any problems when it's off and simply plugged in the wall outlet.
- I can't boot into the recovery (vol down + power) as it goes in the same power-on loop. Same happens with any button combination.
- All of this happens regardless if the phone is plugged in the charger or not.
My questions are:
- Is there any point in opening the phone, getting the battery out for a hard reset and memory wipe?
- Can anything be done through a computer (plugging the phone and somehow tweaking in the firmware of the phone)?
- Can this be a hardware issue and if yes - what specifically?
I'd appreciate any and all suggestions and comments. If you need photos or any additional information I'd be more than happy to provide it.
Cheers!
PS: This is not my phone so I'm not entirely sure about how it was used (drops, water damage, etc.) but it as far as I'm told it hasn't suffered any damage and it does not have any traces of it (it's my mom's old phone).
So, after having two amazing Tab S (first one) and not being able to find a third, I ended up "upgrading" to a Tab S2. (Less screen resolution didn't seem like an upgrade..but hey)
After using it for about a year or so, I finally decided to get off my ass and root it. Had no problems after rooting it. Life was great. Maybe 6-7 months after rooting it, one day it booted up with an FRP lock; I didn't reset it at all so..odd..
Put the tablet aside as I didn't really have time to fix it. Few months later, I decide to pull it out wanting to use it for a project (I'm developing WebUSB FTDI drivers which also worth with Android OTG to allow a web page to access a USB device), I never replaced the original recovery, so my options were limited. I was hoping that perhaps flashing a new ROM that I might be able to keep my files versus just doing a reset in the recovery, which I'm not sure would have worked anyway (FRP) (I'm sure I've seen a device where this worked, IE, any user files were stored actually on a separate partition, thus you'd lose your apps and everything but downloads and such on the internal would be kept). I mean, I figured the chances were low but at least hire than the wipe option - not a huge deal anyway, important stuff is on the uSD.
So, I head over to Samsung's site and download the closest looking S2 rom, it's a SM-T713 (Canada, Gold/32GB/WiFi Only).. The ROM I ended up getting happened to have 4G support, so I didn't get a WiFi only ROM like I should have. Flashed it up with ODIN (AP), didn't change/flash the BL at all.
After flash, tablet booted up fine. It mentioned I would have to log in to google to authorize it (FRP lock) - no big deal, although I'm sure I didn't remote lock it. Do my login, finish the setup. Home screen. Tablet is running fine, nice and snappy.
Installed a few apps, it ran for a few days fine, then I decided I should probably flash it again with a WiFi only ROM, so I hold the power button and get the pop up to shutdown / restart, I press 'Power Off', tablet does it's shut down and powers off.
That's it. Now she's dead. Absolutely no sign of life since then. I tried to power it back on immediately as I had planned on going into DFU and plugging it in to upload another ROM. Nothing. No response. Battery was at 50% when I powered off. No battery symbol or anything when plugged in.
I should not that this was not the tablet's first boot since the flash either; it boot looped due to low battery after flashing a few times (damn samsung low battery boot loops) until I got the power supply plugged in, it was the first time that the "Power Off" option was selected, perhaps it hadn't been reset that way too; something on shutdown change something? I mean WTH?
I have tried:
- literally all key combinations for over a minute (PWR + VOL UP, PWR + VOL DWN, PWR + VOL UP + HOME, PWR + VOL DWN + HOME, PWR + HOME, PWR + VOL UP + VOL DWN, PWR + VOL UP + VOL DOWN + HOME) including while plugging it in, unplugging it
- different chargers, cables (bought brand new one), etc.
- left tablet for 2-3 days hoping it would die
- disassembled tablet, remove battery for few hours, replug battery
I have a USB power meter, when I plug in the tablet, it shows that it's pulling 0.57a constantly. I left it on overnight and it was no longer pulling current, just occasionally going from 0.00a to 0.07-0.10a. When plugged in without the battery, it also occasionally goes from 0.00a to 0.07-0.09a or so. Current usage profile is the same without the OLED plugged in. Something inside is at least slightly functioning.
No components that I notice are getting hot or anything obvious.
It was a gift, thus supposedly refurbished. The device looked great when I got it, no scratches or dings or anything, basically brand new looking so I assumed it had been a return, but upon disassembly, I found evidence that the tablet had been disassembled before, there was two-sided tape holding the screen on instead of any proper adhesive; was such a pain in the ass to take apart and not realizing that this was the case until I opened it only made it harder; regardless I doubt that any prior work could've caused this issue.
Does anyone have any schematics for this device or experienced something like this? I have meters, scope, logic analyzer, etc as I already do a bit of hardware reverse engineering and development.
The only thing I can think is somehow the boot loader got fried? Somehow the modem fw got flashed to boot loader? Is that even possible? I'm really reaching here as I'm really not sure, it's odd how it was working fine, had booted several times yet pressing 'Power Off' killed it when it was working fine. I would like to save this device from the graveyard as it's in great condition otherwise. It did sit for quite a while, so I was worried about the battery but plugging it in after sitting I immediately got the charge screen and it charged right up (even though it was still FRP locked at that point of course).
:crying::crying::crying::crying::crying:
le bump