Database Develop

Why there is delay in development of Roms for X4?

Not even single Custom Rom is ported yet, everyone is flashing Android One Firmware or the stock! ?

I think the A/B partition scheme is slowing down development. If I am not mistaken, several other phones with A/B partitions also have slow development. On top of that, I think our phone is an odd hybrid that has A/B partitions, but will not get Project Treble, so we are stuck in the middle between the two targets.
There is a working TWRP recovery, so that does count for something. I have, as well as several others, been trying to get a bootable device tree for LineageOS, although it is slow going and we all have IRL commitments.

I'm willing to make donations to the custom rom developer. Especially if it is possible to remove the lock from installing sd card as internal memory.

I dont really care about custom roms or new android versions.
I'd just want to be able to install android security updates when motorola no longer supports it..
but that's quite hard if you dont Know a thing about programming i think?

Note 9 Treble Compatible?

I just picked an SM-N960W. I don't have an OEM unlock option in the development settings so I am guessing ROMs and TWRP are not an option, but is the snapdragon Note 9 Treble compatible?

No. Samsung just do their own thing really, the OS is so heavily customised that even if it was "Treble compatible", it most likely wouldn't have any impact on speeding up their release cycle.

treble requires an unlocked bootloader.

Note 9 is partially Project Treble enabled...no seamless upgrades.View attachment 4671347
Sent from my SM-N960U using Tapatalk

bober10113 said:
treble requires an unlocked bootloader.
Click to expand...
Click to collapse
I think you're confusing Project Treble with something else. Project Treble is Google's way of offering faster, seamless updates to stock phones. It works on locked bootloaders.
Basically, a Project Treble phone has two system slots, A and B, like a Pixel device. Both slots have a full system image. While you're phone is operating off slot A, the update will actually download and install on slot B. So you can keep using your phone like normal while the update not only downloads in the background but actually installs. Then it prompts you to restart, during which time it switches system slots, and you'll run on slot B until the next update.
I've heard someone else say it requires an unlocked bootloader, and I'm not sure where that information came from, but it's inaccurate. It absolutely works on a locked bootloader.
Samsung could easily implement Project Treble on their phones. The OG Pixel didn't use Treble until it was upgraded to Oreo, then it had the two slots and used seamless updates. Google required all phones that SHIPPED with Oreo to support Project Treble. It appears the Note 9 supports it, it just doesn't implement it. It's a case of Samsung is big enough to do whatever they want.

As I posted above, the Note 9 is Treble enabled. That means that it supports the new hardware driver model. While it doesn't have the A/B partition for seamless upgrades, that makes for faster upgrades nonetheless.
Sent from my SM-N960U using Tapatalk

Mr. Orange 645 said:
I think you're confusing Project Treble with something else. Project Treble is Google's way of offering faster, seamless updates to stock phones. It works on locked bootloaders.
Basically, a Project Treble phone has two system slots, A and B, like a Pixel device. Both slots have a full system image. While you're phone is operating off slot A, the update will actually download and install on slot B. So you can keep using your phone like normal while the update not only downloads in the background but actually installs. Then it prompts you to restart, during which time it switches system slots, and you'll run on slot B until the next update.
I've heard someone else say it requires an unlocked bootloader, and I'm not sure where that information came from, but it's inaccurate. It absolutely works on a locked bootloader.
Samsung could easily implement Project Treble on their phones. The OG Pixel didn't use Treble until it was upgraded to Oreo, then it had the two slots and used seamless updates. Google required all phones that SHIPPED with Oreo to support Project Treble. It appears the Note 9 supports it, it just doesn't implement it. It's a case of Samsung is big enough to do whatever they want.
Click to expand...
Click to collapse
vagelis said:
As I posted above, the Note 9 is Treble enabled. That means that it supports the new hardware driver model. While it doesn't have the A/B partition for seamless upgrades, that makes for faster upgrades nonetheless.
Click to expand...
Click to collapse
I stand corrected then.
speaking of the subject, I would believe these are the two partitions being called as A and B:

bober10113 said:
I stand corrected then.
speaking of the subject, I would believe these are the two partitions being called as A and B:
Click to expand...
Click to collapse
Interesting. I'm not sure, honestly.

Old thread, but I wanted to clear things up for future readers. A/B partitions (aka seamless updates) are not directly related to treble. They are two different things. Our device IS treble enabled, just like all phones that released with 8.0+, since it's a requirement that Google set. This, and the lack of system-as-root, does prevent us from being able to use A/B GSIs (Generic System Image), but we should be able to run a-only GSIs. The only problem you could face is with an exynos device, since the chip usually isn't supported by the GSI maintainer... there is some that do support it though. I haven't tested this myself on my Note9, but I do have some Treble experience with my OP3T that has been treblized.

FallenFlame said:
Old thread, but I wanted to clear things up for future readers. A/B partitions (aka seamless updates) are not directly related to treble. They are two different things. Our device IS treble enabled, just like all phones that released with 8.0+, since it's a requirement that Google set. This, and the lack of system-as-root, does prevent us from being able to use A/B GSIs (Generic System Image), but we should be able to run a-only GSIs. The only problem you could face is with an exynos device, since the chip usually isn't supported by the GSI maintainer... there is some that do support it though. I haven't tested this myself on my Note9, but I do have some Treble experience with my OP3T that has been treblized.
Click to expand...
Click to collapse
So what about a Canadian Note9? It's a SM-N960W, and I'd love to try a new GSI rather then running pure stock, but I also don't wanna brick this Note.

MoistPicklez said:
So what about a Canadian Note9? It's a SM-N960W, and I'd love to try a new GSI rather then running pure stock, but I also don't wanna brick this Note.
Click to expand...
Click to collapse
ure on a north American device. you can't flash anything apart from stock firmware.

Treble ROMs

Hi guys, I have an SM-N960F dual sim exynos Note 9 and i have recently discovered this whole other element of ROM flashing known as project treble ROMs. I tried to flash a few different ones and i could only get one to work and the rest all just either bootlooped or stayed on the initial splashscreen. I was wondering if anybody could shed some light on them a bit for me and perhaps knew exactly the best way to flash them, and what firmware is best to start on beforehand etc? I found the whole thing EXTREMELY confusing especially with venfor images and kernel images etc...
Thank you for any input/help!

We can't really use the term Project Treble when talking about Samsung phones. Technically it is implemented, but Samsung being Samsung, it's quite a non-standard implementation and not really compatible with anything else.

oddbehreif said:
We can't really use the term Project Treble when talking about Samsung phones. Technically it is implemented, but Samsung being Samsung, it's quite a non-standard implementation and not really compatible with anything else.
Click to expand...
Click to collapse
Ive flashed a few of them onto my phone but it seems to be a bit of hit and miss as to whether they boot up or not. The ones that do have been good in terms of the size and speed etc, I even flashed a generic copy of OneUI which worked well.

I am on Pie base using the Dr.Ketan rom, so I tried a few GSIs which are supposed to be compatible with Pie base. I took them from here.
The way I flash them is:
1. Factory reset from TWRP
2. Flash the GSI as system image
3. Flash stock kernel otherwise you will be stuck on boot logo or you will get into bootloop. To flash the stock kernel I just use Dr.Ketan's rom, because the UI upon flashing allows you to choose and flash stock kernel and skip everything else.
(They mention that we should flash Permissiver also, but it gives error so I can't flash it)
So those GSIs boot up, but they are barely usable. The "System is finishing update" and "System setup will start soon" are stuck for me and never finish. Also for example in the PixelExperience9 from this collection I was not even able to add my Google account because of the system auto-closing almost all system apps that I try to open.
It might be that these things should be done in a different way, but this is my experience for now. So..... back to Dr.Ketan ROM. I was really hoping to get the MIUI GSI as daily, but it seems impossible to me.
EDIT: Lol I realised we are the same people talking on the other thread also, so you gave me the link to the treble collection.

No TWRP for the Pixel 4 because of Android 10?

So it seems TWRP might be an issue getting it on our Pixel 4's.
According to @Dees_Troy, its a problem. Seems they don't even have one for the Pixel 3 on Android 10.
@Dees_Troy
"Pixel 4 is in real danger of not getting TWRP for a while after it's released due to all of the changes made in how recovery works in Android 10."
https://mobile.twitter.com/Dees_Troy/status/1171151359564890113

We'll see, fortunately we know we have a working magisk and that actually takes care of everything I do although I miss the convenience of TWRP, no question. The guy seems to work miracles so I wouldn't be surprised to see him figure it out. If not, I suppose I can only be thankful for everything he's done for us already and wish him luck in his next endeavor. I gotta be honest here, way back on windows phone I was surprised the door wasn't being closed on all this stuff. When Android came along it was like the wild west and I thought there was no way it could go on. Now we're here and iin many respects still having our way with our phone. It's been a pretty good ride.

krabman said:
We'll see, fortunately we know we have a working magisk and that actually takes care of everything I do although I miss the convenience of TWRP, no question. The guy seems to work miracles so I wouldn't be surprised to see him figure it out. If not, I suppose I can only be thankful for everything he's done for us already and wish him luck in his next endeavor. I gotta be honest here, way back on windows phone I was surprised the door wasn't being closed on all this stuff. When Android came along it was like the wild west and I thought there was no way it could go on. Now we're here and iin many respects still having our way with our phone. It's been a pretty good ride.
Click to expand...
Click to collapse
Yea, hopefully I pray he'll figure it out for sure.
Sent from my VS996 using Tapatalk

MicroMod777 said:
So it seems TWRP might be an issue getting it on our Pixel 4's.
According to @Dees_Troy, its a problem. Seems they don't even have one for the Pixel 3 on Android 10.
@Dees_Troy
"Pixel 4 is in real danger of not getting TWRP for a while after it's released due to all of the changes made in how recovery works in Android 10."
https://mobile.twitter.com/Dees_Troy/status/1171151359564890113
Click to expand...
Click to collapse
He will get it there is always a way

Damm that's not good.

Personally, I don't need recovery. My first pixel device and the last thing I want to do is flash some half baked custom ROM for it. Everything I need can be flashed through magisk or EXKM. As long as I can root, I'm good

I'll leave @Dees_Troy's full statement - dated 23rd October 2019 - given on the official TWRP website here as well:
Please note that this post is primary related to TWRP and the Pixel 3 and 4 and devices that may ship in the future that ship with Android 10 as their original version of Android. Older non-Pixel devices that shipped with older versions of Android and receive upgrades to Android 10 are not affected.
Long story short, TWRP support for Android 10 is going to take a while.
Android 10 brings about the largest changes to the way AOSP implements recovery since Google shifted recovery from C to C++ when they moved from Android 4.0 to 4.1 more than 7 years ago. A lot of components in AOSP recovery were moved into subfolders, which makes merging the latest changes into TWRP more time consuming. At least on the Pixel 3, the ramdisk that we use for recovery is now handling part of normal boot in addition to recovery, so we're not sure what the best way will be to go about replacing recovery without affecting the ability to boot up normally. In addition, the way Google is building the ramdisk on the Pixel 3 is a lot different than the past. In the past, the executable binaries in the ramdisk were built as static binaries with no linked libraries. TWRP has almost always been built with separate linked libraries. The new dynamically linked stock ramdisk will make it harder for us to slip TWRP into the ramdisk.
Once we get TWRP compiling with the new changes from 10, we have some additional items that need consideration. As mentioned above, the stock ramdisk is using dynamic linking. Unlike TWRP, the stock ramdisk places the executables and libraries in the usual locations inside a /system folder. Normally TWRP leaves /system alone so that we can mount the system partition to its usual location of /system. If we leave things the way they are on the Pixel 3, mounting the system partition gets tricky. A lot of custom zips depend on mounting the system partition to /system.
Android 10 also introduces a new dynamic partitioning system. Instead of having a dedicated system partition and a dedicated vendor partition, etc. Android 10 uses a super partition. I like to think of the super partition as a partition that contains a bunch of smaller partitions. One of the side effects of this dynamic partition system is that Google has chosen to use a form of the ext4 file system that is for all intents and purposes, read-only. This choice means that even if you wanted to, you can't easily mount and modify the system partition. We haven't really discussed this with other developers yet, but it may impact your ability to do things like install Gapps. In addition, the dynamic partition model means that eventually, we should probably provide you, the user, some GUI driven tools in TWRP to allow you to manage the dynamic partitions that are on the super partition.
On top of all of the above, I, Dees_Troy, am the one who usually handles merges of new versions of Android. My wife is currently pregnant with our fourth child. I am quite busy with my growing family and the need to find a bigger house, so my time for working on TWRP right now is somewhat limited. So, I guess please be patient, or feel free to download the TWRP source code and make the needed changes yourself.
Click to expand...
Click to collapse
Source: twrp.me
My guess is: we got to get familiar with manually patching boot images regarding Magisk, and maybe with flashin ROMs shipping as a GSI (Generic System Image). First time I made such an assumption was, when the first GSIs startet popping up in the respective section here on XDA, and I still guess that this is the way to go for future modding.

5m4r7ph0n36uru said:
I'll leave @Dees_Troy's full statement - dated 23rd October 2019 - given on the official TWRP website here as well:
Source: twrp.me
My guess is: we got to get familiar with manually patching boot images regarding Magisk, and maybe with flashin ROMs shipping as a GSI (Generic System Image). First time I made such an assumption was, when the first GSIs startet popping up in the respective section here on XDA, and I still guess that this is the way to go for future modding.
Click to expand...
Click to collapse
This has been known since before we even got our devices in hand, statement has been shared long ago... When it was new.

wrongway213 said:
This has been known since before we even got our devices in hand, statement has been shared long ago... When it was new.
Click to expand...
Click to collapse
Yes, I know. But I saw yet another thread about TWRP for Pixel on Android 10 popping up, which implies that this thread, as well as this information still isn't widely spread/known as of yet. Just wanted to prevent further TWRP threads popping up on Pixel 4 forums.
Sent from my Google Pixel 4 XL using XDA Labs

5m4r7ph0n36uru said:
Yes, I know. But I saw yet another thread about TWRP for Pixel on Android 10 popping up, which implies that this thread, as well as this information still isn't widely spread/known as of yet. Just wanted to prevent further TWRP threads popping up on Pixel 4 forums.
Click to expand...
Click to collapse
You can't prevent the inevitable. There's always going to some users who don't understand how to use Google or XDA search

GOOGLE Pixel 4XL (coral) - QQ1B.200105.004 - Android 10 . My same rig.
Any updates on TWRP?

kb5rir said:
GOOGLE Pixel 4XL (coral) - QQ1B.200105.004 - Android 10 . My same rig.
Any updates on TWRP?
Click to expand...
Click to collapse
No

Can you boot (not flash) to TWRP on the Pixel 4 XL? The only convenience I'll miss compared to my Pixel 2XL is being able to boot to TWRP and flash Magisk if so...

WorldOfJohnboy said:
Can you boot (not flash) to TWRP on the Pixel 4 XL? The only convenience I'll miss compared to my Pixel 2XL is being able to boot to TWRP and flash Magisk if so...
Click to expand...
Click to collapse
No, it's got to do with the dynamic partitions and mounting /system. From what I've read, even if you booted twrp it would no be functional.

I can only imagine the effects of this dynamic partition on other useful projects like microG...we have our work cut out for us here. I smell innovation!

Sharing a link to a mega-Dive with OxygenOS12 version41 prebuilt f2fs/ext4 Dualboots including major fix to run after OTA or anykinda oxygen12 install

hetres the link to my drive OxygenOS12 module-rom-twrp-MEGA-DRIVE
the reserve folder has a way to ensure any finuished oxygenos12 works
If anyone need help let me know

This looks really cool but it's a bit overwhelming. Could you explain how I can, for example, install one custom rom on slot A and oxygen os 12 on slot B?
Can I dual boot two custom roms or is only oxygen os supported?
Will security lock on one rom affect the other rom?
Is the twrp62 fully working and flashable with oxygen os v41?
Could I format data as f2fs for any custom rom too?

Epic028 said:
This looks really cool but it's a bit overwhelming. Could you explain how I can, for example, install one custom rom on slot A and oxygen os 12 on slot B?
Can I dual boot two custom roms or is only oxygen os supported?
Will security lock on one rom affect the other rom?
Is the twrp62 fully working and flashable with oxygen os v41?
Could I format data as f2fs for any custom rom too?
Click to expand...
Click to collapse
I got OxygenOS so done over I wrote some small flashbles and apps to do the work. I have no way to share a cloud drive with my build.s. youhave to split the userdata with a android OS 11 from orangefoxDualbbot here on xda 1st. You can run Window s if you want on one side and oxygenOS 12. or 11., 10 maybe 9 I dont know. heres pur dualboot OP7 telegram channel Orangfox-Dualboot-channel
I got Oxy12 licked. but like I said you need to cut the drive ewith arecovery in 11 becui;d my build doesent do that. sorry im newbee guy. but mine run busybox, magisk,toybox. lol and it dont car about if you ext4 or f2fs. onething to knwow if you dualboot you cant set a password anfd cant really run encryption on the userdata partiton. nice to meet you bro

Heres another link to my little apps https://mega.nz/file/PvwlFABY#BvFZp-Gp0_3I_DNa3dtXoDmImCq1a4AtJyMMH5izizE
- theres the APP TO put in a folder with a reserve.img from the OS. and be booted into a twrp like mine I share here
https://mega.nz/file/r6IyiZyK#b6x1cv1xh4YV_eFuPbB11viudZQXiFmD9raYxj4Wp54
PS. dont take TWRPs from just anyone I have messed up my lphone just over bad mountsa and stuff.
But I ripp and build stuff and kinds know my phone now. it';s my 3rd OP7PRO loll.
I lost the others tried a OP6 out but it lies so that thing sux. lol
Hey I got video of a 45 secont OTA install from a loaded OS video lol with\music and funny stuff.
more of a direct write no counting so it make it or not . but its a funtion lol

I liked learing OS12 they playing with little drives virtual stuff. that reserve.img is nthe actuall Oxygen12 OS. is links all the guts to everything esle. latley I've been mount it diffent and when it crash and still trys bpoot I just get a standered load of android OEM the probly started with. witch load nothing cusst it just a platform.
pretty much far as 12 for op7pros go, if your phone wont boot into the OS My reserve repatcher here will fix the proble but you know their other stuff to like encription apps modules mounts. but this builds OxygenOS12.