So i just tried to run the new RockMyMoto exploit for the Moto x after the camera update and when i get to the point of running the command line dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto, the line runs and it says "System is not write protected... Executing step 3..." now i'm assuming this is because i have a Dev Edition moto x, but the problem is that nothing actually happens. I'm assuming that the RockMyMoto figures it's already gotten past the write protection and just needs to install superuser. But it doesn't, my phone isn't rooted and supersu doesn't work. anyone got a way around this?
Unlock you bootloader.
shane1 said:
Unlock you bootloader.
Click to expand...
Click to collapse
should've been more clear, my bootloader is unlocked
calumnium said:
should've been more clear, my bootloader is unlocked
Click to expand...
Click to collapse
Then you don't have to do any of this, just adb push su, install supersu and your good... That's the benefit of having an unlocked bootloader... This method is for those of us with locked bootloaders.
Sent from my XT1058 using XDA Premium 4 mobile app
theraffman said:
Then you don't have to do any of this, just adb push su, install supersu and your good... That's the benefit of having an unlocked bootloader... This method is for those of us with locked bootloaders.
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
where should i push it to? i have it pushed to sdcard. also what's the adb command line to install?
system/apps
theraffman said:
Then you don't have to do any of this, just adb push su, install supersu and your good... That's the benefit of having an unlocked bootloader... This method is for those of us with locked bootloaders.
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't think that's quite true--I have the same problem: Droid Maxx DE, unlocked bootloader. and it says "System is not write protected... Executing step 3..."
Writing su to /system/app is not useful. It eventually needs to be written to the path, /system/bin or /system/xbin, but /system is mounted ro...
---------- Post added at 04:37 AM ---------- Previous post was at 04:36 AM ----------
theraffman said:
Then you don't have to do any of this, just adb push su, install supersu and your good... That's the benefit of having an unlocked bootloader... This method is for those of us with locked bootloaders.
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't think that's quite true--I have the same problem: Droid Maxx DE, unlocked bootloader. and it says "System is not write protected... Executing step 3..."
Writing su to /system/app is not useful. It eventually needs to be written to the path, /system/bin or /system/xbin, but /system is mounted ro...
Same issues...anyone please advise? much appreciated...went through all this stuff, got BL unlocked...Now I want root. I am on the first OTA .57 update and getting same errors as stated above. really want to root, recovery and flash this beast! please help!
Bump
Sent from my XT1055 using XDA Premium 4 mobile app
If your boot loader is already unlocked you don't need RockMyMoto....
If you have an unlocked X you can root it doing the following.
1) install twrp recovery
.....a) fastboot flash recovery twrp263.img
2) reboot phone to recovery
3) install su
.....a) mount system in recovery
.....b) adb push su /system/xbin/su
.....c) adb shell chmod 4755 /system/xbin/su
4) reboot device
needed file www.teamblackhat.net/Downloads/su.zip
Click to expand...
Click to collapse
Source: Matthew Pierce on Google+ -> https://plus.google.com/110773150384694258853/posts/6VickA48Ryq
KidJoe said:
If your boot loader is already unlocked you don't need RockMyMoto....
Source: Matthew Pierce on Google+ -> https://plus.google.com/110773150384694258853/posts/6VickA48Ryq
Click to expand...
Click to collapse
but I have updated OTA the camera update which has issues rooting apparently I read. I cant find the twrp263.img download either... any help is much appreciated thanks :good:
A2Trip said:
but I have updated OTA the camera update which has issues rooting apparently I read. I cant find the twrp263.img download either... any help is much appreciated thanks :good:
Click to expand...
Click to collapse
twrp263.img see -> http://forum.xda-developers.com/showthread.php?t=2458449 but you might have to go to post #63 to find a working link
As far as I know, this works both pre and post camera update OTA.
I just got this phone and unfortunately didn't get the developer edition. I am using the "Towel Pie Root" made by a developer here on XDA and got temporary root. So under this temporary root is it possible to flash a recovery and if it is, is it possible to then flash ROMs with the recovery? Thanks in advance!
Sent from my XT1058 using XDA Premium 4 mobile app
You have to have a unlocked bootloader to use twrp. If you are locked down look into safestrap.
Travisdroidx2 said:
You have to have a unlocked bootloader to use twrp. If you are locked down look into safestrap.
Click to expand...
Click to collapse
Alright thanks. I'll look into that tomorrow.
Sent from my XT1058 using XDA Premium 4 mobile app
procitysam said:
I just got this phone and unfortunately didn't get the developer edition. I am using the "Towel Pie Root" made by a developer here on XDA and got temporary root. So under this temporary root is it possible to flash a recovery and if it is, is it possible to then flash ROMs with the recovery? Thanks in advance!
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
When the bootloader on the X is locked, you can only flash components which are signed by Motorola's "digital key" as being for your phone. So you can only flash an entire rom, or parts of it, which are for your phone.
This prevents using 3rd party or custom recoveries, custom roms, etc. as they are not signed by Motorola's key.
PIE, TowelRoot, TowelPieRoot, SlapMyMoto, RockMyMoto, MotoWPNoMo, etc. does NOT allow for bypassing this.
Only unlocking your bootloader will allow you to use parts not signed by moto, like custom recoveries, 3rd party roms, etc.
My thought is that you are on 4.4.2 because you have used TowelPieRoot. Is that correct?
@Travisdroidx2 suggested SafeStrap, but to install/use Safestrap you need to be rooted and have write protection disabled. Unfortunately, on the Moto X, the MotoWpNoMo exploit was used to disable write protection if you can't unlock your bootloader, BUT the vulnerability in the bootloader that was exploited by MotoWpNoMo has been patched in 4.4.2 ROM and above. So you can't use it on 4.4.2, 4.4.3, and 4.4.4. You can't downgrade the bootloader either. In fact, once on 4.4.2 or above, NEVER try to downgrade your ROM, as you could brick your phone!!
i.e. If you have a locked bootloader and are on 4.4.2 or above, you can't disable write protection, and you can't downgrade your phone safely. If you do try, you can't downgrade Motoboot.img (bootloader and a couple of other things), and GPT.BIN (partition table). which can brick your phone and cause other problems.
However, if you were on 4.4 (aka 4.4.0) with its vulnerable bootloader, you could use SlapMyMoto with MotoWpNoMo to root and disable write protection, then use Safestrap to install 4.4.2 and 4.4.4, and retain root and write protection disable.
KidJoe said:
When the bootloader on the X is locked, you can only flash components which are signed by Motorola's "digital key" as being for your phone. So you can only flash an entire rom, or parts of it, which are for your phone.
This prevents using 3rd party or custom recoveries, custom roms, etc. as they are not signed by Motorola's key.
PIE, TowelRoot, TowelPieRoot, SlapMyMoto, RockMyMoto, MotoWPNoMo, etc. does NOT allow for bypassing this.
Only unlocking your bootloader will allow you to use parts not signed by moto, like custom recoveries, 3rd party roms, etc.
My thought is that you are on 4.4.2 because you have used TowelPieRoot. Is that correct?
@Travisdroidx2 suggested SafeStrap, but to install/use Safestrap you need to be rooted and have write protection disabled. Unfortunately, on the Moto X, the MotoWpNoMo exploit was used to disable write protection if you can't unlock your bootloader, BUT the vulnerability in the bootloader that was exploited by MotoWpNoMo has been patched in 4.4.2 ROM and above. So you can't use it on 4.4.2, 4.4.3, and 4.4.4. You can't downgrade the bootloader either. In fact, once on 4.4.2 or above, NEVER try to downgrade your ROM, as you could brick your phone!!
i.e. If you have a locked bootloader and are on 4.4.2 or above, you can't disable write protection, and you can't downgrade your phone safely. If you do try, you can't downgrade Motoboot.img (bootloader and a couple of other things), and GPT.BIN (partition table). which can brick your phone and cause other problems.
However, if you were on 4.4 (aka 4.4.0) with its vulnerable bootloader, you could use SlapMyMoto with MotoWpNoMo to root and disable write protection, then use Safestrap to install 4.4.2 and 4.4.4, and retain root and write protection disable.
Click to expand...
Click to collapse
Yes that's correct that I'm on 4.4.2. Thank you for clearing that up, everything I looked at was confusing. So my last question is Towel Pie Root can only be used for root access apps?
Sent from my XT1058 using XDA Premium 4 mobile app
procitysam said:
Yes that's correct that I'm on 4.4.2. Thank you for clearing that up, everything I looked at was confusing. So my last question is Towel Pie Root can only be used for root access apps?
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sort of.
TowelPieRoot provides READ access to protected folders that you can't touch/see without root permissions. So apps like Root Explorer and the like which don't need to WRITE files in /system and such will be fine.
Apps like AdFree, Xposed, and other things that need to write in /system either wont install, or will need an alternate install process. (Xposed does have a way to install without write permissions).
And of course, any changes done to the write protected folders will be lost at power off/on or "hard boot." This poses a challenge for many when installing Xposed, as they do a normal reboot after install which is a "hard boot" and they lose root and xposed and have to start all over. There is a "soft boot" option that can be used when installing xposed.
Note: I have an unlocked bootloader so I've only read about the challenges of installing Xposed and others who use PIE, Towel ROot, and TowelPieRoot and still have write protection enabled. So you'll really want to read those threads that deal with the ROOT app you want to use, or the root method you are using, to find the details of what can/can't be done.
KidJoe said:
Sort of.
TowelPieRoot provides READ access to protected folders that you can't touch/see without root permissions. So apps like Root Explorer and the like which don't need to WRITE files in /system and such will be fine.
Apps like AdFree, Xposed, and other things that need to write in /system either wont install, or will need an alternate install process. (Xposed does have a way to install without write permissions).
And of course, any changes done to the write protected folders will be lost at power off/on or "hard boot." This poses a challenge for many when installing Xposed, as they do a normal reboot after install which is a "hard boot" and they lose root and xposed and have to start all over. There is a "soft boot" option that can be used when installing xposed.
Note: I have an unlocked bootloader so I've only read about the challenges of installing Xposed and others who use PIE, Towel ROot, and TowelPieRoot and still have write protection enabled. So you'll really want to read those threads that deal with the ROOT app you want to use, or the root method you are using, to find the details of what can/can't be done.
Click to expand...
Click to collapse
Awesome explanation thanks. The app has the option to re-root after a reboot so that shouldn't be a problem. Thanks so much for helping!
Sent from my XT1058 using XDA Premium 4 mobile app
procitysam said:
Awesome explanation thanks. The app has the option to re-root after a reboot so that shouldn't be a problem. Thanks so much for helping!
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sure, re-root after reboot... BUT any changes you made to the write protected folders while would still be lost and have to be redone after a power off/on or "hard boot".
KidJoe said:
When the bootloader on the X is locked, you can only flash components which are signed by Motorola's "digital key" as being for your phone. So you can only flash an entire rom, or parts of it, which are for your phone.
This prevents using 3rd party or custom recoveries, custom roms, etc. as they are not signed by Motorola's key.
PIE, TowelRoot, TowelPieRoot, SlapMyMoto, RockMyMoto, MotoWPNoMo, etc. does NOT allow for bypassing this.
Only unlocking your bootloader will allow you to use parts not signed by moto, like custom recoveries, 3rd party roms, etc.
My thought is that you are on 4.4.2 because you have used TowelPieRoot. Is that correct?
@Travisdroidx2 suggested SafeStrap, but to install/use Safestrap you need to be rooted and have write protection disabled. Unfortunately, on the Moto X, the MotoWpNoMo exploit was used to disable write protection if you can't unlock your bootloader, BUT the vulnerability in the bootloader that was exploited by MotoWpNoMo has been patched in 4.4.2 ROM and above. So you can't use it on 4.4.2, 4.4.3, and 4.4.4. You can't downgrade the bootloader either. In fact, once on 4.4.2 or above, NEVER try to downgrade your ROM, as you could brick your phone!!
i.e. If you have a locked bootloader and are on 4.4.2 or above, you can't disable write protection, and you can't downgrade your phone safely. If you do try, you can't downgrade Motoboot.img (bootloader and a couple of other things), and GPT.BIN (partition table). which can brick your phone and cause other problems.
However, if you were on 4.4 (aka 4.4.0) with its vulnerable bootloader, you could use SlapMyMoto with MotoWpNoMo to root and disable write protection, then use Safestrap to install 4.4.2 and 4.4.4, and retain root and write protection disable.
Click to expand...
Click to collapse
Thanks for the info. I have a Dev edition so never used safestrap myself. I just know it was a option for locked down phones. Thanks for the clarification.
When using the Towel Pie Root app, do you need Superuser installed as well? And if so do you or don't you need the su binary installed?
Hey,
I have previously rooted my ATT xt1058. At one point I had to reset the ROM back to stock. Now, when trying to run RockMyMoto or SlapMyMoto using the official root guides, I am faced with an error. On both root methods, when running "dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto" (or RockMyMoto, I tried both) I am immediately sent to Step 3, and told that my system is not write protected.
ADB confirms that my system is not write protected, however I cannot modify files in /sys/kernel, as SlapMyMoto requires.
I'm unsure of why this is happening, any help fixing it would be appreciated.
Thanks!
Notes about previous root:
I do not have an unlocked bootloader, my bootloader has never been unlocked. I used the SlapMyMoto root guide (from this reddit post) to gain root. Due to an issue with my play store and the volume buttons on my device, I was forced to reset to stock 4.2.2 post-camera, and I stayed there for a while. Now, attempting to root back, I am running into these problems.
Hi,can anyone tell me i have rooted my droid turbo at su4tl-49 using kingroot.
It has full root access.
Can some one tell me if i use root explorer and make kingroot a system file will the root will be permanant or bricked.
I also want to ask that if i edit build.prop or any other file using root explorer will it be brick unless its safe file?
Unless you have unlocked your bootloader, what you are doing is not safe.
bilalrajput said:
Hi,can anyone tell me i have rooted my droid turbo at su4tl-49 using kingroot.
It has full root access.
Can some one tell me if i use root explorer and make kingroot a system file will the root will be permanant or bricked.
I also want to ask that if i edit build.prop or any other file using root explorer will it be brick unless its safe file?
Click to expand...
Click to collapse
Unlock Bootloader, then root with SuperSU, SAFEST bet. Along with TWRP
mac.os.x said:
Unlock Bootloader, then root with SuperSU, SAFEST bet. Along with TWRP
Click to expand...
Click to collapse
He has said repeatedly he doesn't want to do that. He refuses to pay for Sunshine. So, he keeps trying to find a way without unlocking his bootloader (paying money), which we have advised against.
He regains temp root with King Root every time he reboots. He wants our permission to make major system changes, so when he bricks his phone it's not his fault. King Root itself will often mess up your system.
ChazzMatt said:
He has said repeatedly he doesn't want to do that. He refuses to pay for Sunshine. So, he keeps trying to find a way without unlocking his bootloader (paying money), which we have advised against.
He regains temp root with King Root every time he reboots. He wants our permission to make major system changes, so when he bricks his phone it's not his fault. King Root itself will often mess up your system.
Click to expand...
Click to collapse
I agree about KingRoot. What's the deal, I spent I don't remember but like 20 something for sunshine, unless he's a kid he should have the $ to be honest I don't mind paying if there's not a definite free way of anything.
Sent from my DROID Turbo using XDA-Developers mobile app