So I have read the all about KF guide, I read the how to set up adb guide, and I used the KF utility to install my drivers for adb, I checked device manager to make sure I have the correct drivers installed but when I execute "adb devices" there is nothing.. So, I installed ubuntu on a machine, spent hours setting it up for adb, got it all up and running and same thing, adb devices = nothing. So my KF is on 6.3.1 stock software, my goal here is to root, and I'm wondering if it is the new software that is screwing me up?? I already asked if the 6.3 root process will work which someone said it should work just fine.. But I don't know what I'm doing wrong... Any suggestions? I have a friend that is a electrical engineer major who is making me a factory cable... So maybe that is my answer? Thanks
Are you getting an error with adb or are you getting no devices?
I've had usb port problems on my desktop where it wouldn't recognize and ADB device, but switching to a new port worked. Specifically a usb port on a hub, but I imagine this was a very unique case to me, but trying different usb ports is always a good debug step.
Also, usb cables sometimes are bad as well. I have a micro usb cable that only charges, doesn't do any data. I would recommend a new cable as well.
Thirdly, try a different computer if possible. Basically you're trying to isolate the problem is in fact your computer and not your Kindle.
soupmagnet said:
Are you getting an error with adb or are you getting no devices?
Click to expand...
Click to collapse
ADB starts the server, and then says
List of devices attatched
thats it.. So looks like adb is working properly.. Just no devices listed.
superxpro12 said:
I've had usb port problems on my desktop where it wouldn't recognize and ADB device, but switching to a new port worked. Specifically a usb port on a hub, but I imagine this was a very unique case to me, but trying different usb ports is always a good debug step.
Also, usb cables sometimes are bad as well. I have a micro usb cable that only charges, doesn't do any data. I would recommend a new cable as well.
Thirdly, try a different computer if possible. Basically you're trying to isolate the problem is in fact your computer and not your Kindle.
Click to expand...
Click to collapse
I've tried 2 different cables, that will transfer files and charge, and 3 different computers now... My work computer, my home desktop, and my new linux build.. So I don't think its a issue with a cable or a port..
In Windows it's most likely a driver problem. With Linux, you have to make sure you set up your udev rules.
westlandnick said:
So I have read the all about KF guide, I read the how to set up adb guide, and I used the KF utility to install my drivers for adb, I checked device manager to make sure I have the correct drivers installed but when I execute "adb devices" there is nothing.. So, I installed ubuntu on a machine, spent hours setting it up for adb, got it all up and running and same thing, adb devices = nothing. So my KF is on 6.3.1 stock software, my goal here is to root, and I'm wondering if it is the new software that is screwing me up?? I already asked if the 6.3 root process will work which someone said it should work just fine.. But I don't know what I'm doing wrong... Any suggestions? I have a friend that is a electrical engineer major who is making me a factory cable... So maybe that is my answer? Thanks
Click to expand...
Click to collapse
I had the same problem in my Mac environment first time I tried to connect adb. It would not connect until I edited the adb_usb.ini file under my .android directory. If the file doesn't exist, create it and add 0x1949 on a line by itself. If that doesn't work you probably have a driver issue as stated previously.
UK
ukchucktown said:
I had the same problem in my Mac environment first time I tried to connect adb. It would not connect until I edited the adb_usb.ini file under my .android directory. If the file doesn't exist, create it and add 0x1949 on a line by itself. If that doesn't work you probably have a driver issue as stated previously.
UK
Click to expand...
Click to collapse
I think you are right with the driver issue.. Just for fun at home I plugged my HTC Supersonic in and adb didn't see it either, but at work I have set up drivers for my HTC and adb can see it here... And my work computer has that file. I'll try to add that file to my computer at home when I get there and see if it fixes it. Thanks for that, I figured it had to be something simple/stupid.
soupmagnet said:
In Windows it's most likely a driver problem. With Linux, you have to make sure you set up your udev rules.
Click to expand...
Click to collapse
I don't think I set up any udev rules on my linux.. I will check that out as well.
I have a similar problem, and followed probably every adb guide in the forums, along with several other... I bricked my gf's KF accidentally when I was distracted by her son, and missed a step or 2 for the "Kindle Fire Utility", but I THINK the problem started even before that attempting to use the "SuperOneClick" tool to root it... I did everything correctly with the tool BUT from what I've read it is no longer working correctly... The KF is stuck at the boot logo, but I can still turn it on and off... I've added/edited the "adb_usb.ini" file, added myself to the udev group, etc. but the device is still not listed under the "adb devices" command, there is no error, no question marks, no nothing... I've seen it listed as "Google Inc" on some guides under the "lsusb" command, and one with "Lab126" which is what mine is listed as... Also killed/restarted the servers, restarted my computer, shut down my computer, tried different cables (all of which have transfering capabilities), etc. so I am completely lost... Not to mention that the LiveUSB was giving me trouble so instead I erased the Windows 7 partition to fully install Ubuntu 12.04... I've been trying to figure this out for about 3 days to no avail... Any advice???
Thanks in Advance!!!
CJ
(Edit: Just tried the "lsusb" command, and it doesn't even show up like that anymore)
yeah run andadb on your machine do steps 1-4 in terminal http://forum.xda-developers.com/showthread.php?t=1670405 just right click on andadb go to properties permissions allow it to be executed and run it after all 4 steps are done and you have followed the threads instructions use sudo for your fastbboot commands
@Thepooch alright, that took me a BIG step in the right direction, thanks!!! The "lsusb" command now shows that it's connected as "Lab126" again, BUT "adb devices" still comes back with nothing... I'm sooo close, but still so far from getting this thing right...
[email protected]:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 04fc:05d8 Sunplus Technology Co., Ltd Wireless keyboard/mouse
Bus 002 Device 002: ID 0408:03f5 Quanta Computer, Inc.
Bus 003 Device 002: ID 0bda:0186 Realtek Semiconductor Corp.
Bus 001 Device 003: ID 1949:0006 Lab126
[email protected]:~$ adb kill-server
[email protected]:~$ adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:~$ adb devices
List of devices attached
Yeah I'm not seeing the Google driver in the list did you run the sdk and select the top two and Deselect the rest if so that's fine. Power your kindle off type sudo fastboot getvar product plug your kindle in it should power on and terminal output should be product: kindle then type sudo fastboot reboot your kindle will then reboot.
Honestly, I don't know... There was another guide (not sure exactly which one) where I had to install Eclipse and run the sdk and install drivers/platforms from there and I'm not sure exactly which ones it had me install... I tried to do it from the guide that you posted as well but for some reason the part where the sdk was supposed to open etc. didn't work as it was supposed to... The rest worked fine though... I'll have to re-check it, but hopefully that piece of information is what I've been searching for, but at the same time if it is, I'm going to feel even more "special" lol...
Edit: Not sure if the SDK is the same when using Eclipse or not, but the "Android SDK Tools" and "Android SDK Platform Tools" are my first 2 and they were already installed... Did everything you said from there,and I've been "< waiting for device >" for a good 5 minutes now... Is it always this complicated or did I just really screw things up???
Lab126 is your device booted normally or in recovery. As Lab126 you can only issue adb commands. lsusb > Bus 001 Device 005: ID 1949:0100 Lab126
Google inc. is your device in fastboot mode. As Google inc. you can only issue fastboot commands. lsusb > Bus 001 Device 005: ID 18d1:0100 Google Inc.
What seems to be the problem is, what you think to be fastboot is kind of misleading. The stock Kindle ROM has the Kindle Fire logo for its boot animation as well as the bootloader. So, if you're stuck in a boot animation bootloop it could very well seem like you're stuck in fastboot. But that's just a guess.
Enter "adb devices" and see if you're connected.
[Edit:]Also, double check your adb_usb.ini to make sure it's configured properly.
Not sure exactly who you're suggestions are meant to be towards but it fits right along with my problem, and it's put in a much more informative way than I could've put it ... How would I/is it possible for me to get into fastboot while it's still recognized as "Lab126"??? All of my files including "adb_usb.ini" are configured to the best of my knowledge...
When you open adb_usb.ini does it have 0x1949 on its own line and nothing else on that line?
And when you enter "sudo gedit /etc/udev/rules.d/51-android.rules", do you see this...
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTRS{idProduct}=="0006", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTRS{idProduct}=="0100", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
Yup, the only difference is on the 51 rules file, I switched "OWNER="root"" to "OWNER="CJ""...
sdfyhpromotions said:
Yup, the only difference is on the 51 rules file, I switched "OWNER="root"" to "OWNER="CJ""...
Click to expand...
Click to collapse
and you can't get adb to connect?
Not in the 9,837 times I've tried it ... Oh, and it was originally "root" until I read somewhere that it's supposed to be you're account username but I'll try to change it back and see if it makes a difference...
Related
Yes, another one of these issues. None of the other threads provided me any help, so new thread time! Allright, so I had just flashed a stock 6.3.1 Kindle Fire Rom. It all went well. Then I wanted to install FireFireFire Dualboot for other purposes, so i rebooted my Kindle fire first, (I always do this before I do anything rom/recovery related.) I went to adb shell on my computer told it to reboot into fasboot using "fastboot -i 0x1949 flash bootloader u-boot.bin" It boots into fastboot but, the bootloader diddn't seem to install and now my device can't be found on the KFU or standard ADB shell. I would appreciate any help on this issue as I need this kindle fire to be working. I have rebooted it 3 times too see if it could be found it just show "Unknown Device". Thanks, I can provide more info if the need be.
Jared631 said:
Yes, another one of these issues. None of the other threads provided me any help, so new thread time! Allright, so I had just flashed a stock 6.3.1 Kindle Fire Rom. It all went well. Then I wanted to install FireFireFire Dualboot for other purposes, so i rebooted my Kindle fire first, (I always do this before I do anything rom/recovery related.) I went to adb shell on my computer told it to reboot into fasboot using "fastboot -i 0x1949 flash bootloader u-boot.bin" It boots into fastboot but, the bootloader diddn't seem to install and now my device can't be found on the KFU or standard ADB shell. I would appreciate any help on this issue as I need this kindle fire to be working. I have rebooted it 3 times too see if it could be found it just show "Unknown Device". Thanks, I can provide more info if the need be.
Click to expand...
Click to collapse
When you say, " the bootloader diddn't seem to install", could you be more specific?
What does your boot screen look like now?
Were there any error messages?
Did fastboot hang at "waiting for device"?
Do you have custom recovery installed?
Of so, what custom recovery do you have installed?
soupmagnet said:
When you say, " the bootloader diddn't seem to install", could you be more specific?
What does your boot screen look like now?
Were there any error messages?
Did fastboot hang at "waiting for device"?
Do you have custom recovery installed?
Of so, what custom recovery do you have installed?
Click to expand...
Click to collapse
1. Boot screen is saying "KindleFire" the stock one not FFF.
2. No error messages
3. Yes, it hangs at "waiting for device"
4. No I don't
That's what I meant by "It diddn't seem to install".
Okay, the "waiting for device" simply means the drivers aren't working properly. I do not use Windows so I cannot offer any real help other than to tell you to reinstall them. There is a world of different suggestions for fixing the driver problem that you can find by searching the forums or even Google, but they're all hit and miss.
I will tell you to work on the driver issue until you can't take it anymore and then consider, possibly, other options.
Well, I might as well as just use soupkit, as I am dualbooting Ubuntu and Windows XP Pro. I have to wait a bit untill I can use it but, I have it all setup, so I'll get back too you when I get to try it out. If this doesn't work I will do the reinstall drivers, like you said, and hopefully that works. Thanks, for the help!
Update:
Soupkit diddn't work. (FK, not USBboot)
So, now onto Windows XP driver reinstallation.... Yay...
If this doesn't work I guess ill have to do the shorting trick.
Alright, So I did all of your suggestions, soupmagnet. None of them have worked, so I'm lead to beilive it's in some sort of state that won't allow it to be recognized on any ADB shell. I'm going to try the shorting trick, if that doesn't work then I'm pretty much screwed for all I know.
UPDATE:
Just too make sure it wasn't just my Lenovo computer, I pulled out my old gateway, setup the driovers correctly and everything. ( I tested too see if it detected my phone, it did) and it still diddn't detect my Kindle Fire, just said "Unknown Device"
I also have this same issue as well, was going to root my stock 6.2.1, but unplugged it on accident, no FFF, and stuck on the stock orange kindle fire logo.
Jared631 said:
Alright, So I did all of your suggestions, soupmagnet. None of them have worked, so I'm lead to beilive it's in some sort of state that won't allow it to be recognized on any ADB shell. I'm going to try the shorting trick, if that doesn't work then I'm pretty much screwed for all I know.
UPDATE:
Just too make sure it wasn't just my Lenovo computer, I pulled out my old gateway, setup the driovers correctly and everything. ( I tested too see if it detected my phone, it did) and it still diddn't detect my Kindle Fire, just said "Unknown Device"
Click to expand...
Click to collapse
With the device plugged in and powered up, in the Linux terminal, enter...
lsusb
You should see a device labeled either Lab 126 (normal mode) or Google Inc. (fastboot).
Also pay attention to the numbers assigned to the device. You should see one of the following sets:
1949:0006 (for normal mode)
18d1:0100 (for fastboot) -sorry for the typo: fixed-
Anything different will throw off the SoupKit, but it is still fixable.
If "lsusb" doesn't show anything of the sort, you may have bigger problems.
soupmagnet said:
With the device plugged in and powered up, in the Linux terminal, enter...
lsusb
You should see a device labeled either Lab 126 (normal mode) or Google Inc. (fastboot).
Also pay attention to the numbers assigned to the device. You should see one of the following sets:
1949:0006 (for normal mode)
18d1:0100 (for fastboot) -sorry for the typo: fixed-
Anything different will throw off the SoupKit, but it is still fixable.
If "lsusb" doesn't show anything of the sort, you may have bigger problems.
Click to expand...
Click to collapse
thanks, mine showed up what you wrote and changed to normal mode, and finally used ZombiePiratez unbrick tool and worked:good:
soupmagnet said:
With the device plugged in and powered up, in the Linux terminal, enter...
lsusb
You should see a device labeled either Lab 126 (normal mode) or Google Inc. (fastboot).
Also pay attention to the numbers assigned to the device. You should see one of the following sets:
1949:0006 (for normal mode)
18d1:0100 (for fastboot) -sorry for the typo: fixed-
Anything different will throw off the SoupKit, but it is still fixable.
If "lsusb" doesn't show anything of the sort, you may have bigger problems.
Click to expand...
Click to collapse
Thanks. I'll check that out. So to be clear it should just inform me of what mode it is in, correct? Not fix it.
What "lsusb" does, is tells you what USB devices are detected by the system. It doesn't fix anything. It's used a lot as a troubleshooting tool.
Yay.... Progeress?
soupmagnet said:
What "lsusb" does, is tells you what USB devices are detected by the system. It doesn't fix anything. It's used a lot as a troubleshooting tool.
Click to expand...
Click to collapse
Alright, here is what I got.
Bus 002 Device 003: ID 1949:0006 Lab126
So that means it is in normal mode, correct?
----------------------------------------------------------------------------------
Don't know if this helps but,
Correct. So, if you ran the SoupKit and rebooted afterwards, there's no reason it shouldn't work.
Since you are in normal mode, send "adb devices" and tell me what happens. Include error messages if any.
[Edit:] Apparently you posted the pics as I was writing this. This is very interesting. I've seen an issue like this in the not too recent past where a user had a BSOD in the middle of flashing the bootloader. It sort of hard-bricked his device except he could still power it on, but it would not accept commands for anything, and he had the same "unknown device" error. As far as I can remember, it was his bootloader that was messed up, even though it would still power up.
What does "lsusb" give you in fastboot mode?
Adb devices
soupmagnet said:
Correct. So, if you ran the SoupKit and rebooted afterwards, there's no reason it shouldn't work.
Since you are in normal mode, send "adb devices" and tell me what happens. Include error messages if any.
Click to expand...
Click to collapse
This is what happens.
Code:
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$ adb kill-server
[email protected]:~$ adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
[email protected]:~$
soupmagnet said:
Correct. So, if you ran the SoupKit and rebooted afterwards, there's no reason it shouldn't work.
Since you are in normal mode, send "adb devices" and tell me what happens. Include error messages if any.
[Edit:] Apparently you posted the pics as I was writing this. This is very interesting. I've seen an issue like this in the not too recent past where a user had a BSOD in the middle of flashing the bootloader. It sort of hard-bricked his device except he could still power it on, but it would not accept commands for anything, and he had the same "unknown device" error. As far as I can remember, it was his bootloader that was messed up, even though it would still power up.
What does "lsusb" give you in fastboot mode?
Click to expand...
Click to collapse
Also, what is the output of...
sudo /etc/udev/rules.d/51-android.rules
Jared631 said:
Alright, here is what I got.
Bus 002 Device 003: ID 1949:0006 Lab126
So that means it is in normal mode, correct?
Click to expand...
Click to collapse
Before you guys get too far off track...
1949:0006 is shared by the the stock system software, recoveries, CM7 based ROMs and the stock bootloader. These two numbers alone are insufficient to determine the "mode" of the device, so you might very well be in fastboot mode. If you get these numbers, you have to take a look at the bcdDevice value.
Code:
lsusb -v | grep bcdDevice
1.00 is the bootloader.
2.16 is one of the others.
More info here...
http://forum.xda-developers.com/showthread.php?t=1668159
sudo /etc/udev/rules.d/51-android.rules
soupmagnet said:
Also, what is the output of...
sudo /etc/udev/rules.d/51-android.rules
Click to expand...
Click to collapse
Code:
[email protected]:~$ sudo /etc/udev/rules.d/51-android.rules
sudo: /etc/udev/rules.d/51-android.rules: command not found
[email protected]:~$
Here is what I have in the file it's refering too.
Code:
# adb protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTRS{idProduct}=="0006", MODE="0666", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
# fastboot protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTRS{idProduct}=="0100", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
Sorry, I left out "gedit". It should be "sudo gedit /etc..." oh well, whatever.
Either way, that much is correct. It's a tricky situation with stock software because, the boot logo and boot animation are basically the same, and as kinfauns has said, the two modes share the same IDs. But in your case, you can't send either fastboot or adb commands, which makes for an interesting situation. Your udev rules are configured properly for the device, so other than it being in fastboot with a partially broken bootloader, I can't imagine what would cause it to not connect properly.
Definitely use the command that kinfauns gave you and find out what mode you are in. If you are in fastboot, it would seem that your bootloader is corrupt in some way and you would have to use the Firekit to fix it.
As far as I know, if you are using the "shorting trick" correctly to boot the device in USBboot mode, the Firekit should work regardless. (Someone correct me if I'm wrong)
kinfauns said:
1949:0006 is shared by the the stock system software, recoveries, CM7 based ROMs and the stock bootloader
Click to expand...
Click to collapse
I knew that. I just forgot, that's all. ::looks around::
soupmagnet said:
Sorry, I left out "gedit". It should be "sudo gedit /etc..." oh well, whatever.
Either way, that much is correct. It's a tricky situation with stock software because, the boot logo and boot animation are basically the same, and as kinfauns has said, the two modes share the same IDs. But in your case, you can't send either fastboot or adb commands, which makes for an interesting situation. Your udev rules are configured properly for the device, so other than it being in fastboot with a partially broken bootloader, I can't imagine what would cause it to not connect properly.
Definitely use the command that kinfauns gave you and find out what mode you are in. If you are in fastboot, it would seem that your bootloader is corrupt in some way and you would have to use the Firekit to fix it.
As far as I know, if you are using the "shorting trick" correctly to boot the device in USBboot mode, the Firekit should work regardless. (Someone correct me if I'm wrong)
Click to expand...
Click to collapse
I'm going to use the "shorting trick" as a last resort. It's looking like I will anyways. I will post as soon as I get that mode (USB cord is being used at the moment)
Jared631 said:
I'm going to use the "shorting trick" as a last resort. It's looking like I will anyways. I will post as soon as I get that mode (USB cord is being used at the moment)
Click to expand...
Click to collapse
If (when) you try the shorting trick, it's best to use a sharp pair of tweezers or a safety pin to keep from losing the connection while plugging the USB cable in. And the picture of the actual point posted on Pokey's thread is a little misleading...it's considerably smaller.
Hi all.
I have seen this in another kind of devices but haven't found thread related about Kindle Fire (1st gen).
A little introduction:
- My kindle was in CM10 and I noticed it started to be detected as Unknown Device in Windows, so
- I used TWRP to flash 6.3.1 stock ROM BUT forgot to wipe before flashing and rebooting. In that moment my situation was an endless loop wih the Kindle being rebooted after 15 seconds aproximately.
- I modified a cable to make it "factory cable" but even in fastboot (plain kindle fire logo) the Unknown Device was there.
- After many tries I managed to make a Reset to factory defaults in Android in the 15 seconds
- Currently the kindle is in stock ROM but still is not correctly detected.
Of course, I have re-installed the drivers in my computer and even tried in a fresh windows installation with no previous drivers without luck. Also, booted an Ubuntu USB with SoupKit and no lsusb changes after plugin the device (just a few dmesg messages about being unable to enumerate USB device on port).
So, if some of you have any idea to try, please tell me. I have the factory cable and the back cover of the kindle removed... ready for anything!
Thank you for your time!
soukron said:
Hi all.
Also, booted an Ubuntu USB with SoupKit and no lsusb changes after plugin the device (just a few dmesg messages about being unable to enumerate USB device on port).
Click to expand...
Click to collapse
This is the part I mentioned before about dmesg messages:
Code:
[ 234.956030] usb 2-5: >new full-speed USB device number 4 using ohci_hcd
[ 235.136035] usb 2-5: >device descriptor read/64, error -62
[ 235.420038] usb 2-5: >device descriptor read/64, error -62
[ 235.700026] usb 2-5: >new full-speed USB device number 5 using ohci_hcd
[ 235.880055] usb 2-5: >device descriptor read/64, error -62
[ 236.164040] usb 2-5: >device descriptor read/64, error -62
[ 236.444025] usb 2-5: >new full-speed USB device number 6 using ohci_hcd
[ 236.852030] usb 2-5: >device not accepting address 6, error -62
[ 237.028025] usb 2-5: >new full-speed USB device number 7 using ohci_hcd
[ 237.436025] usb 2-5: >device not accepting address 7, error -62
[ 237.436037] hub 2-0:1.0: >unable to enumerate USB device on port 5
And there's no reference in lsusb:
Code:
[email protected]:~$ lsusb
Bus 001 Device 004: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB Flash Drive
Bus 001 Device 005: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Bus 002 Device 002: ID 04ca:0022 Lite-On Technology Corp.
Bus 002 Device 003: ID 046d:0a0b Logitech, Inc. ClearChat Pro USB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[email protected]:~$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/10p, 12M
|__ Port 3: Dev 2, If 0, Class=HID, Driver=usbhid, 1.5M
|__ Port 4: Dev 3, If 0, Class=audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 3, If 1, Class=audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 3, If 2, Class=audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 3, If 3, Class=HID, Driver=usbhid, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/10p, 480M
|__ Port 9: Dev 5, If 0, Class=>ifc, Driver=rtl8187, 480M
From what I've seen, this is usually a problem with the bootloader. How or why, I don't know. That being said, Firekit w/shorting trick seems to be the most successful at resolving this issue.
soupmagnet said:
From what I've seen, this is usually a problem with the bootloader. How or why, I don't know. That being said, Firekit w/shorting trick seems to be the most successful at resolving this issue.
Click to expand...
Click to collapse
I'm trying to follow this thread http://forum.xda-developers.com/showthread.php?t=1636883 but I don't know how to check if the "short trick" is well performed or not. Is there anything I should notice? At this moment if I make the short trick and plug in the usb connector, nothing seems to be working in the kindle but dmesg is continuously showing errors like previous ones.
Regards,
Are you using Firekit? What command?
"That's a special kind of stupid. The kind that makes me laugh"
I'm still in the step of the process when I make the short trick, plug the usb and the kindle should be detected. Should I try the usbboot commands even when there's no kindle entry in lsusb output?
YES absolutely! And hold the power button for 15 seconds to make sure the CPU isn't running before attempting the short.
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
YES absolutely! And hold the power button for 15 seconds to make sure the CPU isn't running before attempting the short.
Click to expand...
Click to collapse
The command is ./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img but it keeps stopped in waiting for OMAP44xx device....
I'm going to try a few times more. Thank you!
BTW, what are the next steps? Because this unit is working properly but the USB port to transfer data between computer and device: it boots, it loads stock firmware, and works properly.
soukron said:
The command is ./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img but it keeps stopped in waiting for OMAP44xx device....
I'm going to try a few times more. Thank you!
BTW, what are the next steps? Because this unit is working properly but the USB port to transfer data between computer and device: it boots, it loads stock firmware, and works properly.
Click to expand...
Click to collapse
Are you using a 32bit or 64bit machine? If you have SoupKit installed, option 2 should have installed 32bit libs, but sometimes it fails...mostly due to Ubuntu servers and them trying to make 32bit libs obsolete. If you're running a 64bit machine, try installing 32bit libs again and see if you get any errors.
Code:
sudo apt-get install ia32-libs
Also since you have SoupKit installed, run it and select option 4 to launch the Firekit. There's really no difference in using Firekit and manually entering the commands for Rekindle but it makes things a little easier. Select "usb_install_fff_twrp". The important thing to know about the "usb_fix_parts..." and "usb_install..." commands in Firekit is that they both use "fastboot boot ..." instead of "fastboot flash ..." to install TWRP and FFF. Meaning, if you reboot or shut the device down before actually installing a bootloader, the device won't turn back on and you'll have to do the shorting trick again.
That being said, from the moment you make the short, you only have about 2 seconds to plug the device in and have Linux detect it before the CPU resets and you have to start all over again.
Hold the power button for 10-15 seconds to make sure the CPU is off before attempting the short.
Launch Firekit and select "usb_install_fff_twrp". When the command is run, you will get the "Waiting for OMAP4 device..." prompt. Let it wait.
To do the shorting trick...
Something I have found to be most useful in this situation is to use a sharp pair of tweezers or safety pin to make the short.
Keep the device flat on a desk or table with the USB connection pointed away from you. Use one hand to hold the short, one hand to plug the device in, and use your body against the other end of the device as leverage as you plug it in.
Using a safety pin, stick the sharp end of the safety pin into the short point and press it in a little to keep it from sliding off when you plug the device in. Squeeze the other end of the safety pin or tweezers to make contact with the metal frame and immediately plug the device in while holding the short.
If the tweezers slip or make contact with the frame before you are ready, hold the power button for 10-15 seconds to make sure the device is completely shut down and try again.
You should see something going on in the terminal to let you know it's working...let it finish.
It might take a few attempts to get the timing right but persistence (and practice) is key...don't give up.
Follow these instructions and I'm positive you'll get it working again. Good luck.
OK, it's a matter of time and try it.
My computer is 64bit, but I am booting a LiveUSB with Ubuntu 12.10 32bits, so no problem around it.
About the short, one friend of mine solded a thin wire in the point in the board and I only have to connect the other side to the wire to the frame each time, so it also seems to be fine. http://forum.xda-developers.com/attachment.php?attachmentid=1045562&d=1336355873
My main concern: once I manage to make properly the short trick and the process goes forward, what will be the next step? What should I expect of this usb_install_fff_twrp command? Will it fix the hardware detection problem automatically?
Thank you again for all your help, I know you answer a lot this kind of questions and your help is very valuable.
soukron said:
OK, it's a matter of time and try it.
My computer is 64bit, but I am booting a LiveUSB with Ubuntu 12.10 32bits, so no problem around it.
About the short, one friend of mine solded a thin wire in the point in the board and I only have to connect the other side to the wire to the frame each time, so it also seems to be fine. http://forum.xda-developers.com/attachment.php?attachmentid=1045562&d=1336355873
My main concern: once I manage to make properly the short trick and the process goes forward, what will be the next step? What should I expect of this usb_install_fff_twrp command? Will it fix the hardware detection problem automatically?
Thank you again for all your help, I know you answer a lot this kind of questions and your help is very valuable.
Click to expand...
Click to collapse
When the OMAP4 device is detected, you will see something similar to this in the terminal:
http://forum.xda-developers.com/attachment.php?attachmentid=1262650&d=1345043823
That will temporarily install the bootloader, which is likely the cause of Linux not being able to detect it in the first place. When you see the yellow triangle on your Kindle, you'll know the Firekit worked. But you still have to permanently install the bootloader via fastboot (or TWRP if accessible) before you reboot the device.
Will it work to get Linux to detect it? Most likely, but there's no way to know for sure until you get a new bootloader installed.
On second thought...
I just realized you may not even have to do that in the first place. Lucky you? If your device is working properly as you said, boot into Android and open up the Terminal Emulator. Make sure the u-boot.bin is on your sdcard and enter the following:
Code:
su
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
reboot
See if that works.
Yes, working with stock ROM but without root access. If there's any way of rooting it without connecting it to the computer I can do it and then use dd to override the block device.
soukron said:
Yes, working with stock ROM but without root access. If there's any way of rooting it without connecting it to the computer I can do it and then use dd to override the block device.
Click to expand...
Click to collapse
Nope...you need root access to use the 'dd' command.
soupmagnet said:
Nope...you need root access to use the 'dd' command.
Click to expand...
Click to collapse
Dude, thank you for your all work but I'm giving up. I'll close it and use it without data cable. I always can use dropbox like applications to transfer data.
Again, thank you, I really appreciate your help.
soukron said:
Dude, thank you for your all work but I'm giving up. I'll close it and use it without data cable. I always can use dropbox like applications to transfer data.
Again, thank you, I really appreciate your help.
Click to expand...
Click to collapse
If y wer on windows, u could have just grabbed a copy of kindle fire utility and had rooted it in merely seconds..
Sent from my GT-I8350 using Board Express
prahladvarda said:
If y wer on windows, u could have just grabbed a copy of kindle fire utility and had rooted it in merely seconds.
Click to expand...
Click to collapse
Unfortunately, it won't work in this situation.
Kindle stuck on kindle fire logo, try using kindle fire utlity with windows xp and 7(64bit):
xp> 'unkonown device' ("install failedand (unsigned)", In system properties I changed the default driver signing option but nothing)
KFU adb status offline and boot status unknown SOUPKIT nothing
w7> driver ok but unknown usb device when plugin. nothing with KFU or linux+soupkit
tried all with normal usb cable. then opened the back and tried with "short the point". nothing. retry today with a factory cable...nothing!
used also firekit in linux...nothing at all.
I don't know anything about this kindle, because I got it from a friend that got it somewhere!!
In Linux, what is the output of 'lsusb' with the device plugged in?
"That's a special kind of stupid. The kind that makes me laugh."
[email protected]:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 079b:004a Sagem XG-760A 802.11bg
Bus 001 Device 005: ID 058f:6387 Alcor Micro Corp. Transcend JetFlash Flash Drive
Bus 001 Device 006: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
Bus 003 Device 002: ID 0461:0010 Primax Electronics, Ltd
Bus 003 Device 003: ID 0461:4d20 Primax Electronics, Ltd HP Optical Mouse
ADD> could be a problem of the kindles usb? cable ok, tried 2 different
When you tried the short trick, did you use it with Firekit? How exactly did you implement it? Did you make sure the device was completely powered down before trying it?
"That's a special kind of stupid. The kind that makes me laugh."
used firekit and soupkit...tried different ways. kindle completely powered down, short trick, reconnected usb. <waiting for divice> ...so repowered down, ecc ecc...nothing. tried also with factory cable, same results
trinitylau said:
used firekit and soupkit...tried different ways. kindle completely powered down, short trick, reconnected usb. <waiting for divice> ...so repowered down, ecc ecc...nothing. tried also with factory cable, same results
Click to expand...
Click to collapse
Are you using a 32 or 64 bit linux install?
"That's a special kind of stupid. The kind that makes me laugh."
ubuntu-12.04.1-desktop-i386.iso
so...there is something that I can try to do? some advice, some procedure to follow?
In windows, does device manager recognize it?
trinitylau said:
so...there is something that I can try to do? some advice, some procedure to follow?
Click to expand...
Click to collapse
[Edit:] Confused this with another thread
awidawad said:
In windows, does device manager recognize it?
Click to expand...
Click to collapse
xp> 'unkonown device' ("install failedand (unsigned)", In system properties I changed the default driver signing option but nothing)
w7> driver ok but unknown usb device when plugin.
soupmagnet said:
All I can really say is that Firekit works for what it does. What it can't do is make up human error. And I have no way to see exactly what your are doing so I have no idea if your problem is related to your procedure/technique/whatever, or if there is something more going on. The best advice I can giver you is to keep trying...be persistent and don't give up.
Click to expand...
Click to collapse
I followed all the instructions ... keep trying!!
always better to try with linux?
trinitylau said:
I followed all the instructions ... keep trying!!
always better to try with linux?
Click to expand...
Click to collapse
SoupKit will only work with Linux...
Yes, use Linux.
"That's a special kind of stupid. The kind that makes me laugh."
I'll post a custom driver in a bit try it on windows 7 when I post link
---------- Post added at 01:32 PM ---------- Previous post was at 12:55 PM ----------
HERE is the custom driver. Replace the driver in the KFU driver folder with this one, then re-run the driver installation (run.bat) and rename it to "android_winusb.inf" without the quotes
soupmagnet said:
SoupKit will only work with Linux...
Click to expand...
Click to collapse
yes, sorry, I meant to continue with linux
trinitylau said:
yes, sorry, I meant to continue with linux
Click to expand...
Click to collapse
Try the windows 7 drivers... It might work
awidawad said:
I'll post a custom driver in a bit try it on windows 7 when I post link
Click to expand...
Click to collapse
ok, thanks! try also this way!
nothing...driver install without problems but still "unknown usb"
trinitylau said:
nothing...driver install without problems but still "unknown usb"
Click to expand...
Click to collapse
Very strange... What firmware was your device running?
I don't know, I got it from a friend, stuck at kindle fire logo
here's what happened:
flashed new ROM (SmoothROM v1.2) in TWRP 2.2.x.
loaded up new ROM where the dock was missing and the background was black. figured something wrong happened on bootup, so I did a hard reboot. (thinking back on it, I think I forgot to install a launcher, which was really, really dumb of me. I've done this a million times and just assumed if I didn't choose one then it would use a default.)
Kindle Fire logo shows up (no animation), quickly flashes off and back on, and then gets stuck at the CM10.1 boot animation.
I can get my computer (Windows 7 64-bit) to recognize the device as an Android Composite ADB Interface in Device Manager only if I install the drivers manually, otherwise it fails. shows up as Amazon Kindle Fire under Devices and Printers.
it isn't recognized in ADB or KFU, which is my biggest concern. (before all this it was recognized just fine.) it's always "Offline" or "error: device not found" or "waiting for device."
I feel like I've literally tried everything at this point. uninstalled and reinstalled EVERYTHING, different ports, different USB cables, different computers, different OSes, pushing commands through ADB...
does anyone have any solutions or suggestions for me at this point? if you want to know what all I've tried I'd be happy enough to type out all I can remember.
cheers,
Rachel
Do you have FireFireFire installed? Are you able to access TWRP using FireFireFire?
Sent from my KFHD 8.9 using Tapatalk 2
soupmagnet said:
Do you have FireFireFire installed? Are you able to access TWRP using FireFireFire?
Sent from my KFHD 8.9 using Tapatalk 2
Click to expand...
Click to collapse
ha, I was thinking you'd be the first one to respond. I don't know how many of your posts I have read trying to figure out a solution to this problem...
I rooted my KF over a year ago, and if my memory serves me correctly, I never installed FFF...
Shame on you.
You need to get into fastboot so you can access TWRP. Even then, you'll need to be able to send fastboot commands. Windows can compound the issues you're dealing with so to save yourself the trouble, you need to get a Linux LiveUSB set up and install SoupKit. That will make sure your your ability to send and and fastboot commands isn't being hindered by the operating system.
Sent from my KFHD 8.9 using Tapatalk 2
soupmagnet said:
Shame on you.
You need to get into fastboot so you can access TWRP. Even then, you'll need to be able to send fastboot commands. Windows can compound the issues you're dealing with so to save yourself the trouble, you need to get a Linux LiveUSB set up and install SoupKit. That will make sure your your ability to send and and fastboot commands isn't being hindered by the operating system.
Sent from my KFHD 8.9 using Tapatalk 2
Click to expand...
Click to collapse
shame on me indeed.
alright, I'm going to do what you said and report back if I have any problems.
thanks!
got Linux 12.04 and Soupkit. tried the shorting trick today with different commands to no avail. I tried changing the bootmode to Normal and Recovery, then install_fff_twrp_from_stock and usb_fix_parts_and_install_fff_twrp.
am I on the right track? what can I do now?
rachste said:
got Linux 12.04 and Soupkit. tried the shorting trick today with different commands to no avail. I tried changing the bootmode to Normal and Recovery, then install_fff_twrp_from_stock and usb_fix_parts_and_install_fff_twrp.
am I on the right track? what can I do now?
Click to expand...
Click to collapse
I don't think you need to be doing the shorting trick just yet. Just use SoupKit to try and install a new bootloader.
Sent from my KFHD 8.9 using Tapatalk 2
same problem
soupmagnet said:
I don't think you need to be doing the shorting trick just yet. Just use SoupKit to try and install a new bootloader.
Sent from my KFHD 8.9 using Tapatalk 2
Click to expand...
Click to collapse
i am actually facing a somewhat similar issue. i had flashed a jelly bean rom on my KF and then used twrp to flash the stock 6.3.1 however, i dont think i did it right. KF would then reboot every 10 sec. Initially it asked me to force close android.processes.acore and calender storage thing. I was able to get rid of these two msges with a "clear data" on the contact storage and calender storage. But KF still reboots every 5-10 sec.
i also tried using soupkit but in the terminal, it say
/home/navshinder/Desktop/SoupKit/SoupKit/soupkit.sh: line 84: /home/navshinder/bin/SoupKit/adb: Permission denied
/home/navshinder/Desktop/SoupKit/SoupKit/soupkit.sh: line 89: /home/navshinder/bin/SoupKit/fastboot: Permission denied
/home/navshinder/Desktop/SoupKit/SoupKit/soupkit.sh: line 84: /home/navshinder/bin/SoupKit/adb: Permission denied
/home/navshinder/Desktop/SoupKit/SoupKit/soupkit.sh: line 89: /home/navshinder/bin/SoupKit/fastboot: Permission denied
Device Status: Device Offline (press enter to refresh)
Pl help.
i can use both windows 7 and linux mint14
thanks
soupmagnet said:
I don't think you need to be doing the shorting trick just yet. Just use SoupKit to try and install a new bootloader.
Sent from my KFHD 8.9 using Tapatalk 2
Click to expand...
Click to collapse
alright, I tried installing a bootloader with no luck.
navshinder said:
i am actually facing a somewhat similar issue. i had flashed a jelly bean rom on my KF and then used twrp to flash the stock 6.3.1 however, i dont think i did it right. KF would then reboot every 10 sec. Initially it asked me to force close android.processes.acore and calender storage thing. I was able to get rid of these two msges with a "clear data" on the contact storage and calender storage. But KF still reboots every 5-10 sec.
i also tried using soupkit but in the terminal, it say
/home/navshinder/Desktop/SoupKit/SoupKit/soupkit.sh: line 84: /home/navshinder/bin/SoupKit/adb: Permission denied
/home/navshinder/Desktop/SoupKit/SoupKit/soupkit.sh: line 89: /home/navshinder/bin/SoupKit/fastboot: Permission denied
/home/navshinder/Desktop/SoupKit/SoupKit/soupkit.sh: line 84: /home/navshinder/bin/SoupKit/adb: Permission denied
/home/navshinder/Desktop/SoupKit/SoupKit/soupkit.sh: line 89: /home/navshinder/bin/SoupKit/fastboot: Permission denied
Device Status: Device Offline (press enter to refresh)
Pl help.
i can use both windows 7 and linux mint14
thanks
Click to expand...
Click to collapse
You need a factory cable to get into fastboot because you didn't wipe system AND factory reset before
flashing a ROM.
rachste said:
alright, I tried installing a bootloader with no luck.
Click to expand...
Click to collapse
Make sure you're not using a USB3.0 port and post the output of the command 'lsusb' from the terminal.
Sent from my KFHD 8.9 using Tapatalk 2
soupmagnet said:
Make sure you're not using a USB3.0 port and post the output of the command 'lsusb' from the terminal.
Sent from my KFHD 8.9 using Tapatalk 2
Click to expand...
Click to collapse
definitely no USB 3.0. all are 2.0.
here are the results:
[email protected]:~$ lsusb
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 045e:076d Microsoft Corp. LifeCam HD-5000
Bus 001 Device 004: ID 056a:0084 Wacom Co., Ltd
Bus 001 Device 005: ID 1532:0016 Razer USA, Ltd
Bus 001 Device 006: ID 046d:c31b Logitech, Inc. Compact Keyboard K300
Bus 001 Device 007: ID 0bc2:0503 Seagate RSS LLC
Bus 002 Device 003: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 102 Flash Drive / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick
Bus 002 Device 004: ID 045e:0719 Microsoft Corp. Xbox 360 Wireless Adapter
Bus 002 Device 005: ID 1949:0005 Lab126
Click to expand...
Click to collapse
rachste said:
definitely no USB 3.0. all are 2.0.
here are the results:
Click to expand...
Click to collapse
Well that's good, but you may need a factory cable to get into fastboot. Once you can get into fastboot, SoupKit should take care of the rest.
enter the following and post the results:
Code:
lsusb -vd 1949:0006 | grep 'bcdDevice'
soupmagnet said:
Well that's good, but you may need a factory cable to get into fastboot. Once you can get into fastboot, SoupKit should take care of the rest.
enter the following and post the results:
Code:
lsusb -vd 1949:0006 | grep 'bcdDevice'
Click to expand...
Click to collapse
I get no results when I enter that.
[email protected]:~$ lsusb -vd 1949:0006 | grep 'bcdDevice'
[email protected]:~$
Click to expand...
Click to collapse
Erp... 1949:0005
Sent from my KFHD 8.9 using Tapatalk 2
soupmagnet said:
Erp... 1949:0005
Sent from my KFHD 8.9 using Tapatalk 2
Click to expand...
Click to collapse
here we go:
bcdDevice 2.16
Click to expand...
Click to collapse
rachste said:
here we go:
Click to expand...
Click to collapse
Yep, you need a factory cable.
Sent from my KFJWI using Tapatalk 2
soupmagnet said:
Yep, you need a factory cable.
Sent from my KFJWI using Tapatalk 2
Click to expand...
Click to collapse
haha, works for me. thanks for your guidance!
First of all, I've spent many, many hours reading everything and trying everything I could find so sincere apologies if I have missed the solution to my problem.
So I have a Kindle Fire which I got months ago and have never been able to make work. It appears to have been almost completely wiped. It can do two things as of now:
1. Be stuck in a bootloop: displays FireFireFire logo, restarts, rinse, repeat.
2. Get into TWRP
Regardless of which of these states the device is in, neither my Windows PC (which has drivers, SDK, tools etc installed) OR my Ubuntu machine (on which I used SoupKit to install the necessaries) can see the device. It doesn't show in Device Manager in Windows and neither fastboot nor adb show any entries for the device when I run them on EITHER platform and in either of the states I can get the device into.
Any input from people more experienced than me would be appreciated. I got a factory cable in the post today so if that will help I have that option available to go. Oh and finally solutions using my Ubuntu machine rather than the Windows one would be strongly preferred although I can do either if I have to.
Boot into TWRP and see if your device shows up under 'lsusb'
...if it does, then use TWRP to "reboot bootloader" and check 'lsusb' again.
Thanks for the quick reply, and sorry for my slow reply back
The device isn't showing when I run lsusb - I assume you would have mentioned if it was not going to obviously be the KF. Anyway just in case, here is the output:
Bus 001 Device 003: ID 0ac8:c33e Z-Star Microelectronics Corp.
Bus 003 Device 002: ID 04f3:0234 Elan Microelectronics Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Anybody got any insight as to what I should do next?
kindlesean said:
Anybody got any insight as to what I should do next?
Click to expand...
Click to collapse
Is it safe to assume you don't have a factory cable?
Also, does the usb cable you're using seated tightly or is it kind of loose?
If it's loose, try this...
Enter the following command in the terminal (Linux) and try to finagle the USB to see if it is a bad connection:
Code:
while true; do lsusb | grep 'Lab126'; done
If you have a bad connection, due to the cable or USB connector, as soon as a good connection is made you will see it output to the terminal. Just remember to ctrl+c to end the loop when you're done with it.
some inforeff
Hey Thanks for the very quick reply!
I actually do have a factory cable, I bought one this week So if the factory cable is likely to be the easiest way to fix things then I have it ready.
I used multiple different USB cables on the two different machines. Should I still try the thing you mentioned or is there something else I should proceed with using the factory cable?
Thanks for the help Soup.
kindlesean said:
Hey Thanks for the very quick reply!
I actually do have a factory cable, I bought one this week So if the factory cable is likely to be the easiest way to fix things then I have it ready.
I used multiple different USB cables on the two different machines. Should I still try the thing you mentioned or is there something else I should proceed with using the factory cable?
Thanks for the help Soup.
Click to expand...
Click to collapse
Before I switched to the black USB cables from Amazon for their quick chargers, my device would do sort of the same thing. I had to pull up or push down on the connection before it would detect. If you have a factory cable made by Skorpn try that one to see if a connection is made. IIRC, Skorpn's factory cables fit very tightly so it might make a difference. Either way, try what I suggested earlier to rule out any hardware based issues with the USB.
I just tried what you suggested with both two different regular USB to Micro USB cables and also with my factory cable. In all cases there was no output in the terminal. I tried it both from TWRP and from the FFF logo screen (which no longer bootloops btw, it seems to just be hanging at the FFF logo now if I don't press power to get into TWRP).
Thanks again
Anyone able to help further? Situation is still the same as in my last post.
kindlesean said:
Anyone able to help further? Situation is still the same as in my last post.
Click to expand...
Click to collapse
You can try to usbboot, but it would require opening your device.
soupmagnet said:
You can try to usbboot, but it would require opening your device.
Click to expand...
Click to collapse
Thanks for the response.
I can open the device if necessary, right now I have a very expensive paperweight so it's not as if I have anything to lose
I assume that there are guides available for the whole procedure i.e. from opening up the device to doing the usbboot?
kindlesean said:
Thanks for the response.
I can open the device if necessary, right now I have a very expensive paperweight so it's not as if I have anything to lose
I assume that there are guides available for the whole procedure i.e. from opening up the device to doing the usbboot?
Click to expand...
Click to collapse
Check the Firekit thread in the Dev section
soupmagnet said:
Check the Firekit thread in the Dev section
Click to expand...
Click to collapse
Will do, thanks again Soup!