Related
hello,i have several problems that are making me very angry.i use updated windows 7 32 bit.
1.i have samsung kies and my device was working normaly,but then today when i connected my phone to pc i got code 43 error device not recognized.i tryed reinstalling kies uninstalling drivers re installing nothing helps i cant even connect when i am in download mode same error.I NEED SOME ANSWERS ASAP COZ IT IS DRIVING ME CRAZY.
2.this one is bit smaller but also annoying,it was happening while usb connection was still working,when i connect my phone(any mode kies or mass storage),then when i copy files from pc to phone it working fine,but when i try to copy something from phone to pc i get random disconnects (connection loss) there is no logical explenation coz its totally random,lets say i copy 100 pics i get dc after 10 then i reconnect phone and click retry he copy 15 more and dc again.
Any1 will any solution plz help coz my phone is at mess atm and cant flash anything.
the source of the usb issue may be your computer.
1) did you always use the same usb port for your phone?
2) how old is your computer?
3) do you live in a humid environment?
I live on guam, and on my older laptop (only two years old!!!), running winxp, 3 of 4 usb ports are no longer usable due to corrosion. they give errors and even when working, sometimes I could lose the connection by moving the cable slightly. also, the last usb port is now getting difficult to use because it's hard to plug in anything
so, if you answered yes to #1, try another port and be prepared to install the drivers again.
if you answered yes to #3, be prepared to replace your usb if they are indeed corroded
well thnx for answer,but my pc is new like 7 months old,usb ports are working just switched mouse and phone mouse working phone not.its driver relater before i had that error and some1 from xda told me to delete everything(kies drivers) related to phone and his drivers and it worked i also see that error(code 43 is common) but fix with uninstalling driver(worked before now doesnt).thing is that something at that moment didnt work well on phone(last time it was my external sd card had to format it)and now pc keeps repeating same error.simply even tho all drivers are installed i get device not recognized,and under device manager it unknown device,also when i tick option to see hidden devices i see omap 3630 but state is unconnected.
xGiox said:
1.i have samsung kies and my device was working normaly,but then today when i conne.............
2.this one is bit smaller but also annoying,it was happening while usb connection was still working,....................
Click to expand...
Click to collapse
When transferring files to and from pc, do you use the original USB cable that came with the phone? Because when i use other cables, i have this issue, when i use the original cable, no probs at all.
if that also doesnt work, try formatting internal and external SD cards
xGiox said:
well thnx for answer,but my pc is new like 7 months old,usb ports are working just switched mouse and phone mouse working phone not.its driver relater before i had that error and some1 from xda told me to delete everything(kies drivers) related to phone and his drivers and it worked i also see that error(code 43 is common) but fix with uninstalling driver(worked before now doesnt).thing is that something at that moment didnt work well on phone(last time it was my external sd card had to format it)and now pc keeps repeating same error.simply even tho all drivers are installed i get device not recognized,and under device manager it unknown device,also when i tick option to see hidden devices i see omap 3630 but state is unconnected.
Click to expand...
Click to collapse
Jack_Random said:
When transferring files to and from pc, do you use the original USB cable that came with the phone? Because when i use other cables, i have this issue, when i use the original cable, no probs at all.
if that also doesnt work, try formatting internal and external SD cards
Click to expand...
Click to collapse
i use original cable and also i did format both external and internal cards several times my first problem is kinda more important atm.
ok i tried connecting my phone to secondary pc running xp gave me same error but simple uninstall of driver and reinstall made it work cant fix it on win 7.
Edit: damn phone wont connect when in download mode cant flash anything -.-.
Connect the phone and go to device manager
If you see the i9003 driver uninstall it then connect the phone to pc again
now windows 7 will download the driver automatically
that's how I fixed my problem
I originally posted this inside the Glorious Overdose V2 thread, but decided to post here as well.
For some reason my computer won't recognize my Sidekick when I plug it in via usb. I do have the samsung drivers installed and it will read my friends Samsung Droid Charge just fine, but when I plug my Sidekick in it comes up saying "USB Device Not Recognized". So far I've tried uninstalling and reinstalling the drivers from the device manager to no avail. Wondering if anyone has an idea as to what it could be. I've also tried googling the solution and everyone says to just uninstall and reinstall the drivers and it should work. Now the phone is not plugged into a USB Hub, extender, or case, it is plugged directly into a usb port on the mother board.
PC Specs just in case:
Motherboard - Gigabyte GA-970A-D3
OS - Windows 7 Ultimate x64
CPU - AMD FX-4100
Memory - 8GB DDR3 1066
Phone:
T-Mobile Sidekick 4G running Glorious Overdose V2
Nothing added just the rom and some apps/games.
I have tried with USB Debugging on and off, either way does not work.
Update: I have since tried Kies mini, as well as the drivers found on Softpedia. Neither of those worked, so I just got done reformatting and reinstalling Windows hoping that would work. At first it did not, right now I am running windows update to see if that was the issue, I'll update of what the outcome is.
Update: After installing all available Windows updates it's still not recognizing the phone. Now no matter what it's saying it's an Unknown Device. Even after I try and do a manual driver update and tell it to look in the folder with the driver files from Softpedia. I'm at a complete loss now.
If anyone has any idea's please let me know.
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Jax184 said:
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Click to expand...
Click to collapse
It's set to USB Debugging. But even then, it should read as something else other then Unknown Device when I plug it in. I have tried plugging it in and selecting Mass Storage, still comes up as Unknown Device.
HewettBR said:
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Click to expand...
Click to collapse
I've thought about that, and from everything I can see it's either the ROM or the drivers. So we'll see...I'll probably try a different ROM and see what happens.
I suggest turning USB debugging off and mass storage on, for how you'll be using it. And recall that you have to change this stuff with the USB cable unplugged.
I've tried that, and after talking with the T2 Technical Support from Samsung for 45min today, the only option left is to send the phone in to get worked on. Though, I'm going into the T-Mobile store and see if they can't replace the phone or give me a loner while this one is out getting repaired.
More info request.
Can you provide us with the names and links to the drivers you have tried?
DuctTapedGoat said:
Can you provide us with the names and links to the drivers you have tried?
Click to expand...
Click to collapse
Kies Mini - http://www.samsung.com/us/support/owners/product/SGH-T839HABTMB
Softpedia - http://drivers.softpedia.com/get/MOBILES/Samsung/SAMSUNG-USB-Driver-1480.shtml
As well as the Samsung Vibrant drivers from both of those sites.
Samsung SideKick 4G Drivers
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
DuctTapedGoat said:
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
Click to expand...
Click to collapse
Thank you, I tried unpacking them to a folder on C:\ went into Device Manager, right clicked on the Unknown Device, Update Driver Software..., Browse My Computer for Driver Software, Set the search to C:\, and still saying Unknown Device is the best driver software for it. No idea why it's doing this.
Proper Driver Update
What is going on is that Windows is seeing a more recent signature file attached to the SK4G drivers on your computer (I don't believe anything at all is wrong with your device) than the working ones there.
First, in Add/Remove Programs, uninstall the Samsung Kies and Samsung Driver pack you installed earlier. Now...
Go into on your PC:
://windows/system32
And locate the same file names, cut them all, and paste them in a temporary folder you create, preferably on the desktop or something similar. You may not find every file, and that's okay, just the ones you can find. Next, you will be wanting to paste the driver files from the package I uploaded. Now, turn off Automatic Updates, so it doesn't automatically install drivers upon connection. Reboot the computer, double check and make sure Automatic Upates are off when you log back on. Now, connect the device and see if it gives you the same results. By removing the old drivers which don't work, you'll be able to force it to the ones we know work, and you /should/ have success. As well - USB data debugging active and activating connection for data transfer via the notification pulldown menu would be the best way to do this initially.
Would I be looking in c:\windows\system32\drivers for the same file names as the ones you packed up?
Ok, so the only one I could find in the drivers folder was modem.sys. But it will not let me move/replace the one that's already in there. It's telling me access is denied, same thing when I try and set the permissions it will not let me. I am logged in as an Administrator, as well it says it when I log in as THE Administrator account. So yeah...
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
DuctTapedGoat said:
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
Click to expand...
Click to collapse
I tried plugging the phone in, still showing up as Unknown Device. Tried UnlockRoot.com's program, no change. Installing the Android SDK right now, as well as I tried deleting the INFCACHE.1 file, and no change with that either. Once I'm done installing the Android SDK I'll redelete the INFCACHE.1 file and restart and try the phone again.
I did go in and check the mounts in recovery and they were set to:
UNMOUNT CACHE
MOUNT DATA
UNMOUNT SDCARD
UNMOUNT SYSTEM
Thank you for your help so far.
UPDATE: So after installing the Android SDK, deleting the INFCACHE.1 file, restarting, and then plugging the phone in, comes up and says the USB Device is Not Recognized. Then goes to search the preconfigured driver folders, and fails to install the driver for Unknown Device. And ADB Devices shows no devices as well(didn't think it would, but yeah).
UPDATE: So after using my friends phone as a conduit to throw the Stock Odexed KJ2 w/ Root(http://forum.xda-developers.com/showthread.php?t=1328698) onto my SDCard and flashing that the phone seemed to go into a soft brick at pre-boot screen(where it says SAMSUNG T-Mobile blah blah blah). Mind you this would freeze before it was even able to get into recovery. So I took it into T-Mobile and they are doing a manufacturer warranty replacement. So hopefully this next phone will be able to connect to the computer and be read correctly.
I have a Samsung galaxy s3 which is just about 2 weeks old, stock rom and not modded in any way, i have been able to connect it to pc and it would be fine and work, the past 2 - 3 days whichever pc i plug it into mine or another pc windows will say that the usb device is not recognized and does not install the driver i also cant access it in any way (from usb).
i need help with this i have no answers on Google and i need to access my phone to get music and stuff on it but we need to figure out why mtp or camera mode or usb debugging all do not work.
Thanks.
pacificblue03 said:
I have a Samsung galaxy s3 which is just about 2 weeks old, stock rom and not modded in any way, i have been able to connect it to pc and it would be fine and work, the past 2 - 3 days whichever pc i plug it into mine or another pc windows will say that the usb device is not recognized and does not install the driver i also cant access it in any way (from usb).
i need help with this i have no answers on Google and i need to access my phone to get music and stuff on it but we need to figure out why mtp or camera mode or usb debugging all do not work.
Thanks.
Click to expand...
Click to collapse
Run the trouble shooting guide in KIES to re-install the drivers . Also, use KIES AIR, that only needs WiFi and you can access files and folders via your pc browser. Hope that helps
unistaller old driver. go to samsung website download lastest driver and install it
depzaj said:
unistaller old driver. go to samsung website download lastest driver and install it
Click to expand...
Click to collapse
Yup that to. BUT, often on the Samsmug site the software version available is one version behind behind that available via online updates Kies.
Tried that
Hi, I have already done all of the above more than 3 times ive removed the drivers, kies and re installed and my computer will always just keep saying usb device not recognized with code 42.
This is what microsoft have to say:
"Windows cannot load the device driver for this hardware because there is a duplicate device already running in the system. (Code 42)
Recommended resolution
A duplicate device was detected. This error occurs when a bus driver incorrectly creates two identically named sub-processes (known as a bus driver error), or when a device with a serial number is discovered in a new location before it is removed from the old location. You may be able to resolve this problem by restarting your computer.
Restart your computer
Click Start, click Shut Down, and then select Restart in the Shut Down Windows dialog box to restart the computer."
I have to go out just now. I'll take a looky see when I get back.
error 43
oh im sorry its not error code 42 but 43
windows detectded problems with this device....
Do you have a Linux OS under the hand? It would give you a lot more information than Windows does... If you dont have but want to try, you can download the disc image from ubuntu.com or any other distro like linux mint or fedora etc.
Just to get information on your phone you dont have to install it, just starting on the liveCD, plugin the phone in and running comands like dmesg, lsusb and maybe hwinfo would be able to tell you what is happening with your phone.
Sent from my Nexus S using XDA
error 43
i have got xubuntu but it is weird tat the phone does this on any computer not just my laptop. i was at work today and it was still an unknown device.
pacificblue03 said:
i have got xubuntu but it is weird tat the phone does this on any computer not just my laptop. i was at work today and it was still an unknown device.
Click to expand...
Click to collapse
This is why I suggest you to try to plug it in a linux machine and run those commands, there is obviously a problem with your device and Linux could help you to define what it is since it gives more information on the hardware.
If you are unfamiliar with dmesg output you can create a pastebin and link it here I will try to help with it. The output of lsusb may provide interesting info too. (as hwinfo but I don't think it is available by default in Xubuntu)
Sent from my Nexus S using XDA
error 43
well i will try if i can but it will be in a day or two as im packed to the top with assignments
Also I did not mention that but you can access your phone via the wifi network starting an ssh or ftp server on it, the one I use is connect bot from the market. This way you can manage you music and files over the network.
Sent from my Nexus S using XDA
error 43
yes i have done it using kies air that works. i will try the ubuntu method as soon as i can. thanks for all your help so far everyone.
Can you confirm that your usb ports on the PC is working with other devices. Its starting to look like a faulty phone. Have you tried a different usb cable, or can you check the current one with another device. We need to exclude all other factors before we conclude it is a faulty phone.
error 43
other devices work yes.
OK, looks like a croaked phone. Last ditch effort. If you go over to the forums at http://www.sevenforums.com/ have a good search for that error 43 code, there might be an answer that I've missed. We could also have a good look at the windows error logs, but I don't hold much hope as you have proven the PC hardware works, and you have checked and cross checked the drivers. All the error logs will show is an expanded view of the error.
I would consider returning the device with a view to a new replacement. Sorry. :-(
.
Thread moved to Q&A due to it being a question. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
Got the same issue on 3 different W7 pc's. Got my sgs3 like 3 days. first day USB connection worked just fine but now there's no way of connection it to pc with USB. offcourse you can connect with WIFI but with USB link is much faster
Galaxy S3 drivers issue...resolved!
pacificblue03 said:
I have a Samsung galaxy s3 which is just about 2 weeks old, stock rom and not modded in any way, i have been able to connect it to pc and it would be fine and work, the past 2 - 3 days whichever pc i plug it into mine or another pc windows will say that the usb device is not recognized and does not install the driver i also cant access it in any way (from usb).
i need help with this i have no answers on Google and i need to access my phone to get music and stuff on it but we need to figure out why mtp or camera mode or usb debugging all do not work.
Thanks.
Click to expand...
Click to collapse
I had the same problem and could not figure out why...here is the deal:
Prior to SGS3, I had the old Samsung Galaxy S/Vibrant and was using the USB cable which came with it...then I thought; maybe the USB cable in the box of GS3 is different or superior...i tried it and VOILA! it worked...so that is all I had to do...all these reboots and re-installing drivers was just a waste of time...PS> I am running Win 7 64bit
USB ERROR
I still cant connect with 3 different cables, i am going to do a factory data reset and tell you all how i go in about 15 minutes...
I have a rooted Nexus 5. MTP and PTP refuse to work. Doesn't matter how I install/remove drivers or anything. I've tried every trick on the internet and no avail.
The PTP storage used to work when I didn't have root, so what's the deal?
Could this be due to my rooting process? To be honest, I don't remember how I rooted. I'm new to the Nexus scene, having come from a samsung device.
However, I was just having this issue with my older E4GT (GS2 variant) when running rooted/custom roms.
Now, I have a friend with a S4 who decided to get rooted/custom roms and is now having the same issues, except before, both his MTP and PTP worked!
I'm lost and losing hope for this stuff.
aaa12585 said:
I have a rooted Nexus 5. MTP and PTP refuse to work. Doesn't matter how I install/remove drivers or anything. I've tried every trick on the internet and no avail.
The PTP storage used to work when I didn't have root, so what's the deal?
Could this be due to my rooting process? To be honest, I don't remember how I rooted. I'm new to the Nexus scene, having come from a samsung device.
However, I was just having this issue with my older E4GT (GS2 variant) when running rooted/custom roms.
Now, I have a friend with a S4 who decided to get rooted/custom roms and is now having the same issues, except before, both his MTP and PTP worked!
I'm lost and losing hope for this stuff.
Click to expand...
Click to collapse
Is the device showing up under Device Manager (which would indicate that the driver is installed--see #2 here)? This is not a "root" issue. I've run rooted devices for over three years and have only had the problem in the early days with the Pandigital Novel. Have you used USBDeview to look at what you have for USB drivers and to make sure all drivers are being removed? Try another cable and another usb port. Some cables don't handle data, they just charge; cables are a variable in the process.
ritchea said:
Have you used USBDeview to look at what you have for USB drivers and to make sure all drivers are being removed? Try another cable and another usb port. Some cables don't handle data, they just charge; cables are a variable in the process.
Click to expand...
Click to collapse
Yes, I've tried all three of those things. This seems almost to be mission impossible.
I am running rooted stock and my friend is running a new rom altogether. using different computers, but getting the same issue.
See, while I can get Fastboot and ADB to work without a hitch, I can't get PTP or MTP working AT ALL.
ADB and Fastboot seems to be the only thing people are focusing on, and that's not my issue... so It's even harder to find solutions online
aaa12585 said:
Yes, I've tried all three of those things. This seems almost to be mission impossible.
I am running rooted stock and my friend is running a new rom altogether. using different computers, but getting the same issue.
See, while I can get Fastboot and ADB to work without a hitch, I can't get PTP or MTP working AT ALL.
ADB and Fastboot seems to be the only thing people are focusing on, and that's not my issue... so It's even harder to find solutions online
Click to expand...
Click to collapse
So it does show under device manager? Have you right-clicked and updated driver? Step #2 in the link pointed to USB drivers rather than adb. Yes, adb Is the usual culprit, but I've seen quite a few reports of your problem lately. Usually, removing the drivers and allowing the PC to reinstall works. Have you tried wireless to transfer files--at least a temporary solution?
If you're interested (desperate enough) to do a factory reset, I'd recommend WUGS toolkit. It will wipe do backup everything. Revert to stock and unroot. Then root and install custom recovery.
Sent from my Nexus 7 using Tapatalk 4
Happened to me when i rooted the device with wugs. I think because I used the RAW drivers. Just uninstall adb android driver from device manager and all the other drivers that resembles the nexus on usbdeview, reboot . Then put again the usb in the pc , and you are ready to go
ritchea said:
So it does show under device manager? Have you right-clicked and updated driver? Step #2 in the link pointed to USB drivers rather than adb. Yes, adb Is the usual culprit, but I've seen quite a few reports of your problem lately. Usually, removing the drivers and allowing the PC to reinstall works. Have you tried wireless to transfer files--at least a temporary solution?
If you're interested (desperate enough) to do a factory reset, I'd recommend WUGS toolkit. It will wipe do backup everything. Revert to stock and unroot. Then root and install custom recovery.
Click to expand...
Click to collapse
I have tried that too, but I end up with the same outcome. Same drivers I would normally have installed and give me no recognition of the device for file transferring.
Fortunately, knowing how this goes down, as it has happened before with me and my S2, I'm not desperate enough to factory reset. As I would ultimately reach the same issue.
I've been interested in wireless file transferring, but I much more prefer not having to upload the file to something like dropbox or manually setup a server. I'm more into the press-and-go (similar to the plug-and-go method... haha, get it?... made a funny there cause it relates to a cord ordeal) routine.
I haven't actively searched that route yet because I'm in hopes that there is a fix for this problem. I'll get to it if there really is no other choice. So, if there is a program that will allow me that ease of access, I'm open to suggestions!
AkaGrey said:
Happened to me when i rooted the device with wugs. I think because I used the RAW drivers. Just uninstall adb android driver from device manager and all the other drivers that resembles the nexus on usbdeview, reboot . Then put again the usb in the pc , and you are ready to go
Click to expand...
Click to collapse
Seeing this makes me question whether I'm confusing the purpose for each of these drivers or you haven't read what I wrote. However, our circumstances differ. I didn't root through conventional means of the toolkits, I just came across it through my search for driver issues. I have tried the method you are suggesting, as the toolkit driver installation steps take me through that step before I do anything else; but this doesn't work. I end up with the same outcome: Device is recognized and drivers are installed (if I allow windows to automatically search for them), but no PTP or MTP for any file transferring.
ok, silly question : Is it enabled on your android phone? under memory ->tap the 3 dots and you will see mtp/ptp try to uncheck and check.
Otherwise I don't really know anything u could do about it.
By using the NRT or toolkits to root, all of the pc's usb drivers were deleted and new/generic/universal ones installed to re-install custom recovery & achieve root. Go to Control Panel on the PC, do you see Portable Devices listing including the Nexus 5 ? Most likely, no - only Android Interface.
A simplistic approach that worked for me is to roll it back - if you are using PC running Windows OS, use System Restore to go back to a previous state to an earlier (earliest possible) time before - with the N5 disconnected. When the PC is restored, turn OFF USB debugging on the N5, connect via the OEM N5 cable - it should be recognized, then turn ON USB debugging if there are missing drivers - let Windows search & install.
At some point, N5 will be recognized as a Portable Device along wit Android Interface, and "Auto Play" would pop up, with full access to all the SD folders & files. Toggle MTP and PTP if necessary as it might install more drivers - you should be good to go.
Reboot the PC just to reconfirm that everything is back to normal, connect N5 and profit - enjoy.
If this work, please share & if it doesn't - please comment what didn't work.
The simplest and shortest way to connect google nexus5 with PC as MTP(Media device)
When I plugged it, there wasn't any yellow exclamation mark within Device Manager. So for me, the drivers were OK. But the device was not listed within my Eclipse DDMS. After a little bit of searching, it was just an option to change in the device settings. By default, the Nexus 5 USB computer connection is in MTP mode (Media Device).
What you have to do is:
Unplug the device from the computer
Go to Settings -> Storage.
In the ActionBar, click the option menu and choose "USB computer connection".
Then select Media device(MTP) or Camera(PTP) based on your requirement...
Plug the device and you should have a popup on the device allowing you to accept the computer's incoming connection..
I hope this will help!
I need to update the Bauhn Sphere AHD5-114 from V1.2 to V1.3 as this is a fix to repartition the device (only allows 1GB for apps, has 32GB storage).
Instructions to update, including driver files are here: https://onedrive.live.com/?cid=a25f...06&ithint=folder,zip&authkey=!ANnJGmqdleVuyX0
The Problem: The phone won't connect to the PC when the phone is off. It connects fine when on. I have tried 3 different computers and about 10 different charging cables, all using the drivers included in the folder.
It connects for 2 seconds then disconnects, windows tries to find a driver but comes up with 'device unplugged'.
Need to either fix connectivity issue or find another way to install the update (this method is with SP Flash Tool).
Note: phone is unrooted (tried Framaroot, SRSroot and Towelroot). Also I'm sure there's a fix somewhere but I've looked for hours, maybe using the wrong keywords but all I've found is connectivity issues with the phone on. All PCs have windows 7.
bump
Created this account to thank you for the files! A friend of mine has the 1GB limit issue, and I want to try their official fix first, before going to unofficial means. I'll try it and let you know what happens.
Not sure where you got with this. Initially I tried the upgrade on a Windows 7 laptop and ran into the same problem you did. The phone wouldn't stay connected. I noticed the instructions "highly recommended" doing the installation on a 32-bit Win XP machine. I gave it a try on a 32-bit WinXP machine and had the same issue. I left the software running, phone plugged in, then unplugged the computer-end of the cable and plugged it into a different USB port. It needed driver software installed, again, so I pointed it to where I'd unzipped the driver, it installed the driver (for the second time) and then the upgrade worked.
The phone is *far* more usable now, it seems that just about all the 32gb is available for app installation. This is how the phone should've been configured out-of-the-box, imo.
Thanks for making the installation software available for download. I couldn't get it from the bauhn site.