yashsingh1/xdaforums huggingface dataset:
[Motorola Droid X2] morphius2036:
No ? is a dumb ?

Don't be sorry to offer what you see as possible information,sometimes a fresh set of eyes is what is needed.

So if you think that your post will be stupid or a bother don't you may never know that could be something that leads to what we are looking for.

Now do search the thread and see if it has been looked at before as to not re# old subjects.

And as for the title I made a syntax error and didn't put [project][no root yet] and it looked like I had the answer.
[Motorola Droid X2] MikeJ92YJ:
Umm How Do You Figure The Title PROJECT Means A Finished Product?

"Project n. a specific task of investigation"
[Motorola Droid X2] morphius2036:
I didn't have it set that way when I first posted imagine [Title]-[Project no root yet]=Oh **** its done...My Bad
[Motorola Droid X2] ashclepdia:
Wondering if anyone has seen this yet and id it could help with anything. Even if it would only help in making our phones run better.

http://sourceforge.net/projects/mb870.motorola/files/Droidx2_VZW/DTN_14.8/

Can anyone explain to me (in pm if it this is way off subject) what would be done with these open source files?
[Motorola Droid X2] singlesword:
The Kernel that is assigned to my phone is listed as : 2.6.32.9-0003-gb6084d9mqr374@nj05lnxdroid5#2, the build thats on site is showing was the 2.2 build but the odd part that im seeing in some of the files is where its referring to a TI OMAP 3 chip which is only in the Droid 3 and Bionic, I'm going to look at some more and see what i can catch.
[Motorola Droid X2] gnuworldorder:
if you go up a directory they also have one for 2.3.4 which isnt on the x2 yet which is kind of confusing
[Motorola Droid X2] singlesword:
This is very true, last night i was talking a friend of mine that works for moto (sale's guy), which he said that there is supposed to be a patch coming out next month for the rebooting and signal issue. The info i get from my friend I take with a pinch of salt tho.
[Motorola Droid X2] ashclepdia:
I believe bionic is omap 4430 tho...

I didn't find much activity after gingerbread was released tho it seems around the date it started being pushed activity stops unless im missing something.

I am gonna search more after im done work and see what I can come up with. Might stop by my sisters so I can look at it on a computer and dive deeper

Hopefully it can point us to something somewhere lol
[Motorola Droid X2] ashclepdia:
Hmmm..prerelease maybe? For a dev maybe? I will look farther...
[Motorola Droid X2] singlesword:
So while digging around the sourceforge site, i found http://sourceforge.net/projects/mb870.motorola/ which allows to download the kernel but for some reasons, I'm having issues with viewing this document, also i was able to find another build listed as 2.3.4 ( http://sourceforge.net/projects/mb870.motorola/files/Droidx2_VZW/DTN_117.15/ ) and from the link before was showing the build of 2.2 which we once had, currently my computer is giving me major issues with viewing these files, maybe because i'm running linux as a VM i dunno yet but im going to try and fix that problem so i can view some of this, but figured that maybe someone on here could look also.
[Motorola Droid X2] DAG425:
The first line is the one that also leads me to believe it is the device encryption you can set up... "Running enc_mgt_tool to set up device encryption for normal power up..." That is definitely referencing the personal device encryption as it runs on startup after you set it up.... I ran it and nothing changes in the files but new files are added....
[Motorola Droid X2] ashclepdia:
Pepper u don't need to sbf to find a change in the log.

go to settings. Location and security.

Data encryption.

Set it up.

I REALLY don't think moto would put a key we could easily find for our bootloader on the device without encrypting the file beyond belief lol
[Motorola Droid X2] Peperm1nt:
lol true, I had found it while I was trying to find the problem with my ROM and say kernel + key so I was like lets just see. I was on the Atrix Port and I figured maybe it was why it had showed up.. oh well
[Motorola Droid X2] morphius2036:
This is what I was looking at but couldn't open the .dat file

Ok digging deeper with this rabbit hole I see in there moto_tpapi, if you go to /system/bin and there is the shell enc_mgt_tool. I tried to pull it but even after chmod'ing it no go but I cat it and in there mentions

looking at the attributes of the pds/security files it shows the typical rwx-rw for files then the moto_tcmd moto_tpapi before file size and in there is the keyring.dat.

I said all of that to say this in the enc_mgt_tool.log

So in my limited understanding is the

the unlock to the emt.dat which unlocks the keyring.dat ??????? I have no clue and I am no where intelligent enough to figure out how to open a .dat file
[Motorola Droid X2] ashclepdia:
I am almost 100% certain that this is all for the device data encryption options.
[Motorola Droid X2] skwoodwiva:
+++++++++++++++++++++++
[Motorola Droid X2] Peperm1nt:
I was on the Attix port for 233. It states in the log that I check the key on the kernel... I think it's the blue or kernel sig. When I flash the 234 tonight, I'll see if it changers
[Motorola Droid X2] ashclepdia:
" Setting ro.sys.mot.encrypt.device and persist.sys.mot.encrypt.device are not set, tool is exiting."

" Running enc_mgt_tool to setup device encryption for normal power up..."

That is why I think its our personal data encryption on the phone.

go into phone settings and encrypt ur data and see if that last line changes.

If it says anything different after encrypt ur data then that's what it is and I recommend taking down ur personal decryption keys. Everyone who posted had a different key. If it was a key FOR UNLOCKING or reading the bootloader signatures (or whatever) I would expect it to be the same.
[Motorola Droid X2] DAG425:
Those last lines don't change after you encrypt your data/phone. but other files referencing the encryption are created...
[Motorola Droid X2] Peperm1nt:
OK, I see what you are saying and it does make since. But what about the kernel? If the BL is locked, why would the data encrypt tool touch the kernel?
[Motorola Droid X2] ashclepdia:
I was thinking because maybe the kernel needs that encrypt key to be able to read that data after it has been encrypted

I am not saying I am right ....this is just the educated guess I'm making from info I have seen. ;)
[Motorola Droid X2] DAG425:
I'm pretty sure you are right tho Ash... It really is the only thing that makes sense and since unfortunately we don't have the bootloader unlock implemented, there is no way to test to verify....
[Motorola Droid X2] naviathan:
Last night I downloaded the 2.3.4 SBF file and extracted the images from it. So far I've been able to find a few interesting things.

1. CG60.img (450MB) is an ext3 file system that contains the system apps apk files.

2. CG65.img (300MB) is also an ext3 file system that contains the kindle app and some games that come preinstalled.

3. CG62.img (20MB) contains the MotoHelper installer for windows.

4. CG47.img (512KB) appears to contain the bootloader

5. CG03.img (512KB) looks like it contains the public and private PKI keys for encryption.

This is where I'm at so far. I used a program called sbf_flash for linux that has an extract option. It breaks out these .img files. Some of them are pure binary and some of them contain file systems. I'm still trying to locate the rootfs, but it's not looking like it's in here.
[Motorola Droid X2] naviathan:
Has anyone thought about modding the build.prop to reflect a dev phone? Maybe we can get our hands on some other phone build.prop files that are unlocked and look for differences in the version format.
[Motorola Droid X2] aceoyame:
Not to be a downer but you guys shouldnt be looking inside of ANYTHING in /system/ if you want to break the bootloader. The keys are going to be inside the sbf file.
[Motorola Droid X2] ashclepdia:
Yeah someone mentioned that to me in beginning of thread and I also realized that moto definitely wouldn't just out something in files we could easily find using something like root explorer or whatever.

I wish I had a working computer so I could break apart sbf and spend my spare time looking for anything useful...:(
[Motorola Droid X2] Zaf9670:
Giving up?

Has everyone given up or is there a new location for updates? I was really hoping by now we'd be getting somewhere or has everyone moved past trying to unlock the bootloader? I notice the AOSP boots but I'd like to be able to adjust the CPU kernels...
[Motorola Droid X2] morphius2036:
Going to have to say most likely no work can be done to the bootloader. We are going to have to hope for a kind soul at Moto to leak out a dev ROM or keys.
[Motorola Droid X2] L2_n19h7m4r3:
Requesting thread to be closed.
[Motorola Droid X2] ashclepdia:
I noticed the same problem when trying to view the kernel package.

And I was doing it from my phone ended up having to reboot

So then I decided yo extract files and view. It never fully extracted and I waited a while for it. But then after stopping it myself and going to extracted folder ibsaw a kernel folder with a TON of files in it. I found the read me file which explained some stuff that might be useful to someone.

Also in the build file u can download I found a file that explains and a script that goes through the builds and lusts them all in a server I believe it is like what has been trying to be done by going through each build one at a tine but this script gives you an entire list of what's on the server. That's what I got from trying to read the script though. I started thinking that that script (checkbuilds.sh) within the build.gz? Could be VERY helpful to the2dcour(sorry if I spelled that wrong buddy!) In finding useful builds. Also some stuff in there about test builds which got my mind running. I just wish I understood more of this.
[Motorola Droid X2] L2_n19h7m4r3:
33,389 files to be exact!
[Motorola Droid X2] ashclepdia:
Holy crap!!

Now all we need is a program that will go through that and narrow it down to things we might need lol and it'll probably end up not having anything useful for what we want anyways. Maybe just clues scattered or something if we were lucky

No wonder I couldn't just straight open and view it. It probably gave my phone a stroke when I clicked on the zip lol. I even had to battery pull as after pressing it it tried to go to next screen but just stopped and wouldn't do anything else. Ack!
[Motorola Droid X2] ashclepdia:
I was also thinking something like that.

Does anyone know any files that have ANY bootloader mentions or information I can start at and branch out from what they contain or mention

I know in one of the files in the kernel folder had one single line in a long script that said something about oem bootloader but I don't think it wasalright anything important really
[Motorola Droid X2] Mr. Clown:
Can we stop the bickering and focus on the topic. Thanks, please keep it clean.
[Motorola Droid X2] ashclepdia:
WOW. Thanks mostknownunknown . Thanks ALOT!

I have been looking for an explanation to this degree so I can really start understanding a lot more about this and what can/needs to be done. I remember seeing that post and at the time didn't have any clue at all what it was about. I still don't understand fully but now I know where to focus my thoughts and research.

And thanks for linking your post here as I can see it being very useful. Do you mind if I have questions on this matter that I need explained if I pm you for info/help?
[Motorola Droid X2] IDMA.DROID.X2:
Sweet. Im a noob, but I got a spare x2. Ill try to do what I can. Let me know if you want me to do something. Happy to try anything in hopes to make this phone better!!!

Sent from my DROID X2
[Motorola Droid X2] mistawolfe:
You, The2DCour and TeamWin should have a sleepover - and take our bounty money.
[Motorola Droid X2] SwiftLegend:
If we found the signature, could we copy it to different files? I no nothing about this..
[Motorola Droid X2] ashclepdia:
Seriously thank you so ugh for all this info. Every time u post I feel like my eyes have been opened even wider.

I really need to get my computer running so I can help wit cheesecake.

and as a side note to the cheesecake project. I am not completely sure but that site I initially posted had a file at the bottom called build.tgz or something to that effect

When I looked at it I found a script called checkbuilds.sh that when I looked at the script I swear it could be used somehow to run through ALL thebuilds on a server and give details about them and list them all for someone to look at. I feel that IF im right and someone can implement it to work like that then the process of looking for/at different builds could become more streamlined and efficient for finding what we are looking for. I just need someone with experience to check it out. When I get done work I will follow up this post with more info on exactly what I saw.
[Motorola Droid X2] SwiftLegend:
Oh ok. I may also have a spare x2 for development. My aunt just got me a iPhone 4(LOL) and I'm gonna use that, so it doesn't go to waste and it will make her happy :) Probably be using it until I get the Prime or the Vigor..
[Motorola Droid X2] ashclepdia:
What is all these things I see when using root explorer it script manager in file

Sys/firmware/fuse

Can anything be done with these files? I see one that says device key one says jtag disable and one says securebootkey

And a bunch of others those just caught my eye and was wondering what the he'll they were and can they be of any use for anything.
[Motorola Droid X2] IDMA.DROID.X2:
It'd be funny if moto dropped the key in a folder for the bootloader to see how long it would take for ppl to find haha

Sent from my DROID X2
[Motorola Droid X2] EvilTim:
It would be even funnier if kevin butler tweeted it
[Motorola Droid X2] mostKnownUnknown:
Sigh. Did you at least try to find out the contents of the files?

./adb shell
$ su
# cd /sys/firmware/fuse
# ls
OdmProduction
kfuse_raw
DeviceKey
JtagDisable
KeyProgrammed
SecBootDeviceConfig
SecBootDeviceSelect
SecureBootKey
sku
SpareBits
SwReserved
SkipDevSelStraps
SecBootDeviceSelectRaw
ReservedOdm
# cat DeviceKey
FFFFFFFF
# cat JtagDisable
0
# cat SecureBootKey
#

To verify that there is nothing in SecureBootKey:

# dd if=/sys/firmware/fuse/SecureBootKey of=/sdcard/Dev/SecureBootKey
0+0 records in
0+0 records out
0 bytes transferred in 0.001 secs (0 bytes/sec)
#

The ReservedOdm is actually known in the Atrix world of having an indication of whether the bootloader is unlocked. The problem is that ReservedOdm (and probably all of the files in that folder) are representation of the internal fuses in the hardware. You can't write into those files. If ReservedOdm bit is the important fuse that needs to be programmed for an unlock, then it needs to be done via a legitimate command (fastboot oem unlock).

I'm building a "Locked Bookloader 101" with most of my notes. The problem is that there soo many people with a different level of understanding the phone architecture.
[Motorola Droid X2] wdenker:
I was reading over here http://www.atrixforums.com/forum/mo...rs-froyo-gingerbread-locked-not-survey-3.html that we might be able to change one of the fuses to get our bootloader unlocked. I may be way off here but they were doing some research and found the first fuse has to do with unlocking the bootloader. I am probably way off base but it is worth a shot. Maybe someone that knows what they are doing can take a look.
[Motorola Droid X2] mostKnownUnknown:
Here's mine:

./adb shell$
$ su
# cd /sys/firmware/fuse/
# ls
OdmProduction
kfuse_raw
DeviceKey
JtagDisable
KeyProgrammed
SecBootDeviceConfig
SecBootDeviceSelect
SecureBootKey
sku
SpareBits
SwReserved
SkipDevSelStraps
SecBootDeviceSelectRaw
ReservedOdm
# cat ReservedOdm
10000000000010001000100000000
#

It's an interesting study. Atrix had way more carriers with their own versions along with the fact that one of their OTA updates caused a hard brick if you downgraded to an earlier SBF. Thus they have plenty of fuse combinations. The hard part is how do we set these fuses ourselves? We could pin point the unlocked bootloader fuse. But then we have no known method to burn the fuse outside of the known fastboot oem unlock command.
[Motorola Droid X2] ashclepdia:
See the thing is ALL the research I am doing is from my phone directly. hell 99% of my posts here are from my phone. My computer is down so my capabilities are kinda limited and so is my knowledge in this subject. I am happy you are making the 101 with your notes as it will help me a lot.

My main thing I can add is fresh eyes and questions that will make people think. If youhave notice I don't think any question or post i've had on this subject had been asked before and it seems ti start some discussion each time. Im just hoping I ask the right question where one time someone says "HOLY CRAP WE CAN DO THIS" and my noobness will have paid off ;)

I still don't know why FFFFFFFF is in device key. Doesn't look like it is useful but is it? Why is it there? Lol what is device key? ;) I may be barking up the wrong tree but its better than not barking at all I think
[Motorola Droid X2] gnuworldorder:
wait is this fuse the same fuse as in filesystem in userspace?
[Motorola Droid X2] morphius2036:
Ok so what am I doing wrong if I go through terminal emulator and su I get # if I do it in ./adb shell I get permission denied. Do I need to remount -rw ? if so what is the mem block I need to remount? not sure if this works the same as an Eris.

Before you ask yes I am rooted running eclipse .5 and V6supercharger with 3G Turbo.

Ignore I didn't see the SuperUser request on the phone.
[Motorola Droid X2] morphius2036:
Not sure what this is

Ok not sure but searched the atrix post and noticed another person had similar output but never showed the decrypt sig: not sure if this is just the recipe for magic brownies or something but here is my out put form /data/emt/enc_mgt_tool.log

Running enc_mgt_tool to setup device encryption for normal power up...
setenv(PATH,/system/bin)
setenv(LD_LIBRARY_PATH,/system/lib)
Setting persist.sys.mot.encrypt.mmc already defined to [0]
Cipher choice: aes256
key-sig file length will be 80 bytes
Not an OMAP device; /system/bin/smoduled is not found.
SBK is programmed; will use TPA_AES_KEY_ENTERPRISE
GroupID temporarily set to mot_tpapi=9007, status=0
GroupID set back to root=0, status=0
Extracting key and signature pair from file...
Hash data match! Verification successful. (file=/data/emt/emt.dat)
Back up file is missing. Creating back up copy...
Error: Unable to create backup copy. system(cp /data/emt/emt.dat /data/emt/emt.bak) returned status=32512, errno=2 No such file or directory
setup_key_sig_pair returning 0
[COLOR="Red"]devcrypt_sig: [8e5cca2d0cb25bf9][/COLOR]
devcrypt_key key length: [32]
Looking for key with signature [COLOR="red"][8e5cca2d0cb25bf9][/COLOR] in kernel keying...
Adding key with key signature [8e5cca2d0cb25bf9] into keying...
Key with signature [8e5cca2d0cb25bf9] added into keying
root aid=[0]
Key ownership was set successfully
Key permission was set successfully
Ecryptfs driver is embedded. /system/lib/modules/ecryptfs.ko does not exist.
Setting ro.sys.mot.encrypt.device and persist.sys.mot.encrypt.device are not set, tool is exiting.
[Motorola Droid X2] DAG425:
I believe this might have to do with the encryption service the phone has built in to it.... But I really do not know...
[Motorola Droid X2] mostKnownUnknown:
Well all FF's in hex usually means it's empty. Second, try modifying the file without restarting. If it is a pure representation of a fuse, you wouldn't be able to change it. Until we know a means of setting a fuse, I would not overwhelm oursleves with stuff that we cannot change.

Maybe a phone restart. Whenever you su in adb, there should be a superuser request. There's no means of remounting here. It is always mounted as one of the various interfaces with the hardware. su alone should be enough to read the folder

Sent you a PM for something to try. It's interesting. But we don't know what this applies to. There are at least 5 signature checks (possibly more) the phone has to do and I doubt this covers all of them. At the same time, AES256 is not a legitimate crypto scheme for signatures. My quess is that this allows the cyrpto variables to work after the OS is loaded. But that's way later in the boot order, and I doubt that this is the same cypto component in the bootloader.

It's cool that people want to help. But there's soo many who see the word "key" or "encryption" and say "that has to be important somehow". But then they have no understanding of a digital signature or cryptography, can't test anything that they find and post on forums confusing people. Look at the xda forums for the Atrix bootloader workaround threads. 95% of the posts are people posting wrong paths. I know people want to help. But use your knowledge of the phone to verify what you find instead of blind posting hoping it is important.

I'll get the 101 out sometime today. Hopefully that clears a few things.
[Motorola Droid X2] Naex:
Do you happen to know what the problem with kexec was? I would assume that Motorola's Kernel would simply not have kexec support which kind of destroys that possibility, do you have a link to the Atrix thread? If it *does* have kexec support then that is probably our easiest (and safest) bet.

Edit: Found the link to kexec from your other post, disregard, I'll read over there.

So, apparently they actually got kexec working to a point they couldn't get a kernel compiled that could actually boot from kexec due to code relocation issues on ARM. Does anyone know if there has been a kexec module compiled for the dx2 or where I might be able to get the kernel source to start messing with compiled modules (a tun.ko would be sweet too).
[Motorola Droid X2] mostKnownUnknown:
Agree wholeheartedly. Kexec is our best chance for a bootloader bypass for the kernel. I don't have the skillset so I'll stick to my crypto knowledge and attack the bootloader problem from the signature side. Here's what I have on the kexec subject:

- singlesword seemed to have stumbled onto a DX2 kernel source: http://xdaforums.com/showpost.php?p=17424418&postcount=20

- If you follow the Atrix kexec thread (http://xdaforums.com/showthread.php?t=1079097), people following kholk's twitter say that he got kexec to run a kernel but then had issues reloading the BP/radio (might be hearsay since kholk stopped posting there after awhile and people just quoted his twitter).

- Sony Xperia X10 XDA guys got kexec to work but also ran into issues with the radio and restarts before eventually making their phone stable: http://xdaforums.com/showthread.php?t=726813

I suggest getting in contact with kholk. If they got a kernel to run, my guess is that it shouldn't be that hard for the DX2 since they have nearly the same memory architecture. I don't think anyone else in the DX2 world is working on this.
[Motorola Droid X2] mattchenzo:
As I mentioned in another thread, soldering iron! Fry that little sucker manually!
[Motorola Droid X2] gnuworldorder:
i see nothing in that file to lead me to believe its anything other than just the regular straight linux kernel. ive been looking threw a few files i think its all just AOSP stuff.
[Motorola Droid X2] wdenker:
Any more work being done on this? I am starting to think I want to sell and move to another manufacturer.
[Motorola Droid X2] ashclepdia:
I was gonna bump this later also.

But I don't think I could get rid of ny x2. As soon as I do I know awesome things will happen. But I was thinking of grabbing me a thunderbolt or incredible 2 or maybe a charge but the lure of their new phones makes me wait ;)
[Motorola Droid X2] K33pw1shen:
Koush just got an x2 so I'd wait at least another month or so cause if he's got one you know good thing will come :)
[Motorola Droid X2] K33pw1shen:
I'm due October 25th for an upgrade and not sure if I should get something else or not so I'm kinda in the same boat ....I'd be will to give up my x2 cheap to help out the cause if I do get something else