Hovatek Forum DEVELOPMENT Android Unpack-Repack boot+super.img
Try our Online TWRP Builder..its free!
Can't login? Please, reset your password.


Unpack-Repack boot+super.img

Unpack-Repack boot+super.img

Pages (3): 1 2 3 Next
blaze2051
blaze2051
blaze2051
Junior Member
31
30-01-2022, 12:32 AM
#1



How and what programs for linux or windows are available to unpack the boot.img and repack with twrp and super.img and repack with gsi img? my device is alldocube Smile_1 T803 w/unisoc T310

1|Smile_1:/ $ ls -al /dev/block/by-name
total 0
drwxr-xr-x 2 root root 1620 2021-10-29 21:28 .
drwxr-xr-x 6 root root 2800 2021-10-29 21:28 ..
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 avbmeta_rs_a -> /dev/block/mmcblk0p70
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 avbmeta_rs_b -> /dev/block/mmcblk0p71
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 boot_a -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 boot_b -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 cache -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 common_rs1_a -> /dev/block/mmcblk0p72
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 common_rs1_b -> /dev/block/mmcblk0p73
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 common_rs2_a -> /dev/block/mmcblk0p74
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 common_rs2_b -> /dev/block/mmcblk0p75
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 dtb_a -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 dtb_b -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 dtbo_a -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 dtbo_b -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 fbootlogo -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 gnssmodem_a -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 gnssmodem_b -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 hypervsior_a -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 hypervsior_b -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 l_agdsp_a -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 l_agdsp_b -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 l_cdsp_a -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 l_cdsp_b -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 l_deltanv_a -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 l_deltanv_b -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 l_fixnv1_a -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 l_fixnv1_b -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 l_fixnv2_a -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 l_fixnv2_b -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 l_gdsp_a -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 l_gdsp_b -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 l_ldsp_a -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 l_ldsp_b -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 l_modem_a -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 l_modem_b -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 l_runtimenv1 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 l_runtimenv2 -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 logo -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 metadata -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 20 2021-10-29 21:28 misc -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2021-10-29 21:28 miscdata -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 18 2021-10-29 21:28 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx 1 root root 23 2021-10-29 21:28 mmcblk0boot0 -> /dev/block/mmcblk0boot0
lrwxrwxrwx 1 root root 23 2021-10-29 21:28 mmcblk0boot1 -> /dev/block/mmcblk0boot1
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 odmko_a -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 odmko_b -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 persist -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 pm_sys_a -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 pm_sys_b -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 20 2021-10-29 21:28 prodnv -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2021-10-29 21:28 sml_a -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2021-10-29 21:28 sml_b -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 socko_a -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 socko_b -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 super -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 sysdumpdb -> /dev/block/mmcblk0p59
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 teecfg_a -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 teecfg_b -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 20 2021-10-29 21:28 trustos_a -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2021-10-29 21:28 trustos_b -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2021-10-29 21:28 uboot_a -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2021-10-29 21:28 uboot_b -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 uboot_log -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 userdata -> /dev/block/mmcblk0p76
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 vbmeta_a -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 vbmeta_b -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 vbmeta_odm_a -> /dev/block/mmcblk0p68
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 vbmeta_odm_b -> /dev/block/mmcblk0p69
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 vbmeta_product_a -> /dev/block/mmcblk0p66
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 vbmeta_product_b -> /dev/block/mmcblk0p67
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 vbmeta_system_a -> /dev/block/mmcblk0p60
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 vbmeta_system_b -> /dev/block/mmcblk0p61
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 vbmeta_system_ext_a -> /dev/block/mmcblk0p62
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 vbmeta_system_ext_b -> /dev/block/mmcblk0p63
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 vbmeta_vendor_a -> /dev/block/mmcblk0p64
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 vbmeta_vendor_b -> /dev/block/mmcblk0p65
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 vendor_boot_a -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 vendor_boot_b -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 wcnmodem_a -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2021-10-29 21:28 wcnmodem_b -> /dev/block/mmcblk0p22
This post was last modified: 30-01-2022, 12:42 AM by blaze2051.
blaze2051
blaze2051
blaze2051
Junior Member
31
31-01-2022, 12:52 AM
#3
(30-01-2022, 03:49 PM)Gargoyle Unpacking super.img
https://forum.xda-developers.com/t/editi...s.4196625/

Boot image
https://github.com/cfig/Android_boot_ima...r/releases

thx but these are not working for me is there a detail guide to repack boot.img with twrp recovery?
Gargoyle
Gargoyle
Gargoyle
Contributor
479
31-01-2022, 03:20 AM
#4
What exactly doesn't work?
I work with it normally without any problems.
blaze2051
blaze2051
blaze2051
Junior Member
31
31-01-2022, 04:07 AM
#5



(31-01-2022, 03:20 AM)Gargoyle What exactly doesn't work?
I work with it normally without any problems.

the unpacking of the boot.img is fine, problem is i dont know what needs to be replaced in order to inject twrp.img into the boot.img

2nd

when i use this commnad--

./lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:3697308624 --group main:2859118592 --partition system:readonly:1970069504:main --image system=./system_a.img --partition vendor:readonly:538230784:main --image vendor=./vendor_a.img --partition system_ext:readonly:350818304:main --image system_ext=./system_ext_a.img --sparse --output ./super.new.img

I get ./lpmake: input/output error and i checked it several times. im using mint 18
blaze2051
blaze2051
blaze2051
Junior Member
31
31-01-2022, 04:59 AM
#6
(31-01-2022, 03:20 AM)Gargoyle What exactly doesn't work?
I work with it normally without any problems.

i even tried to use

fastboot boot twrp.img and i get error too many links tried on usb 3.0 and 2.0
Attached Files
.png
cmd_2022-01-30_19-51-01.png
Size: 34.7 KB / Downloads: 14
blaze2051
blaze2051
blaze2051
Junior Member
31
31-01-2022, 05:37 AM
#7
(31-01-2022, 04:59 AM)blaze2051
(31-01-2022, 03:20 AM)Gargoyle What exactly doesn't work?
I work with it normally without any problems.

i even tried to use

fastboot boot twrp.img and i get error too many links tried on usb 3.0 and 2.0

then i ran

sudo ./fastboot boot twrp.img and i get error status read failed (protocol error) in linux
Gargoyle
Gargoyle
Gargoyle
Contributor
479
31-01-2022, 09:36 AM
#8
(31-01-2022, 04:07 AM)blaze2051
(31-01-2022, 03:20 AM)Gargoyle What exactly doesn't work?
I work with it normally without any problems.

the unpacking of the boot.img is fine, problem is i dont know what needs to be replaced in order to inject twrp.img into the boot.img

2nd

when i use this commnad--

./lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:3697308624 --group main:2859118592 --partition system:readonly:1970069504:main --image system=./system_a.img --partition vendor:readonly:538230784:main --image vendor=./vendor_a.img --partition system_ext:readonly:350818304:main --image system_ext=./system_ext_a.img --sparse --output ./super.new.img

I get ./lpmake: input/output error and i checked it several times. im using mint 18

What error will it print?
Gargoyle
Gargoyle
Gargoyle
Contributor
479
31-01-2022, 09:39 AM
#9
(31-01-2022, 05:37 AM)blaze2051
(31-01-2022, 04:59 AM)blaze2051
(31-01-2022, 03:20 AM)Gargoyle What exactly doesn't work?
I work with it normally without any problems.

i even tried to use

fastboot boot twrp.img and i get error too many links tried on usb 3.0 and 2.0

then i ran

sudo ./fastboot boot twrp.img and i get error status read failed (protocol error) in linux

If you have Android 10 or higher, reboot into fastbootd, adb reboot-fastboot
blaze2051
blaze2051
blaze2051
Junior Member
31
31-01-2022, 10:49 AM
#10



(31-01-2022, 09:39 AM)Gargoyle
(31-01-2022, 05:37 AM)blaze2051
(31-01-2022, 04:59 AM)blaze2051
(31-01-2022, 03:20 AM)Gargoyle What exactly doesn't work?
I work with it normally without any problems.

i even tried to use

fastboot boot twrp.img and i get error too many links tried on usb 3.0 and 2.0

then i ran

sudo ./fastboot boot twrp.img and i get error status read failed (protocol error) in linux

If you have Android 10 or higher, reboot into fastbootd, adb reboot-fastboot

so i dont use fastboot mode, so that means i need to use fastbootd? using this commnad [ adb reboot-fastboot ] all it does is reboot the tablet

If i use commnad adb reboot bootloader. that takes me to fastboot mode
This post was last modified: 31-01-2022, 10:52 AM by blaze2051.
Pages (3): 1 2 3 Next
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram