What! You can take screenshots in any version of TWRP by pressing the power+vol down buttons similarly how you take one in android OS. well i don't know why you cant see the version number even i can't see it maybe i might have removed it in building the TWRP by mistake. Yes i will take a backup . No worries you can try it or let others try it outThis is actually not screenshots of a working TWRP as it could be a picture you got from anywhere for any other device sepcially when there is no screenshot function from TWRP... ^^
There is also no number version including no version of the Android you've been using specially when using the Team Win Recovery Project.
So do a backup of your full system, and take pictures at different steps of the process with the naming convention of the nand backup.
I'd typically be the first one to test it, but this time I'll wait till someone else do install and use it... ^^
Ah please don't remind me again and i will test everything in the TWRP okay
Yeah rightMaking a video of the whole process would be very nice but I think it's a too big "job"...
Just some good screenshots at relevant steps of the backup and restore processes : naming convention of the nandbackup before the backup and restore processes would be enough.
From there we should have enough and relevant information...
One important step and test is to restock the phone (so the TWRP backup should be done on the SDCard)
Reinstall the TRWP, then a other screenshot just before the restore process to see if we have the same naming convention then check if nothing has been lost and if the system isn't corrupted...
If all theses steps are met, I will accept to test this TWRP myself... ^^
Yes i will test all functions of the TWRP and give InformationOkay, okay, I just meant you shouldn't release anything in a hurry/rush before you tested everything yourself, specially with a so dangerous tool like this !!!
Myself I spent many days testing rooting and tested it in different ways before releasing the guide and the root app.
I was also planing to release a guide to upgrade a rooted firmware without losing data at the time of Android 11, then I rejected it when I discovered it was not compatible anymore with Android 12...
You may not have a legal obligation nor legal responsability but you still have a moral obligation/responsibility to others if your tool is bricking or corrupting others phone... ^^
Ok I will check on it as soon as possible sorry for the inconvenienceI tried @TMHAKIMs TWRP:
1. Flashed Original firmware A528BXXS1BVB1 with csc XEZ and then flashed the recovery
- After reboot I still got the standard Android recovery. I have no idea what happened, but it didn't work
2. Flashed Magisked firmware A528BXXS1BVB1 with csc XEZ and then flashed the recovery
- after reboot to recovery it just frozen on the "Samsung Galaxy Secured by Knox" screen. Probably trying to get to the recovery, but couldn't. Had to reflash.
I can safely say that the TWRP doesn't work with A528BXXS1BVB1 firmware.
Well said...although I'd like to point out that we should use respectful and courteous language.You forget that XDA "Developers" is made for "Developers", it's OK to post projects WIP as long as a disclaimer is posted and users are smart enough to read the disclaimer. Not everything needs to be working perfectly, it's completely fair to post your source and work in XDA even if it's not completed so that hopefully a more skilled developer can lend a hand with some of their experience and not be a complete a**** about it.
And no, I'm not only talking about you. There are some people that love pointing out how unexperienced you are and how you're very wrong about the work you did.
You made your guide to the general public and you made sure everything worked the way it's supposed to, and that's fine too, but don't expect everything posted in this site to be working flawless without any bugs, that's not what this site was created for.
We can all learn from each other and not turn this into an ego battle. We're supposed to encourage more people to learn, not discouraging them by telling them all they're doing is wrong.
You forget that XDA "Developers" is made for "Developers", it's OK to post projects WIP as long as a disclaimer is posted and users are smart enough to read the disclaimer. Not everything needs to be working perfectly, it's completely fair to post your source and work in XDA even if it's not completed so that hopefully a more skilled developer can lend a hand with some of their experience and not be a complete a**** about it.I am just saying the same thing as I said the first time I responded to you : Don't release anything before you tested it yourself and before you are sure your twrp is really working and you shouldn't considered others as your "guinea pig" !!!!
This is not a game or a challenge specially when you have no experience in building such a tool just as you admitted it yourself now !
Just before I published my tutorial on how to root the A52S 5G phone I spent many days in testing it in different ways : rooting it, restocking my phone and re-rooting again and again to be sure I was not doing mistakes.
Even after I was sure it was working I totally updated my tutorial taking into account feedback from users to clear up some parts of the tutorial that was not understood or because the Magisk version and some modules have changed.
I have myself the complete twrp tree to build a working twrp for A52 4G phone and the device tree for A52S 5G but I know there is still a lot of work before I can build a working twrp for our phone as I don't considered this as a competition to be "the first one" ... ^^
I know I have to build this twrp from source code and not by swapping incompatible images as you did.
I also tested the no touch twrp but my phone was bootlooping into this custom recovery and thus I had to re-stock completely my phone and I lost some of my apps and data even though I did a full backup. So I also warned other users not to use it with clear explanation on the risk if they do install it even though some may be attempted to test it themself... ^^
I am a retired developer and sys-admin but that doesn't mean I know everything as building such a tool is also new to me, so I am taking my time to understand the whole logic as I don't want to mess up others' phone !