How to Root?


Last Updated: 2009-09-28 05:43:12
  1. Rastaman-FB

    Rastaman-FB Well-Known Member

    Hi there, while im quite up to date and comfortable with doing things on my phone there is one thing that i want to do but have conflicting information from various posts and websites.

    I want to "root" this bad boy but i also want to use the best/most uptodate recovery image along with the most accurate noobs guide to root.

    I work in IT and do work with the phone industry so ill be able to get my head around it.

    i just think there is far to much conflicting info out there

    can someone help me and get the best/latest guide to me?


    thanks in advance

    Advertisement
  2. Shayko

    Shayko Well-Known Member

  3. damuffinman

    damuffinman Well-Known Member

  4. Cougar

    Cougar Well-Known Member

    I was in the same position as you a couple of weeks ago. There's a lot of "guides" that are so terrifically updated and amended that making sense of it was a nightmare. I work in IT also, so I'm not 'technically challenged', but the Android platform is new to me and I didn't want to end up with a very expensive doorstop.

    After a lot of digging, I made the jump, and it went well. I made notes as I went, so if you can hang on a little while, I'll type it up into something sensible and post it up on here.
  5. Rastaman-FB

    Rastaman-FB Well-Known Member

    yeah i can wait for a while mate that would be nice
    im liking that hdbog post
  6. pegasus21

    pegasus21 Well-Known Member

    To root either the recovery or kernel images, you'll need to unpack the images. There is this perl script which will automate this as well as the repacking process.

    HOWTO: Unpack, Edit, and Re-Pack Boot Images - Android Wiki

    I haven't managed to unpack either recovery or kernel under windows so you'll probably have to do it under linux or from your phone.

    After you've unpacked recovery, you can easily modify rooted recovery v3 from the earlier post to the newer version of recovery. Main point is to modify default.prop to have the following parameters set as follows.

    ro.secure=0
    ro.debuggable=1
    persist.service.adb.enable=1

    Then edit init.rc to match v3's (this file is important for setting up the system and recovery settings). After that, just copy the files from the various folders where the unrooted ver is lacking. The picture files have been resaved as png to save space.

    You probably won't need to modify recovery since from what I can tell, it doesn't really change much in newer versions as it's only function is to recover the firmware.

    You can modify kernel for root though I think most users will probably just use su to get root on their adb. Any how the process to unpack is the same as recovery. After you unpack, modify default.prop similarily to the options above.

    In recovery v3, there's a menu option to give root for your normal usage (this is the root that most users would want). Just use that and it's done. If you want to pre-root your images, just get a tool to unpack the system image like unyaffs. Unpack system, drop su into bin and xbin. You could also pre-install busybox into the system image. After you've edited system to your likings, you can remake the image file with a tool called mkbootimg. I have to highlight that I've not edited and repacked a system image yet and I'm not sure how the permissions settings on the files will get affected so you would be better off editing it on a *nix system.

    Hopefully someone with experience in the latter part can shed some light on it.

    Oh yes, if you want to only flash a certain image file as opposed to the whole flashing process, you can just use fastboot to flash.

    To install busybox on a firmware on the phone, there are a few ways. Easiest is to either use the rooted recovery v3 image or a rooted kernel.

    If using the recovery, you'll need to boot up in recovery mode and connect your phone to your computer. For rooted kernel, just connect the phone when it's running normally and make sure adb is enabled in settings.

    1. Run "adb remount"
    2. Next push busybox with "adb push busybox /system/bin/busybox"
    3. Create the symlinks with "adb shell /system/bin/busybox --install -s /system/bin" (you can skip this part if you do not foresee using the rest of the commands that busybox provides)
    4. Modify cp's symlink to allow file managers to copy files "adb shell rm /system/bin/cp"
    "adb shell ln -s /system/bin/busybox /system/bin/cp"

    You should be able to use file managers to copy.
  7. Cougar

    Cougar Well-Known Member

  8. Rastaman-FB

    Rastaman-FB Well-Known Member

    i dont understand what the benefit of doing it your way over the guide posted at the top?

    this is why im scared of rooting. already in this post there are 3 clear different ways with different levels of difficulty

    i dont have linux and have no use for it at home or work so i figure your method is ruled out
  9. pegasus21

    pegasus21 Well-Known Member

    Well it's true the method i listed earlier is clearly harder than the guide posted by cougar. The benefit of creating pre-rooted images is that you can "distribute" it (note that google sent cyanogen a c&d letter for distributing google's closed source apps).

    Another is that you can customise the image in ways not available if you just use the guide.

    The very last part of the guide is mostly just for busybox installation. It can be integrated with the image or installed post-flashed. For file managers to properly copy files, you'll need to replace the cp symlink and link it to busybox.

    I forgot to mention that root in recovery is different from root in kernel and root for normal usage on the phone.

    Root in recovery is to allow you to do administrative tasks when you have problems with your firmware. It allows you to backup your firmware via nandroid.

    In kernel, it's mostly for root via adb or debugging for developers.

    The root in normal usage is where users are more interested in as I've mentioned as it allows you to run programs that can kill other programs for example. This is provided via the su command.
  10. Rastaman-FB

    Rastaman-FB Well-Known Member

    wanted to do it the proper way but cannot flipping work out how to install with adb driver for windows 7 x64.

    EDIT can access adb using andtroid test interface but fastboot does not respond
  11. pegasus21

    pegasus21 Well-Known Member

    Check out my post which is in post 18

    I've pretty much listed out all of the steps to get root that most people would want with fastboot.
  12. Rastaman-FB

    Rastaman-FB Well-Known Member

    yeah im rooted, will takle busybox tomorrow

    will say this though. fastboot was properly annoying on windows 7
    i sorted the adb by using the test version

    i had to then go into fastboot and as fast as i could link fastboot driver error to the adb test driver again. wait for device to boot fully and reboot back into fastboot but it recognised it this time for the flash recovery image.#

    thanks for everyones help
  13. pegasus21

    pegasus21 Well-Known Member

    Ah the timeout. Yea I know what you mean. lol Good to hear that you've done it. cheers.
  14. iMobile

    iMobile Member

    Has anyone tried rooting the galaxy using the "1 click root" method?
  15. pegasus21

    pegasus21 Well-Known Member

    It doesn't work on firmware II5 and probably later ones too.
  16. iMobile

    iMobile Member

    Oh I have H8 so I should be ok. Thanks for your input.

Share This Page