***WARNING*** This method will very likely format your internal/external memory cards. Please be aware of this before running.
http://c-skills.blogspot.com/2011/04/yummy-yummy-gingerbreak.html
Works on:
OLYFR_U4_1.5.7
OLYEM_U4_1.4.2
If you test it and it works on your firmware, send me a PM.
APK has tested to be working on OLYFR_U4_1.5.7: http://forum.xda-developers.com/showthread.php?t=1044765
gingerbreak? does that apply to the atrix?
Ririal said:
http://c-skills.blogspot.com/
I'll start testing this when I get home from work
Click to expand...
Click to collapse
WOW, I hope to see an interesting turnout
Just looks like a different type of gaining root?
It's a new exploit. It worked on my friend's Evo 4G here at work, but I haven't tested it on the Atrix yet. If it works on 1.57, it might make getting root that much easier for us. Looking at the exploit he's using, it's very unreliable as it's an overflow exploit and not a logic exploit like most of the other current methods.
Hm. Giddyup and like always. Thanks for your hard work fen
Sent from my MB860 using XDA Premium App
Tried on the Atrix..popped an error saying could not extract assets
Sent from my MB860 using XDA Premium App
$ /data/local/tmp/GingerBreak
/data/local/tmp/GingerBreak
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Detected Froyo!
[+] Found system: 0xafd14885 strcmp: 0xafd1db25
[+] Found PT_DYNAMIC of size 264 (33 entries)
[+] Found GOT: 0x000142a8
[+] Using device /devices/platform/tegra-sdhci.2/mmc_host/mmc2
[*] vold: 1365 GOT start: 0x000142a8 GOT end: 0x000142e8
[*] vold: 1365 idx: -2048 fault addr: 0x00013830
[+] fault address in range (0x00013830,idx=-2048)
[+] Calculated idx: -1378
[*] vold: 23041 idx: -0001378
[*] vold: 23041 idx: -0001377
[*] vold: 23041 idx: -0001376
[*] vold: 23041 idx: -0001375
[*] vold: 23041 idx: -0001374
[*] vold: 23041 idx: -0001373
[*] vold: 23041 idx: -0001372
[*] vold: 23041 idx: -0001371
[*] vold: 23041 idx: -0001370
[*] vold: 23041 idx: -0001369
[*] vold: 23041 idx: -0001368
[*] vold: 23041 idx: -0001367
[*] vold: 23041 idx: -0001366
[*] vold: 23041 idx: -0001365
[*] vold: 23041 idx: -0001364
[*] vold: 23041 idx: -0001363
[*] vold: 23041 idx: -0001362
[*] vold: 23041 idx: -0001361
[*] vold: 23041 idx: -0001360
[*] vold: 23041 idx: -0001359
[*] vold: 23041 idx: -0001358
[*] vold: 23041 idx: -0001357
[*] vold: 23041 idx: -0001356
[*] vold: 23041 idx: -0001355
[*] vold: 23041 idx: -0001354
[*] vold: 23041 idx: -0001353
[!] dance forever my only one
#
Stupid formatting.
Sweet! Hopefully this carries over to the upcoming update
I get a permission denied error message.
So did this actually work?
Edit: glad your on it seven, I'm hoping it works on that telstra
Sent from my rooted and frozen Bell MB860!
I am very much on it... just trying to get everything working as I know it works, since I was able to gain root once but then never again... I forgot to copy busybox and therefore unable to preserve root.
I saw this earlier today while I was attending classes. Looks very promising for both Froyo and Gingerbread.
Ririal, seeming that this root method works for the telstra sbf, and we should be able to do cwm recovery, do you still think we should be waiting for the bell sbf? What is the "worst case" here? A bad flash before cwm backup?
Does anyone know if there are any different versions of the bell atrix so that the telstra would not work reliably on all bells?
Sent from my rooted and frozen Bell MB860!
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Detected Froyo!
[+] Found system: 0xafd14885 strcmp: 0xafd1db25
[+] Found PT_DYNAMIC of size 264 (33 entries)
[+] Found GOT: 0x000142a8
[+] Using device /devices/platform/tegra-sdhci.2/mmc_host/mmc2
[*] vold: 1364 GOT start: 0x000142a8 GOT end: 0x000142e8
[*] vold: 1364 idx: -2048 fault addr: 0x00013830
[+] fault address in range (0x00013830,idx=-2048)
[+] Calculated idx: -1378
[*] vold: 9865 idx: -0001378
[*] vold: 9865 idx: -0001377
[*] vold: 9865 idx: -0001376
[*] vold: 9865 idx: -0001375
[*] vold: 9865 idx: -0001374
[*] vold: 9865 idx: -0001373
[*] vold: 9865 idx: -0001372
[*] vold: 9865 idx: -0001371
[*] vold: 9865 idx: -0001370
[*] vold: 9865 idx: -0001369
[*] vold: 9865 idx: -0001368
[*] vold: 9865 idx: -0001367
[*] vold: 9865 idx: -0001366
[*] vold: 9865 idx: -0001365
[*] vold: 9865 idx: -0001364
[*] vold: 9865 idx: -0001363
[*] vold: 9865 idx: -0001362
[*] vold: 9865 idx: -0001361
[*] vold: 9865 idx: -0001360
[*] vold: 9865 idx: -0001359
[*] vold: 9865 idx: -0001358
[*] vold: 9865 idx: -0001357
[*] vold: 9865 idx: -0001356
[*] vold: 9865 idx: -0001355
[*] vold: 9865 idx: -0001354
[*] vold: 9865 idx: -0001353
[!] dance forever my only one
#
on my at&t atrix, 1.5.7
so this worked? no more beforeupdate/afterupdate.bat needed now?
dLo GSR said:
so this worked? no more beforeupdate/afterupdate.bat needed now?
Click to expand...
Click to collapse
I'm pretty sure that the idea worked. You'll probably still have to wait for some kind of script to come out before getting it to work. At least unless you're clever enough to figure it out yourself. Based on what I saw in the new Telstra SBF root thread, it needs to be copied to an external SD, and then running it will obtain temp root. From there, you have to copy over busybox and such. Not sure if this will be the exact process of ATT atrix, but I guess we will find out soon enough.
Is anyone working on scripting out a version of this root for 1.57? Perhaps this will work for the new OTA update also...
I tried running this apk that someone put together from this exploit on 1.57
http://stealth.openwall.net/xSports/zimperlich.apk (it was in the comments of that blog post)
It ran successfully, but no SU available afterwards.
bearsfan172 said:
Is anyone working on scripting out a version of this root for 1.57?
Click to expand...
Click to collapse
http://stealth.openwall.net/xSports/zimperlich.apk
leadguy68 said:
I tried running this apk that someone put together from this exploit on 1.57
http://stealth.openwall.net/xSports/zimperlich.apk (it was in the comments of that blog post)
It ran successfully, but no SU available afterwards.
Click to expand...
Click to collapse
Download Root Checker from the market. Sometimes you're rooted but the su icon is not there.
If root checker says you're rooted.. then you just download superuser from the market.
Related
I have made a toolkit for root your device!
Try on stock ROM, you must have these files in /data/local/tmp
- Superuser.apk
- su
- zergRush
CASE sensitieve
Then push the first button, my app is not done, but I will give you a chance to try it
Please report back!
it isn't working.
Also i have tried to run zergRush on the Phone and this is the output:
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x0002e118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[+] Zerglings found a way to enter ! 0x18
[*] Sending 189 zerglings ...
[*] Trying a new path ...
[*] Sending 189 zerglings ...
[*] Trying a new path ...
[*] Sending 189 zerglings ...
[*] Trying a new path ...
[*] Sending 189 zerglings ...
[*] Trying a new path ...
[*] Sending 189 zerglings ...
[*] Trying a new path ...
[-] Zerglings did not leave interesting stuff
for my self the original zergRushexploid works.
all,
after updating my rooted kl7 to la1 I had to reflash using odin (PC) because it did not flash the csc correctly (nullnullnull issue).
trying to root it based on the official thread i end up with
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
--- pushing zergRush"
1442 KB/s (23052 bytes in 0.015s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x0002e118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
Click to expand...
Click to collapse
Any suggestion what to do to regain root? downgrading will most probably not work due to the CSC issue i had in the first try..
thanks
will try to re-flash.
perhaps that works.
Update:
still no progress with rooting after flashing.
Code:
Press any key to continue . . .
--- pushing zImage
4730 KB/s (8387840 bytes in 1.731s)
--- flashing zImage
/dev/block/mmcblk0p5: cannot open for write: Permission denied
--- cleaning up
--- rebooting
Downgrade, then flash with Mobile Odin. Make sure EverRoot is selected.
Solution
Nah, that did not work.
What worked was this:
* downgrade (kk9 in my case)
* root + cwm
* upgrade to LA1
* again NULL error
* just flash the CSC file via odin
THAT actually did work and kept me root.
help!
hey donblick i have the same situiation as your's as mine is i'm not rooted and i want to get root my version is the same as yours N7000DXLA1 .My problem is also the same when i run the runme.exe after pushing 189 zerlings it says blue flames with hellions. So you said you have solve the problem by downgrading? can you help me how to downgrade? thanks
Hello
I was on ROM XXKKA with Root.
I flash the new rom XXLC1 with Mobile ODIN Lite. Now, device isn't anymore root.
Y tried to get root with CF Root en I get
---------------------------------------------------------------
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
--- pushing zergRush"
865 KB/s (23052 bytes in 0.026s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x0002e118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
---------------------------------------------------------------
We should have (temporary) root now
We will try to flash CF-Root kernel now
Please watch for any errors beyond this point!
---------------------------------------------------------------
Appuyez sur une touche pour continuer...
--- pushing zImage
3341 KB/s (8387840 bytes in 2.451s)
--- flashing zImage
/dev/block/mmcblk0p5: cannot open for write: Permission denied
--- cleaning up
--- rebooting
---------------------------------------------------------------
If all is well, CF-Root should be flashed
Your device should be rebooting now
Please check if you have root and CWM after boot completes!
---------------------------------------------------------------
But after that my devic still Unroot...
Anybody can Help??
Thread closed, double plus wrong section.
and i try to unlock uing the megatron....
and i keep getting error..
already tried with 2 comptuers...
[*]
[*] Megatron: LG Optimus 3D/Thrill Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest LG drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
[*] Device found.
[*] Deploying payload...
2078 KB/s (564396 bytes in 0.265s)
pkg: /data/local/tmp/evil.apk
Success
[*] Owning phone...
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Writing to block device...
4 KB/s (4322 bytes in 1.000s)
[*] Searching block device for string, this may take a minute.
[*] Pushing root tools to device...
* daemon not running. starting it now *
* daemon started successfully *
1399 KB/s (22364 bytes in 0.015s)
2112 KB/s (843503 bytes in 0.390s)
[*] Rebooting device again...
[*] Waiting for phone to reboot.
[*] Getting root...
cp: cannot create '/system/bin/su': Read-only file system
Unable to chmod /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
cp: cannot create '/system/app/Superuser.apk': Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
[*] Cleaning up...
cp: cannot stat '/data/local/run-as.bak': No such file or directory
su: permission denied
su: permission denied
rm failed for /data/local/run-as.bak, No such file or directory
Success
[*] Rebooting...
error: protocol fault (no status)
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
davidliu21 said:
and i try to unlock uing the megatron....
and i keep getting error..
already tried with 2 comptuers...
[*]
[*] Megatron: LG Optimus 3D/Thrill Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest LG drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
[*] Device found.
[*] Deploying payload...
2078 KB/s (564396 bytes in 0.265s)
pkg: /data/local/tmp/evil.apk
Success
[*] Owning phone...
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Writing to block device...
4 KB/s (4322 bytes in 1.000s)
[*] Searching block device for string, this may take a minute.
[*] Pushing root tools to device...
* daemon not running. starting it now *
* daemon started successfully *
1399 KB/s (22364 bytes in 0.015s)
2112 KB/s (843503 bytes in 0.390s)
[*] Rebooting device again...
[*] Waiting for phone to reboot.
[*] Getting root...
cp: cannot create '/system/bin/su': Read-only file system
Unable to chmod /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
cp: cannot create '/system/app/Superuser.apk': Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
[*] Cleaning up...
cp: cannot stat '/data/local/run-as.bak': No such file or directory
su: permission denied
su: permission denied
rm failed for /data/local/run-as.bak, No such file or directory
Success
[*] Rebooting...
error: protocol fault (no status)
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
Click to expand...
Click to collapse
try this one
that's the one i used....
Try super one click I don't remember how I rooted I can try later maybe I would have to flash it tho
sent from my acidhazard thrill
I rooted m lg thrill with megatron in windows 7. I didnt have any problem. You can try this.
Ok finally ive tried 3 comouters , non of them works all windows 7 and i use a old computer running windows xp. And it works like a charm lol
Sent from my LG-P925 using XDA
I'm glad ya got it working, but it should of worked fine on win7. Ive been on 7 sense it came out and use nothing else.
davidliu21 said:
and i try to unlock uing the megatron....
and i keep getting error..
already tried with 2 comptuers...
[*]
[*] Megatron: LG Optimus 3D/Thrill Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest LG drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
[*] Device found.
[*] Deploying payload...
2078 KB/s (564396 bytes in 0.265s)
pkg: /data/local/tmp/evil.apk
Success
[*] Owning phone...
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Writing to block device...
4 KB/s (4322 bytes in 1.000s)
[*] Searching block device for string, this may take a minute.
[*] Pushing root tools to device...
* daemon not running. starting it now *
* daemon started successfully *
1399 KB/s (22364 bytes in 0.015s)
2112 KB/s (843503 bytes in 0.390s)
[*] Rebooting device again...
[*] Waiting for phone to reboot.
[*] Getting root...
cp: cannot create '/system/bin/su': Read-only file system
Unable to chmod /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
cp: cannot create '/system/app/Superuser.apk': Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
[*] Cleaning up...
cp: cannot stat '/data/local/run-as.bak': No such file or directory
su: permission denied
su: permission denied
rm failed for /data/local/run-as.bak, No such file or directory
Success
[*] Rebooting...
error: protocol fault (no status)
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
Click to expand...
Click to collapse
Spent hours and hours spread across many days trying to find out what happened. All you need to do is hard reset your phone and take out Micro SD card. Restart your computer to eliminate any usb driver conflicts (don't really need to do this step but you never know). Then run megatron_windows.
I'm trying to root a new Droid 4 for a friend. I rooted one a month or so ago using Motofail without any trouble. But it's not working for me this time.
I'm running Windows 7 x64.
I installed the latest Motorola drivers.
I connected the phone to USB cable and let it install all the drivers with USB Debugging enabled and with it disabled. I did both in Charge only and Mass Storage.
One thing that is unusual in this situation is that the phone hasn't been activated with Verizon. I'm doing this so my friend can keep using his old phone until I have this one set up. I've done this in the past with several Droid Razrs but the other Droid 4 I rooted was already activated. If you think this is causing the trouble, let me know.
Model Number: DROID4
System Version: 6.13.215.XT894
Android Version: 2.3.6
Build Number: 6.5.1_167_DR4-1_M-215
I get the following in command prompt when attempting to root:
[*]
[*] Motofail: Universal Motorola Android Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on Droid 3, Droid Bionic, Droid RAZR, and Droid 4
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Device found.
[*] Deploying payload...
682 KB/s (501292 bytes in 0.717s)
[*] Owning phone...
[*] Motofail: Universal Motorola Android Root Exploit
[*] Copyright (c) 2012 Dan Rosenberg (@djrbliss)
[*] Exploit complete.
[*] Rebooting device...
[*] Waiting for phone to reboot.
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
[*] Attemping persistence...
adb server is out of date. killing...
* daemon started successfully *
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
[*] Cleaning up...
error: device not found
error: device not found
[*] Rebooting...
error: device not found
error: protocol fault (no status)
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
Can anyone help me? I know you can...
Sounds like your Motorola USB drivers are nonexistent or outdated. I would download the latest USB drivers and try it again. You cannot just go by the drivers Windows 7 downloads, you need to download them from the Motorola website.
---------- Post added at 09:45 PM ---------- Previous post was at 09:43 PM ----------
Here's that link:
http://www.motorola.com/Support/US-EN/Support-Homepage/Software_and_Drivers/USB-and-PC-Charging-Drivers
Thanks for the reply. I downloaded the latest drivers and restarted the computer and now I get this...
[*]
[*] Motofail: Universal Motorola Android Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on Droid 3, Droid Bionic, Droid RAZR, and Droid 4
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
adb server is out of date. killing...
* daemon started successfully *
[*] Device found.
[*] Deploying payload...
550 KB/s (501292 bytes in 0.889s)
[*] Owning phone...
adb server is out of date. killing...
* daemon started successfully *
[*] Motofail: Universal Motorola Android Root Exploit
[*] Copyright (c) 2012 Dan Rosenberg (@djrbliss)
[*] Exploit complete.
[*] Rebooting device...
adb server is out of date. killing...
* daemon started successfully *
[*] Waiting for phone to reboot.
adb server is out of date. killing...
* daemon started successfully *
error: protocol fault (no status)
[*] Attemping persistence...
adb server is out of date. killing...
* daemon started successfully *
error: device not found
failed to copy 'su' to '/system/bin/su': Read-only file system
adb server is out of date. killing...
* daemon started successfully *
Unable to chmod /system/bin/su: No such file or directory
adb server is out of date. killing...
* daemon started successfully *
link failed Read-only file system
* daemon not running. starting it now *
* daemon started successfully *
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
adb server is out of date. killing...
* daemon started successfully *
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
[*] Cleaning up...
adb server is out of date. killing...
* daemon started successfully *
[*] Motofail: Universal Motorola Android Root Exploit
[*] Copyright (c) 2012 Dan Rosenberg (@djrbliss)
[*] Exploit complete.
[*] Rebooting...
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
error: protocol fault (no status)
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
It seems to me to go okay until the phone reboots... at that point the phone trys to activate and I wonder if that's messing up the system. Unless someone has a better solution, I'm going to activate the phone and then try it to see if it will make a difference.
Are you giving the program admin rights?
Sent from my DROID4 using Tapatalk 2
I give admin rights by right-clicking on run.bat and selecting Run as administrator? If yes, I've tried that. The problem isn't specific to Droid 4 as I just now tried rooting a Razr with the same results. It's telling me my "adb server is out of date" and then "device not found".
Can any of you guys tell me how to figure out where the problem is and fix it? It's weird because I've rooted 8 Razrs and 1 D4 before without a problem...
Unroot and reroot.
Sent from my DROID4 using Tapatalk 2
I was never rooted so how can I unroot?
Also make sure your phone is in charge only mode, and the screen is unlocked and on when the process begins.
Yes my phone was in Charge only with screen unlocked.
Thanks to all who are responding!
Try using the Droid 4 utility instead of just Motofail.
Then, like papi was saying, try running the unroot process to get rid of any trace of the exploit. You may want to boot into fastboot and run a data/cache wipe at this point. Then, run the root option again.
I got it guys!!! I copied five files from the Motofail folder: busybox, motofail, run.bat, su and Superuser.apk to my Android-sdk\platform-tools\ folder. I then ran run.bat as an Adminstrator and everything went off without a hitch. Yay!!!
But please, can someone tell me why it worked. I would really like to use this as a learning experience because I just spent a frustrating 8 hours or so fussing with this.
Thanks guys!
mrbuilder
It could have been that somehow the program couldnt find those files in the previous directory
Sent from my DROID4 using Tapatalk 2