um, hard brick? - Sprint Samsung Galaxy S III

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.

Related

Help

Screen is all black and keeps vibrating, unable to enter recovery
Odin
Sent from my Galaxy SII T-mobile using XDA
Suriyan72 said:
Screen is all black and keeps vibrating, unable to enter recovery
Click to expand...
Click to collapse
They say you can't help those people who doesnt want to be helped themselves.. you sound like one of those. You spent 20 seconds of your life writing this on the wrong forum.
How about more details on how it got to that state? What did you do?
Didn't do anything phone just rebooted and won't boot up and continues to vibrate
What was the last thing you were doing? We can't help you unless you tell us what you were doing.
Sent from my Galaxy SII T-mobile using XDA
rivas741 said:
Odin
Sent from my Galaxy SII T-mobile using XDA
Click to expand...
Click to collapse
unable to enter download manager or recovery
I second the others. DETAILS MAN. DETAILS. are you rooted? What rom are you on? Gb or ics? Do you have a stock kernel or a custom kernel?
sent from my t989. giggitygiggitygiggitygiggity!
DarthxTyler said:
What was the last thing you were doing? We can't help you unless you tell us what you were doing.
Sent from my Galaxy SII T-mobile using XDA
Click to expand...
Click to collapse
the last thing I did was play words with friends
(deleted by author)
rfail1988 said:
And just to be clear... Are you saying your phone wont boot, or just wont enter recovery mode?
sent from my t989. giggitygiggitygiggitygiggity!
Click to expand...
Click to collapse
rooted on darkside ucle beta 7 and it wont boot up or enter recovery. i take the battery out and put it in and the samsung logo shows up and then screen turns black and starts to vibrate
You might be hard bricked unfortunately :-/ someone posted here recently how to unsoftbrick yourself although i didnt read it. It might be your saving grace. Otherwise... See if odin can flash you back to stock. If that doesnt save you then pray that the T mobile gods have mercy on your soul...
sent from my t989. giggitygiggitygiggitygiggity!
Try going to T-Mobile. I'm sure the retail stores can't check if you're rooted if the phones doesn't boot. Maybe they'll exchange for refurbished.
Sent from my Galaxy SII T-mobile using XDA
rivas741 said:
Try going to T-Mobile. I'm sure the ratail stores can't check if you're rooted if the phones doesn't boot. Maybe they'll exchange for refurbished.
Sent from my Galaxy SII T-mobile using XDA
Click to expand...
Click to collapse
cant it shows the darkside boot animation for a little before it goes black and vibrates
Then you might be in luck... If you ge to thr boot animation then try flashing stock recovery then stock rom via odin. I have faith itll work...
sent from my t989. giggitygiggitygiggitygiggity!
rfail1988 said:
Then you might be in luck... If you ge to thr boot animation then try flashing stock recovery then stock rom via odin. I have faith itll work...
sent from my t989. giggitygiggitygiggitygiggity!
Click to expand...
Click to collapse
it wont go into recovery and odin recognizes the phone for about 5 seconds before it reboots and vibrates again.
What procedure are you using to get into download mode?
Odin will work you just have to get to download mode. Unless you really messed up something you should still be able to gert into download mode. The phone should not reboot once in download mode. Try pulling the battery then reinserting it but do not turn on the phone then plug the usb wire into the pc then hold both vol buttons and power and insert the usb right away hold until you see it enter download mode then follow the instuctions on the screen. You press vol up to continue into download mode or vol down to cancel and reboot.
Make sure its not completly dead. If it is then plug it up and dont touch it for about 10-15 minutes.. It will reboot and you should be fine
Sent from my SGH-T989 using XDA
mojorisin7178 said:
What procedure are you using to get into download mode?
Click to expand...
Click to collapse
pulling out the battery, plugging the usb in, then putting in the battery and holding the volume and power button down, its shows the download screen then reboots
Fly2Deaf said:
Make sure its not completly dead. If it is then plug it up and dont touch it for about 10-15 minutes.. It will reboot and you should be fine
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
my phone has been vibrating forever now, probably wont stop until the battery dies out
May sound dumb, but pull out battery and hold power button for 15 seconds? Lol
Sent from my Galaxy SII T-mobile using XDA

T-Mobile Galaxy S3 won't boot after Odin-HELP

So I just flashed the stock image through Odin (used the USB cable that came with the phone) and it boots past the boot animation(the T-Mobile 4g one) and then just hangs on "SAMSUNG" and it's still glowing and so is the notification LED but it won't boot, it just stays there. Can someone point me in the right direction to get this thing going? Is this a brick? I don't know what is wrong with it.
I believe It is hanging on the kernel (panic.... not you, the phone). Have you tried booting into recovery and wiping cache? (volume up + home button during hard reset)
Edit: Also what are you flashing from (i.e. CM, AOKP, TW custom ROM)?
if you were on a custom rom prior to reverting to stock, you need to do a wipe in recovery
Serious_Beans said:
So I just flashed the stock image through Odin (used the USB cable that came with the phone) and it boots past the boot animation(the T-Mobile 4g one) and then just hangs on "SAMSUNG" and it's still glowing and so is the notification LED but it won't boot, it just stays there. Can someone point me in the right direction to get this thing going? Is this a brick? I don't know what is wrong with it.
Click to expand...
Click to collapse
It took mine a very long time to boot after odin stock flash. But i dont think your screwed since it still powers on. Can you still get into download mode? Try to flash it again and see what happens.
Go into stock recovery and do a factory reset. Then reboot, that should do the trick.
Powered by the SGSIII
Reboot after ODIN
sswb27 said:
It took mine a very long time to boot after odin stock flash. But i dont think your screwed since it still powers on. Can you still get into download mode? Try to flash it again and see what happens.
Click to expand...
Click to collapse
OK, I am sure I am going to get blasted for putting this on the wrong thread but I have search!
Ran the boot program through ODIN on the Sprint version SPH-L710 and phone will not reboot now and cannot power on
toolkit says waiting for device
get the battery, Samsung and download screen briefly then it dies,
Afraid that I bricked it!
Any help would be appreciated!
rvshaw said:
OK, I am sure I am going to get blasted for putting this on the wrong thread but I have search!
Ran the boot program through ODIN on the Sprint version SPH-L710 and phone will not reboot now and cannot power on
toolkit says waiting for device
get the battery, Samsung and download screen briefly then it dies,
Afraid that I bricked it!
Any help would be appreciated!
Click to expand...
Click to collapse
Take out battery, unplug from computer, press and hold volume keys, plug in cable and insert battery again.
See if it goes into download mode.
Powered by the SGSIII
ThC23 said:
Take out battery, unplug from computer, press and hold volume keys, plug in cable and insert battery again.
See if it goes into download mode.
Powered by the SGSIII
Click to expand...
Click to collapse
red light does come on in the left
then battery symbol flash for a minute and nothing else
I ran into this exact same issue. I tried flashing kernal and everything after I did odin. What I had to do in order for my phone to boot was boot into recovery and do a factory reset. Keep in mind this was stock recovery so everything on your sd card will be gone after the wipe.
crash822 said:
I ran into this exact same issue. I tried flashing kernal and everything after I did odin. What I had to do in order for my phone to boot was boot into recovery and do a factory reset. Keep in mind this was stock recovery so everything on your sd card will be gone after the wipe.
Click to expand...
Click to collapse
Yes, wish I could boot into recovery but it will not even boot into recovery. Not sure if is a soft brick cannot load a screen regardless
Volume down + home screen + power button doesn't work for download mode? If you're screen is still powering on and showing the battery charging icon and samsung logo you haven't bricked your phone. I know on previous phones I have had that even though it showed nothing but a black screen odin still picked the phone up and was able to flash it.
crash822 said:
Volume down + home screen + power button doesn't work for download mode? If you're screen is still powering on and showing the battery charging icon and samsung logo you haven't bricked your phone. I know on previous phones I have had that even though it showed nothing but a black screen odin still picked the phone up and was able to flash it.
Click to expand...
Click to collapse
No, Volume down+home screen+power button only produces the Samsung or the Battery symbol for about a second, goes away and nothing else after that but a black screen, ODIN does not see the phone as it is not powered on, hope that makes sense
Factory reset worked perfectly. Too bad T-Mobile already shipped the replacement.
Sent from my SGH-T999 using Tapatalk 2
Johnny Blaze says ________?
I can't believe you called T-Mo for a replacement before performing a simple factory reset. Talk about a waste of money. As a future business owner this upsets me.
Eh lol oh well. Didn't think it would boot.
Sent from my SGH-T999 using Tapatalk 2
Serious_Beans said:
Eh lol oh well. Didn't think it would boot.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Well, if you're gonna play the system, might as well use your old phone to help us diagnose the imei lost problem and help the community. If you feel like helping us out, get ahold of lordmorphus or someone closely involved in this situation to have you run a few tests so we can figure this thing out. Ill be your bestest friend if you do
mrmako777 said:
Well, if you're gonna play the system, might as well use your old phone to help us diagnose the imei lost problem and help the community. If you feel like helping us out, get ahold of lordmorphus or someone closely involved in this situation to have you run a few tests so we can figure this thing out. Ill be your bestest friend if you do
Click to expand...
Click to collapse
Sure I'll pm him and see what we can do.
Sent from my SGH-T999 using Tapatalk 2
I pmed him. I'll see what we can do when he responds.
Sent from my SGH-T999 using Tapatalk 2
Serious_Beans said:
Eh lol oh well. Didn't think it would boot.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I can care less about exchanging the phone, but you did get a reply here of what to do.
What was the point of asking if you weren't gonna bother listening??
Powered by the SGSIII
Oh, Sh*t, I think I just bricked my phone - same thing happened. It now won't even allow me to boot. I took the battery out, unplugged the USB. Plugged the USB in and then put the battery back in. The LED light comes on for about 30 seconds and then goes off and stays OFF. I've tried POWER+UP/DOWN volume and HOME...still no avail.
The computer does recognize [the phone] when I plug it in by making a thumping sound and then it makes a few thumping sounds and then that's it.
PLEASE HELP!

S3 won't boot, load CWM, go into download mode...

Alright, so I have an i-747 (AT&T GS3) running AOKP Jellybean (8.28 build) with the KT747 kernel. I just tried to install Chainfire 3D using the automated installer, and when the phone rebooted, it stuck at the Samsung Galaxy S3 logo until I pulled battery. So I tried rebooting into CWM - same problem. And again with download mode. Even after pulling the battery for a good 5 minutes, nothing works. Am I bricked, or is there some fix for this?
If you can get into CWM your not bricked. If you haven't backed up your phone there is a good chance you will have to start fresh. Its always a wise decision to do a nandroid backup via cwm before doing anything major. Including installing chainfire.
Have you tried wipe/factory reset in CWM?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
g2tegg said:
If you can get into CWM your not bricked. If you haven't backed up your phone there is a good chance you will have to start fresh. Its always a wise decision to do a nandroid backup via cwm before doing anything major. Including installing chainfire.
Have you tried wipe/factory reset in CWM?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I made a nandroid just this afternoon, but I can't actually boot into CWM at all. As in, I turn on the phone (power+home+volume up), it gets to the Galaxy S3 logo and just hangs there. If I could get into CWM (or download mode) this would be about a 10 minute fix, but I'm kind of out of luck here.
Huh. After another battery pull, it let me boot into download mode. I'm gonna try to reflash to stock and hope for the best.
HELP I have the same issue
Hey, Im stuck in the same situation and was wondering if you were able to get it into CWM mode?
MrPhantom31 said:
Huh. After another battery pull, it let me boot into download mode. I'm gonna try to reflash to stock and hope for the best.
Click to expand...
Click to collapse
Hi, sorry to say but sounds like its bricked
Thanks
MrPhantom31 said:
Huh. After another battery pull, it let me boot into download mode. I'm gonna try to reflash to stock and hope for the best.
Click to expand...
Click to collapse
I doubt it's bricked if he got it into download mode. I'm sure he's flashed it and even got his wallpaper back up by now. Please let us know of you've managed to solve this or not MrPhantom.
Sent from my SGS3 i747m (Bell) on CM10 using TapaTalk2
delete post please
Curious?
I know its technically "Solved" but does anyone have any idea why this is happening? I have a Verizon GS3 and it's happening to me. I try to boot and it vibrates once and doesn't turn on. Recovery does the same thing. But going into Download mode works. Odin back to stock as we speak but I'm just curious what went wrong. I just did a clean install of a rom, set it all up (working at the time), set it down for the night and woke up to it like this.
rrrs444230 said:
Hey, Im stuck in the same situation and was wondering if you were able to get it into CWM mode?
Click to expand...
Click to collapse
Same thing happned to me but your not bricked. You can get into bolth download and boot mode easy
Here is how you do it.
RECOVERY MODE
Unplug the USB cable.
Shut down the phone.
Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
[edit]Download Mode
Save that somewhere. Make sure do it right. I got stuck also and thought I couldn't get into recovery but I had to do it right (it hit recovery mode first try) I have learned that most people do it slightly wrong. Make sure follow directions
Download mode
Unplug the USB cable.
Shut down the phone.
Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
To get out of Download Mode, simply press and hold the power button until the phone restarts
if helps hit thanks.
Just save that to a text file somewhere
I have also soft bricked when I deleted my rom once on accident. I dunno how I did it but I would get stuck at the TWRP screen. It wouldn't go to download or anything however when I plugged it into odin it saw it .... I even had a soft brick when screen went black from a bad boot animation and same thing.. and I had one bad soft brick where it took about 100 trys to get it into download mode (black screen) but odin detected it. I spent like 4 hours working on it.
I think
1. People don't follow directions correct (they do it a little wrong) which is enough if your phones messed up for it not to work.
when your phones normal it can get into recovery or download easy but when its sick you got to do it perfect.
2. I think something wrong with the phones (my s2 never had any issues in 2 years of owning it) S3 has tons of issues from usb, to bluetooth, to these soft bricks I have had)
3. Roms play a big part
4. I also think the way storage works in this new phone causes lots issues I dunno why just what I think
anyway Like I said now when I have a isssue I open text and read it and make sure I do it right and 95 percent of the time it was my fault I wasn't doing it right. K just my thoughts
when i try this on my verzion s3 it wont load back into the CWM after installed to finish rooting. it just goes back into the android system recovery. tried it about 10 times and nothing different
phatchef1 said:
when i try this on my verzion s3 it wont load back into the CWM after installed to finish rooting. it just goes back into the android system recovery. tried it about 10 times and nothing different
Click to expand...
Click to collapse
That's most likely cause you're not in the right section..: http://forum.xda-developers.com/forumdisplay.php?f=1708

Bricked?

Bell Galaxy S3 running stock JB rooted
I went to flash to Cyanogenmod 10.1 Nightly, it failed (Error status 7) so I attempted to reboot. Screen went black and stayed black, I left it for a few minutes, nothing happened then tried a battery pull. Now nothing. When I plug into my computer it makes the connect/disconnect chime but nothing else. If I hold down the power for ~10sec my laptop makes the disconnect chime, then when I release the power button it reconnects to my laptop (not sure if that helps any)
Just to further clarify, I cannot get to the download or recovery mod, screen is blank, no led when plugged in either.
Is it hard bricked?
I am looking at mobiletechvideos.com at their JTAG repair service. Is that my only/best option?
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
If all you did was try to flash cm10.1 then you are not bricked. You might not be doing the 3 button combo correctly to get back into recovery. Do this...
Pull Battery so power down device and then put it back in.
Hold volume Down, Home, then Power Button.
Release all of them when the 1st screen pops up. It's all about timing here.
That should take you back into recovery so you can just restore the nandroid backup you should've made prior to flashing anything.
No good, the screen is pure black no matter if I just try to power on, vol up + power + home, or vol down + power + home. Black screen.
Pull your battery, leave it out, and then plug it in.. no buttons or anything, it should turn on and see if it gets to the battery charging screen (which should show a lightning bolt only).
If it gets that far, power button and home button until you feel it vibrate, let go and it should boot.. post if it doesn't..
Don't press volume buttons, just home/power combo until it vibes..
Ok, so I did like you said, pulled battery and plugged the phone in to charge. I now get a solid red LED (this did not happen with the battery in), no lightning bolt though. The red LED turns off after about 2 minutes.
mooseknuckles1 said:
Ok, so I did like you said, pulled battery and plugged the phone in to charge. I now get a solid red LED (this did not happen with the battery in), no lightning bolt though. The red LED turns off after about 2 minutes.
Click to expand...
Click to collapse
Well, at least the power connector inside isn't busted.. that's a good thing..
with it plugged in, does it turn on like normal? Just regular "boot my phone" mode, no recovery or download?
Try while the LED is on, and if nothing, try it after it goes out.. as I'm not entirely sure what that could mean..
Wiltron said:
Well, at least the power connector inside isn't busted.. that's a good thing..
with it plugged in, does it turn on like normal? Just regular "boot my phone" mode, no recovery or download?
Try while the LED is on, and if nothing, try it after it goes out.. as I'm not entirely sure what that could mean..
Click to expand...
Click to collapse
doesnt turn on at all, still just black screen. I tried the home+power button when the LED goes out, no luck.
mooseknuckles1 said:
doesnt turn on at all, still just black screen. I tried the home+power button when the LED goes out, no luck.
Click to expand...
Click to collapse
Just the power button.. no volume/home buttons..
If all that was done was updating CWM on an already rooted phone, then only your recovery is borked, which is still repairable.. but if you were flashing something else, say CF-AutoRoot or a ROM, then I need to know..
Since you said Error=7, then I can assume you already had a working copy of CWM on it.. correct?
Ya I already had CWM on it. I was trying to flash Cyanogenmod 10.1 nightly (todays release) on to the phone. I had Cyanogen10 on it a while back then switched back to stock firmware. I was curious as to the new JB4.2 so I wanted to try out Cyanogenmod 10.1
Wiltron said:
Just the power button.. no volume/home buttons..
If all that was done was updating CWM on an already rooted phone, then only your recovery is borked, which is still repairable.. but if you were flashing something else, say CF-AutoRoot or a ROM, then I need to know..
Since you said Error=7, then I can assume you already had a working copy of CWM on it.. correct?
Click to expand...
Click to collapse
the OP said in 1st post that he was flashing a rom. never mentioned cwm. the only way to have flashed a rom in the first place and gotten a status 7 would have been in a custom recovery.
reserved
Any chance you flashed an international ROM?
upndwn4par said:
Any chance you flashed an international ROM?
Click to expand...
Click to collapse
exactly.
but what all is actually accomplished before an error message?
xBeerdroiDx said:
exactly.
but what all is actually accomplished before an error message?
Click to expand...
Click to collapse
I still have a copy of the zip file on my computer, exact file name is cm-10.1-20130422-NIGHTLY-d2att.zip i cross checked with the Cyanogenmod site it says it is the proper ROM .zip to use
xBeerdroiDx said:
exactly.
but what all is actually accomplished before an error message?
Click to expand...
Click to collapse
I am not familiar with the partitions on that device, so I can't say for sure. But all it takes is one file installed in the wrong place and you'd be in trouble. And if that file gets installed in the recovery partition....
Edit:
mooseknuckles1 said:
I still have a copy of the zip file, exact file name is cm-10.1-20130422-NIGHTLY-d2att.zip i cross checked with the Cyanogenmod site it says it is the proper ROM .zip to use
Click to expand...
Click to collapse
Yup, that's the right one.
Could be the SGS3 sudden death???
upndwn4par said:
I am not familiar with the partitions on that device, so I can't say for sure. But all it takes is one file installed in the wrong place and you'd be in trouble. And if that file gets installed in the recovery partition....
Click to expand...
Click to collapse
i hear ya.
i thought thats why the script was set to check the recovery partition to ensure it was a compatible (up-to-date) platform to install from. i dont understand why it would begin installing and then check. but then, i'm no recovery coder
What about forcing download mode ? I.e. volume down+home and no battery and then plugging in the usb cord. Then put in battery after its in download mode ?
(IIRC)
Sent from my SAMSUNG-SGH-I747 using xda premium
hednik said:
What about forcing download mode ? I.e. volume down+home and no battery and then plugging in the usb cord. Then put in battery after its in download mode ?
(IIRC)
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Nope, nothing.
I want to thank everyone for the help and input so far!
There is no one in town here than can unbrick a hard bricked phone, but Toronto is only a 50min drive and there are a few places that will do it (~$70), or I can order one of those jigs online that plug into the microUSB port for about $60. It's looking like I will be going one of those routes.
mooseknuckles1 said:
Nope, nothing.
I want to thank everyone for the help and input so far!
There is no one in town here than can unbrick a hard bricked phone, but Toronto is only a 50min drive and there are a few places that will do it (~$70), or I can order one of those jigs online that plug into the microUSB port for about $60. It's looking like I will be going one of those routes.
Click to expand...
Click to collapse
um, usb jigs are about $3 on eBay.
i'm assuming you mean send it in for jtag?
xBeerdroiDx said:
um, usb jigs are about $3 on eBay.
i'm assuming you mean send it in for jtag?
Click to expand...
Click to collapse
Jig can work for the gs3. They are cheap no matter what. I used them on my cappy.
Sent from my SAMSUNG-SGH-I747 using xda premium

[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

Categories

Resources