Database Develop

[Project Treble][v1.1][Android PIE + OREO][GSI][A-only]

View attachment 4567426
What is Project Treble:
Project Treble basically partitions your device into two separate partitions, a system and a vendor: system contains your generic system image, while vendor partition has your device specific files required for booting and running your phone. This way we can easily change the system image and be able to run our device on different system images with the same kernel and vendor partition
Read more about Project Treble
What's a GSI?:
A GSI literally means Generic System Image. It is a general system image meant for no specific device. Treble enabled devices have the capability to run a GSI. You can find a GSI here: Phh-Treble
ZTE Axon 7 hardware vs Treble implementation:
Our Axon 7 is an A-only device. This means that regarding the GSI images (GSI = Generic System Image) to be used, you need to get ARM64 and A-Only system images
What's Packaged in the zip:
A boot image (kernel)
A compressed vendor image (vendor)
Requirements:
- Unlock bootloader
- Installed patch EDL to add /vendor part. 800Mb
- Installed TWRP 3.2.1-8 - TREBLE
How to install:
- Format /system, /data and /cache, wipe /vendor
- Install Treble flashable zip package Project_Treble_v1.0-by-NFound
- Install GSI .img in /system part. How to flash a Generic System Image (GSI) on Project Treble supported devices
- Reboot
Alternative Instruction
Working:
Camera (and flashlight)
WiFi
Bluetooth
Telephony (Calls and Data)
Audio (Record and Playback)
Video Playback
Sensors
Broken:
Encryption (format data or remove encryption when coming from a non-treble rom)
Sepolicy is still permissive
Nothing else? Otherwise please report it!
Download:
- TWRP 3.2.1-8 TREBLE
- AXON7_GPT_ADD_VENDOR_800MB
- Project_Treble_v1.1-Axon7-by-NFound
Available GSI images is here
Android Pie Release 1 and other (video proof on Axon 7)
Fixes:
- More fixes for Treble ROM by @Kranoner
Credits:
@djkuz for add part. /vendor
@NFound for the fact that this dude did this for us real
Contributors:
@NFound
OS Version based: 8.X Oreo
ROM Kernel: Linux 3.18.71
ROM Firmware Required: Official BETA B12 Oreo
Version Information
Status: Testing
Source-Code Vendor
Created 2018-08-08
Last Updated 2018-08-12

Reserved

Thank you very much @NFound, i will test this asap. Does the gapps need to be flashed after install?

Waancho said:
Thank you very much @NFound, i will test this asap. Does the gapps need to be flashed after install?
Click to expand...
Click to collapse
Any ARM64 with opengapps.org for 8.x, in GSI 9.x Gapps included

Dear friends! Do not forget to backup before installation, this is a test version. It's time for me to sleep, write. As time will be, I will read your comments. If you find bugs - be sure to specify the version of GSI Android 8.x or 9.x
Thank you!

Hey need fast answer! In this guide is talking about a Vendor 8.1 and 8.0 and 8.0 does not work with this rom, so my question is does this rom support your treble? https://forum.xda-developers.com/pr...development/aosp-9-0-android-9-0-gsi-t3826357

Source code vendor blobs in OP

NFound said:
Source code vendor blobs in OP
Click to expand...
Click to collapse
I am a bit confused: how would non-standard hardware like our famous DAC be used in a treble ROM? Would the vendor partition make specific APIs available for such non-standard hardware?

Thank you for this. Maybe its a stupid question, but does the DAC properly function even when we install a GSI?
I have a feeling that a proper fully functional treble will make the other custom ROM thread for Axon 7 obsolete.

so no EDL needed? I'm so happy because i dont have a windowscomputer.
*edit: i think i did not read good and windows is still needed

Zobat said:
so no EDL needed? I'm so happy because i dont have a windowscomputer.
*edit: i think i did not read good and windows is still needed
Click to expand...
Click to collapse
You dont need a windows-pc. Only twrp

Do we need to install the project treble zip in the OP if we already enabled treble by EDL?

Let me see if I got this whole treble situation straight :cyclops:
I'm running the latest AEX but I assume this guide contains a more updated "treble" so to speak, is that correct? In order to try the GSI's do I need to follow this guide and wipe everything or will the next AEX release update treble and contain the new fixes?

https://sourceforge.net/projects/resurrectionremix-oreo/files/arm64aonly/
Arm64 and A only. Should be working right?

BaamAlex said:
You dont need a windows-pc. Only twrp
Click to expand...
Click to collapse
He DOES need a windows pc since in order to enable treble he needs to flash a file via EDL
troy5890 said:
Do we need to install the project treble zip in the OP if we already enabled treble by EDL?
Click to expand...
Click to collapse
You will need to install this again Project_Treble_v1.0-by-NFound
it contains bug fixes

bornlivedie said:
He DOES need a windows pc since in order to enable treble he needs to flash a file via EDL
Click to expand...
Click to collapse
For this zip here he dont need a PC. For the EDL package yes.

Just wanted to thank you and talk about my experience.
Converting the device to Treble was a breeze. Can be done in under 5 minutes with no issues at all. I'm currently running Android P PR1 with no major problems.
However, when trying to install the GSI (totally not related to your work, but wanted to comment on this so everyone can enjoy treble) I ran into a small problem (error 7) when flashing the POST sGSI zip files. I resolved this by doing the following:
Install the treble zip
Install the GSI
Install the treble zip again
Install the 3 zip files in order
This worked out fine for me.
Again, thanks a million times on your epic feat. This is no small task, and is very welcome. It marks a before and an after.

You, sir, are heaven-sent. Thank you for your good work.

bornlivedie said:
Install the treble zip
Install the GSI
Install the treble zip again
Install the 3 zip files in order
Click to expand...
Click to collapse
Why a second time?

Dear friends!
In the video I am used Release 1.
1. Flash Project Treble
2. Flash GSI
3. !!! In Mounting - UNMOUNT and MOUNT system and vendor!
4. Install patches 1,2,3
5. Reboot
Android Pie Release 1 (Download A-only and patches): https://androidfilehost.com/?w=files&flid=280192
Work GCam: https://github.com/AospExtended/platform_vendor_aosp/blob/8.1.x/prebuilt/common/apk/Gcam.apk
NOTICE: If during a call on Android 9 you do not hear the subscriber. (thx @atakan33 )
PS Here is another list of available GSI ROMs, use the translator!
9.x https://4pda.ru/forum/index.php?act=findpost&pid=75394613&anchor=Spoil-75394613-2
8.x https://4pda.ru/forum/index.php?act=findpost&pid=75394613&anchor=Spoil-75394613-3
Thank you!

[RECOVERY][TREBLE] TWRP Recovery for Zenfone 3

This is a TWRP fully Treble-ready with "Treble enabler" option in order to repartition safely the device.
Features:
TWRP fully Treble-ready;
Maintained with latest TWRP version;
Fully compatible with non-Treble devices - can be used as normal without Treble partitioning;
USB-OTG fixed
Has 'TWRP survival' function for automatically re-installing TWRP recovery when installing ROMs and kernels;
Adds a "Treble enabler" option that allows you to repartition your device in order to support Treble.
Has the option to shrink userdata to create Vendor partitions. All relevant partitions will be resized and formatted in one go.
If you shrink Userdata, it will ERASE DATA AND INTERNAL STORAGE COMPLETELY - but your device will stay compatible with all existing non-Treble ROM's
Instructions
Flash the recovery.
Reboot Recovery
Optional - Use the "Advanced > Treble enabler" option for repartition option.
If you opted to repartition for Treble, you are ready to flash a Treble ROM/Vendor pack.
About TWRP survival
TWRP survival is a simple hook that detects if a boot.img will be installed and restores TWRP after it's flashed. This only works if you have booted TWRP with Tissot Manager 2.0 from a real recovery boot - NOT from a recovery 'hot boot' (fastboot boot method).
You will see in the install log if a TWRP survival attempt is successful in the flash text output.
Automatic TWRP survival works when:
Flashing a ROM ZIP (or AIO) with TWRP
Flashing a boot.img in TWRP "Install Image" mode
Automatic TWRP survival does NOT work when:
Flashing a boot.img via fastboot
Restoring boot in a TWRP backup
Any other way of flashing a boot.img
In these cases, be sure the use the TWRP Installer immediately after flashing or restoring a backup - otherwise you may get the device into a confused state (especially if you restore a non-TWRP boot then try to install an AIO ROM without installing a new TWRP first).
Download
https://zenfone3-dev.gitlab.io/recovery/twrp-treble/
FAQ
Q) After I flash TWRP, I get kicked into fastboot when trying to boot the ROM!
A) Your kernel is not Treble-compatible.
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Q) My PC can't see the MTP (storage) device from TWRP!
A) For dualboot compatibility, MTP is automatically disabled at various points. Just enable it manually in the Mounts menu to get access.
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) I have heard varying results on this. It does for some, not for others. Please assume that this will NOT work.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes!
Q) I see "Failed to mount '/system' (Device or resource busy)" red error in TWRP after flashing a ROM
A) You can safely ignore it. You just need to reboot recovery before you can flash anything else (like Gapps) to this ROM.
Thanks to:
@CosmicDan for his files for Tissot Manager & this thread template
@makorn645, @planet9, @Oki for Party
XDA:DevDB Information
TWRP Recovery for Zenfone 3, Tool/Utility for the Asus ZenFone 3
Contributors
Giovix92, makorn645,
Source Code: https://github.com/Giovix92/android_device_asus_zenfone3/tree/twrp-8.1
Version Information
Status: Stable
Current Stable Version: 20190312
Stable Release Date: 2019-03-12
Created 2019-03-12
Last Updated 2019-03-12

@Giovix92 Does this mean I can use any ROM that is Treble? Or have some restrictions.

dVinsmoke said:
@Giovix92 Does this mean I can use any ROM that is Treble? Or have some restrictions.
Click to expand...
Click to collapse
Just the treble los16 zenfone3 on our forum for now

iamROOTX said:
Just the treble los16 zenfone3 on our forum for now
Click to expand...
Click to collapse
But then I see no difference from a "normal" ROM ported specifically to a device. Should not Treble support be able to use them on several different devices?
For example, should not I be able to go to the AEX Treble download area and use it on ZF3? If it would not be the same as having to wait for a dev port AEX to ZF3.
I'm really confused lol

dVinsmoke said:
But then I see no difference from a "normal" ROM ported specifically to a device. Should not Treble support be able to use them on several different devices?
For example, should not I be able to go to the AEX Treble download area and use it on ZF3? If it would not be the same as having to wait for a dev port AEX to ZF3.
I'm really confused lol
Click to expand...
Click to collapse
What do you expect? It's still in an early stage of porting. Some device specific bits still run from /system. GSI's may work but I doubt anything will work properly.
And I don't plan of supporting GSIs anyway.

makorn645 said:
What do you expect? It's still in an early stage of porting. Some device specific bits still run from /system. GSI's may work but I doubt anything will work properly.
And I don't plan of supporting GSIs anyway.
Click to expand...
Click to collapse
Being sincere I did not expect anything, since I did not understand anything lol This Treble left me was confused lol
So what's the difference of the Lineage Treble for a Lineage normal running in ZF3?

dVinsmoke said:
Being sincere I did not expect anything, since I did not understand anything lol This Treble left me was confused lol
So what's the difference of the Lineage Treble for a Lineage normal running in ZF3?
Click to expand...
Click to collapse
Currently nothing much ( updated proprietary bits + vendor image taken in place )
Maybe in the near future when everything is in place. I'll seperate Vendor image from builds ( noticable smaller updates )

makorn645 said:
Currently nothing much ( updated proprietary bits + vendor image taken in place )
Maybe in the near future when everything is in place. I'll seperate Vendor image from builds ( noticable smaller updates )
Click to expand...
Click to collapse
Also, when vendor img will be split from the ota package, with (if necessary) some adjustments we can flash GSI ROMs easily.

Great work guys!! Waiting for vendor partition, for some tests!

Williknot said:
Great work guys!! Waiting for vendor partition, for some tests!
Click to expand...
Click to collapse
Well, repartition works fine. After repartition a new /vendor partition of 1024mb will be made.
Although, you'll loose your data (apps+personal). So make sure to do a full backup of your device.

Feedback:
* HAVE A BACKUP. This tool messes with your partition table and is still unstable. Your data partition can be resized to the wrong size.
Will come back after a few months to provide more feedback. Appreciate the work guys.

Works fine for me, data is correctly resized even with multiple changes from normal to treble and back...
Can't seem to wipe /cache partition.
Anyone knows why?

[QS said:
;79165451]Works fine for me, data is correctly resized even with multiple changes from normal to treble and back...
Can't seem to wipe /cache partition.
Anyone knows why?
Click to expand...
Click to collapse
A bugfix release will be coming along with the next LineageOS build.

fcbn98 said:
Feedback:
* HAVE A BACKUP. This tool messes with your partition table and is still unstable. Your data partition can be resized to the wrong size.
Will come back after a few months to provide more feedback. Appreciate the work guys.
Click to expand...
Click to collapse
Well, that's normal.
Since you're going to make a new /vendor partition of about 1024mb, /data should be deleted & recreated in order to give some space to the new partition.
Also, what do you mean with "can be resized to the wrong size"?
The tool is pretty stable tho. Can you give more info such as model (ex. ZE552KL 4/64), script version (ex. 4.3b) & other?
Thanks.

I've successfully installed this tool, although attempting to install the new LOS 16 Android 9 ROM we have on this forum results in an error: 7, "Failed to mount '/vendor' (Invalid argument)"
From what I've perused so far in my research, that error mostly crops up on non-treble builds of TWRP, yet I definitely used the latest version from your website. I also redownloaded the latest version of LOS just to recheck, and yep, nothing's changed.
Any clue about what's going on here? I don't know much about Treble ROMs, or custom ROMing to be all honest.
EDIT: I have found the enable Treble option. Even when enabled and installed, after reboot, the /vendor partition cannot be read. It seems that after doing this too, I can't load files over USB, or mount my SD Card. I'm getting pretty confused as to what's happening. I can't boot into system, and fastboot won't connect to my PC.

Kaisogen said:
I've successfully installed this tool, although attempting to install the new LOS 16 Android 9 ROM we have on this forum results in an error: 7, "Failed to mount '/vendor' (Invalid argument)"
From what I've perused so far in my research, that error mostly crops up on non-treble builds of TWRP, yet I definitely used the latest version from your website. I also redownloaded the latest version of LOS just to recheck, and yep, nothing's changed.
Any clue about what's going on here? I don't know much about Treble ROMs, or custom ROMing to be all honest.
EDIT: I have found the enable Treble option. Even when enabled and installed, after reboot, the /vendor partition cannot be read. It seems that after doing this too, I can't load files over USB, or mount my SD Card. I'm getting pretty confused as to what's happening. I can't boot into system, and fastboot won't connect to my PC.
Click to expand...
Click to collapse
Did you follow these steps properly?
https://zenfone3-dev.gitlab.io/tutorials/repartition

can i flash android q gsi images using treble recovery.

Switching back to stock rom
If I have made the treble partition using this recovery is there any way to go back to stock rom?

Avinash007 said:
If I have made the treble partition using this recovery is there any way to go back to stock rom?
Click to expand...
Click to collapse
Wipe vendor, data, cache, dalvik partition and flash any ROM normally.

Can i flash android Q gsi image using this recovery on ze520kl

[guide] steps to flash gsi on redmi note 7

[GUIDE] STEPS TO FLASH GSI ON REDMI NOTE 7 [lavender]​
Many of us tried Flashing GSI on our Redmi Note 7 but failed due to various reasons even though it is absolutely bugless for Redmi Note 7 .
Here are the steps which i will mention below that will let us use the full potential of GSI.
Requirements :
Bootloader Unlocked
TWRP Installed
Ofcourse a working device
Installation Method :
First of all we need the flash the latest chinese beta rom.It gets updated everyweek. Since I have the cn rn7 i prefer to update the vendor partition everyweek for fixes and latest updates.But you can try on your stable rom too (I can't gurantee if things will work out on stable rom or not) .So, first of all be on china beta rom.
Go to fastboot mode and connect your pc to your device .You need to have installed xiaomi drivers to make this work properly. Once you are in fastboot ,open a terminal/cmd and type : fastboot -w ( this will erase your existing system partition and data and internal storage too , so make sure to have a backup if you have something essential on ur device)
Now considering that we have already downloaded a gsi i.e a phh GSI ..now for this case we are gonna assume its aosp as an example.. while in the fastboot mode type : fastboot flash system system.img ( here system.img(it can be of different name too) is the gsi img which you download from phh thread).
Remember : once the flash is completerd reboot to TWRP and not to system.
Once you are in twrp , flash magisk ( flash magisk latest canary as it has support for system as root devices) then press on wipe button of twrp,,,then advanced wipe..then tick mark on system and you will see repair or change file system option.Click on it..Click on repair and resize file system.
Now go to mount settings and mount system partition. Now you can flash gapps if you want .
After flashing gapps finally reboot to system
Voila! After in about 5 mins you will be booted to GSI rom
Post Installation Method :
You will have almost everything working after booting into gsi except you will run into brightness bug which you can fix by the following way
Connect your device with pc and enable mass storage
open a cmd/terminal on ur pc
type the following codes : adb shell
su ( in this case you will have to give permission from your device ; grant it)
setprop persist.sys.qcom-brightness 4095
Congragulations Now you have installed a gsi perfectly on your device
In this way you can flash almost all the gsi available on phh thread Hope this clarifies all of our problems.
Hit Thanks if I helped you somehow with this

shouldn't you be flashing disable_encrypt zip too?

repair or change file system option.Click on it..Click on repair and resize file system. I don''t get this one. There are a few options inside

PROdelision said:
shouldn't you be flashing disable_encrypt zip too?
Click to expand...
Click to collapse
No, its not required.
chiplovez9x said:
repair or change file system option.Click on it..Click on repair and resize file system. I don''t get this one. There are a few options inside
Click to expand...
Click to collapse
Make sure you have allowed modifications on system partition and also you dont have system as read only.

Does fingerprint working on GSI?

what is gsi?

I don't know much but gsi means u can flash almost all roms (which have images). And most of ROMs do have gsi images.. So u can install any rom on your phone. I don't know the steps to do so.. ?

bryanngapopala said:
what is gsi?
Click to expand...
Click to collapse
Simple speaking it's a image with clear android from google

Has anyone tested RR PIE GSI on RN7? Does it work?

Is it possible to boot Android O GSI? :silly:

letsmakecakes said:
No, its not required.
Click to expand...
Click to collapse
here's everything i did:
on miui beta.....already encrypted.
did fastboot -w
flashed latest RR gsi via fastboot
booted to twrp, flashed magisk(v19), repair and resize
reboot
asks for decryption password
where exactly am i going wrong?
able to boot if im using decrypt zip but lockscreen doesnt work.

Is the. Method the same for the global version with global rom?

letsmakecakes said:
[GUIDE] STEPS TO FLASH GSI ON REDMI NOTE 7 [lavender]​
Many of us tried Flashing GSI on our Redmi Note 7 but failed due to various reasons even though it is absolutely bugless for Redmi Note 7 .
Here are the steps which i will mention below that will let us use the full potential of GSI.
Requirements :
Bootloader Unlocked
TWRP Installed
Ofcourse a working device
Installation Method :
First of all we need the flash the latest chinese beta rom.It gets updated everyweek. Since I have the cn rn7 i prefer to update the vendor partition everyweek for fixes and latest updates.But you can try on your stable rom too (I can't gurantee if things will work out on stable rom or not) .So, first of all be on china beta rom.
Go to fastboot mode and connect your pc to your device .You need to have installed xiaomi drivers to make this work properly. Once you are in fastboot ,open a terminal/cmd and type : fastboot -w ( this will erase your existing system partition and data and internal storage too , so make sure to have a backup if you have something essential on ur device)
Now considering that we have already downloaded a gsi i.e a phh GSI ..now for this case we are gonna assume its aosp as an example.. while in the fastboot mode type : fastboot flash system system.img ( here system.img(it can be of different name too) is the gsi img which you download from phh thread).
Remember : once the flash is completerd reboot to TWRP and not to system.
Once you are in twrp , flash magisk ( flash magisk latest canary as it has support for system as root devices) then press on wipe button of twrp,,,then advanced wipe..then tick mark on system and you will see repair or change file system option.Click on it..Click on repair and resize file system.
Now go to mount settings and mount system partition. Now you can flash gapps if you want .
After flashing gapps finally reboot to system
Voila! After in about 5 mins you will be booted to GSI rom
Post Installation Method :
You will have almost everything working after booting into gsi except you will run into brightness bug which you can fix by the following way
Connect your device with pc and enable mass storage
open a cmd/terminal on ur pc
type the following codes : adb shell
su ( in this case you will have to give permission from your device ; grant it)
setprop persist.sys.qcom-brightness 4095
Congragulations Now you have installed a gsi perfectly on your device
In this way you can flash almost all the gsi available on phh thread Hope this clarifies all of our problems.
Hit Thanks if I helped you somehow with this
Click to expand...
Click to collapse
Which GSI should be needed to take? A-only or A/B ?

PROdelision said:
here's everything i did:
on miui beta.....already encrypted.
did fastboot -w
flashed latest RR gsi via fastboot
booted to twrp, flashed magisk(v19), repair and resize
reboot
asks for decryption password
where exactly am i going wrong?
able to boot if im using decrypt zip but lockscreen doesnt work.
Click to expand...
Click to collapse
I have no experience with GSI images, but I know in general that PIE breaks the encryption, if you roll back the security patch level. I don't know it this happened in your case, but I have lost couple of times my encrypted storage when I have tried to restore a backup of rom with older android patch level. After that, the bootup encryption pin is no longer accepted, neither by android nor by twrp, so the only option is to format data to remove encryption and start from scratch.
Were your miui beta and rr gsi of the same android security patch level?

Getting WRONG PIN error after setting up pin ???

letsmakecakes said:
[GUIDE] STEPS TO FLASH GSI ON REDMI NOTE 7 [lavender]
Many of us tried Flashing GSI on our Redmi Note 7 but failed due to various reasons even though it is absolutely bugless for Redmi Note 7 .
Here are the steps which i will mention below that will let us use the full potential of GSI.
Requirements :
Bootloader Unlocked
TWRP Installed
Ofcourse a working device
Installation Method :
First of all we need the flash the latest chinese beta rom.It gets updated everyweek. Since I have the cn rn7 i prefer to update the vendor partition everyweek for fixes and latest updates.But you can try on your stable rom too (I can't gurantee if things will work out on stable rom or not) .So, first of all be on china beta rom.
Go to fastboot mode and connect your pc to your device .You need to have installed xiaomi drivers to make this work properly. Once you are in fastboot ,open a terminal/cmd and type : fastboot -w ( this will erase your existing system partition and data and internal storage too , so make sure to have a backup if you have something essential on ur device)
Now considering that we have already downloaded a gsi i.e a phh GSI ..now for this case we are gonna assume its aosp as an example.. while in the fastboot mode type : fastboot flash system system.img ( here system.img(it can be of different name too) is the gsi img which you download from phh thread).
Remember : once the flash is completerd reboot to TWRP and not to system.
Once you are in twrp , flash magisk ( flash magisk latest canary as it has support for system as root devices) then press on wipe button of twrp,,,then advanced wipe..then tick mark on system and you will see repair or change file system option.Click on it..Click on repair and resize file system.
Now go to mount settings and mount system partition. Now you can flash gapps if you want .
After flashing gapps finally reboot to system
Voila! After in about 5 mins you will be booted to GSI rom
Post Installation Method :
You will have almost everything working after booting into gsi except you will run into brightness bug which you can fix by the following way
Connect your device with pc and enable mass storage
open a cmd/terminal on ur pc
type the following codes : adb shell
su ( in this case you will have to give permission from your device ; grant it)
setprop persist.sys.qcom-brightness 4095
Congragulations Now you have installed a gsi perfectly on your device
In this way you can flash almost all the gsi available on phh thread Hope this clarifies all of our problems.
Hit Thanks if I helped you somehow with this
Click to expand...
Click to collapse
Hi!
Did you not disable dm-verity and force-encryption?
Another question, the dev MIUI roms contain both the system and vendor partitions, right? How do you install only the vendor partitions from them? Or do you just flash MIUI and then reflash the custom ROM system? In that case, won't that affect dm-verity and encryption on the data partition?

Flashing correctly a GSI like in this guide; with vendor ecc ecc, will gcam work? Actually i'm on stock MIUI 10 and obv all working fine with a perfect version. My doubt is it.

Forever Alone said:
Getting WRONG PIN error after setting up pin ???
Click to expand...
Click to collapse
Did you not erase your /data partition through TWRP?
---------- Post added at 03:06 AM ---------- Previous post was at 02:46 AM ----------
Forever Alone said:
Getting WRONG PIN error after setting up pin ???
Click to expand...
Click to collapse
Did you not erase your /data partition through TWRP?

any recommended gsi rom with no bug?

booladi said:
Did you not erase your /data partition through TWRP?
---------- Post added at 03:06 AM ---------- Previous post was at 02:46 AM ----------
Did you not erase your /data partition through TWRP?
Click to expand...
Click to collapse
I did wipe userdata but not internal storage. heard its because i have unencrpyed data partition?

[HOW-TO] Use Generic System Images (GSI A-Only) on Your Xiaomi Mi Mix 2 Devices

Welcome​First of all make sure You know the Basics which are:
-You need to have a unlocked Bootloader
-You need to have the Orange Fox Recovery installed
-You need to have a Kernel and a Vendor Image
-You need to have a Treble A-Only Generic System Image (GSI)
-(Optional) A actual Magisk Installer zip File
-(Optional) A actual Open GApps Installer zip File
(Just use Google and You will find everything)
Alright. Now to the flashing!
-Make sure You have the needed Basics on Your Device including the Files You want to flash
-Wipe everything including data, caches, system, vendor
-Now flash a Vendor and Kernel Image to Your Device
-(You can download My "Vendor Installer" or)
-Flash a Treble AOSP ROM for Your Device and wipe System again
-Flash the Generic System Image using the Image Install from TWRP
DONE!
If You want to install Root and GApps on Your Device:
-Reboot to the Recovery and wipe Data/Caches again
-Install Magisk and GApps (Nothing else yet)
-Reboot to the System
DONE!
This Thread will be updated from Time to Time with new Vendor Installers and better Instructions. Feel free to talk about GSI ROMs in this Thread. I will keep it moderated as good as i can!
Download Links:
https://sourceforge.net/projects/orangefox/files
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Vendor Installer from Me: https://drive.google.com/drive/folders/1onzbCmoy18WlNDNFpq67z0Bv7QHB1d-b?usp=sharing
Actual Vendor: OMNI with EAS Kernel

Hello, I can not flash this vendor file. The orange fox returns ERROR7

q13017 said:
Hello, I can not flash this vendor file. The orange fox returns ERROR7
Click to expand...
Click to collapse
There is a more actual thread around the Mix 2 Forum. Try to search for it over Google, it provides more actual Vendors if i'm not wrong

Hi all! has someone managed to install and use the Pixel experience GSI image? It's stuck on the google logo loading screen for me, maybe i need another vendor?

Atcastells said:
Hi all! has someone managed to install and use the Pixel experience GSI image? It's stuck on the google logo loading screen for me, maybe i need another vendor?
Click to expand...
Click to collapse
Same issue here - the last working version is from March 2019.

If I put a gsi with a vendor from custom firmware, will my phone die?

[GUIDE] [HOW TO]Flash GSIs on Pie Vendor [X01AD]

Since the Pie update GSIs are not working because of System-as-root partiton But ASUS launched a new update in which GSIs are working.
READ WHOLE THREAD CAREFULLY.
REQUIREMENTS:
Unlocked bootloader (After Unlocking bootloader you will get a Red END OF STATE Warning. Don't Worry Press Power Button on that screen
Decrypted Data
Should be on latest firmware
If You're Using PitchBlack Recovery:
1. Boot into Recovery
2. Click On Advanced > Additional > Special > Setting OTA
3. Uncheck "Disable DM-Verity" Option Here
4. Done, Now You Can Use PitchBlack To Flash GSI on Pie Vendor.
INSTALLATION METHOD:
1. Download Any GSI of A/B type.
2. Download latest magisk manager zip
3. Patch your boot.img with Magisk (Tick on Preserve dm-verity by clicking on Advanced settins in magisk) or Download from Here
4. Boot into Recovery and Wipe Data, Dalvik Cache. Do not wipe system
5. Flash patched boot.img
Note: If your data is Encrypted then This step should be done with pitchblack otherwise your data may remain encrypted
6. Flash GSI image
7. Flash latest Magisk.
8. Go to Wipe option > Select Advanced Wipe > Tick on system > Click on Repair or Resize > Click on Resize.
9. Optional : Flash Gapps According to your choice If Gapps are not included in GSI.
10. Reboot System.
There is a possibility That your device will reboot again after asus logo. Don't worry
HIT THANKS IF I HELPED YOU:good:

do you see the red state warning after booting into gsi

sir iam unable to flash gapps after flashing the gsi. TWRP says the gapps variant is incompatible. I tried to flash arm 64 pico for pie. The gsi though boots. I flashed RR pie gsi (A/B) with pie vendor.. Please help Thanks in advance

jeno33 said:
sir iam unable to flash gapps after flashing the gsi. TWRP says the gapps variant is incompatible. I tried to flash arm 64 pico for pie. The gsi though boots. I flashed RR pie gsi (A/B) with pie vendor.. Please help Thanks in advance
Click to expand...
Click to collapse
Sorry I didn't mentioned in guide, that you've to modify script of gapps to get it working. I'll upload modified gapps tomorrow. Again I apologize

jeno33 said:
do you see the red state warning after booting into gsi
Click to expand...
Click to collapse
Red state warning is due to unlocked bootloader. It'll remain as long as bootloader is unlocked. But that doesn't create any problem except for increasing boot time by 5-6 seconds.

use A/B type cannot flash gapps,error 64. A type can flash gapps. Why?

gxfuzion92 said:
use A/B type cannot flash gapps,error 64. A type can flash gapps. Why?
Click to expand...
Click to collapse
Updater-script needs to be modified inside gapps, because gapps wrongly detects architecture as arm.
Install this gappshttps://drive.google.com/file/d/1nS2z4emxHovZ0x3CqXl59r8oBqx9DiPU/view?usp=drivesdk
I have modified the script

what rums for example are loaded and working?
currently the Havoc-OS-v2.0-20181027-GSI-ARM64-Aonly-Official is being loaded and running.
tried miui, flyme, Havoc-OS other versions

Is there any video tutorial?

Any tutorial videos?

gxfuzion92 said:
use A/B type cannot flash gapps,error 64. A type can flash gapps. Why?
Click to expand...
Click to collapse
Hey you able to flash any GSI except havoc 2.0 ??

I'm not able to access your document