Database Info

[UTILITY] Android Flasher 2.1.0.5! (10/10/11)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
S-OFF is essential
Features:
Multiple flashes without closing the application.
Deletes all used files leaving you with nothing more than you had to start with.
Completely automatic, only user thing is to make a splash image, have a recovery img, a hboot img or a radio img.
Unified interface.
Completely in C#
Now supports BMP, PNG, and JPEG images. Not just BMP like NBIMG.
Usable on your Desire, Desire Z, Desire HD, EVO 4g, EVO 3D, Desire S, Incredible S, Thunderbolt and Sensation.
The application double checks the image dimensions to ensure no problems.
Also checks the created splash img file size to ensure no errors.
Click to expand...
Click to collapse
Prerequisites:
USB debugging enabled.
HTC and Fastboot/Hboot drivers must be installed.
Windows with .Net 4.0
Splash image, recovery img, a hboot img or a radio img. (not required for donate version)
Click to expand...
Click to collapse
What it actually does:
This app flashes the specific parts of the device (Bootloader, Recovery, Splash screen, and Radio). It's just a time saver.
The splash screen is the image before the boot animation, if you don't like the white HTC, then change it!
Click to expand...
Click to collapse
Credits to SA7039 for assistance and Google for fastboot, adb and dlls.
Post your SPLASH screens here:
http://forum.xda-developers.com/showthread.php?p=8367224
Got problems? Want to request features? Post a ticket
Click to expand...
Click to collapse
Changelog:
Code:
2.1.0.5
Added: EVO 3D, Incredible S, Desire S and Thunderbolt.
Added recent device display as the first button.
Updated pictures to be higher quality.
Fixed redo progress bug.
Added WiMax
2.1.0.1
Fixed a device bug that affected everything except for the Desire and Sensation.
2.1
Fixed checkboxes
Added 'Already in fastboot' button
Rewrote logging
Fixed donate button ;)
Added update notifications
Auto downloads data folder
Added path conversion to unicode, should help with localisation.
Added Desire HD and EVO 4g support.
Added Device list pages - moved DHD to second page with EVO 4G.
2.0.5
MsgBox for invalid splash image dimensions
Image displays in the center when selected
When you unselect a checkbox, it says 'No file selected.'
Menu button added in the file menu
Label changed Z/HD
Added 'Donate' button ;)
Now verifies that the splash img file is the correct size for flashing
2.0
Brand new, recoded entirely from the ground up.
Supports multiple devices, and image extensions.
Please consider donating .
Soon to come:
With Download Browser for all supported devices:
Click to expand...
Click to collapse

Solid project! I'll be sure to give this a go. Useful tool
Sent from my HTC Desire HD using xda premium

I have a problem. I select Desire HD. So but I can not select the splashscreen to flash it. When I browse a picture there is no file selected. With the older Android Flasher 1.6.1 I have no problem.

I have the same problem as inzaghi75, almost.
I start AndroidFlashe, then choose DesireHD, choose splashscreen/select browse and the select the picture i want for my splash, and hit flash. then the program "stops responding".

MariusOX said:
I have the same problem as inzaghi75, almost.
I start AndroidFlashe, then choose DesireHD, choose splashscreen/select browse and the select the picture i want for my splash, and hit flash. then the program "stops responding".
Click to expand...
Click to collapse
+1 with not responding

looks good great work

WOW!!!!! I've been waiting for something like this! Awesome!

One Word ... Amazing

impressive~

Great tool

Good morning guys.
inzaghi75 said:
I have a problem. I select Desire HD. So but I can not select the splashscreen to flash it. When I browse a picture there is no file selected. With the older Android Flasher 1.6.1 I have no problem.
Click to expand...
Click to collapse
MariusOX said:
I have the same problem as inzaghi75, almost.
I start AndroidFlashe, then choose DesireHD, choose splashscreen/select browse and the select the picture i want for my splash, and hit flash. then the program "stops responding".
Click to expand...
Click to collapse
730000229 said:
+1 with not responding
Click to expand...
Click to collapse
I'll find out what's causing it, because it seems to be for your device only.
Sorry about that.
Cheers,
Daniel
EDIT: Found it, look out for 2.1.0.1 . Sorry guys.

Yeeaah, sorry, still stops responding:S
Edit: Wow, wait. Now i didn't stop, it came up with this message: Error, device not found.
V2.1.0.0 found the device and rebooted it into fastboot.
Edit2: So it seems I didn't have ADB-Drivers :$ But now it stops responding again.
Here's the "flasher.log"
HTML:
ffmpeg version N-32962-gcbf914c, Copyright (c) 2000-2011 the FFmpeg developers
built on Sep 25 2011 21:35:29 with gcc 4.6.1
configuration: --enable-gpl --enable-version3 --enable-runtime-cpudetect --enable-avisynth --enable-bzlib --enable-frei0r --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libfreetype --enable-libgsm --enable-libmp3lame --enable-libopenjpeg --enable-librtmp --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib
libavutil 51. 17. 0 / 51. 17. 0
libavcodec 53. 17. 0 / 53. 17. 0
libavformat 53. 13. 0 / 53. 13. 0
libavdevice 53. 4. 0 / 53. 4. 0
libavfilter 2. 43. 5 / 2. 43. 5
libswscale 2. 1. 0 / 2. 1. 0
libpostproc 51. 2. 0 / 51. 2. 0
Input #0, image2, from 'splash1.jpg':
Duration: 00:00:00.04, start: 0.000000, bitrate: N/A
Stream #0:0: Video: mjpeg, yuvj420p, 480x800 [SAR 96:96 DAR 3:5], 25 tbr, 25 tbn, 25 tbc
File 'splash1.img' already exists. Overwrite ? [y/N] Not overwriting - exiting
< waiting for device >
sending 'splash1' (750 KB)...
OKAY [ 0.138s]
writing 'splash1'...
OKAY [ 0.327s]
finished. total time: 0.465s
But the phone is locked in Fastboot, with the green transferbar on the right side on the screen, nothing happening. Cant use vol-up or vol-down or Power-button.
Edit 3: Ok so i got it working now, after updating the driver.

2.1.0.5 Uploaded, changelog in the first post!

Use this thread: http://forum.xda-developers.com/showthread.php?t=794638

[ROM][M812/A][6.0.1] UNOFFICIAL CyanogenMod 13 for Infocus M812/A

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod 13 for Infocus M812/A, LUNA​
/* Info */
CyanogenMod 13 build for Infocus M812/A, LUNA
This Project is WIP Project.
If you can help me, please contact to me.
E-mail : [email protected]
/* Disclaimer */
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
/* Supported devices */
Infocus M812
Infocus M812A
LUNA [TG-L800S]
* KOR LG U Plus network is not supported.
/* Unsupported devices */
Everything else from supported devices
/* Downloads */
http://sayanogen.com/luna/
/* Donations */
Donate to me : http://forum.xda-developers.com/donatetome.php?u=4114162
/* Open Source */
https://github.com/sktjdgns1189

/* What’s working */
Everything else from not working
/* What’s not working */
.

/* Changelog */
20160621
Initial release

/* Screenshot */

Reserved 4

Reserved 5

Reserved 6

Cool. Gonna test it later after work. Thank you for release!
I see vna (m810) is supported in installer.
Means supported but not tested yet? What hsppens if update runs on mm bootloader? Bootloader unlock is anyway a byte in hidden part of aboot.

heineken78 said:
Cool. Gonna test it later after work. Thank you for release!
I see vna (m810) is supported in installer.
Means supported but not tested yet? What hsppens if update runs on mm bootloader? Bootloader unlock is anyway a byte in hidden part of aboot.
Click to expand...
Click to collapse
Nevermind, the website notice is wrong. now removed the notice.
and VNA is not tested.

sktjdgns1189 said:
Nevermind, the website notice is wrong. now removed the notice.
and VNA is not tested.
Click to expand...
Click to collapse
Nice! Starting.
You have to write some instructions like. First we need to flash recovery image from your site, than do full wipe, than flash the rom.
Testing!
thank you
BTW: CM13 looks like Android 5

so is it compatible with M810 ??

I just just tried. aboot installed and restarted. then flashed recovery, with boot coming errors (FAILED (remote:. dtb not found) unit starts but by hand it does not get too into Recovery (error:. DT fail. (94 / 0x00010001 / 1/0) Any ideas?
Device: M810T. Rom: The last 6.X of Heineken78.
(C:\CWM2>fastboot -i 0x0489 flash aboot aboot.img
target reported max download size of 1862270976 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.035s]
writing 'aboot'...
OKAY [ 0.049s]
finished. total time: 0.084s
C:\CWM2>fastboot -i 0x0489 reboot
rebooting...
finished. total time: 0.004s
C:\CWM2>fastboot -i 0x0489 flash recovery recovery.img
target reported max download size of 1862270976 bytes
sending 'recovery' (14820 KB)...
OKAY [ 0.470s]
writing 'recovery'...
OKAY [ 0.437s]
finished. total time: 0.908s
C:\CWM2>fastboot -i 0x0489 boot recovery.img
downloading 'boot.img'...
OKAY [ 0.469s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.551s
C:\CWM2>)

Fooox1 said:
I just just tried. aboot installed and restarted. then flashed recovery, with boot coming errors (FAILED (remote:. dtb not found) unit starts but by hand it does not get too into Recovery (error:. DT fail. (94 / )
Click to expand...
Click to collapse
dtb not found. Means source codes and compiled kernel has no m810 hardware in database.
I had try to run this CM13 with repacked boot.img based on stock mm kernel and it works. Only wifi and bt are missing.

Pity me was looking forward. Then wait and see if it is what is not.

Fooox1 said:
Pity me was looking forward. Then wait and see if it is what is not.
Click to expand...
Click to collapse
Il post repacked recovery and boot images for m810 when i arrive at home. This will work on m810 for sure,unless bugs with wifi and bt. I could fix them but m810 il get back in week or two.
To thread creator:
-While dialing the number and opposite is not taken yet,when screen goes off due prox sensor, touch still active with screen off.
-All led colors are on during charging or any noticiation. Green light remain also when battery is 100% and usb is not connected.
-Battery usage is average good, but much higher than in 6210 stock.(ondemand), higher much more (interactive-default)
-phone coverage is good, but on 3g Vodafone Ukraine sometimes i cant hear and opposite cant hear me (may be due kernel). In mm official everything ok.
-noticed screen quality less than on mm.
Device: Luna tgls.
What is advantage of this kernel 6.0 to stock one? How we can source codes of kernel for other devices, differ from phx vn2.

Test I like to do. Collect CM nice, you can adjust better. Themes etc.

me too, WiFi, Bluetooth and NFC are stop work for Infocus M810
Sent from my Infocus M810 using XDA-Developers mobile app

sktjdgns1189 said:
.
Click to expand...
Click to collapse
Hi!
Great CM13!!!
A bit modified and using it on m810 like others.Can you help me to get m810 kernel? Because LUNA kernel is missing some drivers like battery and charger in sources

M812 (tw) "dtb not found"
Device : M812 (tw)
firmware : 00WW-6210
Q:\CWM>fastboot -i 0x0489 flash recovery recovery.img
target reported max download size of 2936012800 bytes
sending 'recovery' (14820 KB)...
OKAY [ 0.480s]
writing 'recovery'...
OKAY [ 0.231s]
finished. total time: 0.711s
Q:\CWM>fastboot -i 0x0489 boot recovery.img
downloading 'boot.img'...
OKAY [ 0.480s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.562s
Can sktjdgns1189 and heineken78 help me??

lmamou said:
Device : M812 (tw)
firmware : 00WW-6210
)
Click to expand...
Click to collapse
Oh..this cm13 is made for luna-korean version hardware of m812 with "A".
I have remade it and fixed a lottt for m812.
Il post SUT image, of current version I'm using, so you will be able to flash it from PC in day or two
Also I have added support of qc2.0 not enabled by infocus before.

[RECOVERY][UNOFFICIAL]TWRP Recovery Project UMIDIGI A7 Pro 3.5.2

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 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.
*/Your warranty is now void.
We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or recoverys, kernels.
You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers./*
Click to expand...
Click to collapse
Flash Guide :
1. Unlock your bootloader
2. Download TWRP 3.5.2
3. Enable USB debugging
4. vbmeta from stock firmware
5. Run this Following Command
1. adb reboot bootloader
2. fastboot --disable-verification flash vbmeta vbmeta.img
3. fastboot flash recovery recovery.img
4. fastboot reboot recovery
Click to expand...
Click to collapse
Download
Device tree
Working
• MTP
• fastbootd
• adb
Bugs
• Decryption
• spam me in support group
Changelog
• Initial Build
• Updated to 3.5.2
• Fix some bugs in previous Builds
Credits
• TEAM WIN FOR TWRP
Support Group
Here

Hello mastersenpai05, how are you?
I finally managed to flash a GSI on the Umidigi A7 pro. Flashed PHH's GSI AOSP, version 411 - Android 12.
The problem is that when flashing your TWRP, I can't boot, it's in a loop.
I flashed like this:
[email protected]:~/Documentos/A7pro/twrp 352 Sempai$ sudo su
[sudo] senha para edupaz:
[email protected]:/home/edupaz/Documentos/A7pro/twrp 352 Sempai# adb devices
List of devices attached
A7PRO205020712 device
[email protected]:/home/edupaz/Documentos/A7pro/twrp 352 Sempai# adb reboot fastboot
[email protected]:/home/edupaz/Documentos/A7pro/twrp 352 Sempai# fastboot devices
A7PRO205020712 fastboot
[email protected]:/home/edupaz/Documentos/A7pro/twrp 352 Sempai# fastboot --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta' OKAY [ 0.014s]
Finished. Total time: 0.027s
[email protected]:/home/edupaz/Documentos/A7pro/twrp 352 Sempai# fastboot flash recovery recovery.img (I renamed the image)
Sending 'recovery' (23168 KB) OKAY [ 1.389s]
Writing 'recovery' OKAY [ 0.330s]
Finished. Total time: 1.732s
[email protected]:/home/edupaz/Documentos/A7pro/twrp 352 Sempai# fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.052s
Click to expand...
Click to collapse
Can you give me an idea how to fix the problem?
Now, after writing this message, which I called myself, that this version of TWRP is for Android 10. Do you have any predictions to launch for Android 12?

N
edufpaz said:
Hello mastersenpai05, how are you?
I finally managed to flash a GSI on the Umidigi A7 pro. Flashed PHH's GSI AOSP, version 411 - Android 12.
The problem is that when flashing your TWRP, I can't boot, it's in a loop.
I flashed like this:
Can you give me an idea how to fix the problem?
Now, after writing this message, which I called myself, that this version of TWRP is for Android 10. Do you have any predictions to launch for Android 12
Click to expand...
Click to collapse
Twrp A7 Pro will not work in android 12

mastersenpai05 said:
N
Twrp A7 Pro will not work in android 12
Click to expand...
Click to collapse
BIG mastersenpai05!
Thanks for the feedback. Is it possible to have development for Android 12?

Rooting on MIUI 13.0.3.0

Hi there! So I've been trying to root F2 Pro using official magisk guide, I've patched boot.img (V13.0.3.0.SJKMIXM version, which is the same one I'm running) using Magisk 25.2 and 25.1 using fastboot and fastbootd, flashing or only booting into it, but whatever I do, magisk always displays N/A. Is there any method to root this version? Thanks in advance!

ashirviskas said:
Hi there! So I've been trying to root F2 Pro using official magisk guide, I've patched boot.img (V13.0.3.0.SJKMIXM version, which is the same one I'm running) using Magisk 25.2 and 25.1 using fastboot and fastbootd, flashing or only booting into it, but whatever I do, magisk always displays N/A. Is there any method to root this version? Thanks in advance!
Click to expand...
Click to collapse
Did you try with Magisk manager?

That is exactly what I was doing,.I've just tried magisk canary builds, but the exact same result - Installed: N/A

ashirviskas said:
That is exactly what I was doing,.I've just tried magisk canary builds, but the exact same result - Installed: N/A
Click to expand...
Click to collapse
The bootloader is unlocked?
Did you extract the boot.img from this fastboot rom?
POCO F2 Pro GlobalStableFastbootV13.0.3.0.SJKMIXM12.05.4 GB2022-06-20

NOSS8 said:
The bootloader is unlocked?
Did you extract the boot.img from this fastboot rom?
POCO F2 Pro GlobalStableFastbootV13.0.3.0.SJKMIXM12.05.4 GB2022-06-20
Click to expand...
Click to collapse
The bootloader is unlocked, I can successfully flash patched `boot.img` images (even my banking app stops working and after flashing original `boot.img` it starts working again, so I know that flashing is working), it's just that the magisk app still shows that nothing is installed.
Yes, this is the exact same image I've used.

ashirviskas said:
The bootloader is unlocked, I can successfully flash patched `boot.img` images (even my banking app stops working and after flashing original `boot.img` it starts working again, so I know that flashing is working), it's just that the magisk app still shows that nothing is installed.
Yes, this is the exact same image I've used.
Click to expand...
Click to collapse
I had this phone but I don't remember if it has RAMDISK?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

NOSS8 said:
I had this phone but I don't remember if it has RAMDISK?
Click to expand...
Click to collapse
It does.

And no vbmeta

ashirviskas said:
It does.
Click to expand...
Click to collapse
Surely you did everything correctly but just in case, check.(Possibly post a screenshot of the CMD with the result)
Copy the boot/recovery image to your device
Press the Install button on the Magisk card
If you are patching a recovery image, make sure “Recovery Mode” is checked in options.
In most cases, it should already be automatically checked.
Choose “Select and Patch a File” in the method, and select the stock boot/recovery image
The Magisk app will patch the image to [Internal Storage]/Download/magisk_patched_[random_strings].img.
Copy the patched image to your PC with ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].img
Flash the patched boot/recovery image to your device.
For most devices, reboot into fastboot mode and flash with the command:
fastboot flash boot /path/to/magisk_patched.img or
fastboot flash recovery /path/to/magisk_patched.img if flashing a recovery image
Reboot and voila!
Or use the twrp to flash the modified boot.img

Though I do see it when I run `adb shell ls -l /dev/block/by-name` I will try repatching and reflashing, maybe this is what has been missing.

Here's my latest attempt with vbmeta.img included:
sudo fastboot flash boot magisk_patched-25200_VvhFg.img
[sudo] password for mati:
Sending 'boot' (131072 KB) OKAY [ 3.275s]
Writing 'boot' OKAY [ 2.315s]
Finished. Total time: 5.600s
sudo fastboot flash vbmeta --disable-verity --disable-verification lmi_global_images_V13.0.3.0.SJKMIXM_20220620.0000.00_12.0_global/images
/vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.024s
sudo fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.201s
Opening magisk app it still says `Installed: N/A`

Ok, I've just gotten it to work.. I had older, "hidden" magisk manager app on my phone. Removing it fixed everything, thank you for your time and effort.

ashirviskas said:
Ok, I've just gotten it to work.. I had older, "hidden" magisk manager app on my phone. Removing it fixed everything, thank you for your time and effort.
Click to expand...
Click to collapse
Better than stock(more options, call recorder)and play store certified without root.
https://xiaomi.eu/community/threads/miui-13-stable-release.64441/

Question Unable to install TWRP after rooting Redmi Note 11 Pro 5Gv(veux)

Hello all
I have used the information on here to successfully root my phone (Redmi Note 11 Pro 5G - veux) via magisk but I would like to put TWRP on it however whenever I try to boot the recovery image it does not work. Below I will include the mod el and info of my phone and also the output message of powershell, if anyone can tell me what I am doing wrong that will be great.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I did my flashing with the official mi flash tool to root with magisk but this screenshot from a different author seems to show the information you may need to help me nicely.
Here is the output from powershell when I try to boot the unofficial version I found named "360 pissarro RN 11 Pro+ pjgowtham" which says its for veux but I'm not getting much success.
I have flashed successfully and the drivers seem to be ok and list the device in "fastboot devices" and it is in USB developer mode but other than that I can't figure out why it wont't boot the recovery img so I can install TWRP
I will be eternally grateful if someone can tell me what I am doing wrong or what the actual correct file is
PowerShell Output:
PS C:\Users\Steve\Desktop\platform-tools> fastboot boot C:\Users\Steve\Desktop\recovery.img
downloading 'boot.img'...
OKAY [ 1.086s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.101s
PS C:\Users\Steve\Desktop\platform-tools>

Did you try with command prompt?
cd /d "Adb Destination"
fastboot flash boot recovery.img

No Sir, but I will try it right now

friend.evil said:
Did you try with command prompt?
cd /d "Adb Destination"
fastboot flash boot recovery.img
Click to expand...
Click to collapse
Still the same error:
C:\Users\Steve\Desktop\platform-tools>fastboot boot recovery.img
Sending 'boot.img' (38418 KB) OKAY [ 1.052s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
EDIT: It did actually work I was missing out the flash command, thank you!

tehnooks said:
Still the same error:
C:\Users\Steve\Desktop\platform-tools>fastboot boot recovery.img
Sending 'boot.img' (38418 KB) OKAY [ 1.052s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
EDIT: It did actually work I was missing out the flash command, thank you!
tehnooks said:
Still the same error:
C:\Users\Steve\Desktop\platform-tools>fastboot boot recovery.img
Sending 'boot.img' (38418 KB) OKAY [ 1.052s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
EDIT: It did actually work I was missing out the flash command, thank you!
Click to expand...
Click to collapse
EDIT: AGAIN
Click to expand...
Click to collapse
Didn't actually work now it's just stuck on the FASTBOOT screen
Heres what I got:
C:\Users\Steve\Desktop\platform-tools>fastboot flash boot recovery.img
Sending 'boot_a' (38418 KB) OKAY [ 1.031s]
Writing 'boot_a' OKAY [ 0.147s]
Finished. Total time: 1.454s
Am I using the wrong set of adb files to flash it with? Im using the platform tools from the android sdk

friend.evil said:
Did you try with command prompt?
cd /d "Adb Destination"
fastboot flash boot recovery.img
Click to expand...
Click to collapse
Tried flashing both boot_a and boot_b but still just ended up stuck on the fastboot screen

Had the same problems first, use command Prompt instead of powershell and make sure drivers are updated.
If you need twrp to install a new Rom follow these steps.
First type: fastboot getvar unlocked to check if it's unlocked.
Second Step is to download 2 Firmwares ( one updated and one slightly older ) from here
Flash up to date Firmware ( Slightly older is downloaded incase there are issues ) and boot to system, enable adb in developer options then use magisk to root phone, flash patched boot img with: fastboot flash boot patchboot.img
Edit: To flash a firmware follow this link and look at 2nd post if software isn't opening ( copy adb files to folder before using flash_all.bat )
After your phone is rooted and you made sure it was functional flash twrp: fastboot flash boot twrp12.img
Go to recovery mode, if the phone doesn't respond with touch display insert a usb c hub and add a mouse.
Download Encryption Disabler from Here and go to adb sideload and install it with adb sideload, next step is to install a Rom.
Mount Everything and wipe data then install Rom with ADB Sideload. ( ArrowOS is good ). Flash ROM then Gapps.

friend.evil said:
Had the same problems first, use command Prompt instead of powershell and make sure drivers are updated.
If you need twrp to install a new Rom follow these steps.
First type: fastboot getvar unlocked to check if it's unlocked.
Second Step is to download 2 Firmwares ( one updated and one slightly older ) from here
Flash up to date Firmware ( Slightly older is downloaded incase there are issues ) and boot to system, enable adb in developer options then use magisk to root phone, flash patched boot img with: fastboot flash boot patchboot.img
Edit: To flash a firmware follow this link and look at 2nd post if software isn't opening ( copy adb files to folder before using flash_all.bat )
After your phone is rooted and you made sure it was functional flash twrp: fastboot flash boot twrp12.img
Go to recovery mode, if the phone doesn't respond with touch display insert a usb c hub and add a mouse.
Download Encryption Disabler from Here and go to adb sideload and install it with adb sideload, next step is to install a Rom.
Mount Everything and wipe data then install Rom with ADB Sideload. ( ArrowOS is good ). Flash ROM then Gapps.
Click to expand...
Click to collapse
Which is the most suitable twrp image to use? I cant find one for veux or one named twrp12.img
Thanks!
EDIT: found it at https://drive.google.com/file/d/1-2_8YAfnWgvoRxIecDtN6JBRYWRKq8Ii/view
Thanks a lot it boots the twrp fine now