Hello forums, I am new to xda, and to the motorola section so if I misplaced this post please forgive me. I have check all over the place trying to figure out my problem. I just got the Atrix 2 and tried running a one-click root program only to get the error "more than one device and emulator" I have read online, and from what I can understand that it may be an "adb" error, and that I need to locate the adb devices by using the command prompt (as seen here in the comments of another website cant post cause I'm a new user)
Not being very tech savvy I'm not quite sure how to control cmd, and if this is even the right thing to be looking for. If there is anyone who could walk me through this I would be infinitely grateful. Through these forums, or perhaps email, or skype. I don't want to bog down anyone, but I have been looking forward to getting and rooting this phone for quite a while now.
Thanks
piggies55 said:
Hello forums, I am new to xda, and to the motorola section so if I misplaced this post please forgive me. I have check all over the place trying to figure out my problem. I just got the Atrix 2 and tried running a one-click root program only to get the error "more than one device and emulator" I have read online, and from what I can understand that it may be an "adb" error, and that I need to locate the adb devices by using the command prompt (as seen here in the comments of another website cant post cause I'm a new user)
Not being very tech savvy I'm not quite sure how to control cmd, and if this is even the right thing to be looking for. If there is anyone who could walk me through this I would be infinitely grateful. Through these forums, or perhaps email, or skype. I don't want to bog down anyone, but I have been looking forward to getting and rooting this phone for quite a while now.
Thanks
Click to expand...
Click to collapse
Not sure about the error message, but have you made sure before you try to run the root exploit that your device (in settings/applications) you have the "Unknown Sources" and "USB Debugging" boxes checked?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my MB865 using xda premium
Yea, I made sure to enable both of those settings, since then I have tried messing around with the usb settings. When I set the phone to "charge only" get past the first phase and the phone reboots. However, upon rebooting I get the same error of having more than one device and emulator. I have also tried starting the root with Mass Storage on. Does anyone the source of this error, or some key words I could start researching?
Are you getting that error only when connected to your PC?
Have you seen these?
http://forum.xda-developers.com/showthread.php?t=1639199
http://androidforums.com/droid-all-...hell-error-more-than-one-device-emulator.html
I'm not quite sure what you mean, I dont get error when the phone is disconnected or connected via usb except when running the root program. Thank you for the article on the "bluestacks" problem. I'm not running that program, but I guess it's possible that something else on the computer could be conflicting. I checked task manager, nothing there. The other message talking about killing the adb server, how would I go about doing that? Like I said I'm not super tech savvy, so when it comes to command prompt stuff I have problems. Any suggestions?
Are you running Android 2.3.6. and which one click rooting method are you trying? You may want to download THIS ROOT EXPLOIT FILE, save to your C: drive, and plug in your device, set to "charge only". Then navigate to the C: drive, open the folder, and click the "click to root" option within the folder.
Apex_Strider said:
Are you running Android 2.3.6. and which one click rooting method are you trying? You may want to download THIS ROOT EXPLOIT FILE, save to your C: drive, and plug in your device, set to "charge only". Then navigate to the C: drive, open the folder, and click the "click to root" option within the folder.
Click to expand...
Click to collapse
I know this is a old thread. I faced the same issue and it complained this.
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb.exe shell
error: more than one device and emulator
Click to expand...
Click to collapse
Disconnecting and Reconnected did the trick.
Related
How to sideload for samsung captivate?
1. Download Terminal Emulator from android market (or any terminal).
2. Go to this post on your samsung captivate.
3. Copy this Below
su cd /dbdata/databases/com.android.providers.settings
sqlite3 settings.db
update secure set value = "1" where name = "install_non_market_apps";
.quit
reboot
4. Your phone will reboot and you can sideload. try to download an app from pandaapp.com.
5. Success!!!!!!!!!! Made very easy compared to using Android SDK.
-I dont claim to find this. But i havent seen this on youtube or any where else-
Hope You Luck!
-Jordan5555
Thanks for the info!
Sent from my GT-I9000 using XDA App
It's explained Tip: Enable Non Market App Installs on the Samsung Captivate]here[/url, I used a little variation on that method:
Can I suggest an even easier way of editing and manipulating the settings.db file? I used a combination of Root Explorer, SQLite Editor and Dropbox, modified from this link. You zip and copy settings.db from your Captivate to Dropbox, then you can edit it in Firefox, zip it, copy it back, and manipulate it from there - or I found I could copy the file to another folder I created (modified market), edit the file in there with SQLite, save the file and then copy it back to the original folder following their directions. The one thing you have to be careful of is making sure you're mounted R/W instead of R/O in Root Explorer or you'll get errors, something like 'permission denied'.
The Sideload Wonder Machine is nice, but I'm not always at my computer when I find something I want to try, this method made sideloading totally contained on the Captivate. Works a charm
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i tried the first method by copying the code and i got "Permission Denied" so then i just typed in the first line. got the same "Permission Denied"
is there a step i need to do first?
sorry if there is something obvious i should do first, i'm a bit of a noob
gisxer said:
i tried the first method by copying the code and i got "Permission Denied" so then i just typed in the first line. got the same "Permission Denied"
is there a step i need to do first?
sorry if there is something obvious i should do first, i'm a bit of a noob
Click to expand...
Click to collapse
What are you using, Root Explorer? You have to click the r/w at the top of the screen to enable writing. If it's r/o, that means read only.
Root Explorer? no, just Terminal Emulator and pasted the code into the Terminal window. i take it that's not what it meant
gisxer said:
Root Explorer? no, just Terminal Emulator and pasted the code into the Terminal window. i take it that's not what it meant
Click to expand...
Click to collapse
Ah, no, I see, you're referring to the first method. I dunno, I used what I posted, and it worked well.
nevermind lol
sorry should have mentioned that. the method posted by jordan5555 got the error
Permission denied (Jordans mthd)
Sent from my SAMSUNG-SGH-I897 using Tapatalk
While the process described here isn't technically sideloading, it is enabling installation of non-market applications without being attached to a computer, a.k.a. De-crippling . I have already simplified this process into one click, with no need for running any console commands or downloading the android SDK. Check out One Click De-Cripple for Captivate here.
BTW, your phone will need to be rooted before this process will be successful.
rafter109 said:
While the process described here isn't technically sideloading, it is enabling installation of non-market applications without being attached to a computer, a.k.a. De-crippling . I have already simplified this process into one click, with no need for running any console commands or downloading the android SDK. Check out One Click De-Cripple for Captivate here.
BTW, your phone will need to be rooted before this process will be successful.
Click to expand...
Click to collapse
Having to be rooted is why I went wit the method I posted above - because at the time I wasn't ready to root. What that method did do is force me to learn a bit about Android file structure and how to 'fiddle around' with the innards of the system. Eventually, of course, I got brave, rooted, and it's been all customizing from then on.
Of course, once you've rooted and gone to a custom ROM you never have to worry about all this again
Cant you just use the sideload wonder machine? Worked for me when I didn't have the "install_non_market_apps" file changed.
yentlequible said:
Cant you just use the sideload wonder machine? Worked for me when I didn't have the "install_non_market_apps" file changed.
Click to expand...
Click to collapse
Sure, but then I have to be at my computer to load anything. I far prefer what I did, so it's just plain done. Plus I don't want the constant reminder that AT&T has crippled my phone - a phone I'm paying way too much for monthly.
reinbeau said:
Sure, but then I have to be at my computer to load anything. I far prefer what I did, so it's just plain done. Plus I don't want the constant reminder that AT&T has crippled my phone - a phone I'm paying way too much for monthly.
Click to expand...
Click to collapse
Good point... The only reason I used the sideload wonder machine in the first place was to get root explorer on my phone since the market was not working. After that I just modified the database file.
Hi guys,
Just got my SNS and have been lurking on here trying to figure out how to ROOT it. There are plenty of guides, and I was using this one
http://forum.xda-developers.com/showthread.php?t=895545
For some reason, and at risk of sounding like an idiiot, SDK doesnt have fastboot (or I cant find it) and I cant even use Command Prompt to execute any commands such as "ADB Devices". It also wont let me change the driver to Android Bootloader Interface in Device Manager.
I basically need to start from scratch and Im tearing my hair out trying to figure it out. Sorry about the FRAT
Cheers
Bertrum said:
Hi guys,
Just got my SNS and have been lurking on here trying to figure out how to ROOT it. There are plenty of guides, and I was using this one
http://forum.xda-developers.com/showthread.php?t=895545
For some reason, and at risk of sounding like an idiiot, SDK doesnt have fastboot (or I cant find it) and I cant even use Command Prompt to execute any commands such as "ADB Devices". It also wont let me change the driver to Android Bootloader Interface in Device Manager.
I basically need to start from scratch and Im tearing my hair out trying to figure it out. Sorry about the FRAT
Cheers
Click to expand...
Click to collapse
http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
I liked this guide. First time rooting.
On command prompt, you have to go to the Android\android-sdk\tools folder then execute those fastboot command.
Your command prompt probably says C:\Users\Your User Name.. [I have Windows 7]
Type 'cd..' (without ' ') until your line says C:\>
Then type the following cd Program Files\Android\android-sdk\tools
It could be Program Files (x86) not Program Files.. depends which bit you have. You can type those fastboot command from there.
Thanks for that info. Worked a treat right upto the part where I have to put the clockwork image on. command prompt keeps saying it cannot load it. Any ideas?
Bertrum said:
Thanks for that info. Worked a treat right upto the part where I have to put the clockwork image on. command prompt keeps saying it cannot load it. Any ideas?
Click to expand...
Click to collapse
Did you download ClockWorkMod img and paste it into android-sdk\tools folder? You can do that my opening My Computer folder -> C:\ -> Program Files -> Android -> android-sdk -> tools folder.
Then open command prompt and type like that. I just did the first line for you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yours could be Program Files, not Program Files (x86) though. I downloaded 32-bit version accidentally and I didn't wanted to do it over.
After that you use your Nexus S to boot into bootloader [which the instruction says] and continue on.
thanks all sorted now. now to reinstall all my data as i didnt root straight away. ha!
Thanks for all your help.
Bertrum said:
thanks all sorted now. now to reinstall all my data as i didnt root straight away. ha!
Thanks for all your help.
Click to expand...
Click to collapse
I'm glad I helped. I had hard time rooting yesterday but it's all good now
I finished everything last night. All unlocked and rooted. Also running CM7 rc2 with the n14 kernel.
Its soo fast compared to my old blackberry and my friends galaxy.
Many thanks to the people who worked on the roms and kernels. Your knowledge astounds me.
Sent from my Nexus S using XDA Premium App
Hi!
I rooted my device and tried the UMTS Manager. The Manager does recognize the plugged in device (it shows IDs of the device). But it does not connect.
After digging around, I have done following:
- downloaded usb_modeswitch
- found out the parameters for my UMTS Stick (Nokia CS-19) and created a config file
when calling usb_modeswitch -c nokia.conf my stick changes mode and starts to show with a blinking light that the Modem is ready.
But there is no ttyUSB0 or anything with ttyUSB* in /dev/ So I guess the kernel module for USB seriall is missing.
Is there a way to include this kernel module somehow?
Edit:
ok with a Huawei Stick it works. The USB serial drivers are included. So the question is: how to make the Nokia CS-19 stick work?
I am going to assume this is what my problem was when i was experimenting last night with my 3G data stick.
Haven't had a chance to really read into it yet how to get these to work i spent maybe 5min just to see and figured id look more later. But just for the hell of it figured id plug in my huawei 1691 to see what happened and looked at a few videos showing people having the option under data modes that i dont see.
Ashcunak said:
I am going to assume this is what my problem was when i was experimenting last night with my 3G data stick.
Haven't had a chance to really read into it yet how to get these to work i spent maybe 5min just to see and figured id look more later. But just for the hell of it figured id plug in my huawei 1691 to see what happened and looked at a few videos showing people having the option under data modes that i dont see.
Click to expand...
Click to collapse
I was wrong. A Huawei E173 Stick works fine. So the drivers are not missing. Which 3G data stick do you use?
Look in the description of UMTS Manager. There is a list of working sticks.
huawei 1691 on wind mobile is my stick, looks like the umts manager fixed it and got it working, yay.
Sweet I've just got my T-Mobile dongle working as well
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
BlackICE said:
Hi!
Edit:
ok with a Huawei Stick it works. The USB serial drivers are included. So the question is: how to make the Nokia CS-19 stick work?
Click to expand...
Click to collapse
Did you do anything beside rooting the device, installing busybox and pluging in your stick to get it working with huawei?
Everything looks fine, except it doesn't connect.
Please help.
system/xbin/iproute not found
I tried a Huawei E169 with UMTS manager but I am always having this message error "System error>/system/xbin/iproute not found - install busybox " which I already did. I am rooted and the iproute dont exist.
So far I cant move forward because Im stuck here so please any help would be great thanks
dwmaihorzes said:
I tried a Huawei E169 with UMTS manager but I am always having this message error "System error>/system/xbin/iproute not found - install busybox " which I already did. I am rooted and the iproute dont exist.
So far I cant move forward because Im stuck here so please any help would be great thanks
Click to expand...
Click to collapse
When you open Busybox again, you can choose where to install. Standard installation path is /system/bin. There is a line saying "will be installed to..." and there you can choose /system/xbin.
Greetings
mr.niceguy76
mr.niceguy76 said:
When you open Busybox again, you can choose where to install. Standard installation path is /system/bin. There is a line saying "will be installed to..." and there you can choose /system/xbin.
Greetings
mr.niceguy76
Click to expand...
Click to collapse
Yep it worked thank you. The pen blue LED is always on, and I got IP but cannot achieve internet. What am I misiing ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Same thing happens
Hey,
I hope you guys are fine.
I did the exact same things as dwmaihorzes, but my pen is from Vodafone Portugal.
The blue led keeps on, but i can access Internet on my tablet.
I will ask the same question he asked:
What am I missing?
Regards,
valkirian
Can someone post a guide on how to use umts manager please?
Any developments on this one?
Thank you in advance!
sasdas said:
Can someone post a guide on how to use umts manager please?
Click to expand...
Click to collapse
why not you try PPP widget?
I've tried just about everything to get my fastboot working. I'm running on Windows 8. I've tried tool and scripts, different drivers, HTC Sync, EVERYTHING.
I've gotten ADB to work but fastboot won't recognize my phone.When I put my phone into fastboot mode, I can go into my computer and look up the phone in device manager and I do see the phone. Unfortunately, it presents an error that say the device has failed to start. This has been unchanged through out every "fix" I've tried. Any ideas?
Windows 8 is notorious for breaking fastboot. There are a few supposed ways to fix it. Exactly what have you tried? Saying you've tried "everything" doesn't actually tell us anything.
Sent from my Evita
timmaaa said:
Windows 8 is notorious for breaking fastboot. There are a few supposed ways to fix it. Exactly what have you tried? Saying you've tried "everything" doesn't actually tell us anything.
Sent from my Evita
Click to expand...
Click to collapse
Oops, sorry. I've tried the tools that are supposed to set up fastboot for you, I downloaded the SDK and got the fastboot and adb files but nothing shows up in the "fastboot devices". I've also tried the HTC Sync route as well as numerous drivers that are claimed to be the "fix".
What about some of the guides that are available that specifically address this problem?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Evita
timmaaa said:
What about some of the guides that are available that specifically address this problem?
Sent from my Evita
Click to expand...
Click to collapse
I've tried all the results on that first page. Nearly every time, I get an error message with a yellow triangle for an icon:
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Yeah I thought as much. I haven't seen people with Windows 8+ have much luck with fastboot. To be honest the only real fix I've seen is to use a different version of Windows, unfortunately that isn't as easy as some as it is for others.
Sent from my Evita
timmaaa said:
Yeah I thought as much. I haven't seen people with Windows 8+ have much luck with fastboot. To be honest the only real fix I've seen is to use a different version of Windows, unfortunately that isn't as easy as some as it is for others.
Sent from my Evita
Click to expand...
Click to collapse
Pretty much what I'd figured. Well, thanks for the help. I think I can get by with that app Flashify for now.
KungPow90 said:
Pretty much what I'd figured. Well, thanks for the help. I think I can get by with that app Flashify for now.
Click to expand...
Click to collapse
Download latest HTC driver , go into your device manager in win 8 and in device mgr menu options on top make sure and click show hidden (not connected ) devices. You then will have to click onto the greyed out HTC or android name in device mgr tree and update manually . you have to actually go to the sub folder in the driver update and not just click the folder that its in. Lol its a pain but it does work. You can Google manually install HTC driver for win 8 and there is couple tutorials. Hope it helps. I beta tested win 8
And had to do that. Lol im back to win 7 and Ubuntu now
Senseless Power Unlocked
I've been trying to root for ages, but no matter what I do I can't get ADB to recognize my device. I've tried reinstalling the drivers from I don't know how many sources as well as adb/fastboot several times, but I always get the same result:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the device manager I get a yellow flag on the ADB interface:
I honestly don't think there's any way I can do it unless I get some help from you guys. So please? How do I get my computer to recognize my OPO once and for all?
I'm following this guide FYI (must be the fifth I try): http://android.stackexchange.com/questions/106856/how-to-root-oneplus-one
Thanks to the kind souls willing to give a hand.
Seleuco said:
I've been trying to root for ages, but no matter what I do I can't get ADB to recognize my device. I've tried reinstalling the drivers from I don't know how many sources as well as adb/fastboot several times, but I always get the same result:
?
In the device manager I get a yellow flag on the ADB interface:
In the device manager I get a yellow flag on the ADB interface:
?
I honestly don't think there's any way I can do it unless I get some help from you guys. So please? How do I get my computer to recognize my OPO once and for all?
I'm following this guide FYI (must be the fifth I try): http://android.stackexchange.com/questions/106856/how-to-root-oneplus-one
Thanks to the kind souls willing to give a hand.
Click to expand...
Click to collapse
Honestly you don't need adb portion working to do this. Have you tried seeing if your computer recognizes your opo in fastboot mode?
Turn your phone off hold volume up and power button it will boot into fastboot. Then plug your phone into your computer let it install drivers then open command prompt where your fastboot file is and type fastboot devices if it shows something your good to go follow the rest of the guide unlock bootloader and install a custom recovery and SuperSU to root.
Also if its me I would install twrp recovery.
you sure you got the right drivers?
@Seleuco try this tutorial and also check Y for install adb drivers
http://forum.xda-developers.com/showthread.php?p=48915118
the easiest method for having adb everywhere
You need to install divers first, look at your screenshot, you have no driver installed for adb device.
giaur said:
You need to install divers first, look at your screenshot, you have no driver installed for adb device.
Click to expand...
Click to collapse
Honestly I don't even know at this point, I tried deleting and installing them a dozen times from different sources, but it doesn't recognize them. Do you know any idiot-proow way of installing the drivers?
wulsic said:
@Seleuco try this tutorial and also check Y for install adb drivers
http://forum.xda-developers.com/showthread.php?p=48915118
the easiest method for having adb everywhere
Click to expand...
Click to collapse
Thanks, but I actually took the screenshots right after running that program
Seleuco said:
Thanks, but I actually took the screenshots right after running that program
Click to expand...
Click to collapse
Did you also tried to install the driver manually in device manager?
See this link how you can do that:
http://www.technobuzz.net/install-nexus-5-driver-adb-fastboot-unlock-bootloader/
If these drivers don't work and or can't install then just extract Snoop05's adb installer and use those drivers :good: hope this would work now,
the issue is probably that there are so many drivers installed that they are conflicting with each other and windows is just deciding which one is better, so manually overriding it should fix it and else I guess you have to remove the old adb drivers with an program but first try these easy methods