Hello
I'm trying to run a shell session but getting this error message
adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Ok, it seems obvious what the problem is but I can't find a solution
The phone is plugged, Fastboot seems to recognise the connexion as says fastboot USB
HBOOT version 1.14
Not sure what to do
Any idea?
Many thanks
EDIT Problem Solved - should launch from Recovery - Thank you
OS is Ubuntu 12.10.
Can not get infuse recognized by 'root.sh'.
Can get into 'download mode' so know the cable and usb connections are good.
in debugging mode, lsbusb shows:
Bus 001 Device 049: ID 04e8:681c Samsung Electronics Co., Ltd Galaxy Portal/Spica/S
[email protected]:~$ adb devices
List of devices attached
I9978d24fc7a device
Below is what happens:
[email protected]:~$ ~/Down*/Inf*/root.sh
Raging Against The Cage...
error: device not found
<snip>
Resarting ADB server
Pushing Superuser utils...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
<snip>
Acquiring Network Unlock Codes...
error: device not found
-- Unlock Code:
WARNING: If the code does not work the first or second time
do not keep trying over and over!
WARNING: You can lock your phone if you do this.
Script Complete...
Please type the following at the prompt:
/usr/bin/adb reboot
[email protected]:~$
Ran as 'sudo ~/Down*/Inf*/root.sh' ... did not work either.
Tried searching 'Raging Against The Cage' in search engines plus xda with no luck.
Any help appreciated,
dlw
I don't image the adb command is able to access that sector of the device but for the record, when I connect, I can see the device but
C:\Users\Brad2\Downloads\adbUnzip2Cdrive\adb>adb kill-server
C:\Users\Brad2\Downloads\adbUnzip2Cdrive\adb>adb devices * daemon not running. starting it now on port 5037 * * daemon started successfully *
List of devices attached
51cfe754 offline
I can connect to the device with Odin in download mode, but I do not see a 'pull' or extract feature on Odin, only push.
What is the trick to extracting the boot files from the device? All drivers and sdks are installed and using the current adb.
I recently received my XT1540. I was going to wait the 14 day window I have to return the device prior to unlocking bootloader. In the mean time, are there any ADB commands I can run to gain familiarity of ADB and to ensure I have the proper Motorola drivers?
'adb devices' will let you know if the device is recognized (drivers installed, etc).
Plug in to PC, turn on USB debugging on phone, run the above command. The phone should prompt for you to accept your computer's RSA key, adb should list your device as 'device'.
There is also this: http://developer.android.com/tools/help/adb.html
use the following command to print all adb commands
adb --help
So I get the following:
Code:
C:\Desktop\adb-fastboot-latest_win_linux>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
ZY333TKQ99 unauthorized
I assume this means my drivers are installed correctly and that "unauthorized" is because bootloader is not unlocked. Is this correct?
MrTooPhone said:
So I get the following:
Code:
C:\Desktop\adb-fastboot-latest_win_linux>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
ZY333TKQ99 unauthorized
I assume this means my drivers are installed correctly and that "unauthorized" is because bootloader is not unlocked. Is this correct?
Click to expand...
Click to collapse
Probably unauthorized because you need to accept RSA key request on your phone. You should see a dialog on your phone like this.
quakeaz said:
Probably unauthorized because you need to accept RSA key request on your phone. You should see a dialog on your phone like this.
Click to expand...
Click to collapse
That was it. I did not even look at the phone.
I can not find a method to get twrp to the GT-I9506.
With Odin it does not work even it says all was programmen OK (still remains the old recovery)
and with adb it doesn't work too:
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
01b293754 sideload
adb usb
error: closed
error: closed
adb sideload recovery.img
error: protocol fault (no status)
error: protocol fault (no status)
What can I do (did try various usb cable) ?
Found the solution: You have to disable "Auto Reboot" in Odin !