I apologize ahead but I have not been able to find a thread that addresses my problem.
Kindle Fire (1st gen)
Rooted with KFU, installed FFF, TWRP, Go Launcher and Gaaps. Worked perfectly.
Attempted to flash hashcode's JB ROM with Goo manager and made a mistake.
Attempted to boot to system and all that will show is the Rolling Triangles splash screen
continuously.
I can boot to TWRP.. I want to start over and flash the Amazon update 6.3.1 but my
Windows 7 PC cannot connect to the Kindle over usb. Fastboot seems to connect
(returns "Kindle" on fastboot getvar product) ADB does not show any devices attached.
I have deleted and reinstalled drivers - Windows does not recognize the Kindle.
Will a factory cable allow my PC to recognize my stuck Kindle?
Which version of twrp are you using?
Sent from my Amazon Kindle Fire using xda app-developers app
A factory cable will only put your device in fastboot. If you plug the kindle in while in recovery it should install the correct drivers. Try connecting to your computer and selecting mount and hit the big button to access your sdcard contents, where you can transfer a new rom zip to it. I wouldn`t attempt to flash stock unless you research prior many brick their devices and then a factory cable is needed. Did you wipe before flashing? If so how and what?
Also, do you have FireFireFire installed?
Thank you for your replies!
I have FFF installed
TWRP is 2.3
I did do a cache wipe and factory reset within TWRP
I did see this morning manofFishfry posting "[Q] I need help bad"
and it seems he was having a nearly identical problem with USB
connection.
I will attempt thepooch's recommendation:
http://forum.xda-developers.com/show....php?t=1850038
I will post any progress I make.
Many thanks
M
TWRP 2.3 is your issue if you do get ubuntu setup with Soupkit simply replace 2.3 with 2.2.2.1 and rewipe and reflash another rom.
Thepooch said:
TWRP 2.3 is your issue if you do get ubuntu setup with Soupkit simply replace 2.3 with 2.2.2.1 and rewipe and reflash another rom.
Click to expand...
Click to collapse
Looks like I'm still stuck then - I've only got Win7 on my PC - unbuntu is WAY out of my league.
I'll try Zombiepiratez unbrick utility
M
It`s not that far out of your league. Use universal usb creator to make a live usb with persistent run soupkit on it reboot the usb Your in like flin If you want help I can help you at some point to get this done.
Thepooch said:
It`s not that far out of your league. Use universal usb creator to make a live usb with persistent run soupkit on it reboot the usb Your in like flin If you want help I can help you at some point to get this done.
Click to expand...
Click to collapse
I removed the Kindle drivers from my Laptop PC and then connected my son's unrooted stock KF1. It was recognized, the drivers loaded, and I loaded the KFU drivers and updated them no problem. I ran KFU and got 4000 on the code.
I then plugged in my "stuck in TWRP/FFF/JB Splash Screen" rooted KF1 and the PC sees it as a removable memory device. It prompts me to load it with media when I double click on it. KFU can't find it. ADB can't find it. Fastboot can get "Kindle" from getvar product, but nothing else.
What can I do next?
Thanks!
Update
Micah461 said:
I removed the Kindle drivers from my Laptop PC and then connected my son's unrooted stock KF1. It was recognized, the drivers loaded, and I loaded the KFU drivers and updated them no problem. I ran KFU and got 4000 on the code.
I then plugged in my "stuck in TWRP/FFF/JB Splash Screen" rooted KF1 and the PC sees it as a removable memory device. It prompts me to load it with media when I double click on it. KFU can't find it. ADB can't find it. Fastboot can get "Kindle" from getvar product, but nothing else.
What can I do next?
Thanks!
Click to expand...
Click to collapse
One new thing: I mounted the SD card using TWRP, then my Win 7 Laptop could connect to my Kindle via usb as an external drive. Win 7
then siad the drive needed reformatting. KFU still would not connect.
would the soupkit help in this situation? I had the same problem but figured out the whole mounting from TWRP and it worked for me
Micah461 said:
One new thing: I mounted the SD card using TWRP, then my Win 7 Laptop could connect to my Kindle via usb as an external drive. Win 7
then siad the drive needed reformatting. KFU still would not connect.
Click to expand...
Click to collapse
Your sdcard issue and ADB issue are two completely unrelated things. The ADB issue is due to the way Windows handles drivers. Fix the driver problem or use SoupKit/Linux.
The sdcard issue is due to your sdcard losing its formatting somehow. You'll have to reformat (quick format, block size 4096) in order to use it again. You will lose all data on the sdcard BTW.
"That's a special kind of stupid. The kind that makes me laugh"
Huzzah! Success in spite of myself!
Many thanks to each of the experts that each gave me nuggets of info that eventually
unbricked my KF1.
I last posted that Win 7 would see my Kindle when I used TWRP to mount the SD card.
It prompted for me to "format the device" and feeling I had nothing to lose - selected
default settings and quick format.
This then opened a File Manager window giving me access to the SDcard folder on the KF1.
I had downloaded the Stock update from Amazon update-kindle-6.3.1_D01E_4107720.bin
On another thread - Soupmagnet had said to rename this BIN file to a ZIP - which I did.
I shortened the file name to update-kindle-6.3.1.zip.
I de-mounted the SDcard folder in TWRP.
I wiped the Dalvic and did a factory reset.
I navigated to the Install screen and it found the update file and installed it.
UNBRICKED!
Thanks again for the tireless help you guys give.
Micah461
Related
I looked at almost every thread I could see that sounds like my case but in every one the device is at least being recognized by USB on the computer, in my case it has absolutely no recognition.
I had custom gedeROM. gf didn't like it and so I decided to go back to stock.
within TWRP I did Factory reset, then installed the stock bin file that i renamed to update.zip. Install went through properly so I restarted.
Now it is frozen on Kindle Fire boot screen, and it won't go further. Attaching it to a computer with USB will power the Kindle on but the computer will not detect it, tried on 3 computers, Windows 7 and Linux. I have tried to use all forms of unbricking, everything except opening the Kindle. But since the device isn't being recognized by USB at all on any system I don't know what to do.
With a Factory cable help with this?
Thanks for any help.
slyphin said:
I looked at almost every thread I could see that sounds like my case but in every one the device is at least being recognized by USB on the computer, in my case it has absolutely no recognition.
I had custom gedeROM. gf didn't like it and so I decided to go back to stock.
within TWRP I did Factory reset, then installed the stock bin file that i renamed to update.zip. Install went through properly so I restarted.
Now it is frozen on Kindle Fire boot screen, and it won't go further. Attaching it to a computer with USB will power the Kindle on but the computer will not detect it, tried on 3 computers, Windows 7 and Linux. I have tried to use all forms of unbricking, everything except opening the Kindle. But since the device isn't being recognized by USB at all on any system I don't know what to do.
With a Factory cable help with this?
Thanks for any help.
Click to expand...
Click to collapse
In Linux type lsusb and see if your device is shown. It my be named something weird.
Sent from my Amazon Kindle Fire using xda app-developers app
Did you have adb and fastboot setup on linux when you tried?
I'm pretty sure I did, I used the firekit and that didn't work as well. how do I check if adb and fastboot are for sure running when in linux?
powerpoint45 said:
In Linux type lsusb and see if your device is shown. It my be named something weird.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
when i lsusb, it just sees my usb stick i booted ubuntu from
Installing Amazon's stock update.zip gets rid of FFF and TWRP, so at this point, your only choices are either getting a factory cable (recommended) or cracking open the case and resorting to the USB short trick + firekit.
OK, I have an order for the Factory cable coming so hopefully that will do the trick. Thanks
Ok, so I had TWRP including FFF installed, as well as all the other features that comes with kindle fire utility, when I decided that I wanted to restore to stock firmware.
I placed the update.bin in kindleupdates folder on the Kindle itself, and launched TWRP Recovery to install the rom/firmware.
When it was done installing, I was such a nutjob not thinking, that I decided to also delete everything (system, sdcard, cache, dalvik-cache), as well as to tell it to restore to factory settings, where I immediately after told it to reboot. Totally dumb, I know it, so now it's stuck at the "original"/orange Kindle Fire-logo, and just hanging there (i'm able to turn it on/off though), hence it can't restore stock firmware since I deleted everything off the kindle after I installed that stock firmware. It doesn't even have TWRP anymore (boot options doesn't appear when turning the kindle on.)
I also tried to connect it to the USB-port on my PC, (already have drivers installed), but it just gives me the "badom"-sound implying that a USB has been connected, nothing else. I can't even access the Kindle as an external storage device anymore now.
HELP!
PS: I'm running Windows 7 x64!
Are you unable to reinstall FFF and TWRP?
Yes ):
soupmagnet said:
Are you unable to reinstall FFF and TWRP?
Click to expand...
Click to collapse
Yes because my PC won't even detect my Kindle now!
Fix your drivers.
Otherwise you can use SoupKit w/Linux Live USB to save yourself some hassle in getting ADB to connect. Either way, it's very likely your shell is missing or corrupt, requiring a factory cable to get into fastboot.
saiihtam said:
Yes because my PC won't even detect my Kindle now!
Click to expand...
Click to collapse
You said u heard the beep when u connect.. did u check it in the Device Manager..
You might see it under other devices or under USB devices?
If you are able to see it then you might have a chance
lol
saiihtam said:
Ok, so I had TWRP including FFF installed, as well as all the other features that comes with kindle fire utility, when I decided that I wanted to restore to stock firmware.
I placed the update.bin in kindleupdates folder on the Kindle itself, and launched TWRP Recovery to install the rom/firmware.
When it was done installing, I was such a nutjob not thinking, that I decided to also delete everything (system, sdcard, cache, dalvik-cache), as well as to tell it to restore to factory settings, where I immediately after told it to reboot. Totally dumb, I know it, so now it's stuck at the "original"/orange Kindle Fire-logo, and just hanging there (i'm able to turn it on/off though), hence it can't restore stock firmware since I deleted everything off the kindle after I installed that stock firmware. It doesn't even have TWRP anymore (boot options doesn't appear when turning the kindle on.)
I also tried to connect it to the USB-port on my PC, (already have drivers installed), but it just gives me the "badom"-sound implying that a USB has been connected, nothing else. I can't even access the Kindle as an external storage device anymore now.
HELP!
PS: I'm running Windows 7 x64!
Click to expand...
Click to collapse
lol this reminds me of someone..........(me)
http://forum.xda-developers.com/showthread.php?t=1888581 read
Sorry for double-post, I posted in wrong section, it's hard to define whether this is really a quesiton, but here goes:
Ok, so I had TWRP including FFF installed, as well as all the other features that comes with kindle fire utility, when I decided that I wanted to restore to stock firmware.
I placed the update.bin in kindleupdates folder on the Kindle itself, and launched TWRP Recovery to install the rom/firmware.
When it was done installing, I was such a nutjob not thinking, that I decided to also delete everything (system, sdcard, cache, dalvik-cache), as well as to tell it to restore to factory settings, where I immediately after told it to reboot. Totally dumb, I know it, so now it's stuck at the "original"/orange Kindle Fire-logo, and just hanging there (i'm able to turn it on/off though), hence it can't restore stock firmware since I deleted everything off the kindle after I installed that stock firmware. It doesn't even have TWRP anymore (boot options doesn't appear when turning the kindle on.)
I also tried to connect it to the USB-port on my PC, (already have drivers installed), but it just gives me the "badom"-sound implying that a USB has been connected, nothing else. I can't even access the Kindle as an external storage device anymore now.
HELP!
PS: I'm running Windows 7 x64!
You need a factory cable...
http://forum.xda-developers.com/showthread.php?t=1668159
Jus check if our kindle is coming up under the USB devices as a composite USB device..if so uninstall the driver and reconnect the kindle..
It shd get detected under other devices..install the drivers manually by clicking dont install and use have disk and get it detected as a android phone or android composite interface..
If that works u can use adb commands and try..this might help u recover or kindle
Sent from my MB526 using Tapatalk 2
Hey I'm a brand new member so I apologize in advance if my problem has been solved already, however, I could not find anything on any of the threads. Okay so I am severely confused right now. I have had my Kindle Fire for almost a year now and this problem has never occurred. Ever since I got my Kindle I have been experimenting on it. I rooted it and have flashed many different custom roms. I had been using TWRP Recovery 2.0 for a long time and when I found out that it was outdated I updated it to the new 2.2.1.1 version...Everything seemed to be working perfectly until I tried mounting USB storage in the new TWRP...It did not work. My computer wouldn't recognize it. I kind of just let this slide since I figured I wouldn't need to mount USB storage in TWRP unless it was an emergency. A while later I switched back to the Kindle's stock rom. That's when I noticed that it would not mount...Not only was TWRP not mounting, but it was my Kindle altogether. I deleted all drivers that had any thing to do with Android from my computer. After restarting both my computer and my Kindle I tried mounting again...Nothing. The drivers weren't even reinstalling. To test wether this was a problem with my computer or my Kindle I got my brother's Kindle Fire (Never had any tweaking done to it) and mounted USB storage. It installed the drivers and mounted just fine. I then plugged my Kindle back in and it mounted just fine also. I thought I had solved the issue, but about an hour later I tried mounting my Kindle again and nothing happened. My brother's Kindle will mount (Actually there are a total of four Kindles in my house all of which have not been tweaked except for mine) but mine won't do anything. As a last resort I deleted EVERYTHING with TWRP and flashed the Kindle Fire 6.3.1 update.zip. My Kindle is now true factory default (no root, custom recovery, etc...). I thougt for sure this would work but IT STILL WON'T MOUNT USB STORAGE!!! When I plug my Kindle in and go to "Devices and Printers" it recognizes my device as a "Kindle" but I just cannot get it to mount! I am now stuck with a Kindle that cannot be re-rooted or anything due to the fact that it cannot be recognized with ADB. Sorry for the long post...I am just trying to give as much information as possible. By the way I am running Windows 7 and my Kindle is the only one that will not mount which makes this problem have nothing to do with drivers or my computer. Any help is appreciated. Thanks.
Wheww okay well try a factory reset this will wipe your sdcard as well. It should resolve most your problems. There are multiple things that can cause this to happen but one thing that really comes to mind. Are you ejecting your kindle before hitting the disconnect button? Just a wild guess but failing to do so can cause this disorder the very next time you plug it in. Something that could resolve minor sdcard issues is
Code:
fastboot oem format
don't let this make you to crazy yet RC soupmagnet should be releasing something very soon that will solve the majority of SD card mount problems hint hint . You will need to reroot and flash a custom ROM on it to have success though. So if nothing works hang tight and stay tuned.
This might help
http://forum.xda-developers.com/showthread.php?p=33109015#post33109015
Thepooch, no I had not been ejecting it before disconnecting. I'll do that from now on. Also commands do not work because my computer doesn't recognize my Kindle as either a storage device or an ADB device, and what does it mean what it says "fastboot not found"? I made sure I have the fastboot.exe in my ADB folder...Soupmagnet, I can't get those commands to work since I'm no longer rooted and my computer doesn't recognize me...
Nihilian said:
Thepooch, no I had not been ejecting it before disconnecting. I'll do that from now on. Also commands do not work because my computer doesn't recognize my Kindle as either a storage device or an ADB device, and what does it mean what it says "fastboot not found"? I made sure I have the fastboot.exe in my ADB folder...Soupmagnet, I can't get those commands to work since I'm no longer rooted and my computer doesn't recognize me...
Click to expand...
Click to collapse
Have you installed your adb drivers?
soupmagnet said:
Have you installed your adb drivers?
Click to expand...
Click to collapse
Yeah I downloaded the newest Kindle Fire Utility and installed thoose drivers. When I plug my Kindle in and go to "Device Manager" it lists it as an android phone with ADB Interface. If I plug any other Kindle in then it installs new drivers and doesn't list the ADB Interface. Is this normal?
Nihilian said:
Yeah I downloaded the newest Kindle Fire Utility and installed thoose drivers. When I plug my Kindle in and go to "Device Manager" it lists it as an android phone with ADB Interface. If I plug any other Kindle in then it installs new drivers and doesn't list the ADB Interface. Is this normal?
Click to expand...
Click to collapse
I don't use Windows so I couldn't tell what's normal for that OS.
Use the tutorial here to confirm your drivers are installed properly. Then Shift + right-click on your KFU "tools" folder with adb.exe and fastboot.exe, and select "Open command window here". Enter your adb or fastboot commands there and see how it goes. Start with "adb devices" to see if you are connected. If not, reinstall your drivers and try again.
Some ROMs have different product IDs than the stock OS so you may want to look into that if you are using a custom ROM, and edit your androidwinusb.inf accordingly. I know some JB roms have a PID of 0004 instead of 0006.
If for some reason Windows refuses to cooperate, you could always set up a Linux LiveUSB and get it done a lot easier.
Okay so I've been fiddling around with stuff. I completely uninstalled all Android drivers again then restarted my PC and Kindle. This time I plugged my Kindle in and it installed the correct drivers. It mounted USB just fine. When I tried reinstalling the ADB drivers that came with Kindle Fire Utility it erased the Kindle's normal drivers, so now it won't mount anymore...at least I know that it is a driver problem and that my Kindle doesn't need to be repartitioned. I'm really getting sick of Windows and its annoying drivers...Any ideas on how to get all the drivers to work? If not I think I might just install Ubuntu and screw the need for drivers.
Sent from my M886 using xda app-developers app
If you run the driver bat packaged with kfu with the device plugged in sometimes it will waste the mass storage drivers. It`s always best to run it then plug the device in and see what windows decides to install. Unplug, replug, unplug, replug as well as try this while in recovery because it will also attempt to install the drivers as well in recovery.
Thepooch said:
If you run the driver bat packaged with kfu with the device plugged in sometimes it will waste the mass storage drivers. It`s always best to run it then plug the device in and see what windows decides to install. Unplug, replug, unplug, replug as well as try this while in recovery because it will also attempt to install the drivers as well in recovery.
Click to expand...
Click to collapse
Sweet. I tried it and now everything is working perfectly. Thanks for your help guys.
Nihilian said:
Sweet. I tried it and now everything is working perfectly. Thanks for your help guys.
Click to expand...
Click to collapse
I downloaded the lates kindle fire utility and I enabled debugging, I can see my files but when I run the utility file the adb says offline. I cannot figure it out. : (
So, I tried searching for days on how to fix my problem.
A little while ago I rooted my Kindle Fire, and it was great. Then I did something. Not sure exactly what. But It ended up just doing nothing. When I boot up the Kindle it shows the blue and white Kindle Fire logo. Nothing else past that (unless I go to recovery.) Now, my computer doesnt recognize it anymore, even after doing most of the driver updates that people on here have said to do.
I need help, basically, getting it back to normal, so I can give rooting a try again. Now that I know what exactly I am dealing with, I can do this and not screw everything up.
First, the computer says the driver is installed, yet it doesnt recognize it.
Second, (before the driver mishap) KFU said it was connected but the adb was unknown.
Third, I have CWM and I tried to flash the normal Amazon update to bring it back, and it says"it cant open it (bad)".
Now, I would really like some help with this. I'm just at a complete lost.
Now should I put that into command prompt in the adb part? because it just says fastboot is not recognized.
Yes, It wont do that, it just says error: device not found. also says 'fastboot' is not recognized.
Now its just not connecting to the computer. I installed Android sdk and everything and its just not working. It says the driver is installed but there was an error because a problem had occurred. Any help? :crying:
As soon as you get tired messing with drivers you can move on to something that works http://forum.xda-developers.com/showthread.php?t=1850038
ManofFishFry said:
Yes, It wont do that, it just says error: device not found. also says 'fastboot' is not recognized.
Click to expand...
Click to collapse
I hope u r on windows PC..
first after u set up adb, make sure u install adb drivers that came with kindle fire utility with ur kindle fire unplugged..if u had plugged in kindle fire while doing that, go to device manager and uninstall that device and its driver software and start up from beginning..
keep kf unplugged and install driver..u dont get usb debugging option in stock kf rom..its enabled if u have installed the drivers properly..ur kindle fire appears as android phone in device manager if everything u hav done is correct..
then boot up ur kf..that blue and white kf logo is of firefirefire bootloader..i hope its v1.4a and u see it on right top of the screen..if its stuck there then open command prompt as administrator on ur pc..connect ur kf to pc..type in to cmd
Code:
fastboot devices
if u see something under list of devices attached that will be ur kindle fire(unless some other android device is connected in fastboot mode lol)
Because kindle fire, as far as i know, can only boot into 3 bootmodes(normal, recovery, fastboot) unless u have altered the partition table to install different roms and multiboot ur kindle fire..
if fastboot command is not recognized, try setting the path to where fastboot.exe is present in KFU folder
alternatively u can go to folder where fastboot.exe is located and right click while holding shift and selecting 'open command window here' and fastboot needs to firefirefire bootloader to be installed on ur kindle fire..
also u can try this..
JUST GO TO RECOVERY..twrp has always been a better recovery software than cwm based thing available for kindle fire at least for me..if u go to recovery, ur kf will definitely show up as an adb device..u can change the bootmode using this..just type in:
Code:
adb devices
if ur kf is seen as in recovery then type this in cmd
Code:
idme bootmode 4000
reboot
just report if this worked..
okay well, I deleted all the drivers and started from the beginning. Yet, after running the install_driver.bat I plugged my Kindle in and it still says device not recognized. Now, you how can get adb working? It is coming up as unknown device. Its just seeming like theres something wrong on the kindle part. But hey, what do I know. haha
lol try what will work http://forum.xda-developers.com/showthread.php?t=1850038
But doesn't that require linux? I have windows 7. Is there something like that for windows?
Thepooch said:
lol try what will work http://forum.xda-developers.com/showthread.php?t=1850038
Click to expand...
Click to collapse
Hi i have the same problem but the only thing is that my device is actually verified by the coputer and can connect via usb mount but when i try to install a ROM it says unable to mount and cannot install rom but i see there is something for fixing mounting problems there in soupkit so i'll give it a try.
This is what I get when I try to install the driver....
To run soupkit all you need is at least a 2 gig usb flash drive ubuntu 12.04 32 bit and universal usb creator. By the way your problem with the driver is you (or how you`re going about it), You would trip if I got on your computer and got it to work or could at least tell you why its not working. that`s why I suggested soupkit if you would of actually read the information I gave you, I wouldn`t have had to tell you twice and you would know that to use it it`s not required to be installed on your computer. But hey catch me online I can either help you fight through windows crappy drivers or help you set up soupkit I`m always game for a challenge When updating the driver you need to point it to the 32 bit version of the driver for instance on my computer it`s located here C:\Documents and Settings\HP_Administrator\Desktop\Kindle_Fire_Utility_v0.9.6\Kindle Fire Utility\drivers. After it`s ran unplug and replug device if that doesn`t work power off and power on while connected this generally does the trick when windows finally catches on it will install android adb interface, this is the fastboot driver (if you`re stuck in fastboot). Then select option 1 in KFU for changing bootmodes, then option 1 for normal if it does nothing power off and power on while connected it should then detect the kindle and reset the bootmode to normal. Pm me later I will be online all evening and most every evening I will help you sort it out.
Josepho1997 said:
Whoops! Somehow my post was posted twice. I didn't even get to see your reply. Sorry!
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
this is what I get when I try this... (btw im working with firefirefire. its got the blue and white kindle fire.)
Why don't you let me take a look?
Dark__king said:
Hi i have the same problem but the only thing is that my device is actually verified by the coputer and can connect via usb mount but when i try to install a ROM it says unable to mount and cannot install rom but i see there is something for fixing mounting problems there in soupkit so i'll give it a try.
Click to expand...
Click to collapse
Yes soupkit can fix mounting problems.
This is a very interesting issue with this Kindle windows detects it as unknown usb device, drivers are installed properly from what I can see. Ubuntu with soupkit ran on it fails to detect it in recovery or fastboot. multiple cables tried, lsusb doesn`t show the device connected. I really think this one the computer is the problem, because it`s the only unchanged variable.
Firekit may be the only option if Linux won't detect the device. Before doing that, make sure a USB 3.0 port isn't being used and try a fresh install of Linux to be safe. Otherwise, it seems putting it in USBboot is the only option for getting Linux to detect.
I'm not exactly sure what causes the unknown device error, but it almost always means there is something wrong with the bootloader, and it seems as though Windows might be the main culprit. Not sure why exactly, but it may be similar to the problem soulweeper51 had. Possibly a hardware issue involving the computer's USB port or the motherboard itself.
@ManoFishFry has doomlords cwm recovery and he flashed JB at first I thought it was an issue with cwm not being detected but the fact that it`s not detected in fastboot raised my eyebrows. The bootloader appears to be functional but I cannot rule out any minor state of being broken in another fashion when lsusb returns null. The computer doing the work had never been used prior to the incident so driver install didn`t take place till after the fact. The usb ports are all either 1.0 or 2.0 no 3.0 ports are being used. An alternate computer would be nice to rule out the computer itself @ManoFishFry only has a dinosour of an xp machine as alternate use of is not possible yet, not that it would even be possible to install drivers because of the typical unsigned driver failure of xp and booting ubuntu isn`t happening at the moment on this machine.
I'm willing to bet it is the bootloader.
Just USBboot and get it over with.
We did try usb boot once but it didn`t work will keep trying.