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.
Related
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.
Is this possible, Dual booting stock + custom rom?
bump
chandu4money said:
bump
Click to expand...
Click to collapse
Possibly. Android 10 gives dual booting functionality natively, as a way to give developers an easy way to test things on their phones within a clean sandboxed environment. So this could become an easy possibility. I suppose it depends how Android 10 ROMs are delivered to existing phones.
It could be how treble was introduced. New phones that came with 8 as new had to follow treble file system partitioning schemes, but older phones that upgraded to 8 didn't have to be treble compliant.
Android 10 sets out another new partitioning and file system scheme to enable the dual booting functionality.
I haven't looked into this so don't know the answer, but maybe it will be new phones that launch with 10 that can do this and old phones will be up to the manufacturer to decide if they adopt the new file system scheme when upgrading to 10.
Robbo.5000 said:
Possibly. Android 10 gives dual booting functionality natively, as a way to give developers an easy way to test things on their phones within a clean sandboxed environment. So this could become an easy possibility. I suppose it depends how Android 10 ROMs are delivered to existing phones.
It could be how treble was introduced. New phones that came with 8 as new had to follow treble file system partitioning schemes, but older phones that upgraded to 8 didn't have to be treble compliant.
Android 10 sets out another new partitioning and file system scheme to enable the dual booting functionality.
I haven't looked into this so don't know the answer, but maybe it will be new phones that launch with 10 that can do this and old phones will be up to the manufacturer to decide if they adopt the new file system scheme when upgrading to 10.
Click to expand...
Click to collapse
So anything yet?
How can I make dual boot?
I initially heard about the possibility here.
https://www.xda-developers.com/android-q-dynamic-android-aosp-gsi/
I remember, not long after, seeing discussions that this could be a potential way to allow dual booting for all. However this seems to have disappeared without a trace as I can't find anything relating to this in any later Android Q/10 announcements.
Even OnePlus 7 & 7 Pro got official recovery for dual booting...
Any progress on this? Couldn't find anything on Multirom either
karanpats said:
Any progress on this? Couldn't find anything on Multirom either
Click to expand...
Click to collapse
Unfortunately, not yet...
Isn't an a/b system required for dual booting? For example I remember it being possible on pixels because they have 2 partitions
IoIam said:
Isn't an a/b system required for dual booting? For example I remember it being possible on pixels because they have 2 partitions
Click to expand...
Click to collapse
Nope...
I remember it worked on my redmi note 4, which it has not an A/B based system...
I hope its coming soon
It was working perfectly in my old phone (poco f1)
It's nice to have stock and custom
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!
Hi ! I have juste my pixel 4a 5g two days new in teampixel now.
I come from oneplus & xiaomi to pixel.
I love it but they hadn't many features on settings ex: status bar remove some icons and center clock.
I have a question do you know when they had a Twrp for it ? And if I root it (Always root my devices for mods) no do format data ? And use remove force encryption ? Only unlock BL and flash boot.img ?
I hope there will be devs who will create mods eg: face id & kernel & custom rom.
Have a good day..
TWRP is going to be awhile due to issues with Pixel devices and the A/B boot system among other things. Patience here is going to be required especially for a newer Pixel device like the 4a 5G.
You can unlock the bootloader the same as you would any Pixel device. That means reboot into the bootloader, type "fastboot flashing unlock" and follow the steps to confirm the unlock. Keep in mind this wipes your device as a factory reset would.
As far as rooting the device, use the canary builds of Magisk to achieve this. Again, the rooting steps are the same as previous pixel devices requiring you to patch the boot.img from the factory image and then flash it via fastboot.
rspkt said:
TWRP is going to be awhile due to issues with Pixel devices and the A/B boot system among other things.
Click to expand...
Click to collapse
A/B has been pretty standard for like 5 years now. I had a nexus 6p, pixel xl, pixel 2xl - all A/B all have TWRP. Even the Pixel 4 is *officially* supported by TWRP now. https://twrp.me/google/googlepixel4xl.html
I've never had to wait this long to get an *UNofficial* working version.
mistermojorizin said:
Even the Pixel 4 is *officially* supported by TWRP now. https://twrp.me/google/googlepixel4xl.html
Click to expand...
Click to collapse
Considering the P4 (a phone released in September 2019) JUST got official support I guess it doesn't seem like that quick of a process to me?
OptoChip said:
Considering the P4 (a phone released in September 2019) JUST got official support I guess it doesn't seem like that quick of a process to me?
Click to expand...
Click to collapse
the p4 got officially supported. usually there's unofficial support pretty quickly.
the other thing i was just pointing out it's not the a/b system like the previous poster said.
Yes but they had many phone with A/B on Android 11 comes recently had Twrp "Oneplus" & "Xiaomi" yes is unofficial but works.
I tthink it's because they had more community.
WARNING
This device is an "advanced" tablet that requires a variety of commands and slightly advanced skills. If you don't know words like "adb", "fastboot", "QFIL" ,or "EDL V2 cable", we recommend avoiding customization and operating with ZUI. And I cannot guarantee any damage caused by reading this.
Legion Y700's Stock ROM, ZUI, initially did not support languages other than English and Chinese (I am Japanese) and there was some hassle with using GMS (the latest version, ZUI14, adds an option to use a Google account). So I therefore decided to use GSI to remedy this shortcoming to some extent.
I therefore decided to use GSI to remedy this shortcoming to some extent. This is the flashing process for nazim's crDroid GSI that I wrote about earlier, and the basics are still the same today.
①Unlock bootloader with SN.img. This procedure is the same as for other Lenovo tablets such as the Xiaoxin Pad, so I'll skip this step.
②Put the tablet in Fastboote"d" mode. I usually enter this mode by pressing and holding the volume down and the power button to activate fastboot mode, then selecting "Enter Fastboot" from the recovery menu.
③You have to download the arm64 version from the crDroid GSI link that the text my first post in this thread. I recommend arm64-BgN-vndklite.
④I will assume that you have already configured Android Studio. Start a command prompt and type the command fastboot flash system (the img file you downloaded and unzipped) You can also do this by dragging and dropping the img file into the window before flashing system.
⑤Operate the tablet; proceed to Enter recovery→Wipe data/factory reset to initialize the tablet's data. Otherwise, it will freeze at the title.
⑥Reboot system now and after a while crDroid will start.
Click to expand...
Click to collapse
I recommend crDroid for the following reasons.
This GSI is stable and has few crashes. Performance in games is also kept at a high level.
This GSI supports Face Unlock, which is important because the Y700 does not support fingerprint recognition.
Those who do not need facial recognition or do not want a landscape lock screen can try other ROMs such as LineageOS.
Android 13's GSI is also much more stable than earlier versions. I haven't used it yet because Lawnchair doesn't support it natively, but if you don't, I recommend this one as well. crDroid as well as Project Elixir, which is officially certified, seem to have good battery life.
By the way, there seems to be a problem with Android 13 GSI where "Face Unlock" does not work. However, I found a module called biometric-restore in Pixel Experience's Telegram Group.
It is also possible to return to ZUI by using QFIL.
https://smartasw.com/archives/15575
If Bricked by ROM flash, etc., it may be possible to use an EDL V2 cable (sold by Aliexpress, etc.) to make it ready to flash with QFIL.
I have a bit of writing to do, but I will end here. I will add more when I have more time.
These are perfotmance magisk module for Snapdragon 870
①Thermal Qualcomm 870 (recommended for v5.0)
②Adreno GPU Driver for SM8250 (need HuskyDG's overlayfs v1.13)
And now, Adreno 650 in the Snapdragon 870 is clock limited by Qualcomm to 683MHz. I would like to know if anyone knows how to unlock this.
FIERA03 said:
WARNING
This device is an "advanced" tablet that requires a variety of commands and slightly advanced skills. If you don't know words like "adb", "fastboot", "QFIL" ,or "EDL V2 cable", we recommend avoiding customization and operating with ZUI. And I cannot guarantee any damage caused by reading this.
Legion Y700's Stock ROM, ZUI, initially did not support languages other than English and Chinese (I am Japanese) and there was some hassle with using GMS (the latest version, ZUI14, adds an option to use a Google account). So I therefore decided to use GSI to remedy this shortcoming to some extent.
I therefore decided to use GSI to remedy this shortcoming to some extent. This is the flashing process for nazim's crDroid GSI that I wrote about earlier, and the basics are still the same today.
I recommend crDroid for the following reasons.
This GSI is stable and has few crashes. Performance in games is also kept at a high level.
This GSI supports Face Unlock, which is important because the Y700 does not support fingerprint recognition.
Those who do not need facial recognition or do not want a landscape lock screen can try other ROMs such as LineageOS.
Android 13's GSI is also much more stable than earlier versions. I haven't used it yet because Lawnchair doesn't support it natively, but if you don't, I recommend this one as well. crDroid as well as Project Elixir, which is officially certified, seem to have good battery life.
By the way, there seems to be a problem with Android 13 GSI where "Face Unlock" does not work. However, I found a module called biometric-restore in Telegram, so I share the link.
https://t.me/poncesgsi/98843
It is also possible to return to ZUI by using QFIL.
https://smartasw.com/archives/15575
If Bricked by ROM flash, etc., it may be possible to use an EDL V2 cable (sold by Aliexpress, etc.) to make it ready to flash with QFIL.
I have a bit of writing to do, but I will end here. I will add more when I have more time.
Click to expand...
Click to collapse
What do you mean by Project Elixir is officially certified?
gogitossj said:
What do you mean by Project Elixir is officially certified?
Click to expand...
Click to collapse
Project Elixir GSI is an "official" GSI because its maintainer, Mr. UGLYKID24, is certified by the Elixir development team. On the other hand, crDroid is an "unofficial" GSI because Mr. Nazim is not certified (Ancient OS, which is also certified under Nazim's ROM, is considered an official GSI).
FIERA03 said:
And now, Adreno 650 in the Snapdragon 870 is clock limited by Qualcomm to 683MHz. I would like to know if anyone knows how to unlock this.
Click to expand...
Click to collapse
I wonder if Konabess working for this
FIERA03 said:
These are perfotmance magisk module for Snapdragon 870
①Thermal Qualcomm 870 (recommended for v5.0)
②Adreno GPU Driver for SM8250 (need HuskyDG's overlayfs v1.13)
Click to expand...
Click to collapse
Hey FIERA03, I see you removed the LPDDR and Cache module. Did they have issue?
- can you show me how to install
"By the way, there seems to be a problem with Android 13 GSI where "Face Unlock" does not work. However, I found a module called biometric-restore in Pixel Experience's Telegram Group." ???
- No double taps, no lift to wake, always use the power button is not convenient
- thank you
Can I apply the Samsung ROM on the link to y700?
[CLOSED] One ui gsi to all samsung
updated 8 times One ui gsi to all samsung no boot loops all features are working now i'm using one ui 5 it's pretty fast For those who want, the best 3 game acceleration magisk modules are below, I've been using them for a long time, it's fine...
forum.xda-developers.com
you486jsm said:
Can I apply the Samsung ROM on the link to y700?
[CLOSED] One ui gsi to all samsung
updated 8 times One ui gsi to all samsung no boot loops all features are working now i'm using one ui 5 it's pretty fast For those who want, the best 3 game acceleration magisk modules are below, I've been using them for a long time, it's fine...
forum.xda-developers.com
Click to expand...
Click to collapse
I think the title said: to all samsung
Mrxyzl said:
제목에 이렇게 적혀 있었던 것 같아요: 모든 삼성에게.
Click to expand...
Click to collapse
I heard that this ROM can be installed and used on P11 and P12. Then, wouldn't it be possible on Y700? I don't have the skills, so I'm asking.
I can't seem to flash the system file, I get this error:
C:\Users\Mike\Desktop>fastboot flash system C:\Users\Mike\Desktop\crDroid-8.13-arm64_bgN-Unofficial.img
target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
I unlocked my bootloader using the "fastboot oem unlock-go" command because I couldn't get the SN.img file to work. It does show my bootloader as unlocked. Could this be my issue? Also, my tablet is 12GB 256GB, not sure if that changes which crDroid file I should flash...any help is greatly appreciated.
I figured it out, I was using an outdated version of fastboot. Downloaded this and worked like a charm!