[Q] SuperOneClick - Samsung Captivate 2.2 issue - Upgrading, Modifying and Unlocking

Guys, I tried to use SuperOneClick 1.7 to root my Samsung Captivate that is running 2.2 Android. This is the errors I get:
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
OK
Waiting for device...
* daemon not running. starting it now on port 5037 *
OK
Pushing psneuter...
* daemon not running. starting it now on port 5037 *
OK
chmod psneuter...
* daemon not running. starting it now on port 5037 *
OK
Running psneuter...
* daemon not running. starting it now on port 5037 *
FAILED
-------------------------------------------------------
I am running Windows XP /w sp3.
Any assistance or suggestions are greatly appreciated...Thanks

I had I believe the same error a while ago on a LG P500. I gave up and discovered that it couldn't be done because of something LG put on the ROM..

Related

[Q] Root problem evo

Im sure everyone posts about this but i used the one click auto root tool and everything ran fine up until the end when unrevoked forever or w.e its called was running. said it couldnt connect to daemon and now im stuck on white evo screen wont boot, keep trying to run the RUU but fails to run due to battery being under 30%. I was easily 75% charged before everything. Anyone else run into this problem? i just got my evo today and im feeling like i already failed at trying to root.
Note: i previously owned the htc hero, im a bit familiar with this rooting process, yet the evo is a bit tougher.
rooting issues
are you s-off or no?
Did you install the hboot drivers on your pc
Sent from my PC36100 using XDA Premium App
im stuck on step 8 my phone is showing the red triangle with the ! the DOS promt says...
waiting for the phone...
found the phone connected as 'recovery'
setting up a temporary recovery...
**daemon still not runningerror: cannot connect to daemon
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
**daemon still not runningerror: cannot connect to daemon
what do i do?
devlon305 said:
im stuck on step 8 my phone is showing the red triangle with the ! the DOS promt says...
waiting for the phone...
found the phone connected as 'recovery'
setting up a temporary recovery...
**daemon still not runningerror: cannot connect to daemon
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
**daemon still not runningerror: cannot connect to daemon
what do i do?
Click to expand...
Click to collapse
Does it say S-off or S-On?

[Q] Can not connect from ADB on my PC to Galaxy Note II?

I have a Samsung Galaxy Note II.
Model number: GT-N7100 running Android 4.1.1, kernel version:
3.0.31-310959
[email protected]$1
SMP PREEMPT Wed Oct 10 21:08:07 KST 2012
Build number . JRO03C.N7100XXALJ3
This Samsung is not ROOTED.
I put in Developer options, USB debugging=Debug mode when usb is connected = YES
Connecting the phone to my PC via a USB cable and attempting on the PC to do :
adb shell
gives:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
then doing :
adb devices
List of devices attached
There is no device connected.
Doing:
adb get-stats
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
unknown
adb version
Android Debug Bridge version 1.0.26
I need to add that the phone connects as two disks (internal disk - about 11GB plus my external microSD card - to my Windows 7 PC. I can transfer files both ways via the Windows Explorer . But I see no ADB connection when I try.
When connecting from Ubuntu, I do not see the internal disks and in addition I do not once again get an adb connection.
Under settings/developer options/debugging and allow mock locations are enabled.
select debug app is set to nothing.
Any solutions?
Finally, I found the solution thanks to mskip.
By installing the samsung drivers through the Samsung Galaxy Toolkit I am glad to get the adb and my Galaxy Note II to communicate at long last.
Cheers mskip.

[Q] Having Trouble Rooting my LG Optims E973

Hi
I am trying to root my LG Optimus G E973 (Bell is my carrier)
I followed the instructions exactly as how it is listed here
http://forum.xda-developers.com/showthread.php?t=2181103
But I got stuck when I ran the root package. And the message I keep on getting is
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Any ideas on how I can resolve this?
debugging should be enabled
should be on charge only when you plug in
when prompt put it on mtp, if that fails put it on software mode, it will work

Trouble sideloading XBMC to Fire Stick

Hello all. I'm trying to install xbmc to a fire tv stick. I have successfully done this with a fire tv. I don't know what's going on with the stick.
I can connect to the stick in the adbfire app and I can ping the stick via the command prompt.
I keep getting this error in the command prompt :
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
error : device not found
- waiting for device -
Any ideas?
Please help!
Thanks ahead of time!
deathcharge said:
Hello all. I'm trying to install xbmc to a fire tv stick. I have successfully done this with a fire tv. I don't know what's going on with the stick.
I can connect to the stick in the adbfire app and I can ping the stick via the command prompt.
I keep getting this error in the command prompt :
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
error : device not found
- waiting for device -
Any ideas?
Please help!
Thanks ahead of time!
Click to expand...
Click to collapse
Can you sideload other apps? It sounds like you don't have it configured right. Recheck your IP address.

Running ADB on MacOS with Note 10

Greetings,
I am attempting to run Tasker with AutoApps on my Note 10.
I get the following message when I run ADB from my MacBook.
adb: no devices/emulators found
I have USB Debugging enabled, and I installed Android File Transfer and also tested with Samsung Smart Switch. Both applications make successful connections with my Note 10, but I am confused as to why ADB does not detect my device. Any help is greatly appreciated.
I also ran...
/adb kill-server
./adb devices
and receive the following...
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
There is no device listed.
Any assistance would be greatly appreciated.
Did you try ./adb devices again after daemon had started?

Categories

Resources