Related
Hi all
This is my first post but i have been reading in the forums for a couple of days to see if i can work out how to fix my pride and joy by myself.
I tried to upgrade to WM6 and it seemed to halt mid update and i lost my active sync, it was only a few seconds into the update and i stupidly left the sd card and sim card in the device, this may have been the problem. I can get to the boot loader screen as i can see serial and v1.00 on the grayed out screen. I see USB in place of serial in the boot loader screen when i connect the USB lead and also hear the connection sound on my computer. I know that active sync is working as i have connected my c500 smartphone to check. I have also reinstalled Windows mobile device center. I have also tried to connect on my XP lappy and when i try to start mtty 1.42 it blue screens my lappy (anyone else seen this or have a solution?)
Main thing is can i use an SD image to flash a new rom
If not how can i get active sync to see my device
anyone know a good repair shop in the UK
I really have hunted the forums for an answer to this problem but can't readily find a solution any help gratefully received. Also reassurance that my XDA is not totally dead would be nice.
XDA EXEC
Running boot loader screen only
trying to restore using Vista and Windows XP pro
Yu have not been reading verry well!!!
That is easy to fix, just read WIKI
Disable usb in active synh!!!!
Hi thanks for the speedy reply, but i did try disabling the USB connection in active sync and nothing altered. I may be missing something tho so will have another look at the WIKI. Maybe it's because im using Vista, reason being that my lappy running XP is blue screening, would i be better using the lappy and fixing the mtty problem? If you could give me a link to the easy fix so i could find it a little faster. I really wanted to sort this out myself but i am also concerned that my pda is screwed and although all you maybe see a lazy n00b that hasn't read the site very well i have put in a large number of hours reading, i admit flashing firmware is not something i do every day and im a little out of my comfort zone and a few pointers would be very much appreciated.
I have some staff in my folder wich helped me in any problem situation i have ever been.
Try to borrow someonce PC...
Dont use hubs.
Use the same USB port for the whall proces
Done all of those but still no active sync connection! Is there some way the profile for the PDA in active sync can be removed to allow a clean install? Or can i flash some way with the SD card and avoid Active Sync altogether?
I appear to have sorted the problem now. It would seem that the IR port was conflicting with my active sync connection, i was getting a blue screen and a message about ircomm.sys when i disabled the virtual IR port in control panel my pda connected to the mity application without any problems. Hope this will help someone else that is stuck on the same problem.
So I'm attempting to root the Continuum, but for some reason the phone won't effectively connect to Windows 7. For example, when I hook the phone up to my Samsung i7 laptop, all the phone does is charge. It doesn't even ask me if I would like to use usb storage or anything. The computer also doesn't recognize the device. Any ideas? Thanks!
A couple questions first:
- Did you install the Continuum drivers?
- Does your phone bring up the USB connection in the status bar?
- Does it bring up the Verizon VCast website on connection?
ExNukeSquid said:
A couple questions first:
- Did you install the Continuum drivers?
- Does your phone bring up the USB connection in the status bar?
- Does it bring up the Verizon VCast website on connection?
Click to expand...
Click to collapse
1. I likely did not install the Continuum drivers, and I have no clue where to get them. I'm assuming Samsung's website, but it's a bit hard to figure out and navigate...
2. My phone does not bring up the USB connection in the status bar.
3. When I go to the browser, it brings up the Verizon website with news, etc.
It should probably be stated as well that this phone is not activated. I am using it on wifi only for the time being because I traded it with a friend for another phone.
Alright, so I've figured it out. Strangely enough, I was just using a generic USB to microUSB cable, and I actually needed to use a Samsung cable. Weird, right?
sportsinger75 said:
Alright, so I've figured it out. Strangely enough, I was just using a generic USB to microUSB cable, and I actually needed to use a Samsung cable. Weird, right?
Click to expand...
Click to collapse
So...now that I'm rooted, how in the world do I install a custom rom? I saw that there's a ClockworkMod Recovery out, but what does "Odin" mean? I'm coming from an LG Optimus V and have extensive experience rooting and installing custom roms and recoveries, but I've never heard of that before. Thanks again!
First, we dont have much for custom roms on this phone. The couple we do have contain fairly well written "how-to's" for them.
Second, if you are not sure, do some research and find out as many answers with the vast pool of knowlendge at your fingertips (the interwebs) as you can. There has already been a swarm of questions asked, and I am sure the answers may already be there for you.
I am waiting for the update and Froyo roms to come out before I bother with custom roms, but I am not holding my breath for that. I will probably be on my next Android phone before I will bother. Modding it up with Widgetlocker, ADW Launcher, and some other goodies at the moment to tide me over.
I had this same problem today. USB mass storage wasn't working, adb wasn't working. I wasn't using the samsung cable, but I can't see how that would make a difference, as the cable I was using has worked for literally a couple dozen different phones from different manufacturers - including other samsungs. I had the samsung drivers installed.
The owner claims that only media sync works on his computer as well, and that usb mass storage has never worked. Anyone have any ideas on how to fix this?
i am also getting this problem. as far as i know i am still using the samsung cable, as normal micro-usb cables dont fit in the continuums port. ill look for another one, but this is quite odd. what i have done (all windows 7 64 bit):
drivers uninstalled
drivers installed
lagfix on
lag fix off
factory reset (within adrenalyne's rom)
i am going to try to transfer the stock rom via bluetooth and see if that works
edit: turns out that isnt possible without odi recognizing the device, which it doesnt (not even in download mode). this is very peculiar
some more information: nothing even shows up in device manager. no unknown devices, nothing. the phone charges, but thats it. i might go to the verizon store and see if i can get another cable
My guess is because you are using a 64 bit version of windows..
Sent from my SCH-I400 using XDA App
I use win7 x64 with odin3v1.3 and it always detects.... I have odin on pc screen with files loaded then I pull bat hold the DownVol button and plug in usb
EDIT: I also have 'galaxy s x64 drivers'...I found em on net sumwhere?
Sent from my SCH-I400 using XDA Premium App
jaizero said:
My guess is because you are using a 64 bit version of windows..
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
Why would that matter at all?
The 64bit version of Windows 7 is notorious for not being compatible with a lot of devices. There just arent any 64bit drivers. If you dont understand how to run your software in the proper compatibility mode you will run into problems. I used the x64 version of Win7 for about 12 seconds after I realized my ancient usb optical mouse didnt work lol.
My advice, try running the Samsung driver installer in compatibility mode and see if that doesnt help.
jaizero said:
My advice, try running the Samsung driver installer in compatibility mode and see if that doesnt help.
Click to expand...
Click to collapse
Compatibility mode won't do anything in the case of drivers. I'm not sure what your issue is though as all of my Samsung phones have been picked up fine from within Windows 7 x64. Is the phone picked up on any non-Windows 7 computer? Have you checked in Device Manager to see if it just needs installed?
its the cable. i took mine to the verizon store, they tested it, and gave me a new one for free. works perfectly now
Excellent, problem solved!
So it turns out a factory reset fixed it. Using a moto cable. So that's definitely not the issue. Flashing froyo now. Thanks!
I have encountered that a few times also. Its weird cuz when I plugged the usb into ac charger it almost immediately asks if I want to mount sd for data transfer. 20 mins later I unplug usb from unit and plugit into my win7 pc and nothin? So plugged back into ac unit and it recognize....so I mounted and it didn't know what to do lol. I then plugged back intopc...waited...changed orientation and 'Boom' pc sees it...in fact I change orientation whenever it seems to hang and seems to work....
sent from my XDA phone - its more than a continuum
I should also note that I have never used a samsung cable and every usb micro I've used (moto,kodak,BB,Lg) has fit and worked. But I have noticed some usb related quirks since froyo update like no lock screen after charging till I push home button, inaccurate batt icon (goes from 3/4 to 1/4 in like 10 mins but overall batt life is same as before)...
On an unrelated note I also can't get v6supercharger to work...?
sent from my XDA phone - its more than a continuum
Has anyone been able to connect to the Kin using the Windows Mobile Device Center? (most likely not--I haven't seen anyone posting about it...)
I came across a website with a bunch of tools that look pretty useful for WinCE devices:
http://itsme.home.xs4all.nl/projects/xda/tools.html
It seems that these tools will only work though if the phone can be seen by the windows mobile device center (with its associated rapi.dll driver).
If there is a way to make the windows mobile device center "see" the kin, then maybe we give some of these tools a test drive.... I'm guessing it's a matter of having the correct driver (which seems to be somewhat of a problem )
I've thought about trying it, however my Win 7 x64 computer seems unable to install or uninstall the Windows Mobile Device center. Once I figure it out, or get a computer that can run it, I'll test it. And Activesync (for the older OSs)
On my laptop (have Zune installed on here) I have Win XP, so had to install ActiveSync 4.5. Unfortunately, after plugging in the phone, ActiveSync could not detect my phone. Not sure if having Zune on my laptop makes any difference or not.
Will install Windows Mobile Device Center 6.1 on my Win 7 desktop (no Zune) sometime tonight and see if the phone is detected there.
This is my first post, but I have been reading every single post since I got the phone around three months ago. I didn't feel the need to post because you all know way more than I do, but I think I may have made a discovery that might help your WMDC idea. If you are to turn on both the PPRO and usb_pass thru modes at the same time on the Kin device it creates an entirely new usb mode labeled "usbfn composite driver." which from my quick research I just did is the mode needed for the WMDC. I'll let you pros test it some more, but I'll keep messing around and see if I can get something. Hope it helps in anyway. If not sorry for wasting everyone's time.
kintwofan said:
This is my first post, but I have been reading every single post since I got the phone around three months ago. I didn't feel the need to post because you all know way more than I do, but I think I may have made a discovery that might help your WMDC idea. If you are to turn on both the PPRO and usb_pass thru modes at the same time on the Kin device it creates an entirely new usb mode labeled "usbfn composite driver." which from my quick research I just did is the mode needed for the WMDC. I'll let you pros test it some more, but I'll keep messing around and see if I can get something. Hope it helps in anyway. If not sorry for wasting everyone's time.
Click to expand...
Click to collapse
At least you've been reading. We're aware of the mode, and my limited trials do not let my computer recognise it, but I'm interesting in your research as to which mode is needed by WMDC. Where did you find that out?
http://forum.xda-developers.com/showthread.php?t=405945 here says that usbfn is for wmdc
also micrsoft talks about this mode here http://msdn.microsoft.com/en-us/library/gg159468.aspx
finally do a google search it seems that we have to make a driver to make it work, but there are a lot of templates out there.
Like i said maybe it will help and maybe not. Sorry.
I tested it.
Created a custom made driver in XP ("Kin Lame driver" from "LameCorp by Kussack")for device:
VID 0x045e, PID 0x643, MI_00
Activesync doesnt trigger on the phone in composite mode
Usb sniff shows that when the program talks to the phone, the phone doesnt answer (even not an error code or something).
Dunno about WMDC and/or the "other", the MI_01 device.
johnkussack said:
I tested it.
Created a custom made driver in XP ("Kin Lame driver" from "LameCorp by Kussack")for device:
VID 0x045e, PID 0x643, MI_00
Activesync doesnt trigger on the phone in composite mode
Usb sniff shows that when the program talks to the phone, the phone doesnt answer (even not an error code or something).
Dunno about WMDC and/or the "other", the MI_01 device.
Click to expand...
Click to collapse
How did you create the custom driver? Was it completely built from scratch, or an existing MS driver?
I spent a couple hours last night trying to fake a WMDC driver into driving my Kin, but was unable to. The closest I got was in using the "Pink" driver found in another thread here, but I couldn't do anything with it.
I still want to try getting a different driver to work (I have a Palm Treo Pro/WM 6.1 phone that I want to test, to see what driver it uses and how it works on the computer). If you've already done similar work, it might not be worth my duplicating your efforts, but if I can go about it differently, I'm still going to try.
you just need to add a pattern in wceusbsh.inf, following the existing ones.
It's like not exactly, putting it from memory:
%\USB&VID=0x045E&PID=0x643&MI_00%.DeviceDesc = \USB&VID=0x045E&PID=0x643&MI_00
And later in the file:
\USB&VID=0x045E&PID=0x643&MI_00.DeviceDesc = "Lame kin driver mfker!"
It's just pasting and customizing two lines (like i posted) and it will be labeled as "Windows CE devices" (even not working or being hacked in a wrong file).
I did this with all driver modes, just for fun. Nothing worked, but may worth a try with newer drivers or OS or pc's.
So I got this phone about a week and a half ago cuz my lg g4 bootlooped and I didn't care to fix it. I was excited to be able to root this as my g4 was an unrootable variant, but I can't seem to connect this to my computer for adb access.
Windows device manager doesn't see a USB connection.
I've used multiple ports and computers, all running various windows installs
My phone doesn't see a USB connection, nor does it popup where to change the USB protocol.
I've tried multiple cables, only exception is I dont have a strict USB 3 cable for a computer connection.
I have USB debugging enabled and oem unlocking enabled.
I'm on a family vacation currently but when I get back I'm going to try a Linux install to see if I can get a connection on that. If anyone has any tips Id love them, Google tech support just gave me the page I found on my first Google search. XD and I apologise if this is hard to read, I'm a bit flustered as I don't have much money to buy a new phone with and I'd really like to get this working. Cheers.
Hello All,
I'm new to this forum, so I'm not really sure if this should be general, dev, or just a technical question. Also I'm a software dev, but am not too familiar with android other than lightly using Android Studio for app dev.
Basically my problem comes down to this. I use a custom OpenWrt device as an ethernet dongle for my laptops by loading the g_ether driver. I would like to do this for an android phone as well. Right now I'm trying the s20 and s22 (pretty sure whatever solution I come to will work for both); however, when I plug my dongle in, the phone will see the dongle with all the correct device descriptors and all that, but will not connect and attempt to get an IP.
My current guess is that the phone just doesn't have the right drivers on there (cdc_ether or cdc_subset), or that it is not loading them.
Thus far I've tried poking around with termux, but have not gotten too far. I was hoping this community may be able to help me figure out how to get the phone to use the dongle.
Lastly, would really rather not root the phone unless completely necessary.
Thank you all for any advice!