Update:
I'm leaving this post here for posterity's sake, but an easier root method is now available at:
http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit/
The package may be downloaded at http://vulnfactory.org/public/motochopper.zip
---
As promised, this post describes how to root the Atrix HD Jelly Bean build. This should also work on other Motorola 4.1.2 builds (Razr/Razr Maxx, Razr HD, Razr M, etc.).
The exploit requires setting up a special Samba share and mounting this share on your phone using the File Manager app. I apologize that this process may seem involved for some of you, and request that members of this community help each other out if some of you are having problems completing the procedure. I'm not able to provide individual tech support to every user who wants to root this phone.
The following instructions require a working Linux installation. The following instructions are for Ubuntu. If you don't want to install Ubuntu permanently on your machine, I suggest using a LiveCD installation. Instructions on setting this up are described here:
https://help.ubuntu.com/community/LiveCD#How-To_LiveCD_Ubuntu
Once you're booted into Ubuntu, open a terminal. Create a new directory for your Samba share:
Code:
mkdir /tmp/share
Next, install the samba package:
Code:
sudo apt-get install samba
Edit the configuration file for samba:
Code:
sudo gedit /etc/samba/smb.conf
Add the following lines to the end of the configuration file and save your changes:
Code:
[share]
path = /tmp/share
available = yes
valid users = guest
read only = yes
browsable = yes
public = yes
Close the text editor once you've saved your changes.
Next, create a user for the Samba share by typing in the terminal:
Code:
sudo useradd guest -m -G users
Set a password for the new user. Remember this password:
Code:
sudo passwd guest
Provide a password here and press enter. You won't see the characters you're typing, so be careful.
Next, set a password on the share. Use the same password you just provided:
Code:
sudo smbpasswd -a guest
Type the password you created before and press enter.
Next, restart the Samba server:
Code:
sudo restart smbd
Finally, download and prepare the required files to the Samba share:
Code:
cd /tmp/share
wget [url]http://vulnfactory.org/public/motoshare.tgz[/url]
tar xvf motoshare.tgz
sudo chown root:root pwn
sudo chmod 6755 pwn
At this point, you'll need to know the IP address of your Linux host, which you can get by running "ifconfig" from your terminal (it should be of the form "192.168.x.x").
Next, move over to your Android device. Ensure you have enabled USB Debugging Mode (under Settings -> Development Settings). Ensure your device is connected via Wifi.
Open the "File Manager" app, and select "Remote storage". Click "Add storage", and fill in fields as follows:
Code:
Host IP address: [your Linux machine's IP address]
Domain name: WORKGROUP
Shared folder name: share
User: guest
Password: [the password you created above]
At this point, the phone will mount your Linux share. To complete the process, plug in your phone via USB to your Linux machine, and type the following in your Linux terminal:
Code:
sudo /tmp/share/adb kill-server
sudo /tmp/share/adb shell /storage/rfs0/pwn
If it's successful, this should print "[+] Rooting complete!".
Finally, install Supersu by typing the following in the terminal:
Code:
sudo /tmp/share/adb install /tmp/share/eu.chainfire.supersu.apk
Congratulations, enjoy your rooted device.
I can't stress this enough: I can't provide individualized tech support for everyone on this forum. Please help each other.
TTLayland has been successfully rooted using this technique and has volunteered to help. If you get stuck and can't find support on these forums, feel free to email him at ttlayland (at) gmail (dot) com.
Paypal:
http://goo.gl/zBGb0
Email sent
Sent from my MB886 using xda app-developers app
Email sent
Sent from my Atrix HD using Tapatalk app
Email sent
Sent from my MB886 using xda premium
Email sent. Donation sent
Email and donation sent!
Has anybody gotten the files yet
Sent from my MB886 using xda premium
No. Wait for some hours.
Ok
Sent from my MB886 using xda premium
Pls, if someone will received answer from Dan, let us know please!
Ok, everybody is going to need to wait a bit while I sort out some technical issues. Don't worry, the exploit is already confirmed to work, it's just a matter of making it possible for you all to easily use it.
Sorry if i'm in the wrong thread, but will this exploit work on xt925? It would be great for future development on our phones. I see that devs confirm that atrix HD and RAZR HD are the same phone
Sent from my XT925 using xda app-developers app
uropb said:
Sorry if i'm in the wrong thread, but will this exploit work on xt925? It would be great for future development on our phones. I see that devs confirm that atrix HD and RAZR HD are the same phone
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
XT925 have unlocked bootloader = you can flash insecure kernels and easily get root.
I thought I would be able to do this via email, but it's not going to be possible. I've updated the top post with detailed instructions on the exploit. Good luck.
I will help out all XDA members with is process.
Only afte finishing the process with Dan helping me along.
DO NOT BOTHER HIM WITH A MILLION PMS OR EMAILS.
He has done so much or us. I will take over for tech support and anyone with good Linux experience can help too.
OMG Linux... Maybe windows version will be available? But thanks a LOT for that!!!
+1 for windows version it sounds like it should be easy to port it to windows
Sent from my MB886 using xda premium
joejoejo said:
+1 for windows version
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
There is a technical problem in doing a windows version from what I understand. Its not that difficult to boot a Linux LiveCD or LiveUSB don't even have to install it on your computer.
EDIT: If you need help post it here
Sent from my Galaxy Nexus using Tapatalk 2
Sweet, thanks for the updated post. Can't wait to get back from work and give this a whirl
What's the technical problem in windows
Sent from my MB886 using xda premium
Related
I need to install my own APK on a Android 2.1 emulator, how do i do this?
What i need is to have the Emulator burned onto a CD, and when you open en Emulator file, it will start up containing my APK.
Maybe this is really a question for the forum Android development
-------------------------------------
Sent via the XDA Tapatalk App
Install via adb
adb -e install myapk.apk
Make sure the app receives the startup intent and shows the main activity when it does
Wow that easy? Thanks alot
-------------------------------------
Sent via the XDA Tapatalk App
Any idea where is located a swype dictionary ?
thanks
I would like to know this too, as swype often adds stupid things, like the end of a bit.ly link to my dictionary.
PS, this topic should be in the SGS general forum?
sorry to bring up old thread.
no one figure it out yet ? I don't want to teach swype new word every time I flash rom.
Agreed! I would like to avoid that as well!
/data/data/com.swype.android.inputmethod/
But you need a rooted phone to back up that dir.
Sent from my GT-I9000 using XDA App
[email protected] said:
/data/data/com.swype.android.inputmethod/
But you need a rooted phone to back up that dir.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I'm running a ROM w/ root and cannot back this up.
From my computer, this is what I do from command prompt:
adb shell
# cp /data/data/comblahblahblah /sdcard/blahblah
Operation not supported
#
Basically is what happens
Why can't I download certain mms it tells me download was unsuccessful I don't get it. I'm running aosp rom latest version and handcent app.
Sent from my HERO200 using XDA App
its a bug running our heros on froyo
There's no fix?
Sent from my HERO200 using XDA App
only fix I know is run sense based rom. As far as a fix for froyo others will need to chime in.
xjayman said:
its a bug running our heros on froyo
Click to expand...
Click to collapse
I've never heard of this bug nor had any problems with MMS
If you're having problems with mms try clearing out the telephony database
Code:
adb remount
adb shell
rm /data/data/com.*.*.telephony/databases/telephony.db
adb reboot
Can u give me a little step by step please? I really just know the basics on this phone thanks
Sent from my HERO200 using XDA App
1tondiesel said:
Can u give me a little step by step please? I really just know the basics on this phone thanks
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Acutally seeing as the majority of rooted people probably just use the 'one click' apps it'd be easier to do this via Terminal Emulator.
Download Termial Emulator if you don't already have it on your phone
Open up terminal emulator
Then type out the following code box (at the end of each line you press 'Enter')
Code:
su
rm /data/data/com.*.*.telephony/databases/telephony.db
reboot
1tondiesel said:
Why can't I download certain mms it tells me download was unsuccessful I don't get it. I'm running aosp rom latest version and handcent app.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Try this Froyo MMS fix in my sig, just flash it from recovery
I tried it and it said it could not be found
Sent from my HERO200 using XDA App
1tondiesel said:
I tried it and it said it could not be found
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
What do you mean could not be found? Did you flash it?
No not yours I flashed your fix it didn't work I'm talking about kyouko
Sent from my HERO200 using XDA App
1tondiesel said:
I tried it and it said it could not be found
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
The location should exist...unless it was typed incorrectly or you have an incomplete flash /data/data/com.android.providers.telephony/databases/ should definitely be there.
If you have root explorer or estrongs files explorer with root access you can navigate to that location and delete using those apps too. Rebooting will rebuild the telephony.db file after its deleted.
If you still are having problems trying to find the database file send me a PM and I'll help you out when I can on gtalk.
Edit: Do this, open up terminal emulator and enter these lines in
Code:
su
cd /data/data/com.*.*.telephony/databases
ls
You should get a return line saying
Code:
mmssms.db telephony.db
And then reboot phone?
Sent from my HERO200 using XDA App
1tondiesel said:
And then reboot phone?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
If you're referring to my previous post where you navigate to the directory and enter "ls" to list the files in that directory, then no. Thats just to see if the files are indeed there.
If they are, then you should do that "rm" command I posted before where you delete the telephony.db
If they both weren't there, even after a reboot, then as I said before - either the command wasn't typed in correctly, or the flash was incomplete.
Post what the 'ls' command returned to you after entering it in (ie. mmssms.db and/or telephony.db)
Its telling me not found after I enter "telephony databases"
Sent from my HERO200 using XDA App
Well I got that command to work that deletes the telephony DB but I still cant download certain mms it says download was unsuccessful
Sent from my HERO200 using XDA App
Am I the only 1 who can't download mms on this phone?
Sent from my HERO200 using XDA App
Certain mms types will not work unless you're on a stock based rom. I believe it is the slideshows that are the problem.
Sent from my HERO200 using XDA App
According to some sources from AT&T's Developer site, the Atrix HD was supposed to originally be on 4.0.3 instead of launching 4.0.4. If someone happened to find an Atrix HD (maybe a display model, or a pre-release model) running 4.0.3 instead of 4.0.4... root it and extract the boot.img (kernel) for us
How to extract boot.img (once rooted)-----------
From a computer with latest Motorola drivers installed on Windows, or a linux machine with android-sdk setup:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p31 of=/sdcard/boot.img
From the free "Android Terminal emulator" app from the Play Store:
Code:
su
dd if=/dev/block/mmcblk0p31 of=/sdcard/boot.img
After you get that boot.img on the sdcard with that command, you can go to the pre-installed "Files" app > Device Storage, and email that boot.img to yourself or to someone who can get it on here (xda).
To root android 4.0.3 use:
*403root.zip (Uses TPSparky exploit)
if that fails for some reason...
*DroidRazrRoot404.zip (Razrsedge by Dan Rosenberg)
Latest Motorola USB drivers can be found at:
64: http://developer.motorola.com/tools/usb_drivers/handset_usb_driver_64/
32: http://developer.motorola.com/tools/usb_drivers/handset_usb_driver/
If you can... check around AT&T stores or cell stores and see if their display models are 4.0.3. It's a longshot, but this would hopefully get those on 4.0.4 Rooted
More cases of 4.0.3 spottings, rare as they are:
http://whatsmyua.com/ua/Mozilla/5.0... like Gecko) Version/4.0 Mobile Safari/534.30
Hmm.. interesting. Surely someone has a 4.0.3 version. Although I bought mine from Best Buy a week after it was released and it already had 4.0.4 loaded.
Maybe a Google search might help us.. I'll see what I can dig up.
Sent from my MB886 using xda app-developers app
busarov said:
Hmm.. interesting. Surely someone has a 4.0.3 version. Although I bought mine from Best Buy a week after it was released and it already had 4.0.4 loaded.
Maybe a Google search might help us.. I'll see what I can dig up.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
I didn't add this to the OP, but there is also a slight chance of engineering devices sold as retail. If you go into AP Fastboot and you see Status 1: UNLOCKED then its a special device which can easily be rooted.
mattlgroff said:
I didn't add this to the OP, but there is also a slight chance of engineering devices sold as retail. If you go into AP Fastboot and you see Status 1: UNLOCKED then its a special device which can easily be rooted.
Click to expand...
Click to collapse
Yeah I noticed mine said "Locked" the other day when I installed those other kernels. Now it makes sense.
If only we were lucky enough to find someone with one of these elusive devices.. Kinda like looking for a needle in the ocean..
EDIT: So, question... What are the other menu options in the recovery menu? Such as, BP Tools.. Could there be an exploit hidden in one of them?
Checking what I'm on now
Sent from my MB886 using xda premium
%appdata% said:
Checking what I'm on now
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
What'd you find out?
Sent from my MB886 using xda app-developers app
Not 4.0.3 D=
Sent from my ATRIX HD using xda premium
Might as well just type this here, how do I get rid of this 5 minute lock in-between posts ? Very annoying
I got my phone a day after release and I still have 4.0.4
Kedakari said:
I got my phone a day after release and I still have 4.0.4
Click to expand...
Click to collapse
I should restate this thread, there SHOULD be devices on 77.8.18.MB886.ATT.en.US.
This is the version on AT&T's website for teaching you how to check your system version.
There is a chance this is a rootable system version and it only got patched going to 77.10.16.
If in theory, this version was rootable with the current exploits then the boot.img could be extracted and flashed onto the Atrix HD via the little utility I have or manually through fastboot commands.
This is how I am able to keep root on the DROID RAZR with the 4.0.3 exploit even though we are on 4.0.4. Flashing the 4.0.3 boot.img and rooting with that, then flashing back the 4.0.4 for stability. I hope the same theory could be applied here. Unfortunately 77.8.18 seems the be the farthest back I could find and its 4.0.4 still... but the point can still stand. If anyone wants to check out the update.zip from 77.8.18 to 77.10.16 (stock) then you can find it here:
Download 77.8.18 -> 77.10.16:
http://crackflasher.com/dev/mattlgroff/MB886.ATT.en.US/Blur_Version.77.8.18.MB886.ATT.en.US.zip
Remember, Motorola names their update.zip after the version you were ON, not the one you are going to.
I know this might be a really dumb question but ill ask anyways..
Is there anyway i can run an htc vivid in virtual box?or some other kind of thing like that?
i tend to brick my phone a lot trying all these dumb things so i want
to find a way to test them somehow before i do it on my phone so i dont have to keep recovering it.
any help or ideas?
You can run android in an emulator but not for an exact phone
Sent from my HTC Holiday using xda premium
ZeRo2o9 said:
You can run android in an emulator but not for an exact phone
Sent from my HTC Holiday using xda premium
Click to expand...
Click to collapse
So I can't let's say, tweak a ROM and see if it'll run?
Sent from my HTC PH39100 using xda app-developers app
its called android x86
http://www.android-x86.org/
choose the asus ones because they usually are more compatible with other computers. you might have a problem with wifi though and will have to find a way to install the wifi drivers for your wifi antennae onto android.
DONT FORGET TO THANK MEE )
XxSHaDoWxSLaYeRxX said:
its called android x86
http://www.android-x86.org/
choose the asus ones because they usually are more compatible with other computers. you might have a problem with wifi though and will have to find a way to install the wifi drivers for your wifi antennae onto android.
DONT FORGET TO THANK MEE )
Click to expand...
Click to collapse
Thanks I'll try it out soon. I just gotta wait til I got some time
Sent from my HTC PH39100 using xda app-developers app
That's not running vivid software
Sent from my HTC PH39100 using xda premium
Apparently you can do this from the SDK emulator if you have the ROM in system.img format (which I believe dsixda's kitchen can do, don't remember off the top of my head). Probably won't work with an extracted system image though, but I've never tried so can't confirm.. anyway
Windows PC
1. Download the Android SDK (which includes the emulator) from here.
2. Extract the downloaded zip.
3. Run a command prompt, and change to the 'tools' directory of the SDK (or add the tools directory to your path).
4. Type 'android list target'
5. Note the 'id' number of the '1.5' target (in my case it's '2')
6. Type 'android create avd -n enhanced -t 2' (substitute 2 with the target number determined above if required)
7. You will be prompted to create a hardware profile. This is optional, but I selected 'yes' and accepted the defaults for everything except RAM, where I gave it 256MB.
8. Download your system.img
9. Copy the above file to the location of the enhanced.avd directory ('C:\Documents and Settings\\.android\enhanced.avd' on Windows XP, and 'C:\Users\\.android\enhanced.avd' on Windows Vista).
10. You're ready! Type 'emulator -avd enhanced' to run! Note: inital boot may take a few minutes!
If you get Java errors, you need to download the JDK for your system
Mac OSX
1. Download the Android SDK (which includes the emulator)
2. Extract the downloaded zip.
3. Run Terminal, and change to the 'tools' directory of the SDK (or add the tools directory to the path settings in ~/.profile).
4. Type './android list target'
5. Note the 'id' number of the '1.5' target (in my case it's '2')
6. Type './android create avd -n enhanced -t 2' (substitute 2 with the target number determined above if required)
7. You will be prompted to create a hardware profile. This is optional, but I selected 'yes' and accepted the defaults for everything except RAM, where I gave it 256MB.
8. Download your system.img
9. Copy the above file to ~/.android/avd/enhanced.avd/system.img (e.g. if you saved it to and unzipped it to downloads enter 'cp ~/Downloads/system.img ~/.android/avd/enhanced.avd/system.img')
10. You're ready! Type './emulator -avd enhanced' to run! Note: inital boot may take a few minutes!
If you get Java errors, you need to download the JDK for your system
ZeRo2o9 said:
That's not running vivid software
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Vivid runs android. Android x86 is android. You can always add in sense etc. After so yeah
Sent from my HTC PH39100 using xda app-developers app
XxSHaDoWxSLaYeRxX said:
Vivid runs android. Android x86 is android. You can always add in sense etc. After so yeah
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
Which option would you recommend for someone new to all this?
The androidx86 option or the other android sdk one?
Sent from my HTC PH39100 using xda app-developers app
eddied042092 said:
Which option would you recommend for someone new to all this?
The androidx86 option or the other android sdk one?
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
android x86. easy for n00bs, which i am assuming you are lol (no offense).
Guide located HERE: http://gbatemp.net/threads/how-to-dual-boot-android-with-almost-any-os.320554/
I was just saying android versions are different you'd need the HTC libs and framework for the vivid or else its jus vanilla android like a nexus
sent from my HTC Vivid
Yea ik sorry lol but technically if you added in those frameworks you'd have sense yay xD
Sent from my HTC PH39100 using xda app-developers app