Fastboot non-responsive - HTC U11 Questions & Answers

Hi all,
i got my U11 yesterday. i came to unlock the bootloader and fastboot doesnt recognise the phone. i tested it on my htc 10 and one plus 5 and both respond to getvar all and show as devices

rwallhtc said:
Hi all,
i got my U11 yesterday. i came to unlock the bootloader and fastboot doesnt recognise the phone. i tested it on my htc 10 and one plus 5 and both respond to getvar all and show as devices
Click to expand...
Click to collapse
USB debugging on in developer options?

jhill110 said:
USB debugging on in developer options?
Click to expand...
Click to collapse
yes i had this checked. although both the other phones worked fine i downloaded htc sync and it loaded new drivers. all working now

rwallhtc said:
Hi all,
i got my U11 yesterday. i came to unlock the bootloader and fastboot doesnt recognise the phone. i tested it on my htc 10 and one plus 5 and both respond to getvar all and show as devices
Click to expand...
Click to collapse
Your computer is running Windows or Linux?

Related

Bricked Sensation | It doesn't boot

First off all, sorry for my horrible english
Today I wanted to make S-Off with the juopunutbear tool for windows (version 0,4) but it crashed and now I cant start my phone. I am always starting automatically in to the bootloader.
My first fault was that I hadn't installed the stock RUU. And my second fault was that I interrupted the process.when the juopunutbear logo was on my screen.
My computer doesnt detect my phone in the fastboot mode -.- I have all backups which were made by juopunutbear
Is there any possibility to repair the phone or is it dead? It is unlocked by HTC Dev.
If you need more Information, say it.
StormUltimate said:
First off all, sorry for my horrible english
Today I wanted to make S-Off with the juopunutbear tool for windows (version 0,4) but it crashed and now I cant start my phone. I am always starting automatically in to the bootloader.
My first fault was that I hadn't installed the stock RUU. And my second fault was that I interrupted the process.when the juopunutbear logo was on my screen.
My computer doesnt detect my phone in the fastboot mode -.- I have all backups which were made by juopunutbear
Is there any possibility to repair the phone or is it dead? It is unlocked by HTC Dev.
If you need more Information, say it.
Click to expand...
Click to collapse
You can access to bootloader or the device is not starting at all?
StormUltimate said:
First off all, sorry for my horrible english
Today I wanted to make S-Off with the juopunutbear tool for windows (version 0,4) but it crashed and now I cant start my phone. I am always starting automatically in to the bootloader.
My first fault was that I hadn't installed the stock RUU. And my second fault was that I interrupted the process.when the juopunutbear logo was on my screen.
My computer doesnt detect my phone in the fastboot mode -.- I have all backups which were made by juopunutbear
Is there any possibility to repair the phone or is it dead? It is unlocked by HTC Dev.
If you need more Information, say it.
Click to expand...
Click to collapse
Do you have all drivers for fastboot installed correctly?
Mile_zdr said:
You can access to bootloader or the device is not starting at all?
Click to expand...
Click to collapse
I can access to bootloader, it is starting automatically in to it.
szotaa said:
Do you have all drivers for fastboot installed correctly?
Click to expand...
Click to collapse
I think yeah. I downloaded the adb things and copied it to "C:\adb". I installed HTC drivers by installing HTC sync. I deinstalled HTC sync after installing it but it did not delete the drivers.
EDIT: I am booting automatically to the juponutBear screen but I can access to bootloader.
And it is Version 0.5 and not 0.4 ^^
StormUltimate said:
I can access to bootloader, it is starting automatically in to it.
I think yeah. I downloaded the adb things and copied it to "C:\adb". I installed HTC drivers by installing HTC sync. I deinstalled HTC sync after installing it but it did not delete the drivers.
EDIT: I am booting automatically to the juponutBear screen but I can access to bootloader.
And it is Version 0.5 and not 0.4 ^^
Click to expand...
Click to collapse
you can post what your bootloader says or take a pic of what your bootloader look ?
StormUltimate said:
I think yeah. I downloaded the adb things and copied it to "C:\adb". I installed HTC drivers by installing HTC sync. I deinstalled HTC sync after installing it but it did not delete the drivers.
Click to expand...
Click to collapse
Download this file: http://www.filedropper.com/fastbootflash
Unzip it. Plug in you phone to PC via usb to PC in fastboot mode. (bootloader must say fastboot usb)
Open start here.bat from folder you just have downloaded. Then type "fastboot devices" in start here.bat window. If nothing happens then your phone may not respond to fastboot or you have drivers wrongly installed. If it gives some numbers then your fastboot is working correctly. In case of nothing happening I reccomend installing universal naked driver ( http://forum.xda-developers.com/showthread.php?t=1161769 ) and repeating steps i gave you.
Mile_zdr said:
you can post what your bootloader says or take a pic of what your bootloader look ?
Click to expand...
Click to collapse
It is everything normal but I cant make a pic without a phone ^^
szotaa said:
Download this file: http://www.filedropper.com/fastbootflash
Unzip it. Plug in you phone to PC via usb to PC in fastboot mode. (bootloader must say fastboot usb)
Open start here.bat from folder you just have downloaded. Then type "fastboot devices" in start here.bat window. If nothing happens then your phone may not respond to fastboot or you have drivers wrongly installed. If it gives some numbers then your fastboot is working correctly. In case of nothing happening I reccomend installing universal naked driver ( http://forum.xda-developers.com/showthread.php?t=1161769 ) and repeating steps i gave you.
Click to expand...
Click to collapse
I tried it and it doesnt work. I downloaded the naked drivers and installed it (Windows 8.1) but it doesnt worked. No response from fastboot. And there is no "fastboot usb" only "fastboot".
StormUltimate said:
It is everything normal but I cant make a pic without a phone ^^
I tried it and it doesnt work. I downloaded the naked drivers and installed it (Windows 8.1) but it doesnt worked. No response from fastboot. And there is no "fastboot usb" only "fastboot".
Click to expand...
Click to collapse
To make it say fastboot usb you sometimes have to connect your phone to pc on fastboot and then press vol up or down to refresh it and then fastboot usb appears.
Wysłane z mojego HTC Sensation przy użyciu Tapatalka
szotaa said:
To make it say fastboot usb you sometimes have to connect your phone to pc on fastboot and then press vol up or down to refresh it and then fastboot usb appears.
Wysłane z mojego HTC Sensation przy użyciu Tapatalka
Click to expand...
Click to collapse
Ok, fastboot USB is there. My Computer say all the time "Device cannot be recognized / identify" -.- Yeah, I reinstalled the drivers.
P.S. You can write in polish I can speak and read polish but my written polish is more horrible than my written english
StormUltimate said:
Ok, fastboot USB is there. My Computer say all the time "Device cannot be recognized / identify" -.- Yeah, I reinstalled the drivers.
P.S. You can write in polish I can speak and read polish but my written polish is more horrible than my written english
Click to expand...
Click to collapse
Then IDK whats the problem. You may try installing ruu (but as far as I know it requires working fastboot to install) which can be found in sensation android development section. I'll dig the forum tommorow looking for fix because Im too tired today. Sorry :c. I wish I could write in polish but this is an english forum and it is not allowed to speak other launage over here.
Wysłane z mojego HTC Sensation przy użyciu Tapatalka
StormUltimate said:
It is everything normal but I cant make a pic without a phone ^^
I tried it and it doesnt work. I downloaded the naked drivers and installed it (Windows 8.1) but it doesnt worked. No response from fastboot. And there is no "fastboot usb" only "fastboot".
Click to expand...
Click to collapse
since you are in windows 8.1 use these drivers
http://d-h.st/CE9
also you are seeing the jb screen because probably you didn't remove the temproot
rzr86 said:
since you are in windows 8.1 use these drivers
http://d-h.st/CE9
also you are seeing the jb screen because probably you didn't remove the temproot
Click to expand...
Click to collapse
The drivers doesnt work -.-
I had perm root (I think). Root was all the time active.
I will try it later on an other computer with Windows 7 and if it doesnt work, I will buy a new (not completly news ) HTC Sensation. But it is the last possibility
StormUltimate said:
The drivers doesnt work -.-
I had perm root (I think). Root was all the time active.
I will try it later on an other computer with Windows 7 and if it doesnt work, I will buy a new (not completly news ) HTC Sensation. But it is the last possibility
Click to expand...
Click to collapse
by the way you can flash a ruu manually without pc
no need to buy another sensation
rzr86 said:
by the way you can flash a ruu manually without pc
no need to buy another sensation
Click to expand...
Click to collapse
The other PC is working <3 Fastboot is working ^^ I try to install my backup but you can give me an instruction
It is working again : D <3 Recovery is working, I think that I will make the rest alone.
EDIT: Working 100% now

HTC One A9 ADB command devices OFFLINE NOTHING FIXES! plz help

Well, I managed to previously unlock bootloader, flash TWRP, then rooted an A9 I got on eBay for sprint. When I factory reset it, it went into some French mode, so I decided to start clean and used the official HTC 1.57XXXX RUU.exe Im still unlocked and S-off but I am not rooted and dont have TWRP.
SO now my problem; I CANNOT ****in get ADB command to pickup the A9, all it outputs is OFFLINE.
I went as far as CLEAN install of windows ten. Wiped EVERYTHING.
installed HTC sync manager
installed 15 ADB
restart computer
at this point any normal human being would think that the ADB command should pickup the phone by now.
BTW I've set developer mode, OEM unlocking and usb debugging and accepted that this computer can transfer files.
This sucks. please help. This is day 3 of troubleshooting on my own for something that should have been done in an hour
wholigan423 said:
Well, I managed to previously unlock bootloader, flash TWRP, then rooted an A9 I got on eBay for sprint. When I factory reset it, it went into some French mode, so I decided to start clean and used the official HTC 1.57XXXX RUU.exe Im still unlocked and S-off but I am not rooted and dont have TWRP.
SO now my problem; I CANNOT ****in get ADB command to pickup the A9, all it outputs is OFFLINE.
I went as far as CLEAN install of windows ten. Wiped EVERYTHING.
installed HTC sync manager
installed 15 ADB
restart computer
at this point any normal human being would think that the ADB command should pickup the phone by now.
BTW I've set developer mode, OEM unlocking and usb debugging and accepted that this computer can transfer files.
This sucks. please help. This is day 3 of troubleshooting on my own for something that should have been done in an hour
Click to expand...
Click to collapse
You should try changing USBcable
romanch said:
You should try changing USBcable
Click to expand...
Click to collapse
I did. I have HTC official from the A9 that should be 100% good and another from my GF's M9 and neither are working this is hopeless!
So "adb devices" give your nothing? not a mes on the phone to let adb connect?
Sent from my HTC One A9 using XDA-Developers mobile app
jaypeg123 said:
So "adb devices" give your nothing? not a mes on the phone to let adb connect?
Sent from my HTC One A9 using XDA-Developers mobile app
Click to expand...
Click to collapse
Must have been a driver error because I was able to do it on my other laptop no problem. The weird thing is I flashed twrp via ADB on the A9 (on my pc before getting errors) and then I did my girlfriends M9 and thats when the drivers got funky.
Still tho problem remains I get device offline if I try to hook up to my PC, if it was because of any settings to select on my phone it would say "unauthorized" but thats not the case, I've authorized the phone for usb debugging to my PC
The offline must be due to you using the wrong version of adb, or could it be a firewall/antivirus prog blocking connection?
Sent from my HTC One A9 using XDA-Developers mobile app

Problem with unlocking bootloader

Hey everyone,
So I got my Mi Mix 3 yesterday and I wanted to unlock the bootloader. ( for obvious reasons )
But I encountered a problem. I can't get the Mi Unlock Utility to detect my Mix 3, even though I can communicate with it via ADB
I think I have permission to unlock it, since I get to the unlocking screen
I'm thinking it might be a problem with the drivers.
Or maybe it is a problem with fastboot, because it doesn't show up when I type "fastboot devices"
And yes, I entered fastboot mode with power+volume down.
Did anyone else encounter this problem?
Thanks in advance.
No screenshots because I can't post links yet unfortunately.
Device: Xiaomi Mi Mix 3
MIUI: Miui 10.0 | Stable 10.0.12.0(PEECHFH)
Kernel: 4.9.112-perf-gba589af
Hardware: V1
on
Windows 10 x64 1803
Ryzen 5 1600
CaptainTimo said:
I'm thinking it might be a problem with the drivers.
Or maybe it is a problem with fastboot, because it doesn't show up when I type "fastboot devices"
And yes, I entered fastboot mode with power+volume down.
Click to expand...
Click to collapse
Update:
I installed the Google USB Drivers and Fastboot is working, only when I start the Utility my phone displays:
Code:
Press any key to shutdown
After that, I can't connect to it in fastboot until I fully restart my PC.
Did u activated USB debugging from developer option?
PeppeCNN said:
Did u activated USB debugging from developer option?
Click to expand...
Click to collapse
You don't need usb debugging for unlocking with fastboot
CaptainTimo said:
Update:
I installed the Google USB Drivers and Fastboot is working, only when I start the Utility my phone displays:
.
Click to expand...
Click to collapse
Turns out windows 10 doesn't like to unlock Xiaomi phones.
I used a pc with windows 7 and it worked. Now have to wait a few more hours before I can unlock.
I am having the same problem as you, any idea how to fix it without windows 7?
xstewminator said:
I am having the same problem as you, any idea how to fix it without windows 7?
Click to expand...
Click to collapse
You can also use Windows 8 or 8.1. But other than that I couldn't find any other solution.
Maybe you can try to setup dual-boot on your windows 10 machine, so you have windows 10 and 8.1 installed at the same time. And use the 8.1 for unlocking/flashing your Mix 3.
CaptainTimo said:
You can also use Windows 8 or 8.1. But other than that I couldn't find any other solution.
Maybe you can try to setup dual-boot on your windows 10 machine, so you have windows 10 and 8.1 installed at the same time. And use the 8.1 for unlocking/flashing your Mix 3.
Click to expand...
Click to collapse
Windows 10 - disable driver enforcement
Mackay53 said:
Windows 10 - disable driver enforcement
Click to expand...
Click to collapse
Didn't work for me
CaptainTimo said:
Didn't work for me
Click to expand...
Click to collapse
What steps did you do after booting into win10 from advanced boot options
Mackay53 said:
What steps did you do after booting into win10 from advanced boot options
Click to expand...
Click to collapse
I used a CMD command and rebooted my PC to disable driver enforcement.
But I already succeeded in unlocking and flashing the EU rom using a windows 8 PC.
Mackay53 said:
Windows 10 - disable driver enforcement
Click to expand...
Click to collapse
So I've tried that, for some reason it still has the same problem... I'm going to try to do it on a windows 8.1 machine, but I'm not very hopeful...
Also sometimes it gets to the point of recognizing the device, but then it says device is unlocked, but it actually isnt...
picture attached
xstewminator said:
So I've tried that, for some reason it still has the same problem... I'm going to try to do it on a windows 8.1 machine, but I'm not very hopeful...
Also sometimes it gets to the point of recognizing the device, but then it says device is unlocked, but it actually isnt...
picture attached
Click to expand...
Click to collapse
Have you bound the phone to your account via settings and enable OEM unlock from dev options?
Ok well, I got it to work on my windows 8.1 machine.
This does appear to be an issue with windows 10 in some way.
Now to wait 53 hours... RIP
xstewminator said:
Ok well, I got it to work on my windows 8.1 machine.
This does appear to be an issue with windows 10 in some way.
Now to wait 53 hours... RIP
Click to expand...
Click to collapse
With Windows 10 works...if was unlocked, what u have to wait 53 h? I didn't understood
What RIP?
PeppeCNN said:
With Windows 10 works...if was unlocked, what u have to wait 53 h? I didn't understood
What RIP?
Click to expand...
Click to collapse
You have to wait so many hours before you can unlock, usually 72 hours
Mackay53 said:
You have to wait so many hours before you can unlock, usually 72 hours
Click to expand...
Click to collapse
Maybe I misunderstood...he told before that was unlocked...or was someone else?
Inviato dal mio MIX 3 utilizzando Tapatalk
I also encountered some driver difficulties with Windows 7. My issue was a previously-installed Samsung driver which Windoze was using for the Xiaomi phone. If you have an old driver, Samsung or generic, you need to uninstall it first from the Windoze Add/Remove Programs screen. The Xiaomi driver, once installed, also seemed to cause some problems with other USB drivers, now when I boot it takes a couple of minutes before the keyboard and mouse start working, not a big deal, just another thing to add to the long list of intractable problems with my Windoze installation.
You probably were getting that error due to another running instance of adb server. Try running adb kill-server in admin command prompt, then open the Xiaomi utility.
Sent from my Mi MIX 3 using Tapatalk
Mackay53 said:
Windows 10 - disable driver enforcement
Click to expand...
Click to collapse
It failed for me. I have usb debugging on, OEM unlock is on...
I have correct drivers fastboot adb
not sure what else to do.
Any ideas? Or is windows 10 a lost cause?

(XT2005-3) ADB drivers not working

I've been trying for 2 days now. USB debugging has been on through all of it.
The drivers from the Motorola website install and the plug-in sound is sounded when it is plugged in. When the phone is on the driver works, but not when it's in fastboot mode. When I go into the device management window, it shows that the Motorola driver is active, but the e6 itself isn't really mounted, it's not recognized by adb or Windows itself. When I uninstall the Motorola drivers from the device manager, a driver something along the lines of "Surfna S" appears with an exclamation mark next to it. So the driver is broken and also not the right kind because I have an e6, not an e6S. Am I even doing the right thing? How can i get the drivers working?
EnokiPPT said:
I've been trying for 2 days now. USB debugging has been on through all of it.
The drivers from the Motorola website install and the plug-in sound is sounded when it is plugged in. When the phone is on the driver works, but not when it's in fastboot mode. When I go into the device management window, it shows that the Motorola driver is active, but the e6 itself isn't really mounted, it's not recognized by adb or Windows itself. When I uninstall the Motorola drivers from the device manager, a driver something along the lines of "Surfna S" appears with an exclamation mark next to it. So the driver is broken and also not the right kind because I have an e6, not an e6S. Am I even doing the right thing? How can i get the drivers working?
Click to expand...
Click to collapse
It's possible that you need to manually select the USB driver
See my drivers post in
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my ali using XDA Labs
sd_shadow said:
It's possible that you need to manually select the USB driver
See my drivers post in
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Hey, I know this and old post but you seem very well informed on the topic I'd like you to answer one question, please.
I have almost the same problem as OP, I have a Moto e6s, I check the drivers and the PC detects when the phone is connected and disconnected but I can't pass the < waiting for device> command.
I used to have a device that requires me to hold up some button to engage the fastboot commands but I'm not sure if this could be the case on any Moto.
Thanks in advance.
Teh_Chuz said:
Hey, I know this and old post but you seem very well informed on the topic I'd like you to answer one question, please.
I have almost the same problem as OP, I have a Moto e6s, I check the drivers and the PC detects when the phone is connected and disconnected but I can't pass the < waiting for device> command.
I used to have a device that requires me to hold up some button to engage the fastboot commands but I'm not sure if this could be the case on any Moto.
Thanks in advance.
Click to expand...
Click to collapse
What does the phone screen say?
Window 10?
Window device manager says Motorola adb device?
Sent from my ocean using XDA Labs
sd_shadow said:
What does the phone screen say?
Window 10?
Window device manager says Motorola adb device?
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
The phone screen just shows some bar code the moment I connect the USB.
Yes is Windows 10
Devices manager recognize the device as Android Phone> Android ADB Interface
Also, I have another phone a Huawei and the fastboot commands work fine on that phone.
This is not my phone but it looks like this plus the bar code
https://imgur.com/a/vPHW5Dv
Teh_Chuz said:
The phone screen just shows some bar code the moment I connect the USB.
Yes is Windows 10
Devices manager recognize the device as Android Phone> Android ADB Interface
Also, I have another phone a Huawei and the fastboot commands work fine on that phone.
This is not my phone but it looks like this plus the bar code
https://imgur.com/a/vPHW5Dv
Click to expand...
Click to collapse
Motorola device in fastboot mode should look like this see attached.
Sent from my ocean using XDA Labs
I suspect that Motorola devices that show a barcode have a restricted fastboot mode by carrier request, but that's just a guess.
Sent from my ocean using XDA Labs
sd_shadow said:
I suspect that Motorola devices that show a barcode have a restricted fastboot mode by carrier request, but that's just a guess.
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
I don't think so, I bought it through Amazon so is not attached to any carrier. I used to have a Moto e5 from Verizon and the Huawei are both blocked but I can use <fastboot devices> on those, not this one. I found it very weird. Any other idea? :c
Look I found these videos, they show how to wipe a phone through the recovery mode, I just assume the recovery being different wasn't relevant.
https://www.youtube.com/watch?v=A0CrUvQVlJM&ab_channel=GSMPrime
https://www.youtube.com/watch?v=I7HUWCTSnrQ&ab_channel=GSMPrime
Teh_Chuz said:
I don't think so, I bought it through Amazon so is not attached to any carrier. I used to have a Moto e5 from Verizon and the Huawei are both blocked but I can use <fastboot devices> on those, not this one. I found it very weird. Any other idea? :c
Click to expand...
Click to collapse
There are carrier locked versions on Amazon and Amazon also has Amazon locked versions.
There are few different things that can be locked.
Sim locked means it's locked to certain sim cards and/or cell bands.
Motorola Software Channel can also be locked, the bootloader is usually locked if on certain software channels like Verizon, AT&T, Amazon...
Retail Channels are not usually locked like Retail, RetUS, RetAR, RetEU...
The Software Channel maybe listed in
Settings/about phone sometimes it's not.
The SKU/model # may help narrow it down but not always
Edit:
Usually when listed as unlocked, that refers to sim unlocked, and not the bootloader.
Sent from my ocean using XDA Labs
Did you fixed your issue ? In my case, it work in usb debugging mode for files transfer, fastboot work but adb devices don't see the phone at all.
Xt2005-5 so I didn't found any working TWRP so I can't add Magisk, Gapps and so on ...

OnePlus 8 Hard bricked MSM tool will not work.

Hey everybody, Just curious I recently bought a OnePlus 8 on eBay however when it arrived it was stuck in the bootloader. I tried to use the MSM tool which did finish however once it completed I was greeted with an error on the phone saying "your device is corrupted and cannot be trusted and will not boot" which then placed me back into the bootloader brick, After more digging I found that the bootloader must have not been unlocked beforehand meaning I CAN access fastboot but CANNOT enter any commands such as fastboot OEM unlock without errors.
I am kindly asking if their is a solution for this or am I screwed, thanks in advance.
Try to use a fastboot rom from @mauronofrio
https://forum.xda-developers.com/oneplus-8/how-to/rom-stock-fastboot-roms-oneplus-8-t4084629
It always helped me, when i got stuck.
lauchiebeans said:
Hey everybody, Just curious I recently bought a OnePlus 8 on eBay however when it arrived it was stuck in the bootloader. I tried to use the MSM tool which did finish however once it completed I was greeted with an error on the phone saying "your device is corrupted and cannot be trusted and will not boot" which then placed me back into the bootloader brick, After more digging I found that the bootloader must have not been unlocked beforehand meaning I CAN access fastboot but CANNOT enter any commands such as fastboot OEM unlock without errors.
I am kindly asking if their is a solution for this or am I screwed, thanks in advance.
Click to expand...
Click to collapse
Oneplus 8 stuck
Unfortunately that doesn't work because bootloader is locked and cannot flash anything via fastboot with out error.
lauchiebeans said:
Hey everybody, Just curious I recently bought a OnePlus 8 on eBay however when it arrived it was stuck in the bootloader. I tried to use the MSM tool which did finish however once it completed I was greeted with an error on the phone saying "your device is corrupted and cannot be trusted and will not boot" which then placed me back into the bootloader brick, After more digging I found that the bootloader must have not been unlocked beforehand meaning I CAN access fastboot but CANNOT enter any commands such as fastboot OEM unlock without errors.
I am kindly asking if their is a solution for this or am I screwed, thanks in advance.
Click to expand...
Click to collapse
Are you sure you're flashing the right msm for your variant? IN2015, 2011, 2017?
Oneplus 8 stuck
sx10 said:
Are you sure you're flashing the right msm for your variant? IN2015, 2011, 2017?
Click to expand...
Click to collapse
Yeah I am 100% sure, the process does complete at 300 seconds, could it be that my bootloader was locked previously?
Oneplus 8 stuck
sx10 said:
Are you sure you're flashing the right msm for your variant? IN2015, 2011, 2017?
Click to expand...
Click to collapse
Yeah, tried all tools, for reference my device is in2010.
Just stays in your device is corrupted and will not boot.
Same problems on my oneplus 8?
But I have black screen after displaying the logo
And bootloader is locked
Fastboot oem unlock not work
I tried many version of sms tool but none of them fix my problems
Please help me
ONEPLUS 8
oliver802 said:
Same problems on my oneplus 8
But I have black screen after displaying the logo
And bootloader is locked
Fastboot oem unlock not work
I tried many version of sms tool but none of them fix my problems
Please help me
Click to expand...
Click to collapse
Same boat here, Ive contacted oneplus and they will remote my PC I will update you when that happens.

Categories

Resources