so i think this is a hard brick, but i was installing cm9 and i did everything it said to do but when i came out of recovery and the blue led stayied on and the splash screen never came up so what can i do??? would sprint give me a new one??? fyi i cant get into recovery or download mode
jamcar said:
so i think this is a hard brick, but i was installing cm9 and i did everything it said to do but when i came out of recovery and the blue led stayied on and the splash screen never came up so what can i do??? would sprint give me a new one??? fyi i cant get into recovery or download mode
Click to expand...
Click to collapse
I'm not familiar with cm9 but have you tried a battery pull?
Esoteric68 said:
I'm not familiar with cm9 but have you tried a battery pull?
Click to expand...
Click to collapse
yes its not stuck in a boot loop it doesnt even some up to the " Samsung galaxy s II" screen
I'm not an expert but It isn't a hard brick till your device is non responsive meaning screen doesn't turn on and usb/adb won't detect phone. What you may have is a soft brick or semi brick.
Does your device turn on at all? does it charge? does usb detect it.
Febby said:
I'm not an expert but It isn't a hard brick till your device is non responsive meaning screen doesn't turn on and usb/adb won't detect phone. What you may have is a soft brick or semi brick.
Does your device turn on at all? does it charge? does usb detect it.
Click to expand...
Click to collapse
odin wont as it wont go into download mode and the only thing that turns on is the blue LED light in the top right corner, but it did start to feel warm after a while. and as for ADB idk
jamcar said:
odin wont as it wont go into download mode and the only thing that turns on is the blue LED light in the top right corner, but it did start to feel warm after a while. and as for ADB idk
Click to expand...
Click to collapse
Odd... I'm not very experienced to new samsung devices since my samsung captivate.. I'm not sure if you do, or don't have a jig. I will assume you do though since you said it won't go into download mode.
You mentioned you were flashing CM9, were you on a ICS ROM before?
Febby said:
Odd... I'm not very experienced to new samsung devices since my samsung captivate.. I'm not sure if you do, or don't have a jig. I will assume you do though since you said it won't go into download mode.
You mentioned you were flashing CM9, were you on a ICS ROM before?
Click to expand...
Click to collapse
yeah i was on cm9 and wanted to reflash it cause i was missing somethings.
i dont have a jig but would that work? i thought they only reset your flash counter
If your phone does not turn on (blue light only), can't get into download mode, isn't recognized by a PC (Odin), then it is hard bricked.
It could just be a bad flash or wrong flash, then a JTag service for $50 would solve your issue.
If you messed up your emmc chip, then it is hard bricked for real.
Please provide:
What ROM were you on?
What kernel were you using?
What recovery did you use? (Did you use Rom Manager)
What ROM were you flashing?
jamcar said:
yeah i was on cm9 and wanted to reflash it cause i was missing somethings.
i dont have a jig but would that work? i thought they only reset your flash counter
Click to expand...
Click to collapse
Oh I wouldn't exactly know as I just ordered my SGS2 to get back into the Sammy crowd.. HTC became horrible. The user above me can prob help you best =-)
zonlicht said:
If your phone does not turn on (blue light only), can't get into download mode, isn't recognized by a PC (Odin), then it is hard bricked.
It could just be a bad flash or wrong flash, then a JTag service for $50 would solve your issue.
If you messed up your emmc chip, then it is hard bricked for real.
Please provide:
What ROM were you on?
What kernel were you using?
What recovery did you use? (Did you use Rom Manager)
What ROM were you flashing?
Click to expand...
Click to collapse
how would i JTag it???
cm9
cm9 default kernel
el26 repacked ( the one in the instructions , i used mobile odin to flash that then when right into recovery)
cm9
jamcar said:
yeah i was on cm9 and wanted to reflash it cause i was missing somethings.
Click to expand...
Click to collapse
This is the extra info I was looking for, and is the cause of your hard brick. Very likely you did not Odin the stock EL26 kernel + CWM, which you should have done before reflashing anything. Wiping anything in CWM while on an ICS kernel when you have CM9 on your phone is a death sentence.
Sprint will likely exchange it for a refurbished unit for a $35 fee. www.mobiletechvideos.com may be able to JTAG it for you for $50.
Edit - Oh hmm in your last post it says you did indeed flash the EL26 stock repack. I'm not sure where you went wrong then, but your description sounds like the "blue light of death", which is usually indicative of a hard brick.
Dchibro said:
This is the extra info I was looking for, and is the cause of your hard brick. Very likely you did not Odin the stock EL26 kernel + CWM, which you should have done before reflashing anything. Wiping anything in CWM while on an ICS kernel when you have CM9 on your phone is a death sentence.
Sprint will likely exchange it for a refurbished unit for a $35 fee. www.mobiletechvideos.com may be able to JTAG it for you for $50.
Edit - Oh hmm in your last post it says you did indeed flash the EL26 stock repack. I'm not sure where you went wrong then, but your description sounds like the "blue light of death", which is usually indicative of a hard brick.
Click to expand...
Click to collapse
what do you think i should do, sprint or JTag??? i would kinda like to keep what is on the internal memory, but i dont know if the JTag would do that.
USB jig won't work to fix it. You either have to have Sprint replace it or Jtag can fix this type of brick too. I had the hard brick like you have where only the blue led turns on and he was able to fix it.
MeWarning said:
USB jig won't work to fix it. You either have to have Sprint replace it or Jtag can fix this type of brick too. I had the hard brick like you have where only the blue led turns on and he was able to fix it.
Click to expand...
Click to collapse
did you have the same memory in it after wards???
No, sorry but you're not going to be able to get back anything on internal memory no matter which way you go to fix it. And Sprint is kind of a crap shoot. If they replace your phone and take apart the old one and discover a custom ROM on it they can charge you full price for the replacement. Then again they may just give you a new one and that's it.
jamcar said:
what do you think i should do, sprint or JTag??? i would kinda like to keep what is on the internal memory, but i dont know if the JTag would do that.
Click to expand...
Click to collapse
You're out of luck on your internal memory in either scenario. Sprint will almost definitely exchange it, but it would require you playing dumb, which is up to you. JTAG lets you keep your original device (not a refurb) if you care about that, but you have to mail it to them, get it fixed (hopefully) and have it mailed back. Sprint would likely get you a refurb faster and for $15 less, but again, you'd need to lie to them to avoid any hassles. It really depends on how you want to approach this and what you're comfortable with.
jamcar said:
how would i JTag it???
cm9
cm9 default kernel
el26 repacked ( the one in the instructions , i used mobile odin to flash that then when right into recovery)
cm9
Click to expand...
Click to collapse
You flashed a gingerbread kernel + CWM repack on a CM9 rom. That is such a bad idea.
zonlicht said:
You flashed a gingerbread kernel + CWM repack on a CM9 rom. That is such a bad idea.
Click to expand...
Click to collapse
no it is not .. it just will never boot but just go strait into cwm and flash
Sent from my SPH-D710 using Tapatalk 2 Beta-4
Epix4G said:
no it is not .. it just will never boot but just go strait into cwm and flash
Sent from my SPH-D710 using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
yea thats our only method of having recovery for cm9. that's what i did to update the radio. odin el26cwm, during boot hold volume up, then flash.
toprock23 said:
yea thats our only method of having recovery for cm9. that's what i did to update the radio. odin el26cwm, during boot hold volume up, then flash.
Click to expand...
Click to collapse
Maybe that is possibly the problem.
Most if not all the bricks are because of CM9 or AOKP. If you guys are forced to use a GB kernel + cwm to flash an ICS rom, that might be a problem.
Related
Is bricking your device easy to happen? I'm scared of bricking my phone. Can the phone still brick when you do everything correctly?
Anything is possible.
I took chances on all my phones and never had a problem .
sent from the Dark §¡3€
MarsHD2 said:
Is bricking your device easy to happen? I'm scared of bricking my phone. Can the phone still brick when you do everything correctly?
Click to expand...
Click to collapse
If you do everything correctly, most likely not. A lot of bricks occurs because of user error. Flashing the wrong Galaxy s2 ROM/recovery etc, on our devices... there are a total of 5 variants i think.. only two works with ours.. skyrocket and hercules (i727 and t989)
I haven't heard of any bricks that occurs for doing everything correctly.
I have read up on some rare cases where a phone just blacks out from normal use... from heating up... or just random stuff.. some of the users aren't even rooted. That is purely the fault of the hardware simply giving up.
It is very easy to Root our phone:
ODIN
Flash Recovery
Flash ROM or Superuser
you can even mess up on flashing the recovery but you can actually recover from it. You will get the message where it says "firmware update failed, please connect to kies and recover," this is easily recoverable.. You just go back to ODIN Mode and flash recovery again.
The only way you can BRICK the phone:
1. Flash a ROM that doesn't belong to our device.
2. Mess up on Flashing a Stock ROM (user fault) such as battery falling out.. battery dying.. cable falls out. cable is loose etc.. while in the middle of flashing.
I remember reading that people tried to flash a Modem that didn't belong to our device, but ODIN either prevented this from happening or you get the "firmware update failed..." message.
TL;DR: No it is fairly safe and the only chances of bricking is when flashing something that isn't for our phone.
1. Flash a ROM that doesn't belong to our device.
2. Mess up on Flashing a Stock ROM (user fault) such as battery falling out.. battery dying.. cable falls out. cable is loose etc.. while in the middle of flashing.
Click to expand...
Click to collapse
I still don't see how those two things can mess up the phone? Can't you just use odin to reflash? You would think that they make the download portion of the phone non-writable so you can always use it with odin to reflash in any state. I must be missing something here. Does flashing a ROM mess with the "Download" partition also?
It is normally unwritable to prevent such problems. By using odin, you are bypassing the safety feature of the ROM area. By interrupting the process mid-way, you might not do not copy over all the 'necessary' files for the phone to function at it's lowest levels of operation. IE turn on when you tell it to. Flashing a rom doesn't mess with the user accessible partition.
Is using ClockWorkMod to flash any safer?
Catch-22.
If you want to use the ClockWorkMod app to flash, you will need to grant it superuser permissions. How do you get superuser? You need to be rooted by installing ClockWorkMod.. odin is pretty safe. Make sure to have a half-way charged battery (at least), and click the pda button.
True but how about subsequent flashes
Look bro its hard to brick these samsung but its not impossible trust me i know from experience, my first ever phone i rooted and played with was the galaxy s 4g and lets just say i bricked the **** out of it. think of it like this you flash a rom for a phone that is not yours this phone has a physical keyboard and the only way that phone can get into download mode is a combination of keys on the keyboard (this is just hypothetical) and the only way to get odin to recognize device is to be in DL mode...How can you be in DL with a phone that doesnt have physical keyboard but requires use of it to get into DL mode.
I've never bricked. Been in a bootloop, but just had to wipe and flash again
Sent from my SGH-T989 using xda premium
jdubb1106 said:
Look bro its hard to brick these samsung but its not impossible trust me i know from experience, my first ever phone i rooted and played with was the galaxy s 4g and lets just say i bricked the **** out of it. think of it like this you flash a rom for a phone that is not yours this phone has a physical keyboard and the only way that phone can get into download mode is a combination of keys on the keyboard (this is just hypothetical) and the only way to get odin to recognize device is to be in DL mode...How can you be in DL with a phone that doesnt have physical keyboard but requires use of it to get into DL mode.
Click to expand...
Click to collapse
Get a jig?
Sent from my SGH-T989 using XDA App
jig didnt work on my sgs4g. And all that example was purely hypothetical, just using as example so op understands what people are trying to say.
Sent from my SGH-T989 using xda premium
jordanishere said:
Get a jig?
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
I tried to flash a kernel and a rom for the i9100 on mine using cwm. Flash went through just fine, went to reboot.... Nuthin. Not even a jig brought it back. Just be sure of what you're flashing and you'll be good. I've been flashing roms since the razr v3, and this is my first brick.
Sent from my Nexus One using Tapatalk
zak rabbit said:
I tried to flash a kernel and a rom for the i9100 on mine using cwm. Flash went through just fine, went to reboot.... Nuthin. Not even a jig brought it back. Just be sure of what you're flashing and you'll be good. I've been flashing roms since the razr v3, and this is my first brick.
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
Its tough with all the diff varients. doesnt help that they all have the exact same name too.
Props for not being one of the whiners who blames their brick on xda. hope you get a new t989.
Sent from my SGH-T989 using XDA App
Just to throw this in there - if your phone does ANYTHING when you try to turn it on (soft keys light up/some sort of response from the screen), or plug it in, it is a soft brick in which you should be able to recover the phone. Many times it takes multiple tries (due to picky button combos) but it will come back. Coming from the Vibrant 3g, I can tell you from experience that you know when you have a hard brick because the phone does not respond AT ALL. It doesn't do anything when it's plugged in or when buttons are pressed. The ONLY time I've legitimately bricked a sgs was when I flashed a rom on a low battery not knowing that the phone does not charge in recovery. The battery died during reboot and the phone would not respond to anything. This is a true hard brick.
Also i'm not sure if this has been said but I would never flash anything without art least 50% battery life
The galaxy is pretty cool because of how easy it is to unbrick. All you have to do it load the stock kernel from Odin and plug up the USB, mount the sd, and place the ROM onto the sd and unmount then flash it. In the case that you install a bad ROM, if it's just the kernel then just load the stock kernel with Odin then use the one you want.
Sent from my SGH-T989 using xda premium
iwasblown said:
The galaxy is pretty cool because of how easy it is to unbrick. All you have to do it load the stock kernel from Odin and plug up the USB, mount the sd, and place the ROM onto the sd and unmount then flash it. In the case that you install a bad ROM, if it's just the kernel then just load the stock kernel with Odin then use the one you want.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
that was very confusing, but I'm not sure if you really know what a true hard brick is, which is really hard to unbrick and need to do the jtag stuff.
what you addressed is a softbrick (i don't even consider this a brick because the phone turns on), which is flashing an incomplete rom or kernel that is for our device, however if it was another device's than it might lead to a hardbrick.
Teo032 said:
that was very confusing, but I'm not sure if you really know what a true hard brick is, which is really hard to unbrick and need to do the jtag stuff.
Click to expand...
Click to collapse
A true hard brick cannot be unbricked. With a true hard brick the phone won't turn on and therefore, you cannot use Odin. Jtag also won't work if the phone does not turn on/the hardware buttons don't work.
Hello,
Recently I've flashed Arco's CM9 version. It all went well for a couple of weeks until today. When I booted my phone, suddenly all apps started crashing and then it rebooted. But, the problem is, it is now stuck on a flashing Samsung logo.
Before I've started this thread, I've read many many similar threads about this, and started a 'rescue operation' by my own by using the tutorials for flashing back a stock rom with ODIN and other possibilities.
Unfortunately, after I've tried twice using ODIN, my phone is still stuck in the Samsung logo loop. I also can't enter Recovery mode, but am able to enter Download mode, as you've probably noticed.
As this is my first Android phone, I've always carefully read the tutorials and disclaimers about possible failures. I'm aware that the maker of the rom is not responsible for this.
Since I tried to flash back to stock android 2.3.6 from CM9 kernel, I've read that this could give some problems. My question is:
- Would flashing CM9 back worth a shot, or totally useless?
I hope you can help me, and if there isn't a solution, I hope the shop can cover this as I've got warranty for one year and 9 months.
Care to share how you had flashed it at first...
And you can still boot to recovery rite ?
Sent from my GT-I8150 using xda premium
countdown93 said:
Hello,
Recently I've flashed Arco's CM9 version. It all went well for a couple of weeks until today. When I booted my phone, suddenly all apps started crashing and then it rebooted. But, the problem is, it is now stuck on a flashing Samsung logo.
Before I've started this thread, I've read many many similar threads about this, and started a 'rescue operation' by my own by using the tutorials for flashing back a stock rom with ODIN and other possibilities.
Unfortunately, after I've tried twice using ODIN, my phone is still stuck in the Samsung logo loop. I also can't enter Recovery mode, but am able to enter Download mode, as you've probably noticed.
As this is my first Android phone, I've always carefully read the tutorials and disclaimers about possible failures. I'm aware that the maker of the rom is not responsible for this.
Since I tried to flash back to stock android 2.3.6 from CM9 kernel, I've read that this could give some problems. My question is:
- Would flashing CM9 back worth a shot, or totally useless?
I hope you can help me, and if there isn't a solution, I hope the shop can cover this as I've got warranty for one year and 9 months.
Click to expand...
Click to collapse
it happened to my friends phone also, he can go to DL mode but not recovery mode, he flashed a stock rom via odin, but that didnt help, he was still stuck at samsung logo, and about flashing CM9 again, i guess u cant bcoz u cant go to recovery mode, if youve flashed a stock rom again and that didnt work for you too, i guess u need to send to samsung for repair, i remember my friend said it was a hardware problem, good luck
vanir29 said:
it happened to my friends phone also, he can go to DL mode but not recovery mode, he flashed a stock rom via odin, but that didnt help, he was still stuck at samsung logo, and about flashing CM9 again, i guess u cant bcoz u cant go to recovery mode, if youve flashed a stock rom again and that didnt work for you too, i guess u need to send to samsung for repair, i remember my friend said it was a hardware problem, good luck
Click to expand...
Click to collapse
I've read elsewhere that it was a hardware problem that appeared on 1:10 Wonders... I'm really disappointed since this was my first smartphone...
A small question though: Since I've (tried to) flash it back to stock rom, if I bring it back to the shop where I bought it, would they notice that there was another rom, which could give them a reason that I've void the warranty? I really don't want to pay another amount of cash for this (faulty) phone.
Also in reply to andynroid: I've flashed CM9 the first time with CWM, as adviced by Arco68.
Can you still go to recovery ?
Sent from my GT-I8150 using xda premium
countdown93 said:
I've read elsewhere that it was a hardware problem that appeared on 1:10 Wonders... I'm really disappointed since this was my first smartphone...
A small question though: Since I've (tried to) flash it back to stock rom, if I bring it back to the shop where I bought it, would they notice that there was another rom, which could give them a reason that I've void the warranty? I really don't want to pay another amount of cash for this (faulty) phone.
Also in reply to andynroid: I've flashed CM9 the first time with CWM, as adviced by Arco68.
Click to expand...
Click to collapse
well in my friend's case, samsung accept it and repair it, if the stock rom is flash successfully, i think they wont notice that you've flash i custom rom, good luck though
Am I being dense.... but what is 1:10 Wonder???
I saw this also mentioned by Rio S. (I think)....but did not think anything about it.... but, is it HW version??
Where can I see it on device.
Andy....
Guy says in OP...
can't get Recovery!!!
:banghead:
Sent from my GT-I8150 using Tapatalk
irishpancake said:
Am I being dense.... but what us 1:10 Wonder???
I saw this also mentioned by Rio S. (I think)....but did not think anything about it.... but, is it HW version??
Where can I see it on device.
Andy....
Guy says in OP...
can't get Recovery!!!
:banghead:
Sent from my GT-I8150 using Tapatalk
Click to expand...
Click to collapse
Hi...
I wrote in this thread
http://forum.xda-developers.com/showpost.php?p=25616419&postcount=17
The only solution seems to be to flash an Asian rom with multi package.
Sent from my GT-I8150 using Tapatalk
when you try to enter recovery mode, what is the image you first see? is there an image that look like an android? i cant remember the exactly image but if you see that image, i think you must reflash the CWM via odin. Because every time i reflash the stock rom, my recovery mode will gone. So try to reflash CWM via odin. Nothing wrong if you give it a try
irishpancake said:
Am I being dense.... but what is 1:10 Wonder???
Click to expand...
Click to collapse
i think it is one(1) out of ten(10) or 1 is to 10 sgw has a hardware problem, i guess thats what he meant, but isnt it kinda high
Experienced this as well. Just sent it for warranty and they swapped out the motherboard.
alidsd said:
The only solution seems to be to flash an Asian rom with multi package.
Sent from my GT-I8150 using Tapatalk
Click to expand...
Click to collapse
I've heard and read about that, I thought that Rio did that, but it wasn't succesful.
tomatoman23 said:
when you try to enter recovery mode, what is the image you first see? is there an image that look like an android? i cant remember the exactly image but if you see that image, i think you must reflash the CWM via odin. Because every time i reflash the stock rom, my recovery mode will gone. So try to reflash CWM via odin. Nothing wrong if you give it a try
Click to expand...
Click to collapse
I wished I could enter Recovery mode, but the problem is: I can't
. But I also didn't know that if I flash back to stock rom, the recovery would be gone too. Maybe I should reflash CWM via odin. Nice advice.
vanir29 said:
i think it is one(1) out of ten(10) or 1 is to 10 sgw has a hardware problem, i guess thats what he meant, but isnt it kinda high
Click to expand...
Click to collapse
Jup. One out of ten => 10%. Such an error rate may not appear for such a great brand. That is ridiculously high. Even 1% is too high in my opinion.
Deathmax said:
Experienced this as well. Just sent it for warranty and they swapped out the motherboard.
Click to expand...
Click to collapse
Yeah, but what I've heard from others in the Netherlands: they will say that your device has been damaged by water, which isn't protected by warranty. And the bill is equal to a new device, or even more expensive. I hope they're in 'good mood', otherwise I maybe have to search for another device.
Hey Bro... this happen to me a while ago.... but covered by warranty , just simply told them at the SSC that you do an update via Kies and sxxt happen , coz in my place there are cases that the phone hang after update via Kies not only this model , it happen to others model too.
I suggest that you flash it back to stock before you send it back to SSC , without CWM .
cheers
vanir29 said:
i think it is one(1) out of ten(10) or 1 is to 10 sgw has a hardware problem, i guess thats what he meant, but isnt it kinda high
Click to expand...
Click to collapse
My friend!!!
I think you have solved the mystery of 1:10......
but can Rio S. confirm??
I don't have bricked phone....
but I try to understand what is causing these, so to be of some help....
and 1:10 was a puzzle to me, so thank you...
Sent from my GT-I8150 using Tapatalk
here is what I did
i was coming from Calkulin ROM and decided to go with milestone 5 so i did what the directions said i flashed el26 through odin and when i was doing that the computer died on me (my fault) so i thought it was over, it was time to call in for a new phone but when i took the battery out and went in my recovery and did a restore it was back to normal
so i took my chances and flashed it again this time it worked but i forgot to flash the gaaps so i tried to go back to the recovery i had a stock recovery 3a so i tried flashing el26 through odin mobile and that f***ed everything up now my phone is stuck at the galaxy sII screen with the yellow triangle
so my question is whats best to do? call sprint get a new phone
* i dont want to but a jig might as well get a new phone*
or is there somewhere someone can point me to to fix it
any help will be appreciated thanks.
Are you able to get into download mode by holding power+volume down for a few seconds?
Sent from my SPH-D710 using xda premium
Can you get it into download mode? If so, hook it up to a PC and use the Odin OC EL26 to see if that will clear it up. (The yellow triangle can be removed with Triangle Away once you get to ICS)
And please don't thank me for this - I've just seen sfhub post the same thing time and time again. If anyone deserves credit it would be him for this post.
yea im in it right now
You got this far so your chances of being hard bricked dropped dramatically. Hope the Odin OC does it for you on the first try.
An ICS rom won't boot with el26 kernel so its normal. Just boot into recovery from the triangle screen, wipe, then reflash the from and gapps
Sent from my SPH-D710 using Tapatalk 2
garwynn said:
You got this far so your chances of being hard bricked dropped dramatically. Hope the Odin OC does it for you on the first try.
Click to expand...
Click to collapse
when in OC Odin what do i do its empty and it finds my phone fine but what am i missing?
When in download mode use sfhubs one click restores and you should be up and running again
Sent from my SPH-D710 using xda premium
Why the topic is possibly bricked (Lol) the lol.shouldn't be there
Epic touch phone of xXHELLBoy91Xx
A30laa said:
when in OC Odin what do i do its empty and it finds my phone fine but what am i missing?
Click to expand...
Click to collapse
Once you are in download mode and it finds your phone (a yellow box with a COM port lights up and you'll see "Added!" in the log box) just click Start and wait until the bigger box to the left of the yellow one says "PASS!" If it looks like it's hanging at the Modem, just wait - process takes about 10 minutes regardless if you have a power system or not.
(I'm exaggerating on the time but you'll get the point.)
az18zz said:
Why the topic is possibly bricked (Lol) the lol.shouldn't be there
Click to expand...
Click to collapse
Cus this has happened to me about
10 times since messing with androids lol cant be mad if i dont read every little thing like im suppose to
Thanks everybody hes alive again lol so my question is now after flashing el26 to get milestone what kernel should i get then to make sure i dont lose my custom recovery ?
Sent from my SPH-D710 using XDA
Hey OP I hope you get it up and running but with all the threads about what to do in every situation if your phone takes a dump... I am not sure why you posted this and scaring more people but ok do you!
Next time try odin , try Google, try JTag, try Sprint and last but not least try your TEP. Those are the true steps to getting another phone or your phone up and running(notice none of the steps say make a new post about bricking). I know to some it may seem like this was useless but for those that get it... well Good luck OP
---------- Post added at 06:35 PM ---------- Previous post was at 06:33 PM ----------
A30laa said:
Cus this has happened to me about
10 times since messing with androids lol cant be mad if i dont read every little thing like im suppose to
Click to expand...
Click to collapse
see you got it up and running ..... LOL enjoy and glad to see you got a sense of humor as well
There is no custom recovery for ICS roms until the source is released.....custom recovery on ICS causes bricks
Ya without the custom recovery you're safest option is going to be to Odin back to EL26 with CWM5 any time you want to switch to something else. It's an extra step but the one pretty much surefire way not to get a brick. And use Calk's Format All instead of doing all the wiping manually.
I flashed a rom from CWM recovery.
Here's the part where I get laughed at....
The rom I flashed ended up being a GSM rom.
I can't boot into recovery or even get a charge indicator.
Just a dead phone at this point.
Is there any recovering from this blunder?
teamfdn said:
I flashed a rom from CWM recovery.
Here's the part where I get laughed at....
The rom I flashed ended up being a GSM rom.
I can't boot into recovery or even get a charge indicator.
Just a dead phone at this point.
Is there any recovering from this blunder?
Click to expand...
Click to collapse
try booting up into download mode
and ODIN the stock image
Wolfbeef123 said:
try booting up into download mode
and ODIN the stock image
Click to expand...
Click to collapse
It won't boot into download or recovery.
USB and wall charger won't even charge anymore.
teamfdn said:
It won't boot into download or recovery.
USB and wall charger won't even charge anymore.
Click to expand...
Click to collapse
DANG!
if you can't boot into anything ,then your most likely bricked.
If you have insurance, and your ODIN counter was at zero, you can probably say you dropped it or that it just stopped working and get a replacement for cheaper.
It's dishonest, but oh well.
Next time, please check what you flash...
I've had many close calls too, but I'm sorry about what happened.
If i had some money, (which i'm dead broke) I'd help you out, but like i said, I'm dead broke, i can't even afford a screen protector lol
Ya its ****ed.ya return if insured/has warranty. Odin counter don't matter much. They ain't gonna see it now.. and if u don't have insurance, this is the place to go http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/. Good luck in tha future
Are you sure they won't see the counter?
Someone can fix it for $60 but the flash count won't be noticed?
Anyway, I'm still under 14 day guarantee and I do have TEP so hopefully this all works out.
If still under 14 days then go to sprint and just tell them how you "woke up and it just wouldnt turn on". Its immoral i know but wat can ya do. You'll leave with a new one or at worst one on the way. And no they wont see it. If u do the 14 day sprint return thing cuz its "defective" then it def won't matter wat ur count is.
I downloaded the Jedi Mind Trick JB 2 ROM and installed it via clocwork mod recovery .. That went fine but it took me a few days to realize I didnt have a working video camera anymore on my phone.. so I thought to flash a stock ROOTed rom instead...
Then I found this threat about an updated version of Jedi Mind Trick's ROM labled JB 3.. So I wiped as much as I could in recovery and chose to format all the options it gave me in recover , Format system , data , cache , emms(or something) .. and now when I boot the phone , it shows the first flash screen , and the samsung logo starts to shimmer then it reboots back to the splash screen and repeats this process everal times before just going black and sitting there..
So I've successfully bootlooped my phone doing this..
MY PROBLEM -- I don't know how to charge my phone or connect to it to install anything else..
Is this a serious problem? How can I charge my phone to continue troubleshooting it? It still has some battery to try some things but I don't know how to hook it up to transfer any other roms to it via USB cable and PC in it's current state..
I'm very computer savvy but I'm trying to learn this phone modding stuff and I realy hope I didn't brick my phone in this process.
Can someone please help me out here? I'll be on the forums religiously until I figure this out.
What should I start doing first??
Any help would be greatly appreciated!! Thanks!
still working at it
I think I'm at the point of having to use ODIN to flash a new rom since i cannot simply copy this rom to the sdcard to use clockwork to flash it .. Am I correct on this ?
For some reason this rom I found (should be stock rooted tmobile gSII rom) does not want to open from ODIN's PDA button cause its in .zip and not .tar or anything... I'm not sure how to flash this rom with ODIN ( I'm not even 100% sure this is how its supposed to go) Any suggestions ?
phew
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
zarklon said:
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
Click to expand...
Click to collapse
Is this true? Through a recommendation (haven't done anything to my phone from rooting/flashing KANGSJUGGERNAUT2 years ago), I tried to flash CM10 and ended up with a bootloop myself. Tried flashing through ODIN but it kept crashing; does anyone know why?
Afterward, I tried to reflash it through CWM and from then on bootloops into a installation process that never completes.
For some reason my CWM turned super slow, freezes/hangs and reboots after a few minutes.
I gave the phone to a friend who does this stuff on the regular but he said my initial flash wasn't complete cause in download mode says I'm still running official? No clue.
I was told this via email/chat: "No luck, it won't even boot anymore, I think I'll just bring it back tmrw morn
10:43 PM
Sorry I'm at a wedding (yea I know random) I left my phone with coat check
OK I've narrowed down the reason but not the solution, you had an AOKP based ROM which fundamentally is based on CyanogenMod, but it wasn't correctly flashed as the phone still thought it has factory ROMs still running
11:10 PM
Clockworkmod(even though it was working before) wasn't accessing the partitions of the phone correctly so it wasn't properly wiping or flashing properly.
11:12 PM
So basically from the first time you flashed cwm it didn't flash properly then the next time you flashed using the new recovery it didn't flash anything it was supposed to do itself properly , so basically it was a chain of events in addition to a bad boot loader, that's why it never went to recovery or download mode correctly
11:13 PM
That's something that had to do with the way the phone was built meaning you may of had a bad bootloader from the very begin and are now feeling the synptoms
Basically, and I would hate to be the reason or partially the reason you have a dead phone, basically it was a matter of coincedencr that it happened as this could of happened at anytime, once you have a bad boot loader its pretty much down hill from there"
Any helpful insight as how I can rectify this? is my phone truly dead? Sorry about the quoted format, it was copied and pasted.
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
tronmech said:
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
JahJahLoO said:
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
Click to expand...
Click to collapse
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
sam.balia1012 said:
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
Click to expand...
Click to collapse
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
dont give up
JahJahLoO said:
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
Click to expand...
Click to collapse
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
sam.balia1012 said:
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
Click to expand...
Click to collapse
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
JahJahLoO said:
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
Click to expand...
Click to collapse
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
sam.balia1012 said:
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
Click to expand...
Click to collapse
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
JahJahLoO said:
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
Click to expand...
Click to collapse
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
sam.balia1012 said:
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
Click to expand...
Click to collapse
It might as well have... :crying: