-----------------
---This first post is outdated. My current question is one post below. I've left the content of this post for other noobs to see.
-----------------
Hey folks, sorry to bother you all but all input would be greatly appreciated. I'm rather unfamiliar with android flashing and kernels, and have spent the last 8 hours trying to figure this out to no avail.
Following this (http://forum.xda-developers.com/showthread.php?t=1238070) (section 5) guide on how to get back to stock gingerbread on my phone (after a few partially failed attempts flashing other roms), I was using Odin, had the .pit 2.2 as well as CI500_VZW_EH03_GB_CM.tar.md5 loaded into the program and left it running. About 20 mins in, the phone stopped progressing and I started to get concerned. After two hours, I powered down the phone and proceeded to reattempt the flash. This is when things got weird. My phone was unable to enter the Download Mode and instead showed Android system recovery when plugged in, or a black screen with a phone and a computer, with arrows between when not plugged in. The weirdest part is that the phone no longer recognized vol+ or the power button when in Android Recovery, and could only vol- to go down the menu, then was stuck at the bottom of the list.
I've searched everywhere on this site, and google to try and come up with a solution.
When pluggin into the computer, I hear a connection sound, but the device is not recognized by Odin. Pressing the running a blind vol+ and vol-, then a vol- to hope Odin recognizes the device, as pointed out in this (http://forum.xda-developers.com/showthread.php?t=1764022) thread, resulted in nothing. Holding vol- while pluggin in the usb cable, doesn't show the download mode. All of the steps in this (http://forum.xda-developers.com/showthread.php?t=1026746) thread proved futile, as most of them required download mode anyways.
I'm going to keep searching and keep you posted as things come. Your help as always will be greatly appreciated!
Edit: Things just got weirder... After a few more attempts at making this work, I'm now getting an "Unable to charge non-supported battery. See user manual." With this error, I'm not able to get into Android Recovery anymore. More searching...
Edit 2: AFAIK I'm gonna need a jig. Anyone confirm?
Edit 3: Got a jig, Download Mode working, all is well. Please remove this thread, or leave it for other noob flashers to see.
Hey Folks, its been a while since I last posted in this forum, but I ran into a pretty serious issue earlier this evening. I was attempting to flash CM9 to my T959D and was running into tonnes of trouble. Throughout my attempts I was restoring back to stock rom, kernel and bootloader. During one of these restores, Odin froze in Win 7. Since then I've been unable to detect any form of life from the phone. It simply sits in a black screen. Holding the vol down while booting, blind vol up and down cable inserting, using my Jig and inserting the cable/battery in various orders results in nothing. The most I hear is a device failure to connect sound in Windows with no sign of life in Odin.
What can I do?
Someone posted stating leaving the battery out for multiple days would reset something on the motherboard, allowing me to get into download mode. Though I was hoping to have this resolved tonight. I realize that there aren't many people left with these phones, but I hope someone has a solution to this.
I'm going to be installing ubuntu tonight on an older desktop in a effort to resolve this. Though my experience with it is very limited, and success is unknown.
NOT GOOD... You should wait and see if others have a better solution, but Unbrickable Mod may be your only option.
Posted from my Fascinate using XDA Premium
MultipleMonomials said:
NOT GOOD... You should wait and see if others have a better solution, but Unbrickable Mod may be your only option.
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
Thats not good to hear. Well, I was snooping around looking for someone who could solder this for me, to no avail. My soldering skills are non existent. The most I fixed was a door bell, and I did a terrible job. I won't be able to get my hands on a soldering iron until tomorrow, is it worth trying?
I have located someone who can do a jtag on this model but have a few questions in regards to this:
Since my bootloader was corrupted, would the jtag service put a new bootloader on?
Would it prevent the same thing from happening again?
Are jtags designed on a per-phone basis?
Since there is a telus fascinate T959D as well as a verizon fascinate, and both phones are completely different, would I need to make sure the jtag is meant for this phone?
Is there anything I need to be made aware of before doing this that I haven't mentioned?
I've haven't had any experience with JTAG, but I've heard Unbrickable Mod is preferable. If you're looking for someone who can solder, check out your local RC/hobby store. If that fails, check out an electronics store, though it may take some searching to find one.
Posted from my Galaxy Tab with CM10
TheMegosh said:
Thats not good to hear. Well, I was snooping around looking for someone who could solder this for me, to no avail. My soldering skills are non existent. The most I fixed was a door bell, and I did a terrible job. I won't be able to get my hands on a soldering iron until tomorrow, is it worth trying?
I have located someone who can do a jtag on this model but have a few questions in regards to this:
Since my bootloader was corrupted, would the jtag service put a new bootloader on?
Would it prevent the same thing from happening again?
Are jtags designed on a per-phone basis?
Since there is a telus fascinate T959D as well as a verizon fascinate, and both phones are completely different, would I need to make sure the jtag is meant for this phone?
Is there anything I need to be made aware of before doing this that I haven't mentioned?
Click to expand...
Click to collapse
Make sure you use the stock Samsung cable see if you can reinstall the drivers hook it into the computer and hold volume down if you can get any type of signal from the phone your good.
Sent from my SCH-I500 using Tapatalk 2
---------- Post added at 04:27 PM ---------- Previous post was at 04:24 PM ----------
MultipleMonomials said:
I've haven't had any experience with JTAG, but I've heard Unbrickable Mod is preferable. If you're looking for someone who can solder, check out your local RC/hobby store. If that fails, check out an electronics store, though it may take some searching to find one.
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
Hey no offence but stop telling everyone on the street they need too soljeir there phone with unbrickable mod before they can fix I'm tired of having too calm the person down after you said they have too open up the phone its utter bull****. 1 out of 10 soft bricks you may need it I've been without download mode and fixed mine just fine.
Sent from my SCH-I500 using Tapatalk 2
An update:
Took my phone in to get the jtag service... He said some of my partitions were corrupted, one of which was the boot layer. He put a new bootloader on, and showed it could be placed back into recovery and download mode, but when I got home the device was even more dead than when I left; no device failed to connect sound in windows, just nothing. I'm taking it back to him in a week after exams to get this resolved. Maybe the battery has reached the end of its life...? I checked it with a volt meter, and it had 3v+ so I really don't know.
Sent using Science!
As bbrad pointed out, there may be other solutions, and my answer could be totally wrong, but if even your bootloader is cooked, Unbrickable Mod may be your only hope. Since UM affects startup code literally hardwired into the chip, it should work as long as the JTAG doesn't interfere.
Posted from my Fascinate using XDA Premium
Another update. So apparently I flashed a bootloader from another phone, which royally screwed up the partition, kernel and mounted drives. The technician managed to get the original bootloader, kernel and rom on the phone and everything is working from stock again.
Why on earth is the 959d Telus version such a pain in the ass to customize?
Is there anyone on here that uses a 959d that can direct me to a proper method to leaving stock? Before this entire situation I had vodoo kernel on, with cwm, but every time I flashed a kernel it would hang on reboot and either sit on a black or white screen. In a lot of cases I would flash in cwm, reboot, then I would be brought back to cwm as if there was no rom on the phone at all, no matter what I formatted and wiped.
When I'm not on my phone I can link all of the guides I've tried that leave me back where I started. So I re flash back to stock using Odin.
At the end of the day, I have to ask, is it really worth it in the end? I've rooted and flashed many roms on other phones but have never run into as many problems as with this fascinate t959d
Sent using Science!
Related
I am beginning to think it isn't actually possible. I've tried everything, but I can't seem to brick my Vibrant to a point that I can't recover and Odin back to life. I read that flashing ROMs over bootloaders that aren't compatible can do it, but I was still able to force DL mode (never used a jig--haven't had a need yet) and Odin to stock even after doing that.
I say "with experience" because it is obvious that there are probably thousands of Vibrants that either hit the trash or are sitting in desk drawers somewhere..."bricked." I consider myself experienced with this phone. Been flashing on it for a year, tweaking signal settings, build.prop settings, and scheduler settings. The guys on here that have abused and really pushed their devices to discover the limitations are the ones who I want to hear from if possible. I don't particularly know if, short of dunking it in my coffee, I can be more abusive to this thing. This is one limitation I haven't yet discovered. Is it TRULY unbrickable?
It is possible. I have bricked 2 - most of the older devs have bricked at least one. This sucks for the guys that did the bricking but is good for the guys just starting out because they come into it knowing what not to do.
True bricks generally come about by way of flashing an incorrect sbl or have even happened by interrupting the flashing of a proper sbl.
Most non sbl "bricks", however, are nothing more than soft bricks that patience and perseverance will remedy.
I bricked my phone twice since I started rooting my vibrant. The first one when the usb disconnected from the laptop while it was half way odin. The second time was a hardware brick. The phone just simply has no light lolz. What happened was that I selected all the checkboxes when I odin the GB loader. However, I was able to bring her back to life after trying every possible combination while my heart was pumping 3,000 gallons of my blood in every minutes and my forehead was soaking with smelling sweat. lolz
Oh it can be done, install gb bootloaders from the old days, through light roms, flash the original axura rom, try to flash to stock. spend a week with a black screen, get warranty. Bootloaders are the kiss of death. Odin really only works if you can boot, and p.c. recognizes, through yellow com. If you dont have that your attitude will change dramatically. Youve only had soft bricks, not "The BlackScreen Of Death"
okies try harder, yada yada, yada
yea just try to update your phone using kies
Sent from my T959 using XDA App
S#*T, how could anyone forget, my bad....
jellette said:
It is possible. I have bricked 2 - most of the older devs have bricked at least one. This sucks for the guys that did the bricking but is good for the guys just starting out because they come into it knowing what not to do.
True bricks generally come about by way of flashing an incorrect sbl or have even happened by interrupting the flashing of a proper sbl.
Most non sbl "bricks", however, are nothing more than soft bricks that patience and perseverance will remedy.
Click to expand...
Click to collapse
And I definitely do appreciate the work that you guys do--I was sitting nearly in tears (ok, maybe a little buzz brought the tears) about a month after I bought my vibrant in October 2010. The kid in the T-Mobile store actually rooted it for me when I went back for some help with my bill, so I had access to files that I didn't know what to do with. I tried to apply some crap theme that, at the time, I thought destroyed my phone and turned it into a piece of $400 coffee table art. My wife would have probably beaten me if I hadn't discovered XDA and the brilliant work you guys do. After that little ordeal, I got heavy into reading the threads here and slowly but surely, got pretty fearless thanks to the research you guys had already done for me.
One other question for you: If you had those bricked phones today, would you be able to revive them after an sbl brick?
I believe even the worst brick can be fixed via JTAG Service.
from my understanding and from my noob experiences this phone is unbrickable
Don't forget about the hardware mod that let's you flash boot loaders
Sent from my SGH-T959 using XDA Premium App
It's NOT unbrickable. It's just hard to, unless if your just a total absolute idiot or a accident happens. I know my dogs pulled my usb cord while i was odining once, it caused a brick.
As the vibrant and the sgs are nearly the same, I've never bricked it at all... I just lost my IMEI that's all but that doesn't seem to make any problems at all. That's the only bad thing that happened to me : )
xriderx66 said:
It's NOT unbrickable. It's just hard to, unless if your just a total absolute idiot or a accident happens. I know my dogs pulled my usb cord while i was odining once, it caused a brick.
Click to expand...
Click to collapse
It is unbrickable you can fix it even if bootloader get deleted the only way you can brick it is if USB port is broken
Sent from my GT-I9000 using XDA App
Hi,
I've soft bricked my phone several times and restored it with no problems till last night. I had GB bootloader on my vibrant flashed back stock rom using odin and then upgraded to stock 2.2 rom using KIES. Now phone is not responding to anything. I've spend hours on forums and chats i've tried almost every thing and nothing could bring back my phone I even let it chard over night like some people say did not help.
Please let me know if there any way to restore it? Again it has GB bootloader with stock 2.1 and than upgraded to stock 2.2 via KIES.
Thanks in advance!
Did u get a USB jig yet that should work
Sent from my SGH-T959 using XDA App
manus ferrera said:
Did u get a USB jig yet that should work
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
No not yet...I still want to find a way to restore it without JIG. It should be a way!
I think problem is that most of solutions where posted for Vibrant stock Bootloader not a GB Bootloader. May be there are different steps are required for GB Bootloaders. I don't want to give up
With GB BL you have to use vol+ and power to get into download mode. Just an fyi in case you didnt know.
What he said!
bfranklin1986 said:
yea just try to update your phone using kies
Sent from my T959 using XDA App
Click to expand...
Click to collapse
Thats exactly how I bricked mine, and found out a day after by stumbling across a thread on the dangers of using KIES, when I was newbee dumb!
Also, if you can power the phone on in any way shape or form, meaning if you see anything on the screen, or the LED's illuminate, then you are NOT HARDBRICKED, that is still a softbrick senario!!
And BTW the primary Btloader is what powers the phone one, and the 2ndary Btloader is what loads the OS or ROM!
And when the primary is corrupted, that's a TRUE HARDBRICK scenario, because if you cant power the phone on, then nothing short of JTAGing it , will resurrect it!!
Although Adam Outler, supposedly has a Resurrection program, to JTAG the solder-less way, using pin point test probes and his Resurrection program, to inject and re-flash the Btloaders and thus, bring a dead non powered phone to life!
Link to Adam's Work: http://forum.xda-developers.com/showthread.php?t=1397393
---------- Post added at 11:09 AM ---------- Previous post was at 10:58 AM ----------
anatoliyus said:
No not yet...I still want to find a way to restore it without JIG. It should be a way!
I think problem is that most of solutions where posted for Vibrant stock Bootloader not a GB Bootloader. May be there are different steps are required for GB Bootloaders. I don't want to give up
Click to expand...
Click to collapse
A JIG will not work, if the primary Bootloader is corrupted it wont power on , JIG's only work with phones that will power on, and in his case he corrupted the primary, and only JTAGing it will resurrect it, unless he has the intelligence to try this alternative below, otherwise send it to Adam or TechMobile, the only two guys I know who are true Ninja's with this type of micro surgery!
http://forum.xda-developers.com/showthread.php?t=1397393
It sucks...Just 2 weeks ago I've installed FFC, ordered 1800 Battery...invested money.
Don't want to spend any more money on this old cell phone I may just go and buy new phone then.
---------- Post added at 05:19 AM ---------- Previous post was at 04:48 AM ----------
dseldown said:
Thats exactly how I bricked mine, and found out a day after by stumbling across a thread on the dangers of using KIES, when I was newbee dumb!
Also, if you can power the phone on in any way shape or form, meaning if you see anything on the screen, or the LED's illuminate, then you are NOT HARDBRICKED, that is still a softbrick senario!!
And BTW the primary Btloader is what powers the phone one, and the 2ndary Btloader is what loads the OS or ROM!
And when the primary is corrupted, that's a TRUE HARDBRICK scenario, because if you cant power the phone on, then nothing short of JTAGing it , will resurrect it!!
Although Adam Outler, supposedly has a Resurrection program, to JTAG the solder-less way, using pin point test probes and his Resurrection program, to inject and re-flash the Btloaders and thus, bring a dead non powered phone to life!
Link to Adam's Work: http://forum.xda-developers.com/showthread.php?t=1397393
---------- Post added at 11:09 AM ---------- Previous post was at 10:58 AM ----------
A JIG will not work, if the primary Bootloader is corrupted it wont power on , JIG's only work with phones that will power on, and in his case he corrupted the primary, and only JTAGing it will resurrect it, unless he has the intelligence to try this alternative below, otherwise send it to Adam or TechMobile, the only two guys I know who are true Ninja's with this type of micro surgery!
http://forum.xda-developers.com/showthread.php?t=1397393
Click to expand...
Click to collapse
Thanks...will try this solution. Downloading Ubuntu...
heysoos said:
I am beginning to think it isn't actually possible. I've tried everything, but I can't seem to brick my Vibrant to a point that I can't recover and Odin back to life. I read that flashing ROMs over bootloaders that aren't compatible can do it, but I was still able to force DL mode (never used a jig--haven't had a need yet) and Odin to stock even after doing that.
I say "with experience" because it is obvious that there are probably thousands of Vibrants that either hit the trash or are sitting in desk drawers somewhere..."bricked." I consider myself experienced with this phone. Been flashing on it for a year, tweaking signal settings, build.prop settings, and scheduler settings. The guys on here that have abused and really pushed their devices to discover the limitations are the ones who I want to hear from if possible. I don't particularly know if, short of dunking it in my coffee, I can be more abusive to this thing. This is one limitation I haven't yet discovered. Is it TRULY unbrickable?
Click to expand...
Click to collapse
There are several of us that have including myself, heathen and Eugene just to name a few. We've actually taken the bullet previously so you don't have to. We pretty much know now what will cause a hard brick and that's why you rarely here of one now.
Sent from my SGH-T959 using xda premium
call me a noob, but i thought that Odin was taking too long (45 mins)(tried to switch from CM7 to stock firmware) and was stuck, so i closed out and turned off my phone by taking out the battery (idiot, i know) and now my phone wont turn on, and ive tried taking out the battery, pressing a number of button combos, and the people at radioshack didnt help (big suprise). any ideas?
Try holding the power button alone, for like 15 or more seconds.
Not sure beyond that....
didnt help...what i think the problem is that i dont have a firmware on my phone to boot it from...
You need enter download mode. It's not clear from your post if you tried to enter download mode or not. Can you get into download mode? Do you have a jig?
Btw, 45 minutes was definitely too long for Odin, so there probably wasn't any thing else you could have done.
no, i cannot get into download mode, and i do not have a jig. would that fix the problem completely?
Unsure - seems like somehow you killed your bootloader, not sure how since no return-to-stock package has bootloaders.
You should be able to get into download mode by this method: With the phone powered off, plug in the usb cable while holding the vol up + vol down buttons (but not the power button). When the warning screen appears, press Volume up to continue into download mode.
The jig is just another way to get into download mode, and certainly worth a try if you have one or can borrow one. With the phone powered off, plug in the jig, and the phone will immediately go into download mode.
You must have enough charge on the battery for the phone to turn on.
If the battery has charge, and you are unable to get into download mode by any method, and if you are unable to get any signs of life from your phone in any way, then as Entropy said, you may have damaged bootloaders.
The only way to damage one of the bootloaders, as far as I know, is for Odin to be interrupted while it is flashing the bootloader. So this begs the question, what exactly were you trying to flash that didn't complete in 45 minutes?
If your phone is truely hard bricked, the only way to recover it is to send it to a professional like connexion2005 of Mobile Tech Videos who can use jtag to reset the bootloaders.
Oh oh, I feel bad for the OP.
People keep saying this device is "unbrickable" but apparently not.
votinh said:
Oh oh, I feel bad for the OP.
People keep saying this device is "unbrickable" but apparently not.
Click to expand...
Click to collapse
He should be able to clear it with a jig, but no one can guarantee that this will work. I have seen it fix this issue before though.
votinh said:
Oh oh, I feel bad for the OP.
People keep saying this device is "unbrickable" but apparently not.
Click to expand...
Click to collapse
No one claims it's unbrickable - just that it's damned hard to brick.
I'm still curious what he was trying to flash - I have NEVER heard of anyone hardbricking their devices unless:
1) They screwed with bootloaders - which is why I have included gigantic red warnings with anything I post that includes a bootloader
2) They flashed something not intended for the device
Iskor12 said:
He should be able to clear it with a jig, but no one can guarantee that this will work. I have seen it fix this issue before though.
Click to expand...
Click to collapse
If the bootloader somehow got corrupted (like crawly and Entrophy mentioned) then a jig won't do any good, I think.
It's good that some guru can access and reprogram the bootloader via JTAG.
I keep fingers crossed for OP.
---------- Post added at 09:54 PM ---------- Previous post was at 09:44 PM ----------
Entropy512 said:
No one claims it's unbrickable - just that it's damned hard to brick.
I'm still curious what he was trying to flash - I have NEVER heard of anyone hardbricking their devices unless:
1) They screwed with bootloaders - which is why I have included gigantic red warnings with anything I post that includes a bootloader
2) They flashed something not intended for the device
Click to expand...
Click to collapse
Experienced people can avoid those fundamental mistakes but newbies often get hair pulling, head scratching before mumbling "dang, why would I do that in first place"
Entropy512 said:
No one claims it's unbrickable - just that it's damned hard to brick.
I'm still curious what he was trying to flash - I have NEVER heard of anyone hardbricking their devices unless:
1) They screwed with bootloaders - which is why I have included gigantic red warnings with anything I post that includes a bootloader
2) They flashed something not intended for the device
Click to expand...
Click to collapse
Personal experience here. Flashed a one click for a captivate and bricked it a year ago. Went through everything, reported a success, and even sent reboot command to phone when it was done. 'Rebooted' to a black screen. For the better part of a week I tried everything, and I mean everything. Just unbricked last night/this morning with the 'unbrickable mod'. Wow micro soldering.
What led up to this was flashing a friends captivate with another one click odin package. Bricked it too (really need to quit doing that) but I think a usb jig might have worked on that one, but didn't have one with me. After doing the unbrickable mod to the phone that sat for over a year, I flashed it with the same package that just bricked the second captivate, and it worked fine. I did nothing different. I'm very patient in doing things the right way. Same steps, same software, same computer, no brick.
Sent from my páhhōniē
To the OP
Is getting Samsung Tech support an option, if everything else fails, then you dont have anything to lose, they support by phone and was pleseantly suprised with their help.
AdamOutler is willing to work on bringing the unbrickable mod to the i777. All he needs is an i777, bricked or not. If anyone has one that is bricked, by all means send it to him. He said not only will he
unbrick it using jtag, he'll attempt to do the unbrickable mod to it.
I'd be willing to donate to him and anybody who helps make it possible by sending him their phone.
Sent from my páhhōniē
I've searched and searched, but I've been unable to find a solution to, or even any examples of, my particular problem. I was wiping and formatting everything before I flashing a ROM as I've done countless times before, but this time I decided to format the boot partition, which I can't remember ever doing before, and I think I then pulled the battery before flashing anything.
Now when I put the battery back in or plug in the USB cable (without pressing any buttons at all) the phone immediately shows the Vibrant/Samsung screen and nothing else happens. Holding the power button (or power + vol up, or power + vol down, or power + vol up and down) makes the screen flash off momentarily and then come back on again, but that's it. I can't get into recovery mode, and I couldn't get into download mode either, as the phone won't stay off when I put the battery in.
So, I bought a USB jig and to my relief it enabled the phone to get into download mode. I put the jig in the USB port and insert the battery, and download mode immediately comes up. Then I remove the jig and either connect the USB cable and then start Odin, or start Odin and then connect the USB cable. Either way, Odin doesn't recognize the phone. Windows gives me some sort of error about a malfunctioning USB device.
I know the problem is the phone, and not my cable or computer, because I can Odin to my wife's Vibrant no problem. Any ideas?
sporglak said:
I've searched and searched, but I've been unable to find a solution to, or even any examples of, my particular problem. I was wiping and formatting everything before I flashing a ROM as I've done countless times before, but this time I decided to format the boot partition, which I can't remember ever doing before, and I think I then pulled the battery before flashing anything.
Now when I put the battery back in or plug in the USB cable (without pressing any buttons at all) the phone immediately shows the Vibrant/Samsung screen and nothing else happens. Holding the power button (or power + vol up, or power + vol down, or power + vol up and down) makes the screen flash off momentarily and then come back on again, but that's it. I can't get into recovery mode, and I couldn't get into download mode either, as the phone won't stay off when I put the battery in.
So, I bought a USB jig and to my relief it enabled the phone to get into download mode. I put the jig in the USB port and insert the battery, and download mode immediately comes up. Then I remove the jig and either connect the USB cable and then start Odin, or start Odin and then connect the USB cable. Either way, Odin doesn't recognize the phone. Windows gives me some sort of error about a malfunctioning USB device.
I know the problem is the phone, and not my cable or computer, because I can Odin to my wife's Vibrant no problem. Any ideas?
Click to expand...
Click to collapse
Alrighty, well...I actually remember a thread like this coming up awhile back and having no freakin' clue personally...however it lead me to think that you ought to have done a search of the forums before posting this. I was however wrong. I've spent about the last 45 minutes reading thread upon thread upon thread dealing with this issue without any of them offering a solution. Most were simply saying things like:
G0 TRYZZ A KNEW C0RDDD N00BBBIEEE
Click to expand...
Click to collapse
or
1NSTALLZ NEW DRYVRZ U NAP
Click to expand...
Click to collapse
or even
AI0 TO0L BOXXXX S0LVZZ EET 1DIOT
Click to expand...
Click to collapse
Okay...I made that up. Our community isn't so mean lol However, those were pretty much the only solutions I came across, and sadly they did not work.
So....I'm going to take a shot in the dark and suggest you head on over to this thread and give it a whirl:
http://forum.xda-developers.com/showthread.php?p=15330252
I have not seen this suggested in any of the dozens of threads i visited, and honestly, I don't know all too much about the process, but hopefully it will work for you. Read it over, test it out and if it doesn't work head back here and let us know and we can figure something out...and who knows, maybe by then someone with far more knowledge of this particular problem will pass on through and shed some light on the situation.
But for now, concentrate on staying calm and we'll work through it.
Sounds like you deleted the boot loaders. Make sure you have correct drivers installed, windows isn't auto detecting. Try to get Odin to recognize again, try all USB ports. If you get it recognized make sure to √ re-partition.
BTW Xeno, you made me bust out laughing!
sent from my magic box to yours
---------- Post added at 02:53 AM ---------- Previous post was at 02:33 AM ----------
I just read something about this...its not boot loader just boot image. It suggested trying kies.
sent from my magic box to yours
samsgun357 said:
BTW Xeno, you made me bust out laughing!
-----
I just read something about this...its not boot loader just boot image. It suggested trying kies.
Click to expand...
Click to collapse
All in a days work! Aha!
Also, not to go against your advice, because I think its awesome that you responded and are searching for a "cure" but OP do not, I repeat, do NOT touch kies. I'm sure you've heard about the Holocaust in your history classes at some point, yes? Well that was microscopic compared to the disasters that will befall your vibrant if you bring it anywhere near the kies software. Do NOT do it. Think of the kids for God's sake. That is all.
Xenoism said:
Alrighty, well...I actually remember a thread like this coming up awhile back and having no freakin' clue personally...however it lead me to think that you ought to have done a search of the forums before posting this. I was however wrong. I've spent about the last 45 minutes reading thread upon thread upon thread dealing with this issue without any of them offering a solution. Most were simply saying things like:
or
or even
Okay...I made that up. Our community isn't so mean lol However, those were pretty much the only solutions I came across, and sadly they did not work.
So....I'm going to take a shot in the dark and suggest you head on over to this thread and give it a whirl:
http://forum.xda-developers.com/showthread.php?p=15330252
I have not seen this suggested in any of the dozens of threads i visited, and honestly, I don't know all too much about the process, but hopefully it will work for you. Read it over, test it out and if it doesn't work head back here and let us know and we can figure something out...and who knows, maybe by then someone with far more knowledge of this particular problem will pass on through and shed some light on the situation.
But for now, concentrate on staying calm and we'll work through it.
Click to expand...
Click to collapse
"Failed. Unspecified Error." Thanks for the suggestion, though, Xenoism. I knew that no matter how diligent my search of the forums, somebody would toss out a link to a post I missed.
@xeno, your killing me hahaha! I have heard about bad experiences with kies. I have used it a few times without issue, this was my Pre xda days. I figured this guy didn't have much to lose and if kies hard bricked it, he'd have a better shot of Sammy or tmo hooking him up with a fix. I guess for $40 he could get a JTAG repair.
sent from my magic box to yours
sporglak said:
"Failed. Unspecified Error." Thanks for the suggestion, though, Xenoism. I knew that no matter how diligent my search of the forums, somebody would toss out a link to a post I missed.
Click to expand...
Click to collapse
I was afraid that might not help you. I spent another hour or so this morning looking throughout the web for potential solutions...nothing just yet :/
I'll keep searching though, if you do the same man ^^
I just got a galaxy note for my galaxy nexus last night (traded) and I took it home and install goomanager and downloaded a rom that was "compatible" it saved to the directory that goomanager puts it in so I rebooted into CWMR and cleared cache / data etc then proceeded to install zip from SD Card. it started by saying flashing kernel 4% or whatever and then came back with an error. me being as bright as I am recently...I fixed permissions and rebooted thinking that it would at least let me back into recovery.
I now have a "Dead" note sitting on the floor infinitely "charging" so to speak its just plugged into the wall, Will not boot. Is there a way I can at least get it into Download mode? Hell stick a magnet on it to erase everything even?
I don't need another paper weight..I have an iPhone for that.
Can you boot into download? If so, use Odin to flash the correct kernel.
Can you boot into recovery? If so, flash the correct kernel.
If you can't do either one, your phone is bricked and you will need to send it for a repair. $50 and one week later you will have your phone back with stock 4.0.4 ICS rom. Its called a JTAG service, from www.mobiletechvideos.com. Many note user have gone there, from just this thing.
The jig that works with other phones 99% of the time won't work with the note.
Don't trust CWR. Get your roms from our developers.
Jig 99% Of the time won't work... you made that statistic up. If button combos aren't working it's definitely worth a shot, resistors are super cheap, especially compared to jtag which doesn't sound needed here yet.
And what do you mean. "Don't trust cwr get your roms from the devs here"?
That is a recovery... he didn't download anything with it, he used goomanager.
And even if he downloaded it from here...he would've flashed it in cwm... xda isn't a custom recovery...
So you tried holding the down volume button+ power to get it into download? Flashing a kernel will not remove your recovery/download mode unless you flashed a Rom not made for your device that installed something on said partition(s).
As for the jig...don't know statistics, but I am a one percenter. Worth a shot imo.
https://www.youtube.com/watch?v=6K-lvaAop2w&feature=youtube_gdata_player
Sent from my SAMSUNG-SGH-I717 using Xparent Gray Tapatalk 2
Volume down and power, then when prompted volume up, for download mode.
And I'm also a "1% er" and my jig isn't homemade. Josh from mobile tech gave me one of his he sells on the site.
As nun said, the combos should work, they are in the bootloaders, flashing a kernel won't effect those unless says kernel is for a different device, then you wouldn't get a single thing outta the device at all, no charging screen, no bootloop. Nothing. Whatsoever.
studacris said:
Volume down and power, then when prompted volume up, for download mode.
And I'm also a "1% er" and my jig isn't homemade.
Click to expand...
Click to collapse
Right amigo 99% + 1% = 100%. You and Nunhugger are the only ones who said a jig worked for them. So actually its way higher than 99%. . . But you guys are ninjas. Your phone would probably reboot if you just told it to. I just wanted to kill the eventual jig question early.
And my response about CWR was because it sounded like he used the old app Rom Manager to see what was available. Clearly it was wrong so I told him not to trust it, and put in a plug for our developers.
When an update is released the forum gets slammed with complaints about bad flashes of incorrect kernels, and I have seen several members heal their phone by flashing the correct kernel. I just figured he was not accustomed to the button combos of the note and would get to that eventually. But if it was for the wrong device I wanted him to get his mind around the $50 and week wait.
Sheesh. . . decaf.
Well seeing that I can't Get into either mode and no button combos will work, I am assuming I need the JTAG. I figured an app like GooManager would have at least gave me the right roms for my device. it did say i717 but that could just be my memory playing tricks on me.
Man, I'm real sorry. But the JTAG service has been used by many, and with lots of positive comments. Good luck.
hahah thats okay, I mean its a great phone, definately not worth keeping in a draw collecting dust so I will go with the JTAG service. Thanks Guys!
You still have signs of life, it shows the charging animation, therefore your phone isn't bricked.
Do some searching on making a jig, I personally think it's well worth a try.
You could very well fix your phone for under $10 and have the satisfaction of accomplishing this yourself And have the know how to do it again...
It doesn't have the charging animation. just a dead black screen.
Then why did you say this?:
leveliv said:
I now have a "Dead" note sitting on the floor infinitely "charging" so to speak its just plugged into the wall, Will not boot.
Click to expand...
Click to collapse
That's more than a little misleading...
Will not boot...could mean many things.
From a easily fixed bootloop down to a brick.
Saying it was infinitely charging made it sound less severe.
if it weren't for that line, I wouldn't have bothered to tell you to use a jig.
JTAG it is
cris, why do you need to experiment with finding the proper resistance? Why should there be any variability in that circuit? Perhaps that is why some users have used up as many as six usb port replacement parts.
By the way, my 99% statistic is, like my entire post, just my opinion, and strictly a figure of speech. If it were a fact I was quoting I would have included a footnote. Remember those painful things? Do we have to include disclaimers for any figure we use? Sorry to mislead anyone!
I said "dead" because its not necessarily dead because a JTAG thing can fix it..and I said "charging" because to the normal person who didn't know anything was wrong with said device it would look like it was charging. But anyhow. I'm sending the phone out this week. I just don't understand why all the phones can't be as open as the devices straight from google.
You're phone is dead.
JTAG is akin to zombie, the phone needs disassembled and a special rig is needed to hook to the motherboard and flash EVERYTHING back to the nand at the prebootloader level.
The I717 is pretty much just as open as a nexus as far as easily modified and rooted...
No locked bootloader even which nexus have though it's a single line in a terminal to unlock, that step isn't needed on this device.
Only thing that isn't as open is the hardware drivers.
You may have flashed an incompatible kernel for a DIFFERENT device... and that on any phone will brick you.
And ranger not sure if it's the circuits within the phones that vary from device to device, ands seem to require a more specific voltage across those pins to trigger download mode
Or, if It's the resistors that are the variable. They are only rated within a certain +/- tolerance the cheaper ones having a larger margin of error.
And lol yes I am a ninja, but I didn't do anything special to my jig at all, I got mine from mobiletechvideos, funny enough it's worked on 4 captivates, a vibrant, 2 note 1s, and an s3, but didn't work on an s2 I was fixing.
the one I got from Goomanager was probably for the i700 which shouldn't even be able to happen.
They have video proof of them fixing phones with dead black screens from exactly what happened to mine using the JTAG Method. As far as I am concerned this thread can be closed cause I got the answer to my question.
the JTAG rewrites basically everything anyways so it is being sent out later this week. Till then I'll use a blackberry or something...Take care guys hopefully next time you see me post it will be to help someone and not asking for help
You'll be up and running by next weekend. By then, lots of exciting development will be happening on the released rom.
I doubt it, I live in Canada and have to send it to the states. It probably be closer to the weekend. Unless I expedite everything.
Alright. let us get this straight. I have searched in countless number of forums for solving my issue but I'm NOT able to fix it.
I have a Samsung Galaxy S Vibrant T959. It currently seems to be "soft-bricked" (I always see a mobile connected to a computer and an exclamation icon in between). So to reset it, I have left almost not stone unturned. But no luck so far
As far as I remember, I happened to land it in trouble while I was trying to flash some secondary bootloader using ODIN.
I also tried the micro-USB JIG method by building a 300k-Ohm USB JIG on my own (using three 100k-Ohm resistors), but even that is not working for me. Whenever I connect my phone to my computer, it starts up and shows those three icons. The same happens when I remove the battery, insert it back and start the phone up again. The same happens for each of the numerous key sequences mentioned online for download/recovery mode. So literally NOTHING is working for me. I also tried OneClick.jar, Heimdall. None of them are making me lucky as the phone is not getting detected.
I believe there has to be a way to reset it somehow (although I seem to have screwed something seriously) but nothing seems to work for me. What can I possibly do now?
Attached images show the micro-USB jig that I made and the icon on my phone I see.
From my experience if you can get that far you don't need a jtag. But you did say that you flash bootloader. So you ether need to get the right combo to get to download mode or you are done with out working bootloader. The only other thing that I can think of would be to do the unbrickable mod.
Sent from my Nexus 4
Thanks jrongi1 for the reply.
>> So you ether need to get the right combo to get to download mode or you are done with out working bootloader.
I have tried many, many combos for getting the download mode but no luck so far Can you suggest some if you are aware of one?
The only other thing that I can think of would be to do the unbrickable mod.
>> I tried to know about this but I did not understand what this exactly means? I believe this involves some sort of hardware rework. Can you please point me to steps to do this? Are you referring to this procedure? If yes, I don't believe it's a solution since that procedure is just a preventive measure and not a solution (that's what I understand after reading that whole thing out).
Try that.
reboot computer, turn off phone, take out battery, put the battery back, hold volume up and down buttons and then plug in usb.
Sent from my SGH-T959 using xda app-developers app
This is from N00B_IN_N33D's MIUI guide stickied at the top.
"SOFT" BRICKED WHILE USING ODIN?
If you are getting a "Phone.. ! ..Computer" image (seen above) when booting phone, yes, you are bricked but it is reversible! Just follow these steps...
Make sure you have ODIN OPEN with admin privileges!
1.) Take off your back cover, remove your sim & mirco sd card.
2.) Remove your battery.
Make sure you have the USB plugged into your PC but NOT your phone!
3.) Hold the volume buttons.
4.) Put the battery in.
5.) Put the USB in.
You don't necessarily need the download mode image to be present. As long as you are getting the COM ID to light up yellow in ODIN, just flash back to stock like normal.
Click to expand...
Click to collapse
Sometimes the key combo can be a bit precarious and the timing needs to be precise. I know that when I have taken my Vibes back to stock, it takes me more than a few tries to get it right. You've said you have tried the key combos several time, I think you should keep trying them and get your timing right. I would hate for you to screw up your phone when doing the Unbrickable hardware mod, when it could be something as simple as a timing thing.
As the other guys said work with the buttons and only try the unbrickable mod as a last resort.
Sent from my Nexus 4
Thanks guys for responses.
testomat/Woody, I tried as per your steps almost 8-10 times, but that does not work either
jrongi1,
I do not wish to go for Unbrickable mod either. Anyway, I have contacted a local repairs guy for this issue. He said he can fix this issue using JTAG interface. That costs me 1500INR. That's the only solution I have I guess.
Good luck with the repair I hope that you can get going soon.
Sent from my Nexus 4
Thank you so much again!
Woody said:
This is from N00B_IN_N33D's MIUI guide stickied at the top.
Sometimes the key combo can be a bit precarious and the timing needs to be precise. I know that when I have taken my Vibes back to stock, it takes me more than a few tries to get it right. You've said you have tried the key combos several time, I think you should keep trying them and get your timing right. I would hate for you to screw up your phone when doing the Unbrickable hardware mod, when it could be something as simple as a timing thing.
Click to expand...
Click to collapse
This worked for me.....Many thanks