Memory addresses/Memory Map for RAM, OneNAND, etc. - Bada Software and Hacking General

I am too dumb to find correct region... adresses...
But 2 ways...
1.
JTAG
Not solved yet...
2.
Via Command... + WinComm...
http://forum.xda-developers.com/showpost.php?p=12798324&postcount=3
Code:
[B]Memcpy[/B] address length
Example:
Memcpy 0x00000000 0x100
On U700 I can dump RAM on 0... but not on S8500...
Any suggestions?
Thanx.
Best Regards
Edit.:
Found in ELFs:
SDRAM_START_ADDR 0x20000000
SDRAM_END_ADDR 0x6CFFFFFF
See Screenshots. If Debug Level is Mid or High... but I don't understand, what my handset say to me...
On U700 in Debug Level Low possible to read something... on S8500 no success yet.
But maybe my fault.

Have you find the secret upload mode?
If you go to Fota in internals menu and Type something in there than bada crashes and you have got the upload mode (light bluascreen than only restart with key). but how to communicate with the device, i had not found any tool on the GSPN from samsung.

Try to memcpy RAM from 0x20000000 and 0x40000000 in S8500/8530.
Under the first one address you should find 128MB (0x8000000) of oneDRAM and under the second one 256MB (0x10000000) of SDRAM.

Rebellos said:
Try to memcpy RAM from 0x20000000 and 0x40000000 in S8500/8530.
Under the first one address you should find 128MB (0x8000000) of oneDRAM and under the second one 256MB (0x10000000) of SDRAM.
Click to expand...
Click to collapse
A small doubt:
http://dev.odroid.com/wiki/odroid-t/pds/FrontPage/s_blockdiagram.jpg
Does LPDDR1 corresponds to SDRAM?

jake792 said:
A small doubt:
http://dev.odroid.com/wiki/odroid-t/pds/FrontPage/s_blockdiagram.jpg
Does LPDDR1 corresponds to SDRAM?
Click to expand...
Click to collapse
SDRAM is kind of RAM, widely used in computers nowadays
http://en.wikipedia.org/wiki/Synchronous_dynamic_random_access_memory
LPDDR is subtype of SDRAM designed for mobile phones, that is Low-Power Ram.
I'm not sure if thats LPDDR1 or LPDDR2 in Waves.

Thanx.Also since total amount of ram is 384mb.. lesser availibility of free ram would be there.

Bump...
I have not managed problem to dump memory...
Maybe in RAM it is possible to catch some uncompressed data...
Thanx in advance.
Best Regards

Blub...
Problem 1 unsolved to read from handset via Command in bada:
Code:
[B]Memcpy[/B] address length
Memory Map...Partition Table etc. would be interesting for me in 2013...
Maybe start with Partition Table...
I need more space for apps_compressed.bin in bada 2 XXLA1...
Other ideas decrease for instance OSP partition... for test...
I have now access to edit direct in Binary Bootloader... aka boot_loader.mbn.
My skills to understand source or ELF files are very very EXTREME limited.
Maybe S8500 and S8530 have easy "partition Block" like partition.bin from S8600...
Thanx for reading.
Best Regards
Edit 1.
In ELF it is easier to find...
Code:
FLASH_MODEM_START_ADDR 0x00400000
FLASH_MODEM_END_ADDR 0x01100000
FLASH_CODE_START_ADDR 0x01100000
FLASH_CODE_END_ADDR (0x03100000+FLASH_FOTA_HOLE_RESERVED_SIZE)
FLASH_CODE_COMPRESS_START_OFFSET 0x800
Hmm.
Code:
01100000
I could check Little Endian... in boot_loader.mbn

XPKG5 need other addresses for RC1 and RC2
Also MBUKI...
I need this to identify addresses in Boot...
Best Regards

http://forum.xda-developers.com/showpost.php?p=20188325&postcount=369
Code:
// firmware qmd ver start addr max length
{ S8500v12 | BADA_APPS, 0x03050000, 0x01100000, 0x03500000 },
{ S8500v12 | BADA_RSRC1, 0x04070000, 0x04800000, 0x06F00000 },
{ S8500v12 | BADA_RSRCS, 0x04070000, 0x0B700000, 0x00F00000 },
{ S8530v12 | BADA_APPS, 0x03050000, 0x01300000, 0x03500000 },
{ S8530v12 | BADA_RSRC1, 0x04070000, 0x04A00000, 0x05000000 },
{ S8530v12 | BADA_RSRCS, 0x04070000, 0x09A00000, 0x00F00000 },
{ S8500v20 | BADA_APPS, 0x04020000, 0x01100000, 0x02000000 },
{ S8500v20 | BADA_RSRC1, 0x05020000, 0x05D00000, 0x05A00000 },
{ S8500v20 | BADA_RSRCS, 0x05020000, 0x03A00000, 0x02300000 },
{ S8530v20 | BADA_APPS, 0x04020000, 0x01300000, 0x02000000 },
{ S8530v20 | BADA_RSRC1, 0x05020000, 0x03600000, 0x04100000 },
{ S8530v20 | BADA_RSRCS, 0x05020000, 0x07700000, 0x01E00000 },
{ S8600 | BADA_APPS, 0x04020000, 0x08000000, 0x02000000 },
{ S8600 | BADA_RSRC1, 0x05020000, 0x0A200000, 0x03200000 },
{ S8600 | BADA_RSRCS, 0x05020000, 0x0D400000, 0x02800000 },
{ S7250D | BADA_APPS, 0x04020000, 0x00E00000, 0x01F00000 },
{ S7250D | BADA_RSRC1, 0x05020000, 0x02F00000, 0x01E00000 },
{ S7250D | BADA_RSRCS, 0x05020000, 0x04D00000, 0x01C00000 },
Perfect overview, very helpfull.
Big thanx b.kubica :good:
Best Regards

Memo to me...
Code:
-----------------------------------------------------------
Samsung Secondary Bootloader (SBL) v3.0
Copyright (C) Samsung Electronics Co..
Build On: Jun 8 2011 21:44:47
-----------------------------------------------------------
Re_partition: magic code(0x0)
[PAM: ] ++FSR_PAM_Init
[PAM: ] OneNAND physical base address : 0xb0000000
[PAM: ] OneNAND virtual base address : 0xb0000000
[PAM: ] OneNAND nMID=0xec : nDID=0x50
[PAM: ] --FSR_PAM_Init
fsr_bml_load_partition: pi->[B]nNumOfPartEntry = 7[/B]
partitions loading success
board partition information update.. source: 0x0
.Done.
read 1 units.
==== PARTITION INFORMATION ====
ID : *unknown id* (0x9)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 0
NO_UNITS : 1
===============================
ID : *unknown id* (0x0)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1
NO_UNITS : 7
===============================
ID : *unknown id* (0x1)
ATTR : RW SLC (0x1001)
FIRST_UNIT : 8
NO_UNITS : 796
===============================
ID : *unknown id* (0x14)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 804
NO_UNITS : 716
===============================
ID : *unknown id* (0x15)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1520
NO_UNITS : 372
===============================
ID : *unknown id* (0x17)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1892
NO_UNITS : 56
===============================
ID : *unknown id* (0x18)
ATTR : RW SLC (0x1001)
FIRST_UNIT : 1948
NO_UNITS : 56
===============================
It is possible to "identify" partitons on OneNAND via SBL from I9000 etc...
pi->nNumOfPartEntry = 7
bada Bootloader shows something like this:
Code:
[BM : ] FSR_BML_GetFullPartI() is completed
[BM : ] stPartI.nNumOfPartEntry : 7
[BM : ] 1th PartEntrt(nAttr:0x1002)(nID:0x0)
[BM : ] [1th] pPEntry->n1stVun : 1
[BM : ] [1th] [B]pPEntry->nNumOfUnits : 7[/B]
[BM : ] [1th] pPEntry->nLoadAddr : 0x0
+-------------------------------+
| Bootloader Shadowing FINISHED |
+-------------------------------+
Launch Image at 0x42480000
Catched via UART cable... + JTAG...
Will play little bit with
I9000_s1_odin_20100512.pit
and
I9000_s1_odin_20100803.pit
Tasks for 2014...
Learning more about Partitions...
Best Regards
Edit 1.
Short modified I9000_s1_odin_20100512.pit...
Code:
fsr_bml_load_partition: pi->nNumOfPartEntry = 12
partitions loading success
board partition information update.. source: 0x0
.Done.
read 1 units.
==== PARTITION INFORMATION ====
ID : IBL+PBL (0x0)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 0
NO_UNITS : 1
===============================
ID : PIT (0x1)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1
NO_UNITS : 1
===============================
ID : EF[COLOR="Red"]1[/COLOR] (0x14)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 2
NO_UNITS : 40
===============================
ID : SB[COLOR="Red"]1[/COLOR] (0x3)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 42
NO_UNITS : 5
===============================
ID : SBL[COLOR="Red"]1[/COLOR] (0x4)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 47
NO_UNITS : 5
===============================
ID : PARA[COLOR="Red"]1[/COLOR] (0x15)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 52
NO_UNITS : 20
===============================
ID : KERNE[COLOR="Red"]1[/COLOR] (0x6)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 72
NO_UNITS : 30
===============================
ID : RECOVER[COLOR="Red"]1[/COLOR] (0x7)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 102
NO_UNITS : 30
===============================
ID : FACTORYF[COLOR="Red"]1[/COLOR] (0x16)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 132
NO_UNITS : 1146
===============================
ID : DBDATAF[COLOR="Red"]1[/COLOR] (0x17)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1278
NO_UNITS : 536
===============================
ID : CACH[COLOR="Red"]1[/COLOR] (0x18)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1814
NO_UNITS : 140
===============================
ID : MODE[COLOR="Red"]1[/COLOR] (0xb)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1954
NO_UNITS : 50
===============================
RO I think should mean read only
RW = read/write
SLC and STL
NO_UNITS = Number of ... maybe... not sure

STL = Section Translation Layer (Google for BML FSR and BML STL by Samsung)
unit = 256kB or so
No idea what's SLC, "Single Level Cell" doesn't make much sense here
Probably answer is in there - https://github.com/supercurio/samsung_fsr

About SLC, etc, I wrote something about this here:
http://forum.xda-developers.com/showpost.php?p=33359041&postcount=6
I think the relevant info is in the links...

http://forum.xda-developers.com/showthread.php?t=816449
Found this usefull thread about PIT...
2014 I will play little bit Partition file PIT.
Ideas.
1.
Modifying PIT to 1 partition over the whole size... in my case 512 MB...
To write maxbe Fulldumps...
If this is nonsense during few Security limitations...
2.
Increasing first Partition to write 4 MB boot.bin... to solve this Security thingie...
http://forum.xda-developers.com/showthread.php?t=1250270
So maybe then bada Boot restoreable with SBL...
Summary...
Units seems Blocks... seems 256 KB size...
So I need instead 1 Unit... 16 for Partition 1...
Later more, I will try to "convert" this info from here now:
Code:
==== PARTITION INFORMATION ====
ID : *unknown id* (0x9)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 0
NO_UNITS : 1
Taken from here:
http://forum.xda-developers.com/showpost.php?p=49033160&postcount=11
Best Regards
Edit 1.
So bada Partition table/info looks like this... S8500..
Little bit explained... later more
Code:
==========================
ID
ATTR
FIRST_UNIT 0
NO_UNITS 1
00000000-00040000
[B]256 KB[/B]
==========================
ID
ATTR
FIRST_UNIT 1
NO_UNITS 7
00040000-001C0000
1792 KB [B]2 MB[/B]
1835008 Byte
==========================
ID
ATTR
FIRST_UNIT 8
NO_UNITS 796
203776 KB [B]203 MB[/B]
208666624 Byte
==========================
ID
ATTR
FIRST_UNIT 804
NO_UNITS 716
183296 KB [B]183 MB[/B]
187695104 Byte
==========================
ID
ATTR
FIRST_UNIT 1520
NO_UNITS 372
95232 KB [B]95 MB[/B]
97517568 Byte
==========================
ID
ATTR
FIRST_UNIT 1892
NO_UNITS 56
14336 KB [B]14 MB[/B]
14680064 Byte
==========================
ID
ATTR
FIRST_UNIT 1948
NO_UNITS 56
14336 KB [B]14 MB[/B]
14680064 Byte
===========================

Code:
<6>Scanning device for bad blocks
<7>onenand_bbt_wait: ecc 0xaaaa ctrl 0x0400 intr 0x8080 addr1 0x92 addr8 0x0
<6>OneNAND eraseblock 146 is an initial bad block
<7>onenand_bbt_wait: ecc 0xaaaa ctrl 0x0400 intr 0x8080 addr1 0x5cc addr8 0x0
<6>OneNAND eraseblock 1484 is an initial bad block
<6>OneNAND eraseblock 2047 is an initial bad block
<5>Creating 11 MTD partitions on "(null)":
<5>0x00001f000000-0x00001f500000 : "nv_data"
<5>0x000000400000-0x000009800000 : "fw_block"
<5>0x000000400000-0x000000600000 : "dbl"
<5>0x000000600000-0x000001380000 : "amss"
<5>0x000001300000-0x000003600000 : "apps"
<5>0x000003600000-0x000007700000 : "rsrc1"
<5>0x000007700000-0x000009500000 : "csc"
<5>0x000009500000-0x000009800000 : "fota"
<5>0x000009800000-0x000018f00000 : "stl1"
<5>0x000018f00000-0x00001ec00000 : "stl2"
<5>0x00001ec00000-0x00001f000000 : "secdata"
S8530 UART Log... with latest Android from volk204...
Later I will compare S8500...
Best Regards

S8530 SD-Version ZenDroKat
/proc/mtd
Code:
dev: size erasesize name
mtd0: 00500000 00040000 "nv_data"
mtd1: 09400000 00040000 "fw_block"
mtd2: 00200000 00040000 "dbl"
mtd3: 00d80000 00040000 "amss"
mtd4: 02300000 00040000 "apps"
mtd5: 04100000 00040000 "rsrc1"
mtd6: 01e00000 00040000 "csc"
mtd7: 00300000 00040000 "fota"
mtd8: 0f700000 00040000 "stl1"
mtd9: 05d00000 00040000 "stl2"
mtd10: 00400000 00040000 "secdata"
/proc/partitions
Code:
major minor #blocks name
31 0 5120 mtdblock0
31 1 151552 mtdblock1
31 2 2048 mtdblock2
31 3 13824 mtdblock3
31 4 35840 mtdblock4
31 5 66560 mtdblock5
31 6 30720 mtdblock6
31 7 3072 mtdblock7
31 8 252928 mtdblock8
31 9 95232 mtdblock9
31 10 4096 mtdblock10
253 0 488284 zram0
179 0 1912832 mmcblk0
179 1 602112 mmcblk0p1
179 2 401408 mmcblk0p2
179 3 909311 mmcblk0p3
179 16 1024 mmcblk0boot1
179 8 1024 mmcblk0boot0
179 24 15632384 mmcblk1
179 25 11330560 mmcblk1p1
179 26 18432 mmcblk1p2
179 27 563200 mmcblk1p3
179 28 3719168 mmcblk1p4

http://download.tizen.org/releases/daily/1.0/sbs/
Oh, about PIT...
Check content of file:
lutil.tar.gz
Attached...
Best Regards
Edit 1.
Oh, maybe this helps me to unterstand more...
PIT/XML files
=============
You can convert a PIT file to XML format as follows:
./pit2xml pit/SLP_ALL_Ver04.pit SLP_ALL_Ver04.xml
and back again:
./xml2pit SLP_ALL_Ver04.xml SLP_ALL_Ver04.pit
The relevant data in the file should remain the same.
The XML for SLP_ALL_Ver04.pit looks like this:
Click to expand...
Click to collapse
Edit 2.
According to this example:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<root>
<partition Name="ipl+recovery" FileName="ipl-recovery.bin" DeltaName="" BlockSize="256" BlockLength="2"/>
<partition Name="pit" FileName="pit" DeltaName="" ID="1" BlockSize="256" BlockLength="2"/>
<partition Name="csa" FileName="csa" DeltaName="" ID="2" BlockSize="256" BlockLength="32"/>
<partition Name="u-boot" FileName="u-boot-whdr.bin" DeltaName="" ID="3" BlockSize="256" BlockLength="4"/>
<partition Name="u-boot_bak" FileName="u-boot-whdr.bin" DeltaName="" ID="4" BlockSize="256" BlockLength="4"/>
<partition Name="params" FileName="params" DeltaName="" ID="5" BlockSize="256" BlockLength="4"/>
<partition Name="config" FileName="config" DeltaName="" ID="6" BlockSize="256" BlockLength="8"/>
<partition Name="kernel" FileName="uImage" DeltaName="" ID="7" BlockSize="256" BlockLength="28"/>
<partition Name="kernel_bak" FileName="uImage" DeltaName="" ID="8" BlockSize="256" BlockLength="28"/>
<partition Name="log" FileName="log" DeltaName="" ID="9" BlockSize="256" BlockLength="5"/>
<partition Name="modem" FileName="modem.img" DeltaName="" BinType="1" ID="10" BlockSize="256" BlockLength="64"/>
<partition Name="qboot" FileName="qboot" DeltaName="" ID="11" BlockSize="256" BlockLength="240"/>
<partition Name="UBI" FileName="ubi.img" DeltaName="" ID="12" Attribute="1" BlockSize="256" BlockLength="1627"/>
<partition Name="movinand" FileName="movinand.bin" DeltaName="" DevType="2" Attribute="1"/>
<partition Name="csc" FileName="rfs_part4.csc" DeltaName="" DevType="2" ID="4" Attribute="1"/>
</root>
I will try to "convert":
Code:
I9000_s1_odin_20100512.pit
I9000_s1_odin_20100803.pit
First by hand and my low brain...

Code:
===============================
ID : CACHE (0x18)
ATTR : RW STL SLC (0x1101)
FIRST_UNIT : 1814
NO_UNITS : [B]130[/B]
===============================
ID : MODEM (0xb)
ATTR : RO SLC (0x1002)
FIRST_UNIT : 1944
NO_UNITS : [B]60[/B]
===============================
Aha...
increased reserved space for AMSS... in:
I9000_s1_odin_20100512.pit
Need this for stupid tests... to start with patched SBL...
Best Regards

didn't they already understood and documented every possible part of pit file format?

didn't they already understood
Click to expand...
Click to collapse
Thanx for Link, never seen before...
No idea yet, how easy it is to use... for me.
At the moment for me it is easier to use my little brain + WinHex + example from Samsung Tizen team... in XML Format.
And I am on the older Stuff like I9000 PIT... OneNAND... not eMMC/moviNAND...
No Encryption...
Best Regards
Edit 1.
Short tested this:
http://jenkins.casual-dev.com/job/Analyze PIT File/build
Used this PIT from I9000...
I9000_s1_odin_20100512.pit
Code:
-----BEGIN PIT ANALYSIS-----
PIT Name: TA
PIT Parameter: àú
PIT Parameter: ØC
Entry Count: 13
File Type: 
--- Entry #0 ---
ID: 0 Partition Name: IBL+PBL param: S param: e param: r param: v param: e param: r param: \ param: 9 param: 0 param: \ param: T param: o
Filename: boot.bin param: i param: n param: n param: ; param: C param: : param: \ param: P param: r param: o param: g
Block Size: 1 (512B)
Block range: 256 - 256 (hex 0x100 - 0x100)
FilesystemType: 0 PartType: 0 DevType: 0 BinType: 0
Offset:6684783 Size: 2097268 FOTA: param: a param: m param: param: F param: i param: l param: e param: s param: \ param: E param: S param: T param: s param: o param: f
The IBL+PBL param: S param: e param: r param: v param: e param: r param: \ param: 9 param: 0 param: \ param: T param: o partition, identified as partition number 0, is 512B in size and carries a raw format. This partition resides on the Raw section of the AP undocumented. It identifies itself to Odin as boot.bin param: i param: n param: n param: ; param: C param: : param: \ param: P param: r param: o param: g.The partition carries a filesize of 2097268 and an offset of 6684783.
--- Entry #1 ---
ID: 1 Partition Name: PIT
Filename: param: ries.pit
Block Size: 1 (512B)
Block range: 256 - 256 (hex 0x100 - 0x100)
FilesystemType: 0 PartType: 0 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The PIT partition, identified as partition number 1, is 512B in size and carries a raw format. This partition resides on the Raw section of the AP undocumented. It identifies itself to Odin as param: ries.pit.
--- Entry #2 ---
ID: 20 Partition Name: EFS
Filename: efs.rfs
Block Size: 40 (20.5kB)
Block range: 256 - 295 (hex 0x100 - 0x127)
FilesystemType: 0 PartType: 2 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The EFS partition, identified as partition number 20, is 20.5kB in size and carries a raw format. This partition resides on the Bootloader section of the AP undocumented. It identifies itself to Odin as efs.rfs.
--- Entry #3 ---
ID: 3 Partition Name: SBL
Filename: sbl.bin
Block Size: 5 (2.6kB)
Block range: 256 - 260 (hex 0x100 - 0x104)
FilesystemType: 0 PartType: 0 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The SBL partition, identified as partition number 3, is 2.6kB in size and carries a raw format. This partition resides on the Raw section of the AP undocumented. It identifies itself to Odin as sbl.bin.
--- Entry #4 ---
ID: 4 Partition Name: SBL2
Filename: sbl.bin
Block Size: 5 (2.6kB)
Block range: 256 - 260 (hex 0x100 - 0x104)
FilesystemType: 0 PartType: 0 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The SBL2 partition, identified as partition number 4, is 2.6kB in size and carries a raw format. This partition resides on the Raw section of the AP undocumented. It identifies itself to Odin as sbl.bin.
--- Entry #5 ---
ID: 21 Partition Name: PARAM
Filename: param.lfs
Block Size: 20 (10.2kB)
Block range: 256 - 275 (hex 0x100 - 0x113)
FilesystemType: 0 PartType: 2 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The PARAM partition, identified as partition number 21, is 10.2kB in size and carries a raw format. This partition resides on the Bootloader section of the AP undocumented. It identifies itself to Odin as param.lfs.
--- Entry #6 ---
ID: 6 Partition Name: KERNEL
Filename: zImage
Block Size: 30 (15.4kB)
Block range: 256 - 285 (hex 0x100 - 0x11d)
FilesystemType: 0 PartType: 0 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The KERNEL partition, identified as partition number 6, is 15.4kB in size and carries a raw format. This partition resides on the Raw section of the AP undocumented. It identifies itself to Odin as zImage.
--- Entry #7 ---
ID: 7 Partition Name: RECOVERY
Filename: zImage
Block Size: 30 (15.4kB)
Block range: 256 - 285 (hex 0x100 - 0x11d)
FilesystemType: 0 PartType: 0 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The RECOVERY partition, identified as partition number 7, is 15.4kB in size and carries a raw format. This partition resides on the Raw section of the AP undocumented. It identifies itself to Odin as zImage.
--- Entry #8 ---
ID: 22 Partition Name: FACTORYFS
Filename: factoryfs.rfs
Block Size: 1146 (586.8kB)
Block range: 256 - 1401 (hex 0x100 - 0x579)
FilesystemType: 0 PartType: 2 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The FACTORYFS partition, identified as partition number 22, is 586.8kB in size and carries a raw format. This partition resides on the Bootloader section of the AP undocumented. It identifies itself to Odin as factoryfs.rfs.
--- Entry #9 ---
ID: 23 Partition Name: DBDATAFS
Filename: dbdata.rfs
Block Size: 536 (274.4kB)
Block range: 256 - 791 (hex 0x100 - 0x317)
FilesystemType: 0 PartType: 2 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The DBDATAFS partition, identified as partition number 23, is 274.4kB in size and carries a raw format. This partition resides on the Bootloader section of the AP undocumented. It identifies itself to Odin as dbdata.rfs.
--- Entry #10 ---
ID: 24 Partition Name: CACHE
Filename: cache.rfs
Block Size: 140 (71.7kB)
Block range: 256 - 395 (hex 0x100 - 0x18b)
FilesystemType: 0 PartType: 2 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The CACHE partition, identified as partition number 24, is 71.7kB in size and carries a raw format. This partition resides on the Bootloader section of the AP undocumented. It identifies itself to Odin as cache.rfs.
--- Entry #11 ---
ID: 11 Partition Name: MODEM
Filename: modem.bin
Block Size: 50 (25.6kB)
Block range: 256 - 305 (hex 0x100 - 0x131)
FilesystemType: 0 PartType: 0 DevType: 0 BinType: 0
Offset:0 Size: 0 FOTA:
The MODEM partition, identified as partition number 11, is 25.6kB in size and carries a raw format. This partition resides on the Raw section of the AP undocumented. It identifies itself to Odin as modem.bin.
--- Entry #12 ---
[B]ID: 11 Partition Name:
Filename:
Block Size: 0 (0B)
Block range: 0 - -1 (hex 0x0 - 0xffffffff)
FilesystemType: 0 PartType: 0 DevType: 1 BinType: 1
Offset:0 Size: 0 FOTA:
The partition, identified as partition number 11, is 0B in size and carries a raw format. This partition resides on the Raw section of the CP NAND.
[/B]
-----END PIT ANALYSIS-----
Helpfull to understand maybe last few Bytes of PIT...
Anyway... output not 100 % correct, because Blocksize is 256 KB, instead 512 Byte...
Its the difference between eMCC/moviNAND versus OneNAND...

Related

[DEVs ONLY] Flash Galaxy S without computer : introducing redbend_ua

Hello there
This is a surprise, but software able to flash the phone without any computer intervention was already on it, since the beginning.
Searching for a way to install my future lag fix easily, I remember that there was an "OTA" boot mode.
I know, today nobody saw an OTA on any Galaxy S smartpone (except maybe One on the AT&T Captivate?), but the software is still there.
How does this work :
Basically Linux boots a ramdisk, loading kernel modules and running an init process who start the whole Android experience (bootmode=) or just the recovery mode (bootmode=2).
Other bootmodes are used for battery loading only and Over The Air updates.
In this case, init.rc ask init to start "/sbin/redbend_ua all".
By default this software search for software updates in /data/fota and on similar places in the /sdcard.
It could prove useful another day, but you still have to be root to ask your device to reboot in a specific bootmode
The nice part is that we can use redbend_ua manually too, to do many impossible things before :
command list, pretty comprehensive.
Code:
img [partition name] [delta file] [device node] [temp path]
fs [partition name] [delta file] [mount point] [temp path]
all
dump <source dev> <dest file>
restore <source file> <dest dev>
compare <dev1> <dev2>
png [png file name]
all
Possible usages :
- Flashing the kernel without Odin or any computer
- Backuping and Restoring a whole firmware, including stock one
- Doing more than one operation before automatic reboot through a list of commands in /data/fota/command (not tested yet)
- Messing with bootloaders and bricking your phone for good
Yeah, you must be really carefull this time. Samsung made some partitions read-only for a reason
Hopefully this new tool will be used by most ROM cooker, CyanogenMod, and ClockWorkMod
I'll make a update.zip + redbend_ua template soon if nobody comes up with one.
My Twitter for next news
Joined to this post : redbend_ua working binary. (some firmware ship a new binary that does not accept command line parameters)
-----
Old post, for the record :
Our Galaxy S in Eclair firmwares come with software able to provide update Over The Air.
This firmware is in /sbin directory, which means that it's in the kernel ramdisk.
Look at the output when running the binary without argument or appropriate file:
Code:
# redbend_ua
RedBend Update Agent 6,1,14,1
FOTA : Make Block Device Nodes
UA/(MakeBMLNodes): mknod path=/dev/block/bml4, dev_no=35076
UA/(MakeBMLNodes): mknod path=/dev/block/bml5, dev_no=35077
UA/(MakeBMLNodes): mknod path=/dev/block/bml7, dev_no=35079
UA/(MakeBMLNodes): mknod path=/dev/block/bml8, dev_no=35080
UA/(MakeBMLNodes): mknod path=/dev/block/bml11, dev_no=35083
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
UA/ check_existence: /data/fota/delta.Sbl
UA/(update_all): Check Delta : path_idx(0), part_idx(0), file_path((null)), cnt(0)
UA/ check_existence: /data/fota/delta.zImage
UA/(update_all): Check Delta : path_idx(0), part_idx(1), file_path((null)), cnt(0)
UA/ check_existence: /data/fota/delta.modem
UA/(update_all): Check Delta : path_idx(0), part_idx(2), file_path((null)), cnt(0)
UA/ check_existence: /data/fota/delta.platform
UA/(update_all): Check Delta : path_idx(0), part_idx(3), file_path((null)), cnt(0)
UA/ check_existence: /sdcard/Android/data/temp.fota.delta/delta.Sbl
UA/(update_all): Check Delta : path_idx(1), part_idx(0), file_path((null)), cnt(0)
UA/ check_existence: /sdcard/Android/data/temp.fota.delta/delta.zImage
UA/(update_all): Check Delta : path_idx(1), part_idx(1), file_path((null)), cnt(0)
UA/ check_existence: /sdcard/Android/data/temp.fota.delta/delta.modem
UA/(update_all): Check Delta : path_idx(1), part_idx(2), file_path((null)), cnt(0)
UA/ check_existence: /sdcard/Android/data/temp.fota.delta/delta.platform
UA/(update_all): Check Delta : path_idx(1), part_idx(3), file_path((null)), cnt(0)
fail!
Open /data/fota/fota.status
fsync after write: 0
And here is the result when you provide a fake zImage delta file:
Code:
RedBend Update Agent 6,1,14,1
FOTA : Make Block Device Nodes
UA/(MakeBMLNodes): mknod path=/dev/block/bml4, dev_no=35076
UA/(MakeBMLNodes): mknod path=/dev/block/bml5, dev_no=35077
UA/(MakeBMLNodes): mknod path=/dev/block/bml7, dev_no=35079
UA/(MakeBMLNodes): mknod path=/dev/block/bml8, dev_no=35080
UA/(MakeBMLNodes): mknod path=/dev/block/bml11, dev_no=35083
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
UA/ check_existence: /data/fota/delta.Sbl
UA/(update_all): Check Delta : path_idx(0), part_idx(0), file_path((null)), cnt(0)
UA/(update_all): Check Delta : path_idx(0), part_idx(1), file_path(/data/fota/delta.zImage), cnt(1)
UA/(update_all): Check Delta : path_idx(0), part_idx(1), file_path(/data/fota/delta.zImage), cnt(1)
UA/ check_existence: /data/fota/delta.modem
UA/(update_all): Check Delta : path_idx(0), part_idx(2), file_path((null)), cnt(1)
UA/ check_existence: /data/fota/delta.platform
UA/(update_all): Check Delta : path_idx(0), part_idx(3), file_path((null)), cnt(1)
page_msize: 4096, phy_unit_size: 262144
UA/ Sbl delta does NOT exist! Skip.
page_msize: 4096, phy_unit_size: 262144
UA/ check_existence: /data/fota/fota_zImage
page_msize: 4096, phy_unit_size: 262144
dev: /dev/block/bml8 partition size: 0x780000
40180008: ffff ffff ffff ffff ffff ffff ffff ffff ................
40180018: ffff ffff ffff ffff ffff ffff ffff ffff ................
40180028: ffff ffff ffff ffff ffff ffff ffff ffff ................
40180038: ffff ffff ffff ffff ffff ffff ffff ffff ................
signature: 0xffffffff
page_msize: 4096, phy_unit_size: 262144
common mark dev : /dev/block/bml8 partition size: 0x780000
0xffffffff
page_msize: 4096, phy_unit_size: 262144
page_msize: 4096, phy_unit_size: 262144
UA/(backup_devbml) src: /dev/block/bml7 partition size: 0x780000
UA/(backup_devbml) dst: /dev/block/bml8 partition size: 0x780000
UA/(backup_devbml) backup 128KB at 0x0
UA/(backup_devbml) backup 128KB at 0x40000
UA/(backup_devbml) backup 128KB at 0x80000
UA/(backup_devbml) backup 128KB at 0xc0000
UA/(backup_devbml) backup 128KB at 0x100000
UA/(backup_devbml) backup 128KB at 0x140000
UA/(backup_devbml) backup 128KB at 0x180000
UA/(backup_devbml) backup 128KB at 0x1c0000
UA/(backup_devbml) backup 128KB at 0x200000
UA/(backup_devbml) backup 128KB at 0x240000
UA/(backup_devbml) backup 128KB at 0x280000
UA/(backup_devbml) backup 128KB at 0x2c0000
UA/(backup_devbml) backup 128KB at 0x300000
UA/(backup_devbml) backup 128KB at 0x340000
UA/(backup_devbml) backup 128KB at 0x380000
UA/(backup_devbml) backup 128KB at 0x3c0000
UA/(backup_devbml) backup 128KB at 0x400000
UA/(backup_devbml) backup 128KB at 0x440000
UA/(backup_devbml) backup 128KB at 0x480000
UA/(backup_devbml) backup 128KB at 0x4c0000
UA/(backup_devbml) backup 128KB at 0x500000
UA/(backup_devbml) backup 128KB at 0x540000
UA/(backup_devbml) backup 128KB at 0x580000
UA/(backup_devbml) backup 128KB at 0x5c0000
UA/(backup_devbml) backup 128KB at 0x600000
UA/(backup_devbml) backup 128KB at 0x640000
UA/(backup_devbml) backup 128KB at 0x680000
UA/(backup_devbml) backup 128KB at 0x6c0000
UA/(backup_devbml) backup 128KB at 0x700000
UA/(backup_devbml) backup 128KB at 0x740000
page_msize: 4096, phy_unit_size: 262144
common mark dev : /dev/block/bml8 partition size: 0x780000
0xffffffff
page_msize: 4096, phy_unit_size: 262144
common mark dev : /dev/block/bml8 partition size: 0x780000
0xffffffff
UA/(RB_ImageUpdateMain): ++
UA/(RB_ImageUpdateMain) uPartitionName[zImage]
RB_GetBlockSize: returning 0x40000 (262144)
UA/(RB_UpdateImage): ++
UA/(RB_UpdateImage): Delta file name-/data/fota/delta.zImage
unicode_to_char : zImage
pDeviceDatum.pFirstPartitionData->partition_name: zImage
pDeviceDatum.pFirstPartitionData->partition_type: 0
pDeviceDatum.pFirstPartitionData->file_system_type: 0
unicode_to_char : /data/fota/delta.zImage
RB_OpenFile: Path:/data/fota/delta.zImage | Mode: RDONLY
Successful open() *pwHandle:4
[RB] Illegal field in the delta, or that the given delta is invalid
UA/(RB_UpdateImage) return value from RB_vRM_Update: 0x80000539
UA/(RB_UpdateImage): -- ret=-2147482311
UA/(RB_ImageUpdateMain) pCustomerPartData.updated = -1, rest = -1
UA/(RB_ImageUpdateMain): -- ret=-2147482311
page_msize: 4096, phy_unit_size: 262144
common mark dev : /dev/block/bml8 partition size: 0x780000
0xdeade002
UA/(update_all) Kernel update fail
fail!
Open /data/fota/fota.status
fsync after write: 0
Promising ! This software definitely has the ability to write on protected bml partitions.
Now wee need to find how to produce the .delta files
Sounds great Lets hope you guys can figure it all out.
I just send a message to Red Bend Software through their site.
Actually it may help to find any other delta file for their software. Without sample we won't go anywhere...
I hope they will be kind and answer!
Here is a list of interesting strings found in the binary :
Code:
UA/ Platform delta does NOT exist! Skip.
Can not open src file : %s
Can not open dst file : %s
UA/(%s) write %dbytes
UA/(%s) copy file %s->%s
fsync failed with return value: %d
fsync after write: %d
UA/ %s: %s
/dev/block/bml4
/data/fota/dump_sbl
/dev/block/bml7
/data/fota/dump_kernel
/dev/block/bml12
/data/fota/dump_modem
FOTA : Make Block Device Nodes
UA/(%s): mknod path=%s, dev_no=%u
Failed to open %s: %s
Open %s
lseek failed with return value: %d
read failed with return value: %d
success!
DONE
fail!
FAIL
FOTA
UA/ modem delta does NOT exist! Skip.
/data/fota/backup.modem
UA/ zImage delta does NOT exist! Skip.
/dev/block/bml8
UA/ Sbl delta does NOT exist! Skip.
UA/ERROR(%s) get dual sbl siginfo fail!!
/dev/block/bml5
UA/ERROR(%s) can't find vaild Sbl partitions
UA/ERROR(%s) SBL RAM partition alloc fail
UA/ERROR(%s) RB_ImageUpdateMain Fail ret=(0x%d)
/data/fota/command
/sdcard/Android/data/temp.fota.delta/command
UA/(%s) cache download
/cache/recovery
UA/(%s) create /cache/recovery directory
/cache/recovery/command
reboot recovery
UA/(%s): Check Delta : path_idx(%d), part_idx(%d), file_path(%s), cnt(%d)
SBL update fail
UA/(%s) %s
Kernel update fail
Modem update fail
Platform update fail
Post update fail
WARNNIG
Delta Not Exist
/data/fota
/sbin/images/fota.png
UA/(%s) test
Update Fail!!
/data/fota/fota.status
/data/fota/delta.Sbl
/data/fota/delta.zImage
/data/fota/delta.modem
/data/fota/delta.platform
/sdcard/Android/data/temp.fota.delta/delta.Sbl
/sdcard/Android/data/temp.fota.delta/delta.zImage
/sdcard/Android/data/temp.fota.delta/delta.modem
/sdcard/Android/data/temp.fota.delta/delta.platform
RedBend Update Agent %s
commands:
img [partition name] [delta file] [device node] [temp path]
fs [partition name] [delta file] [mount point] [temp path]
all
dump <source dev> <dest file>
restore <source file> <dest dev>
compare <dev1> <dev2>
png [png file name]
all
unknown
/data/fota/fota_Sbl
/data/fota/fota_zImage
Modem
/data/fota/fota_modem
/data/fota/fota_platform
/dev/block/bml11
OFNI
main
update_all
post_update
update_platform
update_modem
update_zImage
update_Sbl
file_copy
check_existence
MakeBMLNodes
UA/(%s): +
UA/(%s): %s (%lx %x)
UA/(%s): -
UA/(%s): %s (%lx %lx)
UA/(%s): memcpy(0x%x, 0x%x, 0x%x)
%07x:
%02x
%02x
BML_GET_DEV_INFO
page_msize: %d, phy_unit_size: %d
open device file
%s: bmldevice_open failed!
%s: bmldevice_info failed!
src: %s
dst: %s partition size: 0x%x
part_size: 0x%x
failed to read from %s (%s)
read finished
read %d bytes
src: %s partition size: 0x%x
dst: %s
failed to write to %s (%s)
done
UA/(%s) src: %s
UA/(%s) dst: %s partition size: 0x%x
UA/(%s) part_size: 0x%x
UA/(%s) read finished
UA/(%s) read %d bytes
UA/(%s) src: %s partition size: 0x%x
UA/(%s) dst: %s
UA/(%s) signature: 0x%x
*WARN* %s partition is already marked as invalid!
UA/(%s) done
page at 0x%x differ!
UA/(%s) backup 128KB at 0x%x
UA/(%s): ++
UA/(%s) 0x%x
UA/ERROR(%s) Valid partition signature is not invalid
UA/(%s): --
%s, invalide magic key(%x)!!
common mark dev : %s partition size: 0x%x
dev: %s partition size: 0x%x
signature: 0x%x
UA/(%s) dev: %s partition size: 0x%x
UA/ERROR(%s) Signature is not validate (%x)
UA/(%s) SBL, SBL2 partition are diffierent size, check your bml device node name
UA/ERROR(%s) Both partition has valid or invalid signature
UA/(%s) Valid Partition-%s, Update Partition-%s
restore_file
backup_block_file
restore_devbml
backup_devbml
store_dualsbl_partition
load_partition
mark_common_recovery
find_valid_partition
check_dualpartition_validation
ram_write_block
ram_read_block
nand_write_block
nand_read_block
bmldevice_get_size
Image size is bigger than partition!
reading NAND page
BML_UNLOCK_ALL
writing NAND page
6,1,14,1
RB_GetBlockSize
%s: returning 0x%x (%d)
RB_ReadBackupBlock
UA/(%s): %s: offset 0x%lx(%ld), size 0x%lx(%ld)
UA/ERROR(%s) open file %s failed.
UA/ open %s file success
UA/ERROR(%s) error in read size
RB_WriteBackupBlock
UA/(%s): offset 0x%lx(%ld), size 0x%lx(%ld)
UA/ERROR(%s) error in write size
RB_ImageUpdateMain
UA/(%s): ++
UA/(%s) uPartitionName[%s]
UA/(%s) pCustomerPartData.updated = %d, rest = %d
UA/(%s): -- ret=%d
RB_UpdateImage
UA/(%s): Delta file name-%s
pDeviceDatum.pFirstPartitionData->partition_name: %s
pDeviceDatum.pFirstPartitionData->partition_type: %d
pDeviceDatum.pFirstPartitionData->file_system_type: %d
UA/(%s) return value from RB_vRM_Update: 0x%x
unicode_to_char
%s : %s
RecursiveFolderCreater
%s path: %s
temppath: %s
mkdir result: %d errno: %d
RB_CopyFile
%s: %s -> %s
NULL file name find. Abort.
Open %s ENOENT %d
Open %s failed. Abort.
read %d, but write %d, abort.
RB_DeleteFile
%s: %s
unlink value: %d, errno: %d
RB_DeleteFolder
rmdir value: %d, errno: %d
RB_CreateFolder
%s: %s, mode:0x%x
RDONLY
WRONLY
RDWR
Unknown
RB_OpenFile
%s: Path:%s | Mode:
First open() with error %d
copy dir[]=%s
remove dir[]=%s
Fail create folder, Leave RB_OpenFile
After successful creating folder, fail open() with error %d
Successful open() *pwHandle:%ld
RB_ResizeFile
%s: handle %ld, dwSize %d
%s: ret %d handle %ld %d
RB_CloseFile
%s: wHandle = %ld
RB_WriteFile
%s: Handle:%ld , Pos:%ld , Size: %ld
lseek failed with return value: %d
Failed with return value: %d
Bytes Write: %d
fsync Failed with return value: %d
fsync after write: %d
RB_ReadFile
%s: Handle:%ld , Pos:%ld , Size: %ld
read failed with return value: %d
RB_GetFileSize
%s: %ld
lseek errno: %d
Returning Size = 0x%x
RB_Unlink
unlink failed with return value: %d
unlink with return value: %d
RB_Link
symlink failed with return value: %d, errno: %d
symlink with return value: %d
RB_VerifyLinkReference
readlink failed with return value: %d
not same linked path
same linked path
RB_GetFileType
stat failed with return value: %d errno: %d
sbuf.st_mode: %d
S_ISREG(sbuf.st_mode): %d
S_ISLNK(sbuf.st_mode): %d
stat->st_mode = symbolic link file
stat->st_mode = regular file
failed to lstat, err : %d
a2ch
%s : %d
Wrong attribute value: %d
a2ch : %c
chtoa
RB_SetFileAttributes
stat failed with return value: %d
sbuf.st_mode value: %d
ui8pAttribs value: %s
ui32AttribSize value: %ld
attrib_user value: %d
attrib_group value: %d
attrib_other value: %d
att_type value: %d
sbuf.st_mode | attrib: %d
chmod failed with return value: %d
chmod with return value: %d
pUserId value: %s
user_id value: %d
aGroupId value: %s
pGroupId value: %s
group_id value: %d
failed chown %d
success chown %d
RB_FSUpdateMain
UA/(%s) Partition name(%s), mount point(%s)
UA/(%s) pCustomerPartData.updated = %ld, rest = %ld
pDeviceDatum.pFirstPartitionData->partition_name: %s
pDeviceDatum.pFirstPartitionData->partition_type: %d
pDeviceDatum.pFirstPartitionData->file_system_type: %d
return value from RB_vRM_Update: 0x%x
%s/flagsFile
return value from unlink(%s): 0x%x
Installing software
Don't turn off the
phone and
connect the power
cable as possible.
System updated &
reboot now
gui_progress
UA/(%s): ++ uPercent(%d%), gv_delta_count=(%ld)
UA/(%s): -- Print Percent(%d%)
%3d %%
lcd_init
%s(%d): start!
/dev/graphics/fb0
%s(%d): fb0 open fail
%s(%d): fb0 open success
%s(%d): width = %d, height = %d
%s(%d): ioctl set info fail
%s(%d): Error: failed to map framebuffer device to memory.
%s(%d): ioctl start fail
Allocation error-
Current start: %d
Current finish: %d
Requested size: %d
Allocation error:
Current start: %d
Current finish: %d
Requested size: %d
It may accept commands somehow, like those :
img [partition name] [delta file] [device node] [temp path]
fs [partition name] [delta file] [mount point] [temp path]
all
dump <source dev> <dest file>
restore <source file> <dest dev>
compare <dev1> <dev2>
png [png file name]
all
I tried writing commands in /data/fota/command and /cache/recovery/command but the program does not follow my orders
ok it works when i flashed zImage
Code:
# redbend_ua restore /sdcard/jm5.zImage /dev/block/bml7
redbend_ua restore /sdcard/jm5.zImage /dev/block/bml7
RedBend Update Agent 6,1,14,1
FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
page_msize: 4096, phy_unit_size: 262144
src: /sdcard/jm5.zImage
dst: /dev/block/bml7 partition size: 0x780000
part_size: 0x780000
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 247184 bytes
read finished
Wow, this is looking promising.
it seems like htc's flash_image,but much more difficult than it.
raspdeep said:
ok it works when i flashed zImage
Code:
# redbend_ua restore /sdcard/jm5.zImage /dev/block/bml7
redbend_ua restore /sdcard/jm5.zImage /dev/block/bml7
RedBend Update Agent 6,1,14,1
FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
page_msize: 4096, phy_unit_size: 262144
src: /sdcard/jm5.zImage
dst: /dev/block/bml7 partition size: 0x780000
part_size: 0x780000
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 247184 bytes
read finished
Click to expand...
Click to collapse
Nice raspdeep
How did you do ? Every attempt fails here (in recovery or standard mode).
Which initramfs version do you use ?
Code:
redbend_ua restore zImage /dev/block/bml7
RedBend Update Agent 6,1,14,1
FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
page_msize: 4096, phy_unit_size: 262144
src: zImage
dst: /dev/block/bml7 partition size: 0x780000
part_size: 0x780000
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 247184 bytes
read finished
Ok yo don't respond but it works here to, booting on your OC kernel. Now i'll find what is different between our setups
supercurio, you are rapidly becoming one of my Android heros...
distortedloop said:
supercurio, you are rapidly becoming one of my Android heros...
Click to expand...
Click to collapse
Don't know if I can live with that
Code:
ll */*
-rwxr-xr-x 1 root curio 313888 2010-08-26 21:14 oc128uv1/redbend_ua*
-rwxr-xr-x 1 curio curio 314004 2010-08-26 21:16 XWJM5/redbend_ua*
md5sum */*
74f5793536c3cdc902ec269c3f51a165 oc128uv1/redbend_ua
b1ba258a5d673c537a95167267afd6b8 XWJM5/redbend_ua
Different binaries !
Edit : attached working redbend_ua
A diff between strings included in binaries (raw infos, not analyzed yet ^^)
Code:
--- not-working 2010-08-26 21:22:39.594984596 +0200
+++ working 2010-08-26 21:22:20.370634450 +0200
@@ -4,7 +4,6 @@
@F2A
bB,2
H{DYX
-/Q{;
/Qs;
/Qk;
/Qc;
@@ -452,71 +451,52 @@
%mB(
@ #!
!1C "
-reboot
-UA/ Platform delta does NOT exist! Skip.
-Can not open src file : %s
-Can not open dst file : %s
-UA/(%s) write %dbytes
-UA/(%s) copy file %s->%s
- fsync failed with return value: %d
- fsync after write: %d
-UA/ %s: %s
+/data/fota/delta.Sbl
/dev/block/bml4
-/data/fota/dump_sbl
+/dev/block/bml5
+/data/fota/fota_Sbl
+/data/fota/delta.zImage
/dev/block/bml7
-/data/fota/dump_kernel
+/data/fota/backup.zImage
+/data/fota/fota_zImage
+Modem
+/data/fota/delta.modem
/dev/block/bml12
+/data/fota/backup.modem
+/data/fota/fota_modem
+/data/fota/delta.platform
+/data/fota/backup.platform
+/data/fota/fota_platform
+platform delta does NOT exist! Skip.
+existence: s1[%d].existence; %d
+%s: %s
+/data/fota/dump_sbl
+/data/fota/dump_kernel
/data/fota/dump_modem
FOTA : Make Block Device Nodes
-UA/(%s): mknod path=%s, dev_no=%u
Failed to open %s: %s
Open %s
lseek failed with return value: %d
read failed with return value: %d
+ fsync failed with return value: %d
+ fsync after write: %d
success!
DONE
fail!
FAIL
FOTA
-UA/ modem delta does NOT exist! Skip.
-/data/fota/backup.modem
-UA/ zImage delta does NOT exist! Skip.
+modem delta does NOT exist! Skip.
+zImage delta does NOT exist! Skip.
/dev/block/bml8
-UA/ Sbl delta does NOT exist! Skip.
-UA/ERROR(%s) get dual sbl siginfo fail!!
-/dev/block/bml5
-UA/ERROR(%s) can't find vaild Sbl partitions
-UA/ERROR(%s) SBL RAM partition alloc fail
-UA/ERROR(%s) RB_ImageUpdateMain Fail ret=(0x%d)
-/data/fota/command
-/sdcard/Android/data/temp.fota.delta/command
-UA/(%s) cache download
-/cache/recovery
-UA/(%s) create /cache/recovery directory
-/cache/recovery/command
-reboot recovery
-UA/(%s): Check Delta : path_idx(%d), part_idx(%d), file_path(%s), cnt(%d)
-SBL update fail
-UA/(%s) %s
-Kernel update fail
-Modem update fail
-Platform update fail
-Post update fail
-WARNNIG
-Delta Not Exist
-/data/fota
-/sbin/images/fota.png
-UA/(%s) test
-Update Fail!!
+Sbl delta does NOT exist! Skip.
+get dual sbl siginfo fail!!
+can't find vaild Sbl partitions
+reboot
+gv_delta_count[%d]
+dump
+restore
+compare
/data/fota/fota.status
-/data/fota/delta.Sbl
-/data/fota/delta.zImage
-/data/fota/delta.modem
-/data/fota/delta.platform
-/sdcard/Android/data/temp.fota.delta/delta.Sbl
-/sdcard/Android/data/temp.fota.delta/delta.zImage
-/sdcard/Android/data/temp.fota.delta/delta.modem
-/sdcard/Android/data/temp.fota.delta/delta.platform
RedBend Update Agent %s
commands:
img [partition name] [delta file] [device node] [temp path]
@@ -527,29 +507,7 @@
compare <dev1> <dev2>
png [png file name]
all
-unknown
-/data/fota/fota_Sbl
-/data/fota/fota_zImage
-Modem
-/data/fota/fota_modem
-/data/fota/fota_platform
-/dev/block/bml11
OFNI
-main
-update_all
-post_update
-update_platform
-update_modem
-update_zImage
-update_Sbl
-file_copy
-check_existence
-MakeBMLNodes
-UA/(%s): +
-UA/(%s): %s (%lx %x)
-UA/(%s): -
-UA/(%s): %s (%lx %lx)
-UA/(%s): memcpy(0x%x, 0x%x, 0x%x)
%07x:
%02x
%02x
@@ -568,71 +526,67 @@
dst: %s
failed to write to %s (%s)
done
-UA/(%s) src: %s
-UA/(%s) dst: %s partition size: 0x%x
-UA/(%s) part_size: 0x%x
-UA/(%s) read finished
-UA/(%s) read %d bytes
-UA/(%s) src: %s partition size: 0x%x
-UA/(%s) dst: %s
-UA/(%s) signature: 0x%x
-*WARN* %s partition is already marked as invalid!
-UA/(%s) done
page at 0x%x differ!
-UA/(%s) backup 128KB at 0x%x
-UA/(%s): ++
-UA/(%s) 0x%x
-UA/ERROR(%s) Valid partition signature is not invalid
-UA/(%s): --
+signature: 0x%x
+*WARN* %s partition is already marked as invalid!
+backup 128KB at 0x%x
+backup 128KB at 0x%x without signature
+clear mark dev : %s partition size: 0x%x
%s, invalide magic key(%x)!!
-common mark dev : %s partition size: 0x%x
dev: %s partition size: 0x%x
-signature: 0x%x
-UA/(%s) dev: %s partition size: 0x%x
-UA/ERROR(%s) Signature is not validate (%x)
-UA/(%s) SBL, SBL2 partition are diffierent size, check your bml device node name
-UA/ERROR(%s) Both partition has valid or invalid signature
-UA/(%s) Valid Partition-%s, Update Partition-%s
-restore_file
-backup_block_file
-restore_devbml
-backup_devbml
-store_dualsbl_partition
-load_partition
+%s:clear:%s partition size: 0x%x
+%s : write and clear signature done
+%s:write:%s partition size: 0x%x
+%s: Signature is not validate (%x)
+%s signature: 0x%x
+%s +
+%s: SBL, SBL2 partition are diffierent size, check your bml device node name
+Both partition has valid or invalid signature
+Valid Partition-%s, Update Partition-%s
+Siginfo error partition $s (0x%x, 0x%x)
mark_common_recovery
+clear_dualpartition_signature
+write_dualpartition_signature
find_valid_partition
check_dualpartition_validation
-ram_write_block
-ram_read_block
-nand_write_block
-nand_read_block
bmldevice_get_size
Image size is bigger than partition!
reading NAND page
BML_UNLOCK_ALL
writing NAND page
6,1,14,1
+RB_Progress
+%s: (%lu %%)
+RB_GetDelta
+%s: offset 0x%lx(%ld), size 0x%lx(%ld)
+%s: open file %s failed.
+%s: error in read size
RB_GetBlockSize
%s: returning 0x%x (%d)
+RB_ReadImage
+%s: node-%s (%lx %lx)
+RB_WriteBlock
+%s: node-%s (%lx %x)
RB_ReadBackupBlock
-UA/(%s): %s: offset 0x%lx(%ld), size 0x%lx(%ld)
-UA/ERROR(%s) open file %s failed.
-UA/ open %s file success
-UA/ERROR(%s) error in read size
+%s: offset 0x%lx(%ld), size 0x%lx(%ld)
+%s: open file %s failed.
+%s: error in read size
RB_WriteBackupBlock
-UA/(%s): offset 0x%lx(%ld), size 0x%lx(%ld)
-UA/ERROR(%s) error in write size
+%s: error in write size
+RB_ImageUpdateCommon
+uPartitionName[%s]
+%s: pCustomerPartData.updated = %d, rest = %d
RB_ImageUpdateMain
-UA/(%s): ++
-UA/(%s) uPartitionName[%s]
-UA/(%s) pCustomerPartData.updated = %d, rest = %d
-UA/(%s): -- ret=%d
-RB_UpdateImage
-UA/(%s): Delta file name-%s
+%s: backup_file is %s
+%s: size of %s(%s) is %d bytes
+RB_ImageUpdateDualPartition
+%s: backup file(%s) / Valid Partition(%s) / Update Partition(%s)
+%s : RB Image Update Fail
+%s : RB Image Update Done %s
pDeviceDatum.pFirstPartitionData->partition_name: %s
pDeviceDatum.pFirstPartitionData->partition_type: %d
pDeviceDatum.pFirstPartitionData->file_system_type: %d
-UA/(%s) return value from RB_vRM_Update: 0x%x
+return value from RB_vRM_Update: 0x%x
unicode_to_char
%s : %s
RecursiveFolderCreater
@@ -726,8 +680,7 @@
failed chown %d
success chown %d
RB_FSUpdateMain
-UA/(%s) Partition name(%s), mount point(%s)
-UA/(%s) pCustomerPartData.updated = %ld, rest = %ld
+%s: pCustomerPartData.updated = %ld, rest = %ld
pDeviceDatum.pFirstPartitionData->partition_name: %s
pDeviceDatum.pFirstPartitionData->partition_type: %d
pDeviceDatum.pFirstPartitionData->file_system_type: %d
@@ -741,9 +694,9 @@
cable as possible.
System updated &
reboot now
-gui_progress
-UA/(%s): ++ uPercent(%d%), gv_delta_count=(%ld)
-UA/(%s): -- Print Percent(%d%)
+Update is ok.
+Update is failed.
+Restoring...
%3d %%
lcd_init
%s(%d): start!
@@ -962,12 +915,6 @@
insufficient memory
buffer error
incompatible version
-RB_Progress
-%s: (%lu %%)
-RB_GetDelta
-%s: offset 0x%lx(%ld), size 0x%lx(%ld)
-%s: open file %s failed.
-%s: error in read size
Pure virtual function called. Are you calling virtual methods from a destructor?
libc-abort
abort() called in pid %d
@@ -1120,6 +1067,7 @@
/dev/log/main
/dev/log/radio
/proc/self/exe
+unknown
/dev/urandom
stack corruption detected: aborted
ANDROID_PROPERTY_WORKSPACE
Whilst we're talking about retrieving information from binaries...
Does anyone know any good disassembly tools. I managed to compile objdump for ARM (ELF) and run it on the Galaxy S secondary bootloader but it only partially works. It doesn't look like it is handling the binary layout correctly. It's unsure how much of the binary is data and how much is actual instructions so it ends up converting the whole thing to instructions (most of which are obviously bogus).
Benjamin Dobell said:
Whilst we're talking about retrieving information from binaries...
Does anyone know any good disassembly tools. I managed to compile objdump for ARM (ELF) and run it on the Galaxy S secondary bootloader but it only partially works. It doesn't look like it is handling the binary layout correctly. It's unsure how much of the binary is data and how much is actual instructions so it ends up converting the whole thing to instructions (most of which are obviously bogus).
Click to expand...
Click to collapse
Under Linux i use the minimalist tool named "strings". You can learn so much just by reading strings extracted ^^.
Otherwise you have IDA Pro (Windows), which is very powerful.
Benjamin, like you i found objdump quite challenging to use.. and.. not that fun.
supercurio said:
Under Linux i use the minimalist tool named "strings". You can learn so much just by reading strings extracted ^^.
Otherwise you have IDA Pro (Windows), which is very powerful.
Benjamin, like you i found objdump quite challenging to use.. and.. not that fun.
Click to expand...
Click to collapse
Unfortunately IDA Pro doesn't seem to work either. IDA Pro Free doesn't support ARM at all and I tried with IDA Pro Advanced but it seemed to have similar issues to objdump, it couldn't determine the entry point etc.
If I could just get the assembler with comments next to it that indicate which pieces of data (strings in particular) are being referenced that would make my day.
Do you think Sbl.bin is a single unique binary ?
Considering everything that this Second Boot Loader is able to do, i would not be surprised if it's more complex than that.
Anyway I can't say much more about the tools, i'm just a rookie hacker
supercurio said:
Do you think Sbl.bin is a single unique binary ?
Considering everything that this Second Boot Loader is able to do, i would not be surprised if it's more complex than that.
Click to expand...
Click to collapse
It wouldn't be a very reliable boot loader if it depended on other binaries (other than data passed to it by the primary boot loader). However the information I'm after, the Loke protocol, is definitely in there cause I can see the handshake strings I send and receive with Heimdall.
working this into SRE RIGHT NOW!!!!
--edit
scripted, and working
release coming soon!!
designgears said:
working this into SRE RIGHT NOW!!!!
Click to expand...
Click to collapse
Nice
Remember being EXTRA careful manipulating raw bml partitions. You can easily brick your phone for good writing bad data in place of first and second bootloader.
NON-RECOVERABLE
please say that to every potential redbend_ua users
This was the required warning, now enjoy
supercurio said:
Nice
Remember being EXTRA careful manipulating raw bml partition. You can easily
brick your phone for good writing bad data in place of first and second bootloader.
NON-RECOVERABLE
please say that to every potential redbend_ua users
This was the required warning, now enjoy
Click to expand...
Click to collapse
I have borked bml17 before.. was able to go into download and restore stock.

Heimdall (Cross-Platform Flashing Tool) - Galaxy Tab?

I'm the creator of Heimdall the cross platform Galaxy S flashing tool. I was wondering if any one has attempted to flash a Galaxy Tab using my tool?
I suspect that the protocol for flashing the Galaxy Tab is identical. However, I don't have access to a Galaxy Tab so I'm unable to test myself. I would love to add the Galaxy Tab to the list of officially supported devices if someone can confirm it works.
EDIT: Just realised I never updated this post. Heimdall has officially supported the Galaxy Tab for a while now.
I might be able to do it if I find some better firmware to flash. Not sure yet.
Sent from my SCH-I800 using XDA App
I'll give it a try later today. I'm a Linux zealot.
Install notes for Linux + a question
sorry -- wrong thread. No clue how to delete, but I don't want to cross-post so just ignore this.
I compiled and tried using it to flash a modem.bin, but got an error. Heres the console output:
Code:
$ heimdall flash --pit P1_20100909.pit --modem modem.bin
Heimdall, Copyright (c) 2010, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Claiming interface... Failed. Attempting to detach driver...
Claiming interface again... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success
Unexpected device info response!
Expected: 180 or 0
Received:3
Ending session...
Rebooting device...
Re-attaching kernel driver...
rotohammer, thanks for that. It seems as the initialisation process might be slightly different for the Galaxy Tab. Unfortunately the spot where it failed is the exact spot in the protocol that I have basically no clue about. The Galaxy S sends either 180 or 0, which is perhaps some sort of flags indicating the state of the device. Technically the flash could continue past there regardless of the value received but it's a bit of a safety net feature to stop right away.
I'll see if I can get my hands on a Galaxy Tab so I can get Heimdall working for Galaxy Tab users as well.
Works great
For those of you interested, I've modified the Heimdall source on Linux to accept the device info value of 3 and I have successfully flashed 2 different full firmwares on my T-Mobile Tab, as well as many individual files. It works much faster than Odin, and a lot less flaky. I let Benjamin know so he can include support in an upcoming release.
Thanks for the good work, Ben and Roto
Can Heimdall dump partititions from flash for backup?
Technomancer said:
Can Heimdall dump partititions from flash for backup?
Click to expand...
Click to collapse
It can dump, but the dumps, just like those from Odin, aren't very useful. Its a limitation on the exporting function of the phone software.
rotohammer said:
It can dump, but the dumps, just like those from Odin, aren't very useful. Its a limitation on the exporting function of the phone software.
Click to expand...
Click to collapse
I suppose the partitions are not mounted in the "downloading" mode, so any dumps from Heimdall should be better than dumps made using dd from the shell?
rotohammer said:
It can dump, but the dumps, just like those from Odin, aren't very useful. Its a limitation on the exporting function of the phone software.
Click to expand...
Click to collapse
Hi Rotohammer!
Great work again
What did you use as chip-type and chip-id for dumping? I.e.
Code:
heimdall dump --chip-type ??? --chip-id ??? --output <filename>
Volker1 said:
What did you use as chip-type and chip-id for dumping?
Click to expand...
Click to collapse
Code:
heimdall dump --chip-type NAND --chip-id 0 --output hdump.img
I wrote a simple too to display information about PIT files (attached). The factory-installed PIT (/dev/block/bml2) on my T-Mobile US tab is identical to the one known as P1_20100909.pit and reads:
Code:
$ ./PITinfo bml2.dump
Contents of PIT file:bml2.dump
---------------------------------------------------------------------------
file magic = 0x12349876 (expected value)
Unknown data: 0x135d800 0x1 0 0x1331e17 0x2cf560
Number of partitions = 14 (not the usual value)
Partition #1
Usual content: boot.bin, the primary boot loader (low-level hardware initialization)
partition entry type: 0 0 (normal partition)
ID = 0; flags = 0; unknown: 0
size = 1 blocks of 256 * 512 bytes = 131072 B = 128 kB = 0 MB
unknown string: [........]
partition name = [IBL+PBL.........................]
file name = [boot.bin........................................................]
Partition #2
Usual content: partition information table (PIT)
partition entry type: 0 0 (normal partition)
ID = 0x1; flags = 0; unknown: 0
size = 1 blocks of 256 * 512 bytes = 131072 B = 128 kB = 0 MB
unknown string: [........]
partition name = [PIT.............................]
file name = [................................................................]
Partition #3
Usual content: efs.rfs
partition entry type: 0 0 (normal partition)
ID = 0x14; flags = 0x2 (rfs file system); unknown: 0
size = 40 blocks of 256 * 512 bytes = 5242880 B = 5120 kB = 5 MB
unknown string: [........]
partition name = [EFS.............................]
file name = [efs.rfs.........................................................]
Partition #4
Usual content: Sbl.bin, the secondary boot loader (loads linux kernel)
partition entry type: 0 0 (normal partition)
ID = 0x3; flags = 0; unknown: 0
size = 5 blocks of 256 * 512 bytes = 655360 B = 640 kB = 0 MB
unknown string: [........]
partition name = [SBL.............................]
file name = [sbl.bin.........................................................]
Partition #5
Usual content: backup of secondary boot loader
partition entry type: 0 0 (normal partition)
ID = 0x4; flags = 0; unknown: 0
size = 5 blocks of 256 * 512 bytes = 655360 B = 640 kB = 0 MB
unknown string: [........]
partition name = [SBL2............................]
file name = [sbl.bin.........................................................]
Partition #6
Usual content: param.lfs /mnt/.lfs j4fs
partition entry type: 0 0 (normal partition)
ID = 0x15; flags = 0x2 (rfs file system); unknown: 0
size = 20 blocks of 256 * 512 bytes = 2621440 B = 2560 kB = 2 MB
unknown string: [........]
partition name = [PARAM...........................]
file name = [param.lfs.......................................................]
Partition #7
Usual content: zImage, the linux kernel
partition entry type: 0 0 (normal partition)
ID = 0x6; flags = 0; unknown: 0
size = 30 blocks of 256 * 512 bytes = 3932160 B = 3840 kB = 3 MB
unknown string: [........]
partition name = [KERNEL..........................]
file name = [zImage..........................................................]
Partition #8
Usual content: recovery.bin, the backup copy of zImage/initramfs
partition entry type: 0 0 (normal partition)
ID = 0x7; flags = 0; unknown: 0
size = 30 blocks of 256 * 512 bytes = 3932160 B = 3840 kB = 3 MB
unknown string: [........]
partition name = [RECOVERY........................]
file name = [zImage..........................................................]
Partition #9
Usual content: factoryfs.rfs
partition entry type: 0 0 (normal partition)
ID = 0x16; flags = 0x2 (rfs file system); unknown: 0
size = 1320 blocks of 256 * 512 bytes = 173015040 B = 168960 kB = 165 MB
unknown string: [........]
partition name = [FACTORYFS.......................]
file name = [factoryfs.rfs...................................................]
Partition #10
Usual content: dbdata.rfs
partition entry type: 0 0 (normal partition)
ID = 0x17; flags = 0x2 (rfs file system); unknown: 0
size = 348 blocks of 256 * 512 bytes = 45613056 B = 44544 kB = 43 MB
unknown string: [........]
partition name = [DBDATAFS........................]
file name = [dbdata.rfs......................................................]
Partition #11
Usual content: cache.rfs
partition entry type: 0 0 (normal partition)
ID = 0x18; flags = 0x2 (rfs file system); unknown: 0
size = 140 blocks of 256 * 512 bytes = 18350080 B = 17920 kB = 17 MB
unknown string: [........]
partition name = [CACHE...........................]
file name = [cache.rfs.......................................................]
Partition #12
Usual content: modem.bin
partition entry type: 0 0 (normal partition)
ID = 0x8; flags = 0; unknown: 0
size = 64 blocks of 256 * 512 bytes = 8388608 B = 8192 kB = 8 MB
unknown string: [........]
partition name = [MODEM...........................]
file name = [modem.bin.......................................................]
Partition #13
Usual content: Unknown
partition entry type: 0 2 (unknown value)
ID = 0; flags = 0x1; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [l.e. .(.]
partition name = [MOVINAND..)...*...p.i.t.........]
file name = [movinand.mst........D.:.\.2.4.....P.1.\.4... .S.M.D. .i.m.a.g.e.]
Partition #14
Usual content: Unknown
partition entry type: 1 1 (past-the-end marker)
ID = 0x8; flags = 0; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [........]
partition name = [................................]
file name = [................................................................]
I want to flash the Euro firmware (I'm back in Europe right now) by flashing P1000XWJJ4 (and then flash P1000XXJK5 on top). The P1_add_hidden.pit reads:
Code:
$ ./PITinfo P1_add_hidden.pit
Contents of PIT file:P1_add_hidden.pit
---------------------------------------------------------------------------
file magic = 0x12349876 (expected value)
Unknown data: 0x1 0 0x411e17 0x12fae0 0x43d800
Number of partitions = 15 (not the usual value)
Partition #1
Usual content: boot.bin, the primary boot loader (low-level hardware initialization)
partition entry type: 0 0 (normal partition)
ID = 0; flags = 0; unknown: 0
size = 1 blocks of 256 * 512 bytes = 131072 B = 128 kB = 0 MB
unknown string: [........]
partition name = [IBL+PBL.........................]
file name = [boot.bin........................................................]
Partition #2
Usual content: partition information table (PIT)
partition entry type: 0 0 (normal partition)
ID = 0x1; flags = 0; unknown: 0
size = 1 blocks of 256 * 512 bytes = 131072 B = 128 kB = 0 MB
unknown string: [........]
partition name = [PIT.............................]
file name = [................................................................]
Partition #3
Usual content: efs.rfs
partition entry type: 0 0 (normal partition)
ID = 0x14; flags = 0x2 (rfs file system); unknown: 0
size = 40 blocks of 256 * 512 bytes = 5242880 B = 5120 kB = 5 MB
unknown string: [........]
partition name = [EFS.............................]
file name = [efs.rfs.........................................................]
Partition #4
Usual content: Sbl.bin, the secondary boot loader (loads linux kernel)
partition entry type: 0 0 (normal partition)
ID = 0x3; flags = 0; unknown: 0
size = 5 blocks of 256 * 512 bytes = 655360 B = 640 kB = 0 MB
unknown string: [........]
partition name = [SBL.............................]
file name = [sbl.bin.........................................................]
Partition #5
Usual content: backup of secondary boot loader
partition entry type: 0 0 (normal partition)
ID = 0x4; flags = 0; unknown: 0
size = 5 blocks of 256 * 512 bytes = 655360 B = 640 kB = 0 MB
unknown string: [........]
partition name = [SBL2............................]
file name = [sbl.bin.........................................................]
Partition #6
Usual content: param.lfs /mnt/.lfs j4fs
partition entry type: 0 0 (normal partition)
ID = 0x15; flags = 0x2 (rfs file system); unknown: 0
size = 20 blocks of 256 * 512 bytes = 2621440 B = 2560 kB = 2 MB
unknown string: [........]
partition name = [PARAM...........................]
file name = [param.lfs.......................................................]
Partition #7
Usual content: zImage, the linux kernel
partition entry type: 0 0 (normal partition)
ID = 0x6; flags = 0; unknown: 0
size = 30 blocks of 256 * 512 bytes = 3932160 B = 3840 kB = 3 MB
unknown string: [........]
partition name = [KERNEL..........................]
file name = [zImage..........................................................]
Partition #8
Usual content: recovery.bin, the backup copy of zImage/initramfs
partition entry type: 0 0 (normal partition)
ID = 0x7; flags = 0; unknown: 0
size = 30 blocks of 256 * 512 bytes = 3932160 B = 3840 kB = 3 MB
unknown string: [........]
partition name = [RECOVERY........................]
file name = [zImage..........................................................]
Partition #9
Usual content: factoryfs.rfs
partition entry type: 0 0 (normal partition)
ID = 0x16; flags = 0x2 (rfs file system); unknown: 0
size = 1320 blocks of 256 * 512 bytes = 173015040 B = 168960 kB = 165 MB
unknown string: [........]
partition name = [FACTORYFS.......................]
file name = [factoryfs.rfs...................................................]
Partition #10
Usual content: dbdata.rfs
partition entry type: 0 0 (normal partition)
ID = 0x17; flags = 0x2 (rfs file system); unknown: 0
size = 348 blocks of 256 * 512 bytes = 45613056 B = 44544 kB = 43 MB
unknown string: [........]
partition name = [DBDATAFS........................]
file name = [dbdata.rfs......................................................]
Partition #11
Usual content: cache.rfs
partition entry type: 0 0 (normal partition)
ID = 0x18; flags = 0x2 (rfs file system); unknown: 0
size = 140 blocks of 256 * 512 bytes = 18350080 B = 17920 kB = 17 MB
unknown string: [........]
partition name = [CACHE...........................]
file name = [cache.rfs.......................................................]
Partition #12
Usual content: modem.bin
partition entry type: 0 0 (normal partition)
ID = 0x8; flags = 0; unknown: 0
size = 64 blocks of 256 * 512 bytes = 8388608 B = 8192 kB = 8 MB
unknown string: [........]
partition name = [MODEM...........................]
file name = [modem.bin.......................................................]
Partition #13
Usual content: Unknown
partition entry type: 0 2 (unknown value)
ID = 0x3; flags = 0x1; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [l.e. .(.]
partition name = [HIDDEN.D..)...*...p.i.t.........]
file name = [hidden.rfs.t........D.:.\.2.4.....P.1.\.4... .S.M.D. .i.m.a.g.e.]
Partition #14
Usual content: Unknown
partition entry type: 1 1 (past-the-end marker)
ID = 0x8; flags = 0; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [........]
partition name = [................................]
file name = [................................................................]
Partition #15
Usual content: Unknown
partition entry type: 0 2 (unknown value)
ID = 0; flags = 0x1; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [........]
partition name = [MOVINAND........................]
file name = [movinand.mst....................................................]
But it seems like I can't flash movinand.mst with heimdall. Note that it is present in the P1000XWJJ4 firmware file. So I guess I'm better off going the VirtualBox->Win32->Odin route?
Compile on Mac OS X
I've just successfully compiled libusb and Heimdall on Mac OS X.
I needed to set an environment variable by hand so that the "configure" of Heimdall detected libusb:
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:$PKG_CONFIG_PATH
Oh, and of course this source code modification is necessary for the Galaxy Tab to be supported:
main.cpp line 252:
if (unknown != 180 && unknown != 0 && unknown != 3)
Disclaimer: I haven't had time to try flashing anything yet.
I finally found the courage to flash my T-Mo US tab to Euro version. I made my own Franken-rom by combining P1000XWJJ4 with P1000XXJK5. Specifically, I
1. decompressed P1000XWJJ4.rar
2. took boot.bin, Sbl.bin, and dbdata.rfs from P1000XWJJ4/P1000XWJJ4_SERJJ2_XXJID/P1000XWJJ4-REV03-ALL-CL639474.tar.md5 (a tar archive despite the wrong ending)
3. decompressed P1000XXJK5.rar
4. took zImage, cache.rfs, factoryfs.rfs, modem.bin, and param.lfs from P1000XXJK5/P1000OXAJK5.tar
5. P1_20100909.pit
Then I rebooted my tab in download mode, plugged it into my PC's USB, and then flashed
Code:
$ ./heimdall flash --pit P1_20100909.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --boot boot.bin --secondary Sbl.bin --param param.lfs --kernel zImage --modem modem.bin
Heimdall, Copyright (c) 2010, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Claiming interface... Failed. Attempting to detach driver...
Claiming interface again... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success
Downloading device's PIT file...
PIT file download sucessful
Uploading factory filesytem
Factory filesytem upload successful
Uploading cache
Cache upload successful
Uploading data database
Data database upload successful
Uploading primary bootloader
Primary bootloader upload successful
Uploading secondary bootloader
Secondary bootloader upload successful
Uploading param.lfs
param.lfs upload successful
Uploading kernel
Kernel upload successful
Uploading modem
Modem upload successful
Ending session...
Rebooting device...
Re-attaching kernel driver...
I had my German SIM card in and after some booting I ended up with a perfectly working German-localized Euro tab. Switching the language back to US Englisch works fine, too.
Volker1 said:
But it seems like I can't flash movinand.mst with heimdall. Note that it is present in the P1000XWJJ4 firmware file.
Click to expand...
Click to collapse
It is also present in JK2. So I guess in the end you decided not to flash movinand.mst, right ? Unless you used Odin and Heimdall ?
daniel.weck said:
It is also present in JK2. So I guess in the end you decided not to flash movinand.mst, right ? Unless you used Odin and Heimdall ?
Click to expand...
Click to collapse
Alright it looks like you guys have found one more file that Heimdall is technically capable of flashing but doesn't implement. I presume I'm missing quite a few files that the protocol supports, at least that's what the following list of utilised file identifiers would seem to indicate:
Code:
enum
{
kFilePrimaryBootloader = 0x00,
kFileSecondaryBootloader = 0x03,
kFileKernel = 0x06,
kFileParamLfs = 0x15,
kFileFactoryFilesystem = 0x16,
kFileDatabaseData = 0x17,
kFileCache = 0x18
};
I can easily add support for movinand.mst if I can find out what file identifier it uses. Unfortunately I don't have a Galaxy Tab and I need access to one in order to find out.
It's zero, if we trust the output of the PIT reader utility:
http://forum.xda-developers.com/showpost.php?p=9471190&postcount=14
Benjamin Dobell said:
Alright it looks like you guys have found one more file that Heimdall is technically capable of flashing but doesn't implement. I presume I'm missing quite a few files that the protocol supports, at least that's what the following list of utilised file identifiers would seem to indicate:
Code:
enum
{
kFilePrimaryBootloader = 0x00,
kFileSecondaryBootloader = 0x03,
kFileKernel = 0x06,
kFileParamLfs = 0x15,
kFileFactoryFilesystem = 0x16,
kFileDatabaseData = 0x17,
kFileCache = 0x18
};
I can easily add support for movinand.mst if I can find out what file identifier it uses. Unfortunately I don't have a Galaxy Tab and I need access to one in order to find out.
Click to expand...
Click to collapse
Well 0 is the primary bootloader, so right now I'm not trusting it.
Does anyone have any idea what the contents of movinand.mst is? Because I just figured out how to flash the recovery partition directly.
EDIT: And the EFS.

Serial cable instead USB ? UART...

As I'm new to Samsung handsets...
Someone tried to play with serial cable and Qualcomm Tools like Memory Debug for instance?
Download Mode not allow USB Diag for Qualcomm... only Samsung Modem is still alive in Download Mode. So Question is. If serial cable, maybe chance to dump something as you can port to UART...
Best Regards
delete.......
I use usb->serial-ttl 3.3V converter with 528K resistor on pins 4-5 for outputing diag message. And you need JIG with 301K resistor for entering to download mode.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=12689198&postcount=181
Thanx for this info, but tooo difficult for me to understand.
Please help to make such cable for research... or maybe their are existing cables to buy?
I need something like this:
http://www.badanation.de/topic.php?t=1616&page=fst_unread&highlight=widerstand
Such Pictures would be nice:
http://h-3.abload.de/img/p1000660eei7.jpg
I need FULL Pinout please for S8500.
Thanx in advance.
Best Regards
You mean cable/plug for enter download mode? You can buy it. For example in Poland I can buy this for 12 zlotys = 3 euro + delivery costs.
I found that, for Galaxy S, but is possible this is the same
forum.xda-developers.com/showthread.php?t=819551
I "need" alternate cable for communication between PC and S8500.
Also FULL Pinout is welcome.
Best Regards
http://forum.xda-developers.com/showthread.php?t=820275
Here seems few infos... maybe also work for S8500.
Best Regards
After I saw successfully log from srg.mstr.
Thank you very much.
http://forum.xda-developers.com/showpost.php?p=13426392&postcount=183
Less then 1 Euro for male Connector:
http://www.conrad.de/ce/de/product/733923/MICRO-USB-STECKER-TYP-B-5POL/SHOP_AREA_40306
So I will buy few Connectors...
Now I will make checklist for other parts and prices. As I have no cables at home to cut...
Best Regards
TX<-->2
RX<-->3
GND<-->5
resistor between 4<-->5
http://forum.xda-developers.com/showpost.php?p=13293404&postcount=174
Will try to make such cable this year... in 2013 really.
Checklist...
http://www.conrad.de/ce/de/product/...Kabelmontage-ohne-Gehaeuse-BKL-Electronic-Inh
.
.
.
Best Regards
Will try to make such cable this year...
Click to expand...
Click to collapse
Uupsi, only 2 months left... but I have found other way for Bootlog...
via JTAG RAM dump... something above 0x40000000...
Looks like this:
http://forum.xda-developers.com/showpost.php?p=47037737&postcount=34
Best Regards
2013 soon over... but Mission UART is not over...
New attempt... for 2014...
It seems now "cheap" USB stuff available... based on PL2303... symbolic Photo attached...
According to this Pic...
http://forum.xda-developers.com/showpost.php?p=13426392&postcount=183
Other idea is to solder direct to RX TX and GND on PCB... instead resistor...
Maybe...
Best Regards
Short tested with 3 wires soldered direct to RX TX and Ground under battery/label...
Hmm... first test failed with WinComm... maybe my settings are wrong, will try other Tool for Logging...
Best Regards
Btw...
Never seen S5250 or S8600 user trying to capture data over UART...
:silly:
Code:
[PAM: ] OneNAND physical base address : 0xb0000000
[PAM: ] OneNAND virtual base address : 0xb0000000
[PAM: ] FSR_PAM_InitNANDController Success!!
[PAM: ] --FSR_PAM_Init
[BM : ] FSR_BML_GetFullPartI() is completed
[BM : ] stPartI.nNumOfPartEntry : 7
[BM : ] 1th PartEntrt(nAttr:0x1002)(nID:0x0)
[BM : ] [1th] pPEntry->n1stVun : 1
[BM : ] [1th] pPEntry->nNumOfUnits : 7
[BM : ] [1th] pPEntry->nLoadAddr : 0x0
+-------------------------------+
| Bootloader Shadowing FINISHED |
+-------------------------------+
Launch Image at 0x42480000
[BOOT_V1.0 (May 28 2010, 21:22:23)]
SelectBootingMode: H/W...0xe.
[BOOT] ARMCLK: 400000 KHz, MSYSHCLK 200000 KHz,MSYSPCLK: 100000 KHz, [BOOT] DSYSHCLK 166750 KHz,DSYSPCLK: 83375 KHz,PSYSHCLK: 133400 KHz, PSYSPCLK: 66700 KHz,SYSCON_A2M: 200000 KHz
+++FIMD_Drv_INITIALIZE
FIMD_Drv_ChangeMode: MDNIE_MODE
Frame Rate:62 SCLK_FIMD:133400 kHz ClkDiv:4
S6E63M0 : LDI_Pentile_Set_Change Pentile_Value =6c
---FIMD_Drv_INITIALIZE
---FIMD_Drv_SetWinOnOff(WIN4:1)
LCD initialize Finished
Flash_Unlock failed
Poweron status - c0
FSA9480 0x03 Register = 0
FSA9480 0x0A Register = 0
FSA9480 0x0B Register = 0
FSA9480 0x07 Register = 1f
Used WinComm as Tool...
Stupid me not realized that TX connect to RX and RX to TX... :cyclops:
Best Regards
Code:
[PAM: ] ++FSR_PAM_Init
[PAM: ] OneNAND physical base address : 0xb0000000
[PAM: ] OneNAND virtual base address : 0xb0000000
[PAM: ] FSR_PAM_InitNANDController Success!!
[PAM: ] --FSR_PAM_Init
bl3_info_block 1 and 2 not found, Load BL3
+-------------------------------+
| Bootloader Shadowing FINISHED |
+-------------------------------+
Launch Image at 0x42080000
[BOOT_V1.0 (Jan 5 2012, 19:08:14)]
SelectBootingMode: H/W...0xe.
[BOOT] ARMCLK: 400000 KHz, MSYSHCLK 200000 KHz,MSYSPCLK: 100000 KHz, [BOOT] DSYSHCLK 166750 KHz,DSYSPCLK: 83375 KHz,PSYSHCLK: 133400 KHz, PSYSPCLK: 66700 KHz,SYSCON_A2M: 200000 KHz
+++FIMD_Drv_INITIALIZE
FIMD_Drv_ChangeMode: MDNIE_MODE
Frame Rate:62 SCLK_FIMD:133400 kHz ClkDiv:4
S6E63M0 : LDI_Pentile_Set_Change Pentile_Value =6c
---FIMD_Drv_INITIALIZE
---FIMD_Drv_SetWinOnOff(WIN4:1)
LCD initialize Finished
Flash_Unlock failed
Poweron status - 0
FSA9480 0x03 Register = 0
FSA9480 0x0A Register = 4
FSA9480 0x0B Register = 0
FSA9480 0x07 Register = 1f
Display_LSI_Boot : disp_Main_Clean
Display_LSI_Boot : disp_Main_Clean_All
Display_LSI_Boot : disp_Main_Dload_Update
Display_LSI_Boot : disp_dimming_backlight
LDI_S6E63M0_Set_Brightness is Return (Level: 1)
Display_LSI_Boot : disp_dimming_backlight
Display_LSI_Boot : disp_Main_Dload_Update
Display_LSI_Boot : disp_Main_Dload_Message
+SDHC_Open(Ch0)
univ_SD_MEM_PowerOnDevice() : Power On
univ_SD_MEM_PowerOnDevice(ch0) : MASSMEMORY_EN Power On
[SDHC] MPLL source clock from SYSCON : 667000000Hz
[SDHC] SDHC(ch0) source clock from SYSCON : 47642000Hz
[SDHC] SDHC(ch0) Operating Clock : 372203Hz
[SDHC][MMC]byte mode
SD_MEM_Phy_CMD2(ch0) : CID(127~0) : 0x150100, 0x4d324731, 0x44441655, 0x3c7886d
SD_MEM_Phy_Check_moviNAND_Version(ch0) : PRV - 0x16
MMC_Spec = 4
----------------CSD Version 1.0--------in low level-------------
channel: [0]
One Block Size: [512]Byte
Total card Block Count = [4014080]
Total card Capacity Size = [1960]MB
---------------------------------------------------
SD_HostCtrl_IssueCommand[ch0] not SDclk off, cmd13, SD_CLK_CTRL:0x400f
SD_MEM_Phy_TransferState(ch0) :High: Tx : SD_FeedBackClock_BasicDelay
SD_MEM_Phy_TransferState(ch0) :High: Rx : SD_FeedBackClock_InverterDelay
[SDHC] MPLL source clock from SYSCON : 667000000Hz
[SDHC] SDHC(ch0) source clock from SYSCON : 47642000Hz
[SDHC] SDHC(ch0) Operating Clock : 47642000Hz
SD_HostCtrl_IssueCommand[ch0] not SDclk off, cmd13, SD_CLK_CTRL:0xf
SD_HostCtrl_IssueCommand[ch0] not SDclk off, cmd13, SD_CLK_CTRL:0xf
-SDHC_Open(Ch0)
Display_LSI_Boot : disp_Main_Dload_Update
Display_LSI_Boot : disp_Main_Dload_Message
Display_LSI_Boot : disp_Main_Dload_Update
Display_LSI_Boot : disp_Main_Dload_Message
Display_LSI_Boot : disp_Main_Dload_Update
Display_LSI_Boot : disp_Main_Dload_Message
Display_LSI_Boot : disp_Main_Dload_Update
Display_LSI_Boot : disp_Main_Dload_Message
Display_LSI_Boot : disp_Main_Dload_Update
Display_LSI_Boot : disp_Main_Dload_Message
Display_LSI_Boot : disp_Main_Dload_Update
Display_LSI_Boot : disp_Main_Dload_Message
Display_LSI_Boot : disp_Main_Dload_Update
Display_LSI_Boot : disp_Main_Dload_Message
Display_LSI_Boot : disp_Main_Dload_Update
Display_LSI_Boot : disp_Main_Dload_Message
Display_LSI_Boot : disp_Main_Dload_Update
Display_LSI_Boot : disp_Main_Dload_Message
DRV_modem_reset!!!!!!!!!!!!!!!!!
DRV_Send_DBL!!!!!!!!!!!!!!!!!
[DLOAD] Download Completed !!!
DRV_Wait_ModemInit!!!!!!!!!!!!!!!!!
DRV_CopyQSCBootBinary!!!!!!!!!!!!!!!!!
DRV_Send_BootBinaryCopyComplete!!!!!!!!!!!!!!!!!
DRV_Modem_BootingStart retry count = 0.
Display_LSI_Boot : disp_Main_Dload_Update
Display_LSI_Boot : disp_Main_Dload_Message
Display_LSI_Boot : disp_Main_Dload_Update
Display_LSI_Boot : disp_Main_Dload_Message
Display_LSI_Boot : disp_Main_Dload_Update
Display_LSI_Boot : disp_Main_Dload_Message
Display_LSI_Boot : disp_Main_Dload_Update
Display_LSI_Boot : disp_Main_Dload_Message
Display_LSI_Boot : disp_Main_Dload_Update
Display_LSI_Boot : disp_Main_Dload_Message
Display_LSI_Boot : disp_Main_Dload_Update
Display_LSI_Boot : disp_Main_Dload_Message
Display_LSI_Boot : disp_Main_Dload_Update
Display_LSI_Boot : disp_Main_Dload_Message
Display_LSI_Boot : disp_Main_Dload_Update
Display_LSI_Boot : disp_Main_Dload_Message
Display_LSI_Boot : disp_Main_Dload_Update
Display_LSI_Boot : disp_Main_Dload_Message
Display_LSI_Boot : disp_Main_Dload_Update
Display_LSI_Boot : disp_Main_Dload_Message
Uncompressing Linux... done, booting the kernel.
<6>Initializing cgroup subsys cpu
<5>Linux version 3.0.86-g5b25f8d ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 PREEMPT Tue Nov 5 22:35:53 CET 2013
CPU: ARMv7 Processor [412fc082] revision 2 (ARMv7), cr=10c53c7d
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: wave
Memory policy: ECC disabled, Data cache writeback
CPU S5PV210/S5PC110 (id 0x43110222)
<7>s5pv210_init_clocks: initializing clocks
<6>S3C24XX Clocks, Copyright 2004 Simtec Electronics
<4>s3c24xx_register_clock: new clock sclk_csis, id -1, dev (null) uses same enable bit as mout_csis, id -1, dev (null)
<4>s3c24xx_register_clock: new clock lcd, id -1, dev (null) uses same enable bit as sclk_fimd, id -1, dev (null)
<4>s3c24xx_register_clock: new clock mfc, id -1, dev (null) uses same enable bit as sclk_mfc, id -1, dev (null)
<4>s3c24xx_register_clock: new clock iis, id 0, dev (null) uses same enable bit as i2s_v50, id 0, dev (null)
<7>s5pv210_setup_clocks: registering clocks
<7>s5pv210_setup_clocks: clkdiv0 = 14131330, clkdiv1 = 00400400
<7>s5pv210_setup_clocks: xtal is 24000000
<6>S5PV210: PLL settings, A=800000000, M=667000000, E=80000000 V=54000000<6>S5PV210: ARMCLK=800000000, HCLKM=200000000, HCLKD=166750000
HCLKP=133400000, PCLKM=100000000, PCLKD=83375000, PCLKP=66700000
<6>sclk_dmc: source is mout_mpll (1), rate is 166750000
<6>sclk_onenand: source is hclk_dsys (1), rate is 83375000
<6>sclk: source is mout_mpll (6), rate is 133400000
<6>sclk: source is mout_mpll (6), rate is 66700000
<6>sclk: source is mout_mpll (6), rate is 66700000
<6>sclk: source is mout_mpll (6), rate is 66700000
<6>sclk_mixer: source is sclk_dac (0), rate is 54000000
<6>sclk_fimc: source is ext_xtal (0), rate is 24000000
<6>sclk_fimc: source is ext_xtal (0), rate is 24000000
<6>sclk_fimc: source is ext_xtal (0), rate is 24000000
<6>sclk_cam: source is xusbxti (1), rate is 24000000
<6>sclk_cam: source is ext_xtal (0), rate is 24000000
<6>sclk_fimd: source is mout_mpll (6), rate is 133400000
<6>sclk_mmc: source is mout_mpll (6), rate is 51307692
<6>sclk_mmc: source is mout_mpll (6), rate is 47642857
<6>sclk_mmc: source is mout_mpll (6), rate is 47642857
<6>sclk_mmc: source is mout_mpll (6), rate is 47642857
<6>sclk_mfc: source is sclk_a2m (0), rate is 200000000
<6>sclk_fimg2d: source is sclk_a2m (0), rate is 200000000
<6>sclk: source is mout_mpll (1), rate is 66700000
<6>sclk_csis: source is ext_xtal (0), rate is 24000000
<6>sclk_spi: source is mout_epll (7), rate is 80000000
<6>sclk_spi: source is mout_epll (7), rate is 80000000
<6>sclk_pwi: source is ext_xtal (0), rate is 24000000
<6>sclk_pwm: source is ext_xtal (0), rate is 24000000
<6>sclk_mdnie: source is mout_mpll (6), rate is 166750000
<6>sclk_mdnie_pwm: source is ext_xtal (0), rate is 24000000
<6>s5p: 11534336 bytes system memory reserved for mfc at 0x24500000, 0-bank base(0x24500000)
<6>s5p: 11534336 bytes system memory reserved for mfc at 0x4f3f4000, 1-bank base(0x4f3f4000)
<6>s5p: 11534336 bytes system memory reserved for fimc0 at 0x4e8f4000, 1-bank base(0x4e8f4000)
<6>s5p: 11534336 bytes system memory reserved for fimc2 at 0x4ddf4000, 1-bank base(0x4ddf4000)
<6>s5p: 4194304 bytes system memory reserved for jpeg at 0x24500000, 0-bank base(0x24500000)
<6>s5p: 7680000 bytes system memory reserved for fimd at 0x4d6a1000, 1-bank base(0x4d6a1000)
<7>On node 0 totalpages: 72621
<7> Normal zone: 1534 pages used for memmap
<7> Normal zone: 0 pages reserved
<7> Normal zone: 71087 pages, LIFO batch:15
<7>pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
<7>pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 71087
<5>Kernel command line: init=/init loglevel=4
<6>PID hash table entries: 2048 (order: 1, 8192 bytes)
<6>Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
<6>Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
<6>Memory: 69MB 214MB 0MB = 283MB total
<5>Memory: 272496k/325052k available, 17988k reserved, 0K highmem
<5>Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xff000000 - 0xffe00000 ( 14 MB)
vmalloc : 0xf0000000 - 0xfc000000 ( 192 MB)
lowmem : 0xc0000000 - 0xeff00000 ( 767 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.init : 0xc0008000 - 0xc0617000 (6204 kB)
.text : 0xc0617000 - 0xc0ce8000 (6980 kB)
.data : 0xc0ce8000 - 0xc0d34880 ( 307 kB)
.bss : 0xc0d348a4 - 0xc0e76ad8 (1289 kB)
<6>SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
<6>Preemptible hierarchical RCU implementation.
<6>NR_IRQS:339
<6>VIC @fc000000: id 0x00041192, vendor 0x41
<6>VIC @fc010000: id 0x00041192, vendor 0x41
<6>VIC @fc020000: id 0x00041192, vendor 0x41
<6>VIC @fc030000: id 0x00041192, vendor 0x41
<6>mult[140737]
<6>max_delta_ns[2937815369]
<6>min_delta_ns[30517]
<6>rate[32768]
<6>HZ[256]
<6>Console: colour dummy device 80x30
<6>console [tty0] enabled
<6>Calibrating delay loop... <c>795.12 BogoMIPS (lpj=1554432)
<6>pid_max: default: 32768 minimum: 301
<6>Mount-cache hash table entries: 512
<6>Initializing cgroup subsys debug
<6>Initializing cgroup subsys cpuacct
<6>Initializing cgroup subsys freezer
<6>CPU: Testing write buffer coherency: ok
<6>hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available
<6>print_constraints: dummy:
<6>NET: Registered protocol family 16
<6>ram_console: got buffer at 4ff00400, size fec00
<6>ram_console: uncorrectable error in header
<6>ram_console: no valid data in buffer (sig = 0xfeffdfff)
<6>console [ram-1] enabled
<6>S5PC110 Hardware version : EVT1
<6>HWREV is 0xf
S3C Power Management, Copyright 2004 Simtec Electronics
<6>pmstats at 4ffff000
<3>invalid media device
<3>invalid media device
<6>hw-breakpoint: debug architecture 0x4 unsupported.
<6>S5PV210: Initializing architecture
<6>s3c24xx-pwm s3c24xx-pwm.0: tin at 66700000, tdiv at 66700000, tin=divclk, base 0
<6>s3c24xx-pwm s3c24xx-pwm.1: tin at 66700000, tdiv at 66700000, tin=divclk, base 8
<6>s3c24xx-pwm s3c24xx-pwm.2: tin at 66700000, tdiv at 66700000, tin=divclk, base 12
<6>s3c24xx-pwm s3c24xx-pwm.3: tin at 66700000, tdiv at 66700000, tin=divclk, base 16
<6>print_constraints: pd_audio_supply: 5000 mV normal
<6>print_constraints: pd_cam_supply: 5000 mV normal
<6>print_constraints: pd_tv_supply: 5000 mV normal
<6>print_constraints: pd_lcd_supply: 5000 mV normal
<6>print_constraints: pd_g3d_supply: 5000 mV normal
<6>print_constraints: pd_mfc_supply: 5000 mV normal
<6>bio: create slab <bio-0> at 0
<5>SCSI subsystem initialized
<6>usbcore: registered new interface driver usbfs
<6>usbcore: registered new interface driver hub
<6>usbcore: registered new device driver usb
<6>i2c-gpio i2c-gpio.4: using pins 247 (SDA) and 246 (SCL)
<6>i2c-gpio i2c-gpio.5: using pins 203 (SDA) and 204 (SCL)
<3>max8998 6-0066: No interrupt base specified, no interrupts
<3>i2:10, buck2_idx:0
<6>print_constraints: VALIVE_1.2V: 1200 mV
<6>print_constraints: VUSB_1.1V: 1100 mV
<6>print_constraints: VADC_3.3V: 3300 mV
<6>print_constraints: VTF_2.8V: 2800 mV
<6>print_constraints: VLCD_1.8V: 1800 mV
<6>print_constraints: VUSB_3.3V: 3300 mV
<6>print_constraints: VCC_2.8V_PDA: 2800 mV
<6>print_constraints: CAM_AF_2.8V: 2800 mV
<6>print_constraints: CAM_SENSOR_1.2V: 1200 mV
<6>print_constraints: CAM_SENSOR_A2.8V: 2800 mV
<6>print_constraints: CAM_ISP_1.8V: 1800 mV
<6>print_constraints: CAM_ISP_HOST_2.8V: 2800 mV
<6>print_constraints: VGA_DVDD_1.8V: 1800 mV
<6>print_constraints: VCC_3.0V_LCD: 2800 <--> 3200 mV at 3200 mV
<6>print_constraints: VDD_ARM: 750 <--> 1500 mV at 1200 mV
<6>print_constraints: VDD_INT: 750 <--> 1500 mV at 1100 mV
<6>print_constraints: VCC_1.8V: 1800 mV
<6>print_constraints: CAM_ISP_CORE_1.2V: 1200 mV
<6>print_constraints: USB_VBUS_AP:
<6>print_constraints: USB_VBUS_CP:
<6>i2c-gpio i2c-gpio.6: using pins 206 (SDA) and 209 (SCL)
<6>i2c-gpio i2c-gpio.7: using pins 201 (SDA) and 202 (SCL)
<6>i2c-gpio i2c-gpio.8: using pins 42 (SDA) and 43 (SCL)
<6>i2c-gpio i2c-gpio.11: using pins 114 (SDA) and 98 (SCL)
<6>i2c-gpio i2c-gpio.12: using pins 199 (SDA) and 200 (SCL)
<6>s3c-i2c s3c2440-i2c.0: i2c-0: S3C I2C adapter
<6>s3c-i2c s3c2440-i2c.1: i2c-1: S3C I2C adapter
<6>s3c-i2c s3c2440-i2c.2: i2c-2: S3C I2C adapter
<6>Advanced Linux Sound Architecture Driver Version 1.0.24.
<6>Bluetooth: Core ver 2.16
<6>NET: Registered protocol family 31
<6>Bluetooth: HCI device and connection manager initialized
<6>Bluetooth: HCI socket layer initialized
<6>Bluetooth: L2CAP socket layer initialized
<6>Bluetooth: SCO socket layer initialized
<6>Switching to clocksource clock_source_systimer
<6>cfg80211: Calling CRDA to update world regulatory domain
<6>Switched to NOHz mode on CPU #0
<6>NET: Registered protocol family 2
<6>IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
<6>TCP established hash table entries: 16384 (order: 5, 131072 bytes)
<6>TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
<6>TCP: Hash tables configured (established 16384 bind 16384)
<6>TCP reno registered
<6>UDP hash table entries: 256 (order: 0, 4096 bytes)
<6>UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
<6>NET: Registered protocol family 1
<6>PMU: registered new PMU device of type 0
<4>clk_get: could not find clock emu_src_ck for dev s5pv210_etb_device+0x0/0x100 (etb)
<6>wake enabled for irq 165
<6>wake disabled for irq 165
<6>S5PV210 ADC driver, (c) 2010 Samsung Electronics
<6>Loaded driver for PL330 DMAC-0 s3c-pl330
<6> DBUFF-64x8bytes Num_Chans-8 Num_Peri-2 Num_Events-32
<6>Loaded driver for PL330 DMAC-1 s3c-pl330
<6> DBUFF-8x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
<6>Loaded driver for PL330 DMAC-2 s3c-pl330
<6> DBUFF-8x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
<6>ashmem: initialized
<6>ROMFS MTD (C) 2007 Red Hat, Inc.
<7>yaffs: yaffs built Nov 5 2013 22:34:00 Installing.
<6>msgmni has been set to 532
<6>io scheduler noop registered
<6>io scheduler deadline registered
<6>io scheduler row registered (default)
<6>io scheduler cfq registered
<6>io scheduler sio registered
MDNIE INIT ..........
<6>S3C MDNIE Driver, (c) 2010 Samsung Electronics
MDNIE INIT SUCCESS Addr : 0xf003c000
IELCD INIT ..........
<6>S3C IELCD Driver, (c) 2010 Samsung Electronics
IELCD INIT SUCCESS Addr : 0xf0040000
<6>s3cfb s3cfb: [fb2] dma: 0x4db06000, cpu: 0xf0400000, size: 0x002ee000
<6>FIMD src sclk = 166750000
<6>s3cfb s3cfb: pixclock adjusted from 39019 to 41979
<6>[mDNIe] mDNIe_tuning_initialize: addr(0x84), data(0x0)
<6>[mDNIe] mDNIe_tuning_initialize: addr(0x90), data(0x0)
<6>[mDNIe] mDNIe_tuning_initialize: addr(0x94), data(0xfff)
<6>[mDNIe] mDNIe_tuning_initialize: addr(0x98), data(0x5c)
<6>[mDNIe] mDNIe_tuning_initialize: addr(0x9c), data(0x10)
<6>[mDNIe] mDNIe_tuning_initialize: addr(0xac), data(0x0)
<6>[mDNIe] mDNIe_tuning_initialize: addr(0xb4), data(0x3ff)
[mDNIe] mDNIe_Set_Mode: current_mDNIe_UI(6), current_mDNIe_OutDoor_OnOff(0)
<6>s3cfb_late_resume is called
<6>FIMD src sclk = 166750000
<6>s3cfb s3cfb: pixclock adjusted from 41979 to 41979
<6>[mDNIe] mDNIe_tuning_initialize: addr(0x84), data(0x0)
<6>[mDNIe] mDNIe_tuning_initialize: addr(0x90), data(0x0)
<6>[mDNIe] mDNIe_tuning_initialize: addr(0x94), data(0xfff)
<6>[mDNIe] mDNIe_tuning_initialize: addr(0x98), data(0x5c)
<6>[mDNIe] mDNIe_tuning_initialize: addr(0x9c), data(0x10)
<6>[mDNIe] mDNIe_tuning_initialize: addr(0xac), data(0x0)
<6>[mDNIe] mDNIe_tuning_initialize: addr(0xb4), data(0x3ff)
[mDNIe] mDNIe_Set_Mode: current_mDNIe_UI(6), current_mDNIe_OutDoor_OnOff(0)
<3>panel_reset_lcd
<6>s3cfb_late_resume is complete
<6>s3cfb s3cfb: registered successfully
<6>s5pv210-uart.0: s3c2410_serial0 at MMIO 0xe2900000 (irq = 16) is a S3C6400/10
<6>s5pv210-uart.1: s3c2410_serial1 at MMIO 0xe2900400 (irq = 20) is a S3C6400/10
<6>s5pv210-uart.3: s3c2410_serial3 at MMIO 0xe2900c00 (irq = 28) is a S3C6400/10
PA FB = 0x4DB06000, bits per pixel = 32
screen width=480 height=800 va=0xedb06000 pa=0x4db06000
xres_virtual = 480, yres_virtual = 1600, xoffset = 0, yoffset = 0
fb_size=3072000
Back frameBuffer[0].VAddr=edc7d000 PAddr=4dc7d000 size=1536000
No space for NV12 video carveout
<6>brd: module loaded
<6>loop: module loaded
<6>Android kernel panic handler initialized (bind=kpanic)
<6>sec_jack_probe : Registering jack driver
<6>wake enabled for irq 38
<6>sec_jack_init_jack_state<6>sec_jack_set_micbias_state: HWREV=15, on=1
<6>handle_jack_not_inserted
<6>sec_jack_set_micbias_state: HWREV=15, on=0
<6>sec_jack_set_micbias_state: HWREV=15, on=0
<6>wake enabled for irq 167
<6>fsa9480 7-0025: dev1: 0x4, dev2: 0x0
<4>i2c-core: driver [fsa9480] using legacy suspend method
<4>i2c-core: driver [fsa9480] using legacy resume method
<6>modem_io_init done
<6>[MODEM] bp_irq() - PHONE_ACTIVE interrupt, 1 occurence
<6>wake enabled for irq 47
<6>wake enabled for irq 43
<6>modemctl probed
<6>Muxed OneNAND 512MB 1.8V 16-bit (0x50)
<6>OneNAND version = 0x013e
<7>Chip support all block unlock
<7>Chip has 4KiB pagesize
<7>Chip has cache program feature
<6>Scanning device for bad blocks
<7>onenand_bbt_wait: ecc 0xaaaa ctrl 0x0400 intr 0x8080 addr1 0x1dd addr8 0x0
<6>OneNAND eraseblock 477 is an initial bad block
<7>onenand_bbt_wait: ecc 0xaaaa ctrl 0x0400 intr 0x8080 addr1 0x6cf addr8 0x0
<6>OneNAND eraseblock 1743 is an initial bad block
<7>onenand_bbt_wait: ecc 0xaaaa ctrl 0x0400 intr 0x8080 addr1 0x73f addr8 0x0
<6>OneNAND eraseblock 1855 is an initial bad block
<6>OneNAND eraseblock 2047 is an initial bad block
<5>Creating 2 MTD partitions on "(null)":
<5>0x00001e700000-0x00001ec00000 : "nv_data"
<5>0x000003300000-0x000003600000 : "fota"
<6>tl2796: c0, b-6bea38dc, got v 2051000, factory wants 2051000
<6>tl2796: c1, b-7f519b2b, got v 2044000, factory wants 2044000
<6>tl2796: c2, b-ae797fc2, got v 1491000, factory wants 1491000
<6>tl2796_probe successfully probed
<6>PPP generic driver version 2.4.2
<6>PPP Deflate Compression module registered
<6>PPP BSD Compression module registered
<6>PPP MPPE Compression module registered
<6>NET: Registered protocol family 24
<6>tun: Universal TUN/TAP device driver, 1.6
<6>tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
<6>s3c-udc : S3C HS USB Device Controller Driver, (c) 2008-2009 Samsung Electronics
s3c-udc : version 15 March 2009 (DMA Mode)
<6>android_usb gadget: Mass Storage Function, version: 2009/09/11
<6>android_usb gadget: Number of LUNs=2
<6> lun0: LUN: removable file: (no medium)
<6> lun1: LUN: removable file: (no medium)
<6>android_usb gadget: android_usb ready
<7>Registered gadget driver 'android_usb'
<6>input: gpio-keys as /devices/platform/gpio-keys.0/input/input0
<6>input: s5pv210-keypad as /devices/platform/s5pv210-keypad/input/input1
<6>usbcore: registered new interface driver xpad
<6>usbcore: registered new interface driver usb_acecad
<6>acecad: v3.2:USB Acecad Flair tablet driver
<6>usbcore: registered new interface driver aiptek
<6>aiptek: v2.3 (May 2, 2007):Aiptek HyperPen USB Tablet Driver (Linux 2.6.x)
<6>aiptek: Bryan W. Headley/Chris Atenasio/Cedric Brun/Rene van Paassen
<6>usbcore: registered new interface driver gtco
GTCO usb driver version: 2.00.0006<6>usbcore: registered new interface driver hanwang
<6>usbcore: registered new interface driver kbtab
<6>kbtab: v0.0.2:USB KB Gear JamStudio Tablet driver
<6>usbcore: registered new interface driver wacom
<6>wacom: v1.52:USB Wacom tablet driver
<6>input: mxt224_ts_input as /devices/virtual/input/input2
<6>Atmel MXT224 2-004a: family = 0x80, variant = 0x1, version = 0x16, build = 171
<6>bma023 5-0038: bma023 found
<6>bma023 5-0038: al_version=2, ml_version=1
<6>input: accelerometer_sensor as /devices/virtual/input/input3
<3>gp2a: proximity val = 1
<6>input: proximity as /devices/virtual/input/input4
<6>input: orientation_sensor as /devices/virtual/input/input5
<6>max8998-rtc max8998-rtc: RTC CHIP NAME: max8998-rtc
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
<6>s3c-rtc s3c2410-rtc: rtc disabled, re-enabling
<6>s3c-rtc s3c2410-rtc: rtc disabled, re-enabling
<6>s3c-rtc s3c2410-rtc: rtc disabled, re-enabling
<6>s3c-rtc s3c2410-rtc: rtc disabled, re-enabling
<6>using rtc device, s3c, for alarms<6>s3c-rtc s3c2410-rtc: rtc core: registered s3c as rtc0
<6>i2c /dev entries driver
<6>lirc_dev: IR Remote Control driver registered, major 251
<6>IR NEC protocol handler initialized
<6>IR RC5(x) protocol handler initialized
<6>IR RC6 protocol handler initialized
<6>IR JVC protocol handler initialized
<6>IR Sony protocol handler initialized
<6>IR RC5 (streamzap) protocol handler initialized
<6>IR LIRC bridge handler initialized
<6>Linux video capture interface: v2.00
<6>mfc_init: <6>S5PC110 MFC Driver, (c) 2009 Samsung Electronics
<6>S3C JPEG Driver, (c) 2007 Samsung Electronics
<6>JPEG driver for S5PV210
<4>i2c-core: driver [s5p_ddc] using legacy suspend method
<4>i2c-core: driver [s5p_ddc] using legacy resume method
<4>i2c-core: driver [Si4709] using legacy suspend method
<4>i2c-core: driver [Si4709] using legacy resume method
<6>device-mapper: uevent: version 1.0.3
<6>device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: [email protected]
<6>Bluetooth: HCI UART driver ver 2.2
<6>Bluetooth: HCI H4 protocol initialized
<6>cpuidle: using governor ladder
<6>cpuidle: using governor menu
<6>sdhci: Secure Digital Host Controller Interface driver
<6>sdhci: Copyright(c) Pierre Ossman
<6>s3c-sdhci s3c-sdhci.0: clock source 0: hsmmc (133400000 Hz)
<6>s3c-sdhci s3c-sdhci.0: clock source 2: sclk_mmc (51307692 Hz)
<6>mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.0] using ADMA
<6>s3c-sdhci s3c-sdhci.1: clock source 0: hsmmc (133400000 Hz)
<6>s3c-sdhci s3c-sdhci.1: clock source 2: sclk_mmc (47642857 Hz)
<6>mmc1: SDHCI controller on samsung-hsmmc [s3c-sdhci.1] using ADMA
<6>s3c-sdhci s3c-sdhci.2: clock source 0: hsmmc (133400000 Hz)
<6>s3c-sdhci s3c-sdhci.2: clock source 2: sclk_mmc (47642857 Hz)
<6>mmc2: SDHCI controller on samsung-hsmmc [s3c-sdhci.2] using ADMA
<6>usbcore: registered new interface driver usbhid
<6>usbhid: USB HID core driver
<6>logger: created 256K log 'log_main'
<6>logger: created 256K log 'log_events'
<6>logger: created 256K log 'log_radio'
<6>logger: created 256K log 'log_system'
<6>zram: num_devices not specified. Using default: 1
<6>zram: Creating 1 devices ...
<6>WM8994 Audio Codec 0.1
wm8994_extensions: initializing driver v10
<6>s3c_idma_preallocate_buffer: VA-f00c0000 PA-C0000000 163840bytes
<6>asoc: WM8994 PAIFRX <-> samsung-i2s.0 mapping ok
<6>ALSA device list:
<6> #0: smdkc110
<6>oprofile: using arm/armv7
<6>GACT probability NOT on
<6>Mirror/redirect action on
<6>u32 classifier
<6> Actions configured
<6>Netfilter messages via NETLINK v0.30.
<6>nf_conntrack version 0.5.0 (4257 buckets, 17028 max)
<6>ctnetlink v0.93: registering with nfnetlink.
<6>NF_TPROXY: Transparent proxy support initialized, version 4.1.0
<6>NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
<6>xt_time: kernel timezone is -0000
<6>ip_tables: (C) 2000-2006 Netfilter Core Team
<6>arp_tables: (C) 2002 David S. Miller
<6>TCP cubic registered
<6>NET: Registered protocol family 10
<6>mmc0: new high speed MMC card at address 0001
<6>Mobile IPv6
<6>ip6_tables: (C) 2000-2006 Netfilter Core Team
<6>mmcblk0: mmc0:0001 M2G1DD 1.91 GiB
<6>IPv6 over IPv4 tunneling driver
<6> mmcblk0: p1 p2 p3
<6>NET: Registered protocol family 17
<6>NET: Registered protocol family 15
<6>Bluetooth: RFCOMM TTY layer initialized
<6>Bluetooth: RFCOMM socket layer initialized
<6>Bluetooth: RFCOMM ver 1.11
<6>Bluetooth: BNEP (Ethernet Emulation) ver 1.3
<6>Bluetooth: HIDP (Human Interface Emulation) ver 1.2
<6>NET: Registered protocol family 35
<6>VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2
<6>ThumbEE CPU extension supported.
<6>s5pv210_cpufreq_init: S5PV210 cpu-freq driver
<6>regulator_init_complete: pd_mfc_supply: disabling
<6>regulator_init_complete: pd_tv_supply: disabling
<6>regulator_init_complete: pd_cam_supply: disabling
## wifi_probe
wifi_set_power = 1
wifi_set_carddetect = 1
<4>mmc1: queuing unknown CIS tuple 0x80 (50 bytes)
<4>mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
<4>mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
<6>mmc1: new SDIO card at address 0001
F1 signature read @0x18000000=0x9934329
DHD: dongle ram size is set to 294912(orig 294912)
wl_create_event_handler thr:3d started
dhd_attach thr:3e started
dhd_attach thr:3f started
dhd_attach thr:40 started
Broadcom Dongle Host Driver: register interface [wlan0] MAC: 00:90:4c:11:22:33
Dongle Host Driver, version 5.90.195.104
Compiled in drivers/net/wireless/bcmdhd on Nov 5 2013 at 22:34:41
wifi_set_power = 0
=========== WLAN placed in RESET ========
<6>s3c-rtc s3c2410-rtc: rtc disabled, re-enabling
<6>s3c-rtc s3c2410-rtc: setting system clock to 2010-12-31 23:07:37 UTC (1293836857)
<6>FIMC0 registered successfully
<6>FIMC1 registered successfully
<6>FIMC2 registered successfully
<6>S5P TVOUT Driver, (c) 2010 Samsung Electronics
<4>clk_get: could not find clock mout_vpll_src for dev s5p_device_tvout+0x8/0xd8 (s5p-tvout)
<3>failed to find clock "mout_vpll_src"
<6>s5p-tvout s5p-tvout: hpd status: cable removed/not connected
<6>s5p_tv_probe TV Probing is done
<6>max8998_charger_probe : MAX8998 Charger Driver Loading
<6>max8998_charger_probe : pmic interrupt registered
<6>check_lpm_charging_mode : lpm_charging_mode(0)
<6>wake enabled for irq 39
<7>s3c_bat_discharge_reason : Current charge level : 50%
Current time : 6 discharging_time : 0
discharging reason : 0
<7>max8998_charging_control : USB charging enabled
<6>max8998_set_cable : status(1)
<7>max8998_charging_control : USB charging enabled
<7>s3c_bat_discharge_reason : Current charge level : 50%
Current time : 6 discharging_time : 21606
discharging reason : 0
<4>Warning: unable to open an initial console.
<7>init_post begin
<6>Freeing init memory: 6204K
<7>max8998_charging_control : USB charging enabled
OHAI, stage1 init starting
<7>s3c_bat_discharge_reason : Current charge level : 50%
Current time : 6 discharging_time : 21606
discharging reason : 0
<7>max8998_charging_control : USB charging enabled
<7>s3c_bat_discharge_reason : Current charge level : 50%
Current time : 56 discharging_time : 21606
discharging reason : 0
<7>max8998_charging_control : USB charging enabled
<3>bio too big device loop0 (2 > 0)
<3>EXT4-fs (loop0): unable to read superblock
<6>EXT4-fs (loop1): mounted filesystem with ordered data mode. Opts: (null)
<7>s3c_bat_discharge_reason : Current charge level : 50%
Current time : 80 discharging_time : 21606
discharging reason : 0
<7>max8998_charging_control : USB charging enabled
stage1 log:
Fri Dec 31 23:07:37 GMT 2010
Creating filesystem with parameters:
Size: 18874368
Block size: 4096
Blocks per group: 32768
Inodes per group: 1152
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 4608
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/1152 inodes and 1110/4608 blocks
Creating filesystem with parameters:
Size: 419430400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1600
Label:
Blocks: 102400
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/25600 inodes and 3310/102400 blocks
force_recovery: 1
losetup: /dev/loop0: No such file or directory
mount: mounting /dev/loop0 on /system failed: Invalid argument
umount: can't umount /system: Invalid argument
losetup: /dev/loop2: No such device or address
losetup: /dev/loop0: No such device or address
5708 blocks
Fri Dec 31 23:09:02 GMT 2010
<3>init: cannot open '/initlogo.rle'
.
.
.
Taken from XXLA1 with zImage only... cm-10.1-wave-v2.1...
Interesting to see this...
Code:
<6>Memory: 69MB 214MB 0MB = 283MB total
<5>Memory: 272496k/325052k available, 17988k reserved, 0K highmem
<5>Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xff000000 - 0xffe00000 ( 14 MB)
vmalloc : 0xf0000000 - 0xfc000000 ( 192 MB)
lowmem : 0xc0000000 - 0xeff00000 ( 767 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.init : 0xc0008000 - 0xc0617000 (6204 kB)
.text : 0xc0617000 - 0xc0ce8000 (6980 kB)
.data : 0xc0ce8000 - 0xc0d34880 ( 307 kB)
.bss : 0xc0d348a4 - 0xc0e76ad8 (1289 kB)
Best Regards
This is my solution for now... with S8500. Tested by me.
In theory should work with S8530 too...
Later I will move to cable solution with Micro USB + Resistor...
Then hopefully this is working also with S8600 and S5250 for instance...
Best Regards
http://forum.xda-developers.com/showpost.php?p=41670635&postcount=5
In this FPM Mode... I can use AT Commands via UART...
So for now I can read and write something via UART...
Later more...
Best Regards
Made today few stupid mistakes....
510 R instead K...
Then confuse Pin 4 and 5 ...
I have 510 KOHM, but nothing happens...
Maybe not correct enough...
http://forum.xda-developers.com/showthread.php?t=820275
Code:
RID_FM_BOOT_ON_UART, /* 1 1 1 0 1 [B]619K[/B] Factory Mode Boot ON-UART */
I have used 620 KOHM with S8500 and S8600...
Factory Test Mode start ... this thingie with blue then green Screen... but nothing UART out nor input...
Maybe my wires wrong...
Will buy more Resistors...
Best Regards
Edit 1.
No idea yet, where is my mistake...
http://www.droidforums.net/forum/dr...own-motorola-factory-cable-4.html#post2234017
Backside Pinout...
I have now 510 KOHM + 13 KOHM = 523 KOHM...
Flashed to XXJEB to be sure...
Edit 2.
Check up...
My USB converter is alive...
Pin 4 and 5 should be correct, because Resistor Values working...
Will change Pin 2 and 3...
My fault...
For S8530 and S8500 now working.
Code:
[PAM: ] OneNAND physical base address : 0xb0000000
[PAM: ] OneNAND virtual base address : 0xb0000000
[PAM: ] FSR_PAM_InitNANDController Success!!
[PAM: ] --FSR_PAM_Init
bl3_info_block 1 age = 17
bl3_info_block 2 age = 18
BL3_2 Loading
+-------------------------------+
| Bootloader Shadowing FINISHED |
+-------------------------------+
Launch Image at 0x42080000
[BOOT_V1.0 (Jan 5 2012, 19:05:00)]
SelectBootingMode: H/W...0x3.
[BOOT] ARMCLK: 400000 KHz, MSYSHCLK 200000 KHz,MSYSPCLK: 100000 KHz, [BOOT] DSYSHCLK 166750 KHz,DSYSPCLK: 83375 KHz,PSYSHCLK: 133400 KHz, PSYSPCLK: 66700 KHz,SYSCON_A2M: 200000 KHz
Flash_Unlock failed
Poweron status - 20
FSA9480 0x03 Register = 1
FSA9480 0x0A Register = 0
FSA9480 0x0B Register = 8
FSA9480 0x07 Register = 1c
SelectBootingMode: Boot Mode = 1...
+++FIMD_Drv_INITIALIZE
FIMD_Drv_ChangeMode: MDNIE_MODE
Frame Rate:62 SCLK_FIMD:133400 kHz ClkDiv:4
---FIMD_Drv_INITIALIZE
---FIMD_Drv_SetWinOnOff(WIN4:1)
LCD initialize Finished
Display_LSI_Boot : disp_Main_Clean
Display_LSI_Boot : disp_Main_Clean_All
Display_LSI_Boot : disp_dimming_backlight
Display_LSI_Boot : disp_Normal_Init
DRV_modem_reset!!!!!!!!!!!!!!!!!
DRV_Send_DBL!!!!!!!!!!!!!!!!!
[DLOAD] Download Completed !!!
DRV_Wait_ModemInit!!!!!!!!!!!!!!!!!
DRV_CopyQSCBootBinary!!!!!!!!!!!!!!!!!
DRV_Send_BootBinaryCopyComplete!!!!!!!!!!!!!!!!!
DRV_Modem_BootingStart retry count = 0.
AST_POWERON
get_usb_sw_nv 0x40000
USBSwitch : AP
get_uart_sw_nv 0x40000
UARTSwitch : AP
My S8530 first UART output... with cable.
On XXKK5 with S8600 no luck... will try older Firmware...
Best Regards
Edit 1.
S8000 Jet
Code:
USBSwitch : AP
[BB31] VDD INT 1.2V
[BB31] VDD ARM 1.325V
ARM Clock: 400MHz --> 800MHz
[BOOT][DBG] RST_STAT 0x7E00_F904 : 0x00000001
[BOOT] ARMCLK: 800000, MPLL: 194000, HCLKX2: 266666, HCLK: 133333, PCLK: 33333
BootHWCheck: 6...
SelectBootingMode: H/W...0x6.
Poweron status - 10
pPowerOn 0 = 0xB00717E3
pPowerOn 1 = 0x0
pPowerOn 2 = 0x0
pPowerOn 3 = 0x10
pPowerOn 4 = 0x0
pPowerOn 5 = 0x0
pPowerOn 6 = 0x0
pPowerOn 7 = 0x0
pPowerOn 8 = 0x0
pPowerOn 9 = 0x0
pPowerOn 10 = 0x0
pPowerOn 11 = 0x0
pPowerOn 12 = 0x6
pPowerOn 13 = 0x0
FSA9480 0x03 Register = 1
FSA9480 0x0A Register = 0
FSA9480 0x0B Register = 8
FSA9480 0x07 Register = 1C
SelectBootingMode: Boot Mode = 1...
================================
LCD Source CLK -> MPLL(194000)
================================
uClkVal = 0x7 , uClkDir = 0x1
========================================
uVidconReg = 0x1D4 , uClkVal = 0x7
========================================
DRV_modem_reset!!!!!!!!!!!!!!!!!
DRV_Send_DBL!!!!!!!!!!!!!!!!!
[DLOAD] Download Completed !!!
DRV_Wait_MSMInit!!!!!!!!!!!!!!!!!
DRV_CopyMSMBootBinary!!!!!!!!!!!!!!!!!
DRV_Send_BootBinaryCopyComplete!!!!!!!!!!!!!!!!!
Ownership Release 0x5DFFF800, 0x0
AST_POWERON
get_usb_sw_nv 0x0
USBSwitch : AP
get_uart_sw_nv 0x0
UARTSwitch : AP
Drv_TaskEntry Start
DRV_Device_Init...
DRV_Device_Init...: DRV_hwversion = 6.
FSA9480 device ID = 40
JIT UART OFF NU_PWM_FID_SET_GPIO_PWMTOUT ok
prox_sensor_init SUCCESS~~~~~~~~~~~
[BOOT][Err] LCD_DET set PULLDOWN .
[LCD] ESD interrupt enable
acc_sensor_init SUCCESS~~~~~~~~~~~
pif_TaskEntry Start
[MODEMIF_AP_Init] NU_Create_Task pif task success
Create TESTMODE_Queue
Create testmode_task
Create TMFIFO_Queue
Create TESTMODE_RPT_Timer
brcm_bluetooth_main: Start Bluetooth Thread by BootEntry
0002 000.082 0.001.00.00:0000 SYSTEM > MochaTask: OSAL created.
0003 000.084 0.001.00.00:0000 BOOTMGR > MochaTask: OSAL created.
0004 000.091 0.001.00.00:0000 BOOTMGR > MochaTask: UART, USB, and Bluetooth created.
usb_api_open
usb_api_open
0005 000.100 0.001.00.00:0000 SYSTEM > MochaTask: DiagMgr created.
0006 000.106 0.001.00.00:0000 BOOTMGR > MochaTask: DiagMgr created.
0007 000.112 0.001.00.00:0000 EXCEPTION > __MemAllocForDebugHeap: Allocate 1200Kbytes (file OEM\OemDevFIFO.c, line 106)
0008 000.122 0.001.00.00:0000 AGENT > [__SysSecureBootRegisterPktRcvCallback:SysSecureBootPacket.c] __SysSecureBootRegisterPktRcvCallback is called!
0009 000.136 0.001.-1.-1:0000 BOOTMGR > MochaTask: EventMgr created.
0010 000.144 0.001.-1.-1:0000 BOOTMGR > MochaTask: AvMedia created.
0011 000.148 0.001.-1.-1:0000 ALL > DevGetHomeDLFlag : Address(0x0f940000) flag(0x0000ffff)
0012 000.157 0.001.-1.-1:0000 BOOTMGR > MochaTask: Clock created.
0013 000.162 0.001.-1.-1:0000 BOOTMGR > MochaTask: LED created.
0014 000.168 0.001.-1.-1:0000 BOOTMGR > MochaTask: Flip created.
0015 000.174 0.001.-1.-1:0000 SYSTEM > MochaTask: Clock, LED, Flip created.
+SDHC_Open(Ch1)
[SDHC] SDHC(ch1) Operating Clock : 378906Hz
[DS] data_srvc_task() Enter
[DS] diag_srvc_task() Enter
Diag_TaskEntry Start
I9000 tested with success...
So my cable work now with diffferent Samsung handsets...
Accept S8600 ...
Tested also with XXKJ7...
Need few days. Then test with S5250 will follow...
http://forum.xda-developers.com/showthread.php?t=1901376
I9001 is little bit similar to S8600... maybe helpfull.
Also usefull about UART:
http://forum.xda-developers.com/showthread.php?t=1209288
http://forum.xda-developers.com/showthread.php?t=1629359
Best Regards
UART on S5250 work, but not much info... yet...
Code:
AST_POWERON
*MRDY: 1
,~Booting Completed
This is output, if DL Mode...
Code:
AST_DOWNLOAD
I can set UART Logging temporary...
More text...
Best Regards

KB6 ROM (Android 2.2.1) @ Samfirmware for the GT-P1010 (wifi-only Galaxy Tab)

NOTE: the log below pertains to KB5...I haven't had time yet to look into KB6.
http://www.samfirmware.com/WEBPROTECT-p1010.htm
ro.build.display.id=FROYO.XWKB5
ro.build.version.sdk=8
ro.build.version.release=2.2.1
ro.build.date=Thu Feb 17 19:34:43 KST 2011
I'm going to unpack the various RFS archives, to see what's new. I've got a GT-P1000 Galaxy Tab (wifi+3G), so I'm not going to flash with Heimdall (let alone Odin ).
I made backups for factoryfs.rfs / dbdata.rfs etc. using the usual bit-by-bit "dd" -based method, and I've got a trusty TitaniumBackup archive ready, just in case
I notice that TV-out seems to be gone, and FM radio appears to be available. Hardware DSP support seems more present too. (read content logs below for more information)
TAR contents:
Code:
p1wifi_20110128_r10_00.pit (4 KB) (see PIT-info dumped below)
GT-P1010-CSC-SERKB3/
cache.rfs (10.9 MB) (see content listing below)
movinand.mst (51MB) (can be extracted with [URL="http://movitool.ntd.homelinux.org/trac/movitool/"]MoviTool[/URL], based on [URL="http://forum.xda-developers.com/showpost.php?p=9481702&postcount=30"]Volker1's method[/URL])
P1010XWKB5-REV03-ALL-low-CL913814/
boot.bin (256 KB)
cache.rfs (672 KB)
normalboot.img (4.3 MB)
param.lfs (612 KB)
recovery.img (4.3 MB)
Sbl.bin (1.2 MB)
system.rfs (331 MB)
userdata.rfs (1.2 MB)
Output from Volker1's PIT-info utility:
Code:
Contents of PIT file: p1wifi_20110128_r10_00.pit
---------------------------------------------------------------------------
file magic = 0x12349876 (expected value)
Unknown data: 0 0 0 0 0
Number of partitions = 13 (usual value)
Partition #1
Usual content: boot.bin, the primary boot loader (low-level hardware initialization)
partition entry type: 0 0 (normal partition)
ID = 0; flags = 0; unknown: 0
size = 1 blocks of 256 * 512 bytes = 131072 B = 128 kB = 0 MB
unknown string: [........]
partition name = [IBL+PBL.........................]
file name = [boot.bin........................................................]
Partition #2
Usual content: partition information table (PIT)
partition entry type: 0 0 (normal partition)
ID = 0x1; flags = 0; unknown: 0
size = 1 blocks of 256 * 512 bytes = 131072 B = 128 kB = 0 MB
unknown string: [........]
partition name = [PIT.............................]
file name = [p1wifi.pit......................................................]
Partition #3
Usual content: efs.rfs
partition entry type: 0 0 (normal partition)
ID = 0x14; flags = 0x2 (rfs file system); unknown: 0
size = 40 blocks of 256 * 512 bytes = 5242880 B = 5120 kB = 5 MB
unknown string: [........]
partition name = [EFS.............................]
file name = [efs.rfs.........................................................]
Partition #4
Usual content: Sbl.bin, the secondary boot loader (loads linux kernel)
partition entry type: 0 0 (normal partition)
ID = 0x3; flags = 0; unknown: 0
size = 5 blocks of 256 * 512 bytes = 655360 B = 640 kB = 0 MB
unknown string: [........]
partition name = [SBL.............................]
file name = [sbl.bin.........................................................]
Partition #5
Usual content: backup of secondary boot loader
partition entry type: 0 0 (normal partition)
ID = 0x4; flags = 0; unknown: 0
size = 5 blocks of 256 * 512 bytes = 655360 B = 640 kB = 0 MB
unknown string: [........]
partition name = [SBL2............................]
file name = [sbl.bin.........................................................]
Partition #6
Usual content: param.lfs /mnt/.lfs j4fs
partition entry type: 0 0 (normal partition)
ID = 0x15; flags = 0x2 (rfs file system); unknown: 0
size = 20 blocks of 256 * 512 bytes = 2621440 B = 2560 kB = 2 MB
unknown string: [........]
partition name = [PARAM...........................]
file name = [param.lfs.......................................................]
Partition #7
Usual content: zImage, the linux kernel
partition entry type: 0 0 (normal partition)
ID = 0x5; flags = 0; unknown: 0
size = 30 blocks of 256 * 512 bytes = 3932160 B = 3840 kB = 3 MB
unknown string: [........]
partition name = [NORMALBOOT......................]
file name = [normalboot.img..................................................]
Partition #8
Usual content: recovery.bin, the backup copy of zImage/initramfs
partition entry type: 0 0 (normal partition)
ID = 0x8; flags = 0; unknown: 0
size = 30 blocks of 256 * 512 bytes = 3932160 B = 3840 kB = 3 MB
unknown string: [........]
partition name = [RECOVERY........................]
file name = [recovery.img....................................................]
Partition #9
Usual content: factoryfs.rfs
partition entry type: 0 0 (normal partition)
ID = 0x16; flags = 0x2 (rfs file system); unknown: 0
size = 1430 blocks of 256 * 512 bytes = 187432960 B = 183040 kB = 178 MB
unknown string: [........]
partition name = [SYSTEM..........................]
file name = [system.rfs......................................................]
Partition #10
Usual content: dbdata.rfs
partition entry type: 0 0 (normal partition)
ID = 0x17; flags = 0x2 (rfs file system); unknown: 0
size = 302 blocks of 256 * 512 bytes = 39583744 B = 38656 kB = 37 MB
unknown string: [........]
partition name = [USERDATA........................]
file name = [userdata.rfs....................................................]
Partition #11
Usual content: cache.rfs
partition entry type: 0 0 (normal partition)
ID = 0x18; flags = 0x2 (rfs file system); unknown: 0
size = 140 blocks of 256 * 512 bytes = 18350080 B = 17920 kB = 17 MB
unknown string: [........]
partition name = [CACHE...........................]
file name = [cache.rfs.......................................................]
Partition #12
Usual content: modem.bin
partition entry type: 0 2 (unknown value)
ID = 0x3; flags = 0x1; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [........]
partition name = [HIDDEN.D........................]
file name = [hidden.rfs.t....................................................]
Partition #13
Usual content: Unknown
partition entry type: 0 2 (unknown value)
ID = 0; flags = 0x1; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [........]
partition name = [MOVINAND........................]
file name = [movinand.mst....................................................]
The usual CSC cache.rfs content:
Code:
/dbdata/svox/de-DE_gl0_sg.bin
/dbdata/svox/de-DE_ta.bin
/dbdata/svox/en-GB_kh0_sg.bin
/dbdata/svox/en-GB_ta.bin
/dbdata/svox/en-US_lh0_sg.bin
/dbdata/svox/en-US_ta.bin
/dbdata/svox/es-ES_ta.bin
/dbdata/svox/es-ES_zl0_sg.bin
/dbdata/svox/fr-FR_nk0_sg.bin
/dbdata/svox/fr-FR_ta.bin
/dbdata/svox/it-IT_cm0_sg.bin
/dbdata/svox/it-IT_ta.bin
/system/csc/feature.xml
/system/csc/contents.db
/system/csc/others.xml
/system/csc/sales_code.dat
/system/csc/customer.xml
/system/app/MusicODC.apk
/system/T9DB/qwerty_fi.kdb
/system/T9DB/phonepad_cs.kdb
/system/T9DB/qwerty_da.kdb
/system/T9DB/Samsung_400_PLlsUN_xt9.ldb
/system/T9DB/phonepad_lt.kdb
/system/T9DB/Samsung_400_TRlsUN_xt9.ldb
/system/T9DB/Samsung_400_DEusUN_xt9.ldb
/system/T9DB/Samsung_400_ETlsUN_xt9.ldb
/system/T9DB/Samsung_400_ENubUN_xt9.ldb
/system/T9DB/Samsung_400_SVusUN_xt9.ldb
/system/T9DB/qwerty_sv.kdb
/system/T9DB/Samsung_400_DAlsUN.ldb
/system/T9DB/phonepad_uk.kdb
/system/T9DB/phonepad_it.kdb
/system/T9DB/phonepad_el.kdb
/system/T9DB/qwerty_hu.kdb
/system/T9DB/qwerty_es.kdb
/system/T9DB/Samsung_400_UKlsUN_xt9.ldb
/system/T9DB/qwerty_fr.kdb
/system/T9DB/qwerty_et.kdb
/system/T9DB/Samsung_400_SKlsUN_xt9.ldb
/system/T9DB/phonepad_no.kdb
/system/T9DB/qwerty_nl.kdb
/system/T9DB/qwerty_lt.kdb
/system/T9DB/Samsung_400_LVlsUN_xt9.ldb
/system/T9DB/Samsung_400_ITlsUN_xt9.ldb
/system/T9DB/Samsung_400_PTlsUN_xt9.ldb
/system/T9DB/phonepad_da.kdb
/system/T9DB/Samsung_400_HUlsUN_xt9.ldb
/system/T9DB/Samsung_400_ELlsUN_xt9.ldb
/system/T9DB/phonepad_et.kdb
/system/T9DB/Samsung_400_KKlsUN_xt9.ldb
/system/T9DB/phonepad_es.kdb
/system/T9DB/qwerty_sk.kdb
/system/T9DB/phonepad_nl.kdb
/system/T9DB/qwerty_pt.kdb
/system/T9DB/Samsung_400_ESlsUN_xt9.ldb
/system/T9DB/Samsung_400_CSlsUN_xt9.ldb
/system/T9DB/phonepad_ru.kdb
/system/T9DB/phonepad_tr.kdb
/system/T9DB/qwerty_tr.kdb
/system/T9DB/phonepad_de.kdb
/system/T9DB/Samsung_400_FIlsUN_xt9.ldb
/system/T9DB/phonepad_ko.kdb
/system/T9DB/phonepad_fr.kdb
/system/T9DB/phonepad_fi.kdb
/system/T9DB/qwerty_ru.kdb
/system/T9DB/phonepad_en.kdb
/system/T9DB/qwerty_en.kdb
/system/T9DB/qwerty_cs.kdb
/system/T9DB/qwerty_el.kdb
/system/T9DB/Samsung_400_NOlsUN.ldb
/system/T9DB/Samsung_400_RUlsUN_xt9.ldb
/system/T9DB/qwerty_kk.kdb
/system/T9DB/qwerty_no.kdb
/system/T9DB/qwerty_uk.kdb
/system/T9DB/phonepad_lv.kdb
/system/T9DB/phonepad_pl.kdb
/system/T9DB/Samsung_400_NLlsUN_xt9.ldb
/system/T9DB/phonepad_sv.kdb
/system/T9DB/phonepad_sk.kdb
/system/T9DB/Samsung_400_LTlsUN_xt9.ldb
/system/T9DB/qwerty_pl.kdb
/system/T9DB/qwerty_de.kdb
/system/T9DB/Samsung_400_FRlsUN_xt9s.ldb
/system/T9DB/qwerty_ko.kdb
/system/T9DB/qwerty_lv.kdb
/system/T9DB/phonepad_pt.kdb
/system/T9DB/qwerty_it.kdb
/system/T9DB/phonepad_hu.kdb
/system/CSCFiles.txt
/system/SW_Configuration.xml
Changes in /system/app/ :
Removed DailyBriefing, Ebook, Mms, MobileTrackerEngineTwo, MobileTrackerUI, OtaProvisioningService, SamsungWidget_WeatherClock, SoundRecorder, signin, syncmldm, wipereceiver, wssomacp
Added PhoneCrashNotifier, PopupuiReceiverf, qik, qikhelp, skype
Changes in /system/bin/ :
Too many to list, but here are some notable ones:
Removed BCM4329B1_002.002.023.0534.0590.hcd (the driver for the multi-function Broadcom BCM-4329 chipset, also removed in /etc/wifi/ etc.), akmd2 (the multi-sensor driver, now split into several sub-daemons: geomagnetic, gyroscope, temperature, light, orientation, pressure, proximity, etc.)
Notable changes in /system/etc/ :
Added audio/codec/FMRadioEar.ini, audio/codec/FMRadioSpk.ini, and FM-radio stuff in /etc/firmware/ and /lib/libfmradio_jni.so (the Texas Intruments BRF6350 chip supports FM radio...but I don't think that /system/app/ contains an FM tuner application).
Notable addition: /lib/dsp/ + /lib/libOMX*.so + /lib/libVendor_ti_OMX*.so + lib/libaomx_*.so (Texas Intruments OMX/DSP, hardware encoding/decoding of 720p AMR, WB-AMR, AAC, h264, WMA, WMV, MP3, MPEG4, Flac, AC3, S263, etc.)
Code:
720p_h264vdec_sn.dll64P
720p_mp4vdec_sn.dll64P
720p_mp4venc_sn.dll64P
baseimage.dof
baseimage.map
chromasuppress.l64p
conversions.dll64P
dctn_dyn.dll64P
ddspbase_tiomap3430.dof64P
dfgm.dll64P
dynbase_tiomap3430.dof64P
eenf_ti.l64P
h264vdec_sn.dll64P
h264venc_sn.dll64P
ipp_sn.dll64P
jpegdec_sn.dll64P
jpegenc_sn.dll64P
m4venc_sn.dll64P
monitor_tiomap3430.dof64P
mp3dec_sn.dll64P
mp4v720parcdec_sn.dll64P
mp4varcdec_sn.dll64P
mp4vdec_sn.dll64P
mpeg4aacdec_sn.dll64P
mpeg4aacenc_sn.dll64P
mpeg4aridec_sn.dll64P
nbamrdec_sn.dll64P
nbamrenc_sn.dll64P
postprocessor_dualout.dll64P
qosdyn_3430.dll64P
ringio.dll64P
star.l64P
usn.dll64P
vpp_sn.dll64P
wbamrdec_sn.dll64P
wbamrenc_sn.dll64P
wmadec_sn.dll64P
wmv9dec_sn.dll64P
yuvconvert.l64p
Wifi access point doesn't seem very well protected (/etc/wifi/softap/hostapd.conf):
SSID = AndroidAP (not broadcast)
IP = 192.168.43.1
PASS = "password" (WPA)
By the way, the Wifi interface is different than on the fully-featured Tab: tiwlan0 (the access point is tiap0)
Nice let us know what's new and how you make out
This is great news and I am looking forward to your project, thanks!!!
Heads-up: original post updated with PIT partition structure and TAR contents.
Original post updated with further information (FM radio, DSP, etc.). None of this is authoritative, obviously. I am just making plain observations. I haven't even seen the manufacturer's specifications yet for this device.
Splice/combine the ROM with a P1000 ROM?
Cool. Does this mean that your aim to splice/combine the ROM with a P1000 ROM to create a custom Android 2.2.1 ROM WITH 3G capabilities, that is compatible with P1000?
And in that case, it sure would be nice to keep most of what has been removed from /system/* in the P1010 ROM, of course.
Very interesting, thanks for posting the analysis.
I wonder whether GL drivers are any newer than from P1000 ROMs.
And GPS daemon?
Also, interesting about these split sensor drivers.
edit
hmm, interesting, the GL drivers are for SGX530 not 540 like in normal tab.
And the CPU in 1010 is OMAP3 not Hummingbird.
KB6 now online @ Samfirmware.
I'm too busy to look into it though.
Hi,
I just got the Wifi version. How can I check the ROM version?
does the P1010 still have a gps radio?
jackfrostn said:
does the P1010 still have a gps radio?
Click to expand...
Click to collapse
Yes. Only differences between 3g and wifi model:
- no 3G radio
- less powerful CPU/GPU on wifi model (thus can't play HD/Full HD video)
- and off course, wifi model is cheaper
could someone try getting the skype and qik files working
any update on the ROMs progress?
bthoven said:
Yes. Only differences between 3g and wifi model:
- no 3G radio
- less powerful CPU/GPU on wifi model (thus can't play HD/Full HD video)
- and off course, wifi model is cheaper
Click to expand...
Click to collapse
Actually it CAN play HD video. It can record 720p movies so it would only make sense it'd be able to play them. I watch 720p episodes of Breaking Bad on mine.
Sent from my GT-P1010 using XDA Premium App
himmelhauk said:
Actually it CAN play HD video. It can record 720p movies so it would only make sense it'd be able to play them. I watch 720p episodes of Breaking Bad on mine.
Sent from my GT-P1010 using XDA Premium App
Click to expand...
Click to collapse
Yes, it can play 720p lower bitrate whilst the 3G version can play higher bit rate, and also 1080p.
bthoven said:
Yes, it can play 720p lower bitrate whilst the 3G version can play higher bit rate, and also 1080p.
Click to expand...
Click to collapse
Actually it is worth making a correction here as well, it plays 1080 just fine as well, at least for me.
Out of curiousity, where did you see that the wifi has a different CPU/GPU than the GSM/CDMA versions? I'm not finding that info anywhere.
chrisliphart said:
Out of curiousity, where did you see that the wifi has a different CPU/GPU than the GSM/CDMA versions? I'm not finding that info anywhere.
Click to expand...
Click to collapse
In all the TI OMAP libraries and kernel in the ROM?
skype for p1010 wifi
Skype will work with regular rom.i used it all day today
Yes, it does have gps radio on there. Well mine does anyway (in the uk)

ccache not working

I recently started with building LineageOS. However, I see that ccache isn't working for me for some reason. The ccache directory size is just 56MB. The build takes the same amount of time ~5hr(on my laptop). I've even set the cache size as 70GB. However, my out directory is 55.7GB. What am I doing wrong?
Probable relevant log:
Code:
[ 99% 40898/40912] Target cache fs ima...age/out/target/product/kenzo/cache.img
BuildImage: in_dir = /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/cache, out_file = /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/cache.img
fs type is not ext4
Running: mkuserimg.sh -s /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/cache /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/cache.img ext4 cache 268435456 -D /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system -L cache /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/root/file_contexts.bin
make_ext4fs -s -T -1 -S /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/root/file_contexts.bin -L cache -l 268435456 -a cache /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/cache.img /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/cache /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label: cache
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
Running ['mkuserimg.sh', '-s', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/cache', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/cache.img', 'ext4', 'cache', '268435456', '-D', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system', '-L', 'cache', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/root/file_contexts.bin'] command, exit code = 0
/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/cache.img maxsize=273985536 blocksize=135168 total=6398184 reserve=2838528
[ 99% 40904/40912] Construct recovery from boot
failed to reconstruct target deflate chunk 1 [(null)]; treating as normal
chunk 0: type 0 start 0 len 9041930
chunk 1: type 2 start 9041930 len 4148992
chunk 2: type 0 start 10711741 len 1347
Construct patches for 3 chunks...
patch 0 is 205 bytes (of 9041930)
patch 1 is 5082118 bytes (of 1669811)
patch 2 is 152 bytes (of 1347)
chunk 0: normal ( 0, 9041930) 205
chunk 1: deflate ( 9041930, 7662273) 5082118 (null)
chunk 2: normal ( 16704203, 1333) 152
[ 99% 40904/40912] Target userdata fs .../out/target/product/kenzo/userdata.img
BuildImage: in_dir = /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/data, out_file = /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/userdata.img
fs type is not ext4
Running: mkuserimg.sh -s /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/data /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/userdata.img ext4 data 26838785024 -D /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system -L data /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/root/file_contexts.bin
make_ext4fs -s -T -1 -S /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/root/file_contexts.bin -L data -l 26838785024 -a data /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/userdata.img /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/data /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system
Creating filesystem with parameters:
Size: 26838781952
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label: data
Blocks: 6552437
Block groups: 200
Reserved block group size: 1024
Created filesystem with 38/1638400 inodes and 150074/6552437 blocks
Running ['mkuserimg.sh', '-s', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/data', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/userdata.img', 'ext4', 'data', '26838785024', '-D', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system', '-L', 'data', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/root/file_contexts.bin'] command, exit code = 0
/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/userdata.img maxsize=27400671936 blocksize=135168 total=155432808 reserve=276824064
[ 99% 40908/40912] Target system fs im...G/systemimage_intermediates/system.img
BuildImage: in_dir = /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system, out_file = /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/obj/PACKAGING/systemimage_intermediates/system.img
fs type is not ext4
Running: mkuserimg.sh -s /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/obj/PACKAGING/systemimage_intermediates/system.img ext4 system 2684354560 -D /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system -L system /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/root/file_contexts.bin
make_ext4fs -s -T -1 -S /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/root/file_contexts.bin -L system -l 2684354560 -a system /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/obj/PACKAGING/systemimage_intermediates/system.img /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system
Creating filesystem with parameters:
Size: 2684354560
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 10240
Label: system
Blocks: 655360
Block groups: 20
Reserved block group size: 159
Created filesystem with 3340/163840 inodes and 292571/655360 blocks
Running ['mkuserimg.sh', '-s', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/obj/PACKAGING/systemimage_intermediates/system.img', 'ext4', 'system', '2684354560', '-D', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system', '-L', 'system', '/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/root/file_contexts.bin'] command, exit code = 0
[ 99% 40909/40912] Install system fs i...ge/out/target/product/kenzo/system.img
/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/system.img+/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p maxsize=2740531200 blocksize=135168 total=1160426351 reserve=27709440
[ 99% 40910/40912] Package target file...eage_kenzo-target_files-d4b338b746.zip
using prebuilt recovery.img from BOOTABLE_IMAGES...
using prebuilt boot.img from BOOTABLE_IMAGES...
putting script in bin/install-recovery.sh
running: unzip -o -q /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/obj/PACKAGING/target_files_intermediates/lineage_kenzo-target_files-d4b338b746.zip -d /tmp/targetfiles-cmkmqI
++++ boot ++++
using prebuilt boot.img from BOOTABLE_IMAGES...
++++ recovery ++++
using prebuilt recovery.img from BOOTABLE_IMAGES...
++++ recovery (two-step image) ++++
building image from target_files RECOVERY...
running: mkbootfs -f /tmp/targetfiles-cmkmqI/META/recovery_filesystem_config.txt /tmp/targetfiles-cmkmqI/RECOVERY/RAMDISK
running: minigzip
running: /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/host/linux-x86/bin/mkbootimg --kernel /tmp/targetfiles-cmkmqI/RECOVERY/kernel --cmdline androidboot.hardware=qcom ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 ramoops_memreserve=4M buildvariant=userdebug --base 0x80000000 --pagesize 2048 --ramdisk_offset 0x01000000 --tags_offset 0x00000100 --os_version 7.1.2 --os_patch_level 2017-08-05 --ramdisk /tmp/tmpFzhpAo --output /tmp/tmpBQOvrL
++++ system ++++
creating system.img...
BuildImage: in_dir = /tmp/targetfiles-cmkmqI/system, out_file = /tmp/system-d7Wo62.img
fs type is not ext4
Running: mkuserimg.sh -s /tmp/targetfiles-cmkmqI/system /tmp/system-d7Wo62.img ext4 system 2684354560 -T 1230748200 -C /tmp/targetfiles-cmkmqI/META/filesystem_config.txt -B /tmp/system-blocklist-OsEPwM.map -L system /tmp/targetfiles-cmkmqI/META/file_contexts.bin
make_ext4fs -s -T 1230748200 -S /tmp/targetfiles-cmkmqI/META/file_contexts.bin -C /tmp/targetfiles-cmkmqI/META/filesystem_config.txt -B /tmp/system-blocklist-OsEPwM.map -L system -l 2684354560 -a system /tmp/system-d7Wo62.img /tmp/targetfiles-cmkmqI/system
loaded 3332 fs_config entries
Creating filesystem with parameters:
Size: 2684354560
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 10240
Label: system
Blocks: 655360
Block groups: 20
Reserved block group size: 159
Created filesystem with 3342/163840 inodes and 292951/655360 blocks
Running ['mkuserimg.sh', '-s', '/tmp/targetfiles-cmkmqI/system', '/tmp/system-d7Wo62.img', 'ext4', 'system', '2684354560', '-T', '1230748200', '-C', '/tmp/targetfiles-cmkmqI/META/filesystem_config.txt', '-B', '/tmp/system-blocklist-OsEPwM.map', '-L', 'system', '/tmp/targetfiles-cmkmqI/META/file_contexts.bin'] command, exit code = 0
++++ userdata ++++
creating userdata.img...
BuildImage: in_dir = /tmp/tmpbdwQbq/data, out_file = /tmp/tmpucca6X
fs type is not ext4
Running: mkf2fsuserimg.sh /tmp/tmpucca6X 26838785024
in mkf2fsuserimg.sh PATH=/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/host/linux-x86/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/host/linux-x86/bin/:/usr/lib/jvm/java-8-openjdk/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/host/linux-x86/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/development/scripts:/run/media/vinayak/6FA49F144DC575A7/android/lineage/prebuilts/devtools/tools:/run/media/vinayak/6FA49F144DC575A7/android/lineage/external/selinux/prebuilts/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/prebuilts/android-emulator/linux-x86_64:/home/vinayak/venv/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
make_f2fs -l 26838785024 /tmp/tmpucca6X
Info: zone aligned segment0 blkaddr: 512
Info: Overprovision ratio = 1.250%
Info: Overprovision segments = 323 (GC reserved = 167)
Running ['mkf2fsuserimg.sh', '/tmp/tmpucca6X', '26838785024'] command, exit code = 0
userdata size (14) is 0.00% of limit (26838785024)
++++ extrauserdata ++++
++++ cache ++++
creating cache.img...
BuildImage: in_dir = /tmp/tmpQp6j5q/cache, out_file = /tmp/tmpPUYQ9G
fs type is not ext4
Running: mkf2fsuserimg.sh /tmp/tmpPUYQ9G 268435456
in mkf2fsuserimg.sh PATH=/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/host/linux-x86/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/host/linux-x86/bin/:/usr/lib/jvm/java-8-openjdk/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/host/linux-x86/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/development/scripts:/run/media/vinayak/6FA49F144DC575A7/android/lineage/prebuilts/devtools/tools:/run/media/vinayak/6FA49F144DC575A7/android/lineage/external/selinux/prebuilts/bin:/run/media/vinayak/6FA49F144DC575A7/android/lineage/prebuilts/android-emulator/linux-x86_64:/home/vinayak/venv/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
make_f2fs -l 268435456 /tmp/tmpPUYQ9G
Info: zone aligned segment0 blkaddr: 512
Info: Overprovision ratio = 15.000%
Info: Overprovision segments = 35 (GC reserved = 21)
Running ['mkf2fsuserimg.sh', '/tmp/tmpPUYQ9G', '268435456'] command, exit code = 0
cache size (14) is 0.00% of limit (268435456)
done.
[ 99% 40911/40912] Package OTA: /run/m...kenzo/lineage_kenzo-ota-d4b338b746.zip
unzipping target target-files...
running: unzip -o -q /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/obj/PACKAGING/target_files_intermediates/lineage_kenzo-target_files-d4b338b746.zip -d /tmp/targetfiles-Rnr8Wy
--- target info ---
blockimgdiff_versions = (str) 1,2,3,4
blocksize = (int) 131072
boot_size = (int) 67108864
build.prop = (dict) {'persist.audio.dirac.speaker': 'true', 'ro.sys.sdcardfs': 'true', 'persist.audio.fluence.speaker': 'true', 'bluetooth.hfp.client': '1', 'audio.safx.pbe.enabled': 'true', 'dalvik.vm.isa.arm.variant': 'cortex-a53.a57', 'ro.product.cpu.abilist': 'arm64-v8a,armeabi-v7a,armeabi', 'debug.enable.sglscale': '1', 'ro.build.product': 'kenzo', 'persist.data.iwlan.enable': 'true', 'ro.build.id': 'NJH47F', 'ro.hwui.gradient_cache_size': '1', 'dalvik.vm.stack-trace-file': '/data/anr/traces.txt', 'ro.product.cpu.abilist32': 'armeabi-v7a,armeabi', 'ro.build.selinux': '1', 'ro.qc.sdk.audio.fluencetype': 'fluence', 'tunnel.audio.encode': 'false', 'ro.frp.pst': '/dev/block/bootdevice/by-name/config', 'af.fast_track_multiplier': '1', 'dalvik.vm.lockprof.threshold': '500', 'ro.build.fingerprint': 'Xiaomi/kenzo/kenzo:6.0.1/MMB29M/V8.2.1.0.MHOCNDL:user/release-keys', 'ro.product.manufacturer': 'Xiaomi', 'dalvik.vm.isa.arm64.features': 'default', 'audio.offload.pcm.24bit.enable': 'false', 'persist.radio.cs_srv_type': '1', 'ro.hwui.layer_cache_size': '48', 'ro.build.description': 'kenzo-user 6.0.1 MMB29M V8.2.1.0.MHOCNDL release-keys', 'ro.bootimage.build.fingerprint': 'Xiaomi/lineage_kenzo/kenzo:7.1.2/NJH47F/d4b338b746:userdebug/test-keys', 'ro.product.cpu.abi': 'arm64-v8a', 'ro.sys.fw.dex2oat_thread_count': '4', 'ro.product.brand': 'Xiaomi', 'wifi.interface': 'wlan0', 'ro.cm.build.version.plat.sdk': '7', 'ro.product.model': 'Redmi Note 3', 'persist.radio.redir_party_num': '0', 'media.camera.ts.monotonic': '1', 'ro.cmlegal.url': 'https://lineageos.org/legal', 'persist.audio.fluence.voicecall': 'true', 'persist.cne.feature': '1', 'media.msm8956hw': '1', 'audio.offload.multiple.enabled': 'false', 'persist.demo.hdmirotationlock': 'false', 'ro.build.host': 'skynet', 'ro.build.version.security_patch': '2017-08-05', 'telephony.lteOnCdmaDevice': '1', 'media.sf.extractor-plugin': 'libffmpeg_extractor.so', 'ro.product.locale': 'en-US', 'audio.offload.min.duration.secs': '30', 'ro.btconfig.vendor': 'qcom', 'persist.audio.fluence.voicerec': 'true', 'audio.offload.video': 'false', 'dalvik.vm.isa.arm64.variant': 'generic', 'mmp.enable.3g2': 'true', 'persist.radio.NO_STAPA': '1', 'persist.hwc.downscale_threshold': '1.15', 'persist.sys.dalvik.vm.lib.2': 'libart.so', 'persist.loc.nlp_name': 'com.qualcomm.location', 'ro.board.platform': 'msm8952', 'voice.playback.conc.disabled': 'true', 'persist.data.qmi.adb_logmask': '0', 'ro.product.cpu.abilist64': 'arm64-v8a', 'audio.playback.mch.downsample': 'true', 'net.tcp.2g_init_rwnd': '10', 'ro.vendor.extension_library': 'libqti-perfd-client.so', 'persist.radio.multisim.config': 'dsds', 'persist.rild.nitz_long_ons_3': '', 'persist.rild.nitz_long_ons_2': '', 'persist.rild.nitz_long_ons_1': '', 'persist.rild.nitz_long_ons_0': '', 'ro.build.flavor': 'lineage_kenzo-userdebug', 'dalvik.vm.isa.arm.features': 'default', 'audio.deep_buffer.media': 'true', 'rild.libargs': '-d /dev/smd0', 'ro.gps.agps_provider': '1', 'persist.rild.nitz_short_ons_0': '', 'ro.build.version.release': '7.1.2', 'ro.build.version.codename': 'REL', 'DEVICE_PROVISIONED': '1', 'audio.offload.disable': '1', 'net.bt.name': 'Android', 'persist.data.netmgrd.qos.enable': 'true', 'ro.hwui.text_large_cache_width': '2048', 'persist.audio.fluence.audiorec': 'false', 'persist.radio.VT_HYBRID_ENABLE': '1', 'ro.opengles.version': '196610', 'use.voice.path.for.pcm.voip': 'true', 'persist.rild.nitz_plmn': '', 'ro.hwui.text_small_cache_height': '1024', 'ro.build.display.id': 'lineage_kenzo-userdebug 7.1.2 NJH47F d4b338b746 test-keys', 'audio.offload.pcm.16bit.enable': 'false', 'persist.radio.hw_mbn_update': '0', 'ro.config.ringtone': 'Orion.ogg', 'persist.radio.force_on_dc': 'true', 'persist.gps.qc_nlp_in_use': '1', 'debug.egl.hw': '0', 'ro.storage_manager.enabled': 'true', 'ro.carrier': 'unknown', 'ro.product.board': 'msm8952', 'ro.build.version.preview_sdk': '0', 'ro.com.google.clientidbase': 'android-xiaomi', 'persist.radio.start_ota_daemon': '1', 'ro.cm.build.version.plat.rev': '0', 'persist.timed.enable': 'true', 'ro.build.date': 'Tue Aug 22 13:26:20 IST 2017', 'ro.use_data_netmgrd': 'true', 'persist.radio.sib16_support': '1', 'qcom.bluetooth.soc': 'smd', 'ro.build.date.utc': '1503388580', 'audio.offload.buffer.size.kb': '64', 'keyguard.no_require_sim': 'true', 'ro.qc.sdk.audio.ssr': 'false', 'voice.conc.fallbackpath': 'deep-buffer', 'persist.dpm.feature': '5', 'ro.cm.display.version': '14.1-20170822-UNOFFICIAL-kenzo', 'ro.build.version.all_codenames': 'REL', 'mm.enable.smoothstreaming': 'true', 'ro.btconfig.if': 'smd', 'persist.dbg.vt_avail_ovr': '1', 'dev.pm.dyn_samplingrate': '1', 'ro.build.type': 'userdebug', 'ro.hwui.text_small_cache_width': '1024', 'voice.record.conc.disabled': 'false', 'ro.cm.version': '14.1-20170822-UNOFFICIAL-kenzo', 'persist.radio.sw_mbn_update': '0', 'ro.product.name': 'lineage_kenzo', 'ro.hwui.drop_shadow_cache_size': '6', 'ro.build.version.base_os': '', 'ro.telephony.call_ring.multiple': 'false', 'voice.voip.conc.disabled': 'true', 'persist.data.mode': 'concurrent', 'media.sf.omx-plugin': 'libffmpeg_omx.so', 'ro.expect.recovery_id': '0x22ab51ee62435272df9ab420618c4be9c94727ed000000000000000000000000', 'ro.telephony.default_network': '22,20', 'ro.wifi.channels': '', 'ro.hwui.r_buffer_cache_size': '8', 'persist.camera.HAL3.enabled': '1', 'ro.modversion': '14.1-20170822-UNOFFICIAL-kenzo', 'ro.build.characteristics': 'default', 'debug.mdpcomp.logs': '0', 'audio.offload.gapless.enabled': 'true', 'ro.build.version.incremental': 'd4b338b746', 'ro.config.alarm_alert': 'Hassium.ogg', 'ro.hwui.text_large_cache_height': '1024', 'rild.libpath': '/vendor/lib64/libril-qc-qmi-1.so', 'ro.build.tags': 'test-keys', 'ro.sf.lcd_density': '480', 'ro.build.version.sdk': '25', 'ro.cm.releasetype': 'UNOFFICIAL', 'audio.dolby.ds2.enabled': 'true', 'persist.audio.fluence.spk.mono': 'true', 'ril.subscription.types': 'RUIM', 'persist.dpm.nsrm.bkg.evt': '3955', 'ro.build.user': 'vinayak', 'persist.dbg.volte_avail_ovr': '1', 'ro.hwui.path_cache_size': '32', 'ro.product.device': 'kenzo', 'debug.sf.hw': '0', 'persist.rild.nitz_short_ons_1': '', 'persist.rild.nitz_short_ons_2': '', 'persist.rild.nitz_short_ons_3': '', 'persist.radio.rat_on': 'combine', 'ro.btconfig.dev': '/dev/smd3', 'ro.hwui.texture_cache_flushrate': '0.4', 'ro.hwui.texture_cache_size': '72', 'ro.cm.device': 'kenzo', 'audio_hal.period_size': '192', 'ro.btconfig.chip': 'WCN3680', 'ro.telephony.default_cdma_sub': '0', 'persist.radio.apm_sim_not_pwdn': '1', 'persist.hwc.mdpcomp.enable': 'true', 'persist.radio.custom_ecc': '1', 'persist.sys.dun.override': '0', 'ro.config.notification_sound': 'Argon.ogg', 'audio.offload.track.enable': 'false', 'media.aac_51_output_enabled': 'true'}
cache_fs_type = (str) ext4
cache_size = (int) 268435456
default_system_dev_certificate = (str) build/target/product/security/testkey
device_type = (str) MMC
extfs_sparse_flag = (str) -s
extra_recovery_keys = (str) vendor/cm/build/target/product/security/lineage
fs_type = (str) ext4
fstab = (dict) {'/cache': <common.Partition object at 0x7f2d76e445d0>, '/boot': <common.Partition object at 0x7f2d76e44050>, '/system': <common.Partition object at 0x7f2d76e44950>, '/dsp': <common.Partition object at 0x7f2d76e44210>, '/frp': <common.Partition object at 0x7f2d76e44110>, '/persist': <common.Partition object at 0x7f2d76e44810>, '/recovery': <common.Partition object at 0x7f2d76e44750>, '/firmware': <common.Partition object at 0x7f2d76e44610>, '/data': <common.Partition object at 0x7f2d76e44550>, '/misc': <common.Partition object at 0x7f2d76e44790>}
fstab_version = (int) 2
mkbootimg_args = (str) --ramdisk_offset 0x01000000 --tags_offset 0x00000100
mkbootimg_version_args = (str) --os_version 7.1.2 --os_patch_level 2017-08-05
multistage_support = (str) 1
ota_override_device = (str) kate,kenzo
recovery_api_version = (int) 3
recovery_as_boot = (str)
recovery_mount_options = (str) ext4=max_batch_time=0,commit=1,data=ordered,barrier=1,errors=panic,nodelalloc
recovery_size = (int) 67108864
selinux_fc = (str) /tmp/targetfiles-Rnr8Wy/META/file_contexts.bin
squashfs_sparse_flag = (str) -s
system_size = (int) 2684354560
tool_extensions = (str) device/xiaomi/kenzo/../common
update_rename_support = (str) 1
use_set_metadata = (str) 1
userdata_size = (int) 26838785024
unable to load device-specific module; assuming none
using prebuilt recovery.img from BOOTABLE_IMAGES...
using system.img from target-files
Total of 655360 4096-byte output blocks in 6263 input chunks.
Finding transfers...
Generating digraph...
Finding vertex sequence...
Reversing backward edges...
0/0 dependencies (0.00%) were violated; 0 source blocks stashed.
Improving vertex order...
Revising stash size...
Total 0 blocks (0 bytes) are packed as new blocks due to insufficient cache size.
Reticulating splines...
1156825088 1156825088 (100.00%) new __DATA
max stashed blocks: 0 (0 bytes), limit: 214748364 bytes (0.00%)
using prebuilt boot.img from BOOTABLE_IMAGES...
boot size (10713088) is 15.96% of limit (67108864)
running: openssl pkcs8 -in build/target/product/security/testkey.pk8 -inform DER -nocrypt
running: java -Xmx2048m -Djava.library.path=/run/media/vinayak/6FA49F144DC575A7/android/lineage/out/host/linux-x86/lib64 -jar /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/host/linux-x86/framework/signapk.jar -w build/target/product/security/testkey.x509.pem build/target/product/security/testkey.pk8 /tmp/tmpOsziEC /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/lineage_kenzo-ota-d4b338b746.zip
done.
[100% 40912/40912] build bacon
Package Complete: /run/media/vinayak/6FA49F144DC575A7/android/lineage/out/target/product/kenzo/lineage-14.1-20170822-UNOFFICIAL-kenzo.zip
make: Leaving directory '/run/media/vinayak/6FA49F144DC575A7/android/lineage'
#### make completed successfully (04:59:23 (hh:mm:ss)) ####
va6996 said:
I recently started with building LineageOS. However, I see that ccache isn't working for me for some reason. The ccache directory size is just 56MB. The build takes the same amount of time ~5hr(on my laptop). I've even set the cache size as 70GB. However, my out directory is 55.7GB. What am I doing wrong?...
Click to expand...
Click to collapse
Your better off posting your question on the following Official LineageOS thread for your device.
http://forum.xda-developers.com/showthread.php?t=3542491
Good Luck!
~~~~~~~~~~~~~~~
I Am The Egg Man,
They Are The Egg Men.
I Am The Walrus!
Coo Coo Cachoo!
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Categories

Resources