I've had my phone for over a year now without any problems, until now. I did four updates at once, and now I've lost the ability to connect the phone to my PC.
-Radio update from 5.08 to 5.12
-HBOOT updated to 0.35.0017 from I think .0012
-Cyanogen 6.0.0 RC3 to 6.1.1
-intersectRaven kernel update
In that order. Same usb cable, same port (although I've tried different ones).
Everything works as it should, except for the fact that I can't connect via USB. I've been reading random threads for several hours trying everything I can think of. I've downloaded the SDK and updated my drivers. I've been trying to get ADB to work, but my phone never shows up when I do "adb devices". Tried uninstalling, reinstalling drivers using various methods (usbdeview etc), no go. Yes, my USB debug is on.
I was thinking of reflashing Cyanogen and the kernel, but I really don't want to do a data wipe :\ I'm the type of person that will only ask as a last resort, but I'm out of options and I'm now banging my head against a wall in frustration...
Update:
So the problem appears to lie with intersectRaven's kernel.
Last night I reflashed CM 6.1.1 and just ran the stock CM kernel as a test, my usb connect option showed up.
Seeing as I could connect, I took the time to download a newer iR kernel and I flashed that. Tried the usb again and it wouldn't connect.
So I flashed CM again and my usb connected again. So it must be a problem with the way his kernel is interacting with CM on my phone.
Seeing as I haven't seen complaints on the iR kernel thread, it must be a problem localized with my phone. I might make a complaint on his thread, or I might just run the CM stock kernel until a release candidate arrives for CM7, which (hopefully) shouldn't be long.
Related
Hey guys I been having a huge problem with my Samsung Galaxy S 1900M its currently locked with Bell/Virgin Canada. I bought it off of some 2nd hand company. The phone was sold as is saying that it was unable to connect to the computer, (computer does not recognize it at ALL). I bought the phone amusing it was a ROM load problem. It came to me rooted and in almost perfect condition so I was quite happy with my purchase considering I paid $180 USD ($170 CAD). I tried connecting to the computer using the USB that came with the phone, and as stated it does not recognize it at all on ANY Windows/Linux base PCs. I also have another Samsung USB cable that I know works, I tired that as well...no success.
So I am assuming who ever loaded a ROM did not know what they were doing.So I have been searching all over the internet/google, XDA forums and Q&A and everyone point to loading a new kernal....BUT here is where it gets weird. Who ever had this phone previous did not flash a new kernal when updating and put the 3e recovery on the phone, WHICH MEANS I cannot flash any new: Kernals, OR ROMS using the CWM, which btw I am pretty sure isn't working properly because it goes into the base recovery mode with limited options, ex. reboot, sdcard update.zip, wipe cashe, format sdcard...nothing else.
Which brings us back to the original problem, I can not connect to the PC for ODIN to work its magic on the kernal....Please help....
Here is the current load,
Firmware Version: 2.2
Baseband: 19000UGJK4
Kernal Version: 2.6.32.9 shout.leeSEP-09 #1 ( I have never heard of this?)
Build: FROYO.UGJK4
may be a issue with drivers dont quote me though, i had to update drivers after flashing and updateing my galaxy s, as i had simular issue with odin, by not reconize, do you mean windows wont even detect the phone added, or is it connect and nothing? does the phone charge when connected to the pc ?
The phone does charge, but even with the Samsun Keis app, and having the proper Sumsung drivers it still wont even detect the phone. I even went to Device Manager and searched for new hardware/device. I also tried putting it into download mode, and connecting Odin. Windows still wont even detect it. I think its a problem with the kernal....for both issues...
Fixed the problem, hope this helps for others.
Just following up on this as I figured out what to do on my own in case anyone else has this issue.
It was quite simple actually, the kernal was faulty, and so was the ROM that was loaded just as I anticipated
1st:The person that previously owned the phone loaded FROYO custom build that was taken from a leaked version prior to the official release and had no USB support, therefore being unable to connect to the computer.
2nd: The kernal was a custom build and had a 3e recovery built into it and was not able to load any un-verified files(unofficial ROMS, firmwares, updates etc.), therefore I was not able to load a new ROM to fix the first problem, stated above, and visa versa.
I found a program on the market place called "kernal manager", I downloaded the PRO version by searching Google on the computer for the .apk file, I then copied the .apk file onto my external 2 GB SD card and ran the .apk file through the phone. I then opened "kernal manger pro" and opened the menu button, then hit search for kernals. A list of different models of phones came up, I browsed down to my handset maodel (Samsung Galaxy s 19000), press on it, and got a list of kernals. I took each top rated and downloaded kernal listed, did a little research on the internet and found one of them to be suitable. I then went back to the phone chose that kernal through "kernal manager", it asked me to flash then reboot, I hit yes, it then begun the process, and when finished reboot on its own. I then reboot into recovery again after the kernal had loaded and the first reboot and found that the new kernal had succsefully been flashed. I then was able to go about as I please. I uploaded a cm7.zip file to the external sd card, put it in the phone, boot to recovery browsed to the file, and ran it having complete success.
I am now happily running Cyanogen 7. Hope this helps anyone that needs it. Any questions just ask
Hello everybody,
First of all, from what I have seen yet awesome work with Fasty 2.5! Using it has been great, even though I only tried it for a short time.
Here's my problem:
Every time I insert the USB cable, after about five seconds the phone shuts down. All the way to the battery loading animation. And if I don't remove the USB cable, it'll restart that one every five seconds. Additionally, if I plug in the cable during boot, same stuff. Help?
Background:
I'm using a i9010, came from I9010XXKB2, freshly installed. After my first flash of Fasty I even rechecked if I didn't have the same problem with that original rom, but the problem does not happen there. Flashed Fasty 2.5 a second time - the usb plug crash was back. Went back to I9010XXKB2 and it's gone.
Tried different ROMs, namely dlev5 and Apex 9.3 - both work.
So, anybody got ideas? Thanks!
By the way, one idea, maybe it's because of the stock bootloader? Or does Fasty bring it's own? If I want to test that, what do I have to look for in terms of compatibility?
Update: Flashed Fasty 2.5 again, but this time added the SpeedMod kernel afterwards and voila, no more crashing. But somehow it feels less fast unfortunately. Does anybody know a Froyo kernel similar to the Fasty kernel, except for, well, no crashing?
EDIT: Ok, crashes occur with existz's KB1 kernel. Seems like Onix is a good alternative, only have to find a modem to go with then.
Ok, I was at the stock Froyo 2.2 update yesterday and saw 2.3.5 GB and installed using ODIN. There's a couple of aggravating features, mainly every time I plug in via usb or AC, the tethering process crashes. I don't even use tethering and don't know how to disable this process.
Anyways, all I want to do is return to the stock AT&T froyo. I've tried several one click packages for ODIN to return to stock, I CAN get into download mode, but once its plugged into the PC it says its installing device drivers, then it always fails. I tell Windows to search, and of course it can't find any.
How can I get this to work again, all I want is my 2.2 back
Read this thread
I am experiencing headphones detection problem with my Xperia Z1. Headphones are correctly detected first time after reboot. If I try to plug them in after that phone doesn't detect them any more (external speaker is used even after I've plugged them in).
I contacted Sony support and they suggested it might be Smart connect. I cleared it's cache. Didn't help. I disabled/removed it. Didn't help either. I downgraded to an older ROM (don't remember if it was 4.2 or 4.3) and it worked as expected. Then I downloaded fresh .ftf of latest rom. Same problem re-appeared. Tried with Kit Slim custom ROM (based on 4.4) and experienced same problem.
It is obviously a SW problem. Is there any app which would allow me to manually direct sound to either destination? I have SSH server running on my phone. Is there any way to do this via shell? Any API call that I could utilize? I have no experience with Android dev but I am SW engineer and I think I could implement a simple app like this if someone would point me in the right direction.
Thanks!
it's definitely something with smart connect. had the same issue some days ago...... unistalled smart connects updates and installed them again -> works!
Tried that already. Didn't help
I contacted Sony support again and they suggested to try PC Companion's repair feature. What will that do? How that relates to the fact I'm running a rooted custom kernel?
Thank you!
hm try to flash .157 with flashtool. after that flash trinity kernel via flashtool and fastboot -> should work like charm dont forger to save your data before that I did the same and it worked for me
Where could I download that?
Hey guys,
I tried flashing the November factory image, but my phone still says that it's on the stock (October) firmware version.
It's an unlocked, Google Store devices on Verizon. I flashed the QD1A.190821.014.C2 version (and it seemed succesful), but phone still says its on -.007. Rooted with Magisk prior to flashing but disabled all mods.
I tried to flash twice with the same results. Any idea? What am I missing?
well what did the flash log say it must have failed, update your platform-tools, change usb port on pc, change usb cable (or flip the usbC connection sometimes that works in a cable were one of the pins is bad), those things fix 99.9% of non syntax/user errors with fastboot flashes.
I also have Gstore version unlock and rooted no issues on update. Platform-Tools was updated since last release, that may have caused issue but not sure because i updated before the flash....
I had problems with the versions. I was on the .007 October version (bought unlocked from Google). Figured since I'm on T-Mobile, I'd flash the image that was for T-Mobile .014. Turned out it didn't take and it broke the Face Unlock. As soon as I flashed the .007.A3, it's working beautifully. Maybe since you were on .007 before (like me), try the .007.A3?
Well, I updated platform tools and flashed the C3 build and it worked like a charm. Not sure what the issue was, but one of those def fixed it!