Database Info

[Q] Gingeritis - phone no longer seen in adb...?

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.....

[Q] No ADB in APX mode (B70 sbkv2 rooted TF101)

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

help rooting One X

I'm trying to root my phone using the method here: http://forum.xda-developers.com/showthread.php?t=1709424
without much luck... On page 33 one person mentioned getting to Daemon successfully started and having it just hang there, which is my problem, then said it was just dumb user error with never explaining what it was. Several people followed up with the same problem but no answer. Initially I started it up and it would just start up the daemon and sit, so I rebooted my phone to try again and now it doesn't even do that, it just spits out Exploit by beaups, script by designgears and sits there with a blinking cursor.
Phone is in charge only mode, USB Debugging enabled, HTC sync not running, have tried multiple USB cables and ports. I have a mac and am trying this through VirtualBox (and yes, the USB device for the phone is attached - not mounted as a disk). I can only guess this is what's causing the problem but I don't really see why it shouldn't work. Anything I can try?

Did you set the date on the phone forward a day or 2 before you tried again, like the thread says?
I didn't use this root method (rooted back on 1.73). But another person posted having similar troubles. Reinstalling the HTC drivers did the trick for that person.

redpoint73 said:
Did you set the date on the phone forward a day or 2 before you tried again, like the thread says?
I didn't use this root method (rooted back on 1.73). But another person posted having similar troubles. Reinstalling the HTC drivers did the trick for that person.
Click to expand...
Click to collapse
Date doesn't really come into play since the installer doesn't go anywhere. What HTC drivers? There's no mention of those. On a whim I installed HTC Sync and rebooted, I do get farther but don't seem to really get anywhere still. It does more stuff but seems like it keeps killing the server and a check for software updates finds nothing to update.
Exploit by beaups, script by designgears
* server not running *
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
Go to Settings, ATT Software update, check for updates.
Waiting for device to Reboot...
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
Done! Rebooting...
error: more than one device and emulator
Press any key to continue . . .
Click to expand...
Click to collapse

Well I realized that last attempt had HTC Sync running, so I killed that. Now I'm back to sitting at daemon successfully started. For fun I tried to do the non one click root, however indeed after doing the first command I get the more than one device or emulator connected error. adb devices lists my phone once initially, but after running: adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb devices lists my phone multiple times and I can go no further. I might have to try and find a real windows computer to use, maybe the vm is just doing something funky here.

chadcf said:
What HTC drivers? There's no mention of those. On a whim I installed HTC Sync and rebooted.
Click to expand...
Click to collapse
The drivers get installed with HTC Sync. So re-installing Sync would have fixed the drivers, if that was causing the issue. Sorry I can't help you anymore than the suggestions I've already made. Hopefully, somebody else can help.

chadcf said:
Well I realized that last attempt had HTC Sync running, so I killed that. Now I'm back to sitting at daemon successfully started. For fun I tried to do the non one click root, however indeed after doing the first command I get the more than one device or emulator connected error. adb devices lists my phone once initially, but after running: adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb devices lists my phone multiple times and I can go no further. I might have to try and find a real windows computer to use, maybe the vm is just doing something funky here.
Click to expand...
Click to collapse
That's a typical VM issue. You can run right from linux or mac with the manual method. Just get the right version of ADB for your O/S and add a ./ before each command that starts with "adb".

[Q] ADB Shell Error Message

Hello
I'm trying to run a shell session but getting this error message
adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Ok, it seems obvious what the problem is but I can't find a solution
The phone is plugged, Fastboot seems to recognise the connexion as says fastboot USB
HBOOT version 1.14
Not sure what to do
Any idea?
Many thanks
EDIT Problem Solved - should launch from Recovery - Thank you

How to twrp to GT-I9506

I can not find a method to get twrp to the GT-I9506.
With Odin it does not work even it says all was programmen OK (still remains the old recovery)
and with adb it doesn't work too:
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
01b293754 sideload
adb usb
error: closed
error: closed
adb sideload recovery.img
error: protocol fault (no status)
error: protocol fault (no status)
What can I do (did try various usb cable) ?
Found the solution: You have to disable "Auto Reboot" in Odin !