Related
I have extracted the Gear 2 firmware to a zip so people can look at the structure and possibly start modding the device. Its extracted from the newest rom available on Sammobile. If you have any questions let me know.
htt p://bit.ly/1m4mj5m < Remove the space still a junior member
-----------------------------------------------------------------------------------------------------------
I am trying to backup the current partitions to see the kernel/recovery and not getting far. Has anyone else been working on this?
sh-3.2$ cat /proc/partitions
major minor #blocks name
7 0 19732 loop0
179 0 3817472 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 8192 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 8192 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 16384 mmcblk0p9
259 2 12288 mmcblk0p10
259 3 8192 mmcblk0p11
259 4 65536 mmcblk0p12
259 5 131072 mmcblk0p13
259 6 2996224 mmcblk0p14
259 7 524288 mmcblk0p15
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
179:0 179:3 179:7 1:10 1:14 1:4 1:8 259:2 259:6 7:2 7:6
179:1 179:4 179:8 1:11 1:15 1:5 1:9 259:3 259:7 7:3 7:7
179:16 179:5 1:0 1:12 1:2 1:6 259:0 259:4 7:0 7:4
179:2 179:6 1:1 1:13 1:3 1:7 259:1 259:5 7:1 7:5
Current information I can receive from the watch.
If I try to make a backup obviously it fails with the following message..
D:\tizen-wearable-sdk\tools>sdb shell
sh-3.2$ chmod 755 /tmp/rkdump
sh-3.2$ /tmp/rkdump /dev/mmcblk0boot0 /tmp/update.img
/tmp/rkdump: /dev/mmcblk0boot0: Permission denied
sh-3.2$ /tmp/rkdump /dev/mmcblk0p1 /tmp/update.img
/tmp/rkdump: /dev/mmcblk0p1: Permission denied
sh-3.2$ /tmp/rkdump /dev/mmcblk0p2 /tmp/update.img
/tmp/rkdump: /dev/mmcblk0p2: Permission denied
This is my start with the device. I would like others input as well. Thanks!
Bumped did you make any progress?
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Code:
sh-3.2$ ls -lR /dev/block
/dev/block:
total 0
lrwxrwxrwx 1 root root 10 May 15 10:08 179:0 -> ../mmcblk0
lrwxrwxrwx 1 root root 12 May 15 10:08 179:1 -> ../mmcblk0p1
lrwxrwxrwx 1 root root 15 May 15 10:08 179:16 -> ../mmcblk0boot
lrwxrwxrwx 1 root root 12 May 15 10:08 179:2 -> ../mmcblk0p2
lrwxrwxrwx 1 root root 12 May 15 10:08 179:3 -> ../mmcblk0p3
lrwxrwxrwx 1 root root 12 May 15 20:01 179:4 -> ../mmcblk0p4
lrwxrwxrwx 1 root root 12 May 15 10:08 179:5 -> ../mmcblk0p5
lrwxrwxrwx 1 root root 12 May 15 10:08 179:6 -> ../mmcblk0p6
lrwxrwxrwx 1 root root 12 May 15 10:08 179:7 -> ../mmcblk0p7
lrwxrwxrwx 1 root root 15 May 15 10:08 179:8 -> ../mmcblk0boot0
lrwxrwxrwx 1 root root 7 May 15 10:08 1:0 -> ../ram0
lrwxrwxrwx 1 root root 7 May 15 10:08 1:1 -> ../ram1
lrwxrwxrwx 1 root root 8 May 15 10:08 1:10 -> ../ram10
lrwxrwxrwx 1 root root 8 May 15 10:08 1:11 -> ../ram11
lrwxrwxrwx 1 root root 8 May 15 10:08 1:12 -> ../ram12
lrwxrwxrwx 1 root root 8 May 15 10:08 1:13 -> ../ram13
lrwxrwxrwx 1 root root 8 May 15 10:08 1:14 -> ../ram14
lrwxrwxrwx 1 root root 8 May 15 10:08 1:15 -> ../ram15
lrwxrwxrwx 1 root root 7 May 15 10:08 1:2 -> ../ram2
lrwxrwxrwx 1 root root 7 May 15 10:08 1:3 -> ../ram3
lrwxrwxrwx 1 root root 7 May 15 10:08 1:4 -> ../ram4
lrwxrwxrwx 1 root root 7 May 15 10:08 1:5 -> ../ram5
lrwxrwxrwx 1 root root 7 May 15 10:08 1:6 -> ../ram6
lrwxrwxrwx 1 root root 7 May 15 10:08 1:7 -> ../ram7
lrwxrwxrwx 1 root root 7 May 15 10:08 1:8 -> ../ram8
lrwxrwxrwx 1 root root 7 May 15 10:08 1:9 -> ../ram9
lrwxrwxrwx 1 root root 12 May 15 10:08 259:0 -> ../mmcblk0p8
lrwxrwxrwx 1 root root 12 May 15 10:08 259:1 -> ../mmcblk0p9
lrwxrwxrwx 1 root root 13 May 15 10:08 259:2 -> ../mmcblk0p10
lrwxrwxrwx 1 root root 13 May 15 10:08 259:3 -> ../mmcblk0p11
lrwxrwxrwx 1 root root 13 May 15 10:08 259:4 -> ../mmcblk0p12
lrwxrwxrwx 1 root root 13 May 15 10:08 259:5 -> ../mmcblk0p13
lrwxrwxrwx 1 root root 13 May 15 10:08 259:6 -> ../mmcblk0p14
lrwxrwxrwx 1 root root 13 May 15 10:08 259:7 -> ../mmcblk0p15
lrwxrwxrwx 1 root root 8 May 15 10:08 7:0 -> ../loop0
lrwxrwxrwx 1 root root 8 May 15 10:08 7:1 -> ../loop1
lrwxrwxrwx 1 root root 8 May 15 10:08 7:2 -> ../loop2
lrwxrwxrwx 1 root root 8 May 15 10:08 7:3 -> ../loop3
lrwxrwxrwx 1 root root 8 May 15 10:08 7:4 -> ../loop4
lrwxrwxrwx 1 root root 8 May 15 10:08 7:5 -> ../loop5
lrwxrwxrwx 1 root root 8 May 15 10:08 7:6 -> ../loop6
lrwxrwxrwx 1 root root 8 May 15 10:08 7:7 -> ../loop7
sh-3.2$
also found this in sdb help :
commands:
sdb root <on | off> - switch to root or developer account mode
'on' means to root mode, and vice versa
of course on = permission denied ..
OTA update failed, the phone spontaneously shut off and rebooted to the beautiful "Your device is corrupt. It can't be trusted and may not work properly." screen. After being greeted by said screen, the phone reboots and goes to the same screen. Recovery doesn't boot. Fastboot doesn't allow me to flash any image (even signed from google). If I boot into fastboot and do a "fastboot continue", the phone boots to a blank screen with adb running in recovery mode, but with the port closed (can't flash a recovery OTA).
Someone please help. I've tried all solutions I could think of. I don't know what is left.
Sounds like a trip to a Verizon store is in your future :/
mruno said:
Sounds like a trip to a Verizon store is in your future :/
Click to expand...
Click to collapse
Any chance Google themselves would be able to take care of this?
mruno said:
Sounds like a trip to a Verizon store is in your future :/
Click to expand...
Click to collapse
I wonder if the OP unlocked the bootloader and rooted. If so, they might not take too kindly to replacing the device. If it's stock then head there today and get a new one. How about a factory reset attempt?
bobby janow said:
I wonder if the OP unlocked the bootloader and rooted. If so, they might not take too kindly to replacing the device. If it's stock then head there today and get a new one. How about a factory reset attempt?
Click to expand...
Click to collapse
Impossible to factory reset. Recovery does not boot. Bootloader is locked, as fastboot flashing unlock returns as invalid.
dwegiel said:
Impossible to factory reset. Recovery does not boot. Bootloader is locked, as fastboot flashing unlock returns as invalid.
Click to expand...
Click to collapse
Recovery doesn't boot? Do you get the dead Android or something else?
PiousInquisitor said:
Recovery doesn't boot? Do you get the dead Android or something else?
Click to expand...
Click to collapse
Same "Your device is corrupt. It can't be trusted and may not work properly.", and recovery fails to boot. Nothing on the display, phone either shuts off or boots to charging mode.
dwegiel said:
Same "Your device is corrupt. It can't be trusted and may not work properly.", and recovery fails to boot. Nothing on the display, phone either shuts off or boots to charging mode.
Click to expand...
Click to collapse
What was your situation before this started? Unlocked? Rooted?
Edit: I see you were updating.
PiousInquisitor said:
What was your situation before this started? Unlocked? Rooted?
Edit: I see you were updating.
Click to expand...
Click to collapse
None of the above, stock Android OS.
dwegiel said:
Same "Your device is corrupt. It can't be trusted and may not work properly.", and recovery fails to boot. Nothing on the display, phone either shuts off or boots to charging mode.
Click to expand...
Click to collapse
Recovery is sometimes not easy to get in to. I had to do it 3 times in a row before I got it to take. So I'm sure you know it's hold the power button and then hit vol up. But if you don't get it just right it will reboot or turn off. Does adb work?
Ok so this is getting weirder by the second. Just saw a teamwin recovery screen pop up...
I purchased this device second hand and used it with no problems until the first update, but it definitely looks somewhat tampered with. Any advice?
This occurs when I perform a fastboot continue. At that point I have adb up in recovery mode. But since I see nothing on screen, I can do nothing. Can't sideload because it's not at the sideload screen. Suggestions?
EDIT: Okay, so I have a VERY basic adb shell up through TWRP. I can't access TWRP directly because it "hasn't started". Ideas?
EDIT2: adb shell has basic busybox commands and is running root. I have downloaded a new TWRP image. What is the partition where the pixel has its recovery? Under /dev/block/mmc....?
Can you get into bootloader?
Which slot is active?
Can you
Fastboot set_active _b
Or
Fastboot set_active _a
And try getting to recovery or booting?
Sent from my sailfish using XDA Labs
nednednerb said:
Can you get into bootloader?
Which slot is active?
Can you
Fastboot set_active _b
Or
Fastboot set_active _a
And try getting to recovery or booting?
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
b slot is active. Will reboot now and (attempt to) switch to a. Found the appropriate fastboot by googling, please hold...
Code:
Setting current slot to 'a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.098s
What a surprise
Also to clear up, the only way for me to get thrown into this psuedo adb shell in TWRP is to "fastboot continue" at the fastboot screen. Recovery fails to boot. System fails to boot. Fastboot is useless because oem unlock is not possible.
Partition table dumped. Any ideas for where the recovery resides?
Side note: I have never ever seen this many partitions on any device. Ever.
Code:
# cat /proc/partitions
major minor #blocks name
8 16 4096 sdb
8 17 4052 sdb1
8 32 4096 sdc
8 33 4052 sdc1
8 48 49152 sdd
8 49 1024 sdd1
8 50 8 sdd2
8 51 32768 sdd3
8 52 128 sdd4
8 53 4 sdd5
8 54 4 sdd6
8 55 1024 sdd7
8 56 4 sdd8
8 57 2048 sdd9
8 58 2048 sdd10
8 59 1024 sdd11
8 60 4 sdd12
8 61 9020 sdd13
8 0 124866560 sda
8 1 512 sda1
8 2 512 sda2
8 3 512 sda3
8 4 512 sda4
8 5 2048 sda5
8 6 2048 sda6
8 7 512 sda7
8 8 512 sda8
8 9 512 sda9
8 10 512 sda10
8 11 512 sda11
8 12 512 sda12
8 13 256 sda13
8 14 256 sda14
8 15 256 sda15
259 0 256 sda16
259 1 4096 sda17
259 2 4096 sda18
259 3 32768 sda19
259 4 32768 sda20
259 5 32768 sda21
259 6 32768 sda22
259 7 128 sda23
259 8 128 sda24
259 9 71680 sda25
259 10 71680 sda26
259 11 256 sda27
259 12 256 sda28
259 13 256 sda29
259 14 256 sda30
259 15 307200 sda31
259 16 307200 sda32
259 17 2097152 sda33
259 18 2097152 sda34
259 19 119758848 sda35
259 20 4820 sda36
8 64 36864 sde
8 65 512 sde1
8 66 6144 sde2
8 67 4096 sde3
8 68 2048 sde4
8 69 16384 sde5
8 70 7636 sde6
8 80 8192 sdf
8 81 16 sdf1
8 82 256 sdf2
8 83 2048 sdf3
8 84 4 sdf4
8 85 5824 sdf5
Full partition table dumped:
Code:
lrwxrwxrwx 1 root root 16 Jan 1 13:41 aboot_a -> /dev/block/sda17
lrwxrwxrwx 1 root root 16 Jan 1 13:41 aboot_b -> /dev/block/sda18
lrwxrwxrwx 1 root root 16 Jan 1 13:41 apdp_a -> /dev/block/sda29
lrwxrwxrwx 1 root root 16 Jan 1 13:41 apdp_b -> /dev/block/sda30
lrwxrwxrwx 1 root root 15 Jan 1 13:41 board_info -> /dev/block/sdf1
lrwxrwxrwx 1 root root 16 Jan 1 13:41 boot_a -> /dev/block/sda19
lrwxrwxrwx 1 root root 16 Jan 1 13:41 boot_b -> /dev/block/sda20
lrwxrwxrwx 1 root root 15 Jan 1 13:41 bootlocker_a -> /dev/block/sda1
lrwxrwxrwx 1 root root 15 Jan 1 13:41 bootlocker_b -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 Jan 1 13:41 cdt -> /dev/block/sdd12
lrwxrwxrwx 1 root root 16 Jan 1 13:41 cmnlib32_a -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 Jan 1 13:41 cmnlib32_b -> /dev/block/sda14
lrwxrwxrwx 1 root root 16 Jan 1 13:41 cmnlib64_a -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 Jan 1 13:41 cmnlib64_b -> /dev/block/sda16
lrwxrwxrwx 1 root root 16 Jan 1 13:41 ddr -> /dev/block/sdd11
lrwxrwxrwx 1 root root 16 Jan 1 13:41 devcfg_a -> /dev/block/sda23
lrwxrwxrwx 1 root root 16 Jan 1 13:41 devcfg_b -> /dev/block/sda24
lrwxrwxrwx 1 root root 15 Jan 1 13:41 devinfo -> /dev/block/sdf4
lrwxrwxrwx 1 root root 15 Jan 1 13:41 devinfobak -> /dev/block/sdd5
lrwxrwxrwx 1 root root 15 Jan 1 13:41 dip -> /dev/block/sdd7
lrwxrwxrwx 1 root root 15 Jan 1 13:41 dpo -> /dev/block/sdd6
lrwxrwxrwx 1 root root 15 Jan 1 13:41 frp -> /dev/block/sde1
lrwxrwxrwx 1 root root 15 Jan 1 13:41 fsc -> /dev/block/sdd8
lrwxrwxrwx 1 root root 15 Jan 1 13:41 fsg -> /dev/block/sdf3
lrwxrwxrwx 1 root root 16 Jan 1 13:41 hosd_a -> /dev/block/sda21
lrwxrwxrwx 1 root root 16 Jan 1 13:41 hosd_b -> /dev/block/sda22
lrwxrwxrwx 1 root root 16 Jan 1 13:41 hyp_a -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 Jan 1 13:41 hyp_b -> /dev/block/sda12
lrwxrwxrwx 1 root root 15 Jan 1 13:41 keymaster_a -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 Jan 1 13:41 keymaster_b -> /dev/block/sda4
lrwxrwxrwx 1 root root 15 Jan 1 13:41 metadata -> /dev/block/sde5
lrwxrwxrwx 1 root root 15 Jan 1 13:41 mfg -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 Jan 1 13:41 misc -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 Jan 1 13:41 modem_a -> /dev/block/sda25
lrwxrwxrwx 1 root root 16 Jan 1 13:41 modem_b -> /dev/block/sda26
lrwxrwxrwx 1 root root 15 Jan 1 13:41 modemst1 -> /dev/block/sdd9
lrwxrwxrwx 1 root root 16 Jan 1 13:41 modemst2 -> /dev/block/sdd10
lrwxrwxrwx 1 root root 16 Jan 1 13:41 msadp_a -> /dev/block/sda27
lrwxrwxrwx 1 root root 16 Jan 1 13:41 msadp_b -> /dev/block/sda28
lrwxrwxrwx 1 root root 15 Jan 1 13:41 persist -> /dev/block/sdd3
lrwxrwxrwx 1 root root 15 Jan 1 13:41 pg1fs -> /dev/block/sde3
lrwxrwxrwx 1 root root 15 Jan 1 13:41 pg2fs -> /dev/block/sde4
lrwxrwxrwx 1 root root 15 Jan 1 13:41 pmic_a -> /dev/block/sda9
lrwxrwxrwx 1 root root 16 Jan 1 13:41 pmic_b -> /dev/block/sda10
lrwxrwxrwx 1 root root 15 Jan 1 13:41 ramdump -> /dev/block/sde2
lrwxrwxrwx 1 root root 16 Jan 1 13:41 reserve0 -> /dev/block/sda36
lrwxrwxrwx 1 root root 16 Jan 1 13:41 reserve3 -> /dev/block/sdd13
lrwxrwxrwx 1 root root 15 Jan 1 13:41 reserve4 -> /dev/block/sde6
lrwxrwxrwx 1 root root 15 Jan 1 13:41 reserve5 -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 Jan 1 13:41 rpm_a -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 Jan 1 13:41 rpm_b -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 Jan 1 13:41 sec -> /dev/block/sdd4
lrwxrwxrwx 1 root root 15 Jan 1 13:41 ssd -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 Jan 1 13:41 system_a -> /dev/block/sda33
lrwxrwxrwx 1 root root 16 Jan 1 13:41 system_b -> /dev/block/sda34
lrwxrwxrwx 1 root root 15 Jan 1 13:41 tz_a -> /dev/block/sda5
lrwxrwxrwx 1 root root 15 Jan 1 13:41 tz_b -> /dev/block/sda6
lrwxrwxrwx 1 root root 16 Jan 1 13:41 userdata -> /dev/block/sda35
lrwxrwxrwx 1 root root 16 Jan 1 13:41 vendor_a -> /dev/block/sda31
lrwxrwxrwx 1 root root 16 Jan 1 13:41 vendor_b -> /dev/block/sda32
lrwxrwxrwx 1 root root 15 Jan 1 13:41 xbl_a -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 Jan 1 13:41 xbl_b -> /dev/block/sdc1
SUCCESS. Stock recovery boots.
Used the gimped TWRP adb shell to push aboot.img and boot.img from a stock rom. And dded them to the respective partitions, on the _b boot slots.
dwegiel said:
SUCCESS. Stock recovery boots.
Used the gimped TWRP adb shell to push aboot.img and boot.img from a stock rom. And dded them to the respective partitions, on the _b boot slots.
Click to expand...
Click to collapse
May I suggest unlocking the bootloader now that you have things going better for you?
Did you ever get the system to boot up?
Can't FRP is locked. Guess the FRP partition got screwed.
dwegiel said:
SUCCESS. Stock recovery boots.
Used the gimped TWRP adb shell to push aboot.img and boot.img from a stock rom. And dded them to the respective partitions, on the _b boot slots.
Click to expand...
Click to collapse
I have the same problem. I'm trying to follow your steps, but I'm lost
Currently, phone is on Boot-slot: b
Code:
fastboot set_active_a
usage: fastboot [ <option> ] <command>
doesn't do anything
sorry I'm noob. Please help.
azn6929 said:
I have the same problem. I'm trying to follow your steps, but I'm lost
Currently, phone is on Boot-slot: b
Code:
fastboot set_active_a
usage: fastboot [ <option> ] <command>
doesn't do anything
sorry I'm noob. Please help.
Click to expand...
Click to collapse
How do you have the same problem. You have a locked bootloader with TWRP?
Sent from my Pixel using Tapatalk
---------- Post added at 04:03 AM ---------- Previous post was at 04:01 AM ----------
Can you push full OTA image in stock recovery?
Sent from my Pixel using Tapatalk
Sometime you need to build some mod or own custom ROM for a new device or the device which don't have much development on it.On these situations to flash any partition to the device we need to know it's actual block,size,path,user privilage.
This can typically done by a Root explorer or via ADB shell.
In this comprehensive info guide I will focous on getting partition details via ADB shell.
Let's Dive In:-
REQUIREMENTS
1. UNLOCKED BOOTLOADER.
2. SUPERSU/MAGISK FOR ROOT ACCESS.
3. ADB INSTALLED PROPERLY IN PC.
4. RESPECTIVE DEVICE DRIVERS. (e.g. for moto g5 plus,which i have,need motorola usb drivers to be installed.)
PROCEDURE
1. Using df lists the filesystem path alias and size info as seen below (total size, used, free and block size).
Example :
Code:
[email protected]:/ # df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 1714040 3732 1710308 1% /
tmpfs 1819500 712 1818788 1% /dev
/dev/block/mmcblk0p53 3320680 1882092 1438588 57% /system
tmpfs 1819500 0 1819500 0% /mnt
/data/media 25782252 3489280 22292972 14% /mnt/runtime/default/emulated
/dev/block/vold/public:179_65 15640832 11533440 4107392 74% /mnt/media_rw/79D8-1EE2
/mnt/media_rw/79D8-1EE2 15640832 11533440 4107392 74% /mnt/runtime/default/79D8-1EE2
/dev/block/mmcblk0p54 25782252 3489280 22292972 14% /data
/dev/block/mmcblk0p52 253920 228 253692 1% /cache
/dev/block/mmcblk0p19 96688 69552 27136 72% /firmware
/dev/block/mmcblk0p29 2500 2492 8 100% /fsg
/dev/block/mmcblk0p22 12016 5052 6964 43% /dsp
/dev/block/mmcblk0p30 28144 520 27624 2% /persist
/dev/block/loop0 92656 996 91660 2% /su
2. Using cat /proc/mounts shows the partition file path, the alias, the filesystem type, the startnig inode, the number of blocks, read/write status (and other parameters of the individual partition that I'm not entirely sure of).
Example:
Code:
[email protected]:/ # cat /proc/mounts
rootfs / rootfs ro,seclabel,size=1714040k,nr_inodes=428510 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1819500k,nr_inodes=454875,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /dev/cpuset cgroup rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
proc /proc proc rw,relatime,gid=3009,hidepid=2 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tracefs /sys/kernel/tracing tracefs rw,relatime 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/system /system ext4 ro,seclabel,relatime,discard,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,size=1819500k,nr_inodes=454875,mode=755,gid=1000 0 0
/data/media /mnt/runtime/default/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid 0 0
/data/media /mnt/runtime/read/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=23,derive_gid 0 0
/data/media /mnt/runtime/write/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid 0 0
/dev/block/vold/public:179_65 /mnt/media_rw/79D8-1EE2 vfat rw,dirsync,nosuid,nodev,noexec,noatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/mnt/media_rw/79D8-1EE2 /mnt/runtime/default/79D8-1EE2 sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,mask=6 0 0
/mnt/media_rw/79D8-1EE2 /mnt/runtime/read/79D8-1EE2 sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=18 0 0
/mnt/media_rw/79D8-1EE2 /mnt/runtime/write/79D8-1EE2 sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=18 0 0
none /config configfs rw,relatime 0 0
/dev/block/bootdevice/by-name/userdata /data f2fs rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,discard,user_xattr,inline_xattr,acl,inline_data,nobarrier,extent_cache,active_logs=6 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/bootdevice/by-name/modem /firmware ext4 ro,context=u:object_r:firmware_file:s0,nosuid,nodev,relatime,nobarrier,data=ordered 0 0
/dev/block/bootdevice/by-name/fsg /fsg ext4 ro,context=u:object_r:fsg_file:s0,nosuid,nodev,relatime 0 0
/dev/block/bootdevice/by-name/dsp /dsp ext4 ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/persist /persist ext4 rw,context=u:object_r:persist_file:s0,nosuid,nodev,noatime,noauto_da_alloc,data=ordered 0 0
/dev/block/loop0 /su ext4 rw,seclabel,noatime,data=ordered 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,size=1819500k,nr_inodes=454875,mode=755,gid=1000 0 0
/data/media /storage/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid 0 0
/mnt/media_rw/79D8-1EE2 /storage/79D8-1EE2 sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,mask=6 0 0
tmpfs /storage/self tmpfs rw,seclabel,relatime,size=1819500k,nr_inodes=454875,mode=755,gid=1000 0 0
3.Using cat /proc/partitions you will get the actual partition name identifier and the number of blocks in the partition.
Example:
Code:
[email protected]:/ # cat /proc/partitions
major minor #blocks name
7 0 98304 loop0
254 0 524288 zram0
179 0 30535680 mmcblk0
179 1 512 mmcblk0p1
179 2 256 mmcblk0p2
179 3 1792 mmcblk0p3
179 4 64 mmcblk0p4
179 5 1536 mmcblk0p5
179 6 256 mmcblk0p6
179 7 256 mmcblk0p7
179 8 256 mmcblk0p8
179 9 192 mmcblk0p9
179 10 512 mmcblk0p10
179 11 256 mmcblk0p11
179 12 1792 mmcblk0p12
179 13 64 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 256 mmcblk0p15
179 16 256 mmcblk0p16
179 17 256 mmcblk0p17
179 18 192 mmcblk0p18
179 19 102400 mmcblk0p19
179 20 1 mmcblk0p20
179 21 8 mmcblk0p21
179 22 16384 mmcblk0p22
179 23 32 mmcblk0p23
179 24 16 mmcblk0p24
179 25 512 mmcblk0p25
179 26 512 mmcblk0p26
179 27 2048 mmcblk0p27
179 28 2048 mmcblk0p28
179 29 8192 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 512 mmcblk0p31
259 0 128 mmcblk0p32
259 1 16384 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 512 mmcblk0p35
259 4 8192 mmcblk0p36
259 5 16384 mmcblk0p37
259 6 20580 mmcblk0p38
259 7 1024 mmcblk0p39
259 8 32 mmcblk0p40
259 9 512 mmcblk0p41
259 10 1024 mmcblk0p42
259 11 512 mmcblk0p43
259 12 2048 mmcblk0p44
259 13 256 mmcblk0p45
259 14 256 mmcblk0p46
259 15 8 mmcblk0p47
259 16 128 mmcblk0p48
259 17 8192 mmcblk0p49
259 18 8192 mmcblk0p50
259 19 671744 mmcblk0p51
259 20 262144 mmcblk0p52
259 21 3538944 mmcblk0p53
259 22 25784303 mmcblk0p54
179 32 4096 mmcblk0rpmb
179 64 15645696 mmcblk1
179 65 15644672 mmcblk1p1
Here comes a tricky part,
This folder in which by-name output is stored varies from devices to devices.
I will write the procedure to find this thing out.
Note : Here I am using MOTO G5 PLUS [POTTER] for demonstration.
As I change directory to /dev/block/bootdevice/ & ls to see the files & folders in this folder , i found that by-name folder which i was looking for.
Example:
Code:
[email protected]:/ # cd /dev/block/bootdevice/
[email protected]:/dev/block/bootdevice # ls -a -l
total 0
drwxr-xr-x 4 root root 1200 1970-08-14 04:53 .
drwxr-xr-x 4 root root 80 2018-03-22 09:08 ..
drwxr-xr-x 2 root root 1120 1970-08-14 04:53 by-name
drwxr-xr-x 2 root root 1120 1970-08-14 04:53 by-num
lrwxrwxrwx 1 root root 18 1970-08-14 04:53 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p10 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p11 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p12 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p13 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p14 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p15 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p16 -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p17 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p18 -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p19 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 mmcblk0p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p20 -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p21 -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p22 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p23 -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p24 -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p25 -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p26 -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p27 -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p28 -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p29 -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 mmcblk0p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p30 -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p31 -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p32 -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p33 -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p34 -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p35 -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p36 -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p37 -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p38 -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p39 -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 mmcblk0p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p40 -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p41 -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p42 -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p43 -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p44 -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p45 -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p46 -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p47 -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p48 -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p49 -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 mmcblk0p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p50 -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p51 -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p52 -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p53 -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mmcblk0p54 -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 mmcblk0p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 mmcblk0p7 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 mmcblk0p8 -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 mmcblk0p9 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 22 1970-08-14 04:53 mmcblk0rpmb -> /dev/block/mmcblk0rpmb
[email protected]:/dev/block/bootdevice #
Now i will enterby-name folder & see what's inside ?
...
Hola we nailed it !,I found exactly what i was trying to find,the detailed info of partitions.see below code.
Code:
[email protected]:/dev/block/bootdevice # cd by
by-name/ by-num/
[email protected]:/dev/block/bootdevice # cd by-name/
[email protected]:/dev/block/bootdevice/by-name # ls -a -l
total 0
drwxr-xr-x 2 root root 1120 1970-08-14 04:53 .
drwxr-xr-x 4 root root 1200 1970-08-14 04:53 ..
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 DDR -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 [COLOR="magenta"]apdp -> /dev/block/mmcblk0p45[/COLOR]
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 [COLOR="magenta"]boot -> /dev/block/mmcblk0p37[/COLOR]
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 [COLOR="magenta"]cache -> /dev/block/mmcblk0p52[/COLOR]
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 carrier -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 cid -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 cmnlib -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 cmnlib64 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 cmnlib64bak -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 cmnlibbak -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 devcfg -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 devcfgbak -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 dip -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 dpo -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 dsp -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 frp -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 fsc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 fsg -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 [COLOR="magenta"]hw -> /dev/block/mmcblk0p50[/COLOR]
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 keymaster -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 keymasterbak -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 limits -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-08-14 04:53[COLOR="Magenta"] logo -> /dev/block/mmcblk0p33[/COLOR]
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 logs -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 metadata -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 misc -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 [COLOR="magenta"]modem -> /dev/block/mmcblk0p19[/COLOR]
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 modemst1 -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 modemst2 -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mota -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 msadp -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 [COLOR="magenta"]oem -> /dev/block/mmcblk0p51[/COLOR]
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 padA -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 [COLOR="Magenta"]persist -> /dev/block/mmcblk0p30[/COLOR]
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 prov -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 provbak -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 [COLOR="magenta"]recovery -> /dev/block/mmcblk0p38[/COLOR]
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 [COLOR="magenta"]rpm -> /dev/block/mmcblk0p2[/COLOR]
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 rpmbak -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 sbl1bak -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 [COLOR="magenta"]sec -> /dev/block/mmcblk0p24[/COLOR]
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 sp -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 syscfg -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 [COLOR="magenta"]system -> /dev/block/mmcblk0p53[/COLOR]
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 tz -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 tzbak -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 [COLOR="magenta"]userdata -> /dev/block/mmcblk0p54[/COLOR]
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 utags -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 utagsBackup -> /dev/block/mmcblk0p26
[email protected]:/dev/block/bootdevice/by-name #
4. So for a particular device you can use ls -al /dev/block/platform/Your_Folder_Name/by-name to see the mapping between the partition alias and the path of actual partition file with owner & user.
Example:
Code:
[email protected]:/dev/block/bootdevice/by-name # ls - a -l /dev/block/bootdevice/b
ls: -: No such file or directory
ls: a: No such file or directory
total 0
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 DDR -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 apdp -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 boot -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 cache -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 carrier -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 cid -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 cmnlib -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 cmnlib64 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 cmnlib64bak -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 cmnlibbak -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 devcfg -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 devcfgbak -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 dip -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 dpo -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 dsp -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 frp -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 fsc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 fsg -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 hw -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 keymaster -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 keymasterbak -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 limits -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 logo -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 logs -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 metadata -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 misc -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 modem -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 modemst1 -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 modemst2 -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 mota -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 msadp -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 oem -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 padA -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 persist -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 prov -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 provbak -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 recovery -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 rpm -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 rpmbak -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 sbl1bak -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 sec -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 sp -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 syscfg -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 system -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 20 1970-08-14 04:53 tz -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 tzbak -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 userdata -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 utags -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1970-08-14 04:53 utagsBackup -> /dev/block/mmcblk0p26
1|[email protected]:/dev/block/bootdevice/by-name #
Now you must understand that before flashing anything do check the script of that file & make sure it is flashing to the right partition (mmcblk0xxx) according to your device.
IF your are happy & it helped you do hit the THANKS button. It always motivates when someone appreciate your work.
Thank You.
OFFICIAL COMMUNITY
Official Telegram Group
Official Telegram Channel
======== GEEKOFIA ========
VISIT
RESERVED
Big thanks
Thank you very much! That really helped!
I have a Tissot (mi a1) with TWRP dual booted by separating vendor_a, vendor_b, userdata_a, userdata_b. It is dual booted by cosmicdan's twrp with Resurrection remix ( slot_a) official and Dotos official ( slot_b). I want to mount userdata_b in resurrection remix or vice verse.
I have already tried these steps but no result.
1. create a folder named 'data2' in " /data/local/tmp/data2" .
2. open terminal.
3. run su.
4. Enter " mount -o rw /dev/block/mmcblk0p52 /data/local/tmp/data2" (as 52 is my userdata_b partition).
5. no error showing but nothing mounted.
Is there any way to mount this?
Hello,
I would like to install TWRP on an Ulefone Armor 8 I just got (Android 11, Mediatek MT6771 Helio P60, Octa-core Cortex-A73, Mali-G72 MP3). The closest I could find are the files from the Armor 6 model. The phone is almost the same, I even opened an issue on github to see if it is feasible to port those configs to the Armor 8 Pro model.
Is there an unofficial or easy way to build TWRP for this model?
My ultimate goal is to replace stock with TWRP + de-googled LineageOS. I am willing to provide feedback to help official support of both projects on this phone, I need some guidance though, I have never done this.
Any help would be amazing. Thank you very much.
You cann compile TWRP at your own
[GUIDE][NOOB FRIENDLY]How to compile TWRP from source step by step
Hi guys, Today because of the continuous requests of help to compile the TWRP on the developers' dedicated thread, I decided to write a guide for those who know very little about Linux and Android development but want to LEARN Initial...
forum.xda-developers.com
or ask here for help:
[CLOSED] I Will build TWRP for your device!
I wanna build twrp for your device! Pls give info about your device! if possible give stock firmware!
forum.xda-developers.com
jwoegerbauer said:
You cann compile TWRP at your own
[GUIDE][NOOB FRIENDLY]How to compile TWRP from source step by step
Hi guys, Today because of the continuous requests of help to compile the TWRP on the developers' dedicated thread, I decided to write a guide for those who know very little about Linux and Android development but want to LEARN Initial...
forum.xda-developers.com
or ask here for help:
[CLOSED] I Will build TWRP for your device!
I wanna build twrp for your device! Pls give info about your device! if possible give stock firmware!
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you very much. You put me into the right track. I will dig more into that.
I am very concerned if something goes wrong. If I break recovery, I will probably brick the phone. Is there a way to backup the recovery partition and "force" a recovery to that original recovery stock if needed?
If device's Android is rooted, and if ADB got enabled, then you can backup the Recovery partition by means of Android's dd command which is part of any Android distribution ( ToolBox, ToyBox ) and if needed, replay it with the same command.
Thank you. Yes, the device is rooted. I tried that but I couldn't find what is the recovery partition to dump with dd since I don't know how are mapped the devices.
These are the partitions:
Code:
Armor_8_Pro:/ # cat /proc/partitions
major minor #blocks name
1 0 4096 ram0
1 1 4096 ram1
1 2 4096 ram2
1 3 4096 ram3
1 4 4096 ram4
1 5 4096 ram5
1 6 4096 ram6
1 7 4096 ram7
1 8 4096 ram8
1 9 4096 ram9
1 10 4096 ram10
1 11 4096 ram11
1 12 4096 ram12
1 13 4096 ram13
1 14 4096 ram14
1 15 4096 ram15
7 0 85068 loop0
7 8 1776 loop1
7 16 111332 loop2
7 24 888 loop3
7 32 24668 loop4
7 40 5156 loop5
7 48 3920 loop6
7 56 980 loop7
7 64 85068 loop8
7 72 264 loop9
7 80 8680 loop10
7 88 5436 loop11
7 96 1776 loop12
7 104 4700 loop13
7 112 368 loop14
7 120 111332 loop15
254 0 4346084 zram0
8 0 4096 sda
8 16 4096 sdb
8 32 124960768 sdc
8 33 3072 sdc1
8 34 1024 sdc2
8 35 512 sdc3
8 36 20480 sdc4
8 37 1024 sdc5
8 38 32768 sdc6
8 39 65536 sdc7
8 40 23144 sdc8
8 41 32768 sdc9
8 42 8192 sdc10
8 43 16248 sdc11
8 44 8192 sdc12
8 45 49152 sdc13
8 46 2048 sdc14
8 47 65536 sdc15
259 0 8192 sdc16
259 1 8192 sdc17
259 2 8192 sdc18
259 3 14336 sdc19
259 4 102400 sdc20
259 5 1024 sdc21
259 6 6144 sdc22
259 7 1024 sdc23
259 8 15360 sdc24
259 9 15360 sdc25
259 10 15360 sdc26
259 11 16384 sdc27
259 12 1024 sdc28
259 13 32768 sdc29
259 14 65536 sdc30
259 15 8192 sdc31
259 16 5120 sdc32
259 17 8192 sdc33
259 18 8192 sdc34
259 19 9216 sdc35
259 20 102400 sdc36
259 21 1024 sdc37
259 22 6144 sdc38
259 23 1024 sdc39
259 24 15360 sdc40
259 25 15360 sdc41
259 26 15360 sdc42
259 27 16384 sdc43
259 28 1024 sdc44
259 29 32768 sdc45
259 30 65536 sdc46
259 31 8192 sdc47
259 32 6144 sdc48
259 33 6291456 sdc49
259 34 117642208 sdc50
259 35 44032 sdc51
259 36 16384 sdc52
253 0 1834036 dm-0
253 1 515812 dm-1
253 2 1354168 dm-2
253 3 95220 dm-3
7 128 888 loop16
7 136 7832 loop17
7 144 604 loop18
7 152 6920 loop19
7 160 4812 loop20
7 168 24668 loop21
7 176 5088 loop22
7 184 5156 loop23
7 192 2476 loop24
7 200 4824 loop25
7 208 19328 loop26
253 4 4092 dm-4
253 5 4092 dm-5
253 6 117642208 dm-6
And this are the mappings:
Code:
Armor_8_Pro:/ # ls -la /dev/block/by-name/
total 0
drwxr-xr-x 2 root root 1300 2021-06-22 20:36 .
drwxr-xr-x 6 root root 2280 2021-06-22 20:36 ..
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 boot_a -> /dev/block/sdc29
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 boot_b -> /dev/block/sdc45
lrwxrwxrwx 1 root root 15 2021-06-22 20:36 boot_para -> /dev/block/sdc2
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 cam_vpu1_a -> /dev/block/sdc24
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 cam_vpu1_b -> /dev/block/sdc40
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 cam_vpu2_a -> /dev/block/sdc25
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 cam_vpu2_b -> /dev/block/sdc41
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 cam_vpu3_a -> /dev/block/sdc26
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 cam_vpu3_b -> /dev/block/sdc42
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 dtbo_a -> /dev/block/sdc31
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 dtbo_b -> /dev/block/sdc47
lrwxrwxrwx 1 root root 15 2021-06-22 20:36 expdb -> /dev/block/sdc4
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 flashinfo -> /dev/block/sdc52
lrwxrwxrwx 1 root root 15 2021-06-22 20:36 frp -> /dev/block/sdc5
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 gz_a -> /dev/block/sdc27
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 gz_b -> /dev/block/sdc43
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 lk_a -> /dev/block/sdc28
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 lk_b -> /dev/block/sdc44
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 logo -> /dev/block/sdc16
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 md1img_a -> /dev/block/sdc20
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 md1img_b -> /dev/block/sdc36
lrwxrwxrwx 1 root root 15 2021-06-22 20:36 md_udc -> /dev/block/sdc8
lrwxrwxrwx 1 root root 15 2021-06-22 20:36 metadata -> /dev/block/sdc9
lrwxrwxrwx 1 root root 15 2021-06-22 20:36 nvcfg -> /dev/block/sdc6
lrwxrwxrwx 1 root root 15 2021-06-22 20:36 nvdata -> /dev/block/sdc7
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 nvram -> /dev/block/sdc15
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 otp -> /dev/block/sdc51
lrwxrwxrwx 1 root root 15 2021-06-22 20:36 para -> /dev/block/sdc3
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 persist -> /dev/block/sdc13
lrwxrwxrwx 1 root root 23 2021-06-22 20:36 preloader_a -> /dev/block/mmcblk0boot0
lrwxrwxrwx 1 root root 23 2021-06-22 20:36 preloader_b -> /dev/block/mmcblk0boot1
lrwxrwxrwx 1 root root 30 2021-06-22 20:36 preloader_emmc_a -> /dev/block/by-name/preloader_a
lrwxrwxrwx 1 root root 30 2021-06-22 20:36 preloader_emmc_b -> /dev/block/by-name/preloader_b
lrwxrwxrwx 1 root root 15 2021-06-22 20:36 preloader_raw_a -> /dev/block/dm-4
lrwxrwxrwx 1 root root 15 2021-06-22 20:36 preloader_raw_b -> /dev/block/dm-5
lrwxrwxrwx 1 root root 30 2021-06-22 20:36 preloader_ufs_a -> /dev/block/by-name/preloader_a
lrwxrwxrwx 1 root root 30 2021-06-22 20:36 preloader_ufs_b -> /dev/block/by-name/preloader_b
lrwxrwxrwx 1 root root 15 2021-06-22 20:36 proinfo -> /dev/block/sdc1
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 protect1 -> /dev/block/sdc10
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 protect2 -> /dev/block/sdc11
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 scp_a -> /dev/block/sdc22
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 scp_b -> /dev/block/sdc38
lrwxrwxrwx 1 root root 14 2021-06-22 20:36 sda -> /dev/block/sda
lrwxrwxrwx 1 root root 14 2021-06-22 20:36 sdb -> /dev/block/sdb
lrwxrwxrwx 1 root root 14 2021-06-22 20:36 sdc -> /dev/block/sdc
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 sec1 -> /dev/block/sdc14
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 seccfg -> /dev/block/sdc12
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 spmfw_a -> /dev/block/sdc21
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 spmfw_b -> /dev/block/sdc37
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 sspm_a -> /dev/block/sdc23
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 sspm_b -> /dev/block/sdc39
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 super -> /dev/block/sdc49
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 tee_a -> /dev/block/sdc32
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 tee_b -> /dev/block/sdc48
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 userdata -> /dev/block/sdc50
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 vbmeta_a -> /dev/block/sdc17
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 vbmeta_b -> /dev/block/sdc33
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 vbmeta_system_a -> /dev/block/sdc18
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 vbmeta_system_b -> /dev/block/sdc34
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 vbmeta_vendor_a -> /dev/block/sdc19
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 vbmeta_vendor_b -> /dev/block/sdc35
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 vendor_boot_a -> /dev/block/sdc30
lrwxrwxrwx 1 root root 16 2021-06-22 20:36 vendor_boot_b -> /dev/block/sdc46
Unfortunately there is little information about this Armor 8 pro phone model. I tried to use virtualbox and windows to use the SP tool to get the mappings but I couldn't get it to work. Maybe since I am using virtualbox something is not working properly with the drivers. I use linux natively on my notebook.
My roadmap is:
- [X] Root the phone
- [ ] Backup the original recovery partition (in case something goes wrong)
- [ ] Build TWRP
- [ ] Test TWRP on the phone by booting to it first
- [ ] Install TWRP on the phone to replace stock recovery
- [ ] Backup original stock Android image
- [ ] Build LineageOS (Android 11)
- [ ] Install LineageOS
- [ ] Contribute back the build to the LineageOS community
By means of SP Flash Tool create a Scatter file from where you can derive location of recovery.img
Example output:
Code:
partition_index: SYS7
partition_name: RECOVERY
file_name: recovery.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0xec0000
physical_start_addr: 0x0
partition_size: 0x600000
region: NONE
storage: HW_STORAGE_NAND
boundary_check: true
is_reserved: false
operation_type: UPDATE
d_type:
reserve: 0x00
I have the armor 8 pro to. Could you or someone with successfull root guide me through the full process?
I need to say that im pretty much a noob in this so theres no other way to do it with success. I have tried to find professional services without luck. I could even pay some money if that helps you help me.
Iwantrootpls said:
I have the armor 8 pro to. Could you or someone with successfull root guide me through the full process?
Click to expand...
Click to collapse
Write correct model about Armor 8 Pro.
That's already help for know different files & steps.
lopestom said:
Write correct model about Armor 8 Pro.
That's already help for know different files & steps.
Click to expand...
Click to collapse
8gb and 128g version
lopestom said:
Write correct model about Armor 8 Pro.
That's already help for know different files & steps.
Click to expand...
Click to collapse
the official rom download page from ulefone only has 6gb version in it. thats a big difference?
Iwantrootpls said:
the official rom download page from ulefone only has 6gb version in it. thats a big difference?
Click to expand...
Click to collapse
Iwantrootpls said:
8gb and 128g version
Click to expand...
Click to collapse
We have stock ROM for 8G. May be the model about EU or Non-EU that's a doubt now.
The device must ALWAYS be handled with the bootloader unlocked!
Spoiler: WARNING
I am not responsible for any wrong attitude or action of the user. Keep in mind to perform all backups of your device mainly of NvRam, NvData and NvCfg files so that in the future you don't have a headache.
If you want only ROOT: you need the boot.img from stock ROM. Install last magisk (I think is v23) and you can look about patch boot.img. The steps is easy because magisk pacth boot.img and create a new file like pacth_boot.img or other name.
You need flash the pacth_boot.img with fastboot or SPFT.
More info here orr here.
Other way but not principal is about Custom Recovery like TWRP so we have one but it's ALPHA testing.
lopestom said:
We have stock ROM for 8G. May be the model about EU or Non-EU that's a doubt now.
The device must ALWAYS be handled with the bootloader unlocked!
Spoiler: WARNING
I am not responsible for any wrong attitude or action of the user. Keep in mind to perform all backups of your device mainly of NvRam, NvData and NvCfg files so that in the future you don't have a headache.
If you want only ROOT: you need the boot.img from stock ROM. Install last magisk (I think is v23) and you can look about patch boot.img. The steps is easy because magisk pacth boot.img and create a new file like pacth_boot.img or other name.
You need flash the pacth_boot.img with fastboot or SPFT.
More info here orr here.
Other way but not principal is about Custom Recovery like TWRP so we have one but it's ALPHA testing.
Click to expand...
Click to collapse
how do find that out? about the phone says nothing about that
lopestom said:
We have stock ROM for 8G. May be the model about EU or Non-EU that's a doubt now.
The device must ALWAYS be handled with the bootloader unlocked!
Spoiler: WARNING
I am not responsible for any wrong attitude or action of the user. Keep in mind to perform all backups of your device mainly of NvRam, NvData and NvCfg files so that in the future you don't have a headache.
If you want only ROOT: you need the boot.img from stock ROM. Install last magisk (I think is v23) and you can look about patch boot.img. The steps is easy because magisk pacth boot.img and create a new file like pacth_boot.img or other name.
You need flash the pacth_boot.img with fastboot or SPFT.
More info here orr here.
Other way but not principal is about Custom Recovery like TWRP so we have one but it's ALPHA testing.
Click to expand...
Click to collapse
also i cant find my boot.img file that i need to patch later
Iwantrootpls said:
also i cant find my boot.img file that i need to patch later
Click to expand...
Click to collapse
product name= "Ulefone_Armor_8_Pro_8GB_EEA"
Maybe is there a chance i could do these steps with a second mobile phone (samsung s9) and an usb stick (without use of computer)?
Iwantrootpls said:
product name= "Ulefone_Armor_8_Pro_8GB_EEA"
Maybe is there a chance i could do these steps with a second mobile phone (samsung s9) and an usb stick (without use of computer)?
Click to expand...
Click to collapse
Search: https://drive.google.com/drive/folders/1qT2jMCCTt9Q4PBkBlqU1tg5SeIiFvlqP
Update Official Ulefone Armor 8 Pro version: GQ3090RH5_KSXP60_Ulefone_EEA_20210826_V01 – X70HEWS88C7.GQU.Ulefone_EEA.HB.FHJ.AZVF.20210826.V3.01
full_k71v1_64_bsp-user 11 RP1A.200720.011 ( 8G Ram + 128G Rom )
lopestom said:
Search: https://drive.google.com/drive/folders/1qT2jMCCTt9Q4PBkBlqU1tg5SeIiFvlqP
Update Official Ulefone Armor 8 Pro version: GQ3090RH5_KSXP60_Ulefone_EEA_20210826_V01 – X70HEWS88C7.GQU.Ulefone_EEA.HB.FHJ.AZVF.20210826.V3.01
full_k71v1_64_bsp-user 11 RP1A.200720.011 ( 8G Ram + 128G Rom )
Click to expand...
Click to collapse
Thanks! So i am just extracting and starting to patch?
Iwantrootpls said:
Thanks! So i am just extracting and starting to patch?
Click to expand...
Click to collapse
If you not try so you never know.....
figured out. Thanks for good help!
Iwantrootpls said:
figured out. Thanks for good help!
Click to expand...
Click to collapse
good time.
tell me where to download the ADB driver?
does not see Windows in boot mode
Hi,
This is my first project that I'm currently working on.
I recently bought a android dashcam which UI I would like to change based on my personal preferences. Unfortunately I'm struggling to setup an environment where I can test the changes I make before replacing the original UI on the device itself. I identified the SystemUI.apk to be the place where the manufacturer made customization. I will be using the SystemUI.apk built from AOSP and making my changes based on that. I had no luck trying to decompile the SystemUI.apk in a way that I could build it again.
I was thinking that I could use an android emulator to use the same ROM as the device itself. The manufacturer did not provide any support in providing stock firmware images in any way. So I used the following steps to 'export' the firmware.
1. Unlocking the bootloader using the Identifier Token so I can flash images using fastboot. TWRP was not an option here because I could not find any images for my device nor could I port an TWRP image myself.
2. Enable ADB debugging over usb
3. Enable ADB root privileges using the password: 2846 (if i remember correctly)
4. Use ADB remount and ADB root to gain privileges over the partitions
5. Gain information on partition data
6. Use ADB pull to export images based on partitions
After following the above steps the next thing was to import the images into an emulator. I used the following steps to do this:
1. Create a new device within Android Studio that has the same screen size and os.
2. Replace the system.img, ramdisk.img with the exported variants in ~/Android/Sdk/../arm64-v8a
3. Turn off EncryptUserData inside advancedFeatures.ini to prevent errors like partitions that are unable to encrypt
4. Use the command below to start the emulator
Code:
~/Android/Sdk/emulator/emulator -avd Junsun_A104_API_27 -verbose -show-kernel
5. After running the emulator I receive the error below and the screen of the emulator stays black.
Code:
Please append a correct "root=" boot option; here are the available partitions:
fe00 2867200 vda driver: virtio_blk
fe10 67584 vdb driver: virtio_blk
fe20 819200 vdc driver: virtio_blk
fe30 409600 vdd driver: virtio_blk
fe40 524288 vde driver: virtio_blk
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
My assumption is that the emulator does not contain the same partition model used on the device. I could try to export each partition but I wouldn't know how to let the emulator know how to use these partitions. I tried to export the kernel and import it inside the emulator without luck. I did not receive any errors that way.
So my main question is:
- Is there any way I can import the device's rom inside an android emulator
Spoiler: Emulator Config
AvdId=Junsun_A104_API_27
PlayStore.enabled=false
abi.type=arm64-v8a
avd.ini.displayname=Junsun A104 API 27
avd.ini.encoding=UTF-8
disk.dataPartition.size=800M
fastboot.chosenSnapshotFile=
fastboot.forceChosenSnapshotBoot=no
fastboot.forceColdBoot=no
fastboot.forceFastBoot=yes
hw.accelerometer=yes
hw.arc=false
hw.audioInput=yes
hw.battery=yes
hw.camera.back=virtualscene
hw.camera.front=emulated
hw.cpu.arch=arm64
hw.cpu.ncore=4
hw.dPad=no
hw.device.hash2=MD5:7834f5e80eb849ceb46ce01cd4c704f7
hw.device.manufacturer=User
hw.device.name=Junsun A104
hw.gps=yes
hw.gpu.enabled=no
hw.gpu.mode=off
hw.initialOrientation=landscape
hw.keyboard=yes
hw.lcd.density=120
hw.lcd.height=320
hw.lcd.width=1480
hw.mainKeys=no
hw.ramSize=2560
hw.sdCard=yes
hw.sensors.orientation=yes
hw.sensors.proximity=yes
hw.trackBall=no
image.sysdir.1=system-images/android-27/default/arm64-v8a/
runtime.network.latency=none
runtime.network.speed=full
sdcard.size=512M
showDeviceFrame=no
skin.dynamic=yes
skin.name=1480x320
skin.path=_no_skin
skin.path.backup=/home/dangelo/Android/Sdk/skins/tv_1080p
tag.display=Default Android System Image
tag.id=default
vm.heapSize=48
Spoiler: Partition data
$ cat /proc/partitions
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
1 4 8192 ram4
1 5 8192 ram5
1 6 8192 ram6
1 7 8192 ram7
1 8 8192 ram8
1 9 8192 ram9
1 10 8192 ram10
1 11 8192 ram11
1 12 8192 ram12
1 13 8192 ram13
1 14 8192 ram14
1 15 8192 ram15
254 0 1572864 zram0
179 0 30670848 mmcblk0
179 1 5120 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 35840 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 6144 mmcblk0p5
179 6 6144 mmcblk0p6
179 7 1024 mmcblk0p7
259 0 1024 mmcblk0p8
259 1 1024 mmcblk0p9
259 2 1024 mmcblk0p10
259 3 4096 mmcblk0p11
259 4 1024 mmcblk0p12
259 5 1024 mmcblk0p13
259 6 1024 mmcblk0p14
259 7 1024 mmcblk0p15
259 8 1024 mmcblk0p16
259 9 1024 mmcblk0p17
259 10 1024 mmcblk0p18
259 11 1024 mmcblk0p19
259 12 10240 mmcblk0p20
259 13 2048 mmcblk0p21
259 14 25600 mmcblk0p22
259 15 1024 mmcblk0p23
259 16 10240 mmcblk0p24
259 17 20480 mmcblk0p25
259 18 1024 mmcblk0p26
259 19 35840 mmcblk0p27
259 20 2867200 mmcblk0p28
259 21 153600 mmcblk0p29
259 22 409600 mmcblk0p30
259 23 1024 mmcblk0p31
259 24 1024 mmcblk0p32
259 25 27059183 mmcblk0p33
179 24 4096 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
253 0 27059167 dm-0
output using the ls command with arguments that I forgot
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 boot -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 cache -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 fbootlogo -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 gpsbd -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 gpsgl -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_deltanv -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_fixnv1 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_fixnv2 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_gdsp -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_ldsp -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_modem -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_runtimenv1 -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_runtimenv2 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 logo -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 misc -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 miscdata -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 pm_sys -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 prodnv -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 recovery -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 sml -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 sml_bak -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 system -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 trustos -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 trustos_bak -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 uboot -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 uboot_bak -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 uboot_log -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 userdata -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vbmeta -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vbmeta_bak -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vendor -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 wcnmodem -> /dev/block/mmcblk0p20
Spoiler: Device information
Device name: Junsun A104
Android: 8.1. Oreo API level 27
CPU:
64bit
ARM64-V8A
Spreadtrum SC9832e
Memory: 2GB
Kernel architecture: aarch64
Kernel version: 4.4.83-00001-g213b4e3
dangelob said:
Hi,
This is my first project that I'm currently working on.
I recently bought a android dashcam which UI I would like to change based on my personal preferences. Unfortunately I'm struggling to setup an environment where I can test the changes I make before replacing the original UI on the device itself. I identified the SystemUI.apk to be the place where the manufacturer made customization. I will be using the SystemUI.apk built from AOSP and making my changes based on that. I had no luck trying to decompile the SystemUI.apk in a way that I could build it again.
I was thinking that I could use an android emulator to use the same ROM as the device itself. The manufacturer did not provide any support in providing stock firmware images in any way. So I used the following steps to 'export' the firmware.
1. Unlocking the bootloader using the Identifier Token so I can flash images using fastboot. TWRP was not an option here because I could not find any images for my device nor could I port an TWRP image myself.
2. Enable ADB debugging over usb
3. Enable ADB root privileges using the password: 2846 (if i remember correctly)
4. Use ADB remount and ADB root to gain privileges over the partitions
5. Gain information on partition data
6. Use ADB pull to export images based on partitions
After following the above steps the next thing was to import the images into an emulator. I used the following steps to do this:
1. Create a new device within Android Studio that has the same screen size and os.
2. Replace the system.img, ramdisk.img with the exported variants in ~/Android/Sdk/../arm64-v8a
3. Turn off EncryptUserData inside advancedFeatures.ini to prevent errors like partitions that are unable to encrypt
4. Use the command below to start the emulator
Code:
~/Android/Sdk/emulator/emulator -avd Junsun_A104_API_27 -verbose -show-kernel
5. After running the emulator I receive the error below and the screen of the emulator stays black.
Code:
Please append a correct "root=" boot option; here are the available partitions:
fe00 2867200 vda driver: virtio_blk
fe10 67584 vdb driver: virtio_blk
fe20 819200 vdc driver: virtio_blk
fe30 409600 vdd driver: virtio_blk
fe40 524288 vde driver: virtio_blk
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
My assumption is that the emulator does not contain the same partition model used on the device. I could try to export each partition but I wouldn't know how to let the emulator know how to use these partitions. I tried to export the kernel and import it inside the emulator without luck. I did not receive any errors that way.
So my main question is:
- Is there any way I can import the device's rom inside an android emulator
Spoiler: Emulator Config
AvdId=Junsun_A104_API_27
PlayStore.enabled=false
abi.type=arm64-v8a
avd.ini.displayname=Junsun A104 API 27
avd.ini.encoding=UTF-8
disk.dataPartition.size=800M
fastboot.chosenSnapshotFile=
fastboot.forceChosenSnapshotBoot=no
fastboot.forceColdBoot=no
fastboot.forceFastBoot=yes
hw.accelerometer=yes
hw.arc=false
hw.audioInput=yes
hw.battery=yes
hw.camera.back=virtualscene
hw.camera.front=emulated
hw.cpu.arch=arm64
hw.cpu.ncore=4
hw.dPad=no
hw.device.hash2=MD5:7834f5e80eb849ceb46ce01cd4c704f7
hw.device.manufacturer=User
hw.device.name=Junsun A104
hw.gps=yes
hw.gpu.enabled=no
hw.gpu.mode=off
hw.initialOrientation=landscape
hw.keyboard=yes
hw.lcd.density=120
hw.lcd.height=320
hw.lcd.width=1480
hw.mainKeys=no
hw.ramSize=2560
hw.sdCard=yes
hw.sensors.orientation=yes
hw.sensors.proximity=yes
hw.trackBall=no
image.sysdir.1=system-images/android-27/default/arm64-v8a/
runtime.network.latency=none
runtime.network.speed=full
sdcard.size=512M
showDeviceFrame=no
skin.dynamic=yes
skin.name=1480x320
skin.path=_no_skin
skin.path.backup=/home/dangelo/Android/Sdk/skins/tv_1080p
tag.display=Default Android System Image
tag.id=default
vm.heapSize=48
Spoiler: Partition data
$ cat /proc/partitions
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
1 4 8192 ram4
1 5 8192 ram5
1 6 8192 ram6
1 7 8192 ram7
1 8 8192 ram8
1 9 8192 ram9
1 10 8192 ram10
1 11 8192 ram11
1 12 8192 ram12
1 13 8192 ram13
1 14 8192 ram14
1 15 8192 ram15
254 0 1572864 zram0
179 0 30670848 mmcblk0
179 1 5120 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 35840 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 6144 mmcblk0p5
179 6 6144 mmcblk0p6
179 7 1024 mmcblk0p7
259 0 1024 mmcblk0p8
259 1 1024 mmcblk0p9
259 2 1024 mmcblk0p10
259 3 4096 mmcblk0p11
259 4 1024 mmcblk0p12
259 5 1024 mmcblk0p13
259 6 1024 mmcblk0p14
259 7 1024 mmcblk0p15
259 8 1024 mmcblk0p16
259 9 1024 mmcblk0p17
259 10 1024 mmcblk0p18
259 11 1024 mmcblk0p19
259 12 10240 mmcblk0p20
259 13 2048 mmcblk0p21
259 14 25600 mmcblk0p22
259 15 1024 mmcblk0p23
259 16 10240 mmcblk0p24
259 17 20480 mmcblk0p25
259 18 1024 mmcblk0p26
259 19 35840 mmcblk0p27
259 20 2867200 mmcblk0p28
259 21 153600 mmcblk0p29
259 22 409600 mmcblk0p30
259 23 1024 mmcblk0p31
259 24 1024 mmcblk0p32
259 25 27059183 mmcblk0p33
179 24 4096 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
253 0 27059167 dm-0
output using the ls command with arguments that I forgot
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 boot -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 cache -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 fbootlogo -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 gpsbd -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 gpsgl -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_deltanv -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_fixnv1 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_fixnv2 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_gdsp -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_ldsp -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_modem -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_runtimenv1 -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_runtimenv2 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 logo -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 misc -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 miscdata -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 pm_sys -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 prodnv -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 recovery -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 sml -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 sml_bak -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 system -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 trustos -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 trustos_bak -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 uboot -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 uboot_bak -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 uboot_log -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 userdata -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vbmeta -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vbmeta_bak -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vendor -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 wcnmodem -> /dev/block/mmcblk0p20
Spoiler: Device information
Device name: Junsun A104
Android: 8.1. Oreo API level 27
CPU:
64bit
ARM64-V8A
Spreadtrum SC9832e
Memory: 2GB
Kernel architecture: aarch64
Kernel version: 4.4.83-00001-g213b4e3
Click to expand...
Click to collapse
All you should need is the system.img and the kernel, then extract the system.img untill you find the /system/app and/or the /system/priv-app(whichever folder contains your UI.apk), extract a copy of the UI.apk. Then use APKtool to remove the signature on the apk file then decompile the apk file then make your modifications then recompile and re-sign the apk file. Then place the newly modified UI.apk in the system folder where you extracted it from(overwrite/delete the old version of the apk). Then compress all the files back into the system.img like it was originally and then try to use your newly modified system.img in your emulator.
Try using Bluestacks or one of the other leading android emulators instead of using Android Studio.