Hello, I own a RCA Viking Pro 10 tablet with Android 6.0 installed (RCT6303W87M7). I am having a lot of trouble rooting it for two key reasons.
1. It seems to be incompatible with most "One-Click" root applications.
2. It requires a special type of A-A USB cord, so it can not be connected to any computers.
I have looked through many root methods, but none of them seem to work. Any suggestions would be appreciated.
I have the exact same tablet and came upon those same two problems. I have, however, purchased a USB A-to-A cable and tried connecting it to a PC. I noticed that if the tablet is on when you connect it, the PC wont recognize it, but, if the tablet is turned off, the PC sort of recognizes it and begins to download and install drivers. The problem is is that once the drivers and installed, I can't find the tablet in my device manager.
One-click APKs don't work. I've tried, King Root, Kingoroot, One-Click Root, Towel Root, iRoot and virtually any and every one-click root that I come upon in the wild. I've also tried the PC root method with the USB A-to-A cable. I've used iRoot, King Root and Kingoroot. These obviously don't work because of the PC connectivity issue mentioned above.
It's a real nice tablet to dabble with, just a damn shame that there is virtually no information on it out there. If you do a google search, you will more than likely end up at this thread: https://forum.xda-developers.com/an...e-rca-viking-pro-rct6303w87dk-t3325158/page52 . Unfortunately, this thread is dedicated to an older model of this tablet running Lollipop. The only thing to do would be to keep searching and re-searching until we find something on it. Hope this helps.
so i'm still trying to root the RCT6303W87M7. i'm not really trying to install custom roms on it, i just want root access. so to update, i finally got my pc to recognize the device; but i dont beleive that it's recognizing it properly. here's what i did, making sure that USB debugging & OEM unlocking are both enabled in the developer options, i did this:
1. hold the 'power'+'volumeUP' buttons until you get into recovery mode
2. once in recovery mode, go to and select 'Reboot to bootloader'
3. when the 'Fastboot mode' message appears at the bottom of the screen, plug in the USB-A male to male cable to the PC
4. if you have your device manager open, you will notice that it is recognized as 'Android Phone'/'Android Sooner Single ADB Interface"
i tried rooting with three different 'one-click root' pc applications: iRoot(v1.8.8), Kingoroot(v1.5.0), and King Root(v3.5)
these are the results i got:
-iRoot: it connects but the message reads 'Not support mode'
-Kingroot: it detects the device and trys to connect but gets stuck in a loop trying to connect
-Kingoroot: this detects the device as 'HTC Device'. i click the 'Root' button and it trys to root, but it only gets to 19% and then it fails
i'm theorizing that maybe if i get some different drivers for the pc or maybe making sure that the 'one-click root' applications are the latest versions might help. i dont know, we'll see.
again this is for the RCA RCT6303W87M7 running Android 6.0.
if anyone tries this and has more success, please let me know.
Related
How to advise new users to install USB drivers for SGH-I777 on their computer.
I'm thinking that installing Kies Mini is not easiest or best.
Looking for all the options, and opinions as to which is easiest and best.
Thanks.
In personal experience assisting people with their phones not installing properly, people plug their phone in before running any software to install the divers.
I've never had any trouble installing a phone when software is run *before* the phone is ever plugged in to the computer.
Sent from my páhhōniē
The only problem I had was when connecting my phone in download mode for the first time, when my computer failed to install the drivers and couldn't recognize the device (despite having recognized the phone in USB Mass Storage mode previously without my doing anything). My solution was to install Samsung Kies before trying again, which allowed my computer to find the right drivers and install them automatically upon reconnecting the phone. Very easy to do, just need to provide new users with a link to the download site (not enough posts so I can't link it, but it's the first hit upon Googling "Samsung Kies").
Search for:
SAMSUNG USB Drivers for Mobile Phones - Latest Version is v1.4.8.0
and:
Samsung PC Studio 7.2.24.9 (Not sure if this is the latest version)
Uninstall all previous versions of samsung software, drivers, kies, EVERYTHING.
Install both, reboot and plug your phone in and see if it works. ADB wouldn't work until I installed PC Studio. In shell see if "adb devices" shows anything.
Kies is crap and a waste of HDD space.
HERE IS THE LINK TO THE DOWNLOAD!
http://downloadcenter.samsung.com/content/SW/201109/20110928044301055/ATT_i777_GS2_USB_Drivers.zip
Finally it's possible to root Alcatel OT-908 with Windows7
After much research I discovered little information about rooting the phone,
seemed like It was like finding a needle in a haystack.
It had led me trying al kinds of Apps supposedly for rooting, I tried
and tried but none seemed to work.
- tried Z4root did not root
- tried lots of others like Universal AndRoot, but the result ... no root
- tried the latest Gingerbreak v.1.2 , This will work on OT-908 with old Firmware (FRG83G.v61S-0)
However it did not root my Alcatel OT-908 from the store because it had the latest Firmware (FRG83G.v63N-0)
To make it work you must use SuperOneClick, read below on how-to.
STEP 1 :
Turn on USB DEBUGGING op your phone :
(in the menu, then settings, then applications, then development, and then making sure USB debugging is on).
STEP 2 :
You must have ADB DRIVERS installed.
See download links below
STEP 3 :
You must have ALCATEL QUALCOMM USB DRIVERS installed.
See download links below
STEP 4 :
Download and extract the latest version of SuperOneClick.
The version that I used was SuperOneClick v2.2 ,
See download links below
FINAL STEP :
Once the ADB Drivers and QUALCOMM USB Drivers are installed, you can simply rightclick SuperOneClick.exe as administrator
(Important , run as Administrator!)
And when SuperOneClick opens , simply press the Root button, and the rooting process should start automatically
and just wait until everything finishes you will get a message if it's been successfull.
It will ask to install busybox. (This is optional)
Congratulations, you are now equipped with a rooted phone, and you should have superuser access on your android phone´s program list.
If it fails ......
ALTERNATIVE STEP :
Bring your phone into recovery mode ;
You will have to shut down the phone make sure it's off,
then turn it on holding the POWER + VOLUME DOWN buttons and holding them until the screen goes on
As soon as the screen goes on and you see lights, press the HOME button and you are in recovery mode,
quickly plug in the phone on your computers USB port.
This is where the drivers must be installed.
If you have not installed the ADB and ALCATEL drivers windows will at this time ask for drivers and you should just let windows try and find the driver online, let it search and in most cases that is all you need. If it still doesn't recognize all the drivers you should point to the ADB folder in SuperOneClick or in the extracted ADB Driver folder and the ALCATEL QUALCOMM USB DRIVERS folder.
Once the ADB Drivers and QUALCOMM USB Drivers are installed, you can simply rightclick SuperOneClick.exe as administrator
(Important , run as Administrator!)
It's important you do this right after you booted, or the superoneclick program might freeze i've tried it many times and I'm sure this is when it worked, so right after you turned it on through recovery.
(power on + volume down until screen goes on, release and press HOME)
Right after you have done this little procedure correctly you hook it up to USB on your PC and quickly open superoneclick (rightclick administrator open)
and quickly press the ROOT button. (Do this very fast as waiting too long will not work)
You will see it run multiple tasks and when completed it will tell you it's completed and your phone is rooted.
It might ask you if you want busybox to be installed, you can choose
yes or no, but i recommend to just have it installed it may make things easier for you in the future if you plan to do more then just rooting your phone.
That's it.
Once it's completed, you should have the superuser application in your menu.
You can test to see if you have rooted successfull with root checker from the Android Market (a Freeware APP which lets you test if you've got a successfully rooted android phone).
If you have succeeded I recommend rebooting.
You should be having the pleasure of having a rooted Alcatel OT-908
If there are any questions, problems please reply and i will be back from time to time to answer questions.
Good luck to you all !
D.
Can't seem to get your steps to work..
Update: It is all in the timing - for me (after making sure antivirus wasn't clearing out the exploits folder) I had to start superoneclick while it was booting, say during the "WIND" animation screen.
Thanks!!
--------------
Hi,
Trying to follow your steps to root my alcatel ot-908
The first method doesn't work for me - the superoneclick log stops at step #5.
Every other attempt I've made results in superoneclick simply freezing after clicking 'root'.
Can you clarify your 2nd method?
1) How long are you holding the power+volume combo?
2) When you say "screen comes on", what do you see on the screen? If I hold for 30 seconds, I continue to see a dead black screen, with lights ON. Home button has no apparent effect. I have to remove the battery to reset.)
3) Are you connecting the USB and starting superoneclick with the android screen blank? Once I got a screen that had a graphic with an android character and a box with a green arrow flowing into the box.
Any help is appreciated, thanks
Maybe I don't know much, but I can't find any executable file in the ADB drivers.
Thank you for sharing with us!
I have a alcatel 906, this method will work on it?
Hi, I'm on froyo 2.2.2 with kernel frg83g.w635-0 (I updated with the build q 1.9.4, downloaded from alcatel site) This firmware cannot be rooted?
I have the version 2.3.4, and tried all disponeble the net and could not and would need to downgrade to a previous order to rooting the terminal
vasoulitos said:
Maybe I don't know much, but I can't find any executable file in the ADB drivers.
Click to expand...
Click to collapse
Install this one:
download. clockworkmod. com/test/ UniversalAdbDriverSetup.msi (Remove the spaces)
It worked for me, i just rooted mine 5 minutes ago.
I originally posted a threat up on reddit, but I couldn't find a fix for it.
I got a Note 2 do Android development on. I for the life of me cannot get the damn phone to connect to any PC I connect it to via USB; the phone charges, just does not connect. The USB icon does not appear on the device when connected either. I tried 3 different Windows machines, with the same warning I get that the device isn't recognized, but reads it as an 'Unrecognized Device'. I have also tried OS X, does not read it as well.
Here is some of the things I've tried from reading around XDA and other forums that haven't worked for me.
Solutions i've tried with no fix:
Various USB 2.0 cables (I do not have the original cable)
USB 2.0/3.0 and other ports repeatedly.
Enabling USB Debugging
Installing Kies, and Samsung driver from their site
Resetting battery
Booting into recovery mode with device connected
Dial codes for some reason do not work on my phone. I tried entering them with the stock dialer to bring the USB settings, but they don't work. I got around it by installing an app to get the USB mode to MTP, still does not work.
Rooting right now is not option, since Odin requires to be mounted to a machine in order to root. So I'm pretty much stuck. Still can't get this phone to sync on anything.
Device info
Model: SCH-I605
Carrier: Verizon
Android version: 4.4.2 (Kit-Kat)
Stock ROM/Non-Rooted
Hi all, I will try to be as detailed as possible.
I have a MetroPCS LG MS323 which I bought as a second phone to use when I travel as my regular phone is CDMA and I wanted a GSM phone that I could use with a sim card. While on an overseas trip I paid a cellphone place to unlock the phone so I could use other carriers' sim card, it was working fine since then. However, as I don't use the phone on a regular basis it ended up sitting and the battery lost its charge. When I tried to charge it by usb, it started bootlooping (vibrate, LG logo, repeat). After that I pulled the battery and charged it using an external charger. The phone is not rooted. I tried the factory reset key combo, but it gets stuck on the screen which says factory reset processing........ endlessly. I tried to download kdz file and flash with LG flash tool but phone cannot get into download mode. When I press vol key and plug usb cable, it says LOADING.......... press volum up key until download mode starts But it gets stuck there and download mode never starts.
I downloaded adb and fastboot to a Windows 7 laptop, and LG drivers, but when I connect phone and open a terminal adb devices shows no phone connected.
I also downloaded Laf.img for this phone and Laf recovery tool for Windows but again I cannot seem to get computer to see the phone. If I try to use the tool it says "waiting for device"
One difficulty is to trying to plug phone to computer the right way.
Most of the threads say to have phone in battery charge mode with usb debugging enabled, but I can't select any settings if the phone is bricked.
If I just plug the phone to usb when it is turned off it shows a picture of battery but no sign of charging, and computer doesn't detect phone.
If I plug phone to usb first, then hold vol and power key the LG logo will go black and it vibrates, in that case sometimes the Windows laptop will see 2 folders, verinfo and image.
When I plug usb cable to Linux computer and phone is off, same thing just picture of battery but terminal only shows sda1 sda2 sda3 etc no sdb no sdc just like not detected.
If I hold vol down then plug usb it vibrates and stuck on LG logo.
I have also tried to plug usb, then press vol down and power until phone vibrates, then try to let go buttons before LG logo shows up. but it doesn't mount.
If I hold vol up and power, then plug usb. it vibrates and goes to LG logo.
Last night somehow I got it to mount on the linux computer but the file manager was going crazy opening multiple windows and a list of folders would show up for a second, disappear and reappear as if the system was trying to read the folders but having difficulty. Today I am not able to get it to mount.
I have downloaded a linux livecd with adb and fastboot, I haven't tried it yet because I am not sure the path to flash an img file from a different directory on the hard drive on the windows laptop.
I have downloaded aboot.img but don't know how I can flash it if I can't see the phone on any computers.
I have spent days searching for solutions but have not seen the exact same problem, other threads suggest things but often the symptoms are slightly different or with a different phone. So, first of all I need to know what kind of brick I have, because other solutions I have seen posted for completely black screen, or phone detected as qhsusb qualcomm etc. which seems like a different problem.
So the 2 main things are 1, to know which kind of brick because many of the solutions I see posted seem like a different problem.
second, what is the best way to plug to computer so I can see the phone?
I burned a live CD of FWUL and ran adb from linux, still says adb devices nothing shows up. usb cable is plugged in and phone is turned off. Am I doing this wrong? I held down power and vol down until phone vibrates and LG logo appears. adb devices - "list of devices attached" still has nothing showing.. I don't know why even in Linux I can't see any device attached. Also I tried with pressing vol up and power until phone vibrates.
ls /dev/sd* only shows sda sda1 sda2 etc
I have also looked at past threads about unlocking the L70 bootloader, but the bootloader.zip no longer links and the phone does not have busybox installed.
I tried to see it Windows Device Manager but it does not show up anywhere.
This probably won't help, but, when you're at this point, you'll try about anything.
Did you fully install the LG drivers on your PC? Obvious seeming question. I was doing an old Droid Bionic a couple months ago and didnt' switch the USB modes (charging, media, file transfer, whatever it had) to each mode before modding .
As a result, I bricked that Droid bad. It took me almost a week and a half to restore it. I'm not sure if LG drivers work the same way, though I've worked on plenty of them. I think I have an LG Leon still in the scrap heap as a result of trying to replace a cracked digitizer that was bonded to the LCD. If anyone needs parts for one, I've got em, cheap I think that's an MS345 if I recall.
equitube said:
This probably won't help, but, when you're at this point, you'll try about anything.
Did you fully install the LG drivers on your PC? Obvious seeming question. I was doing an old Droid Bionic a couple months ago and didnt' switch the USB modes (charging, media, file transfer, whatever it had) to each mode before modding .
As a result, I bricked that Droid bad. It took me almost a week and a half to restore it. I'm not sure if LG drivers work the same way, though I've worked on plenty of them. I think I have an LG Leon still in the scrap heap as a result of trying to replace a cracked digitizer that was bonded to the LCD. If anyone needs parts for one, I've got em, cheap I think that's an MS345 if I recall.
Click to expand...
Click to collapse
Thanks, yes I had installed latest LG drivers LGMobileDriver WHQL Ver 4.2.0 before trying to flash .kdz file.
A tiny bit of progress to report, after getting a perfect timing to release the power and vol down keys I was finally able to connect to Windows machine. while waiting for drivers to install it was detected as QHSUSB_BULK in device manager, after drivers loaded now it is listed as LGE AndroidNet USB Serial {port (COM4). However when I run adb I still cannot see an attached device. I will look at solutions for the specific type of brick problem which has now been identified.
fofopuka said:
Thanks, yes I had installed latest LG drivers LGMobileDriver WHQL Ver 4.2.0 before trying to flash .kdz file.
Click to expand...
Click to collapse
What I meant was after initially installing the drivers did you switch the USB mode on your LG to all possible settings? Some drivers (like Moto) install more functions only when first called. you'll know if you switch from say charging to MTP or RNDIS you'll see driver install reopen.
also when you first ran ADB and plugged in the phone you probably should have seen more drivers install.
Forgive me if I seem to insult your intelligence. I'm an IT pro w 30 yrs in tech and I didn't know about the multi driver USB functions.
Tom Sgt aka Rootjunky has a good video on this that i initially didn't watch figuring I'd been installing drivers forever. 5 more minutes of watching it would have saved near 40 hrs of work and research
and when r
equitube said:
What I meant was after initially installing the drivers did you switch the USB mode on your LG to all possible settings? Some drivers (like Moto) install more functions only when first called. you'll know if you switch from say charging to MTP or RNDIS you'll see driver install reopen.
also when you first ran ADB and plugged in the phone you probably should have seen more drivers install.
Forgive me if I seem to insult your intelligence. I'm an IT pro w 30 yrs in tech and I didn't know about the multi driver USB functions.
Tom Sgt aka Rootjunky has a good video on this that i initially didn't watch figuring I'd been installing drivers forever. 5 more minutes of watching it would have saved near 40 hrs of work and research
and when r
Click to expand...
Click to collapse
thanks, I found his video for the G2 and no, I have never seen that with the drivers before! good to know. You can't insult my intelligence because most of this is over my head and I'm just trying to follow stuff I found with Google on XDA......
I downloaded and installed the Qualcomm drivers to try and identify if I have the 9006 or 9008 variety brick. However now when I plug in the phone Windows waits to install drivers, then says successful, when I look in device manager now I can't find the phone. But I did notice on the taskbar now there appears an icon named "intel graphics media accelerator driver for mobile" perhaps that is the driver Windows assigned to it? Device manager does have Intel Graphics Media Accelerator under display adapters. The other weird thing is that now it shows the battery as charging, which it never did the other times I plugged it into usb.
fofopuka said:
thanks, I found his video for the G2 and no, I have never seen that with the drivers before! good to know. You can't insult my intelligence because most of this is over my head and I'm just trying to follow stuff I found with Google on XDA......
I downloaded and installed the Qualcomm drivers to try and identify if I have the 9006 or 9008 variety brick. However now when I plug in the phone Windows waits to install drivers, then says successful, when I look in device manager now I can't find the phone. But I did notice on the taskbar now there appears an icon named "intel graphics media accelerator driver for mobile" perhaps that is the driver Windows assigned to it? Device manager does have Intel Graphics Media Accelerator under display adapters. The other weird thing is that now it shows the battery as charging, which it never did the other times I plugged it into usb.
Click to expand...
Click to collapse
have you seen this thread.
https://forum.xda-developers.com/showthread.php?t=2773123
it has the firmware for your model links to drivers and the LG flash tool, (which is warned against newbies (what the hey, it can't get much worse, we were all newbies once, )
Can you boot into fastboot? if so, you could flash the firmware with that.
equitube said:
have you seen this thread.
https://forum.xda-developers.com/showthread.php?t=2773123
it has the firmware for your model links to drivers and the LG flash tool, (which is warned against newbies (what the hey, it can't get much worse, we were all newbies once, )
Can you boot into fastboot? if so, you could flash the firmware with that.
Click to expand...
Click to collapse
Hi, yes although those links no longer work I have found the drivers and flashtool elsewhere. If I try to run flashtool it cannot see the phone. I cannot get into fastboot, and download mode won't load. I cannot see the phone on any Linux machine. The most I can do it see the phone as E: Qualcomm MMC storage USB device in Device Manager, but no other details. Explorer can see 2 folders, image and verinfo. Is there anything I can do with these folders in Windows? adb and fastboot run from terminal still do not list any attached device. Windows did a search for drivers for QHSUSB_BULK, although in device manager it still says LGE AndroidNet USB Serial Port (COM5).
What I really want to do at this point is push aboot.img to the phone, but for some reason I can't access the phone with Linux or adb. maybe because it did not have usb debugging enabled before it bricked. So many of the threads I have seen require a working phone to implement the steps, is there any way to enable usb debugging when the phone doesn't work?
fofopuka said:
Hi, yes although those links no longer work I have found the drivers and flashtool elsewhere. If I try to run flashtool it cannot see the phone. I cannot get into fastboot, and download mode won't load. I cannot see the phone on any Linux machine. The most I can do it see the phone as E: Qualcomm MMC storage USB device in Device Manager, but no other details. Explorer can see 2 folders, image and verinfo. Is there anything I can do with these folders in Windows? adb and fastboot run from terminal still do not list any attached device. Windows did a search for drivers for QHSUSB_BULK, although in device manager it still says LGE AndroidNet USB Serial Port (COM5).
What I really want to do at this point is push aboot.img to the phone, but for some reason I can't access the phone with Linux or adb. maybe because it did not have usb debugging enabled before it bricked. So many of the threads I have seen require a working phone to implement the steps, is there any way to enable usb debugging when the phone doesn't work?
Click to expand...
Click to collapse
Of course, I had forgotten about that. In order to use fastboot, most flashing tools, you HAVE to have USB debugging on.
There are occasional ways around this, though they are few. I do seem to recall oding it on that LG Leon. OR it may have been a Moto e or G, let me look back at previous threads i've asked for help in.
(Hmm, perhaps taking notes, or just leaving a webcam running while I'm doing a new device might be valuable in the future, I think with remarkable hindsight.) :cyclops:
---------- Post added at 02:28 AM ---------- Previous post was at 02:26 AM ----------
And no, you can't do anything to Android files in Windows, except see them. they are generally a different file system
One of the difficulties is just plugging it to a PC. 9 out of 10 times it is not recognized and nothing happens. So far the only way that seems to occasionally work is to plug the usb cable to the Windows 7 laptop, hold vol down and power, release both as soon as it vibrates. Most of the time I can't get it timed exactly right, but if I'm lucky sometimes Windows will detect the usb connection by following these steps. If I try on a Linux machine nothing happens, phone stays invisible. The most I've gotten with Linux is to charge the battery, but will not mount.
It is just a stock phone, not rooted, no busybox, no developer options enabled.
So this is a budget phone , spent hours obsessing over rooting it, did the whole process several different times several different ways,
the funny thing is , i can't event brick this device . this runs OREO 8.1 which a chopped down version of the full OREO 8.0 , basically it's designed for budget "entry level phones" . So i'm wondering
why they would make it so unbrickable? is it possible that this device doesn't even have a bootloader? if not why is it so hard to get to it?
Can't access fastboot mode nor the bootloader
One year later and this is still an issue. Here is my situation:
I bought an OTG (on-the-go) cord that allows me to connect a USB stick to my phone in order to extend my storage capabilities, but my phone doesn't natively support OTG (it basically doesn't have the drivers for it). In order to add support for it I need to root my phone, which I am having serious trouble with.
After hours of researching, installing, uninstalling, and factory resetting I've narrowed everything down to not being able to access the bootloader to select the fastboot mode. Here are my phone details:
Device Name: LG K20 (boot screen says "LG k20 Plus" however)
Model: LM-X120WM
Android Version: 9
Build Number: PKQ1.180904.001
Software Version: X120WM11c
As far as configurations go, I have:
- Enabled Developer Support
- Enabled OEM Unlocking
- Enabled USB Debugging
- Made my computer a Trusted Device on the phone
- There are no special "adb" options or configurations within my phone (I saw one website mentioned something about "adb" some options, but I only saw this once, and my phone doesn't have it anyway).
So far I have tried:
1) Holding the Power + Volume Down button for 10 seconds, then releasing the Power button when I see the LG logo, then repress the Power button until I see the "Factory Reset" menu. All this does it give me options to Factory Reset unfortunately (which I've done).
2) Holding Power + Volume Down button for 10 seconds. This simply reboots the phone and does nothing else.
3) I've downloaded, installed (on both my phone and my computer when needed), and tried rooting using the following programs: Dr.Fone, KingoRoot, RootGenius, iRoot, SuperSU Pro, and Superuser. There were some others I tried as well, but I determined I couldn't get anywhere with them specifically because I could not access fastboot mode (one example is "Magisk Manager").
4) Using ADB tools within command prompt (the most commonly recommended method) I tried rebooting the device into fastboot mode using the command "adb fastboot bootloader". The phone simply reboots and that's it, it has not switched into fastboot mode. You can confirm if you are by using the command "fastboot devices", which my device never shows.
5) I have gone to the LG website in order to download the drivers for this phone, however, while I am able to locate my specific device on the LG website, it directs me to download the "LG Mobile Support Tool", rather than download the drivers specifically for this device. I downloaded and installed the LG Mobile Support Tool but when the tool loads it does not recognize my device and tells me I need to install the drivers, which it gives me an option to do. Naturally I start the process to install the drivers but when it gives me the list of phone models mine is not in there *and you cannot proceed without selecting a model*. So, I tried using the closest model to mine (the LMX510WM), but it still didn't work.
6) Because LG does not have a direct download of the drivers for this device specifically I have tried downloading a variety of different drivers for this device. None have resolved the issue, but at this time *I believe* I have the most recent version of the LG drivers available "LGMobileDriver_WHQL_Ver_4.5.0".
7) I've tried adding the USB drivers through any install tools that came with them, and I've tried installing them manually via "Device Manager -> Add Legacy Hardware" and choosing the driver files specifically. This has not resolved the issue.
8) Installed the "wpdmtp.inf" file found within "c:\windows\INF" as recommended for Windows 10 users on one forum or another. Did not resolve the issue.
9) Installed the full Android Studio suite hoping something I was missing would be available, I also tried using the "adb" tools they provided: no love.
10) I also tried powering off the phone, holding the Volume Down button while plugging in the USB cord. This is supposed to do *something*, the instructions says I should enter "download mode", but on my phone does nothing.
11) the XDA-Developers forum suggested installed LGBridge_Setup.exe if I was having problems with drivers, which I have. When I ran the program it wasn't able to connect to my phone.
At this time I've uninstalled almost all software and all extra drivers from my computer (I left only the "LGMobileDriver_WHQL_Ver_4.5.0" drivers), as well as having factory reset the phone.
Everything is ready for another attempt, I've just run out of ideas. Thoughts?
Hi, I have also been trying to root this phone for the last year, but failed.
Everything is exactly the same as your phone regarding Build#, model # etc except i have software version X120WM10c .
The phone always wants to update but then it fails every single time.
I am hoping to root the phone so i can debloat it, and remove the restrictions preventing me from using it the way I want.
Anyone have any advice/info please post here. I will do the same.
Anyone? No response in almost a year.
ckeays said:
Anyone? No response in almost a year.
Click to expand...
Click to collapse
first of all you guys, are talking about two diferent very disimilar phones.. mediatek v20,qualcomm on the k9.....
myself i have a x210wm k9 im trying to find compatable firmware for.
The phone is working fine without root. Seems very fast for $99 CAD phone!