Hello,
I am trying to flash an alternative ROM on my Samsung J3 SM-J320F using an ubuntu OS. I got adb and fastboot installed, but fastboot doesn't seem to recognize my device as the command
Code:
fastboot oem unlock
only has me waiting endlessly with
Code:
< waiting for any devices >
As far as I have searched the internet, I understand that I am missing drivers to communicate with my Samsung phone, is that correct? I can only seem to find driver packages for Windows, but none for Linux/Ubuntu. Can anyone please help me?
adb seems to find my device just fine, as
Code:
adb reboot bootloader
worked fine.
Any help appreciated. Thank you.
t
Related
So I am having a lot of problems with trying to root my nexus 7. I'm pretty sure it boils down to a driver issue but I'm not sure. I have tried installing the correct drivers over and over again also uninstalling other hardware manufacturers drivers and I cannot get adb to recognize my device when it is shut off and in the boot loader.
When the tablet is on and I have debugging on, adb shows up and is recognized, however my problem is that whenever I reboot into the boot loader I lose adb recognition. So therefore I can't root or do anything else. Fast boot commands work fine its only the issue with adb.
If anyone has any suggestions as to what I can do I would really appreciate it. I don't know if its just a hardware issue or something I am doing wrong on my end.
This is also not my first time manually unlocking/rooting a device
When you initially connect, the device shows up as a "Nexus 7".
When you reboot into the boot loader, the device name changes, and there is no driver for that device.
As far as I could tell, I would have to do the root process under Linux to avoid this issue.
As for me, I just ignored the issue. By the time you reboot the bootloader, you are already rooted.
The only thing you do after the reboot is rename a file. For now I am missing that step...
Yeah I'm using windows xp. When its in boot loader it does change names. I can unlock the bootloader via fastboot but can't do anything with adb. Lol I don't know what else I can do, I'm at a loss.
kevlars9 said:
Yeah I'm using windows xp. When its in boot loader it does change names. I can unlock the bootloader via fastboot but can't do anything with adb. Lol I don't know what else I can do, I'm at a loss.
Click to expand...
Click to collapse
Like I said - I think you are done...
Install a terminal on the Nexus and see what it says to "su". I use one called "terminal emulator". Works fine.
I think fastboot uses adb.
If you connect your Nexus, and type "adb devices" in a command window what does it say?
I believe it says devices attached or something like that. (Not at my computer) but doesn't give me a serial # like I think it should.
If you do not have USB Debugging checked, "adb devices" will just show the List of devices line.
If I set USB debugging on, "adb devices" also shows the Nexus serial number.
If you don't see that, I would double check the device driver you are using.
Under Device Manager, Android Phone, Android Composite ADB Interface it shows:
Driver: Google Inc.
Date: 5/24/2012
Version: 6.0.0.0
Digital Signer: google inc.
Well if I have USB debugging on and tablet on and do adb devices I get the serial # but once I go into boot loader and do adb devices I don't get the serial #.
For device manager I can choose adb interface or adb original interface. I'll have more info when I get out of work and at my computer. Do you have a link to the drivers you used? Or where to find them. Because I have tried a couple of different drivers posted around to no avail.
BTW thanks for helping me out.
I would not use any posted driver - you don't know where that thing has been.
Download the SDK from Google; the correct driver is in there.
Just point the device manager to it when you install drivers.
There are a lot of good descriptions on installing drivers in the other nexus forums
But - again - I think your device driver is fine. You will not be able to talk to the Nexus from ADB after you boot the bootloader
Bootloader has a different device name which ADB can't use under Windows.
Use Linux if you want to do that.
ok, so pretty much what happens is when my tablet is powered on with usb debugging everything is fine and ADB is recognized. Now my problem seems to be when i reboot into the bootloader it seems as though the drivers dont stick and it asks me to install the drivers again and this is where i have had all of my issues. When i type in adb devices in, it just tells me "list of devices attached" and wont let me do anything else (fastboot works). Like i said i was able to unlock my bootloader but i cant flash recovery or do anything else.
When i go into device manage to select the drivers it gives me the option of choosing between adb interface, adb bootloader interface, adb orignal interface and nexus 7 bootloader interface. I have tried all options and nothing seems to work. I have tried multiple usb cords and ports.
If anyone else has any suggestions it would be much appreciated.
I didn't read through everything but your initial problem is adb doesn't work in the bootloader that's where you use fastboot commands either boot into a custom recovery or just boot up normal and make sure debugging is checked.
Try running fastboot devices and see if it shows up. What you need to do is have bootloader unlocked and dismiss the super user zip floating around here pot that on sd card download cwm recovery image floating around boot into bootloader then
fastboot devices
fastboot flash recovery name_of_file.img
fastboot reboot bootloader
select recovery from the menu
Flash the super user zip
Or download a rom that has root and put that on sd card instead of super user zip and after doing the steps above then selecting super user zip select the rom you downloaded and flash. If you're on Linux run sudo first.
Sent from my Galaxy Nexus using xda premium
Delete
Hey guys,
I've been trying to find a solution for this issue the past month.
So decided to open a new thread.
Does anyone here know a fix for windows/mac not detecting this phone in META/bootloader/fastboot mode?
I have installed drivers for this phone (from the phone itself and from google). Enabled USB debugging, checked the OEM Unlock option in settings and turned on unknown sources. But to no avail, once it's in bootloader, it won't respond to fastboot.
It's just written <waiting for any device>
ADB command, however, works fine.
I used adb reboot bootloader and other commands and it worked fine!
This is driving me crazy! Not being able to put TWRP and root this phone.
I looked up systemless root and still you need fastboot for that.
PLEASE PLEASE PLEASE HELP!
Hello!
I have a very big problem. My LG Leon H340N is "bricked" totally, there is only fastboot mode in phone, nothing else.
The problem is that fastboot is not working, when i try to execute some commands it all the time gives me answer: FAILED(Unknow Command) and i don't know how to fix this, i don't have access to download mode, i don't have access to hard reset menu, i don't have access to recovery mode, only fastboot
Could somebody help me ?
How did you get into fastboot mode?
I connect device and laptop via USB and device is starting into fastboot mode automatically.
When device is connected i open cmd (run as administrator) and C:\ cd adb = C:\adb> fastboot devices - and it shows me my device connected as fastboot device then I try to execute some commands but it always gives FAILED(UnknowCommand). The fastboot drivers are installed - original google drivers from android sdk. I'm using Windows 7 Home Premium, i try execute some commands on other laptop with windows 7 starter but the same thing - FAILED(Unknow Command).
Thank you for reply, Regards
Flash the version MS34510d_00
I don't have MetroPCS version it's h340n. And i can't flash anything, because fastboot is not working
Install android 5
Dude, i know, i want to install android 5 but you don't see that fastboot in my phone IS NOT WORKING ? every time, when i try to exec some commands it gives me: FAILED(UnknowCommand)
for mode download
Hey.
I'm trying to root my phone ,and installed adb on my mac- but the device is not showing up after list of devices sucesfully installed...
any suggestions ? i made sure to install the LG drivers , Java (incase) , and its still not showing up in fastboot mode when i type in ./adb devices or fastboot devices....any help would be appreciated....
Hi guys!
I am trying to flash the factory OS downloaded from the dev website, however I have a problem.
When the phone is booted in Android the ADB Interface is recognized without a problem.
However when I reboot to recovery to flash the FW Windows 10 (latest CU version) does not recognize ADB Interface and says This Device Cannot Start Error 10
I have tried these drivers:
adb-setup-1.4.3
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33.0
latest_usb_driver_windows /google driver/
OnePlus+5+USB+drivers+-+Technobuzznet
Nothing has helped, the issue remained the same.
Any suggestion what can I do to get OP5 ADB working when the phone is in Recovery ?
Thank you!
ssj3hulk said:
Hi guys!
I am trying to flash the factory OS downloaded from the dev website, however I have a problem.
When the phone is booted in Android the ADB Interface is recognized without a problem.
However when I reboot to recovery to flash the FW Windows 10 (latest CU version) does not recognize ADB Interface and says This Device Cannot Start Error 10
I have tried these drivers:
adb-setup-1.4.3
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33.0
latest_usb_driver_windows /google driver/
OnePlus+5+USB+drivers+-+Technobuzznet
Nothing has helped, the issue remained the same.
Any suggestion what can I do to get OP5 ADB working when the phone is in Recovery ?
Thank you!
Click to expand...
Click to collapse
same problem.
fix for it -> use linux
setup vmware, install ubuntu
when everything is set up connect device in fastboot mode
open command line:
sudo apt-get update
sudo apt-get install adb
sudo apt-get install fastboot
now you can make adb and fastboot commands, don't forget the sudo before the command e.g.: sudo fastboot reboot
I made the mistake of wiping my entire device when going to do a clean flash so the only thing I could access was recovery. I had no issues with using adb to sort out my mess in Win 10. The last phone I had was an old HTC that I was using between getting my OP3 stolen and the OP5 release and for that I had HTC drivers installed.
Not sure if that is a solution that will help you, but just putting it out there.
ssj3hulk said:
Hi guys!
I am trying to flash the factory OS downloaded from the dev website, however I have a problem.
When the phone is booted in Android the ADB Interface is recognized without a problem.
However when I reboot to recovery to flash the FW Windows 10 (latest CU version) does not recognize ADB Interface and says This Device Cannot Start Error 10
I have tried these drivers:
adb-setup-1.4.3
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33.0
latest_usb_driver_windows /google driver/
OnePlus+5+USB+drivers+-+Technobuzznet
Nothing has helped, the issue remained the same.
Any suggestion what can I do to get OP5 ADB working when the phone is in Recovery ?
Thank you!
Click to expand...
Click to collapse
Did you enable usb debugging in developer options?