Hi!
I have just installed Windows 8 64bit on my PC. Now I want to use flashtool (flashtool-0.9.7.0-windows).
However, it's telling me that I need some drivers before I can flash my phone (xperia play r800i). I tried using this method:
sewer56lol said:
You have to disable driver signature checks as windows won't allow them, if you know how then upon boot go to troubleshoot settings (If you do not dual boot then you are forced to pull in your installation CD and go to Repair Computer section)
Then you go to advanced settings and after you hit boot in Safe Mode, reboot and then install the drivers and after that you need to reboot again to go to normal mode.
Click to expand...
Click to collapse
However, I think that I'm failing miserably. I get this error (while installing the drivers in failsafe mode):
DPInst.exe does not execute on your current Operating System.
Click to expand...
Click to collapse
The drivers I am installing is:
"Sony Ericsson Xperia arc, Xperia Neo, Xperia PLAY, Xperia acro IS11S, Xperia acro SO-02C drivers"
(From a list inside the program "C:\Flashtool\drivers\Flashtool-drivers.exe")
I also tried to do something listed on MSDN:
Thanks Marilyn and Hadron for your responses. It turns out I finally came across the solution I was looking for shortly after posting this. Here's what I did:
Open a command prompt as an admin and type:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS (hit Enter)
bcdedit -set TESTSIGNING ON (hit Enter)
I might have rebooted after that. That put the machine in test mode, like I was going for, and allowed me to install the unverified test driver.
Click to expand...
Click to collapse
From: http://social.msdn.microsoft.com/Forums/en-US/windowsdeveloperpreviewgeneral/thread/941a4bf5-84d3-4bc3-88c6-96f30b787a3c/
But that failed too. Didn't really give me anything but the same error.
I am using Flashtool 64, since I'm on a 64 bit computer.
ANY HELP APPRECIATED!
/edit
When I try to execute the drivers in normal mode (ie. not fail safe) I get this:
" Driver name / status
[ ✓ ] Sony Ericsson (WinUsb) sa0102AdbDeviceClass (12/10/2010 2.0.0010.20010) / Ready to use
[ X ] Sony Ericsson Net (11/18/2010 6.0.6000.16388) / Install failed"
Did you check the flash box & fastboot box when choosing the drivers to install. They are at the bottom of the drivers selection.
Sent from my R800x using xda app-developers app
Lordomn said:
Did you check the flash box & fastboot box when choosing the drivers to install. They are at the bottom of the drivers selection.
Sent from my R800x using xda app-developers app
Click to expand...
Click to collapse
I have tried it now. The results can be seen in this video I've made:
Installation of the drivers
As you can see, it fails to install the drivers.
I have a windows 7 laptop, but its just so slow to work with compared to my desktop w/ w8. The laptop basically have 512 mb ram & 1.66 ghz cpu.
Hope someone can help me fix this issue.
Have you unlocked your bootloader?
E: Never mind. Have you tried to do it manually or through flashtool via adb?
Sent from my R800x using xda app-developers app
was there a solution?
I am facing the same problem here
hoppy_barzed said:
was there a solution?
I am facing the same problem here
Click to expand...
Click to collapse
I dont think there is a fix. Because windows 8 doesn't allow programs on your computer outside the windows marketplace. (correct me if im wrong)
I think your right cherry.
Sent from my R800x
wait... i'm still on the windows 8 consumer preview and was able to flash and unlock my phone both on the same day!...
x1rocket said:
wait... i'm still on the windows 8 consumer preview and was able to flash and unlock my phone both on the same day!...
Click to expand...
Click to collapse
What you tested was the beta. The other guy has the final product of windows 8 which is a different kind of beat.
New Info: In order to install applicatons on your windows 8 machine the applocation must have the approval from microsoft. Ouch..... Im stickin with windows 7 then maybe for good if Microsoft is going this route.
are the drivers just not installing altogether or do you get a can't start error?
chery2k said:
New Info: In order to install applicatons on your windows 8 machine the applocation must have the approval from microsoft. Ouch..... Im stickin with windows 7 then maybe for good if Microsoft is going this route.
Click to expand...
Click to collapse
where did you here that?
edit: did you restart your computer after running the bcdedit commands?
chery2k said:
What you tested was the beta. The other guy has the final product of windows 8 which is a different kind of beat.
New Info: In order to install applicatons on your windows 8 machine the applocation must have the approval from microsoft. Ouch..... Im stickin with windows 7 then maybe for good if Microsoft is going this route.
Click to expand...
Click to collapse
what do you mean approval... do you mean that green box saying not recognised... something like this [found in google] as I cant remember my last time having it but remember when installing flash tool it happened
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I clicked advanced I think then run or something like that... sorry if im no use but trying to track my memory to help fix it for you and others and yes im still in the beta as of now
chery2k said:
What you tested was the beta. The other guy has the final product of windows 8 which is a different kind of beat.
New Info: In order to install applicatons on your windows 8 machine the applocation must have the approval from microsoft. Ouch..... Im stickin with windows 7 then maybe for good if Microsoft is going this route.
Click to expand...
Click to collapse
totally agree with you chery2k just stick to win7 untill oxide& crew have a fix btw I think win8 is S***
also which version of flashtool did u guys try as 0.9.0.0 was released recently and new update coming soon(or may be out).
try this
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
reboot
download drivers (test signed a few)
try to run dpinst64 (if that fails)
manually install them
report back
also smartscreen can be turned off during install of windows 8
me too..
I do not think windows 8 it self the problem. I tested flashing with flashtool 0.9.9.0 in a windows 8 VM, the driver appear to be installed and it attempted to flash, but the phone would disconnect before it could flash. I think the reason for that is the VM.
On my VM i have smartscreen and UAC turned off
the drivers i used are in my previous post
I can confirm drivers are not working anymore on Windows 8....:crying:
to continue with my last post I think the reason people are having problems is USER ERROR and not they are not willing to try and fix it them self.
i installed flash tool and the drivers on windows 8 32 bit without any problem or errors or pop up security screens the only screen i got was the driver not verified by windows crap and just installed it anyway and worked fine...if u just want to flash your phone just install the flashmode and fastboot drivers dont worry about the xperia play driver...and dont forget to disable your antivirus
rawstyle said:
Hi!
I have just installed Windows 8 64bit on my PC. Now I want to use flashtool (flashtool-0.9.7.0-windows).
However, it's telling me that I need some drivers before I can flash my phone (xperia play r800i). I tried using this method:
However, I think that I'm failing miserably. I get this error (while installing the drivers in failsafe mode):
The drivers I am installing is:
"Sony Ericsson Xperia arc, Xperia Neo, Xperia PLAY, Xperia acro IS11S, Xperia acro SO-02C drivers"
(From a list inside the program "C:\Flashtool\drivers\Flashtool-drivers.exe")
I also tried to do something listed on MSDN:
From: http://social.msdn.microsoft.com/Forums/en-US/windowsdeveloperpreviewgeneral/thread/941a4bf5-84d3-4bc3-88c6-96f30b787a3c/
But that failed too. Didn't really give me anything but the same error.
I am using Flashtool 64, since I'm on a 64 bit computer.
ANY HELP APPRECIATED!
/edit
When I try to execute the drivers in normal mode (ie. not fail safe) I get this:
" Driver name / status
[ ✓ ] Sony Ericsson (WinUsb) sa0102AdbDeviceClass (12/10/2010 2.0.0010.20010) / Ready to use
[ X ] Sony Ericsson Net (11/18/2010 6.0.6000.16388) / Install failed"
Click to expand...
Click to collapse
I had a similar problem the other day while working on getting my r800at's fastboot to be identified in Flashtool. I did the same as you, regarding trying to install the Xperia Drivers from the flashtool app itself, but it didn't work.
What I did to successfully install drivers was use SuperOneClick. There should be an option in the Advanced Tab to "Check Drivers", and since it won't find any, it'll ask if you want it to forcibly install the drivers. Allow it to, and it should immediately have working drivers. This worked on a Windows 7 64-bit OS, I'm unsure of how it'll pan out with W8, but good luck.
I'm running win8 too, in the flashtool folder in the C: drive, there should be a drivers folder, just run the installer that's in there. make sure the android SDK is installed first. Did you install android SDK?
Related
Good afternoon,
I see a few people want the 64bit version of the emulator so here it is re packaged into an installer with shorcuts on start menu and desktop for your convenience.
I have also made a 32bit installer to go along with it.
Both the file sets are pulled from the very latest developer suite.
The msi file is 76meg and has the image pre loaded into it.
Just double click to install once installed click the Shortcut on your desktop or start menu.
Enjoy
Links dead
Please enjoy this new links with thanks to member Julianrl
on this post http://forum.xda-developers.com/showpost.php?p=11953242&postcount=91
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey this emu seems to work on windows 7 x64!! had to install it with
"msiexec /i setup.msi" from a command promt (run as administrator) though, but it works!! thanks
ultimasnake said:
Hey this emu seems to work on windows 7 x64!! had to install it with
"msiexec /i setup.msi" from a command promt (run as administrator) though, but it works!! thanks
Click to expand...
Click to collapse
strange! It should be a double click, once you typed that command did you get the gui installer?
Installing using not command promt gives an error, nothing will be copied/extracted/installed.
SaturnusDJ said:
Installing using not command promt gives an error, nothing will be copied/extracted/installed.
Click to expand...
Click to collapse
Do you get the same issues if you right click it and run as administrator?
That option isn't available, I think this is because it is a .msi installer. When reaching the last screen of the installer the button to start the progress has the shield that requires an admin typing his pass, so I gave the pass, but after a while the error shows up:
SaturnusDJ said:
That option isn't available, I think this is because it is a .msi installer. When reaching the last screen of the installer the button to start the progress has the shield that requires an admin typing his pass, so I gave the pass, but after a while the error shows up:
Click to expand...
Click to collapse
what 64bit os are you on?
Working.
Downloaded from rapidshare.
Clicked open. Next, Next!
All done.
Working!
Windows 7 x64
ellite said:
Downloaded from rapidshare.
Clicked open. Next, Next!
All done.
Working!
Windows 7 x64
Click to expand...
Click to collapse
Exactly how it should be, thanks for the feedback..
SaturnusDJ said:
That option isn't available, I think this is because it is a .msi installer. When reaching the last screen of the installer the button to start the progress has the shield that requires an admin typing his pass, so I gave the pass, but after a while the error shows up:
Click to expand...
Click to collapse
I get the same error except I never get prompted for an admin password- it just starts 'copying files' and then flashes to that scren.
Try copying a couple of the smaller size microsoft items from my list, I am on server 2008 r2 on this machine and it works fine...
here's what mine looks like.
I have just installed it with no issues with the below installed programs/ ms addons, have you tried changing the installation directory, do you have administrator rights on the machine?
I also have the same error as previously posted.
I am running Windows 7 Ultimate 64bit. I will try playing around with my currently installed MS Visual Studio etc (I have MS Visual Studio 2010 installed).
anarchyuk said:
what 64bit os are you on?
Click to expand...
Click to collapse
W7 Pro 64-bit.
SaturnusDJ said:
W7 Pro 64-bit.
Click to expand...
Click to collapse
The only thing I can think of is some issue with admin rights, only a few out of the many many downloads of the x64 verison have had issues.
Turn User Account Control off (UAC) and install. I tried on win7 home p. and works well
>control Panel>User Accounts>Change User Account Control
anarchyuk said:
strange! It should be a double click, once you typed that command did you get the gui installer?
Click to expand...
Click to collapse
I tried many different methods to get the x86 installer working on Windows 7 Professional x86 and nothing worked except that specific method:
Run msiexec /i setupx86.msi from an Admin Command Prompt.
I tried all the methods mentioned, even extracted the .msi contents and still nothing worked, but that Admin Command Prompt and that one command got it working. Not sure what the issue actually is, and I ever tried disabling UAC and then executing it from the Admin Command Prompt and still no go - only that specific method worked in my situation.
ultimasnake said:
Hey this emu seems to work on windows 7 x64!! had to install it with
"msiexec /i setup.msi" from a command promt (run as administrator) though, but it works!! thanks
Click to expand...
Click to collapse
It doesn't work at all for me, even after following this command.
I do get the installer window, and click next a few times, get the status bars and click finish.
However, there are no shortcuts on my desktop or in my start menu, and it hasn't copied any files.
I tried using the default install directory and D:\Software\WP7Emu\ but neither worked.
I am on Win 7 Prof x64, and downloaded the x64 version from megaupload
I've found the solution of this problem, try to go to compatibility assistant of Windows 7 and launch the program, after that the installation work perfectly
Very good!
Incredible 2 Custom Recovery Installer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download removed until bugs fixed.
Requirements
Operating System: Windows XP with .NET 2.0, Windows Vista, Windows 7
MUST RUN AS ADMIN TO INSTALL DRIVERS!
Changelog
v12.02.23.2
1. Fixed deadlock when app starts without ADB server already running, added start-up status window.
2. Automatically scan for devices after installing drivers.
v12.02.23
Initial Release
Summary
This tool allows you to try out different recoveries very easily. I was frustrated with the different methods for downloading and installing different recoveries and didn't like that there wasn't really a central place to find them so I wrote this tool to use ADB and Fastboot to very quickly switch between them. This tool is very far from done and more features and probably a complete overhaul are at some point in the near future.
Bugs
1. Cannot select between different devices although it appears to allow you to do so. It might flash to a different phone if you have more than one hooked up in fastboot mode.
2. Doesn't actually check to see if the phone is an Inc 2.
3. Sometimes the recoveries get unlocked even though the phone isn't in fastboot mode, if you click one of them fastboot.exe will wait on the phone forever and freeze the program.
Upcoming Improvements
1. Much improved download size.
2. Ability to try recoveries before flashing them.
3. Threaded device state monitoring - gets rid of prompts and keeps the app from freezing.
4. Ability to select between multiple devices.
5. Eventually a better GUI.
6. More consistency throughout the program.
Reserved for future use.
im gonna try this now, thanks
EDIT: not working on Win7 x64. the program wont run. It just goes not responding as soon as i start it both as admin and normal
werdna87 said:
im gonna try this now, thanks]
EDIT: not working on Win7 x64. the program wont run. It just goes not responding as soon as i start it both as admin and normal
Click to expand...
Click to collapse
I had the same result on Win7 x64.
Update v12.02.23.2
Changelog in first post.
Fixed.
Thanks for pointing out the bug. It was the middle of the night and I was tired, didn't think to try to start the app without ADB already running. Should be fixed now in the first post.
still not working for me same problem
OP,
Are we supposed to manually install the drivers? If so, the x64 drivers will not install, even when run as administrator.
I am also getting the same result with the new files. I even tried killing and starting adb to no avail.
werdna87 said:
still not working for me same problem
Click to expand...
Click to collapse
Start ADB before running the program and let me know if that works. I did find the problem you were having and solved it on my end. Do you see a window that says "Starting ADB . . ." when you run the program? If not, make sure you're running the current version.
FC127 said:
OP,
Are we supposed to manually install the drivers? If so, the x64 drivers will not install, even when run as administrator.
I am also getting the same result with the new files. I even tried killing and starting adb to no avail.
Click to expand...
Click to collapse
Make sure your phone is plugged in before installing the drivers. You might need to uninstall other drivers first or you might not need to install the drivers at all. Does it find your phone if you just skip the driver installation?
Still no go on two different computers both Win7 x64... If I try to install the drivers separately it says that the drivers cannot be installed.
Edit: Upon further investigation, I tried to manually install again by directing the device manager to the EXACT file and this is what I get.
[/URL][/IMG]
You shouldn't have to install the drivers just to get the program to open. Can you describe exactly what's happening?
Grouper said:
You shouldn't have to install the drivers just to get the program to open. Can you describe exactly what's happening?
Click to expand...
Click to collapse
Yeah, I know... When I try to open your exe file it immediately says the program is not responding. I have tried to execute as administrator and run in compatibility mode.
[/URL][/IMG]
FC127 said:
Yeah, I know... When I try to open your exe file it immediately says the program is not responding. I have tried to execute as administrator and run in compatibility mode.
[/URL][/IMG]
Click to expand...
Click to collapse
I have the same issue stated here
Sent from my ADR6425LVW using XDA App
Alright, removed the download link. Guess I'll have to setup a VM to figure this out. It works for me with the included drivers OR the "My HTC" drivers and I'm not having any issues with the app freezing so it must be something about this setup.
Hi
I've tried instal a new rom on my Galaxy Nexus (i9250) but I fail.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Opening Update Package..."
"Installing Package..."
"Set_metadate_recursive: some changes failed
"E:Error in /sdcard/cm-11-20140607-NIGHTLY-maguro.zip
(Status 7)
Instalation aborted
I'm a new newbie and I cant post directly in downloaded rom : http://forum.xda-developers.com/galaxy-nexus/development/rom-carbonrom-kitkat-t2635637
I want to instal a new Rom on my device but I cant 'cause it doesn't have memory card slot and windows 8 didn't recognize my device
How can I copy the files on my deivce?
Anyone can help me to fix this problem?
you probably need to update your recovery img version, easiest way is using fastboot or a toolkit, like wugfresh toolkit(Google wugfresh Gnex it will come right up)
you need to install the drivers.for windows to recognize galaxy nexus as attached, wugfresh can do THAT for you as well.
although I'm a proponent of using manual methods like adb/fastboot, wugfresh can help get you started in the right direction
Wugfresh
First of all , thanks for quick reply.
You're right.My recovery img is old and didn't update since about a year and a half.
I install wugfresh but when I run the program, that doesn't recognize the device.
When I connect the mobile to laptop, I heard a sound about plug a USB Device.
The Mobile phone is on bootloader....
and becaue I didn't know device build number, I click Auto Detect Device + Build....
But doesmn't happen anything
if you aren't worried about losing any user data, first flash a factory stock image which will put device back to out of box state, then you can pick which build and such,
or, before that, do a quick google search for "xda, galaxy nexus, windows 8.1 driver issue" I think I recall someone having similar issues and getting them resolved and the thread should have the info you need in it.
let us know if you find the info you need.
Wugfresh
I Use wugfresh (Nexus Root Toolkit)
Before that , I installed the adb drivers and also change my o.s from Win8 to win XP.
but I see this error while repairing my phone : (the attached file)
I'm so confused...
I didn't what to do...
Install the adb and fastboot drivers.
EDIT: Use the "Full Driver Installation Guide"
Sent from my Galaxy Nexus using XDA Free mobile app
AGoogleUser said:
Install the adb and fastboot drivers.
EDIT: Use the "Full Driver Installation Guide"
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
I'm trying....
I Couldn't
I even try this : http://forum.xda-developers.com/showthread.php?t=2588979
It doesn't recognise my phone.
I feel dumb!
Let me explain my problem by photos :
I run nexus Root Toolkit
In advanced utilities , click on "Launch"
In apperaed window , "Boot Temporary" , I click on "Custom Recovery", then I must browse the file "openrecovery-twrp-2.7.0.0-maguro.img"
After browse the file , this Message Appear : Reebooting your device into bootloader . . .
Then after afew secondes , This message blowes my mind : Fastboot Device Was Not Found . . . .
Also in other parts of Nexus Root Toolkit I have the same problem....
Is there anyway to solv ethis problem?
I would recommend removing the drivers that are installed. it seems that the wrong ones, or maybe something just "borked" with them, happened on original install.
when you plug in device, go into device manager, should be able to right click on your device and uninstall drivers.
then I recommend putting device in bootloader mode. plug in, and see if it installs the drivers automatically for you.
there should also be an.option in wug to "install drivers" I think.
(in your pictures, window on the right side, "Full Driver install....", long button on the top)
::::TRY THIS FIRST::::
I just noticed that you have chosen ICS for model/OS. it is probably trying to use the old fastboot binary for it or something, change that and try 4.2 or even 4.3, you could also try 4.1 but I'm thinking the 4.2or4.3 choice will work for you.
---------- Post added at 01:19 PM ---------- Previous post was at 01:17 PM ----------
do you KNOW how to manually put phone into bootloader/fastboot mode correct?
if not, from powered down state, hold power, volume up, and volume down, all at the same time for a few seconds, it will vibrate, and bring up the bootloader.
I know on my machine, I befoee had to uninstall drivers, then plugged device in while in bootloader mode, and waited as it installed automatically the correct drivers needed.
A million times thanks to you.............................
You saved me
You're my hero....
Thank u so much for your patience & helpful guides....
God bless you....:good::good::good::good::good::good::good:
arashcd said:
A million times thanks to you.............................
You saved me
You're my hero....
Thank u so much for your patience & helpful guides....
God bless you....:good::good::good::good::good::good::good:
Click to expand...
Click to collapse
no problem at all buddy! happy to help!
can I ask what exactly solved it do you know?
also, if issue is resolved, if you can edit your initial post's thread title to say [SOLVED] in front so others know the issue is resolved and others looking for the info provided with the same issue can easily find the fix/steps if needed.
(I don't know if you use tapatalk for forum browsing, but you may have to edit the title of thread via web browser)
if you need anything else feel free to ask here or PM!
I think my problem returns to install drivers.
After your last guide, I removed drivers and for install drivers, I use from Nexus Root Toolkit....
Just one Question :
For last time : How Can I add "Solved" to topic title?
I didn't find any button to do that...
arashcd said:
I think my problem returns to install drivers.
After your last guide, I removed drivers and for install drivers, I use from Nexus Root Toolkit....
Just one Question :
For last time : How Can I add "Solved" to topic title?
I didn't find any button to do that...
Click to expand...
Click to collapse
go to your initial post, there should be button below it that says "edit" or similar. click that, then you probably have to click "go advanced" or "advanced edit" or something like that, I think then you will be able to edit the post title.
if not it's not THAT important
Before you start, keep in mind that this may damage your device. I wouldn’t recommend trying this, but if you really want to, you can feel free to do so at your own risk.
Here is the list of supported devices:
•Nokia Lumia 920
•Nokia Lumia 925
•Nokia Lumia 929 (icon)
•Nokia Lumia 830
•Nokia Lumia 930
•Nokia Lumia 1520
•Nokia Lumia 635 (1GB RAM variant)
•Nokia Lumia 730
•Nokia Lumia 820
•Nokia Lumia 435
•Nokia Lumia 928
A. If you have one of the above devices, you are ready to go!Method 1(older, harder, but still functional)
1. Download both files from here.
2. Unzip both of the files on the folder
3. Open the folder wconnect, then install IpOverUsbInstaller.msi and vcredist_x86.exe
4. Go to your Windows 10 Mobile’s Settings page, then head over to Update & Security > For Developers and enable Developers Mode, as well as Device Discovery
5. Now go to the extracted wconnect folder, then open an elevated command prompt (Shift+right click > Open command window here)
6. After that, you’ll need to connect to the phone — and there’s two way of doing that (USB method is recommended): ◦If you want to connect using USB, type "wconnect.exe usb" and hit enter
6.1 And if you want to connect over Wi-Fi, type wconnect.exe 192.168.xxx.xxx (replace the xxx with your network’s IP)
7. Then it’ll ask for the pairing code, just type the pairing code and hit enter
8. After that, navigate to the extracted adb folder and open an elevated command prompt
9. To make sure that your device is connected, type adb devices and hit enter to show the list of devices that are connected
10. Lastly, place the APK file that you want to install on the same directory (adb folder) and type in adb install APKNAME.apk (replace APKNAME with the APK file’s name)
11. Just wait for it to do its thing and you should be able to install the Android app on your Windows 10 device
Method 2 (new, noob-proof)
1. Download the files here and extract them anywhere
2. Install "IpOverUsbInstaller" and "vcredist_x86"
2. Run "APKDeployment.exe"
3. On your phone go to "Settings/Update & Security/For developers" and enable "Developer mode" and "Device discovery" then press "Pair"
4. Connect your phone to USB, insert the code you got earlier from your phone, into APKDeployment app, then press pair. Your phone should appear as "emulator_555x on USB"
5. Now that you're paired, you can simply drag .apk's into the application then choose to deploy all.
Method 3 (even simpler)
1. Download the package from here and install it.
2. Follow app instructions.
Method 4
Install APKtoWin10m
Download Windows Bridge
On your pc go to "C:\Users\USERNAME\AppData\Roaming\APKTOW10M\connect" then extract the "Windows bridge" contents there. When asked, replace all files.
That's it, the tool should be fixed.
Credits go to @alb3530.
B. VERY IMPORTANT!
1. Do not disconnect the device while an apk is installing.
2. Do not reboot while your phone has Developer Mode Activated.
C. Errors you might encounter and how to fix them.
1. Status 9 - connection problem
If this happens, unregister you device using "Windows Phone Developper Registration 8.1", tool provided alongside Windows Phone 8.1 SDK, or download the lite version from here.Afterwards you will be able to access Developer settings again. Or Hard reset, your choice.
If the method above did not help, another fix is to go to device manager and uninstall these drivers [(coresponding to your device) also delete them if asked] then refresh, and let Windows reinstall them.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Status 14 - device not supported
Either your device is unsupported or you haven't installed "Developer Enhacements" update
To install Developer enhacements update, install Windows Insider from Store and Enroll, then check phone updates. It should show up there.
3. Developer menu crashes, wconnect app hangs
If this happens, unregister you device using "Windows Phone Developper Registration 8.1", tool provided alongside Windows Phone 8.1 SDK, or download the lite version from here.Afterwards you will be able to access Developer settings again. Or Hard reset, your choice.
4. Notification toggles flashing
Just reboot, but remember to disable Developer Mode first.
Source
Someone try this with nhl gamecenter lol
Sent from my iPhone using Tapatalk
COC working on my 1520
Y NO 525 Hardware issue
Use this tool to patch apps with google play services and install them on your phone........ Have Fun
HIT THANKS IF I HELPED YOU
Let's make a working app list. Quote this post to complete it.
Here I go
Facebook
Facebook Messenger
WhatsApp (with instant notifications working!!!)
NO WAY, I CAN NOT BELIVE WHAT I AM SEEING, YES IT WORKS, WHAT A F********************* KNOT BELIVE IT
funciona galera, realmente funciona
uowwww great job, it's works on my lumia 830
anyone tried iGO Primo?
anyone tried Sniper: Hitman ?
fyi, obb files/folders go here
\Data\Users\DefApps\APPDATA\Local\Aow\mnt\shell\emulated\0\Android\obb
after error
adb install "periscope 1.0.4.1.apk"
472 KB/s (9413825 bytes in 19.453s)
pkg: /data/local/tmp/periscope 1.0.4.1.apk
Failure [INSTALL_FAILED_(-2147023436)]
Click to expand...
Click to collapse
"For developers" mode not open anymore.
Anyone have a solution?
Cannot start iopverusb...but....there is a way...
dll is mising.
how to fix the "for developers" option crashing ?
Here's a list from someone on r/windowsphone on reddit: https://www.reddit.com/r/windowspho...all_android_apps_on_windows_10_mobile/ctvvtwj
eric5949:
Just installed Twitter and the Destiny Companion App, they work great, though i would turn off the 3D model in the Destiny app, it made it crash. Clearly project Astoria isn't finished, but damn if it doesn't work good.
Edit: Here's what I've tried.
Facebook: Crash
Messenger: Works, No notifications outside of app, no calling
Snapchat: New versions throw an error when you try to log in, old versions say to update
Destiny Companion App: Works, guardian 3D model may cause app to crash, turn it off in settings.
Amazon App with Store: Works, laggy though. Trying to install an app crashes the app.
Twitter: Works.
Google Play Services: Had to try...for science. Either fails to install or crashes.
Firefox: Crash on launch
Steam: Works
Wikia Game Guides: Works, though crashes sometimes, and some images fail to load
Hearthstone: Crashes with "Failed to download additional files from google play"
Clash of Clans: Works so far, haven't tried IAP because...im not spending money on that game...
Puzzle and Dragons: Not sure what i was expecting here, its hooked pretty hard into Google Play services. Crashed on launch.
TeamSpeak: Crash.
Teamviewer: App works, but it fails to connect to the internet.
Reddit is Fun: App itself works, crashes when logging in with message "not implemented yet"
Waze: Can't get location, forever initializing.
I will update with more as i try them.
Click to expand...
Click to collapse
tried angry birds 2, and COC (both work fine) before the dreaded "For developers" crashing and cant pair anymore.
denisf1981 said:
after error
"For developers" mode not open anymore.
Anyone have a solution?
Click to expand...
Click to collapse
Luiz Guilherme Pereira said:
how to fix the "for developers" option crashing ?
Click to expand...
Click to collapse
vcfan said:
tried angry birds 2, and COC (both work fine) before the dreaded "For developers" crashing and cant pair anymore.
Click to expand...
Click to collapse
Using Windows Phone 8.1 SDK, unregister your device, reboot, then try accesing developemt settings again.
XDRdaniel said:
Using Windows Phone 8.1 SDK, unregister your device, reboot, then try accesing developemt settings again.
Click to expand...
Click to collapse
excellent, it worked. I didn't have to reboot. just clicked unregister, then the dev settings opened fine again.
vcfan said:
fyi, obb files/folders go here
\Data\Users\DefApps\APPDATA\Local\Aow\mnt\shell\emulated\0\Android\obb
Click to expand...
Click to collapse
How can i copy a file to this path?
XDRdaniel said:
Using Windows Phone 8.1 SDK, unregister your device, reboot, then try accesing developemt settings again.
Click to expand...
Click to collapse
thank you, back to work
I'm starting to lose all hope in this device...
I bought my phone from, what I thought, was an official Xiaomi online store, my mistake, buyer beware, lesson learned. However. I have the phone, I like the form factor and all that, and the thought of trying to get a return from a Chinese company sounds like the kind of hassle I don't want to deal with. I'm well experienced in rooting/flashing devices (Nexus 5, OnePlus 2, OnePlus X, Xperia Z5c). I've done it a thousand times on these devices.
My new Mi5S came with "MIUI Global 8.6 | Stable 8.6.10.0(RM1100)" preinstalled.
I only found out after I bought it that the reseller installed this version. They apparently did this so they can make it a global rom. They installed Google play services, Play Store, removed chinese apps and made English the default language. That's great and all, but they also have the Locale setting locked in as China. It's unchangeable. And installing Google Launcher from the Play Store doesn't work (yet Pixel Launcher, downloaded from the web, works fine). Not a huge deal I guess.
Anyway, long story longer, I'm trying to unlock the bootloader.
I got permission, downloaded the Unlocker, VolDown+Power into Fastboot and ran the MiFlash unlocker.
It goes to 50% and then says "Couldn't verify device". That's where I'm stuck.
I've tried everything I can think of, and I just can't unlock the Bootloader.
Is anyone else having this same issue? Has anyone found a way to get TWRP on here?
Had the same issue when unlocking mine - two things worth checking: firstly, make sure the phone is signed in to the same Mi account that you have permission on (you can check it's "properly" linked by going to i.mi.com and clicking Find Device - if it shows as online, you're good). You don't need to use the Mi account at all after this, so once it's unlocked you can unlink and delete the account if you like.
Secondly, make sure the PC you're using has compatible ADB drivers on it - when it's linked by USB in FastBoot mode, make sure that it shows correctly in device manager. I had some weirdness with the previous global driver (still don't know why) and only ended up succeeding when I reinstalled straight from device manager.
MoonBuggy said:
Had the same issue when unlocking mine - two things worth checking: firstly, make sure the phone is signed in to the same Mi account that you have permission on (you can check it's "properly" linked by going to i.mi.com and clicking Find Device - if it shows as online, you're good). You don't need to use the Mi account at all after this, so once it's unlocked you can unlink and delete the account if you like.
Secondly, make sure the PC you're using has compatible ADB drivers on it - when it's linked by USB in FastBoot mode, make sure that it shows correctly in device manager. I had some weirdness with the previous global driver (still don't know why) and only ended up succeeding when I reinstalled straight from device manager.
Click to expand...
Click to collapse
I have verified that I'm using the proper account and that Mi Cloud sees my device as online.
Could you clarify which driver you ended up using?
You cannot unlock bootlader that easy. (Ive own mi5)... my english is not very good so i cannot describe all steps. Just find how to unlock mi5 bootloader. You have to request from xiaomi to let you unlock it. !!! AND I SEE NO PROBLEM HERE.
lummujaj said:
You cannot unlock bootlader that easy. (Ive own mi5)... my english is not very good so i cannot describe all steps. Just find how to unlock mi5 bootloader. You have to request from xiaomi to let you unlock it. !!! AND I SEE NO PROBLEM HERE.
Click to expand...
Click to collapse
I already have permission. Still doesn't work.
I used the driver from here: http://www.xiaomi.cn/content-19-6735-1.html - direct file link is http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
So, check this out. I loaded up the Mi PC software and instead of just clicking on R.Flash, I held shift then clicked R.Flash. It popped up a file select box and I was able to choose the official chinese ROM. It then installed it! No issues or anything. Once it was finished and it booted, I did a factory reset. The initial setup screen ran and I got in to the phone. I installed the Google Play Installer from the Mi Store and that was that.
I now have 8.0.10.0.
Didn't need to unlock the bootloader or anything.
*phew*
dgrasley said:
So, check this out. I loaded up the Mi PC software and instead of just clicking on R.Flash, I held shift then clicked R.Flash. It popped up a file select box and I was able to choose the official chinese ROM. It then installed it! No issues or anything. Once it was finished and it booted, I did a factory reset. The initial setup screen ran and I got in to the phone. I installed the Google Play Installer from the Mi Store and that was that.
I now have 8.0.10.0.
Didn't need to unlock the bootloader or anything.
*phew*
Click to expand...
Click to collapse
You've actually completed the first step in unlocking your bootloader - you need to make sure you are using an official ROM and not a so called "Vendor ROM".
I am still waiting patiently for my Mi5s to get here...
If "fastboot devices" shows your mi5s in fastboot mode right before unlocking - then you have the right driver and the 50% problem should be solved.
CL0SeY said:
You've actually completed the first step in unlocking your bootloader - you need to make sure you are using an official ROM and not a so called "Vendor ROM".
You can unlock in vendor rom..
Without unlocking you should be able to flash official rom using miflash/fastboot
Vendor rom updater/recovery may not word (did not work for me) to update to official chinese rom..
Click to expand...
Click to collapse
MoonBuggy said:
I used the driver from here: http://www.xiaomi.cn/content-19-6735-1.html - direct file link is http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
Click to expand...
Click to collapse
any funky method you have to install the driver? i am struggling here. adb is fine, but fastboot shows no devices. have tried every driver i can find including above!
edit - for the record i disabled driver signature verification in win10 and installed the above drivers, and still no luck. here is my cmd output
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
when it reboot into fastboot a new driver installed on windows and i can see the android bootloader interface in device manager but still no fastboot. weird? also miflash is showing the device when the phone is in fastboot.
---------- Post added 28th October 2016 at 00:33 ---------- Previous post was 27th October 2016 at 23:37 ----------
ok fixed the driver problem. for anyone else stumbling across this:
reboot to fastboot mode, then in device manager update the bootloader interface driver with the google driver that comes inside the C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Driver folder. (you need to have miflash installed obviously)
note that windows10 you may have to disable driver signature verification for this.
:good:
I got my phone today and had the same problem but i solved it at last, i installed the chinese dev rom and then it worked to unlock the bootloader and i have installed xiaomi.eu rom and works great.
I had the same issue, for me it was indeed the fastboot driver.
The solution for me was to put phone in fastboot, connected usb.
In device manager you have to look android bootloader interface, deinstall, and let windows install driver itself.
For me that was the solution...
From what i have read everywhere, using a windows 7 machine instead off windows 10 will solve the issue for sure
marcel112 said:
I had the same issue, for me it was indeed the fastboot driver.
The solution for me was to put phone in fastboot, connected usb.
In device manager you have to look android bootloader interface, deinstall, and let windows install driver itself.
For me that was the solution...
From what i have read everywhere, using a windows 7 machine instead off windows 10 will solve the issue for sure
Click to expand...
Click to collapse
What OS did you use when you successfully did this? Windows 10 or Windows 7 or other?
dgrasley said:
What OS did you use when you successfully did this? Windows 10 or Windows 7 or other?
Click to expand...
Click to collapse
I was using a windows 10 machine, but i didnt succeed severall times.
The thing i did was trying to unlock, 50% error, then boot the phone, turned off find Mi phone, rebooted, tried again still no go, rebooted again, tunred on find Mi phone again, then tried unlocking again...: Eureka!!
That was the solution, so i tried that on a different machine with no drives installed at all!!