Hello All,
Just picked up the Le Max 2 last week (Le X820), what a fantastic phone!
My question though. I have enabled USB debugging on, but cannot get ADB to connect in fastboot? For some reason when I plug it into the PC it only brings up PTP, MTP or charge only. No matter which I pick the phone never asks for authorisation as my other phones do? This I’m guessing is why ADB can’t see it?
I’ve tried toggling it on and off and revoking permissions etc., but no joy.
bump
Same problem with my Le X821 (Indian)
manic_minor said:
Hello All,
Just picked up the Le Max 2 last week (Le X820), what a fantastic phone!
My question though. I have enabled USB debugging on, but cannot get ADB to connect in fastboot? For some reason when I plug it into the PC it only brings up PTP, MTP or charge only. No matter which I pick the phone never asks for authorisation as my other phones do? This I’m guessing is why ADB can’t see it?
I’ve tried toggling it on and off and revoking permissions etc., but no joy.
Click to expand...
Click to collapse
Even I face the same problem, I have enabled usb-debugging and toggled between Charge only and MTP, still ADB does not list my device
Any ideas folks? SDK dev' kit installed. ADB and fast-boot installed. USB debugging on? Have also tried the USB driver cleaner and the universal android USB drivers.
Also tried the adb wireless app,no go?
I am also having this issue.
I have used the Google Generic Driver for Android
I also couldn't get adb working from the booted into normal rom state. But fastboot worked ok from fastboot mode for me.
I had attempted to NOT even look up fastboot devices. I actually honestly proceeded with "adb reboot bootloader" then "fastboot flash recovery recovery.img" BUT instead of recovery.img I downloaded directly from Twrp "twrp-3.0.2-1-x2" and flashed that and it all worked out.
FIXED
****************FIXED*******************
Took a clean intall of Win 10. Permissions popped up after plugging in phone. Now rooted.
Related
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.
As the title suggests, bootloader unlocked no problem, tablet was connecting to ADB at the time, tried to flash recovery which as far as I can tell was not successful (I can't boot to recovery, get the injured Android icon), now I can't connect to ADB (get the "List of devices attached" result). So I'm completely stuck, can't move forward, can't go back to stock, what do I do?
Edit: Apparently it's an issue with my PC, my wife's PC worked fine, why it worked to unlock the bootloader and then stopped I have no idea. Can anyone link me to a solution to get ADB working on my PC again? I tried removing/re-installing drivers, rebooting, you name it, no luck.
With your device booted into recovery or the system do you get anything in device manager? If you get a device with a yellow exclamation mark, right click it. Go to where it allows you to choose a driver from a list on your computer. Select adb android composite (or something like that)
Sent from my Nexus 5 using XDA Free mobile app
Thanks for replying.
So before unlocking the bootloader, with USB debugging enabled I could get the tablet to connect using the ADB driver and could access it with ADB but could not access storage for file transfer, with USB debugging disabled and switching the driver manually to the MTP driver I could access storage but not ADB. I have had other device drivers installed on this PC for my Galaxy phones, I had issues initially with the tablet connecting but showing a yellow exclamation mark, then I removed all of the Android USB devices using USBDeview and installed the 15 second ADB tool to get it working, I'm on Windows 8.1 BTW.
After unlocking the bootloader, with USB debugging enabled I cannot get the tablet to connect using the ADB driver and but it does show as an ADB device with no yellow exclamation mark, I just get the "List of devices attached" result and anything that tries to access the device via ADB hangs or fails. I can still switch the driver to MTP and access the storage just fine.
My wife's PC is a Win7 box and has never had android drivers or ADB installed, I used the 15 Second ADB installer on her PC and the tablet works for ADB and storage access with USB debugging turned on, so there's something I'm missing that needs to be wiped out or reset on my box.
My end goal is stock lolipop rooted.
I botched a flash and now I cant get developer mode / ADB working.
When I started, my tablet was stock ROM, towelroot. I connect tablet in developer mode, flashed dual recovery and everything was great. I copied the pre-rooted lolipop ROM to my SD card and flashed it. HOWEVER instead of turning off the device, I selected reboot from recovery. This resulted in boot loop.
SOOOO, I figured no worries, just flash old ROM and try again. So did this:installed Androxyde Flashtool
opened XperiFirm
downloaded 1276-8392 and 1274-8801 (I've tried the rest using both ROMs btw)
Tools>Bundler>Create>Selected folder>selected SGP312 for device
For branding I entered the above ie 1276-8392
For version I entered the ver ie 10.5.A.230
Flashmode>checked boxes to wipe everything
The flash goes through without a hitch. Under about tablet, I see
Model : SGP312
Android Ver : 4.4.2
Kernel : 3.4.0-perf-g32ce454, [email protected]#1
Build Number : 10.5.A.0.230
I activate USB debugging and unknown sources, connect to USB and Flashtool returns: Device connected with USB debugging turned off
I went into device manager and found the MTP driver. Also of note, the device ID is: USB\VID_0FCE&PID_5194&REV_0228
I downloaded Sony's ADB drivers, tried to manually update device driver and windows7x64 kicked back driver is not for your device.
I edited the INF to include the hardware ID exactly as it appears in device manager and tried again. This time windows let me load the driver. It shows up in device manager as 'Sony sa0107 ADB Interface Driver'
HOWEVER, Flashtool is still giving me the same MTP message and if I cmd prompt "adb devices" I get nada.
Is there a way to verify developer mode on the tablet? What else can I try? The tablet gives me a notification when I connect 'usb debugging mode connected, ready to install software'
Thanks!
_sadpanda said:
I went into device manager and found the MTP driver. Also of note, the device ID is: USB\VID_0FCE&PID_5194&REV_0228
HOWEVER, Flashtool is still giving me the same MTP message and if I cmd prompt "adb devices" I get nada.
Thanks!
Click to expand...
Click to collapse
I had a very similar problem in 2014. I do not want to discourage you, but at the end I send it back to sony for a repair. They gave me a new tablet and said that the mainboard was broken.
Nevertheless, there is a thread in Sony cross device general, where people like you end up: http://forum.xda-developers.com/showthread.php?t=1849170
You can try and search for help there, maybe you have more luck then me.
Its odd... ADB was working and stopped after flash. Is this what you had or just no connection from the start?
Sorry, I misread your post. I thought your tablet would not start and you could not get flashmode working. Sorry for that.
What you could try:
1. Be sure you actually activated USB debugging in developer options
2. When you connect the device, you should get a prompt on the tablet to allow usb debugging from that computer
Maybe try "revoke USB debugging authorisations" in developer options and reconnect
3. Install the drivers from flashtool/drivers/ or install sony pc companion. Delete your old driver from device manager.
4. try switching between MTP and MSC mode in usb connectivity menu
Since ADB worked before it was probably no driver problem. Now you cannot be sure. Most probably you tapped away the said prompt of allowing usb debugging when connecting.
If none of this helps I don't know of anything more. Maybe try different usb ports or even computers.... Or try to flash again
bernddi said:
4. try switching between MTP and MSC mode in usb connectivity menu
Click to expand...
Click to collapse
UGH!!! I'm a jacka$$. I totally forgot about that menu/setting. fixed instantly.
So i forgot the PIN number on my old phone which was not rooted, had no recovery software (Cwm, Xrec, etc.) installed on it, and has usb debugging and auto-mount disabled. We don't know the google account associated with the phone. Basically all I have is the phone and a usb cable. Is there a way to get the user data out of it? Adb won't recognise the device btw. I do apologise if it's a stupid question. The phone automatically connected to the wifi, and I'm on Linux, if that helps. But I managed to get into recovery but adb only recognises the device in sideload mode. The files inside the phone is extremely important to me because it contain photo of my family member that were passed away.
Phone: Vivo V7 Plus
I wanted to try brute-force the PIN with program but unfortuntely the phone will cool down for 7000 second (3hours+)
A phone typically knows of 2 USB modes: ADB & MTP. If MTP mode was enabled and phone supports a USB-C connection then it should be possible to fetch the user-data you're interested in.
jwoegerbauer said:
A phone typically knows of 2 USB modes: ADB & MTP. If MTP mode was enabled and phone supports a USB-C connection then it should be possible to fetch the user-data you're interested in.
Click to expand...
Click to collapse
Hi, first of all thanks for your respond. In order to enable MTP i need to have the phone unlock right? how can i enable MTP if the phone is locked ?
All I know is that ADB is the door to any Android device and nothing than that.
Hey everyone
I'm trying to unlock the bootloader on my Mi A3 (M1906F9SH running stock A11), but for some reason my computer (Windows 10) isn't recognizing it. It doesn't even show in device manager. "adb devices" doesn't identify it as being connected either. Having the phone on, in fastboot or in recovery makes no difference (in recovery it shows the "no command" error). I've tried 3 different usb cable and 3 different usb ports.
Ive tried reinstalling adb drivers, qualcom drivers, ran the 15 seconds ADB installer (again). Tried to add it as a legacy device in device manager but nothing worked.
Then I tried using Linux (sepcifically mAid) but it didnt recognized my phone either.
I recently installed a custom ROM on my poco x3 (and I did so a couple of times in the past with different phones) but it was never this difficult. I honestly don't know where to go from here.
Am I missing something?
diogo-fps said:
Hey everyone
I'm trying to unlock the bootloader on my Mi A3 (M1906F9SH running stock A11), but for some reason my computer (Windows 10) isn't recognizing it. It doesn't even show in device manager. "adb devices" doesn't identify it as being connected either. Having the phone on, in fastboot or in recovery makes no difference (in recovery it shows the "no command" error). I've tried 3 different usb cable and 3 different usb ports.
Ive tried reinstalling adb drivers, qualcom drivers, ran the 15 seconds ADB installer (again). Tried to add it as a legacy device in device manager but nothing worked.
Then I tried using Linux (sepcifically mAid) but it didnt recognized my phone either.
I recently installed a custom ROM on my poco x3 (and I did so a couple of times in the past with different phones) but it was never this difficult. I honestly don't know where to go from here.
Am I missing something?
Click to expand...
Click to collapse
same problem with me
i am also using mi a3 evolution x 7.2
my computer (windows 11) again and again connecting and disconnect usb.
maybe usb port has bad connection.
is usb debugging enabled?
i used ubuntu to root my mi a3 and to install custom ROM, it should show something when in fastboot mode.