[tool][mod][OP6T] Splash screen modification [linux] - OnePlus 6T Guides, News, & Discussion
First, most - if not all - the credits go to @makers_mark.
Please read https://forum.xda-developers.com/oneplus-6/themes/wip-splash-screen-image-injector-t3800836 for technical details. I have just tried this on our OP6T and made slight modifications to the source code of the application.
This linux tool allows you to extract splash screen images from a raw dump of the LOGO partition.
You can then modify the images to your liking and repack them into a raw LOGO partition.
You do need at least basic linux knowledge/skill and you must have a working adb. If you don't know what this is, then this is not a thread for you.
Note: it should be very easy to compile the program under Windows and use it from Windows ... but I do not use Windows myself, I am a linux guy ... feel free to (re)use this and compile under Windows. Instructions below should be reasonably similar if you use PowerShell on Windows.
Note that the phone has 2 LOGO partitions ... more about that below.
Attached zip file contains the following:
- original.logo.bin (raw extract from the original 6T LOGO partition)
- lodepng.c, lodepng.h, OP6logo.c (C source of the utility)
- op6 (linux executable, compiled from source code)
- 0.png, 1.png, ..., 27.png (png splash screen files extracted with the tool from the original.logo.bin)
How to compile the utility (if you would want to do that yourself): download attached zip file, create a new directory and unzip the downloaded zip file into that directory. Then compile from source:
Code:
> mkdir splash
> cd splash
> unzip splash.zip
> cc *.c -o op6
After this you will have an executable called "op6". The zip file already contains a compiled op6, so you do not necessarily need to compile it yourself.
How to use:
1) First, make a raw dump of the LOGO partition. To do that, reboot your phone into twrp (see for example https://oneplus.gadgethacks.com/how-to/install-twrp-recovery-your-oneplus-6t-0190296/ for instructions). With the phone in twrp, open a linux shell, then do:
Code:
> adb shell
# dd if=/dev/block/bootdevice/by-name/LOGO_a of=/data/original.logo.bin
# exit
> adb pull /data/original.logo.bin
You should now have a file called "original.logo.bin" which is exactly 16MB in size. Copy this file to the directory which contains your op6 tool. Also make a backup of the file so you have a copy of the stock LOGO partition.
2) Second, extract (using the op6 tool) the png images from the raw logo dump. To do that, open a linux shell, then do:
Code:
> cd splash
> ./op6 -i original.logo.bin -d
You should see output like:
Code:
#01: Offset:0, Header=SPLASH!!, Width=1080, Height=1920, Data Length=245032, Special=1, Name=0.png, Metadata=, 6220800 decoded bytes
#02: Offset:249856, Header=SPLASH!!, Width=536, Height=60, Data Length=9162, Special=1, Name=1.png, Metadata=, 96480 decoded bytes
#03: Offset:266240, Header=SPLASH!!, Width=1080, Height=1920, Data Length=187698, Special=1, Name=2.png, Metadata=, 6220800 decoded bytes
#04: Offset:458752, Header=SPLASH!!, Width=1080, Height=1920, Data Length=55422, Special=1, Name=3.png, Metadata=, 6220800 decoded bytes
#05: Offset:520192, Header=SPLASH!!, Width=1080, Height=1920, Data Length=187698, Special=1, Name=4.png, Metadata=, 6220800 decoded bytes
#06: Offset:712704, Header=SPLASH!!, Width=392, Height=66, Data Length=6744, Special=1, Name=5.png, Metadata=, 77616 decoded bytes
#07: Offset:724992, Header=SPLASH!!, Width=487, Height=69, Data Length=8478, Special=1, Name=6.png, Metadata=, 100809 decoded bytes
#08: Offset:741376, Header=SPLASH!!, Width=1080, Height=1920, Data Length=119304, Special=1, Name=7.png, Metadata=, 6220800 decoded bytes
#09: Offset:868352, Header=SPLASH!!, Width=1080, Height=2160, Data Length=279186, Special=1, Name=8.png, Metadata=, 6998400 decoded bytes
#10: Offset:1155072, Header=SPLASH!!, Width=536, Height=60, Data Length=9162, Special=1, Name=9.png, Metadata=, 96480 decoded bytes
#11: Offset:1171456, Header=SPLASH!!, Width=1080, Height=2160, Data Length=193798, Special=1, Name=10.png, Metadata=, 6998400 decoded bytes
#12: Offset:1372160, Header=SPLASH!!, Width=1080, Height=2160, Data Length=61522, Special=1, Name=11.png, Metadata=, 6998400 decoded bytes
#13: Offset:1441792, Header=SPLASH!!, Width=1080, Height=2160, Data Length=193798, Special=1, Name=12.png, Metadata=, 6998400 decoded bytes
#14: Offset:1642496, Header=SPLASH!!, Width=392, Height=66, Data Length=6744, Special=1, Name=13.png, Metadata=, 77616 decoded bytes
#15: Offset:1654784, Header=SPLASH!!, Width=487, Height=69, Data Length=8478, Special=1, Name=14.png, Metadata=, 100809 decoded bytes
#16: Offset:1671168, Header=SPLASH!!, Width=1080, Height=2160, Data Length=125402, Special=1, Name=15.png, Metadata=, 6998400 decoded bytes
#17: Offset:1802240, Header=SPLASH!!, Width=1080, Height=2280, Data Length=303732, Special=1, Name=16.png, Metadata=, 7387200 decoded bytes
#18: Offset:2113536, Header=SPLASH!!, Width=536, Height=60, Data Length=9162, Special=1, Name=17.png, Metadata=, 96480 decoded bytes
#19: Offset:2129920, Header=SPLASH!!, Width=1080, Height=2280, Data Length=196846, Special=1, Name=18.png, Metadata=, 7387200 decoded bytes
#20: Offset:2334720, Header=SPLASH!!, Width=1080, Height=2280, Data Length=64572, Special=1, Name=19.png, Metadata=, 7387200 decoded bytes
#21: Offset:2404352, Header=SPLASH!!, Width=1080, Height=2280, Data Length=196848, Special=1, Name=20.png, Metadata=, 7387200 decoded bytes
#22: Offset:2609152, Header=SPLASH!!, Width=392, Height=66, Data Length=6744, Special=1, Name=21.png, Metadata=, 77616 decoded bytes
#23: Offset:2621440, Header=SPLASH!!, Width=487, Height=69, Data Length=8478, Special=1, Name=22.png, Metadata=, 100809 decoded bytes
#24: Offset:2637824, Header=SPLASH!!, Width=1080, Height=2280, Data Length=128452, Special=1, Name=23.png, Metadata=, 7387200 decoded bytes
#25: Offset:2772992, Header=SPLASH!!, Width=1080, Height=2340, Data Length=312118, Special=1, Name=24.png, Metadata=, 7581600 decoded bytes
#26: Offset:3092480, Header=SPLASH!!, Width=536, Height=60, Data Length=9162, Special=1, Name=25.png, Metadata=, 96480 decoded bytes
#27: Offset:3108864, Header=SPLASH!!, Width=1080, Height=2340, Data Length=198370, Special=1, Name=26.png, Metadata=, 7581600 decoded bytes
#28: Offset:3313664, Header=SPLASH!!, Width=1080, Height=2340, Data Length=66096, Special=1, Name=27.png, Metadata=, 7581600 decoded bytes
You should now 28 png files in the directory called "0.png", "1.png", ..., "27.png".
3) Third, check the images. Install an image viewer (for example "eog") on your linux distribution and then do:
Code:
> eog *.png
You will be able to view the splash screens one by one (with eog). The png's are also part of attached zip file.
4) Modify any of the png files to your liking. For example, you can use the linux "gimp" image processing tool. But note that you MUST keep the width and height of the images the same as the original sizes.
5) Repack the modified images. To do that, open a linux shell and do:
Code:
> cd splash
> ./op6 -i original.logo.bin -j 0
You will see output like:
Code:
Resolution Offset Name
-------------------------------------------------------------
1080x1920 0 0.png
536x60 249856 1.png
1080x1920 266240 2.png
1080x1920 458752 3.png
1080x1920 520192 4.png
392x66 712704 5.png
487x69 724992 6.png
1080x1920 741376 7.png
1080x2160 868352 8.png
536x60 1155072 9.png
1080x2160 1171456 10.png
1080x2160 1372160 11.png
1080x2160 1441792 12.png
392x66 1642496 13.png
487x69 1654784 14.png
1080x2160 1671168 15.png
1080x2280 1802240 16.png
536x60 2113536 17.png
1080x2280 2129920 18.png
1080x2280 2334720 19.png
1080x2280 2404352 20.png
392x66 2609152 21.png
487x69 2621440 22.png
1080x2280 2637824 23.png
1080x2340 2772992 24.png
536x60 3092480 25.png
1080x2340 3108864 26.png
1080x2340 3313664 27.png
______________________________________
Original filesize: 16.00 MB
Modified filesize: 3.23 MB
-------------------------------------------------------------
And you should have a file called "modified.logo.bin".
6) To flash the new splash screens, reboot your phone back into twrp. Then open a linux shell and do:
Code:
> adb push modified.logo.bin /data/
> adb shell
# dd if=/data/original.logo.bin of=/dev/block/bootdevice/by-name/LOGO_a
# sync
# sync
# reboot
With the last command, your phone will reboot and if all is well you should see your modified splash screens.
If you want to return to stock, just follow step 6 but flash original.logo.bin file.
What's the story with the 2 partitions? 6T uses the A/B partitioning scheme. Read this thread: https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123, if you want more details.
The LOGO partitions are called: LOGO_a and LOGO_b. In the commands above I have used always LOGO_a but obviously you can use LOGO_b as well.
How do you know which partition (A or B) your phone is booting from? Well, that i easy to find out. Boot your phone normally. Open a linux shell and then do:
Code:
> adb shell
$ getprop ro.boot.slot_suffix
And it will say "_a" or "_b" depending on the partition which your phone is booting from. So that determines whether you have to flash LOGO_a or LOGO_b.
Enjoy.
Note: attached there is also a example.zip file with a original.logo.bin file inside. This is an example where the splash screens from One+ have been replaced by black screens with the Google logo. You can straight flash that into the LOGO_a and/or LOGO_b partitions. I have attached also a bootanimation.zip (black Google pixel style) which plays very nicely with this. The bootanimation.zip file should go into /system/media/ on your device.
Big thanks for the proper credit @foobar66. I do not have the time anymore to even find/dissect bootloaders/partitions these days, and thanks for your documentation. I have seen several people walk away with my free information and dedicated work like they didn't steal it and try and make them self a name (I guess). Thank you!
makers_mark said:
Big thanks for the proper credit @foobar66. I do not have the time anymore to even find/dissect bootloaders/partitions these days, and thanks for your documentation. I have seen several people walk away with my free information and dedicated work like they didn't steal it and try and make them self a name (I guess). Thank you!
Click to expand...
Click to collapse
No problem ... that is only normal, decent and polite behavior. We are here to share and learn on XDA.
The program did not work initially on the original.logo.bin from the 6T (segmentation fault). I made a few small mods to the code to make it work.
Can you share some pictures of the splash screens you have changed to?
MishaalRahman said:
Can you share some pictures of the splash screens you have changed to?
Click to expand...
Click to collapse
See attach. I changed 0.png, 8.png, 16.png and 24.png. Note that they all have slightly different sizes !!!
Great work. I was waiting for this.
Quick question: any idea about the unlocked bootloader image location ?
Edit: works fine.
AnoopKumar said:
Great work. I was waiting for this.
Quick question: any idea about the unlocked bootloader image location ?
Edit: works fine.
Click to expand...
Click to collapse
No not precisely, but here is the list of partitions with their names:
Code:
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 ALIGN_TO_128K_1 -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 ALIGN_TO_128K_2 -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 ImageFv -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 LOGO_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 LOGO_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 abl_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 abl_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 aging -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 aop_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 aop_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 apdp -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 bluetooth_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 bluetooth_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 boot_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 boot_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 cdt -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 cmnlib64_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 cmnlib64_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 cmnlib_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 cmnlib_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 config -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 ddr -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 devcfg_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 devcfg_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 devinfo -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 dip -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 dsp_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 dsp_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 dtbo_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 dtbo_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 frp -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 fsc -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 fsg -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 fw_4j1ed_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 fw_4j1ed_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 fw_4u1ea_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 fw_4u1ea_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 fw_ufs3_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 fw_ufs3_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 fw_ufs4_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 fw_ufs4_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 fw_ufs5_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 fw_ufs5_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 fw_ufs6_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 fw_ufs6_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 fw_ufs7_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 fw_ufs7_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 fw_ufs8_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 fw_ufs8_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 hyp_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 hyp_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 keymaster_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 keymaster_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 keystore -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 limits -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 logdump -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 logfs -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 mdtp_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 mdtp_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 mdtpsecapp_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 mdtpsecapp_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 minidump -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 misc -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 modem_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 modem_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 modemst1 -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 modemst2 -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 msadp -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 odm_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 odm_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 oem_dycnvbk -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 oem_stanvbk -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 op1 -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 op2 -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 param -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 persist -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 qupfw_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 qupfw_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 reserve1 -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 reserve2 -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 sec -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 splash -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 spunvm -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 ssd -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 sti -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 storsec_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 storsec_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 system_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 system_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 toolsfv -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 tz_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 tz_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 userdata -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 vbmeta_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 vbmeta_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 vendor_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 16 1970-01-01 08:50 vendor_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 xbl_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 xbl_b -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 xbl_config_a -> /dev/block/[email protected]
0 lrwxrwxrwx 1 root root 15 1970-01-01 08:50 xbl_config_b -> /dev/block/[email protected]
I am just guessing it might be xbl_a and xbl_config_a ... but I am not sure.
I ran a string search using grep on stock fastboot images. No luck.
foobar66 said:
No not precisely, but here is the list of partitions with their names:
I am just guessing it might be xbl_a and xbl_config_a ... but I am not sure.
Click to expand...
Click to collapse
xbl is the eXtensible bootloader. A 64bit elf. Does it contain images ? is it possible ?
AnoopKumar said:
xbl is the eXtensible bootloader. A 64bit elf. Does it contain images ? is it possible ?
Click to expand...
Click to collapse
Hmm ... very difficult. ELF is the executable and linking format. I guess the images are static binaries which get included in the code as hex arrays or part of the ELF file's "data" section. Theoretically possible but I would not start on it ... will take a lot of time to find out.
foobar66 said:
See attach. I changed 0.png, 8.png, 16.png and 24.png. Note that they all have slightly different sizes !!!
Click to expand...
Click to collapse
Do you have this available for download?
dennisbednarz said:
Do you have this available for download?
Click to expand...
Click to collapse
I will add to |OP| ... I have black screens with central Google logo.
What's the splash screen, the one before the boot animation?
NateDev said:
What's the splash screen, the one before the boot animation?
Click to expand...
Click to collapse
Yes
Do you have plans for working on other device??
If yes, please do it for X00T (ASUS Zenfone Max Pro M1)
I'm uploading the stock splash.img here.
https://t.me/ASUSX00TD/76540
Also if you want any other help, here is our device support group
https://t.me/ZenfoneMaxProOfficial
https://t.me/ASUSX00TD
Thanks for taking the time to put this together.
Does anyone have instructions for how to do this on Windows? The only access I have to Linux is through Chrome OS which is still too finicky to get all if this done with.
clarkcant said:
Thanks for taking the time to put this together.
Does anyone have instructions for how to do this on Windows? The only access I have to Linux is through Chrome OS which is still too finicky to get all if this done with.
Click to expand...
Click to collapse
See the attachment. Just rename your LOGO.img to logo.img
Code:
op6t -i logo.img -d //to extract splash images
op6t -i logo.img -j 0 //repack with changes
For OnePlus 6T replace 24.png and 27.png
Click to expand...
Click to collapse
foobar66 said:
I will add to |OP| ... I have black screens with central Google logo.
Click to expand...
Click to collapse
Is the "Splash.zip" file the Google Logo?
Edit: disregard this. I didn't notice the note that was added
Mogul MAXX said:
Do you have plans for working on other device??
If yes, please do it for X00T (ASUS Zenfone Max Pro M1)
I'm uploading the stock splash.img here.
https://t.me/ASUSX00TD/76540
Also if you want any other help, here is our device support group
https://t.me/ZenfoneMaxProOfficial
https://t.me/ASUSX00TD
Click to expand...
Click to collapse
No ...
@foobar66 Thank you very much for this! Works on OP6 as well. My new splash logo
Related
Oneplus 3 partition table
Hi ! I rescently flashed a zip on OP3 i made for my good old Nexus 5, but it failed, as it didnt mounted system and set_perms had failed so. So i started to dig in /dev/block to find where were the system partition and the idea of searching for full partition table crossed my head. So here's what i found : Partitions names are here : Code: /dev/block/platform/soc/624000.ufshc/by-name What i wrote on terminal, using adb shell with root access : Code: [email protected]:/ # ls -al /dev/block/platform/soc/624000.ufshc/by-name lrwxrwxrwx root root 1970-01-18 10:20 LOGO -> /dev/block/sde17 lrwxrwxrwx root root 1970-01-18 10:20 aboot -> /dev/block/sde15 lrwxrwxrwx root root 1970-01-18 10:20 abootbak -> /dev/block/sde16 lrwxrwxrwx root root 1970-01-18 10:20 apdp -> /dev/block/sde30 lrwxrwxrwx root root 1970-01-18 10:20 bluetooth -> /dev/block/sde23 lrwxrwxrwx root root 1970-01-18 10:20 boot -> /dev/block/sde18 lrwxrwxrwx root root 1970-01-18 10:20 boot_aging -> /dev/block/sde19 lrwxrwxrwx root root 1970-01-18 10:20 cache -> /dev/block/sda3 lrwxrwxrwx root root 1970-01-18 10:20 cdt -> /dev/block/sdd2 lrwxrwxrwx root root 1970-01-18 10:20 cmnlib -> /dev/block/sde26 lrwxrwxrwx root root 1970-01-18 10:20 cmnlib64 -> /dev/block/sde28 lrwxrwxrwx root root 1970-01-18 10:20 cmnlib64bak -> /dev/block/sde29 lrwxrwxrwx root root 1970-01-18 10:20 cmnlibbak -> /dev/block/sde27 lrwxrwxrwx root root 1970-01-18 10:20 config -> /dev/block/sda14 lrwxrwxrwx root root 1970-01-18 10:20 ddr -> /dev/block/sdd3 lrwxrwxrwx root root 1970-01-18 10:20 devcfg -> /dev/block/sda6 lrwxrwxrwx root root 1970-01-18 10:20 devcfgbak -> /dev/block/sda7 lrwxrwxrwx root root 1970-01-18 10:20 devinfo -> /dev/block/sde22 lrwxrwxrwx root root 1970-01-18 10:20 dip -> /dev/block/sde13 lrwxrwxrwx root root 1970-01-18 10:20 dpo -> /dev/block/sde32 lrwxrwxrwx root root 1970-01-18 10:20 dsp -> /dev/block/sde12 lrwxrwxrwx root root 1970-01-18 10:20 frp -> /dev/block/sda8 lrwxrwxrwx root root 1970-01-18 10:20 fsc -> /dev/block/sdf3 lrwxrwxrwx root root 1970-01-18 10:20 fsg -> /dev/block/sde7 lrwxrwxrwx root root 1970-01-18 10:20 hyp -> /dev/block/sde5 lrwxrwxrwx root root 1970-01-18 10:20 hypbak -> /dev/block/sde6 lrwxrwxrwx root root 1970-01-18 10:20 keymaster -> /dev/block/sde24 lrwxrwxrwx root root 1970-01-18 10:20 keymasterbak -> /dev/block/sde25 lrwxrwxrwx root root 1970-01-18 10:20 keystore -> /dev/block/sda5 lrwxrwxrwx root root 1970-01-18 10:20 md5 -> /dev/block/sdf4 lrwxrwxrwx root root 1970-01-18 10:20 mdtp -> /dev/block/sde14 lrwxrwxrwx root root 1970-01-18 10:20 misc -> /dev/block/sda4 lrwxrwxrwx root root 1970-01-18 10:20 modem -> /dev/block/sde11 lrwxrwxrwx root root 1970-01-18 10:20 modemst1 -> /dev/block/sdf1 lrwxrwxrwx root root 1970-01-18 10:20 modemst2 -> /dev/block/sdf2 lrwxrwxrwx root root 1970-01-18 10:20 msadp -> /dev/block/sde31 lrwxrwxrwx root root 1970-01-18 10:20 oem_dycnvbk -> /dev/block/sda9 lrwxrwxrwx root root 1970-01-18 10:20 oem_stanvbk -> /dev/block/sda10 lrwxrwxrwx root root 1970-01-18 10:20 param -> /dev/block/sda11 lrwxrwxrwx root root 1970-01-18 10:20 persist -> /dev/block/sda2 lrwxrwxrwx root root 1970-01-18 10:20 pmic -> /dev/block/sde9 lrwxrwxrwx root root 1970-01-18 10:20 pmicbak -> /dev/block/sde10 lrwxrwxrwx root root 1970-01-18 10:20 recovery -> /dev/block/sde21 lrwxrwxrwx root root 1970-01-18 10:20 reserve -> /dev/block/sdd1 lrwxrwxrwx root root 1970-01-18 10:20 reserve1 -> /dev/block/sda12 lrwxrwxrwx root root 1970-01-18 10:20 reserve2 -> /dev/block/sda13 lrwxrwxrwx root root 1970-01-18 10:20 rpm -> /dev/block/sde1 lrwxrwxrwx root root 1970-01-18 10:20 rpmbak -> /dev/block/sde2 lrwxrwxrwx root root 1970-01-18 10:20 sec -> /dev/block/sde8 lrwxrwxrwx root root 1970-01-18 10:20 splash -> /dev/block/sde33 lrwxrwxrwx root root 1970-01-18 10:20 ssd -> /dev/block/sda1 lrwxrwxrwx root root 1970-01-18 10:20 sti -> /dev/block/sde34 lrwxrwxrwx root root 1970-01-18 10:20 system -> /dev/block/sde20 lrwxrwxrwx root root 1970-01-18 10:20 tz -> /dev/block/sde3 lrwxrwxrwx root root 1970-01-18 10:20 tzbak -> /dev/block/sde4 lrwxrwxrwx root root 1970-01-18 10:20 userdata -> /dev/block/sda15 lrwxrwxrwx root root 1970-01-18 10:20 xbl -> /dev/block/sdb1 lrwxrwxrwx root root 1970-01-18 10:20 xblbak -> /dev/block/sdc1 [email protected]:/ # cat /proc/partitions major minor #blocks name 7 0 98304 loop0 8 0 56582144 sda 8 1 8 sda1 8 2 32768 sda2 8 3 262144 sda3 8 4 1024 sda4 8 5 512 sda5 8 6 128 sda6 8 7 128 sda7 8 8 512 sda8 8 9 10240 sda9 8 10 10240 sda10 8 11 1024 sda11 8 12 8096 sda12 8 13 16192 sda13 8 14 512 sda14 8 15 56238572 sda15 8 16 4096 sdb 8 17 4052 sdb1 8 32 4096 sdc 8 33 4052 sdc1 8 80 1572864 sdf 8 81 2048 sdf1 8 82 2048 sdf2 8 83 4 sdf3 8 84 512 sdf4 8 64 4194304 sde 8 65 512 sde1 8 66 512 sde2 8 67 2048 sde3 8 68 2048 sde4 8 69 512 sde5 8 70 512 sde6 8 71 2048 sde7 8 72 16 sde8 8 73 512 sde9 8 74 512 sde10 8 75 97280 sde11 8 76 16384 sde12 8 77 1024 sde13 8 78 32768 sde14 8 79 8192 sde15 259 0 8192 sde16 259 1 16384 sde17 259 2 65536 sde18 259 3 65536 sde19 259 4 3080192 sde20 259 5 65536 sde21 259 6 4 sde22 259 7 1024 sde23 259 8 512 sde24 259 9 512 sde25 259 10 256 sde26 259 11 256 sde27 259 12 256 sde28 259 13 256 sde29 259 14 256 sde30 259 15 256 sde31 259 16 4 sde32 259 17 33424 sde33 259 18 2048 sde34 8 48 131072 sdd 8 49 32 sdd1 8 50 4 sdd2 8 51 1024 sdd3 I assigned each partition with its space, in kb, to get the full partition table : Code: Size (in Kb) Partitions names and paths --------------------------------------------------------- 98304 loop0 --------------------------------------------------------- 56582144 sda 8 ssd -> /dev/block/sda1[B] 32768 persist -> /dev/block/sda2 262144 cache -> /dev/block/sda3[/B] 1024 misc -> /dev/block/sda4 512 keystore -> /dev/block/sda5 128 devcfg -> /dev/block/sda6 128 devcfgbak -> /dev/block/sda7 512 frp -> /dev/block/sda8 10240 oem_dycnvbk -> /dev/block/sda9 10240 oem_stanvbk -> /dev/block/sda10 1024 param -> /dev/block/sda11 8096 reserve1 -> /dev/block/sda12 16192 reserve2 -> /dev/block/sda13 512 config -> /dev/block/sda14[B] 56238572 userdata -> /dev/block/sda15[/B] --------------------------------------------------------- 4096 sdb 4052 xbl -> /dev/block/sdb1 --------------------------------------------------------- 4096 sdc 4052 xblbak -> /dev/block/sdc1 --------------------------------------------------------- 131072 sdd 32 reserve -> /dev/block/sdd1 4 cdt -> /dev/block/sdd2 1024 ddr -> /dev/block/sdd3 --------------------------------------------------------- 4194304 sde 512 rpm -> /dev/block/sde1 512 rpmbak -> /dev/block/sde2 2048 tz -> /dev/block/sde3 2048 tzbak -> /dev/block/sde4 512 hyp -> /dev/block/sde5 512 hypbak -> /dev/block/sde6 2048 fsg -> /dev/block/sde7 16 sec -> /dev/block/sde8 512 pmic -> /dev/block/sde9 512 pmicbak -> /dev/block/sde10 97280 modem -> /dev/block/sde11 16384 dsp -> /dev/block/sde12 1024 dip -> /dev/block/sde13 32768 mdtp -> /dev/block/sde14 8192 aboot -> /dev/block/sde15 8192 abootbak -> /dev/block/sde16 16384 LOGO -> /dev/block/sde17[B] 65536 boot -> /dev/block/sde18[/B] 65536 boot_aging -> /dev/block/sde19[B] 3080192 system -> /dev/block/sde20 65536 recovery -> /dev/block/sde21[/B] 4 devinfo -> /dev/block/sde22 1024 bluetooth -> /dev/block/sde23 512 keymaster -> /dev/block/sde24 512 keymasterbak -> /dev/block/sde25 256 cmnlib -> /dev/block/sde26 256 cmnlibbak -> /dev/block/sde27 256 cmnlib64 -> /dev/block/sde28 256 cmnlib64bak -> /dev/block/sde29 256 apdp -> /dev/block/sde30 256 msadp -> /dev/block/sde31 4 dpo -> /dev/block/sde32 33424 splash -> /dev/block/sde33 2048 sti -> /dev/block/sde34 --------------------------------------------------------- 1572864 sdf [B] 2048 modemst1 -> /dev/block/sdf1 (EFS1, I suppose) 2048 modemst2 -> /dev/block/sdf2 (EFS2, I suppose) [/B] 4 fsc -> /dev/block/sdf3 512 md5 -> /dev/block/sdf4
How is it, that one flash storage chip is found as different sd* entrys? Like sda to sdf? How is it technically possible for them to split this chip into several "disks"? Could someone explain it to me please?
awesome an information
[DUMP/UNPACK] - OnePlus 6T [OOS 9.0.5/6/7]
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!
[CLOSED] T-Mobile OnePlus 7T Pro 5G McLaren DEV Starts here...
*Request: Can anyone post the super.img of a OnePlus 7T Pro/McLaren (Global Edition)? If you don't know how and still want to help, please let me know. Thank You! Under construction > > > Temp DEV and Research area... Before messing with your phone, please check post #4 on how to backup your partitions. This is the first step towards DEV (You first compare... then make changes/modify and ultimately create a ROM) In the meantime, we will have to work with Magisk Modules. Special thanks to @jhofseth for providing the TMO 5G images & @ntzrmtthihu777 (also @DanDroidOS) for messing up the phone and requesting the images. I basically extracted the 5G images and added the Global Images (also extracted) Okay, here is the deal... The file below is a RAR with 2 folders inside: (ALL files extracted & ready - NO IMG) Folder > mclaren_global_TEKHD (based on OnePlus 7T Pro McLaren Global Firmware with Security Patch 2019-11-01 [hotdog]) with Sub Folders: odm product system vendor Folder > mclaren_TMO_5G_TEKHD (based on TMO OnePlus 7T Pro 5G McLaren Firmware 10.0.13.HD61CB with Security Patch 2019-10-01 [hotdogg] with Sub Folders: odm product system vendor The idea is to encourage development by providing a direct comparison between the 2 Firmwares (Global vs TMO 5G). You can use a software like "Beyond Compare" (or any other) in order to compare files. (Left Side Global vs Right Side TMO 5G) OnePlus7TPro_Global_vs_TMO_5G_Partitions_DEV_KIT_TEKHD.rar
Dual SIM on OnePlus 7T Pro 5G McLaren > Can anyone test this: \vendor\build.prop Search: Code: persist.radio.multisim.config=ssss ...replace with: Code: persist.radio.multisim.config=dsds ...see screenshot below
Activate 5G Radio on OnePlus 7T Pro Global McLaren (When using Global Firmware on TMO 5G Variant) > Can anyone test this: \vendor\build.prop Search: Code: persist.vendor.radio.5g_mode_pref=0 ...replace with: Code: persist.vendor.radio.5g_mode_pref=1 ...see screenshot below
How to backup your own partitions before messing with the phone: Partition Structure on OnePlus 7T Pro 5G McLaren Edition: Code: ls -al /dev/block/platform/soc/1d84000.ufshc/by-name lrwxrwxrwx 1 root root 16 1970-01-29 11:39 5gdump -> /dev/block/sda21 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 ALIGN_TO_128K_1 -> /dev/block/sdd1 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 ALIGN_TO_128K_2 -> /dev/block/sdf1 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 LOGO_a -> /dev/block/sde21 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 LOGO_b -> /dev/block/sde47 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 abl_a -> /dev/block/sde8 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 abl_b -> /dev/block/sde35 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 aging -> /dev/block/sde54 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 aging_mod -> /dev/block/sde55 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 aop_a -> /dev/block/sde1 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 aop_b -> /dev/block/sde28 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 apdp -> /dev/block/sde59 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 bluetooth_a -> /dev/block/sde5 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 bluetooth_b -> /dev/block/sde32 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 boot_a -> /dev/block/sde11 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 boot_b -> /dev/block/sde38 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 carrier -> /dev/block/sda18 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 catecontentfv -> /dev/block/sde72 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 catefv -> /dev/block/sde71 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 cateloader -> /dev/block/sde66 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 cdt -> /dev/block/sdd2 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 cmnlib64_a -> /dev/block/sde13 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 cmnlib64_b -> /dev/block/sde40 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 cmnlib_a -> /dev/block/sde12 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 cmnlib_b -> /dev/block/sde39 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 config -> /dev/block/sda12 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 core_nhlos -> /dev/block/sde20 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 ddr -> /dev/block/sdd3 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 devcfg_a -> /dev/block/sde14 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 devcfg_b -> /dev/block/sde41 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 devinfo -> /dev/block/sde57 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 dip -> /dev/block/sde58 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 dsp_a -> /dev/block/sde9 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 dsp_b -> /dev/block/sde36 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 dtbo_a -> /dev/block/sde17 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 dtbo_b -> /dev/block/sde44 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 frp -> /dev/block/sda6 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 fsc -> /dev/block/sdf5 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 fsg -> /dev/block/sdf4 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 fw_ufs1_a -> /dev/block/sde22 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 fw_ufs1_b -> /dev/block/sde48 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 fw_ufs2_a -> /dev/block/sde23 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 fw_ufs2_b -> /dev/block/sde49 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 fw_ufs3_a -> /dev/block/sde24 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 fw_ufs3_b -> /dev/block/sde50 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 fw_ufs4_a -> /dev/block/sde25 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 fw_ufs4_b -> /dev/block/sde51 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 fw_ufs5_a -> /dev/block/sde26 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 fw_ufs5_b -> /dev/block/sde52 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 hyp_a -> /dev/block/sde3 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 hyp_b -> /dev/block/sde30 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 imagefv_a -> /dev/block/sde19 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 imagefv_b -> /dev/block/sde46 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 keymaster_a -> /dev/block/sde10 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 keymaster_b -> /dev/block/sde37 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 keystore -> /dev/block/sda5 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 limits -> /dev/block/sde63 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 logdump -> /dev/block/sde67 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 logfs -> /dev/block/sde65 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 mdm1m9kefs1 -> /dev/block/sdf7 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 mdm1m9kefs2 -> /dev/block/sdf8 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 mdm1m9kefs3 -> /dev/block/sdf6 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 mdm1m9kefsc -> /dev/block/sdf9 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 mdm1oemnvbktmp -> /dev/block/sde77 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 mdm_oem_dycnvbk -> /dev/block/sda10 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 mdm_oem_stanvbk -> /dev/block/sda11 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 mdmddr -> /dev/block/sdd4 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 mdtp_a -> /dev/block/sde7 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 mdtp_b -> /dev/block/sde34 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 mdtpsecapp_a -> /dev/block/sde6 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 mdtpsecapp_b -> /dev/block/sde33 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 metadata -> /dev/block/sda19 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 misc -> /dev/block/sda3 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 modem_a -> /dev/block/sde4 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 modem_b -> /dev/block/sde31 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 modemst1 -> /dev/block/sdf2 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 modemst2 -> /dev/block/sdf3 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 msadp -> /dev/block/sde60 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 multiimgoem_a -> /dev/block/sde27 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 multiimgoem_b -> /dev/block/sde53 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 oem_dycnvbk -> /dev/block/sda8 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 oem_stanvbk -> /dev/block/sda9 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 op1 -> /dev/block/sde56 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 op2 -> /dev/block/sda7 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 param -> /dev/block/sda4 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 persist -> /dev/block/sda2 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 qupfw_a -> /dev/block/sde15 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 qupfw_b -> /dev/block/sde42 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 rawdump -> /dev/block/sda20 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 recovery_a -> /dev/block/sda14 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 recovery_b -> /dev/block/sda15 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 reserve1 -> /dev/block/sde73 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 reserve2 -> /dev/block/sde74 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 reserve3 -> /dev/block/sde75 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 reserve4 -> /dev/block/sde76 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 secdata -> /dev/block/sde70 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 splash -> /dev/block/sde62 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 spunvm -> /dev/block/sde61 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 ssd -> /dev/block/sda1 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 storsec_a -> /dev/block/sde68 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 storsec_b -> /dev/block/sde78 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 super -> /dev/block/sda13 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 toolsfv -> /dev/block/sde64 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 tz_a -> /dev/block/sde2 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 tz_b -> /dev/block/sde29 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 uefisecapp_a -> /dev/block/sde18 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 uefisecapp_b -> /dev/block/sde45 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 uefivarstore -> /dev/block/sde69 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 userdata -> /dev/block/sda22 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 vbmeta_a -> /dev/block/sde16 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 vbmeta_b -> /dev/block/sde43 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 vbmeta_system_a -> /dev/block/sda16 lrwxrwxrwx 1 root root 16 1970-01-29 11:39 vbmeta_system_b -> /dev/block/sda17 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 xbl_a -> /dev/block/sdb1 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 xbl_b -> /dev/block/sdc1 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 xbl_config_a -> /dev/block/sdb2 lrwxrwxrwx 1 root root 15 1970-01-29 11:39 xbl_config_b -> /dev/block/sdc2 Boot into Fastboot -> Code: adb reboot fastboot Run TWRP -> (You need to have twrp.img on your ADB folder) Code: fastboot boot ./twrp.img For example, if you want to backup LOGO_a -> Code: adb pull /dev/block/sde21 LOGO_a.img After you are done, simply exit/reboot from TWRP (with no modifications, read only) or Code: adb reboot Done Automatic Extraction Tool for TMO 5G McLaren available here.
Announcement: I have created a series of Highly Experimental ROMs. Files are based on Global Firmware. I also have restore/revert files for each Experimental ROM. We can FLASH ZIP -> TEST -> RESTORE. It's LITERALLY a trial & error WIP and THERE IS ALWAYS THE POSSIBILITY OF THINGS GOING WRONG! -> ROM ZIPS are designed from BASIC TO COMPLEX - English please? -> I will try to flash the less amount of partitions required in order to make Global firmware boot & work on our device. I will start with a few partitions (partitions that I know are 100% required) and then move to a more complex set of partitions if required. -> We will try to boot with our Kernel as well as the Global Kernel. Again, Trial & Error. Requirements: - ADB/Fastboot/Linux Knowledge (at least the basic commands and some common sense) - Ability to follow instructions - Patience (each file is 2GB+ in size... and the process is a bit time consuming) - Balls of steel - Dual SIM Tray (optional) If you want to test, you are welcome to join my new Telegram Channel -> HERE - My 2 favorite bots are already there waiting for you! -> I will prepare and upload everything tomorrow, (and during the the next few days) while people start joining the channel. Thank You, TEKHD
@TEKHD Is there any way you could post these partitions? I think I'm gonna need all of them because I flashed the Int version. The system, product, and vendor that we have now just gets me a Qualcomm error aop.img bluetooth.img boot.img dsp.img dtbo.img LOGO.img modem.img oem_stanvbk.img qupfw.img storsec.img multiimgoem.img uefisecapp.img recovery.img vbmeta.img vbmeta_system.img opproduct.img
DanDroidOS said: @TEKHD Is there any way you could post these partitions? aop.img bluetooth.img boot.img dsp.img dtbo.img LOGO.img modem.img oem_stanvbk.img qupfw.img storsec.img multiimgoem.img uefisecapp.img recovery.img vbmeta.img vbmeta_system.img opproduct.img Click to expand... Click to collapse How to restore your OnePlus 7T Pro 5G McLaren: (with easy flash-all.bat script for Windows and flash-all.sh script for Linux) https://forum.xda-developers.com/showpost.php?p=81374031&postcount=67 Thanks @jhofseth ________________________________________________________ @Some_Random_Username Please, can you pull all partitions from latest OnePlus 7T Pro Global McLaren? Like @jhofseth did above? See Link Those global images can help a lot here. We might end up using Magisk Modules for modifications but I would like to see a few things.
Ideally it would be good to get dumps from multiple people with multiple versions and compare hashes of the files to be certain that these dumps are identical across all the phones.
Tell me what you need I'll do my best. I'm still awaiting my unlock bin from OnePlus but I'm definitely interested in converting to global.
TEKHD said: @Some_Random_Username Please, can you pull all partitions from latest OnePlus 7T Pro Global McLaren? Like @jhofseth did above? See Link Those global images can help a lot here. We might end up using Magisk Modules for modifications but I would like to see a few things. Click to expand... Click to collapse Not sure if this is relevant but I managed to extract OnePlus7TOxygen_14.O.08_OTA_008_all_1911061912_3b6d7f83eb174cbc.zip from oneplus's firmware download into individual images; could be helpful? Nvm. Just realized that was the 7t, not 7t pro. Afaict there is no stock image for that up anywhere yet?
ntzrmtthihu777 said: Not sure if this is relevant but I managed to extract OnePlus7TOxygen_14.O.08_OTA_008_all_1911061912_3b6d7f83eb174cbc.zip from oneplus's firmware download into individual images; could be helpful? Nvm. Just realized that was the 7t, not 7t pro. Afaict there is no stock image for that up anywhere yet? Click to expand... Click to collapse I am using ro.system.build.fingerprint=OnePlus/OnePlus7TPro/OnePlus7TPro:10/QKQ1.190716.003/1912060020:user/release-keys on my OP kit. I would like a clean pull from the device itself if possible as a failsafe. (device running whatever latest global firmware; basically something that compares to our current version) Remember, we can't risk ourselves too much. Restoring partitions via fastboot is still risky business. by the way... @ntzrmtthihu777 > Is your fingerprint working fine? @DanDroidOS seems to be having fingerprint issues after restoring.
TEKHD said: I am using ro.system.build.fingerprint=OnePlus/OnePlus7TPro/OnePlus7TPro:10/QKQ1.190716.003/1912060020:user/release-keys on my OP kit. I would like a clean pull from the device itself if possible as a failsafe. (device running whatever latest global firmware; basically something that compares to our current version) Remember, we can't risk ourselves too much. Restoring partitions via fastboot is still risky business. by the way... @ntzrmtthihu777 > Is your fingerprint working fine? @DanDroidOS seems to be having fingerprint issues after restoring. Click to expand... Click to collapse I have a logcat if you can make sense of it
TEKHD said: I am using ro.system.build.fingerprint=OnePlus/OnePlus7TPro/OnePlus7TPro:10/QKQ1.190716.003/1912060020:user/release-keys on my OP kit. I would like a clean pull from the device itself if possible as a failsafe. (device running whatever latest global firmware; basically something that compares to our current version) Remember, we can't risk ourselves too much. Restoring partitions via fastboot is still risky business. by the way... @ntzrmtthihu777 > Is your fingerprint working fine? @DanDroidOS seems to be having fingerprint issues after restoring. DanDroidOS said: I have a logcat if you can make sense of it Click to expand... Click to collapse Click to expand... Click to collapse Hadn't tried it (not putting too much work into customizing the phone as I don't intend to stay on stock any longer than needed) but just set up a thumb print and it seems to be fine. What exactly are you having issues with, setting it up or using it? Not to be a **** but the sensor seems quite anal about dirty print area and dirty fingers, perhaps a good scrub down of both could help? Also are you using any sort of screen protector or just bare screen? And sure, gimme da logcat.
ntzrmtthihu777 said: Hadn't tried it (not putting too much work into customizing the phone as I don't intend to stay on stock any longer than needed) but just set up a thumb print and it seems to be fine. What exactly are you having issues with, setting it up or using it? Not to be a **** but the sensor seems quite anal about dirty print area and dirty fingers, perhaps a good scrub down of both could help? Also are you using any sort of screen protector or just bare screen? And sure, gimme da logcat. Click to expand... Click to collapse It's not the sensor, it won't even let me register a fingerprint.
DanDroidOS said: I have a logcat if you can make sense of it Click to expand... Click to collapse Possibly, if you're rooted, have Android terminal and download the attached on phone: su cp -f /sdcard/Download/settings_fingerprint.xml /data/system/users/0/settings_fingerprint.xml chmod 600 /data/system/users/0/settings_fingerprint.xml reboot (or modified via adb)
DanDroidOS said: It's not the sensor, it won't even let me register a fingerprint. Click to expand... Click to collapse Huh, not getting that here. And where is the logcat?
Here is the logcat:
DanDroidOS said: Here is the logcat: Click to expand... Click to collapse I know it would probably be long and drawn out, but can you say exactly what you've done to the phone up to this point? flashing, bricking, unbricking. what and how you've done it.
@DanDroidOS maybe you could do a Titanium backup, copy to external storage before factory resetting? IMHO, at this point, just going nuclear with factory reset would be what I'd do.
ntzrmtthihu777 said: I know it would probably be long and drawn out, but can you say exactly what you've done to the phone up to this point? flashing, bricking, unbricking. what and how you've done it. Click to expand... Click to collapse unllocked sim & bootloader ==> flashed Omni on slot b: ended up with no calls or text ==> flashed 10.0.4 Europe fastboot rom on slot b: wouldn't boot ==> flashed Omni on slot b: to wait for an update to fix calls ==> Set active back to ' slot a' to see if I could recover ==> flashed dump & super.img: now I'm on 10.0.16 with no working fingerprint
[ROM][UNOFFICIAL] LineageOS 17.1 for Xperia 1 II
{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 10.x (Q),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for LineageOS is available in the LineageOS GitHub repo.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website : http://lineageos.org
About LineageOS Legal : http://lineageos.org/legal/
Important Information
1. This ROM has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.
2. This ROM will never work with any versions of Google Camera (GCam)!
3. You need to flash Stock Android 10 before flashing this ROM.
4. For VoLTE, you need to boot into stock firmware and enable it before flashing this ROM!
5.If you cam from SODP ROMs, you need to go back to official Android 10 firmware, and boot into launcher.
Downloads Links
LineageOS 17.1:
Unofficial-build: Link
Google Applications (optional):
OpenGapps: http://opengapps.org/ (ARM64->Android 10.0->Pico, Nano or Micro)
Information: Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
How to flash
Make sure you upgraded to Official Android 10.0 from Sony
Unlock bootloader is necessary.
Download latest platform-tools from google
1. Install fastbootd drivers, guidance
2. Put your device into fastboot by volume up key.
3. Enter fastbootd:
Code:
fastboot reboot fastboot
4. Flash LineageOS:
Code:
fastboot set_active a
fastboot flash:raw boot boot.img
fastboot flash dtbo dtbo.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot erase metadata
fastboot flash system system.img
fastboot flash product product.img
5. If you are first time to flash LineageOS, Wipe the old userdata:
Code:
fastboot erase userdata
Gapps:
Download Lineage Recovery
You could also choose twrp or else.
Flash and boot into Recovery then choose Apply update - Apply from ADB, then sideload the gapps package on your PC with adb tool:
Code:
adb sideload <PATH OF GAPPS>
Root access:
Flash Magisk in recovery.
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Share a log of the error with CatLog for example
Donation:
If you would like to donate me a cup of tea, you can:
Paypal
Also thanks to:
cramfs28
Shion Kagurazaka 神樂坂紫苑 云贵高原小白鼠扛把子
The LineageOS Team
The CyanogenMod Team
XDA:DevDB Information
Lineage-17.1 for Xperia 1 II, ROM for the Sony Xperia 1 II
Contributors
Sjll
Source Code:
GitHub - sjllls/android_device_sony_pdx203
Contribute to sjllls/android_device_sony_pdx203 development by creating an account on GitHub.
github.com
GitHub - sjllls/android_vendor_sony_pdx203
Contribute to sjllls/android_vendor_sony_pdx203 development by creating an account on GitHub.
github.com
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Created 2020-12-06
Last Updated 2020-12-06
FEATURES AND ISSUES Code: - Boot: Ok - Bluetooth: Ok - WiFi: Ok - WiFi Hotspot: Ok - Wireless display: Not tested - RIL - Phone - Data: Ok - VoLTE: Ok - GPS: Ok - Camera: Ok - Camcorder: Ok - Lights: Ok - MicroSD: Ok - Accelerometer: Ok - Compass: Ok - Gyroscope: Ok - QTI sensors: Ok - Touchscreen: Ok - FM Radio: NA - Fingerprint: Ok - Vibrator: Ok - Microphone: Ok - Audio & music: Ok - Bluetooth audio: Ok - NFC: Ok - Kernel: Ok - Graphics: Ok - 3D Rendering: Ok - Clock: Ok - DRM: Widewine L3 - Offline Charging: Ok - USB: Ok - USB Tethering: Ok - USB OTG: Ok - Encryption: Ok - SEPolicies: Enforce
Reserved
Thank you! I love LineageOS
This is awesome, thanks! Has anyone tested this ROM yet?
Hi, was it difficult to build an aosp for this device? I would lite to try to build for 5 ii but have no experience at all so I'm wondering if it won't be to difficult.
danfauca said: Hi, was it difficult to build an aosp for this device? I would lite to try to build for 5 ii but have no experience at all so I'm wondering if it won't be to difficult. Click to expand... Click to collapse If you have a PC with 16GB+ RAM, 200GB+ disk space, and know the basic operation of ubuntu. You could build LineageOS following some guidances. And if you could test on your Xperia 5 II, I could provide you devcie tree for Xperia 5 II.
I've just checked on sony website and sadly xperia 5 ii isn't on the list of unlockable devices. I'll consider buying xpreria 5 and building LineageOS for it.
danfauca said: I've just checked on sony website and sadly xperia 5 ii isn't on the list of unlockable devices. I'll consider buying xpreria 5 and building LineageOS for it. Click to expand... Click to collapse It is not on the list, but you can unlock bootloader. You need to select xperia 1 ii, and then pass IMEI of xperia 5 ii. Don't ask me why it is like that , but it supposedly works: https://forum.xda-developers.com/t/how-do-you-unlock-the-sony-xperia-5-ii-bootloader.4183593/
Good to know! Thanks
So i go to unlock bootloader with code provided by sony and in cdm is says no phone is recognized. Can anyone help me out?? Thanks
Hey! Good job! I am thinking about flashing to LineageOS, but (as a newbie) I have a important question: - as I see, everything for HW works, but how about camera and photo quality? Is possible to somehow instal those Sony camera pro apps? Thank you for your reply in advance!
Wow! Niice I will give it a try. I'm looking more into a de-googled phone. Is the pro camera app still working? Do you have some instructions on how to build everything? I am interested in contributing. UPDATE: Has anyone tried flashing after upgrading to Android 11?
Sjll said: If you have a PC with 16GB+ RAM, 200GB+ disk space, and know the basic operation of ubuntu. You could build LineageOS following some guidances. And if you could test on your Xperia 5 II, I could provide you devcie tree for Xperia 5 II. Click to expand... Click to collapse I have the 5 II too (58.0.A.22.21). Already unlocked bl and I'm ready for the next step but I'm an ubuntu noob. Maybe I can help on the testing end?
i wanna konw if i flash this rom,how can i reinstall Photography Pro and Cinematography Pro apps
momba5 said: I have the 5 II too (58.0.A.22.21). Already unlocked bl and I'm ready for the next step but I'm an ubuntu noob. Maybe I can help on the testing end? Click to expand... Click to collapse My friends already built it, I will ask him for help. ------------------EDIT----------------------- Released, test and enjoy.
This is super interesting, really looking forward to it, but can't get the partitions to write. Luckily, the failure did not effect the stock android, so its not bricked but no lineageos yet This is the xq-at51 and I did unlock the bootloader. TWRP installed fine. Here's what I did: Code: C:\Tools\android_tools\platform-tools>fastboot set_active a Setting current slot to 'a' OKAY [ 0.009s] Finished. Total time: 0.012s C:\Tools\android_tools\platform-tools>fastboot flash:raw boot boot.img Sending 'boot_a' (98304 KB) OKAY [ 2.527s] Writing 'boot_a' OKAY [ 0.419s] Finished. Total time: 3.015s C:\Tools\android_tools\platform-tools>fastboot flash dtbo dtbo.img Sending 'dtbo' (24576 KB) OKAY [ 0.638s] Writing 'dtbo' OKAY [ 0.053s] Finished. Total time: 0.707s C:\Tools\android_tools\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img Rewriting vbmeta struct at offset: 0 Sending 'vbmeta' (4 KB) OKAY [ 0.005s] Writing 'vbmeta' OKAY [ 0.002s] Finished. Total time: 0.019s C:\Tools\android_tools\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img Sending 'vbmeta_system' (4 KB) OKAY [ 0.004s] Writing 'vbmeta_system' OKAY [ 0.002s] Finished. Total time: 0.019s C:\Tools\android_tools\platform-tools>fastboot erase metadata Erasing 'metadata' FAILED (remote: 'Erasing is not allowed for partition ') fastboot: error: Command failed C:\Tools\android_tools\platform-tools>fastboot flash system system.img Sending sparse 'system' 1/2 (773740 KB) OKAY [ 20.106s] Writing 'system' FAILED (remote: 'No such partition.') fastboot: error: Command failed C:\Tools\android_tools\platform-tools>fastboot erase userdata ******** Did you mean to fastboot format this f2fs partition? Erasing 'userdata' OKAY [ 9.540s] Finished. Total time: 9.545s And here's the partition list I get: Code: C:\Tools\android_tools\platform-tools>adb shell ls -l /dev/block/platform/soc/1d84000.ufshc/by-name total 0 lrwxrwxrwx 1 root root 15 1970-01-01 03:01 LTALabel -> /dev/block/sda2 lrwxrwxrwx 1 root root 15 1970-01-01 03:01 TA -> /dev/block/sda1 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 abl_a -> /dev/block/sda14 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 abl_b -> /dev/block/sda28 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 aop_a -> /dev/block/sda11 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 aop_b -> /dev/block/sda25 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 apdp -> /dev/block/sda43 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 appslog -> /dev/block/sda55 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 bluetooth_a -> /dev/block/sda62 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 bluetooth_b -> /dev/block/sda76 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 boot_a -> /dev/block/sda64 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 boot_b -> /dev/block/sda78 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 cdt -> /dev/block/sda51 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 cmnlib64_a -> /dev/block/sda17 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 cmnlib64_b -> /dev/block/sda31 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 cmnlib_a -> /dev/block/sda16 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 cmnlib_b -> /dev/block/sda30 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 ddr -> /dev/block/sda41 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 devcfg_a -> /dev/block/sda18 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 devcfg_b -> /dev/block/sda32 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 devinfo -> /dev/block/sda40 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 diag -> /dev/block/sda56 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 dsp_a -> /dev/block/sda63 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 dsp_b -> /dev/block/sda77 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 dtbo_a -> /dev/block/sda69 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 dtbo_b -> /dev/block/sda83 lrwxrwxrwx 1 root root 15 1970-01-01 03:01 frp -> /dev/block/sda6 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 hyp_a -> /dev/block/sda13 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 hyp_b -> /dev/block/sda27 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 imagefv_a -> /dev/block/sda20 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 imagefv_b -> /dev/block/sda34 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 keymaster_a -> /dev/block/sda15 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 keymaster_b -> /dev/block/sda29 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 keystore -> /dev/block/sda53 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 limits -> /dev/block/sda46 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 limits-cdsp -> /dev/block/sda47 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 logdump -> /dev/block/sda49 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 logfs -> /dev/block/sda48 lrwxrwxrwx 1 root root 15 1970-01-01 03:01 mdm1m9kefs1 -> /dev/block/sda8 lrwxrwxrwx 1 root root 15 1970-01-01 03:01 mdm1m9kefs2 -> /dev/block/sda9 lrwxrwxrwx 1 root root 15 1970-01-01 03:01 mdm1m9kefs3 -> /dev/block/sda7 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 mdm1m9kefsc -> /dev/block/sda10 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 mdmddr -> /dev/block/sda42 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 metadata -> /dev/block/sda54 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 misc -> /dev/block/sda52 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 modem_a -> /dev/block/sda61 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 modem_b -> /dev/block/sda75 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 msadp -> /dev/block/sda44 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 multiimgoem_a -> /dev/block/sda71 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 multiimgoem_b -> /dev/block/sda85 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 multiimgqti_a -> /dev/block/sda72 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 multiimgqti_b -> /dev/block/sda86 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 oem_a -> /dev/block/sda70 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 oem_b -> /dev/block/sda84 lrwxrwxrwx 1 root root 15 1970-01-01 03:01 persist -> /dev/block/sda3 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 qupfw_a -> /dev/block/sda19 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 qupfw_b -> /dev/block/sda33 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 rddata -> /dev/block/sda91 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 rdimage_a -> /dev/block/sda66 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 rdimage_b -> /dev/block/sda80 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 recovery_a -> /dev/block/sda65 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 recovery_b -> /dev/block/sda79 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 secdata -> /dev/block/sda57 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 spunvm -> /dev/block/sda45 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 ssd -> /dev/block/sda39 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 storsec -> /dev/block/sda50 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 super -> /dev/block/sda89 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 tz_a -> /dev/block/sda12 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 tz_b -> /dev/block/sda26 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 tzxfl_a -> /dev/block/sda23 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 tzxfl_b -> /dev/block/sda37 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 tzxflattest_a -> /dev/block/sda22 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 tzxflattest_b -> /dev/block/sda36 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 uefisecapp_a -> /dev/block/sda24 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 uefisecapp_b -> /dev/block/sda38 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 uefivarstore -> /dev/block/sda58 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 userdata -> /dev/block/sda90 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 vbmeta_a -> /dev/block/sda67 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 vbmeta_b -> /dev/block/sda81 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 vbmeta_system_a -> /dev/block/sda68 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 vbmeta_system_b -> /dev/block/sda82 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 vm-data -> /dev/block/sda60 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 vm-keystore -> /dev/block/sda59 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 vm-linux_a -> /dev/block/sda74 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 vm-linux_b -> /dev/block/sda88 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 vm-system_a -> /dev/block/sda73 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 vm-system_b -> /dev/block/sda87 lrwxrwxrwx 1 root root 15 1970-01-01 03:01 xbl_a -> /dev/block/sdb1 lrwxrwxrwx 1 root root 15 1970-01-01 03:01 xbl_b -> /dev/block/sdc1 lrwxrwxrwx 1 root root 15 1970-01-01 03:01 xbl_config_a -> /dev/block/sdb2 lrwxrwxrwx 1 root root 15 1970-01-01 03:01 xbl_config_b -> /dev/block/sdc2 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 xfl_a -> /dev/block/sda21 lrwxrwxrwx 1 root root 16 1970-01-01 03:01 xfl_b -> /dev/block/sda35 lrwxrwxrwx 1 root root 15 1970-01-01 03:01 xflkeystore -> /dev/block/sda4 lrwxrwxrwx 1 root root 15 1970-01-01 03:01 xflkeystorebak -> /dev/block/sda5
Maybe the answer is from your other thread? 【Use Sony's Recovery and thank you. TWRP and Lineage Recovery not work in fastbootd 】 Click to expand... Click to collapse
Nevermind, the reason for the issue was because I didn't understand that "fastboot reboot fastboot" is needed to get into fastbootd. Fastbootd is a new and confusing concept so I didn't realize I was in fastboot instead of fastbootd when trying to run the commands. Should be able to do this again after getting back to stock recovery.
Working great now, thanks for this rom!
Question Partition usage on an ASUS Zenfone 8
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 ....