I have not found anything passed a couple of people saying they were stuck in apx mode and then they install the apx drivers but no info after that please help your fellow member out
Related
hello i found this forum great for mod my samsung galaxy s here i found a lot of thinks.
but here is my problem i have already install the samsung kies and android sdk, but when i trie to update my phone with kies the process run normally until it come the time that kies put the phone in download mode, there i receive a messege on the windows task bar like i have disconnected the phone and then it says that "error unknow device" and the upgrade on kies cant go on.
any help plz thanks
i have a att galaxy s rooted
windows 7 32bit
latest version of kies
First thing to try is test each of the different usb ports on your computer - if you get the same error on each port then my first instinct would be to reinstall the samsung drivers for your computer.
If you try reinstalling the drivers below is a link to the drivers that have worked the best for me.
http://www.mediafire.com/?0b45zo7o75rc5d5 - samsung captivate windows 32 bit drivers
thanks for your replay. i already have uninstall the drivers and reinstall them with no success, but i will try to test it in other usb port and report later
this is soo bad i have try both of you recomendations and still says usb device not recognize. then it says no driver was install and when i click that it says on the driver part that windows have stop the device for a error code 43.
i have search a lot and i havent find anything close to my problem can anyone else give recomendations on this or tell me if you know something similar to this happend to other users.
ps - i also try on a win xp 32 with the same result
Hey guys,
Hope you can help me out here. I can get into the 3button recovery mode but kies doesnt seem to find my phone. So it cant complete the recovery...
Im running on vista fully updated 64 bit. Downloaded the x64 usb drivers posted somewhere on the XDA forum. Worked before but now nothing...
ps I had to use recovery since my phone got disconnected during an update and didnt complete the process....
Tried installing the newest kies version, an older one, in combination with both the 32 and 64 bit drivers. But so far nothing.
Please help, been at it all night.
Cheers!
my phone is bootlooping and adb isnt recognizing the device and hence smartflashtool
but after installing lg united mobile drivers i get unable to install drivers on windows 7 x64
so can anybody point me to a link to download the drivers. i tried almost all the working links on this forum but does not work
tried it on a win 7 32 bit and it worked
Hello i tried connecting my XSP to flash a new kernel in fastboot mode and windows 7 say unrecognized device i tried installing all drivers provided in the flashtool drivers folder with no result .... I tried installing the fastboot and flashmode drivers but no reaction from the pc it still says unrecognized device .
Sorry for the bad description of the problem but i was typing in a hurry for any details please ask me.
Where can i find the APX drivers for this phone since i can't flash anything in S/W update mode but i also can still use it as a APX device. I found a APX driver on the forum but that isn't for this phone.
Underground597 said:
Where can i find the APX drivers for this phone since i can't flash anything in S/W update mode but i also can still use it as a APX device. I found a APX driver on the forum but that isn't for this phone.
Click to expand...
Click to collapse
You can't flash it through APX because we don't have the SBK.
Better buy another phone.
adryyy said:
You can't flash it through APX because we don't have the SBK.
Better buy another phone.
Click to expand...
Click to collapse
Okay thank you for the reply it's not my main phone i am just trying to fix it to use it as a secondary phone.
Try again?
If you still have the 'brick' in a drawer somewhere, the blob.bin along with all of the other files is now out to allow you to try restoring that phone. Somebody needs to be the first to actually turn it loose and see which firmware version it loads, etc. and it doesn't sound like you have any better remaining options.
Look in this thread: Maybe a working nvflash method