Hello, I hope you can help me solve the following problem.
When I try to connect Folio 100 to my PC, this is not recognized as a device and I can not start the adb.
Adb All information displayed in universal bus driver and not as a device.
I suspect there is an error with the driver used by Windows 7, but not how to fix it.
If anyone has a solution, I would be grateful if you share with me.
Greetings to everyone who has read this message
underwear69 said:
Hello, I hope you can help me solve the following problem.
When I try to connect Folio 100 to my PC, this is not recognized as a device and I can not start the adb.
Adb All information displayed in universal bus driver and not as a device.
I suspect there is an error with the driver used by Windows 7, but not how to fix it.
If anyone has a solution, I would be grateful if you share with me.
Greetings to everyone who has read this message
Click to expand...
Click to collapse
http://forums.computers.toshiba-europe.com/forums/thread.jspa?messageID=224451
Error: you do not have permission to view the requested forum or category.
even after creating a profile and login to the site
Use my ADB guide.
i have tried that but it doesn't recognize the driver as new/better and does not install it.
anyone ?
i still can't use the usb driver also not with the adb guide mentioned above
try using the "pdanet" software, it works for me
found it on android for dummier (guess i am)
reboot folio
press power 3 times on boot
and volume up once
install driver on windows
worked !
Jon2555 said:
Use my ADB guide.
Click to expand...
Click to collapse
I can't go into specifics - but having dealt with over 30 seperate folio's for a certain company beginning with t and rhyming with froshiba, I can confirm sometimes a device may just not work and be recognised by a windows machine. Not worked out what causes it, but ADB just can't see the device. Put it on a different windows machine and it will work perfectly. I believe putting it in fastboot mode does get round that, but when working in the OS mode you are pretty stuffed unless you change computer.
Cable6P said:
found it on android for dummier (guess i am)
reboot folio
press power 3 times on boot
and volume up once
install driver on windows
worked !
Click to expand...
Click to collapse
It worked for me right until I restart my folio to get out of fast boot then the device is gone from android adb devices. Any idea why?
hmmm and again it is connected, driver is right loaded, but fastboot and adb don't see the folio....
Related
Warm regards to the community here. I'm using Samsung & LG android devices past 2 years, with lots of custom roms and kernels; but have no experience dealing with Sony device. I am currently helping one of my friend to install Cyanogenmod on her Xperia mini pro sk17i, and help is required. I assure you, I won't have flooded the forum with a new thread if i'd found the answer. So hoping for a gentle guidance..
Here is what i did :
I followed the instructions given at Sony's website from step 1 to 12 : http://unlockbootloader.sonymobile.com/instructions
- I checked that Bootloader unlock allowed is "Yes", and managed to get my unlock key from Sony.
- I downloaded and installed Android SDK manager, also downloaded Google USB driver package revision 4. Also, i managed to download the zip file from Sony and successfully copied & replaced the android_winusb.inf file in the instructed folder.
- Now, at the step 13 mentioned in the guideline, i'm really stuck. I turn of the phone, press & hold volume up while inserting the usb cable.... there appears small blue light at the top of the device. But, nothing else happens.
>> I mean, the instruction says that i should be asked to point the drivers by computers, but my computer asks for nothing. I'm running on windows7 x86, intel core i3.
Please guide me what is going wrong ?? .... however, i should mention that my computer does gives me a notification sound, kind of what usually happens when i attach anything in the usb port.... but, on the screen, it shows no any notification or no any pop up... just nothing at all. I tried the whole procedure on an another computer running windows7 x64, intel core i5, but still stuck at the same problem.
Your help will be very much appreciated. Thanks in advance.
Have you checked "unknown sources" and "usb debuging" on?You will found them both in settings>applications if i translate it right from my greek menu
T3sla said:
Have you checked "unknown sources" and "usb debuging" on?You will found them both in settings>applications if i translate it right from my greek menu
Click to expand...
Click to collapse
Yes, of course both things are checked. To test the things, i also checked upon SEflashtools, and the device shows up there. However, if i command adb devices, it didn't show up on my second corei5 computer, but id did show up on my previous corei3 computer.
I tried out almost all i can do from my previous experiences of dealing with galaxy and optimus devices.. yet, this one is beating me.
Use drivers and tools from this guide and post the results (also mount sdcard to MSC mode)
If link doesn't work download latest flashtool.On installation folder there is a folder named "drivers".Run the file inside.
you have to manually install the driver of your android phone, go to the device manager on your computer, it should appear as S1 boot Fast boot in other devices, update the usb driver with the dowloaded diver android_win_usb.
your device shluld appear as android ADB Interface then you can proceed to step 14 which sadly where I got stuck too. I can't get a a response back from the said step. inform me if you have luck on the next steps...
mooside said:
you have to manually install the driver of your android phone, go to the device manager on your computer, it should appear as S1 boot Fast boot in other devices, update the usb driver with the dowloaded diver android_win_usb.
your device shluld appear as android ADB Interface then you can proceed to step 14 which sadly where I got stuck too. I can't get a a response back from the said step. inform me if you have luck on the next steps...
Click to expand...
Click to collapse
Same here.
- tried to uninstall Devide from the DeviceManager
- reboot PC
- connect my mini (with Vol-Up, blue LED turns on)
- choosed the "Android Booloader Interface"-Driver
- But Device-Manager says it's "Android ADB Interface"
My Datas:
root
CWM (installed through Installer from Market)
StockRom
Windows 7 (32 bit)
greeting
rookie
mooside said:
you have to manually install the driver of your android phone, go to the device manager on your computer, it should appear as S1 boot Fast boot in other devices, update the usb driver with the dowloaded diver android_win_usb.
your device shluld appear as android ADB Interface then you can proceed to step 14 which sadly where I got stuck too. I can't get a a response back from the said step. inform me if you have luck on the next steps...
Click to expand...
Click to collapse
vsrookie said:
Same here.
- tried to uninstall Devide from the DeviceManager
- reboot PC
- connect my mini (with Vol-Up, blue LED turns on)
- choosed the "Android Booloader Interface"-Driver
- But Device-Manager says it's "Android ADB Interface"
My Datas:
root
CWM (installed through Installer from Market)
StockRom
Windows 7 (32 bit)
greeting
rookie
Click to expand...
Click to collapse
Maybe this video can help you.
Thanks friends. Finally got it working ! .... it appears it was surely driver problem. Tried all the given driver links and installed them, and at least one of them must have solved my problem.
Unlocked the bootloader, and flashed nightly 20. Returned the phone back to her.
Thanks again !
officialreloaded said:
Thanks friends. Finally got it working ! .... it appears it was surely driver problem. Tried all the given driver links and installed them, and at least one of them must have solved my problem.
Unlocked the bootloader, and flashed nightly 20. Returned the phone back to her.
Thanks again !
Click to expand...
Click to collapse
Glad i was able to help you
What worked for me:
I removed these lines from the INF:
%SingleAdbInterface% = USB_Install, USB\VID_0FCE&PID_0DDE
%CompositeAdbInterface% = USB_Install, USB\VID_0FCE&PID_0DDE&MI_01
That worked.
greetings
rookie
Hi,
i have problem with my Novo 7 Paladin. One week ago i installed Google Maps update. After that my tablet was very strange. Sometimes when it go to sleep it won't wake up. I had to press power on again. Later that week there was some graphical glitch on screen (blinking colors). And now i can't boot at all. So i tried the SD card method to recover system. The problem is that i can't boot. Combination of keys like VOL+ and POWER or VOL+ and RESET doesn't work. Then i tried the original USB Boot Tool from Ainol. This tool doesn't work either.
USB Boot Tool
1) install correct USB drivers (press VOL+ and plug USB)
select drivers from tool/drivers/4770
2) unplug USB and start USBBootTool.exe
3) press VOL- and plug USB
4) it says BOOT... please waite0% (attachment boottool.JPG)
5) after some time of waiting the error apears (attachment boottool2.JPG)
Can someone help me please?
Great, so I can throw it away!
ErrorTM said:
Great, so I can throw it away!
Click to expand...
Click to collapse
First try to recharge it overnight, then push power button and see what happens. Anything shown on the screen?
lenik said:
First try to recharge it overnight, then push power button and see what happens. Anything shown on the screen?
Click to expand...
Click to collapse
Tested, same result.
when you connect your tablet to the PC, do you see any devices appear/disappear?
if you use linux, try lsmod (LSMOD lowercase) to see if your tablet shows on the list.
lenik said:
when you connect your tablet to the PC, do you see any devices appear/disappear?
if you use linux, try lsmod (LSMOD lowercase) to see if your tablet shows on the list.
Click to expand...
Click to collapse
I'm using Windows XP. Yes it appears in devices and install drivers.
ErrorTM said:
I'm using Windows XP. Yes it appears in devices and install drivers.
Click to expand...
Click to collapse
If it appears in devices, it's not completely dead. I don't have enough windows experience, but other people had occasional success installing correct drivers and reflashing the device using Ingenic USB Boot Tool or something like that. If the reflash process does not start, most probably it's because you have installed incorrect drivers.
lenik said:
If it appears in devices, it's not completely dead. I don't have enough windows experience, but other people had occasional success installing correct drivers and reflashing the device using Ingenic USB Boot Tool or something like that. If the reflash process does not start, most probably it's because you have installed incorrect drivers.
Click to expand...
Click to collapse
I am willing to install Linux if you think it could help.
I found xburst-tools, which i think is for flash my tablet. I used Ubuntu live distribution. Problem is that i cant even install prerequisities like libconfuse0. I dont know how to install it. Sorry im newbie in linux.
PLEASE! I need to load a new ROM into my MT6575 phone using Smart Phone Flash tool.
I've installed the Mediatek drivers on 4 different computers in my house (Vista, Window 7, Windows 7 64bit, Windows 8) and I cant get ANY of them to work!!
When I look under Ports (COM and LPT) in Device Manager, I ALWAYS get: This device cannot start. (Code 10)
WHAT is going on!! I've wasted so much time with this problem.
johnnysnavely said:
PLEASE! I need to load a new ROM into my MT6575 phone using Smart Phone Flash tool.
I've installed the Mediatek drivers on 4 different computers in my house (Vista, Window 7, Windows 7 64bit, Windows 8) and I cant get ANY of them to work!!
When I look under Ports (COM and LPT) in Device Manager, I ALWAYS get: This device cannot start. (Code 10)
WHAT is going on!! I've wasted so much time with this problem.
Click to expand...
Click to collapse
your not the only one with this problem i have it too with same mt6575 someone help please
Need to uninstall device and reinstall drivers
If you google, "Code 10", you will find that on a Windows system it is an error code generated by the Device Manager "because it can not start a device". In a nut shell, the most likely cause for this is because the device was not properly installed with the right drivers.
If you are running Windows, you can try to use the attached file called USBReview to see what device that is as you know it is your phone. Basically, with this program you can remove all the old drivers and start all the driver installation again.
Try to find your phone either here on xda, on the web or contact your phone's manufacturer - you need drivers!!!
Good luck, Mr. Phelps.
johnnysnavely said:
PLEASE! I need to load a new ROM into my MT6575 phone using Smart Phone Flash tool.
I've installed the Mediatek drivers on 4 different computers in my house (Vista, Window 7, Windows 7 64bit, Windows 8) and I cant get ANY of them to work!!
When I look under Ports (COM and LPT) in Device Manager, I ALWAYS get: This device cannot start. (Code 10)
WHAT is going on!! I've wasted so much time with this problem.
Click to expand...
Click to collapse
ronbo76 said:
If you google, "Code 10", you will find that on a Windows system it is an error code generated by the Device Manager "because it can not start a device". In a nut shell, the most likely cause for this is because the device was not properly installed with the right drivers.
If you are running Windows, you can try to use the attached file called USBReview to see what device that is as you know it is your phone. Basically, with this program you can remove all the old drivers and start all the driver installation again.
Try to find your phone either here on xda, on the web or contact your phone's manufacturer - you need drivers!!!
Good luck, Mr. Phelps.
Click to expand...
Click to collapse
Your USB program does give a lot of information I have never seen before, but I still haven't been able to figure out how to get the driver to load.
thanks, John
I'm having the same problem installing the MT6575 USB VCOM drivers. Is there a workaround to get this installed? I"m using WIN 6 64bit
johnnysnavely said:
PLEASE! I need to load a new ROM into my MT6575 phone using Smart Phone Flash tool.
I've installed the Mediatek drivers on 4 different computers in my house (Vista, Window 7, Windows 7 64bit, Windows 8) and I cant get ANY of them to work!!
When I look under Ports (COM and LPT) in Device Manager, I ALWAYS get: This device cannot start. (Code 10)
WHAT is going on!! I've wasted so much time with this problem.
Click to expand...
Click to collapse
This is what worked for me after lot of experimenting and searching:
- get MTK6575 drivers (for instance from Bruno Martins where he writes about flashing mtk6575 - google: MT6575 flashing tutorial bruno
- Start c/windows/system32/hdwwiz.exe (as admin)
- Click next
- Manually select hardware
- List all devices
- Select the driver (for example usb2ser_Win764.inf)
- from the List select "MediaTek Preloader USB VCOM Port"
(or you can install other drivers from the list if Preloader is not enough..)
On another computer I solved it by installing whole Android SDK, checked my android system and installed updated for SDK (approx. 2 GB) and it installed correct drivers automatically.
Also you can experiment with using another usb port..
Please write here if it helped.
ivy13 said:
This is what worked for me after lot of experimenting and searching:
- get MTK6575 drivers (for instance from Bruno Martins where he writes about flashing mtk6575 - google: MT6575 flashing tutorial bruno
- Start c/windows/system32/hdwwiz.exe (as admin)
- Click next
- Manually select hardware
- List all devices
- Select the driver (for example usb2ser_Win764.inf)
- from the List select "MediaTek Preloader USB VCOM Port"
(or you can install other drivers from the list if Preloader is not enough..)
On another computer I solved it by installing whole Android SDK, checked my android system and installed updated for SDK (approx. 2 GB) and it installed correct drivers automatically.
Also you can experiment with using another usb port..
Please write here if it helped.
Click to expand...
Click to collapse
Tried your first method but still get Code 10 error. Could not understand your second method. Please help. Me device is Qmobile Noir A2
hye.. any progress? am having the same issue.. just for MTK6575 com port driver
Just made my Amoi N820 work
So happy
You get Code 10 becouse your windows couldn't recognize the driver but that's irrelevant becouse flashing will work
No solution?
Any solution on this problem?
I've this china mt6575 galaxy s3 clone and got rooted using CF Root.Got ADB composite driver successfully installed in my pc (using win7 32-bit).When I install preloader usb vcom driver, i'm also facing this 'code 10' issue.Until now I can't install CWM in my phone.(the Flash Tool cannot detect my device).i try to install/push CWM using Terminal Emulator but nothing seems to change .when reboot into recovery mode the same stock recovery appear.Any help please?
orion~X said:
Any solution on this problem?
I've this china mt6575 galaxy s3 clone and got rooted using CF Root.Got ADB composite driver successfully installed in my pc (using win7 32-bit).When I install preloader usb vcom driver, i'm also facing this 'code 10' issue.Until now I can't install CWM in my phone.(the Flash Tool cannot detect my device).i try to install/push CWM using Terminal Emulator but nothing seems to change .when reboot into recovery mode the same stock recovery appear.Any help please?
Click to expand...
Click to collapse
i have thet problem to.
is ther solution?
I HAVE SOLUTION FOR THIS PROBLEM!!
Just ignore the error Code 10! Start the SPFlashtool and load the scatterfile, click on download and connect your switch off Phone with the computer. It will work fine.
Having the Same Problem
I understand I can ignore it and it works on that part, however I'm trying to root my phone now and it's not recognising that I have attached a device to the computer. Please need help to solve the problem. Have the drivers but can't get it without code 10
Hi.
me test for me not work.
iphone 4s.
plz help me.
hihi2u2 said:
I understand I can ignore it and it works on that part, however I'm trying to root my phone now and it's not recognising that I have attached a device to the computer. Please need help to solve the problem. Have the drivers but can't get it without code 10
Click to expand...
Click to collapse
Did you ever get this problem solved as I have the same issue with an MTK 6592 chip based phone?
I have the same problem too.
Installation of Media Tek preloaded drivers gives me Code 10 error.
Has anyone found the solution?
my phone is totally dead without power now after I tried to flash with SP Flash tool using correct ROM. I noticed in device manager that there is a CODE 10 error in mediatek preloader usb driver.. is this the culprit? my phone can no longer be detected now in SPFlash or MTK Droid tools... so hopeless... this is a brandnew phone I bought to be given as gift to my cousin...
I did it! I did it! I did it!
The solution is... we need not MediaTek USB VCOM (Android) (USB\VID_0BB4&PID_0005&MI_02), but PreLoader USB VCOM Port (USB\Vid_0e8d&Pid_2000) !
I have MTK6582 (KingSing S2), the host - WinXPx64.
It looks like my phone (and, maybe, other MTK devices too) have several engineering modes.
I have spent several hours trying to get working VID_0BB4&PID_0005&MI_02, which is exposed, if device is turned on while holding VOL- pressed. In this mode some strange factory mode with nonfunctional menu items is displayed on the screen. But to activate mode with Vid_0e8d&Pid_2000 some trickery is necessary.
Sometimes this USB interface starts repeatedly to appear and disappear every half-second in infinitive loop. I had such situation once, when connected turned off phone to USB cable with battery removed.
I just literally catched MT65xx Preloader by double clicking on it in windows device manager and pressing "install drivers" in it's properties. I have used Driver_Auto_Installer_v1.1236.00\SmartPhoneDriver\x64\Infs\usbvcom.inf from http://spflashtool.com/download/Driver_Auto_Installer_v1.1236.00.zip. DriverVer = 12/24/2011, 2.0000.0.0
After clicking "Read Back" in Flash Tool this insane loop stopped and program started to function as intended.
This interface could also appear once and for very short moment, if turned off phone (with battery inserted) is just connected to host. Also it could be seen again, if power button is pressed. If "Download" or "Read Back" is not pressed in advance in Flash Tool, than boot will continue after smaller than a second pause (if device is functional).
I don't know if running Install.bat (from archive I have given above) is necessary. It didn't installed driver when Vid_0e8d&Pid_2000 wasn't active, but, I guess, running it during short blinks would give the same effect.
Also, I don't know, if advice given in comment#6 in this thread four years ago would work. Maybe, the fault was in older version of driver (DriverVer=05/30/2011,1.1123.0).
Another reason could be that necessary USB interface disappears before windows manages to install driver for it for the first time. Possibly, only if "catched" in device manager, user could manually assign driver to it.
I've been struggling with my UMI Rome for days. It has/had the black screen problem, sometimes won't enter recovery mode, sometimes wouldn't allow charge, sometimes works just fine (yesterday). Last night i mistakenly cut off power during a battery recharge. -- today it has all the above problems (bricked) so I am trying doing a flashing again using the tutorials and tools on the Tehnotone.com site. Sintetix's reply above helps me at least have a better clue on what is going on. Wish me luck! BTW, I am using a Dell Windows 10 pc. (Results to be reported here.)
Sintetix said:
The solution is... we need not MediaTek USB VCOM (Android) (USB\VID_0BB4&PID_0005&MI_02), but PreLoader USB VCOM Port (USB\Vid_0e8d&Pid_2000) !
I have MTK6582 (KingSing S2), the host - WinXPx64.
It looks like my phone (and, maybe, other MTK devices too) have several engineering modes.
I have spent several hours trying to get working VID_0BB4&PID_0005&MI_02, which is exposed, if device is turned on while holding VOL- pressed. In this mode some strange factory mode with nonfunctional menu items is displayed on the screen. But to activate mode with Vid_0e8d&Pid_2000 some trickery is necessary.
Sometimes this USB interface starts repeatedly to appear and disappear every half-second in infinitive loop. I had such situation once, when connected turned off phone to USB cable with battery removed.
I just literally catched MT65xx Preloader by double clicking on it in windows device manager and pressing "install drivers" in it's properties. I have used Driver_Auto_Installer_v1.1236.00\SmartPhoneDriver\x64\Infs\usbvcom.inf from http://spflashtool.com/download/Driver_Auto_Installer_v1.1236.00.zip. DriverVer = 12/24/2011, 2.0000.0.0
After clicking "Read Back" in Flash Tool this insane loop stopped and program started to function as intended.
This interface could also appear once and for very short moment, if turned off phone (with battery inserted) is just connected to host. Also it could be seen again, if power button is pressed. If "Download" or "Read Back" is not pressed in advance in Flash Tool, than boot will continue after smaller than a second pause (if device is functional).
I don't know if running Install.bat (from archive I have given above) is necessary. It didn't installed driver when Vid_0e8d&Pid_2000 wasn't active, but, I guess, running it during short blinks would give the same effect.
Also, I don't know, if advice given in comment#6 in this thread four years ago would work. Maybe, the fault was in older version of driver (DriverVer=05/30/2011,1.1123.0).
Another reason could be that necessary USB interface disappears before windows manages to install driver for it for the first time. Possibly, only if "catched" in device manager, user could manually assign driver to it.
Click to expand...
Click to collapse
I tried what you said. It wouldn't install properly. It kept saying error (code 10) and showed in device management with a caution sign every time I installed the driver. I disabled the forced driver signature thingamabop but it still does it. I guess I'm screwed. Has anyone else fixed this?
my mi a3 is not recognized when in fastboot mode by the computer
I had this problem just some couple of hours ago and what you have to do (or at least it solved this in my end) is go to Manage Devices, scroll to TP-Link Android Phone, expand it and right click Android Bootloader Interface and uninstall without deleting the driver, then refresh for hardware changes and it will install the driver again and fastboot will work this time.
Jhon_Locke said:
I had this problem just some couple of hours ago and what you have to do (or at least it solved this in my end) is go to Manage Devices, scroll to TP-Link Android Phone, expand it and right click Android Bootloader Interface and uninstall without deleting the driver, then refresh for hardware changes and it will install the driver again and fastboot will work this time.
Click to expand...
Click to collapse
I'm facing this same issue. Please can you tell me where I can see Manage Devices on my computer? I'm using Windows 10.
I had the same issue. I tried all the methods that i researched. Even tried virtual machines running Windows 7 and Linux but same thing happens. I thought it was a Windows 10 issue. Til 1 day i tried to use a different cable, and DAMN! that fixed it.
same here, recognized as adb device but not recognized by fastboot.
I'm using Linux and fastboot work well.
The problem is that with lsusb no device is displayed, so I think it's a bootloader issue, is the bootloader environment corrupted? is there other setting to enable other then enable usb debug and enable OEM unlock?
Go to device manager right klik on android device and update the driver automatic.thats all.
U had the same problem and i solved with this.
Probably you don't have installed correctly fastboot drivers
Barbiox Dogg said:
I'm facing this same issue. Please can you tell me where I can see Manage Devices on my computer? I'm using Windows 10
Click to expand...
Click to collapse
im late but if u still need to know then hold down windows and x, a list should come up and then click device manager from there
deniloo said:
my mi a3 is not recognized when in fastboot mode by the computer
Click to expand...
Click to collapse
Just Update the device driver probably be showing under others in Device manager.
Visit this site to get the driver for your device. https://www.getdroidtips.com/download-latest-xiaomi-usb-drivers/
Dears,
How has this issue just "disable driver signature enforcement"
Search youtube on this and follow instruction
Say thanks if it help please,
I'm aware there is another thread on this, but his solution was simply switching the cable. For me, adb is currently working on multiple other phones, but on the G8X, it simply doesn't list the device. Any idea?
I do NOT have the full Android SDK, only the "minimal ADB and Fastboot" package, which just comes with adb, fastboot, and a couple other things. I love it and hope I don't have to install the full SDK for fastboot to work. D:
USB debugging is enabled, the device is connected as "File Transfer," and everything else is as it should be.
1337haXXor said:
I'm aware there is another thread on this, but his solution was simply switching the cable. For me, adb is currently working on multiple other phones, but on the G8X, it simply doesn't list the device. Any idea?
I do NOT have the full Android SDK, only the "minimal ADB and Fastboot" package, which just comes with adb, fastboot, and a couple other things. I love it and hope I don't have to install the full SDK for fastboot to work. D:
USB debugging is enabled, the device is connected as "File Transfer," and everything else is as it should be.
Click to expand...
Click to collapse
Same issue. Trying to use the Button Mapper app, and windows Button Mapper Setup keeps saying "Make sure the device is connected and USB Debugging is enabled."
Help?
You must try multiple times until a notification shows up to trust your PC.
hasso96 said:
You must try multiple times until a notification shows up to trust your PC.
Click to expand...
Click to collapse
Actually it was more "complicated" than that, as it said it ran an older version of the server than the phone at first. I googled some more, and managed to solve it. It was the installation of the LG USB mobile driver. I tried with the windows stock one at first, then tried Google USB driver from the SDKmanager, and even an universal driver didn't work. And even then when it was installed, THEN it said "unauthorized" and I had to just accept the connection on my phone
It's sorted now!
THANK YOU SO MUCH! Man, I wasn't expecting a reply after all this time, figured my unit was somehow defective or something. This worked perfectly! To others suffering, here's the direct link to the LG drivers, current version as of now, 4.4.2: tool.lime.gdms. lge .com/dn/downloader.dev?fileKey=UW00120120425 (Remove the spaces before and after the "lge").
Now I can tweak my system settings, debloat, use Button Mapper. Thanks again!