Development [MAGISK Rom /Base Convertor] 420rom F926B V2.2 - BVA9 - ANDROID 12 - OneUI 4.0 - Sec Patch 01/2022 - Released 28/01/2022

Search This thread

白い熊

Senior Member
Aug 29, 2011
827
286
相撲道
Truly great, @exocetdj

Installed it and it’s nice — I was excited to see Viper in the list of options as I couldn’t get it to function on stock rooted before trying out your ROM.

Anyhow seems Viper is also not working here — gives me an “Abnormal” state. Any ideas? Did you get it to work?
 
  • Love
Reactions: exocetdj

exocetdj

Senior Member
Dec 2, 2011
6,896
4,411
Jah's making me crazy
Truly great, @exocetdj

Installed it and it’s nice — I was excited to see Viper in the list of options as I couldn’t get it to function on stock rooted before trying out your ROM.

Anyhow seems Viper is also not working here — gives me an “Abnormal” state. Any ideas? Did you get it to work?
thanks for the kind words man - only been doing this just over a year!! :)

steps to get V4a working and apologies i didn't include these (do these as soon as you have rebooted after last part of rom flash. . .

1 when rom module is installed, activate the Audio Modification Library module in Magisk and reboot (this is installed automatically by the third zip for you - just needs activating)

2 when rebooted - load up V4a and let it install drivers and reboot

3 when rebooted - disable the AML module and reboot

4 when rebooted - load up V4a and let it install drivers and reboot - v4a should now be working ok (be sure to check legacy mode!!)
 
Last edited:

exocetdj

Senior Member
Dec 2, 2011
6,896
4,411
Jah's making me crazy
AUI4 firmware has been released on WWE - OXM in Mexico - ill release a rebased later

Also thanks to @chrisaw - we will have lean kernel as an install option going forward - this will be chosen in the Master Module flash and the kernel will be built into the Base convertor by the Master Module script depending if the option is chosen

The base convertor will then flash the kernel as part of it's installation in TWRP
 
  • Like
Reactions: Acoustichayes

白い熊

Senior Member
Aug 29, 2011
827
286
相撲道
@exocetdj I’ve gotten into a slight bind, reconfigured the installed options via Magisk install, then after reflashing in TWRP and then in Magisk and rebooting:

— The Magisk with your module is 23000, the current version available is 23001, so it asks you to update in Magisk.
— Done this, then after a reboot — Viper’s disappeared, so tried to reflash the Rom module in Magisk

However it told me something, I think your message is along the lines: “you’ve been poking around in my zips...” Lol. :O)

So then tried to reflash the master module then reinstall a new ROM module but it’s somehow in a circle, doesn’t install Viper...

So then deleting the magisk module in TWRP I see there was nothing — only an AML folder, no 420 folder...

However the sdcard root 420rom folder I couldn’t delete once phone booted, looked like it was locked, so deleted in TWRP.

My question is — why would it be blocked and not delete? Do you save some control files elsewhere — so I can delete them to start with a clean state and try to install your ROM.

What about the Magisk update to 23001 then? Just leave it be — because it’ll mess it up?

However I did it before with your ROM — before I had to reflash the phone for other reasons — and I didn’t seem to have these issues.

Any ideas? Many thanks.
 

exocetdj

Senior Member
Dec 2, 2011
6,896
4,411
Jah's making me crazy
@exocetdj I’ve gotten into a slight bind, reconfigured the installed options via Magisk install, then after reflashing in TWRP and then in Magisk and rebooting:

— The Magisk with your module is 23000, the current version available is 23001, so it asks you to update in Magisk.
— Done this, then after a reboot — Viper’s disappeared, so tried to reflash the Rom module in Magisk

However it told me something, I think your message is along the lines: “you’ve been poking around in my zips...” Lol. :O)

So then tried to reflash the master module then reinstall a new ROM module but it’s somehow in a circle, doesn’t install Viper...

So then deleting the magisk module in TWRP I see there was nothing — only an AML folder, no 420 folder...

However the sdcard root 420rom folder I couldn’t delete once phone booted, looked like it was locked, so deleted in TWRP.

My question is — why would it be blocked and not delete? Do you save some control files elsewhere — so I can delete them to start with a clean state and try to install your ROM.

What about the Magisk update to 23001 then? Just leave it be — because it’ll mess it up?

However I did it before with your ROM — before I had to reflash the phone for other reasons — and I didn’t seem to have these issues.

Any ideas? Many thanks.
Have you updated to AUI4? I have not completed the new rom yet so there will be issues flashing v1 over AUI4 as that's based on AUHF.

Also can you send me an install log showing that message?
 

exocetdj

Senior Member
Dec 2, 2011
6,896
4,411
Jah's making me crazy
@exocetdj I’ve gotten into a slight bind, reconfigured the installed options via Magisk install, then after reflashing in TWRP and then in Magisk and rebooting:

— The Magisk with your module is 23000, the current version available is 23001, so it asks you to update in Magisk.
— Done this, then after a reboot — Viper’s disappeared, so tried to reflash the Rom module in Magisk

However it told me something, I think your message is along the lines: “you’ve been poking around in my zips...” Lol. :O)

So then tried to reflash the master module then reinstall a new ROM module but it’s somehow in a circle, doesn’t install Viper...

So then deleting the magisk module in TWRP I see there was nothing — only an AML folder, no 420 folder...

However the sdcard root 420rom folder I couldn’t delete once phone booted, looked like it was locked, so deleted in TWRP.

My question is — why would it be blocked and not delete? Do you save some control files elsewhere — so I can delete them to start with a clean state and try to install your ROM.

What about the Magisk update to 23001 then? Just leave it be — because it’ll mess it up?

However I did it before with your ROM — before I had to reflash the phone for other reasons — and I didn’t seem to have these issues.

Any ideas? Many thanks.
ok - ignore my last message

The zip you flash in TWRP (the second zip to flash which is created on Master Module flash if it's required) is the firmware modification part (what magisk cant do basically) and also places a marker on the system that is picked up by the final zip on install.

its not detecting that in your case,

Solution:

1 remove all traces of any 420rom modules

2 manually delete the entire 420rom folder in internal storage

3 follow the usual install instructions :)

I am still to release files for AUI4 so am assuming you are still on AUHF firmware? Please don't try to install V1 on AUI4 as the SystemUI will be incompatible and cause booting issues into safe mode or sluggish performance (dumb dumb here restored a TWRP backup with AUHF v1 over AUI4 firmware accidentally :ROFLMAO: :ROFLMAO: :ROFLMAO: :ROFLMAO: :ROFLMAO:
 
  • Like
Reactions: 白い熊

白い熊

Senior Member
Aug 29, 2011
827
286
相撲道
Yeah, I’m on AUHF — I’ve done the full remove of the modules and the directory in the meantime, about to reflash now.

How about that Magisk upgrade once flashed? Should I just leave it at 23000, any thoughts on that?
 

白い熊

Senior Member
Aug 29, 2011
827
286
相撲道
Oh yeah — do you remove Bixby as part of the debloat? It seems to me you did...

The reason is that I remap the power button long press to toggle a super reboot app — and the only way to remap it that I’ve found is via this app called sideActions — which relies on Bixby and somehow replaces the call to it while it’s running or whatever...
 

白い熊

Senior Member
Aug 29, 2011
827
286
相撲道
OK — now it’s problematic:

— removed all 420 traces in /data/adb/modules
— removed the 420rom sdcard folder
— ran standard install

Now when I restarin TWRP to flash the Mod module — it tells me:
— Only uninstall is supported in recovery
Uninstalling!
— Unmounting partitions

So it keeps uninstalling, but won’t install.
 

exocetdj

Senior Member
Dec 2, 2011
6,896
4,411
Jah's making me crazy
OK — now it’s problematic:

— removed all 420 traces in /data/adb/modules
— removed the 420rom sdcard folder
— ran standard install

Now when I restarin TWRP to flash the Mod module — it tells me:
— Only uninstall is supported in recovery
Uninstalling!
— Unmounting partitions

So it keeps uninstalling, but won’t install.
do you want to head over to the telegrsm chat matey?? will sort u easier there. sounds like your flash has gone a bit funny

we can also identify any improvements are needed - can make bixby removal optional for example :cowboy:
 
  • Like
Reactions: 白い熊

白い熊

Senior Member
Aug 29, 2011
827
286
相撲道
OK - I'm finishing some other coding work now - so I'll see you there later. If not today, I'll catch you tomorrow.
 

exocetdj

Senior Member
Dec 2, 2011
6,896
4,411
Jah's making me crazy
Good afternoon all - i am happy to announce v1.1 (beta 5) is now live in the first post.

simple changelog:

v1.1-b5

- added option to either keep or kill Bixby - this is done at the system level and if you nuke Bixby and subsequently decide you want it back, you will need to restore a backup or flash the stock rooted odin files.
- added magisk 23001
- all Goodlock apps updated
- TWRP a37 packaged in convertor
- Rebased to AUI4 firmware

IMPORTANT - ALTHOUGH A BACKUP OF DATA IS ALWAYS RECOMMENDED - THE NEW AUI4 ODIN FILES WILL NOT WIPE DATA

PLEASE SEE MY ROOTING THREAD FOR FLASHING INSTRUCTIONS AND THE ODIN FILES HERE (WHICH CAN ALSO BE FOUND IN THE FIRST POST)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 13
    logo.png




    WELCOME TO 420 ROM - MAGISK ROM FOR SAMSUNG GALAXY Z FOLD 3 5G F926B (SD888)

    Telegram-Group


    Please bear in mind that things will be added as and when my learning and time permits (being a dad with a family and having ADHD myself means things get a lil gnarly) but i will aim to support this ROM as regularly as possible.

    Ill usually release a test to one or two users before each release also - :cyclops:


    CUSTOMIZABLE ONEUI EDITION MAGISK ROM FEATURES: - with Vol +/- keys

    -Add YouTube Vanced - thanks to Vanced peeps github
    -Add 3minit battery - thanks G Harrington - if online menus don't appear, install the apk that the module places on your internal storage in the 420rom folder.
    -Add 3minit clock - thanks G Harrinton
    -Add V4A
    -Add custom 420rom bootanimation thanks to @chalmizzle
    -Add SamsungSans fonts apk
    -Add Goodlock
    -Add SoundAssistant (for increased vol steps)
    -Add Customized Secsettings
    -Add Custom wallpapers (new for A12)
    -Add custom power app with several reboot options
    -Add CTS fix
    -Remove Chrome

    CORE MAGISK ROM FEATURES

    -Detects OMC code and ensures correct OMC folders and files installed
    -detects base rom or rooted stock and presents relevant install features and aborts if attempted to be installed on anything else - should help keep non compatible setups intact :)
    -Device detection to prevent flashing on other devices

    Enabled the following CSC fetures: (thanks @m8980

    - Disable shutter sound menu
    - Support RealTime Network Speed in status bar - working
    - Enable Camera during call
    - Enabled call recording
    - Data usage in quick panel - the feature displays but not the actual data used - if anyone knows a fix, let me know :)

    GOOGLE EDITION FEATURES (FURTHER TO THOSE IN ONEUI EDITION MODULE ABOVE) (coming soon!!!)

    This Module is based on the main Main 420rom Rom Module but replaces some of the Samsung apps with Google ones. It is recommended to backup your Samsung apps 1st!!!

    Installed with Module - Samsung App it replaces
    --------------------------------------
    Google Phone - Samsung Phone
    Google Contacts - Samsung Contacts
    Google Messages - Samsung Messenger
    Google Chrome - Samsung Internet Browser
    Google Calculator - Samsung Calculator
    Google Calendar - Samsung Calendar
    Google Clock - Samsung Clock
    Google Drive - Samsung Cloud (stays installed)
    Google Files - Samsung MyFiles
    Google Fit - Samsung Health (can be reinstalled from Galaxy Apps)
    Google Pay - Samsung Pay
    Google Keep Notes - Samsung Notes
    Google Photos - Samsung Gallery
    Google Recorder - Samsung Recorder
    Google TTS - Samsung TTS
    Google Duo - n/a
    Google News - n/a
    Google Tasks - n/a
    Google Sounds (Sound Picker) - n/a
    Google Apo - n/a
    Google Carrier Services (for RCS) - n/a
    GBoard - Samsung Keyboard
    GMail - Samsung Email
    YouTube Music - Samsung Music
    YouTube Vanced, Vanced Manager & Vanced MicroG - YouTube
    Nova Launcher - OneUI Launcher

    RECOVERY FLASHABLE BASE CONVERTOR FEATURES

    -Does away with warning on splash
    -Debloats a fair whack but not too much
    -rooted with magisk manager
    -flashes latest TWRP during Base flash
    -mines stock files from phone for use in rom flash :)

    Changelog

    v2.2

    - Rebased to BVA9 firmware - 1 Jan 2022 sec patch (EUY)
    - TWRP updated to A8
    - Magisk updated to V24001 (v24 public release)

    v2.1

    - Rebased to BUL8 firmware - 1 Jan 2022 sec patch
    - convertor no longer debloats klmsagent so Samsung health works if version 6.19.5.017 is installed - thanks @dr.ketan and @starbucks2010 for the info
    - added 420rom folder reset zip - this is sent to sdcard and is to be used only when your rom install choices arent being actioned or if old features selected are still being unintentionally installed
    - roboto-thin.ttf added to firmware to stop 3minit clock fc - thanks @dr.ketan

    v2.0.1

    - simple bugfix for those that wish to keep bixby - no need to flash unless you use bixby or have ORD (obsessive romming disorder)

    v2.0

    - rebased on BUL6 OneUI 4 - Android 12 firmware
    - updated magisk
    - updated goodlock apps
    - added new bootanimation
    - added new TWRP to convertor
    - added new wallpapers
    - added wallpapers to dex
    - removed encryption from firmware
    - updated safteynet v2.2.1 fix added
    - updated bluetooth lib patcher added

    v1.1-b5

    - added option to either keep or kill Bixby - this is done at the system level and if you nuke Bixby and want it back, you will need to restore a backup or flash the stock rooted odin files.
    - added magisk 23001
    - all Goodlock apps updated
    - Rebased to AUI4 firmware

    V1-b2
    - initial xda release

    what's next? & Known Bugs we can't do much about or will sort eventually

    - 420rom folder in internal storage needs deleting between every fresh rom flash - this wont matter until you need to select different rom choices - just delete this folder from internal using TWRP file manager

    - you may get the odd systemUI FC in dex


    -if A SYSTEM APP hasn't been removed, try uninstalling it ;) you should now be able to - any updates installed over an original system app remain as they are data apps following an update

    CORE DEV TEAM

    Myself - team owner and Rom Module chef
    @abun880007 - team co-conspirator


    Huge thanks to.................
    @abun880007 for the legendary support and collab
    @Zackptg5 for the brilliant MMT Extended zip
    Rooted with Magisk - thanks @topjohnwu
    @topjohnwu for magisk
    @Winb33) for the samsungsans7.2 fonts
    @superr for the kitchen
    @starbucks2010 for the csc features inspiration
    @Team_DeWitt for the Awesome V4A 2.7 - a must have for audiophiles!!
    G Harrington for the 3minit apps
    Team Vanced for bringing us all youtube Vanced
    @dr.ketan for the various pointers and sage advice :)
    Finally, @m8980, thanks for letting me adapt your CSC features into my module. :good::good::good:

    DOWNLOADS

    420rom website

    XDA:DevDB Information
    [MAGISK Rom & Base], ROM for the Samsung Galaxy Z Fold 3
    6
    Good afternoon all - i am happy to announce v1.1 (beta 5) is now live in the first post.

    simple changelog:

    v1.1-b5

    - added option to either keep or kill Bixby - this is done at the system level and if you nuke Bixby and subsequently decide you want it back, you will need to restore a backup or flash the stock rooted odin files.
    - added magisk 23001
    - all Goodlock apps updated
    - TWRP a37 packaged in convertor
    - Rebased to AUI4 firmware

    IMPORTANT - ALTHOUGH A BACKUP OF DATA IS ALWAYS RECOMMENDED - THE NEW AUI4 ODIN FILES WILL NOT WIPE DATA

    PLEASE SEE MY ROOTING THREAD FOR FLASHING INSTRUCTIONS AND THE ODIN FILES HERE (WHICH CAN ALSO BE FOUND IN THE FIRST POST)
    4
    You're absolutely shure to root your phone, if you're not able to open a 7z file? Good luck ...
    3
    INSTALL PROCEDURE

    FIRSTLY ROOT YOUR DEVICE BY FOLLOWING THIS GUIDE

    1 - FLASH "MASTER MODULE" IN MAGISK AND ENTER INSTALL CHOICES WHEN PROMPTED

    2 - CHECK INTERNAL STORAGE/420ROM FOLDER FOR THE "BASE CONVERTOR" - REBOOT TO TWRP AND FLASH THIS FILE

    3 - THIS FILE WILL DEBLOAT, PERFORM SOME OTHER UNDER THE HOOD MODIFICATIONS AND MINES SYSTEM FILES WHICH THE FINAL ZIP WILL AUTOMATICALLY MODIFY MID-FLASH

    4 - REBOOT TO SYSTEM AND CHECK THE SAME FOLDER AS IN STEP 2 - FLASH THIS "ROM MODULE" IN MAGISK - ALL THE INSTALL OPTIONS YOU MADE IN STEP 1 WILL BE AUTOMATICALLY DETECTED AND ACTIONED IN THIS FLASH.

    5 - REBOOT TO ACTIVATE ROM MODULE AND ENJOY!!
    3
    Ok so i am preparing for release of my rom everything apart from Applock is working - there may also be a systemUI close on dex but we are looking into that

    we have root
    camera works
    and also TWRP now

    Please refer here for the new rooted firmware and process below: - this should be the last time formatting is needed now as going forward we will always have TWRP installed. (if stock remember the step about activating and checking oem unlock in dev settings before you start

    Coming from stock a11/a12 or rooted a11 or even rooted a12 lol

    1 - reboot to download mode

    2 - Load BL_BUL6, AP_F926B_BUL6_exo.tar, CP and HOMECSC into respective odin slots and flash

    3 - when flashed, reboot to TWRP and format device, reboot TWRP and disable MTP under the mount menu

    4 - "adb push Magisk.zip /sdcard" - copy magisk.zip (attached below) to adb folder and send to internal storage using that command in CMD window - flash the magisk.zip

    5 - reboot to system from TWRP menu

    You will then be in a rooted state with fully working TWRP ready to accept the incoming rom :)