Database Users

Adb issues

Ok trying to learn a little about adb. and im trying to push a file to my phone.
cd c:\android-sdk-windows\tools ( done this to change the directory)
c:\android-sdk-windows\tools>adb push screengrab.apk .\sdcard.
failed to copy screengrabber.apk to .\sd card: Read-only file system
how do i change it to a write only file system also. i tryed adb shell i granted it SU permissions. then i done something and its telling me daemon still not runningerror cannot connect to daemon. what exactly does this mean it will start up successfully then it will stop and that message will come up

your sdcard is not read only. make sure you do not have it mounted at all on your computer and verify you are using PROPER command
adb push screengrab.apk /sdcard/

Pirateghost said:
your sdcard is not read only. make sure you do not have it mounted at all on your computer and verify you are using PROPER command
adb push screengrab.apk /sdcard/
Click to expand...
Click to collapse
there is nothing mounted in my pc not internal or sd card when i used the PROPER command. It brings up a whole lot of stuff like the different commands and stuff.

How to prevent update/block update

I've been reading a couple of threads on preventing OTA updates and can't seem to figure it out. I'm more interested in the sqlite & ADB method from this thread (http://forum.xda-developers.com/showthread.php?t=933291). I read this thread about 10 times over and over but can't seem to get it to work. Can someone that's knowledgeable please put instructions that an idiot like me can follow?
I have a rooted NC with firmware 1.2.
1. I've downloaded sqlite3 and nookcolor-easyADB to my PC.
2. I've extracted nookcolor-easyADB and install the install.vbs file.
3. Connected my NC to my PC via USB cable
4. My PC recognizes my NC and the microSD card as a different drive.
i followed the following steps from the thread and nothing works:
***************************************************************
Attached is a working sqlite3 binary.
Copy it to /system/bin
(I transfered it to my SD, then used rootexplorer (mount R/W) to copy into /system/bin))
you will now be able to edit sqlite databases on the nook itself.
--------------------------------------------------------------------------------
Attached Files sqlite3.7z (11.9 KB, 56 views)
--------------------------------------------------------------------------------
In your terminal:
$ adb pull /data/data/com.bn.devicemanager/databases/devicemanager.db devicemanager.db
$ sqlite3 devicemanager.db
sqlite> update registry set value='manual' where name='com.bn.device.fota.mode';
sqlite> .q
$ adb push devicemanager.db /data/data/com.bn.devicemanager/databases/devicemanager.db
$ adb reboot
Congrats Your NC is now permanently blocked from any future BN OTA auto updates.
No more build.prop spoof hacks for each release (sideload only),,,,,, yada yada
***************************************************************
Questions:
should I create a directory in my PC (C:/windows/system/bin) and copy sqlite3 to the /bin folder or copy sqlite3 to my microSD card and insert it into my NC?
Please be very elementary in your answers (as you were explaining it to your 6 year old). Thanks in advance.

There is a free version of SQLite with graphic user interface that allows you to change the fota field from "auto" to "manual". Do a search of title only for "block" and you should find it.

crazyasian2 said:
I've been reading a couple of threads on preventing OTA updates and can't seem to figure it out. I'm more interested in the sqlite & ADB method from this thread (http://forum.xda-developers.com/showthread.php?t=933291). I read this thread about 10 times over and over but can't seem to get it to work. Can someone that's knowledgeable please put instructions that an idiot like me can follow?
I have a rooted NC with firmware 1.2.
1. I've downloaded sqlite3 and nookcolor-easyADB to my PC.
2. I've extracted nookcolor-easyADB and install the install.vbs file.
3. Connected my NC to my PC via USB cable
4. My PC recognizes my NC and the microSD card as a different drive.
i followed the following steps from the thread and nothing works:
***************************************************************
Attached is a working sqlite3 binary.
Copy it to /system/bin
(I transfered it to my SD, then used rootexplorer (mount R/W) to copy into /system/bin))
you will now be able to edit sqlite databases on the nook itself.
--------------------------------------------------------------------------------
Attached Files sqlite3.7z (11.9 KB, 56 views)
--------------------------------------------------------------------------------
In your terminal:
$ adb pull /data/data/com.bn.devicemanager/databases/devicemanager.db devicemanager.db
$ sqlite3 devicemanager.db
sqlite> update registry set value='manual' where name='com.bn.device.fota.mode';
sqlite> .q
$ adb push devicemanager.db /data/data/com.bn.devicemanager/databases/devicemanager.db
$ adb reboot
Congrats Your NC is now permanently blocked from any future BN OTA auto updates.
No more build.prop spoof hacks for each release (sideload only),,,,,, yada yada
***************************************************************
Questions:
should I create a directory in my PC (C:/windows/system/bin) and copy sqlite3 to the /bin folder or copy sqlite3 to my microSD card and insert it into my NC?
Please be very elementary in your answers (as you were explaining it to your 6 year old). Thanks in advance.
Click to expand...
Click to collapse
1. Go here and get the sqllite browser and throw it in a directory on your pc.
2. Use adb and pull the database file from your nook to your pc (like the instructions you quoted).
3. Use the sqllite browser and make the changes and save them.
4. Use adb and push the file back to your nook.
5. Reboot your nook
6. Enjoy being free from updates.

Here's the idiot's guide that worked for me:
1. Go download the following 2 files:
nookcolor-easyADB.zip
sqlitebrowser_200_b1_win.zip
2. Extract “nookcolor-easyADB.zip
this will create a file “.android” in the following directory C:/Users/your_user_account
extract “sqlitebrowser_200_b1_win.zip” anywhere
3. Connect your NC to your PC via USB port.
4. Open the command prompt (it’s in your program, accessories directory)
You should have a prompt that looks like this – C:\Users\your_user_name>
5. Type the following command:
adb pull /data/data/com.bn.devicemanager/databases/devicemanager.db devicemanager.db
This command will go grab the file “devicemanager.db” from your NC and place it in the following location: C:/Users/your_user_account on your PC.
6. Now go to the directory where you extracted “sqlitebrowser_200_b1_win.zip” and double click on the file “SQLite Database Browser 2.0 b1.exe”. This will run the browser that will allow you to open the file “devicemanager.db” and edit it.
7. In the browser click file/open database. It should automatically take you to where the file “devicemanager.db” is located. Select that file.
8. Click on the “Browse Data” tab.
9. Click on the “Table:” pull down menu and click on “registry’.
10. If you look at line 7, all the way to the right is the “value” column it should say “auto”.
11. Double click on “auto” and another window will pop up.
12. Change the word “auto” to “manual”.
13. Click on “Apply changes” and close the window.
14. Click on “save” button on the top left and close the browser.
15. Go back to the command prompt and type the following:
adb push devicemanager.db /data/data/com.bn.devicemanager/databases/devicemanager.db
This command will push the file “devicemanager.db” from your PC back to your NC with the updated file.
16. Type the following command to reboot your NC:
adb reboot
DONE!

I would think the simplest method, using materials you should be halfway familiar with from rooting, is to install ClockworkMod Recovery to your NC. I know it will stop the update from installing, but I'm not sure if the update would quit trying to install.
The simplest ways to get CWM on your NC are:
1) get the ROM Manager app and "Flash ClockworkMod Recovery"
2) if you have a CM7 sdcard, it probably already has ROM Manager, and flashing from there will also install CWM to your internal recovery.

Taosaur said:
I would think the simplest method, using materials you should be halfway familiar with from rooting, is to install ClockworkMod Recovery to your NC. I know it will stop the update from installing, but I'm not sure if the update would quit trying to install.
The simplest ways to get CWM on your NC are:
1) get the ROM Manager app and "Flash ClockworkMod Recovery"
2) if you have a CM7 sdcard, it probably already has ROM Manager, and flashing from there will also install CWM to your internal recovery.
Click to expand...
Click to collapse
This is my thinking as well. B&N tried pushing the update to me and a coworker yesterday. CWR blocked it as expected. Rebooted and all is well. As you mentioned, time will tell if B&N will continue to try to push v1.3 to me. If it becomes obnoxious, I may go this route.

[Q] Mac OSX - ADB - List of devices attached Blank

I am running on a Mac (OSX Lion) and have installed android-sdk-macosx.
I am trying to connect to a Kindle Fire 6.2.2
However, this is as far as I can get:
Code:
bash-3.2# ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
bash-3.2#
As you can see, no devices show up.
I have tried switching cables, USB ports, reboot the device and my machine... banging my head against the wall.
Nothing works.
I have read about 29 pages of posts through this forum, and Googled it.
No dice.
Any suggestions?

would not use the sdk at all - if you use the mac/linux version of kfu you save a lot of time and space - you don't need to use kfu if you don't like to - but all commands you'll ever need are in the tools folder of kfu - it also includes drivers and setup scripts - maybe give it a try:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653

mkdir ~/.android
echo 0x1949 >> ~/.android/adb_usb.ini
ADB needs this entry to see the Kindle Fire no matter what OS you're on.

right - there is also a installation script for this included in the pack - install.sh if i remember right

took the advice above and it's still not working for me. i have the same exact problem. when i try to run install_drivers.sh i get:
cp: drivers/adb_usb.ini: No such file or directory
Done!
logout
[Process completed]
When I run KFU i get:
/Users/donaldclark/kfu/run.sh: line 84: seq: command not found
please help

as far as i know (don't own a mac) you have to call the commands with
./ from terminal window - eg ./run.sh

I also got the same error message at line 84 running the install script in OSX 10.6.8
-E

it's from eratosthene - give him a pm - i'm shure he can help you
http://forum.xda-developers.com/member.php?u=1616763

Try remove the usb driver from your device and re-install gain.

I use Kindle_Fire_Utility_MacLinux_0.9.2 3 with adb.mac
and its located right inside my root directory (not under users) step before.
I went to the files and I opened file called
install_drivers.sh
I did deleted everything behind -p and just dragged
the adb_usb.ini (its located in drivers) into that install_drivers.sh script and I hit save.
thats how it looks like
mkdir -p /Kindle_Fire_Utility_MacLinux_0.9.2 3/drivers/adb_usb.ini/adb_usb.ini
Than I just run adb.mac and all is operational
my kindle was rooted with burittoroot2
If you need those files send me a pm I have them in my dropbox.
somboonr said:
Try remove the usb driver from your device and re-install gain.
Click to expand...
Click to collapse
there is no uninstalling drivers like in windows.

line 84 SOLUTION
Incarnate609 said:
took the advice above and it's still not working for me. i have the same exact problem. when i try to run install_drivers.sh i get:
cp: drivers/adb_usb.ini: No such file or directory
Done!
logout
[Process completed]
When I run KFU i get:
/Users/donaldclark/kfu/run.sh: line 84: seq: command not found
please help
Click to expand...
Click to collapse
Regarding the "run.sh: line 84: seq: command not found", I found out that the "seq" command is not recognized with MAC OS... so I did a search and replace, replacing "seq" with "jot -". Now it works.
Reference: Search google for seq and mac

What worked for me.
I had the same problem after updated the sdk on my MacBook Mac OSX 10.6.8
cd to the tools directory (where android program is located)
run:
./android update usb
./android update adb
then edit the ~/.android/adb_usb.ini file and add 0x1949 as the last line (your previous adb_usb.ini file is overwritten by the above commands).

[TOOLS][ADB][Windows]Push files to device through ADB*now include deodex tools*

See my previous post before in post#2
This is a simple batch file using ADB..
With this you can use ADB to manage your file or APK , Backup, Push Your File to device, or pull file from device..
ADB Work on Stand by Mode (Home Screen) or in Recovery Mode, just set it up..
Extract ADBTOOLSv1.0.1.zip and you will find :
command.bat : Windows Batch Command
_BACKUP_OUT : folder where your backup process done and made
_FLASHING_OUT:
folder for flashing your :
kernel (place your boot.img here)
recovery (place your recovery.img here),
modem (place your modem.bin here)--only for gt p7300
_MODDING_FILE: Folder where your file were created by PULL process
Folder where file for PUSH process should be here
_BATCH_INSTALL : place your APK here for batch install
tools: ADB.exe and busybox binary
success_APK : A folder created for All apk from _BATCH_INSTALL move here after instalation.
Click to expand...
Click to collapse
Notes:
ADB can access all file from device from CWM Recovery, especially CWMR 5.5.0.4
ALL you need to do is:
From Recovery menu, you need to mount /data and /system for ADB working..
THEN, From Command Prompt set ADB Mode to "recovery".(This Batch File set ADB mode to "Home Screen" by default)
So when you use ADB from Online device ( I mean a stand by device).. you dont need to change ADB Mode..
After you set up, you can use ADB as you like..
Code:
=============================================================================
:::: ADB TOOLS FOR GT P7300 and P7310 by suwandiapr
-----------------------------------------------------------------------------
| [*] Before use read this:
| --make sure you have installed adb drivers for your device
| --enable "USB DEBUGGING"
| from (Menu\Settings\Applications\Development)
| --enable "UNKNOWN SOURCES"
| from (Menu\Settings\Applications)
| --increase screen timeout to 10 minutes
| --connect USB cable to PHONE and then connect to PC
| --MAKE SURE YOU HAVE A ROOTED DEVICE AND BUSYBOX
| --Place the right file in the right folder
| --Some feature like Flashing need more tester..so please be aware
| --If you use adb recovery feature, set ADB Mode to recovery
| mount /data and /system from your device recovery
| --If you use adb from homescreen, set ADB Mode to HomeScreen
| --All you Do is your own Risk, use with carefull
-----------------------------------------------------------------------------
****Turn on the screen and allow superuser permission when asked!****
_____________________________________________________________________________
| Current MODDING FILE: NONE | ADB MODE :HomeScreen | sdcard path: /sdcard/|
=============================================================================
:::: ADB PULL ::::
=============================================================================
0 Pulling file from /data ( see result in _MODDING_FILE)
1 Pulling file from /system partition ( see result in _MODDING_FILE)
2 Pulling file from SDcard ( see result in _MODDING_FILE)
3 Backup recovery ( see result in _BACKUP_OUT)
4 Backup Kernel ( see result in _BACKUP_OUT)
5 Backup modem (for P7300 only-see result in _BACKUP_OUT)
6 Backup /system (tar format-see result in _BACKUP_OUT)
7 Backup /efs (tar and .img format-see result in _BACKUP_OUT)
8 Backup APK from /data/app (tar format-see result in _BACKUP_OUT)
=============================================================================
:::: ADB PUSH ::::
=============================================================================
9 Pushing file to /data ( from _MODDING_FILE to device)
10 Pushing file to /system ( from _MODDING_FILE to device)
11 Flashing recovery ( from _FLASHING_OUT to device)
12 Flashing Kernel ( from _FLASHING_OUT to device)
13 Flashing modem for GT P7300 ( from _FLASHING_OUT to device)
=============================================================================
:::: Setting ::::
=============================================================================
14 Set current working File ( for PUSH and PULL )
15 Install busybox on device (need root)
16 Set ADB mode (if you on recovery mode)
17 Install apk ( from _MODDING_FILE to device)
18 Install batch apk ( from _BATCH_INSTALL to device)
=============================================================================
:::: Reboot Menu ::::
=============================================================================
19 Reboot System
20 Boot Into Recovery
21 Reboot Bootloader
22 Quit

My previous post
inspiration from congox case
when you got a problem with bootlop and you forget make a nandroid backup
only have file from other ROM with flashable.zip and need to push the file from your computer to device
you have a recovery support with mount /system and mount /data (tested on CWM 5.5.0.4 and overcome CWM 5.1.2.6) and you can enter this menu while bootloop happen..
STEP 1 : MANUAL
Connect your device with computer
From device, Go to recovery - mounts and storage - mount /system and mount /data
From your computer go to adb terminal and type this
Code:
adb shell "ls /data/media/"
If you can see list of file from your device sdcard, so you make adb work for your device ..
Place your zip file on your path, says on C://backup.zip and you want to copy the file to /sdcard/download/ and type this code
Code:
adb push backup.zip /data/media/download/.
wait for copying progress done..
After you done with moving file to device sdcard, check content of your sdcard with this code
Code:
adb shell "ls /data/media/download/"
When you found your file from list, you can flash backup.zip from recovery
STEP 2 : WINDOWS BATCH FILE
I made a simple Batch File for windows (sorry i dont have MAC or LINUX distro) , this file will make a folder with name "emergency" in SDCARD and with your files inside that.
Extract the FLASHER.rar somewhere on your Local folder,example: on your " Desktop" Folder
in folder "FLASHER" you will find runme.bat and folder "files"
Rename your file ((flashable.zip files you want to send through ADB) to "backup.zip" and then Put your file into this path /FLASHER/files/myfiles/ (just replace the existing "backup.zip" with files from yours)
Connect your tab with Computer
Reboot into Recovery Menu from your device
From menu Mounts and Storage choose mount /system and /data
From your Computer go To Folder flasher and klik runme.bat
Follow the instruction on window untill copying process done and device reboot to recovery again (copying process will take a minutes depend on your file size)
Now you can flash a emergency ROM from recovery
Window instruction
Code:
-----------------------------------------------------------------------------
ADB EMERGENCY COPYING TOOL for TAB 8,9
created by SUWANDIAPR
-----------------------------------------------------------------------------
[*] This script will:
(1) COPY YOUR FILE FROM COMPUTER TO SDCARD/emergency/*
(2) CHECKING YOUR CONNECTED DEVICE DIRECTORY
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) make sure u have installed CWM 5.5.0.4 ON YOUR DEVICE
(3) connect USB cable to PHONE and then connect to PC
(4) Rename your Flashable .zip file with "backup.zip"
and place inside "myfiles" folder on your Computer
(5) from Recovery Menu, Choose "Mounts and storage" then
-mount /system and -mount /data
(6) CONNECT YOUR TAB WITH PC WHILE ON RECOVERY MENU
---------------------------------------------------------------
CONFIRM ALL ABOVE
Sorry for my Bad english, if there is somebody want to correct every words i use , im very welcome and will change with the proper words and sentence..
Hope this help someone..

Nice guide, thanks!!

I needed some help with mounting the system using adb through a batch file.
I use this command
adb -d shell mount -o remount rw /system
But the mounting fails (I have a rooted phone )
pleas help me I know this is off topic

2 possible reasons for this command to fail:
- /default.prop (on the phone) contains the following line: "ro.secure=1". Then you need another boot.img (in fact just a modified ramdisk). look for "unpack-bootimg.pl" or "unpackbootimage" you may find a guide how to do this manually (not too easy). A rooted kernel would also do the trick.
you can check your default prob with this command "adb shell cat /default.prop".
- in some cases mount requires more parameters. try "adb shell mount" and look for the line containing "/system". In front of system is the "device-name". in my case the mount command would look like this:
mount -o remount,rw /block/dev/mmcblk0p24 /system
hope this helps and sorry for answering off-topic questions....

nail16 said:
I needed some help with mounting the system using adb through a batch file.
I use this command
adb -d shell mount -o remount rw /system
But the mounting fails (I have a rooted phone )
pleas help me I know this is off topic
Click to expand...
Click to collapse
you can use busybox and call the binary from the shell
i assume that your device in normal mode ( in home screen)..
here some example..
Code:
su
adb push busybox /tmp/.
adb shell "chmod 755 /tmp/busybox"
adb shell "tmp/busybox mount -o remount,rw /system"
after you type "su" superuser will prompt a request, choose "allow".
glitschi667 said:
2 possible reasons for this command to fail:
- /default.prop (on the phone) contains the following line: "ro.secure=1". Then you need another boot.img (in fact just a modified ramdisk). look for "unpack-bootimg.pl" or "unpackbootimage" you may find a guide how to do this manually (not too easy). A rooted kernel would also do the trick.
you can check your default prob with this command "adb shell cat /default.prop".
- in some cases mount requires more parameters. try "adb shell mount" and look for the line containing "/system". In front of system is the "device-name". in my case the mount command would look like this:
mount -o remount,rw /block/dev/mmcblk0p24 /system
hope this helps and sorry for answering off-topic questions....
Click to expand...
Click to collapse
yes you right glistchi, samsung lock adb root on new firmware on my SG- Note..
And make me flash an older firmware for rooting..

new update

Never mind, got it to work

i want to push same file in data system (/data/data) but my tab is not root. can i??

if from cwm recovery, yes you can.. if from stand by mode (home screen) the answer is no... you need root to make it happen..

i got this error
please help

Stuck in recovery mode

so i wiped all my data in twrtp (all of it) and now im stuck in recovery mode beacuse i cant flash another rom onto my nexus 7
I have tried sideloading with adb sideload but it keeps giving me this error
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* failed to write data 'protocol fault (no status)' *
i have tried destroying adb in task maanger but that doesnt work also running the cmd on admin
Edit: i think i sorted it out i adb push file /data/media
instead of /sdcard that seemed to work. when i tried /sdcard it said it was closed
Anyways yea i was able to flash the files once i pushed them into that folder
So i guess the threads closed not sure why all those other methods didnt work.

me too
john566 said:
so i wiped all my data in twrtp (all of it) and now im stuck in recovery mode beacuse i cant flash another rom onto my nexus 7
I have tried sideloading with adb sideload but it keeps giving me this error
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* failed to write data 'protocol fault (no status)' *
i have tried destroying adb in task maanger but that doesnt work also running the cmd on admin
Edit: i think i sorted it out i adb push file /data/media
instead of /sdcard that seemed to work. when i tried /sdcard it said it was closed
Anyways yea i was able to flash the files once i pushed them into that folder
So i guess the threads closed not sure why all those other methods didnt work.
Click to expand...
Click to collapse
i have the same problem
i do not know what to do =confused:

Here what i did, you need this its the sdk
http://developer.android.com/sdk/index.html
anyways unzip and go into it sdk-> platformtools
place the zip files you want to push inside the folder
then go to start search in windows type cmd right click (run as admin)
You have to be in recovery for this (mines was twrp)(CWM might not work)
type cd "name of the directory that the platform tools are inside"
Example:C:\Users\New\Desktop\adt-bundle-windows-x86-20130522\sdk\platform-tools
this was were mines are
then type adb push "file name" /data/media
example:adb push foo.txt /data/media
After that go into the install folder and try to find the files you pushed