Hello all,
I have a Samsung galaxy S II purchased in Israel from Cellcom.
In my ill advised attempt to unbrand, and thus accelerate, improve memory and battery consumption, I flashed a stock ROM which I believed to be the latest.
The phone works great, with one exception. There seems to be no way to connect it to PC, be it WIN7 32bit or ubuntu 32bit. original usb cable or other cable, my stationary workstation or my laptop, be it USB Storage mode, USB Debugging, that stupid Kies mode, and most importantly because i'd like to flush it back, no Odin Mode. (in win32 - any mode gets "unknown device" status like the device doesn't publish it's name correctly or similar.)
moments before the flash the phone connected in all modes.
I think i've pretty much covered all of the obvious. and there is no problem with my latest sdk and drivers as my Nexus S still connects to both PC's with great success.
SO some info - and what I have already researched.
from http://forum.xda-developers.com/showthread.php?t=1113928, I gather that the PDA on my Cellcome bought SGS2 is either JIKG3 or JIKJ1. and that it's a GT19100T and I gather that denotes some kind of hardware specification.
the ROM I've flushed to my phone has this name:
GT-I9100_XEU_I9100XWKJ3_I9100XEUKH2_I9100XXKI3.tar.md5
everything seems wrong about this ROM in hindsight but, the worst is that it has no T, and probably isn't very hardware compatible. (though the telephony, wifi, camera, sensors and anything I tried works).
The phone is not rooted as after flushing I have lost any USB connectivity. I therefore cannot try and manipulate system files, to try to recover that way.
I have tried to root with the exploit apk. to no effect. I gather it's a statistically challenged way of rooting so I'll try my luck a lot more during the wait for your answer, and report any success.
**Edited**
the "Easy Rooting Toolkit" on http://forum.xda-developers.com/showthread.php?t=1319653
I'll try to run it as best I can, with the shell emulator, instead of on adb, but with debugging enabled.. although it's not a very East Toolkit, when I use it this way..
I'll still report any progress..
**/Edited**
I have seen no one on the internet with this problem. it's really a very stupid problem to have. but a problem nevertheless.
Any insight as to the moves I can try next will be greatly appreciated.
Any information I can add with my limited usb connectivity will be gladly shared. (my "Kies air" works so I can upload to storage that way.. plus i have a shell emulator installed..)
Regards,
Alex.
In ur Device Manager dose it show several unknown devices when connected?
teenvista said:
In ur Device Manager dose it show several unknown devices when connected?
Click to expand...
Click to collapse
just the single one.
There is absolutely nothing wrong with the ROM itself as I have been using it on my phone for a couple weeks now.
The problem exists between your phone and your PC, the PC is stating that it's an unknown device after all.
What I would try is to un-install the device in Device Manager, unplug the device and restart the PC and then plug the phone in again, if that does not work, I would throw in a factory reset of the device itself while repeating the above steps
I think i've pretty much covered all of the obvious. and there is no problem with my latest sdk and drivers as my Nexus S still connects to both PC's with great success.
Click to expand...
Click to collapse
What do you mean by that? The nexus drivers have nothing to do with the galaxy drivers. Only if you run an AOSP rom you will need those drivers. Not if you run a stock rom.
Am I right that your pc sees the phone, but does not recognize it? Did you try reinstalling kies? And then from within kies tried to reinstall the phone drivers?
your PC may not recognize the device after the radio or kernel is changed. what I did was uninstall every single usb device from device manager and reboot, fixed.
Reply to all
jamesyb0i said:
your PC may not recognize the device after the radio or kernel is changed. what I did was uninstall every single usb device from device manager and reboot, fixed.
Click to expand...
Click to collapse
jamesyb0i - I saw that some people have been successful after uninstalling all usb devices, I'm challenged in this task as my keyboard and mouse are USB. I will try it on my laptop as soon as I'll get access to it, though because of the wide range of computer and OS I've tried I'm pretty sure the effort will be ultimately futile.
Lennyz1988 said:
What do you mean by that? The nexus drivers have nothing to do with the galaxy drivers. Only if you run an AOSP rom you will need those drivers. Not if you run a stock rom.
Am I right that your pc sees the phone, but does not recognize it? Did you try reinstalling kies? And then from within kies tried to reinstall the phone drivers?
Click to expand...
Click to collapse
Lennyz1988 - I see your point about the ADB Driver for the Nexus S, but as for the other advice.
As I said, I extensively tried to run it on multiple PC's multiple OS's.
I did try to uninstall / reinstall kies, and kies drivers.
after that didn't help. I got an SGS2 from a friend, just to try it on my computer.
it worked just fine.
achillies400 said:
There is absolutely nothing wrong with the ROM itself as I have been using it on my phone for a couple weeks now.
The problem exists between your phone and your PC, the PC is stating that it's an unknown device after all.
What I would try is to un-install the device in Device Manager, unplug the device and restart the PC and then plug the phone in again, if that does not work, I would throw in a factory reset of the device itself while repeating the above steps
Click to expand...
Click to collapse
The problem I believe is specifically because of the GTI9100/GTI19100T differences
I'm sure as achillies400 said that there is nothing wrong with the ROM itself. BUT the problem is not with my PC's it is more likely the different hardware, and the hardware driver on the phone itself that makes my phone become an "unknown device".
Regards,
Alex.
You could try this exploit.
http://forum.xda-developers.com/showthread.php?t=1296916
Don't know if it will work for you but it's worth a try.
Extract the .zip to /data/local/ on your phone and run the commands.
alex.feigin said:
Hello all,
I have a Samsung galaxy S II purchased in Israel from Cellcom.
In my ill advised attempt to unbrand, and thus accelerate, improve memory and battery consumption, I flashed a stock ROM which I believed to be the latest.
The phone works great, with one exception. There seems to be no way to connect it to PC, be it WIN7 32bit or ubuntu 32bit. original usb cable or other cable, my stationary workstation or my laptop, be it USB Storage mode, USB Debugging, that stupid Kies mode, and most importantly because i'd like to flush it back, no Odin Mode. (in win32 - any mode gets "unknown device" status like the device doesn't publish it's name correctly or similar.)
moments before the flash the phone connected in all modes.
I think i've pretty much covered all of the obvious. and there is no problem with my latest sdk and drivers as my Nexus S still connects to both PC's with great success.
SO some info - and what I have already researched.
from http://forum.xda-developers.com/showthread.php?t=1113928, I gather that the PDA on my Cellcome bought SGS2 is either JIKG3 or JIKJ1. and that it's a GT19100T and I gather that denotes some kind of hardware specification.
the ROM I've flushed to my phone has this name:
GT-I9100_XEU_I9100XWKJ3_I9100XEUKH2_I9100XXKI3.tar.md5
everything seems wrong about this ROM in hindsight but, the worst is that it has no T, and probably isn't very hardware compatible. (though the telephony, wifi, camera, sensors and anything I tried works).
The phone is not rooted as after flushing I have lost any USB connectivity. I therefore cannot try and manipulate system files, to try to recover that way.
I have tried to root with the exploit apk. to no effect. I gather it's a statistically challenged way of rooting so I'll try my luck a lot more during the wait for your answer, and report any success.
**Edited**
the "Easy Rooting Toolkit" on http://forum.xda-developers.com/showthread.php?t=1319653
I'll try to run it as best I can, with the shell emulator, instead of on adb, but with debugging enabled.. although it's not a very East Toolkit, when I use it this way..
I'll still report any progress..
**/Edited**
I have seen no one on the internet with this problem. it's really a very stupid problem to have. but a problem nevertheless.
Any insight as to the moves I can try next will be greatly appreciated.
Any information I can add with my limited usb connectivity will be gladly shared. (my "Kies air" works so I can upload to storage that way.. plus i have a shell emulator installed..)
Regards,
Alex.
Click to expand...
Click to collapse
!!!!!!!!!!!!!!!
I have the same problem, and I couldn't find anyone else w/ it or with answers either.
almost all the same scenario except I have an SGSII AT&T I777 that started out as UCKJ1 and is now UCKH7
My phone started coming up as unknown device. I can not find any remedy to the solution.
Here's my scenario: http://forum.xda-developers.com/showthread.php?t=1372171
My guess is I might try to uninstall "new" programs that I added to the phone and PC, uninstall kies etc. and drivers, and maybe try and do a restore or refresh or something on my phone and see if I can get to "scratch" and re-start from there.
I installed winamp on phone and reinstalled it on PC for wifi, and it kept mounting/unmounting my SD card from phone to computer each time I plugged it in (I think that messed with my card possibly giving it "unknown")
Or also when I changed my Kernel may have made the phone unknown. Those are the only 2 changes I can assume did this to my phone =/
any update on your phone?
UPD: My kernel was causing all my problems. Restored to an earlier backup and it had older kernel. All problems were relieved.
Related
So I had my phone rooted, and removed some of the ATT apps using instructions from here: http://androidforums.com/samsung-captivate/124736-t-bloatware-getting-your-way-delete-some.html
After doing all this, the phone still worked fine, but as of today I can't seem to connect via USB. ADB doesn't see the phone, and even if I disable USB debugging and attempt to just connect as mass storage, the drives don't show up in my computer like they used to.
I attempted a windows rollback to just before I installed the drivers, then reconnected the phone, but I did not get any message about unknown devices, and the phone doesn't seem to be in my device manager.
Can anyone help me out here?
Edit: Running Windows 7 x64
you erased something you werent supposed to. dl the dump posted here & move it to an Micro SD. Put it in your phone and use a program to move it from external to internal memory then load back all the apps you deleted.
If I had deleted something, shouldn't USB connectivity have died right after I did that, and not after a night of doing nothing with the phone?
Either way, How exactly would I go about restoring from that stock dump that was posted?
Mine is doing the same thing. Had a hard time with the windows 7 drivers to begin with though.
I am going back to XP when I get home. Will see if it will recognize it then.
Sent from my SAMSUNG-SGH-I897 using XDA App
Hm, an update on my situation: 3g watchdog died on me a couple times (gave me the popup, asked me to force close), so I decided to reboot the phone, and now everything works like it used to. I had also restarted my PC since the last time I tried (and failed) to connect over USB.
So if anyone else is having similar problems, I guess try rebooting both the phone and your computer.
I'm going to be keeping a copy of that "Rooted Stock System Restore" update.zip on my phone from now on, just in case.
The first Captivate I got from AT&T did the exact same thing right out of the box. I actually had to return it for another unit. Hopefully that was just a freak thing though.
I had a similar issue with windows 7 when I was first trying to connect via usb. Not sure if this will work for you, but I had to plug it into my rear port, the front ones didn't work just for the captivate.
Sent from my SAMSUNG-SGH-I897 using XDA App
it seems im having the same probs too i removed the att stock apps that were in one of the posts, im downloading samsung kies atm to see if that will help...
Edit, it did...windows and ADB redetected it.
I also rooted my Captivate and removed all of the AT&T crap. USB connection is still working fine under Windows 7 x64. Didn't install Kies or drivers either.
Halleleujah!
I had the same problem. Got this file from Samsung, and it worked on my Win7Ultimate 64 bit machine.
Try making sure you are back to touch wiz and see if it works... Worked for me.
I had some issues trying to get my phone to connect also ...
Windows Vista64 Ult.
Initially the MTP driver would hang when the phone was connected, and then eventually it would indicate that the installation was successful, then it would re-install itself after about 5 minutes. This was an endless loop which was severely draining of my system resources causing other applications to hang as well. I removed the drivers and ...
I downloaded the USB drivers from Samsung and installed them, when I connected the phone the computer did not recognize it, nor did the display on the phone indicate that it was plugged in. I tried several different USB ports.
I then changed the mode to mass storage and the phone was recognized, but both the internal and my secondary memory cards displayed 0 bytes free of 0 bytes available.
I downloaded the UK version of Kies, this was an utter waste of time. The Kies utility was not able to connect to the phone at all. I mass storage mode Kies displays an alert that it is not compatible, and the same goes for media player mode. If left in Kies mode the phone displays "connected", but the Kies utility just displays "connecting" and never progresses. Uninstalled Kies, and re-installed the Samsung driver ...
Connected the phone in Media Player mode, which is allowing me to access both memory locations without difficulty. Though windows pisses me off every time I connect the phone because it wants to sync windows media center with the phone ... though this is easily ignored.
Has anyone gotten the Kies utility to work with the captivate?
Battlehymn said:
I downloaded the UK version of Kies, this was an utter waste of time. [...]
Has anyone gotten the Kies utility to work with the captivate?
Click to expand...
Click to collapse
Try the Canada version, that's been working great for me, in Kies mode and all.
I had the similar kind of issue, look for the thread with ODIN and windows drivers, that is what worked for me...
After half an hour trying I have just found a working solution how to connect your SGS in Kies. Here is the deal:
Start Kies, put phone's USB settings in Kies mode. Connect your phone to the PC. Wait until MTP App show "Connected". Go to your PC's Device manager, find Portable Devices and select Disable on GT-I9000. Do not wait for the disabling process to be completed, just disconnect the USB cable. Now connect the USB cable again, wait the MTP App on the phone to show you the message "Connected" and choose Enable on GT-I9000 in Device Manager. After a few seconds your phone should be ready in Kies
I tried this both on x86 and x64 Windows 7 and it works for me.
I hope this will help! And I hope there isn't another thread with this solution. If there is - I'm sorry
i cant wait to get home and try this... another 10h to go
but if this helps ur a geniues
celeronix said:
After half an hour trying I have just found a working solution how to connect your SGS in Kies. Here is the deal:
Start Kies, put phone's USB settings in Kies mode , go to your PC's Device manager, find Portable Devices and select Disable on GT-I9000. Do not wait for the disabling process to be completed, just disconnect the USB cable. Now connect the USB cable again and choose Enable on GT-I9000 in Device Manager. After a few seconds your phone should be ready in Kies
I hope this will help! And I hope there isn't another thread with this solution. If there is - I'm sorry
Click to expand...
Click to collapse
Will put this in the FAQ if we have some confirmations for its effectiveness
when i first bought my phone it worked with kies, but after flashing it to a different firmware there was nothing i could do to get it to connect. i had deleted drivers, re-installed, etc etc but nothing worked. what ended up working was putting the phone in download mode, plugging in the usb to both phone and pc, then putting the phone into recovery mode, and as soon as the recovery menu popped up my device was recognized and the correct drivers were reinstalled and all was fine again
hondaguy said:
when i first bought my phone it worked with kies, but after flashing it to a different firmware there was nothing i could do to get it to connect. i had deleted drivers, re-installed, etc etc but nothing worked. what ended up working was putting the phone in download mode, plugging in the usb to both phone and pc, then putting the phone into recovery mode, and as soon as the recovery menu popped up my device was recognized and the correct drivers were reinstalled and all was fine again
Click to expand...
Click to collapse
If you still have this problem, please try my method and tell me if it works
I had issues and I also tried this method. But it didn't help
Last thing I tried was to format the internal SD. That did the trick for me....
The biggest problem with getting the phone to connect to Kies is two fold:
1) MTP application will ONLY launch from the home screen (touchwiz screen). NOT from any app. drawer / launcher screen
2) If USB mode on the phone is set to Ask on Connection, MTP won't launch due to the USB app. being open (see 1) above)
If you set USB to Kies mode and then ensure you are on the home screen of the phone with nothing else running, Kies WILL connect
Also remember the 16+ size extension bug.
So a full wipe on ur I internal sd card is a good solution just make sure u back it up tour hdd
I also did a "Driver recovery" from Kies and it worked after that. Although MTP driver failed to install for me in this case.
Make sure to update to the latest version of Kies ( Now 1.5.1.0074.45 ) as this version seems far more reliable when connecting the phone
I recently discovered that the culprit of Kies continuously trying to connect to phone was caused by wrong MTP driver selected.
Under WinXP
After phone connected in Kies Mode..Go to Device Manager/Portable device..
If you see a device labeled as "MTP xxx or Portable device.." ,wrong MTP driver or older driver has been used..For my case, a Microsoft 2004 MTP driver was selected.
To fix it.
1) Do a manual driver update..for my case ,i let the driver wizard to search automatically..this round, another newer Microsoft driver was found..in fact 2 of them.. after installing the drivers(Microsoft 2006 MTP driver,2 are listed..). .Now Device Manager/Portable device listed "GT-i9000" ,Kies immediately found my phone.
Driver name that worked are "wpdusb.sys" and "wudfrd.sys" found under \windows\System32\drivers\..
celeronix said:
If you still have this problem, please try my method and tell me if it works
Click to expand...
Click to collapse
You must not understand English. The entire reason I posted a comment was to share how I overcame this issue, so that would mean I no longer have this issue
Probable Fix for Kies
Friends,
I have also faced the same problem (while connecting my SGS via Kies MTP was crashing). It used to work earlier so I started to remove Applications and data in the reverse order of Installation. After I removed "Dolphin Browser HD" and all saved bookmarks it started working.
This may be a probable solution if you also have Installed Dolphin Browser.
~Gaurav
India.
2 different issues.
MTP crashing on phone is independent from Kies on PC cant detect phone.
i couldnt use kies either but i wasnt worried as i hardly have free time now..
this was a simple fix and now it workes perfectly for me.
sorry about the late replay.
thanks
I'm glad that it works for you
try this
try #9 on
http://forum.xda-developers.com/showthread.php?p=8046872#post8046872
You might be interested in my little APK (SGS Toolbox). I first created it to have it read the product code from the nv_data file to allow you to check whether it has been modified after a firmware update. But now I added some extra options, of which one is the option to check whether there are new firmware updates available in KIES by issuing the same request KIES does when checking for new firmware. This way you don't have to connect your phone to your computer all the time to check for new updates in KIES. Note: It sends JM1 as the current firmware version to find the latest. I might send the actual phone's firmware version once I figured out how to find it. See: http://forum.xda-developers.com/showthread.php?t=778244
Thanks, I'll give it a try
Deleted. Wrong thread.
Ever since I rooted I can not get my Epic to connect to a computer period. I'm about to give up and just deal with what I got, hopefully someone can tell me what I'm doing wrong. Before anyone decides to be a smart ass I have used the search function literally for days and have tried tons of things recommended with no result. I am the first to admit I'm an idiot when it comes to anything involving computers but I'm pretty determained to learn.
This has to be the phone because I have tried to connect to 2 desktops (1 running Windows 00 and 1 running the most updated Ubuntu), and 3 laptops (Windows xp, Windows Vista and Ubuntu). When I rooted I used the Vista computer and connected fine (can't anymore). I didn't have the space on the C drive to install the Android SDK so I switched to Ubuntu (first time user btw lol). Somehow when I was backing my SD card I lost any access to it or the notification bar. I never got my SD back til I rebooted but I haven't been able to connect to any PC since. When I charge (even in the car) it always tries to stay in mass storage mode. I basically charge in my car with my phone off hoping it will just charge and not mount my sd card to my car or wall lol. Yes I wiped 3 times, partitioned sd, tried several different cables (but my husband used mine and no problems on his Motorola) I'm sure I've done something wrong when I rooted or mounted to Ubuntu.
I also can't use adb. I followed the directions to the t (a few times lol) but when I run any commands it says "no such file or directory" I didn't have adb on the windows pc when I di noobnl's one click so I never ran the (adb shell ect) commands. I now can't do jack. I am now running noobnl's DI18 ROM with modem.bin flashed thru Clockworkmod.
I have tried all the basics you will find wit 2 days of web search.
My goal is DK28 (dream on Erica lol)...Thanks for any help and for anyone sparing me a lashing ;-)
Sent from my SPH-D700 using Tapatalk
When you plug in on your windows pcs...in Device manager..do you see anything appear? also do you have USB debugging on the phone?
USB debugging on?
Have you tried reinstalling the drivers for the Epic?
Rebooted phone and PC? (Sometimes it helps)
Used Odin?
Something might have been screwed up during one of your downloads, bad file maybe. Try reinstalling your drivers first, use Odin (phone must be in download mode), and see if it recognizes te device. If it does then Odin the stock .tar file and go from there. It'll give you a fresh start.
That's all I can think of right now.
Sent from my SPH-D700 using XDA App
I bet your USB debugging is on since most root's requier it. Even tho it says connect to pc if usb debugging is on it wont connect to my windows 7 box
I would suggest, if you're really having this many issues, just boot into download mode (1 on the keyboard + power button) and odin back to di18.
Just for kicks have you tried Settings > Privacy > Factory data reset? I assume that wiping does the same thing if not more but it's worth it to see if it somehow resets a setting that might be the issue.
What's left - software issue or Hardware issue.
Software:
hmmm...yeah gotta try connecting through Odin which uses downloader mode instead of USB modes...
Can Odin see your phone? Run Odin as admin with antivirus off, and proper samsung drivers installed. Then boot phone holding down 1 key into downloader mode. Connect to computer through USB port on back of computer (i.e. directly to motherboard) - does Odin identify something attached to USB port?
Yes - flash the dk28!
No - with Odin still on, unplug the USB cable, pause, and reconnect it. Still No? Try a different USB port on computer. Also try uninstalling and reinstalling the drivers - be sure to reboot the PC. If still No, then try on another computer, and as you did before, try different cables. Still No?? --> hardware problem with phone.
Hardware problem with phone: Look at the usb port in the phone - is there any junk in there that might interefere with the connection?
Yes - clean it out
No: phone perhaps internally damaged:
Solution for hardware damage:
You and husband clean up and go to sprint store.
At store - tech will know phone is rooted, so:
--Tech more likely to like you? You handle it, maybe even blame husband. Husband can silently attend and look sheepish, playing the part of 'me man, me dominate environment, me break fancy tech of wife, me sorry." Try to get free replacement phone while simultaneously promising never to let your husband root the phone again, or even touch it.
--Tech more likely to like husband? He goes alone, cops to the true story of how you rooted it and then was backing stuff up when it suddenly stopped working [truth from men? so sincere!]. Try to get free replacement phone while simultaneously promising not to let you in the house should you even attempt to root again.
P.S. forgot to add you might turn off the PCs firewall while testing, as well.
quik99 said:
I bet your USB debugging is on since most root's requier it. Even tho it says connect to pc if usb debugging is on it wont connect to my windows 7 box
Click to expand...
Click to collapse
same here. I tried out the free tethering app the other day and with usb debugging on i coudl never get it to install the proper drivers. Without it on and the 64bit drivers installed Odin worked just fine.
I have seen many Galaxy S devices not connect to a computer because of a faulty USB cable. Had my girlfriends sister switch out 3 Vibrants only to accidentally try and connect it to a laptop with a different USB cable and I've seen two others not connect with the stock Samsung USB cable.
How I fixed the tethering issue
I've had the same problem with my galaxy s - connecting to the PC (Win7 32bit) just doesn't do anything. As a test, I had a friend with the same phone/rom (froyo, rooted) connect - and he was able to! It installed the drivers and it just worked. He disconnected, I connected, and now it's fine.
So, see if you can find someone with the same phone and see if they can connect. Makes no sense to me, but it worked.
I've had my Epic fail to mount before. Interestingly any time I had an issue it was with a Mac - it always mounts on a PC. I'll stop now before I open up a can of worms.
Best advice I have is get a Dropbox account. You can use that guy to move files from a computer to the SD card without having to mount to the computer. Perhaps you can get a factory ROM (with root of course) on your phone that way?
You can get a app from the market called SWIFTP (free) & connect to your sdcard via ftp server. This can be a temporary fix till you get your connection error resolved.
I have 1 USB port on my laptop that the Epic shows up as "unknown device" on. Works on every other port, and everything else works just fine on the same port. The factory USB cable is finicky!
Just ran into a problem which took me some time to solve. Thought I would share it to save other people some frustration.
After an adb reboot the i5800 got stuck in "modem" mode. i.e. android booted fine but gave a modem and a serial port over usb rather than adb. Reboots did not solve the problem.
The solution is to enter recovery screen:
reboot recovery
OR
press proper buttons to get into recovery mode
And then perform a reboot from there
Is this the same as *#7284# and selecting "PDA" on UART and USB, or just on USB? Or is this a completely separate thing?
miki.antena said:
Is this the same as *#7284# and selecting "PDA" on UART and USB, or just on USB? Or is this a completely separate thing?
Click to expand...
Click to collapse
Thanks so much for this!!!! After helping hack a friends build.prop to enable Apparatus compatibility in the Market, I found USB wasn't working properly anymore. Resetting changes in the phone didn't help (I had to do this via the phone terminal) although I at least managed to buy Apparatus before the sale ended.
After initially getting confused due to a lack of drivers and the occasional 'nH' showing up devices without drivers which made me think something was borked, I worked out from the VID & PID it was just the lack of drivers making (well I'm not sure why it did the 'nH' sometimes it got serial something instead), once I installed the drivers all was fine.
Except still mass storage wasn't showing and the Samsung connect manager didn't show up on my phone when I connected USB, nor did ADB work at all. In fact, it didn't even show up in the phone menu as debugging mode if I didn't start phone with it connected (or something like that). Funnily enough when I did get it the debugging to show up I did get the USB mass storage to show up in the phone, but it didn't help (it just unmounted the card which I think is all it ever does).
Anyway after a bit more fooling around I eventuall came across http://forum.xda-developers.com/showthread.php?t=1215103 and the stuff about modem and mkasick's post which sounded a lot like it could be my problem. The code for that Samsung phone didn't work so I searched for the 5800 and came across this giving me the right code. Sure enough UART (but not USB) was set to modem instead of PDA. I was unsure whether that was wrong but changed it anyway and yep that fixed it!
I still have no idea what went wrong. I had thought may be the phone didn't like me rebooting via ADB but I've now done that several times. In fact most of the stuff except install a superuser update has been more or less repeated. I guess it was just some strange rare occurence that it somehow got changed. I did have to reconnect the USB while working the first time, not sure why but ADB lost connection then I found couldn't connect. Perhaps that's somehow related. Now that I know what to do, it's trivial but very annoying when I didn't. I still don't get why Samsung decided to make the connect manager (my phone doesn't have that) only to have some hidden option where it can be set to modem or USB.
Partially because of this, I never got to get Tilestorm HD become compatible in time for the sale although my friend wasn't so interested in that. (Eventually I worked out using the THC Tattoo modded market which reports a fake resolution enables it. Well, I also modified the build.prop but I don't know if that was necessary. I wasn't able to do it solely by the build.prop. But it was way too late by then to buy Tilestorm HD cheap.)
Nil Einne said:
I still have no idea what went wrong. I had thought may be the phone didn't like me rebooting via ADB but I've now done that several times.
Click to expand...
Click to collapse
This may sound like crazy idea, but is your USB port/connector clean?
(The USB port allows for dozens of different phone functions when using very specific resistance between data pins.)
i bought a LG D802 32gb last night as i was using a 16 gb before i wanted to flash cloudy g3.. so i tried to install custome recovery twrp...
now i am in fast boot mode..
it says :
[880]fastboot mode started
[910]udc_start()
when i attach usb cable
[1100]-reset-
[1110]-portchange-
[1120]-reset-
[1130]-portchange-
[1140]-fastboot: processing commands
i tried holding volume + and and attaching the usb cable but no luck ... so now i have NO RECOVERY, NO DOWNLOAD MODE, AND MY WINDOWS PICKING UP MY PHONE AS "USB MODEM PHONE ADB PORT"
please help
Hi, background is this..
I have a D802-10C G2 that i rooted the stock 4.2.2 rom a while back using the post chinese method. Easy enough, all worked fine. no complaints. A couple of weeks ago i got offered the OTA 4.4 update, this failed due to the root. I then removed the root using the feature in super su. that seems to have worked as no apps or file managers etc could get root access. However, the OTA still wont work.
Now my problem is my phone will no longer be recognized by any operating system, on multiple computers. I have tried many ADB drivers, Windows 7 wont even detect the device, i've used every PC connect mode, USB debugging. However always the same result, it's as if i'm plugging in a blank usb cable into the computer. Nothing at all.
The only thing that does happen when i connect the phone to a computer is the phone starts to trickle charge. There is nothing detected in Device Manager in Windows 7 I've tried connecting in download mode, nothing. I've tried the LG support tool, PC sync. Nothing.
WiFi does connect to the PC suite fine BTW and other than that the phone is working perfectly. I've also tried connecting multiple usb cables on multiple ports.
I haven't been able to find a single case of the same problem in the week or so i've been looking. Hoping someone can help, i'm thinking i may have soft bricked my phone. I really do not think this is a driver issue.
Any help would be great. cheers
Paul
+1
i have the same problem plz help
cambies said:
Hi, background is this..
I have a D802-10C G2 that i rooted the stock 4.2.2 rom a while back using the post chinese method. Easy enough, all worked fine. no complaints. A couple of weeks ago i got offered the OTA 4.4 update, this failed due to the root. I then removed the root using the feature in super su. that seems to have worked as no apps or file managers etc could get root access. However, the OTA still wont work.
Now my problem is my phone will no longer be recognized by any operating system, on multiple computers. I have tried many ADB drivers, Windows 7 wont even detect the device, i've used every PC connect mode, USB debugging. However always the same result, it's as if i'm plugging in a blank usb cable into the computer. Nothing at all.
The only thing that does happen when i connect the phone to a computer is the phone starts to trickle charge. There is nothing detected in Device Manager in Windows 7 I've tried connecting in download mode, nothing. I've tried the LG support tool, PC sync. Nothing.
WiFi does connect to the PC suite fine BTW and other than that the phone is working perfectly. I've also tried connecting multiple usb cables on multiple ports.
I haven't been able to find a single case of the same problem in the week or so i've been looking. Hoping someone can help, i'm thinking i may have soft bricked my phone. I really do not think this is a driver issue.
Any help would be great. cheers
Paul
Click to expand...
Click to collapse
YOu can try checking the device manager or use other USB port on your phone.
buenarc said:
YOu can try checking the device manager or use other USB port on your phone.
Click to expand...
Click to collapse
The problem is not like the usual ones you will see about "computer not being able to see device" I don't think it's a driver or software issue, or if it is it's unlike any i have found in the weeks i've been searching the net for a solution. Here's why....
When i connect the phone to Windows 7 and 8 ( on 3 different computers) No hardware is detected, nothing in the Device Manager, no yellow question marks indicating 'Unknown Hardware'. Nothing, all it does is start trickle charging.
Now even with no ADB, or any driver at all installed, the computer should still detect the phone. Mine does not.
The same thing happens using OSX and Linux Mint 16 (again multiple computers) No devices or mounted or volumes shown at all. Linux terminal command "$ lsusb" does not list my hardware.
This is why i'm pretty much convinced that there is something wrong with the USB port on the phone. Because, if Linux can't see it then surely it's a hardware problem right?
The only other thing i can think of is, i have messed up the phones firmware while trying to unroot it? but only because the timing of all this is just too uncanny.
I think i'll have to suck it up and admit defeat here. Funny thing is the phone works perfectly and charges fine.
Stuck on 4.2 , with no ADB functionality. Perhaps i'll sell it cheap to someone who doesn't care.
Cheers for the reply mate.
Same problem here!
Only my G2 is not rooted, it is still on factory OS and recently updated to 4.4.2.
I have tried on several computers, different ports and no help.
On the first connection to a PC not connected before windows reports "USB device not recognized" problem.
After that every time I connect the phone to the same computer the phone itself only recognizes that it is using USB charging mode, it does not recognize the computer connection (known by the USB ison on android system tray) even with "Ask upon connection option checked".
Even when I manualy change the Android mode in Settings --> PC Connection from MTP to PTP or even LG software, nothing happens.
Definetly there seems to be a problem with the phone, but I don't beleive it's a software but a firmware problem.
Please help if anyone knows what to do.
same thing happened after installing T-mobile rom thrugh twrp. but my device boots into fastboot and i tryed falshing :
laf.img, boot.img, aboot.img, recovery.img, laf.img
but after reboot my LS980 dissapear from device manager and stucked on LG logo.
Dont know what to do now.
I'm no expert, but given there are a lot of them here and none have weighed in on this with any ideas for a fix, i'm going to assume it's a hardware problem.
Anyone else agree? Hardware problem not software?
Cheers
I guess that you already wiped everything right? Apart from that, i'll suggest you to go to some tech supp and ask them if they can verify that each pin of the micro usb is properly working.
Sorry for my english, hope it helps!
Sent from my LG-D802 using XDA Free mobile app
I will try to check the connector although i dont think that it is a hardware issue.
BTW I can enter the download mode after flashing the mentioned partitions and i can also enter the stock LG recovery but when i do the factory reset it keeps showing Factory reset processing ... for ever
It has happened to me the same thing :crying:, and is a problem with the boot.img, if by chance your G2 version 4.4.2 and the the 4.2.2 boot.img, goodbye.
The only solution is to take it to repair a service official, there will change you the card, with the consequent change of IMEI.quent change of IMEI.
Homero2 said:
It has happened to me the same thing :crying:, and is a problem with the boot.img, if by chance your G2 version 4.4.2 and the the 4.2.2 boot.img, goodbye.
The only solution is to take it to repair a service official, there will change you the card, with the consequent change of IMEI.quent change of IMEI.
Click to expand...
Click to collapse
where are you going to repair your G2?
and how much have you paid the repair?
THANKS
Any fix for this guys i have same problem!
Here I'm getting the yellow !, any suggestion?
Sirs, I flashed the baseband (https://www.androidfilehost.com/?w=files&flid=12880) then it got working back.
solved for me
I have some kinds of that problem, let try:
Settings -> General -> PC Connection -> Select USB connection method -> Media device (MTP) (or whatever)
Got this same issue after flashing cloudy g3 rom. Then later flashing dirty unicorns, which requires jelly bean baseband. But even restoring g3 and 24a baseband, still doesn't work. No pc tethering and no on the go usb. My usb port is basically charge only.
---------- Post added at 03:58 PM ---------- Previous post was at 03:56 PM ----------
Everything else works fine...I actually never even noticed this bc I never tether to pc. But now I have to bc I want flask kdz
Help me please
someone have a solution to this problem?
My Lg G2 D803 still on boot loop (LG logo) and thats all ... no usb connection , reset factory doesnt work ...
HELP PLEASE ...
Thank you
Anyone has an idea how to fix this problem?
same problem
I have a LG G2 . recently updated from vs98027a to vs98039a 5.0 lollipop. Since the update my computer won't recognize my device in download mode and I don't have superuser ppermissions. Help plz
I also have the same problem.
It happened when I tried to backup info through LG PC Suite: the phone disconnected during the process, and now it's not recognized by any PC (http://forum.xda-developers.com/lg-g2/help/lg-g2-recognized-windows-backup-t3155323).
Also found a description of the same problem here: https://www.reddit.com/r/lgg2/comments/2urpnw/lg_g2_usb_only_charging_not_recognized_by_pc/ - no solutions, too.
Did anyone manage to fix this?