As title says, I'm looking for the Windows 10 Drivers for the Ployer Momo8W Dual Boot Tablet.
While updating the Windows 10 version of my tablet an error occured during the installation of the new version. I managed to do a clean install of windows 10 from an USB stick but now I have several "unknown devices" in the device manager, the touch display doesn't respond and screen rotation doesn't work either (everything is upside down as in 180° distorted)
I have found a thread with Ployer Momo7w drivers here on xda, but I'm not sure if they would work on my momo8w though. I hope someone can help me.
Hey buddy.
I'm going through similar with my Momo9w, while playing around trying to make it dual boot I messed it up, removed recovery to accidentally.
Finally managed to get a clean install of Windows 10 on it, then had another go today and now need to go through it all again! Worth a go.
Anyway I wanted to say the Momo7w drivers posted seem to work with my 9W, so I'm sure they will with your 8w.
The only issue I had on win 10 was the touch screen calibration not working right, the touch point was off from where I was touching it. However there is a Chuwi topic on here I've jist been reading with similar problems and fixes, so when I am back to win 10 I will try those.
Ian
centuryheli said:
The only issue I had on win 10 was the touch screen calibration not working right, the touch point was off from where I was touching it.
Click to expand...
Click to collapse
I've got the same issue here. Did you manage to solve that problem?
20qwertz12 said:
I've got the same issue here. Did you manage to solve that problem?
Click to expand...
Click to collapse
Hey Buddy.
Ah, I'm still struggling to be honest.
Originally I installed Windows 8.1 and got the touch screen working fine after a few tries, then it updated to Windows 10 and there was no problem. Then in my stupidity I tried installing a dual boot with Android again and now I'm back to the beginning with Win 8.1 beside me and trying to fix the calibration again!
From the time before it is something to do with the touch screen driver and the Windows driver it installs for the screen, I've read the touch drivers need to be installed after in this case.
I'm currently sat beside the tablet trying to get the touch screen working on Win 8.1 again.
Ian
Thx for the tip with the chuwi thread, managed to install the touch screen drivers and it's now working again
I hope you can solve that problem of yours too
Hi all. Ehhh... Not very closely related, but you guys here appear to be the best experts on the topic on the whole wide internet, so I hope you can help me out.
Just bought a Ployer momo8w dual boot for my daughter, but the accelerometer won't work in Android.
My unit came with a new firmware, Android 5.1.1 and Windows 10. The accelerometer does work in W10, but would not even show up in Cpu-z or sensorbox in Android. Is there any way to 'hack it', or any way to downgrade the firmware to Android 4.4/W8.1 or whatever exact version these used to be shipped with? I could not even google anyone else having this problem, but I have two devices (two daughters) and they both have this issue.
ME TOO HOW INSTALL win10 driver ?
I do a backup using powershell like i found around here... and uploaded to mega.
Here's the link:
Drivers:
hXXps://mega.nz/#!SsdVnSjJ!XPHRqwMmOHVye7XxVoD1qdu95jy7bkV_5BVBBDR-rVE
And for a touchscreen 100% working you need to copy SileadTouch.fw to System32\Drivers folder and reboot.
SileadTouch:
hXXps://mega.nz/#!qgdBhSwS!pF0y7NfyC6UHVIGgDFfcwdnTemya7wUZe4Dt_o2htC0
And for fully working Video, i used Intel Driver Update Utility, downloaded from intel's site, here:
hXXXs://downloadcenter.intel.com/download/25977/Intel-Graphics-Driver-for-Windows-10-and-Windows-7-8-1-15-33-
but you can download the driver from here:
XxXxs://mega.nz/#!W5NUTYZI!sBaGoJhJl0NZvALsBpCMOmvgqdIOTvOVJwabioVBIdc
The only thing that it's not working for me i'ts the mSD Card Reader
i downloaded the first link, but which folder do i put it in? please help im struggeling with the touch
I know this thread is quite old... but I managed to get some drivers at least.
For Bluetooth you can download the official Realtek drivers here:
realtek.com/en/component/zoo/category/rtl8723bs-software
For audio I found this (lenovo website):
support.lenovo.com/us/en/downloads/ds040044
But for touch I still have no clue! The SileadTouch file didn´t work for me.
Related
so i am new to android and i decided " hey why don't i try to root my nexus" so i tried and i cant get any father that checking if the computer can see my device which it cant for some reason. so i went online i figured out that i don't have the usb driver for android. so after that i tried to down load then and i even installed them and restarted my computer and it still wont work. so if any one can help me with my problem it would be greatly appreciated.
On Home Screen, press menu>settings>applications>development and make sure USB debugging is checked.
What OS you running?
Specs would help, where did you get your drivers? What other software have you tried?
i turned on the debugging and it still hasnt worked
i am running xp. i downloaded the android sdk from here
developer.android.com
i just want to put the modaco desire rom on my phone that my onl reason for wanting to root. i really like the sense ui
I am having a similar problem, so i might as well use this thread instead of creating a new one.
I have a dual boot computer, win7 and fedora, both have SDK. I unlocked my nexus one with windows, as i noticed the commands were considerably easier, or at least they don't work when i plug the linux ones into fedora.
Last night i was going to push the undervolt kernel so i plugged my n1 while in win7, It instantly came up complaining about drivers, which i had already installed and had previously worked, i went to re-install them, and windows says they are up to date, but still no luck recognising the device (Debugging mode is definately on)
So i switched to fedora, no driver pop ups obviously, but when i try to push the kernel through, it does not recognise the device.
In the bootloader it says "fastboot usb" while plugged in.
I can't pinpoint when it stopped working, but the last time i used fastboot was to put the RA recovery, since then i flashed CM 5.0.2, CM 5.0.3.1, the desire rom, and used a nandroid restore to get back to 5.0.3.1
Anyone got any ideas? Without fastboot i am pretty much restricted to flashing .zip files from the recovery.
yeah i cant even unlock mine its so frustrating
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
drbrendin said:
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
I tried all day too like a gazillion times.... and wonder does everyone have driver issues? I tried with my XP computer and windows 7, no go, then I read posts people having the same issue, then they just post " nevermind got it" and didn't even write what they did to get it.......
Click to expand...
Click to collapse
not everyone is a dev
Ok, I have my Nexus One set up so I can use with via Windows 7 (desktop) or Ubuntu (Laptop).
The Linux part is a bit more involved, but since everyone is running Windows (unless I missed something), I will work there.
First of all, your phone needs to be in Dev mode (which was covered earlier).
With the phone UNPLUGGED from the PC, uninstall any previous SDK installs you have and be sure to remove the directory.
Then, install the SDK found here: SDK
Install this SDK and let it complete the install, which will include downloading for a bit. You need to do this since the SDK package above does NOT include the right drivers!!!
Once this has been completed, plug your phone into the computer via USB. Your computer will find a new device, however, it cannot locate the drivers for it. Browse and point the installer to:
DRIVE:\PATH_TO_android-sdk-windows\usb_driver
Don't go any further than this!!
Now, let it do it's thing and you should have a new device in the device manager called:
Android Phone
...|_Android Composite ADB Interface
Now, go to the command prompt and change to the following directory:
DRIVE:\PATH_TO_android-sdk-windows\tools
There, you will find adb.exe
Type:
adb devices
and you should see:
List of devices attached
HT019P801614 device
If not, something got screwed up and would need to dig further to help ya.
Ok ill give this a try once get home from school
nexus one root.
Ok assuming that you have the android sdk installed correctly, try rooting your phone via the superboot method. The first link below has a full detailed guide for rooting the nexus one and I believe has all of the device drivers for those who have not been able to get them running well. If you still have trouble getting the drivers working checkout the second link. Anyone who is relatively new to working with the sdk and is not familiar with working the commands check out the third link. Read the entire thread! it is very helpful.
1) http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
2) http://forum.xda-developers.com/showthread.php?t=613217
3) http://forum.xda-developers.com/showthread.php?t=619153
If you have any questions PM me on xda. I'll try and help in anyway, it took my like two days to actually root my nexus, I wasnt familiar with using ADB and Fastboot to root.
One thing I know I was having problems with since I came from the G1 was that the new SDK has to actually be installed via an .exe now. I was used to it all being in a zip so I kept trying to load up what I thought were the right USB drivers, but they were actually the 1.6 drivers I already had. So make sure to run the .exe that comes with the SDK.
ok so while i was downloading the sdk a notification came up that said that it could not rename the directory. is this bad?
i am having an issue with installing the right driver as well. my computer keeps installing the nexus one as a "mass storage device". i have uninstalled and reinstalled a few times but no luck. i have the phone set to debug mode, using XP btw. any help would be appreciated.
Hi all,
I have been strugeling for days now amd figured I will reach out. I have an intercept and over my dead body I can not get my workstation to connect to the phone. Initially my OS was Win7/64, which I saw there was no drivers for this phone. I then loaded a XP VM and it also failed trying a multitude of drivers. I dont know where to go from here.
I also tried (just a little though) on Win7/32 - no go.
Please if you have succesfully loaded the drivers for the Intercept, can you point me to where you got the drivers as well as what OS it is loaded on?
Sincerely,
J
i'm on win 7 64, and i seached around a while ago and ended up with some drivers for another samsung phone that ended up working on my system, and it only connected after i turned off usb debugging, i'll check out my computer and see what i did
It was a very furstrating experience for me. I ended up, finding a sollution over at:
http://forum.sdx-developers.com/index.php?topic=15586.msg194417#msg194417
It worked great. Thought if in future I want to drop a new ron on this baby, I am still stuck.
http://www.samsung.com/us/support/downloads/sprint/SPH-M910ZIASPR click on software do download the drivers.
Good luck with that one... those drivers got me nowhere
Did you try the Easy Tether drivers? http://easytether.blogspot.com/2010/10/easytether-drivers.html
Select Samsung
USB drivers
jluyt said:
Good luck with that one... those drivers got me nowhere
Click to expand...
Click to collapse
Not tooo sure what might have caused you an issue with the drivers from Samsung website. I have used them and never had any issues. I can tell you for fact, that Samsung, has changed their package of USB drivers for these Phones. I recently needed them for me new laptop, and i went there. When i seen the size of the package, i fired up my desktop, and compared the two. none the less i installed them ,and they worked better than the older package they had
Howdy,
My question is, does Odin not work with Windows 8.1 in general? If you have managed to get Odin to register that a device has been connected was there any special way you managed to get around this?
Some background:
I mentioned this issue in the noob friendly section but it seems I am the only one having the issue there. So I'm asking around here if anyone has had this issue under Windows 8.1. All I wish to do is flash the unbranded firmware to remove carrier bloat-ware.
I've downloaded Odin 9.07/9/10 and have the same result, that the device just does not appear.
System is running Win8.1 and has driver signature disabled.
Kies is installed and picks up the device without error
Phone has USB debugging on and appears under 'Device Manager' when in Download mode.
I've had a look around and found nothing with this issue, watched folks do it in various videos too but they were using Win7.
Thanks for reading!
Ste_JDM said:
Howdy,
My question is, does Odin not work with Windows 8.1 in general? If you have managed to get Odin to register that a device has been connected was there any special way you managed to get around this?
Some background:
I mentioned this issue in the noob friendly section but it seems I am the only one having the issue there. So I'm asking around here if anyone has had this issue under Windows 8.1. All I wish to do is flash the unbranded firmware to remove carrier bloat-ware.
I've downloaded Odin 9.07/9/10 and have the same result, that the device just does not appear.
System is running Win8.1 and has driver signature disabled.
Kies is installed and picks up the device without error
Phone has USB debugging on and appears under 'Device Manager' when in Download mode.
I've had a look around and found nothing with this issue, watched folks do it in various videos too but they were using Win7.
Thanks for reading!
Click to expand...
Click to collapse
My guess is that you need to install Samsung's USB drivers for your device. Have a look at the instructions at this, and this page. I suspect that you haven't installed SAMSUNG's Android ADB Interface Driver (look at OP of the second thread), which is used by Odin if I'm not mistaken to talk to your phone and push the images you want via ADB.
Install the Samsung usb drivers!
Odin works fine on my windows 8.1 computer.
ernani said:
My guess is that you need to install Samsung's USB drivers for your device. Have a look at the instructions at this, and this page. I suspect that you haven't installed SAMSUNG's Android ADB Interface Driver (look at OP of the second thread), which is used by Odin if I'm not mistaken to talk to your phone and push the images you want via ADB.
Click to expand...
Click to collapse
That was it. Thanks so much! I removed Kies, rebooted, installed the driver from samsung and rebooted again, after that Odin worked like a charm.
I had a somewhat small problem with this tablet - the virtual keyboard was not as fast as i'd exected to be. So I wanted to reinstall the OS by reflashing the rom/tool provided at http://www.needrom.com/download/chuwi-vi8/ .
It went well, the OS installed but at the end, that tool updated the uefi firmware too. I expected that, i kinda knew what I was doing. At about 80% of uefi flashing, the device went blackscreen and today it's still like that, Maybe battery was too low or it was simply the wrong Bios-uefi This is the first device I permanently broke.... It cannot be connected to a PC simply because it's a PC by its own... Or is it? There is no info on flashing dead win8.1 tablets on google.... Please help me out!
Sam.1211 said:
I had a somewhat small problem with this tablet - the virtual keyboard was not as fast as i'd exected to be. So I wanted to reinstall the OS by reflashing the rom/tool provided at http://www.needrom.com/download/chuwi-vi8/ .
It went well, the OS installed but at the end, that tool updated the uefi firmware too. I expected that, i kinda knew what I was doing. At about 80% of uefi flashing, the device went blackscreen and today it's still like that, Maybe battery was too low or it was simply the wrong Bios-uefi This is the first device I permanently broke.... It cannot be connected to a PC simply because it's a PC by its own... Or is it? There is no info on flashing dead win8.1 tablets on google.... Please help me out!
Click to expand...
Click to collapse
Because there is not a specific forum for your device, this thread will be moved to Windows 8 General
reply
did you find solution ?? I have the same issue.
thanks to share if there is any way to repair it
Hello,
I accidentally hard-bricked my OP5 yesterday (interrupted an accidental reboot - yikes) and managed to unbrick it using the MSMDownloadtool from one of the threads here (thanks!). But I realized afterward that the MSM I used was an old one, and that I have Android 8.1.0 installed and no way to upgrade it (the phone doesn't find any update, and flashing the zip from the official website, I think there is a compatibility issue and it doesn't work...). As I'm really annoyed with android 8 and liked android 10 so much more, is there any way to upgrade it back to android 10?
My question might have already been answer, but I really don't understand most of the things that are said in here...
It might also be important to point out I have some issues with my drivers on my laptop. Windows wouldn't find the ADB driver from Android Studio (while virtually every tutorial said it should work...) and fastboot couldn't find my device.
I hope someone will read this haha ^^'
I'll be forever thankful if someone finds the solution...
edit: The solution was pretty easy actually. Use the "Oxygen updater" that will gradually update your OS until it's recent enough that the phone automatically finds the last update
davidGol1ath said:
Hello,
I accidentally hard-bricked my OP5 yesterday (interrupted an accidental reboot - yikes) and managed to unbrick it using the MSMDownloadtool from one of the threads here (thanks!). But I realized afterward that the MSM I used was an old one, and that I have Android 8.1.0 installed and no way to upgrade it (the phone doesn't find any update, and flashing the zip from the official website, I think there is a compatibility issue and it doesn't work...). As I'm really annoyed with android 8 and liked android 10 so much more, is there any way to upgrade it back to android 10?
My question might have already been answer, but I really don't understand most of the things that are said in here...
It might also be important to point out I have some issues with my drivers on my laptop. Windows wouldn't find the ADB driver from Android Studio (while virtually every tutorial said it should work...) and fastboot couldn't find my device.
I hope someone will read this haha ^^'
I'll be forever thankful if someone finds the solution...
edit: The solution was pretty easy actually. Use the "Oxygen updater" that will gradually update your OS until it's recent enough that the phone automatically finds the last update
Click to expand...
Click to collapse
Glad that you could fix this yourself.
Thanks for sharing!
davidGol1ath said:
Hello,
I accidentally hard-bricked my OP5 yesterday (interrupted an accidental reboot - yikes) and managed to unbrick it using the MSMDownloadtool from one of the threads here (thanks!). But I realized afterward that the MSM I used was an old one, and that I have Android 8.1.0 installed and no way to upgrade it (the phone doesn't find any update, and flashing the zip from the official website, I think there is a compatibility issue and it doesn't work...). As I'm really annoyed with android 8 and liked android 10 so much more, is there any way to upgrade it back to android 10?
My question might have already been answer, but I really don't understand most of the things that are said in here...
It might also be important to point out I have some issues with my drivers on my laptop. Windows wouldn't find the ADB driver from Android Studio (while virtually every tutorial said it should work...) and fastboot couldn't find my device.
I hope someone will read this haha ^^'
I'll be forever thankful if someone finds the solution...
edit: The solution was pretty easy actually. Use the "Oxygen updater" that will gradually update your OS until it's recent enough that the phone automatically finds the last update
Click to expand...
Click to collapse
Great to know you were able to unbrick your device.
I have a similar situation, have bricked my device and tried the MSM download tool to flash, but could not get my device to boot (I get the black screen - blue led on boot).
Could you please share the link to the MSMDownloadtool with the Android 8.1.0 image (let me try with this to see if this can work).