[Q] kernel compiling,zImage packing and unpacking - Android Software/Hacking General [Developers Only]

[Q] kernel compiling,zImage packing and unpacking - Android Software/Hacking General [Developers Only]

first time post a thread~
i got a samsung galaxy tab 7' koran version shw-m180l.
1. as i downloaded source code from source.samsung.com. there are two folders: platfrom and kernel . i'm wondering if the source code of initramfs is out there in the platform folder or in the kernel folder?
2.i got a 3M size kernel "zImage" after cross-compile on fedora 16 x86_64 follow the readme instruction posted with the source codes，and tar -cf it then flashed into my tab .but it could not working properly .the official zImage is about 7M size; i guess the reason why mine zImage is so much smaller than the official one is that i didn't packed the initramfs inside.here is thread of unpacking zImage，i could not unpack even the official zImage using unpack-bootimg.pl .and then i tried to modifiy the zImage using a hexEditor ，sadly find no magic number 1F8B for gzip around 2k data。i guess samsung is using an unusual way to packing zImage(just like samsung develeped the rfs file system instead of using the common yaff2 file system)? if then , how can i unpack ing the zImage?
3. thanks to here some one write a tool reading pit file ，the result is the same with what Heimdall reads in download mode ：
file magic = 0x12349876 (expected value)
Unknown data: 0 0 0 0 0
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........................................................] (bootloader.is recovry program here?)
Partition #2
Usual content: partition information table (PIT) （using a partition to store pit?pc's partition table is on mbr~)
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 （what is efs used for?）
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 （what is this for?）
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 （only 3M? the official zImage is more than 7M size ,how could it be flashed into this partition?）
unknown string: [........] （or when flashing (using Odin) Odin will automatically unpacking zImage and flash kernel into this partition ,flash initramfs into other partition(below one ) ?）
partition name = [KERNEL..........................]
file name = [zImage..........................................................] （partition name is kernel）
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 （only 3M ?）
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 = 1711 blocks of 256 * 512 bytes = 224264192 B = 219008 kB = 213 MB （only 213M？）
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 = 20 blocks of 256 * 512 bytes = 2621440 B = 2560 kB = 2 MB （is this mounted as /data ?only 2M？）
unknown string: [........]
partition name = [DBDATAFS........................]
file name = [dbdata.rfs......................................................]
Partition #11
Usual content: cache.rfs （cache ，like swap of linux ?）
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 （the radio?to surport communication ?）
partition entry type: 0 0 (normal partition)
ID = 0x8;
flags = 0;
unknown: 0
size = 1 blocks of 256 * 512 bytes = 131072 B = 128 kB = 0 MB
unknown string: [........]
partition name = [MODEM...........................]
file name = [modem.bin.......................................................]
Partition #13
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 #14
Usual content: Unknown
partition entry type: 0 2 (unknown value)
ID = 0;
flags = 0;
unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [........]
partition name = [MOVINAND........................]
file name = [movinand.mst....................................................]
4. adb shell df ：
# df
Filesystem Size Used Free Blksize
/dev 221M 76K 221M 4096
/mnt/.lfs: Function not implemented
/mnt/asec 221M 0K 221M 4096
/mnt/obb 221M 0K 221M 4096
/app-cache 12M 0K 12M 4096
/data 485M 314M 171M 4096
/cache 30M 4K 30M 4096
/system 410M 294M 115M 4096
/efs 5M 10K 5M 1024
the size is obviously different from the pit says? which one wrong ?
thank for any information and answer~

Related

[REF][INFO] SCH-I535 Partition Table

Google found this for me somewhere...
So I thought I'll share it with you. Not sure if this has been posted before, but I didn't find it in any search here.
I believe it's for the US SGS3 (SCH-I535), but I am not 100%, only ~85% sure.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@mods: Not sure this is the right place to post this, please move to appropriate place if necessary.
If you're looking for the 32 GB PIT file, you can look in this thread.
If you're looking for the GT-I9300 partition table, look in the thread:
"[REF] GT-I9300 PIT and Flash Analysis [WIP]"

E:V:A said:
Google found this for me somewhere...
So I thought I'll share it with you. Not sure if this has been posted before, but I didn't find it in any search here.
I believe it's for the US SGS3 (SCH-I535), but I am not 100%, only ~85% sure.
@mods: Not sure this is the right place to post this, please move to appropriate place if necessary.
If you're looking for the 32 GB PIT file, you can look in this thread.
Click to expand...
Click to collapse
Thank you for the table dude!
Sent from my SCH-I535 using xda app-developers app

Hey,
Is there a way to extract this kind of informations on a working device ? (i'm interested in HEX values for sectors)

vache said:
Hey,
Is there a way to extract this kind of informations on a working device ? (i'm interested in HEX values for sectors)
Click to expand...
Click to collapse
Check here: http://forum.xda-developers.com/showpost.php?p=30618458&postcount=57
You should be able to convert those bite sizes to hex (also, the table above has a column for hex and the number of sectors in each partition...)
I that what you're looking for?

In fact i want to find fist sector number for each partition to be able to write on it and try to restore my phone. (A bit off topic cause it's not a Samsung phone, but also using MSM8960)

For further details about Android partitions, I have just started the partition mega thread:
"[DEV][REF] El Grande Partition Table Reference"
Enjoy!

E:V:A said:
For further details about Android partitions, I have just started the partition mega thread:
"[DEV][REF] El Grande Partition Table Reference"
Enjoy!
Click to expand...
Click to collapse
You, sir, are big pimpin'. Thanks
Sent from my SCH-I535 using xda app-developers app

E:V:A said:
For further details about Android partitions, I have just started the partition mega thread:
"[DEV][REF] El Grande Partition Table Reference"
Enjoy!
Click to expand...
Click to collapse
You're missing a few mmc blocks for the SCA-I535 (d2vzw). Here they are, but I hve no idea what they do:
Code:
/dev/block/mmcblk0boot0
/dev/block/mmcblk0boot1
/dev/block/mmcblk1p1
/dev/block/mmcblk1p2
The latter two blocks suggest a second eMMC chip with its own NAND storage.
I working on a tool that backs up the SCH-I535 directly to your computer using adb. You can find it HERE. For now, Its only setup for partitions and data that one might use in recovery like CWM or TWRP or even ODIN. I haven't iterated out all the blocks into backup code yet, but I am working on it. I hope to have this list:
Code:
## BLOCK_LIST ##
# Conventions for the list o block are as follows
# [VAR_NAME]="/dev/blockmmcblk#p##" #-> [Known As] ([FS], [mount point if visible], [description]) == [odin img file]
MOD_BLK="/dev/block/mmcblk0p1" #-> CDMA Modem (vfat, mounts at /firmware, its the CDMA modem) == NON-HLOS.bin
SB1_BLK="/dev/block/mmcblk0p2" #-> sbl1 (samsung proprietary fs, sammys odd way of booting part1) == sbl1.mbn
SB2_BLK="/dev/block/mmcblk0p3" #-> sbl2 (samsung proprietary fs, sammys odd way of booting part2) == sbl2.mbn
SB3_BLK="/dev/block/mmcblk0p4" #-> sbl3 (samsung proprietary fs, sammys odd way of booting part3) == sbl3.mbn
ABT_BLK="/dev/block/mmcblk0p5" #-> aboot (unknown fs, this is the bootloader) == aboot.mbn
RPM_BLK="/dev/block/mmcblk0p6" #-> rpm (unknown fs, something to do with the radio) == rpm.mbn
BOT_BLK="/dev/block/mmcblk0p7" #-> boot (yaffs2, boot image contains the kernel) == boot.img
STZ_BLK="/dev/block/mmcblk0p8" #-> tz (porbably samsung proprietary fs, samsungs "Trust Zone" referenced in the sbl boot process) == tz.mbn
PAD_BLK="/dev/block/mmcblk0p9" #-> pad (unknown fs, aka PIT )
PRM_BLK="/dev/block/mmcblk0p10" #-> param (unknown fs, pretty much empty exept for one octet)
EFS_BLK="/dev/block/mmcblk0p11" #-> /efs (ext4, mounts at /efs, has device info like IMEI and MEID)
LT1_BLK="/dev/block/mmcblk0p12" #-> modemst1 (unknown fs, LTE modem 1)
LT2_BLK="/dev/block/mmcblk0p13" #-> modemst2 (unknown fs, LTE modem 2)
SYS_BLK="/dev/block/mmcblk0p14" #-> /system (ext4, everything under /system) == system.img.ext4
DAT_BLK="/dev/block/mmcblk0p15" #-> userdata (ext4. mounts at /data, contains internal sdcard as well at /data/media)
PST_BLK="/dev/block/mmcblk0p16" #-> /persist && /tombstones (ext4, contains very little data) == persist.img.ext4
CHE_BLK="/dev/block/mmcblk0p17" #-> /cache (ext4, its the cache baby) == cache.img.ext4
REC_BLK="/dev/block/mmcblk0p18" #-> recovery (ext4??, recovery image like CWM and TWRP?) == recovery.img
OTA_BLK="/dev/block/mmcblk0p19" #-> fota (ext4, found at /cache/fota, its where OTA updates are stored)
BAK_BLK="/dev/block/mmcblk0p20" #-> backup (unknown fs, where factory reset images are stored?)
FSG_BLK="/dev/block/mmcblk0p21" #-> fsg (unknown fs, may contain files used in factory wipe, somehow linked to the grow partition)
SSD_BLK="/dev/block/mmcblk0p22" #-> ssd (unknown fs maybe ramfs, "Secure Software Download" don't know what its used for)
GRW_BLK="/dev/block/mmcblk0p23" #-> grow (unknown fs, i think this has something to do with ext4 sparse images)
# WTF!?!?!?!?!?!!???
DK1_BLK="/dev/block/mmcblk0boot0" #-> may have something to do with booting (duh, but what)
DK2_BLK="/dev/block/mmcblk0boot1" #-> may have something to do with booting (duh, but what)
DK3_BLK="/dev/block/mmcblk1p1" #-> no idea
DK4_BLK="/dev/block/mmcblk1p2" #-> no idea
# NOTES:
# samsung seems to refer to 4 types of file systems; cgroup, ecryptfs, ext4, fuse
# could ecryptfs be the same as samsungs proprietary file system?
## END_BLOCK_LIST ##
Included in the tool, as options to backup. So far I have working code for System, Data (makes a tar and skips /data/media), Recovery, Userdata (HUGE), Modemst1, Modemst2, CDMA modem, Cache and Boot. But I do want to have all mmc blocks as options because I need a disaster recovery plan as well.
There's still alot of work to be done on it, but for now I use it to back up my device before flashing a rom. Saves on internal storage.
I'll try and convert my block list to you format used in the EL GRANDE Partition Table Reference as soon as possible. I dunno if you'll need it though. I do have alot of knowledge on GPT (GUID Partition Table) formatted storage as well as how EFI vs MBR can work withing such a table. But I can discuss that on the other thread.
I've read what you have so far in that thread and its very helpful.
Ta,
ALQI

Could you follow the instructions in post #2, of the thread I posted above, to obtain an output of parted and fdisk , for both mmcblk0 and mmcblk1?

E:V:A said:
Could you follow the instructions in post #2, of the thread I posted above, to obtain an output of parted and fdisk , for both mmcblk0 and mmcblk1?
Click to expand...
Click to collapse
Not a problem mate. I hope this fits your format.
Device info:
Code:
General Device Name: Samsung Galaxy S3
Manufacturer Product Name: SCH-I535
Processor: Snapdragon S4plus
AOS version: Android JB 4.1.1
Radio FW version: I535VRLHD
System FW version: I535VZWBLI5
Service Provider/ Branding: Verizon
Country: USA
ROM: Almost Stock JellyBean I535VRBLI5 (my own cooking from dsixda's andoid kitchen, added bash binary, nano, busybox and root)
fidsk output for mmcblk0:
Code:
sh-4.2# fdisk -l /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk0: 61071360 sectors, 58.2M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 61059087
Number Start (sector) End (sector) Size Code Name
1 8192 131071 120K 0700 modem
2 131072 131327 256 0700 sbl1
3 131328 131839 512 0700 sbl2
4 131840 132863 1024 0700 sbl3
5 132864 136959 4096 0700 aboot
6 136960 137983 1024 0700 rpm
7 137984 158463 20480 0700 boot
8 158464 159487 1024 0700 tz
9 159488 160511 1024 0700 pad
10 160512 180991 20480 0700 param
11 180992 208895 27904 0700 efs
12 208896 215039 6144 0700 modemst1
13 215040 221183 6144 0700 modemst2
14 221184 3293183 3000K 0700 system
15 3293184 59252735 53.3M 0700 userdata
16 59252736 59269119 16384 0700 persist
17 59269120 60989439 1680K 0700 cache
18 60989440 61009919 20480 0700 recovery
19 61009920 61030399 20480 0700 fota
20 61030400 61042687 12288 0700 backup
21 61042688 61048831 6144 0700 fsg
22 61048832 61048847 16 0700 ssd
23 61048848 61059087 10240 0700 grow
fdisk for those odd mmcblk0boot# devs:
Code:
sh-4.2# fdisk -l /dev/block/mmcblk0boot0
Disk /dev/block/mmcblk0boot0: 2 MB, 2097152 bytes
4 heads, 16 sectors/track, 64 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0boot0 doesn't contain a valid partition table
sh-4.2# fdisk -l /dev/block/mmcblk0boot1
Disk /dev/block/mmcblk0boot1: 2 MB, 2097152 bytes
4 heads, 16 sectors/track, 64 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0boot1 doesn't contain a valid partition table
NOTE: I'm still not sure what these mmcblk0boot# blocks are, but they are there in the file system under /dev/block/ as well as /dev/block/platform/by-name.
fdisk output mmcblk1:
Code:
sh-4.2# fdisk -l /dev/block/mmcblk1
Disk /dev/block/mmcblk1: 15.9 GB, 15931539456 bytes
255 heads, 63 sectors/track, 1936 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 1 1872 15032320 b Win95 FAT32
/dev/block/mmcblk1p2 1872 1937 524288 82 Linux swap
NOTE: mmcblk1 is the external sdcard (i'm dumb cause I thought it was a seperate eMMC chip, but its just plain old MMC) THat little swap space is left over from when I had the OG Droid.
parted output for mmcblk0:
Code:
sh-4.2# parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? Ignore
Ignore
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra 12239 blocks) or
continue with the current setting?
Fix/Ignore? Ignore
Ignore
Model: MMC MBG8FB (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 67.1MB 62.9MB modem
2 67.1MB 67.2MB 131kB sbl1
3 67.2MB 67.5MB 262kB sbl2
4 67.5MB 68.0MB 524kB sbl3
5 68.0MB 70.1MB 2097kB aboot
6 70.1MB 70.6MB 524kB rpm
7 70.6MB 81.1MB 10.5MB boot
8 81.1MB 81.7MB 524kB tz
9 81.7MB 82.2MB 524kB pad
10 82.2MB 92.7MB 10.5MB param
11 92.7MB 107MB 14.3MB ext4 efs
12 107MB 110MB 3146kB modemst1
13 110MB 113MB 3146kB modemst2
14 113MB 1686MB 1573MB ext4 system
15 1686MB 30.3GB 28.7GB ext4 userdata
16 30.3GB 30.3GB 8389kB ext4 persist
17 30.3GB 31.2GB 881MB ext4 cache
18 31.2GB 31.2GB 10.5MB recovery
19 31.2GB 31.2GB 10.5MB fota
20 31.2GB 31.3GB 6291kB backup
21 31.3GB 31.3GB 3146kB fsg
22 31.3GB 31.3GB 8192B ssd
23 31.3GB 31.3GB 5243kB grow
(parted)
NOTE: The second warning with parted, is because the device uses a hybrid MBR/GPT table (gdisk shows us this). This is kinda like dual booting a Mac with Windows and Mac OS X. Also, the "backup" error is because the gpt table backup is in "pad" (aka PIT).
WARNING: Be careful with parted, make sure you tell it to "Ignore" and errors it might find. Also you have to type "quit" to get it to exit from interactive mode.
parted output for mmcblk0boot0
Code:
sh-4.2# parted /dev/block/mmcblk0boot0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0boot0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
Error: /dev/block/mmcblk0boot0: unrecognised disk label
(parted)
NOTE: No need to run parted on mmcblk1 (cause its the external sdcard) nor mmcblk0boot# cause its not part of the gpt. Same goes for gdisk.
gdisk output for mmcblk0
Code:
sh-4.2# gdisk -l /dev/block/mmcblk0
GPT fdisk (gdisk) version 0.8.4
Caution: invalid backup GPT header, but valid main header; regenerating
backup header from main header.
Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
on the recovery & transformation menu to examine the two tables.
Warning! One or more CRCs don't match. You should repair the disk!
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: damaged
****************************************************************************
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
****************************************************************************
Disk /dev/block/mmcblk0: 61071360 sectors, 29.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 61059087
Partitions will be aligned on 16-sector boundaries
Total free space is 8158 sectors (4.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 8192 131071 60.0 MiB 0700 modem
2 131072 131327 128.0 KiB FFFF sbl1
3 131328 131839 256.0 KiB FFFF sbl2
4 131840 132863 512.0 KiB FFFF sbl3
5 132864 136959 2.0 MiB FFFF aboot
6 136960 137983 512.0 KiB FFFF rpm
7 137984 158463 10.0 MiB FFFF boot
8 158464 159487 512.0 KiB FFFF tz
9 159488 160511 512.0 KiB FFFF pad
10 160512 180991 10.0 MiB 8300 param
11 180992 208895 13.6 MiB 8300 efs
12 208896 215039 3.0 MiB FFFF modemst1
13 215040 221183 3.0 MiB FFFF modemst2
14 221184 3293183 1.5 GiB 8300 system
15 3293184 59252735 26.7 GiB 8300 userdata
16 59252736 59269119 8.0 MiB 8300 persist
17 59269120 60989439 840.0 MiB 8300 cache
18 60989440 61009919 10.0 MiB FFFF recovery
19 61009920 61030399 10.0 MiB FFFF fota
20 61030400 61042687 6.0 MiB 8300 backup
21 61042688 61048831 3.0 MiB FFFF fsg
22 61048832 61048847 8.0 KiB FFFF ssd
23 61048848 61059087 5.0 MiB 8300 grow
Again, be very careful when running these disk utilities because they are not meant to handle a hybrid boot. Samsung's odd way of booting makes this kind of analysis difficult because of the prorieray fs they use for sbl1 through sbl3.
Click to expand...
Click to collapse
Wow that's alot of formatting.
Ta,
ALQI

Thanks a lot! In particular to remind people of the "warnings". I'll add that to the other thread.

Hey guys,
I have a I535 S3 that was hard bricked because of a bad flash, I want to try and repair it with JTAG but I don't have the necessary partition boot files...and it's not a supported version either.
Does anybody have a backup of the first 10 partitions from Modem to Param in .bin format?
I know it's possible to do such a backup with adb. or can somebody point me in the right direction?
Thank you!

Sure, I'll dd those for you tomorrow and pm you a Dropbox link.
For the first 10 partitions it shouldn't matter, but do you have a 16GB or 32Gb?
Sent from my SCH-I535 using xda app-developers app

It's the 16Gb version.
Thank you very much... You're a life savor!
Sent from my SGH-I897 using Tapatalk 2

PM sent.

Thank you!
Got them.. Hopefully it works!
Sent from my SGH-I897 using Tapatalk 2

E:V:A said:
Thanks a lot! In particular to remind people of the "warnings". I'll add that to the other thread.
Click to expand...
Click to collapse
As this is GTP parition it uses differing handles for the partition type
here is a example snip of the qualcomm partition.xml for a gtp partition
Code:
<partition label="modem" size_in_kb="65536" type="EBD0A0A2-B9E5-4433-87C0-68B6B72699C7" bootable="false" readonly="true" filename="NON-HLOS.bin"/>
<partition label="sbl1" size_in_kb="128" type="[COLOR="Red"][B]DEA0BA2C-CBDD-4805-B4F9-F428251C3E98[/B][/COLOR]" bootable="false" readonly="false" filename="sbl1.mbn"/>
<partition label="sbl2" size_in_kb="256" type="8C6B52AD-8A9E-4398-AD09-AE916E53AE2D" bootable="false" readonly="false" filename="sbl2.mbn"/>
<partition label="sbl3" size_in_kb="512" type="05E044DF-92F1-4325-B69E-374A82E97D6E" bootable="false" readonly="false" filename="sbl3.mbn"/>
<partition label="aboot" size_in_kb="512" type="400FFDCD-22E0-47E7-9A23-F16ED9382388" bootable="false" readonly="false" filename="emmc_appsboot.mbn"/>
<partition label="rpm" size_in_kb="512" type="098DF793-D712-413D-9D4E-89D711772228" bootable="false" readonly="false" filename="rpm.mbn"/>
<partition label="boot" size_in_kb="10240" type="20117f86-E985-4357-B9EE-374BC1D8487D" bootable="false" readonly="true" filename="boot.img" />
<partition label="tz" size_in_kb="512" type="A053AA7F-40B8-4B1C-BA08-2F68AC71A4F4" bootable="false" readonly="false" filename="tz.mbn"/>
<partition label="pad" size_in_kb="1" type="004A6838-062A-44DF-8152-4F340C05225D" bootable="false" readonly="false" filename="" />
<partition label="modemst1" size_in_kb="3072" type="2013373E-1AC4-4131-B0F8-9158F9654F4F" bootable="false" readonly="false" filename="" />
<partition label="modemst2" size_in_kb="3072" type="2013373E-1AC4-4131-B0F8-9158F9654F4F" bootable="false" readonly="false" filename="" />
<partition label="system" size_in_kb="262144" type="0FC63DAF-8483-4772-8E79-3D69D8477DE4" bootable="false" readonly="true" filename="system.img.ext4" sparse="true"/>
Click to expand...
Click to collapse
could we see if my compiled binaries for gtp partitions return the UUID for type ?
Original Post http://forum.xda-developers.com/showpost.php?p=36019312&postcount=13
Binaries
http://www.sendspace.com/file/5b3jdc
Example output from partx ( non gtp partition, i dont have gtp partition)
Code:
[email protected]:/ # /data/test/partx
Usage:
partx [-a|-d|-s] [--nr <n:m> | <partition>] <disk>
Options:
-a, --add add specified partitions or all of them
-d, --delete delete specified partitions or all of them
-l, --list list partitions (DEPRECATED)
-s, --show list partitions
-b, --bytes print SIZE in bytes rather than in human readable format
-g, --noheadings don't print headings for --show
-n, --nr <n:m> specify the range of partitions (e.g. --nr 2:4)
-o, --output <type> define which output columns to use
-P, --pairs use key="value" output format
-r, --raw use raw output format
-t, --type <type> specify the partition type (dos, bsd, solaris, etc.)
-v, --verbose verbose mode
-h, --help display this help and exit
-V, --version output version information and exit
Available columns (for --show, --raw or --pairs):
NR partition number
START start of the partition in sectors
END end of the partition in sectors
SECTORS number of sectors
SIZE human readable size
NAME partition name
UUID partition UUID
TYPE partition type hex or uuid
FLAGS partition flags
SCHEME partition table type (dos, gpt, ...)
For more details see partx(8).
1|[email protected]:/ # /data/test/partx -l /dev/block/mmcblk0
# 1: 1- 204800 ( 204800 sectors, 104 MB)
# 2: 204801- 205800 ( 1000 sectors, 0 MB)
# 3: 205801- 208800 ( 3000 sectors, 1 MB)
# 4: 208801- 30777343 ( 30568543 sectors, 15651 MB)
# 5: 212992- 213991 ( 1000 sectors, 0 MB)
# 6: 221184- 225279 ( 4096 sectors, 2 MB)
# 7: 229376- 234375 ( 5000 sectors, 2 MB)
# 8: 237568- 258047 ( 20480 sectors, 10 MB)
# 9: 262144- 263143 ( 1000 sectors, 0 MB)
#10: 270336- 271335 ( 1000 sectors, 0 MB)
#11: 278528- 279527 ( 1000 sectors, 0 MB)
#12: 286720- 307199 ( 20480 sectors, 10 MB)
#13: 311296- 511999 ( 200704 sectors, 102 MB)
#14: 516096- 522239 ( 6144 sectors, 3 MB)
#15: 524288- 530431 ( 6144 sectors, 3 MB)
#16: 532480- 538623 ( 6144 sectors, 3 MB)
#17: 540672- 741375 ( 200704 sectors, 102 MB)
#18: 745472- 751615 ( 6144 sectors, 3 MB)
#19: 753664- 759807 ( 6144 sectors, 3 MB)
#20: 761856- 767999 ( 6144 sectors, 3 MB)
#21: 770048- 790527 ( 20480 sectors, 10 MB)
#22: 794624- 815103 ( 20480 sectors, 10 MB)
#23: 819200- 839679 ( 20480 sectors, 10 MB)
#24: 843776- 3911679 ( 3067904 sectors, 1570 MB)
#25: 3915776- 8114175 ( 4198400 sectors, 2149 MB)
#26: 8118272- 8736767 ( 618496 sectors, 316 MB)
#27: 8740864- 9005055 ( 264192 sectors, 135 MB)
#28: 9011200- 10035199 ( 1024000 sectors, 524 MB)
#29: 10035200- 30777343 ( 20742144 sectors, 10619 MB)
[email protected]:/ #
lsblk output
Code:
[email protected]:/ # /data/test/lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 2.1M 0 loop
`-278cb90965c39ee2acfea003ec39e4f5 (dm-0)
254:0 0 2.1M 0 dm /mnt/asec/com.androirc-1
loop1 7:1 0 5.1M 0 loop
`-ce28924bd3284f292fdd7955925746bc (dm-1)
254:1 0 5.1M 0 dm /mnt/asec/com.quoord.tapatalkxda.activity-
loop2 7:2 0 16.3M 0 loop
`-2ef6fb57bc43988a90c9add8bc514237 (dm-2)
254:2 0 16.3M 0 dm /mnt/asec/com.loumasoft.amiga500musiccolle
mmcblk0 179:0 0 14.7G 0 disk
|-mmcblk0p1 179:1 0 100M 0 disk
|-mmcblk0p2 179:2 0 500K 0 disk
|-mmcblk0p3 179:3 0 1.5M 0 disk
|-mmcblk0p4 179:4 0 1K 0 disk
|-mmcblk0p5 179:5 0 500K 0 disk
|-mmcblk0p6 179:6 0 2M 0 disk
|-mmcblk0p7 179:7 0 2.5M 0 disk
|-mmcblk0p8 179:8 0 10M 0 disk
|-mmcblk0p9 179:9 0 500K 0 disk
|-mmcblk0p10 179:10 0 500K 0 disk
|-mmcblk0p11 179:11 0 500K 0 disk
|-mmcblk0p12 179:12 0 10M 0 disk
|-mmcblk0p13 179:13 0 98M 0 disk
|-mmcblk0p14 179:14 0 3M 0 disk
|-mmcblk0p15 179:15 0 3M 0 disk
|-mmcblk0p16 179:16 0 3M 0 disk
|-mmcblk0p17 179:17 0 98M 0 disk
|-mmcblk0p18 179:18 0 3M 0 disk
|-mmcblk0p19 179:19 0 3M 0 disk
|-mmcblk0p20 179:20 0 3M 0 disk
|-mmcblk0p21 179:21 0 10M 0 disk
|-mmcblk0p22 179:22 0 10M 0 disk
|-mmcblk0p23 179:23 0 10M 0 disk
|-mmcblk0p24 179:24 0 1.5G 0 disk
|-mmcblk0p25 179:25 0 2G 0 disk
|-mmcblk0p26 179:26 0 302M 0 disk
|-mmcblk0p27 179:27 0 129M 0 disk
|-mmcblk0p28 179:28 0 500M 0 disk
`-mmcblk0p29 179:29 0 9.9G 0 disk
mmcblk1 179:32 0 14.4G 0 disk
`-mmcblk1p1 179:33 0 14.4G 0 disk
[email protected]:/ #
sample output from blkid
Code:
blkid from util-linux 2.22 (libblkid 2.22.0, 04-Sep-2012)
Usage:
blkid -L <label> | -U <uuid>
blkid [-c <file>] [-ghlLv] [-o <format>] [-s <tag>]
[-t <token>] [<dev> ...]
blkid -p [-s <tag>] [-O <offset>] [-S <size>]
[-o <format>] <dev> ...
blkid -i [-s <tag>] [-o <format>] <dev> ...
Options:
-c <file> read from <file> instead of reading from the default
cache file (-c /dev/null means no cache)
-d don't encode non-printing characters
-h print this usage message and exit
-g garbage collect the blkid cache
-o <format> output format; can be one of:
value, device, export or full; (default: full)
-k list all known filesystems/RAIDs and exit
-s <tag> show specified tag(s) (default show all tags)
-t <token> find device with a specific token (NAME=value pair)
-l look up only first device with token specified by -t
-L <label> convert LABEL to device name
-U <uuid> convert UUID to device name
-v print version and exit
<dev> specify device(s) to probe (default: all devices)
Low-level probing options:
-p low-level superblocks probing (bypass cache)
-i gather information about I/O limits
-S <size> overwrite device size
-O <offset> probe at the given offset
-u <list> filter by "usage" (e.g. -u filesystem,raid)
-n <list> filter by filesystem type (e.g. -n vfat,ext3)
4|[email protected]:/ # /data/test/blkid
/dev/block/mmcblk0: PTTYPE="dos"
/dev/block/mmcblk0p13: SEC_TYPE="msdos" UUID="7365-DAB3" TYPE="vfat"
/dev/block/mmcblk0p17: SEC_TYPE="msdos" UUID="29B2-ACBF" TYPE="vfat"
/dev/block/mmcblk0p21: UUID="57f8f4bc-abf4-0000-675f-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p24: UUID="c63c0c30-700c-4874-9acd-fd507d02000a" TYPE="ext4"
/dev/block/mmcblk0p25: UUID="36caf8ff-15bf-4c24-92e0-0c84a21f3b0c" TYPE="ext4"
/dev/block/mmcblk0p26: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p27: UUID="57f8f4bc-abf4-0000-675f-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p28: UUID="57f8f4bc-abf4-0000-675f-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p29: UUID="887F-1DF5" TYPE="vfat"
/dev/block/mmcblk1: PTTYPE="dos"
/dev/block/mmcblk1p1: UUID="64A1-1B57" TYPE="vfat"
[email protected]:/ #
most will use sgdisk/partx on gtp based partitions. sgdisk also supports the partition info cloning like sfdisk does.
See sfdisk in util-linux sources for more info
darkspr1te

letinsh said:
PM sent.
Click to expand...
Click to collapse
By the way.. Those partitions worked great for jtag.
Thanks again!
Sent from my I897 AoCP CP 4.6

spagman72 said:
Hey guys,
I have a I535 S3 that was hard bricked because of a bad flash, I want to try and repair it with JTAG but I don't have the necessary partition boot files...and it's not a supported version either.
Does anybody have a backup of the first 10 partitions from Modem to Param in .bin format?
I know it's possible to do such a backup with adb. or can somebody point me in the right direction?
Thank you!
Click to expand...
Click to collapse
Hey, I have the sch-i535 Verizon. Do you want me to give it to you?

Israelleite said:
Hey, I have the sch-i535 Verizon. Do you want me to give it to you?
Click to expand...
Click to collapse
spagman72 said:
By the way.. Those partitions worked great for jtag.
Thanks again!
Sent from my I897 AoCP CP 4.6
Click to expand...
Click to collapse
already got him taken care of

Galaxy Camera Partitions

Hey, I was able to make changes to the Heimdall repository to easily gain access to flashing with Linux to the Galaxy Camera. This is important because this is the only way to get a PIT file unless Samsung themselves make changes and issue a new pit.
Here is the PIT for the Samsung Galaxy Camera. http://forum.xda-developers.com/attachment.php?attachmentid=1487728&stc=1&d=1353110552
Here is the partition table:
Code:
Entry Count: 17
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 30797
Unknown 4: 0
Unknown 5: 0
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 80
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size: 0
Partition Block Count: 1734
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOTLOADER
Flash Filename: sboot.bin
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 81
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 1734
Partition Block Count: 312
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TZSW
Flash Filename: tz.img
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: camera.pit
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 50
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 8192
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA0
Flash Filename: -
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 16384
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA1
Flash Filename: -
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 24576
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 65536
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.bin
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 81920
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 98304
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 114688
Partition Block Count: 65536
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RADIO
Flash Filename: modem.bin
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 180224
Partition Block Count: 2097152
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 2277376
Partition Block Count: 3145728
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 5423104
Partition Block Count: 737280
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 6160384
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OTA
Flash Filename: -
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 6176768
Partition Block Count: 409600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TDATA
Flash Filename: -
FOTA Filename:
--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 6586368
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img
FOTA Filename: remained
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
[email protected]:~/code/heimdall/Heimdall/heimdall$
I wanted to log this here for others to use.
To reproduce the changes to Heimdall for the Galaxy Camera, you simply need to "git clone" the heimdall repo located here: https://github.com/Benjamin-Dobell/Heimdall
Then find the line that says kPIDGalaxyS2 in /Heimdall/heimdall/source/BridgeManager.h:
Code:
kPidGalaxyS = 0x6601,
[B]kPidGalaxyS2 = 0x685d,[/B]
kPidDroidCharge = 0x68C3
Then make Heimdall as usual. It's able to pull the Partition Information Table easily.

... And root achieved under Linux. I spoke to Chainfire about CF AutoRoot. He requested a recovery.img. He then posted the binary here. http://download.chainfire.eu/283/CF-Root/CF-Auto-Root/CF-Auto-Root-gd1-ekgc100.zip
I extracted all files from that binary, built heimdall as above and was able to flash. Heimdall will be built for this device soon. I've submitted a ticket.
Code:
[email protected]:~/Desktop/heimdall$ /usr/local/bin/heimdall flash --cache ./cache.img --recovery ./recovery.img
Heimdall v1.4 RC1
Copyright (c) 2010-2012, 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...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading CACHE
100%
CACHE upload successful
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
[email protected]:~/Desktop/heimdall$ adb shell
[email protected]:/ $ su
[email protected]:/ #

AdamOutler said:
Here is the partition table:
Click to expand...
Click to collapse
How did you get that?
I'll be posting the table (based on this) in my partition table thread. But it would be better to obtain the output of the standard partition commands...

Actually that list above, makes little sense. Where are the mount points and "block size" is probably not a block size etc... I'd much rather see the output from these commands...
EDIT:
BTW. Have you managed to rip this thing apart yet? I'd love to see some internal pictures...

Hey Adam thanks for this but one question, should I use this pit file with heimdall or with odin, in both cases which firmware gave you this pit partitioning( on the mexican sgs sometimes different firmwares had different pit)
thanks!

I set up a job to analyze PIT files over at http://jenkins.CASUAL-Dev.com and you can analyze PIT files with more accuracy there.
This is my own breed of Print-Pit.
Code:
PIT Name: Mx
Entry Count: 17
File Type: COM_TAR2
--- Entry #0 ---
ID: 80 Partition Name: BOOTLOADER
Filename: sboot.bin param: md5
Block Size: 1734 (887.8kB)
Block range: 0 - 1733 (hex 0x0 - 0x6c5)
PartType: 2 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The BOOTLOADER partition, identified as partition number 80, is 887.8kB in size. It carries a Basic format and Bootloader data type. The partition resides on the AP EMMC. It identifies itself to Odin as sboot.bin param: md5.
--- Entry #1 ---
ID: 81 Partition Name: TZSW
Filename: tz.img param: md5
Block Size: 312 (159.7kB)
Block range: 1734 - 2045 (hex 0x6c6 - 0x7fd)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The TZSW partition, identified as partition number 81, is 159.7kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as tz.img param: md5.
--- Entry #2 ---
ID: 70 Partition Name: PIT
Filename: camera.pit
Block Size: 16 (8.2kB)
Block range: 34 - 49 (hex 0x22 - 0x31)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The PIT partition, identified as partition number 70, is 8.2kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as camera.pit.
--- Entry #3 ---
ID: 71 Partition Name: MD5HDR
Filename: md5.img param: in.md5
Block Size: 2048 (1.0MB)
Block range: 50 - 2097 (hex 0x32 - 0x831)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The MD5HDR partition, identified as partition number 71, is 1.0MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as md5.img param: in.md5.
--- Entry #4 ---
ID: 1 Partition Name: BOTA0
Filename: -
Block Size: 8192 (4.2MB)
Block range: 8192 - 16383 (hex 0x2000 - 0x3fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The BOTA0 partition, identified as partition number 1, is 4.2MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC.
--- Entry #5 ---
ID: 2 Partition Name: BOTA1
Filename: -
Block Size: 8192 (4.2MB)
Block range: 16384 - 24575 (hex 0x4000 - 0x5fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The BOTA1 partition, identified as partition number 2, is 4.2MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC.
--- Entry #6 ---
ID: 3 Partition Name: EFS
Filename: efs.img param: md5
Block Size: 40960 (21.0MB)
Block range: 24576 - 65535 (hex 0x6000 - 0xffff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The EFS partition, identified as partition number 3, is 21.0MB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as efs.img param: md5.
--- Entry #7 ---
ID: 4 Partition Name: PARAM
Filename: param.bin param: md5
Block Size: 16384 (8.4MB)
Block range: 65536 - 81919 (hex 0x10000 - 0x13fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The PARAM partition, identified as partition number 4, is 8.4MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as param.bin param: md5.
--- Entry #8 ---
ID: 5 Partition Name: BOOT
Filename: boot.img param: md5
Block Size: 16384 (8.4MB)
Block range: 81920 - 98303 (hex 0x14000 - 0x17fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The BOOT partition, identified as partition number 5, is 8.4MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as boot.img param: md5.
--- Entry #9 ---
ID: 6 Partition Name: RECOVERY
Filename: recovery.img param: md5
Block Size: 16384 (8.4MB)
Block range: 98304 - 114687 (hex 0x18000 - 0x1bfff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The RECOVERY partition, identified as partition number 6, is 8.4MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as recovery.img param: md5.
--- Entry #10 ---
ID: 7 Partition Name: RADIO
Filename: modem.bin param: md5
Block Size: 65536 (33.6MB)
Block range: 114688 - 180223 (hex 0x1c000 - 0x2bfff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The RADIO partition, identified as partition number 7, is 33.6MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as modem.bin param: md5.
--- Entry #11 ---
ID: 8 Partition Name: CACHE
Filename: cache.img param: md5
Block Size: 2097152 (1.1GB)
Block range: 180224 - 2277375 (hex 0x2c000 - 0x22bfff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The CACHE partition, identified as partition number 8, is 1.1GB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as cache.img param: md5.
--- Entry #12 ---
ID: 9 Partition Name: SYSTEM
Filename: system.img param: md5
Block Size: 3145728 (1.6GB)
Block range: 2277376 - 5423103 (hex 0x22c000 - 0x52bfff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The SYSTEM partition, identified as partition number 9, is 1.6GB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as system.img param: md5.
--- Entry #13 ---
ID: 10 Partition Name: HIDDEN
Filename: hidden.img param: md5
Block Size: 737280 (377.5MB)
Block range: 5423104 - 6160383 (hex 0x52c000 - 0x5dffff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The HIDDEN partition, identified as partition number 10, is 377.5MB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as hidden.img param: md5.
--- Entry #14 ---
ID: 11 Partition Name: OTA
Filename: -
Block Size: 16384 (8.4MB)
Block range: 6160384 - 6176767 (hex 0x5e0000 - 0x5e3fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
The OTA partition, identified as partition number 11, is 8.4MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC.
--- Entry #15 ---
ID: 12 Partition Name: TDATA param: TA
Filename: - param: erdata.img param: md5
Block Size: 409600 (209.7MB)
Block range: 6176768 - 6586367 (hex 0x5e4000 - 0x647fff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA: param: emained
The TDATA param: TA partition, identified as partition number 12, is 209.7MB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC.
--- Entry #16 ---
ID: 13 Partition Name: USERDATA
Filename: userdata.img
Block Size: 0 (0B)
Block range: 6586368 - 6586367 (hex 0x648000 - 0x647fff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA: remained
The USERDATA partition, identified as partition number 13, is 0B in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as userdata.img. The partition will expand to fill the remainder of the EMMC.
Here's the PIT file: http://d-h.st/3B3
Here's the link where you can analyze a PIT: http://jenkins.casual-dev.com/job/Analyze PIT File/build?delay=0sec

[Request] any method for resizing A13 Tablet partitions?

I have a tablet a13 allwiner , it shared like this
nanda (bootloader) :32 Mb
nandc (system partition) :512 Mb
nandd (data partition) :1.2 Gb
nandg recovery :32 MB
nandj (SD card or internal storage): 1.6Gb
i want to modify size to have (like i found it in other firmware for another tablet based a13 cpu)
512 system
512 data
and 2Gb or above for SDcard
i have extract the original firmware with a10 kitchen and change the content of COMMON _SYS_CONFIG000000.hdr and rebuilding
i have change the file for attempting this size like a want and i see in other firwmare
but after rebuilding and flashing the tablet start with black screen( what happen ?)
the original file :
Code:
[part_num]
num = 9
;------------------------------>nanda, known as bootfs before, includes boot.axf u-boot.bin etc...
[partition0]
class_name = DISK
name = bootloader
size_hi = 0
size_lo = 26384
user_type = 0
ro = 0
;------------------------------>nandb, enviroment for u-boot
[partition1]
class_name = DISK
name = env
size_hi = 0
size_lo = 16384
user_type = 0
ro = 0
;------------------------------>nandc, kernel and ramdisk
[partition2]
class_name = DISK
name = boot
size_hi = 0
size_lo =32768
user_type = 0
ro = 0
;------------------------------>nandd, android real rootfs
[partition3]
class_name = DISK
name = system
size_hi = 0
size_lo = 524288
user_type = 0
ro = 0
;------------------------------>nande, user data
[partition4]
class_name = DISK
name = data
size_hi = 0
size_lo = 1228800 (changed to 524288)
user_type = 0
ro = 0
;------------------------------>nandf, misc
[partition5]
class_name = DISK
name = misc
size_hi = 0
size_lo = 16384
user_type = 0
ro = 0
;------------------------------>nandg, for recovery
[partition6]
class_name = DISK
name = recovery
size_hi = 0
size_lo = 32768
user_type = 0
ro = 0
;------------------------------>nandh, android app cache
[partition7]
class_name = DISK
name = cache
size_hi = 0
size_lo = 262144
user_type = 0
ro = 0
;------------------------------>nandi, data image backup
[partition8]
class_name = DISK
name = databk
size_hi = 0
size_lo = 262144
user_type = 0
ro = 0
;********************************************************************************************************************
; ¹Ì¼þ°üÏÂÔØÎ»ÖÃ £º °ÑÄ³¸ö¹Ì¼þ°üÏÂÔØµ½Ö¸¶¨·ÖÇø, ÏÂÔØ´ÎÊý×î´óÎª7´Î
;
;[downloadi] //¹Ì¼þ°ü0ÏÂÔØÎ»ÖÃ
; part_name = SYSDATAFS //·ÖÇøÃû
; pkt_name = ROOTFS_000000000 //¹Ì¼þ°üÃû³Æ
; verify_file = VERIFY_000000000 //Ð£ÑéÎÄ¼þÃû³Æ
;
; ×¢£º1¡¢ downloadi ±íÊ¾µÚi´ÎÏÂÔØ¹Ì¼þ, download Î¨Ò», Çë²»ÒªËæÒâÐÞ¸Ä
; 2¡¢ part_num Îª·ÖÇøºÅ, ¼´¹Ì¼þÏÂÔØµÄÎ»ÖÃ
; 3¡¢ pkt_name ¹Ì¼þ°üÃû³Æ. ×î´ó³¤¶ÈÎª16byte, ÇÒÃû³Æ¹Ì¶¨. ¿É²Î¿¼"..\\ePDK\workspace\suni\liveclick\image.cfg"
; 4¡¢ verify_file ÎªÐ£ÑéÎÄ¼þÃû³Æ. ¿É²Î¿¼"..\\ePDK\workspace\suni\liveclick\image.cfg"
; 5¡¢ pkt_name ÄÚÈÝ²»Ìî, ±íÊ¾±¾´ÎÏÂÔØÈ¡Ïû. verify_fileÄÚÈÝ²»Ìî, ±íÊ¾²»ÐèÒªÐ£Ñé.
;
; Èç£ºÒª°Ñ¹Ì¼þ°üzdisk.img, ÏÂÔØÔÚµ½SYSDATAFS·ÖÇøÀï¡£ÆäÅäÖÃÎª£º
; [download0]
; part_name = SYSDATAFS
; pkt_name = ROOTFS_000000000
; verify_file = VERIFY_000000000
;********************************************************************************************************************
[down_num]
down_num = 6
[download0]
part_name = bootloader
pkt_name = BOOTLOADER_00000
encrypt = 0
verify_file = VBOOTLOADER_0000
[download1]
part_name = env
pkt_name = ENVIROMENT_00000
encrypt = 0
verify_file = VENVIROMENT_0000
[download2]
part_name = boot
pkt_name = BOOT_00000000000
encrypt = 0
verify_file = VBOOT_0000000000
[download3]
part_name = system
pkt_name = SYSTEM_000000000
encrypt = 0
verify_file = VSYSTEMFS_000000
[download4]
part_name = recovery
pkt_name = RECOVERY_0000000
encrypt = 0
verify_file = VRECOVERYFS_0000
[download5]
part_name = UDISK
pkt_name = DISKFS_000000000
encrypt = 0
is there any way to do it by flashing it with factory firmware and changing the partitions size ?

Not that I know of

Ronny927 said:
Not that I know of
Click to expand...
Click to collapse
i found a rom (for icoo D50 lite) which its parted to 512 system and 512 data i try it by flashing my tablet , and try to rewrite my bootloader, boot.img and restoring system and data but i found only the problem the firmare manage only 9 partition but my original firmware and files manage 10 parition , then my internal storage will be null 0 byte cause boot point on nandj but the last partition is nandi ,
major minor #blocks name
93 0 16384 nanda
93 8 2048 nandb
93 16 32768 nandc
93 24 524288 nandd
93 32 524288 nande
93 40 1024 nandf
93 48 32768 nandg
93 56 262144 nandh
93 64 2494464 nandi
179 0 3872256 mmcblk0
179 1 3868160 mmcblk0p
[email protected]:/ #
Click to expand...
Click to collapse
i do it by moding boot.img all thing is correct only the ft5_ts.so touch screen driver can t be loaded caus the firmware buid 1.45r
i think , it s possible to do it. but what the way to rezise partition with cooking new image .
link for icoo d50 lite http://www.pandawillforum.com/soft/ICOO D50 Lite firmware 20120801.rar
NB : juste i extract the original image and cooking it again without any modif. it aint boot (black screen)

rafik23 said:
i found a rom (for icoo D50 lite) which its parted to 512 system and 512 data i try it by flashing my tablet , and try to rewrite my bootloader, boot.img and restoring system and data but i found only the problem the firmare manage only 9 partition but my original firmware and files manage 10 parition , then my internal storage will be null 0 byte cause boot point on nandj but the last partition is nandi ,
i do it by moding boot.img all thing is correct only the ft5_ts.so touch screen driver can t be loaded caus the firmware buid 1.45r
i think , it s possible to do it. but what the way to rezise partition with cooking new image .
link for icoo d50 lite http://www.pandawillforum.com/soft/ICOO D50 Lite firmware 20120801.rar
NB : juste i extract the original image and cooking it again without any modif. it aint boot (black screen)
Click to expand...
Click to collapse
My first question is why do you want to do this ? If you want a 10 Partition firmware you need the 10 Partition structure... and if you want to load a 9 partition frmware you need the 9 Partition structure....
If you are trying to do this in order to make a particular firmware work on your device i would recommend changing drivers in the one you want to match your hardware and compiing them into a livesuite image for flashing.
If you are trying to mix them for more efficient use of space it likely will require that you insure all references to the block devices point to the correct partitions.... within the firmware I do not know all of the references but I do know that they are referenced in the Boot.img in several files incliding the init.sun5i.rc and a couple of the uevent files. In the system folder one place im sure refers to at least the internal and external SD cards and any usb storage devices is the vold.fstab in /system/etc there are likely other places in the system that reference the actual block devices. I would start by making sure they are all properly pointing to the correct nandx partitions..

[A13 ROM JB 4.2.2 + DRIVERS] how to fix your tablet by modding drivers yourself.

IMPORTANT NOTICE:
i will personally no longer be able to provide support on this rom although there are a few people on xda who will... so my support is officially dicontinued here on this thread... although i have developed a new tool and rom for the A13's and you can get it HERE i will be providing support for HERE..
EDIT: I have developed a new tool for the allwinner a13 to carry out most tasks involving editing scripts, touchscreen parameters and fixes etc.. you can find it HERE
FaaastJB v2.5
A13 Allwinner with Jelly Bean 4.2.2 by Toxicro
MAKE BACKUP - using ZeusToolKit
Caution: don't flash this on KB901 with TS ft5x_ts
Rebased the whole ROM on various builds of JB 4.2.2 to run smooth without tweaks:
- cleaned up
- rooted
- adb enabled by default
- replaced the default launcher with GO Launcher HD
- adapted to accept my custom modules TS
lsmod on default ROM:
device 26862 0 - Live 0x00000000
rtl8150 10305 0 - Live 0x00000000
mcs7830 7581 0 - Live 0x00000000
qf9700 9152 0 - Live 0x00000000
asix 24601 0 - Live 0x00000000
sun5i_csi0 34042 0 - Live 0x00000000
sp0838 19927 1 - Live 0x00000000
camera 53105 1 sun5i_csi0, Live 0x00000000
videobuf_dma_contig 6243 1 sun5i_csi0, Live 0x00000000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0x00000000
cedarx 11869 0 - Live 0x00000000
mali 200007 29 - Live 0x00000000
ump 34213 11 mali, Live 0x00000000
nand 225000 8 - Live 0x00000000
Partitions on default ROM:
[email protected]:/ # busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 176.8M 68.0K 176.7M 0% /dev
tmpfs 176.8M 0 176.8M 0% /mnt/asec
tmpfs 176.8M 0 176.8M 0% /mnt/obb
/dev/block/nandd 503.9M 398.1M 105.9M 79% /system
/dev/block/nande 1.2G 103.7M 1.1G 9% /data
/dev/block/nandh 315.0M 5.2M 309.8M 2% /cache
/dev/block/vold/93:72 1.1G 48.0K 1.1G 0% /mnt/sdcard
/dev/block/vold/93:72 1.1G 48.0K 1.1G 0% /mnt/secure/asec
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
93 0 16384 nanda
93 8 16384 nandb
93 16 32768 nandc
93 24 614400 nandd
93 32 1228800 nande
93 40 16384 nandf
93 48 32768 nandg
93 56 327680 nandh
93 64 262144 nandi
93 72 1171456 nandj
DOWNLOAD ROM:
- New Version v2.5 -
4shared.com - FaaastJB-v2.5
mediafire.com - FaaastJB-v2.5
- Old version v2-
4shared.com - FaaastJB-v2
mediafire.com - FaaastJB-v2
By default Touch Screen DON'T work
STEP BY STEP FOR INSTALLING TS MODULES:
You need to have ADB installed before proceed
1. Flash FaaastJB with Livesuit 1.11
2. Wait for tablet to boot and load
3. Connect your tablet to PC
4. Extract all content from TS MODULE archive to a directory
5. Execute run.bat
6. After press any key dialog the tablet will reboot
7. That's all folks
If you don't know what TS driver to use try Uberizer option k/22 and use command "lsmod" on original working ROM.
I recommend try all archives and test both TS and gsensor for better result, don't stop at the first working TS try more.
OLD TS from FaaastJB 4.1.1 don't work here
DOWNLOAD TS MODULE
Single TS MODULE
- ekt3632.ko aka elan
- gt811_ts.ko
- gt828_ts.ko+mc32x0.ko
- gt811_ts.ko+dmard06.ko
- gsl1680.ko
- ft5x_ts.ko
- goodix_touch.ko
- gslx680.ko+mxc622x.ko
- ssd253x-ts.ko+dmard06.ko
- gslx680.ko
- gsl1680.ko+dmard06.ko
- ft5x_ts.ko
- gt828_ts.ko+mxc622x.ko
- zet6221.ko
- ekt3632.ko aka elan
- ektf2k.ko aka ekt3632+mma7660
- ssd253x-ts.ko+dmard06.ko+mma7660.ko
- elan_ts+mxc622x
- goodix811.ko+mxc622x.ko
- ssd253x-ts.ko
USERS TS MODULE
- gls1680+dmard06+mc32x0 - Thx to meatsos
- mg8698s+mxc622x+sp0838 - Thx to leoZ
- gt828_ts+mma7660 - Thx to goosen999
Multiple TS MODULE
- ft5x_ts, goodix_touch, ssd253x-ts, zet622x, byd693x-ts, gt82x, gt811, pixcir_cxx, gslx680, st1536_ts, elan_ts+mxc622x
- ft5x_ts, goodix_ts, gslX680, nt11003+mxc32x0
- ft5x_ts, ssd253x-ts, gt811_ts, sitronix_i2c_touch+dmard06+mma7660
- ft5x_ts, goodix_touch, ssd253x-ts, zet622x, byd693x-ts, gt82x, gt811, pixcir_touch_811, gsl1680, st1536_ts+mxc622x
- aw5306_ts.ko-pixcir_ts.ko-gt811.ko-gsl168x.ko-sichuang.ko-ft5x_ts.ko+mma7660
- gt811_ts.ko-A13_gslX680.ko-ft5x_ts.ko+mxc622x
- S710TAB - ft5x_ts.ko-gt811.ko-gslX680.ko+mxc622x
SPECIAL TS MODULE
- Ainol Novo7 Legend
- Multiple TS/GS: gslX680-ft5x_ts-gt818_ts-gt811_ts-zet6221+bma250-mma7660-dmard06-mma8452-kxtik-mxc622x-afa750-mma865x-lis3dh-mc32x0 after you use this module you will need to reflash ROM again if not works.
If you have found a TS and have reverse axes or screenshift i recommend to use this tools or try TSCalibration
More application for calibration need more people to test and confirm is working Touch Recalibrate
If you have inverted gsensor you will need to edit this file /system/usr/gsensor.cfg look for your gsensor name and play with this:
gsensor_direct_x = false
gsensor_direct_y = true
gsensor_direct_z = false
gsensor_xy_revert = false
Camera sux anyway on this tablet so if you still want to work you will need to edit script.bin section [csi0_para]
Don't forgot to make BACKUP of default ROM
For backup i recommend Uberizer option i/3.
I recommend this ROM for people who don't have a working TS.
This devices can't be bricked but if you don't find the right ROM they don't work correctly so if you don't know what your doing don't try it.
I recommend this ROM for people who don't have a working TS.
Thanks goes to Toxicro @ Techknow Forums for this rom this is his work..

Inside 4ndroid said:
FaaastJB v2.5
A13 Allwinner with Jelly Bean 4.2.2 by Toxicro
MAKE BACKUP - using Uberizer option i/3
Caution: don't flash this on KB901 with TS ft5x_ts
Rebased the whole ROM on various builds of JB 4.2.2 to run smooth without tweaks:
- cleaned up
- rooted
- adb enabled by default
- replaced the default launcher with GO Launcher HD
- adapted to accept my custom modules TS
lsmod on default ROM:
device 26862 0 - Live 0x00000000
rtl8150 10305 0 - Live 0x00000000
mcs7830 7581 0 - Live 0x00000000
qf9700 9152 0 - Live 0x00000000
asix 24601 0 - Live 0x00000000
sun5i_csi0 34042 0 - Live 0x00000000
sp0838 19927 1 - Live 0x00000000
camera 53105 1 sun5i_csi0, Live 0x00000000
videobuf_dma_contig 6243 1 sun5i_csi0, Live 0x00000000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0x00000000
cedarx 11869 0 - Live 0x00000000
mali 200007 29 - Live 0x00000000
ump 34213 11 mali, Live 0x00000000
nand 225000 8 - Live 0x00000000
Partitions on default ROM:
[email protected]:/ # busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 176.8M 68.0K 176.7M 0% /dev
tmpfs 176.8M 0 176.8M 0% /mnt/asec
tmpfs 176.8M 0 176.8M 0% /mnt/obb
/dev/block/nandd 503.9M 398.1M 105.9M 79% /system
/dev/block/nande 1.2G 103.7M 1.1G 9% /data
/dev/block/nandh 315.0M 5.2M 309.8M 2% /cache
/dev/block/vold/93:72 1.1G 48.0K 1.1G 0% /mnt/sdcard
/dev/block/vold/93:72 1.1G 48.0K 1.1G 0% /mnt/secure/asec
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
93 0 16384 nanda
93 8 16384 nandb
93 16 32768 nandc
93 24 614400 nandd
93 32 1228800 nande
93 40 16384 nandf
93 48 32768 nandg
93 56 327680 nandh
93 64 262144 nandi
93 72 1171456 nandj
DOWNLOAD ROM:
- New Version v2.5 -
4shared.com - FaaastJB-v2.5
mediafire.com - FaaastJB-v2.5
- Old version v2-
4shared.com - FaaastJB-v2
mediafire.com - FaaastJB-v2
By default Touch Screen DON'T work
STEP BY STEP FOR INSTALLING TS MODULES:
You need to have ADB installed before proceed
1. Flash FaaastJB with Livesuit 1.11
2. Wait for tablet to boot and load
3. Connect your tablet to PC
4. Extract all content from TS MODULE archive to a directory
5. Execute run.bat
6. After press any key dialog the tablet will reboot
7. That's all folks
If you don't know what TS driver to use try Uberizer option k/22 and use command "lsmod" on original working ROM.
I recommend try all archives and test both TS and gsensor for better result, don't stop at the first working TS try more.
OLD TS from FaaastJB 4.1.1 don't work here
DOWNLOAD TS MODULE
Single TS MODULE
- ekt3632.ko aka elan
- gt811_ts.ko
- gt828_ts.ko+mc32x0.ko
- gt811_ts.ko+dmard06.ko
- gsl1680.ko
- ft5x_ts.ko
- goodix_touch.ko
- gslx680.ko+mxc622x.ko
- ssd253x-ts.ko+dmard06.ko
- gslx680.ko
- gsl1680.ko+dmard06.ko
- ft5x_ts.ko
- gt828_ts.ko+mxc622x.ko
- zet6221.ko
- ekt3632.ko aka elan
- ektf2k.ko aka ekt3632+mma7660
- ssd253x-ts.ko+dmard06.ko+mma7660.ko
- elan_ts+mxc622x
- goodix811.ko+mxc622x.ko
- ssd253x-ts.ko
USERS TS MODULE
- gls1680+dmard06+mc32x0 - Thx to meatsos
- mg8698s+mxc622x+sp0838 - Thx to leoZ
- gt828_ts+mma7660 - Thx to goosen999
Multiple TS MODULE
- ft5x_ts, goodix_touch, ssd253x-ts, zet622x, byd693x-ts, gt82x, gt811, pixcir_cxx, gslx680, st1536_ts, elan_ts+mxc622x
- ft5x_ts, goodix_ts, gslX680, nt11003+mxc32x0
- ft5x_ts, ssd253x-ts, gt811_ts, sitronix_i2c_touch+dmard06+mma7660
- ft5x_ts, goodix_touch, ssd253x-ts, zet622x, byd693x-ts, gt82x, gt811, pixcir_touch_811, gsl1680, st1536_ts+mxc622x
- aw5306_ts.ko-pixcir_ts.ko-gt811.ko-gsl168x.ko-sichuang.ko-ft5x_ts.ko+mma7660
- gt811_ts.ko-A13_gslX680.ko-ft5x_ts.ko+mxc622x
- S710TAB - ft5x_ts.ko-gt811.ko-gslX680.ko+mxc622x
SPECIAL TS MODULE
- Ainol Novo7 Legend
- Multiple TS/GS: gslX680-ft5x_ts-gt818_ts-gt811_ts-zet6221+bma250-mma7660-dmard06-mma8452-kxtik-mxc622x-afa750-mma865x-lis3dh-mc32x0 after you use this module you will need to reflash ROM again if not works.
If you have found a TS and have reverse axes or screenshift i recommend to use this tools or try TSCalibration
More application for calibration need more people to test and confirm is working Touch Recalibrate
If you have inverted gsensor you will need to edit this file /system/usr/gsensor.cfg look for your gsensor name and play with this:
gsensor_direct_x = false
gsensor_direct_y = true
gsensor_direct_z = false
gsensor_xy_revert = false
Camera sux anyway on this tablet so if you still want to work you will need to edit script.bin section [csi0_para]
Don't forgot to make BACKUP of default ROM
For backup i recommend Uberizer option i/3.
I recommend this ROM for people who don't have a working TS.
This devices can't be bricked but if you don't find the right ROM they don't work correctly so if you don't know what your doing don't try it.
I recommend this ROM for people who don't have a working TS.
Thanks goes to Toxicro @ Techknow Forums for this rom this is his work..
Click to expand...
Click to collapse
how find what drvier TS or Gsensor???

needhelp here...
Inside 4ndroid said:
FaaastJB v2.5
A13 Allwinner with Jelly Bean 4.2.2 by Toxicro
MAKE BACKUP - using Uberizer option i/3
Caution: don't flash this on KB901 with TS ft5x_ts
Rebased the whole ROM on various builds of JB 4.2.2 to run smooth without tweaks:
- cleaned up
- rooted
- adb enabled by default
- replaced the default launcher with GO Launcher HD
- adapted to accept my custom modules TS
lsmod on default ROM:
device 26862 0 - Live 0x00000000
rtl8150 10305 0 - Live 0x00000000
mcs7830 7581 0 - Live 0x00000000
qf9700 9152 0 - Live 0x00000000
asix 24601 0 - Live 0x00000000
sun5i_csi0 34042 0 - Live 0x00000000
sp0838 19927 1 - Live 0x00000000
camera 53105 1 sun5i_csi0, Live 0x00000000
videobuf_dma_contig 6243 1 sun5i_csi0, Live 0x00000000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0x00000000
cedarx 11869 0 - Live 0x00000000
mali 200007 29 - Live 0x00000000
ump 34213 11 mali, Live 0x00000000
nand 225000 8 - Live 0x00000000
Partitions on default ROM:
[email protected]:/ # busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 176.8M 68.0K 176.7M 0% /dev
tmpfs 176.8M 0 176.8M 0% /mnt/asec
tmpfs 176.8M 0 176.8M 0% /mnt/obb
/dev/block/nandd 503.9M 398.1M 105.9M 79% /system
/dev/block/nande 1.2G 103.7M 1.1G 9% /data
/dev/block/nandh 315.0M 5.2M 309.8M 2% /cache
/dev/block/vold/93:72 1.1G 48.0K 1.1G 0% /mnt/sdcard
/dev/block/vold/93:72 1.1G 48.0K 1.1G 0% /mnt/secure/asec
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
93 0 16384 nanda
93 8 16384 nandb
93 16 32768 nandc
93 24 614400 nandd
93 32 1228800 nande
93 40 16384 nandf
93 48 32768 nandg
93 56 327680 nandh
93 64 262144 nandi
93 72 1171456 nandj
DOWNLOAD ROM:
- New Version v2.5 -
4shared.com - FaaastJB-v2.5
mediafire.com - FaaastJB-v2.5
- Old version v2-
4shared.com - FaaastJB-v2
mediafire.com - FaaastJB-v2
By default Touch Screen DON'T work
STEP BY STEP FOR INSTALLING TS MODULES:
You need to have ADB installed before proceed
1. Flash FaaastJB with Livesuit 1.11
2. Wait for tablet to boot and load
3. Connect your tablet to PC
4. Extract all content from TS MODULE archive to a directory
5. Execute run.bat
6. After press any key dialog the tablet will reboot
7. That's all folks
If you don't know what TS driver to use try Uberizer option k/22 and use command "lsmod" on original working ROM.
I recommend try all archives and test both TS and gsensor for better result, don't stop at the first working TS try more.
OLD TS from FaaastJB 4.1.1 don't work here
DOWNLOAD TS MODULE
Single TS MODULE
- ekt3632.ko aka elan
- gt811_ts.ko
- gt828_ts.ko+mc32x0.ko
- gt811_ts.ko+dmard06.ko
- gsl1680.ko
- ft5x_ts.ko
- goodix_touch.ko
- gslx680.ko+mxc622x.ko
- ssd253x-ts.ko+dmard06.ko
- gslx680.ko
- gsl1680.ko+dmard06.ko
- ft5x_ts.ko
- gt828_ts.ko+mxc622x.ko
- zet6221.ko
- ekt3632.ko aka elan
- ektf2k.ko aka ekt3632+mma7660
- ssd253x-ts.ko+dmard06.ko+mma7660.ko
- elan_ts+mxc622x
- goodix811.ko+mxc622x.ko
- ssd253x-ts.ko
USERS TS MODULE
- gls1680+dmard06+mc32x0 - Thx to meatsos
- mg8698s+mxc622x+sp0838 - Thx to leoZ
- gt828_ts+mma7660 - Thx to goosen999
Multiple TS MODULE
- ft5x_ts, goodix_touch, ssd253x-ts, zet622x, byd693x-ts, gt82x, gt811, pixcir_cxx, gslx680, st1536_ts, elan_ts+mxc622x
- ft5x_ts, goodix_ts, gslX680, nt11003+mxc32x0
- ft5x_ts, ssd253x-ts, gt811_ts, sitronix_i2c_touch+dmard06+mma7660
- ft5x_ts, goodix_touch, ssd253x-ts, zet622x, byd693x-ts, gt82x, gt811, pixcir_touch_811, gsl1680, st1536_ts+mxc622x
- aw5306_ts.ko-pixcir_ts.ko-gt811.ko-gsl168x.ko-sichuang.ko-ft5x_ts.ko+mma7660
- gt811_ts.ko-A13_gslX680.ko-ft5x_ts.ko+mxc622x
- S710TAB - ft5x_ts.ko-gt811.ko-gslX680.ko+mxc622x
SPECIAL TS MODULE
- Ainol Novo7 Legend
- Multiple TS/GS: gslX680-ft5x_ts-gt818_ts-gt811_ts-zet6221+bma250-mma7660-dmard06-mma8452-kxtik-mxc622x-afa750-mma865x-lis3dh-mc32x0 after you use this module you will need to reflash ROM again if not works.
If you have found a TS and have reverse axes or screenshift i recommend to use this tools or try TSCalibration
More application for calibration need more people to test and confirm is working Touch Recalibrate
If you have inverted gsensor you will need to edit this file /system/usr/gsensor.cfg look for your gsensor name and play with this:
gsensor_direct_x = false
gsensor_direct_y = true
gsensor_direct_z = false
gsensor_xy_revert = false
Camera sux anyway on this tablet so if you still want to work you will need to edit script.bin section [csi0_para]
Don't forgot to make BACKUP of default ROM
For backup i recommend Uberizer option i/3.
I recommend this ROM for people who don't have a working TS.
This devices can't be bricked but if you don't find the right ROM they don't work correctly so if you don't know what your doing don't try it.
I recommend this ROM for people who don't have a working TS.
Thanks goes to Toxicro @ Techknow Forums for this rom this is his work..
Click to expand...
Click to collapse
hi there, thanks for this rom, i tried all of the ts driver, but nothing work. sorry but i dont know my default driver because before i installed diffrent rom on this tablet, that time i was not working so there is no chance of knowing the default driver, then i opened the back case, the only familliar name there is the allwinner tech a13 nothing more... so there is no indication of the ts driver, is there anyone can help me?

jh3ss said:
hi there, thanks for this rom, i tried all of the ts driver, but nothing work. sorry but i dont know my default driver because before i installed diffrent rom on this tablet, that time i was not working so there is no chance of knowing the default driver, then i opened the back case, the only familliar name there is the allwinner tech a13 nothing more... so there is no indication of the ts driver, is there anyone can help me?
Click to expand...
Click to collapse
there is not much you can do apart from to source more drivers and keep trying different ones until you get a working one... especially as you have no clue on what the modules were on the original firmware....

Need Help for Camera
Hello Brothers.....
Camera problem may be due to camera lib files ... if it not working, we need to rewrite kernel for our allwinner a13 processor....
if anybody have kernel knowledge, pls do it..

Many-many-many THANKS for this ROM! :good:

Hello
I have a problem , my TS doesn't work :
lsmod data
8188eu 621112 0 - Live 0xbf2d1000
rtl8150 10305 0 - Live 0xbf2c4000
mcs7830 7581 0 - Live 0xbf2be000
qf9700 9152 0 - Live 0xbf2b7000
asix 24601 0 - Live 0xbf2ab000
sun5i_csi0 33355 0 - Live 0xbf29d000
gc0308 18608 1 - Live 0xbf294000
camera 61054 1 sun5i_csi0, Live 0xbf280000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0xbf27b000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0xbf271000
cedarx 9351 0 - Live 0xbf26a000
mali 115410 8 - Live 0xbf240000
ump 34349 19 mali, Live 0xbf231000
gslx680 1052023 0 - Live 0xbf106000
byd693x_ts 9094 0 - Live 0xbf0db000
zet622x 17751 0 - Live 0xbf0cd000
ssd253x_ts 21452 0 - Live 0xbf0ac000
goodix_touch 18280 0 - Live 0xbf0a3000
ft5x_ts 77026 0 - Live 0xbf074000
inet_ctp 2227 6 gslx680,byd693x_ts,zet622x,ssd253x_ts,goodix_touch,ft5x_ts, Live 0xbf070000
mxc622x 6310 0 - Live 0xbf06a000
nand 225002 8 - Live 0xbf000000

First link of Multiple TS MODULE don't work
http://www.4shared.com/rar/JBiFCtmb/2-solomonsam.html
However i have installed this ROM and i have installed
gslx680.ko+mxc622x.ko Module
The Touch seem to respond but is not calibrated
I have tried Touch Recalibrate and TSCalibration but the situation remane the same
These are my info on STOCK ROM (i have backuped it whit CWM...but after installed this rom i didn't have the recovery anymore so now i can't restore it because i don't have an OTG adapter for install the recovery on the tablet)
Code:
[email protected]:/ $ su
[email protected]:/ # lsmod
8188eu 621112 0 - Live 0xbf279000
8192cu 575431 0 - Live 0xbf1d1000
mxc622x 6310 0 - Live 0xbf1cb000
rtl8150 10305 0 - Live 0xbf1c4000
mcs7830 7581 0 - Live 0xbf1be000
qf9700 9152 0 - Live 0xbf1b7000
asix 24601 0 - Live 0xbf1ab000
sun5i_csi0 33355 0 - Live 0xbf19d000
gc0308 18608 1 - Live 0xbf194000
camera 61054 1 sun5i_csi0, Live 0xbf180000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0xbf17b000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0xbf171000
cedarx 9351 0 - Live 0xbf16a000
mali 115330 8 - Live 0xbf140000
ump 34309 17 mali, Live 0xbf131000
gslx680 359718 0 - Live 0xbf0af000
pixcir_cxx 23546 0 - Live 0xbf0a4000
gt811 15930 0 - Live 0xbf09c000
byd693x_ts 9094 0 - Live 0xbf08d000
zet622x 17831 0 - Live 0xbf07f000
ssd253x_ts 21452 0 - Live 0xbf075000
ft5x02 61964 0 - Live 0xbf055000
inet_ctp 2227 7 gslx680,pixcir_cxx,gt811,byd693x_ts,zet622x,ssd253x_ts,ft5x02, Live 0xbf039000
nand 169582 8 - Live 0xbf000000
[email protected]:/ # getevetn -lp /dev/input/event0
sh: getevetn: not found
127|[email protected]:/ # getevent -lp /dev/input/event0
add device 1: /dev/input/event0
name: "sun4i-keyboard"
events:
KEY (0001): KEY_ESC KEY_ENTER KEY_HOME KEY_VOLUMEDOWN
KEY_VOLUMEUP KEY_MENU KEY_SEARCH
input props:
<none>
[email protected]:/ # getevent -lp /dev/input/event1
add device 1: /dev/input/event1
name: "axp20-supplyer"
events:
KEY (0001): KEY_POWER
input props:
<none>
[email protected]:/ # getevent -lp /dev/input/event2
add device 1: /dev/input/event2
name: "mxc622x"
events:
ABS (0003): ABS_X : value 7, min -128, max 128, fuzz 0, flat 0, resolution 0
ABS_Y : value 3, min -128, max 128, fuzz 0, flat 0, resolution 0
ABS_Z : value 0, min -128, max 128, fuzz 0, flat 0, resolution 0
input props:
<none>
[email protected]:/ # getevent -lp /dev/input/event3
add device 1: /dev/input/event3
name: "gt811"
events:
ABS (0003): ABS_HAT0X : value 0, min 0, max 0, fuzz 0, flat 0, resolution 0
ABS_HAT1X : value 0, min 0, max 0, fuzz 0, flat 0, resolution 0
ABS_HAT2Y : value 0, min 0, max 0, fuzz 0, flat 0, resolution 0
ABS_HAT3X : value 0, min 0, max 0, fuzz 0, flat 0, resolution 0
ABS_DISTANCE : value 0, min 0, max 0, fuzz 0, flat 0, resolution 0
ABS_MT_TOUCH_MAJOR : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
ABS_MT_WIDTH_MAJOR : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
ABS_MT_POSITION_X : value 0, min 0, max 800, fuzz 0, flat 0, resolution 0
ABS_MT_POSITION_Y : value 0, min 0, max 480, fuzz 0, flat 0, resolution 0
ABS_MT_TRACKING_ID : value 0, min 0, max 5, fuzz 0, flat 0, resolution 0
input props:
<none>
[email protected]:/ # getevent -lp /dev/input/event4
add device 1: /dev/input/event4
name: "gslx680"
events:
ABS (0003): ABS_MT_TOUCH_MAJOR : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
ABS_MT_WIDTH_MAJOR : value 0, min 0, max 200, fuzz 0, flat 0, resolution 0
ABS_MT_POSITION_X : value 0, min 0, max 800, fuzz 0, flat 0, resolution 0
ABS_MT_POSITION_Y : value 0, min 0, max 480, fuzz 0, flat 0, resolution 0
ABS_MT_TRACKING_ID : value 0, min 0, max 11, fuzz 0, flat 0, resolution 0
input props:
<none>
[email protected]:/ #
ALSO ORIGINAL script.fex
Code:
[product]
version = "1.0"
machine = "A13-EVB-V1.0"
[target]
boot_clock = 1008
dcdc2_vol = 1400
dcdc3_vol = 1200
ldo2_vol = 3000
ldo3_vol = 3300
ldo4_vol = 3300
pll4_freq = 960
pll6_freq = 720
power_start = 0
storage_type = 0
[card_boot]
logical_start = 40960
sprite_gpio0 =
[pm_para]
standby_mode = 0
[card_boot0_para]
card_ctrl = 0
card_high_speed = 1
card_line = 4
sdc_d1 = port:PF00<2><1><default><default>
sdc_d0 = port:PF01<2><1><default><default>
sdc_clk = port:PF02<2><1><default><default>
sdc_cmd = port:PF03<2><1><default><default>
sdc_d3 = port:PF04<2><1><default><default>
sdc_d2 = port:PF05<2><1><default><default>
[twi_para]
twi_port = 0
twi_scl = port:PB00<2><1><default><default>
twi_sda = port:PB01<2><1><default><default>
[uart_para]
uart_debug_port = 0
uart_debug_tx = port:PG03<4><1><default><default>
uart_debug_rx = port:PG04<4><1><default><default>
[jtag_para]
jtag_enable = 0
jtag_ms = port:PF00<4><1><default><default>
jtag_ck = port:PF05<4><1><default><default>
jtag_do = port:PF03<4><1><default><default>
jtag_di = port:PF01<4><1><default><default>
[dram_para]
dram_baseaddr = 0x40000000
dram_clk = 432
dram_type = 3
dram_rank_num = 1
dram_chip_density = 2048
dram_io_width = 8
dram_bus_width = 16
dram_cas = 9
dram_zq = 0x7b
dram_odt_en = 0
dram_size = 512
dram_tpr0 = 0x42d899b7
dram_tpr1 = 0xa090
dram_tpr2 = 0x22a00
dram_tpr3 = 0x0
dram_tpr4 = 0x0
dram_tpr5 = 0x0
dram_emr1 = 0x4
dram_emr2 = 0x10
dram_emr3 = 0x0
[nand_para]
nand_used = 1
nand_we = port:PC00<2><default><default><default>
nand_ale = port:PC01<2><default><default><default>
nand_cle = port:PC02<2><default><default><default>
nand_ce1 = port:PC03<2><default><default><default>
nand_ce0 = port:PC04<2><default><default><default>
nand_nre = port:PC05<2><default><default><default>
nand_rb0 = port:PC06<2><default><default><default>
nand_rb1 = port:PC07<2><default><default><default>
nand_d0 = port:PC08<2><default><default><default>
nand_d1 = port:PC09<2><default><default><default>
nand_d2 = port:PC10<2><default><default><default>
nand_d3 = port:PC11<2><default><default><default>
nand_d4 = port:PC12<2><default><default><default>
nand_d5 = port:PC13<2><default><default><default>
nand_d6 = port:PC14<2><default><default><default>
nand_d7 = port:PC15<2><default><default><default>
nand_wp =
nand_ce2 =
nand_ce3 =
nand_ce4 =
nand_ce5 =
nand_ce6 =
nand_ce7 =
nand_spi =
nand_ndqs = port:PC19<2><default><default><default>
good_block_ratio = 0
[mali_para]
mali_used = 1
mali_clkdiv = 2
[twi0_para]
twi0_used = 1
twi0_scl = port:PB00<2><default><default><default>
twi0_sda = port:PB01<2><default><default><default>
[twi1_para]
twi1_used = 1
twi1_scl = port:PB15<2><default><default><default>
twi1_sda = port:PB16<2><default><default><default>
[twi2_para]
twi2_used = 1
twi2_scl = port:PB17<2><default><default><default>
twi2_sda = port:PB18<2><default><default><default>
[uart_para0]
uart_used = 0
uart_port = 0
uart_type = 2
uart_tx = port:PB19<2><1><default><default>
uart_rx = port:PB20<2><1><default><default>
[uart_para1]
uart_used = 0
uart_port = 1
uart_type = 2
uart_tx = port:PG03<4><1><default><default>
uart_rx = port:PG04<4><1><default><default>
[spi1_para]
spi_used = 0
spi_cs0 = port:PG09<2><default><default><default>
spi_cs1 = port:PG13<2><default><default><default>
spi_sclk = port:PG10<2><default><default><default>
spi_mosi = port:PG11<2><default><default><default>
spi_miso = port:PG12<2><default><default><default>
[spi2_para]
spi_used = 0
spi_cs0 = port:PE00<4><default><default><default>
spi_sclk = port:PE01<4><default><default><default>
spi_mosi = port:PB02<4><default><default><default>
spi_miso = port:PB03<4><default><default><default>
[rtp_para]
rtp_used = 0
rtp_screen_size = 5
rtp_regidity_level = 5
rtp_press_threshold_enable = 0
rtp_press_threshold = 0x1f40
rtp_sensitive_level = 0xf
rtp_exchange_x_y_flag = 0
[ctp_para]
ctp_boxchip_type = 2579
ctp_cob = 1
ctp_twi_id = 1
ctp0_used = 1
ctp0_name = "ft5x02"
ctp0_twi_addr = 56
ctp1_used = 0
ctp1_name = "Goodix-TS"
ctp1_twi_addr = 85
ctp2_used = 1
ctp2_name = "ssd253x-ts"
ctp2_twi_addr = 72
ctp2_ssd_type = 75801
ctp4_used = 1
ctp4_name = "zet622x-ts"
ctp4_twi_addr = 118
ctp5_used = 1
ctp5_name = "byd693x-ts"
ctp5_twi_addr = 82
ctp8_used = 0
ctp8_name = "gt82x"
ctp8_twi_addr = 93
ctp9_used = 1
ctp9_name = "gt811"
ctp9_twi_addr = 93
ctp10_used = 1
ctp10_name = "pixcir_cxx"
ctp10_twi_addr = 92
ctp12_used = 1
ctp12_name = "gslx680"
ctp12_twi_addr = 64
ctp12_gsl_type = 8602
ctp13_used = 1
ctp13_name = "sitronix_ts"
ctp13_twi_addr = 96
ctp19_used = 1
ctp19_name = "elan_ts"
ctp19_twi_addr = 20
ctp_screen_max_x = 800
ctp_screen_max_y = 480
ctp_revert_x_flag = 0
ctp_revert_y_flag = 0
ctp_exchange_x_y_flag = 0
ctp_int_port = port:PG11<6><default><default><default>
ctp_wakeup = port:PB03<1><default><default><1>
ctp_io_port = port:PG11<6><default><default><default>
[tkey_para]
tkey_used = 0
tkey_name = "hv_keypad"
tkey_twi_id = 2
tkey_twi_addr = 0x62
tkey_int =
[motor_para]
motor_used = 0
motor_shake =
[disp_init]
disp_init_enable = 1
disp_mode = 0
screen0_output_type = 1
screen0_output_mode = 4
screen1_output_type = 1
screen1_output_mode = 4
fb0_framebuffer_num = 2
fb0_format = 10
fb0_pixel_sequence = 0
fb0_scaler_mode_enable = 0
fb1_framebuffer_num = 2
fb1_format = 10
fb1_pixel_sequence = 0
fb1_scaler_mode_enable = 0
[lcd0_para]
lcd_used = 1
lcd_x = 800
lcd_y = 480
lcd_dclk_freq = 33
lcd_pwm_not_used = 0
lcd_pwm_ch = 0
lcd_pwm_freq = 10000
lcd_pwm_pol = 1
lcd_if = 0
lcd_hbp = 46
lcd_ht = 1055
lcd_vbp = 23
lcd_vt = 1050
lcd_hv_if = 0
lcd_hv_smode = 0
lcd_hv_s888_if = 0
lcd_hv_syuv_if = 0
lcd_hv_vspw = 0
lcd_hv_hspw = 0
lcd_lvds_ch = 0
lcd_lvds_mode = 0
lcd_lvds_bitwidth = 0
lcd_lvds_io_cross = 0
lcd_cpu_if = 0
lcd_frm = 1
lcd_io_cfg0 = 268435456
lcd_gamma_correction_en = 0
lcd_gamma_tbl_0 = 0x0
lcd_gamma_tbl_1 = 0x10101
lcd_gamma_tbl_255 = 0xffffff
lcd_bl_en_used = 1
lcd_bl_en = port:power1<1><0><default><1>
lcd_power_used = 1
lcd_power = port:power0<1><0><default><1>
lcd_pwm_used = 1
lcd_pwm = port:PB02<2><0><default><default>
lcd_gpio_0 =
lcd_gpio_1 =
lcd_gpio_2 =
lcd_gpio_3 =
lcdd0 = port:PD00<2><0><default><default>
lcdd1 = port:PD01<2><0><default><default>
lcdd2 = port:PD02<2><0><default><default>
lcdd3 = port:PD03<2><0><default><default>
lcdd4 = port:PD04<2><0><default><default>
lcdd5 = port:PD05<2><0><default><default>
lcdd6 = port:PD06<2><0><default><default>
lcdd7 = port:PD07<2><0><default><default>
lcdd8 = port:PD08<2><0><default><default>
lcdd9 = port:PD09<2><0><default><default>
lcdd10 = port:PD10<2><0><default><default>
lcdd11 = port:PD11<2><0><default><default>
lcdd12 = port:PD12<2><0><default><default>
lcdd13 = port:PD13<2><0><default><default>
lcdd14 = port:PD14<2><0><default><default>
lcdd15 = port:PD15<2><0><default><default>
lcdd16 = port:PD16<2><0><default><default>
lcdd17 = port:PD17<2><0><default><default>
lcdd18 = port:PD18<2><0><default><default>
lcdd19 = port:PD19<2><0><default><default>
lcdd20 = port:PD20<2><0><default><default>
lcdd21 = port:PD21<2><0><default><default>
lcdd22 = port:PD22<2><0><default><default>
lcdd23 = port:PD23<2><0><default><default>
lcdclk = port:PD24<2><0><default><default>
lcdde = port:PD25<2><0><default><default>
lcdhsync = port:PD26<2><0><default><default>
lcdvsync = port:PD27<2><0><default><default>
[tv_out_dac_para]
dac_used = 1
dac0_src = 0
[hdmi_para]
hdmi_used = 0
[csi0_para]
csi_used = 1
csi_mode = 0
csi_dev_qty = 2
csi_stby_mode = 1
csi_mname = "gc0308"
csi_twi_id = 2
csi_twi_addr = 0x42
csi_if = 0
csi_vflip = 0
csi_hflip = 0
csi_iovdd = ""
csi_avdd = ""
csi_dvdd = ""
csi_flash_pol = 1
csi_facing = 1
csi_mname_b = "gt2005"
csi_twi_id_b = 2
csi_twi_addr_b = 0x78
csi_if_b = 0
csi_vflip_b = 0
csi_hflip_b = 0
csi_iovdd_b = ""
csi_avdd_b = ""
csi_dvdd_b = ""
csi_flash_pol_b = 1
csi_facing_b = 0
csi_pck = port:PE00<3><default><default><default>
csi_ck = port:PE01<3><default><default><default>
csi_hsync = port:PE02<3><default><default><default>
csi_vsync = port:PE03<3><default><default><default>
csi_d0 = port:PE04<3><default><default><default>
csi_d1 = port:PE05<3><default><default><default>
csi_d2 = port:PE06<3><default><default><default>
csi_d3 = port:PE07<3><default><default><default>
csi_d4 = port:PE08<3><default><default><default>
csi_d5 = port:PE09<3><default><default><default>
csi_d6 = port:PE10<3><default><default><default>
csi_d7 = port:PE11<3><default><default><default>
csi_reset = port:power3<1><default><default><0>
csi_power_en = port:power2<1><default><default><1>
csi_stby = port:PB10<1><default><default><1>
csi_flash =
csi_af_en =
csi_reset_b = port:power3<1><default><default><0>
csi_power_en_b = port:power2<1><default><default><1>
csi_stby_b = port:PG03<1><default><default><1>
csi_flash_b =
csi_af_en_b =
[csi1_para]
csi_used = 0
csi_mode = 0
csi_dev_qty = 1
csi_stby_mode = 1
csi_mname = ""
csi_twi_id = 1
csi_twi_addr = 0xba
csi_if = 0
csi_vflip = 0
csi_hflip = 0
csi_iovdd = ""
csi_avdd = ""
csi_dvdd = ""
csi_flash_pol = 1
csi_mname_b = ""
csi_twi_id_b = 1
csi_twi_addr_b = 0x78
csi_if_b = 0
csi_vflip_b = 1
csi_hflip_b = 0
csi_iovdd_b = ""
csi_avdd_b = ""
csi_dvdd_b = ""
csi_flash_pol_b = 1
csi_reset =
csi_power_en =
csi_stby =
csi_flash =
csi_af_en =
csi_reset_b =
csi_power_en_b =
csi_stby_b =
csi_flash_b =
csi_af_en_b =
[camera_list_para]
camera_list_para_used = 1
hm2057 = 1
ov7670 = 0
gc0308 = 1
gt2005 = 1
hi704 = 1
sp0838 = 1
mt9m112 = 0
mt9m113 = 0
ov2655 = 0
hi253 = 0
gc0307 = 0
mt9d112 = 0
ov5640 = 0
gc2015 = 1
ov2643 = 0
gc0329 = 1
gc0309 = 1
tvp5150 = 0
s5k4ec = 0
ov5650_mv9335 = 0
siv121d = 0
gc2035 = 1
sp2518 = 1
gc0328 = 1
[mmc0_para]
sdc_used = 1
sdc_detmode = 1
bus_width = 4
sdc_d1 = port:PF00<2><1><2><default>
sdc_d0 = port:PF01<2><1><2><default>
sdc_clk = port:PF02<2><1><2><default>
sdc_cmd = port:PF03<2><1><2><default>
sdc_d3 = port:PF04<2><1><2><default>
sdc_d2 = port:PF05<2><1><2><default>
sdc_det = port:PG00<0><1><default><default>
sdc_use_wp = 0
sdc_wp =
[mmc1_para]
sdc_used = 0
sdc_detmode =
bus_width =
sdc_cmd =
sdc_clk =
sdc_d0 =
sdc_d1 =
sdc_d2 =
sdc_d3 =
sdc_det =
sdc_use_wp =
sdc_wp =
[mmc2_para]
sdc_used = 0
sdc_detmode = 3
bus_width = 4
sdc_cmd = port:PE08<4><1><2><default>
sdc_clk = port:PE09<4><1><2><default>
sdc_d0 = port:PE04<4><1><2><default>
sdc_d1 = port:PE05<4><1><2><default>
sdc_d2 = port:PE06<4><1><2><default>
sdc_d3 = port:PE07<4><1><2><default>
sdc_det =
sdc_use_wp = 0
sdc_wp =
[ms_para]
ms_used = 0
ms_bs =
ms_clk =
ms_d0 =
ms_d1 =
ms_d2 =
ms_d3 =
ms_det =
[keypad_para]
kp_used = 0
kp_in_size =
kp_out_size =
kp_in0 =
kp_in1 =
kp_in2 =
kp_in3 =
kp_in4 =
kp_in5 =
kp_in6 =
kp_in7 =
kp_out0 =
kp_out1 =
kp_out2 =
kp_out3 =
kp_out4 =
kp_out5 =
kp_out6 =
kp_out7 =
[usbc0]
usb_used = 1
usb_port_type = 2
usb_detect_type = 1
usb_id_gpio = port:PG02<0><1><default><default>
usb_det_vbus_gpio = port:PG01<0><0><default><default>
usb_drv_vbus_gpio = port:PG12<1><0><default><0>
usb_host_init_state = 0
[usbc1]
usb_used = 1
usb_port_type = 1
usb_detect_type = 0
usb_id_gpio =
usb_det_vbus_gpio =
usb_drv_vbus_gpio = port:PG11<1><0><default><0>
usb_host_init_state = 1
[usb_feature]
vendor_id = 6353
mass_storage_id = 1
adb_id = 2
manufacturer_name = "USB Developer"
product_name = "Android"
serial_number = "20080411"
[msc_feature]
vendor_name = "USB 2.0"
product_name = "USB Flash Driver"
release = 100
luns = 2
[gsensor_para]
gsensor_used = 1
gsensor_unuse_name =
gsensor_twi_id = 1
gsensor_twi_addr =
gsensor_int1 =
gsensor_int2 =
[gps_para]
gps_used = 0
gps_spi_id =
gps_spi_cs_num =
gps_lradc =
gps_clk =
gps_sign =
gps_mag =
gps_vcc_en =
gps_osc_en =
gps_rx_en =
[sdio_wifi_para]
sdio_wifi_used = 0
sdio_wifi_sdc_id =
sdio_wifi_mod_sel =
[usb_wifi_para]
usb_wifi_used = 1
usb_wifi_usbc_num = 1
[3g_para]
3g_used = 0
3g_name =
3g_usbc_num =
3g_on_off =
3g_reset =
3g_poweron =
3g_wakeup_out =
3g_wakeup_in =
[gy_para]
gy_used = 0
gy_twi_id = 1
gy_twi_addr = 0
gy_int1 =
gy_int2 =
[ls_para]
ls_used = 0
ls_name = "ltr501als"
ls_twi_id = 1
ls_twi_addr =
ls_int =
[compass_para]
compass_used = 0
compass_twi_id =
compass_twi_addr =
compass_int =
[bt_para]
bt_used = 0
bt_uart_id =
bt_mod_type =
[i2s_para]
i2s_used = 0
i2s_channel =
i2s_mclk =
i2s_bclk =
i2s_lrclk =
i2s_dout0 =
i2s_dout1 =
i2s_dout2 =
i2s_dout3 =
i2s_din =
[spdif_para]
spdif_used = 0
spdif_mclk =
spdif_dout =
spdif_din =
[audio_para]
audio_used = 1
capture_used = 1
audio_lr_change = 1
audio_pa_ctrl = port:PG10<1><default><default><0>
[ir_para]
ir_used = 0
ir0_rx = port:PB04<2><default><default><default>
[rtc_para]
rtc_used = 1
rtc_name = "pcf8563"
rtc_twi_id = 1
rtc_twi_addr = 81
[pmu_para]
pmu_used = 1
pmu_twi_addr = 52
pmu_twi_id = 0
pmu_irq_id = 0
pmu_battery_rdc = 100
pmu_battery_cap = 2600
pmu_init_chgcur = 600
pmu_earlysuspend_chgcur = 600
pmu_suspend_chgcur = 1000
pmu_resume_chgcur = 300
pmu_shutdown_chgcur = 1000
pmu_init_chgvol = 4200
pmu_init_chgend_rate = 15
pmu_init_chg_enabled = 1
pmu_init_adc_freq = 100
pmu_init_adc_freqc = 100
pmu_init_chg_pretime = 50
pmu_init_chg_csttime = 720
pmu_bat_para1 = 0
pmu_bat_para2 = 0
pmu_bat_para3 = 0
pmu_bat_para4 = 0
pmu_bat_para5 = 5
pmu_bat_para6 = 13
pmu_bat_para7 = 16
pmu_bat_para8 = 26
pmu_bat_para9 = 36
pmu_bat_para10 = 46
pmu_bat_para11 = 53
pmu_bat_para12 = 61
pmu_bat_para13 = 73
pmu_bat_para14 = 84
pmu_bat_para15 = 92
pmu_bat_para16 = 100
pmu_usbvol_limit = 1
pmu_usbcur_limit = 0
pmu_usbvol = 4000
pmu_usbcur = 0
pmu_usbvol_pc = 4000
pmu_usbcur_pc = 0
pmu_pwroff_vol = 3300
pmu_pwron_vol = 2900
pmu_pekoff_time = 6000
pmu_pekoff_en = 1
pmu_peklong_time = 1500
pmu_pekon_time = 1000
pmu_pwrok_time = 64
pmu_pwrnoe_time = 2000
pmu_intotp_en = 1
pmu_used2 = 0
pmu_adpdet =
pmu_init_chgcur2 = 400
pmu_earlysuspend_chgcur2 = 600
pmu_suspend_chgcur2 = 1200
pmu_resume_chgcur2 = 400
pmu_shutdown_chgcur2 = 1200
pmu_suspendpwroff_vol = 3500
pmu_batdeten = 1
[boot_extend]
vol_threshold = 3600
[recovery_key]
key_min = 4
key_max = 100
[dvfs_table]
max_freq = 1008000000
min_freq = 60000000
LV_count = 7
LV1_freq = 1104000000
LV1_volt = 1500
LV2_freq = 1008000000
LV2_volt = 1400
LV3_freq = 912000000
LV3_volt = 1350
LV4_freq = 864000000
LV4_volt = 1300
LV5_freq = 624000000
LV5_volt = 1200
LV6_freq = 576000000
LV6_volt = 1200
LV7_freq = 432000000
LV7_volt = 1200
Please help my ç_ç

simone.pri said:
First link of Multiple TS MODULE don't work
[/CODE]
Click to expand...
Click to collapse
I will try this Rom on my TW-Q8 Allwiner once there are more success stories..
Thanks for your work.

Wilsonb said:
I will try this Rom on my TW-Q8 Allwiner once there are more success stories..
Thanks for your work.
Click to expand...
Click to collapse
it works wonderfully well...however, battrey drains a lott! :crying:

My specs
tjkingg said:
it works wonderfully well...however, battrey drains a lott! :crying:
Click to expand...
Click to collapse
I thought people were saying it would brick their device or no touch screen. If not I will do it today. I can work around the battery issue. It came
with a Firmware dated 11-30-2013 witch is not to old.
Should I capture this current firmware image on here for others? (How?)
My Specs on this white framed cheap thing I got recently..
Boxchip Allwinner A13
1008Mhz Single core
Mali 400MP (Single core GPU)
Tablet type:
TW-Q8 (Allwinner)
Screen size 7"
Freq. states 6
Neon capable (video playback)
512mb DDR
-----------------------------
Current firmware
Android 4.1.2
Baseband 1.5
Kernel 3.0.8+
Firmware build
JSD_TW-A0708-V63-120D_20131105

Hi, firstly thank you for you rom. I have a tablet EVOQ QPAD710A. This ROM works on my tablet but i have a problem. With default rom is everythink fine but whit FaaastJB 2.5 tablet working only on usb or charger. On charger or USB tablet do a randomly crap sounds from speaker and when i unplug charger or usb the exact moment of the sound, the tablet turns off hard.
Can anyone help with this?

Wilsonb said:
I thought people were saying it would brick their device or no touch screen. If not I will do it today. I can work around the battery issue. It came
with a Firmware dated 11-30-2013 witch is not to old.
Should I capture this current firmware image on here for others? (How?)
My Specs on this white framed cheap thing I got recently..
Boxchip Allwinner A13
1008Mhz Single core
Mali 400MP (Single core GPU)
Tablet type:
TW-Q8 (Allwinner)
Screen size 7"
Freq. states 6
Neon capable (video playback)
512mb DDR
-----------------------------
Current firmware
Android 4.1.2
Baseband 1.5
Kernel 3.0.8+
Firmware build
JSD_TW-A0708-V63-120D_20131105
Click to expand...
Click to collapse
Download uberizer and go to option 'i' to make a backup or and image file to flash

Hi, guys. Could somebody please tell me, after backing it up with Uberizer i/3, how can I restore this backup?
Thanks,
P.S. Nevermind... Noticed it was option i/4

Auris 1.6 vvt-i said:
Hi, guys. Could somebody please tell me, after backing it up with Uberizer i/3, how can I restore this backup?
Thanks,
P.S. Nevermind... Noticed it was option i/4
Click to expand...
Click to collapse
lol :silly:

Work perfectly on my Bmorn V13 Pro using allwinner a13. Thanks alot

any1 experiencing battery drain??
Sent from my Nexus 7 using XDA Premium 4 mobile app

anyone has ace allwinner a13 8 inch firware?
I already installed this firmware but it seems for 7 inch tablet only. Do yo have firmware for ace 8 inch tablet? thanks!

Will back up current Rom(anyone interested?) Is there a Android 4.4.2 avail for A13?
Will back up current Rom(anyone interested? See below for what I have.)
Is there an Android 4.4.2 Rom avail for Allwinner A13?
Wilsonb said:
I thought people were saying it would brick their device or no touch screen. If not I will do it today. I can work around the battery issue. It came
with a Firmware dated 11-30-2013 witch is not to old.
Should I capture this current firmware image on here for others? (How?)
My Specs on this white framed cheap thing I got recently..
Boxchip Allwinner A13
1008Mhz Single core
Mali 400MP (Single core GPU)
Tablet type:
TW-Q8 (Allwinner)
Screen size 7"
Freq. states 6
Neon capable (video playback)
512mb DDR
-----------------------------
Current firmware
Android 4.1.2
Baseband 1.5
Kernel 3.0.8+
Firmware build
JSD_TW-A0708-V63-120D_20131105
Click to expand...
Click to collapse

Wilsonb said:
Will back up current Rom(anyone interested? See below for what I have.)
Is there an Android 4.4.2 Rom avail for Allwinner A13?
Click to expand...
Click to collapse
do backup
Sent from my XT1033 using XDA Premium 4 mobile app

[UTILITY] STrace 4.8 - Ultimate debugging utility now ported to Android !

about Strace
Android provides Logcat for tracing and debugging Apps , Logcat provides too short information and limited apps also programs has to support logcat or there wo'nt be any log ! this makes Android logcar be completely un-useful in large/advanced programs .
strace is a debugging utility to monitor a program system calls or signals it receives . strace is used while we want to find the reason a program crashes or finding out what causes a process not to work as expected .
strace is much more powerful than Android Logcat . unlike logcat , any process may be monitored by strace also there is no need to rewrite a program for support of strace
usage & downloading
I have ported strace to Android and it works without any bugs
download the lastest binary from this post , move it to /system/bin and set permissions to 755 .
strace has a lot of options you can find by running it using :
Code:
strace --help
most common functions are :
1- using strace to monitor a command :
Code:
strace echo hello
2- using strace to monitor an App/process :
Code:
strace -p 123
(123 is a example , use any other PID you wish )
here is an example of running strace with hello command :
Code:
ALIREZA | strace echo hello
execve("/system/xbin/echo", ["echo", "hello"], [/* 26 vars */]) = 0
mprotect(0x4005d000, 75164, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
mprotect(0x4005d000, 77824, PROT_READ|PROT_EXEC) = 0
mprotect(0x40070000, 4096, PROT_READ) = 0
gettid() = 31648
set_tls(0x40080f6c, 0x40080f30, 0x40081068, 0x40, 0x40080f30) = 0
getpid() = 31648
sigaction(SIGILL, {0x40062ba1, [], SA_RESTART|SA_SIGINFO}, NULL, 0x397a4) = 0
sigaction(SIGABRT, {0x40062ba1, [], SA_RESTART|SA_SIGINFO}, NULL, 0x397a4) = 0
sigaction(SIGBUS, {0x40062ba1, [], SA_RESTART|SA_SIGINFO}, NULL, 0x397a4) = 0
sigaction(SIGFPE, {0x40062ba1, [], SA_RESTART|SA_SIGINFO}, NULL, 0x397a4) = 0
sigaction(SIGSEGV, {0x40062ba1, [], SA_RESTART|SA_SIGINFO}, NULL, 0x397a4) = 0
sigaction(SIGSTKFLT, {0x40062ba1, [], SA_RESTART|SA_SIGINFO}, NULL, 0x397a4) = 0
sigaction(SIGPIPE, {0x40062ba1, [], SA_RESTART|SA_SIGINFO}, NULL, 0x397a4) = 0
mprotect(0x8000, 500100, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
stat64("/vendor/lib/libc.so", 0xbea736b8) = -1 ENOENT (No such file or directory)
stat64("/system/lib/libc.so", {st_mode=S_IFREG|0644, st_size=286596, ...}) = 0
open("/system/lib/libc.so", O_RDONLY) = 7
lseek(7, 0, SEEK_SET) = 0
read(7, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\0\0\0\0004\0\0\0"..., 4096) = 4096
lseek(7, -8, SEEK_END) = 286588
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
mmap2(NULL, 331776, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x400f7000
madvise(0x400f7000, 331776, 0xc /* MADV_??? */) = 0
mmap2(0x400f7000, 271932, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 7, 0) = 0x400f7000
madvise(0x400f7000, 271932, 0xc /* MADV_??? */) = 0
mprotect(0x400f7000, 274432, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
mmap2(0x4013a000, 10344, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 7, 0x43) = 0x4013a000
madvise(0x4013a000, 10344, 0xc /* MADV_??? */) = 0
mmap2(0x4013d000, 45051, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x4013d000
madvise(0x4013d000, 45051, 0xc /* MADV_??? */) = 0
close(7) = 0
mprotect(0x400f7000, 274432, PROT_READ|PROT_EXEC) = 0
stat64("/vendor/lib/liblog.so", 0xbea736b8) = -1 ENOENT (No such file or directory)
stat64("/system/lib/liblog.so", {st_mode=S_IFREG|0644, st_size=13536, ...}) = 0
open("/system/lib/liblog.so", O_RDONLY) = 7
lseek(7, 0, SEEK_SET) = 0
read(7, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\0\0\0\0004\0\0\0"..., 4096) = 4096
lseek(7, -8, SEEK_END) = 13528
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
mmap2(NULL, 20480, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x4000d000
madvise(0x4000d000, 20480, 0xc /* MADV_??? */) = 0
mmap2(0x4000d000, 11235, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 7, 0) = 0x4000d000
madvise(0x4000d000, 11235, 0xc /* MADV_??? */) = 0
mprotect(0x4000d000, 12288, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
mmap2(0x40010000, 4116, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 7, 0x2) = 0x40010000
madvise(0x40010000, 4116, 0xc /* MADV_??? */) = 0
close(7) = 0
stat64("/vendor/lib/libstdc++.so", 0xbea73618) = -1 ENOENT (No such file or directory)
stat64("/system/lib/libstdc++.so", {st_mode=S_IFREG|0644, st_size=5336, ...}) = 0
open("/system/lib/libstdc++.so", O_RDONLY) = 7
lseek(7, 0, SEEK_SET) = 0
read(7, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\0\0\0\0004\0\0\0"..., 4096) = 4096
lseek(7, -8, SEEK_END) = 5328
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
mmap2(NULL, 12288, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40082000
madvise(0x40082000, 12288, 0xc /* MADV_??? */) = 0
mmap2(0x40082000, 2656, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 7, 0) = 0x40082000
madvise(0x40082000, 2656, 0xc /* MADV_??? */) = 0
mprotect(0x40082000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
mmap2(0x40083000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 7, 0) = 0x40083000
madvise(0x40083000, 4096, 0xc /* MADV_??? */) = 0
mmap2(0x40084000, 16, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40084000
madvise(0x40084000, 16, 0xc /* MADV_??? */) = 0
close(7) = 0
mprotect(0x40082000, 4096, PROT_READ|PROT_EXEC) = 0
mprotect(0x40083000, 4096, PROT_READ) = 0
stat64("/vendor/lib/libm.so", 0xbea73618) = -1 ENOENT (No such file or directory)
stat64("/system/lib/libm.so", {st_mode=S_IFREG|0644, st_size=91288, ...}) = 0
open("/system/lib/libm.so", O_RDONLY) = 7
lseek(7, 0, SEEK_SET) = 0
read(7, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\0\0\0\0004\0\0\0"..., 4096) = 4096
lseek(7, -8, SEEK_END) = 91280
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
mmap2(NULL, 98304, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x400d8000
madvise(0x400d8000, 98304, 0xc /* MADV_??? */) = 0
mmap2(0x400d8000, 85924, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 7, 0) = 0x400d8000
madvise(0x400d8000, 85924, 0xc /* MADV_??? */) = 0
mprotect(0x400d8000, 86016, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
mmap2(0x400ee000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 7, 0x15) = 0x400ee000
madvise(0x400ee000, 4096, 0xc /* MADV_??? */) = 0
mmap2(0x400ef000, 32, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x400ef000
madvise(0x400ef000, 32, 0xc /* MADV_??? */) = 0
close(7) = 0
mprotect(0x400d8000, 86016, PROT_READ|PROT_EXEC) = 0
mprotect(0x400ee000, 4096, PROT_READ) = 0
mprotect(0x4000d000, 12288, PROT_READ|PROT_EXEC) = 0
mprotect(0x40010000, 4096, PROT_READ) = 0
stat64("/vendor/lib/libcutils.so", 0xbea736b8) = -1 ENOENT (No such file or directory)
stat64("/system/lib/libcutils.so", {st_mode=S_IFREG|0644, st_size=63252, ...}) = 0
open("/system/lib/libcutils.so", O_RDONLY) = 7
lseek(7, 0, SEEK_SET) = 0
read(7, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\0\0\0\0004\0\0\0"..., 4096) = 4096
lseek(7, -8, SEEK_END) = 63244
read(7, "\1\0\0\0\0\0\0\0", 8) = 8
mmap2(NULL, 126976, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40148000
madvise(0x40148000, 126976, 0xc /* MADV_??? */) = 0
mmap2(0x40148000, 58972, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 7, 0) = 0x40148000
madvise(0x40148000, 58972, 0xc /* MADV_??? */) = 0
mprotect(0x40148000, 61440, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
mmap2(0x40157000, 4620, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 7, 0xe) = 0x40157000
madvise(0x40157000, 4620, 0xc /* MADV_??? */) = 0
mmap2(0x40159000, 57096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40159000
madvise(0x40159000, 57096, 0xc /* MADV_??? */) = 0
close(7) = 0
mprotect(0x40148000, 61440, PROT_READ|PROT_EXEC) = 0
mprotect(0x40157000, 4096, PROT_READ) = 0
mprotect(0x8000, 503808, PROT_READ|PROT_EXEC) = 0
mmap2(NULL, 49152, PROT_READ, MAP_SHARED, 8, 0) = 0x400a4000
futex(0x40140734, FUTEX_WAKE_PRIVATE, 2147483647) = 0
open("/dev/urandom", O_RDONLY) = 7
read(7, "@\236", 4) = 4
close(7) = 0
clock_gettime(CLOCK_MONOTONIC, {29544, 299349465}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40167000
madvise(0x40167000, 4096, 0xc /* MADV_??? */) = 0
mprotect(0x40167000, 4096, PROT_READ) = 0
getuid32() = 0
brk(0) = 0xf0d000
brk(0xf0d000) = 0xf0d000
brk(0xf0e000) = 0xf0e000
write(1, "hello\n", 6hello
) = 6
mprotect(0x40167000, 4096, PROT_READ|PROT_WRITE) = 0
mprotect(0x40167000, 4096, PROT_READ) = 0
futex(0x4014072c, FUTEX_WAKE_PRIVATE, 2147483647) = 0
munmap(0x40167000, 4096) = 0
exit_group(0) = ?
and now lastest download link :
Download Strace 4.8 from here
license
strace is a free software, you may download source of strace from here

Only 4 downloads ?!

Segfault any attemp to use it!
Running on LG P500 (ARMv6) cm-10.2
OK, guess what? Already have it on /system/xbin and that does work.

Very nice tool/utility man.....
will try it to solve issues on my roms...
thanks man :good:
regards,
abhi922.

abhi922 said:
Very nice tool/utility man.....
will try it to solve issues on my roms...
thanks man :good:
regards,
abhi922.
Click to expand...
Click to collapse
Dido, I needed such a tool too.
Thanks

Would like to try it, but the download link requires me to sign up for an account. Can't you make this available some other way?

you dont need an account to download. Between the 2 ads is the download button

SVLAN said:
you dont need an account to download. Between the 2 ads is the download button
Click to expand...
Click to collapse
Thanks, I got it! I really hate these purposely misleading download sites.

Once i run strace -p 123 it will come back
Code:
strace: attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted

SVLAN said:
Once i run strace -p 123 it will come back
Code:
strace: attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted
Click to expand...
Click to collapse
I said :
(123 is a example , use any other PID you wish )
Click to expand...
Click to collapse
You must use the a valid PID , 123 is an example .
For getting PID of an APP/Process , use the this command in terminal :
Code:
ps | grep "abc"
instead of abc , write the process name you want ! for example :
Code:
ps | grep "com.android.acore"
then search for PID in the output and use it with strace !

SVLAN said:
Once i run strace -p 123 it will come back
Code:
strace: attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted
Click to expand...
Click to collapse
You need to be root to attach to already running processes.
I also find the "-f" option useful for more complex executables (which fork new processes). "-o" to write the output to a file can be useful if there is much output.

@alireza7991
Can I use this in the tool in my signature please?

Lgrootnoob said:
@alireza7991
Can I use this in the tool in my signature please?
Click to expand...
Click to collapse
This is a free software , You must accept the GNU Public Licence v2 ( or higher ) terms ; after that , you are allowed to use it .

alireza7991 said:
This is a free software , You must accept the GNU Public Licence v2 ( or higher ) terms ; after that , you are allowed to use it .
Click to expand...
Click to collapse
Sweet!

Huh? It's a well-known, standard unix utility, being a part of Android distribution since Android 1.6 (although, only in debug builds)...
See https://android.googlesource.com/platform/external/strace/ (note all the branches on the left)
It's good to make people aware of it, though, as it's a very useful tool for debugging some kinds of issues.

tom3q said:
Huh? It's a well-known, standard unix utility, being a part of Android distribution since Android 1.6 (although, only in debug builds)...
See https://android.googlesource.com/platform/external/strace/ (note all the branches on the left)
It's good to make people aware of it, though, as it's a very useful tool for debugging some kinds of issues.
Click to expand...
Click to collapse
I haven't seen it, but its just in android sources and only in debug builds for debugging the android but This is a standalone build of latest STrace suitable for developers to debug their APPs . Developers will not download and compile whole android for just having a dynamicly linked strace .
Another thing , why most of you are saying its a well-known/popular linux utility ... , did I say it is not ????

Segfaults on Razr i (intel atom x86).

alireza7991 said:
I haven't seen it, but its just in android sources and only in debug builds for debugging the android but This is a standalone build of latest STrace suitable for developers to debug their APPs . Developers will not download and compile whole android for just having a dynamicly linked strace .
Another thing , why most of you are saying its a well-known/popular linux utility ... , did I say it is not ????
Click to expand...
Click to collapse
But that's something that's popular to do here, a lot of people download the sources and compile the ROMs they run from source. Additionally, this is probably included in every custom ROM out there. My CM10.2 install has the utility built in.
There's no need to be defensive, the RD that's replying to you is just providing links for more reading. The better informed the users of this site are, the more cool stuff we'll see in the future.
Thanks for your strace build!

r3tr0g4m3r said:
Segfaults on Razr i (intel atom x86).
Click to expand...
Click to collapse
This does not work on X86 based platforms.

There're quite a few blog posts on the net about compiling strace from source.
Eg. http://discuz-android.blogspot.com/2008/01/create-google-android-strace-tool.html
I've created a precompiled tgz package that you can extract into the root of your filesystem and it'll put strace into /data/local (i.e. /data/local/bin/strace).
http://muzso.hu/node/4869
I prefer my utilities in /data/local.

Database Info

welcome