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.

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 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.

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 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?

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?

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 :)

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.

XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality.Are you a developer?