Database Info

cannot access adb and cannot bypass registration?

ok so i downloaded the SDK and the windows drivers. i downgraded the phone to rc29 and have just enabled adb on the phone using the command <enter>setprop persist.service.adb.enable 1<enter> and <enter>telnetd<enter>. i opened up CMD in windows and changed the directory where i needed and tried to run adb and it gave me this error: "* daemon not running. starting it now *
* daemon started successfully *
error: device not found"
why did it give me this error? and alo im stuck at the part where im supposed to "copy a busybox binary" using adb push. i dont know exactly what im supposed to do to do that step. i am a noob at this stuff so please be kind and use noob terms and steps.
Thanks
PS: i did connect the phone to the pc with the data cable and the add new hardware thing popped up and i installed the drivers like i was supposed to. it said something about they were installed correctly but may not be working properly, whatever that means.

Try this....
Unplug the phone.
Reboot the computer.
When fully rebooted, plug the phone back in and see what the computer does.
Did it say, "Found new hardware" or some such message?
Did it say that it couldn't find a driver?

Okay - after the OTA updates, I'm now having the same problem! Ouch!
Plugging in, running DOS Command...
c:\> adb devices
Reports that there are no devices attached!
BUG!!!!!!!!!!!!!!!

[Resolved] [Q] Device in APX but not visible using ADB

Hi there,
I have a problem and seems all the threads i found are not helpful....
I have a asus transformer (B50), stock Android 3.2, I've unrootet it from
prime 1.7 using ADB for copy blob file, while tablet was turned on in normal mode.
Here is what makes me sick: I see my device in ADB as long as it's not in APX mode. When i boot my device in APX mode (I use System-Profiler to check if it's really there) then the list of devices is empty.
alex$ sudo ./adb kill-server
alex$ sudo ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
alex$
The same at my Vista PC... device is in APX but not visible for adb...
I used CWM to unroot and install prime, but I don't want to use it again...
Any more ideas? Would be great if someone could help me on that.
thx.

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] XT1039 bootloop and can't get adb to pull files

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

Android 10 ADB

Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
I'm trying to disable some apps through ADB but when the

Cj214 said:
Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
I'm trying to disable some apps through ADB but when the
Click to expand...
Click to collapse
You can't see the device while on fastboot mode of you type adb devices.
You need to make sure debugging is on in the developer preferences.

ADB appears to be working just fine for me.

When using adb make sure you have debugging enabled and grant the popup on screen

adb is not fastboot. You can use adb on twrp or booted system. Fastboot is on bootloader mode.

Also need to make sure that the proper USB drivers on the computer are installed/updated.

Cj214 said:
Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
Click to expand...
Click to collapse
This is working exactly as intended, and not exclusive to Android 10, but rather has been the case as long as I can remember (Jelly Bean? KitKat? Maybe much earlier?):
adb: Only works when booted to OS or in TWRP. Debugging required to be toggle on in phone settings. Does not work in bootloader-fastboot mode.
fastboot: Only works in bootloader-fastboot mode. Debugging is not required to be toggled on.

D:\OnePlus3\Fastboot>adb sideload stock7.zip
opening 'stock7.zip'...
connecting...
adb server version (40) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Thats what adb gives to me...

Bringer1 said:
D:\OnePlus3\Fastboot>adb sideload stock7.zip
opening 'stock7.zip'...
connecting...
adb server version (40) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Thats what adb gives to me...
Click to expand...
Click to collapse
Sounds like another adb server is still running. What does adb kill-server and then trying again do

a second adb server was running.
TNX

Can I mount system rw using adb enabled recovery img from the following link:
https://forum.xda-developers.com/7t-pro/development/recovery-oxygen-os-stock-recovery-adb-t3991865