[ROM] BeyondROM V9.7 [20/03/2023] [A12 HWC1] [Mar Patch] [G970-G973-G975-F/FD]

Search This thread

dan.dior

Member
Feb 9, 2012
20
0
To this 'BR flashing guide'... Has it relevance, that there is no point with the VBMETA implementation?

Is it necessary and/or possible to flash it into the rooted and installed BR9.7 ?

Thanks for the ROM, all that work btw!
 

dan.dior

Member
Feb 9, 2012
20
0
Is the VBMETA patched, when magisk canary patches the complete stock AP? Or is it just patched, if extra?
It would be a good reason to let it out in these BR install instructions.
Is there a VBMETA dis check? Maybe a module for magisk?
 

starbucks2010

Senior Member
Jun 30, 2010
3,354
2,242
Is the VBMETA patched, when magisk canary patches the complete stock AP? Or is it just patched, if extra?
It would be a good reason to let it out in these BR install instructions.
Is there a VBMETA dis check? Maybe a module for magisk?
all the patched files in the AP file changes their extension from .lz4 to img
 
  • Like
Reactions: XtR-Z

kugla13

Member
Jan 1, 2012
34
4
In Beyondrom 9.4 and 95 and 9.6 the SmartView application works but in Beyondrom 9.7 it does not. I also tried clean and dirty flash but it doesn't work. Can you help me?
 
Last edited:

Wreak0Havoc

Member
Jun 24, 2018
14
1
Need help!
phone screen turn on only when always on display is enabled, if not it will show a black screen on phone.
I tried to use Scrcpy to view my screen throw adb to my pc and the screen is on and functional on scrcpy, but not on the actual phone until I enable aod.

1-i tried a clean install of the rom with and without root with complete wipe of everything on the phone.
2- turned off and on all sensors but nothing is fixed
3- turned Accidental touches on and off nothing is fixed

is this a hardware issue?
if yes, how the screen turns on when aod is enabled

other issues even if aod is enabled:

1- while in a phone call if the screen goes black it will never turn back on until the call is ended and the aod is back on then I can turn on the display

2- if I used the proximity sensor to listen to any voice notes and the screen goes black, same with the call problem

in a nutshell need to lock the phone after the screen goes black and wait till the aod shows up to turn on the screen again
 

NEO_CZ

New member
Jul 28, 2014
4
2
Turnov
Need help!
phone screen turn on only when always on display is enabled, if not it will show a black screen on phone.
I tried to use Scrcpy to view my screen throw adb to my pc and the screen is on and functional on scrcpy, but not on the actual phone until I enable aod.

1-i tried a clean install of the rom with and without root with complete wipe of everything on the phone.
2- turned off and on all sensors but nothing is fixed
3- turned Accidental touches on and off nothing is fixed

is this a hardware issue?
if yes, how the screen turns on when aod is enabled

other issues even if aod is enabled:

1- while in a phone call if the screen goes black it will never turn back on until the call is ended and the aod is back on then I can turn on the display

2- if I used the proximity sensor to listen to any voice notes and the screen goes black, same with the call problem

in a nutshell need to lock the phone after the screen goes black and wait till the aod shows up to turn on the screen again
I had this exact same issue when I broke by screen. Half of the amoled screen was white and as it drew too much current it couldn't be turned on from blank state. Only from the always on state. This my case this was a hardware issue. I'm assuming your screen isn't cracked but it could be some bad IC. Try flashing original FW, if persist then replace your screen.
 
  • Like
Reactions: Wreak0Havoc

Wreak0Havoc

Member
Jun 24, 2018
14
1
I had this exact same issue when I broke by screen. Half of the amoled screen was white and as it drew too much current it couldn't be turned on from blank state. Only from the always on state. This my case this was a hardware issue. I'm assuming your screen isn't cracked but it could be some bad IC. Try flashing original FW, if persist then replace your screen.
Indeed mine has a small crack
thanks for the feedback!
 

pep086

Senior Member
Nov 28, 2012
121
23
Hi guys how are you? after following the guide i have a problem with my s10, when flashing on odin 3.14.4 the AP, patched with recovery and magisk, flashing is stuck on recovery.img, i'm on w11 64bits, could it be the windows? tried different usb ports all the same results
i could flash the stock firmware, but i have no root or recovery, is there any other way to flash twrp and magisk via twrp?
thank you,
regards.
 

nicodep

Member
Mar 2, 2006
7
1
Hello, I must have forgotten a step to update dirty to version 9.7 !!
1. Install latest version of Magisk alpha 556da8a.apk
2. With Magisk, patch from twrp-3.7.0_9-2-beyond2lte.img
3. Reboot recovery and flash twrp img file patched
4. Reboot revovery and flash BeyondRom 9.7
5. Reboot recovery, everything works but the basic version is still G975FXXUGHVJ1 and not HWC1!
What should I do ?

THANKS
 

Strifelolz

Senior Member
Hi guys how are you? after following the guide i have a problem with my s10, when flashing on odin 3.14.4 the AP, patched with recovery and magisk, flashing is stuck on recovery.img, i'm on w11 64bits, could it be the windows? tried different usb ports all the same results
i could flash the stock firmware, but i have no root or recovery, is there any other way to flash twrp and magisk via twrp?
thank you,
regards.
Filename inside the .tar must explicitly be "recovery.img" for the recovery partition.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Is anyone able to talk to me please I am stuck and need help. I don't know where to ask.
    Or is it wrong to ask for guidance? If so tell me why it is wrong to ask for guidance. I follow the instructions which are not very clear where to get the right files from. I tried to patch twrp with magisk but it just fails saying wrong file. I tried the file I downloaded twrp-3.7.0_9-2-beyond0lte.img.tar and the extracted recovery.img both say wrong file?
    what this all about ?
    The first step is to download the TWRP image latest ( image not tar )
    Connect your phone to the PC and transfer the recovery image file to the phone’s storage
    Next, download the latest Magisk Manager APK and install it on your Galaxy S10 device
    Once installed, go to the app drawer and launch the ‘Magisk Manager’ application
    Tap on the ‘Install’ button
    Next, tap on ‘Install’ and select the ‘Select and Patch a File’ option
    Navigate to the phone’s storage and select the TWRP recovery image file
    Magisk Manager will now patch the file with the latest version of Magisk
    Once done, the magisk_patched.img (patched TWRP image) file will be available in ‘[internal storage]/Download/’ folder of your phone

    Step 2: Rename and Compress Patched TWRP Image as tar

    At this point, the patched TWRP image is available as a “.img” file. In order to flash it to your Galaxy S10 using Odin, it must be renamed and properly compressed in the “.tar” file format. Simply changing the file’s format from “.img” to “.tar” isn’t going to cut it. This has to be done in a proper way, through the instructions below
    First of all, transfer the patched TWRP image (magisk_patched.img) file from your phone’s storage to the PC
    Open the folder where the file was transferred
    Hold the SHIFT key on the keyboard and right-click on any empty space inside the folder
    Then select the ‘Open PowerShell window here’ option
    Now, enter the following command to rename the ‘magisk_patched.img’ to ‘recovery.img’:

    mv magisk_patched.img recovery.img


    Use the following command to compress the renamed ‘recovery.img’ as tar, according to the device you’re using

    Galaxy S10:
    tar cf twrp-beyond1lte.img.tar recovery.img
    Galaxy S10+
    tar cf twrp-beyond2lte.img.tar recovery.img

    Once the patched TWRP image has been successfully renamed and compressed, it should be ready to flash on your device
    1
    Hey @starbucks2010, thanks for all of your work, I really like your rom. Is there any plans on updating it to Ivan's OneUI 5.1 in the future?
  • 105
    logo (3).png

    BeyondRom V9.7




    Based on Android 12 - G97xFXXSGHWC1


    Devices Supported: G970F(D), G973F(D), G975F(D)






    ROM Features

    <*>Aroma choices: full/dirty wipe, debloat, Bixby key remapping, Emoji</*>
    <*>Supports G970F(D), G973F(D) and G975F(D)</*>
    <*>Base Android 12 G975FXXSGHWC1 odex/deodex Mar 2023 patch level</*>
    <*>Stock Samsung kernel</*>
    <*>CSC features (camera sound menu, call recording, camera during call, etc)</*>
    <*>Knox partially removed, AppLock,</*>
    <*>Included the security bypass from Ian’s multidisabler</*>
    <*>build.prop tweaks: call ring delay, BT passwords remember</*>
    <*>Allow screenshots in secure apps</*>
    <*>Reboot directly in rooted system from power menu (modded services)</*>
    <*>Possibility to choose in aroma to remove the boot warning</*>
    <*>Modded IncallUI with app (add Phone tile - long press for settings)</*>
    <*>Latest patched twrp included in the rom zip</*>


    Changelog v9.7

    <*>Updated to the latest HWC1 OneUI 4.1 FW Mar 2023</*>
    <*>Switched back to magisk canary - remove your actual magisk app and install magisk canary</*>

    Credits

    - John Wu for Magisk
    - IanMacd for multidisabler
    - IanMacd and Oleg for the libbluetooth fix
    - Corsicanu for the TWRP
    - Mr. Waehere for CRB kitchen
    - WinB33 for the FontPack
    - aliwaris for incallui mod
    - adil192 for some shealth mods
    - dutchman89 for the awesome beyond boot animation
    - All people who helped me with ROM testing (Claude, Bananaman and others)

    Download Links for G970F(D)/G973F(D)/G975F(D)

    BR9.7 HWC1 Link
    Digi Link


    ALWAYS CHOOSE REBOOT TO RECOVERY AFTER FLASHING BR ROM OR WHEN REBOOTING FROM TWRP !

    Dirty flash BR 9.7 over BR 9.6 is possible. You must be on at list HVJ5 FW to boot BR9.7 !!!

    Installation procedure

    1. You need to be already on Android 12 fw before attempting to flash BR 9.x
    2. Flash latest TWRP (3.7.0_9-1 or newer patched with Magisk Canary or Alpha, not stable Magisk) in Odin (AP slot), reboot the phone in TWRP using combo keys and the USB cable connected to phone and PC
    3. Wipe your data in TWRP (type YES when asked), flash Ian’s latest multidisabler (v3.1 or newer) to disable the encryption at the next reboot then flash BR 9.x


    In any of the above cases, MAKE SURE THAT YOUR DATA PARTITION IS NOT ENCRYPTED!!!

    If your /data partition is encrypted, flash Ian’s latest multidisabler (v3.1 or newer) and format your data in TWRP after flashing the multidisabler (Wipe data, reply YES when asked in TWRP). Beware that your ENTIRE internal SD will be wiped.
    After the first boot, when you start Magisk Manager for the first time, reply with YES (agree to reboot) after MM have setup your root environment. Toggle ON the magisk hide toggle in magisk manager.

    You can experiment also flashing full stock HWA3 fw + patched twrp+vbmeta with Odin using HOME_CSC to keep your data then reboot immediately in twrp and dirty flash directly BR9.x. It could work but no guarantee.


    Advises

    0. DON'T START FLASHING BRx WITHOUT A FULL TWRP BACKUP !!! Backup to PC your important files: documents, pics, contacts, SMS, etc.
    1. Is advisable to clean flash if coming from A11. You can try to restore your previous saved data with TWRP but you can experience problems
    2. If you have error 1 while flashing the ROM - usually bad ROM zip download; wipe cache + dalvik and try to flash the ROM again
    3. If you like my work, consider buying me a coffee (PayPal link)

    Helpful links

    Telegram chat
    PayPal link


    Happy flashing good people! :)
    29
    BR 6.9 updated to Aug 2020 patch level in OP.


    Happy flashing good people! :)
    9
    the rom is updated to march fw ... enjoy!
    8
    Added S10e support. Link in OP.
    8
    BR has been updated to latest dec 2021 fw. Enjoy !