[Q] ZTE Blade customization - Blade General

Hey guys, flex here. So the deal is that I bought my blade about 2 weeks ago. It's version 2.2 and I've been trying to customizate it for like one week now. At first I heard from someone that my device could have faster that it was when I bought it. So back then I didn't know anything about androids (neither I do now haha), so I just googled "how to make zte blade better" and found someone saying you can do it with Superuser. Downloaded Superuser from somewhere, installed the apk through my sd-card and thought for looong time how does it work and why hasn't my phone become any faster.. :-D
After that I tried still to find solution for this and began to understand what 'rooting' means. And this is where it got tricky. I have tried almost every way how to root, and the rooting programs say that my phone is already rooted, when it really _isn't_. Because all the programs said my phone iz rooted already, I have tried installing some custom ROMs, without any success. It always stays there when I install the clockwork recovery apk, open it and my phone says it's force shutdown, or it doesn't respond. Could it have something to do with the installed Superuser without rooted phone?
What should I do to fix this? Could you help me step-by-step how to root my phone and get some nice custom ROM. I'm not so good at these things as you may see.. :-D
PS. please don't say things like 'go check another threads' because I have checked EVERY of them, guys you are my last hope
Sincerely, flex

Hey flex this thread has got a step by step guide just like you need
wiki.cyanogenmod.com/wiki/ZTE_Blade_(Gen2):_Root_and_Recovery
Sent from my ZTE-BLADE using Tapatalk

Great, thanks! I will try that as soon I wake up tomorrow!

It went well until this part:
Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.
Right-click on ADB.
Click on "Update Driver Software".
Click on "Browse my computer for driver software".
Click on "Let me pick from a list of device drivers on my computer".
Click on "Have Disk".
Click on "Browse".
Navigate to "C:\android-sdk-windows\google-usb_driver" and select "android_winusb.inf".
I clicked "android_winusb.inf" but then it said that my computer doesn't support that filetype or something like that.. What to do now?

Guys what does this mean "Open terminal and run the following commands"?
What is terminal and do I have to download it ?

flexiboi said:
Guys what does this mean "Open terminal and run the following commands"?
What is terminal and do I have to download it ?
Click to expand...
Click to collapse
If youre using win 7/vista, just type in cmd in the start menu and press enter. Else just press win+r and then type cmd and press enter.
flexiboi said:
It went well until this part:
Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.
Right-click on ADB.
Click on "Update Driver Software".
Click on "Browse my computer for driver software".
Click on "Let me pick from a list of device drivers on my computer".
Click on "Have Disk".
Click on "Browse".
Navigate to "C:\android-sdk-windows\google-usb_driver" and select "android_winusb.inf".
I clicked "android_winusb.inf" but then it said that my computer doesn't support that filetype or something like that.. What to do now?
Click to expand...
Click to collapse
It should only say that if you try to open the file not going thru the steps above?

the win+r thingie went well until there came command "exit" it said it didn't find and on the cmd it just closed the cmd

Bro, if you're computer recognizes your Blade, then you probably don't have to do the steps above. That stuff you posted is a "how-to" of installing the Blade drivers on to your computer
---------- Post added at 12:17 PM ---------- Previous post was at 12:16 PM ----------
I mean, can you transfer files to/from your computer, and to/from your phone?

You said you've read all the threads out there, but have you tried this. I had a stock 2.2 blade and when I first flashed a custom rom I had to use temporary root with z4root to install apps I needed (don't ask which cause I don't remember anymore ). Anyhow, If you can't get permanent root for your blade working, You could try temporary rooting it and see how far it gets you

Related

Using the RUU Issues

Hero had a hardware fault w/ the SD slot(good thing too! I dropped it last week and had a bit of rub on the top left that was bothering the hell out of me)
Was going to go get it replaced tonight, but for some damn reason the RUU won't work.
I have the latest RUU(1.56?)
Tried with phone w/ and without USB debugging
Went into fastboot mode(which made W7 install drivers for Android 1.0?) yet the RUU still won't recognize the phone.
I'm not computer illiterate, I'm just having problems with this damn RUU.
Halp?
What's the error you're getting?
The RUU basically says like
"Finding your Android Device" for about 30 seconds then says it cannot find it.
error 170...
ahh we meet again
i've helped a few people through this but i don't want to spoil the fun..
read this
all the way through it has the steps needed to get you up and going.
what os are you running?
just read windows 7..
try right clicking and "run as administrator"
thedudejdog said:
error 170...
ahh we meet again
i've helped a few people through this but i don't want to spoil the fun..
read this
all the way through it has the steps needed to get you up and going.
what os are you running?
just read windows 7..
try right clicking and "run as administrator"
Click to expand...
Click to collapse
I've read this before, I got it from geekfor.me
My windows 7 has the real administrator account enabled, running as administrator won't do anything.
intx said:
I've read this before, I got it from geekfor.me
My windows 7 has the real administrator account enabled, running as administrator won't do anything.
Click to expand...
Click to collapse
ok.
basically my next question is do you want my help or not?
i know how to make it work for you, at least three other people have gotten it to run by following my directions.
thedudejdog said:
ok.
basically my next question is do you want my help or not?
i know how to make it work for you, at least three other people have gotten it to run by following my directions.
Click to expand...
Click to collapse
Why wouldn't I want help?
ok try this.
type "adb devices"
if that sees your phone type reboot into fastboot then type "fastboot devices"
if that sees your phone then run the ruu
adb devices sees it.
boot into fastboot, fastboot devices sees it.
run the RUU, error 170 still >_<
intx said:
adb devices sees it.
boot into fastboot, fastboot devices sees it.
run the RUU, error 170 still >_<
Click to expand...
Click to collapse
have you tried this?
realmrealm said:
For some of the people running into problems with Windows 7 you may want to try:
1. Right-click on the executable file "ARUWizard.exe" and then go to "properties"
2. I believe there is a tab called "Compatibility" or something, click on it.
3. there should be a place for you to click next to a "run this program in compatibility mode" put a check there
4. below that there should be a drop down box, try choosing "Windows XP SP3" (or something similar to that)
5. near the bottom should be a place to check "run as administrator" check that.
6. click "ok" and then try running the program again.
I'm in front of a windows xp computer right now, not windows 7, so excuse me if i don't remember the options correctly, but I should be pretty close.
I also don't even know if this will work, but it's definitely worth a shot.
-AndyS-
Click to expand...
Click to collapse
or this?
10 char...
flipzmode said:
Possible resolutions would be:
1) Putting it in to fast boot and trying it again. Check your error log if it fails and seeing if it identified your phone this time.
2) Open a command prompt and "cd" to the folder where your \sdk\tools\ folder and type in "adb devices" and hit enter and see if it sees your phone. If not then that's your problem. If it DOES see your phone then enter the following command
3) adb shell reboot oem-78 -- that will reboot your phone in to RUU-ready fastboot. If you had the RUU still open then close it. Then open it and try running again.
Click to expand...
Click to collapse
or this?
crunchybutternut said:
Just had a thought.. after updating my HTC Sync software the adb included with my RUU might be out of date. I copied adb.exe, AdbWinApi.dll and fastboot.exe from C:\AndroidSDK\Tools and overwrote the files in the RUU folder. Then I ran it without a hitch.. weird, eh?
Click to expand...
Click to collapse
Tried the first two things, neither helped
I figured out part of the problem though. I had to dig up some 64 bit drivers.
I got the RUU to recognize my phone and it sends it to the bootloader and gets stuck on Waiting for bootloader then errors 170 out.
I'll try copying the files over now.
Replacing those 3 files did the trick!
Thanks
intx said:
Replacing those 3 files did the trick!
Thanks
Click to expand...
Click to collapse
no problem, when i did it i tried all of those steps at once, so i wasn't sure which one fixed it for me. so now (in theory) it should work for you on that machine every time.
wont run and get "ARUGlobal.dll can not be found" even tho im looking right at it....

7" Kindle Fire HD root

Hello everyone! I'm writing because I need help rooting my KFHD 7".
I've read a lot of stuff and I'm kind of familiar with the topic now. This is my first android device though, so I'm still a noob with all of this.
I read a tutorial that said I needed some programs (QemuRoot, Root with restore by Bin4ry, Kindle Fire ADB Drivers).
The first step normally is to install the ADB drivers. Every time I try to install them a window opens and it starts the process, the bar loads completely and gives me an option to "Finish". Now, every time I click "Finish", another window opens and says "The drivers were not properly installed. Please install the drivers manually." I believe this is my main issue. Another thing is, I have no idea when to plug in/out my device... I don't know if I have to try to install the ADB thing when the Kindle's connected, etc. I tried to delete all the Kindle drivers on my pc to reinstall the ADB drivers, but I still get the same error...
Now, when I try to use the other programs, they say that my Kindle should open a dialog window asking if I want to restore my device, and that it will reboot in 10 secs. None of this happens. I just want to root my Kindle so I can use GooglePlay and download some good stuff. Also, I don't live in the US so I pretty much can't use my Kindle for anything. I even paid for Amazon Prime and I can't enjoy Amazon Instant Video (streaming series, etc) because of some geographical restrictions... IF any of you would know a workaround... Thanks
Kindle Fire 7" HD ADB Driver
Krawdd said:
Hello everyone! I'm writing because I need help rooting my KFHD 7".
I've read a lot of stuff and I'm kind of familiar with the topic now. This is my first android device though, so I'm still a noob with all of this.
I read a tutorial that said I needed some programs (QemuRoot, Root with restore by Bin4ry, Kindle Fire ADB Drivers).
The first step normally is to install the ADB drivers. Every time I try to install them a window opens and it starts the process, the bar loads completely and gives me an option to "Finish". Now, every time I click "Finish", another window opens and says "The drivers were not properly installed. Please install the drivers manually." I believe this is my main issue. Another thing is, I have no idea when to plug in/out my device... I don't know if I have to try to install the ADB thing when the Kindle's connected, etc. I tried to delete all the Kindle drivers on my pc to reinstall the ADB drivers, but I still get the same error...
Now, when I try to use the other programs, they say that my Kindle should open a dialog window asking if I want to restore my device, and that it will reboot in 10 secs. None of this happens. I just want to root my Kindle so I can use GooglePlay and download some good stuff. Also, I don't live in the US so I pretty much can't use my Kindle for anything. I even paid for Amazon Prime and I can't enjoy Amazon Instant Video (streaming series, etc) because of some geographical restrictions... IF any of you would know a workaround... Thanks
Click to expand...
Click to collapse
The first step is to get the ADB Driver installed.
The following ADB Driver was provided by Amazon and should install: Kindle Fire ADB drivers
If not, I have an alternative driver here: https://dl.dropbox.com/u/54456659/usb_driver.zip
The alternative driver originates from the Android SDK and is universal for just about any Android device.
Extract the alternative driver to your desktop and follow the install instructions at the bottom of this response.
The instructions are for Windows XP but can be used with Windows 7 and Vista.
Once we get ADB installed then let's plugin the Kindle to your computer to see if it initializes properly.
Reply once you have done this step OR respond with the error OR where you are stuck. We will get you on Google Play!
Amazon Notes regarding this ADB Driver can be found here: https://developer.amazon.com/sdk/fire/connect-adb.html
ALTERNATIVE DRIVER INSTALL (Vista/XP/Windows7):
Windows XP
To install the Android USB driver on Windows XP for the first time:
1. Connect your Android-powered device to your computer's USB port. Windows will detect the device and launch the Hardware Update Wizard.
2. Select Install from a list or specific location and click Next.
3. Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
4. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
5. Click Next to install the driver.
Or, to upgrade an existing Android USB driver on Windows XP with the new driver:
1. Connect your Android-powered device to your computer's USB port.
2. Right-click on My Computer from your desktop or Windows Explorer, and select Manage.
3. Select Device Manager in the left pane.
4. Locate and expand Android Phone in the right pane.
5. Right-click Android Composite ADB Interface and select Update Driver. This will launch the Hardware Update Wizard.
6. Select Install from a list or specific location and click Next.
7.Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
8. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
9.Click Next to upgrade the driver.
prokennexusa said:
The first step is to get the ADB Driver installed.
The following ADB Driver was provided by Amazon and should install: link that you provided
If not, I have an alternative driver here: link that you provided
The alternative driver originates from the Android SDK and is universal for just about any Android device.
Extract the alternative driver to your desktop and follow the install instructions at the bottom of this response.
The instructions are for Windows XP but can be used with Windows 7 and Vista.
Once we get ADB installed then let's plugin the Kindle to your computer to see if it initializes properly.
Reply once you have done this step OR respond with the error OR where you are stuck. We will get you on Google Play!
Amazon Notes regarding this ADB Driver can be found here: link that you provided
Click to expand...
Click to collapse
Thanks for replying! The first ADB Driver (provided by Amazon) is the one that has given me the same error every time... something about an error and me installing the drivers manually (I have no idea how to do). The second link (dropbox) is broken... So right off the bat I'm stuck. The thing is, when I go to device manager, my Kindle Fire says "Android Composite ADB Interface"... I thought I already had ADB, but it appears that no matter what I do I can't get it to work... I don't have SDK or anything like that, though I'm downloading it to see if anything works...
Android Composite ADB Interface
Krawdd said:
Thanks for replying! The first ADB Driver (provided by Amazon) is the one that has given me the same error every time... something about an error and me installing the drivers manually (I have no idea how to do). The second link (dropbox) is broken... So right off the bat I'm stuck. The thing is, when I go to device manager, my Kindle Fire says "Android Composite ADB Interface"... I thought I already had ADB, but it appears that no matter what I do I can't get it to work... I don't have SDK or anything like that, though I'm downloading it to see if anything works...
Click to expand...
Click to collapse
OK, stop there. Even though it gave you an install error, it looks like the driver is installed. So let's move forward assuming they are functioning enough to get the job done.
Leave the Kindle plugged into USB and move on to my step-by-step which can be found 3/4 the way down on this Thread: http://forum.xda-developers.com/showthread.php?t=2064633
Note: The Kindle is left plugged in to USB through the entire tutorial.
prokennexusa said:
OK, stop there. Even though it gave you an install error, it looks like the driver is installed. So let's move forward assuming they are functioning enough to get the job done.
Leave the Kindle plugged into USB and move on to my step-by-step which can be found 3/4 the way down on this Thread: http://forum.xda-developers.com/showthread.php?t=2064633
Note: The Kindle is left plugged in to USB through the entire tutorial.
Click to expand...
Click to collapse
Thanks again. So I have the tool run with restore by bin4ry v18. When I open the folder, there is a RunMe.bat. I right click on it and click on run as administrator. It starts up and I write 1 to use normal mode. When it says that my Kindle should ask me for "restore", my Kindle is sitting there, doing nothing. It doesn't ask me for a restore. Then it says that my device will reboot in 10 seconds... My Kindle, again, does nothing. So that doesn't work... Now, I did another thing. I shift-right-clicked on the inside of the folder and clicked open command window here, then on the cmd that opened up I wrote "runme.bat" So it started the thing again, asked me for the number, etc. I write 1, and then this comes up (and it's stuck there): "Cheking if i should run in Normal Mode or special Sony Mode Please connect your device with USB-Debugging enabled now Waiting for device to shop up, if nothing happens please check if Windoes ADB-drivers are installed correctly!" Now, I have ADB turned ON on my Kindle. I also have the "Install apps" ON on my Kindle... Any suggestions?
Krawdd said:
Thanks again. So I have the tool run with restore by bin4ry v18. When I open the folder, there is a RunMe.bat. I right click on it and click on run as administrator. It starts up and I write 1 to use normal mode. When it says that my Kindle should ask me for "restore", my Kindle is sitting there, doing nothing. It doesn't ask me for a restore. Then it says that my device will reboot in 10 seconds... My Kindle, again, does nothing. So that doesn't work... Now, I did another thing. I shift-right-clicked on the inside of the folder and clicked open command window here, then on the cmd that opened up I wrote "runme.bat" So it started the thing again, asked me for the number, etc. I write 1, and then this comes up (and it's stuck there): "Cheking if i should run in Normal Mode or special Sony Mode Please connect your device with USB-Debugging enabled now Waiting for device to shop up, if nothing happens please check if Windoes ADB-drivers are installed correctly!" Now, I have ADB turned ON on my Kindle. I also have the "Install apps" ON on my Kindle... Any suggestions?
Click to expand...
Click to collapse
I see the problem. The way you are executing the batch files will cause the utilities to fail. You can not run the batch files (RunMe.bat and RootQemu.bat) through the mouse, you must execute them through a CMD Prompt.
OK, let's start from the top.
Let's make sure all the utilities are on your desktop.
Next Double Mouse Click and Open the Root_with_Restore_by_Bin4ry_v17 folder.
Single Left Mouse Click on the Root_with_Restore_by_Bin4ry_v17 folder toolbar.
This highlights the Root_with_Restore_by_Bin4ry_v17 folder.
Note: Make sure none of the files within the Root_with_Restore_by_Bin4ry_v17 are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, type:
Code:
RunMe.bat
Go back to my tutorial and follow the steps (http://forum.xda-developers.com/showthread.php?t=2064633), when you are ready to run Qemu
Next Double Mouse Click and Open the Qemu folder.
Single Left Mouse Click on the Qemu folder toolbar.
This highlights the Qemu folder.
Note: Make sure none of the files within the Qemu are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, type:
Code:
RootQemu.bat
Go back to my tutorial and follow the steps (http://forum.xda-developers.com/showthread.php?t=2064633).
prokennexusa said:
I see the problem. The way you are executing the batch files will cause the utilities to fail. You can not run the batch files (RunMe.bat and RootQemu.bat) through the mouse, you must execute them through a CMD Prompt.
OK, let's start from the top.
Let's make sure all the utilities are on your desktop.
Next Double Mouse Click and Open the Root_with_Restore_by_Bin4ry_v17 folder.
Single Left Mouse Click on the Root_with_Restore_by_Bin4ry_v17 folder toolbar.
This highlights the Root_with_Restore_by_Bin4ry_v17 folder.
Note: Make sure none of the files within the Root_with_Restore_by_Bin4ry_v17 are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, type:
Code:
RunMe.bat
Go back to my tutorial and follow the steps (http://forum.xda-developers.com/showthread.php?t=2064633), when you are ready to run Qemu
Next Double Mouse Click and Open the Qemu folder.
Single Left Mouse Click on the Qemu folder toolbar.
This highlights the Qemu folder.
Note: Make sure none of the files within the Qemu are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, type:
Code:
RootQemu.bat
Go back to my tutorial and follow the steps (http://forum.xda-developers.com/showthread.php?t=2064633).
Click to expand...
Click to collapse
Thanks for the reply. As I said in the previous post, I had already done the "shift right click and open windows command here" thing. It doesn't work. This is where it gets to and stays there forever "Cheking if i should run in Normal Mode or special Sony Mode Please connect your device with USB-Debugging enabled now Waiting for device to shop up, if nothing happens please check if Windoes ADB-drivers are installed correctly!" Now, I have ADB turned ON on my Kindle. I also have the "Install apps" So I'm stuck right at the first step... Doesn't matter what way I run the batch files I can't get them to work.
ADB Communication Issues
Krawdd said:
Thanks for the reply. As I said in the previous post, I had already done the "shift right click and open windows command here" thing. It doesn't work. This is where it gets to and stays there forever "Cheking if i should run in Normal Mode or special Sony Mode Please connect your device with USB-Debugging enabled now Waiting for device to shop up, if nothing happens please check if Windoes ADB-drivers are installed correctly!" Now, I have ADB turned ON on my Kindle. I also have the "Install apps" So I'm stuck right at the first step... Doesn't matter what way I run the batch files I can't get them to work.
Click to expand...
Click to collapse
Let's check the ADB communication path on your workstation.
Open a command prompt at the root of the Qemu folder, type:
Code:
adb kill-server
adb start-server
adb devices
The next command will probably fail, but let's try it:
Code:
android update adb
Finally, try:
Code:
adb shell
Reply back with the results.
prokennexusa said:
Let's check the ADB communication path on your workstation.
Open a command prompt at the root of the Qemu folder, type:
Code:
adb kill-server
adb start-server
adb devices
The next command will probably fail, but let's try it:
Code:
android update adb
Finally, try:
Code:
adb shell
Reply back with the results.
Click to expand...
Click to collapse
Thanks a lot! Well this are the results:
I did adb kill-server and nothing happened.
I did adb start-server and it said "daemon not running. starting it now on port 5037. daemon started succesfully"
I did adb devices and it said "list of devices attached" and then a blank space after that..
I did android update adb and it said "android is not a recognized internal or external command"
I did adb shell and it said "device not found"
I did all of that in the QemuRoot folder.. Am I doing it right? I double click on the folder to open it and then I click on the white space below all the files (while holding shift) and open the command window.
ADB Server Out of Date
Krawdd said:
Thanks a lot! Well this are the results:
I did adb kill-server and nothing happened.
I did adb start-server and it said "daemon not running. starting it now on port 5037. daemon started succesfully"
I did adb devices and it said "list of devices attached" and then a blank space after that..
I did android update adb and it said "android is not a recognized internal or external command"
I did adb shell and it said "device not found"
I did all of that in the QemuRoot folder.. Am I doing it right? I double click on the folder to open it and then I click on the white space below all the files (while holding shift) and open the command window.
Click to expand...
Click to collapse
Yes, you did this perfectly.
Hmmmm, looks like the ADB Driver is NOT working, bummer.
We need to focus on getting the driver functional.
Step 1) Go into Windows Add/Remove Software, find the Android ADB Driver, Uninstall the driver. If you can not find the driver in Add/Remove, then use the Uninstall Utility found in the Qemu folder "Drivers".
Step 2) Remove the Kindle from USB. Reboot the PC.
Step 3) Plug the Kindle back into USB after startup.
Step 4) When the PC has completed the reboot cycle, let's try to install the driver manually using the driver inside the usb_driver folder. Follow my instructions performing a manual driver install.
prokennexusa said:
Yes, you did this perfectly.
Hmmmm, looks like the ADB Driver is NOT working, bummer.
We need to focus on getting the driver functional.
Step 1) Go into Windows Add/Remove Software, find the Android ADB Driver, Uninstall the driver. If you can not find the driver in Add/Remove, then use the Uninstall Utility found in the Qemu folder "Drivers".
Step 2) Remove the Kindle from USB. Reboot the PC.
Step 3) Plug the Kindle back into USB after startup.
Step 4) When the PC has completed the reboot cycle, let's try to install the driver manually using the driver inside the usb_driver folder. Follow my instructions performing a manual driver install.
Click to expand...
Click to collapse
I deleted everything, I rebooted my PC, plugged in my Kindle and it started to install the Kindle drivers... (the normal ones)... It got an error and the driver didn't install... I got to manage under "computer" and i see "other devices" and under that it says "kindle" with a yelow exclamation mark... I go to its properties and drivers, I click update driver and use the folder that you gave me (usb_driver) and it gives me an error, saying that it could not find drivers... now do I set it to install the driver in C:\Users\Name\Desktop\usb_driver? or after usb_driver should I add \amd65 or \i386?
Thanks for your help... I don't know why nothing is working out!!
By the way, i just tried to install the adb drivers again and I got the same error... saying I have to install them manually. I ran both the bin4ry v18 and the qemuroot and both got stuck at "*daemon started successfully*" and they just sit there doing nothing...
ADB Driver Install
Krawdd said:
I deleted everything, I rebooted my PC, plugged in my Kindle and it started to install the Kindle drivers... (the normal ones)... It got an error and the driver didn't install... I got to manage under "computer" and i see "other devices" and under that it says "kindle" with a yelow exclamation mark... I go to its properties and drivers, I click update driver and use the folder that you gave me (usb_driver) and it gives me an error, saying that it could not find drivers... now do I set it to install the driver in C:\Users\Name\Desktop\usb_driver? or after usb_driver should I add \amd65 or \i386?
Thanks for your help... I don't know why nothing is working out!!
Click to expand...
Click to collapse
Yes, you are correct on the path: C:\Users\Name\Desktop\usb_driver
Let's try to install the Kindle Fire ADB Driver provided by Amazon. This time Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose "Run as Administrator".
If that fails, try to Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose Properties.
Then select the "Compatibility" tab
Check "Run this program in compatibility mode for"
Choose Windows XP Service Pack 2
Finally Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose "Run as Administrator".
prokennexusa said:
Yes, you are correct on the path: C:\Users\Name\Desktop\usb_driver
Let's try to install the Kindle Fire ADB Driver provided by Amazon. This time Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose "Run as Administrator".
If that fails, try to Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose Properties.
Then select the "Compatibility" tab
Check "Run this program in compatibility mode for"
Choose Windows XP Service Pack 2
Finally Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose "Run as Administrator".
Click to expand...
Click to collapse
Didn't work... I'm using windows 7 though... When I plugged in my Kindle it said something like Android ADB Composite installed succesfully... It did it by its own... When I try to install the Amazon ADB I get the same error, that i have to install it manually... I tried running the bin4ry root again and it doesn't work...
ADB Communication Issues
Krawdd said:
Didn't work... I'm using windows 7 though... When I plugged in my Kindle it said something like Android ADB Composite installed succesfully... It did it by its own... When I try to install the Amazon ADB I get the same error, that i have to install it manually... I tried running the bin4ry root again and it doesn't work...
Click to expand...
Click to collapse
We are missing something, usually simple.
What is the date and time stamp on the adb.exe daemons in the Root_with_Restore_by_Bin4ry_v17 "Stuff" folder?
---------- Post added at 05:09 PM ---------- Previous post was at 04:20 PM ----------
For everyone having trouble with ADB, here is a video that you may find helpful:
ADB Driver Install Video
prokennexusa said:
we are missing something, usually simple.
What is the date and time stamp on the adb.exe daemons in the root_with_restore_by_bin4ry_v17 "stuff" folder?
---------- post added at 05:09 pm ---------- previous post was at 04:20 pm ----------
for everyone having trouble with adb, here is a video that you may find helpful:
adb driver install video
Click to expand...
Click to collapse
1/13/2012 4:20 pm
ADB Server Out of Date
Krawdd said:
1/13/2012 4:20 pm
Click to expand...
Click to collapse
I thought I was going crazy. I knew it had to be something simple. You must have downloaded these utilities (Qemu and Root_with_Restore_by_Bin4ry_v17) from the developers site and not our site. Our utilities include the latest ADB daemons
which are dated 11/05/2012 11:06AM.
This is your problem.
Please use our utilities:
Kindle_Fire_HD_ADB_Drivers
Root_with_Restore_by_Bin4ry_v17
Qemu
Then go back to our step-by-step instructions. The ADB driver is probably fine, so you can probably bypass that step.
prokennexusa said:
I thought I was going crazy. I knew it had to be something simple. You must have downloaded these utilities (Qemu and Root_with_Restore_by_Bin4ry_v17) from the developers site and not our site. Our utilities include the latest ADB daemons
which are dated 11/05/2012 11:06AM.
This is your problem.
Please use our utilities:
Kindle_Fire_HD_ADB_Drivers
Root_with_Restore_by_Bin4ry_v17
Qemu
Then go back to our step-by-step instructions. The ADB driver is probably fine, so you can probably bypass that step.
Click to expand...
Click to collapse
Genius!!! It went smoothly, I did all the steps on the bin4ry and then qemu, and it said you now have root! How do I now if I actually have root? I don't see any different app in my kindle, I think I should have something like superuser?
Initialize Superuser.apk
Krawdd said:
Genius!!! It went smoothly, I did all the steps on the bin4ry and then qemu, and it said you now have root! How do I now if I actually have root? I don't see any different app in my kindle, I think I should have something like superuser?
Click to expand...
Click to collapse
Yes, you should see Superuser.apk in the APPS Folder. Go ahead and launch Superuser.apk to initialize it.
prokennexusa said:
Yes, you should see Superuser.apk in the APPS Folder. Go ahead and launch Superuser.apk to initialize it.
Click to expand...
Click to collapse
I guess it was too good to be true... there's no superuser.apk in the apps folder.. what to do? I already tried rooting it again and it said that i was rooted again
EDIT: I just woke up and tried again. Instead of usin first the root with restore and second the qemu, I used root with restore twice. Now I have a different app called SuperSU... It isn't Superuser though... It has a picture of the android robot wiith a cape flying... I opened but I have no idea what to do with it!
It worked for the error that you are having.
Hello i just read your post.. before continue sorry about my English is not perfect but i will try to to explain hot to explain the "solution"..
ok the first thing you need to do,is uninstall all the ADB drivers from the device manager.
after that you have to restart your PC..
when your pc is already started install de ADB drivers and then connect your kindle..! and let windows install the drivers again.
It worked for my so i hope it work for you.. =)

✪✪✪ [ROOT] [Restore] [OneClick OR Manual] [PC] [MAC] Kwongger's FLO Noob Root Kit ✪✪✪

✪✪✪ [ROOT] [Restore] [OneClick OR Manual] [PC] [MAC] Kwongger's FLO Noob Root Kit ✪✪✪
EVERYBODY!
WE ARE BACK DUE TO POPULAR DEMAND!!!​
Kwongger's All-In-One FLO Noob Root/Restore Kit FOR PC and Mac
YES! We are ADB FREE!!!​
Why we are back:
I really feel accomplished when I acutally do the commands myself! Apparently so do others, we are back B****ES!
I felt that I didn't get the help I needed/wanted as a n00b on XDA, this is a new account FYI, so I like to make n00b kits with AWESOME instructions, ENJOY!!!
FYI: I want to provide the best possible support that I can (even though this is free)
DOWNLOAD v3 ​
Hey! The ONE-CLICK/Restore update is currently uploading!
Instructions in post #2, Change-log in post #3.
DISCLAIMER:
By downloading the files, you accept the fact that I am NOT in anyway responsible for what YOU do to YOUR device, unless it starts shooting lasers at iOS devices, then all the credit is mine . Really,in all seriousness, this procedure is a BEGINNER procedure, I am simply providing instructions and TOOLS! I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE!!!​
Manual ROOT Instructions!
(If you want One-Click, then Just double-click either the Flo ROOT by Kwongger.bat (to root) or the Flo RESTORE.bat for a out-of-box restoration!
I’ll make a video soonish.​
Driver Installation!
To Install The Drivers Fresh
Connect your Android-powered device to your computer's USB port.
Right-click on Computer from your desktop or Windows Explorer, and select Manage.
Select Devices in the left pane.
Locate and expand Other device in the right pane.
Right-click the device name (such as Nexus S) and select Update Driver Software. This will launch the Hardware Update Wizard.
Select Browse my computer for driver software and click Next.
Click Browse and locate the USB driver folder. (The Google USB Driver is located in<sdk>\extras\google\usb_driver\.)
Click Next to install the driver.
Follow the Instructions!
Upgrade Existing Drivers
Or, to upgrade an existing Android USB driver on Windows 7 with the new driver:
Connect your Android-powered device to your computer's USB port.
Right-click on Computer from your desktop or Windows Explorer, and select Manage.
Select Device Manager in the left pane of the Computer Management window.
Locate and expand Android Phone in the right pane.
Right-click Android Composite ADB Interface and select Update Driver. This will launch the Hardware Update Wizard.
Select Install from a list or specific location and click Next.
Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
Click Browse and locate the USB driver folder. (The Google USB Driver is located in<sdk>\extras\google\usb_driver\.)
Click Next to upgrade the driver
Follow the Instructions!
Click to expand...
Click to collapse
Unlocking The Boot Loader!
1. Enable USB Debugging on your Nexus 7 in Development Settings
2. Open yourself a Command Prompt (or Terminal for MAC) in the Kwongger Nexus 7 folder!
a. Hold down shift
b. Right Click in the folder
c. Click Open Command Window/Prompt here
3. Boot into the bootloader using:
Code:
adb reboot bootloader
!!!!!!!!!!!NOTICE!!!!!!!!!!!!!!!
The next step will FACTORY RESET your device!!!
4. Once it is in the bootloader, enter this:
Code:
fastboot oem unlock
5. It will now ask you if you do, in fact, want to unlock your bootloader. Use Volume up/down to select YES and hit power to Confirm.
6. Your Nexus 7 FHD now has an Unlocked Bootloader.
7. IMPORTANT:
Reboot the device!
Click to expand...
Click to collapse
Choose either TWRP or CWM!
Installing TWRP!!!
1. Get into Your bootloader Again. (Above)
2. Type the following to flash the Team Win Recovery Project version 2.6:
Code:
fastboot flash recovery nexus7twrp.img
note: if you change the name use that in the .img part
3. Done!!!
Installing Clockwork Mod Recovery!!!
1. Get into Your bootloader Again. (Above)
2. Type the following to flash the Team Win Recovery Project version 2.6:
Code:
fastboot flash recovery nexus7CWM.img
note: if you change the name use that in the .img part
3. Done!!!
Click to expand...
Click to collapse
Rooting on Android 4.3!!!
.01 Copy The SuperSU.zip to the internal storage of your device.
1. Boot in to your bootloader and use the volume keys to select Recovery and use the Power button to confirm.
1a. RECOMMENDED: Tap BACKUP and Swype to confirm to make a backup of your current, UNROOTED n7.
2. Tap INSTALL.
3. Navigate to where you put the SuperSU.zip
4. Tap the zip.
5. Swype to confirm the flash!
6. If all goes well (no reason that I know that it shouldn’t) YOUR NEXUS 7 IS ROOTED!!!!
Click to expand...
Click to collapse
CONGRATS!!!!!!!!!!!!!
v1
Nothing New! This is 1.0
Click to expand...
Click to collapse
v2
I updated the Fastboot and ADB because some people were having some issues, it seems to have fixed the issues.
Click to expand...
Click to collapse
v3
I added the ever popular Mac Support! AND Clockwork Mod Recover, I don't know it is touch or not XD, could someone check? Just type
Code:
fastboot boot recovery nexus7CWM.img
and let me know! Thanks in advance.
Click to expand...
Click to collapse
I'm on windows 8 and have all the drivers installed but when I try and use the command "adb reboot bootloader" I get "error: device offline"
---------- Post added at 08:30 AM ---------- Previous post was at 08:12 AM ----------
I got it to work using the normal android sdk download. I couldn't get it to work using just the files I downloaded from you.
Gabik123 said:
I'm on windows 8 and have all the drivers installed but when I try and use the command "adb reboot bootloader" I get "error: device offline"
---------- Post added at 08:30 AM ---------- Previous post was at 08:12 AM ----------
I got it to work using the normal android sdk download. I couldn't get it to work using just the files I downloaded from you.
Click to expand...
Click to collapse
That's weird. I will update it.
Sent from my HTCONE using XDA Premium HD app
Actually!
Are you on 32bit? I included 64bit.
I like that you moved it to General!!!
I always thought that the DEVELOPMENT threads should be only used for KERNELS/ROMS
THANK YOU
Hey man, thanks for the instructions but could you clarify that you have to restart/boot up completely after unlocking the bootloader? I was still in fastboot after unlocking it when I flashed TWRP, and now TWRP is asking for a password, failing on all operations and I'm stuck in a bootloop.
EvanVanVan said:
Hey man, thanks for the instructions but could you clarify that you have to restart/boot up completely after unlocking the bootloader? I was still in fastboot after unlocking it when I flashed TWRP, and now TWRP is asking for a password, failing on all operations and I'm stuck in a bootloop.
Click to expand...
Click to collapse
Dang Dude, I am sorry. I just went ahead and put that in. :/
I want to help you with this.
Can you get into the boot loader or anything? Maybe if you can get TWRP working, I can send you a Nandroid of a stock, one (Once I get mine )
Kwongger said:
Dang Dude, I am sorry. I just went ahead and put that in. :/
I want to help you with this.
Can you get into the boot loader or anything? Maybe if you can get TWRP working, I can send you a Nandroid of a stock, one (Once I get mine )
Click to expand...
Click to collapse
Just found the solution in another thread: Open TWRP, Format Data first, then Factory Reset, finally reboot. I knew it wasn't a long term problem but I'm glad I didn't have to wait for Google to release Factory Images lol.
Gabik123 said:
I'm on windows 8 and have all the drivers installed but when I try and use the command "adb reboot bootloader" I get "error: device offline"
---------- Post added at 08:30 AM ---------- Previous post was at 08:12 AM ----------
I got it to work using the normal android sdk download. I couldn't get it to work using just the files I downloaded from you.
Click to expand...
Click to collapse
I am having this issue in windows 8 also, "offline" but I am getting the same thing using android sdk. Can someone provide some assistance please. Not sure why having such an issue.
EvanVanVan said:
Just found the solution in another thread: Open TWRP, Format Data first, then Factory Reset, finally reboot. I knew it wasn't a long term problem but I'm glad I didn't have to wait for Google to release Factory Images lol.
Click to expand...
Click to collapse
AWESOME!!!!!!!!!!
I feel better now XD
jmill75 said:
I am having this issue in windows 8 also, "offline" but I am getting the same thing using android sdk. Can someone provide some assistance please. Not sure why having such an issue.
Click to expand...
Click to collapse
I don't know... I have Windows 7. I also have NO IDEA why this would happen... Try using a port on the back of the PC (desktop) . If that doesn't do it, try USB 3.0 (if you have it). Also, if you are using the Stock cord, try other cords. That is all I can think of... :/
Kwongger said:
I don't know... I have Windows 7. I also have NO IDEA why this would happen... Try using a port on the back of the PC (desktop) . If that doesn't do it, try USB 3.0 (if you have it). Also, if you are using the Stock cord, try other cords. That is all I can think of... :/
Click to expand...
Click to collapse
There is a way to disable driver verification after rebooting in windows 8. I had to do this with my SGSIII and Win 8 x64, just google around for it, bet that's the problem.
RubenRybnik said:
There is a way to disable driver verification after rebooting in windows 8. I had to do this with my SGSIII and Win 8 x64, just google around for it, bet that's the problem.
Click to expand...
Click to collapse
Thanks! I will find it and add it to the instructions with credit.
Sent from my HTCONE using XDA Premium HD app
I see the pack includes the tools for MAC. I am on 10.8.4. Has anyone tried this on a MAC yet? I will be doing so later.
androidfr33k said:
I see the pack includes the tools for MAC. I am on 10.8.4. Has anyone tried this on a MAC yet? I will be doing so later.
Click to expand...
Click to collapse
Wait how would you do this on mac? Does the same .zip file work or would I need a different one? If you get it working please post a tutorial!
Looks like SuperSU came with the TWRP image(no need to copy it over separately). I tried to reboot from TWRP after updating the recovery and it forced me to flash SuperSU to root.
Nxxx said:
Wait how would you do this on mac? Does the same .zip file work or would I need a different one? If you get it working please post a tutorial!
Click to expand...
Click to collapse
I included Mac ADB... But not fastboot, you would need Fastboot as well, i'll get a Mac pack up tonight.
disregard....
working great! thanks OP

[Q] Help with USB Drivers for Nook Simple Touch

The current project I am trying to work on is trying to get USB mode to work on a rooted NST with NookManager. I have found a guide somewhere else, but it requries pushing boot and uimage files from ADB. I have tried everything I could, even using Ubuntu in Vbox but I haven't been successsful yet. For whatever reason, the USB isn't being read in Vbox-Ubuntu correctly and can't be mounted.
I have done everything I could to install the USB drivers on Windows properly, but I haven't had any luck. I have scoured the forums, but I couldn't find anything. What I need help is how to uninstall what I have reinstall correctly. I have tried the uninstall fuction in device manager but if there is a better way of doing this I haven't found anything. Can anyone help? Point me in the right direction at least? I hope if i can at least get the drivers installed correctly and adb devices to read it properly, I can figure out how to do everything else. It's just that one hurdler I'm having issues with.
I am running win 8.1 pro but willing to use ubuntu if necessary.
I should also mention what I have done. I Have altered the android_winusb.inf and the adb_usb.ini files, which sort of worked, but I still have yellow exclamations ove the device names.
Well, what do the Yellow Warnings say?
The first step is to get the category in Device Manage "Android Devices" (or "Android Phones") with a device listed under it.
If you have yellow, what driver does it say it has loaded?
It should be using WinUSB.sys
What does it say when you try to reload drivers?
If it suggest "Composite USB Device" accept that.
If you are using the latest version of adb.exe (819,200 bytes) it will already have the vendor ID in it for Nook.
You will not have to modify adb_usb.ini (not that it will hurt anything).
The first step is to get the driver installed (obviously).
abd.exe should be able to connect.
If you have a problem you could try omaplink.exe as an independent check of ADB.
Renate NST said:
Well, what do the Yellow Warnings say?
The first step is to get the category in Device Manage...
Click to expand...
Click to collapse
Well to say the least, it's mess
Anyhow, the category is "Other Devices - Nook SimpleTouch"
Driver Provider: Unkown
When I try reinstalling it says:
Windows found driver software for you device but encounterd an error while attempting to install it.
Android Composite ADB Interface​The system cannot find the file specified​I have done the Advance Restart for Win 8 that disables the driver signatures and I still get this message.
The modified .inf file has to be where it was originally.
That is, in the same directory as:
Code:
android_winusb.inf
i386\WdfCoInstaller01009.dll
i386\winusbcoinstaller2.dll
i386\WUDFUpdate_01009.dll
Renate NST said:
The modified .inf file has to be where it was originally.
That is, in the same directory as:
Code:
android_winusb.inf
i386\WdfCoInstaller01009.dll
i386\winusbcoinstaller2.dll
i386\WUDFUpdate_01009.dll
Click to expand...
Click to collapse
It's in the adt-bundle folder under ~sdk/extras/google/usb_driver. Should it be in the i386 folder?
I just meant that you can't take android_winusb.inf from where it was, edit it, plunk it down somewhere else and try to run it from there.
I don't know about "adt-bundle".
Do those 4 files listed above appear together in the same relative positions?
When you try to update the driver keep saying NO until you get to the "Have disk" button.
Renate, your questions helped me figure it out.
Yes all the files are where they are suppose to be in the same relative position that you outlined.
So i did this to get the "Have Disk Button"
I first did a right click "Update Driver software
1. Browse for driver on computer.
2. Clicked "let me pick from a list of device drivers"
3. A windows that says "Select your device type from the list below:"
4. List gives options includes Show all devices, ADB Interface, Android Device
5. I chose Android Device: It gave me a selection of devices and Nook Android Interface was there. I selected that and installed.
6. I then went to the command tutorial and typed in adb devices and I got the serial numbers.
I wrote this out for future refence for myself, and in the hopes it will help someone else.
thank you so much Renate! You were a huge help! I can't wait to start using your USB Host!
Renate NST said:
I just meant that you can't take android_winusb.inf from where it was, edit it, plunk it down somewhere else and try to run it from there.
I don't know about "adt-bundle".
Do those 4 files listed above appear together in the same relative positions?
When you try to update the driver keep saying NO until you get to the "Have disk" button.
Click to expand...
Click to collapse
I'm glad that worked.
I actually meant saying even more Nos until an actual "Have Disk" button appears.
Window caches the driver inf files and you could have had a bad one.

[GUIDE] Fix MTP driver installation on Windows 10

Hi guys and girls...
I just recieved my new phone a few days ago. Plugged it into an old Windows 7 x64 laptop and Windows instantly updated the driver. On a 2016 Dell E7450 Windows 10 x64 laptop... It didn't. Tried the Google USB drver package, but it didn't work either. Windows reports about a problem with an INF file and doesn't finalize the driver install...
I just saw someone reported the same issue in Q/A. I thought it would be a good idea to write a step by step guide.
@ppd0526 proposed an easier solution to fix the issue:
Please if you use this solution, don't forget to say thanks to him in this post: THANKS
ppd0526 said:
I actually just helped a friend out with this. There is an easier fix then having to go through all that and add a known device.
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
Click to expand...
Click to collapse
Uninstalled the driver and reinstalled using this method works fine! :good:
If someone has difficulty with the above or it doesn't work (which it should) i leave the one below just in case...
Click to show the guide:
Right click on the Windows start menu icon and select Device manager:
From here plug your Pixel using your USB cord to your computer. Pull the notification bar on your Pixel and tap on:
USB charging this device
Tap for more options
From the menu, select:
Transfet files
From here, you should see an "Unknown device" or an "MTP device" with an exclamation mark.
Right click on the device and select "Update driver software":
Click: "Browse my computer for driver software:
Click: Let me pick from a list of device drivers on my computer:
Scroll down till you find "LeMobile Android Device" and select it:
Here, select the second option: "MTP USB device"
Success
Now recognized in device manager:
In "This PC":
Hopefully, it will help some people.
Awesome, thanks! After several months with my phone, this just happened to me yesterday and I couldn't figure it out. The Google USB driver reinstall didn't work for me either, but this did!
As a suggestion, it's quicker to get to Device Manager by right clicking on the gear icon (Start) and selecting Device Manager.
JimSmith94 said:
Awesome, thanks! After several months with my phone, this just happened to me yesterday and I couldn't figure it out. The Google USB driver reinstall didn't work for me either, but this did!
As a suggestion, it's quicker to get to Device Manager by right clicking on the gear icon (Start) and selecting Device Manager.
Click to expand...
Click to collapse
Hooray... Thanks for the suggestion. I'm such a n00b when it comes to shortcuts... Edited to save the extra clicks.
5.1 said:
Hi guys and girls...
I just recieved my new phone a few days ago. Plugged it into an old Windows 7 x64 laptop and Windows instantly updated the driver. On a 2016 Dell E7450 Windows 10 x64 laptop... It didn't. Tried the Google USB drver package, but it didn't work either...
I just saw someone reported the same issue in Q/A. I thought it would be a good idea to write a step by step guide.
Click to show the guide below:
Right click on the Windows start menu icon and select Device manager:
From here plug your Pixel using your USB cord to your computer. Pull the notification bar on your Pixel and tap on:
USB charging this device
Tap for more options
From the menu, select:
Transfet files
From here, you should see an "Unknown device" or an "MTP device" with an exclamation mark.
Right click on the device and select "Update driver software":
Click: "Browse my computer for driver software:
Click: Let me pick from a list of device drivers on my computer:
Scroll down till you find "LeMobile Android Device" and select it:
Here, select the second option: "MTP USB device"
Success
Now recognized in device manager:
In "This PC":
Hopefully, it will help some people.
Click to expand...
Click to collapse
Wow, thanks so much. Couldn't figure this out. How did you?
bobby janow said:
Wow, thanks so much. Couldn't figure this out. How did you?
Click to expand...
Click to collapse
Hey... I once had a similar issue with a printer in the past and found this solution on the internet. So when it reappeared with the Pixel, I thought i would try as well. In the end it worked. That's all. I'm glad you sorted it out.
I actually just helped a friend out with this. There is an easier fix then having to go through all that and add a known device.
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
ppd0526 said:
I actually just helped a friend out with this. There is an easier fix then having to go through all that and add a known device.
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
Click to expand...
Click to collapse
Nice... Maybe you can open another thread? Or want me to add it to the OP?
Cheers...
5.1 said:
Nice... Maybe you can open another thread? Or want me to add it to the OP?
Cheers...
Click to expand...
Click to collapse
Adding it to the OP as an alternate method is fine. Better to keep the information consolidated.
ppd0526 said:
Adding it to the OP as an alternate method is fine. Better to keep the information consolidated.
Click to expand...
Click to collapse
Yeah you're right.
By the way, i just tried to uninstall my computer's driver and installed it with your method! Everything's alright.
Thank you...
My PC doesn't have this file wpdmtp.inf
Uninstalled the device and driver. Reconnected and let Windows update driver. Now it works.
Thank you Soo much. It worked exactly like it says in the OP.
This guide doesn't work anymore. MTP Device and MTP USB Device are no longer the menu options. Uninstalling the device doesn't work. You just end up with the exact same MTP with the exclamation point as before.
ppd0526 said:
I actually just helped a friend out with this. There is an easier fix then having to go through all that and add a known device.
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
Click to expand...
Click to collapse
Yes! This works! WooHoo.... just had to uninstall all previous drivers first at the device manager.
Thanks, this worked!
ppd0526 said:
I actually just helped a friend out with this. There is an easier fix then having to go through all that and add a known device.
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
Click to expand...
Click to collapse
Thank you sooo much :victory:, I actually didn't have the wpdmtp.inf in C:\Windows\Inf but I had this folder (link) containing a couple of android drivers and there was wpdmtp.inf file in it, I right clicked and installed it and VOILLAA!!... :laugh: everything went perfect after that. If for any reason you still face MTP problems after this I would recommend to do a manual installation of MTP drivers by going to "Device Manager", click MTP entry with exclamation then "Update Driver Software"->"Browse my computer for driver", navigate to the folder location where you extracted the drivers (link).... you should be done after that. If otherwise you face a problem along the lines of "section in this INF is invalid" while doing manual installation dreboot your PC and find the wpdmtp.inf again, right click then install and you would have fixed your problem. :good:
THANKS!
Oh man! Finally, FREAKING FINALLY, I found a solution that works. Thank u so so so much.
Thank you! This tip worked for me!
I have been having this issue for almost a year, if I wanted pictures and files from my phone, I had to get them from the cloud. Today was the first time in a very long time, that I was able to just copy over files from the phone again from Windows Explorer. THANK YOU!
trying these methods is still failing for me... shows "Pixel" in device manager.. if I try to update drive.. it says either can't find.. or failed...
and if i turn on Transfer Files.. Device manager shows ADB and MTP under "Other" but both fail when trying to update drivers..
YES!!!
5.1 said:
Hi guys and girls...
I just recieved my new phone a few days ago. Plugged it into an old Windows 7 x64 laptop and Windows instantly updated the driver. On a 2016 Dell E7450 Windows 10 x64 laptop... It didn't. Tried the Google USB drver package, but it didn't work either. Windows reports about a problem with an INF file and doesn't finalize the driver install...
I just saw someone reported the same issue in Q/A. I thought it would be a good idea to write a step by step guide.
@ppd0526 proposed an easier solution to fix the issue:
Please if you use this solution, don't forget to say thanks to him in this post: THANKS
Uninstalled the driver and reinstalled using this method works fine! :good:
If someone has difficulty with the above or it doesn't work (which it should) i leave the one below just in case...
Click to show the guide:
Right click on the Windows start menu icon and select Device manager:
From here plug your Pixel using your USB cord to your computer. Pull the notification bar on your Pixel and tap on:
USB charging this device
Tap for more options
From the menu, select:
Transfet files
From here, you should see an "Unknown device" or an "MTP device" with an exclamation mark.
Right click on the device and select "Update driver software":
Click: "Browse my computer for driver software:
Click: Let me pick from a list of device drivers on my computer:
Scroll down till you find "LeMobile Android Device" and select it:
Here, select the second option: "MTP USB device"
Success
Now recognized in device manager:
In "This PC":
Hopefully, it will help some people.
Click to expand...
Click to collapse
WOW, Dude you ROCK!! I have been struggling with this for well over 6 months but just pulled my Pixel back off the shelf for Android PIE and have been determined to find this fix.
Again, thank you very much!!!!!!!
Ki11ian said:
WOW, Dude you ROCK!! I have been struggling with this for well over 6 months but just pulled my Pixel back off the shelf for Android PIE and have been determined to find this fix.
Again, thank you very much!!!!!!!
Click to expand...
Click to collapse
Haha, better late than never... :good:
Cheers...

Categories

Resources