[DEV] Mediapad 10 Link Developer/debug info {LTE Model} - Huawei MediaPad, T-Mobile SpringBoard

Hi All
I recently purchased the Mediapad 10 Link LTE model.
As is my usual habit I am posting my research into the device here. This info is not useful to the day to day user but is ment as a resource of information for developers.
CPU: Hi3620 K3v2 (K3V200)
BaseBand: balong710 (not proven exactly, could be x-gold , needs confirming)
Here i've posted the initial parition data
Parition Information
i rooted early on using Framaroot and Pippin exploit,
I backed up all the partitions and have been running reversing on many
although the cache parition showed no files i did run strings on it returning some usefull info from it's inital setup at factory(assumed)
==================update partition list=================
partition table changed, upgrading partition table...
============upgrade partition table =============
*******************GPT*************************
GptHeader.signatureX: E F I P A R T
GptHeader.revision: 0x00010000
GptHeader.header_size: 0x0000005c
GptHeader.header_crc32: 0x26d7c5cc
GptHeader.my_lba: 0x0000000000000001
GptHeader.alternate_lba: 0x0000000001d59fff
GptHeader.first_usable_lba:0x0000000000000022
GptHeader.last_usable_lba: 0x0000000001d59fff
GptHeader.partition_entry_array_crc32:0x40252416
GptHeader.partition_entry_lba: 0x0000000000000002
GptHeader.num_partition_entries: 0x00000080
GptHeader.sizeof_partition_entry: 0x00000080
partition first_lba last_lba size
xloader 0x100 0x2ff 0M
round 0x300 0x1fff 3M
nvme 0x2000 0x3fff 4M
misc 0x4000 0x5fff 4M
splash 0x6000 0x9fff 8M
oeminfo 0xa000 0x19fff 32M
logo 0x1a000 0x1ffff 12M
vrcb 0x20000 0x21fff 4M
recovery2 0x22000 0x29fff 16M
recovery 0x2a000 0x31fff 16M
boot 0x32000 0x35fff 8M
modemimage 0x36000 0x55fff 64M
modemnv 0x56000 0x59fff 8M
modemnv2 0x5a000 0x5dfff 8M
cache 0x5e000 0xddfff 256M
system 0xde000 0x1ddfff 512M
cust 0x1de000 0x2ddfff 512M
userdata 0x2de000 0x2e5fff 16M
reserve1 0x2e6000 0x2edfff 16M
reserve2 0x2ee000 0x2f5fff 16M
lowpower 0x2f6000 0x2fdfff 16M
data 0x2fe000 0x1d59fff 13496M
=========================================
completing update partition list...
complete_update_partition_list mod boot :first_lba=204800,last_lba=221183
complete_update_partition_list mod recovery :first_lba=172032,last_lba=204799
complete_update_partition_list mod modemimage :first_lba=221184,last_lba=352255
complete_update_partition_list mod modemnv :first_lba=352256,last_lba=368639
complete_update_partition_list mod logo :first_lba=106496,last_lba=131071
complete_update_partition_list mod lowpower :first_lba=3104768,last_lba=3137535
complete_update_partition_list mod vrcb :first_lba=131072,last_lba=139263
complete_update_partition_list mod round :first_lba=768,last_lba=8191
complete_update_partition_list mod userdata :first_lba=3006464,last_lba=3039231
complete_update_partition_list mod system :first_lba=909312,last_lba=1957887
complete_update_partition_list mod cust :first_lba=1957888,last_lba=3006463
complete_update_partition_list mod cache :first_lba=385024,last_lba=909311
==================update partition list=================
partition start_offset dwDataLen first_lba last_lba compress
fastboot 0x13318 0x4610c 0 0 0
boot 0x59dbe 0x49b800 0x32000 0x35fff 0
recovery 0x4f6212 0x5f7800 0x2a000 0x31fff 0
modemimage 0xaf47ac 0x369a094 0x36000 0x55fff 0
modemnv 0x418f5d8 0x69a094 0x56000 0x59fff 0
logo 0x4829e9e 0x3e8000 0x1a000 0x1ffff 0
lowpower 0x4c12f3a 0x81b1ba 0x2f6000 0x2fdfff 0
vrcb 0x542e158 0x200 0x20000 0x21fff 0
round 0x542e3bc 0x200 0x300 0x1fff 0
userdata 0x542eeba 0x44d088 0x2de000 0x2e5fff 0
system 0x58ba8ee 0x1f4a3c28 0xde000 0x1ddfff 0
cust 0x24d89d8c 0x15c08a54 0x1de000 0x2ddfff 0
cache 0x3a993476 0x6190c4 0x5e000 0xddfff 0
sd_blacklist 0x3afac5a0 0x8 0 0 0
sensors 0x3afac708 0x7e796 0 0 0
=================================================
writing partitions...
[firmware_update]:write_partition fastboot
[write_partition_fastboot]:img_file_sizes=286988
[write_partition_fastboot]:success write fastboot_need_write_size(0x10800) to boot0 emmc
[write_partition_fastboot]:write_partition_xloader start.size=3590c
[write_partition_xloader]:success write image to emmc
[firmware_update]:write_partition bootsd_offset = 0x59dbe
vrlhead.MegicNumber:SecVRLTableV1.1
Don't copy boot's vrl header into partition
list_entry.dwDataLen = 0x0049b000
list_entry.start_offset = 0x5a5be
vrlhead.VrlItemTab.Address = 0x05200100
vrl_addr = 0x5200000
tmp_entry->name:sec_token
Click to expand...
Click to collapse
and
Find update package success path:/mnt/sdcard2/dload/update.app
update_package_exist,total upgrade file size=990031520
read_power_supply_info, success to open power supply file /sys/class/power_supply/ChargerAC/online
read_power_supply_info, power supply info is 1
check_charger_online, charger_ac online
low_power_check, charger is online
huawei_sd_update:update_threshold_check success...
coulometer_firmware_upgrade ret = 0
update coulmeter successfully
umount /system error=-1
update coulmeter:unmount system fail
update_threshold_check, boot.status=
get_specified_mbn, fopen /mnt/sdcard2/dload/update.app success!
first module: old_off = 92
first module: dwHeaderlen = 100
first module: dwHeaderVer = 1
first module: dwDataStarAdd = 0xffffffff
first module: dwDatalen = 128
first module: date = 2013.08.21
first module: time = 14.49.21
first module: name = MD5RSA
get_specified_mbn , success to find first module head MD5RSA
first module is not CRC module
mod_head szDispName = CRC:
dwHeaderLen = 128, dwDataStarAdd = 0xffffffff,dwDataLen = 60412,date = 2013.08.21,time = 14.49.21
get_specified_mbn Read module to memory success
get_crc_mbn success...
Create tmp file for integrity check success
Get crclist module raw data success :60412 byte
first module: old_off = 92
first module: dwHeaderlen = 100
first module: dwHeaderVer = 1
first module: dwDataStarAdd = 0xffffffff
first module: dwDatalen = 128
first module: date = 2013.08.21
first module: time = 14.49.21
first module: name = MD5RSA
Begin circulate crc check each module...
sacan first module over
mod_head szDispName = CRC:
dwHeaderLen = 128, dwDataStarAdd = 0xffffffff,dwDataLen = 60412,date = 2013.08.21,time = 14.49.21
mod_head szDispName = PTABLE:
dwHeaderLen = 108, dwDataStarAdd = 0xffffffff,dwDataLen = 17408,date = 2013.08.21,time = 14.49.22
module PTABLE is not compressed
module PTABLE crc check success..................
parsing ptable from update package...
============ partition table =============
partition first_lba last_lba size
xloader 0x100 0x2ff 0M
round 0x300 0x1fff 3M
nvme 0x2000 0x3fff 4M
misc 0x4000 0x5fff 4M
splash 0x6000 0x9fff 8M
oeminfo 0xa000 0x19fff 32M
logo 0x1a000 0x1ffff 12M
vrcb 0x20000 0x21fff 4M
recovery2 0x22000 0x29fff 16M
recovery 0x2a000 0x31fff 16M
boot 0x32000 0x35fff 8M
modemimage 0x36000 0x55fff 64M
modemnv 0x56000 0x59fff 8M
modemnv2 0x5a000 0x5dfff 8M
cache 0x5e000 0xddfff 256M
system 0xde000 0x1ddfff 512M
cust 0x1de000 0x2ddfff 512M
userdata 0x2de000 0x2e5fff 16M
reserve1 0x2e6000 0x2edfff 16M
reserve2 0x2ee000 0x2f5fff 16M
lowpower 0x2f6000 0x2fdfff 16M
data 0x2fe000 0xd8ffff 5412M
=========================================
mod_head szDispName = FASTBOOT:
dwHeaderLen = 240, dwDataStarAdd = 0xffffffff,dwDataLen = 286988,date = 2013.08.21,time = 14.49.22
module FASTBOOT is not compressed
module FASTBOOT crc check success..................
mod_head szDispName = BOOT:
dwHeaderLen = 2458, dwDataStarAdd = 0xffffffff,dwDataLen = 4831232,date = 2013.08.21,time = 14.49.22
module BOOT is not compressed
module BOOT crc check success..................
mod_head szDispName = RECOVERY:
dwHeaderLen = 3154, dwDataStarAdd = 0xffffffff,dwDataLen = 6256640,date = 2013.08.21,time = 14.49.22
module RECOVERY is not compressed
module RECOVERY crc check success..................
mod_head szDispName = MODEMIMAGE:
dwHeaderLen = 28056, dwDataStarAdd = 0xffffffff,dwDataLen = 57254036,date = 2013.08.21,time = 14.49.22
module MODEMIMAGE is not compressed
module MODEMIMAGE crc check success..................
mod_head szDispName = MODEMNV:
dwHeaderLen = 3480, dwDataStarAdd = 0xffffffff,dwDataLen = 6922388,date = 2013.08.21,time = 14.49.24
module MODEMNV is not compressed
module MODEMNV crc check success..................
mod_head szDispName = LOGO:
dwHeaderLen = 2098, dwDataStarAdd = 0xffffffff,dwDataLen = 4096000,date = 2013.08.21,time = 14.49.24
module LOGO is not compressed
module LOGO crc check success..................
mod_head szDispName = LOWPOWER:
dwHeaderLen = 4250, dwDataStarAdd = 0xffffffff,dwDataLen = 8499642,date = 2013.08.21,time = 14.49.24
module LOWPOWER is not compressed
module LOWPOWER crc check success..................
mod_head szDispName = VRCB:
dwHeaderLen = 100, dwDataStarAdd = 0xffffffff,dwDataLen = 512,date = 2013.08.21,time = 14.49.24
module VRCB is not compressed
module VRCB crc check success..................
mod_head szDispName = ROUND:
dwHeaderLen = 100, dwDataStarAdd = 0xffffffff,dwDataLen = 512,date = 2013.08.21,time = 14.49.24
module ROUND is not compressed
module ROUND crc check success..................
mod_head szDispName = USERDATA:
dwHeaderLen = 2302, dwDataStarAdd = 0xffffffff,dwDataLen = 4509832,date = 2013.08.21,time = 14.49.24
module USERDATA is not compressed
module USERDATA crc check success..................
mod_head szDispName = SYSTEM:
dwHeaderLen = 256426, dwDataStarAdd = 0xffffffff,dwDataLen = 524958760,date = 2013.08.21,time = 14.49.24
module SYSTEM is not compressed
module SYSTEM crc check success..................
mod_head szDispName = CUST:
dwHeaderLen = 178292, dwDataStarAdd = 0xffffffff,dwDataLen = 364939860,date = 2013.08.21,time = 14.49.37
module CUST is not compressed
module CUST crc check success..................
mod_head szDispName = CACHE:
dwHeaderLen = 3222, dwDataStarAdd = 0xffffffff,dwDataLen = 6394052,date = 2013.08.21,time = 14.49.46
module CACHE is not compressed
module CACHE crc check success..................
mod_head szDispName = SD_BLACKLIST:
dwHeaderLen = 100, dwDataStarAdd = 0xffffffff,dwDataLen = 8,date = 2013.08.21,time = 14.49.46
module SD_BLACKLIST is not compressed
module SD_BLACKLIST crc check success..................
mod_head szDispName = SENSORS:
dwHeaderLen = 352, dwDataStarAdd = 0xffffffff,dwDataLen = 518038,date = 2013.08.21,time = 14.49.46
module SENSORS is not compressed
module SENSORS crc check success..................
Has scaned the entire module
Integrity check all success!
==================update partition list=================
partition start_offset dwDataLen first_lba last_lba compress
fastboot 0x13318 0x4610c 0 0 0
boot 0x59dbe 0x49b800 0 0 0
recovery 0x4f6212 0x5f7800 0 0 0
modemimage 0xaf47ac 0x369a094 0 0 0
modemnv 0x418f5d8 0x69a094 0 0 0
logo 0x4829e9e 0x3e8000 0 0 0
lowpower 0x4c12f3a 0x81b1ba 0 0 0
vrcb 0x542e158 0x200 0 0 0
round 0x542e3bc 0x200 0 0 0
userdata 0x542eeba 0x44d088 0 0 0
system 0x58ba8ee 0x1f4a3c28 0 0 0
cust 0x24d89d8c 0x15c08a54 0 0 0
cache 0x3a993476 0x6190c4 0 0 0
sd_blacklist 0x3afac5a0 0x8 0 0 0
sensors 0x3afac708 0x7e796 0 0 0
=================================================
recovery: upgrade_package_integrity_check success...
parsing current system ptable......
============ partition table =============
partition first_lba last_lba size
xloader 0x100 0x2ff 0M
round 0x300 0x1fff 3M
nvme 0x2000 0x3fff 4M
misc 0x4000 0x5fff 4M
splash 0x6000 0x9fff 8M
oeminfo 0xa000 0x19fff 32M
logo 0x1a000 0x1ffff 12M
vrcb 0x20000 0x21fff 4M
recovery2 0x22000 0x28fff 14M
recovery 0x2a000 0x31fff 16M
boot 0x32000 0x35fff 8M
modemimage 0x36000 0x55fff 64M
modemnv 0x56000 0x59fff 8M
modemnv2 0x5a000 0x5dfff 8M
cache 0x5e000 0xddfff 256M
system 0xde000 0x1ddfff 512M
cust 0x1de000 0x2ddfff 512M
userdata 0x2de000 0x2e5fff 16M
reserve1 0x2e6000 0x2edfff 16M
reserve2 0x2ee000 0x2f5fff 16M
reserve3 0x2f6000 0x2fdfff 16M
data 0x2fe000 0x1d59fff 13496M
=========================================
parse_ptable_from_file old_ptale success...
fixed_partition_changed_check success...
zhanting:cmdline = size=1G k3v2_lcd_density=1080p [email protected] console=ttyAMA0,115200 k3v2_pmem=1 vmalloc=512M androidboot.hardware=hws10201l
mmcparts=mmcblk01(xloader),p3(nvme),p4(misc),p5(splash),p6(oeminfo),p7(logo),p8(vrcb),p9(recovechecking img fastboot
sizeof(vrlhead) is 2048
sum = 2048
fastboot img has signed
checking img boot
sizeof(vrlhead) is 2048
sum = 2048
boot img has signed
checking img recovery
sizeof(vrlhead) is 2048
sum = 2048
recovery img has signed
[secure_boot_check]:success read fastboot's vrl header from boot0 emmc
boot's vrl addr is 0x05200000
recovery's vrl addr is 0x05208000
huawei_sd_update:integrity_validity_check success...
sd_upgrade_spare_space_check,cust.zip exist...
spare_space_check, the free space of /data is 13052854272
spare_space_check, free space is 13052854272,the size of total files in cust.zip is 0
spare_space_check, space is enough!
sensors_upgrade,sensors path /mnt/sdcard2/dload/sensors.zip
sensors_upgrade, open zip package fail......
partition table changed checking...
data block device path =/dev/block/mmcblk0p22
blk_sec: 30777344.
mmc partition num =22
sum_sec: 3133184
data_sec: 27639808
fs_sec:27639808
partition table changed
Click to expand...
Click to collapse
and
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /mnt/sdcard2 vfat /dev/block/platform/hi_mci.0/mmcblk1p1 (null) 0
2 /system ext4 /dev/block/mmcblk0p16 (null) 0
3 /cache ext4 /dev/block/mmcblk0p15 (null) 0
4 /tmpdata ext4 /dev/block/mmcblk0p18 (null) 0
5 /misc emmc /dev/block/mmcblk0p4 (null) 0
6 /boot emmc /dev/block/mmcblk0p11 (null) 0
7 /recovery emmc /dev/block/mmcblk0p10 (null) 0
8 /data ext4 /dev/block/mmcblk0p22 (null) 0
9 /cust ext4 /dev/block/mmcblk0p17 (null) 0
10 /vrcb emmc /dev/block/mmcblk0p8 (null) 0
I:Boot command: RESET:FACTORY
I:Got arguments from boot message
Command: "recovery" "--part_of_data_format"
ro.runmode=normal
Click to expand...
Click to collapse
I still have more research to format/layout and post. I need to also remove imei/serials from the postings but stay tuned.
DEVS, feel free to post your data.
Please avoid posting questions/recoveries/problems here, keep this thread to known facts needed for development.

Kernel-Device trees
Here is a list of other devices with same cpu, devices marked in red are LTE devices.
Code:
Hi3620 devices
[COLOR="red"]Huawei Ascend D2-6070 TD-LTE
Huawei MediaPad 10 Link LTE-A S10-201L 16GB
Huawei MediaPad 10 Link LTE-A S10-201L 32GB
Huawei MediaPad 10 FHD LTE S10-101L 64GB[/COLOR]
Huawei MediaPad 10 FHD S10-101u 64GB
Huawei MediaPad 10 FHD WiFi S10-101w
Huawei MediaPad 10 FHD S10-101u 16GB
Huawei MediaPad 7 Vogue
Huawei MediaPad 10 Link 3G S10-201u 16GB
Huawei MediaPad 10 Link WiFi S10-201w 16GB
NTT DoCoMo Huawei MediaPad 10 Link / dtab S10-201wd
Huawei STREAM X GL07S
Huawei Honor 3 HN3-U01
Huawei Honor 2 / Honor Quad (Huawei U9508)
Huawei Ascend D2-5000 TD
Huawei Ascend D2-0082 HSPA
Huawei Ascend G615
Huawei Ascend D2-2010 CDMA
Huawei Ascend D1 Quad / Ascend D quad (Huawei U9510)
Huawei Ascend D1 Quad XL (Huawei T9510E)
Huawei Ascend D1 Quad XL / Ascend D quad XL (Huawei U9510E)
[COLOR="red"]Huawei Ascend P2-6011 LTE- src-avalilable[/COLOR]
Huawei Ascend P2
Huawei Ascend Mate MT1-T00
Huawei A199
Huawei Ascend D2 HW-03E (Huawei U9701L)
Huawei Ascend Mate MT1-U06
Device(s) on list above with kernel sources links for comparision/possible ports
Huawei Ascend P2-6011 LTE
Huawei Ascend Mate MT1-U06
Huawei Ascend D2-0082 HSPA
Huawei Ascend G615
Additional info,
Going over Huawei kernel list it seems like the devices with MSM based chips for cpu have newer kernels 3.4 etc and it's own chips are still on 3.0.8
it would be nice if they updated that part. oh well.
A comparison of the two kernels for P2-6011 and Ascend D2-0082 shows no difference apart from make files for android, they both used the same defconfig/.config file, that gives hope for a quick kernel port but could also have changes deeper in the make/.mk files that are introduced with build directives so first I want to build the kernels and then start looking deeper into the sources.
I've found quite a few once I fixed my search parameters. Further work continues.
Full Kernel source found, please note that althought these sources compile , Ive yet too test due to the tablet having a locked bootloader,
Forked kernel sources -Not fully tested

Device specific info - LCD - Touch etc
Kernel Command Line
mem_size=1G k3v2_lcd_density=1080p [email protected] console=ttyS0 k3v2_pmem=1 vmalloc=512M androidboot.hardware=hws10201l mmcparts=mmcblk01(xloader),p3(nvme),p4(misc),p5(splash),p6(oeminfo),p7(logo),p8(vrcb),p9(recovery2),p10(recovery),p11(boot),p12(modemimage),p13(modemnv),p14(modemnvm2),p15(cache),p16(system),p17(cust),p18(userdata),p19(reserve1),p20(reserve2),p21(lowpower),p22(data);mmcblk11(sdcard2) boardid=0x36200110,0x00000025,0x00000082 hw_version=0x0000031f,0x00000623,0x00000000,0x00000001 pd_charge=0 androidboot.serialno=Z3PXXXXXXXXXXX androidboot.swtype=normal fastboot_version=S10-20XlV100R002C001B008SP03_FASTBOOT hpm_value=67 normal_reset_type=ColdReset, cpu_maxfreq=0
Click to expand...
Click to collapse
/proc/bus/devices
Code:
[email protected]:/proc # cat bus/input/devices
I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="k3v2_power_key"
P: Phys=
S: Sysfs=/devices/platform/k3v2_power_key/input/input0
U: Uniq=
H: Handlers=event0
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="k3v2_gpio_key"
P: Phys=
S: Sysfs=/devices/platform/s10_gpio_key/input/input1
U: Uniq=
H: Handlers=event1
B: PROP=0
B: EV=3
B: KEY=c0000 0 0 0
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="sensor00fn11"
P: Phys=sensor00fn11/input0
S: Sysfs=/devices/sensor00/input/input2
U: Uniq=
H: Handlers=event2
B: PROP=2
B: EV=b
B: KEY=0
B: ABS=6730000 0
I: Bus=0018 Vendor=0000 Product=0000 Version=0000
N: Name="acc_input"
P: Phys=
S: Sysfs=/devices/platform/dw-i2c.0/i2c-0/0-0018/input/input3
U: Uniq=
H: Handlers=event3
B: PROP=0
B: EV=9
B: ABS=100 107
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="yamaha_orientation"
P: Phys=
S: Sysfs=/devices/platform/yamaha_orientation.0/input/input4
U: Uniq=
H: Handlers=event4
B: PROP=0
B: EV=9
B: ABS=100 4c7
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HI3620_HI6421_CARD Headset Jack"
P: Phys=ALSA
S: Sysfs=/devices/platform/soc-audio/sound/card0/input5
U: Uniq=
H: Handlers=event5
B: PROP=0
B: EV=23
B: KEY=4 0 0 0 0 0 0 0
B: SW=14
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="lightsensor"
P: Phys=
S: Sysfs=/devices/virtual/input/input6
U: Uniq=
H: Handlers=event6
B: PROP=0
B: EV=9
B: ABS=100 0
[email protected]:/proc #
Sensors:-
LIS303DLHC 3-axis Accelerometer (STMicroelectronics)
AK8963 3-axis Magnetic field sensor (Asahi Kasei Microdevices)
iNemo Orientation sensor (STMicroelectronics)
Light sensor (sensor is 1inch to left of camera) (Taos)
Touch screen synaptics product: TM2662-006 (rmi generic 4)
yamaha orientation (unknown detail yet)
**Pages will be updated as info is sorted**

Related

[Q] OpenVPN with tun.ko

Anyone got OpenVPN running in mini pro?
I tried but it always crash at "get config" in OpenVPN-Settings, and I saw it was crashed at something with routing under console app.
I got the crash report from system, anyone successful with using OpenVPN in mini pro?
crashtime:1298549297
crashtype:1
cpuid:0
processnameOG
crashstring:Watchdog
logname:
crashlog:ERR crash log report. Version 2.
Error in file CM, line 0
Time of crash (m-d-y h:m:s): 02-24-2011 12:06:55
Uptime (h:m:s): 20:13:21
Build ID: M76XX-TSNCJOLYM-53404015
REX_TCB ptr: 0x0f25024c
tcb.task_name: DOG
Register values from rex_core:
ARM_SVC_R0 : 0x0000007d
ARM_SVC_R1 : 0xe010080a
ARM_SVC_R2 : 0x00000000
ARM_SVC_R3 : 0xffff0948
ARM_SVC_R4 : 0x00000015
ARM_SVC_R5 : 0x0e9c10f0
ARM_SVC_R6 : 0x0f3012b8
ARM_SVC_R7 : 0x000000ff
ARM_SVC_R8 : 0x00000000
ARM_SVC_R9 : 0x00000000
ARM_SVC_R10 : 0x00000000
ARM_SVC_R11 : 0x00000000
ARM_SVC_R12 : 0x80000010
ARM_SVC_SP : 0x00000000
ARM_SVC_LR : 0x00000000
ARM_SVC_SPSR : 0x00000000
ARM_SVC_PC : 0x0e62c31c
ARM_SYS_SP : 0x0f251458
ARM_SYS_LR : 0x0dec79d7
ARM_IRQ_SP : 0x00000000
ARM_IRQ_LR : 0x00000000
ARM_IRQ_SPSR : 0x00000000
ARM_ABT_SP : 0x00000000
ARM_ABT_LR : 0x00000000
ARM_ABT_SPSR : 0x00000000
ARM_UDF_SP : 0x00000000
ARM_UDF_LR : 0x00000000
ARM_UDF_SPSR : 0x00000000
ARM_FIQ_R8 : 0x00000000
ARM_FIQ_R9 : 0x00000000
ARM_FIQ_R10 : 0x00000000
ARM_FIQ_R11 : 0x00000000
ARM_FIQ_R12 : 0x00000000
ARM_FIQ_SP : 0x00000000
ARM_FIQ_LR : 0x00000000
ARM_FIQ_SPSR : 0x00000000
ARM_JVA_SP : 0x00000000
ARM_JVA_LR : 0x00000000
ARM_JVA_SPSR : 0x00000000
ARM_CPSR : 0x20000010
Stack Dump (from 0x0f251458):
Addr Data
0x0f251458 0x0f2502e8
0x0f25145c 0x0dec793b
0x0f251460 0x00000000
0x0f251464 0x00000000
0x0f251468 0x00000000
0x0f25146c 0x0eadf975
0x0f251470 0x00000000
0x0f251474 0x0e988088
0x0f251478 0x00000000
Dog Report Information (dog_task_info and dog_task_state)
[idx] Task Name Pri Timeout Count Is_Blocked
[ 0] SND 233 3 2 0
[ 1] 0 0 156 0
[ 2] 0 0 156 0
[ 3] 0 0 156 0
[ 4] 0 0 156 0
[ 5] 0 0 156 0
[ 6] HS 174 11 10 0
[ 7] DIAG 156 11 10 0
[ 8] UI 138 41 37 0
[ 9] NV 130 60 59 0
[ 10] 0 0 156 0
[ 11] 0 0 156 0
[ 12] DS 116 119 118 0
[ 13] PS 113 119 118 0
[ 14] 0 0 156 0
[ 15] SLEEP 2 237 237 0
[ 16] 0 0 156 0
[ 17] 0 0 156 0
[ 18] 0 0 156 0
[ 19] 0 0 156 0
[ 20] EFS 125 60 59 0
[ 21] CM 155 21 0 0
[ 22] VOC 159 11 11 0
[ 23] 0 0 157 0
[ 24] 0 0 157 0
[ 25] 0 0 157 0
[ 26] 0 0 157 0
[ 27] 0 0 157 0
[ 28] QDSP 225 11 11 0
[ 29] 0 0 157 0
[ 30] 0 0 157 0
[ 31] 0 0 157 0
[ 32] 0 0 157 0
[ 33] SEC 103 119 21 1
[ 34] UIM 132 60 60 0
[ 35] 0 0 157 0
[ 36] 0 0 157 0
[ 37] 0 0 157 0
[ 38] 0 0 157 0
[ 39] 0 0 157 0
[ 40] WMS 149 21 11 0
[ 41] TMC 202 11 11 0
[ 42] MMoC 175 11 11 0
[ 43] GSDI 119 60 59 0
[ 44] MDSP 231 60 60 0
[ 45] GCSD 187 11 11 0
[ 46] GSML1 227 11 11 0
[ 47] GSML2 197 11 11 0
[ 48] GLLC 186 11 11

[Recovery ROM] Full recovery ROM for YP-G70 8G INTERNATIONAL

Hi there.
As I promised, here is a full rom of YP-G70 8G INTERNATIONAL version. Based on G70ZSKP8. This is for recovery pruposes (ex. bricked device).
You will need:
- Odin.
- PIT file. Download here.
- ROM. Download here.
Flash it with odin. If you hard-bricked your device, make sure you hit re-partition and phone bootoader update.
What technique or program did you use specifically to identify and extract this partitions files.
The PIT file was pulled with Heimdall (doing a dd dump gets the same file but instead of 4k, you get a 256k file). Also, you can print the output to see which filename of the rom gets on every partition when Odin flashes it.
Also checked the partition table with fdisk and their size. Here is the output:
Code:
# partition table of /dev/mmcblk0
unit: sectors
/dev/mmcblk0p1 : start= 64, size= 15515584, Id= 5
/dev/mmcblk0p2 : start= 0, size= 0, Id= 0
/dev/mmcblk0p3 : start= 0, size= 0, Id= 0
/dev/mmcblk0p4 : start= 0, size= 0, Id= 0
/dev/mmcblk0p5 : start= 128, size= 512, Id=83
/dev/mmcblk0p6 : start= 704, size= 512, Id=83
/dev/mmcblk0p7 : start= 1280, size= 2560, Id=83
/dev/mmcblk0p8 : start= 3904, size= 2560, Id=83
/dev/mmcblk0p9 : start= 6528, size= 10240, Id=83
/dev/mmcblk0p10: start= 16832, size= 20480, Id=83
/dev/mmcblk0p11: start= 37376, size= 15360, Id=83
/dev/mmcblk0p12: start= 52800, size= 15360, Id=83
/dev/mmcblk0p13: start= 68224, size= 593920, Id=83
/dev/mmcblk0p14: start= 662208, size= 274432, Id=83
/dev/mmcblk0p15: start= 936704, size= 131072, Id=83
/dev/mmcblk0p16: start= 1067840, size= 3940352, Id=83
/dev/mmcblk0p17: start= 5008256, size= 10504192, Id=83
This output is useful for those have their partition table destroyed. I had to manually repartition my device.
Then, using dd, I dumped every partition of /dev/block/mmcblk0 and renamed they to match. Finally I packed the file.
In the pit file you linked to, there is a reference to a inand_8G.bin file how would you go about IDing that file and extracting it and of the partitions you listed above which one holds the inand_8G.bin file.
ishish9 said:
In the pit file you linked to, there is a reference to a inand_8G.bin file how would you go about IDing that file and extracting it and of the partitions you listed above which one holds the inand_8G.bin file.
Click to expand...
Click to collapse
In fact, no partition holds inand_8G.bin. Look at heimdall PIT output:
Code:
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Entry Count: 14
Unknown 1: 15718400
Unknown 2: 1
Unknown 3: 0
Unknown 4: 0
Unknown 5: 7703
Unknown 6: 237
Unknown 7: 62704
Unknown 8: 18
--- Entry #0 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 1
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1
Unknown 2: 0
Unknown 3: 0
Partition Name: IBL+PBL
Filename: boot.bin
--- Entry #1 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 2
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1
Unknown 2: 0
Unknown 3: 0
Partition Name: PIT
Filename: YPG70_8G-0304.pit
--- Entry #2 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 3
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 5
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL
Filename: Sbl.bin
--- Entry #3 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 4
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 5
Unknown 2: 6226025
Unknown 3: 7143533
Partition Name: SBL2
Filename: Sbl.bin
--- Entry #4 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 5
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 20
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs
--- Entry #5 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 6
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 40
Unknown 2: 39021280
Unknown 3: 7143533
Partition Name: EFS
Filename: efs.rfs
--- Entry #6 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 30
Unknown 2: 36662408
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage
--- Entry #7 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 8
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 30
Unknown 2: 6684793
Unknown 3: 3014771
Partition Name: RECOVERY
Filename: zImage
--- Entry #8 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 9
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1160
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.rfs
--- Entry #9 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 10
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 536
Unknown 2: 6684780
Unknown 3: 115
Partition Name: DBDATAFS
Filename: dbdata.rfs
--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 11
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 256
Unknown 2: 115
Unknown 3: 115
Partition Name: CACHE
Filename: cache.rfs
--- Entry #11 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 12
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 7696
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: datafs.rfs
--- Entry #12 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 13
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 20516
Unknown 2: 0
Unknown 3: 0
Partition Name: USERFS
Filename: userfs_8G.rfs
--- Entry #13 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 0
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: GANG
Filename: inand_8G.bin
In the partition table I posted earlier, last partition is mmcblk0p17, which contains datafs.rfs. I think that reference is only to show that the PIT file is for 8G. The inand_8G.bin's partition size is 0 bytes.
I know it shows up there as having no information but I have a file from a GANG partition that does have information in it, about 100 Megabytes, now that maybe simply place holder information but it is a partition and it may contain some information how ever little it may actually be. Also looking at the file I got from a GANG partition in a Hex editor the first words that appear are "FATHEAD" this link here has some information about it.
ishish9 said:
I know it shows up there as having no information but I have a file from a GANG partition that does have information in it, about 100 Megabytes, now that maybe simply place holder information but it is a partition and it may contain some information how ever little it may actually be. Also looking at the file I got from a GANG partition in a Hex editor the first words that appear are "FATHEAD" this link here has some information about it.
Click to expand...
Click to collapse
I'll look into it.
When I recovered my galaxy player I did a full dd dump of the mmcblk0 contents. I know it's "hacky", but it worked.
Is there any way you could post the ROM again as it is no longer available via your link.
My YP-G70 turned to a black screen after running google play movies. And since the battery cannot be easilly pulled I feel a flash is in order
Update:
Nevermind I found that I can pull the battery so I just did
Could some one be so kind to repost til full recovery file please.
Update: used this http://forum.xda-developers.com/showpost.php?p=19840746&postcount=420
And som grat help from rumirand, and my player int. is running again.
ident
I've not bricked my device. I'm using Erygit Custom-Rom V3.0 and rj kernel ( I downgraded from PA).
I just want to go back to original factory setting, can I use your ROM and just use it with Odin, without using the PIT file as my device is not bricked.
jamaljan said:
I've not bricked my device. I'm using Erygit Custom-Rom V3.0 and rj kernel ( I downgraded from PA).
I just want to go back to original factory setting, can I use your ROM and just use it with Odin, without using the PIT file as my device is not bricked.
Click to expand...
Click to collapse
XXKPL is much newer, and the available Odin package for it will do exactly what you want.
Mevordel said:
XXKPL is much newer, and the available Odin package for it will do exactly what you want.
Click to expand...
Click to collapse
thanks. is this what you are referring to ?
http://androidromupdate.com/2012/05...-g70-international-to-android-2-3-6-firmware/
jamaljan said:
thanks. is this what you are referring to ?
http://androidromupdate.com/2012/05...-g70-international-to-android-2-3-6-firmware/
Click to expand...
Click to collapse
That looks like the right thing, yes.

Stock Recovery Img from Azpen A729

Hi,
I managed to extract the original Recovery Img from my Azpen A729.
I used the following command:
su
busybox dd if=/dev/block/by-name/recovery of=/sdcard/recovery-backup.img bs=1M
Click to expand...
Click to collapse
The output file is currently 32MB in size. I think it's too big. Is this correct?
This tablet is a dual-core AllWinner A23, 1024x600, 160dpi, KitKat 4.4.2
Any help or comments would be greatly appreciated.
Info so far. ..
Code:
#cat /proc/cmdline:
console=ttyS0,115200 rw init=/init loglevel=4 boot_type=0
partitions=
[email protected]:
[email protected]:
[email protected]:
[email protected]:
[email protected]:
[email protected]:
[email protected]:
[email protected]:
[email protected]:
[email protected]:
[email protected]
Code:
#cat /proc/partitions:
major minor #blocks name
93 0 32768 nanda (bootloader 32MB)
93 8 16384 nandb (env 16MB)
93 16 16384 nandc (boot 16MB)
93 24 786432 nandd (/system 768MB)
93 32 2113536 nande (/data 2.1 GB)
93 40 16384 nandf (misc 16MB)
93 48 32768 nandg (Recovery.32MB)
93 56 524288 nandh (/cache 512MB)
93 64 131072 nandi (databk 128MB)
93 72 16384 nandj (/private 16MB)
93 80 3588096 nandk (/sdcard 3.6GB)
Code:
#lsmod
rtl8150 8115 0 - Live 0x00000000
mcs7830 4948 0 - Live 0x00000000
qf9700 5188 0 - Live 0x00000000
asix 12322 0 - Live 0x00000000
bma250 6339 0 - Live 0x00000000
sunxi_keyboard 2749 0 - Live 0x00000000
gslX680 254201 0 - Live 0x00000000
gslX680new 2876671 0 - Live 0x00000000 (F)
ft5402 84477 0 - Live 0x00000000
ft5x_ts 65070 0 - Live 0x00000000
inet_ctp 1981 4 gslX680,gslX680new,ft5402,ft5x_ts, Live 0x00000000
vfe_v4l2 219284 0 - Live 0x00000000
gc0308 9436 1 - Live 0x00000000
gc2035 10898 1 - Live 0x00000000
vfe_subdev 3827 3 vfe_v4l2,gc0308,gc2035, Live 0x00000000
vfe_os 3175 2 vfe_v4l2,vfe_subdev, Live 0x00000000
cci 2954 2 gc0308,gc2035, Live 0x00000000
cam_detect 46376 1 vfe_v4l2, Live 0x00000000
videobuf_dma_contig 3821 1 vfe_v4l2, Live 0x00000000
videobuf_core 15500 2 vfe_v4l2,videobuf_dma_contig, Live 0x00000000
mali 175001 5 - Live 0x00000000 (O)
lcd 14181 0 - Live 0x00000000
disp 1045429 6 mali,lcd, Live 0x00000000
nand 269898 8 - Live 0x00000000 (O)
recovery?
how do you boot into recovery mode on this device i've tried vol - and pwr button but it doesn't work

Help to upgrade my device to kitkat from jellybean Micromax A77

hello guyz i have micromax a77 device recently i found that fly iq4404 is my partial clone device all are same expect lcm and touch driver that device got kitkat with help of russian developers here is my all device properties
anyone help me to compile kernel with this drivers ?
my device properties found out by device info app given by russian guy
i am not a pro devloper just want someone to help me i m not a noob also so please if any one willing to help can comment down ?
LCM:
console=ttyMT1,921600n1 vmalloc=500M slub_max_order=0 lcm=1-otm8018b_dsi_vdo_fwvga_txd_a1005 fps=5049 pl_t=1060 lk_t=2154 printk.disable_uart=1 boot_reason=4
TPD:
0x01:139:80:825:160:50:0x01:172:240:825:160:50:0x01:158:400:825:160:50
I2C:
AP3216C
BMA220
dummy
dummy_cam_cal
dummy_eeprom
kd_camera_hw
msg2133
VERSION:
Linux version 3.4.5 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Wed Oct 16 21:57:44 CST 2013
PVRVersion:
INTERRUPTS:
CPU0 CPU1
14: 11318 0 - debug-signal
29: 4666213 3040132 - timer
52: 0 0 - mt_usb
57: 0 0 - mtk-thermal
58: 645621 0 - mtk-msdc
59: 84596 0 - mtk-msdc
60: 437 0 - mt-i2c.0
61: 718423 0 - mt-i2c.1
64: 0 0 - mtk-uart
69: 0 0 - mt-i2c.0
71: 0 0 - mt-i2c.1
73: 20888 0 - mtk btif tx dma irq
74: 29319 0 - mtk btif rx dma irq
81: 0 0 - mt-spi.0
84: 0 0 - mtk btif irq
90: 0 0 - mt_emi_mpu, mt6572_devapc
96: 113268 0 - Afe_ISR_Handle
97: 0 0 - M4U_device
100: 0 0 - AHB_ABT
104: 0 0 - mt-spm
106: 12 0 - mt6572-gpt
107: 21325 0 - CCIF
108: 227755 0 - EINT
120: 0 0 - pmic_wrap
121: 42 0 - mtk-kpd
124: 408050 0 - mtk_disp
131: 0 0 - mtk_disp
132: 2489441 0 - mtk_disp
134: 894467 0 - mtk_disp
135: 1237868 0 - mtk_disp
136: 37117 0 - mtkfb
139: 0 0 - MAU0
140: 32 0 - mtk_disp
142: 51612 0 - Vcodec
143: 0 0 - Vcodec
144: 107 0 - isp
146: 706203 0 - mali_gp_irq_handlers
147: 0 0 - mali_mmu_irq_handlers
148: 703579 0 - mali_pp_irq_handlers
149: 0 0 - mali_mmu_irq_handlers
152: 0 0 - MD-WDT
153: 0 0 - BTCVSD_ISR_Handle
154: 156 0 - BTIF_WAKEUP_IRQ
155: 693748 0 - AHB_SLAVE_HIF
FIQ: fiq_glue
IPI0: 0 0 Timer broadcast interrupts
IPI1: 7549993 9760317 Rescheduling interrupts
IPI2: 0 0 Function call interrupts
IPI3: 37112 39285 Single function call interrupts
IPI4: 0 0 CPU stop interrupts
IPI5: 0 0 CPU backtrace
Err: 0
PARTITIONS:
major minor #blocks name
7 0 1254 loop0
7 1 33280 loop1
7 2 31201 loop2
7 3 35359 loop3
179 0 3763200 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 1048576 mmcblk0p4
179 5 307200 mmcblk0p5
179 6 2097152 mmcblk0p6
179 7 253696 mmcblk0p7
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 15601664 mmcblk1
179 97 15600640 mmcblk1p1
254 0 33280 dm-0
254 1 31201 dm-1
254 2 35359 dm-2
CPUINFO:
Processor: ARMv7 Processor rev 3 (v7l)
processor: 0
BogoMIPS: 1993.93
processor: 1
BogoMIPS: 1993.93
Features: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt
CPU implementer: 0x41
CPU architecture: 7
CPU variant: 0x0
CPU part: 0xc07
CPU revision: 3
Hardware: MT6572
Revision: 0000
Serial: 0000000000000000
INPUT:
I: Bus=0019 Vendor=2454 Product=6572 Version=0010
N: Name="mtk-kpd"
P: Phys=
S: Sysfs=/devices/platform/mtk-kpd/input/input0
U: Uniq=
H: Handlers=event0
B: PROP=0
B: EV=3
B: KEY=180 180000 0 40000800 1c1ec0 0 0 0
I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="ACCDET"
P: Phys=
S: Sysfs=/devices/virtual/input/input1
U: Uniq=
H: Handlers=event1
B: PROP=0
B: EV=3
B: KEY=80 0 78 0 40c0000 0 0 0
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="hwmdata"
P: Phys=
S: Sysfs=/devices/virtual/input/input2
U: Uniq=
H: Handlers=event2
B: PROP=0
B: EV=5
B: REL=2
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="mtk-tpd"
P: Phys=
S: Sysfs=/devices/virtual/input/input3
U: Uniq=
H: Handlers=mouse0 event3
B: PROP=2
B: EV=b
B: KEY=400 0 0 0 0 1000 40000800 0 0 0 0
B: ABS=2630000 1000003
I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="mtk-tpd-kpd"
P: Phys=
S: Sysfs=/devices/virtual/input/input4
U: Uniq=
H: Handlers=event4
B: PROP=0
B: EV=3
B: KEY=1000 40000800 0 0 0 0
EMMC:
partno: start_sect nr_sects partition_name
emmc_p1: 00000400 00000002 "ebr1"
emmc_p2: 00004800 00005000 "protect_f"
emmc_p3: 00009800 00005000 "protect_s"
emmc_p4: 0001ba00 00200000 "android"
emmc_p5: 0021ba00 00096000 "cache"
emmc_p6: 002b1a00 00400000 "usrdata"
emmc_p7: 006b1a00 0007be00 "fat"
on the basis of this please help me to compile this source it had booted on my device after i lock it and unlock again white screen come and touch is not working
i know its touch driver and lcm driver problem help me to fix it
source link :- https://github.com/rex-xxx/KK_kernel_iq4404_MT6572

[REF] LEX720 - 64GB - Partition infos

Hi!
As I haven't found this infos online yet, I decided to post this information for reference (maybe it might be useful for someone in the future).
I grabbed this data from a LEX720 (LeEco Le Pro 3, chinese version, dual-sim) with 6GB RAM and 64GB storage while running TWRP recovery.
At the time of the dump on the device the original (chinese/english) 5.8.017S (ro.build.fingerprint: "LeEco/ZL1_CN/le_zl1:6.0.1/WAXCNFN5801709271S/letv09271704:user/release-keys") firmware was installed.
(I attached the full output of "fdisk -l" with all partition details - including start and end sectors - also as a text file.)
Code:
#
# Dumped from LEX720, with 64GB storage:
#
Device Name Size Part Name Mounted Flashed_from
--- /dev/block/sda: ------------------------------------------------------------
/dev/block/sda1 8192 ssd
/dev/block/sda2 32.0M persist /persist/
/dev/block/sda3 256M cache /cache/
/dev/block/sda4 1024K misc
/dev/block/sda5 512K keystore
/dev/block/sda6 128K devcfg devcfg.mbn
/dev/block/sda7 128K devcfgbak
/dev/block/sda8 512K frp
/dev/block/sda9 4096K ramdump
/dev/block/sda10 54.1G userdata /data/
--- /dev/block/sdb: ------------------------------------------------------------
/dev/block/sdb1 4052K xbl xbl.elf
--- /dev/block/sdc: ------------------------------------------------------------
/dev/block/sdc1 4052K xblbak xbl.elf
--- /dev/block/sdd: ------------------------------------------------------------
/dev/block/sdd1 32768 reserve
/dev/block/sdd2 4096 cdt
/dev/block/sdd3 1024K ddr ddr.mbn
--- /dev/block/sde: ------------------------------------------------------------
/dev/block/sde1 512K rpm rpm.mbn
/dev/block/sde2 512K rpmbak rpm.mbn
/dev/block/sde3 2048K tz tz.mbn
/dev/block/sde4 2048K tzbak tz.mbn
/dev/block/sde5 512K hyp hyp.mbn
/dev/block/sde6 512K hypbak hyp.mbn
/dev/block/sde7 2048K fsg
/dev/block/sde8 1024K fsg_gap
/dev/block/sde9 16384 sec
/dev/block/sde10 512K pmic pmic.elf
/dev/block/sde11 512K pmicbak pmic.elf
/dev/block/sde12 110M modem /firmware/ NON-HLOS.bin
/dev/block/sde13 16.0M dsp /dsp/ adspso.bin
/dev/block/sde14 1024K dip
/dev/block/sde15 32.0M mdtp
/dev/block/sde16 1024K aboot emmc_appsboot.mbn
/dev/block/sde17 1024K abootbak emmc_appsboot.mbn
/dev/block/sde18 64.0M boot boot.img
/dev/block/sde19 4096M system /system/ system.* (several files)
/dev/block/sde20 64.0M recovery
/dev/block/sde21 4096 devinfo devinfo.bin
/dev/block/sde22 1024K bluetooth /bt_firmware/ BTFM.bin
/dev/block/sde23 512K keymaster keymaster.mbn
/dev/block/sde24 512K keymasterbak keymaster.mbn
/dev/block/sde25 256K cmnlib cmnlib.mbn
/dev/block/sde26 256K cmnlibbak cmnlib.mbn
/dev/block/sde27 256K cmnlib64 cmnlib64.mbn
/dev/block/sde28 256K cmnlib64bak cmnlib64.mbn
/dev/block/sde29 256K apdp
/dev/block/sde30 256K msadp
/dev/block/sde31 4096 dpo
/dev/block/sde32 100M splash splash.img
/dev/block/sde33 2048K sti
--- /dev/block/sdf: ------------------------------------------------------------
/dev/block/sdf1 2048K modemst1
/dev/block/sdf2 1024K modemst1_gap
/dev/block/sdf3 2048K modemst2
/dev/block/sdf4 1024K modemst2_gap
/dev/block/sdf5 4096 fsc
/dev/block/sdf6 4096 factory
/dev/block/sdf7 4096 bootconfig
/dev/block/sdf8 4096 rootconfig
/dev/block/sdf9 4096 recoveryconfig
/dev/block/sdf10 512K letvconfig
/dev/block/sdf11 512K letveui
/dev/block/sdf12 512K letvsecure
/dev/block/sdf13 512K letvreserve
/dev/block/sdf14 10.0M kernellog
At normal system runtime the mountpoints look like this:
Code:
rootfs / rootfs ro,seclabel,size=2843628k,nr_inodes=710907 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=2940160k,nr_inodes=735040,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,seclabel,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=2940160k,nr_inodes=735040,mode=750,gid=1000 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,size=2940160k,nr_inodes=735040,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/bootdevice/by-name/system /system ext4 ro,seclabel,relatime,discard,data=ordered 0 0
/dev/block/bootdevice/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/dsp /dsp ext4 ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/modem /firmware vfat ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/bootdevice/by-name/bluetooth /bt_firmware vfat ro,context=u:object_r:bt_firmware_file:s0,relatime,uid=1002,gid=3002,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,size=2940160k,nr_inodes=735040,mode=755,gid=1000 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
I also dumped all partitions except the large ones (system, userdata, recovery) using "dd" (from within TWRP recovery) and did a first very simple content check by using the Linux "file" command:
Code:
[email protected] ~/D/_/A/L/0/dumps> file *
aboot: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, stripped
abootbak: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, stripped
apdp: ELF 32-bit LSB no file type, ARM, version 1 (SYSV)
bluetooth: x86 boot sector, code offset 0x3c, OEM-ID "MSDOS5.0", Bytes/sector 4096, sectors/cluster 4, root entries 512, Media descriptor 0xf8, sectors/FAT 33, heads 255, sectors 262144 (volumes > 32 MB) , serial number 0xbc614e, unlabeled, FAT (16 bit)
boot: data
bootconfig: data
cdt: data
cmnlib: ELF 32-bit LSB shared object, ARM, version 1 (SYSV), statically linked, stripped
cmnlib64: ELF 64-bit LSB shared object, version 1 (SYSV), statically linked, stripped
cmnlib64bak: ELF 64-bit LSB shared object, version 1 (SYSV), statically linked, stripped
cmnlibbak: ELF 32-bit LSB shared object, ARM, version 1 (SYSV), statically linked, stripped
ddr: data
devcfg: ELF 64-bit LSB executable, version 1 (SYSV), statically linked, stripped
devcfgbak: ELF 64-bit LSB executable, version 1 (SYSV), statically linked, stripped
devinfo: ASCII text, with no line terminators
dip: data
dpo: data
dsp: Linux rev 1.0 ext4 filesystem data (extents) (large files)
factory: data
frp: data
fsc: data
fsg: data
fsg_gap: data
hyp: ELF 64-bit LSB executable, version 1 (SYSV), statically linked, stripped
hypbak: ELF 64-bit LSB executable, version 1 (SYSV), statically linked, stripped
kernellog: data
keymaster: ELF 32-bit LSB shared object, ARM, version 1 (SYSV), statically linked, stripped
keymasterbak: ELF 32-bit LSB shared object, ARM, version 1 (SYSV), statically linked, stripped
keystore: data
letvconfig: ASCII text, with no line terminators
letveui: data
letvreserve: data
letvsecure: data
mdtp: data
misc: data
modem: x86 boot sector, code offset 0x3c, OEM-ID "MSDOS5.0", Bytes/sector 4096, sectors/cluster 4, root entries 512, Media descriptor 0xf8, sectors/FAT 4, heads 255, sectors 28160 (volumes > 32 MB) , serial number 0xbc614e, unlabeled, FAT (16 bit)
modemst1: data
modemst1_gap: data
modemst2: data
modemst2_gap: data
msadp: ELF 32-bit LSB no file type, ARM, version 1 (SYSV)
persist: Linux rev 1.0 ext4 filesystem data (extents) (large files)
pmic: ELF 64-bit LSB executable, version 1 (SYSV), statically linked, corrupted section header size
pmicbak: ELF 64-bit LSB executable, version 1 (SYSV), statically linked, corrupted section header size
ramdump: data
recovery: data
recoveryconfig: data
reserve: data
rootconfig: data
rpm: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, stripped
rpmbak: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, stripped
sec: data
splash: data
ssd: data
sti: data
tz: ELF 64-bit LSB executable, version 1 (SYSV), statically linked, stripped
tzbak: ELF 64-bit LSB executable, version 1 (SYSV), statically linked, stripped
xbl: ELF 64-bit LSB executable, version 1 (SYSV), statically linked, corrupted section header size
xblbak: ELF 64-bit LSB executable, version 1 (SYSV), statically linked, corrupted section header size
Also, the device can be easily brought into the "Qualcomm HS-USB QDLoader 9008" download mode via adb:
Code:
adb reboot edl
The phone will then show up as "Qualcomm HS-USB QDLoader 9008" in the device manager (if the Qualcomm drivers are installed) and the phone itself will stay totally dark (but running). To leave the Qualcomm download mode simply press the power button for around 10secs (until the device vibrates and reboots).
I personally don't have any experience yet with the Qualcomm Download mode, but this mode should allow a very low-level re-flash ("unbrick") of the device if for some reason the secondary bootloader (SBL) gets destroyed, but only if we have the correct files to flash in this mode!
(Here an unrelated blog post with some general infos about this qualcomm mode: http://www.androidbrick.com/ultimat...agons-are-unbrickable-qhsusb_dload_qpst_qfil/)
If somebody has any more knowledge in this area (i.e. how-to dump the needed files for a low-level SBL restore in the format as they are needed for the Qualcomm tools) then we might be able to unbrick devices in future (and help people like @amdtip who cannot boot anymore into fastboot or recovery).
john
androcheck said:
Also, the device can be easily brought into the "Qualcomm HS-USB QDLoader 9008" download mode via adb:
The phone will then show up as "Qualcomm HS-USB QDLoader 9008" in the device manager (if the Qualcomm drivers are installed) and the phone itself will stay totally dark (but running). To leave the Qualcomm download mode simply press the power button for around 10secs (until the device vibrates and reboots).
I personally don't have any experience yet with the Qualcomm Download mode, but this mode should allow a very low-level re-flash ("unbrick") of the device if for some reason the secondary bootloader (SBL) gets destroyed, but only if we have the correct files to flash in this mode!
(Here an unrelated blog post with some general infos about this qualcomm mode: http://www.androidbrick.com/ultimat...gons-are-unbrickable-qhsusb_dload_qpst_qfil/)
If somebody has any more knowledge in this area (i.e. how-to dump the needed files for a low-level SBL restore in the format as they are needed for the Qualcomm tools) then we might be able to unbrick devices in future (and help people like @amdtip who cannot boot anymore into fastboot or recovery).
john
Click to expand...
Click to collapse
Yeah I reckon they is how they made all the Qualcomm Recovery Tools for the OnePlus as they are a godsend.
@androcheck can you please post cat /proc/partitions aswell ?
thank you
darkobas said:
@androcheck can you please post cat /proc/partitions aswell ?
Click to expand...
Click to collapse
Sure:
Code:
[email protected]_zl1:/ $ cat /proc/partitions
major minor #blocks name
8 0 57073664 sda
8 1 8 sda1
8 2 32768 sda2
8 3 262144 sda3
8 4 1024 sda4
8 5 512 sda5
8 6 128 sda6
8 7 128 sda7
8 8 512 sda8
8 9 4096 sda9
8 10 56772300 sda10
8 64 5242880 sde
8 65 512 sde1
8 66 512 sde2
8 67 2048 sde3
8 68 2048 sde4
8 69 512 sde5
8 70 512 sde6
8 71 2048 sde7
8 72 1024 sde8
8 73 16 sde9
8 74 512 sde10
8 75 512 sde11
8 76 112640 sde12
8 77 16384 sde13
8 78 1024 sde14
8 79 32768 sde15
259 0 1024 sde16
259 1 1024 sde17
259 2 65536 sde18
259 3 4194304 sde19
259 4 65536 sde20
259 5 4 sde21
259 6 1024 sde22
259 7 512 sde23
259 8 512 sde24
259 9 256 sde25
259 10 256 sde26
259 11 256 sde27
259 12 256 sde28
259 13 256 sde29
259 14 256 sde30
259 15 4 sde31
259 16 102400 sde32
259 17 2048 sde33
8 80 32768 sdf
8 81 2048 sdf1
8 82 1024 sdf2
8 83 2048 sdf3
8 84 1024 sdf4
8 85 4 sdf5
8 86 4 sdf6
8 87 4 sdf7
8 88 4 sdf8
8 89 4 sdf9
8 90 512 sdf10
8 91 512 sdf11
8 92 512 sdf12
8 93 512 sdf13
8 94 10240 sdf14
8 48 131072 sdd
8 49 32 sdd1
8 50 4 sdd2
8 51 1024 sdd3
8 16 4096 sdb
8 17 4052 sdb1
8 32 4096 sdc
8 33 4052 sdc1

Categories

Resources