Database Info

[GUIDE] How to install android P GSI Roms

Here a more complete guide.
Hi guys, i finally managed to get Havoc OS Pie fully working, this method should theoretically work on any pie gsi, if not tell me
Its not obligatory to follow this guide by letter, but you should have this things done:
Boot partition with TWRP and Magisk installed(some roms don't boot without root, they stay on splash image)
Formatted data
Selinux set on permissive on boot time(if it's enforcing camera, flashlight and headphones won't work)
Force encryption disabled in fstab.qcom(to fix wrong internal storage space)
Here's the step:
Install TWRP
Reboot recovery and flash magisk zip and this module if you want to install a selinux enforcing rom(you have to select permissive when installing). If you don't know flash to be sure, it doesn't harm.
reboot to bootloader and flash system
Code:
fastboot flash system "system image"
flash userdata.img from stock rom
Code:
fastboot flash userdata images/userdata.img
reboot and rom should boot normally(you should have a wrong storage space due to encryption)
with a rooted file manager edit /vendor/etc/fstab.qcom and change "forceencryption=footer" to "encryptable=footer" to disable encryption, then reboot to recovery
do a format data from TWRP and reboot
Not all these steps are needed on every roms because some don't need rooted kernel, some are permissive and maybe some handles encryption correctly, but by doing all these steps should make any pie rom bugless.
What i have tested(on havoc): camera, wifi, mobile data, hotspot(work but its always without password), headphones, audio, bluetooth, notch(yes, its recognised correctly), flashlight and sms.
Notice: first time you have to set preferred sim for mobile data and sms to get them working.
Huge thanks to
@Voodoojonny for encryption disabling
@d1ngh, @Dees_Troy and Team Win for official TWRP
@Jordan~Kurniawan for the hint of setting selinux to permissive

Great news!
thanks for the guide buddy.

Please explain by video?

Stock camera workink? Or need flash mi a1 cam module?

blue4 said:
Stock camera workink? Or need flash mi a1 cam module?
Click to expand...
Click to collapse
everything is working
you just can't set password for hotspot
if you are using your phone as a hotspot. it will be open

Gapps?

ouroboros12 said:
Gapps?
Click to expand...
Click to collapse
Since this guide's first step is to install TWRP, use TWRP to flash the latest Gapps.

On the note of the final point, "do a format and reboot" how should I go about that?
Using the ROM's factory reset, flashing the stock userdata.img again, or using TWRP?

rosiepie said:
On the note of the final point, "do a format and reboot" how should I go about that?
Using the ROM's factory reset, flashing the stock userdata.img again, or using TWRP?
Click to expand...
Click to collapse
It's the same because now encryption is disabled(formatting data in the classic way with encryption enabled cause a bootloop, this is why i suggest to use userdata from stock).
I will update mainpost.

When you flash userdata.img, why is from stock rom and not from your actual rom?.

Txatxiquesi said:
When you flash userdata.img, why is from stock rom and not from your actual rom?.
Click to expand...
Click to collapse
Because the one from your actual rom is encrypted and can't be read by other roms(if not you can skip this step, but i assume not).
I don't know why formatting with twrp cause a bootloop if device is encrypted, the only way i've found to clean data without issue is flashing userdata from stock... if anyone find another please tell me .

Thx for guide. Working.

blue4 said:
Thx for guide. Working.
Click to expand...
Click to collapse
Welcome, did you followed the entire procedure or only the hints at the top?
I want to be sure that the procedure is correct because i've made a some tests and in fact the procedure i've used it's not exactly the same.
Also, i've found offline charging not working, this seems caused by magisk, could you please check if you have also this issue?

Thank you for this guide! Sadly, we still have the situation to choose between encryption and working twrp. At the first boot, havoc encrypts storage, sothat twrp will not be longer able to encrypt data. "Encryptable=footer" disables encryption, but after that, you will not be able to encrypt phone anymore - I tried under a few scenarios, but encryption just stopped without anything.
And important with Havoc - every securitypatch level of stock leads to other problems - such as no wifi or other bugs. Best results - no bugs @All I got with the combination of @yshalsager´s twrp (18.08.) as kernel combined with stock 9.6.4.0 (july sec patch). You can patch the old twrp with the official afterwards.
Twrp inofficial yshalsager: - mtp not working, vendor not able to being backuped vs official twrp: sdcard not working... And no twrp that can work with pie encryption... Hopefully some dev will find a solution!

Voodoojonny said:
Thank you for this guide!
Click to expand...
Click to collapse
Welcome!
Voodoojonny said:
Sadly, we still have the situation to choose between encryption and working twrp. At the first boot, havoc encrypts storage, sothat twrp will not be longer able to encrypt data.
Click to expand...
Click to collapse
I've seen that re-installing twrp fixes, could you try?
Voodoojonny said:
"Encryptable=footer" disables encryption, but after that, you will not be able to encrypt phone anymore - I tried under a few scenarios, but encryption just stopped without anything.
Click to expand...
Click to collapse
You could just revert the change, flash stock userdata and reboot, this should tehoretically make encryption working again(while deleting all data).
Voodoojonny said:
And important with Havoc - every securitypatch level of stock leads to other problems - such as no wifi or other bugs.
Click to expand...
Click to collapse
Give me a logcat, maybe i will find why.
Don't work even with selinux permissive?

mac12m99 said:
Welcome!
I've seen that re-installing twrp fixes, could you try?
You could just revert the change, flash stock userdata and reboot, this should tehoretically make encryption working again(while deleting all data).
Give me a logcat, maybe i will find why.
Don't work even with selinux permissive?
Click to expand...
Click to collapse
I tried to reinstall twrp with
a) patched stock 9.6.4.0 with and without dm-verity
b) patched stock 9.6.9.0 same as above
Both leads to bootloop flashing userdata.bin doesn't fix
c) a and b with magisk and permissiver - > bootloop
Only Yshalsager's twrp as boot with 9.6.4.0 vendor works... All other vendors: broken wifi; all other kernels: bootloop (no dm verity, permissiver, root - nothing helps)
And if you flash userdata.bin you can read data with twrp, but booting havoc will change data, sothat twrp can't read it anymore. Flashing official twrp installer doesn't change anything...
It'slike a circle... Simply: stock twrp is only compatible with encryption of stock userdata... Only solution: decrypt...
I will send you logs tomorrow! Thank you!

mac12m99 said:
Welcome, did you followed the entire procedure or only the hints at the top?
I want to be sure that the procedure is correct because i've made a some tests and in fact the procedure i've used it's not exactly the same.
Also, i've found offline charging not working, this seems caused by magisk, could you please check if you have also this issue?
Click to expand...
Click to collapse
Yes and no. I flashed directly patched_boot.img for magisk and only booted twrp with fastboot for flashing Gapps and format data. But this procedure is good. The rom is very fast but sometimes micro-lagging more than stock.
Offline charging not work. (Rooted boot.img issue)
---------- Post added at 09:53 PM ---------- Previous post was at 09:07 PM ----------
Pixel Experience working too and smoother than Havoc for me. (Cam)

Apparently, since the last build of Havoc, is not necesary changing selinux, no bootloop on enforcing.

mac12m99 said:
Hi guys, i finally managed to get Havoc OS Pie fully working, this method should theoretically work on any pie gsi, if not tell me
Its not obligatory to follow this guide by letter, but you should have this things done:
Boot partition with TWRP and Magisk installed(some roms don't boot without root, they stay on splash image)
Formatted data
Selinux set on permissive on boot time(if it's enforcing camera, flashlight and headphones won't work)
Force encryption disabled in fstab.qcom(to fix wrong internal storage space)
Here's the step:
Install TWRP
Reboot recovery and flash magisk zip and this module if you want to install a selinux enforcing rom(you have to select permissive when installing). If you don't know flash to be sure, it doesn't harm.
reboot to bootloader and flash system
Code:
fastboot flash system "system image"
flash userdata.img from stock rom
Code:
fastboot flash userdata images/userdata.img
reboot and rom should boot normally(you should have a wrong storage space due to encryption)
with a rooted file manager edit /vendor/etc/fstab.qcom and change "forceencryption=footer" to "encryptable=footer" to disable encryption, then reboot to recovery
do a format data from TWRP and reboot
Not all these steps are needed on every roms because some don't need rooted kernel, some are permissive and maybe some handles encryption correctly, but by doing all these steps should make any pie rom bugless.
What i have tested(on havoc): camera, wifi, mobile data, hotspot(work but its always without password), headphones, audio, bluetooth, notch(yes, its recognised correctly), flashlight and sms.
Notice: first time you have to set preferred sim for mobile data and sms to get them working.
Huge thanks to
@Voodoojonny for encryption disabling
@d1ngh, @Dees_Troy and Team Win for official TWRP
@Jordan~Kurniawan for the hint of setting selinux to permissive
Click to expand...
Click to collapse
Installed aex, the camera does not work. Havoc does not work either.But there is a good news. I made a backup in twrp and then restored it. Restoration of backups works fine.
Then I tried to flash the gsi project treble. In twrp, I did wipe data, system, dalvick and internal storage. then it rebooted into twrp.connected to the computer and downloaded gsi havoc.a, then clicked the installation setting img. and chose the system image. after installation, I rebooted the phone in twrp, and then booted into the system. and the system worked well. the camera and hotspot did not work.

I think many problems people are having here are due to the fact the tutorial, while useful, is incomplete. I had to stuggle a bit but I got everything working as it should (well, besides SELinux Enforcing). I can make a clear English-language thorough tutorial if anyone wants. I don't want to steal anyone's thunder.
Enjoying some Havoc Pie myself atm

[ROM][PIE][9.0]AOSPExtended GSI ROM for X01BD ASUS Zenfone Max Pro M2

Hello all,
I have fully tested AOSOExtended ROM for zenfone Max Pro M2 device. And it has successfully worked for the volte calling and receiving. Only you need to install the IMS.APK which is post booting the room.
Download 64 bit A only
https://api.aospextended.com/downlo...b8bf350d1b37eb1eb2f1a21402438d535e41dae87c4e6
Steps.
1. Once download complete, extract the image file from the zip file.
2. Go to TWRP recovery and wipe out the data,cache, dalvik cache and system only.
3. Now install the image file to the system partition
4. Reboot the system once image has been installed and configure the things after booting. (Note : For JIO users - gapps should not be installed in the first because while booting system first time it will ask for the username and password and internet will not be available due to the default 3G configuration)
5. What you say configure all the things just download the attacks app I am asap and installed it adds normal installation like from the browser or file manager.
6. Reboot once and wait for 2-3 minutes, you will see HD icon.
After this VOLTE will start.
Credit goes to AOSOExtended ROM developer.
Known bugs.
Hotspot is not working
Thank you

Not booting, stuck on asus logo
Previously was on lineage 16
Wiped data,cache, dalvik cache and system
Installed image in system partition
Twrp gives no os message before rebooting.

AmeyMhatre96 said:
Not booting, stuck on asus logo
Previously was on lineage 16
Wiped data,cache, dalvik cache and system
Installed image in system partition
Twrp gives no os message before rebooting.
Click to expand...
Click to collapse
Which recovery did you use?

noob question here
what is IMS.APK?
edit: ah nvm, it's for volte service etc

After installation, it doesn't boot up, getting switch-off after asus logo

srinivasvaka1985 said:
After installation, it doesn't boot up, getting switch-off after asus logo
Click to expand...
Click to collapse
Same here

volte calling doesnt work

romfactory said:
volte calling doesnt work
Click to expand...
Click to collapse
waiting for your builts.

ROMFACTORY said:
volte calling doesnt work
Click to expand...
Click to collapse
try Volte solution given in Recurrection Remix GSI thread for Max Pro M2.
https://forum.xda-developers.com/ma...om-resurrection-remix-7-0-x01bd-asus-t3892628

srinivasvaka1985 said:
After installation, it doesn't boot up, getting switch-off after asus logo
Click to expand...
Click to collapse
You should have decrypted vendor.
So run Decrypt.zip once before installing GSI.

sachinm said:
You should have decrypted vendor.
So run Decrypt.zip once before installing GSI.
Click to expand...
Click to collapse
I done it already but even it doesn't bootup

srinivasvaka1985 said:
I done it already but even it doesn't bootup
Click to expand...
Click to collapse
This is strange issue dont know why.
For me GSI ROMS like HavocOS/Descendant - ver. OneDotFive/LiquidRemix not getting booted.
whereas AOSPExtended/RR 7/Arrow/ Phh-Treble GSI image booted successfully.
Seems ASUS provide bit diff devices of same model. :angel:
Thanks

Android 10 & Custom ROM & Slot A + B

Hello Android developers and enthusiasts,
I've been installing ROM since 2011 so I would not call myself a n00b however I seemingly cannot install an Android 10 ROM without issues. So this is a plea for help and advice!
I know you need to have OOS installed before you install a custom ROM so I use Auto Flash ROM to install OOS with Android 9 via System Update. I then boot and set up phone, install update, reboot and then install the OOS android 10 via the System Update. I then have a OOS installed with Android 10.
Why would I use such an elaborate method you may ask? Well, I tried to download latest OOS from OnePlus site and wipe phone and then install OOS but that fails (didn't record the error I'm afraid).
I then download all the ROM + dependencies on an USB stick and use fastboot to flash Mauronofrio TWRP. I then follow the steps in the ROM instructions. For EvolutionX these were:
First Time Install / Clean Flash
- Have OOS 10.3 flashed to both slots!!
- Boot to recovery
- Flash BUILD.zip (TWRP built-in)
- Wipe Cache
- Format data
- Reboot to recovery (optional)
- Flash Magisk.zip (optional)
- Reboot to system & #KeepEvolving
Click to expand...
Click to collapse
I followed these to the letter but when i rebooted system I got a snapdragon error and it wouldn't even boot into TWRP until I used fastboot to flash boot into TWRP. I also tried HavocROM and same happened.
I did manage to install Syberia using above method but I didn't like the ROM that much unfortunately.
Finally, I've also read up a lot on Slot A and B but it still is not very clear to me. I think I understand it but what happens does not confirm my theories
I therefore have some questions:
- Should I be able to wipe my phone and install OOS on a wiped phone and then install a custom ROM?
- When I install ROM and it says "Reboot Recovery" and then install ROM again. But if I check what slot is being used the reboot doesn't seem to change the slot. My assumption was that booting recovery was to install ROM in the other slot. Is that correct?
Any other tips you can give me?
Again, I like to stress I am not new to installing custom ROMs so I am a bit disappointed that this is causing me such grief.
Following some answers I will retry tomorrow so I can give some more details if needed. For now, appreciate any help.

roel1976 said:
Hello Android developers and enthusiasts,
I've been installing ROM since 2011 so I would not call myself a n00b however I seemingly cannot install an Android 10 ROM without issues. So this is a plea for help and advice!
I know you need to have OOS installed before you install a custom ROM so I use Auto Flash ROM to install OOS with Android 9 via System Update. I then boot and set up phone, install update, reboot and then install the OOS android 10 via the System Update. I then have a OOS installed with Android 10.
Why would I use such an elaborate method you may ask? Well, I tried to download latest OOS from OnePlus site and wipe phone and then install OOS but that fails (didn't record the error I'm afraid).
I then download all the ROM + dependencies on an USB stick and use fastboot to flash Mauronofrio TWRP. I then follow the steps in the ROM instructions. For EvolutionX these were:
I followed these to the letter but when i rebooted system I got a snapdragon error and it wouldn't even boot into TWRP until I used fastboot to flash boot into TWRP. I also tried HavocROM and same happened.
I did manage to install Syberia using above method but I didn't like the ROM that much unfortunately.
Finally, I've also read up a lot on Slot A and B but it still is not very clear to me. I think I understand it but what happens does not confirm my theories
I therefore have some questions:
- Should I be able to wipe my phone and install OOS on a wiped phone and then install a custom ROM?
- When I install ROM and it says "Reboot Recovery" and then install ROM again. But if I check what slot is being used the reboot doesn't seem to change the slot. My assumption was that booting recovery was to install ROM in the other slot. Is that correct?
Any other tips you can give me?
Again, I like to stress I am not new to installing custom ROMs so I am a bit disappointed that this is causing me such grief.
Following some answers I will retry tomorrow so I can give some more details if needed. For now, appreciate any help.
Click to expand...
Click to collapse
Hi!
I had this exact same problem a couple months ago. Rebooting to recovery used to change slots for me, but then it stopped.
What you can do is change active slot manually on Reboot section. By doing this, you don't even have to reboot to recovery in other to flash the other slot (altough I do it just to be safe).
And remember: the rom is flashed on the inactive slot, so after the final flash you gotta change slots one more time.

When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.

Thanks for the info, it really helps.
One question: in your experience can you wipe your phone and then installl OOS on the wiped phone?

So I just booted into TWRP, did standard wipe action: Data, Cache, and Dalvik. I then try to flash the latest OOS zip and I then get this error:
Error applying update: 7 (ErrorCode::kInstallDeviceOpenError)
Updater process ended withL ERROR: 1.
Error installing zip file: '/usbstorage/00, INSTALL/OnePlus6Oxygen_22_OTA_044_all_2002220042_a46425f1bfe43d2.zip
FIXED: I was using TWRP 3.3.1.11 and I then found out there was a newer version: 3.3.1.18 which you can get here: https://sourceforge.net/projects/mauronofrio-twrp/files/Enchilada/
I am now able to install OOS from scratch (ie wiped phone).

remewer said:
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Click to expand...
Click to collapse
I tried this method and everytime I can't seem to flash oos onto the other slot because when it reboots to recovery the folder is encrypted so I can't see which file is the zip. How do I flash the seccond OOS if it shows up encrypted in TWRP.
I have a OnePLus 6 with the latest OOS now because I got into boot loop and i used a flash-all.bat to get back to stock. I also use maronofrio's twrp because that works.

harshybar said:
I tried this method and everytime I can't seem to flash oos onto the other slot because when it reboots to recovery the folder is encrypted so I can't see which file is the zip. How do I flash the seccond OOS if it shows up encrypted in TWRP.
I have a OnePLus 6 with the latest OOS now because I got into boot loop and i used a flash-all.bat to get back to stock. I also use maronofrio's twrp because that works.
Click to expand...
Click to collapse
If you can boot OOS fine, try to do a local update so that both slots have OOS. Then try to flash a custom ROM again using the method I've mentioned.

remewer said:
If you can boot OOS fine, try to do a local update so that both slots have OOS. Then try to flash a custom ROM again using the method I've mentioned.
Click to expand...
Click to collapse
When you say local update you mean while I am running the rom, go to settings then do update from local source?

harshybar said:
When you say local update you mean while I am running the rom, go to settings then do update from local source?
Click to expand...
Click to collapse
Exactly

GuestD2559 said:
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Click to expand...
Click to collapse
@Cypher_01, Try this guide. This worked for me. I did not reinstall Nikgapps. Maybe that's where the problem lies? Don't forget to change the update slot at the end before you restart.​

mi mix 3 - stuck on twrp bootloop ?

Ok so fresh out the box, unlocked bootloader etc.
I have twrp running finally, and have gone through following the steps format/wipe etc.
flashed several differant roms to just try and get one to boot. every reboot it will automatically go into twrp..
I have tried Arrow, Lineage, pixel experience and all of them result in the same mi bootloop and automatically booting twrp.
im following the arrow install instructions :
New build required to be on MIUI Q firmware part (Recommended V12.0.1.0).
Use TWRP.
Make FULL WIPE (system/vendor/data/dalvik/cache) and FORMAT DATA - YES.
Flash ROM (link in first post)
Flash gapps, if need for VANILLA buildtype.
Reboot
when i flash the Xiaomi eu 12.0.1.0 as suggested... twrp bootloop.
so i am sitting with a device going between Mi screen and recovery only. I have no system ?
Can someone point me in the right direction.

Hi,
I do a full wipe like the instruction. After that I install the Xiaomi.eu v12 build. When that is installed immediately install Arrow 11 without formatting (and gapps if you choose the VANILLA build). I then don't install magisk or any other root solution and I reboot the device. This worked for me when I installed LineageOS and when I installed Arrow 10 and now 11.
So I first install Xiaomi and than the ROM I want without a format or reboot between them. If you are booted in the rom I then look into a root solution and install that if you want atleast.

UNBRICKING OP7 PRO

Hello i installed ArrowOS 12 for my OP7 pro, but i figured out that my NFC paymants does not work, so i wanted to go back to stock.
I did everything as said in this thread https://forum.xda-developers.com/t/...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/ but i cant get it to work. Im getting bootloop after even erasing system data, does anyone has any idea what can i do'?

marcin10217 said:
Hello i installed ArrowOS 12 for my OP7 pro, but i figured out that my NFC paymants does not work, so i wanted to go back to stock.
I did everything as said in this thread https://forum.xda-developers.com/t/...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/ but i cant get it to work. Im getting bootloop after even erasing system data, does anyone has any idea what can i do'?
Click to expand...
Click to collapse
This sequence has worked for me every time
1. Reboot twrp/lineage recovery, format data. Reboot bootloader
2. Fastboot boot into TWRP FBEv2
3. Sideload official TWRP 3.5.2.9-0 installer (found on TWRP website). Reboot recovery
4. Copy OOS 11.zip to internal storage. Flash OOS 11.zip. Reboot recovery again
5. Format data in OOS stock recovery & Reboot
6. After boot into OOS 11, just local upgrade rom .zip again, you will have OOS on both slots