Greetings All -
First time post...lurked for a while. Just recently purchased an Atrix HD Dev. Edition. I guess I'm a little bit confused...I got an unlocked bootloader etc., but no su executable or Superuser.apk. Motorola gives no instructions on getting root, just how to unlock your bootloader.
I realize I could flash the phone and run a different image/ROM etc, but I want to just use the current generic ICS install for the time being.
I've rooted multiple other Android devices, so I get the idea of using an exploit to get root, install su/busybox/superuser.apk etc. If I want to get root on this install of ICS 4.0.4 do I still need an exploit to get root? With adb I can manually move over su, busybox etc. but I can't remount system and can't put su in place and change it's perms in order to "SU". I thought that a dev edition phone was supposed to be at least partially "rooted"? Am I missing something here?
Thanks in Advance
If your on ics then there is a 1 click root in the android development section.
sent from my JokerMATRIX HD MAXX
developer edition on ICS, no root
deeje00 said:
If your on ics then there is a 1 click root in the android development section.
sent from my JokerMATRIX HD MAXX
Click to expand...
Click to collapse
I've been searching the forums off and on since January, trying to see if anyone has successfully rooted an unlocked Atrix HD developer edition, ICS 4.0.4. No luck finding anything, so this is my first post. At least I'm not the only one with this problem.
I've tried motofail2go many times but it says "exploit failed" and I verify with Root Check Basic, which confirms that it's not rooted. USB debugging is on, and I've tried it while connected as mass storage and media device. I've tried replacing adb that came in the zip file with a newer version, and also other versions of su and superuser that were suggested.
The volume up + power never seemed to give a unique vibrate; I tried it with screen lock and without, hundreds of times. I also tried running adb bugreport from a separate cmd window, which did produce a double vibration but didn't make a difference.
Is there some reason that this won't work with an unlocked bootloader?
Some of the time you can root generically, try rooting with this "universal root 4.0.4" guide.
Also your "partially" rooted I think you can try installing Super User from the play store
here.
Related
I don't run any roms just root. I received the OTA update lastnite and without thinking, I allowed it to update. I usually use SuperOneClick but that doesn't seem to work with this update. I have searched high and low and can't find any information on rooting this. Any help is appreciated.
SOLVED. I reverted to SuperOneClick 1.7 and used rageagainstthemachine and it worked after a reboot. zergRush in 2.2 doesn't seem to work against this update.
SuperOneClick 2.2.2 Will Work With FRK76 if...
I took the rageagainstthecage exploit file from SuperOneClick 1.7 and placed it in the "Exploits" sub-directory of SuperOneClick 2.2.2 and it worked as well after a reboot. Note: You'll get a warning message about it's incompatibility with Android 2.3 + (not an issue as FRK76 is 2.2.3)
Don't know what the above means
Does 2.3.1 work without modification?
While I still have my 2 year old droid, I don't have my windows computer any more. Is there any way to do this with a Mac?
Noob needing help
sir_lunatic said:
I don't run any roms just root. I received the OTA update lastnite and without thinking, I allowed it to update. I usually use SuperOneClick but that doesn't seem to work with this update. I have searched high and low and can't find any information on rooting this. Any help is appreciated.
Click to expand...
Click to collapse
Good day, I've scoured the xda dev & android forums, and haven't been able to come up with a resolution to this: I let the OTA [FRK76 - 2.2.3] update slip through, and now i'm having issues rooting.
Besides the fact i'm running linux, i refuse to use any of the one click methods.. Would rather root manually so i know what's happening.
I'm running Ubuntu & doing this all through ADB / terminal, following the instructions listed in android forums [Rooting the Droid without rsd lite up to and including FRG83D], i get to step 13 and i still see the $ & not #.
As there anyone out there who can assist?
Thanks much in advance!
sir_lunatic said:
SOLVED. I reverted to SuperOneClick 1.7 and used rageagainstthemachine and it worked after a reboot. zergRush in 2.2 doesn't seem to work against this update.
Click to expand...
Click to collapse
how does one get an older version of SuperOneClick 1.7?
envoy510 said:
Does 2.3.1 work without modification?
Click to expand...
Click to collapse
As per i know it does not.
Pete has a stock rooted FRK76 Rom on his website, fyi
My D1 seems remarkably resistant to rooting. I downloaded SOC 2.3.3, added rageagainstthecage to the exploits folder, and it still won't even really get to the "Waiting for Device" command. It kills/boots the ADB daemon then hangs. If I kill one of the ADB processes manually, I can get it to skip the automatic version check and get to "Waiting for Device" but then nothing happens there, either.
Any help (or hell, an alternate rooting method- I'd do it the long way too) would be great.
flukehawkins said:
My D1 seems remarkably resistant to rooting. I downloaded SOC 2.3.3, added rageagainstthecage to the exploits folder, and it still won't even really get to the "Waiting for Device" command. It kills/boots the ADB daemon then hangs. If I kill one of the ADB processes manually, I can get it to skip the automatic version check and get to "Waiting for Device" but then nothing happens there, either.
Any help (or hell, an alternate rooting method- I'd do it the long way too) would be great.
Click to expand...
Click to collapse
The rageagainstthecage exploit works for the FRK76 build, but I couldn't get SuperOneClick to run without crashing, so I just did it manually.
Download SuperOneClick 1.7
Extract, and use the rageagainstthecage, busybox, su, Superuser.apk with this guide: http://forum.xda-developers.com/showpost.php?p=8315805&postcount=2
The only difference is the block device /system is mounted from (the guide says mtdblock3, and I think on the droid it is mtdblock4). Just type `mount` on the command line and look for the line that has /system and check the mount path.
I used superoneclick 1.7 to root a stock frk76.
On a note to new users...if you are on windows 7, I could not get it to work. I had an old xp machine that I downloaded soc1.7 to, when I first tried to run it, my PC posted an error about .net 2.0 framework. I Google, found, and downloaded the net 2 0 framework and it worked instantly.
It did not give me recovery. I used rsdlite and only rsd recovery after I rooted it to install cwm. Once you install cwm go directly to it and flash your new rom.
For me, after I rooted and had a stock rom, my recovery would not survive a reboot. But after moving cm7 and gapps to my SD card, re-rsd recovery. Booted directly to recovery. Flashed. Once booted I went to rom manager and had it reflash cwm recovery again and it never had another issue.
My steps may sound confusing but this is what I did.
I do not have sdk setup completely on my laptop and found this to be extremely easy. It works 100% and supplied no errors. I hope this helps someone else.
Is there a RUU i can run to unroot my phone?
YoungCorruptionV2.0 said:
Is there a RUU i can run to unroot my phone?
Click to expand...
Click to collapse
No ruu on here but you can simply flash an unrooted stock rom and accept updates thru Verizon.
stkiswr said:
No ruu on here but you can simply flash an unrooted stock rom and accept updates thru Verizon.
Click to expand...
Click to collapse
Ah okay thanks for the tip. I'll look in the development section for one
YoungCorruptionV2.0 said:
Ah okay thanks for the tip. I'll look in the development section for one
Click to expand...
Click to collapse
You may be able to find it on rom manager but def can find it on peter Alfonso site
It seems that with the latest OTA update root functionality has been lost. I see that there are copies of past ROM versions available for download. Perhaps someone has the technical know-how on how to downgrade to these versions?
U need to restore with system.img using factory cable ot any other way geting fast boot mode
You don't need to downgrade the 8.9" as that is still rootable with the new version. Just re-root.
But yea get a motorola factory usb cable from ebay and and then use onelia's recovery to flash back to the previous KF2 or KFHD7 version
Nope...
DssTrainer said:
You don't need to downgrade the 8.9" as that is still rootable with the new version. Just re-root.
But yea get a motorola factory usb cable from ebay and and then use onelia's recovery to flash back to the previous KF2 or KFHD7 version
Click to expand...
Click to collapse
I'm going to have to agree with the initial poster on this thread and say that if your firmware is at 8.1.4, The Bin4ry root is NOT working. I've ran it several times even after a full factory erase / restore, and throughout the entire process all I keep seeing is "permission denied", etc., all indicating that it was unsuccessful. For example, in the terminal step where you type in the 2 commands.. BOTH said "file not found", telling me that the file was never allowed to enter the device in the first place.. in other words, blocked. YES, the process does indeed finish, but su access is certainly not there. I can side-load apks of course, etc... but any apps requiring root access do NOT work.
I have found a way to manually block OTA updates, so if someone can figure out a way to downgrade the firmware back a couple versions, I think we'll be in business.
Please don't take this post as any sort of insult to anyone's intelligence, but I'm just relaying my experiences with the Bin4ry root process. I hope we as a community can come up with a way around this so we can get some custom roms onto this beast soon. cheers.
The binary root still works as of 8.1.4. If you read the entire post for the root process, all the permission denied and file not founds are normal. The root takes advantage of the restore process. I rooted an hd 8.9 today running 8.1.4 with no problems. So unless you guys have the only two hd 8.9's that Amazon changed the software...
I can also confirm that it still works on 8.14.ive rooted about a dozen times now, don't ask you'll be bored. I've also downgraded to 8.13 without any trouble, or factory cable, and rooted afterward. That said, I did let it OTA after downgrading. Again, don't ask.
Peace
Sent from my KFJWI using xda premium
Root and Google Play for Amazon 7" Kindle Fire HD Software Version 8.1.4
fuyoo said:
It seems that with the latest OTA update root functionality has been lost. I see that there are copies of past ROM versions available for download. Perhaps someone has the technical know-how on how to downgrade to these versions?
Click to expand...
Click to collapse
fuyoo,
There is no need to downgrade, Software version roots just fine, see:
http://forum.xda-developers.com/showthread.php?t=2069117
If you get a file not found error:
http://forum.xda-developers.com/showthread.php?t=2086210
I have a feeling that I should probably post a thread of this nature in the development subforums, however I have nothing to present. What I'm looking to do is either modify an existing or build a new script which will root the Bell version of the Atrix HD which is on Jelly Bean. As many of you may know, the methods using Ubuntu, Motofail2Go and the various other options do not work. However they work partially for us. For example, when using Ubuntu I can get the message that I have rooted the device but it cannot copy the certain files (busybox, etc) to the device. On the other hand, MotoFail2Go also works to a certain extent, installing the sudoku.apk and the like, but the root either doesnt work or stick. With this being said, my question is how can I go about modifying any of these scripts or methods to work with 4.1.2 or is there anything I can do to help a developer with this issue? Any direction would be appreciated, whether it is me working alone on this project or with the help of other developers and community members.
Those other apps stick around because they're pushed to a writeable temp folder. If the exploit isn't working, I'm not sure tweaking a script will do anything to help.
Have you tried any other root methods?
The GS4 just got rooted and it hasn't even been released yet
Markyzz said:
Those other apps stick around because they're pushed to a writeable temp folder. If the exploit isn't working, I'm not sure tweaking a script will do anything to help.
Have you tried any other root methods?
The GS4 just got rooted and it hasn't even been released yet
Click to expand...
Click to collapse
As of now I've tried all of the published ways here on XDA and nothing seems to work for 4.1.2 yet it works for 4.1.1 which is why I thought that it would be possible to tweak one of the exploits in whichever way needed to root this slightly different (as it would seem) firmware. I'm not sure where exactly where to start looking when it comes to rooting the device, any help would be appreciated. Which files do I need to have on my device and where do I need to have them in order to obtain root?
So from the beginning I updated from notification on phone from 4.0.4 to 4.1.2. Then bricked after trying to gain root acess. Finally able to flash jb 98.72.22. Tried for days to find a root that worked. Couldn't get motochopper to gain root. Tried god knows how many others. Finally got virtual box, imported Root_Bionic_JB.ova and still wouldn't work. Keep coming across su binary issues. The closest i got was with the virtual box installing superuser. But when I trying to update the binary says unable and to send a log report. What am i doing wrong? is it a step im missing when unzipping to desktop? everything goes smooth until cmd gets to rooting, then says failed. cleaning. press enter to reboot and close. Im about to lose my mind! Please some assistance. I sick of failing every attempt from every suggest forum (quietly sobbing )
You need to go back to what has been proven to work. Moto chopper 2. Not to be insulting BUT I know from experience, just BC you can't get something to work the first couple of times you try it doesn't mean it does not work. Period. Now, where did you get hung up on the Ubuntu exploit? List all that you did.
Sent from my XT875 using xda premium
linux minimal screen shot, and unbuntu hang up
DanRyan85 said:
You need to go back to what has been proven to work. Moto chopper 2. Not to be insulting BUT I know from experience, just BC you can't get something to work the first couple of times you try it doesn't mean it does not work. Period. Now, where did you get hung up on the Ubuntu exploit? List all that you did.
Sent from my XT875 using xda premium
Click to expand...
Click to collapse
Well, not to be insulting, but it was my understanding that moto chopper would only work if temp rooted or had gained root acess previously? I may be wrong. Anyways, the prob. with unbuntu is thing i guess froze (but still ran) after patiently running it like six hours. Last screen at was installing-reinstalling previous "somethings" but I figured need a system clean and would try again. gotta be easier way. so here is my linux minimal screenshot attempt. running root bionic jb ovf file. noticed where it starting going wrong is
chmod: pwn: operation not permitted.
rooting phone...
phone may appear to.......
/system/bin/sh: /storage/rfs0/pwn: not found <-------Right here i noticed the file path on the phone and it's ---> storage/rfs1 Would that have something to do w/ it?
nothing ever vibrates and reboots in flash. got bad flash or something?
MotoChopper works on non TI (OMAP) CPus that are in Motoroal devices.
Coincidentally, it also works on ASUS Tranformer Infinity (and the Prime as well, IIRC).
It does not work on the BIONIC.
The method that works on rooting the JB build on the BIONIC is one that is based upon the older RAZR method - see http://www.droidrzr.com/index.php/topic/16518-root-motoshare-2-old-bug-new-exploit/
Bionic and JB OVA flash superuser binary outdated
Naughtybutbritt said:
So from the beginning I updated from notification on phone from 4.0.4 to 4.1.2. Then bricked after trying to gain root acess. Finally able to flash jb 98.72.22. Tried for days to find a root that worked. Couldn't get motochopper to gain root. Tried god knows how many others. Finally got virtual box, imported Root_Bionic_JB.ova and still wouldn't work. Keep coming across su binary issues. The closest i got was with the virtual box installing superuser. But when I trying to update the binary says unable and to send a log report. What am i doing wrong? is it a step im missing when unzipping to desktop? everything goes smooth until cmd gets to rooting, then says failed. cleaning. press enter to reboot and close. Im about to lose my mind! Please some assistance. I sick of failing every attempt from every suggest forum (quietly sobbing )
Click to expand...
Click to collapse
I am having same issue. Using Marty OVA in virtual box. works great, no issues w/ samba or USB. Root is successfully run. however.
root checker indicated that I am not rooted and as mentioned above, superuser needs to update the binaries.
" the Superuser binary (su) must be updated
please choose an installation method
recovery mode installation is recommended for HTC devices.
Cancel <> Recovery Install<> Install
hit install
there was an error installing superuser. Please send a log of the error to the developer.
<ok>
wonder if I could replace the superuser.adk file in the /home/guest/share directory with a newer adk file?
could not get post on droidrzr.com on a thread there. ( link not permitted by Noobs )
Marty45714 informed us He posted this here as well. can anyone answer this?
T
To Naughty: Sorry about the mix up that was what I meant to say Moto share 2 NOT Motochopper. I had all the same problems as you after some number of tries with motoshare2 I was in business.
To martin: have you already tried the motoshare 2 on Ubuntu?
Sent from my XT875 using xda premium
toddmartin- you're gonna love me...i gotcha
toddmartin said:
I am having same issue. Using Marty OVA in virtual box. works great, no issues w/ samba or USB. Root is successfully run. however.
root checker indicated that I am not rooted and as mentioned above, superuser needs to update the binaries.
" the Superuser binary (su) must be updated
please choose an installation method
recovery mode installation is recommended for HTC devices.
Cancel <> Recovery Install<> Install
hit install
there was an error installing superuser. Please send a log of the error to the developer.
<ok>
wonder if I could replace the superuser.adk file in the /home/guest/share directory with a newer adk file?
could not get post on droidrzr.com on a thread there. ( link not permitted by Noobs )
Marty45714 informed us He posted this here as well. can anyone answer this?
T
Click to expand...
Click to collapse
Ok so using virtual box the ova Root_Bionic_JB_20130501-4 the fourth ubdate of the orginal release. Now i suggest erasing all superuser apps installed your self and anything to do with them. When it's done right, it will appear on it's own and work flawlessly. No uncertianties about it. Then i've posted a screen shot of the commands with notes to help understand easiest. The instant the command to press hardware key or power/or each volume itself is the instant you want to press it. Now the reboot is instantious kinda itself and gotta be noticing phone unless have ungodly long boot up let me know if the screen shot helped what you were asking.
UPDATE:
So I'm trying the reddit instructions again, and I'm making more progress than before. Here's where I'm at now: Everything works flawlessly until I get to step 19. I get a message saying "can't create /sys/kernel/uevent_helper: Permission denied" and my phone never reboots. I've browsed through the comments there and everyone else who gets hung up there just repeats previous steps and has it work (which I've tried) or can't remember how they got it to work. I thought I'd reach out here and see if anyone has any suggestions now.
==================================================
Hey everyone, I've been desperately trying to root my Moto X and I just can't get it to work. I ordered mine about a week ago and I've spent the last two days tinkering away with no success. I've rooted my Droid X and my Droid Razr Maxx in the past, so I would say I have a moderate level of understanding, but I'm stumped by this one.
I tried going the easy route using the Moto X Root Script but it continuously failed for me. I would have posted there, but unfortunately since I'm not the most active user, I haven't even made it to the 10 posts mark so I'm not allowed to... so then I took to the internet and used these instructions I found on Reddit to run through RockMyMoto manually followed by MotoWpNoMoto. I successfully achieved root on 4.2.2 and then accepted the OTA to move to KitKat. However, my phone went into a boot loop and I couldn't get it to respond to anything, so I flashed back to 4.2.2 to try running through the process again. Now, I can't get it to root on 4.2.2 anymore, and I'm not sure what's going wrong.
MotoWpNoMoto does tell me that write protection is already removed, but I'm still not getting anywhere. After flashing back to a clean 4.2.2, I try running the first part of SlapMyMoto, and it says it's all successful, but then when I accept the OTA and try to proceed to the second part of it where you push install.sh, I get an error saying "Install script failed! You received a Permission Denied error while attempting to load the install script into the UEVENT_HELPER. This means that root was not successfully obtained." If I try downloading SuperSU from the marketplace, it tells me no SU binary is installed and the SuperSU can't install it.
Does anyone have any ideas on where to go from here?
pianoman674 said:
Hey everyone, I've been desperatley trying to root my Moto X and I just can't get it to work. I ordered mine about a week ago and I've spent the last two days tinkering away with no success. I've rooted my Droid X and my Droid Razr Maxx in the past, so I would say I have a moderate level of understanding, but I'm stumped by this one.
I tried going the easy route using the Moto X Root Script but it continuously failed for me. I would have posted there, but unfortunately since I'm not the most active user, I haven't even made it to the 10 posts mark so I'm not allowed to... so then I took to the internet and used these instructions I found on Reddit to run through RockMyMoto manually followed by MotoWpNoMoto. I successfully achieved root on 4.2.2 and then accepted the OTA to move to KitKat. However, my phone went into a boot loop and I couldn't get it to respond to anything, so I flashed back to 4.2.2 to try running through the process again. Now, I can't get it to root on 4.2.2 anymore, and I'm not sure what's going wrong.
MotoWpNoMoto does tell me that write protection is already removed, but I'm still not getting anywhere. After flashing back to a clean 4.2.2, I try running the first part of SlapMyMoto, and it says it's all successful, but then when I accept the OTA and try to proceed to the second part of it where you push install.sh, I get an error saying "Install script failed! You received a Permission Denied error while attempting to load the install script into the UEVENT_HELPER. This means that root was not successfully obtained." If I try downloading SuperSU from the marketplace, it tells me no SU binary is installed and the SuperSU can't install it.
Does anyone have any ideas on where to go from here?
Click to expand...
Click to collapse
I we to assume you have a consumers version and not the developer edition?
Sent on my Gummy running Lenoto X
flashallthetime said:
I we to assume you have a consumers version and not the developer edition?
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
That is correct, sorry I forgot to put that in there.
32 GB Consumer on Verizon, Came with KitKat preinstalled.