Related
Hi friends, so there's a lot about installing gsi images on various phones that support project treble but i cannot find anything about how you update them. I installed OmniRom beta3, via fastboot, on my H9L and 3 days later they put out an update. The rom works fine and i set it up to my preference with magisk and it even shows up as Play certified, so all is good. However, with the update I prefer not to go through the whole magisk uninstall/install again. Anyone here knows how you would update an existing gsi images ? If I use fastboot to load the new update wouldn't that erase everything again, as stated on the openkirin.net installation instructions ? or could i jsut fastboot the new beta3.1 over beta3 and just not do a factory reset as recommended ?
Weird everyone writes about installation and no one things about updates ?
thanks.
xzyk said:
Hi friends, so there's a lot about installing gsi images on various phones that support project treble but i cannot find anything about how you update them. I installed OmniRom beta3, via fastboot, on my H9L and 3 days later they put out an update. The rom works fine and i set it up to my preference with magisk and it even shows up as Play certified, so all is good. However, with the update I prefer not to go through the whole magisk uninstall/install again. Anyone here knows how you would update an existing gsi images ? If I use fastboot to load the new update wouldn't that erase everything again, as stated on the openkirin.net installation instructions ? or could i jsut fastboot the new beta3.1 over beta3 and just not do a factory reset as recommended ?
Weird everyone writes about installation and no one things about updates ?
thanks.
Click to expand...
Click to collapse
Good question mate. Since you're on omni I rom do you think it's better than ressuruction remix?
Fredin_ said:
Good question mate. Since you're on omni I rom do you think it's better than ressuruction remix?
Click to expand...
Click to collapse
for me, yes, because one of the most important feature i need is safetynet to pass. Omni was easier to get it to pass safetynet checks (via magisk) then RR. I also like the way Omni implemented the dark theme, obviously all of these are just preferences both roms are good daily drivers.
UPDATE: so i fastbooted the updated img file with stock recovery and did not do any wipes. All was fine including root and certification.
xzyk said:
for me, yes, because one of the most important feature i need is safetynet to pass. Omni was easier to get it to pass safetynet checks (via magisk) then RR. I also like the way Omni implemented the dark theme, obviously all of these are just preferences both roms are good daily drivers.
UPDATE: so i fastbooted the updated img file with stock recovery and did not do any wipes. All was fine including root and certification.
Click to expand...
Click to collapse
Good to hear that you updated successfully. I also love the theme engine in Omni rom but had to switch to stock for the camera
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?
Hi guys, I've dug around the forums everywhere in the internet for very long time, and found out that there is actually custom roms which will work on our devices, with fingerprint working (the only reason why I'm still on stock rom)
So basically there is a cool guy called phhusson which does aosp treble in which he make fixes and patches for all kind of devices, and to our luck it looks like he already did a fix for our fingerprint half year ago
Here is an issue in which we can see that fingerprint specifically for our devices was already fixed
https://github.com/phhusson/treble_experimentations/issues/1370
Here is where you can get the original Phh aosp treble (his work)
GitHub - phhusson/treble_experimentations: Notes about tinkering with Android Project Treble
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Here is lineage os 18.1 based on his(Phh) aosp treble, which means fingerprint there should be working too
[UNOFFICIAL] LineageOS R Mod //LiR
L i R < Your warranty is now void! > We're not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in...
forum.xda-developers.com
P.S: I'm not developer and did not take any part in development of roms in link above, also I do not take any responsibility for your device, shall something happen to it, I'm just a guy trying to people who has been stuck on stock rom (only because of God **** Fingerprint and uncertainty if custom rom from device forum will be receiving any update)
Let me know if anyone tries the lineage os in the link above and if everything is working
It was a bit complicated but I got it working. I have not tested the fingerprint reader which is what you are concerned about but the ROM works without any obvious issues.
TWRP was flashed with Odin after I flashed stock firmware. I used ianmacd's TWRP to flash the GSI. I had to use faizauthar12's BUB5 kernel to get past the stuck LineageOS logo.
This thread for how to make the GSI usable for TWRP: https://forum.xda-developers.com/t/...ung-galaxy-a51-super-partition-image.4216083/
Adding system.img to the zip file instead of creating a new zip file seemed to work better. Multidisabler fork with encryption appears to work.
Hope that helps anyone.
After instaling the .img i ended up with a samsung bootloop
and installing the img using the zip method literally did nothing so yeah
2344534574542433237923447 said:
It was a bit complicated but I got it working. I have not tested the fingerprint reader which is what you are concerned about but the ROM works without any obvious issues.
TWRP was flashed with Odin after I flashed stock firmware. I used ianmacd's TWRP to flash the GSI. I had to use faizauthar12's BUB5 kernel to get past the stuck LineageOS logo.
This thread for how to make the GSI usable for TWRP: https://forum.xda-developers.com/t/...ung-galaxy-a51-super-partition-image.4216083/
Adding system.img to the zip file instead of creating a new zip file seemed to work better. Multidisabler fork with encryption appears to work.
Hope that helps anyone.
Click to expand...
Click to collapse
can you specify how exactly did you install the gsi?
AirAustin said:
can you specify how exactly did you install the gsi?
Click to expand...
Click to collapse
I used the zip method. Renamed the GSI .img file to system.img and put it in the right directory in the zip file. You have to use the tool I linked for TWRP to read the GSI. I flashed the zip through TWRP.
2344534574542433237923447 said:
I used the zip method. Renamed the GSI .img file to system.img and put it in the right directory in the zip file. You have to use the tool I linked for TWRP to read the GSI. I flashed the zip through TWRP.
Click to expand...
Click to collapse
I had to use another ZIP method with twrp to get lineage os to work. And the fingerprint isn't working properly. It's really bugged.
AirAustin said:
I had to use another ZIP method with twrp to get lineage os to work. And the fingerprint isn't working properly. It's really bugged.
Click to expand...
Click to collapse
There's a setting for Samsung in the Phh Treble Settings for the broken fingerprint reader. It might work
2344534574542433237923447 said:
There's a setting for Samsung in the Phh Treble Settings for the broken fingerprint reader. It might work
Click to expand...
Click to collapse
Can you send a screen shot of the settings and check if it works? I no longer have the GSI on my phone
AirAustin said:
Can you send a screen shot of the settings and check if it works? I no longer have the GSI on my phone
Click to expand...
Click to collapse
There seems to be no difference with it on or off. It's not working
I see that it's not working out for other people, sorry for late answer, so anyway moderators feel free to delete this post, as for everyone else feel free to try this urself and experiment a bit, Good luck
its cool that you have fod fixed but does face unlock work as well. I have used a couple of gsis and roms that are not one ui based and i found that aosp face unlock works much better than one ui
MariyanGOD said:
its cool that you have fod fixed but does face unlock work as well. I have used a couple of gsis and roms that are not one ui based and i found that aosp face unlock works much better than one ui
Click to expand...
Click to collapse
It should work, like any gsi
raftomas88 said:
It should work, like any gsi
Click to expand...
Click to collapse
have you tried booting it?
just tried it and the fod doesnt work
RFS3000 said:
just tried it and the fod doesnt work
Click to expand...
Click to collapse
you have to use q vendor for it to work
MariyanGOD said:
you have to use q vendor for it to work
Click to expand...
Click to collapse
Can you link it?
I've collected all files necessary to root and recover (if necessary) the OnePlus 10 Pro with Android 13 Update - NE2211_11_C.21
( Firmware pulled from Oxygen Updater App)
Please note: Root at your own risk.
I'm not liable for any bricked device or issues possibly created from this process.
Stock Boot.zip
magisk_patched-NE2215_11_C.21.zip
Magisk-25.2.apk
stock.recovery.zip
NE2215_11_C.21 Stable (full).zip
Feel free to follow along using this guide:
How to root your Android smartphone: Google, OnePlus, Samsung, Xiaomi, and others too!
If flashing/rooting errors out, and you end up in Qualcomm Crash Dump Mode, please perform the following:
Restart into Fastboot Mode by holding Volume Down + Power buttons until the device vibrates, then release only the power button
Once in Fastboot mode, try flashing a clean boot and recovery to BOTH slots like this :
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
Follow the steps on this site to Flash the stock ROM above using the Fastboot Enhance Tool
https://www.droidwin.com/flash-stoc...-brick/#STEP_1_Download_Fastboot_Enhance_Tool
Feel free to download Fastboot Enhance Tool.zip (backup location)
If you have trouble rebooting to FastbootD (Recovery)
Try swapping Active slots from the application (typically slot A worked for me)
Choose reboot to FastbootD
Sorry if this is a stupid question, but is this to be used when the OP 10 Pro is ALREADY on OS 13, or is this to be used when the unit is on OS 12 (not yet rooted) and you want to take it to OS 13?
Thanks for your help.
Either or would be fine.
It's an upgrade using a full OTA update.
Hi. Is there any oneplus 10 pro compatible twrp? I could not find.
eren15935 said:
Hi. Is there any oneplus 10 pro compatible twrp? I could not find.
Click to expand...
Click to collapse
Not yet, but once I find one I'll upload it ASAP for the community.
Savio Dantes said:
Not yet, but once I find one I'll upload it ASAP for the community.
Click to expand...
Click to collapse
thanks. It would be nice. good work.
Hi there, do you have for C.22?
Savio Dantes said:
Not yet, but once I find one I'll upload it ASAP for the community.
Click to expand...
Click to collapse
There is...check this out
(Guide) Install TWRP + Root + Install Magisk + Bypass Safetynet
Please note, the TWRP image used IS NOT the official TWRP image. I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me. Warning As stated by @beatbreakee , do not flash...
forum.xda-developers.com
(Guide) Install TWRP + Root + Install Magisk + Bypass Safetynet
Please note, the TWRP image used IS NOT the official TWRP image. I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me. Warning As stated by @beatbreakee , do not flash...
forum.xda-developers.com
eren15935 said:
Hi. Is there any oneplus 10 pro compatible twrp? I could not find.
Click to expand...
Click to collapse
Hi. Is there any oneplus 10 pro compatible twrp? I could not find.
linhdanstore said:
Hi. Is there any oneplus 10 pro compatible twrp? I could not find.
Click to expand...
Click to collapse
Literally look above.
Savio Dantes said:
I've collected all files necessary to root and recover (if necessary) the OnePlus 10 Pro with Android 13 Update - NE2211_11_C.21
( Firmware pulled from Oxygen Updater App)
Please note: Root at your own risk.
I'm not liable for any bricked device or issues possibly created from this process.
Stock Boot.zip
magisk_patched-NE2215_11_C.21.zip
Magisk-25.2.apk
stock.recovery.zip
NE2215_11_C.21 Stable (full).zip
Feel free to follow along using this guide:
How to root your Android smartphone: Google, OnePlus, Samsung, Xiaomi, and others too!
Click to expand...
Click to collapse
Can you use ADB tools to restore stock rom if the device was soft bricked?
No. There are a few unbricking tools I've had to use in the past such as MSM tool, Fastboot Enhance Tool, and payload Dumper. (Google them, they're easy to find)
Note, that MSM tools are (nowadays) typically created and coded with a specific device and may also require authentication to unlock.
I've since moved on to the Google Pixel Pro series after seeing the terrible "Franekstien Project" that Oppo applied to Oneplus in their Color OS "make files"... It's literally a "lucky" mash-up of OnePlus Legacy OS and Oppo.
When companies sell out like that, do lazy transitions, etc. and the core reason we supported them in the first place becomes both forgotten and obsolete, that's when I typically stop supporting them.
Savio Dantes said:
No. There are a few unbricking tools I've had to use in the past such as MSM tool, Fastboot Enhance Tool, and payload Dumper. (Google them, they're easy to find)
Note, that MSM tools are (nowadays) typically created and coded with a specific device and may also require authentication to unlock.
I've since moved on to the Google Pixel Pro series after seeing the terrible "Franekstien Project" that Oppo applied to Oneplus in their Color OS "make files"... It's literally a "lucky" mash-up of OnePlus Legacy OS and Oppo.
When companies sell out like that, do lazy transitions, etc. and the core reason we supported them becomes forgotten, an obsolete, after which I typically stop supporting them.
Click to expand...
Click to collapse
Just to clarify does fastboot enhance tool and/or payload dumper works with restoring stock rom?
SKNIZZY said:
Just to clarify does fastboot enhance tool and/or payload dumper works with restoring stock rom?
Click to expand...
Click to collapse
Yes it does.
Fastboot enhance works fine, you need to remove the cow files first and have a valid payload.bin but that's it
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!