Develop Bugs

[Q]Help! PC doesn't recognize Kindle Fire after root

Hello, guys,
I recently rooted my Fire (6.2.2) with Kindle Fire Utility (0.9.3). Kindle is working but my PC (Win7 32) can't recognize it when i'm connecting kindle to PC. And Kindle Fire Utility can't connect to device since then (statusffline).
Maybe I forgotten to switch to normal mode?
How can I fix this?
Thanks.

talcegie [616
With your Kindle plugged in and with KFU (even if it says it is offline), press 1 for Bootmode Menu and select Normal.

meturne2 said:
With your Kindle plugged in and with KFU (even if it says it is offline), press 1 for Bootmode Menu and select Normal.
Click to expand...
Click to collapse
I tried to do this. Got the message "kindle told to reload in normal mode". Kindle reloaded but the problem left.

Sounds like you may have to reload your drivers. Is the computer recognizing the Kindle at all. I had the problem when trying to load files to the SD card that it would not show up as a storage device. I unchecked USB debugging and it showed up. If you are trying to establish an ADB connection you may want to check your ADB setup.
Try cd C:\kindleadb
adb devices
This will tell you if your ADB connection is working.
Maybe this video will help.
http://www.youtube.com/watch?v=_C-H3epEHjo

meturne2 said:
Sounds like you may have to reload your drivers.
Click to expand...
Click to collapse
I tried to reinstall drivers from Kindle Fire utility few times. No result. Is there any way to wipe them from system?
meturne2 said:
Is the computer recognizing the Kindle at all
Click to expand...
Click to collapse
Unknown Device in device manager
meturne2 said:
Try cd C:\kindleadb
adb devices
Click to expand...
Click to collapse
Gives empty output. I'm using adb bundled with Kindle Fire Utility

The same thing happened to me and I just deleted all the files that were associated with the ADB and KFU and reloaded everything. Before you do that you can go into device manager and pull up the properties for unknown device(kindle) go into update drivers and point to the file you downloaded when installing KFU.
I used this video to root mine and the part on installing the drivers works. Make sure you download the driver files attached to the video. Look under "show more" --Links in the video description.
Hope this is helping and not making you more confused.
http://www.youtube.com/watch?v=KapnjR89ICA

The problem solved. It was Windows drivers problem. I've got a USB-stick in another slot during all operations. When I removed it everything worked normally. My motherboard is Asus P5G41T-M.
Thanks to everybody who tried to help.

Kindle not recognized by PC
meturne2 said:
The same thing happened to me and I just deleted all the files that were associated with the ADB and KFU and reloaded everything. Before you do that you can go into device manager and pull up the properties for unknown device(kindle) go into update drivers and point to the file you downloaded when installing KFU.
I used this video to root mine and the part on installing the drivers works. Make sure you download the driver files attached to the video. Look under "show more" --Links in the video description.
Hope this is helping and not making you more confused.
/QUOTE]
-------------------------------------------------------------------------------------------------------------------------
I have attempted several different fixes to get my rooted KF recognized by PCs running VISTA and XP to no avail. My KF is looping TWRP v2.0.0, so I have concluded. Yet if not PC can recognize it as a device...well, please give me your thoughts and suggestions.
Thx,
R
Click to expand...
Click to collapse

Did you try again with the latest utility?? Coz it shd work..
Sent from my MB526 using Tapatalk 2

Here`s my suggestion http://forum.xda-developers.com/showthread.php?t=1882565

[Q] Kindle Fire Brick (possibly FUBAR) Please help!!!

First of all, I search many threads but couldn't find help for my specific problem. I rooted my Kindle Fire 6.2.2. with TWRP. Upon trying to unroot it, it bricked. I downloaded Kindle Fire Utility v0.9.3. to fix this but my computer won't properly recognize my Kindle. It doesn't seem like a driver problem. All I can do when I plug in my Kindle is eject it. And when I try to install FireFireFire, I get this error "Oops...something went wrong. We are unable to locate your Kindle Fire. Make sure it is plugged in and powered on."
Please help! Thanks.

Lyrekz said:
First of all, I search many threads but couldn't find help for my specific problem. I rooted my Kindle Fire 6.2.2. with TWRP. Upon trying to unroot it, it bricked. I downloaded Kindle Fire Utility v0.9.3. to fix this but my computer won't properly recognize my Kindle. It doesn't seem like a driver problem. All I can do when I plug in my Kindle is eject it. And when I try to install FireFireFire, I get this error "Oops...something went wrong. We are unable to locate your Kindle Fire. Make sure it is plugged in and powered on."
Please help! Thanks.
Click to expand...
Click to collapse
Please read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
so you get an understanding of how these different pieces fit together.
I can't get a sense of where your problems begin. 1) TWRP is not used to root. 2) you never mention what your Kindle Fire is doing that you think it's bricked. 3) how did you manage to root it in the first place if your drivers weren't working?

kinfauns said:
Please read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
so you get an understanding of how these different pieces fit together.
I can't get a sense of where your problems begin. 1) TWRP is not used to root. 2) you never mention what your Kindle Fire is doing that you think it's bricked. 3) how did you manage to root it in the first place if your drivers weren't working?
Click to expand...
Click to collapse
Answers: 1. Rooted with BurritoRoot3 and also installed TWRP. 2. It is stucked on the Kindle Fire screen. 3. My drivers were working then and seem to be now. The problem is my computer won't recognize my Kindle. And when I go to Kindle properties, the manufacter, model number, and description all come up as unavaible and grayed out.

Lyrekz said:
Answers: 1. Rooted with BurritoRoot3 and also installed TWRP. 2. It is stucked on the Kindle Fire screen. 3. My drivers were working then and seem to be now. The problem is my computer won't recognize my Kindle. And when I go to Kindle properties, the manufacter, model number, and description all come up as unavaible and grayed out.
Click to expand...
Click to collapse
If you installed TWRP, then you also installed FFF. If by "Kindle Fire screen" you mean the yellow triangle logo and that's all you see when it starts up without it ever blinking black, then you are in fastboot mode. Use KFU to set it back to normal and reboot it. If that doesn't work, you need to check the device manager in Windows and make sure it shows "Android Phone -> Android ADB Interface" for your Kindle Fire. If the device manager does not show that, then you need to uninstall the drivers, remove the device from the device manager, disconnect the KF from your computer and follow these directions....
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6

kinfauns said:
If you installed TWRP, then you also installed FFF. If by "Kindle Fire screen" you mean the yellow triangle logo and that's all you see when it starts up without it ever blinking black, then you are in fastboot mode. Use KFU to set it back to normal and reboot it. If that doesn't work, you need to check the device manager in Windows and make sure it shows "Android Phone -> Android ADB Interface" for your Kindle Fire. If the device manager does not show that, then you need to uninstall the drivers, remove the device from the device manager, disconnect the KF from your computer and follow these directions....
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Click to expand...
Click to collapse
First of all. thank you for the help. And now my Kindle is stuck on the Kindle Fire screen.

Mine is stuck here too..been 3 days.. ordered the factory cable.. hopefully that works.

One thing I've noticed is that sometimes when the you try to issue fastboot commands in fastboot mode it doesn't register. But that doesn't mean you aren't in fastboot mode.
Get your command prompt ready (“ready" means that "fastboot" is in your present working directory)
Turn off your Kindle
Type "fastboot devices" (without quotes)
Turn your Kindle on
Hit enter to send fastboot command
Keep hitting UP arrow to bring up last command and keep hitting enter until your computer recognizes the Kindle. If it doesn't, start over and try again. When it does, then you can change your bootmode.
It WILL work, eventually. If it doesn't, the only other logical explanation is it's a driver issue.
Typically speaking (but not always), the only reason you should ever have to use a factory cable is if you killed your battery and you don't have enough juice to power the device. There are other reasons but they are extremely RARE.
And please forgive my frustration, but this is one of the simplest concepts to master. "Unbricking" your device shouldn't be this difficult...for anyone.
Sent from my Amazon Kindle Fire using xda premium

Readyreadyready
I notice in a post someone is seeing:
"Bricked mine too. It shows up as a USB COM port and spits out "READYREADYREADYREADY" until it disconnects itself. I think this means it should be possible to restore 5.3.2.1 via sp flash tool (or maybe another serial loader). If we can get the right files"
Is that the "Ready" you are saying means wait until fastboot?
soupmagnet said:
One thing I've noticed is that sometimes when the you try to issue fastboot commands in fastboot mode it doesn't register. But that doesn't mean you aren't in fastboot mode.
Get your command prompt ready (“ready" means that "fastboot" is in your present working directory)
Turn off your Kindle
Type "fastboot devices" (without quotes)
Turn your Kindle on
Hit enter to send fastboot command
Keep hitting UP arrow to bring up last command and keep hitting enter until your computer recognizes the Kindle. If it doesn't, start over and try again. When it does, then you can change your bootmode.
It WILL work, eventually. If it doesn't, the only other logical explanation is it's a driver issue.
Typically speaking (but not always), the only reason you should ever have to use a factory cable is if you killed your battery and you don't have enough juice to power the device. There are other reasons but they are extremely RARE.
And please forgive my frustration, but this is one of the simplest concepts to master. "Unbricking" your device shouldn't be this difficult...for anyone.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse

larmores said:
I notice in a post someone is seeing:
"Bricked mine too. It shows up as a USB COM port and spits out "READYREADYREADYREADY" until it disconnects itself. I think this means it should be possible to restore 5.3.2.1 via sp flash tool (or maybe another serial loader). If we can get the right files"
Is that the "Ready" you are saying means wait until fastboot?
Click to expand...
Click to collapse
this is only for kindle fire 1 (2011)
there is a separate section for your device see
Fire Index: Which Amazon (Kindle) Fire Do I have?
for correct forum link
Sent from my XT1096 using XDA Labs

[Q] KF 1 st new version 6.3.1_user_4107920

I am a KF 1st user from China, so maybe my english is not very well.
My KF 1st automatically upgrade to the new version 6.3.1_user_4107920, so i lost my root status.
so i want to root again, i used Kindle Fire Utility 0.9.6,but it shows
ADB Status: Offline
Boot Status: Unknown
i am sure my driver is right, i have root the kf from version 6.2.2 to 6.3.1, and i have read all the thread ablout root and "Kindle Fire Utility 0.9.6"
but i still can't find the answer ,so have anyone can help me ? Thanks a lot!

casport said:
I am a KF 1st user from China, so maybe my english is not very well.
My KF 1st automatically upgrade to the new version 6.3.1_user_4107920, so i lost my root status.
so i want to root again, i used Kindle Fire Utility 0.9.6,but it shows
ADB Status: Offline
Boot Status: Unknown
i am sure my driver is right, i have root the kf from version 6.2.2 to 6.3.1, and i have read all the thread ablout root and "Kindle Fire Utility 0.9.6"
but i still can't find the answer ,so have anyone can help me ? Thanks a lot!
Click to expand...
Click to collapse
Be sure that in your computer > Device Maanger > Kindle Fire is not marked with yellow triangle. This is the only reason it is not detected by the KFU 0.9.6 . It happened to me as well, but was able to re-root my kindle.

vertcam9 said:
Be sure that in your computer > Device Maanger > Kindle Fire is not marked with yellow triangle. This is the only reason it is not detected by the KFU 0.9.6 . It happened to me as well, but was able to re-root my kindle.
Click to expand...
Click to collapse
everything is ok~~~i am sure no yellow triangle~~~

restsrt pc turn iff kindel turn both back on dont plug kindel in uninstall all drivers then rejnstall with kindel unpluged plug in and baw work good luck
Sent from my Kindle Fire using xda app-developers app

Tried it all...Help
Devildog78965 said:
restsrt pc turn iff kindel turn both back on dont plug kindel in uninstall all drivers then rejnstall with kindel unpluged plug in and baw work good luck
Sent from my Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Trying to be as thorough as possible:
I am running a Kindle Fire with software version 6.3.1, which was previously rooted until software update. (Curse you Amazon!)
My computer has Windows 7 64bit
I downloaded adt-bundle-windows-x86_64 and ran SDK Manager.
Ran and closed Eclipse although I am not sure why or what to do with it.
Downloaded/installed:
Android SDK Tools
Android SDK Platform-tools
Android 4.2 and all attendant programs
All of the Extras including Google USB Driver.
Downloaded KFU v0.9.6.
Ran “install drivers” (Also omitted this step after uninstalling in subsequent attempts)
Ran “run.bat.”
In the cmd window that opens I get the KFU menu but under that is listed:
ADB Status: Offline
Boot Status: Unknown
I have also gotten:
ADB Status: Online
Boot Status: Unknown
This happens ad lib whenever it feels like it.
The Kindle never shows anything but the “You can now transfer files, etc” screen.
I have gone from the KFU menu to Bootmode Menu and chosen Normal (4000), as well as, Fastboot. It says “Oops...something went wrong. We are unable to locate your Kindle Fire. Make sure it is plugged in and powered on.” (It was.)
I have restarted both the Kindle Fire and the PC repeatedly. Uninstalled and reinstalled the drivers. Uninstalled/reinstalled the software that comes with SDK Manager.
Device Manager says under ADB Interface that it is Android Composite ADB Interface. Occasionally, however, I have had it listed further down the list as Kindle with the Yellow Error triangle and I have manually installed the drivers from there.
Note: I have also tried:
KindleFireRootNew631 which didn't work at all for me.
SuperOneClick v2.3.3.0 which tells me alternatively that my device appears to be already rooted, which is most definitely is not, and nothing...just kills ADB server and then starts ADB server and then....nada... Although the Windows circle thingie keeps circling, the task manager says it is “Not Responding”.
I have moved the USB port that I am using, always on one of the Mobo backplate USB's.
Changed cables.
Used a different computer.
Have resisted the urge to factory reset the device and/or break it in half!

If you can still transfer files, move everything you want off to your computer, then factory reset. Then try reinstalling drivers and running kfu
Sent from my Amazon Kindle Fire using Tapatalk HD

Have you tried using a factory reset cable ??? as they are different than a regular data cable .for my 1st gen kindle fire i used the factory cable that came with my first kindle black and white that used the e- ink without any problems whatsoever .you should be able to browse the forums to find one for sale i'm pretty sure you can also buy one straight from amazon
Sent from my Kindle Fire using xda app-developers app

[Q] Root Kindle Fire 6.3.2

I am trying to Root my Kindle Fire version 6.3.2, and am looking for the correct Kindle Fire Utility. I do not want to download the wrong one as the ones I have seen were for version 6.3.1 or 6.3. Anyone have suggestions?

Ichigo said:
http://forum.xda-developers.com/showthread.php?t=2192818
Click to expand...
Click to collapse
Hi...
Thanks for the linky, i grabbed it today and for some reason, it's not detecting my device. I've installed/reinstalled the drivers that came down with v0.9.8, still same results. Shows the driver Android ADB Device
When I run the option 2 to install root & superuser error encountered. We are unable to locate your kindle fire. Fastboot uses a different device than ADB. ck device mgr for Kindle or Amazon (when looking, neither are listed.)
So tried to just boot it to FastBoot and same results, device not found.
So being dummy me, i ran the Run script as admin, now i get the Tools\wget cannot be found. Thought maybe it was a long file name issue, so copied folder to c:\temp\ - still same results.
What am I doing wrong here guys?
Thanks in advance and thank you for the work you do for us idiots.
Mark

mrlee1999 said:
When I run the option 2 to install root & superuser error encountered. We are unable to locate your kindle fire. Fastboot uses a different device than ADB. ck device mgr for Kindle or Amazon (when looking, neither are listed.)
So being dummy me, i ran the Run script as admin, now i get the Tools\wget cannot be found. Thought maybe it was a long file name issue, so copied folder to c:\temp\ - still same results.
Click to expand...
Click to collapse
Put everything back where it belongs first. Also, your computer recognizes the kindle as an Android adb device in device manager? You are on 6.3.2 also?
Sent from my Kindle Fire with Tapatalk HD.
Just because I am a Senior Member doesn't mean anything.
I do not count myself any higher than anybody else.

Thanks for replying
I'm on 6.3.2.
It was seeing it as android adb.
I do have it on 1.4.a as well.
I did remove all of the drivers to the point win7 was showing kindle with an !. Reinstalled and rec'd same results. Got pissed at it and removed drivers again rebooted and removed the files under .android. When I get a chance, i'll try reinstall. Maybe by manually deleting the inf file will do some good???. I'll update the post when I have a chance to work on it.
Sent from my SCH-R530U using Tapatalk 2

mrlee1999 said:
Thanks for replying
I'm on 6.3.2.
It was seeing it as android adb.
I do have it on 1.4.a as well.
I did remove all of the drivers to the point win7 was showing kindle with an !. Reinstalled and rec'd same results. Got pissed at it and removed drivers again rebooted and removed the files under .android. When I get a chance, i'll try reinstall. Maybe by manually deleting the inf file will do some good???. I'll update the post when I have a chance to work on it.
Sent from my SCH-R530U using Tapatalk 2
Click to expand...
Click to collapse
Have you tried running KFU under compatibility for Windows XP SP3? Once you do that, it'll automatically ask for admin privileges.
Also, does your device show when you run the command
adb devices
Click to expand...
Click to collapse
on a terminal (or command prompt, on Windows) window?
Sent from my Muffin masquerading as a phone in the coffin.

Thanks
Removing the driver and deleting the files in the .android folder did the trick.
Thanks Everyone!!!!!
Mark

The one that ichigo said is good.

So I was using the new KFU 9.8+ on my first gen kindle (6.3.2)
and during the procedure while I think it was attempting to install FFF bootloader it was on <waiting for device>, my laptop lost batter life and shut down. Upon booting up my computer and trying KFU again
ADB Status: Offline
Boot Status: Unknown
My kindle now displays the logo. I assume it's bricked right now.
Are there any remedies to fix this?

HypothermicInferno said:
My kindle now displays the logo. I assume it's bricked right now.
Are there any remedies to fix this?
Click to expand...
Click to collapse
It is on the orange logo? And it won't boot properly? So the kindle just stays on that screen without getting dim or anything, right?
Sent from my muffin-ated Kindle Fire with Tapatalk HD.
Just because I am a Senior Member doesn't mean anything.
I do not count myself any higher than anybody else.

Bricked as well
My fire also appears to be bricked. "Kindle Fire" is displayed and the screen doesn't dim or anything like that.

mrlee1999 said:
Removing the driver and deleting the files in the .android folder did the trick.
Thanks Everyone!!!!!
Mark
Click to expand...
Click to collapse
I know how to delete the .android folder, but how can I be sure that the deleted drivers are the one associated with adb and not with other programs ? are those the drivers in Windows/system32 ?
How do you do that ?
Thanks

nugroho2 said:
I know how to delete the .android folder, but how can I be sure that the deleted drivers are the one associated with adb and not with other programs ? are those the drivers in Windows/system32 ?
How do you do that ?
Thanks
Click to expand...
Click to collapse
The .android folder is found under the root of your sdcard or you ext-sd. To remover the drivers:
If you are on Windows 7/8:​
Hit the "Start" button on the keyboard, and when the homescreen (Windows 8) or the Start dialogue (Windows 7) pops up, type in "Add or remove".
Hit enter on the highlighted option, which should be "Add or remove programs". (Note: You may have to go into the settings tab if you are running a search on Windows 8)
This will show you a window where all the apps that are currently installed on your computer shows up. (Metro apps don't show up here.) Look through the list until you find your KF drivers. This should be listed as something like this: Kindle Fire Drivers
Highlight the driver and look towards the top of the window. You should see that a "Change/uninstall" button has popped up. Click on that and follow the on-screen instructions to uninstall the drivers.
You're done!
If you are on an older version of Windows:​
The procedure is the same, only you have to go into Control Panel > Add or remove programs to do this.
Good luck rooting your KF. :good:

Kindle Fire Tool
My company is making a Kindle Fire Tool for Windows and Mac. Their are several options that might help you like "Toggle Unbrick" You can also root on Android 6.3.2.
Contact me if you have any questions: [email protected]

thebane90 said:
My fire also appears to be bricked. "Kindle Fire" is displayed and the screen doesn't dim or anything like that.
Click to expand...
Click to collapse
I had the Same issue found it was just stuck in Fastboot mode and Windows does not handle it well at all. I was getting a USB device not recognized error and wouldnt let me change the driver for it. To get back booting again I used
http://forum.xda-developers.com/showthread.php?t=1850038
Followed the direction and everything was good.... Almost I found no matter what computer I use fastboot always comes up as a bad device. :crying:
But that should help you with the "Brick"

Kindle Fire 6.3.2 successfully rooted
mrlee1999 said:
Hi...
Thanks for the linky, i grabbed it today and for some reason, it's not detecting my device. I've installed/reinstalled the drivers that came down with v0.9.8, still same results. Shows the driver Android ADB Device
When I run the option 2 to install root & superuser error encountered. We are unable to locate your kindle fire. Fastboot uses a different device than ADB. ck device mgr for Kindle or Amazon (when looking, neither are listed.)
So tried to just boot it to FastBoot and same results, device not found.
So being dummy me, i ran the Run script as admin, now i get the Tools\wget cannot be found. Thought maybe it was a long file name issue, so copied folder to c:\temp\ - still same results.
What am I doing wrong here guys?
Thanks in advance and thank you for the work you do for us idiots.
Mark
Click to expand...
Click to collapse
I have the same error.
What i did was...
1. Download KFU 0.9.9 (http://forum.xda-developers.com/showthread.php?t=2192818)
2. Download TWRP (http://techerrata.com/browse/twrp2/blaze)
3. Download FFF (http://forum.xda-developers.com/showthread.php?t=1369405)
4. I rename them as "twrp" and "fff" respectively and place them in the "recovery" folder in KFU
5. I manually install the drivers
6. I check in the device manager to show me "Android Phone - Android Composite ADB interface"
7. I run the KFU
and that was all...
I check the root was complete with the https://play.google.com/store/apps/...GwsMSwxLDMsImNvbS5qb2V5a3JpbS5yb290Y2hlY2siXQ..

not visible on my pc.
Hey, I took the first step to root my kf on 6.3.2. I can no longer see the devise on my computer to do anhything else. I only loaded the utility file onto the devise and now what? I can't even delete it. Any thoughts?

Okay... here goes!
Vlasp said:
The one that ichigo said is good.
Click to expand...
Click to collapse
*Takes a deeeeep breath* okay, I thought it looked like the most promising instructions I've found so far too... so, from a TOTAL novice at all of this, here goes! Thanks for the endorsement ( I will definately thank him too! )

So, I went through all the steps outlined by xarenmi, but it STILL doesn't recognize my kindle when I try to use the run tool.
I'm not the best with all this, so...

Help...
Hey, I finally got the google winusb driver installed (I had to do it via SDK manger) but it still recognizes my kindle as "kindle" under "other devices" in the device manager. Also the KFU will not recognize it.. period. just nothing and I'm getting really fed up.
I have followed all instuctions to the T and I am still having issues.

Can't exit fastboot mode

Hello,
I was rying to install FireFireFire in my kindle fire 1 gen by doing this guide: https://forum.xda-developers.com/t/...flashing-fff-twrp-2015.2814955/#post-54124313
Beforehand I rooted kindle with saferoot successfully.
After device entered fbmode, it shows kindle fire logo and can't be recognized on computer.
How do I exit out of fastboot?
Is it possible to exit with short circuiting to boot via USB? how do I do this?
Kindle version is 6.3.4

mrsiri said:
Hello,
I was rying to install FireFireFire in my kindle fire 1 gen by doing this guide: https://forum.xda-developers.com/t/...flashing-fff-twrp-2015.2814955/#post-54124313
Beforehand I rooted kindle with saferoot successfully.
After device entered fbmode, it shows kindle fire logo and can't be recognized on computer.
How do I exit out of fastboot?
Is it possible to exit with short circuiting to boot via USB? how do I do this?
Kindle version is 6.3.4
Click to expand...
Click to collapse
Root doesn't affect flashing Recoveries or bootloaders
Likely a driver issue, Using Windows 10?
The only way to exit out of Fastboot mode that I know is
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot

Thank you for the reply.
I tried using both linux and windows 10 but none detected my kindle.
Can I try the short pin method? Since I never done anything like this before, do I need to ground myself before shorting to not get shocked? since my version is 6.3.4 and the guide had version 6.2.1 idk if I can

mrsiri said:
Thank you for the reply.
I tried using both linux and windows 10 but none detected my kindle.
Can I try the short pin method? Since I never done anything like this before, do I need to ground myself before shorting to not get shocked? since my version is 6.3.4 and the guide had version 6.2.1 idk if I can
Click to expand...
Click to collapse
You don't need to ground your self, you can try the short pin method, it doesn't matter what firmware version is installed.

sd_shadow said:
You don't need to ground your self, you can try the short pin method, it doesn't matter what firmware version is installed.
Click to expand...
Click to collapse
Okay I'll try that and report after doing it.
Thank you again

mrsiri said:
Okay I'll try that and report after doing it.
Thank you again
Click to expand...
Click to collapse
Shorting the pins before, after and during plug in didn't change anything on screen...
It should at least be detected on computer, but either windows or linux don't show anything.
Since I need to lift the cable slightly up for it to connect to computer, I guess the problem is the port.

mrsiri said:
Shorting the pins before, after and during plug in didn't change anything on screen...
It should at least be detected on computer, but either windows or linux don't show anything.
Since I need to lift the cable slightly up for it to connect to computer, I guess the problem is the port.
Click to expand...
Click to collapse
There were lots of port issue reported over the years, likely the most common thing that let to there retirement.