Related
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.
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.
Here's the story - purchased a soft-bricked Vibrant for $50. It booted up to the phone - ! - computer screen. Took it home, used One-Click Unboot. Took a few tries, drivers, and USB ports, but eventually it worked. After that, it was just turning on and hanging at the Vibrant screen. Going along with other threads, I tried flashing to stock from ODIN. I followed this guide: http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
ODIN was finicky but eventually recognized my phone on COM Port 4. With the appropriate PIT and PDA loaded, I clicked Start and all the files uploaded. The phone restarts and.. stuck at Vibrant again. ODIN even lights up with a green PASS but I've let the phone sit and sit and it never gets anywhere.
Is this thing a total dud? Granted I'm trying to boot without a SIM card in it but I didn't think that would make a difference. Please, someone help. I'm stumped and annoyed.
Tried following this guide as well. Same problem. I'm definitely frustrated.
http://forum.cyanogenmod.com/topic/6998-howto-recover-from-a-soft-brick-on-your-vibrant/
I'm having this same problem, any info would be nice. I've actually tried several different guides online and none have worked for me, I can never get past the bootloader screen.
Also, I have been unable to find the file to install CWR, so I have no backup. I know my phone isn't bricked because I can install different modems and such but nothing is working to get it back up and working.
Make sure you've got the right files. Grab the ones out of the noob guide just to be sure
Sent from my SGH-T959 using XDA App
Yep, same problem. I can't seem to get into recovery either. Or connect to ADB to reboot into recovery. I'm tearing my damn hair out over this.
I tried ODIN flashing the Froyo No-Brick ROM for the hell of it cuz I read it fixed this issue as a last ditch for some people. No dice. Boots to the Vibrant screen for a second, then Vibrant switches to Galaxy S and it just sits there.
If no one has any ideas soon, I'm just going to say screw it. Pretty bummed - I've been on a G1 forever and was excited to use an Android phone that doesn't totally suck.
Wrrryyy said:
I tried ODIN flashing the Froyo No-Brick ROM for the hell of it cuz I read it fixed this issue as a last ditch for some people. No dice. Boots to the Vibrant screen for a second, then Vibrant switches to Galaxy S and it just sits there.
If no one has any ideas soon, I'm just going to say screw it. Pretty bummed - I've been on a G1 forever and was excited to use an Android phone that doesn't totally suck.
Click to expand...
Click to collapse
Go into the Developers section and look at the 2nd or 3rd post "Bay_wolf's AIO Vibrant Toolbox 2.5" . Download that into your computer and run 'Flash to Stock'.
That should help you get to where you need to go. Try the one click method first.
PM sent to Wrrryyy
Thanks for the advice guys, but still no go. Installed the drivers from the toolkit but all I can still do is use ODIN to try and flash stock. Results are exactly the same. Reboot into recovery still isn't working - I have a feeling USB debugging was not enabled on this phone before any of this happened so I'm screwed in that respect.
Keep trying, it's not bricked, one combination of files has to work for you.
Well there's only so many files I can apparently try. I've tried JFD, JI6, Eugene No-Brick.. Is there anything else I should trying flashing with ODIN?
Take out your sim card and microSD card. Download the appropriate stock JFD files, make sure you check repartition; you should be fine. USB debugging box not being checked before has nothing to do with your problem now. I believe either your partition or your bootloasder is screwy. Follow my steps above and you should be ok.
In fact, look at this and follow it to the T.
http://forum.xda-developers.com/showthread.php?t=848737
That's what I've tried probably 30 times by now. Repartition checked and unchecked. And yeah I know USB debugging doesn't have to do with ODIN, it's why I'm assuming I can't get ADB to recognize the phone so I could at least try "adb reboot recovery".
Outside of flashing JFD, JI6, or Eugene's No-Brick, is there anything else I could try?
Wrrryyy said:
That's what I've tried probably 30 times by now. Repartition checked and unchecked. And yeah I know USB debugging doesn't have to do with ODIN, it's why I'm assuming I can't get ADB to recognize the phone so I could at least try "adb reboot recovery".
Outside of flashing JFD, JI6, or Eugene's No-Brick, is there anything else I could try?
Click to expand...
Click to collapse
Try eBay
Sent from my T959 using XDA App
I'm in the same boat, same scenario with constant boot loop. This is my girlfriends phone too
IA-32e said:
I'm in the same boat, same scenario with constant boot loop. This is my girlfriends phone too
Click to expand...
Click to collapse
Look for a new girlfriend on ebay
djquick said:
Look for a new girlfriend on ebay
Click to expand...
Click to collapse
Haha no Craigslist I ended up having her file a claim and send it back. I must have borked the bootloader somehow cause now it wont turn on at all. Thank God for insurance. She's SUPER pissed though.
Compared to my Galaxy SII this phone is very finicky and ODIN is even more unreliable than normal. Never hard bricked a device before.
Picked up a G2 practically new for $100. Loving it so far - rooting process was a snap.
F this Vibrant. Back to Craigslist it goes. Still open to ideas before it's gone so I can attempt to get my money back, lol.
Wrrryyy said:
Picked up a G2 practically new for $100. Loving it so far - rooting process was a snap.
F this Vibrant. Back to Craigslist it goes. Still open to ideas before it's gone so I can attempt to get my money back, lol.
Click to expand...
Click to collapse
The only thing I see that will fix the Vibrant when it's in this state is JTAG brick repair for $50. This is after spending 12 hours searching and attempting to ODIN different stock firmwares till I finally hard bricked it.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-4g-vibrant-4g-jtag-brick-repair/
Yeah I was considering this. I e-mailed the guy asking if it was an appropriate fix. I figure, if the service takes care of a hard brick, it can certainly take care of a soft brick. Maybe I'll do that to keep it around as a back-up phone. Thanks for the replies, everyone.
I've got a very definite hard brick situation going on. A few weeks ago I was using my phone, browsing Tapatalk and downloading something with the Dropbox app, and the phone went completely unresponsive (screen on but frozen, no response to any touches), came back after a few seconds, then froze completely. I powered off and tried to reboot, it hung on the boot animation. Not a bootloop, just hanging there. I powered off again and booted into CWM and tried to restore from my backup. It threw a couple errors which unfortunately I don't remember much about, and honestly, I can't remember now if they came up before or after I started the restore. It started restoring, but got hung up restoring system. After waiting what seemed like forever but was probably more like 10 minutes I very hesitantly powered off and went back into recovery, this time attempting to reflash the rom I was using. More or less the same thing, it started but just hung up during the install. I powered off again, intending to put my phone into download mode and try to flash something via Odin, but the poor guy had had enough and wouldn't even power back on. I left it charging overnight, but it never came back on and I've since bought a new phone. However, if it seems to anyone that it would be worthwhile to try a jig or jtag service, I wouldn't mind keeping this phone as a spare. Truth is, I actually miss it.
I was running WanamLite 12.5, which is XWLPX, 4.0.4, with SpeedMod K3-32. I had tried out a couple of what were then pretty much new JB leaks just before the bricking, I know I tried out Omega and Disaster, but I only kept them on for a few hours each time. All of the kernels I've used since 4.0.4 have been considered "safe".
Anyway, again, based on what I've described does anyone think there's a chance of unbricking my phone without replacing the motherboard?
shockwaverider said:
I've got a very definite hard brick situation going on....
Anyway, again, based on what I've described does anyone think there's a chance of unbricking my phone without replacing the motherboard?
Click to expand...
Click to collapse
Firstly, there is no such thing as a "hard brick" for same reason there is no such thing as a "soft brick". There is just "bricked" and no in between, your device is either bricked or it isnt.
What n00bs call "soft bricked" is just when they cant figure out how to get system to boot. Your device is bricked when it wont power on or if it powers on you cant use download/recovery to flash working rom/kernel.
In your case it sounds like you have had a hardware failure and thus will need to get the part fixed/replaced or maybe whole board. To answer your question though, yes you should first try a USB jig to see if you can get device to wake up in download mode and then try again to flash kernel ready for restoring backup or flashing new rom. If this fails then you will need to get it fixed.
TheATHEiST said:
Firstly, there is no such thing as a "hard brick" for same reason there is no such thing as a "soft brick". There is just "bricked" and no in between, your device is either bricked or it isnt.
What n00bs call "soft bricked" is just when they cant figure out how to get system to boot. Your device is bricked when it wont power on or if it powers on you cant use download/recovery to flash working rom/kernel.
In your case it sounds like you have had a hardware failure and thus will need to get the part fixed/replaced or maybe whole board. To answer your question though, yes you should first try a USB jig to see if you can get device to wake up in download mode and then try again to flash kernel ready for restoring backup or flashing new rom. If this fails then you will need to get it fixed.
Click to expand...
Click to collapse
yada yada yada I've heard some developers use "unbrick". Go tell 'em there's no such a thing.
And stop worrying about semantics.
Thanks for the replies. I understand that a so-called "soft brick" isn't really a brick per se, but when even articles in the XDA portal throw around the terms "soft" and "hard" bricks, I would say that the genie is out of the bottle and these terms have, for better or worse, entered the common parlance. I do, however, appreciate the input and quite possibly this is simply a hardware issue, although I will, when time allows, try to wake the phone up with a jig.
gastonw said:
yada yada yada I've heard some developers use "unbrick". Go tell 'em there's no such a thing.
And stop worrying about semantics.
Click to expand...
Click to collapse
BS!
If thats the case link me one single post where any respected dev refers to a system boot issue as a "soft brick".
The only conceivable time they would refer to that is simply to try and help a n00b and it was quicker to refer to it in that way then to explain things.
You can only "unbrick" if your device is "bricked" and having a rom or kernel issue resulting in a system not booting is not "bricked", Its as simple as that.
Hello,
I have a Samsung Galaxy S2.
After reading this post http://forum.xda-developers.com/showthread.php?t=2382579 I decided to root my phone.
So I went ahead and started with this step http://forum.xda-developers.com/showthread.php?t=1118693 because I was unsure if I had a kernel with the MMC-SUPERBRICK-BUG.
After I flashed CWM-SuperSU-v0.97.zip using Odin version 1.85 and after the phone rebooted it was stuck at the "triangle screen" for a few seconds then the display went black and I couldn't do anything further.
Up to this point the phone was still accessible in download mode (volume up, power and center button). I believe this is called "download mode". Sorry but I am a complete noob with rooting phones, etc...
So I panicked and took the phone to a repair shop (big mistake). The guy ran it in download mode then tried to flash something onto the phone (I think he used all 4 fields: Bootloader, PDA, Phone and CSC.
Then, in the middle of the operation, Odin froze when writing "setting up connection". Then the phone died ! pressing the 3 famous buttons does nothing and the phone just stays dead.
I had to leave the phone there as the guy said they will try to bypass stuff and try to connect to the CPU directly (sorry again if this sounds noobish). I did update my modem firmware and my computer BIOS in the past... but I guess this one was more complicated.
At the shop, they asked me to check again in 3 days. I am lost here. I don't know what to do anymore.
Is the phone hard bricked ? Should they bear all expenses for what they did ? I would bring back my phone and try something like this http://forum.xda-developers.com/showthread.php?t=1878255 or even a stock flash but I am afraid I cannot do that as the phone isn't even powering up anymore after they tried to repair it at the shop.
Any advice is appreciated.
Nope. You borked it. You tried to flash custom firmware to the phone & obviously failed spectacularly at it. Instead of trying to flash it yourself via download mode (which you could easily have done unless the NAND was borked), you paid them to do it. Sometimes flashes go bad. Sounds like that's what happened in this case.
Reading between the lines they sound like they're going to try & JTAG it (or have someone else do it). And if that fails I presume they'll change motherboards. You could always get the phone back & take it to someone who does JTAGs if that shop doesn't themselves.
MistahBungle said:
Nope. You borked it. You tried to flash custom firmware to the phone & obviously failed spectacularly at it. Instead of trying to flash it yourself via download mode (which you could easily have done unless the NAND was borked), you paid them to do it. Sometimes flashes go bad. Sounds like that's what happened in this case.
Reading between the lines they sound like they're going to try & JTAG it (or have someone else do it). And if that fails I presume they'll change motherboards. You could always get the phone back & take it to someone who does JTAGs if that shop doesn't themselves.
Click to expand...
Click to collapse
Yes I know I failed at it
Or maybe the shop technician is the one who broke it. At least when I had the phone with me I was still able to boot in Odin mode.
Do you think I could have recovered my phone if I had kept it with me and it was booting in download mode ?
I feel so pissed that I took it to that shop. I just wish I hadn't panicked and I had tried, instead, to fix it at home by asking for more help.
Anyway I still haven't paid them anything so far.
We agreed that they will pay for the motherboard because I brought in a working phone (that would power up at least). The owner of the shop was nice enough to agree that he would only charge me fees for installing new software on the phone (even if they have to change the motherboard) because he knows the phone was booting in Odin mode when I came in to the shop and his technician flashed the wrong firmware.
I also wrote down the board serial number so I can be sure they changed it (if they say they did that). So you are telling me the phone can still be fixed ? What does JTAG mean ?
Even if it is fixed I think I will be too scared to try and root it again. Unless I can understand in advance, step by step, what I need to do and what file version(s) I need to use.
Ok, I got my phone today in good working condition.
According to the shop, they had to replace an IC (I don't know what damaged the IC, I am assuming this happened when they tried to electrically jolt the phone) then JTAG it to get it to work again. They charged me a small fee (and they did end up bearing more than 50% of the expenses) because I brought in a phone that was booting in download mode and they take responsibility for what happened after that (flashing wrong files which caused the phone to completely stop booting).
Anyway, long story short, this was my first attempt to root a mobile phone and I learned my lesson.
I am running the following:
Model Number: GT-I9100
Android Version: 4.0.3 (which I will need to upgrade to 4.1.2 of course)
Baseband Version: I9100XXLPW
I know you will say read the sticky posts or the guides but the truth is, that's exactly what I did (you can see the links to the guide I tried to follow in my original post) and I still ended up failing at rooting/installing cyanogen on my phone right after installing Clockwork Mod.
The truth is I am scared to try again and mess up the phone. So this time I would rather be safe than sorry.
What can I do, this time, to safely root it and install a mod like Cyanogen.
Detailed steps are appreciated:
- Do I need to upgrade to 4.1.2 before rooting as 4.0.3 might have the superbrick bug ?
- How to backup the phone.
- Odin version to use, ClockWork Mod version to use, Cyanogen version to use
- How to connect the phone, how to reboot in download mode and all the necessary actions to avoid bricking my phone.
No spoon feeding aloud on XDA.better to read and learn how to do this and that but before you flash anything after learning how to do that learn how to fix it if it doesn't work. :thumbup:
andrewwright said:
No spoon feeding aloud on XDA.better to read and learn how to do this and that but before you flash anything after learning how to do that learn how to fix it if it doesn't work. :thumbup:
Click to expand...
Click to collapse
Fair enough, I figured I'd get that reply from someone and it's normal to be honest.
I decided not to try anything on my phone before I re-read the guides and be sure I know what I am doing.
I will also keep the phone running on stock firmware (after upgrading to JB 4.1.2) to check the battery consumption behavior which, I hope, will be fine since someone tampered with my phone's electronic components at the shop.