so i'm running Fresh .3 despite what my sig says haha
i'm having a problem running adb. i use terminal on my mac. i am fully rooted and nand unlocked. but this is my problem...
Code:
Matts-Computer:~ Matt$ cd ~/desktop/sdk/tools
Matts-Computer:tools Matt$ ./adb remount
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Matts-Computer:tools Matt$
it happens every time :/
can anyone help?
thanks in advanced.
mrchu001 said:
so i'm running Fresh .3 despite what my sig says haha
i'm having a problem running adb. i use terminal on my mac. i am fully rooted and nand unlocked. but this is my problem...
Code:
Matts-Computer:~ Matt$ cd ~/desktop/sdk/tools
Matts-Computer:tools Matt$ ./adb remount
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Matts-Computer:tools Matt$
it happens every time :/
can anyone help?
thanks in advanced.
Click to expand...
Click to collapse
you aren't in disk mode are you? you need to be in charge mode and usb debugging needs to be checked.
apristel said:
you aren't in disk mode are you? you need to be in charge mode and usb debugging needs to be checked.
Click to expand...
Click to collapse
i'm in charge mode and usb debugging is checked
i'm going crazy trying to fix this..
mrchu001 said:
so i'm running Fresh .3 despite what my sig says haha
i'm having a problem running adb. i use terminal on my mac. i am fully rooted and nand unlocked. but this is my problem...
Code:
Matts-Computer:~ Matt$ cd ~/desktop/sdk/tools
Matts-Computer:tools Matt$ ./adb remount
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Matts-Computer:tools Matt$
it happens every time :/
can anyone help?
thanks in advanced.
Click to expand...
Click to collapse
have you tried updating your android sdk files? have you tried restarting both computer and phone? restarting the specific adb server (adb kill-server)?
i've never seen this error message before from adb. it seems very distinct though, have you tried googling this error message?
I have noticed sometimes when switching roms, even if USB debugging is checked I need to uncheck and check again to get it to work. Other than that, everything should work fine if your on OSX. hmm...
SOLVED
Big thanks once again to vladthedog!
vladthedog said:
HEH! Sorry , I didn't even realize it was the same person! are you able to run
Code:
sudo adb kill-server
sudo adb start-server
adb devices
First line is killing the server
Second line re-starts the server as root (this is REQUIRED)
third line will tell you if all went well
I ran round and round with this initially. the server HAS to start as root. Problem is, you can start the server with NO error messages as someone other than root, and then you will think all is well.
Click to expand...
Click to collapse
/SOLVED - note, tried again to make sure and got "adb not recognized command" or something simlar, so i just did
Code:
sudo su
./adb kill-server
./adb start-server
than i could exit root and it worked still. had to be in the sdk/tools folder for it to work. seems i still haven't gotten ADB into the proper setting to run w/out being in the directory.
[email protected] ~/sdk/tools $ adb devices
List of devices attached
???????????? no permissions
[email protected] ~/sdk/tools $ adb get-state
unknown
[email protected] ~/sdk/tools $ adb remount
error: insufficient permissions for device
Click to expand...
Click to collapse
i have USB debugging enabled.
it does this on every rom i try. currently using latest cyanogen.
not sure how to go about getting 'permission' so i can run ADB commands to my phone.
OS is Linux Mint 9, tried it as SU/ROOT also, get the same thing.
Try another os/computer with your phone and see if you still get the error
http://forum.xda-developers.com/showthread.php?t=722854
there's a thread on someone having java issues with linux mint, but there are multiple posts (prior to figuring out it was java) on other things about getting adb running in linux. look for my post (the long one) because it sounds like you just need to get the device running as root.
vladthedog said:
http://forum.xda-developers.com/showthread.php?t=722854
there's a thread on someone having java issues with linux mint, but there are multiple posts (prior to figuring out it was java) on other things about getting adb running in linux. look for my post (the long one) because it sounds like you just need to get the device running as root.
Click to expand...
Click to collapse
yeah that was my thread =P
ADB worked on this phone fine for a while than just recently started saying No Permissions. I didn't delete anything, didn't adjust anything, all I've done is flash different roms on the phone.
S'pose i'll steal the wifes laptop and load ADB onto it and give it a go later tonight.
HEH! Sorry , I didn't even realize it was the same person! are you able to run
Code:
sudo adb kill-server
sudo adb start-server
adb devices
First line is killing the server
Second line re-starts the server as root (this is REQUIRED)
third line will tell you if all went well
I ran round and round with this initially. the server HAS to start as root. Problem is, you can start the server with NO error messages as someone other than root, and then you will think all is well.
yeah thats what i just did to see and it indeed worked, than came here to post i found it and read yours so now i feel fantastic =D
slowly still learning linux. i might switch from Mint to Ubuntu since it seems to have more made for it and more support out there for a newbie such as myself.
i should also add, i unplugged my usb wireless mouse thinking it may of interfered with it, but seeing that you posted what i tried i'll go that it wasn't it. just a note to anyone else.
Nrre said:
yeah thats what i just did to see and it indeed worked, than came here to post i found it and read yours so now i feel fantastic =D
slowly still learning linux. i might switch from Mint to Ubuntu since it seems to have more made for it and more support out there for a newbie such as myself.
i should also add, i unplugged my usb wireless mouse thinking it may of interfered with it, but seeing that you posted what i tried i'll go that it wasn't it. just a note to anyone else.
Click to expand...
Click to collapse
I'd recommend Ubuntu as well. Over the years I've goofed around with linux, but about 6 months ago I ended up taking the plunge and removing my windows partition and going full-on linux. I've found that ubuntu seems to have the most support out there for us newbies.
Now that I'm more confortable, i've installed a few different flavors of linux on my laptop, but always find myself coming back to ubuntu. again, its primarily because of the support issue when I screw something up
Yeah I am right now switching to Ubuntu since there is a ton more support out there. Loading up the flash drive with it right now.
Once again thanks for all the help.
vladthedog
Thanks that saved my life
Works on Pardus-Linux 2011.2-CONFIRMED
vladthedog said:
HEH! Sorry , I didn't even realize it was the same person! are you able to run
Code:
sudo adb kill-server
sudo adb start-server
adb devices
First line is killing the server
Second line re-starts the server as root (this is REQUIRED)
third line will tell you if all went well
I ran round and round with this initially. the server HAS to start as root. Problem is, you can start the server with NO error messages as someone other than root, and then you will think all is well.
Click to expand...
Click to collapse
Thanks for the post...I was racking my brain trying to get ADB working on Pardus-Linux. I used to be an Ubuntu guy and recently saw the light...LOL.
Thanks for the help.
thanks
thanks i got it WHOO hoo View attachment 1282945 srry i had to re-edit it for my device id
Thank you man ! This procedure also worked for me on Linux Mint !
I was about to try on windows, what a shame...
Now next to the i9500 Quick Flasher there also is the i9505 Quick Flasher, just slight changes to make partitions match
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
www.broodplank.net/I9505-Quick-Flasher-1.0.zip
Created for a fail-safe flash operation of boot.img and recovery.img, all other partitions (currently only system) are experimental.
broodplank1337 said:
Now next to the i9500 Quick Flasher there also is the i9505 Quick Flasher, just slight changes to make partitions match
Download:
www.broodplank.net/I9505-Quick-Flasher-1.0.zip
Created for a fail-safe flash operation of boot.img and recovery.img, all other partitions (currently only system) are experimental.
Click to expand...
Click to collapse
Tried this, it cannot connect to my S4. Yes, I have debugging enabled, and yes my device is in mtp mode.
I get:
Running checks, please wait...
<<< I9505 USB Connection >>>
[ ] I9505 USB Connection
Your I9505 is not connected or unreachable! Please read the instructions for reference.
Snakefood said:
Tried this, it cannot connect to my S4. Yes, I have debugging enabled, and yes my device is in mtp mode.
I get:
Running checks, please wait...
<<< I9505 USB Connection >>>
[ ] I9505 USB Connection
Your I9505 is not connected or unreachable! Please read the instructions for reference.
Click to expand...
Click to collapse
I had some issues with usb as well when I was testing the tool out, but It was fixed after a while, its actually not the tool but the way of mounting usb on the i9505. I fixed it by replacing the adb.exe file with the latest one (which is also included in the zip tho). Can you please test for me if your able to get a normal adb shell? (open cmd window in the quickflasher dir and type "adb shell"), if it says device not found there is an issue with debugging mode. if not then you should test this and pls give me the info:
adb get-state (should return "device")
adb devices (should return a connected device)
If you get negative results here you should kill adb.exe (taskkill /f /im adb.exe for group kill) and try again.
If it does work pls enter:
adb root
adb remount
adb shell
and tel me what you see.
The usb mode is a struggle on the i9505.. I thought hey lets upgrade to CM so I will have mass storage mode.. but no way, only MTP and PTP... (I added the Mass storage option and forced it to be available on my private build, but it still doesn't work..)
Currently trying to find out how to permanently enable oldskool mass storage + adb.
broodplank1337 said:
I had some issues with usb as well when I was testing the tool out, but It was fixed after a while, its actually not the tool but the way of mounting usb on the i9505. I fixed it by replacing the adb.exe file with the latest one (which is also included in the zip tho). Can you please test for me if your able to get a normal adb shell? (open cmd window in the quickflasher dir and type "adb shell"), if it says device not found there is an issue with debugging mode. if not then you should test this and pls give me the info:
adb get-state (should return "device")
adb devices (should return a connected device)
If you get negative results here you should kill adb.exe (taskkill /f /im adb.exe for group kill) and try again.
If it does work pls enter:
adb root
adb remount
adb shell
and tel me what you see.
The usb mode is a struggle on the i9505.. I thought hey lets upgrade to CM so I will have mass storage mode.. but no way, only MTP and PTP... (I added the Mass storage option and forced it to be available on my private build, but it still doesn't work..)
Currently trying to find out how to permanently enable oldskool mass storage + adb.
Click to expand...
Click to collapse
My results:
C:\Windows\system32>cd \
C:\>cd s4 root
C:\S4 root>cd qflash
C:\S4 root\qflash>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: more than one device and emulator
C:\S4 root\qflash>adb get-state
unknown
C:\S4 root\qflash>adb devices
List of devices attached
12138fc0 device
emulator-5554 offline
C:\S4 root\qflash>adb root
error: more than one device and emulator
C:\S4 root\qflash>
Snakefood said:
My results:
C:\Windows\system32>cd \
C:\>cd s4 root
C:\S4 root>cd qflash
C:\S4 root\qflash>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: more than one device and emulator
C:\S4 root\qflash>adb get-state
unknown
C:\S4 root\qflash>adb devices
List of devices attached
12138fc0 device
emulator-5554 offline
C:\S4 root\qflash>adb root
error: more than one device and emulator
C:\S4 root\qflash>
Click to expand...
Click to collapse
ah so you have the emulator in there as well.. thats the problem. to bypass the emulator use:
adb -d
for example adb -d shell or adb -d get-state
do you have an AVD emulator running currently?
broodplank1337 said:
ah so you have the emulator in there as well.. thats the problem. to bypass the emulator use:
adb -d
for example adb -d shell or adb -d get-state
do you have an AVD emulator running currently?
Click to expand...
Click to collapse
What emulator do I have, I've only used the files in your download, as far as I know. Any way to check / remove?
Edit: I had bluestacks installed a while back, but uninstalled it, could this have left some crap behind after it?
Snakefood said:
What emulator do I have, I've only used the files in your download, as far as I know. Any way to check / remove?
Click to expand...
Click to collapse
Hmm the emulator that comes with android sdk, is afaik the only one who can correspond with adb, but it would be odd if you ran it all the time.
check taskmgr, and look for emulator.exe/java.exe, to be sure also kill adb.
You can check if there is an existing emulator if you start AVD manager (if you don't have android sdk at all then its really strange )
broodplank1337 said:
Hmm the emulator that comes with android sdk, is afaik the only one who can correspond with adb, but it would be odd if you ran it all the time.
check taskmgr, and look for emulator.exe/java.exe, to be sure also kill adb.
You can check if there is an existing emulator if you start AVD manager (if you don't have android sdk at all then its really strange )
Click to expand...
Click to collapse
I didn't have sdk installed; I installed it and ran avd manager, doesn't show any installed.
when I run adb -d shell I get [email protected]:/ $
Snakefood said:
I didn't have sdk installed; I installed it and ran avd manager, doesn't show any installed.
when I run adb -d shell I get [email protected]:/ $
Click to expand...
Click to collapse
Ok the output is good. ill add a function to the tool to force adb usb connection
for the meanwhile you can use:
(put boot.img in adb dir)
adb -d push boot.img /sdcard/boot.img
adb -d shell su -c 'dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20'
adb -d shell reboot
broodplank1337 said:
Ok the output is good. ill add a function to the tool to force adb usb connection
for the meanwhile you can use:
(put boot.img in adb dir)
adb -d push boot.img /sdcard/boot.img
adb -d shell su -c 'dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20'
adb -d shell reboot
Click to expand...
Click to collapse
Do I rename my recovery.img from cwm to boot.img for the above, or is this for a different process?
Snakefood said:
Do I rename my recovery.img from cwm to boot.img for the above, or is this for a different process?
Click to expand...
Click to collapse
boot.img = mmcblk0p20
recovery.img = mmcblk0p21
the name of the .img doesn't matter but the partition is important.
Ahh, looking at your image, this now makes sense, I can see the destination partition names as you describe..
Well have a go at this later, unless you plan to release an update later today?
Sent from my Nexus 7 using xda app-developers app
Edit: couldn't get this working, so I just flashed using odin. Thanks for trying to get resolved tho.
Odin is the tool for me, no need more than that.
broodplank1337 said:
ah so you have the emulator in there as well.. thats the problem. to bypass the emulator use:
adb -d
for example adb -d shell or adb -d get-state
do you have an AVD emulator running currently?
Click to expand...
Click to collapse
Hi brood,
just stumbled upon this thread and read about Snakefood's problem.
Although he worked around the error by using Odin I want to give you a hint regarding this specific problem:
he obviously has an adb device installed called emulator-5554 but which is offline. He already gave himself the correct answer:
"I had bluestacks installed a while back, but uninstalled it, could this have left some crap behind after it?"
My diagnose is: yes, BlueStacks definitely leaves a lot of crap behind and does NOT uninstall cleanly. I tested it once and I saw myself compelled to restore an older windows image which I made BEFORE I installed BlueStacks on my windows machine.
BTW: BlueStacks is an Android emulator for Windows but a piece of *%$~#!!! crap, but that's just my humble opinion.
And BlueStacks uses such an adb emulator device entry although I'm not sure if it was called like that. But BlueStacks is not the only Android emulator and most probably other programs of this kind create such an adb entry as well.
skywalker01 said:
Hi brood,
just stumbled upon this thread and read about Snakefood's problem.
Although he worked around the error by using Odin I want to give you a hint regarding this specific problem:
he obviously has an adb device installed called emulator-5554 but which is offline. He already gave himself the correct answer:
"I had bluestacks installed a while back, but uninstalled it, could this have left some crap behind after it?"
My diagnose is: yes, BlueStacks definitely leaves a lot of crap behind and does NOT uninstall cleanly. I tested it once and I saw myself compelled to restore an older windows image which I made BEFORE I installed BlueStacks on my windows machine.
BTW: BlueStacks is an Android emulator for Windows but a piece of *%$~#!!! crap, but that's just my humble opinion.
And BlueStacks uses such an adb emulator device entry although I'm not sure if it was called like that. But BlueStacks is not the only Android emulator and most probably other programs of this kind create such an adb entry as well.
Click to expand...
Click to collapse
Hi Skywalker.
Long time no see . Anyways, OT. I have installed BlueStacks once (in the alpha or beta phase I believe) and I don't remember much of it but I do remember that it was crap idd. Also that it leaves "traces" (if you call adb a trace xd, more like a fail uninstall ) is very lame.. and causing problems for people who are not 100% familiar with adb and its daemon.
The AVD Emulator from the SDK may lag a bit but atleast it doesn't interfere with adb :silly:
Great tool broodplank1337, well done mate this will save ppl from making stupid mistakes
dublinz said:
Great tool broodplank1337, well done mate this will save ppl from making stupid mistakes
Click to expand...
Click to collapse
Thanks ^^, I think that is true hehe, using 'dd' to flash images isn't for the absolute beginner idd ;p
Hi guys,
If you need me to assist more with ahh testing just let me know. Is there an uninstaller to remove what bluestacks left behind, or is the Windows disc the only definite uninstaller
Sent from my GT-I9505 using xda app-developers app
Snakefood said:
Hi guys,
If you need me to assist more with ahh testing just let me know. Is there an uninstaller to remove what bluestacks left behind, or is the Windows disc the only definite uninstaller
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
You should first look in msconfig (start > run > msconfig) at the startup tab and look if there is any startup item from bluestacks.
If there is nothing there look in services.msc (start > run > services.msc) and check for any blue stacks service, and if there is any, disable it.
Next to that you can also use HijackThis (http://sourceforge.net/projects/hjt/) to find startup items. hope it helps
Hey Brood,
See you're doing great work here on the S4 section.:good:
I'm missing your input in the S+ section unfortunatly:crying:
Hey guys!
I've definitely missed something obvious.. and please forgive me in advance
I used to have cyanogenmod 12 installed and had some minor issues that was bugging me. I decided to update the phone with RUU GPE marshmallow.
The phone is working fine now, but I can't use adb commands through usb anymore...
it says
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SH43BWM00xxx offline
I would like to install TWRP 3 but I can't send any commands
how can I get it to work?
phone is S-OFF
and yes.. I have activated usb debugging
check your adb version, command adb version
You need at least 1.0.31 or better 1.0.32
ckpv5 said:
check your adb version, command adb version
You need at least 1.0.31 or better 1.0.32
Click to expand...
Click to collapse
Thanks a lot... I was on my macbook and it didn't work. Tried on my PC and I had a newer version installed there.
Updated the mac adb and everything works on it too