[Q] Kies? - Galaxy Tab Q&A, Help & Troubleshooting

Hi friends. My question is: Do I have to install Kies in order to be posted for upcoming upgrades? I have tried to install Kies umpteen times but somehow it refuses to start on my XP pc. My location is Israel but I download the english version instead of the hebrew one. Does this make a difference?
Thanks!

Are there any error messages when you try to start Kies?
I hope your XP is constantly updated as well.
And the language has no affect on this, as far as I know.

Yes. The message says the program cant be run and windows has to close!
XP is up to date. Any ideas? Thanks!

Related

Very new person, why am i having so much trouble?

When I run the wizard update for rom or radio or anything it says one of two things on my pc, 1. that there is a connection error and or 2. That the program needs to close because it says so. Im sure there is a simple fix to this issue but i just dont know it.
Thanks
I think I know why
After reading through the posts I discovered why I am having so much trouble. Reason being last week I upgraded to Vista, which would explain alot.
Anyone know a way arround this problem?
irishmatt12 said:
Anyone know a way arround this problem?
Click to expand...
Click to collapse
Downgrade to XP...
There are lots of issues with the rom updater and Vista. Unfortunately until a new version of the rom update utility comes out (or some other new method) its going to be an issue.
Not only RUU, WMDC itself sometimes get problems in Vista.
When I connect the Wizard to PC, sometimes WMDC does not show up, and the PPC is not present in My Computer, and you will see a yello exclamation in device manager!
The only thing I can do is to remove the device complete from device manager and let it detects again, then I can use it again for several times.

Big Problem?

I was performing the radio update on my MDAIII and now he hangs in the bootloader with USB in the upper middle und 2.08 in the under middle. All resets won`t bring it back to life. If I try to reinstall the update all I get is a blank message screen (update from version to version) in my Vista. How can I get out of there.
I did everything what was stated here
The original BAUpgradeUT won`t find my device. The MAUpgradeUt_noID.exe gives me the blank screen with the update from to screen.
Drake008 said:
I was performing the radio update on my MDAIII and now he hangs in the bootloader with USB in the upper middle und 2.08 in the under middle. All resets won`t bring it back to life. If I try to reinstall the update all I get is a blank message screen (update from version to version) in my Vista. How can I get out of there.
I did everything what was stated here
The original BAUpgradeUT won`t find my device. The MAUpgradeUt_noID.exe gives me the blank screen with the update from to screen.
Click to expand...
Click to collapse
I'm using a Vista PC.
After the Radio update to 1.15 the error described above is not to go away yet.
What to do, I'm nearly in tears.
Finally I got it back but with an old Romupdate from T-Online. Is there someone who got the QTC 9090 update (latest one)
That was fast..
im glad you solved your problem.
i think someone here has it.
just post what you need and make it as a title for others to read in the digest.
Im not a expert but is vista the problem??
Most likely.
Failed MDA II flash with vista notebook
Hello everybody,
I just read this thread in hope to find a solution for my problem, which is quite similar to the one described here initially.
I got a used MDA III with T_Mobile ROM. Since I'm a customer with O2, I wanted to change the ROM to O2 as well. I followed the directions given in an other thread here (don't have the link just now) and during the flashing, the flash application suddenly had no connection to my MDA III anymore. It was securely settled in its craddle an connected to my laptop via USB. Now my MDA III is stuck in Bootloader Mode with USB v2.07 displayed on the screen.
Each retry of installing either the O2 or the T_Mobile ROM now meet with the error 101: no connection. I read here that you managed to update successfully with a vista pc. Thus I wanted to ask, how you did that since I just don't seem to find the reason for the connection failing each time.
Here is what i tried to establish connection so far:
* disabled virus scanner & firewall
* unplugged the mda III and plugged it in again. It was recognized as a new device but that didn't help the connection issue
Could you please post what you did to make the update work under vista? Help would be greatly appreciated
mda3newbie said:
Hello everybody,
I just read this thread in hope to find a solution for my problem, which is quite similar to the one described here initially.
I got a used MDA III with T_Mobile ROM. Since I'm a customer with O2, I wanted to change the ROM to O2 as well. I followed the directions given in an other thread here (don't have the link just now) and during the flashing, the flash application suddenly had no connection to my MDA III anymore. It was securely settled in its craddle an connected to my laptop via USB. Now my MDA III is stuck in Bootloader Mode with USB v2.07 displayed on the screen.
Each retry of installing either the O2 or the T_Mobile ROM now meet with the error 101: no connection. I read here that you managed to update successfully with a vista pc. Thus I wanted to ask, how you did that since I just don't seem to find the reason for the connection failing each time.
Here is what i tried to establish connection so far:
* disabled virus scanner & firewall
* unplugged the mda III and plugged it in again. It was recognized as a new device but that didn't help the connection issue
Could you please post what you did to make the update work under vista? Help would be greatly appreciated
Click to expand...
Click to collapse
Try on computer with Windows XP and kill activesynk (wcecomm.exe on taskmanager/processes)
Maybe it will work. If u cant flash O2 ROM try to use "MaUpgradeUt_noID.exe". On my Qtek 9090 allways flash using this APPS and allways work.
U can try too format device first, put it on candle and use "mtty1.42.exe". On XP, kill active sync, and open mtty1.42.exe and select port USB and put OK. Do "Enter" on command and should appear USB>. After this write Task 28. This will format all your PC. Try install SO after this. This command delete all files on PPC. I have attach files that you maybe need.
thankfor the tipp and sorry for my late reply. Since I have no XP PC available i tried the mtty1.42.exe on my vista notebook. When i run it however, it only lists com port 1-3, no usb port. Do i have to make a special configuration on vista for it to work?
Thanks in advance,
mda3newbie
mda3newbie said:
thankfor the tipp and sorry for my late reply. Since I have no XP PC available i tried the mtty1.42.exe on my vista notebook. When i run it however, it only lists com port 1-3, no usb port. Do i have to make a special configuration on vista for it to work?
Thanks in advance,
mda3newbie
Click to expand...
Click to collapse
In vista i dont know...sorry for my late reply too.... in XP u must kill ActiveSync process called wincecom.exe. in vista, maybe u have to kill the Windows Mobile Device Center....i dont know...
Dont forget, put the Qtek 9090 in Boot Loader Mode (Pressing Power Button + Record Button + Reset), maybe will appear USB and u can format the device.
If this does not work, try on Windows XP....Find a friend with Windows XP and ask him to use his PC only to do that.
Maybe somebody in forum have the Windows Vista and can help u....
Sorry my terrible english....
Sjogos said:
Try on computer with Windows XP and kill activesynk (wcecomm.exe on taskmanager/processes)
Maybe it will work. If u cant flash O2 ROM try to use "MaUpgradeUt_noID.exe". On my Qtek 9090 allways flash using this APPS and allways work.
U can try too format device first, put it on candle and use "mtty1.42.exe". On XP, kill active sync, and open mtty1.42.exe and select port USB and put OK. Do "Enter" on command and should appear USB>. After this write Task 28. This will format all your PC. Try install SO after this. This command delete all files on PPC. I have attach files that you maybe need.
Click to expand...
Click to collapse
hi guys I tried the step by step process and when im enterin( Task 28 ) then pressed Enter -
Invalid command : Task28
For a help screen, use command ? or h
does any one know where the problem is??
Try this
Downlaod the XDA IIs .exe file and run it - no need to put into USB mode
http://www.o2online.ie/wps/wcm/conn...es+&+accessories/Xda+Range/Software+upgrades/
this should reset to factory default (o2)
it runs on vista too
I am not 100% sure it will work but worth a try
diesel_dog said:
Im not a expert but is vista the problem??
Click to expand...
Click to collapse
Yes, i know my reply is late but the problem ist 100% Vista! i Tryed 2 ours with vista...then i decided to format my pc and to install XP. At the first try it worked!

Settings, system, windows update doest work

I get this message everytime I try to update windows trough windows update:
Connection to updateserver is not available.
result code: 80004005
it says allot more, but the idea of it is that I cant see if its any updates available.
This happens even if im connected trough wifi.
Any ideas?
Is it a way to update to .NET the newest way etc besides this way?
Thanks in advance.
Chris
you will not get .net update via windows update. i don't know if there is a .cab with latest .net, but i've flashed a cooked ROM. In the years i've had windows mobile, i've never used the update feature since there has never been updates.
Search for .net compact framework on the M$ site and select version 3.5. It will download and install to your device.

Upgrading to WM6.5 on XDA IIs - Error 150 Maupgrade

Hey guys,
I am trying to upgrade my XDA to WM6.5. When following the wizard steps, I enter the PDA into the bootload menu, but when I run the application on my XP desktop, I recieve the following error:
Error 150: Rom Upgrade Utility Error
This ROM upgrade utility does not design for your device.
Please get proper ROM upgrade utility and try again.
Help! It's frustrating the hell out of me!
please add which rom you currently use, do you have activesync installed
Me also have the same error
I have yust tried to install the new release with the same result.
I have a Qtek 9090 with WM 6.1 rel 5.2.20262 b. 19949.1.2.0.black, but in the past month I have tested many other...
Simply the install program don't recognize the device so cannot define if it's right or wrong.
Thank you in general for your fantastic jobs !
Sorry !
Yes I have Activesync installed (for another palmsize divice).
What????
Palm size device???? so you dont have activesync... you have hotsync but....
You already tried the WM6.1.... so you have activesync... men you are getting me crazy jejejej lol
BTW...
Try to conect your device if the activesync dont recognize it and sync.... restart your PC and PPC... the if this not works...
Uninstall the AS then Reinstall it..... if not works...
Try to change to other USB port
If dont works check your advanced conections settings
and check or uncheck the advanced network config box..... if not works...
BTW upgrading needs bootloader so put it on Bootloader mode conect it if your PC says something about not recognized just.... try other PC.... are you on VISTA or XP? suggested... XP.
Thanks
I have used very bad words, so don't panic ! The other device is a "normal" HTC 3300 (artemis) with 6.0 italian std rom and A.S. 4.5.0 (Build 5096) on Win XP.
The 9090 syncs regularly and it is regularly connected (I have stopped the bootloader and reboot the BA), I will test to reboot all, and eventually change the USBport, tomorrow morning (I am a little tired now and the eyes start to cross instead of read). As soon as I have done it I will and report here what does happend.
For now many thanks to you and to Xplode also.
night men!!!
Hope it works for you tomorrow... good luckits our pleasure to help.
Have you tryed the following ?
http://wiki.xda-developers.com/index.php?pagename=BA_FAQ_STUCK_AT_STARTUP
All Ok now
Symply from the last uprade of my 9090 I had changed the PC, so it haven't all the right Drivers.
Now, following Win XP requests (it was needing wceusbsh.sys) all is gone right so my 9090 actually exposes: CE OS 5.2.21169 (Build 21169.5.0.0) release. (and I am starting to play )
Many thanks to all.
you do not need drivers, install activesync in your pc, it includes al the drivers you need - if you have it and winxp still wants driver for the ba remove/uninstall activesync and reinstall it again - remember use the latest version of activesync
Hi,
Remove your "puce" and your sd card.
And try again of course with ActivSync.
For less worry upgrade on you BA's...I...WE recommend XP with Active Sync 4.5

Cannot Flash Custom Rom Error 266

As of now, my SPL is downgraded to 1.18, with RSPL and HSPL already installed. I downloaded Windows Mobile Device center, I'm running Windows 7 x86...
I always get the "not connected" message with the device center no matter what, even though I see Windows Mobile drivers in device panel. I've downloaded Deepshining Rom, double clicked on the ROM updater and first thing is it does not show my current image on the phone, when I keep clicking next, I get to the installation screen, with a 0% and then I get the Error 266 message.
I've restarted numerous times, not sure what is going on.
windows driver
drivers all installed in the PC? see in Device Manager check your wp7 device installed correctly, bite also uninstall and re-install wp7 device drivers. I think the error in communication between the PC and the device of wp7
I'm suffering the same problem. Any idea how to counter it? Having HD7 with CotullaHSPL installed. Previously installed deepshine custom room
same problem
me too i have the same problem and i can't find any answer of that
pls can anyone help here that would be great
You need to run in XP both Zune and ActiveSync for the connection to take place.
the-anti-life said:
me too i have the same problem and i can't find any answer of that
pls can anyone help here that would be great
Click to expand...
Click to collapse
you can't find any proper solution of this...try different pc and also check that you select the right rom

Categories

Resources