[Q] failing to root after OTA 2.2.1 - Droid X General

Hoping someone can point me in the right direction. Prior to OTA 2.2.1 had my DX rooted for tethering, but forgot to unroot this week before finally running the update that VZn pushed out. Now when i try to root with any method i can find info on, the rageagainstthecage process gets me to a point where rooting stops. Using ADB shows the DX is connected but offline and the whole process just stops there. Rebooting the DX is the only way to start all over again with the same results. Have seen some posts that maybe the later OTA was different than the earlier one and thats why some are having rooting issues. btw, was using pc mode and debug enabled.
I Sure do miss that tethering!

DasNas said:
Hoping someone can point me in the right direction. Prior to OTA 2.2.1 had my DX rooted for tethering, but forgot to unroot this week before finally running the update that VZn pushed out. Now when i try to root with any method i can find info on, the rageagainstthecage process gets me to a point where rooting stops. Using ADB shows the DX is connected but offline and the whole process just stops there. Rebooting the DX is the only way to start all over again with the same results. Have seen some posts that maybe the later OTA was different than the earlier one and thats why some are having rooting issues. btw, was using pc mode and debug enabled.
I Sure do miss that tethering!
Click to expand...
Click to collapse
Find the APK file for Z4 root and give it a go that way or Superoneclick has always worked for me. Just make sure you have the latest drivers from Motorolla for your phone and PC OS. It's far easier then rageagainstthecage.

Thanks, some of the things I've tried... Z4 all 3 editions, they dont hang and run through as if there sucessful, but when the X reboots and i try running an app like root explorer. It says phone not rooted. Super1click gets stuck in a loop and using adb devices, shows device connected but offline. Rebooting phone is the only way out. I Just can't see what im missing here, other than I should have unrooted b4 the OTA update.

DasNas said:
Hoping someone can point me in the right direction. Prior to OTA 2.2.1 had my DX rooted for tethering, but forgot to unroot this week before finally running the update that VZn pushed out. Now when i try to root with any method i can find info on, the rageagainstthecage process gets me to a point where rooting stops. Using ADB shows the DX is connected but offline and the whole process just stops there. Rebooting the DX is the only way to start all over again with the same results. Have seen some posts that maybe the later OTA was different than the earlier one and thats why some are having rooting issues. btw, was using pc mode and debug enabled.
I Sure do miss that tethering!
Click to expand...
Click to collapse
There's been a coupe threads already started with your issue..I think there's one on the 3rd page called can't reroot after the ota update...find it and follow the directions..
Sent from my DROIDX

Thanks for pointing me in the right direction to find the right post. I have to admit it was a very different approach to finally being able to get RW access to the file system & then using a terminal emulator to delete the old Superuser.apk at 1st try i couldn't get rm superuser.apk to work (no such file or dir) then it hit me its case sesitive. 2nd try & it went away.
Finally rooted again & Tethered!
Android Life is Good Again!

DasNas said:
Thanks for pointing me in the right direction to find the right post. I have to admit it was a very different approach to finally being able to get RW access to the file system & then using a terminal emulator to delete the old Superuser.apk at 1st try i couldn't get rm superuser.apk to work (no such file or dir) then it hit me its case sesitive. 2nd try & it went away.
Finally rooted again & Tethered!
Android Life is Good Again!
Click to expand...
Click to collapse
That's good..Enjoy
Sent from my DROIDX

Related

temp root with visionary and z4 problem?

for some reason.. whenever I do temp root with visionary or z4... It says its rooting.. then my phone "restarts" does the sprint 4g slaph screen and gets stuck on the big 4G logo...
I ran visionary when I first got the shift(temp root to run titanium backup) but now it's not working. anyone know why?
I tried z4 and visionary+ and it makes my phone run very slow. R ran seepu and saw that the cpu usage at max all the time. My phone got hot.
I want to root for the wifi hotspot but I'm afraid of messing up the perm root and bricking my phone, so temp root would be ideal, but it isn't really working. Am i missing something?
Its pretty hard to brick this phone...
Sent from my PG06100 using XDA App
when i was rooting my shift z4 wouldn't work for me at all. it did the exact same thing you're describing, temp root>reboot>no root. visionary worked like a charm both times i've rooted this (i was having second thoughts on keeping it so i flashed it stock one night when i was drunk). anyways, if you follow the instructions line by line and copy/paste the code to adb shell it's a pretty painless process. you can root, backup wimax keys, and install clockwork recovery in a matter of about 20 minutes. everyone is nervous their first time... but it's really not difficult. the biggest problems i had was getting the usb drivers to install correctly (win7 x64) and getting a good copy of visionary. other than that, it's easy.
what i'm really trying to say is, i would suggest just perm rooting your device... with root and titanium you can delete all the crap you don't like (ie. kindle, amazon, nfl or nascar) and it makes it easier to work with. you can also OC/UV the stock rom for an even sweeter experience.
Yup, Perma-rooted. Got help in the Shift IRC, they are very nice ppl.
I was having difficulty with the ordinary Temproot option of Visionary (it kept rebooting and slowing down instead), so I instead tried Temproot on Boot. It worked great just now--I'm hoping it continues to do so.
Visionary and Z4root
I am unable to find this in the Android market, is it safe to search for the .apk's for both and install?
This should get you on the right track...
http://forum.xda-developers.com/showthread.php?t=833953
HolyShift said:
This should get you on the right track...
http://forum.xda-developers.com/showthread.php?t=833953
Click to expand...
Click to collapse
Perfect! Thanks for the quick reply.
I sometimes have the same problem with both Visionary+ and Z4Root. I also notice, that when it fails to root, the app also disappears.
For me, If I reboot, the app comes back. If I try a second time, it always works.

[Q] Trouble Rooting and geting "SU" permissions Mytouch 4g. HELP!

This may sound stupid, but does anyone know how to root specifically a RED mytouch 4g?? Maybe the color is intimidating or something, but I have successfully rooted 6 mytouch 4g's and not run into any problems.. I spent a week on this one to no avail. Its running 2.2.1, software number 1.17.531.2, build number 1.17.531.2 CL277036. Is there a manual way without using visionary? It wont grant me permissions even after temp root. Thanks.
try using the gfree method which is in the development section. It seems thats the only way to root the newer mytouches.
Update: Tried every single forum that appeared in the first 10 pages of google for 50 different search terms, and frankly, I'm ****ing beat.. I found a few similar topic forums, but only ONE exact build number, and everything with the SAME EXACT SYMPTOMS.. Is there really nobody out there that has tackled this debockle? I'm not sure what to do at this point, am I doomed?? I'm not a noob with this phone, but I'm not a developer or a programmer either. Anyone got any alternative root methods, other that the visionary, or flashboot methods for the exact specs on my phone??
I'm having the same issue with my red MT4G, had it since Feb. 11 Was able to root but not able to get the s-off same build and software as yours. Help Please!
tim4w5 said:
I'm having the same issue with my red MT4G, had it since Feb. 11 Was able to root but not able to get the s-off same build and software as yours. Help Please!
Click to expand...
Click to collapse
Thats weird, I achieved s=off, using this method: http://forum.xda-developers.com/showthread.php?t=858996
But I can't get superuser permissions to flash the older version of the bootloader, or use gfree. What did you use to root it?
Are these MT4Gs completely stock and out of the box? When I rooted a friend's device, VISIONary wouldn't even temproot at first. He later uninstalled some app and tried VISIONary again and temproot stuck, so maybe something else on the device is getting in the way? Either that or HTC incorporated some fix, we'd need more people with brand new MT4Gs to confirm.
gfree issues
I seem to be having the same issue but when I go to "chmod 777 gfree" I get the ./gfree: permission denied error
bvince05 said:
I seem to be having the same issue but when I go to "chmod 777 gfree" I get the ./gfree: permission denied error
Click to expand...
Click to collapse
Temp root with visionary then try again. Make sure fastboot is disabled before doing it. If it doesn't temp root try an older version of visionary. I used a combo of gfree method and visionary to get root and s off
Sent from my HTC Glacier using XDA App
EDIT: i replied to this while half asleep so figured i would be a little more clear.
i had the gfree permission denied error you got. so temp rooted with visionary(latest) but just froze up my phone. tried a older version and it temp rooted fine. went in to ADB got SU and threw the chmod command at it again and it went through.
hope this helps, not 100% sure it went through because of what i did but its worth a shot.
jdkoren said:
Are these MT4Gs completely stock and out of the box? When I rooted a friend's device, VISIONary wouldn't even temproot at first. He later uninstalled some app and tried VISIONary again and temproot stuck, so maybe something else on the device is getting in the way? Either that or HTC incorporated some fix, we'd need more people with brand new MT4Gs to confirm.
Click to expand...
Click to collapse
I've tried stock out of the box, used it for a while, got s=off, and it stuck even after factory resetting the phone between trying various different methods.
I agree with you regarding a patch of some sort on the software though. I've found this issue on 2 red htc glaciers now.
And although It's new, and shipped with 2.2.1, a buddy of mine goes through them like candy, and I've rooted every single one of them, no problem. even when they started shipping with 2.2.1 it wasnt an issue. So I think it's the newer manufacture build number etc with the red ones..
mustk1ll20 said:
Temp root with visionary then try again. Make sure fastboot is disabled before doing it. If it doesn't temp root try an older version of visionary. I used a combo of gfree method and visionary to get root and s off
Sent from my HTC Glacier using XDA App
EDIT: i replied to this while half asleep so figured i would be a little more clear.
i had the gfree permission denied error you got. so temp rooted with visionary(latest) but just froze up my phone. tried a older version and it temp rooted fine. went in to ADB got SU and threw the chmod command at it again and it went through.
hope this helps, not 100% sure it went through because of what i did but its worth a shot.
Click to expand...
Click to collapse
I have not tried that yet. Where can I find an older version of visionary? I looked for it on their website, but can't seem to find anything but the current version. (maybe I'm not looking hard enough) but.. Hopefully this will work
think this is the one i used. should be R11. may have been updated though, just got the link from another root method that says it r11.
http://www.megaupload.com/?d=7C2BMH3O
It's definitely r11, I'll try this as soon as I get home. thanks!
No problem, hope it works for you.
Sent from my HTC Glacier using XDA App
I dont think It's working. I installed it, then reboot my phone, then ran the app, and At first It looked really REALLY unstable and kept flashing and doing weird things, so I rebooted again, ran it, and now it looks like it's not doing anything at all. How long did it take for your phone to say root successful, maybe I'm just being impatient.
thats what mine did. Just let it do its thing. If its to unstable to put in your commands use adb. I used adb from start to finish just cuz I find it easier.
Didn't take long. It did flash a black screen things like that. But just follow the guide you were using to a T and once you get temp root it shouldn't be a problem from there
Sent from my HTC Glacier using XDA App
I'm kicking myself in the face for not documenting my method I used. I finally did it, but in such a weird way, I'm not sure exactly WHAT it was. I installed visionary 11, uninstalled r14, uninstalled superuser, and ran r11. out of frustration, I scared up some old methods for rooting 2.2, and installed z4 root.. That made it to the second stage, but froze there. So I RE-installed visionary r14, achieved a temproot, and from there flashed gfree, etc.. and eventually stuck a permaroot with s=off.. I apologize for not figuring out exactly what I was doing wrong, or what I did right to solve the problem.
****kkkkk man your slacking -______- I was looking forward to the answer I'm going crazy as well I rooted 3mt4gs in like 5min but my brothers is driving me nuts >=O
carlosdavampire said:
I'm kicking myself in the face for not documenting my method I used. I finally did it, but in such a weird way, I'm not sure exactly WHAT it was. I installed visionary 11, uninstalled r14, uninstalled superuser, and ran r11. out of frustration, I scared up some old methods for rooting 2.2, and installed z4 root.. That made it to the second stage, but froze there. So I RE-installed visionary r14, achieved a temproot, and from there flashed gfree, etc.. and eventually stuck a permaroot with s=off.. I apologize for not figuring out exactly what I was doing wrong, or what I did right to solve the problem.
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA Premium App
sh root.sh
Im getting passed everything, but when i try to run sh root.sh it say can't open root.sh Someone please help me.
I had troubles rooting my Red Mytouch until I came across this.. http://forum.xda-developers.com/showthread.php?t=995549
Follow this to a T and then do yourself a favor and downgrade your Hboot to 0.85.2007
I rooted mine. Go here. http://theunlockr.com/2010/12/10/ho...s-off-on-the-t-mobile-mytouch-4g-htc-glacier/ took me a bit to figure it out. But on this link it tells you to update if you arnt 2.21 or higher or if you haven't received the outa update. Well I did but when I tryed this method with out the update it didn't work so update anyways. IT WORKS!
Sent from my HTC Glacier using XDA App

how to ROOT Desire Z? -Term.Emu wont open again...

Hi!
So I was looking for a way to use AdFree and backup my device and came across This how to on how to root the desire Z. But once I pushed the first set of files to my device and ran the Terminal Emulator and closed it, it won't open again. So I'm kinda stuck there... . When I re-open the emulator, just as the how-to says, it will force close. But then when I try to open it for the second time, it wont open nad my system gets sllooowwww.... All I can do from there is restart the DZ and open the Emulator again from where I would start the procedure all over again...
Any suggestions?
Is there a recent step by step guide on how to root the DZ?
I dont need s-off, do I?
Thanks
AO
Device specs:
HTC Desire Z
Android 2.2.1
Kernel Version 2.6.32.21
Build Number 1.82.405.1
Same here.
You need to downgrade from 1.82 before you can root. I think there is a sticky that explains this.
Sent from my HTC Vision using XDA App
Indeed, for now you require the much older 1.32 firmware revision in order to root the phone... Or leave it on 1.82 and wait and see if people manage to root the new firmware as well...
that happened to me, but i was able to get around it by downloading a different Terminal Emulator from the android market.
xT4Z1N4TRx said:
that happened to me, but i was able to get around it by downloading a different Terminal Emulator from the android market.
Click to expand...
Click to collapse
And then you rooted your phone with or without downgrading?
What happens, if I dont downgrade? Does it "just" not work or is there a brick risk?
I just rooted a G2 earlier today, essentially a Desire Z, but with one file different to download. This is done entirely in adb and took me 10-15 minutes max. Known as the G-free method: Steps are located here. All links aside from the drivers for your phone to pc are alive. For the drivers for your PC to read through adb (if you don't already have them), you can download them through the Android SDK manager. For a brief guide on setting up ADB, go here.
This will root your phone, unlock sim, give you s-off, super-CID, and ClockworkMod Recovery 3.0.
As mentioned earlier, you will probably have to downgrade your phone's firmware. Check it in your phone's settings with the one required by the wiki before progressing. There are instructions on how to downgrade in there, but I didn't have to go through that step.
Once you're rooted, the first two apps you're gonna want to get are Rom Manager and Titanium backup. Good luck on not getting addicted to custom roms.
takram said:
I just rooted a G2 earlier today, essentially a Desire Z, but with one file different to download. This is done entirely in adb and took me 10-15 minutes max. Known as the G-free method: Steps are located here. .............
Click to expand...
Click to collapse
I've followed the same link as above on two different DesireZ's now and its worked perfectly, just read it a couple of times first, get all the files, check md5's and follow it step by step making sure you don't miss anything.

Kindle Fire lost root. Rooted with Burrito Root

Interesting issue I found today.
I have an Amazon Kindle Fire that I rooted using the Burrito Root method as described in the stickied thread above entitled: "Video guide to rooting etc..."
I followed the instructions as presented in the You Tube video, and achieved root.
I loaded the android market and downloaded the apps I had previously with no dramas. They all run fine.
Last night I downloaded Voodoo OTA Root Keeper as described in another thread.
I got to playing around with it today, and it said I did not have root access. Used the root checker utility as posted in the you tube video previously mentioned, and it too says no root. Attempted to use root explorer, and again no root. Power off and back on, same deal.
Weird to say the least. As far as I know, I have not had an update to the kindle firmware (current version: 6.2.1_user_3103920) which appears to be unchanged since I rooted. There were no issues when I rooted, and all functioned as it should have (rooted I mean)
The only thing I did do in the previous week was download an amazon movie to the device.
Any ideas on WTF happened?
I had been considering installing TWRP...now I am wondering if I should re-root using the same method, or uninstall the stuff I put on in the originl root, and just load TWRP, and do it that way?
Thanks for any input.
Burrito Root gives you root through ADB. In order to get permanent root that's usable by applications such as Root Explorer you need to push the su binary and install the superuser.apk. Not sure if that was covered in whatever video you watched, but there should be instructions and download links kicking around here and rootzwiki somewhere.
Easiest way is to use this http://forum.xda-developers.com/showthread.php?t=1399889 and use option 2 then 3. should be good to go after that.
skourg3 said:
Burrito Root gives you root through ADB. In order to get permanent root that's usable by applications such as Root Explorer you need to push the su binary and install the superuser.apk. Not sure if that was covered in whatever video you watched, but there should be instructions and download links kicking around here and rootzwiki somewhere.
Click to expand...
Click to collapse
For clarification, as I failed to mention it in my original post.
Superuser.apk was installed, as were all commands done through ADB as prescribed...it appeared to have worked flawlessly. Until now. LOL
I am new to the fire, not new to android.
It is rather puzzling, as I have never experienced this type of issue before.
Re use ota root keeper and restore your root
Sent from my Kindle Fire using xda premium
silvertrd said:
For clarification, as I failed to mention it in my original post.
Superuser.apk was installed, as were all commands done through ADB as prescribed...it appeared to have worked flawlessly. Until now. LOL
I am new to the fire, not new to android.
It is rather puzzling, as I have never experienced this type of issue before.
Click to expand...
Click to collapse
Superuser.apk and the su binary are separate things. These are the original instructions. Not sure what the video you watched suggests.
The su binary goes into /system/xbin and you need to:
Code:
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
When Superuser.apk is installed it gets put into /data/app. If you've only done one, but not the other, that's most likely causing your issue.
*Edit* In your original post you mentioned messing around with OTA Rootkeeper. There's a checkbox that backs up the su binary. Maybe it was unchecked when you temporarily unrooted? There's also a button that deletes the su binary backup. Very possible one of these led to your issue.
phunky123 said:
Easiest way is to use this http://forum.xda-developers.com/showthread.php?t=1399889 and use option 2 then 3. should be good to go after that.
Click to expand...
Click to collapse
I had looked at that. My question doing it using that method:
Do I need to uninstall/delete anything from my previous root? or will that program overwrite superuser, etc?
ghost_og:
The video I watched was the same video you link to.
I copied and pasted all of the commands into the adb shell as nat3mil describes.
I wonder where I went wrong? Weird.
Can I just connect the kindle to my computer, run burrito root, and then re-push the commands via adb as described ? I just don't wanna bork it up and brick it.
Veritass said:
Re use ota root keeper and restore your root
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Great idea! Just now tried that after seeing your suggestion. No joy. FML.
silvertrd said:
Can I just connect the kindle to my computer, run burrito root, and then re-push the commands via adb as described ? I just don't wanna bork it up and brick it.
Click to expand...
Click to collapse
It should be fine. I remember having to run it twice and I never went through and deleted anything. Here's something interesting: I checked both /system/bin and /system/xbin when I was rooted and unrooted. Even though I originally installed su to /system/xbin, OTA Rootkeeper places it into /system/bin upon restoring root.
I'm not saying you should do that, but just thought I'd bring it up. Maybe that has to do with why you lost root privelages out of the blue.
Also, I know certain Superuser.apk's were not working properly. The one included in the zip file at Androidpolice is actually com.noshufou.android.su-1.apk. Perhaps try using that one instead?
*Edit2* I just looked at the official thread and noticed he updated the zip and it now uses Superuser.apk. Not sure if Androidpolice ever updated their zip as well.
ghost_og:
Thanks!
I will give it a shot, and report back later this evening.
Regards,
SilverTRD
install busybox from the market and try again
KFU will tell you if it is rooted or not. just connect KF to your pc and run no harm going that far.
I am in the same situation as you are, same steps. Rooted with BR, but didn't root all the way, yet was still able to put the market apps.
My kindle Fire (non-HD) just "lost" root too!!!
No idea how it happened.
I successfully rooted last summer with the KFU and have temp un-rooted/re-rooted MANY times with OTA Rootkeeper . I went in yesterday to root, but the buttons were gone in Rootkeeper and it shows that I'm NOT rooted.
I tried to update/reinstall Superuser but I probably just made things worse.
Is there any way for me to get root back without losing all of my data??
If not, I suspect that I have to go back to KFU and do the root process again, but will this brick my Kindle???
Thanks all!
If you used KFU the first time it should work again as long as you can get good communication and the driver is still installed correctly. Do you still have twrp and fff? if so just flash modaco if you`re on stock no wipes needed and you will never have to worry about loosing root again http://forum.xda-developers.com/showthread.php?t=1439916
Thepooch said:
If you used KFU the first time it should work again as long as you can get good communication and the driver is still installed correctly. Do you still have twrp and fff? if so just flash modaco if you`re on stock no wipes needed and you will never have to worry about loosing root again http://forum.xda-developers.com/showthread.php?t=1439916
Click to expand...
Click to collapse
Thanks Thepooch! I'm at work now, so I'll have to wait until I get home to my laptop to try.
I had no problems with the driver or communication, so that "shouldn't" be an issue.
The root process with KFU actually went painfully smoothly when I did it over the summer so hopefully second time will be the same.
I still have twrp and fff, but I'm not sure what you mean by "just flash modaco if you`re on stock", but I'll come back if i brick.
While losing my data would suck, I won't lose much sleep if I have to wipe it.
Thanks again Thepooch.
Took less than 5 minutes to get the root back with KFU.

[Q] superoneclick stuck

superoneclick 2.3.3 stuck on step 5 (unable to chmod...) and i think i did everything right!
it's on C:/ and i run it as adminstrator but it still stuck-???
Liorgex said:
superoneclick 2.3.3 stuck on step 5 (unable to chmod...) and i think i did everything right!
it's on C:/ and i run it as adminstrator but it still stuck-???
Click to expand...
Click to collapse
Use ZergRush method to root.
sorry for being noob but what does it mean? its something for SOC or its another program?
Liorgex said:
sorry for being noob but what does it mean? its something for SOC or its another program?
Click to expand...
Click to collapse
thats another tool using different method of root.
Here: http://forum.xda-developers.com/showthread.php?t=1321582
Did you enable the Debug USB Settings?
Very nice, thanks!
Step #7 stuck for me
Superone stuck at step #7 on me said waiting for device but never whent finsed the root I have romtool box , titaumbackup, allso have superuser installed plus adw installed could those be the couse of superone getting stuck just before it reinstalled programs.. I have z4 and universalroot allso was truing to root with out pc my phone is a samsung infuse from at&t
SuperOneClick Stuck ** Possible Solutions for some **
Liorgex said:
superoneclick 2.3.3 stuck on step 5 (unable to chmod...) and i think i did everything right!
it's on C:/ and i run it as adminstrator but it still stuck-???
Click to expand...
Click to collapse
I have been trying to root a Sidekick 4G for two days now. But the only process that I could find to do it that was currently updated was SuperOneClick. I am posting this to hopefully help others that might be stuck somewhere along the process because in my extensive searches, I have found so many people that were stuck at the same places I was, but noone seemed to have any answers other than re-install the drivers. Well I installed and re-installed the drivers about 10 times; downloading them from various websites.
Problems that I had:
- My Samsung drivers would install part of the way or not all all
Finally, what worked for me was to DL KIES from the Samsung Website. I installed KIES and let it fix the drivers for me! I was then able to get past the 2nd line in SuperOneClick where it was waiting for ADB but now...
- I was getting stuck at Step 5 in SuperOneClick and sometimes at step 7
What I found was that my virus software (Bitdefender) was deleting the exploits as soon as I started the root process! Even though I thought that I had shut down Bitdefender (in MSCONFIG) when I went back into MSCONFIG to check I found that Bitdefender was turning itself back on!
I found that there was a way in the settings within BD to turn off the autovirus scan for a short period of time. Once I had it all turned off, I unzipped SOC again (because BD apparently couldn't see the zipped up files and never deleted those). I reran SuperOneClick, then it finally worked!!!
Hopefully this helps someone from spending the hours & hours that I did trying to find the solution.
SuperOneClick stuck on step 5 for me too.
-Danik- said:
Use ZergRush method to root.
Click to expand...
Click to collapse
SuperOneClick uses ZergRush. Why would it matter?
Anyway, when mine was stuck at step 5, it did finally clear. You just have to wait.
Every firmware for the MS2 is rootable with Cydia Impactor, even the ones on BL4.
It's easier now
Lean946 said:
Every firmware for the MS2 is rootable with Cydia Impactor, even the ones on BL4.
It's easier now
Click to expand...
Click to collapse
This worked for me. Couldn't have been easier.
Always used SuperOneClick to root my ML2.
Please, check this items:
- User Debugging Mode
- Motorola Flash Interface (on Device manager of your computer), if not show this, will not work well.
With your device manager opened, click on Root button and check if your cell loses connection when stopped at chmod command.
The SuperoneClick uses the zergrush tool and seems like a exploit by anti-spyware softwares. Make sure that you disable when runs the SuperOneClick.

Categories

Resources