First, thank you to all the people who have contributed questions and answers about the Samsung Galaxy S phones. If only the company was as good as their phones!
Here is the problem for which I seek a solution:
Started with unlocked Vibrant I9000M from Bell in Canada.
It arrived with Froyo 2.1-update 1, kernel 2.6.29, UGJH2.
Everything worked, phone worked with an AT&T SIM.
Then I let Kies upgrade to Froyo 2.2, kernel 2.6.32.9, UGJK4.
Problems: headphone jack=no output
USB=no connection with Linux or Windows
screen orientation stays landscape no matter what I do. (except for dial pad).
And worst of all , NO ROOT!
Android recovery 3rd edition will not let me use the update.zip method.
No computer I have used with Android SDK will find the device with adb.
It does not show up as connected with USB in WinXP, WinVista, Win7, Ubuntu, or Kubuntu. I have installed all manner of Samsung USB drivers. Best result to date is in Windows, "device failed to start" Code 10!
So who among us has the way to re-establish a connection with the device so I can get root again and change the ROM to something other than a Samsung ROM apparently designed to close the door on open source?
drddx66
Google Nexus One
Clockwork Recovery
Cyanogen Mod (like 6.1.0-RC1 best)
you wont find much help here because you have a different galaxy s phone. check here
Related
Hi I can't seem to get this working no matter what I try.used windows xp on two different pc with no luck any one help me out
-------------------------------------
Sent via the XDA Tapatalk App
What exactly happen?
My screen just flash the usb logo
-------------------------------------
Sent via the XDA Tapatalk App
Make sure you have your usb settings in the phone to Kies or to ask when you plug in. If you are running any launcher other then touch wiz, Kies will not recognize the device. So if you are running a different launcher, clear its defaults and go to the touchwiz home and then plug the USB in.
You probably downloaded the Kies for the I9000, it doesnt work on TMO Vibrant. There is no Kies for USA available for that model yet. Someone suggested to download the Kies from the Canadian Samsung site instead. I believe that Kies for USA will be made available when Froyo is released for the Vibrant.
I downloaded Kies for the USA yesterday and my Vibrant connects fine.
dashed said:
I downloaded Kies for the USA yesterday and my Vibrant connects fine.
Click to expand...
Click to collapse
Where did you find this? On the Samsung site just now I get this message when looking for Kies on the US site:
Currently, there is no offiical version of Kies Stateside for the SGH-t959 (Vibrant).
I think he used the UK, or Canadian version but when you install it you select USA.
I used the Kies found @ http://www.samsungapps.com/about/onPc.as posted by abhiku in a similar thread. Works perfectly on win 7 64
Could you be more specific? That link redirects to http://www.samsung.com/apps/ which doesn't help much.
oh shiii, looks like they pulled the version i dl/d. thankfully, i store installers of this nature on a backup drive. uploaded to sharebee for ya: http://sharebee.com/8cf24208
Thanks, but that didn't solve the MPT USB driver failing.
what exactly is happening? like when you plug it in is it just saying "failed to install device" or is the pc recognizing it for usb mass storage, but nothing else. Some more details would be very helpful.
I have the home screen on TouchWiz
I plug the phone into the USB port
Several drivers install properly
I get the MTP screen on the phone for a few seconds and then it returns to the home screen. A dialog box on the computer says:
Device driver software was not successfully installed
MTP USB Device XFailed
I have tried 3 versions of Kies and 3 different USB drivers
I tried the I9000 version of kies... I could not figure out how to make it work with the Vibrant.
I dont use Outlook... what are the real benefits? I saw it an sync your music? Is there a basic guide/Q&A for Kies somewhere?
I tried to make it work on a rooted phone and it just fails.
First it wanted me to disable USB debugging, and when I did it failed to connect anyway - the software is a piece of rubbish.
Anyway Samsung states in their FAQ that Vibrant is not supported yet
http://ars.samsung.com/customer/usa..._ID=314807&PROD_ID=560&PG_ID=-1&PROD_SUB_ID=0
the screen on the phone just flases the mtp showing a usb plug
The version of Kies that I successfully connected the Vibrant to is 1.5.1.10074_2.
Windows did all of the driver downloading for me lol. Here is a screenshot of the SGH-T959 connected.
lqaddict said:
I tried to make it work on a rooted phone and it just fails.
First it wanted me to disable USB debugging, and when I did it failed to connect anyway - the software is a piece of rubbish.
Anyway Samsung states in their FAQ that Vibrant is not supported yet
http://ars.samsung.com/customer/usa..._ID=314807&PROD_ID=560&PG_ID=-1&PROD_SUB_ID=0
Click to expand...
Click to collapse
I get the same. This software is junk. And what I saw of the interface makes it look like it was written in the 90s.
From what I am seeing on the international side, it may be that Froyo is installed using it so I was hoping to get things working in anticipation of that. Plus, it has a movie converter so its pretty simple to convert movies to the right format.
i need help, i have tried everywhere and can't find anything and any help would be greatly appreciated
i'm on the road to root my samsung galaxy fascinate and have ran into a laundry list of problems. i have rooted many android phones coming from eclair, froyo, and gingerbread, but seem to be stuck at the slightest of problems when it comes to the fascinate.
i can not install the drivers to the fascinate. i have searched through the web for all the drivers and have tried every possible galaxy driver. the driver simply won't install on my windows 7 prof 64bit machine. i have never ran into this problem before with any other phone. every time i try to install the driver it gets to the very end of the install then pops up with the message "windows was unable to install the driver"
It also gave me the option to view the failed windows installation log, which after many successful steps, at the end the log shows this error:
Action ended 1:26:53: ShowMsiLog. Return value 0.
=== Logging stopped: 12/16/2011 1:26:53 ===
MSI (c) (0C:08) [01:26:53:750]: Product: SAMSUNG USB Driver for Mobile Phones -- Installation operation failed.
MSI (c) (0C:08) [01:26:53:750]: Windows Installer installed the product. Product Name: SAMSUNG USB Driver for Mobile Phones. Product Version: 1.3.550.0. Product Language: 1033. Manufacturer: SAMSUNG Electronics CO., LTD.. Installation success or error status: 1603.
i have also attached the entire log
the first thing i did was plug in the phone, which windows sensed this and automatically installed a driver, not sure which. after this i unplugged the phone and then checked "usb debugging" for rooting purposes and plugged the phone back into the computer which windows then installed another driver automatically, then following the steps from xda to root the phone, i downloaded the given drivers which is where the problem first occurred and the drivers were unable to download.
I'm simply trying to get root access to the phone and can't do anything with the phone with crappy drivers...i can't even mount usb sd card now to transfer data anymore. the drivers have completely been shot. i desperately need help. please
also what is the absolute easiest way to root the fascinate? is it with one click root or with Odin? Because the fascinate just updated itself from 2.2.2 EH05 to 2.3.5 EH03 and i'm not sure which program supports rooting which version of android. also all other android devices simply give root access to the stock rom, which is great cause i get to keep all my apps, messages, contacts...etc, then simply titanium backup everything and transfer it over to the new rom. is it different with the fascinate? will rooting the device simply flash a completely new rooted rom? therefore loosing everything? if anybody has any answers to any of these questions, please be my hero. thanks
Uninstall everything you previously installed in the way of Samsung drivers (in fact, you could use Windows 7 backup and restore to restore your PC to the state it was in the day before you installed the drivers as they are sometimes hard to uninstall completely). Reboot and simply plug your phone (with USB debugging of course), and let Windows automatically install the drivers for you like it did before you installed the ones linked to on XDA. This time, if your PC recognizes your phone, just keep the drivers you have and don't install the ones linked to. Those drivers from the guide are for those whose PC doesn't automatically install working drivers. From that point, just follow the rest of the guide and skip the install drivers part. You will not have to install any further drivers unless you flash an AOSP ROM, in which case you'll have to follow the instructions in the OP of the ROM thread. I hope this works for you.
Has anyone seen John Connor?
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
bigwhat said:
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
Click to expand...
Click to collapse
root is not flashed via odin, rather cwm is...then the root file su_2.6.3.1 is flashed via cwm. If you need directions section 5 of my guide in general section has it covered...everything needed is there including the correct recovery and root file.
I will tell you what...the Fascinate is probably the biggest pain in the ass phone...I tried forever to root my friends and couldn't get it done...need to try again I guess, but it was a driver issue as well..ODIN just wouldn't recognize the dam phone
Use Droidstyles guide. Very easy to follow. Also, the USB cable for some reason seams to be a bit finicky at times with this device. Unplug from phone and replug. Sounds odd but trust me, I have done this many times.
Sent from my SCH-I500 using XDA App
I am having a problem too and it's not covered anywhere i've seen to date. I've got an XP and a Win7 box at home. On both, I've tried with no drivers and i've tried with every other driver set I can find and every time I hook the phone up to the machine it pops up saying USB device couldn't be recognized or something. I'm going nuts! I've never had so much difficulty in my life, not even the first time changing ROMs on anything.
Droidstyle- I've seen your guide and unless I missed it doesn't cover this. Have you seen or heard of this and have any ideas at all?
Thanks!
Hello everyone from XDA!
I've been reading several different posts on the Samsung Galaxy S2 GT-i9100, and though many have been helpful (thank you!), I just can't seem to find the solution I'm looking for.
Not long ago I upgraded the stock firmware from Bell Canada (forget the specs) to:
Android version: 2.3.5
Baseband version: I9100XXKI4
Kernel version: 2.6.35.7-I9100XWJK3-CL647431 [email protected] #2
Build number:: GINGERBREAD.XWKJ3
My phone was also rooted.
Recently, however, I've been trying to upgrade to ICS but without success---and I've tried a number of ways, from the XDA forum to various websites around. I suspect the problem may be with my computer (USB related) and not the phone. I'm not sure, I'm not an expert, which is why I come to you for help, please.
The first and only attempt of ever upgrading the firmware (see above) was a success; as per directions, I used Odin: the PIT, PDA, PHONE, and perhaps CSC as well. It has been some time since the ugrade, and in the mix of trying new and different firmware (without success) I have forgotten exactly what happened.
So my problem, now, is that any time I try to upgrade to ICS (or another firmware for that matter) my computer ends up crashing when the flashing of the phone reaches the "boot.ini" stage. My computer (Windows XP Professional) crashes and a blue screen appears with an error---something to do with USB.
I just can't seem up update my phone.
The phone still works perfectly fine, but I really want ICS. I have tried with and without Kies installed. In fact, Kies even allows me to upgrade to a newer version (though it's not ICS) than I currently have. Unfortunately, though, when I try upgrading via Kies, I am also unsuccessful.
Could this just be my computer's USB? The drivers? If you have had similar experience and know the answer please help!
Hookah-Hoodlum said:
My computer (Windows XP Professional) then crashes and a blue screen appears with a USB error.
Click to expand...
Click to collapse
This screams to me it's the computer.
Have you tried on a different one?
Hookah-Hoodlum said:
The phone still works perfectly fine, but I really want ICS.
Click to expand...
Click to collapse
I agree it sounds like a problem with your PC. You can bypass that problem by using Mobile Odin.
As ctomgee says, a blue screen error indicates a problem with your computer, not phone.
The way you are trying to get ICS also seems strange, the current way to get it would be:
Root phone and install CWM using Chainfire kernel.
Download and put the ICS rom on your sd card.
Boot into CWM, wipe everything and install the rom.
Reboot and you have ICS.
What file were you trying to use to upgrade to ICS?
Thanks
@ ctomgee: I've considered using a friends computer but I'm worried about damaging their computer by having an error appear.
@ oinkylicious: Thanks, I never knew about mobile Odin. I'll check it out.
@Kaze105: I appreciate the steps, thank you. The new firmware is GT-I9100_XEU_I9100XXLPB_I9100XXLPB_I9100XEUKH2.tar.md5 and Kernel_I9100XXLPB.tar.md5, respectively.
If any of you have links or suggestions as to favorite roms, kernels, or the like, well I'm open to suggestions!
Hookah-Hoodlum said:
@ ctomgee: I've considered using a friends computer but I'm worried about damaging their computer by having an error appear.
Click to expand...
Click to collapse
Can't hit the target if you don't take the shot...
I'm having a similar problem.
I decided to root my galaxy s2 with the CF-kernel (so this is my initial flash, and mobile odin is no alternative).
But every time I start (in Odin), my computer crashes.
I tried it on a "native" Windows XP x86 system and in a virtual machine with Windows XP x86(because I am using Linux only).
On my second machine with Windows 7 64bit, I cannot install the device drivers correctly (the CDC component fails to install), so Odin (and Kies as well) does not recognize the Device.
Is there any suggestion or alternative to Odin especially for Linux systems?
Thanks in advance!
Edit: enabling USB 2.0 for the virtual machine and reinstalling the USB-drivers did the trick (the native windows system has no USB 2.0). Now it hangs on connectionsetup, but that's another problem.
Hi can anyone help me I have unlocked my phone to all networks but have been told if I update via Kies
it will lock my handset back to previous carrier ( T Mobile )
I really want to update my os and can't find a way of doing it any help or pointers would be appreciated.
Currently running 2.3.4
kernel I900XXKG1-CL349526
Build GINGERBREAD,XXKG1
You can upgrade to ics and pay to unlock.
If it was me,Id upgrade to 4.0.3 by flashing an unbranded firmware from sammobile(for my region).
Then root,then nand/efs backup,then use one of the free unlock apps on here/play(if required).
Rachmats ics rooting
Odin
Hktool
Helroz unlock
Triangle away
Then Id stick on rootbox/dremkernel.........lol
I have already downloaded firmware from Sam's, phone is currently connected via odin flashing firmware.
This has been running for about an hour now, thou there are still signs of action on my laptop HD.
how long should this process take ?
10 mins tops.
Disable kies and try.
I hope in the last 2 hours youve done some reading about the stuff I listed rather than diving in and ballsing things up.
I have disabled kies and tried again thou it looks like it's still not having it.
Half of what I have been reading is only starting to make sense now i'm getting my head around all this.
If you flash any rom from this site or samfirmware should not lock your phone again. It will stay unlocked.
If only I could get one to load up, fortunately I haven't bricked my phone thou I appear to have an ADB driver issue.
Only noticed this when using a later version of odin, I found a guide relating to this issue, I will give this a try shortly, fingers crossed.
It would appear I have an issue with the ADB drivers.
I have done a fresh install on another laptop, installed Kies looked for updates still no joy.
Then I even tried Heimdall 1.3.1 for os x no joy there either.
Now I am looking into finding and installing the ADB drivers from another source,
I have also tried downloading drivers from sammobile no joy there either.
Can anyone give me some advice on this.
I am trying now to install drivers in compatibility mode with xp. i'm currently running vista.
I checked properties in device manager and status of ADB is > This device cannot start (code 10)
This driver only shows when phone is attached via USB, I have tried to update via device manager
Still no joy
Finally having wiped my laptop and reinstalled windows, installed drivers, odin, connected phone,
I got a pass, 3 roms a CF root later, I settled for an unbranded UK ICS 4.0.4,
rooted phone with appropriate CF kernel,restored data. Tidy, well worth the effort.
I have an international Galaxy Note 2 GT-N7100 which I got cheaply because it exhibited the well known wake-lag phenomena. Unfortunately it has a lot of problems. It had been rooted and flashed with a custom firmware by the previous owner, and I guess he did something he wasn't supposed to. At the moment I'm running Cyanogenmod 10.1.3, the only firmware being stable on my hardware. Returned to stock ROM (ICS and JB 4.3) and both of them were extremely buggy. Same with OmniROM and Cyanogenmod 11. All of them also exhibited the wake lag. So something is seriously odd with this phone.
Anyway - when connecting the phone to the PC (Windows 8.1 x64) seven CDC Communication Interface and one Comneon Suspend will show up in device manager. I was able to install drivers using Zadig but it didn't seem to change anything. Odin 3.09 connects just fine to the phone. I have enabled USB debugging mode. ADB won't list the device (using the command adb devices). I wish to be able to use MTP.
Right now I'm lost. Since it's the same behaviour using different firmwares I assume it's on a quite low level. I have understood it may have something to do with the EMEI but how? I have been looking for dialler codes but without success.
Just letting you guys know I was unable to fix it myself, but a Samsung Service Centre could flash the default firmware for me. It wasn't even very expensive, roughly $30. The phone has been working very well since.