Yessss another dead captivate thread.
I think I'm gonna go die now.
I followed the video guide to install a custom ROM, in the development thread to the letter, and now my phone wont even turn on... (now that im thinking about it, I think I may have left the debugging mode OFF before I went to flash back to stock, maybe thats why?)
I got into download mode, plugged the phone into odin3 JF6 one click, it started and at some point during the process it said "removed" even though I didnt touch anything, and then i got a weird msg saying my device is not recognized, keep in mind the drivers were installed properly, and I had everything double checked before i flashed....
wtf do I do now? Cant boot at all or go back into download mode. this is my third galaxy, got it two days ago ffs.
My only 2 suggestions. Go to the Dev section and in the guides there is a method to make a USB Jig without solder or anything. You're out like $1 if it doesn't work.
Also, what rev is your phone? There's been some threads started saying the newer Rev phones, maybe 1010 and up crap out using normal One-click. Do check your rev level under the battery and do a search of the forums. I know I have seen the threads.
good luck.
1 reboot pc
2 use different usb ports (direct to motherboard)
3 open odin first as administrator
Sent from my GT-I9000 using XDA App
bobbylx said:
My only 2 suggestions. Go to the Dev section and in the guides there is a method to make a USB Jig without solder or anything. You're out like $1 if it doesn't work.
Also, what rev is your phone? There's been some threads started saying the newer Rev phones, maybe 1010 and up crap out using normal One-click. Do check your rev level under the battery and do a search of the forums. I know I have seen the threads.
good luck.
Click to expand...
Click to collapse
I'm not sure if I was looking at the right place, but I think its 10.12. I'll do a search and see what comes up, thanks for your help.
JayPhill89 said:
1 reboot pc
2 use different usb ports (direct to motherboard)
3 open odin first as administrator
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I'll try that, thanks.
Open Odin first then,
1. Remove your battery for 30 seconds, remove external SD card and SIM card
2. Reinsert battery.
3. Hold down both volume buttons and while holding them down plug the phone in.
It should get into download mode then. I bricked my phone and it wouldn't boot up at all and this worked for me.
On a side note, I have not had much luck flashing or doing much of anything on Windows 7 64 bit. I would suggest trying it on an XP machine if you have access to one.
G.Hook said:
Open Odin first then,
1. Remove your battery for 30 seconds, remove external SD card and SIM card
2. Reinsert battery.
3. Hold down both volume buttons and while holding them down plug the phone in.
It should get into download mode then. I bricked my phone and it wouldn't boot up at all and this worked for me.
On a side note, I have not had much luck flashing or doing much of anything on Windows 7 64 bit. I would suggest trying it on an XP machine if you have access to one.
Click to expand...
Click to collapse
I've tried every possible key combination out there and nothing works. I think my best bet is a Jig, unfortunately the source didnt have any transistors in stock so im SOL for now.
Use JIG ... It will be your last help.
Use it as a paper weight.
If you look up samsung captivate jig on ebay you will find some pre built. I bought one not long ago just to have and it works just fine.
I hope this helps. Best of luck to you.
Sent from my GT-I9000 using XDA App
Sounds like you are a victim of the one size odin fits all debacle. You will indeed need a jig to recover and then you must use odin to flash jh2 or later firmware to your phone. Unfortunately, most guides still direct people to flash jf6 even though your situation comes up on a regular basis.
Check out this link for a jig. And there is a video to show you how to build one. Or mobiletechvideo guy sells them for 17 bucks.
http://forum.xda-developers.com/showthread.php?t=889128&highlight=usb+jig
Sent from my SGH-I897 using XDA App
newter55 said:
Sounds like you are a victim of the one size odin fits all debacle. You will indeed need a jig to recover and then you must use odin to flash jh2 or later firmware to your phone. Unfortunately, most guides still direct people to flash jf6 even though your situation comes up on a regular basis.
Click to expand...
Click to collapse
It seems to me like there's consistent irregularities with the entire process, its not uniform at all, which is very frustrating, every one faces different problems, and the solution is never the same.
Anyways, I went out and bought 3 resistors, turns out they were the wrong ones, I found out the colors werent the same of what I needed, but then that just goes to show you how difficult it is, its partly my fault i got the wrong ones, but someone like me who doesnt know much about hardware hacking, walks into an electronic store, faced with several options, is some times lost.
Oh well, I could've fixed it, had I got the right resistors, but then again, who was going to guarantee I wasn't going to kill it again, for the exact same reason I mentioned in the first post, because I need to consider a few things here, first and foremost, that I have a rogers branded device, and these are the ATT forums.
I called rogers and a replacement has been placed, I should be getting it by friday, or tomorrow if im lucky, with whatever comfort that brings, I still have several concerns, and now that I've basically rendered 3 devices to "almost" none-working condition (this one being an exception because I can "possibly" fix it) I'm not even sure how far I want to go.
rsnt said:
It seems to me like there's consistent irregularities with the entire process, its not uniform at all, which is very frustrating, every one faces different problems, and the solution is never the same.
Anyways, I went out and bought 3 resistors, turns out they were the wrong ones, I found out the colors werent the same of what I needed, but then that just goes to show you how difficult it is, its partly my fault i got the wrong ones, but someone like me who doesnt know much about hardware hacking, walks into an electronic store, faced with several options, is some times lost.
Oh well, I could've fixed it, had I got the right resistors, but then again, who was going to guarantee I wasn't going to kill it again, for the exact same reason I mentioned in the first post, because I need to consider a few things here, first and foremost, that I have a rogers branded device, and these are the ATT forums.
I called rogers and a replacement has been placed, I should be getting it by friday, or tomorrow if im lucky, with whatever comfort that brings, I still have several concerns, and now that I've basically rendered 3 devices to "almost" none-working condition (this one being an exception because I can "possibly" fix it) I'm not even sure how far I want to go.
Click to expand...
Click to collapse
My first captivate went fubar within my 30 days and I damaged the nv_data.bin on my second captivate and was stuck with the test IMEI. Samsung fixed my second one for free. Now I'm at the point where I'm totally sure about what precautions I need to take to keep me out of trouble but I'm not sure if I want to risk it again, heh.
The cheap jig does work. It helped me when I accidentally unplugged my phone during an odin flash.
Yes, you make a good point. You will find that most of the guides are written by people like myself who have an early revision or a phone from the initial release. For most of us, from what I've read and experienced, our phones are really hard to brick, ie, button recovery always works, odin one-click works, etc.
I honestly don't know all the differences now between revs. The first hiccup was the phones missing button recovery/download, and now it seems that people are having issues using the Odin One-click that we have been using for months.
I would recommend with your next phone check the rev or manufacture date, then search the forums for people with similar or same revs that have been successful at flashing and find out what they did.
good luck
@bobby
I wasnt trying to diminish the help that the guides provide. The work that went into creating them is certainly appreciated. The problem arises when so many people just tell newcomers to flash with x version of odin without considering the changes that have occured in the newer builds.
Sent from my Liquid Metal using XDA App
newter55 said:
@bobby
I wasnt trying to diminish the help that the guides provide. The work that went into creating them is certainly appreciated. The problem arises when so many people just tell newcomers to flash with x version of odin without considering the changes that have occured in the newer builds.
Sent from my Liquid Metal using XDA App
Click to expand...
Click to collapse
I agree with you completely. I tend to take it for granted that button recovery works for me and that good old odin one-click does too. It seems we need to start collecting data and making new guides.
Something like,
If you have rev, 1006, 1007,1008 go here,
If you have rev 1009 to 1012 go here,
etc.
latest update,
Two cables, and six resistors later, my phone won't go into download mode, lol, I'm not even sure I did things right, I'm gonna try stripping the same cable, used in one of those videos on how to make a jig, I still have three extra resistors.
I'm starting to think its because of it being with rogers. im gonna search the forums.
A micro usb breakout board is the simplest method for constructing a jig.
Wow, I guess I'm lucky that the used Captivate I picked up for my gf is an older one at 1007. Root procedure for her went without a hitch.
From stock rom, all set up and in daily use, WITHOUT ROOTING first.
Put clockwork update.zip on her sdcard.
Reboot into recovery.
Reinstall packages twice to get into clockwork recovery.
Wipe data/factory reset.
Flash Cognition.
Profit.
She's been using it this way for two weeks and loves it so much more than stock.
What was so complicated about the procedure you followed? Or was it the same as this but it just didn't work?
rsnt said:
...and now that I've basically rendered 3 devices to "almost" none-working condition (this one being an exception because I can "possibly" fix it) I'm not even sure how far I want to go.
Click to expand...
Click to collapse
I think you may have a good point. Eventually your carrier will stop replacing bricks for you. If you still have the inclination to play with flashing, investing in a jig would definately be a wise investment and if I were in your shoes, I wouldn't flash anything without one. I made a jig for myself before I ever flashed anything but luckily I have never had to use it, probably because I took the time (about a month and a half of trolling around here reading.) to research what all was involved with what I was about to jump into. Just something to consider in case you want to try again. Good luck!
Related
This is the last time any of you will see me post in the Captivate forum. I've now gone through 2 captivates due to bricks by Odin not working (gets stuck on DO NOT TURN OFF TARGET!!) and never getting past that thus having a bricked phone. And getting phones that have broken key combos. I'm going back to the Aria. I'll just buy a extended battery since those batteries are so bad.
No Android phone will compare to the speed of the Captivate. But at least I will never have to deal with Odin again.
Thanks to all the constant support and updates for the Captivate here at XDA. I really appreciate it. I love the support and updates that the Captivate got. But I can't stand how easy it is to brick for it to be "impossible" to brick.
Your acting like you had to mess with Odin, no one made you and the phone was usuable without it.
You do realize it was your fault right. And the 3 button combo has gotten fixed. Maybe reading more would have helped out some.
Sent from my SAMSUNG-SGH-I897 using XDA App
User error ruined your phone.
Happy Trails..
Wow ... I thought captivate was unbrickable. I've used Odin tons of times with no issues, most recently last night to installed froyo.
Aria isn't too bad, had one for a month. At least you still have support for the Aria.
Sent from my SAMSUNG-SGH-I897 using XDA App
I have to agree with the other posts here. Odin didn't brick your phone, you did.
Sent from my SAMSUNG-SGH-I897 using XDA App
How do you know it was fully bricked? - I've gotten stuck at DO NOT TURN OFF TARGET; I did these steps to fix it.
Try this, move quickly:
1.) Open ODIN One-Click on the computer.
2.) Take out the SIM and SD card.
3.) Put in the battery, quickly holding VOL UP and VOL DOWN and inserting the USB.
It should go into download mode.
dude....really?
I am the least knowledgeable and phone savvy person here IMO. I owned a Nokia N97 for the last year and a half and an N95 for two years bfore that (I recently trashed)
I was able to with two phones root them the first day, delete ATT SW Download the JH7 Update using Kies Mini, UNroot both and update one to 2.2 with ODIN3 with aero issues.
My wife is still deciding on the N97 vs the Captivate. In the mean time I will be using it as a guinea Pig for messing around with. Going to Master clear it and install Froyo today.
I think many times it is user error and the support here is amazing, patient and extremely well implemented.
I think the OP should step back and revisit all the steps.....This is a great device despite the "GPS failings" which are differing in degree based on individual expectations more than actual reality from what I read.
Small issues tend to become large ones and pileons occur quickly across the net. I would bet the GPS issue is not as bad as many phones , better than some worse thano others. I know it is far better than the GPS on the N97 as is the browser...on and on.
Colton5419 said:
How do you know it was fully bricked? - I've gotten stuck at DO NOT TURN OFF TARGET; I did these steps to fix it.
Try this, move quickly:
1.) Open ODIN One-Click on the computer.
2.) Take out the SIM and SD card.
3.) Put in the battery, quickly holding VOL UP and VOL DOWN and inserting the USB.
It should go into download mode.
Click to expand...
Click to collapse
That works for me everytime. No 3 button combo. Turn off, take out battery, start Odin, insert battery, hold only volume up and volume down, plug in usb. Goes straight to download mode. No counting black screens, no timing button release.
Sent from my SAMSUNG-SGH-I897 using XDA App
I "bricked" my phone. It would only boot to a black screen. Just holding down the volume keys, then adding the power key got me into download mode. Odin fixed everything. I actually fixed it so quickly that never got to the, "crap! I just bricked my phone. I hope I can fix this," stage. It was fixed before I even realized it was at the point that a lot of people around here call bricked. I was more just annoyed that now I had to re-odin before flashing.
Just today odin locked up on me and I had to remove the usb; I was getting the phone to pda disconnect screen when trying to do anything. So I quickly did the VOL UP and VOL DOWN while inserting the USB and thankfully all turned out well and I'm back on FROYO JI6 for now.
Well I have two of these things and they are both at the same thing. Phone+computer, None of the key combos will put them in Download mode. I've done every single possible method found to do it and none of them will work. It's not user error. I didn't brick it. I'm not the only person that had Odin freeze and NOT continue. I've had the worst luck with these phones.
Konner920 said:
Well I have two of these things and they are both at the same thing. Phone+computer, None of the key combos will put them in Download mode. I've done every single possible method found to do it and none of them will work. It's not user error. I didn't brick it. I'm not the only person that had Odin freeze and NOT continue. I've had the worst luck with these phones.
Click to expand...
Click to collapse
It is your fault though, because if you try to change kernels and use odin it is up to you. If the phone has the 3 button combo issue that is one thing, but you still need to know that anything you do to your phone is on you. It is not Samsung or ATT's fault for you trying to change kernel's. But there is no talking sense to someone that doesn't understand that fact. Sorry you had bad issues with this phone.
I have yet to brick my Captivate. The rule of thumb is, if you can get it into Download mode.. it's recoverable. If you decide to get rid of your Captivate, that's your business but the phone is a solid one. I had issues flashing Froyo and thought i bricked but it took a few tries with Odin and i got it working. If you want to use custom firmware, you have to put effort into reading up on things.
This is the funniest thing i have read in a long time. Especially since JH7 fixed the key combo issue.
I had never thought of that angle "I bricked my phone, so i better switch brands". Especially when 99% of us are uing Odin with ZERO issues. The only anology that comes to mind is "Every time I adjust the carb screws i more ford it won't start, so I am switching to Chevy"
Good luck OP!
alphadog00 said:
This is the funniest thing i have read in a long time. Especially since JH7 fixed the key combo issue.
Click to expand...
Click to collapse
JH7 didn't fix my 3-button
this is why i am being patient and just waiting for the official update
I dont understand why people feel the need to post a goodbye thread... we dont care....especially if its user error...if you would have taken the time to post a question with the issues you were having some one would have probably helped you..ehhh..you've wasted your breathe and now I've wasted mine...
Sent from my SAMSUNG-SGH-I897 using XDA App
I just got the Captivate about a month ago. Had a regular phone for about a year, touch screen went out, bought a replacement digitizer but knew it was a temporary fix anyway and wanted a new phone. Convinced the maternal unit to use her contract extension to get me a new phone, and snagged the Captivate for $30 from RadioShack. My first Android phone, and I have to say I'm horribly disappointed, but I guess I'm doing something wrong here.
First two or three weeks, my mom had the phone and got to play around with it for a while. Wasn't until the 29th that I got the phone, and I just played around with it for a week and got all the apps I deemed useful and worthwhile. Eventually realized I couldn't use Flash in the browser, nor Skype, etc., without upgrading to 2.2.
So, I went through the tutorial Samsung provided, watched videos on Youtube just to be sure, but followed everything Samsung's tutorial said word for word. ... only for my phone to end up completely screwed up. Gallery, Browser, Music Player, Video Player, and many other default applications were missing. Now I'm smart enough with technology to think, okay, something's wrong. I knew about the factory reset, so I went to go to settings to do that, and realized. ... oh wait, the Settings menu is also missing. Wonderful. There was no "Settings" button in the Applications list, and if I tried getting to it from the menu button, it simply did nothing at all.
Found Odin, flashed back to 2.1, and then factory reset and got rid of every application I had and etc., so that absolutely nothing was on it, basically a stock phone. Tried upgrading again fresh, still following the instructions very closely. Same problem occurred, and I was pissed. Gave up on 2.2, tried flashing back to 2.1 /again/ with Odin, only for my phone to decide it didn't want to enter download mode anymore. Forced it using 'adb reboot download', but alas, it locked up in the middle of flashing back to 2.1 and wouldn't do anything. I waited about 30 minutes to see if it'd resume the flashing process at all, but nothing, so I regrettably had to disconnect the USB cable and hard brick the phone (wouldn't turn on or anything).
Still under warranty, so I replaced it from RadioShack, and now have a new Captivate. Went ahead and installed all the applications I needed, used the Sideload Wonder Machine to install a few third-party applications, had no problem doing that for a while. Didn't bother attempting to upgrade. However, my computer got a trojan and deleted the MBR. Repaired using the XP boot disc, but it meant I was back on SP2. After installing every last one of the damn updates all over again, I decided to check up on some new applications to install via sideloading.
Hooked up my phone, it detected all the new hardware again since the drivers seemingly were also lost amongst everything else during the repair, only for it to encounter an error on the "Samsung Android Composite ADB Interface". So, I uninstalled the drivers, tried installing them manually. Hooked up the phone, but it still wanted to try to install that one driver and failed. I've restarted my computer, uninstalled the drivers, attempted manually installing them through device manager, you name it. Still can't get it to work -- it keeps having a fatal error every time. However, it's only when my phone has USB Debugging on. Installs every single driver perfectly fine when it's off, in MTP/Mass Storage/Kies mode. Just has a "fatal error" in USB Debugging on that one driver.
tl;dr, the drivers are broken on my computer and I can't fix them despite actually /not/ being computer illiterate. And, I kind of still want 2.2, but apparently the stock 2.2 update is a pain in the rear end and I no longer have a warranty through RadioShack now, so I can't risk bricking my phone due to a faulty update process. Any suggestions?
err, the only thing you should have needed to do was install the latest version of Kies, plugged the phone in, it would have prompted you to do the update. It's quite painless..
Edit: Sorry irrelevant
sw411 said:
err, the only thing you should have needed to do was install the latest version of Kies, plugged the phone in, it would have prompted you to do the update. It's quite painless..
Click to expand...
Click to collapse
At the time I tried, Kies itself didn't support the Captivate. Only Kies mini. And in order to do that upgrade, I had to install the drivers, then put the phone into download mode to install more drivers for some odd reason, restart the phone (taking out the battery and putting it back in), then hook it up. Kies mini wouldn't detect the phone for several tries at first, finally got it about the 10th time in. Then go to the "Upgrade phone" link, and yeah. I followed the instructions from Samsung's official SGH-i897 Froyo upgrade guide.
I did EXACTLY as the instructions say, down to the wire. Still ended up both times with all those applications missing and the settings panel missing, unable to do a factory reset without flashing back to 2.1 first.
Install z4root and root phone
Install rom manager
Flash clockwordmod recovery from rom manager
Choose a 2.2 rom from the forums
Download and copy to SD card
Install via rom manager
????????
Profit
Hope this helps. Btw I reccomend firefly or serendipity for the rom
Sent from my Captivate running CyanogenMod7 using XDA Premium App
brendanmurphy said:
Install z4root and root phone
Install rom manager
Flash clockwordmod recovery from rom manager
Choose a 2.2 rom from the forums
Download and copy to SD card
Install via rom manager
????????
Profit
Hope this helps. Btw I reccomend firefly or serendipity for the rom
Sent from my Captivate running CyanogenMod7 using XDA Premium App
Click to expand...
Click to collapse
Only downside to rooting the phone is the voided warranty. I don't entirely know what I'm doing there when it comes to flashing, and if I manage to do something wrong and brick the phone again, I'm completely wiped. I don't have the money to replace the phone at all. I have no job. ._. Only reason I got the phone was because I managed to get some spare money fixing up a friend's computer, and the maternal unit's contract extension was available. I'm not paying for the phone, still my parents. Damn economy in this state is so broken, and I'm screwed over worse since I have no diploma.
However, I was looking into info on the roms, and while I was tempted to try out CM7 for the fact it was 2.3, I actually considered getting Paragon RC6 from what I had read. Just decided not to because I can't replace the phone if I screwed up. In the slim chance I do opt to risk not having a phone at all if I do something wrong, would you say Paragon's worthwhile or would it be better to go with Serendipity? I do like TouchWiz, and Wifi access is a must (200 MB plan isn't going to cover it with how I use data; I'm frequently using Wifi in as many places as is possible), but I'm pretty sure both of those are fine there. Just not really sure which would be better overall, performance-wise.
I can't do either of them right now anyway until I figure out why the drivers aren't installing. So that's my first issue.
Don't worry about bricking I almost guarantee you will brick your phone once. But that is what Odin is for and it's almost impossible to hard brick a phone these days. Just install paragon with the instructions I gave its really fool proof these days to install rom. You will learn by trying if you mess up so be it that's what xda is here for to help.
Drop me a pm anytime if you need help
Sent from my Captivate running CyanogenMod7 using XDA Premium App
brendanmurphy said:
Don't worry about bricking I almost guarantee you will brick your phone once. But that is what Odin is for and it's almost impossible to hard brick a phone these days. Just install paragon with the instructions I gave its really fool proof these days to install rom. You will learn by trying if you mess up so be it that's what xda is here for to help.
Drop me a pm anytime if you need help
Sent from my Captivate running CyanogenMod7 using XDA Premium App
Click to expand...
Click to collapse
Well. Despite it being almost impossible, I've managed it once already within the first month of having one. Kind of why I'm a bit skittish about actually going through with it. I'm definitely all about modding and customizing things to your liking, but not having the funds to fall back on if I /do/ screw up bigtime again, yeeeeah.
After looking at Firefly and Serendipity thoroughly, though, I'm impressed. It's a tough choice between the three (Paragon, Serendipity, and Firefly). I'm leaning towards Serendipity now though after watching a video just to see the interface. Kinda not a huge fan of the GB launcher -- I liked the side-scrolling app launcher more, honestly -- but that's not a big deal.
So, let's see if I've got the details down right before I try anything. Search z4root in Market, install. Subsequently get Rom Manager, install it. Flash ClockworkMod (via Rom Manager). Pick a 2.2 rom (which will be a tough choice), and download it to my microSD card to put in the phone. Install said rom (via Rom Manager). And then, voila, it's done.
Did I miss anything, or am I actually following instructions right here?
Edit: Nope, can't find z4root in the Market anyways. Means I'd have to Sideload it, and until I get this driver issue solved, that's not gonna work either. That's gonna be the first thing necessary to fix since it also means I can't use Odin if I do anything wrong... Downloading Serendipity now though, so if I can get that fixed, I may go ahead and try this out after I get some sleep. But since I'm nocturnal, time for some rest. Hoping for some tips or pointers when I get back on. Definitely looking forward to good experiences with XDA and my Android phone.
Yea those are the exact steps its really simple. http://forum.xda-developers.com/showthread.php?t=944418 try this it will install drivers for you ans sideload apps. This is a useful tool
Sent from my Captivate running CyanogenMod7 using XDA Premium App
The.Se7enth said:
Only downside to rooting the phone is the voided warranty.
Click to expand...
Click to collapse
Quick question. Did you purchase the insurance through AT&T for the phone? If so, you will most likely always be able to get it replaced even if it's been rooted. It's just as simple as calling the help line, and saying that you have no idea what happened, and it won't work now. Of course that is worst case scenario
From my experience, the Captivate is a pretty difficult phone to hard brick compared to some others. For a beginner, all of this can be somewhat overwhelming, we've all been there. But once you get the hang of the whole process, you'll be good to go!
Yeah I've done that once already. Just called in and told them that it seems like a software problem and they replaced it no charge.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Beginner help....
AT&T warranty is for 1 year on new phones, 90 days on phones you purchase as refurbished. (30 day "I just don't like THIS phone" replacement/return in both cases.) If Radio Shack will not replace the phone, AT&T should swap. If neither is willing to help, Samsung will honor their 1 year warranty, but it requires shipping back to Samsung.
Your situation sounds like your Windows PC is the problem. A complete reinstall of Windows & apps (not just a quick MBR repair / install over top of existing stuff) may be your best bet if you can't use a different machine.
Kies Mini should upgrade your phone to 2.2 painlessly - without you having to do anything but plug it in and click the on screen button.
Also if you root and need to return it just flash back to stock which will take away root and at$t is none the wiser, most likely
peypey008 said:
Quick question. Did you purchase the insurance through AT&T for the phone? If so, you will most likely always be able to get it replaced even if it's been rooted. It's just as simple as calling the help line, and saying that you have no idea what happened, and it won't work now. Of course that is worst case scenario
From my experience, the Captivate is a pretty difficult phone to hard brick compared to some others. For a beginner, all of this can be somewhat overwhelming, we've all been there. But once you get the hang of the whole process, you'll be good to go!
Click to expand...
Click to collapse
Nope. Don't feel their insurance policies are worth it. You spend more money on the insurance policy in total, even if it's month-to-month, than you would on a brand new contractless phone. Besides, I had only made $120 from fixing up three ancient computers (so ancient they actually had ISA slots and DIMM SD-RAM memory -- one was even a Pentium II), and only had $50 by the time I bought the phone which was a couple months later. My $50 went towards the phone and a pack of screen protectors, while my mom covered the upgrade fee. Couldn't afford the insurance policy even if we wanted to.
But I do greatly appreciate the encouragement. I'll give it a go in a bit, and try out flashing Serendipity. I'll follow the official instructions from their own website though, because I read this on their FAQ:
"Never use ROM Manager. EVER, EVER, EVER, EVER, EVER!"
pouelle said:
AT&T warranty is for 1 year on new phones, 90 days on phones you purchase as refurbished. (30 day "I just don't like THIS phone" replacement/return in both cases.) If Radio Shack will not replace the phone, AT&T should swap. If neither is willing to help, Samsung will honor their 1 year warranty, but it requires shipping back to Samsung.
Your situation sounds like your Windows PC is the problem. A complete reinstall of Windows & apps (not just a quick MBR repair / install over top of existing stuff) may be your best bet if you can't use a different machine.
Kies Mini should upgrade your phone to 2.2 painlessly - without you having to do anything but plug it in and click the on screen button.
Click to expand...
Click to collapse
RadioShack replaced the phone the first time, but the manager there said after replacing it once, the warranty was thus void. I'm not sure if profanity is allowed here, but you can figure out which word I wanted to reply to him. It's eight letters long, starts with bull.
I've read posts on AT&T forums saying if the phone's bricked or can't be repaired by user methods though, especially if it's rooted, that they won't honor the warranty at all and will consider it user error and that you're out of luck. Even people who tried to upgrade to 2.2 stock had issues with that. But I dunno.
Anyways, my machine works perfectly for everything else. Before the repair, when I tried to upgrade? It was a fresh install. I had just reformatted it because it was performing sluggish before and I decided I wanted a single-boot installation instead of having my old dual-boot of Windows 7 and XP. It's now just XP for the time being, seeing as how the hardware's limited and I want to get the best out of it for gaming (I can run 7 with ease, but it uses more resources than XP, thus games don't run as well).
I realize earlier I may have come off as implying the upgrade to 2.2 process was difficult. I don't mean it was "difficult" by any means necessary. It was simply a plug the phone in, let all the drivers install, unhook and put in download mode, hook up again for more drivers. Restart phone, start up kies, hook up phone, and click "Upgrade phone" button. Accept the terms of service or whatever, and wait. Upgrade starts, phone flips into download mode on it's own, restarts a couple times, and voila, you're on 2.2. I thought it was a piece of cake. My issue is that regardless of how easy it was, it still ended up rather broken because all those applications were missing, on top of the fact the Settings panel was also gone, leaving me unable to perform a factory reset.
I have one last question. If I do somehow manage to get these drivers to work again (without reformatting, which I don't have the time to do), should I have the SIM card out while flashing the ROM? I'm wondering, subconsciously, if somehow that may have had something to do with the upgrade to 2.2 screwing up so bad. I had the SIM card in, with all my applications installed at first. Second time, no apps or anything were installed, but the SIM card was still in.
Edit: Well aware of most forums having a "do not double post" rule, as much as I want to bump this thread with an update on the issue. But, I've restarted my computer, tried a different USB cable, uninstalled and reinstalled the drivers from numerous different sources, and still the same "fatal error" issue on "Samsung Android ADB Composite Interface". I simply cannot get that to install whatsoever, and without it, the phone isn't detected as being hooked up even by SWM, much less anything else. Seriously, what do I do? I'm not reformatting my computer, because I simply see no reason for it, but I have no other computer I can use. How do I get these drivers to install properly like they did before?
The.Se7enth said:
At the time I tried, Kies itself didn't support the Captivate. Only Kies mini. And in order to do that upgrade, I had to install the drivers, then put the phone into download mode to install more drivers for some odd reason, restart the phone (taking out the battery and putting it back in), then hook it up. Kies mini wouldn't detect the phone for several tries at first, finally got it about the 10th time in. Then go to the "Upgrade phone" link, and yeah. I followed the instructions from Samsung's official SGH-i897 Froyo upgrade guide.
I did EXACTLY as the instructions say, down to the wire. Still ended up both times with all those applications missing and the settings panel missing, unable to do a factory reset without flashing back to 2.1 first.
Click to expand...
Click to collapse
Fail, Kies Mini works from Kies mode on the phone. It puts the phone into download mode when you start the upgrade from Kies Mini.
Just saying...
The.Se7enth said:
Nope. Don't feel their insurance policies are worth it. You spend more money on the insurance policy in total, even if it's month-to-month, than you would on a brand new contractless phone. Besides, I had only made $120 from fixing up three ancient computers (so ancient they actually had ISA slots and DIMM SD-RAM memory -- one was even a Pentium II), and only had $50 by the time I bought the phone which was a couple months later. My $50 went towards the phone and a pack of screen protectors, while my mom covered the upgrade fee. Couldn't afford the insurance policy even if we wanted to.
But I do greatly appreciate the encouragement. I'll give it a go in a bit, and try out flashing Serendipity. I'll follow the official instructions from their own website though, because I read this on their FAQ:
"Never use ROM Manager. EVER, EVER, EVER, EVER, EVER!"
RadioShack replaced the phone the first time, but the manager there said after replacing it once, the warranty was thus void. I'm not sure if profanity is allowed here, but you can figure out which word I wanted to reply to him. It's eight letters long, starts with bull.
I've read posts on AT&T forums saying if the phone's bricked or can't be repaired by user methods though, especially if it's rooted, that they won't honor the warranty at all and will consider it user error and that you're out of luck. Even people who tried to upgrade to 2.2 stock had issues with that. But I dunno.
Anyways, my machine works perfectly for everything else. Before the repair, when I tried to upgrade? It was a fresh install. I had just reformatted it because it was performing sluggish before and I decided I wanted a single-boot installation instead of having my old dual-boot of Windows 7 and XP. It's now just XP for the time being, seeing as how the hardware's limited and I want to get the best out of it for gaming (I can run 7 with ease, but it uses more resources than XP, thus games don't run as well).
I realize earlier I may have come off as implying the upgrade to 2.2 process was difficult. I don't mean it was "difficult" by any means necessary. It was simply a plug the phone in, let all the drivers install, unhook and put in download mode, hook up again for more drivers. Restart phone, start up kies, hook up phone, and click "Upgrade phone" button. Accept the terms of service or whatever, and wait. Upgrade starts, phone flips into download mode on it's own, restarts a couple times, and voila, you're on 2.2. I thought it was a piece of cake. My issue is that regardless of how easy it was, it still ended up rather broken because all those applications were missing, on top of the fact the Settings panel was also gone, leaving me unable to perform a factory reset.
I have one last question. If I do somehow manage to get these drivers to work again (without reformatting, which I don't have the time to do), should I have the SIM card out while flashing the ROM? I'm wondering, subconsciously, if somehow that may have had something to do with the upgrade to 2.2 screwing up so bad. I had the SIM card in, with all my applications installed at first. Second time, no apps or anything were installed, but the SIM card was still in.
Edit: Well aware of most forums having a "do not double post" rule, as much as I want to bump this thread with an update on the issue. But, I've restarted my computer, tried a different USB cable, uninstalled and reinstalled the drivers from numerous different sources, and still the same "fatal error" issue on "Samsung Android ADB Composite Interface". I simply cannot get that to install whatsoever, and without it, the phone isn't detected as being hooked up even by SWM, much less anything else. Seriously, what do I do? I'm not reformatting my computer, because I simply see no reason for it, but I have no other computer I can use. How do I get these drivers to install properly like they did before?
Click to expand...
Click to collapse
Yea once you have serendipity installed don't use rom manager but for initial install your fine
Sent from my Captivate running CyanogenMod7 using XDA Premium App
cappysw10 said:
Fail, Kies Mini works from Kies mode on the phone. It puts the phone into download mode when you start the upgrade from Kies Mini.
Just saying...
Click to expand...
Click to collapse
You can "say" all you want, my good sir, but google the instructions. They tell you clearly to put the phone into download mode TO FINISH INSTALLING DRIVERS. You don't start up Kies mini until after all the drivers are installed, at which point you hook up the phone with USB Debugging, not Kies mode. I appreciate your willingness to help, but be sure to read everything I say before you correct me. I'm not that slow. I read instructions thoroughly and I've read quite a lot of posts on these forums. I work with computers regularly -- just not Android. The issue had nothing to do with that anyway, so that doesn't even matter.
brendanmurphy said:
Yea once you have serendipity installed don't use rom manager but for initial install your fine
Sent from my Captivate running CyanogenMod7 using XDA Premium App
Click to expand...
Click to collapse
I'm sure it's possible, and I don't mean to come off disrespectful, but I'm just gonna go with the instructions on their website. Just seems a safer route to install a ROM by the creator's instructions, you know? Only thing I'm not sure about is what they mean by "Flash it in 2e recovery (twice)." on ClockworkMod.
The.Se7enth said:
I have one last question. If I do somehow manage to get these drivers to work again (without reformatting, which I don't have the time to do), should I have the SIM card out while flashing the ROM? I'm wondering, subconsciously, if somehow that may have had something to do with the upgrade to 2.2 screwing up so bad. I had the SIM card in, with all my applications installed at first. Second time, no apps or anything were installed, but the SIM card was still in.
Edit: Well aware of most forums having a "do not double post" rule, as much as I want to bump this thread with an update on the issue. But, I've restarted my computer, tried a different USB cable, uninstalled and reinstalled the drivers from numerous different sources, and still the same "fatal error" issue on "Samsung Android ADB Composite Interface". I simply cannot get that to install whatsoever, and without it, the phone isn't detected as being hooked up even by SWM, much less anything else. Seriously, what do I do? I'm not reformatting my computer, because I simply see no reason for it, but I have no other computer I can use. How do I get these drivers to install properly like they did before?
Click to expand...
Click to collapse
These two are still my top questions now. Is it a good idea to have the SIM card out during the upgrade process, and not put it back in until after the update is 100% complete?
Also, I'm really frustrated about this whole driver thing. I know the drivers aren't broken because I used them on this very computer before, and the repair shouldn't have damaged anything because absolutely everything else is working flawlessly. But every time I've uninstalled the drivers completely, and hook up the phone, it keeps getting a fatal error on that. Apparently "S3C6410 Android ADB" is the name of the device that can't install drivers.
Hey folks. I`m new to Android, but I am well versed in how to manipulate Linux systems and I've got a new SGH-i896 that Ive been itching to tear apart.
I've never touched a phone in regards to hacking, and I know there's a lot of system stuff that can be screwed up while tweaking. What I'd like to do is explore these custom ROMs and see which is best for my specific phone.
If anyone could talk me through a good first option for trying out, it would be great. I see so many options, but I'm not seeing a popular choice, or a safe "for-dummies" ROM. Thanks for any help.
JavaMac said:
Hey folks. I`m new to Android, but I am well versed in how to manipulate Linux systems and I've got a new SGH-i896 that Ive been itching to tear apart.
I've never touched a phone in regards to hacking, and I know there's a lot of system stuff that can be screwed up while tweaking. What I'd like to do is explore these custom ROMs and see which is best for my specific phone.
If anyone could talk me through a good first option for trying out, it would be great. I see so many options, but I'm not seeing a popular choice, or a safe "for-dummies" ROM. Thanks for any help.
Click to expand...
Click to collapse
Welcome!
Now first you must get your tools (Android SDK, Odin3) and study them a bit before flashing anything. Nothing is safe but if it's done properly your chance of bricking your phone are close to none.
Look in the Dev and Q&A for sticky post regarding flashing roms and how to start.
I would recommend you stay away from Gingerbread roms (2.3) for the moment. It requires to flash a new bootloader and you need a good understanding of how to flash and how to use Odin3 options before you venture there.
For your first flash i would recommend flashing Firefly rom but your free to select the one you prefer. Always read the first post of the rom to learn what it offers and don't.
Happy flashing
JavaMac said:
Hey folks. I`m new to Android, but I am well versed in how to manipulate Linux systems and I've got a new SGH-i896 that Ive been itching to tear apart.
I've never touched a phone in regards to hacking, and I know there's a lot of system stuff that can be screwed up while tweaking. What I'd like to do is explore these custom ROMs and see which is best for my specific phone.
If anyone could talk me through a good first option for trying out, it would be great. I see so many options, but I'm not seeing a popular choice, or a safe "for-dummies" ROM. Thanks for any help.
Click to expand...
Click to collapse
What he said^^^
I would start out reading a lot. Start here and here. Use this program to get started. This will allow you to flash FROYO. You can now flash FROYO custom ROMs.To flash Gingerbread go here read post 1 to get directions after flashing Stock FROYO. Once you have the GB bootloaders installed you should be able to flash custom GB ROMs. I stress read a lot before flashing. You can brick your phone easily if you don't. Good luck and welcome to the world of ROM flashing!
silvertag said:
Welcome!
For your first flash i would recommend flashing Firefly rom but your free to select the one you prefer. Always read the first post of the rom to learn what it offers and don't.
Happy flashing
Click to expand...
Click to collapse
I'll second firefly, very nice smooth rom, i used it for over 2 months.
I already had the Android SDK, as well as SuperOneClick. I went ahead and downloaded Odin3, and the Captivate Toolbox and the other linked tools. Thanks for the links by the way. I've also already taken a look at how to flash a custom ROM. I'm going to read a bit more and settle on a choice by tonight.
Thanks for all the help.
Having a bit of trouble on my first go
Hey folks. I went over the reading material that was provided and I went ahead with this guide
[link]http://forum.xda-developers.com/showthread.php?t=884364[/link]
I got through to the point where I had to use Odin. When I clicked start on Odin, it ran through the predicted cycles and claimed to be successful. My device won't mount now though. I can't see it in my computer anywhere, and I'm not sure how to continue.
Any thoughts would be appreciated. Thanks.
You were on stock 2.1 or 2.2 ?
What rom did you flash ?
What files did you put in Odin and with what boxes checked ?
Is the phone booting normally ?
What part does not mount ? (It's not detected by windows but charges when you plug in the usb cable ?)
Settings>applications>usb settings. Make sure thats set to mass storage.
stock has that checked to kies by default.
Let me clarify:
My phone is currently only sitting at the battery screen, with an empty battery image and a spinner.
I can bring up an AT&T splash screen that says "World Phone" below it if I follow the instructions to recovery mode, but it still does nothing.
I'm afraid I've bricked the phone, and I'm missing some clue as to why.
if something comes up on the screen it is not bricked.....i hate that word
you are not bricked. any sign of life at all means not bricked.
what odin did you use? im guessing odin one click, which means you have a newer build phone and it bootloops when odin one click is used.
get into download at this point you may need a jig, once in download mode use this package and you will be ok (you are canadian right?)http://forum.xda-developers.com/showthread.php?t=979133
Thanks for the tip pirateghost.
Hmm, I might be offended a little.
You thank the guy who pops in just to correct your jargon and not the guy giving you a link to help you?
studacris said:
Hmm, I might be offended a little.
You thank the guy who pops in just to correct your jargon and not the guy giving you a link to help you?
Click to expand...
Click to collapse
LOL
damn, studa, tryin to drag me into the dirt
I'm wondering if there's a way to do this without a jig. I don't really want to get that involved if I don't have to.
If I do have to, I will, but let's try to keep this in the software department if we can.
Thanks to everyone who's been helping out here.
Lol I was only joking
no harm done
there are a couple button combos to try if those don't work a jig is needed, but it's a very cheap and easy process to make one not "involved" at all or under 10 us dollars if you were to buy one.
Alright button combos to try:
Both volumes held plug in usb cable.
Cable in, pull the battery, hold the volume buttons while reinserting the battery.
JavaMac said:
I'm wondering if there's a way to do this without a jig. I don't really want to get that involved if I don't have to.
If I do have to, I will, but let's try to keep this in the software department if we can.
Thanks to everyone who's been helping out here.
Click to expand...
Click to collapse
-Remove the battery
-Remove the sim card
-Remove any external sd-card
-Pop battery in
-Hold BOTH volume buttons (on the left) and plug usb cable.
Are you back in download mode ?
Okay, I tried all the button combos, and it did nothing different.
I've only got the one micro usb right now. I guess that means I've got to go out and get another, along with some resistors?
This sucks. I guess I should have remained happy with the Android Rogers gave me.
If you insulate the resistors well enough you don't need to chop up the cable... You can touch the leads of the resistor loop thing you made directly to pins 4 and 5 on the phones usb port. Granted that way takes ALOT more fiddling with to work, but you don't have to hack a cable.
studacris said:
If you insulate the resistors well enough you don't need to chop up the cable... You can touch the leads of the resistor loop thing you made directly to pins 4 and 5 on the phones usb port. Granted that way takes ALOT more fiddling with to work, but you don't have to hack a cable.
Click to expand...
Click to collapse
So if I get the proper resistors, protect my thumb and finger, and apply them carefully to pins four and five on the phone's connection, it works the same way?
Actually, not my phone but a friend's. I was trying to restore it to stock with Odin in order to flash Cyanogen, however Odin was being a real PITA. Through numerous attempts, Odin would refuse to finish the restoration process, often hanging at sbl.bin or Setting PIT file. I tried at least ten times to get it to flash correctly. The final time I decided to let it sit overnight and flash, just in case. When I got up this morning though, it was still hung up. I unplugged the phone and pulled the battery like I had done multiple times the night before, so that I coould give it one last try before I went to work. But this time, the phone wouldn't go into download mode. I had been using the USB and 3 button combo method, but nothing this time. The phone shows no signs of life at this point, and I really don't have anything short of a JTAG left to try on it. Now I have to buy my friend a new phone.
Has anyone else experienced this kind of terrible performance from ODIN? And is there anything other than JTAG I can try. If there is someone out there that can fix it with JTAG, I would also pay money for that. I don't have the soldering skills necessary to fix this thing.
They sell the pre made jigs you can buy, just search for it and you will find plenty
Sent from my SGH-I897 using XDA App
The battery doesn't charge in download mode, the battery could very well just be dead. Pull the battery, reinsert it and plug in the phone to charge it, if all it does is get really hot and never shows any sign of life that is a brick. Check your PM.
super coffee said:
Through numerous attempts, Odin would refuse to finish the restoration process, often hanging at sbl.bin or Setting PIT file. I tried at least ten times to get it to flash correctly.
Click to expand...
Click to collapse
Can't really blame anyone but yourself for that one.. If it hung at sbl.bin and you managed to not brick it, you dodged a bullet.
Anyway, sounds like you dodged several bullets and then the inevitable happened. A jig won't help, and you're correct in your assumption that JTAG is your only way out. Fortunately for you, one of our fellow captivaters is still offering (at least to my knowledge) a free JTAG service. You should contact him to see if he'd be willing to restore your device, his name is connexion2005.
For future reference, don't flash back to stock unless you really need to. And when you do, don't flash an image that includes bootloaders. If you have bootloaders that work (3 button combo enabled on 2.2- bootloaders or 2.3 bootloaders), use a non one-click odin with an image that doesn't include sbl.bin or boot.bin; otherwise you're just taking unnecessary risks.
little8020 said:
They sell the pre made jigs you can buy, just search for it and you will find plenty
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
I got one off eBay for 10 bucks. Probably the best investment I've made as I have encountered about every brick situation you could imagine.
This may sound stupid, but maybe trying to flash GB bootloaders with ODIN(not one-click) could work? Exhausting all options before sending your phone in or having somebody JTAG would be preferable.
+1...they are well worth the money if you do any ROM flashing!
I have same problems before. 3 button combo method didn't work at all. No JTAG at that time.
When you plug your phone to computer, make sure it still can detect "SAMSUNG Android USB composite Device", but not "Unknown devices".
Even I wasn't on download mode or recovery mode, the odin able detect my phone as COM port then I was using Odin3 v1.8. then I put "galaxys-bootloader-JVB.tar.md5" to bootloader since I already have 2.3.3 rom before.
Another "dad, my friend has this problem" thread!?
For future reference, use Heimdall and read instructions thoroughly and multiple times. I just started using Heimdall when I made my move to flash gingerbread again when the KF1 ROM came out and I love it. Regardless how well a program works though, it's only as good as the person operating it. There are TONS of people here far more educated than me when it comes to flashing anything, but I have never bricked, or soft bricked even (yet) and I flash a decent amount.
If all else fails, I did have good luck with Josh @ mobiletechvideos (haven't posted enough times to be allowed to post the link, but he's on youtube. He's also here as connexion2005) he was able to unbrick my phone for $50. The post office does not seem to like to deliver mail from him to me, but I'm typing this on the phone he unbricked.
Sent from my GT-I9000 using XDA App
Josh @ mobiletechvideos rocks!
He unbricked my Captivate!
There is not a problem with odin! Why do people always say don't use odin because it will brick your phone. You have to use it correctly. Make sure before you even open odin that the computer recognizes your phone and you have all of the correct drivers, etc. installed BEFORE even messing with odin. Also be sure to connect to a usb port that is connected to your hard drive to limit the chance of the computer not recognizing your device.
megatronisabeast said:
Also be sure to connect to a usb port that is connected to your hard drive to limit the chance of the computer not recognizing your device.
Click to expand...
Click to collapse
Your hard drive has usb ports?
You mean motherboard?
cappysw10 said:
Your hard drive has usb ports?
You mean motherboard?
Click to expand...
Click to collapse
Yes, the motherboard! Was in the middle of a tech class when I posted that! Guess I can't multi task! Thanks!
Thanks for the feedback guys. I'm here when you need the impossible done to your Captivate...
megatronisabeast said:
There is not a problem with odin! Why do people always say don't use odin because it will brick your phone. You have to use it correctly. Make sure before you even open odin that the computer recognizes your phone and you have all of the correct drivers, etc. installed BEFORE even messing with odin. Also be sure to connect to a usb port that is connected to your hard drive to limit the chance of the computer not recognizing your device.
Click to expand...
Click to collapse
I've had odin fail a few times in a row on me when flashing gb bootloaders for i897. I had odin flashed countless times on multiple devices and computers. I'm pretty sure Odin isn't foolproof. Not everything can be contributed to pebcak, although the vary majority of problems posted on xda are...
kimchi0400 said:
I've had odin fail a few times in a row on me when flashing gb bootloaders for i897. I had odin flashed countless times on multiple devices and computers. I'm pretty sure Odin isn't foolproof. Not everything can be contributed to pebcak, although the vary majority of problems posted on xda are...
Click to expand...
Click to collapse
everytime odin has 'failed' for me, it's been a user error on my part. you need to follow the steps sequentially otherwise you have a higher probability of failure/brickage.
rmal0 said:
everytime odin has 'failed' for me, it's been a user error on my part. you need to follow the steps sequentially otherwise you have a higher probability of failure/brickage.
Click to expand...
Click to collapse
I honestly think that a lot of information here on XDA is only partial and this will get some into trouble. I know people say "search for it, it's here" and it is but the problem is that 10% of the time the information that someone is looking for is buried in a thread and the other 90% the search results list the same question being asked and answered with "it's here search" or "Did you search??"
There honestly should be posting guidelines, for everyone, I mean people take all the time to write disclaimers why not proper directions? Is there a standard Template? If I'm missing it please feel free to point it out.
For example:
This is a 9000/897/896 based ROM
This ROM needs the following bootloaders: ....
This ROM contains Bootloaders: Yes/No
This ROM will change your product code: Yes/No
This ROM requires a Davlik wipe to work: Yes/No
This Kernel is 9000/897/896 based
blah blah blah.......
If the information is readily and easily available then the amount of "dumb" question should go down dramatically and then there will be a "standard"
But then again it's Android/Linux, being fragmented is half the fun..
</rant>Just needed to vent...
OK, My first attempt at messing with the firmware on an Android phone resulted in dismal failure and a dead phone..
Here's the scenario as events unfolded..
Bought an unlocked Galaxy S 4G
Trying to connect my phone to my PC resulted in dismal failure, wondered if it might be a dodgy firmware someone had installed.
*#2663# to update the TSP firmware. This just hung on the updating screen. Eventually the battery gave out. (Don't ask me why I was updating the Touch Screen Panel Firmware, I don't know.. I was fiddling. )
Recharged the battery and rebooted the phone.. Menu and Back buttons on touch pannel light but don't work.
Searched this forum and many others, seems to be a common problem but no clues as to how to resolve.
So I downloaded Odin 307 and the USB drivers, put phone in download mode, installed the following via Odin
CODE_T959VUVKG4_CL385158_REV00_user_low_noship.tar
SGH-T959V-CSC-TMB-VIBRANTP.tar
T959VUVKG4-Phone-CL1037720.tar
Worked fine, but didn't fix the issue with the TSP.
Somewhere I read that maybe it was partition corruption, so I decided to repartition. Ticked the "Repartition" box and used Hawk_Sidekick_VibrantPlus_831.pit (All four of these came as a package I found linked to on this site somewhere.) Odin said it was ok, but now I can't even power the phone on. Screen stays blank. Computer does not recognise USB device. Odin doesn't see it. It seems to be dead.
So.. Is there a rescue remedy from this scenario, or do I use this piece of glass and electronics to wedge my door open?
Please help I'm not going to pretend I knew what I was doing, but I'd like to unbrick this thing so I can at least make phone calls on it and send emails to people saying what a plonker I've been..
Thanks. :crying:
Do you have a T959V or T959 ?
Check under your battery.
Sent from my SGH-T959V using xda premium
T959V
No, I've not tried that. I'll give it a go.
The Heimdall One Click has saved my phone quite a few times, it's simple and effective! Let us know how it goes!
Sent from my Illūsîøn'd Galaxy S³
Ok, so I managed to get it into Download mode and reflashed it in Odin. I'm going to have a go with "oneclick" and see what happens, but at this point the only outstanding thing to fix is the TSP, which is still kaput. (Maybe one click will fix that) I've searched and searched on this forum, there's a whole bunch of dead threads where people have killed their TSP, and no resulting fixes posted. If anyone has any ideas, its would be great if you could post them, because at the moment, "menu" and "back" are still U/S.
Thanks for your help so far. If I get a solution, I'll post it here, I hate abandoned threads where people leech solutions to their probems and don't give feedback.
OK, So I tried this : http://forum.xda-developers.com/showpost.php?p=23121150&postcount=12&nocache=1&z=6720291850525859
No luck..
Next thing to try is an older version of the O/S, apparently if I put on then it downgrades one of the firmware, and running the update again fixes the issue. (On can only hope.. Now I gotta go see if I can find an older version of the OS and try this http://forum.xda-developers.com/showpost.php?p=21987511&postcount=9
:fingers-crossed:
Oh well.. On the plus side, I bought this little cheap phone to play around and learn on.. I seem to be doing just that. :cyclops: