S7 Detailed System Configuration / Hardware info.

Balcora

Balcora

Member
Feb 6, 2011
59
15
For all; I'll start posting a few different tidbits that may be useful to people.
Feel free to add anything extra as well.
Info i post will be dumped from a Telstra branded S7.
(Dual Cam resistive touch, Australian telstra Firmware)


mtd info. (Gathered via: cat /proc/mtd)
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 0a000000 00020000 "system"
mtd2: 00500000 00020000 "recovery"
mtd3: 00060000 00020000 "splash"
mtd4: 06000000 00020000 "cache"
mtd5: 0af00000 00020000 "userdata"
mtd6: 00500000 00020000 "logo"


cpuinfo. (Gathered via: cat /proc/cpuinfo)

Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 163.57
Features : swp half thumb fastmult vfp edsp neon
CPU implementer : 0x51
CPU architecture: 7
CPU variant : 0x0
CPU part : 0x00f
CPU revision : 2

Hardware : QCT QSD8X50 SURF
Revision : 0000
Serial : 0000000000000000

memory info (gathered via: cat /proc/meminfo)
{Most of this will not be useful; but total sizes etc might be ;)}

MemTotal: 425096 kB
MemFree: 193628 kB
Buffers: 1312 kB
Cached: 138856 kB
SwapCached: 0 kB
Active: 146256 kB
Inactive: 61716 kB
Active(anon): 101668 kB
Inactive(anon): 0 kB
Active(file): 44588 kB
Inactive(file): 61716 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 8 kB
Writeback: 0 kB
AnonPages: 67816 kB
Mapped: 53928 kB
Slab: 8448 kB
SReclaimable: 3416 kB
SUnreclaim: 5032 kB
PageTables: 5988 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 212548 kB
Committed_AS: 2594160 kB
VmallocTotal: 1040384 kB
VmallocUsed: 106224 kB
VmallocChunk: 901124 kB

yaffs info (gathered via: cat /proc/yaffs)

YAFFS built:Sep 29 2010 12:21:19
$Id$
$Id$

Device 0 "system"
startBlock......... 0
endBlock........... 1279
totalBytesPerChunk. 2048
nDataBytesPerChunk. 2048
chunkGroupBits..... 0
chunkGroupSize..... 1
nErasedBlocks...... 192
nReservedBlocks.... 5
blocksInCheckpoint. 2
nTnodesCreated..... 5500
nFreeTnodes........ 32
nObjectsCreated.... 700
nFreeObjects....... 28
nFreeChunks........ 12328
nPageWrites........ 0
nPageReads......... 30564
nBlockErasures..... 0
nGCCopies.......... 0
garbageCollections. 0
passiveGCs......... 0
nRetriedWrites..... 0
nShortOpCaches..... 10
nRetireBlocks...... 0
eccFixed........... 0
eccUnfixed......... 0
tagsEccFixed....... 0
tagsEccUnfixed..... 0
cacheHits.......... 0
nDeletedFiles...... 0
nUnlinkedFiles..... 0
nBackgroudDeletions 0
useNANDECC......... 1
isYaffs2........... 1
inbandTags......... 0

Device 1 "userdata"
startBlock......... 0
endBlock........... 1399
totalBytesPerChunk. 2048
nDataBytesPerChunk. 2048
chunkGroupBits..... 0
chunkGroupSize..... 1
nErasedBlocks...... 12
nReservedBlocks.... 5
blocksInCheckpoint. 0
nTnodesCreated..... 8600
nFreeTnodes........ 1775
nObjectsCreated.... 3800
nFreeObjects....... 1767
nFreeChunks........ 14439
nPageWrites........ 50863
nPageReads......... 50001
nBlockErasures..... 785
nGCCopies.......... 30112
garbageCollections. 775
passiveGCs......... 47
nRetriedWrites..... 0
nShortOpCaches..... 10
nRetireBlocks...... 0
eccFixed........... 0
eccUnfixed......... 0
tagsEccFixed....... 0
tagsEccUnfixed..... 0
cacheHits.......... 10350
nDeletedFiles...... 2
nUnlinkedFiles..... 3572
nBackgroudDeletions 0
useNANDECC......... 1
isYaffs2........... 1
inbandTags......... 0

Device 2 "cache"
startBlock......... 0
endBlock........... 767
totalBytesPerChunk. 2048
nDataBytesPerChunk. 2048
chunkGroupBits..... 0
chunkGroupSize..... 1
nErasedBlocks...... 279
nReservedBlocks.... 5
blocksInCheckpoint. 1
nTnodesCreated..... 2000
nFreeTnodes........ 43
nObjectsCreated.... 100
nFreeObjects....... 88
nFreeChunks........ 21857
nPageWrites........ 43
nPageReads......... 57
nBlockErasures..... 0
nGCCopies.......... 0
garbageCollections. 0
passiveGCs......... 0
nRetriedWrites..... 0
nShortOpCaches..... 10
nRetireBlocks...... 0
eccFixed........... 0
eccUnfixed......... 0
tagsEccFixed....... 0
tagsEccUnfixed..... 0
cacheHits.......... 0
nDeletedFiles...... 0
nUnlinkedFiles..... 51
nBackgroudDeletions 0
useNANDECC......... 1
isYaffs2........... 1
inbandTags......... 0
 
yeh that is about what I see in top

$busybox top
Mem: 380512K used, 44560K free, 0K shrd, 17660K buff, 183428K cached
CPU: 2.6% usr 69.9% sys 0.1% nic 13.4% idle 13.4% io 0.0% irq 0.3% sirq

420MB is a funny number, usually it grows as 2 to the somethink ie 250 or 500 meg
 
with capacitive display and an internal "SD"

cat /proc/cpuinfo
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 664.53
Features : swp half thumb fastmult vfp edsp neon
CPU implementer : 0x51
CPU architecture: 7
CPU variant : 0x0
CPU part : 0x00f
CPU revision : 2

Hardware : QCT QSD8X50 SURF
Revision : 0000
Serial : 0000000000000000

Linux localhost 2.6.29-s70 #6 PREEMPT Thu Nov 25 00:47:44 CST 2010 armv7l GNU/Linux

rest is the same
 
Hmmz; those proc's are identical, I don't know much about these capacitive touch versions; but i'd be willing to bet most of their firmware would be compatible with the resistive touch version (of course maybe a little hack around to fix that though).
So if from what ive been reading is true and that the resistive version isn't going to get updates (which is moronic); we could always port them across ;).

Also; going to have a look at the code and see if its possible to force the resistive touch kernel side crap to report properly for multi-touch, (if anyone starts givin me lip about resistive touch being incapable of doing multi-touch, I'll be gettin flamey)
 
If someone can pull the .config and the 'busybox mount' and 'df' outputs too, that might be useful. We could keep track of the firmware revision too.
 
I'll grab em when I have a computer, as I'm house sitting atm. Way 2 lazy to dump it via the phone.

Sent from my S7 using Android Tablet Forum App
 
Mount dump

rootfs on / type rootfs (ro)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /sqlite_stmt_journals type tmpfs (rw,size=4096k)
/dev/block/mtdblock1 on /system type yaffs2 (ro)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev)
/dev/block//vold/179:0 on /sdcard type 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,flush)
/dev/loop9 on /system/bin type ext2 (rw,errors=continue)


df -ah


Filesystem Size Used Available Use% Mounted on
tmpfs 207.6M 16.0K 207.6M 0% /dev
devpts 0 0 0 0% /dev/pts
proc 0 0 0 0% /proc
sysfs 0 0 0 0% /sys
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock1 160.0M 136.9M 23.1M 86% /system
/dev/block/mtdblock5 175.0M 150.7M 24.3M 86% /data
/dev/block/mtdblock4 96.0M 54.2M 41.8M 56% /cache
/dev/block//vold/179:0
469.9M 203.5M 266.3M 43% /sdcard
/dev/loop9 14.5M 3.3M 10.5M 24% /system/bin



Attached is the config,
Reminding that it is the build from the Telstra version.
build S7V100R001C13B021
 

Attachments

  • $config.txt
    47.2 KB · Views: 616
Might attach the partition block sizes as well.

major minor #blocks name

31 0 5120 mtdblock0
31 1 163840 mtdblock1
31 2 5120 mtdblock2
31 3 384 mtdblock3
31 4 98304 mtdblock4
31 5 179200 mtdblock5
31 6 5120 mtdblock6
179 0 498176 mmcblk0
7 9 15360 loop9


True device name
Linux version 2.6.29-s70 ([email protected]) (gcc version 4.4.0 (GCC) ) #8 PREEMPT Wed Oct 27 21:55:55 CST 2010

kernel command line

console=ttyMSM2,115200n8 androidboot.hardware=qsd8k_s7




confirmed diag (also known as qualcomm DM direct interface)
/dev/diag

and by the looks; 2x i2c inferfaces,
/dev/i2c-0
/dev/i2c-1

and 3x qmi interfaces
/dev/qmi[0-2]



Shall grab more later
 
I'm going to debug the UMTS chipset later.

A quick radio log check it appears that the chipset on the S7 has issues with CSS (Cell Site Switching).
Something i'm a little off-put by,
More exploration to be done.

Also,

Anyone who hasn't seen or touched diag before but is decent with lower level hacker,
http://www.qualcomm.com/documents/interface-control-documents
 
Last edited:
Msg above, I see that kernel was compiled by a person called xionglei.

I have just sent him/her an email, if I don't get a response I will get my wife to contact him in chinese.

Perhaps we can get a real answer

Pete, on the move...
 
I have broken a bit more of the boot loader, and in very sexy news we have diag access, I'll upload some full firmware/nand dumps to a website of mine, when I pick the lock to my room, pm me for access to the nand dumps.


Sent from my S7
 
lol, sorry, it was supposed to be; pm me if you want access, and i'll upload them when i pick the lock to my room.
Which is done now.. sigh, broken locks suck :p.
I have to get the Qualcomm QXDM and QPDT software to work with the S7 Diag interface (ahem, the only copies of the 2 things are rather old; but they do support 8x50 chips.
So far the dumps i have out of it; aren't greatly useful, only informational dumps... rather then binary dumps of the sections of nand...
Thankfully the device isn't S-OFF, so its either this; or someone gets a sucessful recovery image written.
(And i'm quite lazy and don't feel like writing it right now :p.)
 
I don't know how the Qualcomm software can affect the S7, but looking forward to hearing your findings :)

And I think you meant it is S-OFF? (well, from my G1 days S-ON is an evil evil thing to have). I can fastboot write to boot and recovery. They work fine. So I am guessing we have S-OFF.

Edit: Actually, it should help to figure out what the radio firmware we are flashing, because right now we are doing it blind
 
You must log in or register to reply here.
Back
Top