Title. I haven't ventured far enough to flash roms yet, still running stock JI6. Is it even a remote possibility to completely brick your Vibrant i.e. no fix?
It seems like whenever someone creates a thread saying they bricked their phone, Odin always magically fixes everything.
Yes, it is possible but VERY unlikely. If I remember correctly, wesgarner bricked his.
I'm new here. I bricked mine up good. haha. I rooted and did a lagfix. It worked great, until tmo sent me the ota update. It softbricked it. So I flashed it with what I thought was a stock rom. then they sent me the update again. After poweroff it won't even turn on. No recovery menu, no download menu, no power. So, yes it is possible.
Yeah, I have bricked 2 of them while doing some things & messing up at like 2am
Anything can be bricked.
Sent from my GT-I9000 using XDA App
You can't brick it, is only a soft brick, the ones that get ''bricked'' are the ones that are hardware locked, they can't get flash back to stock, because recovery nor download mode work after the ''brick''.
Sent from my SGH-T959 using XDA App
Master™ said:
Yeah, I have bricked 2 of them while doing some things & messing up at like 2am
Click to expand...
Click to collapse
what are you doing exactly with it? it can't be fixed even flashing back to stock?
i bricked my first g1 Not my baby tho lots of hours of reading and re-reading
iynfynity said:
what are you doing exactly with it? it can't be fixed even flashing back to stock?
Click to expand...
Click to collapse
Same thing Wes was.
And nope, they couldnt be flashed back with Odin even.
smkr420 said:
i bricked my first g1 Not my baby tho lots of hours of reading and re-reading
Click to expand...
Click to collapse
Same here. I forget what I did wrong, but it was during the Donut hysteria.
Luckily, I've learned to read a but more with the Vibrant before flagging things.
-bZj
_____
-sent from my Samsung Vibrant via XDApp
cervantesjc said:
You can't brick it, is only a soft brick, the ones that get ''bricked'' are the ones that are hardware locked, they can't get flash back to stock, because recovery nor download mode work after the ''brick''.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Hw locked has a fix & You can brick this phone.
I bricked my vibrant by flashing haykuros danger SPL.... Lol. G1 days FTW!
Hardware locked vibrants are considered bricked. Happen to me twice now and had to send in for repair.
I've never seen the term bricked associated with a device like the vibrant.
Sent from my SGH-T959 using XDA App
You certainly can brick a Vibrant, even one that is not hardware locked. I did it last week. I did it by trying to create a custom Odin backup that flashed an incomplete boot loader, I think.
In any case, AFTER a successful Odin update the phone turned off to reboot, and will not turn back on. No amount of messing with it will get the phone to turn on. There is no way I can figure out how to even get Odin to work, because there is no power going to the phone. Bricked.
So, moral of the story:
Follow these rules and it's not possible:
If you have a hardware locked phone, FIX IT.
Don't flash anything for the wrong phone.
Don't accept OTAs if you're hacked.
Only flash things that others have confirmed (can be the dev).
If you're making your OWN stuff (Wes, cparekh), it's quite possible to completely screw your phone.
Related
I have locked hardware vibrant should I take the chance of installing clockwork. And flash rom's Cuz what if I get stuck in vibrant screen than I can't do anything. I bricked my last phone. By usin Odin by adb. It just froze on Odin after that there was no going back. So what should I do?
Sent from my SGH-T959 using XDA App
flameinthefire said:
I have locked hardware vibrant should I take the chance of installing clockwork. And flash rom's Cuz what if I get stuck in vibrant screen than I can't do anything. I bricked my last phone. By usin Odin by adb. It just froze on Odin after that there was no going back. So what should I do?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I personally have had no issues flashing at all. I do not have a locked vibrant but I've literally pulled the cable when in the middle of flashing with odin just to try to brick it, which thankfully I've had good luck thus far. However this is up to your discretion. If you feel competent enough to do it, then go for it. Otherwise if you feel that you'd rather not risk another brick then i'd step back.
Good Luck
Okay so I updated to JI6 from KIES. I was having some problems after the update so I decided to restore my nandroid made by ROM Manager (a backup made before the update - at JFD). I restore it, phone reboots, etc. However, now it is stuck at the "Vibrant Samsung" screen -- you know the one that comes with the T-Mobile logo appears. The odd thing is I even hear the load-up sound that plays, but the phone does not go past the Vibrant screen.
Help please?
Oh and I can still boot into recovery mode...
You sure you are waiting long enough? Mine took about 5 minutes after the firmware upgrade to get past the samsung vibrant screen. I thought it was frozen at first but I guess it takes awhile after the firmware upgrade.
This is after I did the restore from ROM Manager -- not after the firmware upgrade.
This is caused by downgrading from ji6. If you nadroid on ji6 to stock it will brick. I believe the only way to fix would be through odin. Hope it gets worked out.
Sent from my SGH-T959 using XDA App
doh >.>
Why the heck can't I get into Download Mode...
EDIT: Nevermind, got into download mode. Apparently you dont hold power key for DM.
Okay i ll make sure to never help you again. Have fun with your attitude and bricked phone.
Sent from my SGH-T959 using XDA App
Huh? What did I do to you =O
Anyway, I think my phone is really bricked now. Can't get into download mode.
fcbarca17 said:
Okay i ll make sure to never help you again. Have fun with your attitude and bricked phone.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Ha ha he did not even say anything bad xD
DarkAgent said:
Huh? What did I do to you =O
Anyway, I think my phone is really bricked now. Can't get into download mode.
Click to expand...
Click to collapse
Ever get it fixed, im having a similar problem..
Hello guys,
I have problem with my friends facinate.
I don't know what he did but when I tried to boot this phone, I see those logo.
I can't get into recovery mode or odin mode.
Please help me guys~!
brozroy said:
Hello guys,
I have problem with my friends facinate.
I don't know what he did but when I tried to boot this phone, I see those logo.
I can't get into recovery mode or odin mode.
Please help me guys~!
Click to expand...
Click to collapse
looks like he tried booting captivate firmware on his fascinate
nitsuj17 said:
looks like he tried booting captivate firmware on his fascinate
Click to expand...
Click to collapse
How can I get into odin3
Make sure you have the fascinate drivers.
Pull the battery.
Connect phone via USB to your computer.
Hold volume down button then press power.
That should boot it into download (Odin) mode
Sent from my SCH-I500-Fascinate using XDA App
K40 said:
Make sure you have the fascinate drivers.
Pull the battery.
Connect phone via USB to your computer.
Hold volume down button then press power.
That should boot it into download (Odin) mode
Sent from my SCH-I500-Fascinate using XDA App
Click to expand...
Click to collapse
It works on my phone. But not on this phone. Is there any other way?
Thanks
Only other way, that I am aware of, is to boot holding the volume down button with the battery in then connect to USB after the downloader launches.
Did your friend possibly install CWM? If so try holding both volume buttons down and going through Clock Work Mod.
Sent from my SCH-I500-Fascinate using XDA App
Also if you can boot using the second method but don't have CWM installed you can possibly add another ROM named update.zip to the root of the sdcard and use the standard recovery launcher.
This information may be innacurate I come more from Palm Pre tweaking, but I believe that's what I read.
Sent from my SCH-I500-Fascinate using XDA App
I have never seen a Galaxy S phone not be able to get to download mode.. but I think I've only seen one other person dumb enough to flash a Capitvate rom / kernel onto a Fascinate..
That being said, if removing the battery (don't put it back in), plugging in USB and holding volume-down doesn't bring up download mode, you're screwed. The phone obviously needs to be made inoperable before returning. An easy way to do that would be to disconnect the cable to the screen. Alternatively, and much more dangerously, you could microwave if for a few seconds at a time until it dies.
namebrandon said:
Alternatively, and much more dangerously, you could microwave if for a few seconds at a time until it dies.
Click to expand...
Click to collapse
Are you serious?
Inoperable would be a last ditch effort in my opinion. Mistakes happen. These are the kind of mistakes that not only the OP and his friend learn from but also the community as a whole. If we can get him through this we also learn how to help others that make similar mistakes.
Modding / hacking whatever you wish to call it comes down to learning. We learn what works and what doesn't and we try to help others not make those mistakes. I prefer to try everything before nuking a phone that can be recovered.
Sent from my SCH-I500-Fascinate using XDA App
K40 said:
Inoperable would be a last ditch effort in my opinion. Mistakes happen. These are the kind of mistakes that not only the OP and his friend learn from but also the community as a whole. If we can get him through this we also learn how to help others that make similar mistakes.
Modding / hacking whatever you wish to call it comes down to learning. We learn what works and what doesn't and we try to help others not make those mistakes. I prefer to try everything before nuking a phone that can be recovered.
Sent from my SCH-I500-Fascinate using XDA App
Click to expand...
Click to collapse
Thanks. I hope there is other way to flash it.
Keep trying holding both volume buttons down while powering up. If you can get into the default recovery or the download interface this can be corrected.
Sent from my SCH-I500-Fascinate using XDA App
namebrandon said:
I have never seen a Galaxy S phone not be able to get to download mode.. but I think I've only seen one other person dumb enough to flash a Capitvate rom / kernel onto a Fascinate..
Click to expand...
Click to collapse
Yeah. I know. He is very young kids. I think he didn't even read title of thread.
Sorry am at work, any progress on getting the downloader to launch?
Sent from my SCH-I500-Fascinate using XDA App
I would gather he is at the vzw store signing into the kiosk right now and waiting for his name to be called.
good day.
Was just trying to take the small amount of information I have acquired and help the person out.
Sent from my SCH-I500-Fascinate using XDA App
K40 said:
Sorry am at work, any progress on getting the downloader to launch?
Sent from my SCH-I500-Fascinate using XDA App
Click to expand...
Click to collapse
Still stuck in att boot logo
brozroy said:
Still stuck in att boot logo
Click to expand...
Click to collapse
To be honest, you cant fix it.
You can get it to boot once again if you can ever get it back into DL mode, but the phone wont work again. Not until we get a leak for a complete odin package, and that isnt gonna happen anytime soon.
I posted on my odin thread and pretty much any other thread i have done that you should not flash any other galaxy s device's firmware to the fascinate, they are not interchangeable like that. I hope he has insurance on his phone.
fallingup said:
To be honest, you cant fix it.
You can get it to boot once again if you can ever get it back into DL mode, but the phone wont work again. Not until we get a leak for a complete odin package, and that isnt gonna happen anytime soon.
I posted on my odin thread and pretty much any other thread i have done that you should not flash any other galaxy s device's firmware to the fascinate, they are not interchangeable like that. I hope he has insurance on his phone.
Click to expand...
Click to collapse
Thank you guys. I'll just tell him. Good night
Sent from my Android
I can't seem to find a thread to help me restoring my nexus s back to a factory state.
I did flash via adb, but I am having issues with my phone, so I want to re flash.
Thanks for your help
Matt
Code:
fastboot oem lock
fastboot oem unlock
(then lock again if you want)
That will erase EVERYTHING. Then you can flash clockwork back. Then flash one of the stock ROMs (found here on the forums somewhere or from ROM Manager). Basically back to stock. (With custom bootloader). Which you can also get rid of, I just don't remember how
Why not just flash the newest stock from samfirmwares via Odin? Semms quicker and easier to me, but ... are there any disadvantages?
fallenguru said:
Why not just flash the newest stock from samfirmwares via Odin? Semms quicker and easier to me, but ... are there any disadvantages?
Click to expand...
Click to collapse
I've always considered Odin to be a last resort kind of thing. You really shouldn't Odin unless everything else doesn't work and your phone is near screwed. The reason being, should anything go wrong during the Odin flashing, your device runs a very high risk of permanently bricking and the past the point of no return. Its probably the only way of permanently bricking your Nexus.
Sent from my Nexus S using XDA App
Hmm, ok.
I've always used Odin for my Samsung i5700 (Galaxy Spica), mainly because there is nothing else for it. It's always seemed extremely stable and lightweight to me, never mind the factory floor look.
AFAICT Odin can only brick your phone if your computer explodes at exactly the right time (i. e. while it's flashing the bootloader) - no idea if fastboot has additional safeguards or something.
An inexperienced user has a much better chance of screwing up in a multi-step restore, so if the objective is to restore to an out-of-the-box state then I'd still rather use Odin, personally. (For modding parts of firmware and comfort, fastboot beats it hands down.)
I came from the Vibrant, so I see where you're coming from. But like you said, an inexperienced user has a better chance of screwing it up. That's why I recommended the non-odin method to the OP. To each his own I guess. Both methods will take you to the same end result, one which is slightly less of a hassle. I just cringe everytime I use Odin in fear of windows crashing or Odin crashing since previous versions were known to be relatively unstable. Or some other mishap like kicking the USB cable while flashing.
Sent from my Nexus S using XDA App
I just used odin and ROM from here
http://forum.xda-developers.com/showthread.php?t=947950
Restore 2.3.1 through CWM
http://forum.xda-developers.com/showthread.php?t=884093
download the nandroid backup in that thread and restore using cwm. then do a factory reset and lock bootloader with "fastboot oem lock". that's what i did.
peeturr said:
I came from the Vibrant, so I see where you're coming from. But like you said, an inexperienced user has a better chance of screwing it up. That's why I recommended the non-odin method to the OP. To each his own I guess. Both methods will take you to the same end result, one which is slightly less of a hassle. I just cringe everytime I use Odin in fear of windows crashing or Odin crashing since previous versions were known to be relatively unstable. Or some other mishap like kicking the USB cable while flashing.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
while i can agree that odin is not very... user friendly in the sense of many errors. it is very slim chance of it causing a brick. and why not just use heimdall? its the open source solution to odin
Check the Q&A section. Yet another nexus S perma-bricked using Odin. In this case he used the wrong files (i9023 instead of i9020) to flash. Anything could happen. If you could avoid it, you really should because Odin messes with very sensitive files.
Sent from my Nexus S using XDA App
peeturr said:
I've always considered Odin to be a last resort kind of thing. You really shouldn't Odin unless everything else doesn't work and your phone is near screwed. The reason being, should anything go wrong during the Odin flashing, your device runs a very high risk of permanently bricking and the past the point of no return. Its probably the only way of permanently bricking your Nexus.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
What permabrick using odin, never happen.
Sent from my SPH-D700 using XDA App
U can't permbrick your phone with odin
Sent from my Nexus S using XDA App
demo23019 said:
U can't permbrick your phone with odin
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Try loading i9023 Odin files onto your i9020.
Sent from my Nexus S using XDA App
peeturr said:
Try loading i9023 Odin files onto your i9020.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
dont do that that'll mess up with the phone's functionality because it'll start acting like a 9023 when its a 9020.
Maybe the procedure here may help you.
http://theunlockr.com/2011/01/20/how-to-unroot-the-nexus-s/
Actually, I'm quite sure you can brick phones with Odin, if you try. Flashing the wrong firmware (or any other random bucket of bits) certainly works, as you can see. But I'm curious, how would fastboot have prevented this?
Sorry to the OP, I neither wanted to derail your thread nor start a holy war, just offer another option.
well it goes without saying to not use another phones firmware... but using the correct firmware on the correct phone odin has a small chance at bricking.. and thats only when your flashing boot.img and sbl.bin. he shouldnt be using the pit as odin pulls it from the phone. and there is almost no reason to repartition the device.
nabiladeeb said:
Maybe the procedure here may help you.
Click to expand...
Click to collapse
Thanks, really helpfull!
I have a problem;Do I have a I9020 or I9023?
When I look in settings-about phone it is Baseband version I9023XXKB1, but if I look in the fastboot mode I find Baseband version I9020XXKB1.
Witch one is correct?
Please help,
Thank you
peeturr said:
Try loading i9023 Odin files onto your i9020.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
shame on someone using a rom not even made for there phone but still i dont see how that will perm brick your phone when you can still access download mode
Guys I still don't believe it but I did very well this evening I just managed to brick my device by copying some avi and wmv files from the external SD-Card to my internal storage. How did I do that? I have no f...... clue. The phone froze, I waited almost half an hour but nothing happened. So I finally decided to pull the battery and restart the phone. And what did I get? I phone nicely stuck at the boot logo. Ok I thought, no biggie. Let's try to clean cache and dalvik cache, this action had helped in the past when the phone had been stuck at the boot logo. But no, it did not help at all. Then I thought ok, before I restore my nand backup I can still try to reflash the kernel. And I think that killed my phone. After the kernel had successfully been flashed (according to the log in CWM) I tried to reboot but nothing worked anymore. I could not even boot into CWM recovery. Hm, that's not good but now I could still try reflashing the rom using pc odin because the download mode still worked (in fact it still works). But it does absolutely nothing. It does not even start to flash. So bang, there it is, my own full brick. Huray. Off to the service center I go. At least I always paid attention not to increase the flash counter/ trigger the red triangle. So since the phone is completely dead I am optimistic that they should not be able to proof that my phone was rooted (fingers crossed).
In case you are interested, my rom was LRQ, my kernel was the latest version of the PhilZ kerne with it's touch recovery.
did you check to see if the drivers on the computer are properly installed? I'm tinking it might be a case of pc not finding the phone.
or maybe you had some bad blocks since the days of unsafe kernels
altae said:
Guys I still don't believe it but I did very well this evening I just managed to brick my device by copying some avi and wmv files from the external SD-Card to my internal storage. How did I do that? I have no f...... clue. The phone froze, I waited almost half an hour but nothing happened. So I finally decided to pull the battery and restart the phone. And what did I get? I phone nicely stuck at the boot logo. Ok I thought, no biggie. Let's try to clean cache and dalvik cache, this action had helped in the past when the phone had been stuck at the boot logo. But no, it did not help at all. Then I thought ok, before I restore my nand backup I can still try to reflash the kernel. And I think that killed my phone. After the kernel had successfully been flashed (according to the log in CWM) I tried to reboot but nothing worked anymore. I could not even boot into CWM recovery. Hm, that's not good but now I could still try reflashing the rom using pc odin because the download mode still worked (in fact it still works). But it does absolutely nothing. It does not even start to flash. So bang, there it is, my own full brick. Huray. Off to the service center I go. At least I always paid attention not to increase the flash counter/ trigger the red triangle. So since the phone is completely dead I am optimistic that they should not able to proof that my phone was rooted (fingers crossed).
In case you are interested, my rom was LRQ, my kernel was the latest version of the PhilZ kerne with it's touch recovery.
Click to expand...
Click to collapse
I have never considered the "hex-patched" kernels to be safe...
jeriz said:
did you check to see if the drivers on the computer are properly installed? I'm tinking it might be a case of pc not finding the phone.
or maybe you had some bad blocks since the days of unsafe kernels
Click to expand...
Click to collapse
Yep. I don't think the drivers are the problem since the phone is recognized. But it does not start to flash. It simply does nothing and the phone stays in download mode forever.
Entropy512 said:
I have never considered the "hex-patched" kernels to be safe...
Click to expand...
Click to collapse
this in itself is a huge statement
altae said:
I could still try reflashing the rom using pc odin because the download mode still worked (in fact it still works). But it does absolutely nothing. It does not even start to flash.
Click to expand...
Click to collapse
This is diferent... not even start to flash...
Sent from my GT-P3110 using Tapatalk 2
Entropy512 said:
I have never considered the "hex-patched" kernels to be safe...
Click to expand...
Click to collapse
It seems that remaining on Gingerbread (until official JB) for the moment is the best thing for people who do not have a warranty for their Note.
Many people confuse superbrick (phone dead right away, no life even if you plug a charger) and other bricks. This is just an unfortunate other brick not related in any way to emmc described one. Good luck at RMA
Also, copying big video to your sdcard is a good way to kill it. Old i9000 thread was popular with that
Sent from my GT-I9100 using Tapatalk 2
Was running Paranoid Android
Tried to restore the Note back to the latest UK stock ICS ROM via ODIN
Forgot to wipe/davlik before hand
then got stuck in boot loop
more boot loops
Then tried flashing a rooted GB rom in ODIN
stuck now on the Samsung Note boot screen occasionally looping.
Then tried flashing an original non-rooted GB rom in Odin
got stuck on Data.img
Then tried again and it stuck on FACTORYFS wont even get passed this.
Took battery out, then back in...
Now the screen shows three images and the message
firmware upgrade encountered an issue
Now with the Samsung Repair centre in Eastbourne and they are failing to be able to do anything...they still have my NOTE:crying:
Entropy512 said:
I have never considered the "hex-patched" kernels to be safe...
Click to expand...
Click to collapse
Sure, you can theorically miss the binary check in rare circumstances. But this is just "an other brick" without any common relation typical to described emmc brick: no wipe, no flash, and mainly no right away (or even) complete dead phone
Sent from my GT-I9100 using Tapatalk 2
@ Entropy. Even guy above Phil3759 his bricked his note starting from PA which has a "safe" kernel, and eventually superbricking just useing PC Odin (long time considered safe). No wipes involved. Anyway, is Tungstwenty's detection method flawed for stock ICS kernels? Or is there are problem changing the offending byte from a 1 to a zero
Sent from my GT-N7000 using xda app-developers app
At least this brick has made me decide to leave my note well alone, after flashing roms practically daily for the last month or so, I have become insanely addicted to changing roms...once i get the Note back from the Sammy Service place, I am sticking with stock and wait till the official JB update arrives, which looks fantastic.
As it states on all these roms flashing custom roms at your own risk, thus its my own fault, finger crossed it can be sorted.
You can brick any phone, it happens, yes. Superbrick related to emmc bug occurs under special circumstances with typical symptoms.
Binary patching kernels, in theory, if you happen to have duplicate binary code or different, you could miss it. But, as far as i know, and for all manual checks i did, it never happened...
Sent from my GT-I9100 using Tapatalk 2
Since this is not the usual EMMC brick, what is the diagnosis? Just so it can be prevented/avoided in the future
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
Markuzy said:
Since this is not the usual EMMC brick, what is the diagnosis? Just so it can be prevented/avoided in the future
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
I have no clue. And since the phone is now completely dead (even download mode does not work anymore) it's kind of hard to examine it. So I would say we will never now what exactly bricked my phone.
As i said, it is really non recommended to use your internal sdcard for regular heavy write operations like videos. It will be corrupted at a certain point. On the i9000 this used to be a way for some to get warranty. Phone stuck often after a continuous write/wipe overnight
But this is not the superbrick. And one day, all your phones will brick. That's flash storage
Sent from my GT-I9100 using Tapatalk 2
altae said:
I have no clue. And since the phone is now completely dead (even download mode does not work anymore) it's kind of hard to examine it. So I would say we will never now what exactly bricked my phone.
Click to expand...
Click to collapse
I have read about this before. First can't flash with PC Odin. Then recovery mode goes, then download mode and finally dead phone. Friggin' Samsung
Sent from my GT-N7000 using xda app-developers app
shoey63 said:
I have read about this before. First can't flash with PC Odin. Then recovery mode goes, then download mode and finally dead phone. Friggin' Samsung
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
If you read across HTC and other forums, you'll see so much bricks and unhappy people. Why blame Samsung, there will be always faulty devices and unhappy unfortunate people
Sent from my GT-I9100 using Tapatalk 2
Yeah, you're right. Even PC Nand causes grief. Just hoped a Company on the cutting edge of technology like Samsung would have been able to resolve such problems.
Sent from my GT-N7000 using xda app-developers app
I would better trust seagate or corsair to push it further. Samsung HDD always failed on me. Ditched them long ago
Sent from my GT-I9100 using Tapatalk 2
---------- Post added at 11:40 AM ---------- Previous post was at 11:35 AM ----------
By the way, for people that want to know more about binary patching kernels, read here, it is worth it
http://forum.xda-developers.com/showthread.php?p=29609295
Sent from my GT-I9100 using Tapatalk 2