yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] tmartin_nihonsuki:
Nobody seems to have picked you up on this so may I? How does one use su to permanently achieve root on a device? And if it isn't present, how easy is it to install.

TIA
[Android Q&A, Help & Troubleshooting] :
[MENTION=11042391]tmartin_nihonsuki[/MENTION]

Look inside here.
[Android Q&A, Help & Troubleshooting] vindieu:
Good work, I haven't tried this SU "old Unix guru way" to root on the P20HD ("ARM64 processor", correct?).

Someone did? 1.03 ?

Anyhow, I believe the arguments in favor of Magisk are stronger :

- Magisk has modules, magisk hide, and that it's a manager.

- You can have root and custom mods while still using services like Google Play.

- You pass safetynet with magisk root. (Which you probably don't with a single binary in /bin)

- It works by leaving the system partition untouched and modifying the boot partition. This is why it’s referred to as a “systemless” root method.

- With magisk modules you can tweak your system really easily.

- If you want to install busybox its way more easy to the average Joe user by just clicking install in magisk rather than pushing the whole /xbin folder with adb.

- XPosed is now a Magisk module.

- Easy updates.

- And there are many more benefits to Magisk.
[Android Q&A, Help & Troubleshooting] :
[MENTION=9614954]vindieu[/MENTION]

My 2 cents:

Your promotion of Magisk is honorable. IMHO it's not of any interest here when it comes to simply root phone's Android, it's even out of topic. Be aware of fact that Magisk now gets detected by SafetyNet API, too. Also take note that an app ( e.g. banking app ) may have these functions included

isRootNative
isDetectedDevKeys
isDetectedTestKeys
isFoundBusyboxBinary
isFoundDangerousProps
isFoundHooks
isFoundResetprop
isFoundSuBinary
isFoundWrongPathPermission
isFoundXposed
isNotFoundReleaseKeys
isPermissiveSelinux
isSuExists
isFoundMagisk
isFoundRootCloakingApps

to detect whether phone's Android is rooted or not.
[Android Q&A, Help & Troubleshooting] vindieu:
I'm not promoting Magisk, I have no interest except my own.

Moreover, I may be wrong but I believe that there are Magisk modules or Xposed (included) that prevent this detection.

If not, then you can write your own module...
[Android Q&A, Help & Troubleshooting] few__:
There is a Xposed module to avoid safetynet.

However, on Android 10, you can't install xposed without adding magisk.

In order to use magisk, you need to create a vbmeta.

This is also true when using subinary.

You will also need it to install Google.

If you're done, please distribute vbmeta.

I'm rooting for you!

Good luck!
[Android Q&A, Help & Troubleshooting] vindieu:
Good try but it doesn't work.

I was able to patch boot.img on another device because Magisk Manager 7.5.1 advanced options + install are disabled on the P20HD.

YES, I can see Android Tablet/Android Bootloader&ADB Interface in my Windows 10 Device manager.

YES, my P20HD is unlocked and in fastboot mode

PS C:\tmp> .\fastboot getvar current-slot

current-slot:

finished. total time: 0.004s

PS C:\tmp> .\fastboot flash boot_a magisk_patched.img

target didn't report max-download-size

sending 'boot_a' (17392 KB)...

OKAY [ 0.765s]

writing 'boot_a'...

FAILED (remote: unknown reason)

finished. total time: 0.819s

PS C:\tmp> .\fastboot flash boot_b magisk_patched.img

target didn't report max-download-size

sending 'boot_b' (17392 KB)...

OKAY [ 0.762s]

writing 'boot_b'...

FAILED (remote: unknown reason)

finished. total time: 0.814s
[Android Q&A, Help & Troubleshooting] few__:
Unisoc-powered tablets require a signed custom VBmeta and a signed image.

Give me the patched magisk image and I'll sign it.
[Android Q&A, Help & Troubleshooting] vindieu:
We would appreciate that you share with everyone the procedure to sign it...

Please also understand that my boot.img is a security critical part of my device.

Moreover I should have get a different result than this one :

PS C:\tmp> .\fastboot getvar current-slot

current-slot: <============================== NONE !

finished. total time: 0.004s

Thanks!
[Android Q&A, Help & Troubleshooting] few__:
In the case of P80X, this is how it is patched.

python avbtool add_hash_footer --image magisk_patched_boot.img --partition_name boot --partition_size 36700160 --key rsa4096_vbmeta.pem --algorithm SHA256_RSA4096

or

python avbtool add_hash_footer --image magisk_patched_recovery.img --partition_name recovery --partition_size 41943040 --key rsa4096_vbmeta.pem --algorithm SHA256_RSA4096

Change the key and algorithm to your own.

Read more at https://forum.hovatek.com/thread-32674.html .
[Android Q&A, Help & Troubleshooting] vindieu:
ok, now I'm stuck because of a syntax error in the python script "avbtool.py".

(I'm currently running the latest Python version 3.8.5 64bits on my Windows 10 64bits PC)

I've just tried Python 32 bits but it didn't change anything.

Any Python's guru out there?

Thanks!

PS C:\tmp2> python avbtool.py info_image --image magisk_patched.img
File "avbtool.py", line 411
b = 2L**32
^
SyntaxError: invalid syntax

EDIT: Forget about that, I have installed the old Python 2.7....
[Android Q&A, Help & Troubleshooting] few__:
We created a custom signed Vbmeta Image. But I don't know if this will work...

Can someone test it for me?

Best regards!

edit:

If you can't flash the boot image

You must type fastboot --disable-verification flash vbmeta [yourvbmeta.img]
[Android Q&A, Help & Troubleshooting] few__:
The signed magisk patched boot image will be distributed via private message or email.

Send me a private message or send me an email message.

email : deleted

edit : It looks like you can distribute Magisk Image, so I'll distribute it here.

https://bit.ly/3gfG3Aw
[Android Q&A, Help & Troubleshooting] Hanpeng Yang:
Having typed the command and after "Sending 'vbmeta' (1024 KB) OKAY [ 0.044s]", It frozed at "Writing 'vbmeta'"
[Android Q&A, Help & Troubleshooting] few__:
I understand. let's take this VBmeta file and add it to

Type "fastboot --disable-verification flash vbmeta vbmeta-sign.img" and try Flashing it.
[Android Q&A, Help & Troubleshooting] Hanpeng Yang:
I tried this command with the given file, and the same problem occurred.
[Android Q&A, Help & Troubleshooting] few__:
It's a Stock VBmeta Image. I don't know why you can't flash it, but perhaps flashing the stock rom from the research tool will cure it...

(Never stop while in Flash)

Or you may have an older version of platform-tools.

---------- Post added at 04:36 PM ---------- Previous post was at 04:15 PM ----------

Maybe you need to open the properties of vbmeta and check the Unblock box.
[Android Q&A, Help & Troubleshooting] vindieu:
same problem here

By the way, for everyone's information, the 1.03 doesn't have Google Apps BUT there are more background apps & tasks than the 1.01 that can't be desactivated...

It's a Chinese rom first (the reason why it doesn't have Google Apps) but it also includes Western languages.

I guess Teclast has been told to make it difficult (or impossible ?) for Chinese people to install Google Apps on the 1.03.

For instance, the Google Framework will always crash - (maybe it's because the tablet needs to be rooted, I'm not sure...).
[Android Q&A, Help & Troubleshooting] vindieu:
For some reason, flashing doesn't write anything.

YES I am in fastboot mode.

YES I have selected USB Debugging mode in Developpers Menu

YES my tablet is unlocked. On my tablet it is displayed :

"fastboot mode

INFO: LOCK FLAG IS : UNLOCK!!"

YES I currently have no antivirus running on my Windows 10

YES my powershell is in Admin mode.

I am currently running 1.0.3 firmware

Any idea what wrong?? by the way, "current-slot:" is empty?? (see .\fastboot getvar current-slot )

Thanks!
[Android Q&A, Help & Troubleshooting] :
Slots only available if Android has a A/B-partition-system-layout. :)

You can check whether Android is A/B or not

adb shell "getprop ro.build.ab_update"

If TRUE is returned, Android is a A/B-partition-system one.
[Android Q&A, Help & Troubleshooting] vindieu:
adb shell "getprop ro.build.ab_update"
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found

What?? I'm in fastboot mode, and yes, Windows sees my tablet with the correct driver...
[Android Q&A, Help & Troubleshooting] :
[MENTION=9614954]vindieu[/MENTION]

You don't get it, for whatever reason.
[Android Q&A, Help & Troubleshooting] vindieu:
Yes, unfortunately, people born pedagogue are too rare
[Android Q&A, Help & Troubleshooting] vindieu:
Another unsuccessful try with 2 different fastboot, the one on the screenshot and the one (size 1334272) included in "Hovatek ADB fastboot v1.0.41"

Any other idea is welcome!
[Android Q&A, Help & Troubleshooting] :
[MENTION=9614954]vindieu[/MENTION]

Noticed you're running identical thread here:

https://forum.hovatek.com/thread-36170.html
[Android Q&A, Help & Troubleshooting] vindieu:
So what? Is it forbidden? Are you a moderator or something?
[Android Q&A, Help & Troubleshooting] ch3mn3y:
Why are You trying to use ADB command in Fastboot mode? It won't work. You have to be booted to OS and have Debugging on. In Fastboot it won't let You access ADB commands.
[Android Q&A, Help & Troubleshooting] vindieu:
thanks man! Here is the result :

PS C:\tmp2\platform-tools> .\adb devices <=== I got a message on the tablet for RSA key authorization...
List of devices attached
34432367532688 device

PS C:\tmp2\platform-tools> .\adb shell "getprop ro.build.ab_update"
<==== NOTHING ?
PS C:\tmp2\platform-tools>

Does it help??

Thanks again !
[Android Q&A, Help & Troubleshooting] :
[MENTION=9614954]vindieu[/MENTION]

It might help YOU to see that the fastboot subcommands are wrong as far as slots are concerned

fastboot flash boot_a magisk_patched

because there are no slots
[Android Q&A, Help & Troubleshooting] vindieu:
[MENTION=11013503]Hanpeng Yang[/MENTION] : Can you please confirm that you have the same result as I have? (see post #58) Thanks!

[MENTION=1890170]jwoegerbauer[/MENTION] : Why isn't there any slot, what does it mean? Why fastboot subcommands are wrong? Thanks!
[Android Q&A, Help & Troubleshooting] Hanpeng Yang:
Yes, mine's results are identical as yours.
[Android Q&A, Help & Troubleshooting] :
1. You have to ask this question device's OEM/Carrier: they put the Android OS on your tablet. FYI: Google introduced the A/B-partiton-system layout - there you basically have 2 differently mounted system partitions of which only one is active ( slot A ) - with Android 7 to make flashing OTAs more easy. However not all OEMs/Carrriers made it their standard.- for whatever reason.

2. Occupy yourself seriously with fastboot subcommands will say become familiar with fastboot subcommands :D
[Android Q&A, Help & Troubleshooting] vindieu:
Minimum libavb version: 1.0
Header Block: 256 bytes
Authentication Block: 576 bytes
Auxiliary Block: 13568 bytes
Algorithm: SHA256_RSA4096
Rollback Index: 0
Flags: 0
Release String: 'avbtool 1.1.0'
Descriptors:
Chain Partition descriptor:
Partition Name: boot
Rollback Index Location: 1
Public key (sha1): ea410c1b46cdb2e40e526880ff383f083bd615d5
Chain Partition descriptor:
Partition Name: dtbo
Rollback Index Location: 10
Public key (sha1): ea410c1b46cdb2e40e526880ff383f083bd615d5
Chain Partition descriptor:
Partition Name: recovery
Rollback Index Location: 2
Public key (sha1): d9093b9a181bdb5731b44d60a9f850dc724e2874
Chain Partition descriptor:
Partition Name: socko
Rollback Index Location: 11
Public key (sha1): bc688cacacd959cfaafbf0549d080d6fc2d50a08
Chain Partition descriptor:
Partition Name: odmko
Rollback Index Location: 12
Public key (sha1): 425215859f49f31809f16491c2a67e04df79baaf
Chain Partition descriptor:
Partition Name: vbmeta_system
Rollback Index Location: 3
Public key (sha1): e2c66ff8a1d787d7bf898711187bff150f691d27
Chain Partition descriptor:
Partition Name: vbmeta_vendor
Rollback Index Location: 4
Public key (sha1): 9885bf5bf909e5208dfd42abaf51ad9b104ee117
Chain Partition descriptor:
Partition Name: l_modem
Rollback Index Location: 6
Public key (sha1): e93e7d91ba1a46b81a5f15129b4dc5769bf41f26
Chain Partition descriptor:
Partition Name: l_ldsp
Rollback Index Location: 7
Public key (sha1): e93e7d91ba1a46b81a5f15129b4dc5769bf41f26
Chain Partition descriptor:
Partition Name: l_gdsp
Rollback Index Location: 8
Public key (sha1): e93e7d91ba1a46b81a5f15129b4dc5769bf41f26
Chain Partition descriptor:
Partition Name: pm_sys
Rollback Index Location: 9
Public key (sha1): e93e7d91ba1a46b81a5f15129b4dc5769bf41f26
[Android Q&A, Help & Troubleshooting] ch3mn3y:
What is actual difference between P20HD AND T30? They seems almost same...

I know about battery and different CPU, and, ofc, Android 10 at launch.

But what is really different between them that P20HD cost 2/3 of T30?
[Android Q&A, Help & Troubleshooting] vindieu:
I believe that the big difference is Sales.

For the first time, Amazon have decided to trust Teclast and have bought tens of thousands of this new Android 10 model for its sales network (according to one of my friends working for them).

I believe Amazon made the right choice (for once!), this cheap price-quality ratio (value for money) model is almost unbeatable...

http://www.teclast.com/en/zt/P20HD/
[Android Q&A, Help & Troubleshooting] ch3mn3y:
[MENTION=9614954]vindieu[/MENTION]

Thanks. Didn't think about sales and didn't hear about Amazon.

Just thinking about buying something tomorrow and got to P20HD Vs M30 Vs T30 Vs Alldocube i20 Pro.

P20 is the cheapest. T30 has bigger battery and M30 has even bigger one, higher resolution and 128 GB ROM. Alldocube is even better.

However I need a tablet for xCloud, so all I need is LTE and Bluetooth. Plus it have to work.

And have to say price says P20HD. However rooting loving heart says T30, which has a way to root.
[Android Q&A, Help & Troubleshooting] vindieu:
I'm a masochist, I like difficulty :D

I want my P20HD rooted with TWRP + Magisk, someone, someday, will be the first one to succeed.

Just hope that TWRP won't be compiled with some Trojan/Spyware/Malware in it...

I also believe that it'd be cool that Chinese have the choice to install Gapps or not.

Let us have some patience.

I also hope this model will become popular enough to get the famous Customs Roms, that would be cool.
[Android Q&A, Help & Troubleshooting] ch3mn3y:
One more question. Is there somewhere stock firmware for this tablet (P20HD)?

I know about official site, but there an ID number is needed - what is P20HD's one?
[Android Q&A, Help & Troubleshooting] vindieu:
Well, I don't know but here's the 1.03 image content from the google drive upload

( https://xdaforums.com/showpost.php?p=83301419&postcount=21 )
[Android Q&A, Help & Troubleshooting] vindieu:
Isn't ID "P30G_9863A_Android10_MARLIN3_TD_P20HD_OTA_20200731_V1.03" ?

or "s9863a1h10" ?
[Android Q&A, Help & Troubleshooting] :
[MENTION=9614954]vindieu[/MENTION]

My last 2 cents here: I no longer participate this thread. :)

Take note that all your attempts to flash a vbmeta.img - be it signed or unsigned - must miserably fail because your device's ROM doesn't contain such a vbmeta.img you can patch, but it contains the 2 files vbmeta_system.img and vbmeta_vendor. img what have to get patched.

To disable AVB all you have to do is running this command sequence

adb devices
adb pull /vbmeta_system.img "%TEMP%\vbmeta_system.img"
adb pull /vbmeta_vendor.img "%TEMP%\vbmeta_vendor.img"
adb reboot bootloader
fastboot devices
fastboot --disable-verification flash vbmeta_system "%TEMP%\vbmeta_system.img" 2>nul >nul
fastboot --disable-verification flash vbmeta_vendor "%TEMP%\vbmeta_vendor.img" 2>nul >nul
fastboot reboot
[Android Q&A, Help & Troubleshooting] vindieu:
[MENTION=1890170]jwoegerbauer[/MENTION] Thanks anyways, I guess we all have have appreciated your help.

Last question (but not least!) : What is the procedure to follow to patch these 2 "vbmeta_system.img" & "vbmeta_vendor. img" files ?

Thanks
[Android Q&A, Help & Troubleshooting] few__:
[MENTION=9614954]vindieu[/MENTION]

Can you try this?

"fastboot --disable-verification flash vbmeta_a vbmeta.img"

If you have any problems, try this one too :

"fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img"
[Android Q&A, Help & Troubleshooting] vindieu:
I don't want to flash anything, there's a brick risk... Please elaborate. Thanks.
[Android Q&A, Help & Troubleshooting] few__:
Stock VBmeta couldn't do Flash with that command, so I figured that VBmeta might have A/B support as well.

I'm sorry. I don't have this device, so this is just speculation.

https://android.googlesource.com/pl...584f19b2da7bb217d92f9d10416c5b4c1ca/README.md

"This image is designed to go into the vbmeta partition (or, if using A/B, the slot in question e.g. vbmeta_a or vbmeta_b) and be of minimal size (for out-of-band updates)."
[Android Q&A, Help & Troubleshooting] vindieu:
So basically, you disagree with [MENTION=1890170]jwoegerbauer[/MENTION] command sequence??
[Android Q&A, Help & Troubleshooting] few__:
Sorry, I don't know much about the sc9863a device with Android 10.

So I can't say anything from me about what [MENTION=1890170]jwoegerbauer[/MENTION] says about vbmeta_system etc.

I recommend you to trust him.
[Android Q&A, Help & Troubleshooting] vindieu:
I already trusted him from the beginning since he showed a lot of experience, Unix skills & patience, but that's not the problem.

What counts is the final result, how to successfully root this tablet with little risk.
[Android Q&A, Help & Troubleshooting] few__:
Devices with spreadtrum are as easy to recover as mediatek, so you may not have to worry too much about it.

However, you might want to ask this on Hovatek.

For more information, : https://forum.hovatek.com/thread-31800.html

Note that you should never stop while in Flash.
[Android Q&A, Help & Troubleshooting] lidormalich:
AnyOne have Pac file? my Tablet on brick :(

locked bootloder but oem off....
[Android Q&A, Help & Troubleshooting] few__:
Try using the firmware file I uploaded :

https://drive.google.com/file/d/1RAE7Lzrfj5R6B9CGaFLAlYrBhX7gTsaF/view?usp=sharing

This is the Chinese version of the firmware, so Google is not available.
[Android Q&A, Help & Troubleshooting] vindieu:
PS C:\tmp2\platform-tools> .\fastboot devices
34432365632688 fastboot

PS C:\tmp2\platform-tools> .\fastboot --disable-verification flash vbmeta_a vbmeta_custom_s7.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (1024 KB) OKAY [ 0.047s]
Writing 'vbmeta_a' FAILED (remote: 'unknown reason')
fastboot: error: Command failed

PS C:\tmp2\platform-tools> .\fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta_custom_s7.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (1024 KB) OKAY [ 0.054s]
Writing 'vbmeta_a' FAILED (remote: 'unknown reason')
fastboot: error: Command failed

I haven't been able to patch "vbmeta_system.img" & "vbmeta_vendor. img" as [MENTION=1890170]jwoegerbauer[/MENTION] suggested.

Why? When you install Magisk Manager.apk version 7.5.1 on the tablet, even if you grant it all the authorizations it needs

(storage, install unknown app...), you cannot have access to patch any file.

The other option I tried was to path these 2 files in MEMU with Magisk Manager.apk installed, but Magisk patch failed.

I guess this is because MEMU hardware platform is my PC (x86) instead of arm64 (P20HD).

Unfortunately, I don't have any other arm64 device with Magisk patch running ok...

Any suggestion is welcome.
[Android Q&A, Help & Troubleshooting] :
[MENTION=9614954]vindieu[/MENTION]

Please STOP mentioning me! TIA

I don't want to read your kindergarten-like posts anymore.
[Android Q&A, Help & Troubleshooting] few__:
I've created a new vbmeta.

Can you Flash with "fastboot flash vbmeta vbmeta vbmeta_testing.img"?

https://drive.google.com/file/d/1mvpsn3ocv6jfZwZ7K2ZUIQ7JsvnNc_ND/view?usp=sharing
[Android Q&A, Help & Troubleshooting] vindieu:
PS C:\tmp2\platform-tools> .\fastboot flash vbmeta_a vbmeta_testing.img
Sending 'vbmeta_a' (1024 KB) OKAY [ 0.053s]
Writing 'vbmeta_a' FAILED (remote: 'unknown reason')
fastboot: error: Command failed

PS C:\tmp2\platform-tools> .\fastboot flash vbmeta vbmeta_testing.img
Sending 'vbmeta' (1024 KB) OKAY [ 0.038s]
Writing 'vbmeta' ======> WAITING FOREVER...

same with --disable-verification

--disable-verity : unknown option
[Android Q&A, Help & Troubleshooting] vindieu:
?? Oops, I didn't know that it would bother you so much !!!!!!!!!!!!!!!!

Your sudden give up to help is really fishy.

I believe that "you've been told" to stop helping this thread because of my "NSA" quotes,

my warnings about Google spyware/trojans "services"

+ the Apple & Samsung Lobbying.

Like Edward Snowden, I only TOLD THE TRUTH.
[Android Q&A, Help & Troubleshooting] ch3mn3y:
I'm waiting for my P20HD, but I have question: Did You try using blank vbmeta image?
[Android Q&A, Help & Troubleshooting] vindieu:
What do you mean exactly? Please elaborate.
[Android Q&A, Help & Troubleshooting] ch3mn3y:
https://blog.hovatek.com/dm_verity-is-probably-why-that-twrp-flash-ends-in-a-bootloop/
[Android Q&A, Help & Troubleshooting] dannek:
a new version has appeared V1.04_20200822 who uploads it to a cloud ???
[Android Q&A, Help & Troubleshooting] vindieu:
Maybe [MENTION=10747371]few__[/MENTION] can upload it to Google drive like he did for the previous version? If yes, then thanks for everyone!
[Android Q&A, Help & Troubleshooting] vindieu:
No I didn't, I'm using it "as is" for now because I have many things on it that I don't want to delete/backup for now, just for a "try"...

Did you receive your P20HD ?
[Android Q&A, Help & Troubleshooting] ch3mn3y:
Nope. Still waiting. Looking at the shipping status it should be next week, but second half of it.
[Android Q&A, Help & Troubleshooting] newfundland:
Firmware for the P20HD has been uploaded.

The (4EA)

1. P20HD(N6H1)_Android 10.0_EEA_V1.01_SZ (Global firmware, Google Store installed O)

2. P20HD(N6H1)_Android 10.0_EEA_V1.02_SZ (Global firmware, Google Store installed O)

3. P20HD(N6H1)_Android 10.0_V1.03_3F54 (Chinese firmware, Google Store not installed )

4. P20HD(N6H1)_Android 10.0_V1.04_F3D3 (Chinese firmware, Google Store not installed )
[Android Q&A, Help & Troubleshooting] Hanpeng Yang:
Where did you find the global firmware? Because it is not available in the English version of the official website. With the help of Google Translate, I didn't find the place where you could download firmware in the Korean version of the official website.
[Android Q&A, Help & Troubleshooting] kostastnt:
Why everybody owns N6H1 version and I have N6H3? What are the differences? Bought mine from Amazon.es about 3 weeks ago and it is a European version. Reading all the previous post, I understand that there isn't available a safe "1-click" root. Am I wrong?
[Android Q&A, Help & Troubleshooting] newfundland:
I requested the firmware from the place of purchase.(Chinese Seller)
[Android Q&A, Help & Troubleshooting] andrymancy:
Hi, thank you for the firmware. I have a N6H1 with v1.01 EEA. The tablet is unusable (everything crashes) and there is no OTA. I need to reinstall the SO but I can't. Stock recovery says "Error: 21" "footer is wrong" when I use your firmware (of course "Debug USB" and "OEM unlocking" are on)... what can I do? How can I install the firmware you posted?
[Android Q&A, Help & Troubleshooting] vindieu:
It doesn't crash, it's just you. https://forum.hovatek.com/thread-15611.html
[Android Q&A, Help & Troubleshooting] ch3mn3y:
Where can I find Fastboot driver?

EDIT: OK, got it.

Now I think why I was looking for as for unlocking bl I'd need Linux...
[Android Q&A, Help & Troubleshooting] vindieu:
yep! Just install it on a USB key and boot it.
[Android Q&A, Help & Troubleshooting] ch3mn3y:
I know and I already have Ubuntu on my pendrive.

I just cannot find time. Today I had some and... I forgot my notebook's charger to work, so now I'm testing external drive for bad sectors not while I was at work... And it takes time as this **** is 4 TB...

Maybe tomorrow morning nothing will happen?