Windows ARM64 on fajita - OnePlus 6T ROMs, Kernels, Recoveries, & Other Dev

{
"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"
}
oneplus 6/6t 都可用
警告!不当操作可能会导致手机变砖!
-
20210822 updata
-
project address : https://github.com/edk2-porting
and
Tool download :https://drive.google.com/drive/folders/1GrX9JTVpKwo3WNshqIljPRc9Q6dPJDJJ?usp=sharing
boot download : https://github.com/edk2-porting/edk2-sdm845/releases/tag/v1.0.2
drives download : https://github.com/edk2-porting/WOA-Drivers/archive/refs/heads/main.zip
-
Installation tutorial
new tutorial!(English) https://forum.renegade-project.org/t/faq/95
-
article(Chinese) : https://forum.renegade-project.org/t/6-windows/194
-
Device support status
Renegade Project
Renegade Project
renegade-project.org
-
The drive is gradually improving
有问题我会不定期来看的,欢迎提问。
Questions are welcome

How are you doing with the driver ports. Nice work tho!

Keno_I said:
How are you doing with the driver ports. Nice work tho!
Click to expand...
Click to collapse
The driver is currently only basic
Such as wifi, GPU, battery, etc. are all unavailable
But this will gradually improve in the future!
-
驱动目前只有基础的
比如wifi,GPU,电池等都是不可用的
但这会在之后慢慢完善!

Nice. Good work on that, I'm assuming this port will be easier when windows arm devices get more widespread and supported

Good work. This is really great.
Will try that out the next days.
One thing I am just wondering.
How is it handled to boot Windows and Android?
So when you boot up the phone will it boot to Windows or to Android?
Or will it boot to Android and to boot to Windows you will need to fastboot the boot-fajita.img again?
Thanks!

Given it a go, it's not going bad is it? Very nice.
It took a while to set up so I wrote some scripts to partition and boot to recovery, along with scripts within recovery to deal with bootloader config. The only thing that wasn't automatic at this point was running DISM++
Good work. This is really great.
Wishmasterflo said:
Will try that out the next days.
One thing I am just wondering.
How is it handled to boot Windows and Android?
So when you boot up the phone will it boot to Windows or to Android?
Or will it boot to Android and to boot to Windows you will need to fastboot the boot-fajita.img again?
Thanks!
Click to expand...
Click to collapse
By default it will boot Android, unless you flash the windows bootloader img to boot.
I cannot recommend flashing the windows bootloader img at the moment- it worked and windows boots by default but from this point on I was unable to start TWRP, even via fastboot boot, so I'll have to MSM tool it to restore, which *does* wipe windows.
Other thoughts: This is almost usable, however, battery drain is through the roof and the touch screen driver is misconfigured for the display, so touch events are in the wrong place.
Keep going guys!

damiensturdy said:
Given it a go, it's not going bad is it? Very nice.
It took a while to set up so I wrote some scripts to partition and boot to recovery, along with scripts within recovery to deal with bootloader config. The only thing that wasn't automatic at this point was running DISM++
Good work. This is really great.
By default it will boot Android, unless you flash the windows bootloader img to boot.
I cannot recommend flashing the windows bootloader img at the moment- it worked and windows boots by default but from this point on I was unable to start TWRP, even via fastboot boot, so I'll have to MSM tool it to restore, which *does* wipe windows.
Other thoughts: This is almost usable, however, battery drain is through the roof and the touch screen driver is misconfigured for the display, so touch events are in the wrong place.
Keep going guys!
Click to expand...
Click to collapse
Great. Thanks for the answers. I will try that out as well.
I saw in the Tools folder there is a file "TouchScreen.reg" . Does that not fix the touchscreen issues or what does that do?

Wishmasterflo said:
Great. Thanks for the answers. I will try that out as well.
I saw in the Tools folder there is a file "TouchScreen.reg" . Does that not fix the touchscreen issues or what does that do?
Click to expand...
Click to collapse
Actually, the last time I did it I didn't have any touchscreen issues- I must have skipped the reg file!

I just bought a USB-c HUB to connect Mouse, keyboard, USB stick to my phone when setting this up.
So if I see this correct now and the boot file can only be booted via Fastboot and flashing it to boot is not recommended due to issues to boot TWRP afterwards there is no way now to boot that without having the phone connected to a Computer or?
OK I gave that a try now. I could boot to the EFI environment and tried to apply the Windows 11 arm64 image in Dism++.
After done the steps to select the ISO file and target C: it starts to copy files and after like 1 minute I get an error Message but all the text in the message is in Chinese letters so I dont know what the error means.
How can I set the language in Dism++ to english?
Thanks!

Wishmasterflo said:
我刚买了一个 Usb - c Hub 来连接鼠标, 键盘, Usb 粘在我的手机上, 当设置这个。
因此,如果我现在看到这个正确的启动文件,并且引导文件只能通过 Fastboot 启动,并且由于启动 TWRP 的问题而不建议将其闪烁到启动,那么现在没有办法启动该启动,而没有将手机连接到计算机或?
好吧, 我现在试了一下。我可以启动到 EFI 环境,并试图应用 Windows 11 手臂 64 图像在 Dism+.
完成选择 ISO 文件和目标 C 的步骤后:它开始复制文件,1 分钟后我收到一条错误消息,但邮件中的所有文本都以中文字母表示,因此我不知道错误是什么意思。
如何将 Dism+中的语言设置为英语?
谢谢!
Click to expand...
Click to collapse
Sorry for taking so long to reply you But this software seems to be only in Chinese

hehedi233 said:
View attachment 5390973Sorry for taking so long to reply you But this software seems to be only in Chinese
Click to expand...
Click to collapse
Thanks for the reply.
I guess Dism++ is taking the language settings from the Windows PE or boot.img and therefor it is set to Chinese.
I see when booting up the img file that that is set to Chinese. So if that can be changed to English I guess the Dism tool will be english aa well.

Wishmasterflo said:
Thanks for the reply.
I guess Dism++ is taking the language settings from the Windows PE or boot.img and therefor it is set to Chinese.
I see when booting up the img file that that is set to Chinese. So if that can be changed to English I guess the Dism tool will be english aa well.
Click to expand...
Click to collapse
you can go online to find the English version of Dism++, and then pass it in via USB disk

hehedi233 said:
you can go online to find the English version of Dism++, and then pass it in via USB disk
Click to expand...
Click to collapse
I already did that but it is in Chinese as well after launching it when booted the boot.img file therefor I guess it it fetching the language setting from the booted IMG or WinPE already.

Wishmasterflo said:
I already did that but it is in Chinese as well after launching it when booted the boot.img file therefor I guess it it fetching the language setting from the booted IMG or WinPE already.
Click to expand...
Click to collapse
If you downloaded the windows that I uploaded, it is the Chinese version, you can go to uupdump to download the corresponding version of windows. Note that it is arm64

hehedi233 said:
If you downloaded the windows that I uploaded, it is the Chinese version, you can go to uupdump to download the corresponding version of windows. Note that it is arm64
Click to expand...
Click to collapse
Yes that I already did. Its more the WinPE which is in Chinese causing that Dism++ is launching in Chinese as well.
So I assume when I push the English WinPE files/Version to my phone I will have everything in english then and Dism++ will launch in English as well.
Can you provide WinPE in english?

Wishmasterflo said:
Yes that I already did. Its more the WinPE which is in Chinese causing that Dism++ is launching in Chinese as well.
So I assume when I push the English WinPE files/Version to my phone I will have everything in english then and Dism++ will launch in English as well.
Can you provide WinPE in english?
Click to expand...
Click to collapse
winpe-EN.7z
drive.google.com

I laughed when I saw the BSOD
---
当我看到死亡的蓝屏时,我笑了。

Related

Step-by-step guide for installing Windows 7

I already posted this guide in another thread, but to make sure others read it before asking questions that has been asked 10 times before I descided to repost it in a new thread. Enjoy!
As requested - here is a guide on how to install Windows 7 to the HTC Shift.
First of all you need an external DVD drive or a memory stick with 4GB minimum.
READ THIS GUIDE CAREFULLY BEFORE INSTALLING WINDOWS 7.
The information contained in this guide was collected from posts in this thread and I cannot guarantee that everything will work perfect for you!
• Download the beta image
USB-install:
1 - Open Iso file with winrar, and extract all file into folder C:\WINDOWS7\
2 - Open command prompt in administrator mode (start - all programs - accessories - command prompt - right click - run as administrator)
3 - Then type this commands :
- type CD\
- type DISKPART
- type LIST DISK
- type SELECT DISK X (where X is the memory stick disk number you got from LIST DISK)
- type CLEAN (CAUTION; THIS WILL ERASE ALL THE CONTENTS OF THE SELECTED DISK)
- type CREATE PARTITION PRIMARY
- type SELECT PARTITION 1
- type ACTIVE
- type FORMAT FS=FAT32 QUICK
- type ASSIGN
- type EXIT
- type XCOPY C:\WINDOWS7\*.* /S /E /F E:\ (E: \ is the name of usb stick, if your key has an other letter, of course put your) (after *.* and after each letter preceded by / there's a space!)
Reboot, at startup push FN+F10, and choose your usb key.
This will not affect your HTC SHIFT Vista recovery partition.
Thanks killer_t
DVD-install
• Burn the image to a DVD
• If you want to dualboot Windows 7 and Vista you need to partition your harddrive before starting the installation. Use a suitable partition manager such as Paragon Partition Manager and shrink c:/ to approximately 15-17 GB. Create a new partition in the free space.
• Connect the USB DVD drive to your shift
• Press fn+0 (F10) after turning on your shift – select the DVD drive
• Follow the steps for installing Windows. Remember to select partition 2 as target partition if you want to dualboot with Vista. If not you can safely format the existing partition. This will not affect the recovery partition.
____________________________________________________________________________
• Download the shift drivers from HTC
• When you install the drivers – beware that you have to install them with Vista Compatibility mode enabled and run as Administrator. Right-click the driver setup file – click the Compatibility tab – select Windows Vista and mark “run this file as Administrator”
{
"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"
}
• Install all the drivers in the order below and restart your computer when asked to:
a. VistaECDrvV1[1].0.1.10
b. TouchScreen(1[1].1.0.2)
c. Realtek Audio Driver R197(6[1].0.1.5653)
d. Marvell WiFi driver(8[1].114.123.139)
e. Vitakey _AC5023_Fingerprint AP v5[1].0.2.0 and Driver v7.10.1.0 *
f. Extension Kit USBLanDriver(3[1].8.3.7) (Note: you have to install this through driver update in device manager)
g. Shagctrl_1[1].2.6.122-control center - Note that you have to disable aero to get the 1024x600 interpolated resolution working. Right click on dektop -> personalize -> and choose the first "easy of access" Theme.
h. Synaptics MicroPad(10[1].0.11.1)
• - VISTA_INTEL Chipset Driver v8[1].3.0.1014 You can use Windows Update for this one.
• Now that control center is working in Win7 there is no need to liberate your snapvue (if you haven't already done it). 3G,WLAN and BT works out of the box.
Guide for removing the "Evaluation copy. Build 7057.winamin.090305-2000" watermark in Win7 build 7057:
1. Download this patch.
2. Run the patch, command window will open.
3. Y for yes. Press Enter, then Enter again to exit.
4. Reboot. Watermark is gone.
• Finally, if you encounter any problems – READ this thread before asking questions. Remember that “search” is your friend
Thanks for this nice manual!!
I received my Shift 3 days ago and I'm currently installing Windows 7.
I'll let you know if I managed to install it succesfully.
johanromijn said:
Thanks for this nice manual!!
I received my Shift 3 days ago and I'm currently installing Windows 7.
I'll let you know if I managed to install it succesfully.
Click to expand...
Click to collapse
You're welcome
Hope it works out for you...
deadnex said:
You're welcome
Hope it works out for you...
Click to expand...
Click to collapse
Can you please tell me where I can find HSECT2 and CYGWIN?
johanromijn said:
Can you please tell me where I can find HSECT2 and CYGWIN?
Click to expand...
Click to collapse
I've updated the guide with download info
deadnex said:
Both HSECT2 and CYGWIN can be found in this archive
[Mirror]
Click to expand...
Click to collapse
Thanks for the help, mate!
I feel like a bit of a noob now.
I really have no experience with my Shift yet, sorry for that.
Windows 7 runs great btw!
------------
EDIT: Sorry, but I cannot find the needed files in this archive.
EDIT: Found HSECT2 HERE
please, someone can tell me if touch screen works in win7??
Ciauz
nion said:
please, someone can tell me if touch screen works in win7??
Ciauz
Click to expand...
Click to collapse
yes it works, but you should follow the instruction correctly...follow the steps in the step-by-step guide and it will works like a charm
nion said:
please, someone can tell me if touch screen works in win7??
Ciauz
Click to expand...
Click to collapse
Everything works fine in Win7 except Control Center. However, 3G connection and enable/disable BT/WIFI can be done through HSECT2 and CYGWIN. Read my guide for details.
deadnex said:
b. Intel VGA driver(7[1].14.10.1461)
Click to expand...
Click to collapse
this one is not working for me... BSOD again and again... I think that it is better to keep the default one.
what do you think?
out of curiosity - does the recovery partition still boot after this by pressing Fn+F3?
Cause the last laptop (HP) that i installed windows 7 beta to could no longer boot from the recovery partition thereafter. - I suspect that with the HP's it has to have a specific boot sector of HDD for the F12 recovery to work; same as my acer?
Thanks
Kris
i00 said:
out of curiosity - does the recovery partition still boot after this by pressing Fn+F3?
Cause the last laptop (HP) that i installed windows 7 beta to could no longer boot from the recovery partition thereafter. - I suspect that with the HP's it has to have a specific boot sector of HDD for the F12 recovery to work; same as my acer?
Thanks
Kris
Click to expand...
Click to collapse
haven't tried but it should yes.. because it's not part of the partition of Vista... I guess that in vista you CAN'T remove the thing to restore partition.. but in your HP laptop you could and you may have removed it.
koala996 said:
haven't tried but it should yes.. because it's not part of the partition of Vista... I guess that in vista you CAN'T remove the thing to restore partition.. but in your HP laptop you could and you may have removed it.
Click to expand...
Click to collapse
on my hp the recovery partition is defiantly still intact and I can still recover by marking the recovery partition active from vista but when it says press F12 to recover it now does nothing - so I think it must also need its "special" boot sector
kris
i00 said:
on my hp the recovery partition is defiantly still intact and I can still recover by marking the recovery partition active from vista but when it says press F12 to recover it now does nothing - so I think it must also need its "special" boot sector
kris
Click to expand...
Click to collapse
yeah maybe... I think in the shift it is not part of the HDD (not sure about it).
I will try to restore vista soon, because I want to try things today (to have Win7 and WinVista on 2HDDs working on the shift.. Win7 on main HDD and Vista in external one).
edit1 : well ... recovery done no problem for recovery after installing windows 7 !! I save everything on vista side... activate bluetooth and wifi ... and then installing back Vista on another drive and then Windows 7 on main DD
edit2 : arf.. impossible to install windows on a usb drive ... sad ^^ .. well I will feedback Microsoft about it , it would be a GREAT addition to Win7. well.. reinstalling win 7 now !
koala996 said:
Originally Posted by deadnex
b. Intel VGA driver(7[1].14.10.1461) one is not working for me... BSOD again and again... I think that it is better to keep the default one.
what do you think?
Click to expand...
Click to collapse
I have the same problem and the step by step of cygwin installation is not correct how can I turn off/on bt and wi fi?
siriokeliang said:
I have the same problem and the step by step of cygwin installation is not correct how can I turn off/on bt and wi fi?
Click to expand...
Click to collapse
mmh.. I have recovered vista and reinstalled w7 to get wifi and bt working... shame on me ^^
koala996 said:
mmh.. I have recovered vista and reinstalled w7 to get wifi and bt working... shame on me ^^
Click to expand...
Click to collapse
.....me too and now how can I turn off the bt or wi fi? it's too difficult for me......ok fn F3 back to business it's the only solution
siriokeliang said:
.....me too and now how can I turn off the bt or wi fi? it's too difficult for me......ok fn F3 back to business it's the only solution
Click to expand...
Click to collapse
you can disable them ... but I'm not sure if it is "totally" disabled.
for bluetooth .. I have disable in the "device manager".
for wifi.. I have not disabled it again..but you can through "windows mobility center" (not windows mobile device center).
I'm working on Win7 to make everything usable.. if you need somedays... I think I will have some goods news ! the 2 buttons (shag control and resolution switcher) are responding... but I need to make them work
koala996 said:
this one is not working for me... BSOD again and again... I think that it is better to keep the default one.
what do you think?
Click to expand...
Click to collapse
When windows is booting, press F8, select low resolution mode. Then disable Aero in Win7. After that 1024x600 resolution should work
siriokeliang said:
I have the same problem and the step by step of cygwin installation is not correct how can I turn off/on bt and wi fi?
Click to expand...
Click to collapse
Search the forum or check out Pof's blog for more info on HSECT2 and CYGWIN.
It should work, but I haven't tested it myself yet

Windows 10 PRO International custom installation (c5j6 tested)

Hi guys
starting from the windows international iso, I have decided to create a custom installation with already integrated the drivers that comes with the last windows 10 release from Teclast (you can find it here).
WHAT YOU GET:
Windows 10 Pro international
Latest drivers from Teclast
latest updates from Microsoft
.net framework
This iso has been tested on my device (C5J6 with 2.02 bios). Everything is working with out a problem.
INTEGRATED DRIVERS
{
"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"
}
You can download a detailed version here
WHAT YOU NEED
Windows iso (download link on 2nd post)
8GB USB key
USB Hub
USB Keyboard
USB mouse (optional)
A computer running windows
RUFUS (https://rufus.akeo.ie/)
Before you start, ensure you have everything ready. You will need an empty usb key, that will be erased during the process.
INSTRUCTIONS
The process will be divided in two stages. The first will create the usb key with the windows installer. The second will boot the tablet from the usb key and let you install windows 10.
Stage 1
Download the windows iso (link below) and Rufus
Insert your usb key
Start RUFUS
Select your USB key (BE CAREFUL!!! IT WILL BE ERASE)
Select MBR for UEFI (Fig. 1)
Select the downloaded iso and click "start"
Once the process is done, you have a bootable usb key with the Windows installation.
Before starting stage 2, you have to boot your tablet to windows. This is MANDATORY, otherwise you will not be able to boot the usb key. This is due to the nature of the dual boot bios.
Stage 2
Switch off the tablet (FROM WINDOWS! MANDATORY)
Connect everything (mouse,keyboard and usb key) to the usb hub
Connect the usb hub to the tablet
Switch on the tablet
As soon as the screen switch on, start press "ESC" for entering the bios
From the bios select "Save & Exit" (Fig. 2.1)
Select your USB key form "Boot Override" (Fig. 2.2)
Now the tablet will boot from the usb key. The process now is straightforward, just follow the instruction prompt from windows installer.
The installation process will be the usual, for installing windows.
PS: If you have rotation problem, download the Gsensor fix from there: GSensor
First install the .exe than the reg key
Hope you will enjoy :good:
DOWNLOAD LINK
[v. 1] https://mega.nz/#F!xYQywaDD!qIctd7WuhgEv2n_1_3e1SA
[v.2] Home ed.
[v.3] Windows 10 April update --- Changelog
*** IMPORTANT ***
Keep the usb key connected till the first boot. The g sensor drivers are installed during the first boot. Once the installation process has finished, and you reach for the first time the desktop, switch to desktop mode, and the installation process will start. Once the process is complete, reboot.
*** IMPORTANT ***
Hi, I have something to ask:
1) Is it a pre-activated ISO?
2) Does this procedure touch Android partitions? (and Android system of course)
3) During installation process (windows wizard), what partition do you select to install windows?
Thanks..
Maxximo88 said:
Hi, I have something to ask:
1) Is it a pre-activated ISO?
2) Does this procedure touch Android partitions? (and Android system of course)
3) During installation process (windows wizard), what partition do you select to install windows?
Thanks..
Click to expand...
Click to collapse
Hi,
1)No. You will need a serial for activate it
2/3)No. If you start from a tablet that already has a dual boot config (== windows + android already installed), the internal disk will be already partitioned. So you will just need to select and format the partition with the old windows.
OFC, If you want, during the installation wizard you can repartition the whole internal drive.
nrdmtt said:
Hi,
1)No. You will need a serial for activate it
2/3)No. If you start from a tablet that already have a dual boot config (== windows + android already installed), the internal disk will be already partitioned. So you will just need to select and format the partition with the old windows.
OFC, If you want, during the installation wizard you can repartition the whole internal drive.
Click to expand...
Click to collapse
Ok, so I just need to select Windows partition, without touch other partitions (like recovery)...Great!
Maxximo88 said:
Ok, so I just need to select Windows partition, without touch other partitions (like recovery)...Great!
Click to expand...
Click to collapse
Yep.
I have partitioned my tablet with MFT tool only once. Now if I what to change the os, I only need to format the right partition
nrdmtt said:
Yep.
I have partitioned my tablet with MFT tool only once. Now if I what to change the os, I only need to format the right partition
Click to expand...
Click to collapse
Nono wait what do you need?
I am saying that once partitioned with the Intel manufacturing tools, I do not need to chance the partition scheme any more.
If i want to switch from win 8.1 to win 10, i just format the windows partition.
If i want to switch from lollipo to KitKat just flash with adb /data /system partitions.
Can I use this iso for upgrading from within current windows 8.1?
Sent from my Teclast X98 Air 3G (C8J6)
sandroj said:
Can I use this iso for upgrading from within current windows 8.1?
Sent from my Teclast X98 Air 3G (C8J6)
Click to expand...
Click to collapse
I think yes, but I haven't tried personally.
i installed this, its just a clean install without any drivers. am on c5j6 bios v2.05
What language is it?
Is there a chance to get only the driverpack without windows?
Greetings
jagr said:
i installed this, its just a clean install without any drivers. am on c5j6 bios v2.05
Click to expand...
Click to collapse
Are you sure? This sound very strange to me.
During the install process you have to chose the "PRO" version.
neskiuck said:
What language is it?
Click to expand...
Click to collapse
Eng
Lordof9 said:
Is there a chance to get only the driverpack without windows?
Greetings
Click to expand...
Click to collapse
https://mega.nz/#!VQYFgZpK!1EUMfs4ip8UD7SyzRqCJNt4Xb0uH_PCEmZ94PJL4uNI
Those are the drivers that I have integrated.
Regards.
nrdmtt said:
Are you sure? This sound very strange to me.
During the install process you have to chose the "PRO" version.
Click to expand...
Click to collapse
i see. i chose the home version. so we have to purchase a pro serial on our own?
///
jagr said:
i see. i chose the home version. so we have to purchase a pro serial on our own?
Click to expand...
Click to collapse
No one told you to buy a PRO license. If you want use your Home key, just install the home version and then use the drivers pack that I have provided.
I have an original PRO key, so I have modded the pro version.
BTW I will integrate the drivers also in the home version, but you will have to w8, since I currently can not upload it.
Hope you can release International Windows 10 Home version with drivers too since most teclast tablet are shipped with Home licence key. Thanks =)
do integrated driver on the home version please. hurry up. 99%has the home version.
Here we are
Home edition : https://mega.nz/#F!IUIVzKAL!bU60GlkGpKceN7M4ohsbGQ

Easy steps/screenshots to install Windows drivers for FastBoot to work with XA2 Ultra

10/26/2019 update (also posted at the end of this thread):
I was having trouble Using NewFlasher v19 with the "H3223_Customized US_1312-1380_50.2.A.0.400_R2B" firmware I downloaded and extracted with XperiFirm. I kept getting the following:
(short version: occasionally the Sony driver doesn't work for me to flash the latest official update. On those occasions I update the driver in Device Manager to the GordonGate driver that Newflasher provides, and then it works fine, but other times if I just go straight to GordonGate, then it doesn't work either, so go figure. At least it works one way or the other, just depending on I don't know what. )
Code:
ERROR: GetOverLapped_out_Result: failed with error code 1 as follows:
Incorrect function.
- Error write! Need nBytes: 0x18 but done: 0x0
nBytes[0x0]:
- Error writing command getvar:max-download-size!
This was on a relatively new (almost three months old) Windows 10 build 1903 installation, so I hadn't flashed my H3223 on this Windows build yet. I had installed without trouble the same XZ2 driver (they haven't updated it) but no luck. Finally I tried NewFlasher's GordonGate option, I extracted the archive, pointed Device Manager at this folder for the Sony ADB driver and it installed just fine. After that, NewFlasher flashed this just fine. I don't recall ever needing the GordonGate driver, nor it even working when I had attempted it previously.
I was still able to use the XZ2 driver to fastboot boot TWRP.img.
Just FYI if this helps anyone.
Click to expand...
Click to collapse
The following is my original post (if the above new instructions don't get you what you need, or if you need help installing the XZ2 driver in order to boot TWRP - I have no idea if NewFlasher's GordonGate driver would make it so that you could boot TWRP.
I hope this guide with both text descriptions and screenshots for every step can help anyone who had trouble with the driver installation steps. They're not difficult steps, but on three PCs that I installed the drivers on, I found the description of the method to be just a little different than what some users experienced, so please note that you may have a slightly different experience, and this post is not meant to mean that this is the only way to get the Xperia XA2 Ultra drivers installed.
Also note that I have the H3223 model (one of the two "Discovery" types, just in case there are any differences in experiences for those with different variants, as well.
Click to expand...
Click to collapse
Please use this thread for all variants, however, as long as it is regarding the installation of drivers.
First the thanks:
Sony for making their devices bootloader unlockable and being developer-friendly.
@LuK1337 for building official TWRP for the "Pioneer" types of The XA2 Ultra, which at least for 'fastboot boot TWRP.img', works great on the "Discovery" variants as well.
@Chainfire for [BETA][2017.10.01] SuperSU v2.82 SR5, which works great on the ROM v50.1.A.5.59_R6A.
@topjohnwu for Magisk, which I know others are using and I may have to switch to when this device is updated to Android 8.1+, as I know from personal experience SuperSU doesn't work on the 2016 Pixel on Android 8.1, at least not by straight flashing the zip.
@li0nh3art3d and @AngryManMLS for leading me down the path of being able to successfully install the correct drivers, in this thread Unlocking Bootloader/Rooting
If I missed anyone, please let me know and I'll correct ASAP.
Click to expand...
Click to collapse
The steps are (also all instructions and screenshots are available here and below (click on the thumbnails to open larger copies):
1a. Go to the Sony Driver webpage and download Xperia XZ2 driver and unzip it
OR
1b. Go to Xperia XZ2 driver webpage and download the driver and unzip it
2. Put the Xperia XA2 Ultra in Fastboot mode (turn the phone off and disconnect it from any cables, press and hold the Up Volume button, and while doing so, connect the cable from the computer to the phone
3. Right-click on Start Button
4. Click 'Device Manager'
5. 'Device Manager' - 'Other devices'
6. Right-click on 'Android', choose 'Update driver'
7. Choose 'Browse my computer for driver software'
8. Browse or copy-paste path of extracted Xperia XZ2 driver, and choose 'Let me pick from a list of available drivers on my computer'
9. Choose 'Show All Devices', click 'Next'
10. Choose 'Have Disk'
11. Browse to or select in the drop-down menu the path to the extracted Xperia XZ2 driver
12. Click 'OK'
13. Select the only driver that is listed and click 'Next' (on just one of the three PCs I installed the driver to, there were more than one Sony drivers listed, and I'm pretty sure I picked the one that said 'Fastboot' in it in that case)
14. Select 'Yes' at the warning dialog
15. Click 'Close'
16. Observe that Device Manager now lists 'Sony sa0118 ADB Interface Driver' in the 'Sony sa0118' section (again, on just one of the three PCs that I installed the driver too, it said something different in that case)
thanx
thank you for this. I couldnt get anything to work until i tried this. very useful
sonyalmarshad said:
thanx
Click to expand...
Click to collapse
Aklenz07 said:
thank you for this. I couldnt get anything to work until i tried this. very useful
Click to expand...
Click to collapse
You're welcome, glad it helps some people.
Hi, This did not work...... (error code 10) when trying to update driver as in your instructions!...... which i thought might happen as youve directed us to the XZ2 driver instead of XA2 ULTRA driver!!!
Where the hell can I find the proper XA2 ULTRA driver?????? ...cant find anywhere...its crazy!!!
jake333at333 said:
Hi, This did not work...... (error code 10) when trying to update driver as in your instructions!...... which i thought might happen as youve directed us to the XZ2 driver instead of XA2 ULTRA driver!!!
Where the hell can I find the proper XA2 ULTRA driver?????? ...cant find anywhere...its crazy!!!
Click to expand...
Click to collapse
There is no XA2 Ultra driver, that's why we have to use the XZ2 one.
First, thank you for the great guide. Now, sorry about the possibly silly question, but I am a bit of a neophyte. I am able to follow these instructions and install the adb driver for the XA2 Ultra (all works as described). However, after I eject the phone and reconnect it while in USB debugging mode to try to use an adb command (to add a permission to write_secure_settings), Windows does not recognize the phone as an adb device. Thus I cannot do anything. I have tried this on two different Windows machines and the result is the same. Please apologies again if this is silly, but I feel I am missing something important. Thank you in advance.
Flaco05 said:
First, thank you for the great guide. Now, sorry about the possibly silly question, but I am a bit of a neophyte. I am able to follow these instructions and install the adb driver for the XA2 Ultra (all works as described). However, after I eject the phone and reconnect it while in USB debugging mode to try to use an adb command (to add a permission to write_secure_settings), Windows does not recognize the phone as an adb device. Thus I cannot do anything. I have tried this on two different Windows machines and the result is the same. Please apologies again if this is silly, but I feel I am missing something important. Thank you in advance.
Click to expand...
Click to collapse
Thanks, and you're welcome! I'm afraid I haven't actually used ADB that much with this phone. Does Device Manager actually list 'Sony sa0118 ADB Interface Driver' in the 'Sony sa0118' section (as I noted in the OP, on one or more PCs it said something different, and in a differently-named section)? You may find better help if you create a new thread in the general Q&A section since this problem doesn't deal directly with the driver installation problem that this thread is for. Good luck!
roirraW "edor" ehT said:
Does Device Manager actually list 'Sony sa0118 ADB Interface Driver' in the 'Sony sa0118' section (as I noted in the OP, on one or more PCs it said something different, and in a differently-named section)?
Click to expand...
Click to collapse
It does! All goes exactly like your screenshots indicate. But when you eject the phone and reconnect it again in USB Debugging mode, the ADB driver is gone, and you when type 'ADB devices' on CMD, nothing shows, so Windows cannot find it and it's not possible to run any commands. Let me do some more searching prior to starting a new thread.
Flaco05 said:
It does! All goes exactly like your screenshots indicate. But when you eject the phone and reconnect it again in USB Debugging mode, the ADB driver is gone, and you when type 'ADB devices' on CMD, nothing shows, so Windows cannot find it and it's not possible to run any commands. Let me do some more searching prior to starting a new thread.
Click to expand...
Click to collapse
Did you ever have any luck?
roirraW "edor" ehT said:
Did you ever have any luck?
Click to expand...
Click to collapse
Gave up temporarily; until my phone receives the Pie update.
Thanks for checking in!
works also on xa2 standard thank you
stuccamelo said:
works also on xa2 standard thank you
Click to expand...
Click to collapse
Awesome! You're welcome. Glad to help.
Thank you thank you thank you. I was about ready to give up on unlocking bootloader for my xa2 when i found this. Your a lifesaver. Now Ive installed /e/ on 3 devices. i'm 3 for 3 Your data is your data and everyone should take a look at this and ungoogle yourself.
eeloed said:
Thank you thank you thank you.
Click to expand...
Click to collapse
You're welcome!
I was having trouble Using NewFlasher v19 with the "H3223_Customized US_1312-1380_50.2.A.0.400_R2B" firmware I downloaded and extracted with XperiFirm. I kept getting the following:
Code:
ERROR: GetOverLapped_out_Result: failed with error code 1 as follows:
Incorrect function.
- Error write! Need nBytes: 0x18 but done: 0x0
nBytes[0x0]:
- Error writing command getvar:max-download-size!
This was on a relatively new (almost three months old) Windows 10 build 1903 installation, so I hadn't flashed my H3223 on this Windows build yet. I had installed without trouble the same XZ2 driver (they haven't updated it) but no luck. Finally I tried NewFlasher's GordonGate option, I extracted the archive, pointed Device Manager at this folder for the Sony ADB driver and it installed just fine. After that, NewFlasher flashed this just fine. I don't recall ever needing the GordonGate driver, nor it even working when I had attempted it previously.
I was still able to use the XZ2 driver to fastboot boot TWRP.img.
Just FYI if this helps anyone.
{
"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"
}
hi if anyone can help me install twrp on my xa2 ultra, try all possible methods and it is not possible. jump that error, someone who knows how to fix it? i want root to install lineage 17. thank you very much
maximdq said:
hi if anyone can help me install twrp on my xa2 ultra, try all possible methods and it is not possible. jump that error, someone who knows how to fix it? i want root to install lineage 17. thank you very much
Click to expand...
Click to collapse
I don't think you can install TWRP, but you can:
Code:
fastboot boot twrp.img
to boot it each time you want to use it while connected to your PC where you have the TWRP image named "twrp.img", and the latest Android platform tools (available at https://dl.google.com/android/repository/platform-tools-latest-windows.zip) in the same folder as twrp.img. Obviously you have almost all the steps correct, just wanted to spell it out for anyone else with the same problem.
roirraW "edor" ehT said:
I don't think you can install TWRP, but you can:
Code:
fastboot boot twrp.img
to boot it each time you want to use it while connected to your PC where you have the TWRP image named "twrp.img", and the latest Android platform tools (available at https://dl.google.com/android/repository/platform-tools-latest-windows.zip) in the same folder as twrp.img. Obviously you have almost all the steps correct, just wanted to spell it out for anyone else with the same problem.
Click to expand...
Click to collapse
sorry I do not understand. I can't install lineone 17 then? I speak Spanish and the translator does not understand well. Thank you
maximdq said:
I don't think you can install TWRP, but you can:
sorry I do not understand. I can't install lineone 17 then? I speak Spanish and the translator does not understand well. Thank you
Click to expand...
Click to collapse
Yes, your can flash anything you want once you "boot" twrp.img instead of "flash" (or install) it. This device probably doesn't have a discreet Recovery partition, same as on the Google Pixel. It's probably a combination Bootloader/Recovery partition, which is why you can't overwrite the recovery, any instead you have to boot TWRP directly each time you want to use it.
I don't speak Spanish although I had two years of it nearly 40 years ago, but let me know if this doesn't help or you don't figure it out, and I'll try to find an adequate Spanish translation for what I'm saying.

How to install the correct drivers for fastboot to a Windows 10 laptop?

Hi there, I'm a software developer but not an Android developer at all (I have no experience), so answers that are understandable to newbies would be very appreciated
My Moto X4 power button stopped working a few days ago (the phone doesn't register when it is pressed). Based on my Google searching this seems to be a common problem among many users of the phone. Luckily, it wasn't a big issue for me because I could still use the fingerprint scanner to lock/unlock the phone. The problem arose last night when I accidentally let my phone run completely out of battery. With no working power button, I could no longer turn on the phone!
This is especially an issue because I am in a foreign country right now so I can't send my phone in anywhere to get fixed. Yet I really need it for WhatsApp to contact some people today.
I have been following this guide (reddit - How to turn on your phone if/when your power button breaks) to install fastboot and use the reboot command to turn the phone on. Almost every step works fine for me (I successfully installed the Android SDK "platform tools", I can get my phone to go to the fastboot screen by holding the volume down button when plugging in the USB), the only problem is when I plug my phone (in fastboot mode) into my Windows 10 laptop, it does not seem to have the correct drivers installed to communicate with the device. So when I try to run the fastboot reboot command, it just gets stuck at <waiting for any devices> .
I have tried downloading the Motorola Device Manager executable (from here: https://support.motorola.com/us/en/drivers) to install the correct drivers, but even after doing that, when I plug my phone in, the Windows Device Manager still shows my phone as having the incorrect drivers.
{
"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 think that it is a compatibility issue. The first time after installing the Motorola software, Windows created a pop-up about the program potentially installing incorrectly and provided the option to re-install using compatibility settings, but since I hadn't tried the drivers at all yet at that point, I ignored it. I have not been able to reproduce the pop-up since.
How do I install the correct drivers so that I can run the fastboot reboot command?
I'm running 64-bit Windows 10 on an HP Envy laptop.
Any help is extremely appreciated, thank you so much!
Omninano said:
Hi there, I'm a software developer but not an Android developer at all (I have no experience), so answers that are understandable to newbies would be very appreciated
My Moto X4 power button stopped working a few days ago (the phone doesn't register when it is pressed). Based on my Google searching this seems to be a common problem among many users of the phone. Luckily, it wasn't a big issue for me because I could still use the fingerprint scanner to lock/unlock the phone. The problem arose last night when I accidentally let my phone run completely out of battery. With no working power button, I could no longer turn on the phone!
This is especially an issue because I am in a foreign country right now so I can't send my phone in anywhere to get fixed. Yet I really need it for WhatsApp to contact some people today.
I have been following this guide (reddit - How to turn on your phone if/when your power button breaks) to install fastboot and use the reboot command to turn the phone on. Almost every step works fine for me (I successfully installed the Android SDK "platform tools", I can get my phone to go to the fastboot screen by holding the volume down button when plugging in the USB), the only problem is when I plug my phone (in fastboot mode) into my Windows 10 laptop, it does not seem to have the correct drivers installed to communicate with the device. So when I try to run the fastboot reboot command, it just gets stuck at <waiting for any devices> .
I have tried downloading the Motorola Device Manager executable (from here: https://support.motorola.com/us/en/drivers) to install the correct drivers, but even after doing that, when I plug my phone in, the Windows Device Manager still shows my phone as having the incorrect drivers.
I think that it is a compatibility issue. The first time after installing the Motorola software, Windows created a pop-up about the program potentially installing incorrectly and provided the option to re-install using compatibility settings, but since I hadn't tried the drivers at all yet at that point, I ignored it. I have not been able to reproduce the pop-up since.
How do I install the correct drivers so that I can run the fastboot reboot command?
I'm running 64-bit Windows 10 on an HP Envy laptop.
Any help is extremely appreciated, thank you so much!
Click to expand...
Click to collapse
Hi, you can try uninstall from device manager, and run cmd cleanmgr-> clean system files, find device driver and click Ok, this erase all obsolete drivers, and install again Moto Device Manager
Or in the device manager, "update driver"->find driver on my pc->chose driver list, and find adb driver.
Good luck
pd. Sorry for my english, isnt y native languaje and my SO is in Spanish
Datclefxuj said:
Hi, you can try uninstall from device manager, and run cmd cleanmgr-> clean system files, find device driver and click Ok, this erase all obsolete drivers, and install again Moto Device Manager
Or in the device manager, "update driver"->find driver on my pc->chose driver list, and find adb driver.
Good luck
pd. Sorry for my english, isnt y native languaje and my SO is in Spanish
Click to expand...
Click to collapse
Hi Datclefxuj! No problem about the English, I understand what it is like to not be using your first language
I tried what you suggested, but there are a few small issues I ran into.
First, I uninstalled my phone from the device manager.
Then I ran 'cleanmgr' and clicked my C: drive.
But when you say "find device driver and click Ok", I don't know where the device drivers are located on my computer. Where would I typically find those? This is what my cleanmgr looks like:
Also, when you say "in the device manager, 'update driver'->find driver on my pc->chose driver list, and find adb driver", I do not have an adb driver to choose. Where would I download that from? Do I need an adb driver, anyway? I just want to be able to access fastboot on my phone.
I hope that makes sense. Thank you very much!
Omninano said:
Hi Datclefxuj! No problem about the English, I understand what it is like to not be using your first language
I tried what you suggested, but there are a few small issues I ran into.
First, I uninstalled my phone from the device manager.
Then I ran 'cleanmgr' and clicked my C: drive.
But when you say "find device driver and click Ok", I don't know where the device drivers are located on my computer. Where would I typically find those? This is what my cleanmgr looks like:
Also, when you say "in the device manager, 'update driver'->find driver on my pc->chose driver list, and find adb driver", I do not have an adb driver to choose. Where would I download that from? Do I need an adb driver, anyway? I just want to be able to access fastboot on my phone.
I hope that makes sense. Thank you very much!
Click to expand...
Click to collapse
it's here
or after to install motorola drivers
this is my drivers
https://drive.google.com/file/d/1chPe7UJpDC-rkSBoOGcmC0rJDYKmf966/view?usp=sharing
:good:
Datclefxuj said:
it's here
or after to install motorola drivers
this is my drivers
https://drive.google.com/file/d/1chPe7UJpDC-rkSBoOGcmC0rJDYKmf966/view?usp=sharing
:good:
Click to expand...
Click to collapse
MUCHAS GRACIAS!!!!
After following your steps, it worked! I am able to use my phone again!
En serio, thank you so much! I cannot thank you enough!
Omninano said:
MUCHAS GRACIAS!!!!
After following your steps, it worked! I am able to use my phone again!
En serio, thank you so much! I cannot thank you enough!
Click to expand...
Click to collapse
Great! You're welcome!

Question My computer doesn't recognize the phone in fastboot even with drivers installed

Hi all,
I really need your help, my computer doesn't recognize the phone in fastboot, I've installed different drivers and none of them work, in device manager it appears as Android with the yellow exclamation mark. I've already enabled USB Debugging mode, not sure what am I missing, please help.
Check in another USB Port, use original xiaomi's wire...and install latest USB drivers
I have the same problem, i'm using the original xiaomi wire and already installed lastest usb drivers.. the fact is that when I plug in the cell phone in fastboot mode the computer keeps sounds as connecting and disconnecting the device (I used two wires and two different computers)
Yup exact same thing, I hope somebody knows how to fix it and help us out.
Try with mi flash tool software for the computar... And let the program install the original firmware again... I think you can get rid of the problem
Ricardo 182 said:
Try with mi flash tool software for the computar... And let the program install the original firmware again... I think you can get rid of the problem
Click to expand...
Click to collapse
I'll try that, thanks for the help.
I had the same problem, and I fixed it changing the cellphone drivers in device manager, from: "Android" to ---------> "Xiaomi Composite MDB Interface".
Hope it helps someone.
seyren00 said:
I had the same problem, and I fixed it changing the cellphone drivers in device manager, from: "Android" to ---------> "Xiaomi Composite MDB Interface".
Hope it helps someone.
Click to expand...
Click to collapse
Can you please tell me how do I do that?
Ricardo 182 said:
Try with mi flash tool software for the computar... And let the program install the original firmware again... I think you can get rid of the problem
Click to expand...
Click to collapse
Tried that but still don't recognize the phone
seyren00 said:
I had the same problem, and I fixed it changing the cellphone drivers in device manager, from: "Android" to ---------> "Xiaomi Composite MDB Interface".
Hope it helps someone.
Click to expand...
Click to collapse
worked perfect for me! thank you!
liam_lost said:
Can you please tell me how do I do that?
Click to expand...
Click to collapse
{
"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"
}
seyren00 said:
View attachment 5365973
Click to expand...
Click to collapse
Thanks I tried but not sure why it shows this android one
liam_lost said:
Thanks I tried but not sure why it shows this android oneView attachment 5366067
Click to expand...
Click to collapse
Thats it bro, change that to Xiaomi Composite MDB interface, the first time my cellphone showed the same.
Ricardo 182 said:
Check in another USB Port, use original xiaomi's wire...and install latest USB drivers
Click to expand...
Click to collapse
Hi, where do I get the USB drivers? Even the official website says to make sure that "your PC has necessary drivers", but they don't provide any link where you can get them.
The Unlock Tool only has a "Check" button next to the version number, which says "5.5.224.24(Already latest)" and again, no drivers check. There are tons of fishy websites that claim to have the drivers and I have already tried several of them, but no success. Your help would be much appreciated.
Pino76 said:
Hi, where do I get the USB drivers? Even the official website says to make sure that "your PC has necessary drivers", but they don't provide any link where you can get them.
The Unlock Tool only has a "Check" button next to the version number, which says "5.5.224.24(Already latest)" and again, no drivers check. There are tons of fishy websites that claim to have the drivers and I have already tried several of them, but no success. Your help would be much appreciated.
Click to expand...
Click to collapse
https://c.mi.com/thread-3221402-1-0.html try using this guide bro.
seyren00 said:
https://c.mi.com/thread-3221402-1-0.html try using this guide bro.
Click to expand...
Click to collapse
Thank you, unfortunately, it didn't work for me. My device is still not showing up.
liam_lost said:
Hi all,
I really need your help, my computer doesn't recognize the phone in fastboot, I've installed different drivers and none of them work, in device manager it appears as Android with the yellow exclamation mark. I've already enabled USB Debugging mode, not sure what am I missing, please help.
Click to expand...
Click to collapse
Hi, after almost 2 days of constant researching and trying and failing and testing, I have finally figured it out! You need two things: MediaTek Driver and disabling Driver Signature Enforcement in Windows 10. It's because normally, the (64-bit) Windows 10 system won't allow you to install an unsigned driver and the Mediatek Driver is unsigned.
Here are the steps:
1. Press the Windows key on your keyboard, open PC settings
2. Go to Update & Security
3. Go to Recovery tab
4. Press & hold Shift key on your keyboard and click the Restart now button (in the Advanced startup section)
5. Select Troubleshoot ->Advanced setup -> Startup Settings and press Restart
6. Press 7 number key corresponding to "Disable driver signature enforcement" entry.
The system will now boot with the Driver Signature Enforcement disabled (it's going to be automatically enabled with the next restart). Download the Mediatek Driver (official source), unzip the file. Here's how I installed the driver:
1. Press the Windows key, type Device Manager and open the utility program
2. Click the top item in the list (your PC's name) and click Action in the menu and select Add Legacy Hardware.
3. Click Next in the Wizard, select Install hardware manually, and again Next and Next again.
4. Click Have Disk, Browse, navigate to the unzipped folder: SmartPhoneDriver > x64 > Unsigned infs and select the file android_winusb.inf. Click OK and select Media Tek Inc. in the left pane and then Next and Finish.
Your phone will now finally appear in the Unlock Tool.
This should work for all Note 10s users who also happen to have a 64-bit Windows 10 machine. Let me know how it went for you.
hey Guys, i´m new in the forum. But i had the same problem and i´m bringing the solution.
This error happens because Windows doesn´t recognize the bootloader, then you must install manually the bootloader´s driver and connect again your phone, so simple. I´m attaching the driver in this post.
Cheers.
download google usb driver: https://developer.android.com/studio/run/win-usb
connect phone to pc in fastboot mode. then go to device manager and update related driver named: android.
choose have disk and select Android_USB.inf file. then highlight Android bootloader interface and install driver. in win 10 must disable driver signature verification
seyren00 said:
View attachment 5365973
Click to expand...
Click to collapse
After searching for a long time, I found that this is the solution that works 100%. At last I was able to register the unlock of the bootloader today after a week of searching how to do it, since the driver did not work, thank you.

Categories

Resources