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

[ltth]

Thanks mate

Yep unfortunately this will break know so Samsung pay won't work. AFAIK secure folder is now from a11 onwards (unless I have mixed that up with something else lol)

Ok thanks, I use G-Pays so no problem for me.

 

[ltth]

Thanks mate

Yep unfortunately this will break know so Samsung pay won't work. AFAIK secure folder is now from a11 onwards (unless I have mixed that up with something else lol)

Ok, thanks!

 

[jemfalor]

any mods for the modem?? need the bands to be completely unlocked for 5g, nr1 especially

 

[白い熊]

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?

 

[exocetdj]

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!!)

 

[exocetdj]

any mods for the modem?? need the bands to be completely unlocked for 5g, nr1 especially

not as yet mate - hoping to really add to this rom proper when cam fix is out - i have only ported direct from N20U rom for now

 

[exocetdj]

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

 

[白い熊]

@exocetdj a little side finding — not that it bothers me immensely, the boot image replacement doesn’t work, nothing gets replaced.

 

[exocetdj]

@exocetdj a little side finding — not that it bothers me immensely, the boot image replacement doesn’t work, nothing gets replaced.

yep thats been made aware to me

i will aim to fix for next release to get boot animation re-added

 

[白い熊]

@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]

@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]

@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

 

[白い熊]

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?

 

[白い熊]

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...

 

[白い熊]

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]

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

 

[白い熊]

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]

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)

 

[beanbean50]

This rom looks so good wish I choose the fold now!

 

[exocetdj]

This rom looks so good wish I choose the fold now!

It works ok man - shame camera is still buggered on BL unlock without sign of a fix yet tho

had to return to stock as need my camera for a UK based cannabis club meet up tomorrow lol