I have been trying to root my MZ604 xoom using this thread http://forum.xda-developers.com/showthread.php?t=1010568. I've unlocked just fine but having trouble with the adb shell command. I enter adb shell then return I get # then I enter the next command which is mkdir /data/media/sdcard2 and it can't find it what am I missing?
Related
So i'm trying to root my asus transformer by following this guide http://forum.xda-developers.com/showthread.php?t=1106587
i got to the part where it says to type the following command
Code:
adb push gingerbreakBB /data/local/
but i get the error
Code:
C:\Android>adb push gingerbreakBB /data/local/
error: more than one device and emulator
I ran adb devices to see what devices it recognises and it says
Code:
C:\Android>adb devices
List of devices attached
304D197CC264A27E device
28841c943012497 device
what now
unplug one of your devices (maybe your phone?) or use
Code:
adb -s 304D197CC264A27E push gingerbreakBB /data/local/
you might have to swap the serial number, depending what you have plugged in.
thanks mate it seemed like it rooted but it didnt lol. i got the progress bar on when i rebooted the device but it doesnt seem to be rooted hhmmmm any ideas?
Sorry, not sure... maybe your phone is rooted instead :0
Try starting over again without your phone plugged in
if you are on linux or have access to a linux machien use this http://forum.xda-developers.com/showthread.php?t=1198303
Otherwise do this http://forum.xda-developers.com/showthread.php?t=1125714
gee one said:
Sorry, not sure... maybe your phone is rooted instead :0
Try starting over again without your phone plugged in
Click to expand...
Click to collapse
LOLOLOL you were right my phone was plugged in HOWEVER it still didnt work. the progress bar did show up again but wasnt rooted
mrevankyle said:
if you are on linux or have access to a linux machien use this http://forum.xda-developers.com/showthread.php?t=1198303
Otherwise do this http://forum.xda-developers.com/showthread.php?t=1125714
Click to expand...
Click to collapse
thanks i'll try that out later today. i think its sign for my to go to sleep its 3 am right now lolol. i'll post what happens today morning
Oh yeh going to sleep did the trick. I woke up and removed everything by doing the commands
Code:
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
and also followed the this video tutorial
http://www.youtube.com/watch?v=WaZ4B60OWmY&feature=player_embedded
aand it worked it!
Thanks gee one and mrevankyle
kassim3 said:
Oh yeh going to sleep did the trick. I woke up and removed everything by doing the commands
Code:
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
and also followed the this video tutorial
http://www.youtube.com/watch?v=WaZ4B60OWmY&feature=player_embedded
aand it worked it!
Thanks gee one and mrevankyle
Click to expand...
Click to collapse
also would like to add to anyone else encountering this error with other uses of adb to make sure all of bluestacks processes are killed.
I had the same issue when I've tried to room my XT1032 (Moto G)... I fail to install with the SuperBoot way! So I've decide to install CWM and a modified recovery.
On my first try, I receive this message:
Code:
error: more than one device and emulator
When I used the command
Code:
adb devices
I've 2 device... My XT1033 and an AndroidEmulator...
C:\Fastboot>adb devices
List of devices attached
emulator-5554 offline
TA88305ZDH offline
Click to expand...
Click to collapse
Also, the command
Code:
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
is not working for me...
I've use the command:
Code:
adb kill-server
After, I've plug back my XT1033 via USB and launch the command:
Code:
adb usb
Only my XT1033 is now show when I use the
Code:
adb devices
!
So, I've finish my installation with
Code:
fastboot-moto-windows flash recovery recovery.testkeys.img
and I've run a sideload installation with:
Code:
adb-windows sideload supersu.motog.zip
Try this and share me your opinion!
---------- Post added at 11:11 PM ---------- Previous post was at 11:10 PM ----------
I had the same issue when I've tried to room my XT1032 (Moto G)... I fail to install with the SuperBoot way! So I've decide to install CWM and a modified recovery.
On my first try, I receive this message:
Code:
error: more than one device and emulator
When I used the command
Code:
adb devices
I've 2 device... My XT1033 and an AndroidEmulator...
C:\Fastboot>adb devices
List of devices attached
emulator-5554 offline
TA88305ZDH offline
Click to expand...
Click to collapse
Also, the command
Code:
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
is not working for me...
I've use the command:
Code:
adb kill-server
After, I've plug back my XT1033 via USB and launch the command:
Code:
adb usb
Only my XT1033 is now show when I use the
Code:
adb devices
!
So, I've finish my installation with
Code:
fastboot-moto-windows flash recovery recovery.testkeys.img
and I've run a sideload installation with:
Code:
adb-windows sideload supersu.motog.zip
Try this and share me your opinion!
**THIS IS FOR US 3G XOOM ONLY**
**DO NOT USE THIS ON WIFI MODEL**
This guide in no way implies or expresses any warranties.
What you choose to do with your equipment is your sole responsibilty.
__________________________________________________ ______________________________________
SUMMARY
You must already be running Honeycomb 3.2 on your Xoom
You will be unlocking your Xoom, if you have not already. This will wipe data so make sure to back everything up that you would like to keep.
You will be unlocking your Xoom, if you have not already. This will wipe data so make sure to back everything up that you would like to keep.
You will be performing steps in ADB. If you are not familiar with this, read HERE first.
You will need Xoom USB drivers and Fastboot
You will need the boot (kernel) partition with rooted stock 3.2 kernel (thanks & credit to, solarnz and p3droid) [see Attachment]
You will need Superuser.apk and su binary to enable functioning root [see Attachment]
**Before you get started, make sure the USB Debugging option is enabled in the Settings. Go to Settings --> Applications --> Development -->USB Debugging**
PROCEDURE
Download and unzip files. Place kernel.img, superuser.apk & su binary in the same place you will open your command window.
Open command window:
Type; adb devices - you should see a long serial number on the screen. If no serial number appears, recheck your adb, sdk & moto usb driver files.
Type; adb reboot bootloader
Type; fastboot oem unlock - and follow the steps on your xoom's screen (You have to accept the terms by pressing the volume down key, and then select 'accept' by pressing the volume up key.)
Allow the xoom to boot up completely and go back into settings and enable USB debugging again.
In the command window on your PC type; adb reboot bootloader - (if xoom does not respond, disconnect from pc and reboot manually by holding vol up + power. then reconnect after fully rebooted)
Type; fastboot flash boot kernel.img
Type; fastboot reboot
Allow the xoom to boot completely - your xoom should be in normal operating mode for the remainder of the process.
In the command window on your PC type; adb remount
Type; adb push su /system/bin
Type; adb shell ln –s /system/bin/su /system/xbin/su
Type; adb shell chmod 4755 /system/bin/su
Type; adb push Superuser.apk /system/app
Thats it...your done!! Unplug the xoom and reboot. Your xoom is now stock rooted.
You can now flash ClockworkMod, other kernels and roms. To verify root, download a root user app from the market and run it.
You should be prompted to allow superuser permissions.
Mac Only Procedure
You will need fastboot for mac
Open a terminal (located in the utilities folder)
Navigate to your sdk/platform-tools folder
Type; ./adb devices - (look for the xoom serial number to show its connected.)
Type; ./adb reboot bootloader
Type; chmod 755 fastboot
Type; ./fastboot oem unlock
Type; adb reboot bootloader
Type; ./fastboot flash boot kernel.img
Type; ./fastboot reboot
Type; ./adb remount
Type; ./adb push su /system/bin
Type; ./adb shell ln –s /system/bin/su /system/xbin/su
Type; adb shell chmod 4755 /system/bin/su
Type; ./adb push Superuser.apk /system/app
Disconnect and reboot xoom. Download a root app and test.
If you found this helpfull press the THANKS button.
thanks & credit to, solarnz and p3droid for the kernel & jase33 for the form and style of this TUT!
PS: to the mods --> please move this thread to the Dev part, currently it's not possible for me to post in there...
can't get this to work
I've followed the instructions to the letter a half dozen times now and when I get to
adb shell ln –s /system/bin/su /system/xbin/su
The reply is that the folder can't be found. Any advice? thanks much!
I know a lot of people have been looking for a guide like this.
dslcpm said:
I've followed the instructions to the letter a half dozen times now and when I get to
adb shell ln –s /system/bin/su /system/xbin/su
The reply is that the folder can't be found. Any advice? thanks much!
Click to expand...
Click to collapse
I just went on past that step and it appears to have still taken the root.
Hi!
Have you had the su binary in the same direstory
From which youve executed the following cmd:
Type; adb push su /system/bin
Because then everything should be fine!
Bye
Thanks a lot
Move ---> xoom android development
Hi mods,
please move this article to Xoom Android Development.
Thanks
Worked perfect
Sent from my HTC Sensation Z710e using XDA Premium App
hello,
I am trying to set up a simple batch/ script to "automate" the root process.
I am using the mempodroid exploit to gain root access. The problem is this:
I am using this in my script,
adb shell /data/local/mempodroid 0xd9f0 0xaf47 sh
when I use this I get a return of [email protected]:/ # and the cmd window locks up and I can not enter anything.
however if I manually enter this,
adb shell
I get back [email protected]:/ $
and then I enter,
/data/local/mempodroid 0xd9f0 0xaf47 sh
I get back [email protected]:/ #
and that is what I want.
I don't know how to automate it in a working way. Any thoughts?
finished this up and have a working simpleRoot! check it out at acertabletforums.com
and now i have compiled ClockWorkMod for A200 as well! check it out at the same spot!
Hi there! I followed the instructions here:
Code:
Download and unzip files. Place rootboot.img, superuser.apk & su binary in the same place you will open your command window.
Open command window:
Type; adb devices - you should see a long serial number on the screen. If no serial number appears, recheck your adb, sdk & moto usb driver files.
Type; adb reboot bootloader
Type; fastboot oem unlock - and follow the steps on your xoom’s screen (You have to accept the terms by pressing the volume down key, and then select ‘accept’ by pressing the volume up key.)
Allow the xoom to boot up completely and go back into settings and enable USB debugging again.
In the command window on your PC type; adb reboot bootloader - (if xoom does not respond, disconnect from pc and reboot manually by holding vol up + power. then reconnect after fully rebooted)
Type; fastboot flash boot rootboot.img (for WiFi)
OR Type; fastboot flash boot 3Grootboot.img (for 3G Verizon)
Type; fastboot reboot
Allow the xoom to boot completely – your xoom should be in normal operating mode for the remainder of the process.
In the command window on your PC type; adb remount
Type; adb push su /system/bin
Type; adb shell
Type; ln -s /system/bin/su /system/xbin/su (this line starts with lower case “L”, like llama)
Type; chmod 4755 /system/bin/su
Type; exit
Type; adb push Superuser.apk /system/app
to root my xoom. I have an UK xoom 3.2. And everything was going great.
After the first reboot (fastboot flash boot rootboot.img )
When the xoom booted, it was fine, I've logged into my gmail account using my wifi hotspot.
But then ...
after executing this steps and rebooting:
In the command window on your PC type; adb remount
adb push su /system/bin
adb shell
ln -s /system/bin/su /system/xbin/su (this line starts with lower case “L”, like llama)
chmod 4755 /system/bin/su
exit
adb push Superuser.apk /system/app
Now I don't have wifi anymore. The wifi only shows an error.
How can I fix this? I've did a basic search but most related to ppl using version 3.2.1, since I'm using 3.2 I did not believe it would apply to myself.
Any ideas?
Thanks
No idea how to fix that one.
However I can suggest using a one click rooting method in the future - i think i used a tool called xoot the 1st time to root before jumping to ICS.
The above process you mentioned was one of the things that put me off rooting at the start of ownership.
Hopefully someone will be a long soon to help with your problem
What are the specifics of the error you're getting with wifi?
Is the error when you try to turn wifi on?
Did you allow restoring apps/settings when you booted after the rooting process?
Hi lads,
thanks for the support, I've solved by restoring the stock image (3.0) and then using the universal root procedure.
Regards
vinicius.carvalho said:
Hi lads,
thanks for the support, I've solved by restoring the stock image (3.0) and then using the universal root procedure.
Regards
Click to expand...
Click to collapse
where did you get it?
Hey guys. I just got my HOX and have been trying to root it. The software update keeps popping up and I keep refusing, so no worries there. I've got 1.85 right now and have been attempting the methods found here and here, but they just aren't working. I'd prefer to use the manual method. Someone willing to help a guy get started with all this would be the greatest person ever, just saying!
blinkbomber said:
Hey guys. I just got my HOX and have been trying to root it. The software update keeps popping up and I keep refusing, so no worries there. I've got 1.85 right now and have been attempting the methods found here and here, but they just aren't working. I'd prefer to use the manual method. Someone willing to help a guy get started with all this would be the greatest person ever, just saying!
Click to expand...
Click to collapse
check pm
beaups said:
check pm
Click to expand...
Click to collapse
Could you help me too X( ? I got my HOX last night at 8pm; I traded my rooted S2 Skyrocket for it.
Been looking for the past day through forums and google. It's so different from Samsung's phones, but a nice change indeed.
I'm on 1.85 and tried those two methods also. I'm not very familiar with ADB. From reading all night and this morning, I believe I root, unlock bootloader, flash recovery, flash custom roms?
smartnphone said:
Could you help me too X( ? I got my HOX last night at 8pm; I traded my rooted S2 Skyrocket for it.
Been looking for the past day through forums and google. It's so different from Samsung's phones, but a nice change indeed.
I'm on 1.85 and tried those two methods also. I'm not very familiar with ADB. From reading all night and this morning, I believe I root, unlock bootloader, flash recovery, flash custom roms?
Click to expand...
Click to collapse
Follow the instructions in this link http://forum.xda-developers.com/showthread.php?p=30741993
Sent from my HTC One X using xda premium
abhipati said:
Follow the instructions in this link http://forum.xda-developers.com/showthread.php?p=30741993
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks. I used this for ADB http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
I remember using it for my S2, but I don't quite understand the directions for the http://forum.xda-developers.com/showthread.php?t=1709296 method. Could you dumb it down for this HOX noob?
smartnphone said:
Thanks. I used this for ADB http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
I remember using it for my S2, but I don't quite understand the directions for the http://forum.xda-developers.com/showthread.php?t=1709296 method. Could you dumb it down for this HOX noob?
Click to expand...
Click to collapse
I'll try to help! all of the following is my interpretation of the rooting method described here: http://forum.xda-developers.com/showthread.php?t=1709296
What you need:
HOX on ATT 1.85
su binary from http://dl.dropbox.com/u/don'tusemeimabadsubinary
EDIT: The su binary above has issues. Use this one instead: http://dl.dropbox.com/u/9060692/su
Make sure HTC sync is NOT RUNNING (down in system tray)
Make sure phone is set to "charge only" and usb debugging is enabled!
Download correct su file (assuming you don't have a problem with this step )
Put su in same directory as ADB. Get to adb command prompt and cd into that directory
Quote from Butters619: cd means change directory. It is a windows command prompt command. So you would type "cd C:\adb" if that was where your adb folder was. Folder and directory can be used interchangeably, although directory is more "correct". We only say folder because GUIs use folders to represent directories.
NEW - pull sim card
NEW - do factory reset
NEW - when reset is complete, do not replace sim, do NOT connect to wifi. Go through setup, go to settings, enable USB debugging. When that's done:
Enter these commands in adb:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
(If you get file doesn't exist after the FIRST command don't worry - they may not be there)
Now, on the phone, go to settings and check for software update. It will tell you you need to connect to network. Now, replace the SIM OR connect to wifi. Have it check for software update again. When it's done, do NOT click "yes" or "ok" on the phone. Simply:
Enter these commands in adb:
adb shell ls -l /data/local.prop
IF AND ONLY IF you get "file not exists" or anything like that then set your phone's date 2 days ahead and reboot the phone and start over. If you get file info, you're golden. Proceed...
Enter these commands into adb:
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Reboot via adb by entering this command: adb reboot
After phones reboots
Enter these commands in adb:
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
You should be rooted.
A cool username said:
I'll try to help! all of the following is my interpretation of the rooting method described here: http://forum.xda-developers.com/showthread.php?t=1709296
What you need:
HOX on ATT 1.85
su binary from http://dl.dropbox.com/u/don'tusemeimabadsubinary
EDIT: The su binary above has issues. Use this one instead: http://dl.dropbox.com/u/9060692/su
Make sure HTC sync is NOT RUNNING (down in system tray)
Make sure phone is set to "charge only" and usb debugging is enabled!
Download correct su file (assuming you don't have a problem with this step )
Put su in same directory as ADB. Get to adb command prompt and cd into that directory
Quote from Butters619: cd means change directory. It is a windows command prompt command. So you would type "cd C:\adb" if that was where your adb folder was. Folder and directory can be used interchangeably, although directory is more "correct". We only say folder because GUIs use folders to represent directories.
NEW - pull sim card
NEW - do factory reset
NEW - when reset is complete, do not replace sim, do NOT connect to wifi. Go through setup, go to settings, enable USB debugging. When that's done:
Enter these commands in adb:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
(If you get file doesn't exist after the FIRST command don't worry - they may not be there)
Now, on the phone, go to settings and check for software update. It will tell you you need to connect to network. Now, replace the SIM OR connect to wifi. Have it check for software update again. When it's done, do NOT click "yes" or "ok" on the phone. Simply:
Enter these commands in adb:
adb shell ls -l /data/local.prop
IF AND ONLY IF you get "file not exists" or anything like that then set your phone's date 2 days ahead and reboot the phone and start over. If you get file info, you're golden. Proceed...
Enter these commands into adb:
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Reboot via adb by entering this command: adb reboot
After phones reboots
Enter these commands in adb:
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
You should be rooted.
Click to expand...
Click to collapse
Thanks. Yeah i've been trying it alld ay but it can't find where my SU is. it's in the same location as the ADB stuff i believe C:\android-sdk-windows. Seem like some of the senior members are willing to go through teamviewer to help the ones who can't do it. I'll try asking them :/
Sorry I couldn't be of any help, but please let me know if/how you get this to work just in case this happens to me when I get my one x.
Sent from my Touch Pro 2 using xda app-developers app
---------- Post added at 08:22 PM ---------- Previous post was at 08:18 PM ----------
blinkbomber said:
Hey guys. I just got my HOX and have been trying to root it. The software update keeps popping up and I keep refusing, so no worries there. I've got 1.85 right now and have been attempting the methods found here and here, but they just aren't working. I'd prefer to use the manual method. Someone willing to help a guy get started with all this would be the greatest person ever, just saying!
Click to expand...
Click to collapse
I wonder if the one who actually started this thread got his/her phone to work...???
Sent from my Touch Pro 2 using xda app-developers app
Someone think they can help me root the phone? I'm on 1.85 and I believe I finally got adb to recognize my device but after that I don't think I'm doing it right
Sent from my SGH-I777 using XDA Premium App