[Q] Problems Rooting My Photon (more than one device error) - Motorola Photon 4G
I've read lots of the posts here about rooting and I've closely followed the directions, but I'm still having a problem. Also, apologies if I'm posting in the wrong section, but I don't have enough posts for the Dev section, which seems the better destination.
Anyway...I tried both the manual process via ADB and also the one-click method.
In both cases, the problem seems to be that there are two devices running, my Photon (TAxxxxxxBJC) and an emulator (emulator-5554). With the ADB method it appears that I should be able to stop the emulator device via the ADB command, but then the next time I use ADB (for example, to get a list of devices) a Daemon kicks in and restarts the emulator.
I'm pretty sure if I can disable the emulator and keep it disabled that I could root my phone. But even when I stop the emulator and then do the one-click method, the first command restarts the Daemon and the emulator.
Can anyone help me with how to defeat the emulator and keep it from loading during the rooting process? I'm including a screen grab of the feedback from the one-click method to illustrate my issue.
Thanks for any ideas or suggestions...
____________________________________________________
* daemon not running. starting it now *
* daemon started successfully *
Getting temp root
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
RE-boot-en
error: more than one device and emulator
error: more than one device and emulator
Hackin Things
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
deleting all yo
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
Copying files onto phone...
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
Setting permissions...
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
Installing busybox...
error: more than one device and emulator
Cleaning up files...
error: more than one device and emulator
error: more than one device and emulator
"You should have root!"
Press any key to continue . . .
____________________________________________________
Do you have something like blue stacks cloud connect running?
Sent from my MB855 using xda premium
Yes, I did have Blue Stacks running. So, I killed it via Task Manager and then tried to root again. But when I run ADB I'm still seeing both my device and the emulator.
I was previously experimenting with Android Screen Cast, so I checked to see if I could find anything related to that in the running processes but didn't see anything obvious. I'll take a deeper look after sending this note, but any other suggestions that might be causing the eMulator to load?
Thanks for the suggestion and quick reply.
I figured out that I needed to kill the service for Blue Stacks rather than the process. When I did that and then checked the connected devices via ADB it only showed my phone.
Now rooted. One weird thing is that now AndroidScreenCast will not load and I get an "Unable to Load Application" message. Before, I could view my phone screen on my desktop but not interact with it (that required rooting). So, sort of one step forward, one step back.
Thanks very much for the great help.
Have you checked to see if the bluestacks service is running again? (I honestly have no idea what the problem would be; I'm just shooting in the dark.)
Sent from my MB855 using xda premium
In fact, I started Blue Stacks again, because it had been running when Android Screen Cast was working earlier (albeit only in one direction).
So, I just went back and stopped the Blue Stacks service again, and then retried ASC without luck. FWIW, ASC seems to fail during the process of "Getting devices list."
But thanks again for the additional suggestion. You were right on the money with the cause of my not getting rooted, so I'm grateful for that.
Thanks again.
Then don't forget to hit the thanks button please.
Sent from my MB855 using xda premium
Were you able to get rooted?
Yes, or at least I'm pretty sure.
Root Check reports that I'm rooted, but Screenshot produces an error message whenever I try to to take a screenshot and it asks whether I'm rooted. I've also managed to get Android Screen Cast to run again, but it's view-only rather than being able to interact with my phone via my PC screen (rooting required for interactivity)..
On the other hand, Ad Free and My Backup Root seem to be working fine.
Related
HELP!
okay i've read the guide.. HOW TO ADB FOR DUMMIES i am stuck at one point When the new hardware device notification pops-up on your pc point windows to the driver folder we moved to our C-drive(C:\android_adb_usb_driver) and install the adb driver. that was the point where i am stuck.. help! seem like i can't semm to install the adb driver ONE MORE THING when i cmd and cd to C:\adb\tools>adb remount replies error: device not found can anyone help? when i do the same thing C:\adb\tools>adb shell replies error: device not found HELP!!!~
[Solved] n00b needs help with adb and Ubuntu
Hi all,
I searched quite a lot, but seems to me not nearly enough. I've been using adb on my Windows 7 machine for a while now, but would like to have adb at work on my Ubuntu 11.04 machine where I am going to start some boring development.
I have installed the sdk and eclipse and and and (if it is important WHAT I installed more than this, I will elaborate)
lsusb returns
Code:
Bus 002 Device 009: ID 04e8:689e Samsung Electronics Co., Ltd
so I have set my
/etc/udev/rules.d/51-android.rules
to reflect like this:
Code:
SUBSYSTEM=="usb",ATTRS{idVendor}=="04e8",ATTRS{idProduct}=="689e",SYMLINK+="android_adb",MODE="0666
I'm kinda hoping this is wrong and there is an easy fix that I can laugh about.
When I have the emulator running and my phone plugged in
Code:
$sudo adb devices
returns a blank line and something about an emulator, only emulator running yields no blank line and only phone plugged in yields a nice and quiet blank line.
I had this on Windows as well when I struggled with drivers, but the CD sorted it out. I read that the necessary drivers comes with the SDK, but I might be wrong.
I have tried different tutorials and different values for the idProduct and idVendor as some tutorials claim they should be kept constant and not vary per phone... I restarted adb each time I made a change with
Code:
$sudo adb kill-server; sudo adb start-server; sudo adb devices
I'm currently running FirstUA v1.2 if that changes anything.
If you need more info, don't hesitate to ask, I know it's easier to solve problems with the right info (coming from an IT helpdesk).
Digi.Gram said:
Hi all,
I searched quite a lot, but seems to me not nearly enough. I've been using adb on my Windows 7 machine for a while now, but would like to have adb at work on my Ubuntu 11.04 machine where I am going to start some boring development.
I have installed the sdk and eclipse and and and (if it is important WHAT I installed more than this, I will elaborate)
lsusb returns
Code:
Bus 002 Device 009: ID 04e8:689e Samsung Electronics Co., Ltd
so I have set my
/etc/udev/rules.d/51-android.rules
to reflect like this:
Code:
SUBSYSTEM=="usb",ATTRS{idVendor}=="04e8",ATTRS{idProduct}=="689e",SYMLINK+="android_adb",MODE="0666
I'm kinda hoping this is wrong and there is an easy fix that I can laugh about.
When I have the emulator running and my phone plugged in
Code:
$sudo adb devices
returns a blank line and something about an emulator, only emulator running yields no blank line and only phone plugged in yields a nice and quiet blank line.
I had this on Windows as well when I struggled with drivers, but the CD sorted it out. I read that the necessary drivers comes with the SDK, but I might be wrong.
I have tried different tutorials and different values for the idProduct and idVendor as some tutorials claim they should be kept constant and not vary per phone... I restarted adb each time I made a change with
Code:
$sudo adb kill-server; sudo adb start-server; sudo adb devices
I'm currently running FirstUA v1.2 if that changes anything.
If you need more info, don't hesitate to ask, I know it's easier to solve problems with the right info (coming from an IT helpdesk).
Click to expand...
Click to collapse
The SDK Drivers are not for Galaxy Ace , Google for the drivers , they should be easy to find
Sent from my Ultma Weapon using XDA App
It seems that my problem begins with our Proxy server.... As the SDK manager and I had a quarrel about authentication, I downloaded some of the packages directly and forced the manger to use them instead of those on Google. With this, I accidentally downloaded an outdated adb, which had problems specifically with the Galaxy line of phones.... Downloading the correct package now, will see if it works better
Maybe I must just stop before I think of continuing I installed the newer r06 version, and my device is picked up, but now adb shell gives me this: Code: :~$ adb devices List of devices attached S58300c017faf device :~$ adb shell sh: applet not found Any ideas where to look for the applet? Maybe I must continue tomorrow, new day new ideas.
Do you have Debugging turned on? And is the device rooted with Busybox? I assume yes since you're running a custom ROM but double checking. If you're having trouble, I'd either: a) run a VM with XP SP3; b) head to the Android Q&A board here.
mmm, I never though of looking at that, since I figured they do say busybox is installed on this ROM, but thanx for nudging me into that direction, I found this post from ketut.kumajaya so I'm looking into that. Had some issues with not abling to get rw access, but my only problem there was a spelling error in the terminal. I still get the error with the sh: applet not found, even after I tried the advice on that link. I tried installing all 3 versions shipped with BusyBox Installer on all 3 locations, still nothing. Just had an idea I'll try, if you invoke sh in linux you get a new shell, when I invoke sh I get the applet not found error. Maybe I should upgrade my sh or something. Worth a try I am running a VM for the VB programming I do at work, but that doesn't have USB support (to much trouble to reinstall Virtual Box now just for USB support). Last night I tested on Windows 7 (first time since I started using this ROM) and it failed with the same error. I'm sure it's the sh that's broken or something. Will test on my wife's phone tonight (running the same ROM). Thanx for your ideas so far. That's what I love about an online community, even if you don't exactly know what's wrong, people sling ideas around that nudge you in the right direction. One error message at a time
Solved thanx to Ketut Thanx for all your help guys.
[Q] Linux distro binaries within Android?
I just extracted the Gentoo Stage3 package for ARM7A and I am playing around trying to get the binaries to run either through terminal emulator or adb shell on my Galaxy Tab running Gingerbread. I am FULLY aware of how PATH works and all of the normal reasons you would get a "not found" error when trying to run a command, but this one has me stumped. I tried setting my path to include a subdirectory of /system/bin as follows: PATH=/system/bin/gentoo:$PATH and gentoo is where I put my gentoo binaries. When I do which (command) it says: /system/bin/gentoo/(command) When I try to run it, it runs the same command from one of the other directories such as /system/xbin (from busybox) instead. I tried renaming one of the binaries so it has a unique name mv ps wtf I can still do which wtf and get /system/bin/gentoo/wtf THEN when I try to run it I get wtf: not found. Obviously the file is there. Even if I go directly to /system/bin/gentoo and do ./wtf I get wtf: not found. If I copy one of the Android system binaries to /system/bin/gentoo/wtf it will run just fine. Why would I get a not found error for a binary that is obviously there?? I would expect a different error if it wasn't an acceptable binary, so I am lost. Any ideas?
rustyshack3 said: I just extracted the Gentoo Stage3 package for ARM7A and I am playing around trying to get the binaries to run either through terminal emulator or adb shell on my Galaxy Tab running Gingerbread. I am FULLY aware of how PATH works and all of the normal reasons you would get a "not found" error when trying to run a command, but this one has me stumped. I tried setting my path to include a subdirectory of /system/bin as follows: PATH=/system/bin/gentoo:$PATH and gentoo is where I put my gentoo binaries. When I do which (command) it says: /system/bin/gentoo/(command) When I try to run it, it runs the same command from one of the other directories such as /system/xbin (from busybox) instead. I tried renaming one of the binaries so it has a unique name mv ps wtf I can still do which wtf and get /system/bin/gentoo/wtf THEN when I try to run it I get wtf: not found. Obviously the file is there. Even if I go directly to /system/bin/gentoo and do ./wtf I get wtf: not found. If I copy one of the Android system binaries to /system/bin/gentoo/wtf it will run just fine. Why would I get a not found error for a binary that is obviously there?? I would expect a different error if it wasn't an acceptable binary, so I am lost. Any ideas? Click to expand... Click to collapse Just a guess, but I'd bet that the linker path for the binary is having trouble finding a library.
emulator
ok so im trying to emulate my phone onto my PC windows 7... heres the line im putting in... emulator -avd MyDevicesName and here the error im getting emulator: ERROR: unknown virtual device name: 'MyDeviceName emulator: could not find virtual device named 'MyDevicesName'
droidgenius said: ok so im trying to emulate my phone onto my PC windows 7... heres the line im putting in... emulator -avd MyDevicesName and here the error im getting emulator: ERROR: unknown virtual device name: 'MyDeviceName emulator: could not find virtual device named 'MyDevicesName' Click to expand... Click to collapse Try asking.this in the general q&a I think you'll have better luck there
There is an emulator built into the SDK and Eclipse.
ADB install not working
Hello, I own a phone(Model Number ZTE BLADE L5 PLUS) with Android 5.1 lollipop. I am trying to push install a normal apk file which doesn't need any special access. Also, my phone has way more storage space than the size of the apk. When I am trying to install the apk, it looks like it works at first with the message "1 file pushed" with the speed of pushing the apk. The real problem happens after a split second. It suddenly says "Error: Unknown command 'install'" and a huge list of commands which all starts with "pm" comes out. I have tried multiple times, from rebooting adb and typing in the path of the apk instead of inserting the name, but it all failed, with exactly the same issue every time. I also searched about the "adb install" command missing, but ended up wasting time only(only solutions for "adb" command not found came out) I installed adb via Android Studio(Android SDK Platform-Tools), along with the platform suitable for Android 5.1. I didn't download the android emulator though. I hope I could get some help. Thank You