Develop Bugs

[Q] Verizon HTC Incredible

Hi, I'm trying to remove all those annoying pre-loaded aps that VZW put on my phone. I attempted to run the unrevoked3 root + flash thingy and it got hung up part way through - phone still works, and the phone IS rooted. I installed a terminal emulator and saw that all the pre-loaded aps only have "R" access which is why I cannot remove them.
I've tried using "chmod -r 777 <program>" and I get a "failed" message. I've tried the simple "rm /system/app/amazon*" and it tells me it's a read-only file (still). Can anyone help me? I've got some experience with linux and command line, but am still not very good with it and this is my first time attempting to root/hack my phone.
I've got the HTC Incredible running the latest 2.3 gingerbread.

Try to get BUsy Box and see if you have super user access, cuz since you said it hung up half way, chances are your phone did not root completely

Im pretty sure it has been rooted. I downloaded an emulator and when I type "su" the command line goes $->#. Someone else had this similar problem but they wanted to install a different ROM and I just want to remove useless aps. That being said I wasn't able to make any use out of his solution.

I should also point out that a super user icon is now in my aps window. I open it and its just a black screen, possibly because I haven't given anything root access yet?

d-pabs said:
I should also point out that a super user icon is now in my aps window. I open it and its just a black screen, possibly because I haven't given anything root access yet?
Click to expand...
Click to collapse
try installing rom manager from the app store and see if it ask you for permission

Ok, I installed that, but it didn't ask me for permission...is there something I have to adjust in the April itself?

d-pabs said:
Ok, I installed that, but it didn't ask me for permission...is there something I have to adjust in the April itself?
Click to expand...
Click to collapse
if it didnt ask for permission, that means your phone is not rooted, as Clockwork recovery needs permission to use, reroot? or ask in the incredible forum?

Yeah, guess I'll try to reroot. Not sure why the unrevoked3 root didn't work. Will try and post any details about failed tasks during the root process.
Thanks

d-pabs said:
Hi, I'm trying to remove all those annoying pre-loaded aps that VZW put on my phone. I attempted to run the unrevoked3 root + flash thingy and it got hung up part way through - phone still works, and the phone IS rooted. I installed a terminal emulator and saw that all the pre-loaded aps only have "R" access which is why I cannot remove them.
I've tried using "chmod -r 777 <program>" and I get a "failed" message. I've tried the simple "rm /system/app/amazon*" and it tells me it's a read-only file (still). Can anyone help me? I've got some experience with linux and command line, but am still not very good with it and this is my first time attempting to root/hack my phone.
I've got the HTC Incredible running the latest 2.3 gingerbread.
Click to expand...
Click to collapse
Read: http://forum.xda-developers.com/wiki/index.php?title=HTC_Incredible/Guides&Tutorials#Removing_Bloat

binaryhat said:
Read: http://forum.xda-developers.com/wiki/index.php?title=HTC_Incredible/Guides&Tutorials#Removing_Bloat
Click to expand...
Click to collapse
I've seen this thread before and since forgot about it. Thanks for posting it. I assume in order to do what they say in the thread (meaning run the adb shell), you need to root your phone
?

Sorry for taking so long to report back...busy time of year!
As it turns out, my phone actually WAS rooted despite running into the previously posted comments. I was attempting to start over and in doing so, downloaded SDK, JDK and proceeded to mount my phone using adb. All I had to do was reboot my phone in recovery mode and then mount /system. Voila! I have since moved all the useless bloat to a disabled folder...
My next question is this: How do I enable tethering and mobile hotspot?
Thanks for your help.

Wireless tether for root users is a pretty baller app. I show it off once in a while at work when someone flashes their ipad around. The speed is solid.

Hypcrsy said:
Wireless tether for root users is a pretty baller app. I show it off once in a while at work when someone flashes their ipad around. The speed is solid.
Click to expand...
Click to collapse
Is that the name of the ap? Or how can I enable it? I've been told that the pre-loaded mobile hotspot still will not for rooted phones and you need to download a 3rd party ap?

Just searched the "wireless tether" in the market and found it...it says it requires "Netfilter-enabled kernel" What's that mean? I'm still running the stock ROM (2.3 gingerbread). I don't know that I want to run a new ROM....

I downloaded and installed both "wireless tether" and "barnacle" just to try out both. I can view my mobile hotspot on other devices, and I can even connect them to my phone. On the iPhone (4g), I can get what appears to be everything but youtube. On my laptop I can't get any internet signal...
In either tethering ap, I cannot view who/what is connected (i.e. my laptop or iPhone). Any ideas? Are there limitations to these aps?

d-pabs said:
I downloaded and installed both "wireless tether" and "barnacle" just to try out both. I can view my mobile hotspot on other devices, and I can even connect them to my phone. On the iPhone (4g), I can get what appears to be everything but youtube. On my laptop I can't get any internet signal...
In either tethering ap, I cannot view who/what is connected (i.e. my laptop or iPhone). Any ideas? Are there limitations to these aps?
Click to expand...
Click to collapse
I have Barnacle for my Wi-Fi tether and it tells me who is connected to my phone (there should be a "Clients" tab). Do you have any encryption enabled?

I password protected my wireless hotspot and then used both the iPhone and laptop to connect to it, once they connected I tried viewing who was connected to my hotspot in both barnacle and the wireless tether and neither of them would say another device is connected.

Updated version to enable Unknown Sources

This is the latest release of my fix (June 14, 2011). This version addresses the Market ID and Moto Blur issue.
This version does not require the use of scripts on the phone. It uses ADB and sqlite3 (both are included in the zip file).
I created a new thread here because the older version was so full of bugs and comments about said bugs I figured it was time to start fresh, seeing how I am using a different method (the method I should have used to begin with) for this hack. Also, this should have been in development to begin with.
I have not had a chance to test the latest version, aside from verifying the awk command works as exptected. The rest is a strong educated guess, mixed with a re-tooling of it to just use Android Debug Bridge to do what I was having scripts do in the past. Should be much more reliable.
IF YOU DECIDE TO USE THESE INSTRUCTIONS: PLEASE, read through this page entirely from top to bottom at least once prior to doing anything. This way, if you are unsure on anything, you can ask the questions you need answers to. I am not liable for anybody messing up their phone because they didn't think to read the F'n manual prior to following these steps.
If you don't read this through completely before starting, and you brick your system, Don't come crying to me. I warned you.
This version makes it close to impossible to brick the system, but I left that bit in to cover my arse.
If you do not have the phone rooted, download the second zip file, and install the drivers found below:
Motorola Driver(install before you run the batch file)
You will need to enable USB Debugging:
On your phone,go to Settings->Applications->Development->Check "USB Debugging"
Latest version installs busybox for you, but if it doesn't, the script will pause for you to check, and tell you how to quit out of my script before proceding. If you have issues with that, let me know. I haven't tested this version, but by all accounts, it should be more reliable than my previous iterations, with the plus side of not having to purchase an app.
I have not tested it, so you may still need to tell it to install, but it should install the apk.
1. Download the attachment located in this post.
Unzip to a folder on your desktop.
PLUG IN YOUR PHONE NOW!!!
Double click on the batch file ("enable_unknown_sources.bat"). You may have to run as administrator, but I don't think so. Built on Windows XP (I'm a linux guy who wrote this at work in a couple minutes)
When it prompts for you to OK the super user for "unknown", look at your phone. It should have a prompt. If not, it may be ok. We will see....
once your phone has rebooted, you phone will have "unknown sources" enabled already. Don't worry about rebooting. The batch file did that for you.
Quite a bit less work than before. Good news: it's done! never to worry about it again...unless you upgrade....
DISCLAIMER:
DO NOT FOLLOW ANY OF MY STEPS IF YOU ARE UNSURE OF WHAT YOU ARE DOING! I have done my best to ensure that the instructions are accurate, but I made mistakes in the first revision, so who's to say that I didn't miss something this go 'round as well? If you decide to follow this walk-through, your actions are an agreement to not hold me liable if your phone becomes a pretty brick. I am not responsible for what you do with this information. If you have no idea how to do any portion of these instructions, you can either walk away (best idea), or ask for help here.
I am also not the 2nd shooter on the grassy knoll, nor am I the cause of all your woes throughout life. I always wanted to say that in a disclaimer.
Thanks to Vahnyyz for reminding me that I forgot to have you enable USB Debugging.
IF YOU HAVE PROBLEMS:
Have you installed the Motorola Drivers?
Do you have Debugging enabled?
If the answer to the 2 questions above are "yes, damnit! Give me a good answer, and stop wasting my time with these stupid questions", then you will need to tell me at what point the scripts fail. I will look into the problem as fast as I can.

so I tried the program you put on and everything because I haven't been able to root my phone as of yet, but the file I downloaded that included rooting did not work, everytime I ran the application it stated that "Device Not Found" and my phone is connected through USB at the moment.

Forgot a part
Thanks for letting me know about your issue. You need to do the following:
Ensure you have installed the drivers on you computer
Ensure USB Debugging is turned on
To enable USB Debugging, (on your phone...duh) go to Settings->Applications->Development->Check "USB Debugging"

as soon as I run the. bat file, command screen tells me to make sure that busybox is installed, which it is, to unplug phone, go to, busybox and install. Wife's phone is already rooted, once I hit next, "unknown" will pop up on the screen for a second and then....nothing.

Need to fix that to state "....after you ensure busybox is installed, plug phone back in"
Just plug the phone back up prior to proceding
Sent from my GT-I9000 using XDA App

How is the no blur version coming along....anxiously waiting for that!

JBallin4life27 said:
How is the no blur version coming along....anxiously waiting for that!
Click to expand...
Click to collapse
I am running into a problem I believe is caused by an older version of clockworkmod. I am trying to see if I can get a newer version running.
The issue:
It appears that the update file I generate is incompatable with the updater built into the version of ClockWorkMod I am running. Anybody have a newer build of the CWM I can use for testing?

jonsjava said:
I am running into a problem I believe is caused by an older version of clockworkmod. I am trying to see if I can get a newer version running.
The issue:
It appears that the update file I generate is incompatable with the updater built into the version of ClockWorkMod I am running. Anybody have a newer build of the CWM I can use for testing?
Click to expand...
Click to collapse
I had CM6 running on my motorola backflip and still have all the files saved on my computer...would it be in there somewhere and would that be useful to you?

JBallin4life27 said:
I had CM6 running on my motorola backflip and still have all the files saved on my computer...would it be in there somewhere and would that be useful to you?
Click to expand...
Click to collapse
I'm needing the second stage recovery file to make ClockWorkMod something newer than 2.x.x Needing to have it somewhere in the neighborhood of 3.x

jonsjava said:
I'm needing the second stage recovery file to make ClockWorkMod something newer than 2.x.x Needing to have it somewhere in the neighborhood of 3.x
Click to expand...
Click to collapse
Yea lol...no idea what that all means...sorry i'm not any help

[REF]Motorola Moto 360 Stock OTA URLs

Introduction:
This is a list of all known OTA's for the Motorola Moto 360 watch
The Moto 360 has it's ROMs built directly by google, instead of Motorola.
Click to expand...
Click to collapse
File List:
Latest:
LWX48P → LWX48T
See Motorola Moto 360 # Official ROMs - XDA Wiki for a list of files
Click to expand...
Click to collapse
How to flash:
Requirements:
Stock recovery
Unmodified /system
Unlocked bootloader
Basic understanding of command line/shell
Unlock your bootloader
Download and set up adb and fastboot
Reboot into fastboot mode
Open up a command prompt/shell where you saved fastboot
enter into command prompt/shell: "fastboot oem unlock"
Enter recovery mode via onscreen buttons
Enable recovery ui
(How do you do this for this device?)
Set up adb
Select apply update from adb
enter into command prompt: "adb sideload <path to saved update.zip>
Click to expand...
Click to collapse
FAQ:
How to find the ota?
If you're rooted, wait for the device to prompt you to update, then check /cache for the file
If you're not rooted, wait until the same time and do an adb logcat and look for a line with .zip in it
Why isn't the latest ota listed?
We can only list what we have, if the ota from Build X to Build Y isn't listed, we dont have the file for it yet.
How do you setup adb/fastboot
Please read the stickies in the general subforum, this is not a formal guide
Do I need to unlock the bootloader to flash the update zip?
Yes, if you wish to do it manually.
If you allow android to prompt for the update, you do not need to unlock
Can I flash this if I have a custom rom?
No, you must be on a stock AND unmodified rom
Can I flash this if I'm rooted?
Only if you have not modified any files
Click to expand...
Click to collapse
Credits:
birdpcfireworks: KKW22 → KGW42N
dproldan: KGW42N → KGW42R
EthanFirst: KGW42R → KNX01S
xdatastic: LWX48P → LWX48T
Click to expand...
Click to collapse
Changelog:
Dec 16, 2014: Added LWX48P → LWX48T
Oct 25, 2014: Added KGW42N→ KNX01S
Oct 24, 2014: Added KGW42R → KNX01S
Sep 25, 2014: Added KGW42N → KGW42R
Sep 11, 2014: Changed Page Layout to match my other pages
Sep 9, 2014: KKW22 → KGW42N
Sep 6, 2014: Initial page
Click to expand...
Click to collapse
2char

The initial rom is KKW22, I need a dump of it to assist in finding future otas.
It might be possible (this is simply speculation) that there might be an ota soonish to make it land on the same build as the existing g watch/gear live

I'm not familiar with what the current build version is on the other watches, but the first OTA is downloaded immediately upon setting up the device and updates it to KGW42N.
Edit: Dumping /system now.

AJerman said:
I'm not familiar with what the current build version is on the other watches, but the first OTA is downloaded immediately upon setting up the device and updates it to KGW42N.
Edit: Dumping /system now.
Click to expand...
Click to collapse
KGW42N is currently the newest for the gear live, unsure if it is rolling out to the g watch yet (i have yet to recieve an ota notification).
I assume you have a dump of KGW42N? I assume you dont have the ota itself for it, could you make a bug report and send it to me?
(I assume it's still possible, on normal android it's a button in developer settings) It might still be possible to get the filename of the ota.
dumps of either would be useful, along with the bootloader version.

TheManii said:
KGW42N is currently the newest for the gear live, unsure if it is rolling out to the g watch yet (i have yet to recieve an ota notification).
I assume you have a dump of KGW42N? I assume you dont have the ota itself for it, could you make a bug report and send it to me?
(I assume it's still possible, on normal android it's a button in developer settings) It might still be possible to get the filename of the ota.
dumps of either would be useful, along with the bootloader version.
Click to expand...
Click to collapse
Yep, I'll get everything I can, just taking a little time with adb over BT.

So you're saying in the OP you can unlock the bootloader with 'fastboot oem unlock', correct?

mattlgroff said:
So you're saying in the OP you can unlock the bootloader with 'fastboot oem unlock', correct?
Click to expand...
Click to collapse
The text in it is generic, I dont own a wear device but the previous two can.
The main issue right now is figuring out how to connect via fastboot, if it's possible at all I would assume that it is unlockable like the others.
If something is definitely incorrect feel free to let me know how to change it.

TheManii said:
The text in it is generic, I dont own a wear device but the previous two can.
The main issue right now is figuring out how to connect via fastboot, if it's possible at all I would assume that it is unlockable like the others.
If something is definitely incorrect feel free to let me know how to change it.
Click to expand...
Click to collapse
Nothing correct or incorrect to my knowledge. I can't find a single thread or post confirming if its unlockable or not. Kind of hoping you had tried

mattlgroff said:
Nothing correct or incorrect to my knowledge. I can't find a single thread or post confirming if its unlockable or not. Kind of hoping you had tried
Click to expand...
Click to collapse
If you connect via ADB over BT and reboot it into bootloader, among other things there is text saying connect a USB cable. So :/

fodawim said:
If you connect via ADB over BT and reboot it into bootloader, among other things there is text saying connect a USB cable. So :/
Click to expand...
Click to collapse
Well this problems stumps me!

I'm curious if the board supports Wireless USB.

All,
Here's what we know about the stock firmware right now:
1. Moto 360s ship with KKW22 out of the box.
2. Once the watch charges to 80%, it will force OTA to KGW42N.
What we need is someone to get some info about KKW22 before that watch reaches a charge of 80%! When you get your Moto 360, please plug it into the charging cradle and plug it into USB on your computer.
Pair it to your phone with the Android Wear app.
Enable ADB debugging on the watch by going to Settings | About Device and tapping on the build number repeatedly until it says "You are a developer."
At that point, go under Settings | Developer Options and enable ADB debugging.
Install the Google USB drivers for the "unknown device" that appears in the Windows device manager and select it as "Android Composite ADB Device."
Go to a command prompt and do "adb devices". This should cause a prompt to appear on your PHONE asking you to authorize adb. Do so.
Once authorized, do "adb logcat >logcat.txt". Wait about 20 seconds, then press control-C to stop.
Open up the logcat.txt file that was created and search it for "android.clients" (without the quotes) and post the URL to the OTA update here.
Do "adb reboot bootloader" and please post the bootloader version as displayed on the screen.
Reboot the watch again and then run "adb pull /system/build.prop". Open the build.prop file in a text editor and post the values of ro.build.date.utc and ro.build.fingerprint.
At this point, we'll have all the information we need and you can feel free to update to KGW42N happily and enjoy your new toy!
Thanks for your help, guys.

Wait, does this mean that the watch is capable of doing data over Qi?
Also, I'd be glad to help if I ever get my watch.

Slack3r said:
Wait, does this mean that the watch is capable of doing data over Qi?
Also, I'd be glad to help if I ever get my watch.
Click to expand...
Click to collapse
Not sure on the Qi question.
Have you ordered a 360? When is it due to arrive?

oldblue910 said:
Not sure on the Qi question.
Have you ordered a 360? When is it due to arrive?
Click to expand...
Click to collapse
Ordered one from Google Play on Friday, it's at "Leaves warehouse by September 22" so no idea when it will actually show up.
As for the Qi question, as the 360 has an inductive charger there is no way to actually plug into the watch and make a connection directly. Someone in another thread mentioned that Qi supported data transfer in some form, and I was hoping that the cradle would act as a USB interface to the watch. Were you referring to running adb via the phone's connection instead?
I'm really hoping someone will do a teardown of this thing soon. I'm itching to see what's inside.

Slack3r said:
Ordered one from Google Play on Friday, it's at "Leaves warehouse by September 22" so no idea when it will actually show up.
As for the Qi question, as the 360 has an inductive charger there is no way to actually plug into the watch and make a connection directly. Someone in another thread mentioned that Qi supported data transfer in some form, and I was hoping that the cradle would act as a USB interface to the watch. Were you referring to running adb via the phone's connection instead?
I'm really hoping someone will do a teardown of this thing soon. I'm itching to see what's inside.
Click to expand...
Click to collapse
ADB is done over bluetooth. You enable adb debugging over bluetooth on the watch, then on the phone you use the Android Wear app and go to settings and check Debugging over Bluetooth which will connect them, then you plug your phone into your computer and set up an adb tunnel to the watch. It's a bit convoluted and extremely slow. See the other thread in Q&A for more info.

AJerman said:
ADB is done over bluetooth. You enable adb debugging over bluetooth on the watch, then on the phone you use the Android Wear app and go to settings and check Debugging over Bluetooth which will connect them, then you plug your phone into your computer and set up an adb tunnel to the watch. It's a bit convoluted and extremely slow. See the other thread in Q&A for more info.
Click to expand...
Click to collapse
Glad to see someone who lives one town away from me (I'm in Morrisville).
I've never tried debugging via bluetooth on my Gear Live. I've always just snapped the charging cradle on and plugged the watch in via USB.

oldblue910 said:
Glad to see someone who lives one town away from me (I'm in Morrisville).
I've never tried debugging via bluetooth on my Gear Live. I've always just snapped the charging cradle on and plugged the watch in via USB.
Click to expand...
Click to collapse
Ahh, nice! I'm actually closer to Morrisville and RTP than Cary, though I'm technically a Cary address. :laugh:
Yeah, why would you even want to try to use adb via bluetooth if you have an alternative. It took me about 3 hours to do a system dump of the 360! You can expect that if and when any ROMs get built for this device, they'll take HOURS to transfer to the watch.

FCC docs show WiFi, and I suspect WiFi is used for updates.

AJerman said:
Ahh, nice! I'm actually closer to Morrisville and RTP than Cary, though I'm technically a Cary address. :laugh:
Yeah, why would you even want to try to use adb via bluetooth if you have an alternative. It took me about 3 hours to do a system dump of the 360! You can expect that if and when any ROMs get built for this device, they'll take HOURS to transfer to the watch.
Click to expand...
Click to collapse
Apparently the Moto 360 can't do data at all via the dock. You're forced into bluetooth ADB debugging as the dock is literally nothing but a Qi stand. Score one for the G Watch and Gear Live, I guess.

Help rooting G3

Recently got a G3 with Verizon. Running Lollipop 5.0.1. I've done quite a bit of reading about rooting, and understand the concept. Decided to try rooting my phone. I followed the guide here:
http://forum.xda-developers.com/log...de-root-lg-firmwares-kitkat-lollipop-t3056951
I attempted to root my phone several times, on three different PC's each running Windows 7. The farthest I ever get is a 90% complete status where the GUI says "Rooting phone" and the phone says "downloading firmware." I've left it in this state for upwards of 10 minutes and I always end up having to pull the usb and remove the battery in my phone in order to restart it. Upon pulling the USB the GUI will immediately show it had completed the root but when I test for super user status (with Terminal Emulator "su" entry) it says "not found."
USB debugging is enabled. I have tried switching between MTP and PTP connections. I have tried several different USB ports on each machine I attempted this. I tried it by first manually installing the LG drivers on the computer as well as by letting Windows automatically install them. I have tried with the box that says to always allow connections from the computer checked as well as unchecked. I tried versions 1.3 and 1.2 of the script. With version 1.2 it seemed like it finished and it prompted me to push control+c followed by N and enter or something and then the command window closed, but the phone was not rooted.
What am I missing?
I'd really like to get this phone rooted as I am excited to create a recovery and experiment with custom ROM's.
Any ideas are appreciated. Thanks!

The link you provided is to the XDA Forums homepage. The correct link is...
[Guide]LG One Click Root - root LG firmwares (KitKat / Lollipop)
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
The method you'll want to use for LP is located here...
[GUIDE][ROOT] Newest Root Method for LG devices
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
If the 1st method (one-click script) doesn't work for, the 2nd method using the classic way will. Download and extract the "New_LG_Root_v0.1_by_dig.zip" file from the OP, then open an elevated command prompt from within the directory you extracted the files to.

Thanks
I thought I fixed that link. Oh well. Glad to see there's a new method. I will try this. Thanks!

This worked by the way. Thanks again!

TP-LINK Android Phone / ADB Device

Ok so i'm pulling whats left of my hair out as I cannot seem to be able to remove this pest of a driver , windows 8.1 Pro is insisting my Nexus 5X is a TP-Link Android Phone and keeps over writing my google adb drivers so my fastboot / adb no longer works , has / is anybody having this problem? wugfresh install wont overwrite the TP-Link either all universal adb installers wont work either

MKD73 said:
Ok so i'm pulling whats left of my hair out as I cannot seem to be able to remove this pest of a driver , windows 8.1 Pro is insisting my Nexus 5X is a TP-Link Android Phone and keeps over writing my google adb drivers so my fastboot / adb no longer works , has / is anybody having this problem? wugfresh install wont overwrite the TP-Link either all universal adb installers wont work either
Click to expand...
Click to collapse
Kind of surprised you're still running Windows 8.1. Windows 10 is free for you and better in just about every way, regardless of the UI changes. Just a recommendation, though I doubt it'd fix your issue.
There's an easy way to tackle this but it depends on how the driver is being installed. If you're connecting your phone to your computer and Windows is insisting on downloading and installing this "TP-Link" driver from Windows Update, there is a way to disable this in a few easy steps. If you're connecting your phone to your computer and Windows just assumes that it's a "TP-Link Android Phone" and applies the wrong pre-loaded driver (usually gives you a notification near the clock) then we're gonna have to get a bit crafty.
EDIT: Silly question. You don't have USB tethering or any wacky app that would be causing this issue, right?

Alcolawl said:
Kind of surprised you're still running Windows 8.1. Windows 10 is free for you and better in just about every way, regardless of the UI changes. Just a recommendation, though I doubt it'd fix your issue.
There's an easy way to tackle this but it depends on how the driver is being installed. If you're connecting your phone to your computer and Windows is insisting on downloading and installing this "TP-Link" driver from Windows Update, there is a way to disable this in a few easy steps. If you're connecting your phone to your computer and Windows just assumes that it's a "TP-Link Android Phone" and applies the wrong pre-loaded driver (usually gives you a notification near the clock) then we're gonna have to get a bit crafty.
EDIT: Silly question. You don't have USB tethering or any wacky app that would be causing this issue, right?
Click to expand...
Click to collapse
Yeah we will have to get a bit crafty, i hid the TP-Link update in windows update god knows how it got installed but its in and i removed it but its still insisting its a TP-Link Android Phone , man its bugging me out . No tether app or other apps no, thats why im lost as to why its started this BS , windows i know can be tricky WIN10 was not for me plus the free upgrade has past now (29July) anyway.

MKD73 said:
Yeah we will have to get a bit crafty, i hid the TP-Link update in windows update god knows how it got installed but its in and i removed it but its still insisting its a TP-Link Android Phone , man its bugging me out . No tether app or other apps no, thats why im lost as to why its started this BS , windows i know can be tricky WIN10 was not for me plus the free upgrade has past now (29July) anyway.
Click to expand...
Click to collapse
Would you mind doing something for me before performing the steps I'm going to list below? Go into Device Manager with the phone plugged in and installed as the stupid "TP-Link" BS and find it in the list of devices. Should probably be under Portable Devices or something. Right click it and click Properties, go to the Driver tab and click "Driver Details". All of the drivers should be located in the 'system32/DRIVERS' folder. Mind giving me the names of those drivers listed? Naming convention is typically driverName.sys.
Additionally, we're going to try a Group Policy change. Hit Windows Key + R and type 'gpedit.msc' and hit enter. A window labeled "Local Group Policy Editor" should come up. Then do the following:
Expand Computer Configuration (Left hand side, the navigation panel)
Expand Administrative Templates
Expand System
Expand Device Installation
Click Device Installation Restrictions
On the right hand side, now, there should be a list of restrictions. Somewhere in that list there should be an item "Prevent installation of devices not described by other policy settings". Double-click that and another window named the same thing should pop up. In the top left, set it to enabled and click Apply, then OK.
Unplug your phone and get rid of that ****ty driver if you haven't already and then restart and try connecting the phone again to see if the same incorrect driver install occurs.

@MKD73 You ever get this sorted out?

Sorry been away on holiday for the weekend , I'll be taking a look in the morning :victory:

Please give update
Have you resolved this issue? My laptop is acting the same. Device manager sees my phone as "TP-Link Android Phone" with sub category of "Android Bootloader Interface." I can't use ADB with it, not recognized.
I tried doing what Alcolawl said but nothing happens. When I right click the "TP Link--- it just says general properties, no 'drivers' etc. I saw the 'driver' option in the "Andoid bootloader Interface" . It says the driver is: winusb.sys, wdfCoInstaller01009.dll and WinUSBInstaller2.dll. When I tried to edit the group, it says "Windows can not find gpedit.msc
Hope you can help me. My phone is stuck in fastboost mode- LG D838

kalikotpepot said:
Have you resolved this issue? My laptop is acting the same. Device manager sees my phone as "TP-Link Android Phone" with sub category of "Android Bootloader Interface." I can't use ADB with it, not recognized.
I tried doing what Alcolawl said but nothing happens. When I right click the "TP Link--- it just says general properties, no 'drivers' etc. I saw the 'driver' option in the "Andoid bootloader Interface" . It says the driver is: winusb.sys, wdfCoInstaller01009.dll and WinUSBInstaller2.dll. When I tried to edit the group, it says "Windows can not find gpedit.msc
Hope you can help me. My phone is stuck in fastboost mode- LG D838
Click to expand...
Click to collapse
Hi Kalikotpepot,
Got the same issue here., Nexus 5x keeps on rebooting, no way to get to recovery and shows as TP Link on my computer. Did you manage to sort it out somehow?

loeage said:
Hi Kalikotpepot,
Got the same issue here., Nexus 5x keeps on rebooting, no way to get to recovery and shows as TP Link on my computer. Did you manage to sort it out somehow?
Click to expand...
Click to collapse
I did it. Execute :
Code:
rundll32.exe newdev.dll,DeviceInternetSettingUi 2
and prevent driver from being installed.

Help me please!
Did you guys manage to fix it? I tried everything you people said but it didn't work. I have a Blu Vivo Xi+ and my PC only recognizes it as TP-LINK Android Phone. I dumbly deleted it's OS and all it's data when trying to update it. I only have access to TWRP and fastboot, is there a way to fix it? I would love if someone could assist me ?.