I know --- the bootloader is locked. But I still had to prove it to myself. And the info provided here may be useful to developers as well as to end-users.
Here is my story:
Running stock KK 4.4.2 (NCE) on my G900A, I successfully rooted using GeoHot’s towelroot https://towelroot.com/.
Then I froze the AT&T software updater app via Titanium Backup Pro --- since there is presently no way to re-root after updating.
Then I modified the stock recovery image to enable “adbd” (Android Debug Bridge daemon). Here’s a brief description of the process:
Running ADB with root and busybox installed, I created directory: /sdcard/Boot and did this:
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/Boot/recovery.img
Then on Windows, I unpacked recovery.img to kernel and /ramdisk and modified the /ramdisk/init.rc script as follows:
Code:
service recovery /sbin/recovery
service adbd /sbin/adbd recovery
[COLOR="Blue"]
# se[email protected] (09 Dec 2014)
# disabled
# [email protected] (09 Dec 2014)
[/COLOR]
socket adbd stream 660 system system
##++ Security R&D Group
service qrngd /system/bin/qrngd -f
class load_ode_env
user root
group root
oneshot
Then I repacked kernel and modified /ramdisk to recovery-repack.img, dropped it into /sdcard/Boot and flashed it to the recovery partition from 4.4.2 via ADB:
Code:
dd if=/sdcard/Boot/recovery-repack.img of=/dev/block/mmcblk0p16
When I rebooted, my phone returned an error message and rebooted again, this time to download mode. Oh well, I was really hoping to sneak this one past AT&T.
Somewhat nervous, I scoured the web for two days in search of a decent stock NCE build to recover my G900A. But all of the links were slow, flaky, costly and/or plagued with ads --- except for this one…
NCE Stock TAR with md5: http://www.rwilco12.com/forum/showthread.php?tid=883
Odin versions (esp. v1.85 --- considered the most stable):
http://www.rwilco12.com/forum/showthread.php?tid=101
So I downloaded the 1.5GB zip, decompressed to: “G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5”
and ran Odin v1.85 with:
“\{Path-to}\G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5”
in the PDA slot with Auto Reboot and F. Reset Time checked and no others checked except for PDA. Execution was flawless (ref. image below) and my G900A gracefully rebooted to stock KK 4.4.2--- with all of my installed apps, data and settings intact. And I quickly recovered root by re-launching the towelroot APK.
Of course I did lose busybox since it installs under /system/xbin. No problem, I just went to the BB app I had installed earlier and reinstalled BB from there.
Note: When I stripped off the .md5 suffix and opened the resulting .tar file with 7zip, an error message was returned but the file listing was still shown:
Note the absence of a data image --- a good thing if you have installed apps etc.
Something else I found helpful is the G900A partition map. Navigating to /dev/block/platform/msm_sdcc.1/by-name …
Code:
cd /dev/block/platform/msm_sdcc.1/by-name
[email protected]:/dev/block/platform/msm_sdcc.1/by-name # ls -ld *
ls -ld *
lrwxrwxrwx root root 2014-01-02 11:49 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-02 11:49 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-01-02 11:49 backup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-01-02 11:49 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-01-02 11:49 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-01-02 11:49 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-01-02 11:49 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-01-02 11:49 efs -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-01-02 11:49 fota -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-01-02 11:49 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-01-02 11:49 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-01-02 11:49 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-01-02 11:49 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-01-02 11:49 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-01-02 11:49 pad -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-01-02 11:49 param -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-01-02 11:49 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-01-02 11:49 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-01-02 11:49 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-01-02 11:49 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-01-02 11:49 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-01-02 11:49 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-01-02 11:49 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-01-02 11:49 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-01-02 11:49 userdata -> /dev/block/mmcblk0p25
[email protected]:/dev/block/platform/msm_sdcc.1/by-name #
Note especially the boot, recovery, system, data and cache partitions…
Code:
lrwxrwxrwx root root 2014-01-02 11:49 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-02 11:49 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-01-02 11:49 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-01-02 11:49 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-01-02 11:49 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-01-02 11:49 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-01-02 11:49 userdata -> /dev/block/mmcblk0p25
Many thanks to Rwilco12 for SGS5 support: http://www.rwilco12.com/
Also thanks to Krang for consolidating Rwilco12’s SGS5 links: http://www.rwilco12.com/forum/member.php?action=profile&uid=450
sendust7 said:
I know --- the bootloader is locked. But I still had to prove it to myself. And the info provided here may be useful to developers as well as to end-users.
Here is my story:
Running stock KK 4.4.2 (NCE) on my G900A, I successfully rooted using GeoHot’s towelroot https://towelroot.com/.
Then I froze the AT&T software updater app via Titanium Backup Pro --- since there is presently no way to re-root after updating.
Then I modified the stock recovery image to enable “adbd” (Android Debug Bridge daemon). Here’s a brief description of the process:
Running ADB with root and busybox installed, I created directory: /sdcard/Boot and did this:
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/Boot/recovery.img
Then on Windows, I unpacked recovery.img to kernel and /ramdisk and modified the /ramdisk/init.rc script as follows:
Code:
service recovery /sbin/recovery
service adbd /sbin/adbd recovery
[COLOR="Blue"]
# [email protected] (09 Dec 2014)
# disabled
# [email protected] (09 Dec 2014)
[/COLOR]
socket adbd stream 660 system system
##++ Security R&D Group
service qrngd /system/bin/qrngd -f
class load_ode_env
user root
group root
oneshot
Then I repacked kernel and modified /ramdisk to recovery-repack.img, dropped it into /sdcard/Boot and flashed it to the recovery partition from 4.4.2 via ADB:
Code:
dd if=/sdcard/Boot/recovery-repack.img of=/dev/block/mmcblk0p16
When I rebooted, my phone returned an error message and rebooted again, this time to download mode. Oh well, I was really hoping to sneak this one past AT&T.
Somewhat nervous, I scoured the web for two days in search of a decent stock NCE build to recover my G900A. But all of the links were slow, flaky, costly and/or plagued with ads --- except for this one…
NCE Stock TAR with md5: http://www.rwilco12.com/forum/showthread.php?tid=883
Odin versions (esp. v1.85 --- considered the most stable):
http://www.rwilco12.com/forum/showthread.php?tid=101
So I downloaded the 1.5GB zip, decompressed to: “G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5”
and ran Odin v1.85 with:
“\{Path-to}\G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5”
in the PDA slot with Auto Reboot and F. Reset Time checked and no others checked except for PDA. Execution was flawless (ref. image below) and my G900A gracefully rebooted to stock KK 4.4.2--- with all of my installed apps, data and settings intact. And I quickly recovered root by re-launching the towelroot APK.
Of course I did lose busybox since it installs under /system/xbin. No problem, I just went to the BB app I had installed earlier and reinstalled BB from there.
Note: When I stripped off the .md5 suffix and opened the resulting .tar file with 7zip, an error message was returned but the file listing was still shown:
Note the absence of a data image --- a good thing if you have installed apps etc.
Something else I found helpful is the G900A partition map. Navigating to /dev/block/platform/msm_sdcc.1/by-name …
Code:
cd /dev/block/platform/msm_sdcc.1/by-name
[email protected]:/dev/block/platform/msm_sdcc.1/by-name # ls -ld *
ls -ld *
lrwxrwxrwx root root 2014-01-02 11:49 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-02 11:49 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-01-02 11:49 backup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-01-02 11:49 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-01-02 11:49 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-01-02 11:49 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-01-02 11:49 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-01-02 11:49 efs -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-01-02 11:49 fota -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-01-02 11:49 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-01-02 11:49 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-01-02 11:49 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-01-02 11:49 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-01-02 11:49 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-01-02 11:49 pad -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-01-02 11:49 param -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-01-02 11:49 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-01-02 11:49 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-01-02 11:49 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-01-02 11:49 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-01-02 11:49 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-01-02 11:49 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-01-02 11:49 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-01-02 11:49 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-01-02 11:49 userdata -> /dev/block/mmcblk0p25
[email protected]:/dev/block/platform/msm_sdcc.1/by-name #
Note especially the boot, recovery, system, data and cache partitions…
Code:
lrwxrwxrwx root root 2014-01-02 11:49 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-02 11:49 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-01-02 11:49 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-01-02 11:49 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-01-02 11:49 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-01-02 11:49 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-01-02 11:49 userdata -> /dev/block/mmcblk0p25
Many thanks to Rwilco12 for SGS5 support: http://www.rwilco12.com/
Also thanks to Krang for consolidating Rwilco12’s SGS5 links: http://www.rwilco12.com/forum/member.php?action=profile&uid=450
Click to expand...
Click to collapse
Actually a little searching on the forums and you'll find a very simple painless way to reroot after the update, also odin 3.09 or 3.10 is the current version. And if you also search for safestrap in the forums you'll find recovery. You have provided a lot of info here thanks for that but could have saved yourself a lot of grief and time by searching first
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Question, did this return the phone to stock completely? Removing root and safestrap?
can not locate
cstayton said:
Actually a little searching on the forums and you'll find a very simple painless way to reroot after the update, also odin 3.09 or 3.10 is the current version. And if you also search for safestrap in the forums you'll find recovery. You have provided a lot of info here thanks for that but could have saved yourself a lot of grief and time by searching first
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
Safestrap is not available for the SM-G900A? i can not find any.
These are the partitions for the UnitedStates Cricket Desire 510 if anybody needs them
[email protected]_a11ul8x26:/ $ ls -al /dev/block/bootdevice/by-name
ls -al /dev/block/bootdevice/by-name
lrwxrwxrwx root root 2014-12-31 16:00 adsp -> /dev/block/mmcblk
0p16
lrwxrwxrwx root root 2014-12-31 16:00 board_info -> /dev/block/
mmcblk0p3
lrwxrwxrwx root root 2014-12-31 16:00 boot -> /dev/block/mmcblk
0p40
lrwxrwxrwx root root 2014-12-31 16:00 cache -> /dev/block/mmcbl
k0p42
lrwxrwxrwx root root 2014-12-31 16:00 carrier -> /dev/block/mmc
blk0p37
lrwxrwxrwx root root 2014-12-31 16:00 cdma_record -> /dev/block
/mmcblk0p33
lrwxrwxrwx root root 2014-12-31 16:00 control -> /dev/block/mmc
blk0p30
lrwxrwxrwx root root 2014-12-31 16:00 custdata -> /dev/block/mm
cblk0p22
lrwxrwxrwx root root 2014-12-31 16:00 ddr -> /dev/block/mmcblk0
p14
lrwxrwxrwx root root 2014-12-31 16:00 debug_config -> /dev/bloc
k/mmcblk0p28
lrwxrwxrwx root root 2014-12-31 16:00 devlog -> /dev/block/mmcb
lk0p38
lrwxrwxrwx root root 2014-12-31 16:00 dsps -> /dev/block/mmcblk
0p15
lrwxrwxrwx root root 2014-12-31 16:00 extra -> /dev/block/mmcbl
k0p32
lrwxrwxrwx root root 2014-12-31 16:00 fataldevlog -> /dev/block
/mmcblk0p27
lrwxrwxrwx root root 2014-12-31 16:00 fsc -> /dev/block/mmcblk0
p34
lrwxrwxrwx root root 2014-12-31 16:00 fsg -> /dev/block/mmcblk0
p19
lrwxrwxrwx root root 2014-12-31 16:00 hboot -> /dev/block/mmcbl
k0p11
lrwxrwxrwx root root 2014-12-31 16:00 local -> /dev/block/mmcbl
k0p31
lrwxrwxrwx root root 2014-12-31 16:00 mfg -> /dev/block/mmcblk0
p5
lrwxrwxrwx root root 2014-12-31 16:00 misc -> /dev/block/mmcblk
0p24
lrwxrwxrwx root root 2014-12-31 16:00 modem_st1 -> /dev/block/m
mcblk0p25
lrwxrwxrwx root root 2014-12-31 16:00 modem_st2 -> /dev/block/m
mcblk0p26
lrwxrwxrwx root root 2014-12-31 16:00 pdata -> /dev/block/mmcbl
k0p29
lrwxrwxrwx root root 2014-12-31 16:00 pg1fs -> /dev/block/mmcbl
k0p2
lrwxrwxrwx root root 2014-12-31 16:00 pg2fs -> /dev/block/mmcbl
k0p6
lrwxrwxrwx root root 2014-12-31 16:00 radio -> /dev/block/mmcbl
k0p20
lrwxrwxrwx root root 2014-12-31 16:00 radio_config -> /dev/bloc
k/mmcblk0p18
lrwxrwxrwx root root 2014-12-31 16:00 recovery -> /dev/block/mm
cblk0p41
lrwxrwxrwx root root 2014-12-31 16:00 reserve -> /dev/block/mmc
blk0p39
lrwxrwxrwx root root 2014-12-31 16:00 reserve_1 -> /dev/block/m
mcblk0p4
lrwxrwxrwx root root 2014-12-31 16:00 reserve_2 -> /dev/block/m
mcblk0p23
lrwxrwxrwx root root 2014-12-31 16:00 rpm -> /dev/block/mmcblk0
p8
lrwxrwxrwx root root 2014-12-31 16:00 sbl1 -> /dev/block/mmcblk
0p1
lrwxrwxrwx root root 2014-12-31 16:00 sbl1_update -> /dev/block
/mmcblk0p7
lrwxrwxrwx root root 2014-12-31 16:00 sdi -> /dev/block/mmcblk0
p10
lrwxrwxrwx root root 2014-12-31 16:00 skylink -> /dev/block/mmc
blk0p36
lrwxrwxrwx root root 2014-12-31 16:00 sp1 -> /dev/block/mmcblk0
p12
lrwxrwxrwx root root 2014-12-31 16:00 ssd -> /dev/block/mmcblk0
p35
lrwxrwxrwx root root 2014-12-31 16:00 system -> /dev/block/mmcb
lk0p43
lrwxrwxrwx root root 2014-12-31 16:00 tool_diag -> /dev/block/m
mcblk0p21
lrwxrwxrwx root root 2014-12-31 16:00 tz -> /dev/block/mmcblk0p
9
lrwxrwxrwx root root 2014-12-31 16:00 userdata -> /dev/block/mm
cblk0p44
lrwxrwxrwx root root 2014-12-31 16:00 wcnss -> /dev/block/mmcbl
k0p17
lrwxrwxrwx root root 2014-12-31 16:00 wifi -> /dev/block/mmcblk
0p13
[email protected]_a11ul8x26:/ $
Pretty sure the few 510 devs that we do have are already aware of this.
HampTheToker said:
Pretty sure the few 510 devs that we do have are already aware of this.
Click to expand...
Click to collapse
Yep, we sure are lol.. Regular users really wouldn't have a need for this type of information.
Yes i understand but there are people who build roms that donnot know how to do this i am a dev myself and didnt know how to do this when i first started building roms
Hi
can any one verify if the list of my partition is correct and the name matches with the mmcblk0pxx, my vie-l29 was unbricked and recived an erase_emmc
it boot but instable and wifi and sound not working
lrwxrwxrwx root root 1970-01-02 06:44 3rdmodem -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-02 06:44 3rdmodemnvm -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 06:44 3rdmodemnvmbkp -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 06:44 boot -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-02 06:44 cache -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-02 06:44 cust -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-02 06:44 dfx -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-02 06:44 dts -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-02 06:44 fastboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 06:44 frp -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 06:44 fw_hifi -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-02 06:44 fw_lpm3 -> /dev/block/mmcblk0p3
lrw-rw---- system system 1970-01-02 06:44 hisitest0 -> /dev/block/mmcblk0p37
lrw-rw---- system system 1970-01-02 06:44 hisitest1 -> /dev/block/mmcblk0p38
lrw-rw---- system system 1970-01-02 06:44 hisitest2 -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-02 06:44 misc -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 06:44 modem -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-02 06:44 modem_dsp -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-02 06:44 modem_dtb -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-02 06:44 modem_om -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 06:44 modemnvm_backup -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 06:44 modemnvm_factory -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 06:44 modemnvm_img -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 06:44 modemnvm_system -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 06:44 modemnvm_update -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 06:44 nvme -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 06:44 oeminfo -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 06:44 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 06:44 recovery -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-02 06:44 recovery2 -> /dev/block/mmcblk0p22
lrw-rw---- system system 1970-01-02 06:44 reserved1 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 06:44 reserved2 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 06:44 secure_storage -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 06:44 sensorhub -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-02 06:44 splash -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 06:44 splash2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 06:44 system -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-02 06:44 teeos -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 06:44 trustfirmware -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-02 06:44 userdata -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-02 06:44 vrl -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 06:44 vrl_backup -> /dev/block/mmcblk0p2
thank you
any one pls , just share your partition list of your working p9 plus
DUMP - OnePlus 6T [OOS 9.0.5/6]
{
"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"
}
boot.img will help get TWRP issues actually do something with their device. ?!
system.img and vendor.img will help with ports , dev , ect.
these zips are not "flashable" !!! just compressed files
Download: DUMP - OnePlus 6T [OOS 9.0.5]
Download: DUMP - OnePlus 6T [OOS 9.0.6]
Download: DUMP - OnePlus 6T [OOS 9.0.7]
My dump & My G-D upload
thx for the dump. will try to boot the system on my op5 since with openbeta he got treble support
S3V3N said:
DUMP - OnePlus 6T [OOS 9.0.5]
boot.img will help get TWRP issues actually do something with their device. ?!
system.img and vendor.img will help with ports , dev , ect.
these zips are not "flashable" !!! just compressed files
Download: DUMP - OnePlus 6T [OOS 9.0.5]
My dump & My G-D upload
Click to expand...
Click to collapse
Yes, I think this is all I need to fix my device. Oneplus sent me a device that wouldn't boot. L2 Tech remoted in to my pc and said apparently the firmware hasn't been flashed to the device. After 5 minutes of troubleshooting they weren't able to get it to flash.
Eventually I was able to get it to register to my pc and this might be what fixes it for me. Downloading as I type this. Unfortunately I already ordered a replacement that shipped an hour ago and have a refund process to return this one started... At least I can play with it til the new one arrives.
Code:
drwxr-xr-x 2 root root 2060 1970-01-01 04:52 .
drwxr-xr-x 3 root root 2200 1970-01-01 04:52 ..
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 ALIGN_TO_128K_1 -> /dev/block/sdd1
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 ALIGN_TO_128K_2 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 ImageFv -> /dev/block/sde72
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 LOGO_a -> /dev/block/sde20
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 LOGO_b -> /dev/block/sde48
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 abl_a -> /dev/block/sde8
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 abl_b -> /dev/block/sde36
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 aging -> /dev/block/sde58
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 aop_a -> /dev/block/sde1
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 aop_b -> /dev/block/sde29
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 apdp -> /dev/block/sde63
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 bluetooth_a -> /dev/block/sde5
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 bluetooth_b -> /dev/block/sde33
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 boot_a -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 boot_b -> /dev/block/sde39
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 cdt -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 cmnlib64_a -> /dev/block/sde13
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 cmnlib64_b -> /dev/block/sde41
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 cmnlib_a -> /dev/block/sde12
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 cmnlib_b -> /dev/block/sde40
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 config -> /dev/block/sda12
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 ddr -> /dev/block/sdd3
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 devcfg_a -> /dev/block/sde14
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 devcfg_b -> /dev/block/sde42
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 devinfo -> /dev/block/sde61
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 dip -> /dev/block/sde62
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 dsp_a -> /dev/block/sde9
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 dsp_b -> /dev/block/sde37
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 dtbo_a -> /dev/block/sde18
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 dtbo_b -> /dev/block/sde46
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 frp -> /dev/block/sda6
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 fsc -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 fsg -> /dev/block/sdf4
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_4j1ed_a -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_4j1ed_b -> /dev/block/sde49
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_4u1ea_a -> /dev/block/sde22
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_4u1ea_b -> /dev/block/sde50
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs3_a -> /dev/block/sde23
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs3_b -> /dev/block/sde51
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs4_a -> /dev/block/sde24
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs4_b -> /dev/block/sde52
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs5_a -> /dev/block/sde25
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs5_b -> /dev/block/sde53
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs6_a -> /dev/block/sde26
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs6_b -> /dev/block/sde54
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs7_a -> /dev/block/sde27
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs7_b -> /dev/block/sde55
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs8_a -> /dev/block/sde28
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs8_b -> /dev/block/sde56
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 hyp_a -> /dev/block/sde3
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 hyp_b -> /dev/block/sde31
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 keymaster_a -> /dev/block/sde10
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 keymaster_b -> /dev/block/sde38
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 keystore -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 limits -> /dev/block/sde67
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 logdump -> /dev/block/sde71
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 logfs -> /dev/block/sde69
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 mdtp_a -> /dev/block/sde7
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 mdtp_b -> /dev/block/sde35
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 mdtpsecapp_a -> /dev/block/sde6
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 mdtpsecapp_b -> /dev/block/sde34
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 minidump -> /dev/block/sde57
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 misc -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 modem_a -> /dev/block/sde4
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 modem_b -> /dev/block/sde32
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 modemst1 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 modemst2 -> /dev/block/sdf3
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 msadp -> /dev/block/sde64
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 odm_a -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 odm_b -> /dev/block/sda16
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 oem_dycnvbk -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 oem_stanvbk -> /dev/block/sda9
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 op1 -> /dev/block/sde59
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 op2 -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 param -> /dev/block/sda4
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 persist -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 qupfw_a -> /dev/block/sde15
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 qupfw_b -> /dev/block/sde43
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 reserve1 -> /dev/block/sda10
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 reserve2 -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 sec -> /dev/block/sde60
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 splash -> /dev/block/sde66
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 spunvm -> /dev/block/sde65
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 ssd -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 sti -> /dev/block/sde70
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 storsec_a -> /dev/block/sde19
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 storsec_b -> /dev/block/sde47
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 system_a -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 system_b -> /dev/block/sda14
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 toolsfv -> /dev/block/sde68
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 tz_a -> /dev/block/sde2
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 tz_b -> /dev/block/sde30
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 userdata -> /dev/block/sda17
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 vbmeta_a -> /dev/block/sde17
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 vbmeta_b -> /dev/block/sde45
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 vendor_a -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 vendor_b -> /dev/block/sde44
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 xbl_a -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 xbl_b -> /dev/block/sdc1
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 xbl_config_a -> /dev/block/sdb2
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 xbl_config_b -> /dev/block/sdc2
OnePlus6T:/ #
if someone need the partition above
i owned the oneplus 6T since yesterday. i will make my Eragon Custom Rom for it very soon
@skeleton1911
You're right
Because I am just collecting for the purchase of this phone, I unpacked the firmware and shared it. My mistake
My 6T is stuck in boot loop. It was rooted and had blue spark installed. Can I use these files to recover, how?
You take the boot.img .
Then with buttons hold power and vol+ and vol- until the phone reboots
Then you are in Fastboot Mode
Via ADB flash the boot.img
Fastboot flash boot boot.img
pramathesh said:
My 6T is stuck in boot loop. It was rooted and had blue spark installed. Can I use these files to recover, how?
Click to expand...
Click to collapse
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
---------- Post added at 12:40 PM ---------- Previous post was at 12:37 PM ----------
Hold power and vol-+ and vol-
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
skeleton1911 said:
You take the boot.img .
Then with buttons hold power and vol+ .
When the phone boots again release power but still hold vol+
Then you are in Fastboot Mode
Via ADB flash the boot.img
Fastboot flash boot boot.img
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
Click to expand...
Click to collapse
Let me give this a try and report. My guess is that the 9.0.5 update was applied automatically thereby messing my phone. Also, if the phone was 9.0.4 the 9.0.5 image would work fine, right?
pramathesh said:
Let me give this a try and report. My guess is that the 9.0.5 update was applied automatically thereby messing my phone. Also, if the phone was 9.0.4 the 9.0.5 image would work fine, right?
Click to expand...
Click to collapse
Read above again. Hold all buttons.
Also 9.0.5 is on slot b
And 9.0.4 on a.
So if it don't work you can just set slot b
Fastboot --set-active=b
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
skeleton1911 said:
Read above again. Hold all buttons.
Also 9.0.5 is on slot b
And 9.0.4 on a.
So if it don't work you can just set slot b
Fastboot --set-active=b
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
Click to expand...
Click to collapse
So, if I get this right 9.0.5 can be flashed in a and b either. It a cause of concern then, right?
You can flash it in both yes. But useless . If it's on b it's fine
pramathesh said:
So, if I get this right 9.0.5 can be flashed in a and b either. It a cause of concern then, right?
Click to expand...
Click to collapse
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
skeleton1911 said:
You can flash it in both yes. But useless . If it's on b it's fine
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
Click to expand...
Click to collapse
Downloading the files now. Hoping it works fine, let's hope you are still online just in case something goes off!
---------- Post added at 05:39 PM ---------- Previous post was at 05:31 PM ----------
skeleton1911 said:
You can flash it in both yes. But useless . If it's on b it's fine
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
Click to expand...
Click to collapse
I have a weird problem of the device not getting detected. This is the same machine I had used to root the device earlier. No device number is getting shown but the reboot command did work on the terminal
pramathesh said:
Downloading the files now. Hoping it works fine, let's hope you are still online just in case something goes off!
---------- Post added at 05:39 PM ---------- Previous post was at 05:31 PM ----------
I have a weird problem of the device not getting detected. This is the same machine I had used to root the device earlier. No device number is getting shown but the reboot command did work on the terminal
Click to expand...
Click to collapse
only use adb fastboot. sdk . dont use a program etc.
if you want i can take a look, send me a private message, we go via teamviewer ( i need id and password of teamviewer then)
skeleton1911 said:
only use adb fastboot. sdk . dont use a program etc.
if you want i can take a look, send me a private message, we go via teamviewer ( i need id and password of teamviewer then)
Click to expand...
Click to collapse
Using minimal fastboot and adb. The device number isn't shown but fasboot reboot did work on it. Bluespark is showing partition b is active. So I am guessing that is where I have to flash the boot.img. I am happy to let you take over my PC and let you handle it. Let's get over PM, shall we?
pramathesh said:
Using minimal fastboot and adb. The device number isn't shown but fasboot reboot did work on it. Bluespark is showing partition b is active. So I am guessing that is where I have to flash the boot.img. I am happy to let you take over my PC and let you handle it. Let's get over PM, shall we?
Click to expand...
Click to collapse
yes. send me
skeleton1911 said:
yes. send me
Click to expand...
Click to collapse
fastboot did work. Just tried that before sending you a PM. I cannot thank you enough for saving my life here <3
---------- Post added at 06:03 PM ---------- Previous post was at 06:00 PM ----------
Restarting the phone is causing the loop to happen again. Any way to fix that?
Wifi isn't switching on either. Stuck pretty bad here now
pramathesh said:
fastboot did work. Just tried that before sending you a PM. I cannot thank you enough for saving my life here <3
---------- Post added at 06:03 PM ---------- Previous post was at 06:00 PM ----------
Restarting the phone is causing the loop to happen again. Any way to fix that?
Wifi isn't switching on either. Stuck pretty bad here now
Click to expand...
Click to collapse
i will help you.
now send me pm and we will manage it. (teamviewer)
Is this full dump include all partition? I used other fastboot stock rom and somehow end up losing my VOLTE ON SIM slot 1 but when i switch to sim slot 2 everything work...kinda frustrating...kinda news to OP
vouch post for @skeleton1911. Cannot thank you enough for going out of your way to help me resolve the issue
_BГ@ckθut said:
Is this full dump include all partition? I used other fastboot stock rom and somehow end up losing my VOLTE ON SIM slot 1 but when i switch to sim slot 2 everything work...kinda frustrating...kinda news to OP
Click to expand...
Click to collapse
no. not all.
i think he did not own the phone and therefore he dont has all...
BTW little tip:
Never ever flash the modem_st1 and modem_st2 image files.! after that the risk is high to lose imei numbers.
pramathesh said:
vouch post for @skeleton1911. Cannot thank you enough for going out of your way to help me resolve the issue
Click to expand...
Click to collapse
your welcome!
Hi
I want to create a backup of my ASUS Zenfone 8 using images from the partitions which I can then later flash using fastboot to restore the installation
But I do not know which of the partitions are mandatory to backup/restore an installation
In the payload.bin file used to install the ROM (AospExtended 9.x) there are these files that are used to install the ROM:
[[email protected] ~]# ls -lh /data/backup/ASUS_ZENFONE8/payload-dumper/test
total 3.3G
-rw-r--r--. 1 root root 96M Mar 11 11:17 boot.img
-rw-r--r--. 1 root root 24M Mar 11 11:17 dtbo.img
-rw-r--r--. 1 root root 1.4M Mar 11 11:17 odm.img
-rw-r--r--. 1 root root 307M Mar 11 11:18 product.img
-rw-r--r--. 1 root root 445M Mar 11 11:18 system_ext.img
-rw-r--r--. 1 root root 1.2G Mar 11 11:18 system.img
-rw-r--r--. 1 root root 8.0K Mar 11 11:18 vbmeta.img
-rw-r--r--. 1 root root 4.0K Mar 11 11:18 vbmeta_system.img
-rw-r--r--. 1 root root 96M Mar 11 11:19 vendor_boot.img
-rw-r--r--. 1 root root 1.2G Mar 11 11:19 vendor.img
[[email protected] ~]#
Some of the file names match a block device name in /dev/block/by-name but not all:
Spoiler: ls -l /dev/block/by-name
ASUS_I006D:/storage/emulated/0 #
ASUS_I006D:/storage/emulated/0 # ls -l /dev/block/by-name
total 0
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 ADF -> /dev/block/sda12
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 ALIGN_TO_128K_1 -> /dev/block/sdd1
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 ALIGN_TO_128K_2 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 APD -> /dev/block/sda13
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 abl_a -> /dev/block/sde8
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 abl_b -> /dev/block/sde33
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 aop_a -> /dev/block/sde1
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 aop_b -> /dev/block/sde26
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 apdp -> /dev/block/sde52
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 asdf -> /dev/block/sda9
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 asusfw_a -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 asusfw_b -> /dev/block/sda16
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 asuskey -> /dev/block/sdg2
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 asuskey2 -> /dev/block/sdg3
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 asuskey3 -> /dev/block/sdg4
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 asuskey4 -> /dev/block/sdg5
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 asuskey5 -> /dev/block/sdg6
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 asuskey6 -> /dev/block/sdg7
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 batinfo -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 bluetooth_a -> /dev/block/sde5
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 bluetooth_b -> /dev/block/sde30
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 boot_a -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 boot_b -> /dev/block/sde36
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 cdt -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 connsec -> /dev/block/sde63
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 cpucp_a -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 cpucp_b -> /dev/block/sde46
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 ddr -> /dev/block/sdd3
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 devcfg_a -> /dev/block/sde12
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 devcfg_b -> /dev/block/sde37
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 devinfo -> /dev/block/sde50
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 dip -> /dev/block/sde51
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 dsp_a -> /dev/block/sde9
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 dsp_b -> /dev/block/sde34
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 dtbo_a -> /dev/block/sde15
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 dtbo_b -> /dev/block/sde40
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 factory -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 fde -> /dev/block/sda6
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 featenabler_a -> /dev/block/sde22
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 featenabler_b -> /dev/block/sde47
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 frp -> /dev/block/sda5
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 fsc -> /dev/block/sdf6
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 fsg -> /dev/block/sdf4
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 fsgCA -> /dev/block/sdf5
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 ftm -> /dev/block/sda14
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 gpt -> /dev/block/sda10
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 hyp_a -> /dev/block/sde3
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 hyp_b -> /dev/block/sde28
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 imagefv_a -> /dev/block/sde17
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 imagefv_b -> /dev/block/sde42
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 keymaster_a -> /dev/block/sde10
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 keymaster_b -> /dev/block/sde35
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 keystore -> /dev/block/sda4
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 limits -> /dev/block/sde54
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 limits-cdsp -> /dev/block/sde55
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 logdump -> /dev/block/sde57
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 logfs -> /dev/block/sde56
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 mdcompress -> /dev/block/sde62
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 mdtp_a -> /dev/block/sde7
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 mdtp_b -> /dev/block/sde32
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 mdtpsecapp_a -> /dev/block/sde6
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 mdtpsecapp_b -> /dev/block/sde31
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 metadata -> /dev/block/sda22
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 misc -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 modem_a -> /dev/block/sde4
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 modem_b -> /dev/block/sde29
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 modemst1 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 modemst2 -> /dev/block/sdf3
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 multiimgoem_a -> /dev/block/sde20
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 multiimgoem_b -> /dev/block/sde45
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 persist -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 qmcs -> /dev/block/sde24
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 qupfw_a -> /dev/block/sde13
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 qupfw_b -> /dev/block/sde38
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 qweslicstore_a -> /dev/block/sde25
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 qweslicstore_b -> /dev/block/sde49
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 rtice -> /dev/block/sde66
lrwxrwxrwx 1 root root 14 1970-01-04 04:42 sda -> /dev/block/sda
lrwxrwxrwx 1 root root 14 1970-01-04 04:42 sdb -> /dev/block/sdb
lrwxrwxrwx 1 root root 14 1970-01-04 04:42 sdc -> /dev/block/sdc
lrwxrwxrwx 1 root root 14 1970-01-04 04:42 sdd -> /dev/block/sdd
lrwxrwxrwx 1 root root 14 1970-01-04 04:42 sde -> /dev/block/sde
lrwxrwxrwx 1 root root 14 1970-01-04 04:42 sdf -> /dev/block/sdf
lrwxrwxrwx 1 root root 14 1970-01-04 04:42 sdg -> /dev/block/sdg
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 secdata -> /dev/block/sde60
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 shrm_a -> /dev/block/sde18
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 shrm_b -> /dev/block/sde43
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 splash -> /dev/block/sde53
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 spunvm -> /dev/block/sde65
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 ssd -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 storsec -> /dev/block/sde58
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 super -> /dev/block/sda19
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 sysconf -> /dev/block/sdg1
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 sysinfo -> /dev/block/sda11
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 tz_a -> /dev/block/sde2
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 tz_b -> /dev/block/sde27
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 tzsc -> /dev/block/sde64
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 uefisecapp_a -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 uefisecapp_b -> /dev/block/sde41
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 uefivarstore -> /dev/block/sde59
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 userdata -> /dev/block/sda23
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 vbmeta_a -> /dev/block/sde14
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 vbmeta_b -> /dev/block/sde39
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 vbmeta_system_a -> /dev/block/sda20
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 vbmeta_system_b -> /dev/block/sda21
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 vendor_boot_a -> /dev/block/sde23
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 vendor_boot_b -> /dev/block/sde48
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 vm-bootsys_a -> /dev/block/sde19
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 vm-bootsys_b -> /dev/block/sde44
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 vm-data -> /dev/block/sde61
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 xbl_a -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 xbl_b -> /dev/block/sdc1
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 xbl_config_a -> /dev/block/sdb2
lrwxrwxrwx 1 root root 15 1970-01-04 04:42 xbl_config_b -> /dev/block/sdc2
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 xrom_a -> /dev/block/sda17
lrwxrwxrwx 1 root root 16 1970-01-04 04:42 xrom_b -> /dev/block/sda18
ASUS_I006D:/storage/emulated/0 #
Which partitions must I backup to be able to restore an OS installation to the phone?
Which partition is used for what?
regards
Bernd
[Update 12.03.2022 12:30]
I think I found it:
The physical partitions to backup are (either _a or _b):
boot
dtbo
vbmeta
vbmeta_system
vendor_boot
and
super
The other partitions
odm
product
vendor
system
system_ext
are logical devices (also with the ending _a or _b) on the physical partition super
Would be great if some could confirm or correct this ....