Yes, tested on my G781B with Android 13. I used it for install the Bandido kernel and it workedDoes anyone know if it already works with android 13(One UI 5.0)?
I really dont know what about other kernels, but now I can say that Bandido works pretty well, you can try Prime and tell me what about that cause Im looking for that experience too, sorry ^^Thank you for your quick response, I also have the G781B model and was wondering if it would work with android 13. Now that I have the answer, I have another question. I'm also looking forward to installing a custom kernel, (That's why I was wondering if twrp would work with android 13) what would you say is the best custom kernel for my model when it comes to performance and battery because I want a good balance between good battery and good performance. Form what i have collected the best kernal are primekernal, bandido and kimbokernal. So what would you say is the best kernal when it comes to balance between good performance and good battery life?
Thank you in advance.
Note: steps 2-6 are important, missing any will lose your data.Hi everybody,
Sorry in advance for this noob question.
Starting from stock Android12, I went thru all @afaneh92 process and it's working nicely.
Now I'd like to upgrade to Androi13: do I have to rerun exactly all the process (& so loosing my data)?
In other words: are BL unlock and avb disable persistent after an Odin flash ?
Thank you for sharing your skills !
+1Hi everybody,
I've got a S20FE SM-G781B snap 5G with Android12 / One UI 4.1.
Thank to @afaneh92 and many people here, BL unlock, TWRP install and root with Magisk ran perfectly.
For about 1 month now, Android13/ONE UI 5.0 stock FW is available. As a noob, I have some questions about upgrading my phone:
1 - We have to upgrade manually with Odin. But do we have to reflash the vbmeta_disable tar file after (or during) FW upgrade ? (guess the FW flash will enable the verified boot check)
2 - The same way: I imagine that the stock FW flash will overwrite the recovery so we have to reflash TWRP ? May be we can avoid this rebooting on existing TWRP after FW flash and before 1st system boot ?
Is afaneh92's TWRP Rev. 3.7 compatible with Android13/ONE UI 5.0 ?
3 - Is root cancelled by the upgrade ?
As a last question, is there a chance to keep our data thru this procedure ?
Sorry for this bunch of questions but I prefer prevention to fixing if I do something wrong...
Thanks guys !![]()
just follow topjohnwu's instructions, flashing a patched AP archive is preferred over flashing a renamed apk.Hi, I'm currently on Android 13 One UI 5, clean install after a failed update from Android 11 One UI 3.1 in which I had bootloop and had to do a full wipe of all my personal data and lost everything. I want to root my device again, can someone please provide a detailed guide to do it without messing everything up again? My device is an SM-G780G (the 4G Snapdragon).
So I need to follow the Samsung part in that link, got it. But what do you mean with flashing a patched AP instead of a renamed apk? is it for Magisk or what part is that?just follow topjohnwu's instructions, flashing a patched AP archive is preferred over flashing a renamed apk.
![]()
Magisk/install.md at master · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.github.com
it's covered in the guide, Samsung divides their firmware into 4 archives AP, CP, BL and CSC (or HOME_CSC which is the same as csc but doesn't wipe the phone).So I need to follow the Samsung part in that link, got it. But what do you mean with flashing a patched AP instead of a renamed apk? is it for Magisk or what part is that?
Ohhh I understand now, I'm going to do the process later tonight, thanks a lot!it's covered in the guide, Samsung divides their firmware into 4 archives AP, CP, BL and CSC (or HOME_CSC which is the same as csc but doesn't wipe the phone).
the recommended method to root is copying the AP archive to your phone, patching it with the magisk app, copying I back to PC and flashing it along with the other archives in Odin.
oh BTW rooting this way would mean you'd have to flash twrp again as the AP archive contains the stock recovery.Ohhh I understand now, I'm going to do the process later tonight, thanks a lot!
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
multidisabler
. - Run multidisabler again!
.multidisabler
again. will see - Finished.
when done.yes
.To disable encryption manually:
You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.qcom
To avoid stock recovery restoration manually:
Rename system/recovery-from-boot.p to recovery-from-boot.p.bak
I will start working on the new kernel source soon.@afaneh92 just checking in to ask what if any sources to you want / need to help you ?
I'm on the Samsung open source site now and downloading a zip for G781BXXU2CUD1 but I've no idea if it's kernel sources inside (280mbs ish). another page I saw here mentioned using the inquiry tab to submit a request.
if you can tell me exactly what you want I'll more than happily put in a request for it, I'm sure others would too.
I'll edit this later and add the zip files full name that I've downloaded and if you want that I'll put it mediafire or similar.
SM-G781B_SEA_RR_Opensource.zip is the archive name, taken from clicking on G781BXXU2CUD1 which matches my current baseband and buildnumberView attachment 5299763
New build is up.
I'll do my best still testing everything compiling my data etc@QRCode please consider making a thread about the exact method it required, resources needed and your experience with it.
this sort of thing will be useful to others. particularly of interest is the features that don't work currently.