Great, thank you. Is this procedure still the "best" way to update firmware?
Sameer Prabhakar - Mad Ramblings: Samsung I5700 (Galaxy SPICA) Android 2.1 Flashing Guide (Updated)
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
2.1 Official Update is here in Canada.
- Thread starter soorkedy
- Start date
-
- Tags
- samsung galaxy spica
Great, thank you. Is this procedure still the "best" way to update firmware?
Sameer Prabhakar - Mad Ramblings: Samsung I5700 (Galaxy SPICA) Android 2.1 Flashing Guide (Updated)
Beerkan
Android Enthusiast
Those instructions seem ok.. if a little dated (Fed 10). But Odin method is the way to go.
The most important instruction when using Odin is..
[ ] One Package (not ticked)
[x] Reboot (ticked)
[x] Protect OPS (ticked)
[x] Reset Time (ticked) 300
[ ] Debug (not ticked)
Fail to tick this and you could FUBAR your phone for good...
The most important instruction when using Odin is..
[ ] One Package (not ticked)
[x] Reboot (ticked)
[x] Protect OPS (ticked)
[x] Reset Time (ticked) 300
[ ] Debug (not ticked)
Fail to tick this and you could FUBAR your phone for good...
Thanks very much for the advice. After a few false starts I managed to get the firmware updated with Odin. I had to use a new .ops file from the firmwares site to do so (the one included with Odin did not work).
I am now running baseband version i570EXXJD1, build number ECLAIR.XXJE4. It is much faster than the firmware I was using previously.
GPS is still very wonky / slow, though, and I still can't unlock my phone by any of the normal methods. Will have to keep reading.
At this point, do I have much to gain in terms of extending battery life / speeding up the phone by rooting it?
I am now running baseband version i570EXXJD1, build number ECLAIR.XXJE4. It is much faster than the firmware I was using previously.
GPS is still very wonky / slow, though, and I still can't unlock my phone by any of the normal methods. Will have to keep reading.
At this point, do I have much to gain in terms of extending battery life / speeding up the phone by rooting it?
Firmware version: 2.1-update1
BaseBand version: I5700XJF5
Kernel version: 2.6.29 root@sep-36 #2
Build No.: ECLAIR.UXJ5
smoke_weed
Newbie
how do you root this firmwarE?
dragoshell
Lurker
Using New PC Studio, the update gets stuck at step 3(installing the upgrade). It shows 0% and does not continue, and the phone only displays a white samsung logo on black background.
What should I do? It's been like this for an hour and the percentage does not increase. Is it safe to disconnect it and retry?
PS: the phone has been set in the "USB Debugging" mode, because it wasn't seen by the software otherwise.
-------------
UPDATE: I disconnected the phone, removed the battery, restarted the phone, only that now the update software says that it cannot connect to the server. I will try again though
What should I do? It's been like this for an hour and the percentage does not increase. Is it safe to disconnect it and retry?
PS: the phone has been set in the "USB Debugging" mode, because it wasn't seen by the software otherwise.
-------------
UPDATE: I disconnected the phone, removed the battery, restarted the phone, only that now the update software says that it cannot connect to the server. I will try again though
I upgraded my rogers spica via NPS last month. For a while I was stumped where you are, dragoshell.
I found that when NPS became stalled at 0% of the download to phone phase, it was safe to simply unplug the phone, shut it down by removing the battery, and then start it back up again. I found that after doing this my phone booted up exactly as I'd left it including settings and messaging conversations. Obviously I won't promise that if you do what I did you won't brick your device, but I definitely went through that process at least 3 times. It seemed like when NPS crashed at 0% of "downloading to phone", all that the phone had received before the crash was an instruction to await a file transfer, ie it stalled out before the phone tried to actually install anything.
It seems like most people succeed from this point by letting the update crash and using the emergency recovery procedure in NPS. If you're not running a 64 bit OS you should just disconnect the phone at this point, remove the battery, boot it into download mode, reconnect it and let NPS do its emergency recovery. Just be aware that NPS's instructions for putting your spica into download mode are completely wrong. I can't remember the key combo to use but I know NPS will give you a very clear colour diagram of which buttons to hold except they're the wrong ones.
For my part, I'm running Windows 7 64 bit. I was able to put the phone in download mode while unplugged and then attempted to start NPS' emergency recovery, but I wasn't able to actually install the firmware this way. The reason seemed to be that while the phone is in download mode, the USB Debugging flag is not active, which is a problem because Samsung's drivers for non-debugging mode install as seperate device. Some sort of device component umbrella is missing and plug-and-play was telling NPS that yes, I had attatched a samsung device, but no, I had not reconnected the phone it was just interacting with. Consequently NPS couldn't do it's emergency thing.
Unfortunately, as far as I could discover it isn't possible to boot the phone into download mode without disconnecting the USB cable AND powering off the phone. If there's a way to get into download mode without plug-and-play telling NPS you disconnected the spica, that'd probably get you past this, but I couldn't find a way.
I'm pretty sure my download-mode-recognition issue was tied to my OS. The 32 bit drivers straight up didn't work at all, and the 64 bit drivers I found I don't think officially exist. Someone on this forum posted a megaupload link for them, I think they found them on the german(?) version of Samsung's website. It seems like every translation of their website links to different files and conflicting info... I doubt this suprises anyone.
I did a lot of screwing around before I had success, so I can't give an ironclad process, but as best as I can remember this was the sequence that ultimately did the trick. Some steps may be superfluous, I really am not sure.
1) open device manager, plug in your phone, and note which entries in device manager pop up (you should see several devices become attatched, check modems, usb devices, and storage mediums). Uninstall all of them. If windows then detects an unknown device, do not allow the driver installation to proceed; ignore the dialogue boxes until everything's uninstalled, then unplug the phone and cancel out of them. Do not reconnect your phone yet.
2) open add/remove programs, and uninstall everything published by Samsung. Additionally, look for any Nokia software or drivers... believe it or not these are part of Samsung's software package. If you actually have a Nokia phone, just reinstall it later... last I checked their software works normally.
3) reboot. Run a registry cleanup (I use ccleaner, always back up your .reg file) and delete any keys without associations, then reboot again. Samsung's software doesn't even uninstall itself properly, it will leave behind a ton of stuff and then find it again when you reinstall, unless you do this step.
4) download Kies from Samsung. Install it, then use it's self updater for both the software package. Uncheck every option that makes Kies do anything at all during startup. To be sure, go to start->run->msconfig, open the startup tab, and uncheck everything that might have to do with Samsung. Then close Kies *all the way*... double check the task tray, then end Kies and Samsung processes from task manager. Stopping a Kies component often starts a different one so check twice. Apparently it wants to have a process running at all times which opens Kies for you when you manually open Kies. I don't know man.
5) open add/remove programs and uninstall the Samsung driver suite ONLY. Leave Kies alone. If the Nokia package is there leave it alone too. Then reboot.
6) Run the installer for the 64 bit spica drivers. Search this forum for them, I have lost the thread they were in. Afterwards reboot again.
7) Uncheck USB debugging mode on your phone. Attatch your spica to the USB cable and let the plug and play driver installation take place. Then unplug the phone, re-check USB debugging, plug it back in, and allow that driver to install as well. Then unplug the phone.
8) Start Kies, then plug the phone back in. Kies should identify it as something other than removeable storage media, but it may not yet show a model number. From the Kies menu, do the update mobile device driver thing, allow it to download a driver from Samsung and reinstall the phone to the computer. When this is done, disconnect the phone, un-check USB debugging, plug it back in and do the same thing again. (I don't believe this entirely replaces the 64 bit driver files you already installed, but I do think it replaces some of them. This is what I did, you can try not doing it.) Then Disconnect the phone, check USB debugging once more, and reboot your PC.
9) Open task manager and ensure Kies hasn't started any processes on the sly. Then download and install New PC Studio. Allow NPS to update itself. Then reboot one more time, close NPS and its sleeper versions, and make a final check in task manager for anything related to Kies, Samsung, or mobile device connection monitering. Stop anything you find.
10) Power down your phone, remove the SIM card and the SD card, then start it back up. In settings, find and check the boxes for "allow non-Market applications", "allow mock locations", and "stay awake". Be sure you're in USB debugging mode.
11) On your PC, navigate to the installation folder for NPS. Right click on the main executeable, click properties, open the compatability tab, and check the box for "run this program as an administrator". Apply that setting for all users. Granting 1-shot priviledges as you start the software doesn't seem to work, I think because during the firmware update NPS opens a new process without offering you the chance to grant adminitrator priviledges, then promptly fails due to being blocked by the OS.
12) Start NPS, and wait for it to load fully. Plug in your phone and wait again... NPS will probably detect a generic device right away, but after a little bit should identify it as a Galaxy Spica i5700.
13) Without unplugging your phone or closing NPS, deactivate USB Debugging mode on your spica. Wait for NPS to figure itself out. IIRC it will conclude that you have attatched a Samsung USB Modem, though all I remember for sure is it won't know it's an i5700. Once NPS is all caught up, unplug the phone, reactivate USB Debugging, plug it in once more, and wait for NPS to remember what it is.
14) Use the firmware update option in NPS. If I've remembered everything correctly, it should handle itself from here barring a few clicks of OK.
DISCLAIMER: the firmware I got by doing this appears to be a memory hog. It works great for everything except actual phonecalls, during which it crashes a ton. I've installed a bare minimum of anything, gone down to 2 home screens, and do use a task killer... it's still probably my fault, but expect issues if you like to run shmancy resource hogs. I've only seen it happen during calls and it seems to happen fastest when I've left the browser open.
Anyone that gets through with this, let me know.
I found that when NPS became stalled at 0% of the download to phone phase, it was safe to simply unplug the phone, shut it down by removing the battery, and then start it back up again. I found that after doing this my phone booted up exactly as I'd left it including settings and messaging conversations. Obviously I won't promise that if you do what I did you won't brick your device, but I definitely went through that process at least 3 times. It seemed like when NPS crashed at 0% of "downloading to phone", all that the phone had received before the crash was an instruction to await a file transfer, ie it stalled out before the phone tried to actually install anything.
It seems like most people succeed from this point by letting the update crash and using the emergency recovery procedure in NPS. If you're not running a 64 bit OS you should just disconnect the phone at this point, remove the battery, boot it into download mode, reconnect it and let NPS do its emergency recovery. Just be aware that NPS's instructions for putting your spica into download mode are completely wrong. I can't remember the key combo to use but I know NPS will give you a very clear colour diagram of which buttons to hold except they're the wrong ones.
For my part, I'm running Windows 7 64 bit. I was able to put the phone in download mode while unplugged and then attempted to start NPS' emergency recovery, but I wasn't able to actually install the firmware this way. The reason seemed to be that while the phone is in download mode, the USB Debugging flag is not active, which is a problem because Samsung's drivers for non-debugging mode install as seperate device. Some sort of device component umbrella is missing and plug-and-play was telling NPS that yes, I had attatched a samsung device, but no, I had not reconnected the phone it was just interacting with. Consequently NPS couldn't do it's emergency thing.
Unfortunately, as far as I could discover it isn't possible to boot the phone into download mode without disconnecting the USB cable AND powering off the phone. If there's a way to get into download mode without plug-and-play telling NPS you disconnected the spica, that'd probably get you past this, but I couldn't find a way.
I'm pretty sure my download-mode-recognition issue was tied to my OS. The 32 bit drivers straight up didn't work at all, and the 64 bit drivers I found I don't think officially exist. Someone on this forum posted a megaupload link for them, I think they found them on the german(?) version of Samsung's website. It seems like every translation of their website links to different files and conflicting info... I doubt this suprises anyone.
I did a lot of screwing around before I had success, so I can't give an ironclad process, but as best as I can remember this was the sequence that ultimately did the trick. Some steps may be superfluous, I really am not sure.
1) open device manager, plug in your phone, and note which entries in device manager pop up (you should see several devices become attatched, check modems, usb devices, and storage mediums). Uninstall all of them. If windows then detects an unknown device, do not allow the driver installation to proceed; ignore the dialogue boxes until everything's uninstalled, then unplug the phone and cancel out of them. Do not reconnect your phone yet.
2) open add/remove programs, and uninstall everything published by Samsung. Additionally, look for any Nokia software or drivers... believe it or not these are part of Samsung's software package. If you actually have a Nokia phone, just reinstall it later... last I checked their software works normally.
3) reboot. Run a registry cleanup (I use ccleaner, always back up your .reg file) and delete any keys without associations, then reboot again. Samsung's software doesn't even uninstall itself properly, it will leave behind a ton of stuff and then find it again when you reinstall, unless you do this step.
4) download Kies from Samsung. Install it, then use it's self updater for both the software package. Uncheck every option that makes Kies do anything at all during startup. To be sure, go to start->run->msconfig, open the startup tab, and uncheck everything that might have to do with Samsung. Then close Kies *all the way*... double check the task tray, then end Kies and Samsung processes from task manager. Stopping a Kies component often starts a different one so check twice. Apparently it wants to have a process running at all times which opens Kies for you when you manually open Kies. I don't know man.
5) open add/remove programs and uninstall the Samsung driver suite ONLY. Leave Kies alone. If the Nokia package is there leave it alone too. Then reboot.
6) Run the installer for the 64 bit spica drivers. Search this forum for them, I have lost the thread they were in. Afterwards reboot again.
7) Uncheck USB debugging mode on your phone. Attatch your spica to the USB cable and let the plug and play driver installation take place. Then unplug the phone, re-check USB debugging, plug it back in, and allow that driver to install as well. Then unplug the phone.
8) Start Kies, then plug the phone back in. Kies should identify it as something other than removeable storage media, but it may not yet show a model number. From the Kies menu, do the update mobile device driver thing, allow it to download a driver from Samsung and reinstall the phone to the computer. When this is done, disconnect the phone, un-check USB debugging, plug it back in and do the same thing again. (I don't believe this entirely replaces the 64 bit driver files you already installed, but I do think it replaces some of them. This is what I did, you can try not doing it.) Then Disconnect the phone, check USB debugging once more, and reboot your PC.
9) Open task manager and ensure Kies hasn't started any processes on the sly. Then download and install New PC Studio. Allow NPS to update itself. Then reboot one more time, close NPS and its sleeper versions, and make a final check in task manager for anything related to Kies, Samsung, or mobile device connection monitering. Stop anything you find.
10) Power down your phone, remove the SIM card and the SD card, then start it back up. In settings, find and check the boxes for "allow non-Market applications", "allow mock locations", and "stay awake". Be sure you're in USB debugging mode.
11) On your PC, navigate to the installation folder for NPS. Right click on the main executeable, click properties, open the compatability tab, and check the box for "run this program as an administrator". Apply that setting for all users. Granting 1-shot priviledges as you start the software doesn't seem to work, I think because during the firmware update NPS opens a new process without offering you the chance to grant adminitrator priviledges, then promptly fails due to being blocked by the OS.
12) Start NPS, and wait for it to load fully. Plug in your phone and wait again... NPS will probably detect a generic device right away, but after a little bit should identify it as a Galaxy Spica i5700.
13) Without unplugging your phone or closing NPS, deactivate USB Debugging mode on your spica. Wait for NPS to figure itself out. IIRC it will conclude that you have attatched a Samsung USB Modem, though all I remember for sure is it won't know it's an i5700. Once NPS is all caught up, unplug the phone, reactivate USB Debugging, plug it in once more, and wait for NPS to remember what it is.
14) Use the firmware update option in NPS. If I've remembered everything correctly, it should handle itself from here barring a few clicks of OK.
DISCLAIMER: the firmware I got by doing this appears to be a memory hog. It works great for everything except actual phonecalls, during which it crashes a ton. I've installed a bare minimum of anything, gone down to 2 home screens, and do use a task killer... it's still probably my fault, but expect issues if you like to run shmancy resource hogs. I've only seen it happen during calls and it seems to happen fastest when I've left the browser open.
Anyone that gets through with this, let me know.
dudemanguybro
Newbie
Is there a guide somewhere to update my phone? I'm in Canada on Rogers running the stock OS version 1.5
I'v tried connecting my phone to studio 7 and it wont detect my phone. I'v been trying to find a way to upgrade for a couple hours now and nothing seems to be working for me
Any help would be great!
I'v tried connecting my phone to studio 7 and it wont detect my phone. I'v been trying to find a way to upgrade for a couple hours now and nothing seems to be working for me
Any help would be great!
Download the NPS - New PC sudio from samsung website
IN your phone settings , goto SD card & phone storage settings and UNCHECK Mass storage only
It should get the NPS to recognize your phone and you will be able to upgrade it
You should UNLUG any USB device connecting to your computer other than the Phone itself .. i suggest using a laptop for this
dudemanguybro
Newbie
I cant even install NPS. When i click it it says "Error reading initialization file". I'v tried downloading it multiple times and even older versions from other sites come up with the same error....UGH!
Is there any info or links to guides for this? Iv spent the majority of my evening trying to update, and nothing seems to work. I am on windows XP so i dunno if the new NPS dosnt work on it or not or what...
Is there any info or links to guides for this? Iv spent the majority of my evening trying to update, and nothing seems to work. I am on windows XP so i dunno if the new NPS dosnt work on it or not or what...
"Error reading initialization file"? From multiple different versions of the installer? Sounds like that might be your PC, mate. However, if the installshield process gets through the extracting data to install phase before crapping out, you can always try finding the temp folder it dumped everything in and copy/pasting it all somewhere else while it waits for you to accept the EULA. That should at least net you the installer for the phone drivers.
Try downloading a version of NPS from the UK site Samsung Mobile UK - Home
If you get NPS going, it seems less inclined to insist that your phone is a generic mass storage media if you take the SD card out.
If it complains that NPS doesn't support GT-i5700R and tells you to use Kies, click update phone anyway. It seems willing to flash your phone as long as it can see it, even if its picture viewer can't load your gallery (finally something reasonable), and the new rogers firmware is available through NPS.
Try downloading a version of NPS from the UK site Samsung Mobile UK - Home
If you get NPS going, it seems less inclined to insist that your phone is a generic mass storage media if you take the SD card out.
If it complains that NPS doesn't support GT-i5700R and tells you to use Kies, click update phone anyway. It seems willing to flash your phone as long as it can see it, even if its picture viewer can't load your gallery (finally something reasonable), and the new rogers firmware is available through NPS.
dudemanguybro
Newbie
Im trying that right now but the uk NPS is aperently going to take 4 hours for me to download since it wont seem to go faster than 9kbps. Even the other ones took hours to d/l... I really cant believe how hard this is turning out to be.
dudemanguybro
Newbie
I got NPS installed and running, and i got it to recognize my phone.
I initiated the upgrade on my phone but it seems to have frozen halfway through the instalation of stage 3 at 55%...I cant seem to cancle the install or close NPS and im afraid to disconnect my phone but im eventually going to have to because its not doing anything.
What should i do?
Edit**
I ended up calling Roger's, who say they know nothing about the upgrade at all and that there is no upgrade and to call samsung cocerning this issue. I called samsung and they basicly told me the exact same thing, and to call rogers. I disconnected my phone an now it wont fully boot up. It just sits at a screen with a picture of a phone connected to a PC with hazard sign between....is there any way to completely reset my phone???
I initiated the upgrade on my phone but it seems to have frozen halfway through the instalation of stage 3 at 55%...I cant seem to cancle the install or close NPS and im afraid to disconnect my phone but im eventually going to have to because its not doing anything.
What should i do?
Edit**
I ended up calling Roger's, who say they know nothing about the upgrade at all and that there is no upgrade and to call samsung cocerning this issue. I called samsung and they basicly told me the exact same thing, and to call rogers. I disconnected my phone an now it wont fully boot up. It just sits at a screen with a picture of a phone connected to a PC with hazard sign between....is there any way to completely reset my phone???
*Centurion
Newbie
To fix your phone you will have to put it in download mode and flash the firmware with Odin now.
dudemanguybro
Newbie
Lol... I dont know anything about Odin. Will doing this void my warrenty on my phone?
And i hate to ask are there any links to any guides/info on this?
I know its prob on here but iv already spent the entire day searching for info to upgrade, and now fix my phone...i feel like im turning green with rage and frustration! argh!
And i hate to ask are there any links to any guides/info on this?
I know its prob on here but iv already spent the entire day searching for info to upgrade, and now fix my phone...i feel like im turning green with rage and frustration! argh!
Flashing your phone with odin isn't for everyone, if you don't know then don't do it, i did not flash my phone with odin yet, you have been doing it through NPS, you will be fine.
i think i have a solution for you to fix your problem.
PLUG your phone into a computer, or yours, then power your phone on with the usb plug in
tell me what happens
dudemanguybro
Newbie
It loads up the typical Samsung loading bar as it does when you normally boot it up, cept it dosnt load up at all.
I cant get it into recovery mode, NPS wont detect it to do a "Emergancy restore", if i try to upgrade it again it fails.
After spending the past 4 days dealing with "rogers customer service" i guess they are sending me a new phone. Wich is great. But, im worried if i try to update my phone again it will just mess it up again :/
Crash27
Android Enthusiast
Can someone please send me the info on how to update my Spica to 2.1, I have been searching for days for the proper way to do it and I am going crazy, LOL, I am on Rogers and I have tried several PC studio versions and all will not show the phone under Upgrade, I am running Win 7 -64bit not sure if I need to be doing it on a XP computer but I could use some help please.
Thanks
Thanks
*Centurion
Newbie
This is a tutorial thats up to date
http://androidforums.com/samsung-galaxy-spica/124299-root-me-baby-one-more-time.html#post1157246
dudemanguybro
Newbie
I just wanted to post, iv spent the past two weeks calling rogers, talking to multiple representatives in-store, on the phone, and pretty much every "customer service/help" site provided by them from forums, twitter, facebook, email...
And there is no update. Everyone i have talked to has no info on this update. Half the people dont even know what phone im talking about (the spica is no longer even on the roger's webpage)... Roger's has to be the worst company iv ever had to deal with for customer service.
And there is no update. Everyone i have talked to has no info on this update. Half the people dont even know what phone im talking about (the spica is no longer even on the roger's webpage)... Roger's has to be the worst company iv ever had to deal with for customer service.
dudemanguybro
Newbie
Performance you deserve - Samsung Galaxy Spica? (GT-I5700) - All Phones - Mobile Phones | SAMSUNG
I'm a canadian user on Rogers and have been waiting for a working official upgrade for a while now.
I'm not sure if this works but its on the samsung site so im assuming its official and will work. I will probably try it later tonight.
I tried once to update through NPS but ended up bricking my phone, my phone just stopped loading on the install screen and wouldnt go into recovery mode. After dealing with "rogers customer service" for 3 days they sent me a new phone.
I'm just wondering if anyone can confirm this works because i really dont want to have to go through the proccess of dealing with the people at rogers again since no one on their side knows anything about this update and most people i talked to dont even know what the spica is and constantly try to correct me saying "the galaxy S isnt even available yet, sir" or better yet, "are you talking about the new iphone 4?"
Any feedback would be great and thanks!
I'm a canadian user on Rogers and have been waiting for a working official upgrade for a while now.
I'm not sure if this works but its on the samsung site so im assuming its official and will work. I will probably try it later tonight.
I tried once to update through NPS but ended up bricking my phone, my phone just stopped loading on the install screen and wouldnt go into recovery mode. After dealing with "rogers customer service" for 3 days they sent me a new phone.
I'm just wondering if anyone can confirm this works because i really dont want to have to go through the proccess of dealing with the people at rogers again since no one on their side knows anything about this update and most people i talked to dont even know what the spica is and constantly try to correct me saying "the galaxy S isnt even available yet, sir" or better yet, "are you talking about the new iphone 4?"
Any feedback would be great and thanks!
dragoshell
Lurker
After having the phone resetting its settings to factory ones due to messing with the unlock pattern, I tried again to update using the New PC Suite. This time it worked flawlessly, and was very fast!
The only thing that can be noticed after the update is that the phone is a little less responsive (somewhat noticeable), and that it looks better. I hope the phone got rid of the SMS bug (not receiving messages after a while and needed software reset) and that the battery life at least was not affected, but I'll see about that.
The only thing that can be noticed after the update is that the phone is a little less responsive (somewhat noticeable), and that it looks better. I hope the phone got rid of the SMS bug (not receiving messages after a while and needed software reset) and that the battery life at least was not affected, but I'll see about that.
RadioFrogZombie
Lurker
Sorry if this is the wrong place to ask about this, but I might as well try.
I have been using a Samsung Kies Mini to attempt to get the 2.1 upgrade. It goes pretty well for a while, but before it has finished installation, a bubble on my computer will suddenly say that my USB is not recognized! Then the Android screen goes black, except for saying Samsung, and I have to take out the battery and put it back in again to work!
I did everything right. I have it on Mass Storage to first detect the USB, and then when it is connected I turn off the Mass Storage. I can not understand why this is happening!
Does it have to do with the Kies Mini or what? I'm also using Microsoft ActiveSync, if that helps. Any advice would be helpful.
I have been using a Samsung Kies Mini to attempt to get the 2.1 upgrade. It goes pretty well for a while, but before it has finished installation, a bubble on my computer will suddenly say that my USB is not recognized! Then the Android screen goes black, except for saying Samsung, and I have to take out the battery and put it back in again to work!
I did everything right. I have it on Mass Storage to first detect the USB, and then when it is connected I turn off the Mass Storage. I can not understand why this is happening!
Does it have to do with the Kies Mini or what? I'm also using Microsoft ActiveSync, if that helps. Any advice would be helpful.