Related
After much searching and work on fixing my bricked captivate, i broke down and bought a jig from mobiletechvideos.com. It works perfectly as intended, except for the fact that my pc is not recognizing the phone after it enters download mode. As a side note, i may have royally screwed up when i did something in clockwork recovery, where now i cant even get past the ATT World phone boot screen. Im afraid i may have deleted anything that can mount the phone to the pc. I have already installed the proper drivers, I think. Anything i can do to fix this?
So it shows the world phone screen a bunch of times? Plug it into an outlet see if the green battery comes up, just wait for it, the Gray battery will do a short of loop a few times... Once its at the green battery try to turn the phone on, be patient too, if you get the phone on, go to settings> privacy then factory data reset, make sure you backup to external or computer first
Your welcome
Now you say/press thanks
Teaching manners one person at a time
Thats not gonna work... nothing i know of can be done to it. it doesn't move past the att screen. No animation, not sound. Just ATT World Phone. i can get into download mode, but cant connect to computer. Thats the problem right there.
Try restarting your computer? I've had similar issues on a yucky iPhone, and I've read about other Captivate users with it as well, and a restart helped resolve the problem.
Go under your drivers and uninstall them and reinstall them it helped when I finally had got mine "back to his construction job" (lol download mode) it should then work
Sent from my SAMSUNG-SGH-I897 using XDA App
Ive already tried another PC and Uninstalling and reinstalling the drivers to no avail.
It just like the phone isn't even there. It will charge, but wont mount to the PC.
Not trying to insult your intelligence or anything (I might actually be insulting my own) but you have Odin open, right?
Just trying to think of anything lol
Yeah, but it wouldnt matter anyway if the computer doesnt know its there.
Try cleaning the mini usb port. Or switch the usb cord connector the samsung factory one tends to break the data + and -.
As for not getting past the at&t screen. The kernel you installed cannot read the system partition probably corrupted or the kernel you installed cannot read ext4.
If you cannot get it to be recognized send it back to your carrier for repair, should be under warranty.
Thats what im doing now. Thanks for the help, though.
Palen222 said:
After much searching and work on fixing my bricked captivate, i broke down and bought a jig from mobiletechvideos.com. It works perfectly as intended, except for the fact that my pc is not recognizing the phone after it enters download mode. As a side note, i may have royally screwed up when i did something in clockwork recovery, where now i cant even get past the ATT World phone boot screen. Im afraid i may have deleted anything that can mount the phone to the pc. I have already installed the proper drivers, I think. Anything i can do to fix this?
Click to expand...
Click to collapse
You sure you have the proper drivers installed for your phone? The links for them are on the odin forum in captivate development
Sent from my SAMSUNG-SGH-I897 using XDA App
Stuck at "Samsung Galaxy" boot screen, cant get into bootloader, computer wont detect
Hey everyone this has been a huge hassle for me for the last few days and was hoping someone could help me. I have had to resort to using my HTC Legend...which I love but it doesnt have what I need.
I was in recovery the other day trying to load a custom rom through the CWM and I went through and accidentally hit "format system". I couldn't cancel the process so I knew something bad was going to happen....I reboot the phone and for the last 3 days I have had it plugged into the Usb charger with no luck of booting, it has been stuck at the "Samsung Galaxy S 19000M" boot screen and no further. I took the battery out and tried rebooting it after a few minutes. No luck with this either, still stuck at the Samsung screen. I CAN get into "DOWNLOAD MODE" but I CAN NOT get into recovery/bootloader (hold volume up/home button/power button).
I have put it into download mode and and plugged it into the computer (I am running Windows 7 64-bit) and it will not detect it. I have all of the correct drivers, I know this as I have a friend who owns the exact same phone and my computer detects it just fine. Odin nor ADB will detect that there is anything AT ALL plugged into the computer. It does not even come up as, "android device", or "storage", there is nothing, nota, it is as if the phone isn't even plugged in. It will not detect in "download mode" nor while its stuck at the "Samsung Galaxy S" screen, and yes I have tried a different USB cable, and still nothing..
I am quite capable with electronics but I cannot find anything on the internet as of what to do. Is there anything that I could load on an external SD card that would force the phone to flash a ROM with new kernal and modem? I think the phone is empty that is why it is not booting, as if there is nothing to load on the phone. Is there anything at all that anyone can think of??? I am completely stuck. I wanted this phone to last until the Samsung Galaxy S 2 was released here lol.
I'm with Virgin Mobile Canada. Thanks!
Cant you get it into Recovery mode?
Have you tried heimdall?
You will have to follow the instructions coming with it to the letter (about installing some custom USB-driver).
Herman76 said:
Cant you get it into Recovery mode?
Click to expand...
Click to collapse
Hey herman, "I CAN get into "DOWNLOAD MODE" but I CAN NOT get into recovery/bootloader (hold volume up/home button/power button)."
profalbert said:
Have you tried heimdall?
You will have to follow the instructions coming with it to the letter (about installing some custom USB-driver).
Click to expand...
Click to collapse
Hey, I will search for that right away and let you know how it turns out. Thank you!!
well if you have download mode then dont panic.
just flash a 3 file firmware along with pit file and re-partition and you will be fine
azzledazzle said:
well if you have download mode then dont panic.
just flash a 3 file firmware along with pit file and re-partition and you will be fine
Click to expand...
Click to collapse
How can I flash any firmware if my PC will not detect the phone? When I plug the phone in there is nothing. Odin doesn't detect the phone, Keis doesn't detect the phone, ADB does not detect the phone, and I just tried Heindall, and it does not detect the phone..... Maybe the actual hardware for the USB plug in is faulty in its self, in which case I am screwed.
Galaxy19000M said:
How can I flash any firmware if my PC will not detect the phone? When I plug the phone in there is nothing. Odin doesn't detect the phone, Keis doesn't detect the phone, ADB does not detect the phone, and I just tried Heindall, and it does not detect the phone..... Maybe the actual hardware for the USB plug in is faulty in its self, in which case I am screwed.
Click to expand...
Click to collapse
i see..... i only read the last 2 posts and im always telling people off for not reading properly
have you tried the obvious steps such as
Un-install - Re install Kies
Run Odin as administrator
Tried Alternative USB port - direct into the PC motherboard
Finally a different PC all together
hope you can get it workin hate to see another broken SGS
azzledazzle said:
i see..... i only read the last 2 posts and im always telling people off for not reading properly
have you tried the obvious steps such as
Un-install - Re install Kies
Run Odin as administrator
Tried Alternative USB port - direct into the PC motherboard
Finally a different PC all together
hope you can get it workin hate to see another broken SGS
Click to expand...
Click to collapse
I have tried, uninstall-re install of kies, run odin as admin, alternate usb port, anddd I tried plugging it into my laptop...no luck...this absolutely driving me nuts because I know the phone cant be bricked, if I can get into download mode I SHOULD be fine but for some strange reason the phone seems to be undetectable...ahhhhhhhhhhhh if only there was just some way to access the internal storage or a program that would force a flash through an external SD....
I am going to try loading Ubuntu on my computer on one of my HDD and see if it will detect the phone. I am assuming this is my last option and I have high hopes as Ubuntu detects almost anything...I will update...if it doesnt work I might be looking into taking apart the phone its self and intalling a new USB plug in on the phone motherboard...
im not sure of any other steps
last resort.... have you tried another USB cable ? like your friends cable that he uses for his phone ?
EDIT: if i was you i WOULD NOT take the phone apart.... if you do and it does not work, your warranty will be void,
at least if you cant get it working you can send it off for repair and blame kies, you will have a good chance of getting it fixed by samsung than you would yourself
azzledazzle said:
im not sure of any other steps
last resort.... have you tried another USB cable ? like your friends cable that he uses for his phone ?
Click to expand...
Click to collapse
yeah lol like I said in the first post I tried a different USB cable all together.
I have two HTC Legends, tried both cables from them, plus the OEM cable that came with the SGS
azzledazzle said:
im not sure of any other steps
last resort.... have you tried another USB cable ? like your friends cable that he uses for his phone ?
EDIT: if i was you i WOULD NOT take the phone apart.... if you do and it does not work, your warranty will be void,
at least if you cant get it working you can send it off for repair and blame kies, you will have a good chance of getting it fixed by samsung than you would yourself
Click to expand...
Click to collapse
I dont know if it has been opened already by someone else. I bought the phone for $180 CAD from a sort of "2nd turn" site. As in it was being sold as is. The phone problem reported by them was that the USB connectivity was not working. When I originally got the phone from them everything was working correctly, except the USB connectivity like it stated. It came ROOTED and loaded with the leaked version of Froyo before it was out so I automatically assumed that was causing the USB problems. I got around to changing the ROM with a reported working USB using CWM. But, still no luck with USB connectivity. I just dealt with the problem and flashed everything through CWM. Which led me to this...ugh
Is there supposed to be a warranty seal behind the battery cover? Over the screws like there usually is? Cause I see nothing..
thats not good news.
there is no warranty sticker, but samsung could find out if the phone has been opened.
It depends on the actual repair guy, to be honest, samsung will have 100's of phones to repair daily, the majority just get passed on - flashed - wiped - boxed and sent back to the owner.
however if some (P)Rick is having a bad day and wants to find out why the phone is in for repair, and he finds out its been opened up, or its had custom firmware, then he can refuse to fix the phone or send it back to you with a bill included lol.
so you have to have a good excuse incase the worst happens.
if you dont fancy your chances and you feel capable of replacing the USB yourself then hey go for it !!
azzledazzle said:
thats not good news.
there is no warranty sticker, but samsung could find out if the phone has been opened.
It depends on the actual repair guy, to be honest, samsung will have 100's of phones to repair daily, the majority just get passed on - flashed - wiped - boxed and sent back to the owner.
however if some (P)Rick is having a bad day and wants to find out why the phone is in for repair, and he finds out its been opened up, or its had custom firmware, then he can refuse to fix the phone or send it back to you with a bill included lol.
so you have to have a good excuse incase the worst happens.
if you dont fancy your chances and you feel capable of replacing the USB yourself then hey go for it !!
Click to expand...
Click to collapse
Well thank you for all the help. I am going to try installing Ubuntu first and see what happens, I have never had any driver issues with that OS EVER so if its detectable, Ubuntu will be the one to detect it. If that doesn't work I might take my chances and send it in. And if like you said that one person decides to screw me over, they at least have to send it back to me, in which case I will just open it myself and change the USB plug in like I said. (which might not even be the problem...)
Is there anyway to tell on the out side without opening it if it has indeed been opened before???
erm..... i dont think so, but i dont know what measures samsung have took to find this out.
if it was me the obvious things i would look for is, damaged screw heads and scratches down the sides - where the casing has been prised open. other than that i would not know what to look for
either way, i hope u get it fixed
azzledazzle said:
erm..... i dont think so, but i dont know what measures samsung have took to find this out.
if it was me the obvious things i would look for is, damaged screw heads and scratches down the sides - where the casing has been prised open. other than that i would not know what to look for
either way, i hope u get it fixed
Click to expand...
Click to collapse
Well I sent my phone in to Samsung last week and I just got it back today! I opened it up and I guess the problem with the phone was pretty bad lol they just gave me a new phone, I was thinking it was refurbed but it said right on the repair receipt "condition=NEW" I am extremely happy.
That aside, do you know if you can use the SGS II if it is unlocked in Canada?
Hello, my name is TNSM and i'm new here. I signed up because i can't find anything on the internet that can help me, so i thought maybe someone here may be able to help me.
I have a Samsung Galaxy S3 Mini GT-I8190 and i'm experienced with rooting and flashing custom roms stuff. So, i was looking everywhere for a rom that included the HALO feature and after days of failed research, i found a link on Youtube to download a rom with Halo for my smartphone. I went into the recovery, backed up my current rom, wiped data and performed a factory reset, installed the rom and rebooted the phone... but after i chose the "Reboot" option, the phone never again gave a sign of life. It doesn't turn on, it doesn't show any lights whatsoever, i've tried to charge it overnight, but still nothing, considered buying a USB JIG but didn't work, my cousin says the phone seems like it doesn't even have the bootloader anymore... is my phone more than hard-bricked? Is there a way to wake my phone up again? Just for the record, it has no physical damage, it just seems like it has no software inside, that it's just hardware. By the way, when i connect it to the pc using the usb cable, the pc keeps playing the sound that something was plugged in and that something was plugged out right after, and it loops forever.
I'll give more information about the phone if needed. And i hope someone's able to help me.
- TNSM
TNSM said:
Hello, my name is TNSM and i'm new here. I signed up because i can't find anything on the internet that can help me, so i thought maybe someone here may be able to help me.
I have a Samsung Galaxy S3 Mini GT-I8190 and i'm experienced with rooting and flashing custom roms stuff. So, i was looking everywhere for a rom that included the HALO feature and after days of failed research, i found a link on Youtube to download a rom with Halo for my smartphone. I went into the recovery, backed up my current rom, wiped data and performed a factory reset, installed the rom and rebooted the phone... but after i chose the "Reboot" option, the phone never again gave a sign of life. It doesn't turn on, it doesn't show any lights whatsoever, i've tried to charge it overnight, but still nothing, considered buying a USB JIG but didn't work, my cousin says the phone seems like it doesn't even have the bootloader anymore... is my phone more than hard-bricked? Is there a way to wake my phone up again? Just for the record, it has no physical damage, it just seems like it has no software inside, that it's just hardware. By the way, when i connect it to the pc using the usb cable, the pc keeps playing the sound that something was plugged in and that something was plugged out right after, and it loops forever.
I'll give more information about the phone if needed. And i hope someone's able to help me.
- TNSM
Click to expand...
Click to collapse
You may try to pull off the battery for few mins, then with someone's help hold the 3 buttons for download mode and then plug in the battery...
If you can't turn it in download mode there's no way to fix it, except jtag maybe.
I have the feeling I'm going to get repetitive here guys, but I've been reading the troubleshooting threads for over an hour and couldn't find an answer to help me.
Last saturday I was to lazy to move from the couch, so I watched as my S3 Mini ran out of battery. I got the "phone is turning off" screen as usual. Later I went to bed, but as I needed my alarm to go off in the morning I tried turning it on again, and nothing* happened. Plugged it on the wall, nothing*. Replaced the battery, nothing*. Gave it a good half hour plugged, and as you can guess, nothing*.
* when I say nothing, I mean it won't light up, won't vibrate, won't wink for me, won't load any kind of error, it's actually just like if you were trying to turn on a phone without any battery connected, no grasp of life comes from its poor soul.
The only moment I could see some action on the device is when I tried connecting it on the PC a few hours ago, as it installed drivers to Windows. Right after installing the drivers however, it won't show in the file explorer. I've tried to detect it with a few development tools such as ORT and Odin and there was no sucess either. Download or Recover mode will not work as well.
One thing I think worth mentioning, is that ever since I rooted it a couple of years ago, whenever I tried to recharge it while it was off, the standard "green charging battery" would never appear. What would appear on the screen was a freezed loading icon (the one that keeps roling again and again, but frozen). This particular issue never came off, even reseting it or installing new ROMs.
I always used Maclaw's, some of the latest 4.x, because I tought the 5.x was to heavy for the s3 minis.
I've read some about USB JIGs and stuff, but what makes me very curious is what the heck?! The phone was working just fine, the battery runs out and I have a brick? Is this possible? Can anyone tell me any work around?
I apologize for possible grammar mistakes.
ScrewedImei said:
I have the feeling I'm going to get repetitive here guys, but I've been reading the troubleshooting threads for over an hour and couldn't find an answer to help me.
Last saturday I was to lazy to move from the couch, so I watched as my S3 Mini ran out of battery. I got the "phone is turning off" screen as usual. Later I went to bed, but as I needed my alarm to go off in the morning I tried turning it on again, and nothing* happened. Plugged it on the wall, nothing*. Replaced the battery, nothing*. Gave it a good half hour plugged, and as you can guess, nothing*.
* when I say nothing, I mean it won't light up, won't vibrate, won't wink for me, won't load any kind of error, it's actually just like if you were trying to turn on a phone without any battery connected, no grasp of life comes from its poor soul.
The only moment I could see some action on the device is when I tried connecting it on the PC a few hours ago, as it installed drivers to Windows. Right after installing the drivers however, it won't show in the file explorer. I've tried to detect it with a few development tools such as ORT and Odin and there was no sucess either. Download or Recover mode will not work as well.
One thing I think worth mentioning, is that ever since I rooted it a couple of years ago, whenever I tried to recharge it while it was off, the standard "green charging battery" would never appear. What would appear on the screen was a freezed loading icon (the one that keeps roling again and again, but frozen). This particular issue never came off, even reseting it or installing new ROMs.
I always used Maclaw's, some of the latest 4.x, because I tought the 5.x was to heavy for the s3 minis.
I've read some about USB JIGs and stuff, but what makes me very curious is what the heck?! The phone was working just fine, the battery runs out and I have a brick? Is this possible? Can anyone tell me any work around?
I apologize for possible grammar mistakes.
Click to expand...
Click to collapse
try to plug in the phone into charger & leave it there like 20 mins or more. battery loads then.
then try access samsung download mode, if you cant the phone is probably useless (brick for ever) because itslike mthe last standing thing.
& sorry i say that but thats typically samsung behaviuor. there allways this kind of threads in the samsung forums of xda... other manufacturer can mostly be restored or atleast you know what make it dead.
Exactly the same problems happening to me.
This is my thread:
http://forum.xda-developers.com/galaxy-s3-mini/help/sgs3-mini-dead-t3085031
Can you try to follow what appears on this link? (I can't by now because my PC is broken)
I think won't do nothing because you won't be able to access to the recovery mode on android, as me, but to try...
http://forum.xda-developers.com/showthread.php?t=1840030
bejunk said:
try to plug in the phone into charger & leave it there like 20 mins or more. battery loads then.
then try access samsung download mode, if you cant the phone is probably useless (brick for ever) because itslike mthe last standing thing.
& sorry i say that but thats typically samsung behaviuor. there allways this kind of threads in the samsung forums of xda... other manufacturer can mostly be restored or atleast you know what make it dead.
Click to expand...
Click to collapse
Hi there,
Thank you for your interest but I have passed this point already. Tried a brand new battery I had laying down in the drawer (which was fully charged with an universal charger) and there is no answer to any attempt of turning it on. Via recovery, download or normal boot.
CrashOverride93 said:
Exactly the same problems happening to me.
This is my thread:
http://forum.xda-developers.com/galaxy-s3-mini/help/sgs3-mini-dead-t3085031
Can you try to follow what appears on this link? (I can't by now because my PC is broken)
I think won't do nothing because you won't be able to access to the recovery mode on android, as me, but to try...
http://forum.xda-developers.com/showthread.php?t=1840030
Click to expand...
Click to collapse
Hello there,
I'm sorry to hear I'm not the only one affected by this bug (lets call it a bug). This shows there is a lack of concern from Samsung on dealing with this issues, and thus we see that old programmed obsolescence.
I will try that later on the weekend, and I come back here with an report.
Cheers
ScrewedImei said:
Hi there,
Thank you for your interest but I have passed this point already. Tried a brand new battery I had laying down in the drawer (which was fully charged with an universal charger) and there is no answer to any attempt of turning it on. Via recovery, download or normal boot.
Hello there,
I'm sorry to hear I'm not the only one affected by this bug (lets call it a bug). This shows there is a lack of concern from Samsung on dealing with this issues, and thus we see that old programmed obsolescence.
I will try that later on the weekend, and I come back here with an report.
Cheers
Click to expand...
Click to collapse
this guide useless for you. how u want flash things with odin if u cant enter download mode at all??
im really sorry for you that this phone is dead. just can give you 1 advice, dont buy samsung in future.
I have been repaired my phone successfully!!!
I just needed to change two capacitors on its motherboard, and that's it.
Here the video where I have found the info and how to do that. It's in Spanish but easy to understand for you I think. But if you need some help, send me a PM.
can you take a picture from the location of the 2 capasitors and the types of it
Hi everyone.
I have some news. It took me a while but I followed CrashOverride93's advice on that video. It actually solved one issue, as I now can turn it on, but now I have a second problem, I'm stuck on a boot loop, with acess to Download mode ONLY. No recovery.
Considering where my issue started, and where I am now, I have tried the following:
- Flashed via Odin stock ROM, kernel;
- flashed Wipe;
- flashed PARAM;
- three button combo.
So far I couldn't get it pass the boot loop. Any thoughts?
Hello Moto,
So I got my Moto G5s Plus awhile back when it was still new and I tried to root it right off (I know...it was stupid, I realize I should've waited a little until the stock firmware was released and more guides were made), and basically I ended up hard bricking my device.
There are no lights, the screen is completely blank, and the power button does absolutely nothing.
I have heard of a way to revive it from level 0, however, and I was on the path to doing that until I realized that-for some reason-my laptop does not recognize my dead phone at all. In the guide (which I've long since lost the link to..) it said that my phone would appear in my device manager (>start>right click on Computer>manage) under the android tab after installing a bunch of ADB drivers and such, as "ADB-somethingsomething". No such thing happened; I couldn't even find the tab it was referencing. Even after uninstalling and reinstalling the drivers that it mentioned, I couldn't seem to get my laptop to recognize my phone.
Interestingly enough, or perhaps not, I plugged it into my brother's laptop and it recognized it just fine (note, he had the drivers already installed and has meddled quite a bit already in this area).
Anyway, so now I have a pretty much mint condition hardware Moto G5s Plus, and I kind of don't want to spent money on another phone unless I know for sure that I can't fix this one. Is there any way to revive it from the dead?
P.S. I've found the stock ROM for the phone...but there's several different packages. (like..NPS26.116-26; NPS26.116-45; NPSS26.116-45-5; etc...) This my be a very stupid question..but how should I know which one is the one I need to download?
Any and all advice/help would be appreciated.
Thank you
[SOLVED]
So I managed to get it working without using a virtual machine.
To address the first problem, my phone wasn't even charged. To solve this I took a rubber band and tied it around the power and volume down buttons and attached it to a wall outlet for about an hour. (The little white light was flashing to signal that it was receiving power...which was more than I had accomplished than..ever..really...)
The second problem was my computer. I still don't know why it worked out like this, but essentially my computer never recognized my phone as the HS-USB or anything. Instead, my computer recognized it as Motorola ADB Interface (even though it was technically off and hard bricked..). This made recovering it easy, as I simply could fastboot flash the correct stock rom to my phone and go from there.
After trying a few different stock ROMs, I finally got the right one, and could boot into bootloader. And thus, finally, I was able to install TWRP, the OS back, Xposed, and Magisk.
I've used my phone for a bit now and no problems have come up. Installing Xposed did take a bit longer than I thought it would, but other than that I got me phone back.
My moto g5s plus is completely dead even bootloader is not working nothing to show just blank how I can get the solution of this problem. Company is asking to change the motherboard. Help
jaura.mohit said:
My moto g5s plus is completely dead even bootloader is not working nothing to show just blank how I can get the solution of this problem. Company is asking to change the motherboard. Help
Click to expand...
Click to collapse
Are they charging u for the motherboard Change
Yes 18000 rupees
---------- Post added at 06:55 AM ---------- Previous post was at 06:29 AM ----------
yograjfire18 said:
Are they charging u for the motherboard Change
Click to expand...
Click to collapse
18000 rupees hel p me to recover my phone
Rooting is software based thing, which should not damage hardware to that level,, right?
The blank-flash stuff can be helpful for you guys, but we don't have blank-flash files for our device.
You can search, learn and manage how to do it.
EDIT: can you check what happens if you keep pressed powe key and volume- key for atleast 2 minuts ??
____Mdd said:
Rooting is software based thing, which should not damage hardware to that level,, right?
The blank-flash stuff can be helpful for you guys, but we don't have blank-flash files for our device.
You can search, learn and manage how to do it.
EDIT: can you check what happens if you keep pressed powe key and volume- key for atleast 2 minuts ??
Click to expand...
Click to collapse
Yea, no, this is 100% software damage. Like I said, I have a mint condition (hardware wise) phone. I'm pretty sure what I did to mess it up was overwrite the data files for the previous OS. I remember trying to get it back to stock ROM, but having a crap ton of trouble finding it...and then pretty much doing a fight or flight thing and trying a stupid and edgy alternative. (I also remember, even while the phone was still working, it only booted into TWRP once or twice, otherwise it would always come up with an error)
I feel like all I need to do is flash the stock ROM to the device...but without my laptop even recognizing it, I don't know how. Essentially, the question being, is there a way to flash the stock ROM to my device without TWRP, without bootloader, without using the device at all (just my laptop); and if there is...does anyone know how?
Pressing the power and volume buttons did nada.
[edit]
I did some searching and I actually found the two links that I used while trying to recover my phone from the dead.
http://www.aryk.tech/2017/09/moto-g5s-plus-unbrick-solutions.html
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
The difference for me is that I never got my laptop to recognize it as any of the "HS-USB Bulk, HS-USB QDLoad 9008, QHS-USB DLoad 9008"; that's where I stopped in the steps.
I'll be trying to follow the steps in the first link again, but this time through virtualbox (make sure there's no conflicting drivers and whatnot). I'll post back with results whenever I get around to it.
flash -61