[GUIDE] Havoc P and other P GSI with anykernel2 8.1 to P boot patch [temp]

[palbadi]

First things first

1. Remove all pattern, fp, face data and BACKUP all Partition in TWRP ( I lost baseband trying GSI images, those backup saved me).
2. TWRP should be installed and also Force disabled Encryption should be flashed.




Now follow the steps

1. Go to TWRP, wipe dalvik/cache, cache, system, data

2. Go back and Flash HavocP system image as System or you can try other P GSIs..
HavocP-arm64_aonly_vanilla_nosu-0830.zip
( You can check the source here for updates).

Optionally you can flash arm64 Gapps 9.0 (nano or micro is recommended) opengapps.org

3. Next without exiting TWRP flash this zip, this one patches boot for Android P GSI image compatibility..
POST-sGSI_3_v0.5.zip

4. Now go to wipe menu and wipe Dalvik/cache, cache, data and reboot.

For audio distortion fix:
[Temp] How-To Fix Audio distorted on P GSIs

For Volte: not found any fix yet, but may be fixed by tweaking build.prop like some other devices.. Will add if found.
May this line be added in Vendor/bin/init.qcom.sh like One plus 3.

# Hack to get IMS up and running on GSI

if [ -f /data/system/users/0/settings_global.xml ]; then
    sed -i 's/"multi_sim_data_call" value="1"/"multi_sim_data_call" value="-1"/g' /data/system/users/0/settings_global.xml
    restorecon /data/system/users/0/settings_global.xml
fi

This thread is temporary.. Will close it if stable Havoc is released by the Devs

Credits- skulshady, zenixxx, erfanoabdi, EnesSastim, phhusson, SH1M4BD

 

[NexusPenguin]

Hi,
Thanks a lot...
Will try that and report if it worked for me
Hope the back up won't fail on me !!!

EDIT : tried to do exactly as you said...
It may be worth mentioning a thing or two...
1°) that you should install GApps also...
2°) that it takes some time for the device to get out of the "Pocophone" splash screen
3°) that it may take some time until the SIM card is recognized

Regards.

 

[shailendra1993]

Please test multitouch issue, if it exists in this rom.

 

[palbadi]

Hi,
Thanks a lot...
Will try that and report if it worked for me
Hope the back up won't fail on me !!!

EDIT : tried to do exactly as you said...
It may be worth mentioning a thing or two...
1°) that you should install GApps also...
2°) that it takes some time for the device to get out of the "Pocophone" splash screen
3°) that it may take some time until the SIM card is recognized

Regards.

1. Oh sorry opengapps is released officially , updating op..
2. If pocophone splash screen is stuck, force reboot. Booting is fast for me just like stock rom. That stucking happened once in Havoc, rebooting solved.
3. For me sim detection and registration was fast with Jio 4G and Airtel.. BTW I am sure there is conflicts in Modem and OS (this caused baseband 'unknown').. So sometimes it may some time for sims to get recognized or even not be recognized after booting.

In short, these GSIs are not stable.

Please test multitouch issue, if it exists in this rom.

Are you telling about that Ghost touch??? I am now back to stock.. Will test that when I will flash again..
May be software glitch..

 

[shailendra1993]

1. Oh sorry opengapps is released officially , updating op..
2. If pocophone splash screen is stuck, force reboot. Booting is fast for me just like stock rom. That stucking happened once in Havoc, rebooting solved.
3. For me sim detection and registration was fast with Jio 4G and Airtel.. BTW I am sure there is conflicts in Modem and OS (this caused baseband 'unknown').. So sometimes it may some time for sims to get recognized or even not be recognized after booting.

In short, these GSIs are not stable.




Are you telling about that Ghost touch??? I am now back to stock.. Will test that when I will flash again..
May be software glitch..

No, the multitouch bug, ghost touch is different.
Check this out: en.miui.com/forum.php?mod=viewthread&tid=3746297

 

[NexusPenguin]

1.
In short, these GSIs are not stable.

Hi,

Same impression here : Treble needs a lot more work to deliver what Google is aiming at !
I now understand why some ROM devs do not want to release GSI ROM images

Regards.

 

[Technical]

If I wipe system before flashing Havoc image, I cannot flash gapps P (as it seems to be "seeing" the other slot even on oreo).
If I do not wipe system, I can follow the steps and boot Havoc. But an error message appears: "Android System: There is an internal problem with your device. Get in contact with your manufacturer to know the details". Each boot, same message.

 

[palbadi]

If I wipe system before flashing Havoc image, I cannot flash gapps P (as it seems to be "seeing" the other slot even on oreo).
If I do not wipe system, I can follow the steps and boot Havoc. But an error message appears: "Android System: There is an internal problem with your device. Get in contact with your manufacturer to know the details". Each boot, same message.

It is due to mismatch of ro.vendor.build.fingerprint value in build.prop in System and Vendor..

FIX:

1. Connect data cable to PC and boot into twrp
2. Go to Advanced/file manager
3. Copy build.prop from both Vendor and System to Sdcard, so that you copy them to your PC and edit.
4. In PC, Copy those build.prop files from sdcard and change the value of ro.vendor.build.fingerprint from build.prop (system) to build.prop (vendor).
5. Now overwrite the edited build.prop (vendor) to Vendor in the same process and you may give permission 644 (rw-r--r--) that vendor/build.prop
6. Reboot and check

 

[SmallTarzan]

What's the point of flashing the postGSI fixes, when it, at least for me and for my guide, works well without them.

I don't see the point.

 

[palbadi]

What's the point of flashing the postGSI fixes, when it, at least for me and for my guide, works well without them.

I don't see the point.

Havoc did not boot without that zip