Oreo update bricked my Shield TV 2017 16gb - Shield Android TV Q&A, Help & Troubleshooting

Okay guys I really need your help. So I recently installed the dev os 7.0 upgrade and I decided that I wanted to go back to 6.3. So, I managed to do it and I was at the setup. When I finished, I was forced to update to Oreo. The shield rebooted (since I didn't have much of a choice) and it rebooted me to twrp. I thought the update didn't install so I didn't think much of it.
I just rebooted the system. When I rebooted, it went to the Nvidia logo but then it went to a black screen. I turned off the shield and tried going into fastboot by using the hardware method (the controller and pressing a and b buttons) but it didn't work. It just rebooted the system. By the way, I connected the shield (while it was still on the black screen) to my computer and it shows up as an MTP usb device. But, I can't do any adb commands.
So I'm stuck with the black screen. I'm freaking out because I don't know if Nvidia would be willing to replace or fix it. It's still under warranty. But, I want to know if there is a way to fix the shield before resorting to that. I would really appreciate any help. Thank you!

almost the same issue with me.
device is stuck at android splash screen and am not able to go into fastboot
adb sees it as unauthorized device.
expensive paper weight we got

noobhero said:
almost the same issue with me.
device is stuck at android splash screen and am not able to go into fastboot
adb sees it as unauthorized device.
expensive paper weight we got
Click to expand...
Click to collapse
Almost same issue with me, got to nvidia logo and stuck.. so I rebooted and now its showing as APX device..
Pretty sure theres no way to recover from APX on a 16gb

device unauthorized
noobhero said:
almost the same issue with me.
device is stuck at android splash screen and am not able to go into fastboot
adb sees it as unauthorized device.
expensive paper weight we got
Click to expand...
Click to collapse
try these commands
adb kill-server
adb start-server
This authorized my device with similar issue
---------- Post added at 04:01 PM ---------- Previous post was at 03:59 PM ----------
markdb77 said:
try these commands
adb kill-server
adb start-server
This authorized my device with similar issue
Click to expand...
Click to collapse
Also, hold down A +B button while plugging in power to Shield.
This initiates FastBoot.

markdb77 said:
try these commands
adb kill-server
adb start-server
This authorized my device with similar issue
---------- Post added at 04:01 PM ---------- Previous post was at 03:59 PM ----------
Also, hold down A +B button while plugging in power to Shield.
This initiates FastBoot.
Click to expand...
Click to collapse
there is no way to authorize a device without booting into the UI.

noobhero said:
there is no way to authorize a device without booting into the UI.
Click to expand...
Click to collapse
Authorizing a device is only needed for ADB as far as I know, not fastboot.

blunden said:
Authorizing a device is only needed for ADB as far as I know, not fastboot.
Click to expand...
Click to collapse
he's asking me to
markdb77 said:
try these commands
adb kill-server
adb start-server
This authorized my device with similar issue
---------- Post added at 04:01 PM ---------- Previous post was at 03:59 PM ----------
Also, hold down A +B button while plugging in power to Shield.
This initiates FastBoot.
Click to expand...
Click to collapse

noobhero said:
he's asking me to
Click to expand...
Click to collapse
I was referring to the fastboot part.

blunden said:
Authorizing a device is only needed for ADB as far as I know, not fastboot.
Click to expand...
Click to collapse
i am not able to boot into fastboot as noted in my original post.
no matter, i've somewhat settle the issue

noobhero said:
i am not able to boot into fastboot as noted in my original post.
no matter, i've somewhat settle the issue
Click to expand...
Click to collapse
How you settled this issue?

Sunilmane said:
How you settled this issue?
Click to expand...
Click to collapse
Got myself a new set.

I'm still stuck with a brick 2 months later. Any easy instructions on how to get over this yet? Don't want to bin it. It's so much more powerful than my cheap LG TV's smarts.

duffmagic said:
I'm still stuck with a brick 2 months later. Any easy instructions on how to get over this yet? Don't want to bin it. It's so much more powerful than my cheap LG TV's smarts.
Click to expand...
Click to collapse
there's no way around it, at least not now. no bootloader = paper weight.

noobhero said:
Got myself a new set.
Click to expand...
Click to collapse
You can download the stock recovery rom, all instructions are found on Nvidia website.
HTTPS://developer.nvidia.com/gameworksdownload

dragonuk.test said:
You can download the stock recovery rom, all instructions are found on Nvidia website.
HTTPS://developer.nvidia.com/gameworksdownload
Click to expand...
Click to collapse
well if u followed those replies.. you'll notice that fastbooting is no longer an option. because the bootloader, i guess, is already corrupted..
nothing that we download will work.

Related

Bricked NEED HELP! xt905

After unsuccessful flashing phone (from 4.4.2 to 4.1.2) are not included in the boot is not included with the connection to the computer, the green LEDs and goes out, a visitor's computer does not see it.bootloader is unlocked
Can you access fastboot or recovery? If not, there's most probably no way to get it working.
Klen2 said:
Can you access fastboot or recovery? If not, there's most probably no way to get it working.
Click to expand...
Click to collapse
I can not get to the boot prompt. Through the factory cable, the phone tries to join, Windows making a sound device is connected and tighter turns off. And so it is constant. Help what to do?
If you can't access fastboot, there is currently no help
---------- Post added at 12:18 PM ---------- Previous post was at 12:17 PM ----------
Why was the flashing unsuccessful?
Are you able to press down while powering up, to get to fastboot?
victimssun said:
Are you able to press down while powering up, to get to fastboot?
Click to expand...
Click to collapse
Most likely I boot it killed not that he does not react. And there are topics on how to restore the boot?
VladimirP200KM said:
Most likely I boot it killed not that he does not react. And there are topics on how to restore the boot?
Click to expand...
Click to collapse
I'm not following, but I think what Klen2 was trying to say is that, just get it into fastboot and reflash. Did you try this, http://forum.xda-developers.com/showthread.php?t=2786016 ?
Without the battery the phone is defined as a HID device. What could be more?
VladimirP200KM said:
Without the battery the phone is defined as a HID device. What could be more?
Click to expand...
Click to collapse
my question is, new ideas?
As I said, no help. You can look here: http://forum.xda-developers.com/showthread.php?t=2533049
[Q] Hard bricked my XT907, any way to JTAG?

[Q] Bricked and gone?

Pretty sure I know the answer to this, but before I finally through in the towel or rather my Nexus 4 against the wall... I will defer to the resident experts. So, I attempt to install Liquid Smooth 4.0 and after going into TWRP I did a wipe and installed it. I was running the previous official build of Liquid Smooth. I also install gapps for Lollipop. Everything began to boot and then the phone said something to the like apps are starting and it stayed on that screen for a full 8 hours. I went back into recovery and tried to restore from my previous Liquid Smooth. Exact same thing happened. After several attempts I did the unmentionable. I did a full wipe. I know it was a dumb*ss move now. My phone does NOT connect to ANY PC. Every time the PC says device not recognized. Now I have now OS. Only TWRP. I tried sideload, but computer does not recognize device. I bought usb-otg adapter, but found out that usb-otg does not work with Nexus 4. So.... should I throw in the towel? My phone now a fancy paperweight?
Many thanks!
kjtay said:
Pretty sure I know the answer to this, but before I finally through in the towel or rather my Nexus 4 against the wall... I will defer to the resident experts. So, I attempt to install Liquid Smooth 4.0 and after going into TWRP I did a wipe and installed it. I was running the previous official build of Liquid Smooth. I also install gapps for Lollipop. Everything began to boot and then the phone said something to the like apps are starting and it stayed on that screen for a full 8 hours. I went back into recovery and tried to restore from my previous Liquid Smooth. Exact same thing happened. After several attempts I did the unmentionable. I did a full wipe. I know it was a dumb*ss move now. My phone does NOT connect to ANY PC. Every time the PC says device not recognized. Now I have now OS. Only TWRP. I tried sideload, but computer does not recognize device. I bought usb-otg adapter, but found out that usb-otg does not work with Nexus 4. So.... should I throw in the towel? My phone now a fancy paperweight?
Many thanks!
Click to expand...
Click to collapse
Under device manager, what is listed as your phone?
Ajxx16 said:
Under device manager, what is listed as your phone?
Click to expand...
Click to collapse
Unknown Device... It is worth noting that I have used Wugs Toolkit and followed every set of directions to a T. This includes a PC that that has never had my phone in it before. Followed all the steps before I even tried to connect. Also, both PC machine indicate that I have installed the most update driver.
I have zero experience with that toolkit, but have you tired every usb port on your computer and possibly another computer? Your phone is far from gone, this just sounds like a driver issue to me. Is your phone recognizable in bootloader?
I don't actually have this phone but my wife does, as well as my brother. Just the other night my wife's was showing up unrecognized, all I had to do was swap usb ports on the computer.
Ajxx16 said:
I have zero experience with that toolkit, but have you tired every usb port on your computer and possibly another computer? Your phone is far from gone, this just sounds like a driver issue to me. Is your phone recognizable in bootloader?
I don't actually have this phone but my wife does, as well as my brother. Just the other night my wife's was showing up unrecognized, all I had to do was swap usb ports on the computer.
Click to expand...
Click to collapse
I have tried all usb ports and a different usb cord. My OS is gone, so I was hoping to find some way to install a rom or stock. I am at a loss!
How about the bootloader? If you have that feature you can flash stock image
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
Volume down + power incase you didn't know.
Ajxx16 said:
How about the bootloader? If you have that feature you can flash stock image
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
Volume down + power incase you didn't know.
Click to expand...
Click to collapse
I do if I understand the term correctly. I am at the android "start" screen and underneath the android it says
Fastboot Mode
Product_Name - mako
lock state - unlocked
Now what?
Connect it to your computer, and I assume you have fastboot and adb set up correctly. In command prompt type fastboot devices and see if your phone is listed, should give the serial and say fastboot next to that
Not sure if I know how to set up adb correctly... as far as fastboot goes.. I assume that is set up correctly. Would adb work if the PC doesn't recognize my phone?
Well adb is of no use here so I wouldn't worry about it. Is fastboot recognized?
Ajxx16 said:
Well adb is of no use here so I wouldn't worry about it. Is fastboot recognized?
Click to expand...
Click to collapse
Don't mean to sound like an idiot (may be too late for that), but do you mean fastboot recognized on my PC when I plug in my phone? Or does is say fastboot on my phone? PC does not recognize my phone, but it does say fastboot enabled on my phone.
Alright so follow these instructions.
http://forum.xda-developers.com/showthread.php?t=2317790
Get that set up and in the mean time download either the 4.4.4 or 5.0 image here.
https://developers.google.com/android/nexus/images
Once you finish the adb fastboot setup, while your phone is in the boot loader screen you should be able to type into a command prompt "fastboot devices" and your device should be listed.
Ajxx16 said:
Alright so follow these instructions.
http://forum.xda-developers.com/showthread.php?t=2317790
Get that set up and in the mean time download either the 4.4.4 or 5.0 image here.
https://developers.google.com/android/nexus/images
Once you finish the adb fastboot setup, while your phone is in the boot loader screen you should be able to type into a command prompt "fastboot devices" and your device should be listed.
Click to expand...
Click to collapse
I can't get the PC to recognize the phone. The phone is in fastboot mode. It is looking mighty grim!
I'm fairly certain this is just a simple fix on the drivers on your computer, you have access to recovery and boot loader, your phone is far from gone. I'm out atm so I'll check in with ya a little later.
Ajxx16 said:
I'm fairly certain this is just a simple fix on the drivers on your computer, you have access to recovery and boot loader, your phone is far from gone. I'm out atm so I'll check in with ya a little later.
Click to expand...
Click to collapse
An easy fix, do you have a nandroid backup? Just restore it in twrp. As mentioned, you're far from bricked and sol. If you can get into the bootloader it's recoverable.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
An easy fix, do you have a nandroid backup? Just restore it in twrp. As mentioned, you're far from bricked and sol. If you can get into the bootloader it's recoverable.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Would you happen to have a link for an ADB driver he could install? Not sure of the n4 requires something specific.
Ajxx16 said:
Would you happen to have a link for an ADB driver he could install? Not sure of the n4 requires something specific.
Click to expand...
Click to collapse
I'd Google 15 second adb install xda. That'll set yo adb and fastboot on the pc and includes drivers
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I'd Google 15 second adb install xda. That'll set yo adb and fastboot on the pc and includes drivers
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Installed 15 second adb and still nothing recognized on my PC. Still have "fastboot mode" in red on my phone???
kjtay said:
Installed 15 second adb and still nothing recognized on my PC. Still have "fastboot mode" in red on my phone???
Click to expand...
Click to collapse
Open up device manager, look for the phone, right click and hit update driver, then hit let !e choose driver, then select from list, you shpuld see something along the lines of ADB interface. Select that and install and try fastboot devices in command prompt again.
Ajxx16 said:
Open up device manager, look for the phone, right click and hit update driver, then hit let !e choose driver, then select from list, you shpuld see something along the lines of ADB interface. Select that and install and try fastboot devices in command prompt again.
Click to expand...
Click to collapse
I am pretty certain I have the proper drivers installed on 3 computers. Not a single one recognizes the device. I suppose it is possible that it is a hardware issue? If I can figure a way to the computer to recognize the phone I am certain I can save it. Right NOTHING has worked.

where the hell is the fastboot screem for h910

I started the dirty Santa unlock. Its not even getting past the first step because it isn't seeing my bootloader screen. Am I missing something?
Fastboot and ADB drivers installed? Windows or Linux?
Edit: if you aren't familiar with this stuff I advise against it. It's more complicated than the typical root process is.
Caveat Emptor.
elijah420 said:
Fastboot and ADB drivers installed? Windows or Linux?
Edit: if you aren't familiar with this stuff I advise against it. It's more complicated than the typical root process is.
Caveat Emptor.
Click to expand...
Click to collapse
I'm sorry, I was referring to the bootloader screen on the phone, not my pc. Drivers are installed and all is good on that end, but for some reason it wont go to the bootloader screen.
cwis said:
I'm sorry, I was referring to the bootloader screen on the phone, not my pc. Drivers are installed and all is good on that end, but for some reason it wont go to the bootloader screen.
Click to expand...
Click to collapse
Understood. Was asking what OS you run, as to tell you what to download if needed for drivers.
When you have a command prompt\terminal open what does 'adb devices' show?
---------- Post added at 02:52 AM ---------- Previous post was at 02:50 AM ----------
As well, after 'adb devices'
'Adb reboot bootloader'
Try installing 'flashify' from play store.
Is your phone e already rooted?

[HELP] Bricked but fastboot kind of working.

Hey guys, need some help here. I have M1 pro European version and just kind of bricked it:
-The screen stays black, I think system is booting because I can hear unlock click if I press the power button. Also notification led indicates charging when connected.
-in fastboot mode the screen is black too, but fastboot sees the device, though the name is different than before the brick.
-In recovery all I can see is black screen.
Now, here's how this happened:
-I got the phone, updated firmware to 323
-Unlocked successfuly with unofficial unlock
-Tried installing TWRP to no avail - The process seemed to go through fine, but no TWRP, just stock Asus recovery. Tried multiple times, tried rebooting straight to recovery from fastboot, tried on different computers. Weird thing I noticed was that write time in fastboot during the process was like 0.001s, which led me to believe it thought it was writing TWRP, but really wasn't for some reason.
-Then I decided to flash fastboot firmware using this guide: https://forum.xda-developers.com/as...ow-to/guide-revert-to-stock-rom-lock-t3798420
-It started flashing, but during the process I noticed again that all the write times
were super low like 0.001s, which made me expect the worst, and well, here I am now.
It's the first time I have so many problems with rooting a phone. Any help is greatly appreciated, I hope I can fix this considering it kinda works in fastboot mode.
Thanks in advance and have a great day.
Not really an expert but there are problems flashing this phone via usb 3.0 port. If you are using one try a usb 2.0 one.
gr8guzzler said:
Not really an expert but there are problems flashing this phone via usb 3.0 port. If you are using one try a usb 2.0 one.
Click to expand...
Click to collapse
Thanks, but I tried both usb 2 and 3 and both yield same results for me.
gr8guzzler said:
Not really an expert but there are problems flashing this phone via usb 3.0 port. If you are using one try a usb 2.0 one.
Click to expand...
Click to collapse
Thanks, but I tried both usb 2 and 3 and both yield same results for me.
Not sure whether this will work (it does in some cases), try full ADB instead of minimal ADB + ASUS drivers installed from the website.
By what name does the fastboot see the device?
Hye, did you solve the problem?
Don't worry, it’s only soft bricked. All you need to do is to flash a stock service rom. Something like: WW_ZB602KL_15.2016.1805.318_20180712 or WW_ZB601KL(ZB602KL)-15.2016.1805.311-20180623. The reason it is "bricked" is because you flashed the incorrect rom for your device, actual model is important, M1 has many variants.
Try flash stock recovery through fastboot, relock ur device, then place whatever version of stock rom into microsd,
And last flash it via stock recovery
Hi sorry but how can i flash it through fastboot? I have same problem...
kothy said:
Hi sorry but how can i flash it through fastboot? I have same problem...
Click to expand...
Click to collapse
Flash stock recovery? Enter fastboot, connect Ur device to PC
Open cmd command in folder where U place the recovery.img file. Then, type "fastboot devices" to make sure Ur device detected
Then type "fastboot flash recovery (filename)"
Done
If you can see your device name when typing 'fastboot devices' you can do as said above. Could it be dead screen?
RAMBO29 said:
If you can see your device name when typing 'fastboot devices' you can do as said above. Could it be dead screen?
Click to expand...
Click to collapse
Yep, if it shows 'blablabla device' It could be dead screen
Then you can go to next step
Its not a dead screen. You just have a wrong rom/kernal/drives/firmware etc. Its a software issue.
Vico100 said:
Its not a dead screen. You just have a wrong rom/kernal/drives/firmware etc. Its a software issue.
Click to expand...
Click to collapse
i am facing the same issue but cant gent into stock recovery and cant enable usb debugging as well
any solutions.
Get into fastboot. Hold volume up and power. Even if you don't see the screen it should still go into fastboot. Check device manager on windows to see if any devices appear. The phone should vibrate when you turn it on and go into fastboot.
Vico100 said:
Get into fastboot. Hold volume up and power. Even if you don't see the screen it should still go into fastboot. Check device manager on windows to see if any devices appear. The phone should vibrate when you turn it on and go into fastboot.
Click to expand...
Click to collapse
i did that works but screen is blank or dead after flashing fastboot rom
What is your phone model and what rom did you flash?
tried this it did not work
https://forum.xda-developers.com/as...ow-to/guide-revert-to-stock-rom-lock-t3798420
---------- Post added at 10:36 PM ---------- Previous post was at 10:20 PM ----------
can you please help me... i have ZB601KL model... can do fast boot i do not know what to do next.... im stuck on the black screen... i can hear the phone booting up and starting up but its just black screen blinking... please help
---------- Post added at 10:39 PM ---------- Previous post was at 10:36 PM ----------
ASUS_X00TDB is the name of the phone when it boots up
same problem with my device. share if you find any solution.
------------------------------------------------------------------------------
fixed my device following this

trouble with unlocking my bootloader

hey guys,
i just got my 8 pro in the mail, and need to unlock my bootloader. i turned on usb debugging, installed the usb drivers on my pc, and the platform tools.
i pulled up this guide to help: https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-unlocking-bootloader-rooting-t4151823
this is indeed an EU model
im able to run .\ adb devices, and see my device
then, after running .\ adb reboot boatloader, i reach a screen where i am given three language options, and my device shows up under .\fastboot devices
after running .\fastboot unlock oem, i get this message
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
PS C:\Users\FPSReach\Downloads\platform-tools_r30.0.5-windows\platform-tools>
does anyone have any idea what i can do?
sorry if this has been covered before, i did some light searching but really couldnt understand much
FPSReach said:
hey guys,
i just got my 8 pro in the mail, and need to unlock my bootloader. i turned on usb debugging, installed the usb drivers on my pc, and the platform tools.
i pulled up this guide to help: https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-unlocking-bootloader-rooting-t4151823
this is indeed an EU model
im able to run .\ adb devices, and see my device
then, after running .\ adb reboot boatloader, i reach a screen where i am given three language options, and my device shows up under .\fastboot devices
after running .\fastboot unlock oem, i get this message
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
PS C:\Users\FPSReach\Downloads\platform-tools_r30.0.5-windows\platform-tools>
does anyone have any idea what i can do?
sorry if this has been covered before, i did some light searching but really couldnt understand much
Click to expand...
Click to collapse
Shouldn't it be "fastboot oem unlock"?
Yes, that's correct "fastboot oem unlock"
Just follow my guide bud
https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-unlocking-bootloader-rooting-t4151823
Easy step by step
Kollachi said:
Shouldn't it be "fastboot oem unlock"?
Click to expand...
Click to collapse
Yes, my bad, i typed it wrong on here
Just to make sure, i gave it another go right now and got the same " Unable to open fastboot HAL" message
dladz said:
Just follow my guide bud
https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-unlocking-bootloader-rooting-t4151823
Easy step by step
Click to expand...
Click to collapse
Hi sir
You guide is actually the one i found for this
After performing step 3, and reaching the screen with a green START above it, my device no longer responds to fastboot commands, and does not show up after i enter .\fastboot devices (i do still see "fastboot mode" in red text though, weirdly enough)
The only time that my device shows up after entering .\fastboot devices is at the start of step 3, on the language selection screen
What do i do to fix this?
FPSReach said:
Hi sir
You guide is actually the one i found for this
After performing step 3, and reaching the screen with a green START above it, my device no longer responds to fastboot commands, and does not show up after i enter .\fastboot devices (i do still see "fastboot mode" in red text though, weirdly enough)
The only time that my device shows up after entering .\fastboot devices is at the start of step 3, on the language selection screen
What do i do to fix this?
Click to expand...
Click to collapse
? Never had that issue myself. The steps are taken from verified sources and I ran through it myself when I unlocked mine, no one else has said this.
Potentially a driver issue, you using Windows 10 ? Usb 2 or 3? Sometimes people have issues with 3, 2 seems to work for them..
It's been a while since I was on that screen...but the process should be as written.
See if fastboot mode is an option in the start screen (after you've used the ADB reboot bootloader command)
dladz said:
? Never had that issue myself. The steps are taken from verified sources and I ran through it myself when I unlocked mine, no one else has said this.
Potentially a driver issue, you using Windows 10 ? Usb 2 or 3? Sometimes people have issues with 3, 2 seems to work for them..
It's been a while since I was on that screen...but the process should be as written.
See if fastboot mode is an option in the start screen (after you've used the ADB reboot bootloader command)
Click to expand...
Click to collapse
I am on windows 10 and downloaded the usb drivers for the 8 pro beforehand. I just tried again with a usb 2 port, the results are the same.
After using the .\adb reboot bootloader command, my phone screen says "fastboot mode" with the green "start" on top (i just took a pic, to confirm, this is my screen https://imgur.com/tduDZsz ) but at this stage my phone is no longer detected and does not show up under .\fastboot devices or .\adb devices
just for funsies, i downloaded an third party app on my pc called reiboot to get me into fastboot mode
again, it got my phone to this same screen and then said it "failed to enter fastboot" and could no longer detect my phone
this is a brand new model too, a european one, i made this thread within a couple hours of it coming
dladz said:
? Never had that issue myself. The steps are taken from verified sources and I ran through it myself when I unlocked mine, no one else has said this.
Potentially a driver issue, you using Windows 10 ? Usb 2 or 3? Sometimes people have issues with 3, 2 seems to work for them..
It's been a while since I was on that screen...but the process should be as written.
See if fastboot mode is an option in the start screen (after you've used the ADB reboot bootloader command)
Click to expand...
Click to collapse
....oh my god.
I am so sorry, the mistake was on my end.
I followed the instructions meticulously, don't get me wrong.
In a last ditch attempt though, I repeated the process on my old windows 7 laptop with a command prompt
It worked. Im sorry to have disturbed you over this.
If anyone else ever finds this thread while looking for answers, use another computer, i should have tried that earlier.
FPSReach said:
....oh my god.
I am so sorry, the mistake was on my end.
I followed the instructions meticulously, don't get me wrong.
In a last ditch attempt though, I repeated the process on my old windows 7 laptop with a command prompt
It worked. Im sorry to have disturbed you over this.
If anyone else ever finds this thread while looking for answers, use another computer, i should have tried that earlier.
Click to expand...
Click to collapse
So it was a driver issue. Because I did it with Win10 and USB 3.
Kollachi said:
So it was a driver issue. Because I did it with Win10 and USB 3.
Click to expand...
Click to collapse
It probably was, i have no idea what else it could be, honestly
FPSReach said:
....oh my god.
I am so sorry, the mistake was on my end.
I followed the instructions meticulously, don't get me wrong.
In a last ditch attempt though, I repeated the process on my old windows 7 laptop with a command prompt
It worked. Im sorry to have disturbed you over this.
If anyone else ever finds this thread while looking for answers, use another computer, i should have tried that earlier.
Click to expand...
Click to collapse
Yep windows 7 has caused issues in the past, shame really as it's still got it's uses as an OS.
Glad you're sorted.
---------- Post added at 05:46 PM ---------- Previous post was at 05:45 PM ----------
Kollachi said:
So it was a driver issue. Because I did it with Win10 and USB 3.
Click to expand...
Click to collapse
That's correct as 7 chooses the wrong one. Don't think the 10 driver would work.
Haven't looked into it.
dladz said:
Yep windows 7 has caused issues in the past, shame really as it's still got it's uses as an OS.
Glad you're sorted.
---------- Post added at 05:46 PM ---------- Previous post was at 05:45 PM ----------
That's correct as 7 chooses the wrong one. Don't think the 10 driver would work.
Haven't looked into it.
Click to expand...
Click to collapse
Driver issue is sometimes hard to figure out.

Categories

Resources