Database Info

[RECOVERY] [F1f-Spectrum] [TWRP-3.1.1-0] For Project Spectrum Bootloader ONLY!

This is an unofficial port of TWRP Recovery for the Oppo F1F on Project Spectrum Bootloader. Much Thanks and credit goes to the TWRP team, Lineage team, and brinleyaus for making this possible. This will allow flashing of modification zips (eg. supersu, magisk, xposed, etc) over the top of Project Spectrum or flashing spectrum based ROMS.
Instructions:
Already running Project Spectrum
- If you haven't already unlocked you bootloader you will need to go into SETTINGS > ABOUT PHONE and tap BUILD NUMBER 7 times to unlock DEVELOPER OPTIONS, Then go into SETTINGS > DEVELOPER OPTIONS and enable them, also enable ADB DEBUGGING and OEM UNLOCK. Now reboot into fastboot (adb reboot bootloader) and run fastboot oem unlock.
- Install this image file through fastboot (If you are unsure of this step follow one of the many tutorials about installing TWRP through fastboot)
On ColourOs with TWRP
- Do a full wipe first or the install will fail. (In TWRP hit WIPE then swipe to factory reset.) Do a backup first as you will lose data.
- Flash this zip file through twrp and then hit "wipe dalvic and cache", then hit HOME then REBOOT then RECOVERY. (rebooting to the new recovery will ensure the recovery sticks) then Flash any Spectrum based rom or restore any Spectrum based backup. NOTE the ColorOs system and boot.img will still be there but wont boot so you MUST flash or restore a Spectrum based rom before you reboot to system.

Reserved.

MiniBlu said:
Reserved.
Click to expand...
Click to collapse
Battery can't charge full!! Help ?

Added file and instructions to OP to flash Spectum bootloader,firmware and twrp From ColorOs TWRP.

Thank.link from androidfilehost is slowly. I using wifi
Sent from my F1w using XDA-Developers Legacy app

MiniBlu said:
Added file and instructions to OP to flash Spectum bootloader,firmware and twrp From ColorOs TWRP.
Click to expand...
Click to collapse
The TWRP is not the 3.1.1
It is the 3.0.1

khannz7 said:
The TWRP is not the 3.1.1
It is the 3.0.1
Click to expand...
Click to collapse
Which file are you talking about, I just checked the links and the flashable zip was actually pointing to the full ROM which defiantly has the 3.1.1-0 version. (I just fixed the link to point at the bootloader, firmware and twrp zip.) Are you rebooting to recovery after flashing to make it stick?

MiniBlu said:
Which file are you talking about, I just checked the links and the flashable zip was actually pointing to the full ROM which defiantly has the 3.1.1-0 version. (I just fixed the link to point at the bootloader, firmware and twrp zip.) Are you rebooting to recovery after flashing to make it stick?
Click to expand...
Click to collapse
The PS 1
Yeah doing it right....But it is the same old twrp 3.0.1 mentioned somewhere in the G+ forums....
Never mind ....did you get the port to work

khannz7 said:
Yeah doing it right....But it is the same old twrp 3.0.1 mentioned somewhere in the G+ forums....
Never mind ....did you get the port to work
Click to expand...
Click to collapse
Which ps1 g or zip?
I have just checked. None of the files I have posted are the old version. They are all the newest 3.1.1-0 version.
No not yet.

MiniBlu said:
I have just checked. None of the files I have posted are the old version. They are all the newest 3.1.1-0 version.
No not yet.
Click to expand...
Click to collapse
I have installed the full ps rom with twrp but what I got is not 3.1.1 it is the 3.0.1
+
Maybe I could help you somewhere with the port

I have to remove the sd card and then re-insert it then it received. who can solve it? The battery will charge too long to fill up

khannz7 said:
I have installed the full ps rom with twrp but what I got is not 3.1.1 it is the 3.0.1
Click to expand...
Click to collapse
OK, I'll download it and check, maybe I uploaded from the old folder. Hope not 6.5 hours to upload it.

MiniBlu said:
OK, I'll download it and check, maybe I uploaded from the old folder. Hope not 6.5 hours to upload it.
Click to expand...
Click to collapse
I would love to help you with the port and maybe I could get something new to learn:fingers-crossed:

Phucan2017 said:
I have to remove the sd card and then re-insert it then it received. who can solve it? The battery will charge too long to fill up
Click to expand...
Click to collapse
No one. If you don't like it stick with ColorOs or Lineage.
khannz7 said:
I would love to help you with the port and maybe I could get something new to learn:fingers-crossed:
Click to expand...
Click to collapse
Not just yet, just got to work out the ramdisk changes needed to get ported roms to boot properly with spectrum kernel, then I'll share the info with you and then let the porting begin.

MiniBlu said:
No one. If you don't like it stick with ColorOs or Lineage.
Not just yet, just got to work out the ramdisk changes needed to get ported roms to boot properly with spectrum kernel, then I'll share the info with you and then let the porting begin.
Click to expand...
Click to collapse
Cool

I did that. But for oppo f1 this rom is not finished yet but there are still many bugs. I return coloros

Just used the spectrum zip and worked flawlessly.(from other thread oops) Thanks alot.

How to go back to coloros ? Do i need to flash stock recovery ?
Sent from my F1f using XDA Labs

the_reds2000 said:
How to go back to coloros ? Do i need to flash stock recovery ?
Sent from my F1f using XDA Labs
Click to expand...
Click to collapse
No, Read the OP of this thread. There is a zip (and instructions) to return to ColorOs Bootloader,firmware and TWRP. From there you can flash any TWRP flashable ColourOs based Rom (ColorOs or LineageOS) or restore backups from them.

Which root method will be used for this?

[GUIDE] How to flash Treble roms on OnePlus 6

Hey guys! So, as You know, OP6 has Treble, but when You flash GSI's on it, it will take You to EDL mode instead. Why? Well.. because of A/B and VBMETA partition. So... how do we fix it? It's actually pretty simple! Follow the guide and You will be able to boot GSI roms on Your OP6
Note: Before You can flash any GSI, You have to unlock Your bootloader. To do that, simply type: fastboot oem unlock . Just remember that it will wipe Your data!
Important: Flash 5.1.6 or above before flashing v20. It looks like 5.1.6 fixed Treble problems. Files have been updated to: 5.1.7
Step 1: Download any GSI rom You want, in this guide I'll be using Phh Treble latest build: Phh Treble A/B v20 with GApps and SU
(Make sure to extract it before flashing. You can do that with 7zip)
Step 2: Download this zip. It contains stock VBMETA as well as stock boot image, just in case if Your device is rooted. Link: Treble OP6 Files 5.1.7
Step 3: Extract those files on Your desktop for example and open terminal/cmd in the same folder as Your files. (Before You can do that, You should download latest minimal ADB and Fastboot available here: ADB & Fastboot XDA Thread Link ) Now. Copy and paste those commands:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
This command will let You boot non OOS roms, like Phh Treble or any other Treble GSI.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Those commands will flash stock non rooted boot image to both of Your boot partitions (Treble roms need slightly different root that's why we need to use stock boot image for now)
fastboot flash system_a system-arm64-ab-gapps-su.img
fastboot -w flash system_b system-arm64-ab-gapps-su.img
Okay, these commands will flash Phh GSI to both of Your partitions. The only difference is that second command will wipe Your data partition which is most likely required to have a bug free boot. So backup Your data before!
Aaand that's it! :victory: Enjoy Your new GSI rom.
Thanks to Dewang Rocker for making a tutorial video! Make sure to like and subscribe
And one more Thanks to @AxM2 for posting my guide on Github!
OnePlus 6 Treble Github Page
Q/A
Q: Does this method work for all GSI images?
Yes! It should work fine, as long as Your GSI supports A/B partitioning. Most Devs build A/B GSIs so no worries.
Q: Bugs?
Build v20:
Stock camera has problems with focus, but if You install OOS camera it works fine.
Notch is covering screen a little.
Q: I want to see some screenshots!
Credits:
Phhusson for Wonderful GSI!
FunkWizard for latest firmware!
@dylanneve1 for being an awesome friend and helping me with many of my projects.
OnePlus for OP6 and releasing updates that are actually useful!
James Muir for Pixel 2 Guide on Github.
Google for creating Treble for us.​

Looks promising! Anyone tried and confirm that the roms boot?
And what does wiping of data partition means? Will that wipe the internal storage too? or just the "data" (The apps and stuff).

any idea what treble rom/s that has the feature of stretching third party apps to use 18:9/19:9 aspect ratio or whatever instead of it being cropped?

Joyarup said:
Looks promising! Anyone tried and confirm that the roms boot?
And what does wiping of data partition means? Will that wipe the internal storage too? or just the "data" (The apps and stuff).
Click to expand...
Click to collapse
It does boot, tried the guide 3 times already just to make sure that it works. And -w will wipe Your internal storage, not just apps. So make sure to backup everything. Or You can just wipe data in TWRP and then boot GSI. This way Your internal storage won't be deleted. But a full backup is always recommended! Even if You flash new fonts or something .

ProtoDeVNan0 said:
It does boot, tried the guide 3 times already just to make sure that it works. And -w will wipe Your internal storage, not just apps. So make sure to backup everything. Or You can just wipe data in TWRP and then boot GSI. This way Your internal storage won't be deleted. But a full backup is always recommended! Even if You flash new fonts or something .
Click to expand...
Click to collapse
Alright thank you for clearing things, I will give it a try and will let you know!
Thank you for your work.

I get unknown option when running the fastboot --disable-verity command

eminem5055 said:
I get unknown option when running the fastboot --disable-verity command
Click to expand...
Click to collapse
Make sure the drivers and adb and fastboot is installed and your command line is in the exact location as your fastboot.

Joyarup said:
Make sure the drivers and adb and fastboot is installed and your command line is in the exact location as your fastboot.
Click to expand...
Click to collapse
That worked thanks!

Abaddon said:
any idea what treble rom/s that has the feature of stretching third party apps to use 18:9/19:9 aspect ratio or whatever instead of it being cropped?
Click to expand...
Click to collapse
No idea if any rom has settings for 18:9/19:9 displays. But there's also the notch that covers the screen. In OOS we can hide the notch, but in Treble roms the notch will cover some parts of the screen in all apps. YouTube should support 18:9/19:9 though. Maybe there is some app that can help with the notch? Or some Magisk module? I think that GravityBox should allow us to resize status bar so that apps won't be covered, but games hide the status bar so it will be useless in games. We might have to wait for Android P to take care of all the notch problems in GSIs.

Thank you for this!!
How is the camera on treble roms?

I think we need to wait P for notch support, or maybe some modders can do something

Thanks for this guide. Looking forward to trying it out. With that said, just so I have my bases covered - What's the best way return to stock OOS if necessary?
Thanks!

I don't think calling works yet, I am getting a soft reboot every time I try.

azsl1326 said:
Thanks for this guide. Looking forward to trying it out. With that said, just so I have my bases covered - What's the best way return to stock OOS if necessary?
Thanks!
Click to expand...
Click to collapse
I got mine back to stock by following this: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665

sis3970 said:
I got mine back to stock by following this: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
Thanks. Did you try this Treble version?

azsl1326 said:
Thanks. Did you try this Treble version?
Click to expand...
Click to collapse
No. Not yet. Planning to tonight.
Verstuurd vanaf mijn ONEPLUS A6003 met Tapatalk

sis3970 said:
No. Not yet. Planning to tonight.
Verstuurd vanaf mijn ONEPLUS A6003 met Tapatalk
Click to expand...
Click to collapse
Same for me. Also found this forum on XDA for Treble development - https://forum.xda-developers.com/project-treble/trebleenabled-device-development

No boot for me and phhusson, this guide does nothing different then what is mentioned already here as not working > https://forum.xda-developers.com/oneplus-6/help/dev-oneplus-6-luck-treble-seeking-help-t3795202
Tested on a total of 3 devices, no boot on neither, tho Mishaal just told me he got a boot, so it most be something else somewhere we have not yet identified.
Until then I would put a big EXPERIMENTAL and DANGEROUS on this thread.

Can confirm this works, our display tester Dylan Raga got the LineageOS GSI booting.

MishaalRahman said:
Can confirm this works, our display tester Dylan Raga got the LineageOS GSI booting.
Click to expand...
Click to collapse
Exelios said:
tho Mishaal just told me he got a boot, so it most be something else somewhere we have not yet identified.
Click to expand...
Click to collapse
If phh cannot get a boot on his own rom...

Disable Force Encryption Explained And With Benefits

I'll get straight into the matter at hand.
DFE basically disables all the encryption the phone uses. Now that is explained let's get into the benefits of disabling it.
-Battery Life Improvement
-Slighty Better Response Times
So from looking at this you can say that it hardly does anything in terms of making your life easier.
Let's get to the verdict:
If you don't care about security and you trust yourself then i encourage you to disable it
Any mods that will make your experience better is a plus in my book.
P.s: If you are installing any type of gsi then you don't have any choice but to disable it.
Hope this helped you in someway or another.

It's more convenient. Everything else is a bonus.

Does my phone get re-encrypted when i flash a new rom build (pixel experiance) or a new firmware ? I dont get that part.

KabalLV said:
Does my phone get re-encrypted when i flash a new rom build (pixel experiance) or a new firmware ? I dont get that part.
Click to expand...
Click to collapse
DFE patches vendor.

Martensite said:
DFE patches vendor.
Click to expand...
Click to collapse
That's actually wrong information it only patches the android framework so like @KabalLV says the phone gets encrypted every time you wipe and install.

MechaNarutoSucks said:
That's actually wrong information it only patches the android framework so like @KabalLV says the phone gets encrypted every time you wipe and install.
Click to expand...
Click to collapse
I find fix.sh in the dfe.zip. I think this is how magic happen.
#!/sbin/sh
find /vendor/etc -name "fstab.*" -exec sed -i 's/forceencrypt/encryptable/g' {} +
find /vendor/etc -name "fstab.*" -exec sed -i 's/forcefdeorfbe/encryptable/g' {} +
find /vendor/etc -name "fstab.*" -exec sed -i 's/fileencryption/encryptable/g' {} +
And it was fine when I forget to flash dfe with already patched vendor.

MechaNarutoSucks said:
That's actually wrong information it only patches the android framework so like @KabalLV says the phone gets encrypted every time you wipe and install.
Click to expand...
Click to collapse
No.
Encryption is defined in late-stage fstab, and on treble devices that fstab is at /vendor/etc/

CosmicDan said:
No.
Encryption is defined in late-stage fstab, and on treble devices that fstab is at /vendor/etc/
Click to expand...
Click to collapse
Encryption happens in vendor/etc partition thats why when you try to update your device's vendor/firmware, the patch (DFE) will be overwritten with the new files thus enabling the encryption again. But updating only the system (like dirty flashing new LineageOS Rom like OTA update via TWRP [old build > new build]) it won't overwrite vendor/firmware thus the encryption stays the same (if enabled or disabled via patch)

Darklouis said:
Encryption happens in vendor/etc partition thats why when you try to update your device's vendor/firmware, the patch (DFE) will be overwritten with the new files thus enabling the encryption again. But updating only the system (like dirty flashing new LineageOS Rom like OTA update via TWRP [old build > new build]) it won't overwrite vendor/firmware thus the encryption stays the same (if enabled or disabled via patch)
Click to expand...
Click to collapse
Why are you replying to me lol....
Anyway, MIUI ROMs (the custom ones) all seem to include vendor too, which may or may not have FDE disabled.
It's perfectly fine to just flash FDE disable/optional any time, if it's already applied then it won't hurt. Unless it's a toggle script, which I haven't seen anywhere because that'd be annoying.
Sent from my POCOPHONE F1 using Tapatalk

CosmicDan said:
Why are you replying to me lol....
Anyway, MIUI ROMs (the custom ones) all seem to include vendor too, which may or may not have FDE disabled.
It's perfectly fine to just flash FDE disable/optional any time, if it's already applied then it won't hurt. Unless it's a toggle script, which I haven't seen anywhere because that'd be annoying.
Sent from my POCOPHONE F1 using Tapatalk
Click to expand...
Click to collapse
Just giving out additional info.. Hahahaha

CosmicDan said:
Why are you replying to me lol....
Anyway, MIUI ROMs (the custom ones) all seem to include vendor too, which may or may not have FDE disabled.
It's perfectly fine to just flash FDE disable/optional any time, if it's already applied then it won't hurt. Unless it's a toggle script, which I haven't seen anywhere because that'd be annoying.
Click to expand...
Click to collapse
That may be true but everytime i reflash the encryption turns on. So i don't know the exact answer but that's the out outcome of reflashing at least for me.

after flashing each update via twrp, should i flash DFE then magisk or it is needed once?

MechaNarutoSucks said:
That may be true but everytime i reflash the encryption turns on. So i don't know the exact answer but that's the out outcome of reflashing at least for me.
Click to expand...
Click to collapse
Because you're flashing MIUI? The ROM you're flashing, whatever it is, must have its own vendor. Open the ZIP on PC and check yourself if it has vendor.new.dat.br - there is your answer.
hosseinito said:
after flashing each update via twrp, should i flash DFE then magisk or it is needed once?
Click to expand...
Click to collapse
Just flash it again if in doubt, as said it can't do any harm.
Sent from my POCOPHONE F1 using Tapatalk

Is there a reason to still be using 18.0 DFE and not 18.1? Also I have magisk v19 installed. If I update this rom (10.3.4.0|9.4.1) should I flash dfe 18.1 and re-flash magisk v18.1 for the purpose? Thanks

CosmicDan said:
Because you're flashing MIUI? The ROM you're flashing, whatever it is, must have its own vendor. Open the ZIP on PC and check yourself if it has vendor.new.dat.br - there is your answer.Just flash it again if in doubt, as said it can't do any harm.
Click to expand...
Click to collapse
Ok then. Thank you?

CosmicDan said:
Because you're flashing MIUI? The ROM you're flashing, whatever it is, must have its own vendor. Open the ZIP on PC and check yourself if it has vendor.new.dat.br - there is your answer.Just flash it again if in doubt, as said it can't do any harm.
Click to expand...
Click to collapse
Like i said i don't know the exact idea on it so thx for the explanation.
And its true that i only update my rom when there is a new firmware update.

Can I just flash the DFE file in TWRP without wiping data or anything else? Right now I have Lineage installed with everything set up and I would not wipe everything right now just to flash DFE.

Hi i am on global 10.3.5 stable, rooted with magisk and twrp is not installed (only hot booted).
1. Can i just flash dfe?
2 what about ota update? If i just flash dfe Will it ask for any pin after doing ota update?? Or i can just update and then flash dfe again
3. Also i have one doubt. i flashed pixel rom once and i decided to revert back to miui. So i restored my twrp backup of miui and got bootloop. Then i flashed the 10.3.5 zip and vendr/firmware also. But after booting it asked me for pin. i had to fastboot flash the rom again. It wiped all my data. So what did i do wrong here. And how to restore miui twrp backup. Coz its really difficult to back up all the data in my phone every time i flash a rom. Thats holding me back from enjoying the custom roms. So any clarification would be highly appreciated. Thanks

MechaNarutoSucks said:
I'll get straight into the matter at hand.
DFE basically disables all the encryption the phone uses. Now that is explained let's get into the benefits of disabling it.
-Battery Life Improvement
-Slighty Better Response Times
So from looking at this you can say that it hardly does anything in terms of making your life easier.
Let's get to the verdict:
If you don't care about security and you trust yourself then i encourage you to disable it
Any mods that will make your experience better is a plus in my book.
P.s: If you are installing any type of gsi then you don't have any choice but to disable it.
Hope this helped you in someway or another.
Click to expand...
Click to collapse
but how do i do it? i only read dfe dfe dfe everywhere but can't find anywhere how to disable encryption

How can you tell the benefits without providing concrete proof? I am running encrypted since I got my POCO and installed LOS16. I haven't encountered any issues at all with regards to performance or battery life.

Project Treble for Xperia X compact

Project Treble For Xperia X Compact
Based on Sony Open Devices
I am not responsible for bricked devices, dead SD cards,.
Big thanks to Sjll member and his tuto to go treble
Suitable for F5321, A-ONLY GSI ROM​
Required files:
[SODP Kernel version]
All necessary files
[OEM-File]
Download Link
[SYSTEM-File]
Tested with some system gsi files, these work properly :
Pixel experience
/e/
POSP
ArrowOS
[SYSTEM-File WITH FixZygote installed via twrp]
Android Q developer preview
Find all GSI system image here and here
How to go Treble ?
First: Flash recovery
Code:
fastboot flash recovery < Path of recovery.img >
Second: Flash boot image
Code:
fastboot flash boot < Path of boot.img >
Third: Flash vendor file
Code:
fastboot flash cache < Path of vendor.img >
Fourth: flash SW_binaries provided by Sony.
You can download it from Sony official website.
Code:
fastboot flash oem < Path of OEM.img >
Fifth: Flash a GSI compatible System image (arm64 A-ONLY) and boot !
Code:
fastboot flash system < Path of GSI-System.img >
Look here first for questions resolving Xperia X thread
Source Codes
Sjll
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2020-05-09
Last Updated 2020-05-23

Hello mate. It's interesting to see different options come up when we started to think that development for XC come to an end. Thanks for this valuable effort. I want to ask a few things.
1- What is your opinion about dreaded problems with 4.9 kernel like random reboots and some reported Wi-Fi issues (although I don't remember I ever had this) etc.
2- recovery is independent of this setup right? I mean can I use twrp as recovery?
3- I suppose we'll be stuck with this boot.img unless personally build another one with synced sources right?
4-One of your cautions was about dead sd card? Is there a predicted risk or was it a general warning?
Again thanks a lot for this. I think I'll give it a try tomorrow may be.
PS: I also would like to know what to look for compatible GSIs. (I tried Phhs' and some other Android 10 GSIs with zygote and permissiver patches but they didn't past the sony logo. Stuck at sony logo or bootloop)
Update: Question 2 answered. No problem with twrp. Erfan's generic 10 gsi booted with zygote and permisiver patches. But stuck at setup screen.

maluus said:
Hello mate. It's interesting to see different options come up when we started to think that development for XC come to an end. Thanks for this valuable effort. I want to ask a few things.
1- What is your opinion about dreaded problems with 4.9 kernel like random reboots and some reported Wi-Fi issues (although I don't remember I ever had this) etc.
2- recovery is independent of this setup right? I mean can I use twrp as recovery?
3- I suppose we'll be stuck with this boot.img unless personally build another one with synced sources right?
4-One of your cautions was about dead sd card? Is there a predicted risk or was it a general warning?
Again thanks a lot for this. I think I'll give it a try tomorrow may be.
PS: I also would like to know what to look for compatible GSIs. (I tried Phhs' and some other Android 10 GSIs with zygote and permissiver patches but they didn't past the sony logo. Stuck at sony logo or bootloop)
Update: Question 2 answered. No problem with twrp. Erfan's generic 10 gsi booted with zygote and permisiver patches. But stuck at setup screen.
Click to expand...
Click to collapse
1 - I don't know about these problems, I was with 3.x kernel before but you can rebuild the kernel of your choice (it doesn't take too much time) by changing the .dtsi file corresponding to our device
2 - Yes but do not wipe the cache, as the vendor image is in it
3 - Yes, but it doesn't take too much time to build it, share if you do
4 - Just a general warning, not experienced

maluus said:
Hello mate. It's interesting to see different options come up when we started to think that development for XC come to an end. Thanks for this valuable effort. I want to ask a few things.
1- What is your opinion about dreaded problems with 4.9 kernel like random reboots and some reported Wi-Fi issues (although I don't remember I ever had this) etc.
2- recovery is independent of this setup right? I mean can I use twrp as recovery?
3- I suppose we'll be stuck with this boot.img unless personally build another one with synced sources right?
4-One of your cautions was about dead sd card? Is there a predicted risk or was it a general warning?
Again thanks a lot for this. I think I'll give it a try tomorrow may be.
PS: I also would like to know what to look for compatible GSIs. (I tried Phhs' and some other Android 10 GSIs with zygote and permissiver patches but they didn't past the sony logo. Stuck at sony logo or bootloop)
Update: Question 2 answered. No problem with twrp. Erfan's generic 10 gsi booted with zygote and permisiver patches. But stuck at setup screen.
Click to expand...
Click to collapse
1 - I don't know about these problems, I was with 3.x kernel before but you can rebuild the kernel of your choice (it doesn't take too much time) by changing the .dtsi file corresponding to our device
2 - Yes but do not wipe the cache, as the vendor image is in it
3 - Yes, but it doesn't take too much time to build it, share if you do
4 - Just a general warning, not experienced
Normally I set the selinux to permissive so no need to apply the permissiver patch
PS : sometimes it goes into bootloop but if you reboot it starts like a charm (test that with POSP 10)
PS2 : Mobile network does not work with Q roms, if you success to make it work please share
PS3 : POSP Pie works fine

Tell me if I'm thinking of installing Project Treble.
1.Flash all sections through the fastboot?
2.Ask for recovery what is in the link on the github?
3.Ask for a boot link on github?
4.Select vendor.img in the cache section?
5.What to ask for?
6.Select a suitable GSI image and boot again?
If somewhere I am wrong correct me. I'm sorry I'm new to this.

bioshp said:
Tell me if I'm thinking of installing Project Treble.
1.Flash all sections through the fastboot?
2.Ask for recovery what is in the link on the github?
3.Ask for a boot link on github?
4.Select vendor.img in the cache section?
5.What to ask for?
6.Select a suitable GSI image and boot again?
If somewhere I am wrong correct me. I'm sorry I'm new to this.
Click to expand...
Click to collapse
You can get twrp as recovery but do not wipe cache, as vendor img is flashed in it

Good news that /e/ is working correctly, I was about to try to build a e variant on Chippa's build.
I do have one question. Really new to trebble.
If we wanna root it, we apply usual procedure*? flash the root zip(magisk) in recovery

This is amazing!! Breathing new life in to my XC. Thank you for sharing. Just flashed /e/ and it's working really well so far. Although I see that selinux is not enforced, anyone know why?

can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP

zetchonok said:
can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP
Click to expand...
Click to collapse
Xperia UI GSI also does not start for me. What could be?

zetchonok said:
can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP
Click to expand...
Click to collapse
I tried a lot of them to both android 9 and 10 only /e/ boots and works as 9. For the 10 erfans boots but it includes gapps and that stucks at setup. You can leave it as it s but didn't thoroughly tested it.

zetchonok said:
can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP
Click to expand...
Click to collapse
Try to flash userdata also

bioshp said:
Xperia UI GSI also does not start for me. What could be?
Click to expand...
Click to collapse
Q or Pie ROM ?

maluus said:
I tried a lot of them to both android 9 and 10 only /e/ boots and works as 9. For the 10 erfans boots but it includes gapps and that stucks at setup. You can leave it as it s but didn't thoroughly tested it.
Click to expand...
Click to collapse
POSP boots as much of the Pie Gsi, 10 are more capricious (POSP 10 boots for example, but sim is not detected)

betacrypt said:
This is amazing!! Breathing new life in to my XC. Thank you for sharing. Just flashed /e/ and it's working really well so far. Although I see that selinux is not enforced, anyone know why?
Click to expand...
Click to collapse
To avoid SELinux policy errors and fail to boot

nervousapp said:
POSP boots as much of the Pie Gsi, 10 are more capricious (POSP 10 boots for example, but sim is not detected)
Click to expand...
Click to collapse
Then probably erfans 10 is better. Because sim Wi-Fi camera etc works. Just didn't tested thoroughly. Only downside setup doesn't complete. Personally I don't use Google services so no problem for me but setup notification persists like it tries to complete setup but doesn't actually progress.

I flashed /e/ and it's pretty stable and smooth but my device is overheating when charging and even when it's idle and the display is off. I'm getting severe battery drain from it.
EDIT: Wiping all the partitions and flashing from scratch seems to have done the trick.

I've been using Arrow OS and it's pretty stable and smooth so far. Comes with GApps built-in and Jan 2020 security patch:
https://sourceforge.net/projects/arrow-os/files/arrow-9.x/GSI/27_Jan_2020/

maluus said:
Then probably erfans 10 is better. Because sim Wi-Fi camera etc works. Just didn't tested thoroughly. Only downside setup doesn't complete. Personally I don't use Google services so no problem for me but setup notification persists like it tries to complete setup but doesn't actually progress.
Click to expand...
Click to collapse
Hello! You can describe in detail how you installed it, how many have not tried to get further Sony does not work.

mister-13x said:
Hello! You can describe in detail how you installed it, how many have not tried to get further Sony does not work.
Click to expand...
Click to collapse
I didn't anything extraordinary follow the steps in the first post. (Since android version would change I formatted data) use erfanoabdis' unofficial Q gsi which you can find a link at phhusson' gsi images link list. (You can also find the link to phussons list in the first post)

Question [HELP] I keep failing trying to flash a custom Android 12 ROM on the Redmi Note 11 Pro (veux). Can someone help me figure out what I'm doing wrong?

I've owned Samsung, Lenovo and Moto phones before, and I never had any problems unlocking them and flashing custom recoveries and ROMs. This is my 2nd Xiaomi phone and like the 1st I keep bricking and unbricking it. The only thing I can manage to do is sometimes get TWRP on it, or the normal ROM.
- Version: European version of the Redmi Note 11 Pro, codename veux.
- TWRP: https://forum.xda-developers.com/t/twrp-3-7-0_12-for-veux-peux.4520689/
- ROM: https://forum.xda-developers.com/t/rom-13-veux-peux-official-evolution-x-11-09-22.4497785/
___
1st attempt:
1 - After unlocking the bootloader it reinstalled a clean ROM. I then forgot to turn USB debugging on so that was my fault. Because after that I went into fastboot and flashed this TWRP with fastboot flash boot name.img
2 - On this first try I then rebooted to recovery, but it sent me to the normal one instead. In essence I bricked it so I followed this guide to reset it
___
2nd attempt:
1 - I enable USB debugging
2 - go into fastboot: fastboot flash boot name.img
3 - reboot to recovery
4 - in TWRP I try to flash the ROM from the internal storage. It fails after around 33% or something. Errors about not being able to mount certain folders
___
3rd attempt:
1 - reboot to recovery
2 - try and sideload the ROM from my laptop with the command adb sideload name.zip
3 - fails around 40% with similar errors
___
4th attempt:
1 - reboot to bootloader
2 - try instead fastboot boot name.zip to flash the ROM. It gives me the error: requested download size is more than max allowed fastboot
___
In between these tries TWRP sometimes loses touchscreen functionality. I notice when I flash OrangeFox and then TWRP again, I get touchscreen functionality back. I know this is a well known issue but it's interesting I can back TWRP working again when doing the above.
Another interesting is that when I flash OrangeFox and reboot to recovery, it's still TWRP.

When you flash a new ROM, you need to format the userdata and the cache partitions.
EDIT:
Btw, i'm curious to know where you found your OrangeFox build. ^^

Sneilas said:
When you flash a new ROM, you need to format the userdata and the cache partitions.
EDIT:
Btw, i'm curious to know where you found your OrangeFox build. ^^
Click to expand...
Click to collapse
I believe I did format data, cache and dalvik cache as usual. Hm, will check again.
I forgot where I got the OrangeFox from. Might be nothing though.

kerelberel said:
I believe I did format data, cache and dalvik cache as usual. Hm, will check again.
I forgot where I got the OrangeFox from. Might be nothing though.
Click to expand...
Click to collapse
Btw, i do not recommand to flash unofficial images if the maintainer not released it's device tree on GitHub and not linked it on his thread.
We can't know what's inside the recovery.
The recovery can be infected by a malicious code.

Sneilas said:
When you flash a new ROM, you need to format the userdata and the cache partitions.
EDIT:
Btw, i'm curious to know where you found your OrangeFox build. ^^
Click to expand...
Click to collapse
So I made sure to format everything this time. But because I am stoopid I then accidentally sideloaded a MIUI ROM instead of Evolution. I copy/pasted the wrong file name in the cmd window, lol. I was surprised to see the Evolution logo after rebooting, so I got the ROM I wanted by accidentally flashing the other one.
Do I have MIUI on one partition and Evolution on the other? Is that even possible?

kerelberel said:
So I made sure to format everything this time. But because I am stoopid I then accidentally sideloaded a MIUI ROM instead of Evolution. I copy/pasted the wrong file name in the cmd window, lol. I was surprised to see the Evolution logo after rebooting, so I got the ROM I wanted by accidentally flashing the other one.
Do I have MIUI on one partition and Evolution on the other? Is that even possible?
Click to expand...
Click to collapse
From here, i recommand you to ask the maintainer of the Evolution X ROM of your device.
Send him your device infos (code name, processor, etc...).
If you can't access to these info on from phone, contact the reseller of your phone.
Maybe your specific device is not compatible with the ROM.
I'm not enough experienced to help you more.

I don't know if twrp works on veux.
I flashed the boot.img and vendor_boot.img provided by the custom ROM.
The custom ROM was updated using the sideload in recovery mode.
It must be unlocked. USB debug doesn't matter.

Sneilas said:
From here, i recommand you to ask the maintainer of the Evolution X ROM of your device.
Send him your device infos (code name, processor, etc...).
If you can't access to these info on from phone, contact the reseller of your phone.
Maybe your specific device is not compatible with the ROM.
I'm not enough experienced to help you more.
Click to expand...
Click to collapse
I'm fine now, the ROM works, afterwards I also installed Magisk successfully so TWRP works as expected too.
osebee said:
I don't know if twrp works on veux.
I flashed the boot.img and vendor_boot.img provided by the custom ROM.
The custom ROM was updated using the sideload in recovery mode.
It must be unlocked. USB debug doesn't matter.
Click to expand...
Click to collapse
It does, the one I linked in my first post is the one from this specific subforum.
If you need help you can PM me.

Seems like you've managed to fix the problem, and USB debugging only works when you're booted inside the rom, it doesn't do anything in recovery/fastboot.

kerelberel said:
I'm fine now, the ROM works, afterwards I also installed Magisk successfully so TWRP works as expected too.
It does, the one I linked in my first post is the one from this specific subforum.
If you need help you can PM me.
Click to expand...
Click to collapse
Oh ok, i thought you still had problems. ^^

Ritik17 said:
Seems like you've managed to fix the problem, and USB debugging only works when you're booted inside the rom, it doesn't do anything in recovery/fastboot.
Click to expand...
Click to collapse
USB debugging works in some stock/custom recoveries, but in stock recoveries it is limited to sideloading updates signed by the device manufacturer.