missing boot partition on xperia - Android Q&A, Help & Troubleshooting

Hello
I want to install new kernel image, but there is no boot partition, trying "ls" command gives this output:
~ # ls
acct init.goldfish.rc sd-ext
cache init.rc sdcard
config mnt sys
d modules system
data pre_hw_config.sh tmp
default.prop proc ueventd.delta.rc
dev recovery.fstab ueventd.goldfish.rc
etc res ueventd.rc
init root vendor
init.delta.rc sbin
~ # ls -l
drwxr-xr-x 3 root root 0 Feb 28 15:56 acct
drwxrwx--x 1 system cache 2048 Aug 31 16:12 cache
dr-x------ 2 root root 0 Feb 28 15:56 config
lrwxrwxrwx 1 root root 17 Feb 28 15:56 d -> /sys/kernel/debug
drwxrwx--x 1 system system 2048 Aug 31 16:12 data
-rw-r--r-- 1 root root 118 Jul 1 2012 default.prop
drwxr-xr-x 14 root root 3340 Feb 28 15:57 dev
lrwxrwxrwx 1 root root 11 Feb 28 15:56 etc -> /system/etc
-rwxr-xr-x 1 root root 98576 Aug 22 2012 init
-rwxr-xr-x 1 root root 5802 Jul 1 2012 init.delta.rc
-rwxr-xr-x 1 root root 1677 Jul 1 2012 init.goldfish.rc
-rwxr-xr-x 1 root root 15559 Aug 22 2012 init.rc
drwxrwxr-x 6 root system 0 Feb 28 15:56 mnt
drwxr-xr-x 2 root root 0 Feb 25 2012 modules
-rwxr-xr-x 1 root root 1406 Jul 1 2012 pre_hw_config.sh
dr-xr-xr-x 138 root root 0 Jan 1 1970 proc
-rwxr-xr-x 1 root root 243 Jul 1 2012 recovery.fstab
drwxr-xr-x 3 root root 0 Feb 28 15:57 res
drwx------ 2 root root 0 Aug 22 2012 root
drwxr-xr-x 2 root root 0 Jul 1 2012 sbin
drwxrwx--x 2 system system 0 Feb 28 15:56 sd-ext
lrwxrwxrwx 1 root root 11 Feb 28 15:56 sdcard -> /mnt/sdcard
drwxr-xr-x 12 root root 0 Jan 1 1970 sys
drwxr-xr-x 1 root root 2048 Feb 22 12:24 system
drwxr-xr-x 2 root root 0 Feb 28 15:57 tmp
-rw-r--r-- 1 root root 744 Jul 1 2012 ueventd.delta.rc
-rw-r--r-- 1 root root 0 Jul 1 2012 ueventd.goldfish.rc
-rw-r--r-- 1 root root 4225 Jul 1 2012 ueventd.rc
lrwxrwxrwx 1 root root 14 Feb 28 15:56 vendor -> /system/vendor
what should I do? its xperia x8, doesnt support fastboot

Related

Rockchip RK3188 - Dark EvoPAD 9740

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!

[Q] Create a edify_defs file

I tried to create my own edify_defs file to cook my own roms, but every time I try to flash the zip it fails because of that file it's not well. I don't know how to adapt it for my device. I tried to follow the template and other tutorials but it fails too.
Can anyone help me to create this file?
I attach some info:
recovery.fstab
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/bootimg /bootimg emmc defaults defaults
/dev/recovery /recovery emmc defaults defaults
/dev/uboot /uboot emmc defaults defaults
/[email protected] /system ext4 ro,noatime wait
/[email protected] /cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait
/[email protected] /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,encryptable=footer
/devices/platform/mtk-msdc.1/mmc_host/mmc1 auto vfat defaults voldmanaged=sdcard1:auto
Code:
~ # ls -l
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 0 Oct 19 01:35 boot
drwxr-xr-x 2 root root 0 Oct 19 01:35 cache
drwxrwx--x 26 system system 4096 Oct 19 01:14 data
drwxr-xr-x 2 root root 0 Oct 19 01:35 datadata
-rwx------ 1 400 401 1618 Sep 24 20:19 default.prop
drwxr-xr-x 10 root root 3120 Oct 19 01:36 dev
drwxr-xr-x 2 root root 0 Oct 19 01:35 emmc
lrwxrwxrwx 1 root root 20 Jan 1 1970 [email protected] -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 1 1970 [email protected] -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 1 1970 [email protected] -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Jan 1 1970 [email protected]_f -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Jan 1 1970 [email protected]_s -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Jan 1 1970 [email protected]_ro -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Jan 1 1970 [email protected] -> /dev/block/mmcblk0p7
drwx------ 2 400 401 0 Oct 19 01:44 etc
drwxr-xr-x 2 root root 0 Oct 19 01:35 external_sd
-rwx------ 1 400 401 27410 Sep 24 20:19 file_contexts
-rwx------ 1 400 401 975 Sep 24 20:19 fstab.mt8127
-rwx------ 1 400 401 187840 Sep 24 20:19 init
-rwx------ 1 400 401 3151 Sep 24 20:19 init.rc
drwxr-xr-x 2 root root 0 Oct 19 01:35 internal_sd
drwxrwxr-x 5 root system 0 Oct 19 01:35 mnt
dr-xr-xr-x 108 root root 0 Jan 1 1970 proc
-rwx------ 1 400 401 2201 Sep 24 20:19 property_contexts
drwxr-xr-x 2 root root 0 Oct 19 01:35 recovery
drwx------ 3 400 401 0 Sep 24 20:19 res
drwx------ 2 root root 0 Aug 13 16:33 root
drwx------ 3 400 401 0 Sep 24 20:19 sbin
drwxr-xr-x 2 root root 0 Oct 19 01:35 sd-ext
lrwxrwxrwx 1 root root 13 Oct 19 01:35 sdcard -> /data/media/0
-rwx------ 1 400 401 663 Sep 24 20:19 seapp_contexts
-rwx------ 1 400 401 75012 Sep 24 20:19 sepolicy
d---r-x--- 3 root sdcard_r 60 Oct 19 01:35 storage
dr-xr-xr-x 17 root root 0 Oct 19 01:35 sys
drwxr-xr-x 3 400 401 0 Sep 24 20:19 system
drwxrwxr-x 2 root shell 140 Oct 19 01:38 tmp
-rwx------ 1 400 401 7275 Sep 24 20:19 ueventd.rc
Code:
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 1017272 160 1017112 0% /dev
tmpfs 1017272 276 1016996 0% /tmp
tmpfs 1017272 0 1017272 0% /storage
tmpfs 1017272 0 1017272 0% /mnt/secure
tmpfs 1017272 0 1017272 0% /mnt/fuse
/[email protected] 28194832 7112272 21082560 25% /data
/dev/block/vold/179:97
1927480 679284 1248196 35% /storage/sdcard1
/[email protected] 1032088 662876 369212 64% /system
/[email protected] 705512 12632 692880 2% /cache
Thanks.

UBIFS/NAND Partitioning

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?

Building AOSP and Kernel from manufacturer - how to generate boot.img?

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

can't root/downgrade on s7 binary

hello , i can't root on u7 no matter cui4 3 or 2 , when i enter fastboot from the recovery bootloader all it says is entering fastboot mode... , and i can't flash anything it will just stuck on sending... , is it only me? or the root files aren't made for the international variant?
edit: systemless root rights(not sure if it does work at all) with the modified magisk , is downgrading possible?
127|:/ # sysrw
/system/bin/sh: sysrw: inaccessible or not found
127|:/ # cd system
:/system # ls -l
total 14692
drwxr-xr-x 2 root root 4096 2008-12-31 17:00 apex
drwxr-xr-x 101 root root 4096 2008-12-31 17:00 app
drwxr-x--x 4 root shell 13180 2021-10-28 19:57 bin
-rw------- 1 root root 3486 2008-12-31 17:00 build.prop
drwxr-xr-x 3 root root 4096 2008-12-31 17:00 cameradata
drwxr-xr-x 18 root root 4096 2021-10-28 19:54 etc
drwxr-xr-x 2 root root 12288 2008-12-31 17:00 fonts
drwxr-xr-x 5 root root 4096 2008-12-31 17:00 framework
drwxr-xr-x 3 root root 4096 2008-12-31 17:00 hidden
-rw-r--r-- 1 root root 34 2008-12-31 17:00 info.extra
drwxr-xr-x 5 root root 24576 2008-12-31 17:00 lib
drwxr-xr-x 6 root root 28672 2008-12-31 17:00 lib64
-rw-r--r-- 1 root root 280 2008-12-31 17:00 lkm_sec_info
drwxr-xr-x 3 root root 4096 2008-12-31 17:00 media
drwxr-xr-x 169 root root 4096 2008-12-31 17:00 priv-app
lrw-r--r-- 1 root root 8 2008-12-31 17:00 product -> /product
-rw-r--r-- 1 root root 14897702 2008-12-31 17:00 recovery-from-boot.pdrwxr-xr-x 5 root root 4096 2008-12-31 17:00 saiv
drwxr-xr-x 4 root root 4096 2008-12-31 17:00 system_ext
drwxr-xr-x 2 root root 4096 2008-12-31 17:00 tee
-rw-r--r-- 1 root root 257 2008-12-31 17:00 tima_measurement_info
drwxr-xr-x 3 root root 4096 2008-12-31 17:00 tts
drwxr-xr-x 7 root root 4096 2008-12-31 17:00 usr
lrw-r--r-- 1 root root 7 2008-12-31 17:00 vendor -> /vendor
drwxr-xr-x 2 root root 4096 2008-12-31 17:00 vramdiskddata
:/system #

Categories

Resources