Develop Bugs

My sasmung w Wont Turn On

I have a Samsung W which is not rooted, with Stock Rom as i bought it. Everything was ok until yesterday. I put it in my pocket and the phone was Suddenly turned off. Since then the phone won't turn on except that the screen sometimes flashes when pushing numerous times the power button.
When i press the Vol+ + Center Button + Power Button to enter Recovery mode nothing happens.
I will charge it overnight to see if something changes tomorrow.
Need Help please!
Finally Turned it on, But Samsung Kies and ODIN seem not to working at all. Samsung Kies stacks at "Connectind" & ODIN detecs the phone successfully, but when the phone restarts it won't turn on, i have to remove battery and Open it in Download mode again.

Try to enter download mode press vol down + home+ power button if you can enter download mode flash it with odin
Sent from my GT-S5570 using xda app-developers app

maybe the power button has the problem.

I disassembled the phone and the power button is working fine. I can't enter Dwonload Mode. the phone won't turn on at all :/

Since it is not flashed / rooted & with stock rom, just sent in to a service center, it's the safest thing to do right now i think.
After that you can do with it what you want

Hello! I cant sent it to a service center as it has a big mark on the top of it and they will ask me to pay in order to fix it. I finally Managed to Turn it on in DOWNLOAD MODE. I tried http://forum.xda-developers.com/showthread.php?t=1467128 this thread with ODIN and Samsung KIES. Samsung KIES stacks at "Connecting". ODIN detects the phone, downloads data , but when the phone restarts is dead. I have to remove battery and turn it on in Downloading Mode

Snake_A said:
Hello! I cant sent it to a service center as it has a big mark on the top of it and they will ask me to pay in order to fix it. I finally Managed to Turn it on in DOWNLOAD MODE. I tried http://forum.xda-developers.com/showthread.php?t=1467128 this thread with ODIN and Samsung KIES. Samsung KIES stacks at "Connecting". ODIN detects the phone, downloads data , but when the phone restarts is dead. I have to remove battery and turn it on in Downloading Mode
Click to expand...
Click to collapse
What 'big mark' making it cannot be sent back to Samsung lol? Maybe you should install CWM and do a full wipe first before you flashed the ROM with Odin (anyway sending it back to Samsung will still be the best solution as you may accidentally void the warranty when you are trying to fix it)

Well, i believe for ODIN to work first u have to kill Kies Process using the Task manager or you will get some conflict between the two.
Also, if your phone has a scratch on top of it, then your fine. However, if it has a big DENT or if it is broken somewhere, then they will probably assume it was a problem due to a fall or something. However you can always try and send it to the service center and they will probably sort it out or replace your phone as a last resort (even if it has a scratch on it xD).
Hugs

turning on galaxy w
I'm having the same problem here with my galaxy w.. I cant turn it on at all too

Snake_A said:
I have a Samsung W which is not rooted, with Stock Rom as i bought it. Everything was ok until yesterday. I put it in my pocket and the phone was Suddenly turned off. Since then the phone won't turn on except that the screen sometimes flashes when pushing numerous times the power button.
When i press the Vol+ + Center Button + Power Button to enter Recovery mode nothing happens.
I will charge it overnight to see if something changes tomorrow.
Need Help please!
Finally Turned it on, But Samsung Kies and ODIN seem not to working at all. Samsung Kies stacks at "Connectind" & ODIN detecs the phone successfully, but when the phone restarts it won't turn on, i have to remove battery and Open it in Download mode again.
Click to expand...
Click to collapse
What did you do to get your Galaxy W started?

Brick? Faulty power button? (Phone wont stay in download mode)

Hello guys, so today I decided to update my i747 ATT S3 to the latest Task650 Rom, I did as always with the exception that this time I needed to flash a file trough PDA in odin since there was a baseband update back in may. Everything was successful at this point, phone rebooted and went in to the current version of the Task650 ROM i had installed, everything worked great with the exception of my power button that once pressed instead of locking the phone would completely turn it off/trigget the power panel (shutdown,reboot...) so I booted again and powered it off. Tried to get into recovery to flash the latest build of the Task650 ROM without luck, the phone just powers off once trying to boot into recovery, tried the same thing with download mode. At first it went in and stayed in download mode successfully but then I tried to go into recovery again and the same story, went back into download mode and this time it would shut down after 3 or so seconds, sometimes lasts more but no matter what I do it shuts down and the battery has to be pulled in order for it to go into either mode.
At this point to me it looks like a sticked power button but I could be wrong. Any suggestions in order to attend this issue?
[Update] So apparently it really is my power button, wiggled with it for a bit and managed to make the phone boot into the ROM successfully...
Any suggestions on how to permanently fix this issue?
Oscar

Hey man,
If you were able to "wiggle" the power button to work then its definitely the power button. If you have had the phone for a year or less I'd Odin back to stock/ flash counter fix the device and return it to at&t. Back in my captivate days that was a sure sign that the power button was about to malfunction completely. If you are unable to take in for warranty then I'd suggest using the XDA search feature to find the "home remedy power button fixes" or maybe just googling fixes. Mobile tech videos does good work but I won't link to his website because I'm pretty sure its against XDA rules. Or, for even more fun; you could fix it yourself.
Anyways,
Goodluck.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

SOLVED, got phone back from repair shop where power button was successfully replaced

wceoscar said:
SOLVED, got phone back from repair shop where power button was successfully replaced
Click to expand...
Click to collapse
Good to hear man
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

um, hard brick?

I was running the 08/20 nightly of CM10.2 and I was typing a SMS in the CM 10.2 default app, then the screen went black. I left it there for sometime (~25 min) then tried to turn the screen on before doing a battery pull, didn't work, so I pulled the battery and then rebooted but it goes to the samsung screen then goes black. I can't boot a ROM, I can't go into recovery, and I can't go into download mode. Hard bricked? What are my choices.
EDIT: the battery is charged because I was able to boot my step dad's VZW sIII using my battery.

Sounds like a hard brick. I think a USB jig might work.
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!

Whiplashh said:
Sounds like a hard brick. I think a USB jig might work.
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
Click to expand...
Click to collapse
Do you mean "USB jig" or JTAG? To my understanding USB jigs only worked on the sII, but that's just my understanding, which could be wrong.

Did you try this method?-click here

@jamcar If your phone turns on and you get Samsung screen it is NOT BRICKED.
A bricked device does not even turn on.
Hook your phone up to a computer and use odin to flash it back to stock. Or if you can boot into recovery just wipe cache, Dalvik and do factory reset and reflash the rom you are on.
Sent from the future via Tapatalk 4

edfunkycold said:
@jamcar If your phone turns on and you get Samsung screen it is NOT BRICKED.
A bricked device does not even turn on.
Hook your phone up to a computer and use odin to flash it back to stock. Or if you can boot into recovery just wipe cache, Dalvik and do factory reset and reflash the rom you are on.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
I can't get past the first screen that says: SAMSUNG. I can't get into recovery, I can't get into download mode (which means I can't flash a new ROM and can't use ODIN), and can't boot my ROM.

jamcar said:
Do you mean "USB jig" or JTAG? To my understanding USB jigs only worked on the sII, but that's just my understanding, which could be wrong.
Click to expand...
Click to collapse
I thought I saw some people
using them on the s3 to get into Download mode. I heard some had worked.
edfunkycold said:
@jamcar If your phone turns on and you get Samsung screen it is NOT BRICKED.
A bricked device does not even turn on.
Hook your phone up to a computer and use odin to flash it back to stock. Or if you can boot into recovery just wipe cache, Dalvik and do factory reset and reflash the rom you are on.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
He said he couldn't get into recovery. Sounds like somehow his system and recovery got corrupted.
Edit: ALTHOUGH he did say hook it up to a computer then try booting it up!
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!

Ed is right, I done this for a friend who recently thought he bricked his phone.

joeyhdownsouth said:
Did you try this method?-click here
Click to expand...
Click to collapse
I have not, I'll start working on that now.
@joeyhdownsouth so far it is a no go.
But I also don't have a class 10 SD card, so I'll try again when I can get one, hopefully tomorrow. Anyone know why this happened?

jamcar said:
I have not, I'll start working on that now.
@joeyhdownsouth so far it is a no go.
But I also don't have a class 10 SD card, so I'll try again when I can get one, hopefully tomorrow. Anyone know why this happened?
Click to expand...
Click to collapse
I've had plenty of Samsung phones in some pretty bad states (including several hard bricks). Some very similar to your current situation. This includes the s2, s3, note 2, stellar and that's just naming a few. I've never had a phone that booted in any way shape or form and couldn't reach download mode. So if you're situation is as you describe then I'm pretty sure it's a first. Unless it's some sort of corruption (similar to the emmc brickbug that plauged the s2). Maybe even a less severe case of SDS. Just throwing some ideas out there but I bet this ends in needing a warranty repair from Samsung.

@jamcar How are you trying to boot into recovery the 3 finger method? Again I stand solidly on if the phone powers on and you see Samsung it's not bricked. You have other things going on but going through deBricker method is not the answer.
If your phone is powering on and you see Samsung logo then it goes black like it shut off you could be also experiencing the 'sudden death syndrome' which is a power button failure.
Try blowing some compressed air and paying with the power button. It is a known defect on the S3 and Sprint does replace the phone for this issue.
Sent from the future via Tapatalk 4

edfunkycold said:
@jamcar How are you trying to boot into recovery the 3 finger method? Again I stand solidly on if the phone powers on and you see Samsung it's not bricked. You have other things going on but going through deBricker method is not the answer.
If your phone is powering on and you see Samsung logo then it goes black like it shut off you could be also experiencing the 'sudden death syndrome' which is a power button failure.
Try blowing some compressed air and paying with the power button. It is a known defect on the S3 and Sprint does replace the phone for this issue.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
I'm trying to boot into recovery by holding down power+vol up+home then in the corner I see "RECOVERY BOOTING..." then the screen goes black and nothing else happens. I try to go into download mode by holding power+vol down+home, I then get the custom OS warning sign, then if I push vol up the screen goes black, if I push vol down the screen goes black. This is with and without deBricker's SD card mod. (It has no affect).
EDIT: I have been looking into SDS for the sIII and most, if not all, threads are for the international sIII and most people say they fixed it by going through Samsung.
EDIT: if they [Samsung] some how get it into download mode, are they going to care that it looks modified? Custom download count (around 5), modified system status, etc.

If it works at all its not a hard brick. A hard brick needs a JTAG to recovery. Put it in Odin mode and flash from there
Sent from my SPH-L710 using xda app-developers app

IDontKnowMang said:
If it works at all its not a hard brick. A hard brick needs a JTAG to recovery. Put it in Odin mode and flash from there
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
ODIN mode is really called download mode, and if you read the post above yours and the OP then you'll see I can't get into download mode only the Custom OS Warning screen, which isn't download mode

You can't continue from the custom OS warning screen? That leads you to download mode doesn't it?

metalfan78 said:
You can't continue from the custom OS warning screen? That leads you to download mode doesn't it?
Click to expand...
Click to collapse
Usually but no matter what button I hit (vol up to continue into download mode---vol down to reboot) I just get a black screen. Every once in awhile (it has happened twice and I've tried many many times [~50+]) the Green android comes and it say "downloading..." but then the screen goes black and it is never seen by my computer / ODIN.
EDIT: the android comes up a for a spit second

Correct that's because his device is shutting down. The power button is bad. SDS... I sent you a reply to your PM. Worth a shot.
Sent from the future via Tapatalk 4

Okay I'll try Sprint then Samsung.

That explains why. You should definitely follow edfunkycold's suggestions.

edfunkycold said:
Correct that's because his device is shutting down. The power button is bad. SDS... I sent you a reply to your PM. Worth a shot.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
You say it is the power button other people say it is the eMMC. Which is it? I'm only trying to understand this SDS problem better.

[Q] My Phone Won't Boot Into Any Mode

So, my Galaxy S3 suddenly shut off on me, so I tried to reboot it, and it would just say "Galaxy s3" then nothing would show. So I figured it was a software brick and I can just restore a backup. When I tried to access Recovery Mode, it would show that its trying to boot into Recovery, but nothing would happen. So I figured I can just go into Download Mode and restore it through ODIN to get all the partitions working again. It would go to Download Mode for a few seconds, and then just shut off on me before I can even do anything. Everytime I take out the battery and put it back in, it tries to auto boot, but it never gets passed the Samsung s3 logo. Do you think this is a software or hardware brick? And would any of you know how I should go about fixing this?
Thanks a bunch

neim81094 said:
So, my Galaxy S3 suddenly shut off on me, so I tried to reboot it, and it would just say "Galaxy s3" then nothing would show. So I figured it was a software brick and I can just restore a backup. When I tried to access Recovery Mode, it would show that its trying to boot into Recovery, but nothing would happen. So I figured I can just go into Download Mode and restore it through ODIN to get all the partitions working again. It would go to Download Mode for a few seconds, and then just shut off on me before I can even do anything. Everytime I take out the battery and put it back in, it tries to auto boot, but it never gets passed the Samsung s3 logo. Do you think this is a software or hardware brick? And would any of you know how I should go about fixing this?
Thanks a bunch
Click to expand...
Click to collapse
i think the problem is on power button...
if the power button press contiues will be like that
i meet the same case like u...
sory my englis
press thanks if i help...

I agree, the only way it should turn on when you replace the battery is if power was held down. It would explain everything else you mentioned as well. Try gently knocking it back out. Or if comfortable with it, open the device to have a closer kook.
Sent from my SCH-I535 using Tapatalk 4

DocHoliday77 said:
I agree, the only way it should turn on when you replace the battery is if power was held down. It would explain everything else you mentioned as well. Try gently knocking it back out. Or if comfortable with it, open the device to have a closer kook.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
It just turned on, I guess it was the power button.
Sent from my SGH-T999 using xda app-developers app

i'm experiencing a similar issue. I can only get any result while it's plugged in. it wont boot past the second splash screen, I got it into download mode and flashed the stock package from sammobile.com with no change. the phone keeps trying to boot into recovery after flashing stock but it goes to the android with the open chest screen and reboots and tries again over and over. i've taken the phone apart and seen nothing wrong, no corrosion, no water damage and i've even replaced the battery with no success. i tried flashing clockworkmod recovery, the flash was successful but it still wont even boot to recovery. the power button isnt stuck, i can manipulate it when i have the bare motherboard in my hands and still it's fine. would replacing the power switch have any affect? please any thoughts would be appreciated
edit: since flashing stock, plugging the phone into the computer with oem cable causes it to vibrate intermittently. holding power causes it to try recovery mode. running windows 7 with samsung drivers properly installed and adb recognizes my galaxy s2 and captivate no problems. someone mentioned on a post i read about using a 3 part stock rom, modem, pda and phone to flash instead of the all in one tar file, any thoughts?
another edit. this phone has never to my knowledge been rooted or had any kernel/rom flashed onto it. as far as i know it's stock from Wind mobile, 3 months past warranty

[Q] Stuck on samsung logo

Guys, i need help regarding my galaxy w
1.stuck with a samsung logo, it cannot boot, just stuck there as soon
I insert the battery, just flashing samsung logo on and off.
What should i do?
Need tutorial.
Thanks...

sanny77 said:
Guys, i need help regarding my galaxy w
1.stuck with a samsung logo, it cannot boot, just stuck there as soon
I insert the battery, just flashing samsung logo on and off.
What should i do?
Need tutorial.
Thanks...
Click to expand...
Click to collapse
More details please
Your recovery..............
Current rom............
What happened before the loop....................
In order to help you

the phone is 100% stock
never flash before..

1) can the phone get into recovery?
2) can the phone get into download mode?
3) what are you seeing?......the phone gets to the Samsung screen, then seems to restart and repeat?
Sent from my GT-I9100 using xda app-developers app

sanny77 said:
the phone is 100% stock
never flash before..
Click to expand...
Click to collapse
Never flashed anything before? No custom recovery (such as CWM recovery), no kernels, no root, no ROMs, no apps requiring root access to modify system files and no mods? Looks pretty unlikely to me considering the behaviour you're describing. Anyway, if you didn't do any of the things above, could you try another battery in?
Sent from my GT-I9195 using Tapatalk

Try wipe data /factory reset
I have same problem when I was upgrade my SGW into stockrom 2.3.6
when i finished upgrading with odin, the phone is boot loop at samsung logo, restart and back again.
so I turn off the phone, wait until it really off, then I push together = home+volume up+power button.
when the phone is turn on, release the power button only. and then release all button.
it will entering the stock recovery mode, if theres only show the android logo, just press the menu button, and it will show the option.
choose the wipe data/factory reset. and then reboot.
I solve the problem by doing that. Maybe it will help you. thanks.