[ROM][G96xF/DS/FD/N][ALEXNDR] * UHFVB4 * DevBase v7.4 * Encryption support [Mar-25]

[spamtrash]

Hi,
I would like to give my dear S9 to my father.
What should I do to reset it but keep this great Alexndr rom?
Reset from Samsung settings?
Something from TWRP?

Thanks for your kind help

Perform the factory reset from the working phone. You'd need to manually erase your files from storage.

 

[Nigcra]

Nothing has been working with Magisk 23.0 for a while now. No matter if it is the 2FA or the NFC app of my bank.

 

[legedug01]

Thanks for the ROM. All apps and operations are working.

 

[jonsnow69]

Dirty Flashed and so far all is good, thanks for the update.

 

[khaled678]

Is there telegram channel for this great rom ?

 

[charsta]

Hello all! I had some issues with an older version of this rom, so I decided to flash the latest release. However I noticed that Play Store says that the device is not certified and CTS profile is failing. Is there any way to fix that?
I read in previous comments that I can use Magiskhide props or/and the Universal SafetyNet Fix module.
However I'm not sure what I should use and how.
I already clean install the rom twice so I don't want to messed it up again!!

 

[kost7]

Hello all! I had some issues with an older version of this rom, so I decided to flash the latest release. However I noticed that Play Store says that the device is not certified and CTS profile is failing. Is there any way to fix that?
I read in previous comments that I can use Magiskhide props or/and the Universal SafetyNet Fix module.
However I'm not sure what I should use and how.
I already clean install the rom twice so I don't want to messed it up again!!

For me just USFNF v.2.1.2 (along with Riru) was sufficient to pass all Safety Net tests.

 

[TheAKAlias]

Hi guys. So I've a soft brick at my hands and have probably lost my encrypted data.

@_alexndr Can you confirm that the only way I've left - to unbrick my device - includes a complete ODIN factory reset that will include effectively wiping my external sdcard? Or is there a way around?

What happened:

1. downloaded the latest v7.4
2. moved v7.4 install file to external sd
3. booted into twrp and performed system partition backup (system image, system, recovery, boot)
4. initiated via twrp a dirty flash
4.1 received error messager after 1 second: damaged zip file
5. rebooted into sysem - WORKED
5.1 realized my SDcard was not mounted and the system tried to "encrypting sdcard 10%/11%/..."
5.2 shut down system immediately
6. repeated step 5 with same results
7. booted into twrp and tried to restore from backup (system image, system, recovery, boot)
7.1 received error message "extracttarfork() process ended with error=255"
8. rebooted into system and rebooted into twrp
9. performed full restore only "system image"
10. booted into system - same as before, in step 5; immediately shut down
11. tried to boot into twrp without success; bootloader 1 error message: "could not do normal boot. INVALID KERNEL LENGTH"

I am a bit screwed here, i think?

the funny thing is that

(a) a OS boot still required me to enter my encryption pin
(b) the OS itself had no sdcard access/mounting issues apparently, same for TWRP partially. HOWEVER, the TWRP system backup was stored on my external SD card - How was TWRP even able to perform a restore from it, if it could not read /data and the sdcard in the first place?

Don't know what exactly went wrong... thanks for any hints in advance

 

[spamtrash]

Hi guys. So I've a soft brick at my hands and have probably lost my encrypted data.

...

Don't know what exactly went wrong... thanks for any hints in advance

1. ALWAYS check the md sum of the downloaded/copied file. Message in your p. 4.1 suggests that the file was corrupt on some stage? Your point 11 can be a result of this as well, I think.
2. I'd personally neither use nor advice to perform a dirty flash on the encrypted device
3. The behaviour you've described is correct one, please read first post by @_alexndr :
"Regardless of the above root options, starting from DevBase v4.4+, you can also use "encrypt" option (place "encrypt" string anywhere in the ZIP file name, e.g. "G960Fxxx_DevBase_v6.x_encrypt.zip"). All your data will be encrypted "on-the-fly" at next boot after ROM update/reinstall. Wipe data is NOT necessary to use this option. You will NOT lose your data & apps but it is extremely important - do not interrupt encryption process during this "special" boot! "
You've interrupted the process, so I am almost sure that the data are gone now.
I would recommend you the spoiler: "Notes related to encrypted devices:" in the first post as well, as it contains the reply to your question: "Can you confirm that the only way I've left - to unbrick my device - includes a complete ODIN factory reset that will include effectively wiping my external sdcard?"
Anyway, how to recover back to normal?
I do not have access to your device, so actually I am unsure what is the status of it (is it visible to PC in TWRP mode if connected by USB? Can u use adb commands? etc.) so the advice must be pretty generic:
1. Yes, I'd download latest stock ROM using Frija or whatever you prefer
2. Flash with Odin
3. BOOT the device to system and (Again, a personal preference: I hide all my personal data using EDS by Sovworks, paid version because of my laziness as it is compatible with VeraCrypt, TrueCrypt and LUKS and in paid and rooted phone mode it can mount encrypted partitions as FAT, NTFS, EXT4, EXT3, EXT2 and ExFAT and IMHO is better and safer as I am mounting the encrypted partition only while needed, for example when I want to access specific data files or use the KeePass database) DO NOT input security which would trigger encryption on this stage
4. Install TWRP (read the thread and decide which version. Even in the first post you will find the interesting info about the encryption and TWRP version correlations)
5. Download the DevBase and check the checksums to confirm that the file is not damaged;
6. Flash the ROM via TWRP (you can use the "encrypt" option now if you really like it this way
7. Reboot and DO NOT interrput the sdcard encryption (again, pls refer to first post)
8. REMEMBER: before flashing ANYTHING make the BACKUP

 

[TheAKAlias]

Hi spamtrash! Thanks for the answer.

Your points regarding not interrupting encryption are helpful. Also, in the future I'll the check the md sum; but I need to figure out how to do that in android first

However, I've dirty flashed multiple times before to a an updated version of Alexndr's ROM - and never encountered problems. Also, not (consciously) saw the "encrypting SD card" after boot after a dirty flash.

I actually just flash twrp recovery via odin and it fixed the boot issue. I.e. now I can boot into system OS as well, normally and encrypted.

I still receive the "encrypting SD card" message which I still prevent by shutting down again immediately. I am not sure what the process actually does, and I cannot stop it from within the system. It also does only encrypt 8,5 GB (out of 400 GB SD card). Which is why I am not sure what the process is about to encrypt....

Might it be possible that the system is just encrypting my latest TWRP backup (about 8,5 bg in size) - so as you and Alexndr write,... this also happens after every SD card change in TWRP?

In any case... as far as I understand, all my data should still be on the SD card (i can read the file tree via Windows). But for some reason, TWRP and sytem just fail to mount the sd card.

Might the "encrypting sdcard..." process be about some sort of "remounting" the encrypted SD card? Technically, my not modified system ROM should be able to restore the SD card without losing data...?

 

[TheAKAlias]

So just took the risk and letthe encryption process finish. Now, the SD card works perfectly fine again.

Lessons learned for me:

(1) always check the hash sum of ROM updates
(2) changes to SD card in TWRP require a partially reencryption after reboot

Still don't know how the recovery/boot sector got corrupted...

//edit

Ok so I found the issue.... or actually the feature *wall*

If you encrypted your sd card, now wonder the recovery cannot flash from it, as the file is encrypted!! ... and twrp for 965 does not have the capability to read the encryption (as it has with other devices). So.... i need to use an unencrypted sdcard going forward to flash the ROM.

 

[Qa117]

Download ROM

S9 (SM-G960F/DS/FD):
>> G960FXXSHFUJ2_DevBase_v7.4.zip << (Android 10, updated Nov-13-2021, more info HERE)

S9+ (SM-G965F/DS/FD):
>> G965FXXSHFUJ2_DevBase_v7.4.zip << (Android 10, updated Nov-13-2021, more info HERE)

SM-G96xF/DS/N repository:
>> S9/S9+ repository << [ AFH | MediaFire ]

Note:
Check MD5 sum BEFORE flash (useful TOOL), because flashing damaged or incomplete ZIP files could (soft) brick your phone! Correct MD5 sum is shown on the AndroidFileHost website while downloading.

This rom doesn't fit for 9650

 

[spamtrash]

So ... flash the ROM.

Excellent work, overall. I'd encourage you to play with phone (Samsung Galaxy S series is relatively difficult to brick
One hint: I've noitced that you were struggling with checksum on the phone. My personal recommendation: use PC to download, verify checksum and then proceed. Risk of corrupting the file while copying to the phone is minor and if you'd be sure that you have a "good" file on your PC - you do not need to re-download (makes life a bit easier).
Regarding encryption of 8.5GB vs 400GB - a hint: what's the volume of data stored on SDCard?
Last but not least: it is obvious that if your SDCard is encrypted, the Recovery mode will not have access to it: the purpose of encryption is to keep the data encrypted until user boots into the system and authorises himself. Otherwise, the encryption would be pointless as all the data would be unprotected for any thief who would steal the phone and would be able to flash a recovery. It's a feature, not a bug
Hope that you will not abandon XDA and while learning from your own failures, errors and faults - one day wou will be able to try to help others, sharing your experience.
What, actually, I am trying to do in my spare time.

 

[spamtrash]

This rom doesn't fit for 9650

Good, very good discovery.
so, you have found that ROM which is for 960F/DS/FD OR G965F/DS/FD OR G96xF/DS/N does not work for device 9650?
It indeed deserves the Nobel's prize, my young Einstein.

If I'd be you, I would complain to my math teacher in primary school that she/he was not able to tech me the difference between:
9650 and:
960F;
960DS;
960FD;
965F;
965DS;
965FD;
96xF;
96xDS;
95xN????
I'd seriously consider (if I'd be you) to request at least cost of the books to be reimbursed.

 

[vponomarev]

What's the latest Oreo ROM?

 

[hotwert]

Hello all! I had some issues with an older version of this rom, so I decided to flash the latest release. However I noticed that Play Store says that the device is not certified and CTS profile is failing. Is there any way to fix that?
I read in previous comments that I can use Magiskhide props or/and the Universal SafetyNet Fix module.
However I'm not sure what I should use and how.
I already clean install the rom twice so I don't want to messed it up again!!

It seems Magiskhide doesn't work anymore because they have a new method to detect root. My banking app doesn't work either.

I tried anything, Magisk canary Version with zgisk, etc... Nothing works.

You need at least Android 11 to use Magiskhide again.

 

[G_c_]

Kind help required, whenever I try to install this rom without root (including "noroot" in the package name), I soft brick the device (the galaxy s9 logo appears and then the device turns off and then this cycle repeats), there is an error shown in the recovery stating /odm not mounted: no such directory found, I've used the recommended recovery version (3.2.X), what am I doing wrong? I don't want root, since the banking apps don't work.

 

[bilbonotry]

It seems Magiskhide doesn't work anymore because they have a new method to detect root. My banking app doesn't work either.

I tried anything, Magisk canary Version with zgisk, etc... Nothing works.

You need at least Android 11 to use Magiskhide again.

I was able to use Google pay and my banking apps with this ROM. Had Magisk 23, hid Google stuff and banking apps, installed universal safety net fix and riru modules. Had to follow the procedure in another module thread (in a nutshell switch to plane mode, delete Google apps data, delete some value in dg.db of Google pay, reboot, switch off plane mode) but YMMV.
Edit : in fact I did what this module does https://forum.xda-developers.com/t/...s-17-1-22-on-pie.3929950/page-9#post-79643248

 

[hotwert]

I have a problem with Bluetooth, I can connect to my speaker and headphone without any problem. It reconnects once I paired them.

But then I activate airplane mode, and deactivate it, it forgets all Bluetooth connections and I have to pair them again.

When I don't use airplane mode for weeks, it works perfect. But once I use it just for a second, all paired connections are lost...

 

[jonsnow69]

I have a problem with Bluetooth, I can connect to my speaker and headphone without any problem. It reconnects once I paired them.

But then I activate airplane mode, and deactivate it, it forgets all Bluetooth connections and I have to pair them again.

When I don't use airplane mode for weeks, it works perfect. But once I use it just for a second, all paired connections are lost...

This is expected, it happens with rooted Samsung roms, there's a Magisk Module that fixes it: Bluetooth Library Patcher