First time I have hard bricked a Samsung phone and would like to know where I went wrong. All we were trying to accomplish was to root the stock rom and change the revovery to CWM Touch. There was no attempt to upgrade to anything other than the stock rom. Here are the steps I followed:
Powered off phone
Inserted USB Jig (which powers on phone in Download Mode)
Started up Odin 1.85
Loaded cwm-touch-i717-120414.tar.md5 in the PDA slot
Plugged in phone (recognized as Com7)
Flashed
Phone rebooted after the flash and I let it sit until it timed out just to make sure everything seemed okay.
Powered off phone
Inserted USB Jig (which powers on phone in Download Mode)
Started up Odin 1.85
Loaded att_note_root.tar in the PDA section
Plugged in phone (recognized as Com7)
Flashed
Phone rebooted after the flash and seemed okay. On this boot a couple of things asked for root permission but I cant remember which apps. I attached the running phone to my computer and connected using USB Mass Storage. I copied flash_counter_reset_att.zip to the root of the SD card. Checked the MD% hash after copying to the phone. I powered off the phone.
Powered on the phone holding the Vol +/Vol-/Power to boot into CWM recovery
Chose install zip from sdcard
Chose install zip from internal sdcard
Chose flash_counter_reset_att.zip
Chose yes to flash
After the flash completed I went back and chose reboot system now
Here is where all hell broke loose. It was just a black screen and not recognizable by Odin. The phone is now on it's way to MobileTechVideos to get JTAG unbricked.
So my big question is what went wrong or what step did I miss?
WheresWaldo said:
First time I have hard bricked a Samsung phone and would like to know where I went wrong. All we were trying to accomplish was to root the stock rom and change the revovery to CWM Touch. There was no attempt to upgrade to anything other than the stock rom. Here are the steps I followed:
Powered off phone
Inserted USB Jig (which powers on phone in Download Mode)
Started up Odin 1.85
Loaded cwm-touch-i717-120414.tar.md5 in the PDA slot
Plugged in phone (recognized as Com7)
Flashed
Phone rebooted after the flash and I let it sit until it timed out just to make sure everything seemed okay.
Powered off phone
Inserted USB Jig (which powers on phone in Download Mode)
Started up Odin 1.85
Loaded att_note_root.tar in the PDA section
Plugged in phone (recognized as Com7)
Flashed
Phone rebooted after the flash and seemed okay. On this boot a couple of things asked for root permission but I cant remember which apps. I attached the running phone to my computer and connected using USB Mass Storage. I copied flash_counter_reset_att.zip to the root of the SD card. Checked the MD% hash after copying to the phone. I powered off the phone.
Powered on the phone holding the Vol +/Vol-/Power to boot into CWM recovery
Chose install zip from sdcard
Chose install zip from internal sdcard
Chose flash_counter_reset_att.zip
Chose yes to flash
After the flash completed I went back and chose reboot system now
Here is where all hell broke loose. It was just a black screen and not recognizable by Odin. The phone is now on it's way to MobileTechVideos to get JTAG unbricked.
So my big question is what went wrong or what step did I miss?
Click to expand...
Click to collapse
My Friend I'm so sorry to see this from you I really do feel bad for you I hope your phone turns out alright once it get's fixed I do not want to see anyone phone brick this is serious problem
Good Luck To you.......
What carrier version of the phone was it?
All Will Be Well
WheresWaldo said:
First time I have hard bricked a Samsung phone and would like to know where I went wrong. All we were trying to accomplish was to root the stock rom and change the revovery to CWM Touch. There was no attempt to upgrade to anything other than the stock rom. Here are the steps I followed:
Powered off phone
Inserted USB Jig (which powers on phone in Download Mode)
Started up Odin 1.85
Loaded cwm-touch-i717-120414.tar.md5 in the PDA slot
Plugged in phone (recognized as Com7)
Flashed
Phone rebooted after the flash and I let it sit until it timed out just to make sure everything seemed okay.
Powered off phone
Inserted USB Jig (which powers on phone in Download Mode)
Started up Odin 1.85
Loaded att_note_root.tar in the PDA section
Plugged in phone (recognized as Com7)
Flashed
Phone rebooted after the flash and seemed okay. On this boot a couple of things asked for root permission but I cant remember which apps. I attached the running phone to my computer and connected using USB Mass Storage. I copied flash_counter_reset_att.zip to the root of the SD card. Checked the MD% hash after copying to the phone. I powered off the phone.
Powered on the phone holding the Vol +/Vol-/Power to boot into CWM recovery
Chose install zip from sdcard
Chose install zip from internal sdcard
Chose flash_counter_reset_att.zip
Chose yes to flash
After the flash completed I went back and chose reboot system now
Here is where all hell broke loose. It was just a black screen and not recognizable by Odin. The phone is now on it's way to MobileTechVideos to get JTAG unbricked.
So my big question is what went wrong or what step did I miss?
Click to expand...
Click to collapse
I believe the "ONLY" thing you did (wrong?) was the att flash counter zip -Eliminate the Att step - there is a rooting method that does not cause the flash counter to be tripped (i believe it's non touch cwm - then flash the touch cwm - then flash Roms to your Heart's desire) I'm not really sure the flash counter issue really matters - At&t only cares if there is physical damage to the phone because I believe they just re-flash the phone and sell it again.
I'm Mostly responding to say that JTAG is Beastly and your phone will be better than brand new when you get it back - the status of your order won't change until they ship it back (which for me was 7 days), but don't panic (like I did) they are Good & Fast - So relax it cost you $50 & A week, but Hell the phone cost $700 so All Will Soon be well.
Also double check that it was the correct zip files for the Note - I bricked my Skyrocket because I flashed a Note Rom by accident (Thanks JTAG ) - I've got Too Many Samsung Devices - Hope This Helps.
bigdaddy4u said:
I believe the "ONLY" thing you did (wrong?) was the att flash counter zip -Eliminate the Att step - there is a rooting method that does not cause the flash counter to be tripped (i believe it's non touch cwm - then flash the touch cwm - then flash Roms to your Heart's desire) I'm not really sure the flash counter issue really matters - At&t only cares if there is physical damage to the phone because I believe they just re-flash the phone and sell it again.
I'm Mostly responding to say that JTAG is Beastly and your phone will be better than brand new when you get it back - the status of your order won't change until they ship it back (which for me was 7 days), but don't panic (like I did) they are Good & Fast - So relax it cost you $50 & A week, but Hell the phone cost $700 so All Will Soon be well.
Also double check that it was the correct zip files for the Note - I bricked my Skyrocket because I flashed a Note Rom by accident (Thanks JTAG ) - I've got Too Many Samsung Devices - Hope This Helps.
Click to expand...
Click to collapse
I have no issues with MobileTechVideos as I bought one of the first USB jigs when I got my day one Captivate. I am sure it will come back solid.
I did double check that I was using files specific to the Note, but I must say, you Note users have one finicky phone. I will stick with my Skyrocket. I'll look over the instruction for the non counter increasing root in the forums when the phone gets back.
Thanks
You didn't mention if you were able to get back to Clockwork. If you hold volume up and down while pressing power, it takes you straight into Clockwork regardless of the black screen. If so then you aren't bricked. Or if you still want to use Odin, hold volume down and power to get to download mode which is also Odin mode. Did you try these commands using physical button combinations and they did not work? If you didn't try them then you may be spending unnecessary money. If you did try all these things, then maybe you were hard bricked. Of all the Android phones I've owned and I've rooted all of them, I've never been unable to recover. I've only seen one hard brick from a coworker that had a galaxy s on tmobile that would not power on or charge after trying to root.
why did you even need a jig? turn on phone while holding down volume button.
madman604 said:
why did you even need a jig? turn on phone while holding down volume button.
Click to expand...
Click to collapse
+1. I'm so confused now. Maybe he tried to unbrick it first, then the phone turned hard bricked.
The flash counter is kind of a joke, isn't it? I mean, if the tech is looking to see if you flashed something, he cares that you flashed something, not how many times you flashed it.
I think the jig added another variable to the equation, and was unnecessary. None of the threads for rooting required one.
Also, i'd check to see if a MD5 is available for the files you used for the flash. Check the files you used and see if that was the issue.
If the note is new, and really is hardbricked, he's hopefully within the 30 day window. Just take it back for an exchange and tell them it stopped booting.
There is a thread started by ncoder in the international note general forum that has been near the top for a long time. You are not alone. Samsung actually responded!
Edit: Samsung desperately needs a stock failure. Maybe they would fix your phone for free so they could do a JTAG core dump that matches their sources etc.
Sent from my SAMSUNG-SGH-I717 using XDA
jordant2 said:
You didn't mention if you were able to get back to Clockwork. If you hold volume up and down while pressing power, it takes you straight into Clockwork regardless of the black screen. If so then you aren't bricked. Or if you still want to use Odin, hold volume down and power to get to download mode which is also Odin mode. Did you try these commands using physical button combinations and they did not work? If you didn't try them then you may be spending unnecessary money. If you did try all these things, then maybe you were hard bricked. Of all the Android phones I've owned and I've rooted all of them, I've never been unable to recover. I've only seen one hard brick from a coworker that had a galaxy s on tmobile that would not power on or charge after trying to root.
Click to expand...
Click to collapse
Would not go into Clockwork Recovery or Odin with any key combination, simply a black screen.
madman604 said:
why did you even need a jig? turn on phone while holding down volume button.
Click to expand...
Click to collapse
Jig is much faster, and works everytime, nuff said.
babymatteo said:
+1. I'm so confused now. Maybe he tried to unbrick it first, then the phone turned hard bricked.
Click to expand...
Click to collapse
Nope, started with a working phone and after applying the counter reset, which works beautifully on the SkyRocket BTW, that's when it bricked.
PaulF8080 said:
There is a thread started by ncoder in the international note general forum that has been near the top for a long time. You are not alone. Samsung actually responded!
Edit: Samsung desperately needs a stock failure. Maybe they would fix your phone for free so they could do a JTAG core dump that matches their sources etc.
Sent from my SAMSUNG-SGH-I717 using XDA
Click to expand...
Click to collapse
Thanks for the info.
Jamesyboy said:
The flash counter is kind of a joke, isn't it? I mean, if the tech is looking to see if you flashed something, he cares that you flashed something, not how many times you flashed it.
I think the jig added another variable to the equation, and was unnecessary. None of the threads for rooting required one.
Also, i'd check to see if a MD5 is available for the files you used for the flash. Check the files you used and see if that was the issue.
If the note is new, and really is hardbricked, he's hopefully within the 30 day window. Just take it back for an exchange and tell them it stopped booting.
Click to expand...
Click to collapse
I am beginning to agree that the counter seems irrelevant and wholly unnecessary.
Jig simply puts any Samsung phone that is off into Download mode, it is the same as the key combination only easier.
I always check MD5 hashes after I copy to the internal SD card.
I'm with the others on this... Flash counter reset was designed to work on ICS and not GB, I do believe that's where things went bad.
WheresWaldo said:
I am beginning to agree that the counter seems irrelevant and wholly unnecessary.
Jig simply puts any Samsung phone that is off into Download mode, it is the same as the key combination only easier.
I always check MD5 hashes after I copy to the internal SD card.
Click to expand...
Click to collapse
WheresWaldo said:
Thanks for the info.
Click to expand...
Click to collapse
I have no clue if the info applies to you. I just was hoping you still had possibly useful data in your phone. Saving face with your cousin was a side benefit.
Sent from my SAMSUNG-SGH-I717 using XDA
the only other step you forgot is to create a backup after flashing cwm
WheresWaldo said:
Thanks for the info.
Click to expand...
Click to collapse
I have same problem
WheresWaldo said:
First time I have hard bricked a Samsung phone and would like to know where I went wrong. All we were trying to accomplish was to root the stock rom and change the revovery to CWM Touch. There was no attempt to upgrade to anything other than the stock rom. Here are the steps I followed:
Powered off phone
Inserted USB Jig (which powers on phone in Download Mode)
Started up Odin 1.85
Loaded cwm-touch-i717-120414.tar.md5 in the PDA slot
Plugged in phone (recognized as Com7)
Flashed
Phone rebooted after the flash and I let it sit until it timed out just to make sure everything seemed okay.
Powered off phone
Inserted USB Jig (which powers on phone in Download Mode)
Started up Odin 1.85
Loaded att_note_root.tar in the PDA section
Plugged in phone (recognized as Com7)
Flashed
Phone rebooted after the flash and seemed okay. On this boot a couple of things asked for root permission but I cant remember which apps. I attached the running phone to my computer and connected using USB Mass Storage. I copied flash_counter_reset_att.zip to the root of the SD card. Checked the MD% hash after copying to the phone. I powered off the phone.
Powered on the phone holding the Vol +/Vol-/Power to boot into CWM recovery
Chose install zip from sdcard
Chose install zip from internal sdcard
Chose flash_counter_reset_att.zip
Chose yes to flash
After the flash completed I went back and chose reboot system now
Here is where all hell broke loose. It was just a black screen and not recognizable by Odin. The phone is now on it's way to MobileTechVideos to get JTAG unbricked.
So my big question is what went wrong or what step did I miss?
Click to expand...
Click to collapse
Hi all
i have the same problem , i flash a wrong file and phone is hard bricked
now i want to send to MobileTechVideos , i am in Kuwait so my question is
is it safe to send them or any one other in the region to whom i can send?
please suggest me what i should do
My Device is N7000
thanks
deleted...
I was under the impression that the jig didn't work with the note, I recall someone else bricked their phone using one a while back
Sent from my SAMSUNG-SGH-I717 using xda premium
jimmer411 said:
I was under the impression that the jig didn't work with the note, I recall someone else bricked their phone using one a while back
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
I agree. I have never even read of using a jig except for unbricking. Coincidence maybe but i wouldnt risk it again if you get a replacement
Sent from a big ass phone
Related
I have never bricked it before, and I cannot go into download mode... I tried the the Vol up and vol down, didn't work, so I have been using ADB and just ****ed something up....
Now I need to know a way how I can revert back to stock, please and thank you, I will forever owe you one.
EDIT: Okay there is some confusion, to simplify it I will take it step by step:
I replaced an APK file from my system/apps and ever since it has been force closing process.android.acore, so I tried reflashing to stock, it froze while doing so now I have a picture of a caution sign, a phone and a computer coming up on my Vibrant, it will not start up.
It is hardware locked because I have never been able to access download mode via hardware keys(I have always been using ADB).
Is there any way I can reinstall stock? Or is my vibrant now destroyed?
what exactly were you doing when your phone stopped working? "just ****ed something up" makes it hard to pinpoint problems...
I don't know I replaced my phone.apk with another one then ever since then it keeps saying process.android.acore has stopped working. It wouldn't stop showing up so I tried to reflash with Odin to stock but it froze and now it is bricked.
bumping a little bit, I have never bricked it before so I have 0 experience.
What do you mean by froze? On what screen? How far can you get into booting?
bigragu said:
What do you mean by froze? On what screen? How far can you get into booting?
Click to expand...
Click to collapse
Alright let me start over with more detail:
I tried to replace the dialer so I replaced the phone.apk and then process.android.acore kept force closing so then I tried reflashing with stock, during that I don't know what happened but I think my phone froze, so then it shut off and turned back on, I only found a screen with a computer on it... I am assuming it is bricked.... I also know it is hardware locked because I tried going into debug mode with vol up and vol down, how can I unbrick it?
Try moving the stock rom into the phones internal memory via adb. And flash it after a wipe.
I am Also having this same problem
I Flashed my Vibrant through Rom Manager to Froyo 2.2 from eugene373 and sombionix.
After flashing to both ROMS for Froyo I wanted to revert back to 2.1.
I tried to put sombionix 1.3 eclair ROM back on to my phone using clockwork mod.
The flash was not successful it stopped in the middle but the phone came on with a Force close error of an android process.
I tried to reboot through adb reboot recovery with usb debugging enabled.
The phone shut down like it would reboot into recovery mode and now it gets stuck on boot at the samsung vibrant screen.
I tried to use ODIN to flash back to the stock Rom but the phone is recognized in ODIN but will not flash.
ODIN sees the phone but will not get past flash analysis. (Sat for 8 Hours)
I believe this is the definition of bricked. Please Help!!!!!
sheek360 said:
Try moving the stock rom into the phones internal memory via adb. And flash it after a wipe.
Click to expand...
Click to collapse
It isn't even being read by my computer... nothing...
sympala said:
I Flashed my Vibrant through Rom Manager to Froyo 2.2 from eugene373 and sombionix.
After flashing to both ROMS for Froyo I wanted to revert back to 2.1.
I tried to put sombionix 1.3 eclair ROM back on to my phone using clockwork mod.
The flash was not successful it stopped in the middle but the phone came on with a Force close error of an android process.
I tried to reboot through adb reboot recovery with usb debugging enabled.
The phone shut down like it would reboot into recovery mode and now it gets stuck on boot at the samsung vibrant screen.
I tried to use ODIN to flash back to the stock Rom but the phone is recognized in ODIN but will not flash.
ODIN sees the phone but will not get past flash analysis. (Sat for 8 Hours)
I believe this is the definition of bricked. Please Help!!!!!
Click to expand...
Click to collapse
Excuse me sir, make your own thread, don't jack mine...
Smokexz said:
It isn't even being read by my computer... nothing...
Excuse me sir, make your own thread, don't jack mine...
Click to expand...
Click to collapse
lol Sorry Smokexz didn't mean to jack your thread just trying to consolidate phone bricked threads. I will create my own NO PROBLEM.
sympala said:
lol Sorry Smokexz didn't mean to jack your thread just trying to consolidate phone bricked threads. I will create my own NO PROBLEM.
Click to expand...
Click to collapse
Thanks, regardless both our situations are bad .
Please? I really need help with this.
Smokexz said:
Please? I really need help with this.
Click to expand...
Click to collapse
If there is an answer, which I am not sure that there is, it would be here: http://forum.xda-developers.com/showthread.php?t=782739. You may have already seen it, but if not it gives many different processes to try. Good luck!
hourst2 said:
If there is an answer, which I am not sure that there is, it would be here: http://forum.xda-developers.com/showthread.php?t=782739. You may have already seen it, but if not it gives many different processes to try. Good luck!
Click to expand...
Click to collapse
Yep, I'm screwed thanks for the help though.
Can you get the phone in download mode?
Did you try this:
Pull battery
hold the volume up and down
reinsert the battery whiles still holding down the volume up n down
plug in usb cord
it should put you back in to DL mode
Open ODIN and unplug phone from PC and plug back in hopefully it will notice it then.
I am not sure if you can get in DL mode and it just wont let you do anything, but if you have already tried this my apologies.
gthmcty1 said:
Can you get the phone in download mode?
Did you try this:
Pull battery
hold the volume up and down
...
Click to expand...
Click to collapse
Did you even read the OP? He is HARDWARE LOCKED ie BUTTONS DON'T WORK geeze people learn how to read!
And on topic, if you can't ADB and you are Hardware Locked, you are SOL. Try to get an exchange from T-Mobile since it appears that they regard being Hardware Locked as a defect.
Alright thanks
Sent from my Motorola_i1 using Tapatalk
gravis86 said:
Did you even read the OP? He is HARDWARE LOCKED ie BUTTONS DON'T WORK geeze people learn how to read!
And on topic, if you can't ADB and you are Hardware Locked, you are SOL. Try to get an exchange from T-Mobile since it appears that they regard being Hardware Locked as a defect.
Click to expand...
Click to collapse
Your a dumb ass, His thing actually does work.. I was "hardware locked" like 5 times That DOES work, you sir are a DUMB ASS < Had to say it again
(Make sure that your USB is plugged into your computer & not your phone)
Remove the back cover & remove the battery along with your sim & micro SD
Hold the VOL Up & VOL Down
(Keep holding those buttons) Now insert the battery
Plug the usb into your phone.
It will put you back in to DL mode
Open ODIN and unplug phone from PC and plug back in hopefully it will notice it then.
^^Do that
gravis86 said:
Did you even read the OP? He is HARDWARE LOCKED ie BUTTONS DON'T WORK geeze people learn how to read!
And on topic, if you can't ADB and you are Hardware Locked, you are SOL. Try to get an exchange from T-Mobile since it appears that they regard being Hardware Locked as a defect.
Click to expand...
Click to collapse
Wow you come in and try to offer up help and you get some one that feels the need to police the "suggestions"........ Have a coke and a smile my friend...and relax!
gthmcty1 said:
Wow you come in and try to offer up help and you get some one that feels the need to police the "suggestions"........ Have a coke and a smile my friend...and relax!
Click to expand...
Click to collapse
Not to mention that what that guy said actually works...
Some people just make me laugh
(Make sure that your USB is plugged into your computer & not your phone)
Remove the back cover & remove the battery along with your sim & micro SD
Hold the VOL Up & VOL Down
(Keep holding those buttons) Now insert the battery
Plug the usb into your phone.
It will put you back in to DL mode
Open ODIN and unplug phone from PC and plug back in hopefully it will notice it then.
^^Do that
My problem is that I had no idea that i9000 and Fascinate are complete diffrent firmwares. I flashed the 2.2 i9000 onto my Fascinate, I didn't find out this was a huge FUBAR until after the phone wasn't turning on and then I did some extensive searching. So now flashed the CWMRecovery and then the Stock-i500 files. Except for the Recovery file which fails when I try to run it on Odin... I'm completely lost. If anyone knows if it's possible to fix my phone, I would appreciate the help
its bricked. is it still under warranty? tell them it froze and wont turn on. are u stuck in a boot loop?
It was.. it would try to boot up into i9000 then the regular Samsung logo and then I'd get a blue pixelated mess... now when I hit the power buitton there's a cell phone and PC picture with a triangled exclamation mark in the center.
AdventXD said:
It was.. it would try to boot up into i9000 then the regular Samsung logo and then I'd get a blue pixelated mess... now when I hit the power buitton there's a cell phone and PC picture with a triangled exclamation mark in the center.
Click to expand...
Click to collapse
Sounds like it wants to be hooked back up, like it's not out of download mode. That's happened to me when I've unplugged the USB cable when it wasn't expecting me to. Dunno, there is a thread here somewhere about flashing the wrong image, then flashing an intermediary image, then the VZW image and getting things back. Not sure if it applies here, though... Good luck...
Boot in Download mode again
Dont Use Samsung MicroUSB Cable use any Good Quality MicroUSB instead
Flash the Clockwory Kernal and Recovery using ODIN
Copy ClockworkMod Recovery in update.zip format to SDCard
Boot into Recovery in Default Samsung Recovery Apply Update this will take you to clockwork
Flash any Compatible Clean ROM and you are in business,For me this Worked
You see the cable / triangle icon, it means your flash failed to take, and was incomplete. You need to re-flash, start with the kernel. I would use the CWM kernel as mentioned. If that fails let us know.
The only real thing you can do to "brick" this phone is to overwrite bml12 (modem.bin). For example, if you flashed anything with the "phone" box in odin, that will kill your modem. Other than that it will take a little work, but it's all recoverable.
Ok. For one, i have posted warnings all over the place to not do what you did.
And two, if what you flashed an Odin restore file with a modem in it, you will no longer have a working phone. We don't have a way to fix it. Sorry dude, best bet is to take it back to verizon and beg for a warranty replacement. If you are at the phone and computer icon right now, i would just leave it and take it into vzw like that.
namebrandon said:
Other than that it will take a little work, but it's all recoverable.
Click to expand...
Click to collapse
Nope, there are other things you can do to brick it / make it into just a fancy PDA
fallingup said:
Ok. For one, i have posted warnings all over the place to not do what you did.
And two, if what you flashed an Odin restore file with a modem in it, you will no longer have a working phone. We don't have a way to fix it. Sorry dude, best bet is to take it back to verizon and beg for a warranty replacement. If you are at the phone and computer icon right now, i would just leave it and take it into vzw like that.
Click to expand...
Click to collapse
Yeah. Problem is this isn't the first site I went to. There were no warnings in the other guides... Just said "Upgrade Galaxy S to 2.2" It never mentioned it was only for the i9000 model... I've learned my lesson tho. Luckily my buddy works at Verizon and I don't have to jump through rings of fire to get a replacement. Thanks everyone
fallingup said:
Nope, there are other things you can do to brick it / make it into just a fancy PDA
Click to expand...
Click to collapse
Yeah, like put it in a microwave. Which I'm going to do with you shortly if you keep it up. I can always cancel that $97 during my free trial, you know..
I tried to fix the hardware issues because i was not able to get into the recovery mode buy using the 3 button combos. Anyways, I BRICKED IT!!! It wont turn on or able to get to download mode anymore.
Is there a way to get it to turn on again or should i just trash it and should never touch a smart phone again?
Please help!
So, with battery in you plug in the charger like you're going to charge your phone, and you get nothing?
Sent from my SGH-T959 using XDA Premium App
yes, nothing at all.....the phone is completly cold!
I assume you have tried pulling the sim and sd cards out, pull the battery out, connect usb to pc and phone and pop the battery in as you hold the +- vol buttons? Check the usb cable, try anothrone if you have, check the terminals on the phone usb port. If all ok then you might want to try a jig....
Sent from my SGH-T959 using XDA Premium App
I have tried all of the above. But what is the jig?
Sent from my T-Mobile G1 using XDA Premium App
Jig is basically a jumper thru your phones usb port that forces the phone to download mode, or jump start it. Search the forum, they are cheaper here than ebay.
Sent from my SGH-T959 using XDA Premium App
Here you go...http://www.mobiletechvideos.com/blog/?p=570
Sent from my SGH-T959 using XDA App
This phone is incredibly hard to brick...
What exactly did you flash? Everything... In order...
Thanks so much guys!
I just bought one and hope this will work!
Sure, good luck!
Sent from my SGH-T959 using XDA Premium App
s15274n said:
This phone is incredibly hard to brick...
What exactly did you flash? Everything... In order...
Click to expand...
Click to collapse
Well my phone had hardware lock, which i was not able to use 3 button combos to get to recovery mode....so i found this thread.....
I just captured the JI6 OTA update files from one of my phones and found that T-mobile is
updating the SBL with the same file found in this thread, I'm using the same method as T-mobile
to install the new SBL so the chances for a brick are the same but if you are completely
stock just wait for the OTA update and have the phone swapped under warranty in the
event of a brick.
WARNING:
INSTALLING THIS CAN BRICK YOUR PHONE
this is safer than the odin method, but when messing with the phones bootloader
there is always a chance that you could end up with a paper weight (I bricked
one phone messing with this stuff).
Updated 10-15-2010
this is the fix for hardware locked phones in update.zip form
install the phone drivers which can be found at:
http://forum.xda-developers.com/showthread.php?t=728929
put update.zip on the internal sd card (the 12 gb one)
turn on USB debugging in Settings-->Applications-->Development
reboot into recovery, use the RebootRecovery.bat in adb.zip if you dont know
how to do that.
when in recovery use the vol up and down buttons to navigate and power button to
select reinstall packages
install will take about 20-30 seconds and will pause at "writing secondary bootlader" don't panic
the phone will reboot you should be unlocked (or bricked).
update.zip md5=3b32fab99049530d2185014340840a47
Attached Files
File Type: zip adb.zip (253.2 KB, 1153 views)
File Type: zip update.zip (645.5 KB, 1467 views)
After i applied the update.zip, phone didnt reboot. I waited 5 mins phone turned cold, battery was cold as well...so i took the battery out and tried to turn on but no luck.
I hope the jug will help, otherwise i dont know what else to do.
yahase said:
Well my phone had hardware lock, which i was not able to use 3 button combos to get to recovery mode....so i found this thread.....
I just captured the JI6 OTA update files from one of my phones and found that T-mobile is
updating the SBL with the same file found in this thread, I'm using the same method as T-mobile
to install the new SBL so the chances for a brick are the same but if you are completely
stock just wait for the OTA update and have the phone swapped under warranty in the
event of a brick.
WARNING:
INSTALLING THIS CAN BRICK YOUR PHONE
this is safer than the odin method, but when messing with the phones bootloader
there is always a chance that you could end up with a paper weight (I bricked
one phone messing with this stuff).
Updated 10-15-2010
this is the fix for hardware locked phones in update.zip form
install the phone drivers which can be found at:
http://forum.xda-developers.com/showthread.php?t=728929
put update.zip on the internal sd card (the 12 gb one)
turn on USB debugging in Settings-->Applications-->Development
reboot into recovery, use the RebootRecovery.bat in adb.zip if you dont know
how to do that.
when in recovery use the vol up and down buttons to navigate and power button to
select reinstall packages
install will take about 20-30 seconds and will pause at "writing secondary bootlader" don't panic
the phone will reboot you should be unlocked (or bricked).
update.zip md5=3b32fab99049530d2185014340840a47
Attached Files
File Type: zip adb.zip (253.2 KB, 1153 views)
File Type: zip update.zip (645.5 KB, 1467 views)
After i applied the update.zip, phone didnt reboot. I waited 5 mins phone turned cold, battery was cold as well...so i took the battery out and tried to turn on but no luck.
I hope the jug will help, otherwise i dont know what else to do.
Click to expand...
Click to collapse
Have you gotten your jig yet? Did it work?
Don't mean to sound negative, but I'm pretty sure a jig won't work. From what you posted it seems that the update.zip you posted broke your bootloader which is a guaranteed hard brick if true. You should still try if you want to, but if your bootloader really got messed up nothing will bring it back
Sent from my SGH-T959 using XDA App
Settai said:
Don't mean to sound negative, but I'm pretty sure a jig won't work. From what you posted it seems that the update.zip you posted broke your bootloader which is a guaranteed hard brick if true. You should still try if you want to, but if your bootloader really got messed up nothing will bring it back
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
waiiiit doesent odin 1.8.3 has bootloader flash option....wait ...., it does .,
and i think it is incredibly hard to hardbrick phone flashing things through CWM anyway ,ether you are very talented or u have bad luck.
LEAVE YOUR PHONE FOR 10 MIN CONNECTED TO WALL OUTLET , take out battery dont disconect the phone put the batt in leave it for 10 min take it out put it back in try to boot your phone, TRY TO JUMP START IT ,ANYWAY YOU LIKE IT (or gimme your phone)
people return countless phones because someone said its fup because wont turn on been there few times ,still got my phone i dont care how much c*** u gone tell me it wont work i still tell you it will only way i would consider phone usless its when internal sd would get messed up to the point that it wouldnt work at all because u cant reflash sd to work
jig ? what jig, my phone would not turn on for a day to boot back up after messing with it for some time trying to jump start it.
YEAHHHH, I SAID IT DAMIT !
yahase said:
Well my phone had hardware lock, which i was not able to use 3 button combos to get to recovery mode....so i found this thread.....
I just captured the JI6 OTA update files from one of my phones and found that T-mobile is
updating the SBL with the same file found in this thread, I'm using the same method as T-mobile
to install the new SBL so the chances for a brick are the same but if you are completely
stock just wait for the OTA update and have the phone swapped under warranty in the
event of a brick.
WARNING:
INSTALLING THIS CAN BRICK YOUR PHONE
this is safer than the odin method, but when messing with the phones bootloader
there is always a chance that you could end up with a paper weight (I bricked
one phone messing with this stuff).
Updated 10-15-2010
this is the fix for hardware locked phones in update.zip form
install the phone drivers which can be found at:
http://forum.xda-developers.com/showthread.php?t=728929
put update.zip on the internal sd card (the 12 gb one)
turn on USB debugging in Settings-->Applications-->Development
reboot into recovery, use the RebootRecovery.bat in adb.zip if you dont know
how to do that.
when in recovery use the vol up and down buttons to navigate and power button to
select reinstall packages
install will take about 20-30 seconds and will pause at "writing secondary bootlader" don't panic
the phone will reboot you should be unlocked (or bricked).
update.zip md5=3b32fab99049530d2185014340840a47
Attached Files
File Type: zip adb.zip (253.2 KB, 1153 views)
File Type: zip update.zip (645.5 KB, 1467 views)
After i applied the update.zip, phone didnt reboot. I waited 5 mins phone turned cold, battery was cold as well...so i took the battery out and tried to turn on but no luck.
I hope the jug will help, otherwise i dont know what else to do.
Click to expand...
Click to collapse
I'm in the same boat. A jig won't fix it because it's the boot loader. The only way to fix it is through a jtag. I took mine to a local repair shop that had one and got it to boot up, but it was still hardware locked because he had to use a i9000 boot loader. The T959 boot loaders weren't working for him. I tried updating through Kies a couple days later and it screwed up the boot loader again, so I'm sending it to Samsung. As long as they don't determine that it was modified or repaired already, they'll repair it under warranty. I just wish I can find out how much the repair would cost if they determine that the warranty is void.
Please Help me out.
I was using CynogenMod7 ROM. Could not write on my external SD card or mount it .
So decided to go back to Stock froyo firmware.
Tried ODIN to flash to my stock froyo firmware.
Had done it many many many a times earlier with success.
But ODIN could'nt complete the process, it kept on getting struck at Kernel and Factory some times.
Later thought there might be something wrong with bootloader.
Downloaded stock froyo bootloader.
Tried to ODIN the bootloader and got Struck at SBL many times ,Kept on trying then got struck at PARAM.
Removed the battery.
From than on NO Response what so ever combination buttons used.
No battery indicators,No light on Home keys, No signs of any power. Nothing Visible on screen & keys.
Tried usb JIG - no response.
Tried Ultimate UnBrick Resurrector-No response.
No lights .
Please solve my problem.
This may not work because I discovered this by accident. I bricked my phone so bad it looked like it wouldn't even turn on too. So, hopefully this works. Make sure you have your samsung drivers installed. Open Odin and connect the USB to the computer but not to the phone. Do a battery pull and do the three button boot, simultaneously connecting the USB to the phone. Most likely, nothing will happen. Hopefully, the phone will connect to Odin. Then, click start. That's right. Don't put any pit or tar files in, just click start. Hopefully, your phone will reboot to the vibrant screen and is stuck there. If it does, now you can reboot to download mode and Odin whatever files you wanted. If it doesn't work, just keep messing with the three button boot. I apologize for wasted time if it doesn't work. These steps are what I personally did on my phone. Hopefully, it works for you.
Sorry to say but I believe you have hard bricked your phone. If installing bootloaders goes wrong then your phone can turn into a paper weight. You could maybe try a jtag repair but I'm not sure it would help. You could call samsung and ask for a replacement, tell them you updated with kies or something but that's not exactly the truth
Sent from my SGH-T959 using Tapatalk
dr_rp1234 said:
Please Help me out.
I was using CynogenMod7 ROM. Could not write on my external SD card or mount it .
So decided to go back to Stock froyo firmware.
Tried ODIN to flash to my stock froyo firmware.
Had done it many many many a times earlier with success.
But ODIN could'nt complete the process, it kept on getting struck at Kernel and Factory some times.
Later thought there might be something wrong with bootloader.
Downloaded stock froyo bootloader.
Tried to ODIN the bootloader and got Struck at SBL many times ,Kept on trying then got struck at PARAM.
Removed the battery.
From than on NO Response what so ever combination buttons used.
No battery indicators,No light on Home keys, No signs of any power. Nothing Visible on screen & keys.
Tried usb JIG - no response.
Tried Ultimate UnBrick Resurrector-No response.
No lights .
Please solve my problem.
Click to expand...
Click to collapse
OK first, the stock images are 2.1 eclair not 2.2 froyo. Are you sure you have the right files? Are you sure your phone is a t959(3g, no front camera)and not t959v(4g, has front camera). Second, it sounds like a hard brick, if all else fails go to www.mobiletechvideos.com and check out the unbrickable mod and JTAG repair.
If you get your phone in DL mode and you have the correct Odin images, check the repartition box as well as others and run it.
Good luck
sent from my magic box to yours
Remove battery and sim and microsd. Leave out and press and hold power for 30 seconds or so. Leave battery out for a few minutes.
Put battery in and if you are on GB bootloader hold volume up and plug in USB. Might get you to download mode.
I did that with a friends phone about a year ago and got lucky. Odin recognized it. I read that somewhere here on XDA. May be a shot in the dark... but when you get desperate any new ideas to try can be a relief right?
Good luck to you.
After I messed with bootloaders and then tried to get back to stock with Kies I had this problem.
iTz KeeFy said:
You could call samsung and ask for a replacement, tell them you updated with kies or something but that's not exactly the truth
Click to expand...
Click to collapse
I called Samsung and told them that I was just trying to upgrade to 2.2 with their software and they replaced my PCB (printed circuit board) for no cost (including shipping). I have no idea if they tried to figure out if I had really used Kies (if they could even figure it out with the state my phone was in) or if they just replaced the PCB blindly. Worth a shot, I'd say!
Thanks for your concern.
Zeferden said:
This may not work because I discovered this by accident. I bricked my phone so bad it looked like it wouldn't even turn on too. So, hopefully this works. Make sure you have your samsung drivers installed. Open Odin and connect the USB to the computer but not to the phone. Do a battery pull and do the three button boot, simultaneously connecting the USB to the phone. Most likely, nothing will happen. Hopefully, the phone will connect to Odin. Then, click start. That's right. Don't put any pit or tar files in, just click start. Hopefully, your phone will reboot to the vibrant screen and is stuck there. If it does, now you can reboot to download mode and Odin whatever files you wanted. If it doesn't work, just keep messing with the three button boot. I apologize for wasted time if it doesn't work. These steps are what I personally did on my phone. Hopefully, it works for you.
Click to expand...
Click to collapse
Thanks for your concern.
But it did not work for me.
thanks
iTz KeeFy said:
Sorry to say but I believe you have hard bricked your phone. If installing bootloaders goes wrong then your phone can turn into a paper weight. You could maybe try a jtag repair but I'm not sure it would help. You could call samsung and ask for a replacement, tell them you updated with kies or something but that's not exactly the truth
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Thanks for your concern
Its T mobile vibrant T959.
Its T-mobile Vibrant T959 without a front camera.
Totally no response.
No lights on soft keys ( Menu,Home,Back,Search)
No response even When connected with wall charger or PC.
Please help.
Thanks
dr_rp1234 said:
Its T-mobile Vibrant T959 without a front camera.
Totally no response.
No lights on soft keys ( Menu,Home,Back,Search)
No response even When connected with wall charger or PC.
Please help.
Thanks
Click to expand...
Click to collapse
Sorry to say this but your phone is hard bricked, as in nothing can save it but a JTAG or warranty service. You can try to call Samsung and say you hard bricked your phone cause of kies, it worked for another.
Sent from Mount Olympus via Hermes.
you can try this, it works for many user
http://forum.xda-developers.com/showthread.php?p=17858853#post17858853
HELP!
I need help with my Samsung galaxy SGH-T959 Vibrant I got bricked so I was fixing it with odin until my phone fell and it disconnected and red letters and numbers came out. when I try turning my phone on it doesn't until I press the buttons to go to download mode those red numbers come out and I can't do anything. Please Help
When you pulled the battery, after it hung up with Odin, you corrupted the primary Bootloader, because it wasn't completely written in......Last weak possible option is to try every rocker/battery/cable sequence ETC, to get Odin to handshake with the phone!!.....If there's still no sign of life after doing that....Your only option will be to have it JTAG,d in order to rewrite the primary bootloader file back in it.....it'll never power on unless the primary bootloader executes properly!!....you can corrupt the 2ndary BL and the phone will only be soft bricked, but a primary BL corruption is phone DEATH!!....Only place I know of that's reliable is: mobiletechvideos.com....send it to them, they'll rewrite the primary BL back in it and I think 2.1 or 2.2 for you and mail the phone back to you!!....Good luck let us know if you got it powered on with any combination, as that could save another Bricker from having to send it out!!
Randomness Guy........Start your own thread in the troubleshooting forum, AND QUIT TRYING TO HIJACK THIS THREAD!!
i wiped everything including a factory reset then installed liquid rc8 i used correct one for my phone it rebooted but never booted up to the samsung logo doesnt seem to vibrate or anything when i press power wtf?
now when i plug it into pc it shows my external drive then it vanishes then re-appaears and tells me to format it but that doesnt work either
Put in download mode and Odin back to stock.
How full was your battery when you started? May have drained it
Sent from my SAMSUNG-SGH-I717 using xda premium
leo5111 said:
i wiped everything including a factory reset then installed liquid rc8 i used correct one for my phone it rebooted but never booted up to the samsung logo doesnt seem to vibrate or anything when i press power wtf?
Click to expand...
Click to collapse
If you can get back into recovery mode, try reflashing the rom or flashing another rom. I've had cases where a rom just wouldn't work for me (I too, have the AT&T Note). Never had the patience to try to figure out why. I usually try to flash several times (making sure I do a factory wipe) but if it still didn't work, I would just flash another rom.
If you can't get into recovery mode, then you may need to flash a stock rom via ODIN (in download mode) and then start all over from scratch (root the phone, install CMW or TWRP,flash custom rom, etc.). Please search the forums for a stock rom and all the files / instructions on flashing via ODIN if you aren't already familiar with it.
Since your PC recognizes the phone to some degree (it at least recognizes that the phone was connected and interacts with the sd card), it sounds like you have a soft brick which is fixable via one of the methods above. If your phone was hard bricked, then the PC more than likely wouldn't recognize it at all, it would do absolutely nothing and you would basically have a paper weight. It doesn't sound like you have a hard brick.
If anyone else has more insight, please chime in. I'm definitely no expert here.
it wont even light up to samsung logo or even vibrate also the sd is recognised but it randomly connects and disconnects odin does not see phone
leo5111 said:
it wont even light up to samsung logo or even vibrate also the sd is recognised but it randomly connects and disconnects odin does not see phone
Click to expand...
Click to collapse
Perhaps your cable is defective. All of my cables eventually get to the point where I have to twist them and hold them a certain way to work. When that happens I know it's time to replace the cable. You may just need to use another cable.
no i tried with 2 differnt cables also battery was at like 99% when this happened also windows keeps finding my sd for a moment and then vanishes could this be stuck power button? if so i dont see how i didnt touch power button when it rebooted
show tnsraet
leo5111 said:
no i tried with 2 differnt cables also battery was at like 99% when this happened also windows keeps finding my sd for a moment and then vanishes could this be stuck power button? if so i dont see how i didnt touch power button when it rebooted
Click to expand...
Click to collapse
having the exact same issue, did you get this resolved?
Dark_lupus said:
having the exact same issue, did you get this resolved?
Click to expand...
Click to collapse
in star trek speak, she,s dead jim :crying:
leo5111 said:
in star trek speak, she,s dead jim :crying:
Click to expand...
Click to collapse
I'm sorry man hopefully I can fix mine I've been told I performed my whole process of flashing roms right but I don't understand why my phones dont work one new and the other a couple months old...
I put up a thread but not much help from anybody.
Hummmm this just don't sound right.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2