Hi everyone,this is my first post on the XDA forum.Recently,i had installed the Stock Jelly Bean 4.2.1_r1 for the Kindle Fire made by Hashcode.Things have been working well,untill today.I found an app call LCD density modder(2.4.2) and i installed it.After i apply my density change(160 to 200),the system reboot.However,it only passed the Kindle Fire Red logo and then stuck at the Jelly Bean 4.2.1 animation boot.
I have tried to connect the Kindle Fire to my pc and tried to use the Kindle Fire Utility but my ADB is set at offline.I have tried everything,uninstall driver to normal boot-turn off device trick,but none of them has work.I'm a newbie,so this is really confusing for me right now.If anyone know how to fix this,please help me !!!
P.S:Sorry for my bad English.It isn't my native language !!!
UPDATE:
So I've try using Ubuntu 12.10, install Soupkit, It didn't work: ADB status is Offline.
Switch to Ubuntu 12.04. and tried to test something, and I think maybe there is sth wrong.
First I hit this, with my KF plug in
[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:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 046d:c52f Logitech, Inc. Wireless Mouse M305
Bus 001 Device 003: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 001 Device 004: ID 058f:a014 Alcor Micro Corp.
Bus 001 Device 005: ID 0bda:0139 Realtek Semiconductor Corp.
Bus 002 Device 003: ID 8564:1000
Bus 002 Device 007: ID 1949:0005 Lab126
Click to expand...
Click to collapse
Then I remove my KF and did it again, this time it showed this
[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:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 046d:c52f Logitech, Inc. Wireless Mouse M305
Bus 001 Device 003: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 001 Device 004: ID 058f:a014 Alcor Micro Corp.
Bus 001 Device 005: ID 0bda:0139 Realtek Semiconductor Corp.
Bus 002 Device 003: ID 8564:1000
Click to expand...
Click to collapse
So my guess it my PC still recognised it as Lab126.
Then I did another test, I type in
sudo gedit /etc/udev/rules.s/51-android.rules
Click to expand...
Click to collapse
And this showed up:
# adb protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", MODE="0666", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
# fastboot protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
Click to expand...
Click to collapse
So I think that my system need some adjust. Can anyone help me please?
Update: I saw that on when I got lsusb it supposed to say Bus 003 Device 026: ID 1949:0006 Lab126 or something. but I got 0005.
Maybe this is the problem, I don't really know. Can anyone take a look and see what happend to my KF Id.
if you boot to your recovery (twrp) you should have adb available.
then you can set the density back in the build.prop in the system folder.
take care of the permissions !
But i can't boot into TWRP.
My kindle doesn't show up the yellow triangle.It just show up the regular kindle fire logo
gave you a pm ...
I'm trying on Soupkit but it said that "Device Offine", and I really don't know what to do next, first time on Ubuntu and have tried some solutions but they just don't work. Anyone can help?
with ubuntu no drivers are needed - try a other cable first - then maybe contact soupmagnet for further help
Two things...
1) In your PM you said "sudo gedit /etc/udev/rules.d/51-android.rules" opens a blank document, but here you state otherwise. So which is correct?
2) I've seen the PID of 0005 in only one other situation before and it resulted in having to replace the bootloader. But your device has moved past the bootloader and on to the boot animation so your situation may be different...or not. You could try to change your udev rules to match the PID indicated by the device and then reload the udev rules:
Code:
sudo udevadm control --reload-rules
...if that doesn't work, you'll need a factory cable to get the device into fastboot so you can access recovery. Even then, you may be looking at usbboot to fix the bootloader.
"That's a special kind of stupid. The kind that makes me laugh"
1) In your PM you said "sudo gedit /etc/udev/rules.d/51-android.rules" opens a blank document, but here you state otherwise. So which is correct?
Click to expand...
Click to collapse
The PM was wrong, the code when I used was wrong, I type in
Code:
sudo gedit /etc/[B]e[/B]dev/rules.d/51-android.rules
So It was obviously wrong ( but I copy the code from your thread )
Gonna try your suggestion now, Right now I'm in Window so can't try it yet.
Try to get a factory cable in a day or two. May have to build one myself because I live in Vietnam. Or I can try to buy one from China, idk.
Posting the result soon, I hope.
Can one of you guys PM me? I came through a page on the Internet (which XDA won't allow me to post) and I think I found a guy who successfuly solved one similar problem. But I don't understand what he said, so can you help me. The link is on linuxsleuthing blogspot, page :Rubbing Sticks: Lighting The Kindle Fire . Plz have a quick look
raulmadrid1998 said:
Gonna try your suggestion now, Right now I'm in Window so can't try it yet.
Try to get a factory cable in a day or two. May have to build one myself because I live in Vietnam. Or I can try to buy one from China, idk.
Posting the result soon, I hope.
Click to expand...
Click to collapse
What an interesting coincidence...the one other situation where I've seen a PID of 0005 was from a guy in Vietnam. I wonder if there is a connection somehow.
raulmadrid1998 said:
Can one of you guys PM me? I came through a page on the Internet (which XDA won't allow me to post) and I think I found a guy who successfuly solved one similar problem. But I don't understand what he said, so can you help me. The link is on linuxsleuthing blogspot, page :Rubbing Sticks: Lighting The Kindle Fire . Plz have a quick look
Click to expand...
Click to collapse
Everything that guy is talking about, is done automatically in SoupKit when you install it.
Get your factory cable then we can work from there.
Please help
b63 said:
gave you a pm ...
Click to expand...
Click to collapse
My kindles TWRP is gone after i tried installing the kindle os so i can remove jelly bean. Now my kindle wont boot, and wont show up in KFU so i can fix it. When i turn it on it show KINDLE FIRES original logo bright then black outs in like 5 seconds and show it again with a dimmer light. Do you have any idea how i can fix this because ive been searching for 4 weeks now and cant find one thing. thank you.
4 weeks really? Okay well a couple things did you do a full wipe when you flashed stock? My guess is no. What was the charge level of your battery when you flashed update.zip? If you didn't do a full wipe your kindle is stuck trying to handle the data left behind. This requires a factory cable to fix. If your battery was near depleted when you flashed it the problem could be compounded by a 5 second boot loop. My guess is the prior improperly flashing of stock without a full wipe buying a cable and leaving it on charger is your best bet for a fix. Cables can be puchased here http://forum.xda-developers.com/showthread.php?t=1392693 post 9 and worth every penny. Good luck
Related
Hi,
I have a European SGS for a couple of day's now. I have flashed it with JG5 and mimocans lagfix. I have done this with a WinXP virtualbox on an Ubuntu desktop. This worked perfectly. But what I like to do is to work with ADB straight from my Linux box. The problem is that it won't detect my SGS (I have the 'USB Debugging' option on off-course).
When I type prompt> adb devices , my device won't show up. In the WinXP virtualbox it does show up. Can anybody help me on this one?
Kind Regards,
D.
You have to:
sudo adb start-server
adb devices #It works!
adb shell #Or whatever you want.
Hi,
Just tried that but still not working for me? Any other ideas?
Regards,
D.
I didn't have a problem under FC12.
I note you said you were using VirtualBox - you aren't doing something stupid like forwarding the USB port through to Virtual Box so it's not accessible to the base OS?
Cheers
Simon
No my Virtualbox is not running at the moment, so the USB port is not forwarded to the Virtualbox. I'm able to mount the device and copy files to it etc. But ADB doesn't recognize it. With my HTC Hero it worked perfectly. :-(
denvro said:
No my Virtualbox is not running at the moment, so the USB port is not forwarded to the Virtualbox. I'm able to mount the device and copy files to it etc. But ADB doesn't recognize it. With my HTC Hero it worked perfectly. :-(
Click to expand...
Click to collapse
You need to enable debug mode.
lenrek said:
You need to enable debug mode.
Click to expand...
Click to collapse
But if he can see it in XP, when it's started, maybe it's already enabled.
Run a
'lsusb' in the command line, is Samsung device there?
japanfred said:
But if he can see it in XP, when it's started, maybe it's already enabled.
Run a
'lsusb' in the command line, is Samsung device there?
Click to expand...
Click to collapse
Hmm... Maybe he should just disable/delete the USB device from the virtual box. Maybe the service has reserve the device even when the guest is not started?
lenrek said:
You need to enable debug mode.
Click to expand...
Click to collapse
When you've read my initial post you could have read that USB debugging is already enabled.
japanfred said:
Run a 'lsusb' in the command line, is Samsung device there?
Click to expand...
Click to collapse
This is the output of 'lsusb' when the device is connected:
Bus 001 Device 016: ID 04e8:681c Samsung Electronics Co., Ltd
Bus 001 Device 004: ID 058f:6362 Alcor Micro Corp. Hi-Speed 21-in-1 Flash Card Reader/Writer (Internal/External)
Bus 001 Device 002: ID 04a9:172b Canon, Inc. MP140 ser
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 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 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
The Samsung device is showing up.
denvro said:
When you've read my initial post you could have read that USB debugging is already enabled.
This is the output of 'lsusb' when the device is connected:
Bus 001 Device 016: ID 04e8:681c Samsung Electronics Co., Ltd
Bus 001 Device 004: ID 058f:6362 Alcor Micro Corp. Hi-Speed 21-in-1 Flash Card Reader/Writer (Internal/External)
Bus 001 Device 002: ID 04a9:172b Canon, Inc. MP140 ser
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 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 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
The Samsung device is showing up.
Click to expand...
Click to collapse
Maybe you want to try disable USB in your virtualbox setting.
Deleted USB settings in Virtualbox, disabled USB in all my Virtual machines but no luck. My device still doesn't show up in ADB.
Hope somebody else has some tips?
Problem Solved
I solved the problem by updating to the latest Android SDK. Thanks for helping everyone.
i have always had to sudo gedit etc/udev/rules.d/51.android.rules and individually add my device by USB code (ie. SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="681c", MODE="0666" or similar)to get it to work
hi together,
at first, sorry for my bad english, ...i'm from germany.
some time, i was owner of a rooted and flashed KF which worked fine. 6 days before, i installed google play and the keyboard was offline. i went back in twrp 2.2.2.1 and make a wipe and forgot, that i need the software to flash it again. i'm an idiot, i know.
now, i only have twrp in recovery and don't know what to do. i'm not confirm with linux/ubuntu and the handling of soupkit.
facts i have at the moment:
- a KF with twrp 2.2.2.1
- my 2nd pc with a brandnew ubuntu 12.10
- information, that my KF was found on usb in bootloop and twrp, see below:
[email protected]:~$ lsusb
Bus 001 Device 006: ID 18d1:d002 Google Inc.
Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
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
Bus 001 Device 009: ID 1949:0006 Lab126
Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
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]:~$
"Google Inc" and "Lab126" ist the same. google in bootloop and lab126 in recovery mode.
can anybody help me with ubuntu and soupkit, that i can transfer a flashfile to my KF ?
with best regards, stefan
PROBLEM SOLVED - THX
Does your computer recognize the kf? If it does, then why not transfer a rom to it & flash it in twrp?
BrooklynNY said:
Does your computer recognize the kf? If it does, then why not transfer a rom to it & flash it in twrp?
Click to expand...
Click to collapse
thanks a lot :angel:
five minutes before, i found a threadto do just this :good:
at the moment ii try it and i hop it works with aliendroid v8, ....now i will see if this rom has german language.
and a question: whats in your opinion the best rom for a KF ?
das_es said:
hi together,
at first, sorry for my bad english, ...i'm from germany.
some time, i was owner of a rooted and flashed KF which worked fine. 6 days before, i installed google play and the keyboard was offline. i went back in twrp 2.2.2.1 and make a wipe and forgot, that i need the software to flash it again. i'm an idiot, i know.
now, i only have twrp in recovery and don't know what to do. i'm not confirm with linux/ubuntu and the handling of soupkit.
facts i have at the moment:
- a KF with twrp 2.2.2.1
- my 2nd pc with a brandnew ubuntu 12.10
- information, that my KF was found on usb in bootloop and twrp, see below:
[email protected]:~$ lsusb
Bus 001 Device 006: ID 18d1:d002 Google Inc.
Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
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
Bus 001 Device 009: ID 1949:0006 Lab126
Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
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]:~$
"Google Inc" and "Lab126" ist the same. google in bootloop and lab126 in recovery mode.
can anybody help me with ubuntu and soupkit, that i can transfer a flashfile to my KF ?
with best regards, stefan
Click to expand...
Click to collapse
Actually, your problem may be easier to fix than you think.
1) Download a ROM of your choosing to your computer (for stock, choose MoDaCo).
2) Boot the device into recovery (use SoupKit if you need to) and select the "Mount" function.
3) Make sure there is an [X] next to Mount SDcard (you should actually see "[X] Unmount SDcard" when it's selected)
4) In Linux, you should get a prompt asking what you want to do with the mounted volume. Select "view folder" or something similar. Or you could open your file manager and look for it under devices.
5) Transfer the ROM to your sdcard.
6) Wipe system, factory reset then install the ROM.
only TWRP on my KF - PROBLEM SOLVED
thx to all, it was easier to solve this problem as i thought.
i'm really happy now
my wife is happy too. now it's her's and i can by an galaxy note 10.1
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
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!
Hello,
I've been looking into rooting my phone and I have ran into a problem.
I've downloaded everything. adb the files to root my phone etc. But im stuck on trying to find my device
(running kali linux )
i enter the command to locate it in terminal but nothing shows up:
[email protected]:~# adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:~# adb devices
List of devices attached
<----- (is just blank)
ive tried running [lsusb] and it doesnt show up either:
[email protected]:~# lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 064e:d213 Suyin Corp.
Bus 001 Device 003: ID 04ca:3005 Lite-On Technology Corp.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
it seems like my machine doesnt even say its there. Debugging has been checked off, ive changed the usb input or what ever from charge only to mtp to ptp and none of those work either.
first time posting ever on the form since ive spent three days trying to trouble shoot this but yet to come up with something. please help so i can run my phone as root lol!
nieev said:
Hello,
I've been looking into rooting my phone and I have ran into a problem.
I've downloaded everything. adb the files to root my phone etc. But im stuck on trying to find my device
(running kali linux )
i enter the command to locate it in terminal but nothing shows up:
[email protected]:~# adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:~# adb devices
List of devices attached
<----- (is just blank)
ive tried running [lsusb] and it doesnt show up either:
[email protected]:~# lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 064e:d213 Suyin Corp.
Bus 001 Device 003: ID 04ca:3005 Lite-On Technology Corp.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
it seems like my machine doesnt even say its there. Debugging has been checked off, ive changed the usb input or what ever from charge only to mtp to ptp and none of those work either.
first time posting ever on the form since ive spent three days trying to trouble shoot this but yet to come up with something. please help so i can run my phone as root lol!
Click to expand...
Click to collapse
EDIT: I hit enter WAY too quick lol
Do you have the proper USB drivers set up?
Check out this link. It probably has the instructions you need, even though it is for Ubuntu.
EDIT#2: I haven't used Linux in forever, but someone I was just talking to said "shouldn't it be sudo adb devices? I think he was right.
Seems like you have a lot of devices, and possibly a USB hub? Make sure you haven't connected through a hub, which can cause issues.
You're booted into OS when trying to issue adb command (which is required) or alternately custom recovery? Some folks mistakenly believe they can connect adb with phone in bootloader (only fastboot works in bootloader - and it has to be in fastboot mode).
woo hoo stupid fix
I figured it out. Anyone who has this same issue as me sometimes switching usb cords works thanks guys