I just saw that my kies mini offered an update for the phone. I entered debugging mode and did the upgrade. The phone was rooted previously, was running 2.1. The kies mini said that upgrade was complete and i should wait for the phone to completely reboot and turn back on. the phone never came back on and now i can't turn it back on to flash it back to stock. Please help anyone. won't light up or turn on or enter any modes.
Get Odin up on your computer plug in the usb cord on the computer 1st
Remove the battery hold down the volume up and down button and plug in the phone see if it comes up and recognizes. Look in the stickies there are a lot of fixes in there as well. worse case you will need a Jig Look in the stickies for that as well ppl here are selling for 8 bucks
So i made a jig and tried that. Still not turning on. anyone got any other ideas i could try. I think this thing is truely bricked.
simple solution
Go to this addy: http://forum.xda-developers.com/showthread.php?t=954509
It is Baywolf's AIO Toolbox 2.5 do all the steps I describe below and it will restore it back
To Eclair 2.1.1
First though keep you sim and SD card in, pull the battery, open up the program, connect your USB cable to the phone, then put the battery back in! Baywolfs program will detect it, you'll see a port yellow color appear, you now can do a restore, click the flash to stock button, and click pit, use his drop-down list, its already provided, then hit the PDA button, use the tar file he again provided, now its ready, hit the start button, and It will re-flash it back to Eclair 2.1.1 with 0 defects, its an awesome program, and this was the only program, that got me up and running, ODIN and Heimdall's wouldn't respond, but this one saved my ass! trust me, I was in the same scenario, your in! I now have axura 2.3.1.0 up and back running, and I got into that delimna by trying to downgrade a modem, and ODIN totally hosed me up!
Good Luck
Probably got an sbl.bin brick...won't be able to odin.
Whats a sbl.bin brick? does it mean it's done for?
bump 0.o bumpity bumps
I'm in the same boat. A sbl.bin (or boot loader) brick is when the phone is bricked due to a faulty boot loader. The only way to fix it is to have it serviced by someone with a jtag (local repair shop or Samsung). The average repair shop will charge around $50. I'm still trying to find out what Samsung will charge if they determine the phone's warranty is void for some reason.
Related
I odin to KA6 from KA5, including the sbl.bin. When I odin from KA6 to KA7 using the stock ROM, odin hanged at transfering sbl.bin. After waiting for 10 minutes or so, I have to disonncect, remove/reinsert the battery and reboot. The dreaded phone-dotted line-computer with an exclamation point appeared. I tried all the manuvers I can find on the forums but failed to get to the download mode screen. I was desperate and called T-mobile. The tech rep instructed me how to "master reset" the phone, without success. The rep transfered me to Samsung tech support. I was instructed to to the "master reset" a few time without success. I was transfered again to a second level Samsung tech support. I waited for nearly 30 minutes without reaching a human being. I hanged up and called T-mobile again. I was finally offered a replacement. After than, I tried again all the button/battery/usb adapter combinations without being able to get past the phone-computer-exclamation point screen. As the last resort, I tried flashing KA6 with Odin 1.3 in this "brick" mode. Surprisingly, Odin recognised the phone and added a modem port. I was successful in flashing KA6 without seeing the downlaod mode screen. I then flash KA7, again successfully. I just wish to report this for the reference of anybody encountering a similar situation. The new sbl.bin in KA6 may have altered the behavior of the bootloader so that the phone will be automatically be put in download mode if anything goes wrong. That essentially makes the vibrant unbrickable. Just my guess...
chtse53 said:
I odin to KA6 from KA5, including the sbl.bin. When I odin from KA6 to KA7 using the stock ROM, odin hanged at transfering sbl.bin. After waiting for 10 minutes or so, I have to disonncect, remove the battery and reboot. The dread phone dotted line computer with an exclamation point appeared. I tried all the manuvers I can find on the forums but failed to get to the download mode screen. I was desperate and called T-mobile. The tech rep instructed me how to "master reset" the phone, without success. The rep transfered me to Samsung tech support. I was instructed to to the "master reset" a few time without success. I was transfered again to a second level Samsung tech support. I waited for nearly 30 minutes without reaching a human being. I hanged up and called T-mobile again. I was finally offered a replacement. I tried all the button/battery/usb adapter combinations without success getting anything beyond the phone-computer-exclamation point screen. As the last resort, I tried flashing KA6 with Odin 1.3 in this "brick" mode. Surprisingly, Odin recognised the phone and added a modem port. I was successfully in flashing KA6 without seeing the downlaod mode screen. I then flash KA7, again successfully. I just wish to report this for the reference of anybody in a similar situation. The new sbl.bin may have altered the behavior of bootloader so that the phone will be automatically be put in download mode if anything wrong happens. That essentially makes the vibrant unbrickable. Just my guess...
Click to expand...
Click to collapse
wrong section for posting this
@birgertime....this sounds like what happened to you lol
Someone on the General thread had this happen also.. instead of anything working for the soft brick, when he plugged his phone in with ODIN open it brought up a COM port and he finally said "well, I'll try to flash it anyway" and it went.
Good "Need to Know" Info
I had a similar experience. I flashed KA7 and needed to flash another rom, so I went about flashing voodoo via ODIN and it failed and I was stuck at that screen.
I was freaking out a little because I couldn't get into download mode (even tried my jig).
Throughout the whole process I did notice ODIN recognized my phone as if it was in DL mode, which I thought was a little strange.
Anywho after trying everything I decided to try again. So I flashed the kernel again (in the phone ! pc screen) and it worked...
Sooooo...maybe the secondary bootloader allows you a way out if you screw up a flash............
jmcghee1973 said:
Sooooo...maybe the secondary bootloader allows you a way out if you screw up a flash............
Click to expand...
Click to collapse
or maybe it sucks worse than before and is easier to brick
I'd prefer your way though
i had the same thing hapopen to me today . odin hanged ,pulled battary out and dload mode shows phone dot computer icon , plugged in cable and started odin and it showed com port and reflashed it ..worked.
maybe that's the new download mode? lol
Sent from my SGH-T959 using XDA App
iynfynity said:
maybe that's the new download mode? lol
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
It's not. I had a similar experience as some of the others in this thread, but it seems that it is some sort of extra failsafe mode. Because I could NOT get into download mode when this happened.
Is there any special reason you were using ODIN? ClockworkMod seems a far more reliable flashing method than Kies (Mini) or ODIN IMO. I only use ODIN when I can't use ClockworkMod. I like to think I have avoided many (soft)bricks this way. A co-worker of mine bricked his phone by using ODIN with a intermittently connecting USB cable, had he used ClockworkMod instead he likely would have been fine since there's no cable involved. This is an attempt to prevent future bricks, nothing more. Thankfully, I was able to fix it for him.
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
I had the same issue. My phone would not boot or get into download mode so it wouldn't get recognized by Odin or ADB. All I could do it get the phone, exclamation point, computer graphic. After a ridiculous combination of things tried, I was able to get it to download mode by unplugging USB and battery out. Then while holding down volume buttons, plug in the USB cable. This [finally] allowed me to get back to download mode. Hope it helps.
i had my phone rooted with Super Clean 2.8 and tried to flash the stock EB01 Odin from here http://forum.xda-developers.com/showthread.php?t=977493
the phone took a very long time to go through the steps of Odin and got stock at recovery.bin for over an hour then it "failed" now the phone will not turn on or charge or even go into download mode
not sure how to get the phone into download mode manually sorry i always use the power menu built into Super Clean
is my phone bricked?
please help
Nah, you should be able to retry.
1. Take your battery out.
2. Hold down "Volume down" while plugging the USB cable into your phone (and the computer of course).
3. Retry the Odin package. It shouldn't take more than 10 or so minutes (from what I've heard, mine have never taken longer than about 3.
if that doesnt work you may need a jig its not hard to make one or you can buy online just search in the forums here for jig it should come up
i just recovered from a soft brick via home made jig telus fascinate same as vibrant (U.S.)
thank for the help
thanks for the help but my phone will not boot in to download mode i have tried time and time again and nothing comes up on the screen
i may just take the phone to Verizon after work today i have the insurance so they should replace it for free
attempt to bring up download mode, then check odin to see if a yellow light shows up. Sometimes the download mode logo can disappear, however the phone is still able to flash.
Good luck.
went to the Verizon store they are sending me a replacement phone for free
it always helps to have the extended warranty
and i have all my apps back up through titanium backup so it should not take long to get it all up and running again
1st time i ever bricked a phone in 3 years of running custom roms
thanks for the help guys
I think you had an hardware failure. Not that I've read ever thread on every board about the Fascinate, or that I've only been reading for two months, but I do read multiple boards daily and this would be the first hard brick I've read about.
Glad the insurance got you a new phone.
Bought a phone off a guy on craigslist, and sold it to me broken. He said he bricked it when he tried backing up android (was probably going to install a custom rom).
The phone turns on and powers on. It gets to the S screen, then goes black. The phones keys stay lit up and it vibrates every 5 minutes or so.
Not sure what the hell he did, but I feel its gotta be an easy fix.
Any advice? Will buy beers, or a sodas if your underage for the helper
http://forum.xda-developers.com/showthread.php?t=1047087
Just odin back to stock...real simple.
It sounds like a partitioning brick personally. Try using an appropriate PIT and repartitioning using ODIN 1.82 and a valid firmware. If you can't figure it out with conventional flashing, I can always JTAG that phone and have it back to normal just PM me if you need that done.
I am on Cyanogen Mod 7 with my Vibrant and was attempting last night to do a factory data reset on my phone through the menu screen. The phone didn't seem to like me attempting to do that and now every time I boot, no matter which button combination I try I can never get past the black Samsung Vibrant boot-up splash screen.
Is there anything I can do to reset my phone somehow? I've searched the forums and google and can't find anyone with quite my same problem.
Thanks for any help that can be offered,
Brian
Hi Brian,
Since you factory reset the phone, then you don't care about your data at this point? If that is the case, then just boot back into recovery with the appropriate key combos and reflash CM7. You might have to do it twice and don't forget to wipe while you are in there.
See here for Key Combos and another user's CM issue.
I have tried both methods (Froyo and Gingerbread bootloaders) and neither return me back into recovery. If I try the gingerbread method I just reset back to the Samsung screen every 10 seconds or so. If I try the Froyo method, nothing actually happens, it just stays there at the Samung Screen and does nothing.
You are correct in that I don't care about my data at this point.
Thanks,
Brian
Could always try Odin.
Make sure you have ODIN OPEN with admin privileges!
1.) Take off your back cover, remove your sim & mirco sd card.
2.) Remove your battery.
Make sure you have the USB plugged into your PC but NOT your phone!
3.) Hold the volume buttons.
4.) Put the battery in.
5.) Put the USB in.
You don't necessarily need the download mode image to be present. As long as you are getting the COM ID to light up yellow in ODIN, just flash back to stock like normal.
Click to expand...
Click to collapse
Then reinstall CM from scratch. Gotta go for now but I'll check in later on.
Got it up and running late last night. Thanks so much for your help. Was never quite sure what ODIN was but now that I see how it works, it makes sense that it's the fallback plan for people that have done dumb things to their phone like I did.
Thanks again,
Brian
Yep. Odin has saved my bacon more times than I can count.
Sent from my SGH-T959 using Tapatalk 2
i was trying to root a phone for someone and after odin completed it said it had failed.
the phone is a telus samsung t959d running froyo.
I followed the instructions from (I would post the url for the link but i am not allowed to.)cyanogenmod's wiki, after it failed I rebooted the phone and it got stuck on the screen in the attached pic. I have tried to boot back into download mode to no avail. From the screen it's stuck on I cannot get any tool to register the device as being present, adb, heimdall, zdiag, etc... I even tried fastboot out of desperation.Before I used odin I tried to get the phone to boot into the bootloader but it only ever went to either recovery or a normal boot and I tried every button press combo I could think of and found and nada.
Even running adb reboot bootloader just made the device boot normally. I think that if I could get it to boot to fastboot usb i could then try fastboot. I am new to rooting devices and have successfully rooted my HTC EVO3D and got s-off and simlock removed for any carrier. So I do know how to follow instructions properly, why flashing the recovery.bin failed I don't know and every fix I seem to find says BOOT TO DOWNLOAD MODE. if I could do that I wouldn't be having this problem lol. Anyway can someone please help me figure this out. Thanks. ANd if you need any further info please let me know. I don't want to have to give my friend my phone due to a software issue.
And YES I did pick PDA not anything else.
machv5 said:
i was trying to root a phone for someone and after odin completed it said it had failed.
the phone is a telus samsung t959d running froyo.
I followed the instructions from (I would post the url for the link but i am not allowed to.)cyanogenmod's wiki, after it failed I rebooted the phone and it got stuck on the screen in the attached pic. I have tried to boot back into download mode to no avail. From the screen it's stuck on I cannot get any tool to register the device as being present, adb, heimdall, zdiag, etc... I even tried fastboot out of desperation.Before I used odin I tried to get the phone to boot into the bootloader but it only ever went to either recovery or a normal boot and I tried every button press combo I could think of and found and nada.
Even running adb reboot bootloader just made the device boot normally. I think that if I could get it to boot to fastboot usb i could then try fastboot. I am new to rooting devices and have successfully rooted my HTC EVO3D and got s-off and simlock removed for any carrier. So I do know how to follow instructions properly, why flashing the recovery.bin failed I don't know and every fix I seem to find says BOOT TO DOWNLOAD MODE. if I could do that I wouldn't be having this problem lol. Anyway can someone please help me figure this out. Thanks. ANd if you need any further info please let me know. I don't want to have to give my friend my phone due to a software issue.
And YES I did pick PDA not anything else.
Click to expand...
Click to collapse
I kept reading other threads and sadly I din't pully the battery first before disconnecting the usb and repartition may have been checked as I see that it does the as default for my version. Also i turned off ODIN as I was hoping a reboot of my computer might help. I will keep trying to find an answer till someone gets back to me. this post may not even show up if I can't do a second post if no one has replied first.
Everyone was a nub at one time wasn't it FUN hahahahahaha sob cry
machv5 said:
I kept reading other threads and sadly I din't pully the battery first before disconnecting the usb and repartition may have been checked as I see that it does the as default for my version. Also i turned off ODIN as I was hoping a reboot of my computer might help. I will keep trying to find an answer till someone gets back to me. this post may not even show up if I can't do a second post if no one has replied first.
Everyone was a nub at one time wasn't it FUN hahahahahaha sob cry
Click to expand...
Click to collapse
I tried a jig and that didn't work. There must be some way of getting the device to give up on completing a task i no longer can give it due to ODIN being shut off.
Why is it that the "how to root/unlocks" never have the "if x fails then do these steps etc..." Had the how to had "pull the battery before disconnecting USB and don't reset or shut off ODIN" I wouldn't be in this mess. I realize that it's user beware but a few important steps like that in case of a fail would go a long way to you guys not shaking your heads. Instead of "silly nub hahahahahaha". No offence but I get that a lot and try to remember that when I teach someone how to use a computer. I am new at phones not at everything.
Further Developments Please can someone help?
I was giving someone a new memory card and they had a Samsung SGH-I896 it has an EB575152VA battery and the one I have the T959D has an EB575152VU battery. I exchanged my battery for hers by accident somehow and when I plugged my phone in it didn't go to the phone triangle computer logo screen it booted to recovery and said it couldn't charge the battery and kept rebooting to recovery. I got my battery back and it booted back to the phone triangle computer logo again. Grrrr....
The other thing I saw while the recovery screen was an error message that said
Code:
E:/data/fota not accessible
(may not be 100% accurate I don't have the battery to check right now but can get it again if need be) anyway I now see that there may be some light at the end of the tunnel. i have the correct stock firmware for the device I tried flashing it while in recovery but the phone kept rebooting before anything got done. My question is how can I get the dang phone to stop asking for Odin and go to recovery so I can flash stock firmware and ROM back to it? As I cannot as far as I know give it what it wants because I reset Odin and nothing seems to see that the phone is connected to the computer. I am going to try the other battery on a full charge to see what that does.
I am new at all this and want to get it fixed. I cannot afford to send it off to a service center and besides that I want to do it myself as I want to become a developer and droid technician. I would gladly donate to anyone but am still trying to get Google to accept my pay-as-you-go credit card and I don't have PayPal either. Which is really frustrating when it comes to giving back. I posted a Q&A on how to without PayPal or CC but as of the last time I checked no one has gotten back to me about it.
The CyanogenMod guide is flat out WRONG. I've tried to change it, but anything I do is reverted in an instant. I also tried to use it to install the ROM only, ended up bricking my phone and it took me hours to unbrick. That's how I became acquainted with XDA.
So, to get this straight:
1. you're using the stock USB cable
2. you remove the battery
3. you hold volume down
4. you plug in the usb cable
5. after a few seconds, you release volume down
6. the screen does not display a yellow triangle with an android
Posted from my Galaxy Tab with CM10
MultipleMonomials said:
The CyanogenMod guide is flat out WRONG. I've tried to change it, but anything I do is reverted in an instant. I also tried to use it to install the ROM only, ended up bricking my phone and it took me hours to unbrick. That's how I became acquainted with XDA.
So, to get this straight:
1. you're using the stock USB cable
2. you remove the battery
3. you hold volume down
4. you plug in the usb cable
5. after a few seconds, you release volume down
6. the screen does not display a yellow triangle with an android
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
That is correct. If you think that my idea below is a bad one or if I downloaded the wrong firmware package please let me know and /or you have a fix that will work? ty
I have though come up with an idea that may work. I am going to charge the "wrong" battery in erm the right phone lol and then use it to trick the device into booting into recovery instead of the cellphone triangle computer (CTC, for want of a better acronym) The I896 battery ends in a V not an ? (sorry can't rem don't have it on me) from the I896 model I think it is, plugging it into USB with the power off sends it to recovery with the "battery cannot be charged " message instead of the CTC screen.
I tried it but the charge in the battery was too low and rebooted. I am hoping that with a full charge (as long as I don't power on the phone first as this will make it go to CTC logo again.
I am hoping that I can install the update.zip that I made by first unzipping the T959UVJFD_firmware.tar I downloaded then unpacked and then repacked into an update.zip as I don't think that it will read the package as a tar file and if it's not called update.zip The recovery is still stock. If I get the phone working I am not going to try unlocking and rooting it again. I will just post two separate adverts one as a carrier locked device and the other one (higher of course to cover buying the unlock from Telus) as carrier unlocked and then I will buy the unlock code if the blah blah you get the drift. sorry for rambling on.
oh and I can't rem if I said this or not, In recovery it "E:/data/fota not accessible" I don't know what that means yet I have been busy with other things and haven't looked it up yet.
Since you can get into at least some version of recovery, your bootloader is intact and you should be able to unbrick it. You ought to be able to get into download mode using a download jig. You can get one on ebay for a few bucks or you can make one yourself. There's a guide floating around here somewhere that lets you make one from a microusb cable.
Posted from my Galaxy Tab with CM10