Database Users

I can´t install apk to my X10i via CMD adb??

Can not find a usbdriver for ADB that works for sony ericsson x10i?
http://code.google.com/p/adb-file-explorer/
//dong 2007

dong2007 said:
Can not find a usbdriver for ADB that works for sony ericsson x10i?
Click to expand...
Click to collapse
Not looked hard enough ADB, Fastboot, and Nandroid for Noobs

It is not for X10i, but G1 and droid?
Shall i first install Android SDK?

dong2007 said:
It is not for X10i, but G1 and droid?
Click to expand...
Click to collapse
Worked for me.
dong2007 said:
Shall i first install Android SDK?
Click to expand...
Click to collapse
nephron said:
This Guide is for windows only. If you are using Mac OS X please go here: ADB For Dummies
If you are using Linux please go here: [HOW-TO]Set up Android SDK/ADB/Fastboot on Ubuntu Linux
--------------------------------------------------------------------------
Things you need:
Android SDK - Download
Winrar - Download (32bit) Download (64bit)
Windows PC
USB Cable
--------------------------------------------------------------------------
Setting up the Android SDK
Download the file from above
Unzip to your desktop
Take the "android-sdk-windows" folder and move it to the root of your hard drive (C:\)
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-windows\tools
Now, [Get new sdk (1.5r3) to work]
1. Run SDK Setup.exe
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Preparing your phone for ADB
Go to Settings on your phone
Select Applications
Select Development
Make sure 'USB Debugging' is checked
--------------------------------------------------------------------------
Installing Drivers
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
For Android SDK 1.5r3+
1. Run SDK Setup.exe
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in
Code:
cd C:\android-sdk-windows\tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line
Now you are all set to run adb commands
Note: for a list of commands type in 'adb' in cmd
CONGRATS YOU NOW HAVE ADB FULLY RUNNING!
--------------------------------------------------------------------------
"Im not getting a notification of Android ADB when i plug in my USB"
Why: Your computer has detected your phone but as a protable device and as a storage device.
Fix: This took me a lot of research and time to figure out so this is what your are going to do.
First download USBDeview - Here
Unzip it
Run USBDeview.exe as Administrator
You will see all drivers being used on your computer
Highlight and Uninstall all drivers with the description have HTC Android (Should be 3 of them)
Right Click on the driver and press uninstall
Once done, Unplug your phone and plug it back in
You should now get the notification of the ADB device
Follow the steps above to install the drivers
--------------------------------------------------------------------------
When Typing just adb in cmd you will get whats called a "usage doc" which gives you a lits of commands that you can use:
Code:
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] <file> - push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb root - restarts adb with root permissions
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PDP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
--------------------------------------------------------------------------
Commands that you should know
adb push - Insert file to phone such as Stock.apk to /data/app_s
Code:
adb push <pathtofile.apk> <file system location> - Example: adb push c:\app.apk /data/app
adb pull - Remove file from phone such as Stock.apk from /data/app_s
Code:
adb pull <pathtofile.apk> - Example: adb pull /data/app_s/Stock.apk
adb install - Install app to phone
Code:
adb install <path to file> - Example: adb install c:/apps/apps2sd.apk
adb uninstall - Uninstall app from phone
Code:
adb uninstall <name of application> - Example: adb uninstall linda.apk
For more ADB Commands go - Here
--------------------------------------------------------------------------
Thats it for ADB! Congrats and if you have any questions please ask me or if anything is missing or not correct please tell me. I got all of this from research and personal experience.
Click to expand...
Click to collapse

XperiaX10iUser said:
Worked for me.
Click to expand...
Click to collapse
Okej I will try it out..

I can´t install Calculator.apk or the modified youtube.apk (High quality set as default) on my X10i????

for the calculator(is it a system apk) ? if yes then you have to push it to /system/app, if not try installing after signing it.
For youtube.apk i am sure it is a system apk and you need to push it to system/app

realunited123 said:
for the calculator(is it a system apk) ? if yes then you have to push it to /system/app, if not try installing after signing it.
For youtube.apk i am sure it is a system apk and you need to push it to system/app
Click to expand...
Click to collapse
I tried this method:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2/system
adb push YouTube.apk /sdcard/YouTube.apk
adb shell dd if=/sdcard/YouTube.apk of=/system/app/YouTube.apk
adb shell rm /sdcard/YouTube.apk
adb shell reboot
but still falied ?
I have obviously put youtube.apk into SDcard folder

dong2007 said:
I tried this method:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2/system
adb push YouTube.apk /sdcard/YouTube.apk
adb shell dd if=/sdcard/YouTube.apk of=/system/app/YouTube.apk
adb shell rm /sdcard/YouTube.apk
adb shell reboot
but still falied ?
I have obviously put youtube.apk into SDcard folder
Click to expand...
Click to collapse
looking at the screen shot you gave i am sure you haven't pushed it to sdcard .
it should be
Code:
adb push "the path where you have the apk" /sdcard/YouTube.apk
unless you have copied it to android-sdk folder.
And it seems it didn't mount the system to r/w .
Try these:
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb push "the path where you have the apk" /sdcard/YouTube.apk
adb shell dd if=/sdcard/YouTube.apk of=/system/app/YouTube.apk
adb reboot

realunited123 said:
looking at the screen shot you gave i am sure you haven't pushed it to sdcard .
it should be
Code:
adb push "the path where you have the apk" /sdcard/YouTube.apk
unless you have copied it to android-sdk folder.
And it seems it didn't mount the system to r/w .
Try these:
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb push "the path where you have the apk" /sdcard/YouTube.apk
adb shell dd if=/sdcard/YouTube.apk of=/system/app/YouTube.apk
adb reboot
Click to expand...
Click to collapse
now I get this message

Try This....
dong2007 said:
now I get this message
Click to expand...
Click to collapse
First step push the .apk file to your sdcard. then unmount your sdcard.
Then...
Code:
adb shell [B]{press enter}[/B]
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
note the space between the /mtdblock2 and /system...[you typed it without the space the first time]...
now check with the mount command...
Code:
# mount
there should be a few lines of output check for this one...
Code:
/dev/block/mtdblock2 /system yaffs2 rw 0 0
Note the "rw".... it indicates your fs is mounted now as read-write if it is "ro" [read only] then you made a mistake somewhere along the line...
if it is mounted succesfully as rw... then try this...
Code:
#dd if=/sdcard/YouTube.apk of=/system/app/YouTube.apk
then
Code:
#reboot
hope it helps...

dong2007 said:
now I get this message
Click to expand...
Click to collapse
well have you rooted your phone ? which method did you use ?

realunited123 said:
well have you rooted your phone ? which method did you use ?
Click to expand...
Click to collapse
I use Universal Androot (One Click Root), and my phone are rooted. I can use Marketacces, TB, root explorer and Quickbot...

dong2007 said:
I use Universal Androot (One Click Root), and my phone are rooted. I can use Marketacces, TB, root explorer and Quickbot...
Click to expand...
Click to collapse
OK. Maybe reboot you phone and try again ?

sam_a200 said:
First step push the .apk file to your sdcard. then unmount your sdcard.
Then...
Code:
adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
note the space between the /mtdblock2 and /system...[you typed it without the space the first time]...
now check with the mount command...
Code:
# mount
there should be a few lines of output check for this one...
Code:
/dev/block/mtdblock2 /system yaffs2 rw 0 0
Note the "rw".... it indicates your fs is mounted now as read-write if it is "ro" [read only] then you made a mistake somewhere along the line...
if it is mounted succesfully as rw... then try this...
Code:
#dd if=/sdcard/YouTube.apk of=/system/app/YouTube.apk
then
Code:
#reboot
hope it helps...
Click to expand...
Click to collapse
Still not working, i get this message.
Shall i mount or unmount my sdcard, when I start cmd??
I have the unmount...

realunited123 said:
OK. Maybe reboot you phone and try again ?
Click to expand...
Click to collapse
do it automatically via cmd when I use the formula which
(it is actually the only Ossetians it makes the mobile..)
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb push YouTube.apk /sdcard/YouTube.apk
adb shell dd if=/sdcard/YouTube.apk of=/system/app/YouTube.apk
adb shell rm /sdcard/YouTube.apk
adb shell reboot

dong2007 said:
Still not working, i get this message.
Shall i mount or unmount my sdcard, when I start cmd??
I have the unmount...
Click to expand...
Click to collapse
you don't need to mount the sdcard... Maybe try ADB magic ? search the forums for it.

dong2007 said:
Still not working, i get this message.
Shall i mount or unmount my sdcard, when I start cmd??
I have the unmount...
Click to expand...
Click to collapse
Please do read my post again...edited it with further explanations... after typing "adb shell" press enter you will get a new line with "$" symbol... now type "su"... and go on...

sam_a200 said:
Please do read my post again...edited it with further explanations... after typing "adb shell" press enter you will get a new line with "$" symbol... now type "su"... and go on...
Click to expand...
Click to collapse
Now i get message "permission denied" :S

Now can i install the modifed Youtube apk via astro :S
so something must be right
I´ve the modified youtube installed now on my X10i, and it starting with high quality now

[Q] Using a DROID X and MAC together is tough -- can someone help?

Too many threads... too many sites and PC options.
Here's my situation:
Droid X
Used the leak update... running 2.2 now.
Use a MAC. And have Terminal app on DX.
Have SBF file for 2.1 stock, have ZIP files of rooted 2.2's
Dont have custom recovery.
Dont care much about warranty or OTA... just want to be able to apply ZIPs.
I need to somehow either root my DX with Mac or Terminal app. Or flash the SBF to bring things back to 2.1.
Not sure what to do??? Please please help.
I am not familiar with terminal commands...so if you leave instructions that would be great.
-Roman

You follow the same ADB commands, more or less. Why not try something like Universal AndRoot though? Then you could just skip over it.
But, if you need to sbf, I would *think* you follow the Linux instructions.
1) download sbf_flash & sbf file
Code:
cd directory/where/these/are/located
./sbf_flash SBFfileLOCATION

The only way to SBF is to run windows through bootcamp or this http://www.droidforums.net/forum/droid-hacks/38671-flashing-sbf-mac.html . I am in the same boat as you luckily my girlfriend has a dell running Windows. You should also be able to root 2.2 using the Droid 2 method posted in this section http://forum.xda-developers.com/showthread.php?t=766767. I assume you have the SDK downloaded already? The Linux directions does not work for Mac.

x.v_ said:
You follow the same ADB commands, more or less. Why not try something like Universal AndRoot though? Then you could just skip over it.
I TRIED THAT, BUT THERE IS SOME ERROR THAT POPS UP... CAN'T DO IT. 2.2 ISN'T SUPPORTED... I THINK IT'S JUST FOR 2.1..
But, if you need to sbf, I would *think* you follow the Linux instructions.
1) download sbf_flash & sbf file
Code:
cd directory/where/these/are/located
./sbf_flash SBFfileLOCATION
Click to expand...
Click to collapse
SO THAT EASY? JUST TWO COMMAND LINES?
So, if I put the SBF on my desktop it would be:
cd desktop (enter)
./sbf_flash fullSBFfilename.sbf (enter)
???????

romanvail said:
SO THAT EASY? JUST TWO COMMAND LINES?
So, if I put the SBF on my desktop it would be:
cd desktop (enter)
./sbf_flash fullSBFfilename.sbf (enter)
???????
Click to expand...
Click to collapse
Running ADB with Mac OSX and therefore rooting with the mac is EASY. Just make sure you have the Android SDK installed on your Mac. Make sure in your .bash_profile you have the path set to the tools directory of your SDK folder.
Since I can't tell if you have all this down, I'll give you the instructions on setting up adb on the mac (using terminal), then give you the directions I followed on rooting my Droid X from OSX (I am running 2.2 leaked).
Essentially follow these instructions (taken from tjrocks91 on droidforum... I'd link, but I am not yet allowed to post outside links on this forum):
1. Download the Android SDK for Mac OSX. (google it)
2. Extract the zip file to any destination on your Mac. *Remember its path!*
In the AndroidSDK folder, there will be a folder named “tools”. We will be adding this folder to the path on Mac OSX. For this example, extract to your home folder (the folder that contains the desktop, documents, etc. folders)
3. To do this click on Finder > Go > Utilities > Terminal.
4. Type in without quotations “cd ~/”
5. Next, type "touch .bash_profile" to create your new bash or otherwise known path file.
6. Next, type "open -e .bash_profile" to open it in TextEdit. A TextEdit window will open, copy and past this into that window, substituting <username> for your username on OSX:
export PATH=${PATH}:/Users/<username>/AndroidSDK/tools
7. Save the file and close the window.
8. Repeat steps 5 through 7, but replace .bash_profile with ".bashrc" (without the quotes)
9. ADB should be ready to go. Make sure that your Droid X is set to "charge only" when connected via USB, and that you have debug mode set to on in your Android settings (settings>applications>development> USB Debugging)
10. In terminal, type (without the quotes): "adb devices". You should see a return that gives a list of devices attached. If the daemon wasn't started yet, this will do it. After that, type "adb shell" to enter adb.
11. After that, the adb commands are ALL the same on any platform, just make adjustments for different file systems when moving things TO your phone when using the command prompt (and not in the adb shell itself, but using adb commands). OSX follows unix/linux file structure, but not always the linux/unix file arrangement (but pretty darn close, since it is a Unix BSD GUI).
Now onto rooting your DX running 2.2. I've attached the file I used. It is a .rar files, so you will need a .rar extractor. I found a nice free one on the net called UnrarX. Google it, get it. Its free, it works. I will give instructions assuming you have them. These instructions come from karnovaran here on XDA. THey are for the droid 2, but work for the Droid X as well. i will translate them into instructions that can be followed verbatim on Mac (as the instructions he gave are meant for those doing this through the command prompt in windows).
1. Extract the contents of the attached file to your sdk tools folder
2. Open a terminal window and navigate to your sdk tools folder. if you put the sdk folder in your home folder, then the command and path you should enter from the terminal should be something like this:
cd AndroidSDK/tools
3. Now the process is as follows (follow EXACTLY, making sure you are faithful to YOUR file paths). I'm copying almost verbatim from karnovaran:
- adb devices (to verify the connection)
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push su /sdcard/su
- adb push busybox /sdcard/busybox
- adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
- adb shell
- cd data/local/tmp
- chmod 0755 rageagainstthecage-arm5.bin
- ./rageagainstthecage-arm5.bin
- let the process run until it 'kicks' you out (this WILL take a while, so don't TOUCH ANYTHING on your phone. Just go grab a beer and relax until the proces kicks you back out to the tools folder in terminal)
- adb kill-server
- cd <wherever-your-sdk-tools-folder-is>
- adb devices (to verify the connection)
- adb shell (you should now have a # prompt, if not return to ./rage step above)
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/bin/su
- cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
- chmod 4755 /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- exit
- exit
This got me root on my DX and I did this on OSX no problem. The only PC I have that is functional is my laptop for work and because of the content on it and security procedures, though I could do android hacking with it, I will not, so I'm stuck with using my Mac. Thing is that it really is NOT hard. Commands are almost exactly as in Linux/Unix, and OSX terminal runs bash, which is quite versatile (more commands than busybox, iirc) in and of itself. And getting mac root access is bloody easy using sudo if you need it (otherwise, don't use it).
I hope this helps. Have fun.

many steps.... but will go slowly.
Thank you!!!!

Many steps, but they work!

SirBrass said:
Running ADB with Mac OSX and therefore rooting with the mac is EASY. Just make sure you have the Android SDK installed on your Mac. Make sure in your .bash_profile you have the path set to the tools directory of your SDK folder.
Since I can't tell if you have all this down, I'll give you the instructions on setting up adb on the mac (using terminal), then give you the directions I followed on rooting my Droid X from OSX (I am running 2.2 leaked).
Essentially follow these instructions (taken from tjrocks91 on droidforum... I'd link, but I am not yet allowed to post outside links on this forum):
1. Download the Android SDK for Mac OSX. (google it)
2. Extract the zip file to any destination on your Mac. *Remember its path!*
In the AndroidSDK folder, there will be a folder named “tools”. We will be adding this folder to the path on Mac OSX. For this example, extract to your home folder (the folder that contains the desktop, documents, etc. folders)
3. To do this click on Finder > Go > Utilities > Terminal.
4. Type in without quotations “cd ~/”
5. Next, type "touch .bash_profile" to create your new bash or otherwise known path file.
6. Next, type "open -e .bash_profile" to open it in TextEdit. A TextEdit window will open, copy and past this into that window, substituting <username> for your username on OSX:
export PATH=${PATH}:/Users/<username>/AndroidSDK/tools
7. Save the file and close the window.
8. Repeat steps 5 through 7, but replace .bash_profile with ".bashrc" (without the quotes)
9. ADB should be ready to go. Make sure that your Droid X is set to "charge only" when connected via USB, and that you have debug mode set to on in your Android settings (settings>applications>development> USB Debugging)
10. In terminal, type (without the quotes): "adb devices". You should see a return that gives a list of devices attached. If the daemon wasn't started yet, this will do it. After that, type "adb shell" to enter adb.
Last login: Tue Sep 14 09:12:34 on console
Roman-Vails-Computer:~ romanvail$ cd ~/
Roman-Vails-Computer:~ romanvail$ touch .bash_profile
Roman-Vails-Computer:~ romanvail$ open -e .bash_profile
Roman-Vails-Computer:~ romanvail$ touch .bashrc
Roman-Vails-Computer:~ romanvail$ open -e .bashrc
Roman-Vails-Computer:~ romanvail$ adb devices
-bash: adb: command not found
Roman-Vails-Computer:~ romanvail$
*****DOESNT WORK FOR ME*****
Click to expand...
Click to collapse

Do you have the path to adb set properly?
Sent from my DROIDX using XDA App

SirBrass said:
Do you have the path to adb set properly?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Yeah this would be your problem.
@OP,
yes, it would be just that easy IF AND ONLY IF the linux commands apply to macs as well. Which I have NO IDEA on. so proceed at your own risk :z

i finally figured it out... saw another post....
here's what worked:
./
Here's my log in case anyone else needs is:
Roman-Vails-Computer:~ romanvail$ adb
-bash: adb: command not found
Roman-Vails-Computer:~ romanvail$ cd/Users/romanvail/android-sdk-mac_x86/tools -bash: cd/Users/romanvail/android-sdk-mac_x86/tools: No such file or directory
Roman-Vails-Computer:~ romanvail$ cd /Users/romanvail/android-sdk-mac_x86/tools Roman-Vails-Computer:tools romanvail$ ./adb
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number is specified.
Using this ocmmand with no additional arguments
will disconnect from all connected TCP/IP devices.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.
Roman-Vails-Computer:tools romanvail$ adb devices
-bash: adb: command not found
Roman-Vails-Computer:tools romanvail$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015D61C60A003017 device
Roman-Vails-Computer:tools romanvail$ ./adb push Superuser.apk /sdcard/Superuser.apk
1059 KB/s (27688 bytes in 0.025s)
Roman-Vails-Computer:tools romanvail$ ./adb push su /sdcard/su
1802 KB/s (26248 bytes in 0.014s)
Roman-Vails-Computer:tools romanvail$ ./adb push busybox /sdcard/busybox
1918 KB/s (1926944 bytes in 0.980s)
Roman-Vails-Computer:tools romanvail$ ./adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
726 KB/s (5392 bytes in 0.007s)
Roman-Vails-Computer:tools romanvail$ ./adb shell
$ cd data/local/tmp
$ chmod 0755 rageagainstthecage-arm5.bin
$ ./rageagainstthecage-arm5.bin
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3815, 3815}
[*] Searching for adb ...
[+] Found adb as PID 2846
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$ Roman-Vails-Computer:tools romanvail$ ./adb kill-server
Roman-Vails-Computer:tools romanvail$ ./adb kill-server
* server not running *
Roman-Vails-Computer:tools romanvail$ cd /Users/romanvail/android-sdk-mac_x86/tools
Roman-Vails-Computer:tools romanvail$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
XXXXXXXXXXXXXXXX device
Roman-Vails-Computer:tools romanvail$ ./adb shell
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
# cp /sdcard/su /system/bin/su
# cp /sdcard/busybox /system/bin/busybox
# chmod 4755 /system/bin/su
# chmod 4755 /system/bin/busybox
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
# exit
Roman-Vails-Computer:tools romanvail$ exit
logout
[Process completed]

Now that's odd. I only get problems when I try and use ./ just regular "adb" works on my machine.

SirBrass said:
Now that's odd. I only get problems when I try and use ./ just regular "adb" works on my machine.
Click to expand...
Click to collapse
Yea pretty weird... I use OSX 10.5.8
Intel machine... so, it's weird, but IT DID WORK.

romanvail said:
Yea pretty weird... I use OSX 10.5.8
Intel machine... so, it's weird, but IT DID WORK.
Click to expand...
Click to collapse
There's your problem.... you're using leopard . I'm using 10.6.3. Love it. They did well with this new OS version (for those who don't know... the difference to users between Leopard and Snow Leopard for OSX folks is like the diff between Eclair and FroYo... the former is good, but the later far exceeds it under the hood though still remaining almost the same on the front end).
And obviously that means I'm running an intel machine as well. 2008 iMac 20".... 2.66 Ghz Core 2 Duo. Just your regular, nothing-special iMac.

I thought Macs were supposed to be user friendly?
*snicker*
Sent from my DROIDX using XDA App

Will this method work for a Droid X on Android 2.3.4 Gingerbread and with build # 4.5.1_57_DX8-51 Also is there a new one click type solution by now on a Mac?

[Q] Help please, can't seem to reach Clockwork. Logs included, thanks!

Hi there. I got an Epic 4G not too long ago, and I've been attempting to root and install Clockwork to get some custom ROMs on it.
Installed Samsung drivers, phone connects fine. I'm not mounting the SD card, and I've tried it in Charge Only and USB Mass Storage modes.
I ran the sticky'd root method (2.2.6) from the Development subforum under the Epic 4G. Here is my log from that:
Code:
C:\Users\___>CD C:\Users\___\Desktop\Root
C:\Users\___\Desktop\root>adb devices
List of devices attached
D70024857e4d device
C:\Users\___\Desktop\root>run.bat
exploit and busybox made by joeykrim and one click installer made by noobnl and
firon
Press any key to continue . . .
copy and run the exploit (may take 2 minutes)
128 KB/s (5392 bytes in 0.041s)
3 KB/s (88 bytes in 0.026s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}
[*] Searching for adb ...
[+] Found adb as PID 2208
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
make it RW and move files
30 KB/s (687 bytes in 0.022s)
246 KB/s (26264 bytes in 0.104s)
355 KB/s (196521 bytes in 0.540s)
327 KB/s (14428 bytes in 0.043s)
9 KB/s (201 bytes in 0.020s)
413 KB/s (511436 bytes in 1.207s)
8 KB/s (203 bytes in 0.024s)
24 KB/s (479 bytes in 0.019s)
set permission
install busybox
push any key to reboot the phone
Press any key to continue . . .
Alright, so it rebooted. I can see SuperUser, and I can run apps that require root work perfectly (that screenshot one, etc).
So, I go to install Clockwork from the SDX forum (crossposted [link to noobnl's post spliced]). I ran "run-try-first.bat"
Code:
C:\Users\___>CD C:\Users\Media\Desktop\clockwork
C:\Users\___\Desktop\clockwork>adb devices
List of devices attached
D70024857e4d device
C:\Users\___\Desktop\clockwork>adb shell
$ su
su
# exit
exit
$ exit
exit
C:\Users\___\Desktop\clockwork>run-try-first.bat
one click installer and Clockworkmod Recovery v2.5.1.0 made by noobnl, skeeters
lint, and koush
Press any key to continue . . .
remove stock recovery patcher
mount: Operation not permitted
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
copy kernel and flasher
432 KB/s (313888 bytes in 0.708s)
462 KB/s (5820868 bytes in 12.299s)
flashing kernel
RedBend Update Agent 6,1,14,1
FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
open device file: Permission denied
bmldevice_get_size: bmldevice_open failed!src: /sdcard/zImage
dst: /dev/block/bml8 partition size: 0x0
part_size: 0x0
reboot: Operation not permitted
wait 60 second
cleanup
done
Press any key to continue . . .
C:\Users\___\Desktop\clockwork>
So, that seems like it didn't really work. I rebooted and went to recovery with ADB on the computer, with the volume + camera + power method, and got the stock recovery each time.
I went back in and installed ROM Manager, and flashed the newest build for the Epic, didn't work, stock recovery with the E: verification failed error.
I returned to my PC to try "run-try-last.bat"
Code:
C:\Users\___\Desktop\clockwork>run-try-last.bat
one click installer and Clockworkmod Recovery v2.5.1.0 made by noobnl, skeetersl
int, and koush
Press any key to continue . . .
copy and run the exploit (may take 2 minutes)
146 KB/s (5392 bytes in 0.036s)
4 KB/s (88 bytes in 0.020s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}
[*] Searching for adb ...
[+] Found adb as PID 2209
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
remove stock recovery patcher
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
copy kernel and flasher
459 KB/s (313888 bytes in 0.667s)
343 KB/s (5820868 bytes in 16.535s)
flashing kernel
RedBend Update Agent 6,1,14,1
FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
page_msize: 4096, phy_unit_size: 262144
src: /sdcard/zImage
dst: /dev/block/bml8 partition size: 0x780000
part_size: 0x780000
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 53700 bytes
read finished
wait 60 second
cleanup
done
Press any key to continue . . .
C:\Users\___\Desktop\clockwork>adb reboot recovery
Same thing, didn't work. I am currently guessing that the:
Code:
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
is the problem, since I can't seem to remove these files? I don't know.
Help is appreciated! Thanks much!
EDIT
Code:
C:\Users\Media>CD C:\Users\Media\Desktop\Root
C:\Users\Media\Desktop\root>adb shell mount -t rfs -o remount,rw /dev/block/stl9
/system
mount: Operation not permitted
C:\Users\Media\Desktop\root>adb shell
$ su
su
# mount -t rfs -o remount,rw /dev/block/stl9 /system
mount -t rfs -o remount,rw /dev/block/stl9 /system
# rm /system/etc/install-recovery.sh
rm /system/etc/install-recovery.sh
rm failed for /system/etc/install-recovery.sh, No such file or directory
# rm /system/recovery/recovery-from-boot.p
rm /system/recovery/recovery-from-boot.p
rm failed for /system/recovery/recovery-from-boot.p, No such file or directory
#
These files actually don't exist or something

I am having this exact same problem. When I try to use clockwork it goes to the stock android recovery mode and I receive the signature error.

are you rooted first?
nevermind sorry

I can finally answer w/ a why (in addition to an answer) - I think!
Before running the run last script open up an adb shell and type
Code:
su
remount rw
exit
exit
now run the script
I think this happens because the joeykim root leaves the system readonly?
Two other options if the above doesn't work:
1)Start fresh (reflash) from Odin and then install clockwork BEFORE rooting
2)Open up an adb shell and type the commands in the runlast script manually
hope that helps

jimmyz said:
I can finally answer w/ a why (in addition to an answer) - I think!
Before running the run last script open up an adb shell and type
Code:
su
remount rw
exit
exit
now run the script
I think this happens because the joeykim root leaves the system readonly?
Two other options if the above doesn't work:
1)Start fresh (reflash) from Odin and then install clockwork BEFORE rooting
2)Open up an adb shell and type the commands in the runlast script manually
hope that helps
Click to expand...
Click to collapse
I tried to do this and here is what I got. I may have messed up since I am new to this.
c:\samsung>adb shell
$ su
su
remount rw
remount rw
Permission denied
$ Remounting /system </dev/st19> in read/write mode
mount: Operation not permitted
$

Does anyone think it could be caused by the system update that has been rolling out? I downloaded that before I rooted.

I am having the same problem while trying to get Clockwork to work correctly on my Epic.
I also think that the problem is related to the install-recovery.sh and recovery-from-boot.p files. If I run a batch file (run.bat or run-try-first.bat or run-try-last.bat) the first problem is always when it tries to remove these files.
First I tried to just remove the install-recover.sh file
>adb shell rm /system/etc/install-recovery.sh
rm failed for /system/etc/install-recovery.sh, Read-only file system
The system reported that the file system was read-only.
Next I changed the file system to be writable.
>adb shell
$ su
su
# remount rw
remount rw
Remounting /system (/dev/stl9) in read/write mode
# exit
exit
$ exit
exit
This seemed to work ok and no errors were reported
Last I tried to delete the file again.
>adb shell rm /system/etc/install-recovery.sh
rm failed for /system/etc/install-recovery.sh, No such file or directory
This time the system reported that the file (or directory) was not found.
All of the updates have been applied to this phone.
I'm just getting into the Android world so I'm pretty lost right now. I am able to get into the clockwork recovery if I hold the volume-down, camera button and the power button down until the phone is fully turned on. I am not able to update the phone's rom and this problem seems to be tied back to that the phone is not "really" rooted (this is pretty much just a guess...)
Thank you in advance for any help or suggestions you may offer!
Scott

Hi there.
I've redone the entire phone a few times now with Odin. Each time I try a new method of root/flashing clockwork. I've tried in every combination:
-Using Noobl's stuff, including 2.2.7, 2.2.6, and I guess 2.2.5 or whatever he published before that
-Using Koush's clockwork and noobl's clockwork things, both -first and -last
-Pulling the battery during the clockwork reboot and using the camera + volume + power
-Using ADB rebooting and quick rebooting
-Remounting the system RW between root and clockwork, before both, etc
Nothing has worked, tried with no updates applied and with all 3, and with the first one. I guess this android stuff just isn't my cup of tea after all. Time to wait for WP7, I suppose (can't stand this 5 hour battery crap, was hoping to fix it). Tried it on 3 computers, done it every conceivable way.
Thanks to the modding community, rooting community, and everybody who writes the guides. I guess I'm just unlucky or something.
EDIT: Disregard that, randomly worked after pulling the battery during the reboot following Noobl's clockwork install...... well then

If you want to try one last time I would try to manually root etc by entering one line at a time via adb
Sent from my SPH-D700 using XDA App

Installed The Boss Mod V.3
JuiceDefender, Superuser, ROM Manager
I can still only reach Clockwork via the Power + Volume + Camera, not through adb reboot or the clockwork menu...

juchmis said:
Installed The Boss Mod V.3
JuiceDefender, Superuser, ROM Manager
I can still only reach Clockwork via the Power + Volume + Camera, not through adb reboot or the clockwork menu...
Click to expand...
Click to collapse
This is expected behavior if you just used noobnl one click- it installs to bml8. IF you want to reach clockwork through Rom Manager you need to have a modified kernel (on bml7) which many of the custom Roms have built in. After you you do that adb reboot will work but only if you keep the appropriate clockworkwod mod update.zip in the root of your sdcard and select it through the "stock" recovery- this is "fakeflash"

Stuck in KF boot screen - details

Received my KF about a week ago. Just tried to root it yesterday. That was successful. The instructions I was using said this: "This will “root” your Kindle Fire. You can actually stop here but I recommend you to go to the next steps to install TWRP Recovery, which will allow you to install/backup/restore ROMs and also “unroot” your Kindle Fire when needed easily." So, silly me, without doing further research, went on to the next steps. I almost immediately got stuck, here is the code, ending with the -bash where I was stuck.
Zach:~ Zbhest$
Zach:~ Zbhest$ cd Downloads/KindleFireRootMacLinux
Zach:KindleFireRootMacLinux Zbhest$ mkdir ~/.android
mkdir: /Users/Zbhest/.android: File exists
Zach:KindleFireRootMacLinux Zbhest$ cp adb_usb.ini ~/.android/.
Zach:KindleFireRootMacLinux Zbhest$ cp adb_usb.ini ~/.android/
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac kill-server
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac devices* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
08EC002600000001 device
Zach:KindleFireRootMacLinux Zbhest$ sh runmemac.sh
---------------------------------------------------------------
Easy rooting toolkit (v2.0)
created by DooMLoRD
Modified for Kindle Fire for Linux/Mac by Max Lee at RootKindleFire.com
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (10 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
[*] Before u begin:
(1) enable USB DEBUGGING
from (Menu\Settings\Applications\Development)
(2) enable UNKNOWN SOURCES
from (Menu\Settings\Applications)
(3) [OPTIONAL] increase screen timeout to 10 minutes
(4) connect USB cable to PHONE and then connect 2 computer
---------------------------------------------------------------
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
1836 KB/s (23056 bytes in 0.012s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00015118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x000151e0
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x40119cd4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd195bb 0xafd39357
[*] Popping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle USB DEBUGGING (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
4634 KB/s (1075144 bytes in 0.226s)
--- correcting permissions
--- remounting /system
--- copying busybox to /system/xbin/
2099+1 records in
2099+1 records out
1075144 bytes transferred in 0.038 secs (28293263 bytes/sec)
--- correcting ownership
--- correcting permissions
--- installing busybox
--- pushing SU binary
1508 KB/s (22228 bytes in 0.014s)
--- correcting ownership
--- correcting permissions
--- correcting symlinks
--- pushing Superuser app
5116 KB/s (785801 bytes in 0.149s)
--- cleaning
--- rebooting
--- WAITING FOR DEVICE
5382 KB/s (3104805 bytes in 0.563s)
Error: Could not access the Package Manager. Is the system running?
All Done, Kindle Fire ROOTED!!!
Check out RootKindleFire.com for more cool hacks!
Zach:KindleFireRootMacLinux Zbhest$
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac root
restarting adbd as root
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac remountremount succeeded
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac push su /system/xbin/su
260 KB/s (22228 bytes in 0.083s)
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell chmod -6755 /system/sbin/su
Bad mode
Zach:KindleFireRootMacLinux Zbhest$ .adb./adb-mac shell chown 0.0 /system/xbin/su
-bash: .adb./adb-mac: No such file or directory
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell chown 0.0 /system/xbin/su
Zach:KindleFireRootMacLinux Zbhest$ cd Desktop/kindleFireRootNew
-bash: cd: Desktop/kindleFireRootNew: No such file or directory
Zach:KindleFireRootMacLinux Zbhest$ cd desktop/kindlefirerootnew
-bash: cd: desktop/kindlefirerootnew: No such file or directory
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac push su /system/xbin/su
877 KB/s (22228 bytes in 0.024s)
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac root
adbd is already running as root
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac remountremount succeeded
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac push su /system/xboin/su
264 KB/s (22228 bytes in 0.081s)
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell cown 0.0 /system/xbin/su
cown: not found
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell chown 0.0 /system/xbin/su
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell chmod 06755 /system/xbin/su
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac install Superuser.apk
3818 KB/s (785801 bytes in 0.200s)
pkg: /data/local/tmp/Superuser.apk
Success
Zach:KindleFireRootMacLinux Zbhest$ ./adb-mac shell
# su
# idme bootmode 4002
<idme> write 4002 to offset 0x1000
# reboot
Zach:KindleFireRootMacLinux Zbhest$ ./fastboot-mac -i 0x1949 boot twrp-blaze-2.0.0RC0.img
-bash: ./fastboot-mac: No such file or directory
And now my Mac does not recognize my KF. When I unplug my KF it appears bricked (will not turn on), but when it is plugged into a wall outlet I can do the hard reset, it charges, but does not go past the KF boot screen.
Also, ADB does not recognize any devices.
Additionally, I have a windows 7 machine. I was going to attempt to pick up where I left off, but as my KF is listed as an "unknown device," I cannot update drivers (or do not know how to do so manually). I also installed this little number: http://forum.xda-developers.com/showthread.php?t=1430038
And I currently have linux loaded on my W7 machine. When I try to use the "normal_boot" command, which is advised, I get:
"Resetting bootmode to standard boot...
< waiting for device >
"
So, yeah. That is where I am at. I WOULD go on to the other directions in firekit, but would prefer not to completely void the warranty using the "usb boot mode trick".
If windows 7 is the key here, I may need a walk through for driver installation and such. Otherwise, I am not totally disinclined to call customer service and ask for a replacement. Apparently they have been good about replacing rooted kindles?

Same issue right now... already tried reinstalling windows/firekit liveusb but nothing works=\ Is there any news on this problem?

http://support.microsoft.com/kb/315539/en-us
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54

I did read all those threads about such problem before. Just no matter what i do those drivers won't install. I only get unknown device on 7/xp and cannot change it coz when i manually select those drives windows says that there no device info in it=\ Thanks for help anyways

did you select adb_usb.ini ? it's just the folder with this file in it. selecting just the folder is usually enough. if you want to select the file: the driver file is android_winusb.inf. there is the harware info
if you have xp available then use this machine - it's easier

Yeah i did select that inf file (it was only one selectable in folder anyway) but it still says same stuff. I have xp right now if that gonna change something

yes xp is easier to handle because:
only 32bit -> only 1 driver version
no user access control -> don't need to do every thing as administrator
please check the following:
you have a .android folder under your user directory - in this folder is adb_usb.ini - the file has entries for device 0x1949 and 0x18D1 - if not run install.bat from the driver set i provided
check your device manager and delete every entry with kindle or adb
unplug and replug your kf - select the driver i provided manually

Got those 0x1949 and 0x18D1 in adb_usb file. And i only have unknown device every time i plug kindle in, no adb kindle at all

right click unknown device - update driver - select android_winusb.inf
if this don't work we have to cleanup old drivers -> could help per teamviewer if you like

When i try to update driver and manually use inf you provided it says that there no device info there=\ And i got unknown device since fresh windows install so idk what driver can cause it -.- I could ve try teamviewer but my windows is not english so it gonna be quite useless.

what language ?

Well it's in russian +there no laptop drivers yet coz im using xp only for this god dam kindle

ok your right - with russian i have a problem
will try to describe you the steps:
disconnect and power off (pwr ~30sec) your KF
open a command prompt
type "set devmgr_show_nonpresent_devices=1"
type "start devmgmt.msc"
Click Show hidden devices on the View menu in Device Manager
uninstall every entry with kindle, android phone or adb device
power down computer and power on again (no restart)
tell me if your done - we will resume ...

ok i did everything step by step tho there was none of adb/android phone/kindle so i just deleted my unknown device.

ok - lets resume:
you may want to delete your old driver set previously downloaded - it must be faulty
now download the one from this post and extract it to c:\
now plugin your kf (don't power it on - will do it by itself)
if you' asked
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver i attached
-Select okay and okay
just in case you'r not asked:
-Go to device manager
-right click on the exclamation mark kindle
-Choose update driver software
-choose browse my computer for driver software
-choose let me pick from a list of devices on my computer
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver i attached
-Select okay and okay
if this don't work eighter then i would think you have a faulty cable !
try an other one ...

Nope still same=\ Guess i will look for new cable tomorrow then tho this one was just fine today at transfering stuff (dam you nokia!). Well thanks for trying to help anyway.

you have the nokia cable - i have the same one
tell me the status your kf now
stuck at boot screen ?
some other tricks:
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
if you'r stuck in wrong bootmode:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
if you issue the fastboot commands and get <waiting for device> over some while power the kf off (pwr ~30sec) and on. at some point it should recognize the command

Yeah it same as before=\ I have same problem as topic starter aka device in fastboot and windows won't recognize it and install correct drivers. Fastboot commands won't work coz i don't have correct drivers and all they do is stuck on waiting for device/
xx time later = IT WORKS!!! for some weird reason it picked kindle up nothing changed in windows yet it works! Thanks again for your help time to flash recovery again.

courious - just tested on mine
when i switch to fastboot it is recognised as "android adb interface"
not the composite thing !
and i have the same drivers on xp
perhaps you want to try this one:
http://forum.xda-developers.com/showthread.php?t=1428428
sorry - no more ideas ...
UPDATE: hurraaa !!! - wish you all the best and good luck !!!

[Gen8v2, A70B/A70IT2 Froyo] HOWTO: Enable SDE menus without Archos SDE firmware

Hi All,
As some may know, current Official SDE for gen8 doesn't work on the new Froyo Gen8 v2 devices (currently: A70b / A70it2).
As we do on Gen9, there is a way to enable SDE menu in recovery for the new Archos A70S/A70it2. It's quite easy and safe, it has been used multiple times on gen9 and only use Archos commands (except of course temp root that is done by using psneuter).
Disclaimer: I'm not responsible if you blow your device with this, I'm only using existing Archos commands but this is not an official Archos release. Use at your own risks.
If you don't know about SDE, check my Gen9 thread here, it has some pictures that could help (70it2 menus are not exactly the same but are similar).
So, to enable it:
1) You must have adb working, I won't detail how to install or use it here. "adb shell" should give you a '$' prompt, if it doesn't, check your adb installation first.
2) Unzip content of the attached file to a directory (or platform-tools if adb is not in your PATH)
3) Launch enable_sde.bat script (or enable_sde.sh for linux, don't forget to chmod 755 it)
4) It should display something like this:
Code:
5800 KB/s (557962 bytes in 0.093s)
4625 KB/s (2564188 bytes in 0.541s)
5000 KB/s (728825 bytes in 0.142s)
property service neutered.
killing adbd. (should restart in a second or two)
Generating KD...
Updating KD (3293269 bytes)...
0
100
4) If it worked properly (check file sizes, some had troubles with adb push), reboot in recovery with power+vol+, you should now see the SDE boot menu. If you go to recovery, you should see the and if you go to recovery, you should see the "Developer Edition Menu". If it doesn't work for you, please report in this thread.
Next step is to install a rooted build, you can find one here.
Cheers,
LeTama

Flawless victory...excellent.

Hello!
i get the following error:
Code:
D:\test>enable_sde.bat
D:\test>adb push psneuter /tmp
failed to copy 'psneuter' to '/tmp/psneuter': Permission denied
D:\test>adb push init_zImage /tmp
failed to copy 'init_zImage' to '/tmp/init_zImage': Permission denied
D:\test>adb push init-cpio.gz /tmp
failed to copy 'init-cpio.gz' to '/tmp/init-cpio.gz': Permission denied
D:\test>adb shell chmod 755 /tmp/psneuter
chmod: /tmp/psneuter: No such file or directory
D:\test>adb shell /tmp/psneuter
/bin/sh: /tmp/psneuter: not found
D:\test>ping 127.0.0.1 -n 5 -w 1000 1>nul
D:\test>adb shell /usr/bin/kd_flasher -i /tmp/init-cpio.gz -k /tmp/init_zImage
Generating KD...
cannot open kernel file: No such file or directory
mkflashimage failed
D:\test>adb shell sync
D:\test>
it is an archos A70it2.

Honeycomb or Froyo model ?
This one is for Froyo, I changed title to reflect it, sorry. Check my sig for the Honeycomb one...

Ok, it is the honeycomb model I will try the other one - thx!