628 replies to this topic

[beefytr]

could not help updating to 9.20.1 verison and now the rooting via motochopper does not pay.

do we expect some root method soon or is there any alternative to walk around and cheat the gadget?

many thanks

Edited by livinginkaos, 16 September 2013 - 04:51 AM.
Removed OP Quote

[livinginkaos]

could not help updating to 9.20.1 verison and now the rooting via motochopper does not pay.

do we expect some root method soon or is there any alternative to walk around and cheat the gadget?

many thanks

This method will work on the 9.20.1 version as well

[justtjb]

I was having a problem with this, and I simply added a -r to line 85 of the batch fole, to make it read thusly:

 

adb install -r Superuser.apk

 

I will also note that I could not in any case get anything to work in MTP mode - adb simply would not communicate with the phone in that mode.  I had to switch to camera mode to get it to talk.  At the end of all the permutations, I ended up with success in Camera mode, and allowing mock locations.

 

Thanks for the work on this!!!

[corecowcoyboy]

So I was able to root (DROID RAZR M 98.16.3.XT907.Verizon.en.US), used adb shell as root and remount /system directory to change the files I wanted.

 

Now that I'm done, what is required to properly 'unroot' my phone? I would not like it to 'brick' next update.

 

One thing I noticed when I ran the bat file and the phone rebooted that a number of applications began to update. Is this normal?

[livinginkaos]

There areva couple of ways to unroot. There is Mattlgroff's unroot tool in the play store, you can flash the FXZ or you can simply flash the system partition with the system.img.

From My S4 Dev Edition

[msimmons]

OP updated with motochopper 1.2.  It now includes an updated script for Mac/Linux (thanks tECHIDNA and LivingInKaos).  It now has the ability to help those where the script fails due to old remnants of su kicking around on the system partition.  Just drop the system.img.ext4 file from the FXZ in the system dir and it'll flash it for you as part of the process to give you a clean start on rooting.

 

I think old remnants of su is my problem, but I don't fully understand what you are saying to do. What system dir? I wouldn't say I'm a newbie, but as a windows dev, android is a little bit of a different environment than I am used to.

 

Here is what happens when I run the batch file. I have [re]downloaded the usb drivers, am using the stock cable, and the post is 2.0.

 

Please Login or Register to see this Hidden Content

 

(I can also get it to not fail on installing Superuser.apk by uninstalling SuperSU before running the batch file.) Once I've run the bat, I go to open SuperSU and receive a popup "The SU binary needs to be updated, continue?" When I hit ok, I get a second box asking for "normal" or "twrp/cwm," since I don't know what that is, I assume normal but that results in an "install failed" (and the other doesn't appear to do anything). 

 

I believe my boot loader is unlocked (since it warns me on every boot).

 

All I want to do is let tasker turn my GPS on and off

 

Droid razr hd - 9.18.79.xt926.Verizon.en.US

[SamuriHL]

If you're unlocked you shouldn't be using this method as it's for locked phones.  If you're truly unlocked, install TWRP recovery and use that to flash the supersu zip from chainfire.

[msimmons]

If you're unlocked you shouldn't be using this method as it's for locked phones.  If you're truly unlocked, install TWRP recovery and use that to flash the supersu zip from chainfire.

I don't see a TWRP download for razr. 

Please Login or Register to see this Hidden Content

 

(Spoke too soon, working on this now: 

Please Login or Register to see this Hidden Content

 )

 

Edit:

I'm up and running again! thanks a ton!

(Using the code in the batch file in the OP, I figured out how to flash the twrp I found in the link above. Then I downloaded the supersu.zip and installed that via twrp. Once that was done, I was able to get SecureSettings to work as it did before)

[cmh714]

I believe that is rather old. Look here:

Please Login or Register to see this Hidden Content

 

post #254 tells you how to replace the recoveries with the latest using Tucstwo's tool

[msimmons]

I believe that is rather old. Look here:

Please Login or Register to see this Hidden Content

 

post #254 tells you how to replace the recoveries with the latest using Tucstwo's tool

Thanks! I'll run this later. (As mad as I was at Verizon/Motorola for making me have to do all this extra work, I have to admit, I've learned a lot about my phone ) 

[PFreeman008]

Thanks for the hack, it's gotten me further then any other exploit. However I still can't seem to get root. I'm running XT926

 

This is what happens. It seems to be returning with an failed status of e00002ed. I've followed all the instructions that the OP has posted, just shy of the adding of the system.img.ext4 files as I don't know where to get this file.

[*] Waiting for device...

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

[*] Device found.

[*] Rebooting to AP Fastboot mode...

[*] Checking for system.img or system.img.ext4...

[*] Flashing old boot.img

< waiting for device >

(bootloader) Variable not supported!

target reported max download size of 31457280 bytes

sending 'boot' (10240 KB)...

OKAY [  0.768s]

writing 'boot'...

ERROR: usb_read failed with status e00002ed

FAILED (status read failed (Operation timed out))

finished. total time: 0.976s

[*] Rebooting...

ERROR: could not clear input pipe; result e00002ed, ignoring...

ERROR: could not clear output pipe; result e00002ed, ignoring....

rebooting...

ERROR: usb_write failed with status e00002ed

 

finished. total time: 0.000s

 

peter

[SamuriHL]

You've got some interesting issues.  I'm going by gut feel on this but I'd say you got platform tools in the path somewhere and that's causing it to use the wrong fastboot version.  That's issue number 1.  The second issue is a USB failure.  USB3 port by chance?  Do you have the latest Moto USB driver installed?  Original OEM USB cable?  It's not a script problem and flashing system is most definitely not going to help here.

[cmh714]

After searching around, I agree with Sam. Could be a fastboot or adb version issue maybe.

[johnthehillbilly]

The USB error can also be caused by a loss of power on USB port typically caused by using a non externally powered USB hub with too many USB devices plugged into it..... I have gotten that USB error before.....

That being said, while following the above advice, do not use a hub and try unplugging any unnecessary USB devices....

HD tappin' .... hillbilly style!!

[cmh714]

I have never tried flashing through a hub but that makes sense. Try and remove any extra links in the chain.

[PFreeman008]

You've got some interesting issues.  I'm going by gut feel on this but I'd say you got platform tools in the path somewhere and that's causing it to use the wrong fastboot version.  That's issue number 1.  The second issue is a USB failure.  USB3 port by chance?  Do you have the latest Moto USB driver installed?  Original OEM USB cable?  It's not a script problem and flashing system is most definitely not going to help here.

 

So I'm plugged straight into the the back of my work's 2009 era iMac (I am an admin on it). According to Apple, it has USB 2.0 ports. Moto drivers installed. The only culprit would be the cable, I actually no longer have the original as a former coworker stole it (but gave me hers, for a different android phone back).

 

peter

[cmh714]

So going back to what Sam said, is it possible you have other drivers for other phones installed? or maybe BlueStacks?

 

Also we had members that had issues on older MacBook Pros, and your iMac is even older.....

[SamuriHL]

Um, you didn't specify that you were running on a mac.  That's rather important information to know.  Are you running windows on this mac or are you trying to run the sh script?

[PFreeman008]

sh script.

 

I'll try some more from my W7 computer @ home.

 

peter

[SamuriHL]

Yea, I'd try on a windows machine and see what happens.  It SHOULD work on a mac but it's not the most common thing so who knows what issues there are.  Windows is a much more known quantity so if you have access to a windows box it'd be easier.