Database Users

ADB Server Out of Date?

I was getting this message on my computer after the adb shell command, but everything seemed to work after that...? After searching about 300 pages (seemed like that many anyways) I looked at the readme file and ended up running the tools\android.bat update sdk command.... I guess it found and update and is re-downloading and installing the entire SDK program again... Is this normal/necessary?
The reason I want that message to go away is because the Pre-Kitchen didn't seem to work after it received that message "adb server is out of date".. I just want to make sure I'm not messing something up by doing this "update"
Thanks..!

nck4857 said:
I was getting this message on my computer after the adb shell command, but everything seemed to work after that...? After searching about 300 pages (seemed like that many anyways) I looked at the readme file and ended up running the tools\android.bat update sdk command.... I guess it found and update and is re-downloading and installing the entire SDK program again... Is this normal/necessary?
The reason I want that message to go away is because the Pre-Kitchen didn't seem to work after it received that message "adb server is out of date".. I just want to make sure I'm not messing something up by doing this "update"
Thanks..!
Click to expand...
Click to collapse
I've gotten that error as long as I can remember...it mostly just happens if there's been a long time between adb sessions or I've disconnected my phone somewhere along the way. It's no big deal, it just restarts itself into a working state and never causes an issue as far as I can tell.

I belive this happens when there is in insstance of ADB currently running in your processes list and you are trying to start a new session.
It should just kill the running ADB and start a new deamon.

OK, I was just wondering, everything seems to work fine as far as I can tell.. I just wanted to make sure I wasn't missing anything.
Thanks!

Permission issues with su and rom .3

Hey guys,
Im new to Android and after being a BlackBerry user for 8 years, anyway heres my issue.
1. I did the root rom per the instructions...no problem
2. flashed the recovery and have that working...no problem
3. downloaded the .3 rom with the built in busybox and su...Here's where things get confussing for me.
I tried to use adb and it asks me (are you root?), tried adb remount and got (operation not permitted) the usb debug is on and working and the su app on the phone maintains a black screen....(I think this is not right...)
Then I closed out the current cmd window...opened a fresh cmd window and typed>adb shell and got $, then i entered su and got # from here im stuck, what are the commands to get back to adb shell and su also how do I get the whitelist permissions working...
In short adb shell worked fine with the original root rom, I'm sure its an operator error any help is appreciated.
Chris

SO if I understood correctly you already have v3 installed?
If you do check on your phone its probably asking you for permission on the phone when you click on always allow the command should go thru adb.
make sure you have debuggin on otherwise all you will get is a black screen when su permission pops up.

t2noob said:
SO if I understood correctly you already have v3 installed?
If you do check on your phone its probably asking you for permission on the phone when you click on always allow the command should go thru adb.
make sure you have debuggin on otherwise all you will get is a black screen when su permission pops up.
Click to expand...
Click to collapse
can you guys post a walk through for noobies? imstuckat black screen

vash8806 said:
can you guys post a walk through for noobies? imstuckat black screen
Click to expand...
Click to collapse
There are plenty around... seriously google it. But, this specific issue I just experienced. Seems on the custom ROM that is out (EvilEris) the SU request screen doesn't work right off the bat. I went and used an app on the device to request root (terminal) then when the black screen pops up, hit back or home, or action. As the phone is basically frozen at this point it prompted me to forceclose the superuser.apk. I did. Once forceclosed, it worked fine.

adb shell
su
look at phone, click allways all
...
..
.
jcase

jcase said:
adb shell
su
look at phone, click allways all
...
..
.
jcase
Click to expand...
Click to collapse
Or just download Terminal Emulator from Market.
open it up.
Type su.
Hit allow/always allow.
Now try it for other stuff (like wireless tether) and see if it pops up instead of a black screen.

haha..I simply went to settings>Applications>Development and checked the USB debugging mode.... [read it on another thread...should have read before I posted...haha]

vash8806 said:
haha..I simply went to settings>Applications>Development and checked the USB debugging mode.... [read it on another thread...should have read before I posted...haha]
Click to expand...
Click to collapse
niiiice

Help! Connecting thru USB, but not able to flash anything

Brand new phone...can't believe i did something wrong only a few hours into it!?
To cut to it, i am not able to run anything on my PC to my Atrix bc the phone is not visible to it via usb sync. It DOES still see it if i needed to transfer files etc, just not so i can flash anything to it off the PC.
And not sure if it has anything to do with it, but it seems like i ran into my problem when i inserted and formatted my SD card. Here's what i did (and i hadn't gotten very far):
I rooted with SuperOneClick, then I installed DG's Adeo ROM and the update.
I was trying to install Gingerbread and was just putting busybox installer on my phone when i went to put my SD card in there from my old phone. i formatted the card and it seemed after i did that i lost connectivity via the USB. It could still access the phone, but everytime i run ATRIX4G_MobileTV_GBTheme.bat it hangs at "daemon started succesfully" . It also hangs if i try to run SuperOneClick again on "waiting for device."
I wasn't sure what to do to get it running right again so i did a full wipe from the settings. Still can't connect
Any help be greatly appreciated. i've literally had this phone 4 hours so sorry if i'm missing something dumb

Try running aRoot (search this forum) and then trying all that.

thanks for that suggestion, gonna try that....just as soon as the damn search function comes back!!
oh the waiting...i am not going to be able to sleep tonight till i get somethin happenin

No need to search, it's only hanging about 3-5 posts down in this section. It's also here:
http://forum.xda-developers.com/showthread.php?t=981866

Ran aRoot - seems to run through the steps without a failure, but it went VERY fast, like 3 seconds...and it hangs when i try to "unroot"
so, all in all it seems like its still not recognizing the phone as before when connected through USB

Dillsnik said:
Ran aRoot - seems to run through the steps without a failure, but it went VERY fast, like 3 seconds...and it hangs when i try to "unroot"
so, all in all it seems like its still not recognizing the phone as before when connected through USB
Click to expand...
Click to collapse
Do you have Root Explorer? If so, look in /sbin and see if you have 'adbd' showing
OR
Have you tried installing the ADB interface from the Android SDK? See if your device can be seen? If not see THIS ARTICLE (external link to addictivetips) on setting up ADB.

No, I don't have Root Explorer
I installed SDK and ADB and it does show up, but only when the USB setting is set to "Motorola phone portal." None of the other options it shows up in device mgr.

I am kinda stabbing in the dark at this point...thinking maybe it's a driver issue?
maybe if i uninstall all the drivers and start from scratch i might have some luck? i actually did unistall all the drivers thru device mgr, but they just came right back next time i connected...so maybe i need to delete them entirely?
any suggestions to trouble shoot this greatly appreciated...i know it's probably small potatos but i'm really jammed up here...

Moved as not android development

Have you tried installing the latest drivers again directly from the Motorola Mobility site? You can install Media Link or just the drivers with MotoHelper. For some reason my phone installed all of this, but there were updates available immediately.
The ADB interface should function when USB is set to None.
Sent from my Rooted Atrix using Tapatalk Pro

Yeah i actually did a system restore and reinstalled all the drivers etc.
I can see the phone now in the device mgr under ADB interface when connection is set to "None" for USB
But still hangs when trying to flash basically anything

Do you have or can you pick up a Terminal Emulator in the Market and list the files in /sbin? See if you have adbd...
From $
su
cd /sbin
ls (Lower case L, not 1)
Look through list of files for adbd.
Sent from my Rooted Atrix using Tapatalk Pro

OK, No it's not in there

See this post here: http://forum.xda-developers.com/showpost.php?p=11738847&postcount=1 and the cooresponding thread for replacing adbd. There's another post in the thread about changing the permissions so that it doesn't get lost again with a reboot. You might have to purchase Root Explorer since you cannot push anything via ADB over USB.
Sent from my Rooted Atrix using Tapatalk Pro

This seems to be the type of problem i am having, very much thanks for directing me to that other thread.
At this point i have copied ADB to the sbin folder but nothing flashing yet...need to read through that thread more and play with it.
What a PITA so far but thanks so much for the help!

No problem. I hope it works out. If you don't mind, post up and let me know if you get it going and what it took so we can try to help others.
Sent from my Rooted Atrix using Tapatalk Pro

[Q] Stuck on splash screen

Good evening everyone.
To start with, yes I've read all the similar topics and none of them helped me
To my problem now. My phone has been flashed with a custom ROM for 1-2 months now (I don't remember exactly) and this morning I woke up to find my phone turned off. While trying to turn it on, no matter how much time has passed, it's stuck on the splash screen refusing to load the home screen
Is there any suggestion that does not involve me losing all my data because I have no backup of them?
Waiting for any suggestions.

See if you can connect with usb, and adb can communicate with device.
If yes, you can save the /data/data folder(in which are all configurations) + /data/app folder(in which are all apps except these on sdcard if any).
You can also run adb logcat from command prompt and see if you can find what app causes the error and the bootloop, and if maybe you can uninstall/reinstall this app, or delete the folder of that app on /data/data folder, to hopefully solve the error.
Try to install a program like QtADB, droid explorer or Android manager to avoid use command line and simplify some of above operations as copy/delete folders or install/uninstall apps.
If you need more help, PM me to speak in greek(it' s better)

I've just installed QtADB and connected the phone while being inside ClockwordMod v4.0.0.5.
The truth is that from here I don't get almost any useful information (don't know why). One positive aspect is that I can copy data from/to the phone.
While stuck in the splash screen I can't connect through adb though.

You mean not at all? Usually when appears IDEOS screen you can connect via adb, after some time and when the error start maybe the device freezes and then adb probably disconects, but until then you can take some useful logcat info for the error.
You can also have some more functions with QtADB on recovery mode if you mount the partitions first.
Maybe and the app manager work then(I haven't tested though).

Managed to get logcat information while turning on the phone. I'm attaching the log file with the error lines.
Trying to read them right now to find a solution. Any help appreciated.

gkaran said:
Managed to get logcat information while turning on the phone. I'm attaching the log file with the error lines.
Trying to read them right now to find a solution. Any help appreciated.
Click to expand...
Click to collapse
By reading your log i think the problem is permissions. Try to fix permissions with recovery tool.

[HELP] ADB Tools not working? Check here.

So you probably have the same problem as i had not long ago, you try using a Tool like Android Command, or SGN3ModTool, or kn0x0ut, or Android AIO Flasher or what not, and it just wont work, and you dont have any idea, why. The answer is pretty simple, yet very hidden and not thought about that much, i first figured it out very lately, and it took some time, so if you are one of them having one of the listed problems above, welcome to my help thread
Q: I get "Device Not Found"
A: Install the latest ADB drivers for all Android Phones, found here: http://adbdriver.com/downloads/
Q: Now i installed all drivers for my Device, but it still wont work. Why?
A: Are you pretty sure "USB Debugging" is enabled in the Developer Options? If not, enable it.
Q: I dont find the "Developer Options" on my Device. How do i get them?
A: I assume you got Android 4.2 or higher, since then, you have to press 7 times on the build number. Go to the "Device Info" tab, and scroll down to "Build Number" and press 7 times in a row on that, it will tell you, that the "Developer Options" have been enabled.
Q: Ok so now i did that, but it STILL wont work, WHY!?
A: Well then i guess you came to the points i landed at, where i didnt know the problem, lucky for you, i found the yet simple, but a bit "Im a Noob, idk that" fix. To fix this, first check your "SELinux Status" under "Device Options", if it is on "Permissive" then it should work for you now, and your good to go, if your in the situation of "Enforced", then you came where i was, no way. How to fix it? Easy, either you can try option 1 or 2. Or just ignore the fact its there and try finding out what it is, until you die trying to find it out
1: (This option might NOT work for some! Samsung Devices, i know it says all in the list, but Samsung Deviced without KNOX will work anyway, and some with KNOX even will, if you disabled KNOX with SuperSU or any other ROOT Tool). Install SELinux Mode Changer
App: https://play.google.com/store/apps/details?id=com.mrbimc.selinux&hl=de
After its installed, enter the app and change it to "Permissive". Reboot your Device, and now try again to connect with USB ADB, it will work guaranteed
2: Install a KERNEL that has SELinux status set to "Permissive" incase the first option does NOT work for you. (Samsung Galaxy Note 3 SM-N9005 ONLY!)
KERNEL 1: http://forum.xda-developers.com/showthread.php?t=2540246
KERNEL 2: http://forum.xda-developers.com/showthread.php?t=2471416
To be honest, i prefer the first KERNEL more, more options and also it has no bugs known for now, the second has some bugs, but less features, if you try staying close to STOCK.
That was all from me for now, if you need more info or help, your welcome to ask.
PM: Want to know what SELinux is? Here: http://en.wikipedia.org/wiki/Security-Enhanced_Linux
Short description: SELinux was invented by the NSA and MAC, to provide more security for Android system, to say it short: To simply **** up the life for Developers . "Enforced" means all request are denied instantly, so thats why ADB USB wont work, cause all requests to the Device are blocked. With "Permissive" this though, makes it so all requests are allowed, but logged and being watched, but still can be run, without problems.

While this is a list with common things that you can do to enable ADB it is still a little misleading - there is ABSOLUTELY no requirement that you NEED to be SELinux permissive for standard ADB to work - that is only the case in certain cooked ROMs + certain kernels, but if you are on stock and you have things installed OK on the PC it will work perfectly with SELinux set to enforcing.
The other thing that is missing is the fact that the latest ADB (since 4.2.x I think) is also doing an extra security-check on the phone - so you need a special adb program on the PC (so that the program can correctly answer to the extra check), and then you need to answer YES when the phone asks if you want to allow ADB rights for that ID (which normally the phone will remember and not ask again).

xclub_101 said:
While this is a list with common things that you can do to enable ADB it is still a little misleading - there is ABSOLUTELY no requirement that you NEED to be SELinux permissive for standard ADB to work - that is only the case in certain cooked ROMs + certain kernels, but if you are on stock and you have things installed OK on the PC it will work perfectly with SELinux set to enforcing.
The other thing that is missing is the fact that the latest ADB (since 4.2.x I think) is also doing an extra security-check on the phone - so you need a special adb program on the PC (so that the program can correctly answer to the extra check), and then you need to answer YES when the phone asks if you want to allow ADB rights for that ID (which normally the phone will remember and not ask again).
Click to expand...
Click to collapse
Thats not correct, i run STOCK ROM, i cannot run any ADB tools without having SELinux set to Permissive, i only want to help people who have the same problem, most people arent like you, who know everything in the world, so they need a bit of help, thats all i wanted to help them with.