i need help, i have tried everywhere and can't find anything and any help would be greatly appreciated
i'm on the road to root my samsung galaxy fascinate and have ran into a laundry list of problems. i have rooted many android phones coming from eclair, froyo, and gingerbread, but seem to be stuck at the slightest of problems when it comes to the fascinate.
i can not install the drivers to the fascinate. i have searched through the web for all the drivers and have tried every possible galaxy driver. the driver simply won't install on my windows 7 prof 64bit machine. i have never ran into this problem before with any other phone. every time i try to install the driver it gets to the very end of the install then pops up with the message "windows was unable to install the driver"
It also gave me the option to view the failed windows installation log, which after many successful steps, at the end the log shows this error:
Action ended 1:26:53: ShowMsiLog. Return value 0.
=== Logging stopped: 12/16/2011 1:26:53 ===
MSI (c) (0C:08) [01:26:53:750]: Product: SAMSUNG USB Driver for Mobile Phones -- Installation operation failed.
MSI (c) (0C:08) [01:26:53:750]: Windows Installer installed the product. Product Name: SAMSUNG USB Driver for Mobile Phones. Product Version: 1.3.550.0. Product Language: 1033. Manufacturer: SAMSUNG Electronics CO., LTD.. Installation success or error status: 1603.
i have also attached the entire log
the first thing i did was plug in the phone, which windows sensed this and automatically installed a driver, not sure which. after this i unplugged the phone and then checked "usb debugging" for rooting purposes and plugged the phone back into the computer which windows then installed another driver automatically, then following the steps from xda to root the phone, i downloaded the given drivers which is where the problem first occurred and the drivers were unable to download.
I'm simply trying to get root access to the phone and can't do anything with the phone with crappy drivers...i can't even mount usb sd card now to transfer data anymore. the drivers have completely been shot. i desperately need help. please
also what is the absolute easiest way to root the fascinate? is it with one click root or with Odin? Because the fascinate just updated itself from 2.2.2 EH05 to 2.3.5 EH03 and i'm not sure which program supports rooting which version of android. also all other android devices simply give root access to the stock rom, which is great cause i get to keep all my apps, messages, contacts...etc, then simply titanium backup everything and transfer it over to the new rom. is it different with the fascinate? will rooting the device simply flash a completely new rooted rom? therefore loosing everything? if anybody has any answers to any of these questions, please be my hero. thanks
sorry didn't see what section this was in, also have posted this in the Q & A section, my apologies
This is elementary, but did you unzip the drivers file after you downloaded it? The reason I ask is I had same problem for about 10 mins before I realized my brainfart.
As for root, just flash a rooted rom, either stock or custom. Tutorials and guides are all over this site just dig a little.
Have u try downloading the driver directly from samsung.com ? No way to mess up that way.
Backup everything if u dont want to loose it. Sms backup from Market let u save ur text to your gmail account. Save your contacts to the SD card, by exporting it as vcard. Then titanium like u already know.
Once u flash new rom u will loose everything. Flash new custom rom will berooted already.
Related
(Moved from development forum, newb root thread)
I recently received my phone back from a HTC repair. I hadn't used it til today as I was waiting for froyd 1.5 to come out before rooting it and setting it up. Today I switched it on and it asked me if I wanted to update the software, I clicked no. Then I followed the steps in the OP but had problems in step 5 : everytime I typed anything (including "su") and hit enter I had a message saying "denied" or words to that effect, despite the UniversalAndroot program giving the "woot rooted" message.
This is the part where I might have done something stupid - I decided to let the phone update itself to the latest software, and then I was planning to run the UniversalAndroot again. I thought that maybe UA had been tested on the latest official HTC stuff but not whatever 2.1 but not fully updated version that mine had come back from repair with. It went to the update screen and the progress bar completed, it tried to reboot but just got stuck on the white boot screen with the green HTC logo. If I pull the battery out and start again it just hangs at the same screen.
I can get the 2.73.405.5 WWE RUU to see the phone when in fastboot, but when I try to update it it eventually gives me error 140 "bootloader version error".
I tried to load it through HBOOT using kazuni's technique in his thread "A way of flashing the RUU rom extract" (sorry, it won't let me paste a link to the actual thread) but it says "main version is older, update fail". Do I need to send it off to HTC again? I just got it back! Will they be able to tell what broke it and refuse to fix it?
Many many thanks
Try the 2.1 downgrade in my sig below.
Please could you explain "The recovery can be flashed via running 'runindos.bat'."? I assume I need to install this adb program that people keep mentioning?
Also what is the goal here? To upgrade my phone to 2.1 (which was already on from the HTC repair, the OTA update just said something about adding g-sensor calibration tool) to then root it or to downgrade my phone to 1.5 to root?
Many thanks!
Ah, just seen adb guide on villain forums. OK, I'll follow the guide to get adb installed, put your recovery files in the /tools folder, but then how exactly do I flash the recovery? Simply by typing runindos.bat in cmd whilst in the correct folder?
Ah, I see, I just run the batch file from your recovery download. Sorry for all the dumb questions! I ran this with my phone on fastboot usb but it said this :
adb server is out of date. killing...
* daemon started successfully *
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
"Files copied and permissions set, rebooting HTC Andriod 2.1"
"Your phone will now reboot into normal mode, then reboot into recovery mode. I
f it does not reboot the second time, wait 10 minutes and manually reboot and be
gin again."
error: device not found
As far as I can tell nothing happened on my phone. I assume my usb drivers are fine as the RUU was able to begin updating before it gave me the 140 version error. Any ideas?
It's the ADB drivers, what OS are you using?
I am using Windows 7. I thought i read that the latest version of htc sync had drivers fully compatible with win 7 and the RUU seems to see it fine once I selected 'my htc' drivers under adb in device manager. I am confused!
HairyBones said:
I am using Windows 7. I thought i read that the latest version of htc sync had drivers fully compatible with win 7 and the RUU seems to see it fine once I selected 'my htc' drivers under adb in device manager. I am confused!
Click to expand...
Click to collapse
You may want to build an XP workstation eitha virtual or physical. Don't be alarmed. Yes, the latest version of HTC Sync does contain the drivers. However, they some what don't work for majority of users. Sorry.
Just did a quick google - will http://www.microsoft.com/windows/virtual-pc/download.aspx work?
HairyBones said:
Just did a quick google - will http://www.microsoft.com/windows/virtual-pc/download.aspx work?
Click to expand...
Click to collapse
virtual box - http://www.virtualbox.org/
vmware player - http://www.vmware.com/products/player
Eek - I need to get an xp install disc and set it up like I was loading it onto an actual PC? The microsoft tool within win 7 definitely wouldn't work?
HairyBones said:
Eek - I need to get an xp install disc and set it up like I was loading it onto an actual PC? The microsoft tool within win 7 definitely wouldn't work?
Click to expand...
Click to collapse
Yeh, to install XP you will need an install disk, unless you download XP Trial version VHD. This is the trial version from Microsoft in virtual machine mode.
http://www.microsoft.com/downloads/...90-958F-4B64-B5F1-73D0A413C8EF&displaylang=en
Windows XP Mode with Windows Virtual PC, available for Windows 7 editions Professional, Enterprise, and Ultimate, provides a licensed virtual Windows XP Professional environment for compatibility with applications not compatible with Windows 7. Windows Virtual PC supports USB attachment, therefor supporting direct connection of USB devices to the virtual Windows XP environment.
For information and to download Windows XP Mode or Windows Virtual PC visit the product page microsoft.com/windows/virtual-pc/default.aspx
Brandon
Windows Outreach Team- IT Pro
I have run into another issue. I can not mount my phone to computer. I think this is happening because of me rooting my phone. I was able to root the phone successfully. But somewhere along the way something happened and I can't mount my phone to my pc. This is as if my pc is not reading/recognizing the phone when plugged in. However, my phone is reading its memory and sd card perfectly.
When I plug the phone to my pc:
With USB Debugging off... I dont even get a notification in the slide down menu asking me to either mount/unmount.
With USB Debugging on... I do get the option in slidedown menu to mount my phone. At the same time the computer shows a pop up message asking me to install driver software for Samsung_Android. In the meantime , I press mount sd card which by the way is still not recognized by the computer.
I dont have the driver for samsung_android to install on the computer.
This thread here describes how I rooted my phone. I thought this background info might be helpful in solving the problem.
Does anyone know a potential fix for this situation.
Thanks.
When this happened to me having it" ask what to do" when connected may have solved the issue. I went through this just yesterday. You also might re-boot your phone and computer a few times...nothing like that can hurt. Until someone who actually knows something finds this thread : P
67 views and just one reply.
**bump... someone gotta know the solution
Reading your post is a little confusing. If you are saying you cannot "mount" the phone the term Mount is replaced with "connect usb storage" in the pull down. If yours is saying mount, then your rooting process may have not worked. It is hard to tell based on how you wrote this up. Use the one-click rooting you can find all you need INCLUDING the Samsung computer drivers (32 or 64bit) @ unlockr.com along with a nice youtube video showing the whole process beginning to end.
Additional thoughts:
If you are really jacked you can always go to the bible (in the top of this general forum) and search for the "ALL in One" zip to flash back to stock...etc. The All in One has the stock kernel, the .pit (used for mapping) the 32 bit driver/64 bit driver for the computer and Odin all in one Zip. You should have this in your computer folder named (unbrick tools) either way you should get all this if you are going to be customizing the phone, along with the Eugene's froyo that does not brick rom. This rom is a lifesaver should you flash in a way where the format will not recognize the stock format. You can flash this 1st then stock right after and that ALWAYS gets you back to stock.
In the future, when you are trying to describe what is going on try to be careful with terminology it is important not to use terms loosely otherwise we are just guessing on how to help......... hope this helps
Thanks for your thoughts. It seemed as if my computer was lacking the drivers for samsung vibrant so I installed them from here
and now I can connect my phone to the pc and its working fine. I thought I had downloaded and installed the drivers before when I downloaded on the big download button on the top and installed some fake software from advertisement.
If you ever flash a 2.2 rom and experience the problem again with the drivers already installed, this might fix it...
http://forum.xda-developers.com/showthread.php?t=846384
I have had the easiest run so far in getting my HD2 to work with WP7, installling DFT's ROM and getting an activation code was a breeze. All is good except for one issue. When I connect by USB to my PC, the PC shows a window saying that it is seeking and then installing Device Driver Software. It does this every time I connect and then concludes by saying that my unidentified device is now ready for use. Zune then tells me that it can't make a connection between my HD2 and the internet but it can still sync files etc. I have installed Windows Device Manager (with .NET4 and developer tools etc.) and it too can't connect with my HD2. I've pursued the references in various threads to firewall issues and so on but I'm none the wiser.
Can anyone advise me what I should look at or what to try?
Other than this, I just want to say a huge THANKYOU to all at XDA and the extended community of interested/interesting folks who make it such a fantastic resource for everyone - BRAVO!
im having this EXACT same problem! anyone got any answers?
Zune
Guys,
Did you install Zune Desktop Software?
Once you have installed Zune, it should pick up your device.
Let me know if that does not work
I've tried everything except doing a hard-reset. And, yes, of course I installed Zune on PC
i assume you mean Windows mobile device center?
you dont need it
it should connect and be done, the fact that it isnt remember the correct driver suggests something on the driver side is buggered.
With the phone connected go in to the computers device manager, and right click on anything to do with the phone, including and unknown devices, right click and uninstall them all, before it installes them all again, disconnect the phone
look for a tool on google called USBDVIEW
make sure you get the correct version 32bit / 64bit
You will also need the USB IDs if you want to see who makes each device
put it on your PC and run it in admin mode
Locate anything todo with the phone and right click and remove them all
Remove Zune
Remove Windows mobile Device center
restart your PC
install zune first
Then plug in your phone into a different USB port and not in to a HUB
See how you get on with that
Second thoughts, ive attached the 32 and 64 bit versions, both already have the USB device IDs file with them, just copy the zip file to your PC, extract, and run as admin, all credit goes to the owner of this, i found them at http://www.nirsoft.net/utils/usb_devices_view.html
sorry double post
Didn't work. =/
UPDATE: It did work
Zune cannot connect to an HD2 running Windows Phone 7 unless the time and date match on the phone and the computer. Make sure that your date and time are set up correctly on the phone, and do match the time and date with your computer. It is a long shot, but it worked for me before.
For the driver problem, dazza9075 gave the best advice.
Hmmm, so much for that fun. I was running WP 7004 when the computer first couldn't find the phone, after doing what dazza said the driver problem got fixed, and Zune found the phone. I updated from 7004 to 7008, how ever the phone kinda crashed at step 8 (restarting your phone) so i restarted it manually, the update is working fine except now Zune can't find my phone again. Not even after doing Dazzas method again.
I will try to change the time zones maybe that will do the trick.
I just got my Gtab today and can already find things I just cant live with so im trying to prep for a new ROM when there are some stable ones out there.
I have downloaded everything from the CWM recovery and root threads but i cant seem to get a driver to work... I have tried section #2 multiple times over on both XP pro x86 & Win7 pro x64 but i end up with the same 3 unknown devices on both *neither have SDK*. When i try to install the unknown USB device with the drivers supplied in nvflash it cant find anything suitable *even pointing to sub-directories*. I downloaded the drivers mentioned in the rooting thread and installed those, I went back to the DM and tried every single directory in the newly unpacked location "C:\Program Files\Samsung\etc.." which had quite a few different ones but i havent gotten anywhere.
I remember this being almost identical to the problems i had trying to root my phone so I finally found linux directions and worked from my mac. Does anyone have a clue whats going on and how to get MS FAIL OS to work?
I guess im the only person having this problem... ohh joy another android that is going to be a pain in the as to root
on your computer, uninstall ALL the samsung drivers (for any previous samsung device/phone). Then connect the tab to your computer and let it search on its own. on your tab the usb debugging should be turned off.
I think the tab is designed to let windows recognize it as usb, but if you have any previous drivers they get into the way.
Well guys I've been trying for hours now, whenever I try to install the USB drivers in order to unlock my bootloader, when I plug in my Nexus it installs the MTP drivers on it's own, if I try to install the google drivers downloaded from ADB all I get is a message saying the best drivers for my device are already installed and it doesn't let me overwrite them.
If I go with the use disk option it doesn't let me choose the usb_drivers folder because it just wants to use a .inf file, whener I follow the instructions the toolkit dictates I read the dead end with the "The best drivers for your device are already installed"
I'm so angry right now.... Please help me.
Are you on a Windows XP operating system by any chance? There are major issues with MTP mounting on WinXP regardless of the service pack you're on. Some people claim they've gotten things working by updating WMP, via a Naked Driver and even by installing the Android SDK. Let me know if you are indeed on WinXP & I'll get you some links
Did you try following Wug's Nexus Root Toolkit to install the drivers? That helped me. I cannot post a link so look around for it.
I'm running Windows 7 64 bit, thanks guys, I just gave up and did it in my sister's laptop, it worked on the first damn attempt, maybe the drivers of my N10 were screwing something up, that's my best guess.
Glad you got that sorted--just for future reference, a common recommendation for people having driver issues with their Nexus devices is to simply go into Win Device Manager, uninstall all your current Nexus & ADB drivers and restart. Then plug your phone in via USB and let the auto installation do its thing. Usually this fixes all issues w conflicting device drivers