I changed CID to GOOGL001 and tried to flash a RUU and somehow my hboot got f'd. It will not connect with adb or fastboot. The Android guy doesn't look well. Anyone know how I can fix this?
{
"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 still have the old firmware installed. The Google edition firmware version is inside brackets which means that there was an attemp to flash it bit it failed.
Sent from my HTC One using Tapatalk
Ivanovic said:
You still have the old firmware installed. The Google edition firmware version is inside brackets which means that there was an attemp to flash it bit it failed.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
OK, if it don't show up on fastboot, how can I re-flash firmware?
Can you enter recovery?
Sent from my HTC One using Tapatalk
Your bootloader is locked as well. get it unlocked.
Ivanovic said:
Can you enter recovery?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I do have twrp recovery and can get to it no problem. Phone works ok, but it loses data signal quite often and has to be rebooted to regain data.
SaHiLzZ said:
Your bootloader is locked as well. get it unlocked.
Click to expand...
Click to collapse
I tried HTC1Guru bootloader reset tool to unlock bootloader and it said successful, but still shows relocked.
When you connect your phone,fastboot or normal, isn't it recognised and listed under devices?
Sent from my HTC One using Tapatalk
Ivanovic said:
When you connect your phone,fastboot or normal, isn't it recognised and listed under devices?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
No, "waiting on device".
I can connect to see files when phone is booted up...just not adb or fastboot.
USB debugging enabled? Reinstall drivers for your OS.
Ivanovic said:
Enable usb debugging?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
No usb debugging was not on(DOH!) but after I put it on. adb devices did recognize when the phone was booted normally, however after I did adb reboot-bootloader then it rebooted in fastboot and back to "waiting on device"
Try the drivers uninstall/install thing if you have time but let the phone be on fastboot while installing the drivers
Sent from my HTC One using Tapatalk
I'm guessing what I need is either twrp flashable firmware or a RUU exe that will run with CID of GOOGL001.
...or maybe I'm just screwed. I actually got someone wanting to buy the phone, but I wanted to fix it first. I have another One as well. This one is an ATT version and my other is TMobile.
Maybe if bootloader unlocked it would help????
Ivanovic said:
Try the drivers uninstall/install thing if you have time but let the phone be on fastboot while installing the drivers
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
My other HTC One works fine in fastboot and I have installed the drivers a couple times...even back on a Win 7 machine now because I thought maybe it was the Win 8.1 on my laptop.
ok, I dunno whether we are two of a kind...but I literally have the exact same problem! But my device says "tampered and unlocked" on the top. But if I go into a root checker app...it tells me that "this phone isn't rooted...
Does anyone have a clue on how to work around this please! Thanks!
Gonna try this http://www.youtube.com/watch?v=Gqfly8XVw6w
Edit...nevermind. Not what I thought it was
Btw what happens when you try selecting "recovery mode" ? Mine just throws up a red triangle with an exclamation mark...
Scrowlerfly said:
Btw what happens when you try selecting "recovery mode" ? Mine just throws up a red triangle with an exclamation mark...
Click to expand...
Click to collapse
I get recovery ok (twrp) just can't see device in fastboot to reflash firmware upgrade.
Related
Okay, Im at a loss and need some help.
I tried to load a ROM and it went bad. I can access bootloader and TWRP recovery.
I dont have a nandroid backup. The ROM I attempted to install is corrupt.
I cant seem to MOUNT in TWRP or PUSH a new ROM.zip through recovery with ADB.
I believe this is because of losing debugging when I attempted to install the corrupt ROM.
FUBAR and dont know what to do!
Any suggestions or help would be greatly appreciated.
3.04.651.2 RUU
3.05.651.5 RUU
BD619 said:
3.04.651.2 RUU
3.05.651.5 RUU
Click to expand...
Click to collapse
BD, Ive tried to PUSH these with ADB but ADB isnt working, Im thinking this is due to debugging not being turned on. I cant turn it on because I have no operating system to boot into...
ChaseQ said:
BD, Ive tried to PUSH these with ADB but ADB isnt working, Im thinking this is due to debugging not being turned on. I cant turn it on because I have no operating system to boot into...
Click to expand...
Click to collapse
In ADB when I try adb usb I get,
ADB server is out of date. killing...
* daemon started successfully *
error: device not found
ChaseQ said:
In ADB when I try adb usb I get,
ADB server is out of date. killing...
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
You run these from your PC while booted to bootloader
BD619 said:
You run these from your PC while booted to bootloader
Click to expand...
Click to collapse
yes.
This is what I get if i try any commands in ADB
Im thinking this is an issue with not being able to turn on debugging due to a corrupt ROM I cant get into.
ChaseQ said:
yes.
This is what I get if i try any commands in ADB
Im thinking this is an issue with not being able to turn on debugging due to a corrupt ROM I cant get into.
Click to expand...
Click to collapse
Read the instructions posted in the 3.04 RUU thread
DB, Ill buy ya a case of beer if you get this mess Ive caused fixed!
{
"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"
}
BD619 said:
Read the instructions posted in the 3.04 RUU thread
Click to expand...
Click to collapse
OKAY! Giving that a try in the morning. If Im back up and running, beer money is on its way my friend!
Didnt work...I think Im having a driver issue or something. Fastboot and ADB just wont seem to see the device..
Not sure what you doing, but adb probably isn't all that interesting yet. You should be going to the bootloader, selecting fastboot, plugging your cable in, then running "fastboot devices" to check connectivity.
If no device shows up, try updating the drivers to the most recent bigdaddy619 posted in his various threads. One way or another, need fastboot working.
Also try Killing off ADB.exe in Win task manager. Then try again with a fresh one. When Flashing ViperOne 3.5, this helped me tremendously with the RUU.
Give us some details about your OS? Are you using Windows 7/8/8.1? 8 and 8.1 require different drivers.
Sent from my HTC Butterfly s using Tapatalk
Most of your useful adb work will probably be in a custom recovery (TWRP or CWM) at this stage; just saying that whether or not you've got debugging working really has no relevance at this point.
Did you get your phone up and running?
I've already read the forums in search of a solution, I've uninstalled all htc drivers and reinstalling a single htc one driver. adb push wont work cause it can't find the device... What had happen was, I installed viper one "successfully" and it kept rebooting after starting up, so I went into recovery and wiped everything so it kept bringing me back to bootloader, Now i can't install a rom cause of this "device not found" issue. I hate this so much, it happen before and somehow it randomly worked, but this time it seems like luck isn't on my side... halp.
nibblemynutz said:
I've already read the forums in search of a solution, I've uninstalled all htc drivers and reinstalling a single htc one driver. adb push wont work cause it can't find the device... What had happen was, I installed viper one "successfully" and it kept rebooting after starting up, so I went into recovery and wiped everything so it kept bringing me back to bootloader, Now i can't install a rom cause of this "device not found" issue. I hate this so much, it happen before and somehow it randomly worked, but this time it seems like luck isn't on my side... halp.
Click to expand...
Click to collapse
check FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
nkk71 said:
check FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
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"
}
Tried that, that's what i meant when i said i uninstalled the driver. and when I plugged it in without a driver it didn't say "one" anything, just unknown device.
As you can see the device is correctly installed. but still can't be found, and it isn't displaying under my computer.
nibblemynutz said:
Tried that, that's what i meant when i said i uninstalled the driver. and when I plugged it in without a driver it didn't say "one" anything, just unknown device.
As you can see the device is correctly installed. but still can't be found, and it isn't displaying under my computer.
Click to expand...
Click to collapse
looks like your phone is booted in bootloader, you must be booted in custom recovery to use adb commands. My phone is listed as ''My HTC'' when booted in OS or in bootloader and under ''Android adb interface'' when booted in recovery.
Cancel pc security and firewall...
Sent from my HTC One using xda premium
alray said:
looks like your phone is booted in bootloader, you must be booted in custom recovery to use adb commands. My phone is listed as ''My HTC'' when booted in OS or in bootloader and under ''Android adb interface'' when booted in recovery.
Click to expand...
Click to collapse
Tried it in fastboot/bootloader/ recovery twrp/
device still could not be found.
horst81, I disabled firewall and tried. no good.
Someone should just release an aio for this issue, it seems so easy to solve but then again nothing i've tried seems to be working.
Solved!!! I uninstalled the drivers and rebooted then tried everything again. this time I went into recovery mode and it actually worked.
Thanks alray.
Hey there,
I failed to upgrade my moto x to lollipop and accidentally erased the Android OS.
Basically, when I try to turn it on, it gets stuck at the moto bootlogo. If I press te volume down and the lock buttons, I do get to the boot screen (AP Fastboot Flash Mode), but, no matter what option I select, it goes back to the bootlogo and gets stuck again.
When I connect to my pc, it appears as Motorola ADB Interface at the device manager, even with Driver Signature Enforcement disabled. That makes it impossible for me to update the device with the RiffBox Drivers and, therefore, to have it accepted by Blankflash.
Is there any way to save this phone?
Thanks a lot in advance.
luiza1up said:
Hey there,
I failed to upgrade my moto x to lollipop and accidentally erased the Android OS.
Basically, when I try to turn it on, it gets stuck at the moto bootlogo. If I press te volume down and the lock buttons, I do get to the boot screen (AP Fastboot Flash Mode), but, no matter what option I select, it goes back to the bootlogo and gets stuck again.
When I connect to my pc, it appears as Motorola ADB Interface at the device manager, even with Driver Signature Enforcement disabled. That makes it impossible for me to update the device with the RiffBox Drivers and, therefore, to have it accepted by Blankflash.
Is there any way to save this phone?
Thanks a lot in advance.
Click to expand...
Click to collapse
Do you still need help with this brick?
Flarbenshweezel said:
Do you still need help with this brick?
Click to expand...
Click to collapse
Yes, please.
No one?
What model is your X? Is it a pure edition?
dustin_b said:
What model is your X? Is it a pure edition?
Click to expand...
Click to collapse
No. It wasn't the pure edition, but I unlocked the bootloader before screwing the firmware instalation
Dont worry its fixable. As long as you're still able to get it in to the boot loader mode.
Sent from my XT1095 using XDA Free mobile app
flameinthefire said:
Dont worry its fixable. As long as you're still able to get it in to the boot loader mode.
Sent from my XT1095 using XDA Free mobile app
Click to expand...
Click to collapse
What am I supposed to do, then?
Once I get to the bootloader, no matter what option I select, it goes back to that logo again and I get stuck.
Here you go..
How to unroot moto x(Return to stock): http://youtu.be/vFQiiMsDu9o
Sent from my XT1095 using XDA Free mobile app
luiza1up said:
What am I supposed to do, then?
Once I get to the bootloader, no matter what option I select, it goes back to that logo again and I get stuck.
Click to expand...
Click to collapse
You can flash your system.img in fastboot. You just have to find the right one for your model.
flameinthefire said:
Here you go..
How to unroot moto x(Return to stock): http://youtu.be/vFQiiMsDu9o
Sent from my XT1095 using XDA Free mobile app
Click to expand...
Click to collapse
It doesn't work since the phone is not recognized as a usb device. If I go to windows device manager, it shows the phone as Android Device - Motorola ADB Interface.
dustin_b said:
You can flash your system.img in fastboot. You just have to find the right one for your model.
Click to expand...
Click to collapse
How is that possible if all I can get is the fastboot screen, but any option selected leads to that boot logo again?
luiza1up said:
How is that possible if all I can get is the fastboot screen, but any option selected leads to that boot logo again?
Click to expand...
Click to collapse
What response do you get if you type "fastboot devices" ?
Steve-x said:
What response do you get if you type "fastboot devices" ?
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
0430820086 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>
luiza1up said:
How is that possible if all I can get is the fastboot screen, but any option selected leads to that boot logo again?
Click to expand...
Click to collapse
You flash from the fastboot screen. You don't select any of the options.
dustin_b said:
You flash from the fastboot screen. You don't select any of the options.
Click to expand...
Click to collapse
First of all, thanks for all the help.
Still, I did what you suggested and now it gets stuck on that Bootloader Unlocked Warning.
luiza1up said:
First of all, thanks for all the help.
Still, I did what you suggested and now it gets stuck on that Bootloader Unlocked Warning.
Click to expand...
Click to collapse
Which version of phone do you have and which version are you flashing?
Steve-x said:
Which version of phone do you have and which version are you flashing?
Click to expand...
Click to collapse
The version I used to have before was as it follows:
{
"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"
}
So, after rooting, I tried the LXE 22.46-17 firmware. That's when the OS was erased.
I finally managed to solve it.
It is a Nextel firmware, so I wasn't flashing the system.img right.
Thank you all for your kindness and answers.
Hey guys,
i have an big problem with my HTC One M7:
I installed "One_M7_7.15.401.1_stock_system_dump.zip" from HD Revolution to get on Lollipop but it showed an Error and after restarting i cant get into the Phone and i cant get into the recovery. The recovery pops up for like one second or less and throws me into a bootloop.
I wanted to flash a new Recovery via adb/fastboot but my Computer doesnt shows me my device. On the bootloader in the fastboot menu it shows "Fastboot USB" in red.
I installed much different drivers but it just doesnt show up. In device manager it says: Unknown USB Device (device failed enumeration) and the error code 43 in details.
I just dont know what to do anymore...
Anyone got an solution for that?
Mrdestroierr1 said:
Hey guys,
i have an big problem with my HTC One M7:
I installed "One_M7_7.15.401.1_stock_system_dump.zip" from HD Revolution to get on Lollipop
Click to expand...
Click to collapse
Not really sure why you installed this one. This is a non-official/leaked version before the official one was released (7.19.401.2) and the latest version is 7.19.401.51.
but it showed an Error
Click to expand...
Click to collapse
Would help to be more precise, what error exactly?
and after restarting i cant get into the Phone and i cant get into the recovery. The recovery pops up for like one second or less and throws me into a bootloop.
Click to expand...
Click to collapse
What recovery (name + version) is installed on your phone?
I wanted to flash a new Recovery via adb/fastboot but my Computer doesnt shows me my device. On the bootloader in the fastboot menu it shows "Fastboot USB" in red.
Click to expand...
Click to collapse
well at least you have "fastboot usb" which mean there is actually a working data connection between the phone and your ocmputer
I installed much different drivers but it just doesnt show up. In device manager it says: Unknown USB Device (device failed enumeration) and the error code 43 in details.
Click to expand...
Click to collapse
You need the latest drivers from htc. What is your windows version? What is your bootloader version?
sorry i had to make a new account:/
alray said:
Not really sure why you installed this one. This is a non-official/leaked version before the official one was released (7.19.401.2) and the latest version is 7.19.401.51.
Would help to be more precise, what error exactly?
some changes failed
What recovery (name + version) is installed on your phone?
i had cwm but i dont know which version (the m7 was inactive for 1-2 years)
well at least you have "fastboot usb" which mean there is actually a working data connection between the phone and your ocmputer
You need the latest drivers from htc. What is your windows version? What is your bootloader version?
i downloaded the drivers yesterday. i got windows 10 (im now trying with ubuntu). it got hboot 1.44
Click to expand...
Click to collapse
---------- Post added at 03:47 PM ---------- Previous post was at 03:25 PM ----------
I think i got it. Ubuntu worked. thanks alray for your answer. Because of you i checked HBoot 1.44 and this isnt compatible with Windows 10/8. In Ubuntu adb doesnt work but fastboot does. Now i flashed TWRP and installed the Rom again.
Now it boots up but it is in the boot screen since 5 Minutes:/
#Edit It doesnt boot up... and adb doesnt work so i cant push another rom on the phone..
#edit 2 adb works when im in recovery (tought i had to be in bootloader -> fastboot) now it could work with a downloaded nandroid backup :good:
mrdestroierrr1 said:
sorry i had to make a new account:/
Click to expand...
Click to collapse
You shouldn't, its against forum rules
http://forum.xda-developers.com/announcement.php?a=81
You should contact a moderator to disable the other account or this one might also be disabled.
I think i got it. Ubuntu worked. thanks alray for your answer. Because of you i checked HBoot 1.44 and this isnt compatible with Windows 10/8
Click to expand...
Click to collapse
Yep, exactly why I wanted to know, good job.
In Ubuntu adb doesnt work but fastboot does.
Click to expand...
Click to collapse
ADB will only work from a booted rom or from a custom recovery, not in bootloader mode.
{
"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"
}
help htc one m7
I am trying to send a ROOM from the computer to my internal memory via ADB sideload command to be able to install by twrp, so it is not going to talk that it is not possible to read, I tested with ADB devices and perfectly motra my device, someone can you help me?
C:\HTC>adb devices
List of devices attached
SH3ALW904272 sideload
C:\HTC>adb sideload Rom.zip
loading: 'Rom.zip'
* cannot read 'Rom.zip' *
C:\HTC>
ewvisjean said:
I am trying to send a ROOM from the computer to my internal memory via ADB sideload command to be able to install by twrp, so it is not going to talk that it is not possible to read, I tested with ADB devices and perfectly motra my device, someone can you help me?
C:\HTC>adb devices
List of devices attached
SH3ALW904272 sideload
C:\HTC>adb sideload Rom.zip
loading: 'Rom.zip'
* cannot read 'Rom.zip' *
C:\HTC>
Click to expand...
Click to collapse
What version of TWRP are you using?
Hey guys
I just bought a new Mi 9 Lite and instantanously wanted to unlock it.
so i did all the steps and then tried to connect with mi unlock the first time to see how long the waiting period is
After i booted into fastboot with volume down + power i connected the phone to the computer and it suddenly went black.
Only in the upper corner it showed a cut off text saying: "any key to shut down" -> see attached photo
{
"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"
}
Mi Unlock didnt detect it, and neither did Adb fastboot...
Do you know a fix? i really dont want to send it back...
And im pretty certain this was not my mistake, as i tried it multiple times
Same happens when you try to boot into fastboot with "adb reboot bootloader" ?
BTW to see if your device is properly recognized while you are in Fastboot you should use "Fastboot devices" not "adb devices"
Also make sure you installed all required drivers (Qualcomm ones and the drivers you install from within MiFlash)
the reason is windows 10, on 7 it works
k3lcior said:
Same happens when you try to boot into fastboot with "adb reboot bootloader" ?
BTW to see if your device is properly recognized while you are in Fastboot you should use "Fastboot devices" not "adb devices"
Also make sure you installed all required drivers (Qualcomm ones and the drivers you install from within MiFlash)
Click to expand...
Click to collapse
Thanks for your fast answer!
I just tried it again, and adb as well as fastboot devices do recognize the phone.
The blackscreen from fastboot only appears upon opening the mi flash unlock tool... In the exact same moment...
As you said i tried "adb reboot bootloader", but the same happened upon opening the tool.
I couldnt find the qualcomm ones though, didnt know where to install them from...
Btw. if it helps i have Windows 8.1
But havent had Problems with the Mi9 or Redmi 4 Prime unlock (which just now worked fine)
Romancier said:
I couldnt find the qualcomm ones though, didnt know where to install them from...
Click to expand...
Click to collapse
https://androidfilebox.com/tool/qualcomm-qdloader-hs-usb-driver-32-bit-64-bit/
k3lcior said:
androidfilebox....com/tool/qualcomm-qdloader-hs-usb-driver-32-bit-64-bit/
Click to expand...
Click to collapse
Installed it, and even re-installed all the usual drivers. Still, the black screen pops up as soon as i open the unlock tool...
Check if your phone isn't fake one.
This is unusual for an official Xiaomi device.
arvarobert said:
Check if your phone isn't fake one.
This is unusual for an official Xiaomi device.
Click to expand...
Click to collapse
How would i check?
Also its not from china, but from a well known german vendor so guarantee would be no problem. But everything is fine and believable, so i would have no reason to be suspicious.
I guess i will try with another computer next week or something. Maybe its USB 2.0 or something..
At least thats what that thread suggests: https://forum.xda-developers.com/redmi-note-5-pro/help/help-press-key-to-shutdown-fastboot-t3816021
Thanks for your suggestions!!!
Romancier said:
How would i check?
Also its not from china, but from a well known german vendor so guarantee would be no problem. But everything is fine and believable, so i would have no reason to be suspicious.
I guess i will try with another computer next week or something. Maybe its USB 2.0 or something..
At least thats what that thread suggests: https://forum.xda-developers.com/redmi-note-5-pro/help/help-press-key-to-shutdown-fastboot-t3816021
Thanks for your suggestions!!!
Click to expand...
Click to collapse
Is your phone recognized in device manager when you are in fastboot?
Also i heard there is some bug/incompatibility with Ryzen CPU's, do you have Ryzen or Intel?
k3lcior said:
Is your phone recognized in device manager when you are in fastboot?
Also i heard there is some bug/incompatibility with Ryzen CPU's, do you have Ryzen or Intel?
Click to expand...
Click to collapse
Indeed it is recognizes in adb as well as in fastboot.
It's an old Thinkpad im working on, so its an Intel. I still only have simple Usb-ports.
But im surprised as it has worked with the Mi 9 also a few weeks ago...