Jump to content


Photo

[WIP] Disected Moto Files


  • Please log in to reply
11 replies to this topic

#1 Zeklandia

Zeklandia

    Developer

  • Members
  • PipPip
  • 75 posts
  • Twitter:@Zeklandia
  • Google+:+Asher Wood
  • LocationThe Internet
  • Current Device(s):Droid RAZR

Posted 25 December 2012 - 02:56 PM

These are sections of the .bin files in the latest JB update for the Razr. The orginals can be found here.

mbm.bin:

Please Login or Register to see this Hidden Content



This is interesting, right? I see several things:

- Support for different OMAP processors
- Unimpleminted comments on everything we want
- 2 locked status codes
- 2 unlocked status codes
- VENDOR FLASH MODE?!?!?!?!?!?!? HOLY HELL!!!!!!
- Work in progress battery stat detector?!?!
- A whole crapload of text related to device unlocking!
- HOLY SH*T!


Next up, mbmloader_hs.bin:

Please Login or Register to see this Hidden Content


Things I noticed:

- Debug mode
- PPA

Next up, mbmloader_ns.bin:

Please Login or Register to see this Hidden Content



What I noticed:

- Most of the files end with this sequence:

Please Login or Register to see this Hidden Content


- Not much here
- Mentions hmldr.bin

Next, device_tree.bin:

Please Login or Register to see this Hidden Content



Noticed:

- Verizon, Motorola, MOT_AP
- Random English words
- sensors, touch buttons, touch screen, and other device parts
- Lots of code in this file...


Next, cdt.bin (16gb version):

Please Login or Register to see this Hidden Content


Noticed:

- Customer, Verizon, and MOT_AP
- Partitions on internal storage

Here is the Terms of Service for unlocking the device:


Please Login or Register to see this Hidden Content


  • mattlgroff, Zeklandia and my2cents like this

Asher Wood
Linux, Android, Java, C/C++ Developer.
Google+ | Github


#2 BytecodeMe

BytecodeMe

    Private Pile

  • Superuser
  • 2,004 posts
  • Twitter:@BytecodeMe
  • LocationSan Diego, California
  • Current Device(s):Nexus 4, Droid Razr Maxx HD

Posted 25 December 2012 - 03:06 PM

I noticed this looking through also... didn't want to excite anyone.

Out in the open now I guess.

Sent from my DROID RAZR using Tapatalk 2

byte3plusrainbowsmallllllllller.png


#3 mattlgroff

mattlgroff

    The Dark Knight

  • Developer
  • 2,298 posts

Posted 25 December 2012 - 03:10 PM

Those are all partitions which we see in the fastboot files.

By the way those Customer Verizon MOT_AP stuff you see are the signatures on the files.

Please do not Personal Message me for help or troubleshooting. They will be ignored. Post in threads or start one in Q&A sections.

If you feel the need to donate to me, click here.


#4 Zeklandia

Zeklandia

    Developer

  • Members
  • PipPip
  • 75 posts
  • Twitter:@Zeklandia
  • Google+:+Asher Wood
  • LocationThe Internet
  • Current Device(s):Droid RAZR

Posted 25 December 2012 - 03:12 PM

Those are all partitions which we see in the fastboot files.

By the way those Customer Verizon MOT_AP stuff you see are the signatures on the files.


Signatures? Odd. There are only a few that share the same endings.

It looks to me like Moto is trying to get a way for us to unlock the device. If it's possible, maybe there's some way to enter Vendor Flash Mode.
  • Zeklandia likes this

Asher Wood
Linux, Android, Java, C/C++ Developer.
Google+ | Github


#5 Cruiserdude

Cruiserdude

    Member

  • Members
  • PipPip
  • 49 posts
  • Twitter:@andrewblitch

Posted 25 December 2012 - 07:26 PM

It's possible they're throwing us a few hints a la Samsung, but I wouldn't get too excited just yet. Remember, this is apparently an early engineering build, as evidenced by all the Chinese language stuff in there, the early timeframe of it, possibly the odd build number, and certainly the fact that it was pulled within hours and they said it was a mistake. Granted, it's quite possible it was a "mistake", but I would expect things referring to an unlocked bootloader to be present in software intended only for engineering devices. Can it get us anywhere? Again, maybe, but for now just be glad to have fully functional Jellybean. It runs great, everything works, and the phone is no longer noticeably slower than my S3, which is saying alot because the S3 rips.

#6 Zeklandia

Zeklandia

    Developer

  • Members
  • PipPip
  • 75 posts
  • Twitter:@Zeklandia
  • Google+:+Asher Wood
  • LocationThe Internet
  • Current Device(s):Droid RAZR

Posted 26 December 2012 - 07:01 AM

It's possible they're throwing us a few hints a la Samsung, but I wouldn't get too excited just yet. Remember, this is apparently an early engineering build, as evidenced by all the Chinese language stuff in there, the early timeframe of it, possibly the odd build number, and certainly the fact that it was pulled within hours and they said it was a mistake. Granted, it's quite possible it was a "mistake", but I would expect things referring to an unlocked bootloader to be present in software intended only for engineering devices. Can it get us anywhere? Again, maybe, but for now just be glad to have fully functional Jellybean. It runs great, everything works, and the phone is no longer noticeably slower than my S3, which is saying alot because the S3 rips.



Chinese? There's not any Chinese, that's just because the hex code is being represented in ANSII.

Also, other than the status codes, anything related to unlocking the device is commented out.

Asher Wood
Linux, Android, Java, C/C++ Developer.
Google+ | Github


#7 dillanshives

dillanshives

    Member

  • Members
  • PipPip
  • 132 posts
  • LocationVancouver Washington

Posted 26 December 2012 - 09:40 PM

Chinese? There's not any Chinese, that's just because the hex code is being represented in ANSII.

Also, other than the status codes, anything related to unlocking the device is commented out.


There are some things in the software that are Chinese. There is a Chinese Input.apk, for example.
If I helped you at all, don't be afraid to hit that like button! :D

#8 thrasher194

thrasher194

    http://androidn00b.com/

  • Members
  • PipPip
  • 226 posts
  • Google+:Thrasher194@gmail.com
  • LocationNorthCarolina, USA
  • Current Device(s):Motorola G4 Play (xt1609)

Posted 26 December 2012 - 10:43 PM

check for chineese in language & input under "MOTO Chinese input" i unclicked mine.

#9 Zeklandia

Zeklandia

    Developer

  • Members
  • PipPip
  • 75 posts
  • Twitter:@Zeklandia
  • Google+:+Asher Wood
  • LocationThe Internet
  • Current Device(s):Droid RAZR

Posted 27 December 2012 - 07:47 AM

check for chineese in language & input under "MOTO Chinese input" i unclicked mine.



There are some things in the software that are Chinese. There is a Chinese Input.apk, for example.



That's even included on the Razr M and HD.

Asher Wood
Linux, Android, Java, C/C++ Developer.
Google+ | Github


#10 Zeklandia

Zeklandia

    Developer

  • Members
  • PipPip
  • 75 posts
  • Twitter:@Zeklandia
  • Google+:+Asher Wood
  • LocationThe Internet
  • Current Device(s):Droid RAZR

Posted 05 January 2013 - 10:26 AM

Updated OP:

+ Added Terms of Service
* Fixed some text EOL's
- Removed Several Unkown Characters

Asher Wood
Linux, Android, Java, C/C++ Developer.
Google+ | Github


#11 Semseddin

Semseddin

    Member

  • Members
  • PipPip
  • 27 posts
  • Locationİstanbul
  • Current Device(s):XT910

Posted 12 September 2013 - 01:47 PM

Hello zeklandia, 

 

Do you have any progress or additional information about this ? I've checked what's inside the files like you did but i have no specialized logic to do the job. 



#12 Zeklandia

Zeklandia

    Developer

  • Members
  • PipPip
  • 75 posts
  • Twitter:@Zeklandia
  • Google+:+Asher Wood
  • LocationThe Internet
  • Current Device(s):Droid RAZR

Posted 02 November 2013 - 07:30 PM

Neither do I, but I have noticed that in one of the files it lists several different boot modes, including factory ones. Maybe somebody with more experience can tear this apart.


Asher Wood
Linux, Android, Java, C/C++ Developer.
Google+ | Github





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users