Back up the partitions I mentioned and see if you have problems restoring it
Also, I've always found dynamic partitions to be messy, so try to reboot to recovery before restoring. Don't restore as soon as you back up.
Also, I've always found dynamic partitions to be messy, so try to reboot to recovery before restoring. Don't restore as soon as you back up.
Once again, read back this thread history as I sent privately the recovery.log file to BlackMesa123 before the release of the version 3.7.0_3 !
I'm a retired developer and as sys admin and even if I'm not an Android specialist I participated in different projects with older version of Android such as with Asus Transformer 1 (ethernet function when there was none at this time) and the Galaxy Note 3, but also in the Androidx86 (for PC) project as I added the multitouch function when this project was working only as single touch display... I was also working on the Mesa project...
I never worked on "custom roms" just because I prefer original manufacturers firmwares with proprietaries apps.
Any how, I am not trying to glorify myself but just to say I'm not a total noob...
I also have not enough time to participate to actual Android projects as I have other projects outside Android and the tech environment...
Very funny as you are telling a very different version from BlackMesa123 as he said only the "Super" partition is needed and since I reported him the Vendor partition could not be restored with TWRP 3.7..0_2, the reason he updated it to 3.7.0_3, and in he repeated the same in his last post !!! ^^
So please, read the posts with more attention before responding... ^^
Other problem, even with his last version I couldn't restore the Data partition as I said in my previous post and first post from today !!!
After a backup I always reboot into the recovery mode before creating a backup and I do the same when my restores failed !!!
At the very end, when everything fails I reboot into Download mode to flash a stock firmware...
Restoring the actual partitions version is not an option and is totally useless !
What I need is to restore the previous backup just in case I have problem after an upgrade.
As I said in my last post this is exactly what I do "reboot to recovery before restoring" and I always did so !!!
I'm in genuine surprise here. It looks like the one not knowing how to read or understand what's being written is someone else lol
BlackMesa123 said to back up super instead of vendor because vendor is included inside super and the vendor backup/restore could be broken because of how dynamic partitions work. He NEVER said that's ALL you need for a complete backup.
I'm seeing a recurring theme here. You keep posting over and over and over again you're having trouble with the same partitions (odm, Vendor, system, product)
And we've told you. Don't back those partitions up, just back up super which has those partitions because individually is when it causes problems. I don't know why that's so hard to understand.
As you said LOL as looks like you're missing some posts including the one when I said I sent the recovery.log file to BlackMesa123 privately !!! ^^
I guess you have problems with your glasses and trouble with time... LOL
First read my post #100. Then
"BlackMesa123 :
Jan 3, 2023
Backup/restoring logical partitions might not work correctly due to how this feature works. Try to backup the whole super partition instead of each partition individually (system/vendor/odm/product), also make sure your external SD isn't formatted as FAT32 since this FS has a 4GB limit per file that might break your backup files."
So his instructions were not very clear...
Then this is because I sent him a recovery.log file he rebuild a new 3.7.0_3 version of his TWRP to fix these issues or supposed to be... as I only had issue in restoring both Vendor boot and Vendor system partition with 3.7.0_2 and which was fixed with the latest version, except the latter was unable to restore the Data partition and the Super partition precisely... ^^
What is hard to understand is when you do a full backup, each partition should be "packed" separately even though these partitions are dynamic : there is a beginning and an end with optionally an index to indicate the position of each of them. No ???
So even after a full backup, if you restore only the Super partition there should be no problem with system/vendor/odm/product partitions but I had problems with these same partitions, including the biggest problem with the Data partition (error 255) which has no relationship with the Super partition !
Finally, you asked "Why are you trying to restore a very old backup when you've had problems over and over again restoring it?", but is CVL2 that old to you ??????? ^^
Post #100 says
Which you then sent the logs to the dev and got fixed in January 4th
Here you say that your restore was OK
Then here you say you have problems with a backup you made BEFORE it was fixed which you concluded that it wasn't compatible with an old restore
Here, you say you unticked the product partition. This means you backed up product partition after we've countless times have told you
Do NOT backup the product partition
Do NOT backup the system partition
Do NOT backup the odm partition
Do NOT backup the vendor partition
Please PLEASE PLEASEEEEEEEEEEEEE backup the Super partition, not these individually.
Is everything understood now? Do you know what you need to do?
EDIT: Let me try to explain it again so that we're all in the same page here
Back up:
- Data
- Super
- Boot
- EFS
And that's it. That's all a backup needs.
Don't backup system, don't backup vendor, don't backup odm, don't back up product. I know you mentioned something about not being able to restore data but give our backup method a try. If you're still having the 255 error with your data restoration (and I mean data as in the data partition, not data as a general term) then send the developer ANOTHER log since the first log you provided has nothing to do with this new problem you're having
Last edited:
It was true as it was the actual Android version (CVL2 - XEF) and a totally fresh new backup but I had the issues with the previous version CVI6-XEF created less than a month ago and it was already Android 13 !!! ^^
I then said we will see with the next Samsung firmware...
Thus you forgot my first post of the day #110 :
"I installed another firmware from Australia on my french phone, then re-installed your TWRP and I tried to recover my previous backup (CVL2) with the super partition but the operation failed with error message in regard with ODM, VENDOR and another partition I can't remember (probably the Product partition)...
I couldn't even restore my data partition due to an error 255. So I lost all my apps, data and my settings !"
So the Australian Android version I installed as I thought it was newer : A528BXXU1DWA2 and I reinstalled the latest TWRP version again and I tried to restore the CVL2 backup that led to the issues I described !
So this a indeed a real issue if you can't restore a previous backup or any older backups since the bootloader is the same !!!
You just forgot the phrase before the fact I unticked the product partition : "So to avoid a soft brick or a bootloop I tried to recover from my latest CVL2 backup but the restore stops at the "Product" partition with a failed message !" I didn't want to create a book to describe the issue so I forgot to explain it was after re-installing the latest TWRP version 3.7.0_3.
Again the messages was unclear and was not countless as you pretend.
So what you suggest is to let this TWRP unfinished, buggy and to use it NOT the standard way and not as it should normally work ???
And yes I was actually talking about the Data partition not being able to restore it !!!
Finally, what about the recovery partition : backing up or not ???
What I suggest is you leave those partitions alone to people who actually know what they're doing
I've given you the proper way of creating a full backup. Other partitions aren't needed for regular users. If doing it my way still doesn't work for you then provide logs so that we can look of it and finally tell you what's wrong instead of us trying to imply lots of what you're doing wrong
No, not needed. Why would you need to backup the recovery?
You still don’t understand (or don’t wanna understand) this is the new standard for Android devices, you just have to backup 1 bigger super partition rather than each logical partitions inside it just to be sure you don’t encounter any issue due to the mismatched metadata in super. There’s nothing you, me or anyone can do about (unless you know how to use lptools to edit the super metadata), deal with it.
Regarding other non-logical partitions, recovery logs would be much appreciated to understand what’s wrong with your device, the error code alone just tells us something got wrong while backing up/restoring.
You still don’t understand (or don’t wanna understand) this is the new standard for Android devices, you just have to backup 1 bigger super partition rather than each logical partitions inside it just to be sure you don’t encounter any issue due to the mismatched metadata in super. There’s nothing you, me or anyone can do about (unless you know how to use lptools to edit the super metadata), deal with it.
Regarding other non-logical partitions, recovery logs would be much appreciated to understand what’s wrong with your device, the error code alone just tells us something got wrong while backing up/restoring.
I have already spent so many hours to rebuild my system all over again and I'm fed up with this !
I wish someone else would send you the recovery.log file as I'm sure I'm not alone to have this issue.
If other people don't have any issue with your recovery restoring the Data partition or any other partitions the standard or non standard way, then let us know either !!!
Hello, I need clarification on this, "if you've already rooted your device you can skip it and flash directly the recovery without any extra steps." This means If my device is rooted i can use this method from TWRP site "
App Install Method (Requires Root):
Download the Official TWRP App (root required):
Install the app and open it. Agree to the Terms. Select TWRP Flash. Select your device from the device list (a52sxq) and choose a version. The file will download to your Downloads folder. Browse to and select the file. Tap on Flash to Recovery. Find out more about the app here."
Or so it means that i can go directly to this "Download Odin3, Samsung's Android USB Drivers, the latest TWRP's tar and a disabled vbmeta image." and on flashing procedure?
Thank you in advance
Having your device rooted implies you have already have formatted your data partition and flashed a patched vbmeta, so you can just flash the recovery.img without any extra steps either via the TWRP app or another way.
Thanks you, yes my device is rooted but i did not flashed a patched vbmeta, i followed instructions from Magisk, this
"
Instructions
- Use either samfirm.js, Frija, or Samloader to download the latest firmware zip of your device directly from Samsung servers.
- Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
- Press the Install button in the Magisk card
- If your device does NOT have boot ramdisk, check the “Recovery Mode” option
- Choose “Select and Patch a File” in method, and select the AP tar file
- Start the installation, and copy the patched tar file to your PC using ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].tar
DO NOT USE MTP as it is known to corrupt large files. - Reboot to download mode. Open Odin on your PC, and flash magisk_patched.tar as AP, together with BL, CP, and CSC (NOT HOME_CSC because we want to wipe data) from the original firmware.
- Your device should reboot automatically once Odin finished flashing. Agree to do a factory reset if asked.
- If your device does NOT have boot ramdisk, reboot to recovery now to enable Magisk (reason stated in Magisk in Recovery).
- Install the Magisk app you’ve already downloaded and launch the app. It should show a dialog asking for additional setup.
- Let the app do its job and automatically reboot the device. Voila! "
Magisk patches both boot.img and vbmeta.img so you’re good to go.
The “.img” one, “.tar” file should be used only on Odin3.Great
And i have one more question, when downloading TWRP from TWRP app(to flash recovery from app) which file to select, img or img.tar?
I suppose img?
@BlackMesa123 and @ShaDisNX255 ,
Looks like if you don't get issues with Data partition and probably with other partitions is the fact you're using a custom and probably a permissive kernel !
I didn't use this recovery since my last post but I saw in the other XDA sections with newer Samsung phones with Android 13 they are having the same problem whether with Snapdragon or with Exynos.
So Data partition can't be recovered with stock kernel from Samsung as it is read only partition !!!
I saw you were supplying a custom kernel based on A528BXXU1DVK5 which is not the latest version but the latest Samsung supplied the source code and I don't know if there are many changes between A528BXXU1DVK5 and A528BXXUDWA4 which is the latest firmware dated January 2023.
Anyway, I'm not planning to install your custom kernel, but I just wanted to let you know and also to other users/readers of this thread about my investigation about this issue and this should probably be added to OP...
At least, this does prove the problem was NOT about me and not just on my side... ^^
Looks like if you don't get issues with Data partition and probably with other partitions is the fact you're using a custom and probably a permissive kernel !
I didn't use this recovery since my last post but I saw in the other XDA sections with newer Samsung phones with Android 13 they are having the same problem whether with Snapdragon or with Exynos.
So Data partition can't be recovered with stock kernel from Samsung as it is read only partition !!!
I saw you were supplying a custom kernel based on A528BXXU1DVK5 which is not the latest version but the latest Samsung supplied the source code and I don't know if there are many changes between A528BXXU1DVK5 and A528BXXUDWA4 which is the latest firmware dated January 2023.
Anyway, I'm not planning to install your custom kernel, but I just wanted to let you know and also to other users/readers of this thread about my investigation about this issue and this should probably be added to OP...
At least, this does prove the problem was NOT about me and not just on my side... ^^
Got nothing to do with your kernel since TWRP is run with it's own version of a kernel.
How can it be a read only partition if that's where all user apps are downloaded and the user settings are stored?
I have no idea what @BlackMesa123 did and changed in his custom recovery kernel...
Was it a stock kernel or a custom permissive kernel ? I don't know !
You both are pretending you didn't encounter any issues with whatever partitions so I suspect you are both using a custom kernel as @BlackMesa123 released his own custom kernel in this A528B section and you're probably using a custom kernel with your custom ROM either... ^^
I can't retrieve the xda thread mentioning this data partition issue which could be fixed with a permissive kernel at the moment. But I'll let you know when I put my hand on it.
What I just know is that I can't restore my previous data partition as I was able to do before the release of Android 13 on my A528B phone, just as I didn't get any issues at all with any other partitions with Android 12 btw...
And from now we/you didn't get any feedbacks from any other users , but me since the release of A13...
Strange, don't you think so ???
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
If you just want to install Magisk you can simply download the "Magisk-vX.X.apk" from its GitHub page and rename it to "Magisk.zip". Then flash it using TWRP and voila, you've installed Magisk.
GSIs are a completely different thing (it's basically a generic system.img that is supposed to run on a majority of Android phones without any modifications). I wouldn't really recommend using GSIs as this phone has actual custom ROMs that work way better (more features working, less bugs, etc).1
Yes, usually you can. If you can see "OEM Unlock" in developer settings you will definitely be able to flash TWRP. -
36Team Win Recovery Project
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 doing this to your device * 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. */
Disclaimer:
- I am not responsible about any damage of any kind that this custom binary may cause.
- Please pay attention to this post & related ones before proceeding and follow the guide correctly. I will not offer support for any issues that have been already stated.
- Your Knox Warranty Bit will be blown once you flash this or others custom binaries, preventing you to use Knox features. It can't be resetted in any way, so think twice before flashing this.
- Bugs can be reported here in XDA or via the community's Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs.
What's TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, root your device and more.
Read more about TWRP here: https://twrp.me/about/
How do I flash and set it up correctly?
Please notice that the following guide is meant for full stock devices, if you've already rooted your device you can skip it and flash directly the recovery without any extra steps.
Before starting, make sure to backup all your data and important files stored in your phone, since this procedure will format your data partition.
- Download Odin3, Samsung's Android USB Drivers, the latest TWRP's tar and a disabled vbmeta image.
- Make sure your phone's bootloader is unlocked, follow the guide below in case it isn't:
- Open the Settings app, enter Developer Options and enable OEM unlocking (If you don't see Developer Options, enter into About phone>Software info and tap "Build number" 10 times to show it).
- Enter Download Mode: to do so power off your device, connect it to a computer via an USB cable and hold both volume up and volume down buttons.
- Long press volume up to unlock the bootloader. This will wipe your data and your phone will automatically reboot.
- Go through the initial setup. Skip through all the steps since data will be wiped again later. Make sure to connect the device to Internet during the setup.
- Enter Developer Options and check that the OEM unlocking option exists and is grayed out. This means our bootloader is unlocked and your phone has no KnoxGuard lock set.
- Connect your phone to your PC and boot in Download Mode (power off your device and hold both volume up and volume down buttons).
- Open Odin3, select the TWRP tar by clicking the "AP" button and the patched vbmeta tar by clicking "USERDATA", then press the Start button.
- Reboot your phone in recovery mode: while it still plugged in your PC, hold both the power and volume up buttons.
- Once TWRP has booted you need to format again your data partition in order to be able to boot in system again. To do so touch Wipe>Format Data and follow the instructions in screen.
Bugs:
- Decryption will only work if no password/PIN/pattern is set in Android (One UI 4.x/5.x).
Download:
Galaxy A52s 5G (a52sxq):
twrp.me
Bootloader/Modem collection:
GitHub
Sources:
Kernel source code: https://github.com/BlackMesa123/android_kernel_samsung_sm7325/tree/sep-15/twrp-12.1
Device tree: https://github.com/TeamWin/android_device_samsung_a52sxq
Changelog:
Check Post #2.
A52s 5G Community Telegram Groups:
General
Development
Credits:
Samsung for the kernel source code
TeamWin for their awesome recovery
@Captain_Throwback for his help and troubleshooting
@ShaDisNX255 & @ronardnx for testing out the recovery14Changelog:
Please note that this only includes device-specific changes. For global TWRP changes, go to twrp.me.
20240218 (3.7.1_12-0)
- Updated kernel to FWK4
- Fix exFAT related issues
20231224 (3.7.0_12-4)
- Updated kernel to EWJ1
- Support Android 14 decrypt
- Set framerate to 120hz
20230104 (3.7.0_12-3)
- Fix /vendor backup restoring
20221223 (3.7.0_12-2)
- Updated kernel to DVK5
- Support Android 13 decrypt with no password
- Fix /efs, /sec_efs backup
20221208 (3.7.0_12-1)
- Fix fastbootd
- Disable stock recovery patching in /vendor
20221015 (3.7.0_12-0)
- First release14Really proud to announce that my request to became the official TWRP maintainer for Galaxy A52s has been accepted! Link in the main thread has been updated to now redirect directly to the twrp.me page of this device.9It's been a while since I released something here in XDA. I'm happy to join the modding train again with this custom recovery, hoping to see more cool stuff come out for this device soon
6
