I've spent the last week trying to get my phone rooted from 4.4 downgraded to 4.2.2 got root access but I couldn't get motowpnomo to run.. but now I FINALLY got it to run and go.. but I can't remember what to do after I get motowpnomo, and i re-flashed back to stock NON root 4.2.2... but i don't remember what to do after that. I've typed so many commands in CMD and all that, I'm at a loss....please guide me in the right direction please!!!
Just read over the slap my moto thread again. I'm sure you already have, but read it again and try asking in that thread. Good luck and hope all goes well!
Sent from my iPad using Tapatalk
Use adb to push su. Then push slapmymoto.jar. that's the first step. Then follow the instructions on the first couple posts in the slap thread. I don't remember all the commands but they are outlined in the thread. Your almost home. Don't over think it. You can do it.
slapped the sh*t out of my X
lowvolt1 said:
Use adb to push su. Then push slapmymoto.jar. that's the first step. Then follow the instructions on the first couple posts in the slap thread. I don't remember all the commands but they are outlined in the thread. Your almost home. Don't over think it. You can do it.
slapped the sh*t out of my X
Click to expand...
Click to collapse
OK...so I just fallow the directions like I did before I used motowpnomo?
Sent from my XT1060 using xda premium
xpsychox said:
OK...so I just fallow the directions like I did before I used motowpnomo?
Sent from my XT1060 using xda premium
Click to expand...
Click to collapse
Yes. Just follow the steps in the slapped thread.
slapped the sh*t out of my X
lowvolt1 said:
Yes. Just follow the steps in the slapped thread.
slapped the sh*t out of my X
Click to expand...
Click to collapse
Sweet..the I'll do it when I get home from work..
Sent from my XT1060 using xda premium
ok, so i go threw slapmymoto's directions. i start with pushing slapmymoto, then push rockmymoto, then i try to telnet and connect to phone threw ipaddres on port 2222 (like instructed) try to run command "dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto" says something about WP. So I take the update of 4.4 and try command "
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"
it says "cannot find specified path" ideas?
oops, double posted by accident..
Do not push rock my moto
slapped the sh*t out of my X
---------- Post added at 04:15 PM ---------- Previous post was at 04:13 PM ----------
You don't push rock my moto.
You do run dalvikvm command three times as specified. Don't worry about the no wp.
You will have to run cydia and telnet or puttytel each time.
slapped the sh*t out of my X
lowvolt1 said:
Do not push rock my moto
slapped the sh*t out of my X
---------- Post added at 04:15 PM ---------- Previous post was at 04:13 PM ----------
You don't push rock my moto.
You do run dalvikvm command three times as specified. Don't worry about the no wp.
You will have to run cydia and telnet or puttytel each time.
slapped the sh*t out of my X
Click to expand...
Click to collapse
OK.. So do it exactly the same except don't push rockmymoto?
Sent from my XT1060 using xda premium
Do it exactly per instructions.
Do not push rock.
Do not worry about the wp.
Do take your time.
Do not over think it.
slapped the sh*t out of my X
---------- Post added at 04:39 PM ---------- Previous post was at 04:20 PM ----------
Okay. I'm sitting at PC. looking at the slap thread.
1) unzip slapmymoto 1.0
Push slapmymoto.jar to sdcard/slapmymoto
2) run cydia impactor and start telnet as system on port 2222
3) either telnet or use puttytel and run dalvikvm -cp /sdcard/slapmymoto.jar slapmymoto
When the device tells you to reboot, do this with adb reboot
4) when the device comes back up, run impactor again and either telnet or use puttytel and run dalvikvm -cp /sdcard/slapmymoto.jar slapmymoto again
The device will reboot.
5) one the device is back up. Take 4.4 OTA.
Once on 4.4 you will enable USB debugging and continue.
6) in adb run adb shell
7) run cp /sdcard/install.sh /data/local/tmp/install.sh
8) run chmod 755 /data/local tmp/install.sh
9) run echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
10) either wait for the device to reboot or toggle blue tooth.
(Note) sometimes the device will not reboot. Simply manually reboot.
11) install supersu from play store open it and update binaries.
(Note) all above files must be in your fastboot folder.
slapped the sh*t out of my X
lowvolt1 said:
Do it exactly per instructions.
Do not push rock.
Do not worry about the wp.
Do take your time.
Do not over think it.
slapped the sh*t out of my X
---------- Post added at 04:39 PM ---------- Previous post was at 04:20 PM ----------
Okay. I'm sitting at PC. looking at the slap thread.
1) unzip slapmymoto 1.0
Push slapmymoto.jar to sdcard/slapmymoto
2) run cydia impactor and start telnet as system on port 2222
3) either telnet or use puttytel and run dalvikvm -cp /sdcard/slapmymoto.jar slapmymoto
When the device tells you to reboot, do this with adb reboot
4) when the device comes back up, run impactor again and either telnet or use puttytel and run dalvikvm -cp /sdcard/slapmymoto.jar slapmymoto again
The device will reboot.
5) one the device is back up. Take 4.4 OTA.
Once on 4.4 you will enable USB debugging and continue.
6) in adb run adb shell
7) run cp /sdcard/install.sh /data/local/tmp/install.sh
8) run chmod 755 /data/local tmp/install.sh
9) run echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
10) either wait for the device to reboot or toggle blue tooth.
(Note) sometimes the device will not reboot. Simply manually reboot.
11) install supersu from play store open it and update binaries.
(Note) all above files must be in your fastboot folder.
slapped the sh*t out of my X
Click to expand...
Click to collapse
ok, so I did the commands, installed 4.4 and ran rest of commands.. I have root access, but SU won't update... i open it, it says "cancel, or install from recovery" if i click install from recovery, it boots to android laying down with red "!" and says "error" and reboots. If I try and hold volume down and power to get into recovery and install the update that way, same thing... android laying down with red "!" ...ideas?
xpsychox said:
ok, so I did the commands, installed 4.4 and ran rest of commands.. I have root access, but SU won't update... i open it, it says "cancel, or install from recovery" if i click install from recovery, it boots to android laying down with red "!" and says "error" and reboots. If I try and hold volume down and power to get into recovery and install the update that way, same thing... android laying down with red "!" ...ideas?
Click to expand...
Click to collapse
Does it say install normal? It should
slapped the sh*t out of my X
lowvolt1 said:
Does it say install normal? It should
slapped the sh*t out of my X
Click to expand...
Click to collapse
no, the only update options I have in recovery, or cancel.. I'm wondering If one of the commands failed and I didn't see it.
What super su are you using
slapped the sh*t out of my X
lowvolt1 said:
What super su are you using
slapped the sh*t out of my X
Click to expand...
Click to collapse
the one with the "#" symbol..
xpsychox said:
the one with the "#" symbol..
Click to expand...
Click to collapse
open the market and make sure SuperSU is up to date. might be your issue. if it is up to date try removing it and reinstalling the SuperSU from chainfire
dray_jr said:
open the market and make sure SuperSU is up to date. might be your issue. if it is up to date try removing it and reinstalling the SuperSU from chainfire
Click to expand...
Click to collapse
I think his issue is the wrong supersu. I sent him a link to the chainfire one. Will see if that helps.
slapped the sh*t out of my X
Very possible I would just have him uninstall it and reinstall it from the market
Sent from Rooted Sprint Moto X, TWRP, enhanced kernel
dray_jr said:
Very possible I would just have him uninstall it and reinstall it from the market
Sent from Rooted Sprint Moto X, TWRP, enhanced kernel
Click to expand...
Click to collapse
He just confirmed it worked. I think we can call this one resolved.
slapped the sh*t out of my X
Related
ok, so i tried to get help in the actual froyo 2.2.13 install thread but i'm not getting an answer.
i downloaded, installed, and it said it was successful.. i rebooted, went into the settings to see if it changed, and it still said 2.2.9. i tried to do it again and now my phone will not reboot into recovery using droid x bootstrap or rom manager... won't even go into it if i do it manually... i tried to uninstall bootstrap and rom manager and reinstalling, no luck. please help.
brandon2x said:
ok, so i tried to get help in the actual froyo 2.2.13 install thread but i'm not getting an answer.
i downloaded, installed, and it said it was successful.. i rebooted, went into the settings to see if it changed, and it still said 2.2.9. i tried to do it again and now my phone will not reboot into recovery using droid x bootstrap or rom manager... won't even go into it if i do it manually... i tried to uninstall bootstrap and rom manager and reinstalling, no luck. please help.
Click to expand...
Click to collapse
Try these comands from :
AllDroid Public Board»Motorola»Droid X Forums»Droid X Rooting»How to get 2.2, Rooted, on your Droid X
under:
If you have /system/xbin/su and /system/app/Superuser.apk, but cannot use "Superuser" (no prompts from Superuser app, "permission denied" when you try to run "su"), just do the following:
Run "adb shell"
Run "/system/xbin/su"
Watch your screen for Superuser app to prompt for permission and click "allow"
Run "mount -o remount,rw /dev/block/system /system"
Run "cp /system/xbin/su /system/bin/su"
Run "chmod 4755 /system/bin/su"
Open the SuperUser application on the phone (app launcher) and make sure that "superuser" isn't listed and denied. If so, "forget it" and return to step 2. If you can't find SuperUser, it's not installed and you should download from this posts attachments and "adb install Superuser.apk"
[optional] Run "mount -o remount,ro /dev/block/system /system"
This should help you get your su working again.
not sure on your process so if you still do not have the .13 I would go back to your process and see what you are missing. I rebooted into recovery from bootstrap when I installed mine. Then I had to do the above commands to get my su back.
If you still don't have it, try the FULL instructions from here:
MDW Presents: Droid X 2.3.13 - The Froyo Upgrade
read through it and see if #5 from step 2 pertains to you.
The biggest thing to remember is to mount before you select the file to load on your sd card.
This thread:
Motorola Droid 2Droid 2 Android DevelopmentHow to root the Droid 2
will also be helpful regarding root if you have further questions.
Hope this helps.
My su is working fine. Nothing is being denied when I open it. Just cannot get to recovery with any option... im lost...
Sent from my DROIDX using XDA App
Maybe just double check through adb shell even if you are not having su issues?
Run "adb shell"
Run "/system/xbin/su"
Watch your screen for Superuser app to prompt for permission and click "allow" (I never saw any request)
Run "mount -o remount,rw /dev/block/system /system"
Run "cp /system/xbin/su /system/bin/su"
Run "chmod 4755 /system/bin/su"
I had similar issues of nothing being denied after a successful install and had to do the su commands. It helped me to reboot into recovery afterwards.
Sent from my DROIDX, Froyo FTW. Obsidian?
Ok im still learning.... how do I "run adb shell" and do these commands you're telling me...
Sent from my DROIDX using XDA App
brandon2x said:
Ok im still learning.... how do I "run adb shell" and do these commands you're telling me...
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I saw your post in the other thread. The best thing you can do is go through the links I gave you. Start with the root thread and click the more directions link in it. read through the processes and make sure you download all files and also understand what sbf is. Once you have all of the tools to do root and load whatever leak or rom you want you should be set. Understanding what is going on is key. This is a decision you are making to alter your phone for your benefit. Take the time to download SDK and whatever else is needed for your computer. Become familiar with what shell is and how to get there as well as explore within it. If you can get shell down and how to access your su and run commands, you should know enough to start. There are many things you need to research in order to be confident in what you are doing. I am sure you will not have a problem, just putting the time in to figure out everything is key. This is what I had to do.
I think that this is the best advice I can give you. None of us can know exactly what you are doing so you need to know the processes and choose which one is going to work for your circumstance. Good luck and if you have anymore problems I am sure all of us on xda can figure out a solution for you.
ok, finally, with a little help i got my phone rerooted and back to normal. learned a lot in the process too. thanks to all...
Originally posted by Stetsonaw at androidforums...
Please be aware that I did not write these instructions. I only posted them. Stetsonaw wrote these instructions. While comfortable in ADB and have rooted my phone many times in testing as well as rolled back the versions etc... I have no more insight into how or why it is not working for you. If you followed the directions exactly on a version 4 phone, this should work no problem.
Haxcid
Links to the necessary files are listed at the bottom.
Remember, I am not at fault if you brick your phone, now, proceed.
Connect your phone in charge only mode to install the LG Bootstrapper and drivers, or grab the LG Universal Drivers.
Change your USB Mode to Internet Connection
Go into Settings/Applications/Development and ensure USB Debugging is turned on
If all goes according to plan, you should see the ADB Ladybug icon in your notification bar
I updated the Rootzwiki page with the same info found below.
Busybox actually comes installed by LG on the Revo, how awesome is that??
Download the rageagainstthecage binary
Download the SU binary
Move these files to the same directory your adb.exe is in.
Code:
The > and # characters below illustrate the prompt
you should have, if you have the $ when you go into adb shell,
exit out and type 'adb usb' then go back into adb shell and
you should see the #
Open Command prompt (either use the Windows Key+R and type cmd or start/run, then type cmd)
32-bit users: >cd c:\program files\android\android-sdk\platform-tools
64-bit users: >cd c:\program files (x86)\android\android-sdk\platform-tools
Or >cd (whatever directory adb is in)
>adb devices (verifies you are connected)
>adb push rageagainstthecage-arm5.bin /data/local/temp/rage
(if the above command fails due to read-only, type 'adb usb' then 'adb root' to validate root status, then 'adb devices' again to verify connection)
>adb push su /data/local/temp/su
>adb shell chmod 777 /data/local/temp/rage
>adb shell ./data/local/temp/rage
>adb shell (If this gives you a $ prompt instead of a # prompt, type 'su', if that fails, 'exit', 'adb usb' like above.)
#mount -o remount,rw -t ext3 /dev/mmcblk0p12 /system
#busybox cp /data/local/temp/su /system/bin/su
#chmod 6755 /system/bin/su
Verify the file is in place w/correct permissions
#cd /system/bin
#ls -l *su
After the ls command you should see the following returned by the system:
-rwsr-sr-x root root 26248 2011-05-29 01:09 su
At this point, you may way to remove the files you put in /data/local/temp (optional):
#rm /data/local/temp/su
#rm /data/local/temp/rage
continue with commands
#reboot
Download and install SuperUser from the Market
Thanks Zennmaster, _mrbirdman_ for finding the linux routes and birdman for helping me out, and droidx8971 for helping me find all the information possible!
http://wikifilez.com/Root Files/revolution/rageagainstthecage-arm5.bin
http://wikifilez.com/Root Files/revolution/su
https://market.android.com/details?id=com.noshufou.android.su&feature=search_result
http://www.lg.com/us/support/mc-support/drivers/LGAndroidDriver_Ver_1.0_All.exe
Just a note for some. The rageagainstthecage bin file may be detected as a virus/trojan. It is not. You may want to disable your antivirus before downloading the .bin file.
I run avira on my desktop and it caught the file as a virus everytime I downloaded it and then deleted it. Avast on my laptop however did not.
Root is simple if you follow the instructions. You need to make sure that adb recognizes your device. Takes 5 minutes to complete, took me longer to install adb again and update it.
Any reason to not use the one click method? Seems to be working
bwhxeon said:
Any reason to not use the one click method? Seems to be working
Click to expand...
Click to collapse
No idea. I have not used the one click. Create a thread for it. I posted what I know which is adb.
Successfully Rooted
with RootzWiki instructions for Windows, needed the remount and busybox lines to overcome the permission denied when pushing su.
Hey guys, either using S1C or ADB Commands, have we found out if it's possible to unroot this as long as you Nand Backup the stock rom then unroot from there yet? Just because I got this phone as a filler/4g unl. lock and got buyback on it from best buy so I could buy a dual/quad later on when they come out .
MXFrodo195 said:
Hey guys, either using S1C or ADB Commands, have we found out if it's possible to unroot this as long as you Nand Backup the stock rom then unroot from there yet? Just because I got this phone as a filler/4g unl. lock and got buyback on it from best buy so I could buy a dual/quad later on when they come out .
Click to expand...
Click to collapse
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Haxcid said:
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Click to expand...
Click to collapse
Oh ya I know, I just always keep a stock one, on the Inc if you factory reset from an AOSP rom, you'd bootloop, so you had to make sure you were on a Sense 1.0 or stock rom(from my experience), so I was just making sure it was no big deal to go back.
Any idea when we will have cw on this?
Haxcid said:
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Click to expand...
Click to collapse
I tried the factory reset. I am still rooted.
navycow said:
I tried the factory reset. I am still rooted.
Click to expand...
Click to collapse
That's what i figured. Can anyone verify if you remove SU and Rage through adb will it unroot?
Sent from my VS910 4G using XDA Premium App
MXFrodo195 said:
That's what i figured. Can anyone verify if you remove SU and Rage through adb will it unroot?
Sent from my VS910 4G using XDA Premium App
Click to expand...
Click to collapse
If you have to return your device, simply remove the superuser app, after you unfreeze anything you may have frozen then factory reset. They honestly will never know it was rooted. The only way now that you can really tell is the super user app from market.
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
navycow said:
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
Click to expand...
Click to collapse
Thank you for confirming this. My revolution just came in the mail today!
Thanks for posting this here for me Haxcid!
Sent from 1885
navycow said:
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
Click to expand...
Click to collapse
Cool thanks for checking. Any benefits for ADB over S1C? Can't wait to finally root and freeze half these apps. I think we need a few more twitters to praise koush for a recovery on this beast.
Sent from my VS910 4G using XDA Premium App
Is there recovery for this now? Did I miss something?
stetsonaw said:
Is there recovery for this now? Did I miss something?
Click to expand...
Click to collapse
No No, I was saying we need to praise Koush's good work so he will make one faster .
And Stetsonaw, any idea if I root through ADB, can I unroot with S1C, since it uses the same idea.
S1C for whatever reason will not run(tried three computers, a XP, Vista, and Win7 lol), it keeps freezing at the same spot, everytime.
Should be able to, since S1C does what the ADB method does... or you could just delete the 'su' file out of /system/bin and /system/xbin (if it's there) to unroot.
EDIT: I couldn't get S1C to open on my desktop, and my laptop, which would open the program, would bluescreen when i connected the phone, so i had no choice but to do it the ADB way.
stetsonaw said:
Should be able to, since S1C does what the ADB method does... or you could just delete the 'su' file out of /system/bin and /system/xbin (if it's there) to unroot.
EDIT: I couldn't get S1C to open on my desktop, and my laptop, which would open the program, would bluescreen when i connected the phone, so i had no choice but to do it the ADB way.
Click to expand...
Click to collapse
Hmmm, ya now my computer for whatever reason won't open up ADB through command. This is getting irritating lol. Should be nice and simple, but it just won't go through. If I downloaded the SDK Manager like 4 months ago, it shouldn't matter, correct?
make sure you change directory to wherever your adb.exe is located... as in:
Code:
cd C:\Program Files\Android\android-sdk-windows\platform-tools
Im trying to root my moto x with RockMyDroid and when i try the telnet command with the cydia impactor i get an error message reading : Link failed file exists.... any suggestions?
Did you ever sort this out?
im also getting same issue and the threads for rock my moto slapy my moto have been un responsive for any info . so your not the only one
teddy2122 said:
Im trying to root my moto x with RockMyDroid and when i try the telnet command with the cydia impactor i get an error message reading : Link failed file exists.... any suggestions?
Click to expand...
Click to collapse
bump...
Same for me. I've been struggling for 3 days with no luck. Everything goes well until "telnet {my moto x ip} 2222" in Impactor. "Link Failed file exists"
Someone help!
clevertrevor777 said:
bump...
Same for me. I've been struggling for 3 days with no luck. Everything goes well until "telnet {my moto x ip} 2222" in Impactor. "Link Failed file exists"
Someone help!
Click to expand...
Click to collapse
Are you using the cydia impactor correctly? I had this issue because i was trying to use the "telnet {ip} 2222" command in the impactor instead of the command prompt. to do it correctly:
open the impactor
use the drop down menu on the impactor, choose "# start telnetd as system on port 2222"
Hit start
when that has completed, Open up a new command prompt window and type telnet {ip} 2222"
you should now be connected
Let me know if this helped! :good:
Unlock your phone or disable the key guard before starting Impactor
Link Failed file exists - SOLVED
teddy2122 said:
Im trying to root my moto x with RockMyDroid and when i try the telnet command with the cydia impactor i get an error message reading : Link failed file exists.... any suggestions?
Click to expand...
Click to collapse
I fell your pain. I struggled with the same error. When I figured it out I felt like an idiot. After you open the telnet session in Cydia Impactor, move over to the command prompt to run "telnet {device ip} 2222". I assume you attempted to run this in Cydia Impactor as well.
teddy2122 said:
Are you using the cydia impactor correctly? I had this issue because i was trying to use the "telnet {ip} 2222" command in the impactor instead of the command prompt. to do it correctly:
open the impactor
use the drop down menu on the impactor, choose "# start telnetd as system on port 2222"
Hit start
when that has completed, Open up a new command prompt window and type telnet {ip} 2222"
you should now be connected
Let me know if this helped! :good:
Click to expand...
Click to collapse
A buddy just showed me the solution... You were exactly correct. Also, for anyone else in the same situation, also ensure that telnet is activated in windows.
CONTROL PANEL -> PROGRAMS AND FEATURES -> TURN WINDOWS FEATURES ON OR OFF -> SCROLL DOWN AND CHECK THE TELNET CLIENT BOX
Hopefully that helps someone out there. Happy rooting!
Mine was active, but its not longer working. I was able to root earlier but its not working now stating that the file exists already. and when I try using puttytel it tells me that:
~ $ dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
RockMyMoto 1.0
by Justin Case
PayPal Donations maybe sent to: [email protected]
Special thanks to saurik, you rock!
System is not write protected...
Executing step 3...
~ $
and thats as far as I can go. And I check root, nothing, i check SU nothing, nothing is working (
Vahnyyz said:
Mine was active, but its not longer working. I was able to root earlier but its not working now stating that the file exists already. and when I try using puttytel it tells me that:
~ $ dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
RockMyMoto 1.0
by Justin Case
PayPal Donations maybe sent to: [email protected]
Special thanks to saurik, you rock!
System is not write protected...
Executing step 3...
~ $
and thats as far as I can go. And I check root, nothing, i check SU nothing, nothing is working (
Click to expand...
Click to collapse
You can buy an unlock code again for the bootloader. I'd get on it quick tho, before it ends again.
Then you can root easily, without all the exploits.
kj2112 said:
You can buy an unlock code again for the bootloader. I'd get on it quick tho, before it ends again.
Then you can root easily, without all the exploits.
Click to expand...
Click to collapse
I'm sorry I must have not stated it before, I'm currently on Republic Wireless, unless they do unlock codes I don't think I'll be able to do that... but if I am, I'm totally willing to do that asap if you let me know where and how lol
Vahnyyz said:
I'm sorry I must have not stated it before, I'm currently on Republic Wireless, unless they do unlock codes I don't think I'll be able to do that... but if I am, I'm totally willing to do that asap if you let me know where and how lol
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2751177
Read through here or ask about it here.
Hopefully it can work for you.
I can push files but telnet doesnt want to run them or something.
ERROR MESSAGE:
"dalvik vm unable to locate class 'rockmymoto'.
I dont think I could be anymore drained and pissed off right now. I'm trying to get 4.4 rooted. It's been SIX HOURS so far. Not sure whats wrong. I've seen that other people have had the problem and there solutions don't fix my problem.
I've reinstalled everything, drivers sdk/adb, java, motorola device drivers, etc multiple times.
I have rsdlite'd back to 4.2.2 camera update
installed motorola mobility drivers (phone says "mot composite adb device" under device manager)
I run adb and do an "adb devices" and my device shows up.
I run a adb push rockmymoto.jar /sdcard/ and also SU
I reboot
the files show up
I connect to 2222 with cylmida (*sp) impactor
obtained my ip address,
ran telnet and connected
but when I do the dalvikvm -cp /sdcard/rockmymoto.jar rockmymoto command
I get teh #$^*$# error that says "dalvik vm unable to locate class 'rockmymoto'.
#&($#& YOU MACHINE!!!!!!!!!!!!
Any idea what I am doing wrong? I have unauthorized apps installation enabled. I have usb debugging enabled. ????
If you're trying to root 4.4, I think you need to be using slapmymoto.
Sent from my XT1060 using Tapatalk
MikeG7265 said:
If you're trying to root 4.4, I think you need to be using slapmymoto.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Thanks but I'm trying to root 4.2.2 and then go to 4.4. To do that I need rock and motowpnomodofrodo. then slappy
I'm still stuck with the same dalvikvm error like it cant find the rock and su even though it was pushed with ADB. I've spent WAY too much time trying to get this working. I even had to dig out the old wireless router. and YES AP is off in my router.
Possibly an issue with case sensitivity?
nhizzat said:
Possibly an issue with case sensitivity?
Click to expand...
Click to collapse
OMG that was it. THANK YOU! The next thing I ran into was the math problem that RockmyMoto gave me. It was: a/50=? ....WTF. Thankfully i reran rock and it asked me a real math question.
I have rooted my phone successfully, and in the beginning apps that required root access would check for root, and request su access, but now that doesn't happen.
1. Anyone know what happened, and how do I get applications to request root access again?
2. How do I update the SuperSU binary, when it asks?
Rooted using SlapMyMoto, on Android 4.4 Stock.
Make sure you have the latest supersu from the play store but when it asks you to update the SU binary, it should show two options, normal and twrp, since i'm assuming you're locked (plus it's just easier), choose normal. Also, i'm not sure what the process is, but you might need to re-run whatever it is that you use to root (i'm unlocked so i'm not familiar with the process) because it sounds like you don't have system mounted as rw. If this is the result of an OTA, because people are losing rw from taking the verizon OTA, you might be out of luck until a new method is found.
-edit- another fix might be to re flash supersu if you have safestrap installed, and just clarification, it will not ask for root for the same app twice unless you tell it to ask again next prompt.
StATicxTW0T said:
Make sure you have the latest supersu from the play store but when it asks you to update the SU binary, it should show two options, normal and twrp, since i'm assuming you're locked (plus it's just easier), choose normal. Also, i'm not sure what the process is, but you might need to re-run whatever it is that you use to root (i'm unlocked so i'm not familiar with the process) because it sounds like you don't have system mounted as rw. If this is the result of an OTA, because people are losing rw from taking the verizon OTA, you might be out of luck until a new method is found.
-edit- another fix might be to re flash supersu if you have safestrap installed, and just clarification, it will not ask for root for the same app twice unless you tell it to ask again next prompt.
Click to expand...
Click to collapse
Thanks for the reply. I took the OTA to 4.4 from 4.2, and I was still rooted. Something happened with SuperSU, and now the phone is behaving as if it is not rooted, or it's half rooted (if that makes sense).
MyBackupPro would always ask for root access, and then SuperSU would grant it automatically. Now this doesn't happen. Also, I'm trying to use Helium backup as well, and when it tries to ask for root access, it fails. Any app that usually requests root access doesn't even ask.
Thanks.
akhenax said:
Thanks.
Click to expand...
Click to collapse
I wouldn't take my word for it, but i remember reading about a downgrade then upgrade process where you would downgrade to 4.2.2 post cam then root then upgrade again, it might help, no guarantee's though.
StATicxTW0T said:
I wouldn't take my word for it, but i remember reading about a downgrade then upgrade process where you would downgrade to 4.2.2 post cam then root then upgrade again, it might help, no guarantee's though.
Click to expand...
Click to collapse
I always thank replies whether it helps or not.
I am trying to retrace the steps I did to root, but not the entire process. Hope to save time from having to redo everything again.
I fixed it.
I did the following steps (not sure if this did anything but...):
uninstall SuperSU
adb reboot bootloader
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot reboot
adb push su /data/local/tmp/su
adb push install.sh /data/local/tmp/install.sh
adb push rec.sh /data/local/tmp/rec.sh
adb push install-recovery.sh /data/local/tmp/install-recovery.sh
adb push setup.sh /data/local/tmp/setup.sh
adb reboot
adb shell
echo "/data/local/tmp/rec.sh" > /sys/kernel/uevent_helper
<-- THIS FAILS, as expected. It worked when I first rooted the device, but doesn't work any longer, but this is OK.
it returns: /system/bin/sh: can't create /sys/kernel/uevent_helper: Permission denied
Once again, this is OK.
Install SuperSU
DO NOT OPEN IT. JUST INSTALL IT.
Apps now request root permission.
adb shell getprop ro.boot.write_protect
returns a value of:1 which means my bootloader is locked write protection is enabled, but I still have proper root access.
Hope this helps the next guy.
akhenax said:
adb shell getprop ro.boot.write_protect
returns a value of:1 which means my bootloader is locked, but I still have proper root access.
Click to expand...
Click to collapse
This actually means that write protection is enabled.
Did you try to reboot into"recovery" to set write protection off?
nhizzat said:
Did you try to reboot into"recovery" to set write protection off?
Click to expand...
Click to collapse
I don't think I'm versed enough in this to answer this question accurately, for the very reason you quoted "recovery". How would you accomplish such a feat, step by step?
akhenax said:
I don't think I'm versed enough in this to answer this question accurately, for the very reason you quoted "recovery". How would you accomplish such a feat, step by step?
Click to expand...
Click to collapse
power down, hold volume down and power, youll get a black screen with blue letters. use volume down button to naviagte and power to select.
xpsychox said:
power down, hold volume down and power, youll get a black screen with blue letters. use volume down button to naviagte and power to select.
Click to expand...
Click to collapse
The question was: Did you try to reboot into"recovery" to set write protection off?
Do your steps allow one to do this?
akhenax said:
The question was: Did you try to reboot into"recovery" to set write protection off?
Do your steps allow one to do this?
Click to expand...
Click to collapse
ahh, my bad miss read it.. lol... oops
akhenax said:
I don't think I'm versed enough in this to answer this question accurately, for the very reason you quoted "recovery". How would you accomplish such a feat, step by step?
Click to expand...
Click to collapse
When in Android, connect the phone to your PC USB port. I hope you've already installed the Android SDK and Moto drivers. Open a cmd prompt with admin privileges and type "adb devices" to check if your PC recognizes the phone. If so, then type "adb reboot recovery". The phone will reboot just as it normally would, only this time write protection is off. Or do the steps below or type "adb reboot bootloader".
xpsychox said:
power down, hold volume down and power, youll get a black screen with blue letters. use volume down button to naviagte and power to select.
Click to expand...
Click to collapse
Volume up to select, actually.