[Q] Help me problem solve AHD5-114 - General Questions and Answers

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.

Related

[Q] USB does not recognize(Unknow Driver)

Thanks evryone. I hope you can help me.
Yesterday ,I usual mobile phone to connect to the PC,
but,the pc tips me:"USB does not recognize(Unknow Driver)",
I've done a lot of action, including: replacement of data line, a replacement computer, but still no.
At present, the machine has been used for WIFI update to the official system 2.3.4.already unlocked,but unroot.
What am I to do to recover????Please help,thank you.
Not sure how to solve that problem, but perhaps you could delete any related drivers for your nexus s and try to install this driver after.
Weird that it won't be picked up by a different computer.

[Q] SK4G not being recognized on PC

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.

[Q] Samsung Galaxy S3 - Driver issues W7

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...

Any official fix for MTP driver installation failed?

I just got a S3 yesterday but was greeted with the dreaded MTP driver installation failed message on win 7 (32 bit)
I installed the regular verizon s3 drivers from samsung's site, did the same thing, uninstalled and tried Kies and let it install the drivers, same problem
tried a different usb port, same thing
restarted the comp and computer, still no go
im getting frustrated now
it seems samsung has known about this issue for over a month now but still hasnt been able to fix it
my a500 and galaxy nexus work fine with MTP so not sure why this would mess up
ive looked at other threads but there was no clear solution on how to fix it
I don't have any issues with mine
Sent from my SCH-I535 using Xparent Blue Tapatalk 2
thats nice but it doesnt exactly do anything for my problem
Joey22688 said:
thats nice but it doesnt exactly do anything for my problem
Click to expand...
Click to collapse
Did you try a factory reset?
Sent from my SCH-I535 using xda app-developers app
This happened to me too but I was running a CM10 ROM. What are you running and have you tried a different ROM?
Unfortunately, I cannot remember exactly what I did but I recall allowing Windows (I'm on W7) to find the drivers and install for me.
I'm not having any issues either, I'm using both 32/64 versions of Win 7...
These are the drivers I'm using:
http://downloadcenter.samsung.com/content/SW/201206/20120620051748445/Verizon_Wireless_I535_GSIII_Samsung_USB_Driver_v1_4_6_0.exe
Hope this helps..
I think I found the problem (its not the phone)
its the drivers that samsung issued
I plugged the phone on my win 7 64 bit desktop (not installing any drivers beforehand) and I got a few failed messages for drivers but I was able to access the file system fine
I then installed the driver pack posted and above then got the mtp driver installation failed message and was unable to access the file system
uninstalled the driver pack and connected the phone back up and I can access the file system (with some other drivers failing to install, I think relating to usb modem stuff ect...)
so until samsung fixes the driver problem I will have to deal with a few driver installation failed message every time I hook up the phone, but at least I can access the file system
im running the phone on the stock ics btw, didnt install cm10 or anything like that, the phone is rooted though but I rooted it after I found out about the mtp driver problem so it shouldnt mean anything
I have the same problem on Windows 7 32 bit. I rooted my phone and installed samba as a temporary fix.
Plus I just bought an external 32 GB SD card and I plan on using that as my workaround and just transfering files between the two.
Sent from my SCH-I535 using Tapatalk 2
Problem for me was the root.
Could you humor me and try this:
- go into the superuser app
- Select the 'temp unroot' checkbox from the first screen.
- unplug then replug the USB cable on your phone. The drivers should install on the first try this time (they did for me) and Kies should work too.
The problem seems to be that SuperUser exploits the USB Debug internally so, even though USB Debug is unchecked, it is still detected as checked by the connection and fails the install of the driver.
Solution #2 is the amazing script that transforms your MTP connection into a UMS one (look in this thread http://forum.xda-developers.com/showthread.php?t=1785243 and thank open1your1eyes0 ). Once in UMS, you don't need the MTP driver to see your device so that's another approach.
Good luck
I bought Samsung Galaxy S3 2 weeks ago. Windows installed the drivers for it when first connected to my Windows 7 64 bit PC. It came up in the list of Devices on the Explorer. I installed "Kies_2.5.0.12094_28_8" which installed USB driver on top of the Windows driver. At the end of the installation, it gave "failure to install Samsung MTP driver".
Saw a thread on other forum where it was suggested to remove the driver from System Driver window under Control Tab/System and reboot. To be cautious, uninstalled Kies. Rebooted PC. Windows installed the driver. As soon as Kies was installed the whole issue unfolded again.
Looks like ALL Kies versions (including previous version of Kies_v2.3.3.12085_7_5) have incompatible and wrong driver which is resulting in this unresolvable situation.
I removed the MTP driver (control panel/system/device manager - MTP driver has ? mark - this is the one). Then removed the phone and rebooted PC. After reboot, connected the phone back. Windows detected the device and automatically installed the driver. The device is listed in Explorer and is fully accessible. Started Kies. It showed the device as GT-I9300. It took a while and connected to the phone. All functions became useable. Sync'ed the contacts etc.
Day2. Booted the PC. Device is still shown in Explorer. Kies shows GT-I9300 and then displays "Connecting Device" - IT FAILS TO CONNECT and on pressing "Trouble shooting" button, it re-installs its own drivers and fails to install MTP driver AGAIN" - the Kies software SUCKS
Solved! For real!
For some reason, any of those options helped me to make it work:
- Reinstall Windows Media Player
- Remove registry key
- Clean up old usb drivers
- re-install 100 times drivers from Verizon, Samsung. Even old versions.
- Install from Windows Update. I tried to do that 1000 times. Gosh!
- enable UMT access (mass storage) on the phone.
The only thing that worked was, for some reason , getting the drivers from a random computer that was the only computer that worked.
Windows 7 x64
Attached the files. Go to the devices manager and update the drivers.
Israel Leite
How I solved it
Joey22688 said:
I just got a S3 yesterday but was greeted with the dreaded MTP driver installation failed message on win 7 (32 bit)
I installed the regular verizon s3 drivers from samsung's site, did the same thing, uninstalled and tried Kies and let it install the drivers, same problem
tried a different usb port, same thing
restarted the comp and computer, still no go
im getting frustrated now
it seems samsung has known about this issue for over a month now but still hasnt been able to fix it
my a500 and galaxy nexus work fine with MTP so not sure why this would mess up
ive looked at other threads but there was no clear solution on how to fix it
Click to expand...
Click to collapse
1. Un-install Samsung Kies and USB drivers
2. Then install the Install Samsung Usb driver for mobile phones version 1.4.6.0
3. with phone un-pluged from the usbcable Go into settings/Developer Options un-check Stay Awake un-check USB debugging un-check Allow mock locations Now hit the HOME button then plug in the USB cable and your are set..
This worked perfectly painless for me :laugh:
Solution x Win XP
This solution worked for me.
Install microsoft patch for usb and reinstall MTP driver
see:
http://forum.xda-developers.com/showthread.php?t=1150211
Hope this helps

[Q] Problem with USB mass storage

Solved: Hopefully this helps someone else. I uninstalled all LG drivers from my PC. Then I connected my phone in via usb and checked my device drivers and updated them. However, rather than letting Windows find the best MTP drivers I chose to browse my computer and picked from a list on my PC. I selected the Linux drivers and everything works perfectly now,
I have a P509 running WC’s AOKP Milestone #6 but I did something stupid…while cleaning up files and programs I uninstalled my LG usb driver for my P509 and now I can’t get the PC to recognize the phone. I run W7 64 bit and it just won’t connect - not even from recovery. On another XP PC it connects no problem (it has LG driver 4.9.4 installed although I don’t recall installing it) and my laptop running W7 64 bit connects no problem either (it has LG driver 3.6 installed, but again I don’t recall installing it on the laptop either). Installing 4.9.4 or 3.6 on my problem PC doesn’t help. I keep getting an error that “MTP… whatever” failed. It’s driving me nuts. I can use the other computers if I need to but the problem PC is my main unit and more convenient to use for all my needs. Also, the phone is recognized by my work PC which has no LG drivers installed at all, nor could I if I wanted to as I don't have admin rights.
Any suggestions for my W7 PC?
Thanks,

Categories

Resources