Database Develop

Required Help with connecting phone to PC in order to root

I am trying to root my device, to the final goal of installing a Nougat build on it. Been browsing through lots of guides, including this one which looks rather friendly:
https://www.idroidspace.com/how-to-root-htc-one-m7/
The problem is that the software did not recognize my phone.
I have enabled USB debugging. the PC detects the phone, I also have HTC Driver installed (downloaded HTC Sync Manager).
I also unlocked the boot-loader in the past, with success to the best of my knowledge (anyway I can confirm?).
Another problem I got that may come from the same source is that when opening command prompt and putting ADB Devices it wouldn't detect anything.
I have already old version of TWRP installed but I cannot flash the nougat from it, and in order to update the TWRP I wanted to root the device.
Am pretty much a beginner but can follow orders.

Droriley said:
I am trying to root my device, to the final goal of installing a Nougat build on it.
Click to expand...
Click to collapse
It's a waste of time to root if you're planning to flash a Nougat rom. It's a well spread misconception when ppl say "I want to root my phone" cause you're not rooting the phone, you're rooting the operating system on it (the rom). Most custom roms are pre-rooted so when flashing it on your phone you'll already have root. If you flash a non-rooted rom over your already rooted rom, you'll loose root hence why it's a waste of time to do it now. The only thing needed to flash a custom rom is a unlocked bootloader and a custom recovery.
Been browsing through lots of guides, including this one which looks rather friendly:
https://www.idroidspace.com/how-to-root-htc-one-m7/
The problem is that the software did not recognize my phone.
Click to expand...
Click to collapse
Outdated guide and tools
I also unlocked the boot-loader in the past, with success to the best of my knowledge (anyway I can confirm?).
Click to expand...
Click to collapse
Reboot in bootloader mode and check the first line of text it will either be ***LOCKED*** ***UNLOCKED*** or ***RELOCKED***
Another problem I got that may come from the same source is that when opening command prompt and putting ADB Devices it wouldn't detect anything.
Click to expand...
Click to collapse
Make sure you have the latest drivers version. ADB commands are only usable when booted in the OS with usb debugging turned on and you also need to unlock your screen once after connecting the phone to your PC. ADB commands will also work when booted in TWRP recovery. WIll not work in bootloader mode where you have to use FASTBOOT commands.
I have already old version of TWRP installed but I cannot flash the nougat from it
Click to expand...
Click to collapse
What is your twrp version and what rom do you want to flash? What is your "fastboot getvar all" ?
and in order to update the TWRP I wanted to root the device.
Click to expand...
Click to collapse
You don't need root to update TWRP, just flash the latest version using fastboot in bootloader mode:
Code:
fastboot flash recovery file_name.img
fastboot erase cache
fastboot reboot-bootloader

Alray, thanks for your thorough reply. I'd appreciate further help.
Reboot in bootloader mode and check the first line of text it will either be ***LOCKED*** ***UNLOCKED*** or ***RELOCKED***
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"
}
https://www.dropbox.com/s/iyxepbaiu4x1uva/2017-06-12 00.23.29.jpg?dl=0
I believe the Bootloader is indeed unlocked.
Make sure you have the latest drivers version. ADB commands are only usable when booted in the OS with usb debugging turned on and you also need to unlock your screen once after connecting the phone to your PC. ADB commands will also work when booted in TWRP recovery. WIll not work in bootloader mode where you have to use FASTBOOT commands.
Click to expand...
Click to collapse
I don't know where from do I get the latest ADB drivers. As said, I downloaded HTC Sync Manager.
USB Debugging is turned on.
I tried in TWRP Recovery - still with no success.
What is your twrp version and what rom do you want to flash? What is your "fastboot getvar all" ?
Click to expand...
Click to collapse
https://www.dropbox.com/s/n8gojoe3jgv8wzm/2017-06-12 00.24.19.jpg?dl=0
You don't need root to update TWRP, just flash the latest version using fastboot in bootloader mode:
Click to expand...
Click to collapse
Much like trying to flash the below rom - I was not able to flash the newer TWRP.
https://www.dropbox.com/s/l2wvgrhjgifjlcp/2017-06-12 00.24.51.jpg?dl=0
https://www.dropbox.com/sh/jhmyj852saithxa/AABalcp37aOSFrI2FTarRTUoa?dl=0
Code:
fastboot flash recovery file_name.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Need assistance with the step before.

Droriley said:
Alray, thanks for your thorough reply. I'd appreciate further help.
https://www.dropbox.com/s/iyxepbaiu4x1uva/2017-06-12 00.23.29.jpg?dl=0
I believe the Bootloader is indeed unlocked.
I don't know where from do I get the latest ADB drivers. As said, I downloaded HTC Sync Manager.
USB Debugging is turned on.
I tried in TWRP Recovery - still with no success.
https://www.dropbox.com/s/n8gojoe3jgv8wzm/2017-06-12 00.24.19.jpg?dl=0
Much like trying to flash the below rom - I was not able to flash the newer TWRP.
https://www.dropbox.com/s/l2wvgrhjgifjlcp/2017-06-12 00.24.51.jpg?dl=0
https://www.dropbox.com/sh/jhmyj852saithxa/AABalcp37aOSFrI2FTarRTUoa?dl=0
Need assistance with the step before.
Click to expand...
Click to collapse
TWRP 2.6.3.0 is really outdated. This version does not have the required kernel to support the fstab file system used by recent roms. You need at least twrp 2.7.1.1, or the latest version: 3.1.N0.0
Are you using the original usb cable that came with the phone? If no you might want to double check if your usb cable is capable of data transfer (there are usb cables that only have the +5v and ground connections for charging but not the data+ and data- connections). Try another usb ports/cable.

alray said:
TWRP 2.6.3.0 is really outdated. This version does not have the required kernel to support the fstab file system used by recent roms. You need at least twrp 2.7.1.1, or the latest version: 3.1.N0.0
Are you using the original usb cable that came with the phone? If no you might want to double check if your usb cable is capable of data transfer (there are usb cables that only have the +5v and ground connections for charging but not the data+ and data- connections). Try another usb ports/cable.
Click to expand...
Click to collapse
This one ain't good? https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html
any other way I can sort it out? I cannot manage to connect to my phone via command promp - I tried both in Fast boot and in Recovery.
PC feels the phone though - when on normal landing page I can see the phone content on explorer + it generates HTC Sync Manager.
Any way I can flash the updated TWRP from phone itself?

Droriley said:
PC feels the phone though - when on normal landing page I can see the phone content on explorer + it generates HTC Sync Manager.
Click to expand...
Click to collapse
You need to uninstall HTC sync manager, otherwise it will not work.
Or eaven better way is to install just naked drivers instead of sync manager.

Tarx100 said:
You need to uninstall HTC sync manager, otherwise it will not work.
Or eaven better way is to install just naked drivers instead of sync manager.
Click to expand...
Click to collapse
Where from?
Sent from my SM-G920F using Tapatalk

[GUIDE] Unbrick your Nokia 5

If your phone got stuck in 900E mode
-Hold Vol Up + Power for a few times to boot the phone to recovery mode
-Flash the ORIGINAL boot, system partitions and detele the data and cache partitions (choose flash image in TWRP for img files) (I used this yadi.sk/d/rcNFNnPp3MhtMe )
-Flash SuperSU in the recovery to patch the boot partition then reboot
If your phone got bootloop-ed
-Hold Vol Up + Power until the screen turns off then release
-Open OnlineUpdateTool (patched) and load your firmware in nb0 format
-Plug in your phone, it'll reboot to download mode
-Proceed to reflash the firmware
If your phone got stuck in 9008 mode
-Use @heineken78 's nb0 tools ( drive.google.com/file/d/0B3Wy4Ok3qGszaXhzM29YOEhrMW8 ) to extract the nb0 firmware
-Take the rawprogram, patch0 and firehose file with images in the rawprogram (search with the keyword filename) and put it inside a folder, rename according to the xml
-Load rawprogram, patch0 and firehose in QFIL, one by one to boot the phone
-You can use the firmware above for QFIL
Credits
@hikari_calyx for the method
@Quixote78 for OST and patch
These methods should also work on Nokia 2, 6, 7 (Although firmware isn't available for Nokia 7) and 8 in theory.
And, you can use EDL cable to force enter Qualcomm 9008, which doesn't work on Nokia 8. (Nokia 7 may not work either)
Click to expand...
Click to collapse

These methods should also work on Nokia 2, 6, 7 (Although firmware isn't available for Nokia 7) and 8 in theory.
And, you can use EDL cable to force enter Qualcomm 9008, which doesn't work on Nokia 8. (Nokia 7 may not work either)
Nokia 3? It has a MT6737M processor.

Hi, I'm now using Mac, where can I find the onlineUpdateTool? I have googled for quite some time.
Thanks
---------- Post added at 07:54 AM ---------- Previous post was at 07:46 AM ----------
Hi, I've found your onlineUpdateTool.zip, however, it requires password, could you please provide me? Tks

Hi, actually, my case is not bootlooped, it stucks on the recovery mode screen when I turn my phone on.
Please assist.

mrsilver256 said:
Hi, actually, my case is not bootlooped, it stucks on the recovery mode screen when I turn my phone on.
Please assist.
Click to expand...
Click to collapse
Password is 123
For stock recovery, power off the phone and plug in with OnlineUpdateTool open (rom loaded) and proceed to reflash
For TWRP, flash boot and system, delete data and cache then SuperSU root it

wolfyapl said:
Password is 123
For stock recovery, power off the phone and plug in with OnlineUpdateTool open (rom loaded) and proceed to reflash
For TWRP, flash boot and system, delete data and cache then SuperSU root it
Click to expand...
Click to collapse
Hi,
Is the stock rom is in here (nokia 5 included in name)
//mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg,
do I need to extract it to get nbo file?
Thank you

Hi,
I've run onlineUpdateTool.zip on windows 10 and it stops working all the time.

mrsilver256 said:
Hi,
I've run onlineUpdateTool.zip on windows 10 and it stops working all the time.
Click to expand...
Click to collapse
Have you installed it?

I don't really understand the thread
Help me. I don't think mine is bootloop because once it shows the Powered by android logo, after a few seconds it shut itself down. I've tried multiple methods like wipe data factory reset and installing OTA zips in the recovery mode but no luck at all. Is there any way to solve this problem?
I would really appreciate all the help.

mizuke said:
Help me. I don't think mine is bootloop because once it shows the Powered by android logo, after a few seconds it shut itself down. I've tried multiple methods like wipe data factory reset and installing OTA zips in the recovery mode but no luck at all. Is there any way to solve this problem?
I would really appreciate all the help.
Click to expand...
Click to collapse
If you use TWRP, reflash the ORIGINAL system.img and boot.img. Otherwise, reboot to bootloader

mrsilver256 said:
Hi,
I've run onlineUpdateTool.zip on windows 10 and it stops working all the time.
Click to expand...
Click to collapse
I'm running windows 7 and it's doing the same. :crying::crying:

mizuke said:
I'm running windows 7 and it's doing the same. :crying::crying:
Click to expand...
Click to collapse
Guys, install OST, patch it, and run from the installation folder after deleting config file

mrsilver256 said:
Hi,
I've run onlineUpdateTool.zip on windows 10 and it stops working all the time.
Click to expand...
Click to collapse
mizuke said:
I'm running windows 7 and it's doing the same. :crying::crying:
Click to expand...
Click to collapse
Try delete file: OnlineUpdateTool.exe.config in installation folder and start program again buddy.

thank you for this great post, i have nokia 5 ta-1024 and its dead, please provide me link of nokia ta-1024 firmware.

My nokia got bootlooped?Help please!!
I have powered android logo,(i was at twrp screen and i tried to set english theme i put file ui.zip to the sd card twrp/theme/ ticked first ZIP box at the first section and slided and then my phone nokia 5(TA-1053 ) rebooted and then i cant get to twrp again :\

Hi all, I have try to install this firmware ND1-3700-0-00WW-B03.nb0 on my Nokia 5 but when this phone restarts, I receive this message on Online Update Tool..
{
"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"
}

roxy94 said:
Hi all, I have try to install this firmware ND1-3700-0-00WW-B03.nb0 on my Nokia 5 but when this phone restarts, I receive this message on Online Update Tool..
Click to expand...
Click to collapse
Same problem here...

SimGa said:
Same problem here...
Click to expand...
Click to collapse
Same on my ta1024 ...omg dead phone without system... what to do?
Is this tool error or wrong firmware / nbo file maybe? its like a adb error ...
Now im using my lumia 950 ...

dex87xda said:
Same on my ta1024 ...omg dead phone without system... what to do?
Is this tool error or wrong firmware / nbo file maybe? its like a adb error ...
Now im using my lumia 950 ...
Click to expand...
Click to collapse
You need to flash any security OTA for 7.1 and then you can flash any firmware with OST

Hi,
I need help. I tried to flash Android 8 and it only says No command and I can't enter into the OS
Any help?
Thanks

HELP! I can boot into DOWNLOAD mode only, how to re-flash to oero?

STORY: My TA-1004 autoupdate to Android Pie on 22Dec after I turn off my phone to charge battery.
and I follow this " https://forum.xda-developers.com/nokia-8/development/android-9-0-pie-patched-boot-img-t3875977 " to try flash "fastboot flash boot "NB-01-551-b05-Magisk-TWRP" for flash TWRP and magisk to my TA-1004 pie. and I stuck on "nokia logo" after flash, someone said "Factory reset" , I try to use "wipe>format data" in TWRP, until now, I can boot in to download mode only.
I also try this "https://forum.xda-developers.com/nokia-8/how-to/guide-restore-nokia-to-stock-t3867646 "
to restore to oreo and stuck on "Next is greyed out, click on "Edit Phone Information", you will get an error message after a while, clik on OK, BUT Next is still greyed" . Can anyone help me please?

Please check that you have the correct fastboot drivers installed. Open Windows Device manager, and check the properties of your Fastboot device. Do you see HMD Global as the manufacturer? If not, the drivers may not be correct and you should install the Nokia drivers.

singhnsk said:
Please check that you have the correct fastboot drivers installed. Open Windows Device manager, and check the properties of your Fastboot device. Do you see HMD Global as the manufacturer? If not, the drivers may not be correct and you should install the Nokia drivers.
Click to expand...
Click to collapse
thx for reply first,
I can check "Fastboot Device" in Windows Device manager , HMD Global as the manufacturer.
I can check "fastboot devices" by adb/fastboot.exe

kelvin31 said:
thx for reply first,
I can check "Fastboot Device" in Windows Device manager , HMD Global as the manufacturer.
I can check "fastboot devices" by adb/fastboot.exe
Click to expand...
Click to collapse
It should work in that case. Give a try to the NOST tool shared in the Nokia 8 forums itself.

singhnsk said:
It should work in that case. Give a try to the NOST tool shared in the Nokia 8 forums itself.
Click to expand...
Click to collapse
NOST is it means Nokia OST (Online Service Tool) latest version and I need download android pie rom first?

kelvin31 said:
NOST is it means Nokia OST (Online Service Tool) latest version and I need download android pie rom first?
Click to expand...
Click to collapse
NOST" - short for "No Service Tool"
https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
You should use the existing NB0 which you have for the Nokia 8. I think it is on Oreo only. I hope you do have it.

singhnsk said:
It should work in that case. Give a try to the NOST tool shared in the Nokia 8 forums itself.
Click to expand...
Click to collapse
singhnsk said:
NOST" - short for "No Service Tool"
https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
You should use the existing NB0 which you have for the Nokia 8. I think it is on Oreo only. I hope you do have it.
Click to expand...
Click to collapse
THx
let me study it first,
thank you very much

singhnsk said:
NOST" - short for "No Service Tool"
https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
You should use the existing NB0 which you have for the Nokia 8. I think it is on Oreo only. I hope you do have it.
Click to expand...
Click to collapse
hello, I m stuck on unlock_critical, do you have any idea?
{
"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"
}

kelvin31 said:
hello, I m stuck on unlock_critical, do you have any idea?
Click to expand...
Click to collapse
You need to be flashing the actual unlock.bin file you used to unlock the Nokia 8. As you see in your CMD window, the command did not work out.
Make sure you're CMDing in the directory of your unlock file. Then send the command
Code:
fastboot flash unlock UnlockFile.bin
Remember to replace UnlockFile.bin with the name of actual unlock file in your PC.

singhnsk said:
You need to be flashing the actual unlock.bin file you used to unlock the Nokia 8. As you see in your CMD window, the command did not work out.
Make sure you're CMDing in the directory of your unlock file. Then send the command
Code:
fastboot flash unlock UnlockFile.bin
Remember to replace UnlockFile.bin with the name of actual unlock file in your PC.
Click to expand...
Click to collapse
unlock.bin is it provide by HMD that one?
I have receive my nokia 8 unlock bootloader file before by HMD,
name called unlock.key
is it this one? should I rename it to unlock.bin ?
thank you

kelvin31 said:
You need to be flashing the actual unlock.bin file you used to unlock the Nokia 8. As you see in your CMD window, the command did not work out.
Make sure you're CMDing in the directory of your unlock file. Then send the command
unlock.bin is it provide by HMD that one?
I have receive my nokia 8 unlock bootloader file before by HMD,
name called unlock.key
is it this one? should I rename it to unlock.bin ?
thank you
Click to expand...
Click to collapse
Yes, that's the one. You don't have to rename it. Just pass it the way you did earlier.
fastboot flash unlock unlock.key
When it gets accepted, then run:
fastboot flashing unlock_critical

singhnsk said:
Yes, that's the one. You don't have to rename it. Just pass it the way you did earlier.
fastboot flash unlock unlock.key
When it gets accepted, then run:
fastboot flashing unlock_critical
Click to expand...
Click to collapse
its work,
I need to flash unlock.key again even I unlocked my bootloader in september.
but I need flash again after auto update..
I also fastboot flashing unlock_critical, work too.
but got another problem.....
NOST tool error code: 0xa24b
ERROR= BATTERY_VOLTAGE_TOO_LOW_FAIL (0xA24B).
I can't charge or very very slow maybe.
I charge it over 1 hour still lower than NOST tool requirement(30%)...
my TA-1004 can not power off since first flash fail....
I keep saw "download mode" over light and I can't power off...
I did try volup + power, it turn off 2 sec and auto start again boot into download mode...
how can I force power off it?
thank you

kelvin31 said:
its work,
I need to flash unlock.key again even I unlocked my bootloader in september.
but I need flash again after auto update..
I also fastboot flashing unlock_critical, work too.
but got another problem.....
NOST tool error code: 0xa24b
ERROR= BATTERY_VOLTAGE_TOO_LOW_FAIL (0xA24B).
I can't charge or very very slow maybe.
I charge it over 1 hour still lower than NOST tool requirement(30%)...
my TA-1004 can not power off since first flash fail....
I keep saw "download mode" over light and I can't power off...
I did try volup + power, it turn off 2 sec and auto start again boot into download mode...
how can I force power off it?
thank you
Click to expand...
Click to collapse
You can power off the phone from the stock recovery or TWRP. That is, if you are able to boot into any of them. If you have the stock recovery file, then flash it to the phone. After that force reboot it and continue to hold the keys and it should go into recovery mode. The phone will essentially start faster in recovery mode. Or you can also choose the "Power off" option in recovery to power off the phone.
If you cannot get into recovery, then you cannot power it off. And in that case you will have to bear this slow charge only. Just plug it into a wall charger and leave it for a few hours. You can then check the battery capacity after connecting to the PC and sending the following command:
Code:
fastboot oem battery getcapacity
Start NOST and flash the phone if it is higher than the required

singhnsk said:
You can power off the phone from the stock recovery or TWRP. That is, if you are able to boot into any of them. If you have the stock recovery file, then flash it to the phone. After that force reboot it and continue to hold the keys and it should go into recovery mode. The phone will essentially start faster in recovery mode. Or you can also choose the "Power off" option in recovery to power off the phone.
If you cannot get into recovery, then you cannot power it off. And in that case you will have to bear this slow charge only. Just plug it into a wall charger and leave it for a few hours. You can then check the battery capacity after connecting to the PC and sending the following command:
Code:
fastboot oem battery getcapacity
Start NOST and flash the phone if it is higher than the required
Click to expand...
Click to collapse
THanks for help.
I charge it over 10 hrs, I did, I can flash NB1-488B Oreo 8.1 back, I can use my phone right now, thank you very much

Sony Xperia XA2 - Flashing TWRP stuck on "waiting for any device"

HELP!
I installed platform-tools_r33.0.2-windows and UniversalAdbDriverSetup, now i'm trying to flash TWRP on the XA2 Phone by using this cmd command:
adb devices
- daemon not running, starting now at xxx
adb flash recovery twrp.img
- waiting for any device
What am i doing wrong?? Please help!!
{
"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"
}

Boot phone in fastboot mode
Execute "fastboot flash recovery twrp.img"

LR7875 said:
Boot phone in fastboot mode
Execute "fastboot flash recovery twrp.img"
Click to expand...
Click to collapse
How? Im pressing volume up and then connecting the phone to the pc, then i see a blue light. Is this fastboot mode? Thats what im already doing for 3 hours...

Yeah just did it again... volumeup+connect phone to pc, blue light appears on phone (fastboot mode i asume).
on pc in cmd i type adb devices, it starts the daemon.
then i type "fasboot flash recovery twrp.img"
result in cmd: "waiting for any device"
Wtf?

I swear this is so cancer can't handle this ****, the F is wrong with sony? This phone is buggy AF im trying to insall TWRP for like 4 hours now, this is a ****ing joke. What a waste of time.

Try the 15 seconds adb and fastboot driver if you haven't already

LR7875 said:
Try the 15 seconds adb and fastboot driver if you haven't already
Click to expand...
Click to collapse
This? https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
I doubt it will be any different from the platformtools adb? How could this help?

LR7875 said:
Try the 15 seconds adb and fastboot driver if you haven't already
Click to expand...
Click to collapse
You mean minimal adb ? or can you provide a link?

Connect the phone in fastboot mode (LED = blue) and open the device manager. Do you see the phone under "Other Devices" or "Android" with an exclamation mark? Then you need an ADB/bootloader interface driver. Get this for example:
https://developer.sony.com/file/download/xperia-xz2-driver/
(Yes, XZ2! There is no official XA2 driver)
Unzip it somewhere and force install the driver:
Right click on the device manager entry from above, "Update driver", "Browse my computer...", "Let me pick...", "List/show all...", "Have disk...", browse to the folder from above, open the selected .inf file and install.
Fastboot should work now. At least that's how I got it to work on a new PC.
BTW, just use "fastboot devices" to check whether it works. If your device doesn't appear, you don't need to try other fastboot commands - it won't work.

I have this problem, when installing twrp to my Sony Xperia XA2 (H3123), I am trying to install several versions of Twrp, for example: twrp-3.2.2-0-pioneer.img, twrp-3.7.0_9-0 -pioneer.img, my Sony is on Android 9

Carljaynp03 said:
I have this problem, when installing twrp to my Sony Xperia XA2 (H3123), I am trying to install several versions of Twrp, for example: twrp-3.2.2-0-pioneer.img, twrp-3.7.0_9-0 -pioneer.img, my Sony is on Android 9
Click to expand...
Click to collapse

Did you unlock the bootloader ?

Carljaynp03 said:
View attachment 5734133
Click to expand...
Click to collapse
I agree with faraway, if i remember correctly when i had this issue i didn't unlock the bootloader.
I typed a specific number in the phone dial app and it said that the bootloader is unlocked, however there is another step you need to take that i had overlooked, you need a bootloader unlock code.
The code is free, not like with chinese spyware huawai they want your money for the code...
Unlock Bootloader - Open Devices - Sony Developer World
developer.sony.com
https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/how-to-unlock-bootloader/#tutorial-step-4
and use one of these commands in cmd/adb
fastboot flashing unlock
fastboot oem unlock

Carljaynp03 said:
View attachment 5734133
Click to expand...
Click to collapse
What is your end goal? To flash a custom ROM like LineageOS? Then you can temporarily flash a recovery image to the boot partition:
fastboot flash boot <recovery_filename>.img
You don't really need TWRP for this, just use the latest official LOS Recovery:
https://download.lineageos.org/pioneer
Also see: https://wiki.lineageos.org/devices/pioneer/install
Or do you want to "permanently" install TWRP on an existing system? Then you need to directly boot into TWRP and install it from its GUI:
fastboot boot <twrp_filename>.img
See: https://twrp.me/sony/sonyxperiaxa2.html
I haven't tried the latter on the XA2 yet though and don't know how permanent that installation really is. It maybe gone after an OTA update.

irgendwer2 said:
What is your end goal? To flash a custom ROM like LineageOS? Then you can temporarily flash a recovery image to the boot partition:
fastboot flash boot <recovery_filename>.img
You don't really need TWRP for this, just use the latest official LOS Recovery:
https://download.lineageos.org/pioneer
Also see: https://wiki.lineageos.org/devices/pioneer/install
Or do you want to "permanently" install TWRP on an existing system? Then you need to directly boot into TWRP and install it from its GUI:
fastboot boot <twrp_filename>.img
See: https://twrp.me/sony/sonyxperiaxa2.html
I haven't tried the latter on the XA2 yet though and don't know how permanent that installation really is. It maybe gone after an OTA update.
Click to expand...
Click to collapse
Booting a temprary image did not work when i tried it, most likely because the bootloader wasn't unlock.

Privacydroid said:
Booting a temprary image did not work when i tried it, most likely because the bootloader wasn't unlock.
Click to expand...
Click to collapse
Independent from the bootloader status: you can't flash an image directly to the recovery partition on the XA2/Pioneer (like he tried, see screenshot) because such a dedicated partition doesn't exist on this and other A/B devices. Instead the recovery is built into the boot image.
That's why you have to use fastboot flash boot instead of recovery.

irgendwer2 said:
Independent from the bootloader status: you can't flash an image directly to the recovery partition on the XA2/Pioneer (like he tried, see screenshot) because such a dedicated partition doesn't exist on this and other A/B devices. Instead the recovery is built into the boot image.
That's why you have to use fastboot flash boot instead of recovery.
Click to expand...
Click to collapse
follow the next steps you mentioned use: fastboot flash boot recovery from LineageOS, and my phone went into a constant boot shutdown and restart, then this message appeared

and the bootloader is open

Shutdown the phone after flashing the recovery image (it doesn't seem like you did that). Then hold Volume Down + Power to boot into recovery.

irgendwer2 said:
Independent from the bootloader status: you can't flash an image directly to the recovery partition on the XA2/Pioneer (like he tried, see screenshot) because such a dedicated partition doesn't exist on this and other A/B devices. Instead the recovery is built into the boot image.
That's why you have to use fastboot flash boot instead of recovery.
Click to expand...
Click to collapse
I get that the recovery is only for a temporary boot, when i tried it, it didn't work but i can't remember what the error was.

Question help - qualcomm crash dump

Hi,
had a rooted 2213 OP10 Pro.
Tried to update it to the latest C26 update locally. after it extracted, just rebooted without permission and I lost root.
opened magisk and there no option to inactive slot after ota.
booted into fastboot and flashed magisk patched boot. when it booted, opened magisk and there an option to write to inactive slot. did it.
after that, the phone is in qualcoom crash dump mode.
Can I recover it somehow ? what should i don next ?
please any advice, this is my work phone.

Lior84 said:
Hi,
had a rooted 2213 OP10 Pro.
Tried to update it to the latest C26 update locally. after it extracted, just rebooted without permission and I lost root.
opened magisk and there no option to inactive slot after ota.
booted into fastboot and flashed magisk patched boot. when it booted, opened magisk and there an option to write to inactive slot. did it.
after that, the phone is in qualcoom crash dump mode.
Can I recover it somehow ? what should i don next ?
please any advice, this is my work phone.
Click to expand...
Click to collapse
Can you go into bootloader mode?

TheNewHEROBRINE said:
Can you go into bootloader mode?
Click to expand...
Click to collapse
yes

{
"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"
}
This is probably the cause of the issue. Magisk switched your active slot to the previous one which becomes unbootable after the update completes successfully. You should be able to switch back to your working slot by doing fastboot --set-active=other, although I'm not 100% sure this is right solution I think it's a reasonable one. I'm always a bit scared suggesting solutions to people who have a recent OnePlus phone since they can't unbrick it if they end up in a hard brick.

TheNewHEROBRINE said:
View attachment 5847335
This is probably the cause of the issue. Magisk switched your active slot to the previous one which becomes unbootable after the update completes successfully. You should be able to switch back to your working slot by doing fastboot --set-active=other, although I'm not 100% sure this is right solution I think it's a reasonable one. I'm always a bit scared suggesting solutions to people who have a recent OnePlus phone since they can't unbrick it if they end up in a hard brick.
Click to expand...
Click to collapse
did't understood the command that you suggested.
did copy paste to it and it says unrecognized option

Lior84 said:
did't understood the command that you suggested.
did copy paste to it and it says unrecognized option
Click to expand...
Click to collapse
Is your phone in bootloader mode and recognized by fastboot? Can you send a screenshot of the command + error?

TheNewHEROBRINE said:
Is your phone in bootloader mode and recognized by fastboot? Can you send a screenshot of the command + error?
Click to expand...
Click to collapse
ok, opened updated platofrm tools and did what you said...
it's worked !!!
now is the only problem that I have no root
How I bring it back ? my version is NE2213_11_c.26

Lior84 said:
ok, opened updated platofrm tools and did what you said...
it's worked !!!
now is the only problem that I have no root
Click to expand...
Click to collapse
Boot the Magisk patched boot.img (don't flash it!). Then go into Magisk and do a direct install (DON'T do install to inactive slot). Then reboot and check if root is still there.

TheNewHEROBRINE said:
Boot the Magisk patched boot.img (don't flash it!). Then go into Magisk and do a direct install (DON'T do install to inactive slot). Then reboot and check if root is still there.
Click to expand...
Click to collapse
where to get it ? or how to make it ?

Lior84 said:
booted into fastboot and flashed magisk patched boot.
Click to expand...
Click to collapse
You can use the one you already have, you just need to do fastboot boot magisk_patched.img (or whatever it's called) instead of fastboot flash.

TheNewHEROBRINE said:
You can use the one you already have, you just need to do fastboot boot magisk_patched.img (or whatever it's called) instead of fastboot flash.
Click to expand...
Click to collapse
i did this. it sending it and succeeded. then says boot failed ( remote unrecognized command)

Lior84 said:
i did this. it sending it and succeeded. then says boot failed ( remote unrecognized command)
Click to expand...
Click to collapse
Are you sure you're in bootloader mode and not fastbootd?

Lior84 said:
i did this. it sending it and succeeded. then says boot failed ( remote unrecognized command)
Click to expand...
Click to collapse
adb reboot fastboot reboots you to fastbootd, not bootloader mode! You need to do adb reboot bootloader.

TheNewHEROBRINE said:
adb reboot fastboot reboots you to fastbootd, not bootloader mode! You need to do adb reboot bootloader.
Click to expand...
Click to collapse
OK, finally everything worked. I'm a little bit rusty (my first android was HTC desire back in 2010).
Thank you very much, You really saved me a lot of time and frustration !!! I already started to think how to get all the data back.
I really appreciate your help !!!
THank you again.
Lior

You're welcome!