[*]
[*] Motochopper: Android root exploit (Windows version)
[*] v1.0
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on the Motorola Razr HD, Razr M, Razr Maxx HD, and Atrix HD.
[*] Supports lots of other devices as well. ;-)
[*]
[*] Before continuing, ensure that USB debugging is enabled, that you
[*] have the latest USB drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] WARNING: This will likely void the warranty on your device. I am
[*] not responsible for any damage to your phone as a result using this
[*] tool.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: protocol fault (status read)
[*] Device found.
[*] Pushing exploit...
error: more than one device and emulator
error: more than one device and emulator
[*] Pushing root tools...
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
[*] Rooting phone...
error: more than one device and emulator
[*] Cleaning up...
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
[*] Exploit complete. Press enter to reboot and exit.
Press any key to continue . . .
[ROOT] Motochopper: {WARNING: No longer works on newer builds}
#101
Posted 13 April 2013 - 01:05 PM
#102
Posted 13 April 2013 - 01:13 PM
XT910 root tool for now let it please. tired of waiting.Ah, this isnt for your phone, and it appears from the message that you already have root or at least the superuser app
#103
Posted 13 April 2013 - 01:25 PM
If you use adb and run "adb devices" when the device is connected, what shows?Sorry, that's what I meant. Don't have BlueStacks installed. Here's the error output:
Sig by livinginkaos
Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7
#104
Posted 13 April 2013 - 01:32 PM
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
TA26101T54 device
emulator-5554 offline
#105
Posted 13 April 2013 - 01:33 PM
Sig by livinginkaos
Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7
#106
Posted 13 April 2013 - 02:07 PM
RAZR HD Dev (I could have bought a Platypus instead)
Sig by livinginkaos
Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7
#107
Posted 13 April 2013 - 02:42 PM
#108
Posted 13 April 2013 - 08:39 PM
#109
Posted 14 April 2013 - 04:03 AM
Help!!
#110
Posted 14 April 2013 - 07:53 AM
try looking in the right forum section. Takes almost no time to help yourself.Need root for Motorola RAZR(XT910) Android 4.1.2
Help!!
Sent from my N4 running Paranoid Android
#111
Posted 14 April 2013 - 10:14 PM
First of all, let me say thank you very much!
Now for hopefully a simple question. I typically go through the process of root > factory reset > reinstall and I typically have no issues with Superuser or SuperSU staying installed after the factory reset.
Every time I reset my HD, I seem to lose the superuser app and I end up having to root again using the tool to get it back. Is this a problem with my phone, or does this new exploit prevent a permanent installation of Superuser? I only ask because when I finally decided to install and run Voodoo OTA Rootkeeper, it shows that the phone is still rooted and has no Superuser installed.
I'm just looking for an answer as losing superuser on a factory reset is new to me. If losing Superuser on reset is typical with some phones, I'm fine with it. However, if there is an issue with my phone and this is not typical, I'd also like to know.
I just like to goof around with my phones every now and then and after I tend to try something major, I like to do a factory reset.
Again, I say thanks for this great tool!
#112
Posted 15 April 2013 - 03:34 PM
"We are the People Verizon warned you about"
8 GB Bionic JB, 16 GB Bionic JB, Bionic Lapdock X2, Razr Maxx XT912 JB, Razr M XT907 JBLX
#113
Posted 16 April 2013 - 09:13 AM
Hello, I've tried this in my Razr D3
and it did not work. It stops at "Rooting phone, this may take a few mins" and nothing happens. Is the phone bricked? I have not reset it yet. Should I do it?#114
Posted 16 April 2013 - 09:27 AM
"We are the People Verizon warned you about"
8 GB Bionic JB, 16 GB Bionic JB, Bionic Lapdock X2, Razr Maxx XT912 JB, Razr M XT907 JBLX
#115
Posted 16 April 2013 - 09:27 AM
Another person blind to the "this is not for OMAP phones" warning
Sent from my DROID RAZR using Tapatalk 2
To be fair its a Mediatek device
Sent from my Galaxy Nexus using Tapatalk 2
Please do not Personal Message me for help or troubleshooting. They will be ignored. Post in threads or start one in Q&A sections.
#116
Posted 16 April 2013 - 09:32 AM
To be fair its a Mediatek device
Sent from my Galaxy Nexus using Tapatalk 2
Yes it's mediatek, and it's been so hard to find a root method, so I tought this would work since it says for other phones. My question is if I can reset the phone since the process stopped in the middle, or if is there anything I should do before reboot to avoid damage?
#117
Posted 16 April 2013 - 01:24 PM
Yes it's mediatek, and it's been so hard to find a root method, so I tought this would work since it says for other phones. My question is if I can reset the phone since the process stopped in the middle, or if is there anything I should do before reboot to avoid damage?
thanks God it's still working. Is there any root solution for Mediatek 4.1.2?
#118
Posted 17 April 2013 - 11:52 AM
Dan, me love you long time for this one broski (no homo). You done did it now. You done and gone some impossible shiznit and made everyone crazy.
I just donated and I hope that other people will follow suit. This kind of work deserves SUPPORT. If everyone gave even a little bit, it would amount to a lot more than most people might think.
THANK YOU.
- livinginkaos likes this
#119
Posted 17 April 2013 - 03:10 PM
First of all, let me say thank you very much!
Now for hopefully a simple question. I typically go through the process of root > factory reset > reinstall and I typically have no issues with Superuser or SuperSU staying installed after the factory reset.
Every time I reset my HD, I seem to lose the superuser app and I end up having to root again using the tool to get it back. Is this a problem with my phone, or does this new exploit prevent a permanent installation of Superuser? I only ask because when I finally decided to install and run Voodoo OTA Rootkeeper, it shows that the phone is still rooted and has no Superuser installed.
I'm just looking for an answer as losing superuser on a factory reset is new to me. If losing Superuser on reset is typical with some phones, I'm fine with it. However, if there is an issue with my phone and this is not typical, I'd also like to know.
I just like to goof around with my phones every now and then and after I tend to try something major, I like to do a factory reset.
Again, I say thanks for this great tool!
My story... superuser binary update was necessary. I updated the app and all appears swell. Now I gave to try OTA Rootkeeper.
Sent from my XT912 using Tapatalk 2
#120
Posted 17 April 2013 - 05:33 PM
Any chance there will be any love for the Bionic?
5 user(s) are reading this topic
0 members, 5 guests, 0 anonymous users