So I am doing a Dash Install (Here me out). I know there are other successful tablets installed and the bugs have been worked out of those, however my dash limits me to only installing this specific tab 4 because of size. I have rooted and installed TWRP already, I can access ADB devices through CMD on my windows machine and see the devices. However when I running fastboot oem-charge-mode 0 it goes into a continuous 'waiting for devices' prompt. I need this so that when the tablet dies I do not have to remove my dash.
Related
I am hoping someone can help me before the ICS OTA hits in the US.
I am trying to root, but I can NOT get ADB to see the TPT.
I am using win 7 64 bit, and have downloaded the adb driver and modified the .inf. It shows up in dev man under android phone as thinkpad adb, but when I run adb devices...nothing.
I installed that latest Java dev and android stk but still nothing.
The TPT is on OTA 2.5.
I have searched everywhere but cannot fined any answer.
Any ideas?
Thanks!
Is USB debugging enabled on your tpt? Did you try a different USB cable/port? On your PC are you in the same directory as adb.exe?
Yes, Yes, and Yes.
ADB is running fine...it just cant see the TPT even tho windows can.
I'm sure you're a little frustrated. I had that happen, and it turned out there were two adb processes running. A reboot fixed that. I'm sorry I don't have the answer.
It IS frustrating, but I appreciate your suggestions!
try running the emulator and make sure you can connect to it via adb, as a check to make sure adb deamon is starting up correctly.
True. Worked for me.
For whatever reason, it was my system that I do all my adb work on....just refuses to see the TPT.
Used my notebook with nothing installed and it went just fine.
My Win7-64 PC could only see my TPT as a portable device, and was listed between drive letters. I wanted to see it under "Android Phones."
After about 6 hours of searching, having installed the Lenovo-provided drivers probably 40 times, I went out on a limb and opened the Device Mangler, individually uninstalled each of the portable devices, including the TPT. Rebooted my PC. Plugged in the TPT, and finally it appeared under Android Phones, and ADB recognized it (I typed "adb devices" in the command prompt and it was listed).
What it came down to is the driver that wanted to be the default was trumping the one I wanted. Beware the Diva. She's not all that.
I should add that I also unplugged a usb card reader (that was making all the drive letters) because I thought that might be the culprit, but it still showed up in the Device Mangler, so I don't think unplugging it made a difference.
I miss Win2K.
My tablet is in developer mode, USB data bugging is clicked on. In storage, MTP is clicked on. Using the latest Android SDK along with the latest Google Win USB drivers (also different cables, different ports, uninstalled and reinstalled all drivers and software, turned on and off debug, debug authorization.. Just about everything I can think of.) Also, no, not rooted, fully stock. Been searching for a few days for this problem that occurs while trying to upgrade to Kit Kat 4.4 from JWR66Y 4.3 on my nexus 10.
Plug in my n10 normally and WIN7 will see it in the device manager as Android Device, Android Composite ADB Interface, Hardware Ids =
USB\VID_18D1&PID_4EE2&REV_0226&MI_01
USB\VID_18D1&PID_4EE2&MI_01
Boot the n10 into recovery and the adb sideload, the n10 shows everything correctly and waits for the adb sideload file. CONNECT THE USB cable and Win7 does not recognize the device. Tries to find a driver for 'other devices, nexus 10' but eventually returns with no driver found. Tried installing from specific directories (new google usb driver download), letting it search windows update evewn search my entire hd. It cannot locate a driver. Device manager shows an entirely different Hardware Id for 'other devices, Nexus 10' =
HARDWARE IDS (OTHER DEVICES, NEXUS 10)
USB\VID_18D1&PID_D001&REV_0226
USB\VID_18D1&PID_D001
I did a search with this information and found others had this ID/problem with their Nexus 7 during the Jelley Bean upgrade!
http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/
There is no Nexus 10 in this file, but the second line of 'google nexus (generic)' list the ID that I have when booting normally.
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01
I assume that if I replace this number with the ID I see in adb sideload mode (USB\VID_18D1&PID_D001) I should be able to install the correct USB and ADB drivers as others did on their n7 (shown in that link)?
My problem is identical to tbe description on that link, but I am guessing at the fix for the n10. This sounds like the solution to me, but I am also worried if it could be a sign of a bigger broblem or might brick my nexus. So any help would be appreciated!
Thanks all!
Ed
I tried changing the ID initially as well but then adb throws errors about the ini file not being verified. In the end I installed these to get the adb drivers properly installed: http://koush.com/post/universal-adb-driver
After that Windows finally properly recognised my N10 (and the command adb devices also showed it could see the device) and I was able to sideload kitkat.
Duplicate deleted
KiraYahiroz said:
I tried changing the ID initially as well but then adb throws errors about the ini file not being verified. In the end I installed these to get the adb drivers properly installed: http://koush.com/post/universal-adb-driver
After that Windows finally properly recognised my N10 (and the command adb devices also showed it could see the device) and I was able to sideload kitkat.
Click to expand...
Click to collapse
Wow, I hope someone finds this thread and it saves them the headaches and searches I have been through. Worked just like you said, installed this adb usb driver and it picked it right up. I wonder why google couldn't get the google driver to read their own nexus 10 tablet!
Now running Kitkat 4.4 with no data loss, thanks to you Kira!
Thank you!
Ed
KiraYahiroz said:
I tried changing the ID initially as well but then adb throws errors about the ini file not being verified. In the end I installed these to get the adb drivers properly installed: http://koush.com/post/universal-adb-driver
After that Windows finally properly recognised my N10 (and the command adb devices also showed it could see the device) and I was able to sideload kitkat.
Click to expand...
Click to collapse
Thank you, been banging my head around to try and find a fix, worked like a charm for sideloading KitKat.
cheers
Oh my god, pushing this thread because I almost needed 6 hours to root my Nexus 10 with other ADB drivers but this one worked!
Hello all,
I'm having difficulty trying to run EFS Pro v2.0.70/v2.0.72 to backup my EFS folder on my GT-I9505. I get stuck at the part when it says "Initializing ADB server..." and it just sits there. I just want to point out that I had made a backup of my EFS folder on my GT-I9505 when I first got my phone (around May), but it seems to have been deleted! Anyway, I found some good steps in another thread, as follows:
Before starting, check the following:
Device is fully rooted
SuperSU (or equivalent) is active
USB debugging is ON (Settings->More->About device: Tap several times on "Build number" to enable Developer options and tick USB debugging)
Busybox downloaded AND installed (normal or smart) on your device
Microsoft .NET Framework 4.0 installed on your PC
Samsung USB driver is installed (either by installing Kies or just the driver alone.
Kies is not active (neither as application nor process, check Windows Taskmanager)
ADB fully functional ("adb devices" recognises your phone) -- (look here for a basic ADB tutorial/how to)
In case ADB is not running you need to install the ADB driver
Run EFS Professional as administrator.
Make sure to grant SuperSU access to Shell and confirm the RSA fingerprint request once they pop up on your screen.
Of course, your device should be on the home screen, not on the lock screen
I've followed all these steps, checking each methodically, and guess what, I'm still stuck at "initializing ADB server..."! I even go to cmd and type in "adb devices" and my phone shows up, I see on my phone that a shell has been granted, and yes, I am rooted, I have busybox, and Samsung drivers, .NET 4.0 framework and USB debugging, it's driving me mad, I've even tried different USB ports, and nothing!
If anyone has any suggestions, please fire away!
I have the exact same problem, but with my S3 (I9300) ...
No one who can help?
Did you get sorted my i9505 is the same and I have two phones but one wont work..
Hi, i've been using my nexus 4 for a long time but recently (probably since patch 4.4.2) I've had this problem where I don't get adb authentication prompt on my phone when using usb-debugging. I have Cyanogenmod latest stable version installed.
I'm using adb drivers that come with android sdk (also tried 4 others!), version of adb is recent (1.0.31) and I have verified that by typing adb version.
adb devices list my nexus 4 as unauthorized (reboot bootloader gives unauthorized too) cause the prompt doesn't appear as it should.
I've done some extensive searching and here are what I've tried (to summerize these, I've tried all solutions currently on the internet probably) - this list might be incomplete as I don't remember everything I did:
Uninstall all usb related drivers and reinstall the correct drivers again (multiple times, with reboots).
Disabling and reenabling usb-debugging. Unplug and plug phone in. restarting adb server... etc.
disabling MTP, even trying PTP and tethering (desperation).
trying to set usb secure to 0 (wasn't set to zero, any way for me to set it to zero?)
trying to manually copy keys from computer to android (very weird that this one didn't work, maybe I did something wrong?)
Edit: I think I figured out why setting secure to 0 didn't persist. Working on it, learning how to unpack bootimg.
I can't access my N7 with adb (when booted) or fastboot (while in the bootloader). It's connected via a USB cable. This is both with a Mac and WUGS. Commands like fastboot devices or adb devices return nothing as the device isn't seen. I can connect my N4 and use those commands without problem. I just tried doing the same with my 2013 N7 and it's not being seen, either. Strange. I don't think I've had this problem before on the Mac. I have on Windows, which I can sometimes resolve by installing and reinstalling drivers until something works.
I'd wanted to update the 2012 N7 to Lollipop.
Thoughts, anyone?
maigre said:
I can't access my N7 with adb (when booted) or fastboot (while in the bootloader). It's connected via a USB cable. This is both with a Mac and WUGS. Commands like fastboot devices or adb devices return nothing as the device isn't seen. I can connect my N4 and use those commands without problem. I just tried doing the same with my 2013 N7 and it's not being seen, either. Strange. I don't think I've had this problem before on the Mac. I have on Windows, which I can sometimes resolve by installing and reinstalling drivers until something works.
I'd wanted to update the 2012 N7 to Lollipop.
Thoughts, anyone?
Click to expand...
Click to collapse
Crazy as it sounds, try another USB cable. Reboot everything, plug in fresh, and try again. Failing that, use WUGS to reinstall all your USB drivers. Use the stock Google.
The cable was the culprit. I tried another and it worked. Thanks so much!
I'm having a similar problem that's driving me insane.
Nexus 7 wi-fi version
I've loaded every driver on the planet and in recovery mode it simply will not show up. And I'm not talking won't show up using ADB, I get absolutely nothing in device manager. So before anyone tells me to point to the device and manually change the driver, there is no device to try and point a driver to.
In "normal" mode, it shows up perfectly fine in Device Manager as Android ADB Composite Device. ADB will list it in devices with no problem. It will accept the "adv reboot recovery" command perfectly and reboot the tablet into stock recovery. The minute it does that, the device disappears from the Device Manager list and nothing takes it's place. I've tried to have it search for new hardware, I've tried the Google USB drivers kit, I've used Koush's Universal Driver install. I've used 3 different cables on 2 different USB ports.
This is a completely stock N7 running 4.4.4 plugged into a Windows 8.1 64 bit PC.
The last thing I'm wondering is do I have to unlock the bootloader at all? I don't want to because it'll wipe the tablet. If so I guess I'll just wait out the actual OTA rather than try to sideload it.
Any suggestions would be appreciated.
Yaz75 said:
Any suggestions would be appreciated.
Click to expand...
Click to collapse
Any suggestions at all?
Ummm... does the Stock Recovery actually run "adbd" by default? If it doesn't (or it doesn't start adbd until you execute the sideload menu item), then you wouldn't normally see anything on the other side of the cable with a stock Recovery. (I don't have my tablet with me to check)
Here's an extra "any suggestion at all":
Get rid of Windows and use Linux; there are no drivers to screw with in the latter case.
No, seriously. But probably not what you are thinking.
If you can get a "live CD" to boot** on your PC, you can (as root) run the "lsusb" command to see what devices are enumerated on the USB bus, port by port.
In conjuction with the decoder ring at the end of this post, you can determine from inspection of the USB VID/PID identifiers whether or not all the hardware is behaving, and whether or not the tablet is in the mode you think it is supposed to be in.
The reason this is valuable is that it allows you to take drivers completely off the table; if everything is as it should be, then you know that all the hardware and cabling are functioning correctly, the tablet is behaving correctly, your PC hardware is behaving correctly, and that 100% of the problem is Windows driver issues.
If you want to go the extra 1/4 mile, you can put a copy of (Linux) fastboot & adb plus your flashables on a USB key, and run adb or fastboot from the Live CD boot. It won't matter that the live CD doesn't have them preinstalled, they will be on your USB key. It will be easier on you if you can find statically-linked fastboot and adb binaries; if not you will have to copy one or two supporting shared libs (.so files) along with the binaries, and find out what LD_LIBRARY_PATH is all about.
suppose the USB key mounts at /media/usb1; then
$ sudo /bin/bash
# mkdir /tmp/tools
# cp /media/usb1/fastboot /media/usb1/adb /media/usb1/*.so /tmp/tools/
# chmod 755 /tmp/tools/*
# export LD_LIBRARY_PATH='/lib:/usr/lib:/tmp/tools:.'
# cd /tmp/tools
# ./fastboot devices
OR
# ./adb devices
Good luck; as you are using Windows you are going to need it. Hahaha LOL
**depending on whether your BIOS on your win 8.x PC can be toggled between UEFI and Legacy modes or not, this can be either trivial (Legacy boot mode) or complicated (UEFI) requiring a "Trusted Computing" crypto boot shim from MisterSoftie.
Ok this works for me
Use USBDeview (http://www.nirsoft.net/utils/usb_devices_view.html)
delete all the associated drivers like Google, Samsung, etc for ADB, etc
Restart Computer
Reconnect N7 without MTP and USB debugging
Wait for PC to recognise device and install driver
*If you see something like PC unable to recognise device, go into device and Update Driver and choose "Automatic....."
Disconnect and Reconnect with MTP and USB Debugging
Wait for PC to recognise device and install driver
Restart N7 in bootloader
Wait for PC to recognise device and install driver
Profit
* My PC OS is Win 8.1 Pro 64bit
make sure mtp is switched off, i couldnt get adb or fastboot on my nexus just now . switched off mtp and works fine