Related
There are allot of bricks on this device. But this one is kinda hard to figure out. Anyway....Ive flashed some things on my kindle fire before but this time i tried to flash honeycomb meant for the galaxy tab. YES i know it is crazy. But i just like honeycomb better than ICS. So then i rebooted and it didnt work but then i wiped the system and flashed it again. Reboot and it will not boot up or show a charging light. I tried kindle fire unbrick 1.1 and the utility and the kindle fire utility 0.9.3 and tried to boot into recovery. DID NOT WORK. PLEASE HELP!
Beeyoth said:
There are allot of bricks on this device. But this one is kinda hard to figure out. Anyway....Ive flashed some things on my kindle fire before but this time i tried to flash honeycomb meant for the galaxy tab. YES i know it is crazy. But i just like honeycomb better than ICS. So then i rebooted and it didnt work but then i wiped the system and flashed it again. Reboot and it will not boot up or show a charging light. I tried kindle fire unbrick 1.1 and the utility and the kindle fire utility 0.9.3 and tried to boot into recovery. DID NOT WORK. PLEASE HELP!
Click to expand...
Click to collapse
Well if your PC regonizes it try reinstalling TWRP.. then boot into recovery and flash a new Rom...
fiddlefaddle said:
Well if your PC regonizes it try reinstalling TWRP.. then boot into recovery and flash a new Rom...
Click to expand...
Click to collapse
it does not recognize it
Beeyoth said:
it does not recognize it
Click to expand...
Click to collapse
Not even KFU? Try reinstalling your drivers.. if that does not work I cannot help you..
fiddlefaddle said:
Not even KFU? Try reinstalling your drivers.. if that does not work I cannot help you..
Click to expand...
Click to collapse
the drivers will install but kfu will not recognize it
Kindle fire Utility should work even without being recognized (well it did for me after turning on and off 3 times).
Does the device at least get's the firefirefire logo? If so, this is what I did
-Turn your kindle off by holding the power button down for at most 20 seconds.
-Plug kindle into your computer
-Run the unbrick utility
-Turn kindle on
-Wait for the Caution Sign with the fire logo (firefirefire logo)
-Choose first option on utility (Recovery Loop)
-Wait... (a max of 10 minutes)
This should work, if not, try to turn off your kindle on and off, and then try again.
==========================================
Well, if that doesn't work, I know there's someone is working on "factory cables" which (I think) should fix this problems.
Wish I could be more help.
zane203 said:
Kindle fire Utility should work even without being recognized (well it did for me after turning on and off 3 times).
Does the device at least get's the firefirefire logo? If so, this is what I did
-Turn your kindle off by holding the power button down for at most 20 seconds.
-Plug kindle into your computer
-Run the unbrick utility
-Turn kindle on
-Wait for the Caution Sign with the fire logo (firefirefire logo)
-Choose first option on utility (Recovery Loop)
-Wait... (a max of 10 minutes)
This should work, if not, try to turn off your kindle on and off, and then try again.
==========================================
Well, if that doesn't work, I know there's someone is working on "factory cables" which (I think) should fix this problems.
Wish I could be more help.
Click to expand...
Click to collapse
didnt work
try to use mount
in twrp, select mount, then ull see it on your computer
maybe try this one:
http://forum.xda-developers.com/showthread.php?t=1430038
b63 said:
maybe try this one:
http://forum.xda-developers.com/showthread.php?t=1430038
Click to expand...
Click to collapse
is there a way to not make a factory cable?
Beeyoth said:
is there a way to not make a factory cable?
Click to expand...
Click to collapse
...did you actually read the thread b63 linked you to?
Dasanko said:
...did you actually read the thread b63 linked you to?
Click to expand...
Click to collapse
yeah....sorry but please someone help!
Beeyoth said:
yeah....sorry but please someone help!
Click to expand...
Click to collapse
can i call you Rip, or you prefer Mr Van Winkle?
if adb is not working you still may have fastboot.
try powering kf off type "fastboot devices" into a command line. (open prompt in folder where you have fastboot installed on pc) it should say waiting for device.
then plugin kf to usb cable and power on if you've got fastboot it's easy, if you haven't it's a factory cable or a door wedge
Sent from my Galaxy Nexus using xda premium
lovejoy777 said:
if adb is not working you still may have fastboot.
try powering kf off type "fastboot devices" into a command line. (open prompt in folder where you have fastboot installed on pc) it should say waiting for device.
then plugin kf to usb cable and power on if you've got fastboot it's easy, if you haven't it's a factory cable or a door wedge
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
PERFECT! But heres the problem, it wont turn on
will a motorola factory cable work with the kindle fire? if so, how do i fix this thing?
Buy a factory cable instead of making one
If your unit doesn't turn on at all and isn't recognized by the PC whatsoever then that is your only hope
Kujila said:
Buy a factory cable instead of making one
If your unit doesn't turn on at all and isn't recognized by the PC whatsoever then that is your only hope
Click to expand...
Click to collapse
i already have one. i have a motorola factory cable. I was wondering if i can fix my kindle fire with it. if so, how do i do it?
Beeyoth said:
i already have one. i have a motorola factory cable. I was wondering if i can fix my kindle fire with it. if so, how do i do it?
Click to expand...
Click to collapse
Factory in the sense that the cable used is one in the same as the cable used in initially programming the device at the manufacturer, not in the sense that it is an OEM cable that came with a phone.
Sent from my MB860 using XDA
backspacepc said:
Factory in the sense that the cable used is one in the same as the cable used in initially programming the device at the manufacturer, not in the sense that it is an OEM cable that came with a phone.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
second one.
Hey guys, I'm not sure how I got my Kindle stuck in a boot loop, but I need some help getting it out. I have this thread http://forum.xda-developers.com/showthread.php?t=1399889 for unbricking. The problem I run into is that for some reason the utility wont show my device at all. In my device manager on my computer it shows the kindle as Amazon with the yellow triangle. I have tried everything I could find to get my computer and thus the utility used in the above thread to pick it up and get it out of the boot loop. In case you need to know the ROM I tried to flash before I had this issue can be found here http://forum.xda-developers.com/showthread.php?t=1614004 .
Exact same issue doesn't connect to computer
Sent from my iPhone using Tapatalk
Bahamutmaester said:
Hey guys, I'm not sure how I got my Kindle stuck in a boot loop, but I need some help getting it out. I have this thread http://forum.xda-developers.com/showthread.php?t=1399889 for unbricking. The problem I run into is that for some reason the utility wont show my device at all. In my device manager on my computer it shows the kindle as Amazon with the yellow triangle. I have tried everything I could find to get my computer and thus the utility used in the above thread to pick it up and get it out of the boot loop. In case you need to know the ROM I tried to flash before I had this issue can be found here http://forum.xda-developers.com/showthread.php?t=1614004 .
Click to expand...
Click to collapse
ncvikingx97 said:
Exact same issue doesn't connect to computer
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
If you are getting stuck at the ROM's bootanimation and it won't go any further, your system software is broken. You'll have to get to recovery or at least into fastboot mode to fix it. If you have the stock bootloader, you have no easy way to get into recovery, so you'll probably need a factory cable. Read this...
http://forum.xda-developers.com/showthread.php?t=1668159
This probably won't hurt either...
http://forum.xda-developers.com/showthread.php?t=1552547
Thanks
Just contacted amazon about getting a new factory cable. Also, as much as I hate to admit it, I could probably use that guide
ncvikingx97 said:
Just contacted amazon about getting a new factory cable. Also, as much as I hate to admit it, I could probably use that guide
Click to expand...
Click to collapse
I hope you are joking...
http://forum.xda-developers.com/showthread.php?t=1550999
didn't work
Okay so I plugged my kindle in with a samsung charger I had, and it turned on when I plugged it in. Now it is plugged in, and it can't get past the kindle fire logo. What should I do? The computer doesn't recognize it either
ncvikingx97 said:
Okay so I plugged my kindle in with a samsung charger I had, and it turned on when I plugged it in. Now it is plugged in, and it can't get past the kindle fire logo. What should I do? The computer doesn't recognize it either
Click to expand...
Click to collapse
Download in use Kindle Fire Utility from the development section. Use it install window driver for KF, install TWRP, and reset boot mode. It is the tool for you. You just need to study how to use it.
Hope it helps.
Ok I know tons of people think they have bricked their device, but usually it is just a soft brick....hopefully I am the same. I tried to root my kindle fire using KFU. Something happened, it didn't work. Now it just stays on the boot screen. In windows it isn't recognized, I have read the forums and know to reinstall the drivers, but I can't because Windows recognizes it as an unknown device, (code 43), so they won't install. I have tried using the unbrick utility, but it doesn't work since windows isn't recognizing the device. I have a mac too that won't recognize it, at least I don't think it does. Maybe there is a way to get the drivers installed I am missing, but I tried following all of the tutorials here, and its not wokring. Is it possible that I can still fix it, or is it done. Thanks for any help.
DIRKxxxDIGGLER said:
Ok I know tons of people think they have bricked their device, but usually it is just a soft brick....hopefully I am the same. I tried to root my kindle fire using KFU. Something happened, it didn't work. Now it just stays on the boot screen. In windows it isn't recognized, I have read the forums and know to reinstall the drivers, but I can't because Windows recognizes it as an unknown device, (code 43), so they won't install. I have tried using the unbrick utility, but it doesn't work since windows isn't recognizing the device. I have a mac too that won't recognize it, at least I don't think it does. Maybe there is a way to get the drivers installed I am missing, but I tried following all of the tutorials here, and its not wokring. Is it possible that I can still fix it, or is it done. Thanks for any help.
Click to expand...
Click to collapse
Is it a 1st Gen Kindle Fire or 2nd? If it's a 2nd Gen you "might" be in trouble
Sent from my Fire Kindling A-Pad
guitarman2010 said:
Is it a 1st Gen Kindle Fire or 2nd? If it's a 2nd Gen you "might" be in trouble
Sent from my Fire Kindling A-Pad
Click to expand...
Click to collapse
Its first generation...
DIRKxxxDIGGLER said:
Its first generation...
Click to expand...
Click to collapse
In most cases I've seen of Windows complaining of an unknown device, it seems to be a problem with the bootloader. The fact that you can't even get it to accept commands from the Mac leads me to believe it is the same in your case.
You'll likely need to put the device in USBboot ("shorting trick") and install a working bootloader with Firekit.
"That's a special kind of stupid. The kind that makes me laugh."
What Soup said will work. This is what I did, as I was having the same problem as you.
1. Turn off your KF
2. peel off back cover from KF.
3. Make sure the A side of the usb cable is plugged in to your PC.
4. Find the short spot and put something there like a small screw driver point or a paper clip.
Here's a link to the picture. http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51
5. While you have your metal on the short spot turn on the KF.
6. After about 20 seconds or so Windows will now recognize it. Use KFU to put it in recovery mode, installing Fire, ETC.
Thanks guys, I'll try that when I get home from work today and report back.
Sent from my SAMSUNG-SGH-I747 using xda premium
Thanks for your help, it's up and working now with stock kernel and rom. Really appreciate your help!
Sent from my SAMSUNG-SGH-I747 using xda premium
Relikk356 said:
What Soup said will work. This is what I did, as I was having the same problem as you.
1. Turn off your KF
2. peel off back cover from KF.
3. Make sure the A side of the usb cable is plugged in to your PC.
4. Find the short spot and put something there like a small screw driver point or a paper clip.
Here's a link to the picture. http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51
5. While you have your metal on the short spot turn on the KF.
6. After about 20 seconds or so Windows will now recognize it. Use KFU to put it in recovery mode, installing Fire, ETC.
Click to expand...
Click to collapse
I having the same problem but for Kindle fire hd 7". I tried to use both stock cable and factory cable but it didn't work anyway. Any solution? please help me. Thank you
Hi. So the other day I installed TWRP on my Kindle Fire successfully. The KF was at 10.2.6, I'm not sure if that means it's a Kindle Fire 2 or not. Anyways, when I went to flash FFF, I stupidly flashed the .zip as a bootloader, thus making my Kindle Fire completely unusable. When I press the power button, nothing at all happens. Nothing I do will make the screen turn on or the power button to flash in any way. I've tried using Firekit with usbboot and the shorting trick, but that hasn't worked for me. (I just installed stock Ubuntu to a flash drive with the fk file on root, I'm fairly certain that's all that needed to be done?)
Anyways, my Kindle is unresponsove, and the usbboot trick has yet to work for me. I really want to save this guy. I've heard the KF cannot be completely bricked through software/flashing. I hope it's true! Any help would be greatly appreciated. Thank you.
if that is your software version then yes you have kindle fire 2, i'd wait for someone with more experience on here to post, but it sounds to me like you are going to need a factory cable
chris_m128 said:
if that is your software version then yes you have kindle fire 2, i'd wait for someone with more experience on here to post, but it sounds to me like you are going to need a factory cable
Click to expand...
Click to collapse
Thanks fro replying. I'm pretty sure a factory cable only puts it into fastboot if you have a working bootloader. I don't, so I don't think it would work.
I remember an instance where a friend of mine had a broken bootloader, and we used a factory cable to restore it, this was on the kindle fire. we had to first reflash the bootloader. I hope this is possible here.
---------- Post added at 11:59 AM ---------- Previous post was at 11:58 AM ----------
but you'll have to ask someone with more experience than me sorry.
jophish said:
Hi. So the other day I installed TWRP on my Kindle Fire successfully. The KF was at 10.2.6, I'm not sure if that means it's a Kindle Fire 2 or not. Anyways, when I went to flash FFF, I stupidly flashed the .zip as a bootloader, thus making my Kindle Fire completely unusable. When I press the power button, nothing at all happens. Nothing I do will make the screen turn on or the power button to flash in any way. I've tried using Firekit with usbboot and the shorting trick, but that hasn't worked for me.
Click to expand...
Click to collapse
I think you need a Factory cable to recover.
If you connect the Kindle to the PC and try adb devices in a terminal window, what do you see?
From the software version, you have KF2, as such you need to use the tools and ROMs from the KF2 threads. You could try to use the one click freedom boot and TWRP installer, to see if you can get that on.
From there you would probably have to push one of the 10.1 ROMs on, or the 10.2.6 recovery image, and then start again.
This seems to be happening a lot, and could be avoided if people read a bit more before using the wrong tools.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
chronicfathead said:
I think you need a Factory cable to recover.
If you connect the Kindle to the PC and try adb devices in a terminal window, what do you see?
From the software version, you have KF2, as such you need to use the tools and ROMs from the KF2 threads. You could try to use the one click freedom boot and TWRP installer, to see if you can get that on.
Click to expand...
Click to collapse
Howdy. I just fashioned a factory cable, just jumping +5V to pin 4, right? It seems to be doing absolutely nothing. No lights or anything are turning on. The freedom boot just spits out "error: device not found" and hangs on "Pushing Stack". Again, I was under the impression that the factory cable only made it boot in fastboot if you already have a working bootloader. I'll try loading into Ubuntu and see what it says in terminal. Thanks
EDIT: So, when I type adb devices into terminal, I get:
The program 'adb' is currently not installed. You can install it by typing:
sudo apt-get install android-tools-adb
You will have to enable the component called 'universe'
Could this have been my problem to begin with?
EDIT 2: Well, I installed ADB. There are no devices found when I enter that command, and the shorting trick with still doesn't work. Ugh.
jophish said:
Howdy. I just fashioned a factory cable, just jumping +5V to pin 4, right? It seems to be doing absolutely nothing. No lights or anything are turning on. The freedom boot just spits out "error: device not found" and hangs on "Pushing Stack". Again, I was under the impression that the factory cable only made it boot in fastboot if you already have a working bootloader. I'll try loading into Ubuntu and see what it says in terminal. Thanks
EDIT: So, when I type adb devices into terminal, I get:
The program 'adb' is currently not installed. You can install it by typing:
sudo apt-get install android-tools-adb
You will have to enable the component called 'universe'
Could this have been my problem to begin with?
EDIT 2: Well, I installed ADB. There are no devices found when I enter that command, and the shorting trick with still doesn't work. Ugh.
Click to expand...
Click to collapse
Leave your Kindle plugged in for an hour using the normal cable, as it may be totally flat.
The attached diagram shows what pins need joining. If you can, make sure none of the other pins are shorting.
Hold the power button for 20 seconds, plug in your fastboot cable, power on the Kindle.
You should see some traffic lights on the screen.
If you can get fastboot enabled, you should be able to push the correct partitions back on using the partitions from the factory restore image, your backup files or from the recovery thread. Hope you get it running.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
chronicfathead said:
Leave your Kindle plugged in for an hour using the normal cable, as it may be totally flat.
The attached diagram shows what pins need joining. If you can, make sure none of the other pins are shorting.
Hold the power button for 20 seconds, plug in your fastboot cable, power on the Kindle.
You should see some traffic lights on the screen.
If you can get fastboot enabled, you should be able to push the correct partitions back on using the partitions from the factory restore image, your backup files or from the recovery thread. Hope you get it running.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
I tried the fastboot cable out on a working Kindle Fire, and it worked correctly, so I did wire it right. I did as you said, holding the power button down and then plugging in the cable, and nothing happens still on the KF2. I have access to the insides, should I unplug the battery? It should be around 85% charged. Thanks again.
Edit: BIG NEWS~ Not really. When I plug the Kindle Fire with the fastboot cable into Windows, it appears under Device Manager as "Unknown Device" with a yellow triangle, but nothing shows up on the Kindle, no lights or anything. Hmph.
jophish said:
I tried the fastboot cable out on a working Kindle Fire, and it worked correctly, so I did wire it right. I did as you said, holding the power button down and then plugging in the cable, and nothing happens still on the KF2. I have access to the insides, should I unplug the battery? It should be around 85% charged. Thanks again.
Edit: BIG NEWS~ Not really. When I plug the Kindle Fire with the fastboot cable into Windows, it appears under Device Manager as "Unknown Device" with a yellow triangle, but nothing shows up on the Kindle, no lights or anything. Hmph.
Click to expand...
Click to collapse
You could have tried sending it back to Amazon, but you say you have opened it.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
chronicfathead said:
You could have tried sending it back to Amazon, but you say you have opened it.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
Urgh. I closed it up. Is there any way they'd know if I'd opened it?
I'm in exactly the same boat as you, also flashed FFF (by accident) on my device. Haven't been able to fix it yet but I do have a factory cable. Also did the USB trick, but that didn't have an effect either.
chronicfathead said:
I think you need a Factory cable to recover.
If you connect the Kindle to the PC and try adb devices in a terminal window, what do you see?
From the software version, you have KF2, as such you need to use the tools and ROMs from the KF2 threads. You could try to use the one click freedom boot and TWRP installer, to see if you can get that on.
From there you would probably have to push one of the 10.1 ROMs on, or the 10.2.6 recovery image, and then start again.
This seems to be happening a lot, and could be avoided if people read a bit more before using the wrong tools.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
In my case, I did by accident because it wasn't clear to me which KF generation I had (I've bricked mine just after christmas). These forums were not really clear either, I had a Kindle Fire so I just looked for a KF guide. After I bricked it I found out my device was a second generation Kindle Fire.
plinders said:
I'm in exactly the same boat as you, also flashed FFF (by accident) on my device. Haven't been able to fix it yet but I do have a factory cable. Also did the USB trick, but that didn't have an effect either.
In my case, I did by accident because it wasn't clear to me which KF generation I had (I've bricked mine just after christmas). These forums were not really clear either, I had a Kindle Fire so I just looked for a KF guide. After I bricked it I found out my device was a second generation Kindle Fire.
Click to expand...
Click to collapse
Hi, to clarify: you cannot boot into TWRP? No logos at boot at all? No boot?
I would send it back to Amazon...
Same Here..
I was thinking that all kindle fire are the same... installed fire fire fire using KFU and device got bricked....!
Hope someone here could help us get our devices up and running again...
yudanjah said:
Hi, to clarify: you cannot boot into TWRP? No logos at boot at all? No boot?
I would send it back to Amazon...
Click to expand...
Click to collapse
Nothing whatsoever.
I can't really send it back to Amazon, because of two reasons:
1) I already opened up the back
2) It was gifted to me from the US, and there is no Dutch Amazon, so I'd have to send the device back to the person who gifted to me, that person has to mail it to Amazon from there, and the replacement device has to come back the same way (via that person). That's not a situation I'd like to put that person in.
jophish said:
Urgh. I closed it up. Is there any way they'd know if I'd opened it?
Click to expand...
Click to collapse
I am sure they can figure it out. Can you boot into TWRP?
If so, you can still recover...
Dame problem
plinders said:
Nothing whatsoever.
I can't really send it back to Amazon, because of two reasons:
1) I already opened up the back
2) It was gifted to me from the US, and there is no Dutch Amazon, so I'd have to send the device back to the person who gifted to me, that person has to mail it to Amazon from there, and the replacement device has to come back the same way (via that person). That's not a situation I'd like to put that person in.
Click to expand...
Click to collapse
Same problem dude, did you fix it?
i.robert said:
Same problem dude, did you fix it?
Click to expand...
Click to collapse
Not yet I'm afraid. Everything I tried so far hasn't worked.
yudanjah said:
Hi, to clarify: you cannot boot into TWRP? No logos at boot at all? No boot?
I would send it back to Amazon...
Click to expand...
Click to collapse
No, Absolutely nothing. I really would like to get this working.
jophish said:
No, Absolutely nothing. I really would like to get this working.
Click to expand...
Click to collapse
same here we need a new firekit for the kf2
Help..
any updates on the fix? I hope someone out there could help us revive our bricked kindle fire 2... :angel:
kindle fire 2
flashed wrong bootloader (fff)
no power
no lights
no adb
shorting trick is not working for me :crying:
I recently rooted my Kindle Fire 1st generation to use Simple CM. I flashed it correctly and it worked fine, but to my surprise I recieved an iPad Mini as a gift. My parents asked for the Kindle and I said sure. Now, they wanted to go back to the original Amazon OS. So I downloaded a Kindle Fire stock zip to flash. I soon found out it was only an update... Now my Kindle successfully flashed it, I was setting it up, then it started to reboot, and it showed the launcher screen of Amazon, and then it gave me error pop-ups and it reboots after 30 seconds. I have been trying to get it to recognize on my computer but ADB and KFU aren't working the best. And now it says at 40% charge it will attempt to factory restore. (I will try soon). It repeats booting, then goes to the home screen, then it goes and shows errors and then does it again every 30 seconds. I am 13 years old and probably made a big mistake. I have read the threads on here and no solutions have worked. So I think it is bricked, and I have to give it to my parents by tonight and it has to have some sort of Amazon software or even CM. Is there anybody or anything that can help fix the Kindle Fire?
Thank you in advance, Jake.
You need to access fastboot to wipe data. You may need a factory cable.
In some cases, users have been fast enough to get into the settings and factory reset from there, so you may want to try that first.
soupmagnet said:
You need to access fastboot to wipe data. You may need a factory cable.
In some cases, users have been fast enough to get into the settings and factory reset from there, so you may want to try that first.
Click to expand...
Click to collapse
Have you heard of anyone that tried that? I will definately try it being that you have 1000+ thanks on the meter.
EDIT: I attempted to factory reset but it still did the same thing..... How do I enter fastboot and detect the Kindle in 30 seconds?
I attempted to root my kindle fire with KFU and it hasn't powered on or charged since... Is it bricked or can it be repaired.... anyone?
strykrmas said:
I attempted to root my kindle fire with KFU and it hasn't powered on or charged since... Is it bricked or can it be repaired.... anyone?
Click to expand...
Click to collapse
Well, that depends...
Is your Kindle Fire a second generation Kindle Fire?
soupmagnet said:
Well, that depends...
Is your Kindle Fire a second generation Kindle Fire?
Click to expand...
Click to collapse
yeah it is... help... please
strykrmas said:
yeah it is... help... please
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2391047
It's still a WIP, but that's the only hope you have of restoring your device.
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2391047
It's still a WIP, but that's the only hope you have of restoring your device.
Click to expand...
Click to collapse
I'm not that skilled in soldering and besides i'm too much of a noobie to attempt that anyway... thanks for your help...