Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,771,588 Members 47,958 Now Online
XDA Developers Android and Mobile Development Forum

SGT3 10.1 Rom Developing by learning developers

Tip us?
 
r2d23cpo
Old
(Last edited by r2d23cpo; 11th February 2014 at 05:27 AM.)
#1  
Member - OP
Thanks Meter 52
Posts: 34
Join Date: Jan 2014
Default SGT3 10.1 Rom Developing by learning developers

Read First. The information posted in this thread can be extremely dangerous. We are here to get and share information. If you are looking for real development please see Angel666 thread at
" [Development][Source]CyanogenMod 11 for SGT-3 10.1" => http://forum.xda-developers.com/show....php?t=2633554
Please if you can donate to Angel666. He is our only current real NONE Stock Rom development.

Objective: We are a bunch of newbie trying to promote New NONE Stock Rom Development for Galaxy Tab 3 10.1. Witch carries "La maldicion del x86 processor". All available rom development is base on stock samsung rom. Not a single AOSP or Cianogenmod rom has been release. We need expertise guys. But since there is shortage I propose this thread so that Brave or Crazy newbie can share an experience ourself.

Rules:
xda Forum Rule:
1) We are in Development Area. All post has to be related ONLY to development by the rules of this forum. Be aware.

This thread rules
2) All development information are accepted no mater how dummy you think they may be.

3) ALL Developers Accepted - please help us or get involve.

4) All None developers - yes here you can post and share your development trouble.

5) Please be smart, Go Away while you can. Please consider the position you are in now:

> Part of XDA-developers. You have given you first step away of the common user!!!!!

> Have a Galaxy Tab 3 10.1. You have found your self a magic gadget that carries "Maldicion"

> Android Development Area - Ohhhh boy here is where you started to make your first big error for a common user. Go away.

> You put your best hope of salvation in a guy who think is an angel of hell. Sorry Angel666.

> Now you are following a bunch of inpatient crazy guys that have no idea what to do!!!! To make it difficult most have P5210 - wifi only while Angel666 has P5200 3g!

You been warm if you are a Nice common xda user. Go Away. Do not blame us if you get touch by the "Maldicion".

Back to business:

Bunch of nice links for you to start reading:
Yessss first read.
Then read again.
If you have time left then read more

XDA nice placesssss
Chef Central > Android => http://forum.xda-developers.com/chef-central/android

General discussion > XDA-University
COMPILE From Source For Any Phone On Linux Distros [BUILD ENVIRONMENT TO COMPILE]
=> http://forum.xda-developers.com/show....php?t=2060017

Android Development and Hacking > Android Software Development
[GUIDE] The Comprehensive AOKP Building Guide => http://forum.xda-developers.com/show....php?t=2217175

xda-university.com => http://xda-university.com/
http://xda-university.com/as-a-devel...d-rom-is-built
http://xda-university.com/as-a-devel...ng-source-code
http://xda-university.com/video-guides


Other

cyanogenmod.org
forum.cyanogenmod.com => h__p://forum.cyanogenmod.com/
wiki.cyanogenmod.org => h__p://wiki.cyanogenmod.org/w/Main_Page
Development => h__p://wiki.cyanogenmod.org/w/Development
Build_Guides => h__p://wiki.cyanogenmod.org/w/Build_Guides
How To Port CyanogenMod Android To Your Own Device => h__p://wiki.cyanogenmod.org/w/Doc:_porting_intro
download.cyanogenmod.org => h__p://download.cyanogenmod.org/
Unofficial_Ports => h__p://wiki.cyanogenmod.org/w/Unofficial_Ports
h__ps://github.com/CyanogenMod
h__ps://github.com/cyanogenmod/android_device_samsung_p5100
h__ps://github.com/CyanogenMod/android_device_samsung_p5110
h__ps://github.com/CyanogenMod/android_device_samsung_p5113

Google => h__p://source.android.com/source/index.html

Intel Developer Zone - software.intel.com
h__p://software.intel.com/en-us/search/site/language/en?query=intel+eula+x86+android+&sort_by=search_ap i_relevance&sort_order=DESC&collapsed_state=null
Intel Opensource Technology center => h__ps://01.org/android-ia/

github.com repositories
kumajaya repositories => h__ps://github.com/kumajaya?tab=repositories
Samsung Galaxy Tab 3 8.0 SM-T310 => h__ps://github.com/kumajaya/android_device_samsung_lt01wifi
HazouPH / android_device_motorola_smi => h__ps://github.com/HazouPH/android_device_motorola_smi
HazouPH / android_device_motorola_smi-plus => h__ps://github.com/HazouPH/android_device_motorola_smi-plus

Nice P2xx developers
h__ps://github.com/Angel666?tab=repositories
h__ps://github.com/Angel666/device_samsung_santos103g

h__ps://bitbucket.org/DutchDanny
h__ps://bitbucket.org/DutchDanny/kernel_samsung_santos10/src
h__ps://bitbucket.org/DutchDanny/android_kernel_santos10wifi/src

h__ps://github.com/trevd?tab=repositories
h__ps://github.com/trevd/android_device_samsung_p52xx
h__ps://github.com/trevd/android_kernel_samsung_santos10

info on Patches
h__p://review.cyanogenmod.org/#/q/owner:%22Trevor+Drake%22+status:merged,n,z
h__ps://github.com/HazouPH/android_device_motorola_smi/tree/jellybean/patch
h__ps://bitbucket.org/seandroid/frameworks-base/commits/4c1d9043b3a0c6d82872af1ec9f9daab7fa32d03

x86 similar devices
h__p://sourceforge.net/projects/razr-i.motorola/files/razr-i/9.8.2I-50_SMI-28/
oxavelar / android_device_motorola_intel_smi => h__ps://github.com/oxavelar/android_device_motorola_intel_smi
HazouPH / android_device_motorola_smi => h__ps://github.com/HazouPH/android_device_motorola_smi
HazouPH / android_device_motorola_smi-plus => h__ps://github.com/HazouPH/android_device_motorola_smi-plus

android-x86
h__ps://groups.google.com/forum/#!forum/android-x86
h__p://git.android-x86.org/

I think this is good enough to start this thread
The Following 9 Users Say Thank You to r2d23cpo For This Useful Post: [ Click to Expand ]
 
CAG-man
Old
#2  
CAG-man's Avatar
Senior Member
Thanks Meter 158
Posts: 294
Join Date: Apr 2013
Location: Athens, Ohio

 
DONATE TO ME
Lots of good information. I am a crazy one that has been looking to start developing ROMS. Why not end my frustration with my TAB 3. I will begin reading and learning and will help develop a non TW ROM.

Sent from my SAMSUNG-SGH-I337 using xda app-developers app
The CAG-MAN

AT&T G900A Galaxy S5
Awaiting to be rooted and customized

AT&T I337 Galaxy S4

Galaxy Tab 3 10.1 GT-P5210
WiFi Only
CAGrom Debloated

Donations are used to acquire new equipment and devices to make CAGrom. Thank you
 
r2d23cpo
Old
#3  
Member - OP
Thanks Meter 52
Posts: 34
Join Date: Jan 2014
I been having some troubles with Heimdall. It wont program my tablet? the error is "ERROR: Protocol initialisation failed!"

 
Code:
Heimdall v1.4.0

Copyright (c) 2010-2013, 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/

Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Initialising protocol...
ERROR: Protocol initialisation failed!

Releasing device interface...


So I started looking for P5210 pit and since I could not found one I decided to try an old trick use in other devices.

I use
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=481 skip=2176
And after testing the pit it seems correct. Looking inside it shows that its real name is "GT-P5210_EUR_XX_20130523.pit" so I rename it.

It is funny the only previews pit I found was for GT-P5200_EUR_XX_20130523.pit. Similar names.

So I created the other missing file needed for heimdall the "firmware.xml"

I attached the files.

But I still have not find why Heimdall wont communicate with Tablet?

Here is an analisys of the partition table

Code:
	
	P5200		P5200		P5210		P5210		P5010		P5010
Identifier	Partition Name		Flash FileName		Partition Name		Flash FileName		Block Size		Block Count
1	 RESERVED1		 -		 RESERVED1		 -		81920		6144
2	 EFS			 efs.img		 EFS		 efs.img		16384		40960
3	 CONFIG		 -		 CONFIG		 -		196608		32768
4	 FACTORY	 -		 FACTORY		 -		229376		4096
5	 MEDIA		 -		 MEDIA		 -		233472		4096
6	 CACHE		 cache.img		 CACHE		 cache.img		5324800		716800
7	 RESERVED2	 -		 RESERVED2		 -		237568		8192
8	 SYSTEM		 system.img		 SYSTEM		 system.img		286720		4833280
9	 USERDATA	 userdata.img		 USERDATA		 userdata.img		6041600		24715264
10	 BOOT		 boot.img		 BOOT		 boot.img		106496		40960
11	 RECOVERY		 recovery.img		 RECOVERY		 recovery.img		147456		40960
12	RADIO		modem.bin		 RESERVED3				188416		8192
13	 HIDDEN		 hidden.img		 HIDDEN		 hidden.img		5120000		204800
14	 CARRIER		 carrier.img		 CARRIER		 carrier.img		245760		8192
15	 TDATA		 tdata.img		 TDATA		 tdata.img		253952		8192
16	 PARAM		 param.bin		 PARAM		 param.bin		73728		8192
17	 PERSDATA		 persdata.img		 PERSDATA		 persdata.img		262144		24576
18	 BOTA0		 -		 BOTA0		 -		8192		4096
19	 BOTA1		 -		 BOTA1		 -		12288		4096
20	 DNX		 dnx_fwr.bin		 DNX		 dnx_fwr.bin		88064		2048
21	 OTA		 -		 OTA		 -		90112		16384
70	 OSIP		 osip.bin		 OSIP		 osip.bin				1
71	 PIT		GT-P5200_EUR_XX_20130523.pit		 PIT		 GT-P5210_EUR_XX_20130523.pit		34		15
72	 SBOOT		 sboot.bin		 SBOOT		 sboot.bin		49		6095
73	 MD5HDR		 md5.img		 MD5HDR		 md5.img		6144		2048
74	 SBOOT2		 sboot2.bin		 SBOOT2		 sboot2.bin		57344		16384
80	 IAFW		 iafw.bin		 IAFW		 iafw.bin				4096
I know the table looks bad. But take the data to a spread sheet. Note that the Block Size & Block Count shown is for P5210 only. it is different for P5200.
Attached Files
File Type: gz Heimdall package files.tar.gz - [Click for QR Code] (10.0 KB, 21 views)
The Following 3 Users Say Thank You to r2d23cpo For This Useful Post: [ Click to Expand ]
 
Nitro_123
Old
#4  
Senior Member
Thanks Meter 66
Posts: 333
Join Date: Feb 2011
Location: Salmiya
Now that we know the partitions, would it be possible to package say ubuntu and flash it to the device using heimdall ? is that possible at all :/
Trying to help
The Following User Says Thank You to Nitro_123 For This Useful Post: [ Click to Expand ]
 
r2d23cpo
Old
#5  
Member - OP
Thanks Meter 52
Posts: 34
Join Date: Jan 2014
@Nitro_123

jijiji you are like us, you want with all your hart Ubuntu in Tab3 10.1. Nice
We on the other hand, want with all our hart AOSP or Cianomodgen.
I bet you having Ubuntu alt least boot up should be feasible but at this moment I may not be your guy.

I am trying to make Heimdall work for Tab3 10.1.

Good news:
I thought I had detected what seems the problem. But My collection of data was done in WIN7 version.
I have setup my CodeBlocks to compile Heimdall so that I can work on it.
I have started to do some mods, recompiling and testing.

Bad news
Ubuntu Heimdall behave very different than in WIN7. Delays are different even the debug messages change.
So the initial thought of a time delay of 1 second is not seen in Ubuntu. Still failed in the same spot.
Heimdall source have no comments!!! But it has many print labels that are easy to spot.
All the nice tools that I have to debug usb are for windows! I need to get some for Ubuntu.


Still It seems feasible.
The Following 4 Users Say Thank You to r2d23cpo For This Useful Post: [ Click to Expand ]
 
r2d23cpo
Old
#6  
Member - OP
Thanks Meter 52
Posts: 34
Join Date: Jan 2014
I just want to say that I still working. Not as easy as I thought.
In Ubuntu many USB Device Managers query the USB port, disk driver , HID, Modemmanager, Audio & Video Player etc..(many others).

In particular some even "claim" the USB for them-self. This alternate USB managers make difficult the reverse engineering. In other words when I sniff ( monitor) the USB data I am never sure who sent what!!! I can say that I am learning a lot for sure.

Today i decide to use a different strategy. I will create my own communication program so I now for sure what I been sending to the Device. Well I will use an old ATT Captivate for initial testing. The Idea is to create a a good sequence that I can latter test against my P5210. With the intention to know if I can recreate the good sequence that I had record previously with WIn7+Odin.

It is not my intention to create my own Heimdall, but to have a good comparison to point the defect or suggested modification in Heimdall.

Be back when I get something useful.
The Following 2 Users Say Thank You to r2d23cpo For This Useful Post: [ Click to Expand ]
 
moonbutt74
Old
(Last edited by moonbutt74; 14th June 2014 at 01:32 AM.)
#7  
moonbutt74's Avatar
Senior Member
Thanks Meter 230
Posts: 503
Join Date: May 2014
Exclamation pit file

hello,

sorry to bother you,
my question is, is this pit file specific to heimdall usage or is it a universal file usable in odin?
thank you for your time

m

afterthought, there i a point in the boot process where a flag android cos path taken
go here http://forum.xda-developers.com/show...2589370&page=2 post #18
the theory being if this can be modified/sticken/spoofed etc. then any kernel should load and boot through.
The Following User Says Thank You to moonbutt74 For This Useful Post: [ Click to Expand ]
 
r2d23cpo
Old
#8  
Member - OP
Thanks Meter 52
Posts: 34
Join Date: Jan 2014
First my apologies to all. Personal issues had keet me out of this game. Still even when this tread did not got rolling I see that it did on:

"[SIGNUP] [DEVELOPMENT] signup sheet for AOSP build team", in the General area.


@moonbutt74

I can not deny to respond to you, my respect to your wonderful work in this forum. Thank for your time.

First be careful with what I say. I am no developer.

Quote:
Originally Posted by moonbutt74 View Post
... is this pit file specific to heimdall usage or is it a universal file usable in odin?
My best guest is that all Samsung PITs files are "universal". I have never seen a PIT file in this forum that was to be use only for Odin or Heimdall.!!! But I cab be mistaken.

Now the question is really: Is this a good PIT for P5210??? How I got it?
Well it is explained on response #3. http://forum.xda-developers.com/show...93&postcount=3

Quote:
So I started looking for P5210 pit and since I could not found one I decided to try an old trick use in other SAMSUNG devices.

I use
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=481 skip=2176
And after testing the pit it seems correct. Looking inside (Reading the PIT file) it shows that its real name is "GT-P5210_EUR_XX_20130523.pit" so I rename it like that.
Just download Heimdall package files.tar.gz. In it you will see a folder P5200, the pit inside was downloaded from the web. But inside the folder P5210 you will see "GT-P5210_EUR_XX_20130523.pit" That is the file I created with

Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=481 skip=2176
then renamed "out.pit" to read instead "GT-P5210_EUR_XX_20130523.pit"

You can look at the pit file using "PIT Magic v1.3.10 - Samsung PIT Creator, Editor, Analyzer!"

http://forum.xda-developers.com/show....php?t=1916936

Or you can use Heimdall PRINT function for the PIT.

Here is the report using the Analisys fubction on the pit

 
Code:
----------------------------------------------------------
PIT Magic v1.3.10 Copyright  Gaz 2012.
----------------------------------------------------------
Analysis for: GT-P5210_EUR_XX_20130523.pit
----------------------------------------------------------


----------------------------------------------------------
<<< Pit File Start >>>
----------------------------------------------------------


----------------------------------------------------------
<<< PIT File Header Information >>>
----------------------------------------------------------

Header Magic: 0x12349876     (4 Bytes)
Entry Count:  27             (4 Bytes)

----------------------------------------------------------
Dummy Data #1 (In String and Hexadecimal Format):
----------------------------------------------------------
String:       COM_
Hexadecimal:  434F4D5F

----------------------------------------------------------
Dummy Data #2 (In String and Hexadecimal Format):
----------------------------------------------------------
String:       TAR2
Hexadecimal:  54415232

----------------------------------------------------------
Dummy Data #3 (In String and Hexadecimal Format):
----------------------------------------------------------
String:       inte
Hexadecimal:  696E7465

----------------------------------------------------------
Dummy Data #4 (In String and Hexadecimal Format):
----------------------------------------------------------
String:       lsb
Hexadecimal:  6C736200

----------------------------------------------------------
Dummy Data #5 (In String and Hexadecimal Format):
----------------------------------------------------------
String:       
Hexadecimal:  00000000

----------------------------------------------------------
Dummy Data Length: (4 Bytes Per Block, 20 Bytes In Total.)
----------------------------------------------------------

Header Size: (28 Bytes)


----------------------------------------------------------
<<< PIT File Entries >>>
----------------------------------------------------------


----------------------------------------------------------
Entry Memory Address: 0x1C
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 70
Attribute:                  5       (READ / WRITE)
Update Attribute:           1               (FOTA)
Block Size:                 
Block Count:                1
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             OSIP
Flash FileName:             osip.bin
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0xA0
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 71
Attribute:                  5       (READ / WRITE)
Update Attribute:           1               (FOTA)
Block Size:                 34
Block Count:                15
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             PIT
Flash FileName:             GT-P5210_EUR_XX_20130523.pit
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0x124
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 72
Attribute:                  5       (READ / WRITE)
Update Attribute:           1               (FOTA)
Block Size:                 49
Block Count:                6,095
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             SBOOT
Flash FileName:             sboot.bin
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0x1A8
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 73
Attribute:                  5       (READ / WRITE)
Update Attribute:           1               (FOTA)
Block Size:                 6,144
Block Count:                2,048
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             MD5HDR
Flash FileName:             md5.img
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0x22C
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 18
Attribute:                  5       (READ / WRITE)
Update Attribute:           1               (FOTA)
Block Size:                 8,192
Block Count:                4,096
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             BOTA0
Flash FileName:             -
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0x2B0
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 19
Attribute:                  5       (READ / WRITE)
Update Attribute:           1               (FOTA)
Block Size:                 12,288
Block Count:                4,096
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             BOTA1
Flash FileName:             -
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0x334
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 2
Attribute:                  5       (READ / WRITE)
Update Attribute:           5               (FOTA)
Block Size:                 16,384
Block Count:                40,960
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             EFS
Flash FileName:             efs.img
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0x3B8
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 74
Attribute:                  5       (READ / WRITE)
Update Attribute:           1               (FOTA)
Block Size:                 57,344
Block Count:                16,384
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             SBOOT2
Flash FileName:             sboot2.bin
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0x43C
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 16
Attribute:                  5       (READ / WRITE)
Update Attribute:           1               (FOTA)
Block Size:                 73,728
Block Count:                8,192
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             PARAM
Flash FileName:             param.bin
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0x4C0
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 1
Attribute:                  5       (READ / WRITE)
Update Attribute:           1               (FOTA)
Block Size:                 81,920
Block Count:                6,144
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             RESERVED1
Flash FileName:             -
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0x544
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 20
Attribute:                  5       (READ / WRITE)
Update Attribute:           1               (FOTA)
Block Size:                 88,064
Block Count:                2,048
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             DNX
Flash FileName:             dnx_fwr.bin
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0x5C8
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 21
Attribute:                  5       (READ / WRITE)
Update Attribute:           1               (FOTA)
Block Size:                 90,112
Block Count:                16,384
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             OTA
Flash FileName:             -
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0x64C
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 10
Attribute:                  5       (READ / WRITE)
Update Attribute:           1               (FOTA)
Block Size:                 106,496
Block Count:                40,960
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             BOOT
Flash FileName:             boot.img
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0x6D0
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 11
Attribute:                  5       (READ / WRITE)
Update Attribute:           1               (FOTA)
Block Size:                 147,456
Block Count:                40,960
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             RECOVERY
Flash FileName:             recovery.img
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0x754
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 12
Attribute:                  5       (READ / WRITE)
Update Attribute:           1               (FOTA)
Block Size:                 188,416
Block Count:                8,192
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             RESERVED3
Flash FileName:             -
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0x7D8
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 3
Attribute:                  5       (READ / WRITE)
Update Attribute:           5               (FOTA)
Block Size:                 196,608
Block Count:                32,768
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             CONFIG
Flash FileName:             -
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0x85C
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 4
Attribute:                  5       (READ / WRITE)
Update Attribute:           5               (FOTA)
Block Size:                 229,376
Block Count:                4,096
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             FACTORY
Flash FileName:             -
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0x8E0
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 5
Attribute:                  5       (READ / WRITE)
Update Attribute:           5               (FOTA)
Block Size:                 233,472
Block Count:                4,096
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             MEDIA
Flash FileName:             -
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0x964
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 7
Attribute:                  5       (READ / WRITE)
Update Attribute:           1               (FOTA)
Block Size:                 237,568
Block Count:                8,192
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             RESERVED2
Flash FileName:             -
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0x9E8
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 14
Attribute:                  5       (READ / WRITE)
Update Attribute:           5               (FOTA)
Block Size:                 245,760
Block Count:                8,192
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             CARRIER
Flash FileName:             carrier.img
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0xA6C
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 15
Attribute:                  5       (READ / WRITE)
Update Attribute:           5               (FOTA)
Block Size:                 253,952
Block Count:                8,192
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             TDATA
Flash FileName:             tdata.img
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0xAF0
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 17
Attribute:                  5       (READ / WRITE)
Update Attribute:           5               (FOTA)
Block Size:                 262,144
Block Count:                24,576
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             PERSDATA
Flash FileName:             persdata.img
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0xB74
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 8
Attribute:                  5       (READ / WRITE)
Update Attribute:           5               (FOTA)
Block Size:                 286,720
Block Count:                4,833,280
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             SYSTEM
Flash FileName:             system.img
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0xBF8
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 13
Attribute:                  5       (READ / WRITE)
Update Attribute:           5               (FOTA)
Block Size:                 5,120,000
Block Count:                204,800
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             HIDDEN
Flash FileName:             hidden.img
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0xC7C
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 6
Attribute:                  5       (READ / WRITE)
Update Attribute:           5               (FOTA)
Block Size:                 5,324,800
Block Count:                716,800
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             CACHE
Flash FileName:             cache.img
FOTA FileName:              


----------------------------------------------------------
Entry Memory Address: 0xD00
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 9
Attribute:                  5       (READ / WRITE)
Update Attribute:           5               (FOTA)
Block Size:                 6,041,600
Block Count:                
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             USERDATA
Flash FileName:             userdata.img
FOTA FileName:              remained


----------------------------------------------------------
Entry Memory Address: 0xD84
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 80
Attribute:                  2                (STL)
Update Attribute:           1               (FOTA)
Block Size:                 
Block Count:                4,096
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             IAFW
Flash FileName:             iafw.bin
FOTA FileName:              


----------------------------------------------------------
<<< Pit File End >>>
----------------------------------------------------------


So to all my buddies. This PIT File is NOT Official, I just used some tools previously discussed in XDA for other Samsung devices.


Quote:
Originally Posted by moonbutt74 View Post
afterthought, there i a point in the boot process where a flag android cos path taken
go here http://forum.xda-developers.com/show...2589370&page=2 post #18
the theory being if this can be modified/sticken/spoofed etc. then any kernel should load and boot through.
Wao, that will be nice. In fact this is the first step to run Ubuntu from boot on our device. There are a couple of friend that will like that.
I will try later to read at the link to try to inform myself.

What I have understood on this boot process is that Samsung has place some sort of Signature in the Boot/Kernel/firmware. If we try to mod or use anything different it fail the Signature Process forcing the boot process to fail. Something like that. Forgive me If I am wrong.

So I will expect that kitkat will test the boot partition for its signatures. And if the boot partitions are not as expected Kitkat fail!! At least that is how the Galaxy S*** guys has explained! Again, Forgive me If I am wrong.
The Following 2 Users Say Thank You to r2d23cpo For This Useful Post: [ Click to Expand ]
 
r2d23cpo
Old
#9  
Member - OP
Thanks Meter 52
Posts: 34
Join Date: Jan 2014
Jijiji

I am confuce. I am reading your article and found you new my anwser back on may!!

Also found that kali is another linux distro! So we are talking the same objective.

Tags
development, source
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes