[GUIDE] Install GSI on Galaxy S9 Snapdragon

[jorvacf]

I on stock now, but i going to try the new Pixel Experience compilation, and may be it works.

Ok, please let us know your your experience with that ROM.

---------- Post added at 11:08 AM ---------- Previous post was at 11:03 AM ----------

Now the brightness works, you just have to do this:

Update the phone to the July security patch (This updaates the vendor) Do you mean on stock rom?
Then download th July patch of any GSI Where can we get the July patch? or you mean to download the latest GSI of the ROM we want?

 

[hunchen]

I have encountered a problem, when I brushed into g9650_klabit_pie_gsi_V2.zip, there is no error, but the boot is infinitely restarted in the first interface, only the original boot.img can be restored to boot normally, but the fingerprint does not work, how can I solve it?

 

[FedericoPeranzi]

I have encountered a problem, when I brushed into g9650_klabit_pie_gsi_V2.zip, there is no error, but the boot is infinitely restarted in the first interface, only the original boot.img can be restored to boot normally, but the fingerprint does not work, how can I solve it?

Did you delete the rw_system.sh file ?

 

[hunchen]

Did you delete the rw_system.sh file ?

I deleted the file and can use it, but the fingerprint is invalid. What should I do next? My bottom package is G9650ZCU5CSFB. Security patch June 1, can you provide me with a complete operation step? I am very grateful.

 

[FedericoPeranzi]

I deleted the file and can use it, but the fingerprint is invalid. What should I do next? My bottom package is G9650ZCU5CSFB. Security patch June 1, can you provide me with a complete operation step? I am very grateful.

For now the fingerprint does not work.
The singal bar works for you?

 

[hunchen]

For now the fingerprint does not work.
The singal bar works for you?

I found a solution. I am using Chinese firmware. The security patch is June, and the gsi I brushed in is July. The security patch must be consistent with the fingerprint. In addition, I need to change the vendor/build.prop file. Now I am Fingerprint can be used

 

[cristiansc93]

Procedure ended in a bootloop in my G9650, did I do something wrong?
1. Fully flash G9650ZHS4CSF2_G9650OWA4CSD1 with Odin.
2. TWRP.
3. System Image.
4. GSI Kernel.
5. Delete rw_script.
6. RMM_patch+forceencrypt_remover.
Edit: Also failed formatting data and testing both images (Pixel Experience and AOSP)
Edit 2: Tried the procedure again and I was able to boot into PixelExperience finally, but the system wont stop crashing at the first screen after a reboot. I deleted the rw file at system/bin and flashed the "Disable Force Encryption" file in the first comments page.

 

[trinzto]

Does this guide work for S9 Exynos too if I use the Endurance GSI Kernel? I have never managed to make any GSI work on S9 Exynos. Has somebody tried it?

 

[burninitup]

Does this guide work for S9 Exynos too if I use the Endurance GSI Kernel? I have never managed to make any GSI work on S9 Exynos. Has somebody tried it?

Same question. I have tried a lot of GSIs and never managed to boot into any of them. Tried this method too, still no success.

 

[trinzto]

Same question. I have tried a lot of GSIs and never managed to boot into any of them. Tried this method too, still no success.

That's so sad, I've heard of some people who managed to install it after flashing Oreo vendor image but it doesn't work for me either, idk
If you find a solution one day please tell me, I'm really desperate lol

 

[jorvacf]

Hi all,

Does anybody was able to install a GSI Rom ons Snapdragon variant? If so, could you please share your experience and confirm if the steps on this thread works correctly?

Thanks

 

[klabit87]

Hi all,

Does anybody was able to install a GSI Rom? If so, could you please share your experience and confirm if the steps on this thread works correctly?

Thanks

Yes it works.

Sent from my Pixel 2 XL using Tapatalk

 

[jorvacf]

Yes it works.

Sent from my Pixel 2 XL using Tapatalk

Thank you bro, could you please share your thoughs? It is worth changing official to GSI?

 

[klabit87]

Thank you bro, could you please share your thoughs? It is worth changing official to GSI?

Really just a matter of preference to be honest. Try it. If you don't like it, you can always restore a backup.

Sent from my Pixel 2 XL using Tapatalk

 

[cristiansc93]

Is there a way to set-up a pattern lock, it seems that every time I touch the security tab in settings my hole system broke, first the settings app crashes and the system fail to load the lock screen at the next boot

 

[klabit87]

Is there a way to set-up a pattern lock, it seems that every time I touch the security tab in settings my hole system broke, first the settings app crashes and the system fail to load the lock screen at the next boot

Your firmware patch date needs to match the gsi patch date. For instance, you get July security patch date rom, you need to make sure to have the firmware if that month in order for vendor security patch date to match.

Sent from my Pixel 2 XL using Tapatalk

 

[GrandiosoTOAST]

Does this support U devices as well?

 

[klabit87]

Does this support U devices as well?

An unlocked bootloader is necessary so no.

Sorry

Sent from my Pixel 2 XL using Tapatalk

 

[GrandiosoTOAST]

An unlocked bootloader is necessary so no.

Sorry

Sent from my Pixel 2 XL using Tapatalk

Figured as much, but wanted to clarify. Thanks

 

[cristiansc93]

Your firmware patch date needs to match the gsi patch date. For instance, you get July security patch date rom, you need to make sure to have the firmware if that month in order for vendor security patch date to match.

Sent from my Pixel 2 XL using Tapatalk

There must be something off with my procedure, I beg for your help. The latest patch of the PixelExperience Rom is specified as July in the OP, but procedure failed as before. I checked the patch level inside PixelExperience before the system broke down and it said "August 1st", so I tried again with an august firmware, but the procedure failed again.
Update: I ended up returning to stock after trying to flash july->july, july->aug,aug->augu. But I'm encountering the same problem after rooting in stock.

Perhaps I might find help here? the procedure was

- Upgrade latest firmware through Frija and Odin
- Finish initial set-up and boot inside twrp
- Flash no-verity zip without allowing the system modification startup screen.
- Reboot in twrp and flash kernel,magisk and RMMpatch.
- Wipe data and wait first boot to complete
- Touch anything related to security and crash the system =(

My carrier is ATT, but ATT hasnt updated in a while and I can no longer return to att firmware, is this entire situation because of this?

Edit2: Tried again using ALL Mexico regions, US and Panama of the stock firmware but nothing worked. I have everything working in stock is just the root procedure what breaks the system.
I have a security patch level of 1st of July. And I'm rooting like so...

- Wipe everything (requires type "yes")
- flash no-verity, kernel_v5 and RMM
- Wipe again for good measure

At this stage the phone boots and everything is working properly, but touching a security related setting in the configuration or settings breaks the hole system the next boot; meanwhile no lock-screen can be set nor fingerprint.

Symptoms: At the next startup the systemUI lockscreen displays a briefly a black rectangle at the top left corner of the screen before changing to a "No service" dialog, exactly when that happends the bottom left corner of the screen pops "Safe Mode" and suddenly the UI restarts similarly to what "adb shell am-restart" does and the cycle continues infinitely.

Sorry for the long comment, any idea is dearly appreciated.
Fixed: No-verity zip file has just updated and with it my problem was fixed, but I'm way too scared to try PixelExperience now as the OP clearly stated to only use the july patch and last time I deviated, this happenned.
NoVerity.zip