Related
I look at some forums on how to do it and I'm pretty positive I can do it. But what exactly are the risks?
Is there a chance of brick?
Will I lose data?
Is it even a necessary upgrade?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Yes, there is a chance for a brick but that is rather minimal. It's the same risk that you take each time you use ODIN one click to return to stock.
Before you flash be sure to do a backup using TiBu for your apps and I use "export to external SD card" for my contacts.
Necessary upgrade? That is all up to you to decide. I did it because I wanted something new.
McKillroy11 said:
I look at some forums on how to do it and I'm pretty positive I can do it. But what exactly are the risks?
Is there a chance of brick?
Will I lose data?
Is it even a necessary upgrade?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
1.Of coarse there is a chance of a brick. Anytime you flash your device there is a potential of something going wrong. Doesn't happen that often, but it does happen. Luckily, we have lots of ways of getting out of a jam.
2.You shouldn't lose any data if you back up properly. If you need to use a computer and manually drag your pictures and music or whatever to a safe spot, or like the user above me use TiBu and make a backup of your apps and data and stuff.
3.It is not a necessary upgrade, but it is indeed exactly that.. an "upgrade"
I'm not gonna talk up which gingerbread ROMs I like, but I will say i cannot go back to froyo. The smooth, lag-free experience i have had with gingerbread has been more than pleasant.
But as always read the OP and instructions...and of coarse re-read just to be sure.
Like Nike, just do it.
Coreym said:
1.Of coarse there is a chance of a brick. Anytime you flash your device there is a potential of something going wrong. Doesn't happen that often, but it does happen. Luckily, we have lots of ways of getting out of a jam.
Click to expand...
Click to collapse
1. Is not true. You DON'T risk bricking EVERYTIME you flash ANYTHING. The only time you risk a brick (and I mean brick as in not a thing coming out of the phone, nothing not one little sign of life at all. Nothing. Anything other than that is NOT a brick) is when you are flashing bootloaders, but if you are not flashing bootloaders, which most of the time you aren't you can not brick the worst that can happen is a situation that is commonly (and stupidly) called a "soft brick" that's just when something is broken and it can't boot all the way to a functioning OS, but again that example isn't a brick at all because it's 99.9% of the time recoverable.
OP you are flashing bootloaders so in this case there is a small risk of a brick. But like was said it's the exact same risk as odin one click.
studacris said:
1. Is not true. You DON'T risk bricking EVERYTIME you flash ANYTHING. The only time you risk a brick (and I mean brick as in not a damn thing coming out of the phone, nothing not one little sign of life at all. Nothing. Anything other than that is NOT a brick) is when you are flashing bootloaders, but if you are not flashing bootloaders, which most of the time you aren't you can not brick the worst that can happen is a situation that is commonly (and stupidly) called a "soft brick" that's just when something is broken and it can't boot all the way to a functioning OS, but again that example isn't a brick at all because it's 99.9% of the time recoverable.
OP you are flashing bootloaders so in this case there is a small risk of a brick. But like was said it's the exact same risk as odin one click.
Click to expand...
Click to collapse
I didn't mean to be so critical .. I more meant to say what I said in my second sentence about something COULD go wrong but thanks for explaining it better for the OP
Sent from my SGH-I897 using XDA Premium App
Even if you do brick it's nothing to freak out about. 9 times out of 10 just putting the phone into download mode and using Odin again does the trick. Even if you need to build/buy a jig, the chances that it's so bricked that you'd need to JTAG it or send it in are ridiculously small.
Superalpaca said:
Even if you do brick it's nothing to freak out about. 9 times out of 10 just putting the phone into download mode and using Odin again does the trick. Even if you need to build/buy a jig, the chances that it's so bricked that you'd need to JTAG it or send it in are ridiculously small.
Click to expand...
Click to collapse
See it's this kind of stuff I'm talking about. This loose use of the term brick.
If you can recover it by any means other than jtag it's not a brick. There are no different degrees of bricking, if it's bricked it doesn't do a anything. Not a single solitary bit of computing, it just sits there doing nothing no matter what. Dead. A corpse.
It's either bricked or not. Just because the kernel/rom is broken and it doesn't boot properly does not mean it's bricked at all. If the bootloaders are intact and it tries to boot but fails at the kernel/rom level that is easily fixed. Throwing the term brick around in that situation, even when you add the retarded "soft brick" modifier, will just scare the poop out of a noob who just needs to remain calm and take the proper steps to have a working phone.
studacris said:
See it's this kind of stuff I'm talking about. This loose use of the term brick.
If you can recover it by any means other than jtag it's not a brick. There are no different degrees of bricking, if it's bricked it doesn't do a damn thing. Not a single solitary bit of computing, it just sits there doing nothing no matter what. Dead. A corpse.
It's either bricked or not. Just because the kernel/rom is broken and it doesn't boot properly does not mean it's bricked at all. If the bootloaders are intact and it tries to boot but fails at the kernel/rom level that is easily fixed. Throwing the term brick around in that situation, even when you add the retarded "soft brick" modifier, will just scare the **** out of a noob who just needs to remain calm and take the proper steps to have a working phone.
Click to expand...
Click to collapse
I hear ya and totally agree. But you do realize not that long ago, A LOT of people referred to the phone-!-computer screen as being "bricked". We know now that we are pretty far off from having an actual "bricked" phone in a lot of situations. But even the devs used to refer to that as a bricked device. Just gonna take some time for everyone to figure it out.
For me I went on YouTube and found joshs' video on how to flash continuum. It was very helpful and gave me the main idea of how the process is
Sent from my GT-I9000 using XDA App
Coreym said:
I hear ya and totally agree. But you do realize not that long ago, A LOT of people referred to the phone-!-computer screen as being "bricked". We know now that we are pretty far off from having an actual "bricked" phone in a lot of situations. But even the devs used to refer to that as a bricked device. Just gonna take some time for everyone to figure it out.
Click to expand...
Click to collapse
Which is why I'm trying to nip that in the bud from now on, or actually about a month ago when I coined the phrase, "soft bricked" is now called "clayed" because there is no such thing as a soft brick in the real world or the phone world, if a brick is soft it hasn't been baked yet in the kiln so it's still just clay, but it works in phone terms too if you have a brick you can't mold it or change anything about it, it's a brick. With clay it's still moldable and able to be worked with.
And the phone....!....pc seen just means a flash was incomplete. flashing anything successfully, even a modem, will get rid of that screen.
Granted if the kernel/rom is still incomplete it won't boot completely and be working, it'll just be "clayed" in a bootloop. So a complete odin rom is probably needed to have a working phone, but like I said flashing anything successfully will at least get rid of that screen.
dreezy1209 said:
For me I went on YouTube and found joshs' video on how to flash continuum. It was very helpful and gave me the main idea of how the process is
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
You got that URL for the YouTube video?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
McKillroy11 said:
You got that URL for the YouTube video?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=UOyx5JQ_8_I
in the video he uses talon kernel, i wouldnt suggest that because now most roms are not based on jvb which that talon is, so if yoou fallow the steps with that kernel and flash a jvh based rom it will bootloop, i suggest a kernel in this thread:http://forum.xda-developers.com/showthread.php?t=1042543
if its a jvh rom grab this one:I9000_reoriented_vG.1.2_novoo.tar
studacris said:
Which is why I'm trying to nip that in the bud from now on, or actually about a month ago when I coined the phrase, "soft bricked" is now called "clayed" because there is no such thing as a soft brick in the real world or the phone world, if a brick is soft it hasn't been baked yet in the kiln so it's still just clay, but it works in phone terms too if you have a brick you can't mold it or change anything about it, it's a brick. With clay it's still moldable and able to be worked with.
And the phone....!....pc seen just means a flash was incomplete. flashing anything successfully, even a modem, will get rid of that screen.
Granted if the kernel/rom is still incomplete it won't boot completely and be working, it'll just be "clayed" in a bootloop. So a complete odin rom is probably needed to have a working phone, but like I said flashing anything successfully will at least get rid of that screen.
Click to expand...
Click to collapse
"clayed"... I like it.. It makes a lot more sense than "soft-bricked" I myself will start to use that phrase thanks!
studacris said:
See it's this kind of stuff I'm talking about. This loose use of the term brick.
If you can recover it by any means other than jtag it's not a brick. There are no different degrees of bricking, if it's bricked it doesn't do a damn thing. Not a single solitary bit of computing, it just sits there doing nothing no matter what. Dead. A corpse.
It's either bricked or not. Just because the kernel/rom is broken and it doesn't boot properly does not mean it's bricked at all. If the bootloaders are intact and it tries to boot but fails at the kernel/rom level that is easily fixed. Throwing the term brick around in that situation, even when you add the retarded "soft brick" modifier, will just scare the **** out of a noob who just needs to remain calm and take the proper steps to have a working phone.
Click to expand...
Click to collapse
I agree, but it's a term that everybody uses. Sort of like how a ton of metal music is called "hardcore", even when it's not hardcore. Etc. I guess I just assumed that when I gave different conditions for each degree of "brick"(or clay, whatever the terminology), a noob or otherwise inexperienced person could distinguish the difference rather than see "brick" and freak out.
I dunno, I've "bricked" my phone to the point of requiring a jig before, it's super easy and nothing to get freaked out about. If anything, it's a wonderful learning experience, which is something people should be expecting when they do this sort of stuff anyways. It isn't an iPhone.
I watched the video and I don't know how to downgrade to 2.1. Also will I need to re-root my phone after going to gingerbread or the downgrade?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Superalpaca said:
I agree, but it's a term that everybody uses. Sort of like how a ton of metal music is called "hardcore", even when it's not hardcore. Etc. I guess I just assumed that when I gave different conditions for each degree of "brick"(or clay, whatever the terminology), a noob or otherwise inexperienced person could distinguish the difference rather than see "brick" and freak out.
I dunno, I've "bricked" my phone to the point of requiring a jig before, it's super easy and nothing to get freaked out about. If anything, it's a wonderful learning experience, which is something people should be expecting when they do this sort of stuff anyways. It isn't an iPhone.
Click to expand...
Click to collapse
ive done it on purpose out of curiosity and wanting to see for myself, like i mentioned earlier the phone...!....pc just means a flash was marked incomplete so a fun learning experience: Flash a kernel with odin and yank the chord halfway through the flash. you might get a screen with a pretty color followed by the phone....!.....pc screen. now flash a modem with odin and let that finish like normal, the phone...!...pc screen will no longer be there, it will still be clayed because the kernel is broken, but it wont have that screen anymore. then flash the kernel like normal and it will be fixed likje nothing ever happened. this has no risk of bricking whatsoever because there are no bootloaders involved in the flash.
ive never had to use the jig i built my button combos have always worked, i still built one cause its super easy and handy to have if i ever need it but i just never have
McKillroy11 said:
I watched the video and I don't know how to downgrade to 2.1. Also will I need to re-root my phone after going to gingerbread or the downgrade?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
if you are flashing a custom rom and not staying on stock gingerbread then it will already be rooted.
to return to stock everything (stock bootloaders also) use odin one click. http://forum.xda-developers.com/showthread.php?t=731989
to return to a stock rom but still retain the gingerbread bootloaders use this package http://forum.xda-developers.com/showthread.php?t=995143
both of those methods of returning to stock would be an out of the box unrooted stock rom.
McKillroy11 said:
I watched the video and I don't know how to downgrade to 2.1. Also will I need to re-root my phone after going to gingerbread or the downgrade?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Use odin3 oneclick downloader. That will put you back at stock 2.1
Here it is. But if you don't know how to use it. You should really learn it.
http://www.megaupload.com/?d=SBSMALFJ
here's a vid for Odin:
http://www.youtube.com/watch?v=UDtxnH4lFuk
Sent from my SGH-I897 using XDA Premium App
studacris said:
Which is why I'm trying to nip that in the bud from now on, or actually about a month ago when I coined the phrase, "soft bricked" is now called "clayed" because there is no such thing as a soft brick in the real world or the phone world
Click to expand...
Click to collapse
I agree the term "brick" is thrown around too liberally, but I was under the impression that a "soft brick" was a SOFTware problem, and a "hard brick" was a HARDware problem. I guess I was mistaken, since "hard bricks" can still be the result of software issues. (right?)
Sent from a phone inside a phone inside a KFC inside a McDonald's.
twvance said:
I agree the term "brick" is thrown around too liberally, but I was under the impression that a "soft brick" was a SOFTware problem, and a "hard brick" was a HARDware problem. I guess I was mistaken, since "hard bricks" can still be the result of software issues. (right?)
Sent from a phone inside a phone inside a KFC inside a McDonald's.
Click to expand...
Click to collapse
A hard brick occurs when the bootloaders are written improperly or gingerbread and froyo bootloaders are mixed. Completely software. If the bootloaders can't load the boot sequence you get absolutly nothing from it.
You can still recover from a hard brick with jtag, if it was a hardware problem like severe water damage there is no coming back from that at all. So I guess that's just called a broken phone.
I think I posted this in the wrong forum, I suppose I was a little confused on my phone
I have a US AT&T version of the i727 Skyrocket. I think i accidentally flashed an improper kernel:
http://forum.xda-developers.com/showthread.php?t=1369977
I didn't realize I was browsing the wrong forum *sigh*.
Anyway, when I went to reboot after installing the kernel in CWM, I get a black screen. If I hold down both volume buttons and plug in USB, I get nothing. It doesn't seem to put it in download mode. There, it doesn't get recognized in ODIN.
What are my options here? Would a "jig" actually do anything in this case? I can't tell the scenarios it can actually recover from and not.
Hard brick, its done
Jtag or send to samsung
hedpe said:
I think I posted this in the wrong forum, I suppose I was a little confused on my phone
I have a US AT&T version of the i727 Skyrocket. I think i accidentally flashed an improper kernel:
http://forum.xda-developers.com/showthread.php?t=1369977
I didn't realize I was browsing the wrong forum *sigh*.
Anyway, when I went to reboot after installing the kernel in CWM, I get a black screen. If I hold down both volume buttons and plug in USB, I get nothing. It doesn't seem to put it in download mode. There, it doesn't get recognized in ODIN.
What are my options here? Would a "jig" actually do anything in this case? I can't tell the scenarios it can actually recover from and not.
Click to expand...
Click to collapse
If it does absolutely nothing, i'd say you bricked it which is quite possible if you flashed something for another phone. I don't think a jig will do you any good, based on things i've read before. Not 100%. Maybe someone else will give you some better input.
thanks for the replies. I can't get it in to download mode at all, so I'm afraid it's hard bricked.
Are there any guides to doing the jtag repair yourself? I'm pretty tech-savvy and comfortable opening up the phone, etc. I could get my hands on a jtag unit.
I just don't want to keep bricking it and sending it out for another $50. I'd rather have a solution where I can fix it myself.
hedpe said:
thanks for the replies. I can't get it in to download mode at all, so I'm afraid it's hard bricked.
Are there any guides to doing the jtag repair yourself? I'm pretty tech-savvy and comfortable opening up the phone, etc. I could get my hands on a jtag unit.
I just don't want to keep bricking it and sending it out for another $50. I'd rather have a solution where I can fix it myself.
Click to expand...
Click to collapse
I don't know any off hand, but why would you keep bricking it?
xcrazydx said:
I don't know any off hand, but why would you keep bricking it?
Click to expand...
Click to collapse
I'd hope not to, but on my first try I bricked it. I've never bricked my Nexus S after a ton of crappy kernels. Sigh...
Doesn't look like anyone has figured out a homebrew JTAG solution.
hedpe said:
I'd hope not to, but on my first try I bricked it. I've never bricked my Nexus S after a ton of crappy kernels. Sigh...
Doesn't look like anyone has figured out a homebrew JTAG solution.
Click to expand...
Click to collapse
Well, jtag for this phone was just made possible only a month or two ago. There may be a guide somewhere, but I dunno. You flashed something from a completely different phone, any time you do that you are pretty much guaranteed a brick. Just pay attention to what you're doing, man. Read more and flash less.
xcrazydx said:
Well, jtag for this phone was just made possible only a month or two ago. There may be a guide somewhere, but I dunno. You flashed something from a completely different phone, any time you do that you are pretty much guaranteed a brick. Just pay attention to what you're doing, man. Read more and flash less.
Click to expand...
Click to collapse
Right, understandable. Lesson learned there.
I can't tell if this is legitimate or not:
http://www.jtagbox.com/2012/03/page/2/
$50 isn't too bad. Obviously doing it yourself, if you could, would be better. I'd be on the safe side though and have mobiletech (i'm assuming you know about them), do it.
Hello, so here is the story the best I can tell it. I have done quite a bit of work on Iphones, Ipods, and roms on my own phones, because of this my friends son asked if I had ever JTag'd a phone before, which I had never heard of at the time. Apparently a friend of his was trying to load a custom ROM on his Verizon Galaxy S3 and something went wrong. Unfortunatly, I have no idea what ROM he tried loading or how he tried loading it. All I do know is, there is no response on the phone at all, the screen stays black. When you plug it into the computer, the computer recognizes a device but asks for a qhsusb_dload driver. I have read that this is a hard brick, and needs Jtag service, however I have also read that it is really hard to actually hard brick a phone, and this is actually more of a soft brick. Can anyone confirm this, and is it possible that just a USB jig will work to force it into download mode? I have ordered a Jig and it should be here next week, but I wanted to ask some questions in the mean time. Thanks for your help.
pedenspeed said:
Hello, so here is the story the best I can tell it. I have done quite a bit of work on Iphones, Ipods, and roms on my own phones, because of this my friends son asked if I had ever JTag'd a phone before, which I had never heard of at the time. Apparently a friend of his was trying to load a custom ROM on his Verizon Galaxy S3 and something went wrong. Unfortunatly, I have no idea what ROM he tried loading or how he tried loading it. All I do know is, there is no response on the phone at all, the screen stays black. When you plug it into the computer, the computer recognizes a device but asks for a qhsusb_dload driver. I have read that this is a hard brick, and needs Jtag service, however I have also read that it is really hard to actually hard brick a phone, and this is actually more of a soft brick. Can anyone confirm this, and is it possible that just a USB jig will work to force it into download mode? I have ordered a Jig and it should be here next week, but I wanted to ask some questions in the mean time. Thanks for your help.
Click to expand...
Click to collapse
Good luck. That qhsusb tag denotes a hard brick.
pedenspeed said:
Hello, so here is the story the best I can tell it. I have done quite a bit of work on Iphones, Ipods, and roms on my own phones, because of this my friends son asked if I had ever JTag'd a phone before, which I had never heard of at the time. Apparently a friend of his was trying to load a custom ROM on his Verizon Galaxy S3 and something went wrong. Unfortunatly, I have no idea what ROM he tried loading or how he tried loading it. All I do know is, there is no response on the phone at all, the screen stays black. When you plug it into the computer, the computer recognizes a device but asks for a qhsusb_dload driver. I have read that this is a hard brick, and needs Jtag service, however I have also read that it is really hard to actually hard brick a phone, and this is actually more of a soft brick. Can anyone confirm this, and is it possible that just a USB jig will work to force it into download mode? I have ordered a Jig and it should be here next week, but I wanted to ask some questions in the mean time. Thanks for your help.
Click to expand...
Click to collapse
That sucks, that my friend, is a hardbrick, fixable, but its a process and tedious.
Sent from my Secret Base in Outer Space
I had the same thing happen to me. See here http://forum.xda-developers.com/showthread.php?t=1770341
I pushed a corrupt ROM and it borked. Contrary to your post, it is easy to brick this S3. I've hard bricked twice.... Just be sure the files you flash are for your variation of the S3 (ie don't flash an ATT rom onto a VZW fone) and make sure you got a good download by checking the md5.
FWIW, Josh over at MobileTechVideos.com has JTAG'd me back both times. Fair price and quick service. I believe he's the only dude in the US doing it...
Sent from my SCH-I535 using xda app-developers app
hi there, unfortunately i flash the wrong rom, and the result is the same of the first poster
what i can do? what is jtag?
i have bought a j usb someone have used it? it works?
what is "jtag?"
It's a debugging port that can be used to push firmware onto memory. Mostly used for diagnostics and initial programming since it allows debugging after the first cpu instruction.
UnEZ said:
It's a debugging port that can be used to push firmware onto memory. Mostly used for diagnostics and initial programming since it allows debugging after the first cpu instruction.
Click to expand...
Click to collapse
i have bought the jig usb, i'll try, if download mode starts, then what i should do? follow this guide? http://forum.xda-developers.com/showthread.php?t=1840030
Interested to see if you are able to get the jig to work. I have not heard of a jig working on a hard brick. Yes if you get back into download mode just start the process over with Odin
Sent from my SCH-I535 using xda premium
arkas90 said:
i have bought the jig usb, i'll try, if download mode starts, then what i should do? follow this guide? http://forum.xda-developers.com/showthread.php?t=1840030
Click to expand...
Click to collapse
Hey arkas90 did JIG work for you i am in the same boat trying to revive my s3 . Please let us all know if that works
So, as title says, I think I managed to brick my tab for good, but you never know, so I'm asking for ideas.
Basically while I was rooting it the power of the building went off, and like a dumb monkey I was rooting it with the desktop PC instead of the laptop
Now it doesn't turn on, download mode doesn't work, if I plug it on PC gives a wrong name and fails to find the drivers (that were already installed and working before). I tried removing the battery to make sure it wasn't in some weird stuck/bootloop situation, but it didn't change anything.
Other ideas? I'm willing to try more or less anything at this point
Edit:
If it helps, it is a p3110 (galaxy tab 2 7.0 wifi only)
And the only sign of life I get is by plugging it on the PC it keeps detecting for a second the cpu (OMAP4430)
If you cant get into download mode then it needs a jtag. Sad to hear. Most times it's a user flashing the wrong recovery/rom. Never power loss.
Talk about bad luck... Sadly what you have right now ia called a hard brick. Your gonna need a Jtag to bring your device back to life. You can contact certain people that offer that service for around 40.00$ I wish you goodluck.
Never power loss.
Click to expand...
Click to collapse
I thought it was because the transfer of the PDA was halted midway since the PC was turned off by the power failure. Oh well...
MistedEvo said:
Talk about bad luck... Sadly what you have right now ia called a hard brick. Your gonna need a Jtag to bring your device back to life. You can contact certain people that offer that service for around 40.00$ I wish you goodluck.
Click to expand...
Click to collapse
Seems I can't find any that do it for the p3110 here in Italy, I might have to ship it overseas, so I figure it'd be more like 75+$
Is trying to send it back to Samsung worth a try?
Hi,
i have same problem with Galaxy Tab 2 P5100 several month ago. If your device is bricked and can't be turned on in download mode best solution for you is sending it to Samsung. Because Galaxy Tab 2 it is impossible to repair it with JTAG yet. I've visited a lot of masters in my country - all said that it is unbrickable now. Also i've visited official Samsung service and they proposed to replace entire board of my tablet because it they can't repair it programmatically.
I assume you tried booting into recovery?
Any chance ODIN detects it ? Anything at all.....
DigitalMD said:
I assume you tried booting into recovery?
Click to expand...
Click to collapse
Sean_Seany said:
Any chance ODIN detects it ? Anything at all.....
Click to expand...
Click to collapse
Tried both, even on other two PCs, but no signs of life. I guess I'll just send it back to Samsung and see what happens
The_Bard said:
Tried both, even on other two PCs, but no signs of life. I guess I'll just send it back to Samsung and see what happens
Click to expand...
Click to collapse
Flashing your tab using odin didn't ruined your warranty?
what will you say to them? spilled coffee on it?
anyways good luck buddy. :good::good:
hope you have you baby smiling again
akshayjoshi1993 said:
Flashing your tab using odin didn't ruined your warranty?
what will you say to them? spilled coffee on it?
anyways good luck buddy. :good::good:
hope you have you baby smiling again
Click to expand...
Click to collapse
Samsung seems to be quite open to ignoring similar details, I'll just say "it doesn't boot up" and see.
It worked a couple of years back when I sent back a galaxy one with issues reading the external SD that would boot into a custom rom
And a clearly opened monitor that I broke trying to get the panel out to do a DIY projector ;D
I believe I hard-bricked my Galaxy S Blaze. It won't power on with or without a new battery. It won't even buzz when I plug it into the computer. I tried flashing a modified version of CM 10 for S Blaze and it flashed the boot logo, then turned off. I can't get it back on. Please help.
Thanks,
Qiangong2
Qiangong2 said:
I believe I hard-bricked my Galaxy S Blaze. It won't power on with or without a new battery. It won't even buzz when I plug it into the computer. I tried flashing a modified version of CM 10 for S Blaze and it flashed the boot logo, then turned off. I can't get it back on. Please help.
Thanks,
Qiangong2
Click to expand...
Click to collapse
Are you able to boot to anything (recovery or Odin)? If you can get it to boot at all to the other modes, it's probably just soft bricked. If the phone is completely unresponsive to the power button and you're 100% sure that it's not the battery, then yes, it's probably hard bricked. Just about the only fix for a hard bricked phone is to get it JTAG'ed.
You can buy your own setup for around 200 (http://www.cellcorner.com/xshp/unlock-phone-codes/z3x-easy-jtag-box.html), but I'd only do that if you are a developer and plan to hard brick a lot or you want to go into business for this yourself.
Your other option is to send your phone off for jtag. Here's one service: http://www.brickedmyphone.com/products/jtag-unbrick-service/ but there are hundreds of others, and even some users here on XDA that would be willing to help
**WARNING** I do not endorse the above mentioned service at all. I have never used them and cannot vouch for their credibility or honesty. Neither I, nor XDA, are responsible for the consequences of your choices or actions.
jparnell8839 said:
Are you able to boot to anything (recovery or Odin)? If you can get it to boot at all to the other modes, it's probably just soft bricked. If the phone is completely unresponsive to the power button and you're 100% sure that it's not the battery, then yes, it's probably hard bricked. Just about the only fix for a hard bricked phone is to get it JTAG'ed.
You can buy your own setup for around 200 (http://www.cellcorner.com/xshp/unlock-phone-codes/z3x-easy-jtag-box.html), but I'd only do that if you are a developer and plan to hard brick a lot or you want to go into business for this yourself.
Your other option is to send your phone off for jtag. Here's one service: http://www.brickedmyphone.com/products/jtag-unbrick-service/ but there are hundreds of others, and even some users here on XDA that would be willing to help
**WARNING** I do not endorse the above mentioned service at all. I have never used them and cannot vouch for their credibility or honesty. Neither I, nor XDA, are responsible for the consequences of your choices or actions.
Click to expand...
Click to collapse
Off Topic: Whoa! You appeared out of no where! How you been? Haven't seen you online in a while... You feeling better I guess? :silly:
xWolf13 said:
Off Topic: Whoa! You appeared out of no where! How you been? Haven't seen you online in a while... You feeling better I guess? :silly:
Click to expand...
Click to collapse
Well, without going into too much detail (it's not that i don't want to talk about it, just don't wanna thread-jack, can go into more detail in PM), I'm feeling a lot better. Got some help that I needed.
jparnell8839 said:
Are you able to boot to anything (recovery or Odin)? If you can get it to boot at all to the other modes, it's probably just soft bricked. If the phone is completely unresponsive to the power button and you're 100% sure that it's not the battery, then yes, it's probably hard bricked. Just about the only fix for a hard bricked phone is to get it JTAG'ed.
You can buy your own setup for around 200 (http://www.cellcorner.com/xshp/unlock-phone-codes/z3x-easy-jtag-box.html), but I'd only do that if you are a developer and plan to hard brick a lot or you want to go into business for this yourself.
Your other option is to send your phone off for jtag. Here's one service: http://www.brickedmyphone.com/products/jtag-unbrick-service/ but there are hundreds of others, and even some users here on XDA that would be willing to help
**WARNING** I do not endorse the above mentioned service at all. I have never used them and cannot vouch for their credibility or honesty. Neither I, nor XDA, are responsible for the consequences of your choices or actions.
Click to expand...
Click to collapse
Okay, thanks. Odin and Heimdall both don't work. It doesn't even vibrate when i turn it on. I've tried different batteries as well. Seems like it has been hard bricked
Thanks for your help though