"Hard" Vs "Soft" rooted phone. Can't find the thread


  1. Stein1071

    Stein1071 Member

    The other day I stumbled across a thread somewhere about the difference between a "hard" and "soft" rooted phone. Basically, it was the difference between the "one click method" and the manual method but it talked about how you could alter the "one click" by changing some code in a boot image file. Can anyone link me to this thread or help me find any information on this. I'm having some issues with some things and I think the fact that I rooted with the "one click" method is what is causing the issues. Don't know why I didn't bookmark the thread but it is what it is. Thanks

    Advertisement
    :
  2. redsox985

    redsox985 Well-Known Member

    Are you talking like temporary vs. permanent root? AFAIK, "hard" and "soft" are only used in the Android community to describe the level of bricking a phone and it's reversability. Temporary root is lost on reboot whereas permanent is well...just that, unless you unroot. Perma rooting your phone shouldn't cause any issues unless you change anything.

    A rooted vs. stock phone will only look different in that the rooted one will have SuperUser in the app drawer, but will not function differently AT ALL unless you initiate something requiring root access (SuperUser privileges). This is usually where problems arise, not the actual root process.
  3. Stein1071

    Stein1071 Member

    No, I didn't think it was temporary vs permanent. Temporary so far as, gone on reboot. The thread actually talked about the one click method and it generally being a "soft" (I think by soft, the thread author probably meant easily/quickly reversible but I'm using their terminology) root type method but it could be altered into a "hard" root method by changing a variable in a line in a boot image. It even had a link to this page for help on unpacking and repacking the image.

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

    I've been having some issues with Droid Commander and a couple of other programs on my laptop and another machine that I'm trying to use with my phone. They keep telling me that I don't have root access. I've gotten that with a couple of apps as well, to the point that they were unusable. Anyway, I was researching along these lines when I fell on this thread. It mentioned the problem I was having specifically and the "hard" vs "soft" thing but I can't find anything about it now.

    Hell, maybe I dreamt it. I've been pretty stressed lately and not sleeping all that much.....
  4. Stein1071

    Stein1071 Member

    Nevermind. I found it & I know the issue with the terminology too. It's in the FAQ on Android Commanders website. Anyway, here's what I was getting at...

    Quoting Android Commander FAQ:

    My phone is rooted, but program runs without root access. Why?
    There are two types of root:

    • Soft Root: gives you root access from the shell and phone applications.
    • Hard Root: gives you root access from the ADB and the shell.
    You need this second.
    How to get ADB root access?
    You have two ways:

    • Flash any custom ROM, they are modified to work with root access.
    • Edit your boot image.
      • Pull out your boot.img.
      • Unpack.
      • Edit default.prop file, set value
  5. sjstokes1

    sjstokes1 New Member

    I have had this same problem with being able to use android commander because it says i dont have root access. It gives me instructions to pull the boot image and change on part of it to give me access. I am super new to this and have been trying to get to the boot image and everything else for days. I need to use this program to get clock work via rom manager to work can some one please break it down for me. I need to be able to access my phone via android commander.
Loading...

Share This Page