Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,739,156 Members 47,034 Now Online
XDA Developers Android and Mobile Development Forum

MOTOACTV ROMs

Tip us?
 
simx
Old
#61  
Member
Thanks Meter 7
Posts: 61
Join Date: Oct 2005
Quote:
Originally Posted by bdaman80 View Post
I need a brave soul or two. any takers?
I'm ready
NA
 
bdaman80
Old
#62  
bdaman80's Avatar
Senior Member
Thanks Meter 135
Posts: 383
Join Date: Mar 2011
Location: Pittsfield, Il
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
If I have helped you , please hit "Thanks"

Dont forget to support the EFF - I'm a card carrying member, are You?

Samsung SGS III (SGH-I747) - Currently ROM Jumping
MotoACTV 8Gb - ClearDroid for ACTV
Acer Iconia A500 - ReFlexx
HTC Inspire 4G - Retired
Motorola Atrix2 - Retired
HTC Lexikon - Retired
Samsung Aviator (SCH-R930) - Retired
Infinitec Pocket TV M1 (Never Released) - Bricked
Infinitec Pocket TV M3 - Retired

bdaman-dev.net
 
tansoftware
Old
(Last edited by tansoftware; 18th March 2012 at 07:12 PM.)
#63  
tansoftware's Avatar
Senior Member
Thanks Meter 64
Posts: 147
Join Date: Sep 2004
Location: Toronto
Lightbulb 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.
Attached Thumbnails
Click image for larger version

Name:	Explore2fs.JPG
Views:	78
Size:	42.5 KB
ID:	953281  
TANworks™
All Rights Reserved.

 
kevina90
Old
#64  
kevina90's Avatar
Senior Member
Thanks Meter 72
Posts: 527
Join Date: Jul 2010
Location: maryland
Quote:
Originally Posted by tansoftware View Post
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?
Phone: LG G3
Status: Stock Rooted

Tablet: Nexus 7
Status: CM

Watch: Motorola Motoactv
Status: Stock Rooted

Retired: HTC Aria, HTC Titan II, iPhone 2g, Blackberry Curve 8520, HTC ONE XL, HP Touchpad
 
tansoftware
Old
#65  
tansoftware's Avatar
Senior Member
Thanks Meter 64
Posts: 147
Join Date: Sep 2004
Location: Toronto
Quote:
Originally Posted by kevina90 View Post
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?
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.
TANworks™
All Rights Reserved.

 
ClearD
Old
#66  
ClearD's Avatar
Recognized Developer
Thanks Meter 1154
Posts: 2,875
Join Date: Jan 2009
Location: Gallipolis

 
DONATE TO ME
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?
Phone: AT&T Samsung Galaxy S3
Phone ROM: ClearDroid-BD SGS3 1.1.1 B Stable
Watch: Motorola MotoACTV
Watch ROM: ClearDroid 1.1.9 T5
PLEASE OVERCLOCK RESPONSIBLY:
"You mean I might break my car by driving it 140 mph all the time?
It's on the speedometer, so it has to be ok, right?" -bdaman80

.: If I help you, click "Thanks" to let me know! :.
USE THE SEARCH BUTTON BEFORE ASKING QUESTIONS
 
bdaman80
Old
(Last edited by bdaman80; 18th March 2012 at 08:47 PM.)
#67  
bdaman80's Avatar
Senior Member
Thanks Meter 135
Posts: 383
Join Date: Mar 2011
Location: Pittsfield, Il
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
Attached Thumbnails
Click image for larger version

Name:	uploadfromtaptalk1332098667698.jpg
Views:	114
Size:	161.3 KB
ID:	953444  
If I have helped you , please hit "Thanks"

Dont forget to support the EFF - I'm a card carrying member, are You?

Samsung SGS III (SGH-I747) - Currently ROM Jumping
MotoACTV 8Gb - ClearDroid for ACTV
Acer Iconia A500 - ReFlexx
HTC Inspire 4G - Retired
Motorola Atrix2 - Retired
HTC Lexikon - Retired
Samsung Aviator (SCH-R930) - Retired
Infinitec Pocket TV M1 (Never Released) - Bricked
Infinitec Pocket TV M3 - Retired

bdaman-dev.net
 
tansoftware
Old
#68  
tansoftware's Avatar
Senior Member
Thanks Meter 64
Posts: 147
Join Date: Sep 2004
Location: Toronto
Quote:
Originally Posted by ClearD View Post
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 :)
TANworks™
All Rights Reserved.

 
Prack
Old
#69  
Prack's Avatar
Senior Member
Thanks Meter 190
Posts: 699
Join Date: Dec 2010
Location: Lino Lakes, MN

 
DONATE TO ME
Quote:
Originally Posted by bdaman80 View Post
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
woot I see 1000 mhz in that setcpu screen
Samsung Galaxy SIII - Paranoid Android 4.4
Asus Transformer Prime/Keyboard Dock - CROMBi-kk
Motorola Xoom - EOS 4.4.4
Motorola MotoACTV - ClearDroid ACTV 1.2.0 T2
Motorola Droid - Unofficial CM 10
Motorola Droid X - Gummy v1.3.0
HTC Droid Incredible - Evervolv 4.0.0
LG Optimus V - Quattrimus CM 9
Ouya - Stock/Rooted
Google Chromecast
Raspberry Pi x3 - Raspbian(Mumble), Raspbmc(XBMC), Raspbian(phpBB/mysql)
 
bdaman80
Old
#70  
bdaman80's Avatar
Senior Member
Thanks Meter 135
Posts: 383
Join Date: Mar 2011
Location: Pittsfield, Il
Yes you do


Sent from my DeathStar disabled device
If I have helped you , please hit "Thanks"

Dont forget to support the EFF - I'm a card carrying member, are You?

Samsung SGS III (SGH-I747) - Currently ROM Jumping
MotoACTV 8Gb - ClearDroid for ACTV
Acer Iconia A500 - ReFlexx
HTC Inspire 4G - Retired
Motorola Atrix2 - Retired
HTC Lexikon - Retired
Samsung Aviator (SCH-R930) - Retired
Infinitec Pocket TV M1 (Never Released) - Bricked
Infinitec Pocket TV M3 - Retired

bdaman-dev.net

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes