Related
Help mee.
I have bought a s3 that is locked to Orange, need to unlock, but odin does not see the phone in recovery/dl mode.
Odin see the phone in normal mode , but each time i put into start/+vol/home odin see nothing.
I have kies updated.
Thanks
crazydiamond1970 said:
Help mee.
I have bought a s3 that is locked to Orange, need to unlock, but odin does not see the phone in recovery/dl mode.
Odin see the phone in normal mode , but each time i put into start/+vol/home odin see nothing.
I have kies updated.
Thanks
Click to expand...
Click to collapse
I had a similar thing when i was plugged into a usb hub
Was ok when i plugged directly into the pc
Install Samsung Kies to be able your PC to detect your phone via Odin
also check the debugging mode in the developer options
bordikun said:
Install Samsung Kies to be able your PC to detect your phone via Odin
also check the debugging mode in the developer options
Click to expand...
Click to collapse
I have Kies, also tried debugging, i need root to unlock phone
Try to use the latest Odin
Odin v3.04
bordikun said:
Try to use the latest Odin
Odin v3.04
Click to expand...
Click to collapse
I have uninstalled the older Kies, re installed the latest.
I have installed the lastest odin.
Have tried to link up with and without debugging, odin still does not see phone when in recovery mode.
Only time odin see the phone when phone is in normal mode.
Starting to get annoyed now lol, i cant cut my sim to fit phone, untill this is done
I cant see my s2 on odin either, what am i doing wrong ????
1. Reboot PC
2. Ensure KIES is not running and kill any KIES processes in PC task manager.
3. Download mode
4. Connect USB directly to PC port (no hub)
5. Wait for any drivers to instal or load on PC
6. Start Odin in administrator mode
If still no good;
a) Different USB cable
b) Different PC USB port and wait for drivers
Sent from my GT-I9300 using xda premium
Thanks . Seems that I had been pressing volume up not down.
I have another question . I used chainfire Rom to debrand the phone but keis does not recognize . How can I solve this . Could it be because the phone is rooted ?
i am having this problem at the mo, I have tried all of the above, apart from a different pc.
oden worked fine with my galaxy s2
is there any more updates on how to sort this out please?
thanks
ian
I know this is a 7 day old thread, but I feel for you having been in the same situation. Firstly, have you installed the Android SDK? If not then I advise you to do so. Do a search on how to install the SDK. There maybe smaller downloads available with a package of the binaries you need to do some testing i.e. adb. The instructions will elaborate about how to set up your Environment settings in Windows. Essentially ADB needs to be called from within any part of your Windows system....or else you will have to cd to its location each and every time you want to do something like this. So once you have done that, open command prompt and type adb and see what comes up? If it says bad command or file name it means your environment settings for the ASK are incorrect, if it displays the adb help text in command prompt you are ready to proceed.
When you plug your device in (not in DL or recovery modes) is it detected by the PC? If so then your drivers are probably fine. If not then it maybe 1 of 2 things? 1 the device is detected but the MTP drivers have not been loaded or 2. No detection what so ever and all drivers need to be installed.
To determine how to proceed you will need to do a bit of investigating.
Note the USB drivers are included as part of the Android SDK.
Check in Device manager inside of Windows to see if anything is detected when you plug it in. If so but it has a yellow exclamation ! then it would indicate you need to update your drivers (but not always?). From here you can test to see if the phone is detected and you only need MTP drivers.
If not then I would suggest uninstalling Keis all together and downloading and installing the Samsung USB drivers separately. Install the drivers. Plug in the phone. If it is not detected straight away, then reboot the PC then plug the phone into a different USB port. From here you can determine how to proceed by using adb.
plug your phone in via USB and open command prompt and type this: adb devices
You should see 1 of 2 things.
1) The words "list of devices attached" followed by a 16 digit long ID number a gap and the word "device"
2) just the words "list of devices attached" and then blank and nothing else?
If a device ID is returned then you can proceed with the following. Otherwise you need to do some additional trouble shooting
Proceed here:
Once it is detected by Windows and shows up in Explorer then unplug the phone and go into settings and developer options and check enable USB debugging. Once you have done this it should allow your device to be seen in DL and recovery modes.
Troubleshoot: If not detected try the following:
1) Reboot the PC and plug into a new USB port that you have not previously plugged into.
2) Try disabling USB debugging plugging the device in and then unplugging it and reenabling USB debugging
3) From the status bar try switching modes between MTP and PTP modes. Wait a good minute or so between to allow Windows to detect the driver change. Tip a good indication is your notification tray Icon with green USB disk with a magnifying glass swirling around....Note if you cannot see this at all you probably should drag it into the notification panel so that you CAN!
4) Open up device manager again and ensure no yellow exclamation marks !
Once all this is right and you can get List of devices attached followed by an ID number then you can for sure be able to detect your device from Odin. Make sure you are running Odin 3.04, run it as admin (not necessary but have heard that it helps?)
Good luck
James
I have an S4 Active that NO MATTER WHAT I DO, Odin will NOT see phone in Download mode, it will with the phone on, and my PC will see the phone, but not Odin. I am stumped. I have tried 3 PC's, I have ALL the drivers and then some. I am Stumped.
rekamyenom said:
I have an S4 Active that NO MATTER WHAT I DO, Odin will NOT see phone in Download mode, it will with the phone on, and my PC will see the phone, but not Odin. I am stumped. I have tried 3 PC's, I have ALL the drivers and then some. I am Stumped.
Click to expand...
Click to collapse
have you tried factory resetting the phone?
afasayan said:
have you tried factory resetting the phone?
Click to expand...
Click to collapse
Several times
rekamyenom said:
Several times
Click to expand...
Click to collapse
You can try with minimal/no drivers i.e. uninstall kies if you have it and delete the drivers you might have installed on your own-it sounds counter productive but it has worked for me a few times.
You can also try to either install kies or the drivers separately.
Try the forum for your own phone, the people there might know better about this problem.
Also what OS are you on?
afasayan said:
You can try with minimal/no drivers i.e. uninstall kies if you have it and delete the drivers you might have installed on your own-it sounds counter productive but it has worked for me a few times.
You can also try to either install kies or the drivers separately.
Try the forum for your own phone, the people there might know better about this problem.
Also what OS are you on?
Click to expand...
Click to collapse
I will give all that a try. I'm on 4.4.2 build NH3. That's why I need Odin, to get back to build NE3
rekamyenom said:
I will give all that a try. I'm on 4.4.2 build NH3. That's why I need Odin, to get back to build NE3
Click to expand...
Click to collapse
By OS I meant the computer's OS.
afasayan said:
By OS I meant the computer's OS.
Click to expand...
Click to collapse
I have tried several computers using Windows 7 and Windows XP both 32 and 64
My phone isn't being detected by adb. Almost as if USB Debugging isn't even enabled (which it is). ADB is just blank when I run adb devices.
I've installed the LG VZW G3 drivers. Any suggestions?
Make sure you change the USB mode to internet and then Ethernet. Took me a while to figure that out.
Make sure you have developer options visible
Enable USB debugging
Connect your phone to your computer
Pull down and change the USB connection from installer/MTP to internet > ethernet
Open Command Prompt window where ADB is installed, and type in "adb devices"
Allow when you see the RSA prompt
Run the batch file for ioroot, type "adb reboot recovery", install from adb, run sideload command, and then reboot
Also, make sure you're running the latest version of the SDK. Mine wouldn't work until I updated. HTH!
mjforte said:
Make sure you change the USB mode to internet and then Ethernet. Took me a while to figure that out.
Click to expand...
Click to collapse
+1
Sent from my VS985 4G using Tapatalk
mjforte said:
Make sure you change the USB mode to internet and then Ethernet. Took me a while to figure that out.
Click to expand...
Click to collapse
+1 - This was my problem too...many thanks!
usb drivers
blmartin said:
+1 - This was my problem too...many thanks!
Click to expand...
Click to collapse
Use the LG USB drivers for Verizon Wireless!
Change the usb connection mode to Internet/Ethernet
My adb was the problem on mine. I had to reinstall java jdk and the sdk and worked perfectly the first time I tried after that
asialove2013 said:
Use the LG USB drivers for Verizon Wireless!
Change the usb connection mode to Internet/Ethernet
Click to expand...
Click to collapse
Either I'm completly blind or ... my G3 doesn't have that option. I only got "Charge Phone", "Media Device (MTP)", and "Send images (PTP)" to configure the USB PC CONNECTION. I also have the option to switch on USB tethering, but that doesn't change anything for the better, either.
Where's that Internet/Ethernet connection mode hidden?
The internet option might not appear until the usb is connected to the pc. Recheck available options while connected.
-Set phone for PTP connection
-Plug phone into PC via USB. You should see a driver loading/loaded message on your PC
-On the phone, change USB connection to Internet, then select Ethernet on the submenu that will appear
(PTP seems to "wake up" the ADB driver on the PC side for me. This was mandatory on a couple of prior phones/tablets, so it's what I did with the G3.)
Or switch to Linux and never hear about drivers ever again!
Verizon on Windows 8.1
So, the problem I had on windows 8.1 was that when you connect the device and it asks you what action to take automatically, you need to click that and install the Verizon stuff. I had my phone in USB debugging and Ethernet mode while doing this install. After it installed everything, the window on my phone for debugging permission showed up, and I allowed it. The phone now shows up in adb. I don't know if this was obvious but I thought Id mention it anyway
After the last G3 update from Verizon, the Ethernet option is gone. I can't get it to talk with ADB any longer. I see the developer mode come up on the phone, but it never asks for security key or appears in the ADB list. Anybody have any good ideas? This is on a Mac and I've never had a problem before doing this.
EDIT: After juggling back and forth from PTP to MTP to PTP, restarting ADB, I got it to connect. No clue what the key was, but working again for the moment. The Ethernet option is still gone from the phone though so that simple fix is no longer an issue.
Averix said:
After the last G3 update from Verizon, the Ethernet option is gone. I can't get it to talk with ADB any longer. I see the developer mode come up on the phone, but it never asks for security key or appears in the ADB list. Anybody have any good ideas? This is on a Mac and I've never had a problem before doing this.
EDIT: After juggling back and forth from PTP to MTP to PTP, restarting ADB, I got it to connect. No clue what the key was, but working again for the moment. The Ethernet option is still gone from the phone though so that simple fix is no longer an issue.
Click to expand...
Click to collapse
I installed the skydragon rom, which is based on stock so probably the same. I found that PTP worked but MTP did not. This is in Ubuntu Linux.
I'm trying to root my Verizon LG G3 on 5.0.1 VS98524B, but now ADB wont recognize my device. Yesterday I was trying to root it using a one click root tool but it would fail (it would say successful, but would not achieve root). today I decided to use the LG flash tool to restore my phone and try again. then I saw that the tool (which claims to support all g3 models on all firmwares above kitkat) did not support VS98524B, but there is another that does, but surprise surprise, adb no longer finds my phone.
update... I have found that ADB on Ubuntu does find and recognize my device, and the security prompt comes up on my device. (does not come up for any window computer)
I have tried; restoring my phone again, installing and reinstalling the drivers, use different computers (2 win 7, one win 10), use different cables, on different ports, change between ptp and mtp, toggling and untoggling usb debugging, restarting my computer, etc.
adb doesn't find the phone while running a root tool, or just doing the adb devices command in cmd....
looked at many threads, and not many (if any) seem to have this problem, and all who did were able to solve using one of the steps I mentioned above....\\
any help?
update... Using Ubuntu adb does recognize my device, and prompts the security pop-up on my phone. (the pop-up does NOT come up for any windows pc)... but I cant figure out how to root the device using Ubuntu)
RESOLVED-- I uninstalled (again) the drivers, and grabbed new updated ones from the LG webpage (which ARE different than the suggested drivers on the root tool page.) then installed the android studio on my computer, and redownloaded adb... not sure which of these steps made the difference, but it worked! now rooted.
You should get a RSA fingerprint window that you have to accept on the G3 when connecting. If you're not receiving it, look in
(C:\Users\*username*\.android)
(C:\android)
(C:\Windows\System32\config\systemprofile\.android)
Delete adbkey and adbkey.pub in those 3 locations. Tap the "Revoke USB Debugging Authorizations" button below USB debugging in developer options. Set connection to internet>ethernet. Restart the adb server in command prompt (adb start-server) and plug your phone in while looking for the RSA fingerprint window to popup on your phone.
hawkswind1 said:
You should get a RSA fingerprint window that you have to accept on the G3 when connecting. If you're not receiving it, look in
(C:\Users\*username*\.android)
(C:\android)
(C:\Windows\System32\config\systemprofile\.android)
Delete adbkey and adbkey.pub in those 3 locations. Tap the "Revoke USB Debugging Authorizations" button below USB debugging in developer options. Set connection to internet>ethernet. Restart the adb server in command prompt (adb start-server) and plug your phone in while looking for the RSA fingerprint window to popup on your phone.
Click to expand...
Click to collapse
I don't think there's been an Internet/Ethernet option since before 12B, or at least before 23C.
@Coltonbyu, choose MTP for your connection type.
hawkswind1 said:
You should get a RSA fingerprint window that you have to accept on the G3 when connecting. If you're not receiving it, look in
(C:\Users\*username*\.android)
(C:\android)
(C:\Windows\System32\config\systemprofile\.android)
Delete adbkey and adbkey.pub in those 3 locations. Tap the "Revoke USB Debugging Authorizations" button below USB debugging in developer options. Set connection to internet>ethernet. Restart the adb server in command prompt (adb start-server) and plug your phone in while looking for the RSA fingerprint window to popup on your phone.
Click to expand...
Click to collapse
I did as you said, but the prompt never appears on my phone, which is odd, as it appeared before the factory reset, but will no longer appear for any windows pc. (it does appear on Ubuntu though)
Hi, I have tried unlocking BL via virtual machine with windows, redirecting usb port to it from my Fedora. Normal mode of phone worked fine. The same with fastboot. But wgen I tried do it when phone was in download mode, my Linux didn't saw it. No new message in dmesg and no new devices in lsusb.
Have anyone tried and saw his phone in download mode under Linux?
ajesik said:
Hi, I have tried unlocking BL via virtual machine with windows, redirecting usb port to it from my Fedora. Normal mode of phone worked fine. The same with fastboot. But wgen I tried do it when phone was in download mode, my Linux didn't saw it. No new message in dmesg and no new devices in lsusb.
Have anyone tried and saw his phone in download mode under Linux?
Click to expand...
Click to collapse
I have it working in VirtualBox under OSX without issue. I have all of the phone's various USB devices, adb, fastboot, and edl, configured to pass through to the Windows 10 VW automatically. I have flashed the phone in edl mode several times this way.
I upgraded couple of days ago to new PC - Ryzen 5 2600/rog strix b450-f gaming with clean windows 10/64 and now i have problems with adb bootloaader driver and cmd commands. Before i was on intel xeon/gigabyte motherboard socket 775 windows 7/64
I use tool all in one, install usb drivers. When phone is turn on, with usb debuging, i can enter phone storage, device manager see phone as poco,everything is ok. When i start tool all in one i can see device id,i can go into fastboot mode(phone restart and go into fastboot). When phone goes into fastboot,device manager see it as Kedacom usb device/android bootloader interface, or sometimes as android phone/android composite usb device. I have adb/fastboot files all i need on pc. When i enter some command trough cmd,for example fastboot devices,or fastboot reboot bootloader, on phone screen goes to dark and in left top corner with small font is written phone will turn off. On cmd i see afther command i set and pres enter only ??????? questionmarks. So i must again manually enter fastboot mode.
I cant get fastboot/adb to work. I try to install other adb/fastboot drivers(xiaomi and google original from tool all in one),try to connect phone cable to other usb port(2.0/3.0/3.1) at the back of pc chase,also 2.0 in front case. I try other usb cable also. Try to manually update google drivers from this forum,then i cant bcouse some ini file is missing or if i set have disc and do manualy with some other driver it cant see phone in adb-fastboot mode. I try all that fall on my mind with no luck.
At the and i goes to my friend and try to install tool all in one,install google usb drivers from that tool,install adb/fastboot files. Try to enter fastboot and do same commands as before with cmd,and everything is working fine as it was with my old pc setup. Device manager see it as Kedacom usb device/android bootloader. He also have amd cpu/chipset - but it is not ryzen with fresh w10/64
Is there any fix for my case? Does anybody have same problem?