yashsingh1/xdaforums huggingface dataset:
[XPERIA X10 Android Development] maxrfon:
Hi!

Yes i am a bit busy with my normal work :) So i am not that often here and sure i found a lot of things. Tell me in pm the way you reset MPU, maybe you are using a wrong method.

Later i come back with my research results and hopefully we can carry something out of it.
[XPERIA X10 Android Development] Blagus:
Might be a sign of Bootrom mode? (In case phone supports it, since S1 platform usually don't support it via USB cable...)
[XPERIA X10 Android Development] :
@binary:

before digging inside kexec problem, i should understand entire principle of that thing.

any sources to read about ?

about loader: s1 loader does not support loaders chaining, so after you sending another loader to phone - it refuse it at header stage and enter shutdown loop.
[XPERIA X10 Android Development] Hawkysoft:
idk if this is usefull, but for some reason it shows my device as red? o.0

if i try to read it as an brown thing it tells me...

Action journal
15:18:11 Read flash memory
15:18:11 Reads flash memory content and stores it to a file. The phone firmware security certificate has to be brown.
15:18:11 Operating system: Microsoft Windows 7 Ultimate Edition (build 7600), 64-bit
15:18:11 Application version: 0.16.3191 (beta)
15:18:11 . The action name is 'Read flash memory'
15:18:11 Selected phone type: Xperia™ X10
15:18:11 Selected connection method: USB EROM
15:18:11 i Instructions
15:18:11 i 1. Make sure the phone battery is charged to at least 50%.
15:18:11 i 2. Switch off the phone!
15:18:11 i 3. Remove the phone battery and wait at least 5 seconds before reinserting it!
15:18:11 i 4. Press and hold the return back button, then connect the cable to the phone!
15:18:11 . The action started waiting for the user
15:18:35 . The action finished waiting for the user
15:18:35 Connecting via SEMC USB Flash Device (USB2)...
15:18:35 Device driver version: 2.2.0.5
15:18:35 Detected chipset: QSD8250
15:18:35 Boot mode: EROM
15:18:35 EROM version: 1226-2253 R8A013
15:18:35 IMEI: xxxxxxxxxxxxxxxxxxxxx
15:18:35 Device ID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
15:18:35 Minimum loader AID: 0001
15:18:35 Color: Brown
15:18:35 Sending loader...
15:18:35 Waiting for loader response...
15:18:39 Saving data to file: Xperia X10_xxxxxxxxxxxxxxxxxxxxxxxxxxxx.bin
15:18:39 e Failed!
15:18:39 . The action entered shutdown phase
15:18:39 . The action reported failure

Error code
# 2BD6700B172A93A0

Error details
---
72 CA DC F8 77 FF 37 EC 65 F4 1D 9F CF E4 CF 2B
CD AA AB F9 77 AE 99 F6 A1 98 08 55 B1 5B 01 04
ED AC 2B 27 39 0C 97 D3 CB BC ED BD 91 D6 D1 9F
D7 1C BE 3D E9 72 39 79 CE 18 21 1F 12 03 F7 99
E1 CB 21 E1 A4 DC 44 65 6B 09 F1 12 CA 0F DD 9E
5C 4D 09 19 E4 C1 E4 E6 98 9F 7E A3 FE 99 0D FD
00 31 C9 A3 42 70 05 13 D6 CE BC 44 E6 29 D2 8E
EE 9B 48 CB 08 0B D5 F6 84 A4 EF 3B 44 A8 B3 3B
49 E7 05 C9 EA 0B F4 51 C7 34 F2 64 91 EB C4 00
D5 D7 15 EC 9E 4D 78 08 F0 72 B1 1B 61 48 60 7C
6D DE 5F E3 88 0C 9C DA 84 A6 C3 D0 1F 56 AF 94
1D 6E DB 48 69 A0 14 64 F5 36 03 40 C0 C6 DF A4
CD 0E 7C 66 B5 82 77 54 AB 3A 23 50 75 21 BF 5E
20
---
[XPERIA X10 Android Development] MrHassell:
The default is red, mostly all devices firmware is red and nearly all firmwares around for download are just modified red, we can never cook a red firmware due to the certificate / drm issue.

The firmwares compiled and created by J & Z are a lot more work and effort than just modified retail firmwares, tweaks, skins and apps..

I don't hink there's anything wrong with the modded or themed roms (firmwares) or that these kind of offerings are in anyway bad, they are great looking and could be better packaged as themes. These whole firmware packs, modded retail firmwares just confuse the matter, calling them rom even more again, they are if anything ram lol

Max credit to B, Z and J who genuinely compile and use brown keys to sign and make their work distribution ready! afaik this is why SE make sources available on dev world. The build.prop states the keys as red if official build, modded or not but brown also run and work perfectly :) im amazed how anyone could not make a nandroid or xRecovery backup and have a play with the GingerBread or Xfree beta4 roms and not feel compelled to want to help this work..

@maxfron - we share the same goals and hopes! Thanks to your good work, were a step closer everyday :)

@Bin4ry - can we bypass any memory address and keep essential rpc ranges isolated?

@the_laser - thank you for posting into this with your brilliance and clearing the decks! We have a good chance to hit the ground running with you and @blagus working on this and everyone who grabs the keys and starts signing builds! Blue, brown or green.. Let's take it beyond patches and themes

sent from a phonebox
[XPERIA X10 Android Development] 28spawn:
Hello just asking someone looked into /system/lib/libasahi_playnow_red_brown.so?

There is some crazy things inside like Sec_ASAHI_GetSecure_mode Sec_ASAHI_GetLiveRootPublicKey Sec_ASAHI_CoreVerifySignature Sec_ASAHI_GetTestRootPublicKey Sec_ASAHI_Internal_free Sec_ASAHI_CertificateDataList_Destroy Sec_ASAHI_GetMemMethod R2_ALG_MFUNC_pkcs1_asn1_verify_small R2_ALG_CTX_new_chain

Maybe can be useful or not!

Tks
[XPERIA X10 Android Development] MrHassell:
MallocRSA

Playnow is the Sony app store, which is covered by the Marlin DRM, for content and your observations are correct, the certificates are also exchanged with sources here for authentication, verification, validation and revokation, this is the most traditional aspect of a DRM implementation, for apps, music, video and in a nutshell - content.

MallocRSA_MallocMemsetRSA = this is why we have problems on Kexec-Tool and getting out of reserved... It's so unnecessary and I want to remove it.

The Inter Trust specification is here for anyone interested in content delivery and security.

SeaCert BootStrap DRM again is using Marlin Broadband DRM, implementation is different. Interesting in the way this package package denotes - red_brown - which is like.. a beta release? Intriguing...

Looking inside is more interesting and it's almost as if you are able to see obfuscated methods - plain text ref's = malloc / ELF... in fact sequence order events..

I'm interested in WHY Sony took the bootstrap process defined by the Open Mobile Alliance, mashed it up and why they need to go further than the apparent need for DRM and protecting PlayNow content.

Being this boot loader is the lowest level of the phone, it may be in breach of privacy laws. Nobody was ever informed of this value added security implementation or the benefit it has. Look's to me - knee jerk reaction to enforce a single O/S on the phone and in response the the PS3 master keys being passed about, meaning anyone could run Linux on a PS3 and use it for among other things, DECRYPTING RSA CERTIFICATES due to the advanced Cell processor from IBM at it's heart.
[XPERIA X10 Android Development] anders260:
Will this help us if he have success?

http://www.coveringweb.com/2011/02/geohot-to-jailbreak-playstation-phone.html
[XPERIA X10 Android Development] mad-murdock:
private key exploit

hey,

i am here to bring back an old idea - which wasn't ever tested here i guess (i follow this thread for half a year now)

its about the calculation of the ps3 private key. in my opinion, chances are high, sony uses/used the same libs they used for ps3 security in other areas of security. or better to say: using libs in ps3 which they used before.

the basic idea of this attack as short as possible:

the formular of private key encryption (i call it RSA from here) is, you cannot calculate the private key it was signed with. but sony did one big mistake: this formular includes a random number. their random number in sonys algorythms was always the same. so you have two signed binary files, both signed with the same key and using the same random number in algorythm. now you can take the RSA formular, resolve it to random number, set it into the original formular (as you know both random numbers are the same) and have one less unknown variable. so you can use it to calculate the private key. the math involved is more complex, but this is the basic idea.

in my opinion, it is worth a try if we have the same issue on xperia.

what we need? two files signed with the same key where a resulting private key could be tested to be valid most easy. thats where you guys come in. it should be as old as possible - that exploit was made public to a huge audience in 12/2010 - sony for sure fixed that issue and new signed files all have different random numbers included in the process.

if you have agreed on those two files, i would contact the fail0verflow guys, and ask them to use their tools on it (with explaining, why we are kinda stucked at xperia crack currently). i have no contact to them yet - so if one of you prefers to contact them yourself, feel free.

we should get a private key then, use it to sign a custom file, try to flash it, and then see if it works or is rejected. overall not that much effort with the possible result in getting the private key. if it succeeds, we sure need to calculate a lot more of private keys. if it fails, well, we know it doesnt work.

whats your opinion about this plan?
[XPERIA X10 Android Development] nidalius:
Laser say that SE use different Key for each Model , & Sony erricsson is not Sony this why i dont expect succes with this approach but who Know ,
[XPERIA X10 Android Development] mad-murdock:
True, but they might still use same base security libs. Worth a try imho.

Swyped with cyanogenmod 7 powered HTC Desire HD. Excuse typos.
[XPERIA X10 Android Development] yetep:
Sorry to add something that's already been suggested but surely adding a fake-remote server to SEUS and diverting it to a fake-install file would bypass the bootloader?
[XPERIA X10 Android Development] totalundone:
It's an interesting idea. I too thought something like this might work... ...

However, we first have to ask "when does it go online to check certificates (or whatever w/ Marlin)"? I *think* it checks over GSM (I believe this is allowed without any charges to the user) during boot. At that point, there's no way to be a man-in-the-middle without some serious access to their servers.

I could be very wrong, I'm still trying to understand this :)
[XPERIA X10 Android Development] Blagus:
Wouldn't work, flash files sent to phone by SEUS are still checked in phone because files HAVE to be signed with retail key.
[XPERIA X10 Android Development] andreicloud:
Has anyone tried to use the fastboot protocol so far? like: "fastboot oem unlock"=>unlocks bootloader | or is it only for the nexus one? or "fastboot flash X Y" where X is the partition and Y is the image? Maybe the bootloader could be bypassed somehow... => booting up in the standard kernel (2.6.29) and have a custom init to use kexec to bootstrap the custom kernel. Even if the standard kernel doesn't have kexec enabled we could still execute a linux kernel because it is a relocatable elf on most systems. The whole setup isn't ideal but it could get custom kernels running until there is a better solution.
[XPERIA X10 Android Development] Ether_Man:
That cant possibly be true since if it was, the phone wouldnt be possible to boot without a SIM, or without coverage. which it is... The check CANNOT be by remote. It's just not possible unless SE had their own net, that accepted phones without SIMs as well as had perfect coverage all over the world... Which we know simply isnt true. So we know that any checks are local and not over the net... Anyone claiming that it's done over the net, is simply spouting nonsense... Updates to the certs could be done OTA, but the check just cant.
[XPERIA X10 Android Development] cruzin_cruzing:
Response from George Hot:
[XPERIA X10 Android Development] cruzin_cruzing:
UPDATE:

After emailing him about how magik8ball's was willing to donate his Xperia X10:
[XPERIA X10 Android Development] Mr. Clown:
back on topic please
[XPERIA X10 Android Development] shin4u:
found a file in /system/bin/keystore

Is this file have something to do with encryption keys.....maybe you guys wanna have look...

not sure wht is this but found something about this in "init.rc"

file: /system/bin/keystore
[XPERIA X10 Android Development] wolfilein:
a few days ago, i was able to boot into xrecovery with the kexec from zdzihu

and without rebooting

but it seems like the usb port isn't powered on lsusb doesn't show me the device
[XPERIA X10 Android Development] Blagus:
How did you do it? Are you able to load custom kernels too?
[XPERIA X10 Android Development] wolfilein:
this was easy,

just load the kernel from zdzihu and then press back to boot up in the xrecovery.

but you can't talk to the pc via usb and xrecovery haven't an terminal emulator
[XPERIA X10 Android Development] Blagus:
But how? What is the comnand line and where did you put zImage file? To which partition do you append?
[XPERIA X10 Android Development] XperianPro:
How did you change kernel?
[XPERIA X10 Android Development] shin4u:
boot.img

I am not able to see mtd for boot.img and recovery.img under /dev/mtd...is there any other way to access these files???

Or if someone can upload boot.img and recovery.img that will be gr8.

Regards

Shin
[XPERIA X10 Android Development] Blagus:
recovery is locked on Xperia...
[XPERIA X10 Android Development] NFSCRYSIS:
And if you write your bootloader with custom firmware and flash through Flashtool? Do not ride? Or modify the downloaded files from SEUS and flash through it, such as firmware officially but the changes ... not much kick, but if not work then nothing else will write, unnecessarily in this I - 0
[XPERIA X10 Android Development] Blagus:
No, that's not so easy, if that was possible we would already have CM and many other fully-working ROMs on Xperia...
[XPERIA X10 Android Development] brandoncw:
Don't know if this has been discussed yet but has anyone tried breaking into the phone through PC Companion? Is it possible to find some weakness in the software and exploit that? Possibly force it to load new FW into the phone.

Just a thought...
[XPERIA X10 Android Development] Blagus:
No, no and no - no matter how you flash the phone, it will still require properly signed .sin files that can be checked on phone so there's no way to exploit SEUS or PCC...
[XPERIA X10 Android Development] qwer23:
Seems like Trip has r/w access on bootloader or something. Sorry I don't really know anything about this stuff, so just read here (starting at post 187) and and tell me what you think. Major breakthrough or not? :(

@Trip: I hope you're okay with me posting this in here.
[XPERIA X10 Android Development] iruganisan:
as you have said, its not a breakthrough, it is still ROM ported not fresh flash, coz of its boot loader lock by SE, still not yet crack though.. hopefully it will....
[XPERIA X10 Android Development] qwer23:
You misunderstood me. I'm not talking about the Arc ROM port. Go to post 187 as I specified. Trip can access and customize kernel files. That's why I asked ;)
[XPERIA X10 Android Development] MrHassell:
xRecovery Terminal (add bourne shell with python)

I understood you clearly, your talking about the Radio, which other than establishing communication channels and IS the basis of the baseband problems.. is not the bootloader or even protected, was no breakthrough!

Zdzihu compiled a kernel for X10 as update.zip file and is how we all got the DOCOMO multi touch on our devices.

I like the idea of incorporating a shell and terminal into nand flash / recovery... perhaps this isn't so impossible and would allow for the traces we need... we lack clarity due to the encryption! +1 - good thinking :)
[XPERIA X10 Android Development] MrHassell:
this is very clever ;) :cool: - Z made xRecovery for nandroid backups on the Xperia and Binary got root, made kernel patches for docomo... multiple topics here mixed up! :)
[XPERIA X10 Android Development] qwer23:
Bummer! So it doesn't get us anything that he was able to extract the kernel? Sorry then, I got excited and wanted to share. :(

Mods, please delete, since it's not dev related.
[XPERIA X10 Android Development] MrHassell:
you may be onto something in Trip's radio thread, looks like has kernel modules as a directory list.. very interesting picture :)

Meanwhile I've been looking inside spl.bin and found the sequence from power > nand > kernel loading...

androidboot.carrier=ALL Load

Load Bootimg header OK

Load kernel OK

Load ramdisk OK

Load SPL2 OK

Clearing RAM...

Load OK.

jump to spl2

jump to linux kernel

Security Unlocked RADIO-N/A EVT1 EVT2-1 EVT2-2 EVT2-5 EVT2-4 EVT2-3 EVT3 DVT1-1 DVT2-1 PVT UNKNOWN 32A 32B HBOOT
[XPERIA X10 Android Development] Blagus:
Does anyone knows how to find root partition? I've tried mount and fdisk, none showed me what is mounted on /

Maybe it's some of addresses listed in /dev when executing:

# ls /dev/*
[...]
30000062:00010000
3000000b:00030000
30000064:00010000
30000066:00010000
3000000a:00010000
30000048:00010000
30000089:00010000
3000000e:00060000
30eeeeee:00010000
3000006b:00010000
3000008c:00040000
3000fe00:a82d4624
40000101:00010000
30000012:00010000
30000013:00030000
30000014:00020000
30000071:00010000
30000091:00020000
30000016:9c95bb4d
30000019:821a1945
3000001b:9f7c9388
3000003c:beb78360
3000005b:a60286b0
3000001d:ba845703
30000000:dd7fe79a
30000002:00020000
3000005f:00010000
30000015:00010000
30000060:00010000
30000015:731f0000
30000003:d03123cc
3000005d:00010000
30000061:00010000
3000005d:9202a8e4
30000081:00010000
3000005d:00000000
00000000:0
[...]
[XPERIA X10 Android Development] pato66:
public keys.... idd_report.pem/idd_config.pem

Are these files anything?

-----BEGIN PUBLIC KEY-----

MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAox0ezqBasj7XFg9/uebk

q/O/pf9pWxFzJZlELsukCaz9Orv7lA7DmRWdlucbySh8ayGbqeG4FdFCWowHhvu/

nLtqoEn9sz5gEaHeSTssv8YHyaRqWU+ZeoFL7un7mmYfvSbyOVoOOGMuJNncK5RB

ORPM+GMR505j0yMNhc5rJQxeM/1wZYBW6zZN1DfA+18TXIoWbtQH5LFMfnmnFnfu

Rpm1MetPW+Gow5KTS278WRyJNh2bQe0+ldO9WJ/DOEAwErSyWtRfXF5BU7eLz+Cn

aMHZsCba7EixL/VyVgGjTqGhoF/CT6PQ8O5PINcKNxTdhF2GtKR/bZizzu4Q+ocy

bQIDAQAB

-----END PUBLIC KEY-----

-----BEGIN PUBLIC KEY-----

MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2gKeSIg3oxJHTUrdX+co

AXcFPz/p1YOdMkHA8rfMxaqtJ4IB28e4pYPha0pqVag12WYrhk+dA99SYpoX2AkR

fDeE4T2oJeWtrJ8FINyoX3W5uZUnQ2g2h5L+/UjVZXf4ZoAZ4fL+wMjep1lcwvn6

g4IxoibxKYBkwcI2bQ37nUWIuo93xKnEt1YiDbe8Q02n0kyBH8e31sYV+ysEfGix

zKavTPpv7Q21Zho1UMtJJgynTkwduDKW2Yf05CiUvEF8ed78UsWx8ZjRNEs2aoEf

Hu6X2mJ5jIPP72Kxnk0P5OW3HyO787Vayal2O878fw61ZqIjmM26MI803VGZrULn

GQIDAQAB

-----END PUBLIC KEY-----

This is a testkey.x509.pem

-----BEGIN CERTIFICATE-----

MIIDkTCCAnmgAwIBAgIBATANBgkqhkiG9w0BAQUFADBlMQswCQYDVQQGEwJTRTEv

MC0GA1UEChMmU29ueSBFcmljc3NvbiBNb2JpbGUgQ29tbXVuaWNhdGlvbnMgQUIx

JTAjBgNVBAMUHFNvbnlfRXJpY3Nzb25fRV9DQV9UZXN0X2RjNzAwHhcNMDAwMTAx

MTA1ODA2WhcNMzUwMTAxMTA1ODA2WjB2MQswCQYDVQQGEwJTRTEvMC0GA1UEChMm

U29ueSBFcmljc3NvbiBNb2JpbGUgQ29tbXVuaWNhdGlvbnMgQUIxNjA0BgNVBAMU

LVNvbnlfRXJpY3Nzb25fRV9BcHBsaWNhdGlvbl9TaWduaW5nX1Rlc3RfZGM3MDCC

ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAPGELixx1XZCt9BMtztQSWum

WyhBQVxk1t7bIHX4xV6iwNmj/9qRIc5xBW8Zt63AAPPUyMP9p97YolIUhb7fYfxu

Fy+ifl1HT/iZMPVbheF6/x/oEFLC8k34yHNUgm3cSKunDUhUrVXv+6jZjIZUjnpb

AoO4+bA3LVEMKABXm9vXnEXUZNjwdX3Fm6MCiTgwdOvcy9SHLSywQntxsYiodrfM

xUeEGlmSzqm5qDgSpLY5EpA6TWsCee3nxgG8izV1ZT6qF8boDjDYeDn37wq5TdtR

MdxK1Zf8h1YNSFavKpkYkmjl8DS6KQQnHPQDH8/jVnrAIhu8PWO/WS8oCzjZnE0C

AwEAAaM7MDkwDwYDVR0TAQH/BAUwAwIBADAOBgNVHQ8BAf8EBAMCB4AwFgYDVR0l

AQH/BAwwCgYIKwYBBQUHAwMwDQYJKoZIhvcNAQEFBQADggEBAJNtUqu5McmoPQPE

jQgQKptUPP3grsVWaOF+o3xMxfMZa49nJGmpLtHNex55kwC+YBWvWh+MbWCF9tSJ

ScbMoJcM6PZxoESLG3mqkXgmvMdqO2uTVzFeP5DaLRgqXncx3qpDWj2l34+GFFGF

LwZp2kPW904NxB8thcxFfNmANfPs95X7kC9jbmQgwf//XInBhnDbbSkZPtWLjmzx

KYULUdhBg+NFIpLA8K4J26M0xbo4ZLcE4JcnsL7vLyDS1w4s48vIa41740rp57ak

+PUhmiKMWyWj+Zcfmt0zxzeH1i46n0QDenCzG6906V5rCPPYgm9wV6qjws9BS017

t4VMfFo=

-----END CERTIFICATE---

Sorry, delete please if Its useless
[XPERIA X10 Android Development] Hawkysoft:
@pato66, yeah stuff that been posted weeks ago... ty for your try tho...
[XPERIA X10 Android Development] Cablekevin:
I think it's a good time to start brainstorming on IRC, boards sometimes can limit our minds.

Any new progress? First post here btw i didn't want to post anything in this dev thread except this.

Server: irc.freenode.net

Channel: #x10-update

Would be awsome if some X10 users/devs would come over to have some nice discussions about our X10.
[XPERIA X10 Android Development] MrHassell:
mounts

# mount

mount

rootfs / rootfs ro 0 0

tmpfs /dev tmpfs rw,mode=755 0 0

devpts /dev/pts devpts rw,mode=600 0 0

proc /proc proc rw 0 0

sysfs /sys sysfs rw 0 0

tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0

/dev/block/mtdblock2 /system yaffs2 ro 0 0

/dev/block/mtdblock3 /data yaffs2 rw,nosuid,nodev 0 0

/dev/block/mtdblock1 /cache yaffs2 rw,nosuid,nodev 0 0

DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,user_id=0,group_id=0,allow_other 0 0

/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

#

Next I guess your asking about the mounts?

/dev/block/mtdblock1 = /cache

/dev/block/mtdblock2 = /system + /etc

/dev/block/mtdblock3 = /data

Interesting thing happens when you take a good look at init.rc...

# start master reset

exec /sbin/mr

# check if flash aborted

exec /sbin/checkaortedflash

take a good dig into this and see the mount mtd partitions

# mount mtd partitions

# Mount /system rw first to give the file system a chance to save a checkpoint

mount yaffs2 mtd@system /system

mount yaffs2 mtd@system /system ro

remount

# We chown/chmod /data again so (wtf lol) because mount is run as root + defaults

mount yaffs2 mtd@userdata /data nosuid

nodev

chown system system /data

chmod 771 /data

does the same thing with cache... mount 1

there is some interesting reading there but the eprom > loader stage is where we need to intersect - out of the firmware loading and mount points being defined ;)

# pwd

pwd

/sys/devices/virtual/block/mtdblock0

# ls -l

ls -l

-rw-r--r-- root root 4096 2011-03-09 23:20 uevent

-r--r--r-- root root 4096 2011-03-09 23:20 dev

lrwxrwxrwx root root 2011-03-09 23:20 subsystem -> ../../../../class/block

-r--r--r-- root root 4096 2011-03-09 23:20 range

-r--r--r-- root root 4096 2011-03-09 23:20 ext_range

-r--r--r-- root root 4096 2011-03-09 23:20 removable

-r--r--r-- root root 4096 2011-03-09 23:20 ro

-r--r--r-- root root 4096 2011-03-09 23:20 size

-r--r--r-- root root 4096 2011-03-09 23:20 capability

-r--r--r-- root root 4096 2011-03-09 23:20 stat

drwxr-xr-x root root 2011-03-09 23:20 power

drwxr-xr-x root root 2011-03-09 23:20 holders

drwxr-xr-x root root 2011-03-09 23:20 slaves

drwxr-xr-x root root 2011-03-09 23:20 queue

lrwxrwxrwx root root 2011-03-09 23:20 bdi -> ../../bdi/31:0

EDIT: What you will see if you look into init.rc is the Discretix DRM middle ware is initialized here, which is beyond the scope of Marlin or the bootstrap process that already occurred. If you are looking at it here, you are looking at the end of the sequence, so turn it upside down and look at it again!