Database Info

adb not working with N1 rooted?

hi,
two days ago i rooted my Nexus One FRF91-Vodafone with these two methods ( forum.xda-developers.com/showthread.php?p=7548842 and forum.xda-developers.com/showthread.php?t=736271). Still some commands of adb don't work and i can't find a solution.
Code:
C:\>cd android/tools
C:\android\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT05EP800252 device
C:\android\tools>adb shell
$ su
su
# id
id
uid=0(root) gid=0(root)
# exit
exit
$ exit
exit
C:\android\tools>adb remount
remount failed: Operation not permitted
C:\android\tools>adb root
adbd cannot run as root in production builds
C:\android\tools>
as you can see the device is connected in debug mode and i am rooted but the commands "adb remount" and "adb root" don't work (and maybe some other commands? i don't know). does it happen because the bootloader is still locked? if so, is there a way to have those commands working without unlocking it? if not, what could it be?
sorry for my english
thanks a lot

[Q] Struggling to Root ONE XL Telstra - HELP?

Ok so Ive been trying to root my Telstra One XL for a few days now and it just wont do it. I've tried several one click options and all do the same thing. Here is a text dump from the one click batch file.
---------------------------------------------------------------
One-Click Root ToolKit For HTC One X!
Script by Max Lee from OneXRoot.com
Credits go to XDA users sparkym3 and Dan Rosenburg for exploit.
---------------------------------------------------------------
[*] This script will:
(1) root your HTC One X on ICS
(2) install Busybox
(3) install SU files
[*] Before u begin:
(4) Make sure to read full instructions at OneXRoot.com!
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Please hit Enter when ready.
Press any key to continue . . .
Rooting...
adb server is out of date. killing...
* daemon started successfully *
Start Rooting...
reboot #1 - DO NOT DISCONNECT YOUR DEVICE!
error: protocol fault (no status)
* daemon not running. starting it now *
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
reboot #2 - DO NOT DISCONNECT YOUR DEVICE!
adb server is out of date. killing...
* daemon started successfully *
error: protocol fault (no status)
* daemon not running. starting it now *
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
failed to copy 'su' to '/system/bin/su': Read-only file system
adb server is out of date. killing...
* daemon started successfully *
Unable to chmod /system/bin/su: No such file or directory
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 *
rm failed for /system/xbin/su, No such file or directory
link failed Read-only file system
failed to copy 'Superuser.apk' to '/system/app/./Superuser.apk': Read-only file
system
rm failed for /data/local.prop, No such file or directory
3632 KB/s (1075144 bytes in 0.289s)
mount: permission denied (are you root?)
/system/xbin/busybox: cannot open for write: Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
rebooting
All Done rooting HTC One X, check out OneXRoot.com for more cool stuff like ROMs
, hacks, tips, and more!
Press any key to continue . . .
Any help would be awesome.

I just figured it all out. It turned out HTCSync running in the background was messing with ADB. Exited that in windows, tried the above method again and it all worked fine... No more 3 Dot!!!
Thanks heaps for all the help everyone

Whoa, that looks like what was happening to me last night trying to root my second HOX. Thanks I will unload HTCsync if it's running.

How to exit htc sync from the backgrd?
Sent from my HTC One XL using XDA Premium App

sstimo said:
How to exit htc sync from the backgrd?
Sent from my HTC One XL using XDA Premium App
Click to expand...
Click to collapse
ctrl+shift+esc -> processes tab -> look for anything regarding htcsync -> right click -> end process tree -> ok = htcsync background tasks killed

wollow86 said:
Ok so Ive been trying to root my Telstra One XL for a few days now and it just wont do it. I've tried several one click options and all do the same thing. Here is a text dump from the one click batch file.
---------------------------------------------------------------
One-Click Root ToolKit For HTC One X!
Script by Max Lee from OneXRoot.com
Credits go to XDA users sparkym3 and Dan Rosenburg for exploit.
---------------------------------------------------------------
[*] This script will:
(1) root your HTC One X on ICS
(2) install Busybox
(3) install SU files
[*] Before u begin:
(4) Make sure to read full instructions at OneXRoot.com!
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Please hit Enter when ready.
Press any key to continue . . .
Rooting...
adb server is out of date. killing...
* daemon started successfully *
Start Rooting...
reboot #1 - DO NOT DISCONNECT YOUR DEVICE!
error: protocol fault (no status)
* daemon not running. starting it now *
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
reboot #2 - DO NOT DISCONNECT YOUR DEVICE!
adb server is out of date. killing...
* daemon started successfully *
error: protocol fault (no status)
* daemon not running. starting it now *
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
failed to copy 'su' to '/system/bin/su': Read-only file system
adb server is out of date. killing...
* daemon started successfully *
Unable to chmod /system/bin/su: No such file or directory
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 *
rm failed for /system/xbin/su, No such file or directory
link failed Read-only file system
failed to copy 'Superuser.apk' to '/system/app/./Superuser.apk': Read-only file
system
rm failed for /data/local.prop, No such file or directory
3632 KB/s (1075144 bytes in 0.289s)
mount: permission denied (are you root?)
/system/xbin/busybox: cannot open for write: Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
rebooting
All Done rooting HTC One X, check out OneXRoot.com for more cool stuff like ROMs
, hacks, tips, and more!
Press any key to continue . . .
Any help would be awesome.
Click to expand...
Click to collapse
Did you try setting your date ahead two days? Then try rooting
Sent from my HTC One XL using xda premium

[HELP] ADB cannot find my ville C2!

Hey guys.
So far, I am working on Ubuntu 13.10 to install Ubuntu touch on my device.
Guys, this is my problem, what is raging me, because it's just a question of drivers -.-
Code:
[email protected]:~/development/android-sdk-linux/platform-tools$ adb devices
List of devices attached
SH265W------ offline
I cannot find my device.
Can anyone help me to fix this?
In bootloader, I cannot do any adb commands, because my terminal is always showing me this:
Code:
[email protected]:~$ adb kill-server
[email protected]:~$ adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:~$
[email protected]:~$ cd ~/development/android-sdk-linux/platform-tools
[email protected]:~/development/android-sdk-linux/platform-tools$ ubuntu-device-flash --channel=devel --bootstrap
2014/06/17 17:10:48 Expecting the device to be in the bootloader... waiting
I have updatet my SDK and my adb is full-updated.
Please help me as fast as you can.. (I'm a little bit noobish on ubuntu)
Greetz
Mii La Bee <3

Push..
Sent from my Bee-Phone using Honey. Greetz! Mii La Bee. <3

Try running adb under root:
Code:
sudo adb kill-server
adb kill-server
sudo adb start-server
AND/OR:
Run:
Code:
lsusb
Output example:
Code:
Bus 002 Device 103: ID [COLOR="Red"]04e8[/COLOR]:[COLOR="Blue"]6860[/COLOR] Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II]
Create new rules file (/lib/udev/rules.d/10-adb.rules), and add this rule to it (edit it with the correct information):
Code:
# ADB
SUBSYSTEM=="usb", ATTR{idVendor}=="[COLOR="Red"]04e8[/COLOR]", ATTR{idProduct}=="[COLOR="Blue"]6860[/COLOR]", MODE="0600", OWNER="[COLOR="Cyan"]your_username[/COLOR]"
Then restart udev (udevadm control --reload-rules) or reboot your computer.

Black SpideR said:
Try running adb under root:
Code:
sudo adb kill-server
adb kill-server
sudo adb start-server
AND/OR:
Run:
Code:
lsusb
Output example:
Code:
Bus 002 Device 103: ID [COLOR="Red"]04e8[/COLOR]:[COLOR="Blue"]6860[/COLOR] Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II]
Create new rules file (/lib/udev/rules.d/10-adb.rules), and add this rule to it (edit it with the correct information):
Code:
# ADB
SUBSYSTEM=="usb", ATTR{idVendor}=="[COLOR="Red"]04e8[/COLOR]", ATTR{idProduct}=="[COLOR="Blue"]6860[/COLOR]", MODE="0600", OWNER="[COLOR="Cyan"]your_username[/COLOR]"
Then restart udev (udevadm control --reload-rules) or reboot your computer.
Click to expand...
Click to collapse
Thanks.
Will try it soon.. I punched my PC.. so ... xD yea we have to wait..
Sent from my Bee-Phone using Honey. Greetz! Mii La Bee. <3

Recovering mmssms.db via ADB on Xperia with broken screen

Hi Guys,
My phone's screen has broken and I can't see anything, although the touch still works. I have been able to connect it to the PC to take my music and photos off the internal storage, and my contacts are backed up to Google, but my texts are not and I'd like to recover them.
I've read that they normally reside in /data/data/com.android.providers.telephony/databases/mmssms.db and I should be able to pull this via ADB.
When the phone is booted to the OS it is not detected by ADB at all with 'error: device not found'. I thought USB debugging was on, but obviously not. I can boot to recovery (custom CWM) and now adb will connect to the device. However, when I try to pull the sms db I get 'No such file or directory'
Code:
[email protected] ~ $ sudo adb start-server
[sudo] password for james:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected] ~ $ adb shell
error: device not found
[email protected] ~ $ adb devices
List of devices attached
[email protected] ~ $ adb devices
List of devices attached
CB5122TH5B device
[email protected] ~ $ adb shell
~ # mkdir /mnt/sdcard/tmp
~ # cat /data/data/com.android.providers.telephony/databases/mmssms.db > /mnt/sdcard/tmp/mmssms.db
cat: can't open '/data/data/com.android.providers.telephony/databases/mmssms.db': No such file or directory
~ # su cat /data/data/com.android.providers.telephony/databases/mmssms.db > /mnt/sdcard/tmp/mmssms.db
cat: can't open '/data/data/com.android.providers.telephony/databases/mmssms.db': No such file or directory
/sbin/sh: su: not found
~ # exit
[email protected] ~ $ adb pull su /data/data/com.android.providers.telephony/databases/mmssms.db
remote object 'su' does not exist
~ # ls /data
~ #
It would appear the directory /data is empty but I bet that's because I don't have permissions to view the contents. I'm guessing this is also why su is not found.
Can anyone help me to get over this hurdle? Please bear in mind I'm not familiar with ADB and not great in a Linux shell either; the above commands took a bit of reading to find, but I do understand what they're trying to do.
My phone is a Sony Xperia T LT30p and is rooted running Xperiment 3.5 and Clockworkmod recovery 6.0.4.6 and I'm running ABD on Linux.
Any help would be appreciated! Cheers :good:

scrcpy connect to remote adb server problems

I am using adb version 1.0.32 on an armv7l development board. In an attempt to use scrcpy to connect remotely to the adb I first set:
on the armv7l remote board:
adb kill-server
adb -a nodaemon server start
then from another terminal on the remote board try doing a "adb devices" to make sure it sees the connected android device but what happens is unexpected I get:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
with no devices showing up. It is lighting off a completely new adb server and ignoring the fact that it is already running.
ps shows
1304 root 30184 S adb -a nodaemon server start
1315 root 20964 S adb -P 5037 fork-server server
If I don't have the first adb running and do "adb devices"
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
001e06481bc3 device
I tried this same scenario on my ubuntu 18.04 box with adb 1.0.32 and had no problem with "adb devices" launching an extra process:
ps only shows
xxx 18322 10891 0 16:49 pts/2 00:00:00 adb -a nodaemon server start
and adb devices shows:
List of devices attached
001e064809ac device
without the extra daemon getting launched.
This is causing scrcpy to not function properly when I am trying:
export ADB_SERVER_SOCKET=tcp:<ip of remote board>:5037
scrcpy --tunnel-host=<ip of remote board>
it returns :
scrcpy 1.23 <https://github.com/Genymobile/scrcpy>
INFO: Tunnel host/port is set, --force-adb-forward automatically enabled.
ERROR: Could not find any ADB device
ERROR: Server connection failed
naturally it couldn't find any devices because "adb devices" is not working properly on the remote board. Incidently I tried the same scenario with just the localhost and it works flawlessly.
The question is why is the same version adb not working on one platform vs another?