Related
I've search using windows "64-bit" root froyo and no search results return.
tried following the thread - [Guide] The 100% Fool Proof Guide: STOCK N1 to ROOT to SENSE UI/CM (Android 2.1)!
but at the part where it should say fastboot, no matter what i try it shows fastboot usb. and then the following steps fail.
milomak said:
I've search using windows "64-bit" root froyo and no search results return.
tried following the thread - [Guide] The 100% Fool Proof Guide: STOCK N1 to ROOT to SENSE UI/CM (Android 2.1)!
but at the part where it should say fastboot, no matter what i try it shows fastboot usb. and then the following steps fail.
Click to expand...
Click to collapse
I followed that guide to the letter to root my N1 while running Windows 7 x64. Make sure to use the PDANet drivers (as mentioned in that tutorial): http://www.junefabrics.com/android/download.php
milomak said:
but at the part where it should say fastboot, no matter what i try it shows fastboot usb. and then the following steps fail.
Click to expand...
Click to collapse
That makes no sense.
What part should say fastboot? Where are you typing fastboot, and where are you seeing "fastboot usb".
Be more detailed so we can help you.
codesplice said:
I followed that guide to the letter to root my N1 while running Windows 7 x64. Make sure to use the PDANet drivers (as mentioned in that tutorial):
Click to expand...
Click to collapse
i think this was where things went wrong. i am used to linux so didn't reboot after installing the pda drivers. i think it was the reboot that has got me through.
milomak said:
i think this was where things went wrong. i am used to linux so didn't reboot after installing the pda drivers. i think it was the reboot that has got me through.
Click to expand...
Click to collapse
Cool, so you got it working? Awesome
my htc one was previously on a 4.3 rom. I formatted data to go back to 4.1.2. Normally this is no problem as i just sideload a rom using adb. However now when I try to use the adb sideload command or any command it just brings up a list of adb commands. I updated sdk and made sure i installed all 4.1-4.3 apis. What can i do now? adb devices command does show the device connected and in sideload. Is this a problem on the phone end? Please any help would be appreciated, freaking out right now!!
Are you running your commands from you android-sdk/platform-tools folder?
When you say you get a list of adb commands it seems you are not issuing the commands from the proper folder.
and ccesbt
bigdaddy619 said:
Are you running your commands from you android-sdk/platform-tools folder?
When you say you get a list of adb commands it seems you are not issuing the commands from the proper folder.
Click to expand...
Click to collapse
Yes i am issuing them from the platform-tools folder. Its worth mentioning I have literally done this a hundred times before. Fortunately I was able to put a rom.zip on a usb drive and use USB OTG to flash it. I still would like to know what is going on with my adb though. Do you think it could be a problem with the recovery? I am using TWRP and i believe it might be one version old, but it did work before so i really dont know. Going to try a new recovery and see. Thanks for the reply.
hituinthedome said:
Yes i am issuing them from the platform-tools folder. Its worth mentioning I have literally done this a hundred times before. Fortunately I was able to put a rom.zip on a usb drive and use USB OTG to flash it. I still would like to know what is going on with my adb though. Do you think it could be a problem with the recovery? I am using TWRP and i believe it might be one version old, but it did work before so i really dont know. Going to try a new recovery and see. Thanks for the reply.
Click to expand...
Click to collapse
I'm using TWRP 2.5.0.0 and don't have any problems sideloading or pushing files to my device I know there is a different file structure for 4.2.2 and 4.3 roms that could be the problem the path you are trying to use is wrong just a thought not 100% sure though
So apparently it seems to be a driver problem. My computer stopped recognizing the device when it went into recovery. Fastboot works and I was able to use fastboot commands, so it was just recovery. I tired using multiple types of recoveries as well and i still nothing. ADB devices resulted in nothing showing up and any adb command resulted in a list of commands showing. So if you are having this problem try reinstalling drivers for HTC and ADB. I had to use a whole other computer all together because i think sometimes drivers do not work correctly on windows 8. Everything worked perfectly on my windows vista pc.
I have helped a few folks with Win8 rescue their phones in the past couple weeks so I can confirm it will work on Win8
bigdaddy619 said:
I have helped a few folks with Win8 rescue their phones in the past couple weeks so I can confirm it will work on Win8
Click to expand...
Click to collapse
I know it will work because it did before for me too. I am just saying sometimes dealing with windows 8 can be tricky.
I am grateful for people like you who come to the aid of less proficient folk such as myself. Thanks for your help and input!
hituinthedome said:
I know it will work because it did before for me too. I am just saying sometimes dealing with windows 8 can be tricky.
I am grateful for people like you who come to the aid of less proficient folk such as myself. Thanks for your help and input!
Click to expand...
Click to collapse
NP
Reason For Edit: Already Answered, Tapatalk Didnt Want To Load Responses So Didn't See It Was Already Answered
It started here:
http://forum.xda-developers.com/showthread.php?t=2530605
I followed this post.
http://forum.xda-developers.com/showthread.php?t=2509676
Got nowhere because of the puttytel window timeout problem.
Related to this post was this post:
http://forum.xda-developers.com/showthread.php?p=47749358#post47749358
I have an unlocked bootloader on Moto X from sprint. I just need the easiest way to root.
This looked confusing. http://forum.xda-developers.com/showthread.php?t=2536200. Gotta be another way.
Have considered restoring to stock and taking the dang thing back http://atsgadgets.com/how-to-restor...lite-att-t-mobile-sprint-verizon-us-cellular/. So frustrated.
I've offered paypal to those who can do it successfully. I am so burnt out on trying to make this work. This PITA is not worth android. I have a one click jailbroken phone now. And I have successfully rooted and installed custom roms before but this is totally out of hand how complex this is for me. Maybe I'm just remedial but it seems several are having trouble with this model. For open source, this should not be this tough.
/rant. Almost ready to throw in the towel, but still listening.....
Sorry for the multiple posts. Just trying to get some new opinions. HTC Evo 4 g was done in 10 minutes. This has taken 4 days.
:crying:
bullpen7979 said:
I have an unlocked bootloader on Moto X from sprint. I just need the easiest way to root.
This looked confusing. http://forum.xda-developers.com/showthread.php?t=2536200. Gotta be another way.
Have considered restoring to stock and taking the dang thing back http://atsgadgets.com/how-to-restor...lite-att-t-mobile-sprint-verizon-us-cellular/. So frustrated.
I've offered paypal to those who can do it successfully. I am so burnt out on trying to make this work. This PITA is not worth android. I have a one click jailbroken phone now. And I have successfully rooted and installed custom roms before but this is totally out of hand how complex this is for me. Maybe I'm just remedial but it seems several are having trouble with this model. For open source, this should not be this tough.
/rant. Almost ready to throw in the towel, but still listening.....
Sorry for the multiple posts. Just trying to get some new opinions. HTC Evo 4 g was done in 10 minutes. This has taken 4 days.
:crying:
Click to expand...
Click to collapse
Are you on 4.4 and what computer OS are you using?
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
bullpen7979 said:
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
Click to expand...
Click to collapse
Here, go into Settings -> About Phone and tell me what your Build Number is (at the very bottom).
Do not put in the cmd window mfastboot, just try fastboot flash recovery twrp 2.6.3.1-ghost-4.4.img. Now also put the recovery image in the same folder as fast boot, I believe its SDK tools folder
Sent on my Moto X
bullpen7979 said:
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
Click to expand...
Click to collapse
The method that you thought was confusing, is the one you should use. If I have time, I could try helping you with it.
ALU0506, the build number is 13.9.0Q2.X-116-MX-17-57-1. Thanks everyone for your help.
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
bullpen7979 said:
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
Click to expand...
Click to collapse
I can try helping over gtalk.
bullpen7979 said:
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
Click to expand...
Click to collapse
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
I will try that as soon as I can and get back to you. I have two computers one at my hotel and one here. I'm not sure I have the ADB tools on my netbook
Sent from my XT1056 using xda app-developers app
bullpen7979 said:
I will try that as soon as I can and get back to you. I have two computers one at my hotel and one here. I'm not sure I have the ADB tools on my netbook
Sent from my XT1056 using xda app-developers app
Click to expand...
Click to collapse
if you are still looking for help i can help you get this done on gtalk as well. send me a pm with your username. it will take virtually no time at all
jayboyyyy said:
if you are still looking for help i can help you get this done on gtalk as well. send me a pm with your username. it will take virtually no time at all
Click to expand...
Click to collapse
especially since he already unlocked the bootloader. Just flash recovery, then flash supersu.zip.
aooga said:
especially since he already unlocked the bootloader. Just flash recovery, then flash supersu.zip.
Click to expand...
Click to collapse
ya during his four days of misery, he could have just read for 1 hour on the stuff so it would seem confusing anymore and then he would have had a rooted phone. But either way, his problem is solvable with a few simple instructions.
OK Jay/Aooga.
Finally back from work.
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
open cmd window, typed adb reboot bootloader, and got:
T063202TFL and fastboot, and then a prompt.
OK Jay/Aooga.
Finally back from work.
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
open cmd window, typed adb reboot bootloader, and got:
T063202TFL and fastboot, and then a prompt.
Phone is in fastboot mode with white, yellow green text.
Device is unlocked. Status code 3.
Battery OK Charging
Transfer mode USB connected.
It looked as though I had to be able to accept the 4.4 kitkat OTA in order to get this done. but when i went to the usual spot to look for system updates it said there were none available.
Anyhow, I am super grateful for your help. Sorry to be such a remedial doofus
Looks like we can wait till tomorrow. Or today. Or whatever timeline it is.
Some background...Rooted and unlocked. I removed encryption right after I bought it.
I attempted to flash 5.1 the update. I flashed the bootloader and radio first, and rebooted the bootloader. Everything went fine until I tried to flash the system image. I got a lot of "sparse" errors.
When it rebooted it re-encrypted the device. But now nothing works. Phone, NFC ect shows errors. I can get into the bootoader, and I can flash stuff, but the recovery menu is gone,. It's just an error icon with "no connection" now.
Any ideas on how I can salvage this? I already backed everything up before I started. Is there a way I can just wipe everything and go back to stock? Even if it is 5.01?
EDIT - My bootloader is still showing as unlocked. I did not re-lock it.
JeffDenver said:
Some background...Rooted and unlocked. I removed encryption right after I bought it.
I attempted to flash 5.1 the update. I flashed the bootloader and radio first, and rebooted the bootloader. Everything went fine until I tried to flash the system image. I got a lot of "sparse" errors.
When it rebooted it re-encrypted the device. But now nothing works. Phone, NFC ect shows errors. I can get into the bootoader, and I can flash stuff, but the recovery menu is gone,. It's just an error icon with "no connection" now.
Any ideas on how I can salvage this? I already backed everything up before I started. Is there a way I can just wipe everything and go back to stock? Even if it is 5.01?
EDIT - My bootloader is still showing as unlocked. I did not re-lock it.
Click to expand...
Click to collapse
Install factory images using fastboot
https://developers.google.com/android/nexus/images
You might have "soft bricked" it, but if you still have bootloader access you are fine
I actually tried that, but it will not recognize it from ADB...I can flash stuff via fastboot, but ADB does not see it.
I did fully update the android SDK before I started. Should'nt that have updated all the drivers needed for ADB?
JeffDenver said:
I actually tried that, but it will not recognize it from ADB...I can flash stuff via fastboot, but ADB does not see it.
I did fully update the android SDK before I started. Should'nt that have updated all the drivers needed for ADB?
Click to expand...
Click to collapse
you update via fastboot, while youre in the bootloader. adb has nothing to do with it.
When I go to the platform tools folder, and use "adb devices", it tells me nothing after "list of devices attached". As if it does not see the phone.
When I attempt to "fastboot -w update image-shamu-lmy47d.zip", a window comes up and scrolls 3 or 4 lines too fast to see, and then exits. Nothing happens.
JeffDenver said:
When I go to the platform tools folder, and use "adb devices", it tells me nothing after "list of devices attached". As if it does not see the phone.
Click to expand...
Click to collapse
Have you updated the SDK? Drivers installed? Also, read up on how to use fastboot. Fastboot only works from bootloader, not when booted into Android.
I'm all for adb, but save yourself a headache and get wugs toolkit and use force flash.
Sent from my Nexus 6 using XDA Free mobile app
Better to learn some basics first then you shall fear no soft brick ever!
http://forum.xda-developers.com/showthread.php?t=2277112
Evolution_Freak said:
Have you updated the SDK? Drivers installed? Also, read up on how to use fastboot. Fastboot only works from bootloader, not when booted into Android.
Click to expand...
Click to collapse
SDK is updated. I assumed it updated drivers as well. If not, where do I get those?
I do understand that fastboot only works while in the bootloader. I have not attempted to use it while in Android.
JeffDenver said:
When I attempt to "fastboot -w update image-shamu-lmy47d.zip", a window comes up and scrolls 3 or 4 lines too fast to see, and then exits. Nothing happens.
Click to expand...
Click to collapse
Just extract the .zip and flash the things inside separately using fastboot. You can skip user data I believe (or not if you don't care about erasing your device). Using the -w switch would have erased it anyway. The commands are easy, just "fastboot flash system system.img" and the like. Change "system" and "system.img" for the file you're flashing.
Evolution_Freak said:
Have you updated the SDK? Drivers installed? Also, read up on how to use fastboot. Fastboot only works from bootloader, not when booted into Android.
Click to expand...
Click to collapse
Konfuzion said:
I'm all for adb, but save yourself a headache and get wugs toolkit and use force flash.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Where do I get that from?
JeffDenver said:
Where do I get that from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=56913254
Sent from my Nexus 6 using XDA Free mobile app
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
Evolution_Freak said:
Better to learn some basics first then you shall fear no soft brick ever!
http://forum.xda-developers.com/showthread.php?t=2277112
Click to expand...
Click to collapse
Better fear the bootloader downgrade soft brick
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
I'm all for adb, but save yourself a headache and get wugs toolkit and use force flash.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Are you sure you know what adb is?
:/
rootSU said:
Are you sure you know what adb is?
:/
Click to expand...
Click to collapse
What's it to you? Yeah I'm fine with adb thanks. If you want to discuss something other than helping the OP go ahead and pm me.
Sent from my Nexus 6 using XDA Free mobile app
mwalt2 said:
Just extract the .zip and flash the things inside separately using fastboot. You can skip user data I believe (or not if you don't care about erasing your device). Using the -w switch would have erased it anyway. The commands are easy, just "fastboot flash system system.img" and the like. Change "system" and "system.img" for the file you're flashing.
Click to expand...
Click to collapse
Ok, I did this. It appeared to work correctly, but...
My phone looks like it did before. In "about" I see it shows 5.1 as the version. I have lost root. Shouldn't I be reset to factory appearance since I overwrote the entire system? Everything looks intact, including nova launcher.
Phone appears to be working normally. I am on the phone on hold as I type this. I am just worried about problems down the road. Do I need to flash anything else? Can I assume the bootloader and radio installed correctly?
Konfuzion said:
What's it to you? Yeah I'm fine with adb thanks. If you want to discuss something other than helping the OP go ahead and pm me.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Its just you mentioned a toolkit as an alternative to adb but adb has nothing to do with any of this so if you're going to be helping the OP, I thought I'd better check that you know what you're talking about. ...which I don't think you do... So back to the point, how I'm helping the OP is by telling him to ignore everything you say. THAT'S "what's it" to me. Cheeky chops
@JeffDenver, ignore this guy. Use fastboot. Read general > all in one guide > question 28 for any info you may need, including drivers.
to repeat again, you use fastboot to flash the factory img, while youre in the bootloader. it should take you just several minutes to do, or a little bit longer if you are being very carefull. adb has nothing to do with it.
JeffDenver said:
Ok, I did this. It appeared to work correctly, but...
My phone looks like it did before. In "about" I see it shows 5.1 as the version. I have lost root. Shouldn't I be reset to factory appearance since I overwrote the entire system? Everything looks intact, including nova launcher.
Phone appears to be working normally. I am on the phone on hold as I type this. I am just worried about problems down the road. Do I need to flash anything else? Can I assume the bootloader and radio installed correctly?
Click to expand...
Click to collapse
its probably a good idea to factory reset since you're going up a major version and have already had problems.
rootSU said:
Its just you mentioned a toolkit as an alternative to adb but adb has nothing to do with any of this so if you're going to be helping the OP, I thought I'd better check that you know what you're talking about. ...which I don't think you do... So back to the point, how I'm helping the OP is by telling him to ignore everything you say. THAT'S "what's it" to me. Cheeky chops
@JeffDenver, ignore this guy. Use fastboot. Read general > all in one guide > question 28 for any info you may need, including drivers.
Click to expand...
Click to collapse
The reason I suggested wugs, is the first thing it has you do after installation is walks you through removing old drivers and installing the correct drivers and making sure that the phone is recognized. Then it will download the needed files and check the md5's which would help to avoid further problems.
Sent from my Nexus 6 using XDA Free mobile app
Full stock LVY48H on Fi . I've been wanting to go Marshmallow, but Google hasn't gotten around to sending me the OTA. I found this thread in the General forum and downloaded the appropriate .ZIP, but the contents don't look a bit like the ROM downloads, so fastboot doesn't appear to be an option. How do I put it on?
Download factory image, extract, flash each img file separately except for userdata.
Mostlyhrmlss said:
Full stock LVY48H on Fi . I've been wanting to go Marshmallow, but Google hasn't gotten around to sending me the OTA. I found this thread in the General forum and downloaded the appropriate .ZIP, but the contents don't look a bit like the ROM downloads, so fastboot doesn't appear to be an option. How do I put it on?
Click to expand...
Click to collapse
If your bootloader is unlocked, you can flash it manually in ABD or use that toolkit (for factory image). I did that but it it also wiped my phone, which was fine by me, it needed a good cleaning after flashing updates to another custom 5.1.1 rom over and over again!
@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
@Tower1972: Attached is a screenshot of the contents of the ZIP. How would I go about flashing that with ADB?
Mostlyhrmlss said:
@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
Click to expand...
Click to collapse
RTFM
Tower1972 said:
If your bootloader is unlocked, you can flash it manually in ABD or use that toolkit (for factory image). I did that but it it also wiped my phone, which was fine by me, it needed a good cleaning after flashing updates to another custom 5.1.1 rom over and over again!
Click to expand...
Click to collapse
when youre giving advice to someone, make sure that its correct. you dont flash anything with adb, you use fastboot. fastboot is different than adb.
@boomerbubba: FTFY: Here's a guide on how to do that. I prefer civility when applicable; my sympathies for whatever is going on in your life to make you want to answer in such a way.
@simms22: Turns out the advice was correct: "adb sideload [OTA file].zip" is the appropriate command to accomplish what I'm after here.
Some strategic Googling found me the answer while I was awaiting responses, here it is for the benefit of anyone who should have the same question. Prollyshooda done that first.
Mostlyhrmlss said:
@boomerbubba: FTFY: Here's a guide on how to do that. I prefer civility when applicable; my sympathies for whatever is going on in your life to make you want to answer in such a way.
@simms22: Turns out the advice was correct: "adb sideload [OTA file].zip" is the appropriate command to accomplish what I'm after here.
Some strategic Googling found me the answer while I was awaiting responses, here it is for the benefit of anyone who should have the same question. Prollyshooda done that first.
Click to expand...
Click to collapse
actually, you were incorrect. you said use adb to manually flash. now you said adb for adb sideload. those are two completely different things. all adb sideload does is move a file from your computer to your phone.
edit.. now you are right, i read your response wrong :angel:
Contrition on the Internet? Whodathunkit! We should get together for a beer, I like your kind of folk.
Mostlyhrmlss said:
Contrition on the Internet? Whodathunkit! We should get together for a beer, I like your kind of folk.
Click to expand...
Click to collapse
contrition is one of the things that pull me down. but its honesty, and the truth. so i stay with it
Mostlyhrmlss said:
@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
@Tower1972: Attached is a screenshot of the contents of the ZIP. How would I go about flashing that with ADB?
Click to expand...
Click to collapse
I don't know what zip file that is, but it's not a factory image from Google. If you download a factory image from Google, you extract every img file and flash using fastboot.
What is everyone's fascination with adb sideload?
nhizzat said:
What is everyone's fascination with adb sideload?
Click to expand...
Click to collapse
It doesn't require an unlocked bootloader. Which for the people that haven't done that, it wipes your phone as part of the unlock process.
Also, it is a smaller download if you are on an ISP with limited bandwidth.
Google says....
http://https://developers.google.com/android/nexus/images
That will get you going, but since the included script won't work, you have to unzip the zip package, what you will find inside the parent folder. Happy flashing
nhizzat said:
I don't know what zip file that is, but it's not a factory image from Google. If you download a factory image from Google, you extract every img file and flash using fastboot.
What is everyone's fascination with adb sideload?
Click to expand...
Click to collapse
That ZIP is an OTA downloaded from the thread referenced in my original post. My fascination with adb sideload (now that I know what it is) is that I can accomplish an upgrade with a single command, which suits my advanced case of laziness very well . Seems much easier than unzipping a file, then unzipping a file from that file (more than doubling the storage requirement, I have a rather small SSD) and issuing several fastboot commands with slightly different syntaxes and hoping I didn't miss (or mistype) something.
I already know how to do a full flash, I unlocked the bootloader and did so first thing when I bought it used to make sure it was cleared of the previous owner's data and completely up-to-date. What I wasn't sure of is if it would be safe to do so for a full version jump. I'm much more comfortable with OTAs since I've applied several and it stands to reason that a carrier would never issue one if it might cause an undue number of problems for their support staff to address.
Martend said:
That will get you going, but since the included script won't work...
Click to expand...
Click to collapse
That script just burns my biscuits. Why in the name of all that is neat and groovy can't Google fix such a basic problem?
Mostlyhrmlss said:
That script just burns my biscuits. Why in the name of all that is neat and groovy can't Google fix such a basic problem?
Click to expand...
Click to collapse
because its fixed in the latest version of fastboot, that no one seems to be using..
simms22 said:
because its fixed in the latest version of fastboot, that no one seems to be using..
Click to expand...
Click to collapse
Why break it in the first place? lol It's the first thing you learn here, debug & test before releasing it to the masses
So, I got the latest ADB and FASTBOOT from here, put the device in ADB update mode through recovery mode (already OEM unlocked and USB debugging enabled), ran 'adb sideload <filename>' as instructed onscreen, and got "error: device (null) not found" from the command. The device shows up in the Windows device manager when in bootloader mode, but disappears when I go to recovery mode. What am I doing wrong?
Mostlyhrmlss said:
So, I got the latest ADB and FASTBOOT from here, put the device in ADB update mode through recovery mode (already OEM unlocked and USB debugging enabled), ran 'adb sideload <filename>' as instructed onscreen, and got "error: device (null) not found" from the command. What am I doing wrong?
Click to expand...
Click to collapse
do you have the drivers installed? fastboot wont see your device until then.
I installed the drivers as part of the ADB/FASTBOOT package referenced above, but that's not the problem: the device is not shown at all in the Windows device manager, as if it wasn't plugged in.