1. Home
  2. Mobile
  3. How to root motorola i1 adb method

How To: Root Motorola i1 [ADB Method]

Finally there is some great news for Motorola i1 users waiting to root their handsets. GotHeart at CyanogenMod Forum has achieved root through conventional ADB method. There is no single click root available until now for i1, but we can speculate it to surface real soon. Here is the step by step guide on rooting your Motorola i! but please only try this if you are comfortable with ADB based rooting.

CAP201008291028

1. The first step is to install ADB along with Motorola drivers. After you have installed ADB, it is recommended but not essential to add “Tools” to your drive path.

2. Once you have installed the above mentioned goodies, download Motorolai1-Root.zip file, extract and save on C drive Root i.e. C:\I1RootFiles.

3. Connect your Motorola i1 to the computer and run command prompt [Start > Run> cmd].

4. Now type The following commands In Command Prompt[ This will push all necessary files to your handset’s SD card]:

  • adb devices
  • adb push C:\I1RootFiles\Superuser.apk /sdcard/Superuser.apk
  • adb push C:\I1RootFiles /sdcard/su
  • adb push C:\I1RootFiles\rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
  • adb push C:\I1RootFiles\Install-Root-sh /data/local/tmp/Install-Root.sh
  • adb push C:\I1RootFiles\busybox /sdcard/busybox

5. Now you have all the files needed for rooting on your handset’s SD card. After this, Type the following commands in command prompt:

  • adb shell
  • cd /data/local/tmp
  • chmod 0755 rageagainstthecage-arm5.bin
  • chmod 0755 Install-Root.sh

6. Wait for the installation to finish and keep your phone connected to computer.

7. Once the installation is complete, launch Market and download ConnectBot Terminal.

8. Now open ConnectBot on your phone and type:

  • cd /data/local/tmp
  • /rageagainstthecage-arm5.bin

9. Now wait until [+]Forked XXXX Childs message appears.

10. Once you see the message mentioned above, type exit to close ConnectBot Terminal.

11. Once this is done, re launch ConnectBot on your phone and type:

  • /data/local/tmp/Install-Root.sh
  • exit
  • exit

12. After running the commands mentioned above, you will see # sign instead of $. If this is the case, then you have successfully rooted your phone.

13. Now reboot your phone through ConnectBot by typing:

  • #Sync
  • #reboot

There are no custom ROMS available until now but with root achieved, the possibilities are virtually limitless, so Enjoy!

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.

default avatar image
Read Full Bio
Ali Waqas
Latest from Author
Microsoft Teams Background Blur During Video Calls (GUIDE) HDMI Port Not Working in Windows 10: How to Fix HDMI Output Problems

239 Comments

  3. this is the worst list of instructions i have ever read by far!!!! this list of instructions should be reposted. i have followed every step possible and that thing i read up there by “ssrrgg” which may it do something in dos but thats it and i didnt get the message they said up about the XXXX or whatever. now i got gotta look else where. i will post something when i find it. if you dont know how to post or blog ask someone . damn this is annoying to get this far and not be able to finish!!!

  4. Everything goes fine until i run the Install-Root.sh I get this:

    # ./Install-Root.sh
    ./Install-Root.sh
    ./Install-Root.sh: cannot create /system/xbin/busyboxchown: read-only file syste
    m
    ./Install-Root.sh: cannot create /system/xbin/su: read-only file system
    Unable to chmod /system/xbin/su: No such file or directory
    Unable to chmod /system/xbin/su: No such file or directory
    ./Install-Root.sh: cannot create /system/app/Superuser.apk: read-only file syste
    m
    Unable to chmod /system/app/Superuser.apk: No such file or directory
    Unable to chmod /system/app/Superuser.apk: No such file or directory
    Usage: mount [-r] [-w] [-o options] [-t type] device directory

    Any help anyone?

    • I ran into the same problem, it’s because /system is read only.

      You have to remount the folder from read only to read/write. I’m not the not the best at explaining things, but I’ll try to get you through it.

      After “[+]forks XXXX childs” pops up, exit & reopen. Issue a “mount” command from the terminal, and look at the line that lists /system. Then change that line to mount -o remount,rw -t /system. For example, if you see:

      /dev/block/mtdblock3 /system yaffs2 ro 0 0

      The mount command you’ll enter will be:

      mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system

      All you should see is this pop up twice:

      Usage: mount [-r] [-w] [-o options] [-t type] device directory
      Usage: mount [-r] [-w] [-o options] [-t type] device directory

      /system is now read/write, so you can run ./Install-Root.sh with no problem.

      Hope this helps guy ;D

  6. When I run the final step of /data/local/tmp/Install-Root.sh

    it says it cannot create file in read only file system what do I do?

  7. Everything installed thru dos perfectly….now ConnectBot continues to say it cant find rageagainstthecage-arm5.bin…..which setting do i use in Connect bot ssh or local? please help im sooo close

    • ok so i got the file to install and NOW its saying it cant find Install-Root.sh and ive pushed it there a few times and am positive its there….anyone else have that problem or know whats wrong?

    • Same here – now ConnectBot continues to say it cant find rageagainstthecage-arm5.bin – Any Help. I’ve picked my way thru this fixing all the bugs I’ve come to. But I can’t get around this one.

  8. Got the problem, well it worked for me, after $ chmod 0755 rageagainstthecage-arm5.bin
    type ./rageagainstthecage-arm5.bin
    and then do the phone stuff:)

  9. $ chmod 0755 rageagainstthecage-arm5.bin
    Unable to chmod 0755 rageagainstthecage-arm5.bin: No such file or directory

    HELP!

  10. $ chmod 0755 rageagainstthecage-arm5.bin
    my computer doesnt find the file, but it IS there, any help?

    but in step 8 in host just grab the local and in nickname just put something, and thats it.

  12. when I run the adb shell this is what happens and nothing else. the phone does nothing at all.

    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Users\*******>adb shell
    $ cd /data/local/tmp
    cd /data/local/tmp
    $ chmod 0755 rageagainstthecage-arm5.bin
    chmod 0755 rageagainstthecage-arm5.bin
    $ chmod 0755 Install-Root.sh
    chmod 0755 Install-Root.sh
    $

    what am I doing wrong?

    and when I try step 8, I input the command ‘/rageagainstthecage-arm5.bin’ minus the ‘ and it says the ‘/rageagainstthecage-arm5.bin: not found’ minus the ‘. I then found out that the file was in fact no in that directory so i then manually moved the file there on the phone, again the same problem still happened.

    Any help at all? I can not get around this, would be a great help.

    • adb devices
      adb push C:\I1RootUpdate\Superuser.apk /sdcard/Superuser.apk
      adb push C:\I1RootUpdate /sdcard/su
      adb push C:\I1RootUpdate\rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
      adb push C:\I1RootUpdate\Install-Root.sh /data/local/tmp/Install-Root.sh
      adb push C:\I1RootUpdate\busybox /sdcard/busybox

      adb shell
      cd /data/local/tmp
      chmod 0755 rageagainstthecage-arm5.bin
      chmod 0755 Install-Root.sh

Searching for something else?

Chances are, we can find what you're looking for: