Hello,
I have a question for all coockers about file structure.
I've managed to edit my OS.nb for removing the first partition how is unusable on our Prophet.
My problem is now with RomMaster : I can't extract my XIP anymore, I test to Fix my XIP start and end address but don't work (Make_XIP from hypercore don't work too).
Some informations :
My error with RomMaster :
[Info] It is a common ROM.
[Error] File struct error, xip end offset is 0x77b82448, but file length is 0x035f0000.
Click to expand...
Click to collapse
What I test to resolve my problem, so it don't work too
D:\ROMEDIT> RomMaster.exe -s 0x00000400 -e 0x0030FFF0 -w 5 OS.nb
[Info] It is a common ROM.
[Error] File struct error, xip end offset is 0x77b82448, but file length is 0x035f0000.
Click to expand...
Click to collapse
My OS.nb info (make with NBInfo.exe)
NBInfo 2.1rc2
'OS.nb' has valid boot sector
Partition table:
Partition 0
-----------
File System: 0x23 (XIP RAM)
Start Sector: 0x00000002
Total Sectors: 0x00001800
Boot indicator: 0x00
First Head: 0x02
First Sector: 0x01
First Track: 0x00
Last Head: 0x7f
Last Sector: 0x01
Last Track: 0x30
Partition 1
-----------
File System: 0x25 (imgfs)
Start Sector: 0x00001880
Total Sectors: 0x00019700
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x01
First Track: 0x31
Last Head: 0xff
Last Sector: 0x01
Last Track: 0x1c7
Partition 2
-----------
File System: 0x00 (unknown)
Start Sector: 0x00000000
Total Sectors: 0x00000000
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x00
First Track: 0x00
Last Head: 0x00
Last Sector: 0x00
Last Track: 0x00
Partition 3
-----------
File System: 0x00 (unknown)
Start Sector: 0x00000000
Total Sectors: 0x00000000
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x00
First Track: 0x00
Last Head: 0x00
Last Sector: 0x00
Last Track: 0x00
Geometry: flash has 128 virtual heads
MSFLSH50 header found at offset 0x200
(0 Reserved Entries, 2 Flash Region Entries)
Flash Region Entry 0:
---------------------
Region type: XIP
Start phys. block: 0x00000000
Size in phys. blocks: 0x00000000
Size in log. blocks: 0x00000061 -> Size in sectors: 0x00003080
Sectors per block: 0x00000080
Bytes per block: 0x00010000
Compact blocks: 0x00000000
-> Bytes per sector: 0x00000200
Flash Region Entry 1:
---------------------
Region type: READONLY_FILESYS
Start phys. block: 0x00000000
Size in phys. blocks: 0x00000000
Size in log. blocks: 0x0000032e -> Size in sectors: 0x00019700
Sectors per block: 0x00000080
Bytes per block: 0x00010000
Compact blocks: 0x00000000
-> Bytes per sector: 0x00000200
Searching for IMGFS signature...
Found IMGFS at byte 0x00310000 (sector 0x00001880).
dwFSVersion: 00000001
dwSectorsPerHeaderBlock: 00000001
dwRunsPerFileHeader: 00000001
dwBytesPerHeader: 00000034
dwChunksPerSector: 00000008
dwFirstHeaderBlockOffset: 00000200
dwDataBlockSize: 00001000
szCompressionType: XPR
dwFreeSectorCount: 00000000
dwHiddenSectorCount: 00000100
dwUpdateModeFlag: 00000000
---
Click to expand...
Click to collapse
So, if anyone can explain to me how to fix my XIP addresses to extract and modify it... Or without fixing an another method to extract XIP from my ROM (RomMaster and Make_XIP don't work with it)
Thanks in advance for your responses.
ps : sorry for my English for my problem explain but it's not my native language
Have you tried msflshtool to extract your xip partition ?!
hma4 said:
Have you tried msflshtool to extract your xip partition ?!
Click to expand...
Click to collapse
Thanks for your response, when I dump my ROM with this tool I've two files OS.nb.part0 and OS.nb.part1, so what is the real format of those files ? it's nb or bin extension (real) cause I want a bin file to edit with XipPort how request a xip.bin file.
I havn't tried to rename it cause don't say if it's the good format.
Just need that
Another question : for XIP can I add/remove some "FF FF" at the end to change the size? (for offset definition msflh50 header) ?
Thank for your hard work, perfect ROM and your help
xvx45 said:
Thanks for your response, when I dump my ROM with this tool I've two files OS.nb.part0 and OS.nb.part1, so what is the real format of those files ? it's nb or bin extension (real) cause I want a bin file to edit with XipPort how request a xip.bin file.
I havn't tried to rename it cause don't say if it's the good format.
Just need that
Another question : for XIP can I add/remove some "FF FF" at the end to change the size? (for offset definition msflh50 header) ?
Thank for your hard work, perfect ROM and your help
Click to expand...
Click to collapse
it's bin format. just rename it to xip.bin
you don't have to touch those FF in xip
Thank hma4 for your quick responses !
I'll test it !
So addinf FF at the end of XIP can make it unusable or anything else ?
hma4 said:
Have you tried msflshtool to extract your xip partition ?!
Click to expand...
Click to collapse
hma4
how to use this tool ( command, or Syntax )
Thank so much
Related
Hi there.
As I promised, here is a full rom of YP-G70 8G INTERNATIONAL version. Based on G70ZSKP8. This is for recovery pruposes (ex. bricked device).
You will need:
- Odin.
- PIT file. Download here.
- ROM. Download here.
Flash it with odin. If you hard-bricked your device, make sure you hit re-partition and phone bootoader update.
What technique or program did you use specifically to identify and extract this partitions files.
The PIT file was pulled with Heimdall (doing a dd dump gets the same file but instead of 4k, you get a 256k file). Also, you can print the output to see which filename of the rom gets on every partition when Odin flashes it.
Also checked the partition table with fdisk and their size. Here is the output:
Code:
# partition table of /dev/mmcblk0
unit: sectors
/dev/mmcblk0p1 : start= 64, size= 15515584, Id= 5
/dev/mmcblk0p2 : start= 0, size= 0, Id= 0
/dev/mmcblk0p3 : start= 0, size= 0, Id= 0
/dev/mmcblk0p4 : start= 0, size= 0, Id= 0
/dev/mmcblk0p5 : start= 128, size= 512, Id=83
/dev/mmcblk0p6 : start= 704, size= 512, Id=83
/dev/mmcblk0p7 : start= 1280, size= 2560, Id=83
/dev/mmcblk0p8 : start= 3904, size= 2560, Id=83
/dev/mmcblk0p9 : start= 6528, size= 10240, Id=83
/dev/mmcblk0p10: start= 16832, size= 20480, Id=83
/dev/mmcblk0p11: start= 37376, size= 15360, Id=83
/dev/mmcblk0p12: start= 52800, size= 15360, Id=83
/dev/mmcblk0p13: start= 68224, size= 593920, Id=83
/dev/mmcblk0p14: start= 662208, size= 274432, Id=83
/dev/mmcblk0p15: start= 936704, size= 131072, Id=83
/dev/mmcblk0p16: start= 1067840, size= 3940352, Id=83
/dev/mmcblk0p17: start= 5008256, size= 10504192, Id=83
This output is useful for those have their partition table destroyed. I had to manually repartition my device.
Then, using dd, I dumped every partition of /dev/block/mmcblk0 and renamed they to match. Finally I packed the file.
In the pit file you linked to, there is a reference to a inand_8G.bin file how would you go about IDing that file and extracting it and of the partitions you listed above which one holds the inand_8G.bin file.
ishish9 said:
In the pit file you linked to, there is a reference to a inand_8G.bin file how would you go about IDing that file and extracting it and of the partitions you listed above which one holds the inand_8G.bin file.
Click to expand...
Click to collapse
In fact, no partition holds inand_8G.bin. Look at heimdall PIT output:
Code:
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Entry Count: 14
Unknown 1: 15718400
Unknown 2: 1
Unknown 3: 0
Unknown 4: 0
Unknown 5: 7703
Unknown 6: 237
Unknown 7: 62704
Unknown 8: 18
--- Entry #0 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 1
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1
Unknown 2: 0
Unknown 3: 0
Partition Name: IBL+PBL
Filename: boot.bin
--- Entry #1 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 2
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1
Unknown 2: 0
Unknown 3: 0
Partition Name: PIT
Filename: YPG70_8G-0304.pit
--- Entry #2 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 3
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 5
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL
Filename: Sbl.bin
--- Entry #3 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 4
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 5
Unknown 2: 6226025
Unknown 3: 7143533
Partition Name: SBL2
Filename: Sbl.bin
--- Entry #4 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 5
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 20
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs
--- Entry #5 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 6
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 40
Unknown 2: 39021280
Unknown 3: 7143533
Partition Name: EFS
Filename: efs.rfs
--- Entry #6 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 30
Unknown 2: 36662408
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage
--- Entry #7 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 8
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 30
Unknown 2: 6684793
Unknown 3: 3014771
Partition Name: RECOVERY
Filename: zImage
--- Entry #8 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 9
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1160
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.rfs
--- Entry #9 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 10
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 536
Unknown 2: 6684780
Unknown 3: 115
Partition Name: DBDATAFS
Filename: dbdata.rfs
--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 11
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 256
Unknown 2: 115
Unknown 3: 115
Partition Name: CACHE
Filename: cache.rfs
--- Entry #11 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 12
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 7696
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: datafs.rfs
--- Entry #12 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 13
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 20516
Unknown 2: 0
Unknown 3: 0
Partition Name: USERFS
Filename: userfs_8G.rfs
--- Entry #13 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 0
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: GANG
Filename: inand_8G.bin
In the partition table I posted earlier, last partition is mmcblk0p17, which contains datafs.rfs. I think that reference is only to show that the PIT file is for 8G. The inand_8G.bin's partition size is 0 bytes.
I know it shows up there as having no information but I have a file from a GANG partition that does have information in it, about 100 Megabytes, now that maybe simply place holder information but it is a partition and it may contain some information how ever little it may actually be. Also looking at the file I got from a GANG partition in a Hex editor the first words that appear are "FATHEAD" this link here has some information about it.
ishish9 said:
I know it shows up there as having no information but I have a file from a GANG partition that does have information in it, about 100 Megabytes, now that maybe simply place holder information but it is a partition and it may contain some information how ever little it may actually be. Also looking at the file I got from a GANG partition in a Hex editor the first words that appear are "FATHEAD" this link here has some information about it.
Click to expand...
Click to collapse
I'll look into it.
When I recovered my galaxy player I did a full dd dump of the mmcblk0 contents. I know it's "hacky", but it worked.
Is there any way you could post the ROM again as it is no longer available via your link.
My YP-G70 turned to a black screen after running google play movies. And since the battery cannot be easilly pulled I feel a flash is in order
Update:
Nevermind I found that I can pull the battery so I just did
Could some one be so kind to repost til full recovery file please.
Update: used this http://forum.xda-developers.com/showpost.php?p=19840746&postcount=420
And som grat help from rumirand, and my player int. is running again.
ident
I've not bricked my device. I'm using Erygit Custom-Rom V3.0 and rj kernel ( I downgraded from PA).
I just want to go back to original factory setting, can I use your ROM and just use it with Odin, without using the PIT file as my device is not bricked.
jamaljan said:
I've not bricked my device. I'm using Erygit Custom-Rom V3.0 and rj kernel ( I downgraded from PA).
I just want to go back to original factory setting, can I use your ROM and just use it with Odin, without using the PIT file as my device is not bricked.
Click to expand...
Click to collapse
XXKPL is much newer, and the available Odin package for it will do exactly what you want.
Mevordel said:
XXKPL is much newer, and the available Odin package for it will do exactly what you want.
Click to expand...
Click to collapse
thanks. is this what you are referring to ?
http://androidromupdate.com/2012/05...-g70-international-to-android-2-3-6-firmware/
jamaljan said:
thanks. is this what you are referring to ?
http://androidromupdate.com/2012/05...-g70-international-to-android-2-3-6-firmware/
Click to expand...
Click to collapse
That looks like the right thing, yes.
» OMAPFlash v4.15 (Aug 12 2011)
» -v
» Entering parameter file:Targets\Projects\espresso\omap4430hs_1200MHZ.txt at li
ne: 1
» -omap 4
» -t 36000
» -p OMAP4430_8G_HS
» -2
» chip_download EMMC Targets\Projects\espresso\MLO.hs
» chip_download EMMC Targets\Projects\espresso\Sbl.bin
» command cold_sw_reset
» Leaving parameter file:Targets\Projects\espresso\omap4430hs_1200MHZ.txt
» @targets\Projects\espresso\omap4430hs_1200MHZ.txt
» Looking for device (omap usb)
» Please turn on device
» Waiting for device (omap usb)
» Found device (omap usb)
» Requesting ASIC id
» AsicId items 05
» AsicId id 01 05 01 44 30 07 04
» AsicId secure_mode 13 02 01 00
» AsicId public_id 12 15 01 3F A1 B4 41 92 B4 47 75 9B F2 C3 7C D7 FA 21
CA A6 EF DF 17
» AsicId root_key_hash 14 21 01 49 D3 8A 83 CA 2D EF 29 0B DF 4E 54 67 2D 6F
EA 08 9C 39 8F 6F 86 A3 4D D3 0C 74 77 B7 A4 54 1D
» AsicId checksum 15 09 01 9C 66 9A D9 68 2A DC CF
» Searching 2nd for: OMAP4430_8G_HS 443007 04 HS
» Loading second file Targets\2nd-Downloaders\dnld_startup_omap4_hs_4g_es2.s2.si
gned.2nd.hs
» Entering parameter filemapflash2nd.txt at line: 45
» -pheriphalboot_reopen
» Reading board configuration file Targets\Configurations\configuration_omap4430
_8g.txt
» Reading definition file .\targets\definitions\definitions_omap4.txt
» -board_config Targets\Configurations\configuration_omap4430_8g.txt
» Leaving parameter filemapflash2nd.txt
» Sending size of second file (0x00006E60 bytes)
» Transferring second file to target (0x6E60 bytes)
» Closing boot connection
» Found device (omap usb)
» Waiting for 2nd
» Found 2nd
» Looking for a driver for 'EMMC'
» chip_driver EMMC Targets\Flash-Drivers\emmc_drv.bin sid 1 width 4 delay 9 rpap
i_base 0x00028400
» Downloading driver
» Downloading 'Targets\Flash-Drivers\emmc_drv.bin'
» Sending data (47160 bytes) :::::::::::::::::::: [47160]
Interface 'OMAPFLASH DRIVER v6'
Driver 'eMMC JESD84-A43'
Driver configuration: sid = 0x00000001
Driver configuration: width = 0x00000004
Driver configuration: delay = 0x00000009
Driver configuration: rpapi_base = 0x00028400
MMC sid = 0x01
MMC mmc_volt = 0x01
MMC data_width = 0x04
MMC card_rca = 0x04
MMC card_type = 0x03
MMC data_width_support = 0x08
MMC transfer_clk_max = 0xBB80
MMC card_size = 0x1D5A000
eMMC CID MID = 0x15 // Manufacturer ID
eMMC CID CBX = 0x01 // Card/BGA
eMMC CID OID = 0x00 // OEM/Application ID
eMMC CID PNM = 0x9B4100009E1B // Product name
eMMC CID PRV = 0x19 // Product revision
eMMC CID PSN = 0x00009E1B // Product serial numbe
r
eMMC CID MDT = 0x9E // Manufacturing date
eMMC CID CRC = 0x0D // CRC7 checksum
eMMC CSD CSD_STRUCTURE = 0x03 // CSD structure
eMMC CSD SPEC_VERS = 0x04 // System specification
version
eMMC CSD TAAC = 0x27 // Data read access-tim
e 1
eMMC CSD NSAC = 0x01 // Data read access-tim
e 2 in CLK cycles (NSAC*100)
eMMC CSD TRAN_SPEED = 0x32 // Max. bus clock frequ
ency
eMMC CSD CCC = 0x00F5 // Card command classes
eMMC CSD READ_BL_LEN = 0x09 // Max. read data block
length
eMMC CSD READ_BL_PARTIAL = 0x00 // Partial blocks for r
ead allowed
eMMC CSD WRITE_BLK_MISALIGN = 0x00 // Write block misalign
ment
eMMC CSD READ_BLK_MISALIGN = 0x00 // Read block misalignm
ent
eMMC CSD DSR_IMP = 0x00 // DSR implemented
eMMC CSD C_SIZE = 0x00FF // Device size
eMMC CSD VDD_R_CURR_MIN = 0x06 // Max. read current @
VDD min
eMMC CSD VDD_R_CURR_MAX = 0x06 // Max. read current @
VDD max
eMMC CSD VDD_W_CURR_MIN = 0x06 // Max. write current @
VDD min
eMMC CSD VDD_W_CURR_MAX = 0x06 // Max. write current @
VDD max
eMMC CSD C_SIZE_MULT = 0x01 // Device size multipli
er
eMMC CSD ERASE_GRP_SIZE = 0x1F // Erase group size
eMMC CSD ERASE_GRP_MULT = 0x1F // Erase group size mul
tiplier
eMMC CSD WP_GRP_SIZE = 0x0F // Write protect group
size
eMMC CSD WP_GRP_ENABLE = 0x01 // Write protect group
enable
eMMC CSD DEFAULT_ECC = 0x00 // Manufacturer default
ECC
eMMC CSD R2W_FACTOR = 0x02 // Write speed factor
eMMC CSD WRITE_BL_LEN = 0x09 // Max. write data bloc
k length
eMMC CSD WRITE_BL_PARTIAL = 0x00 // Partial blocks for w
rite allowed
eMMC CSD CONTENT_PROT_APP = 0x00 // Content protection a
pplication
eMMC CSD FILE_FORMAT_GRP = 0x00 // File format group
eMMC CSD COPY = 0x01 // Copy flag (OTP)
eMMC CSD PERM_WRITE_PROTECT = 0x00 // Permanent write prot
ection
eMMC CSD TMP_WRITE_PROTECT = 0x00 // Temporary write prot
ection
eMMC CSD FILE_FORMAT = 0x00 // File format
eMMC CSD ECC = 0x00 // ECC code
eMMC CSD CRC = 0x33 // CRC
eMMC EXT_CSD S_CMD_SET = 0x00 // Supported Command Se
ts
eMMC EXT_CSD BOOT_INFO = 0x15 // Boot information
eMMC EXT_CSD BOOT_SIZE_MULTI = 0x0A // Boot partition size
eMMC EXT_CSD ACC_SIZE = 0x07 // Access size
eMMC EXT_CSD HC_ERASE_GRP_SIZE = 0x00 // High-capacity erase
unit size
eMMC EXT_CSD ERASE_TIMEOUT_MULT = 0x04 // High-capacity erase
timeout
eMMC EXT_CSD REL_WR_SEC_C = 0x07 // Reliable write secto
r count
eMMC EXT_CSD HC_WP_GRP_SIZE = 0x01 // High-capacity write
protect group size
eMMC EXT_CSD S_C_VCC = 0x01 // Sleep current (VCC)
eMMC EXT_CSD S_C_VCCQ = 0x01 // Sleep current (VCCQ)
eMMC EXT_CSD S_A_TIMEOUT = 0x07 // Sleep/awake timeout
eMMC EXT_CSD SEC_COUNT = 0x01D5A000 // Sector Count
eMMC EXT_CSD MIN_PERF_W_8_52 = 0xA0 // Minimum Write Perfor
mance for 8bit at 52MHz
eMMC EXT_CSD MIN_PERF_R_8_52 = 0x00 // Minimum Read Perform
ance for 8bit at 52MHz
eMMC EXT_CSD MIN_PERF_W_8_26_4_52 = 0x00 // Minimum Write Perfor
mance for 8bit at 26MHz, for 4bit at 52MHz
eMMC EXT_CSD MIN_PERF_R_8_26_4_52 = 0x00 // Minimum Read Perform
ance for 8bit at 26MHz, for 4bit at 52MHz
eMMC EXT_CSD MIN_PERF_W_4_26 = 0x00 // Minimum Write Perfor
mance for 4bit at 26MHz
eMMC EXT_CSD MIN_PERF_R_4_26 = 0x00 // Minimum Read Perform
ance for 4bit at 26MHz
eMMC EXT_CSD PWR_CL_26_360 = 0x00 // Power class for 26MH
z at 3.6V
eMMC EXT_CSD PWR_CL_52_360 = 0x00 // Power class for 52MH
z at 3.6V
eMMC EXT_CSD PWR_CL_26_195 = 0x00 // Power class for 26MH
z at 1.95V
eMMC EXT_CSD PWR_CL_52_195 = 0x00 // Power class for 52MH
z at 1.95V
eMMC EXT_CSD CARD_TYPE = 0x01 // Card type
eMMC EXT_CSD CSD_STRUCTURE = 0x00 // CSD structure versio
n
eMMC EXT_CSD EXT_CSD_REV = 0x00 // Extended CSD revisio
n
eMMC EXT_CSD CMD_SET = 0x02 // Command set
eMMC EXT_CSD CMD_SET_REV = 0x05 // Command set revision
eMMC EXT_CSD POWER_CLASS = 0x00 // Power class
eMMC EXT_CSD HS_TIMING = 0x00 // High-speed interface
timing
eMMC EXT_CSD BUS_WIDTH = 0x00 // Bus width mode
eMMC EXT_CSD ERASED_MEM_CONT = 0x00 // Erased memory conten
t
eMMC EXT_CSD BOOT_CONFIG = 0x00 // Boot configuration
eMMC EXT_CSD BOOT_BUS_WIDTH = 0x00 // Boot bus width1
eMMC EXT_CSD ERASE_GROUP_DEF = 0x00 // High-density erase g
roup definition
EMMC eMMC DRIVER INIT COMPLETE
» Downloading complete
» Elapsed time: 0:00.452 (104336 bytes/s)
» End loading driver
» Downloading
» Downloading 'Targets\Projects\espresso\MLO.hs'
» Sending data (262144 bytes) :::::............... [65536]
Please someone help me.My phone is dead since one month
ME too
nirmalece19 said:
» OMAPFlash v4.15 (Aug 12 2011)
» -v
» Entering parameter file:Targets\Projects\espresso\omap4430hs_1200MHZ.txt at li
ne: 1
» -omap 4
» -t 36000
» -p OMAP4430_8G_HS
» -2
» chip_download EMMC Targets\Projects\espresso\MLO.hs
» chip_download EMMC Targets\Projects\espresso\Sbl.bin
» command cold_sw_reset
» Leaving parameter file:Targets\Projects\espresso\omap4430hs_1200MHZ.txt
» @targets\Projects\espresso\omap4430hs_1200MHZ.txt
» Looking for device (omap usb)
» Please turn on device
» Waiting for device (omap usb)
» Found device (omap usb)
» Requesting ASIC id
» AsicId items 05
» AsicId id 01 05 01 44 30 07 04
» AsicId secure_mode 13 02 01 00
» AsicId public_id 12 15 01 3F A1 B4 41 92 B4 47 75 9B F2 C3 7C D7 FA 21
CA A6 EF DF 17
» AsicId root_key_hash 14 21 01 49 D3 8A 83 CA 2D EF 29 0B DF 4E 54 67 2D 6F
EA 08 9C 39 8F 6F 86 A3 4D D3 0C 74 77 B7 A4 54 1D
» AsicId checksum 15 09 01 9C 66 9A D9 68 2A DC CF
» Searching 2nd for: OMAP4430_8G_HS 443007 04 HS
» Loading second file Targets\2nd-Downloaders\dnld_startup_omap4_hs_4g_es2.s2.si
gned.2nd.hs
» Entering parameter filemapflash2nd.txt at line: 45
» -pheriphalboot_reopen
» Reading board configuration file Targets\Configurations\configuration_omap4430
_8g.txt
» Reading definition file .\targets\definitions\definitions_omap4.txt
» -board_config Targets\Configurations\configuration_omap4430_8g.txt
» Leaving parameter filemapflash2nd.txt
» Sending size of second file (0x00006E60 bytes)
» Transferring second file to target (0x6E60 bytes)
» Closing boot connection
» Found device (omap usb)
» Waiting for 2nd
» Found 2nd
» Looking for a driver for 'EMMC'
» chip_driver EMMC Targets\Flash-Drivers\emmc_drv.bin sid 1 width 4 delay 9 rpap
i_base 0x00028400
» Downloading driver
» Downloading 'Targets\Flash-Drivers\emmc_drv.bin'
» Sending data (47160 bytes) :::::::::::::::::::: [47160]
Interface 'OMAPFLASH DRIVER v6'
Driver 'eMMC JESD84-A43'
Driver configuration: sid = 0x00000001
Driver configuration: width = 0x00000004
Driver configuration: delay = 0x00000009
Driver configuration: rpapi_base = 0x00028400
MMC sid = 0x01
MMC mmc_volt = 0x01
MMC data_width = 0x04
MMC card_rca = 0x04
MMC card_type = 0x03
MMC data_width_support = 0x08
MMC transfer_clk_max = 0xBB80
MMC card_size = 0x1D5A000
eMMC CID MID = 0x15 // Manufacturer ID
eMMC CID CBX = 0x01 // Card/BGA
eMMC CID OID = 0x00 // OEM/Application ID
eMMC CID PNM = 0x9B4100009E1B // Product name
eMMC CID PRV = 0x19 // Product revision
eMMC CID PSN = 0x00009E1B // Product serial numbe
r
eMMC CID MDT = 0x9E // Manufacturing date
eMMC CID CRC = 0x0D // CRC7 checksum
eMMC CSD CSD_STRUCTURE = 0x03 // CSD structure
eMMC CSD SPEC_VERS = 0x04 // System specification
version
eMMC CSD TAAC = 0x27 // Data read access-tim
e 1
eMMC CSD NSAC = 0x01 // Data read access-tim
e 2 in CLK cycles (NSAC*100)
eMMC CSD TRAN_SPEED = 0x32 // Max. bus clock frequ
ency
eMMC CSD CCC = 0x00F5 // Card command classes
eMMC CSD READ_BL_LEN = 0x09 // Max. read data block
length
eMMC CSD READ_BL_PARTIAL = 0x00 // Partial blocks for r
ead allowed
eMMC CSD WRITE_BLK_MISALIGN = 0x00 // Write block misalign
ment
eMMC CSD READ_BLK_MISALIGN = 0x00 // Read block misalignm
ent
eMMC CSD DSR_IMP = 0x00 // DSR implemented
eMMC CSD C_SIZE = 0x00FF // Device size
eMMC CSD VDD_R_CURR_MIN = 0x06 // Max. read current @
VDD min
eMMC CSD VDD_R_CURR_MAX = 0x06 // Max. read current @
VDD max
eMMC CSD VDD_W_CURR_MIN = 0x06 // Max. write current @
VDD min
eMMC CSD VDD_W_CURR_MAX = 0x06 // Max. write current @
VDD max
eMMC CSD C_SIZE_MULT = 0x01 // Device size multipli
er
eMMC CSD ERASE_GRP_SIZE = 0x1F // Erase group size
eMMC CSD ERASE_GRP_MULT = 0x1F // Erase group size mul
tiplier
eMMC CSD WP_GRP_SIZE = 0x0F // Write protect group
size
eMMC CSD WP_GRP_ENABLE = 0x01 // Write protect group
enable
eMMC CSD DEFAULT_ECC = 0x00 // Manufacturer default
ECC
eMMC CSD R2W_FACTOR = 0x02 // Write speed factor
eMMC CSD WRITE_BL_LEN = 0x09 // Max. write data bloc
k length
eMMC CSD WRITE_BL_PARTIAL = 0x00 // Partial blocks for w
rite allowed
eMMC CSD CONTENT_PROT_APP = 0x00 // Content protection a
pplication
eMMC CSD FILE_FORMAT_GRP = 0x00 // File format group
eMMC CSD COPY = 0x01 // Copy flag (OTP)
eMMC CSD PERM_WRITE_PROTECT = 0x00 // Permanent write prot
ection
eMMC CSD TMP_WRITE_PROTECT = 0x00 // Temporary write prot
ection
eMMC CSD FILE_FORMAT = 0x00 // File format
eMMC CSD ECC = 0x00 // ECC code
eMMC CSD CRC = 0x33 // CRC
eMMC EXT_CSD S_CMD_SET = 0x00 // Supported Command Se
ts
eMMC EXT_CSD BOOT_INFO = 0x15 // Boot information
eMMC EXT_CSD BOOT_SIZE_MULTI = 0x0A // Boot partition size
eMMC EXT_CSD ACC_SIZE = 0x07 // Access size
eMMC EXT_CSD HC_ERASE_GRP_SIZE = 0x00 // High-capacity erase
unit size
eMMC EXT_CSD ERASE_TIMEOUT_MULT = 0x04 // High-capacity erase
timeout
eMMC EXT_CSD REL_WR_SEC_C = 0x07 // Reliable write secto
r count
eMMC EXT_CSD HC_WP_GRP_SIZE = 0x01 // High-capacity write
protect group size
eMMC EXT_CSD S_C_VCC = 0x01 // Sleep current (VCC)
eMMC EXT_CSD S_C_VCCQ = 0x01 // Sleep current (VCCQ)
eMMC EXT_CSD S_A_TIMEOUT = 0x07 // Sleep/awake timeout
eMMC EXT_CSD SEC_COUNT = 0x01D5A000 // Sector Count
eMMC EXT_CSD MIN_PERF_W_8_52 = 0xA0 // Minimum Write Perfor
mance for 8bit at 52MHz
eMMC EXT_CSD MIN_PERF_R_8_52 = 0x00 // Minimum Read Perform
ance for 8bit at 52MHz
eMMC EXT_CSD MIN_PERF_W_8_26_4_52 = 0x00 // Minimum Write Perfor
mance for 8bit at 26MHz, for 4bit at 52MHz
eMMC EXT_CSD MIN_PERF_R_8_26_4_52 = 0x00 // Minimum Read Perform
ance for 8bit at 26MHz, for 4bit at 52MHz
eMMC EXT_CSD MIN_PERF_W_4_26 = 0x00 // Minimum Write Perfor
mance for 4bit at 26MHz
eMMC EXT_CSD MIN_PERF_R_4_26 = 0x00 // Minimum Read Perform
ance for 4bit at 26MHz
eMMC EXT_CSD PWR_CL_26_360 = 0x00 // Power class for 26MH
z at 3.6V
eMMC EXT_CSD PWR_CL_52_360 = 0x00 // Power class for 52MH
z at 3.6V
eMMC EXT_CSD PWR_CL_26_195 = 0x00 // Power class for 26MH
z at 1.95V
eMMC EXT_CSD PWR_CL_52_195 = 0x00 // Power class for 52MH
z at 1.95V
eMMC EXT_CSD CARD_TYPE = 0x01 // Card type
eMMC EXT_CSD CSD_STRUCTURE = 0x00 // CSD structure versio
n
eMMC EXT_CSD EXT_CSD_REV = 0x00 // Extended CSD revisio
n
eMMC EXT_CSD CMD_SET = 0x02 // Command set
eMMC EXT_CSD CMD_SET_REV = 0x05 // Command set revision
eMMC EXT_CSD POWER_CLASS = 0x00 // Power class
eMMC EXT_CSD HS_TIMING = 0x00 // High-speed interface
timing
eMMC EXT_CSD BUS_WIDTH = 0x00 // Bus width mode
eMMC EXT_CSD ERASED_MEM_CONT = 0x00 // Erased memory conten
t
eMMC EXT_CSD BOOT_CONFIG = 0x00 // Boot configuration
eMMC EXT_CSD BOOT_BUS_WIDTH = 0x00 // Boot bus width1
eMMC EXT_CSD ERASE_GROUP_DEF = 0x00 // High-density erase g
roup definition
EMMC eMMC DRIVER INIT COMPLETE
» Downloading complete
» Elapsed time: 0:00.452 (104336 bytes/s)
» End loading driver
» Downloading
» Downloading 'Targets\Projects\espresso\MLO.hs'
» Sending data (262144 bytes) :::::............... [65536]
Please someone help me.My phone is dead since one month
Click to expand...
Click to collapse
i think NAND error , cannot get into recovery mode, but get into dowload mode, flash via odin error
» OMAPFlash v4.15 (Aug 12 2011)
» -v
» Entering parameter file:Targets\Projects\espresso\omap4430hs_1200MHZ.txt at li
ne: 1
» -omap 4
» -t 36000
» -p OMAP4430_8G_HS
» -2
» chip_download EMMC Targets\Projects\espresso\MLO.hs
» chip_download EMMC Targets\Projects\espresso\Sbl.bin
» command cold_sw_reset
» Leaving parameter file:Targets\Projects\espresso\omap4430hs_1200MHZ.txt
» @targets\Projects\espresso\omap4430hs_1200MHZ.txt
» Looking for device (omap usb)
» Please turn off device
» Please turn on device
» Waiting for device (omap usb)
» Found device (omap usb)
» Requesting ASIC id
» AsicId items 05
» AsicId id 01 05 01 44 30 07 04
» AsicId secure_mode 13 02 01 00
» AsicId public_id 12 15 01 3F A1 B4 41 92 B4 47 75 9B F2 C3 7C D7 FA 21
CA A6 EF DF 17
» AsicId root_key_hash 14 21 01 49 D3 8A 83 CA 2D EF 29 0B DF 4E 54 67 2D 6F
EA 08 9C 39 8F 6F 86 A3 4D D3 0C 74 77 B7 A4 54 1D
» AsicId checksum 15 09 01 9C 66 9A D9 68 2A DC CF
» Searching 2nd for: OMAP4430_8G_HS 443007 04 HS
» Loading second file Targets\2nd-Downloaders\dnld_startup_omap4_hs_4g_es2.s2.si
gned.2nd.hs
» Entering parameter filemapflash2nd.txt at line: 45
» -pheriphalboot_reopen
» Reading board configuration file Targets\Configurations\configuration_omap4430
_8g.txt
» Reading definition file .\targets\definitions\definitions_omap4.txt
» -board_config Targets\Configurations\configuration_omap4430_8g.txt
» Leaving parameter filemapflash2nd.txt
» Sending size of second file (0x00006E60 bytes)
» Transferring second file to target (0x6E60 bytes)
» Closing boot connection
» Found device (omap usb)
» Waiting for 2nd
» Found 2nd
» Looking for a driver for 'EMMC'
» chip_driver EMMC Targets\Flash-Drivers\emmc_drv.bin sid 1 width 4 delay 9 rpap
i_base 0x00028400
» Downloading driver
» Downloading 'Targets\Flash-Drivers\emmc_drv.bin'
» Sending data (47160 bytes) :::::::::::::::::::: [47160]
Interface 'OMAPFLASH DRIVER v6'
Driver 'eMMC JESD84-A43'
Driver configuration: sid = 0x00000001
Driver configuration: width = 0x00000004
Driver configuration: delay = 0x00000009
Driver configuration: rpapi_base = 0x00028400
MMC sid = 0x01
MMC mmc_volt = 0x01
MMC data_width = 0x04
MMC card_rca = 0x04
MMC card_type = 0x03
MMC data_width_support = 0x08
MMC transfer_clk_max = 0xBB80
MMC card_size = 0x1D5A000
eMMC CID MID = 0x15 // Manufacturer ID
eMMC CID CBX = 0x01 // Card/BGA
eMMC CID OID = 0x00 // OEM/Application ID
eMMC CID PNM = 0x9B4100009E1B // Product name
eMMC CID PRV = 0x19 // Product revision
eMMC CID PSN = 0x00009E1B // Product serial numbe
r
eMMC CID MDT = 0x9E // Manufacturing date
eMMC CID CRC = 0x0D // CRC7 checksum
eMMC CSD CSD_STRUCTURE = 0x03 // CSD structure
eMMC CSD SPEC_VERS = 0x04 // System specification
version
eMMC CSD TAAC = 0x27 // Data read access-tim
e 1
eMMC CSD NSAC = 0x01 // Data read access-tim
e 2 in CLK cycles (NSAC*100)
eMMC CSD TRAN_SPEED = 0x32 // Max. bus clock frequ
ency
eMMC CSD CCC = 0x00F5 // Card command classes
eMMC CSD READ_BL_LEN = 0x09 // Max. read data block
length
eMMC CSD READ_BL_PARTIAL = 0x00 // Partial blocks for r
ead allowed
eMMC CSD WRITE_BLK_MISALIGN = 0x00 // Write block misalign
ment
eMMC CSD READ_BLK_MISALIGN = 0x00 // Read block misalignm
ent
eMMC CSD DSR_IMP = 0x00 // DSR implemented
eMMC CSD C_SIZE = 0x00FF // Device size
eMMC CSD VDD_R_CURR_MIN = 0x06 // Max. read current @
VDD min
eMMC CSD VDD_R_CURR_MAX = 0x06 // Max. read current @
VDD max
eMMC CSD VDD_W_CURR_MIN = 0x06 // Max. write current @
VDD min
eMMC CSD VDD_W_CURR_MAX = 0x06 // Max. write current @
VDD max
eMMC CSD C_SIZE_MULT = 0x01 // Device size multipli
er
eMMC CSD ERASE_GRP_SIZE = 0x1F // Erase group size
eMMC CSD ERASE_GRP_MULT = 0x1F // Erase group size mul
tiplier
eMMC CSD WP_GRP_SIZE = 0x0F // Write protect group
size
eMMC CSD WP_GRP_ENABLE = 0x01 // Write protect group
enable
eMMC CSD DEFAULT_ECC = 0x00 // Manufacturer default
ECC
eMMC CSD R2W_FACTOR = 0x02 // Write speed factor
eMMC CSD WRITE_BL_LEN = 0x09 // Max. write data bloc
k length
eMMC CSD WRITE_BL_PARTIAL = 0x00 // Partial blocks for w
rite allowed
eMMC CSD CONTENT_PROT_APP = 0x00 // Content protection a
pplication
eMMC CSD FILE_FORMAT_GRP = 0x00 // File format group
eMMC CSD COPY = 0x01 // Copy flag (OTP)
eMMC CSD PERM_WRITE_PROTECT = 0x00 // Permanent write prot
ection
eMMC CSD TMP_WRITE_PROTECT = 0x00 // Temporary write prot
ection
eMMC CSD FILE_FORMAT = 0x00 // File format
eMMC CSD ECC = 0x00 // ECC code
eMMC CSD CRC = 0x33 // CRC
eMMC EXT_CSD S_CMD_SET = 0x00 // Supported Command Se
ts
eMMC EXT_CSD BOOT_INFO = 0x15 // Boot information
eMMC EXT_CSD BOOT_SIZE_MULTI = 0x0A // Boot partition size
eMMC EXT_CSD ACC_SIZE = 0x07 // Access size
eMMC EXT_CSD HC_ERASE_GRP_SIZE = 0x00 // High-capacity erase
unit size
eMMC EXT_CSD ERASE_TIMEOUT_MULT = 0x04 // High-capacity erase
timeout
eMMC EXT_CSD REL_WR_SEC_C = 0x07 // Reliable write secto
r count
eMMC EXT_CSD HC_WP_GRP_SIZE = 0x01 // High-capacity write
protect group size
eMMC EXT_CSD S_C_VCC = 0x01 // Sleep current (VCC)
eMMC EXT_CSD S_C_VCCQ = 0x01 // Sleep current (VCCQ)
eMMC EXT_CSD S_A_TIMEOUT = 0x07 // Sleep/awake timeout
eMMC EXT_CSD SEC_COUNT = 0x01D5A000 // Sector Count
eMMC EXT_CSD MIN_PERF_W_8_52 = 0xA0 // Minimum Write Perfor
mance for 8bit at 52MHz
eMMC EXT_CSD MIN_PERF_R_8_52 = 0x00 // Minimum Read Perform
ance for 8bit at 52MHz
eMMC EXT_CSD MIN_PERF_W_8_26_4_52 = 0x00 // Minimum Write Perfor
mance for 8bit at 26MHz, for 4bit at 52MHz
eMMC EXT_CSD MIN_PERF_R_8_26_4_52 = 0x00 // Minimum Read Perform
ance for 8bit at 26MHz, for 4bit at 52MHz
eMMC EXT_CSD MIN_PERF_W_4_26 = 0x00 // Minimum Write Perfor
mance for 4bit at 26MHz
eMMC EXT_CSD MIN_PERF_R_4_26 = 0x00 // Minimum Read Perform
ance for 4bit at 26MHz
eMMC EXT_CSD PWR_CL_26_360 = 0x00 // Power class for 26MH
z at 3.6V
eMMC EXT_CSD PWR_CL_52_360 = 0x00 // Power class for 52MH
z at 3.6V
eMMC EXT_CSD PWR_CL_26_195 = 0x00 // Power class for 26MH
z at 1.95V
eMMC EXT_CSD PWR_CL_52_195 = 0x00 // Power class for 52MH
z at 1.95V
eMMC EXT_CSD CARD_TYPE = 0x01 // Card type
eMMC EXT_CSD CSD_STRUCTURE = 0x00 // CSD structure versio
n
eMMC EXT_CSD EXT_CSD_REV = 0x00 // Extended CSD revisio
n
eMMC EXT_CSD CMD_SET = 0x02 // Command set
eMMC EXT_CSD CMD_SET_REV = 0x05 // Command set revision
eMMC EXT_CSD POWER_CLASS = 0x00 // Power class
eMMC EXT_CSD HS_TIMING = 0x00 // High-speed interface
timing
eMMC EXT_CSD BUS_WIDTH = 0x00 // Bus width mode
eMMC EXT_CSD ERASED_MEM_CONT = 0x00 // Erased memory conten
t
eMMC EXT_CSD BOOT_CONFIG = 0x00 // Boot configuration
eMMC EXT_CSD BOOT_BUS_WIDTH = 0x00 // Boot bus width1
eMMC EXT_CSD ERASE_GROUP_DEF = 0x00 // High-density erase g
roup definition
EMMC eMMC DRIVER INIT COMPLETE
» Downloading complete
» Elapsed time: 0:00.580 (81310 bytes/s)
» End loading driver
» Downloading
» Downloading 'Targets\Projects\espresso\MLO.hs'
» Sending data (262144 bytes) :::::............... [65536]
I've been trying to get this thing fixed for months. I have a Verizon Galaxy Tab SCH-i905 that would not boot up fully. I've downloaded every file available for it on the web I believe. I think the partitions are screwed up. It won't boot up (gets stuck on splash screen), won't go into recovery, and only goes into download mode. This is even after reflashing the stock rom in ODIN and attempting to flash CWM.
The only file I haven't found is a stock pit file to flash in ODIN. From what I understand, the pit file can be extracted from a working device in Hielmdall. Someone, please post this up!
shawndh said:
I've been trying to get this thing fixed for months. I have a Verizon Galaxy Tab SCH-i905 that would not boot up fully. I've downloaded every file available for it on the web I believe. I think the partitions are screwed up. It won't boot up (gets stuck on splash screen), won't go into recovery, and only goes into download mode. This is even after reflashing the stock rom in ODIN and attempting to flash CWM.
The only file I haven't found is a stock pit file to flash in ODIN. From what I understand, the pit file can be extracted from a working device in Hielmdall. Someone, please post this up!
Click to expand...
Click to collapse
If you can assist me with finding the instructions to extract the files, I would be happy to get you mine.
I have tried using EFS Professional (I can't post links so just google it) and it should pull pit files, but I haven't been sucessful.
You need busy box installed as well.
There might be a better way, but I don't know it.
bentheexo said:
If you can assist me with finding the instructions to extract the files, I would be happy to get you mine.
Click to expand...
Click to collapse
I dont know how to do it either but I'll do some research and post back. Thanx for offering. BTW, is your device rooted?
Yes with 10.1 official. Cwm too.
Sent from my SGH-T999 using Tapatalk
This was a pain to pull had a lot of driver issues
I am not sure if its right but it does show a lot of info
I actually screwed up my tab somehow... After installing recovery + 10.1 cyn I was left with a tablet missing 20 gigs of space some reason it was showing 12 total
Ended up restoring the 3.2 recovery file and I still had same issue
After several updates still same issue
Once it updated to 4.0 it went back to my correct normal hard drive space and thats when I pulled this
Code:
----------------------------------------------------------
PIT Magic v1.3.10 Copyright © Gaz 2012.
----------------------------------------------------------
Analysis for: i905-32gig.pit
----------------------------------------------------------
----------------------------------------------------------
<<< Pit File Start >>>
----------------------------------------------------------
----------------------------------------------------------
<<< PIT File Header Information >>>
----------------------------------------------------------
Header Magic: 0x12349876 (4 Bytes)
Entry Count: 19 (4 Bytes)
----------------------------------------------------------
Dummy Data #1 (In String and Hexadecimal Format):
----------------------------------------------------------
String:
Hexadecimal: 00000000
----------------------------------------------------------
Dummy Data #2 (In String and Hexadecimal Format):
----------------------------------------------------------
String:
Hexadecimal: 00000000
----------------------------------------------------------
Dummy Data #3 (In String and Hexadecimal Format):
----------------------------------------------------------
String:
Hexadecimal: 00000000
----------------------------------------------------------
Dummy Data #4 (In String and Hexadecimal Format):
----------------------------------------------------------
String:
Hexadecimal: 00000000
----------------------------------------------------------
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: 0
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 512
Block Count:
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SMD
Flash FileName: emmc.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xA0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 2
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 512
Block Count: 6
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BCT
Flash FileName: bct.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x124
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 3
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 512
Block Count: 1
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PT
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x1A8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 4
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 512
Block Count: 4
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EBT
Flash FileName: bootloader.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x22C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 5
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 512
Block Count: 4
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EB2
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x2B0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 6
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 512
Block Count: 8
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: GP1
Flash FileName: fusetrigger.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x334
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 7
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 512
Block Count: 24
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: 8
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 512
Block Count: 10
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SOS
Flash FileName: recovery.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x43C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 9
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 512
Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: LNX
Flash FileName: boot.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x4C0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 10
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 512
Block Count: 1,156
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: APP
Flash FileName: system.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x544
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 11
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 512
Block Count: 896
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CAC
Flash FileName: cache.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x5C8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 12
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 512
Block Count: 4
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MSC
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x64C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 13
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 512
Block Count: 24
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MDM
Flash FileName: modem.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x6D0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 14
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 512
Block Count: 27,545
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: UDA
Flash FileName: data.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x754
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 15
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 512
Block Count: 48
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: LTE
Flash FileName: lte_modem.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x7D8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 16
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 512
Block Count: 12
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EF2
Flash FileName: nvblock.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x85C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 17
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 512
Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OTA
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x8E0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 18
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 512
Block Count: 600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HID
Flash FileName: hidden.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x964
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 19
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 512
Block Count: 2
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: GPT
Flash FileName:
FOTA FileName:
----------------------------------------------------------
<<< Pit File End >>>
----------------------------------------------------------
MY SII can not flah in any rom with a /data process or can not do wipe data ,and I have my friend see this he made a special PIT for me to solve it .THEN my intersd is now 8.5G what happened? does my phone can have 11.5G again?
Yup just use another pit file wid appropriate values...
Search s2 android development.. u will get a thread dedicated to pit files
doctor_droid said:
Yup just use another pit file wid appropriate values...
Search s2 android development.. u will get a thread dedicated to pit files
Click to expand...
Click to collapse
YES I have tried 3G and 4G pit file and Im going to try 5G pit file ...
And I hanve download the pit magic to analysis a good to go pit and found this ----------------------------------------------------------
PIT Magic v1.3.10 Copyright © Gaz 2012.
----------------------------------------------------------
Analysis for: zui.pit
----------------------------------------------------------
----------------------------------------------------------
<<< Pit File Start >>>
----------------------------------------------------------
----------------------------------------------------------
<<< PIT File Header Information >>>
----------------------------------------------------------
Header Magic: 0x12349876 (4 Bytes)
Entry Count: 15 (4 Bytes)
----------------------------------------------------------
Dummy Data #1 (In String and Hexadecimal Format):
----------------------------------------------------------
String:
Hexadecimal: 00000000
----------------------------------------------------------
Dummy Data #2 (In String and Hexadecimal Format):
----------------------------------------------------------
String:
Hexadecimal: 00000000
----------------------------------------------------------
Dummy Data #3 (In String and Hexadecimal Format):
----------------------------------------------------------
String:
Hexadecimal: 00000000
----------------------------------------------------------
Dummy Data #4 (In String and Hexadecimal Format):
----------------------------------------------------------
String:
Hexadecimal: 00000000
----------------------------------------------------------
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: 0
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size:
Block Count:
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: GANG
Flash FileName: emmc.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xA0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 1
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size:
Block Count:
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash FileName: boot.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x124
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 4
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 8,192
Block Count: 40,960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash FileName: efs.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x1A8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 2
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size: 49,152
Block Count: 2,560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL1
Flash FileName: Sbl.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x22C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 3
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size: 53,248
Block Count: 2,560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL2
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x2B0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 5
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size: 57,344
Block Count: 16,384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash FileName: param.lfs
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x334
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 6
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size: 73,728
Block Count: 16,384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: KERNEL
Flash FileName: zImage
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x3B8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 7
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size: 90,112
Block Count: 16,384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x43C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 8
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 106,496
Block Count: 409,600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash FileName: cache.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x4C0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 9
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size: 516,096
Block Count: 32,768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEM
Flash FileName: modem.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x544
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 10
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 6,488,064
Block Count: 1,744,896
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FACTORYFS
Flash FileName: factoryfs.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x5C8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 11
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 8,232,960
Block Count: 4,194,304
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DATAFS
Flash FileName: data.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x64C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 12
Attribute: 2 (STL)
Update Attribute: 0 (UNKNOWN)
Block Size: 12,427,264
Block Count: 17,293,312
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: UMS
Flash FileName: ums.rfs
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x6D0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 13
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 29,720,576
Block Count: 1,048,576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash FileName: hidden.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x754
----------------------------------------------------------
Binary Type: 1 (COM. PROCESSOR)
Device Type: 1 (FILE / FAT)
Identifier: 9
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size:
Block Count:
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name:
Flash FileName:
FOTA FileName:
----------------------------------------------------------
<<< Pit File End >>>
----------------------------------------------------------
the man told me he double size the /data so it works...
Seems u r now on a roller coaster
doctor_droid said:
Seems u r now on a roller coaster
Click to expand...
Click to collapse
Ithink the space will not come back ...
coeo91 said:
Ithink the space will not come back ...
Click to expand...
Click to collapse
Good one :laugh: :laugh: