Database Info

Windows 7 RUU - how to get it working

Simple really.
When it fails search for instructions on how to get it working with Vista - I never had a problem with Vista myself but upgrading to Windows 7 it just failed so I found http://forum.xda-developers.com/showthread.php?t=313001
and followed the instructions there.
I was trying it out omn my Universal as I don't use it now so it didn't matter - but now I have a shiny new ROM on it I might just start using it again

Windows 7 Ultimate x64
RUU's were crashing for me just at the PDA detection stage.
I tried custom compatibility settings for the RUU:
Run this program as administrator
Disable Visual Themes
Disable Desktop Compisition
Run in Windows XP SP2 Compatibility Mode
These should work with Win 7 x64 however you may need to apply these settings to the other executable files in the RUU folder (EnterBootLoader and RUUGetInfo).

Thanks. It seems as that worked. I also had to switch usb ports.
~Leko

Issue using ADB and Windows 7?

I apologize if this is not the right forum and I would request that it be moved, not deleted, if possible if its the wrong forum. I'm kind of stuck here.
Have a bit of an interesting situation. I am running Windows 7,
got the USB driver successfully installed... boot up the command prompt and BAM:
C:\android>adb remount
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
C:\android>adb devices
List of devices attached
Here is the weird thing...
C:\android>fastboot devices
HT97JLV05321 fastboot
It looks like the fastboot is recognizing that my phone is attached but the adb shell will not. Any ideas what the issue could be?

LOL, I just switched back from Ubuntu to Windows 7 just to see how things have progressed. There are so many little Windows 7 quirks that drive me crazy that drove me back to Ubuntu almost instantly. Give Linux a try. A good starting Linux OS would be Linux Mint:
http://www.linuxmint.com/index.php

I had a similar issue when I tried it. Despite the fact that there are 64-bit drivers for Vista/7 available, I don't believe they actually work for ADB currently. I'm pretty sure everyone who has ADB working is using Windows XP 32-bit.

I actually burned a copy of Ubuntu that I was just going to run off of the CD. I'll give that a shot and see if it lets me do what I need to do. Thanks for the quick responses.

I am using Windows 7 final (RTM) (64-bit) and also Windows 7 Beta (32-bit) on two different computers. They all work fine with adb commands.

ch4dr0x said:
I apologize if this is not the right forum and I would request that it be moved, not deleted, if possible if its the wrong forum. I'm kind of stuck here.
Have a bit of an interesting situation. I am running Windows 7,
got the USB driver successfully installed... boot up the command prompt and BAM:
C:\android>adb remount
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
C:\android>adb devices
List of devices attached
Here is the weird thing...
C:\android>fastboot devices
HT97JLV05321 fastboot
It looks like the fastboot is recognizing that my phone is attached but the adb shell will not. Any ideas what the issue could be?
Click to expand...
Click to collapse
I faced the same problem a few days ago. I have Windows 7 Ultimate x64 and in a first installations the drivers work fine and the device has been displayed, but BAM when I try to use ADB no way.
After many tries I resolved the issue running the Command Prompt as "Run as administrator" and VOILA worked fine.
I hope this can help you.

ch4dr0x said:
I actually burned a copy of Ubuntu that I was just going to run off of the CD. I'll give that a shot and see if it lets me do what I need to do. Thanks for the quick responses.
Click to expand...
Click to collapse
Try Mint instead of Ubuntu. Mint is Ubuntu based. The big difference with Mint is that it already has all of your codecs installed - great for beginners.

If you installed first the htc sync, you have to remove the current drivers..
and had the drivers from the androidsdk pack! There's is a a lot of program who delete usb installed hardware/drivers.. delete all from htc on this programs!
Hope this solves ur issue!

I use Win7 64bit(rc1) .. i have the amd64 driver installed..
I see the phone from adb (not fastboot) when it's normally connected with USB debugging turned on.
I see the phone from fastboot (not adb) when it's in fastboot mode.

I have no choice but to laugh at myself, just realized I was IN FASTBOOT on my phone and not recovery. Fail me.
Now if I could just edit this apps2hd code /sigh.

ricardomega said:
If you installed first the htc sync, you have to remove the current drivers..
Click to expand...
Click to collapse
and remove htc sync, there are a process than cause problem with adb (i don't remember the name)
I kill this process and adb 100% work fine, or unistall HTC Sync..

GOOGLE KNOWS EVERYTHING!!
http://www.google.com/search?hl=en&rlz=1C1CHNB_enUS326US327&q=remove+usb+drivers+programs+android+htc&aq=f&oq=&aqi=

ricardomega said:
GOOGLE KNOWS EVERYTHING!!
http://www.google.com/search?hl=en&rlz=1C1CHNB_enUS326US327&q=remove+usb+drivers+programs+android+htc&aq=f&oq=&aqi=
Click to expand...
Click to collapse
Except that... that wasn't my issue Its ok thanks for the input.

"error: device not found"
I can't get ADB to work with my Windows 7 X64 Ultimate. Windows automatically install a driver for the phone when I plug it in. When I try to install my own driver with the one in the SDK, I get:
"....doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Doing a update to the driver, it says the one I have installed is already up to date.
I have the latest Win 7 with all important Window updates.

parrot5 said:
I am using Windows 7 final (RTM) (64-bit) and also Windows 7 Beta (32-bit) on two different computers. They all work fine with adb commands.
Click to expand...
Click to collapse
The same confi, the same result

Everything works fine here with Win 7 Ultimate x64, you just install the driver in the Android SDK.

make sure u have usb debugging checked... cause i have windows 7 rtm ultimate and my adb works fine... i just loaded the needed file into windows/system32 and also put my fastboot.exe in there and added the tools folder to the environment variables and have no problems

What do I load to the system32 folder? I can't install the drivers from the SDK package. Is there a way to overwrite the ones Windows automatically installs and thinks is more up to date?

detonate said:
"error: device not found"
I can't get ADB to work with my Windows 7 X64 Ultimate. Windows automatically install a driver for the phone when I plug it in. When I try to install my own driver with the one in the SDK, I get:
"....doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Doing a update to the driver, it says the one I have installed is already up to date.
I have the latest Win 7 with all important Window updates.
Click to expand...
Click to collapse
Make sure your phone is in recovery mode and NOT fastboot mode.

Finally, I experienced that error you people had been reporting. It MAY have to do with the HTC Sync driver, as suggested, but it really had worked fine with other roms before, so I am not sure. I tried uninstalling and reinstalling the driver, tried to push the ADB driver manually, but that didn't work. And, before I try to uninstall the HTC Sync driver as suggested (I don't even know if I have that installed), I got it working by just plugging in another USB flash drive. Go figure.
So for anyone still having the issue after trying all other solutions, try this bizarre one:
1. Go to device manager and uninstall the HTC disk drive device. (This alone won't work, I tried)
2. With phone still plugged in, plug in a USB disk drive (or maybe just any USB device?) into another USB port.
3. Suddenly Windows 7 detect that unknown ADB driver, as it should. Now you can go ahead to install the correct ADB driver.
As a side note, this computer running Windows 7 Beta/RC have had a lot of problems with USB disk drives in general. The problems disappear after Windows 7 RTM (final).

Unbrick your NEXTBOOK 7 PREMIUM

Ok, just bricked my Nextbook 7
Here is how I flashed a firmware without access to recovery:
If you are in a bootloop, Connect USB and Power.
Press and hold pin on back until you hear windows try to detect a device but the screen is off.
Download this: http://arctablet.com/assets/tools/Firmware/Rockchip_CPU_based/Rockchip_Batch_Tool_v1.4.zip
Install the driver from the drivers folder.
3. Installing the drivers on the computer
Following the tablet entering in recovery mode, the computer should now show it has found a new USB device and prompt for a device driver. Select the appropriate driver in the driver directory from the Rockchip Flash Tool 1.4 package.
It will then install the driver for RK29 Device
4. Sending the firmware to the tablet
The flashing tool should display a green square around the number 1 in the lower left area of the Windows application.
Select the firmware file to flash using the button in the top right area of the application. Select the update.img file from here:
http://www.multiupload.com/NQHSNZJSO2
Then push the Upgrade button to transfer the selected firmware to the tablet.
The firmware will be copied to the tablet, a progression counter will go from 0% to 100% on this step, followed by a verification.
You are done, let the tablet reboot and update itself. It should take a few minutes for the flash process to finish.
This procedure has been successfully tested on Windows XP 32 bits for flashing a bricked NextBook 7 Premium YF1011 (but should work on others)

Hi, the multiupload link seems down, would it be possible to re-up? thanks!

And how exactly are you supposed to install the drivers from the driver folder? Because those are not Runable files, theyre drivers, with no install command. So, my daughters nextbook is bricked, wont install drivers(says not successfully installed after i plug it in) and there is no way to install the drivers from the batch file. Anything you left out??? Id like to unbrick this thing. Thanks..

SOLVED
I found out how to install the drivers on windows 7!
Follow this:
click the start button > type in the search box right above the start button "device manager"
(make sure the tablet is plugged in and in USB MODE)
right click the tablet or unknown device
select install/update driver manually
browse for the driver in the download folder then it should be updated
worked for me.

Nextbook 8 stuck in bootloop
I am a noob. My Nextbook 8 is stuck in bootloop, the last app i downloaded was firefox. Ive read that this can be fixed by starting safe mode and doing a factory reset, how do i do this?!? Im desperate, and would greatly appreciate any help that works, thanks.

[Q] Bricked Asus Transformer TF 101 B60

Hi all first off I'm sorry if this has been posted before but I'm having a problem unbricking an Asus transformer tf101 B60, I'll start with what's going on or not for that matter. lol
1. Boot to recovery is CWM-Based Recovery v5.5.0.4 roach-tf101-r2
2. will not see sd card / backup-restore= -2014-04-05.02.52.56 / no files found
3. Choose a zip = e: can't open /sdcard/update.zip
4.PC windows 7 pro 64 bit will not see the tablet when plugged into usb getting unrecognized device,force driver still getting yellow ding=device cannot start
if I plug in the usb and turn on the tablet windows does not even see that and unit sits on logo screen. and other screen the cold lynx boot that hangs there.
So in short I'm hitting a brick wall, windows won't see it, it won't see the SD card in recovery mode.
I've read in these posts how to fix this problem and have all the software / firmware you name it, but they all say almost the same thing, windows needs to see the device in order for any of these fixes to work, and thus is my wall I'm hitting.
Any help to find a solution to this problem would be oh so thankful to you all and call you Tablet Gods, this was a tablet given to me as a paper weight and I thought if it boots it can be fixed?
Thanks for your time and God like tablet knowledge.
Cheers.

Install the APX drivers (Universal Naked Drivers) and use the tool "Easyflasher" to flash TWRP recovery (Forget CWM) both from this link
http://forum.xda-developers.com/showthread.php?t=1688012
You might need to install the APX drivers manually using Device Manager
If you find that the PC still does not see the TF101, you might need a new cable

Driver Not Working
*Detection* said:
Install the APX drivers (Universal Naked Drivers) and use the tool "Easyflasher" to flash TWRP recovery (Forget CWM) both from this link
http://forum.xda-developers.com/showthread.php?t=1688012
You might need to install the APX drivers manually using Device Manager
If you find that the PC still does not see the TF101, you might need a new cable
Click to expand...
Click to collapse
I booted the unit into recover mode and windows sees unknown device..Ok
Tried to install new naked driver and getting a splash saying not compatible with windows 64 bit, I tried this on a brand new windows 7 pro 32 bit laptop and got the same results. I do have a brand new usb cable for it thinking that the old one was faulty, tried adb again same thing no device found, are there any commands in terminal emulator that can force the driver on the usb port? I'm thinking that if windows sees an unknown device then at least it sees something there just not whats there? Am i wrong in that somehow it's lost the usb firmware connection? so the driver will not install and if forced does not make the connection to the device? So this is my results.
So I'm ready to put gun in mouth over this, my laptops going to divorce me over driver abuse and the tablet mocks me with the frozen Asus logo.
Again Thanks for all the advice and i'll keep slugging it out.As this unit is in perfect condition outside of the Bricked part

You don't need to boot it into recovery mode to start with, just install the drivers normally first with the TF101 connected and booted normally
It's always going to say it can't find the device if the driver isn't installed
Focus on getting that APX driver installed and working, once you have that installed, Im pretty sure it will see the device fine

Asus TF101 B60 Softbrick? What Now?
Hello all.
I've been searching in vain for an answer to my Bricked Asus tf101? I'm just going to get right to the problem.
I can't get the tablet to be seen by windows 7 pro 64bit, Unknown device and yes I've tried everything, except asking if there's a way to force connection through a terminal like I've seen done with a router and a network switch to force a flash file so as to get at least a response after a reboot instead of just the Asus splash screen, here's a summary.
The Good.
1. I can boot to recovery CWM-based recovery v5.5.0.4 roach-tf101-r2 with menu's
Bad: Does not see sd card only see's internal and there's no file or folder error for backup/restore
2.Boots to screen with 2 icons data wipe and linix cold boot and goes nowhere from there just hangs.
So I'm stuck here, I have all to tools to do the job only if windows would see it, Adb does not see device which means the same thing no driver no fix,
Everywhere I read it says do this and that and it will restore to factory, that would be great if windows saw the thing, so I'm looking for a way to get the tablet to boot to something other than a loop. also tried the put the E101_SDUPDATE.zip in the root of the SD card and restart, does not see the card or file or both so it's not loading the file?
1. windows 7 not seeing device, will not take force drivers, Universal-Nvidia-Asus- MTP
2. recovery does not see sd card, so can't flash new anything?
3. So no communication from SD/USB
4. Is there a terminal command I can use to force a Blob or flash a recovery to the tablet when drivers and USB don't respond?
And to top that off my laptop filed for divorce for driver abuse..lol I'm not giving up.
Thanks to you all,
I want to thank you all for your time and advice it is very much appreciated, and I'll keep slugging away because I know there's a fix out there.
Cheers.

Drivers need to be signed in 64bit windows, use 32bit Win 7 either on another machine or in VMWare or Virtualbox etc
Then the drivers should install

Thanks
*Detection* said:
Drivers need to be signed in 64bit windows, use 32bit Win 7 either on another machine or in VMWare or Virtualbox etc
Then the drivers should install
Click to expand...
Click to collapse
Thanks for the Advice, Is there a thread outlining this so I can give it a try? I do have a new laptop I'm building out with windows 7 Pro 32bit as I've had so much trouble with the 64bit version.

If you're building a 32bit Win 7 laptop, then no need for virtual machines, just use that laptop, this is the Easyflasher thread, you should only need to follow the couple of simple instructions once you have 32bit Win 7 running
http://forum.xda-developers.com/showthread.php?t=1688012
Basically in a nutshell:
1) Plug in TF101 to PC and make sure ADB debugging is enabled in Dev options on TF
2) Drivers will/should fail to install
3) Open Device manager
4) Right click the ! missing driver
5) Update driver > Point to extracted Universal Naked Drivers from Easyflasher thread
6) Drivers should install
7) Leave TF plugged into PC
8) Power TF off
9) Hold Volume Up & Power until the PC sounds the USB connect sound
10) TF is now in APX mode (Nothing on TF screen yet) drivers should install, check Device Manager, if it doesn't install, point it to the extracted Universal drivers folder again until they are installed
11) Follow instructions to use Easyflasher
12) Done

*Detection* said:
If you're building a 32bit Win 7 laptop, then no need for virtual machines, just use that laptop, this is the Easyflasher thread, you should only need to follow the couple of simple instructions once you have 32bit Win 7 running
http://forum.xda-developers.com/showthread.php?t=1688012
Basically in a nutshell:
1) Plug in TF101 to PC and make sure ADB debugging is enabled in Dev options on TF
2) Drivers will/should fail to install
3) Open Device manager
4) Right click the ! missing driver
5) Update driver > Point to extracted Universal Naked Drivers from Easyflasher thread
6) Drivers should install
7) Leave TF plugged into PC
8) Power TF off
9) Hold Volume Up & Power until the PC sounds the USB connect sound
10) TF is now in APX mode (Nothing on TF screen yet) drivers should install, check Device Manager, if it doesn't install, point it to the extracted Universal drivers folder again until they are installed
11) Follow instructions to use Easyflasher
12) Done
Click to expand...
Click to collapse
I am trying to get mine out of the reboot loop and cant seem to get it into APX mode to install the drivers.....any idea how go from here and have been trying step 9 above.
Will keep on trying to see if I can get it to work

Sicknote said:
I am trying to get mine out of the reboot loop and cant seem to get it into APX mode to install the drivers.....any idea how go from here and have been trying step 9 above.
Will keep on trying to see if I can get it to work
Click to expand...
Click to collapse
Need more info
What happens when you try to enter APX mode?
Which OS are you running on the PC?
Do the APX drivers install ?
etc etc etc

*Detection* said:
Need more info
What happens when you try to enter APX mode?
Which OS are you running on the PC?
Do the APX drivers install ?
etc etc etc
Click to expand...
Click to collapse
When i try to put it in APX mode, the screen goes black but pc does not see it. I have tried this bit lots of times and not sure if I'm missing something...
Have the drivers in a folder on my desk top. Have watched videos on YouTube but what i see is not happening when i try it...
OS is windows 7.
Drivers don't install.

Sicknote said:
When i try to put it in APX mode, the screen goes black but pc does not see it. I have tried this bit lots of times and not sure if I'm missing something...
Have the drivers in a folder on my desk top. Have watched videos on YouTube but what i see is not happening when i try it...
OS is windows 7.
Drivers don't install.
Click to expand...
Click to collapse
You're not going to be able to put the tablet into APX mode till you get the drivers installed correctly.
With the tablet connected to the computer and the tablet on, download the naked driver package. open up device manager and right click on Other Devices - APX and chose update driver. Chose browse and then go to where you downloaded the naked driver package. If it complains that they aren't signed, click install anyway. If successful, you should now be able to put your tablet in APX mode.

Oneplus USB Drivers missing after wipe and fastboot flash

After softbrick I wiped and flashed OOS 10.3 (following https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665, flash-all-partitions-fastboot.bat). All works fine so far but when I plug in the phone and select file transfer, I no longer see the Oneplus CD with the USB drivers (was this erased in the wipe and not reloaded?). Windows 10 still recognized the phone as A6003 using a windows driver (Microsoft from 2006, version 10.0.18362.1), but the data transfer between phone and PC is terribly slow (< 0.5MB/s) and a process "windows driver foundaton" uses lots of CPU).
Any suggestion how to restore the driver section on the phone, and/or install native Onpleus 6 drivers on Windows 10 ?

In the meantime i reinstalled 10.3 again with local upgrade (+ re-root), which solved a number of other issues (eg missing emojis). This made the Oneplus CD drive appear again, but without logo and without drivers. Presumably still something missing...
I found USB drivers on the web (https://www.getdroidtips.com/download-oneplus-usb-drivers/) and did install those, but actually nothing changed. Still have the standard microsoft drivers..
Maybe somebody could quickly check if this driver is actually the same as the one provided by oneplus: Microsoft date 21/06/2006 version 10.0.18362.1 ?
Thanks