So I've been playing around with the Beta VI build of Gingeritis and was going to change out the bootanimation to go back to the stock one, and adb isn't functioning for me all of the sudden. USB Debugging is flipped on on the device so I'm not sure what's up.... anyone else having this problem?
Flashing a rom won't bork your adb. Use cmd prompt to get into your adb directory & type "adb start-server" (without quotes), connect phone to computer, then type "adb devices". What does it say
Sent from my ADR6400L using XDA App
That's what I thought, however it seems there's something not quite right here:
G:\temp>adb kill-server
G:\temp>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
G:\temp>adb devices
List of devices attached
G:\temp>
Go to settings > wireless & networking, enable internet passthrough mode
Sent from my ADR6400L using XDA App
Yup that's what I was missing - installed the driver and adb picked back up again. Weird that the drivers between the kernels changed, wonder if it's just because that gingersense kernel is based off another device and not the T-Bolt.....
Hi,
I rooted my TF101 using Razorclaw, then i installed Recovery Installer, i can enter CWM and make nandbackup, everything is ok.
BUT
When i want to use ADB in APX mode, the TF doesn't appear in the devices list.
Asus Sync is installed, the USB Debugging option is checked (i unchecked and checked it again) and when the TF is booted in normal mode, i can see it in ADB :
D:\android\Eeepad\scripts>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
37c708940c041d7 device
Click to expand...
Click to collapse
I can see it in the device manager :
Asus Android Composite ADB Interface
Click to expand...
Click to collapse
When i switch to APX mode, in the device manager i have :
NVIDIA USB Boot-recovery driver for Mobile devices
Click to expand...
Click to collapse
(it seems the drivers are ok ?)
D:\android\Eeepad\scripts>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Click to expand...
Click to collapse
=> no device listed
I made "adb kill-server", "adb start-server", no more device listed
As soon as i reboot the TF, it appears again in the device list and i can go to the shell :
D:\android\Eeepad\scripts>adb devices
List of devices attached
37c708940c041d7 device
D:\android\Eeepad\scripts>adb shell
$ su
su
#
Click to expand...
Click to collapse
Is there an issue with B70 sbkv2 or CWM ?
Do you still access ADB in APX mode with the same config ?
Thanks
there is no ADB in APX (bootloader) mode
Hi,
Sorry for that, i was thinking i should at least see the device.
But I understand now, bootloader mode does what it's made for and nothing more
Thanks
so my tf300 is rooted and unlocked bootloader, im trying to do the disabling journaling
im already at twrp and my tablet is connected to my pc
but everytime im trying the adb shell it says:
daemon could not start, starting at port 5037
daemon started succesfully
error: device not found
what seems to be the problem here? i tried to install my sdk, still no luck.
Using USBDeview (suggested here - comment 7 : http://code.google.com/p/android/issues/detail?id=2676 ) helped me get my TF300 to appear under 'adb devices'.
Still can't seem to access the device via localhost though.
(I'm trying to get access for web-dev purposes - see here : http://forum.xda-developers.com/showthread.php?t=1966358 )
I don't image the adb command is able to access that sector of the device but for the record, when I connect, I can see the device but
C:\Users\Brad2\Downloads\adbUnzip2Cdrive\adb>adb kill-server
C:\Users\Brad2\Downloads\adbUnzip2Cdrive\adb>adb devices * daemon not running. starting it now on port 5037 * * daemon started successfully *
List of devices attached
51cfe754 offline
I can connect to the device with Odin in download mode, but I do not see a 'pull' or extract feature on Odin, only push.
What is the trick to extracting the boot files from the device? All drivers and sdks are installed and using the current adb.
Hi,
all of a sudden, my XT1039 Moto G has entered a never ending bootloop that goes like this:
- powers up, motorola animation runs fine
- if the sim is inserted, it lets me tap the numbers for 5 seconds, then it soft reboots by itself
- if the sim is not inserted, it loads fine, it lets me do what I can do in 5 seconds, then it soft reboots by itself
my XT1039 is totally stock, unrooted, the last app I've installed is a flashlight app from the Google App Store, to turn on and off the back led, three days ago, and has been working fine for three days since then.
What I have done so far:
- booted android to safe mode: 5 seconds, and it bootloops again
- booted to recovery and wiped the cache partition, rebooted to android and the problem is still there
- when powered off, held the vol up and down buttons for two minutes: somebody wrote it worked for him, it doesn't work for me
- tried all the other options on the recovery menu (Factory, BP Tools, QCOM), but they all seem to do nothing, and get me again to the bootlooping
- booted to flashboot with an otg cable and a usb pendrive, hoping a magic "backup to usb" option would show up, but it doesn't
- disconnected the battery for 5 minutes, and replaced it with a known good working one out my wife's XT1032 (same battery model), still no luck
now I'm almost ready to boot to recovery and wipe data/factory reset, but I still would like to copy the Pictures folder out of the device first, so I tried with adb:
- installed the Motorola (and the universal too) drivers on my Win 8.1 and downloaded a recent version of adb.exe (Android Debug Bridge version 1.0.32)
- during the 5 seconds of bootloop life, I can browse the XT1039 folders from Win 8.1 explorer, but 5 seconds is too short to do anything
- booted the XT1039 in flashboot, but the command adb devices doesn't see my device
- while in flasboot, navigated in Recovery --> Apply Update from ADB, the Win 8.1 alerts me there's something new on the USB chain, and adb devices says:
List of devices attached
TA98601*** sideload
but in the sideload mode it seems I can't run the pull command to get my files out of the damned device, every command like adb pull, push, shell, returns the same error:
error: closed
Is there anything else I can try to get my files out of the XT1039, before restoring it to factory ?
Any hint is highly appeciated, thanks
I can see that you were able to boot into recovery, and assuming that you are using a recent version of TWRP, you can attach the device to a computer via USB while in TWRP. and copy the pictures folder that way.
Hope this helps
Edit: It sound like you were using the stock recovery, so boot into fastboot mode and flash the recovery with instructions from here.
Professor Gibbins said:
I can see that you were able to boot into recovery, and assuming that you are using a recent version of TWRP, you can attach the device to a computer via USB while in TWRP. and copy the pictures folder that way.
Hope this helps
Edit: It sound like you were using the stock recovery, so boot into fastboot mode and flash the recovery with instructions from here.
Click to expand...
Click to collapse
You can't install TWRP with a locked bootloader, and unlocking the bootloader wipes data...
Of course. It never actually occurred to me that the bootloader would be locked.
Although, have you tried running
Code:
adb kill-server
adb start-server
and trying the 'adb pull' commands again?
Professor Gibbins said:
Of course. It never actually occurred to me that the bootloader would be locked.
Although, have you tried running
Code:
adb kill-server
adb start-server
and trying the 'adb pull' commands again?
Click to expand...
Click to collapse
Yes, unfortunately the bootloader is locked, the phone is stock as if just bought out of a shop.
Here's the sequence of commands ran while in fastboot
C:\adb>adb kill-server
* server not running *
C:\adb>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\adb>adb devices
C:\adb>adb pull /system/app/Settings.apk
error: device not found
and the here's the sequence of commands ran in fastboot-->recovery --> apply update from ADB (the only option I've found that seems to enable some adb functionality)
C:\adb>adb kill-server
C:\adb>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\adb>adb devices
List of devices attached
TA98601*** sideload
C:\adb>adb pull /system/app/Settings.apk
error: closed