yashsingh1/xdaforums huggingface dataset:
[Other SmartWatches] ClearD:
Vmware should be fine, I use it sometimes for Linux stuff.
[Other SmartWatches] bdaman80:
I'm a big fan of virtualbox, but it seems very buggy on usb passthrough

Sent from my DeathStar disabled device
[Other SmartWatches] tansoftware:
Solution Found...

You are correct... The update binary you are using is corrupt or does not function correctly with the device.

My findings so far after intensive testing:

1st issue, the format command in your updater-script is utilizing 4 args. Your update binary is only capable of seeing 3 args. As a result, the format command fails, the system partition remains, and is basically overwritten by the new system folder in your zip. Surprisingly no error is generated and the script continues to run as a result of the faulty update binary used.

2nd issue, you are mounting system as ext3, MTD which is wrong. Your correct filesystem/device address is ext3, MMC. Don't use MTD for the system partition. Instead use MMC.

3rd issue, you are not clearing the data, cache, and dalvik partitions.

I have been testing with update binaries and have found a suitable one which works.

I have also found a workaround to erase system instead of formating it which works 100% every time. The same workaround can be used to clear cache, data, and dalvik :-)

Code below:

ui_print("");

ui_print("Test - Utility - Format");

ui_print("Mounting");

mount("ext3", "MMC", "/dev/block/mmcblk1p18", "/system");

ui_print("Formatting /system...");

delete_recursive("/system");

ui_print("Unmounting");

unmount("/system");

ui_print("");

ui_print("...Finished.");

ui_print("");

For your reference, I have attached a working zip sample.

WARNING !!! THE FILE ATTACHED WILL WIPE YOUR SYSTEM PARTITION. IT IS INTENDED FOR TESTING PURPOSES AS AN ALTERNATIVE TO THE FORMAT COMMAND IN UPDATER-SCRIPT !!!

YOU HAVE BEEN WARNED !!! USE AT YOUR OWN RISK !!!
[Other SmartWatches] ClearD:
Any idea of the syntax to flash the boot.img properly? I keep getting status 7 error (assert failed) with the binary from the official OTA update (the one that includes the boot.img).
[Other SmartWatches] bdaman80:
I need a brave soul or two. any takers?
[Other SmartWatches] simx:
I'm ready :)

NA
[Other SmartWatches] bdaman80:
For some reason I can't post link from my phone.

Hit me up on gtalk bdaman80 at gmail

Sent from my DeathStar disabled device
[Other SmartWatches] tansoftware:
Serial Number Found !!!

Wow have I ripped my watch apart :-D

It seems Big M has done a good job hiding the device ID number necessary for future updates/upgrades.

A simple "adb get-serialno" will return the board's (OMAP) serial number. This is useless and probably used for debugging purposes only. Big M does not use this serial number as it has no control over OMAP SOCs productions.

But what Big M does not want you to know, is that they have hidden their own traceable serial number in a hidden partition... The PDS partition.

Yep that's right folks... our traceable serial numbers are hidden in the PDS partition.

To access that partition you will need to dump the PDS partition:

adb shell dd if=/dev/block/mmcblk1p6 of=/sdcard/pds.img bs=1024

Then you will need to pull the dumped img to your pc:

adb pull /sdcard/pds.img

Once you have the pds.img file on your PC, use "Explor2fs" to open the IMG file. This will show you the full the directory structure within pds.img.

On your left, browse to the "device_id" folder, and you should see a "id_file" on your right.

Right click "id_file" and select the "export file" option to export the file to your PC.

Attached is a screenshot for reference.

Use the notepad to view the exported file and see your unique device ID no.

The "id_file" contains your valuable device ID used for verification during firmware upgrades and OTA updates. Interestingly, init.rc calls the PDS partition for serial no verification during the boot initialization process.

It is possible to corrupt your PDS partition rendering your watch un-upgradeable. Be careful when tampering around.
[Other SmartWatches] kevina90:
Wait, so when we rooted our motoactvs, we flashed over the PDS partition? In that case, we should backup the id_file from our stock watch and then we should be able to update from there on out right?
[Other SmartWatches] tansoftware:
I cannot confirm that. I do not believe our update methods tamper with the PDS partition. Further testing needs to be carried out to confirm failure of upgrades.
[Other SmartWatches] ClearD:
It doesn't tan. We only flash the boot.img, that's all. Then copy over the root binaries, superuser, recovery, and supporting files.

That partition is not touched.

My guess is it's a mismatched build.prop; as there is one in the boot image as well as one in /system. We need to match those before it will let us update, but I'm not sure how to pull the one from a boot.img, otherwise I'd just match it in the "return to stock" button of the root tool and everyone would be able to update. The ones there now are from 2 different devices, so the serials and such don't match. Little help? ;)
[Other SmartWatches] bdaman80:
Test kernel seems fine, but I need some testers on same as me, and different versions than both of mine. I'm on 4.55.78

Sent from my DeathStar disabled device
[Other SmartWatches] tansoftware:
I do not believe so... I cannot find any reference to another Device ID number in Boot img. Just checked and can confirm that boot only requests it from the PDS partition. I do not believe that Big M injects your ID inside your update before pushing it to you. Honestly, that would sound suicidal for Big M's engineers :-P

The Build prop is programmed to be overwritten at every boot regardless of what you put in your system folder. I have even been able to isolate the code and stop it from doing so on reboot :-)
[Other SmartWatches] Prack:
woot I see 1000 mhz in that setcpu screen :D
[Other SmartWatches] bdaman80:
Yes you do :)

Sent from my DeathStar disabled device
[Other SmartWatches] Sideburns4life:
I dunno if this helps anyone. However my friend just got an 8gb active and he's running the 4.55.97 update. He then decided to root using the root tool and replaced the boot.img file and then used the root step. He has all the features of the latest version (ie percent on battery). And he is able to install zeam launcher and custom apps and whatnot.
[Other SmartWatches] ClearD:
Can he run

adb pull /system system

then zip the system folder that's created and send it to me?

I can build from that, hopefully.

Next rom update will use bda's latest kernel, pending stability. :)
[Other SmartWatches] Sideburns4life:
I'll see what I can get from him and get back to you.
[Other SmartWatches] tansoftware:
Finally got boot to flash from updater script !!!

I have to say... This was one hell of a b**ch !!! The reason boot flashing has been failing is because of the faulty recovery we have, hence the Beta status of our recovery.

For this to work, you will need busybox installed on your system folder.

Meaning... Make sure busybox libraries are present in /system/xbin.

If you are flashing a new ROM, run package_extract_dir first to dump system first.

Then place the following code at the very end of the updater script to flash boot.img :

ui_print("");

ui_print("Test - Boot - Flasher");

ui_print("Mounting System");

mount("ext3", "MMC", "/dev/block/mmcblk1p18", "/system");

ui_print("");

ui_print("Stage 1... Extracting");

package_extract_dir("bootimg", "/tmp");

ui_print("Stage 2... Setting Perms");

set_perm(0, 0, 0777, "/tmp/boot.img");

ui_print("Stage 3... Flashing Boot");

run_program("/system/xbin/busybox", "dd", "if=/tmp/boot.img", "of=/dev/block/mmcblk1p12", "bs=1024");

ui_print("Unmounting System");

unmount("/system");

ui_print("");

ui_print("Flash Successful");

ui_print("");

Note:

- No need to mount system again if you've done that in the beginning of the script.

- I've placed boot.img in a separate folder named bootimg within the zip file.

- Remember to set /tmp/boot.img permissions to give busybox access to boot.img

I have tested this and can confirm that it is working 100%.

Enjoy :-)
[Other SmartWatches] CEnnis91:
The 4.55.97 files are up for real this time (no one really needs 4.55.78 at this point), sorry for the delay, thanks for all the help, and enjoy. =)

*crosses fingers*
[Other SmartWatches] ClearD:
(double post; remember to thank CEnnis91 and utkanos for their hard work!)
[Other SmartWatches] simx:
successful update .97

Successfully updated to ROOTED .97 now

Thanks CEnnis91

NA
[Other SmartWatches] CEnnis91:
5.6.0!

Sorry guys for another update; hopefully you can forgive me. 5.6.0 stock and rooted are now available (I said it would be easy once we got all the kinks out). There also might be some more good news: because I obtained a completely stock system.img (thanks embeem), it's possible that updating will again be possible via motocast if you flash the stock-5.6.0-update.zip. We won't know for sure until the next update however.
[Other SmartWatches] seaer:
HOW?

How 'd you do it? Overclocking1000MHZ？

---------- Post added at 02:42 AM ---------- Previous post was at 02:24 AM ----------

Look forward to update for a long time, Alway staying at the4.55.78:(
[Other SmartWatches] ClearD:
I got this one.

OMAP3 Processor, same one used in the Droid 2; Droid 2 has it running at 1 Ghz, so why shouldn't we? They toned ours down for the watch, presumably to save battery power. ;)
[Other SmartWatches] speedyink:
The day has come! Using 5.6.0 beautifully here, rooted, and working well! A donation is on the way CEnnis
[Other SmartWatches] Prack:
Does the motoactv app on your phone still work with the device?

Also do we have a custom kernel yet that allows us to go to 1000mhz or will setcpu already allow it?
[Other SmartWatches] CEnnis91:
These are only stock images for right now, the custom kernel is still considered in alpha state right now iirc. Without the actual device, I don't want to be fooling around with custom bits and whatnot. Once I have the device however, I will release a custom ROM with some of my own ideas in mind. I can guarantee it will not be themed, and it will always be the latest source available, with the option for an overclock kernel should it be stable enough for my liking. I should be getting the device around the end of the month or so, so enjoy the stock images. -- That's all I'll release for now. =)
[Other SmartWatches] Prack:
Sounds great. Thank you for all the hard work. What are you going to name the ROM? I'm not worried about themes or extra features so much. The OC kernel would be nice but I still think you should name it :)
[Other SmartWatches] CEnnis91:
I had the name picked out around a month ago, but I'm not going to reveal that either, yet ;)
[Other SmartWatches] Prack:
Quick post it before another motoactv dev claims it! :p
[Other SmartWatches] simx:
5.6.0 problems

I installed rooted 5.6.0, the flick to activate display function stops working after about 3 or 4 hours, I have to reboot for it to work again, any ideas?

NA
[Other SmartWatches] sike009:
5.6.0 works!

the rooted 5.6.0 rom works very well! Thanks!

New input form,new workouts,and more watch look,connect wifi without USB, it's really good!

But the musics in it are gone,I don't know why.
[Other SmartWatches] speedyink:
I never used it before updating, but I do get text messages pushed to it now that i've set it up. I don't get calls though..
[Other SmartWatches] pmcnano:
Erm, I updated with the rooted 5.6.0 zip and...it worked perfectly...6 hours later the device died, it wont turn on again, really weird, I had battery and everything, it just died. I cant boot it at all now.

If I connect to the charger it will come up with the motorola logo and overheat...

If I try to turn on with the power button it doesnt do anything

If I connect to the computer it turns on the charging led and after a while it turns off

Any clues? D:
[Other SmartWatches] bdaman80:
Changed the kernel source code to remove the 600mhz limit

Sent from my DeathStar disabled device
[Other SmartWatches] ClearD:
Can you get into fastboot? If so, download my root tool and return to stock.
[Other SmartWatches] pmcnano:
Noup, hadnt been able since it says the battery is too low. What I can tell you is that it was working perfectly and I had around 50% battery when it died.

Has anyone tried the factory cable on this device?
[Other SmartWatches] ClearD:
Battery % shouldn't prevent you from getting into fastboot, but I think factory cable may be the way to go for you. I'm looking into making one myself, it can't be that hard lol.
[Other SmartWatches] RayToombs:
Just want to make sure I have read this right. If I want to get the 5.6 on my moto active I can flash through recovery? Correct? Thank you
[Other SmartWatches] pmcnano:
yea, I can get into fastboot, but I cant charge it so it says battery low! and LOL about the factory cable, it seems a pain in the ass without buying additional stuff, so I bought yesterday from sparkfun the microusb breakout :P That way it will be easy...though :( From 3.6dls that costed the microusb my cart finished @ 166 dls D: DAMN SPARKFUN! lol!

I will let you know!
[Other SmartWatches] ClearD:
Lol! What else did you buy? From your idea, I bought one too just now. My cart was only like $7.50 or something. :)
[Other SmartWatches] dantrevino:
Yup. Just flashed and its working perfectly.
[Other SmartWatches] kenshiro2012:
Is it possible to flash 5.6.0 using the MotoACTV Root Tool V1.1.3?
[Other SmartWatches] peablo.lingon:
how can I restore my device to celan version like straight for store ??
[Other SmartWatches] pmcnano:
Im waay to weak for SparkFun...!! :D

Bought all this D:

http://www.sparkfun.com/products/10031 x2

http://www.sparkfun.com/products/9064 x4

http://www.sparkfun.com/products/10455 x1

http://www.sparkfun.com/products/8742 x2

http://www.sparkfun.com/products/8272 x4 (which btw should have been 8 D: )

http://www.sparkfun.com/products/8276 x4

Lol!! In my defense, I live in Mexico so shipping its 33 dls...i had to buy more stuff :P
[Other SmartWatches] ClearD:
Going to try to update the root tool tonight if I can. :)

That means my Rom is temporarily on hold lol.
[Other SmartWatches] pmcnano:
Well! Im heading the movies but I did manage to make my factory cable and I connected quickly and it seems it works

:D yeeeey
[Other SmartWatches] RayToombs:
Thank you will be updating
[Other SmartWatches] pmcnano:
Well I did the factory restore. Fastboot wrote everything ok! No errors at all. Still same symptoms. If i leave it connectes to the wall it will stay at the M logo and start heating like crazy :( what da fuq
[Other SmartWatches] ClearD:
You may have a defective device... :(
[Other SmartWatches] pmcnano:
The same happened to a friend's motoactv, after flashing the modded boot.img the watch died.

Its so weird.....will check on warranty, meh :(
[Other SmartWatches] ClearD:
Which watch and which version?
[Other SmartWatches] pmcnano:
He had the 16GB one, mine is 8GB.....btw there's no key combination to boot directly to recovery right?
[Other SmartWatches] ClearD:
Not that we're aware of yet :( That's pretty much the holy grail at this point in time lol. Well, that and a working launcher for 5.6.0...
[Other SmartWatches] CEnnis91:
Just flash the stock 5.6.0 ROM in recovery and boot it up.
[Other SmartWatches] Prack:
Launchers don't work in 5.6.0? :(
[Other SmartWatches] ClearD:
They're... touchy. At the least.

Basically, I believe you can sideload them, by installing them through ADB, however I can't get one to actually flash WITH the rom itself. A rom would do no good for you guys if you have to plug into your pc to sideload a launcher just to make it work. :)

The rest of it works, I believe. Google maps + supporting files, flick wrist to turn device on (even with another launcher), etc. Just need to make one work... I've tried 2 versions of ADW, and Zeam so far. Neither wants to boot properly.
[Other SmartWatches] speedyink:
What do you mean no working launcher? Launcher pro works fine here.

Edit: never mind, I didn't see your last post about a working launcher with flash.
[Other SmartWatches] stevensmith2000:
Okay so working with my GTablet and Skyrocket, I'm used to mounting SD card from Recovery to transfer the .zip file to the device...

What is the best way to transfer the 5.6.zip file to my Motoactv? I tried to do this after I wiped cache and wiped user data and realized that it didn't mount usb storage. Is there an easy way to do this from within recovery menu?

Please let me know.

Thanks

*edit* Nevermind, figured out if I just reboot and stop adb, I can transfer the file quite easily.
[Other SmartWatches] Prack:
I thought you meant launchers in general. I understand if you can't put one in the ROM that's no big deal to side load our own.
[Other SmartWatches] CubeCloudOS:
Just Tried Flashing...

Just tried flashing 5.6.0 tried pushing su myself but never mind I'm lazy I'll just do it with the Root Tool
[Other SmartWatches] ClearD:
:p You can't flash 5.6.0 (the one in this thread) without being rooted first lol. It requires clockworkmod recovery. :)
[Other SmartWatches] CubeCloudOS:
Smacks head.....

^_^ thats why it wouldn't work at first...

Thanks!
[Other SmartWatches] quarq:
Hi

I'd like to know if those who have rooted the device have been able to install Google's MyTracks software and if it works and most importantly if it's able to connect to an ANT+ device.

Thanks!

J
[Other SmartWatches] CubeCloudOS:
WIMM and i'm?

I was thinking after looking at those that our device is WAYYYY faster and has more ram so... since the apps from those devices are SPECIFICALLY designed for small screens if anyone with one of those could pull the system/app/ folder and mod the apks to work with ours? (Especially the weather and phone dialer from the i'm)

Edit: BTW which version of facebook works? Mine I downloaded keeps FC'ing
[Other SmartWatches] bdaman80:
I installed "my tracks" on my test device. Seemed to work. As far as the cord would reach. Never fc though
[Other SmartWatches] kensikora:
I'm trying to update from my rooted 4.55.78 to rooted 5.6.0, but I keep getting "installation aborted" in CWM.

Any idea why that might be happening? I am feeling kind of dumb.

EDIT: Fixed. I just had to toggle signature verification.
[Other SmartWatches] CubeCloudOS:
Same here?!? Why does it not work? I flicked my wrist so hard my elbow joints are hurting like h*-cabbage- but the screen won't turn on...

Edit: Thanks bdaman80 any ideas why? Oh and when I move my wrist a little bit it turns on but when I actually want to check the time it stays put... weird huh? (I think they built a AI that wants to p*-cabbage- you off in this version)
[Other SmartWatches] bdaman80:
The "drunken rage fist pump" seems to turn mine on. Oh, and moving hand to change channels on tv remote. But out walking - nothing turns on.

I would prefer to turn it off 100% Tapping power button is preferred method for me.
[Other SmartWatches] kensikora:
Okay, I can't get it to work at all. Not even once have I intentionally or accidentally gotten this shake to wake thing to work. I know it's on, because I've checked and unchecked that box a few times to be sure. I just want to be able to check the time without using my other hand.
[Other SmartWatches] simx:
Just reboot the device then it will start working again, it will ultimately stop working, Moto admitted that there is a bug that stops this function, they will soon release a fix for it.

This has nothing to do with rooting at all.

NA
[Other SmartWatches] CubeCloudOS:
Thank you...

Will I have to reflash once they release it?
[Other SmartWatches] CubeCloudOS:
[rom] ics (4.0.3)

[ROM] ICS [No longer working on due to differences in epicmtd.zip and f100.zip] (4.0.3)

No longer worked on

Working:

Nothing but theme'd (Blue overscroll, app drawer animations applied to framework, wallpaper, icons)

Next version [No longer worked on] (v0.2):

Touchscreen! (Hopefully)

Wifi

Fixed launcher Fc'

Better themed

Files used:

gapps-ics-20120317.zip - Won't work but anyways... It'll look nice :D

aokp-ics-epicmtd.zip - My source 4.0.1 files (May not work cause this is a Epic 4G rom but I couldn't find a droid one)

cm7-updated-droid-signed.zip - Found a gingerbread stock droid rom (thanks utkanos!)

rooted-5.6.0-signed-f100.zip - ... got it at the front of the OP

SU-Flashable-3.0.6.zip - extracted from aokp-ics-epicmtd.zip

First one to get a ICS-like rom working w/ or w/o the files above gets thanks for tons of my saved time :) heheh
[Other SmartWatches] ClearD:
That would be wonderful, but considering we can't even get an aftermarket launcher to flash properly, I'm wondering if it could even be done lol. We don't even have an AOSP build yet. One step at a time, young jedi. x]
[Other SmartWatches] CEnnis91:
Actually there has already been steps towards an AOSP rom, however not by me. I personally have no interest in giving this device AOSP for more than one reason.

1) gingerbread and ics (ics ESPECIALLY) will not run very smoothly with only 256mb of ram and a 600mhz processor -- coming from a user of the Droid 1 for 2 years

2) there has been a lot of "optimization" done to this device in order to allow the custom motoactv apps that originally drew you into buying this device; putting AOSP on this device will likely break these apps
[Other SmartWatches] ClearD:
You actually read my mind. That's why the rom I was working on was based off the stock build (like I always do) lol. As bdaman knows, I cannot stand to detract from the stock features of a device. It might be nice for a few things, the aosp I mean, but I'm not sure that simply putting pieces of an AOSP build into the stock rom wouldn't be even better (the settings, for instance). :)
[Other SmartWatches] IseeBrickedPhones:
What we need is a custom clone of this moto launcher which has extensibility that indexes and shows all installed APKs.

I am more than happy with he UI of this device, I just want an easy way to launch sideloaded apps.

Maybe a simple launcher mapped to the music button would do for me...
[Other SmartWatches] CubeCloudOS:
Well maybe a simple launcher would be nice like you said with some AOSP settings and custom button mapping options (because I use start button for launcher not music so...)(in the rom not the tool)
[Other SmartWatches] CubeCloudOS:
BTW just saying I only bought the device for the root :) lol
[Other SmartWatches] iancrosser:
Motoactv update working with stock rom

Previously rooted using the 5.6.0 rooted rom.

Then flashed the stock 5.6.0 using clockwork recovery. After that latest update worked perfectly.

Very happy there is a way to restore the device to a pre-root condition ^_^
[Other SmartWatches] lownox:
I am thinking of editing the stock laucher to add another page for apps. Maybe make it simply call one of those "app drawer" apps. Thoughts???

Also, anyone have 6.6 .img or .zip yet? Please upload. Thanks.

I just got one of these little beasties and want to start playing. But, ya know... I gotta have the latest. And mine isn't playing nice atm.
[Other SmartWatches] IseeBrickedPhones:
Would love this. Like the look and feel of the stock UI but would like a few custom apps.
[Other SmartWatches] kensikora:
That sounds incredible. If you can pull that off, that would be absolutely ideal. I would prefer that over launching ADW just to open my app drawer or swipe through homescreens to launch an app.

But now that you've put this thought in my head, I can't stop thinking about how awesome that would be. So please, succeed.
[Other SmartWatches] lownox:
Yes, unfortunately... It is always easier said than done. :banghead:
[Other SmartWatches] kanecb89:
I was able to update to 6.6 wanna walk me through the .img you need pulled and what adb command are needed to pull it?
[Other SmartWatches] IseeBrickedPhones:
Did you look at the Sony launcher from the x10mini?
[Other SmartWatches] CubeCloudOS:
I saw it!! Very cool
[Other SmartWatches] peablo.lingon:
anyone have 6.6 .zip yet? Please upload. Thanks.
[Other SmartWatches] jorge_moran_jams:
Is it possible to sideload?

Has anyone been able to actually sideload a launcher and also install other apps and launch them?
[Other SmartWatches] speedyink:
....umm, yeah?
[Other SmartWatches] ClearD:
No.