[Q] adb help. Can't find device - HTC EVO 3D

Howdy.
I've done the HTC unlock and am trying to flash recovery.img via adb. I've downloaded sync, sdk, and java. Set path for sdk, java...etc.
When I go to fastboot and try....adb push recovery.img /sdcard/ it says
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
What am I missing?

nineandtwo3rds said:
Howdy.
I've done the HTC unlock and am trying to flash recovery.img via adb. I've downloaded sync, sdk, and java. Set path for sdk, java...etc.
When I go to fastboot and try....adb push recovery.img /sdcard/ it says
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
What am I missing?
Click to expand...
Click to collapse
Make sure its charge only and using a good cable and a good USB port then open CMD in platform tools folder and type adb devices...it should start the daemon and list the device try that and see if it find it
Sent from my PG86100 using xda premium

Related

Shell Root / JIT problem

Hi
I just get my X10 and i wanted to root it and install JIT. I read somewhere in this forum that the easiest way to root is z4root or superoneclick. I used z4root and i rooted it, everything was cool. Next i was looking for a tutorial how to install JIT and make phone faster. It was hard to find but finaly after 2 hours i found something called Android 2.1 OPTIMISER V2. I downloaded it and i did follow this steps :
Code:
To do it you need to have a rooted 2.1 X10
Step One
-Have PC companion open
-Download and extract the file
-Then open the SuperClick folder and run SuperClick as admin
-Then click on shell root
-The steps are the same as the previous root procedure
-Connect your phone then click on charge, then click on usb debugging
-If it doesn't work then unplug, un tick, then plug and tick usb debugging again
Step Two
-Once you have shell root open the 2_jit_enabler.bat file
-Press any key
-You should see some lines of code and when finish your phone will turn off
-Then unplug your phone then start it up
-The initial boot will take a while so wait
-After boot your phone will come back to normal
Step Three
-Now run SuperClick as admin again
-Run the root procedure, click on root...........you should know the rest by now
Now you have JIT and Root.
But... there is something like "shell root" and i have problem with that step.
I can't even pass step one because my phone can't shell root or i'm doing something wrong.
I ran Pc Companion on my pc and i clicked shell root in superoneclick 1.5.4 then at the " waiting for device " i connected the cable and selected "charge" after that i selected debug mode and this is what i got in log :
Code:
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
14 KB/s (5392 bytes in 0.372s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
It didn't loop forever it just disconnects and connects - i hear sounds of it and it keep asking which mode i want to connect. After that last "waiting for device" it's stuck.
The battery indicator in phone keep showing charging icon even there is no cable conected and program stops responding. I have to reset x10 to get it back to normal.
Same thing happens when i push Unroot button. Only "Root" seems to work because it didn't loop and after 1 min i had the info that my phone is already rooted.
So my question is : is it my fault or program ? what do i have to do to make it work.
Oh and i don't want to flash another rom with jit and root.
Hello Epil0g,
So if you already have Root access via Z4root follow this post i made in other Thread to install Xrecovery:
http://forum.xda-developers.com/showpost.php?p=10197944&postcount=2
ONce you have Xrecovery installed in your phone (You can check if you have by pressing the "back" key several times right after the "sony Ericsson" white logo appears when you reboot your phone.
2.- Download the Jit V2.zip from this Thread and save it to any folder on your SD Card
http://forum.xda-developers.com/showthread.php?t=885977
3.- Go into Recovery Mode (Pressing Back right after SE Logo)
4.- Choose install custom zip from SD Card
5.- Browse to the folder were you saved the file and select it.
6.- if it asks for confirmation select yes.
7.- Wait untill the process finishes and then select - Reboot phone
8.- Enjoy.
Jim
Hi Jim and thanks for your reply.
I followed your steps and everything works nice. I have 756 in Quadrant I think it's not bad result. But I'm also thinking about those useless applications like timescape facerecognition etc. etc. While this .bat file from optimizer won't work without shell root is there any other way to delete these apps ? I dont want to delete them one by one I'm looking for something automatic like this optimizer.
Thanks
Titanium backup can remove them
Sent from my X10i using XDA App
Epil0g said:
Hi Jim and thanks for your reply.
I followed your steps and everything works nice. I have 756 in Quadrant I think it's not bad result. But I'm also thinking about those useless applications like timescape facerecognition etc. etc. While this .bat file from optimizer won't work without shell root is there any other way to delete these apps ? I dont want to delete them one by one I'm looking for something automatic like this optimizer.
Thanks
Click to expand...
Click to collapse
Hey Bro i just updated my .rar file and now it contains 1 script to delete and backup all those Junk Apks...
1.- Download this file and unrar it on your SD (Again if it ask to overwrite select yes)
2.- Go to Gscript Lite and load the script called "Clean Junk!"
3.- Run it
4.- Reboot and you´ll be set.
5.- Give me some feedback.
PS all the Apps are backed up on /sdcard/Android - if you want to delete them you can find it there.
If this was helpfull you can use the Thanks button
Jim
Unfortunately gscript don't see any of the scripts. Only xrecovery.sh and xrecovery-reinstall.sh. I tried to copy few times but with same effect.
Epil0g said:
Unfortunately gscript don't see any of the scripts. Only xrecovery.sh and xrecovery-reinstall.sh. I tried to copy few times but with same effect.
Click to expand...
Click to collapse
Sorry my bad... I didn't post the Link lol ...
http://dl.dropbox.com/u/15148882/gscript.rar
Here you go... Just update your gscript folder on your SD Card.
If this was helpful... Use the thanks button lol..
Jim
Yup. It works, thanks
Has this method been updated for use on x10a yet? I folled along while trying it but couldnt get it to go into recovery mode. It just hung at the white ericsson screen. I re-read the posts here and noticed it was for the 2.0.A.0.504 edition.
Sent from my X10a using XDA App
cobaltleo said:
Has this method been updated for use on x10a yet? I folled along while trying it but couldnt get it to go into recovery mode. It just hung at the white ericsson screen. I re-read the posts here and noticed it was for the 2.0.A.0.504 edition.
Sent from my X10a using XDA App
Click to expand...
Click to collapse
It should work if you have Root Access... But check my other thread on this section.. The link is under my signature..
Jim
Sent from my X10 running Froyo...

Automatic version check failed. Is your OS version 2.0 or higher?

I get that message every time I try to root my LG Optimus S. I select yes (it is running 2.2), but still can't root.
I have my phone set to have USB debugging mode set on and rebooted the phone as well as redownloading SuperOneClick to hopefully remove any configuration files, but I still get the following error when trying to root:
SuperOneClick v1.9.1.0
Checking drivers...
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Getting OS Version...
Pushing psneuter...
602 KB/s (585731 bytes in 0.949s)
OK
chmod psneuter...
error: closed
FAILED
Click to expand...
Click to collapse
I tried running adb manually after killing the adb.exe process and get:
C:\SOC\ADB>adb root
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adbd is already running as root
C:\SOC\ADB>adb shell
error: closed
Click to expand...
Click to collapse
Use z4root. Works for O1 having 2.2.
z4root works like a charm. try it!

[Q] [q] this adb not working is driving me insane!!! H=e=l=p!!!

this has been a problem after problem situation the whole way through trying to knock my HTC one out of this softbrick state it is currently trapped in.
long story short. currently at point where trying to sideload rom to phone... past flashing twrp.img... and if its not one error its the next.
1) adb will refuse to start.. it will just stick on:
C:\adb>adb start-server
* daemon not running. starting it now on port 5037
2) C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
3) last error type, everything will be running smoothly then as after the 'adb sideload ROM.zip' or should it be this,'adb sideload Desktop/ROM.zip' dont know but it shoots back "error: closed"
FIX THIS PLEASEEEEEEEEEEEE!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Linux Mint ADB sees my phone as 'offline' & how to 'untrust' computer

After connecting the phone via usb cable, "adb devices" command lists :
$ adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
FA3BSWG00401 offline
1) First time it asked whether to trust this computer and I checked 'always trust this computer'. Is there a way to untrust a specific computer / make it ask again ?
2) plugging the cable to my older SGS3 works fine :
$ adb devices
List of devices attached
4df1d4650790afdf device
Has anybody encountered this before ?
Additional info :
$ adb version
Android Debug Bridge version 1.0.32
Revision 57224c5cff69-android
I'm using Linux Mint 17.2, NuSense 6 (Lolipop)

HTC M8 Not loading fastboot mode or anything freeze and not responce

It not loading nothing stock just can be restarted by (Up volume + Power button) But is shows same think. :eek
Try adb, cmd, everything, anything. I got all drivers the PC see the phone and before this happens.
Whit cmd : adb Devices it show me
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FA89HWM66658 online
BUT NOW is shows me
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FA89HWM66658 offline
And i cant do nothing just power on and power off... charge up and wait till battery gets completely down. :good:

Categories

Resources