Finally there is some good news for Motorola Devour owners waiting for a root to emerge. It is noticeable that Motorola Devour root procedure is the same as rooting Motorola Droid X with only some minor changes. The rooting method for devour is working fine but we are still not sure whether a custom ROM has been flashed after achieving the root.
Here is the step by step guide on rooting your Motorola Devour direct from Android Forums. Please note that this procedure is only intended for advanced users meaning that you should have ample hands on rooting experience before embarking on this guide.
This whole set of instructions was lifted directly from the instructions
on how to root the Droid X with a few edits here and there.
(Run means type the command in quotes [but not the quotes] then press the Enter key)
1.Download the attached archive and expand it to a folder you can find (eg. c:\devour_root)
2.Set up ADB (You’ll need to google this part)
3.On the phone: Home, Menu Button, Settings, Applications, Development: Make sure the “USB debugging” option is enabled/checked.
4.Status bar, USB connection: Make sure “PC Mode” is selected.
5.Open a command prompt (Windows: Start, Run, “cmd”, OK; Linux: Terminal)
6.Run “adb devices”. If you don’t see your device listed under “List of devices attached”, return to step 2 and follow the link to setup ADB (use that topic for support) and return here when “adb devices” lists your X.
7.Run “CD c:\devour_root” (or where ever you expanded the archive)
8.Run “adb push Superuser.apk /sdcard/Superuser.apk”
9.Run “adb push su /sdcard/su”
10.Run “adb push busybox /sdcard/busybox”
11.Run “adb push exploid /sqlite_stmt_journals/exploid”
12.Run “adb shell”
13.Run “cd sqlite_stmt_journals”
14.Run “chmod 755 exploid”
15.On your phone, navigate to a screen where you can switch wifi/bluetooth on/off easily (settings, or a home screen with a widget)
16.IMMEDIATELY after executing the next step, toggle wifi or bluetooth off and back on
17.Run “./exploid” and follow directions on screen. Once this completes you’ll be back at a shell prompt.
18.Run “rootshell”. You’ll be prompted for a password.
19.Type in password “secretlol” and press Enter then you are root! (You’ll know because your prompt will now be a “#” instead of “$”)
20.Run “mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system”
21.Run “busybox cp /sdcard/Superuser.apk /system/app/Superuser.apk”
22.Run “busybox cp /sdcard/su /system/bin/su”
23.Run “busybox cp /sdcard/busybox /system/bin/busybox”
24.Run “chmod 4755 /system/bin/su”
25.Run “chmod 4755 /system/bin/busybox”
26.Run “rm /system/bin/rootshell”
27.Run “exit” to drop from root to a non-root user shell (on phone still)
28.Run “exit” to drop back to your machine command prompt (instead of phone)
To Confirm root is established:
Run “adb shell”
Run “su” (now you should see the # sign which indicates you are root)
Watch your screen so you can allow Superuser root access.
You’re done! feel free to kill the bloat apps and such. (I haven’t tested killing anything yet.)
NOTE: It might be a smart idea to do “rm /system/bin/rootshell” after you have su and superuser in place as ANY program will have access to your root if you leave it (cause everyone will know the password)
NOTE: If the ‘busybox cp’ commands do not work try
“dd if=/sdcard/Superuser.apk of=/system/app/Superuser.apk”
“dd if=/sdcard/su of=/system/bin/su”
“dd if=/sdcard/busybox of=/system/bin/busybox”
-added busybox in front of the cp commands
-mounted the system read write
-changed out Birdman’s su and Superuser.apk to the ones from xda-developers – View Single Post – [APP] Superuser 2.2.2 – Install fixed (really this time) [2010-07-07]
Birdman for rooting the Droid X
ChainsDD for posting the su and Superuser.apk files.
Credits (Originally posted on
AllDroid(link not available anymore))
Sebastian Kramer for this blog post – https://c-skills.blogspot.com/2010/07…-trickery.html
Birdman – for editing Sebastians work for the droidx
[mbm] – for answering birdmans many questions while root was tried (and failed xD)
And of course if anything goes wrong and breaks it is no ones fault but your own. XD
BTW: I’ve only tested this on my Devour. Your mileage may vary.
Disclaimer: Please attempt this guide at your own risk. AddictiveTips won’t be responsible in case your device bricks or any other damage occurs due to this method.