So Retroid recently came out with the RP3+.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-It runs Android 11
-Has an option in developer settings for OEM unlocking
-Easy access to adb and fastboot
AND you can run shell scripts as ROOT from within the settings.
For now I'm simply trying to make a backup boot.img
The typical command would be:
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
But the file does not exist.
Ive been able to run some basic scripts successfully from the run shell script as root option leading to a complete file list of everything on the system.
Here is a list of all the files in ./dev/block/
./dev/block./dev/block/loop27./dev/block/dm-13./dev/block/dm-12./dev/blo - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
Any help with rooting this device or simply backing up the system would be greatly appreciated.
ApatheticEuphoria said:
So Retroid recently came out with the RP3+.
-It runs Android 11
-Has an option in developer settings for OEM unlocking
-Easy access to adb and fastboot
AND you can run shell scripts as ROOT from within the settings.
For now I'm simply trying to make a backup boot.img
The typical command would be:
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
But the file does not exist.
Ive been able to run some basic scripts successfully from the run shell script as root option leading to a complete file list of everything on the system.
Here is a list of all the files in ./dev/block/
./dev/block./dev/block/loop27./dev/block/dm-13./dev/block/dm-12./dev/blo - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
Any help with rooting this device or simply backing up the system would be greatly appreciated.
Click to expand...
Click to collapse
It's always difficult when the firmware isn't readily available for download. But it sounds like you're on the right track - dump the boot image, patch in Magisk, unlock the bootloader, and flash the patched image for root.
Try this guide, it sounds like you just need to establish where the boot partition is mounted
V0latyle said:
It's always difficult when the firmware isn't readily available for download. But it sounds like you're on the right track - dump the boot image, patch in Magisk, unlock the bootloader, and flash the patched image for root.
Try this guide, it sounds like you just need to establish where the boot partition is mounted
Click to expand...
Click to collapse
Thank you very much for the guide. It is indeed a start.
Here are the results from Ways #1,2:
Code:
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
7 0 888 loop0
7 1 24676 loop1
7 2 84832 loop2
7 3 5152 loop3
7 4 111128 loop4
7 5 1904 loop5
7 6 888 loop6
7 7 24676 loop7
7 8 6564 loop8
7 9 8608 loop9
7 10 5020 loop10
7 11 736 loop11
7 12 740 loop12
7 13 19040 loop13
7 14 18372 loop14
7 15 3784 loop15
254 0 2222624 zram0
259 0 64 pmem0
179 0 122142720 mmcblk0
179 1 10240 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 6144 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 1024 mmcblk0p7
259 1 1024 mmcblk0p8
259 2 1024 mmcblk0p9
259 3 4096 mmcblk0p10
259 4 8192 mmcblk0p11
259 5 8192 mmcblk0p12
259 6 2048 mmcblk0p13
259 7 2048 mmcblk0p14
259 8 2048 mmcblk0p15
259 9 2048 mmcblk0p16
259 10 2048 mmcblk0p17
259 11 2048 mmcblk0p18
259 12 1024 mmcblk0p19
259 13 1024 mmcblk0p20
259 14 10240 mmcblk0p21
259 15 10240 mmcblk0p22
259 16 2048 mmcblk0p23
259 17 25600 mmcblk0p24
259 18 25600 mmcblk0p25
259 19 1024 mmcblk0p26
259 20 1024 mmcblk0p27
259 21 10240 mmcblk0p28
259 22 10240 mmcblk0p29
259 23 20480 mmcblk0p30
259 24 20480 mmcblk0p31
259 25 6144 mmcblk0p32
259 26 6144 mmcblk0p33
259 27 1024 mmcblk0p34
259 28 1024 mmcblk0p35
259 29 1024 mmcblk0p36
259 30 1024 mmcblk0p37
259 31 1024 mmcblk0p38
259 32 1024 mmcblk0p39
259 33 10240 mmcblk0p40
259 34 10240 mmcblk0p41
259 35 65536 mmcblk0p42
259 36 65536 mmcblk0p43
259 37 102400 mmcblk0p44
259 38 102400 mmcblk0p45
259 39 8192 mmcblk0p46
259 40 8192 mmcblk0p47
259 41 8192 mmcblk0p48
259 42 8192 mmcblk0p49
259 43 6500352 mmcblk0p50
259 44 102400 mmcblk0p51
259 45 76800 mmcblk0p52
259 46 76800 mmcblk0p53
259 47 25600 mmcblk0p54
259 48 25600 mmcblk0p55
259 49 1024 mmcblk0p56
259 50 1024 mmcblk0p57
259 51 16384 mmcblk0p58
259 52 10240 mmcblk0p59
259 53 1024 mmcblk0p60
259 54 1024 mmcblk0p61
259 55 1024 mmcblk0p62
259 56 1024 mmcblk0p63
259 57 1024 mmcblk0p64
259 58 1024 mmcblk0p65
259 59 1024 mmcblk0p66
259 60 1024 mmcblk0p67
259 61 1024 mmcblk0p68
259 62 1024 mmcblk0p69
259 63 1024 mmcblk0p70
259 64 1024 mmcblk0p71
259 65 8192 mmcblk0p72
259 66 8192 mmcblk0p73
259 67 16384 mmcblk0p74
259 68 16384 mmcblk0p75
259 69 114635759 mmcblk0p76
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
179 24 125173760 mmcblk1
179 25 125157376 mmcblk1p1
253 0 1266204 dm-0
253 1 370464 dm-1
253 2 1733700 dm-2
253 3 595004 dm-3
253 4 1160912 dm-4
253 5 113704 dm-5
253 6 1244960 dm-6
253 7 1246136 dm-7
253 8 364532 dm-8
253 9 1706256 dm-9
253 10 585532 dm-10
7 16 6084 loop16
7 17 84832 loop17
7 18 10184 loop18
7 19 5152 loop19
7 20 264 loop20
7 21 7948 loop21
7 22 4732 loop22
7 23 2812 loop23
7 24 111128 loop24
7 25 1904 loop25
7 26 3732 loop26
253 11 75508 dm-11
253 12 25116 dm-12
253 13 114635756 dm-13
7 27 153600 loop27
Code:
total 0
drwxr-xr-x 2 root root 1560 2023-01-11 05:33 .
drwxr-xr-x 3 root root 1640 2023-01-11 05:33 ..
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 avbmeta_rs_a -> /dev/block/mmcblk0p70
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 avbmeta_rs_b -> /dev/block/mmcblk0p71
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 boot_a -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 boot_b -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 cache -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 common_rs1_a -> /dev/block/mmcblk0p72
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 common_rs1_b -> /dev/block/mmcblk0p73
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 common_rs2_a -> /dev/block/mmcblk0p74
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 common_rs2_b -> /dev/block/mmcblk0p75
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 dtb_a -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 dtb_b -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 dtbo_a -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 dtbo_b -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 fbootlogo -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 gnssmodem_a -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 gnssmodem_b -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 hypervsior_a -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 hypervsior_b -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_agdsp_a -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_agdsp_b -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_cdsp_a -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_cdsp_b -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_deltanv_a -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_deltanv_b -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_fixnv1_a -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_fixnv1_b -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_fixnv2_a -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_fixnv2_b -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_gdsp_a -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_gdsp_b -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_ldsp_a -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_ldsp_b -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_modem_a -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_modem_b -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_runtimenv1 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 l_runtimenv2 -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 logo -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 metadata -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 20 2023-01-11 05:33 misc -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2023-01-11 05:33 miscdata -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 odmko_a -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 odmko_b -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 persist -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 pm_sys_a -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 pm_sys_b -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 20 2023-01-11 05:33 prodnv -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2023-01-11 05:33 sml_a -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2023-01-11 05:33 sml_b -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 socko_a -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 socko_b -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 super -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 sysdumpdb -> /dev/block/mmcblk0p59
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 teecfg_a -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 teecfg_b -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 20 2023-01-11 05:33 trustos_a -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2023-01-11 05:33 trustos_b -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2023-01-11 05:33 uboot_a -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2023-01-11 05:33 uboot_b -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 uboot_log -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 userdata -> /dev/block/mmcblk0p76
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_a -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_b -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_odm_a -> /dev/block/mmcblk0p68
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_odm_b -> /dev/block/mmcblk0p69
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_product_a -> /dev/block/mmcblk0p66
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_product_b -> /dev/block/mmcblk0p67
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_system_a -> /dev/block/mmcblk0p60
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_system_b -> /dev/block/mmcblk0p61
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_system_ext_a -> /dev/block/mmcblk0p64
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_system_ext_b -> /dev/block/mmcblk0p65
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_vendor_a -> /dev/block/mmcblk0p62
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vbmeta_vendor_b -> /dev/block/mmcblk0p63
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vendor_boot_a -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 vendor_boot_b -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 wcnmodem_a -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2023-01-11 05:33 wcnmodem_b -> /dev/block/mmcblk0p22
ApatheticEuphoria said:
Thank you. Its a start. Tried Way #1 and got some info. Way #2 isnt working (Removed the color code*)
Code:
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
7 0 888 loop0
7 1 24676 loop1
7 2 84832 loop2
7 3 5152 loop3
7 4 111128 loop4
7 5 1904 loop5
7 6 888 loop6
7 7 24676 loop7
7 8 6564 loop8
7 9 8608 loop9
7 10 5020 loop10
7 11 736 loop11
7 12 740 loop12
7 13 19040 loop13
7 14 18372 loop14
7 15 3784 loop15
254 0 2222624 zram0
259 0 64 pmem0
179 0 122142720 mmcblk0
179 1 10240 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 6144 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 1024 mmcblk0p7
259 1 1024 mmcblk0p8
259 2 1024 mmcblk0p9
259 3 4096 mmcblk0p10
259 4 8192 mmcblk0p11
259 5 8192 mmcblk0p12
259 6 2048 mmcblk0p13
259 7 2048 mmcblk0p14
259 8 2048 mmcblk0p15
259 9 2048 mmcblk0p16
259 10 2048 mmcblk0p17
259 11 2048 mmcblk0p18
259 12 1024 mmcblk0p19
259 13 1024 mmcblk0p20
259 14 10240 mmcblk0p21
259 15 10240 mmcblk0p22
259 16 2048 mmcblk0p23
259 17 25600 mmcblk0p24
259 18 25600 mmcblk0p25
259 19 1024 mmcblk0p26
259 20 1024 mmcblk0p27
259 21 10240 mmcblk0p28
259 22 10240 mmcblk0p29
259 23 20480 mmcblk0p30
259 24 20480 mmcblk0p31
259 25 6144 mmcblk0p32
259 26 6144 mmcblk0p33
259 27 1024 mmcblk0p34
259 28 1024 mmcblk0p35
259 29 1024 mmcblk0p36
259 30 1024 mmcblk0p37
259 31 1024 mmcblk0p38
259 32 1024 mmcblk0p39
259 33 10240 mmcblk0p40
259 34 10240 mmcblk0p41
259 35 65536 mmcblk0p42
259 36 65536 mmcblk0p43
259 37 102400 mmcblk0p44
259 38 102400 mmcblk0p45
259 39 8192 mmcblk0p46
259 40 8192 mmcblk0p47
259 41 8192 mmcblk0p48
259 42 8192 mmcblk0p49
259 43 6500352 mmcblk0p50
259 44 102400 mmcblk0p51
259 45 76800 mmcblk0p52
259 46 76800 mmcblk0p53
259 47 25600 mmcblk0p54
259 48 25600 mmcblk0p55
259 49 1024 mmcblk0p56
259 50 1024 mmcblk0p57
259 51 16384 mmcblk0p58
259 52 10240 mmcblk0p59
259 53 1024 mmcblk0p60
259 54 1024 mmcblk0p61
259 55 1024 mmcblk0p62
259 56 1024 mmcblk0p63
259 57 1024 mmcblk0p64
259 58 1024 mmcblk0p65
259 59 1024 mmcblk0p66
259 60 1024 mmcblk0p67
259 61 1024 mmcblk0p68
259 62 1024 mmcblk0p69
259 63 1024 mmcblk0p70
259 64 1024 mmcblk0p71
259 65 8192 mmcblk0p72
259 66 8192 mmcblk0p73
259 67 16384 mmcblk0p74
259 68 16384 mmcblk0p75
259 69 114635759 mmcblk0p76
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
179 24 125173760 mmcblk1
179 25 125157376 mmcblk1p1
253 0 1266204 dm-0
253 1 370464 dm-1
253 2 1733700 dm-2
253 3 595004 dm-3
253 4 1160912 dm-4
253 5 113704 dm-5
253 6 1244960 dm-6
253 7 1246136 dm-7
253 8 364532 dm-8
253 9 1706256 dm-9
253 10 585532 dm-10
7 16 6084 loop16
7 17 84832 loop17
7 18 10184 loop18
7 19 5152 loop19
7 20 264 loop20
7 21 7948 loop21
7 22 4732 loop22
7 23 2812 loop23
7 24 111128 loop24
7 25 1904 loop25
7 26 3732 loop26
253 11 75508 dm-11
253 12 25116 dm-12
253 13 114635756 dm-13
7 27 153600 loop27
Click to expand...
Click to collapse
So you just need to figure out which partition is /boot. There's a way to do this but I forget how.
I did find this on Stack Exchange:
Run find /dev -name 'by-name' 2>/dev/null to find the by-name directory. It should list one, though if there are a couple, it shouldn't be a problem and both should work.
Take the directory name and run ls -la <by-name-directory> (replacing the place holder with the actual directory name)
Find the name of the partition you are interested in - if you want just the kernel, the name is boot, or if your device has multiple slots, it is probably boot_a - and record the physical partition path listed for it. It should be something like /dev/block/mmcblk0p22 (this is on my Mi A1 device - if you have a different one, the number after "p" will be different and possibly even the number before "p").
Click to expand...
Click to collapse
There's also this guide. At least you're able to run shell as root, that's a huge advantage.
V0latyle said:
So you just need to figure out which partition is /boot. There's a way to do this but I forget how.
I did find this on Stack Exchange:
There's also this guide. At least you're able to run shell as root, that's a huge advantage.
Click to expand...
Click to collapse
Right?! I seen that as an option and just had to see what I could do with it.
So to see the partitions I put in
Code:
ls -al /dev/block/platform/soc/soc:ap-apb/71400000.sdio/by-name/ > /sdcard/info.txt
Saved as info.sh and ran from the run root script option.
(The output file will be stored in Internal Storage for whatever reason.)
To backup the boot images I put in
Code:
dd if=/dev/block/mmcblk0p42 of=/sdcard/boot_a.img
dd if=/dev/block/mmcblk0p43 of=/sdcard/boot_b.img
and again saved as getboot.sh and ran from the setting.
So according to this guide:
Patch Stock Boot Image via Magisk and Flash it using Fastboot
If you want to root your Android device then you can check out how to Patch Stock Boot Image via Magisk and Flash it using Fastboot method.
www.getdroidtips.com
It seems to have an A/B partition.
Ive backed up my boot.img files.
Patched them with Magisk.
They're ready to flash.
Code:
sending 'boot_a' (65536 KB)...
OKAY [ 1.478s]
writing 'boot_a'...
FAILED (remote: Flashing Lock Flag is locked. Please unlock it first!)
finished. total time: 1.498s
As expected.
To unlock Bootloader, I am hesitant to try anything yet.
With help from some kind and knowledgeable members of the official Discord I got the bootloader unlocked.
However they advised me NOT to flash the magisk patched boot.img until it is "resigned with avbtool to match what the keys are in vbmeta."
They said if I try and flash as is I will likely brick or get stuck in bootloop.
So I'll need help with that part. No idea how to do that.
Here's what I did to get the bootloader unlocked:
Back up Internal Storage (User data will be erased).
Install the drivers from here https://androiddatahost.com/dsa6h
Boot the RP3+ into the Bootloader by powering off the device, Pressing and holding the PWR and VOL + buttons until it boots to recovery and then select reboot to bootloader from the recovery options.
Connect the device to the PC and go to https://turtleletortue.github.io/subut-rehost/ on Google Chrome.
Click Connect.
Click "fastboot gadget" and connect.
Click Unlock.
On the device there will be a warning "Warning: Unlock device may erase user data. Press volume down button to confirm that. Press volume up button to cancel."
Press volume down.
Wait for it to complete.
Then reboot by pressing and holding PWR and Vol down.
There is a warning everytime I reboot but it goes away shortly and boots normally.
ApatheticEuphoria said:
With help from some kind and knowledgeable members of the official Discord I got the bootloader unlocked.
However they advised me NOT to flash the magisk patched boot.img until it is "resigned with avbtool to match what the keys are in vbmeta."
They said if I try and flash as is I will likely brick or get stuck in bootloop.
So I'll need help with that part. No idea how to do that.
Here's what I did to get the bootloader unlocked:
Back up Internal Storage (User data will be erased).
Install the drivers from here https://androiddatahost.com/dsa6h
Boot the RP3+ into the Bootloader by powering off the device, Pressing and holding the PWR and VOL + buttons until it boots to recovery and then select reboot to bootloader from the recovery options.
Connect the device to the PC and go to https://turtleletortue.github.io/subut-rehost/ on Google Chrome.
Click Connect.
Click "fastboot gadget" and connect.
Click Unlock.
On the device there will be a warning "Warning: Unlock device may erase user data. Press volume down button to confirm that. Press volume up button to cancel."
Press volume down.
Wait for it to complete.
Then reboot by pressing and holding PWR and Vol down.
There is a warning everytime I reboot but it goes away shortly and boots normally.
Click to expand...
Click to collapse
I have the regular RP3. Every time I try going into bootloader, it directs me straight to the RP3 boot and it stays that way till I press Boot again. Nothing happens.
A video on how to do it would be better.
If anyone knowledgeable could help me get avbtool installed properly on either Linux or Windows , it should be simple to get the keys from the vbmeta images and resign my patched boot images. I just need help with that part and I'll be rooted.
ApatheticEuphoria said:
If anyone knowledgeable could help me get avbtool installed properly on either Linux or Windows , it should be simple to get the keys from the vbmeta images and resign my patched boot images. I just need help with that part and I'll be rooted.
Click to expand...
Click to collapse
Do you think it is possible, by unlocking the boot, to install a custom firmware on the retroid pocket 3+ ? (JelOS, AmberElec, Batocera, etc.) ?
gremen said:
I have the regular RP3. Every time I try going into bootloader, it directs me straight to the RP3 boot and it stays that way till I press Boot again. Nothing happens.
A video on how to do it would be better.
Click to expand...
Click to collapse
I'm Sorry. I don't own an RP3 so the process may be different.
SoPlissken77 said:
Do you think it is possible, by unlocking the boot, to install a custom firmware on the retroid pocket 3+ ? (JelOS, AmberElec, Batocera, etc.) ?
Click to expand...
Click to collapse
Yes, Definitely.
----
Slowly trying to get avbtool working on my own. (Im honestly not very good at this stuff).
For now I'll share the code for extracting the vbmeta images:
dd if=/dev/block/mmcblk0p56 of=/sdcard/vbmeta_a.img
dd if=/dev/block/mmcblk0p57 of=/sdcard/vbmeta_b.img
Saved as getvbmeta.sh and ran from the run root script option.
(The output files will be stored in Internal Storage)
So I've been collaborating with OP on Discord and made a set of scripts to do the dirty work for me... I had to fix avbtool and make a script to extract the vbmeta keys automatically... as well as add a neat little wrapper!
They wanted me to make a full writeup but tbh I'm too lazy so I made a 1-click solution instead!... Now I'd say THIS is a worthy Valentines day gift!
GitHub - skompc/retroid-pocket-3-plus-autoroot: A set of python scripts that will autosign modified vbmeta and boot images for RP3+
A set of python scripts that will autosign modified vbmeta and boot images for RP3+ - GitHub - skompc/retroid-pocket-3-plus-autoroot: A set of python scripts that will autosign modified vbmeta and ...
github.com
ApatheticEuphoria said:
I'm Sorry. I don't own an RP3 so the process may be different.
Yes, Definitely.
----
Slowly trying to get avbtool working on my own. (Im honestly not very good at this stuff).
For now I'll share the code for extracting the vbmeta images:
dd if=/dev/block/mmcblk0p56 of=/sdcard/vbmeta_a.img
dd if=/dev/block/mmcblk0p57 of=/sdcard/vbmeta_b.img
Saved as getvbmeta.sh and ran from the run root script option.
(The output files will be stored in Internal Storage)
Click to expand...
Click to collapse
I really like the RP3+ but I find Android unsuitable for retrogaming. On the Retroid discord or the Reddit, there are many requests for a linux port or a dualboot
UPDATE: There is now a successful public root available for the RP3+
GitHub - skompc/retroid-pocket-3-plus-autoroot: A set of python scripts that will autosign modified vbmeta and boot images for RP3+
A set of python scripts that will autosign modified vbmeta and boot images for RP3+ - GitHub - skompc/retroid-pocket-3-plus-autoroot: A set of python scripts that will autosign modified vbmeta and ...
github.com
Make backups and use at your own risk.
ApatheticEuphoria said:
UPDATE: There is now a successful public root available for the RP3+
GitHub - skompc/retroid-pocket-3-plus-autoroot: A set of python scripts that will autosign modified vbmeta and boot images for RP3+
A set of python scripts that will autosign modified vbmeta and boot images for RP3+ - GitHub - skompc/retroid-pocket-3-plus-autoroot: A set of python scripts that will autosign modified vbmeta and ...
github.com
Make backups and use at your own risk.
Click to expand...
Click to collapse
Can you help me with the backups. Been trying to figure it out but having a tough time because I'm not great at linux
Irishdude5280 said:
Can you help me with the backups. Been trying to figure it out but having a tough time because I'm not great at linux
Click to expand...
Click to collapse
Try this:
[GUIDE] How to do a FULL low level backup of your Android Device
This Guide is simple and is straight the point, but is helpful and may come in handy for those who experience a hard-bricked phone or missing file in your phone like I did. Basically, nandroid is not a FULL backup, it only backs up your system...
forum.xda-developers.com
Rather than a terminal emulator you just save the command as backup.sh and run from within the handheld's run script as root setting.
ApatheticEuphoria said:
Try this:
[GUIDE] How to do a FULL low level backup of your Android Device
This Guide is simple and is straight the point, but is helpful and may come in handy for those who experience a hard-bricked phone or missing file in your phone like I did. Basically, nandroid is not a FULL backup, it only backs up your system...
forum.xda-developers.com
Rather than a terminal emulator you just save the command as backup.sh and run from within the handheld's run script as root setting.
Click to expand...
Click to collapse
I will give this a shot! Thank you I found all of the info you put here very helpful!
So I took a full system backup to my SD card using
dd if=/dev/block/mmcblk0 of=/mnt/media_rw/D873-812D/mmcblk0.img
saved as backupSD.sh
I am assuming that the mnt point "/mnt/media_rw/D873-812D/" is just for my SD but not sure on that, I found it by running OP's info.sh with the card mounted.
EDIT: thought about it and I actually might have found it by running mount command in termux. Been a long day sorry.
It made a .img of 125 GB, which seems to be a block level backup of the entire internal storage like I wanted. I extracted it with 7zip and see individual .img files for each of the partitions shown in the info.txt
Trying to extract those I get
Cannot open file as archive
Tried mounting them in WSL with
sudo mount -t drvfs V: /mnt/v To mount my windows drive where image is
sudo mount -o ro,loop /mnt/v/mmcblk0.img /mnt/android
mount: /mnt/android: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
It honestly looks like it worked perfectly im just trying to figure out forsure i have a good backup before going forward. that is why I was trying to mount it somehow.
also ran OP's commands for backing up boot a and b and vbmeta a and b
So I am ready to try and root it just want some confidence in my backups first. Any thoughts would be appreciated.
Irishdude5280 said:
So I took a full system backup to my SD card using
dd if=/dev/block/mmcblk0 of=/mnt/media_rw/D873-812D/mmcblk0.img
saved as backupSD.sh
I am assuming that the mnt point "/mnt/media_rw/D873-812D/" is just for my SD but not sure on that, I found it by running OP's info.sh with the card mounted.
EDIT: thought about it and I actually might have found it by running mount command in termux. Been a long day sorry.
It made a .img of 125 GB, which seems to be a block level backup of the entire internal storage like I wanted. I extracted it with 7zip and see individual .img files for each of the partitions shown in the info.txt
Trying to extract those I get
Cannot open file as archive
Tried mounting them in WSL with
sudo mount -t drvfs V: /mnt/v To mount my windows drive where image is
sudo mount -o ro,loop /mnt/v/mmcblk0.img /mnt/android
mount: /mnt/android: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
It honestly looks like it worked perfectly im just trying to figure out forsure i have a good backup before going forward. that is why I was trying to mount it somehow.
also ran OP's commands for backing up boot a and b and vbmeta a and b
So I am ready to try and root it just want some confidence in my backups first. Any thoughts would be appreciated.
Click to expand...
Click to collapse
Interesting. Thank you. I was wondering why it was saving files to internal storage and not the SD card. That seems to be the proper way to do it. As for why you can't extract the individual partitions, maybe it has something to do with 7zip, have you tried different software to explore the .img files? Maybe extract the main .img and then the partitions with something like Power ISO or WinRAR.
I tried your suggestion and PowerISO apparently likes adware so my AV blocked it. I threw the exe in Virus Total and it too says its full of Adware. WinRar by memory is full of adds for itself, tried it anyways with no luck.
I then found this https://www.sleuthkit.org/sleuthkit/ which is basically forensic tools for examining DD images from android devices. I was able to determine with those tools that the data is in fact there, but encrypted.
In theory a restore should still work if restored to the same device so I feel a little bit better, but still not sure i have a rock solid backup. Not even sure how I could verify at this point considering its encrypted
So did you successfully root your device? I want to try it but I am nervous without knowing if i can restore. One thing I wanted to clear up on too is with what I have read about devices with the a/b partitions, my understanding is I only need to patch 1 set of boot and vbmeta images right? Then I just flash the patched images to both the a and b partitions?
Full Root Guide for Retroid Pocket 3+
USE AT YOUR OWN RISK!!! I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE!!! ALWAYS ENSURE YOU HAVE A BACKUP!!!
-----------------
1. Doing a full partition backup to your SD Card. (You'll need 128gb or greater)
To get the path to your SD enter the following command in a text editor and save as SDNAME.sh
Code:
ls /mnt/media_rw/ > /sdcard/SDNAME.txt
To run the script, copy the .sh file to your RP3+, go to the Settings of your device, then Handheld Settings > Advanced > Run Script as Root. Navigate to the .sh file and run it.
The SDNAME.txt will be found on Internal Storage.
The output should be in this format: ####-####
Next enter the following command in a text editor and save as BACKUP.sh
Code:
dd if=/dev/block/mmcblk0 of=/mnt/media_rw/####-####/backup.img
Replace ####-#### with the result from SDNAME.txt
To run the script, copy the .sh file to your RP3+, go to the Settings of your device, then Handheld Settings > Advanced > Run Script as Root. Navigate to the .sh file and run it.
The recovery image will be saved as backup.img on your SD Card and will include ALL partitions of the RP3+.
-----------------
2. Unlocking the bootloader.
On your Windows PC go to:
https://androiddatahost.com/wp-content/uploads/SPD_Driver_R4.20.4201.zip
Download and extract the zip file and Install the driver specific to your OS.
Power off your RP3+.
Press and hold the POWER and VOLUME UP buttons until it boots to recovery mode.
Select reboot to bootloader from the recovery options.
Connect the device to the PC and go to:
Spreadtrum / Unisoc Bootloader Unlock Tool
on Google Chrome.
Click Connect.
Click "fastboot gadget" and connect.
Click Unlock.
On the device there will be a warning:
"Warning: Unlock device may erase user data. Press volume down button to confirm that. Press volume up button to cancel."
Press volume down.
Wait for it to complete. It may take awhile so be patient and do not interrupt the process*
When its complete reboot by pressing and holding POWER and VOLUME DOWN.
There is a warning everytime you reboot now but it goes away shortly and boots normally.
-----------------
3. Dumping your boot_a and vbmeta_a partitions.
Enter the following commands in a text editor and save as getbootandvbmeta.sh
Code:
dd if=/dev/block/mmcblk0p42 of=/sdcard/boot_a.img
dd if=/dev/block/mmcblk0p56 of=/sdcard/vbmeta_a.img
To run the script, copy the .sh file to your RP3+, go to the Settings of your device, then Handheld Settings > Advanced > Run Script as Root. Navigate to the .sh file and run it.
The boot_a.img and vbmeta_a.img files will be stored on Internal Storage.
-----------------
4. Patching the boot_a.img file with Magisk.
Go to:
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Scroll down to Assets and download, then install the latest Magisk.apk
Open Magisk.
Tap "Install" Next to Magisk at the top.
Tap "Select and Patch a File"
Navigate to your boot_a.img file and tap it.
Tap "LET'S GO -->"
The patched boot_a.img file will have an output similar to magisk_patched-26000_Lf8IC.img and will be stored in the Download directory on Internal Storage.
-----------------
5. Resigning the keys for boot_a.img and vbmeta_a.img
Boot up a 64-bit Linux OS.
Open a terminal and enter:
Code:
git clone https://github.com/skompc/retroid-pocket-3-plus-autoroot
Navigate to the downloaded retroid-pocket-3-plus-autoroot folder.
Right click patch.sh and go to properties.
Click Permissions.
Change Access to Read & Write for all.
Tick the "Allow this file to run as a program" box
Click Close.
Open a browser and go to:
https://repo.anaconda.com/archive/Anaconda3-2023.03-Linux-x86_64.sh
To download Anaconda3.
Go to your downloads folder, Right click Anaconda3-2023.03-Linux-x86_64.sh and click properties.
Click Permissions.
Change Access to Read & Write for all.
Tick the "Allow this file to run as a program" box
Click Close.
Right click in the Download folder and Click "Open Terminal Here".
Drag Anaconda3-2023.03-Linux-x86_64.sh into the terminal and press Enter.
Press Enter to review the license agreement. Then press and hold Enter to scroll.
When you see ( END ) type yes then yes again.
Press Enter to Install Anaconda3 to your root directory.
The installer prompts you to choose whether to initialize Anaconda Distribution by running conda init. Anaconda recommends entering “yes”.
The installer finishes and displays, “Thank you for installing Anaconda3"
Connect your RP3+ to the system and copy your vbmeta_a.img and magisk_patched-26000_Lf8IC.img files to the retroid-pocket-3-plus-autoroot directory on your Linux OS.
Rename vbmeta_a.img to vbmeta.img
Rename magisk_patched-26000_Lf8IC.img to magisk.img
Right click in the retroid-pocket-3-plus-autoroot folder and Click "Open Terminal Here".
Drag patch.sh into the Terminal and press Enter.
"Extracting keys from vbmeta
Creating custom key for boot
Creating custom vbmeta and signing
Signing magisk.img
DONE!!!
Press any key to continue"
Press the Any Key.
-----------------
6. Flashing the Signed Images.
Copy the vbmeta_custom.img and magisk.img files over to your Windows OS.
Download and extract Minimal adb and fastboot:
Minimal ADB and Fastboot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Run openCMDhere.bat
Power off your RP3+.
Press and hold the POWER and VOLUME UP buttons until it boots to recovery mode.
Select reboot to fastboot/bootloader from the recovery options.
Connect the RP3+ to your PC.
On the CMD Terminal, Enter:
Code:
fastboot devices
You should see the device listed.
To flash the 4 necessary boot and vbmeta partitions enter the following commands:
Code:
fastboot flash vbmeta_a /YOUR PATH HERE/vbmeta_custom.img
Code:
fastboot flash vbmeta_b /YOUR PATH HERE/vbmeta_custom.img
Code:
fastboot flash boot_a /YOUR PATH HERE/magisk.img
Code:
fastboot flash boot_b /YOUR PATH HERE/magisk.img
Code:
fastboot reboot
-----------------
You now have Magisk ROOT!!!
!!!!WARNINGS!!!!
NEVER UPDATE MAGISK THROUGH THE APP! ALWAYS REPATCH YOUR ORIGINAL BOOT IMAGE!
IF BY ANY CHANCE YOU RECEIVE A PROMPT TO DO AN OTA UPDATE, DON'T DO IT! YOU WILL BOOTLOOP! (Go into settings and disable all automatic updates, Enable Developer options and Disable OTA updates)
MAKE SURE TO HAVE MULTIPLE BACKUPS ON HAND IN CASE OF A BRICK! WHILE SOMEONE IS MAKING AN UNBRICKING TOOL IT WILL NOT WORK WITHOUT BACKUPS!
-----------------
Credits to skompc AKA SquirrelHurtz AKA u/FoxyCatDogThing for the avb patch script.
Credits to Turtle and hartleysch for the bootloader unlock.
Credits to ApatheticEuphoria for the comprehensive guide.
Related
I see a lot of users asking for pit file for T210/R 8GB after bricking their partition table due to a bad flash, i see here to share it.
This pit file is extracted from rooted Tab 3 T210/R 8GB .
Unzip attached zip and flash pit file along with stock firmware in odin.
...Do not flash it if there is no need to...
Flash it if Odin says: "there is no pit partition" or "Re-Partition operation failed", in this case "Re-Partition" must be marked.
!Flash it at your own risk and responsibility!
THX to @Greaper88
T210 8GB partition table
List of blocks by number:
Code:
adb shell
cat /proc/partitions
major minor #blocks name
179 0 7634944 mmcblk0
179 1 1024 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 4096 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 12288 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 12288 mmcblk0p8
179 9 12288 mmcblk0p9
179 10 12288 mmcblk0p10
179 11 10240 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 4096 mmcblk0p13
179 14 1472512 mmcblk0p14
179 15 204800 mmcblk0p15
179 16 204800 mmcblk0p16
179 17 5640192 mmcblk0p17
179 48 2048 mmcblk0boot1
179 24 2048 mmcblk0boot0
179 72 1927168 mmcblk1
179 73 1926144 mmcblk1p1
List of blocks by name:
Code:
adb shell
ls -al /dev/block/platform/sdhci-pxav3.2/by-name
lrwxrwxrwx root root 2014-04-24 19:30 BOTA0 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-04-24 19:30 CACHE -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-04-24 19:30 EFS -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-04-24 19:30 HIDDEN -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-04-24 19:30 KERNEL -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-04-24 19:30 MEP -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-04-24 19:30 MISC -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-04-24 19:30 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-04-24 19:30 MRD -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-04-24 19:30 NVM -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-04-24 19:30 PARAM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-04-24 19:30 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-04-24 19:30 SBL -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-04-24 19:30 SBL2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-04-24 19:30 SYSTEM -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-04-24 19:30 USER -> /dev/block/mmcblk0p17
thanks for the info.
Samsung Galaxy Tab3 SM-T210R Pit file
Hi do you also have the pit file for samsung galaxy tab 3 sm-t210r? or do you know where to get it? thank you
Do they use the same partition table since they're both 8GB?
edit: And if your PIT is messed up already, you can't hurt anything by trying it. As long as it provides enough space for everything that needs to be installed, I would expect it to be fine.
PIT info from SM-T210R
Blocks list by number:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 1024 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 4096 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 12288 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 12288 mmcblk0p8
179 9 12288 mmcblk0p9
179 10 12288 mmcblk0p10
179 11 10240 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 4096 mmcblk0p13
179 14 1472512 mmcblk0p14
179 15 204800 mmcblk0p15
179 16 204800 mmcblk0p16
179 17 5640192 mmcblk0p17
179 48 2048 mmcblk0boot1
179 24 2048 mmcblk0boot0
179 72 31166976 mmcblk1
179 73 22163085 mmcblk1p1
179 74 8003906 mmcblk1p2
179 75 999983 mmcblk1p3
Click to expand...
Click to collapse
Blocks list by Name:
lrwxrwxrwx root root 2014-11-11 04:22 BOTA0 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-11-11 04:22 CACHE -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-11-11 04:22 EFS -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-11-11 04:22 HIDDEN -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-11-11 04:22 KERNEL -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-11-11 04:22 MEP -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-11-11 04:22 MISC -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-11-11 04:22 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-11-11 04:22 MRD -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-11-11 04:22 MRD_BK -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-11-11 04:22 NVM -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-11-11 04:22 PARAM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-11-11 04:22 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-11-11 04:22 SBL -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-11-11 04:22 SBL2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-11-11 04:22 SYSTEM -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-11-11 04:22 USER -> /dev/block/mmcblk0p17
Click to expand...
Click to collapse
From what I can tell, the PITs are exactly the same. "dev/block/mmcblk1" and "mmcblk1p*" (the "p*" refers to the partition #)are the external microSD card. Mine has 3 partitions: Link2sd and swap.
So, based on these findings, I would try this PIT file if I needed to for my T210R. But again, flash at your own risk
SG Tab 3 Pit File
Thank you Greaper88, i'll try that but can you teach me how to use that pit file on odin? Thank you
ljgrn_cnmi12 said:
Thank you Greaper88, i'll try that but can you teach me how to use that pit file on odin? Thank you
Click to expand...
Click to collapse
Using a PIT file assumes you also have a ROM to flash.
In the attached pic, Box 1 should show "COM: ##" when your device is connected and in download mode.
Box 2 is highlighting the "Re-partition" box. It needs to be checked, otherwise Odin won't rewrite the PIT.
Box 3 is clicking "PIT" and selecting the PIT file downloaded from this forum.
Box 4 is selecting your ROM for your device: http://forum.xda-developers.com/galaxy-tab-3/general/tab-3-7-0-sm-t210-r-stock-4-4-2-kitkat-t2930075
Since the ROM referenced in that link is stock all the way, I would try flashing it first without using the PIT, then using the PIT if it fails.
Box 5 is clicking the "Start" button and waiting.
Good luck to you
@Greaper88
thank you for sharing
please can you share pit partition of your 210R (i guess it is the same as 210, but to be sure)
use this command to extract it (in adb shell or terminal emulator):
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=481 skip=2176
zip the output and attached to a post
samersh72 said:
@Greaper88
please can you share pit partition of your 210R (i guess it is the same as 210, but to be sure)
use this command to extract it (in adb shell or terminal emulator):
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=481 skip=2176
zip the output and attached to a post
Click to expand...
Click to collapse
Cool. Thanks. Learn something new evry day
pit file for tab 3 p5210
Hi...pls i nid help on pit file for tab 3 p5210...i'd appreciate any link...fanx
I have tried my best to follow this tutorial but it hasn't fixed my Galaxy Tab 3 - SM-T210. This is the error message I'm getting. Can anyone spot what I'm doing wrong?
Hi,
i have problem to reflash the lates ROM for P3100.
first i install the lates rom with success, after few days i have error "Can't load native library. CPU arch invalid for this build" then my tab restart. i tried to re flash thr ROM and its success but still same problem then i flash other version ROM its success but when its booting still on the same ROM. i also try to flash stock rom using odin, its success but same problem, booting and still using SlimROM. i have no idea with this problem please help
ROM SlimKAT
Recovery : TWRP
[email protected]:/ $ ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name/
ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name/
lrwxrwxrwx root root 2014-05-16 23:08 CACHE -> /dev/block/mmcbl
k0p7
lrwxrwxrwx root root 2014-05-16 23:08 DATAFS -> /dev/block/mmcb
lk0p10
lrwxrwxrwx root root 2014-05-16 23:08 EFS -> /dev/block/mmcblk0
p1
lrwxrwxrwx root root 2014-05-16 23:08 FACTORYFS -> /dev/block/m
mcblk0p9
lrwxrwxrwx root root 2014-05-16 23:08 HIDDEN -> /dev/block/mmcb
lk0p11
lrwxrwxrwx root root 2014-05-16 23:08 KERNEL -> /dev/block/mmcb
lk0p5
lrwxrwxrwx root root 2014-05-16 23:08 MODEM -> /dev/block/mmcbl
k0p8
lrwxrwxrwx root root 2014-05-16 23:08 PARAM -> /dev/block/mmcbl
k0p4
lrwxrwxrwx root root 2014-05-16 23:08 RECOVERY -> /dev/block/mm
cblk0p6
lrwxrwxrwx root root 2014-05-16 23:08 SBL1 -> /dev/block/mmcblk
0p2
lrwxrwxrwx root root 2014-05-16 23:08 SBL2 -> /dev/block/mmcblk
0p3
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 20480 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 716800 mmcblk0p7
259 0 20480 mmcblk0p8
259 1 1433600 mmcblk0p9
259 2 12640239 mmcblk0p10
259 3 524288 mmcblk0p11
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
179 24 15724544 mmcblk1
179 25 15723520 mmcblk1p1
any idea ? seems every i install apk its success but after restart the phone the program gone, same with when i uninstall apk, when reboot the phone the program still there. whatever im done all coming back
attach recovery log
anyone?
Hi,
My phone is stuck at boot stage where the rom logo animation (CrDroid rom) is animating, so no freeze. The phone never goes further than that.
I can boot into either bootloader, Fastboot (Secure boot: enabled, Lock State: unlocked) and recovery. I also have access to ADB/Fastboot from PC. I've managed to init a shell but /sdcard is empty
When I enter recovery (TWRP 3.3.1-hh), this is the content of recovery log/terminal:
Code:
[COLOR="Red"]Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Failed to mount '/cache' (Invalid argument)[/COLOR]
Updating partition details...
[COLOR="Red"]Failed to mount '/data' (Invalid argument)
Failed to mount '/cache' (Invalid argument)[/COLOR]
...done
[COLOR="red"]Unable to mount storage
Failed to mount '/data' (Invalid argument)[/COLOR]
Full SELinux support is present.
[COLOR="red"]Unable to mount /data/media/TRWP/.twrps[/COLOR]
MTP Enabled
What solution do I have in order to retrieve my data? I think I encrypted the phone with a SIM PIN code, but I'm not sure because I do it sometimes when I flash a ROM, but this time I may have decided not to do it. I can't remember for sure. The other reason for my doubt is if I understand correctly, some recent versions of Android are forced encrypted, though I thought that was only valid for stock ROM which is not my case.
I found this topic (https://forum.xda-developers.com/oneplus-6/how-to/tutorial-decrypt-flash-rom-pie-oreo-roms-t3838643) that seems to describe a process in order to get encrypted files back by flashing a ROM, but it's for OnePlus6. Do you guys think this can work for me?
Help would be much appreciated.
Best regards,
Specs: Nexus 5 (LG-D821), TWRP 3.3.1-HH, crDroidAndroid-9.0-20191014-hammerhead-v5.8 (https://forum.xda-developers.com/google-nexus-5/development/rom-crdroid-v5-4-t3931587)
EDIT: I gave it up in the end
Bump,
Anyone that can help?
danoussh said:
Hi,
My phone is stuck at boot stage where the rom logo animation (CrDroid rom) is animating, so no freeze. The phone never goes further than that.
I can boot into either bootloader, Fastboot (Secure boot: enabled, Lock State: unlocked) and recovery. I also have access to ADB/Fastboot from PC. I've managed to init a shell but /sdcard is empty
When I enter recovery (TWRP 3.3.1-hh), this is the content of recovery log/terminal:
What solution do I have in order to retrieve my data? I think I encrypted the phone with a SIM PIN code, but I'm not sure because I do it sometimes when I flash a ROM, but this time I may have decided not to do it. I can't remember for sure. The other reason for my doubt is if I understand correctly, some recent versions of Android are forced encrypted, though I thought that was only valid for stock ROM which is not my case.
I found this topic (https://forum.xda-developers.com/oneplus-6/how-to/tutorial-decrypt-flash-rom-pie-oreo-roms-t3838643) that seems to describe a process in order to get encrypted files back by flashing a ROM, but it's for OnePlus6. Do you guys think this can work for me?
Help would be much appreciated.
Best regards,
Specs: Nexus 5 (LG-D821), TWRP 3.3.1-HH, crDroidAndroid-9.0-20191014-hammerhead-v5.8 (https://forum.xda-developers.com/google-nexus-5/development/rom-crdroid-v5-4-t3931587)
Click to expand...
Click to collapse
You can't decrypt files on n5.
There are 2 types of encryption:
FBE - File Based Encryption
FDE - Full Disk Encryption
We don't have fbe. When you press the encrypt button in Rom settings. You will get fde. I don't know crdroid but if you encrypted your disk, than sorry afaik no chance to rescue your files here. Go and start with formatting data partition or flash stock 6.0.1 and flash another rom again.
lulli1 said:
You can't decrypt files on n5.
There are 2 types of encryption:
FBE - File Based Encryption
FDE - Full Disk Encryption
We don't have fbe. When you press the encrypt button in Rom settings. You will get fde. I don't know crdroid but if you encrypted your disk, than sorry afaik no chance to rescue your files here. Go and start with formatting data partition or flash stock 6.0.1 and flash another rom again.
Click to expand...
Click to collapse
Thanks for the reply. I really hoped there was a way by installing a new rom above which would allow full disk encryption to be unlocked again.
EDIT: Before I give up, here is some extra info.
I can navigate through the TRWP file manager on system through folders, I see files and folders. Is that a clue that my phone is not full disk encrypted, or is full disk encrypted only for user data and the full system?
Also here is a dump I did via ADB shell.
Code:
~ # [6ncat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 512 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 22528 mmcblk0p18
179 19 22528 mmcblk0p19
179 20 22528 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 512 mmcblk0p24
179 25 1500000 mmcblk0p25
179 26 30720 mmcblk0p26
179 27 265375 mmcblk0p27
179 28 13404138 mmcblk0p28
179 29 5 mmcblk0p29
179 32 4096 mmcblk0rpmb
~ # [6n
------------------------------------------
~ # ls -la /dev/block/platform/msm_sdcc.1/by-name/[J
__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 620 Jan 5 21:43 .
drwxr-xr-x 4 root root 700 Jan 5 21:43 ..
lrwxrwxrwx 1 root root 21 Jan 5 21:43 DDR -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 Jan 5 21:43 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Jan 5 21:43 abootb -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 5 21:43 boot -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 5 21:43 cache -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Jan 5 21:43 crypto -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Jan 5 21:43 fsc -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Jan 5 21:43 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Jan 5 21:43 grow -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Jan 5 21:43 imgdata -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jan 5 21:43 laf -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Jan 5 21:43 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 5 21:43 misc -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 20 Jan 5 21:43 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Jan 5 21:43 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 5 21:43 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 Jan 5 21:43 pad -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jan 5 21:43 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Jan 5 21:43 recovery -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 Jan 5 21:43 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 5 21:43 rpmb -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 Jan 5 21:43 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Jan 5 21:43 sbl1b -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Jan 5 21:43 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 Jan 5 21:43 ssd -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Jan 5 21:43 system -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 20 Jan 5 21:43 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Jan 5 21:43 tzb -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 5 21:43 userdata -> /dev/block/mmcblk0p28
~ # [6n
I gave up and decided to reinstall android.
For those who may have trouble flashing because of /data not wanting to format, try to flash new TWRP recovery (latest one for your device.). You should be able to boot back into recovery and then you can format/wipe /data.
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.