yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab S9 series] Anghirrim:
I was just about to ask you when you sleep... :ROFLMAO:
[Samsung Galaxy Tab S9 series] ArchVisions:
Lol, now you know. :)
[Samsung Galaxy Tab S9 series] Anghirrim:
Oh and.... should I copy/paste the stock recovery.fstab and replace the device tree one with it?

Edit: nvm, I compared both and the key partitions are here. Mounting options just removed the vbmeta check.

However, I may have to check the encryption part, /data is mounted with encryption support (in original A54 fstab) if I am right.
[Samsung Galaxy Tab S9 series] Anghirrim:
Ahhhhh, I think I understood.... I was looking for the dtbo.img in my fully extracted stock firmware and the only thing I could find was the recovery_dtbo..... but stupid me, the dtbo.img is at the root of the AP/ folder once extracted!

So now, I can confirm also that based on stock firmware images and /AP/META/dynamic_partitions_info.txt, the following content of my boardconfig.mk is OK.

I had to update two values (in red) on dynamic partitions vs the original A54 boardconfig.

# Partitions

BOARD_FLASH_BLOCK_SIZE := 4096

BOARD_BOOTIMAGE_PARTITION_SIZE := 67108864

BOARD_DTBOIMG_PARTITION_SIZE := 8388608

#BOARD_INIT_BOOT_IMAGE_PARTITION_SIZE := 16777216

BOARD_VENDOR_BOOTIMAGE_PARTITION_SIZE := 33554432

BOARD_RECOVERYIMAGE_PARTITION_SIZE := 100663296

TARGET_USERIMAGES_USE_EXT4 := true

TARGET_USERIMAGES_USE_F2FS := true

# Dynamic partitions

# BOARD_SUPER_PARTITION_SIZE :=

BOARD_SUPER_PARTITION_SIZE := 12817793024 # A54 Device Tree original was 11429478400

BOARD_SUPER_PARTITION_GROUPS := group_basic

BOARD_GROUP_BASIC_SIZE := 12813598720 # A54 Device Tree original was 11425284096

BOARD_GROUP_BASIC_PARTITION_LIST := system odm product vendor vendor_dlkm # TODO system_dlkm
[Samsung Galaxy Tab S9 series] Rainbow_Dash:
[ 0.742655] [4: init: 1] init: Loaded kernel module /lib/modules/usb_f_dm.ko
[ 0.742745] [4: init: 1] init: Loading module /lib/modules/direct_dm.ko with args ''
[ 0.744649] [4: init: 1] cpif: direct_dm_create: +++
[ 0.744661] [4: init: 1] cpif: direct_dm_read_dt: version:2 shm_rgn_index:12
[ 0.744666] [4: init: 1] cpif: direct_dm_read_dt: hw_iocc:0 info_desc_rgn_cached:0 buff_rgn_cached:0
[ 0.744670] [4: init: 1] cpif: direct_dm_read_dt: info_rgn_offset:0x00000000 info_rgn_size:0x00000100
[ 0.744675] [4: init: 1] cpif: direct_dm_read_dt: desc_rgn_offset:0x00000100 desc_rgn_size:0x00007f00
[ 0.744679] [4: init: 1] cpif: direct_dm_read_dt: buff_rgn_offset:0x00008000
[ 0.744682] [4: init: 1] cpif: direct_dm_read_dt: max_packet_size:32768 usb_req_num:128 irq_index:4
[ 0.744687] [4: init: 1] cpif: direct_dm_read_dt: use_rx_timer:1 rx_timer_period_msec:1000
[ 0.744693] [4: init: 1] cpif: cp_mbox_register_handler: idx:4 num:0 intmr0:0x0000fffe
[ 0.744699] [4: init: 1] cpif: direct_dm_setup_region: ddm_pbase is null
[ 0.744702] [4: init: 1] cpif: direct_dm_create: direct_dm_setup_region() error:-12
[ 0.744707] [4: init: 1] Kernel panic - not syncing: Direct DM driver probe failed
[ 0.744714] [4: init: 1] CPU: 4 PID: 1 Comm: init Tainted: G C E 5.15.104 #1
[ 0.744721] [4: init: 1] Hardware name: Samsung GTS9FEWIFI EUR OPEN board based on S5E8835 (DT)

This is your issue, this kernel module for some reason is failing

Not sure why, don't have exynos modules source on hand, but even so you probably mixed something up. Don't know
[Samsung Galaxy Tab S9 series] ArchVisions:
That doesn't make any sense I extracted the kernel modules! I grabbed the kernel modules from the stock recovery image.
[Samsung Galaxy Tab S9 series] Anghirrim:
@Rainbow_Dash THANKS A LOT FOR YOUR HELP!!!!!

With the proper dtbo.img and the tiny adjustments I have made to the boardconfig.mk, TWRP flashes and boots just fine.

@ArchVisions was able to boot it.

As you said, touch screen does not work, but other options seem to be working OK using an USB-C adaptor and a mouse 😁
[Samsung Galaxy Tab S9 series] Rainbow_Dash:
hah glad to be of help

For touchscreen you reproduce what i did here . you get keyboard_stm and tsp_stm from your stock vendor image (/vendor/firmware to be exact) and place the folders just like i have in that commit

There's a chance if your touchscreen panel vendor is different it won't be called tsp_stm but something else like tsp_goodix. But it should start with ' tsp_ ' either way
[Samsung Galaxy Tab S9 series] ArchVisions:
Thank you!
[Samsung Galaxy Tab S9 series] Anghirrim:
THanks! Weirdly, touchscreen does work sometime, and then stops working... even without adding your things.
[Samsung Galaxy Tab S9 series] ArchVisions:
OK, the touchscreen to works now. It will stop working though whenever the screen times out though. The final thing I would like to implement is decryption. Or at least something to make TWRP recognize /data. I even tried to reset in TWRP, but even after that TWRP can't seem to recognize anything in it. Same as well with the app and priv-app folders of the system and product partition which I really wanted to edit, but I don't think is possible because of erofs. Is a implementation of multidisabler needed in TWRP for decryption?
[Samsung Galaxy Tab S9 series] Rainbow_Dash:
Decryption on exynos is a no-go at any level. You have to wipe data and somehow disable decryption but to disable decryption you need writable vendor partition

I remember having touchscreen die on my note10 with official twrp as well after it times out and locks. Not sure what to make of it.

There's no multidisabler for these newer devices. Only thing you can do is disable replacement of recovery with that repack zip. To make writable partitions you need to re-create new ones in f2fs or ext4
[Samsung Galaxy Tab S9 series] BlackMesa123:
This is false. The tree they're using as base for their device is mine (Galaxy A54) and has full decryption support.

@ArchVisions @Anghirrim please add proper authorship in your repositories as yours are missing my original commits/authorship.
[Samsung Galaxy Tab S9 series] Rainbow_Dash:
Ah neat. Last exynos i used was 9825 and decryption was not a thing. Glad to be proven wrong.
[Samsung Galaxy Tab S9 series] Anghirrim:
Hi,

I did almost everything locally and as I was facing some 2FA authentication issue while doing "git push" from my computer, I just made an archive out of the device tree folder and sent it to @ArchVisions .

Given that we only made a few changes to your device tree to adapt it, I believe the easiest will be to fork your A54 tree and do the few commits online.

Will it be sufficient to preserve authorship and link between your and our github repos?

Thanks,

Side note: I'm not a dev, I just kinda know some basics for building/porting roms, but no more. So expect some misunderstanding or stupid questions from my side. 😅
[Samsung Galaxy Tab S9 series] ArchVisions:
Well this is indeed surprising. I do here mixed things about decryption, but this one actually makes sense. How exactly would me and @Anghirrim implement decryption correctly for our device?

By no means, I am a dev. I am still learning a lot of things.
[Samsung Galaxy Tab S9 series] ArchVisions:
While not exynos I have seen people do it with devices like the Tab S8 series. The guy added a multidisabler in TWRP that gave you the possibility to resize the vender partition.
[Samsung Galaxy Tab S9 series] Rainbow_Dash:
Multidisabler is something else. It added rw capabilities to already existing f2fs partitions. We have erofs which by design it's made to be read only. So re-creating the image is the only way i know of
[Samsung Galaxy Tab S9 series] ArchVisions:
Erofs was introduced to devices after 2020. The Tab S8 has erofs.
[Samsung Galaxy Tab S9 series] Rainbow_Dash:
I'm pretty certain tab s8 still had f2fs
[Samsung Galaxy Tab S9 series] ArchVisions:
Mhm
[Samsung Galaxy Tab S9 series] BlackMesa123:
Yes, this is the ideal.
[Samsung Galaxy Tab S9 series] BlackMesa123:
All you probably need is to replace the prebuilt kernel (& modules) and all the proprietary vendor blobs in ramdisk with the ones from your device, the only thing you would have to modify in the configs is just the device codename and those few flags referencing partitions size. The TAs in /vendor/tee were compressed in tar archives by myself as A54 SecureOS will refuse to load TAs if they do not match the bootloader build installed in the device, it's probably the same on Tab S9 FE as they share the same SoC.
[Samsung Galaxy Tab S9 series] BlackMesa123:
EROFS is the standard in Android nowadays and Samsung adopted it for every device shipping with Android 13 onwards (2023> released devices). Introducing stuff such as multidisabler or other scripts that disable encryption/change the OS FS is just completely stupid imho.
[Samsung Galaxy Tab S9 series] Rainbow_Dash:
I agree

Having TWRP modify the filesystem

by default

once it's booted is a really bad idea and in some cases even broke some roms. But if you include a binary that gets manually triggered by a terminal command, eh who cares. I guess this is one of the reasons why many aosp devs refuse to hear about twrp and push for their recoveries instead

Hey wild question, is there something about recent devices that enabled this? Because i see you bundled the trustzone applets then initialized gatekeeper and decryption works? I was wondering why we didn't think of this before
[Samsung Galaxy Tab S9 series] ArchVisions:
Good to know!
[Samsung Galaxy Tab S9 series] BlackMesa123:
I'm not into Exynos devices myself so Idk if the same behavior applies to other Exynos devices other than A54/Exy 1380 based devices: as opposed to Exynos devices where TAs are shipped inside the vendor partition (OS), Qcom devices have TAs stored inside a bootloader specific partition (apnhlos). No wonder most of TWRP builds in Samsung devices are broken, they're either made by buildbots/people who have zero knowledge and just put together a broken TWRP device tree basing off other devices without even know what they're doing
[Samsung Galaxy Tab S9 series] Anghirrim:
@BlackMesa123 @Rainbow_Dash

I have forked the device tree and made all changes but changing the prebuilt kernel.

GitHub - Anghirrim/android_device_samsung_gts9fewifi: Samsung Galaxy Tab S9 FE Wifi TWRP Device Tree.

Samsung Galaxy Tab S9 FE Wifi TWRP Device Tree. Contribute to Anghirrim/android_device_samsung_gts9fewifi development by creating an account on GitHub.

github.com

As the file is larger than 25Mo, I'll have to push it from my local repository.

So as github documentation says, I have cloned my new device tree locally, then copy/pasted the prebuilt kernel in the prebuilt directory and followed the instruction to add the file to my github repo, but it fails:

[Anghirrim@OptiAnghi gts9fewifi]$ git add .
[Anghirrim@OptiAnghi gts9fewifi]$ git commit -m "Add prebuilt kernel for gts9fewifi"
[android-12.1 645c21e] Add prebuilt kernel for gts9fewifi
1 file changed, 0 insertions(+), 0 deletions(-)
create mode 100644 prebuilt/Image
[Anghirrim@OptiAnghi gts9fewifi]$ git push origin android-12.1
Username for 'https://github.com': Anghirrim
Password for 'https://Anghirrim@github.com':
Énumération des objets: 6, fait.
Décompte des objets: 100% (6/6), fait.
Compression par delta en utilisant jusqu'à 6 fils d'exécution
Compression des objets: 100% (4/4), fait.
erreur : échec RPC ; HTTP 400 curl 22 The requested URL returned error: 400
send-pack: unexpected disconnect while reading sideband packet
Écriture des objets: 100% (4/4), 16.67 Mio | 7.55 Mio/s, fait.
Total 4 (delta 1), réutilisés 0 (delta 0), réutilisés du paquet 0 (depuis 0)
fatal : l'hôte distant a fermé la connexion de manière inattendue
Everything up-to-date

Did I do anything wrong?

Side note: I also tried "git remote add https://github.com/Anghirrim/android_device_samsung_gts9fewifi.git' and it returned that the origin was already properly set.
[Samsung Galaxy Tab S9 series] Rainbow_Dash:
Wild

I'll give this a shot on my 9825, 8895, 8890 and 7420 and come back to this (y)(y)
[Samsung Galaxy Tab S9 series] Anghirrim:
Ok, found a solution, I had to increase the buffer size and then pushed the prebuilt kernel image.

Device tree is now complete.

Side question, my recovery/root/lib/modules are from stock firmware , XXU1BWKB, while the rest (dtbo.img, dtb and touch firmware) are from XXS2BXB3 (the latest one).

Should I keep it as it is if it works fine? Or update the modules?

Thanks,
[Samsung Galaxy Tab S9 series] Rainbow_Dash:
Not sure how it happened, but yeah you ideally want them to be the same firmware be it new or old. Now if it works i guess it works. Do whatever you feel like
[Samsung Galaxy Tab S9 series] Anghirrim:
Oh it's just because I had the previous firmware already downloaded when I started replacing files, and ended up with the newest one. Lol.
[Samsung Galaxy Tab S9 series] DocSnyder75:
The recovery works for me. But i tryed to flash a GSI System, but its not work. The gsi is not flashed.

What can i do?
[Samsung Galaxy Tab S9 series] Anghirrim:
Which version did you try? For the Tab S9 or Tab S9 FE?

And if Tab S9 FE, which one? there are several attempts on my GDrive.
[Samsung Galaxy Tab S9 series] DocSnyder75:
I use the Tab S9 ultra. TWRP works so far ... Stock boots fine, but im not able to flash a image to system.
[Samsung Galaxy Tab S9 series] Anghirrim:
Ah sorry, the TWRP I am trying to build is for Tab S9 FE.
[Samsung Galaxy Tab S9 series] DocSnyder75:
If this a TWRP problem? Can i hope for future?
[Samsung Galaxy Tab S9 series] Anghirrim:
Hi,

Thanks for the advice.

So, here is what we did:

- All you probably need is to replace the prebuilt kernel (& modules) ==> We did replace prebuilt kernel, dtb, dtbo.img and also the content of /recovery/root/lib/modules.

- all the proprietary vendor blobs in ramdisk with the ones from your device ==> We did only for recovery/root/vendor/firmware content.

- We did not change anything in:

- recovery/root/vendor/lib64

- recovery/root/vendor/etc (or system/etc)

- recovery/root/vendor/tee ==> What to do here?

- the only thing you would have to modify in the configs is just the device codename and those few flags referencing partitions size. ==> Of course yes, I did update all necessary makefiles. While for the flags referencing partitions sizes, I found them only in boardconfig.mk, and had only to update the two dynamic partitions. The others were the same between A54 and Tab S9 FE.

- The TAs in /vendor/tee were compressed in tar archives by myself as A54 SecureOS will refuse to load TAs if they do not match the bootloader build installed in the device, it's probably the same on Tab S9 FE as they share the same SoC. ==> Not sure I follow you here. I'll have a look at what TA's are and come back with questions if needed. I saw that at least there is one per stock firmware version.

Once again, thanks a lot both for your help and support.
[Samsung Galaxy Tab S9 series] Rainbow_Dash:
You should probably start a new thread since you already have a semi-working build
[Samsung Galaxy Tab S9 series] Rainbow_Dash:
Can you link me the gsi you tried flashing so i can give it a go myself?

And while i troubleshoot that, try flashing it with fastbootd and let me know if that works
[Samsung Galaxy Tab S9 series] Anghirrim:
Yes, I think that'll be better. And we'll stop squatting your thread.

I'll do tomorrow (and thanks for your patience).
[Samsung Galaxy Tab S9 series] DocSnyder75:
I use this https://github.com/ponces/treble_aosp/releases

With DSU Sidelaoder works this GSI great. Pure Android ...

I will try fastbootd tomorrow.
[Samsung Galaxy Tab S9 series] DocSnyder75:
Yes it works fine with fastboot trough twrp. Ponces aosp runs great so far ...
[Samsung Galaxy Tab S9 series] Anghirrim:
@Rainbow_Dash

Just fyi, decryption now works on S9 FE. :)

@BlackMesa123 , we finally understood what to do with /tee. Thanks!
[Samsung Galaxy Tab S9 series] DocSnyder75:
For me USB OTG dosent work. I cant mount my USB stick. What can i do? SD Card the same ... Wont work.
[Samsung Galaxy Tab S9 series] Anghirrim:
@Rainbow_Dash ,

May I ask you one last question about the disabled vbmeta. Is it supposed to be device specific?

ArchVisions managed to flash and boot TWRP using BlackMesa's vbmeta. Once he got access to fastboot

d

, we tried to create a S9 FE dedicated one from stock firmware by doing:

fastbootd flash --disable-verity --disable-verification vbmeta vbmeta.img

Then, from adb shell:

dd if=/dev/block/sda24 of=/sdcard/vbmeta.img

And finally, we made a .tar out of the output file. But no success while trying to flash with Odin.

Could you please clarify how it should be done, the only tutorials on the net give the fastboot command and I don't know what to do with Boot Editor though...? Thanks,
[Samsung Galaxy Tab S9 series] Rainbow_Dash:
the vbmeta i created should be compatible with the s9fe as well. I created it with avbtool

You can read more about it here
[Samsung Galaxy Tab S9 series] Anghirrim:
Okay thanks!

This link is much more clear than my previous readings (https://android.googlesource.com/platform/external/avb/+/master/README.md).

Thanks for the info and the link!
[Samsung Galaxy Tab S9 series] flanter21:
Sorry I'm a bit of a noob (it's been 8 years since I last flashed TWRP to a device). I flashed the repack.zip while in TWRP using adb sideload, but now my device is bootlooping into TWRP and I can't access android. I'm redownloading the rom using frija but does anyone have a clue of what I did wrong? Sorry again!

EDIT: ok the solution is just that when you get into TWRP you go wipe --> format data, then after that you can reboot into TWRP again. This explains it really well.

For the repack.zip, again its just adb sideload repack.zip

To put TWRP there in the first place, if you're using heimdall use the command heimdall flash --RECOVERY recovery.img --no-reboot --USERDATA vbmeta.img obviously making sure you have the files in the same folder as you. Then you hold vol down+power until the screen goes black then vol up+power until the unlocked bootloader warning comes up. Got this from here.
[Samsung Galaxy Tab S9 series] TxT-1:
Decoding doesn't work for me I just tried it with my sm-x916b
[Samsung Galaxy Tab S9 series] ArchVisions:
You didn't read correctly the post. There is currently no decryption support.
[Samsung Galaxy Tab S9 series] TxT-1:
Maybe I didn't read it correctly because I expected Decryption

TeamWin

Ofox team for repack zip, just flash it and decrypt it
[Samsung Galaxy Tab S9 series] TxT-1:
Rainbow_Dash​

Is there a way to decrypt your twrp ?

​
[Samsung Galaxy Tab S9 series] essence25:
This thread is a bit confusing. Which TWRP link do I download for the TAB S9+ ??

"TWRP-gts9p-V1.tar" or "gts9p_twrp_try2.tar"
[Samsung Galaxy Tab S9 series] Rainbow_Dash:
For s9+ try the _try2.tar file and let me know if it works. It's still untested
[Samsung Galaxy Tab S9 series] essence25:
Has anyone tested gts9p_twrp_try2.tar on the TAB S9+ Plus ? I'm a bit scared to install it since I have customized the device. Anyone can confirm if it works?

I want to be able to image the internal storage for backup and restore it if I ever screw up the system etc.

ArchVisions, when using your NinjaSU-123 (LKI) kernel will the data partition be readable in this TWRP?​
[Samsung Galaxy Tab S9 series] flanter21:
What's everyone's knoxguard status? Reason I ask is because my device keeps locking up due to remaining installment balance even though I bought it without any trade in or finance directly from Samsung and it's a wifi model. I asked Samsung to unlock it once, which worked... for a few days. I've now asked again, but after I set it up, it went from KG STATUS: COMPLETED (11) to KG STATUS: CHECKING (11). Then the first time, it changed to ACTIVE after a few days. Does anyone have any idea what I'm doing wrong?
[Samsung Galaxy Tab S9 series] essence25:
Where do I check?
[Samsung Galaxy Tab S9 series] ArchVisions:
In Download Mode it is KG status
[Samsung Galaxy Tab S9 series] ArchVisions:
Yes it should work fine.
[Samsung Galaxy Tab S9 series] essence25:
Say I want to image/backup my system running your kernel KSU LKM, in order to backup the tablet so I can restore it exactly as it was backed up. What is the most efficient way to do that? Do I need to disable forced encryption?

If I install TWRP now, can I do that? Is the data partition readable with your kernel? Also when making a backup, what needs to be backed up? just data?
[Samsung Galaxy Tab S9 series] ArchVisions:
You can't backup the data partition nowadays. Only with decryption. Multi-Disabler for example was made for F2FS or the Tab S8 not the Tab S9. If you really wanted to decryption support would need to be added to TWRP using the TAs. Currently I don't have the time for development anymore as I have been busy with other things. @Rainbow_Dash your TWRP could use decryption just saying. :)
[Xiaomi Redmi Note 7 Pro Questions & Answers] dhdhdhjuels:
Does anyone know if there's s HyperOS rom for violet (Redmi Note 7 Pro)? And if yes, can you send me the thread/link?
[Xiaomi Redmi Note 7 Pro Questions & Answers] andreilito:
Violet - Browse /ReleasedRom at SourceForge.net

sourceforge.net
[Xiaomi Redmi Note 7 Pro Questions & Answers] andreilito:
HyperOS Changelogs

[ ]March 06, 2024

----Date: 06.03.2024---

• Initial Build Based On HyperOS EU ( Thanks Xiaomi EU Team )

• Initial Vendor Port

• Dynamic Rom

• Firmware Inbuilt

• Decrypted By Default

• Enforcing Build

• Added Unlimited G-Photos Spoof ( Check Out On Settings/Additional Settings/Extra Features )

• Added Higher Fps Spoof On Some Games

• Added Secure Screenshot Bypass Spoof

• Added Modded Package Installer

• Safety Net Passes By Default

• Updated Camera To 5.0

• Hyper Non-KSU Kernel By Default ( Use This Kernel For KSU )

• Removed Mi-Soundfx ( Now No Bugs )

• More Are There ( Lazy To Write )

Bugs?

• AOD
[Xiaomi Redmi Note 7 Pro Questions & Answers] andreilito:
Flashing Instructions

[ ]March 06, 2024

• Flash This OrangeFox Recovery

• Reboot into recovery

• Wipe Cache, Dalvik, and Data ( Don't Touch Anything Else )

• Flash The Rom Zip

• Format Data ( If You Are Coming From Encrypted Rom )

• Reboot into system

--Special Note--

super_empty.img is included in the zip
[Xiaomi Redmi Note 7 Pro Questions & Answers] andreilito:
Credits For HyperOS

[ ]March 06, 2024

Thanks to all these wonderful peeps, I was able to build this rom. I really appreciate there efforts..

@bhatsahab ,@Dandaaaa For most of the help and fixes

@raghavt20 For super implementation

@HyperPower17 For base kernel

@dulquersalmaan22 ,@kakashi1v1 For Mods

Special Thanks To @blacktape75 For Everything

@Curious_Nom ,@shahadatofficial10 For testing
[Xiaomi Redmi Note 7 Pro Questions & Answers] andreilito:
HyperOS

Status: PORT

Android: 13 (T)

Released: 06.03.24

By: @Blank1016

Disclaimer

Download [2.97GB]

Changelogs

Flashing Instructions

Credits

Screenshots

Support: @Blank_Ports

Follow: @RedmiNote7ProChannel

Join: @VioletDiscussion
[Realme GT] kutu34:
Help

I don't have 120hz in the settings, only 60hz and 90hz, but my phone should switch to 120Hz, I have a realme gt, if you can think of anything I will be very happyView attachment 6078078
[General Questions and Answers] ruth3n:
Hey, guys! I think I just erased something I shouldn't have. Now when I turn the phone on, it says "dm-verity corruption" and after pressing the power button to bypass this message it shows "Orange State" and after booting up after 5s it just shuts down. I tried to go into Fastboot but it just reboots and it all happens again. I would be grateful if you can help me.

Realme C21 with Qualcomm CPU
[Samsung Galaxy A52 5G] KokaiBalazs- dev:
what the title really says please if you on oneui 6 then please dump the boot.img for me bcs i dont want to download the whole irmware just for that