Related
Hey all, trying to push gtalk library files to MildWild 4.3 system dir has turned into a massive headache.
ADB doesn't recognize I have my device connected. Commands always return "error:device not found". "adb devices" command returns blank.
From the tutorials I've read in these forums, I was under the impression HTC Sync drivers in fastboot mode are needed to use ADB. No dice. I've tried other drivers I've found in the forms as well: "android-usb-driver.zip" from unrevoked and "adb_driver_htc.zip" (found this in the sim unlock utility thread).
Any suggestions on how to troubleshoot this further?
What is the proper name of the device in device manager? Right now I'm using HTC Sync drivers in fastboot and the name is: Android USB Devices > My HTC.
The guides I've read never touch on this issue, they always skip it and assume the device is connectable.
Thanks in advance
JT-on said:
Right now I'm using HTC Sync drivers in fastboot and the name is: Android USB Devices > My HTC.
Click to expand...
Click to collapse
To use ABD you need to be connected in recovery or a booted device.
nlooooo said:
To use ABD you need to be connected in recovery or a booted device.
Click to expand...
Click to collapse
Brilliant. Like you said, ADB recognized my device in both booted OS and recovery. However, I needed to be in recovery to push files to the system directory. Thanks.
You're welcome. You can push in booted device you just need to enable superuser rights in adb shell.
Sent from my HTC Desire using Flashes and Thunders
JT-on said:
Hey all, trying to push gtalk library files to MildWild 4.3 system dir has turned into a massive headache.
ADB doesn't recognize I have my device connected. Commands always return "error:device not found". "adb devices" command returns blank.
From the tutorials I've read in these forums, I was under the impression HTC Sync drivers in fastboot mode are needed to use ADB. No dice. I've tried other drivers I've found in the forms as well: "android-usb-driver.zip" from unrevoked and "adb_driver_htc.zip" (found this in the sim unlock utility thread).
Any suggestions on how to troubleshoot this further?
What is the proper name of the device in device manager? Right now I'm using HTC Sync drivers in fastboot and the name is: Android USB Devices > My HTC.
The guides I've read never touch on this issue, they always skip it and assume the device is connectable.
Thanks in advance
Click to expand...
Click to collapse
90% of the time the problem is with the drivers etc. Use this tutorial to fix that : http://goo.gl/OS3Vi
If you still encounter the problem then you can use ADBwireless available at google play to wirelessly connect your device to the computer
Hope it helps :highfive:
Unchecking MTP did it. Thanks!!
Why is that necessary on the N7Flo but not my old N7 or the N4 (or any other device I've had contact with for that matter)?
Also, anyone know how I can get devices to show up as a folder...you know...like a thumb drive?
rmp5s said:
Unchecking MTP did it. Thanks!!
Why is that necessary on the N7Flo but not my old N7 or the N4 (or any other device I've had contact with for that matter)?
Also, anyone know how I can get devices to show up as a folder...you know...like a thumb drive?
Click to expand...
Click to collapse
You can't. Both the n4 and the n7 have their memorys formatted as ext4, partition type that windows can't access normally. MTP was the only sollution google had.
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,
I'm trying to unlock bootloader on my GNex but unfortunately, when i reboot it in fastmode (through adb reboot-bootloader or pressing VOL- , VOL+ and POWER), the device do nothing: It shows an android with "the chest open", in the top of the it shows "START" but any button works and when i try fastboot devices command, i have no response. i try to see if there is any device connected through lsusb, but the device doesn't appears.
It seems to be stuck and the only way to reboot in normal mode is removing the battery.
Anyone could help me?
Thanks,
xekin
More info about:
This is what is shown in fastboot mode:
FASTBOOT MODE
PRODUCT NAME - tuna
VARIANT - maguro
HW VERSION - 9
BOOTLOADER VERSION - PRIMEKK15
BASEBAND VERSION - I9250XXLJ1
CARRIER INFO - NONE
SERIAL NUMBER - 1234123414341
SIGNING - production
LOCK STATE - LOCKED
How can i re-install or re-flash "fastboot mode"? I tried flashing OMAP4440 but nothing happened. I've tried to access to fastboot from win7, win8 and ubuntu. In all of them adb works correctly.
It seems that your bootloader is fine. Reinstall driver and fastboot file, and do the right unlock command.
Sent from my Galaxy Nexus using xda premium
samersh72 said:
It seems that your bootloader is fine. Reinstall driver and fastboot file, and do the right unlock command.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Read closer. OP isn't using Windows. lsusb is a Linux command - plus he stated he already tried under Windows and it worked. Under Windows, it seems OP hasn't told device manager what driver the device should use, WHEN connected in fastboot mode.
OP, search ' android udev rules' then follow instructions. And maybe you're not seeing the device under lsusb because you're not allowed to (yet). In the meantime, you can use 'sudo lsusb' to escalate permissions.
Then, install android SDK and/or update your existing versions.
Still, it's not clear, OP, do your hardware keys work? I mean, can you press up or down, and see the other options like Recovery etc?
Sent from my Nexus
bk201doesntexist said:
Read closer. OP isn't using Windows. lsusb is a Linux command - plus he stated he already tried under Windows and it worked. Under Windows, it seems OP hasn't told device manager what driver the device should use, WHEN connected in fastboot mode.
OP, search ' android udev rules' then follow instructions. And maybe you're not seeing the device under lsusb because you're not allowed to (yet). In the meantime, you can use 'sudo lsusb' to escalate permissions.
Then, install android SDK and/or update your existing versions.
Still, it's not clear, OP, do your hardware keys work? I mean, can you press up or down, and see the other options like Recovery etc?
Sent from my Nexus
Click to expand...
Click to collapse
Thanks for your responses
Actually, I did it lot of times, different drivers version (google, samsung) in diferent OS, but always the same result. In linux I checked that the properly udev config file is set:
cat /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"
One for google and the other for samsung,
In bootloader, any button works, It is a bit annoying because, I watched a lot of youtube videos in which the START message changes when UP/DOWN buttons are pushed. (To recovery for example)
Now, after tested with adt included adb/fastboot commands, I'm testing with the command included in ubuntu platform (wiki.ubuntu.com/Touch/Install). But it doesn't work neither
I followed also some tutos about odin (one of them was yours), but it neither recognizes my gnex.
xekin said:
Thanks for your responses
Actually, I did it lot of times, different drivers version (google, samsung) in diferent OS, but always the same result. In linux I checked that the properly udev config file is set:
cat /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"
One for google and the other for samsung,
In bootloader, any button works, It is a bit annoying because, I watched a lot of youtube videos in which the START message changes when UP/DOWN buttons are pushed. (To recovery for example)
Now, after tested with adt included adb/fastboot commands, I'm testing with the command included in ubuntu platform (wiki.ubuntu.com/Touch/Install). But it doesn't work neither
I followed also some tutos about odin (one of them was yours), but it neither recognizes my gnex.
Click to expand...
Click to collapse
anyone has this problem? i mean if there is someone who has a gnex which doesn't response when he pushes up,down buttons?it looks like frozen, and the usb doesn't seem to work
xekin said:
Thanks for your responses
Actually, I did it lot of times, different drivers version (google, samsung) in diferent OS, but always the same result. In linux I checked that the properly udev config file is set:
cat /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"
One for google and the other for samsung,
In bootloader, any button works, It is a bit annoying because, I watched a lot of youtube videos in which the START message changes when UP/DOWN buttons are pushed. (To recovery for example)
Now, after tested with adt included adb/fastboot commands, I'm testing with the command included in ubuntu platform (wiki.ubuntu.com/Touch/Install). But it doesn't work neither
I followed also some tutos about odin (one of them was yours), but it neither recognizes my gnex.
Click to expand...
Click to collapse
Is your user in group "plugdev"? 'gpasswd -a <user> <group>' as root
Run fastboot with root privileges enabled
bk201doesntexist said:
Is your user in group "plugdev"? 'gpasswd -a <user> <group>' as root
Run fastboot with root privileges enabled
Click to expand...
Click to collapse
Thanks
yep, it doesn't work with my user or root. this is what i see with a dmesg when fastboot mode:
hub 2-0:1.0: connect-debounce failed, port 1 disabled
Click to expand...
Click to collapse
Any idea?
xekin said:
Thanks
yep, it doesn't work with my user or root. this is what i see with a dmesg when fastboot mode:
Any idea?
Click to expand...
Click to collapse
seems to be quite an old bug on Ubuntu (https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88530)
use another usb port/controller?
are you connecting the device to a USB HUB? More devices connected to the PC?
change usb cables?
try to update your kernel to latest (3.9.x) ?
is this a laptop? try to remove the battery, wait like 10min, turn it on again
same prolem nexus 4
I am having the same problem with my nexus 4 sometimes it connects and then desconnects what can i do ?Please help!! :crying::crying::crying::crying::crying:
xekin said:
More info about:
This is what is shown in fastboot mode:
FASTBOOT MODE
PRODUCT NAME - tuna
VARIANT - maguro
HW VERSION - 9
BOOTLOADER VERSION - PRIMEKK15
BASEBAND VERSION - I9250XXLJ1
CARRIER INFO - NONE
SERIAL NUMBER - 1234123414341
SIGNING - production
LOCK STATE - LOCKED
How can i re-install or re-flash "fastboot mode"? I tried flashing OMAP4440 but nothing happened. I've tried to access to fastboot from win7, win8 and ubuntu. In all of them adb works correctly.
Click to expand...
Click to collapse
did u change your bootloader version?
should be PRIMELC03 from stock.. KK15 was the old version. that why u got this issues. just back to stock version (newest).
try boot to odin bootloader (long press volume down + power button). if your phone can boot to odin then install the odin toolkit (pc)
I was using KFU (0.9.9) to install TWRP. When it went to reboot into fastboot mode, the kindle fire boot logo (stock) appeared and the power light turned green. It is now stuck like this. KFU and Windows 7 does not recognize the kindle. I have tried turning it off and back on, but it just goes back to the same screen.
kindlestuck said:
I was using KFU (0.9.9) to install TWRP. When it went to reboot into fastboot mode, the kindle fire boot logo (stock) appeared and the power light turned green. It is now stuck like this. KFU and Windows 7 does not recognize the kindle. I have tried turning it off and back on, but it just goes back to the same screen.
Click to expand...
Click to collapse
[HOW-TO] Before asking for troubleshooting help...
Frequently Asked Questions - Amazon Kindle Fire
[GUIDE] Kindle Fire For Beginners
[HOW-TO] Root / Install a ROM / Unroot / Revert to Stock (A KFFB Supplement)
He has all of the drivers installed, but KFU seems to have an issue with file paths. I have redownloaded it for him and I also updated his copy of the SDK with Kindle Fire drivers and a newer ADB. The KFU returns an error "System cannot find the path specified for everything, even though it is extracted straight out of the zip it came in. All he did was choose install TWRP and it didn't even make it to fastboot mode before it bricked.
Zeklandia said:
He has all of the drivers installed, but KFU seems to have an issue with file paths. I have redownloaded it for him and I also updated his copy of the SDK with Kindle Fire drivers and a newer ADB. The KFU returns an error "System cannot find the path specified for everything, even though it is extracted straight out of the zip it came in. All he did was choose install TWRP and it didn't even make it to fastboot mode before it bricked.
Click to expand...
Click to collapse
Thank you for your insight, but all the information needed to fix what is a very common problem can be found in the threads to which links have been provided. The device IS in fastboot. Simply changing the bootmode is the key to resolving the problem. That being said, the KFU is not the end all/be all to changing the bootmode or installing TWRP.
soupmagnet said:
Thank you for your insight, but all the information needed to fix what is a very common problem can be found in the threads to which links have been provided. The device IS in fastboot. Simply changing the bootmode is the key to resolving the problem. That being said, the KFU is not the end all/be all to changing the bootmode or installing TWRP.
Click to expand...
Click to collapse
It is not in fact in fastboot, it is not even listed in adb devices or fastboot devices.
---------- Post added at 12:52 PM ---------- Previous post was at 12:29 PM ----------
I have a feeling it is trying to boot into stock recovery, as KFU was trying to reboot into TWRP (which never installed because KFU was broken).
---------- Post added at 12:55 PM ---------- Previous post was at 12:52 PM ----------
If we can get out of stock recovery, that would be useful. Do you have any idea how to bring up the menu in stock recovery? Does he need to hold the power button down or press it in a pattern?
Zeklandia said:
It is not in fact in fastboot, it is not even listed in adb devices or fastboot devices.
Click to expand...
Click to collapse
While some who know me better may be prepared to see me respond in my usual manner at this point, I have instead, decided to play nice
I have been a member of this forum for quite some time and have seen hundreds of different problems in just as many scenarios for each, and I can assure you, without even a shred of doubt, that the device is in fact in fastboot mode (unless, of course, the information provided in the OP is inaccurate).
You can find information for properly identifying fastboot mode in the "Frequently Asked Questions" thread and the "Fastboot Guide" linked to within it, so please feel free to prove me wrong.
With that,
Just because the device itself doesn't respond to fastboot commands from the computer, doesn't mean the device isn't in fastboot mode. It simply means (in this case) that the drivers are not properly installed or configured, despite the steps taken to do so. Windows is very tricky when it comes to installing drivers for Android and there are hundreds of posts within these forums that should be able to convince you of that. If you want to eliminate all doubt and ensure that driver problems aren't just compounding the issue, set up a Linux LiveUSB and either install SoupKit, or configure it manually to communicate with the device via USB so that adb and fastboot commands will work properly.
Good luck
I appreciate you trying to help, but his device is 100% stock. KFU has set it to boot into recovery, and it will continue to boot into the stock recovery until we can find a way to change that idme bootmode. Tomorrow, I will attempt to use my factory cable on it, but for now all fastboot does is wait for device. I use Linux, so if it truly is in fastboot mode, then it should have no problem, especially with the factory cable.
Zeklandia said:
I appreciate you trying to help, but his device is 100% stock. KFU has set it to boot into recovery, and it will continue to boot into the stock recovery until we can find a way to change that idme bootmode. Tomorrow, I will attempt to use my factory cable on it, but for now all fastboot does is wait for device. I use Linux, so if it truly is in fastboot mode, then it should have no problem, especially with the factory cable.
Sent from my Battle Droid
Click to expand...
Click to collapse
Looking at your signature, I see that you are technically competent enough to take a look at the KFU 'run.bat' and see how it works. When the option to install TWRP is selected, the script uses Pokey9000's 'fbmode' to boot into fastboot mode. Once KFU is able to detect the device in fastboot, it then uses fastboot commands to flash TWRP to the recovery partition and then reboot to recovery. If the KFU were able to detect the device in fastboot mode and TWRP was not installed due to file paths, then the device would still boot into the stock recovery, normally, and you would see plenty of error messages giving you a clue as to what went wrong. Messages in the KFU window compared to those found in the script itself can also show you where things went wrong.
What happens (more times than I care to try and estimate) is, due to the way Windows handles Android drivers, when the device is put into fastboot mode (even though adb commands were working at the time), the fastboot drivers aren't working properly, the script cannot move forward and the device gets stuck in fastboot mode.
As I mentioned earlier, the "Fastboot Guide" linked to in the FAQ, tells you how to recognize fastboot mode beyond all uncertainty. With all due respect, I'd suggest you look into it before deciding that you know best in this particular situation.
And not to make assumptions about your level of proficiency with Linux, but don't forget that you have to either set up udev rules for the device, or run your fastboot commands as root for it to work properly.
same issue...
yes perhaps you should be a little more sympathic to the OP as 1. he probably has a valid issue (im having the same problem...neither windows nor Soupkit is recognizing my KF thats stuck in the white and orange logo fastboot and 2. none of the above links help this problem in any manner. I have been researching this issue for days now and have tried a few different distros (just my luck Mint's persistance didnt work...sigh) and no matter what, my computer will not communicate with the KF.
it seems my KF is now bricked because I ran the KFU and selected install "FireFireFire" before rooting...it sure would have been nice if some sort of warning would have popped up asking "ARE YOU SURE YOU WANT TO DO THIS and HAVE YOU CHECKED THAT YOU ARE CURRENTLY ROOTED??" because it sure seems that ANYONE making the big mistake i did of trying to install fff without first having root would have this same problem.
if you have any other suggestions it sure would be appreciated...thanks.
menriquez said:
yes perhaps you should be a little more sympathic to the OP as 1. he probably has a valid issue (im having the same problem...neither windows nor Soupkit is recognizing my KF thats stuck in the white and orange logo fastboot and 2. none of the above links help this problem in any manner. I have been researching this issue for days now and have tried a few different distros (just my luck Mint's persistance didnt work...sigh) and no matter what, my computer will not communicate with the KF.
it seems my KF is now bricked because I ran the KFU and selected install "FireFireFire" before rooting...it sure would have been nice if some sort of warning would have popped up asking "ARE YOU SURE YOU WANT TO DO THIS and HAVE YOU CHECKED THAT YOU ARE CURRENTLY ROOTED??" because it sure seems that ANYONE making the big mistake i did of trying to install fff without first having root would have this same problem.
if you have any other suggestions it sure would be appreciated...thanks.
Click to expand...
Click to collapse
Make no mistake about it...I am sympathetic to every single person who "bricks" their device. However, I find it very hard to be sympathetic to those who fail to take personal responsibility for a problem they created due to not having done the appropriate amount of research before getting involved in something they didn't understand.
First off, your device does not have to be rooted to install FireFireFire. As a matter of fact, it's better that you install FireFireFire before trying to root...but your drivers have to be in working order from the start. And you have absolutely NO RIGHT to push blame on someone else just because you don't have the knowledge necessary to modify your device without tools made by other people. It is your device and your responsibility...so own up to it.
Second, I can say beyond all uncertainty that the information needed to understand and resolve yours and 90% of all other situations in this forum, can be found in those 4 links posted earlier. But since no one seems to want to believe that, I guess I'll just have to prove it to you.
1) Being stuck at the Kindle Fire logo means your device is in one of two states; in fastboot mode, or in normal mode but without a working system to boot to. This is explained in both the Frequently Asked Questions thread and the Fastboot Guide thread linked to within it. FAQ #16, Fastboot Guide
2) Also explained in the threads mentioned previously, is information on determining what state the device is in by paying attention to the behavior of the Kindle Fire logo as the device starts up. If the Kindle Fire is displayed brightly and stays brightly lit indefinitely, the device is in fastboot mode. If the Kindle Fire logo is brightly lit for a few seconds then flashes and/or goes dim, then it is trying to boot normally to a non-working system. With that knowledge, you can easily determine your next course of action...also based on the information found in the links provided. FAQ #16, Fastboot Guide
3) The key to fixing 99% of all Kindle Fire problems is getting access to custom recovery. There are two ways to access custom recovery when your device is malfunctioning, through FireFireFire, or through fastboot. If you don't have FireFireFire installed, the only option you have left is fastboot. If the device is trying to boot normally to a non-working system, then your only option for accessing fastboot is with a factory cable. FAQ #16, 17, 26, 29, 32, 33, Fastboot Guide
4) If your device is already in fastboot mode, and you are unable to change your bootmodes with the command line in Windows, it is because your drivers aren't properly installed. There is no other possible scenario. FAQ #14, KFFB - post #3
5) If you are using Windows, and you are unable to fix your drivers despite the wealth of information available to you for getting the drivers to work properly, then you use use Linux. FAQ #15
Your situation is no different. If I were to make an educated guess, I would say device is stuck in fastboot mode because your drivers weren't working properly...and you only have Microsoft to blame for that. As for Linux, it will not communicate your device using ADB or fastboot automatically. You have to either run the commands as the root user, or set up udev rules for your device. If you used the SoupKit to set up your udev rules using a LiveUSB, you have to have working persistence. The way it's configured now is to reboot in order for the udev rules to be loaded. If you don't have working persistence, everything you did prior to the reboot will be lost (This is also explained to you in the SoupKit thread).
With that being said, you have NO RIGHT to get offended if I would rather post a few links and expect the user to do the appropriate amount of research on their own to fix a problem THEY CREATED, than spend my personal time to tell every single user that comes to this forum with the exact same problems, everything that I have told you just now.
I wish you the best of luck in getting your device fixed, and I have no qualms about providing you support for the things in the aforementioned threads that you don't understand. But I WILL NOT hold your hand and tell you every single little thing that you need to know in order for you to fix your own device.
soupmagnet said:
Make no mistake about it...I am sympathetic to every single person who "bricks" their device. However, I find it very hard to be sympathetic to those who fail to take personal responsibility for a problem they created due to not having done the appropriate amount of research before getting involved in something they didn't understand.
First off, your device does not have to be rooted to install FireFireFire. As a matter of fact, it's better that you install FireFireFire before trying to root...but your drivers have to be in working order from the start. And you have absolutely NO RIGHT to push blame on someone else just because you don't have the knowledge necessary to modify your device without tools made by other people. It is your device and your responsibility...so own up to it.
Click to expand...
Click to collapse
wow...sigh...listen the last thing my post tried to do is shift blame...i CLEARLY stated *I* made a BIG MISTAKE didn't I?? i dont need a flame war here sheesh im just trying to fix this ****ty kindle for a buddy.
Second, I can say beyond all uncertainty that the information needed to understand and resolve yours and 90% of all other situations in this forum, can be found in those 4 links posted earlier. But since no one seems to want to believe that, I guess I'll just have to prove it to you.
1) Being stuck at the Kindle Fire logo means your device is in one of two states; in fastboot mode, or in normal mode but without a working system to boot to. This is explained in both the Frequently Asked Questions thread and the Fastboot Guide thread linked to within it.
2) Also explained in the threads mentioned previously, is information on determining what state the device is in by paying attention to the behavior of the Kindle Fire logo as the device starts up. If the Kindle Fire is displayed brightly and stays brightly lit indefinitely, the device is in fastboot mode. If the Kindle Fire logo is brightly lit for a few seconds then flashes and/or goes dim, then it is trying to boot normally to a non-working system. With that knowledge, you can easily determine your next course of action...also based on the information found in the links provided.
3) The key to fixing 99% of all Kindle Fire problems is getting access to custom recovery. There are two ways to access custom recovery when your device is malfunctioning, through FireFireFire, or through fastboot. If you don't have FireFireFire installed, the only option you have left is fastboot. If the device is trying to boot normally to a non-working system, then your only option for accessing fastboot is with a factory cable.
4) If your device is already in fastboot mode, and you are unable to change your bootmodes with the command line, it is because your drivers aren't properly installed. There is no other possible scenario.
5) If you are using Windows, and you are unable to fix your drivers despite the wealth of information available to you for getting the drivers to work properly, then you use Linux.
Click to expand...
Click to collapse
lol i read and did ALL of that my chippy friend...the logo starts and stays bright so im sure im in fastboot mode. i got the latest ubuntu on a pen, like i said after i tried Mint 15 and discovered that persistence on a pen doesn't work well with that distro currently. ubuntu did, and in fact recognizes all my other android devices no problem...but nothing at all when i plug the kindle
Your situation is no different. If I were to make an educated guess, I would say device is stuck in fastboot mode because your drivers weren't working properly...and you only have Microsoft to blame for that. As for Linux, it will not communicate your device using ADB or fastboot automatically. You have to either run the commands as the root user, or set up udev rules for your device. If you used the SoupKit to set up your udev rules using a LiveUSB, you have to have working persistence. The way it's configured now, is to reboot in order for the udev rules to be loaded. If you don't have working persistence, everything you did prior to the reboot will be lost (This is also explained to you in the SoupKit thread).
Click to expand...
Click to collapse
like i said both in my original post and above, i figured out the persistence issue its working now. the reboot loaded the rules but when the script runs im getting two errors which, due to my deep frustration at the time i didn't write down the exact wording. i figured i'd chill for a while and then try again later.
With that being said, you have NO RIGHT to get offended if I would rather post a few links and expect the user to do the appropriate amount of research on their own to fix a problem THEY CREATED, than spend my personal time to tell every single user that comes to this forum with the exact same problems, everything that I have told you just now.
I wish you the best of luck in getting your device fixed, and I have no qualms about providing you support for the things in the aforementioned threads that you don't understand. But I WILL NOT hold your hand and tell you every single little thing that you need to know in order for you to fix your own device.
Click to expand...
Click to collapse
hey i totally appreciate your help and your wish of luck lord knows ill take anything right now this stupid "project" has caused me more grief then i could have ever imagined it could. btw, i didnt get "offended" i just thought maybe you were being kinda hard on the OP due to my experience dealing with the exact same issues he posted he was dealing with...
...believe it or not not everyone who doesn't have the same experiences with this stuff as you do aren't necessary idiots or unskilled at using complex systems. thanks again for your continued help and do have a great day!
menriquez said:
wow...sigh...listen the last thing my post tried to do is shift blame...i CLEARLY stated *I* made a BIG MISTAKE didn't I?? i dont need a flame war here sheesh im just trying to fix this ****ty kindle for a buddy....!
Click to expand...
Click to collapse
The last thing I want to do is to get into a flame war with anyone, but when someone comes to the forum and says something like...
it sure would have been nice if some sort of warning would have popped up asking "ARE YOU SURE YOU WANT TO DO THIS and HAVE YOU CHECKED THAT YOU ARE CURRENTLY ROOTED??" because it sure seems that ANYONE making the big mistake i did of trying to install fff without first having root would have this same problem
Click to expand...
Click to collapse
...which, by the way, is entirely based on misinformation...it is very easy for someone to assume the author is, whether directly or indirectly, speaking poorly about a developer's work and assigning blame by presuming that the mistake would not have been made if the tool in question had been made differently. Based on the limited information from your original post, one can only assume that your situation is no different from the hundreds of other users with the same exact problem that also swore the information available did not pertain to their situation and that they were somehow unique, only to find out 50 posts later that it was not the case.
But rather than letting this discussion escalate any further, lets try a different approach. I will give you the benefit of the doubt and entertain the thought that your situation is in fact unique and that there is possibly some other solution for your problem. But, in order for me to do that, I'm going to need some information...very detailed information.
From what I gather so far, based on the information you've provided in your second post is...
1) Your device is in fastboot, confirmed by the fact that the Kindle Fire logo stays brightly lit.
2) You are currently using a LiveUSB with Ubuntu installed and working persistence.
3) When you ran the SoupKit install script, you received errors of some sort, but don't you remember what they were.
4) You are unable to send any fastboot commands at all.
The things I would like to know are...
1) What version of Ubuntu are you running?
2) What brand of pendrive are you using?
3) What is the exact error you received when trying to install the SoupKit?
4) With your device connected, enter the following commands (in Linux) and post the results:
Code:
lsusb -vd 1949: | grep 'bcdDevice'
Code:
cat ~/.android/adb_usb.ini
Code:
sudo cat /etc/udev/rules.d/51-android.rules
soupmagnet said:
...
But rather than letting this discussion escalate any further, lets try a different approach. I will give you the benefit of the doubt and entertain the thought that your situation is in fact unique and that there is possibly some other solution for your problem. But, in order for me to do that, I'm going to need some information...very detailed information.
From what I gather so far, based on the information you've provided in your second post is...
1) Your device is in fastboot, confirmed by the fact that the Kindle Fire logo stays brightly lit.
2) You are currently using a LiveUSB with Ubuntu installed and working persistence.
3) When you ran the SoupKit install script, you received errors of some sort, but don't you remember what they were.
4) You are unable to send any fastboot commands at all.
The things I would like to know are...
1) What version of Ubuntu are you running?
2) What brand of pendrive are you using?
3) What is the exact error you received when trying to install the SoupKit?
4) With your device connected, enter the following commands (in Linux) and post the results:
Code:
lsusb -vd 1949: | grep 'bcdDevice'
Code:
cat ~/.android/adb_usb.ini
Code:
sudo cat /etc/udev/rules.d/51-android.rules
Click to expand...
Click to collapse
firstly i'm very appreciative of your decision to get this back on a positive track and even more thankful that you are still trying to help...
1. ubuntu 13.04 32-bit
2 16gb sandisk with 1024m persistance
3. i reinstalled everything and double checked it...i am no longer getting any errors running soupkit it just says "device offline"
4 lsusb -vd 1949: | grep 'bcdDevice' - nothing just the prompt
5. cat ~/.android/adb_usb.ini - 0x1949
6 . sudo cat /etc/udev/rules.d/51-android.rules -
# 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"
well thats it...i plug my nexus 7 and GS3 and even an ultra cheapo zte warp sequent and it connects right up to all of those...
menriquez said:
firstly i'm very appreciative of your decision to get this back on a positive track and even more thankful that you are still trying to help...
1. ubuntu 13.04 32-bit
2 16gb sandisk with 1024m persistance
3. i reinstalled everything and double checked it...i am no longer getting any errors running soupkit it just says "device offline"
4 lsusb -vd 1949: | grep 'bcdDevice' - nothing just the prompt
5. cat ~/.android/adb_usb.ini - 0x1949
6 . sudo cat /etc/udev/rules.d/51-android.rules -
# 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"
well thats it...i plug my nexus 7 and GS3 and even an ultra cheapo zte warp sequent and it connects right up to all of those...
Click to expand...
Click to collapse
Oh........this again....
For reasons I have yet to figure out, there are rare (and I do mean rare) situations where Linux just will not detect the device whatsoever. When you enter the 'lsusb' command, whether the udev rules are configured properly or not, Linux should still detect your device when plugged into the USB. I can probably count on one hand the number of times I've seen this happen, and I've never been able to recreate the problem on my own.
It could be caused by using the wrong USB port (i.e. USB3.0 instead of USB2.0), it could be caused by the USB pendrive itself, you could have a faulty cable, it may even be the Linux install itself, but those are just wild guesses because I have really don't know. My best estimate is that there is a bug in the stock bootloader that sometimes causes it to malfunction when put into fastboot because (in the few instances I've seen), users that were able to resolve their situation did so by using usbboot to install a custom bootloader. This of course requires opening the device and performing the "shorting trick" to drop the device into usbboot mode.
If I were you, considering you probably haven't attempted to usbboot before, you should try a different USB port, a different USB cable, and a different pendrive to see if you have any luck. Otherwise, you may have no other choice but to usbboot.
The unfortunate thing usbbooting is, it's just one of those things you have to somehow figure out on your own, even with the instructions given in the Firekit/usbboot thread (it's really about technique more than anything else). I've done it several times myself, mostly for testing and various other reasons, but the first time (when I really needed it), took practically forever to get it right.
If you do take the usbboot route, you can launch Firekit from the SoupKit utility script (option #4, I think) and follow the instructions in the Firekit thread. Be very careful opening the device, use a safety pin for creating the short (the reason will become apparent when you get the device opened), and most of all...good luck.
[Edit:] And yes, crow is very tasty
kindlestuck said:
I was using KFU (0.9.9) to install TWRP. When it went to reboot into fastboot mode, the kindle fire boot logo (stock) appeared and the power light turned green. It is now stuck like this. KFU and Windows 7 does not recognize the kindle. I have tried turning it off and back on, but it just goes back to the same screen.
Click to expand...
Click to collapse
Charge kindle, boot into the frozen logo screen with no animation, plug into computer, and reboot computer, i want to share this with everyone because it worked for my kindle
Okay so first off:
- Chinese Variant with OxygenOS installed
- OEM unlocking enabled
- Im on linux
will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up, i tried installing the oneplus adb drivers which ended with no change.
however, doing ``adb reboot fastboot`` and then ``fastboot devices`` it succeeds, now trying ``fastboot flashing unlock`` returns with:
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Click to expand...
Click to collapse
i read in another post that i may need to try ``fastboot oem unlock`` or ``fastboot oem unlock-go`` both of which return:
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Click to expand...
Click to collapse
So im kind of at a loss here of what to do.... any ideas?
UPDATE:
Thanks to these three posts I was able to get it working:
adb/fastboot wont recognize my device.
Okay so first off: - Chinese Variant with OxygenOS installed - OEM unlocking enabled - Im on linux will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up...
forum.xda-developers.com
adb/fastboot wont recognize my device.
Okay so first off: - Chinese Variant with OxygenOS installed - OEM unlocking enabled - Im on linux will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up...
forum.xda-developers.com
adb/fastboot wont recognize my device.
Okay so first off: - Chinese Variant with OxygenOS installed - OEM unlocking enabled - Im on linux will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up...
forum.xda-developers.com
i'm not familiar with OnePlus or Linux...
but what version of adb & fastboot are you employing? And/or I've seen this kind of issue happen (randomly) because of an usb cord issue, of all things -- I wonder if it's a Google Pixel thing, but you never know...
simplepinoi177 said:
i'm not familiar with OnePlus or Linux...
but what version of adb & fastboot are you employing? And/or I've seen this kind of issue happen (randomly) because of an usb cord issue, of all things -- I wonder if it's a Google Pixel thing, but you never know...
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.41
Version 33.0.3p2-android-tools
I've attempted different cables and ports and still have this issue.
Try on Windows
ikram.senguen said:
Try on Windows
Click to expand...
Click to collapse
If I could avoid installing an entire operating system (VM or straight on hardware) that would be preferable.
limepot said:
Android Debug Bridge version 1.0.41
Version 33.0.3p2-android-tools
I've attempted different cables and ports and still have this issue.
Click to expand...
Click to collapse
I'm unsure if OnePlus prefers its own type of platform tools (as I've just recently learned that certain manufactured devices have their own preferred ways of getting adb & fastboot), but if your device can/prefer the same as Google Pixels, you should be if you can -- or try, if you haven't -- using Google's/Android's official platform tools from the developer site; there's a Linux version (which is what triggered my thought on this as that is your setup) and, although it caused great issue for Pixel's (or A/B devices, i imagine), version is updated to r34.0.2 . Maybe the latest updated version might work where yours isn't...
just a thought...
*although much of this is out of my league, again as I am not familiar with OnePlus or Linux...
simplepinoi177 said:
I'm unsure if OnePlus prefers its own type of platform tools (as I've just recently learned that certain manufactured devices have their own preferred ways of getting adb & fastboot), but if your device can/prefer the same as Google Pixels, you should be if you can -- or try, if you haven't -- using Google's/Android's official platform tools from the developer site; there's a Linux version (which is what triggered my thought on this as that is your setup) and, although it caused great issue for Pixel's (or A/B devices, i imagine), version is updated to r34.0.2 . Maybe the latest updated version might work where yours isn't...
just a thought...
*although much of this is out of my league, again as I am not familiar with OnePlus or Linux...
Click to expand...
Click to collapse
thanks! ill give it a try.
limepot said:
thanks! ill give it a try.
Click to expand...
Click to collapse
doesnt seem to make a difference here unfortunately.
limepot said:
Okay so first off:
- Chinese Variant with OxygenOS installed
- OEM unlocking enabled
- Im on linux
will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up, i tried installing the oneplus adb drivers which ended with no change.
however, doing ``adb reboot fastboot`` and then ``fastboot devices`` it succeeds, now trying ``fastboot flashing unlock`` returns with:
i read in another post that i may need to try ``fastboot oem unlock`` or ``fastboot oem unlock-go`` both of which return:
So im kind of at a loss here of what to do.... any ideas?
Click to expand...
Click to collapse
On windows computer, disable driver signature, and you should see a watermark in lower right corner of home screen that states test mode, then install the latest op USB drivers. Make sure to uninstall the old op USB driver first. Then reboot, disable driver signature signing, the reboot computer again. Then start you adb and fastboot commands.
TheGhost1951 said:
limepot said:
Okay so first off:
- Chinese Variant with OxygenOS installed
- OEM unlocking enabled
- Im on linux
....
So im kind of at a loss here of what to do.... any ideas?
Click to expand...
Click to collapse
On windows computer, disable driver signature, and you should see a watermark in lower right corner of home screen that states test mode, then install the latest op USB drivers. Make sure to uninstall the old op USB driver first. Then reboot, disable driver signature signing, the reboot computer again. Then start you adb and fastboot commands.
Click to expand...
Click to collapse
Too bad OP stated he's she's not on windows, but on Linux...
simplepinoi177 said:
Too bad OP stated he's not on windows, but on Linux...
Click to expand...
Click to collapse
tried windows just now (she) same issue, although i did not try their suggestion, i will have to attempt that.
limepot said:
tried windows just now (she) same issue, although i did not try their suggestion, i will have to attempt that.
Click to expand...
Click to collapse
What type of USB port are you using? I was having all kinds of issues with adb and fastboot and it turned out to be because my computer doesn't have any USB 2.0 ports. I found two potential solutions, one of which was to get a hub with USB 2.0 ports, and the other was to change some settings in windows 10. If your computer doesn't have a USB 2.0 port you could try using a hub with USB 2.0 ports, or you could do some searching to see if there's a workaround for your Linux distro like there is for windows.
Masterchief87 said:
What type of USB port are you using? I was having all kinds of issues with adb and fastboot and it turned out to be because my computer doesn't have any USB 2.0 ports. I found two potential solutions, one of which was to get a hub with USB 2.0 ports, and the other was to change some settings in windows 10. If your computer doesn't have a USB 2.0 port you could try using a hub with USB 2.0 ports, or you could do some searching to see if there's a workaround for your Linux distro like there is for windows.
Click to expand...
Click to collapse
i tried on various different ports, i tried on 2.1 and 3 so far no luck.
ive been spending way too much time trying to install windows and ended up being able to on an old laptop so im going to try the windows suggestions (this laptop has only 2.0 ports), that ive seen so far.
Are your fastboot drivers upto date? When you connect your device to pc in fastboot, try searching in the drivers for adb,bootloader,or smth named driver. If not there then your device will probably be in the "others" driver tab with an exclamation mark.
TheGreatBumBum said:
Are your fastboot drivers upto date? When you connect your device to pc in fastboot, try searching in the drivers for adb,bootloader,or smth named driver. If not there then your device will probably be in the "others" driver tab with an exclamation mark.
Click to expand...
Click to collapse
again, linux, i just installed the drivers on my newly installed windows machine, just installed drivers anyways.
limepot said:
again, linux, i just installed the drivers on my newly installed windows machine, just installed drivers anyways.
Click to expand...
Click to collapse
Oh yeah sorry bout that, just want to tell you windows is a bit buggy. I had to install the fastboot drivers every 5-10 minutes.Dunno why,Dunno how.
Back to basics, use only the motherboard/rear ports. Some phones are picky about the cable, you might need to use a factory cable. Does the computer see the phone at all? If not you don't have the right drivers.
Also 'adb reboot fastboot' "working" doesn't mean it worked.
In simple terms, the command will work but it must return a device ID below it and should trigger the phone to trust the PC.
Command order on Windows is:
adb devices
adb reboot fastboot
"whatever the Oneplus Unluck command is" some phones have different ones for different models.
TheGhost1951 said:
On windows computer, disable driver signature, and you should see a watermark in lower right corner of home screen that states test mode, then install the latest op USB drivers. Make sure to uninstall the old op USB driver first. Then reboot, disable driver signature signing, the reboot computer again. Then start you adb and fastboot commands.
Click to expand...
Click to collapse
Okay after taking a lot of time this was indeed the solution, thankyou!
Linux systems oftentimes have issues due to udev rules and missing group memberships of your user. For example on arch you can install android-udev and add the user to the adbusers group. I don't know if there are any packages for debian based distros, but I think they use the plugdev goup for udev rules.
The following gh repo is a good place to start:
GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
Android udev rules list aimed to be the most comprehensive on the net - GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
github.com
der_akinator said:
Linux systems oftentimes have issues due to udev rules and missing group memberships of your user. For example on arch you can install android-udev and add the user to the adbusers group. I don't know if there are any packages for debian based distros, but I think they use the plugdev goup for udev rules.
The following gh repo is a good place to start:
GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
Android udev rules list aimed to be the most comprehensive on the net - GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
github.com
Click to expand...
Click to collapse
This is incredibly helpful thankyou.