Related
I Read your thread of "Namaste Guide to Arc Rooting" etc and I Started following the procedure of Rooting my LT15i without unlocking the bootloader.
But the moment i connected my Arc in flash mode, It started installing the drivers of "S1 Boot Download" but then it didnt succesfully install them. It also failed to download the drivers via Windows Update.
Could you please provide me the drivers or the Link to them? Or a workaround (if any)
Thank You!
I'm Sorry For Double Posting but 32 Views and not a single Reply!
Isn't there any solution to this?
Same here mate
install pc companion..then conect your device..pc companion auto install all driver on your pc..
If your using Win 7 it seems to be a bit stupid concerning the MTP driver i had to reinstall PC companion several times befor it would install the MTP driver properly.
on My XP machine it seems to do it on its own when i connect the phone pretty fast. Win 7 alot slower and half the time it fails to install
There are all drivers what you need
This package includes Fastboot, Flashmode and ADB Drivers for all XPERIA devices
It's from Flashtool
If you have win7 64 bits or win vista 64 bits and you follow the official SE guide (so you have donwloaded Android SDK + modified inf file from SE site), you have to use the inf file I've posted here instead of SE one.
If you are following lollylost100 guide, you'll find needed packages here
Today I tried to revert back from ICS to GB. I made a VMWARE Windows 7 installation on my MAC(host os). Installed PC Companion, Flashtool an al the drivers. Started flashing, and everything seemed to be ok. Flashtool started flashing system.sin to my phone, it failed with "S1 header checksum error"
Tried flashing different firmwares, all failed on different points with that error.
As a consequence, my phone failed to boot and stalled at Sony Ericsson logo or at that screen with exclamation mark. I have to say I felt quite bad.
After that, I made a bootcamp partition (which I hate doing and having on my mac), installed all of the above and flashed firmware flawlessly. A relief that was!
I wonder, what could be the reason for that behaviour in vmware installation? Did I miss some important step with the VM setup? (question targeted at those, that flash their phones inside vmware)
Thanks for answers!
flashtool linux editon may work on a mac because it's java based
you can ask to developer for a better explanation
yacloo said:
flashtool linux editon may work on a mac because it's java based
you can ask to developer for a better explanation
Click to expand...
Click to collapse
Sent question to him already. Well, I'm not quite interested in linux version (I couldn't find it anyway), I just wonder, what is the difference between vmware and bootcamp installation, since the same OS, and software versions were used.
lyteo said:
Sent question to him already. Well, I'm not quite interested in linux version (I couldn't find it anyway), I just wonder, what is the difference between vmware and bootcamp installation, since the same OS, and software versions were used.
Click to expand...
Click to collapse
flashtool website you can find all windows/linux editions : http://androxyde.github.com/Flashtool/
about to mac os compatibility you may check this post
http://forum.xda-developers.com/showpost.php?p=24925310&postcount=34
I think windows use native usb driver on bootcamp
I am not sure but vmware has its own usb driver and serves as a bridge between the two systems
maybe bad usb bridge driver was causing the problem
AT&T S3. Rooted but stock ROM. Windows 8 64bit. For some reason, if I try to copy files to from phone/card right after connecting the phone, it works fine. But if I wait a while, I can't copy any files to/from the phone but I can browse the folders.
Any ideas?
Have you tried a different computer with windows xp? Someone else had an issue with transferring files via windows 8 as well, but windows xp worked perfectly.
Sent from my SAMSUNG-SGH-I747
I had this problem too, remove all the drivers, hook it back up and let Windows find drivers with Windows Update, it will work... theres a thread somewhere with installable drivers that work for 8... It was linked to in the past few days in a another Q/A thread...
Quasimodem said:
I had this problem too, remove all the drivers, hook it back up and let Windows find drivers with Windows Update, it will work... theres a thread somewhere with installable drivers that work for 8... It was linked to in the past few days in a another Q/A thread...
Click to expand...
Click to collapse
I essentially tried this, went into device manager, removed drivers, rebooted, plugged in phone. Also tried installing latest Samsung drivers. Typical Windows "make your life more hectic rather than easier" BS. And I'm a Windows Expert. Short solution - get a Mac. LOL. Well at least I know I'm not alone. When I find more spare time, I'll retry everything I can think of.
the search wasn't trash this time and found the thread I was talking about, try these:
http://forum.xda-developers.com/showpost.php?p=11498043&postcount=1
I unlocked my bootloader on my pixel xl and now when I select the "Transfer Files" MTP mode on my device, I can only copy files from the phone and not to it.
I copied twrp and the other files I needed to my google drive and proceeded with installing the RC Dirty Unicorns 11 for Pixel XL Marlin and got the rom fully working.
But MTP is still not working correctly after the bootloader unlock.
anyone have any ideas?
I am using the adb/fastboot/drivers package from xda located here. https://forum.xda-developers.com/showthread.php?t=2588979
It has worked fine for me for months, I am just hoping to find a way to copy all my files back to the internal storage from my windows 10 PC.
First, I'd recommend getting ADB and fastboot directly from Google to make sure you have the current version. Having read around on the Pixel XL forums for a couple months now, that seems to be the first necessary step in troubleshooting. Check this article for a how-to if you don't want the entire Android SDK: http://lifehacker.com/google-finally-lets-you-download-adb-and-fastboot-as-st-1790840830
I downloaded the official sdk platform tools from https://developer.android.com/studio/releases/platform-tools.html as the article states.
but that is only adb, fastboot, systrace, etc1trace, dmtracedump, sqlite3, etc
this platform sdk package from google does not include the pixel xl usb driver package that is included in the link I posted.
I have replaced the platform tools on my system with the offical ones from google to make sure.
I have now done some additional research and found this url
https://developer.android.com/studio/run/win-usb.html
I extracted the driver packages from Snoop05's thread that I linked and did a file compare with beyond compare.
They are exactly the same usb drivers that google published 9/20/2014
I am going to download the SDK Manager and check back in the thread.
The pixel USB drivers are stored on the phone itself.
aholeinthewor1d said:
The pixel USB drivers are stored on the phone itself.
Click to expand...
Click to collapse
Drivers are part of your operating system. I am using windows 10 and Microsoft provides them as part of the windows operating system and via windows update as part of Microsoft's WHQL program.
It is possible that from time to time Google will release a new driver package via the link I posted above or they will provide it to Microsoft for WHQL driver certification to update via windows update.
The device uses MTP and there for acts like a Camera presenting it's sd card instead of the old classic usb hard drive emulation. All phone manufacturers started using MTP because it doesn't require the phone to unmount the storage from the phone to access it. When it was unmounted on older phones it would cause apps to crash if they were looking for files on the storage when it was unmounted.
There is no folder on the device containing inf, cat, dll files to be used for driver installation.
Your device is being accessed with the generic driver that microsoft provided with the installation of windows.
joe ferreira said:
Drivers are part of your operating system. I am using windows 10 and Microsoft provides them as part of the windows operating system and via windows update as part of Microsoft's WHQL program.
It is possible that from time to time Google will release a new driver package via the link I posted above or they will provide it to Microsoft for WHQL driver certification to update via windows update.
The device uses MTP and there for acts like a Camera presenting it's sd card instead of the old classic usb hard drive emulation. All phone manufacturers started using MTP because it doesn't require the phone to unmount the storage from the phone to access it. When it was unmounted on older phones it would cause apps to crash if they were looking for files on the storage when it was unmounted.
There is no folder on the device containing inf, cat, dll files to be used for driver installation.
Your device is being accessed with the generic driver that microsoft provided with the installation of windows.
Click to expand...
Click to collapse
I'm aware of what drivers are. I'm going off of what people on here have said previously. I never specifically looked for them but multiple people have said the drivers are on the pixel so they can install to computer when connected.
aholeinthewor1d said:
I'm aware of what drivers are. I'm going off of what people on here have said previously. I never specifically looked for them but multiple people have said the drivers are on the pixel so they can install to computer when connected.
Click to expand...
Click to collapse
please do not take this the wrong way, those people are wrong.
The drivers are not "on the pixel"
I am on the latest insider preview of Windows 10 and have other weird stuff going on with build 15007 so if the android sdk doesn't fix it I will just reimage my pc.
It is time again anyways.
Thanks for your help.
joe ferreira said:
please do not take this the wrong way, those people are wrong.
The drivers are not "on the pixel"
I am on the latest insider preview of Windows 10 and have other weird stuff going on with build 15007 so if the android sdk doesn't fix it I will just reimage my pc.
It is time again anyways.
Thanks for your help.
Click to expand...
Click to collapse
Yea I assume something didn't sound right but didn't pay attention. I did a clean install on windows 7 on a new SSD the other day and didn't have to download android studio or any drivers. I hate windows 10
Edit. Like I said I never looked into it but I found this just now. Who's knows..
"Previous iterations of Android have removed the Mass Storage capability which made the phone act as an USB. Instead of that, we have MTP (Media Transfer Protocol). These standard MTP drivers come bundled with the phone and no need for separate installation.
ok let me explain a different way.
Plug in your phone.
open device manager
expand portable devices
double click on Pixel XL
Click the Driver Tab
This will show you that the MTP driver for the Pixel XL is provided by Microsoft and written on 6/21/2006.
This is the Microsoft provided generic driver for all MTP devices.
Google provides directions here... https://developer.android.com/studio/run/oem-usb.html#InstallingDriver
for how to update the MTP driver for android devices.
I wasted the last hour downloading Android Studio to check out it's usb driver and it is the same as the ones in the other 2 packages.
Off to wipe my PC.
So for the past few hours, Ive been having issues running the HTC RUU on my x64 Windows 10 Pro Laptop. After countless downloads and installs, I figure I share my solution for those in the future.
Problem: HTC RUU will not run, It will go to Accept or Decline T&E, then goto InstallShield, but does nothing after.
Solution:
HTC Sync
ADB Drivers
DotNet
Visual C++ 2008 x86
Make sure RUU.EXE has compatibility mode set to Windows 7 or XP SP3 ( tried both and got them to work on each setting )
Ive un-installed and re-installed so many versions of each. But only the Visual C++ is what really matters. Even if you're on x64 OS, you will need to install Visual C++ 2008 x86. Because The HTC RUU looks for the x86 files/directories.
Google the downloads and links.
Hope this saves someone a few hours of headaches or in my case 3 hours.
Cheers
-Wayne
are you on a custom ROM or a stock Sense ROM? I had trouble RUU-ing a stock package to update my firmware because of an issue with fastboot and LineageOS. I believe you can place a zip in the root of your SD card (it has to be named 2PS6IMG.zip) and flash it from bootloader mode or some similar mode. Fastboot worked fine while I was on the stock ROM
hello
RyanCanning said:
are you on a custom ROM or a stock Sense ROM? I had trouble RUU-ing a stock package to update my firmware because of an issue with fastboot and LineageOS. I believe you can place a zip in the root of your SD card (it has to be named 2PS6IMG.zip) and flash it from bootloader mode or some similar mode. Fastboot worked fine while I was on the stock ROM
Click to expand...
Click to collapse
you cant run ruu if you are bootloader unlocked, and is obligated is relock bootloader -fastboot oem lock that let you run the ruu again,after you relock and run the ruu , you can unlock the bootloader if want,and install another recovery, and rom
korko said:
you cant run ruu if you are bootloader unlocked, and is obligated is relock bootloader -fastboot oem lock that let you run the ruu again,after you relock and run the ruu , you can unlock the bootloader if want,and install another recovery, and rom
Click to expand...
Click to collapse
There is absolutely no requirement to relock the bootloader to flash an RUU or for that matter anything else on HTC 10.
shortyboy said:
So for the past few hours, Ive been having issues running the HTC RUU on my x64 Windows 10 Pro Laptop. After countless downloads and installs, I figure I share my solution for those in the future.
Problem: HTC RUU will not run, It will go to Accept or Decline T&E, then goto InstallShield, but does nothing after.
Solution:
HTC Sync
ADB Drivers
DotNet
Visual C++ 2008 x86
Make sure RUU.EXE has compatibility mode set to Windows 7 or XP SP3 ( tried both and got them to work on each setting )
Ive un-installed and re-installed so many versions of each. But only the Visual C++ is what really matters. Even if you're on x64 OS, you will need to install Visual C++ 2008 x86. Because The HTC RUU looks for the x86 files/directories.
Google the downloads and links.
Hope this saves someone a few hours of headaches or in my case 3 hours.
Cheers
-Wayne
Click to expand...
Click to collapse
I managed to run the US Unlocked RUU (2.51.617.1.exe) yesterday without (too many) issues.
I am on Win 10 Pro x64 (fall creator update).
From working with my previous HTC (ONE), I had already working HTC drivers, adb/fastboot, and registry hack so Win 10 can communicate with HTC devices over USB in fastboot.
Of note, I also do a bit of programming, so I have Visual C++ installed on this computer.
I ran the RUU.exe in admin mode. (NO compatibility modes set.) It was slooooow to load & run. I thought that the program was broken, but it eventually started. It was like 3 minutes before InstallShield open, then some minutes between each of the "questions" screens. I opened hardware monitor and noted no increased CPU/memory/Lan usages, so I am not sure what all the waiting was. <I have a reasonably fast setup - overclocked Intel desktop, SSD, Gb wired internet ... all the time this was running , I noted only like <10% usage of resources on my machine.>
But once the program got to detecting the phone, and actually doing the update, it was quite fast & painless.
I am pretty sure that the RUU running in slo-mo isn't normal, but at least it worked!
The problem sounds very familiar! Will definitely try with Visual C++ 2008 x86
How about all the rest? HTC Sync, ADB Drivers, DotNet… I’m only installing Windows on one of my Macs in order to run this RUU
Also… do you have an idea if I’ll get the same problem in Win 7? I’m not going to use it anyway, so I don’t really care which version of Windows I install.