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

Search This thread

starbucks2010

Senior Member
Jun 30, 2010
3,354
2,242
OXM is a group of csc from a certain region. It means that it doesn't matter which csc fw you dl, the result will be the same for all the csc from oxm group. 1 fw for more csc in short. XEF is part of oxm group.
 
  • Like
Reactions: [Legenda]

[Legenda]

Senior Member
Dec 27, 2012
312
34
OXM is a group of csc from a certain region. It means that it doesn't matter which csc fw you dl, the result will be the same for all the csc from oxm group. 1 fw for more csc in short. XEF is part of oxm group.
Thanks.

But I install Lineage recovery to have a rom for tomorrow. But I can't even install lineage.

And I don't know how move back to twrp. Because I can't use Odin as well... it doesn't detect my phone on recovery.
 

slitbrain

Member
Feb 6, 2012
34
17
Thanks.

But I install Lineage recovery to have a rom for tomorrow. But I can't even install lineage.

And I don't know how move back to twrp. Because I can't use Odin as well... it doesn't detect my phone on recovery.
You have to get to download mode for the flashing in Odin (phone off - >bixby + vol down->connect the USB c cable which is already connected to the computer), then you can flash twrp (.tar) over the AP slot. Be fast and push vol up + bixby at the reboot to just get into twrp. 👌
 
  • Like
Reactions: [Legenda]

[Legenda]

Senior Member
Dec 27, 2012
312
34
You have to get to download mode for the flashing in Odin (phone off - >bixby + vol down->connect the USB c cable which is already connected to the computer), then you can flash twrp (.tar) over the AP slot. Be fast and push vol up + bixby at the reboot to just get into twrp. 👌
Yeah ! Thanks a lot. That was the missing point : go to download mode.
Thanks mate. 👍👍
 
  • Like
Reactions: slitbrain

slitbrain

Member
Feb 6, 2012
34
17
How to flash BR 9.4 without any problems (most of us know but sometimes it is just a small detail thought of as routine that's enough to fail...😭):
1. Make a full backup in Twrp and store it somewhere save. 🔑
2. Get the stock HVJ5 rom. (check for the right regional code, samfirm tool is quite helpful)
3. Flash HVJ5 in Odin (all files but home_csc)
4. Boot up, enable dev mode as well as USB debugging.
5. Go back to dl mode and flash twrp in AP slot as well as vbmeta in CP slot. (without vbmeta twrp won't boot up and you are stuck at dl mode screen)
6. Straight up to twrp. (vol+/bixby/power just like three seconds)
7. Completely reset internal SD (type yes...)
8. Flash multidisabler right after.
9. Flash BR 9.4.
10. Flash magisk apk and the corresponding patched twrp.
11. Reboot and set up magisk before logging into your accounts (Google, Samsung...), enable zygisk, flash safetynet zip, set up forced blocklist.
[12. Enable highest available swap ram in system maintenance, force reboot (vol - and power) and twrp reboot (vol+ and bixby, power until boot logo) before system reboot kicks in.]
13. Reboot to recovery, cleach cache/dalvik, reboot to recovery.
14. Be happy about the sheer poetry of a custom Rom working fine and thank starbucks2010.
15. Share your experiences with others asking for help.
🎉🎊🎈
 
Last edited:

[Legenda]

Senior Member
Dec 27, 2012
312
34
How to flash BR 9.4 without any problems (most of us know but sometimes it is just a small detail thought of as routine that's enough to fail...😭):
1. Make a full backup in Twrp and store it somewhere save. 🔑
2. Get the stock HVJ5 rom. (check for the right regional code, samfirm tool is quite helpful)
3. Flash HVJ5 in Odin (all files but home_csc)
4. Boot up, enable dev mode as well as USB debugging.
5. Go back to dl mode and flash twrp in AP slot as well as vbmeta in CP slot. (without vbmeta twrp won't boot up and you are stuck at dl mode screen)
6. Straight up to twrp. (vol+/bixby/power just like three seconds)
7. Completely reset internal SD (type yes...)
8. Flash multidisabler right after.
9. Flash magisk apk and the corresponding patched twrp.
10. Reboot and set up magisk before logging into your accounts (Google, Samsung...), enable zygisk, flash safetynet zip, set up forced blocklist.
[11. Enable highest available swap ram in system maintenance, force reboot (vol - and power) and twrp reboot (vol+ and bixby, power until boot logo) before system reboot kicks in.]
11. Reboot to recovery, cleach cache/dalvik, reboot to recovery.
12. Be happy about the sheer poetry of a custom Rom working fine and thank starbucks2010.
13. Share your experiences with others asking for help.
🎉🎊🎈
I'm here :
3- I downloaded my firmware with samfirmtool.
But after flash the latest firmware. Odin failed to install it.
Any tips? Am I that bad to follow instructions step by step ? :poop:
 

Attachments

  • Capture d’écran 2022-11-17 203455.png
    Capture d’écran 2022-11-17 203455.png
    17.8 KB · Views: 45
  • 2.png
    2.png
    54.2 KB · Views: 47

zogoibi

Senior Member
Aug 18, 2011
419
71
Hi all.
Sorry for the nooby question, but is it possible to de-googlefy and instead microGfy this ROM?
How to flash BR 9.4 without any problems (most of us know but sometimes it is just a small detail thought of as routine that's enough to fail...😭):
1. Make a full backup in Twrp and store it somewhere save. 🔑
2. Get the stock HVJ5 rom. (check for the right regional code, samfirm tool is quite helpful)
3. Flash HVJ5 in Odin (all files but home_csc)
4. Boot up, enable dev mode as well as USB debugging.
5. Go back to dl mode and flash twrp in AP slot as well as vbmeta in CP slot. (without vbmeta twrp won't boot up and you are stuck at dl mode screen)
6. Straight up to twrp. (vol+/bixby/power just like three seconds)
7. Completely reset internal SD (type yes...)
8. Flash multidisabler right after.
9. Flash magisk apk and the corresponding patched twrp.
10. Reboot and set up magisk before logging into your accounts (Google, Samsung...), enable zygisk, flash safetynet zip, set up forced blocklist.
[11. Enable highest available swap ram in system maintenance, force reboot (vol - and power) and twrp reboot (vol+ and bixby, power until boot logo) before system reboot kicks in.]
11. Reboot to recovery, cleach cache/dalvik, reboot to recovery.
12. Be happy about the sheer poetry of a custom Rom working fine and thank starbucks2010.
13. Share your experiences with others asking for help.
🎉🎊🎈
Thanks for taking the trouble to write this mini-guide, but I'm missing the step where it should say: "Flash BR9.4". When do I do that? As far as I can see (and I've read your guide thrice), there is only a step for flashing stock ROM, not Beyond ROM.
Another question: where is that safetynet zip you talk about in step 10? Do I absolutely need it?
 

slitbrain

Member
Feb 6, 2012
34
17
Hi all.
Sorry for the nooby question, but is it possible to de-googlefy and instead microGfy this ROM?

Thanks for taking the trouble to write this mini-guide, but I'm missing the step where it should say: "Flash BR9.4". When do I do that? As far as I can see (and I've read your guide thrice), there is only a step for flashing stock ROM, not Beyond ROM.
Another question: where is that safetynet zip you talk about in step 10? Do I absolutely need it?
You are absolutely right. 😂👌Sorry, I really missed the most important thing, must have been kind of busy. Thanks for the heads up. 👍
 
  • Like
Reactions: zogoibi

zogoibi

Senior Member
Aug 18, 2011
419
71
Hello @starbucks2010 and thanks for your work.
I read many of you here writing about HVJ5 FW, but I'm confused about the term firmware (FW), because it is rather polysemic. I often see it as synonims with ROM, and I never know when people write FW when they want to write ROM, and vice-versa. (To be perfectly honest, I am also not sure what exactly the "firmware" consists of in the mobile phone's world, though I'm pretty familiar with it in the computer's world.)
So, to clarify, by HVJ5 FW do you mean the full Samsung stock rom with build number G97X-etc-etc-HVJ5? Or simply the non-system bits of that (i.e. modem, bootloader, recovery, boot, whatever)? In other words: do I need to flash Samsung's latest stock ROM beofe going ahead and try to install BR9.4 as per OP's instructions, or can I simply update (I guess via Odin) the "firmware" (or some parts of it, depending on the meaning we give to "firmware")?
That much for trying to install BR9.4
Now, let's say I want to install BR9.3 (which I downloaded some weeks ago). I am presently on LOS 19.1 (which I flashed over Samsung's full stock SGHVI1 ROM). So, assuming I am already on the appropriate "firmware", can I install BR9.3 directly over LOS, or again, must I revert to Samsung's stock ROM?
Sorry for the long post, but I am always so confused about the (correct or incorrect) interchangeability of the words "ROM" and "FW", as well as by the ambiguous word "stock".
Thank you in advance.
 
Last edited:
  • Like
Reactions: [Legenda]

zogoibi

Senior Member
Aug 18, 2011
419
71
You are absolutely right. 😂👌Sorry, I really missed the most important thing, must have been kind of busy. Thanks for the heads up
Sure! Most welcome. Now it makes a lot more sense to me. 🙃
By the way, I've just written another post with a couple of questions directed at BR's developer, but perhaps you can help me with them: Do you think I can flash BR9.3 over LOS 19.1 (for which I has previously on Samsung's stock HVI1), or do I in any case need to revert to Samsung's stock for that? (The same would go for BR9.4, respectively installing Samsung's HVJ4). I assume that being on Samsung's stock is the safe way, but is it the only way? Or is it possible to skip all the hassle by simply updating the relevant parts of the firmware?
 

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 !