Database Users

[EXPLAINED] z2_row (pro) | /factory to /vendor | revert to /factory - TREBLE

A GUIDE TO FLASH LATEST TREBLE ROMS, OLDER TREBLE ROMS OR NON-TREBLE ROMS ROMS
UPDATE: A guide to rename our /factory partition as /vendor so that you can flash OLDER Android Oreo treble builds! We do not need this guide on Android Pie custom ROMs or for Stock ZUI WE ONLY NEED THIS FOR ANDROID OREO TREBLE BUILDS REQUIRING /factory renamed as /vendor
for Lenovo Zuk Z2 PRO
Latest Treble : /factory renamed i.e switched to /vendor
Older Treble:/factory mounted as /vendor
Non-Treble: Nothing to do with Vendor, Factory stuff lol
INTRO
As you all know that we now have TREBLE, and Zuk-devs are working hard to improve it further so that when the time comes we can move to GSI builds of future Android versions.
Recently, Zuk-devs have renamed the /factory partition into /vendor partition previously we were mounting /factory as /vendor but now it has been converted(renamed) to /vendor partition with this you'll be able to use a Proper Magisk zip, and you don't need a modded/edited Magisk, etc and lotta other kinds of stuff that we will discuss and come to know in the future.
rootdir: fstab: Use the right label for our vendor partition.
TUTORIAL:
What you want to do:
** Flash OLD TREBLE ROMS /factory is renamed to /vendor - NOTE NOT NEEDED FOR NEWER ROMS! **
Instructions:
* Flash "Factory2Vendor_plus.zip",
*Flash belowTWRP,
*Reboot To TWRP,
*Flash ROM,
+ GApps / + Magisk etc
* Reboot.
*Enjoy :fingers-crossed:
Downloads:
Factory2Vendor_pro: https://androidfilehost.com/?fid=746010030569969371
TWRP for /factory renamed as /vendor roms https://github.com/cosmedd/android_...eases/download/20180413/20180413_recovery.img
** REVERTING BACK to NORMAL aka renaming /vendor back to/factory **
Instructions:
*Flash "Vendor 2Factory_plus.zip",
*Flash OFFICIALTWRP,
*Reboot TWRP,
*Flash ROM,
+ GApps / + Magisk etc
*Reboot.
*Enjoy :fingers-crossed:
Downloads:
Vendor2Factory_pro: https://androidfilehost.com/?fid=673956719939835215
https://twrp.me/zuk/zukz2row.html
** REVERTING BACK to NORMAL aka renaming /vendor back to/factory **
Instructions:
*Flash ROM,
+ GApps / + Magisk etc
*Reboot.
*Enjoy :fingers-crossed:
Notes:
This 'New TWRP' will work for both Latest Treble and Non-Treble RoMs
For ZUI also no need to flash any patch, New TWRP shall work (Needs to be tested)
You can flash Non Treble RoMs and Nougat Builds or other builds with the new TWRP and no patches need to be flashed
Once you flash "factory2vendor" or "vendor2factory" you do not need to flash again unless mentioned in the build
or if you want to revert back to Old Treble RoMs where /factory was mounted as /vendor
CREDITS
Zuk-devs - Davidevinavil, DD3Boh and Cosmedd (https://github.com/zuk-devs)
@Fedor917 for giving the idea
And all others who have contributed in any manner! :highfive:​

Reserved

You'll be able to use above method for Latest AEX coming soon by Davidevinavil and all the ROMs compiled using the latest sources as per by Zuk-devs
Links added, enjoy

thx

Can we make this procedure opposite? i.e. flash first twrp and than that zip? I normally flash twrp with official twrp app

1 or 2 should I do if I want to flash from the latest zui to AEX5.4 ,thx

thanks

Thanks zuk developer

I just tryed to flash Vendor 2Factory_pro..zip but I get following error "failed to mount '/vendor' (invalid argument)". I was in previous version 5.4 (1104). After restart, it does not load the rom but the bootloader. problem is the devices is not recognized under "adb devices" when in bootloader. Any ideas will be very welcome

darquesp said:
I just tryed to flash Vendor 2Factory_pro..zip but I get following error "failed to mount '/vendor' (invalid argument)". I was in previous version 5.4 (1104). After restart, it does not load the rom but the bootloader. problem is the devices is not recognized under "adb devices" when in bootloader. Any ideas will be very welcome
Click to expand...
Click to collapse
In bootloader (fastboot) you must use
fastboot -i 0x2b4c
ADB works in twrp or with system . Just follow this guide .

mar.ur said:
In bootloader (fastboot) you must use
fastboot -i 0x2b4c
ADB works in twrp or with system . Just follow this guide .
Click to expand...
Click to collapse
I installed the vendor, but the twrp is only black.
Any solution?

JustBr said:
I installed the vendor, but the twrp is only black.
Any solution?
Click to expand...
Click to collapse
Did you install latest twrp after flashing f2v

mar.ur said:
In bootloader (fastboot) you must use
fastboot -i 0x2b4c
ADB works in twrp or with system . Just follow this guide .
Click to expand...
Click to collapse
Thanks. I flashed last rom and after that updated twrp with twrp app and now I get no error about partitions.
I thought that to flash a twrp image with adb, I should do into fastboot mode. Can I also do it into recovery or system just with command : fastboot -i 0x2b4c flash recovery twrp.img?
Which guide do you mean? I checked on this thread and could not find a guide about adb.
Many thanks!

You can install twrp.img in any twrp .Just go to install/ install image and choose new twrp.img , then mark recovery and flash it .

mar.ur said:
Did you install latest twrp after flashing f2v
Click to expand...
Click to collapse
my twrp and 3.1, downloaded a recovered image(new twrp ), select image, recover and flash .. and the screen continues black, do not start twrp ... !!!!

JustBr said:
my twrp and 3.1, downloaded a recovered image(new twrp ), select image, recover and flash .. and the screen continues black, do not start twrp ... !!!!
Click to expand...
Click to collapse
I test a lot of systems . Last I was on mokee 7.1.2 with redwolf twrp with vendor partition ( not the latest ) . I install f2v.zip then twrp https://github.com/cosmedd/android_...eases/download/20180413/20180413_recovery.img . After that restart to recovery . Finally install to the latest Aex . No problems at all . First of all start with 2018.03.11 twrp , then install f2v.zip , 2018.04.13 twrp , restart to recovery and install aex or rr . That's all

Hy bro,
Can you send me the twrp version 2018.03.11 link?

failed to mount 'vendor'
After following the previous steps. TRWP start to show "failed to mount 'vendor' (invalid argument)'" message. I'm able to install the AEX 5.4, but the google apps do not crashes.
Any help?
Solved: wrong TWRP.
Nice boot animation

JustBr said:
Hy bro,
Can you send me the twrp version 2018.03.11 link?
Click to expand...
Click to collapse
https://github.com/cosmedd/android_...eases/download/20180311/20180311_recovery.img

mar.ur said:
https://github.com/cosmedd/android_...eases/download/20180311/20180311_recovery.img
Click to expand...
Click to collapse
Last help, I do everything by the pc, in fasboot mode ? or last twrp by his flash (twrp).

How to Use GSi on treble Device ?

Could anybody explain how to flash GSi on treble. i will describe what steps i did
1) Flashed Project_Treble_v1.1-Axon7-by-NFound
2)Flashed Havoc GSI Arm64 Aonly.img as system image
3)before reboot an error showed , NO OS DETECTED but after reboot stuck on a Tiny penguin logo . Waited for 10 minutes nothing happened
What i have to do to get it work

I'm not sure with this one.
I've read and reread posts here regarding this, I've seen other people in your position with the "No Os detected" after the install, I need to delve into this more.

From what I've read, did you add vendor partition?
I read through the steps here
https://forum.xda-developers.com/axon-7/development/nf-t3826885
steps
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.
- Reboot
I hope this helps
Instructions are from NFounds post
Thank you NFound

alwynjoshy said:
3)before reboot an error showed , NO OS DETECTED but after reboot stuck on a Tiny penguin logo . Waited for 10 minutes nothing happened
Click to expand...
Click to collapse
NO OS DETECTED is normal on GSI.
You flashing filesystem image (.img) over system partition and twrp won't be aware of changes to partitions until reboot.
alwynjoshy said:
What i have to do to get it work
Click to expand...
Click to collapse
Try LOS15.1 base and flash it again.
I tried HavocOS Oreo GSI 08/19 and it's working for now.
I didn't try Pie version of Havoc on LOS15.1.
Please, report, if you still have a call bug (not receiving incoming calls) . VoLTE may not work on GSI, I'm not even sure if it's working on LOS15.1.

xerocopy said:
NO OS DETECTED is normal on GSI.
You flashing filesystem image (.img) over system partition and twrp won't be aware of changes to partitions until reboot.
Try LOS15.1 base and flash it again.
I tried HavocOS Oreo GSI 08/19 and it's working for now.
I didn't try Pie version of Havoc on LOS15.1.
Please, report, if you still have a call bug (not receiving incoming calls) . VoLTE may not work on GSI, I'm not even sure if it's working on LOS15.1.
Click to expand...
Click to collapse
On Treble havoc i have call issue, What if try HavocOS Oreo GSI 08/19 with Los 15.1 base, would be that free from call bug

Syberclone said:
From what I've read, did you add vendor partition?
I read through the steps here
https://forum.xda-developers.com/axon-7/development/nf-t3826885
steps
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.
- Reboot
I hope this helps
Instructions are from NFounds post
Thank you NFound
Click to expand...
Click to collapse
Actually i am stuck in tiny Penguin ? logo, Tried the all steps you said, do i have to do any specific steps in Mount partition?

alwynjoshy said:
On Treble havoc i have call issue, What if try HavocOS Oreo GSI 08/19 with Los 15.1 base, would be that free from call bug
Click to expand...
Click to collapse
I don't know, you need to try. If you will have same problem like on PT 1.1 (you receiving calls on first boot and VoLTE works, but loosing ability to receive calls and VoLTE doesn't work after reboot), we could blame IMS service/VoLTE.
Current LOS 15.1 is capable to use GSI roms and it's better to use it because Project Treble made by NFound may not be updated anymore. It has also a fix for AK4490.
Try with LOS15.1 or change GSI rom.
Before you start, make sure that your vendor partition is created from the end of the system partition and it has 512mb size.
Use Party 0.5 tool by OKI in TWRP by flashing his zip or flash TWRP Labs by Oki which contain Party tool.
Thanks Oki for such a wonderful tools.

xerocopy said:
I don't know, you need to try. If you will have same problem like on PT 1.1 (you receiving calls on first boot and VoLTE works, but loosing ability to receive calls and VoLTE doesn't work after reboot), we could blame IMS service/VoLTE.
Current LOS 15.1 is capable to use GSI roms and it's better to use it because Project Treble made by NFound may not be updated anymore. It has also a fix for AK4490.
Try with LOS15.1 or change GSI rom.
Before you start, make sure that your vendor partition is created from the end of the system partition and it has 512mb size.
Use Party 0.5 tool by OKI in TWRP by flashing his zip or flash TWRP Labs by Oki which contain Party tool.
Thanks Oki for such a wonderful tools.
Click to expand...
Click to collapse
Actually i was on NFound's 800Mb partition and i flashed oki's version and its showed updating partition table after when i verify i saw 500mb Partition, Would that steps cause any issues?

alwynjoshy said:
Actually i was on NFound's 800Mb partition and i flashed oki's version and its showed updating partition table after when i verify i saw 500mb Partition, Would that steps cause any issues?
Click to expand...
Click to collapse
Not sure about Project Treble 1.0, it may not install on 512mb vendor. 1.1 should install w/o problems.
512mb vendor is required for LOS15.1 or LOS16.0.
Edit: If you had any files on data partition, they are probably lost.

In NFounds post there is this
"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"
It looks like 2 imgs are required? Arm64 and A-only, unless these 2 are integrated?

Syberclone said:
In NFounds post there is this
"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"
It looks like 2 imgs are required? Arm64 and A-only, unless these 2 are integrated?
Click to expand...
Click to collapse
You need arm64 A-only image. It is one .img file and it need to installed on system partition. It's similar to updating TWRP from recovery.
A/B is for devices which have two /system partitions and in case of problems, you could go back from B to A system if device won't boot. Cool feature, sadly, not for us.

xerocopy said:
You need arm64 A-only image. It is one .img file and it need to installed on system partition. It's similar to updating TWRP from recovery.
A/B is for devices which have two /system partitions and in case of problems, you could go back from B to A system if device won't boot. Cool feature, sadly, not for us.
Click to expand...
Click to collapse
I have question, by manufacturer we don't have the vendor partition, the developer created the partition for vendor then couldn't they create A, B partitions also?

alwynjoshy said:
I have question, by manufacturer we don't have the vendor partition, the developer created the partition for vendor then couldn't they create A, B partitions also?
Click to expand...
Click to collapse
I'm not sure, Seamless-update is really low-level feature, deeper than bootstack, kernel etc. Repartitioning doesn't make a sense.
Because Axon 7 was made before the feature was introduced by Google, we won't get it.
Did you try LOS15.1? Someone mention VoLTE is working LOS.
Here is Installation guide for LOS 15.1 made by Oki

xerocopy said:
I'm not sure, Seamless-update is really low-level feature, deeper than bootstack, kernel etc. Repartitioning doesn't make a sense.
Because Axon 7 was made before the feature was introduced by Google, we won't get it.
Did you try LOS15.1? Someone mention VoLTE is working LOS.
Here is Installation guide for LOS 15.1 made by Oki
Click to expand...
Click to collapse
No Volte label on status bar but on caller screen HD symbol shows. I flashed custom kernal and went to boot loop. Bro thanks for your reply

xerocopy said:
I'm not sure, Seamless-update is really low-level feature, deeper than bootstack, kernel etc. Repartitioning doesn't make a sense.
Because Axon 7 was made before the feature was introduced by Google, we won't get it.
Did you try LOS15.1? Someone mention VoLTE is working LOS.
Here is Installation guide for LOS 15.1 made by Oki
Click to expand...
Click to collapse
Where did you get all that bull?
A-B updates are as simple as a secondary system partition, and all that's needed is a fastboot command to select the active patrtition, which is present in B12 (not in previous N builds though). Of course if the system partition is still 5gb then you'll have like 10.5 gb used by vendor and system, plus all the other small partitions like bt and stuff.
Why exactly is a low level feature, deeper than bootstack?? It's a damn partition
I talked to djkuz before and he told me all this. At least I have a source.
"Because Axon 7 was made before the feature was introduced by Google, we won't get it."
Then what about Treble?

Noob Friendly GUIDE TO GSIs [P,Q] [TULIP:RN6PRO]

NOOB FRIENDLY? yea I guess so!
Thanks to @erfanoabdi for porting Android Q GSIs, OEM GSIs, etc......
NB: I don't know if other developer's GSIs would work or not.. Or even this would work for you.. It did for me for Q.. Try at your own risk.. Don't blame anyone if you made a mess! And i'm not a dev.. so.. there's no use of reporting bugs to me... although you can comment it so that someone might just maybe knowing how to help you!
Things You'll need
1. Unlocked bootloader
2. Custom Recovery (TWRP preferably)
3. Total backup (in case something goes wrong)
4. Treblized ROM(Most ROMs for Tulip are basically Treble Supporting)
5. Vendor(I strongly recommend Xiaomi.eu Android 9 Vendor! LINK: https://sourceforge.net/projects/xi...eu_multi_HMNote6Pro_9.4.25_v10-9.zip/download )
6. GSI of your Choice from https://mirrors.lolinet.com/firmware/gsi/
(PLEASE NOTE THAT TULIP ONLY SUPPORTS ARM64 A ONLY GSIs)
7. IF AND ONLY IF YOU'RE FLASHING ERFAN'S GSI THEN YOU NEED TO FLASH PERMISSIVERv2 AFTER FLASHING ANY GSI BE IT P OR Q.. AND IF YOU'RE FLASHING ANDROID Q GSI YOU NEED TO FLASH FIXZYGOTEv2 AS WELL
Q: How to make vendor Lonely? / How to install vendor alone?
A: Flash the Xiaomi.EU pie ROM and wipe dalvik,cache, system.. Don't wipe Vendor!!
Steps To Follow
1. Flash the ROM [Xiaomi.eu Based on Android 9 PIE]
2. Wipe Dalvik, Cache, System. DO NOT WIPE VENDOR
3. Now Flash the Genric System Image /GSI/ of your choice.
4. If and only if you're flashing Erfan's GSIs, FLASH PERMISSIVERv2 AFTER FLASHING ANY GSI BE IT P OR Q.. AND IF YOU'RE FLASHING ANDROID Q GSI YOU NEED TO FLASH FIXZYGOTEv2 AS WELL
5. Although in some cases when GSIs did not boot i flashed the latest Genom Kernel 4.4.180 and it seemed to boot up properly!
6. Reboot!
NB: There are bugs.. a lot... so you'll probably need the backup you previously created... Just sayin'....
Simply hit the thanks button..
No no no... pleaseeee...:good::angel:

Aha

Hi, one question, what recovery need?. I try some but when flash permisiver= error dont mount system. Good guide and thanks

fratletimac said:
Hi, one question, what recovery need?. I try some but when flash permisiver= error dont mount system. Good guide and thanks
Click to expand...
Click to collapse
Um... I used the twrp_v6 from the telegram group and it did work! Hope this helps!
https://t.me/tulip_updates/1014

Is this vendor can boot Irfan oxygen os GSI?

Anyone using any GSIs?

Thanks, goo help!
Probably not for me ??

[appeal][p]z3 dual D6633 patch for running z3 roms

hi guys
i need a patch for z3 dual that would be able to run z3 single-sim roms on z3 dual in android 9 pie
can any develpoer make it for me?please
thanks

please
somebody help meeeeeee

I found some patch on old oreo Z3 thread.
Also, I read the LOS 15 thread today. You need a specific TWRP for D6633. But I can't find this file.
This patch only tested on oreo ROMs so I don't know if it will work on pie.
Anyway, there you go.
You'll need a clean flash. The steps are:
- Flash TWRP 3.3.1 (if you want to install LOS 16.0, flash the boot.img from the .zip)
- reboot to TWRP, wipe everything (system, cache, dalvik, data, internal storage. BUT if you store the ROM and gapps file on internal storage, DO NOT wipe internal storage)
- flash ROM, Gapps, reboot to TWRP
- flash this dualsim patch, reboot to system
Good luck.

Zerikwan said:
I found some patch on old oreo Z3 thread.
Also, I read the LOS 15 thread today. You need a specific TWRP for D6633. But I can't find this file.
This patch only tested on oreo ROMs so I don't know if it will work on pie.
Anyway, there you go.
You'll need a clean flash. The steps are:
- Flash TWRP 3.3.1 (if you want to install LOS 16.0, flash the boot.img from the .zip)
- reboot to TWRP, wipe everything (system, cache, dalvik, data, internal storage. BUT if you store the ROM and gapps file on internal storage, DO NOT wipe internal storage)
- flash ROM, Gapps, reboot to TWRP
- flash this dualsim patch, reboot to system
Good luck.
Click to expand...
Click to collapse
thanks man appreciate that
problem still exist
ive got another problem too
after flashing a rom i want to boot to recovery but recovery doesnt load i mean it just reboots again and again
i tried many wayz but still cant go to TWRP after flashing rom

foli2 said:
thanks man appreciate that
problem still exist
ive got another problem too
after flashing a rom i want to boot to recovery but recovery doesnt load i mean it just reboots again and again
i tried many wayz but still cant go to TWRP after flashing rom
Click to expand...
Click to collapse
Sorry, I forgot to mention that.
The TWRP 3.3.1 from the link is only work on LOS 16.0. If you flash another ROM with TWRP 3.3.1, the TWRP will break.
In other word, you must flash the correct TWRP for the ROM. Also, in the past, there is a specific TWRP for Z3 dual but the link is dead.

Zerikwan said:
Sorry, I forgot to mention that.
The TWRP 3.3.1 from the link is only work on LOS 16.0. If you flash another ROM with TWRP 3.3.1, the TWRP will break.
In other word, you must flash the correct TWRP for the ROM. Also, in the past, there is a specific TWRP for Z3 dual but the link is dead.
Click to expand...
Click to collapse
i got frustrated completely

[Guide][NITROGEN][10][10] Phh Quack/LOS 17 GSI with Android 10 vendor

All you do is your own risk.
I did install (with wiping data) the following:
1. OrangeFox 10 recovery, check "disable dv-verify" to be on for 20.1.16+ vendor, then from it
2. Latest China Beta
https://xiaomifirmwareupdater.com/miui11/
3. Phh-gsi Quack / Andy Yan's LOS 17 GSI
https://github.com/phhusson/treble_experimentations/releases
https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/
4. Open gapps (optional)
5. Fix to enable Camera2, bluetooth and wired audio (attached)
6. Gcam (optional) - MGC_6.1.021_BSG_Arnova-TlnNeun_Urnyx05-v3.6.apk abd others
https://www.celsoazevedo.com/files/android/google-camera/dev-urnyx05/
What works: everything except exfat

Will try. What are the issues?

The only issue I had so far is Audiofx crash in LOS with gmaps navigate voice. Just deleted los soundfx app in Orangefox.
Please note: Android10 partition scheme is a/b, you have to use a/b gsi

btvbtv said:
The only issue I had so far is Audiofx crash in LOS with gmaps navigate voice. Just deleted los soundfx app in Orangefox.
Please note: Android10 partition scheme is a/b, you have to use a/b gsi
Click to expand...
Click to collapse
A/B?

Yep, Android 10 roms from Xiaomi are system-as-root, so bvN (a/b) gsi is suitable

btvbtv said:
All you do is your own risk.
I did install (with wiping data) the following:
1. OrangeFox 10 recovery, then from it
2. Latest China Beta
3. Phh-gsi Quack / Andy Yen's LOS 17 GSI
4. Open gapps (optional)
5. Camera2 enabler
6. Gcam
What works: radio, wifi, bt, camera, gapps
What does not work: please report if anything
Click to expand...
Click to collapse
Camera 2 enabler zip please
Thanks

This one should work https://forum.xda-developers.com/showpost.php?p=81149057&postcount=3

btvbtv said:
This one should work https://forum.xda-developers.com/showpost.php?p=81149057&postcount=3
Click to expand...
Click to collapse
steps are not explicit
flash latest china beta....do you wipe after?
ive flashed xiaomi.eu latest
then GSI
no gapps just to see if booted and nothing

China beta is linked from this thread OP
https://forum.xda-developers.com/mi-max-3/how-to/rom-official-recovery-fastboot-roms-mi-t3827503
Latest Xiaomi.eu failed to boot any gsi for me

btvbtv said:
China beta is linked from this thread OP
https://forum.xda-developers.com/mi-max-3/how-to/rom-official-recovery-fastboot-roms-mi-t3827503
Latest Xiaomi.eu failed to boot any gsi for me
Click to expand...
Click to collapse
ok got that and trying again.....
did you boot the china beta then back to recovery and flash or just flash all together then boot?
flash china beta
then GSI
reboots to fastboot screen
---------- Post added at 04:20 PM ---------- Previous post was at 04:17 PM ----------
my exact steps
1. reboot to recovery
2. advanced wipe .....data, system. vendor, ART, cache
3. flash china beta 20.1.2....no wipe
4. flash GSI
5. reboot to see if boots
tried Revenge OS and its booting now
.....needs the actual chinese full rom to boot.....
Revenge has not booted yet but i will try a few more now
---------- Post added at 05:37 PM ---------- Previous post was at 05:20 PM ----------
the flashing procedure of gsi
format device
except internal
flash latest firmware
flash treble rom (optional)
flash gsi as system image
reboot.
after getting reboot issue (if stuck at boot logo)
reboot recovery
mount system
open system/privapp folder
then
delete
dpservices
factory test
hardware test
hydra services
19t services
folders
remove simcards
reboot
comolete setup
reinsert sim
enjoy
**** some steps may not be needed ****

My steps were (after some mangling with various roms, so not 100% sure everything was clean)
- use orangefox
- flash china beta
- flash gsi
- clean data, cache, dalvik
- flash gapps
- reboot system

btvbtv said:
My steps were (after some mangling with various roms, so not 100% sure everything was clean)
- use orangefox
- flash china beta
- flash gsi
- clean data, cache, dalvik
- flash gapps
- reboot system
Click to expand...
Click to collapse
link me the one you have booting as none ive tried so far have worked
all stuck at boot logo
they should boot without gapps

https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.0/
Use arm64-bvN

Or arm64-ab 208
https://github.com/phhusson/treble_experimentations/releases

btvbtv said:
Or arm64-ab 208
https://github.com/phhusson/treble_experimentations/releases
Click to expand...
Click to collapse
them ones work but the others don't boot. gonna try and figure out why

Xiaomi Pie was a-only, Android 10 is system-as-root (a/b).

Last evoX from january doen't want to boot.

Link for china beta pls....thx!

https://forum.xda-developers.com/showpost.php?p=81405639&postcount=9

someone tested with erfanGSI?