Develop Bugs

[Q] Yellow triangle, not charge, not switch off, not recognised by win7

Hello,
Apology has to make a new thread, but I went through many and didnt get my problem fixed
I rooted my fire, installed CM7 and used for quite sometime it all went well. But recently I have left it unused for about a couple of weeks, when I picked it up again, the battery is totally discharged, and I put it to the charger, it can never boot.
Whenever I connect fire to a charger (tried both wall and PC), it shows the yellow triangle for 2 sec then switch off, and automatedly restart again to the triangle, then off again... I cannot get it switch off or 20sec reset as the power button is not responding, off the charger, it switched off immediately. And it cannot be recognised by win7 32bit
I have tried:
1. Newest KFU, set to boot normal --> "waiting for device", cannot switch off by pressing 20sec power button, so cannot get it to fastboot
To clarify, I am sure I have driver installed correctly since I used KFU early on to root the fire. There is nothing in windows device manage when i plugged in fire.
2. Left it charge for overnight , tried both kindle fire wall charger and ipad charger (output 5v 2.1Amp), didnt charge the battery.
Now I am running out of ideas, is my fire really dead?
Any help will be much appreciated.

http://forum.xda-developers.com/showthread.php?t=1392693&page=25
read from post #226 to #246
maybe this one as a last resort:
http://forum.xda-developers.com/showthread.php?t=1405052

Thanks mate, I will try to find a factory cable and try that.

zhenmutou said:
Thanks mate, I will try to find a factory cable and try that.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1550999

Ordered one from China, takes a couple of months for shipping to Europe. When I am waiting, I am wondering if I take the battery off the fire, is there any device can charge the battery directly?

Why not get a micro usb cable and a 100Ω resistor and have one made for yourself? only needs 1 solder, i'd expect any electronics repair shop could do it for you if you could explain to him what you wanted. A mate at uni who is studying electronics did mine for me. At least give it a try, better than waiting months just to boot your kindle up. Hashcode is getting there on the new kernel, intresting times to have a (working ) kindle fire

Thanks, its a good point. Unfortunately I live in Denmark, such a job would normally costs at least 50euro. I am not confident enough for DIY, guess I better off waiting for my shipment

why did'nt order from http://forum.xda-developers.com/showpost.php?p=23049902&postcount=254
got mine in - don't remember exactly - 6 days i think

Another thought, if I put my battery to another working kindle fire to get it charged. Would that work?

maybe - never tried that - check it out if you have this option and report back

Possible Solution
First Download the Kindle Unbricking Utitlity, which is focused on Unbricking your kindle. There will be various options. For your problem, click Stuck at Logo. In addition you need Java to run the executable program
To get your computer to recognize the Kindle, Download the Kindle Fire Utitlity. Extract and navigate to the directory that includes three folders, and two batch files. There should be a batch file called "run". Open it and it will reinstall your drivers. If it doesnt work try for two more times.

thedeveloper1 said:
First Download the Kindle Unbricking Utitlity, which is focused on Unbricking your kindle. There will be various options. For your problem, click Stuck at Logo. In addition you need Java to run the executable program
To get your computer to recognize the Kindle, Download the Kindle Fire Utitlity. Extract and navigate to the directory that includes three folders, and two batch files. There should be a batch file called "run". Open it and it will reinstall your drivers. If it doesnt work try for two more times.
Click to expand...
Click to collapse
Thanks, but it didnt work. clicked Stuck at logo, it brought up a cmd window with device not found error

does your usb power turn on kindle with triangle?
Sent from my Kindle Fire using xda premium

Yes, it does. And unplug the usb, kindle switch off immediately

[Question] Kindle Fire is possibly dead.

Guys,
Details: Using Windows 7 64 bits, on a notebook.
Here is the full history of my brand new brick... call me stupid.
Second day with my Kindle Fire, I tryed to root my kindle fire.
Downloaded the KFU 0.9.5, instaled the drivers.
But the KFU wasn't workig... I only was getting the ADB offline status and the "waiting for device" message.
When I realized that the drivers I had were from my Motorola Milestone.
Next step: Uninstall the wrong drivers, and reinstall the new ones.
Only with this i could get the device to work with KFU.
Open the Run application at KFU folder.
Choosed option 2: Install Permanent Root with Superuser.
All worked fine until i get the message "with great powers come great responsabilityies" press any key to continue...
[EDIT: Tried to install Gapps extras... I don't remember if Kindle was dead before this or after]
The Kindle rebooted, got to the screen with the "kindle" word, and died.
Since that I'm getting no power on, no led lights, no response when connected to usb... nothing.
What should I do?
Go to Motorola Tech Support (here in my city) and try to use a factory cable?
or
I can only put my hopes on USB Boot Mode?
Guys, thanks in advance and sorry for my english, I certainly made some msitakes.
Or I can try Firekit?

That's strange, installing the wrong device drivers on your computer shouldn't affect your Kindle.
What it really sounds like is your battery died in the process of installing the FFF bootloader. How was your battery before you started? Have you tried holding the power button for 20 seconds for a hard shutdown?
As far as I know, the only thing that will cause power on issues is a broken bootloader. In which case, USB boot with firekit is your only option.

I guess I had at least 50% o battery charge, or more... I can't remember...
If I push the power button now, the Kindle will get warm, as if it was in use. And if I hold for 20s, will shut down...
I don't even started to install de fire fire fire bootloader, I installed the permanent root with super user and then went to install GApps. I guess my kindle was shutdown before Gapps install.
What should I do? Test the factory cable first?
When you say that I have to use Firekit, you are saying that I have to open my Kindle?

Left the Fire charging for at least 12 hours.
Tried to power on, to hold 20s and nothing happened.
I'll gonna try this:
Fix power on problems: If the Fire's screen never seems to turn on, you may have wrecked the bootloaders or the partitioning. Fortunately most of the time this results in the CPU falling into the low level USB boot mode. Use the "usb_fix_parts_and_install_fff_twrp" to rebuild the flash enough to boot TWRP. You don't need to use the USB shorting trick for this one, just power up the Kindle after running the script.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1430038
My question is: I'm running Ubuntu within VMWare tools. Can I boot from usb stick this way?
Gonna try this before I use factory cable or open my Kindle Fire.
EDIT:
Reading the FIREKIT Topic, this post: http://forum.xda-developers.com/showpost.php?p=25814062&postcount=26
My issue is kind of different from his... I'm guessing I'll have to open my Kindle anyway... Started yesterday, but I was messing with the case, gonna find some proper tools

VMs will not work. You have to create a bootable Linux LiveUSB thumb drive.

DuendePaladino said:
Left the Fire charging for at least 12 hours.
Tried to power on, to hold 20s and nothing happened.
I'll gonna try this:
http://forum.xda-developers.com/showthread.php?t=1430038
My question is: I'm running Ubuntu within VMWare tools. Can I boot from usb stick this way?
Gonna try this before I use factory cable or open my Kindle Fire.
Click to expand...
Click to collapse
If you already have a working Ubuntu installation, you don't have to make the USB stick. You can just run the fk binary in your Ubuntu setup.

kinfauns said:
If you already have a working Ubuntu installation, you don't have to make the USB stick. You can just run the fk binary in your Ubuntu setup.
Click to expand...
Click to collapse
I've tried it on a VM and had it confirmed by other users that VMs aren't fast enough to detect the USB in time. From what I've seen, it has always been suggested to either use either a straight Linux install or a bootable LiveUSB.

soupmagnet said:
I've tried it on a VM and had it confirmed by other users that VMs aren't fast enough to detect the USB in time. From what I've seen, it has always been suggested to either use either a straight Linux install or a bootable LiveUSB.
Click to expand...
Click to collapse
I guess it might depend on the VM, but I disagree with the generalization that VMs are too slow and have issues with USB.
The only thing I've seen is that Oracle's VirtualBox USB implementation breaks adb. I've never tried VMWare, but Parallels Desktop for both my Ubuntu and Windows setups work perfectly. Never had an issue.

DuendePaladino said:
What should I do? Test the factory cable first?
Click to expand...
Click to collapse
Anybody who is going to be modifying the basic software of their Kindle, or even just root it and play around, should have a factory cable. Xda member SkOrPn makes good ones at a reasonable price and ships them quickly. See http://forum.xda-developers.com/showpost.php?p=25725396&postcount=338.
(From what you wrote earlier, I presume that you don't yet have convenient access to a factory cable but would have to go out of your way to use one. If you do, in fact, have easy access to one, I can't imagine why you wouldn't try using it instead of putting a lot of effort into looking for alternatives.)

aarons510 said:
Anybody who is going to be modifying the basic software of their Kindle, or even just root it and play around, should have a factory cable. Xda member SkOrPn makes good ones at a reasonable price and ships them quickly. See http://forum.xda-developers.com/showpost.php?p=25725396&postcount=338.
(From what you wrote earlier, I presume that you don't yet have convenient access to a factory cable but would have to go out of your way to use one. If you do, in fact, have easy access to one, I can't imagine why you wouldn't try using it instead of putting a lot of effort into looking for alternatives.)
Click to expand...
Click to collapse
Without a working bootloader, a factory cable is useless.

soupmagnet said:
Without a working bootloader, a factory cable is useless.
Click to expand...
Click to collapse
All the scene leads to this... USB Boot.
About the USB stick, I was making some confusion about it.
But, I´ll gonna make one stick right now.

Guys,
I made the usb stick... just figuring how to open the kindle fire, without ruining the case.
But I guess today I'll made the short trick.
Question: I'll keep the 6.3 stock room that i tried to root? Or I'll have to download another ROM?

Is there any know issues about firekit compatibility with ubuntu 12.04?
Like this here? http://forum.xda-developers.com/showpost.php?p=25918331&postcount=10

I WON!!!!
I'M BEOWULF!!!!
Serious now...
Firekit method, with short trick... keep trying... until you find the right spot for the shor... and will work
EDIT:
THANK YOU GUYS!!!
I wouldnt be that happy without your help and your knowledge... You're the real Beowulf!

[Q] Stuck "Kindle Fire" Spash screen after unrooting

Hi,
My rooted KF started behaving, weirdly so I decided to start from scratch and unroot it using the ClockworkMod recovery utility interface that was automatically loaded when I rooted it using Breakdroid. It started life with 6.2.2 but then updated itself to 6.3, so I downloaded the following file to do the unroot, and converted it into a .zip file called update.zip.
//kindle-fire-updates.s3.amazon...1E_4019920.bin
and went into the ClockworkMod recovery utility mounted my KF, did a factory reset, then applies sdcard update.zip which appeared to perform sucessfully, however when I rebooted, it launched the Stock KF screen, no fire fire fire, and has since stayed there. Can anyone please help! Many thanks.

Does KFU recognize it? If it does you are good to go.

Hi,
Nope. I'm using a Mac, so I use Breakdroid, and it's not picking it up.

http://forum.xda-developers.com/showthread.php?t=1644970

soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=1644970
Click to expand...
Click to collapse
Keep up the good work soupmagnet!

Thanks soupmagnet,
I know it's the same question asked over and over again, I'll give it a shot and let you know if I sort it out. Appreciate your time.

All things point to a factory usb cable which I have ordered. Now I have to read books the old way...analogue!

nickvon said:
All things point to a factory usb cable which I have ordered. Now I have to read books the old way...analogue!
Click to expand...
Click to collapse
Actually a factory cable, while nice to have, doesn't seem necessary in your case. (Hint Read about the different bootmodes.

Hi again Soupmagnet,
So I eventually got hold of my factory cable which I ordered off Ebay from Hong Kong, so I plugged it in and hey presto, nothing happened. I'm still stuck on the Kindle Fire screen. I've been using a Mac and Breakdroid doesn't pick it up at all. I decided to see if a PC could pick it up using KFU, and it's still offline, although in My Computer I do see an external drive and device manager does call it Kindle. I have a feeling I am the 1% of bricked Kindle Fire users that have well and truly properly bricked their Kindle. Could it perhaps be the cable not in fact being a factory cable at all? I'm getting pretty desperate with this situation. Can you offer me advise.
Nickvon

Oh and further to my last I was changing boot modes but as it couldn't recognize the device, it was pointless.

nickvon said:
I have a feeling I am the 1% of bricked Kindle Fire users that have well and truly properly bricked their Kindle.
Click to expand...
Click to collapse
Take a breath, relax, and rest assured that you are more likely in the upper 90% range.
As I said before, the factory cable, while nice to have isn't usually required to fix most devices. All it does, is puts the device in fastboot mode and provides direct power to the device via usb in case of low or now power
Your problem is simply a matter of fixing your drivers so you can communicate with the device and change the bootmode.
[Edit:] It's been a while since this post was first started so I forgot you were using Mac instead of Windows.
Open your Terminal and enter the following:
Code:
cat ~/.android/adb_usb.ini
Your output should read:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
Anything other than would explain why you aren't able to change the bootmode normally.
Are you using Terminal commands to change the bootmode or are you using Breakdroid?

[Q] Bricked Kindle

I was given a "bricked" kindle to take a look at last week. Here is the story I was given.
User installed a custom rom, but it was for a lower version (didnt fully understand this)
Afterwards it locks on the kindle fire logo during boot.
User made a factory cable to restore the unit, and now anytime ANY usb is plugged into the device it shuts off immediately.
I tried opening the device and shorting the required pins, but plugging in the usb doesnt do anything. It appears to be charged, but I have no way of knowing.
It doesnt show as anything in device manager (it looks to be fully off)
Pressing the power button still gets it to start and hang at the kindle logo.
My guess is the factory cable was made incorrectly and shorted the usb board but I figured I would see what others thought.
Thanks

Any opinions?

I had this problem a couple times. I'm not 100% sure how to resolve the problem you're having but I will tell you what I did to solve mine, so you at least have some kind of help to try and fix the issue.
When I plugged it in, my computer wouldn't recognize my Kindle but I noticed it would show a new device in the USB Controller list, showing it as a USB Composite device. I went and deleted the OEM files that are created for Android devices from c:\windows\inf\ just to make sure the next process would have better success (Mine were labeled 64, 65 and 88). Then I simply selected the composite device option for my Kindle and hit Update Driver and selected the drivers folder that came with KFUtility. Once it was detected, I used the Unbrick utility found here -> http://forum.xda-developers.com/showthread.php?t=1428428
After rebooting it worked like a charm.
I realize this may not work for you, but it is at least something worth trying because you never know.

narume said:
I had this problem a couple times. I'm not 100% sure how to resolve the problem you're having but I will tell you what I did to solve mine, so you at least have some kind of help to try and fix the issue.
When I plugged it in, my computer wouldn't recognize my Kindle but I noticed it would show a new device in the USB Controller list, showing it as a USB Composite device. I went and deleted the OEM files that are created for Android devices from c:\windows\inf\ just to make sure the next process would have better success (Mine were labeled 64, 65 and 88). Then I simply selected the composite device option for my Kindle and hit Update Driver and selected the drivers folder that came with KFUtility. Once it was detected, I used the Unbrick utility found here -> http://forum.xda-developers.com/showthread.php?t=1428428
After rebooting it worked like a charm.
I realize this may not work for you, but it is at least something worth trying because you never know.
Click to expand...
Click to collapse
Thanks for the thought, but nothing shows in device manager. I believe this is due to the kindle shutting off the second you plug any usb into it.

bump?

The shutting off thing doesn't sound inherent of a properly made factory cable the rest of it points directly to drivers IMO as far as your device not being recognized I can show you how to rule out the driver issue out of the equation lemme know

Thepooch said:
The shutting off thing doesn't sound inherent of a properly made factory cable the rest of it points directly to drivers IMO as far as your device not being recognized I can show you how to rule out the driver issue out of the equation lemme know
Click to expand...
Click to collapse
I'll definitely try the factory cable again (the user tried this, but who knows)
But as far as the device not being recognized... Like I said, the second you plug it into usb (either computer, or power plug) it shuts off.
Its not that I get a windows notification for "not recognized" windows doesnt see it period.

it should not turn your device off it should appear stuck at the logo like I said sounds like a bad build guess you misunderstood
---------- Post added at 06:45 PM ---------- Previous post was at 06:38 PM ----------
only use a 2.0 usb port and try it from the device in an off position

[Q] KF2 Empty and not recognized on windows

So I was trying to change my son's Fire 2 over to the new Kit Kat OS, and as I was downloading the necessary files to my computer, I thought I would wipe everything, since he had managed to pretty much fill it with junk, (he's 8). I have TWRP, (2.3.3.0) installed, and used that to wipe everything, including the internal storage and the format data wipe. I have done this with my Fire 1 with no issues, but this time I ran into a problem. TWRP works fine, but now windows won't recognize the tablet. When I go to mount the usb storage to copy the os files over, windows 7 cant load the device drives, and in my device manager it shows the Amazon Kindle fire 2 with the yellow exclamation mark next to it, saying that the drivers for this device are not installed. I have the SDK installed, and I have gone through and re installed the device drivers several times, and also uninstalled the kindle from the device list in manager. Nothing is working. I have attempted fastboot, but when I do try, it gets stuck at the "press the button menu" for TWRP, and after running the fastboot -i 0x1949 getvar product command, it tells me it sees an Otter2-Prod-04.
Does anybody have any ideas or suggestions on how I can get into the usb storage so I can load the OS info? Thanks for any help.

Dead?
Well, I rebooted from TWRP and it just went black. No light when the cable is plugged in, (factory cable), no twenty second reset working, nothing. IS it safe to assume I now have a pretty paperweight, and I should be looking into getting my son another tablet?

xanthian23 said:
Well, I rebooted from TWRP and it just went black. No light when the cable is plugged in, (factory cable), no twenty second reset working, nothing. IS it safe to assume I now have a pretty paperweight, and I should be looking into getting my son another tablet?
Click to expand...
Click to collapse
Leave it on the charger overnight. Keep trying 20 second reboot. If you can get back into recovery you can adb sideload a rom into the device.
You've never been able to USB Mount this device from recovery.
Good luck. No reason it should be bricked....
How did you try to get into fast boot? You need a fastboot cable. This device is NOTHING LIKE the kf1.
Edit: also need to be sure exactly which kf2 you have.
--》Sent from my mind to your screen

mindmajick said:
Leave it on the charger overnight. Keep trying 20 second reboot. If you can get back into recovery you can adb sideload a rom into the device.
You've never been able to USB Mount this device from recovery.
Good luck. No reason it should be bricked....
How did you try to get into fast boot? You need a fastboot cable. This device is NOTHING LIKE the kf1.
Edit: also need to be sure exactly which kf2 you have.
--》Sent from my mind to your screen
Click to expand...
Click to collapse
I have the standard cheap Kf2, no HD, just the upgrade from the first from last year, (2012), they were selling around Christmas last year. I have tried getting it to start back up, but with no success. I don't even understand why it shut down like that. I hadn't done anything to it other than reboot, which I had done successfully several times before. As for the fastboot, I may be incorrect. I ran the adb command: fastboot -i 0x1949 getvar product in CMD, and then plugged the kindle in and booted up. It showed it was an otter4 or something like that, which I thought meant it was in fastboot. At that time I was using my S4 usb cable. I'm sure I can sort out ho to sideload a rom via adb if I can ever get it started back up again. I had thought about opening it up and unplugging the battery and then re-plugging it back it to try to reset it, but I doubt it will help. Would getting a fastboot cable possibly make it start back up? If anyone has any suggestions on how I can get this thing started up again I would greatly appreciate it. I fell like crap for bricking my kids kindle, he's 8, so it's really important to him. It'll take me several months to save up to buy another one, so if I can get it running again, that would be awesome.

Here's a bit of an oddity, and maybe this spells some hope for me yet. So I plug the KF2 into the computer with the factory cable, hold down the power button for twenty seconds, let go, and then hit the power button again, for about a second, and windows makes the usb device plugged in sound, followed by a usb rejected or not recognized sound. It repeats this over and over for about thirty seconds or so and then stops. So there is something going on with the kindle, and its not flat out dead, or at least it seems. Is this a good sign? Does this help anyone to figure out what I might need to do?

So just to be sure that I was using a fastboot cable, even though I believe that my samsung s4 cable is fastboot capable, and I'm pretty sure I am using the factory cable, (it's not marked so I can't be 100% sure), I built my own fastboot cable, via instructions on how to do so on xda. (found HERE) It's doing the same thing with windows making the usb device inserted / recognized sound, followed by the usb device error sound. I'm guessing that this is a bad thing, am I correct?

One more bit of information to add to the list. I attempted to do the fastboot mode again,and decided to watch my device manager. Whenever windows chimes off that it detects a usb device, something called OMAP 4430 pops up for about a second before disappearing when the error sound comes on. I'm going to try and get a driver for that, just to see what happens. Maybe it'll help. I doubt it, but you never know until you try...

This just keeps getting weirder and weirder. So I installed the omap driver for windows and android, and now windows recognizes the device, but only for about a second. It just keeps cycling through the usb connected sound, recognizing the omap device, and then the usb disconnected sound, as though the device were being plugged in and then unplugged about every second for roughly thirty seconds. I'm starting to think there is something seriously wrong, which bites. If anyone has any suggestions, I'm all ears.

That's a hard brick' we can't use the usboot/aboot utility to fix the device like you can on other omap devices because we need a certain signed file to fix the boot loader. Only amazon has that file and they aren't giving it out. There is a way to recover your device from a hard brick but you need to be good with a soldering iron and have a USB sdcard reader, the kind that kinda is like a flashdrive rather than the multi type readers and some really small wire. Kurohyou wrote a tutorial on how to fix it in the kf2 dev section, not sure if he ever added the part in on how to reflash the boot loader from Linux, but if you take this route and try to fix it I wouldn't mind helping.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
That's a hard brick' we can't use the usboot/aboot utility to fix the device like you can on other omap devices because we need a certain signed file to fix the boot loader. Only amazon has that file and they aren't giving it out. There is a way to recover your device from a hard brick but you need to be good with a soldering iron and have a USB sdcard reader, the kind that kinda is like a flashdrive rather than the multi type readers and some really small wire. Kurohyou wrote a tutorial on how to fix it in the kf2 dev section, not sure if he ever added the part in on how to reflash the boot loader from Linux, but if you take this route and try to fix it I wouldn't mind helping.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
OK, I have both a tf - micro sd card usb card reader, and a full sd card usb card reader. I'll have to go digging for them in the morning, but I think I can find them. I'm also really good with a soldering iron, (used to be a vcr / tv repair technician), It took me roughly two minutes to do the homemade factory cable. So I am game, especially since at this point I really have nothing to loose by trying. Would you mind posting a link to where the tutorial is? I'm going to go looking for it, but just in case I can't find it, a link would help. And thank you so much for this suggestion!

OK, I found the tutorial on how to wire everything up and what's needed. I'll have to go get some small wire and a better tip for my iron, but aside form that, the wiring and soldering seems simple enough. My problem is going to be dealing with linux. I know Windows backwards and forwards, but I have a pretty limited knowledge of linux, aside from a few things we did in school to cover general PC repair. I can get it up an running, which I will do tomorrow, but I may need some help sorting out what to do with it once I have the board lined up and ready to roll, which will have to wait till next week when I get back from a work trip. Do you know if kurohyou offers repairs? If it's not too expensive, I would be willing to pay for the fix.

He might repair it, he just made a solderless repair tool to repair them. But like I said I'm more than willing to help with the Linux side, I'm a PC tech myself and use Linux primarily, you can basically burn an ubuntu live CD or put it on a USB stick and boot into the entire os without having to install it, from there's its as simple as plugging the device into the PC, and seeing what device path it assigned to the kindle's emmc, and running a dd command to flash the boot loader back onto the device.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
... you can basically burn an ubuntu live CD or put it on a USB stick and boot into the entire os without having to install it, from there's its as simple as plugging the device into the PC, and seeing what device path it assigned to the kindle's emmc, and running a dd command to flash the boot loader back onto the device.
Click to expand...
Click to collapse
Yeah, I've ran a live usb version of unbuntu a few times, and in the past I have had the full version on my system, but I rarely ever used it, so I got rid of it. I have an extra 600 gig's of space just sitting around on my laptop, so I will install a full version, and get off my lazy rear and start learning linux. This should be a good first lesson. I can't do any of this until next week though, so I will be pm'ing you once I've gotten everythig hooked up and ready to go. Thanks again for the help.
I had a question about the repair though. I went through the discussion, and I may have just missed it, but did he ever figure out how to get the OS up and running? From what I could tell, he was still working on it, and hadn't managed to get a working rom loaded. I probably just either missed it, or didn't understand one of the post's.