Hi,
I initially started out debugging with GDB and got to a point where I wanted to be able to step into an android module/device driver. I could never successfully do it with it GDB so I did lots of searching and found out about KGDB which from all accounts is supposed to be the preferred way of debugging the kernel and modules in Linux based machines. I went through the exercise of getting KGDB cross compiled and inserted on my device and that part went ok. When I try to communicate to the device via GDB (target remote /dev/ttyHSL0) I get a device not found error message even though the file is there when I look at it via adb.
(gdb) target remote /dev/ttyHSL0
/dev/ttyHSL0: No such file or directory.
After doing more investigation and thinking about things a little we know that the way to communicate via an Android handset is with adb so this in itself is probably an indication as to why it's difficult to communicate to the device via KGDB.
Does anyone have any up to date or successful instructions on how to connect to a handset using KGDB?
Thanks
Related
Here's the situation: Couldn't get retainroot working on previous occasion on my 64-bit system. Installed SDK on 32bit Win 7 system and was able to use both beforeupdate.bat and afterupdate.bat. Now...when trying to use any of the MODS available, adb cann't recognize my device and I get error messages like "psneuter failed to execute properly". I've done my searches on this subject in XDA but i don't think anyone else's experience is the same since the Atrix is a bit different. This is the first time i've had so much issues with adb. If anyone has any clue whats going on. I've all but given up on this device. I'm 14 days in with it and all headaches.
fightingcrest said:
Here's the situation: Couldn't get retainroot working on previous occasion on my 64-bit system. Installed SDK on 32bit Win 7 system and was able to use both beforeupdate.bat and afterupdate.bat. Now...when trying to use any of the MODS available, adb cann't recognize my device and I get error messages like "psneuter failed to execute properly". I've done my searches on this subject in XDA but i don't think anyone else's experience is the same since the Atrix is a bit different. This is the first time i've had so much issues with adb. If anyone has any clue whats going on. I've all but given up on this device. I'm 14 days in with it and all headaches.
Click to expand...
Click to collapse
Make sure that you've mounted USB as "None", you can do so by pulling down the notification bar. Hope that helps!
fightingcrest said:
Here's the situation: Couldn't get retainroot working on previous occasion on my 64-bit system. Installed SDK on 32bit Win 7 system and was able to use both beforeupdate.bat and afterupdate.bat. Now...when trying to use any of the MODS available, adb cann't recognize my device and I get error messages like "psneuter failed to execute properly". I've done my searches on this subject in XDA but i don't think anyone else's experience is the same since the Atrix is a bit different. This is the first time i've had so much issues with adb. If anyone has any clue whats going on. I've all but given up on this device. I'm 14 days in with it and all headaches.
Click to expand...
Click to collapse
make sure usb debugging is ON, set usb connection to NONE. I'm assuming you have sdk installed in c:\ of computer. Then go to cmd prompt and type: "cd c:\android-sdk-windows\platform-tools" [enter]
Then, type: "adb devices" [enter]
Should detect device, or something is wrong.
Hell, just go install the CWM and install the mods that way. A lot of them are updated to now work with CWM. See here: http://forum.xda-developers.com/showthread.php?t=1019143
Posted this on the general discussion section but have had no replies, hopefully someone here can help?
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
have you try on a different pc?
maybe on your PC there is some problem with the drivers.
Moreover to connect via
adb u must enable Debug mode on your device in the application menu.
To flash kernel or other directly from your sd you can use the clockwordmode, but to install it you must before
install it and i fear you must use your cable connection
Sent from my GT-I9100 using XDA App
I have tried multiple PCs and a mac, even windows on bootcamp. I have installed drivers on every one, even uninstalled and reinstalled on one. One PC, my laptop was a fresh windows install (it was a linux box but I needed windows to use Odin). I was in debug mode and not in debug mode when attempting adb. Thanks for the suggestions though. As I said, I have tried numerous things and am completely stuck! so frustrating!
"I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device"
Exactly there... you can try to force device to install a different driver.
Double click the unknown device then driver then update driver then find software in your computer then choose manually from a list of device drivers in your computer then show all devices you should see "android adb interface" or something related to google or android.
Try it... i hope this can help you.
Hey guys. I'm trying to root my m8 by using the toolkit. Well, I try to get the Token ID but adb fails since it can't find any devices. I've uninstalled the drivers, re installed, tried different sources, everything and I just can't get it to be recognized by ADB.
Anybody have any ideas? I'm running Win8x64
Regards
Smith
I'm having the same problem
smithisize said:
Hey guys. I'm trying to root my m8 by using the toolkit. Well, I try to get the Token ID but adb fails since it can't find any devices. I've uninstalled the drivers, re installed, tried different sources, everything and I just can't get it to be recognized by ADB.
Anybody have any ideas? I'm running Win8x64
Regards
Smith
Click to expand...
Click to collapse
Make sure your SDK is up to date, and that you are opening the command prompt from the proper location. Also make sure that USB debugging is enabled in developer options on the device.
I've had the same issue. I did all of the above and even tried on a Mac and adb still hasn't recognized my phone. Im on win 7x64. Still researching for an answer.
I'm not sure if this will hold true for everyone, but what worked for me was to updat the adp.exe and dlls. Then after I did that, ran the get token script from the toolbox, open the phone to the home screen, and accept the connection request from the computer.
I ended up having to just start the process over again on a different computer, but it worked, so I'm happy lol.
Regards
Smith
You can also try disabling USB Debugging and re-enabling it while the USB is connected. Works for me so far
I have a couple of questions about Linux and its communication with Android. Linux is supposed to communicate better with your device, right? Or have I been lying myself. So, what exactly are your options to debrick a device using Terminal in Linux ( I'm using ubuntu )? You cannot use adb if you havent enabled USB Debugging mode, which is not enabled on the tablet I'm trying to revive, and cannot use fastboot with no root privileges on the device. All this time I have thought that Linux communicates way better with android devices than Windows does, but I cant find any guides on how to unbrick this tablet. Although I have posted a thread about the specific model, I'm not gonna post it here to make it blah-blah-blah thread, I dont want you to do all the work, I just need somebody to point me in the right direction. Bricked tablet, USB Debugging not checked, not rooted, bootloader locked. What can be done within Linux to Revive the tablet?
Anybody?
Well, all the inter operating system communication is relative. I personally prefer Linux. And fast boot doesn't need root. If your device isn't booting up yet try using lsusb after plugging the phone to check whether the phone is connected. Add that to udev rules and then fastboot should work
Coltie ~ Did you get this worked out?
Where's your other post w/specs?
Hello all,
EDIT (20180902 @ 1230 EDT): So, it must be a driver issue on my desktop machine, as I was able to communicate with the phone using my laptop (the original computer I used to root the phone). If anyone cares to explain anything to me regarding my original post, feel free, but consider the original issue solved. I have other issues that are unresolved though, such as the lack of operational wifi/BT (no MAC address) that I would gladly accept help with.
I'm attempting to turn an old Stratosphere into a portable Kali Linux device, and I thought the first step would be to root it. I followed these instructions: "https://rootzwiki.com/topic/7840-kernel-guide-root-your-stratosphere/" and everything seemed top be fine, however, now I have no MAC address (among other things) so I cannot connect to wifi. Much googling later, still no resolution found.
So, I ended up installing the CWM recovery by following this: "https://rootzwiki.com/topic/11949-recovery-clockworkmod-recovery-v-5027/". I did a heard reset, factory reset, and rebooted. Now, when attempting to flash the stock ROM using Heimdall and running heimdall detect, I get an libusb error -12, and even though Heimdall then reports "device detected", I cannot flash the ROM (get same libusb error).
I'm new to this whole process. I'm not an Android developer, programmer, etc. I consider myself relatively computer-literate. I have a little bit of Linux experience, but I'm currently using Win10 for all of this experimentation. I'm not sure what I've done wrong, or how to fix it. Why did the MAC address disappear? I have no BT either. I always thought the MAC address was a hardware parameter, but I'm assuming that flashing the rooted image is what has caused this issue.
Anyway, the Stratosphere is running Android 2.3.6. Any help would be appreciated. Thanks in advance