U696CL Old Thread - Android won't show up as USB device on VirtualBox after putting phone in ADB/EDL mode?

Search This thread

gregeerg

Senior Member
May 12, 2022
109
14
Do you have a regular (known good) boot image?
Get imgutil.exe (from my sig).
Code:
C:\>imgutil.exe good_boot.img /v
C:\>imgutil.exe recovery.img /v
Yeah, I have the exact boot/recovery.img from the phone itself. Both work perfectly. But trying to get TWRP to work but keeps getting overwritten with stock recovery. This is the result from the stock boot/recovery:

Code:
PS F:\bootrecoveryOG> .\imgutil.exe boot.img /v
Header2:        1,660 (0000067C)
Kernel:    13,620,992 (00CFD700) @ 80008000
  Stub:    13,620,933 (00CFD6C5)
Ramdisk:      880,207 (000D6E4F) @ 81000000
DTB:        2,235,141 (00221B05)
Padding:   16,814,080 (01009000)
Command: console=ttyMSM0,115200,n8 androidboot.console=ttyMSM0 androidboot.hardware=qcom androidboot.memcg=true user_debug=30 msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlycon=msm_hsl_uart,0x78B0000 vmalloc=300M androidboot.usbconfigfs=true cgroup.memory=nokmem,nosocket loop.max_part=7 buildvariant=user

PS F:\bootrecoveryOG> .\imgutil.exe recovery.img /v
Header2:        1,660 (0000067C)
Kernel:    13,620,992 (00CFD700) @ 80008000
  Stub:    13,620,933 (00CFD6C5)
Ramdisk:    7,383,094 (0070A836) @ 81000000
Recovery:     844,828 (000CE41C)
DTB:        2,235,141 (00221B05)
Padding:   27,086,848 (019D5000)
Command: console=ttyMSM0,115200,n8 androidboot.console=ttyMSM0 androidboot.hardware=qcom androidboot.memcg=true user_debug=30 msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlycon=msm_hsl_uart,0x78B0000 vmalloc=300M androidboot.usbconfigfs=true cgroup.memory=nokmem,nosocket loop.max_part=7 buildvariant=user

Result from one of the test TWRP images:
Code:
PS C:\Users\user\Desktop> .\imgutil.exe recoverytest.img /v
Header2:        1,660 (0000067C)
Kernel:    13,620,992 (00CFD700) @ 80008000
  Stub:    13,620,933 (00CFD6C5)
Ramdisk:    6,119,612 (005D60BC) @ 81000000
Recovery:     844,828 (000CE41C)
DTB:        2,235,141 (00221B05)
Padding:      845,824 (000CE800)
Command: console=ttyMSM0,115200,n8 androidboot.console=ttyMSM0 androidboot.hardware=qcom androidboot.memcg=true user_debug=30 msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlycon=msm_hsl_uart,0x78B0000 vmalloc=300M androidboot.usbconfigfs=true cgroup.memory=nokmem,nosocket loop.max_part=7 androidboot.selinux=permissive buildvariant=user buildvariant=eng
 
Last edited:
  • Like
Reactions: Renate

gregeerg

Senior Member
May 12, 2022
109
14
Yes, but fastboot booting you got a dtb error. Are you sure of the presence of a dtb in boot.img & recovery.img or whether it's a red herring.
Edited my reply above with the results ^

"Are you sure of the presence of a dtb in boot.img & recovery.img or whether it's a red herring."
I have no idea since I'm not good with all of this stuff.
 

Renate

Recognized Contributor / Inactive Recognized Dev
Feb 3, 2012
3,277
1,454
Boston
www.temblast.com
Nexus 7 (2013)
Moto E5
Thank you. I've not had a lot of experience with Type 2 images. Do you have a link for the TWRP one?

You can see from the printout that you are using the direct copy of the whole partition. The actual image is just a part of that. No, it doesn't make much difference. I just prefer to truncate them to actual size. I want to see the TWRP image to see if my calculations are correct.
 

gregeerg

Senior Member
May 12, 2022
109
14
Thank you. I've not had a lot of experience with Type 2 images. Do you have a link for the TWRP one?

You can see from the printout that you are using the direct copy of the whole partition. The actual image is just a part of that. No, it doesn't make much difference. I just prefer to truncate them to actual size. I want to see the TWRP image to see if my calculations are correct.
TWRP: https://www.mediafire.com/file/ms2lrbejy6d56ep/recoverytest.img/file

Stock: https://www.mediafire.com/file/zmq5vvemloi99pm/recovery.img/file

If it matters, I was told that this is a very barebones basic TWRP version that was built to test. And was told, “I could take apart the super, the ones inside and try to remedy the situation, then put them back together and refresh the super” but they’re at work right now.
 
Last edited:
  • Like
Reactions: aIecxs

Renate

Recognized Contributor / Inactive Recognized Dev
Feb 3, 2012
3,277
1,454
Boston
www.temblast.com
Nexus 7 (2013)
Moto E5
Thanks, @gregeerg you enabled me to fix two bugs. recoverytest.img does not have any empty padding at the end, but your other two images still do have ~15M, ~26M of zeroes at the end. (You can download the new version of imgutil.exe if you like.)

Code:
C:\>imgutil /v recoverytest.img
Header2:        1,660 (0000067C)
Kernel:    13,620,992 (00CFD700) @ 80008000
Ramdisk:    6,119,612 (005D60BC) @ 81000000
Recovery:     844,828 (000CE41C)
DTB:        2,235,141 (00221B05)
Command: console=ttyMSM0,115200,n8 androidboot.console=ttyMSM0 androidboot.hardware=qcom androidboot.memcg=true user_debug=30 msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlycon=msm_hsl_uart,0x78B0000 vmalloc=300M androidboot.usbconfigfs=true cgroup.memory=nokmem,nosocket loop.max_part=7 androidboot.selinux=permissive buildvariant=user buildvariant=eng
 

gregeerg

Senior Member
May 12, 2022
109
14
Thanks, @gregeerg you enabled me to fix two bugs. recoverytest.img does not have any empty padding at the end, but your other two images still do have ~15M, ~26M of zeroes at the end. (You can download the new version of imgutil.exe if you like.)

Code:
C:\>imgutil /v recoverytest.img
Header2:        1,660 (0000067C)
Kernel:    13,620,992 (00CFD700) @ 80008000
Ramdisk:    6,119,612 (005D60BC) @ 81000000
Recovery:     844,828 (000CE41C)
DTB:        2,235,141 (00221B05)
Command: console=ttyMSM0,115200,n8 androidboot.console=ttyMSM0 androidboot.hardware=qcom androidboot.memcg=true user_debug=30 msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlycon=msm_hsl_uart,0x78B0000 vmalloc=300M androidboot.usbconfigfs=true cgroup.memory=nokmem,nosocket loop.max_part=7 androidboot.selinux=permissive buildvariant=user buildvariant=eng
Download form here? Still says last updated in April. https://www.temblast.com/imgutil.htm
EDIT: Now says May.

So what exactly does this all mean now? What should I do next?
 

gregeerg

Senior Member
May 12, 2022
109
14
can you please post list of all partitions (#59)? get the feeling there are some missing.. I need super.img at least, including sha2 checksum (#73)
Partitions. SUper is block 14:
Code:
phhgsi_a64_ab:/ $ su
:/data/data # ls -l $(find /dev/block -name by-name)
/dev/block/by-name:
total 0
lrwxrwxrwx 1 root root 20 1969-12-31 21:47 DDR -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 1969-12-31 21:47 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 1969-12-31 21:47 abootbak -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 apdp -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 boot -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 carrier -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 cmnlib -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 cmnlib64 -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 cmnlib64bak -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 cmnlibbak -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 config -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 devcfg -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 devcfgbak -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 devinfo -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 dip -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 dpo -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 dsp -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 20 1969-12-31 21:47 dtbo -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 1969-12-31 21:47 dtbobak -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 factory -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 fsc -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 1969-12-31 21:47 fsg -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 keymaster -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 keymasterbak -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 keystore -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 limits -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 mcfg -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 mdtp -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 metadata -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 misc -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 18 1969-12-31 21:47 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx 1 root root 20 1969-12-31 21:47 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 modemst1 -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 modemst2 -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 mota -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 msadp -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 oem -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 persist -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 recovery -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 rpm -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 rpmbak -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 sbl1 -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 sbl1bak -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 20 1969-12-31 21:47 sec -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 splash -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 super -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 syscfg -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 tz -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 tzbak -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 userdata -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 20 1969-12-31 21:47 vbmeta -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 vbmeta_system -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 vbmeta_systembak -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 vbmetabak -> /dev/block/mmcblk0p10

/dev/block/platform/soc/7824900.sdhci/by-name:
total 0
lrwxrwxrwx 1 root root 20 1969-12-31 21:47 DDR -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 1969-12-31 21:47 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 1969-12-31 21:47 abootbak -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 apdp -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 boot -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 carrier -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 cmnlib -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 cmnlib64 -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 cmnlib64bak -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 cmnlibbak -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 config -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 devcfg -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 devcfgbak -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 devinfo -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 dip -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 dpo -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 dsp -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 20 1969-12-31 21:47 dtbo -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 1969-12-31 21:47 dtbobak -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 factory -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 fsc -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 1969-12-31 21:47 fsg -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 keymaster -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 keymasterbak -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 keystore -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 limits -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 mcfg -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 mdtp -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 metadata -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 misc -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 20 1969-12-31 21:47 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 modemst1 -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 modemst2 -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 mota -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 msadp -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 oem -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 persist -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 recovery -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 rpm -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 rpmbak -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 sbl1 -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 sbl1bak -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 20 1969-12-31 21:47 sec -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 splash -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 super -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 syscfg -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 tz -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 tzbak -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 userdata -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 20 1969-12-31 21:47 vbmeta -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 vbmeta_system -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 vbmeta_systembak -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1969-12-31 21:47 vbmetabak -> /dev/block/mmcblk0p10

Sha sum command isn't working for some reason but worked yesterday and whatever I checked yesterday matched.
Code:
phhgsi_a64_ab:/ $ sha256sum boot.img
sha256sum: boot.img: No such file or directory
 
  • Like
Reactions: aIecxs

Renate

Recognized Contributor / Inactive Recognized Dev
Feb 3, 2012
3,277
1,454
Boston
www.temblast.com
Nexus 7 (2013)
Moto E5
So what exactly does this all mean now? What should I do next?
Mmm, nothing. I think that @Alecxs is on the trail of something.

imgutil.exe (in its simplest usage) is a good sanity check for an image. It tells you (reliably now) what is there.
In more advanced usage it allows you to swap stuff or add files to ramdisk without exploding/imploding everything.
I use it to cook up all my mods.
 

aIecxs

Senior Member
Feb 17, 2016
1,889
538
gitlab.com
these partitions are not dumped yet. I need super.img at least, please upload zip archive

Code:
adb exec-out "su root dd if=/dev/block/mmcblk0p2 status=none 2> /dev/null" > DDR.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p5 status=none 2> /dev/null" > aboot.elf
adb exec-out "su root dd if=/dev/block/mmcblk0p50 status=none 2> /dev/null" > apdp.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p53 status=none 2> /dev/null" > carrier.img
adb exec-out "su root dd if=/dev/block/mmcblk0p16 status=none 2> /dev/null" > cmnlib.mbn
adb exec-out "su root dd if=/dev/block/mmcblk0p18 status=none 2> /dev/null" > cmnlib64.mbn
adb exec-out "su root dd if=/dev/block/mmcblk0p43 status=none 2> /dev/null" > config.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p32 status=none 2> /dev/null" > devcfg.mbn
adb exec-out "su root dd if=/dev/block/mmcblk0p13 status=none 2> /dev/null" > devinfo.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p46 status=none 2> /dev/null" > dip.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p52 status=none 2> /dev/null" > dpo.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p34 status=none 2> /dev/null" > dsp.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p54 status=none 2> /dev/null" > factory.img
adb exec-out "su root dd if=/dev/block/mmcblk0p24 status=none 2> /dev/null" > fsc.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p3 status=none 2> /dev/null" > fsg.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p20 status=none 2> /dev/null" > keymaster.mbn
adb exec-out "su root dd if=/dev/block/mmcblk0p42 status=none 2> /dev/null" > keystore.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p15 status=none 2> /dev/null" > limits.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p49 status=none 2> /dev/null" > mcfg.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p47 status=none 2> /dev/null" > mdtp.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p41 status=none 2> /dev/null" > misc.img
adb exec-out "su root dd if=/dev/block/mmcblk0p1 status=none 2> /dev/null" > modem.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p35 status=none 2> /dev/null" > modemst1.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p36 status=none 2> /dev/null" > modemst2.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p45 status=none 2> /dev/null" > mota.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p51 status=none 2> /dev/null" > msadp.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p44 status=none 2> /dev/null" > oem.img
adb exec-out "su root dd if=/dev/block/mmcblk0p40 status=none 2> /dev/null" > persist.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p28 status=none 2> /dev/null" > rpm.mbn
adb exec-out "su root dd if=/dev/block/mmcblk0p26 status=none 2> /dev/null" > sbl1.mbn
adb exec-out "su root dd if=/dev/block/mmcblk0p4 status=none 2> /dev/null" > sec.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p37 status=none 2> /dev/null" > splash.img
adb exec-out "su root dd if=/dev/block/mmcblk0p25 status=none 2> /dev/null" > ssd.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p14 status=none 2> /dev/null" > super.img
adb exec-out "su root dd if=/dev/block/mmcblk0p48 status=none 2> /dev/null" > syscfg.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p9 status=none 2> /dev/null" > vbmeta.img
adb exec-out "su root dd if=/dev/block/mmcblk0p22 status=none 2> /dev/null" > vbmeta_system.img
 

gregeerg

Senior Member
May 12, 2022
109
14
these partitions are not dumped yet. I need super.img at least, please upload zip archive

Code:
adb exec-out "su root dd if=/dev/block/mmcblk0p2 status=none 2> /dev/null" > DDR.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p5 status=none 2> /dev/null" > aboot.elf
adb exec-out "su root dd if=/dev/block/mmcblk0p50 status=none 2> /dev/null" > apdp.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p53 status=none 2> /dev/null" > carrier.img
adb exec-out "su root dd if=/dev/block/mmcblk0p16 status=none 2> /dev/null" > cmnlib.mbn
adb exec-out "su root dd if=/dev/block/mmcblk0p18 status=none 2> /dev/null" > cmnlib64.mbn
adb exec-out "su root dd if=/dev/block/mmcblk0p43 status=none 2> /dev/null" > config.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p32 status=none 2> /dev/null" > devcfg.mbn
adb exec-out "su root dd if=/dev/block/mmcblk0p13 status=none 2> /dev/null" > devinfo.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p46 status=none 2> /dev/null" > dip.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p52 status=none 2> /dev/null" > dpo.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p34 status=none 2> /dev/null" > dsp.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p54 status=none 2> /dev/null" > factory.img
adb exec-out "su root dd if=/dev/block/mmcblk0p24 status=none 2> /dev/null" > fsc.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p3 status=none 2> /dev/null" > fsg.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p20 status=none 2> /dev/null" > keymaster.mbn
adb exec-out "su root dd if=/dev/block/mmcblk0p42 status=none 2> /dev/null" > keystore.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p15 status=none 2> /dev/null" > limits.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p49 status=none 2> /dev/null" > mcfg.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p47 status=none 2> /dev/null" > mdtp.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p41 status=none 2> /dev/null" > misc.img
adb exec-out "su root dd if=/dev/block/mmcblk0p1 status=none 2> /dev/null" > modem.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p35 status=none 2> /dev/null" > modemst1.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p36 status=none 2> /dev/null" > modemst2.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p45 status=none 2> /dev/null" > mota.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p51 status=none 2> /dev/null" > msadp.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p44 status=none 2> /dev/null" > oem.img
adb exec-out "su root dd if=/dev/block/mmcblk0p40 status=none 2> /dev/null" > persist.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p28 status=none 2> /dev/null" > rpm.mbn
adb exec-out "su root dd if=/dev/block/mmcblk0p26 status=none 2> /dev/null" > sbl1.mbn
adb exec-out "su root dd if=/dev/block/mmcblk0p4 status=none 2> /dev/null" > sec.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p37 status=none 2> /dev/null" > splash.img
adb exec-out "su root dd if=/dev/block/mmcblk0p25 status=none 2> /dev/null" > ssd.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p14 status=none 2> /dev/null" > super.img
adb exec-out "su root dd if=/dev/block/mmcblk0p48 status=none 2> /dev/null" > syscfg.bin
adb exec-out "su root dd if=/dev/block/mmcblk0p9 status=none 2> /dev/null" > vbmeta.img
adb exec-out "su root dd if=/dev/block/mmcblk0p22 status=none 2> /dev/null" > vbmeta_system.img
Thanks a TON for the commands. I literally sit here refreshing the page for replies every 30s or so but sorry for this delayed reply. Took a while to transfer super.img to my PC & getting it all uploaded. Looks like 30mins more to upload to a file sharing site, sorry for the wait
 

gregeerg

Senior Member
May 12, 2022
109
14
Mmm, nothing. I think that @Alecxs is on the trail of something.

imgutil.exe (in its simplest usage) is a good sanity check for an image. It tells you (reliably now) what is there.
In more advanced usage it allows you to swap stuff or add files to ramdisk without exploding/imploding everything.
I use it to cook up all my mods.
Would you happen to know of any scripts that can unpack/extract and re-pack a super.img file?
 
Sorry, I haven't dealt with super (dynamic partitions) yet.
I would think that the best/safest way to deal with that would be using recovery with it mounted and access system and vendor that way,
won't be booting recovery until we can defeat the reflash procedure. I'm pretty sure they moved it to vendor. In the process of rebuilding and modifying super.img. Stay Tuned.....
 

Renate

Recognized Contributor / Inactive Recognized Dev
Feb 3, 2012
3,277
1,454
Boston
www.temblast.com
Nexus 7 (2013)
Moto E5
Sometimes fastboot boot <image> has problems. The "gold standard" is always fastboot flash <part> <image> and reboot.
If you flash recovery, reset and go directly to recovery there should be no problem with overwriting.
That is, unless your recovery is broken and it attempts that first, fails, reboots to system and gets overwritten.

You can also flash recovery, then flash a modified misc with "boot-recovery" at address 0, then reset.
 
  • Like
Reactions: aIecxs

gregeerg

Senior Member
May 12, 2022
109
14
Sometimes fastboot boot <image> has problems. The "gold standard" is always fastboot flash <part> <image> and reboot.
If you flash recovery, reset and go directly to recovery there should be no problem with overwriting.
That is, unless your recovery is broken and it attempts that first, fails, reboots to system and gets overwritten.

You can also flash recovery, then flash a modified misc with "boot-recovery" at address 0, then reset.
"Sometimes fastboot boot <image> has problems." I could see that, but every single time for hours and multiple PC reboots?
 

Renate

Recognized Contributor / Inactive Recognized Dev
Feb 3, 2012
3,277
1,454
Boston
www.temblast.com
Nexus 7 (2013)
Moto E5
"Sometimes fastboot boot <image> has problems." I could see that, but every single time for hours and multiple PC reboots?
No, I meant "sometimes" as in some situations. I've never been able to nail down the whys.
If fastboot boot doesn't work on a particular image, it's never going to work on it.

Fastboot flash recovery recovery.img. Do your buttons work well enough to make it go to recovery on reboot?
If not, then do the misc hack. Just make sure that you start with a clean copy of your existing.

I didn't notice that you aren't A/B. Your misc partiton should be all zeroes normally.
 

gregeerg

Senior Member
May 12, 2022
109
14
No, I meant "sometimes" as in some situations. I've never been able to nail down the whys.
If fastboot boot doesn't work on a particular image, it's never going to work on it.

Fastboot flash recovery recovery.img. Do your buttons work well enough to make it go to recovery on reboot?
If not, then do the misc hack. Just make sure that you start with a clean copy of your existing.
Yes, they do. I've manually went into recovery countless times now as well as from adb/fastboot commands. No matter what, the recovery.img always gets overwritten by the stock.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    EDIT: See the unofficial thread I made that has to do with the U696CL root and where we are:

    Been trying to figure this out for 5-6hrs now. My Linux VM on my Windows 10 PC detects my phone when plugged into my PC. Great. What I cannot figure out is how to get the phone to still show up when I re-boot it into EDL/ADB mode. It simply doesn't show up in my VM *nor* my PC. But when it's booted normally, it shows just fine on both. PLEASE help. For reference: https://forum.xda-developers.com/t/umx-u693cl-assurant-wireless.4085149/post-86882085
    1
    all it needs is linux and working method to enter EDL mode.

    I recommend to boot Xubuntu 20.04 LTS from pendrive and create a backup straight from pure linux instead (no more issues with vm usb passthrough)

    extract UMX-U693CL-FireHose_Programmer.mbn from UMX_U693CL-A-Team-Root_Recovery_Package.zip and see if it works for your device.

    device must listed as QDLoader 9008 mode in lsusb

    Code:
    edl --loader='/path/to/UMX-U693CL-FireHose_Programmer.mbn' rl dumps

    (run sudo apt update once then follow install instructions as descripted here)
    https://github.com/bkerler/edl
    1
    Factory Loader = Firehose programmer. the Loaders repo is a collection for other devices. "Install EDL Loaders" is for adding own firehose file to collection. you don't need this. just add the --loader flag to each command pointing to your own loader.

    "Device is in Sahara error state, please reboot device" is most likely caused by timeout. some devices only accept initiation during first 30 sec

    Wait, add —loader to what commands?
    EDIT: ok, I went into EDL mode again and very quickly ran the initial command you gave. It says “Firehose mode detected, uploading…” and is sitting there currently. Not sure how long that’s supposed to take but it’s been a good 18mins. I ran adb devices and phone isn’t showing there at the moment
    1
    .bin .mbn .elf file whatever name it has is irrelevant as it will be renamed. dirname doesn't matter you can name it tmp, newstuff, examples just put your file(s) somewhere.

    usage is (where ~/tmp is any directory with your own files and Loaders is existing target dir inside edl)
    Code:
    cd edl
    git submodule update --init --recursive
    fhloaderparse ~/tmp Loaders

    your linux is live distro from pendrive? you don't need this as you have to re-install everything on each boot anyway, its temporary linux like DVD so it's pointless.
    the only command needed is that from post #2 it's fine to test loaders. it seems like the loader is crashing your phone...
    I installed Xubuntu with my Windows so I can boot into either.
    So my commands in Terminal would look like this then if the Programmer you linked that I downloaded is at the newstuff folder?:
    Code:
    cd edl
    git submodule update --init --recursive
    fhloaderparse /home/name/edl/newstuff/ Loaders

    Because running that doesn't have seemed to change anything? Still empty folders.
    1
    you could also request user release source code in compliance to GPL. You can probably pick up in person between 9-5 in Shenzhen office :p