SPECIAL THANKS TO
@Lunarixus on XDA
I wouldn't have figured out how to maneuver the pixel 2 XL partition table without him.
!!!WARNING PLEASE READ!!!!
This tutorial only applies to Walleye (regular 2). There's another tutorial for Taimen (2 XL). Please join the telegram group if you can! Google Pixel Development Group.ALSO, this only increases system partition on slot B. If you want to flash GSIs, make sure you are on the correct slot with this command:fastboot --set-active=bREQUIREMENTS:
Walleye with unlocked bootloader.
Updated adb & fastboot binaries.
GNU parted for ARM64. Get it here: https://guidedflame.dev/parted
Custom recovery for Walleye with adb support.
STEPS:
1. Enable USB Debugging
2. Reboot into fastboot modeadb reboot bootloader
3. Boot into the recovery (format data if it is stuck on splash screen)fastboot boot path/to/recovery.img (optional) you can flash TWRP permanently if you wish. fastboot flash boot_a path/to/recovery.img and fastboot flash boot_b path/to/recovery.img DO NOT FLASH TWRP. JUST BOOT TO IT.
4. In TWRP...
If it asks you to decrypt your data, do it.
If it asks you to swipe for RW permissions on system partition, do it.
Unmount all partitions. Click on Mount, then un-tick everything.
5. Back to your PC. Copy parted to /sbin.adb push path/to/parted /sbin
6. Enter shell mode.adb shell
7. Change permissions of parted.chmod 777 /sbin/parted
8. It's time to use parted!We mainly use 3 commands. Here's how they work.
rm x - Removes partition number x. For example: rm 13
Click to expand...
Click to collapse
mkpart name fstype startUNIT finishUNIT - Makes a partition where fstype is the type of filesystem (like ext4), start is the beginning of the partition, and finish is the end of the partition. UNIT is the unit for the start and finish arguments (like KB, MB, B, or s) For example: mkpart system_a ext4 32KB 1000KB
Click to expand...
Click to collapse
name x part_name - Names partition number x and gives it part_name as a label. For example: name 14 userdata
Click to expand...
Click to collapse
In your terminal (still in shell mode), type parted /dev/block/sda
It should greet you with a welcome screen. Type p free, and save what you get in a screenshot or text file (on windows you can copy and paste in notepad, or use Snipping Tool, since it's installed by default). THIS IS VERY IMPORTANT IF YOU GET STUCK!!!!
{
"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"
}
We have to delete all partitions starting from the bottom until system_b. Make sure to keep the screenshot or text file you saved earlier from p free, because we are gonna need it to recreate the deleted partitions later. YOUR PARTITION SCHEME MIGHT BE DIFFERENT THAN THIS. Make sure to STOP after system_b is removed.
rm 45
rm 44
rm 43
Once you are done, it's time to recreate those partitions. We do it in the proper order now, starting from system_b. Refer to the screenshot or text file you saved earlier. We will increase the partition size to 3GB to be able to boot most GSIs, including Android 12. If it says that the partition isn't aligned, type Ignore.
mkpart system_b ext2 4073MB 7173MB
mkpart padding1 7173MB 7179MB
mkpart userdata ext4 7179MB 62400MB (if you have 128GB Walleye, do mkpart userdata ext4 7179MB 126300MB)
Check your partitioning with p free and compare with your screenshot/text file. It should be similar, with some extra free spaces.
Time to name the partitions.
name 43 system_b
name 44 padding1
name 45 userdata
Check your partitioning again with p free. It should show the named partitions. If everything looks good to you, leave parted.
quit
9. Exit shell mode.
exit
10. Reboot into fastboot mode
adb reboot bootloader
11. Format all the partitions we made
fastboot erase system_bfastboot erase padding1fastboot erase userdatafastboot format:ext2 system_bfastboot format:ext4 userdataAnd that's all!
NOTICE: At this point, the partitions should repopulate themselves on the next boot. If they don't, flash latest Android 11 stock ROM (And flash it using flash-all.bat for windows/flash-all.sh for linux).
Flashing the stock ROM won't undo your partitioning. You will keep your 3GB system partition!
Click to expand...
Click to collapse
You can start immediately flashing GSIs/Android 12. If you're stuck on splash screen, that means the partitions didn't repopulate correctly. Follow the advice above!
If you have any questions, or accidentally brick your device, join the telegram group for direct support, or ask here in the XDA thread.
Thanks for your help on the Telegram group man. I just skipped Step 11 and did fastboot -w so I completed the process without any errors.
always type wrong,so crazy its code,
Related
Hello everyone,
Let me explain veeeery briefly my story.
During an update, the phone froze and I had to turn it off. I'll spare you all that happened next, but in practice "cache" and "persist" partition have failed.
Now, the first one is minor and I could rebuild it and format it without much thought, the second one, unfortunately, I could not retrieve it and I was forced to do the same thing. Too bad that the "persist" partition holds all the necessary configurations to operate the various sensors of the smartphone.
Always avoiding to tell you all the attempts I made (and trust me, I made them all), the last remaining solution, and probably the working one, is to get a dump of the "persist" partition to flash via fastboot. That is, I need a backup of this memory space (taken from a Xiaomi Redmi Notes 4G (Qualcomm) - single SIM, working of course).
Here's how to create this file, then you will have to send it to me (There are few simple steps).
-----------------------------------------------------
Connect the phone to PC with USB.
First, verify that the device is responding ADB (Use ADB while the phone is in recovery mode, as a matter of privileges)
Code:
adb devices
{
"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"
}
If you see a character string, then the device is connected.
Now enter into Shell and check the "persist" partition number
[Each line is a command where to give ENTER - After the # I just put a comment. Type just the previous part.]
Code:
adb shell [B][COLOR="DarkRed"]#Enter into shell[/COLOR][/B]
parted /dev/block/mmcblk0 [B][COLOR="darkred"]#Start a tool to manage partitions[/COLOR][/B]
unit MB [B][COLOR="darkred"]#Set size in MB[/COLOR][/B]
print [B][COLOR="darkred"]#Display the partitions list[/COLOR][/B]
You should see a partitions list. In my case (and probably in all the Xiaomi devices), the "persist" partition is the #26.
At this point it's possible to dump (Backup) that memory space.
If you are still in the "parted" tool, then you need to quit it first, typing "quit", to get back in the shell (but without going further out from the shell)
Code:
quit [B][COLOR="darkred"]#Quit the "parted" tool[/COLOR][/B]
dd if=/dev/block/mmcblk0[COLOR="SeaGreen"][B]p26[/B][/COLOR] of=/sdcard/persist.img [B][COLOR="DarkRed"]#dump from partition #26, one highlighted in green (persist), making a file into internal memory[/COLOR][/B]
Done!
Now you have just to take that file and send it to me. If you want to continue using terminal (since you have already), you can copy the files to your PC as follows:
Code:
exit [B][COLOR="DarkRed"]#if you are still into shell, then you need to exit[/COLOR][/B]
adb pull /sdcard/persist.img C:\
Now you copied the file (that was created into internal memory) to your PC, in the C: \ drive
Please attach this file on reply.
Thank you!
Updated OP
Inviato dal mio Nexus 4 utilizzando Tapatalk
Up
Inviato dal mio Nexus 4 utilizzando Tapatalk
same problem
Attached a zipped persist.img file taken from mmcblk0p26 of dior device. Hope this helps.
MiniBlu
zenida said:
Hello everyone,
Let me explain veeeery briefly my story.
During an update, the phone froze and I had to turn it off. I'll spare you all that happened next, but in practice "cache" and "persist" partition have failed.
Now, the first one is minor and I could rebuild it and format it without much thought, the second one, unfortunately, I could not retrieve it and I was forced to do the same thing. Too bad that the "persist" partition holds all the necessary configurations to operate the various sensors of the smartphone.
Always avoiding to tell you all the attempts I made (and trust me, I made them all), the last remaining solution, and probably the working one, is to get a dump of the "persist" partition to flash via fastboot. That is, I need a backup of this memory space (taken from a Xiaomi Redmi Notes 4G (Qualcomm) - single SIM, working of course).
Here's how to create this file, then you will have to send it to me (There are few simple steps).
-----------------------------------------------------
Connect the phone to PC with USB.
First, verify that the device is responding ADB (Use ADB while the phone is in recovery mode, as a matter of privileges)
Code:
adb devices
If you see a character string, then the device is connected.
Now enter into Shell and check the "persist" partition number
[Each line is a command where to give ENTER - After the # I just put a comment. Type just the previous part.]
Code:
adb shell [B][COLOR="DarkRed"]#Enter into shell[/COLOR][/B]
parted /dev/block/mmcblk0 [B][COLOR="darkred"]#Start a tool to manage partitions[/COLOR][/B]
unit MB [B][COLOR="darkred"]#Set size in MB[/COLOR][/B]
print [B][COLOR="darkred"]#Display the partitions list[/COLOR][/B]
You should see a partitions list. In my case (and probably in all the Xiaomi devices), the "persist" partition is the #26.
At this point it's possible to dump (Backup) that memory space.
If you are still in the "parted" tool, then you need to quit it first, typing "quit", to get back in the shell (but without going further out from the shell)
Code:
quit [B][COLOR="darkred"]#Quit the "parted" tool[/COLOR][/B]
dd if=/dev/block/mmcblk0[COLOR="SeaGreen"][B]p26[/B][/COLOR] of=/sdcard/persist.img [B][COLOR="DarkRed"]#dump from partition #26, one highlighted in green (persist), making a file into internal memory[/COLOR][/B]
Done!
Now you have just to take that file and send it to me. If you want to continue using terminal (since you have already), you can copy the files to your PC as follows:
Code:
exit [B][COLOR="DarkRed"]#if you are still into shell, then you need to exit[/COLOR][/B]
adb pull /sdcard/persist.img C:\
Now you copied the file (that was created into internal memory) to your PC, in the C: \ drive
Please attach this file on reply.
Thank you!
Click to expand...
Click to collapse
mny315 RUS said:
same problem
Click to expand...
Click to collapse
Thanks bro ))
Yeah, sorry I abandoned this thread because I found help from MIUI Italia forum. I should update procedure here but I can't now... I don't know if I can post a link from another forum... Maybe later I'll translate and paste here
Thread on MIUI
Hi I finally decided to send my z3c D5803 in for repair.
I want to remove any sensitive data from the device.
It runs on rooted Android 5.1.1 and has TWRP 2.8.7.0 installed. Over the time I installed a lot of xposed modules and tweaked a lot of settings. So I really want to keep my exact system image.
I have several Questions for every step:
1. Which partitions should I backup
{
"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"
}
According to What should I back up in TWRP?
`The default backup options in TWRP are system, data, and boot`
1.1 Is `Kernel Image` the same as boot ?
1.2. I just go with the defualt settings ?
2. My first simple idea was to remove the external SDcard after the backup from step 1 and perform a "factory reset" using TWRP:
2.1 root and TWRP is preserved ?
3. When the phone is back from repair I just boot in recovery and recover only the /data partition from the inserted SDcard ?
3.1
Is wiping /data enough to remove all sensitive data ( password manager app) [ SdCard removed of course ] ?
What about XPOSED Modules that maybe contain sensitive data ?
4. I guess the TWRP factory reset does not secure erase data ?
4.1 Does anyone know the method that TWRP uses to remove the data from the /data partition?
-> I read about encrypt the phone but a lot of discussions say that you have to unroot before and I guess this would destroy my whole plan of just erasing the /data partition ?
4.1 Does anybody know and tested method to add a additional layer of security.
I found this:
Normal erasing via TWRP should be enough. But if you want to erase all of your data on the phone then you need to execute the TRIM command on your flash storage.
You can do this on TWRP by following the steps:
– Mount the /system partition
– Go to Advanced and then Terminal Command
– Execute the command to TRIM /system partition:
fstrim -v /system
– Execute the command to TRIM /data partition:
fstrim -v /data
– Execute the command to TRIM /cache partition:
fstrim -v /cache
When you delete data from your storage, the actual data is not cleaned but the link to the internal blocks (where the actual data is stored) is made as invalid or the block is made as dirty.
TRIM command is designed specifically for flash storage. When you execute TRIM command on flash storage, it cleans all the data of all the blocks.
NOTE:
But you need to be careful, as the TRIM actually erases block by block and flash storage has limited erase and write cycles.
Click to expand...
Click to collapse
Well personally it doesn't really matter but backup Data,System and Boot(kernel image) and if you really want to remove everything transfer pictures to your computer and wipe internal storage
And when you backup everything will be kept and when you wipe everything will be wiped including password managers and etc,and when you restore it back everything will be as you left it with everything on your device as before.
for encryption disable: (replace /vendor/etc/fstab.qcom file and run "fastboot -w")
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
# A/B fstab.qcom variant
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/bootdevice/by-name/system / ext4 ro,barrier=1,discard wait,resize,slotselect,verify
/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,barrier=0,noauto_da_alloc,discard,noatime,lazytime wait,resize,check,crashcheck,quota
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
/dev/block/bootdevice/by-name/modem /vendor/firmware_mnt vfat ro,shortname=lower,uid=0,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait,slotselect
/dev/block/bootdevice/by-name/bluetooth /vendor/bt_firmware vfat ro,shortname=lower,uid=1002,gid=3002,dmask=227,fmask=337,context=u:object_r:bt_firmware_file:s0 wait,slotselect
/devices/soc/a800000.ssusb/a800000.dwc3/xhci-hcd.0.auto* /storage/usbotg vfat nosuid,nodev wait,voldmanaged=usbotg:auto
/dev/block/bootdevice/by-name/dsp /vendor/dsp ext4 ro,nosuid,nodev,barrier=1 wait,slotselect
/dev/block/bootdevice/by-name/persist /mnt/vendor/persist ext4 noatime,nosuid,nodev,barrier=1 wait
for GSİ roms fixes: (add lines in /vendor/build.prop)
Code:
persist.dbg.volteavailovr=1
persist.imx376_sunny.low.lux=310
persist.imx376_sunny.light.lux=280
persist.imx376_ofilm.low.lux=310
persist.imx376_ofilm.light.lux=280
qemu.hw.mainkeys=0
persist.camera.HAL3.enabled=1
persist.camera.eis.enabled=1
persist.camera.preview.ubwc=0
persist.camera.stats.test=0
persist.camera.depth.focus.cb=0
persist.camera.isp.clock.optmz=0
persist.camera.linkpreview=0
persist.camera.isp.turbo=1
persist.camera.set.afd=4
persist.bokeh.switch.lux=290
persist.camera.auxswitch.threshold=330
persist.camera.mainswitch.threshold=419
ims.apk for Mi A2: (for VoLTE)
https://www84.zippyshare.com/v/WznfyJtc/file.html
Full stable custom Pie Rom link:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development/aosp-9-0-phh-treble-t3831915
Miui camera magisk module (for fix fingerprint on custom roms):
https://forum.xda-developers.com/mi-a2/themes/miui-camara-features-magisk-t3841269
for Root(for install magisk):
https://forum.xda-developers.com/mi-a2/development/boot-mi-a2-patched-magisk-boot-image-v9-t3863494
TWRP:
https://forum.xda-developers.com/mi-a2/development/recovery-unofficial-twrp-recovery-mi-a2-t3825146
GSİ treble rom list(installable for mi a2):
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list
Treble fix for wayne(6x):
https://github.com/MI6XDev/treble_fix_for_wayne/wiki/fix_en_us
Telegram Group:
http://t.me/MiA2OffTopic
Payload dumper(file in my telegram channel:laugh:
https://t.me/PlayBoyStore/954
for Headsup enable/disable:
https://www73.zippyshare.com/v/PCy2u5VV/file.html
{
"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"
}
Thanks for sharing.
@parduscix
I think you should warn users that fastboot -w wipes all user data!
kishd said:
@parduscix
I think you should warn users that fastboot -w wipes all user data!
Click to expand...
Click to collapse
I know that remove everything.
parduscix said:
I know that remove everything.
Click to expand...
Click to collapse
Your method of removing encryption doesn't work flawlessly. It might work tho, but after doing this I can no longer install apps from Google Play, the download just never starts
nicholasneutron2277 said:
Your method of removing encryption doesn't work flawlessly. It might work tho, but after doing this I can no longer install apps from Google Play, the download just never starts
Click to expand...
Click to collapse
So we should backup all data before wiping
parduscix said:
So we should backup all data before wiping
Click to expand...
Click to collapse
I mean it doesn't fetch that data from the cloud also
How to install gsi rom?
parduscix said:
I know that remove everything.
Click to expand...
Click to collapse
I think you missed the point. If you post a guide you must inform people in the op if their data will be wiped.
IjazCI said:
How to root gsi pie 9.0 aosp ?
Is it by flashing magisk via twrp ?
I don't need root, but i need to add those lines ,as last time i flashed aosp 9.0 , i dont had navigation bar and volte.
Click to expand...
Click to collapse
yes. You must flash magisk zip with twrp.
You must add build prop lines in /vendor/build.prop and reboot. next install ims apk and reboot 2 times. VoLTE and Navbar will fixed.
iEstuardo said:
How to install gsi rom?
Click to expand...
Click to collapse
You must download any gsi rom. (mi a2 = gsi ab arm64/mi 6x = gsi a only arm64)
Next you uncompress system.img.xz(Windows users can use 7zip/Linux users can use "xz -d system.img.xz")
then flash with fastboot
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img #mi 6x doesn't have this partition
finally you must wipe data and reboot.
So today I wanted to try something as I had issues with an app.
I made a full nandroid backup with twrp.
After setting up my phone and try the new app I wanted to restore to the old situation.
When restoring I got the error
createTarFork() process ended with ERROR: 255
After a reboot, no decryption password is asked, all files and folders have strange names.
As a result the phone doesn't boot any more except into recovery.
I'm on oxigen os 9.0.8, latest twrp.
Any clues on how I can fix this.
Phone is a brick now...
yelti said:
So today I wanted to try something as I had issues with an app.
I made a full nandroid backup with twrp.
After setting up my phone and try the new app I wanted to restore to the old situation.
When restoring I got the error
createTarFork() process ended with ERROR: 255
After a reboot, no decryption password is asked, all files and folders have strange names.
As a result the phone doesn't boot any more except into recovery.
I'm on oxigen os 9.0.8, latest twrp.
Any clues on how I can fix this.
Phone is a brick now...
Click to expand...
Click to collapse
Some treads below yours is the possible solution https://forum.xda-developers.com/oneplus-5/help/createtarfork-process-error255-t3727673
And: you should always remove pin/security before restore or before backup
strongst said:
Some treads below yours is the possible solution https://forum.xda-developers.com/oneplus-5/help/createtarfork-process-error255-t3727673
And: you should always remove pin/security before restore or before backup
Click to expand...
Click to collapse
Thx,
I checked but not really my situation.
I don't have the 999 users issue.
I have made a screenshot of my /sdcard folder:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
* it seem that my picture is not comming through, so a link to it imgur
Hopes this sheds some light.
What I got from those threads:
My backup was pretty large, 22GB.
I think I will try to flash the stock rom and see where that gets me.
yelti said:
Thx,
I checked but not really my situation.
I don't have the 999 users issue.
I have made a screenshot of my /sdcard folder:
* it seem that my picture is not comming through, so a link to it imgur
Hopes this sheds some light.
What I got from those threads:
My backup was pretty large, 22GB.
I think I will try to flash the stock rom and see where that gets me.
Click to expand...
Click to collapse
So I tried a sideload of the factory images.
Flashing is successfull, next I reboot the phone.
It shows me the oneplus logo and reboots to recovery.
I tried installing the stock recovery, but then when I try to sideload the firmware, the usb device is not recognized.
I have an idea, but I don't know if is doable.
I would want to backup the data partition, (adb pull /dev/block/sda13 data_encrypted.img).
Next I would wipe the phone completely, setup encryption with the same pincode.
Next I would like to restore the old data, but I don't know how.
I hope this way I will ask to decrypt my data partition again.
Anyone an idea?
So an update:
I dumped the data and recovery partition.
Code:
adb pull /dev/block/sda13 data_encrypted.img
adb pull /dev/block/sde22 recovery.img
5494 KB/s (67108864 bytes in 11.927s)
Next I wiped the data partition, phone started normally.
I encrypted the phone again with the same pin code.
Next I tried a nandroid backup and restore while the phone was encrypted, no issues there.
Next I flashed an older recovery to the phone.
Now the test to restore the recovery from the image.
On the phone with an adb sheel:
Code:
dd of=/dev/block/sde22 | nc -l -p 9999
On the pc:
Code:
adb forward tcp:9999 tcp:9999
nc 127.0.0.1 9999 < recovery.img
On the phone I get a lot of data on the screen and the message
Code:
8+0 records in
8+0 records out
4096 bytes transferred in 64.155 secs (63 bytes/sec)
First thing I noticed: number of bytes transferred where not the same as the original recovery.
Next I dumped the recovery partition again to disk and compared the md5 hashes, not the same.
Rebooted the phone and it did not go into recovery.
So this process did not work.
Any ideas?
So, It didn't work with netcat, so I did the following:
connect an usb-c to usb-a coverter to the phone, and connected the external drive with the "bad" image on it.
Then dd-ed the image to the data partition.
When I rebooted the phone, it didn't ask for a pin code and the file and folders where gibbirish again.
So I was back to the starting position.
I'm affraid my data is lost forever :s.
Hello @yelti , I know it's been a long time but I'm kinda into the same issue. Have you been able to fix yours? Do you remember how? Thanks.
This tool I called it opsplash.This tool does not support mtk device, qualcomm only!cause it can unpack/repack oppo splash format image.
{
"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"
}
pic from my cygwin terminalIf you like my tool, you can buy me a cofface.Donate : https://paypal.me/affggh
First get your splash image
How can I get my splash image.
adb shell
# give root access
su
dd if=/dev/block/by-name/splash of=/sdcard/splash.img
# or
dd if=/dev/block/by-name/splash_a of=/sdcard/splash_a.img
exit
adb pull /sdcard/splash.img splash.img
# or
adb pull /sdcard/splash_a.img splash_a.img
Click to expand...
Click to collapse
Now we have splash image, unpack pics from splash image.
# powershell
.\opsplash.exe unpack -i splash.img -o pic
Click to expand...
Click to collapse
# linux bash
./opsplash unpack -i splash.img -o pic
Click to expand...
Click to collapse
They are basicly same...
Notice : The pic which you replace must have same format and same width and height pixel
After replace your bitmap image, repack and flash it back
./opsplash repack -i splash.img -o new-splash.img
Click to expand...
Click to collapse
Here we success generated a new-splash.img, flash it back to your phone and test wether it work.
Source code : https://github.com/affggh/opsplash
reserved
affggh said:
This tool I called it opsplash.This tool does not support mtk device, qualcomm only!cause it can unpack/repack oppo splash format image.
View attachment 5721337
pic from my cygwin terminalIf you like my tool, you can buy me a cofface.Donate : https://paypal.me/affggh
First get your splash image
How can I get my splash image.
Now we have splash image, unpack pics from splash image.
# powershell
# linux bash
They are basicly same...
Notice : The pic which you replace must have same format and same width and height pixelView attachment 5721339
View attachment 5721341
After replace your bitmap image, repack and flash it back
View attachment 5721343
Here we success generated a new-splash.img, flash it back to your phone and test wether it work.
View attachment 5721345
Source code : https://github.com/affggh/opsplash
Click to expand...
Click to collapse
Will work on realme 5 sir?
Adamant12 said:
Will work on realme 5 sir?
Click to expand...
Click to collapse
You can just try it, I've test it on oneplus 8t ,realme gt2, realme gt neo2,oppo r11s
Some question about this tool to modify bootlogo on my OnePlus 8T with Android 13:
when launching command dd if=/dev/block/by-name/splash of=/sdcard/splash.img or dd if=/dev/block/by-name/splash_a of=/sdcard/splash_a.img I have as a result No such file or directory on my OnePlus 8T
which tool to download and use on Windows 64 to unpack and repack?
can you share adb commands to push the modded image file?
Thank you
EDIT: dd if=/dev/block/by-name/logo_a of=/sdcard/logo_a.img did the job
I need the command to flash modded logo_a, should be dd if=/sdcard/logo_a.img of=/dev/block/by-name/logo_a
Tool is unable to read splash for oneplus 8 (instantnoodle). which is logo partition
(i opened an issue on github)
I managed to change boot.bmp on a oneplus9 when it repacks the splash_a image the size difference was worrying.
But I chanced it and flashed it back
Code:
DD if=/sdcard/new-image.img of=/dev/block/by-name/splash_a
And rebooted, stupidly I was booting from slot b so I just repeated the step above but used b
Code:
DD if=/sdcard/new-image.img of=/dev/block/by-name/splash_b
Works fine, unsure if it would affect updating or reflashing so I will probably swap the old one back in before doing anything else.