Android ROM包的常见结构有没有一些资料描述?

最大的社区版本,Ubuntu的发源地
回复
科学之子
帖子: 2284
注册时间: 2013-05-26 6:58
系统: Debian 9

Android ROM包的常见结构有没有一些资料描述?

#1

帖子 科学之子 » 2017-10-23 16:44

Android ROM包的常见结构有没有一些资料描述?
像各个文件的作用,内容格式等等之类
用sdat2img解不开
mount也解不开

代码: 全选

$ ./sdat2img.py system.transfer.list system.new.dat system.img
sdat2img binary - version: 1.0

Command "move" is not valid.
难道因为是升级包,所以rom包不完整,无法提取?

代码: 全选

$ 7z l ./bbkupdate_4018437.zip 

7-Zip [32] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,32 bits,2 CPUs Pentium(R) Dual-Core  CPU      E5500  @ 2.80GHz (1067A),ASM)

Scanning the drive for archives:
1 file, 203547382 bytes (195 MiB)

Listing archive: ./bbkupdate_4018437.zip

--
Path = ./bbkupdate_4018437.zip
Type = zip
Physical Size = 203547382
Comment = signed by SignApk@loki

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2009-01-01 00:00:00 .....     10415482     10414847  patch/boot.img.p
2009-01-01 00:00:00 .....      1432319      1432025  patch/xbl.elf.p
2009-01-01 00:00:00 .....       357392       169176  keymaster.mbn
2009-01-01 00:00:00 .....       218088       127289  cmnlib.mbn
2009-01-01 00:00:00 .....       266240        96311  hyp.mbn
2009-01-01 00:00:00 .....        49068        14380  devcfg.mbn
2009-01-01 00:00:00 .....      1953792       523821  tz.mbn
2009-01-01 00:00:00 .....       503808       239026  BTFM.bin
2009-01-01 00:00:00 .....     14599670     14600541  patch/NON-HLOS.bin.p
2009-01-01 00:00:00 .....       270008       151177  cmnlib64.mbn
2009-01-01 00:00:00 .....       224808       118922  rpm.mbn
2009-01-01 00:00:00 .....     16777216      4398648  dspso.bin
2009-01-01 00:00:00 .....        39736        13496  pmic.elf
2009-01-01 00:00:00 .....        65576        65544  patch/abl.elf.p
2009-01-01 00:00:00 .....         2254          802  OEM_PD1709_CMCC_RWB.transfer.list
2009-01-01 00:00:00 .....         4096          130  OEM_PD1709_CMCC_RWB.new.dat
2009-01-01 00:00:00 .....         1997         1997  OEM_PD1709_CMCC_RWB.patch.dat
2009-01-01 00:00:00 .....         2203          784  OEM_PD1709_CN-YD-A.transfer.list
2009-01-01 00:00:00 .....         4096          130  OEM_PD1709_CN-YD-A.new.dat
2009-01-01 00:00:00 .....         2015         2015  OEM_PD1709_CN-YD-A.patch.dat
2009-01-01 00:00:00 .....         2254          800  OEM_PD1709_CN-YD-B.transfer.list
2009-01-01 00:00:00 .....         4096          130  OEM_PD1709_CN-YD-B.new.dat
2009-01-01 00:00:00 .....         2001         2001  OEM_PD1709_CN-YD-B.patch.dat
2009-01-01 00:00:00 .....         2203          783  OEM_PD1709_CN-YD.transfer.list
2009-01-01 00:00:00 .....         4096          130  OEM_PD1709_CN-YD.new.dat
2009-01-01 00:00:00 .....         1980         1980  OEM_PD1709_CN-YD.patch.dat
2009-01-01 00:00:00 .....         2204          781  OEM_PD1709_CTCC_RWC.transfer.list
2009-01-01 00:00:00 .....         4096          130  OEM_PD1709_CTCC_RWC.new.dat
2009-01-01 00:00:00 .....         1994         1994  OEM_PD1709_CTCC_RWC.patch.dat
2009-01-01 00:00:00 .....         2254          799  OEM_PD1709_FULL_SC.transfer.list
2009-01-01 00:00:00 .....         4096          130  OEM_PD1709_FULL_SC.new.dat
2009-01-01 00:00:00 .....         1984         1984  OEM_PD1709_FULL_SC.patch.dat
2009-01-01 00:00:00 .....         2253          798  OEM_PD1709_FULL_UNICOM_RWA.transfer.list
2009-01-01 00:00:00 .....         4096          130  OEM_PD1709_FULL_UNICOM_RWA.new.dat
2009-01-01 00:00:00 .....         2003         2003  OEM_PD1709_FULL_UNICOM_RWA.patch.dat
2009-01-01 00:00:00 .....         2024          738  OEM_PD1709_GMS.transfer.list
2009-01-01 00:00:00 .....         4096          129  OEM_PD1709_GMS.new.dat
2009-01-01 00:00:00 .....         2000         2000  OEM_PD1709_GMS.patch.dat
2009-01-01 00:00:00 .....       967417       376154  system.transfer.list
2009-01-01 00:00:00 .....       967463       376161  system.transfer.list.origin
2009-01-01 00:00:00 .....       495616       229191  system.new.dat
2009-01-01 00:00:00 .....    169199457    169199457  system.patch.dat
2009-01-01 00:00:00 .....       230586        27627  file_contexts.bin
2009-01-01 00:00:00 .....       250361        77737  META-INF/com/google/android/updater-script
2009-01-01 00:00:00 .....      1536392       859734  META-INF/com/google/android/update-binary
2009-01-01 00:00:00 .....          358          201  META-INF/com/android/metadata
2009-01-01 00:00:00 .....         1367          983  META-INF/com/android/otacert
2009-01-01 00:00:00 .....         3646         1386  META-INF/MANIFEST.MF
2009-01-01 00:00:00 .....         4070         1529  META-INF/CERT.SF
2009-01-01 00:00:00 .....         1459         1125  META-INF/CERT.RSA
------------------- ----- ------------ ------------  ------------------------
2009-01-01 00:00:00          220897786    203539786  50 files
头像
astolia
论坛版主
帖子: 6396
注册时间: 2008-09-18 13:11

Re: Android ROM包的常见结构有没有一些资料描述?

#2

帖子 astolia » 2017-10-23 20:07

增量包肯定不会是完整文件系统。用hd之类的看它前几个字节是什么,估计是bsdiff或者imgdiff2一类的
科学之子
帖子: 2284
注册时间: 2013-05-26 6:58
系统: Debian 9

Re: Android ROM包的常见结构有没有一些资料描述?

#3

帖子 科学之子 » 2017-10-24 1:57

astolia 写了:增量包肯定不会是完整文件系统。用hd之类的看它前几个字节是什么,估计是bsdiff或者imgdiff2一类的
那是否有可能通过增量包来上传su之类的程序实现root或其它类似的特殊目的呢?
从我的水平来看完全没有头绪,虽然貌似,可能,也许,理论上存在可能性.
不知实践中可能性如何或如何操作.
头像
astolia
论坛版主
帖子: 6396
注册时间: 2008-09-18 13:11

Re: Android ROM包的常见结构有没有一些资料描述?

#4

帖子 astolia » 2017-10-24 8:07

META-INF下的数字签名文件就是防止你干这种事的。除非你手机bootloader允许刷入可以不验证签名的第三方recovery程序,否则签名是绕不过的,走这条路root就别想了
回复