Database Info

HP Slatebook X2 - maya - development thread (recovery,root)

This is a development thread, if your question belongs to general topic, please check the General topic
IMPORTANT : if you've just bought the device, and it is still under 4.2, DO NOT UPDATE with OTA. You would not be able to root the device (unless you buy an expensive cable)
STATUS
TWRP is fully working - selinux is available
On 4.2.2, Root is available via two methods : with cable improved here (great work guys) or without by using Towelroot
On 4.3, root is only achievable with the cable method : unlocking bootloader, booting recovery and flashing the supersu.zip
Recovery, root and unlock
Recovery (updated on 27/02/2015)
On bootloader, you can either :
1) boot it : fastboot -i 0x03F0 boot recovery.img (adapt to .img filename)
2) flash it : fastboot -i 0x03F0 flash recovery recovery.img (adapt to .img filename)
flashing it allows to have access to recovery directly, you need to keep pressing volume down when switching on the tab.
TWRP 2.8.1 Recovery (flashable)
HP's recovery
Rom available
MayaMod - cooked by juanig
Prerooted latest OTA Rom : 4.3-17r20-05-24 STOCK ROOTED : Thanks juanig (mirror by mrzood)
Misc
Partition infos
Data cable ref : 728141-001 SPS-Micro USB to USB - Mandatory to unlock bootloader and flash custom rom Picture
Rooting
With your bootloader unlocked (by cable), flash the supersu zip linked here
If you didn't update to 4.3, you can root with Towelroot v1 (thanks to mrzood for hosting)
once root, you can unlock your bootloader if not yet done.
Unlocking bootloader
With a cable : fastboot -i 0x03F0 oem unlock. WARNING: this will reset your tablet to factory default and loose all your data
By flashing a file, you need to be root : all info there (great work guys)
Sources
HP has released 4.2.2 source code, mirrored here
HP has now released 4.3 source code here mirrored here (thanks Scratz)
My device tree
Archives :
TWRP 2.8 Recovery (flashable)
TWRP 2.7.0 Recovery (flashable) (thanks to Juanig for testing)
CWN recovery - booting but partially working
TWRP - booting but partially working

--

Indeed, I'll update op on that point.
In addition, I need testers for twrp new release, as I don t have my cable yet

Addition of partition layout information

I'll give the new TWRP a try when I have some free time today.

Latest TWRP seems to work fine. Did not cause any softbricking.
Now I just need to make a working 4.2.2 zip to try and flash over my 4.3 install.
Works:
- Backup to external SD (tablet ext SD, did not test dock SD slot.)
- Restore from SD
- Wakes via touchpad/keyboard
- Mounts
- File browser
- Reboots to system and bootloader
Broken:
- Mouse pointer. It's there but does not move when using touchpad.
Here's a 14mb log file that I copied to SD if you wish to view: http://files.mrzood.com/14-7-8.1758zulu.recovery.log

Good news ! Did you flash it or boot on it ?

BENETNATH said:
Good news ! Did you flash it or boot on it ?
Click to expand...
Click to collapse
Flashed.

Ok, so could you do a full backup and share it with me ?

BENETNATH said:
Ok, so could you do a full backup and share it with me ?
Click to expand...
Click to collapse
Sent you a PM with the download link to the zipped backup.

Good work guys and thanks to Ben for starting the development thread. I'll spread the word to a HP forum and also to a Google+ Slatebook site as well.
EDIT: Just had another look at the price of the cable on the HP website and it's gone up to AUD $78!! HP are really not helping our cause here are they?

GrievousMcG said:
Good work guys and thanks to Ben for starting the development thread. I'll spread the word to a HP forum and also to a Google+ Slatebook site as well.
EDIT: Just had another look at the price of the cable on the HP website and it's gone up to AUD $78!! HP are really not helping our cause here are they?
Click to expand...
Click to collapse
i had no reply from their VP HP' assistance..
sad, sad situation.
For people with a cable, and interested in testing a custom rom with TWRP, here is one :
http://www.mediafire.com/download/bk92dlpdctt95tu/cm-10.1-20140704-UNOFFICIAL-maya.zip

BENETNATH said:
i had no reply from their VP HP' assistance..
sad, sad situation.
For people with a cable, and interested in testing a custom rom with TWRP, here is one :
http://www.mediafire.com/download/bk92dlpdctt95tu/cm-10.1-20140704-UNOFFICIAL-maya.zip
Click to expand...
Click to collapse
Flashed. Will not boot. Tired re-flash, wipe data, etc. Had to restore back to HP ROM

thanks for confirming

New build is online :
https://mega.co.nz/#!EBdWAILa!oFF9kSAGbN2OGhG6Jeu_qMLqLN2aBuU4kaKKZ6m8G9w

device tree added in OP
still no cable..it might became painful to be stuck without rom testing capabilities..

addition of a CM10.2 rom to test.
without testers, i'm stuck currently..

BENETNATH said:
addition of a CM10.2 rom to test.
without testers, i'm stuck currently..
Click to expand...
Click to collapse
My Slatebook is on the way, if I find a cable for a reasonable price I would be happy to test...

I got problem.
Do you have original recovery for reflash it?
I cannot try the 4.3 update with custom recovery (fail).
Can i try to flash CM 10.2 directly over the custom recovery?
At this time, i did a backup of 4.2.2 and restore it succesfully.
Thanks for your hard work.
I dont have the cable.

Without cable, your boot loader is not unlocked. You cannot flash a custom Rom.

[RECOVERY][THEA] TWRP 3.2.3-0 Touch Recovery [OFFICIAL]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
DOWNLOAD : https://dl.twrp.me/thea/
BUGS:
If you have found a bug, please consider posting it to our github issues log and then I'll report to Dess_Troy. If you have a significant problem that cannot be answered in this thread, your best bet is to PM Dees_Troy directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[RECOVERY][THEA] TWRP 3.2.3-0 Touch Recovery [OFFICIAL], ROM for the Moto G 2014 LTE
Contributors
luca020400, LuK1337
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Created 2016-02-07
Last Updated 2018-08-07

Reserved

Reserved
Source code : motog2014devteam
Source code : CyanogenMod

ok and how can we install it?

javierutxo said:
ok and how can we install it?
Click to expand...
Click to collapse
fastboot flash recovery file.img

LuK1337 said:
fastboot flash recovery file.img
Click to expand...
Click to collapse
aja, and what about unlock bootloader and rooting? the same process than moto g 2014?

javierutxo said:
aja, and what about unlock bootloader and rooting? the same process than moto g 2014?
Click to expand...
Click to collapse
Yes

javierutxo said:
ok and how can we install it?
Click to expand...
Click to collapse
Take the steps from here http://forum.xda-developers.com/moto-g-2015/general/rooting-moto-g-2015-lte-xt1078-t3086069
Just change the twrp.mg for the one in this post.
Good Luck!

Thank you!! Its worked for me on XT1072

Hello, It worked just fine on my XT1078
Thanks!

Is it possible to make this an "official" release ?

551790 said:
Is it possible to make this an "official" release ?
Click to expand...
Click to collapse
Yes , but I'm not going to do that

luca020400 said:
Yes , but I'm not going to do that
Click to expand...
Click to collapse
Hi Luca! Can you explain shortly how you built this image? Any manual that you can point me to?
I'm asking because I'd like to build it also for peregrine...

New build up
Download

idk whats happening. i unlocked my phone and installed this recovery and when i try to enter in recovery mode it shows and android with the exclamation sign and never continues to the actual recovery. it just stays there forever and then reboots by itself. can anyone tell me what is wrong?

Maledroid said:
idk whats happening. i unlocked my phone and installed this recovery and when i try to enter in recovery mode it shows and android with the exclamation sign and never continues to the actual recovery. it just stays there forever and then reboots by itself. can anyone tell me what is wrong?
Click to expand...
Click to collapse
You haven't flashed twrp
Reboot to bootloader
By pc
fastboot flash recovery twrp-thea.img
( with admin/sudo )
Then reboot to recovery

luca020400 said:
New build up
Download
Click to expand...
Click to collapse
Hi Luca, thank you very much for your hard work on this device.
About this new release of TWRP, I'd like to know, if possible, what are the main differences with the previuos one.

cgb.spender said:
Hi Luca, thank you very much for your hard work on this device.
About this new release of TWRP, I'd like to know, if possible, what are the main differences with the previuos one.
Click to expand...
Click to collapse
TWRP fixes
The TWRP version still 2.8.6 but it's 2.8.7

My encrypted TWRP nandroid backups fail with the following error message:
E:createTarFork() process ended with ERROR=255
Click to expand...
Click to collapse
This only happens when I use encryption, and it always happens right near the end of backing up the Data partition (the System partition backup completes successfully).
N.B. The percentage of files and MB processed do not increase in-step, like with an unencrypted backup. The MB percentage increases to 90%+ far quicker than the percentage of files processed. When the percentages come in-line with each other near the end of the Data partition backup, it fails, and the above error message is given.
I was using a Titan build of TWRP to create nandroid backups on my Thea device previously, and had no issues with encrypted backups.
This is an issue, as there are sensitive security details stored in the backup, which must be encrypted with a strong password.

Internal Storage failure?
sunka1 said:
My encrypted TWRP nandroid backups fail with the following error message:
....
Click to expand...
Click to collapse
This happens to me all the time all of a sudden. I did not change anything at all, except for flashing a new CM version.
I also get a strange stat error, something with google.photo cache.
Yesterday, I have then flashed the new 2.8.6(7). from a few posts above and that gave my phone the rest. It might be because I flashed through TWRP itself into the recovery partition, but now additional to the backup error above when I want to erase dalvik cache, the recovery just hangs. I also can't restore a backup atm.
Now I have reflashed the real 2.8.6.0 recovery and it still hangs when I want to wipe dalvik... wtf is going on here?
And oh yea, my phone does not boot anymore either, it just loops at the flash screen...
UPDATE:
After I found some info on this thread about similar issues, I factory reset my phone with stock recovery (TWRP was not reliable anymore, even the 2.8.6.0 version that was running perfectly before) and then reflashed the latest CM on a wiped internal storage. Now I am up and running again with minimal loss of data due to my TB backups that are scheduled and save to the SD.
But this leaves a very weird feeling back, basically my phone was rendered useless out of nowhere (I was running the previous CM for 2 weeks already), making TWRP backups impossible and forcing me to wipe the internal storage with all media on it without giving me the chance to back it up (MTP in TWPR was also very flaky and died several times half in copy operations). Something is going very wrong with this phone, never ever had that on any of my 5 previous htc devices and the fact that the OnePlusOne users are among the main ones that reported similar issues, I have a feeling it is linked to cheap storage quality. Motorola is a Chinese company now after all... :-/

OPO can't boot into custom recovery CM11.0

Hello all!
Newly registered here, has been lurking around for some time though.
I just received my replacement OnePlus due to the death of the first one and wanted to do a custom recovery and install Oxygen or Carbon for a little better battery life and back up possibilities.
My problem is: I can't get the phone to boot into recovery.
I did some research and people mentioned trying TWRP and PhilZ's recoveries - those had no result for me.
I have followed official video from OnePlus and also tried C4ETech's way for those two mentioned above.
The ones I tried were PhilZ's 6.50.2 and 6.58.8, for TWRP I used 2.8.5.1 and 2.8.4.1
Tried to do it with OPO toolbox and that didn't work either (TWRP, CWM, PhilZ tested)- all the functions would work, but once I flash the phone - it would boot into stock CM11.
When I try to boot it into recovery, it would stay on the first logo for 7-8 seconds, after that vibrates again and goes into stock CM11.
The same would happen if I go to advanced boot and boot into recovery.
I have changed the options under Developers folder as required already.
I have tried flashing the phone on two computers - win7 x64 and Win 8.1 x64.
Any help would be appreciated.
I have the phone for almost two weeks already and still can't ring myself to setting it up because of previous experience of data loss. (not worried about pictures - those are on Gdrive )

format c:\ said:
Hello all!
Newly registered here, has been lurking around for some time though.
I just received my replacement OnePlus due to the death of the first one and wanted to do a custom recovery and install Oxygen or Carbon for a little better battery life and back up possibilities.
My problem is: I can't get the phone to boot into recovery.
I did some research and people mentioned trying TWRP and PhilZ's recoveries - those had no result for me.
I have followed official video from OnePlus and also tried C4ETech's way for those two mentioned above.
The ones I tried were PhilZ's 6.50.2 and 6.58.8, for TWRP I used 2.8.5.1 and 2.8.4.1
Tried to do it with OPO toolbox and that didn't work either (TWRP, CWM, PhilZ tested)- all the functions would work, but once I flash the phone - it would boot into stock CM11.
When I try to boot it into recovery, it would stay on the first logo for 7-8 seconds, after that vibrates again and goes into stock CM11.
The same would happen if I go to advanced boot and boot into recovery.
I have changed the options under Developers folder as required already.
I have tried flashing the phone on two computers - win7 x64 and Win 8.1 x64.
Any help would be appreciated.
I have the phone for almost two weeks already and still can't ring myself to setting it up because of previous experience of data loss. (not worried about pictures - those are on Gdrive )
Click to expand...
Click to collapse
Are you checking the md5 of the recovery files after downloading to ensure that they haven't become corrupt during the download? Exactly which recoveries have you flashed (full filenames please)? Also, is the flash with fastboot definitely succeeding? I'd suggest not using a toolkit because they inevitably cause problems.

Heisenberg said:
Are you checking the md5 of the recovery files after downloading to ensure that they haven't become corrupt during the download? Exactly which recoveries have you flashed (full filenames please)? Also, is the flash with fastboot definitely succeeding? I'd suggest not using a toolkit because they inevitably cause problems.
Click to expand...
Click to collapse
I did verify the checksums for TWRP recovery files. They matched.
The ones I used: openrecovery-twrp-2.8.4.1-bacon and openrecovery-twrp-2.8.5.1-bacon
I was not able to find md5 data for PhilZ files, just certificates.
I tried toolkit after going through command prompt. I'm not sure if it is succeeding, nothing happens as far as phone rebooting by itself. The process seems to run and say that it was successful in the prompt.
Do you want me to go though it and post the screenshot?
I've tried not doing "fastboot reboot" command, as it was mentioned in the "Noobs" section - still no result.

format c:\ said:
I did verify the checksums for TWRP recovery files. They matched.
The ones I used: openrecovery-twrp-2.8.4.1-bacon and openrecovery-twrp-2.8.5.1-bacon
I was not able to find md5 data for PhilZ files, just certificates.
I tried toolkit after going through command prompt. I'm not sure if it is succeeding, nothing happens as far as phone rebooting by itself. The process seems to run and say that it was successful in the prompt.
Do you want me to go though it and post the screenshot?
I've tried not doing "fastboot reboot" command, as it was mentioned in the "Noobs" section - still no result.
Click to expand...
Click to collapse
Forgot to add philz_touch_6.50.2-bacon and philz_touch_6.58.8-bacon were used.

format c:\ said:
I did verify the checksums for TWRP recovery files. They matched.
The ones I used: openrecovery-twrp-2.8.4.1-bacon and openrecovery-twrp-2.8.5.1-bacon
I was not able to find md5 data for PhilZ files, just certificates.
I tried toolkit after going through command prompt. I'm not sure if it is succeeding, nothing happens as far as phone rebooting by itself. The process seems to run and say that it was successful in the prompt.
Do you want me to go though it and post the screenshot?
I've tried not doing "fastboot reboot" command, as it was mentioned in the "Noobs" section - still no result.
Click to expand...
Click to collapse
Is there any reason you're flashing older versions of TWRP? They're pretty outdated now. Grab the latest version from here:
https://dl.twrp.me/bacon/twrp-2.8.7.0-bacon.img.html
As long as it says it's successful in the terminal window it should have flashed ok. What build of CM is currently on your phone?

Heisenberg said:
Is there any reason you're flashing older versions of TWRP? They're pretty outdated now. Grab the latest version from here:
As long as it says it's successful in the terminal window it should have flashed ok. What build of CM is currently on your phone?
Click to expand...
Click to collapse
It did work! Now I'm a happy camper Trying to install Oxygen right now.
It was on 11.0. My old phone was running that OS as well, but it was having issues with screen artifacts I have upgraded to 12.0 and system was running fine for 2 day, after that screen died completely. Buttons at the bottom of the phone were working, but it looked like just the back light was on.
Huge thanks to you, Heisenberg!

I was flashing older versions, because I found only those from the official video link. It sent me to techerrata page and the latest one over there was and still is 2.8.5.1

format c:\ said:
It did work! Now I'm a happy camper Trying to install Oxygen right now.
It was on 11.0. My old phone was running that OS as well, but it was having issues with screen artifacts I have upgraded to 12.0 and system was running fine for 2 day, after that screen died completely. Buttons at the bottom of the phone were working, but it looked like just the back light was on.
Huge thanks to you, Heisenberg!
Click to expand...
Click to collapse
format c:\ said:
I was flashing older versions, because I found only those from the official video link. It sent me to techerrata page and the latest one over there was and still is 2.8.5.1
Click to expand...
Click to collapse
Awesome, very glad to see you got it working. I realised after my post that your current CM version is in the title of the thread, lol, oops. That Techarrata site doesn't get updated anymore as they have a new site now, so the latest builds can always be found here:
https://dl.twrp.me/bacon/

[ROM][7.1.2][v521][OFFICIAL] LineageOS 14.1 LG G-Pad X 8.0 v521[Nightly]

LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for Lineage OS is available in the Lineage OS Github repo.
Install instructions:
* Reboot into recovery
* Wipe data, system and cache if it's a fresh install (any rom which is not official Lineage, including Cyanogenmod).
* No wipes required if you're updating from a previous official build of Lineage (wipe cache and dalvik cache recommended).
* Flash ROM and, optionally, Gapps and Root. Reboot.
Download links:
* OfficialROM: https://download.lineageos.org/v521 [nightly]
* Gapps: Open GApps
* Root: https://download.lineageos.org/extras [su (arm)]
Source Code: https://github.com/LineageOS
Version Information
Status: Nightly
Last Updated 2017-04-28

I have flashed your build and all is well so far except for the Developer Options isn't accessable. I only use this for the Advanced reboot options and root access options. Any way to get this accessable or should I wait for the next build? Thanks

Hawksronny said:
I have flashed your build and all is well so far except for the Developer Options isn't accessable. I only use this for the Advanced reboot options and root access options. Any way to get this accessable or should I wait for the next build? Thanks
Click to expand...
Click to collapse
The past couple of builds somehow broke the Developer Options. Im going to guess and say it has something to do with the code for 7.1.2 being merged as there have been a lot of things changed in the Settings repo. Ive been trying to use older Settings and Developer apks but none have worked.

I have narrowed down the boot issue to the sepolicy file inside the ramdisk.

On the latest build developer options is just a white blank screen. . Now I can't figure out how to get into recovery mode, I usually just boot into recovery through adb but I can't use adb without turning on USB debugging

pdxmark78 said:
On the latest build developer options is just a white blank screen. . Now I can't figure out how to get into recovery mode, I usually just boot into recovery through adb but I can't use adb without turning on USB debugging
Click to expand...
Click to collapse
no need to wipe if coming from previous nightly. if u dnt wipe u can keep ur adb and root options without needing to go into developer settings.
to get into recovery hold vol. down and power until the LG screen appears
then let go of the power button ,while still holding the vol dwn. count 1sec then press and hold power again.
you will be brought to a screen asking if u want to favtory reset press yes then yes again.
it will not wipe anything but it will then reboot in recovery

New build up. Going to work you magic

Munns86 said:
New build up. Going to work you magic
Click to expand...
Click to collapse
Unfortunately the older ramdisk isn't going to work with the new builds as they're 7.1.2. We're going to have to wait until the issue is found and fixed in the source. Ive tried every workaround i can think of ive gotten it as far as a bootloop with the device being recognized in adb, monitor etc. going to try and debug see if i can figure out why its looping.
Looks like the last workung nightly is going to be 04/14, for now.

HighRidas said:
Unfortunately the older ramdisk isn't going to work with the new builds as they're 7.1.2. We're going to have to wait until the issue is found and fixed in the source. Ive tried every workaround i can think of ive gotten it as far as a bootloop with the device being recognized in adb, monitor etc. going to try and debug see if i can figure out why its looping.
Looks like the last workung nightly is going to be 04/14, for now.
Click to expand...
Click to collapse
Well thanks all the same. You've done great work. We've pretty much handed the answer to the maintainer that you've found and they still have done nothing.

i'm keep getting update error. update completes around 45%.. then E:unknown command in red... anyone knows what to do? it goes to boot screen, then blank screen... does not boot.

alphakp295 said:
i'm keep getting update error. update completes around 45%.. then E:unknown command in red... anyone knows what to do? it goes to boot screen, then blank screen... does not boot.
Click to expand...
Click to collapse
Try re-downloading sounds like a corrupted file.

Well some possible good news. The next build should be fixed. The problem was cleared on the regression tracker.

New build is up on the official site and is confirmed working

Developer options still freezes. but, if you do not wipe, your settings should remain

v521-Resurrection-Remix-N-v5-8-x-OMS-LG-G-Tab-X-8.0

Recently acquired this nifty little tablet. I've toyed around and upgraded to stock Nougat (v52120f).
I've followed the dirtycow method for rooting and installing TWRP. I am able to successfully sideload latest nightlies of LOS (lineage-14.1-20170505-nightly-v521-signed) and/or Resurrection (RR-N-v5.8.3-20170509-v521-Nightly). After the flash, both my wifi and bluetooth MAC addresses have changed from the original. Restoring back to stock restores the original MAC addresses.
Stock - 5c:af:06:xx:xx:xx
LOS - 00:0a:f5:23:47:54
RR - 00:0a:f5:23:47:54
Anyone else seen this issue?

Hi is there a way to have irda blaster (infrared) working with this ROM? Thanks

jotade said:
Hi is there a way to have irda blaster (infrared) working with this ROM? Thanks
Click to expand...
Click to collapse
if you want to try this kernel out. flash image in recovery. can't guarantee it will work as i don't have anything to test it on but i enabled everything, that I could find, IR-rc related
https://www.mediafire.com/file/07397adkju2on9g/boot.img

HighRidas said:
if you want to try this kernel out. flash image in recovery. can't guarantee it will work as i don't have anything to test it on but i enabled everything, that I could find, IR-rc related
https://www.mediafire.com/file/07397adkju2on9g/boot.img
Click to expand...
Click to collapse
Thanks i will try but flash via fastboot flash boot boot.img? O how. Please let me know

jotade said:
Thanks i will try but flash via fastboot flash boot boot.img? O how. Please let me know
Click to expand...
Click to collapse
in twrp recovery select install image then select the downloaded .img file and select boot.

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.