[Q] Phone stuck on Booting - Vibrant Q&A, Help & Troubleshooting

Hi
My phone is stuck on splash screen and have tried hard reset but phone does not turn;s on.
Phone doesn't connects to KIES even on boot screen??
Can anyone help me ??? Its URGENT

Pretty sure your phone is supported by kies mini, not kies.
You cannot perform a software recovery or update with kies mini. You could try flashing the stock ROM back onto the device or send it in to Samsung for a free software reflash.
If you send it in to Samsung it will take about 2 weeks.
Your carrier may be able to perform a software reflash as well.
Just curious...has your phone ever suffered liquid damage? It can cause damage to components on the PBA that would prevent it from booting up.
Hope this helps! Feel free to pm me if you have any questions
Sent from CM 10.2 optimized sph-l710

Nope.. it was not dropped in any liquid nor its pba is damaged... i think its hard bricked now ...

rahulrustagi said:
Nope.. it was not dropped in any liquid nor its pba is damaged... i think its hard bricked now ...
Click to expand...
Click to collapse
If you were using kies when this happened then your phone is basically a paper weight unfortunately. Kies is notorious for hard bricking phones so for future reference, stay away from kies. Best way to upgrade is flashing custom ROMS through cwm recovery mode. Try and flash back to stock with Odin, I have heard of people being able to get Odin to see the phone even if your not in download mode. If that doesn't work then maybe try buying a USB jig to get into download mode. If that doesn't work either then try calling Samsung and tell them kies bricked your phone, they have replaced out of warranty phones before due to kies bricking them.
Sent from my SGH-T959 using Tapatalk 2

it got hard bricked using odin only... kies was not running that time...i flashed stock ginger bread rom over stock froyo and using 512 pit file... and it displyed failed on ODIN..and then when i removed the phone battery first and then USB unplugged.... pushed back battery again..pressed both volume button...booommm no screen till then...i really dont know what to do now...

Samsung will not replace a phone bricked by kies, not sure who told you that.
Samsung's warranty doesn't cover replacements only repairs.
If your phone was bricked by kies they'll be able to fix it though.
A reflash would solve your problem if you can't get it to flash in Odin.
Their system doesn't require you to be able to get into download mode.
Hope you're able to get it working if not send that biatch in
Reflash is free in or out of warranty
Sent from CM 10.2 optimized sph-l710

ShadowCodes said:
Samsung will not replace a phone bricked by kies, not sure who told you that.
Samsung's warranty doesn't cover replacements only repairs.
If your phone was bricked by kies they'll be able to fix it though.
A reflash would solve your problem if you can't get it to flash in Odin.
Their system doesn't require you to be able to get into download mode.
Hope you're able to get it working if not send that biatch in
Reflash is free in or out of warranty
Sent from CM 10.2 optimized sph-l710
Click to expand...
Click to collapse
Search the forum, multiple people have reported getting their phone fixed for free because kies bricked it. I wouldn't say it if it wasn't true....
Sent from my SGH-T959 using Tapatalk 2

iTz KeeFy said:
Search the forum, multiple people have reported getting their phone fixed for free because kies bricked it. I wouldn't say it if it wasn't true....
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
yes i was a victim too but thanks to noob guide then...i used it many times as i was used to bricking... :good:so you can follow this then let know what happened. follow every step there... http://forum.xda-developers.com/showthread.php?t=848737

iTz KeeFy said:
Search the forum, multiple people have reported getting their phone fixed for free because kies bricked it. I wouldn't say it if it wasn't true....
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
Fixed yes but not replaced
I work for Samsung, and I wasn't trying to be rude, I was just informing you of our standard policies.
To the OP,
I hope some of the guides to unbricking on here will help you as they have helped many others.
I myself have had some bricked devices up and running using these forums without having to send it in
Sent from CM 10.2 optimized sph-l710

Related

The impossible? I think I just did it...

I think I might have permanently bricked a vibrant lol...ok well maybe I shouldn't be laughing. I have a vibrant that does not turn on, I don't get any images, but when im charging the phone still gets warm.
So here's what happen, I been telling my friend to root his phone and out custom rims on there...he finally gave in after being frustrated by the lack of support Tmobile and Samsung was giving and tried to root and flash himself. During the flash in odin something went wrong and I had to flash it back to stock. I rooted the phone with oneclick root. Installed rom manager and flashed clcokwork recovery. I rebooted into clockwork, reinstalled packages, cleared/wipe cache/data, and flashed team whiskey's bionix-v (awesome rom by the way!!) It flashed and rebooted....bit never turned back on. I don't even get to the boot images....just blackness.
I did some research to no avail....if anyone has any suggestions or anything, it would be greatly appreciated!!
I already tried the 3 button to try to get it into recovery, battery pull with the 3button fix....with usb plugged and unplugged...but odin still fails to recognize it.
My last resort is the jig to try to get it to at least download/recovery mode. =(
Sent from my SGH-T959 using XDA App
Doesn't really sound like anything you did would brick the phone - even though the screen doesnt come on, does your computer recognize it when you plug it in?
Yeah I agree. Nothing in those course of events would point to bricking your phone.
I am so sorry for your loss.
btw did you try pulling the battery for a few minutes then trying to power it on?
The phone is bricked. Same thing haopened to me flashing the same rom. I wasnt the first and you wont be the last.
I really wish we could figure out why this is happening.
Sent from my SGH-T959 using XDA App
the PBL on the phone crashed. Most likely the bad ODIN flash caused the PBL to become corrupt. When it received the new SBL for froyo, it crapped on itself.
This is where people begin to blame the roms for bricking. When in fact, it is not the roms at all. It's ODIN corrupting the Primary Bootloader when ODIN freezes or crashes.
But other than that, your hosed. Just contact TMO for a warranty replacement.
They will tell you that you need to perform a master reset using the hardware keys...dumb asses.
then have you check the water damage square under the battery.
Then will send you off a replacement.
tooclose said:
I think I might have permanently bricked a vibrant lol...ok well maybe I shouldn't be laughing. I have a vibrant that does not turn on, I don't get any images, but when im charging the phone still gets warm.
So here's what happen, I been telling my friend to root his phone and out custom rims on there...he finally gave in after being frustrated by the lack of support Tmobile and Samsung was giving and tried to root and flash himself. During the flash in odin something went wrong and I had to flash it back to stock. I rooted the phone with oneclick root. Installed rom manager and flashed clcokwork recovery. I rebooted into clockwork, reinstalled packages, cleared/wipe cache/data, and flashed team whiskey's bionix-v (awesome rom by the way!!) It flashed and rebooted....bit never turned back on. I don't even get to the boot images....just blackness.
I did some research to no avail....if anyone has any suggestions or anything, it would be greatly appreciated!!
I already tried the 3 button to try to get it into recovery, battery pull with the 3button fix....with usb plugged and unplugged...but odin still fails to recognize it.
My last resort is the jig to try to get it to at least download/recovery mode. =(
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
so you bricked your friends phone, not your own?? thats messed up... why did you wipe data before you flashed the rom?? lol is that a regulation? i never wipe my stuff until after i let the rom run for more than 10 mins. unless im told different.. besides i thought all of tw roms wipe so you didnt need to. lol correct me if im wrong
@jellette no my computer doesn't recognize it....I have a windows 7 pc...and the latest odin
@hazard99 yes I've tried several battery pulls with different options with 3button....no luck =(
@alkaloid i've flashed, rooted alot of phones going back to my pearl, sidekick, bb pearl, htc hd2, my own vibrant....maybe cuz they were all my phones and I took the time to be careful...haha
@kooksta yeah I know I feel bad...im letting him hold my hd2 til I can get a fix or just have it replaced...I usually do a backup and wipe before every flash never had a problem and I thought that was standard but not sure...
@krylon I was thinking the same thing ...when he tried to update it on odin with the froyo update it corrupting something...the devs on here do a great job!! Never before have ever had any problems!
Thinking back to it, the only thing I can think of is after I installed rom manager and flashed clockwork recovery and I booted into clockwork...I think the lettering was still blue? I think its my understanding that if its still blue the phone is not rooted, green lettering means rooted, and red means rooted with voodoo activated...correct me if i'm wrong. But I THINK the lettering was blue, but the phone has to be rooted to run rom manager right?
Lazy to make so bought the jig from ebay, should get it in a few days to test ...
If anyone else has similiar experiences and/or fix....would love to hear them!
Sent from my SGH-T959 using XDA App
Like you said, the Rom would've done it for him regardless. It wasn't his fault he bricked his friends phone. Hopefully he told his friend the possible repercussions of modding his device however. Like Krylon said, its just a corruption caused by odin. Nothing he could've done differently to prevent it besides not modding the phone itself. Oh well, happens. Like Kyrlon said, warrenty replace it. Simple and done.
tooclose said:
Lazy to make so bought the jig from ebay, should get it in a few days to test ...
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
@tooclose
off topic, i need a new jig (another one), can you send me the link in ebay where you bought that?
or anyone?
krylon360 said:
the PBL on the phone crashed. Most likely the bad ODIN flash caused the PBL to become corrupt. When it received the new SBL for froyo, it crapped on itself.
This is where people begin to blame the roms for bricking. When in fact, it is not the roms at all. It's ODIN corrupting the Primary Bootloader when ODIN freezes or crashes.
But other than that, your hosed. Just contact TMO for a warranty replacement.
They will tell you that you need to perform a master reset using the hardware keys...dumb asses.
then have you check the water damage square under the battery.
Then will send you off a replacement.
Click to expand...
Click to collapse
Wait, so if I was running Bionix V and wanted to flash a new rom, what would be the proper procedure? All these crashes from Odin is starting to scare me
I forget who the seller was but just do a search for vibrant jigs ...there's several sellers...good luck!
Just got the jig...its a no go =(
Sent from my SGH-T959 using XDA App
yes , i fix my phone fron the point where you are now without no jib anyway since u got solutin comin in mail i wont explain since it took me and hour to figure how to get my phone to odin .yes from blank screen to phone warm when chargin i got it to work =}
Speaking of the PBL, how can I verify that mine is not corrupt? I flashed bionix V twice and assume the SBL is intact, but I still would like to verify that both are working correctly.
bartek25 said:
yes , i fix my phone fron the point where you are now without no jib anyway since u got solutin comin in mail i wont explain since it took me and hour to figure how to get my phone to odin .yes from blank screen to phone warm when chargin i got it to work =}
Click to expand...
Click to collapse
I think you should explain it just in case it happens to others later on or make a seperate post on how to please
Moved of: Samsung Vibrant > Vibrant General
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
method of unbricking
bartek25: Would love to know your magic to bring the dead phone back to life. Mine is completely dead acting like the battery is dead even though it is fully charged and I've read and tried ever method I can find.
Any suggestions other than sending it in Samsung or the carrier in getting a hard bricked phone fixed? Anyone with a jtag interface who likes to make a few extra bucks on the side?
I'm a noob to all of this custom rom business but earlier today I installed Bionix, everything went great and was a lot easier to do than I had anticipated.
Anyways I'm just wondering, I did not have to use ODIN, really all I did was root, install rom manager, cwr, create nandroid and titanium backups, transfer bionix zip to internal dir and then bootup in cwr.
I guess my question is, why was ODIN necessary for the topic poster?

Vibrant Bricked.

I got my vibrant bricked yesterday while i was returning to stock rom and then upgrading it to Froyo through samsung kies mini. I tried all types of combinations of keys and ended up it failure. I cant get the mobile into download mode. Many say that with the help of USB jig i can unbrick it easily and get the download mode back.
I would like to know few opinion regarding this.
Have you read the thread below this one? Is your problem similar?
Sent from my SGH-T959 using XDA
GG88 said:
Have you read the thread below this one? Is your problem similar?
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
Yea you mean the thread Vibrant bricked? Maybe not. [E:Can't mount, Solved ??
Yea i saw tat thread this was the problem i had when i tried to revert from a cm9 mod. Then i downloaded the stock eclair v2.1 rom and flashed it using odin. After that only i got the phone bricked where i upgraded to froyo using the samsung kies mini and when everything got upgraded the phone didnt reboot at all for about 1/2 hr. i tried all sort of things and nothing responded.
Yeah that's the thread I was talking about, I've had that problem and went through all that but not your issue. Sorry thought I could help.
Sent from my SGH-T959 using XDA
Actually The Problem is.
We Updated the Device to CM7 and ICS and we messed up the Modem in it. SO we didnt get signal after the boot up and also by flashing a Modem.
Then what we did is, we used ODIN back to ECLAIR and it boot up fine and we got signal and everything was working fine like out of the box.
Then we used KIES MINI to update the software from ECLAIR TO FROYO officially.
Kies mini went fine in the Process and after it said Firmware update process completed we click finished and then nothing showed up on the device..
It shows blank screen all the time, key combination wont work and also it wont boot up.
Also we tried the download mode by pulling out the battery, still no sign of download mode yet..
Yea been searching in many forums and saw some useful posts regarding this brick.
There has been some problems with the update of froyo v2.2 that is released and many customers got the phone bricked during this update. This is the same thing that happened to me the other day..
http://androidgals.com/2011/01/22/froyo-upgrade-fails-for-some-vibrant-users-see-our-fix/
Hope i get my jig today and try to get into the download mode and update you guys here. Anyways....... its like ((

[SOLVED] my i9100 died on me, what now!

well guys seems my sgs2 i9100 died on me.
I'm an experienced user so I know what I'm doing, but this time seems it died.
what happened.
flashed new LQ5 sammy rom via odin for a quick test drive, all went smooth and tested all I had to test.
then it was time to flash another rom via odin.
as always before flashing another rom, I boot into fake recovery using cwm 5.8.1.5 and erase all partitions, system,data & cache and then reeboot straight to download mode to reflash the other rom via odin.
well this time, after erasing partitions I reebooted but it just went dead.
I tried about everything, even booting with usb jig into download mode, but it just doesnt work. screen is always black no message no signal no nothing.
what can I try to before RMA this Sucker ?
edit: solved by repair center replacing PBA MAIN
tks in advance,
remorema
remorema said:
well guys seems my sgs2 i9100 died on me.
I'm an experienced user so I know what I'm doing, but this time seems it died.
what happened.
flashed new LQ5 sammy rom via odin for a quick test drive, all went smooth and tested all I had to test.
then it was time to flash another rom via odin.
as always before flashing another rom, I boot into fake recovery using cwm 5.8.1.5 and erase all partitions, system,data & cache and then reeboot straight to download mode to reflash the other rom via odin.
well this time, after erasing partitions I reebooted but it just went dead.
I tried about everything, even booting with usb jig into download mode, but it just doesnt work. screen is always black no message no signal no nothing.
what can I try to before RMA this Sucker ?
tks in advance,
remorema
Click to expand...
Click to collapse
Well nothing, there are only to things that can resurrect this paperweight for you, and my guess is that you have neither of them
1. Fix it using JTAG
2. Change the PCB
So send it off to a repair centre near you mate
Best regards
Sendt fra min GT-I9300 med Tapatalk2
Ratata82 said:
Well nothing, there are only to things that can resurrect this paperweight for you, and my guess is that you have neither of them
1. Fix it using JTAG
2. Change the PCB
So send it off to a repair centre near you mate
Best regards
Sendt fra min GT-I9300 med Tapatalk2
Click to expand...
Click to collapse
I have good soldering skills but For jtag looks like there´s a box needed, and since its still under warranty I guess I'll try to RMA before opening and permanently void my warranty.
Sounds like you hit the eMMC brick. I know this sounds cruel but it gave me the heads up as I was about to flash the new LQ5 ROM. Might think twice about it. Don't mess about with it, just send it off for repair and play dumb.
Sent from my GT-I9100 using Tapatalk 2
themadba said:
Sounds like you hit the eMMC brick. I know this sounds cruel but it gave me the heads up as I was about to flash the new LQ5 ROM. Might think twice about it. Don't mess about with it, just send it off for repair and play dumb.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
I think it has to do with the fake recovery. once this LQ5 firmware as a new pit file different from the older gingerbread one. and the fake recovery might not be prepared to deal with the partitions the way this new pit repartitoned
If you stay off the recovery, the rom works flawlessly, its my bad habbit of formatting the partitions before flash that screwd me
its nice that I have a usb jig and the counter is zero that way they cannot acuse me of using non official firmware.
Can you explain to me what the “fake" recovery is? Do you mean custom recovery?
Sent from my GT-I9100 using Tapatalk 2
themadba said:
Can you explain to me what the “fake" recovery is? Do you mean custom recovery?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
this http://www.clockworkmod.com/rommanager
you can boot into stock recovery and from there boot into fake recovery without the need to having a custom recovery installed in your phone.
Interesting. You didn't have ClockworkMod Recovery then? Because ROM Manager and CWMR don't get on together. Just return your phone to Samsung and say the update failed in Kies. It's a 50/50 chance they will fix it. But it's worth a try.
Sent from my GT-I9100 using Tapatalk 2
The same has happened to me after an LQ5 NanDroid backup. Phone is dead, cannot boot, get recovery to start, no Odin, no Jig; nothing. Will it have to be sent for repair peeps?
Sent from my HTC Desire using XDA App
fs1023 said:
The same has happened to me after an LQ5 NanDroid backup. Phone is dead, cannot boot, get recovery to start, no Odin, no Jig; nothing. Will it have to be sent for repair peeps?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
either that or a jtag box.
Sent from my STM712HCZ using Tapatalk 2
Well if it is the eMMC brick, even a JTAG repair won't save it. A new motherboard is in place. Just send it to Samsung and play stupid
Sent from my GT-I9100 using Tapatalk 2
This is really bad if Samsung enabled MMC_CAP_ERASE in this new kernel, they absolutely should not have done this given the known consequences...
Sent from my GT-N7000 using Tapatalk 2
themadba said:
Well if it is the eMMC brick, even a JTAG repair won't save it. A new motherboard is in place. Just send it to Samsung and play stupid
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
if jtag cant save it does that mean samsung wont be able to confirm what appened to the board?
Sent from my STM712HCZ using Tapatalk 2
remorema said:
if jtag cant save it does that mean samsung wont be able to confirm what appened to the board?
Sent from my STM712HCZ using Tapatalk 2
Click to expand...
Click to collapse
if ur phone is bricked samsung will not knw wat u had done
just act stupid in front of them
i did the same thing when i had bricked by phone
i told them i was updating the phone in kies and after that my phone din start
What build did you die on? Saying "LQ5" is useless - with ICS you MUST include the FULL build identifier including region code when talking about a given build.
Well now I might be little more cautious, but I have wiped multiple times using the dial code and it worked fine.
Might be the touch recovery done something or you!
Have to be sure before everyone gets Bizzurk about the Emmc brick, which we didn't have until now.
Fix it by JTAG / univ on Samsung Centre
Sent from my GT-I9100 using xda premium
neerajganga said:
if ur phone is bricked samsung will not knw wat u had done
just act stupid in front of them
i did the same thing when i had bricked by phone
i told them i was updating the phone in kies and after that my phone din start
Click to expand...
Click to collapse
yep
will do that
Sent from my STM712HCZ using Tapatalk 2
The LQ5 release the OP is talking about is the leaked Samsung release of 4.0.4 for the GS2. Leaked a few days ago by sammobile.com. Is there any way to tell if the MMC_CAP_ERASE is still present in Samsung's new kernel? Or that is is at least equal to 0?
Sent from my GT-I9100 using Tapatalk 2
Mobile Odin Pro
Just a heads up. I purchased and used Mobile Odin Pro from since the release and have always used that ever since to flash leaked or official samsung roms due to the fact the pc version bricked my i5800 years back. Happy to say, It never failed me, Also it has support for Wipe Data and Also Dalvik cache. Options to Enable Ever Root, Inject Super Su (Best), And Mobile Odin so your always ROOTED :good:. Gotta hand it to Chainfire for his awesome works. I would suggest for everyone to use it for a worry free Day anytime changing non custom recovery roms, also I have had problems using superuser in the past when trying to install CWMR. Never with Super SU Pro, That's why I use it. Before thinking this post is not useful, think about it, you would be able to wipe data before flashing with no need to worry and perform it via fake recovery or CWMR. Also Odin performs MD5 checksum at your request to ensure its official.

revert to ICS from JB

I have installed slim bean on my vibrant but found it laggy....so i wants to back to ics ...now i m flashing ics rom but getting error as installation aborted.
I have flashed glitchy kernel but no luck
Help me
Odin back to stock first. I think your treading on dangerous territory if you try to go from JB to ICS directly.
I agree with Toast ^^
I always suggest going back to stock via odin before doing anything like that, just to be safe.
If you can't or are in a rush,....you can get back to ICS from JB in the usual way (full wipe, flash)...I do it all the time, since odin isn't an option for me
at the moment...so I can assure you it's more or less safe, since my phone is still running just fine even though I've gone back and forth without odin quite a few times.
But again, if possible....always odin.
Good luck!
Finally tried to flash phone with odin but i m not able to go into download mode...i have tried 3keys combo, usb jig but no luck.
Now phone is stuck on samsung vibrant screen maybe now its bricked.
Any suggestions wat to do now ?
Sent from my SGH-T999 using xda app-developers app
sanchitgrover said:
Finally tried to flash phone with odin but i m not able to go into download mode...i have tried 3keys combo, usb jig but no luck.
Now phone is stuck on samsung vibrant screen maybe now its bricked.
Any suggestions wat to do now ?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
if u have gb bootloader u have to use 2 button combo...if that doesn't work then ............why can't u enter recovery and flash slim bean u had ....and later Odin to stock?
sanchitgrover said:
Finally tried to flash phone with odin but i m not able to go into download mode...i have tried 3keys combo, usb jig but no luck.
Now phone is stuck on samsung vibrant screen maybe now its bricked.
Any suggestions wat to do now ?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Sometimes it can be tricky getting into DL mode. Try pulling the battery, have phone plug in to the cable/PC, hold button combo and put the battery back in. Also try different ports on PC doing this. If you have any life you are not hard bricked so don't panic!
Sent from my SGH-T959 using xda premium
Tried both ways to enter into bootloader but no luck..
I m not able to go into recovery or download mode.
I m feeling i have killed my vibrant
Sent from my SGH-T999 using xda app-developers app
when did last time u used download mode? were u able to use recovery after flashing slimbean? u should have odined back before installing ics ............I think if u can't enter both recovery and download mode then u might have hard bricked ur vibrant.........
Downgrading
When downgrading, upgrading or flashing new roms, it is always good practice to odin back to stock. This will help remove any "ghost" files that may still be around.
Sorry to hear about your phone but don't give up. Keep searching the forums and you may find a way to fix our phone.
I have searched all forums but not found any gud answers .
Is there any way to unbrick hard bricked phones ?
Sent from my SGH-T999 using xda app-developers app
I heard about one click unbrick ......just search it ......that will be ur last hope............if that won't work then u got ur self new fancy paper weight .....sorry cantdo anything .......if u are in India then give to Samsung service centre they might help
Just because you don't see the graphic showing download mode doesn't mean you cannot get in it.
In a post a couple days ago called "I need help!" Woodrube posted a guide about it.
Open Odin, plug in your USB to PC, not phone yet.
Now try to enter download mode. You may set no graphics or black screen but, it doesn't mean Odin won't see your phone. Its happened 3 times that I know of in the last couple days. Since you can still see the Vibrant text all hope isn't lost.
Just some "in case you need it" info, you can go to
www.mobiletechvideos.com
They can do a JTAG repair to fix a hard brick. They can also perform the unbrickable mod. They are very professional and have fast service. I shipped my phone off from Washington D.C. to them in Texas on a tuesday, I had my phone back on monday. They stayed in contact to notify me when my phone arrived, when they completed and shipped.
Hopefully no one will need their service but JIC.
Sent from my SGH-T959 using xda premium

[Q] Possibly Bricked GS3?

I'm new to the whole rooting scene, and I decided I was going to root my GS3. I had a little bit of help, but it was mostly on my own. I did some reading and decided to try out the ToolKit. I didn't have much luck with that, so I used Odin (Odin 3.07) to restore (I guess?) the original stock file. So I, reset it completely, and put Team Win Recovery on it to attempt to flash CM10. I got Status 7 (?) every time, so I had to restore to stock using Odin once more. The battery level was above 90% and during the restoration of stock, the screen turned off and I'm unable to boot into download or recovery mode. If I plug it in with the battery nothing happens, but without the battery in it, the red LED lights up. Am I bricked? Does anyone have any ideas?
Sounds like a hard brick if you can't get into download mode. Keep trying to get in download mode, flash a stock rom, reset in recovery then root it with CF_Root or just CWM and flash supersu
xSpeced said:
Sounds like a hard brick if you can't get into download mode. Keep trying to get in download mode, flash a stock rom, reset in recovery then root it with CF_Root or just CWM and flash supersu
Click to expand...
Click to collapse
It won't let me boot into download mode. I've tried a couple of times. Do you have any other suggestions? Or should I just take it in to a Radio Shack/Sprint store and see if they can replace it if I just act dumb. It might be SDS is what I'm thinking because I had it plugged in and it just died. And it was getting pretty hot.
Could very well be the Sudden Death issue some of S3 owners were confronted with during last weeks. If that's the case Samsung will repair it and replace motherboard of your S3. Worth a try I would say.
Sent from my GT-I9300 using xda app-developers app
Jan-Ernst said:
Could very well be the Sudden Death issue some of S3 owners were confronted with during last weeks. If that's the case Samsung will repair it and replace motherboard of your S3. Worth a try I would say.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
From the reading I've been doing in the past couple of hours, it does appear to be Sudden Death. But it could also very well just be hard bricked. I'm just going to tell them it's SDS just in case though :X Thanks for the help!

Categories

Resources