Hallo all, I need help! Anyone want to send me log after adb shell command
Code:
ls /dev/oncrpc
Thanks!
Code:
crw-rw---- 1 0 1000 253, 0 Jun 8 12:19 00000000:0
crw-rw---- 1 0 1000 253, 9 Jun 8 12:19 30000000:e9fb8210
crw-rw---- 1 0 1000 253, 8 Jun 8 12:19 30000002:00020002
crw-rw---- 1 0 1000 253, 4 Jun 8 12:19 30000003:f94d6efb
crw-rw---- 1 0 1000 253, 25 Jun 8 12:19 3000000a:00010001
crw-rw---- 1 0 1000 253, 23 Jun 8 12:19 3000000e:00020001
crw-rw---- 1 0 1000 253, 19 Jun 8 12:19 30000012:00010001
crw-rw---- 1 0 1000 253, 18 Jun 8 12:19 30000013:00020002
crw-rw---- 1 0 1000 253, 17 Jun 8 12:19 30000014:00020001
crw-rw---- 1 0 1000 253, 15 Jun 8 12:19 30000016:d6bb93e6
crw-rw---- 1 0 1000 253, 14 Jun 8 12:19 30000019:821a1945
crw-rw---- 1 0 1000 253, 13 Jun 8 12:19 3000001b:90258183
crw-rw---- 1 0 1000 253, 10 Jun 8 12:19 3000001d:ba845703
crw-rw---- 1 0 1000 253, 12 Jun 8 12:19 3000003c:aa5a11fe
crw-rw---- 1 0 1000 253, 24 Jun 8 12:19 30000048:00010004
crw-rw---- 1 0 1000 253, 11 Jun 8 12:19 3000005b:a60286b0
crw-rw---- 1 0 1000 253, 7 Jun 8 12:19 3000005f:00010001
crw-rw---- 1 0 1000 253, 5 Jun 8 12:19 30000060:00010002
crw-rw---- 1 0 1000 253, 2 Jun 8 12:19 30000061:00010001
crw-rw---- 1 0 1000 253, 26 Jun 8 12:19 30000066:00010001
crw-rw---- 1 0 1000 253, 22 Jun 8 12:19 3000006b:00010001
crw-rw---- 1 0 1000 253, 1 Jun 8 12:19 30000081:00010002
crw-rw---- 1 0 1000 253, 21 Jun 8 12:19 3000008c:00020002
crw-rw---- 1 0 1000 253, 16 Jun 8 12:19 30000091:00010001
crw-rw---- 1 0 1000 253, 20 Jun 8 12:19 3000fe00:a82d4624
crw-rw---- 1 0 1000 253, 6 Jun 8 12:19 30100001:00000000
crw-rw---- 1 0 1000 253, 3 Jun 8 12:19 30100002:00000000
unlocking
Hi munjeni, can you unlock my htc Desire c, it is a seconde device i have to unlock
Code:
00000000:0
30000000:e9fb8210
30000002:00020002
30000003:f94d6efb
3000000a:00010001
3000000e:00020001
30000012:00010001
30000013:00020002
30000014:00020001
30000016:d6bb93e6
30000019:821a1945
3000001b:90258183
3000001d:ba845703
3000003c:aa5a11fe
30000048:00010004
3000005b:a60286b0
3000005f:00010001
30000060:00010002
30000061:00010001
30000066:00010001
3000006b:00010001
30000081:00010002
3000008c:00020002
30000091:00010001
3000fe00:a82d4624
30100001:00000000
30100002:00000000
Writing from Turkey. We've got a tablet brand Dark. The model EvoPAD 9740 has the Rockchip RK3188 chip in it. My intention is to put CM in it. Before I start building a custom rom from ground up I wanted to see if it is possible to build a rom by combining the image files from CM releases and manufacturer releases. The files and folders below are from the manufacturer image.
I used rpunkack to unpack r9740.img from akortek.org/download/evopad/R9740/R974031072013.rar
Here they are :
Code:
drwxr-xr-x 2 rhinestorm 4096 Oct 1 20:44 [backupimage]
-rw-r--r-- 1 rhinestorm 37228548 Oct 1 20:44 backup.img
drwxr-xr-x 2 rhinestorm 4096 Oct 1 20:44 [Image]
-rw-r--r-- 1 rhinestorm 1018399 Oct 1 20:44 boot.img
-rw-r--r-- 1 rhinestorm 1018387 Oct 1 20:44 boot.img-raw
-rw-r--r-- 1 rhinestorm 10985520 Oct 1 20:44 kernel.img
-rw-r--r-- 1 rhinestorm 10985508 Oct 1 20:44 kernel.img-raw
-rw-r--r-- 1 rhinestorm 49152 Oct 1 20:44 misc.img
-rw-r--r-- 1 rhinestorm 24969216 Oct 1 20:44 recovery.img
-rw-r--r-- 1 rhinestorm 510087168 Oct 1 20:44 system.img
-rw-r--r-- 1 rhinestorm 577 Oct 1 20:44 [COLOR="Red"]package-file[/COLOR]
-rw-r--r-- 1 rhinestorm 609 Oct 1 20:44 [COLOR="Red"]parameter[/COLOR]
-rw-r--r-- 1 rhinestorm 194926 Oct 1 20:43 r9740.img-BOOT
-rw-r--r-- 1 rhinestorm 102 Oct 1 20:43 r9740.img-HEAD
-rw-r--r-- 1 rhinestorm 32 Oct 1 20:44 r9740.img-MD5
-rw-r--r-- 1 rhinestorm 266 Oct 1 20:44 recover-script
-rw-r--r-- 1 rhinestorm 194926 Oct 1 20:44 RK3188Loader(L)_V1.24.bin
-rw-r--r-- 1 rhinestorm 584550404 Oct 1 20:43 update.img
-rw-r--r-- 1 rhinestorm 933 Oct 1 20:44 update-script
package-file
Code:
package-file package-file
bootloader RK3188Loader(L)_V1.24.bin
parameter parameter
misc Image/misc.img
kernel Image/kernel.img
boot Image/boot.img
recovery Image/recovery.img
system Image/system.img
backup backupimage/backup.img
update-script update-script
recover-script recover-script
parameters
Code:
FIRMWARE_VER:4.1.1
MACHINE_MODEL:EvoPAD R9740
MACHINE_ID:007
MANUFACTURER:RK30SDK
MAGIC: 0x5041524B
ATAG: 0x60000800
MACHINE: 3066
CHECK_MASK: 0x80
KERNEL_IMG: 0x60408000
#RECOVER_KEY: 1,1,0,20,0
CMDLINE:console=ttyFIQ0 androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:[email protected](misc),[email protected](kernel),[email protected](boot),[email protected](recovery),[email protected](backup),[email protected](cache),[email protected](userdata),[email protected](kpanic),[email protected](system),[email protected](user)
up!
Hi,
Was playing with ROMs and got my phone system destroyed in the process. Can still put the phone into the download and recovery modes. In the recovery mode twrp is working fine and I can still flash files in the download with fastboot. So I have a stock KDZ file and am looking to restore the phone into a working condition.
Since I'm on Linux, flashing KDZ files with standard LG tools is a problem as they don't work on Linux. So my plan was to flash relevant parts of the KDZ file on Linux using the following approach:
1. Extract KDZ file. See [*] below.
2. Combine all system_*******.bin fragments into a single system.bin file
3. fastboot flash system /path/to/system.bin
4. No point flashing recovery and boot since the phone still boots into recovery and twrp is working fine, right?
5. ...?
Any problems with the above plan? Suggestions? Thanks
[*]
Code:
[email protected]:~/extracted$ ls -l
total 6335492
-rw-r--r-- 1 luser luser 1048576 Jul 19 19:16 aboot_300032.bin
-rw-r--r-- 1 luser luser 1048576 Jul 19 19:16 abootbak_304128.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 apdp_1064960.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:17 BackupGPT_30784512.bin
-rw-r--r-- 1 luser luser 15728640 Jul 19 19:16 boot_442368.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 cmnlib_1084416.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 cmnlib64_1086464.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 cmnlib64bak_1087488.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 cmnlibbak_1085440.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 devcfg_1068032.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 devcfgbak_1069056.bin
-rw-r--r-- 1 luser luser 16777216 Jul 19 19:16 dsp_212992.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 factory_704512.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 keymaster_1088512.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 keymasterbak_1089536.bin
-rw-r--r-- 1 luser luser 18874368 Jul 19 19:16 laf_507904.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 lksecapp_1082368.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 lksecappbak_1083392.bin
-rw-r--r-- 1 luser luser 88080384 Jul 19 19:16 modem_16384.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 msadp_1065984.bin
-rw-r--r-- 1 luser luser 5242880 Jul 19 19:16 persist_786432.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 PrimaryGPT_0.bin
-rw-r--r-- 1 luser luser 1572864 Jul 19 19:16 raw_resources_770048.bin
-rw-r--r-- 1 luser luser 1572864 Jul 19 19:16 raw_resourcesbak_778240.bin
-rw-r--r-- 1 luser luser 17825792 Jul 19 19:16 recovery_573440.bin
-rw-r--r-- 1 luser luser 17825792 Jul 19 19:16 recoverybak_638976.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 rpm_202752.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 rpmbak_203776.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 sbl1_198656.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 sbl1bak_200704.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 sec_299008.bin
-rw-r--r-- 1 luser luser 134217728 Jul 19 19:16 system_1130496.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 system_1392640.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 system_1394312.bin
-rw-r--r-- 1 luser luser 131596288 Jul 19 19:16 system_1398416.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_1658888.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:17 system_1918600.bin
-rw-r--r-- 1 luser luser 131596288 Jul 19 19:17 system_1922704.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_2183176.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:17 system_2442888.bin
-rw-r--r-- 1 luser luser 131596288 Jul 19 19:17 system_2446992.bin
-rw-r--r-- 1 luser luser 5767168 Jul 19 19:17 system_2707464.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:17 system_2965504.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:17 system_2967176.bin
-rw-r--r-- 1 luser luser 131596288 Jul 19 19:17 system_2971280.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_3231752.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:17 system_3491464.bin
-rw-r--r-- 1 luser luser 131596288 Jul 19 19:17 system_3495568.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_3756040.bin
-rw-r--r-- 1 luser luser 1048576 Jul 19 19:17 system_4018184.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:17 system_4276224.bin
-rw-r--r-- 1 luser luser 39845888 Jul 19 19:17 system_4280328.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:17 system_4538368.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_4542472.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_4804616.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_5066760.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_5328904.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_5591048.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_5853192.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_6115336.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_6377480.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_6639624.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_6901768.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_7163912.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_7426056.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:17 system_7685768.bin
-rw-r--r-- 1 luser luser 177733632 Jul 19 19:17 system_7689216.bin
-rw-r--r-- 1 luser luser 3144155136 Jul 19 20:13 system.img
-rw-r--r-- 1 luser luser 1572864 Jul 19 19:16 tz_204800.bin
-rw-r--r-- 1 luser luser 1572864 Jul 19 19:16 tzbak_208896.bin
I have a device that uses UBIFS and I'm trying to increase the partition size of the /system disk as it doesn't have much space and only half of the NAND is partitioned. Unfortunately, it's not as simple as I thought as the entire nand chip doesn't populate in /dev as a single device.
Here's the boot log where MTD partitions are enumerated.
HTML:
[ 0.000000] Kernel command line: noinitrd rw console=ttyHSL0,115200,n8 androidboot.hardware=qcom ehci-hcd.park=3 msm_rtb.filter=0x37 lpm_levels.sleep_disabled=1 earlycon=msm_hsl_uart,0x78b1000 androidboot.serialno=796a00b0 androidboot.authorized_kernel=true androidboot.baseband=msm rootfstype=ubifs rootflags=bulk_read root=ubi0:rootfs ubi.mtd=13
Code:
[ 0.478465] sps: BAM device 0x07984000 is not registered yet.
[ 0.478706] sps:BAM 0x07984000 is registered.
[ 0.478723] msm_nand_bam_init: msm_nand_bam_init: BAM device registered: bam_handle 0xdde0c800
[ 0.478966] sps:BAM 0x07984000 (va:0xe0bc0000) enabled: ver:0x19, number of pipes:7
[ 0.481536] msm_nand_parse_smem_ptable: Parsing partition table info from SMEM
[ 0.481577] msm_nand_parse_smem_ptable: SMEM partition table found: ver: 4 len: 20
[ 0.481602] msm_nand_version_check: nand_major:1, nand_minor:5, qpic_major:1, qpic_minor:5
[ 0.481640] msm_nand_scan: NAND Id: 0x2690ac98 Buswidth: 8Bits Density: 512 MByte
[ 0.481649] msm_nand_scan: pagesize: 4096 Erasesize: 262144 oobsize: 256 (in Bytes)
[ 0.481656] msm_nand_scan: BCH ECC: 8 Bit
[ 0.481670] msm_nand_scan: CFG0: 0x290409c0, CFG1: 0x08045d5c
[ 0.481670] RAWCFG0: 0x2b8401c0, RAWCFG1: 0x0005055d
[ 0.481670] ECCBUFCFG: 0x00000203, ECCBCHCFG: 0x42040d10
[ 0.481670] RAWECCCFG: 0x42000d11, BAD BLOCK BYTE: 0x00000175
[ 0.481691] Creating 20 MTD partitions on "7980000.nand":
[ 0.481711] 0x000000000000-0x000000280000 : "sbl"
[ 0.482399] 0x000000280000-0x000000500000 : "mibib"
[ 0.482994] 0x000000500000-0x000001b80000 : "efs2"
[ 0.483584] 0x000001b80000-0x000001c80000 : "tz"
[ 0.484194] 0x000001c80000-0x000001d40000 : "rpm"
[ 0.484816] 0x000001d40000-0x000001e40000 : "aboot"
[ 0.485364] 0x000001e40000-0x000002880000 : "boot"
[ 0.485922] 0x000002880000-0x000002900000 : "scrub"
[ 0.486496] 0x000002900000-0x000006fc0000 : "modem"
[ 0.487080] 0x000006fc0000-0x000007140000 : "misc"
[ 0.487672] 0x000007140000-0x000007bc0000 : "recovery"
[ 0.488269] 0x000007bc0000-0x000007c80000 : "fota_none"
[ 0.488883] 0x000007c80000-0x000009340000 : "recoveryfs"
[ 0.489491] 0x000009340000-0x000011bc0000 : "system"
[ 0.490036] 0x000011bc0000-0x000012b40000 : "pad1"
[ 0.490729] 0x000012b40000-0x000013f80000 : "userrw"
[ 0.491301] 0x000013f80000-0x000017a40000 : "hdata"
[ 0.491890] 0x000017a40000-0x00001f000000 : "ntgfota"
[ 0.492500] 0x00001f000000-0x00001f8c0000 : "cust"
[ 0.493103] 0x00001f8c0000-0x000020000000 : "persist"
[ 0.493719] msm_nand_probe: NANDc phys addr 0x7980000, BAM phys addr 0x7984000, BAM IRQ 35
[ 0.493729] msm_nand_probe: Allocated DMA buffer at virt_addr 0xdf446000, phys_addr 0x9f446000
/dev
Code:
crw-rw---- 1 root root 90, 0 Jan 1 1970 mtd0
crw-rw---- 1 root root 90, 1 Jan 1 1970 mtd0ro
crw-rw---- 1 root root 90, 2 Jan 1 1970 mtd1
crw-rw---- 1 root root 90, 20 Jan 1 1970 mtd10
crw-rw---- 1 root root 90, 21 Jan 1 1970 mtd10ro
crw-rw---- 1 root root 90, 22 Jan 1 1970 mtd11
crw-rw---- 1 root root 90, 23 Jan 1 1970 mtd11ro
crw-rw---- 1 root root 90, 24 Jan 1 1970 mtd12
crw-rw---- 1 root root 90, 25 Jan 1 1970 mtd12ro
crw-rw---- 1 root root 90, 26 Jan 1 1970 mtd13
crw-rw---- 1 root root 90, 27 Jan 1 1970 mtd13ro
crw-rw---- 1 root root 90, 28 Jan 1 1970 mtd14
crw-rw---- 1 root root 90, 29 Jan 1 1970 mtd14ro
crw-rw---- 1 root root 90, 30 Jan 1 1970 mtd15
crw-rw---- 1 root root 90, 31 Jan 1 1970 mtd15ro
crw-rw---- 1 root root 90, 32 Jan 1 1970 mtd16
crw-rw---- 1 root root 90, 33 Jan 1 1970 mtd16ro
crw-rw---- 1 root root 90, 34 Jan 1 1970 mtd17
crw-rw---- 1 root root 90, 35 Jan 1 1970 mtd17ro
crw-rw---- 1 root root 90, 36 Jan 1 1970 mtd18
crw-rw---- 1 root root 90, 37 Jan 1 1970 mtd18ro
crw-rw---- 1 root root 90, 38 Jan 1 1970 mtd19
crw-rw---- 1 root root 90, 39 Jan 1 1970 mtd19ro
crw-rw---- 1 root root 90, 3 Jan 1 1970 mtd1ro
crw-rw---- 1 root root 90, 4 Jan 1 1970 mtd2
crw-rw---- 1 root root 90, 5 Jan 1 1970 mtd2ro
crw-rw---- 1 root root 90, 6 Jan 1 1970 mtd3
crw-rw---- 1 root root 90, 7 Jan 1 1970 mtd3ro
crw-rw---- 1 root root 90, 8 Jan 1 1970 mtd4
crw-rw---- 1 root root 90, 9 Jan 1 1970 mtd4ro
crw-rw---- 1 root root 90, 10 Jan 1 1970 mtd5
crw-rw---- 1 root root 90, 11 Jan 1 1970 mtd5ro
crw-rw---- 1 root root 90, 12 Jan 1 1970 mtd6
crw-rw---- 1 root root 90, 13 Jan 1 1970 mtd6ro
crw-rw---- 1 root root 90, 14 Jan 1 1970 mtd7
crw-rw---- 1 root root 90, 15 Jan 1 1970 mtd7ro
crw-rw---- 1 root root 90, 16 Jan 1 1970 mtd8
crw-rw---- 1 root root 90, 17 Jan 1 1970 mtd8ro
crw-rw---- 1 root root 90, 18 Jan 1 1970 mtd9
crw-rw---- 1 root root 90, 19 Jan 1 1970 mtd9ro
brw-rw---- 1 root root 31, 0 Jan 1 1970 mtdblock0
brw-rw---- 1 root root 31, 1 Jan 1 1970 mtdblock1
brw-rw---- 1 root root 31, 10 Jan 1 1970 mtdblock10
brw-rw---- 1 root root 31, 11 Jan 1 1970 mtdblock11
brw-rw---- 1 root root 31, 12 Jan 1 1970 mtdblock12
brw-rw---- 1 root root 31, 13 Jan 1 1970 mtdblock13
brw-rw---- 1 root root 31, 14 Jan 1 1970 mtdblock14
brw-rw---- 1 root root 31, 15 Jan 1 1970 mtdblock15
brw-rw---- 1 root root 31, 16 Jan 1 1970 mtdblock16
brw-rw---- 1 root root 31, 17 Jan 1 1970 mtdblock17
brw-rw---- 1 root root 31, 18 Jan 1 1970 mtdblock18
brw-rw---- 1 root root 31, 19 Jan 1 1970 mtdblock19
brw-rw---- 1 root root 31, 2 Jan 1 1970 mtdblock2
brw-rw---- 1 root root 31, 3 Jan 1 1970 mtdblock3
brw-rw---- 1 root root 31, 4 Jan 1 1970 mtdblock4
brw-rw---- 1 root root 31, 5 Jan 1 1970 mtdblock5
brw-rw---- 1 root root 31, 6 Jan 1 1970 mtdblock6
brw-rw---- 1 root root 31, 7 Jan 1 1970 mtdblock7
brw-rw---- 1 root root 31, 8 Jan 1 1970 mtdblock8
brw-rw---- 1 root root 31, 9 Jan 1 1970 mtdblock9
crw-rw---- 1 root root 10, 90 Jan 1 1970 ramdump_AR6320
crw-rw---- 1 root root 10, 89 Jan 1 1970 ramdump_AR6320_SD
crw-rw---- 1 root root 10, 85 Jan 1 1970 ramdump_modem
crw-rw---- 1 root root 10, 80 Jan 1 1970 ramdump_smem
cat /proc/mounts
Code:
rootfs / rootfs rw 0 0
ubi0:rootfs / ubifs rw,relatime,bulk_read,chk_data_crc 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
tmpfs /dev tmpfs rw,relatime,size=64k,mode=755 0 0
devpts /dev/pts devpts rw,relatime,gid=5,mode=620 0 0
tmpfs /run tmpfs rw,nosuid,nodev,mode=755 0 0
tmpfs /var/volatile tmpfs rw,relatime 0 0
tmpfs /media/ram tmpfs rw,relatime 0 0
ubi0:usrfs /data ubifs rw,relatime,bulk_read,chk_data_crc 0 0
/dev/ubi1_0 /firmware ubifs rw,relatime,bulk_read,chk_data_crc 0 0
ubi2:userrw /mnt/userrw ubifs rw,sync,relatime,bulk_read,chk_data_crc 0 0
ubi3:hdata /mnt/hdata ubifs ro,relatime,bulk_read,chk_data_crc 0 0
tmpfs /media/drives tmpfs ro,relatime,size=4k 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
var /var tmpfs rw,relatime 0 0
/dev/loop0 /mnt/hdata/licenses squashfs ro,relatime 0 0
I tried poking around /sys/devices/7980000.nand but I'm not as experienced with *NIX systems. I've also tried messing with QPST and similar tools but to no avail.
bump
MR1100?
I have been able to successfully build AOSP for Android 8.1 (I want to say `lunch aosp_arm64`), and I also got the source for the kernel from the manufacturer which successfully builds. The problem is when I try to flash it onto the device with `fastboot flashall`. There is no boot.img file anywhere. I guess I'm kind of confused on where to put the kernel build output and how to generate a valid boot.img.
Here's what files are output from the kernel build:
HTML:
Image .Image.cmd Image.gz .Image.gz.cmd Image.gz-dtb .Image.gz-dtb.cmd
Here's what is in the AOSP directory out/target/product/generic:
HTML:
-rwxrwx--- 1 root vboxsf 85 Dec 31 16:21 advancedFeatures.ini
-rwxrwx--- 1 root vboxsf 7 Dec 31 16:15 android-info.txt
-rwxrwx--- 1 root vboxsf 61 Jan 2 16:00 build_fingerprint.txt
drwxrwx--- 1 root vboxsf 68 Jan 1 04:23 cache
-rwxrwx--- 1 root vboxsf 69206016 Jan 1 04:23 cache.img
-rwxrwx--- 1 root vboxsf 91766 Dec 31 15:23 clean_steps.mk
-rwxrwx--- 1 root vboxsf 380 Dec 31 16:21 config.ini
drwxrwx--- 1 root vboxsf 136 Jan 1 13:49 data
drwxrwx--- 1 root vboxsf 102 Jan 1 02:15 dex_bootjars
drwxrwx--- 1 root vboxsf 204 Jan 1 14:21 fake_packages
drwxrwx--- 1 root vboxsf 204 Dec 31 18:03 gen
-rwxrwx--- 1 root vboxsf 304809 Jan 1 14:25 installed-files.json
-rwxrwx--- 1 root vboxsf 96906 Jan 1 14:25 installed-files.txt
-rwxrwx--- 1 root vboxsf 42220 Jan 1 14:24 installed-files-vendor.json
-rwxrwx--- 1 root vboxsf 12044 Jan 1 14:24 installed-files-vendor.txt
-rwxrwx--- 1 root vboxsf 4088328 Dec 31 16:21 kernel-ranchu
-rwxrwx--- 1 root vboxsf 2248129 Dec 31 16:15 module-info.json
drwxrwx--- 1 root vboxsf 782 Jan 1 14:24 obj
-rwxrwx--- 1 root vboxsf 38 Dec 31 15:10 previous_build_config.mk
-rwxrwx--- 1 root vboxsf 1025236 Jan 1 14:21 ramdisk.img
drwxrwx--- 1 root vboxsf 102 Dec 31 16:09 recovery
drwxrwx--- 1 root vboxsf 1122 Jan 1 14:21 root
drwxrwx--- 1 root vboxsf 306 Jan 1 13:48 symbols
drwxrwx--- 1 root vboxsf 612 Jan 1 14:25 system
-rwxrwx--- 1 root vboxsf 2147483648 Jan 1 14:30 system.img
-rwxrwx--- 1 root vboxsf 2149580800 Jan 1 14:33 system-qemu.img
-rwxrwx--- 1 root vboxsf 576716800 Jan 1 14:12 userdata.img
drwxrwx--- 1 root vboxsf 340 Jan 1 13:49 vendor
-rwxrwx--- 1 root vboxsf 99999744 Jan 1 14:25 vendor.img
-rwxrwx--- 1 root vboxsf 102760448 Jan 1 14:33 vendor-qemu.img
I feel like there's just one step I'm missing/not understanding somewhere.
It ended up being that Image.gz-dtb was the kernel image and Image.gz was the ramdisk image, so I was able to use those with abootimg to create a boot.img file