Related
I installed the drivers from Samsung and the full SDK. ADB accessed via the device (adb devices, etc.) successfully.
But when I go to the device recovery mode command adb devices returns no device.
I noticed that when in recovery mode the device does not appear in the list of devices from Windows.
Appears usb to install some components but none of them is the adb interface. I tried anyway to force them to install the
driver Google: Android Bootloader Interface, continued without listing. What caught my attention is that the device does not
appear S6102 as when he is out of recovery mode. I think then the GT-S6102 does not allow access via ADB.
Device: Samsung Galaxy Y Duos GT-S6102
O.S.: Windows 7 Home Basic 64bits
ROM: ICS Dream Fusion v1.3
Kernel: Compact V1.2.6
Its kernel problem... I will look into it when I get time.. currently having exams... sorry for trouble it caused you. ..
But please post these threads in appropriate section... Q & A section that is..
Thanks for informing... will report this thread to move..
**Nothing is True... Everything is Permitted**
Muffins.. muffins everywhere!
Thanks.
I'm sorry, I did not know could post in Q & A because there had SGY, sorry. I will not repeat it.
I created two posts in the wrong section. Please ask him to change too.
(Title - Can I use another phone dialer on my GT-S6102?)
Very Thanks.
@Nitu and Felix. I don't think its kernel issue. Even in stock kernel you can't use adb when in recovery mode or odin mode.
What is the point in trying to use adb in revery mode?
Sent from my GT-B5512 using Tapatalk 2
---------- Post added at 11:50 PM ---------- Previous post was at 11:28 PM ----------
Johnfelix said:
I installed the drivers from Samsung and the full SDK. ADB accessed via the device (adb devices, etc.) successfully.
Appears usb to install some components but none of them is the adb interface. I tried anyway to force them to install the
driver Google: Android Bootloader Interface, continued without listing. What caught my attention is that the device does not
appear S6102 as when he is out of recovery mode. I think then the GT-S6102 does not allow access via ADB.
Click to expand...
Click to collapse
Your statement is not clear to me. I assume if you boot your phone normally (not recovery or download mode) you are able to use adb on your phone. If you can use phone as mass storage device and run adb commands when in normal mode then all drivers are probably installed. You can confirm this by connect phone to pc amd looking in device manager for errors.
In my experience the name that appears when you install drivers or when you look at list of devices connected to your pc is not always same as the model name of your phone as the phone comes with multiple harware components which require their own drivers be installed on pc and it would be unfair to sometimes lump these hardware components under one name
Sent from my GT-B5512 using Tapatalk 2
I can use ADB when I connect the phone in normal mode. But I can not do kernel update and some that need to access the system offline.
Then it tried to access recovery mode and this mode does not work the ADB.
I work with computers in technical maintenance, and do updates and configurations in android devices (smartphones and tablets).
In cases like time to recover or fix Foo may be necessary to access recovery mode.
I do not know the Samsung Galaxy Y GT-S6102 but I saw the video on youtube of a device from HTC that runs the ADB in recovery mode.
I get you. Maybe its a problem withe samsung galaxy y series. Even in ubuntu where drivers are not a problem you can't use adb in recovery mode.
So maybe we both need to continue googling
Sent from my GT-B5512 using Tapatalk 2
For using adb u need a perm. Cwm in kernel wid adb enabled. Usually it doesnt work properly on stock recovery.
Sent from my GT-S5360 using XDA
May I just ask what could my problem be?
I am encountering some issues with ADB.
When the phone is turned on, it says it is offline.
So when I try to connect it through ADB via Recovery, its offline status is gone and ADB cannot detect my device.
I confirmedt his using code: adb devices
Does anyone know how can I connect it to ADB?
What I already did:
- Installed Samsung Drivers Completely
- Enabled USB Debugging on GALAXY Note 3
delete the drivers , install kies for note 3 connect the phone , when it is detected in kies and go to tools and look for reinstall drivers
disconnect and reinstall the drivers from kies then you will be good to go with adb ..
ALTHOUGH i dont understand adb its like they torture us adb works when it wants to specially in windows.
fahadali2315 said:
delete the drivers , install kies for note 3 connect the phone , when it is detected in kies and go to tools and look for reinstall drivers
disconnect and reinstall the drivers from kies then you will be good to go with adb ..
ALTHOUGH i dont understand adb its like they torture us adb works when it wants to specially in windows.
Click to expand...
Click to collapse
hey mate, still no response from adb during recovery mode . .
trevourlance27 said:
hey mate, still no response from adb during recovery mode . .
Click to expand...
Click to collapse
Did you try twrp ,with adb shell ? Might be issue with your recovery.
Sent from my SM-N9005 using Tapatalk
fahadali2315 said:
Did you try twrp ,with adb shell ? Might be issue with your recovery.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
well for now i don't want to have root access nor trigger knox . .
i've tested other note 3's and when i try to connect them to adb with pure stock, they respond
any possible ways without changing recovery to twrp?
(ill plan rooting next time because the device is still new) but yeah thanks for the ideas
I want to unlock my moto g 1sr gen's bootloader......
I have android SDK latest version....
All latest drivers installed... From official website and as the official guide suggested...
I have USB Debugging on....
When I plug in my device my PC does read my phone......in all modes of debugging....
But when I open command prompt and type adb devices it gives the output as
List of devices:
And its empty....
Also when I put my device into fastboot and type the get unlock data command
It says
<waiting for device>
And it never ends ....
I have to manually close it...
Is there a toolkit which would unlock my bootloader or unlock bootloader and also root it?
The for your help....I m using windows vista with latest updates installed as I updated it yesterday.....
I have attached a screenshot
Sent from my XT1033 using XDA Free mobile app
Try going to device manager in Windows, then make sure the driver for your phone that Windows is using is the Motorola driver not the windows driver. If it's still using the windows driver like I suspect, unintelligible it and rerun the Motorola driver program in repair mode.
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution?
BTW, I am using a Windows 10 computer.
Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly.
Thank you in advance for any assistance.
phaino00 said:
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution?
BTW, I am using a Windows 10 computer.
Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly.
Thank you in advance for any assistance.
Click to expand...
Click to collapse
Delete the drivers you have installed, boot into fastboot and have Windows automatically detect and install for you. Have you tried that? What source did you get your fastboot drivers from?
phaino00 said:
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution?
BTW, I am using a Windows 10 computer.
Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly.
Thank you in advance for any assistance.
Click to expand...
Click to collapse
Msmdownload drivers are not the same at all, they are Qualcom drivers. Uninstall your fastboot drivers and let windows install them
phaino00 said:
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so, any solution?
BTW, I am using a Windows 10 computer.
Also, I was able to install the International Version on my TMO variant One Plus 6T via the MSM tool method, so the drivers appear to be installed correctly.
Thank you in advance for any assistance.
Click to expand...
Click to collapse
Oh man, I had issues getting my 6t to connect to my PC when I first got my 6t. The answer for me was to plug my phone into a USB 2.0 port on the BACK of my PC instead of the front USB ports my PC has. Try using the back USB ports and let me know if that works for you!
Thank you all. I will try these suggestions later today and report back.
I tried the suggestions and still no success in fastboot connecting with my device. Thanks again for the suggestions.
After trying to multiple times reinstall the drivers, manually selecting "Android Bootloader Interface" did the trick for me on win10:
wtfandroid.com/fix-fastboot-device-not-recognised-problem/
Issue resolved. Selected Android Bootloader Interface in Device Manager and fastboot recognized my device. Unlocked Bootloader, installed TWRP and Magisk. Root achieved.
Thank you all!!!
jullev said:
After trying to multiple times reinstall the drivers, manually selecting "Android Bootloader Interface" did the trick for me on win10:
wtfandroid.com/fix-fastboot-device-not-recognised-problem/
Click to expand...
Click to collapse
Thank you! I can't believe I didn't think to check that.
it is solved for me oneplus 6t not recognized in fastboot
{ solved for me } hello brother, i got this problem also my head was about to explosing, install/uninstall drivers and adb drivers also, without any success, when the device is on normal mod the adb terminal can recognize it and in fastboot mod not recognize my devie (the list empty).
i was trying to install TWRP, so i have reboot my device to fastboot mod, and i didn't think about List of devices (because it not show my device) i wrote the comand to install TWRP directly so it success to install 100%,
so no need to write : adb devices when your device is in fastboot mod, it will not show you in the list, but you can apply what you want normally
good luck
hichemkanon said:
{ solved for me } hello brother, i got this problem also my head was about to explosing, install/uninstall drivers and adb drivers also, without any success, when the device is on normal mod the adb terminal can recognize it and in fastboot mod not recognize my devie (the list empty).
i was trying to install TWRP, so i have reboot my device to fastboot mod, and i didn't think about List of devices (because it not show my device) i wrote the comand to install TWRP directly so it success to install 100%,
so no need to write : adb devices when your device is in fastboot mod, it will not show you in the list, but you can apply what you want normally
good luck
Click to expand...
Click to collapse
Hello. I am having the same issues. But can you provide more steps on how to install TWRP. Can you provide the command/steps used to directly install TWRP?
Thank you.
phaino00 said:
Issue resolved. Selected Android Bootloader Interface in Device Manager and fastboot recognized my device. Unlocked Bootloader, installed TWRP and Magisk. Root achieved.
Thank you all!!!
Click to expand...
Click to collapse
Did this and still not able to recognize it in fastboot mode
sonice43 said:
Hello. I am having the same issues. But can you provide more steps on how to install TWRP. Can you provide the command/steps used to directly install TWRP?
Click to expand...
Click to collapse
Rijul30 said:
Did this and still not able to recognize it in fastboot mode
Click to expand...
Click to collapse
This is why I use Linux in my LOS Install Guide. You can boot Linux from a USB without installing it. Fastboot and ADB just work, without any drivers. Install TWRP, reboot and your PC will be back to windows. My guide covers installing TWRP.
Really need help. I'm going in circles and wasting a lot of time:
I'm attempting to root a OP6T A6013. Its already been unlocked.
My device is recognized when powered up as an ADB device.
But when i boot into the bootloader it isnt recognized as a fastboot device, and my laptop (Win 8.1) shows ""device malfunctioned. USB not recognized". I've also been trying to install the OP driver but I'm not sure its working correctly. But would that cause the problem with recognizing fastboot?
I've root my OP7Pro (twice, actually) and though I had some driver issues then eventually figured it out. But I never had issues with fastboot.
Any tips or direction?
Hey all , replying to share my solution to this exact problem I was having..
My OP6T (T-Mobile converted to international) was not showing in fastboot devices but showed in ADB.. after hours of searching google and XDA , I ended up just plugging my 6T into another computer and it worked! , instantly recognized my device without hassle.
So just a fyi, it could be something simple as switching USB ports or even another computer.
hopefully this helps if someone get's stuck at this point.
I had this issue with a OP8Pro... I went to Windows Update and selected View Optional Updates and found Android Bootloader Device on the list. I selected this to download, and then fastboot worked perfectly.
OhioYJ said:
This is why I use Linux in my LOS Install Guide. You can boot Linux from a USB without installing it. Fastboot and ADB just work, without any drivers. Install TWRP, reboot and your PC will be back to windows. My guide covers installing TWRP.
Click to expand...
Click to collapse
sudo fastboot oem unlock worked in linux in first shot while windows was unable to recognize the device.
Thanks a ton.
EDIT : Just to add .. this linux was in VM
OhioYJ said:
This is why I use Linux in my LOS Install Guide. You can boot Linux from a USB without installing it. Fastboot and ADB just work, without any drivers. Install TWRP, reboot and your PC will be back to windows. My guide covers installing TWRP.
Click to expand...
Click to collapse
I agree. Linux is far better when flashing android phones
anonymoustl said:
I had this issue with a OP8Pro... I went to Windows Update and selected View Optional Updates and found Android Bootloader Device on the list. I selected this to download, and then fastboot worked perfectly.
Click to expand...
Click to collapse
This worked for my OnePlus 9 Pro running Windows 10. Happy modding!
So im trying to unlock my bootloader of my redmi k20, i have installed adb drivers properly, and adb commands work fine when the phone is on, but as soon as i enter fastboot mode my device does not even appear as an other device or anything in device manager .
Since I've tried fastboot mode on an other phone(redmi note 10 pro) and it was detected as a fastboot device on the same PC, I DONT THINK ITS A PC DRIVER PROBLEM rather the phone problem and im in a disarray rn while being stuck in miui (with alot of bugs) and no future support whatsoever.
sujan smash said:
So im trying to unlock my bootloader of my redmi k20, i have installed adb drivers properly, and adb commands work fine when the phone is on, but as soon as i enter fastboot mode my device does not even appear as an other device or anything in device manager .
Since I've tried fastboot mode on an other phone(redmi note 10 pro) and it was detected as a fastboot device on the same PC, I DONT THINK ITS A PC DRIVER PROBLEM rather the phone problem and im in a disarray rn while being stuck in miui (with alot of bugs) and no future support whatsoever.
Click to expand...
Click to collapse
adb devices
adb reboot bootloader
fastboot devices
Adb and fastboot devices must show the same ID of your phone.
If one works and the other does not, I bet problem must be in the drivers (I use the good, old, Minimal Adb and Fastboot package)
If even adb devices fail, problem may be in the USB cable
Btw, make sure that USB debugging in Developer options is enabled.
For unlocking BL, OEM unlocking must be also enabled
zgfg said:
adb devices
adb reboot bootloader
fastboot devices
Adb and fastboot devices must show the same ID of your phone.
If one works and the other does not, I bet problem must be in the drivers (I use the good, old, Minimal Adb and Fastboot package)
If even adb devices fail, problem may be in the USB cable
Btw, make sure that USB debugging in Developer options is enabled.
For unlocking BL, OEM unlocking must be also enabled
Click to expand...
Click to collapse
As u can see usb debugging and oem unlocking are both enabled
And the device is detected as an adb device but not in fastboot mode,
Nor as an Android or unknown device in Device manager either
sujan smash said:
As u can see usb debugging and oem unlocking are both enabled
And the device is detected as an adb device but not in fastboot mode,
Nor as an Android or unknown device in Device manager either
Click to expand...
Click to collapse
Everything looks correctly set but you could still try another PC and USB cable
zgfg said:
Everything looks correctly set but you could still try another PC and USB cable
Click to expand...
Click to collapse
Well i did that too, tried it on my laptop too no luck there also,
As ive mentioned in the first thread ,
It is detecting redmi note 10 in fastboot mode on the same pc with same cable and everything, but not redmi k20, so its not abt PC drivers its something to do with my phone
Then really a problem with the phone - but I guess, your guarantee period has expired long ago
zgfg said:
Then really a problem with the phone - but I guess, your guarantee period has expired long ago
Click to expand...
Click to collapse
Yep it sucks, Thanks Anyways