Is it possible to install GSI ROMs? - Samsung Galaxy S21 Questions

Hello, I'm trying to install a GSI ROM on my Exynos S21 SM-G991N, since there weren't any custom ROMs for it. Is it possible to install a GSI ROM to S21? and how can I install one?

Hi, yes I was able to installs various GSIs successfully by installing TWRP and flashing the GSI with this guide from this thread:
How to make GSI Flasher for Samsung Galaxy A51 Super Partition Image
How to convert a gsi image so that it can be installed on a dynamic partition or super image partition. It may be work for other Android devices. This tool will help you to install gsi image on Dynamic Partition or Super Image Partition...
forum.xda-developers.com

Thanks!

Vailskier said:
Hi, yes I was able to installs various GSIs successfully by installing TWRP and flashing the GSI with this guide from this thread:
How to make GSI Flasher for Samsung Galaxy A51 Super Partition Image
How to convert a gsi image so that it can be installed on a dynamic partition or super image partition. It may be work for other Android devices. This tool will help you to install gsi image on Dynamic Partition or Super Image Partition...
forum.xda-developers.com
Click to expand...
Click to collapse
I tried it and I successfully installed a ROM, but I'm stuck in a bootloop. Can I know which GSI did you use?

hayang1027 said:
I tried it and I successfully installed a ROM, but I'm stuck in a bootloop. Can I know which GSI did you use?
Click to expand...
Click to collapse
I used the official Havoc GSI (the unofficial somehow didn't work), but I was also able to install the Linage GSI and PHH GSI. I think you have to pick the A/B variant and for me only the NON-vndklite version worked. I also usually restore a stock backup first (without recovery to keep TWRP), then I format data and after that install the GSI (without magisk).
I hope this helps

Vailskier said:
I used the official Havoc GSI (the unofficial somehow didn't work), but I was also able to install the Linage GSI and PHH GSI. I think you have to pick the A/B variant and for me only the NON-vndklite version worked. I also usually restore a stock backup first (without recovery to keep TWRP), then I format data and after that install the GSI (without magisk).
I hope this helps
Click to expand...
Click to collapse
I used the Official Havoc-OS 4.1 A/B, but I couldn't boot with it. Maybe it is different depending on the model?

I have experienced this sometimes as well, key for me was to restore the super partition to stock, format data and then flash the gsi with the zip mentioned in the comment above. I have the exynos variant.

Vailskier said:
I have experienced this sometimes as well, key for me was to restore the super partition to stock, format data and then flash the gsi with the zip mentioned in the comment above. I have the exynos variant.
Click to expand...
Click to collapse
I finally installed it! Thanks for helping!

(deleted)

Vailskier said:
I have experienced this sometimes as well, key for me was to restore the super partition to stock, format data and then flash the gsi with the zip mentioned in the comment above. I have the exynos variant.
Click to expand...
Click to collapse
I cannot enroll fingerprint because on-screen fingerprint sensor is not working. Also, I can't use 5G or LTE (only H+)
Is there a way to make any of them work?

Fingerprint sadly does not work for me either. I was able to switch to LTE in the mobile data settings. I hope the GSIs will soon support fingerprint for S21

Vailskier said:
Fingerprint sadly does not work for me either. I was able to switch to LTE in the mobile data settings. I hope the GSIs will soon support fingerprint for S21
Click to expand...
Click to collapse
The LTE unavailable thingie was a problem of all Korean carriers on a VoLTE unsupported ROM. I just ended up customizing One UI

Related

Can't get root access on Custom Roms except RR

Unlocked my Bootloader recently.
Flashed almost all the best ROMs available. But can't get root access in any of them except Resurrection Remix. The root access on RR works coz it is prerooted and needs a small addonSU to activate it fully. Coutresy of LineageOS/CyanogenMod.
Magisk would give out "Cannot mount /vendor" "Error:1". I tested it on all the latest builds of all the ROMs(AOSP, AOiSP, dotOS, Cardinal etc..)
Tried flashing Magisk versions out there including the treble version of the beta. Also tried the flashing 'boot.img' trick. Still the same thing shows up.
My device : Redmi Note 4 SD
Recovery : Redwolf/TWRP(tried with both of them)
Has anyone been experiencing the same issue??? Has anyone figured out a solution??
Also, RR also seems to give out the same error when flashing Magisk. When I installed Titanium Backup, it said I have 16 cm-SU installed. Can't find a way to uninstall or remove it either.
uncannyjish said:
Unlocked my Bootloader recently.
Flashed almost all the best ROMs available. But can't get root access in any of them except Resurrection Remix. The root access on RR works coz it is prerooted and needs a small addonSU to activate it fully. Coutresy of LineageOS/CyanogenMod.
Magisk would give out "Cannot mount /vendor" "Error:1". I tested it on all the latest builds of all the ROMs(AOSP, AOiSP, dotOS, Cardinal etc..)
Tried flashing Magisk versions out there including the treble version of the beta. Also tried the flashing 'boot.img' trick. Still the same thing shows up.
My device : Redmi Note 4 SD
Recovery : Redwolf/TWRP(tried with both of them)
Has anyone been experiencing the same issue??? Has anyone figured out a solution??
Also, RR also seems to give out the same error when flashing Magisk. When I installed Titanium Backup, it said I have 16 cm-SU installed. Can't find a way to uninstall or remove it either.
Click to expand...
Click to collapse
I think all the ROMs you listed are Treble ROMs. They require a special Treble version of Magisk which is usually linked in the ROM threads
Noter2017 said:
I think all the ROMs you listed are Treble ROMs. They require a special Treble version of Magisk which is usually linked in the ROM threads
Click to expand...
Click to collapse
I tried the treble versions of magisk too. Even tried the beta. No luck.
Figured it out
uncannyjish said:
Unlocked my Bootloader recently.
Flashed almost all the best ROMs available. But can't get root access in any of them except Resurrection Remix. The root access on RR works coz it is prerooted and needs a small addonSU to activate it fully. Coutresy of LineageOS/CyanogenMod.
Magisk would give out "Cannot mount /vendor" "Error:1". I tested it on all the latest builds of all the ROMs(AOSP, AOiSP, dotOS, Cardinal etc..)
Tried flashing Magisk versions out there including the treble version of the beta. Also tried the flashing 'boot.img' trick. Still the same thing shows up.
My device : Redmi Note 4 SD
Recovery : Redwolf/TWRP(tried with both of them)
Has anyone been experiencing the same issue??? Has anyone figured out a solution??
Also, RR also seems to give out the same error when flashing Magisk. When I installed Titanium Backup, it said I have 16 cm-SU installed. Can't find a way to uninstall or remove it either.
Click to expand...
Click to collapse
So it was a problem with the treble implementation of the ROM. I was installing treble ROMs using the stock TWRP/Redwolf recovery. These recoveries install the ROM but don't work or make the /vendor partition. This has led many people to believe that there is something wrong with their phone. Anyway, flashing a custom treble recovery did the job. Although not each one of them is perfect, TWRP_3.2.1-7_mido-treble by @NFound is the best one.
Solved every problem faced by me till now. Custom Magisk for Redmi Note 4 is available and works like a charm.
Magisk-v16.3-mido-treble
It seems no one faced this issue before, anyway this would help the new comers like me.
Thanks.
Couldn't get
I am using RR ROM Oreo since 2 weeks and finding ways to root it
But can't find any way to do it
Addonsu is not working
Treble magisk is not working
I need to change my recovery
But the ROM ended up encrypting my internal storage
So should I clean data to format and remove encryption
Or I can directly install a new recovery ?
Format then wipe everything. With a help of a pc or a laptop download a treble supported recovery or the Firefox recovery(search it).Then try again.

Finally Encrypted MI 8!

I have been struggling to encrypt MI 8 as without encryption, I feel like I am walking naked
After lots of trial and error, finally got it working. Here are the steps:
Prerequisites: Flash TWRP (TWRP-3.2.3-1110-XIAOMI8-EN-wzsx150) by @gulp79 - https://goo.gl/scMQwd
1. Copy the following files to the phone:
a. Vendor/firmware from @infrag - https://drive.google.com/open?id=1BJKthOJrWaWevaxus7rYkJNc95icIOsD
b. Copy Havoc (Dipper Update 25-11-2018) by @ZeNiXxX + Gapps to the phone.
c. Titanium Backup all the user apps and copy the backup to your PC. You will have to format data and you will lose everything on the phone.
2. Reboot to TWRP.
3. Flash vendor/firmware + Havoc + Gapps.
4. Wipe - Format Data (where you have to type "yes"). This will wipe everything from your /data partition, including /sdcard.
5. Reboot to System.
6. Setup the phone and add fingerprint/PIN (important).
7. Restore the user apps from Titanium Backup by copying the backup from the PC.
8. If you need Magisk, copy it to /sdcard and reboot to TWRP and flash it. When you boot to TWRP, you will be prompted to enter PIN to decrypt data.
Voila!
Phone is encrypted and you can sleep happy.
PS: Big thanks to @ZeNiXxX (for an awesome and feature rich Havoc ROM), @gulp79 (for converting the latest TWRP to English), @infrag (for providing the flashable vendor/firmware), @milouk (default kernel in Havoc), and OpenGAPPS team.
What exactly does it do?
By.TRabZonLu™ said:
What exactly does it do?
Click to expand...
Click to collapse
It encrypts your phone. If you ever lose a phone, no one can access your data.
Without encryption, if you give me a phone which has a PIN or Pattern setup with/without fingerprint, I can easily remove the PIN/Pattern in TWRP and boot your phone and look at all the data.
Without encryption, it's analogous to walking naked.
You should specify that it is for AOSP & LOS in title, MIUI Stock Global & China has built in System & Data encryption already. ( .EU multi ROM has only system encryption)
RainGater said:
I have been struggling to encrypt MI 8 as without encryption, I feel like I am walking naked
Snip
Click to expand...
Click to collapse
My phone is on global stable. Do I use the same steps if I want to keep my phone encrypted? Thanks a lot!
What if you want to have encryption using MIUI ROM ?
pmatthew said:
What if you want to have encryption using MIUI ROM ?
Click to expand...
Click to collapse
This thread is outdated, encryption works well now.
nfsmw_gr said:
This thread is outdated, encryption works well now.
Click to expand...
Click to collapse
I would not say that; yesterday I turned on the Phone encryption on xiaomi.eu stable rom (MIUI 10.2), and after that the phone booted only to Recovery. I had to format data, reinstall the ROM, and modify fstab.qcom, to have encryption...
pmatthew said:
I would not say that; yesterday I turned on the Phone encryption on xiaomi.eu stable rom (MIUI 10.2), and after that the phone booted only to Recovery. I had to format data, reinstall the ROM, and modify fstab.qcom, to have encryption...
Click to expand...
Click to collapse
I still can't find a way for GLOBAL ROM (latest PIE) to have DATA & SYSTEM encryption while keeping ROOT. Boot loops to recovery every time.... If anyone has this or can achieve this, please share. The closest i've been is I can get root, and have DM Verity with Optional encryption just fine -but as soon as i choose to encrypt the phone from the menu, it errors trying, then continuously boot loops.
pmatthew said:
I would not say that; yesterday I turned on the Phone encryption on xiaomi.eu stable rom (MIUI 10.2), and after that the phone booted only to Recovery. I had to format data, reinstall the ROM, and modify fstab.qcom, to have encryption...
Click to expand...
Click to collapse
Agimax said:
I still can't find a way for GLOBAL ROM (latest PIE) to have DATA & SYSTEM encryption while keeping ROOT. Boot loops to recovery every time.... If anyone has this or can achieve this, please share. The closest i've been is I can get root, and have DM Verity with Optional encryption just fine -but as soon as i choose to encrypt the phone from the menu, it errors trying, then continuously boot loops.
Click to expand...
Click to collapse
Umm, I flashed latest global myself a couple of days ago through fastboot.
I admit I didn't root the clean booted global rom, but mi-globe and xiaomi.eu variants got rooted just fine for me with Magisk V18.0.
nfsmw_gr said:
Umm, I flashed latest global myself a couple of days ago through fastboot.
I admit I didn't root the clean booted global rom, but mi-globe and xiaomi.eu variants got rooted just fine for me with Magisk V18.0.
Click to expand...
Click to collapse
Of course, Root without encryption is fine. Try running ROOT with DATA & SYSTEM encryption. That is the issue i am finding. Xiaomi.eu doesn't come with encryption out of the box for DATA. GLOBAL ROM defaults to encryption for SYSTEM & DATA on first boot. If it's not encrypted or flashing the DM-Verity/FEC remover first, running Magisk root is fine. As i stated, GLOBAL ROM with ROOT and FULL system & data encryption is where the issue lies.
Agimax said:
Of course, Root without encryption is fine. Try running ROOT with DATA & SYSTEM encryption. That is the issue i am finding. Xiaomi.eu doesn't come with encryption out of the box for DATA. GLOBAL ROM defaults to encryption for SYSTEM & DATA on first boot. If it's not encrypted or flashing the DM-Verity/FEC remover first, running Magisk root is fine. As i stated, GLOBAL ROM with ROOT and FULL system & data encryption is where the issue lies.
Click to expand...
Click to collapse
No I mean I was encrypted as well.
I'd try again just to be sure about what I said but I've finalized my LOS setup right now haha.
I'm almost 100% certain I was encrypted because I never formated data from twrp, just flashed stock, twrp, xiaomi.eu, magisk.
This shouldn't remove the encryption, and besides without the remover zip the rom enforces encryption, and I didn't flash the remover zip.
nfsmw_gr said:
No I mean I was encrypted as well.
I'd try again just to be sure about what I said but I've finalized my LOS setup right now haha.
I'm almost 100% certain I was encrypted because I never formated data from twrp, just flashed stock, twrp, xiaomi.eu, magisk.
This shouldn't remove the encryption, and besides without the remover zip the rom enforces encryption, and I didn't flash the remover zip.
Click to expand...
Click to collapse
- you said you flashed twrp, xiaomi.eu and magisk. Xiaomi.eu isn't encrypted by default without editing the values manually......Soo.... No you didn't have encryption and root in that scenario.
Agimax said:
- you said you flashed twrp, xiaomi.eu and magisk. Xiaomi.eu isn't encrypted by default without editing the values manually......Soo.... No you didn't have encryption and root in that scenario.
Click to expand...
Click to collapse
If I didn't format data after flashing xiaomi.eu the encryption has no reason to be gone.
If it had gone then the internal storage on my device would be blank. But all the files were there.
So yeah the encryption remained.
In any case believe what you will, I'm not gonna flash everything again just to prove my point.
If I need to go back to miui for any reason I'll do it and post back, otherwise give it a go yourself.
nfsmw_gr said:
If I didn't format data after flashing xiaomi.eu the encryption has no reason to be gone.
If it had gone then the internal storage on my device would be blank. But all the files were there.
So yeah the encryption remained.
In any case believe what you will, I'm not gonna flash everything again just to prove my point.
If I need to go back to miui for any reason I'll do it and post back, otherwise give it a go yourself.
Click to expand...
Click to collapse
I've tried xiaomi.eu in the past. The latest build i tried is dec 22, 2018, but the phone never encrypted. Contrary to LOS it always encrypted when i flashed it.
So, if your phone encrypted, then you need to decrypt it by entering the pattern/security when booting to recovery right?
To make sure if my phone encrypted, i boot to twrp and security pattern will appear. If its not encrypted, there will be no security pattern in twrp boot. I double checked it with connecting the phone with usb cable, An encrypted phone will always displaying random text/folder file, while not encrypted phone always display the real file.
So, i formatted data and flash xiaomi.eu (magisk etc) to see if it encrypted, its not. And i wipe everything again, i flashed LOS (etc), but it still not encrypted. So, i formatted data, and flash LOS (etc) right away, and the the phone was encrypt.
I think the fault was xiaomi.eu dec 22 build???
So, my final conclusion atm xiaomi.eu encryption is still fail.
Sent from my Mi 8 using Tapatalk
Yes MIUI ROM encryption is still fail
Just to confirm post above.
This eu rom encrypt only if you trip Fstab or you flash before an official Miui rom and encrypt it. then you can flash custom miui rom or miuirum and encrytion stay.
I don't explain why but I tested it on my old MI5.
Totally an unnecessary effort, but useful for those FBI agents. It's also hard to remove the encryption tho, I flashed a thousand times to remove the encryption and I won't mess with it again, but still an useful thread for FBI agents.
Finally figured out how to Root MIUI Global Stock AND keep DATA/Storage encryption
https://forum.xda-developers.com/showpost.php?p=78988313&postcount=4
Does this have something in relation with the bootloop when I try to flash any ROM that's different than MIUI? I'm very curious because my Mi 8 started to have bootloop problems when the Android Pie came out. Only one version of TWRP works for me, PixelExperience gives me bootloop when I flash it, xiaomi.eu works only following very specific steps (and this is the only one I've succesfully installed).

Unable to install Oreo GSI ROMs

Hello. I have an unlocked G8342, and I'm trying installing phh's GSI. But after I flashed the system image, I cannot boot my phone. It just shows "SONY" and then rebooted automatically.
I tried flashing the SW_binaries_for_Xperia_Android_9.0_2.3.2_v5_yoshino.img or SW_binaries_for_Xperia_Android_8.1.6.4_r1_v16_yoshino.img.
Before I unlock my phone, I've upgraded to the official Pie release. But what I'm installing is Oreo. Does this matter? Or what should I do in order to make it work?
Balthild said:
Hello. I have an unlocked G8342, and I'm trying installing phh's GSI. But after I flashed the system image, I cannot boot my phone. It just shows "SONY" and then rebooted automatically.
Before I unlock my phone, I've upgraded to the official Pie release. But what I'm installing is Oreo. Does this matter? Or what should I do in order to make it work?
Click to expand...
Click to collapse
if u dont backup ur TA partition before unlocking your bootloader, camera will not work on oreo gsi roms. I recommend u can try pie gsi roms, but it has worse camera quality and stability issues..
arslancn said:
if u dont backup ur TA partition before unlocking your bootloader, camera will not work on oreo gsi roms. I recommend u can try pie gsi roms, but it has worse camera quality and stability issues..
Click to expand...
Click to collapse
I just cannot even boot the GSI ROM. The camera might have issues, but it's not important right now...
Balthild said:
I just cannot even boot the GSI ROM. The camera might have issues, but it's not important right now...
Click to expand...
Click to collapse
I am having the same issue as you, I can't boot every gsi, even the 9.0 ones
yuezhengbaizhi said:
I am having the same issue as you, I can't boot every gsi, even the 9.0 ones
Click to expand...
Click to collapse
what gsi rom are you trying to flash? Do you have TWRP installed? I have a SOV36 (Japan AU version) and it boots with most of all gsi's. Currently using omni rom.
Here is my steps for flashing.
1. boot into twrp
2. goto wipe and factory reset (don't wipe data, system or cache just factory reset)
3. flash img
3a. optional: goto wipe; repair and resize system (if you want gapps)
4. flash gapps
5. flash magisk if you want root
6. reboot
Hope this helps
sinkoo1979 said:
what gsi rom are you trying to flash? Do you have TWRP installed? I have a SOV36 (Japan AU version) and it boots with most of all gsi's. Currently using omni rom.
Here is my steps for flashing.
1. boot into twrp
2. goto wipe and factory reset (don't wipe data, system or cache just factory reset)
3. flash img
3a. optional: goto wipe; repair and resize system (if you want gapps)
4. flash gapps
5. flash magisk if you want root
6. reboot
Hope this helps
Click to expand...
Click to collapse
I have tried the Phh's latest 9.0 GSI and RR's GSI and ERFAN's Q GSI and the official q GSI from Google.
None of them work, all stuck on the Sony boot logo
yuezhengbaizhi said:
I have tried the Phh's latest 9.0 GSI and RR's GSI and ERFAN's Q GSI and the official q GSI from Google.
None of them work, all stuck on the Sony boot logo
Click to expand...
Click to collapse
latest RR gsi did not work for me either but roms like omni, bootleggers, lineage 16 all booted on my SOV 36
Flash the lastest pie ftf, then follow sinkoo1979, instructions, also be sure you only flash ARM64-A versions.. I know Omni, Bliss and bootleggers work with imo bootleggers was the nicest but the unofficial one here has ceased development.. Use open camera for your pics...
The Roms are a hit or miss...make and keep a twrp backup handy...

Procedure for flashing GSI roms (LineageOS)

Hey guys, I'm trying to install LineageOS GSI (arm64 A/B) on my Mi A3 and seem to be having some trouble getting the GSI to actually boot successfully.
I have already done my research both on XDA and elsewhere online, yet most threads focused on the device seem to be of little to no use and/or filled with spam replies that only serve to confuse people looking into this.
A quick note regarding the aforementioned threads:
I don't mean to sound disrespectful to the community, but honestly, bashing somebody over why they'd rather install anything but your own fav piece of software is completely ridiculous.
Without further ado, my case goes as follows:
I'm starting fresh with the latest stock firmware, after having unlocked my bootloader ofc (critical too), I've successfully installed TWRP, wiped, installed the system image and yet after rebooting I'm just greeted with good ol' Fastboot, at which point I either directly flash the stock firmware and try again or wipe my data and whatnot (through TWRP, if reinstalled) and still end up with Fastboot.
Therefore, I have to ask you guys:
Has anyone previously successfully installed any GSI rom on the Mi A3?
Did you flash the system img while on stock firmware or a previously flashed custom rom (ie Pixel Experience)?
Is there any need for any special patch similar to the ones used for MIUI based Xiaomi phones?
Did you face any other issues while trying to flash a GSI?
My intention is to eventually install microG using Nanodroid.
Thanks for asking. I was trying to flash Havoc, crDroid and MSM-Xtended Android 10 GSIs but I can't boot the phone.
I have flashed lots of GSIs in the past, but this is really intriguing me, I can't boot on Mi A3. Wiping or formatting data does not solve, neither Permissiver or Disable Dm-verity zips did the job... :crying:
I successfully bootet the LineageOS GSI yesterday. I was not coming from stock though. I think this process should work assuming you already bootet to TWRP:
1. flash the GSI image to system partition using TWRP
2. flash the TWRP installer to keep your recovery
3. (not sure if needed) flash no fde patch
4. optional: flash some other stuff like Magisk and gapps
5. wipe data and dalvik
I think it rebooted to recovery on my first try but worked after flashing everything again. I probably made some mistake on my first attempt but just make sure to try again before giving up.
Also there's this tutorial but it's not at all what I did to get it working:
https://forum.xda-developers.com/mi-a3/how-to/tutorial-flash-custom-rom-mi-a3-t3977169

Updated Guide for Project Treble/GSI installing with KVT -- Install (almost) any ROM

ABOUT VERSIONS OF kvt:
2.x is if you're coming from stock Oreo or Pie
3.x seems to be only for stock Pie (otherwise networks don't work) - Oreo modem still has to be flashed though
There is a guide for GSI, but it is outdated, no longer maintained and all links are dead. That's why I'm creating this up to date guide.
If you do not know, what is Project Treble and GSIs, google it first. Proceed only if you know what are you doing. This guide is only for those, who know what is bootloader, fastboot, recovery and TWRP. If you don't, learn that first. There are many guides (for example guides for rooting and Magisk) UNLOCKED BOTLOADER REQUIRED
Guide
1) Download needed files:
- treble recovery: https://mega.nz/#F!b8RgGQCa!48TRsDcJFpaAGNOcc9Fb-A?GxR2TCAA
(this is my mirror, as original links are dead, don't know who is the original developer)
- kvt (find lastest version here) https://androidfilehost.com/?w=files&flid=303096&sort_by=date&sort_dir=DESC (developer deivesj)
(this allows GSI to work on Moto Z2 Play with some of it's stock features like fingerprint gestures, device gestures, pass safety-net and more)
- if you want to use Android 9.0 Pie based ROMs and older, you might want to use V7 kvt instead:
https://mega.nz/#!7w5V1KpQ!uoCMqynn5D83trvZ6uXY30S8b9rLiBlXf1JTeMYQ0rc
- if you are coming from stock Android 9.0 Pie ROM, you will need modem from Android 8.0 Oreo
https://mega.nz/file/mxhxXCaI#nJpdQ3nPnc6urkYP8vLrVb_vc_7EsnXK7MXw3U1xohw
- you may need stock recovery https://mega.nz/#!XphFEIxK!yNdHJSakfO90K1ua92SODoqd85nvwRi7h65EA8RkOuI
-GSI of your choice (links below)
transfer kvt to your phone to external microSD, keep the rest in your PC
1) go to fastboot mode (power+volume up simulaneously)
2) flash treble recovery (using fastboot command: fastboot flash recovery 'filename.img')
3) boot to recovery and wipe system, data, cache
Note: after boot to recovery, touchscreen doesn't work. Turn screen off and on to make it work!
4) in recovery, flash kvt zip. It will guide you through
5) reboot back to bootloader
6) flash chosen GSI as system image (fastboot flash system 'filename.img')
7) if you are coming from stock Pie, flash Oreo modem (fastboot flash modem NON-HLOS.bin)
reboot
Note: If you are coming from stock ROM, decryption may fail. The easiest way is to temporarily flash stock recovery. After decryption fails, it will prompt you to reboot and format data. TWRP can't do it, but stock recovery can. After you are booted, you can flash TWRP again.
Where to get GSIs:
the biggest list is here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
For Z2 Play, always download arm64 version and Aonly
There is a folder with ported stock ROMS (MIUI, Samsung, Moto...) on mirrors.lollinet but they do not work on Z2 Play. I also tried various stock ROM ports from other sources and they did not work. Custom ROMs fork fine.
Magisk:
Standard Magisk versions may not work. If you get bootloop, after installing Magisk, flash uninstaller. Then you can try phusson's version:
leodexe said:
Updates:
Magisk 20.x: https://sourceforge.net/projects/expressluke-gsis/files/Extras/phh-magisk-ten/
Click to expand...
Click to collapse
Ask if something isn't clear.
updated treble
Updates:
KVT 2.6: https://androidfilehost.com/?fid=8889791610682867863
Magisk 20.x: https://sourceforge.net/projects/expressluke-gsis/files/Extras/phh-magisk-ten/
I am currently using Pixel Experience Plus (Android 10) GSI, I installed it with latest KVT 2.6 and most stuff works out of the box. If you come from Stock Pie you need to flash the modem file from Stock Oreo to get proper audio during calls, as the modem from Android 9 gets bugged on Custom ROMs breaking the audio during calls. http://www.mediafire.com/file/q8nbpybxc8mjyew/NON-HLOS-Z2P-STOCK-8-OREO.7z/file
Confirmation
Mate can u confirm whether this kvt fix the screen flickering issue when there are more than 3 notifications in the status bar and does it have fingerprint gestures enabled???
lordfinix said:
Mate can u confirm whether this kvt fix the screen flickering issue when there are more than 3 notifications in the status bar and does it have fingerprint gestures enabled???
Click to expand...
Click to collapse
I don't use fingerprint gestures so I can't tell you about that. Also I had experiencing some crashes and reboots with this GSI lately, so I will try with another one once I can access internet to download anothet GSI.
CONFIRMED
i confirm it by flashing the flickering issue is gone and the gestures works as well this is by far the most stable KVT released kudos to developers
There are new versions of kvt available. Check the updated first post for link to deivesj's last files.
I did not experience any flickering or other graphical glitches with the new (2.X) versions of kvt (unlike the old v8 one).
Fingerprint gestures work, but not in all gsis
leodexe said:
Updates:
KVT 2.6: https://androidfilehost.com/?fid=8889791610682867863
Magisk 20.x: https://sourceforge.net/projects/expressluke-gsis/files/Extras/phh-magisk-ten/
I am currently using Pixel Experience Plus (Android 10) GSI, I installed it with latest KVT 2.6 and most stuff works out of the box. If you come from Stock Pie you need to flash the modem file from Stock Oreo to get proper audio during calls, as the modem from Android 9 gets bugged on Custom ROMs breaking the audio during calls. http://www.mediafire.com/file/q8nbpybxc8mjyew/NON-HLOS-Z2P-STOCK-8-OREO.7z/file
Click to expand...
Click to collapse
Thanks, I will update the guide
Could someone please give me a mirror of kvt v2.6? androidfilehost is terribly slow...
Hello,
Seem to have lost my network after flashing the pixel experience gsi from stock. imei missing as well. Any help?
It may be problem with modem.
What was your stock ROM? 8.0 or 9.0?
What version of kvt did you use? 2.x or 3.x?
How install?
how is the modem installed?
It's explained in the guide, step 7.
Wrongly flashed modem may cause WiFi, Bluetooth and SIM not to work
Kvt link is down. But you can use LineageOS with treble support now

Categories

Resources