Development [ROM] BeyondROM v2.3 [22/01/2023]-[BWA2]-[EXYNOS]-[SM-S908B-S906B-S901B]

Search This thread

tschertel

Senior Member
Jan 30, 2011
157
24
Mannheim
Samsung Galaxy S22 Ultra
Hi @starbucks2010

I'm not asking for any ROM update or anything. I'd just like to ask if this ROM is still in development.
There are one or two more ROMs for our S22 Ultra, and their threads have updates, while here we don't have much action.
Like I said, this is a humble question, just to make sure we gonna have updates when they are required/available.

Thanks.
 

Skyllery

Senior Member
Mar 22, 2013
855
474
St-Denis Reunion
LG G3
Sony Xperia Z3
Thx a lot for your hard work,

Jumped to custom rom because having an issue with battery (Drain in LTE) since day 1 and neither factor reseting nor reflashing stock firmware did anything. Barely have 3h SOT without using much the device. I hope a debloated rom will fix my issue or my neighborhood will see a flying S22U somedays.

Cheers

Edit : 15.11 : 1st real cycle .. 50% Left and +3Hrs SOT. Still having this strange drain in LTE but Literally doubled SOT with half LTE half Wifi during the day and even if the battery isn't settled yet.
Triying to install BetterBatteryStats to figure what is draining in LTE.
 
Last edited:

Skyllery

Senior Member
Mar 22, 2013
855
474
St-Denis Reunion
LG G3
Sony Xperia Z3
probably bad coverage ... LTE signal of 1-2 bars drains quite fast the battery
I live on an island with lots of mountains in middle. But on the coast the coverage isn't that bad. Mostly full bars and LTE+ connected. I switched to LTE preferred to avoid 5g search as it's not yet available on my carrier.

But it's way better on your rom. Idle 1.6% / h screen off and around 8%/h screen on wifi 12%/h on LTE.
Will let the battery settle and see in some days. At least with root i can log everything and see wakelocks.

Regards
 
  • Like
Reactions: starbucks2010

tschertel

Senior Member
Jan 30, 2011
157
24
Mannheim
Samsung Galaxy S22 Ultra
I live on an island with lots of mountains in middle. But on the coast the coverage isn't that bad. Mostly full bars and LTE+ connected. I switched to LTE preferred to avoid 5g search as it's not yet available on my carrier.

But it's way better on your rom. Idle 1.6% / h screen off and around 8%/h screen on wifi 12%/h on LTE.
Will let the battery settle and see in some days. At least with root i can log everything and see wakelocks.

Regards
I just switched off the 5G because it's not available everywhere here (Germany), so the phone keeps searching and uses more battery.
Now I have much longer battery life.
 
  • Like
Reactions: Skyllery

MuyKurioso

Senior Member
Mar 17, 2015
205
38
Hi, thanks for all of your hard work. Do you happen to know if this will work on a SM-S906E/DS?

Have a good day.
 

rafal.polska.b

Senior Member
Mar 22, 2015
266
70
Gdynia
I'm currently on stock ROM Android 12 AVI3 Kernel 5.10.66-afaneh92. I'm rooted, TWRP 3.6.2_12-4 and Magisk 25.2 with bunch of modules.
I need your help for moving from current stock ROM to BeyondROM Android 13 BVKB.
What steps should I take?
Should I first move back completely to stock Android 13?
I'm thinking about this process:
1. Make inventory of installed Magisk modules, make backup of my files to USB OTG
2. Patch AP_BVKB file in Magisk, transfer patched file to PC, extract vbmeta.img
3. Extract recovery.img from twrp-3.7.0_12-1_afaneh92-b0s.tar
4. Create new twrp-vbmeta.tar file which contain vbmeta.img from patched AP_BVKB file and recovery.img from twrp-3.7.0_12-1_afaneh92-b0s.tar
5. Remove fingerprints and lockscreen's PIN
6. Uninstall all Magisk modules. Once all modules are uninstalled followed by reboots perform final reboot to download mode
7. Using Odin flash all stock files in slots: AP->AP, BL->BL, CP->CP, CSC->CSC (Which Odin to use? Original one 3.13.1 or 3.14.4?)
8. In stock recovery format data, start Android 13 but configure nothing
9. Reboot to download mode
10. In Odin's options unselect Auto Reboot and flash twrp-vbmeta.tar in slot USERDATA
11. When flashing is completed keep USB cable plugged in, hold Volume Down and Power and as soon as the screen goes black press and hold Volume Up and Power in order to boot directly into TWRP. If this step is unsuccessfull then repeat steps 8 and 9
12. In TWRP full wipe (wipe -> Format Data -> type "yes" when asked and confirm)
13. Reboot phone back to TWRP (Reboot -> Recovery)
14. Flash BeyondROM (in TWRP -> Install. If using OTG "select storage", select "USB OTG" select BeyondROM zip on the USB device, wipe to confirm, follow on screen options, when flash is complete "save logs" (in case you have any flashing issues) click finish, reboot to System
15. Configure system, download and install Magisk Canary (?) (why not the official 25.2 or Magisk Delta?) and install Magisk's modules
16. Install Swift Backup and restore applications from backups stored on Google Drive (or install applications from Google Play Store and restore from Swift Backup only application's data? I saw somewhere that for upgrading from Android 12 to Android 13 it is better to not restore applications and data but install applications from Play Store and then restore from backup data only - can someone deny or confirm?)

Are these steps 1-16 correct?
 
I'm currently on stock ROM Android 12 AVI3 Kernel 5.10.66-afaneh92. I'm rooted, TWRP 3.6.2_12-4 and Magisk 25.2 with bunch of modules.
I need your help for moving from current stock ROM to BeyondROM Android 13 BVKB.
What steps should I take?
Should I first move back completely to stock Android 13?
I'm thinking about this process:
1. Make inventory of installed Magisk modules, make backup of my files to USB OTG
2. Patch AP_BVKB file in Magisk, transfer patched file to PC, extract vbmeta.img
3. Extract recovery.img from twrp-3.7.0_12-1_afaneh92-b0s.tar
4. Create new twrp-vbmeta.tar file which contain vbmeta.img from patched AP_BVKB file and recovery.img from twrp-3.7.0_12-1_afaneh92-b0s.tar
5. Remove fingerprints and lockscreen's PIN
6. Uninstall all Magisk modules. Once all modules are uninstalled followed by reboots perform final reboot to download mode
7. Using Odin flash all stock files in slots: AP->AP, BL->BL, CP->CP, CSC->CSC (Which Odin to use? Original one 3.13.1 or 3.14.4?)
8. In stock recovery format data, start Android 13 but configure nothing
9. Reboot to download mode
10. In Odin's options unselect Auto Reboot and flash twrp-vbmeta.tar in slot USERDATA
11. When flashing is completed keep USB cable plugged in, hold Volume Down and Power and as soon as the screen goes black press and hold Volume Up and Power in order to boot directly into TWRP. If this step is unsuccessfull then repeat steps 8 and 9
12. In TWRP full wipe (wipe -> Format Data -> type "yes" when asked and confirm)
13. Reboot phone back to TWRP (Reboot -> Recovery)
14. Flash BeyondROM (in TWRP -> Install. If using OTG "select storage", select "USB OTG" select BeyondROM zip on the USB device, wipe to confirm, follow on screen options, when flash is complete "save logs" (in case you have any flashing issues) click finish, reboot to System
15. Configure system, download and install Magisk Canary (?) (why not the official 25.2 or Magisk Delta?) and install Magisk's modules
16. Install Swift Backup and restore applications from backups stored on Google Drive (or install applications from Google Play Store and restore from Swift Backup only application's data? I saw somewhere that for upgrading from Android 12 to Android 13 it is better to not restore applications and data but install applications from Play Store and then restore from backup data only - can someone deny or confirm?)

Are these steps 1-16 correct?
1.Yes
2,3,4. In twrp theard by afaneh You have 2 tar files (one vbmeta, second twrp) and You canon do one
5,6. Skip
7. Use Odin 4.14.1_3B_PatcheD (https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/). Use AP-AP, BL-BL,CP-CP,CSC-HOME_CSC (only if You use earlier multidisabler) and in USERDATA file which You do in 2,3,4 steps. Don't forget about unselect Auto Reboot.
8a. If You used multidisabler earlier while installing twrp then You can use HOME_CSC to don' lose data. After odin success don't unplug USB and boot to twrp ( for clean flash you must do factory reset-recomended before flash BR. For dirty just flash BR)
8b. If You don't used multidisabler earlier You must after boot to TWRP:
- Go to Advanced > Terminal, type: multidisabler.
If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.
- Type: multidisabler again. will see - Finished. when done.
- Go back to Wipe > Format Data > type yes.
- Reboot to recovery.
-Flash BR
15. For Samsung devices canary magisk is recomended but other versions should work too (Delta is fork which lets you use magisk option )
16. Restoring backups or installing belong to you.

I see You are from Poland, You can send me pm when you will questions or need help
 
  • Like
Reactions: starbucks2010

rafal.polska.b

Senior Member
Mar 22, 2015
266
70
Gdynia
Then I'm confused.
There is vbmeta.img in patched by Magisk AP
There is vbmeta.img in vbmeta_disabled_R.tar (TWRP thread)
Which vbmeta.img should I use and combine with recovery.img taken from twrp-3.7.0_12-1_afaneh92-b0s.tar into twrp-vbmeta.tar and put that twrp-vbmeta.tar into USERDATA Odin's slot?

Is it correct:
Patched by Magisk AP into AP slot
BL into BL slot
CP into CP slot
CSC into CSC slot
twrp-vbmeta.tar (which contain: recovery.img from twrp-3.7.0_12-1_afaneh92-b0s.tar + vbmeta.img from vbmeta_disabled_R.tar) into USERDATA slot
?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    The BR23 has been updated to the latest fw BWA2 Jan 2023 patch level.
    Please read carefully the rom changes regarding magisk and flash magisk alpha from OP or you won't see the root.

    Happy flashing good people ! :)
    1
    The BR23 has been updated to the latest fw BWA2 Jan 2023 patch level.
    Please read carefully the rom changes regarding magisk and flash magisk alpha from OP or you won't see the root.

    Happy flashing good people ! :)
    s906b flashed
    best rom mate, thanks for your hard work
    1
    1
    I don't have one.. how come I'm the only one with that problem though
    You're not the only one. I had the same issue and just ended up buying an OTG cable. Then, I had a message that the ROM cannot be installed since you need to update from BWA2 version of the firmware and I had none after performing full data wipe. Eventually, I just flashed another ROM via Odin😂
  • 14


    logo_beyond-xda.png




    Latest Version v2.3 [22/01/2023]

    ROM Maintainer: Andrei @starbucks2010




    ROM Info:

    Supported devices:
    [SM-S908B] [SM-S906B] [S901B]

    ROM Base: S90xBXXS2BWA2 (Android 13) Jan 2023 Patch Level



    ROM Features:


    Kernel:
    • Stock Samsung kernel
    • All partitions RW

    CSC features:
    • Call Recording
    • Camera shutter sound menu
    • Real time network speed in statusbar
    • AppLock Enabled

    ROM Disarm:
    • Light ROM debloat
    • Disabled Encryption
    • Patched Samsung SmartWatch pairing
    • Disabled stock recovery-from-boot

    Modded Settings/Services
    • Screenshots in secure apps allowed
    • Phone status: Official
    • Software Info ROM Details

    Fixes:
    • Galaxy watch pairing
    • SafetyNet Patch (must enable Zygisk and install SN kdrag0n magisk module)
    • Secure Folder

    Other Tweaks/Mods:
    • Warning boot screen removed, BR custom boot animation
    • Automatic EFS backup
    • Various build prop tweaks
    • Pre-rooted with Magisk Alpha (needs magisk alpha app install after flash)
    • Netflix playback HD (tbc)
    • Unlimited storage for Google Photos


    ROM constraints:

    • Needs to install Magisk Alpha app after rom flash or you won't see the soot
    • For Safetynet and Wallet use latest kdrag0n v2.4.x magisk module



    Not working
    • Knox related apps: Samsung Pay, Samsung AutoFill



    Changelog

    v2.3

    - Based to latest firmware [BWA2] OneUI 5.0 **You must be on BWA2 firmware to flash BR2.3 ROM zip**
    -
    Switched to magisk alpha patching
    - Updated InCallUI (same app for half/full screen picture caller)

    #######################################
    PREVIOUS VERSION
    #######################################

    v2.2
    - Based to latest firmware [BVL1] OneUI 5.0 **You must be on BVL1 firmware to flash BR2.2 ROM zip**



    Credits


    - John Wu for Magisk
    - Mr. Waehere for the kitchen and support
    - afaneh92 for S22 TWRP and endless help
    - LeeXDA18 for help with knox/VK removal and more fixes
    - the elite team of ROM testers (Mark, Nuno, Kuba, Ashley and many more)
    - dutchman89 for Beyond boot logo
    - nguyenxuanhua for the Netflix tip
    - If you like my work and want to support me, consider buying me a coffee (PayPal link)


    Download Links

    CURRENT VERSION
    ###############################
    SM-S908B ROM Download BWA2 [BR2.3]
    SM-S906B ROM Download BWA2 (BR2.3)
    SM-S901B ROM Download BWA2 (BR2.3)
    ###############################


    USEFUL LINKS
    ###############################
    BeyondROM S22 Group [Telegram]
    S22 TWRP [XDA]
    S22+ TWRP [XDA]
    S22U TWRP [XDA]
    If you like my work, support me and buy me a coffee (PayPal link)


    Installation:

    **Note: These steps will trip Knox and possibly void warranty on your phone**
    **Note: Following these steps you will lose data on your phone, so back-up before continuing**


    UNLOCK BOOTLOADER:


    • Enable Developer Options: Settings > About Phone > Software Information > Keep clicking 'Build Number'
    • Enable OEM Unlock: Settings > Developer Options > Click 'OEM Unlock' to enable it
    • Turn of phone
    • Hold Volume Up + Volume Down, plug in USB cable (PC to Phone)
    • You’re now in download mode (Blue Screen)
    • Press and hold Volume up (bootloader unlock screen)
    • Pres Volume up to confirm
    • **Warning** This will now wipe your phone and restart and couple of times but this is normal
    • When the phone is booted, connect to internet, skip the initial setup, you don't need to sign in to anything
    • Unlock should be enabled now and greyed out
    • Congrats you've unlocked your bootloader !

    FLASH TWRP + PATCHED VBMETA

    • OEM Unlock should be enabled now and greyed out
    • Download TWRP and patched vbmeta for your device from above links
    • ]Boot phone into download mode (from power off Volume Up + Volume Down and plugin USB cable)
    • Press Volume up to continue
    • Load up ODIN
    • Go to options and turn off auto reboot
    • Select USERDATA slot and select the TWRP+Patched VBMETA file tar you built (Device Specific)
    • Click Start and wait for Odin to complete with a PASS message
    • Now Keep USB cable plugged in, hold Volume Down and Power and as soon as the screen goes black press and hold Volume Up and Power
    • You should now be in TWRP

    IN TWRP
    • Do a full wipe (wipe > Format Data > type 'yes' when asked and confirm)
    • Reboot phone back to recovery (Reboot > Recovery)
    • Download ROM and copy either to the phone (PC to Phone) or to a USB OTG device

    FLASH ROM:

    • In TWRP click 'Install'
    • If using OTG click 'select storage', select 'USB OTG'
    • Browse to the location of the ROM zip on the USB device, Select and wipe to confirm
    • Follow on screen options
    • When flash is complete, click 'save logs' (in case you have any flashing issues)
    • Click finish
    • Reboot to System
    • After flash and setup download and install Magisk Canary app from Magisk github and install, when you run for the first time the magisk will need to do some setup and will then automatically reboot the phone
    • After reboot you're all set, congratulations !

    Please take note of the changelog as it will mention if you need to be on a certain version to flash this version or if dirty flash from previous version is ok


    When upgrading FW to flash the latest these are the recommended steps.

    It is assumed that you are already on BeyondROM.


    • Download the latest/required version of the firmware (Samfirm, Frija etc...)
    • Unzip the ROM
    • Boot phone into Download mode
    • Load up Odin, turn off auto-reboot
    • Insert the relevant files into their slots (BL = BL, AP=AP, CP=CP, CSC=HOME_CSC) **It's important to use HOME_CSC to keep your data intact**
    • In the USERDATA slot insert your TWRP+PatchedVBMETA tar file (Device Specific)
    • Start Flash
    • When flashing completes, keep USB plugged in, hold Volume Down + Power, as soon as the screen goes black hold Volume Up + Power pressed to enter TWRP
    • When in TWRP, flash latest BeyondROM
    • When complete, save logs, reboot to system
    • Enjoy!

    Enjoy flashing good people ! :)
    6
    The BR23 has been updated to the latest fw BWA2 Jan 2023 patch level.
    Please read carefully the rom changes regarding magisk and flash magisk alpha from OP or you won't see the root.

    Happy flashing good people ! :)
    6
    The rom has been updated to the latest BVKB fw Nov 2022.

    Happy flashing good people! :)
    5
    The BR22 has been updated to the latest fw BVL1 Dec 2022 patch level.

    Happy flashing good people ! :)
    5
    How exactly did you achieve the rw? Can you please give me step by step tutorial? Thanks (y)

    So are you trying to tell me that I've been basically wasting my time by doing 1 on 1 customer support in private with you for over 12 pages since July trying to get my rw script to work for all Samsung devices? :unsure:
    I am a little bit disappointed. I was honestly expecting more high quality feedback and a little bit more enthousiasm from you as well as a little bit more honesty. :(
    You could've told me back in July that you cannot or do not want to help me make my rw script to work on ALL devices out there but you only want to make YOUR device rw... Isn't that a little bit egoistic on your part? :unsure:
    Speaking of honesty. Didn't you tell me the other day that you're not a developer yet here you are publishing a ROM that's fully rw in a thread with a [DEVELOPMENT] tag... :unsure:

    What is dubious about my rom?
    I always had options to make my rom from many other sources: twrp backup after running afaneh rw script, offline manual creation of rw images but I chose to help you hoping to automate the rw image creation with your script.
    I had the willingness to help you making the script working over 12 pages of discussion as you say and countless tests but you never listen to my advises.
    Honestly, no point of washing our laundries in public.

    And this is the end of this topic from my point of view.

    Guys guys guys, is it really the best place to have such a discussion?

    I highly advise you to use the 13th page of your long discussion to clear things out. It's not like you're new to XDA ... 😉