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
Related
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...
Hey,
I'm new to rooting and i found out that i had to downgrade my desire hd before i could use VISIONary, so i downloaded all the downgrade files and installed android sdk driver revision 3
I opened cmd and went to the downgrade folder but as i don't want *to brick my phone I tought lets put in a safe command to see if it works so i typed "adb devices" *and it said that adb server is not up to date and then something like this:
* starting daemon*
* daemon started successfully *
Device list
Some letters and numbers connected
Can i just proseed or is something wrong cus i'm worried i'll brick it
Thanks in advance, a new android user
Never mind the downgrade worked perfectly
hi there,
After some hours reading and trying to fix it myself, I have to admin that I need help with rooting my new KFHD8,9 Firmware 8.4.1:
I would rather post in the referring development threads, but I am not allowed to yet. So i am asking here for help
The thing is that all my devices at home are running Linux (Ubuntu 13.04) and I am not trusting the "use-Windows-in-a-VM-and-use-USB-to-root" method
Now I was following the Tutorial from seokhun and decided to use the Bin4ry method to root, because it is delivered with the RunMe-script as a windows-batch and a shell-script.
The android-tools (android-tools-adb, android-tools-fastboot and android-tools-fsutils) have been successfully installed via apt-get and are working (I can use adb and fastboot to get device information).
When I try to execute the RunMe.sh (have made it executable via chmod +x before) and choose the option 1 it is stuck:
Code:
Make a choice:
Please enter a valid number(1 to x):
1
Checking if I should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
Waiting for device to shop up, if nothing happens please check if Windows ADB-drivers are installed correctly!
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
The script hangs at the line with the first use of the delivered adb with the wait-for-device parameter (inside the stuff folder).
Code:
mytest() {
echo "Checking if I should run in Normal Mode or special Sony Mode"
echo "Please connect your device with USB-Debugging enabled now"
echo "Waiting for device to shop up, if nothing happens please check if Windows ADB-drivers are installed correctly!"
./stuff/adb wait-for-device
./stuff/adb pull /system/app/Backup-Restore.apk . > NUL
./stuff/adb pull /system/bin/ric . > NUL
If I run my installed version of adb it terminates successfully with
Code:
adb wait-for-device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]: ...
But when I call the delivered adb inside the stuff folder it never terminates:
Code:
../Root_with_Restore_by_Bin4ry_v30/stuff$ ./adb wait-for-device
adb server is out of date. killing...
* daemon started successfully *
has anybody a clue?
Its me again
I am wondering if i can exchange the delivered ADB with my installed and Working ADB.
If it can be replaced, why is it delivered for Windows and Linux and why most tutorials set them AS requirement proceeding :what:
Sent from my Incredible S using xda app-developers app
Create a live usb with persistent must be an 8 gig usb flash drive for maximum persistent. Use this creator http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/ . Use linux mint maya the mate one with codecs 32bit http://www.linuxmint.com/edition.php?id=105. Boot it and use this script http://forum.xda-developers.com/showthread.php?t=2162973 . That is all you will need good luck. You can use 32bit ubuntu12.04 as well the reason to use these distros is that the newer ones don`t run soupkit installer properly in a terminal it makes the installation much cleaner I have been able to force install on some of the later distros but it`s a serious pain in the rear.
thanks for your reply!
I will try it with Ubuntu 12.04 the next days!
worked fine with Ubuntu 12.04. Thank you very much for the hint!
badbutz said:
worked fine with Ubuntu 12.04. Thank you very much for the hint!
Click to expand...
Click to collapse
Your welcome anytime.:highfive:
Glad i checked forums first
Was going to help a friend root, twrp and cm 10.1 his KF 8.9 after work today. his laptop is running 13.04 ubuntu. glad i ran across this post before wasting significant time. 1'll bring a 12.04 laptop with me. Thanks to Thepooch for sharing this info and have a great week!
Hello friends, I come to expose my problem, if someone can help me, I would appreciate it very much.
I have installed the latest [TOOL]Minimal ADB and Fastboot [1-6-17] in my Win 10 64bit PC, The PC recognizes me device, I can install the TWRP (.28) by fastboot and works great later flash again the stock recovery (recovery_OBT8N.img) and try to install the oficial OTA with sideload, it say "cannot read", I try:
* Re-installing the ADB drivers from others.
* With the original file name, and with the name modified "update.zip".
* Reboot my PC and device.
* Used the Ccleaner.
* With Adm CMD
* Leaving and entering the address where are the drivers and the file, with the CMD
* Typing: adb kill-server. adb root. adb sideload update.zip
* typing the file name: "update.zip" - "update" - "update.zip.zip"
* Putting the drivers in another direction
* Try differents files: ("OB10.zip" and "OOS4.zip"
* Use generic adb and nexus adb
* The lasted Stock recovery (recovery_OBT8N.img)
I know I can install OOS4 with twrp, I know because I have it, but I wanted to remove the DM-verity message and I followed this guide: [FIX] Device-Mapper-Verity fix for Oxygen OS Nougat Rom ( 4.0 and Open Beta's) And that's how I knew I can not use the sideload....
If anyone knows that I could try more, thank you very much, thank you.
ERNZT said:
Hello friends, I come to expose my problem, if someone can help me, I would appreciate it very much.
Click to expand...
Click to collapse
More info would be a pleasure ur on twrp? Boot into it type adb push Filename /sdcard/ it should push the file to /sdcard/ so you can manually flash it.
ERNZT said:
Hello friends, I come to expose my problem, if someone can help me, I would appreciate it very much.
I have installed the latest [TOOL]Minimal ADB and Fastboot [1-6-17] in my Win 10 64bit PC, The PC recognizes me device, I can install the TWRP (.28) by fastboot and works great later flash again the stock recovery (recovery_OBT8N.img) and try to install the oficial OTA with sideload, it say "cannot read", I try:
* Re-installing the ADB drivers from others.
* With the original file name, and with the name modified "update.zip".
* Reboot my PC and device.
* Used the Ccleaner.
* With Adm CMD
* Leaving and entering the address where are the drivers and the file, with the CMD
* Typing: adb kill-server. adb root. adb sideload update.zip
* typing the file name: "update.zip" - "update" - "update.zip.zip"
* Putting the drivers in another direction
* Try differents files: ("OB10.zip" and "OOS4.zip"
* Use generic adb and nexus adb
* The lasted Stock recovery (recovery_OBT8N.img)
I know I can install OOS4 with twrp, I know because I have it, but I wanted to remove the DM-verity message and I followed this guide: [FIX] Device-Mapper-Verity fix for Oxygen OS Nougat Rom ( 4.0 and Open Beta's) And that's how I knew I can not use the sideload....
If anyone knows that I could try more, thank you very much, thank you.
Click to expand...
Click to collapse
Most of the times the problem is really on the desktop configuration, ie usb drivers, adb version, usb port power, user profile permissions, etc. Note that you need a newer adb version to do stuff such as sideload. From the top of my head, I think you need 1.0.32 or newer. I know it seems overkill, but until google decides to distribute the platform tools in a separate minimal bundle, the best option is to install the android SDK. You can choose then to selectively install only the platform tools that include adb.
Sent from my ONEPLUS A3000 using Tapatalk
https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47 is definitely the best fix i found, if it doesn't work reboot your PC and do it again it worked for me.
Hope it can helps
Minimal ADB and Fastboot>adb devices
List of devices attached
adb server version (31) doesn't match this client (39); killing...
* daemon started successfully *
fastboot devices havent
quamqom other method driver pls help
byjon09 said:
Minimal ADB and Fastboot>adb devices
List of devices attached
adb server version (31) doesn't match this client (39); killing...
* daemon started successfully *
fastboot devices havent
quamqom other method driver pls help
Click to expand...
Click to collapse
TRY update adb flatform tool
ı m 100 files download maybe just bootloader opened download mode no normal mode no recovery no
bootloader files find
Hard_k.i.k said:
TRY update adb flatform tool
Click to expand...
Click to collapse
the problem is that I stupidly turned off the bootlarder lock while downloading the android version, now fastboot devices don't see it, adb devices see it in fastboot,n I need to turn on the phone when I can't
https://queeshop.blogspot.com/2017/11/tutorial-how-to-fix-qhsusbbulk-or.html this method ?????
https://www.droidwin.com/fix-adb-server-version-doesnt-match-this-client-killing/ whichi*******???