yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9 & S9+ Cross Device Development] bahmonkeys:
Thanks alexandr

Works very well for me. Seems very smooth haven't really had any issues at all coming from BRJ6. For me, it seems a little bit quicker especially opening and going through translational windows.

Anyone know how to auto hide the Nav Bar? There used to be a dot on the old nav bar to auto hide it.
[Samsung Galaxy S9 & S9+ Cross Device Development] mevorach:
Thanks alexndr ! Everything works ! coming from pie 5.9 r2 . dirty flash .
[Samsung Galaxy S9 & S9+ Cross Device Development] valmar:
Now a little different: settings / screen / navigation bar
[Samsung Galaxy S9 & S9+ Cross Device Development] bahmonkeys:
Thanks. I have seen the full gesture for the 3 buttons on the nav bar. The recents button does not seem to work with full gesture nav bar
[Samsung Galaxy S9 & S9+ Cross Device Development] maglise:
Pie Bootloader

Hi,

I didn't flash the new bootloader for now, and wonder if it could explain some little bugs like the ext. sdcard not functionning normally or the missing apps or service like Ledcover ?

Is it possible that by flashing the new Pie bootloader, I could have a better experience ?

Thanx for your work.

Maglise
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
Have you flashed this ROM already? I'm asking, because:

1. There is no SdCard bug starting from v6.0 (see post #49 for details)

2. DevBase ROM v6.0 flashes Pie BL by default, unless you bypassed it intentionally, but method is described in my other thread

3. Without customized options.prop there should not be missing apps and/or services - by default only Social & Microsoft apps have been removed + some not working (with KNOX 0x1) stuff like Secure Folder & Samsung Pay. All other apps & features are present and works :cool:

If I'm wrong and you flashed this ROM just with customized options.prop file - please post here /cache/devbase_install.log - I will try to help

Answering main question - I haven't found a bug definitely related to BL version in Pie yet (as I mentioned in post #50 already)
[Samsung Galaxy S9 & S9+ Cross Device Development] maglise:
Pie Bootloader

Hi, Thank you

No I didn't flash your ROM yet, I flashed Soldier's one, version 1, 2 and 3 with the same issues, and wonder if it's gonna be different regarding Sdcard and Ledcover issues I have.

That's why I was asking a question here about the bootloader, and especially the ledcover since It's useless right now, doesn't screen off when I close it, and not screen on when I open it, and of course no leds working. I can live without it but I prefered to find a solution. And I thought maybe the oreo bootloader could be the reason.

Anyway, thanx for your work and answers.

Maglise

I
[Samsung Galaxy S9 & S9+ Cross Device Development] j.Nahoy:
i got error failed to mount '/odm' (Invalid Argument) after i did clean install, format data and full wipe.

can u help me to fix it?
[Samsung Galaxy S9 & S9+ Cross Device Development] Andrw0830:
Hey [MENTION=5150393]_alexndr[/MENTION], I just installed this and thanks for releasing this for our device, I did notice a couple things I hope you can answer. I am running this on G960F and have the following issues

- I edited the options.prop file from the .zip and copied it to external_sd, but when I installed the ROM, even the Microsoft apps didn't debloat. I made sure for the Virtual Debloat section to name the apk exactly what the APK name is so don't know what's going on

- In the past since I am using the G960F on a Canada Carrier, I would copy my carriers, CSC folder into odm/omc followed by our SW_Configuration.xml file and that carriers config would show up and I could toggle VoLTE and WiFi calling, but the ROM keeps loading XEU.

- the root of the Settings app has weird menu options like 'T roaming' and 'Service Provider' options which was not present in other Pie Beta's I've tried.

I did do a clean flash before flashing so your input would be greatly appreciated. Thanks again.
[Samsung Galaxy S9 & S9+ Cross Device Development] mevorach:
Is there a change from rc1 to rc4 ?
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
A small introduction to the v6.0's principle of operation. My ROM flashes major partitions in technically same way as PC Odin does (since ages), but starting from v6.0 it applies also to /odm (otherwise, in case of Android Pie - there is a high risk of CSC related issues).

While it is not a problem when you have bought your device with unbranded OXM multi CSC package (if your original/factory CSC is contained in post #1) - the problem may start if you bought a factory branded device (if your original/factory CSC is NOT contained in post #1), because branded devices have slightly different /odm partition size. Installation of v6.0 will fail in such case (it will fail then even with PC Odin if you use HOME_CSC_*.tar.md5 file)

Solution is very simple - you need to flash ONCE original firmware containing OXM multi CSC package (using CSC_*.tar.md5 file, do not use HOME_CSC_* !!!) and you will solve partitions problem FOREVER :) (it will re-part your phone's memowy with unbranded PIT, so it will also format /data !!!)

You may think "fine, but what with RMM/OEM lock?". You just need to be agile enough and all will be fine :) When PC Odin flashing process will end - you need to let phone (auto)reboot ONCE to the stock recovery to finish all operations, but when it will (auto)reboot second time - you need to IMMEDIATELY press Download Mode keys combination, then just flash TWRP (and then you can even flash this ROM directly)

EDIT: starting from RC6 I introduced /odm block size detection - above procedure is not necessary anymore :cool: /odm is created from the scratch during install (instead of flashing odm.img) and will always match :cowboy:

Starting from Pie there is no simple way to replace /odm content (by just copying) because of complex SELinux contexts introduced by Sammy for /odm partition in Pie (different for specific content). If you want to try Pie without issues - at the moment I would suggest you to force BTU or XEU and then leave /odm content alone, until I will find a good solution for people using non-standard /odm content

NOTE: Make sure you are using v6.0 installer, NOT v5.9 !!!

RC2/RC3 contains suggestions I got in my "stable" thread, in RC4 I fixed some minor "typos" I found myself in the installer's alghoritm.

If you successfully flashed RC1 (without error messages) - there is no need to update. Updating thread to RC4 was just a prevention :)
[Samsung Galaxy S9 & S9+ Cross Device Development] MadSilence:
Hmm Okay, I cant get SIM TOOL to work. Which is required for most banking apps, AND Citrix Secure Hub wont work. A Security policy didnt allow you to Connect.. Ive tried magisk hide and package rename. It will not work =( Magisk passes safetynet BTW!

PS: Without magisk installed (non root) no apps will work. Vipps(banking) says this phone is rooted etc=)
[Samsung Galaxy S9 & S9+ Cross Device Development] j.Nahoy:
thanks for great clear instructions, i got it
[Samsung Galaxy S9 & S9+ Cross Device Development] mevorach:
netfix doesn't work. no error, just not loading . tried "netfix enabler" doesn't help .
[Samsung Galaxy S9 & S9+ Cross Device Development] Andrw0830:
Thanks I'll wait then before changing the odm. I did download the v6.0 installer. Is there any suggestion for why the options.prop debloat didn't work? Does it have to be on internal storage instead of external_sd?
[Samsung Galaxy S9 & S9+ Cross Device Development] bahmonkeys:
Do a clean wipe and reinstall the app. Btw this is a personal app, not really a system bug or installer bug that I think anyone is worried about :o

For me I haven't had any issues.
[Samsung Galaxy S9 & S9+ Cross Device Development] saxena1:
[MENTION=5150393]_alexndr[/MENTION]

Today I flash your G965FXXU2ZRKN_DevBase_v6.0.RC4 (clean installlation) rom installed & boot with massage only offical firmware can use (like as custom binary blocked massage).so I have to flash again oreo stock firmware via Odin that's ok .I tried SoLdieR9312s PIE BETA ROM v 3.0 it boot ok tried dirty flash over this same problem appear.i tried three times to try but not got success .what's wrong with me? I hope you understand this.
[Samsung Galaxy S9 & S9+ Cross Device Development] mevorach:
Did wipe and reinstall I do not think it is a personal problem I am wondering if anyone else have the same problem with this beta build ( I am sure it is not a Rom issue )
[Samsung Galaxy S9 & S9+ Cross Device Development] bahmonkeys:
Run safety net and see if it's passing. As read above that this Rom passes the safety net for banking apps.
[Samsung Galaxy S9 & S9+ Cross Device Development] mevorach:
Passes both of them ! still Netflix not loading !
[Samsung Galaxy S9 & S9+ Cross Device Development] mevorach:
OK the lib\liboemcrypto.so was under vendor folder and not under system
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
RC5 released :cool: fixed saving devbase_install.log in case of installation aborts with an error

There is no need to update if you flashed any previous v6.0.RCx already and installation passed without an error message

Strange, no idea, for me built-in Sim Toolkit works, my banking app also works without issues

Seems like you are locked with Pie bootloader (my ROM flashes it by default).

As far as I know - ROM you are talking about does not contain bootloader on-board (it need to be flashed separately), so if you flashed it directly after stock Oreo - you tried Pie ROM with Oreo BL.

You can do 2 experiments:

1. When you are on other ROM - update bootloader to Pie (you can find it in my repository) and check what will happen.

2. When you flash my ROM and you will see "only official binaries allowed" - try to flash only Oreo BL from official firmware using PC Odin, instead of full stock firmware, and check what will happen.

Please let me know if possible. Results will let me know if there is something to fix or not

I do not use Netflix at all, but just downloaded from Play Store and it loads (I mean setup wizard starts and offers me services)

Please try RC5 but please force BTU CSC to make sure that new /odm content will be flashed. With custom options.prop installer works as intended, the problem is with SELinux contexts of modified files (if these files not came from original Pie /odm).

In case of further problems please post here devbase_install.log (in /data or /cache, depending on data encryption)
[Samsung Galaxy S9 & S9+ Cross Device Development] zidane02:
Hi Sir [MENTION=5150393]_alexndr[/MENTION], I have dirty flashed from ZRKA to ZRKN and after boot, I got black screen only and notification bar keeps on appearing and disappearing.. Until it auto reboots to TWRP. What could be my problem?

EDIT: I reflashed BRJ8 but without booting I forced reboot to TWRP and dirty flashed ZRKN. It booted properly lol, what is happening? Meaning you can't dirty flash over to older pie? But the thing is, I lost all my settings including home screen, i lost all folders on app drawer. Good thing I still have my apps installed and don't have to reinstall each again.

EDIT 2: Plus this is smoother than ZRKA. Thanks so much..

EDIT 3: I think my GPS is not working, could it be a bug? or only mine? can anyone check theirs if is working for you? Thank you.

EDIT 4: Lol, I just needed to manually allow permission to google play services. Why it is not asking me? It is already fixed now, but is somehow slow to recognize my location. Maybe I needed to clean flash this ROM. T_T
[Samsung Galaxy S9 & S9+ Cross Device Development] saxena1:
Seems like you are locked with Pie bootloader (my ROM flashes it by default).

As far as I know - ROM you are talking about does not contain bootloader on-board (it need to be flashed separately), so if you flashed it directly after stock Oreo - you tried Pie ROM with Oreo BL.

You can do 2 experiments:

1. When you are on other ROM - update bootloader to Pie (you can find it in my repository) and check what will happen.

2. When you flash my ROM and you will see "only official binaries allowed" - try to flash only Oreo BL from official firmware using PC Odin, instead of full stock firmware, and check what will happen.

Please let me know if possible. Results will let me know if there is something to fix or not

1st opinion is not working create same problem

2nd opinion works prefect. Thanks :D
[Samsung Galaxy S9 & S9+ Cross Device Development] Spl4tt:
Hmm, Anybody else noticing much slower screenlock and unlock / screen off and screen on?

It's incredibly annoying waiting almost a second after you press the powerbutton to turn the screen on/off. Samsung devices tend to be slow with this, but now it's really really bad.
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
Thread has been updated :cool: (v6.0.RC6)

- Major changes for people with factory branded device, who never flashed OXM ROM to re-part phone's memory (problem described in post #61 has been definitely solved, post #61 has been edited)

- Some minor bugfixes/improvements in the installer's alghoritm

For me - this version seems to be very close to final v6.0 :cowboy:

NOTE:

There is no need to update for those who installed a previous RCx and it has been installed & works without issues

You can try clean install if possible, but if you decide clean install - please use RC6, because if something will go wrong - I will get more information about issues from /data/devbase_install.log

I tested "encrypt" only having Pie already - mentioned it in post #27 (haven't tested from Oreo, encrypted already)

Since dirty flash over Oreo works - in theory it "should" work also with encryption :o

Screen on - immediately

Screen off - about 0,5s here...

Not much annoying for me (let's see next Sammy's beta)
[Samsung Galaxy S9 & S9+ Cross Device Development] Spl4tt:
Hmm. It's a really big delay for me. Not sure what's the cause. Screen on takes as long as screen off. And screen off takes so long, I can even press something on the screen before it turns off.

Definitely far worse than it was on Oreo

I'll wait for the next few builds then, and will do another clean flash. It's currently not my main phone, so no big deal
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
Yes, default behavior of AOD has changed in Pie - you need to set "display mode" -> "always display" in it's advanced settings
[Samsung Galaxy S9 & S9+ Cross Device Development] SilentWorld:
Hi, could you help me? I need the system files of the beta so I can make roms for devices that will not get pie
[Samsung Galaxy S9 & S9+ Cross Device Development] zidane02:
Thank you so much. After a clean flash, everything is working now plus smoother and battry is better than dirty flash.
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
According to your previous report related to AOD - you successfully installed Pie beta with the newest bootloader (included in Pie DevBase). What happened exactly in the meantime?

BTW - I'm using ZRKN DevBase with the newest BL, without any issue. I performed clean install when I decided to stay with Pie as daily driver
[Samsung Galaxy S9 & S9+ Cross Device Development] ilos:
Just to be sure... i don't see any comment about Exynos.. it's safe to flash devbase on S9+ Exynos version ?

Anyone with this devbase get viper4android from Magisk repo working ?
[Samsung Galaxy S9 & S9+ Cross Device Development] 4timepi:
Do we need to flash dm-verity disabler, RMM bypass or Magisk separately? Or this is included in your rom and it is enough to flash TWRP and your rom? Thanks for reply and for your work!
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
Thread has been updated :cool:

Update is only G965F for the moment (for G960F it will come probably tomorrow)

No it is not necessary. It is enough to flash TWRP and then ROM. If you plan to perform clean install - then you probably will need to install only Magisk Manager app manually (available in post #1)
[Samsung Galaxy S9 & S9+ Cross Device Development] mevorach:
Did clean flash and got this " Only official release binaries are allowed to be ..."

and no recovery !!!!!!
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
Flash only Oreo BL using PC Odin and your phone will boot normally and you will see that TWRP is also in place.

See post #86 above for details

DO NOT flash Oreo stock ROM to "solve" problem !!!

BTW: Have you tried an other ROM or Oreo DevBase ROM in the meantime? I'm asking because I'm trying to figure out what happened exactly in your case
[Samsung Galaxy S9 & S9+ Cross Device Development] mevorach:
well... I was panic and flash oreo last rom from my country with odin , restart to download and flash latest twrp , restart to recovery format data and flash your rom again ( RL5_ RC7)

SAME happened red line with warning . so I did the same but with SoLdieR9312s rom and it worked. So I guess something wrong with your new rom ( BL?) I think SoLdieR9312s uses oreo BL. now I do not see the " oem unlock" in developer mode

and I do not know how to go back to your rom with pie bl
[Samsung Galaxy S9 & S9+ Cross Device Development] mevorach:
Dose not pass safenet ctsProfile false .
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
Seems like you are locked but only with Pie BL

AFAIK - Soldier's ROM does not contain BL at all (need to be flashed separately) - that's why it booted normally. Some time ago I advised to do an experiment to [MENTION=2986787]saxena1[/MENTION] (see post #72 for details) - see his report (post #74).

For me lock appeared when I was playing too hard with /odm security contexts manually - phone booted normally but with unknown CSC and with strange menus in settings (T-Mobile, roaming, etc). Interesting thing is that lock came at NEXT BOOT after it happened.

Look at the attachments and you will see that it is possible to have ZRL5 DevBase with ZRL5 bootloader. Permanent solution which worked for me is described in post #86 (BTW. You can try to wait a few minutes after first boot of stock Pie, not sure if another wipe and another setting up Pie was really necessary - just described my exact way in details :) )

Also noticed it... For some reason SafetyNet fails with Magisk 18.0 + ZRL5 combination. With 17.3 all is ok EDIT: Fixed in RC8
[Samsung Galaxy S9 & S9+ Cross Device Development] :
Hello

For information

https://twitter.com/topjohnwu/status/1072812881232715776
[Samsung Galaxy S9 & S9+ Cross Device Development] judasith:
Prenormal State

Hi, just to report for your info that after clean installing ZRL5, and incredibly while I was already in the system choosing the initial privacy settings, the S9+ suddenly crashed and went into the "Prenormal" black screen of death with red writing state.

Flashing latest OREO BL with ODIN seemed to fix it.
[Samsung Galaxy S9 & S9+ Cross Device Development] mevorach:
exact Same thing happened to me !!!
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
Just figured out the isuue... It seems to be somehow related to Magisk v18.0. Indeed - after clean install after some time - random reboot happened (being aware of the potential issue you reported - I have used BRJ6 BL so nothing wrong happened). It was probably due to lack of Magisk Manager, because at next boot - I immediatelly installed the newest Magisk Manager and it not happened again.

Repeated same scenario (clean install) with Magisk v17.3 inside the ROM and there is no such issue

Anyway - I have prepared v6.0.RC8. Starting from RC8 - bootloader will not be updated anymore (baseband/modem will be still updated as it is much more important). Also - RC8 contains Magisk 17.3 because of above issue in case of clean install (important for those who have Pie bootloader already)

By the way - I have fixed SafetyNet issue in ZRL5 (it was my mistake) - it will pass no mather which Magisk version you decide to use :D

THREAD HAS BEEN UPDATED :cool:

v6.0.RC8 download links for both devices are available in post #1 (thanks again to [MENTION=4128352]ASHLEY117[/MENTION] for G960F dumps)

This is the information for beta stock ROM users (even for those with KNOX 0x0) :)

In case of Pie based custom ROMs there is a workaround :D see attachments
[Samsung Galaxy S9 & S9+ Cross Device Development] mevorach:
So just to make sure rc8 include oreo bl or pie bl ?
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
It does not contain BL at all, so if you are on Oreo BL at the moment - it will stay same. Only baseband/modem will be updated to up to date version.

Even if you are on Pie BL - issue you reported with clean install should not repeat due to Magisk v17.3 on board
[Samsung Galaxy S9 & S9+ Cross Device Development] mevorach:
But it is too late for me , I was on pie BL and had to downgrade to oreo BL ( because of that issue ) and I am waiting for a safe way to upgrade back to Pie BL .
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
For me there was no other way to update BL to Pie than described in post #86 (tried everything else...):

https://xdaforums.com/showpost.php?p=78379098&postcount=86

If sh*t happened once - you can get rid of "KG state: Prenormal" with Pie BL only official way (but waiting 7 days is not necessary, at least wasn't for me)

You can update to v6.0.RC8 safely, no matter if problem happened already or not, but IMO you CAN'T update your BL to Pie until you will pass above linked way
[Samsung Galaxy S9 & S9+ Cross Device Development] saxena1:
congratulations to [MENTION=5150393]_alexndr[/MENTION] for best rom till today. New version G965FXXU2ZRL5_DevBase_v6.0.RC8 boot perfectly with out flashing oreo bootloader (clean flash directly from oreo to this 965f). :D
[Samsung Galaxy S9 & S9+ Cross Device Development] mevorach:
So you are on oreo BL !
[Samsung Galaxy S9 & S9+ Cross Device Development] saxena1:
Yes on oreo bootloader .
[Samsung Galaxy S9 & S9+ Cross Device Development] saxena1:
[MENTION=5150393]_alexndr[/MENTION] I found a bug in phone incoming call with no sound any solution for this?. Other bug in tw launcher white text when night mode applied but it was solved to replace with other version (s.shot attached):D
[Samsung Galaxy S9 & S9+ Cross Device Development] _alexndr:
I've already given you the solution in post #86 if you want to use Pie BL again :)

IMO "risk" of 7 days lock is only if you accidentally let Oreo stock ROM boot to system. Just do EXACTLY as I wrote in post #86 and all should be fine :good: :)

https://xdaforums.com/showpost.php?p=78379098&postcount=86

No problem here with sounds. Have you tried to change incoming call sound to an other (I mean an other stock sound)?

Second bug (night mode) is just related to latest official beta and exists even in official beta (pure stock)
[Samsung Galaxy S9 & S9+ Cross Device Development] irancosta:
Hi guys. Im already on ZRL5 BL. Am i safe to flash this rom? S9+ here. Thanks a lot!!!
[Samsung Galaxy S9 & S9+ Cross Device Development] saxena1:
No problem here with sounds. Have you tried to change incoming call sound to an other (I mean an other stock sound)?

Tried with other stock sound but problem still exists.i want a suggestion with you can I try to replace incallui with previous version beta 2?(only incall ui or contact &dialer)