[Q] Samsung Kies "Device not Supported" error - Captivate General

I plugged my phone up to KIES yesterday, to find that there was an update available. I'm not sure what update it was, but I'm almost certain it was a phone upgrade, possibly 2.2. KIES began downloading the update, and did so successfully. However, after doing the download, and upon starting the next step, my phone was no longer visible. I got the "searching for device" which stay like that forever. So, I closed down KIES, restarted my computer, and the phone. Once I did this, and went started KIES up again, I now recieved a "Device not supported" error. For this reason, I think it may have been a KIES update. However, I"m not sure what kind of update it was. I did a system restore to about 2 weeks ago, and it says I have KIES version 1.5.2.10093. I tried plugging my phone up again, and at first it went to "Searching for device" but after a few seconds said, "Device not supported."
Phone INFO:
Model Number: SAMSUNG-SGH-I897
Firmware version: 2.1-update1
Baseband version: I897UCJH7
Kernel version: 2.6.29
jeteak.lee sep-11 #2
Build Number: ECLAIR.UCJH7
Is anyone else having this issue, or is there a known issue to counter this?
Thanks for you help.

I'm having this issue also. I'm using the latest build of cognition w/ a restored ID. My KIES would recognize the device until I just updated the KIES program a few minutes ago.

Okay, so it must be Kies then... i read in another forum that someone believed Samsung altered the program so that US residents couldn't update to 2.2 early.... someone also said they installed an earlier version of KIES after installing the new update, and Kies was once again able to "support" the device... Any ways around doing this, or is it a known issue?
Sent from my SAMSUNG-SGH-I897 using XDA App

Yea I'd like to revert back to the previous build.

Maybe a Reg Hack for the new ver of Kies would allow it to support the device. Anybody familiar with what might do that?

So after some more digging... i found an interesting thing. When I connect my phone in media mode and/or mass storage mode, KIES recognized my phone... however, once my interest to to KIES mode, same old "device not supported"... however, you can't do anything in the other two modes. Someone else posted that Samsung had told them Kies won't recognize the device until 2.2...
Sent from my SAMSUNG-SGH-I897 using XDA App

Uploading an older installer now, will edit and post a URL when it's done.
Edit to add: Here it is.
I hope this helps.

A thread about this was already ongoing. Also a upload of the older version of kies in that tread.
http://forum.xda-developers.com/showthread.php?t=830194

veive said:
Uploading an older installer now, will edit and post a URL when it's done.
Edit to add: Here it is.
I hope this helps.
Click to expand...
Click to collapse
thanks! much appreciated

Related

Device Driver Help

I'm new to this forum and new to android... I have Win 7 64-bit and I can't seem to get the usb drivers to install for my Captivate. Please help!
Intel i7 Processor
I am a new user and cant post links yet but head over to the android forums>captivate and its one of the 4 stickies with links for drivers
Netstalker2009 said:
I'm new to this forum and new to android... I have Win 7 64-bit and I can't seem to get the usb drivers to install for my Captivate. Please help!
Intel i7 Processor
Click to expand...
Click to collapse
I got it from here.
http://www.samsung.com/us/consumer/...ATT/index.idx?pagetype=prd_detail&tab=support
Under the downloads section, there is Manuals and Software. click software and download it form there!
madjsp said:
I got it from here.
http://www.samsung.com/us/consumer/...ATT/index.idx?pagetype=prd_detail&tab=support
Under the downloads section, there is Manuals and Software. click software and download it form there!
Click to expand...
Click to collapse
My goodness. I installed SAMSUNG Kies(kies_win.exe) 2.0.3.11082_152_4 30-Sep-2011 82.5MB
just to get the Windows 7 phone drivers.
My firewall/HIPS needed to authorize about 30 things the install process wanted to do. I have NEVER had an install need so many grants --never. Also, I have a fairly fast computer, and it was the longest install, time-wise, I have ever seen on this machine. This program better make my morning coffee after all that.
Can KIES be uninstalled and leave the drivers in place?
Don't know. Doesn't hurt to keep it around, just in case you need to reinstall drivers again. Did you get kies or mini kies?
mrhaley30705 said:
Don't know. Doesn't hurt to keep it around, just in case you need to reinstall drivers again. Did you get kies or mini kies?
Click to expand...
Click to collapse
Full. The other thread I was reading said you needed the full version to ensure the Windows 7 drivers would work. All I want is the drivers.
Does KIES run as an all-time service and speak to Samsung every time you plug in your phone (Captivate)? If so, I have to find and disable the service, or remove it--but I want to keep the drivers is the problem. Does uninstalling it leave the drivers there?
I also have Win7 x64 running in my computer. I do NOT have Kies installed on my computer and I have only the drivers installed. There is no reason to even have Kies unless you're just a typical end user upgrading to a stock firmware.
On my old computer with Kies, I never remember seeing Kies call home to anything other then the software update server to check for updated Kies versions. All the firewall and traffic logs were clean. (Except for the update check)
Sent from my Captivate
The only reason to haves full kies is the drivers. Officially, the I897 isn't supported by KIES. If you try to connect your phone, it plainly says"device not supported".
let me repeat...in a different thread, many people were reporting that they were not able to "see" the phone sd as a folder when on Windows 7 64bit machines.
Someone else there reported that installing latest full 64 KIES allowed it to work. THAT is why I went to full KIES.
I now have further info... the phone USB connection did work with KIES installed, but after seeing the monster that full KIES was, I uninstalled it. USB connection still worked. End of my issue--which might not have been an issue anyway, as I did not try installing driver-package-only since others were reporting problems with Windows 7 64 doing that. Whew.
---------- Post added at 08:53 PM ---------- Previous post was at 08:43 PM ----------
mrhaley30705 said:
The only reason to haves full kies is the drivers. Officially, the I897 isn't supported by KIES. If you try to connect your phone, it plainly says"device not supported".
Click to expand...
Click to collapse
Interesting, as I got drilled to the KIES dl package at the Samsung site by selecting my I897 phone model in the page's field's popdowns. It is a very recent date, 30-Sep-2011, so maybe this version does work.
I cannot verify that either way as I did not run it with the phone--only installed it, verified drivers allowed USB connection, then uninstalled (due to size/intrusiveness as described before).
I wasn't aware that full kies could even be downloaded on the Samsung/USA site. When i've dl'd, I had to change my location to UK. Are you sure it's not mini kies?
mrhaley30705 said:
I wasn't aware that full kies could even be downloaded on the Samsung/USA site. When i've dl'd, I had to change my location to UK. Are you sure it's not mini kies?
Click to expand...
Click to collapse
I don't think 82 MB is mini !!
Got it here
http://www.samsungapps.com/about/onPc.as?COUNTRY_CODE=CAN&LANGUAGE_CODE=ENG
SAMSUNG Kies (kies_win.exe) 2.0.3.11082_152_4 30-Sep-2011 82.5MB
Now I see that a drill down at Samsung, starting here
http://www.samsung.com/us/support/#
leads you to this file
Win XP/Vista/Windows 7 Sep 27, 2010 SAMSUNG Kies, Others (Software) (ver.11011.4) 41.0
ENGLISH
which is different from what I got.
Now I don't know how I wound up on the other site, but, for me, it is a moot point as I have uninstalled it all--except the drivers apparently remained since the phone connects OK.

[Q] "Sorry I'm Having Trouble Communicating..."

So I've been trying to unlock my Samsung Focus with ChevronWP7. I have followed >>this<< guide, step by step, but after I click both boxes and click on "Unlock", I get "Sorry, I'm having trouble communicating with the phone. Please make sure it's connected using USB. Please start the Zune application." So then I tried another guide(can't find the link right now), which included disabling the network, using WPConnect.exe, etc, but that didn't work either. I am completely at a loss of why this damn error keeps popping up. I restarted both my PC and phone numerous times, I've tried different USB ports and cables, but nothing is working. Anyone have any tips?
My OS version is 7.0.7390.0, Firmware Revision is 2103.11.3.3 and Zune version is 4.7.1404.0 if that helps at all.
Thank you, maxx.
I had same problem and I used the guide below and it worked on the first try. Most importantly was STEP 2 for me. Uninstalling Zune and using the version from the link provided in the guide at step 2.
[Tutorial] Unlock your phone; prevent relock & prepare for updates!
Well damn, it says my firmware isn't compatible with CWP7. I guess that and my Zune version is why it doesn't work. Is it possible to revert back to a previous firmware version?
try to downgrade to previous version (if possible) from zune.
If your phone came with NoDo (7392 or 7390) installed the only way to unlock at the moment is to flash a previous firmware version. Check the forums if there is one for your provider and phone.
If i'm not wrong you can checkwith Ansar's rom.
Have you resolved the problem yet? It seems there is something wrong with the "hosts" file. Generally, this file is in folder "C:\windows\system32\drivers\etc". Open it, delete all lines like "192.168.1.101 developerservices.windowsphone.com". Then, save it, try ChevronWP7 again in admin permission, it should be OK. If still not works, please send email to me, [email protected].
maxxdout said:
So I've been trying to unlock my Samsung Focus with ChevronWP7. I have followed >>this<< guide, step by step, but after I click both boxes and click on "Unlock", I get "Sorry, I'm having trouble communicating with the phone. Please make sure it's connected using USB. Please start the Zune application." So then I tried another guide(can't find the link right now), which included disabling the network, using WPConnect.exe, etc, but that didn't work either. I am completely at a loss of why this damn error keeps popping up. I restarted both my PC and phone numerous times, I've tried different USB ports and cables, but nothing is working. Anyone have any tips?
My OS version is 7.0.7390.0, Firmware Revision is 2103.11.3.3 and Zune version is 4.7.1404.0 if that helps at all.
Thank you, maxx.
Click to expand...
Click to collapse
maxx,
Chevron WP7 DOES NOT work with 7390 and above. As you have found out, the only option is to downgrade the firmware to an older version and then unlocking it. I tried searching and was not able to find it ( or I did not know what the hell I was looking for, HTC HD7 user here )
If your Focus came with a older version and you updated using Zune, you can try restoring
Open Zune--> Settings-->Phone-->Updates-->Restore
Try posting in the Samsung Focus forum. You might get some help.Good luck...

[Q] Nexus S 4G - A Soft, Squishy, Brick.

Good day, XDA.
Recently, I became the proud owner of a Nexus S 4G, primarily because whomever had the phone prior to me had decided that flashing a GSM rom onto their Nexus S 4G would be a good idea. Needless to say, and as you can all probably guess, this did not benefit the functionality of this phone.
So lets start from the top, the phone is able to power on and boot up, it is running 2.3.6 stock. About phone reads the following:
Model Number: Nexus S
Android Version: 2.3.6
Baseband Version: Unknown
Kernel Version: 2.6.35.7-gf5f63ef [email protected] #1
Build Number: GRK39F
It has no SU binary. While powered up in this mode, it can charge VIA usb, but is unable to be seen by the computer with debugging mode on, or with debugging mode off. Neither option would seem to result in the phone being picked up by either Windows or Linux (Odd that it charges fine though. I did confirm this was not a "Charge Only" cable.)
Moving on, I can boot into fastboot, where I am presented with the following:
Product Name - Herring
HW Version - Rev 03 (JTAG)
Bootloader Version - I9020XXKA3
Baseband Version - I9020XXKF1
Carrier Info - SPR
Lock state - Unlocked.
At the bottom when booting into fastboot, it shows me "USB Control Init", followed immediately by "USB Control Init End". The computer does not see the device when plugged in here either. So no pushing fastboot or adb commands.
Booting into recovery, I am presented with Andy, standing next to a White triangle with a yellow exclaimation mark in it. After fiddling around with the power and volume buttons, I am eventually presented with a screen that states
"Android system recovery <3e>". Oh boy! Stock recovery. How lucky I am. It has the option to apply update from /sdcard, but these need to be signed; and it seems every update.zip file for the Nexus S 4G that I can find makes the assumption that you are on the previous android version, and will not flash if you are not.
So here is where I currently am. I can download zip files over wifi and attempt to push them out to the phone, but there is no PC connectivity, which seems to hinder my attempts at making it work a bit better. I will admit, I am new to the Nexus S (Having never used one before), and to the Samsung devices rooting community (Having been exclusively HTC prior to this). So I might be missing something; does anyone have any thoughts on where to go from here? Sorry for the long post.
SoberSquid said:
Good day, XDA.
Recently, I became the proud owner of a Nexus S 4G, primarily because whomever had the phone prior to me had decided that flashing a GSM rom onto their Nexus S 4G would be a good idea. Needless to say, and as you can all probably guess, this did not benefit the functionality of this phone.
So lets start from the top, the phone is able to power on and boot up, it is running 2.3.6 stock. About phone reads the following:
Model Number: Nexus S
Android Version: 2.3.6
Baseband Version: Unknown
Kernel Version: 2.6.35.7-gf5f63ef [email protected] #1
Build Number: GRK39F
It has no SU binary. While powered up in this mode, it can charge VIA usb, but is unable to be seen by the computer with debugging mode on, or with debugging mode off. Neither option would seem to result in the phone being picked up by either Windows or Linux (Odd that it charges fine though. I did confirm this was not a "Charge Only" cable.)
Moving on, I can boot into fastboot, where I am presented with the following:
Product Name - Herring
HW Version - Rev 03 (JTAG)
Bootloader Version - I9020XXKA3
Baseband Version - I9020XXKF1
Carrier Info - SPR
Lock state - Unlocked.
At the bottom when booting into fastboot, it shows me "USB Control Init", followed immediately by "USB Control Init End". The computer does not see the device when plugged in here either. So no pushing fastboot or adb commands.
Booting into recovery, I am presented with Andy, standing next to a White triangle with a yellow exclaimation mark in it. After fiddling around with the power and volume buttons, I am eventually presented with a screen that states
"Android system recovery <3e>". Oh boy! Stock recovery. How lucky I am. It has the option to apply update from /sdcard, but these need to be signed; and it seems every update.zip file for the Nexus S 4G that I can find makes the assumption that you are on the previous android version, and will not flash if you are not.
So here is where I currently am. I can download zip files over wifi and attempt to push them out to the phone, but there is no PC connectivity, which seems to hinder my attempts at making it work a bit better. I will admit, I am new to the Nexus S (Having never used one before), and to the Samsung devices rooting community (Having been exclusively HTC prior to this). So I might be missing something; does anyone have any thoughts on where to go from here? Sorry for the long post.
Click to expand...
Click to collapse
what model is your nexus s? i9020A i9023 ect..? the link below has a ton of stock roms for various nexus s versions and most are flashable via Stock Recovery
http://forum.xda-developers.com/showthread.php?t=1063664
It is the SPH-D720, my appologies for leaving that out. Unfortunately, it seems the D720 has the misfourtune of not having a fully flashable ROM listed on that page.
SoberSquid said:
It is the SPH-D720, my appologies for leaving that out. Unfortunately, it seems the D720 has the misfourtune of not having a fully flashable ROM listed on that page.
Click to expand...
Click to collapse
Its a shame it wont connect to adb because that's one of the few nexus s that has signed images flashable via fastboot.
Sent from my Nexus S using xda premium
Indeed. It is quite odd - It can boot into fastboot, download mode, etc just fine, but it isn't picking it up at all on the PC. I'm thinking it has to do something with the kernel-mode USB drivers, prehaps there are different drivers used for the CDMA and GSM varients? It is a bit frustrating because it would be a fairly simple fix if fastboot could pick it up.
SoberSquid said:
Indeed. It is quite odd - It can boot into fastboot, download mode, etc just fine, but it isn't picking it up at all on the PC. I'm thinking it has to do something with the kernel-mode USB drivers, prehaps there are different drivers used for the CDMA and GSM varients? It is a bit frustrating because it would be a fairly simple fix if fastboot could pick it up.
Click to expand...
Click to collapse
You might want to try reinstalling the drivers, I use an apple computer & they dont require those drivers so i cant be much help there. Here's another link to check out. Pete Alfonso makes roms from the Nexus S and has the original signed software images for the Nexus S 4g and some other stuff that might help you... http://download.peteralfonso.com/crespo4g
Hmm, looking at his site, he has quite a lot of good stuff, most of it requires a non-stock recovery though. The Nexus S 4G (When it came out), was running 2.3.4, in contrast to the normal Nexus S. I wonder, Since my phone is currently reading on a GSM rom/radio, could I flash the phone to 2.3.3 (Android 2.3.3/GRI40/XXKB1 Radio/KA3 Bootloader), use gingerbreak to gain SU, install CWM, and possibly flash back to a proper baseband and rom from there? Or is that really looking at mucking things up?
SoberSquid said:
Hmm, looking at his site, he has quite a lot of good stuff, most of it requires a non-stock recovery though. The Nexus S 4G (When it came out), was running 2.3.4, in contrast to the normal Nexus S. I wonder, Since my phone is currently reading on a GSM rom/radio, could I flash the phone to 2.3.3 (Android 2.3.3/GRI40/XXKB1 Radio/KA3 Bootloader), use gingerbreak to gain SU, install CWM, and possibly flash back to a proper baseband and rom from there? Or is that really looking at mucking things up?
Click to expand...
Click to collapse
I wouldnt flash any rom with a bootloader not made for your phone.
---------- Post added at 01:22 PM ---------- Previous post was at 01:18 PM ----------
scott8281 said:
I wouldnt flash any rom with a bootloader not made for your phone.
Click to expand...
Click to collapse
you might try this flashable update... Look down towards the bottom of the page... they are flashable via stock recovery.... http://forum.xda-developers.com/showthread.php?t=1063664 D720:
Android 2.3.4 (Build GRJ06D/PRKC9 Radio/KC5 Bootloader)
2.3.4 (GRJ06D) -> 2.3.4 (GRJ22)
2.3.4 (GRJ06D) -> 2.3.5
2.3.4 (GRJ06D) -> 2.3.7
Android 2.3.4 (Build GRJ22/PRKD8 Radio/KC5 Bootloader)
2.3.4 (GRJ22) -> 2.3.5
2.3.4 (GRJ22) -> 2.3.7
Android 2.3.5 (Build GRJ90/PRKE5 Radio/KC5 Bootloader)
2.3.5 -> 2.3.7
Tried all 3 of those, they state the following:
-- Install /sdcard/Download ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
I believe all 3 of those are expecting you to be on the prior android version, and when it sees that you are not, it fails.
SoberSquid said:
Tried all 3 of those, they state the following:
-- Install /sdcard/Download ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
I believe all 3 of those are expecting you to be on the prior android version, and when it sees that you are not, it fails.
Click to expand...
Click to collapse
Well crap! im officially out of ideas... Best of luck to you, Im certain that with your phone able to boot into bootloader that its fixable
Ahh, well thanks anyway for trying to assist! Anyone else have ideas on how to fix this, or anyone else experience this before?
Assuming I cannot recover this, as it is slowly looking fairly unrecoverable, does anyone have a recommended JTAG service (Preferably in the US)? I'm not aware of any around my area. I did see a few online, but I'm unsure as to how trustworthy any of them are...
Did you try the roms listed here?
http://forum.xda-developers.com/showthread.php?t=1078213
Hmm. Without fastboot its tough to flash a rom, Did you try the factory data reset option in your settings, IS it showing error?
you're lucky i just did this last week.
seems that jerk flashed a gsm radio to that phone.
what you'll need to do is ODIN the phone to flash the CDMA radios back. you can find that HERE just follow the steps in that program and then you should be booting 2.3.4.
from there take the updates from sprint to get back to 2.3.7.
something about flashing a gsm radio hosed the MEID of my new phone, so keep that in mind. you may need to repair it afterwards before you can use it on sprint.
if you need help get back with me but that program should do the trick for you.
saranyan said:
Did you try the roms listed here?
http://forum.xda-developers.com/showthread.php?t=1078213
Hmm. Without fastboot its tough to flash a rom, Did you try the factory data reset option in your settings, IS it showing error?
Click to expand...
Click to collapse
Tried those; those were the ones listed on Peter Alfonso's Site (Who I assume is BuglessPete? Like I said, I'm new in this section ). Unfortunately the Odex/Deodex require signature verification to be off, and the other updates are only partial updates, so they make the presumption you are on the prior Android revision, and promptly fail signature verification if you are not, so yeah unfortunately none of those had worked :/
thedudejdog said:
you're lucky i just did this last week.
seems that jerk flashed a gsm radio to that phone.
what you'll need to do is ODIN the phone to flash the CDMA radios back. you can find that HERE just follow the steps in that program and then you should be booting 2.3.4.
from there take the updates from sprint to get back to 2.3.7.
something about flashing a gsm radio hosed the MEID of my new phone, so keep that in mind. you may need to repair it afterwards before you can use it on sprint.
if you need help get back with me but that program should do the trick for you.
Click to expand...
Click to collapse
Thanks much - I downloaded the program, ran setup.exe, installed all of it (Wow, this looks familiar from way back when I had a Samsung Moment, lol.). Threw the phone into download mode and waited. Unfortunately, it went downhill from here - It just sits there stating "Detect Port...", and shows disconnected. In Windows, under device manager, I went to view>devices by connection, then expanded out to my USB Port Hub. I don't show any devices there. So it seems that my phone is simply not being picked up by my computer - I did verify the USB cable I had was a data cable, and not a charge-only cable. And while hard to see them, the pin connectors in the charging port on the phone look good.
When I go into download mode (Or fastboot, for that matter), it shows the following on the screen, which I think is part of the cause of this issue:
"USB Control Init"
"USB Control Init End"
These happen right after one another. I'm not really sure why the USB controller wouldn't be working in this case, but I think whomever had the phone before me (in an attempt to fix an issue), decided to restore this phone back to stock using the I9020T files. I believe the Nexus S GSM variant may have a different USB controller in it, which is causing the drivers to malfunction on the CDMA variant, but I could be wrong. I haven't seem something like this occur before, lol.
Here are some fancy photos:
Download mode (Plus the error message given):
http://i.imgur.com/T4wOE.jpg
USB Port:
http://i.imgur.com/COAhb.jpg
Its an odd error, and looking online, some others who had it just had a bent usb port, but mine appears to be good, and all 5 pins look A-OK.
(Also, as a side note: Man, look a the viewing angles on that thing in the second shot, you can still see the error from the first pretty clearly. That is awesome.)
SoberSquid said:
Here are some fancy photos:
Download mode (Plus the error message given):
http://i.imgur.com/T4wOE.jpg
USB Port:
http://i.imgur.com/COAhb.jpg
Its an odd error, and looking online, some others who had it just had a bent usb port, but mine appears to be good, and all 5 pins look A-OK.
(Also, as a side note: Man, look a the viewing angles on that thing in the second shot, you can still see the error from the first pretty clearly. That is awesome.)
Click to expand...
Click to collapse
In download mode it should show up as a Samsung diag modem or something like that.
I'll bet it's your cord or usb port on your PC. Can you try a different port or cable?
Sent from my Nexus S 4G using xda premium
Tried different ports (And different computers, My linux box is the same) - I have also been through 3 different cords trying this. - That message comes up immediately, even if there is no USB cable connected.
SoberSquid said:
Tried different ports (And different computers, My linux box is the same) - I have also been through 3 different cords trying this. - That message comes up immediately, even if there is no USB cable connected.
Click to expand...
Click to collapse
are you seeing any com port at the bottom of the window? mine is com4
SoberSquid said:
When I go into download mode (Or fastboot, for that matter), it shows the following on the screen, which I think is part of the cause of this issue:
"USB Control Init"
"USB Control Init End"
These happen right after one another. I'm not really sure why the USB controller wouldn't be working in this case, but I think whomever had the phone before me (in an attempt to fix an issue), decided to restore this phone back to stock using the I9020T files. I believe the Nexus S GSM variant may have a different USB controller in it, which is causing the drivers to malfunction on the CDMA variant, but I could be wrong. I haven't seem something like this occur before, lol.
Click to expand...
Click to collapse
and don't worry about that error, mine says that too

[Q] question about download mode

hi,
I updated my samsung infuse to 2.3.6 and now when I get into download mode it says at the top custom download binary:NO and the next line says current binary: samsung official. How can I get it back to normal download mode? I could really use help with this
giligan30 said:
hi,
I updated my samsung infuse to 2.3.6 and now when I get into download mode it says at the top custom download binary:NO and the next line says current binary: samsung official. How can I get it back to normal download mode? I could really use help with this
Click to expand...
Click to collapse
Hey, good thing for you is that the screen you are describing IS normal download mode. With the 2.3.6 update came an update to the way download mode looks and works. That custom download binary:NO just means that you haven't loaded any custom binaries to the phone (you're on the stock one), and where it says current binary, it lists which version you are on: in this case, official Samsung.
Nothing is wrong, and all is as it should be.
Thanks a million. I was worried for bit. I have an other question that hopefully you can help me out with. I have been trying to use odin and superoneclick since I updated to 2.3.6 and I can't get the phone to work with either odin or superoneclick. It worked fine with both programs before the update. I really wanna root the phone but haven't been able to. Hope you or anyone can help me out.
giligan30 said:
Thanks a million. I was worried for bit. I have an other question that hopefully you can help me out with. I have been trying to use odin and superoneclick since I updated to 2.3.6 and I can't get the phone to work with either odin or superoneclick. It worked fine with both programs before the update. I really wanna root the phone but haven't been able to. Hope you or anyone can help me out.
Click to expand...
Click to collapse
seems like SOC doesnt work with the official update
and try re installing drivers or using different USB ports on PC before giving up
try each at least 3 times and make sure you are not using a hub or anything
and you have a direct USB connection
Heimdall and Odin get picky sometimes
As jayRokk says, uninstall your Samsung drivers and Kies installation in Control Panel / Programs and Features (or Add Remove Programs). Reinstall Kies to be sure that your drivers are installed correctly (This is for Odin, to get drivers for Heimdall you have to use the zadig program that comes with Heimdall to install a different driver on one specific port.).
Then, you might want to try this Odin package that I put together to make it easy to get stock AT&T Gingerbread with root.:
http://forum.xda-developers.com/showthread.php?t=1613523

[Q] How to get 4.3 update for US Cellular SCH-R530U

I need help. I have tried to download the 4.3 update for US Cellular for sg3 from the Samsung site and from xda site. Everytime it tries to install to my computer, there is always an error extracting. I shut off firewall, Norton, and uninstalled anything Samsung from my computer, but still get error msg. I have talked to someone else with same problem. Must be a glitch with the download itself?
Meanwhile, I tried to get the 4.3 update from Kies. Kies updated to v2.6. Then it says my phone not supported. Makes me do Kies3. Still says my phone not supported. Kies refuses to connect to my phone, even though I never had problems before. Says my s/n is incorrect. Comes down to my IMEI being corrupted, I guess.
I used Triangle Away, then unrooted, but am still not able to get 4.3 update OTA through USCellular. It just constantly says checking for updates. I assume it knows my phone has been modified.
Can anyone help me figure out how to get the 4.3 update? I am only a little tech savvy. I originally rooted with One Click Root, but would be willing to root with something else if necessary. Thanks to anyone in advance for some help.
US Cellular SG3 SCH-R530U 4.1.2
baseband R530UVXAMD4
Build JZO54K.R530UVXAMD4
4.3 Jellybean for US Cellular SCH-R530U
smithar said:
I need help. I have tried to download the 4.3 update for US Cellular for sg3 from the Samsung site and from xda site. Everytime it tries to install to my computer, there is always an error extracting. I shut off firewall, Norton, and uninstalled anything Samsung from my computer, but still get error msg. I have talked to someone else with same problem. Must be a glitch with the download itself?
Meanwhile, I tried to get the 4.3 update from Kies. Kies updated to v2.6. Then it says my phone not supported. Makes me do Kies3. Still says my phone not supported. Kies refuses to connect to my phone, even though I never had problems before. Says my s/n is incorrect. Comes down to my IMEI being corrupted, I guess.
I used Triangle Away, then unrooted, but am still not able to get 4.3 update OTA through USCellular. It just constantly says checking for updates. I assume it knows my phone has been modified.
Can anyone help me figure out how to get the 4.3 update? I am only a little tech savvy. I originally rooted with One Click Root, but would be willing to root with something else if necessary. Thanks to anyone in advance for some help.
US Cellular SG3 SCH-R530U 4.1.2
baseband R530UVXAMD4
Build JZO54K.R530UVXAMD4
Click to expand...
Click to collapse
I have the the same phone down to the baseband and build number. I've downloaded the 4.3 executable, but when I run it on my Windows 7 Home Premium PC, the file extraction always fails. Not sure why, and I can't find anything online about the problem.
I'm wondering if it is even worth the time to try and update the phone? Because something that should be straight forward, is completely bass ackwards.
Any help from the community?
Thanks!
US Cellular Galaxy S III
Model Number: SCH-R530U
Android Version: 4.1.2
Baseband Version: R530UVXAMD4
Build Number: JZO54K.R530UVXAMD4
Kernel Version: 3.0.31-1131058
4.3 update
kevin1061 said:
I have the the same phone down to the baseband and build number. I've downloaded the 4.3 executable, but when I run it on my Windows 7 Home Premium PC, the file extraction always fails. Not sure why, and I can't find anything online about the problem.
I'm wondering if it is even worth the time to try and update the phone? Because something that should be straight forward, is completely bass ackwards.
Any help from the community?
Thanks!
US Cellular Galaxy S III
Model Number: SCH-R530U
Android Version: 4.1.2
There was a new update on the Samsung site dated Dec 3. Comes as a zip file. I tried on 2 different computers. Still got error message while installing to computer. Once again I emailed Samsung support. All they came back with was instructions on how to flash it to my phone. Very frustrating. Every email I have sent them, I tell them the simple update tool won't even install on my computer. It has nothing to do with not updating my phone itself. I sent them a new email this morning, stressing to stop giving me instructions on how to update my phone, but that their download still has problems just installing to our computers.
I have decided that I probably won't be able to get the 4.3 update since Samsung and US Cellular can't give us a good download. I also can't use Kies or OTA. Oh well. I'm sure I will rethink having a Samsung phone ever again. Think I'll go back to Motorola, or maybe even try an HTC for once. Looks like their 4.3 updates have been good.
Click to expand...
Click to collapse

Categories

Resources