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.
sorry if these are noob questions, however GSI's and custom roms confuse me, and I really don't want to brick my phone on accident
Preface:
I have a rooted moto g6 with an unlocked bootloader that supports project treble. as per getprop ro.treble.enabled running pie 29.55-24 Software channel Retail US
1. Can I flash a GSI on my phone
2. Where is there a good guide on how to flash a gsi
3. Will it factory reset my phone
4, Is there anything I should do beforehand
5. Are there any GSI's I can't flash
(What I think is 1:yes 2:If i knew i wouldn't be here 3:yes 4:backup system images 5: Yes
Thanks
Android Adam said:
sorry if these are noob questions, however GSI's and custom roms confuse me, and I really don't want to brick my phone on accident
Preface:
I have a rooted moto g6 with an unlocked bootloader that supports project treble. as per getprop ro.treble.enabled running pie 29.55-24 Software channel Retail US
1. Can I flash a GSI on my phone
2. Where is there a good guide on how to flash a gsi
3. Will it factory reset my phone
4, Is there anything I should do beforehand
5. Are there any GSI's I can't flash
(What I think is 1:yes 2:If i knew i wouldn't be here 3:yes 4:backup system images 5: Yes
Thanks
Click to expand...
Click to collapse
There are different types of treble devices you know. Only a couple GSI work on the g6.
GSI is a system image, so usually flash with fastboot.
Fastboot flash system system.img
Or in TWRP with the "install image" option.
The G6 does not have a b partition. So only try ones that say "arm A only". Meaning arm, not arm 64, and a - only, not a/b.
There is an entire section of this site devoted to it. Search "Project Treble". Without the quotes obviously
Here you go
https://forum.xda-developers.com/project-treble
Better yet here ya go
Built for the g6.
All GSIs are generic system images, so technically they can Flash on any device that has treble (with the correct CPU architecture and partitioning scheme) but when one gets built for your device most of the bugs have been worked out
madbat99 said:
There are different types of treble devices you know. Only a couple GSI work on the g6.
GSI is a system image, so usually flash with fastboot.
Fastboot flash system system.img
Or in TWRP with the "install image" option.
The G6 does not have a b partition. So only try ones that say "arm A only". Meaning arm, not arm 64, and a - only, not a/b.
There is an entire section of this site devoted to it. Search "Project Treble". Without the quotes obviously
Here you go
https://forum.xda-developers.com/project-treble
Better yet here ya go
Built for the g6.
All GSIs are generic system images, so technically they can Flash on any device that has treble (with the correct CPU architecture and partitioning scheme) but when one gets built for your device most of the bugs have been worked out
Click to expand...
Click to collapse
Thank you so much. I installed Lineage OS from https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029 and my phone is working HOWEVER I can't read battery usage from setting but /data/system/batterystats.bin exists
Android Adam said:
Thank you so much. I installed Lineage OS from https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029 and my phone is working HOWEVER I can't read battery usage from setting but /data/system/batterystats.bin exists
Click to expand...
Click to collapse
I would try the one I linked to. It is the most likely to have everything working. Descendant two dot two
The one you're trying to use says it's extremely specific to his device. Majorly buggy for others. Including A only devices.
Android Adam said:
Thank you so much. I installed Lineage OS from https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029 and my phone is working HOWEVER I can't read battery usage from setting but /data/system/batterystats.bin exists
Click to expand...
Click to collapse
Did you ever manage to get battery to work? Mine doesn't either nor does the USB-C port
Sorry I need help installing the ROM GSi RR I get an error in the text of insufficient space and I get error 70 to someone else happens? And I tried to fix the problem and when I managed to install the gapps the phone did not start someone can help me?
ACM1PT said:
Sorry I need help installing the ROM GSi RR I get an error in the text of insufficient space and I get error 70 to someone else happens? And I tried to fix the problem and when I managed to install the gapps the phone did not start someone can help me?
Click to expand...
Click to collapse
Please link to the rom so I can try to help. describe what you're trying to do
Android Adam said:
Please link to the rom so I can try to help. describe what you're trying to do
Click to expand...
Click to collapse
Could you give me a guide on how to install with gapps? Sorry I have to write in English everything I did my language is Spanish sorry
ACM1PT said:
Could you give me a guide on how to install with gapps? Sorry I have to write in English everything I did my language is Spanish sorry
Click to expand...
Click to collapse
I need to know which rom you are using. Please post a link to it. Is this it https://www.google.com/amp/s/forum....urrection-remix-v7-0-arm64-32-b-t3891636/amp/
Android Adam said:
I need to know which rom you are using. Please post a link to it. Is this it https://www.google.com/amp/s/forum....urrection-remix-v7-0-arm64-32-b-t3891636/amp/
Click to expand...
Click to collapse
Are you using Oreo or pie
Android Adam said:
Are you using Oreo or pie
Click to expand...
Click to collapse
pie bro,
I will try to install again have it happen
ACM1PT said:
pie bro,
I will try to install again have it happen
Click to expand...
Click to collapse
I found the problem. The system partition is too small so GApps always fails. To solve it go to twrp adb push your rom, and flash it. Then go to format then system hit repair then resize and confirm. Of you are flashing a big GApps (Super) do it again. Flash GApps then Magisk (for root) then you're done
Proof of concept - I've successfully booted my own LineageOS GSI on A60 (which is identical to M40 in terms of hardware); other PHH-based GSIs should work as well.
Procedure? Just pack your favorite ARM64 AB GSI image into a .tar and flash via Odin. It's that simple (to at least make it boot).
As far as I've discovered, bugs are 1) bad manual brightness behaviour (can be fixed similarly to this - the command to use here is "setprop persist.sys.phh.samsung_backlight 2"), 2) calls are always in speaker mode, 3) MTP is broken (can be fixed with a modified stock kernel in the future) and 4) no VoLTE as with all GSIs.
If you install one now, there's no navbar on boot, and statusbar doesn't account for the hole-punch either, but I've already submitted a device overlay to PHH, which should fit both A60 and M40. GSIs built afterwards should look better (like in the screenshot, where I already applied the overlay).
With no TWRP available, setup can be tough, but overall it's pretty refreshing to see AOSP-based stuff running on this device.
As a m40 user it sounds me great and left hope for my device.. looking foreword to it
dear AndyYan, could you provide links(to twrp and GSI themselves) or something?
sorry. no need of providing. I misunderstood
Great!
Great Work buddy. Hope you make progress and soon have a smooth GSI on your device :good:
AndyYan said:
Proof of concept - I've successfully booted my own LineageOS GSI on A60 (which is identical to M40 in terms of hardware); other PHH-based GSIs should work as well. .....
.....With no TWRP available, setup can be tough, but overall it's pretty refreshing to see AOSP-based stuff running on this device.
Click to expand...
Click to collapse
Hey, when im trying to flash with odin (AP), the app has just shutted down. What's the correct way to install?
Even tho, app for checking treble says me, that i have A-only while you say youve flashed AB
MediaNik said:
Hey, when im trying to flash with odin (AP), the app has just shutted down. What's the correct way to install?
Even tho, app for checking treble says me, that i have A-only while you say youve flashed AB
Click to expand...
Click to collapse
My bad, I forgot to mention that the image has to be renamed to system.img.ext4 before packaging.
We're A-only but system-as-root. Images for system-as-root are named AB for historical reasons.
AndyYan said:
My bad, I forgot to mention that the image has to be renamed to system.img.ext4 before packaging.
We're A-only but system-as-root. Images for system-as-root are named AB for historical reasons.
Click to expand...
Click to collapse
it is being flashed, but when it's done, it goes in download mod, displays small red exclamation mark and says "reason system: error validating footer"
MediaNik said:
it is being flashed, but when it's done, it goes in download mod, displays small red exclamation mark and says "reason system: error validating footer"
Click to expand...
Click to collapse
Then probably dm-verity kicking in (weird, how come when we've unlocked BL already).
I installed Magisk beforehand (patch AP), try it yourself.
Can you make please more detailed guide how to flash it
Because when I try, it gives me error
AndyYan said:
Proof of concept - I've successfully booted my own LineageOS GSI on A60 (which is identical to M40 in terms of hardware); other PHH-based GSIs should work as well.
Procedure? Just pack your favorite ARM64 AB GSI image into a .tar and flash via Odin. It's that simple (to at least make it boot).
As far as I've discovered, bugs are 1) bad manual brightness behaviour (can be fixed similarly to this), 2) calls are always in speaker mode, 3) MTP is broken (can be fixed with a modified stock kernel in the future) and 4) no VoLTE as with all GSIs.
If you install one now, there's no navbar on boot, and statusbar doesn't account for the hole-punch either, but I've already submitted a device overlay to PHH, which should fit both A60 and M40. GSIs built afterwards should look better (like in the screenshot, where I already applied the overlay).
With no TWRP available, setup can be tough, but overall it's pretty refreshing to see AOSP-based stuff running on this device.
Click to expand...
Click to collapse
can you please tell me how to do that?
deadinside322 said:
Can you make please more detailed guide how to flash it
Because when I try, it gives me error
Click to expand...
Click to collapse
tomznottomo said:
can you please tell me how to do that?
Click to expand...
Click to collapse
So slightly more details:
1) Make sure Magisk is properly installed (patch AP) and running on your device first, likely because we need it to disable dm-verity
2) Download any ARM64 AB GSI and rename the image (*.img) to system.img.ext4
3) Pack it into tar format (e.g. 7-zip)
4) Flash via Odin
5) Enter stock recovery and wipe data
I'm not too keen on showing the way because an official Android 10 update is around the corner (being intensively beta-tested in China), which could potentially fix the bunch of bugs in running GSIs (most critical being call audio).
AndyYan said:
So slightly more details:
1) Make sure Magisk is properly installed (patch AP) and running on your device first, likely because we need it to disable dm-verity
2) Download any ARM64 AB GSI and rename the image (*.img) to system.img.ext4
3) Pack it into tar format (e.g. 7-zip)
4) Flash via Odin
5) Enter stock recovery and wipe data
I'm not too keen on showing the way because an official Android 10 update is around the corner (being intensively beta-tested in China), which could potentially fix the bunch of bugs in running GSIs (most critical being call audio).
Click to expand...
Click to collapse
im noob bro can you give me your facebook or instagram please :<
@deadinside322 I see you're from 4PDA, greetings. The flashing process does not involve TWRP (we don't have one), which is admittedly unorthodox. What error did you encounter anyway?
BTW I've tried a few ways to port TWRP with no success. I wish you luck there, and don't forget to open-source if you do succeed.
tomznottomo said:
im noob bro can you give me your facebook or instagram please :<
Click to expand...
Click to collapse
Sorry, I'm not interested in step-by-step assistance. If you're new to this you ought to take some more time to research to prevent screwing up. I can help when you're in progress and hit actual problems.
AndyYan said:
@deadinside322 I see you're from 4PDA, greetings. The flashing process does not involve TWRP (we don't have one), which is admittedly unorthodox. What error did you encounter anyway?
BTW I've tried a few ways to port TWRP with no success. I wish you luck there, and don't forget to open-source if you do succeed.
Sorry, I'm not interested in step-by-step assistance. If you're new to this you ought to take some more time to research to prevent screwing up. I can help when you're in progress and hit actual problems.
Click to expand...
Click to collapse
Hello, I also tried to port TWRP three times already, it didn’t work out in any way.
The problem was that the firmware in Odin was infinitely loaded, and some simply did not want to boot.
Android 10 has released for both A60 (A6060ZCU1BTC9) and M40. I've switched to using it as base for GSIs, and it fixes the call speaker problem; other mentioned issues remain. The flashing process stays the same as well.
Changing firmware galaxy m40 to galaxy a60 open china
Hi, im using galaxy m40, if i flash the galaxy a60 firmware, my phone work or brick, has any one try that?
have anyone tried flasing android 12 gsi to m40?
So guyz since our redmi note 9 has a "Project treble" support,can we just directly flash any GSI custom rom from this link: https://forum.xda-developers.com/project-treble/trebleenabled-device-development ?! Or its still need a developer modification??
great question
In theory yes, but I had the experience of flashing only with the Adb commands and only on devices with "a only" slots it starts up but remember that the Redmi note 9 has two "a / b" slots so I flashed the other device and it asked me twrp and the file "copy partitions.zip" to start I suppose the same thing will happen on this device, we will wait, I can't test GSI on my note 9 because I have important information and I don't have time but I would already be making reports about it.
straikerxd said:
In theory yes, but I had the experience of flashing only with the Adb commands and only on devices with "a only" slots it starts up but remember that the Redmi note 9 has two "a / b" slots so I flashed the other device and it asked me twrp and the file "copy partitions.zip" to start I suppose the same thing will happen on this device, we will wait, I can't test GSI on my note 9 because I have important information and I don't have time but I would already be making reports about it.
Click to expand...
Click to collapse
Ah ok thx bro
Let me know if u managed to boot up a GSI rom on RN9 Merlin
MerlinTop1 said:
Ah ok thx bro
Let me know if u managed to boot up a GSI rom on RN9 Merlin
Click to expand...
Click to collapse
I Managed IT to boot 2 different gsis. Lineare OS 18 and caos Android 11. So i think GSI Roms are No Problem. But my Mobile Data was broken in gsis
I suggest you to keep on stock rom firmware only.
Root it with magisk. Flash it with twrp.
And everything is fine.
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
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!