Related
So, I broke my phone and a buddy had an MDA laying around. However, when you turn it on a ton of errors come up:
Init_Tray.exe
CapNotify.exe
WiFiInit.exe
CheckAutoRun.exe
all are missing or cannot be found.
I tried the hard reset and no go. I was able to get it into bootloader mode and attempted to try the T-mobile ROM upgrade in hopes that I could fix this phone and I got error 274. Does this mean the phone cannot be fixed?? WM runs all goofy and I'm hoping that someone can provide some insight on this phone. TIA.
In the words of the immortal Johnny Five from the movie "Short Circuit"-INPUT! NNNEEEDDD INPUT!!! But seriosuly man, download the Wizard Service Tool, and tell us what information it displays, such as your IPL/SPL, if its a G4 or G3 and whatnot...than we can help yah!
Got the tool and at first it would not let me run the ENAB RAPI + UNASSIGNED APPS, but finally it let me. (just so you know, from time to time when connected to ActiveSync it will disconnect on it's own). Got ENAB + APPS to work, but when I hit DEVICE INFO I get the following:
Warning!
A device was detected but one (or both) of RAPI
Communications and Applications Policy isn't
enabled.
Use first button for that purpose and try again
--------
So, I ran it (ENAB+APPS) again and it was successful again, but when I hit the DEVICE INFO I get the same error.
Is there any possible way to flash the ROM via the SD card??? I think one the biggest problems is the Active Sync connectivity.
bane126 said:
Is there any possible way to flash the ROM via the SD card??? I think one the biggest problems is the Active Sync connectivity.
Click to expand...
Click to collapse
Nopes ! sdcard rom flash is only possible,if you already had backed up the present rom on a sdcard and secondly, if the phone is already CID unlocked.
You can manually copy and paste the two cabfiles 'EnableRapi' and 'Cert_SPCS',in your phone and execute,they can be found in the installation folder of the Wizard Service Tool...> files folder in the program files in C:\ drive,if you are able to establish connection with Activesync.
To verify the connectivity,get your phone into Bootloaders mode (multicolor screen) and hook up the phone with pc via usb,check if small usb appear at the bottom of the Bootloaders,if its there,than its establishing connection,otherwise,your usb cable or mini usb port of the phone is faulty.
Many connections problems are also related to weak battery,get the battery fully charged.
If it establishes connection in Bootloaders,than download the official carrier's rom and flash it in Bootloaders,it'll work out.
Cheers!
I was able to put these files 'EnableRapi' and 'Cert_SPCS' on there, but when I go to execute it does it super fast and I don't get a verification. Is that normal?
I will charge the battery and try that too. Thanks.
Yes, that is normal..all they do is tweak 2 settings, they dont actually write anything, and no, they dont have any kind of confirmation screen to go along with them.
Finally!!!!
So, I was finally able to bring this badboy back to a usable state. After many failed attempts at flashing the ROM I tried something that I hadn't done before. I killed the wcescomm process and disabled ActiveSync via USB before I connecting the MDA in bootloader mode. Once I did this the ROM update began working and I almost jumped out of my seat at work. Was able to get it going without and crazy errors and now have a usable MDA. Thanks for everyones advice.
Kill the wcescomm process!!!! and disable USB AS!!!!
When you start to flash and run RUU,it automatically disables and stops Activesync,but yes,sometimes it helps out by manually disabling and or altogether stop activesync running by stopping wcescomm process.
Anyway,glade you got it working.
Hello
I have a big problem with the drivers to my phone in both Vista and XP, when I connect my phone it is not recognized by the computer.
It shows up as an unknown device and I am unable to update the drivers, it says that I already have the best avaliable drivers.
I can not access the phone thru the computer.
I have searched for answers and nothing has worked I have even formated my computer but still the same problem.
Does anybody have any solutions or thoughts about this problem?
//Johan
Have you tried downloading the Android sdk and directing Windows to the drivers supplied? It's weird you have a problem with XP, my Dell recognized the phone first time.
Clinton
Yeah I have tried that it just says that the best available drivers are installed.
Yeah it is weird, it worked for a while and then it just stopped working after playing around with som tethering apps. But I thought that it would work again after formatting the computer, but no.
Check the Sapphire wiki in my signature - fezza added some info on how to fix driver issues in there yesterday.
Solved it by Hard-reset on phone, just plugged it in and BAM ...
When I connect my Galaxy S to my PC it starts to install the drivers.
The driver consist of 3 parts, but the last one, the MTP USB device, fails to install. I tried restarting my pc after installing Kies and also tried alternate drivers for Windows 7 x64.
When I connect my phone in Kies mode I get an error saying:
FsUsbService64
Service Initiali Failed
(screenshot attached)
Anyone familiar with this problem and/or it's solution?
kashmir83 said:
When I connect my Galaxy S to my PC it starts to install the drivers.
The driver consist of 3 parts, but the last one, the MTP USB device, fails to install. I tried restarting my pc after installing Kies and also tried alternate drivers for Windows 7 x64.
When I connect my phone in Kies mode I get an error saying:
FsUsbService64
Service Initiali Failed
(screenshot attached)
Anyone familiar with this problem and/or it's solution?
Click to expand...
Click to collapse
I have the same problem, however using Windows XP 32 bit SP3
And I get:
Try this, its good for win7 32bit and 64bit also. (My girlfriend and I both have our own SGS, and her win7 32bit is working flawlessly with this driver just like my win764bit.)
Aylarth said:
Try this, its good for win7 32bit and 64bit also. (My girlfriend and I both have our own SGS, and her win7 32bit is working flawlessly with this driver just like my win764bit.)
Click to expand...
Click to collapse
Yeah I've tried this package. Same error.
RagnarIceblood said:
I have the same problem, however using Windows XP 32 bit SP3
And I get:
Click to expand...
Click to collapse
Thanks a lot! I will try this later on when I'm able to connect to my pc.
If this doesn't work, could it have something to do with the firmware version?
RagnarIceblood said:
Yeah I've tried this package. Same error.
Click to expand...
Click to collapse
dang... then this is something I cant help in, I'm really sorry
kashmir83 said:
Thanks a lot! I will try this later on when I'm able to connect to my pc.
If this doesn't work, could it have something to do with the firmware version?
Click to expand...
Click to collapse
All I know is that this usb driver package helped me and my gf either, without this pack I got the same error like you did, and since then everything works properly. If this package cant help you then I have to admit this is beyond my knowledge.
Just found our that i left my usb cable at work
Thanks again for your suggestion. I will try this after the weekend.
Aylarth said:
dang... then this is something I cant help in, I'm really sorry
Click to expand...
Click to collapse
Some more info.
The last one is from Event Viewer, where it claims that this version of Windows does not support Windows Portable Device drivers.
What a bunch of bollox, my HTC HD2 synced just fine. Must be Samsung crappy driver I guess.
And yeah, I got v 4.5 of windows installer.
update: after lots of googling, I've solved the issue.
re-installed Windows Mediaplayer 11 !
RagnarIceblood said:
update: after lots of googling, I've solved the issue.
re-installed Windows Mediaplayer 11 !
Click to expand...
Click to collapse
huh?.. mediaplayer? wierd solution ..
I had this issue too, on my moms pc.
I installed kies befor plugging my phone to the pc, it worked perfectly then, installed the drivers and all. could not see if you had tried that. so its worth a shot
another thing to keep in mind
open TASK Manager in Windows
and make sure ADB.EXE is not running
if ADB.exe is there just end task it
when ADB.exe is left in memory, it locks up the USB connection with the phone, and Kies goes into dumb mode
drhonk said:
huh?.. mediaplayer? wierd solution ..
Click to expand...
Click to collapse
Not really, WMP 10 is the one responsible for the stock MTP driver.
My old computer worked fine with kies, but this new 64 bit one just wont insall the mtp driver, even if i try manually.
Just a quick note on what I discovered last night when trying to get my SGS connected.
Bluetoothe needs to be off
It has to be using the stock Home screen I was as ever using LauncherPro. As soon as I switched back to stock it connected.
rocketpaul said:
My old computer worked fine with kies, but this new 64 bit one just wont insall the mtp driver, even if i try manually.
Click to expand...
Click to collapse
try what I did, re-install WMP 10 (or 11)
I don't know if this is obvious or not... but if your running a downloaded Launcher such as Launcher Pro... make sure you revert back to the stock launcher when trying to connect to KIES. This has been my problem until I stumbled across it last week.
TeamSancheZz said:
I don't know if this is obvious or not... but if your running a downloaded Launcher such as Launcher Pro... make sure you revert back to the stock launcher when trying to connect to KIES. This has been my problem until I stumbled across it last week.
Click to expand...
Click to collapse
how do you do that btw?
reinstall wmp11
hey ive got the same problem..
but how do you reinstall windows media player 11 on vista?
AllGamer said:
another thing to keep in mind
open TASK Manager in Windows
and make sure ADB.EXE is not running
if ADB.exe is there just end task it
when ADB.exe is left in memory, it locks up the USB connection with the phone, and Kies goes into dumb mode
Click to expand...
Click to collapse
Unfortunately, this did not fix it on my droid X
When I try to open Kies on my PC I get the following message. "Cannot set Owner property to a Window that has not been shown previously"
This problem has only started today and I had not done anything to course it.
I have tried reinstalling Kies but I still get the same message.
Any help will be thankful for.
are you using Windows 7 ?? try to run KIES as administrator, if that fails, try running in compatibility mode, like xp or summit.
weird problem, also check you have latest version
Yes Windows 7. I always run a administrator. Have downloaded latest Kies since this problem started.
Anyway thanks for your help.
I don't know what happened but all of a sudden Kies is now working again.
My thanks to those who looked in. I just hope that it stays working OK.
windows 7 has that problem for me to..
Hello ppls.
I've read some similar threads about this problem, tried some solutions, didn't worked and they didin't really had my situation.
So lets begin. My phone isn't recognized by my computer of anysort. When i plug the device i get this error: Windows has stopped this device because it has reported problems. (Code 43) .Tried solutions for the error with no succes.
I run Windows 7 64 bit,4gb Ram, Intel Quad Core 2,2 Ghz. I downloaded the drivers for the device from samsung, bummer when i manually try to update the drivers and set the path to where the drivers are it says The device is already up to date,even with online search.
What i've tried so far:
1. Tried in normal condition with KIES. Debugging off.
2. Debuggind on. Same
3. Different PC with windows 7 32 bits, same error, same solutions that don't work
4. Updating .Net framework
5. Installing a program that automaticly detects drivers. It didnt even see it.
6. Checking the cable for corrosion or anything else faulty. Cleaned it even.
7. Yelling are the stupid phone !!
Thank you.
rahbert said:
Hello ppls.
I've read some similar threads about this problem, tried some solutions, didn't worked and they didin't really had my situation.
So lets begin. My phone isn't recognized by my computer of anysort. When i plug the device i get this error: Windows has stopped this device because it has reported problems. (Code 43) .Tried solutions for the error with no succes.
I run Windows 7 64 bit,4gb Ram, Intel Quad Core 2,2 Ghz. I downloaded the drivers for the device from samsung, bummer when i manually try to update the drivers and set the path to where the drivers are it says The device is already up to date,even with online search.
What i've tried so far:
1. Tried in normal condition with KIES. Debugging off.
2. Debuggind on. Same
3. Different PC with windows 7 32 bits, same error, same solutions that don't work
4. Updating .Net framework
5. Installing a program that automaticly detects drivers. It didnt even see it.
6. Checking the cable for corrosion or anything else faulty. Cleaned it even.
7. Yelling are the stupid phone !!
Thank you.
Click to expand...
Click to collapse
Have you tried with a different USB cable?
No because i connected succesfully my friends galaxy fit with it, so the cable is not the problem.
thry manualy installing galaxy s drivers on pc?
Uninstall and reinstall the drivers.
Try different drivers.
Make sure you're using a Samsung wrong with the Samsung drivers.
Use a different PC.
Keep trying!
I gave up...I tried everything.Spent hours of searching forums and applying solution, nothing works... Tried On 3 different pc's. 1 with win 7 64bit, and the rest win 7 32 bit. I can't manually install the drivers either. Says there are already up to date when i set a location for the drivers to detect...I can't even use it as mass storage.
rahbert said:
I gave up...I tried everything.Spent hours of searching forums and applying solution, nothing works... Tried On 3 different pc's. 1 with win 7 64bit, and the rest win 7 32 bit. I can't manually install the drivers either. Says there are already up to date when i set a location for the drivers to detect...I can't even use it as mass storage.
Click to expand...
Click to collapse
To try using different drivers you would need to uninstall the current driver.
And just to be sure, you didn't flash to CM7/MIUI recently, not realizing Samsung drivers won't recognize your phone anymore, right? Nexus S drivers for those ROMs.
Its on the original ROM i think. Recently bought it second hand, 1 year old.
I couldn't find different drivers...except 32 bit and 64bit, but they all are the same version. Maybe post a link or something. Mine are 1.4.4.
Firmware version: 2.3.3
Baseband version i9000XXJVO
Kernel Version: 2.6.35.7-i9000xwjvh - CL184813 [email protected] #Dark_core_2.4 Mon May 16 15:02:38 EEST 2011
Build Number: DarkyRom JVH v10.1
SOLVED. The problem was from the ROM Darky 10.2. I went to a service did a resoft donno how they do it, installed me the original gingerbread 2.3.4 and now works like a charm!
rahbert said:
SOLVED. The problem was from the ROM Darky 10.2. I went to a service did a resoft donno how they do it, installed me the original gingerbread 2.3.4 and now works like a charm!
Click to expand...
Click to collapse
Just for future reference, this site is filled with tutorials on how to do just that. In fact, that is what this site is all about—new ROMs, new ideas, and how to get them onto your device. Look around next time.
upichie said:
Just for future reference, this site is filled with tutorials on how to do just that. In fact, that is what this site is all about—new ROMs, new ideas, and how to get them onto your device. Look around next time.
Click to expand...
Click to collapse
Dude i'm not the kinda of guy that doesn't research first. Like i mentioned i tried everything i found with no effect. The thing is, the problem reappeared after a day, with the new rom. Took it back to the service, said its a virus from some apps i installed...Is it possible? Thing is, it worked even after i restored all my apps.
I couldn't change the rom either because neither Odin or Heimdall saw my phone, if that is what you reffered to. If you know how to resoft a phone without the pc recognizing it (not even as a composite USB device in download mode or debugmode) and just Showing in Odin or Heimdall "Unknown Device" and failed at installing ClockworkMod, be my guest and redirect me to the tutorial, or tell me how to do it.
Thx
rahbert said:
Dude i'm not the kinda of guy that doesn't research first. Like i mentioned i tried everything i found with no effect. The thing is, the problem reappeared after a day, with the new rom. Took it back to the service, said its a virus from some apps i installed...Is it possible? Thing is, it worked even after i restored all my apps.
I couldn't change the rom either because neither Odin or Heimdall saw my phone, if that is what you reffered to. If you know how to resoft a phone without the pc recognizing it (not even as a composite USB device in download mode or debugmode) and just Showing in Odin or Heimdall "Unknown Device" and failed at installing ClockworkMod, be my guest and redirect me to the tutorial, or tell me how to do it.
Thx
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1347899
upichie said:
http://forum.xda-developers.com/showthread.php?t=1347899
Click to expand...
Click to collapse
How can i use Mobile Odin if i can't root it?
Anyway the problem has been identified as the driver behind the usb slot of the phone, At least that what the guy at the service said...for the moment i'm waiting. I'll keep you posted.
rahbert said:
How can i use Mobile Odin if i can't root it?
Anyway the problem has been identified as the driver behind the usb slot of the phone, At least that what the guy at the service said...for the moment i'm waiting. I'll keep you posted.
Click to expand...
Click to collapse
Throw it against the wall then. You ask us for help, disregard all of it, and then update us on what the service desk told you. If you will only listen to them, then don't ask us, kay? Appreciated.
Hi, there.
Actully, the rahbert's question is not bad. How can i use Mobile Odin if i can't root the device?
Or, how can I root without PC? Is it possible? I have exactly the same problem:
Nexus S (I9020), ICS 4.0.4(stock). When I plug the device: the error is reported(Code 43).
Should I try wipe data/factory reset? I really don't want to do this, because there is another good question: How can I fully backup my data(Titanium and so on) without root access? Can you suggest me something? Thanks.
Herman76 said:
Have you tried with a different USB cable?
Click to expand...
Click to collapse
Changing the USB cable worked for me. Thanks!!