Related
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.
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!
Does anyone have any ideas on how to flash a GSI to the Dynamic Super Partition? I've been trying for a month to flash DotOS and nothing. I can get it to flash using "fastboot flash super" but flashing to system it fails. Still doesn't boot regardless, even if I flash vbmeta and stock boot. I have no idea what I'm doing wrong.
phenomenalblaze said:
Does anyone have any ideas on how to flash a GSI to the Dynamic Super Partition? I've been trying for a month to flash DotOS and nothing. I can get it to flash using "fastboot flash super" but flashing to system it fails. Still doesn't boot regardless, even if I flash vbmeta and stock boot. I have no idea what I'm doing wrong.
Click to expand...
Click to collapse
When I was testing out GSI I used this method:
I would just change the rom name in .bat(?) File. Everything flashed and booted fine. The only issue I had with GSI roms & AT&T was that I couldn't get mobile service.
Better to stick with one of the many custom roms made for Pixel 4/XL. I mean I'd rather use something made for my device than something universal. Cool to try out new things though I get it. DotOS is not too much different than anything else.. DotOS has a different look, a different theme/ui.. I'm referring to DotOS Android 11. I used DOT on my OnePlus 6t, before I got my Pixel 4XL. I'll see what I can find about what you are talking about here and if and when I do find some good reads I'll return and link to them in this same post. I would definitely search high and low and look around in PHH's GSI notes and see what all is in them about this sort of thing. How are you doing your install? What is your installation process step by step?
I haven't used a GSI since my Motorola phones a few years ago but I remember depending on what device installation varies. I'll see if I can locate anything and link it here and tag you if I do. Cheers.
Edit added: Turns out DotOS devs revamped the new Android 12 theme engine and plan on releasing it once they drop v5 2 of their DotOS rom!! Maybe someone will compile DotOS. I plan on getting another better laptop in six months. If it's not available for us then I'll take a few cracks at it and if I'm successful I'll first get permission from DotOS and show them what I have and if they okay it I'll post some Pixel 4XL coral builds. But that will be six to nine months away from now. Times are hard. May happen sooner..
@phenomenalblaze I found a tool thats supposedly made for this sort of thing here:
I'm usually not HUGE on using toolkits on Android because you don't learn anything that way you know. .But figured I'd share.
Have never needed to install a GSI before but as we're kind of stuck here without a single custom ROM, I thought I'd have a look.
AFAIK installing one of these would still leave the door open for stock recovery to be used should something go wrong, so as long as you've made a back up it should be fine.
I'm just curious as to the method of installation?
Has anyone had any experience with GSI ROMs before.
How was it? Did it work?
Would DSU image loader be an option?
I've attached what treble version we have and the relevant info required from the treble info app.
Apparently we have VNDK compatibility, not sure what that is but we have it.
Hi @dladz, I ran into a similar question three years ago when I bought a Xiaomi Mi 8 Pro. I was so used to using custom ROMs that I didn't even check before I bought it whether any custom ROMs would be available.
I was honestly shocked to see that that wasn't the case - there was absolutely NOTHING available - and that I had ended up with a device that couldn't even be unlocked right away, you had to wait and open a Mi account to be allowed to unlock it. I couldn't believe it at the time, I had come from a OnePlus X and had helped others root and install custom ROMs on other OnePlus phones without any problems, so I felt like I had just thrown quite some money out the window to run around with a mobile Chinese Spyware gadget I didn't want to use.
That was the first time I ever came across the term GSI ROM and it took me several weeks to figure out how to flash a ROM that I could also use afterwards. I knew I wouldn't want to have a stock ROM by a company that has very loose data privacy standards and even clearly states they collect your data (Lesson learned, I thought, I just had to buy a "proper" phone again and no more phones from budget manufacturers).
Several weeks later, after I had finally managed to get a custom GSI ROM working on my device I posted a lengthy how-to here on XDA.
Again, it took me weeks to get everything to work that I could not go without. And even then, I had to resign to the fact that many features of the phone would not be working (The fingerprint sensor, for example. Also, the Xiaomi Mi stock rom apparently had excellent GPS support (dual GPS support) but GPS positioning is just alright on the GSI ROM I'm using, also there were many cool Xiaomi apps like a compass app that wouldn't work outside MIUI). But I was more than happy I had gotten different GSI ROMs to work in the end and settled on one that I could live with, knowing my phone wouldn't be sending data to some Chinese servers constantly.
Now that the Mi 8 Pro has become a bit slower over time with all the latest apps, I took the plunge and spent a ton of money on the OnePlus 10 Pro 256 GB version only to be disappointed again, but this time by a company that used to be the epitome of openness when it came to custom development.
I got my OnePlus 10 Pro on release in my region in April, together with the 50W wireless charger and both have been sitting here since April, I'm not touching that phone until I can remove all the Spyware it comes installed with. At this stage, I'm not yet willing to go through the weeklong trial-and-error again that it took to get the Mi 8 Pro running a custom GSI ROM (also considering that some of its features never worked...), but if OnePlus doesn't get its **** together soon with the MSM tool and some openness towards developers, I will seriously just consider selling it on eBay again (It is brandnew after all) and will never buy another phone from OnePlus again. This has been an extreme disappointment and I'm still struggling to understand why they wouldn't support custom development any more. I had checked the OnePlus 9 Pro threads on XDA just to see if there's still custom development going on for OnePlus and it seemed everything was still OK, but now... .
On a more positive note: The Mi 8 Pro did eventually get some custom ROM love and there are now several ROMS to choose from, so to answer your original question - If you ask me, don't bother with GSI ROMs until we can be sure there won't be any custom ROMs for our phone. I'm still hoping that will be the case.
Gsi will work but no fingerprint or faceunlock.
Installing is easy just reboot to fastbootd open device with fastboot enchanted and delete all _cow files and reboot too bootloader flash stock vbmeta with
"fastboot --disable-verity --disable-verification vbmeta vbmeta"
Download gsi that you like and flash it in fastbootd using "fastboot flash system gsi.img"
MrScarl3t said:
Gsi will work but no fingerprint or faceunlock. And many more visual glitches.
Installing is easy just reboot to fastbootd open device with fastboot enchanted and delete all _cow files and reboot too bootloader flash stock vbmeta with
"fastboot --disable-verity --disable-verification vbmeta vbmeta"
Download gsi that you like and flash it in fastbootd using "fastboot flash system gsi.img"
Click to expand...
Click to collapse
Well... I tried GSI and some steps and sure enough I broke my phone (hard brick) so now I'm on Google 6 pro
MrScarl3t said:
Gsi will work but no fingerprint or faceunlock.
Click to expand...
Click to collapse
Unless someone posts a step-by-step guide with screenshots of a successful flash, I wouldn't believe anything.
This sounds more like it:
Twiggy000b said:
Well... I tried GSI and some steps and sure enough I broke my phone (hard brick) so now I'm on Google 6 pro
Click to expand...
Click to collapse
It took me weeks going back and forth, going back to stock and retrying again before I had any luck at all with my Mi 8 Pro.
Theoretically, it should work, but you can easily hard-brick your phone if you take one wrong turn and then goodbye to a phone with a premium price tag and no open MSM tool available... .
yo-less said:
It took me weeks going back and forth, going back to stock and retrying again before I had any luck at all with my Mi 8 Pro.
Theoretically, it should work, but you can easily hard-brick your phone if you take one wrong turn and then goodbye to a phone with a premium price tag and no open MSM tool available... .
Click to expand...
Click to collapse
Yeah was not happy said screw it and went back to google at least ive got lineage os now lol but still what a waste of 1k
Twiggy000b said:
Yeah was not happy said screw it and went back to google at least ive got lineage os now lol but still what a waste of 1k
Click to expand...
Click to collapse
Did you try sending it in?
I'll make a guide just like I did with the Xiaomi 11t pro. Post it within a week
Already did it when I got the device but I use the fingerprint alot so not for me.
Only tricky is reflashing system when you want to go for stock again.
nah i reached out and oneplus never got back to me.
sorry to hear that :/
Twiggy000b said:
Well... I tried GSI and some steps and sure enough I broke my phone (hard brick) so now I'm on Google 6 pro
Click to expand...
Click to collapse
What phone was you on mate??
MrScarl3t said:
I'll make a guide just like I did with the Xiaomi 11t pro. Post it within a week
Already did it when I got the device but I use the fingerprint alot so not for me.
Only tricky is reflashing system when you want to go for stock again.
Click to expand...
Click to collapse
That would be great, I'll be your test subject, I can live without fingerprint and face unlock.
Think the camera might be a bit meh but maybe I can live with that.
Another odd thing is I got treble check and it said I cannot use treble ROMs?
No idea if that's true but that's what the app said.
dladz said:
That would be great, I'll be your test subject, I can live without fingerprint and face unlock.
Think the camera might be a bit meh but maybe I can live with that.
Another odd thing is I got treble check and it said I cannot use treble ROMs?
No idea if that's true but that's what the app said.
Click to expand...
Click to collapse
Yeah camera is gcam but the main sensor is fine with it.
Every OnePlus 10 pro works with gsi, and general boot images as well. I will start tomorrow making the guide.
Will test if you can use rollback zip to get back to stock
Here you go https://forum.xda-developers.com/t/how-to-flash-a-gsi-on-oneplus-10-pro-t.4479429/
MrScarl3t said:
Here you go https://forum.xda-developers.com/t/how-to-flash-a-gsi-on-oneplus-10-pro-t.4479429/
Click to expand...
Click to collapse
Legend
Hello Guys!
I'm thinking to install GSI ROM on my Redmi note 12 pro 5G. I have some experience with custom ROM flashing in TWRP. As far as I know there's no TWRP recovery available for my phone!
Can I flash GSI ROM with Fastboot mode in my device?
If you have experience or some guide for me to Flash GSI, please could you tell me?
And I don't familiar with those terms in GSI ROM name so I'm afraid that I would brick my device or some would go wrong.
I'm planning to flash AOSP 12.1 v416 by PHH or Android 13 Project Elixir.
Redmi note 12 pro should be similar close to Note 10, an A/B device with dynamics partitions
Read here, just find the appropriate GSI image and everything else specific for Note 12 pro
[GSI][PHH][13] Guide & Support [Mojito][Sunny]
Why should I use a GSI ? Mojito already have custom ROMs ¯\_(ツ)_/¯ Yes. But this thread exists due to the following reasons: You don't wanna fear about devs stop shipping updates. You don't wanna re-flash your custom recovery / kernel after each...
forum.xda-developers.com
x3r0.13urn said:
Redmi note 12 pro should be similar close to Note 10, an A/B device with dynamics partitions
Read here, just find the appropriate GSI image and everything else specific for Note 12 pro
[GSI][PHH][13] Guide & Support [Mojito][Sunny]
Why should I use a GSI ? Mojito already have custom ROMs ¯\_(ツ)_/¯ Yes. But this thread exists due to the following reasons: You don't wanna fear about devs stop shipping updates. You don't wanna re-flash your custom recovery / kernel after each...
forum.xda-developers.com
Click to expand...
Click to collapse
i think there is no twrp for this device yet but i think it is fine to just flash gsi.
keithsze001 said:
i think there is no twrp for this device yet but i think it is fine to just flash gsi.
Click to expand...
Click to collapse
True, you won't need twrp or any recovery at all to flash gsi.
Step to flash twrp/recovery is optional if you want to get rooted because fastboot doesn't have sideload function. Unless you go for KernelSU, it's a different topic.
Nowadays twrp function starts to decease, unless you need to dump/backup partition without root. I use included recovery from rom for A/B dynamic device
Thanks for the info, I haven't flashed GSI yet. does anyone know any working well rom or recommend ROM for Ruby except MIUI. I will leave my experience after I flashed GSI.Hope some rom for this device will come out!
Xenolast said:
Thanks for the info, I haven't flashed GSI yet. does anyone know any working well rom or recommend ROM for Ruby except MIUI. I will leave my experience after I flashed GSI.Hope some rom for this device will come out!
Click to expand...
Click to collapse
I am looking forward to hear your experience on gsi !
Please let us know if you find any particular stable rom for this device.
piyush_duggal said:
Please let us know if you find any particular stable rom for this device.
Click to expand...
Click to collapse
I bet if the buyers smart enough, they'll mostly will pass buying this. The price is closer to almost a mint second hand of Poco F4, offering almost better in everything except for maybe the main sensor (ov64b vs. imx766). And here we are Poco F4 has already a headstart in custom rom community.
And if you're willing to let go the OIS, Poco F3 isn't that bad either, price nowadays should be the same, its only disadvantages are slower charging and again, main sensor (imx586 vs imx766).
And the last, not to mention that Poco F5 is just around the corner... That should put some coffin nails to Redmi note 12 Pro.
x3r0.13urn said:
I bet if the buyers smart enough, they'll mostly will pass buying this. The price is closer to almost a mint second hand of Poco F4, offering almost better in everything except for maybe the main sensor (ov64b vs. imx766). And here we are Poco F4 has already a headstart in custom rom community.
And if you're willing to let go the OIS, Poco F3 isn't that bad either, price nowadays should be the same, its only disadvantages are slower charging and again, main sensor (imx586 vs imx766).
And the last, not to mention that Poco F5 is just around the corner... That should put some coffin nails to Redmi note 12 Pro.
Click to expand...
Click to collapse
the phone is just released, how could you put the nail? we haven't seen any development for this phone yet.
try Pixel Experience GSI: https://github.com/ponces/treble_build_pe/releases
groovepeppy said:
the phone is just released, how could you put the nail? we haven't seen any development for this phone yet.
Click to expand...
Click to collapse
What I said was: if you're looking for a particular good phone with a good custom roms support, and if you want it now, or very quickly from now, Poco F4 is already here, and its price is very close to Note 12 Pro with same feature and even more potent SoC. And if custom roms in Poco F4 aren't adequate, there's also Poco F3, its community is more active than F4, new one old stock F3 should be priced similar to Note 12 Pro, only if you're willing to loose the fast 67w charger and OIS in Note 12 Pro.
But if you still want Note 12 Pro with custom rom... Well, that's up to you. I didn't say it wouldn't see any custom rom, it just... looks less interesting than the others two.
Redmi Note 8 Pro is the most active for MTK device as far as I know, and for more two years consecutive after its release, it was ridden by a lot of issues. It was ironed out very lately, just after A12 out, and sadly most people has already moved out. Another one was Redmi Note 9 and Redmi 9, merlin and lancelot, again, most their roms stay on A11 firmware because latest A12 firmware gives a lot of headache. I've seen some development on Note 10s (evoX) and Poco M4 Pro (ported roms?), which those are MTK, but again, they're very slow and they had been released earlier than Note 12 Pro, but to be honest, those devices didn't bring the same attractive to Note 12 Pro.
If those aren't providing enough for arguments... Its closest rival is their own Poco X5 Pro, which again uses more common and widespread soc in custom rom community, the SD 778g, which it has some development on similar device such Mi 11 Lite 5g. Xiaomi 12 Lite also uses SD 778g, still hasn't seen any development yet.
tl;dr: there are many xiaomi devices, even the "flagship" Xiaomi 12 or Xiaomi 12 Pro, has yet seen any custom roms. I'd say: stick to existing community or any "its looks more guaranteed to be supported by community" devices rather than hoping this one would have one in the future.
x3r0.13urn said:
What I said was: if you're looking for a particular good phone with a good custom roms support, and if you want it now, or very quickly from now, Poco F4 is already here, and its price is very close to Note 12 Pro with same feature and even more potent SoC. And if custom roms in Poco F4 aren't adequate, there's also Poco F3, its community is more active than F4, new one old stock F3 should be priced similar to Note 12 Pro, only if you're willing to loose the fast 67w charger and OIS in Note 12 Pro.
But if you still want Note 12 Pro with custom rom... Well, that's up to you. I didn't say it wouldn't see any custom rom, it just... looks less interesting than the others two.
Redmi Note 8 Pro is the most active for MTK device as far as I know, and for more two years consecutive after its release, it was ridden by a lot of issues. It was ironed out very lately, just after A12 out, and sadly most people has already moved out. Another one was Redmi Note 9 and Redmi 9, merlin and lancelot, again, most their roms stay on A11 firmware because latest A12 firmware gives a lot of headache. I've seen some development on Note 10s (evoX) and Poco M4 Pro (ported roms?), which those are MTK, but again, they're very slow and they had been released earlier than Note 12 Pro, but to be honest, those devices didn't bring the same attractive to Note 12 Pro.
If those aren't providing enough for arguments... Its closest rival is their own Poco X5 Pro, which again uses more common and widespread soc in custom rom community, the SD 778g, which it has some development on similar device such Mi 11 Lite 5g. Xiaomi 12 Lite also uses SD 778g, still hasn't seen any development yet.
tl;dr: there are many xiaomi devices, even the "flagship" Xiaomi 12 or Xiaomi 12 Pro, has yet seen any custom roms. I'd say: stick to existing community or any "its looks more guaranteed to be supported by community" devices rather than hoping this one would have one in the future.
Click to expand...
Click to collapse
You got the point, you are right. MTK are very slow in development.
I've flashed 2 GSI ROM (Acient OS, Project Elixir) today.
For somehow, I can't flash vbmeta because it made phone to bootloop when I tried to go fastboot on cmd. Project Elixir is lastest version and it have this strange bug that can't connect to internet via wifi even with VPN and DNS Change. Everything is working fine.
But those two ROM have same issue sharing that's brightness can't be decrease or increase and Screen is flickering in every 5 sec or so.
I didnt test camera with GCam since I've to prepare for my work trip. I may write more later about them.
Xenolast said:
I've flashed 2 GSI ROM (Acient OS, Project Elixir) today.
For somehow, I can't flash vbmeta because it made phone to bootloop when I tried to go fastboot on cmd. Project Elixir is lastest version and it have this strange bug that can't connect to internet via wifi even with VPN and DNS Change. Everything is working fine.
But those two ROM have same issue sharing that's brightness can't be decrease or increase and Screen is flickering in every 5 sec or so.
I didnt test camera with GCam since I've to prepare for my work trip. I may write more later about them.
Click to expand...
Click to collapse
Do you succeed to flash Elixir?? if yes can you share your exact way of flashing...I have bootloop on MI logo..I flashed at least 15 times with different setup without success..thanks
Xenolast said:
I've flashed 2 GSI ROM (Acient OS, Project Elixir) today.
For somehow, I can't flash vbmeta because it made phone to bootloop when I tried to go fastboot on cmd. Project Elixir is lastest version and it have this strange bug that can't connect to internet via wifi even with VPN and DNS Change. Everything is working fine.
But those two ROM have same issue sharing that's brightness can't be decrease or increase and Screen is flickering in every 5 sec or so.
I didnt test camera with GCam since I've to prepare for my work trip. I may write more later about them.
Click to expand...
Click to collapse
Please try this, maybe it's a mediatek related GSI issue https://forum.xda-developers.com/t/gsi-13-lineageos-20-light.4509315/post-87620773
it seems that MIUI 14 cause big problems to flash GSI.. A downgrade to MIUI 13 can solve it
rayman95 said:
it seems that MIUI 14 cause big problems to flash GSI.. A downgrade to MIUI 13 can solve it
Click to expand...
Click to collapse
I did flash with MIUI 14 and successfully.
I erase user data,system,cache and A/B partition too.
I would use them if I have time to solve all the problem for myself and I think it's usable as daily rom.
The only problem I face is I can't flash vbmeta and it cause me bootloop to fastboot.
And important things is if you are in fastboot mode, phone screen show as FASTBOOTD
if not you are still in bootloader.
I use
Fastboot getvar is-userspace
Before
Fastboot boot fastboot
Xenolast said:
I did flash with MIUI 14 and successfully.
I erase user data,system,cache and A/B partition too.
I would use them if I have time to solve all the problem for myself and I think it's usable as daily rom.
The only problem I face is I can't flash vbmeta and it cause me bootloop to fastboot.
And important things is if you are in fastboot mode, phone screen show as FASTBOOTD
if not you are still in bootloader.
I use
Fastboot getvar is-userspace
Before
Fastboot boot fastboot
Click to expand...
Click to collapse
Can you share your exact way to flash please. I don't want to erase one more time my device....for nothing and flash again miui...thanks
Xenolast said:
I did flash with MIUI 14 and successfully.
I erase user data,system,cache and A/B partition too.
I would use them if I have time to solve all the problem for myself and I think it's usable as daily rom.
The only problem I face is I can't flash vbmeta and it cause me bootloop to fastboot.
And important things is if you are in fastboot mode, phone screen show as FASTBOOTD
if not you are still in bootloader.
I use
Fastboot getvar is-userspace
Before
Fastboot boot fastboot
Click to expand...
Click to collapse
That doesn't sound as a working solution.
Your are writing .... If I have time to solve all the problem for myself ....
So what does that mean ?
And .....
I erase user data,system,cache and A/B partition too......
is also stupid. In a and b slots are the boot, vbmeta, system_vbmeta. So if you erased a and b slots, it can't boot without boot partition.
rayman95 said:
Can you share your exact way to flash please. I don't want to erase one more time my device....for nothing and flash again miui...thanks
Click to expand...
Click to collapse
I'm back from my trip and I will comment here my process and screenshots. I'm redownloading all tools and rom to my pc.
I'm one of the end user and I'm sorry if I confused you all with unclear method but I will try to describe every step I did.
I'm finding solution for screen flickering, auto brightness issue and no internet connection error.