Originally Posted by peablo.lingon

when I try do adb shell I see device not found

Do you have adb installed on your computer?

If you don't I would suggest you download jays easy modder tool
It has what u need for ad to work... you can find the tool link on the wiki

Sent from my SPH-D710 using xda premium

after I did step by step easy modder tool I run MiniADB to do adb shell and this is what I see:

C:\Users\Stanley Junior\Desktop\MiniADB>cmd.exe
Microsoft Windows [Wersja 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Wszelkie prawa zastrzeżone.

C:\Users\Stanley Junior\Desktop\MiniADB>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found

C:\Users\Stanley Junior\Desktop\MiniADB>adb push CWMR5x_F100_recoveryB.img/data/
local/
Android Debug Bridge version 1.0.26

-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. Overrides ANDROID_SERI
AL
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 devic
es.

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 i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal 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 specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader 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 th
e 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 u
pdated.

- 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 prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.

C:\Users\Stanley Junior\Desktop\MiniADB>adb shell
error: device not found

C:\Users\Stanley Junior\Desktop\MiniADB>adb reboot recovery
error: device not found

C:\Users\Stanley Junior\Desktop\MiniADB>

Originally Posted by CEnnis91

Well that didn't take me very long, if you updated to 4.55.97, great, but the latest available is now 5.6.0! And the stock 5.6.0 has a high chance of again working with Motocast (you can thank embeem for that) =)

http://forum.xda-developers.com/show....php?t=1534073

ClearD, cennis91, Utkanos- Great Work Guys! made a small donation to all 3 of you
Keep up the great work!

ok, everyone try to help me - THANK YOU VERY MUCH !! but what is wrong becasue You send me link and anoteher and another... I did step by step from this site http://motoactv.wikispaces.com/ I flashed my motoactv, did backup and rooted. What next why my PC doesn`t see motoactv and how install android on motoactv. I downloaded motoactv easy modder and did every 6 steps. Still nothing what is wrong ?? please help

Originally Posted by peablo.lingon

after I did step by step easy modder tool I run MiniADB to do adb shell and this is what I see:

C:\Users\Stanley Junior\Desktop\MiniADB>cmd.exe
Microsoft Windows [Wersja 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Wszelkie prawa zastrzeżone.

C:\Users\Stanley Junior\Desktop\MiniADB>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found

C:\Users\Stanley Junior\Desktop\MiniADB>adb push CWMR5x_F100_recoveryB.img/data/
local/
[...]

C:\Users\Stanley Junior\Desktop\MiniADB>adb shell
error: device not found

C:\Users\Stanley Junior\Desktop\MiniADB>adb reboot recovery
error: device not found

C:\Users\Stanley Junior\Desktop\MiniADB>

Alright, restart the device, and restart the computer, then try miniadb again. You're in normal boot mode on the device, right? Not fastboot? ADB will not work in fastboot.

Also, why are you manually trying to flash the recovery? If you rooted, it's already there.

When you flashed the boot image in fastboot, what did it say? Did it show success?

On a side note, me and CEnnis91 and utkanos have been working on a 5.6.0 rom tonight. I'm having issues with a secondary launcher though, as it's refusing to boot after I place the launcher in the Rom. I might need to create a workaround for it tomorrow...

as I said flash comleted and boot completed. I hold power and start buttons for 3 sec. how put device in normal boot mode ?

how open clockworkmmod ??

after i did root:

-Looking for device... Make sure the device is turned on and booted normally.
-The script will not continue if your MotoACTV is not connected.
-Root will only be successful after the modified boot.img has been flashed.
-Remounting system partion read/write...
remount failed: Operation not permitted
-Pushing su...
failed to copy 'su' to '/system/bin/su': Read-only file system
failed to copy 'su' to '/system/xbin/su': Read-only file system
-Granting permissions to su...
Unable to chmod /system/bin/su: Read-only file system
Unable to chmod /system/xbin/su: Read-only file system
-Installing Superuser...
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
-Pushing busybox and granting permissions...
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: Read-only file system
-Installing busybox...
-Installing Clockworkmod Recovery
1261 KB/s (3596288 bytes in 2.784s)
/dev/block/mmcblk1p13: cannot open for write: Permission denied
-We're now rooted with Superuser, Busybox, and Clockworkmod Recovery installed.
Rebooting now.
Aby kontynuować, naciśnij dowolny klawisz . . .


and I don`t know what next ?

For normal boot, you just turn the device on with the power button. :P I will be able to help more tomorrow, bedtime for tonight. 5 am lol.

Sent from my HTC Inspire 4G using XDA-funded carrier pigeons

Originally Posted by rapjr7

They haven't released all the source, they still have some proprietary source code that runs on the MSP430 coprocessor. The MSP430 reads some of the sensors and computes calories and such when the OMAP processor is sleeping. This is why the accelerometer doesn't work for changing the screen orientation, the accelerometer data is not available as raw readings, it is processed by the MSP430 into calories and MET's. If you look in the system log you'll see messages there showing the parameters the MSP430 is computing.

There may be a way to get raw accelerometer readings out of the MSP430, there are two MSP430 firmware images in the filesystem, one is the normal firmware and one is 'factory'. The factory firmware may allow testing of the sensors in which case it may be possible to get the accelerometer data into a standard Android device file format. The driver for the msp430 is in a file named msp430.c in the kernel code, and it includes the ability to reflash the MSP430 using ioctl's. I haven't tried it since there's a good chance the whole system will stop working if it's done wrong. However, it could be that this is where the serial number is also stored, on the MSP430, perhaps in EEPROM. Since Motorola can keep this code proprietary it would be a logical place to hide things.

I've been working on using the MOTOACTV to build a medical sensor gateway to securely forward data from body worn sensors, kind of a mini-sensor hub. Part of some research work I'm involved with at a college. So I've been looking at how the MOTOACTV built-in sensors work.

Well then, if you end up finding a way to either forward the data or convert it, let us know I've been working on getting other utility programs running such as a compass app.
The problem with this is two fold, the motoactv has no magnetic sensor so the magnetic north won't work and while direction and bearing work with maps(gps data only) , the raw data isn't processed in the compass apps therefore the compass doesn't rotate"also part of that proprietary software of the accelerometer "

Sent from my Nexus S 4G using XDA

Originally Posted by peablo.lingon

as I said flash comleted and boot completed. I hold power and start buttons for 3 sec. how put device in normal boot mode ?

how open clockworkmmod ??

peablo.lingon:

Polski nie jest moim ojczystym językiem, przetłumaczył to dla mnie mój znajomy. Aby naprawić Twoje urządzenie, potrzebujesz pliku wykonywalnego (binarki) fastboot oraz połączenia urządzenia z Twoim komputerem. Następnie, mając wyłączone urządzenie, włącz je, a podczas włączania przytrzymaj przycisk służący do obniżania głośności. Na górze powinien być widoczny napis "fastboot bootloader mode". W tym momencie musisz wykonać następującą komendę :

$> fastboot flash boot boot.img

gdzie boot.img to zhakowane jądro, które możesz znaleźć w wielu miejscach w tym wątku. Po pomyślnym zakończeniu komendy, uruchom :

$> fastboot reboot

Co uruchomi urządzenie ponownie i załaduje Twój normalny ROM. W tym momencie potrzebny będzie mój obraz naprawczy na Twoim urządzeniu :

$> adb push filename.img /data/local/

Następnie otwórz sesję adb, powinieneś zobaczyć znak '#' oznaczający uprawnienia administratora (root). W tym shellu uruchom następującą komendę :

dd if=/data/local/filename.img of=/dev/block/mmcblk1p13

Która poskutkuje zapisaniem obrazu naprawczego do urządzenia. Następnie wyjdź z powłoki adb i uruchom komendę :

$> adb reboot recovery

Urządzenie powinno się teraz znaleźć w trybie naprawczym, z którego możesz zapisywać do pamięci flash jakiekolwiek pliki, jakie tylko chcesz.

Thank you a lot one more question my pc dosen't see motoactv as storage and I can't add mp3. I really wanna install android because i need app from android market to running

Sent from my MB525 using XDA