Related
So i downloaded WM6 Black 2.0, and its constantly crashing, so i wanted to re-install it and see if that helped.
now whenever i try to launch the file, i get an error message that states
"custom RUU has encountered a problem and needs to close. we are sorry for the inconvenience."
So im wondering what changed that wont allow me to run the ruu file? Im kinda freaking out here because i need to get my phone working! its constantly crashing on me!
i hope someone knows a fix for this, i tried to search but came up with nothing
newnoise1024 said:
So i downloaded WM6 Black 2.0, and its constantly crashing, so i wanted to re-install it and see if that helped.
now whenever i try to launch the file, i get an error message that states
"custom RUU has encountered a problem and needs to close. we are sorry for the inconvenience."
So im wondering what changed that wont allow me to run the ruu file? Im kinda freaking out here because i need to get my phone working! its constantly crashing on me!
i hope someone knows a fix for this, i tried to search but came up with nothing
Click to expand...
Click to collapse
Looks like a problem on your PC... (I mena for the Customruu crashing)
newnoise1024 said:
So i downloaded WM6 Black 2.0, and its constantly crashing, so i wanted to re-install it and see if that helped.
now whenever i try to launch the file, i get an error message that states
"custom RUU has encountered a problem and needs to close. we are sorry for the inconvenience."
So im wondering what changed that wont allow me to run the ruu file? Im kinda freaking out here because i need to get my phone working! its constantly crashing on me!
i hope someone knows a fix for this, i tried to search but came up with nothing
Click to expand...
Click to collapse
Had this happen to me. I downloaded .net framework 3.0 from the M$ site and then it worked fine.
Maybe that will help you.
Jim
Need more info?
newnoise1024 said:
So i downloaded WM6 Black 2.0, and its constantly crashing, so i wanted to re-install it and see if that helped.
now whenever i try to launch the file, i get an error message that states
"custom RUU has encountered a problem and needs to close. we are sorry for the inconvenience."
So im wondering what changed that wont allow me to run the ruu file? Im kinda freaking out here because i need to get my phone working! its constantly crashing on me!
i hope someone knows a fix for this, i tried to search but came up with nothing
Click to expand...
Click to collapse
Ok, first off, this is not a flame. It's an education, ok?
When posting a problem, it's best practice to let us know your:
Model of phone
Radio version
Boot Loader version
OS on your PC
ActiveSync version (s/b 4.5 by now)
Then, and only then, will you be able to get some intelligent answers. You also need to follow the link in my signature and there you will find answers.
If you're still stuck, usually re-downloading the RUU will result in a working ROM patch, unless you have other PC issues. You really need to fix that first, and the guides posted here are FULL of the diagnostic and troubleshooting steps that will propel you to a successful resolution.
Please read those posts, add your info, and you may be extremely pleased with the results.
Good reading!
newnoise1024 said:
So i downloaded WM6 Black 2.0, and its constantly crashing, so i wanted to re-install it and see if that helped.
now whenever i try to launch the file, i get an error message that states
"custom RUU has encountered a problem and needs to close. we are sorry for the inconvenience."
So im wondering what changed that wont allow me to run the ruu file? Im kinda freaking out here because i need to get my phone working! its constantly crashing on me!
i hope someone knows a fix for this, i tried to search but came up with nothing
Click to expand...
Click to collapse
First off; relax. At least the problem isn't with your phone. It's a heck of a lot easier to fix a PC.
I assume you've already tried to re-download the file?
Did you completely reboot your PC? Shut it down to power down, then restart. Make sure you don't have any extra USB stuff plugged in (like cameras, etc). If you have a PS/2 mouse and KB, use those, and not USB versions. One trick is to have the USB bus on your computer completely empty except for your phone.
Head over to Microsoft's site and download a fresh version of Compact Framework .NET (3.0 is the current version). Reboot after installing it -- even though it doesn't tell you to.
Run Windows Update. Make sure you're OK on those.
If that doesn't work, try downloading another ROM (OS only) -- like the Cingular Black 2.02 or the LVSM ROM, and see if that works.
You can also strip it apart -- use WinRAR to open the EXE file that you've been executing and extract the .nbh file from the EXE. Then go and download this guy: http://wiki.xda-developers.com/index.php?pagename=Hermes_CustomRUU and extract it into its own folder. Copy that .nbh file into that directory, and execute the executable -- it will flash your phone with a known good flasher.
But.... stepping all of the way back ... if the ROM doesn't work on your phone, it's very likely reflashing it won't help a single bit. Those ROM's are checksummed when they go on the phone -- if they're corrupted, they won't load right in the first place (and you'd end up with a boot-loader only phone). Soo... uh.. first, reboot/clean USB, then try a different ROM.
Last resort will be completely reinstalling Windows XP. I've had to do this several times because Windows will get in some weird state and it refuses to flash my phone. I finally gave up and started flashing on my Mac using a Windows virtual machine -- it's a lot easier to restore my Windows system to a working point when I do that.
Thanks to everyone who gave a response!
Here's all the information i was asked to post ( i will remember this for next time)
Cingular 8525 HERM100
Radio version: 1.40.30.00
Boot Loader version: (Not quite sure what this is?)
OS on your PC: Pro Black 2.0
ActiveSync version 4.5
I have redownloaded the ruu about 3 times and it has failed everytime.
Restarted the PC, disconnected everything from my laptop, realized that i havent installed Framework .NET 3.0, ( although i have it on my phone as i needed it to run hitchhiker)
So i'm going to download framework .NEt 3.0 and run it.
As for my phone, i uninstalled all the apps, hard resetted and everything is working fine right now, hasn't froze at all since yesteray, so im going to wait it out and see if something happens again.
Thanks again to everyone!! This forum is really really helpful.
-Matthew
How to determine the bootloader version
newnoise1024 said:
Boot Loader version: (Not quite sure what this is?)
-Matthew
Click to expand...
Click to collapse
You need to have a look at your user guide, as it states how to enter bootloader and check the version. Otherwise press and hold the left OK button and the power button at the same time, then hit the reset button with your stylus. You will enter a tri-color screen. This is bootloader mode. Jot down the numbers and compare against the below link.
Exiting is simple, press the reset button with your stylus.
Here's a valuable link for updating your bootloader.
Bootloader Version: SPL-1.40.01pro
IPL-1.01
i just tried to install Framework .NET 3.0 and got this error message
[04/20/07,08:50:20] Windows Communication Foundation: [2] Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603
[04/20/07,08:57:35] Windows Communication Foundation: [2] Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603
[04/20/07,08:57:54] WapUI: [2] DepCheck indicates Windows Communication Foundation is not installed.
[04/20/07,08:57:54] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0 was not attempted to be installed.
i uninstalled any previous version, is there something i'm missing?
.Net Framework co-existence
newnoise1024 said:
Bootloader Version: SPL-1.40.01pro
IPL-1.01
i just tried to install Framework .NET 3.0 and got this error message
[04/20/07,08:50:20] Windows Communication Foundation: [2] Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603
[04/20/07,08:57:35] Windows Communication Foundation: [2] Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603
[04/20/07,08:57:54] WapUI: [2] DepCheck indicates Windows Communication Foundation is not installed.
[04/20/07,08:57:54] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0 was not attempted to be installed.
i uninstalled any previous version, is there something i'm missing?
Click to expand...
Click to collapse
You're probably missing version 2.0 of the .NET framework. .NET Framework is to be left in place once installed. You should have left V 2.0 installed and added .NET 3.0. Go to www.microsoft.com/net and get version 2.0 redistributable re-installed on your machine. (If you can). If you cannot, search the KB and you may get by without rebuilding your OS.
"Head over to Microsoft's site and download a fresh version of Compact Framework .NET (3.0 is the current version). To be extra safe, go into Add/Remove Programs and uninstall any existing versions -- reboot -- then install the new CF Framework. Reboot after installing it -- even though it doesn't tell you to."
this is the advice i was given in this thread, so i uninstalled version 2.0 before installing version 3.0.
So am i screwed now? lol
Well, version 3.0 just installed successfully... does that mean i still need to install 2.0? or am i fine just running 3.0?
Sorry for all the questions, i just want this fixed :/
You should be good. Give it a go.
If not, just dl .Net CF2 and install that. I think you are fine now though.
Edit: never mind
version 2.0 installed fine
Thanks everyone
I just post this thread in order to help others which are having the same problem as I am and to avoid looking arround on all the posts for this answer.
I'm so happy that I've not yet test this procedure wanted to share with you ASAP.
Thanks pvdhelm
pvdhelm said:
Follow these instructions and your vista problem is over.
I used this guide and it works for my artemis p3300 phone!
Please try downloading the latest WMDC first before attempting anything in this section of the guides. you will find the latest version HERE .
To follow this guide please make sure you have a copy of WinRAR installed, I will refer to the Windows Mobile Device Centre as the WMDC for ease of reading. If you do not have the WMDC installed please go here to install it first.
One problem with windows VISTA is that it uses the new "Windows Mobile Device Centre" and not activesync which we are used to, thus our standard RUU programs will not upgrade our Hermes devices as in windows XP. This guide will show you how to configure VISTA to work just the same as XP with our RUU programs.
For this guide firstly you need to download the new drivers:
Drivers for Windows Vista x32
Drivers for Windows Vista x64
Please note the x64 drivers are unsigned so to use them successfully you must disable driver signing.
Extract the contents to a folder on your desktop, call this folder "AS_DRIVERS". It contains the drivers from activesync which we will use instead of the native VISTA WMDC drivers when the device is in bootloader.
Now you must enter the bootloader on your device, to do this press and hold both the side ok button and the power button then put your stylus into the hole on the bottom of the device, your device will reset and show the red blue green bootloader screen. LEAVE THE DEVICE IN BOOTLOADER MODE and connect it using the USB cable to your VISTA PC.
Now navigate into the WMDC (Start>All Programs>Windows Mobile Device Center) and click on the "connection settings" menu icon
In the connection settings menu untick "allow USB connections" then press OK.
Now exit the WMDC and return to the desktop, go into the start menu and type "Services", this will take you into the local services dialogue and show a list of all services either running or registered with your pc.
Scroll down the list and make sure these services are present:
Windows Mobile-based connectivity
Windows Mobile 2003-based connectivity
If these services are not started then double click each one and set them to Automatic start by clicking the "startup-type" drop-down menu and selecting automatic then click the start button in the same window, apply the setting by pressing OK. Now return back to the desktop again.
Go into the start menu and type "Device Manager" then run, this will take you into the device manager. Click the "+" symbol next to "Mobile Devices" and double click on "HTC USB Sync".
This will bring up the properties of the currently connected device (the hermes in bootloader).
Go to the "Driver" tab and click "Update Driver".
Click "Browse My Computer for Driver Software".
Select "Let me pick from a list...."
Click the "Have Disk" button.
Click "Browse" and navigate to the AS_DRIVERS folder we created earlier.
Vista x32 users select the file "wceusbsh.inf"
Vista x64 users select the file "wceusbshx64.inf"
Then click Open.
click next and the driver will be installed (wait a moment).
Press close and escape back to the desktop now.
Now we must stop the WMDC process, start the task manager by pressing Ctrl+Shift+Escape.
click the WMDC line and click "End Process". In the confirmation window, again press End Process.
Now re-enter the WMDC and re-enable USB connections (click connection settings and tick the box "enable USB connections").
Your RUU programs for HardSPL/Radios/WM6 ROMs should now run as desired once you are synced with WMDC. Since we have updated the driver which vista uses when the device is in bootloader mode.
NOTE:: This technique is still in testing so if you have any issues please post in the official thread. Until we find another way to get RUU working with vista you may need to revert back to XP for upgrading your Artemis.
Click to expand...
Click to collapse
Just test it without any problem. I confirm the feasability of this procedure.
It rocks!
Always restart after before trying. It has worked with me.
Ha, Well I have tested and all works well, after this I've flashed USPL and B&B 3.7 ROM with no difficulty.
Now if I could only figure out why Mobile device Center will not install properly on my Vista Ultimate that I just 'upgraded' to today. It connected once, ran the sync but did not back up the contacts on my phone to outlook, and now on subsequent tries, the program wont open because of 'unknown problems'.
Maybe it's a sign to roll back to XP.
uninstall wmdc and then re-install. I had this error at first but fixed now.
Shand359 said:
uninstall wmdc and then re-install. I had this error at first but fixed now.
Click to expand...
Click to collapse
I had a feeling, I did that procedure once already with redundant results....but then again, half of my peripherals such as DVD-ROM, or wireless card didn't work, but then miraculously started working just as I was about to teach my laptop how to fly.
I will keep trying, thank you.
itschase said:
I had a feeling, I did that procedure once already with redundant results....but then again, half of my peripherals such as DVD-ROM, or wireless card didn't work, but then miraculously started working just as I was about to teach my laptop how to fly.
I will keep trying, thank you.
Click to expand...
Click to collapse
I'm not sure if that is the problem, but did you tried after restart vista?
When I made the procedure it was not working and then tried to restart and it was perfect.
Bluetooth sync works fine, but USB won't load driver. WM5 OEM, so no bootloader on my 8525. Will this solve my USB problem?
Hmm .. tried to follow the process above and Vista told me I already had the most recent version of the driver .. strange huh ?
For French :
http://www.forummobiles.com/index.php?showtopic=136003&hl=nuls
scratch that .. i missed a bit
Shand359 said:
uninstall wmdc and then re-install. I had this error at first but fixed now.
Click to expand...
Click to collapse
Agreed. Some 'versions' of windows Vista have WMDC built in, it is no good, uninstall WMDC and download the version from MS web site. Once installed run Windows Update.
owencutajar said:
Hmm .. tried to follow the process above and Vista told me I already had the most recent version of the driver .. strange huh ?
Click to expand...
Click to collapse
I had this issue too, uninstall vista drivers first, then install those from XP.
I followed these directions to update my Himalaya/Alpine-like i-mate PDA2 with disappointing results -- at first. WMDC claimed there was an error and I could not get it to respond. I flounced away and pouted for a little bit, and when I came back decided the only thing I could think of to change now before re-installing WMDC altogether was to roll back the driver for the mobile devices (in device manager) and WA-LA! Pouting works! I am now able to sync and Klaus (the i-mate) plays nice with Bob (PC)... ah, household bliss!
Thanks!
i still cannot get my laptop to see the artemis when it is bootloader mode - i have the XP driver on!!!!
I would love to try it, but does anybody have a german manual, or a translation program that translates Windows English into Windows German?
So I tried following one of the guides posted here at XDA to retrieve my MSL#.
** EDIT **
XDA FORUMS WILL NOT allow me to post links, because I have a new account, and it hasnt been approved. So I am just going to post the links to the screenshots without the "http" in front. I also had to remove the "." from the first part of the web address. So "google.com" would be "google com". You will have to manually copy and paste the URL, and add the periods to first part of the address.
IF A MOD IS READING THIS CAN YOU PRETTY PLEASE APPROVE MY ACCOUNT? Thanks!
I followed this guide:
forum xda-developers com/showthread.php?t=697487#
I downloaded the pre-requisites, and started to follow the steps.
I am on Windows 7 32bit, and these instructions are for Windows 7 64bit.
Once I cam to the section where I chose my drivers I chose the ones for x86 since I am running 32bit.
It installed the drivers fine. However, it installed the device under the "PORTS" section of the "Device Manager".
The screenshots for the instructions show the device being installed under the "MODEMS" section.
So I thought I did something wrong, and before doing any further research, I decided to delete the device that was installed under the "PORTS" section. I figured by doing this I could start from scratch, and correct whatever it was that I did wrong. Dumb move!!!
I removed the drivers from "C:\windows\system32\drivers" and also from "C:\windows\system32\driversstore\filerepository"
I unplugged my phone, rebooted my machine, dialed "##3424#" to enter diagnostic mode, connected my phone to the computer, and it DID NOT recoginze any new hardware.
I also tried removing any references from regedit for "htcdiag", which is the driver that was installed.
This produced the same result.
I have attached screenshots of the devices currently in my device manager.
Device Manager Screenshot #1:
img46 imageshack us/img46/8923/screenshot1ka.jpg
Device Manager Screenshot #2:
img163 imageshack us/img163/1479/screenshot2m.jpg
Device Manager Screenshot #3:
img202 imageshack us/img202/9158/screenshot3hj.jpg
Please help me get this working!
Thank you!
Have you tried msl reader from the market ?
mendez_v said:
Have you tried msl reader from the market ?
Click to expand...
Click to collapse
No, but at this point I am less worried about the MSL, and more worried about getting the android phone to show up properly under the device manager. When I rooted the phone I installed a modified HTC USB Driver, and then my phone showed up under device manager. As you can see from the screenshots my phone does not show up in device manager AT ALL anymore.
I know this was a rookie move, but someone must have done this before, or at the VERY least must have some suggestions on how to get the drivers reinstalled on my machine for my phone.
Anyone.... Bueller? Bueller?
** ONE MORE BUMP **
Perhaps all the useful contributors were on an extended Labor Day vacation.
guht said:
No, but at this point I am less worried about the MSL, and more worried about getting the android phone to show up properly under the device manager. When I rooted the phone I installed a modified HTC USB Driver, and then my phone showed up under device manager. As you can see from the screenshots my phone does not show up in device manager AT ALL anymore.
Click to expand...
Click to collapse
Have you plugged the phone in and tried "scan for hardware changes"?
Still no luck.....The HTC website has a support section with drivers you can download.
OR-
Do you have the android sdk installed on your computer? There is a usb driver package you can use in the sdk.
If you still cannot get it to connect, then flash a rooted stock rom and see if your computer can connect then.
As far as your MSL, just call Sprint and ask them. The rep will ask why you need it. Just tell them your phone has been acting odd and that you are going to do a reset, which you have done before in the past ; ). They will then transfer you to a tech which will ask you again why you need it. Just respond the same about doing a reset, which you have done many times before.....you will then have your MSL - takes only a couple of minutes.
My phone bricked, so i'm following the tutorial on how to unbrick it, everything was working fine and extracted the file. After that, boarddiag crashed and only opens with the program going to the task bar and i'm unable to click on it and show as the front window... any one have a fix for this? i've ran the program as admin, installed microsoft c++ 2012, downloaded it several times, rebooted my pc several times, tried compability mode and still won't open, I've gone to task manager and cancelled the process tree.... I have the lg g3 d851 tmobile connected to the pc and it shows in device manager. I don't know what else to do to open BoardDiag. Can you guys help me? Have you seen this problem with any programs?
I get the same problem but is easy fix it when the app run only in task bar use right button on mouse and put move option whit arrows and when u see the correct position push enter u can see any app hidden on taskbat i hope i can help u.
nachumama said:
My phone bricked, so i'm following the tutorial on how to unbrick it, everything was working fine and extracted the file. After that, boarddiag crashed and only opens with the program going to the task bar and i'm unable to click on it and show as the front window... any one have a fix for this? i've ran the program as admin, installed microsoft c++ 2012, downloaded it several times, rebooted my pc several times, tried compability mode and still won't open, I've gone to task manager and cancelled the process tree.... I have the lg g3 d851 tmobile connected to the pc and it shows in device manager. I don't know what else to do to open BoardDiag. Can you guys help me? Have you seen this problem with any programs?
Click to expand...
Click to collapse
*On will crackers xda link(https://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091) he mentions: "With windows 64 bit you need restart pc then click f8 choose disbable driver singturne..." Did you try that?
*In the files you extracted from the tot look and see if there is a .txt file listed; if so remove it from the folder and try loading the extracted files into the tool's folder again; I believe that file is a directory for the partitions so you may have to put it back in that extraction folder after after you get the partition files loaded into the tool.
This work for me
Hold down SHIFT key and right click on a running program icon on the taskbar, a popup menu should appear, click on Move then use the Left/Right Arrow key to move it.
Do the same for the rest of the running programs.
Let’s see if you can at least get them to move over, then we’ll see if other apps follow suit...
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 ?.