Development [ROM] BeyondROM v4.3 [21/03/2024]-[DXBD]-[EXYNOS]-[SM-S908B-S906B-S901B]

[tschertel]

It gives an error when installing the program. I downloaded the RAM belonging to my system, but it didn't work. My system is sm-s908b

It gives an error when installing the program. I downloaded the RAM belonging to my system, but it didn't work. My system is sm-s908b

Did you unlock the bootloader? Did you install TWRP?

 

[tschertel]

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.

 

[starbucks2010]

What updates are you taking about? Beyond rom 2.0 is based on the latest fw bvja.

 

[tschertel]

What updates are you taking about? Beyond rom 2.0 is based on the latest fw bvja.

I mean, when a new bvja comes out.

 

[Skyllery]

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.

 

[starbucks2010]

probably bad coverage ... LTE signal of 1-2 bars drains quite fast the battery

 

[Skyllery]

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

 

[tschertel]

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.

 

[juda iskariotsky]

good job, it could be nice if you post it in s22+ thread https://xdaforums.com/f/samsung-galaxy-s22-plus.12513/

 

[Mr.5g]

del

 

[starbucks2010]

Any S22+ S906B user willing to test BR21 BVKB ?

 

[Phk]

What's the possibility of using full disk encryption with this rom?

Thanks

 

[starbucks2010]

What's the possibility of using full disk encryption with this rom?

Thanks

what's the use of encryption if the twrp doesn't support it?

 

[Phk]

what's the use of encryption if the twrp doesn't support it?

FDE should come from boot, why does TWRP need to support it? Is it the first boot system?
Thanks

 

[MuyKurioso]

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.

 

[starbucks2010]

No, it won't work on snapdragon devices.

 

[starbucks2010]

The rom has been updated to the latest BVKB fw Nov 2022.

Happy flashing good people!

 

[BrimoFan123]

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?

 

[Kuba1996]

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://xdaforums.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

 

[BrimoFan123]

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
?