Related
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.
Not working anymore.
Sorry.
Do you mean that you had your old tablet already killed, and then you recovered it following these steps?
You can see it here, in my Twitter
https://twitter.com/victorcangil16/status/642389331768942592
Can anyone confirm this on a separate dead tablet? if so its a pretty damn good find.
Hi Victorcangil 16,
Could you exactly discribe how did you make this miracle (which drivers...) ?
Thanks
jo2e said:
Hi Victorcangil 16,
Could you exactly discribe how did you make this miracle (which drivers...) ?
Thanks
Click to expand...
Click to collapse
I used Windows 10 with the NVIDIA Family USB Drivers. I made the process I described in the first post
Victorcangil 16 said:
I used Windows 10 with the NVIDIA Family USB Drivers. I made the process I described in the first post
Click to expand...
Click to collapse
Ok,
Thx for your reply Victorcangil 16.
But how did your device was recognized by windows before done this process ? APX or something else
It was reconized as normal device by Windows, like if I plug my phone to the PC. And the drivers I had to configure them manually, if not, It gives me error when doing FastBoot
Victorcangil 16 said:
It was reconized as normal device by Windows, like if I plug my phone to the PC. And the drivers I had to configure them manually, if not, It gives me error when doing FastBoot
Click to expand...
Click to collapse
It stay on :"<waiting for device>"
And my tablet is not reconized as normal device but as "APX"
What does APX mean?
Change the ADB drivers interface using the next process:
Search in Windows: Device Manager
If the ADB interface has a Yellow alert, Right Click, Update Drivers, Select from Computer, Use Disk, Use all, and then select the file in the NVIDIA Drivers folder (in my case, Downloads). Accept,
Victorcangil 16 said:
What does APX mean?
Click to expand...
Click to collapse
I don't known. My tablet appears like that in the peripherics manager ...
If you hace skype, I can help you easily
Victorcangil 16 said:
If you hace skype, I can help you easily
Click to expand...
Click to collapse
Yes i have skype.
But i think i got the problem : my tablet wasn't rooted and the bootloader was locked...
I think you saved your shield because it was rooted...
I thinks is that. If is has not unlocked bootloader, you can't change nothing. But to unlock it, just type in Fastboot: "fastboot oem unlock" (tablet will Factory Reset)
Victorcangil 16 said:
I thinks is that. If is has not unlocked bootloader, you can't change nothing. But to unlock it, just type in Fastboot: "fastboot oem unlock" (tablet will Factory Reset)
Click to expand...
Click to collapse
Same thing with this command : <waiting for device>
:/ I think something is going on with Drivers
Hi, one question for such kind of reactivation - root is required ?
Yes, Root and Unlocked Bootloader are required ro recover the "killed" Tablet
Just bought by mistake deactivated Shield...is it possible to make root via fastboot ?
I've tried several times to unlock the bootloader and it will not respond to any commands once in fastboot mode. I've tried to follow this guide https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ but whenever I type "fastboot oem unlock" it just says "waiting for any device" and nothing happens. I have usb debugging enabled and oem unlocking on so I don't know what I'm doing wrong. I have the platform tools from Google installed. I can run adb and type "adb reboot bootloader" and it responds, but after that, no fastboot commands work. I mainly just wanted to root so I could restore my apps and data via Titanium Backup. Is there a temp root solution I can use? Or has anyone else experienced this?
Let me know if you need more info. Hopefully this is an easy one.
What do you get if you run "adb devices"?
thedrizzle said:
What do you get if you run "adb devices"?
Click to expand...
Click to collapse
ADB: USAGE: unknown command DEVICES
Or do you mean run it while it's in fastboot?
I feel like it's something simple I'm missing. I've never had trouble figuring this stuff out. I've been rocking an HTC M8 on VenomRom since forever ago so it was time for an upgrade. I've looked at several different guides, but some of them seem to be incomplete. Like the guide at the official TWRP page says to power off the phone. Then it says to hold volume up to go into fastboot mode. I tried following those instructions to a T, but that didn't actually do anything. It doesn't say where to put the twrp.img file, it just says to run the command to boot the .img. Getting into fastboot isn't a problem. It's that no matter what I do once it's in fastboot, I just get "waiting for any device". I've tried the OnePlus6t Manager because I thought maybe I needed a one-click method. But again, it gets to fastboot and goes nowhere from there.
blockhead428 said:
I feel like it's something simple I'm missing. I've never had trouble figuring this stuff out. I've been rocking an HTC M8 on VenomRom since forever ago so it was time for an upgrade. I've looked at several different guides, but some of them seem to be incomplete. Like the guide at the official TWRP page says to power off the phone. Then it says to hold volume up to go into fastboot mode. I tried following those instructions to a T, but that didn't actually do anything. It doesn't say where to put the twrp.img file, it just says to run the command to boot the .img. Getting into fastboot isn't a problem. It's that no matter what I do once it's in fastboot, I just get "waiting for any device". I've tried the OnePlus6t Manager because I thought maybe I needed a one-click method. But again, it gets to fastboot and goes nowhere from there.
Click to expand...
Click to collapse
Do not forget to enable OEM Unlocking in Developer options
Sent from my ONEPLUS A6013 using Tapatalk
Just my 2 cents I'm not an expert but it Might be your drivers or when you installed adb did you do it with administrator rights? The first time tried I couldn't get it to work it wasn't detecting the device in fastboot so I reinstalled adb and then it worked
I just rooted mines today but I went off a YouTube video I looked up and they had everything you needed to download in the description. Took about ten minutes ? I'm not sure if I can put a link on here
DinarQ8 said:
Do not forget to enable OEM Unlocking in Developer options
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I've done that also. Developer options are enabled, USB debugging, and OEM unlocking. Are there newer drivers I need? But if that was an issue, it wouldn't allow me to do "adb reboot bootloader". It'll reboot to fastboot mode, but after typing "fastboot oem unlock" it just says waiting for any device.
blockhead428 said:
ADB: USAGE: unknown command DEVICES
Or do you mean run it while it's in fastboot?
Click to expand...
Click to collapse
In the picture it shows you typed your commands all capitals letters
Dr8ven said:
Just my 2 cents I'm not an expert but it Might be your drivers or when you installed adb did you do it with administrator rights? The first time tried I couldn't get it to work it wasn't detecting the device in fastboot so I reinstalled adb and then it worked
I just rooted mines today but I went off a YouTube video I looked up and they had everything you needed to download in the description. Took about ten minutes I'm not sure if I can put a link on here
Click to expand...
Click to collapse
Try and post it. It let me post the link to the guide in the initial posting. You could be on to something.
This is where I got my version of ADB. https://developer.android.com/studio/releases/platform-tools It's not so much an "install" as it is unpacking a zip archive.
twinnfamous said:
In the picture it shows you typed your commands all capitals letters
Click to expand...
Click to collapse
I did not know it was case-sensitive. I just tried again and it seems to show my devices (I'm transferring files off of my m8 which is why it shows two).
Good call, brother! Where do I go from here?
blockhead428 said:
I did not know it was case-sensitive. I just tried again and it seems to show my devices (I'm transferring files off of my m8 which is why it shows two).
Good call, brother! Where do I go from here?
Click to expand...
Click to collapse
you need to be careful in fastboot. One wrong command can lead to a catastrophe.
I used the adb installer from the same video. Once you unzip it. It's an .exe file which I granted administrator rights to install... it installs adb and drivers and it worked for me
That's the video and did it to a T
Another thing don't use power shell use command
twinnfamous said:
you need to be careful in fastboot. One wrong command can lead to a catastrophe.
Click to expand...
Click to collapse
I'm following a video now. I'm thinking I didn't have the ADB drivers installed so I'm trying that now.
Let us know how it turned out ?
Dr8ven said:
Let us know how it turned out
Click to expand...
Click to collapse
Still getting nowhere. I thought my problem was that I didn't intall the drivers as administrator. So I did it again, following this video https://www.youtube.com/watch?v=B-XZy27wy5o When I reboot into bootloader, I type "fastboot devices" and it just goes right back to the command prompt. Nothing happens. I guess I'm going to try the old fashioned computer restart and see what happens. If all else fails, I can unplug it from the wall and blow on it, lol.
I swear, I've never been this simple before.
blockhead428 said:
Still getting nowhere. I thought my problem was that I didn't intall the drivers as administrator. So I did it again, following this video https://www.youtube.com/watch?v=B-XZy27wy5o When I reboot into bootloader, I type "fastboot devices" and it just goes right back to the command prompt. Nothing happens. I guess I'm going to try the old fashioned computer restart and see what happens. If all else fails, I can unplug it from the wall and blow on it, lol.
I swear, I've never been this simple before.
Click to expand...
Click to collapse
::sigh:: Still no joy. Restarted pc, ran adb devices and it showed my phone. So i reboot into bootloader, typed fastboot devices and it still took me right back to the command prompt.
blockhead428 said:
::sigh:: Still no joy. Restarted pc, ran adb devices and it showed my phone. So i reboot into bootloader, typed fastboot devices and it still took me right back to the command prompt.
Click to expand...
Click to collapse
I was thinking that maybe the latest OTA broke the bootloader unlock process, but someone else in this thread said they just unlocked theirs. I don't understand what the issues is. I've followed this video so closely I could re-enact it in my sleep.
Got it! I had two sets of drivers installed so I uninstalled both and it finally recognized my phone in fastboot. My old drivers from my m8 from 2014 were probably interfering with it. I knew it was something simple. I feel like Carl in Sling Blade when they bring him the lawn mower engine and he says "ain't got no gas in it, mmhmmm".
Nice! For a noob I wasn't too far off lol it just had to be one of those two issues
Enjoy happy rooting ?
blockhead428 said:
Got it! I had two sets of drivers installed so I uninstalled both and it finally recognized my phone in fastboot. My old drivers from my m8 from 2014 were probably interfering with it. I knew it was something simple. I feel like Carl in Sling Blade when they bring him the lawn mower engine and he says "ain't got no gas in it, mmhmmm".
Click to expand...
Click to collapse
Hi I have the same problem, when fastboot it says waiting device. I also had rooted my other phone, so how to find my other driver phone in device manager because I can't find it
Guys whenever i try to flash the recovery using fastboot command it returns the error mentioned in the photo attached i am on the latest firmware 061
SoorajN7 said:
Guys whenever i try to flash the recovery using fastboot command it returns the error mentioned in the photo attached i am on the latest firmware 061
Click to expand...
Click to collapse
Have you unlocked the bootloader before flashing?
Yeah I did
SoorajN7 said:
Yeah I did
Click to expand...
Click to collapse
1) Use latest platform tools and run adb devices command before flashing to check device status.
2) Use Windows + Intel with USB 2.0
Tianhe said:
1) Use latest platform tools and run adb devices command before flashing to check device status.
2) Use Windows + Intel with USB 2.0
Click to expand...
Click to collapse
The latter one is not being fulfilled and causes issues to many, including me. Has anyone messaged this to Asus Team?
Invincible-Venom said:
The second latter is the one not being fulfilled and causes issues to many, including me. Has anyone messaged this to Asus Team?
Click to expand...
Click to collapse
Windows + USB 2.0 ? AMD Ryzen has documented fastboot problems (not Athlon), so nothing much Asus can do. And I can use fastboot on USB 3.0 (on Windows) so this is a variable problem.
Tianhe said:
Windows + USB 2.0 ? AMD Ryzen has documented fastboot problems (not Athlon), so nothing much Asus can do. And I can use fastboot on USB 3.0 (on Windows) so this is a variable problem.
Click to expand...
Click to collapse
AMD confirmed problems only on Ryzen 2nd gen chipsets. Yeah it's true, Asus can't do anything into this matter.
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.