Having trouble rooting my Moto X - Moto X Q&A

I've been following this guide http://www.reddit.com/r/MotoX/comments/1t5ei6/guide_root_verizon_nondeveloper_moto_x_44/ for rooting my Moto X but once I reach step 8, it says Dalvik VM can't locate "SlapMyMoto" Here's the entire error:
~ $ dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto.
Dalvik VM unable to locate class 'SlapMyMoto/'
java.lang.NoClassDefFoundError: SlapMyMoto/
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.ClassNotFoundException: Didn't find class "SlapMyMoto." on path: /sdcard/SlapMyMoto.jar
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:65)
at java.lang.ClassLoader.loadClass(ClassLoader.java:501)
at java.lang.ClassLoader.loadClass(ClassLoader.java:461)
... 1 more
Help please

Change what you posted:
~ $ dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto.
to:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
Notice the trailing "." is gone.
edit, use this: http://forum.xda-developers.com/showthread.php?t=2538896
Not some red thingy.

syntrix said:
Change what you posted:
~ $ dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto.
to:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
Notice the trailing "." is gone.
edit, use this: http://forum.xda-developers.com/showthread.php?t=2538896
Not some red thingy.
Click to expand...
Click to collapse
damn I missed that. I spent over 5 hours on this :crying:
Thanks man you don't even know how happy I am atm

tomh12player said:
damn I missed that. I spent over 5 hours on this :crying:
Thanks man you don't even know how happy I am atm
Click to expand...
Click to collapse
And I haven't even done those mods yet! But having decades of command line experience help to notice these things! Good luck!!! :good::good:
Please post a link to XDA on the red post! If any XDA people see it, they might want to stab it

Related

[ROOTING] The M7 Exploit + Newbie Guide

To be honest, I'm a nice guy, but when threads get filled with utter "OMG, How do I root?" posts, I get pissed off. I don't mean to backseat moderate or anything, I just really get fed up sometimes. Hence, I've broken out the hardcore side of myself, and I present:
Coburn's (mostly) failproof rootmeplz kthxbai tutorial, featuring the awesome m7 exploit.
YOU CANNOT USE THIS ROOT GUIDE TO INSTALL ANDROID 2.0.x/2.1/2.x AT THIS MOMENT IN TIME. PLEASE DO NOT ASK IF YOU CAN INSTALL ANDROID 2.x USING ROOT, AT THIS STAGE IT'S A BIG FAT NO! THANK YOU FOR YOUR ATTENTION!!
Alright.
Easy to understand, plain english guide
Download the ZIP file attached to this post. Extract the files to a safe location - perhaps C:\Tattoo ?
Now, you'll need adb for windows. You can get it from my website's server here: ADB for windows.
Make sure your device is in USB Debug Mode (Settings > Applications > Development). This is ESSENTIAL!
Extract all the files in the adb4win zip file to your C:\Tattoo folder.
Now, go to Command Prompt. In XP, it's under System Tools in Accessories. In Vista/7, it'll be under accessories.
Do the following at the command line:
C:\Users\Coburn> cd C:\Tattoo
This will change your working directory from C:\Users\Coburn (or silimar) to C:\Tattoo .
Now, at the command line, do this:
C:\Tattoo> adb-windows shell "mkdir /data/local/bin" (with the quotes!).
This makes a directory on the Tattoo under /data/local, called bin. If you get a error (like mkdir failed, file/folder exists), this is fine! Don't sweat it.
Now, run this command:
C:\Tattoo> adb-windows push m7 /data/local/bin/m7
...and wait until finish.
Run this:
C:\Tattoo> adb-windows shell "cd /data/local/bin && chmod 755 ./m7" (with the quotes!)
This allows you to run the sucker.
Now, the fun part. Run this:
C:\Tattoo> adb-windows shell
This will dump you at a "$" shell. do the following:
C:\Tattoo> adb-windows shell
$ cd /data/local/bin
$ while ./m7 ; do : ; done
...lotsa text will flow down your screen. This is normal. Sometimes the exploit causes adb to freeze up, I don't know. I think it may be due to the exploit. It worked on my mac fine though...
Soon, you'll be greeted with this:
#
This is the root prompt! If you get stuff like this:
# usage: reboot ...
usage: reboot ....
usage: reboot ...
Just keep your cool, press enter and the # will say "Boo" again. This is due the exploit spawning reboots to gain the shell.
Then, do these commands from this thread's first post:
-bm- and the hax0rs crew said:
You did it, you should be root now!
Let's set some variables:
Code:
export LD_LIBRARY_PATH=/system/lib
export PATH=/system/bin
[...] check if ur root:
Code:
id
You should get something like this:
Code:
# id
uid=0(root) gid=1000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
uid=0(root) is important.
Click to expand...
Click to collapse
When you get this:
C:\Tattoo> adb-windows shell
$ cd /data/local/bin
$ while ./m7 ; do : ; done
[... lotsa pasta ...]
#
You can do anything then! Look at /system, /data, etc etc. You're broken free, my friend, and you'll forever be free. Until you press that exit button. you didn't. You didn't press that exit button? lolwut u did? Grrrrrrr!!!
EDIT: Added Guide to remount partitions. It's below.
Now you need to install su. Exit your root shell (via CTRL+C) (NO, Coburn, are you serious? ME LOSE ROOT SHELL?! ) and download this su.zip and extract it to C:\Tattoo. DO NOT EXIT THE COMMAND PROMPT WINDOW.
Meanwhile, back at the ranch, in your command prompt window, do this:
C:\Tattoo> adb-windows push su /data/local/bin/su
Then break out a shell...
C:\Tattoo> adb-windows shell
at the $ prompt, enter:
$ chmod 755 /data/local/bin/su
$ cd /data/local/bin/
..run the exploit again via "while 'true' ; do ./m7 ; done" to get root again then enter ...
# chown root.root /data/local/bin/su
# chmod 4755 /data/local/bin/su
# mount -o rw,remount /dev/block/mtdblock5 /data
# mount -o rw,remount /dev/block/mtdblock3 /system (This line allows you to play around with files on the system partition!)
After that, you can exit out of the root shell, and try a normal shell and this:
$ /data/local/bin/su
...which should make you get a nice # prompt. (Sometimes it doesn't, for me it got su: permission denied, wtf?)
(End SU Part of guide)
Tested on Windows 7. Also works on a phone terminal emulator too!
Keep your cool peeps - I do this for fun, I'm not a fulltime android dev. I am an addict though.
Happy rootin my friends.
Cheers,
Tattoo Hacker Coburn.
Greets fly out to the geeks that hacked it originally - without you, I'd have got a nexus one.
Thanks for marsdroid for correcting an error. Kudos to you, bro!
"ANDROID - It's a virus. In a Good Way. Once it's in your system, you can't get rid of it."
You should also add the "su" part in order to get root easier after the first time. Otherwise you have to do the exploit every time you want #
You could also add an explanation on how to remount the partitions without nosuid, so that a suid su can work.
mainfram3 said:
You could also add an explanation on how to remount the partitions without nosuid, so that a suid su can work.
Click to expand...
Click to collapse
Noted. Will do.
LordGiotto said:
You should also add the "su" part in order to get root easier after the first time. Otherwise you have to do the exploit every time you want #
Click to expand...
Click to collapse
Heh, yeah. Might add that up too.
Coburn64.
Thanks Man.
Nice Thread.
Thank you Coburn
svprm said:
Coburn64.
Thanks Man.
Nice Thread.
Click to expand...
Click to collapse
Thanks bro for your thanks.
I'm very glad you did that work, I'm kind of busy but I will update my statusposting and link to your HowTo!
Thats great community work.
[ROOTING] The M7 Exploit + Newbie Guide
Easy to understand, plain english guide
Click to expand...
Click to collapse
I apologize for my english, it's not my native language and I tried my best. ;-)
Keep up your work!
-bm-
-bm- said:
I'm very glad you did that work, I'm kind of busy but I will update my statusposting and link to your HowTo!
Thats great community work.
I apologize for my english, it's not my native language and I tried my best. ;-)
Keep up your work!
-bm-
Click to expand...
Click to collapse
You're welcome. I actually wanted this thread to help your thread, I wanted to spawn a m7 exploit thread to keep the original thread (which is based on the classic m6 exploit) clean of "How do I root with m7" and such.
Keep up the good work too, bm!
Thanks Coburn, so m6 is useless..
adb shell rm /data/local/bin/m6?
thx for the work , and corrections ! deleted the ealyer post
?
When i get # , and type:
# chown root.root /data/local/bin/su
i get :
chown root.root /data/local/bin/su
chown: not found
#
What i'm doing wrong /??
liderzre said:
When i get # , and type:
# chown root.root /data/local/bin/su
i get :
chown root.root /data/local/bin/su
chown: not found
#
What i'm doing wrong /??
Click to expand...
Click to collapse
type
export LD_LIBRARY_PATH=/system/lib
export PATH=/system/bin
rooted
Ty. Guide is not 100% for noobs. (ME).
Problem copying files to system partition after successfull rooting
Hi
The device was rooted successfully (from the first time using m7)
But I have very strange problem.
I try to update some files in the /system (updating fonts in /system/fonts).
I successfully run following command to remount system with rw permissions
/system/bin/mount -o rw,remount /dev/block/mtdblock3 /system
But when I try to copy files to /system/fonts I get "not enough memory" error.
If I run "df" command it shows that /system has 14% free before write attempt
But if I run "df" command after the write attempt I see that there is no free space.
It looks like there is some protection mechanism that prevents copying files to /system partition.
Does any one has an idea how to solve it?
Thanks
ronyrad said:
Hi
The device was rooted successfully (from the first time using m7)
But I have very strange problem.
I try to update some files in the /system (updating fonts in /system/fonts).
I successfully run following command to remount system with rw permissions
/system/bin/mount -o rw,remount /dev/block/mtdblock3 /system
But when I try to copy files to /system/fonts I get "not enough memory" error.
If I run "df" command it shows that /system has 14% free before write attempt
But if I run "df" command after the write attempt I see that there is no free space.
It looks like there is some protection mechanism that prevents copying files to /system partition.
Does any one has an idea how to solve it?
Thanks
Click to expand...
Click to collapse
The problem is well known an jet we have got no explanation. It looks like an additional security system build in by HTC. That is what also prevents us from flashing Custom ROMS at the moment. Development goes on here: http://forum.xda-developers.com/showthread.php?t=631540&page=18 but there is no solution or explanation until now.
-bm-
Could it be that it seems to be that the driver (yaffs) is possibly trying to copy /system into memory, and then reflash the partition all at once (to prevent NAND/NOR tear and wear)?
this guide is in error and will for sure not work ...
you should post probberly ...specially now when things is working....
there is no reason do do a NONSENCE guide .....
thx for the work thoe
Click to expand...
Click to collapse
Excuse me, but it was tested working. I do not post false or misleading information, so please don't accuse me of posting something that won't work. It does work. If you have troubles, you're not following it correctly. Start again and work one step at a time.
Coburn64 said:
Excuse me, but it was tested working. I do not post false or misleading information, so please don't accuse me of posting something that won't work. It does work. If you have troubles, you're not following it correctly. Start again and work one step at a time.
Click to expand...
Click to collapse
don't worry for such baseless allegations coburn.... u r doing a great job. keep up this good work bro.... thanks a lot for this wonderful presentation...
waiting for ur custom ROM.....
Coburn64 u are missing a ; in the 2. while
and i dont expect the newbies to sit back and wait for the "BUUH"..
but im sure someone will....
thx again
EDIT Coburn64 fixed it

[Q] help w jb root

all is good until the last step whats going on?
[email protected]:/tmp/share$ tar xvf motoshare.tgz
adb
busybox
pwn
su
Superuser.apk
[email protected]:/tmp/share$ sudo chown root:root pwn
[email protected]:/tmp/share$ sudo chmod 6755 pwn
[email protected]:/tmp/share$ /tmp/share/adb shell /storage/rfs0/pwn
bash: /tmp/share/adb: No such file or directory
[email protected]:/tmp/share$
Please give me the response for the terminal command:
ls -l /tmp/share/adb
re jb root
[email protected]:/tmp/share$ ls -l /tmp/share/adb
-rwsr-sr-x 1 jody jody 204436 Feb 11 11:49 /tmp/share/adb
jodybgoode said:
[email protected]:/tmp/share$ ls -l /tmp/share/adb
-rwsr-sr-x 1 jody jody 204436 Feb 11 11:49 /tmp/share/adb
Click to expand...
Click to collapse
I will get back to you after I talk with Dan. Unless another set of eyes knows the solution.
Sent from my MB886 using xda app-developers app
Try running the last command as simply "adb shell /storage/rfs0/pwn"
(i.e. without the prefix /tmp/share/)
Help confused
djrbliss said:
As promised, this post describes how to root the Atrix HD Jelly Bean build. This should also work on other Motorola 4.1.2 builds (Razr/Razr Maxx, Razr HD, Razr M, etc.).
The exploit requires setting up a special Samba share and mounting this share on your phone using the File Manager app. I apologize that this process may seem involved for some of you, and request that members of this community help each other out if some of you are having problems completing the procedure. I'm not able to provide individual tech support to every user who wants to root this phone.
The following instructions require a working Linux installation. The following instructions are for Ubuntu. If you don't want to install Ubuntu permanently on your machine, I suggest using a LiveCD installation. Instructions on setting this up are described here:
https://help.ubuntu.com/community/LiveCD#How-To_LiveCD_Ubuntu
Once you're booted into Ubuntu, open a terminal. Create a new directory for your Samba share:
Code:
mkdir /tmp/share
Next, install the samba package:
Code:
sudo apt-get install samba
Edit the configuration file for samba:
Code:
sudo gedit /etc/samba/smb.conf
Add the following lines to the end of the configuration file and save your changes:
Code:
[share]
path = /tmp/share
available = yes
valid users = guest
read only = yes
browsable = yes
public = yes
Close the text editor once you've saved your changes.
Next, create a user for the Samba share by typing in the terminal:
Code:
sudo useradd guest -m -G users
Set a password for the new user. Remember this password:
Code:
sudo passwd guest
Provide a password here and press enter. You won't see the characters you're typing, so be careful.
Next, set a password on the share. Use the same password you just provided:
Code:
sudo smbpasswd -a guest
Type the password you created before and press enter.
Next, restart the Samba server:
Code:
sudo restart smbd
Finally, download and prepare the required files to the Samba share:
Code:
cd /tmp/share
wget [url]http://vulnfactory.org/public/motoshare.tgz[/url]
tar xvf motoshare.tgz
sudo chown root:root pwn
sudo chmod 6755 pwn
At this point, you'll need to know the IP address of your Linux host, which you can get by running "ifconfig" from your terminal (it should be of the form "192.168.x.x").
Next, move over to your Android device. Ensure you have enabled USB Debugging Mode (under Settings -> Development Settings). Ensure your device is connected via Wifi.
Open the "File Manager" app, and select "Remote storage". Click "Add storage", and fill in fields as follows:
Code:
Host IP address: [your Linux machine's IP address]
Domain name: WORKGROUP
Shared folder name: share
User: guest
Password: [the password you created above]
At this point, the phone will mount your Linux share. To complete the process, plug in your phone via USB to your Linux machine, and type the following in your Linux terminal:
Code:
sudo /tmp/share/adb kill-server
sudo /tmp/share/adb shell /storage/rfs0/pwn
If it's successful, this should print "[+] Rooting complete!".
Finally, install Supersu by typing the following in the terminal:
Code:
sudo /tmp/share/adb install /tmp/share/eu.chainfire.supersu.apk
Congratulations, enjoy your rooted device.
I can't stress this enough: I can't provide individualized tech support for everyone on this forum. Please help each other.
TTLayland has been successfully rooted using this technique and has volunteered to help. If you get stuck and can't find support on these forums, feel free to email him at ttlayland (at) gmail (dot) com.
Paypal:
http://goo.gl/zBGb0
Click to expand...
Click to collapse
Got this error:
[email protected]:/tmp/share$ sudo /tmp/share/adb shell /storage/rfs0/pwn
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
mount: Operation not permitted
sh: can't create /system/xbin/busybox: Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
sh: busybox: not found
cp: /system/bin/su: Read-only file system
Unable to chown /system/bin/su: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
link failed Read-only file system
[+] Rooting complete!
[email protected]:/tmp/share$
Then it says: "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" when opening SuperSU
PLEASE HELP HERE OR MY EMAIL! : [email protected]
Thanks in advanced
progrockguy said:
Try running the last command as simply "adb shell /storage/rfs0/pwn"
(i.e. without the prefix /tmp/share/)
Click to expand...
Click to collapse
progrockguy said:
Try running the last command as simply "adb shell /storage/rfs0/pwn"
(i.e. without the prefix /tmp/share/)
Click to expand...
Click to collapse
that worked kinda. well it says rooting complete but when i update superuser or root checker says root fail
Please Help: error: device offline
I am getting the following error
[email protected]:/tmp/share$ sudo /tmp/share/adb kill-server
[email protected]:/tmp/share$ sudo /tmp/share/adb shell /storage/rfs0/pwn
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device offline
[email protected]:/tmp/share$
I am running the LiveCD in VMware Workstation
Sorry for the duplicate posts
worked perfectly after i used a 32 bit live disk
jodybgoode said:
worked perfectly after i used a 32 bit live disk[/QUOTE
Did you use Ubuntu and which version?
do you have a link to the CD?
Did you boot a machine or you used VMware or Virtualbox?
Click to expand...
Click to collapse
Why would anyone even attempt to use a VM for this simple root method? You could've been rooted already if you had just followed the instructions.
Same problem here. I couldn't get past the adb kill-server command. It would tell me there is no such directory. If any one can get past this can someone please tell me what they did to get past it.
Black_halo said:
Same problem here. I couldn't get past the adb kill-server command. It would tell me there is no such directory. If any one can get past this can someone please tell me what they did to get past it.
Click to expand...
Click to collapse
I am stuck, I have tried so many machine to no luck
Please someone help
Start over and just copy and paste each single line and hit enter do not copy multiple code lines .
ATRIX HD running BATAKANG 1.10
sickkside13 said:
Start over and just copy and paste each single line and hit enter do not copy multiple code lines .
ATRIX HD running BATAKANG 1.10
Click to expand...
Click to collapse
I did, no luck
Dammz man idk what else to tell you yesterday i spend all day trying to root too but just when i was about to give up i got everything g working
ATRIX HD running BATAKANG 1.10
sickkside13 said:
Dammz man idk what else to tell you yesterday i spend all day trying to root too but just when i was about to give up i got everything g working
ATRIX HD running BATAKANG 1.10
Click to expand...
Click to collapse
hehehehe
Does the root method have anything to do with having android sdk and ndk on your system? Im thinking thats what it is now. Would i have to have linux sdk to run with terminal root or windows sdk?
Black_halo said:
Does the root method have anything to do with having android sdk and ndk on your system? Im thinking thats what it is now. Would i have to have linux sdk to run with terminal root or windows sdk?
Click to expand...
Click to collapse
No, you don't need the Android SDK/NDK, since I included a copy of ADB in the tarball file that you extracted to /tmp/share.
What's the output of "ls -l /tmp/share/adb" on your Linux machine?
I had to re-flash official JB firmware in RSD Lite before the exploit would work. Before that, the Exploit would return "Root Complete", but there was no root access (though I could su to # in adb). I run Ubuntu 12.04 x64 at work already with Windows in VirtualBox.
RSD Lite doesn't seem to want to complete a flash in the Windows VMs I run in VirtualBox at work, so I waited until I got home and used my Windows 8 Pro machine to RSD the phone with the official JB firmware. I run Ubuntu 12.04 in a VirtualBox on that machine already, so after the RSD flash, I ran the exploit from that VM - BINGO - worked on the first try.
Failing other options, you might want to try re-flashing JB in RSD Lite and running the exploit on a fresh device.
I used the firmware in this thread (To fix the issue the thread is about):
http://forum.xda-developers.com/showthread.php?t=2057078
If you decide to try that, Be SURE to get the firmware zip AND THE XML and replace the XML before flashing!!

[Q] SlapMyMoto Error: Permission Denied

Hey Everyone,
When I get to the last step of the SlapMyMoto rooting process, I get the following error message:
Code:
/system/bin/sh: can't create /sys/kernel/uevent_helper: Permission denied
I was running into exactly the same problem yesterday, so today I started the entire process from scratch and manually typed everything in. I even ran the entire process from my Macbook (rather than a Windows VM) since several people said that the process worked on the first shot via Mac.
@jcase
If anyone can help, I'd really appreciate it. Thanks!
bobo-the-drunk said:
Hey Everyone,
When I get to the last step of the SlapMyMoto rooting process, I get the following error message:
Code:
/system/bin/sh: can't create /sys/kernel/uevent_helper: Permission denied
I was running into exactly the same problem yesterday, so today I started the entire process from scratch and manually typed everything in. I even ran the entire process from my Macbook (rather than a Windows VM) since several people said that the process worked on the first shot via Mac.
@jcase
If anyone can help, I'd really appreciate it. Thanks!
Click to expand...
Click to collapse
paste the command and full output here please
Thanks for the speedy reply @jcase! I accidentally closed the telnet terminal after I finished that part of the process, but here's all the ADB content.
Code:
supermacbook:~ Bobo$ adb shell getprop ro.boot.write_protect
0
supermacbook:~ Bobo$ adb push /Users/Bobo/Downloads/SlapMyMoto-1.0/SlapMyMoto.jar /sdcard/SlapMyMoto.jar
3848 KB/s (67653 bytes in 0.017s)
supermacbook:~ Bobo$ adb reboot
supermacbook:~ Bobo$ adb reboot
supermacbook:~ Bobo$ adb shell
[email protected]:/ $ cp /sdcard/install.sh /data/local/tmp/install.sh
[email protected]:/ $ chmod 755 /data/local/tmp/install.sh
[email protected]:/ $ echo "/data/local/tmp/install.sh" > /sys/kernel/uvent_helper
/system/bin/sh: can't create /sys/kernel/uevent_helper: Permission denied
Code:
[email protected]:/ $ echo "/data/local/tmp/install.sh" > /sys/kernel/uvent_helper
Typo, it is uevent_helper not uvent_helper
bobo-the-drunk said:
Thanks for the speedy reply @jcase! I accidentally closed the telnet terminal after I finished that part of the process, but here's all the ADB content.
Code:
supermacbook:~ Bobo$ adb shell getprop ro.boot.write_protect
0
supermacbook:~ Bobo$ adb push /Users/Bobo/Downloads/SlapMyMoto-1.0/SlapMyMoto.jar /sdcard/SlapMyMoto.jar
3848 KB/s (67653 bytes in 0.017s)
supermacbook:~ Bobo$ adb reboot
supermacbook:~ Bobo$ adb reboot
supermacbook:~ Bobo$ adb shell
[email protected]:/ $ cp /sdcard/install.sh /data/local/tmp/install.sh
[email protected]:/ $ chmod 755 /data/local/tmp/install.sh
[email protected]:/ $ echo "/data/local/tmp/install.sh" > /sys/kernel/uvent_helper
/system/bin/sh: can't create /sys/kernel/uevent_helper: Permission denied
Click to expand...
Click to collapse
You're right, but I actually already caught that (actually adb shell told me...)
Here's the unabridged version:
Code:
supermacbook:~ Bobo$ adb shell
[email protected]:/ $ cp /sdcard/install.sh /data/local/tmp/install.sh
[email protected]:/ $ chmod 755 /data/local/tmp/install.sh
sh[email protected]:/ $ echo "/data/local/tmp/install.sh" > /sys/kernel/uvent_helper
/system/bin/sh: can't create /sys/kernel/uvent_helper: No such file or directory
sh" > /sys/kernel/uvent_helper <
/system/bin/sh: can't create /sys/kernel/uvent_helper: No such file or directory
sh" > /sys/kernel/uevent_helper <
/system/bin/sh: can't create /sys/kernel/uevent_helper: Permission denied
1|[email protected]:/ $
sh" > /sys/kernel/uevent_helper <
/system/bin/sh: can't create /sys/kernel/uevent_helper: Permission denied
1|[email protected]:/ $
sh" > /sys/kernel/uevent_helper <
/system/bin/sh: can't create /sys/kernel/uevent_helper: Permission denied
1|[email protected]:/ $
sh" > /sys/kernel/uevent_helper <
/system/bin/sh: can't create /sys/kernel/uevent_helper: Permission denied
I'm having the same error
Has anyone had any success? I've tried on ubuntu and windoze 7. Both come back with this error:
/system/bin/sh: can't create /sys/kernel/uevent_helper: Permission denied
I'm so close, I can almost smell the root. Any additional help would be greatly appreciated.
Same here
acupunk said:
Has anyone had any success? I've tried on ubuntu and windoze 7. Both come back with this error:
/system/bin/sh: can't create /sys/kernel/uevent_helper: Permission denied
I'm so close, I can almost smell the root. Any additional help would be greatly appreciated.
Click to expand...
Click to collapse
Also getting this when trying to root. Im on windows 7
i think i know what your issue is. i did it last night when i was trying to root 4.4
your skipping a step.
after you type in cwgin
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
then you reboot your device
but then you have to run the command again in cwgin but this time it should reboot it self.
then continue with the rest of the commands
i missed it the first time threw. and it gave me the same issue. hope that helps
Thanks
dray_jr said:
i think i know what your issue is. i did it last night when i was trying to root 4.4
your skipping a step.
after you type in cwgin
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
then you reboot your device
but then you have to run the command again in cwgin but this time it should reboot it self.
then continue with the rest of the commands
i missed it the first time threw. and it gave me the same issue. hope that helps
Click to expand...
Click to collapse
Thank you, but that's not the problem. I did run slapmymoto twice. Any other ideas? I'm actually on a Droid Maxx so I can't downgrade and start over.
acupunk said:
Thank you, but that's not the problem. I did run slapmymoto twice. Any other ideas? I'm actually on a Droid Maxx so I can't downgrade and start over.
Click to expand...
Click to collapse
''
if you are allready on 4.4 i think your stuck for now untill they find a way to root 4.4 without downgrading
sounds like you missed something before you ran the OTA
bobo-the-drunk said:
Thanks for the speedy reply @jcase! I accidentally closed the telnet terminal after I finished that part of the process, but here's all the ADB content.
Code:
supermacbook:~ Bobo$ adb shell getprop ro.boot.write_protect
0
supermacbook:~ Bobo$ adb push /Users/Bobo/Downloads/SlapMyMoto-1.0/SlapMyMoto.jar /sdcard/SlapMyMoto.jar
3848 KB/s (67653 bytes in 0.017s)
supermacbook:~ Bobo$ adb reboot
supermacbook:~ Bobo$ adb reboot
supermacbook:~ Bobo$ adb shell
[email protected]:/ $ cp /sdcard/install.sh /data/local/tmp/install.sh
[email protected]:/ $ chmod 755 /data/local/tmp/install.sh
[email protected]:/ $ echo "/data/local/tmp/install.sh" > /sys/kernel/uvent_helper
/system/bin/sh: can't create /sys/kernel/uevent_helper: Permission denied
Click to expand...
Click to collapse
I was stuck here too until I realized that I was not su by default on the shell.
Type su and hit enter
once you have a # at the prompt then type the rest.
This fixed it for me right away.
n0-0ne said:
I was stuck here too until I realized that I was not su by default on the shell.
Type su and hit enter
once you have a # at the prompt then type the rest.
This fixed it for me right away.
Click to expand...
Click to collapse
Thanks, but su is not installed without root.
acupunk said:
Thanks, but su is not installed without root.
Click to expand...
Click to collapse
Ok, maybe I'm wrong but thats what worked for me, try it or not it's no skin off my back.
Root on Windows 7 wont work
I have tried about 5 times to get my Moto X rooted with SlapMyMoto and i have had no luck. Any help would be greatly appreciated.
supertrav1980 said:
I have tried about 5 times to get my Moto X rooted with SlapMyMoto and i have had no luck. Any help would be greatly appreciated.
Click to expand...
Click to collapse
make your own thread and make sure you paste your CMD with the error your gettings or the issues your having.
Root on Windows 7 wont work
dray_jr said:
make your own thread and make sure you paste your CMD with the error your gettings or the issues your having.
Click to expand...
Click to collapse
will do. thanks.

[Q] Mac Toolkit help please

I'm on the last step of mjphillips1981's mac toolkit for 4.4 rooting and it won't finish:
Code:
Press ENTER to finish the SlapMyMoto process.
Open a new terminal window by pressing Command+N
In the new terminal window type the following command
./adb shell echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
Press ENTER when you have finished the above command
I keep getting the error:
Code:
-bash: /sys/kernel/uevent_helper: No such file or directory
I've been at this all day
try this
open terminal
cd to the toolkit folder
type the following (one line at a time)
./adb shell
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
I think these lines need to be separated.
Hit me up on Google+ and lets see if we can work through this.
An I would suggest that you put questions in the toolkit thread. I was just browsing and noticed this. If you put the question in the thread I get an email.
nwinston96 said:
I'm on the last step of mjphillips1981's mac toolkit for 4.4 rooting and it won't finish:
Code:
Press ENTER to finish the SlapMyMoto process.
Open a new terminal window by pressing Command+N
In the new terminal window type the following command
./adb shell echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
Press ENTER when you have finished the above command
I keep getting the error:
Code:
-bash: /sys/kernel/uevent_helper: No such file or directory
I've been at this all day
Click to expand...
Click to collapse
nwinston96 said:
I'm on the last step of mjphillips1981's mac toolkit for 4.4 rooting and it won't finish:
Code:
Press ENTER to finish the SlapMyMoto process.
Open a new terminal window by pressing Command+N
In the new terminal window type the following command
./adb shell echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
Press ENTER when you have finished the above command
I keep getting the error:
Code:
-bash: /sys/kernel/uevent_helper: No such file or directory
I've been at this all day
Click to expand...
Click to collapse
missed some commands it looks like but im not sure if anything is diffrent because your on a mac
but here is the step by step from jcase's thread
Step1)
Unzip SlapMyMoto-1,0.zip and push the jar file to your internal storage
Code:
adb push SlapMyMoto.jar /sdcard/SlapMyMoto.jar
Step2)
Use http://www.cydiaimpactor.com/ to open up a telnet session as system user on port 2222. We covered how to use Impactor and telnet in the RockMyMoto root, I won't be covering it again since this post is going to be long enough already, see here -> http://forum.xda-developers.com/show....php?t=2509590 or http://rootzwiki.com/topic/107098-ro...the-first-ota/
Connecting over telnet, and run Stage1 with this command:
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
When the device tells you to reboot, do this manually with "adb reboot" or your power button. It will not auto reboot on this step
Step3)
Once the device has rebooted, run Impactor again and connect over telnet just like in the previous step, then run the same command
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
Once the device has rebooted, please take the 4.4 OTA.
Step4)
Now that we are on 4.4, we can finish the process with adb shell:
Code:
adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
dray_jr said:
missed some commands it looks like but im not sure if anything is diffrent because your on a mac
but here is the step by step from jcase's thread
Step1)
Unzip SlapMyMoto-1,0.zip and push the jar file to your internal storage
Code:
adb push SlapMyMoto.jar /sdcard/SlapMyMoto.jar
Step2)
Use http://www.cydiaimpactor.com/ to open up a telnet session as system user on port 2222. We covered how to use Impactor and telnet in the RockMyMoto root, I won't be covering it again since this post is going to be long enough already, see here -> http://forum.xda-developers.com/show....php?t=2509590 or http://rootzwiki.com/topic/107098-ro...the-first-ota/
Connecting over telnet, and run Stage1 with this command:
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
When the device tells you to reboot, do this manually with "adb reboot" or your power button. It will not auto reboot on this step
Step3)
Once the device has rebooted, run Impactor again and connect over telnet just like in the previous step, then run the same command
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
Once the device has rebooted, please take the 4.4 OTA.
Step4)
Now that we are on 4.4, we can finish the process with adb shell:
Code:
adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
Click to expand...
Click to collapse
These commands are all in the toolkit. The only one that needed to be enter on individual lines is the one he listed.
I just wish he would have posted the question in the Toolkit thread so I could have helped earlier.
mjphillips1981 said:
These commands are all in the toolkit. The only one that needed to be enter on individual lines is the one he listed.
I just wish he would have posted the question in the Toolkit thread so I could have helped earlier.
Click to expand...
Click to collapse
Ok I have the toolkit for Windows but I'm not familiar with the Mac one thanks for correcting my mistake and getting him
Sent from my XT1056 using XDA Premium 4 mobile app
mjphillips1981 said:
try this
open terminal
cd to the toolkit folder
type the following (one line at a time)
./adb shell
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
I think these lines need to be separated.
Hit me up on Google+ and lets see if we can work through this.
An I would suggest that you put questions in the toolkit thread. I was just browsing and noticed this. If you put the question in the thread I get an email.
Click to expand...
Click to collapse
Thanks, I think this did it. The only thing is that I had to manually reboot my phone, but it appears I am rooted as I'm able to run root-only apps. XDA wouldn't let me post on your thread because I don't have the required number of posts. Glad you came across this thread! Thanks again
nwinston96 said:
Thanks, I think this did it. The only thing is that I had to manually reboot my phone, but it appears I am rooted as I'm able to run root-only apps. XDA wouldn't let me post on your thread because I don't have the required number of posts. Glad you came across this thread! Thanks again
Click to expand...
Click to collapse
You're welcome! From what I read. Some people do experience that the phone does not reboot on its own.
Glad you got it working.
I just removed the toolkit. It's too hard to for me to get things working correctly when I do not have a consumer device to test with.

[Q] Stuck on last steps on Moto X root

I have tried finding the answer in the forums, but cannot find another with the same problem in the development forum and in this Q&A forum.
I have been following the root path by jcase. My phone was stock 4.4. I downgraded with RSD Lite to 4.2.2. I rooted with RockMyMoto. I did the MotoWPNoMo step.
Code:
B:\Important\Moto X\adt-bundle-windows-x86-20131030\adt-bundle-windows-x86-20131
030\sdk\platform-tools>adb shell getprop ro.boot.write_protect
0
B:\Important\Moto X\adt-bundle-windows-x86-20131030\adt-bundle-windows-x86-20131
030\sdk\platform-tools>
Everything seemed to work to that point. I installed 4.2.2 again and did RockMyMoto. It took some time, but it said it worked good. I still had write access after this.
I used RSD Lite to install 4.4-13.11.1Q2.X-69-3 since I was unsure if I should do the OTA update now that 4.4.2 is out.
Install was fine, but when I run the final steps, the file does not exist:
Code:
B:\Important\Moto X\adt-bundle-windows-x86-20131030\adt-bundle-windows-x86-20131
030\sdk\platform-tools>adb shell
[email protected]:/ $ cp /sdcard/install.sh /data/local/tmp/install.sh
cp /sdcard/install.sh /data/local/tmp/install.sh
cp: /sdcard/install.sh: No such file or directory
1|[email protected]:/ $
I still have write access as far as I can tell:
Code:
B:\Important\Moto X\adt-bundle-windows-x86-20131030\adt-bundle-windows-x86-20131
030\sdk\platform-tools>adb shell getprop ro.boot.write_protect
0
B:\Important\Moto X\adt-bundle-windows-x86-20131030\adt-bundle-windows-x86-20131
030\sdk\platform-tools>
I still get a "0" with this command. It feels like I am so close, can anyone help? Should I take the 4.4 OTA update instead using RSD Lite?
Cheers!
grenik said:
I have tried finding the answer in the forums, but cannot find another with the same problem in the development forum and in this Q&A forum.
I have been following the root path by jcase. My phone was stock 4.4. I downgraded with RSD Lite to 4.2.2. I rooted with RockMyMoto. I did the MotoWPNoMo step.
Code:
B:\Important\Moto X\adt-bundle-windows-x86-20131030\adt-bundle-windows-x86-20131
030\sdk\platform-tools>adb shell getprop ro.boot.write_protect
0
B:\Important\Moto X\adt-bundle-windows-x86-20131030\adt-bundle-windows-x86-20131
030\sdk\platform-tools>
Everything seemed to work to that point. I installed 4.2.2 again and did RockMyMoto. It took some time, but it said it worked good. I still had write access after this.
I used RSD Lite to install 4.4-13.11.1Q2.X-69-3 since I was unsure if I should do the OTA update now that 4.4.2 is out.
Install was fine, but when I run the final steps, the file does not exist:
Code:
B:\Important\Moto X\adt-bundle-windows-x86-20131030\adt-bundle-windows-x86-20131
030\sdk\platform-tools>adb shell
[email protected]:/ $ cp /sdcard/install.sh /data/local/tmp/install.sh
cp /sdcard/install.sh /data/local/tmp/install.sh
cp: /sdcard/install.sh: No such file or directory
1|[email protected]:/ $
I still have write access as far as I can tell:
Code:
B:\Important\Moto X\adt-bundle-windows-x86-20131030\adt-bundle-windows-x86-20131
030\sdk\platform-tools>adb shell getprop ro.boot.write_protect
0
B:\Important\Moto X\adt-bundle-windows-x86-20131030\adt-bundle-windows-x86-20131
030\sdk\platform-tools>
I still get a "0" with this command. It feels like I am so close, can anyone help? Should I take the 4.4 OTA update instead using RSD Lite?
Cheers!
Click to expand...
Click to collapse
did you make sure that you ran this command via telnet/impactor
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
then after the phone rebooted you have to run the same command again over telnet/impactor
?
grenik said:
I have tried finding the answer in the forums, but cannot find another with the same problem in the development forum and in this Q&A forum.
I have been following the root path by jcase. My phone was stock 4.4. I downgraded with RSD Lite to 4.2.2. I rooted with RockMyMoto. I did the MotoWPNoMo step.
Code:
B:\Important\Moto X\adt-bundle-windows-x86-20131030\adt-bundle-windows-x86-20131
030\sdk\platform-tools>adb shell getprop ro.boot.write_protect
0
B:\Important\Moto X\adt-bundle-windows-x86-20131030\adt-bundle-windows-x86-20131
030\sdk\platform-tools>
Everything seemed to work to that point. I installed 4.2.2 again and did RockMyMoto. It took some time, but it said it worked good. I still had write access after this.
I used RSD Lite to install 4.4-13.11.1Q2.X-69-3 since I was unsure if I should do the OTA update now that 4.4.2 is out.
Install was fine, but when I run the final steps, the file does not exist:
Code:
B:\Important\Moto X\adt-bundle-windows-x86-20131030\adt-bundle-windows-x86-20131
030\sdk\platform-tools>adb shell
[email protected]:/ $ cp /sdcard/install.sh /data/local/tmp/install.sh
cp /sdcard/install.sh /data/local/tmp/install.sh
cp: /sdcard/install.sh: No such file or directory
1|[email protected]:/ $
I still have write access as far as I can tell:
Code:
B:\Important\Moto X\adt-bundle-windows-x86-20131030\adt-bundle-windows-x86-20131
030\sdk\platform-tools>adb shell getprop ro.boot.write_protect
0
B:\Important\Moto X\adt-bundle-windows-x86-20131030\adt-bundle-windows-x86-20131
030\sdk\platform-tools>
I still get a "0" with this command. It feels like I am so close, can anyone help? Should I take the 4.4 OTA update instead using RSD Lite?
Cheers!
Click to expand...
Click to collapse
Your problem is you used RSD Lite instead of taking the ota. When you use RSD Lite to flash system.IMG it completely erases the system and all traces of the backdoor installed by slapmymoto to gain root.
Sent from my XT1058 using XDA Premium 4 mobile app
Dark9781 said:
Your problem is you used RSD Lite instead of taking the ota. When you use RSD Lite to flash system.IMG it completely erases the system and all traces of the backdoor installed by slapmymoto to gain root.
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I thought that may be the case, but I felt it was best to check since installing the wrong OTA update would make it so I could not root. I went back to 4.2.2, Slapped the Moto, and took the OTA. Worked like a charm!
Thank you for solving my problem.

Categories

Resources