First and foremost I have read through tons of pointless threads which led me no where. Soo I recently rooted my at&t galaxy note with no problem (triumph) went a few days with no problems. After an attempt to update CWM I lost the availability to go into recovery; I went to do a factory reset and now it wont allow me to do anything. So I attempted to boot into cwm (no luck) tried finger configuration e.g. up, down, power and so on (no luck) booting into Odin mode works. So i assume this is a soft brick buuut Odin wont recognize the device (i dont see the 0:[COM4]). I have all drivers, uninstalled and re installed erased and re downloaded Odin still nothing. Ive all but given up (ordered a HTC1s just in case). Anyone know something I missing? In advance Im looking for fixes thanks for your patience and understanding with this debockle.
waterstander said:
First and foremost I have read through tons of pointless threads which led me no where. Soo I recently rooted my at&t galaxy note with no problem (triumph) went a few days with no problems. After an attempt to update CWM I lost the availability to go into recovery; I went to do a factory reset and now it wont allow me to do anything. So I attempted to boot into cwm (no luck) tried finger configuration e.g. up, down, power and so on (no luck) booting into Odin mode works. So i assume this is a soft brick buuut Odin wont recognize the device (i dont see the 0:[COM4]). I have all drivers, uninstalled and re installed erased and re downloaded Odin still nothing. Ive all but given up (ordered a HTC1s just in case). Anyone know something I missing? In advance Im looking for fixes thanks for your patience and understanding with this debockle.
Click to expand...
Click to collapse
Some ideas
try different pc or different usb
try different Odin...see my signature for GNote Everything page...
http://forum.xda-developers.com/showthread.php?p=28040353#post28040353
if you can get to Odin you can fix it...
I know you said you uninstalled I would try it again, then try diff usb
good luck
Are you able to get phone into download mode?
Sent from my SAMSUNG-SGH-I717 using xda premium
waterstander said:
First and foremost I have read through tons of pointless threads which led me no where. Soo I recently rooted my at&t galaxy note with no problem (triumph) went a few days with no problems. After an attempt to update CWM I lost the availability to go into recovery; I went to do a factory reset and now it wont allow me to do anything. So I attempted to boot into cwm (no luck) tried finger configuration e.g. up, down, power and so on (no luck) booting into Odin mode works. So i assume this is a soft brick buuut Odin wont recognize the device (i dont see the 0:[COM4]). I have all drivers, uninstalled and re installed erased and re downloaded Odin still nothing. Ive all but given up (ordered a HTC1s just in case). Anyone know something I missing? In advance Im looking for fixes thanks for your patience and understanding with this debockle.
Click to expand...
Click to collapse
Maybe this will help
http://forum.xda-developers.com/showthread.php?t=1586223
Sent from my SAMSUNG-SGH-I717 using xda premium
Check your usb cord. Mine recently softbricked due to a faulty usb cord. I also changed usb ports.
Sent from my SAMSUNG-SGH-I717 using xda premium
Thanks everyone for the info but after a break and some stumbling around, Kies allowed me to factory reset even though my device wasn't being recognized by the computer (go figure). I'm now up an running cheers to all the helpful comments
Sent from my SAMSUNG-SGH-I717 using xda premium
waterstander said:
Thanks everyone for the info but after a break and some stumbling around, Kies allowed me to factory reset even though my device wasn't being recognized by the computer (go figure). I'm now up an running cheers to all the helpful comments
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
great glad it worked out...can you pls put solved in your title...thx
Related
Hi to everyone! Is my first thread here. I have a Samsung Vibrant SGH-T959 and try to update using Odin3 v1.85. Everything go well but at end apear Fail in Odin and the phone turn off. I think the phone go to restart but never turn on again and I can't turn on now. I press power botton and no response. I try to put it in download mode or recovery mode and I can't. What is next? I order a JIG, but a friend told me that no correct my problem.
One does not update via Odin (well 99% of the time IMO) Odin is usually used to revert to stock and reset partitions.
Did you have the repartition checked?
Did you try and flash a ROM or Boot loaders?
When you hook the phone to the computer and open up Odin does it still show a yellow box? If so flash back to JFD and start over.
If you tried to flash bootloaders your only hope of unbricking it may be a JTAG service (google it).
It may be late for you now...but a warning to others - Messing with Odin is one of the quickest ways to brick your phone. I dont think Ive ever actually heard of anyone hard brick a T959 without Odin.
Unless your updating the boot loader hard brick is near impossible. Odin is not to blame, and the risk is negligible.
My vibrant died a few days ago reverting to stock to deposit a check (so GPS would work). Sounds like the phone just died. Mine is hardware dead and sounds just like yours. Wont turn on or acknowledge a current when plugged into the charger.
BTW: Unlike some other phones, if you click re-partition on the Vibrant and have the pit file. You can repartition and it not muck up the phone... well unless the repartitioning itself went AWOL.
Moped_Ryder said:
One does not update via Odin (well 99% of the time IMO) Odin is usually used to revert to stock and reset partitions.
It may be late for you now...but a warning to others - Messing with Odin is one of the quickest ways to brick your phone. I dont think Ive ever actually heard of anyone hard brick a T959 without Odin.
Click to expand...
Click to collapse
I agree with ya Moped_Ryder about the quirks of using Odin, although Ive never had a problem with it, as long as I do or don't tick the wrong buttons or try flashing the wrong SW for the wrong application ETC ETC!!
Ironically, a half a day too late, I found out about the dangers and horrors of using the Samsung Kies update, and that was what BRICKED my phone, Its corrupted the primary and 2ndary Boot-loaders, BUT again it wasn't ODIN that did it!! Personally I use CWM to flash anything above stock JFD.
BTW I JUST INSTALLED YOUR ROM GREAT WORK, IVE NEVER SEEN FROYO ACT AND PERFORM SO WELL! WHY WOULD I REVERT BACK TO FROYO, BECAUSE IVE HAD TOO MANY WEIRD PROBLEMS WITH ALL THE ICS's and Froyo cured all the app problems I needed working and plus Ive got the loud ringtone again ETC ETC!! Only thing I miss. Is not being able to use my FFC I modded the phone with. I'm wondering if there is a way to port that part of the needed SW into your Froyo to support FFC's Sometimes Old is better, but to each their own!! Anyway great job, Thanks a ton!!
Unfortunately you have a hard brick. I know, I did the same thing. Fortunately it doesn't mean your phone is toast. Go to mobiletechvideos.com, you need a JTAG service. I also recommend the Unbrickable Mod. They can do that service for you. You can find out more about unbrickable mod, search in xda. Good luck!
Sent from my SGH-T959 using xda premium
Don't necessarily give up.
My phone was doing the same thing after I screwed up a flash. The screen would not light up and there was no indication of the phone powering up at all no matter what I did. Tried all sorts of tricks (researched from XDA) to get into download mode or otherwise get it to at least partially boot, aboslutely nothing worked. Out of desperation, I found a guy within driving distance of me that sold jigs, got one within a couple of hours. Popped the jig into my phone, went right into download mode, flashed stock no problem. Phone has worked fine ever since.
Don't give up. Hopefully the jig will work.
I had a similar issue with my phone after using Odin,it was completely hard bricked. As I am in Europe no possibility for Jtag but I found the Unbrickable Mod by Adam Outler. Using it you really need very good soldering skills. If you're not good with that try to find someone to do it on any electronic repairs or something, that's the way that I did,it will cost you few bucks.
Sent from my SGH-T959 using XDA
You cannot brick this phone. I thought I bricked mine a couple times and panicked like hell only to have fixed the problem. Odin is reverting back to 2.1 or 2.2 if you mess up. If you are having trouble with Odin, try Heimdall. As far as turning your phone on, take out the battery, put it back in, plug in usb with odin or heimdall running, volume up and down while pressing power button. Hold this until download mode shows up. odin back to stock. After this, try re-flashing the new firmware you tried, but read the developers instructions again before doing so. I hope this helped
Even if you brick the phone hopelessly with a bad bootloader flash, it's not really lost. If you Google something like "Vibrant jtag repair" you'll find that you can get you phone fixed.
can you help me for sgh-t959v
skayalgomas said:
Hi to everyone! Is my first thread here. I have a Samsung Vibrant SGH-T959 and try to update using Odin3 v1.85. Everything go well but at end apear Fail in Odin and the phone turn off. I think the phone go to restart but never turn on again and I can't turn on now. I press power botton and no response. I try to put it in download mode or recovery mode and I can't. What is next? I order a JIG, but a friend told me that no correct my problem.
Click to expand...
Click to collapse
i downloaded the .tar file 2.2.3 for sgh-t959v for flashing my phone
but odine failed the process and now my device is even not getting turned on.
my name is sourabh mattu
mail id is [email protected]
phn. +919217574416
Hi, so i have a galaxy s2 and i was running LiteningRom 2.7 (which when i updated it to you didn't have to wipe memory before flashing..) Anyway yesterday i tried to updated to the new 2.9 version of LiteningRom and i didn't wipe memory/cache and it failed half way through with odin.
this brought up the little Phone-Triangle-PC icon on the screen, and i could get it back into Download mode, so then i followed a tutorial i seen on the internet, i downloaded the 2 Files for the stock firmware MD5 and or PIT i cant think.
Note: the files were for SGSI9100G
under the battery my s2 is the SGSI9100GSMH
so anyway the tutorial told me to check "Re-Partition"
so i did and it got half way through and it failed again but now
the phone will not do anything at all :/
cannot establish a link with odin via USB
cannon boot the phone/no lights/no vibrations/no screen on
it would seem im in deep doo-doo thought i might as well ask on here though as i am now phone-less and its terrible haha.
P.S i have tried the "jig" to force it into Download mode and it does nothing,
it would seem as if the boot loader is not even on the device anymore.
Please help and any advice would be greatly appreciated
misterashman said:
Hi, so i have a galaxy s2 and i was running LiteningRom 2.7 (which when i updated it to you didn't have to wipe memory before flashing..) Anyway yesterday i tried to updated to the new 2.9 version of LiteningRom and i didn't wipe memory/cache and it failed half way through with odin.
this brought up the little Phone-Triangle-PC icon on the screen, and i could get it back into Download mode, so then i followed a tutorial i seen on the internet, i downloaded the 2 Files for the stock firmware MD5 and or PIT i cant think.
Note: the files were for SGSI9100G
under the battery my s2 is the SGSI9100GSMH
so anyway the tutorial told me to check "Re-Partition"
so i did and it got half way through and it failed again but now
the phone will not do anything at all :/
cannot establish a link with odin via USB
cannon boot the phone/no lights/no vibrations/no screen on
it would seem im in deep doo-doo thought i might as well ask on here though as i am now phone-less and its terrible haha.
P.S i have tried the "jig" to force it into Download mode and it does nothing,
it would seem as if the boot loader is not even on the device anymore.
Please help and any advice would be greatly appreciated
Click to expand...
Click to collapse
I9100GSMH is a i9100. Not an i9100G.
If none of the three button combos work and the jig too then enjoy:
http://forum.xda-developers.com/showthread.php?t=1192853
Sent from my GT-I9100 using Tapatalk 2
It's either jtag or service centet for you pal.
Sent from my GT-I9100 using xda premium
Thanks guy's ill see what i can do.
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
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