I'm ready
NA
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.
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?
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?
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
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.
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).
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
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.
Yes it is deeper. You would need an app on the iPhone and an app on the motoactv. Writing the app is not the problem. Getting a complete implementation of blues on the motoactv is.
And like I said, I can write the iPhone app and maybe the android app but the blues install / implementation is way over my head.
Will be working on this tonight. I just found out how to make the flash script clear cache and dalvik for you, pre-install. That'll probably save some headache, but it works only in edify format. Not sure what the stock recovery uses...
Anyways, I'm home!