Related
I'm not sure about the rest of you Captivate owners, but mine has been undergoing a serious update for the past 2 hours. The first update I noticed was to Kies Mini from v10082.8.1 to v1.0.0.110104.1. I couldn't upgrade using Kies mini. Instead, Kies mini simply updated itself.
After seeing this, I performed a Phone update from my Captivate itself and it's still going at it.
Let us know if it is froyo
Sent from my SAMSUNG-SGH-I897 using XDA App
not to burst your bubble, but it probably isn't, for like the millionth time if official Froyo is released you will hear about it, stop being so optimistic whenever a kies update comes out. Trust me when this thing hits it'll hit hard, you won't not know lol
Sent from my bullet proof phone
phoney_stuff said:
I'm not sure about the rest of you Captivate owners, but mine has been undergoing a serious update for the past 2 hours. The first update I noticed was to Kies Mini from v10082.8.1 to v1.0.0.110104.1. I couldn't upgrade using Kies mini. Instead, Kies mini simply updated itself.
After seeing this, I performed a Phone update from my Captivate itself and it's still going at it.
Click to expand...
Click to collapse
My Kies mini updated sometime last week to:
SAMSUNG Kies mini Application v1.0.0.10104_1
It might be in preparation for the froyo update but not here yet.
Nope!
Just attempted OTA and no new firmware and then did Kies mini and latest is jh7 sorry.
phoney_stuff said:
I'm not sure about the rest of you Captivate owners, but mine has been undergoing a serious update for the past 2 hours. The first update I noticed was to Kies Mini from v10082.8.1 to v1.0.0.110104.1. I couldn't upgrade using Kies mini. Instead, Kies mini simply updated itself.
After seeing this, I performed a Phone update from my Captivate itself and it's still going at it.
Click to expand...
Click to collapse
Many posts about Kies Mini update last week.
When Froyo does drop you'll see all kinds of articles on the regular internet sites.
Added: I'm still betting on St. Patrick's Day!
those #'s refer to KIES software versions.
It is simply and update for your Kies desktop software......nothing to do with firmware for your smartphone.
I'm still going for Christmas - although they had said by end of November... so we still have what? 2 more days at this point
avgjoegeek said:
I'm still going for Christmas - although they had said by end of November... so we still have what? 2 more days at this point
Click to expand...
Click to collapse
Actually - the date for US has always been "by the end of the year" as reported by SamsungUSA twitter and facebook. It was the international Galaxy S (i9000) that was end of November. Many sites interpreted that to mean us to as our phones are also "Galaxy S".
My bad... false alarm. Nothing to see here. Move along.
I'm still puzzled why both Kies mini and my phone took ages to do whatever it did. Whateva! I want some Froyo!
Well all signs point to very soon. Samsung said we would get it by the end of the year, which means in less than a month. There was also a tip a couple weeks ago that Captivates running Froyo out of the box would go on sale on the first Sunday in December and the OTA would begin rolling out possibly the Monday after (12/6).
Can we all agree to post news about a Froyo update AFTER you actually get the OS on your phone?
It seems like every other day someone posts news that they have been notified/downloading an update.
skinien said:
Can we all agree to post news about a Froyo update AFTER you actually get the OS on your phone?
It seems like every other day someone posts news that they have been notified/downloading an update.
Click to expand...
Click to collapse
THIS is the best advice anybody has given on the oft repeated subject - +2 for this person...
Speaking of the new version of Kies... Since mine upgraded, it won't let me check for updates while in debug mode. When I take it out of debug mode, my PC doesn't see my phone... Any ideas?
You're chasing after a Unicorn people.
MikeyMike01 said:
You're chasing after a Unicorn people.
Click to expand...
Click to collapse
Not to mention stock froyo would be a Unicorn with half a horn
gk527 said:
Speaking of the new version of Kies... Since mine upgraded, it won't let me check for updates while in debug mode. When I take it out of debug mode, my PC doesn't see my phone... Any ideas?
Click to expand...
Click to collapse
What os are you running? If it Win 7 x64, this is what I run, then you could try a fresh install of Kies. Scrub the system of all things Samsung (apps, drivers, etc..) and then do a fresh install of Kies. Let it install the drivers. Once complete reconnect phone and let Windows reinstall drivers for device. Then see if you can get the computer to see the phone.
If that doesn't work, there was a post about a patched .dll that worked for some. Search for "Kies doesn't recognize my phone".
cappysw10 said:
What os are you running? If it Win 7 x64, this is what I run, then you could try a fresh install of Kies. Scrub the system of all things Samsung (apps, drivers, etc..) and then do a fresh install of Kies. Let it install the drivers. Once complete reconnect phone and let Windows reinstall drivers for device. Then see if you can get the computer to see the phone.
If that doesn't work, there was a post about a patched .dll that worked for some. Search for "Kies doesn't recognize my phone".
Click to expand...
Click to collapse
I am running Windows 7 Ultimate x64. Thanks for the information. I'll give it a try.
alphadog00 said:
Actually - the date for US has always been "by the end of the year" as reported by SamsungUSA twitter and facebook. It was the international Galaxy S (i9000) that was end of November. Many sites interpreted that to mean us to as our phones are also "Galaxy S".
Click to expand...
Click to collapse
Maybe their "by the end of the year" is lunar calendar year... which will put the release at 2/2/2011.
With the upcoming Froyo update coming in the future sometime I have never been able to connect with Kies. It is always stuck on connecting device have tried it on two computers with the same result. What other tips can anyone give to correct this (have already searched the forums and read numerous threads) or will they actually release a Kies for the Captivate. Would like to have the ability to move data back and forth from the mobile device without jumping through hoops.
Thanks, Roger
Sounds familiar
charrog,
I've had my Captivate since August and I haven't found anything to get it to reliably connect to a computer. It seems that others on here have tricky connections at best. I've managed to connect but nothing reliably. I've had Kies, Kies mini and USB connections all work at times and not work at times. I've had 2 different Captivates and 5 different computers I've tried with. I've used Win XP, Vista and Win 7. They all acted similar so I do not think it is a Windows thing. You will find numerous "fixes" posted on here but if you do your homework you will find that none of them work for everyone and different "fixes" work for different people. If I had to guess I would say that it depends on what you have installed and configured on the phone and the computer before you know what "fix" might work for you, if any work. Either way, it's a crapshoot trying to get connectivity between the Captivate and a computer. Hope you have better luck than I have had.
I'm running Windows 7 Professional and a virgin, er ah, unrooted Captivate phone.
Device Manager reports Windows sees the phone as a portable device: SGH-I87. The two drives are accessible from C:\. The drivers are properly installed because under USB controllers I see SAMSUNG Android USB Composite Device. From Windows I can navigate both the SD card and the phone's built-in storage.
But I have never been able to connect to AT&T's server using Kies Mini. Well, never is not correct. I initially installed Kies Mini For Captivate 10082_8_1 and could connect and got a response my phone was up-to-date (or something similar). However, at one log in Kies automatically updated to v1.0.0.10104_1 and since that time no connection has been possible. Kies just sits there saying I should connect a phone which I do and nothing happens at all.
Other stuff: 1) I removed Kies Mini entirely and reinstalled the original version. No sooner I booted the old version up and it updated again. 2) The first version wanted to connect with USB debugging "on." The new version explicitly says to turn USB debugging "off." 3) It's curious the updated version of Kies Mini is not the one on Samsung's AT&T support site; the old one is the only version there.
It's my conclusion the phone is fine and the drivers are fine. Kies Mini is either incompatible with the phone or with Windows. Just how AT&T and Samsung intend to back out of this mess is hard to figure.
Just why neither AT&T nor Samsung choose to communicate on what's going on confirms what we all know. The technology is pretty good but the concern--or appreciation--either company expresses for its tech-savvy public is frustratingly, totally absent.
Samsung's way of dealing with the Kies not working issue for me was after a 1 1/2 hour phone call to tech support that got upgraded to a tier 2 tech the final result was "I'm sorry sir but Kies is not supported in the United States." They suggested looking in the market and PURCHASING software that would allow me to connect my phone and computer together. Needless to say, my next phone WILL NOT BE A SAMSUNG!
For me this works 100% of the time.
1. Make sure kies mini is closed
2. Connect phone using usb cable with main usb port- no extension cable and no front ports
3. Phone should be set to kies mode or ask
4. If asked select kies on phone but either way wait for phone to go past intializing and say connected
5. Open kies mini on pc
6. Kies should see your phone
7. If server unavailable close kies and reopen (sometimes 5 times)
8. If update found you may see another server unavailable message- try again
Sent from my MB520 using XDA App
That rep was mis-informed, Marty. Indeed, the recent, full versions of Kies specifically prevent support for any Samsung Android phone sold by AT&T. But, Kies Mini is solely to support (I'm laughing so hard here I can barely type) AT&T's Samsung Android phones. That bit of software is a very silly, one-horse show.
I have several Samsung products in my home. I think they make fine products and, in my experience, they are well supported (not excellently but rather adequately). I am almost certain the problems we are experiencing result entirely from AT&T's effort to extract maximum possible revenue from the phones they sell and, at the same time, to minimize their support costs to the lowest level possible.
One final point: Us "techie-types" represent a tiny fraction of their overall audience. If they lost all of us it would likely make a tiny, insignificant dip in their revenue stream. The shame of this is that if they made some accommodation to us they might significantly increase revenues. I can't tell you how many people ask me what phone to buy. For those who are stuck with AT&T I have to recommend an HTC phone over a Samsung phone and for those who can use another carrier I am forced to recommend they use that other carrier.
I really like the Captivate and Android but I am forced to stay with AT&T. Every day my resentment for my imprisonment advances by several points.
alphadog00 said:
For me this works 100% of the time.
....
6. Kies should see your phone
...
Click to expand...
Click to collapse
Ah, but it does not!
Just for the heck of it, I rebooted Windows and turned off the phone. Then I started Windows. I opened Device Manager so I could watch what Windows was up to as I followed your instructions.
I connected the USB cable to the phone and started the phone. When the phone was connected--but Kies still not started--I touched "Kies (Firmware update)" on the phone. In Device Manager I could see both the device (Portable Devices) and the drivers (USB controllers) had properly initialized. The phone's screen reported "Connected... Press the home key to quit Samsung Kies." (Note Samsung Kies had not been started which is, I think, some kind of a clue as to what's wrong). Then, I started Samsung Kies. Kies wanted me to connect a phone. Endlessly. Mindlessly.
Did it all again. Same result. To his/her credit, whatever some programmer did wrong fails consistently. (I am cursed by always seeing the bright side of every dark situation. )
We're all dealing with folk medicine and voodoo here. Each one of us has had something that works for him/her upon occasion and, in good faith, we each pass on our "good news" as if we had just found the Holy Grail.
Frustration is a word I use to indicate I'm confident my next attempt will meet with success. The word I use to describe something that will never work until something I have no way of knowing is changed by someone who does not care in the least about my frustration is disgust.
I'm quite much disgusted with AT&T as regards support for this phone. I actually don't think Samsung deserves my ire. I'm pretty sure--by holding a promise of selling thousands of Samsung phones over Samsung's head--AT&T by either its indifference or its incompetence or both has jeopardized Samsung's reputation and bastardized the Captivate--an otherwise excellent phone in most respects--at the same time.
Picsman said:
Ah, but it does not!
Just for the heck of it, I rebooted Windows and turned off the phone. Then I started Windows. I opened Device Manager so I could watch what Windows was up to as I followed your instructions.
I connected the USB cable to the phone and started the phone. When the phone was connected--but Kies still not started--I touched "Kies (Firmware update)" on the phone. In Device Manager I could see both the device (Portable Devices) and the drivers (USB controllers) had properly initialized. The phone's screen reported "Connected... Press the home key to quit Samsung Kies." (Note Samsung Kies had not been started which is, I think, some kind of a clue as to what's wrong). Then, I started Samsung Kies. Kies wanted me to connect a phone. Endlessly. Mindlessly.
Did it all again. Same result. To his/her credit, whatever some programmer did wrong fails consistently. (I am cursed by always seeing the bright side of every dark situation. )
We're all dealing with folk medicine and voodoo here. Each one of us has had something that works for him/her upon occasion and, in good faith, we each pass on our "good news" as if we had just found the Holy Grail.
Frustration is a word I use to indicate I'm confident my next attempt will meet with success. The word I use to describe something that will never work until something I have no way of knowing is changed by someone who does not care in the least about my frustration is disgust.
I'm quite much disgusted with AT&T as regards support for this phone. I actually don't think Samsung deserves my ire. I'm pretty sure--by holding a promise of selling thousands of Samsung phones over Samsung's head--AT&T by either its indifference or its incompetence or both has jeopardized Samsung's reputation and bastardized the Captivate--an otherwise excellent phone in most respects--at the same time.
Click to expand...
Click to collapse
Are you using Kies or Kies mini?
My instructions are for Kies Mini. The full version of Kies will not connect to the captivate - older versions will though. But I will admit it is difficult. with a mix of drivers (captivate, and generic samsung) and 2 different versions of kies, the full version of Kies is very hit or miss when connecting. It also is finicky about USB ports and cables.
Everything I mention above relates to Kies Mini...
The last version of the full Kies which works with this phone is v1.5.3.10093_82. Because I have installed software which duplicates every feature I would use in the full version, I have never tried to install it.
Picsman said:
That rep was mis-informed, Marty. Indeed, the recent, full versions of Kies specifically prevent support for any Samsung Android phone sold by AT&T. But, Kies Mini is solely to support (I'm laughing so hard here I can barely type) AT&T's Samsung Android phones. That bit of software is a very silly, one-horse show.
I have several Samsung products in my home. I think they make fine products and, in my experience, they are well supported (not excellently but rather adequately). I am almost certain the problems we are experiencing result entirely from AT&T's effort to extract maximum possible revenue from the phones they sell and, at the same time, to minimize their support costs to the lowest level possible.
One final point: Us "techie-types" represent a tiny fraction of their overall audience. If they lost all of us it would likely make a tiny, insignificant dip in their revenue stream. The shame of this is that if they made some accommodation to us they might significantly increase revenues. I can't tell you how many people ask me what phone to buy. For those who are stuck with AT&T I have to recommend an HTC phone over a Samsung phone and for those who can use another carrier I am forced to recommend they use that other carrier.
I really like the Captivate and Android but I am forced to stay with AT&T. Every day my resentment for my imprisonment advances by several points.
Click to expand...
Click to collapse
Picsman,
I gave up on trying to get Samsung to help me by the time Kies mini came out. It's like gambling each time I connect the USB cable. Today it might connect, tomorrow or later today it might not. My issue is that Samsung and ATT advertised the phone as being able to sync with Outlook. While trying to get that to work the Samsung techs gave up on me and used the "Kies not supported" line to just end my tech phone call. I do the same as you now. When my friends see my new snazzy phone they all ask about it, I was even asked by a waiter at a restaraunt the other day. I tell them all the same thing. I love Android, ATT is so-so and stay away from Samsung phones. I've had lots of years of success with HTC phones so I recommend those. As far as carrier I just tell everyone to look for the best deal. The carriers have all gotten past the point where I care about loyalty. I've been with ATT since back when it was still Bellsouth or was it Cingular then Bellsouth, either way, over 12 years. Do they give me any special deal? nope. The good deals go to new customers. The best deal you can find is who I recommend anymore unless there is a reason for something different like no reception for so and so carrier in my area, etc. I don't recommend one way or the other the iPhone. I won't buy one because Steve Jobs thinks he is god and he gets to pick what I do with my phone and what apps I can load. I won't do business that way so the iPhone is not an option for me. The part I hate most is that I'm afraid to flash and try new ROMS since everything I see about fixing a bricked phone requires a USB connection and mine doesn't work more than it does work.
As I was reading your lament it occurred to me everything you said is somehow applicable to almost everything bought and sold these days. There is no such thing as reward for being a long-term customer and there is no such thing as customer service. Like the old days of the snake oil salesman rumbling into town with his horse and wagon, the objective is to sell as many bottles of the magic potion he has and then get the heck out of Dodge before there's a critical mass of people yelling "liar, liar." It's all a sad commentary on how things are these days.
It's sad, but seems true in most cases anymore. The bigger the company the more it happens too it seems.
Ok I have done the impossible well at least it seemed that way I have been able to install the mtp drivers I downloaded the new Kies version for the Captivate listed here after connecting instead of stuck on connecting to PC it now says The device is not supported by Kies. I downloaded it from here http://www.samsung.com/ca/support/d...&prd_mdl_name=SGH-I896&prd_ia_sub_class_cd=P#
This makes no sense any ideas?
Oh this is what I did to fix the mtp driver issue...
This is not correct. I think your driver is outdated. Could you do what I said:
- uninstall the driver (click right mouse button on "Android MTP" and select "uninstall" in the menu)
- disconnect the device
- remove from windows folder/subfolders everything related: wpdmtp*.* (especially wpdmtp.inf and WPDMTPHW.INF in windows/inf folder)
- reinstall windows media player ver 11 or 12 (depends on windows version, ver11 for Windows XP)
- connect your device and install driver automatically
The device should be reported as I9000 or similar not "MTP device" and not "Android MTP"
charrog said:
Oh this is what I did to fix the mtp driver issue...
This is not correct. I think your driver is outdated. Could you do what I said:
...
The device should be reported as I9000 or similar not "MTP device" and not "Android MTP"
Click to expand...
Click to collapse
I'm confused! It's hard to figure out how your two messages are related to each other.
The site you show is in Canada and, while for a Captivate, it seems to be for a SGH-i896 as opposed to a SGH-i897 which is not Rogers but rather AT&T. And, what's this about an I9000?
To get help, you need to explain what device you have (Samsung model number), your carrier (Rogers or whom), and what you are trying to do.
If the Kies you downloaded says it does not support your phone, it may be because your phone is not an SGH-i896.
Need more info, please.
Yes you are correct mine is a ATT version no wonder oh well was excited for a moment thought it was released for all Captivates oh well at least I finally got the MTP issue resolved....the info to fix the MTP problem was from a this thread http://forum.xda-developers.com/showpost.php?p=8701204&postcount=76
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.
Alright, so, to get started, I am actually decently tech savvy, and I wish i had rooted my phone before I even tried following the crap that samsung put up, but heres how it went.
I have a Samsung Infuse 4G on the ATT network
I finally found out how to update to Gingerbread through Kies. I spent all night charging my phone, went to Kies, and started the upgrade. About 6% through the upgrade, it said it needed an emergency recovery. I was worried, and I followed all instructions. I let the emergency recovery page sit for a day, and all it did was sit at 6% the whole time, so I resorted to my next best option, rooting it.
I have tried Ultimate Unbrick, One Click Unbrick, and Hiemdall, though I didn't get extensive with Hiemdall.
One Click said it was successful, but my phone doesn't turn on, so I tried the emergency recovery again, and still sat at 6%, then it switched to that it couldn't fix it.
Ultimate Unbrick starts off well, seeming as it is doing soemthing, but then freezes at factoryfs.rfs. Mind you I am running it in compatability mode for XP SP2 as an administrator, and I have run it on Win7 as an admin as well.
Hiemdall I got a little confused, so Im going to try that again.
Im gonna have to say, Im done with Samsung after this phone. Ive had samsung phones for 10 years (not by choice, im 19 and my mom pays for it), and every time something stupid happens, its like they kill themselves on purpose.
Is anyone possibly able to help me get my phone back to working condition? I wont be able to get a new phone for about a month, and thats only if I can find a job, which is hard when I have no phone.
Thank you to anyone who can help.
Does your phone display anything on its screen at all? If so, there's still hope.
Have you installed drivers properly?
Make sure that anything related to Kies is killed on your computer's task manager.
Try using different USB ports.
As much as possible, use a Windows XP. I had the same "stuck at factoryfs.rfs" problem and I tried it at an XP and it worked.
If nothing works, try buying a jig off of e-bay. They're about a dollar or two. Invest in some.
If it's completely borked, time to go buy an S3.
Sent from my SAMSUNG-SGH-I997 using xda premium
I can get into download mode where it shows the android shoveling in a caution sign
I installed the drivers
I havent checked that kies thing yet, Ill do that now
Ill try another USB port and get back to ya on that part
I don't own any computers with windows XP. Only a Win7 and a crappy laptop with Ubuntu on it (the laptop is crappy, not ubuntu)
Im so broke a candybar looks like rich food
And Im done with Samsung after this, Ill prob go windows phone and hack the Android market onto it.
LMAO Idk I still like Samsung over HTC and Apple. It can get really complicated --yes -- but it's worth.
Also, make sure to restart computer and then do the things I suggested you to do.
Sent from my SAMSUNG-SGH-I997 using xda premium
Im aiming for Nokia.
So, I disabled kies
Restarted my computer
Tried a different USB port
restarted Odin
Reran everything
and now, it wont even get to factoryfs.rfs
Do you possibly have a link to Hiemdall thats the newest version?
You should restart before disabling Kies. This is because of the fact that when you restart, your computer re-runs Kies.
Sent from my SAMSUNG-SGH-I997 using xda premium
I disabled after I restarted as well. Sorry, my steps were out of order.
Hmmm that's odd. Try it on a different computer tomorrow. Possibly a friend's?
Sent from my SAMSUNG-SGH-I997 using xda premium
Im gonna try heimdall first and see if I can contact a friend tomorrow. I just moved and my friends out here are more busy than the other ones I used to live by.
Heimdall Link.
Try fresh installation remove drivers from Driver Manger, run the drivers again and use Heimdall package. you need to have latest java and it need to be run as application not in any of the zip/jar file opener like 7zip etc., right click and you will see run using java<your version >
http://forum.xda-developers.com/showthread.php?t=1524081
it is clearly explained on the link what to do,
If you found difficult you can read the thread to see some probable answers as well.
Hope it will solve your query.
So I'm reading this everywhere and it says I have to use kies to upgrade the software. After reinstalling kies and formatting the tablet, kies is telline me that my device cannot receive software updates via kies. What gives?
How do I do this, this is very frustrating. Why can't Samsung just update their crap over the air like everyone else. Do I need to manually download the firmware from here and install it via the sd card?
Thanks.
tab plus wifi only US live oTA but!!!
its available. mine just came OTA when i turned it on this morning 6210 tab plus wifi only. but when i tried to install it it didn't work. its up on the sammobile site too as least but i don't have a pc (have a mac) to run that ridiculous kies app. go to galaxy tab plus general here on xda and there is a thread running about the new ics out (unrooted)
Same here. I've had a couple of firmware updates in the last week or so but I'm still at 3.2. Either its prepping my tablet for ICS or they were true 3.2 updates.
I chatted with a Samsung tech rep and she said that they were upgrading customers in batches and not everyone at once. Never heard that one before. I suppose if you wanted to keep the load on your servers happy, batching would make sense...
Anybody else hear about this?
G.B. Says
And remember, talking dogs are liars.