Related
I am trying to access my phone through ADB to register w/o data. My device center and device manager both see the phone ("Android Phone" in DC, and "ADB Interface > HTC Dream" in DM). However, when I run ADB from the command line it cannot find my device. I have tried reinstalling drivers, killing and starting the ADB server, and even re-flashing my phone.
Note: When booting the phone from a fresh flash I DON'T have to enter "<enter>setprop persist.service.adb.enable 1<enter>" to initialize ADB. It is automatically seen as an ADB device, and after entering the command it is only seen as a storage device.
Thanks in advance.
(unlocking a Dream on Windows 7 x64)
Solved it by installing the drivers from here: http://www.mydigitallife.info/2009/08/24/workaround-for-htc-hero-sync-problem-in-windows-7/
How to unbrick soft bricked Atrix, I installed http://www.youtube.com/watch?v=wQvrEH74dgI and when I installed Gapps, it didn't started and when I tryed system restore it did so but when it started it got stucked at "M" screen and nothing else is happning.
knotabs loca
manyelski said:
How to unbrick soft bricked Atrix, I installed http://www.youtube.com/watch?v=wQvrEH74dgI and when I installed Gapps, it didn't started and when I tryed system restore it did so but when it started it got stucked at "M" screen and nothing else is happning.
Click to expand...
Click to collapse
I'm in a similar situation. I was asked to use latest CWM. I happened to use Tenfar's CWM that came with the boot loader unlock.
I haven't tried it yet. Will give a shot this weekend
Hi!
I'd suggest the following:
1. Install ADB from the Android SDK.
2. Turn on Settings -> Applications -> Development -> USB Debugging.
3. Connect your phone to a computer. (If you do not have a cable, have it connect to the same local network.)
4. Select 'Motorola Phone Portal' as connection method.
5. Reboot while holding Vol. Down.
6. When you see 'Fastboot', tap Vol. Down until 'Early USB Enumeration' appears.
7. Press Vol. Up.
8. Go to a command line where your ADB executable is.
8a. If you have connected by network, find out your device's IP address and type adb connect <IP>
9. Type adb wait-for-device
10. Type adb logcat
Now, Android's system log should appear. Scroll up and carefully look for error messages - the cause for this could be widely different, I had the same problem with 'Error: ID mismatch' or something along those lines. It is likely that the application itself is the problem, and that uninstalling it will fix things. If you come to that conclusion from the log:
11. Terminate logcat (Ctrl+C, usually)
12. Type adb shell
13. Type cd /data/app
14. Type ls *gapps* (If that fails, type ls and look manually)
15. Take the file name for Gapps' .apk and type rm <filename>
16. Reboot
17. Rejoice
Sincerely,
V
PS: Will I always have to enter a captcha when posting, or is this just for noobs? I HATE captchas.
Intelensprotient said:
Hi!
I'd suggest the following:
1. Install ADB from the Android SDK.
2. Turn on Settings -> Applications -> Development -> USB Debugging.
3. Connect your phone to a computer. (If you do not have a cable, have it connect to the same local network.)
4. Select 'Motorola Phone Portal' as connection method.
5. Reboot while holding Vol. Down.
6. When you see 'Fastboot', tap Vol. Down until 'Early USB Enumeration' appears.
7. Press Vol. Up.
8. Go to a command line where your ADB executable is.
8a. If you have connected by network, find out your device's IP address and type adb connect <IP>
9. Type adb wait-for-device
10. Type adb logcat
Now, Android's system log should appear. Scroll up and carefully look for error messages - the cause for this could be widely different, I had the same problem with 'Error: ID mismatch' or something along those lines. It is likely that the application itself is the problem, and that uninstalling it will fix things. If you come to that conclusion from the log:
11. Terminate logcat (Ctrl+C, usually)
12. Type adb shell
13. Type cd /data/app
14. Type ls *gapps* (If that fails, type ls and look manually)
15. Take the file name for Gapps' .apk and type rm <filename>
16. Reboot
17. Rejoice
Sincerely,
V
PS: Will I always have to enter a captcha when posting, or is this just for noobs? I HATE captchas.
Click to expand...
Click to collapse
I can't turn on my phone, or DO ANYTHING with it, the only thing is that I get "M" screnn taht's all, if i want to turn it down I hae to do a battery poll.
Excactly, that's what Early Enumeration is for Usually, USB is loaded when the OS is up, I suppose - at least you can't normally connect with ADB during boot. However, with Early Enumeration set, you can connect while the phone is still booting and access every capability ADB or the shell is able to provide. (Granted, uninstalling the .apk in question with adb uninstall did not work for me, that's why I posted the manual approach, but that may have been an error on my side.)
I wonder if my issue is the same. Mine is stuck in a 'dual core' reboot over and over.. I can't get into recovery mode or anything. Sometimes I hate phones.
JeRrYFaR said:
I wonder if my issue is the same. Mine is stuck in a 'dual core' reboot over and over.. I can't get into recovery mode or anything. Sometimes I hate phones.
Click to expand...
Click to collapse
Mine is tha same
Stuck in mortorola unlocked boot screen
Intelensprotient said:
Hi!
I'd suggest the following:
1. Install ADB from the Android SDK.
2. Turn on Settings -> Applications -> Development -> USB Debugging.
3. Connect your phone to a computer. (If you do not have a cable, have it connect to the same local network.)
4. Select 'Motorola Phone Portal' as connection method.
5. Reboot while holding Vol. Down.
6. When you see 'Fastboot', tap Vol. Down until 'Early USB Enumeration' appears.
7. Press Vol. Up.
8. Go to a command line where your ADB executable is.
8a. If you have connected by network, find out your device's IP address and type adb connect <IP>
9. Type adb wait-for-device
10. Type adb logcat
Now, Android's system log should appear. Scroll up and carefully look for error messages - the cause for this could be widely different, I had the same problem with 'Error: ID mismatch' or something along those lines. It is likely that the application itself is the problem, and that uninstalling it will fix things. If you come to that conclusion from the log:
11. Terminate logcat (Ctrl+C, usually)
12. Type adb shell
13. Type cd /data/app
14. Type ls *gapps* (If that fails, type ls and look manually)
15. Take the file name for Gapps' .apk and type rm <filename>
16. Reboot
17. Rejoice
Sincerely,
V
PS: Will I always have to enter a captcha when posting, or is this just for noobs? I HATE captchas.
Click to expand...
Click to collapse
How do you find the device's IP address?
[GUIDE] Connecting the LG G3 to Linux/ADB (Aka stop "waiting for device....")
A bunch of people seem to be having trouble using Linux and ADB with their new phones. This is a step-by-step guide. I hope it helps some people.
Disclaimer: I am not responsible for anything you do to your devices. Following these instructions may or may not damage your phone or computer or anything else. You understand that following these instructions is done at your own risk.
THIS GUIDE DOESN'T WORK FOR VERIZON USERS ---> Edit: Thanks to Annoyingduck, we have the technique for the Verizon variant in post #5. If you are a VZW user, start with step #8 below and then replace steps 14 and 15 with annoyingducks instructions!
This has been tested on Ubuntu 14.04. Other variants may require some small changes.
This has been tested on the D851 (TMobile) variant. Sprint and ATT should be the same I think.
REQUIREMENTS: You must have root access to your linux box.
1. Unplug your phone from the computer
2. Make yourself a "developer" on your phone. Settings > General > About phone > Software information ... then tap "Build number" a bunch of times until it says "You are now a developer" or something like that.
3. Go into the developer settings ... Settings > General > Developer options
4. Check "USB Debugging"
5. Plug the phone in to your computer
6. Drop down the notifications menu and click on the item that has the subtitle "Tap for more USB options". Most likely, the main title will say "Media Device (MTP)". Anyway - click on that.
7. Then choose the option "Send Images (PTP)"
8. Tap your way back Home and then eject and unplug the phone from your computer again.
http://developer.android.com/sdk/installing/index.html?pkg=tools
9. As root, edit or create the file: /etc/udev/rules.d/51-android.rules
10. Add this line (if it isn't already there) Note that the idVendor is 1004 !!! :
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666", GROUP="plugdev"
11. Save the file and then run (as root):
Code:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
12. Then as root, run:
Code:
sudo service udev restart
13. Then:
Code:
sudo killall -9 adb
14. Plug your phone in, then try
Code:
adb devices
15. Hopefully, you'll see something like "LGD85149abcd01 device" ... which indicates that it is time to celebrate.
Now go root your phone or start developing uber-apps or something else equally awesome.
If the guide was useful, don't forget to hit Thanks!
Good luck!
Frank.
PS. Special shout out to the guys who developed PurpleDrake. I hope this guide helps some of the questions that are being asked on that thread ... and eases their work load.
thanks.
this will definitely help those who want to try purpledrake root
I get lost at step 9 lol.
ailima said:
A bunch of people seem to be having trouble using Linux and ADB with their new phones. This is a step-by-step guide. I hope it helps some people.
Disclaimer: I am not responsible for anything you do to your devices. Following these instructions may or may not damage your phone or computer or anything else. You understand that following these instructions is done at your own risk.
THIS GUIDE DOESN'T WORK FOR VERIZON USERS
This has been tested on Ubuntu 14.04. Other variants may require some small changes.
This has been tested on the D851 (TMobile) variant. Sprint and ATT should be the same I think.
--> NOTE: Verizon users need to connect to ADB a little differently. <-- You'll have to find different instructions.
REQUIREMENTS: You must have root access to your linux box.
1. Unplug your phone from the computer
2. Make yourself a "developer" on your phone. Settings > General > About phone > Software information ... then tap "Build number" a bunch of times until it says "You are now a developer" or something like that.
3. Go into the developer settings ... Settings > General > Developer options
4. Check "USB Debugging"
5. Plug the phone in to your computer
6. Drop down the notifications menu and click on the item that has the subtitle "Tap for more USB options". Most likely, the main title will say "Media Device (MTP)". Anyway - click on that.
7. Then choose the option "Send Images (PTP)"
8. Tap your way back Home and then eject and unplug the phone from your computer again.
http://developer.android.com/sdk/installing/index.html?pkg=tools
9. As root, edit or create the file: /etc/udev/rules.d/51-android.rules
10. Add this line (if it isn't already there) Note that the idVendor is 1004 !!! :
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666", GROUP="plugdev"
11. Save the file and then run (as root):
Code:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
12. Then as root, run:
Code:
sudo service udev restart
13. Then:
Code:
sudo killall -9 adb
14. Plug your phone in, then try
Code:
adb devices
15. Hopefully, you'll see something like "LGD85149abcd01 device" ... which indicates that it is time to celebrate.
Now go root your phone or start developing uber-apps or something else equally awesome.
If the guide was useful, don't forget to hit Thanks!
Good luck!
Frank.
PS. Special shout out to the guys who developed PurpleDrake. I hope this guide helps some of the questions that are being asked on that thread ... and eases their work load.
Click to expand...
Click to collapse
Great and useful guide Bro !
For Verizon, just enable debugging, connect phone, choose internet connection, ethernet (that will enable debugging), then in terminal just run sudo adb devices, the rsa key will pop up on screen, check it to always allow. Adb will show device as offline in the terminal window, now just run adb devices again without sudo and your good to go...
Thank you!
If you have ARCH / Manjaro or any ARCH base just type
sudo pacman -S android-udev
Plug in phone and profit
Just as an FYI to Fedora and CentOS 64 bit users: If you get an error about libraries missing you need to add the 64 bit libraries.
Code:
yum clean all
Code:
yum update
Code:
yum install glibc.i686 zlib.i686 libstdc++.i686 ncurses-libs.i686
After that you should be good.
annoyingduck said:
For Verizon, just enable debugging, connect phone, choose internet connection, ethernet (that will enable debugging), then in terminal just run sudo adb devices, the rsa key will pop up on screen, check it to always allow. Adb will show device as offline in the terminal window, now just run adb devices again without sudo and your good to go...
Click to expand...
Click to collapse
This worked for me.
I thank this guide will help too
But, don't use his files to root only the orignal purpledrake files from xda !
http://www.androidrootz.com/2014/07/how-to-root-lg-g3.html
Awesome, thanks. Always try look for those vendor ID's and stopping my phones of trying to install some darn Windows applications.
Android is Linux, why does it need Windows to function?
Thank you!
If i may to add more links for what help others:
ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.3+ (and for win 8+)
http://forum.xda-developers.com/showthread.php?t=2588979
Fastboot problems on Windows 8+ x64 with USB 3.0
http://forum.xda-developers.com/showthread.php?t=2256359
How to install ADB and Fastboot on Windows for use with Android [Guide] 2 methods
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Thanks!!! This really helped
Thank you
Very helpful
Thanks for the guide. Would it work on Mac OS X ?
Ths,it wroks pretty good.
Didn't work first time even though I took great care in implementing the command line steps (permissions, file name, file contents, location). Had to go back from the start to notice the PTP step! Howcome it needs to be in Picture Transfer mode? ...Not essential, as I have adb working now, but thought someone might know.
Many, many thanks! Incidentally, i'm only putting it in debugging mode to hunt down what's turning on my G3's Bluetooth by itself. I've never turned BT on nor have I paired it with anything for any reason. I've had the phone two weeks and I've turned bluetooth off a half-dozen times or so. It shows no correlation with Airplane Mode or the WiFi NFC switch or anything else - just happens while the phone is sitting unattended. If anyone has insight on that one, please share it w/me somehow.
Additional steps
If after the steps above device is not detected by sudo ./adb devices, turn off development options: click all apps button->click Settings->click General->Developer options->turn it off, change phone connection to "charging", then change connection to "Send Images (PTP)", and turn back on Developer options, run sudo ./adb devices, and it should detect the phone
Thank you very much. Works for me - LG-F460K 4.4.2
Would this work on LG G4? Currently I have the "waiting for device" problem.
Hi Folks,
I'm trying to send AT command and retrieve it's output via adb shell or an app.
I tried several stuff I already found here, like service ATFwdCmd but it didn't exist in MTK device.
I found with getprop that the "baseband" device must be on /dev/ttyC0 but on my device it didn't exist.
output of getprop
[rild.libargs]: [-d /dev/ttyC0]
[rild.libpath]: [/system/lib/mtk-ril.so]
So I started reversing the mtk-ril.so and found that there is a "property_get("mux.debuglog.enable")", and I tried to set this property with setpropex but it's not working too.
I tried using atinout tool at sourceforge with echo 'at+cops?' | atinout - /dev/ttyGS0 -. I also tried the MTK Engineering App and tried to enable full modem log, without luck again.
I'm stuck at here now, if anyone has an idea, i will be very happy to speak with him
PS: sorry for my bad english
Cheers,
Jon
hi, did you solved this ?
I also need to send AT commands on a MTK device, but I have no luck .
Using "cat /dev/pts/4 &" & "echo -e 'ATI\r' > /dev/pts/4" approach gives me no predictive response (the output is sent to logcat and ...partially to the above background process (even when calling "stop ril-daemon", i suspect this is doing nothing, the mtkrild process is still running, killing the mtkrild ..is no solution, the connectivity is lost).
Is there any reliable way we can use mtkrild directly to send AT Commands "
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Same issue - following
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Sunil_511 said:
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Click to expand...
Click to collapse
Hi, Sunil_511...
Bit speculative this, and I can't say for certain if the following solution would work, because I've never had this problem myself. It also requires that your Nexus 7 be in a fully bootable state.
Go to your Nexus 7 Developer Options in the devices settings and tap on 'Revoke USB debugging authorisations'. Tap on OK to confirm. See attached screenshot.
This, theoretically, should wipe the slate clean.
Reboot both your N7 and your PC/laptop and when you next reconnect your N7 to your PC/laptop, you'll be asked to authorise this new USB connection when you perform some action that requires it.
Well, that's the plan anyway.
Good luck?.
Rgrds,
Ged.
Nope, in my case my tab is not booting to recovery or system. The only option is adb and it is showing unauthorized. My last option what i think off is to change the motherboard.
Following
I have the same error and like to follow
Sunil_511 said:
I have the same error and like to follow
Click to expand...
Click to collapse
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
thanks buddy, i have tried pushing the adb keys but no luck. I will try tge second option. Will let you know after trying.
No difference still the same
BxG4ever said:
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Click to expand...
Click to collapse
tnsmani said:
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
Click to expand...
Click to collapse
Tried your suggestion.. Which i might have tried eventually from googling.. Doesn't make any difference.
Fixed
After doing all the researches, i had to buy a new motherboard and then replace it. Installed new rom and now using it. Spared about 1400INR for a 32 gig version.